Narration Script for ODI 11g NF eStudy

MODULE 1: Standard JDeveloper-Based IDE: Oracle Data Integrator Studio

Title

Hello, and welcome to this Oracle eStudy course entitled Oracle Data Integrator 11g: New Features. My

name is Richard Green. I am a curriculum developer at Oracle and I have helped educate customers on

Oracle products since 1997. I will be your tour guide for the next hour of interactive lectures and review

sessions.

The aim of this course is to introduce you to the new and enhanced features of Oracle Data Integrator 11g.

After completing this course, you should be able to appreciate the new and expanded features of this

release, including an understanding of the business reasons and technical benefits of these features. With

the focus on new and enhanced features only, this course is not intended as an overall introduction to all of

the features of Oracle Data Integrator.

A case study involving Simon Howell, a data integration project manager of a fictitious company, brings

out the business benefits of upgrading to the new version of Oracle Data Integrator.

Using The Player

Before we begin, now might be a good time to take a look at some of the features of this Flash-based course

player. Feel free to skip this slide and start the lecture if you’ve attended similar Oracle eStudy courses in

the past.

(click) To your left, you will find a hierarchical course outline. This course enables and even encourages

you to go at your own pace, which means you are free to skip over topics you already feel confident on, or

jump right to a feature that really interests you, or go back and review topics that were already covered.

Simply click on a course section to expand its contents and then select an individual slide. However, note

that by default we will automatically walk you through the entire course without requiring you to use the

outline.

(click) Standard Flash player controls are also found at the bottom of the player, including pause, previous,

and next buttons. There is also an interactive progress bar to fast forward or rewind the current slide.

Interactive slides may have additional controls and buttons along with instructions on how to use them.

Also found at the bottom of the player is a panel containing any additional reference notes for the current

slide. Feel free to read these reference notes at the conclusion of the course, in which case you can

minimize this panel and restore it later. Or if you prefer you can pause and read them as we go along.

(click) Various handouts may be available from the Attachments button, including the audio narration

scripts for this course.

The course will now pause, so feel free to take some time and explore the interface. Then when you’re

ready to continue, click the NEXT button below, or alternatively click the Module 1 slide in the course

outline at left.

About This Course

Introduction

So after having been given a quick introduction to the goals of this course, you still may be asking yourself

“Am I in the right place?” To help you answer this question, you can access information here regarding the

course’s objectives, target audience, and prerequisites.

Overview

This course introduces you to the new and enhanced features of Oracle Data Integrator 11g . It does not

attempt to provide every detail about a feature or cover aspects of a feature that were available in previous

releases. This course does not serve as a general introduction to the broad set of features and functionality

of Oracle Data Integrator.

This course is most useful if you have prior hands-on experience with the previous 10g release of Oracle

Data Integrator.

For broad or detailed information about the entire range of Oracle data integration capabilities, refer to the

documentation and Oracle University courses for data integration and data warehousing.

Course Objectives

After completing this course, you should be able to:

Identify changes in the Oracle Data Integrator 11g architecture and components

Describe components of the new Fusion (JDeveloper) user interface

Identify the new and enhanced usability and productivity features

Describe the enhancements to Knowledge Modules

Describe the changes to ODI agents

And explain the business benefits of each new feature

What are the Prerequisites?

To get the most from this course, you should have thorough familiarity, preferably hands-on, with the

previous 10g version of Oracle Data Integrator.

4 Course Road Map

This course consists of eight modules:

1. The first module is Standard JDeveloper-Based IDE: Oracle Data Integrator Studio

2. (click) The second module is Core Design-Time Features for Enhanced Productivity and

Performance

3. (click) The third module is Developer Usability and Productivity Enhancements

4. (click) The fourth module is New Features for Administration

5. (click) The fifth module is Using Load Plans to Organize Scenario Executions

6. (click) The sixth module is Enhanced Diagnostic Features and Capabilities

7. (click) The seventh module is Technologies and Knowledge Module Enhancements

8. (click) The eighth module is New Architectures Supported for Enterprise-Scale Deployment

Options

5 Module 1 title slide: Standard JDeveloper-Based IDE: Oracle Data Integrator Studio

Let us now proceed with the 1st module, Standard JDeveloper-Based IDE: Oracle Data Integrator Studio.

6 Module Topics

The user interface has been entirely redesigned in this release to improve developer productivity and make

advanced features more accessible.

This module’s topics include:

The new navigator organization

(click) New look and feel

(click) Redesigned editors

(click) and Improved user assistance

7 Should We Upgrade Now to the New Release?

Now let’s meet Simon Howell and his team. Simon Howell, a data integration project manager of a

fictitious company, wants to know what are the main new and enhanced features of Oracle Data Integrator

11g.

[click] Simon needs to decide whether to remain at ODI 10g,

or if now is the time to upgrade to Release 11g.

8 New Navigator Organization

The Designer editor, Operator editor, Topology editor, and Security editor are now called Designer

Navigator, Operator Navigator, Topology Navigator, and Security Navigator, all of which make up the

Oracle Data Integrator Studio.

