informatica-getting started

8/7/2019 Informatica-Getting Started

1/150

Getting Started

Informatica PowerCenter(Version 7.1.1)


2/150

Informatica PowerCenter Getting Started

Version 7.1.1

August 2004

Copyright (c) 19982004 Informatica Corporation.

All rights reserved. Printed in the USA.

This software and documentation contain proprietary information of Informatica Corporation, they are provided under a license agreement

containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. Nopart 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 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 WashingtonUniversity 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 GNULesser 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-2004 The Apache Software Foundation. All rights reserved.

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 informationprovided 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.


3/150

ii i

Table of Contents

List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

New Features and Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

PowerCenter 7.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

PowerCenter 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv

PowerCenter 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xviii

About Informatica Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv

About this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv

Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv

Other Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi

Visiting Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . xxviVisiting the Informatica Webzine . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi

Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi

Visiting the Informatica Developer Network . . . . . . . . . . . . . . . . . . . . xxvi

Obtaining Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii

Chapter 1: Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Using the PowerCenter Client in the Tutorial . . . . . . . . . . . . . . . . . . . . . 3

Connecting to Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2: Tutorial Lesson 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Creating Repository Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Connecting to the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Creating a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Assigning Privileges to a Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Creating a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

What Comes Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Creating a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Folder Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14


4/150

i v Table o f Con tents

Folders in this Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Creating Source Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

What Comes Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Chapter 3: Tutorial Lesson 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Creating Source Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Viewing Source Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Creating Target Defini tions and Target Tables . . . . . . . . . . . . . . . . . . . . . . . 27

Creating Target Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Creating Target Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

What Comes Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31


Creating a Pass-Through Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Creating a Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Connecting Transformations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Creating Sessions and Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Configuring Database Connections in the Workflow Manager. . . . . . . . .39

Creating a Reusable Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Creating a Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Running and Monitoring Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Opening the Workflow Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Running the Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47What Comes Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49


Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Creating a New Target Definition and Target . . . . . . . . . . . . . . . . . . . . . . . .54

Creating a Target Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Creating a Target Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Creating a Mapping with Aggregate Values. . . . . . . . . . . . . . . . . . . . . . . . . .58

Creating a Mapping with T_ITEM_SUMMARY . . . . . . . . . . . . . . . . . .58

Creating an Aggregator Transformation . . . . . . . . . . . . . . . . . . . . . . . . .58

Creating an Expression Transformation . . . . . . . . . . . . . . . . . . . . . . . . .63

Creating a Lookup Transformation . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Connecting the Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Designer Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68


5/150

Table of Conte nt s v

Using the Overview Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Arranging Transformations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Creating a Session and Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Creating the Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Creating the Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Running the Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

What Comes Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74


Creating a Mapping with Fact and Dimension Tables . . . . . . . . . . . . . . . . . . 76

Creating Targets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Creating the Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Creating a Filter Transformation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Creating a Sequence Generator Transformation . . . . . . . . . . . . . . . . . . . 81

Creating a Stored Procedure Transformation . . . . . . . . . . . . . . . . . . . . . 83

Completing the Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Creating a Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Creating the Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Creating a Link Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Running the Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91


Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Creating the XML Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Importing the XML Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Editing the XML Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Creating the Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Creating a Mapping with XML Sources and Targets . . . . . . . . . . . . . . . . . . 104

Creating an Expression Transformation . . . . . . . . . . . . . . . . . . . . . . . . 104

Creating Router Transformations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Completing the Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Creating a Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Appendix A: Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Suggested Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Transformations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121


6/150

v i Table o f Con tents

Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Mapplets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Worklets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121


7/150

List of Figures vii

List of Figures

Figure 4-1. Pass-Through Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Figure 4-2. Sample Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Figure 5-1. Transformation Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Figure 6-1. Mapping with Fact and Dimension Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Figure 7-1. Mapping with XML Sources and Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Figure 7-2. XML Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Figure 7-3. ENG_SALARY.XML Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Figure 7-4. SLS_SALARY.XML Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117


8/150

v ii i L is t o f F igures


9/150

List of Tables ix

List of Tables

Table 1-1. Administrator Repository Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Table 1-2. Repository Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Table 1-3. ODBC Data Source Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Table 1-4. Workflow Manager Connectivity Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Table 1-5. Native Connect String Syntax for Database Platforms . . . . . . . . . . . . . . . . . . . . . . . 5

Table 5-1. Transformation Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Table 6-1. F_PROMO_ITEMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Table 6-2. Stored Procedure Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Table A-1. Naming Conventions for Transformations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120


10/150

x Li st of Tabl es


11/150

xi

Preface

Welcome to PowerCenter, Informaticas software product that delivers an open, scalable dataintegration solution addressing the complete life cycle for all data integration projects

including data warehouses and data marts, data migration, data synchronization, andinformation hubs. PowerCenter combines the latest technology enhancements for reliablymanaging data repositories and delivering information resources in a timely, usable, andefficient manner.

The PowerCenter metadata repository coordinates and drives a variety of core functions,including extracting, transforming, loading, and managing data. The PowerCenter Server canextract large volumes of data from multiple platforms, handle complex transformations on thedata, and support high-speed loads. PowerCenter can simplify and accelerate the process ofmoving data warehouses from development to test to production.


12/150

xii Preface

New Features and Enhancements

This section describes new features and enhancements to PowerCenter 7.1.1, 7.1, and 7.0.

PowerCenter 7.1.1

This section describes new features and enhancements to PowerCenter 7.1.1.

Data Profiling

Data sampling. You can create a data profile for a sample of source data instead of the

entire source. You can view a profile from a random sample of data, a specified percentageof data, or for a specified number of rows starting with the first row.

Verbose data enhancements. You can specify the type of verbose data you want thePowerCenter Server to write to the Data Profiling warehouse. The PowerCenter Server canwrite all rows, the rows that meet the business rule, or the rows that do not meet thebusiness rule.

Session enhancement. You can save sessions that you create from the Profile Manager tothe repository.

Domain Inference function tuning. You can configure the Data Profiling Wizard to filterthe Domain Inference function results. You can configure a maximum number of patternsand a minimum pattern frequency. You may want to narrow the scope of patterns returnedto view only the primary domains, or you may want to widen the scope of patternsreturned to view exception data.

Row Uniqueness function. You can determine unique rows for a source based on aselection of columns for the specified source.

Define mapping, session, and workflow prefixes. You can define default mapping,session, and workflow prefixes for the mappings, sessions, and workflows generated whenyou create a data profile.

Profile mapping display in the Designer. The Designer displays profile mappings under aprofile mappings node in the Navigator.

PowerCenter Server Code page. PowerCenter supports additional Japanese language code pages, such as JIPSE-

kana, JEF-kana, and MELCOM-kana.

Flat file partitioning. When you create multiple partitions for a flat file source session, youcan configure the session to create multiple threads to read the flat file source.

pmcmd. You can use parameter files that reside on a local machine with the Startworkflowcommand in the pmcmdprogram. When you use a local parameter file, pmcmdpasses

variables and values in the file to the PowerCenter Server.


13/150

Preface xiii

SuSE Linux support. The PowerCenter Server runs on SuSE Linux. On SuSE Linux, youcan connect to IBM, DB2, Oracle, and Sybase sources, targets, and repositories usingnative drivers. Use ODBC drivers to access other sources and targets.

