HP Integrity NonStop H-Series User Manual
Page 54
Table 13 Components of Infinispan (continued)
Element/Attribute
Component
•
default-cache:
Each cache container can contain multiple caches.
The default configuration of the cache container has only one
local-cache named local-ejb.
•
module:
The module whose class loader must be used to build this
cache container.
The following is a snippet:
passivation="false" fetch-state="false" purge="false">
This element defines a local cache. Inifinispan cache can be clustered in
multiple modes and one of them in LOCAL. In this mode, the cache acts
standalone. The following are the attributes for the same:
local-cache
•
name:
The name of the cache.
•
batching:
The batching feature in Infinispan that can improve the
cache performance. In NSASJ, batching is enabled since, the only
participant in cache operations is Infinispan.
This element sets the eviction policy. The entries are only evicted from the
local cache and not from the store. The following are the attributes for
the same:
eviction
•
strategy:
The entries to be evicted are selected based on the Least
Recently Used (LRU) pattern.
•
maxEntries:
The maximum number of entries allowed in memory.
This element configures the remote store which is the clustered Infinispan
HotRod server. The following are the attributes of the same:
remote-store
•
cache:
The name of the namedCache configured in the remote store
(Infinispan HotRod server). The entries that are evicted are stored in
that cache in the Hotrod server.
•
shared:
Specifies whether the store is shared by multiple caches. In
case of NSASJ, each instance of NSASJ shares the store. An indication
about the store sharing prevents the cache from making unnecessary
writes to the store.
•
preload:
If set to true, the cache loads the data in the store at startup.
This prevents any cache operations that result due to lazy loading.
•
passivation:
If set to true, data is written only to the cache store
when it is evicted from memory resulting in Passivation. The next time
data is requested, it is activated which means that data is brought
back to memory and removed from the persistent store. Whereas, if
false, the cache store contains a copy of the contents in memory, so
write to cache results in cache-store writes. This essentially gives
a write-through configuration. In case of NSASJ, the cache store
54
Configuring NSASJ