My Oracle Support Banner

Best Practices For Setting Up ODI Architectures Using Multiple Distinct Master Repositories (Doc ID 577891.1)

Last updated on MAY 18, 2020

Applies to:

Oracle Data Integrator - Version 4.1.01.04 and later
Information in this document applies to any platform.

Purpose

Industrial best practices oblige the setting up of multiple IS environments in order to enforce strict and independent development, Q&A and production operations.

As a result, it is often required to set up multiple ODI (Oracle Data Integrator) environments resulting in the installation of multiple, and separate groups of ODI Repositories.

A direct consequence of such an approach is the setting up of multiple distinct Master Repositories, for example:

These two ODI environments will then be entirely independent of each other in both technical and logical terms.

However, frequent and programmable exchange is required from the development set up to the production environment in order for new developments to be installed and / or corrections applied to existing programs. Such operations will be based on the the Export - Import features of ODI.

Scope

This bulletin details:

  1. The consequences on internal IDs.  (Repositories, ODI Objects in general (Datastores, Models...?)
  2. What should be performed at the Topology level.
  3. How to synchronize Work Repositories.

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Scope
Details
 1. Object ID's
 ODI 12c
 ODI 11g and ODI 10g
 2. Topology
 2.1. Phase 0: full synchronization
 2.2. After Phase 0
 3. Synchronize the Work Repositories
 3.1. Work Synchronization WD1 > WH2
 3.2. Work Synchronization WH2 > WP2
 3.3. Work Synchronization WH2 > WD1
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.