This is a walkthrough for assisting customers to seamlessly migrate from BusinessEvents 5.x to 6.x version. 

This walkthrough provides a migration strategy to existing users to upgrade from BusinessEvents (BE) 5.x to 6.x version.

The goal of this walkthrough is to assist users for a seamless migration to BusinessEvents 6.x.&nbsp;

Migration to BusinessEvents 6.x is a two step approach.&nbsp;

Both these topics are covered in detail in the next steps.

Changes in Functionality with BusinessEvents 6.x

Introduction

Once BE 6.x is installed (use the latest BE 6.x version), any projects that are created with the BE 5.x (or earlier) version need to be imported into the BE 6.x BusinessEvents Studio to begin the Project Migration process.&nbsp; We recommend importing a BE 5.x project into the BE 6.x BusinessEvents Studio environment and rebuilding archives.&nbsp; 

Below section describes the Project Migration using the NewId(obj @id) as well as LegacyId (long @id).

When a project from BE 5.x is migrated to BE 6.1.1 or higher versions, the project will be migrated to the NewId (Key-based Lookup) implementation by default. (BE 6.0.0 and 6.1.0 versions have the Legacy Lookup as the default lookup implementation). 

The below table lists the functions that are no longer supported with BE 6.x under the new key-based lookup and their equivalent functions that need to be used. These BE 5.x functions will work as-is with the Legacy Lookup with BE 6.x. LegacyId/Legacy Lookup strategy will be deprecated in the future. It is strongly recommended to modify the existing project implementation to adopt the key-based lookup capability for improved BE engine performance.&nbsp;

Details for Migration using the new key-based entity lookup is provided in the BusinessEvents Administrator Guide (link below) under the Migration of TIBCO BusinessEvents 5.x Projects section. (Page 15) 

The entity lookup strategy (from TIBCO BE versions 4.x and 5.x) in which an entity instance can be fetched or loaded into working memory by specifying its LongId(@id) or the extId with or without specifying the URI is referred to as the legacy lookup strategy. By default, with BE 6.1.1 and higher versions, the legacy lookup strategy is disabled. 

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;* Remove&nbsp; # (or uncomment) the below mentioned properties under the section&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<code class="inline-code">Uncomment below properties to change to Legacy ID mode</code>&nbsp;in studio.tra&nbsp;file located at -&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<code class="inline-code">BE_HOME/bin/studio/eclipse/configuration </code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # be.engine.id.useLegacy=true &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;# TIBCO.BE.function.catalog.getbykeys=false

&nbsp; &nbsp; &nbsp; &nbsp; * For Runtime: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Add the property <code class="inline-code">be.engine.id.useLegacy=true</code> in the project CDD file at the &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;cluster level or in&nbsp;<code class="inline-code">BE_HOME/bin/be-engine.tra</code> file.

&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp;For JDBC deployment (create SQL scripts):&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Add property <code class="inline-code">be.engine.id.useLegacy=true</code> in&nbsp;<code class="inline-code">BE_HOME/bin/be-storedeploy.tra</code> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;file before creating the SQL scripts&nbsp;in Studio or with the&nbsp;<code class="inline-code">be-storedeploy</code> utility on &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;command line. &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;*&nbsp;Restart BE 6.x BusinessEvents Studio.

Refer to the documentation for more details on enabling the LegacyId based lookup. 

Project Migration

This section describes the migration of project data from BE 5.x to 6.x version.

Data Migration from BE 5.x to 6.x version

The below table summarizes the possible options and the steps for Data Migration for the Legacy and (NewId) Key-based lookup implementation.