See information about the latest product version
Converting a message map from a .msgmap file to a .map file
You must convert a message map from a previous version of IBM® Integration Bus to a graphical data map before you can modify it by using the Graphical Data Mapping editor.
Before you convert a legacy message map, complete the following steps:
- 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. Alternatively, you can migrate the WebSphere Message Broker Version 6.1 or WebSphere Message Broker Version 7 Toolkit development resources. For more information, see Migrating development resources to WebSphere Message Broker Toolkit Version 8.0.
- Verify that all the projects that include resources used by the legacy message map are available in your workspace, and the project dependencies are defined.
- 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, if you want to modify mapping operations that are defined in a legacy message map, you must first convert your map to a graphical data map (.map file). A graphical data map is known as a message map in IBM Integration Bus.
To use a converted legacy message map in your message flows, you must replace legacy Mapping nodes with new Mapping nodes. For more information, see Replacing a WebSphere Message Broker Version 7 Mapping node.
To convert a legacy message map to a message map by using the IBM Integration Toolkit, complete the following steps:
Your message map is converted to a message map that can be modified by using the Graphical Data Mapping editor.
Modify each message flow that references the legacy message map so that new Mapping nodes reference your new message map. For more information, see Replacing a WebSphere Message Broker Version 7 Mapping node.