8-1

3
Oracle Data Integrator
Topology: Connecting to the World
8-2
Objectives
Understand the basic concepts behind the Topology
interface.
Understand logical and physical architecture.
Know how to plan a Topology.
Have learnt current best practices for setting up a Topology.
After completing this course, you will:
8-3
What is the Topology?
Topology The representation of the
information system in ODI:
Technologies: Oracle, DB2, File, etc.
Datatypes for the given technology
Data Servers for each technologies
Physical Schemas under each data server
ODI Agents (run-time modules)
Definition of Languages and Actions
8-4
Properties of Physical Schemas
An ODI physical schema always consists of 2 data server
schemas:
The Data Schema, which contains the datastores
The Work Schema, which stores temporary objects
A data server schema is technology-dependant.
Catalog Name and/or Schema Name
Example: Database and Owner, Schema
A data server has:
One or more physical schemas
One default physical schema for server-level temporary objects

8-5
Concepts in Reality
Technology Data server Schema
Oracle Instance Schema
Microsoft SQL Server Server Database/Owner
Sybase ASE Server Database/Owner
DB2/400 Server Library
Teradata Server Schema
Microsoft Access Database (N/A)
JMS Topic Router Topic
File File Server Directory
8-6
Important Notes
8-7
Oracle 10g
Linux
Oracle 9i
Example Infrastructure
Windows
Windows Linux
ACCOUNTING
SALES
Windows
Production site: Tokyo
Production site: Boston
MS SQL Server
db_dwh
db_purchase
MS SQL Server A
db_dwh
MS SQL Server B
db_purchase
Oracle
ACCT
SAL
8-8
The Physical Architecture in ODI
Data server
Physical schema
Legend
Oracle-Boston9
ACCOUNTING
Oracle-Boston10
SALES
MSSQL-Boston
db_dwh
db_purchase
MSSQL-TokyoB
purchase
Oracle-Tokyo
ACCT
SAL
MSSQL-TokyoA
dwh
8-9
Prerequisites to Connect to a Server
Drivers (JDBC, JMS)
Drivers must be installed in /oracledi/drivers
This should be done on all machines connecting to the data
server.
Connection settings (server dependant)
Machine name (IP Address), port
User/Password
Instance/Database Name,
8-10
Important Note
8-11
1. Right-click the technology of
your data server
2. Select Insert Data Server
3. Fill in the Name
4. Fill in the connection settings:
Data Server
User and Password


(Optional) JNDI Connection
Creating a Data Server
8-12
Creating a Data Server - JDBC
1. Select the JDBC tab
2. Fill in the JDBC driver
3. Fill in the JDBC URL
4. Test the connection
5. Click OK
Select driver Select URL
8-13
The JDBC URL
The JDBC driver uses a URL to connect to a database system.
The URL describes how to connect to the database system.
The URL may also contain driver-specific parameters
Use the select button to choose the
driver class name and URL template.
8-14
1. Click the Test button
2. Select the Agent to test
this Connection
Local (No Agent) performs the
test with the Topology
Manager GUI.
3. Click Test
The driver must be
installed
Testing a Data Server connection
8-15
Note test the connection
8-16
1. Right-click the data server and
select Insert Physical Schema
2. Select or fill in:
Data Schema
Work Schema
3. Select whether this is the
Default schema
4. Click OK
A warning appears
Creating a Physical Schema
8-17
What is a Logical Schema?
Developers should not have to worry about
the actual location of the data servers, or the
updates in user names, IP addresses,
passwords, etc.
To isolate them from the actual physical
layer, the administration will create a Logical
Schema that is simply an alias for the
physical layer.
8-18
Alias vs. Physical Connection
MS SQL Server
db_dwh
Windows
Development site: New York, NY
Datawarehouse
(Logical Schema)
Logical Architecture: the Alias
Physical Architecture: the Physical Connection
User: Srv_dev
Password: 12456
IP:10.1.3.195
Database: db_dwh
8-19
Modifications of the Physical
Connection
MS SQL Server
db_dwh
Windows
Production Server: Houston, TX
Datawarehouse
(Logical Schema)
Logical Architecture: the Alias
Physical Architecture: the Physical Connection
User: Srv_prod
Password: 654321
IP:10.1.2.221
Database: db_dwh
Changes in the actual physical
information have no impact on
the developers who always
refers to the same logical alias

