Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 4 Migrating Projects from Earlier Versions : Migrating 3.x Projects

Migrating 3.x Projects
This section outlines how to migrate 3.x projects, after you install TIBCO BusinessEvents 5.1 (as explained in Chapter 1 through Chapter 3 of this guide).
 
Task A Import, Clean, and Validate the 3.x Project
1.
If you will migrate from the Oracle Types backing store or from a Berkeley DB OM to the Cache OM with JDBC backing store, keep the 3.x project
2.
Task B Configure Runtime Properties in the CDD File
Most of the configuration that was done in TRA files is now done in the CDD file. Ensure that all valid 3.x runtime settings (except JVM and system level properties) are configured in the CDD. Some properties are not relevant in the current version, and additional properties not used in 3.x have been added to the product. You may have to add some properties manually to CDD property sheets. Here are some tips:
BE_HOME/studio/eclipse/configuration/studio.tra
See Understanding the CDD File (For 3.x Users) for background information that helps you work with the CDD file.
Task C Check that be-engine.xml Settings are in the CDD File
You can change CDD file values at deploy-time without having to rebuild the EAR file. Therefore there is no need for the be-engine.xml file. (It was used to add properties to the TIBCO Administrator UI in order to make changes at deploy time.)
Check that all the properties from your 3.x be-engine.xml that are valid in 5.1 are present in the CDD file.
Task D Add Project Libraries (If Used)
Version 3.x project libraries containing entities (concepts, events and so on) are not compatible with project libraries in release 4.0.0 and higher, because the format for entities changed in the 4.0.0 release. They are not migrated.
(3.x project libraries that contain only shared resources will work in version 4.0.0 and up, but that is not a common use for project libraries. The format of shared resources remains the same in 5.1).
If you want to continue to use the 3.x project libraries, recreate the libraries and add them to the 5.1 project build path after migration. Follow instructions in the section Working with Project Libraries, in Chapter 1, Project Tasks of TIBCO BusinessEvents Developer’s Guide.
Task E Reconfigure TIBCO BusinessEvents-ActiveMatrix BusinessWorks Integration Projects (If Used)
Configuration of TIBCO BusinessEvents-ActiveMatrix BusinessWorks integration projects has changed. If a 3.x project contains TIBCO ActiveMatrix BusinessWorks or TIBCO Adapter resources, plan to use two projects: a TIBCO Designer project for the TIBCO Designer resources, and a TIBCO BusinessEvents Studio project. See Chapter 38, ActiveMatrix BusinessWorks Integration in TIBCO BusinessEvents Developer’s Guide for details.
Task F Migrate 3.x Decision Manager Projects (If Used)
If you want to continue to use decision tables, you must purchase the TIBCO BusinessEvents Decision Manager add-on product.
In a Decision Manager 3.x project, decision tables were in a separate project called a decision project, with a .dp file extension (along with related files). Decision projects were maintained in a separate application that is no longer used. The decision projects provided the decision tables for the TIBCO Designer project that contained the virtual rule functions (implemented by the decision tables).
To import 3.x decision projects you must first import the 3.x TIBCO Designer project into TIBCO BusinessEvents Studio as a TIBCO BusinessEvents Studio project. Then you import the related decision project into that TIBCO BusinessEvents Studio project. The decision table format is migrated to the current format during import.
1.
2.
In TIBCO BusinessEvents Studio, select Import from the File menu. You see the Import wizard Select dialog.
3.
4.
5.
The decision tables are now added to the TIBCO BusinessEvents Studio project.
6.
Task G Migrate 3.x Database Concepts and State Models (If Used)
If you want to continue to use database concepts or state models, you must purchase the TIBCO BusinessEvents Data Modeling add-on product.
After importing the project, you must configure the Cluster Definition Descriptor (CDD) file to add the JDBC connection project path or paths, and enable database concepts on all engines (processing units) where you want to use them. Steps are as follows:
1.
2.
3.
 
Task H Choose a Cache Provider and Configure Settings (Cache OM only)
Beginning with TIBCO BusinessEvents 5.0.0, Oracle Coherence is no longer provided with TIBCO BusinessEvents. An internal component, TIBCO BusinessEvents DataGrid, is used by default. See Migrating from Coherence to TIBCO BusinessEvents DataGrid Cache Provider for important information about migration of Coherence functions. If you use cache OM, action is required:
The property  tangosol.coherence.distributed.localstorage is migrated automatically to the cache-provider-neutral property be.engine.cluster.isSeeder. However, a change in design makes this property redundant. Cache storage is now set at the processing unit level, using a checkbox labeled Enable Cache Storage. It is not possible to set this checkbox at migration time. To complete migration, remove the isSeeder property and instead configure cache storage for non-cache agents as needed use the processing unit setting Enable Cache Storage in the project CDD file. Note that enabling cache storage on non-cache agents is not recommended for production. It can be useful for testing and demonstration purposes.
Task I Migrate Legacy Oracle-only Backing Stores to JDBC Backing Store
The legacy Oracle-only (Oracle Types) backing store is no longer supported. If you were using the legacy Oracle-only (Oracle Types) backing store, you must migrate to the current implementation. See Oracle Types to JDBC Backing Store Migration.
Task J (All Cases) Validate the Project in TIBCO BusinessEvents Studio
It is recommended that you validate the project in TIBCO BusinessEvents Studio after migration, to help ensure that the project is correctly configured.
Certain validation checks were added after 4.0. So validating the project may reveal issues that were not caught in the earlier release from which you migrated.
Task K Rebuild EAR Files
As with any upgrade, you must rebuild all EAR files created with an earlier version.
 
 
 

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved