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

Last updated on NOVEMBER 06, 2023

Applies to:

Oracle Data Integrator - Version 4.1.01.04 and later
Oracle Data Integrator on Marketplace - Version 1.0.2 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 Oracle Data Integrator (ODI) 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:

in a development set up: a Master and one or more attached Work Repositories;
in a production set up: a Master with its attached Work Repositories.

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.

The article applies to the current 12C release.

Scope

This bulletin details:

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