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

Cluster Tab — Cache OM — Backing Store Settings
TIBCO BusinessEvents Express  This section relates to Cache OM functionality and does not apply to TIBCO BusinessEvents Express edition.
For the related procedure, see Configuring a Cache OM Cluster — Cluster Tab.
If not checked, either the cluster does not have a backing store or the backing store is temporarily disabled, for example during testing phases of a project.
Note: Individual entities can be set to not use the backing store. See Has Backing Store in Table 8, Cluster Tab — Cache OM — Domain Object Override Settings (Sheet 1 of 4).
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.
If write-behind strategy is used with Oracle Coherence cache provider, you can also set tangosol.coherence.distributed.threads in the cluster level 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.
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:
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.