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.
Review Changes in behavior in message maps converted from legacy message maps and Considerations for mapping messages modeled in message sets.
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.
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:
Deploy and test your message flow. For more information, see Deploying resources.