D64974GC10 Ag PDF

THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM ONLY.
COPYING eKIT MATERIALS FROM THIS COMPUTER IS STRICTLY PROHIBITED
Activity Guide
D64974GC10
Edition 1.0
December 2010
D68949
Oracle University and Egabi Solutions use only
Oracle Data Integrator 11g:

Integration and
Administration
Disclaimer
This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and
print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way.
Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display,
perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization
of Oracle.
The information contained in this document is subject to change without notice. If you find any problems in the document, please
report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
Restricted Rights Notice
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United
States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS
The U.S. Governments rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted
by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.
Trademark Notice
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.
Authors
Viktor Tchemodanov, Richard Green
Technical Contributors and Reviewers
Nagavalli Pataballa, Nancy Greenberg, Denis Gray, Jeff Pollock, FX Nicolas,
Christophe Dupupet, Art Hetherington, Usha Ramanathan, Gerry Jurrens,
Phillip Scott, Taj-ul Islam
This book was published using:
Oracle Tutor
THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM ONLY. COPYING eKIT MATERIALS FROM THIS COMPUTER IS STRICTLY PROHIBITED
Copyright 2010, Oracle and/or its affiliates. All rights reserved.
Practices for Lesson 2 .............................................................................................................................. 1-1

Practices for Lesson 2: Flow of Data........................................................................................................ 1-2
Practice 2-1: Creating and Connecting to ODI Master and Work Repositories ........................................... 1-3
Practice 3-1: Setting Up and Installing an ODI Agent ................................................................................ 2-2
Practice 4-1: Working with Topology ........................................................................................................ 3-2
Practice 5-1: Creating a Model ................................................................................................................ 4-2
Practice 6-1: Setting Up a New ODI Project ............................................................................................. 5-2
Practice 7-1: Checking Data Quality in the Model ..................................................................................... 6-2
Practice 8-1: Creating ODI Interface: Simple Transformations .................................................................. 7-2
Practice 9-1: Creating ODI Interface: Complex Transformations ............................................................... 8-2
Practice 9-2: Creating ODI Interface: Implementing Lookup ...................................................................... 8-20
Practices for Lesson 10 ............................................................................................................................ 9-1
Practice 10-1: Creating ODI Interface: Exporting a Flat File to a Relational Table ...................................... 9-2
Practice 11-1: Using Native Sequences with ODI Interface ....................................................................... 10-2
Practice 11-2: Using Temporary Indexes ................................................................................................. 10-15
Practice 11-3: Using Data Sets with ODI Interface.................................................................................... 10-24
Practice 12-1: Using Temporary ODI Interfaces ....................................................................................... 11-2
Practice 12-2: Developing a New Knowledge Module ............................................................................... 11-33
Practice 13-1: Creating an ODI Procedure ............................................................................................... 12-2
Practice 14-1: Creating an ODI Package.................................................................................................. 13-2
Practice 14-2: Using ODI Package with Variables and User Functions ...................................................... 13-13
Practice 15-1: Working with ODI Versions................................................................................................ 14-2
Practice 16-1: Creating and Scheduling an ODI Scenario ......................................................................... 15-2
Practice 17-1: Enforcing Data Quality with ODI Interface .......................................................................... 16-2
Practice 18-1: Implementing Changed Data Capture ................................................................................ 17-2
Practice 19-1: Setting Up ODI Security .................................................................................................... 18-2
Practice 19-2: Integration with Enterprise Manager and Using ODI Console.............................................. 18-21
Oracle Data Integrator 11g: Integration and Administration Table of Contents

i
Table of Contents

Practice 20-1: Executing an ODI Scenario Through the ODI Public Web Service....................................... 19-2
Oracle Data Integrator 11g: Integration and Administration Table of Contents

ii
Chapter 1
Practices for Lesson 2
Chapter 1 - Page 1
Practices for Lesson 2: Flow of Data
Chapter 1 - Page 2
Use Case Scenario:

John works as a database administrator for FN Enterprise. In FN Enterprise, John is responsible
for performing database management and integration tasks on various resources within the
organization. In particular, John is responsible for data loading, transformation, and validation.
To set his ODI environment, he needs to set up the security with his OD and create Master and
Work repositories.
Background:
The first steps to setting up Oracle Data Integrator are to create database users for the Master
and Work repositories, then create the Master repository, connect to the Master repository,
create the Work repository, and then connect to the Work repository.
In this practice, you first use SQL Developer to create the database users for the Master and
Work repositories. Then, in ODI you create and connect to the ODI Master Repository and the
ODI Work Repository.
Note: These are practice repositories. In later lessons, you use other Master and Work
repositories that are partially predefined with source and target objects.
data
base
play .
png
SQL Developer
Create SNPM1 database user for

master repository
Create SNPW1 database user for
work repository
datab0
24.gif
Oracle Data
Integrator
Create master repository

Create Master Repository connection
Master Repository Pr 2-1 with SNPM1
as the user
Create work repository
Create WORKREP_PR2-1 work
repository connection with SNPW1 as
the user
Your Tasks:

Chapter 1 - Page 3
Practice 2-1: Creating and Connecting to ODI Master and Work

Repositories
The RDBMS used in this practice is Oracle 11g. To connect to your RDBMS, perform the
following steps:
Step
Screen/Page Description
Choices or Values
a.
MS Windows
Start the SQL Developer by selecting Start >

Programs > Oracle-OraDb11g_home1 >
Application Development > SQL
Developer. When SQL Developer starts,
close the Logging Page Log tab.
b.
Oracle SQL Developer
In Oracle SQL Developer, click + to expand

the connection Administrator. In the window
that follows, enter system in the User name
field, oracle1 in Password, and then click
OK.
a.
b.
2.
Create the RDBMS schema or user (Oracle 11g) for the Master repository.

Chapter 1 - Page 4
1.
Choices or Values
a.
Click OK to The RDBMS user/schema can

be created by executing the following SQL
command:
create user snpm1 identified by
password
default tablespace users
temporary tablespace temp;
Note: You can find this command in the text
file 2-1.txt located in c:\LABS\Text
folder.
Enter this command and then click the Run
button.
Note: In this command, password is the
value of password to connect to user snpm1.
b.
Grant connect privileges to the newly created

user by executing the following SQL
command:
grant connect, resource to snpm1;
c.
Expand the Other Users node to verify that

user snpm1 was successfully created.
a.
b.

Chapter 1 - Page 5
Step
c.
3.
Create the ODI Master repository:
Chapter 1 - Page 6
Choices or Values
a.
MS Windows
Start Oracle Data Integrator: Start >

Programs > Oracle ODI 11g-Home >
Oracle Data Integrator > ODI Studio.
b.
Oracle Data Integrator
Open the New Gallery by choosing File >

New.
In the New Gallery, in the Categories tree,
select ODI.
Select from the Items list the Master
Repository Creation Wizard. Click OK.
The Master Repository Creation Wizard
appears.
c.
Master Repository Creation Wizard
In the Master Repository Creation Wizard,

select the browse icon of the JDBC Driver
and then select Oracle JDBC Driver. Click
OK. Edit the JDBC URL to read:
jdbc:oracle:thin:@localhost:1521:orcl
Enter the User as snpm1 and the Password
as password . Click the Test Connection
button and verify successful connection. Click
OK. Click Next on the Master Repository
Creation Wizard screen.
d.
Master Repository Creation Wizard
In the Authentication window, enter the

Supervisor Password as SUNOPSIS. Enter
SUNOPSIS again to confirm the password.
Click Next.
Note: User names and passwords are casesensitive in ODI.
e.
Password Storage
In the Password Storage window, select

Internal Password Storage, and then click
Finish. When Master Repository is
successfully created, you will see the Oracle
Data Integrator Information message. Click
OK. The ODI Master repository is now
created.
f.
Message
Verify that ODI Master Repository was

created successfully, and then click OK.
a.

Chapter 1 - Page 7
Step
b.
Chapter 1 - Page 8
c.
Chapter 1 - Page 9
d.
e.
Chapter 1 - Page 10
f.
4.
Connect to the ODI Master repository by creating a new ODI Master Login:
Step
Choices or Values
Screen/Page
Description
a.
Oracle Data
Integrator
Open the New Gallery by choosing File > New. In the New
Gallery, in the Categories tree, select ODI. From the Items
list, select Create a New ODI Repository login.
b.
Repository
Connections
Configure the repository connections with the parameters

from the following tables. To enter the JDBC URL, click the
button next to the JDBC URL field and select
jdbc:oracle:thin:@<host>:<port>:<sid>, as shown
in the screen, then edit the URL. Select the Master
Repository only button. Click the Test button. Verify

Chapter 1 - Page 11
Choices or Values
Screen/Page
Description
successful connection and click OK. Click OK to save the

connection.
Oracle Data Integrator Connection
Parameter
Value
Login Name
Master Repository Pr 2-1
User
SUPERVISOR
Password
SUNOPSIS
Database Connection (Master Repository)

Parameter Value
User
snpm1
Password password
Driver List Oracle JDBC Driver
Driver
Name
oracle.jdbc.OracleDriver
Url
Note: Do not copy and paste in the JDBC URL field. This
may cause problems with entering a valid URL string.
Instead, open the drop-down menu and select the correct
driver from the list. Type the correct URL in the Url field.
Note: The ODI user name (SUPERVISOR) is case-sensitive.
c.
Oracle Data
Integrator
Click Connect to Repository. Select the newly created

repository connection, Master Repository Pr 2-1, from the
drop-down list. Click OK. The ODI Topology Manager starts.
You are now successfully logged in to the ODI Topology
Manager.
d.
Import Service
Description
Click the Topology tab. Click the Repositories tab in the left
panel of the Topology Manager. Verify that your newly
created Master repository is in the Repositories window.
a.

Chapter 1 - Page 12
Step
b.
Chapter 1 - Page 13
c.
Chapter 1 - Page 14
5.
d.
Use SQL Developer to create the RDBMS schema/user for the Work repository.

Chapter 1 - Page 15
Choices or Values
a.
If not opened, open SQL Developer. Create

the schema by executing the following SQL
command:
create user snpw1 identified by
password
default tablespace users
temporary tablespace temp;
Note: You can find this command in the text
file 2-1.txt located in c:\LABS\Text
folder.
Click Run.
b.
Grant connect privileges to the newly created

user by executing the following SQL
command:
grant connect, resource to snpw1;
c.
Run the following command to verify that

user snpw1 was successfully created and
shown among other users in the list:
select * from all_users;
a.
b.

Chapter 1 - Page 16
Step
c.
6.
Now that you created the RDBMS schema/user, use ODI Topology Navigator to create the
ODI Work repository:

Chapter 1 - Page 17
Choices or Values
Screen/Page
Description
a.
In ODI, click the Topology Navigator tab and then click to

the Repositories panel.
Right-click the Work Repositories node and select New
Work Repository.
The Create Work Repository Wizard opens.
b.
Specify ODI Work

Repository Connection
Properties
In the screen that follows, enter the parameters shown in the

following table. Click the Test button. Verify successful
connection and click OK.Click Next.
Parameter Value
Technology Oracle
Driver
Name
oracle.jdbc.driver.OracleDriver
JDBC Url
User
snpw1
Password
password
c.
Specify Work
Repository properties
In the Specify Work Repository properties panel, set the ID

to 1. Set the Name to WORKREP_PR2-1. In the Password
field, enter SUNOPSIS. In the Work Repository Type field,
leave Development unchanged. Click Finish. Verify that
the newly created Work repository is now in the work
repositories tree view.
Note: The Development type of repository enables
management of design-time objects such as data models
and projects (including interfaces, procedures, and so on). A
development repository includes also the run-time objects
(scenarios and sessions). This type of repository is suitable
for development environments.
d.
Create Work Repository

Login
In the Create Work Repository Login window, click Yes.

Enter the Login name: Work Repository Pr 2-1, as shown
in the screen. Click OK.
e.
Verify that Work repository WORKREP_PR2-1 was created

and is shown under the Work Repositories node.
a.

Chapter 1 - Page 18
Step
b.
Chapter 1 - Page 19
c.
d.
Chapter 1 - Page 20
e.
7.
Disconnect from the Master repository and connect to the Work repository:

Chapter 1 - Page 21
Choices or Values
Screen/Page
Description
a.
Click the ODI menu and select Disconnect Master

Repository Pr 2-1.
b.
Click Connect To Repository.
c.

Login
Select Work Repository Pr 2-1 from the Login Name

drop-down list. In the Password field, enter SUNOPSIS.
Click OK. Click the Designer tab. The following ODI
Designer screen appears.
You have now successfully created and connected to the
ODI Work repository.
d.

Login
Click ODI menu and select Disconnect Work repository

Pr 2-1.
a.
b.

Chapter 1 - Page 22
Step
c.
d.
Chapter 1 - Page 23
Chapter 1 - Page 24
Chapter 2
Chapter 2 - Page 1
Use Case Scenario:

John is responsible for data loading, transformation, and validation. He created Master and
Work repositories. Now he continues setting up his ODI environment by installing an ODI Agent.
Background:
A common task that is performed by using ODI is to set up and install ODI Agent as a service.
After the ODI scenarios are created, they can be scheduled and orchestrated by using an ODI
Agent, which is a lightweight Java process that orchestrates the execution of ODI scenarios. In
this practice, you create and execute an ODI Agent, which will be used in subsequent practices
for orchestration of the execution of ODI objects.
First you run encode <password> to generate an encrypted password.
You copy/paste that string into the odiparams.bat file that contains ODI agent parameters.
You then switch to ODI, and define a physical agent named localagent. Next, you define a
logical agent also named localagent, mapping it to the same-named physical agent. You specify
the Global context as the context in which to make this particular mapping of logical to physical
agents.
In the command window, you execute agent.bat to start the agent that you named localagent.
In ODI, you test connection to your newly created agent.
The directions on the following pages will take you through these activities:
1. Run encode oracle1 to generate an encrypted password string
2.
Edit odiparams.bat, inserting the encrypted password
3.
In ODI, define a physical agent named localagent
4.
In ODI, define a logical agent named localagent, mapping it to the physical agent named
localagent for the Global context
5.
Execute agent.bat, to start an agent named localagent.
6.
Verify connection to the newly created agent localagent in ODI

Your Tasks:

Chapter 2 - Page 2
Practice 3-1: Setting Up and Installing an ODI Agent
Before executing the agent.bat file to create the ODI Agent, you must run the encode
password command to generate an encrypted password and paste it into the
odiparams.bat parameter file. To do so, perform the following steps:
Step
Choices or Values
Screen/Page
Description
a.
MS Windows and
text editor
Navigate to the ODI_HOME directory, where ODI is installed

and open the agent\bin subdirectory:
(C:\Oracle\Middleware\Oracle_ODI1\oracledi\agen
t\bin). Navigate to the odiparams.bat file, right-click this
file, and select Edit to open it with a text editor. Leave this editor
open. You will run a batch file from a Command window and
return to this text editor to copy the results into the
odiparams.bat file.
Explanation: You need to edit the odiparams.bat file to set
the repository connection information for the ODI Agent to use.
The password information is stored as an encrypted string. You
will generate the encrypted string in a Command window.
b.
Command Prompt
Leave the text editor open, and open the Command window
(Start -> Run -> cmd). Change the directory to the
ODI_HOME\agent\bin directory:
C:\Oracle\Middleware\Oracle_ODI1\oracledi\agent
\bin
c.
Command Prompt
To generate the encrypted password string, you will be using

the agent command, encode <password>. Because your
password is the word oracle1, enter and execute the following
command in the Command window:
encode oracle1
Keep the Command window open, as you will be returning to it
after editing the odiparams.bat file.

Chapter 2 - Page 3
1.
d.
Choices or Values
Screen/Page
Description
Command Prompt
and text editor
Copy the generated, encrypted password from the Command

window (from the Command windows pull-down menu, select
Edit > Mark, then highlight the password with your mouse) and
insert it into the odiparams.bat file as the value for the
ODI_MASTER_ENCODED_PASS parameter. Verify and, if
necessary, edit settings for other parameters from the following
table, save the odiparams.bat file, and then close it. The
agents connectivity is now set up.
Parameter
Value
ODI_MASTER_DRIVER
oracle.jdbc.OracleDriver
ODI_MASTER_URL
ODI_MASTER_USER
DEV_ODI_REPO
ODI_MASTER_ENCODE
Insert your encoded password.
D_PASS
ODI_SECU_WORK_REP WORKREP
ODI_SUPRVISOR_ECO
Leave the default value.
DED_PASS
ODI_USER
ODI_ENCODED_PASS
ODI_JAVA_HOME
C:\jdk1.6.0_18
Note
DEV_ODI_REPO is an RDBMS schema/user (Oracle 11g) for
the Master repository. It was precreated for this and subsequent
practices.
Work Repository name is WORKREP.
Because each time that you encode the password, it receives
different values, your encoded password will differ from the one
provided in the screen.
Do not change the default value of the ODI_USER and
ODI_ENCODED_PASS parameters. Those parameters were
precoded during ODI installation.
a.

Chapter 2 - Page 4
Step
c.
b.
Chapter 2 - Page 5
d.
2.
Now that you have generated an encoded password and pasted it into the
odiparams.bat file, you need to create the ODI physical and logical agent definitions. To
create these ODI agent definitions, perform the following steps:

Chapter 2 - Page 6
Choices or Values
Screen/Page
Description
a.
MS Windows
ODI Login
If it is not started, start Oracle Data Integrator. Click Connect

To Repository. Select DEV_ODI_REPO from the Login Name
drop-down list. Click OK.
b.
Topology navigator
Click Topology Navigator tab. In Topology Navigator, select the

Physical Architecture panel. Right-click the Agents node.
Select New Agent.
c.
Agent: localagent
Fill in the following fields:

Name: localagent
Host: Network name or IP address of the machine the agent
has been launched on. Verify that this parameter is set to
localhost.
Port: Listening port used by the agent. By default, this port is
20910. Leave the default value.
Web Application Context: Name of the Web application
corresponding to the Java EE agent deployed on an
application server. For standalone agents, this field should be
set to oraclediagent.
Set Maximum number of sessions supported by this agent to
250. Click the Save button.
d.
Topology Navigator
Local Agent: New
Now you have to insert a logical agent in Logical Architecture,

and map it to the newly created Physical agent. Click the
Logical Architecture tab. Right-click Agents and select New
Logical Agent. On the screen that follows, set the Name to
localagent. Set Physical Agents to localagent. From the
file menu, click Save, and then close the Logical Agent tab.
a.

Chapter 2 - Page 7
Step
c.
d.
b.
Chapter 2 - Page 8
Now that you have created the agent and defined the ODI physical and logical agents, you
can start the agent directly from the command line.
Step
Choices or Values
Screen/Page
Description
a.
Command Prompt
Switch back to the Command window you left open at the

ODI_HOME\agent\bin directory
(C:\Oracle\Middleware\Oracle_ODI1\oracledi\agen
t\bin). Execute the agent.bat file by using the following
command:
agent -NAME=localagent
b.
Services
The agent is now starting. Verify that ODI Agent is successfully

started. Minimize the window Command Prompt agentNAME=localagent.
Note: This command window should remain open during all
labs.
c.
Oracle Data
Integrator
In ODI, click the Test icon to verify connection of the agent

localagent.
You successfully created and connect to ODI agent. Close the
localagent tab
Log tab
. Also, close the Messages .
a.

Chapter 2 - Page 9
3.
c.
b.
Chapter 2 - Page 10
Chapter 3
Chapter 3 - Page 1
Use Case Scenario:

