BEA WebLogic Server, User Manual

Page: 189 / 294

Troubleshooting and Error Messages
BEA WebLogic Adapter for SAP User’s Guide 9-7
The following SOAP response document results when iBSE receives an invalid SOAP
request:
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Client</faultcode>
<faultstring>Parameter node is missing</faultstring>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
In the previous example, iBSE did not receive an element in the SOAP request message that
is mandatory for the WSDL for this Web service.
Adapter-Specific Error Handling
When an adapter raises an exception during run time, the SOAP agent in iBSE produces a
SOAP fault element in the generated SOAP response. The SOAP fault element contains fault
code and fault string elements. The fault string contains the native error description from
the adapter target system. Because adapters use the target system interfaces and APIs,
whether an exception is raised depends on how the target systems interface or API treats
the error condition. If a SOAP request message is passed to an adapter by the SOAP agent in
iBSE and that request is invalid based on the WSDL for that service, the adapter may raise an
exception yielding a SOAP fault.
Although it is almost impossible to anticipate every error condition that an adapter may
encounter, the following examples show how adapters handle common error conditions
and how error conditions are then exposed to the Web services consumer application.