ETL/ELT
ODI components
Studio (DOTS) - It's development IDE
Designer Navigator
Operator Navigator
Topology Navigator - maintain connection between source and targets
Security Navigator
Agent
COnsole
Repositories
Topology - For creating connections
Designer
Object --> We create object to move data from source to target. Interface are
grouped together which is called package
11g- Interface
12c - mapping
Operator --> Contain infor on Whether interface was failed or successful. Failure
reason , time taken
Security - Admin purpose, creating user, role, grants
Repositories - where the objects are stored
connections details
sessions are stored
paswword, user info , profiles, roles are stored
2 type - Master - Security, Topology
Work - Designer, Operator
-------------------
Declarative design
-------------------
Models
Scenerio
Version
Projects- FOleder-> mapping--> procedure
-------
Work repo --> 2 type-> Execution repo (Production purpose) and Development Repo
(Dev+test purpose)
Designer Navigator- used to design data integrity checks and build transformations
Operator Navigator- is the production management and monitoring tool. It's designed
for IT production operators. Through operator navigator, we can manage
mapping executions in this sessions as well as the
scenerios in prod
Topology Navigator- is ussed to manage the info on system's physical and logical
architecture. Through topology operator, we can manage the topology of our
information system, the technologies and their data type
TOPOLOGY -- the ODI topology is a physical and logical representation of the Oracle
data integrator architecture and components.
DataServers - The physical components that stores and expose structured data are
defined as DataServers and connects to a single tecjnology.
example - Oracle DB
-----------
create One mater repo user / schema
create One work repo user / schema
create One source schema / user
create One target schema / user
create One login user , which is available in snp_user
create 2 physical scheme 1 for source+work schema and 1 for target+work schema
(work schema can be a different schema or we can user source or target schema as
well)
Topology--> Physical Architecture --> create data source--> Under data source
craete physical for source and target
There can be n number of physical schema based on the technlogy used as source
(oracle , excel, MSSQL, MySQL)
Like physical schema , we nned to craete logical schema as well for source and
Target. (Odi_Target + Odi_Source).
These Physical schema and logical schema are connected by CONTEXTS. There should be
one context for each environment (1 for Dev,1 for test ,1 for prod).
Multiple Context can have same name but code shoud be different.
ODI agents - ODI agents orchestrate the execution of jobs.
Craete models -
--------------
Models are the objects that will store the metadata in ODI. Meta data of data
source / target.
Model works on top of ligical schema
Reverse Engineer
RKM(Reverse Engineering Module ) - 2 types - Standard and customized. Customized
interacts with system tables.
Standard use JDBC connectivity to retrieve data tables.
Create model folder then cfreate model and map logical schema. To populate table go
to reverse engineering.
We can click on Reverse Engineer (to import / populate all tables) or Selective
reverse engineering (to import specific tables).
Mask option is also available to filter.
Customized model requires knowledge module to map and When we craete a new project,
6 KMs are craeted by default.
We can use standard if JDBC connectivity is available. If not, we can use
customized
Knowledge module are sequence of steps. Whcih can be imported from C:\Oracle\
Middleware\Oracle_Home\odi\sdk\xml-reference
Reverse- Engineering
Loading
Check
Integration
Journalizing
Service
DataServers vs schema
Requirements--> Select the technlogy like Oracle then
create data servers
create physical schema
to choose tables, views , synonyms
create source and
targetc
Physical architecture contains dataservers
Logical archetecture contains logical schema
Split component --> 1 to Many
Set component --> Many to 1
