Migrating Project Data

After you import the project, you must migrate the project data. The data migration process depends on the entity lookup strategy (new ID or legacy ID) and the persistence option implemented in the project.

For migrating the project data, following are the considerations:

  • By default, the TIBCO BusinessEvents projects are migrated to the new ID implementation.

  • You can migrate TIBCO BusinessEvents projects irrespective of the store or persistence mode.

  • The Check for Duplicates feature in an agent cluster configuration is no longer supported in new ID. It was used to check the cluster-wide duplicates across entities. If the TIBCO BusinessEvents version 5.x project has the Check for Duplicates feature enabled, then you must refactor the project to remove this dependency.

    For details about project refactoring, see Element Refactoring Operations in TIBCO BusinessEvents Developer Guide.

    Duplicate checks within entities continue to be supported.

  • You can choose between refactoring or lift-and-shift strategies to migrate project data based on the factors such as migration timeline, efforts, the complexity of use-cases, and licensing.

For possible data migration options and respective processes, see Data Migration Options.

Note: Download and install the third-party supported software (database or external data grids) used in the project to the versions supported with TIBCO BusinessEvents version 6.x. For details about the installation and configurations for third-party software, see their respective documentation.

For details about the supported versions, see the Readme.txt file available at the TIBCO BusinessEvents® Enterprise Edition Product Documentation page.