Accessing the Web Service from a Command Line

21 Monitoring Integration Processes 21-1 21 Monitoring Integration Processes This chapter describes how to manage your development executions in Operator Navigator. An overview of the Operator Navigator’s user interface is provided. This chapter includes the following sections: ■ Section 21.1, Introduction to Monitoring ■ Section 21.2, Monitoring Executions Results ■ Section 21.3, Managing your Executions

21.1 Introduction to Monitoring

Monitoring your development executions consists of viewing the execution results and managing the development executions when the executions are successful or in error. This section provides an introduction to the monitoring features in Oracle Data Integrator. How to work with your execution results is covered in Section 21.2, Monitoring Executions Results . How to manage your development executions is covered in Section 21.3, Managing your Executions .

21.1.1 Introduction to Operator Navigator

Through Operator Navigator, you can view your execution results and manage your development executions in the sessions, as well as the scenarios and Load Plans in production. Operator Navigator stores this information in a work repository, while using the topology defined in the master repository. Operator Navigator displays the objects available to the current user in six accordions: ■ Session List displays all sessions organized per date, physical agent, status, keywords, and so forth ■ Hierarchical Sessions displays the execution sessions also organized in a hierarchy with their child sessions ■ Load Plan Executions displays the Load Plan Runs of the Load Plan instances ■ Scheduling displays the list of physical agents and schedules ■ Load Plans and Scenarios displays the list of scenarios and Load Plans available ■ Solutions displays the list of solutions 21-2 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator The Operator Navigator Toolbar Menu You can perform the main monitoring tasks via the Operator Navigator Toolbar menu. The Operator Navigator toolbar menu provides access to the features detailed in Table 21–1 .

21.1.2 Scenarios

A scenario is designed to put a source component interface, package, procedure, variable into production. A scenario results from the generation of code SQL, shell, etc. for this component. When a scenario is executed, it creates a Session. Scenarios 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.3 Sessions

In Oracle Data Integrator, an execution results in a Session. Sessions are viewed and managed in Operator Navigator. A session is an execution of a scenario, an interface, a package or a procedure, and so forth undertaken by an execution agent. A session is made up of steps which are themselves made up of tasks. A step is the unit of execution found between a task and a session. It corresponds to a step in a package or in a scenario. When executing an interface or a single variable, for example, the resulting session has only one step. Table 21–1 Operator Navigator Toolbar Menu Items Icon Menu Item Description Refresh Click Refresh to refresh the trees in the Operator Navigator accordions. Filter Filter activated Click Filter to define the filters for the sessions to display in Operator Navigator. Auto Refresh Click Auto Refresh to refresh automatically the trees in the Operator Navigator accordions. Connect Navigator Click Connect Navigator to access the Operator Navigator toolbar menu. Through the Operator Navigator toolbar menu you can: ■ Import a scenario ■ Import and export the log ■ Perform multiple exports ■ Purge the log ■ Display the scheduling information ■ Clean stale sessions 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: