Message Image  

Converting a message map from WebSphere Message Broker v7 to a graphical data map in WebSphere Message Broker v8 or IBM Integration Bus

 View Only
Tue June 02, 2020 09:28 AM

You can compile and deploy legacy message maps in WebSphere Message Broker Version 8 and IBM Integration Bus. However, if you need to modify any of these resources, you must convert them into message maps (that is, graphical data maps) that the new Mapping node consumes.

This article helps you plan and convert legacy message maps.


In WebSphere Message Broker v8 and IBM Integration Bus, you can transform data graphically:

  • You use a Mapping node in a message flow to model a step in your integration solution that requires data transformation.
  • A Mapping node uses a graphical data map, known as a message map, to define all your data transformations.
  • You define your transformation logic by using XPath 2.0 expressions. You can also call Java methods, ESQL procedures, or complex XPath expressions by using specialized transforms such as the Custom Java, Custom XPath, or Custom ESQL transforms.  
  • You use the Graphical Data Mapping editor to create and edit message maps.

When you upgrade an integration solution, that includes data transformations done in a Mapping node, from WebSphere Message Broker v7 to WebSphere Message Broker v8 or IBM Integration Bus, consider the following behavior:

  • You can import message flows that use message maps. These maps are referred as legacy maps in this document.
  • You can continue to view and deploy legacy message maps, but you cannot modify them.
  • You can compile and deploy message flows that use legacy message maps.

The BAR file that you use to deploy the solution must have the option Compile and in-line resources set. This setting might be incompatible with some other functions, such as deployable subflows that require deploy as source mode.

Legacy message map

A legacy message map is a message map created as a .msgmap file in earlier versions of WebSphere Message Broker v8, for example in WebSphere Message Broker Version 7.

Note: From WebSphere Message Broker Version 8 onwards, legacy message maps are accessible in read-only mode and cannot be modified by using the IBM Integration Toolkit.

When to convert a legacy message map?

Convert a legacy message map when you want to:

  • Modify an existing transformation in a legacy message map.
  • Add a condition on a transform in a legacy message map.
  • Add additional transformations.
  • Change the legacy message map transformation logic

More detailed information in IBM Knowledge Center

For more information to help you plan and perform the conversion of legacy message maps, see the IBM Integration Bus product documentation in IBM Knowledge Center; in particular: