SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPT

[Former Member]

Hi there,

I am trying to publish a file from SAP as web service using XI and SOAP Adapter.

I am using ABAP proxy to get the data into XI.

Designing and Configuration in XI has no problems because when i use File adapter the data is trasmitted to FTP server.

But when I used SOAP Reciever adapter I am getting following error in RWB

Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Error during parsing of SOAP header.

<b>Scenario</b>: SAP ABAP Proxy -> XI -> WebService. Asynchronous.

<b>SOAP</b> Receiver adaptor.

<b>Target URL</b> http://<host>:<port number >/sap/xi/engine?type=entry&version=3.0&Sender.Service=SAPDC2653&Interface=urn:bzttest:00:hsa:test%5EOB_MI_BZT_TEST&QualityOfService=ExactlyOnce

Do not use SOAP Envelop is checked.

<b>SOAP Action</b> http://sap.com/xi/WebService/soap1.1

What i am missing here? How should I solve this problem?

Any help is appreciated,

Thx,

Yogi

[stefan_grube]

> <b>Target URL</b> http://<host>:<port number

> >/sap/xi/engine?type=entry&version=3.0&Sender.Service=

> SAPDC2653&Interface=urn:bzttest:00:hsa:test%5EOB_MI_BZ

> T_TEST&QualityOfService=ExactlyOnce

This is the URL if the Integration Server, you should look for the correct URL.

> Do not use SOAP Envelop is checked.

That does not make sense for a web service and that is the cause for the error.

Stefan

[Former Member]

Hi Yogi -

Where are you trying to "publish" to - what endpoint? When the endpoint is a file receiver, it's understandable. Even so for a soap receiver, but your target URL is pointing back to the XI integration engine. This type of call belongs on the SOAP sender side of XI, not the SOAP receiver. Even the name of your interface ("OB_MI_BZT_TEST") implies that the interface being called is an outbound interface. For SOAP receiver, it should be an inbound interface.

Perhaps more clarification on what you're trying to do as far as sending the data to an aysnc soap endpoint is needed.

Regards,

Jin

[Former Member]

Jin,

I am trying to expose the web service on XI web server it self.

Yogi

[Former Member]

Say there's a bapi/rfc that you want to call on an R/3 backend (e.g. 4.6c). On it's own, the R/3 system cannot expose the rfc/bapi as a web service, but XI can. So in this case, the scenario would be:

WS client -> XI -> R/3

When XI "exposes" a web service, it is exposing a service for a receiving system (in the above example, the R/3 system). XI itself does not provide or contain the service implementation. When XI exposes a web service, it is always done via the <b>sender</b> soap adapter (i.e. if soap adapter is used). Receiver soap adapter is used to call or consume an actual web service from an external application.

Regards,

Jin

[Former Member]

Hi Yogi,

Do you have WSDL fie of webservice? If you have try to test it with XML-spy.

If it works or not. If it won't work first try to run web service with XML-spy and then implement same security/ authentications/ URL details in SOAP adapter.

And check “Note 856597 - FAQ: XI 3.0 SOAP Adapter”.

Hope it helps

Regards

[Former Member]

Rohan,

You want me to test WSDL created by Define Web Service wizard?

In my scenario I am trying to publish a web service Asynchronously. I am not consuming or calling any external service.

Thx,

Yogi

[Former Member]

Hi Yogi,

In your scenario, you are sending data from SAP to XI through Proxy.

Then you are using Receiver SOAP adapter to send data to webservice.

What is this webservice???? is it third party or it is another XI scenario with Sender SOAP adapter??

What ever it is either XI sender Adapter or any third party webservice you can check whether webservice is working properly or not with XML-spy.

You can use Altova XML spy, it free available on net.

Hope it helps.

Regards.

[Former Member]

Hi Yogi,

Please read following and understand functionality of Receiver SOAP adapter scenario.

/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1

/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2

Hope it helps.

Regards

[agasthuri_doss]

Hi,

This Thread might help you

https://www.sdn.sap.com/irj/sdn/profile?userid=3301691

The HTTP code 500 indicates internal error in your application.

Check on to the stacktrace in

<local drive>:usrsapXXXYYYj2eeclusterserver0log

check note number 804124 at service.sap.com

Regards

Agasthuri Doss