If iShare Maps is configured to make use of tilecaches for base mapping then often the tilecache is placed on the publicly accessible DMZ server. If this is the case then the tilecache has to be updated from an internal copy as and when the base mapping is updated.
The other option with tilecaches is to create a reverse proxy on the DMZ server. This will point to a tilecache held on some internal server. The advantage of this is that the iShare Administrator only has to update one single tilecache - on the internal server. The disadvantage is that there may be some minor performance hit suffered by the internal server.
The following guide describes the process of setting a reverse proxy to handle tilecache requests.
For this example we'll presume there are four virtual directories set up in IIS on the internal server. All of these point to the tilecache root folder and are named tilecache0, tilecache1, tilecache2 and tilecache3.
IIS requires the Application Request Routing module in order to create a reverse proxy. Install this before continuing.
The mapsource should be configured with four tilecache URIs:
Now that's configured any request that is for any other of the tilecache0..3 directories will be rewritten to the internal server.