Anda di halaman 1dari 97

Oracle Data Integrator

Author-Priyanka
Payal Mehta


2
Document Control
Change Record









Reviewers



Date Author Version Change Reference
20-Oct-08 Priyanka 0.1 Initial Draft
Name Position
Anuj Mohan Sherry Project Manager
3
General Information
This document contains the course notes for ODI training.
Scope
- The scope of the training will introduce to ODI & how to use this tool for
Data Integration applications.

Training Prerequisites
- Knowledge of SQL.

Conventions
ODI Oracle Data Integrator

Notes
- Please refer to the notes attached to the slides for detailed explanation
and for Navigations

4
Course Agenda
ODI Architecture & Components
Creating Master & Work Repository
ODI Logical & Physical Schema
Creating ODI objects
Model
Project
Interfaces
Procedures
Packages
Creating Scenario ,Monitoring & Scheduling Scenario
Different Features of ODI
ODI Architecture & Components
Introduction
6
Oracle Data Integrator- An Introduction
Oracle data integrator is a member of the Oracle fusion middleware family of products. It
mainly addresses data integration needs in heterogeneous environments.

It is a comprehensive data integration platform that covers all data integration requirements
from high-volume, high-performance batches, to event-driven, trickle-feed integration
processes, to SOA-enabled data services

This software product is based on a unique E-LT architecture. Its main features are its
graphical modules and software agents that helps in checking data consistency and data flow.
It enhances user productivity modularized design approach


7
Technical capabilities

It deals with various technologies ( Hypersonic SQL, XML, Oracle) etc.

It reduces the documentation and programming phases by more than 90%.

Erroneous data can be corrected either on the source or on the target wherever it is
located in the information system.

It manages the isolation and recycling of erroneous data.

It stores the business rules independent of underlying technology. This helps in
modifying the interface without changing the transformation rules (mapping,
calculations, filters, aggregation, etc).

Rule maintenance is an isolated operation.


8
Architecture Overview

Oracle Data Integrator is built on several components all working together around
a centralized metadata repository.

Below are the four graphical modules that are used to create and manage ODI objects:

Designer is used to define data stores (tables, files, Web services, and so on), interfaces
(data mappings), and packages (sets of integration steps, including interfaces).
Topology Manager is used to create and manage connections to data sources and agents
and is usually restricted so that only administrators have access.
Operator is used to view and manage production integration jobs.
Security Manager manages users and their repository privileges.


Being Java-based, these applications can run in any Java environment, including Microsoft
Windows, Macintosh OS X, and Linux.
9
Architecture Overview (contd.)

Graphical modules connect the repository
Creation of Master and Work Repository
11
Creating Master Repository
To create a Master Repository
Click on Start Menu Programs Oracle Oracle Data Integrator Repository
Management Master Repository Creation.

12
Master Repository Creation (Contd.)
1
2
3
4
5
6
7
8
13
Master Repository Creation (Contd.)
14
To create Login for Master Repository
Click on Start Menu Programs Oracle Oracle Data Integrator
Topology Manager
Login Creation
15
Login Creation(Contd.)
1
1
2
3
4
5
6
7
8
9
16
Login to Topology Manager
1
17
1
2
3
Topology Manager
18
Creating Work Repository
1
2
19
Work Repository Creation (Contd.)
2
1
2
3
1
3
20
Work Repository Creation (Contd.)
1
2
ODI Logical & Physical Schema
22
Creating Context
1
23
1
2
Context Creation (Contd.)
24
Creating Data Server for File
25
1
2
Creating Data Server for File
26
Creating Data Server for File
1
27
Creating Data Server for File(Contd.)
1
2
3
1
28
Creating Physical Schema for File
1
1
2
3
29
Creating Physical Schema for File(Contd.)
2
3
1
3
30
Physical and Logical Architecture for File
31
Creating Data Server for Oracle
1
2
1
2
3
4
32
Creating Physical Schema for Oracle
1
2
3
1
2
1
2
3
33
Physical and Logical Architecture for Oracle
ODI Objects - Model
35

