Enable servlet caching

After a servlet is invoked, the output to be cached is generated, and a cache entry is created. The cache entry contains the output of the servlet and the side effects of the invocation. For example, side effects include calls to other servlets or Java Server Pages (JSP) files, as well as metadata about the entry, including timeout and entry priority information.

Unique entries are distinguished by an ID string generated from the HttpServletRequest object for each invocation of the servlet. You can base servlet caching on request parameters and attributes, the URI used to invoke the servlet, session information, or other options, including cookies.

Note: To enable servlet caching, the dynamic cache service must also be enabled. See Enable dynamic cache for more information. To enable servlet caching:

Note that when Servlet caching is enabled for the WebSphere_Portal Application Server, users receive an error while trying to access the WCM authoring portlet. To fix, download APAR# PK03601.

1. Start the WAS administrative console.
2. In the topology tree, expand Servers and click Application Servers.
3. Click the server you want to work with.
4. Click Web Container.
5. Select the Enable servlet caching check box under the Configuration tab.
6. Click Apply or OK.

Note: You must restart your application server for the changes to take effect.