Importing Projects with Legacy ID Lookup

To migrate projects with the legacy ID lookup implementation, perform the following tasks:

    Procedure

  1. To continue using legacy ID-based lookup when migrating existing projects into TIBCO BusinessEvents version 6.x workspace, you must first setup the environment in the BE_HOME for a project. For a detailed process, see Enabling the Legacy Lookup Strategy.

  2. Import an existing project into TIBCO BusinessEvents version 6.x workspace using the existing TIBCO BusinessEvents Studio project import utility option.

    For a detailed process, see Importing Projects in TIBCO BusinessEvents Studio.

    Alternatively, you can also use a command-line utility studio-tools to import an existing project into TIBCO BusinessEvents version 6.x workspace. After successfully running the utility, open the project in the TIBCO BusinessEvents Studio version 6.x.

    For a detailed process, see Importing an Existing Project from the CLI.

  3. If the TIBCO BusinessEvents 5.x project has modified Object Management configurations to use Apache Ignite or TIBCO FTL clustering with either ActiveSpaces 4.x Store or Apache Ignite Cache with or without persistence, make the corresponding changes in the project CDD file.
  4. If the TIBCO BusinessEvents 5.x project has used StudioUtil.buildClasses and StudioUtil.buildEar catalog functions then you must update project to remove useLegacyCompiler boolean parameter from these functions.
  5. Rebuild the project EAR using the TIBCO BusinessEvents Studio 6.x.

    For a detailed process, see Compiling Project and Building an EAR File.