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

Cluster Tab — Cache Manager — Domain Objects Settings
Add as needed to configure object management options at the object level. Mode determines whether objects are kept in memory, in cache, or both. Preload options define how objects are loaded from the backing store to the cache network at system startup.
Related settings are available using entity metadata properties. CDD settings override metadata settings.
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.
Default Level Settings
 
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.
See Chapter 8, Cache Modes and Project Design in TIBCO BusinessEvents Architect’s Guide to understand the effect of this setting.
Preloading settings are used only if a backing store is enabled. Preloading objects and object handles means loading the cache from the backing store at system startup. Objects and handles not preloaded are loaded when needed.
Unchecked: Uncheck to disable all preloading. If unchecked then all other preloading properties and settings including entity metadata settings related to preload are ignored.
Checked: If checked, preloading is enabled. The settings Preload Caches and Preload Handles determine if those preload settings are enabled.
If object preloading is enabled, this setting specifies the number of entries (objects) to preload for each domain object. Objects are fetched in a non-deterministic manner. Can be overridden at the entity level.
all: All objects are loaded into the cache from the backing store. Lower level settings can override this setting by excluding specified objects.
none: No objects are included. This setting overrides all lower level settings.
Default is all. However the Preload Enabled setting for all individual object settings is unchecked thus disabling all object preloading by default.
Specifies whether object handles are loaded into the ObjectTable cache. The ObjectTable cache holds references (handles) to the objects themselves. See The Role of the Object Table for more detail.
all: All object handles are preloaded. The Overrides settings can override this setting by excluding specified objects’ handles.
none: No object handles are preloaded. This setting overrides all lower level settings.
include: the object-level settings in the Overrides section specify which objects’ preload handles are included.
Entity Level Object Overrides and Settings
 
See Chapter 8, Cache Modes and Project Design in TIBCO BusinessEvents Architect’s Guide to understand the effect of this setting.
Unchecked: If unchecked, this object is not preloaded.
Checked: If checked, this object is preloaded.
If this object will be preloaded, this setting specifies the number of entries (objects) to preload for this domain object. Objects are fetched in a non-deterministic manner.
If the Default level property Preload Handles is set to all then you can set this property to false to override that setting and exclude this object’s handles from being preloaded.
If the Default level property Preload Handles is set to include then you can set this property to true to preload its handles.
If this object uses Cache+Memory mode, and Subscribe Cluster is checked, specify a subscription preprocessor. This preprocessor provides 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 that use the same mode. See Using Locks to Ensure Data Integrity Within and Across Agents in TIBCO BusinessEvents Architect’s Guide for details.