Introduction :
Oracle Data
Integrator is built on several components all working together around a
centralized metadata repository. These components – graphical modules, runtime
agents and web-based interfaces – in conjunction with other advanced features
make ODI a lightweight, legacy-free, state of the art data integration
platform. This technical brief describes the Oracle Data Integrator
architecture in detail.
Architecture Overview
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.
ODI Studio
ODI Studio
provides four graphical Navigators for managing ODI artifacts: Designer,
Operator, Topology and Security. ODI Studio offers an easy to use graphical
user interface and can be installed on various platforms such as Microsoft
Windows, Linux and Mac OS.
The
ODI Studio Navigators are as follows:
•
Designer
defines declarative rules for data transformation and data integrity. All
project development
takes place in this module; this is where database and application metadata are imported and
defined. The Designer module uses metadata and rules to generate data integration
scenarios or load plans for production. This is the core module for developers
and metadata
administrators.
•
Operator
manages and monitors data integration processes in production. It is designed
for operators and
shows execution logs with error counts, the number of rows processed, execution
statistics, the actual code that is executed, and so on. At design time,
developers can also use the Operator module for debugging purposes.
•
Topology
defines the physical and logical architecture of the infrastructure. The infrastructure
or projects administrators register servers, database schemas and catalogs, and agents in the
master repository through this module.
• Security
manages user profiles and their privileges. Security can also assign access authorization
to objects and features. Security administrators generally use this module. All
modules store their information in the centralized repository.
Runtime
Components: The Agents
At runtime, the
Agent coordinates the execution of the ODI scenarios. It retrieves the code
stored in the ODI repository, connects to the various source and target systems
and orchestrates the overall data integration process. There are two types of
ODI Agents:
• The
Standalone Agent can be installed on the source or target systems and requires
a Java Virtual Machine.
•
The Java EE Agent is deployed on Oracle WebLogic Server and can benefit from the application server layer features such as
clustering for High Availability requirements.
With the
Extract-Load Transform (E-LT) architecture, the Agent rarely performs any
transformation. It simply retrieves code from the ODI repository and then
requests database servers, operating systems, or scripting engines to execute
that code. When the execution is completed, the Agent updates the execution
logs in the repository and then reports error messages and execution
statistics. Users can review the execution logs from the Operator Navigator,
the ODI Console Web interface or Oracle Fusion Middleware Control Console.
It is important to understand that although
the Agent can act as a transformation engine, it is rarely used for that
purpose. Agents are installed at tactical locations in the information system
to coordinate the integration processes and leverage existing systems. They are
multithreaded, load-balanced, lightweight components in this distributed
integration architecture.
Repositories
The Repository
consists of a Master Repository and typically several Work Repositories. These repositories
are sets of tables stored in relational database management systems such as
Oracle, Microsoft SQL Server, IBM DB2 and others. All objects that the ODI modules
configure, develop, or use are stored in one of these repositories, and are
accessed in client-server mode by the various components of the architecture.
The Master
Repository contains the security information (user profiles and privileges),
the topology information (definitions of technologies and servers), and the
source code for all versions of all ODI objects ever versioned. The information
contained in the Master Repository is maintained with Topology and Security
Navigators in ODI Studio as well as with ODI Console.
Project objects
are stored in a Work Repository. Several Work Repositories can coexist
in the same installation. This is useful for maintaining separate environments
or to reflect a particular versioning lifecycle—for example, development,
quality assurance, and production environments.
A
work repository stores information for
• Models (i.e.
metadata)—including datastores, columns, data integrity constraints, cross
references, data
lineage and impact analysis
• Projects—including
interfaces, packages, procedures, folders, knowledge modules, and
variables
• Runtime
information—including scenarios, load plans, scheduling information, and
logs
Users manage the
content of a work repository with the Designer and Operator Navigators in ODI Studio.
The Agent at runtime also accesses work repositories. When a Work Repository is
used only to store execution information (typically for production purposes),
it is called an execution repository. An execution repository is accessed at
runtime with the Operator Navigator, ODI Console and by the Agents. It is
important to remember that each Work Repository is always attached to one and
only one master repository.
ODI Console and
Fusion Middleware Control Console
ODI Console is a
Java Enterprise Edition (Java EE) application that provides Web access to
repositories. It
allows users to browse Design-Time objects, including projects, models, and
execution logs. Through its comprehensive Web interface, users can see flow
maps, trace the source of all data,and even drill down to the field level to
understand the transformations 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 WebLogic Server and also provides administrators with
the ability to view and edit Topology objects such as Data Servers, Physical
and Logical Schemas as well as to manage their repositories.
Oracle Data
Integrator offers an extension for the Oracle Enterprise Manager Fusion
Middleware Control Console which allows end users to monitor their ODI components
along with other Fusion Middleware modules from a single administration
console.
For Oracle online training classes please contact : training@virtualnuggets.com
No comments:
Post a Comment