Showing results for 
Search instead for 
Did you mean: 

help in SOAP to SOAP scenario

Former Member
0 Kudos


can anyone give me a clear idea or if u already have any blogs which will give me a detailed information about a Soap to soap scenario and how will it be possible to handle errors. help me out in understanding a SOAP scenario.

reward points if useful



Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos


Receiver SOAP Adapter

The receiver SOAP adapter connects XI with an external Web service. To call the Web

service, you need to define a message interface that represents the structure of the

request and response of the Web service. You can create this message interface easily

with the help of a WSDL file that represents the Web service. If this is not possible, you must create the message interface based on data types.

Uploading the WSDL

Since the WSDL describes the message interface, you upload the WSDL into the

Integration Repository. Go to your Software Component Version and open the required

Namespace. Create an External Definition.

In the external definition object, choose Category wsdl and click Import external

definitions.After importing the WSDL file, you can view the included messages on the Messages tab page:

The namespaces of the messages are part of the WSDL description and can

differ from the namespace of the external definition object.

Now you can create a message interface corresponding to the message types from the external definition. You need the message interface for routing the message to the Web service.

In the message interface object, select the message types of the external definition

object by using the input help.

After assigning the output and input message, save and activate your work. Now you can use the message interface for routing and mapping.

Creating a Message Interface Without WSDL

For some scenarios it is not possible to provide a WSDL file. In this case you need to create a message interface according to the message structure of the server. The best way to achieve this is by using an example SOAP message for the request and the response message.

Since the SOAP adapter creates the SOAP envelope you have to extract the SOAP

body. Usually, Web services ignore declarative attributes (xsi:type), therefore you can delete them. The namespace declaration of the root tag must be applied. The XI

message payload should be the following message.

Create a data type, message type, and message interface according to this structure. In the message type, apply the correct name and namespace of the message.

Creating a SOAP Receiver Channel

To call the Web service, you create a communication channel with type SOAP and

direction receiver in the Integration Directory. The obligatory parameters in the

configuration are Target URL and SOAP action. You get the values you have to enter

here from the WSDL file.

You find the target URL at the tag soap:address and the SOAP action at the tag


If more than one message type is described in the WSDL, several SOAP actions

might also be defined. Check for the correct operation name. If no SOAP action is

defined in the WSDL, you can leave the parameter in the receiver channel empty.

For the receiver SOAP adapter you need at least the following parameters.

If the Web service is outside your system landscape and you need to address a proxy server, select the Configure Proxy checkbox and fill in the corresponding fields.

soap to soap scenario


sap to webservice


This might help you to get more picture on SOAP

Check these


/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2 [original link is broken] [original link is broken] [original link is broken]

For more details on SOAP..



Former Member
0 Kudos


First go thru this pdf...

soap to soap scenario


And then...

soap to soap scenario,

1. Select any Web Service from Net. Open WSDL source code. Save that file.test this web service in a SOAP Tester.

Sample web services:

2. Import wsdl in external definition of your Integration repository.

3.Design n Configure all objects.

4. sender channel & receiver channel : soap

Receiver Channel SOAP

1. In receiver SOAP channel Specify The URL of Web service provider.

2. Leave username and pwd blank.

3. Mention SOAP Action. Which is available in wsdl file .search it manually

After configuring Receiver chanel and completing config part, do main thing..

> Go to Tools Menu option in Integration Builder>> Select Define web service.

Specify details for sender service and sender CC.

Standard URL provided by XI is http://<server>:<port>/XISOAPAdapter/MessageServlt?channel=:<Service>:<SenderChannel>

where server is your Xi server and port name of your server.

specify your sender service and sender comm channel(this is done because now you are providing web service through xi after using your own message intrerfaces)

Save wsdl file generated by this step and test it in Soap tester (eg SOAP UI or XML SPY)

check with this blog for startup:



/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2 [original link is broken] [original link is broken] [original link is broken]

**************Reward point,if found useful

Former Member
0 Kudos