Lotus Web Content Management caches (Tuning Guide 6.1.x)
Overview
WCM caches are managed through the IBM WAS Administration Console in the following location:Resources | Cache instances | Object cache instances
WCM Item Caching
services/cache/iwk/strategy - WCM Item cachingDefault size: 2000, default lifetime: infinite, usage pattern: regular.
Stores internal WCM items. Any WCM item read from the database will first check this cache. WCM items cover...
- Content
- Workflow
- Workflow Stages
- Workflow actions
- Taxonomies
- Categories
- Authoring Templates
- Presentation Templates
- Sites
- Siteareas
- Library Components
The cache entry will be updated or cleared when its corresponding WCM Item is updated or deleted.
WCM Summary
services/cache/iwk/objectsummary - Lotus Web Content Management SummaryDefault size: 2000
Default lifetime: infinite
Usage pattern: regularStores summaries of WCM Items. The summaries are used to display in lists in the authoring portlet or used internally in the WCM API to calculate Lotus Web Content Management Item Document IDs used for Iterators. The cache entry will be cleared when a WCM Item is updated that will affect this summary.
WCM Basic Caching
services/cache/iwk/moduleDefault size: 2000
Default lifetime: infinite
Usage pattern: regularUsed for WCM Basic caching. Refer to the Information Center for instructions on setting up Basic caching. The Basic cache stores the entire response. The key is based only on the URL so all users will see the same response.
Advanced and Resources
services/cache/iwk/processing - Advanced and ResourcesDefault size: 2000
Default lifetime: 1 month (configurable)
Usage pattern: regularStores the binary MIME for file and image resources in Lotus Web Content Management. The maximum size of resources to store is set in the Lotus Web Content ManagementConfigService.properties file as the property resourceserver.maxCacheObjectSize (in kb). Resources over this size are not cached and are streamed directly to the response. The expiry is set in the same file as: resourceserver.cacheExpiryDate. The cache entry will be cleared when that resource is updated.
Stores page data if WCM Advanced caching is enabled. Refer to the Information Center for instructions on enabling WCM Advanced caching. The processing cache stores advanced caches for the following types:
Site Similar to .Basic. Caching except that .Connect Tags. are processed each time. User Stores a copy of an item in the cache for each user. Secured Users that belong to the same groups will access the same cached items. Personalized Users who have selected the same personalization categories and keywords, and who belong to the same Group, will access the same cached items. The session option for Advanced caching is not stored in the processing cache, but in the session cache.
Session Cache
services/cache/iwk/session - SessionDefault size: 2000
Default lifetime: infinite
Usage pattern: regularStores the page data for when session advanced caching is enabled.
Menu
services/cache/iwk/menu - Menu
Default size: 2000
Default lifetime: infinite
Usage pattern: regularStores WCM Menu entries. An entry comprises of the Content IDs associated with a particular menu. The entries are retrieved and cached without applying security. Whenever a user needs that menu.s results, their specific security will then be applied to the cached results. A dynamic menu, which is one that is affected by the current user.s context (e.g. based on categories in a users profile) will store a separate cache entry for each different context. The cache entry will be cleared when a Lotus Web Content Management Item is updated that will affect this menu.
Navigator
services/cache/iwk/nav NavigatorDefault size: 2000
Default lifetime: infinite
Usage pattern: regularStores parent to child relationships that comprise a Lotus Web Content Management navigator. A complex navigator might have multiple parent to child relationships (e.g. if siblings are included). The navigator entry is made up of the IDs of the parent and children. This cache will be cleared upon any WCM Item update in the system.
Absolute Path
services/cache/iwk/abspath - Absolute pathDefault size: 5000
Default lifetime: infinite
Usage pattern: regularStores JCR path to ID relationships. The cache entry will be cleared when a WCM Item is updated that will affect it.
Missed Items
services/cache/iwk/missed - Missed ItemsDefault size: 5000
Default lifetime: infinite
usage pattern: regularStores JCR paths that does not exist. This is used primarily for multi locale solutions to determine if items of other locales exist or not. The cache entry will be cleared when a WCM Item is updated that will affect it.
Library
services/cache/iwk/global - LibraryDefault size: 2000
Default lifetime: infinite
Usage pattern: regularContains a lookup for library ID, name and path to the library object. This is pre-populated up to the cache size at Portal startup.
Library Parent
services/cache/iwk/libparent - Library ParentDefault size: 2000
Default lifetime: infinite
Usage pattern: regularStores a list of all children library IDs to a given parent ID. Introduced for Quickr to group libraries within a teamspace together.
Draft Summary
services/cache/iwk/draftSummary - Draft SummaryDefault size: 2000
Default lifetime: infinite
Usage pattern: regularStores the identity of the draft summary to the identity of the draft WCM Item.
User Cache
User cacheSize is fixed to 2000. Default is disabled.
Operates using a Least Recently Used algorithm. It is not shared across nodes in the cluster and it does not use dynacache. It does not update when LDAP changes. User cache is disabled by default but you can enable it with the following setting: user.cache.enabled=true in Lotus Web Content ManagementConfigService.properties. When you enable user cache, to run a module called MemberCacheManager or restart the server. To enable the module, add the following to Lotus Web Content ManagementConfigService.properties:
connect.businesslogic.module.template.class=com.presence.connect.wmmcomms
connect.businesslogic.module.template.remoteaccess=true
connect.businesslogic.module.template.autoload=false