In this blog we will learn about Oracle Data Integrator Repositories.
You can refer this blog for ODI 11g Installation & Setup on Windows OS.
Suppose you are just done with the ODI installation on your machine:
Now you are going to use the ODI Studio to develops, operate & administrate some ELT project work. But you need some space/location to start working & to save your all work. Basically you need ODI repository to store the information you are going to develop, configure or used by the ODI.
There are two types of ODI repositories: Master & Work Repository
- Objects developed, configured, operated/used by the ODI stored in one of these two types of repositories.
- Repositories are accessed in client/server mode by various components of the ODI architecture.
- Master Repository is usually associated with multiple Work Repositories.
- Each Work repository can associate with only one Master Repository.
- Work repository can either be Development Work Repository or Execution Work repository. (We will discuss this point later in this blog)
Refer this YouTube video to setup Master & Work Repositories in ODI 11g using Oracle.
Master Repositories are used to store:
- ODI Connection Information: JDBC URLs, LDAP information, user names and passwords for source/target connections.
- ODI Security Information: ODI users names and passwords, ODI users privileges and profiles information, if security is handled by ODI.
- Version Information: When a new version of an object is created in the ODI, that information is saved in the Master Repository.
Information contained in the Master Repository is maintained with the Topology Navigator and the Security Navigator in ODI Studio.
- Data contained in master repository is mostly static data and will be going through minimum changes, whenever any topology or security information added/updated.
- ODI components access the Master Repository, whenever they need the topology and security information data stored in it.
Work Repositories are used to store:
- Project Information: Folders/Sub-folders, packages, interface, procedure, variables, sequences, functions, knowledge module etc.
- Models: Data Store structures and metadata, fields, columns, constraints etc.
- Load Plans & Scenarios: Load plans information & scenarios.
- Operations: Execution details, scheduling information, and logs.
The contents of a Work Repository are managed by using Designer and Operator. They are also accessed by the agent at run time.
When a Work Repository is used only to store execution, operations logs information (typically for production environment), it is called an execution work repository. Designer Navigator is disabled in this execution repository.
Work repository consists of two sub-types: Development Work Repository & Execution Work repository.
Development Work Repository:
- Repository which contains all the objects which are used for developing the development project i.e. packages, interface, procedure, variables, sequences, load plans, data stores etc.
- Designer Navigator & Operator Navigator both are available for Development Work Repository.
- Usually, used for development projects.
Execution Work Repository:
- Repository which stores only the scenarios (executable files) & execution information, no source code & designer information available here.
- Usually, used for production and test environments to make sure that source code will not be modified in a live environment.
- Operator Navigator is available, but Designer Navigator is restricted for Execution Work Repository.
Checkout this blog for understanding of relationship between ODI Master & Work Repository.
Refer this YouTube video to Install ODI 11g on Windows OS.
Happy Learning! Your feedback would be appreciated!