Migrating Data from Legacy ActiveSpaces based Clusters

To migrate data from 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
For old projects with Shared All persistence configurations, the same database schema can be used for new cache providers. For this migration path, you do not need to use the migration utility.
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. Open the be-storedeploy.tra file at the location BE_HOME/bin and set the appropriate environment variable.

    • (Optional) Set the environment variable ACTIVESPACES_HOME based on the new project configuration.
    • (Optional) Set the environment variable 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. If the new project is configured with a backing store (ActiveSpaces or Apache Cassandra), ensure that the required schemas are setup in the corresponding backing store.

    For more information, see Generating Deployment Scripts for a Store.

  7. To generate the migration script, run the store deployment script generation utility using the following steps:

    1. Open a command window and navigate to <BE_Home>/bin.

    2. Use the following command to run the migration utility be-storedeploy:

      be-storedeploy -p <property file of the project> -u <processing unit name> -op migration -c <path to CDD file of the project> -n <engine name>

      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.