Reserved word support. If any source, target, or lookup table name or column name

contains a database reserved word, you can create and maintain a file, reswords.txt,containing reserved words. When the PowerCenter Server initializes a session, it searchesfor reswords.txt in the PowerCenter Server installation directory. If the file exists, thePowerCenter Server places quotes around matching reserved words when it executes SQLagainst the database.

Teradata external loader. When you load to Teradata using an external loader, you cannow override the control file. Depending on the loader you use, you can also override theerror, log, and work table names by specifying different tables on the same or different

Teradata database.

Repository

Exchange metadata with other tools. You can exchange source and target metadata withother BI or data modeling tools, such as Business Objects Designer. You can export orimport multiple objects at a time. When you export metadata, the PowerCenter Clientcreates a file format recognized by the target tool.

Repository Server

pmrep. You can use pmrep to perform the following functions:

Remove repositories from the Repository Server cache entry list.

Enable enhanced security when you create a relational source or target connection in therepository.

Update a connection attribute value when you update the connection.

SuSE Linux support. The Repository Server runs on SuSE Linux. On SuSE Linux, youcan connect to IBM, DB2, Oracle, and Sybase repositories.

Security

Oracle OS Authentication. You can now use Oracle OS Authentication to authenticatedatabase users. Oracle OS Authentication allows you to log on to an Oracle database if youhave a logon to the operating system. You do not need to know a database user name andpassword. PowerCenter uses Oracle OS Authentication when the user name for an Oracleconnection is PmNullUser.

Web Services Provider

Attachment support. When you import web service definitions with attachment groups,you can pass attachments through the requests or responses in a service session. Thedocument type you can attach is based on the mime content of the WSDL file. You canattach document types such as XML, JPEG, GIF, or PDF.


14/150

xiv Pref ac e

Pipeline partitioning. You can create multiple partitions in a session containing webservice source and target definitions. The PowerCenter Server creates a connection to theWeb Services Hub based on the number of sources, targets, and partitions in the session.

XML Multi-level pivoting. You can now pivot more than one multiple-occurring element in an

XML view. You can also pivot the view row.

PowerCenter 7.1

This section describes new features and enhancements to PowerCenter 7.1.

Data Profiling

Data Profiling for VSAM sources. You can now create a data profile for VSAM sources.

Support for verbose mode for source-level functions. You can now create data profileswith source-level functions and write data to the Data Profiling warehouse in verbosemode.

Aggregator function in auto profiles. Auto profiles now include the Aggregator function.

Creating auto profile enhancements. You can now select the columns or groups you wantto include in an auto profile and enable verbose mode for the Distinct Value Countfunction.

Purging data from the Data Profiling warehouse. You can now purge data from the DataProfiling warehouse.

Source View in the Profile Manager. You can now view data profiles by source definitionin the Profile Manager.

PowerCenter Data Profiling report enhancements. You can now view PowerCenter DataProfiling reports in a separate browser window, resize columns in a report, and viewverbose data for Distinct Value Count functions.

Prepackaged domains. Informatica provides a set of prepackaged domains that you caninclude in a Domain Validation function in a data profile.

Documentation Web Services Provider Guide.This is a new book that describes the functionality of Real-time

Web Services. It also includes information from the version 7.0 Web Services Hub Guide.

XML User Guide. This book consolidates XML information previously documented in theDesigner Guide, Workflow Administration Guide, and Transformation Guide.

Licensing

Informatica provides licenses for each CPU and each repository rather than for eachinstallation. Informatica provides licenses for product, connectivity, and options. You store


15/150

Preface xv

the license keys in a license key file. You can manage the license files using the RepositoryServer Administration Console, the PowerCenter Server Setup, and the command lineprogram, pmlic.

PowerCenter Server 64-bit support. You can now run 64-bit PowerCenter Servers on AIX and HP-UX

(Itanium).

Partitioning enhancements. If you have the Partitioning option, you can define up to 64partitions at any partition point in a pipeline that supports multiple partitions.

PowerCenter Server processing enhancements. The PowerCenter Server now reads ablock of rows at a time. This improves processing performance for most sessions.

CLOB/BLOB datatype support. You can now read and write CLOB/BLOB datatypes.

PowerCenter Metadata Reporter

PowerCenter Metadata Reporter modified some report names and uses the PowerCenter 7.1MX views in its schema.

Repository Server Updating repository statistics. PowerCenter now identifies and updates statistics for all

repository tables and indexes when you copy, upgrade, and restore repositories. Thisimproves performance when PowerCenter accesses the repository.

Increased repository performance. You can increase repository performance by skippinginformation when you copy, back up, or restore a repository. You can choose to skip MXdata, workflow and session log history, and deploy group history.

pmrep. You can use pmrep to back up, disable, or enable a repository, delete a relationalconnection from a repository, delete repository details, truncate log files, and run multiplepmrep commands sequentially. You can also use pmrep to create, modify, and delete afolder.

Repository

Exchange metadata with business intelligence tools. You can export metadata to and

import metadata from other business intelligence tools, such as Cognos Report Net andBusiness Objects.

Object import and export enhancements. You can compare objects in an XML file toobjects in the target repository when you import objects.

MX views. MX views have been added to help you analyze metadata stored in therepository. REP_SERVER_NET and REP_SERVER_NET_REF views allow you to seeinformation about server grids. REP_VERSION_PROPS allows you to see the version

history of all objects in a PowerCenter repository.


16/150

xvi Pref ac e

Transformations

Flat file lookup. You can now perform lookups on flat files. When you create a Lookuptransformation using a flat file as a lookup source, the Designer invokes the Flat FileWizard. You can also use a lookup file parameter if you want to change the name or

location of a lookup between session runs. Dynamic lookup cache enhancements. When you use a dynamic lookup cache, the

PowerCenter Server can ignore some ports when it compares values in lookup and inputports before it updates a row in the cache. Also, you can choose whether the PowerCenterServer outputs old or new values from the lookup/output ports when it updates a row. Youmight want to output old values from lookup/output ports when you use the Lookuptransformation in a mapping that updates slowly changing dimension tables.

Union transformation. You can use the Union transformation to merge multiple sourcesinto a single pipeline. The Union transformation is similar to using the UNION ALL SQLstatement to combine the results from two or more SQL statements.

Custom transformation API enhancements. The Custom transformation API includesnew array-based functions that allow you to create procedure code that receives andoutputs a block of rows at a time. Use these functions to take advantage of thePowerCenter Server processing enhancements.

Midstream XML transformations. You can now create an XML Parser transformation or

an XML Generator transformation to parse or generate XML inside a pipeline. The XMLtransformations enable you to extract XML data stored in relational tables, such as datastored in a CLOB column. You can also extract data from messaging systems, such asTIBCO or IBM MQSeries.

Usability

Viewing active folders. The Designer and the Workflow Manager highlight the active

folder in the Navigator.

Enhanced printing. The quality of printed workspace has improved.

Version Control

You can run object queries that return shortcut objects. You can also run object queries basedon the latest status of an object. The query can return local objects that are checked out, the

