Cache OM with a Backing Store

To provide data persistence, you can implement a backing store for use with Cache OM.

During regular operation, cache data is written to the backing store. On system restart, data in the backing store is restored to the cache cluster.

Note: Database Disconnection Situations:  In the event of a lengthy database disconnection, no events are processed until the database connection is restored. Depending on configuration, event processing may continue for some time to avoid disruption from short disconnections. For example, engine processes are blocked only when the database write queue is full (either the write-behind queue or the cache-aside queue). For more on these options see Database Write Tuning Options for Cache Aside .

Implementing a Backing Store

To implement a backing store, you provide a supported database product. Scripts are provided to set up the database for your project’s ontology. If the ontology changes, scripts help you adapt the backing store accordingly (though some manual work may be required depending on the nature of the changes). Existing backing store data can be preserved.

For backing store configuration, see JDBC Backing Store Setup in TIBCO BusinessEvents Configuration Guide.

Configuring Backing Store Options

Various options are available for configuring the backing store for your needs, as explained in this chapter. See Storage and Retrieval of Entity Objects for more information about fine grained controls over data storage and retrieval.