Resources Required for Setting Up the Database
Provided Configuration Resources
The table below lists resources required and sections following explain the procedures for setting up backing store tables.
Resource | Default Location and Notes |
---|---|
Provided Files in BE_HOME/bin | |
base_types.xml |
The base_types.xml file is used by the deployment utility. Do not edit this file. |
be-jdbcdeploy
executable
be-jdbcdeploy.tra |
Only used for manual SQL script generation. Generally not needed. You can use a TIBCO BusinessEvents Studio option instead.
(See Generated SQL Scripts below). |
create_tables_oracle.sql create_tables_sqlserver.sql create_tables_db2.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_oracle.sql initialize_database_sqlserver.sql |
Use the appropriate script for your DBMS.
By default the user is called BE_USER with the password BE_USER and the user has DBA rights. Edit the script if you want the user to have a different name or different rights. For SQL Server, this script also creates the default database, with the name BE_USER and makes it the default database for the user BE_USER. |
Generated SQL Scripts
These scripts are generated when you use the File > Export > 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-jdbcdeploy executable. You specify script name prefix at the command line. Scripts are generated in the same directory where you run be-jdbcdeploy. |
|
yourname.sql | 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 | The yourname_alter.sql script is for use in schema migration. Generated only after updates are made to the be-jdbcdeploy.tra file. See Updating Existing Backing Store Schema . |
yourname_cleanup.sql | For use as needed. This script truncates the tables. |
yourname_delete.sql | This script is used for deleting entities that have been marked as deleted (applies only if write-behind database write strategy is used). |
yourname_remove.sql | For use as needed. This script removes the database schema. You can use it to reset the project. |