Cluster Deployment Descriptor Reference : Cluster Tab — Cache OM — Backing Store Properties

Cluster Tab — Cache OM — Backing Store Properties
Add properties as needed depending on backing store configuration.c
Oracle Database Strategy  If the Cluster tab > Backing Store > Strategy field is set to oracle, then Oracle Database strategy settings are used, and this property corresponds to the OracleConnectionCacheManager class property WaitTimeout.
Specifies behavior when a connection is requested and there are already Cluster tab > Connection > Max Size connections active. If the be.backingstore.dburi.pool.waitTimeout.0 value is greater than zero (0), each connection request waits for up to the specified number of seconds. If no connection is returned to the pool before the timeout elapses, a No Database Connection available exception is thrown.
The waitTimeout and inactivityTimeout properties specify wait periods to minimize the creation and destruction of connections (an expensive operation).
Oracle Database Strategy  If the Cluster tab > Backing Store > Strategy field is set to oracle, then Oracle Database strategy settings are used, and this property corresponds to the OracleConnectionCacheManager class property InactivityTimeout.
Specifies the number of seconds an unused connection remains available (so that other threads can use it). After this period, the connection is closed and removed from the pool.
Oracle Database Strategy  If the Cluster tab > Backing Store > Strategy field is set to oracle, then Oracle Database strategy settings are used, and this property corresponds to the OracleConnectionCacheManager class property ReadTimeout.
Use this property to handle situations where engines running inference agents hang when the JDBC connection to the backing store is slow or intermittent. If no response is received from the database within the specified period, a call is aborted.
Specifies the number of transactions committed at one time. Set this property to the desired number of transactions to suit your needs.
By default, deleted entities are removed from the Oracle-only backing store automatically at system startup. Set this property to false to disable that behavior.
Specifies the user whose schema is used for the backing store. This property enables you use to a different schema than the schema of the user specified in the JDBC Connection resource. For example:
The user specified in the JDBC connection resource must have CRUD privileges to the schema of the user specified in the be.backingstore.dburi.schema.0 property.
Default value: If the be.backingstore.dburi.schema.0 property is not specified, the schema of the user specified in the JDBC connection resource is used.
If set to true the cache size is limited. Limited caches can be used only when a backing store is used to store entries in excess of the limit.
This property value is internally set to true if the Cluster tab > Object Management > Backing Store checkbox is checked. You can override the setting using this property, if you want to use an unlimited cache size with a backing store.
Also see notes for be.engine.limited.cache.back.size.limit.
Specifies the size of the limited cache, in number of cache entries for each object type in each agent where local storage is enabled (cache agents, and other agents where the local storage property is explicitly enabled).
See The Role of the Object Table in TIBCO BusinessEvents Architect’s Guide for more details about the object table.