Restarting a Session Using a Web Service

Running Integration Processes 20-27 Monitoring a Session Status To monitor the status of a session from a command line via the web service: 1. Change directory to the agentbin directory of the Oracle Data Integrator installation. 2. Enter the following command to start a scenario. On UNIX systems: .getsessionstatusremote.sh session_number work_ repository remote_agent_url odi_user odi_password -w wait_mode -t timeout -i interval -h http_timeout -v Table 20–10 lists the different parameters of this command, both mandatory and optional.

20.11.12 Using the Run-Time Web Services with External Authentication

The web services examples in this chapter use an ODI authentication within the SOAP body, using the OdiUser and OdiPassword elements. When external authentication is set up for the repository and container based authentication with Oracle Platform Security Services OPSS is configured See Section 23.3.2, Setting Up External Authentication for more information, the authentication can be passed to the web service using HTTP basic authentication, WS-Security headers, SAML tokens and so forth. OPSS will transparently handle the authentication on the server-side with the identity provider. In such situation, the OdiUser and OdiPassword elements can be omitted. The run-time web services will first try to authenticate using OPSS. If no authentication parameters have been provided, OPSS uses anonymous user and the -v Verbose mode. Table 20–10 GetSessionStatusRemote command Parameters Parameters Description session_number Number of the session to monitor. work_repository Name of the work repository containing the scenario. remote_agent_url URL of the run-time agent that will run this session. odi_user Name of the user used to run this sessions. odi_password This user’s password. -w wait_mode Wait mode: ■ 0: Do not wait for session completion, report current status. ■ 1: Wait for session completion then report status. -t timeout Timeout in seconds for waiting for session to complete if sync_ mode = 2. -i interval Polling interval for session status if sync_mode = 2. -h http_timeout HTTP timeout for the web services calls. -v Verbose mode. Table 20–9 Cont. Startscenremote command Parameters Parameters Description 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.