You can
configure a local near cache to work along with a dynamic cache data
grid on the appliance or collective. The near cache uses local Java
virtual machine (JVM) resources. Typically, the near cache holds a
subset of the data that is in the dynamic cache data grid on the appliance.
About this task
To
enable the near cache for a dynamic cache data grid, you must set
a custom property to set the map template name for the WebSphere Application Server dynamic cache instance.
Procedure
Set the following custom property to
enable the near cache. - com.ibm.websphere.xs.dynacache.map_template_name: Specify IBM_DC_NCI_PARTITIONED_.* to
change the template name. Setting this custom property on a cache
instance enables a near cache for that cache instance.
For more information about setting custom properties on the dynamic
cache, see
Customizing a dynamic cache instance with custom properties.
What to do next
By default, the maximum size of the dynamic near cache corresponds
to the maximum number of entries for a single partition in the remote
dynamic cache data grid. A least recently used (LRU) eviction algorithm
is used to maintain this size. To further control the size of the
near cache, you can take the following action:
- Configure the com.ibm.websphere.xs.dynacache.near_cache_size custom
property to specify the maximum number of cache entries that are allowed
in the near cache. For more information, see Dynamic cache custom properties.