Informatica

PowerMart /
PowerCenter 7 Basics
PC6B-20030512

Education Services

 Informatica Corporation, 2003. All rights reserved.

 Course Objectives
At the end of this course you will:
 Understand how to use all major PowerCenter 7
components
 Be able to perform basic Repository administration tasks
 Be able to build basic ETL Mappings and Mapplets
 Be able to create, run and monitor Workflows
 Understand available options for loading target data
 Be able to troubleshoot most problems

2
 Extract, Transform, and
Operational Systems Load Decision Support
Data
RDBMS Mainframe Other Warehouse

• Transaction level data Aggregate Data

Cleanse Data • Aggregated data
• Optimized for Transaction Consolidate Data • Historical
Response Time Apply Business Rules
• Current De-normalize
• Normalized or De-
Normalized data
Transform

ETL Load
Extract

3
PowerCenter Architecture

4
 PowerCenter 7
Architecture native
native
Server

Sources Targets

TCP/IP
Repository
Heterogeneous Server Heterogeneous
Targets Targets

TCP/IP Repository
Agent

native
Repository Designer Workflow Workflow Rep Server Repository
Manager Manager Monitor Administrative

Console
Not Shown: Client ODBC Connections for Source and Target metadata
5
 PowerCenter 7
Components
• PowerCenter Repository
• PowerCenter Repository Server
• PowerCenter Client
• Designer
• Repository Manager
• Repository Server Administration Console
• Workflow Manager
• Workflow Monitor
• PowerCenter Server
• External Components
• Sources
• Targets 6
 Repository Topics
By the end of this section you will be familiar with:
 The purpose of the Repository Server and Agent
 The Repository Server Administration Console GUI
interface
 The Repository Manager GUI interface
 Repository maintenance operations
 Security and privileges
 Object sharing, searching and locking
 Metadata Extensions
7
 Repository Server
 Each Repository has an independent
architecture for the management of the
physical Repository tables
 Components:
Server
one Repository Server, and
a Repository Agent for each Repository
Repository
Server

Repository
Agent

Repository Repository Server

Administration Console
Manager Repository
Client overhead for Repository management is greatly
reduced by the Repository Server
8
 Repository Server
Features
 Manages connections to the Repository
from client applications
 Can manage multiple Repositories on
different machines on a network
 Uses one Repository Agent process to
insert, update and fetch objects from
the Repository database tables, for
each Repository it manages
 Maintains object consistency by
The Repository Server runs on the same system running the Repository Agent
controlling object locking 9
 Repository Server
Administration Console
Use Repository Administration console to Administer Repository
Servers and
Repositories through Repository Server. Following tasks can be
performed:

• Add, Edit and Remove Repository Configurations

• Export and Import Repository Configurations
• Create a Repository
• *Promote a local Repository to a Global Repository
• Copy a Repository
• Delete a Repository from the Database
• Backup and Restore a Repository
• Start, Stop, enable and Disable a Repositories
• View Repository connections and locks
• Close Repository connections.
• Upgrade a Repository

10
 Repository Server
Administration Console

Information HTML View

Nodes

Console Tree
Hypertext Links to
Repository
Maintenance Tasks

11
 Repository Management
• Perform all Repository
maintenance tasks
through Repository
Server from the
Repository Server
Administration Console
• Create the Repository
Configuration
• Select Repository
Configuration
• Create and
• Notify Users
perform
• Delete maintenance
• Propagate
tasks:
• Backup • Register
• Copy from • Restore
• Disable • Un-Register
• Export Connection • Upgrade
• Make Global
12
 Repository Manager
Use Repository manager to navigate
through multiple folders and repositories.
Perform following tasks:

 Manage the Repository

• Launch Repository Server Administration
Console for this purpose
• Implement Repository Security
• Managing Users and Users Groups
• Perform folder functions
• Create, Edit, Copy and Delete folders
• View Metadata 13
 Repository Manager
Interface
Navigator
Window

Main Window

Dependency Window

