Soap Fault not processed with http 500

[Former Member]

Hello,

when receiving http 500 messages, the soap fault is not processed

correctly and not forwarded to fault mappping. We receive a system

error message so the response process is aborted, but due to soap fault

message an application error message is expected.

(System details: xi, component version Sap

NetWeaver 2004s, components level 11)

My SOAP Fault Structure looks like:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/draft-msg-header-06.xsd" xmlns:SO="http://www.xxx.com/EAI">

<SOAP-ENV:Header>

....some more tags and messages......

</SOAP-ENV:Header>

<SOAP-ENV:Body>

<SOAP-ENV:Fault>

<SOAP-ENV:Code>

<SOAP-ENV:Value>env:Sender</SOAP-ENV:Value>

<SOAP-ENV:Subcode>

<SOAP-ENV:Value>E</SOAP-ENV:Value>

</SOAP-ENV:Subcode>

</SOAP-ENV:Code>

<SOAP-ENV:Reason>

<SOAP-ENV:Text>Message</SOAP-ENV:Text>

</SOAP-ENV:Reason>

<SOAP-ENV:Detail>

<DocInfoSet>

<ApplicationArea>

....some more tags and messages....

</ApplicationArea>

</DataArea>

</DocInfoSet>

</SOAP-ENV:Detail>

</SOAP-ENV:Fault>

</SOAP-ENV:Body>

SAP Note 856597 FAQ 7 described the same problem, but it did not help.

Aslo i have read WSDL 1.1 Binding Extension for SOAP 1.2 https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0d7349b6-0901-0010-ddbe-ec43178a... but nor realy sure how to use this.

Does somebody has a idea why the response process is aborted and how to correct it?

Mario

null

[Former Member]

Hi,

Saw this old post and thought I would reply.

For reference, you can only capture SOAP faults from the SOAP adapter when they appear in SXI_MONITOR as an "application error"

There are only certain HTTP codes that are treated as "application error" under certain circumstances. These are outlined in this post:

/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi

Have a read.

Cheers

Colin.

[Former Member]

Can somebody tell me if the SOAP Adapter in XI supports SOAP1.2 messages or not?

thx

[henrique_pinto]

As for documentation:

Sender soap adapter: http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm

Receiver soap adapter: http://help.sap.com/saphelp_nw2004s/helpdata/en/29/5bd93f130f9215e10000000a155106/frameset.htm

it will work only with SOAP 1.1 Message Protocol.

Regards,

Henrique.

[Former Member]

Mario,

No it dont support 1.2. It only supports 1.1.

Check this weblog for SOAP1.2. I think it is still in the initial stages:

/people/kevin.liu/blog/2006/04/12/wsdl-11-binding-extension-for-soap-12

---Satish

[Former Member]

Does this mean XI cannot parse the SOAP fault messages at all? I am having similar issues. I even tried generating a schema from the actual error message from SOAP reciever, including it as external definition in XI and mapping the that to a fault message inbound to the sender system. Nothing works - this is crazeeeeeeeeeeee

m

[Former Member]

Hi,

we are using a synchronized message and sending via SOAP Adapter.

The Soap message is generated by our self...

When we send the SOAP message and getting a HTTP200 response from receiver everything works fine, SOAP Response mapping etc... but when we recieve a HTTP500 and a SOAP Fault message the synchronized process is aborted and we receive a system Error message. Our SOAP Fault mapping is not executed. So i dont know what is wrong!?

We are sending and receiving SOAP1.2 messages

[Former Member]

Hi-

Check this blogs to find out your problem

/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services

/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client

[Former Member]

Hi Mario,,

Can u brief more on ur scenario and explain where exactly the fault mapping is not getting the Fault msg of SOAP....

Regards

Ashwin M

[Former Member]

Hi,

As per the ans given in SAP Note : 856597 FAQ No7.

It is indicating the System Error message , so try to check the why it was happened.

Regards

Chilla