latest version of checked in objects, or a collection of all older versions of objects.

Web Services Provider

Real-time Web Services. Real-time Web Services allows you to create services using theWorkflow Manager and make them available to web service clients through the WebServices Hub. The PowerCenter Server can perform parallel processing of both request-response and one-way services.

Web Services Hub. The Web Services Hub now hosts Real-time Web Services in additionto Metadata Web Services and Batch Web Services. You can install the Web Services Hubon a JBoss application server.


17/150

Preface xvii

Note: PowerCenter Connect for Web Services allows you to create sources, targets, andtransformations to call web services hosted by other providers. For more informations, seePowerCenter Connect for Web Services User and Administrator Guide.

Workflow MonitorThe Workflow Monitor includes the following performance and usability enhancements:

When you connect to the PowerCenter Server, you no longer distinguish between onlineor offline mode.

You can open multiple instances of the Workflow Monitor on one machine.

You can simultaneously monitor multiple PowerCenter Servers registered to the samerepository.

The Workflow Monitor includes improved options for filtering tasks by start and endtime.

The Workflow Monitor displays workflow runs in Task view chronologically with the mostrecent run at the top. It displays folders alphabetically.

You can remove the Navigator and Output window.

XML SupportPowerCenter XML support now includes the following features:

Enhanced datatype support. You can use XML schemas that contain simple and complexdatatypes.

Additional options for XML definitions. When you import XML definitions, you canchoose how you want the Designer to represent the metadata associated with the importedfiles. You can choose to generate XML views using hierarchy or entity relationships. In a

view with hierarchy relationships, the Designer expands each element and reference underits parent element. When you create views with entity relationships, the Designer createsseparate entities for references and multiple-occurring elements.

Synchronizing XML definitions. You can synchronize one or more XML definition whenthe underlying schema changes. You can synchronize an XML definition with anyrepository definition or file used to create the XML definition, including relational sourcesor targets, XML files, DTD files, or schema files.

XML workspace. You can edit XML views and relationships between views in theworkspace. You can create views, add or delete columns from views, and definerelationships between views.

Midstream XML transformations. You can now create an XML Parser transformation oran XML Generator transformation to parse or generate XML inside a pipeline. The XMLtransformations enable you to extract XML data stored in relational tables, such as datastored in a CLOB column. You can also extract data from messaging systems, such as

TIBCO or IBM MQSeries.


18/150

xvi ii P re face

Support for circular references. Circular references occur when an element is a direct orindirect child of itself. PowerCenter now supports XML files, DTD files, and XMLschemas that use circular definitions.

Increased performance for large XML targets. You can create XML files of severalgigabytes in a PowerCenter 7.1 XML session by using the following enhancements:

Spill to disk. You can specify the size of the cache used to store the XML tree. If the sizeof the tree exceeds the cache size, the XML data spills to disk in order to free upmemory.

User-defined commits. You can define commits to trigger flushes for XML target files.

Support for multiple XML output files. You can output XML data to multiple XMLtargets. You can also define the file names for XML output files in the mapping.

PowerCenter 7.0

This section describes new features and enhancements to PowerCenter 7.0.

Data Profiling

If you have the Data Profiling option, you can profile source data to evaluate source data and

detect patterns and exceptions. For example, you can determine implicit data type, suggestcandidate keys, detect data patterns, and evaluate join criteria. After you create a profilingwarehouse, you can create profiling mappings and run sessions. Then you can view reportsbased on the profile data in the profiling warehouse.

The PowerCenter Client provides a Profile Manager and a Profile Wizard to complete thesetasks.

Data Integration Web ServicesYou can use Data Integration Web Services to write applications to communicate with thePowerCenter Server. Data Integration Web Services is a web-enabled version of thePowerCenter Server functionality available through Load Manager and Metadata Exchange. Itis comprised of two services for communication with the PowerCenter Server, Load Managerand Metadata Exchange Web Services running on the Web Services Hub.

Documentation Glossary. The Installation and Configuration Guidecontains a glossary of new PowerCenter

terms.

Installation and Configuration Guide. The connectivity information in the Installationand Configuration Guideis consolidated into two chapters. This book now containschapters titled Connecting to Databases from Windows and Connecting to Databasesfrom UNIX.

Upgrading metadata. The Installation and Configuration Guidenow contains a chaptertitled Upgrading Repository Metadata. This chapter describes changes to repository


19/150

Preface xix

objects impacted by the upgrade process. The change in functionality for existing objectsdepends on the version of the existing objects. Consult the upgrade information in thischapter for each upgraded object to determine whether the upgrade applies to your currentversion of PowerCenter.

Functions

Soundex. The Soundex function encodes a string value into a four-character string.SOUNDEX works for characters in the English alphabet (A-Z). It uses the first characterof the input string as the first character in the return value and encodes the remainingthree unique consonants as numbers.

Metaphone. The Metaphone function encodes string values. You can specify the length ofthe string that you want to encode. METAPHONE encodes characters of the Englishlanguage alphabet (A-Z). It encodes both uppercase and lowercase letters in uppercase.

Installation

Remote PowerCenter Client installation. You can create a control file containinginstallation information, and distribute it to other users to install the PowerCenter Client.You access the Informatica installation CD from the command line to create the controlfile and install the product.

PowerCenter Metadata Reporter

PowerCenter Metadata Reporter replaces Runtime Metadata Reporter and InformaticaMetadata Reporter. PowerCenter Metadata Reporter includes the following features:

Metadata browsing. You can use PowerCenter Metadata Reporter to browse PowerCenter7.0 metadata, such as workflows, worklets, mappings, source and target tables, and

transformations. Metadata analysis. You can use PowerCenter Metadata Reporter to analyze operational

metadata, including session load time, server load, session completion status, sessionerrors, and warehouse growth.

PowerCenter Server

DB2 bulk loading. You can enable bulk loading when you load to IBM DB2 8.1.

Distributed processing. If you purchase the Server Grid option, you can groupPowerCenter Servers registered to the same repository into a server grid. In a server grid,PowerCenter Servers balance the workload among all the servers in the grid.

Row error logging. The session configuration object has new properties that allow you todefine error logging. You can choose to log row errors in a central location to helpunderstand the cause and source of errors.

External loading enhancements. When using external loaders on Windows, you can nowchoose to load from a named pipe. When using external loaders on UNIX, you can nowchoose to load from staged files.


20/150

xx Preface

External loading using Teradata Warehouse Builder. You can use Teradata WarehouseBuilder to load to Teradata. You can choose to insert, update, upsert, or delete data.Additionally, Teradata Warehouse Builder can simultaneously read from multiple sourcesand load data into one or more tables.

Mixed mode processing for Teradata external loaders. You can now use data driven loadmode with Teradata external loaders. When you select data driven loading, thePowerCenter Server flags rows for insert, delete, or update. It writes a column in the targetfile or named pipe to indicate the update strategy. The control file uses these values todetermine how to load data to the target.

Concurrent processing. The PowerCenter Server now reads data concurrently fromsources within a target load order group. This enables more efficient joins with minimalusage of memory and disk cache.