Output Window

14
 Users, Groups and
Repository Privileges
Steps:

 Create groups
 Create users
 Assign users to
groups
 Assign privileges to
groups
 Assign additional
privileges to users
(optional)

15
 Managing Privileges
Check box assignment of privileges

16

Folder Permissions
Assign one user as the
folder owner for first tier
permissions

 Select one of the owner’s

groups for second tier
permissions

 All users and groups in

the Repository will be
assigned the third tier
permissions
17
 Object Locking
 Object Locks preserve Repository integrity
 Use the Edit menu for Viewing Locks and Unlocking
Objects

18
 Object Searching
(Menu- Analyze – Search)
 Keyword search
• Limited to keywords
previously defined in
the Repository
(via Warehouse
Designer)

 Search all
• Filter and search
objects

19
 Object Sharing
 Reuse existing objects
 Enforces consistency
 Decreases development time
 Share objects by using copies and shortcuts

COPY SHORTCUT
Copy object to another Link to an object in another
folder folder
Changes to original object Dynamically reflects
not captured changes to original object
Duplicates space Preserves space
Required security settings for sharing objects:
Copy from shared or
• Repository Created from a shared
Privilege: Use Designer
unshared folder folder
• Originating Folder Permission: Read
• Destination Folder Permissions: Read/Write
20
 Adding Metadata
Extensions
 Allows developers and partners to
extend the metadata stored in the
Repository
 Accommodates the following metadata
types:
• Vendor-defined - Third-party application
vendor-created metadata lists
• For example, Applications such as Ariba or
PowerConnect for Siebel can add information
such as contacts, version, etc.
• User-defined - PowerCenter/PowerMart 21
 Sample Metadata
Extensions

Sample User Defined

Metadata, e.g. - contact
information, business user

Reusable Metadata Extensions can also be created in the Repository Manager

22
 Design Process
1. Create Source definition(s)
2. Create Target definition(s)
3. Create a Mapping
4. Create a Session Task
5. Create a Workflow from Task components
6. Run the Workflow
7. Monitor the Workflow and verify the results

23
 Source Object
Definitions
By the end of this section you will:
 Be familiar with the Designer GUI
interface
 Be familiar with Source Types
 Be able to create Source Definitions
 Understand Source Definition
properties
 Be able to use the Data Preview
option
24
 Source Analyzer
Designer Tools

Analyzer Window

Navigation
Window

25
 Methods of Analyzing
Sources
Repository
 Import from Database
 Import from File
 Import from Cobol File
 Import from XML file
 Create manually Source
Analyzer

Relational XML file Flat file COBOL file

26
 Analyzing Relational Sources
Source Analyzer
Relational Source
ODBC Table
View
Synonym
DEF

Repository
Server

TCP/IP
Repository
Agent
native

Repository
DEF
27
 Analyzing Relational
Editing Source Sources
Definition Properties

28
Analyzing Flat File Sources
Source Analyzer
Mapped Drive Flat File
NFS Mount
Local Directory DEF
Fixed Width or
Delimited

Repository
Server

TCP/IP
Repository
Agent
native

Repository
DEF
29
 Flat File Wizard
 Three-step
wizard
 Columns can
be renamed
within wizard
 Text, Numeric
and Datetime
datatypes are
supported
 Wizard
‘guesses’
datatype
30
 XML Source
Source Analyzer Analysis
Mapped Drive
.DTD File
NFS Mounting
Local Directory DEF

DATA
Repository
Server

TCP/IP
Repository
Agent In addition to the DTD file, an
XML Schema or XML file
native can be used as a Source
Definition
Repository
DEF
31
Analyzing VSAM Sources
Source Analyzer .CBL File
Mapped Drive
NFS Mounting
DEF
Local Directory

Repository DATA
Server

TCP/IP
Repository
Agent Supported Numeric Storage Options:
COMP, COMP-3, COMP-6
native

Repository
DEF
32
VSAM Source Properties

33
 Target Object
