proxy to SOAP

[Former Member]

This is a Proxy to SOAP scenario.

I have been given a xsd and wsdl seperately from the receiver side

I have imported xsd into IR under external definition, created MI, and completed mapping.

How to configure my receiver SOAP adapter?

1) I think I need to be provided with wsdl ratther than xsd from receiver side.

Any inputs please.

[Former Member · Accepted solution]

Hi,

As you have said, you have the wsdl with you then you can try with it also.

but the xsd taht you have used is similar to it, then its of no use.

In Receiver SOAP adapter you have to use the Target url for the given wsdl.

At the bottom of wsdl file you will get the url details.

Thanks

swarup

[Former Member]

Thanks for quick replies.

WSDL do not have message structure, thats why it i have imported xsd into IR.

If you see xmlns:xsd1="http://abcd.com/xxx.xsd he had reference to schema but this wsdl do not have msg strcutrure.

when i import this wsdl into IR, under Messages tab, i could not see anything.

This is the wsdl,

<?xml version="1.0" encoding="UTF-8"?>

<definitions targetNamespace="http://abcd.com/xxx.wsdl"

xmlns:tns="http://abcd.com/xxx.wsdl"

xmlns:xsd1="http://abcd.com/xxx.xsd"

xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

xmlns="http://schemas.xmlsoap.org/wsdl/">

<message name="initializeSessionRequest">

<part element="xsd1:Username" name="Username"/>

<part element="xsd1:Password" name="Password"/>

</message>

<message name="initializeSessionResponse">

<part element="xsd1:initializeSessionReturn" name="body"/>

</message>

<message name="closeSessionRequest"/>

<message name="closeSessionResponse">

<part element="xsd1:closeSessionReturn" name="body"/>

</message>

<message name="processRequestRequest">

<part element="xsd1:version" name="version"/>

<part element="xsd1:contentType" name="contentType"/>

<part element="xsd1:action" name="action"/>

</message>

<message name="processRequestResponse">

<part element="xsd1:processRequestReturn" name="body"/>

</message>

<message name="sessionID">

<part element="xsd1:sessionID" name="body"/>

</message>

<portType name="XOGPortType">

<operation name="processRequest">

<input message="tns:processRequestRequest"/>

<output message="tns:processRequestResponse"/>

</operation>

<operation name="initializeSession">

<input message="tns:initializeSessionRequest"/>

<output message="tns:initializeSessionResponse"/>

</operation>

<operation name="closeSession">

<input message="tns:closeSessionRequest"/>

<output message="tns:closeSessionResponse"/>

</operation>

</portType>

<binding name="XOGServiceSoapBinding" type="tns:XOGPortType">

<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>

<operation name="initializeSession">

<input message="tns:initializeSessionRequest"/>

<output message="tns:initializeSessionResponse"/>

</operation>

<operation name="processRequest">

<input message="tns:processRequestRequest">

<soap:header message="tns:sessionID" part="body" use="literal"/>

</input>

<output message="tns:processRequestResponse"/>

</operation>

<operation name="closeSession">

<input message="tns:closeSessionRequest">

<soap:header message="tns:sessionID" part="body" use="literal"/>

</input>

<output message="tns:closeSessionResponse"/>

</operation>

</binding>

<service name="XOGService">

<documentation>Niku XOG API</documentation>

<port binding="xsd1:XOGServiceSoapBinding" name="XOGServicePort">

<soap:address location="http://nikunexus.niku.com/niku/services/XOGService"/>

</port>

</service>

<types>

<schema targetNamespace="http://abcd.com/xxx.xsd" xmlns="http://www.w3.org/2001/XMLSchema">

<element name="sessionID" type="string"/>

<element name="processRequestReturn" type="anyType"/>

<element name="initializeSessionReturn" type="anyType"/>

<element name="closeSessionReturn" type="anyType"/>

<element name="Username" type="string"/>

<element name="Password" type="string"/>

<element name="version" type="string"/>

<element name="contentType" type="string" default="text/xml"/>

<element name="action" type="string"/>

</schema>

</types>

</definitions>

[Former Member]

Hi,

Thats fine you can use the xsd file as external defination and in SOAP receiver use the target url from the bottom of wsdl.

That would be fine

Thanks

Swarup

[Former Member]

Hi,

You can use Wsdl File while creating the Target Structure

How to configure Receiver SOAP Adapter

http://help.sap.com/saphelp_nw70/helpdata/EN/ae/d03341771b4c0de10000000a1550b0/frameset.htm

Regards

Seshagiri