Configuring Backing Store for Cache OM
This topic provides the information on configuring the following backing stores:
- Oracle
- SQL Server
- DB2
- MySQL
- PostgreSQL
Additional backing stores are available only for Apache Ignite cache:
- ActiveSpaces, see Configuring ActiveSpaces as a Store Provider.
- Apache Cassandra, see Configuring Apache Cassandra as a Store Provider.
- Procedure
-
Open the project CDD file in TIBCO BusinessEvents Studio and on the Cluster tab, configure the cluster and cache provider as per your project requirements.
Cluster and Cache Provider Reference Topic Legacy ActiveSpaces cluster and cache Setting Up Legacy ActiveSpaces as Cluster and Cache Provider TIBCO FTL cluster and Apache Ignite cache Apache Ignite cluster and cache -
In the navigation tree, expand Object Management and select Persistence.
- In the Configuration window, from the Persistence Option list, select
Store
. -
From the Store Type list, select the backing store as required.
- Oracle
- SQL Server
- DB2
- MySQL
- PostgreSQL
-
ActiveSpaces, see Configuring ActiveSpaces as a Store Provider.
- Apache Cassandra, see Configuring Apache Cassandra as a Store Provider.
-
In the navigation tree, select Object Management > Persistence > Connection and in the configuration section, configure the settings mentioned in the JDBC Backing Store Connection Settings.
You can start 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.
JDBC Backing Store Connection Settings Property Description URI Specifies the JDBC 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%%.
To create a of JDBC Connection shared resource, see Shared Resources.
Min Size Minimum number of connections in the JDBC connection pool used for the backing store. Max Size Maximum number of 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 this field to the same value as theAgent.AgentClassName.dbthreadcount
setting.Initial Size Specifies the initial size of the JDBC connection pool used for the backing store, when it is created on startup. - In the navigation tree, select Properties and add properties based on your requirement. For details about of available propertiessee CDD Cluster Tab Backing Store Properties Reference.
- Save the CDD file.
be.engine.cluster.recovery.threads
in
CDD Cluster Tab Backing Store Properties Reference.