See Reset the Backing Store Tutorial for various levels of reset you can do if you want to reuse this tutorial example.What happens if I change the project ontology after setting up the database schema? If you change the project ontology you must update the database schema. You must also update the schema if you add an entity that you previously excluded from the backing store. A utility is provided that can handle most changes. Certain changes require manual updates. See the section Updating an Existing Backing Store Schema, in TIBCO BusinessEvents Administration.What are the minimum permissions for the database user? At a minimum, the user must be able to create tables and views. By default the BE_USER user created by the scripts has DBA privileges.The tutorial uses the default username (BE_USER) and password (BE_USER). You can change the username by editing the BE_HOME/bin/ initialize_databaseYourDBMS.sql script.
Running the initialize_databaseYourDBMS.sql script deletes the user before creating it again. Running the create_tables_YourDBMS.sql drops all database tables before creating them again. This means you can run these scripts again during test phases of your project development, without having to take extra cleanup steps.
1. Open a command window in BE_HOME/bin (default location of the scripts) and type the following command for Oracle (if you use the default SID you can omit @SID):This script creates the TIBCO BusinessEvents database user. This user must be used to run the other scripts. You see messages like the following:
Using your database product, you can configure additional users to access the database, in addition to this user.Next you log on as the TIBCO BusinessEvents user, BE_USER by default, and run a script to create non-project specific tables.
1. You see various harmless error messages the first time you run the script, and various messages saying Table created and Index created.This step requires the EAR file that contains the fraud detection project ontology. Use the file you built at the end of the section Configure the TIBCO BusinessEvents Studio Project
1.
2. Run be-jdbcdeploy.exe using the following command:be-jdbcdeploy -o fdstore C:\tibco\be\5.0\examples\standard\FraudDetectionStore\fdstore.earFor certain situations, you must also specify the CDD location. However the tutorial example does not require this.The generated scripts appear in the directory where you run the executable. If you are following the tutorial instructions, the following files appear in the BE_HOME/bin directory:The use of these scripts is explained in Table 49, Resources Required for JDBC Backing Store Implementation in TIBCO BusinessEvents Administration.
Note that the line beginning No valid database URL/Connection information provided" refers to a routine for migrating from an older backing store implementation to the current implementation. It does not indicate a problem in your setup.Summary and Next StepCongratulations! You are ready to deploy the FraudDetectionStore project.
Copyright © TIBCO Software Inc. All Rights Reserved.