Configuring 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 administrative console to save the output of portlets to the dynamic cache.

Before you begin

To enable portlet fragment caching, you must complete Enabling the dynamic cache service.

About this task

Unique entries are distinguished by an ID string that generates from the PortletRequest object each time the portlet runs. You 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

Procedure

  1. In the administrative console, click Servers > Application servers > server_name > Portlet container settings > Portlet container in the administrative console navigation tree.
  2. Select Enable portlet fragment cache under the Configuration tab.
  3. Click Apply or OK.
  4. Restart WebSphere Application Server.

    See Managing application servers for more information.

What to do next

Define the cache policy for your portlets by Configuring cacheable objects with the cachespec.xml file.



In this information ...


Related concepts
Related reference

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 4:28:44 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-mp&topic=tdyn_portletcaching
File name: tdyn_portletcaching.html