8-20
Mapping Logical and Physical
Resources
MS SQL Server
db_dwh
Windows
Development site: New York, NY
Windows
MS SQL Server
db_dwh
db_purchase
Production site: Houston, TX
Windows
MS SQL Server A
dwh
QA: New York
Datawarehouse
(Logical Schema)
Logical Architecture
Physical Architecture
But changing the connectivity
from one server to the other can
become painful

8-21
Mapping Logical and Physical
Resources
MS SQL Server
db_dwh
Windows
Development site: New York
Windows
MS SQL Server
db_dwh
db_purchase
Production site: Boston
Windows
MS SQL Server A
dwh
Production site: Tokyo
Datawarehouse
(Logical Schema)
Logical Architecture
Contexts
Physical Architecture
For that purpose, the
definition of Contexts will
allow you to attach more
than one physical definition
to a Logical Schema

8-22
Mapping Logical and Physical
Resources
Windows
MS SQL Server
db_dwh
db_purchase
Production site: Boston
Datawarehouse
(Logical Schema)
Production
Logical Architecture
Contexts
Physical Architecture
Purchase
(Logical Schema)
Of course, a
given context
will map all
physical
connections

Unix
MS SQL Server
CRM
CRM
(Logical Schema)
Production Production
8-23
Note Design-Time vs. Run-Time
8-24
Notes
8-25
Logical Architecture/Context views
Logical Schema
Technology
Logical Agent
The same technologies are displayed in Physical and Logical Architecture views.
You can reduce the number of technologies displayed
Windows > Hide Unused Technologies
Context
8-26
1. Double-click the context
2. Go to the Agents tab
3. For each logical agent, select
the corresponding physical
agent in the context.
4. Go to the Schemas tab
5. For each logical schema, select
the corresponding physical
schema in the context.
6. Click OK.

Linking Logical and Physical Architecture
8-27
Planning the Topology
1. Identify the physical architecture
All data servers
All physical schemas
Required physical agents
2. Identify the contexts
3. Define the logical architecture
Name the logical schemas
Name the logical agents
4. On paper, write out a matrix of logical/physical mappings
This matrix helps you plan your topology
8-28
Matrix of Logical/Physical Mappings
Logical Schemas
Contexts Accounting Sales
Development
ACCOUNTING in
Oracle on Windows
SALES in
Oracle on
Windows

Tokyo
ACCT in Oracle on
Linux


1
2

8-29
JDBC Driver
A JDBC driver is a Java driver that provides access to a type of
database.
Type 4: Direct access via TCP/IP
Type 3: Three- tier architecture
Type 2: Requires the database client layer
Type 1: Generic driver to connect ODBC data sources.
Drivers are identified by a Java class name.
Class must be in present on the classpath.
Drivers are distributed as .jar or .zip files
Should be copied to the /oracledi/drivers directory.
8-30
Some Examples of Drivers and URLs
Technology Driver URL
Oracle oracle.jdbc.driver.OracleDriver jdbc:oracle:thin:@<host>:<port>:<sid>
Microsoft SQL Server com.inet.tds.TdsDriver jdbc:inetdae7:<host>:<port>
Sybase (ASE, ASA, IQ) com.sybase.jdbc2.jdbc.SybDriver jdbc:sybase:Tds:<host>:<port>/[<db>]
DB2/UDB (type 2) COM.ibm.db2.jdbc.app.DB2Driver jdbc:db2:<database>
DB2/400 com.ibm.as400.access.AS400JDBCDriver jdbc:as400://<host>[;libraries=<library>]
Teradata com.ncr.teradata.TeraDriver jdbc:teradata://<host>:<port>/<server>
Microsoft Access (type 1) sun.jdbc.odbc.JdbcOdbcDriver jdbc:odbc:<odbc_dsn_alias>
File (Sunopsis driver) com.sunopsis.jdbc.driver.file.FileDriver jdbc:snps:dbfile