P.8 PTS ODI11g SettingUp Project

Copyright 2010, Oracle. All rights reserved.
<Insert Picture Here>

Oracle Data Integrator
Setting Up a New ODI Project
PTS Workshop: ODI 11g
<Insert Picture Here>
Agenda

ODI Projects
ODI Folders
Knowledge Modules
Exporting and Importing Objects
ODI Markers
Lab Overview
Q&A

ODI Projects
What Is a Project?
A project is a collection of ODI objects created by
users for a particular functional domain.
Oracle Data Integrator Projects:
Overview
What can a project contain?
Folders:
Packages
Interfaces
Procedures
Variables, sequences,
user functions
Knowledge modules
Markers
How to Use ODI Project in Your
Work?
An ODI project should represent a functional domain or an
integration project.
Projects have their own objects (knowledge modules,
variables, markers, and so on).
Objects in the projects can be shared by duplication.
You can also use global variables, sequences, and so on.
Examples:
Project: Chaining ACCOUNTING < > INVOICING
Project: Loading the data warehouse
Project: Generating and sharing sales results
Creating a New Project
1. Select New Project from
the drop-down menu.
2. Select a name.
3. Optionally, change the
code.
Code is used to prefix
project variables.
Keep it short.
4. Default markers are
added automatically.
5. One folder is created to hold
interfaces, packages, and procedures.
ODI Folders
What Is a Folder?
A folder is a hierarchical grouping beneath a project and
can contain other folders and objects.
Every package, interface, or procedure must belong to a
folder.
When should you create folders? One guideline is to create a
folder per "package" or scenario.
This way, all interfaces that are used in the same package
are grouped together.
The folder represents all that is necessary for a given
execution unit.
As a result, maintenance is typically simplified.
Creating a New Folder
1. Right-click a project
or folder.
2. Select New Folder.

3. Name the folder.

You can drag folders to
other folders.
Organizing Projects and Folders
When do you need a new project?
When you start working on a new integration project or
functional domain
When you want to keep objects separated
When do you need a new folder?
For organizational purposes within the project
Project/folder boundaries:
Objects cannot be shared between projects.
Global variables, sequences, and user functions can
be used by any project.
Objects within a project can be used in all folders.
Knowledge Modules
What Is a Knowledge Module?
A knowledge module is a code template containing
the sequence of commands necessary to carry out a
data integration task.
There are different knowledge modules for loading,
integration, checking, reverse engineering, and
journalizing.
All knowledge modules work by generating code to
be executed at run time.
Types of Knowledge Modules
There are six types of knowledge modules:
KM type Description
CKM Check
Checks data in a data store for errors statically or
during an integration process
IKM Integration
Uses a given strategy to populate the target data store
from the Staging Area
LKM Loading
Assembles data from source data stores to the
Staging Area
RKM
Reverse
engineering
Retrieves the structure of a data model from a
database. It is needed only for customized reverse
engineering.
JKM Journalizing
Sets up a system for Changed Data Capture to reduce
the amount of data that needs to be processed
I
n
t
e
r
f
a
c
e
s

M
o
d
e
l
s

SKM Data Services
Deploys Data Services that provide access to data in
datastores.
Which Knowledge Modules Are
Needed?
All knowledge modules to be used in a project must
be imported into the project.
Which knowledge modules would you need?
Start with basic SQL knowledge modules.
Add technology-specific knowledge modules as
needed.
For your projects, you will need LKMs, IKMs, and
CKMs only.
Knowledge Modules: Examples
LKM File to Oracle (SQLLDR)
Uses Jython to run SQL*LOADER via the OS
Much faster than basic LKM File to SQL
LKM Oracle to Oracle (DBLINK)
Loads from Oracle data server to Oracle data server
Uses Oracle DBLink
IKM Sybase ASE Slowly Changing Dimension
Uses SCD flags on columns
Creates historical rows when needed
CKM Oracle
Enforces logical constraints during data load
Automatically captures error records
Importing Knowledge Modules
1. Right-click the project.
2. Select Import > Import
Knowledge Modules.
3. Choose the
import directory.
ODI KMs are found
in the /xml-reference
subdirectory.
4. Select one or more
knowledge modules.
Use the Ctrl/Shift keys for
multiple selection.
Replacing Existing KMs
Import replace mode
Updates all interfaces using the KM
Preserves existing options
Does not update generated scenarios
Why replace an existing KM?
When a newer version is released
To undo any undesirable changes made
Replacing Existing KMs
1. Right-click the KM.
2. Select Import Replace.
3. Select the replacement
file.

