Direct migration from 3.0.0 and after to the current release is supported. After importing the 3.x project into BusinessEvents Studio, some manual steps will be required due to the changes in architecture.
In 3.x (and earlier), runtime properties were set using individual properties set in one or more TRA files. In some cases, runtime properties were set in TIBCO Designer, specifically in the BAR resource, and some were set in the TIBCO Designer TRA file.
Now only JVM-level properties (those that need to be used before the engine starts up) are set in the
be-engine.tra file. Properties that were set in the TIBCO Designer TRA file (
designer.tra) are now generally set in the
studio.tra file:
In 4.x, runtime properties and other deploy-time settings are configured using a structured XML file called the Cluster Deployment Descriptor (CDD). A multi-tab editor in BusinessEvents Studio enables easy maintenance of this file.
The CDD file provides fields for all commonly used settings, and it has property sheets where you can add other properties as needed. The property sheets are available at various levels, cluster, engine, and agent) so that you can scope the effect of the property appropriately.
When you import a 3.x project into BusinessEvents Studio, a CDD file is created using all known properties that can be automatically migrated. You must also check to ensure all properties are migrated. You may have to add some properties manually. Some properties are not relevant in the 4.x product, and additional properties not used in 3.x have been added to the product.
See Property Migration Reference for a list of 3.x runtime properties and their equivalent in 4.x.
If you use the preloading feature to load objects from the backing store into cache, you may have to reconfigure your settings. Configuration is done only in the CDD file now, and the logic of inclusion and exclusion has been simplified.
Some agents and processing units are created for you based on information available. After you import the project into BusinessEvents Studio, edit the CDD file to fully configure the agents and engines (processing units) as needed.
It is recommended that you use the current backing store implementation, the JDBC backing store. The JDBC backing store works with more DBMS products than the legacy Oracle-only backing store. It also has a more human-readable schema.
If you use the TIBCO BusinessEvents Decision Manager add-on, you must follow a procedure to import the 3.x decision project (containing the decision tables) after you import the related 3.x TIBCO Designer project. See the
TIBCO BusinessEvents Decision Manager User’s Guide for details.