On the Execution Cycle tab, specify the parameters for the repeat mode of the On the Variables tab, unselect Latest Value for variables for which you want to

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 Running Integration Processes 20-23 StartedRunInformation OdiLoadPlanInstanceId2001OdiLoadPlanInstanceId RunCount1RunCount MasterRepositoryId0MasterRepositoryId MasterRepositoryTimestamp1290196542926MasterRepositoryTimestamp StartedRunInformation executionInfo ns2:OdiStartLoadPlanResponse

20.11.6 Stopping a Load Plan Run Using a Web Service

The invokeStopLoadPlan operation of the agent web service stops a running Load Plan run identified by the Instance ID and Run Number in a given work repository. The Load Plan instance is stopped by the agent providing the web service. Note that the StopLevel parameter can take the following values: ■ NORMAL: Waits until the current task finishes and then stops the session. ■ IMMEDIATE: Stops the session immediately, cancels all open statements and then rolls back the transactions. See Section 20.8, Stopping a Load Plan Run for more information on how to stop a Load Plan run and Section 20.11.5, Executing a Load Plan Using a Web Service for more information on the other parameters used by the invokeStopLoadPlan operation. OdiStopLoadPlanRequest Credentials OdiUserodi_userOdiUser OdiPasswordodi_passwordOdiPassword WorkRepositorywork_repositoryWorkRepository Credentials OdiStopLoadPlanRequest LoadPlanInstanceIdload_plan_instance_idLoadPlanInstanceId LoadPlanInstanceRunCountload_plan_run_countLoadPlanInstanceRunCount StopLevelstop_levelStopLevel OdiStopLoadPlanRequest OdiStopLoadPlanRequest The invokeStopLoadPlan 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 OdiStopLoadPlan response: S:Envelope xmlns:S=http:schemas.xmlsoap.orgsoapenvelope S:Body ns2:OdiStopLoadPlanResponse xmlns:ns2=xmlns.oracle.comodiOdiInvoke executionInfo StoppedRunInformation OdiLoadPlanInstanceId3001OdiLoadPlanInstanceId RunCount1RunCount MasterRepositoryId0MasterRepositoryId MasterRepositoryTimestamp1290196542926MasterRepositoryTimestamp StoppedRunInformation executionInfo ns2:OdiStopLoadPlanResponse