OracIe Data Integrator

Architecture Overview
2
ntroduction
Oracle Data Integrator is built on seeral components all working together around a centralized
metadata repository. 1hese components - graphical modules, runtime agents and web-based interaces
- in conjunction with other adanced eatures make ODI a lightweight, legacy-ree, state o the art data
integration platorm. 1his technical brie describes the Oracle Data Integrator architecture in detail.

Architecture Overview
1he ODI architecture is organized around a modular repository, which is accessed in client-serer
mode by components such as the ODI Studio and execution Agents that are written entirely in Jaa.
1he architecture also includes a web-based application, the ODI Console, which enables users to
access inormation through a \eb interace and an extension or Oracle lusion Middleware Control
Console.

OD Studio
ODI Studio proides our graphical Naigators or managing ODI artiacts: Designer, Operator,
1opology and Security. ODI Studio oers an easy to use graphical user interace and can be installed
on arious platorms such as Microsot \indows, Linux and Mac OS.













Iigure J - ODI Studio Navigators connect to the repository
OracIe Data Integrator
Architecture Overview
3
1he ODI Studio Naigators are as ollows:
x Designer deines declaratie rules or data transormation and data integrity. All project
deelopment takes place in this module, this is where database and application metadata are
imported and deined. 1he Designer module uses metadata and rules to generate data
integration scenarios or load plans or production. 1his is the core module or deelopers and
metadata administrators.
x Operator manages and monitors data integration processes in production. It is designed or
operators and shows execution logs with error counts, the number o rows processed,
execution statistics, the actual code that is executed, and so on. At design time, deelopers can
also use the Operator module or debugging purposes.
x 1opology deines the physical and logical architecture o the inrastructure. 1he
inrastructure or projects administrators register serers, database schemas and catalogs, and
agents in the master repository through this module.
x Security manages user proiles and their priileges. Security can also assign access
authorization to objects and eatures. Security administrators generally use this module.
All modules store their inormation in the centralized repository.

Runtime Components: The Agents
At runtime, the Agent coordinates the execution o the ODI scenarios. It retriees the code stored in
the ODI repository, connects to the arious source and target systems and orchestrates the oerall data
integration process. 1here are two types o ODI Agents:
x 1he Standalone Agent can be installed on the source or target systems and requires a Jaa
Virtual Machine.
x 1he Java LL Agent is deployed on Oracle \ebLogic Serer and can beneit rom the
application serer layer eatures such as clustering or ligh Aailability requirements.
\ith the Lxtract-Load 1ransorm ,L-L1, architecture, the Agent rarely perorms any transormation.
It simply retriees code rom the ODI repository and then requests database serers, operating
systems, or scripting engines to execute that code. \hen the execution is completed, the Agent updates
the execution logs in the repository and then reports error messages and execution statistics. Users can
reiew the execution logs rom the Operator Naigator, the ODI Console \eb interace or Oracle
Iusion Middleware Control Console.

It is important to understand that although the Agent can act as a transormation engine, it is rarely
used or that purpose. Agents are installed at tactical locations in the inormation system to coordinate
the integration processes and leerage existing systems. 1hey are multithreaded, load-balanced,
lightweight components in this distributed integration architecture.

OracIe Data Integrator
Architecture Overview
4

Iigure 2 - Standalone Runtime Components

Repositories
1he Repository consists o a Master Repository and typically seeral Work Repositories. 1hese
repositories are sets o tables stored in relational database management systems such as Oracle,
Microsot SQL Serer, IBM DB2 and others. All objects that the ODI modules conigure, deelop, or
use are stored in one o these repositories, and are accessed in client-serer mode by the arious
components o the architecture.

1he Master Repository contains the security inormation ,user proiles and priileges,, the topology
inormation ,deinitions o technologies and serers,, and the source code or all ersions o all ODI
objects eer ersioned. 1he inormation contained in the Master Repository is maintained with
1opology and Security Naigators in ODI Studio as well as with ODI Console.

OracIe Data Integrator
Architecture Overview
5

Iigure 3 - Master repository and Work repositories

Project objects are stored in a Work Repository. Seeral \ork Repositories can coexist in the same
installation. 1his is useul or maintaining separate enironments or to relect a particular ersioning
liecycle-or example, deelopment, quality assurance, and production enironments.

A work repository stores inormation or

x Models ,i.e. metadata,-including datastores, columns, data integrity constraints, cross
reerences, data lineage and impact analysis
x Projects-including interaces, packages, procedures, olders, knowledge modules, and
ariables
x Runtime information-including scenarios, load plans, scheduling inormation, and logs
Users manage the content o a work repository with the Designer and Operator Naigators in ODI
Studio. 1he Agent at runtime also accesses work repositories. \hen a \ork Repository is used only to
store execution inormation ,typically or production purposes,, it is called an execution repository. An
execution repository is accessed at runtime with the Operator Naigator, ODI Console and by the
Agents. It is important to remember that each \ork Repository is always attached to one and only one
master repository.

OracIe Data Integrator
Architecture Overview
6
OD Console and Fusion Middleware Control Console
ODI Console is a Jaa Lnterprise Ldition ,Jaa LL, application that proides \eb access to
repositories. It allows users to browse Design-1ime objects, including projects, models, and execution
logs. 1hrough its comprehensie \eb interace, users can see low maps, trace the source o all data,
and een drill down to the ield leel to understand the transormations used to build the data. In
addition, end users can launch and monitor scenarios execution through ODI Console.

ODI Console can be installed on Oracle \ebLogic Serer and also proides administrators with the
ability to iew and edit 1opology objects such as Data Serers, Physical and Logical Schemas as well as
to manage their repositories.

Oracle Data Integrator oers an extension or the Oracle Lnterprise Manager Iusion Middleware
Control Console which allows end users to monitor their ODI components along with other lusion
Middleware modules rom a single administration console.

Iigure 4 - ODI Console and Lnterprise Manager Iusion Middleware Control Console

OracIe Data Integrator
Architecture Overview
7
Other Features
Oracle Data Integrator also includes the ollowing components and eatures:

x Knowledge Modules make it possible to quickly and easily integrate technologies, databases,
and applications. 1hey exist or a large range o platorms, including Oracle, Lxadata, Big
Data, Oracle Applications, Oracle GoldenGate, 1eradata, Netezza, SAP LRP, SAP B\ and
XML.
x 1he Changed Data Capture ,CDC, eature tracks changes in source systems and reduces the
olume o processed data by extracting only the changed data. ODI can use natie database
eatures to capture changes or Oracle GoldenGate.
x 1he integration with Oracle Business Intelligence Lnterprise Ldition proides business
users with report-to-source data lineage.
x Adanced Web Services capabilities oer best-in-class integration with Serice-Oriented
Architecture ,SOA, enironments
x 1he Load Balancing eature enables large olumes o data to be processed by automatically
balancing the workload between seeral Agents.
x Adanced Version Management proides an interace to manage, saeguard, and replicate
reisions o units o work, een in the largest deelopment enironments.

Conclusion
Oracle Data Integrator is a lightweight, legacy-ree, state-o-the-art data integration platorm. \ith its
superior perormance and lexible architecture, Oracle Data Integrator can be used in arious types o
projects such as Data \arehousing, SOA, Business Intelligence or Application Integration.