Cache instances

 

+

Search Tips   |   Advanced Search

 

An application uses a cache instance to store, retrieve, and share data objects within the dynamic cache.

Each cache instance can be configured independently for...

Objects that are stored in a particular cache instance are not affected by other cache instances. This means that if you store an object named object_1 with a value of object_data in CacheInstanceX, you can also store an object with the same name, but different value in CacheInstanceY.

Objects that are stored in a particular cache instance are available to applications on other servers by accessing a cache instance of the same name. The two servers must be within the same replication domain to share data.

There are two types of cache instances...

An object cache instance is a location in addition to the default shared dynamic cache where J2EE applications can store, distribute, and share objects. After configuring object cache instances, you can use the DistributedMap or DistributedObjectCache interfaces in the com.ibm.websphere.cache package to programmatically access your cache instances.

Servlet cache instances are locations in addition to the default dynamic cache where dynamic cache can store, distribute, and share the output and the side effects of an invoked servlet.

The JNDI name that is specified for the cache instance in the console maps to the <cache-instance> element in the cachespec.xml configuration file. Any <cache-entry> elements that are specified within a <cache-instance> element are created in that specific cache instance. Any <cache-entry> elements that are specified outside of a <cache-instance> element are stored in the default dynamic cache instance.


 

Related tasks

Use the DistributedMap and DistributedObjectCache interfaces for the dynamic cache
Use object cache instances
Use servlet cache instances

 

Related Reference

Task overview: Accessing data from applications
cachespec.xml file