Resources Required for Setting Up the Database
For details about the supported versions, see the Readme.txt file available at the TIBCO BusinessEvents Enterprise Edition® Product Documentation page.
The file extension of the resource identifies the store type for which the resource is used:
.sql
- JDBC backing stores.tibdg
- TIBCO ActiveSpaces.cql
- Apache Cassandra
Provided Configuration Resources
The following table lists the resources available in TIBCO BusinessEvents at BE_HOME/bin for setting up stores.
Resource | Default Location and Notes |
---|---|
base_types.xml
|
The
base_types.xml file is used by the deployment utility. Do not edit this file.
|
|
Only used for manual SQL script generation. Generally not needed. You can use a TIBCO BusinessEvents Studio option instead.
See Generated SQL Scripts . |
create_tables_*.sql
|
Use the appropriate SQL (DDL) script for your DBMS. This script creates the tables that are used to maintain the metadata.
The script drops any existing tables and recreates them. |
dbkeywordmap.xml
|
This file contains mappings to handle words used in the TIBCO BusinessEvents project that are database reserved words. See Ontology Identifiers that Use Database Key Words for details. |
initialize_database_<database>.sql
|
Use the appropriate script for your DBMS.
By default the user is called
For SQL Server, this script also creates the default database, with the name
Note: Use a different user (and schema) for every TIBCO BusinessEvents project that needs a backing store. This script drops the user (and therefore all the tables) and adds the user again.
|
Generated SQL Scripts
These scripts are generated when you use the File > Export > TIBCO BusinessEvents > JDBC Deployment wizard. The value for yourname is specified in the Output Script Name Prefix setting. You specify the location of the scripts in the wizard.
You can manually execute the
be-storedeploy
executable. You specify script name prefix at the command line. Scripts are generated in the same directory where you run
be-storedeploy
.
Script Filename | Description |
---|---|
yourname.sql
yourname.tibdg yourname.cql |
This SQL (DDL) script creates schema tables and types. |
yourname.aliases |
This file has entries if the database table identifiers are longer than the DBMS maximum character limit. See and Configuring Aliases File and Project Schema Script . |
yourname_alter.sql
yourname_alter.tibdg yourname_alter.cql |
The
yourname_alter.sql script is for use in schema migration. Generated only after updates are made to the
be-storedeploy.tra file. See
Updating Existing Backing Store Schema .
|
yourname_delete.sql |
For use as needed. This script deletes the entities that have been marked as deleted in the object table. Restriction: Not applicable for TIBCO ActiveSpaces and Apache Cassandra.
|
yourname_cleanup.sql
yourname_cleanup.cql |
For use as needed. This script truncates the tables. Restriction: Not applicable for TIBCO ActiveSpaces.
|
yourname_remove.sql
yourname_remove.tibdg yourname_remove.cql |
For use as needed. This script removes the database schema. You can use it to reset the project. |