Oracle Data Integrator- Objects
Model
A model is a set of data stores corresponding to data structures contained in a physical
schema. Model is organized into a set of model folders basically to categorize each of the
technologies being used .
Datastore
Datastore are part of model which defines data structure. Each model should contain at
least one Datastore. We have different type of Datastore depending upon source e.g.
Flat File Datastore ,Oracle Table Datastore




36
Logical Structure (Models Tab)
XXCNV_TEST_SUPPLIER
XXCNV_TEST_SUPPLIER_FILE_M
XXCNV_TEST_SUPP_HEADER_FILE_DS
XXCNV_TEST_SUPP_SITES_FILE_DS
XXCNV_TEST_SUPP_BANK_FILE_DS
XXCNV_TEST_SUPPLIER_STG_M
XXCNV_TEST_SUPP_HEADER_STG_DS
XXCNV_SUPP_SITES_STG_DS
XXCNV_SUPP_BANK_STG_DS
37
2
1
3
Creating a Model Folder in Models tab
38
1
2
Creating a File Model
39
1
3 2
Creating a File Model (contd.)
40
1
2
Creating a File Model (contd.)
41
1
2
Creating a File Datastore
42
1
2
3
Creating a File Datastore (contd.)
43
1
2
3
Creating a File Datastore (contd.)
44
1
2
Creating a File Datastore (contd.)
45
2
Viewing Source File Data
1
46
Viewing Source File Data (contd.)
47
1
2
Creating a Oracle Model
48
1
Creating an Oracle Model
49
1
2
Creating a Oracle Model (contd.)
50
1
2
Creating Oracle Datastore
51
1
2
3
Creating Oracle Datastore (Contd.)
52
Creating Oracle Datastore (Contd.)
1
53
Creating Oracle Datastore (Contd.)
ODI Objects - Project
55

Oracle Data Integrator- Objects
Project
Package
The package is the largest unit of execution in Oracle Data Integrator. A
package is made up of a sequence of steps organized into an execution
diagram.
Interface
An interface consists of a set of rules that define the loading of a Datastore or
a temporary target structure from one or more source Data stores.
Procedure
A Specific Procedure is a reusable component that groups operations that do
not fit in the Interface framework - loading a target Datastore from one or
more sources
56
Logical Structure (Projects Tab)
XXCNV_TEST_SUPPLIER
XXCNV_TEST_SUPPLIER_PRJT
XXCNV_TEST_SUPP_HEADER_INT
XXCNV_SUPP_SITES_INT1
XXCNV_SUPP_SITES_INT2
XXCNV_SUPP_BANK_INT
57
Creating a Project Folder
58
1
Creating a Project Folder (contd.)
59
1
Creating a Project
60
Adding Knowledge Modules
61
Knowledge Modules (contd.)
62
Knowledge Modules (contd.)
63
Knowledge Modules (contd.)
ODI Objects - Interfaces
65
1
2
Creating an Interface
66
1
Creating an Interface (contd.)
67
1
Creating an Interface (contd.)
68
1
Creating an Interface (contd.)
69
1
Creating an Interface (contd.)
70
1
Creating an Interface (contd.)
71
2
1
Executing the Interface
72
1
Executing the Interface (contd.)
73
1
Viewing Result
74
1
2
3
Viewing Result (contd.)
75
2
1
Viewing Data
76
Viewing Data (contd.)
ODI Objects Procedure & Packages
78
1
2
Creating Procedure
79
Creating Procedure
1
2
80
1
2
Creating Procedure(Contd.)
81
1
3
2
4
Creating Procedure(Contd.)
82
Procedure: A reusable component that groups operations




83
Creating Package



1
2
84
Package: Largest unit of execution in ODI. Made up of a sequence of steps



Creating Scenario ,Monitoring & Scheduling
Scenario
86
Creating Scenario



1
2
1
87
Scheduling Scenario



88
Scheduling Scenario



Different Functionalities available with ODI
90
Column Mapping: Using a source or any calculation rule on source information
91
Mapping Rules: Using database functions or default values
92
Variable: A value stored in Oracle Data Integrator
93
Multi-table Joins(Equi/Cross/Outer)
94
Filters: Return functionally useful records. Tracking of error at any level is easy.
95
Objects can be exported then re-imported in one or more different contexts.




96
A new version can be generated to identify subsequent modifications




97
Thank You