Web Services Guide

10.2.1

Back Next

System-Defined Faults

The Data Integration Service generates a system-defined fault when it encounters a system error. When a system error occurs, the Data Integration Service returns an error message in a system-defined fault.

For example, the Data Integration Service might return the following fault when a numeric input port receives data that is not numeric:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode>WSCMN_10022</faultcode>
         <faultstring>[WSCMN_10022] Mapping execution failed: [com.informatica.platform.ldtm.common.ExecutionException: [MPSVCCMN_10009] The Mapping Service Module [MappingService] encountered an exception with the following details: [LDTM_0072] [ERROR] XML parsing component [Input_S2R] message code: [66022], message body: A data conversion error occurred in field [customerID] of the transformation group [Operation]. The field contains the following data: [1100AA].].</faultstring>
         <detail>         </detail>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>

The example uses SOAP 1.1.

You can return an error message to the web service client without a Fault transformation. You can raise a fault by calling the ABORT(msg) function in an Expression transformation. When you call an ABORT message, the Data Integration Service generates a system-defined fault message. The message that you pass into the ABORT function becomes the fault string in the system-defined fault.

Rename Saved Search

Table of Contents

Web Services Guide

Web Services Guide

System-Defined Faults

System-Defined Faults