Home


2.4.1 Features of DynaCache

The main features of DynaCache are described in Table | -2.

Table 2-2 DynaCache features

Cache object Description
Servlet/JSP results DynaCache can cache any existing whole page or fragment generated by a servlet or JSP. DynaCache matches data found in the HTTP request header with the cache rules specified in the XML configuration file - cachespec.xml.
Command cache

(Web Services, POJOs and EJBs)

Used to cache dynamic data before it is transformed into a presentable format (that is, HTML). These include EJB and Web service responses. A cacheable command object must inherit from the class com.ibm.websphere.command.cachableCommandImpl for it to work with DynaCache.
Replication support Enables cache sharing and replication in a clustered environment.
Invalidation support Includes rules-based, time-based, group-based, and programmatic cache invalidation techniques to ensure the freshness, consistency, and accuracy of the content.
Edge of network caching support Extends the WebSphere Application Server caches into network-based caches, through the implementation of external cache control and distributed-fragment caching and assembly support.
JSR168 compliant portlets DynaCache can cache any existing whole page or fragment generated by a servlet, JSP or a JSR 168 compliant Portlet1. DynaCache matches data found in the HTTP request header with the cache rules specified in the XML configuration file, cachespec.xml.
Cache monitor Cached results can be viewed and managed via a cache monitor J2EE application. The cache monitor provides a GUI interface to change the cached data manually. You have to install the application manually using the CacheMonitor.ear file (located in the <WAS_HOME>/installableapps directory) using the WAS Admin GUI.

This installable Web application provides a real-time view of the state of the DynaCache. The only way to externally manipulate the data in the cache is by using the cache monitor.

After installation, the cache monitor can be accessed as: http://your host_name:your port_number/cachemonitor.

1Support added in WebSphere Application Server v6.1.0.0

Note: We recommend taking great care if the cache monitor is enabled in production not to clear the cache using the monitor. If the cache is cleared in a production environment, it can lead to instability or poor performance until the caches are repopulated. If environment access is not controlled, we recommend not installing the cache monitor in production to eliminate any inadvertent use of cache clearing.

+

Search Tips   |   Advanced Search