Table of Contents

Search

  1. Preface
  2. Understanding PowerExchange for Web Services
  3. Configuring PowerExchange for Web Services
  4. Web Service Sources and Targets
  5. Web Services Consumer Transformation
  6. Creating and Configuring Web Service Workflows
  7. Appendix A: Datatype Reference

PowerExchange for Web Services User Guide for PowerCenter

PowerExchange for Web Services User Guide for PowerCenter

SOAP Fault Messages

SOAP Fault Messages

If there is a problem with the SOAP request, the Web Service application connection, or the web services host for the web service you want to access, the session might fail when reading from a web service source, writing to a web service target, or using a Web Services Consumer transformation. The PowerCenter Integration Service captures SOAP fault messages. You can configure the session properties to fail a session when there is a SOAP fault message or to write the message to a target.
SOAP fault messages contain specific information about the error.
The following table describes the SOAP 1.1 fault message elements:
Element
Description
faultcode
Faultcode element can contain any of the following indicators:
  • VersionMismatch. Invalid namespace for the SOAP Envelope element.
  • MustUnderstand. Immediate child element of the SOAP header contains the MustUnderstand parameter value set to true. The web services host does not understand the SOAP header and stops processing the rest of the message.
  • Client. The PowerCenter Integration Service SOAP request contains incorrect data or formatting.
  • Server. There is a problem with the web services host.
faultstring
Describes the error.
faultactor
Optional. URI identifying the address of the web services host that generated the error.
detail
Optional. Describes the cause of the error.
The following is an example of a SOAP 1.1 fault message:
<env:Body>   <env:Fault>     <faultcode>env:Client</faultcode>     <faultstring>Invalid input</faultstring>     <faultactor>Optional URI</faultactor>     <detail>Optional additional information</detail>   </env:Fault> </env:Body>
The following table describes the SOAP 1.2 fault message elements:
Element
Description
Code
A fault identification. The Value element of Code must be one of the following values:
  • infasoapns:DataEncodingUnknown
  • infasoapns:MustUnderstand
  • infasoapns:Receiver
  • infasoapns:Sender
  • infasoapns:VersionMismatch
Reason
An explanation of the error.
Node
Contains the URI of the SOAP node that generated the fault.
Role
Optional information about the object that caused the fault to occur.
Detail
Optional information that varies based on the fault.
The following is an example of a SOAP 1.2 fault message:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"> <soapenv:Body> <soapenv:Fault> <soapenv:Code> <soapenv:Value>soapenv:Receiver</soapenv:Value> </soapenv:Code> <soapenv:Reason> <soapenv:Text xml:lang="en-US">Your name is required.</soapenv:Text> </soapenv:Reason> <soapenv:Detail/> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope>
If the SOAP fault message indicates that the web service consumer caused the error, you might be able to correct the error and run the session successfully. When a session fails, check the session log. If it contains a SOAP fault message, you can determine if the PowerCenter Integration Service SOAP request caused the error. If the SOAP request caused the error, the faultcode specifies Client. If the faultcode specifies Client, read the SOAP fault message to determine how to modify the SOAP request before running the session again.
A SOAP fault message cannot identify an improper Web Service application connection or endpoint URL. If you see a SOAP fault message after a session fails, check the application connection settings or the endpoint URL contained in the WSDL file.
If the faultcode specifies Server, the web services host caused the error. If the web services host caused the error, you cannot fix the error. You can only run the session again to see if the server is ready to accept the SOAP request.

0 COMMENTS

We’d like to hear from you!