P. 1
PC8x90L1D_StudentGuide_20081124GV9 (1)

PC8x90L1D_StudentGuide_20081124GV9 (1)

3.0

|Views: 2,260|Likes:
Published by Ummed Mahala

More info:

Published by: Ummed Mahala on Feb 04, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

08/19/2013

pdf

text

original

PowerCenter 8.x/9.

0 Level I Developer Student Guide
Version – L1D_20081124GV9

1

PowerCenter 8.x Level I Developer Student Guide Version 04 April2008 Copyright (c) 2008 Informatica Corporation. All rights reserved. Printed in the USA. This software and documentation 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 this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. Use, duplication, or disclosure of the 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 document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Informatica Corporation does not warrant that this documentation is error free. Informatica, PowerMart, PowerCenter, PowerChannel, PowerCenter Connect, MX, and SuperGlue 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 software are copyrighted by DataDirect Technologies, 1999-2002. Informatica PowerCenter products contain ACE (TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University and University of California, Irvine, Copyright (c) 1993-2002, all rights reserved. Portions of this software contain copyrighted material from The JBoss Group, LLC. Your right to use such materials is set forth in the GNU Lesser General Public License Agreement, which may be found at http://www.opensource.org/licenses/lgpl-license.php. The JBoss materials are provided free of charge by Informatica, “as-is”, without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Portions of this software contain copyrighted material from Meta Integration Technology, Inc. Meta Integration® is a registered trademark of Meta Integration Technology, Inc. This product includes software developed by the Apache Software Foundation (http://www.apache.org/). The Apache Software is Copyright (c) 1999-2005 The Apache Software Foundation. All rights reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit and redistribution of this software is subject to terms available at http://www.openssl.org. Copyright 1998-2003 The OpenSSL Project. All Rights Reserved. The zlib library included with this software is Copyright (c) 1995-2003 Jean-loup Gailly and Mark Adler. The Curl license provided with this Software is Copyright 1996-2007, Daniel Stenberg, <Daniel@haxx.se>. All Rights Reserved. The PCRE library included with this software is Copyright (c) 1997-2001 University of Cambridge Regular expression support is provided by the PCRE library package, which is open source software, written by Philip Hazel. The source for this library may be found at ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre. InstallAnywhere is Copyright 2005 Zero G Software, Inc. All Rights Reserved. Portions of the Software are Copyright (c) 1998-2005 The OpenLDAP Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted only as authorized by the OpenLDAP Public License, available at http://www.openldap.org/software/release/license.html. This Software is protected by U.S. Patent Numbers 6,208,990; 6,044,374; 6,014,670; 6,032,158; 5,794,246; 6,339,775 and other U.S. Patents Pending. DISCLAIMER: Informatica Corporation provides this 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. The information provided in this documentation may include technical inaccuracies or typographical errors. Informatica could make improvements and/or changes in the products described in this documentation at any time without notice.

Preface

Welcome to the PowerCenter 8 Level I Developer course. Data integration is a large undertaking with many potential areas of concern. The PowerCenter infrastructure will greatly assist you in your data integration efforts and alleviate much of your risk. This course will prepare you for that challenge by teaching you the most commonly used components of the product. You will build a small operational data store (ODS) using PowerCenter to extract from Source tables and files, transform the data, load it into a staging area, and finally into the operational data store. The Instructor will teach you about Mappings, transformations, Sources, Targets, Workflows, Sessions, Workflow tasks, Connections, and the Velocity methodology.

iii

About This Guide
Course Objectives
After completing this course, you should be able to:

• • • • •

Use PowerCenter 8 Designer to build mappings that move data from sources to targets Use PowerCenter 8 Workflow Manager to build and run a workflow that runs a session based on a mapping Design mappings and workflows based on business needs Perform basic troubleshooting of PowerCenter mappings and transformaitons Use Informatica Support options to resolve questions and problems about Informatica PowerCenter 8

Audience
This course is designed for data integration and data warehousing implementers. You should be familiar with data integration and data warehousing terminology, and in using Microsoft Windows software.

Document Conventions
This guide uses the following formatting conventions:
If you see… Æ It means… Indicates a submenu to navigate to. Example

Click Repository Æ Connect.
In this example, you should click the Repository menu or button and choose Connect.

boldfaced text
UPPERCASE

Indicates text you need to type or enter.

Click the Rename button and name the new source definition S_EMPLOYEE. T_ITEM_SUMMARY Connect to the Repository using the assigned login_id. Note: You can select multiple objects to import by using the Ctrl key. Tip: The m_ prefix for a mapping name is…

Database tables and column names are shown in all UPPERCASE. Indicates a variable you must replace with specific information. The following paragraph provides additional facts. The following paragraph provides suggested uses or a Velocity best practice.

italicized text
Note: Tip:

Other Informatica Resources
In addition to the student guides, Informatica provides these other resources:

x x x x x x x

Informatica Documentation Informatica Customer Portal Informatica web site Informatica Developer Network Informatica Knowledge Base Informatica Professional Certification Informatica Technical Support

Obtaining Informatica Documentation
You can access Informatica documentation from the product CD or online help.

Visiting Informatica Customer Portal
As an Informatica customer, you can access the Informatica Customer Portal site at http://my.informatica.com. The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica Knowledge Base, and access to the Informatica user community.

Visiting the Informatica Web Site
You can access Informatica’s 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 Developer Network
The Informatica Developer Network is a web-based forum for third-party software developers. You can access the Informatica Developer Network at the following URL:
http://devnet.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.

Visiting the Informatica Knowledge Base
As an Informatica customer, you can access the Informatica Knowledge Base at http://my.informatica.com. The Knowledge Base lets you search for documented solutions to known technical issues about Informatica products. It also includes frequently asked questions, technical white papers, and technical tips.

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/services/education_services/certification/default.htm

v

North America / South America Informatica Corporation Headquarters 100 Cardinal Way Redwood City. California 94063 United States Toll Free 877 463 2435 Standard Rate United States: 650 385 5800 Europe / Middle East / Africa Informatica Software Ltd.com for general customer service requests WebSupport requires a user name and password. or you can use our WebSupport Service. White Waltham Maidenhead.com. Ltd. You can request a user name and password at http://my.informatica. Berkshire SL6 3TN United Kingdom Toll Free 00 800 4632 4357 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 Asia / Australia Informatica Business Solutions Pvt.Providing Feedback Email any comments on this guide to education@informatica.com for technical inquiries support_admin@informatica. 301 & 302 Prestige Poseidon 139 Residency Road Bangalore 560 025 India Toll Free Australia: 00 11 800 4632 4357 Singapore: 001 800 4632 4357 Standard Rate India: +91 80 5112 5738 . You can call or email your nearest Technical Support Center listed in the following table. Obtaining Technical Support There are many ways to access Informatica Technical Support.com. Use the following email addresses to contact Informatica Technical Support: x x support@informatica. 6 Waltham Park Waltham Road.

Using the Debugger 9. Mapping Fundamentals 3. Lookup Transformations 7. Mapping Design Workshop 14. PowerCenter 9.0 New Features Page 0-1 1-1 2-1 3-1 4-1 5-1 6-1 7-1 8-1 9-1 10-1 11-1 12-1 13-1 14-1 15-1 vii . Expression and Filter Transformations 5. Controlling Workflows 13. PowerCenter Overview 2. Joining and Merging Data 6. Course Introduction 1. Workflow Basics 4. Updating Target Tables 10. Mapping Techniques 11. Mapplets and Worklets 12. Workflow Design Workshop 15. Sorter and Aggregator Transformations 8.Table of Contents Module 0.

.

x/9.0 Level 1 Developer L1D_20081124GV9 PowerCenter 8.1 0 PowerCenter 8.Course Introduction 0.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .

0 Level I Developer Copyright © 2010 Informatica Corp .x/9.Course Introduction 0.2 Module 0: Course Introduction PowerCenter 8.

3 Introductions • Logistics/Site Information • Introductions • About you • How do you expect to benefit from this course? 0 Module 0: Course Introduction 3 of 22 PowerCenter 8.Course Introduction 0.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.

Course Introduction 0.x Level I Developer is designed for Developers and Consultants • This course enables participants to use the principal features of Informatica PowerCenter 8 for integrating data between disparate applications • This material assumes familiarity with database concepts and technology Module 0: Course Introduction 4 of 22 PowerCenter 8.4 Course Audience • PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.

x/9.0 Level I Developer Copyright © 2010 Informatica Corp .Course Introduction 0.5 Course Objectives • When you have completed this course. you should be able to: • Use PowerCenter 8 Designer to build mappings that move data from sources to targets • Use PowerCenter 8 Workflow Manager to build and run a workflow that runs a session based on a mapping • Design simple mappings and workflows based on business needs • Perform basic troubleshooting of PowerCenter mappings and transformations • Use Informatica Support options to resolve questions and problems about Informatica PowerCenter 8 0 Module 0: Course Introduction 5 of 22 PowerCenter 8.

0 Level I Developer Copyright © 2010 Informatica Corp . Workflow Basics 4. Sorter and Aggregator Transformations Module 0: Course Introduction 6 of 22 PowerCenter 8. Joining and Merging Data 6. Mapping Fundamentals 3.x/9.Course Introduction 0.6 Course Agenda 1. PowerCenter Overview 2. Expression and Filter Transformations 5. Lookup Transformations 7.

Workflow Design Workshop 0 Module 0: Course Introduction 7 of 22 PowerCenter 8.x/9. Updating Target Tables 10. Using the Debugger 9.0 Level I Developer Copyright © 2010 Informatica Corp .7 Course Agenda Continued 8. Controlling Workflows 13. Mapping Design Workshop 14. Mapping Techniques 11.Course Introduction 0. Mapplets and Worklets 12.

x/9. Informatica provides these other resources: • Corporate Website • Global Education Services • Customer Portal • Product Documentation • Knowledge Base • Technical Support • Informatica Product Certification Module 0: Course Introduction 8 of 22 PowerCenter 8.Course Introduction 0.8 Other Informatica Resources • In addition to the student guides.0 Level I Developer Copyright © 2010 Informatica Corp .

x/9. training.9 Informatica Corporate Website • Can be accessed at www.Course Introduction 0. education and implementation services Module 0: Course Introduction 0 9 of 22 PowerCenter 8.informatica.0 Level I Developer Copyright © 2010 Informatica Corp .com • Website provides: • Corporate information and background • Upcoming events and access to Informatica Communities. Blogs and Tech Net • Nearest sales office location • Product information. literature and partner information • Information on technical support.

com/products_services/education_services • Discover new training offerings • New courses added regularly • Learn about Informatica Certification Module 0: Course Introduction 10 of 22 PowerCenter 8.Course Introduction 0.10 Informatica Education Services • Products + Services Æ Education Services • www.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .informatica.

11 Informatica Customer Portal • • Available to Informatica customers and partners at http://my.0 Level I Developer Copyright © 2010 Informatica Corp .informatica.x/9.com 0 Website provides: • • • • • • • Product Access to ATLAS system Knowledge Base Access to the User Community User Group info Newsletters Debugging Tools Velocity Module 0: Course Introduction documentation Support Informatica / 11 of 22 PowerCenter 8.Course Introduction 0.

Course Introduction 0.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.12 Accessing the Customer Portal • Use your company email id to register • Provides default access to: • Most recent documentation • Knowledge base • Default does not provide online support access • Request using Project ID • Once approved you can create Service Requests • Available for 11 countries Module 0: Course Introduction 12 of 22 PowerCenter 8.

0 Level I Developer Copyright © 2010 Informatica Corp .x/9.Course Introduction 0.13 Informatica Documentation • Can be accessed via: • Product CD or Download link • Online help • Documentation Center 0 Module 0: Course Introduction 13 of 22 PowerCenter 8.

14 Informatica Knowledge Base • Can be accessed via the Customer Portal http://my.x/9.com • Contains • Documented solutions to known technical issues • Answers to frequentlyasked questions (FAQs) • White papers • Technical tips • Perform generic.0 Level I Developer Copyright © 2010 Informatica Corp .or specific-searches Module 0: Course Introduction 14 of 22 PowerCenter 8.informatica.Course Introduction 0.

Course Introduction 0.x/9.com username and password 0 • Alternative Support access via: • • Call / email your nearest Technical Support Center • See Student Note Email Technical Support directly (may be delay in response): • support@informatica.0 Level I Developer Copyright © 2010 Informatica Corp .com Module 0: Course Introduction 15 of 22 PowerCenter 8.informatica.com • support_admin@informatica.15 Informatica Technical Support • Preferred Support access via: • Online using the Web Support Service using http://my.

16 Creating a Service Request • Check the Knowledge Base to see if a solution exists • If a solution exists.0 Level I Developer Copyright © 2010 Informatica Corp . navigate to the Service Requests tab • Click the New button Module 0: Course Introduction 16 of 22 PowerCenter 8.x/9. a Service Request is not required • On the Online Support page.Course Introduction 0.

x/9. fill out all required fields • Provide as much relevant detail as possible so engineers can recreate the problem.17 Creating a Service Request Continued • On the service request form. if necessary 0 Module 0: Course Introduction 17 of 22 PowerCenter 8.Course Introduction 0.0 Level I Developer Copyright © 2010 Informatica Corp .

x Level I Developer PowerCenter 8 XML Support PowerCenter 8.x New Features v PowerCenter 8 Data Migration PowerCenter 8.x Upgrade PowerCenter 8.x Level II Developer PowerCenter 8 Team-Based Development PowerCenter 8 High Availability PowerCenter 8 Data Cleanse and Match B2B Data Transformation Additional Recommended Training Module 0: Course Introduction 18 of 22 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .x PowerCenter 8.5+ Administrator PowerCenter 8.18 PowerCenter Education and Certification Path PowerCenter 8 Quickstart PowerCenter 8.5 Unified Security PowerCenter 8.Course Introduction 0.x/9.

19 PowerExchange Education Path 0 Introduction to PowerExchange PowerCenter 8.x/9.5 Level I Administrator PowerCenter 8 High Availability PowerCenter 8 Team-Based Development PowerExchange Basics Additional Recommended Training Module 0: Course Introduction 19 of 22 PowerCenter 8.Course Introduction 0.0 Level I Developer Copyright © 2010 Informatica Corp .

6 Workbench Level I Informatica Data Explorer 8.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .6 New Features Additional Recommended Training Module 0: Course Introduction 20 of 22 PowerCenter 8.Course Introduction 0.20 Data Quality Education and Certification Path Informatica Data Quality 8.5 Cleansing Workshop Informatica Data Quality 8.6 Level I Data Quality Assessment Using IDE Data Quality Assessment Using IDQ Informatica Data Quality 8.5 Matching Workshop Data Quality Assessment Using IDQ Informatica Data Quality 8.

0 Level I Developer Copyright © 2010 Informatica Corp . »Advanced Administration »Advanced Mapping Design Informatica Certified Consultant » PowerCenter QuickStart (eLearning) » PowerCenter 8.21 Data Integration Certification Path Level Certification Title Recommended Training Required Exams 0 Informatica Certified Administrator » PowerCenter QuickStart (eLearning) » PowerCenter 8.5 New Features » PowerCenter 8.x/9.5+ Administrator (4 days) » PowerCenter Developer 8. »Advanced Administration »Advanced Mapping Design »Advanced Admistration »Enablement Technologies Additional Training: » PowerCenter 8.5+ Administrator (4 days) » PowerCenter Developer 8.Course Introduction 0.6 New Features » PowerCenter 8 Upgrade » PowerCenter 8 Team-Based Development » PowerCenter 8.x Level I (4 days) » PowerCenter Developer 8 Level II (4 days) »Architecture & Administration.5 Unified Security ` Module 0: Course Introduction 21 of 22 PowerCenter 8.5+ Administrator (4 days) »Architecture & Administration.x Level I (4 days) » PowerCenter Developer 8 Level II (4 days) » PowerCenter 8 Data Migration (4 days) » PowerCenter 8 High Availability (1 day) »Architecture & Administration. »Advanced Administration Informatica Certified Developer » PowerCenter QuickStart (eLearning) » PowerCenter 8.

6 Additional Training: » Data Quality Assessment Using Informatica Data Explorer » Data Quality Assessment Using Informatica Data Quality » Informatica Data Quality 8.6 Level I (4 days) » Informatica Data Explorer 8.6 Level I (2 days) »Data Quality 8.6 Level I (4 days) »Data Quality 8.6 New Features Module 0: Course Introduction 22 of 22 PowerCenter 8.22 Data Quality Certification Path Level Certification Title Recommended Training Required Exams Informatica Certified Specialist: Data Quality » Informatica Data Quality 8.6 Informatica Certified Professional » Informatica Data Quality 8.6 Level I (2 days) »Data Explorer 8.0 Level I Developer Copyright © 2010 Informatica Corp .6 Informatica Certified Specialist: Data Explorer » Informatica Data Explorer 8.x/9.5 Matching Workshop » Informatica Data Quality 8.Course Introduction 0.6 »Data Explorer 8.5 Cleansing Workshop » Informatica Data Quality 8.

0 Level I Developer Copyright © 2010 Informatica Corp .x/9.1 Module 1: PowerCenter Overview PowerCenter 8.PowerCenter Overview 1.

x/9.PowerCenter Overview 1.2 Module Objectives After completing this module you will be able to: • Explain the purposes of PowerCenter • Define terms used in PowerCenter • Name major PowerCenter components Module 1: PowerCenter Overview 2 of 32 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

and made to work as a seamless whole • But the different databases don’t talk to each other! Marketing (ORCL) Manufacturing (DB2) Accounting (SAP) Inventory (SQL Server) Sales (SalesForce) Resource Planning (PSFT) Billing (Sybase) Module 1: PowerCenter Overview 3 of 32 PowerCenter 8. compared.x/9.3 The Problem • Large organizations have a lot of data • The data can be stored in many formats.PowerCenter Overview 1. including databases and unstructured files • This data must be collated. combined.0 Level I Developer Copyright © 2010 Informatica Corp .

x/9. and it transports the data between the two applications.PowerCenter Overview 1.4 The Problem Continued • Many organizations have implemented connectors between these databases • Every pair of databases requires a unique connector Manufacturing (DB2) Marketing (ORCL) Sales (SalesForce) Accounting (SAP) Resource Planning (PSFT) Billing (Sybase) Inventory (SQL Server) Module 1: PowerCenter Overview 4 of 32 Connector A connector is a piece of custom software that performs two functions: it converts data from the format of one application to the format of another application. Technical Note To be precise. to connect n databases fully requires (1+2+…+(n-1)) connectors. PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

5 The Problem Continued • If you change one database.x/9. many connectors have to be upgraded Manufacturing (DB2) Marketing (ORCL) Sales (SalesForce) Accounting (upgraded) Resource Planning (PSFT) Billing (Sybase) Inventory (SQL Server) Module 1: PowerCenter Overview 5 of 32 PowerCenter 8.PowerCenter Overview 1.0 Level I Developer Copyright © 2010 Informatica Corp .

x/9.0 Level I Developer Copyright © 2010 Informatica Corp .PowerCenter Overview 1.6 The Solution: Data Integration • Data Integration technologies allow applications using different databases and formats to communicate with each other using one connection each Manufacturing (DB2) Marketing (ORCL) Data Integration! Accounting (SAP) Resource Planning (PSFT) 6 of 32 Billing (Sybase) Sales (SalesForce) Inventory (SQL Server) Module 1: PowerCenter Overview PowerCenter 8.

PowerCenter Overview 1.0 Level I Developer Copyright © 2010 Informatica Corp .7 Informatica PowerCenter • Informatica PowerCenter is the premium data integration solution available today • “Database neutral” – will communicate with any database • Powerful data transformations convert one application’s data to another’s format Manufacturing (DB2) Marketing (ORCL) Informatica PowerCenter Accounting (SAP) Inventory (SQL Server) Resource Planning (PSFT) 7 of 32 Billing (Sybase) Sales (SalesForce) Module 1: PowerCenter Overview PowerCenter 8.x/9.

PowerCenter Overview 1.0 Level I Developer Copyright © 2010 Informatica Corp . accounting.8 Example: Data Migration • A company purchases a new accounts payable application • PowerCenter can move the existing account data to the new application • Preserves data lineage for tax. and other legally mandated purposes Accounting (old) Informatica PowerCenter Accounting (new) Module 1: PowerCenter Overview 8 of 32 PowerCenter 8.x/9.

PowerCenter Overview 1.9 Example: Application Integration • Company A purchases Company B • To achieve the benefits of consolidation.0 Level I Developer Copyright © 2010 Informatica Corp . Company B’s billing system must be integrated into Company A’s billing system Billing A Informatica PowerCenter Billing B Module 1: PowerCenter Overview 9 of 32 PowerCenter 8.x/9.

product.x/9. reference data hubs. etc. supplier.PowerCenter Overview 1. single view of customer.10 Example: Data Warehousing • Data warehouses put information from many sources together for analysis • Data is moved from many databases to the warehouse Manufacturing (DB2) Accounting (SAP) Inventory (SQL Server) Sales (SalesForce) Resource Planning (PSFT) Marketing (ORCL) Billing (Sybase) Informatica PowerCenter Data Warehouse 10 of 32 Module 1: PowerCenter Overview Additional Examples of Data Integration In addition to the examples given on these slides. employee. PowerCenter is deployed for: • Data Synchronization – ongoing exchange of data between disparate applications • Data Hubs – master data management. real-time reporting PowerCenter 8. • Business Activity Monitoring – business process improvement.0 Level I Developer Copyright © 2010 Informatica Corp .

0 Level I Developer Copyright © 2010 Informatica Corp .x/9.PowerCenter Overview 1.11 Data Integration Methodology: ETL Source(s) •Extract the data from a source system •Transform it as needed Data Integration! •Load it to a target system Target(s) Module 1: PowerCenter Overview 11 of 32 PowerCenter 8.

12 ETL for Data Warehousing Operational Systems RDBMS Mainframe Other Decision Support Data Warehouse • Transaction data • Optimized for transaction response time • Current • Normalized or De-normalized data • Aggregate data • Cleanse data • Consolidate data • Apply business rules • De-normalize data • Aggregated data • Historical data Transform ETL Extract Load 12 of 32 Module 1: PowerCenter Overview PowerCenter 8.PowerCenter Overview 1.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .

or from a file • This database or file is referred to as the source • The structure of the source is contained in a source definition object. row by row.0 Level I Developer Copyright © 2010 Informatica Corp .PowerCenter Overview 1. Extract Source Informatica PowerCenter Module 1: PowerCenter Overview 13 of 32 PowerCenter 8.13 ETL: Extract • PowerCenter reads data. from a table (or group of related tables) in a database.x/9.

x/9.PowerCenter Overview 1.14 ETL: Transform • PowerCenter converts the rows into a format the second (target) system will be able to use • The logic for this conversion is defined in transformation objects Extract Transform Source Informatica PowerCenter Module 1: PowerCenter Overview 14 of 32 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

x/9. row by row. or to a file • This database or file is referred to as the target • The structure of the target is contained in a target definition object Extract Transform Load Source Informatica PowerCenter Target Module 1: PowerCenter Overview 15 of 32 PowerCenter 8. to a table (or group of related tables) in a database.15 ETL: Load • PowerCenter writes data.PowerCenter Overview 1.0 Level I Developer Copyright © 2010 Informatica Corp .

PowerCenter 8.x/9. in sequence or in parallel. applies transformation logic to the data. and writes the transformed data to targets.0 Level I Developer Copyright © 2010 Informatica Corp .PowerCenter Overview 1. It reads data from sources.16 Mapping • A set of transformations. that move and transform data from one or more source(s) to one or more target(s) • Mappings exist entirely inside PowerCenter Informatica PowerCenter Source(s) Target(s) transformations mapping Module 1: PowerCenter Overview 16 of 32 Mappings A mapping logically defines the ETL process.

0 Level I Developer Copyright © 2010 Informatica Corp .x/9.PowerCenter Overview 1.17 Transformations • Transformations receive data and transform it • Generate new fields • Modify data • Select and pass data Transformations Module 1: PowerCenter Overview 17 of 32 PowerCenter 8.

18 Session • The object that runs a mapping Session Mapping Transformation Module 1: PowerCenter Overview 18 of 32 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.PowerCenter Overview 1.

A session is a task that runs a mapping. Other tasks include: • Command – runs a shell script • Email – sends an email • Decision – branches a workflow conditionally • Timer – waits for a defined period PowerCenter 8.x/9.0 Level I Developer Copyright © 2010 Informatica Corp . functions.PowerCenter Overview 1.19 Workflow • An ordered set of one or more sessions and other tasks. designed to accomplish an overall operational purpose Other Tasks Workflow Session Mapping Transformation Module 1: PowerCenter Overview 19 of 32 Tasks A task is an executable set of actions. or commands.

etc) • Datatype (character string. Metadata The word metadata literally means “data about data. decimal. etc. which may reside in any of a number of supported relational database management systems.x/9. and workflows PowerCenter 8. transformations.” It is the information that describes data. database table. integer.) • Mapping logic • Workflow logic • Stored in a metadata repository Repository Module 1: PowerCenter Overview 20 of 32 Note The repository is implemented as a schema. Common contents of metadata include the source of a dataset. targets. and its limitations. precision.0 Level I Developer Copyright © 2010 Informatica Corp . Metadata in PowerCenter PowerCenter uses metadata to define sources. XML file. how it should be accessed. etc) • Other attributes (length.PowerCenter Overview 1. mappings.20 Metadata • Defines data and processes • Examples: • Source and target definitions • Type (flat file.

5 Architecture ODBC Sources Native drivers/ ODBC Domain Integration Service TCP/IP Native drivers/ ODBC Targets TCP/IP ODBC TCP/IP Repository Service Repository Service Process HTTPS Administration Console Security Domain Native drivers PowerCenter Client Native drivers Repository Domain Metadata 21 of 32 Module 1: PowerCenter Overview Sources and Targets Can be relational tables or heterogeneous files (such as flat files. VSAM files.PowerCenter Overview 1.0 Level I Developer Copyright © 2010 Informatica Corp . execute workflows on the Integration Service. and manage the repository PowerCenter 8. monitor the workflows. inserts. and updates repository metadata Contains all the metadata needed to run the ETL process Integration Service Repository Service Repository Service Process Repository Client Tools Desktop tools used to populate the repository with metadata. or XML) The engine which performs all the ETL logic Manages connectivity to metadata repositories that contain mapping and workflow definitions Multithreaded process that retrieves.21 PowerCenter 8.x/9.

a workspace to the right.5) Designer Workflow Manager Workflow Monitor Create ETL mappings Monitor and Create and start control workflows workflows Module 1: PowerCenter Overview 22 of 32 Note Designer and Repository Manager access the repository through the Repository Service.x/9. Workflow Manager and Workflow Monitor connect to the Integration Service. The UIs typically have toolbars.1) Administration Console (browser-based) Perform domain and repository service tasks: • Create/configure nodes and repository services • Upgrade/delete • Start/stop • Backup/restore • Manage users and groups (In PowerCenter 8. Each client has its own user interface.22 PowerCenter Client Applications Administration Administration Console Development Repository Manager Manage repository • connections • folders • objects • users and groups (in PowerCenter 8. a navigation window to the left.PowerCenter Overview 1. and an output window at the bottom.0 Level I Developer Copyright © 2010 Informatica Corp . PowerCenter 8.

Targets Client Apps* Designer Tools Transformation toolbar Workspace Navigator Window Output Window Status Bar * Single login to client applications – click on icons to open other tools – they are already connected to repository Module 1: PowerCenter Overview 23 of 32 PowerCenter 8.PowerCenter Overview 1.23 Designer: Create Mappings. Sources.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.

PowerCenter Overview 1.24 Designer Tools Target Transformation Mapplet Source Designer: Developer: Designer: Analyzer: create create source create target create reusable objects transformations mapplets objects Mapping Designer: create mappings Module 1: PowerCenter Overview 24 of 32 PowerCenter 8.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .

allows editing Ports represent table columns or file fields Module 1: PowerCenter Overview 25 of 32 PowerCenter 8.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .25 Transformation 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.PowerCenter Overview 1.

PowerCenter Overview 1.x/9.26 Workflow Manager: Create and Run Workflows Connections Client Applications Tasks Navigator Window Workflow Manager Tools Workspace Status Bar Output Window Module 1: PowerCenter Overview 26 of 32 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

27 Workflow Manager Tools Create reusable tasks Create worklets Create workflows Module 1: PowerCenter Overview 27 of 32 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .PowerCenter Overview 1.x/9.

0 Level I Developer Copyright © 2010 Informatica Corp .x/9.PowerCenter Overview 1.28 Session Tasks: Run a Single Mapping ƒ Iconized view – shows the task in relation to the rest of the workflow ƒ Edit view – shows task properties. allows editing ƒ Two or more Sessions can point to a single mapping Module 1: PowerCenter Overview 28 of 32 PowerCenter 8.

x/9.PowerCenter Overview 1.0 Level I Developer Copyright © 2010 Informatica Corp .29 Workflow Monitor: View Workflow Progress Navigator Window Output Window Gantt Chart View Task View Time Window Module 1: PowerCenter Overview 29 of 32 PowerCenter 8.

x/9.PowerCenter Overview 1.30 Repository Manager: Administer Folders Navigator Window Status Bar Output Window Main Window Module 1: PowerCenter Overview 30 of 32 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

Because creation of Staging tables is fairly trivial. PowerCenter 8. we are simulating part of the creation of a (very simple) Dimensional Data Warehouse.x/9. you will begin with data in OLTP tables and flat files. used for populating ODS Business Function: ODS/EDW Operational Data Store or Electronic Data Warehouse is normalized data in an enterprise data Model that aligns data from various OLTP Systems DB Schema: ODSxx Business Function: DDW Dimensional Data Warehouse uses Fact and Dimension tables in second normal form to speed report generation and allow for historical data Covered in Level two Developer class DB Schema: SDBU DB Schema: STGxx Module 1: PowerCenter Overview 31 of 32 Note In the labs for this course.PowerCenter Overview 1.31 Class Scenario Business Function: OLTP Data in an online Transaction processing system Business Function: Staging Data format similar to OLTP. This will provide more realistic uses of the capabilities of PowerCenter. you will do more work on moving data from STG to ODS. bring data to Staging.0 Level I Developer Copyright © 2010 Informatica Corp . In these labs. and from Staging (STG) to the Operational Data Store (ODS).

32 Summary This module showed you how to: • Explain the purposes of PowerCenter • Define terms used in PowerCenter • Name major PowerCenter components Module 1: PowerCenter Overview 32 of 32 PowerCenter 8.PowerCenter Overview 1.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.

x/9.1 Module 2: Mapping Fundamentals PowerCenter 8.Mapping Fundamentals 2.0 Level I Developer Copyright © 2010 Informatica Corp .

0 Level I Developer Copyright © 2010 Informatica Corp .x/9.Mapping Fundamentals 2.2 Module Objectives After completing this module you will be able to • Create source and target definitions from flat files and relational tables • Create a mapping using existing source and target definitions • Use links to connect ports Module 2: Mapping Fundamentals 2 of 22 PowerCenter 8.

delete. update.x/9.Mapping Fundamentals 2. reject Router: routes rows conditionally Union: Performs a union-all join between two data streams Module 2: Mapping Fundamentals 3 of 22 PowerCenter 8.3 PowerCenter Transformations (partial list) Source Qualifier: reads from data sources Expression: performs row-level calculations Filter: uses a condition statement to select rows for inclusion Sorter: sorts data Aggregator: performs aggregate calculations Joiner: joins heterogeneous sources Lookup: looks up values and passes them to other objects Update Strategy: tags rows for insert.0 Level I Developer Copyright © 2010 Informatica Corp .

0 Level I Developer Copyright © 2010 Informatica Corp .Mapping Fundamentals 2.4 Specialized PowerCenter Transformations Transaction Control: allows data-driven commits and rollbacks Java: allows Java code to be used within PowerCenter Midstream XML Parser: parses XML anywhere in a mapping Midstream XML Generator: creates XML anywhere in a mapping More Source Qualifiers: read from XML.x/9. message queues and applications Module 2: Mapping Fundamentals 4 of 22 PowerCenter 8.

x/9.Mapping Fundamentals 2.5 PowerCenter Designer • Provides tools to define and manipulate • • • • • Sources Targets Transformations Mappings Other objects Module 2: Mapping Fundamentals 5 of 22 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

dynamic links to the objects contained in that folder used by mappings in other folders. Technically. regardless of the “blue arm” icon. and managed in the Repository Manager application. The “blue arm” icon indicates that the folder permits shortcuts. They are created in the Administration Console application. Shortcut Folders PowerCenter 8. all folders are “shared” with all users who have the appropriate folder permissions.x/9. The folders are PowerCenter repository objects and are not related to Windows directories. Folder Management Folders are created and managed in the Repository Manager application.Mapping Fundamentals 2.0 Level I Developer Copyright © 2010 Informatica Corp . objects are organized in folders Repository Folder Sub folders Module 2: Mapping Fundamentals 6 of 22 Repository Management Repositories are not created and managed in the Designer application. Do not confuse repository folders with the directories visible in Windows Explorer.6 Repositories • Objects are stored as metadata in repositories • Within a repository.

x/9. PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp . Placing each source in a folder based on its connection type avoids confusion when this is the case.7 Source Definitions • Defines the structure of a data source such as a relational database table or a flat file • Created using the Source Analyzer in the PowerCenter Designer application • Enables you to preview the data in the source Flat file sources Relational Database Connections Tables in DB source OLTP Module 2: Mapping Fundamentals 7 of 22 Note Two sources from different systems may use the same name.Mapping Fundamentals 2.

and PeopleSoft • PowerExchange • Mainframes Module 2: Mapping Fundamentals 8 of 22 PowerCenter 8.8 Source Analyzer • The Designer tool for creating source definitions • Import source definitions from: • • • • • Relational databases Flat files XML sources Cobol sources Applications such as SAP.Mapping Fundamentals 2. Siebel.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.

PowerCenter 8.x/9. Converts native source datatypes to PowerCenter transformation datatypes. All ports are input/output. Ports Represent table columns or file fields.Mapping Fundamentals 2.9 Source Qualifier Transformation • Selects records from flat file and relational table sources and converts to PowerCenter internal datatypes Module 2: Mapping Fundamentals 9 of 22 Type Description Active Mandatory for all flat file and relational sources in a mapping. For relational tables.0 Level I Developer Copyright © 2010 Informatica Corp . Selects records from flat file and relational table sources. creates a SQL SELECT statement.

10 Lab 2-1 – Creating Source Definitions In the lab you will: • Use wizards to import Source definitions from a flat file and a relational database table • Preview the data in the Sources Module 2: Mapping Fundamentals 10 of 22 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.Mapping Fundamentals 2.

x/9.Mapping Fundamentals 2.11 Target Definitions • Define the structure of a target such as a relational database table or a flat file • Created using the Target Designer in the PowerCenter Designer application • Can be • Copied from a source object • Imported from relational database • Imported from flat file • A shortcut to a target in another folder Module 2: Mapping Fundamentals 11 of 22 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

12 Target Designer • The Designer tool for creating targets • Wizards import target definitions from • • • • Flat files Relational database tables XML Applications such as SAP BF and MQ Series Module 2: Mapping Fundamentals 12 of 22 PowerCenter 8.Mapping Fundamentals 2.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.

0 Level I Developer Copyright © 2010 Informatica Corp .x/9.13 Lab 2-2 – Creating Target Definitions In the lab you will: • Create a Target definition from scratch • Create a Target definition from a Source definition and change the Target type Module 2: Mapping Fundamentals 13 of 22 PowerCenter 8.Mapping Fundamentals 2.

0 Level I Developer Copyright © 2010 Informatica Corp .Mapping Fundamentals 2.14 Shortcuts • A shortcut is a dynamic link to the original object • Usually a target or source definition • The original object must be in a shortcut folder • Not all folders permit creation of shortcuts • Shortcut folders display with a “hand” (similar to a shared folder in Windows Explorer) • To create a shortcut drag the object to another open folder or any workspace where the object type is allowed • Shortcuts appear in the Navigator window with a small curved arrow Module 2: Mapping Fundamentals 14 of 22 PowerCenter 8.x/9.

and is easily translated from and to the native datatypes of application databases Note Integration datatypes are sometimes referred to as “ASCII Neutral” PowerCenter 8.15 Datatypes • PowerCenter must “know” the data types used internally by both source and target systems • These are called native datatypes • The Source Qualifier converts the source data to a standard format used internally by PowerCenter • This is the integration or transformation datatype • The target definition object converts it to the native datatype of the target system Module 2: Mapping Fundamentals 15 of 22 Note The integration datatype standardizes transformations.Mapping Fundamentals 2.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .

Mapping Fundamentals 2. consult Help Æ Content Æ Index Æ port-to-port data conversion PowerCenter 8.x/9. native and transformation datatypes must be compatible (or must be explicitly converted) Module 2: Mapping Fundamentals 16 of 22 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 l other numeric datatypes • Numeric datatypes l string • Date/Time l date or string For further information.16 Datatype Conversion NATIVE DATATYPES TRANSFORMATION DATATYPES Specific to the source and target database types Display in source and target tables within Mapping Designer PowerCenter internal datatypes Display in transformations within Mapping Designer Source DB native datatypes Transformation datatypes Target DB native datatypes ƒ ƒ Transformation datatypes allow mix and match of source and target database types When connecting ports. in the PowerCenter client.0 Level I Developer Copyright © 2010 Informatica Corp .

17 Transformation Ports • Data passes into and out of transformations through input and output ports Input Ports Output Ports Module 2: Mapping Fundamentals 17 of 22 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .Mapping Fundamentals 2.x/9.

PowerCenter 8.18 Passive transformations • One row comes in. provided only that the rows going out are a one-for-one match with the rows going in.Mapping Fundamentals 2. one row goes out – one-for-one input to output • Same number of rows output as input • Example: a transformation that converts character data to numerical data 3 rows in Passive Transformation 3 rows out “(510) 555-7283” “(613) 382-2929” “(650) 385-5000” 5105557283 6133822929 6503855000 Module 2: Mapping Fundamentals 18 of 22 Note The transformation is considered “passive” regardless of what transformations take place within a row.x/9. Examples Examples of passive transformations include Expression and Lookup transformations.0 Level I Developer Copyright © 2010 Informatica Corp .

PowerCenter 8. and Sorter transformations. Router.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .Mapping Fundamentals 2. many rows out • May not be the same number output as input • Example: a transformation that discards rows with bad data 3 rows in 2 rows out “(510) 555-7283” (613) 382-299 (650) 385-5000 Active Transformation 5105557283 6503855000 Module 2: Mapping Fundamentals 19 of 22 Examples Examples of active transformations include Filter.19 Active Transformations • Many rows in.

Mapping Fundamentals 2.com Note We do not use the Velocity templates in this course Note In Velocity. exp_.x/9. PowerCenter 8.informatica. see http://devnet. agg_. the standard is to begin the names of all Source Qualifier objects with “SQ_”. … • Best practices Module 2: Mapping Fundamentals 20 of 22 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.20 Velocity Methodology Informatica’s Velocity methodology includes: • Templates • Mapping specification templates • Source to target field matrix • Naming conventions • Object type prefixes: m_. The Mapping Designer automatically names the Source Qualifier this way when you drag a Source object onto the Mapping canvas. s_. followed by the name of the source.0 Level I Developer Copyright © 2010 Informatica Corp . wfl_.

x/9.Mapping Fundamentals 2.0 Level I Developer Copyright © 2010 Informatica Corp .21 Lab 2-3 – Creating Mappings • In the lab you will: • Create shortcuts to objects in the shortcut (SC) folder • Create a pass-through Mapping that brings data from a single Source to a single Target Module 2: Mapping Fundamentals 21 of 22 PowerCenter 8.

Mapping Fundamentals 2.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.22 Summary This module showed you how to • Create source and target definitions from flat files and relational tables • Create a mapping using existing source and target definitions • Use links to connect ports Module 2: Mapping Fundamentals 22 of 22 PowerCenter 8.

1 Module 3: Workflow Basics PowerCenter 8.0 Level 1 Developer Copyright © 2010 Informatica Corp .Workflow Basics 3.x/9.

0 Level 1 Developer Copyright © 2010 Informatica Corp .x/9. and verify the results Module 3: Workflow Basics 2 of 13 PowerCenter 8. monitor its execution.2 Module Objectives After completing this module you will be able to: • Create a basic Workflow and link its tasks • Run a Workflow.Workflow Basics 3.

x/9.Workflow Basics 3.0 Level 1 Developer Copyright © 2010 Informatica Corp .3 PowerCenter Tasks Session: Run the logic of a mapping Command: Run external commands Email: Send an email to a defined recipient Decision: Choose between paths in a Workflow Assignment: Assign values to variables Timer: Wait or pause for specified time Control: Terminate or fail a Workflow Event Wait: Wait for an event Event Raise: Cause an Event Wait task to trigger Module 3: Workflow Basics 3 of 13 PowerCenter 8.

x/9.0 Level 1 Developer Copyright © 2010 Informatica Corp .4 Workflow Object • Executes a series of Mappings (as Sessions) and other tasks Module 3: Workflow Basics 4 of 13 PowerCenter 8.Workflow Basics 3.

Workflow Basics 3.0 Level 1 Developer Copyright © 2010 Informatica Corp .x/9.5 Workflow Manager • The Workflow Manager is the PowerCenter application that enables designers to build and run workflows • Can be launched from Designer by clicking the “W” icon Module 3: Workflow Basics 5 of 13 PowerCenter 8.

x/9.0 Level 1 Developer Copyright © 2010 Informatica Corp .Workflow Basics 3.6 Workflow Designer • The tool in Workflow Manager where you create Workflow objects Module 3: Workflow Basics 6 of 13 PowerCenter 8.

x/9.0 Level 1 Developer Copyright © 2010 Informatica Corp .7 Start Task • Is always the first task in a Workflow Module 3: Workflow Basics 7 of 13 PowerCenter 8.Workflow Basics 3.

8 Session Task • Implements the execution of a Mapping Module 3: Workflow Basics 8 of 13 PowerCenter 8.0 Level 1 Developer Copyright © 2010 Informatica Corp .x/9.Workflow Basics 3.

Workflow Basics 3.x/9.0 Level 1 Developer Copyright © 2010 Informatica Corp .9 Links in Workflows • Indicate the flow of control from one task to the next • The flow may branch either: • Unconditionally (multiple links are followed from a single task) • Using Decision tasks (only one branch is followed) Module 3: Workflow Basics 9 of 13 PowerCenter 8.

0 Level 1 Developer Copyright © 2010 Informatica Corp .10 Running a Workflow • Right-click in the Workflow and select “Start Workflow” • Passes control to Workflow Monitor Module 3: Workflow Basics 10 of 13 PowerCenter 8.x/9.Workflow Basics 3.

0 Level 1 Developer Copyright © 2010 Informatica Corp .x/9.11 Workflow Monitor • Displays all Workflows and tasks in real time • Provides access to logs and results Module 3: Workflow Basics 11 of 13 PowerCenter 8.Workflow Basics 3.

0 Level 1 Developer Copyright © 2010 Informatica Corp .x/9.12 Lab 3-1: Create and Run Workflows • In this lab you will… • Create and run Workflows that run the Mappings you created in Lab 3 Module 3: Workflow Basics 12 of 13 PowerCenter 8.Workflow Basics 3.

0 Level 1 Developer Copyright © 2010 Informatica Corp .Workflow Basics 3.x/9. and verify the results Module 3: Workflow Basics 13 of 13 PowerCenter 8. monitor its execution.13 Summary This module showed you how to: • Create a basic Workflow and link its tasks • Run a Workflow.

0 Level 1 Developer Copyright © 2010 Informatica Corp .Workflow Basics 3.x/9.14 PowerCenter 8.

Expression and Filter Transformations 4.1 Module 4: Expression and Filter Transformations PowerCenter 8.0 Level 1 Developer Copyright © 2010 Informatica Corp .x/9.

2 Module Objectives After completing this module you will be able to: • Use Expression transformations to perform calculations on a row-by-row basis • Use Filter transformations to pass rows based on userdefined conditions Module 4: Expression and Filter Transformations 2 of 19 PowerCenter 8.Expression and Filter Transformations 4.x/9.0 Level 1 Developer Copyright © 2010 Informatica Corp .

x/9. replace strings.3 Expression Transformation Performs row-level calculations (no aggregate functions) Click here to invoke the Expression Editor Module 4: Expression and Filter Transformations 3 of 19 Type Description Passive Modifies individual ports (columns) within a single row.) • Numerical calculations • Scientific calculations • Special functions (lookup. Business Purpose Use the logical and arithmetic operators and built-in functions for: • Character manipulation (concatenate. Can add and suppress ports. etc. truncate.Expression and Filter Transformations 4. etc. number. truncate.) • Datatype conversion (to char. etc.) • Data manipulation (round. Cannot perform aggregation across multiple rows.0 Level 1 Developer Copyright © 2010 Informatica Corp . etc. etc. to date. decode.) PowerCenter 8. etc.) • Testing (for spaces.) • Data cleansing (check nulls.

0 Level 1 Developer Copyright © 2010 Informatica Corp .Expression and Filter Transformations 4. multiply.x/9.4 Uses of Expression Transformation: Examples • • • • • Adjust employee salaries Concatenate first and last names Convert strings to numbers Arithmetic – add. subtract. divide numeric values Test conditional statements and pass the results to target tables or other transformations Module 4: Expression and Filter Transformations 4 of 19 PowerCenter 8.

constants and return values from other transformations Module 4: Expression and Filter Transformations 5 of 19 Comments Comments can be added to expressions by prefacing them with //.x/9.5 Expression Editor • An expression is a calculation or conditional statement for a specific port • Can contain other ports. functions. variables. PowerCenter 8. This allows later developers to understand the logic behind an expression.Expression and Filter Transformations 4. operators.0 Level 1 Developer Copyright © 2010 Informatica Corp .

g. GET_DATE_PART.5.Expression and Filter Transformations 4.6 Functions Provided Character manipulation e. LTRIM. ISNULL.g. IS_NUMBER Update variables e. the expression LENGTH (“HELLO WORLD”) / 2 returns the numerical value 5.g. CONCAT.g. SETMINVARIABLE Module 4: Expression and Filter Transformations 6 of 19 Tip Highlighting a function and pressing F1 will launch the online help at the selected function section. For example. UPPER Datatype conversion e. IIF. ISNULL. TO_CHAR. TO_DECIMAL Detect & correct errors e.x/9.g. SIN. COS.g.g. DECODE Test values e. REPLACECHR Manipulate dates e. LOG. SQRT More mathematical operations e. Note All expressions resolve to a single value of a specific datatype. POWER. PowerCenter 8. SETVARIABLE. e. IS_DATE.g.0 Level 1 Developer Copyright © 2010 Informatica Corp .g. DIFF_DATES Mathematical operations e. TAN Special constructs.

To output the contents of a variable port. the I and O checkboxes are unavailable (grayed out). indicating that a variable port can not be used for input or output. only in Edit view Module 4: Expression and Filter Transformations 7 of 19 Note Variable ports cannot be output directly. create an output port whose value is the variable.7 Variable Ports ƒ Use to: ƒ Simplify complex expressions ƒ Example: extract month from a date for use in several output ports ƒ Provide storage for temporary values ƒ Improve efficiency ƒ Variable ports are not visible in Normal view. PowerCenter 8. When V is checked.Expression and Filter Transformations 4. Creating A transformation variable is created by creating a port and selecting the V check box.x/9.0 Level 1 Developer Copyright © 2010 Informatica Corp .

The result must be compatible with the port’s datatype. The variable persists across the set of records.Expression and Filter Transformations 4. the expression is evaluated and the result is assigned to the variable port. string to “”) when the Mapping logic is processed Module 4: Expression and Filter Transformations 8 of 19 Note When a record is processed. and may be used or modified anywhere in the set of records.x/9. PowerCenter 8.8 Variable Ports (Continued) ƒ Variables are initialized (numeric to 0.0 Level 1 Developer Copyright © 2010 Informatica Corp .

x/9.0 Level 1 Developer Copyright © 2010 Informatica Corp .9 Order of Evaluation • PowerCenter evaluates ports in the following order: • Input and Input/Output ports • Variable ports • Output ports • Variable ports are evaluated in the order they appear in the Ports tab • Order of evaluation is critical when one variable refers to another • Reference to a variable that has not yet been evaluated will use the value from the previous row • This is always Null for the first row in the datastream – can cause errors! Module 4: Expression and Filter Transformations 9 of 19 PowerCenter 8.Expression and Filter Transformations 4.

0 Level 1 Developer Copyright © 2010 Informatica Corp .x/9.Expression and Filter Transformations 4. correct number of arguments in functions.10 Expression Validation The Validate and OK buttons in the Expression Editor both parse the current expression to: ƒ Resolve references to ports in other transformations ƒ Parse default values ƒ Check spelling. other syntactical errors Module 4: Expression and Filter Transformations 10 of 19 PowerCenter 8.

Expression and Filter Transformations 4. some in lower case.x/9.11 Expression Example 1 • Check.0 Level 1 Developer Copyright © 2010 Informatica Corp . Clean. and Record Errors • Clean up item name • Some item names are in UPPERCASE. some in MiXEd • They should all be in Title Case • Missing data • Some records are incomplete • Invalid dates • Sometimes dates are input in an invalid format • Invalid numbers • Certain numeric fields sometimes contain nonnumeric data • Reporting • Need a count of the changes to item names • Incorrect and missing data should be tagged and a report generated Module 4: Expression and Filter Transformations 11 of 19 PowerCenter 8.

x/9.12 Expression Example 1 Solution • Item names can be set to title case using the INITCAP function • The ISNULL function will detect null values • The IS_DATE and IS_NUMBER functions can check for correct formatting • Variables can be used to count the number of errors detected or corrected Module 4: Expression and Filter Transformations 12 of 19 PowerCenter 8.Expression and Filter Transformations 4.0 Level 1 Developer Copyright © 2010 Informatica Corp .

x/9.Expression and Filter Transformations 4.13 Expression Example 2 • Calculate Sales Discounting and Inventory Days • Discount tracking • Compare the suggested sale price to the actual sale price to determine the level of discounting • Create a field that tracks this comparison for reporting • Days in Inventory • Determine how long a given item has been in inventory Module 4: Expression and Filter Transformations 13 of 19 PowerCenter 8.0 Level 1 Developer Copyright © 2010 Informatica Corp .

Expression and Filter Transformations 4. 10) unless applicable Module 4: Expression and Filter Transformations 14 of 19 PowerCenter 8.14 Performance Considerations for Expressions • Avoid multiple conversions of the same data • Decimal Æ String Æ Decimal • Integer Æ Decimal Æ Integer • Date Æ String Æ Date • Strings are more ‘expensive’ for the server to process than mathematical calculations • Avoid default data type/size for new ports (string.0 Level 1 Developer Copyright © 2010 Informatica Corp .x/9.

Expression and Filter Transformations

4.15

Filter Transformation
Passes rows conditionally

Module 4: Expression and Filter Transformations

15 of 19

Type Description

Active Allows 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.

PowerCenter 8.x/9.0 Level 1 Developer

Copyright © 2010 Informatica Corp

Expression and Filter Transformations

4.16

Filter Example
• Existing customer records need to be updated to reflect changes to columns such as address
• However, only existing customer records are to be updated – not new customer records

• Use a Filter transformation to pass only customer records with a legitimate master customer ID number

Module 4: Expression and Filter Transformations

16 of 19

PowerCenter 8.x/9.0 Level 1 Developer

Copyright © 2010 Informatica Corp

Expression and Filter Transformations

4.17

Lab 4-1 – Using Filters and Expressions
• In this lab you will…
• Move data from the Customer staging table to the ODS database
• Use an Expression transformation to reformat data • Use a Filter transformation to pass only valid records

Module 4: Expression and Filter Transformations

17 of 19

PowerCenter 8.x/9.0 Level 1 Developer

Copyright © 2010 Informatica Corp

Expression and Filter Transformations

4.18

Lab 4-2 – Features and Techniques
• In this lab you will…
• Learn some features and techniques that will increase your efficiency as a PowerCenter Developer

Module 4: Expression and Filter Transformations

18 of 19

PowerCenter 8.x/9.0 Level 1 Developer

Copyright © 2010 Informatica Corp

Expression and Filter Transformations

4.19

Summary
This module showed you how to: • Use Expression transformations to perform calculations on a row-by-row basis • Use Filter transformations to pass rows based on userdefined conditions

Module 4: Expression and Filter Transformations

19 of 19

PowerCenter 8.x/9.0 Level 1 Developer

Copyright © 2010 Informatica Corp

0 Level 1 Developer Copyright © 2010 Informatica Corp .20 Module 4: Expression and Filter Transformations 20 of 19 PowerCenter 8.Expression and Filter Transformations 4.x/9.

Joining and Merging Data 5.x/9.1 Module 5: Joining and Merging Data PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

0 Level I Developer Copyright © 2010 Informatica Corp .2 Module Objectives After completing this module you will be able to: • Use pipeline branches in Mappings • Join homogeneous Sources using a Source Qualifier • Define heterogeneous joins using the Joiner transformation • Merge records from multiple places into one record set using the Union transformation • Create and use reusable transformations Module 5: Joining and Merging Data 2 of 22 PowerCenter 8.Joining and Merging Data 5.x/9.

Joining and Merging Data 5.0 Level I Developer Copyright © 2010 Informatica Corp .3 Source Pipelines • Each Source Qualifier transformation starts a single Source pipeline • A single Mapping can have multiple Source pipelines • Each pipeline must terminate with at least one Target • Transformations can split one source pipeline into multiple pipeline branches 1 mapping T Source pipeline T T T 2 pipeline branches SQ T T T Module 5: Joining and Merging Data 3 of 22 PowerCenter 8.x/9.

Joining and Merging Data 5.4 Multiple Pipelines • A single Mapping may contain more than one pipeline SQ 2 source pipelines T T T T T T T 1 mapping SQ T Module 5: Joining and Merging Data 4 of 22 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.

Joining and Merging Data 5.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.5 Homogeneous Joins • Homogeneous joins combine data from tables in the same database related by a common field • The join is specified in the Source Qualifier transformation • The join is performed on the Source database at runtime • When SQL generated by the SQ transformation executes Source 1 Source 2 SQ T Module 5: Joining and Merging Data 5 of 22 PowerCenter 8.

such as tablea. a join condition is automatically created • You can enter a join condition.employee_id=tableb.0 Level I Developer Copyright © 2010 Informatica Corp .employee_id • Default is inner join Module 5: Joining and Merging Data 6 of 22 PowerCenter 8.x/9.Joining and Merging Data 5.6 Defining Homogeneous Joins • If the tables have a Primary/Foreign Key relationship in the database.

Joining and Merging Data 5.x/9.7 Example of Homogeneous Join • A business updates its Product ODS table regularly • This requires a join of Product and Product-Cost • The two tables • Are in the same database • Have a primary/foreign key relationship based on Product_ID Module 5: Joining and Merging Data 7 of 22 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

8 Heterogeneous Joins • Heterogeneous joins are joins using dissimilar sources. Specifically.0 Level I Developer Copyright © 2010 Informatica Corp . such as a matching ID field Master Source Joiner Detail Source Join Condition: Master.Joining and Merging Data 5.CustomerID = Detail. the pipeline from the Detail source ends at the Joiner.x/9. the other Detail • The Joiner selects rows from the two sources based on a join condition. PowerCenter 8. such as • Oracle table and DB2 table • Flat file and database table • Two flat files • Use a Joiner transformation (performs the join within the mapping) • One source is designated the Master. flowing into the pipeline from the Master source.CustomerID Module 5: Joining and Merging Data Join Results 8 of 22 Pipelines A Joiner transformation combines two pipelines into a single transformation.

the other Detail • M property indicates ports from the Master Source when checked Module 5: Joining and Merging Data 9 of 22 Type Description Active Combines fields from two data sources into a single combined data source.0 Level I Developer Copyright © 2010 Informatica Corp .Joining and Merging Data 5. 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 PowerCenter 8.x/9.9 Joiner Transformation Performs heterogeneous joins on two data flows Ports • Input or Input/Output • One Source is designated Master.

0 Level I Developer Copyright © 2010 Informatica Corp .x/9.10 Joiner Example • Sales transaction data resides on a flat file • Product data resides on a relational table • Sales transactions require product data Module 5: Joining and Merging Data 10 of 22 PowerCenter 8.Joining and Merging Data 5.

keeps all rows from Master and matching rows from Detail • Full outer join .11 Join Types • Normal (inner) join – keeps only matching rows based on the condition • Master outer join .x/9.Joining and Merging Data 5.0 Level I Developer Copyright © 2010 Informatica Corp .keeps all rows from both Master and Detail Module 5: Joining and Merging Data 11 of 22 PowerCenter 8.keeps all rows from Detail and matching rows from Master • Detail outer join .

Joining and Merging Data 5.12 Specify Join Type Module 5: Joining and Merging Data 12 of 22 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.

0 Level I Developer Copyright © 2010 Informatica Corp .13 Specify Join Condition Module 5: Joining and Merging Data 13 of 22 PowerCenter 8.x/9.Joining and Merging Data 5.

each row in the detail Source is compared to the values in the index cache • Upon a match. the rows from the data cache are included in the outgoing data stream Module 5: Joining and Merging Data 14 of 22 PowerCenter 8.Joining and Merging Data 5.0 Level I Developer Copyright © 2010 Informatica Corp .14 Joiner Cache • Two types of cache memory: index cache and data cache • All rows from the master Source are read into cache • Index cache contains values for all ports from the master Source which are part of the join condition • Data cache contains those port values not specified in the join condition • After the cache is loaded.x/9.

Module 5: Joining and Merging Data 15 of 22 PowerCenter 8.x/9.%ile value • Must set for both values • The Integration Service compares the two and uses the lower value as the maximum memory limit • If this value is set to 0 for either attribute.15 Enable Automatic Memory Settings • Configure values for: • Maximum Memory Allowed for Automatic Memory Attributes – numeric value • Maximum Percentage of Total Memory Allowed for Automatic Memory Attributes .Joining and Merging Data 5.0 Level I Developer Copyright © 2010 Informatica Corp . the Integration Service disables automatic memory settings and uses default values.

16 Union Transformation • Merges row sets from multiple pipelines One output port group One or more input port groups Module 5: Joining and Merging Data 16 of 22 Type Description Active Merges data from multiple pipelines or pipeline branches to a single pipeline branch. Does not remove duplicate rows. similar to the SQL statement UNION ALL. Business Purpose Enables you to convert data from multiple sources into a single rowset PowerCenter 8.Joining and Merging Data 5.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.

0 Level I Developer Copyright © 2010 Informatica Corp .17 Union Groups • Create groups on the Groups tab • Each group has an identical set of ports Module 5: Joining and Merging Data 17 of 22 PowerCenter 8.x/9.Joining and Merging Data 5.

18 Group Ports • Create on the Group Ports tab Module 5: Joining and Merging Data 18 of 22 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.Joining and Merging Data 5.

x/9.e. PRODUCT_ID3) Module 5: Joining and Merging Data 19 of 22 PowerCenter 8.Joining and Merging Data 5.0 Level I Developer Copyright © 2010 Informatica Corp . “PRODUCT_ID” • Copies of each port appear in the Input groups (i..19 Union Ports • Each group port created appears in the Output group (i..e. PRODUCT_ID2.

As a result.Joining and Merging Data 5. changing a reusable transformation may invalidate the mappings containing instances of the transformation. PowerCenter 8.x/9.20 Reusable Transformations • Create in Transformation Developer • Or create in Mapping Designer and ‘promote’ • Listed in Transformations node of navigator • Drag and drop into any mapping Module 5: Joining and Merging Data 20 of 22 Warning Instance of reusable transformations inherit any changes to the reusable transformation. Note To make a non-reusable copy of a reusable transformation.0 Level I Developer Copyright © 2010 Informatica Corp . hold the Ctrl key while dragging and dropping.

0 Level I Developer Copyright © 2010 Informatica Corp .Joining and Merging Data 5.21 Lab 5-1 Joining Data • In this lab you will… • • • • Create a Mapping with two data flows Create a homogeneous join using a Source Qualifier Make a transformation reusable Create a heterogeneous join using a Joiner transformation Module 5: Joining and Merging Data 21 of 22 PowerCenter 8.x/9.

0 Level I Developer Copyright © 2010 Informatica Corp .x/9.22 Summary This module showed you how to: • Use pipeline branches in Mappings • Join homogeneous Sources using a Source Qualifier • Define heterogeneous joins using the Joiner transformation • Merge records from multiple places into one record set using the Union transformation • Create and use reusable transformations Module 5: Joining and Merging Data 22 of 22 PowerCenter 8.Joining and Merging Data 5.

x/9.1 Module 6: Lookup Transformations PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .Lookup Transformations 6.

0 Level I Developer Copyright © 2010 Informatica Corp .2 Module Objectives After completing this module you will be able to: • Use Lookup transformations to bring in additional data related to a row Module 6: Lookup Transformations 2 of 12 PowerCenter 8.x/9.Lookup Transformations 6.

3 Lookup Functionality Lookup Data Input value Input value Lookup value(s) Output with Lookup values Lookup Transformation Lookup condition: ITEM_ID = IN_ITEM_ID PRICE <= IN_PRICE Module 6: Lookup Transformations 3 of 12 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.Lookup Transformations 6.

or dynamic. PowerCenter 8. Business Purpose Allows data from external sources such as product codes. may be thought of as a “subquery. to be brought into the row being processed.” May be connected. unconnected. In SQL terms.0 Level I Developer Copyright © 2010 Informatica Corp .. names. etc.x/9.Lookup Transformations 6. dates.4 Lookup Transformation Returns values from a database table or flat file associated with a given input value Ports • Mixed • Check L column for lookup values to be looked up Usage: • Returns related values (if value not found returns null) Module 6: Lookup Transformations 4 of 12 Type Description Passive Allows the inclusion of additional information in the transformation process from an external database or flat file source.

Lookup Transformations 6.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .5 Lookup Condition • Compares one or more input fields with fields in the lookup source • Similar to a SQL “WHERE” clause • The Lookup transformation returns values that match the condition Module 6: Lookup Transformations 5 of 12 PowerCenter 8.

Lookup Transformations 6. caching is always performed. the rows from the cache are included in the stream Module 6: Lookup Transformations 6 of 12 Note Caching for lookup tables is an option. PowerCenter 8. When the lookup references a flat file.x/9. values from the Lookup input port(s) that are part of the lookup condition are compared to the index cache • When a match is found.6 Lookup Cache • Uses index and data cache • Index cache contains values from all ports which are part of the lookup condition • Data cache contains values from all output ports which are not part of the lookup condition • After the cache is loaded.0 Level I Developer Copyright © 2010 Informatica Corp .

Lookup Transformations 6. performance gain because only one.x/9. but stale data may pose a problem Module 6: Lookup Transformations 7 of 12 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp . local SQL SELECT Cache stored on Server hard drive and used next session unless … Reload lookup table each session • Lookup cache persistent • • Re-cache from lookup source • Persistent cache can improve performance.7 Lookup Caching Properties • Lookup caching enabled • • Lookup table cached on Server For relational lookup tables.

0 Level I Developer Copyright © 2010 Informatica Corp . The cache sizes represent upper boundaries on how much of the index and data caches will reside in memory. PowerCenter 8. Name Lookup Data and Index Cache Size The lookup cache is divided into an index cache and a data cache.x/9. Any overflows are written to disk.8 Caching Options Module 6: Lookup Transformations 8 of 12 Attribute Lookup SQL Override Description Overrides default SQL to query the lookup table – only with caching enabled Lookup Cache Directory The location on disk where files associated with the lookup cache are stored.Lookup Transformations 6.

any value. or error. Lookup condition Connection information Displays the condition set in the Condition tab.Lookup Transformations 6.9 Other Lookup Transformation Properties Module 6: Lookup Transformations 9 of 12 Attribute Lookup Table Name Description The name of the table from which the transformation looks up values Lookup Policy on Multiple Match What to do when the transformation finds multiple rows that match the lookup condition: first row.0 Level I Developer Copyright © 2010 Informatica Corp .x/9. Can use exact connection information or the $Source and $Target variables. Source type Tracing level Relational or flat file Detail to include in the session log PowerCenter 8. Specifies the database containing the lookup table. last row.

0 Level I Developer Copyright © 2010 Informatica Corp . Can be set to a comma or a period (full stop).x/9. Decimal Separator Defaults to period (full stop). Defaults to high. Case-Sensitive String Comparison If selected. PowerCenter 8.10 Other Lookup Transformation Properties (Continued) Module 6: Lookup Transformations 10 of 12 Attribute Datetime Format Thousand Separator Description Defaults to MM/DD/YYYY HH24:MI:SS Defaults to no separator. Sorted Input Indicates whether the lookup file data is sorted. If it is.Lookup Transformations 6. then checking this box makes the lookup more efficient. Null Ordering Determines whether null values are considered high or low. the Integration Service differentiates between upper and lower case when matching lookup conditions. Can be set to a comma.

0 Level I Developer Copyright © 2010 Informatica Corp .11 Lab 6-1 – Using the Lookup Transformation • Use a Lookup transformation to import date information • Use a variable port to calculate net and gross profit Module 6: Lookup Transformations 11 of 12 PowerCenter 8.Lookup Transformations 6.x/9.

12 Summary This module showed you how to: • Use Lookup transformations to bring in additional data related to a row Module 6: Lookup Transformations 12 of 12 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .Lookup Transformations 6.x/9.

x/9.1 Module 7: Sorter and Aggregator Transformations PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .Sorter and Aggregator Transformations 7.

x/9.2 Module Objectives After completing this module you will be able to: • Calculate values based on data in a set of records using the Aggregator transformation • Order a set of records based on one or more fields using the Sorter transformation Module 7: Sorter and Aggregator Transformations 2 of 12 PowerCenter 8.Sorter and Aggregator Transformations 7.0 Level I Developer Copyright © 2010 Informatica Corp .

descending.Sorter and Aggregator Transformations 7.3 Sorter Transformation Sort Order Sorts data on one or more ports Sort Keys Ports • Input/Output • Define one or more sort keys • Define sort order for each key Module 7: Sorter and Aggregator Transformations 3 of 12 Type Description Active Sorts incoming data based on one or more key values. or mixed. The Sorter transformation is often more efficient than adding an ORDER BY clause to the Source Qualifier. Business Purpose Use before an Aggregator transformation to improve overall performance.0 Level I Developer Copyright © 2010 Informatica Corp .x/9. PowerCenter 8. Sort order may be ascending.

4 Sorter Transformation Properties Module 7: Sorter and Aggregator Transformations 4 of 12 Property Case Sensitive Description Determines whether the Sorter differentiates between upper and lower case characters. Transformation Scope Transaction: Applies transformation logic to all rows in a transaction. All Input: Applies the transformation logic on all incoming data. treat nulls as lower values than any other.0 Level I Developer Copyright © 2010 Informatica Corp . Other Properties Deal with caching . all ports are considered as part of the sort key. Distinct Treats output rows as distinct. Work Directory A directory where the Integration Service will create temporary files when sorting data. regardless of incoming transaction boundaries.see next slide PowerCenter 8. Null Treated Low If selected.x/9.Sorter and Aggregator Transformations 7. If this is selected.

x/9. the Integration Service fails the session • If the size of the incoming data is greater than the cache size.Sorter and Aggregator Transformations 7. PowerCenter uses temporary files • The location of these files is set using the Work Directory property Module 7: Sorter and Aggregator Transformations 5 of 12 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .5 Sorter Cache • All the incoming data is passed into cache memory before the sort operation is stored in cache memory • Size of the cache memory is set by the Sorter Cache Size property • May be from 1 MB to 4 GB • If the cache size is larger than the available amount of memory.

6 Aggregator Transformation Performs aggregate calculations Ports • Mixed I/O ports allowed • Variable ports allowed • Group By allowed Create aggregate expressions in non-input ports Usage • Standard aggregations Module 7: Sorter and Aggregator Transformations 6 of 12 Type Description Active Calculates aggregates such as sums. across multiple groups of rows. average values.Sorter and Aggregator Transformations 7.x/9. etc. PowerCenter 8. averages. minimums and maximums. summaries by period.0 Level I Developer Copyright © 2010 Informatica Corp . Business Purpose Enables calculation of gross profits or margins.

7 Aggregator Properties Module 7: Sorter and Aggregator Transformations 7 of 12 Attribute Cache Directory Description 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.0 Level I Developer Copyright © 2010 Informatica Corp . Aggregator Data Cache Size Data cache size for the transformation. PowerCenter 8. Default size is set to Auto. Default cache size is set to Auto. Use only if the mapping passes sorted data to the Aggregator.x/9. Transformation Scope Transaction: applies transformation logic to all rows in a transaction.Sorter and Aggregator Transformations 7. All input: applies the transformation logic on all incoming data. Aggregator Index Cache Size Index cache size for the transformation.

x/9. overflow is written to disk • No rows are returned until all rows are aggregated • Checking the “sorted input” attribute bypasses caching.Sorter and Aggregator Transformations 7.8 Aggregator Cache • Two types: Index and Data • Index contains group by port values • Data cache contains all port values. as well as the sort operation that occurs implicitly in an Aggregator PowerCenter 8. including variable and connected output ports • • • • Non “group by” input ports used in non-aggregate output expressions Non “group by” input/output ports Local variable ports Ports containing aggregate function (multiply by three) • One output row is returned for each unique occurrence of the “group by” ports” Module 7: Sorter and Aggregator Transformations 8 of 12 Key Points • If there is not enough memory specified in the index and data cache properties.0 Level I Developer Copyright © 2010 Informatica Corp .

Sorter and Aggregator Transformations 7.x/9. condition) Module 7: Sorter and Aggregator Transformations 9 of 12 PowerCenter 8.9 Aggregate Expressions Aggregate functions AVG COUNT FIRST LAST MAX MEDIAN MIN PERCENTILE STDDEV SUM VARIANCE Conditional Aggregate expressions are supported: Conditional SUM format: SUM(value.0 Level I Developer Copyright © 2010 Informatica Corp .

Sorter and Aggregator Transformations 7.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.10 Data Concatenation • Determines whether some ports (data flow arrows) can bypass a transformation • Works only if: • Combining branches of the same source pipeline • AND neither branch contains an active transformation ALLOWED DISALLOWED Passive T T T Active T Module 7: Sorter and Aggregator Transformations 10 of 12 PowerCenter 8.

0 Level I Developer Copyright © 2010 Informatica Corp .x/9.Sorter and Aggregator Transformations 7.11 Lab 7-1 – Using Aggregators and Sorters • In this lab you will… • Split a pipeline into two branches to feed two Aggregator transformations and write out data to two separate tables • Use Sorter transformations to improve the efficiency of the Mapping Module 7: Sorter and Aggregator Transformations 11 of 12 PowerCenter 8.

12 Summary This module showed you how to: • Calculate values based on data in a set of records using the Aggregator transformation • Order a set of records based on one or more fields using the Sorter transformation Module 7: Sorter and Aggregator Transformations 12 of 12 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .Sorter and Aggregator Transformations 7.x/9.

x/9.Using the Debugger 8.1 Module 8: Using the Debugger PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

x/9.0 Level I Developer Copyright © 2010 Informatica Corp .2 Module Objectives After completing this module you will be able to: • Use the Debug wizard and toolbar to debug a mapping Module 8: Using the Debugger 2 of 9 PowerCenter 8.Using the Debugger 8.

3 Debugger • The Debugger is a wizard-driven tool that runs a test session • Allows you to • Follow a record across a mapping from transformation to transformation • Set and modify breakpoints within a mapping • Change data and variable values • The Debugger only works with valid mappings • Use the Designer Output Window to determine why a mapping is not valid Module 8: Using the Debugger 3 of 9 PowerCenter 8.Using the Debugger 8.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.

Using the Debugger

8.4

Debugger User Interface
Debugger Toolbar

Current Source Qualifier Indicator

Output Window – Debugger or Session Log

Target Instance Window

Transformation Instance Data Window

Module 8: Using the Debugger

4 of 9

PowerCenter 8.x/9.0 Level I Developer

Copyright © 2010 Informatica Corp

Using the Debugger

8.5

Using the Debugger
1. Press F9 to start the Debugger
• Stops when the Integration Service is ready

2. Choose an existing session or define a one-time debug session
• Options:
• Load or discard target data • Save debug environment for later use

3. Monitor the Debugger windows
• Output window – view Debug or Session log • Transformation Instance Data window – view transformation data • Target Instance window – view target data

Module 8: Using the Debugger

5 of 9

PowerCenter 8.x/9.0 Level I Developer

Copyright © 2010 Informatica Corp

Using the Debugger

8.6

Using the Debugger Continued
4. Move through the session
• Menu options include
• Next instance – examine a row as it progresses through the transformations in the mapping • Step to instance– select a transformation and ‘step’ through the rows that flow through it • Show current instance • Continue • Break now

5. Modify data and breakpoints
• When the Debugger pauses you can:
• Change data • Change variable values • Add or change breakpoints

Module 8: Using the Debugger

6 of 9

PowerCenter 8.x/9.0 Level I Developer

Copyright © 2010 Informatica Corp

Using the Debugger

8.7

Set Breakpoints
1. Edit breakpoint 2. Choose global or specific transformation 3. Choose to break on data condition or error – optionally skip rows 4. Add data conditions for breakpoint 5. Add breakpoint(s)

6. Continue (to next breakpoint)
Module 8: Using the Debugger

7 of 9

PowerCenter 8.x/9.0 Level I Developer

Copyright © 2010 Informatica Corp

Using the Debugger

8.8

Lab 8-1 – Using the Debug Wizard
• In this lab you will…
• Use the Debug Wizard • Use the Debug toolbar

Module 8: Using the Debugger

8 of 9

PowerCenter 8.x/9.0 Level I Developer

Copyright © 2010 Informatica Corp

x/9.Using the Debugger 8.9 Summary This module showed you how to: • Use the Debug wizard and toolbar to debug a mapping Module 8: Using the Debugger 9 of 9 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

0 Level I Developer Copyright © 2010 Informatica Corp .Using the Debugger 8.x/9.10 Module 8: Using the Debugger 10 of 9 PowerCenter 8.

Updating Target Tables 9.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .1 Module 9: Updating Target Tables PowerCenter 8.

delete) Module 9: Updating Target Tables 2 of 7 PowerCenter 8.x/9.Updating Target Tables 9.0 Level I Developer Copyright © 2010 Informatica Corp .2 Module Objectives After completing this module you will be able to: • Use an Update Strategy transformation to determine how the Target should handle records (insert. update.

update. updated. based on one or more criteria.x/9. or deleted.Updating Target Tables 9.0 Level I Developer Copyright © 2010 Informatica Corp . PowerCenter 8. Each row can be “tagged” with one of the tags shown on the following slide. or reject) based on an expression Ports • All input / output • Specify the Update Strategy Expression – IIF or DECODE logic determines how to handle the record Example • Updating Slowly Changing Dimensions Module 9: Updating Target Tables 3 of 7 Type Description Active “Tags” a row with the appropriate DML (Data Manipulation Language) for PowerCenter’s writer to apply to the relational target. may need to be inserted. Business Purpose A target table may require historical information dealing with existing entries. delete. The Update Strategy transformation meets this requirement. Rows written to a target table.3 Update Strategy Transformation Specifies how each row updates target tables (insert.

Updating Target Tables 9. the table definition in the mapping must have a key identified. and subsequently placed in the appropriate “bad file”. If the “Forward Rejected Rows” attribute is checked (default). Otherwise. the session created from the mapping will fail. If the attribute is unchecked. then the reject rows will be skipped. no action to be taken on the target table Module 9: Updating Target Tables 4 of 7 Note For the row tags DD_DELETE and DD_UPDATE. PowerCenter 8.x/9.0 Level I Developer Copyright © 2010 Informatica Corp . then rows tagged with DD_REJECT will be passed on to the next transformation or the Target.4 Update Strategy Flags • The Update Strategy transformation sets one of the following flags for each row: • • • • DD_INSERT – tags the row for insertion to the target table DD_UPDATE – tags the row for updating in the target table DD_DELETE – tags the row for deletion from the target table DD_REJECT – tags the row for rejection.

In some cases there may be a performance benefit to splitting a mapping with updates and inserts into two mappings and sessions.x/9.0 Level I Developer Copyright © 2010 Informatica Corp . DD_INSERT. DD_REJECT) ƒ Expression is evaluated for each row ƒ Rows are tagged according to the logic of the expression ƒ Appropriate SQL is submitted to the target database: insert.5 Update Strategy Expression Example IIF (high_value_client_score > 75. one performing the inserts and one the updates. PowerCenter 8.Updating Target Tables 9. Rejected rows may be forwarded through the mapping Module 9: Updating Target Tables 5 of 7 Performance Considerations Update Strategy performance can vary depending on the number of updates and inserts. delete or update ƒ DD_REJECT means the row will not have SQL written for it.

Updating Target Tables

9.6

Lab 9-1: Updating Target Tables
• In this lab you will…
• Use a single Source definition to read two files and combine their data in a single data stream • Remove duplicate rows • Create logic that
• Rejects records if the incoming CUSTOMER_ID is missing • Inserts the record if the customer does not already exist in ODS_CUSTOMERS • Updates the record if the customer already exists in ODS_CUSTOMERS

Module 9: Updating Target Tables

6 of 7

PowerCenter 8.x/9.0 Level I Developer

Copyright © 2010 Informatica Corp

Updating Target Tables

9.7

Summary
This module showed you how to: • Use an Update Strategy transformation to determine how the Target should handle records (insert, update, delete)

Module 9: Updating Target Tables

7 of 7

PowerCenter 8.x/9.0 Level I Developer

Copyright © 2010 Informatica Corp

Updating Target Tables

9.8

Module 9: Updating Target Tables

8 of 7

PowerCenter 8.x/9.0 Level I Developer

Copyright © 2010 Informatica Corp

Mapping Techniques

10.1

Module 10: Mapping Techniques

PowerCenter 8.x/9.0 Level I Developer

Copyright © 2010 Informatica Corp

Mapping Techniques

10.2

Module Objectives
After completing this module you will be able to: • Set and use system and Mapping variables and parameters • Use unconnected Lookup transformations to provide values on an as-needed basis • Use a Router transformation to divide a single set of records into multiple sets of records

Module 10: Mapping Techniques

2 of 24

PowerCenter 8.x/9.0 Level I Developer

Copyright © 2010 Informatica Corp

3 System Variables SYSDATE ƒ Provides current datetime on the PowerCenter Server machine • Not a static value SESSSTARTTIME ƒ Returns the system date value on the PowerCenter Server • Used with any function that accepts transformation date/time datatypes • Not to be used in a SQL override • Has a constant value $$$SessStartTime ƒ Returns the system date value as a string. Business Purpose System variables provide consistency to program execution. Uses system clock on machine hosting PowerCenter Server • Format of the string is database type dependent • Used in SQL override • Has a constant value Module 10: Mapping Techniques 3 of 24 Description System variables hold information derived from the system.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.Mapping Techniques 10. PowerCenter 8. The user cannot control the content of the variable but can reference the information contained within the variable.

0 Level I Developer Copyright © 2010 Informatica Corp .4 Example • The developer needs to set the value of a port to indicate when the record was last updated by PowerCenter • Create a port called LAST_UPDATED and set its value to the expression SYSDATE Module 10: Mapping Techniques 4 of 24 PowerCenter 8.x/9.Mapping Techniques 10.

x/9. specified for the session task • Provide increased development flexibility • Can be used in pre and post-SQL Module 10: Mapping Techniques 5 of 24 Description A Mapping can utilize parameters and variables to store information during execution. Both can be accessed from anywhere in the Mapping. while variables can change (vary). 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 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .Mapping Techniques 10.5 Mapping Parameters and Variables • Represent declared values: • Variables can change in value during run-time • Parameters remain constant during run-time • Apply to all transformations within a Mapping • Declared in Mappings menu • Format is $$VariableName or $$ParameterName • Value is initialized by the specification that defines it • Parameter values can be set to a different value in a parameter file. 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.

If this is true and the parameter type is not String.x/9. and Min. Default is false. Aggregation Type IsExpVar PowerCenter 8. In a session with multiple partitions. If true. IsExpVar determines how the Integration Service expands the parameter in an expression string. the IS fails the session. The PowerCenter Server uses the aggregation type of a mapping variable to determine the final current value of the mapping variable. Max. the PowerCenter Server combines the variable value from each partition and saves the final value into the repository. Aggregation types include Count (for integer datatype). 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. the IS expands the parameter after parsing the expression.0 Level I Developer Copyright © 2010 Informatica Corp . A parameter or variable’s scope is the object in which it was created.Mapping Techniques 10.6 Declaring Mapping Parameters and Variables Mappings – Declare Parameters and Variables menu option Set aggregation type See Note Set datatype User-defined ($$name) Set optional initial value Module 10: Mapping Techniques 6 of 24 Scope Parameters and variables can be used only inside the object in which they are created.

Mapping Techniques 10.x/9.7 Using Mapping Parameters and Variables Use parameters or variables in expression 7 of 24 Module 10: Mapping Techniques PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

the values of variables are saved to the repository.x/9.value) • Sets the variable to the larger of its current value and the value passed to the function • SETMINVARIABLE($$Variable.8 Functions to Set Mapping Variables • SETVARIABLE($$Variable. the final value for a variable with an Aggregate type of MIN will be whichever is smaller. The SetVariable function writes the final value of a variable to the repository based on the Aggregation Type selected when the variable was defined. subtract 1. the current value or the initial value.0 Level I Developer Copyright © 2010 Informatica Corp .. Similarly. $$ParamName or $$VariableName).Mapping Techniques 10. The final value written to the repository for a variable that has an Aggregate type of MAX will be whichever is greater.value) • Sets the variable to the smaller of its current value and the value passed to the function Module 10: Mapping Techniques 8 of 24 Variable Persistence At the end of a successful session. the current value or the initial value.value) • Sets the variable to the value specified • Executes only for rows marked Insert or Update • SETCOUNTVARIABLE($$Variable) • Increments a counter variable • If the row is marked for Insert. PowerCenter 8. if it is marked for Delete. otherwise. do not change • SETMAXVARIABLE($$Variable.e. Naming Convention User-defined variable and parameter names always begin with $$ (i. add 1.

Parameter file 2.0 Level I Developer Copyright © 2010 Informatica Corp .9 Parameters & Variables – Initialization Priority Parameters 1.Mapping Techniques 10. Declared initial value 3. Default value Module 10: Mapping Techniques 9 of 24 Parameter File A file that holds information about definitions of variables and parameters Values for variables that were saved in the Repository after successful completion of a Session Repository Saved Value Declared Initial Value The initial value. Repository saved value 3. Parameter file 2. Declared initial value 4.x/9. as set by the user when creating the variable or parameter Set by the system Default Value PowerCenter 8. Default value Variables 1.

using a variable defined in the mapping and has its value set in a parameter file Ensure that everyone uses the same value in expressions.x/9. Create two parameters that represent “Yes” and “No.0 Level I Developer Copyright © 2010 Informatica Corp . track when a mapping was last executed using a mapping variable Potential Value 100 'US' Param Name or Var Param Var $$MAX_NUM_DAYS_OPEN $$REG_PROC_LOCATION 'Y' 'N' Param Param $$YES_1_CHAR $$NO_1_CHAR SESSSTARTTIME Variable $$LAST_RUN_DT Module 10: Mapping Techniques 10 of 24 PowerCenter 8. To perform an incremental extraction.10 Examples of Variable/Parameter Usage Reason/Goal Expression that determines whether a support case has been open greater than 100 days Set the value of the processing center where the session is executed.Mapping Techniques 10.” Have all mappings use these values via a parameter file.

Business Purpose A source table may have a small percentage of records with incomplete data.11 Unconnected Lookup ƒ ƒ ƒ ƒ Commonly used when a Lookup not needed for every record No links from/to other transformations Lookup data is called at the point in the Mapping that needs it Lookup function can be set within any transformation that supports expressions Unconnected Lookup Function in the Expression calls the Unconnected Lookup Module 10: Mapping Techniques 11 of 24 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.Mapping Techniques 10.0 Level I Developer Copyright © 2010 Informatica Corp .x/9. on an as-needed basis. These “holes” in the data can be filled by performing a lookup to another table or tables. PowerCenter 8.

Mapping Techniques 10.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.12 Unconnected Lookup Example • A small percentage of records are missing the CUST_ID field Module 10: Mapping Techniques 12 of 24 PowerCenter 8.

customer_id) Lookup function ƒ Condition is evaluated for each row but Lookup function is called only if condition is satisfied Module 10: Mapping Techniques 13 of 24 Key Points • Use the Lookup function (:lkp.Mapping Techniques 10. 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.13 Calling the Unconnected Lookup ƒ Use Lookup function within a conditional statement Condition Row keys (passed to Lookup) IIF ( ISNULL(customer_id). but the session may fail at runtime PowerCenter 8.x/9.MYLOOKUP(order_no).:lkp.0 Level I Developer Copyright © 2010 Informatica Corp .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.

each representing one item in an order. The customer_id can be derived from the value of order_no.Mapping Techniques 10.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .14 Unconnected Lookup Advantages ƒ Data lookup is performed only for those rows which require it. Substantial performance can be gained EXAMPLE: A Mapping will process 500.000 rows.MYLOOKUP(order_no). customer_id) Lookup Condition (true for 2 percent of all rows) (called only when condition is true) Net savings = 490. IIF ( ISNULL(customer_id). For two percent of those orders (10. :lkp.000 lookups Module 10: Mapping Techniques 14 of 24 PowerCenter 8.000) the customer_id value is NULL.

x/9. or expression that calls lookup is invalid. Module 10: Mapping Techniques 15 of 24 PowerCenter 8.Mapping Techniques 10.0 Level I Developer Copyright © 2010 Informatica Corp .15 Unconnected Lookup Functionality One lookup port value may be returned for each lookup Must select a Return port in the Ports tab.

lookupname • Data from several input ports may be passed to the Lookup transformation but only one port may be returned • The port to be returned is designated by the Lookup transformation’s R (return) port • If a port is not selected as the R port.x/9.Mapping Techniques 10.16 Key Points • An unconnected lookup can improve performance if the lookup table is static • Use the lookup with a conditional statement • The condition is evaluated only for those rows where the condition evaluates to TRUE • The transformation is called using the expression :lkp. the mapping will not be invalidated but the session will fail at runtime Module 10: Mapping Techniques 16 of 24 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

by checking the Return (R) port option for the output port that provides the return value Only executed when the lookup function is called Less visible.Mapping Techniques 10.x/9. as the lookup is called from an expression within another transformation Default values are ignored 17 of 24 Module 10: Mapping Techniques PowerCenter 8. shows where the lookup values are used Default values are used Separate from the mapping data flow Returns one value .17 Connected versus Unconnected Lookups CONNECTED LOOKUP UNCONNECTED LOOKUP Part of the mapping data flow Returns multiple values (by linking output ports to another transformation) Executed for every record passing through the transformation More visible.0 Level I Developer Copyright © 2010 Informatica Corp .

0 Level I Developer Copyright © 2010 Informatica Corp .18 Joins versus Lookups Source Qualifier Join Advantages Can join any number of tables Full functionality of standard SQL available May reduce volume of data on network Disadvantages Can only join homogeneous relational tables Can affect performance on the source database Advantages Can join heterogeneous sources Can join non-relational sources Can join partially transformed data Disadvantages Can only join 2 input data streams per joiner Only supports equijoin SQL override supported Does not support “OR” conditions Can be unconnected & invoked as needed Disadvantages Cannot output multiple matches Unconnected can only have 1 return value “OR” conditions not supported Joiner Advantages Lookup Can re-use cache across session runs Can re-use cache w/in mapping Can modify cache dynamically Can choose to cache or not to cache Can query relational table or flat file Inequality comparisons are allowed Module 10: Mapping Techniques 18 of 24 PowerCenter 8.Mapping Techniques 10.x/9.

Business Purpose Allows you to write records from a single source into multiple targets based on user-defined criteria. PowerCenter 8. A Router transformation has one input group. each of which has its own filter condition.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .Mapping Techniques 10.19 Router Transformation Sends rows to different destinations based on filter conditions Ports • All input/output • Specify filter conditions for each Group Usage • Link source data in one pass to multiple filter conditions Module 10: Mapping Techniques 19 of 24 Type Description Active Passes row data to different groups based on filter-like conditions. and one or more output groups.

Mapping Techniques 10.20 Router Groups ƒ Input group (always one) ƒ User-defined output groups  Each group has one condition  ALL group conditions are evaluated for each row  One row can pass multiple conditions ƒ Unlinked Group outputs are ignored ƒ Default group (always one) capture rows that fail all Group conditions Module 10: Mapping Techniques 20 of 24 Performance Considerations A Router transformation is functionally equivalent to several Filter transformations in parallel. once for each condition. because a row is read once into the input group but evaluated multiple times. PowerCenter 8. performance can be substantially better.0 Level I Developer Copyright © 2010 Informatica Corp . However.x/9.

Note that multiple target objects can be instances of the same target table. the record for a salesperson hired less than 90 days ago will be routed to both STG_EMPLOYEES_NEW and STG_EMPLOYEES_SALES. you must ensure that their filter conditions are mutually exclusive.x/9. PowerCenter 8.Mapping Techniques 10.0 Level I Developer Copyright © 2010 Informatica Corp . If you wish to prevent single records from being routed to multiple Targets. only one INSERT statement will be generated per record. In the example above. you would prefix the conditions for the positionbased tables with “DATE HIRED >= 90 DAYS AGO AND”. If this is the case.21 Router Functionality DATE_HIRED < 90 days ago POSITION_CODE  SALES Note: New employees will be routed to two Targets POSITION_CODE = SALES Module 10: Mapping Techniques 21 of 24 Note In the diagram above.

x/9. Sub-Prime. and city into High-Income. Postal code.0 Level I Developer Copyright © 2010 Informatica Corp .CSV file so that the data can easily be loaded into a spreadsheet Module 10: Mapping Techniques 22 of 24 PowerCenter 8.Mapping Techniques 10.22 Lab 10-1 – Filling In Missing Data • In this lab you will… • Use a Unconnected Lookup to attempt to find in what city customers purchased their cars • Use a Router to categorize customers based on income level. and Uncategorized categories • Override the relational writer to write out to a .

x/9.23 Lab 10-2 – Load Employee Staging Table • In this lab you will… • Use a persistent Repository variable to hold and increment the latest employee identification number • Further leverage the reusable transformation re_exp_Format_Person Module 10: Mapping Techniques 23 of 24 PowerCenter 8.Mapping Techniques 10.0 Level I Developer Copyright © 2010 Informatica Corp .

Mapping Techniques 10.24 Summary This module showed you how to: • Set and use system and Mapping variables and parameters • Use unconnected Lookup transformations to provide values on an as-needed basis • Use a Router transformation to divide a single set of records into multiple sets of records Module 10: Mapping Techniques 24 of 24 PowerCenter 8.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .

Mapplets and Worklets 11.1 Module 11: Mapplets and Worklets PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.

0 Level I Developer Copyright © 2010 Informatica Corp .Mapplets and Worklets 11.2 Module Objectives After completing this module you will be able to: • Describe Mapplets • Use a Mapplet in a mapping • Describe Worklets Module 11: Mapplets and Worklets 2 of 18 PowerCenter 8.x/9.

they can also simplify complex mapping maintenance. PowerCenter 8.x/9. A Mapplet must pass data out to the Mapping via a Mapplet Output transformation.Mapplets and Worklets 11. These instances inherit all changes to the parent Mapplet.0 Level I Developer Copyright © 2010 Informatica Corp . Note Mapplets are reusable by nature – a Mapping uses an instance of a Mapplet. A Mapplet receives input data from either an internal Source or the Mapping pipeline that calls the Mapping. which may affect the behavior of the Mappings that use the instances.3 Mapplets • A Mapplet contains transformations and may be embedded into a Mapping Module 11: Mapplets and Worklets 3 of 18 Type Description Passive or Active Mapplets combine multiple mapping objects for reusability.

in many Mappings.4 Mapplet Designer Mapplet Input & Output transformations (pass data from or to mapping) Mapplet Designer Tool Module 11: Mapplets and Worklets 4 of 18 Example A business. PowerCenter 8. This functionality is used in several types of feeds.Mapplets and Worklets 11. as part of its daily sales.0 Level I Developer Copyright © 2010 Informatica Corp . so the Mapplet shown here was created to provide this functionality. identically. needs to apply discounts. performing a number of lookups and aggregating the sales values.x/9.

Mapplets and Worklets 11.x/9.5 Mapplet Input Transformation Passes data from a Mapping into a Mapplet Passive Ports • Output ports only Usage • Only those ports connected from an Input transformation to another transformation will display in the resulting Mapplet Transformation Transformation • Connecting the same port to more than one transformation is disallowed • Pass to an Expression transformation first Module 11: Mapplets and Worklets 5 of 18 Type Passive Description Acts as an input to a Mapplet PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

6 Mapplet Input Transformation Example • The Mapplet Input transformation receives sales transactions for processing Module 11: Mapplets and Worklets 6 of 18 PowerCenter 8.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .Mapplets and Worklets 11.

x/9.0 Level I Developer Copyright © 2010 Informatica Corp .7 Mapplet Output Transformation Passes data from a Mapplet into a Mapping Passive Ports • Input ports only Usage • Only those ports connected to an Output transformation (from another transformation) will display in the resulting Mapplet One (or more) Mapplet Output transformations are required in every Mapplet Module 11: Mapplets and Worklets • 7 of 18 Type Passive Description Acts as an output from a Mapplet PowerCenter 8.Mapplets and Worklets 11.

0 Level I Developer Copyright © 2010 Informatica Corp .x/9.Mapplets and Worklets 11.8 Mapplet Output Transformation Example • The Mapplet Output transformation returns the processed transactions to the Mapping Module 11: Mapplets and Worklets 8 of 18 PowerCenter 8.

x/9.Mapplets and Worklets 11.0 Level I Developer Copyright © 2010 Informatica Corp .9 Mapplet with Multiple Output Groups Can output to multiple instances of the same target table Module 11: Mapplets and Worklets 9 of 18 PowerCenter 8.

the mapping is valid because a Router can have unconnected output groups. PowerCenter 8. If that is not permitted.0 Level I Developer Copyright © 2010 Informatica Corp .x/9. an unconnected output group could result in a transformation having no output connections. then the mapping will be invalid.Mapplets and Worklets 11. • But if the Mapplet outputs are fed by a Router. For example: • If the Mapplet outputs are fed by an Expression transformation. the mapping is invalid because an Expression requires a connected output.10 Unmapped Mapplet Output Groups Module 11: Mapplets and Worklets 10 of 18 Warning When the Mapplet is expanded at runtime.

you cannot use a Mapplet inside another Mapplet.0 Level I Developer Copyright © 2010 Informatica Corp . PowerCenter 8.Mapplets and Worklets 11.x/9.11 Example: Data Sources Defined Inside Mapplet Mapping Sources define source data within Mapplet Mapplet Mapplet Output transformation Note: Mapplet must come first in mapping Module 11: Mapplets and Worklets 11 of 18 Note Mapplets cannot be nested – that is.

0 Level I Developer Copyright © 2010 Informatica Corp .Mapplets and Worklets 11.12 Passive and Active Mapplets Passive Mapplet Multiple passive Mapplets can populate the same target instance Active and passive Mapplets cannot populate the same target instance contains only passive transformations Active Mapplet Multiple active Mapplets cannot populate the same target instance contains one or more active transformations Module 11: Mapplets and Worklets 12 of 18 PowerCenter 8.x/9.

0 Level I Developer Copyright © 2010 Informatica Corp .13 Mapplet Parameters and Variables • Similar to Mapping parameters and variables • Defined by using the menu option Mapplets Æ Parameters and Variables • A parameter or variable defined in a Mapplet is not visible in any parent mapping • A parameter or variable defined in a Mapping is not visible in any child Mapplet Module 11: Mapplets and Worklets 13 of 18 PowerCenter 8.x/9.Mapplets and Worklets 11.

Mapplets and Worklets 11.x/9.14 Lab 11-1 – Creating a Mapplet • In this lab you will… • Create a Mapplet and use it in a Mapping Module 11: Mapplets and Worklets 14 of 18 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

tasks.0 Level I Developer Copyright © 2010 Informatica Corp .15 Worklet • • • • An object representing a set or grouping of Tasks Can contain any Task available in the Workflow Manager Worklets expand and execute inside a Workflow A Workflow which contains a Worklet is called the “parent Workflow” • Worklets CAN be nested (unlike Mapplets) • Reusable Worklets – create in the Worklet Designer • Non-reusable Worklets – create in the Workflow Designer Module 11: Mapplets and Worklets 15 of 18 Description Worklets are optional processing objects inside Workflows. They can be created directly in a Workflow (nonreusable) or in the Worklet Designer (reusable) Business Purpose A Workflow may contain dozens of tasks.x/9. The Workflow can run as-is. run in the appropriate operational order. from start to finish. or the developer can place natural groupings into Worklets. executing task-by-task. During Workflow design they will develop naturally in “groupings” of meaningfully-related tasks. A Worklet’s relationship to a Workflow is like that of a Mapplet to a Mapping.Mapplets and Worklets 11. PowerCenter 8. or functionally related set of. They contain PowerCenter tasks that represent a particular grouping of.

select Worklets | Create Worklets Node Module 11: Mapplets and Worklets 16 of 18 PowerCenter 8.16 Creating Worklets ƒ In the Worklet Designer.Mapplets and Worklets 11.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .

x/9.Mapplets and Worklets 11.17 Using a Worklet in a Workflow Worklet used in a Workflow Module 11: Mapplets and Worklets 17 of 18 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

0 Level I Developer Copyright © 2010 Informatica Corp .Mapplets and Worklets 11.18 Summary This module showed you how to: • Describe Mapplets • Use a Mapplet in a mapping • Describe Worklets Module 11: Mapplets and Worklets 18 of 18 PowerCenter 8.x/9.

Controlling Workflows 12.1 Module 12: Controlling Workflows PowerCenter 8.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .

0 Level I Developer Copyright © 2010 Informatica Corp .Controlling Workflows 12. Command • Explain the purpose of the pmcmd utility • Schedule workflows to run automatically Module 12: Controlling Workflows 2 of 30 PowerCenter 8. Event Raise.x/9. Event Wait.2 Module Objectives After completing this module you will be able to: • Set and use workflow variables • Use link conditions and Decision tasks to control the execution of a workflow • Use other workflow tasks: Email.

3 Link Conditions • You can set conditions on workflow links: • • If the link condition is True.x/9. PowerCenter 8. • You can use workflow variables in the condition (next slide) Note: the words SUCCEEDED and FAILED are reserved for use in expressions Module 12: Controlling Workflows 3 of 30 Reserved Words In addition to SUCCEEDED and FAILED. STOPPED and ABORTED are reserved for use in link conditions. STARTED. the next task is executed If the link condition is False. Consult the Workflow Administration guide for valid values for all Predefined variables. right-click a link and enter an expression that evaluates to True or false.0 Level I Developer Copyright © 2010 Informatica Corp . NOT STARTED. the next task is not executed • To set a condition.Controlling Workflows 12. the words DISABLED.

x/9.0 Level I Developer Copyright © 2010 Informatica Corp .4 Incoming Links • OR – run the task as soon as any link condition is TRUE • AND – run the task when all link conditions are TRUE Module 12: Controlling Workflows 4 of 30 PowerCenter 8.Controlling Workflows 12.

x/9. PowerCenter 8. Workflow variables convey that information from one task to another.0 Level I Developer Copyright © 2010 Informatica Corp .5 Variables Used in a Workflow Pre-defined variables User-defined variables (next slides) Task-specific variables Built-in system variables 5 of 30 Module 12: Controlling Workflows Types Workflow variables come in two types: user-defined and pre-defined Business Purpose A workflow can contain multiple tasks and multiple pipelines. One or more tasks or pipelines may be dependent on the status of previous tasks.Controlling Workflows 12.

0 Level I Developer Copyright © 2010 Informatica Corp .x/9.6 Declaring User-Defined Workflow Variables • To declare user-defined workflow variables • Click Workflows Æ Edit and select the Variables tab • Variables can persist across sessions in a workflow • The value is saved in the repository Module 12: Controlling Workflows 6 of 30 PowerCenter 8.Controlling Workflows 12.

and Timer tasks and link conditions Task-Specific Variables Module 12: Controlling Workflows 7 of 30 Note Predefined workflow variables are discussed in more detail in the Workflow Administration Guide PowerCenter 8. e.x/9.7 Pre-defined Workflow Variables • Include system variables and task-specific variables • System variables (SYSDATE and WORKFLOWSTARTTIME) can be used for calculating variable dates and times..g.Controlling Workflows 12. in Assignment task link conditions • Task-specific variables are available in Decision. Assignment.0 Level I Developer Copyright © 2010 Informatica Corp .

0 Level I Developer Copyright © 2010 Informatica Corp . SrcFailedRows.Controlling Workflows 12.x/9.8 Pre-defined Workflow Variable Example • Session 2 depends on success of Session 1 • Defined as session status = successful and failed rows = 0 • Code the link from Session 1 to Session 2 so that Session 2 will not run unless all criteria are true • Use the task-specific workflow variables Status. and TgtFailedRows in the Link condition expression • Session 4 should not run if Session 3 takes more than one hour • Test the system variable WORKFLOWSTARTTIME in the Link condition expression Session 1 Start Session 3 Session 4 Session 2 Module 12: Controlling Workflows 8 of 30 PowerCenter 8.

0 Level I Developer Copyright © 2010 Informatica Corp . An Assignment task can do certain calculations to establish the value for a workflow variable.x/9. as testing criteria to determine if or when other workflow tasks/pipelines should be run. Business Purpose Running a workflow task may depend on the results of other tasks or calculations in the workflow.Controlling Workflows 12.9 Assignment Task – Setting User-Defined Workflow Variables Assigns a value to a user-defined workflow variable Note: The variable must have been declared in the workflow Variables tab General Tab Expressions Tab Module 12: Controlling Workflows 9 of 30 Description Can establish the value of a Workflow Variable. This value may determine whether other tasks or pipelines are run. PowerCenter 8. whose value can be used at a later point in the workflow.

x/9.10 Assignment Task Example • Session 4 should run at least one hour after Session 3 completes • The Assignment Task is coded to set a time that the Timer will wait for • To prevent the Assignment task from running until after Session 2 completes.0 Level I Developer Copyright © 2010 Informatica Corp . use a Link Condition Module 12: Controlling Workflows 10 of 30 PowerCenter 8.Controlling Workflows 12.

workflows have multiple paths.Controlling Workflows 12.x/9. depending on the business-defined rules and operational rules of processing. depending on whether the set criteria is true or false Business Purpose Commonly.11 Decision Task ƒ Tests for a condition during the workflow and sets a flag based on the condition ƒ Use a link condition (or a Control task) downstream to test the flag and control execution flow ƒ Can use workflow variables in condition Module 12: Controlling Workflows 11 of 30 Description Decision tasks enable workflow designers to set criteria by which the workflow will or will not proceed to the next set of tasks. Others are pipelines of tasks that should only run if the previous tasks are successful.0 Level I Developer Copyright © 2010 Informatica Corp . Still others should be run only if those tasks are not successful. and subsequently tested for a True or False condition PowerCenter 8. Some are simply concurrent tasks. What determines the success or failure of a task or group of tasks is user-defined. The criteria are set as the decision condition in a Decision task.

12 Decision Task Example • If Session 3 is successful. run Session 4 • If Session 3 fails. send an email to the system administrator Module 12: Controlling Workflows 12 of 30 PowerCenter 8.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .Controlling Workflows 12.

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. a subject line. the status of tasks (or combinations of tasks) within it.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.Controlling Workflows 12. Users can define email addresses. the impact of the Integration Service sending the emails is minimal PowerCenter 8.13 Email Task ƒ Sends an email within a workflow Note: emails can also be sent post-session in a Session task ƒ Can be used with a link condition to notify success or failure of prior tasks Module 12: Controlling Workflows 13 of 30 Description Email tasks enable PowerCenter to send email messages at various points in a workflow. and the email message text. or various metadata results of a session Performance Considerations The PowerCenter domain must be configured to use a running. Business Purpose Various business and operational staff may need to be notified of the progress of a workflow. configured email server. However.

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.0 Level I Developer Copyright © 2010 Informatica Corp . It always works in concert with an Event Raise task.x/9. 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.Controlling Workflows 12. PowerCenter 8. Note that the Workflow must be running in order to recognize a pre-defined event.14 Event Wait Task ƒ ƒ Pauses processing of the pipeline until a specified event occurs Events can be: ƒ ƒ Pre-defined – file watch User-defined – created by an Event Raise task elsewhere in the workflow Module 12: Controlling Workflows 14 of 30 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.

0 Level I Developer Copyright © 2010 Informatica Corp .15 Pre-defined Event Example • Session 2 cannot run until the daily sales report file has been placed on the server • The Event Wait task is configured to watch for the file to appear • Session 2 does not run until the Event Wait task finds the file Module 12: Controlling Workflows 15 of 30 PowerCenter 8.x/9.Controlling Workflows 12.

Controlling Workflows 12.x/9.16 Event Wait Task (cont’d) Events Tab Specify either a pre-defined or user-defined event User-defined events must be declared in the workflow Events tab Module 12: Controlling Workflows 16 of 30 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

PowerCenter 8. They send a signal to an Event Wait task that a set of pre-defined events has occurred.x/9.17 Event Raise Task ƒ ƒ ƒ Sets the location of a user-defined event in the workflow User-defined events are triggered when the PowerCenter Server executes the Event Raise Task User-defined events must be declared in the workflow Events tab Used with the Event Wait Task Module 12: Controlling Workflows 17 of 30 Description Event Raise tasks are always used in conjunction with user-defined Event Wait tasks. along the pipeline from the Start task to the Event Raise task.0 Level I Developer Copyright © 2010 Informatica Corp .Controlling Workflows 12. Business Purpose This task allows signals to be passed from one spot in the workflow to another that a particular series of predetermined events has occurred.

the developer: 1. PowerCenter 8.x/9. Includes an Event Raise task at a suitable point in the workflow.g. Includes an Event Wait task at a suitable point in the workflow. after a parallel pipeline has been completed.18 User-Defined Event Example • Session 5 should run after both Session 2 and Session 4 complete successfully • The Event Raise task raises a user-defined event when Session 2 completes successfully • The lower pipeline will not proceed beyond the Event Wait task until the event has been raised Module 12: Controlling Workflows 18 of 30 User-Defined Events For a user-defined event..Controlling Workflows 12. Defines an event in the workflow properties (prior to workflow processing) 2. where further processing must await some specific event 3.0 Level I Developer Copyright © 2010 Informatica Corp . e.

the entire task can be set to fail if any one of the individual commands fails. Business Purpose OS commands can be used for any operational or business unit related procedure.0 Level I Developer Copyright © 2010 Informatica Corp . Command tasks can be set to run one or more OS commands or scripts/batch files. each individual command can be set not to run if a preceding command fails. and can be run at any point in a workflow. If more than one command is coded into a Command Task. before proceeding to the next task in the workflow. Additionally and optionally.or postsession in a Session task ƒ Command task status (success or failure) is held in the taskspecific variable $command_task_name.19 Command Task ƒ Specifies one or more UNIX command or shell script. PowerCenter 8. All commands or batch files referenced must be executable by the OS login that owns the Integration Service process. DOS command or batch file for Integration Services to run during a workflow Note: UNIX and DOS commands can also be run pre.Controlling Workflows 12.STATUS Module 12: Controlling Workflows 19 of 30 Description Command tasks are inserted in workflows and worklets to enable the Integration Service to run one or more OS commands of any nature.x/9.

x/9.Controlling Workflows 12. 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.0 Level I Developer Copyright © 2010 Informatica Corp . PowerCenter 8. opens it and verifies control totals or record counts with some external source of information. or FTPs the file to another box location.20 Command Task (cont’d) Add Cmd Remove Cmd Module 12: Controlling Workflows 20 of 30 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. 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.

Controlling Workflows 12.0 Level I Developer Copyright © 2010 Informatica Corp .21 Timer Task Waits for a specified period of time to execute the next task General Tab Timer Tab • Absolute Time • Datetime Variable • Relative Time Module 12: Controlling Workflows 21 of 30 PowerCenter 8.x/9.

fails.22 Control Task Stops. or aborts the Worklet or Workflow Module 12: Controlling Workflows 22 of 30 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .Controlling Workflows 12.x/9.

PowerCenter 8. However. stopping or aborting the parent Workflow means that no further progress takes place along that branch in the top-level Workflow. or abort either the parent Workflow or the top-level Workflow. Stops the workflow that is running. Marks the status of the workflow or worklet that contains the Control task as failed after the workflow or worklet completes.Controlling Workflows 12. Stops the workflow or worklet that contains the Control task. Stop Parent Abort Parent Aborts the workflow or worklet that contains the Control task. Fail Top-Level Workflow Fails the workflow that is running. Stop Top-Level Workflow Abort Top-Level Workflow Aborts the workflow that is running.0 Level I Developer Copyright © 2010 Informatica Corp .” The PowerCenter Server fails the Control task if you choose this option. Stop = Stop executing after orderly shutdown. stop.x/9.23 Control Options Control Option Fail Me Fail Parent Description Marks the Control task as “Failed. Abort = Stop executing immediately Module 12: Controlling Workflows 23 of 30 Note The Control task can fail. Note: Fail = Complete but set status to “failed”. This can cause the top-level Workflow to stop if there is no other branch.

Controlling Workflows

12.24

Reusable Tasks
• Session, Email and Command tasks can be reusable • Use the Task Developer to create reusable tasks • Reusable tasks appear in the Navigator Tasks node and can be dragged and dropped into any workflow In a workflow, a reusable task is indicated by a special symbol

Module 12: Controlling Workflows

24 of 30

Business Purpose

Occasionally, a certain mapping logic may be required to run in multiple workflows. Since a mapping is reusable, the developer can code multiple sessions, all based on the same mapping. However, it is simpler to create a reusable session based on the mapping. Once created in the Task Developer, an instance of the Reusable Session can be placed in any workflow or Worklet.

Performance Considerations

Use reusable session tasks sparingly. Retrieving the metadata for a reusable session task and its child instances from the repository takes longer than retrieving the metadata for a non-reusable session task.

PowerCenter 8.x/9.0 Level I Developer

Copyright © 2010 Informatica Corp

Controlling Workflows

12.25

pmcmd utility
• Line command utility providing most Workflow Manager operations, e.g. start workflow • Example of syntax: pmcmd startworkflow -sv MyIntService -d MyDomain -u seller3 -p jackson -f SalesEast wf_SalesAvg

Note: The password can be provided through the PASSWORD environmental variable. To do this, you can encrypt the password using the pmpasswd utility on the PowerCenter Services machine and then enter the encrypted password in pmcmd.
Module 12: Controlling Workflows

25 of 30

Description

The pmcmd command line utility allows the developer to perform most Workflow Manager operations outside of the PowerCenter client tool. These commands can be used in batch files.

PowerCenter 8.x/9.0 Level I Developer

Copyright © 2010 Informatica Corp

Controlling Workflows

12.26

Workflow Scheduler
• Set and customize workflow-specific schedule

Module 12: Controlling Workflows

26 of 30

PowerCenter 8.x/9.0 Level I Developer

Copyright © 2010 Informatica Corp

Controlling Workflows

12.27

Workflow Scheduler (cont’d)

Module 12: Controlling Workflows

27 of 30

PowerCenter 8.x/9.0 Level I Developer

Copyright © 2010 Informatica Corp

Controlling Workflows

12.28

Lab 12-1 – Using Assignment and Decision Tasks
• In this lab you will…
• Create a workflow that eliminates some types of bad data from getting into ODS_SALES • Assign workflow variables to keep track of how many times the workflow has run • Increment workflow variables using an Assignment task • Branch in a workflow using Link conditions and a Decision task to choose to run the next session or report an error

Module 12: Controlling Workflows

28 of 30

PowerCenter 8.x/9.0 Level I Developer

Copyright © 2010 Informatica Corp

x/9.Controlling Workflows 12.29 Lab 12-2 – Using Events and Timers • In this lab you will… • • • • Create a workflow that raises and uses a User-Defined event Stop the workflow “nicely” if the tables load properly Set a timer to fail the workflow if it takes more than 15 minutes Schedule the workflow to run at a particular time Module 12: Controlling Workflows 29 of 30 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

Controlling Workflows 12.0 Level I Developer Copyright © 2010 Informatica Corp .x/9. Command • Explain the purpose of the pmcmd utility • Schedule workflows to run automatically Module 12: Controlling Workflows 30 of 30 PowerCenter 8.30 Summary This module showed you how to: • Set and use workflow variables • Use link conditions and Decision tasks to control the execution of a workflow • Use other workflow tasks: Email. Event Raise. Event Wait.

0 Level I Developer Copyright © 2010 Informatica Corp .1 Module 13: Mapping Design Workshop PowerCenter 8.x/9.Mapping Design Workshop 13.

Mapping Design Workshop 13.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .2 Module Objectives After completing this module you will be able to: • Follow best practices for mapping design Module 13: Mapping Design Workshop 2 of 4 PowerCenter 8.

Mapping Design Workshop 13.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .3 Workshop 13-1: Mapping Design Workshop • In this lab you will… • Practice designing your own mappings Module 13: Mapping Design Workshop 3 of 4 PowerCenter 8.

0 Level I Developer Copyright © 2010 Informatica Corp .4 Summary This module showed you how to: • Follow best practices for mapping design Module 13: Mapping Design Workshop 4 of 4 PowerCenter 8.Mapping Design Workshop 13.x/9.

1 Module 14: Workflow Design Workshop PowerCenter 8.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .Workflow Design Workshop 14.

Workflow Design Workshop 14.x/9.2 Module Objectives After completing this module you will be able to: • Follow best practices for workflow design Module 14: Workflow Design Workshop 2 of 4 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .

x/9.Workflow Design Workshop 14.0 Level I Developer Copyright © 2010 Informatica Corp .3 Workshop 14-1: Workflow Design Workshop • In this lab you will… • Practice designing your own workflows Module 14: Workflow Design Workshop 3 of 4 PowerCenter 8.

4 Summary This module showed you how to: • Follow best practices for workflow design Module 14: Workflow Design Workshop 4 of 4 PowerCenter 8.0 Level I Developer Copyright © 2010 Informatica Corp .x/9.Workflow Design Workshop 14.

Workflow Design Workshop 15.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .1 Module 15: Workflow Design Workshop 15 PowerCenter 8.

0: • • • • • • • • Lookup transformation enhancements SQL transformation enhancements XML Parser enhancements Verbose Logging enhancement License Management enforcement Integration Service log file rollover Mapping Architect for Visio Additional Transformations infacmd Command Line enhancements Module 15: Workflow Design Workshop 2 of 8 PowerCenter 8.2 Objectives After completing this module you will be able to: • Describe New Features in PowerCenter 9.x/9.0 Level I Developer Copyright © 2010 Informatica Corp .Workflow Design Workshop 15.

you can add to or update the lookup cache.3 PowerCenter 9. Number of retries and sleep interval are configurable. • SQL overrides for uncached lookups. 15 Module 15: Workflow Design Workshop 3 of 8 Cache Updates You can update the lookup cache based on the results of an expression. You can update the dynamic lookup cache with the results of an expression Database Deadlock Resilience Database deadlock does not cause immediate session failure.x/9. • Database deadlock resilience. You can include lookup ports in the SQL query PowerCenter 8. The IS attempts to run the last statement in a lookup again.Workflow Design Workshop 15. When an expression is true.0 New Features • Lookup Transformation • Cache updates – Update Dynamic Cache Condition. Multiple Rows Return SQL Overrides for Uncached Lookups You can configure the Lookup transformation to return all rows that match a lookup condition You can create an SQL override for uncached lookup.0 Level I Developer Copyright © 2010 Informatica Corp . • Multiple rows return.

the order in which the operations are performed becomes important.x/9. Allows Referential Integrity constraints to be observed.Workflow Design Workshop 15.0 New Features • SQL Transformation • Environmental SQL for SQL Transformation • Set Active or Passive at design time for SQL Transform • Exactly Once semantics for SQL Transformation • XML Transformation • XML Parser Validation • Verbose Log • Log exact query in Verbose mode Module 15: Workflow Design Workshop 4 of 8 SQL Transform Exactly Once Semantics When deleting and inserting records with referential integrity constraints. XML Transformation Parser can validate an XML document against a schema Routes invalid XML to an error port Routes messages to a separate output group Verbose Log The exact query executed is logged in Verbose mode PowerCenter 8.4 PowerCenter 9.0 Level I Developer Copyright © 2010 Informatica Corp .

0 New Features • License Management • Core license management • Repository license management • Integration Service • Mapping Architect for Visio • New mapping objects including Normalizer.5 PowerCenter 9.Workflow Design Workshop 15. shortcuts. PowerExchange Target definition Can configure a transformation to use a shortcut You can create a Mapping template that contains these objects. Custom Transformation. Custom transformation 15 Module 15: Workflow Design Workshop 5 of 8 License Management Number of cores enforcement: Ensures that licensees do not exceed licensed number of cores Repository Licensing: Ensures that licensees do not exceed licensed number of repositories Integration Service Mapping Architect for Visio Session log file rollover: Limit the size of session logs for real-time sessions New Mapping Objects: Pipeline Normalizer.x/9.0 Level I Developer Copyright © 2010 Informatica Corp . PowerExchange Source Definition. or reusable transformations PowerCenter 8.

x/9.Workflow Design Workshop 15.0 New Features • Command Line • Infacmd to include new application services Module 15: Workflow Design Workshop 6 of 8 Infacmd expanded to infacmd ds (data services) include management infacmd isp (Informatica service manager) of all Informatica application services infacmd oie (Object import and export) infacmd prs (Model Repository services) infacmd rtm (Analyst Tool services) infacmd sql (SQL data services) infacmd help <application service> for help on each service type PowerCenter 8.6 PowerCenter 9.0 Level I Developer Copyright © 2010 Informatica Corp .

0: • • • • • • • • Lookup transformation enhancements SQL transformation enhancements XML Parser enhancements Verbose Logging enhancement License Management enforcement Integration Service log file rollover Mapping Architect for Visio Additional Transformations infacmd Command Line enhancements 15 Module 15: Workflow Design Workshop 7 of 8 PowerCenter 8.x/9.7 Summary This module showed you how to: • Describe New Features in PowerCenter 9.0 Level I Developer Copyright © 2010 Informatica Corp .Workflow Design Workshop 15.

0 Level I Developer Copyright © 2010 Informatica Corp .Workflow Design Workshop 15.8 PowerCenter 8.x/9.

1 ____ rehtO ____ retekrameleT ____ rebmuN 008 ____ beW ?ssalc siht rof retsiger ot esu uoy did dohtem tahW )tnirp( noitamrofnI lanoitpO )tnirp( enohP liam-E ynapmoC emaN ruoY noitamrofnI deriuqeR rotcurtsnI noitacoL etaD tratS esruoC eltiT esruoC Global Education Services Course Evaluation .21 llorne ot ysae ti edam ssecorp noitartsigeR .31 gninrael ot evicudnoc saw seitilicaf eht fo ytilauq ehT .3 ?sloot yreuq LQS ot erusopxe fo level ruoy saw tahW .8 ot em elbane ot emit ssalc desu ylevitceffe rotcurtsni ehT aera tcejbus eht ni elbaegdelwonk saw rotcurtsni ehT .1 slairetaM dna tnetnoC esruoC lufpleh erew rotcurtsni eht yb desu sdia lausiv ehT .6 lairetam esruoc eht gninrael ni depleh sesicrexe bal ehT .71 reyolpme ym rof tnemtsevni elihwhtrow a saw gniniart sihT .9002/61/1 0 5 4 3 2 1 llarevO gniniarT eht htiw deifsitas ma I .9 stpecnoc yek eht nrael .01 snoitseuq ksa ot stneduts degaruocne rotcurtsni ehT .51 llarevO 0 5 4 3 2 1 gninrael ym ni loot evitceffe na saw tnempiuqe moorssalC .3 sevitcejbo detats eht tem esruoc ehT .61 ecnamrofrep boj ym evorpmi lliw gniniart sihT .4 tnetnoc eht revoc ot hguone gnol saw htgnel esruoc ehT .2 ?tcudorp eht ot erusopxe fo level ruoy saw tahW .41 noitartsigeR dna seitilicaF yletelpmoc dna ylraelc derewsna erew snoitseuq tnedutS .7 rotcurtsnI sbal gnirud lufpleh dna elbaliava saw rotcurtsni ehT .2 snoitatcepxe ym tem tnetnoc esruoc ehT .11 hguone gnol saw sbal rof dettolla emit ehT .5 elbacilppA eergA toN ylgnortS 5 eergA 4 lartueN 3 eergasiD eergasiD ylgnortS 2 1 decnavdA lacinhceT emoS laminiM enoN ?stpecnoc BDR ot erusopxe fo level ruoy saw tahW .

e li a m .e rebmuN enohP rebmuN enohP e ma N e maN .sesruoc ruo fo eno morf tifeneb dluow leef uoy enoyna rof noitamrofni tcatnoc edivorp esaelP seY 5 oN 0 ?srehto ot esruoc siht dnemmocer uoy dluoW ?su htiw ssenisub od ot reisae ti ekam dluow taht evah uoy od snoitseggus tahW ?ees ot ekil uoy dluow )s(esruoc pu wollof tahW ?tnemnorivne moorssalc eht gnivorpmi rof evah uoy od snoitseggus tahW ?esruoc eht fo yreviled reh/sih evorpmi ot rotcurtsni eht reffo uoy dluow snoitseggus tahW ?ralucitrap ni tinu ynA ?retrohs ro regnol edam eb esruoc eht dluohS ?ralucitrap ni bal ynA ?denetrohs ro denehtgnel eb emit bal eht dluohS :sseL ?egarevoc sseL ?ssalc ni egarevoc erom eriuqer scipot tahW ?noitatneserp ro dna slairetam :tnemevorpmi esruoc rof tseggus uoy nac snoitadnemmocer tahW :tsaeL :eroM ?yhw dna uoy rof elbaulav tsael .elbaulav tsom eht erew stinU tahW Global Education Services Course Evaluation :tsoM .9002/61/1 li a m .

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->