Skip to main content

Oracle

Types of Oracle Data Integrator (ODI) Repositories

As I have been putting together my ODI blog posts I wanted to put together another post discussing the different types of ODI repositories, “Master and Work.”  But the repository I want to touch upon the most in the “Work” repository and the different options the ODI work repository has to offer.   Now before I get into my post let me give you the Oracle definition of the two types of repositories within ODI.

 

  • Types of Oracle Data Integrator (ODI) RepositoriesMaster Repository: This is a data structure containing information on the topology of the company’s IT resources, on security and on version management of projects and data models. This repository is stored on a relational database accessible in client/server mode from the different Oracle Data Integrator modules. In general, you need only one master repository. However, it may be necessary to create several master repositories in one of the following cases:

o   Project construction over several sites not linked by a high-speed network (off-site development, for example).

o   Necessity to clearly separate the interfaces’ operating environments (development, test, production), including on the database containing the master repository. This may be the case if these environments are on several sites.

 

  • Work Repository: This is a data structure containing information on data models, projects, and their use. This repository is stored on a relational database accessible in client/server mode from the different Oracle Data Integrator modules. Several work repositories can be created with several master repositories if necessary. However, a work repository can be linked with only one master repository for version management purposes.[1]

Now that you have a better understanding of the two types of ODI repositories, I wanted to dive more into the work repository.  Now regardless of your environment DEV, TEST or PROD you will need a master repository.  But the work repository can be setup in two different ways.  Either you can have a ODI Development Work Repository (DWR) or a ODI Execution Work Repository (EWR).

Oracle - Guide to Oracle Cloud: 5 Steps to Ensure a Successful Move to the Cloud
Guide to Oracle Cloud: 5 Steps to Ensure a Successful Move to the Cloud

Explore key considerations, integrating the cloud with legacy applications and challenges of current cloud implementations.

Get the Guide

Screen Shot 2014-08-31 at 3.05.32 AM

Now the ODI DWR repository biggest difference from your ODI EWR repository will have your ODI Designer tab in which you will see your projects tab (packages, interfaces, procedures, variables, sequences, user functions, knowledge modules, markers), models tab, load plans and scenarios tab, global objects tab, solutions tab, and etc.  Basically to put it simply the ODI DWR repository is setup in which developers are allowed to develop their ODI E-LT components.

Screen Shot 2014-08-31 at 3.06.20 AM

 

The ODI EWR repository is execution only and used mainly for your production environment.  Here you cannot modify your ODI code and you can only migrate your ODI scenarios and load plans in which you can execute.

Screen Shot 2014-08-31 at 3.06.53 AM

 

Hopefully this short post has shed some better understanding on the different types of ODI repositories.  For more information on ODI repositories visit, Oracle’s Introduction to Oracle Data Integrator Repositories.

 

References: 

[1] http://docs.oracle.com/cd/E21764_01/integrate.1111/e12643/admin_reps.htm

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Chris Evans

Chris Evans has extensive management, technical, consulting and customer service skills. He provides hands-on expertise in project leadership and management, assessments, methodologies, data modeling, database design, meta data, systems analysis, and development. He has worked with multiple platforms, and his experience spans a wide range of operational and data warehouse environments. In addition to his BI background, Chris Evans has a experience in marketing strategy for major consumer brands.

More from this Author

Categories
Follow Us