Using the TX Map node with a precompiled map and a single input

Develop a message flow with a TX Map node specified with a precompiled map, that, at run time, is triggered to run by a single input.

The map could have many input cards. Only one nominated card receives data from the message flow, while each of the other cards pull data directly from their adapter.

The map could have many output cards. Cards that are connected to the message flow propagate data to the flow, while each of the unconnected cards send data directly to their adapter.

To develop a simple message flow that demonstrates this scenario, do the following steps. They are based on the assumption that you used Map Designer to create a source map (.mms) file, containing an executable map with one or more input cards, and one or more output cards, and that you compiled the map for a target platform, creating a compiled map (.mmc) file.

  1. Create a new message flow project in the IBM® Integration Development perspective.
  2. Create a new message flow in the project. Select Use default broker schema, or provide your own schema name to qualify the message flow name.
  3. Drag a TX Map node, from the palette onto the canvas for your message flow.
    The node initially has no output terminals and one failure terminal.
  4. Navigate to the Properties view.
  5. On the Basic tab of the TX Map node, select the precompiled map.
  6. On the Input tab of the TX Map node, select the map card that receives the input.
  7. Drag an input node, for example, a FileInput node or MQInput node, to the canvas, and connect the out terminal of the input node to the in terminal of the TX Map node.
    The message from the input node overrides the adapter of the map’s selected input card.
  8. Configure the input node with the necessary transport-related properties.
  9. On the Input Message Parsing tab of the input node, configure the message template properties to describe the format of the input message. Select the domain from the list of supported message domains.
  10. Drag an output node, for example, a FileOutput node or MQOutput node, to the canvas, and connect one of the output terminals of the TX Map node to the in terminal of the output node.
    Connecting the output terminal overrides the adapter of the corresponding output card.
  11. Configure the output node with the necessary transport-related properties.
  12. On the Outputs tab of the TX Map node, configure properties to describe the format of the output message propagated by the output card.
    1. Click Add to add a set of properties.
      The Add Properties entry dialog appears.
    2. Enter values for Card Number, Message Domain, Message Set, and Message Type, and click OK.
      Message Domain must be one of the supported message domains.
  13. Repeat steps 10 through 12 for each output terminal that you want to connect.
  14. Press Ctrl+S to save the message flow.
Manually create and build the broker archive (bar) file, and then deploy it to the broker. You must also manually deploy the compiled map (.mmc) file to the broker's file system.
When the message flow runs, the message from the input node is passed to the TX Map node, and the TX Map node runs the map. The message overrides the adapter specified on the selected input card. For example, if the input card uses the File adapter, the map does not read from the file; it uses the message from the message flow. Connected output terminals override the adapters of the corresponding output cards. For example, if an output card uses the File adapter, the map does not write to the file; it propagates the message to the message flow.