Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# 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.

Resources Required for JDBC Backing Store Implementation
Resource | Default Location and Notes
--- | ---
`base_types.xml` | The `base_types.xml` file is used by the deployment utility. Do not edit this file.
`be-storecdeploy.exe` `be-storedeploy.tra` | 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` `create_tables_as.tibdg` `create_tables_cassandra.cql` | 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` `initialize_database_cassandra.cql` | 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`. 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 > Backingstore Deployment > 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`.

Generated SQL scripts
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.
yourname_migration.sql | This script is generated to migrate existing database data from legacy ID format to new ID format for a project with shared all or store persistence configurations (with the new ID lookup implementations). When run on the existing database, the migration script copies the data to the new ID format by setting the extId as the primary key for all entities in database tables. The script adds a unique value wherever extId value is null for the rows in the existing database tables and also maintains all the reference and containment relationships of the data. Note: The former legacy ID tables are renamed with the suffix as `<TableName>_old`. You can delete these tables manually.

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.