Table of Contents

Search

  1. Preface
  2. Web Services
  3. SOAP Web Services
  4. WSDL Data Object
  5. Schema Object
  6. How to Create a SOAP Web Service
  7. Operation Mappings
  8. Parsing Web Service SOAP Messages
  9. Generating Web Service SOAP Messages
  10. Web Service Consumer Transformation
  11. REST Web Services
  12. How to Create a REST Web Service
  13. REST Web Service Consumer Transformation
  14. REST Web Service Consumer Transformation Use Cases
  15. REST and SOAP Web Service Administration
  16. Datatype Compatibility

Web Services Guide

Web Services Guide

Fault Transformation

Fault Transformation

The Fault transformation represents the Fault element in the web service WSDL. The Fault transformation generates a user-defined fault in the web service operation.
The Fault transformation represents either of the following user-defined faults:
Predefined fault
A predefined fault is where the Fault transformation represents the Fault element in the web service WSDL. In a predefined fault, the Fault transformation creates an error message from relational data in the web service operation mapping.
Generic fault
A generic fault is where the Fault transformation does not represent any of the Fault elements defined in the web service WSDL for a web service operation. The Fault transformation for a generic fault returns a generic error message when an error occurs in a transformation. You can create and configure a Fault transformation for a generic fault from the Developer tool.
An operation mapping can contain multiple Fault transformations. You can add multiple instances of the same Fault transformation in a mapping to generate the same message in different parts of the mapping.
You can add Fault transformations to the mapping or remove them from the mapping without changing the operation signature. If you know that a fault error can never occur when the mapping runs, you can remove the Fault transformation from the mapping. You must connect a Fault transformation to an upstream transformation or the mapping is not valid.
When you create a fault in an operation that has a SOAP 1.1 binding, the wizard creates the faultcode, faultstring, and faultactor elements. When you create a fault in an operation that has a SOAP 1.2 binding, the wizard creates the code, reason, node, and role elements. When you add elements to the fault, the wizard adds the elements to the detail group in the fault. Use the Fault transformation
Ports
tab to view the operation fault hierarchy, add transformation input ports, and map the input ports to the operation fault. The operation fault hierarchy defines the SOAP response message hierarchy for error messages that result from a user-defined fault.
You can map XML data from one string or text input port to the entire SOAP response. When you map XML data to the entire SOAP response, you cannot map ports to nodes in the operation fault.
Configure advanced properties in the Fault transformation
Advanced
tab.

0 COMMENTS

We’d like to hear from you!