WebSphere

Protocol conversion

Connect service endpoints that use different protocols.

About this task

If your goal is to connect endpoints that use different protocols you can achieve this by creating mediation modules that convert between different protocols. For example, if you want to connect Web services using SOAP/HTTP to Java™ Message Service (JMS) applications.
Figure 1. Actor (service requester) and system (ESB)
Messages can be converted from one protocol to another using a mediation module
To connect endpoints that use different protocols complete the following steps.
Note: these steps provide an overview, they do not include all instructions for creating a complete mediation module. For complete instructions on how to construct a mediation module refer to the WebSphere® Integration Developer documentation.
Procedure
  1. The integration developer creates and exports a mediation module by completing the following steps.
    1. Create and configure a mediation module. Use WebSphere Integration Developer to create a mediation module. Click this link to go to the topic for WebSphere Integration Developer.
    2. Create an export with a binding appropriate to the service requester. If the service requester is a Web service, the binding can be a Web service binding, (using SOAP/HTTP or SOAP/JMS), or an HTTP binding. Click this link to go to the topic for WebSphere Integration Developer.
    3. Create an import with a binding appropriate to the service provider. If the service provider is a JMS application, the binding should be a JMS binding. The run time supports different types of JMS bindings in order to support different JMS providers. Click this link to go to the topic for WebSphere Integration Developer.
    4. Wire the mediation module. If two services have the same interface, and no mediations are required, you can wire the export directly to the import. If two services have different interfaces, or you need to mediate the message, a mediation flow component is needed to do the transformations. Click this link to go to the topic for WebSphere Integration Developer.
    5. Export the mediation module. From WebSphere Integration Developer export the mediation module as an EAR file. Click this link to go to the topic for WebSphere Integration Developer.
  2. The runtime administrator deploys and administers the mediation module by completing the following steps.
    1. Deploy the mediation module. Use the runtime administrative console to install the EAR file as a new application. Click this link to go to the topic for WebSphere ESB. Click this link to go to the topic for WebSphere ESB for z/OS. Click this link to go to the topic for WebSphere Process Server. Click this link to go to the topic for WebSphere Process Server for z/OS.
    2. Start the application associated with the mediation module. Use the runtime administrative console to start the application associated with the SCA module (mediation modules are types of SCA modules). Click this link to go to the topic for WebSphere ESB. Click this link to go to the topic for WebSphere ESB for z/OS. Click this link to go to the topic for WebSphere Process Server. Click this link to go to the topic for WebSphere Process Server for z/OS.

Results

When a service request invokes your mediation module then messages are converted from one protocol to another by the run time.

Example

Figure 2. Message protocol conversion using a mediation module
Web service message, using SOAP/HTTP, is converted to JMS message

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 20 June 2010 00:38:51 BST (DRAFT)


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wbpm.scenarios.esb1.620.doc/tasks/twesb_usecaseprotocolconversion1.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).
iDoc on