Reviewing Successful Sessions Monitoring Executions Results

21-12 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator

3. Click OK.

The log data is exported into the specified location. Note that you can also automate the log data export using the OdiExportLog tool. Importing Log Data Importing log data allows you to import into your work repository log files that have been exported for archiving purposes. To import the log:

1. From the Operator Navigator toolbar menu select Connect Navigator Import

Log 2. In the Import of the log dialog:

1. Select the Import Mode. Note that sessions can only be imported in Synonym

Mode INSERT mode. Refer to Section 19.1.3, Import Modes for more information.

2. Select whether you want to import the files From a Folder or From a ZIP file.

3. Enter the file import folder or zip file.

4. Click OK.

The specified folder or ZIP file is imported into the work repository.

21.3.4 Managing Scenarios and Load Plans

You can also manage your executions in Operator Navigator by using scenarios or Load Plans. Before running a scenario, you need to generate it in Designer Navigator or import from a file. See Chapter 13, Working with Scenarios . Load Plans are also created using Designer Navigator, but can also be modified using Operator Navigator. See Chapter 14, Working with Load Plans for more information. Context Sessions execution Context. Leave the default All Contexts value, if you do not want to filter based on a context. Status The possible states are Done, Error, Queued, Running, Waiting, Warning and All States. Leave the default All States value, if you do not want to filter based on a given session state. User User who launched the session. Leave the default All Users value, if you do not want to filter based on a given user. Session Name Use as a wildcard. For example DWH matches any session whose name begins with DWH. Advanced options This set of options allow to parameterize the output file format. Character Set Encoding specified in the export file. Parameter encoding in the XML file header. ?xml version=1.0 encoding=ISO-8859-1? Java Character Set Java character set used to generate the file. Table 21–5 Cont. Log Export Parameters Properties Description Monitoring Integration Processes 21-13 Launching a scenario from Operator Navigator is covered in Section 20.3.1, Executing a Scenario from ODI Studio and how to run a Load Plan is described in Section 20.6, Executing a Load Plan .

21.3.4.1 Load Plan and Scenario Folders

In Operator Navigator, scenarios and Load Plans can be grouped into Load Plan and Scenario folders to facilitate organization. Load Plan and Scenario folders can contain other Load Plan and Scenario folders. To create a Load Plan and Scenario folder:

1. In Operator Navigator go to the Load Plans and Scenarios accordion.

2. From the Load Plans and Scenarios toolbar menu, select New Load Plan and

Scenario Folder .

3. On the Definition tab of the Load Plan and Scenario Folder editor enter a name for

your folder.

4. From the File menu, select Save.

You can now reorganize your scenarios and Load Plans. Drag and drop them into the Load Plan and Scenario folder.

21.3.4.2 Importing Load Plans, Scenarios, and Solutions in Production

A Load Plan or a scenario generated from Designer can be exported and then imported into a development or execution repository. This operation is used to deploy Load Plans and scenarios in a different repository, possibly in a different environment or site. Importing a Load Plan or scenario in a development repository is performed via Designer or Operator Navigator. With a execution repository, only Operator Navigator is available for this purpose. See Section 13.6, Importing Scenarios in Production for more information on how to import a scenario in production and Section 14.4.3.2, Importing Load Plans for more information on the Load Plan import. Similarly, a solution containing several scenarios can be imported to easily transfer and restore a group of scenarios at once. See Chapter 18, Working with Version Management for more information. Note that when connected to an execution repository, only scenarios may be restored from solutions.

21.3.5 Managing Schedules

A schedule is always attached to one scenario or one Load Plan. Schedules can be created in Operator Navigator. See Section 20.9, Scheduling Scenarios and Load Plans for more information. You can also import an already existing schedule along with a scenario or Load Plan import. See Section 13.6, Importing Scenarios in Production and Section 14.4.3, Exporting, Importing and Versioning Load Plans for more information. You can view the scheduled tasks of all your agents or you can view the scheduled tasks of one particular agent. See Section 20.9.1.3, Displaying the Schedule for more information.