Basic web content caching

This is the simplest caching option. The first time a web page is rendered by the Web Content Manager application, it is stored in a cache. Users then access this page from the cache until it expires. Only then is the web page rendered afresh. The main benefit of this scenario is improved performance. Basic caching should only be used on static content that does not require "real-time" access.

Advanced web content caching

There are two major differences between basic caching and advanced caching:

Advanced caching can cache pages based on different user profiles.

Cache parameters in connect tags and URL requests can be used to override your server's default advanced web content caching settings allowing you to set custom cache settings for individual web pages or components.

Table 1. Advanced caching types

Advanced caching type

Details

Site caching

This is the same as the basic web content cache except that cache parameters in connect tags and URL requests can be used to override your server's default advanced web content caching settings.

Session caching

When session caching is enabled, a copy of each Web page a user visits is stored in the session cache. The User accesses the cached version of a web page until they start a new session, or until the cached web page is expired from the cache.

User caching

When user caching is enabled, a copy of each Web page a user visits is stored in the user cache. The user accesses the cached version of a web page until the cached web page is expired from the cache.

Secured caching

Secured caching is used on sites where the item security features are used to grant different users access to different Web pages and components based on the groups they belong to.

Personalized caching

Personalized caching is used to cache web pages of users who have the same "personalization profile". This means that users who have selected the same personalization categories and keywords, and who belong to the same group, share a single cache.

Default web content caching versus custom caching

Cache parameters in connect tags and URL requests can be used to override your server's default advanced web content caching settings allowing you to set custom cache settings for individual web pages or components.

In most cases, basic, site and session caching would only be used as your server's default web content cache. User, secured and personalized caching would mostly be used when using custom caching in connect tags and URL requests.

Web Content Management Cache Instances

With IBM WebSphere® Portal, Web Content Management caches are managed through the IBM WebSphere Application Server Administration Console in the following location: Resources

Lotus Web Content Management Summary

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

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

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.

Menu

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

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.

Missed Items

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.

Draft Summary

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=trueconnect.businesslogic.module.template.autoload=false

Web content cache configuration

You can tailor the caching behavior of your web content environment by changing configuration settings such as the default cache type and expire settings.

You define and manage web content cache options in the WCM WCMConfigService service using the WebSphere® Integrated Solutions Console.