Generating Scripts Manually

This section explains how to generate scripts using a manual procedure, instead of using the TIBCO BusinessEvents Studio wizard.

Note: If you are using the SQL Server, then before you execute be-jdbcdeploy, open the file BE_HOME/bin/be-jdbcdeploy.tra for editing. Specify sqlserver in the last line:
java.property.jdbcdeploy.database.type [oracle | sqlserver | mysql]

This step requires the EAR file for the project. The database utility uses the project ontology information from the EAR file.

Procedure

  1. Open a command window and navigate to BE_HOME/bin.
  2. Run be-jdbcdeploy.exe using a command with the following format:
    be-jdbcdeploy [-h] [--propFile] [-p property file] [-o schema output file] [-c CDDpath] [-a true|false] [-optimize] EAR Path
    For example:
    be-jdbcdeploy -o acme -c D:/myproj/acme.cdd D:/ears/acme.ear
  3. The generated scripts appear in the directory where you run the executable.
    For example, if you provide the schema output filename acme, you would see files called acme.sql, acme.aliases, acme_alter.sql, acme_cleanup.sql, acme_delete, and acme_remove.sql.

    The user-defined part of the database schema is in the schema output file (yourname.sql) as schema definition commands. The options are explained in Schema Definition Commands Options