There are two main steps to creating a globe cache:
- Setting the globe caching properties.
- Creating the globe cache tiles.
This topic explains the first step only, about the properties you can set for your globe server cache.
When you are ready to begin creating cache tiles after you have reviewed and set the properties described below, see Creating globe cache tiles for more information about creating the tiles.
Globe caching properties
The Caching tab of the Service Editor is the place where you can set globe cache properties. See Accessing globe cache properties for instructions on how to get to the Caching tab.
Below are the available cache settings on the Caching tab for globe services:
The server cache directory
From the Caching tab on the Service Editor, you can change the default server cache directory that was selected when you created the globe service. The drop-down directory will list all registered cache directories on the server.
When you install ArcGIS for Server, a server cache directory and its associated virtual cache folder is automatically created for you. The default location is <ArcGIS Server installation directory>/arcgis/server/usr/directories/arcgiscache. The server cache directory stores caches of prerendered tiles that your globe service uses for faster display. One server cache directory can hold multiple caches; however, if you want, you can add more than one server cache directory to your server.
Once the service is published, you can use the geoprocessing tools in ArcGIS to build the cache for you and store it in the cache directories. Cached services often require large amounts of storage on disk, so ensure your cache directories are adequately proportioned to handle the data created during the caching process.
To learn more about the server cache directory, see How globe caches work
Creating tiles on demand
Tiles are always created when users navigate the globe, so the option to create tiles on demand is always enabled. Tiles for previously uncached areas will be added to the cache when they are first requested by a client.
Note:
For elevation layers you must create the full cache using the globe cache generation tool mentioned above. A full globe cache is required in order to consume a globe service that contains an elevation layer since you cannot rely on users navigating the entire globe to create the cache on demand.
The map caching section contains a useful topic on using on-demand caching the most effective way. See Map caching on demand for detailed usage tips.
Allowing clients to cache tiles locally
Finally, you have the option to allow clients to cache tiles locally. When users navigate your globe service, by default, the tiles are stored on their local machines. This can improve performance if they tend to navigate the same areas. However, once you update your globe cache, their tiles will be outdated, and they will explicitly need to clear their local caches before they can see the changes. If you update your globe cache frequently, consider not allowing users to cache tiles locally.
Globe cache tile creation
After you have finalized your caching properties and published your globe service, right-click your service in the Catalog tree, and click Manage Cache > Manage Tiles to begin creating tiles. This geoprocessing tool can also be used to update if your data has changed.