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

Before you convert a legacy message map, you must complete one of the following tasks:

Import your resources from WebSphere® Message Broker Version 6.1 or WebSphere Message Broker Version 7. For more information, see Importing resources from previous versions.
Migrate the WebSphere Message Broker Version 6.1 or WebSphere Message Broker Version 7 Toolkit development resources. For more information, see Migrating development resources.

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 WebSphere Message Broker Version 8 and later versions, a message map, that is a graphical data map, cannot be called from ESQL statements in a Compute node. For compatibility with earlier releases of the product, you can still deploy and run a legacy message map in a BAR file. You must include the whole message flow to the BAR file and set the Compile and in-line resources option.

If you need to modify the logic in your legacy message map, you must convert the map to a message map 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 instructions outlined in any of the following steps:

Replace the Compute node and the legacy message map with a new message map.
1. Convert the legacy message map (.msgmap) to a message map ( .map). For more information, see 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. It might be possible to use support pac "IA9Y: Map to ESQL Plug-In" to help with the conversion of the message map to ESQL http://www.ibm.com/support/docview.wss?uid=swg24017156.

What to do next

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