Saturday, 7 March 2015

Types of Work repositories

odi-work-repository-types

While creating the work repository under a master repository we come across this situation, to choose the type of repository. There are two types of work repositories possible as explained below.
  1. Development: This type of repository allows management of design-time objects such as data models and projects (including interfaces, procedures, etc). A development repository includes also the run-time objects (scenarios and sessions). This type of repository is suitable for development environments. 
  2. Execution: This type of repository only includes run-time objects (scenarios, schedules and sessions). It allows launching and monitoring of data integration jobs in Operator Navigator. Such a repository cannot contain any design-time artifacts. Designer Navigator cannot be used with it. An execution repository is suitable for production environments.

Oracle Data Integrator repositories

There are two types of repositories:
  1.  Master repositories
  2. Work repositories
These repositories are data bases stored in RDBMS. Usually there will be one master repository and several work repositories attached to the master repository. 

Master repository: Master repository stores the information defined by topology manager and security navigator. Master Repository stores the following information 
  1. Security Information i.e. information about users, profiles and access privileges 
  2. Topology information including technologies, Data servers, physical and logical schemas , contexts, agents and languages
  3. ODI versions and objects 
Work Repository: Work repository should always attached to a master repository. 
Work repository stores the information defined in Designer navigator . It stores the following information: 
  1. Data models: metadata, constraints, references, data lineage, etc 
  2. Projects: interfaces, packages, procedures, folders, knowledge modules, etc 
  3. Scenarios, scheduling information and logs Work repository contents manged by designer and operator.