CDD Configuration Procedures : Entity-Level Configuration for Cache and Backing Store

Entity-Level Configuration for Cache and Backing Store
You can configure individual concepts and events and their properties as needed for special circumstances. Such configuration is not generally required. However, it is available for advanced tuning or for special situations.
The metadata properties related to preloading are used only if the CDD Cluster setting Preload Enabled is checked. See Understanding How Entity Objects are Managed for details.
Metadata Properties for Entities (Events and Concepts)
Metadata properties in an entity’s Metadata section are used to fine-tune backing store behavior. Additional meta properties that may appear are used with BusinessEvents add-ons. Only backing-store metadata properties are documented in this section. In most cases metadata property configuration is not required.
Metadata properties exist both at the entity level, and at the property level.
Note  These properties are ignored if the backing store feature has not been configured for the application or if it is configured but disabled in the CDD editor. See Cluster Tab — Cache Manager — Backing Store Settings.
For the Oracle-only (legacy) backing store, you can enter a custom type name, instead of the Oracle type name generated by the backing store scripts. This is useful for giving short or meaningful names to types.
You can enter a custom table name, instead of the name generated by the backing store scripts. This is useful for giving short or meaningful names to types. This setting is used for both the JDBC backing store and the Oracle-only (legacy) backing store. See Set Metadata Properties for Long Identifiers, as Desired for more details.
The property Agent.AgentClassName.cacheTxn.updateCache is set to false.
If set to true: When a rule action changes the value of any of this 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.
If set to true, this object is preloaded from backing store to cache. See Cluster Tab — Cache Manager — Domain Objects Settings to understand when this setting is used and how it is overridden.
If be.engine.cluster.isCacheLimited is set to true, then you can set this metadata property value to false so that for this entity the cache is not limited.
If be.engine.cluster.isCacheLimited is set to false, then you can set this metadata property value to true, so that for this entity the cache is limited.
There is no entity-level setting for the size of a limited cache. The size is set using this cluster-wide property:
Specifies how many objects of this type to load on at system startup. Used only this object is preloaded, based on the effective preload property. See notes for field Preload on Recovery, above.