cancel
Showing results for 
Search instead for 
Did you mean: 

Testing Webservices in XI with XML Spy

Former Member
0 Kudos

Hi ,

I am trying to define a Webservice in XI from the ID by going to Tools -> Define Webservice( the usual way ) and I got the WSDL.I am trying to use the same from XML Spy to send SOAP messages to XI.But there is something wrong in the link generated.Does somebody has a prior exp or idea about what needs to be done exactly to get it running.

Regards,

Sudip.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

You have to give this URL while defining webservice from ID....

http://[server]:[port]/XISOAPAdapter/MessageServlet?channel=:[sender communication channel service]:[sender communication channel name]

Check this blog to generate WDSL file...

/people/community.user/blog/2006/10/24/exposing-bapi-as-web-services-through-sap-xi

USE this WSDL file while testing with XMLSPY

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Sudip.

If the endpoint wich you used in the wizard define is well formed like as the next format:

http://[server]:[port]/XISOAPAdapter/MessageServlet?channel=:[sender communication channel service]:[sender communication channel name]

In the xml spy, click in create new soap request then use the url of the wsdl file disk, it will make an soap request, then you put the correct values inside their tags.

If you have done an good work, it will response with an soap response.

I hope to be helpful you

Regards

Sergio Gómiz

bhavesh_kantilal
Active Contributor
0 Kudos

Sudip,

One more issue i remmeber when using the WSDL generated by XI in XML Spy was that I had to go to the URL and replace all & with & amp; ( without the space) and then the request was triggered to XI.

if you are facing an issue while posting would suggest you give this a try and let us know if it does the trick.

regards

Bhavesh

Former Member
0 Kudos

Hi Bhavesh,

I was trying the second option to send it to the integration server directly. But the error which I get it as follows

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP:Body>

<SOAP:Fault>

<faultcode>SOAP:Server</faultcode>

<faultstring>System Error</faultstring>

<detail>

<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">

<context/>

<code>RCVR_DETERMINATION.MESSAGE_INCOMPLETE</code>

<text>Message is incomplete. No Sender found</text>

</s:SystemError>

</detail>

</SOAP:Fault>

</SOAP:Body>

</SOAP:Envelope>

But this is a working scenario.

link which is generated is as follows

http://bsw6220:51000/sap/xi/engine?type=entry&amp;version=3.0&amp;Sender.Party=http%3A%2F%2Fsap.com%...

Any idea what went wrong?

Regards,

Sudip.

Former Member
0 Kudos

THe URL actually contains "& amp;" instead of &.

Former Member
0 Kudos

Hi,

try

&amp instead & amp

Chilla.

Former Member
0 Kudos

i am that without space only.

bhavesh_kantilal
Active Contributor
0 Kudos

Sudip,

Try replacing the & amp; with an & and test your scenario.

I dont rememebr if my problem was with & amp; or & , so i woudl suggest that you remove the amp; and also give it a shot.

Regards

Bhavesh

bhavesh_kantilal
Active Contributor
0 Kudos

Hi,

You can generate the WSDL with 2 Url's.

1. Section 3.2.2 of this document describes sending the SOAP request to the adapter engine and then the Sender SOAP adapter forwards it to the integratin engine. Look into the section 3.2.2 and check if this is how you created the WSDL and the URL.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873...

2. Or, you can send the request directly to the integration engine. Refer to this blog by Stefan and use the URL in the blog if needed. No need for a sender SOAP adapter in this case,

/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine

Regards

Bhavesh