Right-click the Scheduling node under a scenario or a Load Plan in the Designer

Running Integration Processes 20-21 This operation returns a response in the following format: ?xml version = 1.0 encoding = ISO-8859-1? ns2:OdiStartScenResponse xmlns:ns2=xmlns.oracle.comodiOdiInvoke Session543001Session ns2:OdiStartScenResponse

20.11.3 Monitoring a Session Status Using a Web Service

The getSessionStatus operation of the agent web service returns the status of one or more sessions in a given repository, identified by their Session Numbers provided in the SessionIds element. It manages both running and completed sessions. OdiGetSessionsStatusRequest Credentials OdiUserodi_userOdiUser OdiPasswordodi_passwordOdiPassword WorkRepositorywork_repositoryWorkRepository Credentials SessionIdssession_numberSessionIds OdiGetSessionsStatusRequest This operation returns a response in the following format: SessionStatusResponse SessionIdsession_idSessionId SessionStatusstatus_codeSessionStatus SessionReturnCodereturn_codeSessionReturnCode SessionStatusResponse The Return Code value is zero for successful sessions and possible status codes are: ■ D: Done ■ E: Error ■ M: Warning ■ Q: Queued ■ R: Running ■ W: Waiting

20.11.4 Restarting a Session Using a Web Service

The invokeRestartSess operation of the agent web service restarts a session identified by its session number provided in the SessionID element in a given work repository. The session is executed by the agent providing the web service. Only sessions in status Error or Waiting can be restarted. The session will resume from the last non-completed task typically, the one in error. Note that you can change the value of the variables or use the KeepVariables boolean element to reuse variables values from the previous session run. invokeRestartSessRequest Credentials OdiUserodi_userOdiUser OdiPasswordodi_passwordOdiPassword WorkRepositorywork_repositoryWorkRepository Credentials Request 20-22 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator SessionIDsession_numberSessionID SynchronoussynchronousSynchronous KeepVariables0|1KeepVariables Variables Namevariable_namename Valuevariable_valueValue Variables Request invokeRestartSessRequest This operation returns a response similar to InvokeStartScen, depending on the Synchronous element’s value.

20.11.5 Executing a Load Plan Using a Web Service

The invokeStartLoadPlan operation of the agent web service starts a Load Plan in a given work repository. The Load Plan is executed by the agent providing the web service. Note the following concerning the parameters of the invokeStartLoadPlan operation: ■ OdiPassword: Use a password in clear text. ■ Context: Use the context code. ■ Keywords: If you use several keywords, enter a comma separated list of keywords. ■ Name: Use the fully qualified name for variables: GLOBAL.variable_name or PROJECT_CODE.variable_name The following shows the format of the OdiStartLoadPlanRequest. OdiStartLoadPlanRequest Credentials OdiUserodi_userOdiUser OdiPasswordodi_passwordOdiPassword WorkRepositorywork_repositoryWorkRepository Credentials StartLoadPlanRequest LoadPlanNameload_plan_nameLoadPlanName ContextcontextContext KeywordskeywordsKeywords LoadPlanStartupParameters Namevariable_nameName Valuevariable_valueValue LoadPlanStartupParameters StartLoadPlanRequest OdiStartLoadPlanRequest The invokeStartLoadPlan operation returns the following values in the response: ■ Load Plan Run ID ■ Load Plan Run Count ■ Master Repository ID ■ Master Repository timestamp The following is an example of an OdiStartLoadPlan response: ?xml version = 1.0 encoding = UTF8? ns2:OdiStartLoadPlanResponse xmlns:ns2=xmlns.oracle.comodiOdiInvoke executionInfo