Browse for the file.
Exporting and Importing Objects
Exporting and Importing
Needs:
Moving objects between projects
Wanting to send an interface to an off-site
colleague
Sharing ODI objects between repositories
For example, migrating objects from a
development
repository to a maintenance repository
Solution:
Export to an XML file.
Import the file into the other project.
Exporting an Object
1. Right-click the object.
2. Select Export.
3. Specify:
The export
directory
The export file name
(without .xml)
Whether to export child
objects
4. To export a work
repository, use the
menu system.

Importing an Object
1. Right-click the project or
folder.
2. Select Import > Import
<object>.
3. Specify:
The import type
The import directory
The file(s) to import
4. To import a repository or
topology, use the File menu.

ID Numbers: Overview
Every ODI object has
an internal ID number.
It is shown on its
Version tab.
Unique number for this
datastore in this
repository: 4
ID of the repository where
it was created: 001
ID number is unique for each type of
object.
ID number is exported with the object.
Import Types
There are two modes for importing ODI objects:
Duplication:
A new ID number for the
object is generated based
on the new repository
Synonym:
The ID stored in the export file is used
There are three submodes:
INSERT: Performs inserts into the repository
UPDATE: Performs updates in the repository
INSERT_UPDATE: Inserts new records and updates existing ones in the
repository
No ODI objects are deleted
Internal ID references are maintained

Choosing the Import Mode
Select Synonym mode:
To exchange objects between two repositories having
different identifiers
To update (add components to) an object with an export file
To ensure that you import objects in the right order:
Import objects on which other objects depend first.
For example: Before importing an interface, you should
import the models that it uses.
There is an optional module for dependency management.
Select Duplication mode:
To create a duplicate of the original object from the export file
To reuse an object in a different project, in the same
repository
Markers
What Is a Marker?
A marker is a tag that you can attach to any
ODI object, to help organize your project.
Markers can be used to indicate progress,
review status, or the life cycle of an object.
Graphical markers attach an icon to the object, whereas
nongraphical markers attach numbers, strings, or dates.
Markers can be crucial for large teams, allowing communication
among developers from within the tool.
Review priorities.
Review completion progress.
Add memos to provide details on what has been done or has
to be done.
This can be particularly helpful for geographically dispersed
teams.
Tagging Objects with Markers
1. Right-click the object.

2. Select Add Marker.

3. Select the marker group,
then the
marker.

4. The marker appears
next to the object.
Removing Markers
1. Right-click the marker.

2. Select Remove or Remove
All.
Marker Groups
A marker group is a collection of related markers.
Normal: One marker is selected at a time.
Multistate: Any combination of symbols can be
selected.
One marker group can contain both graphical and
nongraphical markers.
Project and Global Markers
Project markers:
Are created in the Markers
folder under a project
Can be attached only to
objects in the same project
Global markers:
Are created in the Global
Markers folder in the
Others view
Can be attached to models
and global objects
1. Right-click Global
Markers or Markers.
2. Select New Marker
Group.
3. Enter the Group
Name.
4. Enter the group
options.
Display Position
Auto-increment
Multi-state
5. Add markers.
6. For each marker, set:
The icon
The name
The type
Creating a Marker Group
Lab Overview
Lab Objectives
In this lab, you will learn how to:

Set up a new project
Use folders to organize your work
Import the right knowledge modules
Import and export objects
Lab 6: Creating Project and Folders
Overview
2. Create folder
HandsOn
1. Create project
PTS Lab 06-
Setting Up New
Project
3. Import Knowledge
Modules required for
working with the
following
technologies:
Sources:
MySQL
File
Targets:
Oracle

P.8 PTS ODI11g SettingUp Project

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

P.8 PTS ODI11g SettingUp Project

Загружено:

Авторское право:

Доступные форматы

Copyright 2010, Oracle. All rights reserved.

<Insert Picture Here>

Вам также может понравиться