From Traditional Integration to Composition – Enterprise Business Services - Applied SOA Patterns on the Oracle Platform - page 285

cessing is terminated by the Raise Error operation with the following message: The mes-
sage has been filtered .
Now, we have come to the last part of the VETRO sequence: operate. We will pass the
message to the Adapter Facade Proxy Service, which will do the actual dispatching.
Operate
The operate task is actually the routing implementation. In the request action pipe, we set
ABO and Transport Header (which is responsible for transporting the JCA parameters that
are related to the Transport Adapter properties):
Implementation of the Operate functionality on OSB
Replace the message body with the results of the transformation (or the original body if
the transformation step was omitted). The Adapter Facade Proxy is (traditionally) based
on CustomService.wsdl , our dummy service which we use for dynamic binding.
Please refer to the simple WSDL in the following screenshot. The CTUMessage payload
is our generic message container.