Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 26 Backing Store Configuration : CDD Cluster Tab Backing Store Settings Reference

CDD Cluster Tab Backing Store Settings Reference
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 Backing Store Settings and Properties.
Note: Individual entities can be set to not use the backing store. See Has Backing Store in CDD Cluster Tab Domain Object Override Settings Reference.
Select which of the supported DBMS products to use: Oracle, SQL Server, or Berkeley DB.
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.
Checkbox unchecked means 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.
Checkbox checked means Cache Aside  Writes data to the cache and at the same time to the backing store. User controls are available for threads and queue size, and other options such as using parallel or sequential operations in the post-RTC phase.
See Chapter 10, Threading Models and Tuning in TIBCO BusinessEvents Architect’s Guide for more information.
See Setting up Shared Nothing Persistence for details on setting up Shared Nothing persistence.
ASYNC   This policy is recommended if you want to avoid frequent IO operations, which can slow inference agents.
SYNC  Solid State Drives (SSD) are recommended when using this policy.
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.
Although the limit is seldom reached, you can guarantee a connection is always available for a dbwriter thread as follows. Set the this field to the same value as the Agent.AgentClassName.dbthreadcount setting.
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.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved