JDBC Backing Store

A backing store enables persistent backup of the objects generated and modified at runtime. Use of a backing store enables recovery in the event of a system-wide failure.

For instructions on migrating from the legacy Oracle Types (Oracle only) backing store to the JDBC backing store, see the migration chapters in TIBCO BusinessEvents Installation

The backing store feature requires use of Cache object management. Before you add a backing store, develop your caching solution and test it. Also ensure that your project ontology is completely configured.

Note:
  • Use a separate schema and schema owner for each project, even if different projects use the same ontology (otherwise ontology conflicts can occur).
  • If your project ontology changes after the backing store is in place, you must update the backing store schema. See Updating Existing Backing Store Schema .

The upper (blue) area in the diagrams shows TIBCO BusinessEvents Studio configuration tasks. The lower (yellow) area shows database setup utility tasks. The tasks shown map to task sections in this chapter.

For the simplest case where no additional project configuration is required (see Ontology Identifiers that Exceed the DBMS Maximum Column Length).

Main Tasks in Setting up a Backing Store
Note: Task D is not available for DB2 since DB2 uses the OS runtime authentication system. Therefore, this step (run the initialize database script) does not apply to DB2.
Complete Task Flow
Note: Task F is not available for DB2 since DB2 uses the OS runtime authentication system. Therefore, this step (run the initialize database script) does not apply to DB2.

For more information see Ontology Identifiers that Exceed the DBMS Maximum Column Length.