This section outlines how to migrate 4.x projects, after you install TIBCO BusinessEvents 5.0 (as explained in Chapter 1 through Chapter 3 of this guide).
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.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.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 a TIBCO BusinessEvents 4.x Project at the Command Line.
1. After installing TIBCO BusinessEvents 5.0, start TIBCO BusinessEvents Studio using a different workspace from the workspace containing the 4.x projects.
2.
− 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.
− 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.0 — Automatic Migration Changes for details). However, only the CDD file specified here is used for HTTP channel property migration.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 value is index.htmlBecause the replacement properties now have default values, you only have to add the properties if you need to set a non-default value.
• If you have not changed the provided 4.x property values, and don’t need to use a non-default value in 5.0, remove the 4.x properties from the CDD.
• If you changed the value for one or both of the above properties, rename the property or properties to the 5.0 name (as shown above). Do this in the dashboard agent properties area of the CDD, for all affected dashboard agents (or at a higher level as appropriate to the scope you want to use).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 G Rebuild EAR FilesThis option is equivalent to the following menu option in TIBCO BusinessEvents Studio: File > Import > TIBCO BusinessEvents > Existing TIBCO BusinessEvents 4.0 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.0 — Automatic Migration Changes.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.
1. Navigate to BE_HOME/studio/bin/ and open a command prompt.studio-tools -op importExistingProject [-h] -p studioProjDir [-o targetProjDir] [-c CDDprojectPath] [-u PUNameFromCDD]studio-tools -op importExistingProject -p C:\FT\SomeProj -o c:\MyWorkspace\SomeProj -c COM.cdd -u InvprocIf 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 projectWhen 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 5, TIBCO BusinessEvents Studio Tools Options for Importing an Existing Project, provides detailed information about the options.
-op importExistingProject Specifies the importExistingProject operation for importing a TIBCO BusinessEvents Studio project into the workspace. Source project: absolute path to the project directory of the TIBCO BusinessEvents Studio project to be imported. Optional. Absolute path to the target project directory, where the project is imported to.If you specify the source project directory name as the last element in the path, it is used as the target project directory. If you specify a different directory as the last element in the path, the directory is created if it does not exist, and the source project directory is imported within the specified target directory.If you do not specify a target project directory, the original project contents are updated. If the project to be imported is a TIBCO BusinessEvents version 4 project, it is no longer compatible with version 4 after the import.If the target location points to an existing project, the import does not proceed and this message displays: Optional. The CDD to use for migration actions. Project path of the CDD (path relative to the root directory of the source project). 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.HTTP channel settings from this PU are migrated to all HTTP channel resources in the project.
1. Start TIBCO BusinessEvents Studio. In Windows, click Start > All Programs > TIBCO > YourEnvironment > TIBCO BusinessEvents 5.0 > TIBCO BusinessEvents Studio.
2. From the File menu select New > Project. You see the New Project — Select a Wizard dialog.
3.
4. In the Project Name field, enter the directory name where the imported project is located. (This is used as the project name.)
5. (If you imported the project to a directory in your default workspace, skip this step.) If the project directory is located outside the default workspace, uncheck the Use default location checkbox and browse to the parent directory of the project imported at the command line.
6. Click Finish. The project folders appear in the Studio Explorer view.
Copyright © TIBCO Software Inc. All Rights Reserved.