PC95 L1D 201311 SG CD

Unauthorized reproduction or distribution prohibited. Copyright 2012, Informatica and/or its affiliates.
Informatica PowerCenter 9.x

Level One Developer
Student Guide
Version: PC95_L1D_201311
Informatica PowerCenter 9x Level One Developer

Version: PC95_L1D_201311
November 2013
Copyright (c) 19982013 Informatica Corporation. All rights reserved.
This educational service, materials, documentation and related software contain proprietary
information of Informatica Corporation and are provided under a license agreement containing
restrictions on use and disclosure and are also protected by copyright law. Reverse engineering
of the software is prohibited. No part of the materials and documentation may be reproduced or
transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without
prior consent of Informatica Corporation. The related software is protected by U.S. and/or
international Patents and other Patents Pending.
Use, duplication, or disclosure of the related software by the U.S. Government is subject to the
restrictions set forth in the applicable software license agreement and as provided in DFARS
227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR
12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.
The information in this educational service, materials and documentation is subject to change
without notice. If you find any problems in this educational service, materials or documentation,
please report them to us in writing.
Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT,
PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata
Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data
Transformation, Informatica B2B Data Exchange Informatica On Demand, Informatica Identity
Resolution, Informatica Application Information Lifecycle Management, Informatica Complex
Event Processing, Ultra Messaging and Informatica Master Data Management are trademarks or
registered trademarks of Informatica Corporation in the United States and in jurisdictions
throughout the world. All other company and product names may be trade names or trademarks
of their respective owners.
Portions of this educational service, materials and/or documentation are subject to copyright held
by third parties, including without limitation: Copyright Adobe Systems Incorporated. All rights
reserved. Copyright Microsoft. All rights reserved. Copyright Oracle. All rights reserved.
Copyright @ the CentOS Project.
This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501;
6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775; 6,640,226;
6,820,077; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110,
7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422, 7,720,842; 7,721,270; and
international Patents and other Patents Pending.
6,029,178;
6,789,096;
7,254,590;
7,774,791,
DISCLAIMER: Informatica Corporation provides this educational services, materials and

documentation as is without warranty of any kind, either express or implied, including, but not
limited to, the implied warranties of non-infringement, merchantability, or use for a particular
purpose. Informatica Corporation does not warrant that this educational service, materials,
documentation or related software is error free. The information provided in this educational
service, materials, documentation and related software may include technical inaccuracies or
typographical errors. The information in this educational service, materials, documentation and
related software is subject to change at any time without notice.
Unauthorized reproduction or distribution prohibited. Copyright 2012, Informatica and/or its iiaffiliates.
Preface
Welcome to the PowerCenter 9x Level One Developer course.
This four-day, instructor led course introduces students to Informatica PowerCenter 9.x
through lecture and hands-on exercises. The course is designed for Database Developers
who are new to Informatica PowerCenter.
Informatica PowerCenter is a collection of thick client workbench tools that Developers
can use to create, execute, monitor and schedule ETL processes.
The course will introduce attendees to working with the PowerCenter Designer,
Workflow Manager, and Workflow Monitor tools, performing tasks such as creating
transformations, mappings, reusable objects, sessions and workflows to extract, transform
and load data. They will develop cleansing, formatting, sorting and aggregating
procedures. They can learn how to use routers, update strategies, parameters /variables
and overrides. This course will cover many different types of lookups, such as cached,
persistent, dynamic and multiple row returns. Workflow tasks will be created to define a
set of instructions for executing the ETL.
Prerequisites:
Prerequisites include basic familiarity with Windows GUI and at least two years work
experience and some knowledge of SQL.
Course Objectives:
After successfully completing this course, students should be able to:
Use Informatica Support to resolve questions and problems with PC9.x.
Use PowerCenter 9.x Designer to build mappings that extract data from a source
to a target, transforming it as necessary.
Use PowerCenter transformations to cleanse, format, join, aggregate and route
data to the appropriate targets
Perform error handling/trapping using PowerCenter mappings
Use PowerCenter 9.x Workflow Manager to build and run a workflow which
executes a sessions associated with a mapping
Design and build simple mappings and workflows based on essential business
needs.
Perform basic troubleshooting using PowerCenter logs and debugger
Audience:
This course is designed for database developers with little or no experience of
PowerCenter.
.
Unauthorized reproduction or distribution prohibited. Copyright 2012, Informatica and/or itsiiiaffiliates.
Document Conventions
This guide uses the following formatting conventions:
If you see
It means
Example
>
Indicates a submenu to navigate

to.
boldfaced text
Indicates text you need to type or

enter.
Click Repository > Connect.

In this example, you should click the
Repository menu or button and choose
Connect.
Click the Rename button and name the new
source definition S_EMPLOYEE.
UPPERCASE
Database tables and column

