Migrating from Earlier Versions : Other Post Import Actions

Other Post Import Actions
This section lists other minor actions that may be required to complete the migration.
Backing store actions required may be more extensive. See Migrate the Backing Store Implementation and Backing Store Data for guidelines.
Check Runtime Properties, Remove from TRA, Add to CDD as Needed
See Runtime Properties are Configured in the CDD File for background information.
Check that all TRA file properties used in the 3.x project and that are valid in the 4.x project have been migrated. If any valid properties are missing, add them as needed:
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.
BE_HOME/studio/eclipse/configuration/studio.tra
Reconfigure Integration with TIBCO ActiveMatrix BusinessWorks
Integration is achieved differently in BusinessEvents 4.x because BusinessEvents is an Eclipse based product now, not a TIBCO Designer-based product. In all cases you’ll need to use two projects, one for BusinessEvents and one for ActiveMatrix BusinessWorks. A plug-in for BusinessEvents runs in TIBCO Designer to facilitate the integration.
See Chapter 21, ActiveMatrix BusinessWorks Integration, in TIBCO BusinessEvents Developer’s Guide for complete details. Below are a few pointers:
For TIBCO Administrator Deployment, CDD Replaces be-engine.xml
As explained in Check Runtime Properties, Remove from TRA, Add to CDD as Needed, properties that were formerly set in the TRA and other property files in 3.x are now configured using the CDD file.
In 4.x you can change CDD file values at deploy-time without having to rebuild the EAR file (the CDD file used is stored outside the EAR file).
Action
Ensure that all properties that were added to the 3.x project’s be-engine.xml file are present in the CDD file, if the properties are still in use in the 4.0 product.
Add Project Libraries to the 4.x Project
Version 3.x project libraries containing entities (concepts, events and so on) are not compatible with 4.x because the format for entities has changed. They are not migrated.
(3.x project libraries that contain only shared resources will work in 4.x, but that is not a common use for project libraries. The format of shared resources remains the same in 4.x).
Action
If you want to continue to use the 3.x project libraries, recreate the libraries and add them to the 4.x project build path after migration. Follow instructions in the section Creating and Using Project Libraries, in Chapter 2, Project Tasks of TIBCO BusinessEvents Developer’s Guide.