Configure dynamic fragment cache

 

+
Search Tips   |   Advanced Search

 

Overview

Dynamic fragment cache provides content caching and is configured through the WAS administrative console.

Note that when Servlet caching is enabled for the WebSphere_Portal appserver, users may receive an error while trying to access the WCM authoring portlet. To fix, install APAR# PK03601

 

Configure dynamic fragment cache

To configure dynamic fragment cache...

  1. Log in to the Administrative Console for WAS.

  2. Go to...

    Servers | Application Servers | portal_server | Configuration | Dynamic Cache Service

    ...and set the following fields...

    Startup state Enable service at service startup
    Cache size Type a value between 100 and 200000 to specify the maximum number of entries the cache holds.
    Default priority Accept the default value to to specify the default priority for cache entries, determining how long an entry stays in a full cache.

  3. Click Apply or OK to accept the changes.

To activate servlet caching...

  1. Log in to the Administrative Console for WAS.

  2. Go to...

    Servers | Application Servers | portal_server | Web Container | Configuration | Enable servlet caching | OK

 

Monitoring the cache

WAS provides Dynamic Cache Monitor for monitoring the contents and behavior of the fragment cache. Use Dynamic Cache Monitor to view cache statistics, contents, and policies.

To enable the Dynamic Cache Monitor application, install the CacheMonitor.ear file located in the <WAS_PATH>/installableApps directory. The application must be deployed on the server where WebSphere Portal is installed.

To access the Dynamic Cache Monitor application using the /cachemonitor URI, you need the necessary rights for the /cachemonitor servlet.

 

See also

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.