Sie sind auf Seite 1von 23

Oracle Data Integrator 11g Bootcamp

Lesson 2 : Topologies

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Agenda
Start to use the Topology navigator within ODI 11g
Understand ODI physical architectures
Learn how to create data servers
Create physical schemas
Create logical schemas, and link them to physical ones through contexts

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Topologies
The physical and logical representation of the ODI components and architecture
Contains connections to data servers, repositories, agents and contexts
Defined using the Topology navigator within ODI Studio

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Technologies
Types of data source that can be connected
to by ODI
Databases, files, application software,
web services
Typically accessed through JDBC drivers
Can be extended to cover non-shipped
data sources

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Creating Data Sources in ODI 11g : Overview


Data sources are required in order to connect mappings to your data
Defined in the Topology Navigator
A typical data source combines three ODI objects
A Data Server connection to a physical database
A Physical Schema connecting to a particular database account/schema
A Logical Schema, through a Context, that connects to a physical schema
Allows connections to be set up that keep
a common name (logical schema) that can
point to different physical sources
depending on environment (prod, test etc)

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Data Servers
Connections through to physical data sources
Oracle database, directory of files, XML file, application server
For databases, defines the login that will be used to connect
Can subsequently be used to connect to multiple schemas
Made up of a name, credentials, and either JDBC or JNDI connection details

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Creating a Data Server Part 1 : Select Technology


Select technology on which the data server is based
Right-click and select New Data Server

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Creating a Data Server Part 2 : Enter Name and Connections


Enter name for data server
Enter connection details (username and password) if appropriate
Leave blank for files, XML etc

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Creating a Data Server Connection to a JAX-WS Server


For web service (JAX-WS) connections, enter Base URL for published services
Also enter name for directory for saving web services into

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Creating a Data Server Part 3 : Enter JDBC Connection Details


Select JDBC Driver from list
Select JDBC URL template from list
Use Test Connection button to test using default agent

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Logical Schemas
The logical name (or alias ) for the schemas you will work with
Combined with a Context at run time, will point to a particular physical schema on
a particular data server
Allows us to create interfaces that work with logical schema names, and will not
need re-writing as we move between environments

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Creating a Logical Schema Step 1 : Select Technology


Navigate to the Logical Architecture panel in the Topology Navigator
Select technology, right-click and select New Logical Schema

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Creating a Logical Schema Step 2 : Enter Name


Type in a name for the logical schema
This will be the alias that you ll use for interfaces, models etc
We will define the context and physical schema next, to link this logical schema to
an actual database schema

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Physical Schemas
The actual database schemas (within Data Servers) that contain the data
Two schemas are defined for each physical schema
The Schema (contains the data)
The Work Schema (where temporary tables are created)
If schema and work schema differs, make sure credentials used in associated
data server can create tables within each schema

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Work Tables and Default Schemas


ODI creates temporary tables and other structures when executing mappings
E$ : Errors
C$ : Loading (extracts)
I$ : Integration (data loading)
J$, JV$, T$ : Journalizing (CDC)
These will go in the designated work schema
If you have more than one physical schema defined for a data store, the Default
work schema will be used

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Contexts
Used for defining environments, allows a logical schema to map to more than one
physical schema
Default context is Global , can create others

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Creating a Physical Schema Step 1 : Select Data Server


Navigate back to the Physical Architecture panel in the Topology Navigator
Right-click on the data server in which you will create the physical schema

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Creating a Physical Schema Step 2 : Select Schemas from List


Select schema and work schema from the list visible via the data server
If more than one physical schema for this data server, select which is default

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Creating a Physical Schema Step 3 : Define Context


Specify, for which context, this physical schema maps to a logical one
For simple systems (one environment), it will map 1:1
For multi-environment systems, define multiple contexts and map this physical
schema to the correct logical one using the appropriate context

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Defining New Contexts


To define a new context, navigate to the Contexts panel, then select
New Context from the panel menu.
Name the context, and then use from that point in project

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Hands-On Labs
Lab 2 : Data Servers, Logical & Physical Schemas, and Contexts

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Summary
Data sources in ODI 11g are defined using the Topology navigator
Made up of data servers (physical databases, servers etc), logical and physical
schemas
One logical schema can map to multiple physical schemas, depending on context
Allows aliases to be defined that work across DEV, TEST, PROD environments
Connections can be made to databases, OLAP servers, files, XML etc
Connections are physically made using JDBC or JNDI drivers

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com

Oracle Data Integrator 11g Bootcamp


Lesson 2 : Topologies

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : enquiries@rittmanmead.com W: www.rittmanmead.com