Stopping a Load Plan Run Using a Web Service

Running Integration Processes 20-29 The following call will be made to the ReplyTo address http:host001:8080examplesservletsservletRequestPrinter. Note that this call contains the response to the Action specified in the request, and includes the original MessageID to correlate request and response. ?xml version=1.0 encoding=UTF-8? S:Envelope xmlns:S=http:schemas.xmlsoap.orgsoapenvelope S:Header To xmlns=http:www.w3.org200508addressinghttp: host001:8080examplesservletsservletRequestPrinterTo Action xmlns=http:www.w3.org200508addressingxmlns.oracle.comodiOdiInvoke:reque stPortType:getSessionStatusResponseAction MessageID xmlns=http:www.w3.org200508addressinguuid:eda383f4-3cb5-4dc2-988c-a4f70517 63eaMessageID RelatesTo xmlns=http:www.w3.org200508addressinguuid:71bd2037-fbef-4e1c-a991-4afcd8cb 2b8eRelatesTo S:Header S:Body ns2:OdiGetSessionsStatusResponse xmlns:ns2=xmlns.oracle.comodiOdiInvoke SessionStatusResponse SessionId26001SessionId SessionStatusDSessionStatus SessionReturnCode0SessionReturnCode SessionStatusResponse ns2:OdiGetSessionsStatusResponse S:Body S:Envelope For more information on WS-Adressing, visit these World Wide Web Consortium W3C web sites at the following URLs: ■ Web Services Addressing: http:www.w3.orgSubmissionws-addressing ■ WS-Addressing SOAP Binding : http:www.w3.orgTR2006REC-ws-addr-soap-20060509 ■ WS-Addressing WSDL Binding : http:www.w3.orgTR2006WD-ws-addr-wsdl-20060216

20.11.14 Using Asynchronous Web Services with Callback

Long-running web service operations can be started asynchronously following the pattern of JRF asynchronous web services or asynchronous BPEL processes. These follow a request-response port pair pattern. In this pattern, the web service client implements a callback operation. When the server completes the operation requested by the client, it sends the result to this callback operation. Two specific operations in the agent web service support this pattern: invokeStartScenWithCallback and invokeRestartSessWithCallback. These operations provide the following features: ■ They do not return any response. These are one way operations. 20-30 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator ■ The client invoking these two operation must implement respectively the invokeStartSceCallback and invokeRestartSessCallback one way operations. Results from the invokeStartScenWithCallback and invokeRestartSessWithCallback actions are sent to these operations. ■ The invocation should provide in the SOAP header the ReplyTo and possibly FaultTo addresses. If the methods are invoked without a ReplyTo address, the operation will execute synchronously which corresponds to a invokeStartScen or invokeRestartSess operation. When a fault is generated in the operation, it will be sent to the ReplyTo address or FaultTo address. A scenario or session started synchronously using the invokeStartScenWithCallback and invokeRestartSessWithCallback will start and will not return any SOAP response, as they are one way operations. When the session completes, the response is sent the callback address. Note: Oracle BPEL takes care of automatically implementing these operations and sends out WS-Addressing headers that point to these endpoints.