As with any procedure that modifies your data, ensure that you have made backups before you begin.
See Updating an Existing Oracle Database Schema for the impact of different kinds of changes and how you can update the backing store schema.Task A Prepare Files
1. Open your project in TIBCO Designer, and build the EAR file. Model information in the EAR will be used to build tables in the database.
2. Ensure that be-oracle.jar is located in BE_HOME/lib (or other location in your class path).
3. Copy your JDBC drivers file to BE_HOME/lib/ext (or other location in your class path). These files are part of the Oracle Client software.Task B Generate the SQL ScriptsOpen a command window and navigate to BE_HOME\bin. Run be-oradeploy.exe using a command with the following format:
If you are not running from the default folder (BE_HOME/bin) or if you are not using the default files, you must provide both the --propFile and the -p parameters, and pass them the fully qualified name of the TRA file. For example:be-oradeploy --propFile c:\mypath\myfile.tra -p c:\mypath\myfile.tra
Specifies the property file. If not specified, the default property file is used, that is, be-oradeploy.tra in the current directory. See note above. Specifies the Oracle schema output filename for deployment. In the command window, you see various messages as schema definition commands are created in the generated scripts and the scripts are created.The generated scripts appear in the directory where you ran the executable. For example, if you provided the schema output filename acme, you would see files called acme.sql, acme.aliases, acme_cleanup.sql, acme.delete.sql and acme_remove.sql.The user-defined part of the database schema is created in yourname.sql as schema definition commands. In Task E you run this script (together with provided scripts) to build the schema in the database.If the aliases file has entries, do the following to provide short aliases for all names longer than 30 characters (see Extra Procedure to Handle Long Database Identifier Names for more details):
1.
2. For each entity, property, and state machine name that exceeds 30 characters in length, provide an alias using a name that is shorter than 30 characters. Ensure the name is unique.TABLE.D_NewConceptNewConceptNewConceptNewConcept.alias= D_NewConceptNewConceptNewConceptNewConceptTABLE.D_NewConceptNewConceptNewConceptNewConcept.alias= D_NewConceptNewConceptNewCon
3. Perform Task B, Generate the SQL Scripts, again. This time, the aliases you created are used.
Running the initialize_database.sql script drops all existing backing store tables. If you have data you need to retain, contact TIBCO support for assistance.In the initialize_database.sql script, the Oracle user is set to be_user, with password be_user. You can edit the script as needed to change these default settings. The documentation uses the default username and password.
2. Navigate to the location of the scripts (or copy them all to the BE_HOME/bin directory) and open an SQLPlus prompt. (Open a command window, type SQLPlus then provide the system user credentials.)
3. Type @initialize_database.sql to run the provided script, initialize_database.sql. You see messages like the following:
Note that the script assumes that it has been run before. It deletes the user before creating it again. This means you can run the script again without having to take extra steps. This is useful for testing purposes.
Using your database product, you can configure additional users to access the database, in addition to this user.In this step, you run scripts to create the database schema under the user you created. The schema combines the definitions in base-types.xml, create-tables.sql, and the generated schema output file (acme.sql as an example).Note that these scripts also perform cleanup before creating the schema. The first time you run the scripts, you see harmless error or warning messages because there is nothing to delete.
1. Login to the Oracle server as be_user, password be_user (or whatever username and password you set in the script in Task D).
2. Navigate to the location of the scripts and open an SQLPlus prompt. Identify yourself as be_user with password be_user.
c.
Copyright © TIBCO Software Inc. All Rights Reserved.