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


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

CDD Cluster Tab Backing Store Properties 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.
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 > Backing Store > 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.
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.
See Write Behind Options in TIBCO BusinessEvents Architect’s Guide.
When distributed batch recovery is enabled (be.engine.cluster.recovery.distributed.strategy=batch), the recovery manager divides the target table into many smaller batches and assigns 1-to-n number of these batches to each node (for them to execute recovery).
Users can instead define be.engine.cluster.recovery.distributed.batchpernode=2 and prevent that too few, or too many batches are created
be.engine.cluster.useDBBatching
Note  For use with cache aside and only when the parallel operations feature is used.

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