John created the Master and Work repositories and installed an ODI Agent as a background
service. To complete setting up his ODI infrastructure, he needs to create contexts, a data
sever, and physical and logical schemas.
Background: Before you begin working on your ODI projects, you need to describe your ODI
infrastructure in the topology. As a starting point of this practice, you will use the environment
provided with the ODI installation. The infrastructure includes several servers. You need to
define the following new data server and its attached physical schemas.
Data Server: ORACLE_ORCL_LOCAL
Define two of three schemas available in this instance:

Schema
Description
SALES_DEV
Schema storing the target tables for

development purposes
SALES_PROD
Schema storing the production target

tables
STAGING
Schema used to store ODI temporary

objects (not used in this practice)
Both the SALES_DEV and SALES_PROD physical schemas contain identical table structures
and correspond to the same logical schema called ORACLE_ORCL_LOCAL_SALES. The
mapping for this logical schema depends on the context.
Note: Completing these tasks is critical for all subsequent practice sessions.
This practice consists of the following six steps:

1. Define the Production context.
2. Define the Development context (a third context, Global, is pre-seeded).
3. Define the ORACLE_ORCL_LOCAL data server.
4.
5.
Define the ODI physical schemas for data server: SALES_DEV,SALES_PROD.

Define the ORACLE_ORCL_LOCAL_SALES ODI logical schema.

Chapter 3 - Page 2
Practice 4-1: Working with Topology
6. Map the logical schema to the two physical schemas, in terms of the three contexts.
Your Tasks:
1. If not started, start Oracle Data Integrator and open the DEV_ODI_REPO connection.
Note: The username and password are case-sensitive.
a. Select Start > Programs > Oracle ODI11g-Home > Oracle Data Integrator > ODI
Studio. Click Connect To Repository.
b. Log in with the following details. Click OK.
Login name: DEV_ODI_REPO
User: SUPERVISOR
Password: SUNOPSIS

Chapter 3 - Page 3
Create a new context:

a. Click the Topology navigator tab, and then click the Context tab.
b.
Click the New Context icon
c.
Enter your context parameters as shown below. The context window should appear as
follows. Click the Save button
on the toolbar, and then select New Context.
Name: Production
Code: PRODUCTION
Password: Leave this field empty.
Default: Select this check box, and click Yes to confirm in the pop-up window.

Chapter 3 - Page 4
2.
To create another new context , repeat the operations:

Name: Development
Code: DEVELOPMENT
Password: Leave this field empty.
Default: Leave the check box deselected.
The contexts should appear as follows:
3.
Create an ORACLE_ORCL_LOCAL data server:

a.
Click the Physical Architecture tab. Expand the Technologies node, select the
Oracle node, and then right-click and select New Data Server.

Chapter 3 - Page 5
d.
Enter the following information on the Definition tab:
Name: ORACLE_ORCL_LOCAL
Instance Name: ORCL
User: ODI
Password: ODI

Chapter 3 - Page 6
b.
Click the JDBC tab. Click the

button at the right of the JDBC Driver field. In the
window that appears, select Oracle JDBC Driver, and then click OK.
d.
Click the
button to the right of the JDBC URL field. In the window that appears,
select the first URL, and then click OK.

Chapter 3 - Page 7
c.
4.
Edit the JDBC URL to have the following:

URL: jdbc:oracle:thin:@localhost:1521:ORCL
The JDBC tab should now appear as follows:
Test this data server:

a. Click the Test Connection button. Click Yes to confirm saving your data before testing
the connection. In the Information window, click OK.

Chapter 3 - Page 8
e.
5.
In the dialog box that appears, click the Test button. Click OK.
Create a physical schema for this data server: ORACLE_ORCL_LOCAL.SALES_DEV with

the following parameters:
Data Schema: SALES_DEV
Work Schema: STAGING
a.
Default check box: Selected

Expand the Oracle node. Right-click the newly created data server,
ORACLE_ORCL_LOCAL, and then select New Physical Schema.

Chapter 3 - Page 9
b.
In the new window that appears, select SALES_DEV from the Schema (Schema)
drop-down list, and then select STAGING from the Schema (Work Schema) dropdown list. Verify that the Default check box is selected, and leave all the other fields
unchanged. Click the Save button
appears.
. Click OK in the Information window that

Chapter 3 - Page 10
b.
6.
Expand: Oracle > ORACLE_ORCL_LOCAL. The Physical schema

ORACLE_ORCL_LOCAL.SALES_DEV appears in the tree view:
Create a physical schema ORACLE_ORCL_LOCAL.SALES_PROD for the

ORACLE_ORCL_LOCAL data server:
Data Schema: SALES_PROD
Work Schema: STAGING
a.
Default Schema: Not selected

Select the ORACLE_ORCL_LOCAL data server in the tree view, and then right-click
and select New Physical Schema.
b.
In the new window that appears, select SALES_PROD from the Schema (Schema)
drop-down list, and then select STAGING from the Schema (Work Schema) dropCopyright 2010, Oracle and/or its affiliates. All rights reserved.

Chapter 3 - Page 11
c.
fields unchanged. Click the Save button
7.
. In the Information window, click OK.
Create a logical schema, ORACLE_ORCL_LOCAL_SALES, and map this schema to different

physical schemas, for the different contexts.
Development Context: To the ORACLE_ORCL_LOCAL.SALES_DEV physical schema
Production Context: To the ORACLE_ORCL_LOCAL.SALES_PROD physical schema
a.
Global Context: To the ORACLE_ORCL_LOCAL.SALES_DEV physical schema

Select the Logical Architecture tab and expand the Technologies node. Select the
Oracle node, and then right-click and select New Logical Schema.

Chapter 3 - Page 12
down list. Check that the Default check box is not selected, and leave all the other
8.
Enter the name of the logical schema ORACLE_ORCL_LOCAL_SALES. To map this

logical schema to physical schemas in different contexts, select the appropriate
physical schema in front of each context, as shown in the following screen. Click the
Save button.
The logical schema FILE_DEMO_SRC is predefined for you and is mapped in the Global
context to a physical schema that represents a subfolder in a file system. Map
FILE_DEMO_SRC to the same physical schemas in the Development and Production
contexts.
a. In the Logical Architecture, expand the File node, and double-click the
FILE_DEMO_SRC logical schema. Ensure that the logical schema FILE_DEMO_SRC
is mapped to the physical schemas in the Development, Global, and Production
contexts, as follows. Click the Save button.

Chapter 3 - Page 13
b.
Repeat the previous step for the following logical schemas:
In XML technology, the logical schema XML_DEMO_GEO should be mapped to the

physical schema XML_DEMO_DIM.GEO, as follows.
In Hypersonic SQL, the logical schema HSQL_DEMO_SRC should be mapped

to the physical schema HSQL_LOCALHOST_20001_Default in all contexts.

Chapter 3 - Page 14
b.
In Hypersonic SQL, the logical schema HSQL_DEMO_TARG should be mapped

to the physical schema HSQL_LOCALHOST_20002_Default, as follows.
Note: Ensure that these mappings are similar in the three contexts. Close all the tabs, as
shown:
9.
You set up ODI agent localagent in Practice 3-1. Link the Logical agent to the Physical
agent in all three contexts and test the connection.
a. In the Physical Architecture, open the Physical agent localagent. Similarly, open the
Logical agent, localagent, in the Logical Architecture. Ensure that this Logical agent,
localagent, is linked to Physical agent localagent in all three contexts as follows.

Chapter 3 - Page 15
b.
In the physical agents localagent tab, click Test, and verify successful connection.
Click OK, and then close all the tabs.

Chapter 3 - Page 16
Save your changes.
Chapter 3 - Page 17
Chapter 3 - Page 18
Chapter 4
Chapter 4 - Page 1
Use Case Scenario:

John created a new ODI project and imported knowledge modules that will be used for
development of his integration project. Now, John needs to create new ODI Models and
reverse- engineer all tables and files in the models.
Background:
In the previous practice, you configured the schemas containing the application datastored in
the Oracle database. You now create the Oracle Sales Application model corresponding
to this data and reverse-engineer the schemas data structures. You also reverse-engineer the
structure of an XML file to a Geographic Information model that you define.
Your Tasks:
1. Start the ODI Demo source environment: Select: Start > Programs > Oracle ODI 11g-Home
> Oracle Data Integrator > Shortcut to startdemo. If the Open File Security Warning
window appears, click Run. The Oracle DI Demo Source command shell window opens.

Chapter 4 - Page 2
Practice 5-1: Creating a Model
2.
Create a model for the Oracle schema.

a. In Designer, select the Models tab.
b.
Click the New Model
icon and then select New Model.
c.
Specify (enter or select) the following parameters on the Definition tab:
Name: Oracle Sales Application
Code: ORACLE_SALES_APPLICATION
Technology: Oracle
Logical Schema: ORACLE_ORCL_LOCAL_SALES

The Definition tab should appear as shown:

Chapter 4 - Page 3
Note: You should have this command shell window running during all the labs.
3.
Click the Reverse Engineer tab, and then select Development from the Context dropdown list. Click the Save button.
Reverse-engineer all the tables in this model.

a. Right-click Oracle Sales Application model and select the Reverse Engineer option. If
the Confirmation window appears, click Yes.
Note: The progress of the reverse engineering process is shown on the status bar.

Chapter 4 - Page 4
d.
Verify the model reverse-engineered successfully. In the tree view, expand the Oracle
Sales Application model. The datastores of the model appear.
Expand the TRG_CUSTOMER datastore, and then expand the Columns and Constraints
nodes. The list of columns and constraints that were reverse engineered for this table
appear in the tree view. Check that the columns and constraints that were reverse

Chapter 4 - Page 5
b.
create table TRG_CUSTOMER (

CUST_ID
NUMERIC(10) not null,
DEAR
VARCHAR(4),
CUST_NAME
VARCHAR(50),
ADDRESS
VARCHAR(100),
CITY_ID
NUMERIC(10) not null,
PHONE
VARCHAR(50),
AGE
NUMERIC(3),
AGE_RANGE
VARCHAR(50),
SALES_PERS
VARCHAR(50),
CRE_DATE
DATE,
UPD_DATE
DATE,
constraint PK_TRG_CUSTOMER primary key (CUST_ID),
constraint FK_CUST_CITY foreign key (CITY_ID)
references TRG_CITY (CITY_ID));
Note: The constraint called FK_SALES_CUST TRG_SALES is defined on another table.
As it references TRG_CUSTOMER, it also appears here.

Chapter 4 - Page 6
engineered for the TRG_CUSTOMER table correspond to its data definition language
(DDL) given below. Close the tabs.
Create a model for an XML file.

a.
Click the New Model
icon and then select New Model.
b.
Specify (enter or select) the following parameters on the Definition tab:
Name: Geographic Information
Code: GEOGRAPHIC_INFORMATION
Technology: XML
c.
Logical Schema: XML_DIM_GEO

The Definition tab should appear as below. Click the Reverse Engineer tab.
d.
Select Development from the Context drop-down list. Click the Save button.

Chapter 4 - Page 7
4.
Reverse-engineer all the tables in this model.

a. In the Models tree view, right-click Geographic Information model and select the
Reverse Engineer option.
Note: The progress of the reverse engineering process is shown on the status bar.
b.
Verify that the model reverse-engineered successfully. In the tree view, expand the
Geographic Information model. The datastores of the model appear.

Chapter 4 - Page 8
5.
Open the XML file GEO_DIM.xml corresponding to the XML model that you have reverseengineered. The file is at the following location:
C:\Oracle\Middleware\Oracle_ODI1\oracledi\demo\xml
a. Open Windows Explorer, and go to the
C:\Oracle\Middleware\Oracle_ODI1\oracledi\demo\xml directory.
b.
c.
7.
Right-click the GEO_DIM.xml file and select Open.

The XML file opens in Internet Explorer. The file structure appears as shown here:
The file hierarchy is GEOGRAPHY_DIM > country > region > city > and so on..
Compare the XML file content with the reverse-engineered structure in the Hierarchical
view. In Designers tree view, expand the Geographic Information node, and then the
Hierarchy node. Expand the datastores under this node.
The hierarchy of the XML file is reproduced here. The XML file has been mapped to a
relational structure, with foreign keys to map the links between the different levels of
hierarchy. Close the Geographic Information model tab

Chapter 4 - Page 9
6.
Chapter 4 - Page 10
Chapter 5
Chapter 5 - Page 1
Use Case Scenario:

John is responsible for an integration project, which includes data loading, transformation, and
validation. He created contexts, a data sever, and physical and logical schemas in the
Topology. To start an integration project, John needs to create a new ODI project and import
knowledge modules that will be used for development of his project.
Background:
Now you assume the role of a project leader who is starting an integration project.
You create a project named HandsOnLoads with a folder named HandsOn. You import
knowledge modules for working with three sources (Hypersonic SQL, XML, and File) and one
target (Oracle.)
Note: Completing this practice is critical for all the following practice sessions.
Your Tasks:
1. Create a project, HandsOnLoads, with a folder called HandsOn.
a.
In Designer Navigator select Projects tab, click the New Project

select New Project.
b.
Enter the name of the project: HandsOnLoads. The code is automatically generated.

Chapter 5 - Page 2
icon, and then
Practice 6-1: Setting Up a New ODI Project
Click the Save button to create the project. The project appears in the tree view.
Expand the HandsOnLoads project node.
d.
ODI creates a folder called FirstFolder. Double-click this folder. In the editing window
that appears, edit the folder in the Name field, HandsOn. Click the Save button.

Chapter 5 - Page 3
c.
Import the knowledge modules required for working with the following technologies:
Sources:
Hypersonic SQL
XML
a.
File
Targets
Oracle
Select the HandsOnLoads project node. Right-click, and then select Import > Import
Knowledge Modules.

Chapter 5 - Page 4
2.
The Import Knowledge Modules window appears. Click the
c.
Navigate to C:\Oracle\Middleware\Oracle_ODI1\oracledi\xml-reference,
and then click Open. A list of knowledge modules appears.

Chapter 5 - Page 5
button.
b.
Select the following knowledge modules that are used in this project. Use the Ctrl key
for multiple selections. Click OK. In the screen that follows, click Close.
CKM HSQL
CKM Oracle
IKM Oracle Incremental Update
IKM SQL Control Append
LKM File to SQL
LKM SQL to Oracle
e.
Review Import Report, and then close it.


Chapter 5 - Page 6
d.
Check the imported knowledge modules by expanding corresponding nodes under

HandsOnLoads > Knowledge Modules, as shown here:

Chapter 5 - Page 7
f.
Close the HandsOnLoads and HandsOn tabs.
Chapter 5 - Page 8
Chapter 6
Chapter 6 - Page 1
Use Case Scenario:

John created new ODI Models and reverse-engineered all the tables and files in the models.
Now, John needs to check the quality of data in the models, define the constraints on the
models, and detect possible errors in data.
Background:
After the models are defined, you need to check the quality of the data in these models. In this
practice, you check the quality of data in the models and define constraints on models for the
given sample application.
First you create a new model, HSQL_ORDERS_APPLICATION, as a duplicate of the model
HSQL_SRC.
You then create a referential constraint on the SRC_CUSTOMER table's CITY_ID column, using
SRC_CITY as the parent table.
Next, you create a condition constraint on the SRC_CUSTOMER table:
Length(SRC_CUSTOMER.PHONE) > 6
Your Tasks:
1. Create a new model, HSQL_ORDERS_APPLICATION, as a duplicate of the model
HSQL_SRC.
a. In Designer, open the Models tab. Right-click HSQL_SRC model and select Duplicate
selection to duplicate the datastore. Click Yes.

Chapter 6 - Page 2
Practice 7-1: Checking Data Quality in the Model
Open the Copy of the HSQL_SRC model and rename it as HSQL Orders Application.
For Code, enter HSQL_ORDERS_APPLICATION. Click Save to save the model. If
you get a warning message, click Yes to finish saving.

Chapter 6 - Page 3
b.
Create a Reference constraint between the SRC_CUSTOMER and SRC_CITY datastores in

the new model. This reference is on the CITY_ID column.
a. Expand the HSQL Orders Application model, and expand the SRC_CUSTOMER
datastore.

Chapter 6 - Page 4
2.
Select the Constraints node, right-click, and select the New Reference option.
c.
From the Table drop-down list, select the SRC_CITY table. The name of the constraint
is automatically generated. Click the Columns tab.

Chapter 6 - Page 5
b.
3.
Click the
Add icon, and use drop-down lists to select the CITY_ID column for both
tables of reference. (Note that the Primary Table column is City, which you want to
also change to CITY_ID.) Click the Save button.
Create a Condition constraint on SRC_CUSTOMER to check that the phone number contains
six or more characters.
a. Select the Constraints node again for SRC_CUSTOMER, right-click, and select the New
Condition option.
Enter Phone Number Length in the Name field.

Select Oracle Data Integrator Condition from the Type drop-down list.
Enter the following expression in the Where field:
o
LENGTH(SRC_CUSTOMER.PHONE) > 6.
In the Message field, enter A phone number should contain more than 6
characters.
Note: You can also use the Expression Editor icon

expression.
to graphically edit the

Chapter 6 - Page 6
d.
Click the Validation icon
to validate your expression syntax.
c.
On the Oracle Data Integration Information screen, click OK. Click the Save button to
add the condition, and the close the tab.
Run a static check on the HSQL Orders Application model.

a. Select the HSQL Orders Application model tab and click Control tab.

Chapter 6 - Page 7
4.
b.
5.
Select Knowledge Module CKM HSQL.HandsOnLoads. Click the Save button. Close
the HSQL Orders Application model tab.
Select the HSQL Orders Application model in the tree view, right-click, and select Control >
Check.
a.
In the Execution dialog box, select Development context and then click OK.
b. Click OK when the Information dialog box notifies you that the session has started.

Chapter 6 - Page 8
b.
Click the Operator Navigator icon tab

. The Operator window appears. Click
the Hierarchical Sessions tab. Expand the All Executions node. Expand the HSQL Orders
Application session. Expand its Steps node. The session should appear complete,
containing steps marked with check marks and warnings, as shown here.
Note: You can optionally review the content of this session and see the different SQL
commands issued to perform the check operations.

Chapter 6 - Page 9
6.
Review the errors detected in the SRC_CUSTOMER datastore.

a. Click the Designer Navigator tab. In the Designer window, expand the HSQL Orders
Application model, select the SRC_CUSTOMER datastore, right-click, and select
Control > Errors.
b.
View the table that lists the errors detected in your table. You have one join error and
seven invalid phone numbers. Each line also contains the content of the invalid record.
c.
Verify the following:
d.
How many customers have an invalid CITY_ID? (1)
How many customers have invalid phone number? (7)

Close these tabs.

Chapter 6 - Page 10
7.
Chapter 7
Chapter 7 - Page 1
Use Case Scenario:

John created the new ODI models and reverse-engineered all the tables and files in the models,
defined the constraints on the models, and checked data quality. Now, John begins working on
creating ODI Interfaces to pass data between models and perform simple data transformations.
These interfaces will then be used for the development of his integration project.
Background:
After the models are defined and the quality of the data is verified, you need to create an ODI
Interface to perform transformations. In this practice, you create simple interfaces with one
target table and a single source. You will run these interfaces and check the execution.
In this practice, you create three interfaces. First, you create an interface called INT_8-1,
loading the TRG_COUNTRY datastore in the Oracle Sales Application model with the content of
the SRC_REGION table from the HSQL Orders Application model. This simple interface has no
transformations.
The second interface, INT_8-2, is a duplicate of INT_8-1, to which flow control is activated,
and constraints in the target table are checked.
The third interface, INT_8-3, loads the TRG_COUNTRY datastore in the Oracle Sales
Application model with the content of the SRC_CITY table from the HSQL Orders Application
model. In this interface, flow control is activated, constraints in the target table are checked,
and city population values are transformed from individual to times 1,000.
Note: Completing this practice is critical for other practice sessions.
Your Tasks:

