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 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:

Migrating Primary Keys

While migrating the projects, you can optionally use the new ID implementation introduced in TIBCO BusinessEvents version 6.0.0. This sets the existing extID as the primary key in the migrated data.

You can migrate projects with extId with TIBCO ActiveSpaces 2.x - Shared Nothing persistence configuration to the new ID while still keeping ActiveSpaces 2.x - Shared Nothing configuration.

Procedure
1. (Only for migrating projects to use new Id) Set properties as follows:
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.
   • Set the java.property.be.engine.id.useLegacy property to false.
2. Open the be-engine.tra file at the location BE_HOME/bin and set the java.property.be.engine.id.useLegacy property to false.
3. Open the studio.tra file at the location BE_HOME/bin/studio/eclipse/configuration and set the java.property.be.engine.id.useLegacy property to false.
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 theTIBCO BusinessEvents Administration guide.

6. Run the data migration 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 <custom property file of the project> -u <processing unit name> -op migration -c <path to CDD file of the project> <path to EAR file of the project> -n <engine name> -discovery <source discovery URL for migrating ActiveSpaces 2.x projects to ActiveSpaces 2.x projects with new Id> -listen <destination listen URL for migrating ActiveSpaces 2.x projects to ActiveSpaces 2.x projects with new Id> -cname <source cluster name for migrating ActiveSpaces 2.x projects to ActiveSpaces 2.x projects with new Id> 

      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.