P.10 PTS ODI11g Variables Functions Procedures Packages

8/10/2019 P.10 PTS ODI11g Variables Functions Procedures Packages

1/52

Copyright 2010, Oracle. All rights reserved.


2/52


3/52


Agenda

Variables User Functions Procedures Packages

Lab Overview Q&A


4/52


Variables


5/52


What Is a Variable?

Variable An ODI object whichstores a typedvalue, such as a number, string or date.Variables are used to customize transformationsas well as to implement control structures, suchas if-then statements and loops, into packages.


6/52


Variable Scope

Scope defines where the variable can be used. Global variables are accessible everywhere

(defined in the Others tab of the Designer tree). Project variables are accessible within the project

(and defined under the project in the Designer tree).

The scope is defined by the location of thevariable:

Global variables: in the Others view, under Globalvariables

Project variables: in the P rojects view, underVariables

To refer to a variable, prefix its name according toits scope:

Global variables: GLOBAL. Project variables: .


7/52


Variable Configuration: The Definition

Historize: keep all values taken by the Variable Last value: only keep the most recent value Not persistent: discard the value

Description ofvariable

Data type: Alphanumeric (250 chars)Date (Java format)

Numeric (10 digits).

Value given if no stored value


8/52


Variable Configuration: The Query

SQL Refreshinstruction

Logical Schema used forrefreshing

The result of a SQL query can be stored into a variable: The query must return a single value of the correct type. The query is executed by a Ref resh Var i ab l e package step. Can also refresh manually .


9/52


Using a Variable in The Mappings

When used, a variable is prefixed according to its scope: Global variable : GLOBAL. Project variable : .

Tip: Use the Expression Editor to avoid mistakes in variables

names.


10/52


11/52


User Functions


12/52


What Is a User Function?

User Function Across-technology macro

defined in a lightweight syntax used to create analias for a recurrent piece of code orencapsulate a customized transformation.


13/52


Simple Example

A simple formula:I f is nul l then else end if

Can be implemented differently in differenttechnologies: Oracle

nvl(, )

Other technologies:case when is nul l

then else end

And could be aliased to:NumberToTi t le (, )


14/52


15/52


Note Functions in Execution Log


16/52


How to Create a User Function

1. Select the Functions node in aproject, or in the Others view2. Right-click > Inew User Function3. Fill in the:

Name

Syntax Description

4. Select the Group , or type in thename of a new group.


17/52


Defining the Implementations

1. Select theImplementations tab

2. Click the Add button.3. Enter the code for the

implementation4. Select the applicable

technologies.


18/52


Syntax of the Implementations

The function's syntax and implementation arguments arespecified in one of the following formats :

$( ) $( )

If is supplied it must be s (string), n (numeric) or d (date). For example: $( t i t le )s

Argument names in the syntax and implementation should matchexactly. Examples:

Syntax:NullValue( $(myvar iable) , $(mydefaul t ) )

Implementation:case when $(myvar iable) i s nul l

then $(mydefaul t )e lse $(myvar iable)

end


19/52


Using User Functions

At design-time, you can refer to user functions like anyregular database function

You can use them in mappings, joins, filters, procedures, etc. They are available in the expression editor.

When the code is generated: Project functions are identified first, then global functions. If a function is recognized, it is turned into the implementation

corresponding to the technology of the generated code. If the function is not recognized, the generated code remains

unchanged.


20/52


Procedures


21/52


What is a procedure?

Procedure A sequence of commands executed by database engines, the operating

system, or using ODI Tools. A procedure canhave options that control its behavior.Procedures are reusable components that canbe inserted into packages.


22/52


Procedure Examples

Email Administrator procedure:1. Uses the OdiSendMail ODI tool to send an administrative

email to a user. The email address is an option.

Clean Environment procedure:1. Deletes the contents of the /temp directory using the

OdiFileDelete tool 2. Runs DELETE statements on these tables in order:

CUSTOMER, CITY , REGION , and COUNTRY

Create and populate RDBMS table:1. Run SQL statement to create an RDBMS table.2. Run SQL statements to populate table with records.


23/52


Procedure Examples (cont.)

Initialize Drive procedure:1. Connect to a network drive using either a UNIX or Windows command (depending on an

option).2. Create a /work directory on this drive.

Email Changes procedure:1. Wait for 10 rows to be inserted into the INCOMING table.2. Transfer all data from the INCOMING table to the OUTGOING table.3. Dump the contents of the OUTGOING table to a text file.4. Email this text file to a user.


24/52


How to Create a New Procedure

1. Right-click the Procedures node under aproject and select New Procedure.

