Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 4 Cluster Deployment Descriptor Reference : Cluster Tab — Cache OM — Backing Store Properties

Cluster Tab — Cache OM — Backing Store Properties
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.
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 WaitTimeout.
Specifies behavior when a connection is requested and there are already Cluster tab > Connection > Max Size connections active. If the be.backingstore.dburi.pool.waitTimeout.0 value is greater than zero (0), each connection request waits for up to the specified number of seconds. If no connection is returned to the pool before the timeout elapses, a No Database Connection available exception is thrown.
The waitTimeout and inactivityTimeout properties specify wait periods to minimize the creation and destruction of connections (an expensive operation).
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 InactivityTimeout.
Specifies the number of seconds an unused connection remains available (so that other threads can use it). After this period, the connection is closed and removed from the pool.
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 ReadTimeout.
Use this property to handle situations where engines running inference agents hang when the JDBC connection to the backing store is slow or intermittent. If no response is received from the database within the specified period, a call is aborted.
Specifies the number of transactions committed at one time. Set this property to the desired number of transactions to suit your needs.
Used with write-behind strategy only. By default, deleted entities are removed from the backing store automatically at system startup. Set this property to false to disable that behavior. See Handling Entities Deleted from a Backing Store for more details.

Copyright © TIBCO Software Inc. All Rights Reserved