names are shown in all
UPPERCASE.
Indicates a variable you must
replace with specific information.
Connect to the Repository using the assigned

login_id.
Note:
The following paragraph provides

additional facts.
Note: You can select multiple objects to

import by using the Ctrl key.
Tip:
The following paragraph provides

suggested uses or a Velocity best
practice.
Tip: The m_ prefix for a mapping name is
italicized text
T_ITEM_SUMMARY
Unauthorized reproduction or distribution prohibited. Copyright 2012, Informatica and/or itsivaffiliates.
Other Informatica Resources

In addition to the student and lab guides, Informatica provides these other resources:
Informatica Documentation
Informatica Customer Portal
Informatica web site
Informatica Developer Network
Informatica Knowledge Base
Informatica Multimedia Knowledge Base
Informatica How-to Library
Informatica Professional Certification
Informatica Technical Support
Obtaining Informatica Documentation

The Informatica Documentation team takes every effort to create accurate, usable documentation. If
you have questions, comments, or ideas about this documentation, contact the Informatica
Documentation team through email at infa_documentation@informatica.com. We will use your
feedback to improve our documentation. Let us know if we can contact you regarding your
comments. The Documentation team updates documentation as needed. To get the latest
documentation for your product, navigate to Product Documentation from
http://mysupport.informatica.com.
Visiting the Informatica Customer Portal

http://mysupport.informatica.com
As an Informatica customer, you can access the Informatica Customer Portal site. The site contains
product information, user group information, newsletters, access to the Informatica customer support
case management system (ATLAS), the Informatica How-To Library, the Informatica Knowledge
Base, the Informatica Multimedia Knowledge Base, Informatica Product Documentation, and access
to the Informatica user community.
Visiting the Informatica Web Site

You can access Informaticas corporate web site at:
http://www.informatica.com
The site contains information about Informatica, its background, upcoming events, and locating
your closest sales office. You will also find product information, as well as literature and partner
information. The services area of the site includes important information on technical support,
training and education, and implementation services.
Visiting the Informatica Technology Network

The Informatica Developer Network is a web-based forum growing online community and
interactive forum for data integration and data quality professionals around the globe. You can
access the Informatica Developer Network at the following URL:
http://community.informatica.com/
The site contains information on how to create, market, and support customer-oriented add-on
solutions based on interoperability interfaces for Informatica products.
Unauthorized reproduction or distribution prohibited. Copyright 2012, Informatica and/or its vaffiliates.
Visiting the Informatica Knowledge Base

As an Informatica customer, you can access the Informatica Knowledge Base at
http://mysupport.informatica.com. Use the Knowledge Base to search for documented solutions
to known technical issues about Informatica products. You can also find answers to frequently
asked questions, technical white papers, and technical tips. If you have questions, comments, or
ideas about the Knowledge Base, contact the Informatica Knowledge Base team through email at
KB_Feedback@informatica.com.
Visiting the Informatica Multimedia Knowledge Base

As an Informatica customer, you can access the Informatica Knowledge Base at
http://mysupport.informatica.com. Use the Knowledge Base to search for documented solutions
to known technical issues about Informatica products. You can also find answers to frequently
asked questions, technical white papers, and technical tips. If you have questions, comments, or
ideas about the Knowledge Base, contact the Informatica Knowledge Base team through email at
KB_Feedback@informatica.com.
Visiting the Informatica How-To Library

As an Informatica customer, you can access the Informatica How-To Library at
http://mysupport.informatica.com. The How-To Library is a collection of resources to help you
learn more about Informatica products and features. It includes articles and interactive
demonstrations that provide solutions to common problems, compare features and behaviors, and
guide you through performing specific real-world tasks.
Obtaining Informatica Professional Certification

You can take, and pass, exams provided by Informatica to obtain Informatica Professional
Certification. For more information, go to:
http://www.informatica.com/products_services/education_services/certification/Pages/index.aspx
Providing Feedback
Email any comments on this guide to education@informatica.com.
Obtaining Technical Support

There are many ways to access Informatica Technical Support. You can call or email your nearest
Technical Support Center listed in the following table, or you can use our WebSupport Service.
Use the following email addresses to contact Informatica Technical Support:
support@informatica.com for technical inquiries

support_admin@informatica.com for general customer service requests
WebSupport requires a user name and password. You can request a user name and password at:
Unauthorized reproduction or distribution prohibited. Copyright 2012, Informatica and/or itsviaffiliates.
Informatica Global Customer Support

You can contact a Customer Support Center by telephone or through the Online Support. Online
Support requires a user name and password. You can request a user name and password at
Use the following telephone numbers to contact Informatica Global Customer Support:
North America / South
America
Informatica Corporation
Headquarters
100 Cardinal Way
Redwood City, California
94063
United States
Europe / Middle East / Africa
Asia / Australia
Informatica Software Ltd.

