Exporting and Importing a Work Repository

20 Running Integration Processes 20-1 20 Running Integration Processes This chapter describes how to run and schedule integration processes. This chapter includes the following sections: ■ Section 20.1, Understanding ODI Executions ■ Section 20.2, Executing Interfaces, Procedures, Packages and Model Operations ■ Section 20.3, Executing a Scenario ■ Section 20.4, Restarting a Session ■ Section 20.5, Stopping a Session ■ Section 20.6, Executing a Load Plan ■ Section 20.7, Restarting a Load Plan Run ■ Section 20.8, Stopping a Load Plan Run ■ Section 20.9, Scheduling Scenarios and Load Plans ■ Section 20.10, Simulating an Execution ■ Section 20.11, Managing Executions Using Web Services

20.1 Understanding ODI Executions

An execution takes place when an integration task needs to be performed by Oracle Data Integrator. This integration task may be one of the following: ■ An operation on a model, sub-model or a datastore, such as a customized reverse-engineering, a journalizing operation or a static check started from the Oracle Data Integrator Studio ■ The execution of a design-time object, such as an interface, a package or a procedure, typically started from the Oracle Data Integrator Studio ■ The execution of a run-time scenario or a Load Plan that was launched from the Oracle Data Integrator Studio, from a command line, via a schedule or a web service interface Oracle Data Integrator generates the code for an execution in the form of a session or in the from of a Load Plan run if a Load Plan is executed. A run-time Agent processes this code and connects to the sources and targets to perform the data integration. These sources and targets are located by the Agent using a given execution context. 20-2 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator When an execution is started from Oracle Data Integrator Studio, the Execution Dialog is displayed. This dialog contains the execution parameters listed in Table 20–1 . Session Lifecycle This section describes the session lifecycle. See Section 14.1, Introduction to Load Plans for more information on Load Plan runs and the Load Plan life cycle. The lifecycle of a session is as follows: 1. An execution request is sent to the agent, or the agent triggers an execution from a schedule. Note that if the execution is triggered from Oracle Data Integrator Studio on a design-time object interface, package, etc., Studio pre-generates in the work repository the code for the session before sending the request. If the execution is started from a scenario, this phase is not necessary as the scenario already contains pre-generated code.

2. The agent completes code generation for the session: It uses the context provided

to resolve the physical information such as data server connections and fully qualified tables names. This resulting code is written into the work repository as a session in Waiting status.

3. The agent initializes the connections to the source and target data servers that are

required for the execution of the session.

4. The agent acknowledges the execution request. If the execution was started from

the Studio, the Session Started Dialog is displayed.

5. The agent executes each of the tasks contained in this session, using the

capabilities of the database servers, operating systems, or scripting engines to run the code contained in the session’s tasks.

6. While processing the session, the agent updates the execution log in the repository,

reports execution statistics and error messages. Once the session is started, you can monitor it in the log, using for example Operator Navigator. Refer to Chapter 21, Monitoring Integration Processes for more information on session monitoring. 7. When the session completes, tasks are preserved or removed from the log according to the log level value provided when starting for this session. Table 20–1 Execution Parameters Properties Description Context The context into which the session is started. Agent The agent which will execute the interface. The object can also be executed using the agent that is built into Oracle Data Integrator Studio, by selecting Local No Agent. Log Level Level of logging information to retain. All session tasks with a defined log level lower than or equal to this value will be kept in the Session log when the session completes. However, if the object execution ends abnormally, all tasks will be kept, regardless of this setting. Simulation Check Simulation if you want to simulate the execution and create an execution report. Refer to Section 20.10, Simulating an Execution for more information.