Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Dynamic caching > Administer the dynamic cache service > Use the dynamic cache service
Configure servlet caching
After a servlet is invoked and completes generating the output to cache, a cache entry is created containing the output and the side effects of the servlet. These side effects can include calls to other servlets or JSP files or metadata about the entry, including timeout and entry priority information. Configure servlet caching to save the output of servlets and JSP files to the dynamic cache. To enable servlet caching, complete the tasks in the Using the dynamic cache service topic.
Unique entries are distinguished by an ID string that is generated from the HttpServletRequest object each time the servlet runs. We can then base servlet caching on:
- Request parameters and attributes of the Universal Resource Identifier (URI) that was used to invoke the servlet
- Session information
- Other options, including cookies
Because JSP files are compiled into servlets, the dynamic cache function treats JSP files the same as servlets, except in specifically documented situations.
Procedure
- In the admin console, click...
Servers > Server Types > WebSphere application servers > server_name
> Web container settings > Web container
- Select Enable servlet caching under the Configuration tab.
- Click Apply or OK.
- Restart WAS. Refer to the Managing application servers topic for more information.
What to do next
Define the cache policy for your servlets by Configuring cacheable objects with the cachespec.xml file.
Related
Dynamic caching with Asynchronous Request Dispatcher
Configure cacheable objects with the cachespec.xml file
Use the dynamic cache service
Manage application servers