WAS v8.5 > Administer applications and their environment > Welcome to administering Dynamic caching > Administer the dynamic cache service > Use the dynamic cache service

Configure portlet fragment caching

After a portlet is invoked and completes generating the output to cache, a cache entry is created, containing the output and the side effects of the portlet. These side effects can include calls to other portlets or metadata about the entry, including timeout and entry priority information. Configure portlet fragment caching with the WebSphere Application Sever dmgr console to save the output of portlets to the dynamic cache.

To enable portlet fragment caching, you must complete the steps in the Using the dynamic cache service topic. Unique entries are distinguished by an ID string that generates from the PortletRequest object each time the portlet runs. We can then base portlet fragment caching on:

• Request parameters and attributes
• Session information
• Portlet-specific information, portlet session, portlet window ID, portlet mode, and portlet window state

1. In the dmgr console, click Servers > Server Types > WebSphere application servers > server_name > Portlet container settings > Portlet container > Application servers > server_name in the dmgr console navigation tree.

2. Select Enable portlet fragment cache under the Configuration tab.

3. Click Apply or OK.

4. Restart WAS.

   Refer to the Managing application servers topic for more information about managing the application servers.

Define a cache policy for the portlets. Note that portlets are not cached unless an applicable caching policy is defined in a cachespec.xml file. Refer to the Configuring cacheable objects with the cachespec.xml file topic for general task information about defining a cache policy. Refer to the Configuring caching policies for portlets topic for information about defining portlet-specific aspects in a cache policy.

Subtopics

• Configure caching policies for portlets
  Fragment caching for portlets requires defined a cache policy in a cachespec.xml file, either within the portlet WAR file or globally. If no caching policy is defined and applicable to a particular portlet, that porlet is not cached.
• Configure caching policies for portlets
  Fragment caching for portlets requires defined a cache policy in a cachespec.xml file, either within the portlet WAR file or globally. If no caching policy is defined and applicable to a particular portlet, that porlet is not cached.

Related concepts:

Portlets

Related

Configure portlet fragment caching with wsadmin
Use the dynamic cache service
Manage application servers
Configure cacheable objects with the cachespec.xml file

Reference:

Portlet container settings

+

Search Tips   |   Advanced Search