odi - topology

8/10/2019 ODI - Topology

1/30

8-1

3Oracle Data Integrator

Topology: Connecting to the World


2/30

8-2

Objectives

Understand the basic conceptsbehind the Topology

interface.

Understand logical and physicalarchitecture.

Know how to plan a Topology.

Have learnt current best practices for setting up a Topology.

After completing this course, you will:


3/30


4/30

8-4

Properties of Physical Schemas

An ODI physical schema always consists of 2 data serverschemas:

The Data Schema, which contains the datastores

The Work Schema, which stores temporary objects

A data server schemais technology-dependant.

Catalog Nameand/or Schema Name Example: Database and Owner, Schema

A data server has:

One or more physical schemas

One defaultphysical schema for server-level temporary objects


5/30

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


6/30

8-6

Important Notes


7/308-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/308-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


9/308-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,


10/308-10

Important Note


11/308-11

1. Right-click the technologyofyour data server

2. Select Insert Data Server

3. Fill in the Name

4. Fill in the connection settings: Data Server

Userand Password

(Optional) JNDI Connection

Creating a Data Server


12/308-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 driverSelect URL


13/30


14/308-14

1. Click the Test button

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


15/308-15

Note test the connection


16/308-16

1. Right-click the data server and

select Insert Physical Schema

2. Select or fill in:

Data Schema

Work Schema3. Select whether this is the

Default schema

4. ClickOK

A warning appears

Creating a Physical Schema


17/30

8-17

What is a Logical Schema?

Developers should not have to worry aboutthe 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

Schemathat is simply an alias for the

physical layer.


18/30

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

: 12456IP:10.1.3.195

Database: db_dwh

f f


19/30

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

: 654321IP:10.1.2.221

Database: db_dwh

Changes in the actual physicalinformation have no impact on

the developers who alwaysrefers to the same logical alias

M i L i l d Ph i l


20/30

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 connectivityfrom one server to the other can

become painful

M i L i l d Ph i l


21/30

8-21


Resources

MS SQL Server

db_dwh

Windows

Development site: New York

Windows

MS SQL Server

db_dwh

db_purchase


Windows

MS SQL Server A

dwh

Production site: Tokyo

Datawarehouse

(Logical Schema)Logical Architecture

Contexts


For that purpose, thedefinition of Contexts willallow you to attach morethan one physical definitionto a Logical Schema

M i L i l d Ph i l


22/30

8-22


Resources

Windows

MS SQL Server

db_dwh

db_purchase


Datawarehouse

(Logical Schema)

Production

Logical Architecture

Contexts


Purchase

(Logical Schema)

Of course, a

given contextwill map allphysicalconnections

Unix

MS SQL Server

CRM

CRM

(Logical Schema)

Production Production


23/30

8-23

Note Design-Time vs. Run-Time


24/30


25/30


26/30

8-26

1. Double-click the context

2. Go to theAgents tab

3. For each logical agent, selectthe corresponding physicalagent in the context.

4. Go to the Schemastab5. For each logical schema, select

the corresponding physicalschema in the context.

6. Click OK.

Linking Logical and Physical Architecture


27/30


28/30


29/30

8-29

JDBC Driver

A JDBC driver is a Java driver that provides access to a type ofdatabase.

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/driversdirectory.


30/30

8 30

Some Examples of Drivers and URLs

Technology Driver URL

Oracle oracle.jdbc.driver.OracleDriver jdbc:oracle:thin:@::

Microsoft SQL Server com.inet.tds.TdsDriver jdbc:inetdae7::

Sybase (ASE, ASA, IQ) com.sybase.jdbc2.jdbc.SybDriver jdbc:sybase:Tds::/[]

DB2/UDB (type 2) COM.ibm.db2.jdbc.app.DB2Driver jdbc:db2:

DB2/400 com.ibm.as400.access.AS400JDBCDriver jdbc:as400://[;libraries=]

Teradata com.ncr.teradata.TeraDriver jdbc:teradata://:/

Microsoft Access (type 1) sun.jdbc.odbc.JdbcOdbcDriver jdbc:odbc:

File (Sunopsis driver) com.sunopsis.jdbc.driver.file.FileDriver jdbc:snps:dbfile

odi - topology

Documents