The Oracle-standard user interface, which is now based on the Fusion Client Platform, provides an efficient

and flexible way to manage navigators, panels, and editors.

9 New Look and Feel of Editors

The ODI 11g user interface, which follows Oracle standards, preserves ODI 10g features while improving

usability. The editors have toolbars, expandable navigation trees on the left containing the usual ODI object

types, and workbench areas on the right for defining and editing ODI objects.

10 Easier Switching Among Editors

In previous releases of ODI, you had to close an editor to be able to open another.

[click] In ODI 11g, you can leave multiple editors open and switch among them by clicking their tabs.

[click] Within each editor, a number of tree views provide access to different kinds of information. You

can dock, undock, and rearrange these views to customize your work environment.

[click] For example, this screenshot of the Topology Navigator shows the Physical Architecture view that

lists data servers and physical schemas sorted by technology.

[click] You can expand other views within the Topology Navigator, such as Contexts, Logical

Architecture, Languages, Repositories, and General Action.

[click] The area to the right is referred to as the Workbench. When you double-click an element, its

window appears in this area.

11 Improved User Assistance

When you log in to the ODI client for the first time, you are presented with the Start Page, with links to

common sets of tasks. The top level of links are organized by a typical sequence of ODI tasks:

[click] 1. Define the Topology

[click] 2. Manage Data Models

[click] 3. Build Projects

[click] 4. Operate Integration Jobs

12 Using Online Help

The online Help has been entirely rewritten to support the new ODI 11g user interface.

The Help Center provides quick access to help and common tasks, as well as links to useful Oracle

resources.

Review

In this module, you should have learned about:

The new navigator organization

The new look and feel

The Redesigned editors

and Improved user assistance

Quiz

MODULE 2: Core Design-Time Features for Enhanced Productivity and Performance

15 Title Slide

Welcome to Module 2, Core Design-Time Features for Enhanced Productivity and Performance. In this

lesson, Simon is pleased to learn about the benefits of ODI 11g support for datasets and set-based operators,

the support for natural joins, the support for partitioning, the ability to define lookups, derived Select for

temporary interfaces, automatic temporary index management, and support for native sequences.

16 Module Topics

This module’s topics include:

Datasets and set-based operators

[click] Support for natural joins

[click] Partitioning

[click] Lookups

[click] Derived select for temporary interfaces

[click] Automatic temporary index management

[click] and Support for Native Sequences

17 Productivity and Performance Enhancements?

ODI 11g now provides a set of core features for increasing development productivity and the performance

of the integration flows.

Simon plans to decide when to upgrade to ODI 11g based on what he learns of its benefits.

[click] Simon asks: What are the performance and productivity enhancements?

[click] Another question is: What are the improvements for design time tasks?

18 Datasets and Set-Based Operators

ODI 11g brings support for datasets and set-based operators.

A dataset represents the data flow coming from a group of joined and filtered source datastores. Each

dataset includes the target mappings for this group of sources. Several datasets can be merged into the

interface target datastore using set-based operators such as Union and Intersect. The support for datasets as

well as the set-based operators supported depend on the capabilities of the staging area’s technology.

19 Flow with Multiple Datasets

This use of datasets accelerates interface design, and reduces the number of interfaces needed to merge

several data flows into the same target datastore.

You can add, remove, and order the datasets of an interface and define the operators between them in the

DataSets Configuration dialog.

Note that the set-based operators are always executed on the staging area; in this example, the staging area

named MEMORY_ENGINE.

When designing the integration interface, the mappings for each dataset must be consistent. This means that

each dataset must have the same number of target columns mapped.

20 Defining a Dataset

There are three main steps to defining a dataset.

[click] First, In the Source Diagram toolbar click Add /Remove DataSet... to display the DataSets

Configuration dialog.

[click] Second, click Add new DataSet... A new line is added for the new dataset at the bottom of the list.

In the DataSet Name field, give the name of the new dataset. This name will be displayed in the dataset tab.

In the Operator field, select the set-based operator for your dataset.

[click] Third, in the Interface editor, choose the tab containing the name of the dataset you defined. Now

you can drag datastores into the workspace area to serve as sources for this dataset.

21 Using Set-based Operators

This slide offers guidelines for using set-based operators successfully.

The support for datasets as well as the set-based operators supported depend on the capabilities of the

staging area’s technology.

When designing the integration interface, the mappings for each dataset must be

consistent, this means that each dataset must have the same number of target columns

mapped.

[click] In your interface, add several datasets.

[click] Select an IKM supporting datasets. In ODI 11g, all IKMs have been updated to support datasets and

set-based operators.

22 Automatic Degree of Parallelism

ODI 11g adds support for natural joins.

[click] A natural join is a join statement that compares the common columns of two tables with each other.

This join does not require any join expression to be specified, and is handled by the engine that processes it.

This engine automatically matches columns with the same name.

There are a few precautions for using natural joins:

You should check whether common columns exist in both tables, before doing a natural join.

Natural joins may cause problems if columns are added or renamed.

Also, no more than two tables can be joined using this method.

23 Support for Partitioning

