Importing Projects from TIBCO BusinessEvents Version 5.x to 6.x

When you migrate projects from TIBCO BusinessEvents version 5.x to 6.x, there is a shift in the entity lookup strategy in cache and stores from object table-based legacy ID lookup to key-based ID lookup.

To know the detailed differences between the key-based and legacy lookup strategies, see Primary Key Strategies.

When you migrate the TIBCO BusinessEvents projects from version 5.x, the legacy lookup strategy is disabled and TIBCO BusinessEvents projects are migrated to the new ID lookup implementation by default. You might continue to use the legacy ID in the migrated projects (in select cases) with some configurations in the project. However, using the legacy ID lookup strategy is discouraged.

Tip: It is advisable to modify the existing project implementation to adopt the key-based lookup capability for improved TIBCO BusinessEvents Enterprise Edition engine performance and better compatibility with modern stores.
Note:
  • Opening an existing workspace containing TIBCO BusinessEvents 5.x projects in TIBCO BusinessEvents Studio of version 6.x migrates the projects to TIBCO BusinessEvents version 6.x automatically.
  • As part of the project migration, the .beproject file is deleted. The information in the .beproject file is transferred to their corresponding sections in the pom.xml.