Backing Store Setup and Configuration

Setup refers to using the provided scripts to create the backing store schema for your project.

See Resources Required for Setting Up the Database for the DBMS-related requirements.

For the basic setup tasks, see Initializing the Database and Generate Non-Project Tables. However it is important that you first read the section Ontology Identifiers that Exceed the DBMS Maximum Column Length to understand if you need to do any special project configuration before running the scripts. (Other project configuration can be done before or after you do the setup tasks.)

In addition to setting up the backing store (and doing related project configuration for special cases), you also configure the TIBCO BusinessEvents Studio project to use the backing store according to your needs. You can do the following to configure backing store behavior:

  • Use the Shared All persistence option, with Database Type Oracle or SQL Server (formerly known as JDBC backing store).
  • You can use either write-behind or cache-aside database write strategy.
  • Tune the database connection pool properties.
  • You can use Use a limited or unlimited cache. You can define a global setting and configure object level overrides.
  • Control how the cache is preloaded from the backing store at startup. You can define a global setting and configure object level overrides.

See Configuring Backing Store Settings in the CDD (Now or Later).

You must also add a JDBC Connection resource to your project, before or after the backing store setup.

To make the flow of tasks simpler, all TIBCO BusinessEvents Studio project configuration is documented before the setup tasks, because some TIBCO BusinessEvents Studio configuration is required in certain cases. The procedures make it clear which configuration can be done before or after backing store setup.

Excluding Entities from the Backing Store

You do not have to use the backing store for all entities. In the CDD file you can specify entities for which you do not want to use the backing store.

Note: If later you want to include any excluded entities, you must change the setting and update the backing store setup as explained in Updating Existing Backing Store Schema .

See Configuring CDD for Special Cases (As Needed) for details.