ODI 11g supports partitioning of datastores.

[click] Partitions can be reverse-engineered using RKMs, or they can be manually created in models.

[click] When designing an interface, it is possible to define the partition to address, on the source and

target datastores.

[click] ODI code generation handles the partition usage syntax for each technology that supports this

feature.

[click] The partitioning is defined by the technology used:

24 Using Partitioning in an Interface

This screenshot shows where, in an interface’s mapping, you can specify the use of partitions on a target

datastore.

25 Lookups (Engage interaction)

Introduction

A wizard is available in the interface editor to create lookups using a source as the driving table and a

lookup datastore or interface. These lookups now appear as compact graphical objects in the interface

sources diagram. This feature simplifies the design and readability of interfaces using lookups, and allows

for optimized code for execution.

Generate Lookup Using Left Outer Join

You can generate the lookup as a Left Outer Join in the FROM clause.

Generate Lookup as Expression in Select Clause

Or, you can generate the lookup as an expression in the SELECT clause (in this case, the lookup table is

accessed in-memory). This second syntax is sometimes more efficient on small lookup tables.

26 Using Lookups

First ensure that the Technology you have chosen supports lookups. A Technology can have one of three

possible levels of lookup support:

None

Join

or Select

[click] In an interface, you can invoke the creation of a lookup in either of two ways:

From the File menu, choose New to open the Gallery and the Table Lookup Wizard

[click] or, Click the Lookup Wizard button

27 Lookup Wizard

These screenshots show that the lookup wizard has two steps. In the first step, you simply select your

driving and lookup tables. In the second step, you define the lookup condition, and you can specify several

options.

28 Derived SELECT for Temporary Interfaces

When using a temporary interface as a source or a lookup table in another interface, you can choose not to

persist the target of the temporary interface, instead generating a Derived Select (sub-select) statement

corresponding to the loading of the temporary datastore. Consequently, the temporary interface no longer

needs to be executed to load the temporary datastore. The code generated for the sub-select is either a

default generated code, or a customized syntax defined in an IKM.

This feature eliminates the need for complex packages to handle temporary interfaces, and simplifies the

execution of cascades of temporary interfaces.

This slide summarizes the new ODI 11g support for Derived SELECT for temporary interfaces.

First, in the Technology definition dialog, you place a checkmark at "Support Derived Table."

[click] Later, when you are working in the dialog for an interface that has a temporary source, a new

checkbox appears: "Use temporary interface as derived table".

29 Automatic Temporary Index Management

When creating joins or filters on source tables, you can have ODI 11g automatically generate temporary

indexes for optimizing the execution of these joins or filters. The user selects the type of index that needs to

be created in the list of index types for the technology. Knowledge modules automatically generate the code

for handling indexes creation before executing the join and filters as well as deletion after usage.

This feature provides automated optimization of join and filter execution, and enables better performances

for integration interfaces.

30 Support for Native Sequences

Oracle Data Integrator now provides support for a new type of sequence that directly maps to database-

defined sequences. When created, these can be picked from a list retrieved from the database. Native

Sequences are used as regular Oracle Data Integrator sequences, and the code generation automatically

handles technology-specific syntax for sequences.

In the Technology Definition dialog, you place a checkmark for "Supports Native Sequence" and you

provide a local sequence mask.

[click] Then, in the Technology Sequel dialog, you set the "Native Sequence Reverse SQL Query".

This feature simplifies the use of native sequences in all expressions, and enables cross references when

using such sequences.

31 Creating a Native Sequence

In the sequence definition tab, in the Sequence configuration area, select Native Sequence.

[click] In the Native sequence name field, click the ellipsis button and select a native sequence to use.

32 Review

In this module, you should have learned about the new ODI 11g support for:

Datasets and set-based operators

Support for natural joins

Partitioning

Lookups

Derived select for temporary interfaces

Automatic temporary index management

Support for Native Sequences

Module 3: Developer Usability and Productivity Enhancements

34 Title slide

In this module, you learn about the new and improved features of ODI 11g that enhance usability and

productivity.

35 Module Topics

This module’s topics include:

The New interface editor

[click] the Quick-Edit editor

[click] Auto fixing

[click] the Scenario naming convention user parameter

[click] and the Oracle Data Integrator Java API

36 How Is Developer Productivity Enhanced?

In addition to the entire redesign of the development interface, ODI 11g has new features that improve the

developer’s productivity.

[click] Simon now wants to know what are the new features of ODI 11g that enhance the productivity of

his developers.

37 New Interface Editor

The interface editor, used to create the integration interfaces, has been entirely redesigned to use the

JDeveloper diagramming framework. The advantages of this new editor include:

an Improved look and feel

Support for graphical options on diagram objects. For example, color and fonts can be changed for

individual diagram objects, and compact and expanded view can be used for better readability.

Thumbnail and zoom in/out is supported on the sources and flow diagram, to navigate large

diagrams.

Structure view supports diagram navigation using the keyboard.

Multiple source columns can be dropped directly onto the target datastore for faster mapping.

The Target mapping table is improved: mapping properties (such as Position, Indicator, Name and

Mapping expression) can be displayed selectively and sorted.

