CDD Cluster Tab Domain Object Override Settings Reference

Many settings simply override the value of default settings.

See CDD Cluster Tab Domain Object Default Settings for general details about the use of each setting. The table below only provides details that are specific to overrides.

CDD Cluster Tab Domain Object Override Settings
Property Notes
Entity URI
  Specifies the project path to the entity for which overrides are being set. Defaults to the selected entity’s URI. For example: /Concepts/MyConcept.
Mode
  Overrides the Default level setting for this object type.
Memory Only Mode
If you set the mode for an entity to Memory Only, the rest of the properties in this section are not relevant and are ignored. Backing store is disabled for entities that use Memory Only mode.
Caution
If you change from Memory Only mode to a cache mode after the backing store has been set up, you must update the backing store schema. See Updating Existing Backing Store Schema .
Preload Entities
  Specifies whether objects of the specified type are loaded into the cache from the backing store on system startup (both normal startup and recovery).

Overrides the Preload Entities setting at the Default level.

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.

Default is default.

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

Overrides the Preload Handles setting at the Default level.

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 prevent preloading the selected entities’ handles.

Default is default.

Preload Fetch Size
  Overrides the Preload Fetch Size setting in the Default settings.
Check for Version
  Overrides the value of the same-named setting in the Default settings.
Constant
  Overrides the value of the same-named setting in the Default settings.
Evict from Cache on Update
  Overrides the value of the same-named setting in the Default settings.
Is Cache Limited
  Overrides the value of the same-named setting in the Default settings.
Subscribe Cluster
  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.
Subscription Preprocessor
  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.

The required signature for a subscription preprocessor is as follows:

boolean FunctionName(long id, String extId, int typeId, int version, boolean isDeleted)

Cache plus memory is a deprecated feature. See TIBCO BusinessEvents Release Notes for details.

Backing Store Section
Has Backing Store
  Used only if the Backing Store > Enabled checkbox is checked. To exclude an entity from the backing store, uncheck the Has Backing Store checkbox.
Caution
If you enable this override setting after the backing store has been set up, you must update the backing store schema. See Updating Existing Backing Store Schema .
Concepts Related by Containment or Inheritance
All concepts related by containment or inheritance must either be included in the backing store or excluded from the backing store. That is, they must share the same value for the Has Backing Store setting.

Default value is checked.

Table Name
  Specifies a table name to be used in the backing store. Typically used if the entity name is long. See Ontology Identifiers that Exceed the DBMS Maximum Column Length for details.
Properties Metadata Section
Property
  Displays the property name. Read-only.
Present in Index
  If checked, sets an unordered index on the property.

Used only if Oracle Coherence is the cache provider. Also used only if the query agent has enabled indexing: see be.agent.query.enable.filter.optimizer in CDD Agent Classes Tab Properties Reference .

Encrypted
  Specifies whether the property should be encrypted. The values are:
  • true
  • false (default)
Note:
  • For field level encryption to work, cluster level "Security" must be enabled and policy file must have 'data_encryption=true' set in it.
  • Fields that are indexed can not be selected for encryption.
  • Fields that are used in query filters should not be encrpyted.
Max Length
  Used with backing store to specify the length of string properties that exceed 255 characters (that is the actual contents stored in the column is more than 255 characters). Specifies the expected maximum length for the property. See String Properties that Exceed the DBMS Maximum Column Length for details.
Reverse References
  This setting is for use only with ConceptReference type concept properties.

With a backing store, database updates related to a referring concept in a referenced concept can cause decreased performance. This happens when there are very many reverse references in a shared instance (referenced by many other instances).

To address this issue, set the value to false for ConceptReference type properties.

If you set the value to false, you must explicitly remove ConceptReference properties for deleted referenced concepts in the referring concept in your code.

For example, if employee is a ConceptReference type property in a concept acme, and smith is an instance of a concept type employee, then you would set Reverse References to true for the employee ConceptReference property, and you would add something like this to rules:

acme.employee = null;
Instance.deleteInstance(smith);

Or, for array properties:

Instance.PropertyArray.removeConceptReference(acme.employee, smith);
Instance.deleteInstance(smith);

Default is true.