Real time processing enhancements. You can now use real-time processing in sessions thatalso process active transformations, such as the Aggregator transformation. You can applythe transformation logic to rows defined by transaction boundaries.

Repository Server

Object export and import enhancements. You can now export and import objects usingthe Repository Manager and pmrep. You can export and import multiple objects and

objects types. You can export and import objects with or without their dependent objects.You can also export objects from a query result or objects history.

pmrep commands. You can use pmrep to perform change management tasks, such asmaintaining deployment groups and labels, checking in, deploying, importing, exporting,and listing objects. You can also use pmrep to run queries. The deployment and objectimport commands require you to use a control file to define options and resolve conflicts.

Trusted connections. You can now use a Microsoft SQL Server trusted connection to

connect to the repository.

Security

LDAP user authentication. You can now use default repository user authentication orLightweight Directory Access Protocol (LDAP) to authenticate users. If you use LDAP, therepository maintains an association between your repository user name and your externallogin name. When you log in to the repository, the security module passes your login name

to the external directory for authentication. The repository maintains a status for eachuser. You can now enable or disable users from accessing the repository by changing thestatus. You do not have to delete user names from the repository.

Use Repository Manager privilege. The Use Repository Manager privilege allows you toperform tasks in the Repository Manager, such as copy object, maintain labels, and changeobject status. You can perform the same tasks in the Designer and Workflow Manager ifyou have the Use Designer and Use Workflow Manager privileges.

Audit trail. You can track changes to repository users, groups, privileges, and permissionsthrough the Repository Server Administration Console. The Repository Agent logssecurity changes to a log file stored in the Repository Server installation directory. The


21/150

Preface xxi

audit trail log contains information, such as changes to folder properties, adding orremoving a user or group, and adding or removing privileges.

Transformations

Custom transformation. Custom transformations operate in conjunction with proceduresyou create outside of the Designer interface to extend PowerCenter functionality. TheCustom transformation replaces the Advanced External Procedure transformation. You cancreate Custom transformations with multiple input and output groups, and you cancompile the procedure with any C compiler.

You can create templates that customize the appearance and available properties of aCustom transformation you develop. You can specify the icons used for transformation,the colors, and the properties a mapping developer can modify. When you create a Customtransformation template, distribute the template with the DLL or shared library youdevelop.

Joiner transformation. You can use the Joiner transformation to join two data streams thatoriginate from the same source.

Version Control

The PowerCenter Client and repository introduce features that allow you to create andmanage multiple versions of objects in the repository. Version control allows you to maintainmultiple versions of an object, control development on the object, track changes, and usedeployment groups to copy specific groups of objects from one repository to another. Versioncontrol in PowerCenter includes the following features:

Object versioning. Individual objects in the repository are now versioned. This allows youto store multiple copies of a given object during the development cycle. Each version is aseparate object with unique properties.

Check out and check in versioned objects. You can check out and reserve an object youwant to edit, and check in the object when you are ready to create a new version of theobject in the repository.

Compare objects. The Repository Manager and Workflow Manager allow you to comparetwo repository objects of the same type to identify differences between them. You cancompare Designer objects and Workflow Manager objects in the Repository Manager. Youcan compare tasks, sessions, worklets, and workflows in the Workflow Manager. The

PowerCenter Client tools allow you to compare objects across open folders andrepositories. You can also compare different versions of the same object.

Delete or purge a version. You can delete an object from view and continue to store it inthe repository. You can recover or undelete deleted objects. If you want to permanentlyremove an object version, you can purge it from the repository.

Deployment. Unlike copying a folder, copying a deployment group allows you to copy aselect number of objects from multiple folders in the source repository to multiple folders

in the target repository. This gives you greater control over the specific objects copied fromone repository to another.


22/150

xxi i Pr ef ac e

Deployment groups. You can create a deployment group that contains references toobjects from multiple folders across the repository. You can create a static deploymentgroup that you manually add objects to, or create a dynamic deployment group that uses aquery to populate the group.

Labels. A label is an object that you can apply to versioned objects in the repository. Thisallows you to associate multiple objects in groups defined by the label. You can use labelsto track versioned objects during development, improve query results, and organize groupsof objects for deployment or export and import.

Queries. You can create a query that specifies conditions to search for objects in therepository. You can save queries for later use. You can make a private query, or you canshare it with all users in the repository.

Track changes to an object. You can view a history that includes all versions of an object

and compare any version of the object in the history to any other version. This allows youto see the changes made to an object over time.

XML Support

PowerCenter contains XML features that allow you to validate an XML file against an XMLschema, declare multiple namespaces, use XPath to locate XML nodes, increase performancefor large XML files, format your XML file output for increased readability, and parse or

generate XML data from various sources. XML support in PowerCenter includes thefollowing features:

XML schema. You can use an XML schema to validate an XML file and to generate sourceand target definitions. XML schemas allow you to declare multiple namespaces so you canuse prefixes for elements and attributes. XML schemas also allow you to define somecomplex datatypes.

XPath support. The XML wizard allows you to view the structure of XML schema. You

can use XPath to locate XML nodes.

Increased performance for large XML files. When you process an XML file or stream, youcan set commits and periodically flush XML data to the target instead of writing all theoutput at the end of the session. You can choose to append the data to the same target fileor create a new target file after each flush.

XML target enhancements. You can format the XML target file so that you can easily viewthe XML file in a text editor. You can also configure the PowerCenter Server to not output

empty elements to the XML target.

Usability

Copying objects. You can now copy objects from all the PowerCenter Client tools usingthe copy wizard to resolve conflicts. You can copy objects within folders, to other folders,and to different repositories. Within the Designer, you can also copy segments ofmappings to a workspace in a new folder or repository.

Comparing objects. You can compare workflows and tasks from the Workflow Manager.You can also compare all objects from within the Repository Manager.


23/150

Preface xxiii

Change propagation. When you edit a port in a mapping, you can choose to propagatechanged attributes throughout the mapping. The Designer propagates ports, expressions,and conditions based on the direction that you propagate and the attributes you choose topropagate.

Enhanced partitioning interface. The Session Wizard is enhanced to provide a graphicaldepiction of a mapping when you configure partitioning.

Revert to saved. You can now revert to the last saved version of an object in the WorkflowManager. When you do this, the Workflow Manager accesses the repository to retrieve thelast-saved version of the object.

Enhanced validation messages. The PowerCenter Client writes messages in the Outputwindow that describe why it invalidates a mapping or workflow when you modify adependent object.

Validate multiple objects. You can validate multiple objects in the repository withoutfetching them into the workspace. You can save and optionally check in objects thatchange from invalid to valid status as a result of the validation. You can validate sessions,mappings, mapplets, workflows, and worklets.

View dependencies. Before you edit or delete versioned objects, such as sources, targets,mappings, or workflows, you can view dependencies to see the impact on other objects.You can view parent and child dependencies and global shortcuts across repositories.

Viewing dependencies help you modify objects and composite objects without breakingdependencies.

Refresh session mappings. In the Workflow Manager, you can refresh a session mapping.

Ab I f i D i


24/150

xxiv P re face