Also: sources, targets, filters, and joins can be selected and edited directly in the flow diagram.

38 Using Quick-Edit Editor

You can use the Quick-Edit Editor to perform the same actions as on the Mapping tab of the Interface

Editor, in a nongraphical form. With this nongraphical editor you can:

Add and Remove a Component

Edit a Component

Add, Remove, and Configure Datasets

and Change the Target DataStore

The properties of the following components are displayed in tabular form and can be edited in the

Quick-Edit Editor:

Sources

Lookups

Joins

Filters

and Mappings

39 Auto Fixing

Interface errors are now trapped and raised and indicated with helpful tips. Errors can be automatically

fixed with a single click.

When you save an interface, or click the error button from the interface editor toolbar,

[click] a list of all the design errors in the interface is displayed with meaningful messages and tips.

[click] Automated fixes are suggested and can be applied with a single click.

40 Scenario Naming Convention User Parameter

When generating a scenario or a group of scenarios from the Studio or using a tool, [click] the default naming convention that is used for naming the scenario can be defined in a pattern (by object name, folder path or project name) using the Scenario Naming Convention user parameter. New scenarios are named after the component, according to the Scenario Naming Convention user parameter. See ODI 11g User Guide, for more information. [click] The following tags can be used in the pattern.

• PROJECT_NAME: Name of the project containing the object

• FOLDER_PATH: Folder path to the object from in the project tree, separated with

underscores

• FOLDER_NAME(n): Name of one folder in the path, starting from the bottom (n=1

corresponds to the object‘s parent) to the top folder in the project tree. If the folder does not exist for the given index, returns an empty string

• FOLDER_NAME: Shortcut to FOLDER_NAME(1)

OBJECT_NAME: Name of the source object of the scenario

41 ODI Java API

ODI 11g provides a Java API for managing run-time and design time artifacts.

[click] Using this API, Java developers can embed ODI in their product and can drive integration process

creation from their own user interface.

42 Review

In this module, you should have learned about:

the New interface editor

the Quick-Edit editor

Auto fixing

the Scenario naming convention user parameter

and the Oracle Data Integrator Java API

MODULE 4: New Features for Administration

44 Title

Welcome to Module 4, New Features for Administration. In this module, you learn about the features that

have been added to ODI 11g to improve manageability of the Oracle Data Integrator components and

sessions.

45 Module Topics

This module’s topics include:

the New Oracle Data Integrator Console that replaces the Metadata Navigator

Oracle Fusion Middleware Control Console integration

Stale session detection and management

the Kill sessions immediate capability

the new Import reports

and Repository Corruption Prevention

46 Does This Release Help Administrators

Simon has looked at the new features that enhance developer productivity. Now he wants to see if this 11g

version of Oracle Data Integrator has new features to help ODI administrators.

[click] He assigns a team member to investigate whether there are any new features in support of ODI

administrators.

47 ODI Console Replaces Metadata Navigator

The first thing that Simon's team member discovers is that the Metadata Navigator's functionality has been

replaced by the ODI Console.

The ODI Console replaces the Metadata Navigator of ODI releases prior to ODI 11g. ODI Console

provides Web access to ODI repositories. It allows users to navigate projects, models, logs, and so on.

Business users, developers, operators, and administrators use their Web browsers to access ODI Console.

Note that with ODI Console you also can perform executions.

Using this console, production users can set up an environment, manage run-time operations and browse

through design-time artifacts.

This web interface integrates seamlessly with Oracle Fusion Middleware Control Console and allows

Fusion Middleware administrators to drill down into the details of Oracle Data Integrator components and

sessions.

[click] The last slide of this eStudy shows where you can access a hands-on Oracle By Example OBE

course on using the ODI Console.

48 Integration with Enterprise Manager Console

Oracle Data Integrator provides an extension integrated into the Enterprise Manager Fusion Middleware

Control Console. The Oracle Data Integrator components can be monitored as a “domain server” (this is a

WebLogic term) via this console, and administrators can have a global view of these components along

with other Fusion Middleware components from a single administration console.

[click] The last slide of this eStudy shows where you can access a hands-on Oracle By Example OBE

course on ODI integration with Enterprise Manager Console.

49 Enhanced Session Control (Articulate Engage interaction)

Introduction ODI 11g introduces two new features for enhanced session control. To see these new features, click each of the blue tabs on the left. Kill Sessions Immediate

Kill Sessions Immediate causes Sessions to be stopped in an immediate mode.

This mode will attempt to abort the current operation (for example, SQL statements launched against a database engine) instead of waiting for its completion.

Stale Session Detection and Management

ODI is now able to detect stale sessions that remain pending due to an unexpected shutdown of the agent or repository.

In ODI 11g, such stale sessions are now managed and pushed to an error state. 50 Import Report

The new import report is displayed after every import operation. Read it carefully to determine eventual

errors of the import process.

The import report gives you details on the:

Import Mode

Imported Objects

Deleted Objects

Created Missing References

and Fixed Missing References

With this new feature, importing objects becomes a very transparent operation as all changes can be

