Creating a message map from a Mapping node

You can use a Mapping node to create a message map with messages as input and output objects. Data from database tables can also be used as input to the message map.

Before you begin

Before you create a message map, you must complete the following tasks:
  1. Create an application, a library, an integration service, or an Integration project, as described in the following topics:
  2. Create a message flow. For more information, see Creating a message flow.
  3. Define the message flow content that includes a Mapping node. For more information, see Defining message flow content.

Procedure

To create a graphical data mapping (.map) file from a Mapping node:

  1. In the Integration Development perspective, open your message flow.
  2. Double-click a Mapping node that does not have a message map that is associated with it, or right-click the Mapping node and click Open Map.
    The New Message Map wizard opens.
  3. On the Specify a new message map file pane, the type of message map that you want to create is selected as Message map called by a message flow node. This is a message map that can be accessed from a node.
  4. Specify the Container, Map name, and broker schema for the message map, or use the values that have been entered for you by the wizard. Click Next.

    When some message flow nodes (for example Connector nodes or any node that defines either a JSON or a DFDL message), are connected to the Mapping node, some predefined values might be automatically specified.

    If your message map is likely to be used by multiple solutions, store it in a shared library. If you are using a JSON schema model, the container must be the shared library in which your JSON schema files are stored.

  5. On the Select map inputs and outputs pane, select your input type:
    • If you want to use a DFDL, XML, or JSON schema-defined element, expand the list of available input objects, and select the input objects that you want to use as inputs to the message map.

      If necessary, use the Filter map input names field to filter what is shown in the list of available objects. Each object in the list is displayed in the form: objectname {namespace}.

    • If you want to use SOAP, BLOB, or JSON messages as input (and you have no JSON schema), expand IBM supplied message models, and select the message model type.
  6. Select your mapping output type:
    • If you want to use a DFDL, XML, or JSON schema-defined element, expand the list of available output objects, and select the output objects that you want to use as outputs for the message map.

      If necessary, use the Filter map output names field to filter what is shown in the list of available objects. Each object in the list is displayed in the form: objectname {namespace}.

    • If you want to use SOAP, BLOB, or JSON messages as input (and you have no JSON schema), expand IBM supplied message models, and select the message model type.
  7. Optional: On the Select the domain to create the output pane, specify the Output domain for the message map (if it is not the same as the output type selected in step 6).
  8. Click Finish to create the message map.

Results

The new message map is created, and the Graphical Data Mapping editor opens with the selected inputs and outputs.

A message map is created as a .map file.

In the Application Development view, the message map is displayed under a Maps category. Maps are organized by namespace.

What to do next

Edit the message map, and define transformations between the input message assembly and the output message assembly. For more information, see Editing message maps.