Copyright © TIBCO Software Inc. All Rights Reserved |
This section outlines how to migrate 3.x projects, after you install TIBCO BusinessEvents 5.0 (as explained in Chapter 1 through Chapter 3 of this guide).
If you are migrating 3.0.0 projects that use the Oracle Types backing store, you must first upgrade your 3.0.0 installation to the latest 3.x version and update the Oracle Types backing store schema. After the schema update you can then migrate the data to the JDBC backing store, which you configure in the 5.0 version project.If you are using Berkeley DB Object Management, see For Berkeley DB Object Management Users Only for preliminary steps to take in order to change to Cache OM.
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. In TIBCO BusinessEvents Studio select Project > Validate to validate the project and then review the issues in the Problems tab and in the Error Log tab and resolve any errors. See Clean and Validate 3.x Projects.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:
• Add runtime engine properties to the CDD file at the appropriate level for the scope of the property:
− Processing Unit level for engine-wide scope in the specified type of engine (Processing Unit). You will have to think about your engines differently, as running different kinds of agent classes.
• TIBCO BusinessEvents properties that were configured in the TIBCO Designer TRA file generally go in the TIBCO BusinessEvents Studio TRA file:BE_HOME/studio/eclipse/configuration/studio.tra
• Remove the runtime properties that are now configured elsewhere from the TRA file and ensure that only JVM or system level properties remain. Leaving these properties in the TRA can cause problems at runtime.See Understanding the CDD File (For 3.x Users) for background information that helps you work with 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.0 are present in the CDD file.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.0).If you want to continue to use the 3.x project libraries, recreate the libraries and add them to the 5.0 project build path after migration. Follow instructions in the section Working with Project Libraries, in Chapter 2, 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 21, ActiveMatrix BusinessWorks Integration in TIBCO BusinessEvents Developer’s Guide for details.If you want to continue to use decision tables, you must purchase the TIBCO BusinessEvents Decision Manager add-on product. You import the 3.x decision project (containing the decision tables) after you import the related 3.x TIBCO Designer project (see TIBCO BusinessEvents Decision Manager User’s Guide).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. If you use cache OM, action is required:
• If you want to switch from Oracle Coherence to TIBCO BusinessEvents DataGrid, you must manually reconfigure the CDD file settings. See Configuring a TIBCO BusinessEvents DataGrid Cluster in TIBCO BusinessEvents Administration for details.
• If you want to continue using Oracle Coherence as the cache provider, you must acquire a licensed copy of Oracle Coherence software and do some configuration. See the Enabling Use of Oracle Coherence as the Cache Provider and Configuring Oracle Coherence Cluster Discovery sections in TIBCO BusinessEvents Administration for details.
• 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.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.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 J Rebuild EAR Files
Copyright © TIBCO Software Inc. All Rights Reserved |