Using the Run-Time Web Services with External Authentication

Monitoring Integration Processes 21-3 Two special steps called Command On Connect and Command On Disconnect are created if you have set up On Connect and Disconnect commands on data servers used in the session. See Setting Up On ConnectDisconnect Commands for more information. The task is the smallest execution unit. It corresponds to a command in a KM, a procedure, and so forth. Sessions can be grouped into Session folders. Session folders automatically group sessions that were launched with certain keywords. Refer to Section 21.3.3.3, Organizing the Log with Session Folders for more information.

21.1.4 Load Plans

A Load Plan is the largest executable object in Oracle Data Integrator. It uses Scenarios in its steps. A Load Plans is an organized hierarchy of child steps. This hierarchy allows conditional processing of steps in parallel or in series. Load Plans are imported into production environment and can be organized into Load Plan and Scenario folders. See Section 21.3.4, Managing Scenarios and Load Plans for more details.

21.1.5 Load Plan Executions

Executing a Load Plan creates a Load Plan instance and the first Load Plan run for the instance. This Load Plan instance is separated from the original Load Plan and can be modified independently. Every time a Load Plan instance is restarted, a Load Plan run is created for this Load Plan instance. A Load Plan run corresponds to an attempt to execute the instance. See Section 14.1.1, Load Plan Execution Lifecycle for more information. When running, a Load Plan Run starts sessions corresponding to the scenarios sequenced in the Load Plan. Note that in the list of Load Plan executions, only the Load Plan runs appear. Each run is identified by a Load Plan Instance ID and an Attempt or Run Number.

21.1.6 Schedules

You can schedule the executions of your scenarios and Load Plans using Oracle Data Integrator’s built-in scheduler or an external scheduler. Both methods are detailed in Section 20.9, Scheduling Scenarios and Load Plans . The schedules appear in Designer and Operator Navigator under the Scheduling node of the scenario or Load Plan. Each schedule allows a start date and a repetition cycle to be specified.

21.1.7 Log

The Oracle Data Integrator log corresponds to all the Sessions and Load Plan instancesruns stored in a repository. This log can be exported, purged or filtered for monitoring. See Section 21.3.3, Managing the Log for more information.

21.1.8 Status

A session, step, task or Load Plan run always has a status. Table 21–2 lists the six possible status values: 21-4 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator When finished, a session takes the status of the last executed step Done or Error. When finished, the step, takes the status of the last executed task Except if the task returned a Warning. In this case, the step takes the status Done. A Load Plan is successful status Done when all its child steps have been executed successfully. It is in Error status when at least one of its child steps is in error and has raised its exception to the root step.

21.2 Monitoring Executions Results

In Oracle Data Integrator, an execution results in a session or in a Load Plan run if a Load Plan is executed. A session is made up of steps which are made up of tasks. Sessions are viewed and managed in Operator Navigator. Load Plan runs appear in the Operator Navigator. To review the steps of a Load Plan run, you open the editor for this run. The sessions attached to a Load Plan appear with the rest of the sessions in the Operator Navigator.

21.2.1 Monitoring Sessions

To monitor your sessions:

1. In the Operator Navigator, expand the Session List accordion.

2. Expand the All Executions node and click Refresh in the Navigator toolbar.

3. Optionally, activate a Filter to reduce the number of visible sessions. For more

information, see Section 21.3.3.1, Filtering Sessions . Table 21–2 Status Values Status Name Status Icon for Sessions Status Icon for Load Plans Status Description Done The Load Plan, session, step or task was executed successfully. Done in previous run The Load Plan step has been executed in a previous Load Plan run. This icon is displayed after a restart. Error The Load Plan, session, step or task has terminated due to an error. Running The Load Plan, session, step or task is being executed. Waiting The Load Plan, session, step or task is waiting to be executed. Warning Sessions and tasks only ■ For Sessions: The session has completed successfully but errors have been detected during the data quality check. ■ For Tasks: The task has terminated in error, but since errors are allowed on this task, this did not stop the session. Queued Sessions only The session is waiting for an agent to be available for its execution