6 Waltham Park
Waltham Road, White Waltham
Maidenhead, Berkshire
SL6 3TN
United Kingdom
Informatica Business
Solutions Pvt. Ltd.
301 & 302 Prestige Poseidon
139 Residency Road
Bangalore 560 025
India
Toll Free
877 463 2435
Toll Free
00 800 4632 4357
Standard Rate
United States: 650 385 5800
Standard Rate
Belgium: +32 15 281 702
France: +33 1 41 38 92 26
Germany: +49 1805 702 702
Netherlands: +31 306 022 797
United Kingdom: +44 1628 511 445
Toll Free
Australia: 00 11 800 4632
4357
Singapore: 001 800 4632 4357
Standard Rate
India: +91 80 5112 5738
Unauthorized reproduction or distribution prohibited. Copyright 2012, Informatica and/or itsviiaffiliates.
Unauthorized reproduction or distribution prohibited. Copyright 2012, Informatica and/or its

viiiaffiliates.
Unauthorized reproduction or distribution prohibited. Copyright 2012, Informatica and/or its affiliates.0.1
Module 0: Student Resources
Student note text here
PowerCenter 9.x Level 1 Developer
Copyright 2013 Informatica Corp
Specialist
PK
Expert
PK
BPK
PE
Master
PK
ProductTraining
ProductTraining
ProductTraining
ProductCoreExam
ProductCore
Exam
ProductCore
Exam
FieldExperience
BPK PE
FieldExperience
VelocityBest
Practice Training
VelocityBest
Practice Training
VelocityExam
VelocityExam
MultipleProduct
Experience
Handson Exam
PK-Product knowledge, BPK-Best practices knowledge, PE-Project Experience

M-Mandatory, R-Recommended
Module 1: PowerCenter Overview
1.10
1.11
1.12
1.13
1.14
1.15
1.16
1.17
1.18
1.19
1.20
Sources and Targets
Can be relational tables or heterogeneous files (such as flat files, VSAM

files, or XML)
Integration Service
The engine which performs all the ETL logic
Repository Service
Manages connectivity to metadata repositories that contain mapping and

workflow definitions
Repository Service
Process
Multithreaded process that retrieves, inserts, and updates repository

metadata
Repository
Contains all the metadata needed to run the ETL process
Client Tools
Desktop tools used to populate the repository with metadata, execute

workflows on the Integration Service, monitor the workflows, and manage
the repository
1.21
Sources and Targets

files, or XML)
Integration Service
Repository Service

Repository Service
Process

metadata
Repository
Client Tools

the repository
1.22
Sources and Targets

files, or XML)
Integration Service
Repository Service

Repository Service
Process

metadata
Repository
Client Tools

the repository
1.23
Sources and Targets

files, or XML)
Integration Service
Repository Service

Repository Service
Process

metadata
Repository
Client Tools

the repository
1.24
Sources and Targets

files, or XML)
Integration Service
Repository Service

Repository Service
Process

metadata
Repository
Client Tools

the repository
1.25
Note
Designer and Repository Manager access the repository through the Repository
Service.
Workflow Manager and Workflow Monitor connect to the Integration Service.
Each client has its own user interface. The UIs typically have toolbars, a navigation
window to the left, a workspace to the right, and an output window at the bottom.
1.26
Module 2: ETL Fundamentals
Repository Management
Repositories are not created and managed in the Designer application.

They are created in the Informatica Administrator tool, and managed in
the Repository Manager application.
Folder Management
Folders are created and managed in the Repository Manager

application.
Shortcut Folders
Do not confuse repository folders with the directories visible in

Windows Explorer. The folders are PowerCenter repository objects
and are not related to Windows directories.
Technically, all folders are shared with all users who have the
appropriate folder permissions, regardless of the blue arm icon. The
blue arm icon indicates that the folder permits shortcuts, dynamic
links to the objects contained in that folder used by mappings in other
folders.
Note
Two sources from different systems may use the same name. Placing each
source in a folder based on its connection type avoids confusion when this is
the case.
2.10
2.11
2.12
2.13
2.14
Note
The transformation is considered passive regardless of what

transformations take place within a row, provided only that the rows going
out are a one-for-one match with the rows going in.
Examples
Examples of passive transformations include Expression and Lookup

transformations.
2.15
Examples
Examples of active transformations include Filter, Router, and Sorter

transformations.
2.16
Type
Active
Description
Mandatory for all flat file and relational sources in a mapping. Selects
records from flat file and relational table sources. For relational tables,
creates a SQL SELECT statement. Converts native source datatypes to
PowerCenter transformation datatypes.
Ports
Represent table columns or file fields. All ports are input/output.
2.17
Note
The integration datatype standardizes transformations, and is easily