identified and archived.

51 Repository Corruption Prevention

When you import objects across repositories, ODI takes into account the following cases to avoid the risks

of import errors and repository corruption:

[click] Import in Synonym mode that may erase text with incorrect information is checked and not

allowed.

[click] ODI does not allow importing objects from two repositories with the same repository

identifier into a target repository. This avoids object collision and corruption.

[click] When attaching a work repository containing objects imported from another repository, a

warning is raised to the user.

[click] In addition, import of objects that reference non-existing objects now creates missing

references, identified in the import report. Such references can be resolved by importing the missing

object.

52 Review

In this lesson, you should have learned about:

How the New Oracle Data Integrator Console replaces Metadata Navigator

The new integration with the Oracle Fusion Middleware Control Console

The new capability to detect and manage Stale sessions

The new feature for performing Kill sessions immediate

The new Import report

And the new Repository Corruption Prevention features

Module 5: Using Load Plans to Organize Scenario Executions

54 Title

Welcome to Module 5, Using Load Plans to Organize Scenario Executions. In this module, you learn the

benefits of using Load Plans to organize Scenario executions. You see how to use the Load Plan editor to

create, manage, and use Load Plans.

55 Module Topics

This module’s topics include:

What are Load Plans?

[click] the Load Plan editor

[click] Load Plan step sequence

[click] and Defining restart behavior

56 Should We Organize Executions with Load Plans?

Simon has just learned that the execution of Scenarios can now be organized by a new feature called

Load Plans.

[click] In his team's very large data warehouses with thousands of tables to populate, Simon wants to

know: can Load Plans execute hundreds of Scenarios so that the data will flow from source to target most

efficiently?

When Simon's team uses ODI to populate very large data warehouses, it is common to have thousands of

tables being populated using hundreds of scenarios. The execution of these scenarios has to be organized in

such a way that the data throughput from the sources to the target is the most efficient within the batch

window. He has been told that Load Plans help organize the execution of scenarios in a hierarchy of

sequential and parallel steps for these types of use cases.

57 What are Load Plans?

A Load Plan is an executable object in Oracle Data Integrator that can contain a hierarchy of steps that can

be executed conditionally, in parallel or in series.

[click] A Load Plan is the largest executable object in ODI, using scenarios in its steps. The leaves of this

hierarchy of steps are scenarios.

[click] Packages, interfaces, variables, and procedures can be executed in the set of scenarios that make up

a load plan.

[click] Don't think of Load plans as substitutes for packages or scenarios. Rather, they are used to organize

at a higher level the execution of packages and scenarios.

[click] Load Plans also provide exception handling strategies if any of the scenarios in the Load Plan

end in error.

58 Load Plan Editor

This screenshot shows a sample Load Plan created in ODI for loading a data warehouse.

The Load Plan Editor provides a single environment for designing Load Plans. The Load Plan steps are

added, edited and organized in the Steps tab of the Load Plan Editor. The Steps Hierarchy table defines the

organization of the steps in the Load Plan. Each row in this table represents a step and displays its main

properties.

You can drag components such as packages, integration interfaces, variables, procedures, or scenarios from

the Designer Navigator into the Steps Hierarchy table for creating Run Scenario steps for these

components.

You can also use the Add Step Wizard or the Quick Step tool to add Run Scenario steps and other types of

steps into this Load Plan.

59 Load Plan Steps

A Load Plan is made up of a sequence of several types of steps. Each step can contain several child steps.

Depending on the step type, the steps can be executed conditionally, in parallel, or sequentially.

By default, a Load Plan contains an empty root serial step. This root step is mandatory and the step type

cannot be changed.

60 Defining the Restart Behavior

ODI 11g gives you flexibility in defining restart behavior. The Restart Type option defines how a step in

error restarts when the Load Plan is restarted.

You can define the Restart Type parameter in the Exception Handling section of the Properties Inspector.

Depending on the step type, the Restart Type parameter can take the values listed in the table on this slide.

61 Review

In this lesson, you should have learned about:

What are Load Plans

The Load Plan editor

Defining a Load Plan step sequence

and Defining restart behavior

Module 6: Enhanced Diagnostic Features and Capabilities

63 Title Slide

Welcome to Module 6, Enhanced Diagnostic Features and Capabilities. In this module, you learn about new

and enhanced ODI 11g features for detecting and troubleshooting errors.

64 Module Topics

This module’s topics include:

Enhanced error messages with more precise information

[click] Enhanced notifications and logging that use the Oracle Logging Framework

[click] Code execution simulation to simulate the results of executing an interface

[click] and Row-by-row KMs for debugging purposes

65 Improved Troubleshooting?

Now Simon turns his attention to the troubleshooting and debugging capabilities of the 11g release of

Oracle Data Integrator.

[click] He wants to know: Does ODI 11g give users new options for troubleshooting?

66 Enhanced Error Messages

Error messages raised by ODI Components and Sessions have been enhanced to provide administrators and

production operators with precise information for troubleshooting and fixing the status of the architecture,

and for debugging the sessions.

