Migrating Projects from Earlier Versions : Oracle Types to JDBC Backing Store Migration

Oracle Types to JDBC Backing Store Migration
The Oracle-only (Oracle Types) backing store is not supported in 5.0.0  If you were using this backing store implementation in your prior version of TIBCO BusinessEvents, implement a JDBC backing store and migrate your data to it as explained in this section.
If you were using the JDBC backing store in any release, no migration is required.
Migration steps depend on whether you are migrating from 3.0.0, or from a later 3.x release, or from a 4.x release, as indicated in the tasks below.
During migration, you must keep the JDBC Connection resource for the existing Oracle-only backing store, and you must be able to connect to it.
The data migration process uses two backing stores, the legacy backing store and the new JDBC backing store. However after migration, you'll have one backing store. Use of two backing stores is limited to migration procedures.
If you plan to make any schema changes, make them after the backing store data is migrated successfully, following directions in TIBCO BusinessEvents Administration.
 
Task A All Versions
Back up your backing store data.
Task B 3.0.0 Only: Upgrade to 3.x and Update the Legacy Backing Store Schema
New TIBCO BusinessEvents metadata tables were added to the backing store schema in version 3.0.1. If you are upgrading from version 3.0.0, you first must upgrade to the latest 3.x version before you migrate data to a JDBC backing store.
1.
2.
3.
Login to the Oracle server as be_user, password be_user (or whatever username and password you are using, as set in the initialize_database.sql script).
4.
Navigate to the location of the scripts (by default in BE_HOME/bin) and open an SQLPlus prompt. Identify yourself as the user you logged in as.
5.
@create_tables.sql
Running this script does not affect any existing tables (therefore there is no need to run be-oradeploy.exe). Your database tables are now configured.
Task C 3.x Only: Import Projects into TIBCO BusinessEvents Studio
Import the project into TIBCO BusinessEvents Studio and ensure that the migrated project is configured correctly. See Migrating 3.x Projects for full details.
Task D Add a JDBC Backing Store
In this task, you set up a new backing store, including creation of a new JDBC Connection resource.
Do not remove the JDBC Connection resource for the Oracle-only backing store database from your project until you have completed all migration tasks.
1.
2.
It's a good idea to open your project again in TIBCO BusinessEvents Studioand test both the JDBC connections. If you need to make corrections to the connections, do so before you build the EAR.
3.
Task E Set Up the TIBCO BusinessEvents TRA File
Open the BE_HOME/bin/be-migration.tra file and specify appropriate values for the properties shown below, with example values. For notes on the properties see Backing Store Data Migration Property Reference.

 
# Oracle/JDBC Migration Properties
be.migration.batchsize 1000
be.migration.workersize 16
be.migration.objecttable true
be.migration.target.type jdbc
 
# Database URLs
# Source database:
be.oracle.dburi.count 1
be.oracle.dburi.0 /Resources/myORCL.sharedjdbc
be.oracle.dburi.pool.initial.0 5
be.oracle.dburi.pool.min.0 5
be.oracle.dburi.pool.max.0 10
 
# Target database:
be.jdbc.dburi.count 1
be.jdbc.dburi.0 /Resources/myJDBC.sharedjdbc
be.jdbc.dburi.pool.initial.0 5
be.jdbc.dburi.pool.min.0 5
be.jdbc.dburi.pool.max.0 10

 
Task F Run the Data Migration Process
1.
Open a command prompt, navigate to BE_HOME/bin, and execute the following command:
   be-migration -copy -ear EARFile
Wait until the process is complete
2.
If you set the property be.migration.objecttable=false in Task E then you must manually migrate OBJECTTABLE table contents. (Use your DBMS product documentation for this task.)
3.
Task G Remove Legacy Backing Store and JDBC Connection
When you have tested the migration and are sure that all is working well, you can remove the legacy backing store JDBC connection and archive, or otherwise remove, the legacy backing store files.
Backing Store Data Migration Property Reference
 
If the existing Oracle backing store contains a large amount of data, the migration process can take many hours to complete. If this is the case, you can shorten the process using this property.
When this property is set to false, the migration process ignores the data contained in OBJECTTABLE table. Skipping this table can shorten the migration time considerably.
If you skip migration of the OBJECTTABLE table, you must then copy this table from the Oracle to the JDBC backing store database using other tools (or simple SQL scripts).
jdbc: The JDBC backing store schema. Use this value for migrating from an Oracle backing store to a JDBC backing store (the procedure documented in this section).
oracle: No longer valid as an option.