translated from and to the native datatypes of application databases
Note
Integration datatypes are sometimes referred to as ASCII Neutral
2.18
Datatype Conversion
Datatypes can be converted by:

Passing data between ports with different datatypes
Passing data from an expression to a port
Using transformation functions
Using arithmetic operators
The following type conversions are supported:
Numeric datatypes other numeric datatypes
Numeric datatypes string
Date/Time date or string
For further information, in the PowerCenter client, consult Help
Content Index port-to-port data conversion
2.19
2.20
2.21
2.22
2.23
2.24
A workflow is a set of ordered tasks that describe runtime ETL processes. Tasks can be
sequenced serially, in parallel and conditionally. Each linked icon represents a task.
2.25
2.26
2.27
2.28
A task is an executable set of actions, functions, or commands.
2.29
2.30
2.31
2.32
2.33
2.34
2.35
2.36
2.37
Velocity Phases
Velocity covers the entire data integration project lifecycle:

Phase 1: Manage
Phase 2: Architect
Phase 3: Design
Phase 4: Build
Phase 5: Deploy
Phase 6: Operate
For more information, access MySupport at www.informatica.com
Note
We do not use the Velocity templates in this course
Note
In Velocity, the standard is to begin the names of all Source Qualifier

objects with SQ_, followed by the name of the source. The Mapping
Designer automatically names the Source Qualifier this way when you
drag a Source object onto the Mapping canvas.
2.38
2.39
Note
In the labs for this course, we are simulating part of the creation of a
(very simple) Dimensional Data Warehouse. In these labs, you will begin
with data in OLTP tables and flat files, bring data to Staging, and from
Staging (STG) to the Operational Data Store (ODS).
Because creation of Staging tables is fairly trivial, you will do more work
on moving data from STG to ODS. This will provide more realistic uses
of the capabilities of PowerCenter.
2.40
2.41
2.42
Module 3: Troubleshooting
3.10
3.11
3.12
3.13
Records rejected by the source or target go into the .bad file(s).

Records that have a transformation error go into the session log.
Therefore if a row of data is both rejected and causes a transformation error, it may end up in both
locations.
When the Integration Service reads non-numeric data in a numeric column from a flat file, it drops
the row and writes a message in the session log. Also, when the Integration Service reads nondatetime data in a datetime column from a flat file, it drops the row and writes a message in the
session log.
Such a target and/or source reject would put the record in the .bad file as well.
3.14
3.15
Module 4: Transformations, Tasks and Reusability
Type
Passive
Description
Modifies individual ports (columns) within a single row. Can add and suppress
ports. Cannot perform aggregation across multiple rows.
Business
Purpose
Use the logical and arithmetic operators and built-in functions for:
Character manipulation (concatenate, truncate, etc.)
Datatype conversion (to char, to date, etc.)
Data cleansing (check nulls, replace strings, etc.)
Data manipulation (round, truncate, etc.)
Numerical calculations
Scientific calculations
Special functions (lookup, decode, etc.)
Testing (for spaces, number, etc.)
Comments
Comments can be added to expressions by prefacing them with //. This

allows later developers to understand the logic behind an expression.
Tip
Highlighting a function and pressing F1 will launch the online help at the selected
function section.
Note
All expressions resolve to a single value of a specific datatype. For example, the
expression LENGTH (HELLO WORLD) / 2 returns the numerical value 5.5.
Note
Variable ports cannot be output directly. To output the contents of a variable

port, create an output port whose value is the variable.
Creating
A transformation variable is created by creating a port and selecting the V check

box. When V is checked, the I and O checkboxes are unavailable (grayed out),
indicating that a variable port can not be used for input or output.
Note
When a record is processed, the expression is evaluated and the result is assigned
to the variable port. The result must be compatible with the ports datatype.
The variable persists across the set of records, and may be used or modified
anywhere in the set of records.
4.10
4.11
4.12
4.13
Type
Active
Description
Rows which meet the filter condition are passed through to the next
transformation. Rows which do not meet the filter condition are skipped.
Business Purpose
A business may choose not to process records which do not meet a data
quality criterion.
4.14
4.15
4.16
Warning
Instance of reusable transformations inherit any changes to the reusable

transformation. As a result, changing a reusable transformation may
invalidate the mappings containing instances of the transformation.
Note
To make a non-reusable copy of a reusable transformation, hold the Ctrl

