How to Propagate a SOAP Fault from a Backend System to a Client Using Oracle Service Bus?

(Doc ID 860492.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle Service Bus - Version 2.5 and later
Information in this document applies to any platform.


How to propagate the exact SOAP Fault received from a back end service to the client via Oracle Service Bus / ALSB?

In a scenario with a message flow like:

Client -> External Proxy Service -> Internal Proxy Service -> Business service -> Backend Service

a SOAP Fault is generated by the Backen Service as follows, however, it is not correctly propagated to client.

The Backend Service is returning:

  <urn:Report xmlns:urn="urn:ecms:log:report">
      <soapenv:Header xmlns:soapenv=""
         <lmnk:messageIdentification soapenv:actor=""
                                     soapenv:mustUnderstand="0" xmlns:lmnk="">
      <soapenv:Body xmlns:soapenv=""
              <faultcode xmlns:ns1="">ns1:Client.InvalidRequest</faultcode>
              <faultstring>Group does not exist within organization</faultstring>
                <message />

However the client is receiving the following:

 <urn:Report xmlns:urn="urn:ecms:log:report">
     <soapenv:Header xmlns:soapenv="" />
       <soapenv:Body xmlns:soapenv="" />


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms