Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Web content cache configuration
Caching options for IBM® Workplace Web Content Management™ are defined in the WCMConfigService.properties file.
File location:
- Windows:
portal_server_root/wcm/shared/app/config/wcmservices
- Linux:
portal_server_root/wcm/shared/app/config/wcmservices
- i5/OS:
portal_server_root/wcm/shared/app/config/wcmservices
Set the default Web content cache type
The default Web content caching environment for your Web content server is specified by editing the following properties:- connect.businesslogic.defaultcache
- connect.moduleconfig.ajpe.contentcache.defaultcontentcache
| defaultcache value | defaultcontentcache value | |
| No caching | False | None |
| Basic cache | True | N.A. |
| Site caching | False | Site |
| Session caching | False | Session |
| User caching | False | User |
| Secured caching | False | Secured |
| Personalized caching | False | Personalized |
Additional default Web content cache parameters
Web content cache configuration settings are specified by the following properties in the WCMConfigService.properties file.
The following properties can be defined for each cache:
| Basic cache |
connect.businesslogic.defaultcacheexpires connect.businesslogic.defaultcache connect.businesslogic.moduleresponsecacheconfig.flushexpiredinterval connect.businesslogic.moduleresponsecacheconfig.writeindexinterval connect.businesslogic.moduleresponsecacheconfig.cachedir connect.businesslogic.moduleresponsecacheconfig.memcachesize connect.businesslogic.moduleresponsecacheconfig.diskcachesize |
| Advanced cache: All |
connect.moduleconfig.ajpe.contentcache.defaultcontentcache connect.moduleconfig.ajpe.contentcache.contentcacheexpires connect.moduleconfig.ajpe.contentcache.flushexpiredinterval connect.moduleconfig.ajpe.contentcache.writeindexinterval connect.moduleconfig.ajpe.contentcache.cachedir connect.moduleconfig.ajpe.contentcache.memcachesize connect.moduleconfig.ajpe.contentcache.diskcachesize |
| Advanced cache: Session cache only |
connect.sessioncacheconfig.memcachesize |
| cachedir | The directory on your server used to store cached data. |
| contentcacheexpires | This sets the default expiry for all advanced caches. It can be either a relative period or an absolute date and time. |
| defaultcache | If true, basic caching is enabled. If false or missing, advanced caching is enabled. |
| defaultcacheexpires | This sets the default expiry for the basic cache. It can be either a relative period or an absolute date and time. |
| defaultcontentcache | If the advanced cache is enabled, the default advanced cache is set here. |
| diskcachesize | This is used to set the number of elements that can be held in a disk cache at any one time. If the value is 0, the disk cache will not be created. |
| flushexpiredinterval | This sets how often to check for expired items. (In seconds.) |
| memcachesize | This sets the number of elements that can be held in a memory cache at any one time. If the value is 0, the memory cache will not be created. |
| writeindexinterval | This sets how often to write the index to disk in seconds. 0 indicates to write on every change. |
Cache size strategy
Content is normally stored in a cache until it has expired. However, if your cache is configured too small, some cached content may be dropped from the cache to make room for newly cached content. This may result in a drop in performance. For this reason, it is important to configure your memory cache and disk cache to be large enough to store your most important content until it expires normally.
Dropping items from caches: Items least recently accessed from the cache will be the first dropped from a cache.