Converting a legacy message map that is called from an ESQL statement in a Compute node

To convert a legacy message map that is called from an ESQL CALL statement in a Compute node, you must implement your ESQL logic in a Mapping node, and call the converted legacy message map through a Submap transform.

Before you begin

Review Changes in behavior in message maps converted from legacy message maps and Considerations for mapping messages modeled in message sets.

About this task

In IBM App Connect Enterprise, a graphical data map cannot be called from ESQL statements in a Compute node. You cannot modify or deploy a legacy message map in a BAR file.

Before you can modify or deploy a legacy message map (.msgmap format), you must convert it to a message map (.map format) and modify your message flow logic.

Procedure

To convert a legacy message map that is called by an ESQL CALL statement in a Compute node, complete the following steps:

  • Replace the Compute node and the legacy message map with a new message map and Mapping node:
    1. Convert the legacy message map (.msgmap) to a new message map (.map), as described in Converting a message map from a .msgmap file to a .map file.
    2. Replace each Compute node that includes a call to the legacy message map with a Mapping node.
    3. Create a new message map for each Mapping node.
      In this message map, complete the following steps:
      1. Create a message model that defines the overall input and output data structure to the Mapping node.
      2. Define the transforms that implement equivalent logic to the ESQL routine.
      3. Replace the CALL statement with a Submap transform. For more information, see Submap.
      4. Configure the converted legacy message map as the mapping routine of the Submap transform.
  • Replace the called message map with an ESQL function that provides equivalent logic.

What to do next

Deploy and test your message flow. For more information, see Deployment rules and guidelines.