Converting a WebSphere Enterprise Service Bus service implementation manually

Follow these steps to manually convert a WebSphere Enterprise Service Bus service that is implemented with mediation flow components:

1. Implement each service source operation as a subflow. For more information, see Subflows.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.