Migrating Projects from Earlier Versions
Read this chapter carefully and follow all migration steps that apply to your case.
For non-project related actions required for various situations, see Post Installation Tasks .
Migration of add-on products is also included, so that all migration information is available in one place.
Many of the actions you must take to migrate projects to the current release depend on the version you are migrating from, and the features you use. Some manual steps are required. More manual steps are required for earlier versions than for 4.x projects due to the changes in architecture.
Read the rest of this section and then check the section for the release from which you are migrating:
- If you are upgrading from 5.0 to 5.1, the CDD model needs to be refreshed. See Migration from 5.0 to 5.1 for details.
- If you are upgrading from 4.0, first upgrade to 4.0.1 and then migrate to 5.1. See Migration of 4.x Projects, and referenced sections.
- If you are upgrading from 3.x, you can migrate directly to 5.0 and then to 5.1. Follow the manual steps as required. See Migration of 3.x Projects, and referenced sections.
- If you are upgrading from a version earlier than 3.0, first upgrade to the latest 3.x version, following directions in the 3.x documentation.
- Migrating from Coherence to TIBCO BusinessEvents DataGrid Cache Provider
TIBCO DataGrid cache provider feature replaces Coherence as the built-in cache provider in version 5.0.0. A set of core Coherence functions has been renamed (and additional internal changes have been made) so that these functions can be used with either the Coherence or the TIBCO BusinessEvents DataGrid cache provider. The renamed functions are in the Standard catalog Cluster.DataGrid category. - Fixing Errors Due to Use of Words in Reserved Word List
- Migrating with Berkeley DB Object Management
Berkeley DB OM, formerly called Persistence OM, is an older form of data persistence. Support for this option is removed in version 5.1. - Migration from 5.0 to 5.1
- Migration from 4.x to 5.1
- Migration of 4.x Projects
This section outlines how to migrate 4.x projects, after you install TIBCO BusinessEvents 5.2. - Migration of 3.x Projects
This section outlines how to migrate 3.x projects, after you install TIBCO BusinessEvents 5.5. - CDD File Overview (For 3.x Users)
Beginning with the 4.0.0 release, most runtime properties and other deploy-time settings are configured using a structured XML file called the Cluster Deployment Descriptor (CDD). A big advantage of this change is that 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). - Importing a 3.x TIBCO Designer Project
You can directly import 3.x projects using the TIBCO BusinessEvents Studio user interface and save it as a current version project. You can also import a 3.x project at the command line. Import from versions earlier than 3.x is not supported. - Clean and Validate 3.x Projects
This section explains how to clean and validate a 3.x project, and how to fix errors. - Oracle Types to JDBC Backing Store Migration
Copyright © TIBCO Software Inc. All rights reserved.