REQUIREMENTS, INSTALLATION

AND NEW FEATURES OF ODI 12C

Canburak Tmer, 03/04/2014
About me
@canburakTBlog www.canburaktumer.com/blog linkedin.com/in/canburaktumer
Ege University, CompEng, 2012
ITU, MSc CompEng, cont.
Intern ETL Developer at Turkcell Technology
Part-time ETL Developer at Turkcell Technology
Associate Consultant at Oracle Consultancy BI&DW
BI&DW Specialist at MAKEIT Software & Consulting
Agenda
Requirements of ODI 12c
Installation of ODI 12c
New Features of ODI 12c
Mappings
Components
Knowledge Modules
Requirements of ODI 12c
Java 7
Oracle 11g 11.1.0.7.0 +
Oracle 11g R2 11.2.0.3.0 +
Oracle 12c 12.1.0.1.0 +
http://bit.ly/PbfRdK
Agenda
Requirements of ODI 12c
Installation of ODI 12c
New Features of ODI 12c
Mappings
Components
Knowledge Modules
Installation of ODI 12c
Agenda
Requirements of ODI 12c
Installation of ODI 12c
New Features of ODI 12c
Mappings
Components
Knowledge Modules
New Features of ODI 12c
Declarative Flow-Based Design
Reusable Mappings
Multiple Target Support
Step-by-step debugger
Knowledge Module Architecture
OWB Integration
OGG Integration
Enhanced Parallelism
Declarative Flow-Based Design
Mappings instead of Interfaces
Flow instead source and target datasets
Components arrived
Reusable Mappings
Generic input and output signatures
Able to join, filter etc. (all operations of a mapping)
Decrease development time
Multiple Target Support
Using Split component
Flow is divided depending on given expression
Step by step debugger
Mappings, procedures, packages, scenarios
Breakpoints can be set
Variable values can be seen or edited
Data in intermediate steps can be queried
Knowledge Module Architecture
Component-style Knowledge Modules in addition to
Template-style Knowledge Modules
Increases reusability
OWB Integration
Able to run OWB jobs (OdiStartOwbJob tool)
Able to see running OWB jobs through operator, console,
enterprise manager
OWB Repository can be set as a Data Server in Topology
OWB to ODI Migration Utility to import OWB Mappings
OGG Integration
OGG source and target can be configured as Data Server
in Topology. Brings flexibility of seperating physical and
logical schemas and enable context usage.
OGG Extract and replicate parameters can be set by
pyhsical schema, no need to change parameter files
anymore.
Using JAgent technology, OGG parameter files can be
automatically deployed and run on OGG source and
target servers.
Enhanced Parallelism
In-mapping parallelism
Loading sources in parallel to the staging area
Can be modified in pyhsical view of a mapping
Q&A
Thanks