Definitions
By the end of this section you will:
 Be familiar with Target Definition
types
 Know the supported methods of
creating Target Definitions
 Understand individual Target
Definition properties

34
 Creating Target
Definitions
Methods of creating Target
Definitions
 Import from Database
 Import from an XML file
 Manual Creation
 Automatic Creation

35
 Automatic Target
Creation
Drag-and-
drop a
Source
Definition
into
the
Warehouse
Designer
Workspace

36
 Import Definition
from Database
Can “Reverse engineer” existing
object definitions from a database
system catalog or data dictionary
Warehouse
Designer
Database
ODBC

Table
Repository View
Server DEF Synonym

TCP/IP Repository
Agent

native
Repository DEF
37
 Manual Target
Creation 2. Add desired columns
1. Create empty definition

3. Finished target definition

ALT-F can also be used to create a new column

38
Target Definition
Properties

39
Target Definition Properties

40
 Creating Physical
Tables
DEF

DEF

DEF Execute SQL

via
Designer

LOGICAL PHYSICAL
Repository target table Target database
definitions tables

41
Creating Physical Tables

Create tables that do not already exist in

target database
 Connect - connect to the target database
 Generate SQL file - create DDL in a script
file
 Edit SQL file - modify DDL script as needed
 Execute SQL file - create physical tables in
target database

Use Preview Data to verify

the results (right mouse
click on object)
42
 Transformation
Concepts
By the end of this section you will be
familiar with:
 Transformation types and views
 Transformation calculation error
treatment
 Null data treatment
 Informatica data types
 Expression transformation
 Expression Editor
 Informatica Functions
 Expression validation 43
 Transformation
Informatica Types
PowerCenter 7 provides
23 objects for data transformation
• Aggregator: performs aggregate calculations
• Application Source Qualifier: reads Application
object sources as ERP
• Custom: Calls a procedure in shared library or DLL
 Expression: performs row-level calculations
 External Procedure (TX): calls compiled code for
each row
 Filter: drops rows conditionally
 Joiner: joins heterogeneous sources
 Lookup: looks up values and passes them to other
objects
 Normalizer: reorganizes records from VSAM, 44
Relational and Flat File
 Transformation Types
 Router: splits rows conditionally
 Sequence Generator: generates unique
ID values
 Sorter: sorts data
 Source Qualifier: reads data from Flat
File and Relational Sources
 Stored Procedure: calls a database
stored procedure
 Transaction Control: Defines Commit and
Rollback transactions
 Union: Merges data from different
databases 45
 Transformation Views
A transformation has
three views:
 Iconized - shows the
transformation in
relation to the rest of
the mapping
 Normal - shows the
flow of data through
the transformation
 Edit - shows
transformation ports
and properties; allows
editing
46
 Edit Mode
Allows users with folder “write” permissions to change
or create transformation ports and properties
Define transformation
Define port level handling
level properties

Enter comments
Make reusable

Switch
between
transformations

47
 Expression
Transformation
Perform calculations using non-aggregate functions
(row level)

Passive Transformation
Connected

Ports
• Mixed
• Variables allowed
Click here to invoke the
Expression Editor
Create expression in an
output or variable port

Usage
• Perform majority of
data manipulation
48
 Expression Editor
 An expression formula is a calculation or conditional statement
 Used in Expression, Aggregator, Rank, Filter, Router, Update Strategy
 Performs calculation based on ports, functions, operators, variables,
literals, constants and return values from other transformations

49
 Informatica Functions
- Samples
ASCII
CHR
CHRCODE
Character Functions
CONCAT
INITCAP
 Used to manipulate
INSTR
LENGTH
character data
LOWER
LPAD
 CHRCODE returns the
LTRIM numeric value (ASCII or
RPAD
RTRIM Unicode) of the first
character of the string
SUBSTR For backwards compatibility only - use || instead
UPPER
REPLACESTR
REPLACECHR passed to this function
50
 Informatica Functions
