Migrating Data from Old TIBCO BusinessEvents Projects to Version 6.x

You can use the migration utility be-storedeploy to migrate data from old projects to the version 6.x. You can perform the following types of data migration:

Migrating Data from TIBCO ActiveSpaces 2.x based Clusters

To migrate data from TIBCO ActiveSpaces 2.x (Legacy ActiveSpaces) clusters to newly supported store and cluster providers in TIBCO BusinessEvents, you can use the migration utility. TIBCO BusinessEvents still supports the old store and cluster providers and you do not need to migrate data to continue using them. The minimum supported versions for data migration to new stores are ActiveSpaces version 2.3 and above, and TIBCO BusinessEvents version 5.5.0 and above.

The following table shows the supported data migration paths:

TIBCO BusinessEvents version 5.x configuration TIBCO BusinessEvents version 6.x configuration
Legacy ActiveSpaces - Shared Nothing Apache Ignite - Shared Nothing
Legacy ActiveSpaces - Shared Nothing TIBCO ActiveSpaces store
Legacy ActiveSpaces - Shared Nothing Apache Cassandra store

Migrating Primary Keys

When you migrate a project, the data is migrated to the new ID implementation by default.

The new ID implementation sets the existing extID as the primary key in the migrated data. You can migrate the project with extId with Legacy ActiveSpaces - Shared Nothing persistence configuration to the new ID while still keeping Legacy ActiveSpaces - Shared Nothing configuration.

You can optionally continue to use Legacy Id settings while migrating a project.

For details, see Enabling the Legacy Lookup Strategy.

Before you begin Download and install TIBCO ActiveSpaces, Apache Cassandra, and TIBCO FTL as required by the project configuration. For details about the installation and configurations, see their respective documentation.
    Procedure
  1. Set the following environment variables in the be-storedeploy.tra file located at BE_HOME/bin as applicable:
    • ACTIVESPACES_HOME based on the new project configuration
    • FTL_HOME based on your project requirement
  2. Import the old project to the TIBCO BusinessEvents Studio. For more information, see Importing Projects in TIBCO BusinessEvents Studio.

  3. Configure the backing store or the Shared Nothing persistence as required. For more information, refer one of the topics below:

    Persistence Option Reference
    TIBCO ActiveSpaces as backing store Configuring ActiveSpaces as a Store Provider
    Apache Cassandra as backing store Configuring Apache Cassandra as a Store Provider
    Apache Ignite for Shared Nothing persistence Configuring Apache Ignite as a Cache Provider
  4. Build an EAR file for the project. For more information, see Build an EAR File.
  5. Start the cache agents for your old TIBCO BusinessEvents project. For details on starting the agents, see the TIBCO BusinessEvents Administration guide.

  6. Run the be-storedeploy data migration utility.

    For a detailed process, see Generating Deployment Scripts for a Store.

    For projects with no cache no cluster configurations, run the migration utility with default processing unit. For details about the be-storedeploy utility options, see Store Deployment CLI Utility Options.