Enabling the Legacy Lookup Strategy

The legacy lookup strategy is the entity lookup strategy from TIBCO BusinessEvents version 5.x where an entity instance can be fetched or loaded into working memory by specifying its Long ID or extId with or without specifying its URI.

In TIBCO BusinessEvents version 6.3.0, the legacy lookup strategy is disabled and the migrated projects use the new ID (Key-based Lookup) implementation by default. To continue using the legacy ID in the migrated TIBCO BusinessEvents projects, follow the process:

    Procedure
  1. To use the legacy ID mode, set the following properties:
    PropertyLocationAction
    be.engine.id.useLegacy

     

    studio.tra file
    located at
    BE_HOME/bin/studio/eclipse/configuration/

    		Set the property to true.
    The property already exists in the studio.tra file in the commented out form.

    be-engine.tra file
    located at BE_HOME/bin/

    or project CDD file at the cluster level

    		 For runtime configuration, add the property and set it to true.

    be-storedeploy.tra file
    located at BE_HOME/bin/

    or project CDD file at the cluster level

    For JDBC deployment, before creating the SQL scripts in Studio or with the be-storedeploy utility on command line, add the property and set it to true.

    TIBCO.BE.function.
    catalog.getbykeys

    studio.tra file
    located at
    BE_HOME/bin/studio/eclipse/configuration/

    Set the property to false to use legacy ID.

    Note: If the the value of the Legacy Id for previous version is set to true in the pom.xml file, then it is set to true in the current version.

  2. Restart TIBCO BusinessEvents Studio.

Result
  • The Cluster.DataGrid.*ByExtId catalog function is available for use.
  • The object table is used for store or cache lookups.