key while dragging and dropping.
4.17
4.18
4.19
4.20
4.21
Module 5: Features and Techniques
Module 6: Joins and Link Conditions
Example:
A business sells a high volume of products and updates the Product Dimension table on a regular
basis. To update the dimension table, a join of the PRODUCT and PRODUCT_COST table is
required. Since the source tables are form the same database and have a key relationship only a
single Source Qualifier transformation is needed.
Pipelines
There are two pipelines; one from the master source, one from the detail.
The master pipeline ends at the Joiner transformation, while the detail
pipeline continues to the target.
Type
Active
Description
Combines fields from two data sources into a single combined data
source, based on one or more common fields called the join condition
Business Purpose
Enables data from different systems to be combined to achieve desired

structure and results
6.10
6.11
6.12
6.13
6.14
6.15
6.16
6.17
6.18
6.19
6.20
Module 7: Using the Debugger
Module 8: Sequence Generators, Lookups and Additional Workflow Tasks
Type
Active or Passive
Description
Allows the inclusion of additional information in the transformation process from

an external database or flat file source. In SQL terms, may be thought of as a
subquery. May be connected, unconnected, or dynamic.
Business Purpose Allows data from external sources such as product codes, dates, names, etc., to
be brought into the row being processed.
Report Error. The Integration Service reports an error and does not return a row. If you do not
enable the Output Old Value On Update option, the Lookup Policy On Multiple Match option is
set to Report Error for dynamic lookups.
Use First Value. Returns the first row that matches the lookup condition.
Use Last Value. Return the last row that matches the lookup condition.
Use All Values. Return all matching rows
Use Any Value. The Integration Service returns the first value that matches the lookup
condition. It creates an index based on the key ports instead of all Lookup transformation
ports.
8.10
8.11
8.12
8.13
8.14
When you do not configure $Source Connection Value:
And you have one source in your mapping, the database connection you specify for the
source will be used as the value for $Source.
If a Joiner transformation is in the mapping before a Lookup or Stored Procedure

transformation, the database connection used will be from the detail source of the Joiner.
If a Lookup or Stored Procedure transformation comes before a Joiner transformation in the

mapping, the database connection for the source connected to the lookup or SP
transformation will be used as the value of $Source.
If an unassigned variable is used for an Unconnected Lookup or Stored Procedure

transformation, the session will fail. Therefore, you would always need to define the variable
on the session.
When you do not configure $Target Connection Value:
And you have only one target in the mapping, the database connection you specify for the
target will be used for the lookup or SP.
If you have Multiple relational targets in the mapping and the $Target connection value is not
configured, the session fails.
If your mapping contains an Unconnected Lookup or Stored Procedure and the $Target
connection value is not configured, the session fails.
8.15
Description
Event Wait tasks wait for either the presence of a named flat file (a predefined event) or some other user-defined event to occur in the workflow
processing. Note that the Workflow must be running in order to
recognize a pre-defined event.
Business Purpose
An Event Wait task watching for a flat file by name is placed in a

workflow because some subsequent processing is dependent on the
presence of the file.
An Event Wait task waiting for the occurrence of a user-defined event
will be strategically placed so that the workflow should not proceed
further until some other set of tasks and conditions has occurred. It
always works in concert with an Event Raise task.
8.16
8.17
8.18
8.19
Description
Email tasks enable PowerCenter to send email messages at various

points in a workflow. Users can define email addresses, a subject line,
and the email message text. When called from within a Session task, the
message text can contain variable Session-related metadata for
example, one message for Session success and another for failure.
Business Purpose
Various business and operational staff may need to be notified of the

progress of a workflow, the status of tasks (or combinations of tasks)
within it, or various metadata results of a session
Performance
Considerations
The PowerCenter domain must be configured to use a running,

configured email server. However, the impact of the Integration Service
sending the emails is minimal
8.20
8.21
Note
The Control task can fail, stop, or abort either the parent Workflow or the top-level
Workflow. However, stopping or aborting the parent Workflow means that no further
progress takes place along that branch in the top-level Workflow. This can cause
the top-level Workflow to stop if there is no other branch.
8.22
Description
Command tasks are inserted in workflows and worklets to enable the

Integration Service to run one or more OS commands of any nature. All
commands or batch files referenced must be executable by the OS login
that owns the Integration Service process.
Business Purpose
OS commands can be used for any operational or business unit related

procedure, and can be run at any point in a workflow. Command tasks
can be set to run one or more OS commands or scripts/batch files,
before proceeding to the next task in the workflow. If more than one
command is coded into a Command Task, the entire task can be set to
fail if any one of the individual commands fails. Additionally and
optionally, each individual command can be set not to run if a preceding
command fails.
8.23
Examples of Command
Tasks
A Session task that produces an output file can be followed by a

Command task that copies the file to another directory, or FTPs the file
to another box location. The command syntax is the same as that which
would accomplish this at the OS command prompt on the Integration
Service machine.
A Session task that relies on a flat file as source data can be preceded
by a Command task that verifies the presence of the file, opens it and
verifies control totals or record counts with some external source of
information.
A series of multiple concurrent or sequential Sessions can be followed

