CDD Cluster Tab Backing Store Settings Reference

Use this reference for the backing store settings.

Note: 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.

CDD Cluster Tab Backing Store Settings
Property Notes
Persistence Option: None

Specifies that 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 CDD Cluster Tab Domain Object Override Settings Reference .

Default is set to None.

Persistence Option: Shared All
Database Type Select which of the supported DBMS products to use: Oracle, SQL Server, or Berkeley DB.

Default is Oracle.

Strategy Used only if the Database Type is set to Oracle.

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.

Default is jdbc.

Cache Aside Available only for the backing store database types Oracle and SQL Server.

Choose between these two options:

  • 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 Threading Models and Tuning in TIBCO BusinessEvents Architect’s Guide for more information.

Enforce Pools Available only for the backing store database types Oracle and SQL Server.

Check this property if you want to enforce connection pool properties. See Database Connection Properties for the property details.

Default is unchecked.

Berkeley DB Data Store Path Available only for the backing store database type Berkeley DB.

Enter the absolute path of the data store to be used. The data store needs to be located on a network drive that can be accessed by all the cache nodes.

Persistence Option: Shared Nothing
Persistence Path Specifies the absolute path to the directory where the data is to be stored. For example, /tmp/datastore/.

Set this value for each individual processing units.

Persistence Policy Specifies the type of communication to be used to maintain persistence: asynchronous (ASYNC) or synchronous (SYNC).
  • 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.

Default is async.

Backing Store > Connection Settings

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.

Pool settings are used only if Enforce Pools is checked.

URI 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:
/SharedResources/JDBC Connection.sharedjdbc

You can also use a global variable to specify the connection.

Default value is %%DbUri1%%.

Min Size Minimum number of JDBC connections in the JDBC connection pool used for the 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.

Default is 10.

Max Size Maximum number of JDBC connections in the JDBC connection pool used for the backing store. Connections do not exceed the maximum.

The value of this property overrides the value of the Maximum Connections setting in the JDBC Connection resource.

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.

Similarly (and also seldom needed), with Coherence cache provider, you can guarantee a connection is available by setting this field to the same value as the property tangosol.coherence.distributed.threads.

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.

Default is 10.

Initial Size Specifies the initial size of the JDBC connection pool used for the backing store, when it is created on startup. 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 InitialLimit.

Default is 10.