Conversion Functions
TO_CHAR (numeric)
TO_DATE
TO_DECIMAL  Used to convert
TO_FLOAT
TO_INTEGER
datatypes
TO_NUMBER

ADD_TO_DATE
DATE_COMPARE
DATE_DIFF Date Functions
GET_DATE_PART
LAST_DAY  Used to round, truncate,
ROUND (date) or compare dates;
SET_DATE_PART
TO_CHAR (date) extract one part of a
TRUNC (date) date; or perform
arithmetic on a date 51

 Informatica
ABS
Functions
Numerical Functions
CEIL
CUME
 Used to perform
EXP
FLOOR
mathematical
LN operations
Scientific Functions on numeric
COS
LOG COSH
MOD data
 Used to calculate SIN
MOVINGAVG SINH
geometric values
MOVINGSUM TAN
POWER of numeric data TANH
ROUND
SIGN
SQRT
TRUNC

52
ERROR
Informatica Functions
Special Functions
ABORT Used to handle specific conditions within a session;
DECODE search for certain values; test conditional
statements
IIF
IIF(Condition,True,False)

ISNULL Test Functions

IS_DATE
IS_NUMBER
IS_SPACES  Used to test if a lookup result is
null
• Used to validate data
SOUNDEX

METAPHONE Encoding Functions

 Used to encode string values 53

 Expression Validation
The Validate or ‘OK’ button in the
Expression Editor will:
 Parse the current expression
• Remote port searching (resolves references
to ports in other transformations)
 Parse transformation attributes
• e.g. - filter condition, lookup condition,
SQL Query
 Parse default values
 Check spelling, correct number of 54
• Use Variable Portsexpressions
to simplify complex
• e.g. - create and store a depreciation
formula to be
referenced more than once
• Use in another variable port or an
output port expression
• Local to the transformation (a variable
port cannot also be an input or output
port)
• Available in the Expression, Aggregator
and Rank transformations

55
 Informatica Data
NATIVE Types
DATATYPES TRANSFORMATION
Specific to the source and
target database types
Native Transformation
Display in source and target
tables within Mapping
Designer
DATATYPES
PowerMart / PowerCenter
internal datatypes based on
ANSI SQL-92
Native
Display in transformations
within Mapping Designer

 Transformation datatypes allow mix and match of source and target

database types
 When connecting ports, native and transformation datatypes must be
compatible (or must be explicitly converted)
56
 Datatype Conversions
Intege Decim Double Char Date Raw
r al
Intege X X X X
r
Decima X X X X
l
Double X X X X
 All numeric data can be converted to all other numeric datatypes,
Char X double,
e.g. - integer, X and decimal
X X X
 Date X
All numeric data can be converted to string, andXvice versa
 Raw X
Date can be converted only to date and string, and vice versa
 Raw (binary) can only be linked to raw
 Other conversions not listed above are not supported
 These conversions are implicit; no function is necessary
57
 Mappings
By the end of this section you will be
familiar with:
 Mapping components
 Source Qualifier transformation
 Mapping validation
 Data flow rules
 System Variables
 Mapping Parameters and Variables
58
Mapping Designer
Transformation Toolbar

Mapping List

Iconized Mapping

59
 Pre-SQL and Post-SQL
Rules
• Can use any command that is valid for
the database type; no nested comments
• Can use Mapping Parameters and
Variables in SQL executed against the
source
• Use a semi-colon (;) to separate
multiple statements
• Informatica Server ignores semi-colons
within single quotes, double quotes or
within /* ...*/ 60
 Data Flow Rules
 Each Source Qualifier starts a single data stream
(a dataflow)
 Transformations can send rows to more than one
transformation (split one data flow into multiple pipelines)
 Two or more data flows can meet together -- if (and only if)
they originate from a common active transformation
 Cannot add an active transformation into the mix

ALLOWED DISALLOWED

Passive Active

T T T T

Example holds true with Normalizer in lieu of Source Qualifier. Exceptions are:
Mapplet Input and Joiner transformations
61
 Connection Validation
