Executing a Load Plan Using a Web Service

20-28 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator OdiUser and OdiPassword are checked. Otherwise this is in case of invalid credentials to OPSS OPSS throws an authentication exception and the web service is not invoked.

20.11.13 Using WS-Addressing

The web services described in this chapter optionally support WS-Addressing. WS-Addressing allows replying on an endpoint when a run-time web service call completes. For this purpose, two endpoints, ReplyTo and FaultTo, can be optionally specified in the SOAP request header. These endpoints are used in the following way: ■ When the run-time web service call completes successfully, the result of an Action is sent to the ReplyTo endpoint. ■ If an error is encountered with the SOAP request or if Oracle Data Integrator is unable to execute the request, a message is sent to the FaultTo address. If the FaultTo address has not been specified, the error is sent to the ReplyTo address instead. ■ If Oracle Data Integrator encounters errors while processing the request and needs to raise an ODI error message, this error message is sent back to the ReplyTo address. Note that callback operations do not operate in callback mode unless a valid ReplyTo address is specified. The following is an example of a request that is sent to retrieve the session status for session 20001: soapenv:Envelope xmlns:soapenv=http:schemas.xmlsoap.orgsoapenvelope xmlns:odi=xmlns.oracle.comodiOdiInvoke soapenv:Header xmlns:wsa=http:www.w3.org200508addressing wsa:Action soapenv:mustUnderstand=1xmlns.oracle.comodiOdiInvokegetSessionStatuswsa:Ac tion wsa:ReplyTo soapenv:mustUnderstand=1 wsa:Addresshttp:host001:8080examplesservletsservletRequestPrinterwsa:Add ress wsa:ReplyTo wsa:MessageID soapenv:mustUnderstand=1uuid:71bd2037-fbef-4e1c-a991-4afcd8cb2b8ewsa:MessageI D soapenv:Header soapenv:Body odi:OdiGetSessionsStatusRequest Credentials --You may enter the following 3 items in any order-- OdiUserOdiUser OdiPasswordOdiPassword WorkRepositoryWORKREP1WorkRepository Credentials --Zero or more repetitions:-- SessionIds20001SessionIds odi:OdiGetSessionsStatusRequest soapenv:Body soapenv:Envelope Note: OPSS authentication is only possible for a Public Web Service or JEE Agent deployed in a Oracle WebLogic Server. 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.