Chapter 7 - Page 2
Practice 8-1: Creating ODI Interface: Simple Transformations
Create an interface called INT_8-1, loading the TRG_COUNTRY datastore in the Oracle
Sales Application model with the content of the SRC_REGION table from the HSQL Orders
Application model. You must map the columns of the same name without any
transformation. Ensure that you take only distinct records.
a. In Designer, click the Projects tab, and expand the HandsOnLoads project. Expand the
HandsOn folder. Select the Interfaces node, right-click, and select the New Interface
option.
b.
In the Interface window, enter INT_8-1 as the name of the interface. Ensure that the
Optimization Context is Global. Click the Mapping tab.
c.
In the Designer Navigator to the left, click the Models tab. In the tree view, expand the
Oracle Sales Application model. Drag the TRG_COUNTRY datastore from the tree
view to the Target Datastore zone (see the following screen: the panel to the right of
the panel with text stating Drag datastores. as sources for this dataset). The
datastore appears in this zone.

Chapter 7 - Page 3
1.
Expand the HSQL Orders Application model and drag the SRC_REGION datastore
from the model tree to the Sources zone of your diagram (the panel to the left of the
target panel). An Automap dialog box appears. Click Yes. Now the system
automatically maps fields in the source and target datastores.

Chapter 7 - Page 4
d.
Click the Flow tab. After the flow diagram initializes, you may want to use the zoom-out
button to see all the objects in the diagram. Click the box for Target + Staging Area that
is labeled Target (ORACLE_ORCL_LOCAL), and then in the Target Properties panel,
select the Distinct Rows check box. If open, click the
button to minimize the
Messages log. Your screen now looks as shown here.
Note: Confirm that the Distinct Rows check box is selected.

Chapter 7 - Page 5
e.
2.
Click the Save button to save your interface. If the Locking Object window appears,
select Dont show this window next time, and click Yes.
Run this interface, and check the content of the TRG_COUNTRY table.
a. Expand the Interfaces node, right-click the newly created interface INT_8-1, and then
select Execute.

Chapter 7 - Page 6
f.
Click OK in the Execution window, and then click OK when the Session Started
message appears.
c.
Click the Operator tab to open the ODI Operator Navigator. The Operator window
appears.
Note: In Operator, you may need to click the Refresh button
session.

Chapter 7 - Page 7
to view the new
b.
In the Session List tab, expand the All Executions node. The session called INT_8-1
should appear complete. Expand this session in the tree view as shown:
e.
In your interface window, click the Mapping tab. In Target datastore

TRG_COUNTRY, right-click COUNTRY, and then select Data.
f.
A window appears with the loaded data.


Chapter 7 - Page 8
d.
3.
Verify your data and close this window. Close INT_8-1 tab. If the Unlocking Object
window appears, select Dont show this window next time check box and click Yes.
Create an interface called INT_8-2 that loads the TRG_REGION datastore in the Oracle
Sales Application model with the content of the SRC_REGION table from the Orders
ApplicationHSQL model. You must map the columns of the same name without any
transformation. Ensure that flow control is activated and all constraints in the target table
are checked.
Note: Because this new interface uses the same source as the previous one, you will
duplicate it.
a. Select the Designer tab. If not open, click the Projects tab and select the INT_8.1
interface. Right-click and select Duplicate Selection, and then click Yes in the
confirmation box. A copy of your interface appears.

Chapter 7 - Page 9
g.
Double-click the interface Copy of INT_8.1 to edit it.
c.
In the Name field, change the name to INT_8-2 and then click the Mapping tab.

Chapter 7 - Page 10
b.
Click the perform layout button

Confirmation window, click Yes.
to customize the view of the Source zone. In the
e.
In the Designer, click the Models tab, and then drag the TRG_REGION datastore from
the Oracle Sales Application model to the Target Datastore zone. Leave the source
datastore unchanged. Click Yes to perform automatic mapping.

Chapter 7 - Page 11
d.
f.
Click the Flow tab. In the diagram, click the box labeled Target
(ORACLE_ORCL_LOCAL). In the Target Properties section, scroll down the IKM
option list to FLOW_CONTROL, and ensure that it is set to true.

Chapter 7 - Page 12
Click the Controls tab. Ensure that the selected KM is CKM Oracle. The value for
each Constraint should be true.

Chapter 7 - Page 13
g.
b.
Click OK in the Execution window, and then click OK when the Session Started
message appears.

Chapter 7 - Page 14
4.
h. Click the Save button to save your interface.

Run this interface, and check the content of the TRG_REGION table.
a. Click the Execute button.
In ODI Operator verify that your new interface executed successfully:
5.
a.
In the Interface window, click the Mapping tab. Select the TRG_REGION target
datastore (click the name of the datastore), right-click, and select Data. A window
appears with the loaded data.

Chapter 7 - Page 15
6.
Verify the data, close this window, and then close your interface INT_8-2.
Create an interface called INT_8-3 that loads the TRG_CITY datastore in the Oracle Sales
Application model with the content of the SRC_CITY table from the HSQL Orders
Application model. Ensure that flow control is activated and all constraints in the target
table are checked. You need to transform the city population values because the target
table unit is thousands of inhabitants, whereas the source table unit is inhabitants.
a. If not open, select the Designer tab, click the Projects tab, and then the Interfaces
node. Right-click and select New Interface.

Chapter 7 - Page 16
b.
In the Interface: NEW window, enter INT_8-3, and then click the Mapping tab.
c.
If not open, click the Models tab. In the tree view, expand the Oracle Sales Application
model. Drag the TRG_CITY datastore from the tree view to the Target Datastore zone.
The datastore appears in this zone.

Chapter 7 - Page 17
b.
Expand the HSQL Orders Application model and drag the SRC_CITY datastore from
the model tree to the Sources zone of your diagram. Click Yes to perform Automatic
Mapping.

Chapter 7 - Page 18
d.
Select the POPULATION column in the target datastore.
f. In the Mapping Properties section of the Property Inspector, in the Implementation tab,
edit the expression to populate the POPULATION column with the number of
thousands of inhabitants rounded to the nearest thousand. Edit the expression to have
the following: FLOOR(SRC_CITY.POPULATION/1000)
Note: You use the FLOOR function to perform rounding.

Chapter 7 - Page 19
e.
To verify the expression, click Check the Expression in the RDBMS button
OK.
h.
Click the Flow tab. Click the box labeled Target (ORACLE_ORCL_LOCAL). In the
Target Properties, scroll down the IKM option list to FLOW_CONTROL, and ensure
that it is set to true.

Chapter 7 - Page 20
. Click
g.
Click the Controls tab. Ensure that the selected CKM is CKM Oracle. The value for
each Constraint should be true. Click the Save button to save your interface. Close
your interface editor tab.

Chapter 7 - Page 21
i.
Run this interface, and check the content of the TRG_CITY table.
a. In the Designer Projects tab, right-click interface INT_8-3, and then select Execute.
b.
Click OK in the Execution window, and then click OK when the Session started
message appears.

Chapter 7 - Page 22
7.
Open the Operator Navigator and verify that your interface session executed
successfully:
Note: In Operator, you may need to click the Refresh button

Chapter 7 - Page 23
c.
In the Designer Navigator, open the Models tab. In the Oracle Sales Application
model, right-click the TRG_CITY datastore and select the Data option. A window
appears with the loaded data. Scroll down and view the total number of loaded records
and loaded data.

Chapter 7 - Page 24
d.
e.
Verify the data, and then close this window.

Note: The POPULATION column should show thousands of inhabitants.

Chapter 7 - Page 25
Chapter 7 - Page 26
Chapter 8
Chapter 8 - Page 1
Use Case Scenario:

John created the interfaces to pass data between models and perform simple ELT
transformations. Now John needs to create a more complex interface to load data in the target
model from different sources. He also needs to perform some data transformation and filtering,
and provide a date when data was updated.
Background:
In the previous practices, you learned how to create a simple ODI Interface.
In this practice, you create a more complex interface with several sources to load the
TRG_CUSTOMER datastore in the Oracle Sales Application model with the content of
SRC_CUSTOMER table and the SRC_SALES_PERSON files from different models. You apply
filtering to retrieve only customers with CUST_ID < 105. In addition, you populate the update
date (UPD_DATE) column with the System date in the mapping implementation field.
Your Tasks:
1. Create an interface called INT_9-1, loading the TRG_CUSTOMER datastore in the Oracle
Sales Application model.
a. In ODI Designer, click the Projects tab, and then the Interfaces node. Right-click and
select New Interface.

Chapter 8 - Page 2
Practice 9-1: Creating ODI Interface: Complex Transformations
In the Interface: NEW window, enter INT_9-1, set Optimization Context to

Development, and then click the Mapping tab.
c.
In the Designer Navigator, click the Models tab, and then in the tree view expand the
Oracle Sales Application model. Drag the TRG_CUSTOMER datastore from the tree
view to the Target Datastore zone. The datastore appears in this zone.

Chapter 8 - Page 3
b.
d.
In the Design Navigator Models tab, expand the FLAT_FILE_SRC model. Drag the
SRC_SALES_PERSON datastore to the Sources zone of your diagram.

Chapter 8 - Page 4
In the Design Navigator Models tab, expand the HSQL Orders Application model and
drag the SRC_CUSTOMER datastore to the Sources zone of your diagram. Click Yes
to perform Automatic mapping. If necessary, rearrange the datastores. Your diagram
should resemble the following:

Chapter 8 - Page 5
e.

Chapter 8 - Page 6
f.
.
Drag the SALES_PERS_ID column from the SRC_CUSTOMER source datastore onto
the ID column of the SRC_SALES_PERSON datastore. A join appears between these
two sources.
Select and drag the CUSTID column from the SRC_CUSTOMER source datastore to
the CUST_ID column in the TRG_CUSTOMER target datastore. Select the CUST_ID
column in the Target Datastore zone. The Mapping Properties panel shows the
mapping.

Chapter 8 - Page 7
g.
Note: You may find it useful to select the Freeze View button
before you perform the
next step.
i. Drag the FIRST_NAME and LAST_NAME columns from the SRC_CUSTOMER
source into the Mapping: CUST_NAME Implementation Tab field, and then edit the
mapping to have the following mapping expression:
INITCAP(SRC_CUSTOMER.FIRST_NAME) || ' ' ||
INITCAP(SRC_CUSTOMER.LAST_NAME)
Note: Ensure that the Active Mapping check box is selected for the CUST_NAME column
of the target datastore.

Chapter 8 - Page 8
Note: Ensure that the Active Mapping check box is selected for the CUST_ID column of
the target datastore.
h. Select the CUST_NAME column in the Target Datastore zone. The Mapping
Properties panel changes to show an empty mapping.
j.
Scroll down and select the Staging Area button on the Execute on panel.
Note: If the Thumbnail window is open, close it to extend the Mapping panel

Chapter 8 - Page 9
Drag the LAST_NAME column from the SRC_SALES_PERSON source datastore to the
SALES_PERS column in the target datastore. Click the SALES_PERS column in the
target datastore, and then edit the mapping to have the following mapping expression:
UPPER(TES.LASTNAME). Click the Staging Area option from the Execute on panel.

Chapter 8 - Page 10
k.
l.
Select the UPD_DATE column in the Target Datastore zone and enter the SYSDATE in
the Mapping implementation field. Click the UPD_DATE column again, and then select
the Staging Area option from the Execute on panel.
Note: Ensure that the Active Mapping check box is selected for the UPD_DATE
column of the target datastore.

Chapter 8 - Page 11

Chapter 8 - Page 12
m. Repeat step l for the CRE_DATE column. Because the value of the CRE_DATE column
should not be changed later, deselect the Update check box. Ensure that the Staging
Area option is selected from the Execute on panel.
In the diagram, drag the CUSTID column from the SRC_CUSTOMER source to the
workbench (the gray background). A filter appears with the CUST_ID column name.

Chapter 8 - Page 13
n.
Edit the filter expression to have SRC_CUSTOMER.CUSTID < 105. Scroll down and
ensure that the Source option from the Execute on panel is selected.

Chapter 8 - Page 14
o.
p.
Click the Flow tab. Click SrcSet1 (FILE_GENERIC). In the Source Set Properties,
select LKM File to SQL.

Chapter 8 - Page 15
In the Flow tab, click the Target datastore. In the Target Properties panel, set the
option DELETE_ALL to the value true as shown next. Click the Save button to save
the interface.
Note: By setting DELETE_ALL to true, you ensure that the table is cleared before
you populate it with new data.

Chapter 8 - Page 16
q.
2.
Run this interface, and check the content of the TRG_CUSTOMER table.
a.
b.
In the Projects tab, select interface INT_9-1. Click the Execute button
.
Click OK in the Execution window, and then click OK when the Session started
message appears. Open Operator, and verify that your Interface executed
successfully.
Note: In ODI Operator Navigator, you may need to click the Refresh icon

Chapter 8 - Page 17
c.
Return to Designer, click the Mapping tab, and select the TRG_CUSTOMER target
datastore (click the name of the datastore). Right-click and select the Data option. A
window appears with the loaded data.

Chapter 8 - Page 18
d.
Close this window, and then close your interface.
Chapter 8 - Page 19
Use Case Scenario:

John created an interface to load data in the target model from different sources and perform
data transformation and, filtering, and provided a date when data was updated. Now John
needs to implement a lookup to fetch additional information for the data loading in the target.
Background:
In the previous practices, you created an interface with several sources to load the
TRG_CUSTOMER datastore in the Oracle Sales Application model with the content of the
SRC_CUSTOMER table and the SRC_SALES_PERSON files from different models. Now you
implement the lookup to load data in the target according to the age range provided in the
lookup table.
Your Tasks:
1. Create an ODI Interface with a new lookup.
a. In the Designer, duplicate interface INT_9-1. Open the copy of INT_9-1 and rename
the interface INT_9-2. Ensure that the Staging Area Different From Target check
box is deselected. Click the Mapping tab.

Chapter 8 - Page 20
Practice 9-2: Creating ODI Interface: Implementing Lookup
b.
In the Mapping tab, click the
button to arrange the datastores in the source pane.
In the Confirmation window, click Yes. Click the Add a new Lookup

Chapter 8 - Page 21
icon.
In the Lookup Tables Wizard, select the SRC_CUSTOMER table in the Driving Table
pane. In the Lookup Table pane, expand the HSQL_SRC model, and then select
SRC_AGE_GROUP. For alias, enter LKUP_AGE_RANGE, and then click Next.
d.
In the screen that follows, select the AGE column in the Source table pane. Select
AGE_MIN in the Lookup pane, and then click the Join button.

Chapter 8 - Page 22
c.
e.
Edit the lookup condition to read:

SRC_CUSTOMER_AGE BETWEEN LKUP_AGE_RANGE.AGE_MIN. Select AGE_MAX in
the Lookup pane, and then click the Join button again.

Chapter 8 - Page 23
Edit the Lookup condition to read: SRC_CUSTOMER_AGE BETWEEN

LKUP_AGE_RANGE.AGE_MIN AND LKUP_AGE_RANGE.AGE_MAX. Click Finish.

Chapter 8 - Page 24
f.
Click the
button to arrange your datastores in the Source pane. In the
Confirmation window, click Yes. Select AGE_RANGE in the target datastore, and click
the Expression Editor icon

Chapter 8 - Page 25
g.
In the Expression Editor, select the AGE_RANGE column and drag it into the
expression window. Verify that your expression is LKUP_AGE_RANGE.AGE_RANGE.
Click OK to close the Expression Editor.

Chapter 8 - Page 26
h.
i.
To verify the SQL expression, click the Check the expression in DBMS icon
then click OK. Click the Flow tab.

Chapter 8 - Page 27
, and
In the Flow tab, click the Target area and ensure that IKM Selector is set to IKM Oracle
Incremental Update. Save the interface INT_9-2.
k.
In the Designer Projects tab, select INT_9-2, and then click the
interface. Select the Simulation check box, and then click OK.
l.
In the Simulation window, scroll down to view the generated code for your lookup, and
then click Close.

Chapter 8 - Page 28
icon to execute your
j.
Chapter 8 - Page 29
Run interface INT_9-2 and view the lookup data.

a.
Click the Execute button again to run your interface

Note: Do not select the Simulation check box.
. Click OK. Click OK again.

Chapter 8 - Page 30
2.
Click the Operator tab and verify that your interface INT_9-2 successfully executed.
c.
Double-click (SRCSet1 - Load data), and then click the Code tab. View the code on the
source and on the target.

Chapter 8 - Page 31
b.
Switch from the Operator Navigator to the Designer Navigator in the Projects tab, and
open the INT_9-2 interface if it is not still open. Click the interfaces Mapping tab.
Right-click Target Datastore TRG_CUSTOMER, and then select the Data option.
View your lookup data. Close the Data Editor window. Verify that your interface is
saved and the close the tabs.

Chapter 8 - Page 32
d.
Chapter 8 - Page 33
Chapter 8 - Page 34
Chapter 9
Chapter 9 - Page 1
Use Case Scenario:

In addition to the group of interfaces created earlier, John needs to create a project and an
interface to export data from a flat file and load this data into a relational table. He also needs to
verify the quality of data loaded in the table.
Background:
In the previous practices, you learned how to create ODI Interfaces, which transform data from
one or more relational tables in the source to a relational table in the target.
In this practice, you create from scratch an ODI project and an interface to export data from a
flat file to a relational table, execute and monitor the Interface with ODI, and check data quality.
In this practice, you perform the following 10 steps, detailed here:
1. In Topology Navigator, define the FILE_GENERIC.C:\labs\Files\Flat_files
physical schema.
2. In Topology Navigator, define the FLAT_FILES_SRC logical schema.
3. In Designer Navigator, create the Export-FF-RT project.
4. In Designer Navigator, create the Flat File1 source model.
a. Create the SRC_SALES_PERSON datastore.
b. Point to the resource: C:\labs\Files\Flat_files\SRC_SALES_PERSON.TXT.
c. Reverse-engineer and format the data (fixed length positions, data types).
5. In SQL Developer, create the RDBMS schema ODI_STAGE to host the ODI target
datastore.
6. In SQL Developer, create the TRG_SALES_PERSON table to serve as the ODI datastore for
the target model.
7. In Topology Navigator, create the ODI target data server, ODI_STAGE; physical schema
ODI_STAGE; and logical schema ODI_STAGE.
8. In Designer Navigator, create the ODI target model, Oracle_RDBMS1.
9. Reverse-engineer the model and check the populated TRG_SALES_PERSON datastore
table.
10. Create a new ODI interface to perform the flat file to RDBMS table transformation.
Your Tasks:
1. Create a new physical schema for the source flat-file model.
a. If not connected, connect to the Work repository, DEV_ODI_REPO. Enter
SUPERVISOR in the User field and SUNOPSIS in the Password field. Click OK to log
in.

Chapter 9 - Page 2
Practice 10-1: Creating ODI Interface: Exporting a Flat File to a