[click] Session, Step, and Task Information: This information is already contained in repository

tables. This information is added to error messages.

[click] Step Functional Information: This information is generated per step type. It should be stored

along with the session’s step as free text (this is design-time message generation)

[click] Stack Trace: This information is what has already been in the ODI 10g error messages.

67 Enhanced Notifications and Logging

Oracle Data Integrator 11g components now use the Oracle Logging Framework. Logging in any

component can be configured to meet the requirements of development, test, and production environments.

[click] In addition to this logging capability, agent components can now raise status and session

information in the form of Java Management Extension (JMX) notifications that propagate to any

administration console.

68 Code Execution Simulation

ODI 11g brings a new design-time feature that lets you simulate an interface execution. Simulating an

execution generates and displays the code corresponding to the execution, without running this code.

Execution simulation provides reports suitable for code review.

To simulate an execution:

1. First, in the Project view of the Designer Navigator, select the object you want to execute, right-

click and select Execute.

[click] Alternatively, if your object is open, click the Execute button.

2. [click] Next, in the Execution dialog box, set the execution parameters and select Simulation.

3. [click] Next, Click OK. The Simulation report is displayed. You can click Save to save the

report as an .xml or .html file.

69 Row-by-Row KMs for Debugging

Knowledge modules supporting row-by-row loading and integration have been introduced for debugging purposes. The two types of row-by-row KMs are:

• LKM SQL to SQL • and IKM SQL Incremental Update

[click] These knowledge modules break up the source dataset and load rows one by one. This type of processing allows logging each row operation to aid debugging.

70 Review

In this lesson, you should have learned about:

Enhanced error messages

Enhanced notifications and logging

Code execution simulation

and Row-by-row KMs for debugging

Module 7: Technologies and Knowledge Module Enhancements

72 Title

Welcome to Module 7, Technologies and Knowledge Module Enhancements. In this module, you learn

about new and enhanced knowledge modules and technologies delivered in the ODI 10g lifecycle patch sets

and in the ODI 11g release.

73 Module Topics

This module’s topics include:

ODI 10g Release 3 patch features

Knowledge module enhancements

Oracle Business Intelligence Enterprise Edition features

Oracle multi-table inserts

and Teradata multi-statements

74 Enhancements to Technologies and KMs?

Simon and his team have heard that a patch release of ODI 10g and the new release of ODI 11g have

introduced new knowledge modules and support for an expanded variety of technologies.

[click] Simon needs to know: which technologies and knowledge modules have been enhanced, and which

new technologies and knowledge modules have been added?

75 ODI 10g Release 3 Patch Features

This slide does not list new features of ODI 11g, but rather the new features delivered in the ODI 10g

Release 3 patch sets.

76 New KM Integrates Oracle GoldenGate and ODI

Let us focus on one of the new features from the ODI 10g Release 3 patch sets.

By using a Knowledge Module approach, ODI and Oracle GoldenGate can be integrated to provide greater

optimization and extensibility.

[click] This integration generates GoldenGate configurations from the ODI user interface.

[click] The ODI Journalizing Knowledge Module for Goldengate uses GoldenGate technology

to copy changed data from a source, with the least impact on that source.

[click] ODI then transforms the data and sends the result to the target.

[click] This Knowledge Module delivers an out-of-the-box pattern for Real-Time Data Integration.

This Knowledge Module for Oracle GoldenGate leverages the power of Oracle GoldenGate for its real-

time, log-based changed data capture.

77 Knowledge Module Enhancements

Leaving the new features of the 10g Release 3 patch sets, we now return to the new features of ODI 11g.

Specifically, let us look at enhancements to knowledge modules. Click on each blue bar for the answer to

its question.

[click] Do knowledge modules now support Partitioning? Yes, Oracle Reverse Engineering Knowledge

Modules can now reverse-engineer partitions.

[click] Do knowledge modules now support datasets and set-based operators? Yes, all Integration

Knowledge Modules have been updated to support datasets and set-based operators.

[click] Do knowledge modules now support automatic temporary index management? Yes, Oracle and

Teradata IKMs and LKMs have been updated to support automatic temporary index management.

[click] Do knowledge modules now support Oracle Database multi-table inserts. Yes, a new Integration

knowledge module for Oracle allows populating several target tables from a single source, reading the data

only once.

[click] Do knowledge modules now support Teradata multi-statements? Yes, A new Teradata Integration

knowledge module provides support for Teradata multi-statements, allowing integration of several flows in

parallel.

78 OBIEE Features

ODI 11g supports the reverse-engineering of View Objects that are exposed in the Oracle Business

Intelligence Enterprise Edition physical layer.

[click] Later, these view objects can be used as sources of integration interfaces.

79 Review

In this lesson, you should have learned about:

ODI 10g Release 3 patch features

Knowledge module enhancements

and Oracle Business Intelligence Enterprise Edition features

Module 8: New Architectures Supported for Enterprise-Scale Deployment Options

81 Title

Welcome to Module 8, New Architectures Supported for Enterprise-Scale Deployment Options. In this

module, you learn about the new features that support expanding into enterprise-scale deployments.

