Enabling the Key-Based Lookup Strategy

For backward compatibility, by default, the key-based lookup strategy is disabled and only the legacy lookup strategy is used.

    Procedure

  1. Edit and add the following properties in the TRA files:

    Store Lookup Strategy Properties
    TRA File Property
    BE_HOME/bin/be-engine.tra java.property.be.engine.id.useLegacy=false
    BE_HOME/bin/be-storedeploy.tra

    java.property.be.engine.id.useLegacy=false
    BE_HOME/studio/

    eclipse/configuration/studio.tra

    be.engine.id.useLegacy=false

  2. (Optional) While using key-based lookup strategy to load concept using external key or composite key, enable the following property in the TRA file,

    Key-based Lookup Strategy Properties
    TRA File Property

    BE_HOME/studio/eclipse /configuration/studio.tra

    TIBCO.BE.function.catalog.getbykeys=true
  3. Save the TRA files and restart TIBCO BusinessEvents Studio.
Result
  • The Cluster.DataGrid.*ByExtId catalog functions are not available for use. You can use Cluster.DataGrid.*ByUri functions instead. Also, the Instance.getByIdByUri catalog function is not available.
  • The object table is not used for store or cache lookups. Thus, in the CDD editor, the Preload Handles setting (Cluster > Object Management > Domain Objects > Overrides) is also not available.
  • If you have enabled the key-based lookup strategy (Step 2), the following settings are now available to use:
    • The Cluster.DataGrid.CacheLoadConceptByKeysByUri() and Instance.getByKeysByUri catalog function to load concepts using composite keys.
    • The Present in Key column under Properties Metadata section of the entities override (Cluster > Object Management > Domain Objects > Overrides) settings in the CDD editor.