SOAP adapter URL causing problems

[Former Member]

Hi gurus,

As of PI 7.1, SAP is recommending to use:

http://host:port/XISOAPAdapter/MessageServlet?senderParty=FP&senderService=FS&interface=IF&receiverP...

instead of

http://<serverhost>:<port>/XISOAPAdapter/MessageServlet?channel=<party>:<ServiceName>:<ChannelName>;

while sending messages to the SOAP adapter. BUT, the new format is causing problems when the developers are trying to import the WSDL (to Webdynpro, eclipse, etc). Also, XMLSpy complains that the xml is not well-formed because of the soap address field.

So I removed the & signs and replaced them with the escape equivalent of &amp; for the new format and tried to use:

http://host:port/XISOAPAdapter/MessageServlet?senderParty=FP&amp;senderService=FS&amp;interface=IF&a...

But this time, SOAP adapter replies saying there is no binding. How to overcome this?

Thanks

Gokhan

[former_member200962 · Accepted solution]

are you testing using XML SPY??

XML SPY is infamous for giving the binding not found error...

Try from RWB ---> Component Monitoring ---> IE ---> TestMessage...

Regards,

Abhishek.

[stefan_grube]

Choose the "old" version, that will work.

Regards

Stefan

[former_member200962]

try this format:

http://<hostname OR IP addr>:<portno>/XISOAPAdapter/MessageServlet?channel=:<SenderService>:<SenderSOAPCC>&version=3.0&Sender.Service=<senderService>&Interface=<senderNamespace>%5E<senderMI>

[Former Member]

Hi,

I am testing from external tools, not XMLSpy. I guess the web page is removing also some of the characters of the URL you suggested, or is it correct?

[ravi_raman2]

did you try replacing the & with &amp.....?

Just curious..

Regards

Ravi Raman

[Former Member]

Yes, I did as I pointed out. But this time, I get the "no binding" error from PI, as it cannot determine any channels for it.

BTW, some runtimes actually call the correct url with & signs by converting &amp's at runtime.

[former_member200962]

dont think that any characters are removed from the URL......did you face any error in using it?...i am using this url format in SAP SOAP Client....