82 Module Topics

This module's topics include:

Standalone Agents

[click] Java EE Agents

[click] Support for WLS clustering

[click] external password storage

[click] External authentication and single sign-on

[click] repository connection retry

[click] integration with OPMN

83 Support for Enterprise-Scale Deployments?

Simon's team has had success using ODI. They want to know if ODI 11g introduces any new features that

will help them expand into enterprise-scale deployments.

84 ODI 11g Changes to Run-time Agent

Prior to ODI 11g, ODI had two types of agents: listener agents and scheduler agents. In ODI 11g, the run-

time agent is available as a standalone agent or a Java EE agent.

[click] Both of these agents are now connected to a single Work Repository and act as schedulers. The

agents are started with the built-in scheduler service activated. This scheduler service takes its schedules

from all the work repositories attached to the connected master.

[click] The agents connect systematically to the Master Repository at startup; agents are always connected

to Master Repository.

[click] The run-time agent now uses the HTTP protocol rather than its own protocol.

[click] The agent now includes its own Web service interfaces. A Web service can be invoked not only

with a JavaEE agent, but with a standalone agent. In this case, you do not need to have an application server

in your machine.

85 Standalone Agent

The ODI 11g Standalone Agent is similar to the ODI 10g Agent

[click] The Standalone Agent has its own built-in Load Balancer + Scheduler

[click] It can be protected via Oracle Process Manager and Notification. Specific scripts are provided for

OPMN. OPMN will be discussed later in this module.

[click] The Standalone Agent is installable via the Oracle Universal Installer or Manually with the

Companion CD

[click] The Standalone Agent includes Windows .bat and Unix shell scripts plus Config Files

[click] A number of ODI 10g Scripts have been deprecated

86 New Procedure for Installing Standalone Agent

The procedure for installing the ODI 11g Standalone Agent differs from the procedure for installing ODI

10g agents. First, use the encode password program to generate an encrypted password string.

[click] Second, edit the odiparams.bat file, inserting the encrypted password you generated in the previous

step.

[click] Third, define a physical agent in ODI.

[click] Fourth, define a logical agent in ODI, using the Global context to map it to the physical agent you

defined in the previous step.

[click] Finally, and here is where it is different from previous versions of ODI, only now you can execute

agent.bat after you have performed the previous four steps.

87 Java EE Agent

The Java EE Agent is delivered as a Template. You install it with Oracle Universal Installer in a

Middleware Home. You generate it from ODI Studio, then deploy it with WebLogic Server Configuration

Wizard. The configuration is stored in the Template, except for passwords.

[click] The Java EE Agent uses WebLogic Server capabilities, including: Clustering, Datasources, and

Load Balancing

[click] The Java EE Agent has its own built-In Scheduler. The Coherence engine stored in the WebLogic

Server is used for clustered built-in scheduling, Scheduler uniqueness, and migration handled by a

Coherence Cache

[click] The Java EE Agent does not include command line scripts.

[click] The last slide of this eStudy provides you a website address to access an Oracle University Oracle-

By-Example self-study course that gives you hands-on experience working with Standalone Agents and

Java EE Agents.

88 Support for WLS Clustering

Oracle Data Integrator 11g supports Clustering for the Java EE agents deployed on a WebLogic Server.

The main characteristics of this JEE Clustered Configuration are:

ODI applications run on two clustered WebLogic Server-managed servers. The WebLogic Server

cluster synchronizes configuration for common artifacts of WebLogic Server used by ODI, such as

data sources.

To avoid duplicate schedule processing, only one of these agents behaves like a scheduler. A

Coherence cache is used to handle scheduler service uniqueness and migration.

The agent provides failover scheduling capabilities.

Requests to the ODI agent in a cluster must be routed via a load balancer or via an HTTP proxy

server. The address of this fronting server is used by clients to connect transparently to any of the

ODI servers in the cluster.

89 External Password Storage (Articulate Engage)

Introduction

Oracle Data Integrator 11g introduces an option for storing passwords outside of ODI, rather than in the

Master Repository.

To learn some details of external password storage, click each of the blue tabs on the left.

Where Can Passwords Be Stored Externally?

Passwords can now optionally be stored in an external corporate credential store, instead of the usual

encryption in the Master Repository.

Which Passwords Can Be Externally Stored?

Data server and context passwords can be stored externally.

ODI Users and their passwords can remain in the Master Repository, or they too can be externally

authenticated

When Do You Set Password Storage?

You can set password storage at the time of Master Repository creation, or, at the time of Master

Repository import.

90 External Password Management

To recover a password if an external store crashes, the User must be disconnected. In this case, all

passwords will be lost.

[click] If you are switching between internal and external password storage, the User must be

disconnected.

[click] In this case of switching between internal and external password storage, only the Context

passwords will be lost.

91 External Authentication and SSO

ODI stores all user information as well as users' privileges in the master repository by default. When a user

logs in to ODI, it logs in against the master repository. This authentication method is called internal

authentication. ODI can optionally use Oracle Platform Security Services to authenticate its users against an external

