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


Chapter 30 JDBC Backing Store Setup : Configure Backing Store Settings in the CDD (Now or Later)

Configure Backing Store Settings in the CDD (Now or Later)
You can do the backing store configuration before or after you configure the database itself. These settings are ignored by the setup utility.
Task D Configure Backing Store Settings and Properties (Now or Later)
Reference Tables
Reference tables for all the properties are documented here:
CDD Cluster Tab Backing Store Settings Reference
CDD Cluster Tab Backing Store Properties Reference
Configure Database-Related Settings
1.
2.
3.
In the Database Type field, select oracle or sqlserver, depending on the type of database you are using.
4.
If you select oracle then in the Strategy setting, also select the pooling strategy: oracle or jdbc. Connection pool settings are interpreted differently depending on your choice here, as documented in the reference tables listed above.
5.
See Post-RTC and Epilog Handling and Tuning Options in TIBCO BusinessEvents Architect’s Guide for more on write strategies.
6.
If you want to enforce JDBC connection pool settings and properties, check the Enforce Pools checkbox. If you do not want to enforce connection pool settings and properties, uncheck the box.
7.
Select Connection on the left do the following:
Domain Object Overrides
As desired, you can configure CDD settings related to domain objects (entity instances) such as mode, preloading, limited cache options. See Chapter 28, Domain Objects Configuration.
Preventing Database Outages when a Cluster Ceases with Processing
A new feature was added to allow that the Inference engine continues running during a database down period, when all database updates are buffered through the ActiveSpaces caching mechanism. Although the length of the database down period is limited by the available memory for ActiveSpaces datagrid (or by the buffer sizes in case of Coherence).
When database connections are restored, all buffered transactions will be played back and data loss will be avoided.
Required configuration settings:
1.
2.
3.
4.
5.
ObjectCacheFullyLoaded flag is set to 'true' (<property name="be.engine.cluster.isObjectCacheFullyLoaded" value="true"/>)
These settings make sure that all the data that Inference engine needs is already cached, and anything that is not found in the cache won’t be in the database either. Regardless whether or not database is available, if a 'read/get' does not find the searched entity in cache, database is never queried.
Suggested settings: In addition to the required settings, the following CDD settings are recommended:
1.
2.
3.
4.
<property name="be.backingstore.connection.retry.count" value="0"/> and with cache-aside database connections are not needed except during startup).
5.
<roles>*:info runtime.service:info kernel.core:debug backingstore:all jdbcstore:all jdbcstore.impl:all sql.text:all sql.vars:all</roles>
Limitations:

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