Managing the Mapping Service Configuration
The Mapping Service provides a simplified interface to perform Mapping Service rendering,
themes, overlays, and conversions. It provides both simple operations that are more
frequently used, or more complex operations that require higher levels of customization.
The Mapping Service is configured and managed using the Spatial Manager utility. See
Mapping Service in the
Services section of the Spectrum Spatial Guide for more information.
To view the Mapping Service settings, select Spatial Manager. From the Settings page, click
Edit to configure the following Mapping Service settings:
- Image directory
- The temporary cache directory for map images used during SOAP requests for the Mapping
Service, when returnImage is set to false in the request.
Important: If you change this setting to use an image directory that already contains
files or directories, be aware that those files and directories will be deleted
due to the nature of cache directories.
- Access Base URL
- The URL location for the image directory, typically
http://hostname:port/rest/Spatial/MappingService/internal/imageCache.This allows map images to be retrieved
using HTTP GET.
- Expire images after
- Time (in seconds) to wait until the image file is tagged for deletion from the
- Scan image directory for expired images every
- The interval (in seconds) that the service scans the image cache for expiring
Any changes you make to the Mapping Service configuration are automatically loaded; you do not
need to reload a modified configuration using the JMX console.
Note: The Mapping Service configuration file MappingConfiguration is
pre-configured and located in the Configuration directory under the
root repository. For example, a default installation will place the Mapping Service
configuration file at
Although you can use a WebDAV tool such as WebFolders to copy this configuration file
from the repository then upload the modified file, manual editing of this file should
only be done by advanced users who require functionality that is not supported by the
current version of Spatial Manager (v10.1). Unexpected results may occur
when using a manually edited configuration file with Spatial Manager.