Identity Store, which contains enterprise users and passwords. Such an identity store is used at the

enterprise level by all applications, in order to have centralized user and password definitions and Single

Sign-On. In such a configuration, the ODI master repository only contains references to these enterprise

users. This authentication method is called external authentication.

ODI can authenticate its users against a variety of external identity stores, such as

Oracle Internet Directory LDAP Server, or WebLogic Server.

[click] The last slide of this eStudy provides you a website address to access an Oracle University Oracle-

By-Example self-study course that gives you hands-on experience working with External Authentication.

92 Repository Connection Retry

The Agent, when connected to a repository based on Oracle RAC technology, can be configured with

connection retry logic.

If one of the Oracle RAC nodes supporting sessions for an agent becomes unavailable, the agent is able to

retry and continue its session on another node of the Oracle RAC infrastructure.

[click] You can specify RETRY NUMBER and INTERVAL in the ODIPARAMS file or in the Template.

93 Oracle Process Manager and Notification (OPMN)

There are three methods available for starting and stopping standalone agents.

[click] The ODI standalone agent can be startedand stopped from a command line interface using scripts,

or it can be controlled by a number of other methods.

[click] One of the alternative methods for controlling the ODI standalone agent is the use of OPMN.

OPMN can help manage process control actions like start, stop, and restart of JEE and non-JEE

applications. You can use OPMN to start, stop, and monitor the ODI standalone agent.

ODI 11g does not include a standalone version of OPMN. If OPMN is not already available in your

environment via Oracle middleware products, you can download OPMN separately.

[click] Fortunately, OPMN is included in the installation of several Oracle middleware products such as

Oracle Enterprise Performance Management suite and Oracle Application Server.

The steps to configure OPMN to manage ODI standalone agents are outlined in the ODI 11g Installation

Guide.

[click] The last slide of this eStudy provides you a website address to access an Oracle University Oracle-

By-Example self-study course that gives you hands-on experience working with External Authentication.

94 Java EE WLS Agent Template Generation

ODI 11g provides a wizard to automatically generate templates for deploying Java EE agents in Oracle

WebLogic Server.

[click] Such a template includes the Java EE Agent and its configuration, and can optionally include

[click] the Libraries and drivers for the datasources, and

[click] the JDBC datasource definitions required for this agent,

[click] as well as the Template target.

By using the Oracle WebLogic Configuration Wizard, domain administrators can extend their domains or

create a new domain for the ODI Java EE runtime agents.

95 WebLogic Server Templates for Java EE Agents

ODI 11g provides pre-packaged WebLogic Server templates for Java EE components.

[click] Oracle Data Integrator provides templates for:

• [click] A pre-configured Java EE Runtime Agent

• [click] Oracle Data Integrator Console

• [click] Public Web Services

• [click] and an Enterprise Manager plugin

These templates are used to create a WLS domain for Oracle Data Integrator or extend an existing domain

with Oracle Data Integrator components.

96 Automatic Datasource Creation for WebLogic Server

Java EE Components use JDBC datasources to connect to the repositories as well as to the source and target

data servers, and benefit, when deployed in an application server, from the connection pooling feature of

their container.

[click] To facilitate the creation of these datasources in the application server, Oracle Data Integrator

Studio provides an option to deploy a datasource into a remote Oracle WebLogic application server.

97 Review

In this module, you should have learned about:

The Standalone Agent and the Java EE Agent

Support for WebLogic Server Clustering

External Password Storage

External Authentication

Repository Connection Retry

Integration with Oracle Process Manager and Notification

Java EE WebLogic Server Agent Template Generation

Pre-Packaged WebLogic Server Templates for Java EE Components

And Automatic Datasource Creation for WebLogic Server

98 QUIZ

99 Adopting the New Features of ODI 11g

Now that Simon Howell, data integration project manager, has learned the new and enhanced features of

Oracle Data Integrator 11g, what has he decided to do?

[click] Based on what the new and enhanced data integration features can deliver, Simon has decided to

plan a schedule for upgrading from ODI 10g to 11g!

100 Course Summary

Let's review all the new and enhanced ODI 11g features covered in this course.

In this course, you should have learned about:

[click] how ODI 11g uses standard JDeveloper-Based IDE for the Oracle Data Integrator Studio

[click] the design-time features for enhanced productivity

[click] Developer usability and productivity enhancements

[click] New features for administrators

[click] how to use load plans to organize scenario executions

[click] the enhanced diagnostic features and capabilities for troubleshooting

[click] New ODI Technologies and enhanced Knowledge Modules

[click] and new architectures that support enterprise-scale deployments

101 How Can I Learn More?

This slide shows the Web address for the Oracle Learning Library series of Oracle by Example OBE

courses for ODI 11g. These thirteen OBE courses provide hands-on practice for specific ODI 11g topics.

[click] In addition to these short Web-based self-study courses, there is a 5-day instructor led classroom

course listed in the Oracle University website. The title of that course is Oracle Data Integrator 11g:

Integration and Administration.

Thank you for taking this eStudy course on ODI 11g New Features!

End of Oracle 11g R2 DW New Features eStudy