by a single Command task coded to copy or move all session logs
created by the workflow to a special daily backup directory.
8.24
Description
Decision tasks enable workflow designers to set criteria by which the workflow
will or will not proceed to the next set of tasks, depending on whether the set
criteria is true or false
Business Purpose
Commonly, workflows have multiple paths. Some are simply concurrent tasks.
Others are pipelines of tasks that should only run if the previous tasks are
successful. Still others should be run only if those tasks are not successful.
What determines the success or failure of a task or group of tasks is userdefined, depending on the business-defined rules and operational rules of
processing.
The criteria are set as the decision condition in a Decision task, and
subsequently tested for a True or False condition
8.25
8.26
8.27
8.28
8.29
8.30
8.31
8.32
Note
Caching for lookup tables is an option. When the lookup references a flat file,
caching is always performed.
8.33
8.34
8.35
8.36
8.37
8.38
8.39
8.40
Module 9: Update Strategies, Routers and Overrides
Type
Active
Description
Tags a row with the appropriate DML (Data Manipulation Language) for
PowerCenters writer to apply to the relational target. Each row can be
tagged with one of the tags shown on the following slide.
Business Purpose
A target table may require historical information dealing with existing

entries. Rows written to a target table, based on one or more criteria,
may need to be inserted, updated, or deleted. The Update Strategy
transformation meets this requirement.
Note
For the row tags DD_DELETE and DD_UPDATE, the table definition in the
mapping must have a key identified. Otherwise, the session created from the
mapping will fail.
If the Forward Rejected Rows attribute is checked (default), then rows tagged
with DD_REJECT will be passed on to the next transformation or the Target, and
subsequently placed in the appropriate bad file. If the attribute is unchecked,
then the reject rows will be skipped.
Performance
Considerations
Update Strategy performance can vary depending on the number of

updates and inserts. In some cases there may be a performance benefit
to splitting a mapping with updates and inserts into two mappings and
sessions, one performing the inserts and one the updates.
Records rejected by the source or target go into the .bad file(s).

Records that have a transformation error go into the session log.
Therefore if a row of data is both rejected and causes a transformation error, it may end up in both
locations.
When the Integration Service reads non-numeric data in a numeric column from a flat file, it drops
the row and writes a message in the session log. Also, when the Integration Service reads nondatetime data in a datetime column from a flat file, it drops the row and writes a message in the
session log.
Such a target and/or source reject would put the record in the .bad file as well.
Type
Active
Description
Passes row data to different groups based on filter-like conditions. A

Router transformation has one input group, and one or more output
groups, each of which has its own filter condition.
Business Purpose
Allows you to write records from a single source into multiple targets
based on user-defined criteria.
Performance
Considerations
A Router transformation is functionally equivalent to several Filter

transformations in parallel. However, performance can be substantially
better, because a row is read once into the input group but evaluated
multiple times, once for each condition.
Note
In the diagram above, the record for a salesperson hired less than 90 days ago
will be routed to both STG_EMPLOYEES_NEW and
STG_EMPLOYEES_SALES.
If you wish to prevent single records from being routed to multiple Targets, you
must ensure that their filter conditions are mutually exclusive.
In the example above, you would prefix the conditions for the position-based
tables with DATE HIRED >= 90 DAYS AGO AND.
Note that multiple target objects can be instances of the same target table. If this
is the case, only one INSERT statement will be generated per record.
9.10
9.11
9.12
9.13
9.14
9.15
9.16
Module 10: Sorting and Aggregating Data Using PowerCenter
10.1
10
10.2
10.3
Type
Active
Description
Sorts incoming data based on one or more key values. Sort order may
be ascending, descending, or mixed.
Business Purpose
Use before an Aggregator transformation to improve overall

performance. The Sorter transformation is often more efficient than
adding an ORDER BY clause to the Source Qualifier.
10
10.4
Property
Description
Case Sensitive
Determines whether the Sorter differentiates between upper and lower

case characters.
Work Directory
A directory where the Integration Service will create temporary files

when sorting data.
Distinct
Treats output rows as distinct. If this is selected, all ports are considered
as part of the sort key.
Null Treated Low
If selected, treat nulls as lower values than any other.
Transformation Scope
Transaction: Applies transformation logic to all rows in a transaction.

All Input: Applies the transformation logic on all incoming data,
regardless of incoming transaction boundaries.
Other Properties
Deal with caching - see next slide
10.5
10
10.6
Type
Active
Description
Calculates aggregates such as sums, averages, minimums and

maximums, across multiple groups of rows.
Business Purpose
Enables calculation of gross profits or margins, summaries by period,

