Converting the message map

After the map resources are imported, you can then convert the map to a graphical data map.

Before you begin

If you are using your own message map for this scenario, review Before: initial message map behavior.

About this task

This scenario includes tailored steps for converting the message map, and does not include all possible options and methods available. If you want to see more about the generic steps, or about all possible options and methods available, see Changes in behavior in message maps converted from legacy message maps.

If you import your messaging solutions from WebSphere® Message Broker Version 6.1 or WebSphere Message Broker Version 7.0, you can still compile and deploy message flows that use message map (.msgmap) files, provided that the message flow is built in a BAR file that has the option compile and in-line resources set. However, in WebSphere Message Broker Version 8.0 and later, message map files are accessible in read-only mode and cannot be modified by using the IBM® Integration Toolkit.

In WebSphere Message Broker Version 8.0 and later, if you want to modify mapping operations that are defined in a message map, you must first convert your message map to a graphical data map (.map) file.

When you convert a message map, message flows that reference the unconverted message map cannot be deployed until you modify each message flow to reference the new graphical data map instead.

To convert the scenario message map to a deployable graphical data map by using the IBM Integration Toolkit, complete the following steps:


  1. In the Application Development view, right-click MembersMFPFlow_Mapping.msgmap (or a .msgmap that you want to convert), and click Convert Message Map from .msgmap to .map.

    Your new graphical data map is created, and is displayed in the Application Development view. Your message map is renamed MembersMFPFlow_Mapping.msgmap_backup, and is displayed after your new graphical data map in the Application Development view.

In the Application Development view, you can see that the scenario message flow has a problem that is indicated by a red box with a cross:

MembersMFPFlow.msgflow with a red cross box indicating that there is a problem with the message flow.

You must now modify the message flow that referenced the previous message map so that the message flow instead references your new graphical data map. In this scenario, MembersMFPFlow.msgflow uses

  1. In the Application Development view, double-click MembersMFPFlow.msgflow.
    The message flow opens in the Message Flow editor.

    The message flow as displayed in the Graphical Data Mapping editor.

  2. In the Message Flow editor, identify the Mapping node from a previous version of WebSphere Message Broker.
    If you click an old Mapping node, you get a warning message box, that informs you that the node cannot find your previous message map.

    Example of information message for the step.

    You can also identify a previous version of a Mapping node by clicking it. In the Properties view, the node title includes the type as Mapping (deprecated).

    Mapping Node properties window showing the text "Mapping (deprecated)".

    The Mapping node must be replaced so that it can accept the new graphical data map.

Check the Basic tab in the Properties view of the deprecated Mapping node. The Mapping routine field contains the value MembersMFPFlow_Mapping. This value is the name of the routine for the map, that is required for the new Mapping node.

  1. In the Palette, expand the Transformation section, then drag a new Mapping node from the Palette to the canvas of the Message Flow Editor.
    A new Mapping node is added to your message flow, and is assigned a default name. If you rename the node, the name that you choose must be unique in the message flow.
    Note: If you do not change the default name now, you can change it later by using the name field in the Description tab.
  2. Select your new Mapping node.
    The node properties are displayed in the Properties view.
  3. In the Properties view, the Mapping routine property contains a default value, which must be replaced. Click Browse... to locate it, or specify your .map file in the format {BrokerSchemaName}:MapName.

    {default} indicates that no broker or integration node schema is used by the graphical data map. There is no schema for the scenario, and so {default} is shown.

    For the scenario, replace the MapName value with MembersMFPFlow_Mapping.

    Mapping Node properties with the value from the steps added to the Mapping routine field.

  4. Move the existing connections from your previous Mapping node to your new Mapping node. Drag the connectors by using the mouse.
    You can also use the Terminal Selection dialog box to move the connections, but this usage is not covered in this scenario; for more information, see Creating node connections with the Terminal Selection dialog box.
  5. Select your previous Mapping node, and press the delete key (del) to remove it from your message flow.
  6. You have replaced the Mapping node and updated the message flow to reference the new graphical data map. Save your changes.


The message map is converted to a graphical data map that can be modified by using the Graphical Data Mapping editor, and MembersMFPFlow.msgflow accepts the new map, as shown in the following image:

MembersMFPFlow.msgflow no longer displaying a red cross box.

What to do next

After you convert a message map, open and check the map for any warnings or errors on transforms. In this scenario, you must configure the transforms to resolve errors and warnings. Next, follow the tasks for Configuring the converted transforms