Powered By

Free XML Skins for Blogger

Powered by Blogger

Friday, January 9, 2009

Integrating Remote Client/Web Services by Using the SOAP Adapter

The following documentation describes how you can use the SOAP adapter to connect a remote client or Web services provider to the Integration Server. The remote client or Web services provider can perform the task of either a sender or receiver, or both.

Use

Some remote clients or Web services providers are only able to communicate by means of SOAP messages. You use the SOAP adapter to connect such systems to the Integration Server directly.

The SOAP adapter provides a runtime environment that includes various SOAP components for the processing of SOAP messages. It uses a helper class to instantiate and control these SOAP components. For more information about the SOAP adapter, see: Structure linkSOAP Adapter.

Description

A remote client or Web services provider is connected to the Integration Server by means of the SOAP adapter to exchange SOAP messages. The SOAP adapter receives a message from the remote client or Web services provider, converts the SOAP protocol into the XI message protocol (SOAP with header enhancements) and then sends the message to the Integration Server to be processed further.

To forward messages to a receiver remote client or Web services provider, the SOAP adapter receives the message from the Integration Server, converts it into a SOAP message, and then sends it to the remote client or Web services provider.

This graphic is explained in the accompanying text

Example

A remote client sends a SOAP message to the SOAP adapter on the Integration Server. The SOAP adapter converts the SOAP message to XI message protocol and transfers it to the Integration Server for further processing. Two receivers are determined:

· A remote Web services provider

· An SAP business system, which is able to receive XI message protocol directly

On the receiver side, the SOAP adapter converts the XI message protocol into a SOAP message and then sends the message to the remote Web services provider. The other receiver simply receives the XI message protocol message.

No comments:

Archives