Examples of invalid connections in a
Mapping:
 Connecting ports with incompatible
datatypes
 Connecting output ports to a Source
 Connecting a Source to anything but
a Source Qualifier or Normalizer
transformation
 Connecting an output port to an
output port or an input port to
another input port
 Connecting more than one active 62
 Mapping Validation
 Mappings must:
• Be valid for a Session to run
• Be end-to-end complete and contain valid expressions
• Pass all data flow rules
 Mappings are always validated when saved; can be validated
without being saved
 Output Window will always display reason for invalidity

63
 Workflows
By the end of this section, you will be familiar with:
 The Workflow Manager GUI interface
 Workflow Schedules
 Setting up Server Connections
 Relational, FTP and External Loader

 Creating and configuring Workflows

 Workflow properties
 Workflow components
 Workflow Tasks
64
 Workflow Manager
Interface
Task
Tool Bar

Workflow
Designer
Tools

Workspace
Navigator
Window

Output Window

Status Bar
65
Workflow Manager Tools
• Workflow Designer
• Maps the execution order and dependencies
of Sessions, Tasks and Worklets, for the
Informatica Server

• Task Developer
• Create Session, Shell Command and Email
tasks
• Tasks created in the Task Developer are
reusable

66
 Workflow
• A Workflow is setStructure
of instructions for
the Informatica Server to perform
data transformation and load
• Combines the logic of Session Tasks,
other types of Tasks and Worklets
• The simplest Workflow
Link is composed of
a Start Task, a Link and one other Task

Start Session
Task Task

67
 Workflow Scheduler
Objects
• Setup reusable
schedules to
associate with
multiple Workflows
– Used in Workflows
and Session Tasks

68
•
Server Connections
Configure Server data access connections
– Used in Session Tasks
Configure:
2. Relational
3. MQ Series
4. FTP
5. Custom
6. External Loader

69
 Relational Connections
• (Native
Create a relational )
(database) connection
– Instructions to the Server to locate
relational tables
– Used in Session Tasks

70
 Relational Connection
 Define nativeProperties
relational (database)
connection

User Name/Password

Database connectivity
information

Rollback Segment
assignment (optional)

Optional Environment SQL

(executed with each use of
database connection)

71
 FTP Connection
 Create an FTP connection
− Instructions to the Server to ftp flat files
− Used in Session Tasks

72
 External Loader
−
Connection
 Create an External Loader connection
Instructions to the Server to invoke database bulk loaders
− Used in Session Tasks

73
•
Task Developer
Create basic Reusable “building blocks” – to
use in any Workflow
• Reusable Tasks
• Session Set of instructions to
execute Mapping logic
• Command Specify OS shell /Command
Session
script
command(s) to run Email

during the Workflow

• Email Send email at any point in the
Workflow
74
 Session Task
 Server instructions to runs the logic of ONE specific Mapping
• e.g. - source and target data location specifications,
memory allocation, optional Mapping overrides,
scheduling, processing and load instructions

 Becomes a
component of a
Workflow (or
Worklet)
 If configured in
the Task
Developer,
the Session Task
is reusable
(optional)

75
• SpecifyCommand
one (or more)Task
Unix shell or DOS
(NT, Win2000) commands to run at a
specific point in the Workflow
• Becomes a component of a Workflow (or
Worklet)
• If configured in the Task Developer, the
Command Task is reusable (optional)

Commands can also be referenced in a Session through the Session

“Components” tab as Pre- or Post-Session commands
76
Command Task

77
 Additional Workflow
Components
• Two additional components are Worklets
and Links
• Worklets are objects that contain a
series of Tasks

• Links are required to connect objects in a

Workflow

78
 Developing Workflows
Create a new Workflow in the Workflow
Designer
Customize
Workflow name

Select a
Server

79
 Workflow Properties
Customize Workflow
Properties

Workflow log displays

Select a Workflow
Schedule (optional)

May be reusable or
non-reusable

80