Relational Table
Click Topology navigator. In Topology navigator, click the Physical Architecture tab,
select Technologies > File. Right-click FILE_GENERIC, and then select New Physical
Schema.
c. For the Directory (Schema) and Directory (Work Schema) fields, enter the path to the
directory where your input flat files are located (C:\LABS\Files\Flat_files).
Select the Default check box and click Yes in the Confirmation window, and then click

Chapter 9 - Page 3
b.
the Save button. Close the editing window for your new physical schema. On the
Information window that follows, click OK. Close the editing tab.
d.
Verify that your new Physical schema was added under the FILE_GENERIC data
server in the Technologies tree view.

Chapter 9 - Page 4
Open Logical Architecture, navigate to Technologies > File, right-click File, and select
New Logical Schema.
f.
Enter the Logical Schema name: FLAT_FILES_SRC, and select the Physical schema
FILE_GENERIC in all three contexts as shown here. Click Save and close the editing
window.

Chapter 9 - Page 5
e.
2.
Verify that your new Logical schema was added under the File node in the
Technologies tree view.
Create the new project in ODI.

a. Open the Designer tab and then click Projects. In the window that opens, click the New
Project button
b.
and then select New Project to add a new project.
On the screen that appears, set the Name of the project to Export-FF-RT in the Name
field. The Code field is filled in automatically. Click Save, and then close the tab. The
newly created Export-FF-RT project now appears in the Projects pane.

Chapter 9 - Page 6
g.
Create a new model for the flat-file source datastore.

a.
In ODI Designer, click the Models tab, and then click the New Model
the New Model option to insert a new model.
b.
On the screen that follows, enter the values provided in the following table. Click the
Reverse Engineer tab. Set the Context to Development. Click the Save icon.
Parameter
Value
Name
Flat_File_1
Technology
File
Logical Schema
FLAT_FILES_SRC

Chapter 9 - Page 7
. Then select
3.
4.
Create a new ODI source datastore.

a. Right-click the newly created Flat_File1 model, and then select New Datastore.

Chapter 9 - Page 8
On the screen that appears, set the Name to SRC_SALES_PERSON. Click the button
next to the Resource Name field. Navigate to the C:\labs\Files\Flat_files folder,
and then select the SRC_SALES_PERSON.txt file. Click Open.
c.
Click the Files tab. Set the File Format to Fixed, and then click the Columns tab.

Chapter 9 - Page 9
b.
On the Columns tab, click the Reverse Engineer button. The following Confirmation
screen appears. Click Yes. The Column Setup Wizard appears.

Chapter 9 - Page 10
d.
Place the cursor, and then click the ruler at the beginning of each column as shown
next. The wizard marks each column as shown in the following screens.

Chapter 9 - Page 11
e.
After the columns are marked, click each column data to select a column, and then set
the name and data type for each column in the Definition panel to the right, as shown
in the following screens. For the names and data types of each column, refer to this
table. Click OK when you have finished.
Column
Name
Data type
C1
SALES_PERSON_ID
numeric
C2
FIRST_NAME
string
C3
LAST_NAME
string
C4
DATE_HIRED
string

Chapter 9 - Page 12
f.
g.
The columns should look as follows. Click Save to save the model. If the Unlocking
Object window appears, select the check box and click OK. Expand Flat_File_1 >
SRC_SALES_PERSON > Columns and view the newly created columns.

Chapter 9 - Page 13
h.
In the Flat_File_1 model, right-click the SRC_SALES_PERSON datastore, and then

select the View Data option. Close all tabs as shown next.

Chapter 9 - Page 14
5.
You must create a schema to host the ODI target datastore. To create a new RDBMS
schema for the ODI datastore, perform the following steps:
a. Open the Oracle SQL Developer window .You will create the schema by executing the
following SQL commands:
create user <MY_SCHEMA> identified by <MY_PASS>
default tablespace <MY_TBS> temporary tablespace <MY_TEMP>;
Note: If not started, you need to start SQL Developer and open the Administrator
connection (User Name: system, Password: oracle1). Refer to Practice 2-1.
In this command:

Chapter 9 - Page 15
<MY_SCHEMA> corresponds to the name of the schema you want to create:

ODI_STAGE
<MY_PASS> corresponds to the password that you gave: ODI_STAGE
<MY_TBS> corresponds to the Oracle tablespace where the data will be stored:
USERS
<MY_TEMP> corresponds to the temporary default tablespace: TEMP

To create a user, enter the following command. Verify that user ODI_STAGE is created
successfully.
Note: These commands also are provided in the text file 10-1.txt, which is located
in the C:\LABS\Text folder.
create user ODI_STAGE identified by ODI_STAGE
default tablespace users temporary tablespace temp;
b.
Grant connect privileges to the newly created user by executing the following SQL
command:
grant connect, resource, create trigger, create view to
ODI_STAGE;
6.
Now you need to create a new ODI datastore for the target model. This datastore will be
used within the ODI Interface. To create a new ODI target datastore, perform the following
steps:
a. In SQL Developer create a new connection called ODI_STAGE. Enter the username
as ODI_STAGE with the password ODI_STAGE. For SID enter ORCL. Click Test to
verify the connection. Click the Save button and then click Connect.

Chapter 9 - Page 16
Create your target table by executing the following SQL commands. Expand the
connection, ODI_STAGE > Tables > TRG_SALES_PERSON, and verify that the table
is created successfully.
CREATE table "TRG_SALES_PERSON"(
"SALES_PERSON_ID" NUMBER(8,0) NOT NULL,
"FIRST_NAME" VARCHAR2(80),
"LAST_NAME" VARCHAR2(80),
"DATE_HIRED" VARCHAR2(80),
"DATE_UPDATED" DATE NOT NULL,
constraint "TRG_SALES_PERSON_PK" primary key("SALES_PERSON_ID")
)

Chapter 9 - Page 17
b.
After you have created the new database target datastore, you need to create a new ODI
target data server and the physical schema. To create the ODI target data server and
physical schema, perform the following steps:
a. In ODI, open ODI Topology Navigator and then select the Physical Architecture tab.
Expand Technologies, right-click Oracle, and select New Data Server.
b.
In the Data Server: New window, enter the values provided in the following table. Click
the JDBC tab.
Parameter
Value
Name
ODI_STAGE
Instance/dblink (Data Server)
ORCL
User
ODI_STAGE
Password
ODI_STAGE

Chapter 9 - Page 18
7.
Click
for JDBC Driver. Select Oracle JDBC Driver. Click OK. Click
for JDBC
Url, select jdbc:oracle:thin:@<host>:<port>:<sid>, and then click OK. Edit the Url to
read: jdbc:oracle:thin:@localhost:1521:ORCL for Oracle Database.
Note: Do not copy and paste in the JDBC Url field. This action may cause problems
with entering a valid URL string.

Chapter 9 - Page 19
c.
Click Test Connection. In the window that opens, click Yes to save your data. In the
Information window, click OK. Click Test to verify a successful connection. Click OK.
e.
Expand Oracle technology node, right-click ODI_STAGE data server, and then select
New Physical Schema.

Chapter 9 - Page 20
d.
In the Schema (Schema) and Schema (Work Schema) field, enter your ODI_STAGE
schema. Click the Save button. Close the ODI_STAGE.ODI_STAGE physical schema
window. In the Information window, click OK.

Chapter 9 - Page 21
f.
Open the Logical Architecture tab, expand Technologies > Oracle. Right-click Oracle
technology and then select New Logical Schema.
h.
Name logical schema ODI_STAGE. In all three contexts, connect this logical schema
to the ODI_STAGE physical schema as shown here. Click the Save button and then
close the tabs.
Create a new ODI target model that will be used within your ODI Interface. To create a new
ODI target model, perform the following steps:
a. Open ODI Designer. Click the Models tab and select New Model. On the screen that
appears, enter the values provided in the following table. Click the Reverse Engineer
tab.
Parameter
Value
Name
Oracle_RDBMS1

Chapter 9 - Page 22
8.
g.
Oracle
Logical Schema
ODI_STAGE
b.
On the Reverse Engineer tab, set the Context to Development. Click the Save button
and then close the Oracle_RDBMS1 tab.
c.
In the Models tab, right-click the Oracle_RDBMS1 model. Select Reverse Engineer. To
verify that the TRG_SALES_PERSON datastore is successfully reversed, expand the
model as shown here.

Chapter 9 - Page 23
Technology
Create a new ODI Interface to perform a flat-file-to-RDBMS-table transformation.

a. In ODI Designer, click the Projects tab. Expand your project, Export-FF-RT, and then
expand First Folder. Right-click Interfaces and select New Interface. In the
Optimization Context field, select Development.

Chapter 9 - Page 24
9.
On the screen that follows, enter the interface name as INT-Exp-FF-RT. If selected,
deselect the Staging Area Different From Target check box. Click the Mapping tab.
c.
Click the Models tab to drag the source and target to the diagram. Drag the
SRC_SALES_PERSON.txt datastore from the Flat_File1 model into the Sources
container. Drag the TRG_SALES_PERSON datastore from the Oracle_RDBMS1
model into the Target Datastore container. When Designer asks Do you want to
perform an Automatic Mapping? click Yes.

Chapter 9 - Page 25
b.
Chapter 9 - Page 26
Set the value for the DATE_UPDATED column in Target Datastore to System date. In
Target Datastore, select DATE_UPDATED. In the Implementation tab, enter SYSDATE.
Select Staging Area in the Execute on section. Ensure that the Active Mapping check
box is selected.
e.
Select the FIRST NAME column in Target Datastore and edit the mapping to read:
ltrim(SRC.FIRST_NAME). This function removes left spaces in the FIRST_NAME
column. In the Execute on section, select Staging Area. Click OK. Repeat this step for

Chapter 9 - Page 27
d.
Column
Mapping implementation
FIRST NAME
Ltrim(SRC.FIRST_NAME)
LAST NAME
Ltrim(SRC.LAST_NAME)
DATE HIRED
Ltrim(SRC.DATE_HIRED)
columns LAST NAME and DATE HIRED. Refer to the mapping implementation
provided in the following table.

Chapter 9 - Page 28
Chapter 9 - Page 29
For this interface, you export a flat file directly to a relational table target. The
knowledge modules required for this interface are LKM File to SQL and IKM SQL
Incremental Update. To import the KMs, click the Project tab in the left panel and
expand the Knowledge Modules folder. Right-click Loading (LKM) and select Import
Knowledge Modules.

Chapter 9 - Page 30
f.
In the File import directory field, you should have entered

C:\Oracle\Middleware\Oracle_ODI1\oracledi\xml-reference. Press and
hold the Ctrl key, and then select IKM SQL Incremental Update and LKM File to SQL.
Click OK. Close the Import Report window. View the imported KMs in the Projects tree
view.

Chapter 9 - Page 31
g.
Chapter 9 - Page 32
Click the Flow tab. Click the SrcSet_0 (FILE GENERIC) datastore. The properties for
the source appear in the following screen. For LKM, select LKM File to SQL from the
LKM drop-down list if not selected. Now you need to ensure that the temporary objects
created during the transformation are deleted. Set the LKM option
DELETE_TEMPORARY_OBJECTS to <Default>:true as shown here.
i.
Click the Target datastore. Select IKM SQL Incremental Update. Set the IKM option
Flow_Control to False. Set the IKM option DELETE_ALL to True. Click Save.

Chapter 9 - Page 33
h.
To test your interface, click the Execute button

. The following screen appears.
Retain the defaults and click OK. On the next screen, click OK.

Chapter 9 - Page 34
j.
Open ODI Operator and verify that your interface was executed successfully. In
Operator, click Session List tab, select All Executions, and the then click the refresh
button
l.
. View the execution results for the interface INT-EXP-FF-RT.
Double-click Step 12 and click the Execution tab. View the number of rows inserted
into the target table (16).

Chapter 9 - Page 35
k.

Chapter 9 - Page 36
10. Use the Quick Edit feature to enable filtering rows with Sales_Person_ID > 30. In addition,
you capitalize the first letter of each last name and first name, leaving the other characters
in lowercase.
a. In the INT-EXP-FF-RT tab, select Quick-Edit tab, expand Filters section, and then click
Add Filters icon.
Select SALES_PERSON_ID row, and then click Expression Editor icon

. In the left
panel of Expression Editor, double-click SALES_PERSON_ID. Edit the expression to
read: SRC.SALES_PERSON_ID > 30. Click OK. For Execution Location, select
Staging. Click OK.

Chapter 9 - Page 37
b.
c.
Scroll down and expand the Mappings section. In Mappings, click the
Ltrim(First_name) column , and then select the Expression Editor icon. In functions,
expand Strings, and then double-click the INITCAP function. Edit the expression to
read: INITCAP(Ltrim(SRC.FIRST_NAME)). Click OK.

Chapter 9 - Page 38
d.
Repeat the previous step for the column LAST_NAME. Your result is shown in the
following screen. Click the Mapping tab and save your interface
.

Chapter 9 - Page 39
a.
In Designer execute your interface
. Click OK. Click OK again
b.
Open ODI Operator and verify that the interface executed successfully. Open step 8
Integration. Click the Code tab, and view your modifications.

Chapter 9 - Page 40
11. Execute your modified interface and verify the result.
Chapter 9 - Page 41
Click the INT_EXP_FF_RT tab. In the Mapping tab, right-click the target datastore and
select Data. View the filtered rows (SALES_PERSON_ID > 30) inserted in the table.
Close your Data Editor and the tabs.

Chapter 9 - Page 42
c.
Chapter 9 - Page 43
Chapter 9 - Page 44
Chapter 10
Chapter 10 - Page 1
Use Case Scenario:

John created interfaces to load data in the target model from different sources and performed
data transformation, filtering, and implemented lookups. Now John needs to create an interface
that would load data in the table by using Oracle native sequence, which generates ID numbers
for the target table.
Background:
In this practice, you first use ODI to define the procedure Create_ORCL_SEQ_FAM_ID. You
then execute this procedure, which creates the sequence SEQ_FAMILY_ID in the RDBMS.
Next, you use ODI to create an ODI definition of the native sequence you just created in the
RDBMS, using the same name, SEQ_FAMILY_ID.
Finally, you create and execute the interface INT-11-1 to load the TRG_PROD_FAMILY target
table by using the new native sequence to generate ID numbers for that table.
Your Tasks:
1. Create and execute an ODI procedure that creates an Oracle native sequence.
a. If not connected, connect to the DEV_ODI_REPO work repository (User:
SUPERVISOR, Password: SUNOPSIS). Click the Designer tab.
b.
In the Projects tab, expand: HandsOnLoads > HandsOn. Right-click Procedures and
select New Procedure. Name the new procedure: Create_ORCL_SEQ_FAM_ID. Set
the Target technology to Oracle, as shown next. Click the Details tab.

Chapter 10 - Page 2
Practice 11-1: Using Native Sequences with ODI Interface
In the Details tab, select the Add command button

. In the Name field, enter:
Create ORCL SEQ. In the Command on target tab, set the Technology field to
Oracle. In the Schema drop-down list, select ORACLE_ORCL_LOCAL_SALES. In
the Command panel, enter the command, which creates the following sequence. Click
the Save icon to save the procedure. Close the tab.
.
Note: This command is provided in the text file 11-1.txt in the following location:
c:\LABS\Text.

Chapter 10 - Page 3
c.
Run the procedure Create_ORCL_SEQ_FAM_ID and verify the result of the execution
in Operator.
d.

Chapter 10 - Page 4
2.
Open SQL Developer and expand: Administrator > Other Users > SALES_DEV >
Sequences. Verify that your sequence SEQ_FAMILY_ID was created in RDBMS.
Create a new Native Sequence in ODI.

a. Open Designer. Click the Projects tab and expand: HandsOnLoads > HandsOn . Rightclick Sequences, and then select New Sequence.

Chapter 10 - Page 5
e.
Name the new sequence SEQ_FAMILY_ID. Select the Native Sequence check box. In
the schema filed, select ORACLE_ORCL_LOCAL_SALES. Click the
icon. In the
window that follows, select the DEVELOPMENT context, and then select the native
sequence SEQ_FAMILY_ID. Click OK. Your screen should look as shown next. Save
the sequence, and then close the tab.

Chapter 10 - Page 6
b.
3.
Create a new interface to load the Product Family table by using the Native Sequence.
a. Right-click Interfaces, and select New Interface. Enter the new interface name:
INT_11-1. In the Optimization Context field, select Development. Click the Mapping
tab.

Chapter 10 - Page 7
In the Models tab, expand the HSQL_SRC model and Oracle Sales Application model.
Drag the SRC_PRODUCT datastore from the HSQL_SRC model to the source area in
your interface. Drag the TRG_PROD_FAMILY datastore from the Oracle Sales
Application model to the target area. Click Yes to perform automatic mapping.
c.
In the Target Datastore area, select FAMILY_ID, and then click the Expression Editor
icon
. Expand the Project Sequences node, and then drag the sequence
SEQ_FAMILY_ID to the expression area. Click OK. Click the Flow tab.

Chapter 10 - Page 8
b.
Chapter 10 - Page 9
In the Flow tab, click Target datastore, and then set IKM Selector to IKM SQL Control
Append. In the Options, set FLOW_CONTOL to false, and set DELETE_ALL to true.
Select the Distinct Rows check box. Save your interface. When the Fix Issue Dialog
window appears, select Fix. This option enables not checking the FAMILY_ID column
for not null.

Chapter 10 - Page 10
d.
Execute the newly created interface and verify the data in the target table.
a. Execute Interface INT_11-1 as shown next, and then verify execution in the Operator
tab.
4.

In the INT_11-1 tab, select the Mapping tab, right-click the Target Datastore
TRG_PROD_FAMILY, and then select Data. Verify the data inserted in the table. Close
the Data Editor window and INT_11-1 tab.

b.
Use Case Scenario:

John created interfaces to load data in the target model from different sources and performed
data transformation. He also created an interface, which loads data in the table by using Oracle
native sequence, which generates ID numbers for the target table.
Now John needs to load the target product table by using the source product table and the
lookup against the table, which contains the ID numbers generated by the newly created
interface with the native sequence. John also needs to create a temporary index on the source
tables to implement the join on the source.
Background:
In the previous practice, TRG_PROD_FAMILY was a target table. In this practice,
TRG_PROD_FAMILY serves as one of the source tables.
First you create a new ODI interface, INT-11-2 to load data into the TRG_PRODUCT target
datastore table in the Oracle Sales Application model. You specify the source tables as
SRC_PRODUCT from the HSQL_SRC model, and TRG_PROD_FAMILY from the Oracle Sales
Application model.
TRG_PROD_FAMILY will be used as a lookup table to obtain the ID number generated by the
previous lessons interface that used a sequence to populate the ID number.
For the lookup, you create a temporary index to join SRC_PRODUCT and TRG_PROD_FAMILY on
their FAMILY_NAME column.
Finally, you execute the interface, view the source code, and examine the inserted rows in the
TRG_PRODUCT target datastore.
Your Tasks:
1. Create a new ODI Interface with a temporary index on the source tables.
a. Expand the project HandsOnLoads > HandsOn > Interfaces. Right-click Interfaces and
select New Interface. Name this interface INT_11-2. Click the Mapping tab.

