Introduction ODI

Oracle Data Integrator is a data Integration Platform

Based on ELT Architecture (Extract, Load,Transform).

Platform Independent. Supports all Platform, Hardware and OS.

Supports all RDBMS Like Oracle, Exadata and Teradata.

Support for Flat Files, XML and ERPs.

No need for Separate ETL Server.

ODI Component Architecture
Repositories
 Master Repository
Security information like Users, Profiles, and
rights of the ODI platform
Topology information like Technologies, Server
definitions, Schemas etc.,
Versioned and Archived Objects
 Work Repository
Models, Schema definition, Metadata, data
quality constraints etc.,
Projects, Business Rules, Packages,
Procedures, Folders etc.,
Scenarios, Scheduling information and logs.
 ODI STUDIO
Used to access the repositories by the admins,
developers and Operators.
Fusion Client platform based User interface.
To Administer the infrastructure(Security and
Topology)
Developing Projects.
Scheduling , Operating and Monitoring
executions.
ODI STUDIO - Navigators
 Designer Navigator
Develop Projects
Release Scenarios
Core Module for Developers and Metadata Administrators
 Operator Navigator
Monitor ODI in Production
Displays execution logs,rows processed, error counts etc.,
 Topology Navigator
Defines the Physical and Logical Architecture of the infrastructure.
Administrators register servers , database schemas, and agents in the Master Repository.
 Security Navigator
Manages user profiles, roles, and Privileges
Assign access authorization to objects and features.
 Agent
The Agent coordinate the execution of the ODI
sessions.
Agent retrieve code from the ODI repository
and requests db servers/OS/scripting engines
to execute the code.
When execution completes , updates the
execution logs in the repository and reports
the error messages and execution statistics.
 Types of Agents
Standalone Agents can be installed on the source or target systems and
require a Java Virtual Machine.
Colocated Standalone Agents can be installed on the source or target
systems as well. They can be managed using Oracle Enterprise Manager
and must be configured with an Oracle WebLogic domain. Colocated
Standalone Agents can run on a separate machine from the Oracle
WebLogic Administration Server.
Java Enterprise Edition (Java EE) Agents are deployed on Oracle WebLogic
Server and can benefit from the application server layer features such as
clustering for High Availability requirements. Java EE Agents can be
managed using Oracle Enterprise Manager.
Knowledge Modules