I think it’s time for a fresh look at Oracle Data Integrator 12c. What is ODI? How has it evolved over the years and where is it going? And, of course, how do you get started with Oracle Data Integrator? I plan to share what I love about ODI, how to get started building your first ODI project, and what makes Oracle Data Integrator 12c the premier ETL and data warehousing tool on the market. It’s time to get back to the basics! Presented at UTOUG Training Days 2017.

1. Oracle Data Integrator 12c: Getting Started
Michael Rainey | UTOUG Training Days 2017

2. • Michael Rainey - Technical Advisor
• Spreading the good word about gluent
products with the world
• Oracle Data Integration expertise
• Oracle ACE Director
• mRainey.co
• gluent.com
2
Introduction
we liberate enterprise data

3. About Gluent
We are long term Oracle Database &
Data Warehousing guys –
long history of performance & scaling
About 20 people in distributed teams in US & UK
The world is changing – we help customers
to get the best out of both worlds!
we liberate enterprise data
Gluent Data Platform enables all
applications to access all enterprise
data, at anytime, on demand, and
without any code migration or rewrites

4. • Gluent to be featured in the Startup
Showcase at Strata + Hadoop World
(Tomorrow!)
• Hadoop for Database Professionals
one-day training course (March 21st)
4
Quick announcements
gluent.com/event/hadoop-for-database-professionals-2

5. Why “Getting Started”

6. 6
Many conference presentations get too technical, too fast

7. What is ODI?

8. • E-LT (Extract, Load, Transform) vs ETL
• Heterogeneous sources and targets
• Built to integrate all data
• Flexibility
• Reusable code templates
(Knowledge Modules)
• Open API
• ODI will adapt to your data warehouse - and not the other way around
• Flow based mappings
• Logical vs Physical
8
What is ODI?

9. 9
Where did ODI come from?
Early 2000s: Sunopsis
formed
2006:
Oracle acquires Sunopsis.
2010:
Oracle Data Integrator
11g released. Oracle’s
first real update to ODI.
Late 2013:
Oracle Data Integrator
12c released, combining
ODI and OWB features.
2012:
ODI for Big Data
first released

10. 10
ODI 12c Architecture and Components
*image source: https://docs.oracle.com/middleware/1221/odi/concepts/img/architecture.png

11. 11
Typical ODI repository setup - the basics
Source: ateam-oracle.com/how-many-odi-master-repositories-should-we-have

12. 12
Typical ODI repository setup - full-blown environment
Source: ateam-oracle.com/how-many-odi-master-repositories-should-we-have

13. Installation and Configuration

14. • Know the different types of installs
• Standard - used for Standalone Agent or
on client machine (ODI Studio only)
• Enterprise - JEE Agent or Colocated Agent,
ODI Console, FMC plugin
14
Choose your installation type wisely

15. 15
Configuration is half the battle
CONFIGURATION

16. • ODI_HOME/odi/studio/odi.sh|exe
• Connect to existing repository
• If none exists, run RCU first
• Boom, you’re in!
16
ODI Studio Configuration

17. • ODI_HOME/oracle_common/common/bin/config.sh|exe
• Run the WebLogic Server configuration wizard
• Standalone Agent
• Create domain outside of ODI Oracle Home
• JEE Agent
• Add credentials mapping
• Create / configure admin server, nodemanager,
topology, etc.
17
Standalone or JEE Agent Configuration

18. 18
ODI Agent - how it works
ODI Agent
ODI repository
Source database
Target database
1. Execution request via http(s)
2. Agent communicates
with ODI repository to
generate code and gather
source/target connection
3. Agent passes code to
source/target databases
and updates repository
execution logs

19. Getting Started

20. • Data Server
• Connection to the data source
• Physical Schema
• Database schema
• Work schema
• Logical Schema
• Abstracts the physical connection/schema from the logical
• Development occurs against the Logical Schema
• Model
• Metadata object tied to Logical Schema
• Represents database schema, file directory, XML document, etc
• Datastore
• Logical representation of table, file, XML element, etc.
20
Topology, Contexts, Models, and Datastores - Oh my!
All of these objects must
be created and setup
prior to any mapping
development can occur.

21. • There’s another way to get started - quickly!
• New Model and Topology Objects wizard -
ODI 12.1.3
• In ODI 11g, the ODI QuickStart was a 10 step
checklist, where each step led to another
section in the documentation
21
Developer’s Quickstart

22. 22
Topology, Contexts, Models, and Datastores

23. 23
Logical Constraints on the metadata

24. 23
Logical Constraints on the metadata

25. 23
Logical Constraints on the metadata

26. 23
Logical Constraints on the metadata

27. Mappings and Knowledge Modules

28. 25
Mappings - Logical
Datastore
component
Join
component
Split output to
multiple target
tables
Mappings are built from
datastore and components
to logically form the ETL

29. 26
Mappings - Physical
Physical implementations of the
mappings are represented based
on location of the datastore.
Knowledge Modules are selected
to generate the code.

30. 26
Mappings - Physical
Physical implementations of the
mappings are represented based
on location of the datastore.
Knowledge Modules are selected
to generate the code.
ODI will adapt to your data warehouse
- and not the other way around

31. 27
Knowledge Modules - the secret sauce
*image source: Fusion Middleware Developing Knowledge Modules with Oracle Data Integrator

32. 27
Knowledge Modules - the secret sauce
*image source: Fusion Middleware Developing Knowledge Modules with Oracle Data Integrator

33. 27
Knowledge Modules - the secret sauce
*image source: Fusion Middleware Developing Knowledge Modules with Oracle Data Integrator

34. Orchestration
Packages and Load Plans

35. • Group like objects together
• Perform specialized tasks (looping, etc)
29
Packages

36. • Executes Scenarios (execution objects that are essentially compiled code)
• Steps can be run in parallel or serially
• If - then - else step can evaluate a variable to determine path
• Exception steps can be customized and executed on failure
30
Load Plans - the top level orchestration object

37. More flexibility
Procedures

38. • Reusable components for admin tasks
• DDL, file archive scripts, exception handling, etc
• Moving or transforming data, it probably should be a mapping
• Creating a complex, recurring task for data manipulation, probably a
Knowledge Module
32
Procedures for maintenance tasks and one-off functions
Images source: http://ritt.md/9E

39. • Integration with GoldenGate (change
data capture) and Enterprise Data
Quality (for…data quality)
• ODI for Big Data
• ODI Cloud Service
33
Other notable features

40. • Oracle Data Integrator is…
• an E-LT / data integration tool
• built to integrate all data
• flexible. ODI will adapt to your data warehouse - and not the other way around
• Choose your installation wisely and know configuration is more involved
• Many objects must be created prior to Mapping development
• Use the Developer’s Quickstart!
• Flow based mappings separate business logic from physical implementation
• Knowledge Modules are the “secret sauce” of ODI
• More info:
mRainey.co/odi12c-getting-started
ateam-oracle.com/?cat=64
blogs.oracle.com/dataintegration
34
Recap

41. 35
we liberate enterprise data
thank you!