Introduction – Oracle Data
Integrator (ODI)
Oracle purchased Sunopsis in October 2006 and
re-branded it as Oracle Data Integrator (ODI).
Oracle Data Integrator an application using the
database for set-based data integration.
Oracle Data Integrator provides a fully unified
solution for building, deploying, and managing complex data warehouses.
ODI is widely used data integration
software product, it provides a new declarative design approach to defining
data transformation and integration processes, resulting in faster and simpler
development and maintenance. Based on a unique “E-LT” architecture, Oracle Data
Integrator not only guarantees the highest level of performance possible for
the execution of data transformation and validation processes but is also the
most cost-effective solution available today.
ODI (Oracle Data Integrator) unifies of integration
by transforming large volumes of data efficiently, processing events in real
time through its advanced Changed Data Capture (CDC) with time based
automation.
Oracle Data Integrator is also based on a unique
E-LT (Extract - Load Transform) architecture which eliminates the need of an
ETL Server sitting between the sources and the target server
A) Why Oracle Data Integrator?
- ELT Architecture provides high performance.
- Active integration enables real time data
warehousing and operational data hubs.
- Declarative design improves developer productivity.
- Knowledge modules provide flexibility and
extensibility.
- ODI combines three style of data integration:
- Data based, event based and service based
ODI shortens implementation times with its declarative design approach.
B) Today’s Business Issues:
Now a day’s increasingly fast-paced
business environment, organizations need to use more specialized software
applications; they also need to ensure the coexistence of these applications on
heterogeneous hardware platforms and systems and guarantee the ability to share
data between applications and systems. Projects that implement these
integration requirements need to be delivered on-spec, on-time and on-budget.
C) ODI provides Unique Solutions:
The key reasons why more than 500
companies have chosen Oracle Data Integrator for their ETL needs:
·
JOB Dependency Matrix: The featured functionality by ODI to
design the complex functional architectures for required business logics.
Dependency of the object will be designed and it will be managed by ODI.
·
Faster and simpler development and maintenance: The declarative rules driven approach
to ETL greatly reduces the learning curve of the product and increases
developer productivity while facilitating ongoing maintenance. This approach
separates the definition of the processes from their actual implementation, and
separates the declarative rules (the “what”) from the data flows (the “how”).
·
ETL automation: ODI has capability to remove the manual
interventions in the ETL process, which may causes day to day business
activities. To improve the productivity and performance it may use real-time
data replication products.
·
Better execution performance: traditional ETL software is based on proprietary engines
that perform data transformations row by row, thus limiting performance. By
implementing E-LT architecture, based on your existing RDBMS engines and SQL,
you are capable of executing data transformations on the target server at a
set-based level, giving you much higher performance.
·
Platform Independence: Oracle Data Integrator supports all platforms, hardware and OSs
with the same software.
·
Data Connectivity: Oracle Data Integrator supports all RDBMSs including all leading
Data Warehousing platforms such as Teradata, IBM DB2, Netezza, Oracle, Sybase
IQ and numerous other technologies such as flat files, ERPs, LDAP, XML.
·
Cost-savings: the elimination of the ETL hub server and ETL engine reduces
both the initial hardware and software acquisition and maintenance costs. The
reduced learning curve and increased developer productivity significantly
reduce the overall labor costs of the project, as well as the cost of ongoing
enhancements.
D) ODI Architecture:
The ODI
architecture is organized around a modular repository, which is accessed in
client-server mode by components such as the ODI Studio and execution Agents
that are written entirely in Java.
The architecture
also includes a web-based application, the ODI Console, which enables users to
access information through a Web interface and an extension for Oracle Fusion
Middleware Control Console.
Fig 1: Oracle Data Integrator Architecture
E) Traditional ETL Vs E-LT Process
1) Extract: Extracting the data from various sources.
2) Load: Loading the
data into the destinations target.
3) Transform: Transforming
data according to a set of business rules
In response to the issues raised by ETL
architectures, a new architecture has emerged, which in many ways incorporates
the best aspects of manual coding and automated code-generation approaches.
Known as “E-LT”, this new approach changes
where and how data transformation takes place, and leverages existing developer
skills, RDBMS engines and server hardware to the greatest extent possible.
In essence, E-LT moves the data transformation
step to the target
RDBMS, changing the order of operations to
