![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
• Ensure that you copied your JDBC drivers file to BE_HOME/lib/ext/tpcl (or other location in your class path). See Task A, Ensure DBMS Software and Drivers are in Place.You can generate the project-schema-specific SQL scripts using the JDBC Deployment wizard in TIBCO BusinessEvents Studio.
1. In TIBCO BusinessEvents Studio Explorer, right-click the name of the project for which are creating SQL scripts and select Export > TIBCO BusinessEvents > JDBC Deployment. Click Next.
2. You see the Generate JDBC deployment scripts wizard. Complete the values as follows.
The default value is oracle Browse to and select a directory where the scripts are to be generated, for example, BE_HOME/bin (This directory is used if you generate files manually.) Enter a prefix for the output script filenames. For example, if you enter acme, the following scripts are generated: acme.sql, acme.aliases, acme_alter.sql, acme_cleanup.sql, acme_delete, and acme_remove.sql.
− If you are creating a new JDBC backing store, click Finish. The scripts are generated in the location you specified. Information about script generation is also printed to the Console tab.
− If you are migrating an existing JDBC backing store, click Next. You see the Generate Migration SQL Scripts page. See step 4 for details.
If you are using SQL Server: Before you execute be-jdbcdeploy, open the BE_HOME/bin/be-jdbcdeploy.tra file for editing. Specify sqlserver. in the last line:
1.
2. Run be-jdbcdeploy.exe using a command with the following format: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. In Task J you run this script (together with provided scripts) to build the schema in the database.
Optional. Specifies the property file. If not specified, the default property file is used, that is, be-jdbcdeploy.tra in the current directory. Tip If you specify a directory path, the backing store scripts are generated in the specified directory and the last element of the path is taken as the schema output filename. Optional. Specifies the absolute path to the CDD file. See Cases That May Need Additional Setup to understand when the CDD file is needed.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |