Executing a Scenario from ODI Studio

Running Integration Processes 20-9 ■ Stopping a Session From a Command Line . ■ From ODI Console. See Section 22.2.3, Managing Scenarios and Sessions .

20.5.1 Stopping a Session From ODI Studio

To stop a session from Oracle Data Integrator Studio: 1. In Operator Navigator, select the running or waiting session to stop from the tree.

2. Right-click then select Stop Normal or Stop Immediate.

3. In the Stop Session Dialog, click OK.

The session is stopped and changed to Error status.

20.5.2 Stopping a Session From a Command Line

Before stopping a session from a command line, read carefully the following requirements: ■ The command line scripts, which are required for performing the tasks described in this section, are only available if you have installed the Oracle Data Integrator Standalone Agent. See the Oracle Fusion Middleware Installation Guide for Oracle Data Integrator for information about how to install the Standalone Agent. ■ To use this command the connection to your repository must be configured in the odiparams file. See Chapter 4.3, Managing Agents for more information. To stop a session from a command line: 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: .stopsession.sh session_id [-AGENT_URL=remote_agent_url] [-STOP_LEVEL=normal default | immediate] On Windows systems: stopsession.bat session_id [-AGENT_URL=remote_agent_ url][-STOP_LEVEL=normal default | immediate] Table 20–3 lists the different parameters of this command, both mandatory and optional. The parameters are preceded by the - character and the possible values are preceded by the = character. You must follow the character protection syntax specific to the operating system on which you enter the command. Table 20–4 StopSession command Parameters Parameters Description session_id Number ID of the session to be restarted. -AGENT_URL=remote_ agent_url URL of the run-time agent that stops this session. By default the session is executed by a local Java process started from the command line. [-STOP_LEVEL=normal default | immediate] The level used to stop a running session. If it is omitted, normal will be used as the default stop level. 20-10 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator

20.6 Executing a Load Plan

Load Plans can be executed in several ways: ■ Executing a Load Plan from ODI Studio ■ Executing a Load Plan from a Command Line ■ From a Web Service. See Section 20.11.5, Executing a Load Plan Using a Web Service for more information. ■ From ODI Console. See Section 22.2.4, Managing Load Plans .

20.6.1 Executing a Load Plan from ODI Studio

In ODI Studio, you can run a Load Plan in Designer Navigator or in Operator Navigator. To run a Load Plan in Designer Navigator or Operator Navigator: 1. In the Load Plans and Scenarios accordion, select the Load Plan you want to execute.

2. Right-click and select Execute.

3. In the Start Load Plan dialog, select the execution parameters: ■ Select the Context into which the Load Plan will be executed. ■ Select the Logical Agent that will run the step. ■ In the Variables table, enter the Startup values for the variables used in this Load Plan.

4. Click OK.

5. The Load Plan Started Window appears.

6. Click OK.

A new execution of the Load Plan is started: a Load Plan instance is created and also the first Load Plan run. You can review the Load Plan execution in the Operator Navigator.

20.6.2 Executing a Load Plan from a Command Line

You can start a Load Plan from a command line. Before executing a Load Plan from a command line, read carefully the following requirements: ■ The command line scripts, which are required for performing the tasks described in this section, are only available if you have installed the Oracle Data Integrator Standalone Agent. See the Oracle Fusion Middleware Installation Guide for Oracle Data Integrator for information about how to install the Standalone Agent. Note: To use this command the connection to your repository must be configured in the odiparams file. See Section 4.3, Managing Agents for more information. Note: A Load Plan cannot be executed using the ODI Studio built-in agent called Local No Agent.