average values, etc.
10.7
Attribute
Description
Cache Directory
Local directory for the index and data cache file
Tracing Level
Amount of detail displayed in the session log for this transformation
Sorted Input
Indicates input data is presorted by group. Use only if the mapping

passes sorted data to the Aggregator.
Aggregator Data Cache

Size
Data cache size for the transformation. Default size is set to Auto.
Aggregator Index Cache

Size
Index cache size for the transformation. Default cache size is set to Auto.
Transformation Scope
Transaction: applies transformation logic to all rows in a transaction.

All input: applies the transformation logic on all incoming data.
10
10.8
Key Points
If there is not enough memory specified in the index and data cache
properties, overflow is written to disk
No rows are returned until all rows are aggregated
Checking the sorted input attribute bypasses caching and aggregate
calculations are performed as the Integration Service reads rows for
each group.
10.9
10
10.10
10.11
Type
Passive
Description
Unconnected Lookups allow the inclusion of additional information in the

transformation process from an external source when they are referenced
within any transformation that supports expressions.
Business Purpose
A source table may have a small percentage of records with incomplete data.
These holes in the data can be filled by performing a lookup to another table
or tables, on an as-needed basis.
10
10.12
10.13
10
10.14
Key Points
Use the Lookup function (:lkp.lookupname) within a conditional

expression
The condition is evaluated for each row but the Lookup function is only
called when the record requires it
Data from several input ports may be passed to the Lookup
transformation, but only one port may be returned, as designated by
the R(eturn) property in the Lookup transformation
If no port is set as R the mapping will not be invalid, the lookup will
return all nulls.
10.15
The port to be returned is designated by the Lookup transformations R (return) port.

If a port is not selected as the R port, the mapping will not be invalidated but the lookup will return
nulls.
10
10.16
10.17
10
10.18
10.19
Description
System variables hold information derived from the system. The user
cannot control the content of the variable but can reference the
information contained within the variable.
Business Purpose
System variables provide consistency to program execution.
10
10.20
Description
System variables hold information derived from the system. The user
cannot control the content of the variable but can reference the
information contained within the variable.
Business Purpose
System variables provide consistency to program execution.
10.21
10
10.22
Description
A Mapping can utilize parameters and variables to store information

during execution. Each parameter and variable is defined with a specific
datatype. Parameters are different from variables in that parameters are
fixed for the run of the Mapping, while variables can change (vary). Both
can be accessed from anywhere in the Mapping.
Business Purpose
Mapping variables and parameters are used:

To simplify Mappings by carrying information within or between
transformations
To improve maintainability by allowing quick changes to values in a
Mapping
10.23
Scope
Parameters and variables can be used only inside the object in which
they are created. A Mapping variable created for Mapping_1 is available
only within that Mapping and cannot be used by another Mapping or
Mapplet in the same workflow. A parameter or variables scope is the
object in which it was created.
Aggregation Type
The PC Integration Service uses the aggregation type of a mapping

variable to determine the final current value of the mapping variable. In a
session with multiple partitions, the Int Service combines the variable
value from each partition and saves the final value into the repository.
Aggregation types include Count (for integer datatype), Max, and Min.
IsExpVar
IsExpVar determines how the Integration Service expands the parameter

in an expression string. If true,
the Integration Service expands the parameter before parsing the
expression. If false, the Integration Service expands the parameter after
parsing the expression. Default is false.
10
10.24
10.25
Variable Persistence
At the end of a successful session, the values of variables are

saved to the repository. The SetVariable function writes the final
value of a variable to the repository based on the Aggregation Type
selected when the variable was defined.
The final value written to the repository for a variable that has an
Aggregate type of MAX will be whichever is greater, the current
value or the initial value. Similarly, the final value for a variable with
an Aggregate type of MIN will be whichever is smaller, the current
value or the initial value.
Naming Convention
User-defined variable and parameter names always begin with $$

(i.e., $$ParamName or $$VariableName).
10
10.26
Parameter File
A file that holds information about definitions of variables and parameters
Repository Saved
Value
Values for variables that were saved in the Repository after successful
completion of a Session
Declared Initial
Value
The initial value, as set by the user when creating the variable or parameter
Default Value
Set by the system
10.27
10
10.28
10.29
10
10.30
10.31
Service variables. Define general properties for the Integration Service such as email addresses,
log file counts, and error thresholds.
Service process variables. Define the directories for Integration Service files for each Integration
Service process. $PMRootDir, PMSessionLogDir, and $PMBadFileDir are examples of service
process variables.
10
10.32
10.33
10
10.34
From WhatIs.com
In data warehousing and business intelligence, a star schema is the simplest form of a dimensional
model, in which data is organized into facts and dimensions.
A fact is an event that is counted or measured, such as a sale or login.
A dimension contains reference information about the fact, such as date, product, or customer.
A star schema is diagramed by surrounding each fact with its associated dimensions. The resulting
diagram resembles a star.
10.35
10
10.36
Type
Passive or Active
Description
Mapplets combine multiple mapping objects for reusability; they can also
simplify complex mapping maintenance. A Mapplet receives input data from
either an internal Source or the Mapping pipeline that calls the Mapping. A
Mapplet must pass data out to the Mapping via a Mapplet Output
transformation.
Note
Mapplets are reusable by nature a Mapping uses an instance of a Mapplet.

