JTileCache Setup

chris.whitney@gmail.com

Building

Using maven to generate a war file: mvn package

Configuration

All JTileCache configuration is done in the jtilecache.properties file. Since this file is located inside of the packaged war file, it is a bit cumbersome to use (particularly on application servers that don't explode the war). Future versions might change this location to make it easier to use. If you are building JTileCache from source, you can also specify your configuration before packaging, which might be easier.

In addition to the jtilecache.properties file, JTileCache also uses properties files for commons-logging and cache configuration. Included are sample files for setting up commons-logging with log4j and configuring the JCS cache.

Running

Copy the war file into the webapps directory of your application server. JTileCache should be available at http://server:port/jtilecache/jtilecache . There is sample OpenLayers interface (if you have a Geoserver deployed alongside JTileCache and topp:states available) at http://server:port/jtilecache . Also included is src/docs/JCSAdmin.jsp, a basic cache viewer-- copy it into src/main/webapp (or copy into a running web application root folder) to use. it exposes cache clearing without a password, do not use it for a public-facing server.

Debugging

• IOError in logs: Broken Pipe in the logfiles usually occurs when a client stops a request. This usually occurs when openlayers pans around faster than the tiles are received.