Lotus Web Content Management caches (different Dynacache objects used by WCM)

    Web Content Management Cache Instances
    Web Content Management Item caching
    Web Content Management Summary
    Web Content Management Basic Caching
    Advanced and Resources
    Session Cache
    Menu
    Navigator
    Absolute path
    Missed Items
    Library
    Library Parent
    Draft Summary
    User cache


Lotus Web Content Management Cache Instances


With IBM WebSphere® Portal V6.1, the Lotus Web Content Management caches are managed through the IBM WebSphere Application Server Administration Console in the following location: Resources > Cache instances > Object cache instances.


Lotus Web Content Management Item Caching


services/cache/iwk/strategy – Lotus Web Content Management Item caching
Default size: 2000, default lifetime: infinite, usage pattern: regular.

This cache stores internal Lotus Web Content Management items. Any Lotus Web Content Management item read from the database will first check this cache. Lotus Web Content Management items cover Content, Workflow, Workflow Stages, Workflow actions, Taxonomies, Categories, Authoring Templates, Presentation Templates, Sites, Siteareas, and all Library Components. The cache entry will be updated or cleared when its corresponding Lotus Web Content Management Item is updated or deleted.


Lotus Web Content Management Summary


services/cache/iwk/objectsummary – Lotus Web Content Management Summary
Default size: 2000, default lifetime: infinite, usage pattern: regular.

This cache stores summaries of Lotus Web Content Management Items. The summaries are used to display in lists in the authoring portlet or used internally in the Lotus Web Content Management API to calculate Lotus Web Content Management Item Document IDs used for Iterators. The cache entry will be cleared when a Lotus Web Content Management Item is updated that will affect this summary.


Lotus Web Content Management Basic Caching


services/cache/iwk/module
Default size: 2000, default lifetime: infinite, usage pattern: regular.

This cache is used for Lotus Web Content Management 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 Resources
Default size: 2000, default lifetime: 1 month (configurable), usage pattern: regular.

This cache stores 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.

This cache also stores page data if Lotus Web Content Management Advanced caching is enabled. Refer to the Information Center for instructions on enabling Lotus Web Content Management 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.
Note: The session option for Advanced caching is not stored in the processing cache, but in the session cache.

Session Cache


services/cache/iwk/session - Session
Default size: 2000, default lifetime: infinite, usage pattern: regular.

This cache stores the page data for when session advanced caching is enabled. See the InfoCenter for enabling Lotus Web Content Management Advanced caching.


Menu


services/cache/iwk/menu - Menu
Default size: 2000, default lifetime: infinite, usage pattern: regular.

This cache stores Lotus Web Content Management 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 Navigator
Default size: 2000, default lifetime: infinite, usage pattern: regular.

This cache stores 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 Lotus Web Content Management Item update in the system.


Absolute Path


services/cache/iwk/abspath – Absolute path
Default size: 5000, default lifetime: infinite, usage pattern: regular.

This cache stores JCR path to ID relationships. The cache entry will be cleared when a Lotus Web Content Management Item is updated that will affect it.


Missed Items


services/cache/iwk/missed – Missed Items
Default size: 5000, default lifetime: infinite, usage pattern: regular.

This cache stores 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 Lotus Web Content Management Item is updated that will affect it.


Library


services/cache/iwk/global - Library
Default size: 2000, default lifetime: infinite, usage pattern: regular.

This cache contains 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 Parent
Default size: 2000, default lifetime: infinite, usage pattern: regular.

This cache stores 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 Summary
Default size: 2000, default lifetime: infinite, usage pattern: regular.

This cache stores the identity of the draft summary to the identity of the draft Lotus Web Content Management Item.


User Cache


User cache
Size is fixed to 2000. default is disabled.

This cache 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, you must 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< /code>
connect.businesslogic.module.template.remoteaccess=true
connect.businesslogic.module.template.autoload=false


Resources :
http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Lotus_Web_Content_Management_caches

No comments:

Post a Comment