How to troubleshoot soap adapters

[former_member198282]

Hi, all.

I know this question have been asked many times in the forum. However, I haven't found the answer that I need. I'm setting up a simple test scearnio: jdbc -> PI -> web service. The web service is setup with a bapi published as a web service in soamanager. I am able to test the web service from the portal wsnavigator without any issue.

However, when I am trying to call the web service using the soap adapter, nothing happens even though I can see the checkered flag in the sxmb_moni. The RWB also reports no error. Here is the soap receiver adapter config:

target url: http://XXXX:8013/sap/bc/srt/wsdl/bndg_4D9D2ACF4C0913E5E10000000A6430E2/wsdl11/allinone/ws_policy/doc...

The above url is received from the "Open WSDL document for selected binding" from soamanager. I have also supplied the user/password in the adapter configuration. The option "Do not use soap envelop" is selected as I don't think the soamanager service has a soap envelop. The "soap action" is left blank.

Please advise if I have done something wrong. I have added a breakpoint on the bapi and nothing happens. So I don't believe the web service in soamanager is ever called.

Thanks,

John.

[aashish_sinha]

Hi,

Have a look into below document and see if you doing something similar.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024...

Regards

Aashish Sinha

[former_member198282]

Hi, Aashish

I am aware of this link. But it does not help since our web service is coming from soamanager(where I believe is the culprit). Any other idea?

Thanks,

Jonathan.

[Former Member]

Hi,

If you are using a webservice on a backend system then most probably the soap envelope is used.

if the message was delivered successfully and you checked that in the RWB on the communication channel log then I suggest you do a check in the receiving system in soamanager under logs if there is not a parsing error on their side

[former_member198282]

Hi, Horia.

This is what I am doing now. In the soap adapter url, if I use the link in "Open WSDL document for selected binding", everything is fine in RWB and sxmb_moni. But nothing happens on soamanager. If I use the url from "Calculated Access URL" under transport settings on soamanager, I do get an error from the soamanager trace. The error is the following:

A SOAP Runtime Core Exception occurred in method get_http_headers of class CL_SOAP_HTTP_TPBND_ROOT at position id 3 with internal error id 1007 and error text SRT: Unsupported xstream found: ("HTTP Code 200 : OK") (fault location is 1 ).

Note that the 2 url's are not the same. But then I haven't found a way to resolve the runtime error above. Also, I don't know which url should I use in the soap adapter.

Thanks,

Jonathan.

Edited by: Jonathan Ma on Apr 29, 2011 9:42 PM

[Former Member]

Try filling the "soap action" field with the name of the operation called from WS. Also, are you using splitting or packaging on the scenario? There are some bugs where the payload is ignored when a certain condition is met.

[former_member198282]

Hi, Lucas.

I am not doing any splitting or packaging in my scenario(not using AAE at all). What soap action do you put in if it is a web service in the soamanager?

Thanks,

Jonathan.

[former_member200962]

SOAP action will be present in the WSDL file itself...it is an optional parameter....what about the status of the SOAP receiver channel in RWB --> Channel Monitoring?

[former_member198282]

I didn't see any soap action in the wsdl file ... the soap receiver channel shows no error. As a matter of fact, it thought that the message has been delivered successfully.

Thanks,

Jonathan.