To complete the conversion of an export or an import and
its binding, you must replace the Passthrough nodes for transport-specific IBM® Integration Bus message flow nodes, configure the message domain
to specify the data parser that you want to use, and manually implement
the function selector and the fault handling.
About this task
In IBM Integration Bus, you use
a message flow node to recreate an export or an
import and its binding. To specify the parser that you want to use
to serialize or deserialize your data, you configure the Message Domain property. To handle faults, you connect
the Fault terminal of a node and implement its logic. For exports only, you must manually implement
the function selector when the WebSphere® Enterprise Service
Bus mediation module is converted into an application.
Procedure
To finalize the conversion of an export or an import
that is referenced by a WebSphere Enterprise Service
Bus Callout mediation primitive, together with its binding, complete
the following steps:
- In the Review results view, double-click
the following to-do message: Manually convert the binding that
has the following implementation class: ''{0}''.
The Message Flow editor opens the message flow to show the placeholders created
for your WebSphere Enterprise Service
Bus mediation module
exports and imports.
- Identify the Passthrough nodes for your export
or import.
The Passthrough nodes are named after your mediation
module export or import. In the case of an export placeholder node that represent the response
in a request-response operation, the placeholder node ends with _Reply.
-
Identify the message flow
nodes that you must use in IBM Integration Bus
to recreate the export or the import binding configuration. For more information about IBM Integration Bus
message flow
nodes, see Built-in nodes.
- For an export with an interface that defines one or more one-way operations, you must
identify one Input
message flow
node. For example, if the transport associated with the export in
WebSphere Enterprise Service
Bus is of type MQ Binding, then you use an MQInput
node to recreate the export.
- For an export with an interface that defines at least one request-response operation, you
must identify one Input
message flow
node and one reply message flow
node. For example, if the transport associated with the export in
WebSphere Enterprise Service
Bus is of type MQ Binding, then you use an MQInput
node and an MQReply
node to recreate the export.
- For an import that defines a synchronous interaction, you must identify one message flow
node to handle the synchronous request and response interaction.
For example, if the transport associated with the import in WebSphere Enterprise Service
Bus
is of type HTTP Binding, then you use an HTTPRequest
node to recreate the import.
- For an import that defines an asynchronous interaction, you must identify one message flow
node to handle the request asynchronously, and one message flow
node to handle the response asynchronously. For example, if the
transport associated with the import in WebSphere Enterprise Service
Bus is of type HTTP
Binding, then you use an HTTPAsyncRequest
node and an HTTPAsyncResponse
node to recreate the import.
- Drag and drop the message flow nodes that you identified
in the previous step onto the message flow, and configure them.
- For an export, complete the following steps in order:
- Drag and drop the Input node that you identified for
your export.
- Delete the Passthrough node. This node is the node that is named after your export.
- Rename your Input node: Select the node. In the Properties view, select Description. Edit the Node name property and enter the name of the export.
- Configure the message domain. In the Properties view, select
Input Message Parsing. Configure the Message domain
property by selecting a message domain. For more information, see Parsers.
- Configure other node properties.
- Drag and drop a RouteToLabel node to dynamically determine
the route that a message takes through the message flow, based on its content.
- Optional: If the export has an interface with one operation, connect
the output terminal of the Input node to the input terminal
of the RouteToLabel node.
- Optional: If the export has an interface with multiple operations,
you must implement the logic of the function selector.
- Drag and drop a JavaCompute node, or a Compute node, or a Mapping node.
- Connect the output terminal of the Input node to the input terminal of the JavaCompute node, the Compute node, or the Mapping node.
- Implement the function selector logic that is associated with
your export.
- Connect the output terminal of the JavaCompute node, the Compute node, or the Mapping node to the input terminal of the RouteToLabel node.
- If there is a Passthrough node with the name YourExportName_Reply, where YourExportName is the name of your export, drag and drop the reply node that you identified in a previous
step, and then replace the Passthrough node.
- Rename your reply node:
Select the node. In the Properties view, select Description. Edit the Node name property and enter YourExportName_Reply, where YourExportName is the name of the export.
- Configure other node properties.
- Connect the output terminal of the operation subflow to the input
terminal of the reply node.
- Implement the fault binding logic. Review the information available about the node to see how to handle errors and exceptions. For example, to learn
how to handle MQInput errors, see Handling MQInput handling
errors.
- Save your changes.
- For an import that defines a synchronous interaction, complete
the following steps in order:
- Drag and drop the node that
you identified for your import.
- Delete the Passthrough node. This node is the node that is named after your import.
- Connect your node in the
same way as the Passthrough node was connected.
- Rename your node: Select
the node. In the Properties view, select Description. Edit the Node name property and enter the name of the import.
- Configure the message domain that you want to use to parse the response message. In the
Properties view, select Response Message Parsing.
Configure the Message domain property by selecting a message domain. For more
information, see Parsers.
- Configure other node properties.
- Implement the fault binding logic. Review the information available
about the node to see how to
handle errors and exceptions.
- Save your changes.
- For an import that defines an asynchronous interaction, complete
the following steps in order:
- Drag and drop the asynchronous request node that you identified for your
import.
- Delete the Passthrough node. This node is the node that is named after your import.
- Connect the asynchronous request node in the same way as the Passthrough node was connected. You connect
the input terminal of the asynchronous request node only.
- Rename your node: Select
the node. In the Properties view, select Description. Edit the Node name property and enter the name of the import.
- Configure other node properties.
- Depending on how the asynchronous response is correlated with
the request, you can drag and drop the asynchronous response node onto the same message flow where you added the asynchronous
request node, or to a new message flow.
- If the request and response nodes are in the same message flow, IBM Integration Bus handles the correlation
of the response to the request.
- If you create a new message flow, you must implement the correlation of the request and response
manually.
- In the asynchronous response node, configure the message
domain that you want to use to parse the response message. In the Properties
view of the asynchronous response node, select
Input Message Parsing or Response
Message Parsing. Configure the Message domain property
by selecting a message domain. For more information, see Parsers.
- Configure other node properties.
- If you have one message flow to
handle the asynchronous request and response, connect the output terminal
of the asynchronous response node to the input terminal of the node to which the output terminal of the Passthrough node was connected.
- If you have different message flows to handle the asynchronous request and response, copy the part of
the message flow that was connected
to the output terminal of the Passthrough node into the new message flow. Then, implement the correlation
logic between both message flows.
- Implement the fault binding logic. Review the information available
about the node to see how to
handle errors and exceptions.
- Save your changes.
What to do next
In the Review results view, right-click the to-do task. Select Complete.