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

Cluster Tab — Cache OM — Backing Store Settings
Unless otherwise noted, these settings are used both for the legacy (Oracle Types or Oracle-only) backing store and for the JDBC backing store. See JDBC Backing Store Configuration and Appendix A, Setting up an Oracle-Only Backing Store for setup details.
A limited cache  is used by default when the backing store is enabled. To override this default at the cluster level, add the following property and set its value to false: be.engine.cluster.isCacheLimited. You can also override the global setting at the entity level. See Entity-Level Configuration for Cache and Backing Store.
Note: Individual entities can be set to not use the backing store. See Metadata Properties for Entities (Events and Concepts).
com.tibco.be.oracle.BECoherenceOracleStore — for legacy Oracle backing store.
If you use Oracle Database, you have the option of using either the TIBCO BusinessEvents internal pooling implementation, or Oracle Database’s implementation. Possible values are as follows:
jdbc  Use the internal pooling mechanism.
oracle  Use Oracle’s pooling mechanism (see the class OracleConnectionCacheManager in the package oracle.jdbc.pool). When set to oracle then the TIBCO BusinessEvents pooling property values are used to set their corresponding to Oracle Database properties.
Write-behind  Writes data to the cache and then to the backing store. One write-behind thread is used for each entity type. See also tangosol.coherence.distributed.threads which is set in the Processing Units tab (see Processing Units Tab — General Settings and Properties.)
Cache-aside  Writes data to the cache and at the same time to the backing store. User controls are available for the threading and queue size. See Post RTC Options — Cache-aside and Write-behind.
Try running with default pool values and monitor the behavior. Using more connections improves runtime performance and can also speed up recovery in the event of a failure.
Specifies the project path, that is, the path from the project root to the JDBC Connection resource, to define the connection to the backing store. For example:
Used by JDBC backing store only if Cluster tab > Backing Store > Strategy is set to oracle. Also used by the Oracle-only legacy backing store.
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 MinLimit.
Maximum number of JDBC connections in the JDBC connection pool used for the backing store. Connections do not exceed the maximum.
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 MaxLimit.
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 InitialLimit.