Practice 11-2: Using Temporary Indexes
In the Models tab expand the Oracle Sales Application and HSQL_SRC models. Drag
the TRG_PRODUCT datastore from the Oracle Sales Application model to the target
area. Drag the TRG_PROD_FAMILY datastore from the Oracle Sales Application to
the Source mapping area. Click Yes to perform automatic mapping. Drag the
SRC_PRODUCT datastore from the HSQL_SRC model to the source mapping area,
as shown next. Click Yes to perform automatic mapping
c.
Create a join between the two source tables by dragging FAMILY_NAME in the
TRG_PROD_FAMILY datastore to FAMILY_NAME in the SRC_PRODUCT datastore,
as shown in the following screen.

b.
Click the Join and scroll down to view the Join Property inspector. In the Temporary
Indexes section, set the index on SRC_PRODUCT(SRC_PRODUCT) to Non-Unique.
Click the Flow tab.

d.
e.
Click the Flow tab. In the flow tab, click the target datastore. Verify that the
DELETE_ALL parameter is set to false. Save your interface.

2.
Execute the Interface and verify the results.

a. In the Projects tab, execute your interface INT_11-2 as shown in the following screen.
Click OK. Click OK again.

b.
Open ODI Operator, and verify that your interface executed successfully. Expand the
session to view steps as shown in the following screen.

Double-click the step Integration INT_11-2 Create Temp. Indexes on Work. In the
Session Task, select the Code tab. View the source code.
d.
Scroll down, and then double-click the step Integration INT_11-2 Insert new rows,
as shown in the screen. View the number of inserted rows.

c.
Open the Designer tab. In the Interface INT_11-2 tab, select the Mapping tab. Rightclick the target datastore, and then select Data to view inserted rows. Close Data
Editor window and the tabs.
e.

Use Case Scenario:

John created an interface to load data in the target model from different sources and perform
data transformation and filtering, and provided a date when data was updated. He also
implemented a lookup to fetch additional information for the data loading in the target. Now John
creates an interface with multiple data sets to add in a bulk feed of customer data from another
system.
Background:
In this practice, you add a new data set to an interface. Building upon the interface INT_9-2
you created in Lesson 9, you will add a bulk feed of customer data from another system by
adding another data set.
First, you make a copy of interface INT_9-2, naming the copy as INT_11-3. This copy
includes the default data set you defined in INT_9-2.
Now you create a new data set, naming it BULK_CUST_DATA. For its source, you specify the
TRG_BULK_CUSTOMER datastore from the Oracle Sales Application model.
You specify the UNION operator to unite this new source of data with the default data set that
you specified in INT_9-2.
Next, you perform an execution simulation to preview the code that will be used for this new
data set with the UNION operator.
Finally, you execute the interface and verify the rows inserted into the target table.
.
Your Tasks:
1. Create an ODI interface with multiple data sets.
a. In the Designer, right-click interface INT_9-2 and then duplicate it. Open the duplicate
interface and rename it INT_11-3.Open the Mapping tab.

Practice 11-3: Using Data Sets with ODI Interface
b.
To arrange tables, click the Perform Layout icon

Add/Remove DataSet icon
, and then click Yes. Click the
, and then click Add new DataSet

Enter the new data set name: BULK_CUST_DATA. Select Operator: UNION. Close the
DataSets Configuration window.
d.
In the Mapping tab, select the BULK_CUST_DATA data set tab. In the Models tab,
drag the TRG_BULK_CUSTOMER datastore from the Oracle Sales Application to the
Source area of the interface. Click Yes to perform automatic mapping.

c.
e.
Open the Flow tab and verify the flow of your interface. Click the Target datastore.
Ensure that the FLOW_CONTROL option is set to true and the DELETE_ALL option is
set to true, as shown in the following.

Open the Mapping tab again, select BULK_CUST_DATA tab, and then save interface
INT_11-3.

f.
Perform an execution simulation in the Development context. In the Simulation window,

scroll down and view the simulated code for the data set TRG_BULK_CUSTOMER
with the UNION operator as shown next.

g.
Execute interface INT_11-3 and verify the execution results.

a. Execute interface INT_11-3.

2.
Open the Operator. Verify that the session INT_11-3 executed successfully. Scroll
down and open the task Integration INT_11-3- Insert new rows. Verify the number
of inserts in the target table.
b.

Chapter 11
Chapter 11 - Page 1
Use Case Scenario:

John created interfaces to load data in the target models from different sources and performed
data transformation and filtering, and implemented a lookup to fetch additional information for
the data loading in the target. John also created an interface with multiple data sets to add in a
bulk feed of customer data from another system.
Now John needs to create a temporary interface, which is used for loading data to a sales target
datastore.
Background:
In this practice, you perform the following steps:
1. Create a temporary interface, INT_12-1.
2.
3.
Use datastores SRC_ORDERS and SRC_ORDER_LINES from the HSQL_SRC model,

joined on ORDER_ID.
Use SRC_CUSTOMER as a lookup table.
Create a temporary target table, TEMP_AGG_ORDERS.
Aggregate some of its columns by using the MIN, MAX, and AVG functions.
Create interface INT_12-1-2
Use the temporary interface INT_12-1 as a source.
Use the datastore TRG_SALES as the target.
Execute INT_12-1-2 and examine the rows inserted into TRG_SALES.
Your Tasks:
1. Develop an ODI Temporary interface.

