iWay Business Services Provider (iBSP) serves as both a SOAP gateway into the adapter framework and as the engine for some of the adapters. In both design time and run time, various conditions can cause errors in iBSP when Web services that use adapters are running. Some of these conditions and resulting errors are exposed the same way, regardless of the specific adapter. Others are exposed differently, based on the adapter being used. This appendix explains what you can expect when you encounter some of the more common error conditions, on an adapter-specific basis.

Usually the SOAP gateway (agent) inside the iBSP passes a SOAP request message to the adapter required for the Web service. If an error occurs, how it is exposed depends on the adapter and the API or interfaces that the adapter uses. A few scenarios cause the SOAP gateway to generate a SOAP fault. In general, anytime the SOAP agent inside the iBSP receives an invalid SOAP request, a SOAP fault element is generated in the SOAP response. The SOAP fault element contains fault string and fault code elements. The fault code elements contains a description of the SOAP agent error.

The following SOAP response document results when iBSP 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 this example, iBSP did not receive an element in the SOAP request message that is mandatory for the WSDL for this Web service.

For more information about error handling, see the iWay Installation and Configuration manual.