p.5 pts odi11g topology

8/12/2019 P.5 PTS ODI11g Topology

1/35

Copyright 2010, Oracle. All rights reserved.


2/35

Oracle Data Integrator

Topology Concepts

PTS Workshop: ODI 11g


3/35


Insert Picture Here>

Agenda

ODI Topology Overview

Physical Architecture

Logical Architecture

Topology Planning

Advanced Concepts Lab Overview

Q&A


4/35


ODI Topology


5/35


What is the Topology?

TopologyThe representation of theinformation systemin ODI:

Technologies: Oracle, DB2, File, etc.

Data Serversfor each technologies

Physical Schemasunder each data server

ODI Agents(run-time modules)

Definition of Languagesand Actions

Topology Navigator provides access to everything that isconsidered part of the ODI topology


6/35


What Topology Navigator Contains

Physical architecture

Data servers, physical schemas and agents

Logical architecture

Logical schemas and agents, contexts

Technology-related information

Technologies, languages, actions

ODI architecture components

Repositories and agents


7/35


Topology Navigator: Overview

Topology Navigator stores all the information in the Master

repository.

Making changes in Topology Navigator:

Affects all attached repositories

May affect the behavior of the work in progress or runningprocesses


8/35


Topology Navigator: Overview

Tree view

TopologyNavigator

views

Workbench

Manualrefresh


9/35


Physical Architecture


10/35


Physical Architecture View

Technology

Data server

Physical agent

Physical schemas

To reduce the number oftechnologies displayed:

Select Windows >Hide Unused Technologies


11/35


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 temporaryobjects


12/35


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


13/35


Prerequisites for Connecting to a

Server

Drivers (JDBC, JMS)

Drivers must be installed in the appropriate driver sub-

directory for ODI Studio, standalone agent, and JEE agent

This should be done on all the machines connecting to the

data server Machines running an Oracle Data Integrator GUI

Machines running an Oracle Data Integrator Agent

Connection settings (server-dependent)

Machine name (IP address), port

User/password

Instance/database name


14/35


Important Note

The username is used to access all the underlying schemas,databases, or libraries in the data server.

Ensure that this user account has sufficient privileges.

For database:

SELECT

INSERT/UPDATE

CREATE/DROP

READ


15/35


1. Right-click the technologyof your data server

2. Select New Data Server

3. Fill in the Name

4. Fill in the connectionsettings:

Data Server Userand Password

(Optional) JNDIConnection

Creating a Data Server


16/35


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 connection5. Save the Data Server

Select driver

Select URL


17/35


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.


18/35


1. Click the Test Connection

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 beinstalled

Testing a Data Server connection


19/35


Logical Architecture


20/35


Logical Architecture and Context

Views

The same technologies are displayed in

Physical and Logical Architecture views.

Technology

Logical schemas

Logical agent

Contexts

To reduce the number oftechnologies displayed:

Select Windows >Hide UnusedTechnologies


21/35


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.


22/35


ContextConnects Logical to Physical

Oracle

Windows

Development site: NewYork

Linux

Oracle

Production site:Boston

Linux

Oracle

Production site:Tokyo

Logicalarchitecture

Contexts(a context maps individuallogical resources ontoindividual physical resources)

Physicalarchitecture

SALES_DEVSALES_PRODSALES_DEV

Development Global Production

ORACLE_ORCL_LOCAL_SALES(Logical schema)


23/35


Creating a Logical Schema

1. Go to the Logical

Architecture view.

2. Right-click the schema

technology.

3. Select New Logical Schema.4. Enter the schema Name.

5. You can associate the

schema with the physical

schemas, in different

contexts, here.


24/35


Editing a Context to Link the Logical

and Physical

1. Double-click the context.

2. Click the Agents tab.

3. For each Logical agent, select

the corresponding Physical

agent in the context.4. Click the

Schemas tab.

5. For each logical

schema, select

a correspondingphysical schema

in the context.


25/35


Planning


26/35


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


27/35


Matrix of Logical/Physical Mappings

Logical Schemas

Contexts Accounting Sales

DevelopmentACCOUNTING in

Oracle on Windows

SALES inOracle on

Windows

TokyoACCT in Oracle on

Linux

1

2


28/35


Lab Overview


29/35


Lab Objectives

In this lab series, you will learn how to:

Set up Oracle Data Integrator environment by creating

the Master and Work repositories

Use Topology Navigator to create the physical andlogical architectures

Create data servers and physical schemas

Link the physical and logical architectures

Install an ODI Agent as a background service


30/35


Lab 4-1: Master and Work Repository

Overview

Create and connect to the ODI Master Repositoryand the ODI Work Repository

SQL Developer

Create SNPM1 databaseuser for masterrepository

Create SNPW1 databaseuser for workrepository

Oracle Data

Integrator

Create masterrepository

Create Master Repositoryconnection MasterRepository Pr 2-1 withSNPM1 as the user

Create workrepositoryCreate WORKREP_PR2-1work repository connectionwith SNPW1 as the user

Oracle Data

IntegratorCreate master repository

Create Master Repositoryconnection Master Repository Pr2-1 with SNPM1 as the user

Create workrepository

Create WORKREP_PR2-1workrepository connection withSNPW1 as the user


31/35


Lab 4-2: Topology

Objects You Create in the Lab

Check markindicates

default context Logical schema you

create in practice

Data server youcreate in practicePhysical schemasyou create in practiceGlobal is a

pre-seeded

contextTwo contexts youcreate in practice

L b 4 2 T l


32/35


Lab 4-2: Topology

Overview1. Define Production context2. Define Development context (a 3rdcontext, Global, is pre-seeded)

3. Define ORACLE_ORCL_LOCAL data server4. Define ODI physical schemas for data server: SALES_DEV,

SALES_PROD5. Define ORACLE_ORCL_LOCAL_SALES ODI logical schema6. Map logical schema to the two physical schemas, in terms of the three

contexts

Logical schema youcreate in practice

Check markindicates

default context

Global is a

pre-seeded

contextTwo contexts youcreate in practice

Data server youcreate in practice

Physical schemasyou create in practice


33/35


Lab 4-3: Agents

Overview

Set up and install ODI Agent as a service


34/35


p.5 pts odi11g topology

Documents