Using the dynamic cache service
Use the dynamic cache service to improve application performance
by caching the output of servlets, web services, and WebSphere® Application
Server commands into memory.
Dynamic cache service multi-cell and multi-core group invalidation
Dynamic cache service multi-cell and multi-core group invalidation
enables caches created in different cells to be synchronized without
the cache entries being replicated across cell boundaries. When this
function is enabled for either servlet and object cache instances,
data gets cached in both cells as a result of the cells handling
the same traffic. When a cache entry is invalidated, using the Java
Message Service (JMS), the ID of the invalidated cache entry is sent
to a peer cell. The receiving cell uses a service integration bus
to process the invalidation. This function can also be used to propagate
invalidations to other core groups in the same cell.
Disabling template-based invalidations during JSP reloads
By setting the Java virtual
machine (JVM) com.ibm.ws.cache.CacheConfig.disableTemplateInvalidation custom
property to true, the template-based invalidations
are disabled during JSP reloads.
Dynamic cache provider for the JPA 2.0 second level cache
Learn to use the WebSphere Application Server dynamic cache
service as a Java Persistence API (JPA) second level (L2) cache provider.
JPA 2.0 has standardized the L2 cache interface. WebSphere Application Server supports the JPA
standard. The dynamic cache service plugs in as a level 2 cache provider
to JPA. The L2 cache boosts the performance of your JPA application
and you can configure and monitor the dynamic cache service for your
JPA application in the WebSphere Application Server environment.
Last updated: April 18, 2014 05:01 AM CDT http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-iseries&topic=container_dyn_admin File name: container_dyn_admin.html