About Informatica Documentation

The complete set of documentation for PowerCenter includes the following books:

Data Profiling Guide. Provides information about how to profile PowerCenter sources toevaluate source data and detect patterns and exceptions.

Designer Guide. Provides information needed to use the Designer. Includes information tohelp you create mappings, mapplets, and transformations. Also includes a description ofthe transformation datatypes used to process and transform source data.

Getting Started. Provides basic tutorials for getting started.

Installation and Configuration Guide. Provides information needed to install and

configure the PowerCenter tools, including details on environment variables and databaseconnections.

PowerCenter Connect for JMSUser and Administrator Guide. Provides informationto install PowerCenter Connect for JMS, build mappings, extract data from JMS messages,and load data into JMS messages.

Repository Guide. Provides information needed to administer the repository using theRepository Manager or the pmrep command line program. Includes details onfunctionality available in the Repository Manager and Administration Console, such ascreating and maintaining repositories, folders, users, groups, and permissions andprivileges.

Transformation Language Reference. Provides syntax descriptions and examples for eachtransformation function provided with PowerCenter.

Transformation Guide. Provides information on how to create and configure each type oftransformation in the Designer.

Troubleshooting Guide. Lists error messages that you might encounter while usingPowerCenter. Each error message includes one or more possible causes and actions thatyou can take to correct the condition.

Web Services Provider Guide.Provides information you need to install and configure the WebServices Hub. This guide also provides information about how to use the web services that theWeb Services Hub hosts. The Web Services Hub hosts Real-time Web Services, Batch WebServices, and Metadata Web Services.

Workflow Administration Guide. Provides information to help you create and run

workflows in the Workflow Manager, as well as monitor workflows in the WorkflowMonitor. Also contains information on administering the PowerCenter Server andperformance tuning.

XML User Guide. Provides information you need to create XML definitions from XML,XSD, or DTD files, and relational or other XML definitions. Includes information onrunning sessions with XML data. Also includes details on using the midstream XMLtransformations to parse or generate XML data within a pipeline.

Ab t thi B k


25/150

Preface xxv

About this Book

Getting Startedis written for the IS developers and software engineers who are responsible forimplementing a data warehouse. It provides a tutorial to help first-time users learn how to use

PowerCenter. Getting Startedassumes you have knowledge of your operating systems,relational database concepts, and the database engines, flat files, or mainframe systems in yourenvironment. The guide also assumes you are familiar with the interface requirements foryour supporting applications.

The material in this book is available for online use.

Document Conventions

This guide uses the following formatting conventions:

If you see It means

italicized text The word or set of words are especially emphasized.

boldfaced text Emphasized subjects.

italicized monospaced text This is the variable name for a value you enter as part of anoperating system command. This is generic text that should be

replaced with user-supplied values.

Note: The following paragraph provides additional facts.

Tip: The following paragraph provides suggested uses.

Warning: The following paragraph notes situations where you can overwriteor corrupt data, unless you follow the specified procedure.

monospaced text This is a code example.

bold monospaced text This is an operating system command you enter from a prompt to

run a task.

Other Informatica Resources


26/150

xxv i P re face

Other Informatica Resources

In addition to the product manuals, Informatica provides these other resources:

Informatica Customer Portal

Informatica Webzine

Informatica web site

Informatica Developer Network

Informatica Technical Support

Visiting Informatica Customer PortalAs 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 Knowledgebase, Informatica Webzine, and access to the Informatica usercommunity.

Visiting the Informatica WebzineThe Informatica Documentation team delivers an online journal, the Informatica Webzine.This journal provides solutions to common tasks, detailed descriptions of specific features,and tips and tricks to help you develop data warehouses.

The Informatica Webzineis a password-protected site that you can access through theCustomer Portal. The Customer Portal has an online registration form for login accounts toits webzine and web support. To register for an account, go to http://my.informatica.com.

If you have any questions, please email [email protected].

Visiting the Informatica Web Site

You can access Informaticas corporate web site at http://www.informatica.com. The sitecontains information about Informatica, its background, upcoming events, and locating yourclosest sales office. You will also find product information, as well as literature and partnerinformation. The services area of the site includes important information on technicalsupport, training and education, and implementation services.

Visiting the Informatica Developer Network

The Informatica Developer Network is a web-based forum for third-party softwaredevelopers. 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-


27/150

Preface xxvii

The site contains information on how to create, market, and support customer-oriented add-on solutions based on Informaticas interoperability interfaces.

Obtaining Technical Support

There are many ways to access Informatica technical support. You can call or email yournearest Technical Support Center listed below or you can use our WebSupport Service.

WebSupport requires a user name and password. You can request a user name and password athttp://my.informatica.com.

North America / South America Africa / Asia / Australia / Europe

Informatica Corporation

2100 Seaport Blvd.

Redwood City, CA 94063

Phone: 866.563.6332 or 650.385.5800

Fax: 650.213.9489

Hours: 6 a.m. - 6 p.m. (PST/PDT)

email: [email protected]

Informatica Software Ltd.

6 Waltham Park

Waltham Road, White Waltham

Maidenhead, Berkshire

SL6 3TN

Phone: 44 870 606 1525

Fax: +44 1628 511 411

Hours: 9 a.m. - 5:30 p.m. (GMT)

email: [email protected]

BelgiumPhone: +32 15 281 702

Hours: 9 a.m. - 5:30 p.m. (local time)

France

Phone: +33 1 41 38 92 26


Germany

Phone: +49 1805 702 702Hours: 9 a.m. - 5:30 p.m. (local time)

Netherlands

Phone: +31 306 082 089


Singapore

Phone: +65 322 8589

Hours: 9 a.m. - 5 p.m. (local time)

Switzerland

Phone: +41 800 81 80 70

Hours: 8 a.m. - 5 p.m. (local time)


28/150

xxviii Preface


29/150

1

C h a p t e r 1

Before You Begin

This chapter includes the following topics:

Overview, 2

Connecting to Databases, 4

Overview


30/150

2 Chapter 1 : Before You Beg in

Overview

In this Getting Startedguide, you will find multiple lessons that introduce you toPowerCenter, and how to use it to load transformed data into file and relational targets. The

lessons in this book are designed for beginners to PowerCenter.This tutorial walks you through the process of creating a data warehouse. The tutorial teachesyou how to:

Create users and groups.

Add source definitions to the repository.

Create targets and add their definitions to the repository.

Map data between sources and targets. Instruct the PowerCenter Server to write data to targets.

Monitor the PowerCenter Server as it writes data to targets.

In general, you can set your own pace for completing the tutorial. However, Informaticarecommends completing an entire lesson in one sitting, since each lesson builds on a sequenceof related tasks.

For additional information, case studies, and updates on using Informatica products, see theInformatica online journal, the Informatica Webzine. You can access the webzine athttp://my.Informatica.com.

Getting Started

Before you can begin the lessons, read Product Overview in the Installation andConfiguration Guide. The product overview explains the different components that work

together to extract, transform, and load data.

Also, your administrator must install and configure the PowerCenter Client applications andthe PowerCenter Server. Verify your administrator has completed the following steps:

Install PowerCenter client applications. You will use the PowerCenter Client applicationsto manage users, define sources and targets, build mappings and mapplets with thetransformation logic, and create sessions and workflows to run the mapping logic.

Install the Repository Server. The Informatica Repository Server manages connections tothe repository from client applications. It inserts, updates, and fetches objects from therepository database tables.

Create a repository. The Informatica repository is at the center of the Informatica suite.When you create objects with the Informatica applications, you create a set of metadatatables within the repository database that the Informatica applications access. ThePowerCenter Client and Server access the repository to save and retrieve metadata.

Install the PowerCenter Server. The PowerCenter Server extracts the source data,performs the data transformation, and loads the transformed data into the targets.

Register the PowerCenter Server in the Workflow Manager. You can create workflows


31/150

Overview 3

once the administrator registers an PowerCenter Server.

For an overview on installing and configuring all the PowerCenter components, seeInstallation and Configuration Overview in the Installation and Configuration Guide.

You will also need the information necessary to connect to your source, target, and repositorydatabases. You can use the tables in Connecting to Databases on page 4 to enter theconnectivity information. Contact your administrator for the necessary information.

Using the PowerCenter Client in the Tutorial

The PowerCenter Client is comprised of applications that you use to manage the repository,design mappings and mapplets, create sessions and workflows to load the data, and monitor

workflow progress.

In this tutorial, you use the following applications and tools:

Repository Manager. Use the Repository Manager to create and administer the metadatarepository. In Lesson 1, you perform some tasks that you need to complete before you startthe other lessons in the book. You use the Repository Manager to create a repository userand group. You create a folder to store the metadata you create in the lessons.

Repository Server Administration Console. Use the Repository Server Administrationconsole to administer the Repository Servers and repositories.

Designer. Use the Designer to create mappings that contain transformation instructionsfor the PowerCenter Server. Before you can create mappings, you must add source andtarget definitions to the repository. In this tutorial, you use the following tools in theDesigner:

Source Analyzer. Import or create source definitions. In Lesson 2, you use the Designerto create source definitions.

Warehouse Designer. Import or create target definitions. In Lesson 2, you use theDesigner to create target definitions. You also create tables in the target database basedon the target definitions.

Mapping Designer. Create mappings that the PowerCenter Server uses to extract,transform, and load data. In Lessons 3 to 5, you use the Mapping Designer to createmappings that extract data from sources and load it to a target.

Workflow Manager. Use the Workflow Manager to create and run workflows and tasks. Aworkflow is a set of instructions that describes how and when to run tasks related toextracting, transforming, and loading data. In Lessons 3 to 5, you use the WorkflowManager to create Session tasks to run the mappings you create, and workflows to run thesessions.

Workflow Monitor. Use the Workflow Monitor to monitor scheduled and runningworkflows for each PowerCenter Server. In Lessons 3 to 5, you run the workflows youcreate, and use the Workflow Monitor to monitor the workflow runs.

For more information on PowerCenter, see Product Overview in the Installation andConfiguration Guide.

Connecting to Databases


32/150


g

To use the lessons in this book, you need to connect to your source, target, and repositorydatabases. You can use the tables in this section to record the connectivity information you

need to connect to the databases. Contact your administrator if you need any connectioninformation listed below.

Use Table 1-1 to enter the information you need to connect to the repository as theAdministrator:

Note: Use the Administrator profile for the lessons Creating Repository Users and Groupson page 8 and Creating a Folder on page 14 only. For all other lessons, you will use the userprofile you create to login to the repository.

Use Table 1-2 to enter the information you need to connect to the repository in eachPowerCenter Client tool. Use the user profile you create in Creating a User on page 12:

You need to create an ODBC connection for your source and target databases, if not alreadycreated. For details, see Connecting to Databases from Windows in the Installation andConfiguration Guide.

Table 1-1. Administrator Repository Login

Repository

Repository Name

Repository Administrator Username

Repository Administrator Password

Repository Server Host Name

Repository Server Port Number

Table 1-2. Repository Login

Repository

Repository Name

Repository Username

Repository Password

Repository Server Host Name

Repository Server Port Number

Use Table 1-3 to enter the information you need to connect to your source and targetd t b fr m th D i n r


33/150

Connecting to Databases 5

databases from the Designer:

For more information about ODBC drivers, see Using ODBC in the Installation andConfiguration Guide.

Use Table 1-4 to enter the information you need to create database connections in theWorkflow Manager:

Table 1-5 lists the native connect string syntax to use for different database platforms:

Table 1-3. ODBC Data Source Information

Source Connection Target Connection

ODBC Data Source Name

Database Username

Database Password

Table 1-4. Workflow Manager Connectivity Information

Source Database Connection Object Target Database Connection Object

Database Type

Username

Password

Connect String

Code Page

Database Name

Server Name

Domain Name

Note: You may not need all properties in this table.

Table 1-5. Native Connect String Syntax for Database Platforms

Database Platform Native Connect String Example

IBM DB2 dbname mydatabase

Informix dbname@servername mydatabase@informix

Microsoft SQL Server servername@dbname sqlserver@mydatabase

Oracle dbname.world (same as TNSNAMES entry) oracle.world

Sybase servername@dbname sambrown@mydatabase

Teradata Teradata* ODBC_data_source_name or

ODBC_data_source_name@db_name or

ODBC_data_source_name@db_user_name

TeradataODBC

TeradataODBC@mydatabase

TeradataODBC@sambrown


34/150



35/150

7

C h a p t e r 2

Tutorial Lesson 1


Creating Repository Users and Groups, 8

Creating a Folder, 14

Creating Source Tables, 16

What Comes Next, 19

Creating Repository Users and Groups


36/150

8 Chapter 2: Tutorial Lesson 1

You can create a repository user profile for everyone working in the repository, each with aseparate user name and password. You can also create user groups and assign each user to one

or more groups. Then, grant repository privileges to each group, so users in the group canperform tasks within the repository (such as use the Designer or create workflows).

The repository user profile is not the same as the database user profile. While a particular usermight not have access to a database as a databaseuser, that same person can have privileges toa repository in the database as a repositoryuser.

Informatica tools include two types of security:

Privileges. Repository-wide security that controls which task or set of tasks a single user orgroup of users can access.

Permissions. Security assigned to individual folders within the repository.

PowerCenter uses the following privileges:

Use Designer

Browse Repository

Use Repository Manager

Use Workflow Manager

Workflow Operator

Administer Repository

Administer Server

Super User

You can perform various tasks for each privilege. For a list of the tasks you can perform witheach privilege, see Repository Security in the Repository Guide.

Privileges depend on your group membership. Every repository user belongs to at least onegroup. For example, the user who administers the repository belongs to the Administratorsgroup. By default, you receive the privileges assigned to your group. While it is most commonto assign privileges by group, the repository administrator, who has either the Super User orAdminister Repository privilege, can also grant privileges to individual users.

As an administrator, you can perform the following tasks: Create groups.

Assign privileges to groups.

Create users and assign them to groups.

In the following steps, you will perform the following tasks:

1. Connect to the repository as an Administrator. If necessary, ask your administrator for