2. Enter:- The name- The description

3. Optionally, define the default:

- Source technology- Target technology


25/52


26/52


27/52


Which Parameters Should Be Set?

The following parameters should be set in the command: Technology: Overrides the default technology for the procedure Logical Schema: For DBMS technologies (Jython, OS, and ODI

tools do not require a schema) Context: If you want to ignore the execution context Ignore Errors: If the command must not stop the procedure. A

warning is issued only if the command fails.


28/52


Valid Types of Commands

Some examples of the types of commands that can be used in ODIprocedures:

SQL statement

OS commands

ODI Tools

Jython programs

Executed on any DBMS technologyDELETE, INSERT, SELECT, statements.

Executed on theOperating System technologyIn OS-specific syntax using shell commands or binary programs

Executed on theODI API technology Any ODI tool command call.

Executed on theJython technology.Jython code interpreted by the agent (Extensibility Framework).


29/52


More Elements

In addition, we have access to the following ODI-specific elements that canbe used within the commands:

Variables

Sequences

User Functions

They may be specified either in substitution mode #, or in bind mode:

They may be specified either in substitution mode #, or in bind mode:

Used like DBMS functions. They are replaced at code generation time by theirimplementation.


30/52


Types of Options

Options are typed procedure parameters- Checkbox , value or text

Options are used to control procedures:- Commands may or may not be executed depending on the

values of checkbox options.- Value or text options can be used within the command toparameterize the code.

Options have a default value . The value can also bespecified when the procedure is used.


31/52


How to Create a New Option

1. Right-click the nameof the procedure.

2. Select New Option.3. Enter:

- The name- The description- The help text

4. Select:

- A type- A default value- A position to

display in


32/52


How to Make a Command Optional

1. Open a command andclick the Options tab

2. Select the option box if itshould trigger thecommand execution

3. If the command shouldrun, independently of anyoptions, select the AlwaysExecute check box


33/52


34/52


Packages


35/52


What Is a Package?

Package : An organized sequence ofsteps thatmakes up a workflow.

Each step performs a small task, and they arecombined together to make the package.


36/52


How to Create a Package

1. Create and name a blank package.2. Create the steps that make up the package:

Drag interfaces from the Projects view onto theDiagram tab.

Insert ODI tools from the toolbox.3. Arrange the steps in order:

Define the first step. Define the success path. Set up error handling.


37/52


Package Diagram

Diagram

Oracle DataIntegratortool step

Interface step(selected)

Interface step(selected)

ToolboxToolbar

Procedurestep


38/52


Package Diagram Toolbar

Execute package Execute selected step

Edit selected stepHide/showsuccess links

Hide/showfailure links

Select

Next step onsuccess

Next stepon failure

Duplicateselection

Delete selection

Rearrangeselection

Print package

Page setup

Shows errorsin the diagram


39/52


Steps

The two most common package steps are:- Interface steps- ODI tool steps

Steps are created and sequenced in the package diagram.


40/52


41/52


42/52


Note Interfaces Are Reusable


43/52


44/52


How to Create an ODI Tool Step

1. In Toolbox, expand thegroup containing the toolthat you want to add.

2. Click the tool.

3. Click the diagram.- A step named afterthe tool appears.

4. Change the step namein the Properties panel.

5. Set the tools properties.


45/52


Note Tool Steps Are Not Reusable

A Si l P k


46/52


A Simple Package

This package executes two interfaces, and then archives somefiles.

If one of the three steps fails, an email is sent to theadministrator.

Step onfailure

First step

Step on success


47/52


How to Sequence Package Steps

1. Define the first step.- Right-click and select First Step.

2. Define the success path.a. Select the Next step on success tool. b. Click the first step, the second step, and so on for the entire

success path.3. Set up error handling.

a. Select the Next step on failure tool. b. Click one step, then click the next step.c. Repeat to define the failure path wherever needed.

4. To delete links or steps:a. Use the Select tool to select a link or step.b. Click the Delete selection button (or press the Delete key on

the keyboard).


48/52


Executing a Package

1. Click the Executebutton.

2. Open Operator Navigator.- The package is

executed as a session.

- Each package step isa step in OperatorNavigator.- Tool steps appear

with a single task.

- Interface steps showeach command

as a separate task.


49/52


Lab Overview


50/52


Lab Objectives

In this lab, you will learn how to:

Create a user function Create a variable

Create a package Create a procedure


51/52



52/52

Date post:	02-Jun-2018
Category:	Documents
Upload:	nareshreddyguntaka
View:	225 times
Download:	0 times

P.10 PTS ODI11g Variables Functions Procedures Packages

Documents