Convert a WebSphere® Enterprise Service
Bus service
that is implemented with a mediation flow component into message flows and subflows.
About this task
In IBM® Integration Bus, you implement a message flow per converted mediation flow component. You implement a subflow per converted operation. For more
information, see Message flows
overview and Subflows.
In WebSphere Enterprise Service
Bus, a mediation flow component provides
a service that is implemented with mediation flows. There is one mediation
flow per source operation. A mediation flow consists
of a sequence of processing steps that are run when an input message
is received. Mediation primitives define the processing
steps. A mediation flow has a request flow. This request flow is where
you define the flow of the outgoing message from the source operation.
A mediation flow can call a target operation at the end of a request
flow by using a callout mediation primitive, or inline within the
flow by using the service invoke mediation primitive.
Procedure
Follow these steps to manually convert a WebSphere Enterprise Service
Bus service that is implemented
with mediation flow components:
-
Implement each service source operation as a subflow. For more information, see Subflows.
-
Use a message flow input node, and optionally a reply node for
request-response operations, in place of a mediation module export and its corresponding binding
type. For more information, see Input nodes and MQReply
node.
-
Use a message flow output Node, and optionally a request node or an
asynchronous request node and an asynchronous response node for request-response operations, in
place of a mediation module import and its corresponding binding type. For more information, see
Output nodes and Request nodes.
-
Specify a message domain in an input or output node to define the parser that is applied to
data by a message flow. (In WebSphere Enterprise Service
Bus, you
specify a Data Handler or a Data Binding on an export or import to define how data format
transformation happens.) For more information, see Message domains and parsers.
-
Define the properties a message flow has. Message flow properties are used to affect the behavior of the message flow, and are defined by promoting message flow node properties. For more information, see Properties and Promoted properties.
- If you implement a WebSphere Enterprise Service
Bus service
as an IBM Integration Bus application:
- Build the function selector logic in your message flow application if your service
defines multiple operations and the binding type is a non-SOAP binding.
When the binding is SOAP, the SOAP input node includes the logic
to identify the operation requested based on message information.
- Build the fault selector that is associated with an import
if the interface includes multiple faults. This fault selector applies
for non-SOAP bindings.