Web Services
This section describes changes to web services.
Fault Transformation
Effective in version 9.5.0, you can configure a Fault transformation to return a generic error message when the error is not defined by a fault element in the WSDL. When you create a Fault transformation for a generic fault in a web service, you must define the operation mapping logic that returns the error condition.
Previously, you could create a Fault Transformation to return a predefined fault from a fault element. The web service used a fault element to define the fault. You could configure a Fault transformation to return a custom error message.
Fault Terminology
Effective in version 9.5.0, the fault handling terminology changed. Faults can be of the following types:
- •System defined
- •User-defined
The following table shows the terminology changes:
9.5 Term | Previous Term |
|---|
System defined fault. | Generic fault. |
User-defined fault. | - |
Predefined fault. | User-defined fault. |
Generic fault. | - |
Manual Web Services
Effective in version 9.5.0, the Developer tool contains behavior changes for web services that you create manually.
The Developer tool contains the following behavior changes:
- •When you change an element type from complex to simple, the Developer tool clears the location of the associated port. Previously, the Developer tool deleted the associated port.
- •When you change an element type from simple to complex, the Developer tool marks the port as not valid. Previously, the Developer tool cleared the location of the associated port.
SOAP 1.2
Effective in version 9.5.0, the following changes are implemented for SOAP 1.2:
- •Each web service can have one or more operations that use either a SOAP 1.1 binding or a SOAP 1.2 binding but not both.
- •The SOAP request can be of SOAP 1.1 or SOAP 1.2 format. The SOAP request is based on the type of binding that is used by the binding operation associated with the operation mapping.
- •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.
Previously, you could only create an operation with a SOAP 1.1 binding and create a fault in an operation with a SOAP 1.1 binding.
Transport Layer Security
Effective in version 9.5.0, if you enable Transport Layer Security (TLS) for a web service, you must set the Data Integration Service HTTP protocol type property to HTTPS or Both. Then, you must set the HTTPS port for each Data Integration Service process.
Previously, if you enabled TLS for a web service, you had to enable TLS for the Data Integration Service process and then set the HTTPS port for the process.
When you upgrade, the upgrade process sets the HTTP protocol type property to one of the following values:
- •HTTP if only the HTTP port was set for the Data Integration Service process.
- •HTTPS if only the HTTPS port was set for the Data Integration Service process.
- •Both if both the HTTP and the HTTPS ports were set for the Data Integration Service process.