Web Service Manager Doesn't Send Back WSDL 1.1 Compliant SOAP Message If CM/DM Is Down (Doc ID 744504.1)

Last updated on NOVEMBER 18, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.0.0.0 and later
Information in this document applies to any platform.
Checked for relevance on 19-Jan-2012.
*** Checked for relevance on 11-18-2016 ***

Symptoms

The current implementation of Web Services (WS) does not support SOAP (Simple Object Access Protocol ) faults. Currently BRM WS Manager propagates the error messages as flists converted to xml through WS.

 Steps To Reproduce:

1. On a BRM instance with WS Manager running, stop the CM, DM, or both.
2. Make a WS call using a preferred tool (e.g SOAP UI).

When BRM is down, WS manager returns the below (xml format):

<opcodeReturn>ERROR: <?xml version="1.0" encoding="UTF-8"?>
<flist>
<ERROR_CODE>27</ERROR_CODE>
<ERROR_DESCR>ERR_NAP_CONNECT_FAILED</ERROR_DESCR>
<FIELD_NAME>UnknownField0</FIELD_NAME>
<LOCATION>Unknown Location</LOCATION>
</flist>
</opcodeReturn>

It should be returning a SOAP failure packet like below:

<SOAP-ENV:Envelope
xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/'
SOAP-ENV:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'
xmlns:v='http://www.eggheadcafe.com/webservices/'>;
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>27</faultcode>
<faultstring>ERR_NAP_CONNECT_FAILED</faultstring>
<detail>
<message>Unknown Location</message>
<errorcode>UnknownField0</errorcode>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>


The WSDL 1.1 specification section which refers to SOAP faults is available at the following link http://www.w3.org/TR/wsdl#_soap:fault

Changes

 

Cause

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