This section explains how to migrate data from an Oracle-only backing store to a newly created JDBC backing store or to an upgraded legacy Oracle-only backing store. As a result, the BusinessEvents engine can continue running under the new backing store, using historical data.It is strongly recommended that you migrate to the JDBC backing store implementation. See Migrate the Backing Store Implementation and Backing Store Data for guidelines.The process outlined here migrates the data from an Oracle-only backing store to a newly created JDBC backing store. You can also migrate data from an older Oracle-only backing store to a newer Oracle-only backing store, but that is a less common case.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. However after migration, you'll have one backing store. Use of two backing stores is limited to migration procedures.The first task is to set up a new backing store, including creation of a new JDBC Connection resource.
• If you are migrating to a JDBC backing store, follow all the instructions in Chapter 15, JDBC Backing Store Configuration, which is in TIBCO BusinessEvents Administration.
• If you are migrating to an Oracle-only backing store, follow all the instructions in Appendix A, Setting up an Oracle-Only Backing Store, which is in TIBCO BusinessEvents Administration.
Do not remove the JDBC Connection resource for the Oracle-only backing store database from your project until you have completed all migration tasks.When you have set up the new backing store, including the CDD settings, Rebuild the EAR file.Open the BE_HOME/bin/be-migration.tra file and specify appropriate values for the properties shown below (with example values). Notes on the properties follow.
1.
2. If you set the property be.migration.objecttable=false in Task B then you must manually migrate OBJECTTABLE table contents.
Copyright © TIBCO Software Inc. All Rights Reserved.