<Insert Picture Here>

Oracle Data Integrator Demo

Balwant Singh
 Objectives

• Introduction

• Architectural Overview

• Components of ODI
Prerequisite

• Basic knowledge of ELT data processing

• Working knowledge of SQL
Introduction

 Acquired from SUNOPSIS

 Widely used data integration software product

 Based on a unique “E-LT” architecture

 ODI is built around a modular repository

architecture
ODI Architecture
 ODI Components
• Components of ODI are
• Topology Manager
• Designer
• Security Manager
• Operator
• Agent
• Scheduler
• Metadata Navigator

• Repository
• Master Repository
• Work Repository & Execution Repository
 ODI Components
• Designer – To reverse engineer, develop projects, generate scenario

• Topology Manager – Define the infrastructure of information system,agent

• Operator – Operate production, monitor sessions, monitor load plan,log level

information,

• Security Manager – Manages user privileges, permissions, create users,

create profile

• Metadata Navigator – Web access to repository. URL , master . Work,

• Agent – issues commands to source, target, two types agent- Standalone-

JAVEj2ee. It orchestrate the excution

• Scheduler – Schedules a interface, scenario, Schedule the jobs, with the help
Agent.
Repositories
 Master Repository

• There is usually only one master repository that stores

the following information:
• Security information including users, profiles and rights
for the ODI platform
• Topology information including technologies, server
definitions, schemas, contexts, languages and so forth.
• Versioned and archived objects.
 Work Repository

• The work repository is the one that contains actual developed

objects. A Work Repository stores information for:
• Models, including schema definition, datastores structures and
metadata, fields and columns definitions, data quality
constraints, cross references, data lineage and so forth.
• Projects, including business rules, packages, procedures,
folders, Knowledge Modules, variables and so forth.
• Scenario execution, including scenarios, scheduling information
and logs.
• When the Work Repository contains only the execution
information (typically for production purposes), it is then called an
Execution Repository.
 Agents
• This is run time component which connects to
repository and executes the code . Agents also
records execution time, logging, and messages for
each execution. Agents are of two type
• a) Standalone Agents
• b) Java EE agents.
• Both type of agents are mulTI threaded java programs
and can be configured for high availability. Java EE
agents require WebLogic Server where as
Standalone Agents run in their own JVM container (no
application server is required for standalone agent)
Knowledge Module