Cluster Deployment Descriptor Reference : Cluster Tab — Cache OM — Domain Objects Settings

Cluster Tab — Cache OM — Domain Objects Settings
Configure object management options at the default (that is global) level, and as needed add entries to configure overrides at the object level.
Two tables are provided, one for the settings at the default level, and one for the similar settings that can be set for individual objects.
All objects use the default level settings unless you add an entry for them at the override level.
Default Level Settings
 
With Cache OM, you can keep memory objects in the cache or Rete network using the following cache modes. The setting you choose here applies to all objects except those for which you explicitly override this value.
Memory Only: Objects are not persisted in the cache. They are kept in the Rete network (working memory) only.
Cache Only: Objects are persisted in the cache. They must be loaded into working memory as needed. This is the most common choice for a cache cluster.
Cache+Memory (also written as Cache Plus Memory): Objects are persisted in the cache. They are also kept current in the Rete network.
Note: Due to issues with concurrency, use Cache Plus Memory only for constants and objects that change infrequently.
Note  If you set the mode to Memory Only, the rest of the properties in this section are not relevant and are ignored.
See Chapter 8, Cache Modes and Project Design in TIBCO BusinessEvents Architect’s Guide to understand the effect of this setting.
Checked: All objects are preloaded into the cache from the backing store. Lower level settings can override this setting by excluding specified objects.
Unchecked: No objects are preloaded. into the cache from the backing store. Lower level settings can override this setting by including specified objects.
Specifies whether object handles are loaded into the ObjectTable cache. The ObjectTable cache holds references (handles) to the objects themselves.
Handles are used in the object table. See The Role of the Object Table in TIBCO BusinessEvents Architect’s Guide for more details.
Checked: All object handles are preloaded. Lower level settings can override this setting by excluding handles for specified objects.
Unchecked: No object handles are preloaded into the cache from the backing store. Lower level settings can override this setting by including handles for specified objects.
If Preload Entities or Preload Handles or both are checked, this setting specifies the number of entity objects or handles (or both) to preload for each entity type whose objects or handles (or both) are configured to be preloaded.
Entity Level Object Overrides and Related Settings
 
Note  If you set the mode to Memory Only, the rest of the properties in this section are not relevant and are ignored.
Specifies whether objects of the specified type are loaded into the cache from the backing store on system startup (both normal startup and recovery).
Default: Use the Preload Entities setting specified at the default level.
True: Objects of the specified type are preloaded into the cache from the backing store. If the default level setting is not to preload entities, you can use this override to preload selected entities.
False: No objects of the specified type are preloaded into the cache from the backing store. If the default level setting is to preload entities, you can use this override to not preload selected entities.
Specifies whether object handles for the specified type are loaded into the cache from the backing store on system startup (both normal startup and recovery).
Default: Use the Preload Handles setting specified at the default level.
True: Handles for the specified type are preloaded into the cache from the backing store. If the default level setting is not to preload handles, you can use this override to preload selected entities’ handles.
False: No handles for the specified type are preloaded into the cache from the backing store. If the default level setting is to preload handles, you can use this override to preload selected entities’ handles.
If this object uses Cache+Memory mode, and Subscribe Cluster is checked, specify a subscription preprocessor. This preprocessor is generally used to provide locking to ensure data consistency. See Using Locks to Ensure Data Integrity Within and Across Agents in TIBCO BusinessEvents Architect’s Guide for details.
If this object uses Cache+Memory mode, check this checkbox to subscribe to subscription RTCs, so that changes to this object in one Rete Network are also changed in the Rete networks across all inference agents. See Using Locks to Ensure Data Integrity Within and Across Agents in TIBCO BusinessEvents Architect’s Guide for details.