WAS v8.5 > End-to-end paths > Dynamic caching > Improving service with the dynamic cache service > Tasks: Using the dynamic cache service to improve performanceUse servlet cache instances
Before beginning, enable the dynamic cache service.
Perform this task so the application can access dynamic cache servlet cache instances. Using servlet cache instances can improve the performance of the application because we can store the output and the side effects of an invoked servlet. Servlet cache instances also give you the necessary control over the cache for multiple applications that are running in an application server.
- Enable servlet caching.
- Configure one or more cache instances.
- In the dmgr console, click...
Resources > Cache instances > Servlet cache instances
- Specify the scope of the cache instance.
Specify a scope of cell to make the cache instance available to all the servers that are in the cell. Node scope makes the cache instance available to all servers in a node. Server scope makes the cache instance available to the selected server only. If necessary, we can mix the scopes.
- Click Apply to save the scope.
- Specify the settings for the cache instance.
The Name and JNDI name fields are required. The JNDI name is the name attribute specified in the < cache-instance> element in the cachepec.xml file. An example of a JNDI name specified in the cachespec.xml file follows:
< cache-instance name="services/cache/instance_one">
In this example, specify services/cache/instance_one as the JNDI name.
- Update the application.
To use a servlet cache instance, specify a < cache-instance> element that has a name that is equal to the JNDI Name for this cache instance.
Subtopics
- Servlet cache instance page
- Servlet cache instance settings
- Use the DynamicContentProvider interface for dynamic cache
Related concepts:
Cache instances
Use object cache instances
Use the dynamic cache service
Configure servlet caching