Chapter 24 Setting up a Backing Store Database : Resources Required for Setting Up the Database

Resources Required for Setting Up the Database
The table below lists resources required and sections following explain the procedures for setting up backing store tables.
This feature has been tested with Oracle 10g Enterprise Edition and Oracle Database 10g Express Edition (see the readme file for specific version information).
Oracle JDBC drivers are not provided. Download the client from the Oracle web site or find the drivers in your Oracle Client installation. Copy the JAR files (for example, ojdbc14.jar) to BE_HOME/lib/ext or elsewhere in your class path. Backing store functionality has been tested with Oracle Thin driver.
The initialize_database.sql script drops the user (and therefore all the tables) and adds the user again. By default the user is called be_user with the password be_user and has DBA rights. Edit the script if you want the user to have a different name or different rights.
The base_types.sql script defines the base types, corresponding to the BusinessEvents object data structure.
The create_tables.sql script creates the tables that are used to maintain the metadata.
yourname.aliases
yourname_remove.sql
yourname_cleanup.sql
yourname_alter.sql
These scripts are generated when you run the be-oradeploy executable, as explained below, and they are located in the same directory where you run be-oradeploy.
You provide the value of yourname when you generate the scripts.
The yourname.sql script is executed after the provided scripts are executed, as explained in the procedures below. It creates schema tables and types.
The yourname.aliases script has entries if your project has names longer than 30 characters. You must perform a procedure to provide aliases for long names, and then regenerate the SQL scripts again using the be-oradeploy utility. The procedure is explained in Task C, Shorten Long Names Using the Aliases File.
The yourname_remove.sql script can be used as needed. It removes the database schema. You can use it to reset the project
The yourname_cleanup.sql script can be used as needed. It truncates the tables.
The yourname_alter.sql script is for use in schema migration. Generated only if properties are added to be-oradeploy.tra, to identify the existing database and its user and password. See Updating an Existing Backing Store Database Schema.