Caching the output of servlets, commands, and JavaServer Pages (JSP) improves application
performance. WebSphere® Application Server consolidates several caching activities including servlets, web
services, and WebSphere commands into one service called the dynamic cache. These caching
activities work together to improve application performance, and share many configuration parameters
that are set in the dynamic cache service of an application server. You can use the dynamic cache to
improve the performance of servlet and JSP files by serving requests from an in-memory cache. Cache
entries contain servlet output, the results of a servlet after it runs, and metadata.
About this task
The dynamic cache service works within an application server Java™ virtual machine (JVM), intercepting calls
to cacheable objects. For example, it intercepts calls through a servlet
service method or a command execute method, and either stores the
output of the object to the cache or serves the content of the object
from the dynamic cache.
Procedure
- The dynamic cache service is enabled by default.
You
can configure the default cache instance in the administrative console.
Refer to the Using the dynamic cache service topic for more information.
- Configure the type of caching that you are using:
- Configuring servlet caching.
- Configuring portlet fragment caching.
- Configuring Edge Side Include caching.
- Configuring command caching.
- Example: Caching web services.
- Configuring the JAX-RPC web services client cache.
- Monitor the results of your configuration using the dynamic
cache monitor.
Refer to the Displaying cache information
topic for more information about the dynamic cache monitor.
What to do next
To use the DistributedMap and DistributedObjectCache interfaces
for the dynamic cache, refer to the Using the DistributedMap and DistributedObjectCache
interfaces for the dynamic cache topic.