CDD Cluster Tab Domain Objects Default Settings Reference

The Domain Object Default settings apply to all objects except those for which you explicitly configure overrides, using the Domain Object Overrides section.

See CDD Cluster Tab Domain Object Override Settings Reference.

CDD Cluster Tab Domain Object Default Settings
Property Notes
Mode
  With Cache OM, you can keep memory objects in the cache or Rete network using the following cache modes.
  • 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): Deprecated feature. Due to issues with concurrency, in clusters with multiple active inference agents, 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 Cache Modes and Project Design in TIBCO BusinessEvents Architect’s Guide to understand the effect of this setting.

    Default is Cache Only.

Preload Entities
  Specifies whether objects are loaded into the cache from the backing store on system startup (both normal startup and recovery).
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.

Default is unchecked.

Preload Handles
  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.

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.

Default is unchecked.

Preload Fetch Size
  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.

This setting applies to both objects and handles and cannot be set differently for each.

Objects and handles are fetched in a non-deterministic manner.

This setting can be overridden at the entity level.

Set to 0 to preload all. Set to a number to load that number of objects or handles (or both).

Default is 0. Ignored unless Preload Entities or Preload Handles or both are checked.

Check for Version
  This field applies to concepts that use cache-only mode or cache+memory mode.

An inference agent uses its L1 cache, a local cache of limited size, to improve access time to the concepts stored in the cluster cache. When an agent finds a concept instance in this local cache, the Check for Version setting determines whether the agent will use the instance directly, or instead check in the cluster cache for more recent version.

If Checked
(default value) The agent checks in the cluster cache for a more recent version. If a more recent version exists, it will be used, and will replace the one found in the local cache.
If Not Checked
The agent uses the instance found locally.

When content-aware load balancing is used, the local instance can be used without checking for version, improving performance.

Default is checked.

Constant
  This field applies to entities that use the cache-only mode or the cache+memory mode. In multi-engine deployments, use only for entities that do not change after creation.

The processing unit has a special local cache used only for entities marked as Constant. Entities placed in this cache are only removed when they are explicitly deleted. If the processing unit finds an entity in the constant cache, it will use it without checking in the cluster.

If Checked
The entity is marked Constant, and uses the constant cache.
If Not Checked
The entity does not use the constant cache.

Default is unchecked.

Evict from Cache on Update
  Used only if both of the following are the case:
  • Cache-aside database write strategy is used
  • The property Agent.AgentClassName.cacheTxn.updateCache is set to false (see CDD Agent Classes Tab Properties Reference )

    If checked: When a rule action changes the value of any of an entity’s properties, then the entity instance is evicted from the cache (updates are saved in the backing store)

    Use as needed to improve performance and cache memory management. For example, if an entity is not accessed frequently, it may save memory in the cache if the entity is evicted from cache after it is updated.

    Possible values are checked (true) and unchecked (false).

    Default is unchecked.

Is Cache Limited
  If checked, the cache size is limited.

Limited cache requires use of a backing store. See Configuring a Limited (or Unlimited) Cache .

The size of the entity cache and the size of the object table cache are set in the Object Management section of the Cluster tab.

If not checked, the cache size is unlimited.

You can override this default setting in entity overrides.

Default is unchecked.

Subscribe Cluster
  For objects that use 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.

Default is checked.