This document summarizes the requirements, installation, and new features of Oracle Data Integrator 12c. It outlines that ODI 12c requires Java 7 and Oracle 11g or 12c databases. It also lists several new features including declarative flow-based design, reusable mappings, a step-by-step debugger, knowledge module architecture, and enhanced parallelism capabilities. The document provides high-level information about installing ODI 12c and introduces several new features but does not go into detail about any single topic.

1. REQUIREMENTS, INSTALLATION
AND NEW FEATURES OF ODI 12C
Canburak Tümer, 03/04/2014

2. 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

3. Agenda
• Requirements of ODI 12c
• Installation of ODI 12c
• New Features of ODI 12c
• Mappings
• Components
• Knowledge Modules

4. 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

5. Agenda
• Requirements of ODI 12c
• Installation of ODI 12c
• New Features of ODI 12c
• Mappings
• Components
• Knowledge Modules

6. Installation of ODI 12c

7. Agenda
• Requirements of ODI 12c
• Installation of ODI 12c
• New Features of ODI 12c
• Mappings
• Components
• Knowledge Modules

8. 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

9. Declarative Flow-Based Design
• Mappings instead of Interfaces
• Flow instead source and target datasets
• Components arrived

10. Reusable Mappings
• Generic input and output signatures
• Able to join, filter etc. (all operations of a mapping)
• Decrease development time

11. Multiple Target Support
• Using «Split» component
• Flow is divided depending on given expression

12. 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

13. Knowledge Module Architecture
• Component-style Knowledge Modules in addition to
Template-style Knowledge Modules
• Increases reusability

14. 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

15. 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.

16. Enhanced Parallelism
• In-mapping parallelism
• Loading sources in parallel to the staging area
• Can be modified in pyhsical view of a mapping

17. Q&A

18. Thanks