the user name and password. Otherwise, ask your administrator to complete the lessonsin this chapter for you.

2. Create the TUTORIAL group. To do this, you need to log in to the repository as theAdministrator.


37/150

Creating Repository Users and Groups 9

3. Assign privileges to the TUTORIAL group.

4. Create a new user.

Connecting to the Repository

To perform the following tasks, you need to connect to the repository. If you are alreadyconnected to the repository, disconnect and connect again to log in as the Administrator.

Note: Use the Administrator user name and password you entered in Table 1-1 on page 4.Otherwise, ask your administrator to perform the tasks in this chapter for you.

To connect to the repository:

1. Launch the Repository Manager.

A list of all repositories appears in the Navigator.

2. Double-click the repository you use in the tutorial.

3. Enter the repository user name and password for the Administrator user. Click Connect.

The dialog box expands to enter additional information.

4. Enter the host name and port number needed to connect to the repository database.

5. Click Connect.

You are now connected to the repository as the Administrator user.

Creating a GroupIn the following steps, you will create a new group.

To create the TUTORIAL group:

1. Select the repository in the Navigator, and choose Security-Manage Users and Privileges.

The Manage Users and privileges dialog box contains tabs for users, groups, andprivileges that lists all existing users, groups, and privileges in the repository.

2. Select the Groups tab.

The Groups tab includes the default groups, Administrators and Public. You cannot editor remove these groups.

Note: The Groups tab may display more groups if your administrator created additionalgroups.


38/150


3. Click Add.

The New Group dialog box appears.

4. Type TUTORIAL for the name of the new group and Tutorial as the description. ClickOK.

The new TUTORIAL group appears on the Groups tab.

5. Click OK to return to the Repository Manager.

Assigning Privileges to a Group

The next step is to grant privileges to the TUTORIAL group


39/150


The next step is to grant privileges to the TUTORIAL group.

To assign privileges to the TUTORIAL group:

1. In the Manage Users and privileges dialog box, select the Privileges tab. The privilegescurrently assigned to users and groups are displayed.

The TUTORIAL group has the following default privileges:

Browse Repository

Use Designer

Use Workflow Manager Use Repository Manager

Users in the TUTORIAL group now can create workflows in any folder for which theyhave read permission.

Creating a User

The final step is to create a new user and add this user to the TUTORIAL group You will use


40/150


The final step is to create a new user and add this user to the TUTORIAL group. You will usethis profile throughout the rest of this tutorial.

To create a new user:

1. In the Manage Users and privileges dialog box, select the Users tab.

The dialog box lists all the users in the repository.

2. Click Add.

3. In the New User dialog box, enter your name as the user name.

4. Enter contact information, such as a phone number, if needed.

5. In both the Password and Confirm Password fields, enter your password.

6. Click the Group Memberships tab.

7. Select TUTORIAL and click Add.


41/150


8. Click OK.

You now have all the privileges associated with the TUTORIAL group.

What Comes Next

In the next section, you will create a tutorial repository folder. You will save all objects youcreate in these lessons in the tutorial folder.

Creating a Folder


42/150


Folders provide a way to organize and store all metadata in the repository, includingmappings, schemas, and sessions. Folders are designed to be flexible to help you organize your

repository logically. Each folder has a set of properties you can configure to define how usersaccess the folder. For example, you can create a folder that allows all repository users to seeobjects within the folder, but not to edit them.

Folder Permissions

Permissions allow repository users to per form tasks within a folder. With folder permissions,you can control user access to the folder, and the tasks you permit them to perform.

Folder permissions work closely with repository privileges. Privileges grant access to specifictasks while permissions grant access to specific folders with read, write, and execute access.However, any user with the Super User privilege can perform all tasks across all folders in therepository. Folders have the following types of permissions:

Read permission. Allows you to view the folder as well as objects in the folder.

Write permission. Allows you to create or edit objects in the folder.

Execute permission. Allows you to run or schedule workflows in the folder.

Folders in this Tutorial

For this tutorial, you will create a single folder, Tutorial_yourname. You will add metadata tothis folder about orders, customers, and products.

To create a new folder:

1. In the Repository Manager, choose Folder-Create.

2. Enter Tutorial_yournameasthe name of the folder.

3. Select your user name as the owner of the folder.

Because your user name is a member of the Public group, the Owners Group defaults tothat group. Users who belong to more than one group must select a group from the list.

4. Select TUTORIAL as the Group for the folder.


43/150

Creating a Folder 15

5. Click OK to create the folder.

The new folder now appears as part of your repository.

6. Exit the Repository Manager.

Creating Source Tables


44/150


With most data warehouses, you already have existing source tables or flat files. Before youcontinue with the other lessons in this book, you need to create the source tables in the

database. In this lesson, you run an SQL script in the Warehouse Designer to create samplesource tables. The SQL script creates sources with 7-bit ASCII table names and data.

When you run the SQL script, you create the following source tables:

CUSTOMERS

DEPARTMENT

DISTRIBUTORS

EMPLOYEES ITEMS

ITEMS_IN_PROMOTIONS

JOBS

MANUFACTURERS

ORDERS

ORDER_ITEMS PROMOTIONS

STORES

Generally, you use the Warehouse Designer to create target tables in the target database. TheWarehouse Designer generates SQL based on the definitions in the workspace. However, wewill use this feature to generate the source tutorial tables from the tutorial SQL scripts thatship with the product.

To create the sample source tables:

1. Launch the Designer, double-click the icon for your repository, and log into therepository.

Use your user profile to open the connection.

2. Double-click the Tutorial_yournamefolder.

3. Choose Tools-Warehouse Designer to switch to the Warehouse Designer.

4. Choose Targets-Generate/Execute SQL.


45/150

Creating Source Tables 17

The Database Object Generation dialog box gives you several options for creating tables.5. Click the Connect button to connect to the source database.

6. Select the ODBC data source you created for connecting to the source database. Use theinformation you entered in Table 1-3 on page 5.

7. Enter the database user name and password and click the Connect button.

You now have an open connection to the source database. You know that you are

connected when the Disconnect button displays and the ODBC name of the sourcedatabase appears in the dialog box.

8. Make sure the Output window is open at the bottom of the Designer.

If it is not open, choose View-Output.

9. Click the browse button to find the SQL file. The SQL file is installed in the Tutorialfolder in the PowerCenter Client installation directory.

10. Select the SQL file appropriate to the source database platform you are using. ClickOpen.

Alternatively, you can enter the file name and path of the SQL file.

Platform File

Informix SMPL_INF.SQL

Microsof t SQL Server SMPL_MS.SQL

Oracle SMPL_ORA.SQL

Sybase SQL Server SMPL_SYB.SQL

DB2 SMPL_DB2.SQL

Teradata SMPL_TERA_SQL

11. Click Execute SQL file.

The database now executes the SQL script to create the sample source database objectsand to insert values into the source tables. While the script is running, the Output


46/150


and to insert values into the source tables. While the script is running, the Outputwindow displays the progress.

12.

When the script completes, click Disconnect, and then click Close.

What Comes Next

I h l ill d fi i i i h i b d h


