Attaching and Deleting a Work Repository Erasing a Work Repository Renumbering Repositories

Administering the Oracle Data Integrator Repositories 3-11

7. In the Renumbering the Repository - Step 4 dialog click Yes.

8. The work repository and all the objects attached to it are renumbered. Renumbering a Master Repository 1. In the Topology Navigator, go to the Repositories panel. 2. Expand the Master Repositories node and right-click the master repository you want to renumber. 3. Select Renumber...

4. In the Renumbering the Repository - Step 1 dialog click Yes.

5. In the Renumbering the Repository - Step 2 dialog enter a new and unique ID for the master repository and click OK. 6. The master repository and all the details stored in it such as topology, security, and version management details are renumbered.

3.8.4 Tuning the Repository

Concurrent connections to the repository database may be controlled and limited by the database engine where the repository is stored. On Oracle the property limiting the number of connections is max_processes. When running a large number of parallel executions, you may need to tune the database to increase the maximum number of connections allowed to the repository database. The number of connections required depends on the number of sessions running the connection: ■ Each session execution requires two database connections one to the master, one to the work repository for the duration of execution, and also a third database connection is required for a security check for a very short period when the session begins. ■ For non-Oracle databases, each Load Plan step consumes an additional connection as a lock while the Load Plan is being executed. 3-12 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator 4 Setting-up the Topology 4-1 4 Setting-up the Topology This chapter describes how to set up the topology in Oracle Data Integrator. An overview of Oracle Data Integrator topology concepts and components is provided. This chapter contains these sections: ■ Section 4.1, Introduction to the Oracle Data Integrator Topology ■ Section 4.2, Setting Up the Topology ■ Section 4.3, Managing Agents

4.1 Introduction to the Oracle Data Integrator Topology

The Oracle Data Integrator Topology is the physical and logical representation of the Oracle Data Integrator architecture and components. This section contains these topics: ■ Section 4.1.1, Physical Architecture ■ Section 4.1.2, Contexts ■ Section 4.1.3, Logical Architecture ■ Section 4.1.4, Agents ■ Section 4.1.5, Languages ■ Section 4.1.6, Repositories

4.1.1 Physical Architecture

The physical architecture defines the different elements of the information system, as well as their characteristics taken into account by Oracle Data Integrator. Each type of database Oracle, DB2, etc., file format XML, Flat File, or application software is represented in Oracle Data Integrator by a technology. A technology handles formatted data. Therefore, each technology is associated with one or more data types that allow Oracle Data Integrator to generate data handling scripts. The physical components that store and expose structured data are defined as data servers. A data server is always linked to a single technology. A data server stores information according to a specific technical logic which is declared into physical schemas attached to this data server. Every database server, JMS message file, group of flat files, and so forth, that is used in Oracle Data Integrator, must be declared as a data server. Every schema, database, JMS Topic, etc., used in Oracle Data Integrator, must be declared as a physical schema.