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


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

Migrating 4.x Projects
This section outlines how to migrate 4.x projects, after you install TIBCO BusinessEvents 5.1 (as explained in Chapter 1 through Chapter 3 of this guide).
Task A Upgrade 4.0.0 Projects to 4.0.1
If you are running 4.0.0, first upgrade to 4.0.1. Open the 4.0.0 projects in TIBCO BusinessEvents Studio and save them.
Task B Import Projects in TIBCO BusinessEvents Studio
A command line utility to do the same actions is also provided. After importing using the command line utility an additional procedure is required before you can work with the project in TIBCO BusinessEvents Studio. See Importing an Existing TIBCO BusinessEvents Project at the Command Line.
For details about what is migrated, see Migration from 4.x to 5.1.
1.
2.
Select File > Import > Existing TIBCO BusinessEvents Studio Project and click Next.
3.
4.
Check the Copy project into workspace checkbox. This option copies the project into your current workspace.
Uncheck the Copy project into workspace checkbox and specify an import location.
5.
If your project has no HTTP channels, click Finish (this is the only option).
6.
If you clicked Next you see the Select Processing Unit dialog. Select the project CDD, and within it, the processing unit that contains the HTTP properties to be migrated.
All CDD files in the project are touched by the migration (see Migration from 4.x to 5.1 for details). However, only the CDD file specified here is used for HTTP channel property migration.
An informational panel displays the settings that will be migrated.
Task C TIBCO BusinessEvents Views CDD Change
If you use the TIBCO BusinessEvents Views add-on product, you may need to update the CDD for changes to the following dashboard agent properties:
The default is BE_HOME/views/web-root
Because the replacement properties now have default values, you only have to add the properties if you need to set a non-default value.
Do the following depending on your use case:
 
Task D 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 E 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 F (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 G Rebuild EAR Files
As with any upgrade, you must rebuild all EAR files created with an earlier version.
 
 
Importing an Existing TIBCO BusinessEvents Project at the Command Line
This option is equivalent to the following menu option in TIBCO BusinessEvents Studio: File > Import > TIBCO BusinessEvents > Existing TIBCO BusinessEvents Studio Project, explained in Task B, Import Projects in TIBCO BusinessEvents Studio.
After you complete the procedures in this section, complete the migration tasks as shown following Task B, as needed for your project.
When you use this command-line (or TIBCO BusinessEvents Studio) option to import 4.x TIBCO BusinessEvents Studio projects, the same migration actions are done as in the UI-based migration. See Migration from 4.x to 5.1
Before you can use a 4.x project imported at the command-line in TIBCO BusinessEvents Studio you must do another procedure, explained in To Open a Project Imported at the Command Line in TIBCO BusinessEvents Studio.
To Import an Existing 4.x Project at the Command Line
1.
Navigate to BE_HOME/studio/bin/ and open a command prompt.
2.
studio-tools -core importExistingProject [-h] -p studioProjDir [-o targetProjDir] [-c CDDprojectPath] [-u PUNameFromCDD]
For example:
studio-tools -core importExistingProject -p C:\FT\SomeProj -o c:\MyWorkspace\SomeProj -c COM.cdd -u Invproc
If HTTP channel properties are migrated (from a specified CDD and processing unit to all HTTP channel resources’ Advanced tab) you see a message like this:
Migrating HTTP properties of Processing Unit "PUName" from CDD "CDDprojectPath" to HTTPChannel(s) present in the project
When the import has completed successfully, you see a message in the command window like the following:
The existing 4.0 TIBCO BusinessEvents project has been successfully imported to c:\MyWorkspace\SomeProj.
Table 4, TIBCO BusinessEvents Studio Tools Options for Importing an Existing Project, provides detailed information about the options.
Specifies the importExistingProject operation for importing a TIBCO BusinessEvents Studio project into the workspace.
Optional but if specified -c must also be specified. Specifies the name of the PU (within the specified CDD) that contains settings to be migrated.
To Open a Project Imported at the Command Line in TIBCO BusinessEvents Studio
To open a project imported at the command line, you must add it as a new project.
1.
Start TIBCO BusinessEvents Studio. In Windows, click Start > All Programs > TIBCO > ENV_NAME > TIBCO BusinessEvents 5.1 > TIBCO BusinessEvents Studio.
2.
From the File menu select New > Project. You see the New Project — Select a Wizard dialog.
3.
Select TIBCO BusinessEvents > Studio Project and click Next.
4.
5.
6.
Click Finish. The project folders appear in the Studio Explorer view.
 
 

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