Configure portlet fragment caching
Overview
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 WAS console to save the output of portlets to the dynamic cache.
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
To enable portlet fragment caching, in the console, click...
Servers | Application servers | server | Portlet container settings | Portlet container | Configuration tab | Enable portlet fragment cache | OK
...and then restart WAS
What to do next
Define the cache policy for your portlets
Related tasks
Configure portlet fragment caching with the wsadmin tool
Related Reference
Portlet container settings