Troubleshooting
Problem
SOAP faults must be sent with HTTP 500 error code
Symptom
The WS-I Basic Profile standard requires that all SOAP faults be sent with a 500 HTTP error status. Currently, GIS sends these faults with a 200 status. If the user attempts to force a 500 status to be returned, than a default Jetty error message is returned to the user rather than the SOAP fault document.
Resolving The Problem
This enhancement adds functionality to the SOAP Outbound Adapter, B2B HTTP client/server, and Perimeter HTTP client/server adapters.
To enable this new functionality, the following assignment needs to be added to all SOAP Outbound adapters used in the flow: <assign to=""></assign>
Direct access to process data must be provided for the 'MessageFromService' to leverage the automatic communication of certain parameters to the HTTP client/response adapters. The HTTP adapters must also allow for direct access to process data on the 'MessageToService' side in order for them to read the parameters passed from the SOAP Outbound service.
If this access is not provided, than the following must be manually passed to the HTTP client/response adapter:
<doc-has-headers>true</doc-has-headers>
<status-code>500</status-code>
<xport-raw-xresponse>true</assign>
<xport-doc-on-error>true</assign>
The default behavior for the system will remain to return 200 statuses with SOAP fault messages as well as act as it did previously when faced with a 500 status.
Historical Number
NFX1142
Product Synonym
[<p><b>]Function Area[</b><p>];SOAP;[<p><b>]Escalation ID[</b><p>];1362966;[<p><b>]Fix ID[</b><p>];35708;[<p><b>]Severity[</b><p>];Normal;[<p><b>]Type[</b><p>];NewFunctionality;[<p><b>]Build[</b><p>];1981
Was this topic helpful?
Document Information
Modified date:
18 May 2020
UID
swg21560289