![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
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).
Berkeley DB object management is removed from the product in version 5.1. If you are migrating from Berkeley DB, see For Berkeley DB Object Management Users Only for preliminary steps to take in order to change to Cache OM.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.
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.1 for details). However, only the CDD file specified here is used for HTTP channel property migration.
The default value is index.htmlBeginning 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:
• If you want to switch from Oracle Coherence to TIBCO BusinessEvents DataGrid, you must manually reconfigure the CDD file settings. See Chapter 24, Cache OM and Cluster Configuration in TIBCO BusinessEvents Developer’s Guide 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.Task G Rebuild EAR FilesThis 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.1Before 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 -core importExistingProject [-h] -p studioProjDir [-o targetProjDir] [-c CDDprojectPath] [-u PUNameFromCDD]Migrating HTTP properties of Processing Unit "PUName" from CDD "CDDprojectPath" to HTTPChannel(s) present in the projectTable 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.
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.
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 |