47/150

What Comes Next 19

In the next lesson, you will create source definitions in the repository based on the sourcetables you just created. You will also create target definitions and create tables in the target

database based on the target definitions.


48/150



49/150

21

C h a p t e r 3

Tutorial Lesson 2


Creating Source Definitions, 22

Creating Target Definitions and Target Tables, 27 What Comes Next, 31

Creating Source Definitions

Now that you have added the source tables containing sample data, you are ready to create the


50/150


Now that you have added the source tables containing sample data, you are ready to create thesource definitions in the repository. The repository contains a description of source tables, notthe actual data contained in them. After you add these source definitions to the repository,you can use them in a mapping.

To import the sample source definitions:

1. In the Designer, choose Tools-Source Analyzer to open the Source Analyzer.

2. Double-click the tutorial folder to view its contents.

Every folder contains nodes for sources, targets, schemas, mappings, mapplets, and

reusable transformations.

3. Choose Sources-Import from Database.

4. Select the ODBC data source to access the database containing the source tables.

5. Enter the user name and password to connect to this database. Also, enter the name ofthe source table owner, if necessary.

Use the database connection information you entered in Table 1-3 on page 5.

In Oracle, the owner name is the same as the user name. Make sure that the owner nameis in all caps (for example, JDOE).

6. Click Connect.

7. In the Select tables list, expand the database owner and the TABLES heading.

If you click the All button, you can see all tables in the source database.

You should now see a list of all the tables you created by running the SQL script inaddition to any tables already in the database.

8. Select the following tables:


51/150

Creating Source Definitions 23

CUSTOMERS

DEPARTMENT DISTRIBUTORS

EMPLOYEES

ITEMS

ITEMS_IN_PROMOTIONS

JOBS

MANUFACTURERS

ORDERS

ORDER_ITEMS

PROMOTIONS

STORES

Note: Database objects created in Informix databases have shorter names than thosecreated in other types of databases. For example, the name of the tableITEMS_IN_PROMOTIONS, created in these scripts, is shortened toITEMS_IN_PROMO.

Tip: Hold down the Ctrl key to select multiple tables. Or, hold down the Shift key toselect a block of tables. You may need to scroll down the list of tables to select all tables.

9. Click OK to import the source definitions into the repository.

The Designer displays the newly imported sources in the workspace. You can chooseLayout-Scale to Fit to fit all the definitions in the workspace.


52/150


A new database definition (DBD) node appears under the Sources node in the tutorialfolder. This new entry has the same name as the ODBC data source to access the sourcesyou just imported. If you double-click the DBD node, the list of all the imported sourcesdisplays.

Viewing Source Definitions

You can view details for each source definition.

To view a source definition:

1. Double-click the title bar of the source definition for the EMPLOYEES table to open theEMPLOYEES source definition.

The Edit Tables dialog box opens and displays all the properties of this source definition.The Table tab shows the name of the table, business name, owner name, and the databasetype. You can add a comment in the Description section.

2. Click the Columns tab.

The Columns tab displays the column descriptions for the source table.

Note: The source definition should match the structure of the source table. Therefore,Informatica recommends that you do not modify source column definitions after youimport them.


53/150

Creating Source Definitions 25

3. Click the Metadata Extensions tab.

Metadata extensions allow you to extend the metadata stored in the repository byassociating information with individual repository objects. For example, you may wish tostore your contact information, such as name or email address, with the sources youcreate. You associate information with repository objects using metadata extensions.

You will create some user-defined metadata extensions that define the date you create thesource definition and the name of the person who created the source definition.

4. Click the Add button twice to add two new metadata extensions.

Two new rows appear.

5. Edit the new rows so the Metadata Extensions tab looks like the following graphic:

Add Button


54/150


Note: Use your name for the CreatorName value and todays date for theSourceCreationDate value.

6. Click Apply.

7. Click OK to close the dialog box.

8. Choose Repository-Save to save your changes to the repository.

Creating Target Definitions and Target Tables

You can import target definitions from existing target tables, or you can create the definitionsand then generate and run the SQL to create the target tables In this lesson ou ill create a


55/150

Creati ng Target Defin ition s and Target Tables 27

and then generate and run the SQL to create the target tables. In this lesson, you will create atarget definition in the Warehouse Designer, and then create a target table based on thedefinition.

Creating Target Definitions

The next step is to create the metadata for the target tables in the repository. The actual tablethat the target definition describes does not exist yet.

Target definitions define the structure of tables in the target database, or the structure of filetargets the PowerCenter Server creates when you run a workflow. If you add a targetdefinition to the repository that does not exist in a relational database, you need to createtarget tables in your target database. You do this by generating and executing the necessarySQL code within the Warehouse Designer.

In the following steps, you will copy the EMPLOYEES source definition into the WarehouseDesigner to create the target definition. Then, you will modify the target definition bydeleting and adding columns to create the definition you want.

To create the T_EMPLOYEES target definition:

1. In the Designer, switch to the Warehouse Designer.

2. Click and drag the EMPLOYEES source definition from the Navigator to the WarehouseDesigner workspace.

The Designer creates a new target definition, EMPLOYEES, with the same column

definitions as the EMPLOYEES source definition and the same database type.Next, you will modify the target column definitions.

3. Double-click the EMPLOYEES target definition by to open it.

The Edit Tables dialog box appears.

4. Click Rename and name the target definition T_EMPLOYEES.

Note: If you need to change the database type for the target definition, you can select the

correct database type when you edit the target definition.

5. Click the Columns tab.

The target column definitions are the same as the EMPLOYEES source definition.

Add Button


56/150


6. Select the JOB_ID column and click the delete button.

7. Delete the following columns:

ADDRESS1

ADDRESS2

CITY

STATE

POSTAL_CODE

HOME_PHONE

EMAIL

Delete Button

When you finish, the target definition should look similar to the following targetdefinition:


57/150

Creati ng Target Defin ition s and Target Tables 29

Note that the EMPLOYEE_ID column is a primary key. The primary key cannot accept

null values. The Designer automatically selects Not Null and disables the Not Nulloption. You now have a column ready to receive data from the EMPLOYEE_ID columnin the EMPLOYEES source table.

Note: If you want to add a business name for any column, scroll to the right and enter it.

8. Click OK to save your changes and close the dialog box.

9. Choose Repository-Save.

Creating Target Tables

You can use the Warehouse Designer to run an existing SQL script to create target tables.

Note: When you use the Warehouse Designer to generate SQL, you can choose to drop thetable in the database before creating it. To do this, select the Drop Table option. If the targetdatabase already contains tables, make sure it does not contain a table with the same name asthe table you plan to create. If the table exists in the database, you lose the existing table anddata.

To create the target T_EMPLOYEES table:

1. In the workspace, select the T_EMPLOYEES target definition.

2. Choose Targets-Generate/Execute SQL.

The dialog box to run the SQL script appears.

3. In the Filename field, enter the following text:

C:\[your installation directory]\MKT_EMP.SQL

If you installed the client software in a different location, enter the appropriate driveletter and directory.


58/150


4. If you are connected to the source database fro

informatica-getting started

Documents