An operation mapping can contain an Input transformation, an Output transformation, and multiple Fault transformations. The Input, Output, and Fault transformations process SOAP messages. The mapping can also contain other transformations that retrieve, transform, or update data based on the web service operation that the client requests.

After you create a web service in the Developer tool, configure an operation mapping for each operation in the web service. An operation mapping represents the logic for an operation.

When you configure the operation mapping, you define how the Data Integration Service processes the data that it receives in the SOAP request. The SOAP request can be of SOAP 1.1 or SOAP 1.2 format based on the binding type used by the binding operation associated with the operation mapping.

The Input transformation receives a SOAP request from a web service client and then returns data to transformations downstream in the mapping. The transformations perform the operation that the client requests.

The Output transformation receives data to return to the client. The Output transformation generates a SOAP response message to send to the client.

If an error occurs, the Data Integration Service generates a fault. The Data Integration Service returns user-defined faults from a Fault transformation. A user-defined fault consists of two types of faults: predefined fault and generic fault.

To configure the operation mapping, complete the following steps:

Configure the Input, Output, and Fault transformations.
Create and configure additional transformations to implement the operation logic.
Link ports.
Validate and save the mapping.

You can view and configure operation mapping properties on the

General

tab,

Operation

tab, and the

Advanced

tab in the operation mapping

Properties

view.