Caching Notes
- Caching behavior can be configured in the ehcache.xml file that lives at the root of the ExpereIEServices.EAR.
- The following caches should be defined for Expere to function properly:
- ContentCompiledObject - holds compiled content
- Font - caches fonts used when rendering static documents
- Fontconfigcache: holds the font configuration cache information
- Image - holds images used when rendering dynamic documents.
- The default configuration of ehcache uses the Java temp directory when overflowing objects to the disk store. Adjust amount of maxBytesLocalDisk based on the amount of disk space available. The value is defaulted to 50GB; however, if that amount of disk space is not available then you should reduce that setting.
- If the application is going to be deployed multiple times on the same hardware (even in separate application server instances) the disk store path must not be the same for more than one application instance or their cache files will collide. Set the diskStore path to the perferred Expere cache storage location.
- Exercise caution if changing any percentages. It is unlikely that you will gain anything by changing these percentages. The updated ehcache.xml file allocates memory by percentage rather than elements. It is no longer necessary to adjust.
- The Expere Document Engine application has a Cache Manager page that may be used to check the status of each of the caches. The Cache Manager displays two level counts for the ContentCompiledObject and Image caches:
- Level one is hash values.
- Level two contains the actual cache objects. The purpose of level two is to avoid caching the identical object more than once.
- Template fonts are also cached.