These instances inherit all changes to the parent Mapplet, which may affect
the behavior of the Mappings that use the instances.
10.37
Example
A business, as part of its daily sales, needs to apply discounts, performing a

number of lookups and aggregating the sales values.
This functionality is used in several types of feeds, so the Mapplet shown
here was created to provide this functionality, identically, in many Mappings.
10
10.38
Type
Passive
Description
Acts as an input to a Mapplet
10.39
10
10.40
Type
Passive
Description
Acts as an output from a Mapplet
10.41
10
10.42
10.43
Warning
When the Mapplet is expanded at runtime, an unconnected output group could

result in a transformation having no output connections. If that is not permitted,
then the mapping will be invalid.
For example:
If the Mapplet outputs are fed by an Expression transformation, the
mapping is invalid because an Expression requires a connected output.
But if the Mapplet outputs are fed by a Router, the mapping is valid
because a Router can have unconnected output groups.
10
10.44
Note
Mapplets cannot be nested that is, you cannot use a Mapplet inside
another Mapplet.
10.45
10
10.46
10.47
10
10.48
Module 11: Mapping Workshop
11.1
11
11.2
11.3
11
11.4
In this lab, we will build a fact table that tracks promotions by day for each dealership for each
product being sold.
11.5
11
Module 12: Workflow Workshop
12.1
12
12.2
12.3
12
12.4

PC95 L1D 201311 SG CD

Загружено:

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

Оригинальное название

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

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

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

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

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

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

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

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

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

PC95 L1D 201311 SG CD

Загружено:

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

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

Unauthorized reproduction or distribution prohibited. Copyright 2012, Informatica and/or its affiliates.

Informatica PowerCenter 9.x

Informatica PowerCenter 9x Level One Developer

DISCLAIMER: Informatica Corporation provides this educational services, materials and

Indicates a submenu to navigate

Indicates text you need to type or

Click Repository > Connect.

Database tables and column

Connect to the Repository using the assigned

The following paragraph provides

Note: You can select multiple objects to

The following paragraph provides

Tip: The m_ prefix for a mapping name is

Unauthorized reproduction or distribution prohibited. Copyright 2012, Informatica and/or itsivaffiliates.

Other Informatica Resources

Obtaining Informatica Documentation

Visiting the Informatica Customer Portal

Visiting the Informatica Web Site

Visiting the Informatica Technology Network

Visiting the Informatica Knowledge Base

Visiting the Informatica Multimedia Knowledge Base

Visiting the Informatica How-To Library

Obtaining Informatica Professional Certification

Obtaining Technical Support

support@informatica.com for technical inquiries

Unauthorized reproduction or distribution prohibited. Copyright 2012, Informatica and/or itsviaffiliates.

Informatica Global Customer Support

Europe / Middle East / Africa

Informatica Software Ltd.

Unauthorized reproduction or distribution prohibited. Copyright 2012, Informatica and/or itsviiaffiliates.

Unauthorized reproduction or distribution prohibited. Copyright 2012, Informatica and/or its

Module 0: Student Resources

Student note text here

PowerCenter 9.x Level 1 Developer

Copyright 2013 Informatica Corp

Module 0: Student Resources

Student note text here

PowerCenter 9.x Level 1 Developer

Copyright 2013 Informatica Corp

Module 0: Student Resources

Student note text here

PowerCenter 9.x Level 1 Developer

Copyright 2013 Informatica Corp

Module 0: Student Resources

PK-Product knowledge, BPK-Best practices knowledge, PE-Project Experience

Copyright 2013 Informatica Corp

Module 1: PowerCenter Overview

Student note text here

PowerCenter 9.x Level 1 Developer

Copyright 2013 Informatica Corp

Module 1: PowerCenter Overview

Student note text here

PowerCenter 9.x Level 1 Developer

Copyright 2013 Informatica Corp

Module 1: PowerCenter Overview

Student note text here

PowerCenter 9.x Level 1 Developer

Copyright 2013 Informatica Corp

Module 1: PowerCenter Overview

Student note text here

PowerCenter 9.x Level 1 Developer

Copyright 2013 Informatica Corp

Module 1: PowerCenter Overview