Wiring a mediation flow

Request and response flows in the Mediation Flow editor have nodes which are the end points of the flow, and mediation primitives; wires are used to connect nodes and primitives to create the flow.

In a mediation flow, primitives are wired between the nodes in sequence from left to right in the order in which they process the message.

Wiring primitives in the Mediation Flow editor

In the Mediation Flow editor, hover your mouse over the output terminal of the node or primitive. An orange box with a handle appears around the terminal, as shown here:

Output terminal of the Input node

Drag the handle from the output terminal of the source node to the input terminal of the target.

Wire Input node to Message Logger primitive

Notice that once the connection is made, the message type of the source is propagated to the target.

Message type propagated to the target node

Wiring incompatible message types

If the output terminal of the source node and input terminal of the target node use different message types, you will see the following pop-up message when attempting to wire the nodes: A connection cannot be created, because the message types are incompatible.

Incompatible message types

In this case, you will need to use an XSL Transformation primitive or Custom mediation primitive to map the input and output message types.

Tips on wiring primitives
  • Lay out the primitives on the request or response flow canvas to visualize your flow, then wire them together.
  • Ensure that you have specified the properties in the Details view of the mediation primitive.
  • To save time when setting properties, wire the primitives before you add the properties, so that editors such as the XPath Expression Builder and the XML mapping editor can build the schema view based on the message types.
  • For most mediation primitives, the mediation flow editor detects the message types and only allows you to wire primitives that have compatible message types. However for custom mediation and XSL Transformation primitives, the editor does not check message types during wiring. Specify the message type of your custom mediation primitive in the Terminals tab of the Properties view to ensure that the primitive can be wired only to primitives of a compatible type.

    To specify the message type in the Terminals tab view, select the terminal, and click Change, as shown below: Terminal properties view showing Change button..

Related tasks
Defining source and target operations
Adding mediation primitives to the flow
Building XPath expressions

Related information

Setting properties in mediation flows

Feedback
(C) Copyright IBM Corporation 2005, 2006. All Rights Reserved.