IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

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:

  1. 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 IBM Integration Toolkit Version 9.0.
  2. 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.
  3. 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.

Note: The conversion process is not reversible. However, you can run the conversion of a legacy message map multiple times. You must rename the converted legacy message map by removing _backup from the converted map name.

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:

  1. Start the conversion process: In the Application Development view, right-click the message map that you want to convert, and click Convert Message Map from .msgmap to .map.

    To covert multiple legacy message maps, right-click a folder, project, application, or library that contains one or more maps, and click Convert Message Map from .msgmap to .map.

    • Your converted message map is created, and is displayed in the Application Development view.
    • Your legacy message map is renamed MessageMapName.msgmap_backup, and is displayed in the Application Development view.
  2. Open the converted map in the Graphical Data Mapping editor: In the Application Development view, double-click your new message map.

    The message map opens in the Graphical Data Mapping editor.

  3. Review the transformation logic that was created by the conversion process to ensure that it produces the correct output for your application.
    1. Review and replace each Task transform. For more information, see Managing conversion errors on converted legacy message maps.

      If your legacy message map contains complex mapping structures that the conversion process was not able to re-create, your message map includes Task transforms to assist you in manually re-creating those structures.

      Task transforms are listed in the Problems view.

    2. Review all the conversion annotation icons () that are associated to transforms in your map. For more information, see Managing conversion warnings on converted legacy message maps.

      Conversion annotation icons are displayed on the lower left of the transform in the Graphical Data Mapping editor.

      Note: You can accept or reject all the transforms in a converted map in one single click.

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.

br40806_.htm | Last updated Friday, 21 July 2017