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, 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. 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
Procedure
- In the administrative console, click Servers > Application servers > servername > Portlet container settings > Portlet container in the administrative console navigation tree.
- Select Enable portlet fragment cache under the Configuration tab.
- Click Apply or OK.
- Restart WebSphere Application Server.
See Manage 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 .
Related tasks
Configuring portlet fragment caching with the wsadmin tool