Using or converting legacy resources into message maps

If you want to deploy legacy message maps (.msgmap format) in IBM® App Connect Enterprise, you must first convert them into message maps in .map format, which the IBM App Connect Enterprise Mapping node can consume.

About this task

Legacy message maps cannot be deployed in IBM App Connect Enterprise until they have been converted.

A legacy message map is a message map that was created as a .msgmap file in WebSphere® Message Broker Version 7 or earlier.

The functions provided by the following legacy message flow nodes in WebSphere Message Broker Version 7 (and earlier versions) were replaced with the new Mapping node in later versions of WebSphere Message Broker and IBM Integration Bus:
  • DataDelete node
  • DataInsert node
  • DataUpdate node
  • Extract node
  • Mapping node
  • Warehouse node

Procedure

Follow these guidelines when you use legacy message maps and legacy message flow nodes in your integration solutions:

  • IBM App Connect Enterprise does not support WebSphere Message Broker Version 7.0 legacy message maps (.msgmap). You can import message flows that contain legacy message maps into the IBM App Connect Enterprise Toolkit. However, you can view these message flows in read-only mode only, and you cannot deploy and run them. If you try to deploy a BAR file that contains a legacy message map, you see a BIP2355 error message. Before you run a message flow that contains a legacy message map or a legacy Mapping node, you must convert them by following the instructions in Using or converting legacy resources into message maps.
  • You must change the transformation logic in your integration solution when a legacy message map is invoked from an ESQL CALL statement. For more information, see Converting a legacy message map that is called from an ESQL statement in a Compute node.

    A message map cannot be called from an ESQL CALL statement.