ORepositories

Repositories

The central component of the architecture is the Oracle Data Integrator Repository. It stores configuration information about the IT infrastructure, metadata of all applications, projects, scenarios, and the execution logs. Many instances of the repository can coexist in the IT infrastructure. The architecture of the repository is designed to allow several separated environments that exchange metadata and scenarios (for example: Development, Test, Maintenance and Production environments). In the figure above, two repositories are represented: one for the development environment, and another one for the production environment. The repository also acts as a version control system where objects are archived and assigned a version number. The Oracle Data Integrator Repository can be installed on an OLTP relational database.
The Oracle Data Integrator Repository is composed of a master repository and several Work Repositories. Objects developed or configured through the user interfaces are stored in one of these repository types.
There is usually only one master repository that stores the following information:

• Security information including users, profiles and rights for the ODI platform
  
• Topology information including technologies, server definitions, schemas, contexts, languages etc.
  
• Versioned and archived objects.
  

The Work Repository is the one that contains actual developed objects. Several work repositories may coexist in the same ODI installation (for example, to have separate environments or to match a particular versioning life cycle). A Work Repository stores information for:

• Models, including schema definition, datastores structures and metadata, fields and columns definitions, data quality constraints, cross references, data lineage etc.
  
• Projects, including business rules, packages, procedures, folders, Knowledge Modules, variables etc.
  
• Scenario execution, including scenarios, scheduling information and logs.
  

When the Work Repository contains only the execution information (typically for production purposes), it is then called an Execution Repository.