Chapter 11 - Page 2
Practice 12-1: Using Temporary ODI Interfaces
If not connected, connect to the DEV_ODI_REPO work repository (User:

b.
In the Projects tab, expand: HandsOnLoads > HandsOn. Right-click Interfaces, and
then select New Interface. Name the new interface INT_12-1. In the Optimization
Context field, select Development. For Staging Area, select Hypersonic SQL:
HSQL_DEMO_SRC. Click the Mapping tab.
c.
Open the Models tab. Expand the HSQL_SRC model, and drag SRC_ORDERS and
SRC_ORDER_LINES datastores from the model to the Source area.

Chapter 11 - Page 3
a.
d.
Drag the ORDER_ID column from the datastore SRC_ORDERS to the datastore
SRC_ORDER_LINES to create a Join.

Chapter 11 - Page 4
e.
Click the Lookup icon to start the Lookup Wizard

. Ensure that your Driving table is
SRC_ORDERS. Select the Lookup table, SRC_CUSTOMER, in the HSQL_SRC
model. For the Lookup table, edit the Alias to read: LKUP_SRC_CUSTOMER as
shown in the following screen. Click Next.

Chapter 11 - Page 5
Select the CUST_ID column in the Source table and the CUSTID column in the Lookup
table, as shown in the screen, and then click Join. Click Finish.

Chapter 11 - Page 6
f.
Now you need to create a temporary target datastore. Drag the column CUST_ID from
the SRC_ORDERS table to the Target area. Click <Temporary Target DataStore>. In
the Temporary Target Properties, enter Name: TEMP_AGG_ORDERS, as shown in
the following screen.

Chapter 11 - Page 7
g.
Drag the column ORDER_ID from SRC_ORDERS to the Target area. Edit the mapping
to read: MIN(SRC_ORDERS.ORDER_ID). Scroll down to the Target Column
Properties section and rename this column to FIRST_ORDER_ID. Click the interface
tab and view the result.

Chapter 11 - Page 8
h.
Chapter 11 - Page 9
i.
Again, drag the column Order_ID from SRC_ORDERS to the Target area. Edit the
mapping to read MAX(SRC_ORDERS.ORDER_ID). Scroll down and rename this column
LAST_ORDER_ID.

Drag the column ORDER_DATE from SRC_ORDERS to the Target area. Edit the
mapping to read MIN(SRC_ORDERS. ORDER_DATE). Scroll down and rename this
column FIRST_ORDER_DATE.

j.
Similarly, drag the column ORDER_DATE again from SRC_ORDERS to the Target
area. Edit the mapping to read MAX(SRC_ORDERS. ORDER_DATE). Scroll down and
rename this column LAST_ORDER_DATE.

k.
In the Source area, expand the lookup datastore. Drag the FIRST_NAME column from
the lookup table to the Target area. In the Target area, click the FIRST_NAME column.
Start the Expression editor
, and then drag the LAST_NAME column from the left
panel of the Expression Editor to the expression" area.

l.
LK_UP_SRC_CUSTOMER.LAST_NAME, as shown next. Click OK. Click the

to validate the expression.

button
m. Edit the expression to read LK_UP_SRC_CUSTOMER.FIRST_NAME | | ||
n.
Scroll down, and in the Target Column Properties, rename this column CUST_NAME.

Drag the column QTY from the SRC_ORDER_LINES source datastore to the Target
area. Edit the mapping expression to read SUM(SRC_ORDER_LINES.QTY).

o.
Drag the column AMOUNT from the SRC_ORDER_LINES source datastore to the
Target area. Edit the mapping expression to read AVG(SRC_ORDER_LINES.AMOUNT).
In the Target Column Properties, rename this column AVG_AMOUNT.

p.
Drag again the column AMOUNT from the SRC_ORDER_LINES source datastore to
the Target area. Edit the mapping expression to read
SUM(SRC_ORDER_LINES.AMOUNT). Rename this column SUM_AMOUNT.

q.
Drag the column PRODUCT_ID from the SRC_ORDER_LINES source datastore to

the Target area.

r.
In the Target datastore, click the SUM_AMOUNT column. In the Execute on section,
select Staging Area. Repeat this step for all the other columns that have a function in
mapping expression. Refer to the following table to verify the execution location. Your
Target datastore should now look as shown in the screen. Click the Flow tab.
Column
Execution Location
SUM_AMOUNT
Staging Area
AVG_AMOUNT
Staging Area
CUST_ID
Source
CUST_NAME
Source
FIRST_ORDER_DATE
Staging Area
FIRST_ORDER_ID
Staging Area
LAST_ORDER_DATE
Staging Area
LAST_ORDER_ID
Staging Area
PRODUCT_ID
Source

s.
Staging Area
QTY
t.
Verify the flow, and then save your temporary interface. Verify that your temporary
interface appeared in the tree view. Close your interface tab.
Note the color of your newly created temporary interface in the objects tree view.

2.
Create a new interface, which uses the newly created temporary interface as a source.
a. In the HandsOnLoads project, start creating a new ODI interface, INT_12-1-2, as
shown next. In the Optimization Context field, select Development. Open the Mapping
tab.

Drag the temporary interface, INT_12-1, from the Projects tab to the Source area.
c.
Drag the datastore TRG_SALES from the Oracle Sales Application model to the
Target Datastore area. Click Yes to perform automatic mapping.

b.
In the Target Datastore, select the FIRST_ORD_DATE column. Drag the

FIRST_ORDER_DATE column from the temporary interface in the source area to the
Implementation tab in the Mapping Properties area.

d.
Repeat the previous step to map columns FIRST_ORDER_ID, LAST_ORDER_ID, and

LAST_ORDER_DATE to the corresponding columns in the temporary interface in the
Source area. Map AMOUNT to SUM_AMOUNT, PROD_AVG_PRICE to the
AVG_AMOUNT column in the temporary interface, as shown below.
f.
In the Source panel, click INT_12-1 (TEMP_AGG_ORDERS), scroll down to the

Source Properties section, and then select the Use Temporary Interface as Derived
Table (Sub-Select) check box.

e.
g.
To view data derived from the temporary interface, right-click the temporary interface
and select Data. Close the Data Editor window.

h.
Select the Flow tab, click Target datastore, and verify the flow of your interface. In the
Target Properties, set the DELETE_ALL option to true. Save the interface, and then
close the interface tab.

Execute the interface INT_12-1-2 and verify the execution results.

a. Execute the interface INT_12-1-2.

3.
Open ODI Operator Navigator and verify that the interface INT_12-1-2 executed
successfully. Scroll down and open the task Integration - INT_12-1-2 - Insert new
rows. Verify the number of inserts.

b.
c.
In the Models tab in the Oracle Sales Application model, right-click the TRG_SALES
datastore, and select View Data. View the rows inserted in the target datastore.

Use Case Scenario:

To develop the integration project, John created the ODI project and the interface to export data
from a flat file and load this data into a relational table. Now he decides to modify the existing
KM to create an audit table each time the interface runs.
Background:
After the interface is created and tested, you may need to create a new knowledge module to
use with the interface.
In this practice, you duplicate an existing knowledge module, IKM SQL Incremental Update,
naming the new knowledge module IKM Oracle UI - Audit. You add two commands to the
knowledge module, Create Audit Table and Insert Audit Records, using command syntax
provided in text files.
Next, you duplicate an existing interface, INT-Exp-FF-RT, naming the new interface INT-EXPFF-RT. You change the new interfaces IKM selection to use the new knowledge module you
just created, IKM Oracle UI - Audit.
Finally, you execute interface INT-EXP-FF-RT and examine the audit records inserted into the
audit table created by your knowledge module.
Duplicate the knowledge module, IKM SQL Incremental Update, naming the new KM IKM
Oracle UI Audit. You insert into the KM two new commands: Create Audit Table
and Insert Audit Records.
Duplicate the interface INT-EXP-FF-RT, naming the new interface INT-EXP-FF-RT-Audit.
You change the interfaces IKM entry to use your new KM: IKM Oracle UI Audit.
Your Tasks:
1. Create the new knowledge module with new functionality to create an audit table and insert
audit records.

Practice 12-2: Developing a New Knowledge Module
If not connected, connect to the DEV_ODI_REPO work repository (User:

b.
Open ODI Designer and click the Projects tab. Select Projects > Export-FF-RT >
Knowledge Modules > Integration (IKM). Right-click IKM SQL Incremental Update and
select Duplicate Selection. In the window that follows, click Yes.

a.
Double-click Copy IKM SQL Incremental Update to edit it. Rename this KM IKM
Oracle UI Audit. Click the Details tab.
Note: If the message for Object Locking/Unlocking is displayed, click OK.
d.
Click the Details tab. On the Details screen, review the commands in the current KM.
c.
Select Insert new rows and then click the Add
icon to add the new command.

In the Command New window, name this command Create Audit Table. Select
the Ignore Errors check box. Set the Technology on Target to Oracle. Enter the
following command to create the audit table. Verify that the check boxes in the
Journalizing section are not selected. If necessary, deselect them.
Note: You can find this command in the file 12-2.txt, provided in the following
location: c:\Labs\Text.

e.
f.
Click the Details tab. Scroll down and select the Create Audit Table command.
Click the
icon several times to move the command up and place it right after the
Insert new rows step, as shown below. Select the Ignore Errors check box, as shown
in the following below. Click the Add icon again

create table <%=odiRef.getTable("L", "TARG_NAME", "A")%>_H

(
<%=odiRef.getColList("", "[COL_NAME]\t[DEST_CRE_DT]NULL",
",\n\t", "", "PK")%>,
AUDIT_DATE
DATE,
AUDIT_INDICATOR VARCHAR2(1)
)
Similarly, create the command that inserts audit records in the audit table, as shown in
the screen. Name this command Insert Audit Records. Select the Ignore Errors
check box. Set the Technology on Target to Oracle. Enter the command provided
below.
Note: You can find this command in the file 12-2.txt, provided in the following

Note: In these substitution methods, you use the following parameters:

GetTable:
L: Local naming convention. For example, in Oracle that would be

schema.table (versus R for remote: schema.table@server).
A: Automatic. It enables ODI to determine which physical schema to use (the

Data schema [D] or the Staging schema [W]).
getColList:
Notice the PK parameter. If it is used, only the columns that are part of the
primary key are included.

Insert into <%=odiRef.getTable("L", "TARG_NAME", "A")%>_H

(
<%=odiRef.getColList("", "[COL_NAME]", ",\n\t", "", "PK")%>,
AUDIT_DATE,
AUDIT_INDICATOR
)
select
<%=odiRef.getColList("", "[COL_NAME]", ",\n\t", "",
"PK")%>,
sysdate,
IND_UPDATE
from <%=odiRef.getTable("L","INT_NAME","W")%>
g.
Click the Details tab. Scroll down and select the Insert Audit Records command.
Click the
icon several times to move the command up and place it right after the
Create Audit Table step, as shown in the next screen. Click Save, and then close
the tab.

2.
Verify that your new knowledge module, IKM Oracle UI Audit, appeared in the
Knowledge Modules tree.
Modify the interface INT-EXP-FF-RT to be executed with your newly created knowledge
module. You will need to duplicate the existing interface, rename it, and then change the
IKM entry to use IKM Oracle UI-Audit.

h.
On the Projects tab, right-click the interface INT-EXP-FF-RT and select Duplicate. Click
Yes on the Confirmation screen.
b.
Double-click the interface Copy of INT-Exp-FF-RT. Change the name of the interface
to INT-Exp-FF-RT-Audit, as shown in the screen. Click the Flow tab.
a.

On the Flow tab, click Target (ODI_STAGE)-Target + Staging Area to open the IKM
Selection section. Select IKM Oracle UI Audit. Ensure that in the IKM Selection
section, FLOW_CONTROL and STATIC_CONTROL options are set to false, as shown
in the screen. Click the Save button, and then close the tab.

c.

To execute your new interface, select the interface and click the Execute button
Click OK. Click Yes to save your interface. Click OK again to start the execution.
Click the Operator tab to open ODI Operator. Click to open the All Executions node. If
necessary, click the Refresh icon
session steps.
e.
, find your new interface session, and view the
Scroll down and double-click the Create Audit Table step. View the content of the
Definition and Code tabs for this step. Close the tab.

d.
f.
Similarly, view the Insert Audit Records step information. Refer to the following
screens. Click Cancel.

Open the Oracle SQL developer and expand the ODI_STAGE connection (for the
password, enter ODI_STAGE). Select Tables node and if necessary click the Refresh
button
. Doubleclick the Audit table TRG_SALES_H, click Data tab, and verify
that your Audit table was created and populated with audit records, as shown next.
3.
In addition, you create an option for your new knowledge module to make your KM more
user-friendly. This option will enable an end user to choose when to generate audits.
a. In Designer, click the Projects tab, right-click IKM Oracle UI Audit, and select New
Option. Name this option AUDIT_CHANGES, set Type to Check Box, and Default
Value to true. Click Save and close the AUDIT_CHANGES option tab.

g.
Now you need to link this option to your steps in KM. Double-click IKM Oracle UI Audit, and click the Details tab. Double-click your new step, Create Audit Table, to edit
it, and then scroll down and click the Options.

b.
Deselect the Always Execute check box. Select AUDIT_CHANGES. This will condition
the execution of these steps with the value set by the end user. Click Save. Click the
Details tab.

c.
Repeat the previous step for the Insert Audit Records command, as shown in the
following screens. Click Save to save your KM and close the tab.

d.
Double-click INT-Exp-FF-RT-Audit to edit it. Click the Flow tab, click Target
(ODI_STAGE), and verify that the option AUDIT_CHANGES is set to true.
Execute the interface

e.
If not opened, open ODI Operator, select All Executions, and then click the Refresh
button and view the execution results. Both Create Audit Table and Insert Audit
Records steps should be present.

f.
In Designer, edit the interface to set the option AUDIT_CHANGES to false. Save your
interface and then execute your interface again

g.
In ODI Operator, click the Refresh button and view the execution results. The new KM
steps to create and populate an audit table are not executed.

h.
Chapter 12
Chapter 12 - Page 1
Use Case Scenario:

John created the new ODI project and an interface to perform the transformations described in
the previous practices. Now he needs to modify his project by adding an ODI procedure to
create a relational table and populate it with data.
Background:
A common task that is performed by using ODI is to create and populate a relational table. This
practice walks you through the steps that are needed to create a project and a procedure that
will create and populate a relational table with data. You also execute the procedure and verify
the execution within ODI Operator.
In this practice, you use the same RDBMS schema, ODI dataserver, and ODI physical schema
all named ODI_STAGEwhich you created in Practice 10-1. In the predefined project,
Procedure-CRT-TBL, you create the procedure PRD-create-populate-table.
Next, you add commands to drop, create, and populate a table, using the syntax provided in text
files.
Finally, you execute the procedure and verify that the table was created and populated with
records.
1. Create the project Procedure-CRT-TBL.
2. Create the procedure PRD-create-populate-table.
3. Add commands to drop, create, and populate a table.
Your Tasks:
1. Create new project in ODI Designer.

Chapter 12 - Page 2
Practice 13-1: Creating an ODI Procedure
Switch to the Designer Navigator. Click the Designer tab. Select the Projects tab, click
the New Project
b.
icon, and select New Project.
Enter the name of the project: Procedure-CRT-TBL. Click the Save button to create the
project and close the tab. The project appears in the tree view. Expand the ProcedureCRT-TBL project node.
Note: In this practice, you use the same RDBMS schema, ODI data server, and physical
schema that you created in Practice10-1. If you have not performed Practice 10-1,
complete Practice 10-1, steps 5 and 7 to create the RDBMS schema, the ODI source data
server, and the physical schema for your new RDBMS model.
c. Open the ODI Topology Navigator, select Physical Architecture. Expand Technologies
> Oracle > ODI _STAGE. Verify that you have the physical schema ODI_STAGE
created under ODI_STAGE data server.

Chapter 12 - Page 3
a.
Open ODI Designer. In the Projects tab, select Procedure-CRT-TBL > First Folder.
Right-click Procedures and select New Procedure.
e.
Enter the procedure name as PRD-create-populate-table. Set Target Technology to

Oracle. Click the Details tab. Click the icon
to add a step in the procedure.

Chapter 12 - Page 4
d.
In the Command: New window, enter the parameters of the procedure and the
command on the target provided in the following table. You need this command to drop
the table in case a table with this name exists. Select the Ignore Errors check box.
Parameter
Value
Name
Drop table
Technology
Oracle
Schema
ODI_STAGE
Ignore Errors
Checked
DROP table ODI_STAGE.SRC_SALES_PERSON
g.
Select the Details tab, and then click the icon

to add another step in the
procedure. In the Command: New screen, if not selected, click the Command on
Target tab. Enter the parameters of the procedure and the command provided below.
Note: You can copy this command from the 13-1.txt file, which is provided in your
Lab folder in the following location: c:\Labs\Text.

Chapter 12 - Page 5
f.
Value
Name
Create Table
Technology
Oracle
Schema
ODI_STAGE
Ignore Errors
Unchecked
CREATE table "SRC_SALES_PERSON" (

"SALES_PERSON_ID" NUMBER(8,0) NOT NULL,
"FIRST_NAME" VARCHAR2(80),
"LAST_NAME" VARCHAR2(80),
"DATE_HIRED" VARCHAR2(80),
"DATE_UPDATED" DATE NOT NULL,
constraint "SRC_SALES_PERSON_PK" primary key("SALES_PERSON_ID")
)
h.
Click the Details tab. Click the icon

SRC_SALES_PERSON table.
to enter the step to populate the
In the Command: New screen, click the Command on Target tab. Enter the
parameters and the command shown below. Click the Details tab to view your steps.
Note: You can copy this command from the file 13-1.txt, which is provided at the
following location: c:\Labs\ Text.
i.
Parameter
Value
Name
Populate table
Technology
Oracle

Chapter 12 - Page 6
Parameter
Schema
ODI_STAGE
Ignore Errors
Unchecked
Chapter 12 - Page 7

Chapter 12 - Page 8
begin
insert into ODI_STAGE.SRC_SALES_PERSON values
(11,'Andrew','Andersen','22/02/1999',sysdate);
(12,'John','Galagers','20/04/2000',sysdate);
(13,'Jeffrey','Jeferson','32422',sysdate);
(20,'Jennie','Daumesnil','28/02/1988',sysdate);
(21,'Steve','Barrot','24/09/1992',sysdate);
(22,'Mary','Carlin','14/03/1995',sysdate);
(30,'Paul','Moore','36467',sysdate);
(31,'Paul','Edwood','18/03/2003',sysdate);
(32,'Megan','Keegan','29/05/2001',sysdate);
(40,'Rodolph','Bauman','29/05/2000',sysdate);
(41,'Stanley','Fischer','37233',sysdate);
(42,'Brian','Schmidt','25/08/1992',sysdate);
(50,'Anish','Ishimoto','30/01/1992',sysdate);
(51,'Cynthia','Nagata','28/02/1994',sysdate);
(52,'William','Kudo','28/03/1993',sysdate);
end;
2.
Click Save and close the tab.
Execute your newly created procedure and verify the results.

a. Expand Procedure-CRT-TBL > Procedures, select the newly created procedure PRDcreate-populate-table, and then click the Execution button to run the procedure
.
Click OK. Click OK again.

Chapter 12 - Page 9
j.
Open ODI Operator. In ODI Operator, click the All Executions node, click the Refresh
icon, find your session, and verify that your procedure executed successfully.
c.
Open the Oracle SQL developer and expand the ODI_STAGE connection. Select
Tables node and click the Refresh button
. Doubleclick the newly created table
SRC_SALES_PERSON, click the Data tab, and verify that your table
SRC_SALES_PERSON was successfully created and populated with records as
shown in the following screen.
3.
Additionally, you create an option to delete rows from the target audit table, which you
created in Practice 12-2. To delete rows, you add a command that uses the value of the
option in the code. If the value of this option is set to Y, the command to delete records
will be executed.
a. Right-click your procedure and select New Option. Name this option
DELETE_AUDIT_RECORDS, and set Type to Value. Add the description as shown on
the screen. Set the default value of this option to Y (no quotes). Click the Save icon.

b.
Open your procedure, PRD-create-populate-table, and then click the Details tab. Click
the Add icon to add a new command.
c.
Add the new command on Target to delete records in the audit table
TRG_SALES_PERSON_H. Set the parameters as shown in the following table.
Note: You can copy this command from the file 13-1.txt, which is provided at the
following location: c:\Labs\Text.

b.
Value
Name
DELETE AUDIT RECORDS
Technology
Oracle
Schema
ODI_STAGE
Ignore Errors
Checked
d.
Click the Options tab and verify that the value of your newly created option is set to Y.
Click the Save icon.
Note: To view the inputs in the Options tab, you must click the Refresh button.
e.
Execute your procedure. In Operator, verify that the procedure executed successfully.

Parameter
f.
Open SQL Developer and expand ODI_STAGE > Tables. Open the Audit table
TRG_SALES_PERSON_H, click the Data tab, and verify that the rows were deleted
from the Audit table.

Chapter 13
Chapter 13 - Page 1
Use Case Scenario:

While working on his data integration projects, John created the ODI project and a number of
interfaces for ELT processing. Now he decides to build a procedure for handling repetitive
operations and a package to use this procedure and the interfaces.
Background:
A common task that is performed by using ODI is to create a package that executes a number
of objects (Interfaces, Procedures) in the flow. In this practice, students create an ODI
procedure and package to execute the sequence of transformations with the interfaces created
in the previous practices.
In this practice, you create a procedure, DELETE_TARGET, for deleting from the
TRG_CUSTOMER, TRG_CITY, TRG_REGION, and TRG_COUNTRY tables.
Then you create and execute a package, PKG_14-1. This package runs your new procedure,
and then runs four interfaces you defined earlier in Lessons 8 and 9, which will use these same
tables as targets:
The DELETE_TARGET procedure
Practice 8-1 interface
Finally, you run this package and review its execution in ODI Operator.
Your Tasks:
1. Create a DELETE_TARGET procedure that deletes the data in the TRG_CUSTOMER,
TRG_CITY, TRG_REGION, and TRG_COUNTRY tables in the ORACLE_LOCAL_SALES logical
schema.
a. If not open, log in to DEV_ODI_REPO and enter SUPERVISOR for the username and
SUNOPSIS for the password.

Chapter 13 - Page 2
Practice 14-1: Creating an ODI Package
In the Designer tab, click the Projects tab, and then select the Procedures node from
the HandsOnLoads > HandsOn folder. Right-click the Procedures node and select the
New Procedure option.
c.
Enter DELETE_TARGET in the Name field, and select ORACLE as the Target
Technology. Click the Details tab, and then click the Add icon
d.
In the Name Field, enter DELETE TRG_SALES. In the Schema field, select
ORACLE_ORCL_LOCAL_SALES. In the Context field, select Development.
In the Command field, enter the following code:

Chapter 13 - Page 3
b.
e.
Click the Add icon. In the Name Field, enter DELETE TRG_CUSTOMER. In the
Schema field, select ORACLE_ORCL_LOCAL_SALES. In the Context field, select
Development.
In the Command field, enter the following code:
DELETE FROM <?=odiRef.getObjectName("L", "TRG_CUSTOMER",
"ORACLE_ORCL_LOCAL_SALES", "", "D") ?>
This method returns the table name with run timedependent information, such as the
Oracle schema name that may vary depending on the context and topology. Select the
Ignore Errors check box. Select the Details tab.

Chapter 13 - Page 4
DELETE FROM <?=odiRef.getObjectName("L", "TRG_SALES",

This method returns the table name with run timedependent information, such as the
Oracle schema name that may vary depending on the context and topology. Select the
Ignore Errors check box. Select the Details tab.
Repeat the two previous steps to create the commands DELETE TRG_CITY, DELETE
TRG_REGION, and DELETE TRG_COUNTRY, which delete the tables TRG_CITY,
TRG_REGION, and TRG_COUNTRY, respectively, as shown in the following screen.
Note: To enter the commands, you may refer to the file 14-1.txt provided at the

Chapter 13 - Page 5
f.
g.
Open the Details tab to view the commands. Click the Save button, and then close the
procedure tab.

Chapter 13 - Page 6
Create a package, PKG_14-1, that runs:
The DELETE_TARGET procedure
The INT_8-1 interface

Note: These interfaces were created in Practice 8-1 and Practice 9-1.
a. Expand the Interfaces and Procedures nodes in the HandsOnLoads > HandsOn folder.
Right-click the Packages node and select the New Package option.
b.
Enter PKG_14-1 in the Name field, and then click the Diagram tab. In the tree view,
expand the Interfaces node and Procedures node. Select the DELETE_TARGET
procedure from the tree view, and then drag it to the diagram workbench. A
DELETE_TARGET step appears in the package.

Chapter 13 - Page 7
2.
Repeat the operation for the INT_8-1, INT_8-2, INT_8-3, and INT_9-1 interfaces. The
package should appear as follows.
d.
Rename your steps with the names of the tables loaded by the step. In the Diagram
window, click the step for the DELETE_TARGET procedure. Edit the Step name:
DELETE TARGET TABLES, as shown in the following screen. In the diagram, click the
empty space. The step is now renamed Delete Target Tables.

Chapter 13 - Page 8
c.
Similarly edit the names of the other steps in the diagram, as follows.
f.
Click the Step After Success tool icon

on the Package toolbar. Click the Delete
Target Tables step. Press and hold the left mouse button and move the cursor over the
Countries step. Then, release the mouse button. A green arrow appears between
these steps.

Chapter 13 - Page 9
e.
Click the Countries step. Press and hold the left mouse button and move the cursor
over the Regions step. Then, release the mouse button. A green arrow appears
between these steps. Repeat this operation to link the steps in the correct order:
Countries > Cities > Regions > Customers, as follows.
h.
Click the Save button to save this package and close the package tab.
Run this Package and review its execution in ODI Operator.

a.
Click the Execute package button

to run this package. Click OK in the Execution
window that appears, and then click OK again.

3.
g.
In ODI Operator, click the Refresh icon. In the session list, expand the All Executions
node. The session called PKG_14-1 should appear as complete. You can expand the
nodes in the session to see the steps and tasks corresponding to your procedure
commands and the interfaces that have been executed.
c.
Open the Designer tab and close the PKG_14-1 tab. Click Yes to unlock this package.

b.
Use Case Scenario:

John needs to add more complexity to the workflow by creating a user function for mapping the
values. This function will convert the values (0, 1, 2) to (Mr, Mrs, Ms). He also needs to
create a variable DELETION_FLAG for counting the number of lines in TRG_CUSTOMER and to
have the Delete Target step running only if DELETION_FLAG is greater than 0.
Background:
A common task that is performed by using ODI is using user functions and variables to add
more complexity to your workflows and mappings. This practice will explain how to use
variables, user functions, and the more advanced features in the packages.
1. In the HandsOnLoads project, define a user function group named Conversion,
containing a user function named DearConvert.
2.
3.
4.
5.
Use this function in the interface INT_9-1 to convert the values (0, 1, 2) to (Mr, Mrs,
Ms).
In ODI Designer, create a numeric variable DELETION_FLAG that counts the number of
lines in TRG_CUSTOMER.
Duplicate the PKG_14-1 package, naming the new package PKG_14-2.
Have the DELETE_TARGET procedure run only if the DELETION_FLAG variable is greater
than 0.
Your Tasks:
1. Create a user function called DearConvert in a new user function group called
Conversion. This function converts the values (0, 1, 2) to (Mr, Mrs, Ms). Implement
this function for Oracle as linked technology with a CASE WHEN expression.
Note: Remember to use the dollar sign ($) when using the parameters.
a. Select the User Functions node in the HandsOnLoads project. Right-click this node
and select New User Function.

Practice 14-2: Using ODI Package with Variables and User Functions
Enter DearConvert in the Name field, enter Conversion in the Group field, and enter
the following in the Description field:
Converts the values (0, 1, 2) to (Mr, Mrs, Ms). In the Syntax
field, enter: DearConvert($1)
Note: $1 is the parameter name you use in the decision case structure shown in the
following scren.
Click the Implementations tab, and then click the Add button.

b.
In the Implementation window, select Hypersonic SQL from the list of Linked
Technologies. Verify that Oracle technology is also selected. Enter the following code
in the Implementation syntax field. Click OK to save this implementation. Click the
Save icon, and then close the DearConvert user function tab.
Note: In Locking/Unlocking Object windows that may appear, click Yes.
Note: To enter the commands, you may refer to the file 14-2.txt provided at the
CASE WHEN $1 = '0' THEN 'Mr' WHEN $1 = '1' THEN 'Mrs'

WHEN $1 = '2' THEN 'Ms' ELSE NULL END
c.

2.
You use this function in the interface INT_9-1 to convert the source DEAR column into the
target DEAR column.
a. In the Projects tree view expand Interfaces. Double-click the interface INT_9-1 to open
it. In the Locking window, click Yes. Click the Mapping tab.

3.
In the Target datastore, select the Dear column. Edit the implementation in the
Properties panel to have the following code:
DearConvert(SRC_CUSTOMER.DEAR). Scroll down to select the Staging Area
option from the Execute on panel. Click the Save button to save the interface.
Run the INT_9-1 interface and review the conversion result.

b.
In the interface window, click the Execute button. In the Execution window, select
Development context, and then click OK. Click OK when the Session started
message appears. Close the INT_9-1 editing tab.
b.
Click the Operator tab. Select All Executions, and then click Refresh. Expand the All
Executions node. The session called INT_9-1 should appear as complete.

a.
In the Mapping tab, right-click the Target datastore and select Data. Verify that the
column DEAR was populated with Mr as shown below.

c.
Create a numeric variable called DELETION_FLAG that counts the number of lines in
TRG_CUSTOMER.
a. In the Designer, open the Projects tab, and select the Variables node in the
HandsOnLoads project. Right-click this node and then select New Variable.

4.
Enter DELETION_FLAG in the Name field, select Numeric as the Datatype, and enter 0
in the Default Value field. In the Action field, select Historize to enable viewing the
history of all values for this variable.
c.
Click the Refreshing tab. Select ORACLE_ORCL_LOCAL_SALES as the schema, and in

the Select Query field, enter the following expression. Click the Save button to save the
variable. Close the DELETION_FLAG variable tab.
Note: To enter commands, refer to the file 14-2.txt provided at the following

b.
5.
Modify this package to have the Delete Target step running only if DELETION_FLAG is
greater than 0.
a. Duplicate the PKG_14-1 package. Open the package Copy of PKG_14-1 and rename
it PKG_14-2.
SELECT COUNT(*) FROM <?=odiRef.getObjectName("L", "TRG_CUSTOMER",


Select the Diagram tab. In the project tree, and expand the Variables node. Drag the
DELETION_FLAG variable from the tree view to the diagram. Click the
Deletion_FLAG step and then rename this step Refresh Customer Count.
Ensure that the Type field is set to the Refresh variable.
Note: You need to click the step in the diagram to view the new step name.
b.

Drag the DELETION_FLAG variable from the tree view to the diagram again. Rename
this step Flag > 0?, change the Type to Evaluate Variable. In the Operator field,
select > as the operator, and enter 0 in the Value field.
d.
Right-click the Refresh Customer Count step and select First Step. Click the Next
c.
step on success tool

on the Package toolbar, and link the step Refresh
Customer Count to the step Flag >0? Using the same tool, link the step Flag >
0? to the step Delete Target tables. Click the Next step on failure tool
on
the Package toolbar, and link the step Flag > 0? to the Countries step, as shown
below. Click Save to save the package. Close the tab.

Run the new package and check if the Delete Target Tables step was executed.
a. Right-click the package PKG_14-2, and then select Execute. Click OK in the Execution
window, and then click OK when the Session started message appears.

6.
b.
In the Operator, verify that the latest session called PKG_14-2 appears as complete,
with a Delete Target Tables step executed.

Open the Designer tab. Open the package PKG_14-2 again, and then select Diagram.
To delete records from the target tables, select the Delete Target Tables step, rightclick, and select Execute Step. Click OK in the Execution window, and then click OK
when the Session started message appears.

c.
Now, when records from the target tables are deleted, execute the entire package
PKG_14-2 again. Click OK in the Execution window, and then click OK when the
Session started message appears.

d.
Open the Operator and expand the latest session called INT_14-2. Verify that the
Delete Target Tables step is no longer executed.
Note: Because the Customers tables were emptied by the execution of the Delete
Target Tables step, the value of variable Flag >0? changes when refreshed to False,
and the Delete Target Tables step is no longer executed. Close the PKG_14-2
tab.

e.
Chapter 14
Chapter 14 - Page 1
Use Case Scenario:

In addition to the group of Interfaces created earlier, John needs to create a project and an
interface to export data from a flat file and load this data into a relational table. He also needs to
verify the quality of the data loaded in the table.
Background:
one or more relational tables in the source to a relational table in the target.
In this practice, you take an interface and create a first version of it, version 1.0.0.0. Next, you
change some details of the interfaces mapping and create a second version of the interface,
version 1.0.0.1.
Then you use the ODI Version Browser and Version Comparison tool to compare these two
versions of the interface and to detect the differences between them.
Finally, you generate a PDF report of the versions, and then restore the original version.
1. Create an interface
2. Create a new version 1.0.0.0 of the interface
3. Change the interface flow and create another version of the interface, version 1.0.0.1
4. Use the Version Browser to compare versions of the interface and create a version
comparison report
Your Tasks:
1. Create a new Interface with Oracle Data Integrator.
a. If not connected, connect to the ODI work repository DEV_ODI_REPO. Log in with the
following details. Click OK.
Login name: DEV_ODI_REPO
User: SUPERVISOR
Password: SUNOPSIS.

Chapter 14 - Page 2
Practice 15-1: Working with ODI Versions
In Designer, click the Projects tab. Expand HandsOnLoads > HandsOn > Interfaces,
and select INT_9-1. Right-click this interface and select Duplicate. In the Confirmation
window, click Yes.

Chapter 14 - Page 3
b.
2.
Double-click Copy of INT_9-1. Name the new interface INT_15-1. Click Save to
save the interface. Close the INT_15-1 tab.
Create new versions of INT_15-1.


Chapter 14 - Page 4
c.
To create a new version of INT_15-1: Right-click INT_15-1 and select Version >
Create Version. On the screen that follows, view the suggested version number. Leave
this default number. Click OK.
a.

Chapter 14 - Page 5
Double-click INT_15-1 to edit it. Click the Flow tab. On the flow tab, click Target
Datastore. Select the Distinct Rows check box. Click the Save button and close your
interface tab.
c.
To create another version of this modified Interface, right-click INT_15-1 and select
Version > Create Version. On the screen that follows, click the Previous Versions
b.

Chapter 14 - Page 6
d.
View the previous (original) version of your interface. Optionally, enter the description
of the new version in the Description field. Click OK to save your new version.

Chapter 14 - Page 7
button.
Now, you explore your versions by using the Version Browser. Click ODI > Version
Browser. View your versions with all the necessary information.

Chapter 14 - Page 8
e.
Compare the newly created version.

a. With Version Browser open, select both versions: (1.0.0.0) and (1.0.0.1) for interface
INT_15-1. Right-click the selected versions and select Compare.

Chapter 14 - Page 9
3.
Select Modified Fields and deselect other check boxes. Now you have a more compact
view of your changes. Click the Print button.
c.
On the Report generation screen, select the New objects check box. Click
to specify the PDF file location.

button
b.

d. Specify the PDF file location: C:\Documents and Settings\Administrator\My

Documents\. Name your report: Practice 15-1 Interfaces comparison.
Click Save. Your report will be saved in C:\Documents and
Settings\Administrator\My Documents\Practice 15-1 Interfaces comparison. Click
Generate. Click OK.
Open your PDF file with your report. Scroll down to view the report. Close the report.
Click OK to close the Versions Comparison tool.

e.
Restore the original version of your interface.

a. In the Version Browser, select INT_15-1 version 1.0.0.0, and click the Restore this
version
icon. Click OK. Click OK again.

4.
In the Objects tab, double-click interface INT_15-2. Click the Version tab. View your
current restored version: 1.0.0.0. Click OK.
b.

Chapter 15
Chapter 15 - Page 1
Use Case Scenario:

Earlier, John created the ODI procedure to create a relational table and populate it with data.
Now John needs to create an ODI scenario and schedule its execution.
Background:
A common task that is performed by using ODI is to create an ODI scenario and schedule its
execution. You already developed the ODI procedure that creates a relational table and
populates the relational table with data.
In this practice, you learn how to create and schedule an ODI scenario to run the procedure you
created in Practice 12-1.
First, in the Designer Navigators Projects tab, you generate a scenario for the PRD-createpopulate-table procedure.
Then, in Topology Navigator, you verify connection to ODI Agent.
Next, in Designer Navigator, you schedule the scenario with ODI Agent.
You switch back to Topology Navigator to review the scheduling of the agent.
Finally, in Operator Navigator, after the scheduled scenario execution time, you verify that the
scenario has executed.
Your Tasks:
1. Create a new scenario with Oracle Data Integrator.
a. If not connected, connect to the Work repository WORKREP. Select DEV_ODI_REPO
from the Login Name drop-down list. Enter SUPERVISOR in the User field and
SUNOPSIS in the Password field. Click OK to log in.

Chapter 15 - Page 2
Practice 16-1: Creating and Scheduling an ODI Scenario
In ODI Designer, click the Projects tab. On the Projects tab, expand the project:
Procedure-CRT-TBL > First Folder > Procedures. Right-click the PRD-createpopulate-table procedure and select Generate Scenario.
c.
Name the scenario PRD_CREATE_POPULATE_TABLE. Set the Version to 001. Click

OK.

Chapter 15 - Page 3
b.
2.
Expand the PRD-create-populate_table procedure and expand Scenarios. Right-click

the PRD_CREATE_POPULATE_TABLE scenario to view the possible options, as
Note: The scenario has now been successfully created. You can now execute the
scenario directly, use the scenario within a package, or schedule the scenario within
ODI.
Now you need to schedule an ODI scenario with ODI Agent. To schedule the scenario,
perform the following steps:
a. In Topology Navigator, verify connection to ODI agent, as shown in the following
screen.
Note: If ODI Agent is not set up and running, you must perform the steps specified in
Practice 3-1 before continuing.

Chapter 15 - Page 4
d.
Expand the PRD-create-populate-table procedure. Expand Scenarios >

PRD_CREATE_POPULATE_TABLE Version 001. Right-click Scheduling and select
New Scheduling.
Note: To schedule a scenario, an ODI Agent must be set up. If an ODI Agent is not set
up within the ODI Topology Manager, perform Practice 3-1, Setting Up and Installing
an ODI Agent.

Chapter 15 - Page 5
b.
On the screen that follows, select the agent where the scheduled scenario will run:
localagent. Set Context as Development and log level to 5. Set Execution to Simple
and click the
button. Set the execution time to approximately five minutes from the
current system time, as shown in the following screen. Click the Save button.

Chapter 15 - Page 6
c.
d.
Expand Scheduling and verify that the DEVELOPMENT / localagent entry is now
inserted under Scheduling.

Chapter 15 - Page 7
Start Topology Manager to review the scheduling of the Agent. In the Physical
architecture, expand the Agents node and double-click localagent. On the localagent
screen, click Update Schedule. On the screen that follows, click OK. Click OK again.

Chapter 15 - Page 8
e.
3.
Click the View Schedule button. The screen that appears shows you the scheduling
information. Click OK to close schedule. Close the tabs: Localagent tab and Scenario
Scheduling.
To verify the execution of the scheduled scenario, perform the following steps:
a. Click the ODI Operator tab to open ODI Operator. In ODI Operator, click the Session
List tab. Wait until the scheduled execution time to view the execution results, and then
click the Refresh icon.
b.
Expand: Physical Agent > localagent -1> PRD_CREATE_POPULATE_TABLE, and

view the execution results for the PRD-create-populate-table procedure. Note the
execution time of this scenario. That is the time that you scheduled with ODI Agent.
You have now successfully scheduled a scenario with an agent scheduler.

Chapter 15 - Page 9
f.
Chapter 16
Chapter 16 - Page 1
Use Case Scenario:

John is responsible for data loading, transformation, and validation. He created a project and an
interface to export data from a flat file and load this data into a relational table. Now John needs
to verify the quality of data loaded in the table.
Background:
one or more relational tables in the source to a relational table in the target and to export data
from a flat file to a relational table. In this practice, you perform data quality control for the
interface created in Practice 10-1.
First, for a certain datastore, you verify that the primary key constraint is marked static, and two
columns are marked mandatory with static control.
You then create an interface using that datastore as a target.
In the interfaces Flow tab, you set STATIC_CONTROL to True. In the Controls tab, you ensure
the knowledge module is set to CKM SQL (a knowledge module that you will import) and you
set maximum allowed errors to 5.
For two columns in the target datastore, you will select the Check Not Null check box so that
control errors will be generated if these columns are not loaded.
You will run the interface with Flow Control set to FALSE. You will verify that there are control
errors on three records, and that the three records with errors were loaded into the target
datastore.
Finally, you will rerun the interface, with Flow Control set to TRUE, and verify that errors are
excluded from the target datastore.
Your Tasks:

Chapter 16 - Page 2
Practice 17-1: Enforcing Data Quality with ODI Interface
If not connected, connect to the Work repository, WORKREP. To connect, click Connect to
Repository. Select DEV_ODI_REPO from the Login Name drop-down list. Enter
SUPERVISOR in the User field and SUNOPSIS in the Password field. Click OK to login.
2.
Modify INT-Exp-FF-RT (created in Practice 10-1) to enable checking data quality in the
target table.
a. Click the Projects tab. Select Knowledge Modules > Check (CKM). Right-click Check
(CKM) and select Import Knowledge Modules:

Chapter 16 - Page 3
1.
In the File import directory field, select CKM SQL and click OK. Close the Import
Report window. Verify that CKM SQL was successfully imported and is shown in the
tree view.
b.

Chapter 16 - Page 4
In the Models tab, expand Oracle_RDBMS1 > TRG_SALES_PERSON > Constraints,

and then double-click TRG_SALES_PERSON_PK. Click the Control tab and verify that
Static is selected.
d.
In the model Oracle_RDBMS1, expand TRG_SALES_PERSON > Columns, doubleclick the column LAST_NAME, and then click the Control tab. Select Static to enable
static control. Select the Mandatory check box. Click the Save button. Repeat the same
step to enable Static control for the DATE_HIRED column. Save your changes and
close the tabs.
c.

Chapter 16 - Page 5
e.
In the Projects tab, expand the Export-FF-RT project, and then duplicate the interface
INT-EXP-FF-RT. Open the copy of the interface and rename it as INT-EXP-FF-RTQuality, and then click the Mapping tab.

Chapter 16 - Page 6
Delete the filter for the column SALES_PERSON_ID, as shown in the following screen,
and then click the Flow tab.

Chapter 16 - Page 7
f.
In the Flow tab, Click Target + Staging Area (ODI_STAGE) to open the Options
section. Set the static control option to true. Click the Controls tab.

Chapter 16 - Page 8
g.
On the Controls tab, ensure that your KM is set to CKM SQL. Set the maximum
number of errors allowed to 5. Leave the other options with the default values. Click the
Mapping tab.
i.
In Target Datastore, select the LAST NAME column, and then select the Check Not
Null check box. Repeat the same step for the DATE HIRED column. Click the Save
button to save your changes.

Chapter 16 - Page 9
h.
Execute your Interface

. Click the Execution tab to view the execution results with
the number of errors, as shown in the screen.
Note: You may need to click the Refresh
icon to view your last execution.

j.
On the Models tab, right-click the TRG_SALES_PERSON target datastore and select
Control > Errors. View the records with errors as shown in the screen:
l.
Right-click the TRG_SALES_PERSON datastore and select View Data. Verify that the
rows with errors are still inserted in the target datastore. Close the
TRG_SALES_PERSON data tabs.

k.
m. Click the INT-EXP-FF-RT-Quality tab. On the Interface screen, click the Flow tab.
Set Flow Control to true. Save your changes, and then execute the interface

On the Models tab, right-click TRG_SALES_PERSON and select View Data. Verify that
the rows with errors are excluded from the data in the target datastore. Close the tabs.

n.
Chapter 17
Chapter 17 - Page 1
Use Case Scenario:

As a database administrator, John is responsible for data loading, transformation, and
validation. He wants to be able to detect changes in his source environment. For that purpose,
he needs to implement Changed Data Capture in his data integration project.
Background:
A common task that is performed by using ODI is to implement Changed Data Capture. In this
practice, students implement Changed Data Capture to detect changes in the source
environment for the interface created earlier in Practice 8-1. You will capture changes of data in
the SRC_CITY table in the Oracle Sales Application model. Then, you modify the interface to
process changed records only.
In this practice, you perform change data capture in an interface, using the JKM Oracle
Simple knowledge module.
First, you import this knowledge module, and create a model by using this journalizing
knowledge module.
Then you create an interface by using the IKM Oracle Incremental Update knowledge
module, specifying capture of journalized (changed) data only.
1. Import the JKM Oracle Simple knowledge module.
2.
3.
4.
5.
6.
Create a model, Oracle_RDBMS2, specifying this knowledge module in the Journalizing

tab.
Reverse-engineer the model, verifying the resulting structure.
Add the models SRC_SALES_PERSON table to CDC, and start the Journal by using the
default subscriber SUNOPSIS.
Use Data viewer to change data in the table and verify in Journal Data that the data change
was captured.
Create an interface to process changed data only.
Your Tasks:
1. Import the appropriate JKM in the project.
a. If not open, log in to the WORKREP Work repository with the login name
DEV_ODI_REPO (enter SUPERVISOR for username and SUNOPSIS for password).

Chapter 17 - Page 2
Practice 18-1: Implementing Changed Data Capture
Click the Projects tab. Expand the Procedure-CRT-TBL > Knowledge Modules node,
right-click Journalization (JKM), and select Import Knowledge Modules.
c.
Select JKM Oracle Simple to import and click OK. Close Import Report.

Chapter 17 - Page 3
b.
In the Models tab, create a new model named Oracle _RDBMS2. For Technology,
enter: Oracle. Select the logical schema ODI_STAGE. Click the Reverse Engineer tab
and set Context to development. Verify the setting, as shown in the following screen.
Click the Journalizing tab.
Note: The table SRC_SALES_PERSON was created in the ODI_STAGE schema in Practice
13-1.

Chapter 17 - Page 4
d.
In the Knowledge Module menu, select JKM Oracle Simple.Procedure-CRTTBL, as shown in the following screen. Click the Save icon
then close the tab.
f.
to save your model and
Reverse-engineer the model Oracle_RDBMS2. Expand this model and verify its
structure as follows.

Chapter 17 - Page 5
e.
2.
Set up the CDC Infrastructure. You will start the CDC on the SRC_SALES_PERSON table in
the Oracle_RDBMS2 model.
a. To add the table to CDC, expand the Oracle_RDBMS2 model, right-click the
SRC_SALES_PERSON table, and select Change Data Capture > Add to CDC. Click Yes
to confirm.

Chapter 17 - Page 6
Click the Refresh
icon. The small yellow clock icon is added to the table
. Right-click the SRC_SALES_PERSON table again and select

Changed Data Capture > Start Journal.

Chapter 17 - Page 7
b.
In this practice, you use the default subscriber SUNOPSIS. For that reason, you do not
have to add another subscriber. Click OK to confirm that your subscriber is
SUNOPSIS. In the Information window, click OK again. Wait several seconds, then
click Refresh
green now
and verify that the tiny clock icon at the SRC_SALES_PERSON table is
. This means that your journal has started properly.

Chapter 17 - Page 8
c.
3.
Click the ODI Operator icon to open the Operator. Click Refresh. Select All Executions
and verify that the SRC_SALES_PERSON session executed successfully.
View the data and the changed data.

a. In the Designer window, open the Models tab. Right-click the SRC_SALES_PERSON
datastore and select Data.
b.
Select the row with SALES_PERSON_ID = 11. Change the value of the LASTNAME
column to Anderson. Similarly, select the row with SALES_PERSON_ID = 51, and
then change the value to Smith. Save your changes and close the tab.

Chapter 17 - Page 9
d.
Right-click the table again and select View Data. Scroll down, and verify that the rows
are modified. Close the tab.

c.
To verify that your changed data is captured, right-click SRC_SALES_PERSON, and

select Change Data Capture > Journal Data. Find the captured changed records in the
journal data. Close the tab.

d.
Create an interface that processes captured data changes. The interface loads the
TRG_SALES_PERSON_CDC datastore in the Oracle_RDBMS1 model with the content of the
SRC_ SALES_PERSON table from the Oracle_RDBMS2 model. The purpose of this
interface is to process and load only changed data.
a. First you need to add one more knowledge module. In ODI Designer, click the Projects
tab, and then expand the Export-FF-RT project. Import the new Knowledge Module:
IKM Oracle Incremental Update. Close the report.

4.
Now you need to create one more target datastore to store only changed data. In the
Models tab, expand OracleRDBMS1, duplicate the TRG_SALES_PERSON datastore,
and rename the copy as TRG_SALES_PERSON_CDC. Save the
TRG_SALES_PERSON_CDC datastore and then close the tab.

b.
Open data in the TRG_SALES_PERSON_CDC datastore, and then click the Delete
Current Row icon repeatedly to delete all the rows. Save your changes and close the
tab.

c.
In the Projects tab, expand Export-FF-RT > First Folder > Interfaces. Right-click
Interfaces, and then select New Interface.
e.
In the Interface: NEW window, enter INT_SALES_PERSON_CDC as the name of the

interface. Ensure that the Optimization Context is Development. Click the Mapping tab.
f.
Open the Models tab. In the tree view, expand the Oracle_RDBMS1 model. Drag the
TRG_SALES_PERSON_CDC datastore from the tree view to the Target Datastore zone.
Expand the Oracle_RDBMS2 model and drag the SRC_ SALES_PERSON datastore

d.
from the model tree to the Sources zone of your diagram. Click Yes to perform
automatic mapping. Save your interface.

Right-click the caption of the source datastore and select Data. Scroll down to preview
the current source data. Close the Data window.

g.
Click the Flow tab, click the Staging Area caption, and verify that the selected IKM is
IKM Oracle Incremental Update. Select Distinct Rows.

h.
i.
Now you modify this interface to process only the changed data. Click the Mapping
tab. Click the source datastore. In the Diagram property panel, select the Journalized
Data only check box.

To check the new source data set, repeat step d. View your data again. Only the
changed data should be visible. Close the data window.

j.
5.
Save your interface and close the tab. Execute the interface to process only journalized
records.
Verify the execution results.

a. Open the Operator. Click Refresh. Expand the All Executions node and verify that your
session, INT_SALES_PERSON_CDC, executed successfully.
b.
View the data in the TRG-SALES_PERSON_CDC datastore and verify that only three
changed rows are inserted in the target datastore.

k.
In the Models tab, right-click the SRC_SALES_PERSON datastore and select Drop Journal.
Click OK, and then click OK again. Right-click the SRC_SALES_PERSON datastore again,
and then select Remove from CDC. Click Yes to confirm removing the datastore from CDC.

6.
Chapter 18
Chapter 18 - Page 1
Use Case Scenario:

As a database administrator at FN Enterprise, John is responsible for performing database
management and integration tasks on various resources within the organization. John is also
responsible for enforcing the ODI security policies. To set his ODI environment, he needs to set
up the security with ODI.
Background:
Using the ODI Security Manager module, you can manage security in Oracle Data Integrator.
In this practice, you explore the security features of ODI Security Manager. You create a profile,
grant 3 methods (actions) to the profile, and create a new ODI user to whom you assign that
profile.
You then assign the profile to your new user, and grant a specific method (View) for a specific
object (Scheduling) for your new user. You also define user parameters that enable specific
functionality for your new user.
Finally, you define password policies that control the case sensitivity and length of user-defined
passwords.
1. In ODI Security Navigator, expand the Profiles panel and duplicate the Repository Explorer
profile, naming the new profile REVIEWER. You grant three methods to the REVIEWER
profile: Compare with version, Duplicate, and Export from object Model.
Note: You may need to click the View menu and open the Security Navigator.
2. Create a new ODI user, INT_PROJECT_REVIEWER.
3.
4.
5.
6.
Assign the new profile REVIEWER to your newly created user. To connect to ODI Master
and Work repositories, assign the built-in profile CONNECT, to the new user
INT_PROJECT_REVIEWER.
Grant the View method for the Scheduling object to user INT_PROJECT_REVIEWER.
Define user parameters to enable specific functionality for INT_PROJECT_REVIEWER.
Define password policies to enforce passwords to be uppercase and greater than 8
characters.
Your Tasks:
1. To define an ODI security policy, you need to create an appropriate profile for working
methods used in your project.
a. Start Oracle Data Integrator and connect to the Master repository. For Login Name,
enter Master Repository. Enter SUPERVISOR for user and SUNOPSIS for
password. Click the Profiles tab.

Chapter 18 - Page 2
Practice 19-1: Setting Up ODI Security
From the View menu, open the ODI Security Navigator. Open the Profiles tab. Rightclick the generic REPOSITORY EXPLORER profile and select Duplicate Selection. Click
Yes to confirm.

Chapter 18 - Page 3
b.
Double-click Copy of REPOSITORY EXPLORER to edit.
d.
Rename your new profile REVIEWER. Click the Save button to save this profile. The
profile REVIEWER appears in the Profiles tree structure.

Chapter 18 - Page 4
c.
Assign the appropriate authorizations to REVIEWER.

a. Open the Objects Tab. In the Profiles tab, expand REVIEWER > Model, as shown
below. Only the View method is permitted for Model now.

Chapter 18 - Page 5
2.
b.
In the Objects tab, expand Model and select the method Compare with Version.
Drag the Compare with Version method to the profile REVIEWER. In the
Confirmation window, click Yes.

Chapter 18 - Page 6
c.
Repeat step c to add the methods Duplicate and Export... to the profile
REVIEWER. In Profiles, expand REVIEWER > Model, and verify that the methods

Chapter 18 - Page 7
3.
Create a new ODI user.

a. Click the Users tab and select New user. The New User window opens.

Chapter 18 - Page 8
Compare with version, Duplicate, and Export... are added to the object
Model, as shown in the following screen. Save the profile REVIEWER and close the tab.
Name the new user: INT_PROJECT_REVIEWER. Click Enter a password.
c.
Enter the password (INTEGRATION), and then confirm this password. Do not select the
Allow expiration date check box. Click OK. Click the Save button
to save this new
user. User INT_PROJECT REVIEWER is now displayed in the Users tree structure.

Chapter 18 - Page 9
b.
Assign the profile REVIEWER to user INT_PROJECT_REVIEWER.

a. Make sure that both the Profiles and Users panels are displayed together in ODI
Security Navigator. Click the profile REVIEWER in the Profiles panel and drag it to user
INT_PROJECT REVIEWER in the Users panel. Click Yes to confirm granting the profile.

4.
In the Users panel, expand the INT_PROJECT REVIEWER > Profiles node and
verify that profile REVIEWER was assigned to this user.
c.
To connect to ODI Master and Work repositories and other objects, assign the built-in
profile CONNECT to your new user. Select the profile CONNECT and drag it to user
INT_PROJECT REVIEWER. Click Yes to confirm granting CONNECT to your new user.

b.
Verify that the profiles CONNECT and REVIEWER are added to your new user:
e.
You can also grant privileges to use certain methods for objects directly to your user.
Ensure that the Objects and Users panels are open. In the Objects panel, scroll down
and then expand the object Scheduling. Select View. Drag this method to
INT_PROJECT REVIEWER.

d.
f.
5.
Verify that authorization to the object Scheduling with the method View was added
to user INT_PROJECT_REVIEWER, as shown in the following screen.
Connect your new user to the ODI Work repository and verify your access to ODI artifacts.

From the ODI menu, select Disconnect DEV_ODI_REPO. Connect to your work
repository as the newly created user. Select DEV_ODI_REPO for the Login Name.
Enter INT_PROJECT_REVIEWER for the user and INTEGRATION for the password.
b.
In the Designer tab, click the Projects tab and Models tab, and then expand your
projects and models to verify that you have access to view all your artifacts.

a.
Define user parameters so that the user can enable specific ODI functionality. Ensure that a
help message is displayed if an interface diagram is empty and objects remain unlocked
when opening. In addition, you may want to set a delay between two refreshes in seconds
and the number of elements displayed in a branch of the Operator tree view.
a. In ODI Security Manager, select ODI > User Parameters.

6.
Edit the user parameters as shown in the following table. Click OK. Click the ODI menu
and select Disconnect DEV_ODI_REPO to close this user connection.
Parameter
Value Functionality
Help for Interface Diagram 1
Display a Help message when the Interface

Diagram is empty
Lock object when opening
Lock object when opening
Delay between two

refreshes (seconds)
Operator Display limit

(0=no limit)
200
Inter-refresh delay
Number of elements displayed in a branch of the
Operator tree view

b.
Open your connection with user SUPERVISOR. Select Security Navigator. Define
Password Policies. These policies consist of a set of rules that will be checked when the
password is defined by the user.
a. From the ODI menu, select Disconnect DEV_ODIREPO. Connect to
DEV_ODI_REPO with user SUPERVISOR. For the password, enter SUNOPSIS. Open
Security Navigator. Click the
Add a Policy icon.
icon, and then select Password policy. Click the

7.
Name this policy Policy 1. Enter the rule description as shown in the following
screen. Set Conditions to match to All. In the Rules section, click Text and select is
uppercase. Click the add rule button (with the + sign).
c.
Enter another rule: Length >= 8. Click OK.


b.
On the screen that follows, select the Active check box. Select the Passwords are
valid for check box, and set it to 30 days. Click OK to save this Password policy. Click
OK again. Close the Security Navigator tab.

d.
Use Case Scenario:

Oracle Data Integrator provides an extension integrated into the Fusion Middleware Control
Console (Enterprise Manager). The Oracle Data Integrator components can be monitored as a
domain through this console, and administrators can have a global view of these components,
along with other Fusion Middleware components from a single administration console. John
decided to begin using this feature. He created the Web Logic Server (WLS) domain, ODIDOMAIN. Now John needs to deploy and configure the ODI Java EE Agent with the existing
WLS domain. He also needs to configure the ODI Enterprise Manager and ODI Console Plugin with WLS.
Background:
In this lab, you perform the steps needed to deploy and configure the ODI Java EE Agent,
Enterprise Manager11g, and ODI Console plug-in to an existing WLS domain. You use
Enterprise Manager 11g and ODI Console to access your ODI objects.
1. Deploy and configure the ODI Java EE agent, Enterprise Manager, and ODI Console
with the existing WebLogic domain.
2. Connect to the WebLogic Server and managed server, odi_server1.
3. Use Enterprise Manager to administer ODI.
4. Use ODI Console to explore the ODI environment.
Your Tasks:
1. Deploy and configure the ODI Java EE agent and Enterprise Manager on the existing
WebLogic domain, ODI-DOMAIN.
Note: This domain was precreated for this practice.
a. In Topology Navigator, open Physical architecture and then create a new ODI Agent.
Name this agent OracleDIAgent. Set the port to 8002 and Host to localhost. Verify
that the Web application context is set to oraclediagent, as shown below. Save
your new physical agent.
Note: The agent name is case-sensitive! Use the exact name OracleDIAgent, as

Practice 19-2: Integration with Enterprise Manager and Using ODI

Console
In the Logical architecture, create a new logical agent with the same name as your new
physical agent, OracleDIAgent. Link this logical agent to the physical agent
OracleDIAgent in all three contexts, as shown below.
c.
d.
Extend the WebLogic server domain ODI-DOMAIN with the ODI agent application.
To deploy and configure domains with WLS, you start the config.bat file from the ODI
Home Install directory C:\Oracle\Middleware\Oracle_ODI1\common\bin.
Start the command shell and change directory to

b.
e.
Select Extend an Existing WebLogic Domain, and then click Next.
f.
Select the WebLogic domain directory ODI-DOMAIN, as shown below. Click Next.

C:\Oracle\Middleware\Oracle_ODI1\common\bin. Execute the command

config, which starts the Configuration Wizard.
In the screen that follows, select Oracle Data Integrator Agent 11.1.1.1 (Oracle
JRF will then also be selected; leave this option selected). Select the Oracle
Enterprise Manger Plugin For ODI 11.1.1.0, which will also include the Oracle
Enterprise Manager 11.1.1.0. Also select Oracle Data Integrator-Console-11.1.1.0.
Click Next. In the screen that follows, click OK to replace the existing component.

g.
h.
In the next screen, accept the default application location. Click Next.

The wizard will set up the ODI repository connection within the domain server. During
the wizard configuration, the repository connection information must be supplied. Click
the check boxes next to ODI Master schema, and next to ODI Work schema. Configure
the JDBC component schema as shown in the following table. Click Next.
Database Connection (Master Repository)
Parameter
Value
Vendor
Oracle
Driver
Oracles driver (Thin) for

Service connections
Schema Owner
DEV_ODI_REPO
Schema Password
oracle1
DBMS/Service
orcl
Host Name
localhost
Port
1521

i.
Verify that the test was successful (if not, correct any connectivity settings). Click Next.
k.
In the next screen, select Managed Servers, Clusters and Machines. Click Next.

j.
Set Listen port to 8002 for managed server odi_server1. Click Next.
m. In the Configure Clusters screen, click Next.

l.
In the Configure Machines screen, click Next.
o.
The Assign Servers to Machines screen will already have the odi_server1 assigned to
localODImachine. Click Next.

n.
Review the Configuration Summary, and then click Extend. When the domain is
created, click Done.

p.
Connect to the WebLogic server and managed server odi_server1.

a. In the command shell, change directory to the directory of the WLS Home C:\Oracle\Middleware\user_projects\domains\ODI-DOMAIN\bin. Execute
the startweblogic command.

2.
Security must be set up for the JAVA EE application to have access to the ODI
repository. The entry will be created within the credential store, which will allow the
JAVA EE Agent to authenticate itself to be able to use the required resources. This
user should be a user that is already set up in the ODI Security. In this practice, we use
user SUPERVISOR. To do this, you execute Web Logic Scripting Tool (WLST),
connect to our running Admin server and add the credential store. To start WLST, in
the new command window, change directory to the WLS_HOME common bin C:\Oracle\Middleware\oracle_common\common\bin, and then execute the
command wlst.
c.
To connect to the running Admin server, execute the following command:

connect('weblogic','welcome1','t3://localhost:7002')

b.
Execute the following command to add the correct credential store for ODI Supervisor:
createCred(map="oracle.odi.credmap", key="SUPERVISOR",
user="SUPERVISOR", password="SUNOPSIS", desc="ODI SUPERVISOR
Credential").
Also execute the command to add the correct credential store for the domain ODIDOMAIN:
createCred(map="oracle.odi.credmap", key="ODI-DOMAIN",
user="weblogic", password="welcome1", desc="ODI-DOMAIN
Credential").
To exit WLST, execute the command exit().
Note: All commands are case-sensitive! You can copy commands from the text file
19-2.txt provided in the c:\LABS\text folder.
Note: During run time, the JAVA EE Agent will access this credential store authentication.
e.
To start managed server odi_server_1, change directory to WLS Home C:\Oracle\Middleware\user_projects\domains\ODI_DOMAIN\bin, and use
the execute command StartManagedWeblogic odi_server1. For Username,
enter weblogic. For the password, enter welcome1. Verify that your managed server
is started in RUNNING mode.

d.
f.
From ODI Designer, test connectivity of your configured ODI Java EE agent. Click OK.

Use Enterprise Manager to administer ODI.

a. Start the browser and enter http://localhost:7002/em. Log in to Enterprise
Manager. For the user, enter weblogic. For the password, enter welcome1. On the
screen that follows, click Continue.
b.
With Enterprise Manager, a process and resources can be monitored and managed.
You can explore the deployed application by clicking on each link. You can see

3.
c.
Expand odiconsole node. Then click MASTER REPOSITORY to view more details.
Note: Your information may differ from the information provided on these screens.

running processes, workload, log file information, and more. Drill down into ODI objects
by expanding ODI in the left panel, as shown in the following screen.
Click the OracleDIAgent to see the Java EE agent information.
e.
Click the localagent node to see details for the standalone agent.

d.
Expand the Application Deployment node, and then click oraclediagent. View the
WebLogic server application deployment information.

f.
Use ODI Console to explore the ODI environment.

a. In the browser, open the new window, and then enter
http://localhost:8002/odiconsole to start the Oracle Data Integrator Console.
To log in, enter SUPERVISOR for the user ID, and enter SUNOPSIS for the password.

4.
Click the Design Time tab. Expand Projects, Models, and Topology.
c.
Select the Export-FF-RT project, and then click the View icon:

b.
Scroll down and click the First Folder link. Select the Interfaces tab. Explore the
interfaces created in your Export-FF-RT project.

d.
Click other tabs. Explore the different ODI objects in your project.
f.
Similarly explore models in your Work repository. To explore the datastores, scroll
down and select Sub-Model Name. Scroll down and view the datastores.

e.
Stop WebLogic server.

a. To stop managed server odi_server_1, change directory to WLS Home C:\Oracle\Middleware\user_projects\domains\ODI_DOMAIN\bin, and
then execute the command stopManagedWebLogic odi_server1. For the user
name, enter weblogic. For the password, enter welcome1.
b.
To stop the WebLogic server, execute the command stopWebLogic.

5.
Chapter 19
Chapter 19 - Page 1
Use Case Scenario:

John created the procedure, which creates a relational table and populates it with data. Now,
John needs to generate a scenario and create an ODI public Web service to execute the
scenario.
Background: This practice has two aims: 1) To teach you how to execute a scenario through
the ODI public Web service and 2) To become familiar with the use of the
OdiInvokeWebService tool. Therefore, the OdiInvokeWebService tool will be used to
invoke the ODI public Web service that commands an agent to connect to a given Work
repository, and to start a specific scenario. In this practice, you use the interface created in
Practice 10-1.
1. Create and execute a new scenario, INT_EXP_FF_RT.
2. Create a new package, OdiInvokeWebService.
3.
4.
5.
6.
Select the OdiInvokeWebService tool from the toolbox and create the corresponding
step in the package.
Define parameters of the Web service by using the Advanced dialog box and SOAP Editor.
Invoke your Web service from the SOAP Editor to execute the scenario INT_EXP_FF_RT.
View the response and verify the execution results.
Your Tasks:
1. If not connected, connect the Work repository, WORKREP. To connect, click Connect to
Repository. Select DEV_ODI_REPO from the Login Name drop-down list. Enter
SUPERVISOR in the User field and SUNOPSIS in the Password field. Click OK to log in.

Chapter 19 - Page 2
Practice 20-1: Executing an ODI Scenario Through the ODI Public Web
Service
In the ODI Designer tab, expand the project Export-FF-RT > First Folder >
Interfaces. Right-click the interface INT_EXP_FF_RT, and then select Generate
Scenario. Name the new scenario: INT_EXP_FF_RT. Set the version to 001.
b.
In the Topology Navigator, verify connection to your standalone agent localagent.

Note: Ensure that your standalone agent is created and successfully started. To create
and start an ODI agent, refer to Practice 3-1.
a.

Chapter 19 - Page 3
Expand the interface and execute a newly created scenario, as shown below. For
Agent, select localagent. Click OK to confirm the execution.

Chapter 19 - Page 4
c.
d.
To view the results of the execution in Operator, click the Operator icon
on the
Designer toolbar. Click Refresh. Expand the All Executions node. The
INT_EXP_FF_RT session should appear as complete.

Chapter 19 - Page 5
.
Create a new package by using the OdiInvokeWebService tool.
a. On the Projects tab, expand the project Procedure-CRT-TBL > First Folder >
Packages. Right-click Packages and select New Package. Enter
OdiInvokeWebService in the Name field, and then click the Diagram tab.

Chapter 19 - Page 6
2.
Scroll down and select the OdiInvokeWebService tool from the toolbox. Click the
diagram workbench. An OdiInvokeWebService tool step appears in the package.

Chapter 19 - Page 7
b.
In the Properties panel, retain the default name OdiInvokeWebService 1 for the Step
name field. Scroll down, and define the parameters in the Properties panel as follows:
Parameter
Value
WSDL URL
- Leave blank -
Port Type
- Leave blank -
Operation
- Leave blank -
XML Request
- Leave blank -
Request File
- Leave blank -
Storage Mode for Response File
FILE_APPEND
File Encoding for Response File
ISO8859_1
XML Encoding for Response File
ISO8859_1

Chapter 19 - Page 8
c.
C:/TEMP/WebServiceToolStep
HTTP User
- Leave blank -
HTTP Password
- Leave blank -
Execution Timeout (ms)
- Leave blank -
d.
Click the Advanced button. A new window opens. Enter

http://localhost:20910/oraclediagent/OdiInvoke?wsdl for the Web
Service Description File (WSDL) URL field. Click the Connect to WSDL button .
The appropriate port OdiInvokePortType is automatically detected and the available
operations are displayed at the left.
e.
Select the invokeStartScen operation in the left panel and then enter the parameters in
the request parameter fields as provided in the following table. Your SOAP Editor panel
should appear as follows.
Note: Press Enter each time to confirm your entries.
Response File
Parameter
Value
<OdiUser>
SUPERVISOR

Chapter 19 - Page 9
SUNOPSIS
<WorkRepository>
WORKREP
<ScenName>
INT_EXP_FF_RT
<ScenVersion>
001
<Context>
DEVELOPMENT
<LogLevel>
<SyncMode>
True
<OdiPassword>
f.
Click the Source tab to view the scenario request. Click the Remove Blank Optional
Elements icon
to remove all blank optional elements from the query. This is
necessary to construct a valid query. The request should be as shown below.
Note: You can also select the Clean up before execution check box
. This option
automatically deletes the empty optional elements in the SOAP request.

Invoke your Web service.

a.
To invoke your Web service, click the Invoke Web Service

icon. Click the SOAP
Editor tab. The response is displayed in the right panel of the SOAP Editor. Verify that
your Web service processed successfully, as shown in the screen.

3.
Click the Source tab again to view the scenario response. The response should be as
shown in the following right panel. Click OK to close the window. Click the Save button
to save your package and close the tab.
b.

In ODI Operator, verify that scenario INT_EXP_FF_RT successfully executed.

c.

D64974GC10 Ag PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

D64974GC10 Ag PDF

Uploaded by

Copyright:

Available Formats

THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM ONLY.

COPYING eKIT MATERIALS FROM THIS COMPUTER IS STRICTLY PROHIBITED

Oracle University and Egabi Solutions use only

Oracle Data Integrator 11g:

Oracle University and Egabi Solutions use only

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 2 .............................................................................................................................. 1-1

Oracle Data Integrator 11g: Integration and Administration Table of Contents

Oracle University and Egabi Solutions use only

Oracle University and Egabi Solutions use only

Practices for Lesson 20 ............................................................................................................................ 19-1

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Oracle Data Integrator 11g: Integration and Administration Table of Contents

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 2

Oracle University and Egabi Solutions use only

Practices for Lesson 2

Oracle University and Egabi Solutions use only

Practices for Lesson 2: Flow of Data

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 2

Use Case Scenario:

Create SNPM1 database user for

Create master repository

Practices for Lesson 2

Oracle University and Egabi Solutions use only

Practice 2-1: Creating and Connecting to ODI Master and Work

Start the SQL Developer by selecting Start >

Oracle SQL Developer

In Oracle SQL Developer, click + to expand

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 2

Oracle University and Egabi Solutions use only

Oracle SQL Developer

Click OK to The RDBMS user/schema can

Oracle SQL Developer

Grant connect privileges to the newly created

Oracle SQL Developer

Expand the Other Users node to verify that

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 2

Oracle University and Egabi Solutions use only

Oracle University and Egabi Solutions use only

Create the ODI Master repository:

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 2

Start Oracle Data Integrator: Start >

Oracle Data Integrator

Open the New Gallery by choosing File >

Master Repository Creation Wizard

In the Master Repository Creation Wizard,

Master Repository Creation Wizard

In the Authentication window, enter the

In the Password Storage window, select

Verify that ODI Master Repository was

Practices for Lesson 2

Oracle University and Egabi Solutions use only

Oracle University and Egabi Solutions use only

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 2

Oracle University and Egabi Solutions use only

Copyright 2010, Oracle and/or its affiliates. All rights reserved.