Set 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.
Set portlet fragment caching with the WebSphere Application Sever admin console to save the output of portlets to the dynamic cache.
To enable portlet fragment caching...
- In the admin console, click...
Servers | Application servers | myserver | Portlet container settings | Portlet container
- Select Enable portlet fragment cache under the Configuration tab.
- Click Apply or OK.
- Restart WAS.
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
Next steps
Define a cache policy for the portlets. Portlets are not cached unless an applicable caching policy is defined in a cachespec.xml file.
Related concepts
Portlets
Related tasks
Set portlet fragment caching with wsadminSet caching policies for portlets