The Map Tiling Service configuration consists of a set of global parameters that define how tiles are generated. These parameters are used if optional parameters defined in the named tiles are not specified. If a named tile has defined these parameters, then the parameters in the global configuration will be overwritten.
The following are global configuration paramters:
Description Required
Type Parameter
The URL defines the location of your local repository where resource are stored that are yes
string RepositoryURL
accessed by the Map Tiling service. This URL should point to the Repository Service rmi, for example:
http://localhost:8080/RepositoryService/rmi In most instances, this URL should not be changed.
Note:
The date on which the client should delete the map tile from the cache, and request a new copy from no
string ExpirationDate
the server. The ExpirationDate value must be specified as a W3C formatted date string (for example, 2013-12-31).
The ExpirationDate parameter has effect only when using external caching software such as Squid or Apache.
Note:
The available types of tiles generated by the tile server for named tiles when the MimeList is not specified.
no string
MimeList
The resolution of the tile images in dots per inch (the number of individual dots that can be placed no
integer MapResolution
within the span of one linear inch). The minimum dpi you can define is 72, anything less would render a poor quality image. If a value less than 72 is defined, the service will throw an exception. The rendering quality (anti-alias) of the tile images generated. You can specify either Speed or Quality. no
string MapRendering
If MapRendering is not specified in either the global configuration or in a named tile, the default rendering quality is Speed.
Tells the service not to render LabelLayers when generating a tile. The value is case-insensitive. If no
boolean RenderLabels
RenderLabelsis not specified in either the global configuration or in a named tile, the default is 'true'. Used to prevent the clipping of labels when a label crosses a tile boundary. The PadFactor controls no
integer PadFactor
the amount of space is rendered around the requested tile with 0 meaning no padding, 1 meaning padding of 1 tile around the requested tile and so on. If PadFactor is not specified in either the global configuration or in a named tile, the default is 1.0.
Internally, the Map Tiling service draws tiles to an offscreen bitmap (OSBM) (e.g., BufferedImage). To help speed up rendering of tiles by reducing garbage collection pauses, pools of offscreen bitmaps may be used to avoid constantly creating new ones. The OSBMPooling configuration controls how the offscreen bitmaps are created in memory.
If the OSBM pooling section of the configuration is removed, then pooling will not be enabled.
Note:
The following are OSBM configuration paramters:
Description Required
Type Parameter
Controls the maximum number of offscreen bitmaps (per tile dimension) that can be allocated by the no
integer MaxActive
pool (checked out to client threads, or idle in the pool) at one time. When non-positive, there is no limit to the number of objects per key. When this value is reached, the keyed pool is said to be exhausted. The default setting for this parameter is 8.
The minimum number of idle offscreen bitmaps (per tile dimension) that should always be available. no
integer MinIdle
If this parameter is set to a positive number and TimeBetweenEvictionRunsMillsis greater than zero, each time the idle object eviction thread runs, it will try to create enough idle instances so that there will be this number of idle instances available under each key. The default setting for this parameter is 0.
The maximum number of offscreen bitmap that can sit idle in the pool (per tile dimension) at any time. no
integer MaxIdle
When negative, there is no limit to the number of objects that may be idle per key. The default setting for this parameter is 8.
The global limit on the number of objects that can be in circulation (active or idle) within the combined no
integer MaxTotal
set of pools. When non-positive, there is no limit to the total number of objects in circulation. When MaxTotalis exceeded, all keyed pools are exhausted. When MaxTotal is set to a positive value and an offscreen bitmap is requested when at the limit with no idle instances available, an attempt is made to create room by clearing the oldest fifteen percent (15%) of the elements from the keyed pools. The default setting for this parameter is -1 (no limit).
The behavior when the pool of offscreen bitmaps is exhausted. The options are fail, grow, or block. no
string ExhaustedAction
Description Required
Type Parameter
Fail will throw an exception when an offscreen bitmap is requested when the pool is exhausted. Grow, the default, will create a new offscreen bitmap and return it, making MaxActive meaningless. Block will stop the process until a new or idle object is available.
Optionally, one may configure the pool to examine and possibly evict objects as they sit idle in the pool and to ensure that a minimum number of idle objects is maintained for each key. This is performed by an idle object eviction thread, which runs asynchronously. Caution should be used when configuring this optional feature.
Eviction runs require an exclusive synchronization lock on the pool. If they run too frequently or incur excessive latency when creating, destroying or validating object instances, performance issues may result. The idle object eviction thread may be configured using the
MinEvictableIdleTimeMillsand
TimeBetweenEvictionRunsMillsparameters. The minimum amount of time that an offscreen bitmap may sit idle in the pool before it is eligible no
integer MinEvictableIdleTimeMills
for eviction due to idle time. When non-positive, no object will be dropped from the pool due to idle time alone. This parameter has no effect unless TimeBetweenEvictionRunsMillisis greater than zero. The default setting for this parameter is 30 minutes.
How long the eviction thread should sleep before examining idle offscreen bitmaps. When
no integer
TimeBetweenEvictionRunsMills
non-positive, no eviction thread will be launched. The default setting for this parameter is -1 (i.e., by default, idle object eviction is disabled).