Exporting and Importing the Master Repository ExportImport the Topology and Security Settings

ExportingImporting 19-15

3. Click OK.

Field codes The first field of each record produced contains a code identifying the kind of information present on the row. You can customize these codes as necessary. ■ Oracle Data Integrator Information Record Code : Code used to identify rows that describe the current version of Oracle Data Integrator and the current user. This code is used in the first field of the record. ■ Master , Work, Agent, and Technology Record Code: Code for rows containing information about the master repository, the work repositories, the running agents, or the the data servers, their version, etc. Record Separator and Field Separator These separators define the characters used to separate records lines in the file, and fields within one record. Table 19–3 Cont. Technical Environment Export Parameters Properties Description 19-16 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator Part VI Part VI Running and Monitoring Integration Processes This part describes how to run and monitor integration processes. This part contains the following chapters: ■ Chapter 20, Running Integration Processes ■ Chapter 21, Monitoring Integration Processes ■ Chapter 22, Working with Oracle Data Integrator Console 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.