PC 811 InstallationGuide

Installation and Configuration
Guide
Informatica PowerCenter®
(Version 8.1.1)
Informatica PowerCenter Installation and Configuration Guide
Version 8.1.1
April 2007
Copyright (c) 1998–2007 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, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerMart, SuperGlue, Metadata Manager, Informatica Data
Quality and Informatica Data Explorer 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 and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies,
1999-2002. All rights reserved. Copyright © Sun Microsystems. All Rights Reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal
Technology Corp. All Rights Reserved.
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-2004, 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 expressed 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.
Table of Contents
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv
Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Visiting Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Visiting the Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . xxv
Obtaining Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Part I: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Chapter 1: PowerCenter Installation Components . . . . . . . . . . . . . . . 3

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Installation Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
PowerCenter Standard/Advanced Edition 32 bit/64 bit DVD . . . . . . . . . . 5
PowerCenter Documentation DVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
PowerCenter License Key CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
PowerCenter Service Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
PowerCenter Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Data Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Metadata Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
PowerCenter Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
PowerCenter Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Administrative Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
PowerCenter Repository Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Data Analyzer Data Profiling Reports . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Chapter 2: Installation and Upgrade Overview . . . . . . . . . . . . . . . . . 15

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
iii
Single or Multiple Machine Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Single Machine Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Multiple Machine Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Installing PowerCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
PowerCenter Complete Installation Steps . . . . . . . . . . . . . . . . . . . . . . . 19
PowerCenter Services Custom Installation Steps . . . . . . . . . . . . . . . . . . 20
Data Analyzer Custom Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . 21
Metadata Manager Custom Installation Steps . . . . . . . . . . . . . . . . . . . . 22
Upgrading PowerCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Compatible PowerCenter Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Memory and CPU Resource Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
PowerCenter Version 6.x / 7.x Upgrade Steps . . . . . . . . . . . . . . . . . . . . 24
PowerCenter Version 8.0 Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . 25
PowerCenter Version 8.1 Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . 27
Upgrading Data Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Upgrading Metadata Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Metadata Manager Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 3: PowerCenter Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . 33

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Web Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Database Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
JBoss Application Server Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . 41
IBM WebSphere Application Server Prerequisites . . . . . . . . . . . . . . . . . 41
BEA WebLogic Server Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Third-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Working with 32-bit and 64-bit Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Running PowerCenter on 32-bit and 64-bit Platforms . . . . . . . . . . . . . . 46
Migrating to a 64-bit Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Chapter 4: Before You Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Pre-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Step 1. Create Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
PowerCenter Domain Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
iv Table of Contents
Repository on Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
PowerCenter Repository on IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . 53
PowerCenter Repository on Sybase ASE . . . . . . . . . . . . . . . . . . . . . . . . 53
Data Profiling Warehouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Data Analyzer Repository on Sybase ASE . . . . . . . . . . . . . . . . . . . . . . . 54
Data Analyzer Repository on Microsoft SQL Server . . . . . . . . . . . . . . . 54
Data Analyzer and Metadata Manager Repository on Sybase ASE . . . . . . 54
Metadata Manager Repository and Source Repository on IBM DB2 . . . . 55
Step 2. Create Database User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Rules and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Step 3. Install Database Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Step 4. Create a System User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Windows User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
UNIX User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Step 5. Configure Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Configuring Environment Variables on UNIX . . . . . . . . . . . . . . . . . . . 59
Database Client Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . 60
Library Path Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Locale Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Java Component Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
libstdc++.so.5 Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
X Window Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
PowerCenter Services Environment Variables . . . . . . . . . . . . . . . . . . . . 63
Testing the Database Connection on UNIX . . . . . . . . . . . . . . . . . . . . . 65
Step 6. Establish Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Step 7. Verify License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Step 8. Configure Web Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Step 9. Install Languages (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Step 10. Install the Application Server (Optional) . . . . . . . . . . . . . . . . . . . . 70
JBoss Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
BEA WebLogic Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
IBM WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Step 11. Install X Virtual Frame Buffer (Optional) . . . . . . . . . . . . . . . . . . . 73
HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
AIX and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Step 12. Prepare for Installation from a Hard Disk (Optional) . . . . . . . . . . . 74
Table of Contents v
Chapter 5: Before You Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
PowerCenter Version 6.x/7.x Pre-Upgrade Steps . . . . . . . . . . . . . . . . . . . . . 79
Step 1. Establish the PowerCenter Installation Environment . . . . . . . . . 79
Step 2. Configure Database Connectivity . . . . . . . . . . . . . . . . . . . . . . . 79
Step 3. Prepare the Repository for Upgrade . . . . . . . . . . . . . . . . . . . . . . 80
Step 4. Prepare the Informix and Teradata Data Profiling Warehouse . . . 80
Step 5. Back Up and Copy PowerCenter Configuration Files . . . . . . . . . 80
Step 6. Back Up and Uninstall Web Services Provider . . . . . . . . . . . . . . 80
PowerCenter Version 8.0 Pre-Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . 82
Step 1. Prepare the Repository for Upgrade . . . . . . . . . . . . . . . . . . . . . . 82
Step 2. Note Domain Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Step 3. Stop Informatica Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Step 4. Unset Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Step 5. Back Up Metadata Configuration Files . . . . . . . . . . . . . . . . . . . 83
PowerCenter 8.1 Pre-Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Step 1. Back Up Domain Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Step 2. Back Up Configuration Metadata . . . . . . . . . . . . . . . . . . . . . . . 85
Step 3. Stop Informatica Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Preparing the Repository for Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Step 1. Set Up the PowerCenter Repository Database . . . . . . . . . . . . . . . 86
Step 2. Optimize Upgrade Performance . . . . . . . . . . . . . . . . . . . . . . . . . 86
Step 3. Prepare Informix, Teradata, or Oracle 8 Repositories . . . . . . . . . 87
Step 4. Create a Copy of a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Backing Up and Copying Configuration Files . . . . . . . . . . . . . . . . . . . . . . . 89
Step 1. Create a PowerCenter Server Configuration File . . . . . . . . . . . . . 89
Step 2. Back Up the Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . 91
Step 3. Verify the Character Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Step 4. Copy the Configuration Files to the Domain . . . . . . . . . . . . . . . 92
Data Analyzer Pre-Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Step 1. Set Up the Data Analyzer Repository Database . . . . . . . . . . . . . . 93
Step 2. Back Up the Data Analyzer Repository . . . . . . . . . . . . . . . . . . . 93
Step 3. Restore the Data Analyzer Repository . . . . . . . . . . . . . . . . . . . . 93
Step 4. Copy Customized Files and Shared Documents . . . . . . . . . . . . . 94
Metadata Manager Pre-Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Step 1. Set Up the Repository Databases . . . . . . . . . . . . . . . . . . . . . . . . 96
Step 2. Copy the Metadata Manager Repository . . . . . . . . . . . . . . . . . . 96
vi Table of Contents
Step 3. Back Up Existing Parameter Files . . . . . . . . . . . . . . . . . . . . . . . 96
Step 4. Note Information for the Business Objects XConnect . . . . . . . . 97
Part II: PowerCenter Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Chapter 6: PowerCenter Complete Installation in Graphical

Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Installing PowerCenter Standard Edition . . . . . . . . . . . . . . . . . . . . . . . . . 103
Installing PowerCenter Advanced Edition . . . . . . . . . . . . . . . . . . . . . . . . . 128
Chapter 7: PowerCenter Custom Installation in Graphical

Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Installing PowerCenter Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Upgrading from PowerCenter 8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Installing Data Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Installing Metadata Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Chapter 8: PowerCenter Complete Installation in Console

Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Rules and Guidelines for Using Console Mode . . . . . . . . . . . . . . . . . . 212
Installing PowerCenter Standard Edition . . . . . . . . . . . . . . . . . . . . . . . . . 213
Installing PowerCenter Advanced Edition . . . . . . . . . . . . . . . . . . . . . . . . . 224
Chapter 9: PowerCenter Custom Installation in Console Mode . . . 237

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Installing PowerCenter Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Upgrading from PowerCenter 8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Installing Data Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Installing Metadata Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Chapter 10: PowerCenter Client Installation . . . . . . . . . . . . . . . . . . 265

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Table of Contents vii

Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Running the Complete Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . 267
Running the Custom Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Running a Silent Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Step 1. Create the Properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Step 2. Run the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Chapter 11: PowerCenter Reports Installation . . . . . . . . . . . . . . . . . 281

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Installation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Installing PowerCenter Reports in Graphical Mode . . . . . . . . . . . . . . . . . . 284
Installing PowerCenter Reports in Console Mode . . . . . . . . . . . . . . . . . . . 288
Chapter 12: Documentation Installation . . . . . . . . . . . . . . . . . . . . . . 291

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Installing from the Hard Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Installing PowerCenter Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Viewing PowerCenter Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Updating PowerCenter Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Updating PowerCenter Client Help . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Updating Administration Console Help . . . . . . . . . . . . . . . . . . . . . . . 296
Installing the PowerCenter Web-Based HTML Help . . . . . . . . . . . . . . . . . 297
Chapter 13: PowerCenter Utilities Installation . . . . . . . . . . . . . . . . . 299

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
PowerCenter Command Line Programs and Utilities . . . . . . . . . . . . . . . . . 301
Rules and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Data Analyzer Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Ear Repackager Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Import Export Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
License Update Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
PowerCenter Integration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Repository Backup Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Data Analyzer Repository Upgrade Utility . . . . . . . . . . . . . . . . . . . . . . 309
Update System Accounts Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Metadata Manager Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
viii Table of Contents

Ear Repackager Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
License Update Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Repository Backup Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Update System Accounts Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Chapter 14: Informatica Development Platform Installation . . . . . . 315

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Installing the Informatica Development Platform . . . . . . . . . . . . . . . . . . . 317
Installation Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Chapter 15: After You Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Configuring Informatica Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Configuring Application Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Creating and Configuring the Repository Service . . . . . . . . . . . . . . . . 328
Creating and Configuring the Integration Service . . . . . . . . . . . . . . . . 329
Configuring the Metadata Manager Scheduler Service . . . . . . . . . . . . . . . . 330
Creating a Data Profiling Warehouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Step 1. Create the Data Profiling Warehouse . . . . . . . . . . . . . . . . . . . . 331
Step 2. Create the Data Profiling Warehouse Views
for Data Analyzer (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Step 3. Configure Connectivity to the Data Profiling Warehouse . . . . . 333
Step 4. Configure a Data Source and Data Connector
for Data Analyzer (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Configuring the PowerCenter Integration Utility for WebSphere . . . . . . . . 334
Step 1. Configure the notifyias.ear File . . . . . . . . . . . . . . . . . . . . . . . . 334
Step 2. Update the notifyias.properties File . . . . . . . . . . . . . . . . . . . . . 336
Updating a Data Analyzer or Metadata Manager License . . . . . . . . . . . . . . 337
Configuring Microsoft SQL Server for a Data Analyzer Repository . . . . . . . 338
Setting Up the PowerCenter Repository Reports . . . . . . . . . . . . . . . . . . . . 339
Step 1. Create a Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Step 2. Add the Data Source to a Data Connector . . . . . . . . . . . . . . . . 341
Step 3. Set Up Schedules for Cached Reports . . . . . . . . . . . . . . . . . . . 345
Switching PowerCenter Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Setting Up the Data Analyzer Data Profiling Reports . . . . . . . . . . . . . . . . . 351
Step 1. Configure a Data Source for the Data Profiling Warehouse . . . . 351
Step 2. Create a Data Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Step 3. Add a Data Profiling Data Source to a Data Connector . . . . . . 354
Table of Contents ix
Configuring INFA_HOME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Chapter 16: Troubleshooting a PowerCenter Installation . . . . . . . . 359

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Troubleshooting Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Installer Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Installation Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Service Manager Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Services Log Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Troubleshooting Domains and Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Creating the Domain Configuration Database . . . . . . . . . . . . . . . . . . . 366
Creating or Joining a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Starting Informatica Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Pinging the Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Adding a License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Troubleshooting Application Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Creating and Enabling a Repository Service . . . . . . . . . . . . . . . . . . . . 369
Creating and Restoring Repository Content . . . . . . . . . . . . . . . . . . . . 370
Creating and Enabling an Integration Service . . . . . . . . . . . . . . . . . . . 371
Troubleshooting Data Analyzer and Metadata Manager . . . . . . . . . . . . . . . 372
Creating a Data Analyzer Repository . . . . . . . . . . . . . . . . . . . . . . . . . 372
Creating and Updating a Metadata Manager Repository . . . . . . . . . . . . 372
Switching Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Troubleshooting Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
JBoss Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
WebLogic Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Troubleshooting the PowerCenter Client . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Installer Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Chapter 17: Uninstalling PowerCenter . . . . . . . . . . . . . . . . . . . . . . . 385

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Uninstallation Rules and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Running the Uninstaller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Before You Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Uninstallation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Running the Uninstaller on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
x Table of Contents
Running the Uninstaller on Windows . . . . . . . . . . . . . . . . . . . . . . . . . 389
Complete Uninstallation in Graphical Mode . . . . . . . . . . . . . . . . . . . . . . . 390
Partial Uninstallation in Graphical Mode . . . . . . . . . . . . . . . . . . . . . . . . . 392
Uninstallation in Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Part III: Upgrading PowerCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Chapter 18: Upgrading PowerCenter . . . . . . . . . . . . . . . . . . . . . . . . 401

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
PowerCenter Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
PowerCenter Repository Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Using the Upgrade Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Validate Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Troubleshooting Configuration File Validation . . . . . . . . . . . . . . . . . . 407
Upgrade a Global Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Troubleshooting Creating and Enabling a Repository Service . . . . . . . . 411
Troubleshooting a Repository Upgrade . . . . . . . . . . . . . . . . . . . . . . . . 411
Upgrade a Local Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Upgrade the PowerCenter Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Troubleshooting Creating and Enabling an Integration Service . . . . . . 418
View Upgrade Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Upgrade Domain and Node Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Running Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Step 1. Upgrade Gateway Node Metadata . . . . . . . . . . . . . . . . . . . . . . 421
Step 2. Upgrade Domain Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Step 3. Upgrade Worker Node Metadata . . . . . . . . . . . . . . . . . . . . . . . 422
Upgrade the PowerCenter Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Upgrade the PowerCenter Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Upgrade Data Profiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Running Data Profiling Upgrade Scripts . . . . . . . . . . . . . . . . . . . . . . . 427
Step 1. Prepare the Data Profiling Warehouse . . . . . . . . . . . . . . . . . . . 428
Step 2. Upgrade the Data Profiling Warehouse . . . . . . . . . . . . . . . . . . 428
Step 3. Upgrade Schema and Views for Data Analyzer
Data Profiling Reports (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Step 4. Recreate the ODBC Connection to the Data Profiling
Warehouse (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Table of Contents xi
Chapter 19: Upgrading Data Analyzer . . . . . . . . . . . . . . . . . . . . . . . 431
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Run the Repository Upgrade Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Update Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Complete the Repository Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Increasing Transaction Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Chapter 20: Upgrading Metadata Manager . . . . . . . . . . . . . . . . . . . . 441

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Running the Metadata Manager Upgrade Utility on Windows . . . . . . . . . . 444
Running the Metadata Manager Upgrade Utility on UNIX . . . . . . . . . . . . . 449
Upgrading the Metadata Manager Client . . . . . . . . . . . . . . . . . . . . . . . . . . 453
Metadata Manager Client Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . 453
Chapter 21: After You Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
PowerCenter 6.x / 7.x Post-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 457
Step 1. Register Local Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Step 2. Configure Application Services . . . . . . . . . . . . . . . . . . . . . . . . 457
Step 3. Update Password Environment Variable . . . . . . . . . . . . . . . . . . 457
Step 4. Upgrade to a Unicode Repository . . . . . . . . . . . . . . . . . . . . . . 458
Step 5. Move PowerCenter Server Run-time Files . . . . . . . . . . . . . . . . 458
Step 6. Configure the Web Services Hub . . . . . . . . . . . . . . . . . . . . . . . 458
Step 7. Install Database Client Software . . . . . . . . . . . . . . . . . . . . . . . 459
PowerCenter 8.0 Post-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
Step 1. Reconfigure Environment Variables . . . . . . . . . . . . . . . . . . . . . 460
Step 2. Move Integration Service Run-time Files . . . . . . . . . . . . . . . . . 460
Step 3. Update Service Logs Directory . . . . . . . . . . . . . . . . . . . . . . . . 461
Step 4. Recreate Repository Service for Metadata Manager . . . . . . . . . . 461
Step 5. Install Database Client Software . . . . . . . . . . . . . . . . . . . . . . . 461
PowerCenter 8.1 Post-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Step 1. Restart Informatica Services . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Step 2. Update the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Step 3. Move Integration Service Run-time Files . . . . . . . . . . . . . . . . . 463
Data Analyzer Post-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Step 1. Update the Custom Color Schemes . . . . . . . . . . . . . . . . . . . . . 464
xii Table of Contents

Step 2. Update the Cached Reports . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Step 3. Update the Location of Shared Documents . . . . . . . . . . . . . . . 465
Step 4. Refresh the PowerCenter Table Definitions . . . . . . . . . . . . . . . 465
Step 5. Update Applications that Use the Data Analyzer SDK . . . . . . . 466
Metadata Manager Post-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Step 1. Refresh Metadata Manager Views . . . . . . . . . . . . . . . . . . . . . . 467
Step 2. Delete Obsolete Metadata Manager Objects . . . . . . . . . . . . . . . 468
Step 3. Import Metamodels for an IBM DB2 Repository . . . . . . . . . . . 469
Step 4. Update Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Part IV: Configuring Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Chapter 22: Understanding Connectivity . . . . . . . . . . . . . . . . . . . . . 473

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Connectivity Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
Domain Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Native Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Establishing Native Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Establishing ODBC Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
PowerCenter Client Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Connecting to the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Connecting to Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Connecting to the Integration Service . . . . . . . . . . . . . . . . . . . . . . . . 481
Repository Service Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Connecting from the PowerCenter Client . . . . . . . . . . . . . . . . . . . . . . 483
Integration Service Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
Connecting from the PowerCenter Client . . . . . . . . . . . . . . . . . . . . . . 484
Connecting to the Repository Service . . . . . . . . . . . . . . . . . . . . . . . . . 484
Data Analyzer and Metadata Manager Connectivity . . . . . . . . . . . . . . . . . . 486
Chapter 23: Connecting to Databases from Windows . . . . . . . . . . . 487

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Connecting to an IBM DB2 Universal Database . . . . . . . . . . . . . . . . . . . . 489
Configuring Native Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Table of Contents xiii

Configuring ODBC Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Connecting to an Informix Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Connecting to Microsoft Access and Microsoft Excel . . . . . . . . . . . . . . . . . 493
Connecting to a Microsoft SQL Server Database . . . . . . . . . . . . . . . . . . . . 494
Connecting to an Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Connecting to a Sybase ASE Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Connecting to a Teradata Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Chapter 24: Connecting to Databases from UNIX . . . . . . . . . . . . . . 503

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Connecting to Microsoft SQL Server on UNIX . . . . . . . . . . . . . . . . . . 504
Connecting to an IBM DB2 Universal Database . . . . . . . . . . . . . . . . . . . . 505
Connecting to an Informix Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
Connecting to an Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
Connecting to a Sybase ASE Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Connecting to a Teradata Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Connecting to an ODBC Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Sample odbc.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
Part V: Appendices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
xiv Table of Contents

Appendix A: Starting and Stopping Informatica Services . . . . . . . . 529
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Starting and Stopping Informatica Services on UNIX . . . . . . . . . . . . . . . . 531
Starting and Stopping Informatica Services on Windows . . . . . . . . . . . . . . 532
Stopping Informatica Services Using the Administration Console . . . . . 533
Appendix B: Starting and Stopping Application Servers . . . . . . . . 535

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Starting and Stopping Applications on JBoss Application Server . . . . . . . . . 537
Starting JBoss Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Stopping JBoss Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Starting and Stopping Applications on BEA WebLogic Server . . . . . . . . . . 540
Starting BEA WebLogic Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Stopping BEA WebLogic Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Starting and Stopping Applications on IBM WebSphere Application
Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
Starting IBM WebSphere Application Server . . . . . . . . . . . . . . . . . . . . 542
Stopping Applications on IBM WebSphere Application Server . . . . . . . 545
Appendix C: Logging in to the Administration Console . . . . . . . . . 547

Logging in to the Administration Console . . . . . . . . . . . . . . . . . . . . . . . . 548
Appendix D: ODBC Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549

Client ODBC Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
Integration Service ODBC Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Appendix E: JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553

Installed JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
JDBC Driver for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
Appendix F: LANG Environment Variable for Linux . . . . . . . . . . . . 557

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
Table of Contents xv
xvi Table of Contents
List of Figures
Figure 18-1. Upgrade Wizard - Upgrade Global Repository Page . . . . . . . . . . . . . . . . . . . . . 409
Figure 18-2. Upgrade Wizard - Upgrade Local Repository Page . . . . . . . . . . . . . . . . . . . . . . 413
Figure 18-3. Upgrade Wizard - Upgrade PowerCenter Server Page . . . . . . . . . . . . . . . . . . . . 416
Figure 18-4. Upgrade Wizard - Upgrade Summary Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Figure 22-1. PowerCenter Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Figure 22-2. PowerCenter Repository Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Figure 23-1. ODBC Microsoft SQL Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
List of Figures xvii

xviii List of Figures
List of Tables
Table 1-1. Installed PowerCenter Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .. 7
Table 1-2. PowerCenter Services Installation Directories . . . . . . . . . . . . . . . . . . . . . .. . .. . .. 8
Table 1-3. Installed Data Analyzer Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .. 9
Table 1-4. Installed Metadata Manager Components . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 11
Table 1-5. Installed Client Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 12
Table 2-1. PowerCenter Compatible Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 23
Table 3-1. PowerCenter Component Installation Prerequisites . . . . . . . . . . . . . . . . . .. . .. . . 34
Table 3-2. Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 35
Table 3-3. Database Requirements for PowerCenter Components . . . . . . . . . . . . . . . .. . .. . . 38
Table 3-4. JBoss Application Server Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 41
Table 3-5. IBM WebSphere Application Server Prerequisites . . . . . . . . . . . . . . . . . . .. . .. . . 41
Table 3-6. BEA WebLogic Server Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 42
Table 3-7. Third-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 43
Table 4-1. PowerCenter Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 59
Table 4-2. UNIX Database Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 60
Table 4-3. UNIX Library Path Environment Variable. . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 60
Table 4-4. AIX and HP-UX Library Path Environment Variables . . . . . . . . . . . . . . . .. . .. . . 62
Table 4-5. Port Numbers for PowerCenter Services . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 66
Table 4-6. Directories and Files Required for Installation . . . . . . . . . . . . . . . . . . . . . .. . .. . . 74
Table 5-1. pmserverexportreg Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 90
Table 5-2. Data Analyzer Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 94
Table 6-1. PowerCenter Repository Information . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . 122
Table 6-2. WebSphere Application Server Security and Repository Authentication . . . .. . .. . 125
Table 6-3. Data Analyzer Repository Information . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . 126
Table 6-7. Metadata Manager Repository Information . . . . . . . . . . . . . . . . . . . . . . . .. . .. . 151
Table 7-6. Metadata Manager Repository Information . . . . . . . . . . . . . . . . . . . . . . . .. . .. . 209
Table 8-1. JBoss Application Server Default Port Values . . . . . . . . . . . . . . . . . . . . . . .. . .. . 215
Table 8-5. JBoss Application Server Default Port Values . . . . . . . . . . . . . . . . . . . . . . .. . .. . 226
List of Tables xix

Table 8-7. WebSphere Application Server Security and Repository Authentication. . . .. . .. . .233
Table 8-8. Data Analyzer Repository Information . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .234
Table 8-9. Metadata Manager Repository Information . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .235
Table 9-1. PowerCenter Repository Information . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .244
Table 9-2. JBoss Application Server Default Port Values . . . . . . . . . . . . . . . . . . . . . .. . .. . .250
Table 9-4. Data Analyzer Repository Information . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .254
Table 9-5. JBoss Application Server Default Port Values . . . . . . . . . . . . . . . . . . . . . .. . .. . .257
Table 9-6. PowerCenter Repository Information . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .260
Table 9-8. Metadata Manager Repository Information . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .263
Table 10-1. Silent Installation Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .278
Table 13-1. PowerCenter Command Line Programs and Utilities . . . . . . . . . . . . . . . .. . .. . .301
Table 13-2. Data Analyzer Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .302
Table 13-3. EAR Repackager Utility Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .303
Table 13-4. Import Export Utility Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .303
Table 13-5. License Update Utility Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .304
Table 13-6. Repository Backup Utility Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .309
Table 13-7. Repository Upgrade Utility Variables . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .309
Table 13-8. Update System Accounts Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .310
Table 13-9. Metadata Manager Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .311
Table 13-10. EAR Repackager Utility Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .312
Table 13-11. License Update Utility Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .312
Table 13-12. Repository Backup Utility Variables . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .313
Table 13-13. Update System Accounts Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .314
Table 15-1. Scripts for Creating a Data Profiling Warehouse . . . . . . . . . . . . . . . . . . .. . .. . .331
Table 15-2. Scripts for Creating the Data Profiling Warehouse Views . . . . . . . . . . . . .. . .. . .332
Table 15-3. PowerCenter Repository Reports Cached Report Schedules . . . . . . . . . . .. . .. . .345
Table 15-4. Data Connector Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .353
Table 16-1. Debug Log File Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .362
Table 16-2. Summary Log File Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .363
Table 16-3. Installation Log Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .364
Table 16-4. WebSphere Application Server Log Files . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .375
Table 17-1. PowerCenter Uninstallation Directories . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .388
Table 17-2. Uninstallation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .396
Table 18-1. PowerCenter Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .402
Table 18-2. PowerCenter 7.x to PowerCenter 8.1.1 Repository Size Increase . . . . . . . .. . .. . .403
Table 18-3. Required Configuration File Parameters . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .408
Table 18-4. Upgrade Global Repository Options . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .410
Table 18-5. Upgrade Local Repository Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .414
Table 18-6. Integration Service Upgrade Options . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .417
Table 18-7. upgradeGatewayNode Options and Arguments . . . . . . . . . . . . . . . . . . . .. . .. . .421
Table 18-8. upgradeDomain Options and Arguments . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . .422
xx List of Tables
Table 18-9. upgradeWorkerNode Option and Argument . . . . . . . . . . . . . . . . . . . . . . . . .. . 423
Table 18-10. Procedure for Upgrading a Data Profiling Warehouse to PowerCenter 8.1.1 .. . 427
Table 18-11. Scripts for Upgrading the Data Profiling Warehouse to PowerCenter 8.1.1 . .. . 428
Table 18-12. Scripts for Upgrading the Data Profiling Warehouse Schema and Views . . . .. . 429
Table 22-1. Drivers Used by PowerCenter Components . . . . . . . . . . . . . . . . . . . . . . . . . .. . 475
Table 22-2. Native Connect String Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 478
Table 22-3. Recommended Database ODBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 480
Table 22-4. PowerCenter Client Connectivity Requirements . . . . . . . . . . . . . . . . . . . . . .. . 481
Table 22-5. Repository Service Connectivity Requirements . . . . . . . . . . . . . . . . . . . . . . . .. . 483
Table 22-6. Integration Service Connectivity Requirements . . . . . . . . . . . . . . . . . . . . . . .. . 484
Table D-1. PowerCenter Client ODBC Function Calls . . . . . . . . . . . . . . . . . . . . . . . . . .. . 550
Table D-2. Integration Service ODBC Function Calls . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 552
Table E-1. JDBC Drivers Installed for Supported Databases . . . . . . . . . . . . . . . . . . . . . . .. . 554
Table E-2. JDBC Connection String Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 555
Table F-1. Valid Values for the LANG Environment Variable for Linux Machines . . . . . . .. . 558
List of Tables xxi

xxii List of Tables
Preface
Welcome to PowerCenter Standard and Advanced Edition. With these PowerCenter editions,
Informatica extends the definition of the base enterprise data integration platform to include
additional, key capabilities such as metadata analysis (Metadata Manager), data-ready
reporting (Data Analyzer), server grid, and team-based development to enable comprehensive
end to end data integration solutions.
The PowerCenter repository coordinates and drives a variety of core functions, including
extracting, transforming, loading, and managing data. The Integration Service can extract
large volumes of data from multiple platforms, handle complex transformations on the data,
and support high-speed loads. PowerCenter can simplify and accelerate the process of
building a comprehensive data warehouse from disparate data sources.
Data Analyzer makes accessing, analyzing, and sharing enterprise data simple and easily
available to decision makers. Data Analyzer enables you to gain insight into your business
processes and develop business intelligence.
Metadata Manager is an enterprise information asset management and analysis solution. It
enables you to analyze and manage metadata from any system. It also enables you to gain
insight into your metadata for impact and content analysis and allows you to view data and
information flow across systems.
xxiii
About This Book
The Installation and Configuration Guide is written for the system administrators who are
responsible for installing and configuring the PowerCenter product. This guide assumes you
have knowledge of your operating systems, relational database concepts, and the database
engines, flat files, or mainframe systems in your environment. This guide also assumes you are
familiar with the interface requirements for your supporting applications and that you are
familiar with the application server that you plan to use with Data Analyzer or Metadata
Manager.
The material in this book is also available online.
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 an
operating 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 overwrite
or 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.
xxiv Preface
Other Informatica Resources
In addition to the product manuals, Informatica provides these other resources:
♦ Informatica Customer Portal
♦ Informatica web site
♦ Informatica Knowledge Base
♦ Informatica Global Customer Support
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, Informatica Documentation Center, and access to the
Informatica user community.
Visiting the Informatica Web Site

You can access the Informatica corporate web site at http://www.informatica.com. The site
contains information about Informatica, its background, upcoming events, and sales offices.
You will also find product and partner information. The services area of the site includes
important information about technical support, training and education, and implementation
services.
Visiting the Informatica Knowledge Base

As an Informatica customer, you can access the Informatica Knowledge Base at
http://my.informatica.com. Use the Knowledge Base to search for documented solutions to
known technical issues about Informatica products. You can also find answers to frequently
asked questions, technical white papers, and technical tips.
Obtaining Customer Support

There are many ways to access Informatica Global Customer Support. You can contact a
Customer Support Center by using the telephone numbers listed the following table, you can
send email, or you can use the WebSupport Service.
Use the following email addresses to contact Informatica Global Customer Support:
♦ support@informatica.com for technical inquiries
♦ support_admin@informatica.com for general customer service requests
Preface xxv
WebSupport requires a user name and password. You can request a user name and password at
http://my.informatica.com.
North America / South America Europe / Middle East / Africa Asia / Australia
Informatica Corporation Informatica Software Ltd. Informatica Business Solutions

Headquarters 6 Waltham Park Pvt. Ltd.
100 Cardinal Way Waltham Road, White Waltham Diamond District
Redwood City, California Maidenhead, Berkshire Tower B, 3rd Floor
94063 SL6 3TN 150 Airport Road
United States United Kingdom Bangalore 560 008
India
Toll Free Toll Free Toll Free

877 463 2435 00 800 4632 4357 Australia: 1 800 151 830
Singapore: 001 800 4632 4357
Standard Rate Standard Rate Standard Rate

United States: 650 385 5800 Belgium: +32 15 281 702 India: +91 80 4112 5738
France: +33 1 41 38 92 26
Germany: +49 1805 702 702
Netherlands: +31 306 022 797
United Kingdom: +44 1628 511 445
xxvi Preface
Part I: Introduction
This part contains the following chapters:

♦ PowerCenter Installation Components, 3
♦ Installation and Upgrade Overview, 15
♦ PowerCenter Prerequisites, 33
♦ Before You Install, 49
♦ Before You Upgrade, 77
1
2
Chapter 1
PowerCenter Installation
Components
This chapter includes the following topics:
♦ Overview, 4
♦ Installation Package, 5
♦ PowerCenter Services, 7
♦ Data Analyzer, 9
♦ Metadata Manager, 10
♦ PowerCenter Client, 12
♦ PowerCenter Reports, 13
3
Overview
PowerCenter Standard Edition includes PowerCenter and Data Analyzer for PowerCenter
Repository Reports. PowerCenter Advanced Edition includes Standard Edition plus Metadata
Manager. The installation process configures the products and establishes connections
between services, servers, clients, and repositories.
You can install the complete set of PowerCenter components or select a custom installation to
install each component separately. The PowerCenter components you can install depend on
your license. You can install PowerCenter in graphical mode or console mode.
If you perform a complete installation, you install all components on one machine. If you
perform a custom installation, you select the component you want to install. You install each
component on the same machine or on different machines.
Depending on your license, you can install the following components:
♦ PowerCenter Services. Includes the Service Manager and application services that run in a
domain. The PowerCenter installer installs and configures PowerCenter Services. You can
create a new domain or join an existing domain. The installer can create the PowerCenter
repository or connect to an existing PowerCenter repository. For more information, see
“PowerCenter Services” on page 7.
♦ Data Analyzer. Includes Data Analyzer and JBoss Application Server. The installer installs
Data Analyzer on JBoss Application Server, BEA WebLogic Server, or IBM WebSphere
Application Server. The installer can create the Data Analyzer repository or connect to an
existing repository. For more information, see “Data Analyzer” on page 9.
♦ Metadata Manager. Includes Metadata Manager and JBoss Application Server. The
installer installs Metadata Manager on JBoss Application Server, BEA WebLogic Server, or
IBM WebSphere Application Server. The installer can create the Metadata Manager
repository or connect to an existing repository. The installer creates the PowerCenter
repository for Metadata Manager. For more information, see “Metadata Manager” on
page 10.
♦ PowerCenter Client. Includes client tools for PowerCenter and Metadata Manager. For
more information, see “PowerCenter Client” on page 12.
♦ PowerCenter Reports. Includes administrative and metadata reports. For more
information, see “PowerCenter Reports” on page 13.
You install the PowerCenter components from the PowerCenter installation DVD. The
installation package also includes the PowerCenter Documentation DVD, the PowerCenter
Utilities DVD, and the PowerCenter License Key CD. For more information about the
installation package, see “Installation Package” on page 5.
Depending on the version of PowerCenter, you may also apply a service pack to a
PowerCenter installation. For more information about PowerCenter service packs, see
“PowerCenter Service Pack” on page 6.
4 Chapter 1: PowerCenter Installation Components

Installation Package
The PowerCenter installation package contains the following DVDs, CDs, and service packs:
♦ PowerCenter Standard/Advanced Edition 32 bit/64 bit DVD. Contains the PowerCenter
installation files for components on all platforms, PowerCenter utilities, and customer
support tools. For more information, see “PowerCenter Standard/Advanced Edition 32
bit/64 bit DVD” on page 5.
♦ PowerCenter Documentation DVD. Contains the PowerCenter manuals, release notes,
and online help. For more information about the PowerCenter Documentation DVD, see
“PowerCenter Documentation DVD” on page 6.
♦ PowerCenter License Key CD. Contains the license keys for PowerCenter, Data Analyzer,
and Metadata Manager. For more information, see “PowerCenter License Key CD” on
page 6.
♦ PowerCenter Service Pack. Contains updates to the latest version of PowerCenter. For
more information, see “PowerCenter Service Pack” on page 6.
You can use Informatica Electronic Software Distribution (ESD) to get the PowerCenter
installer. Informatica provides the PowerCenter installer in ZIP and TAR format for you to
download using FTP. After you download the ZIP or TAR file, you unpack or unzip the
installer. You can then run the installation from the download files on a hard disk or create a
DVD to run the installer on multiple machines.
Informatica provides more information about downloading the installer in an email message
when you purchase PowerCenter. The information includes the user name, password, and
detailed instructions on downloading the installer. If you do not have the download
instructions, contact Informatica Global Customer Support.
Note: If you apply a PowerCenter service pack, the installation package contains the service
pack installer only. The installer is available only through ESD. For more information, see
“PowerCenter Service Pack” on page 6.
PowerCenter Standard/Advanced Edition 32 bit/64 bit DVD

The installation DVD contains the installers for graphical mode and console mode for all
PowerCenter components on all platforms. If you install PowerCenter in graphical mode, you
can choose the Server, Reports, or Client installer. If you install PowerCenter in console
mode, you run the Server and Reports installers separately.
Depending on your license, the server installation includes PowerCenter Services,
PowerCenter Repository Reports, Data Analyzer, and Metadata Manager. You can use the
server installation to perform a complete or custom installation.
The reports installation installs administrative and metadata reports that you can import into
a Data Analyzer or Metadata Manager instance. You can install administrative reports,
PowerCenter Repository Reports, and Data Analyzer Data Profiling Reports.
The DVD also contains customer support tools and command line programs and utilities for
PowerCenter, Data Analyzer, and Metadata Manager. You can install and run the command
Installation Package 5
line programs and utilities on a machine without installing PowerCenter. The DVD contains
all the files required by the programs and utilities. You do not need a license key to install or
run the programs and utilities.
PowerCenter Documentation DVD

PowerCenter provides a DVD that contains all documentation for the PowerCenter products.
After you install PowerCenter, you can run the documentation installer to install PowerCenter
documentation.
The PowerCenter Documentation DVD includes the following documentation:
♦ All PowerCenter books in PDF format
♦ Online help for the PowerCenter Client and the Administration Console
♦ Release notes for PowerCenter, Data Analyzer, and Metadata Manager
♦ Metadata Manager IME files for custom XConnects
PowerCenter License Key CD

The PowerCenter License Key CD contains the license keys for PowerCenter, Data Analyzer,
and Metadata Manager. Informatica ships one license key for PowerCenter and another
license key for Data Analyzer and Metadata Manager. You do not need a license key to install
the PowerCenter Client or Metadata Manager Client.
When you install PowerCenter, you install all PowerCenter options, PowerCenter Connects,
and metadata exchange options. The options and connections available to you are based on
your license. You can install PowerCenter Standard Edition or PowerCenter Advanced Edition
based on your license key.
You may receive a full or incremental license key. If you receive a full license key, you can
create or join a domain when you install PowerCenter. If you receive an incremental license
key, you can join a domain when you install PowerCenter.
Note: If you download the PowerCenter installation files and documentation from the
Informatica FTP site, you receive the required license keys by email.
PowerCenter Service Pack

A PowerCenter service pack contains updates to the latest version of PowerCenter. To apply a
service pack, you unzip or untar the installer and apply the service pack to an existing
PowerCenter installation.
The PowerCenter components updated by a service pack depend on the service pack version
you install. For more information about applying a PowerCenter service pack, see the
PowerCenter Service Pack Installation Guide.

PowerCenter Services
PowerCenter Services consists of a Service Manager and application services that run in a
domain. A domain is a collection of nodes and services that you can group in folders based on
administration ownership.
You create a domain when you first install PowerCenter Services. You can run the installation
on other machines to add the machines to the domain as nodes. You use the PowerCenter
Administration Console to manage the domain after you install PowerCenter Services.
When you run the installer, you install Informatica Services. Informatica Services runs as a
service on Windows and as a daemon on UNIX. When you start Informatica Services,
Informatica Services starts the Service Manager, which manages all domain operations.
For more information about PowerCenter domains, nodes, services, and the Administration
Console, see “Understanding Domains” in the PowerCenter Administrator Guide.
For more information about using the installer to create a domain or add a node to a domain,
see “Single or Multiple Machine Installation” on page 17.
Table 1-1 describes the PowerCenter Services components included in a PowerCenter Services
installation:
Table 1-1. Installed PowerCenter Components
Component Description Installation Summary
Informatica Services Starts the Service Manager on a node. - Installed in /server/bin directory under the
Installs as a service on Windows and PowerCenter installation directory.
as a daemon on UNIX. - Service or daemon started during installation.
Service Manager Manages domain operations on a - Installed in /server/tomcat directory under the
node. Includes authentication, PowerCenter installation directory.
authorization, configuration, domain, - Started during installation.
licensing, and log functions.
Repository Service Manages connections to the - Installed in /server/bin directory under the
PowerCenter repository. PowerCenter installation directory.
- Service started during installation.
- Connection established to the PowerCenter
repository.
PowerCenter repository Stores metadata for PowerCenter - Repository tables created.

source and target data, workflows,
sessions, and mappings.
Integration Service Extracts, transforms, and loads data to - Installed in /server/bin directory under the
PowerCenter targets. If Metadata PowerCenter installation directory.
Manager is installed, extracts and - Service started during installation.
loads metadata based on XConnect - Connection established to the Repository
workflows. Service.
PowerCenter Services 7
Table 1-1. Installed PowerCenter Components
Java Runtime Required by the Service Manager and - Installed in the java directory under the
Environment Java-based PowerCenter components. PowerCenter Services installation directory.
DataDirect 5.1 ODBC ODBC drivers used by the Integration - Installed in the ODBC5.1 directory under the
Drivers Service and PowerCenter Client. PowerCenter installation directory.
Directory Structure
PowerCenter Services are installed in the server directory under the PowerCenter installation
directory. The server directory contains PowerCenter applications, configuration files, and
storage directories for PowerCenter Services.
Table 1-2 describes the directories created under the server directory during a PowerCenter
Services installation:
Table 1-2. PowerCenter Services Installation Directories
Directory Name Contents
bin Contains PowerCenter application service executables and command line programs.
config Contains the node configuration file.
infa_shared Default storage location for run-time files used by Integration Service processes and
domain log events files generated by the Log Manager.
You can configure the shared directory location for the Integration Service processes and
the Log Manager in the Administration Console after installation.
tomcat Contains the Service Manager application files and the Service Manager log files.

Data Analyzer
You can install Data Analyzer with PowerCenter Standard or Advanced Edition. Data
Analyzer requires an application server. You can run Data Analyzer on one of the following
application servers:
♦ JBoss Application Server
♦ BEA WebLogic Server
♦ IBM WebSphere Application Server
If you run Data Analyzer on JBoss Application Server, you can install JBoss Application
Server with Data Analyzer or use an existing instance of JBoss Application Server. Informatica
includes JBoss Application Server version 4.0.3 in the PowerCenter installer.
If you run Data Analyzer on BEA WebLogic Server or IBM WebSphere Application Server,
you must obtain and install the application server before you install PowerCenter Standard
Edition.
For more information about application server prerequisites for Data Analyzer, see
“Application Servers” on page 40.
Table 1-3 describes the Data Analyzer components installed with a PowerCenter installation:
Table 1-3. Installed Data Analyzer Components
Data Analyzer Web application to analyze data from data - Installed on selected application server.
sources and create reports. - Data Analyzer utilities installed in the
Data Analyzer directory under the
PowerCenter installation directory.
- Connection established to Data Analyzer
repository.
Data Analyzer Stores metadata for Data Analyzer schemas, - Repository tables created.
Repository reports, and dashboards.
JBoss Application Server Java application server that manages - Installed in the JBoss403 directory under
processes for Data Analyzer. the PowerCenter installation directory.
- Application server started.
DataDirect JDBC Drivers JDBC drivers for use with Data Analyzer. - Connection established between Data
Analyzer and the Data Analyzer
repository.
Data Analyzer 9
Metadata Manager
Metadata Manager uses an application server to manage processes. You can run Metadata
Manager on one of the following application servers:
♦ BEA WebLogic Server
If you run Metadata Manager on JBoss Application Server, you can install JBoss Application
Server with Metadata Manager or use an existing instance of JBoss Application Server.
Informatica includes JBoss Application Server version 4.0.3 in the PowerCenter installer.
If you run Metadata Manager on BEA WebLogic Server or IBM WebSphere Application
Server, you must obtain and install the application server before you install PowerCenter
Standard Edition. The installer does not install BEA WebLogic Server or IBM WebSphere
Application Server.
For more information about application server prerequisites for Metadata Manager, see
“Application Servers” on page 40.
Metadata Manager XConnects are a set of PowerCenter workflows that Metadata Manager
uses to extract metadata from sources and load into the Metadata Manager repository. The
workflows are stored in the PowerCenter repository. You use the Metadata Manager
Configuration Console to run the XConnects to load metadata to the Metadata Manager
repository. Metadata Manager XConnects are installed when you install Metadata Manager.
When you install Metadata Manager, the PowerCenter installer can create a PowerCenter
repository or connect to an existing PowerCenter repository to store the XConnect workflows.
It creates a Metadata Manager folder in the PowerCenter repository to store the XConnect
workflows that you run from the Metadata Manager Configuration Console.
If you perform a complete installation of PowerCenter Advanced Edition, the installer uses
the PowerCenter repository as the PowerCenter repository for Metadata Manager. You must
create a separate database and user account for another PowerCenter repository and create a
Repository Service when you configure the application services.
Note: The PowerCenter repository that stores the Metadata Manager XConnects is called the
Integration repository in the Metadata Manager documentation.

Table 1-4 describes the Metadata Manager components installed with a PowerCenter
installation:
Table 1-4. Installed Metadata Manager Components
Metadata Manager Web application for analyzing and reporting - Installed on top of selected application
Server on metadata from PowerCenter and other server.
applications. - Installed in the Metadata Manager
directory under the PowerCenter
installation directory.
- Connections established to the Metadata
Manager repository.
- Connections established to the
PowerCenter repository.
Metadata Manager Stores the Metadata Manager schema, - Repository tables created.
Repository reports, dashboards, source metadata to - Metadata Manager warehouse tables
analyze and report on, and the packaged created.
metamodels that classify source metadata. - Metamodels installed.
PowerCenter Repository Stores Metadata Manager XConnect - Metadata Manager XConnect metadata
for Metadata Manager metadata. Also known as the Integration created in the Metadata Manager folder.
repository.
JBoss Application Server Java application server that manages - Installed in the JBoss403 directory under
processes for Metadata Manager. the PowerCenter installation directory if
new JBoss Application Server instance
is the selected application server.
- Application server started.
Metadata Manager PowerCenter workflows to extract and load - PowerCenter workflows created in the
XConnects metadata. Metadata Manager folder of specified
Data Direct JDBC Drivers JDBC drivers for use with Metadata - Establishes a connection between
Manager. Metadata Manager and the Metadata
Manager repository.
Metadata Manager 11
PowerCenter Client
With the PowerCenter Client installation, you can install the complete set of PowerCenter
client tools or select the custom installation to install the PowerCenter Client and Metadata
Manager Client separately. You can install the PowerCenter and Metadata Manager clients on
a Windows platform. You can use graphical or silent installation to install the PowerCenter
Client components.
The PowerCenter Client includes the following tools:
♦ Designer
♦ Repository Manager
♦ Workflow Manager
♦ Workflow Monitor
♦ Data Stencil
The Metadata Manager Client includes the following tools:
♦ Metadata Manager Console
♦ Custom Metadata Configurator
Table 1-5 describes the client components installed with PowerCenter:
Table 1-5. Installed Client Components
PowerCenter Client Manage users, define sources and targets, - Installed in the client directory under the
build mappings and mapplets with the PowerCenter Client installation directory.
transformation logic, and create workflows to - No configuration performed.
run the mapping logic.
Metadata Manager Client Client application you use to create, - Installed in the Metadata Manager
configure, and run Metadata Manager directory under the PowerCenter Client
XConnects. installation directory.
- Code page and PowerCenter repository
for Metadata Manager name configured.
DataDirect 5.1 ODBC ODBC drivers for use with the PowerCenter - Installed in the ODBC5.1 directory under
Drivers Client and Metadata Manager Console. the PowerCenter Client and Metadata
Manager Client installation directory.
- No configuration performed.

PowerCenter Reports
PowerCenter provides administrative and metadata reports that you can import into a Data
Analyzer or Metadata Manager instance.
The PowerCenter Reports include the following reports:
♦ Administrative reports
♦ PowerCenter Repository Reports
♦ Data Analyzer Data Profiling Reports
Administrative Reports
Administrative reports are a set of prepackaged administrative reports that enable system
administrators to track user activities and monitor processes. The reports provide a view into
the information stored in a Data Analyzer or Metadata Manager repository. They include
details on application usage and report schedules and errors.
For a list of all reports included in the Data Analyzer administrative reports, see “Working
with the Data Analyzer Administrative Reports” in the Data Analyzer Administrator Guide.
PowerCenter Repository Reports

PowerCenter Repository Reports are a set of prepackaged dashboards and reports that allow
you to analyze the following types of PowerCenter repository metadata:
♦ Source and target metadata, including shortcuts, descriptions, and corresponding database
names and field-level attributes
♦ Transformation metadata in mappings and mapplets, including port-level details for each
transformation
♦ Mapping and mapplet metadata, including the targets, transformations, and dependencies
for each mapping
♦ Workflow and worklet metadata, including schedules, instances, events, and variables
♦ Session metadata
♦ Change management metadata, including versions of sources, targets, labels, and label
properties
♦ You must enable versioning in PowerCenter for versions to be tracked and analyzed.
♦ User and group metadata
♦ Operational metadata, including runtime statistics
For a list of all reports included in the PowerCenter Repository Reports, see the PowerCenter
Repository Reports Reference.
PowerCenter Reports 13
Data Analyzer Data Profiling Reports
Use the Data Analyzer Data Profiling Dashboard to access the Data Analyzer Data Profiling
reports. Data Analyzer provides the following types of reports:
♦ Composite reports. Display the Data Analyzer Data Profiling metadata reports and
summary reports. From the composite reports, you can drill down into profile metadata
and summary reporting on specific functions.
♦ Metadata reports. Display basic metadata about a data profile and the source-level and
column-level functions in a data profile. They also provide historic statistics on previous
runs of the same data profile.
♦ Summary reports. Display data profile results for specific source-level and column-level
functions in a data profile.

Chapter 2
Installation and Upgrade

Overview
This chapter contains the following topics:
♦ Overview, 16
♦ Single or Multiple Machine Installation, 17
♦ Installing PowerCenter, 19
♦ Upgrading PowerCenter, 23
♦ Upgrading Data Analyzer, 29
♦ Upgrading Metadata Manager, 31
15
Overview
This section outlines the steps to install a complete or custom version of PowerCenter
Standard and Advanced Edition or to upgrade a previous version of PowerCenter. You can
install PowerCenter on a single machine or multiple machines.
The installation and upgrade steps depend on whether you install PowerCenter for the first
time or upgrade a previous version:
♦ Install PowerCenter. You can install a complete or custom version of PowerCenter
Standard or Advanced Edition. For more information about installing PowerCenter, see
“Installing PowerCenter” on page 19.
♦ Upgrade PowerCenter. You can upgrade a previous version of PowerCenter. The upgrade
steps depend on the version of PowerCenter you want to upgrade. For more information,
see “Upgrading PowerCenter” on page 23.
♦ Upgrade Data Analyzer. You can upgrade a previous version of PowerAnalyzer or Data
Analyzer. For more information, see “Upgrading Data Analyzer” on page 29.
♦ Upgrade Metadata Manager. You can upgrade a previous version of SuperGlue or
Metadata Manager. For more information, see “Upgrading Metadata Manager” on
page 31.
These steps refer to additional chapters where you can obtain more information.
Note: You can install PowerCenter on the same machine as an existing version of PowerCenter
if you do not upgrade the existing version. You do not need to uninstall your current version
of PowerCenter to install PowerCenter 8.1.1. You must install PowerCenter 8.1.1 in a
different directory from the previous version. If you install on the same machine as an existing
PowerCenter 8.x installation, you must first stop Informatica Services.
16 Chapter 2: Installation and Upgrade Overview

Single or Multiple Machine Installation
When you install PowerCenter Services, the installer prompts you to create a PowerCenter
domain or join an existing domain. You can run the installer to complete the following tasks:
♦ Create domain. The installer installs PowerCenter Services on the machine and creates a
domain and node on the machine.
♦ Join domain. The installer installs PowerCenter Services and adds the machine as a worker
node or gateway node to an existing domain. You must create a domain before you can
join a domain.
You can create or join a domain based on your installation requirements. You can install
PowerCenter Services in the following environments:
♦ Single machine installation. The domain consists of a single machine or node. All
application services, such as the Integration Service and Repository Service, run on a single
machine.
♦ Multiple machine installation. The domain consists multiple machines or nodes. One
node serves as the gateway and routes requests from the other nodes in the domain. The
other nodes can be gateway nodes or worker nodes. You can have multiple nodes in the
domain.
For more information about the PowerCenter Services architecture, see the Administrator
Guide.
Single Machine Installation

A single machine installation consists of a domain with one node. All application services,
including the Integration Service and Repository Service, run on the node.
Use the following steps as a guideline to install PowerCenter Services on a single machine:
1. Complete the pre-installation tasks.
2. Install PowerCenter Services and choose to create a domain. Enter the domain and node
information. This machine is the gateway node for the domain.
The installer installs PowerCenter Services, creates the domain and node on the machine,
starts Informatica Services, creates and starts application services, and establishes
connectivity to the PowerCenter repository.
3. Use the Administration Console to configure the application services.
Multiple Machine Installation

A multiple machine installation consists of a domain with multiple nodes. To create a domain
with multiple nodes, run the installer on one machine to create the domain and a node. Run
the installer on other machines to add those machines as gateway or worker nodes in the
domain.
Single or Multiple Machine Installation 17

You can configure the nodes in the domain to run application services. The node where you
create the domain serves as the master gateway for the domain and handles requests from
services running on the other nodes in the domain.
Use the following steps as a guideline to install PowerCenter Services on multiple machines:
1. Complete the pre-installation tasks on each machine.
2. Run the PowerCenter installer on the machine and choose to create a domain. Enter the
domain and node information. If you choose to create a Repository Service and an
Integration Service, the installer prompts you for the PowerCenter repository
information.
The installer installs PowerCenter Services, creates the domain and node on the machine,
starts Informatica Services, creates application services, and establishes connectivity to
the PowerCenter repository. This machine becomes the gateway for the domain.
3. Run the PowerCenter Services installer on another machine and choose to join a domain.
Enter the information for the domain, including domain name and port number, that
you created in step 2.
The installer installs PowerCenter Services, creates a node on the machine, adds the node
to the domain, and starts Informatica Services on the node.
4. Use the Administration Console to configure the nodes and the application services for
the domain.
For example, you can run the Integration Service and Repository Service on separate
nodes.

Installing PowerCenter
The installation steps depend on the type of installation you want to perform:
♦ Complete PowerCenter Standard or Advanced Edition installation. Installs all
PowerCenter Standard or Advanced Edition components. For more information, see
“PowerCenter Complete Installation Steps” on page 19.
♦ PowerCenter Services custom installation. Install PowerCenter Services. For more
information, see “PowerCenter Services Custom Installation Steps” on page 20.
♦ Data Analyzer custom installation. Install Data Analyzer and PowerCenter Repository
Reports. For more information, see “Data Analyzer Custom Installation Steps” on page 21.
♦ Metadata Manager custom installation. Install Metadata Manager. For more information,
see “Metadata Manager Custom Installation Steps” on page 22.
The PowerCenter installer installs the PowerCenter components, collects the configuration
information, and then configures the PowerCenter components. You must complete a step
successfully before you can continue to the next step. If you are unable to configure
PowerCenter components during installation, you may be able to configure them after
installation.
PowerCenter Complete Installation Steps

To install the complete version of PowerCenter Standard or Advanced Edition, complete the
following tasks:
1. Verify prerequisites. Depending on the edition you install, verify the prerequisites for
PowerCenter Services, Data Analyzer, Metadata Manager, and the PowerCenter Client,
including minimum system requirements, supported databases, and web browsers. For
more information, see “PowerCenter Prerequisites” on page 33.
2. Complete the pre-installation tasks. Pre-installation tasks include creating the repository
databases and domain configuration database, setting up database users, installing the
repository database client, creating a system user, configuring the web browser, and
installing the application server for Data Analyzer and Metadata Manager. For more
information, see “Before You Install” on page 49.
3. Install PowerCenter Standard or Advanced Edition. Select Complete for the installation
set. You can choose to create or join a domain. The installer creates a Repository Service
and Integration Service and the PowerCenter and Data Analyzer repositories, starts
Informatica Services, and installs Data Analyzer on the selected application server.
If you install PowerCenter Advanced Edition, the installer creates the PowerCenter
repository for Metadata Manager and installs Metadata Manager on the selected
application server. You must create a separate repository for use with the PowerCenter
Client tools after installation.
For more information about installing PowerCenter, see “PowerCenter Complete
Installation in Graphical Mode” on page 101 or “PowerCenter Complete Installation in
Console Mode” on page 211.
Installing PowerCenter 19
4. Install the PowerCenter Client and Metadata Manager Client. Install the PowerCenter
Client on Windows. If you are installing PowerCenter Advanced Edition, you also install
the Metadata Manager Client. For more information about installing the PowerCenter
Client, see “PowerCenter Client Installation” on page 265.
5. Install PowerCenter Reports. Install PowerCenter Reports on Data Analyzer. For more
information, see “PowerCenter Reports Installation” on page 281.
6. Install PowerCenter documentation. Install PowerCenter documentation on Windows.
For more information, see “Documentation Installation” on page 291.
7. Configure PowerCenter. Includes configuring Informatica Services and application
services, configuring the PowerCenter Integration Utility, creating a Data Profiling
warehouse, and setting up PowerCenter Repository Reports. If you installed PowerCenter
Advanced Edition, you must also create the PowerCenter repository for use with the
PowerCenter Client tools. For more information, see “After You Install” on page 323.
8. Configure the PowerCenter Client machines. Configure the PowerCenter Client
machines to connect to each source and target database you need to access and create an
ODBC connection for each database you access. For more information, see “Connecting
to Databases from Windows” on page 487.
9. Set up the Metadata Manager Console. If you install PowerCenter Advanced Edition,
verify the PowerCenter repository, Integration Service, and Repository Service
connections in the Metadata Manager Console. Also, configure the PowerCenter source
directory in the Metadata Manager Console. For more information, see “Setting Up the
Metadata Manager Console” in the Metadata Manager Administrator Guide.
PowerCenter Services Custom Installation Steps

When you perform a custom installation, you install PowerCenter Services only. Complete
the following tasks to install PowerCenter Services:
1. Verify prerequisites. Verify the prerequisites for PowerCenter Services and the
PowerCenter Client, including minimum system requirements, supported databases, and
web browsers. For more information, see “PowerCenter Prerequisites” on page 33.
2. Complete the pre-installation tasks. Pre-installation tasks include creating the
PowerCenter repository database and domain configuration database, setting up database
users, installing the repository database client, creating a system user, and configuring the
web browser. For more information, see “Before You Install” on page 49.
3. Install PowerCenter Advanced Edition. Select Custom for the installation set. Select the
PowerCenter Services component. You can choose to create or join a domain.
For more information, see “PowerCenter Custom Installation in Graphical Mode” on
page 153 and “PowerCenter Custom Installation in Console Mode” on page 237.
4. Install the PowerCenter Client. Install the PowerCenter Client on Windows. For more
information, see “PowerCenter Client Installation” on page 265.

6. Configure PowerCenter. Configure Informatica Services and use the Administration
Console to configure application services. You can also configure Data Profiling. For
more information, see “After You Install” on page 323.
7. Configure the PowerCenter Client machines. Configure the PowerCenter Client
machines to connect to each database you need to access and create an ODBC
connection for each database you access. For more information, see “Connecting to
Databases from Windows” on page 487.
Data Analyzer Custom Installation Steps

When you perform a custom installation of Data Analyzer, you install Data Analyzer only.
You can install using graphical or console mode on UNIX and using graphical mode on
Windows.
Complete the following tasks to install Data Analyzer:
1. Verify prerequisites. Verify prerequisites for Data Analyzer, including minimum system
requirements and supported repository databases. For more information, see
“PowerCenter Prerequisites” on page 33.
2. Complete the pre-installation tasks. Pre-installation tasks include creating the Data
Analyzer repository database and setting up a database user, creating a system user,
configuring the web browser, and installing the application server for Data Analyzer. For
more information, see “Pre-Installation Tasks” on page 50.
3. Install Data Analyzer. Select Custom for the installation set and select the Data Analyzer
component. The installer installs Data Analyzer on the selected application server, and
creates the Data Analyzer repository.
page 153 or “PowerCenter Custom Installation in Console Mode” on page 237.
4. Install administrative reports. You can use the PowerCenter Reports installer to install
the Data Analyzer administrative reports. For more information, see “PowerCenter
Reports Installation” on page 281.
5. Install PowerCenter documentation. You can install the documentation on Windows.
6. Configure the PowerCenter Integration Utility. If you run Data Analyzer on IBM
WebSphere Application Server, you must configure the PowerCenter Integration Utility
client resource (notifyias.ear). For more information, see “Configuring the PowerCenter
Integration Utility for WebSphere” on page 334.
7. Configure Microsoft SQL Server (Optional). If you use a Microsoft SQL Server database
for the Data Analyzer repository, you must install JDBC XA stored procedures. For more
information, see “Configuring Microsoft SQL Server for a Data Analyzer Repository” on
page 338.
Installing PowerCenter 21
Metadata Manager Custom Installation Steps
When you perform a custom installation of Metadata Manager, you install Metadata Manager
only. You can install Metadata Manager using graphical or console mode on UNIX and using
graphical mode on Windows.
Complete the following tasks to install Metadata Manager:
1. Verify prerequisites. Verify prerequisites for Metadata Manager, including minimum
system requirements and supported repository databases. For more information, see
2. Complete the pre-installation tasks. Pre-installation tasks include creating database user
accounts for the Metadata Manager repository and PowerCenter repository for Metadata
Manager, configuring the web browser, and installing the application server for Metadata
Manager. For more information, see “Pre-Installation Tasks” on page 50.
3. Install Metadata Manager. Select Custom for the installation set and select the Metadata
Manager component. The installer creates the PowerCenter repository for Metadata
Manager and connects to the Metadata Manager repository.
page 153 or “PowerCenter Custom Installation in Console Mode” on page 237.
4. Install the Metadata Manager Client. You can install the Metadata Manager Client on
Windows. For more information, see “Running the Custom Client Installation” on
page 271.
6. Set up the Metadata Manager Console. Verify the PowerCenter repository for Metadata
Manager, Integration Service, and Repository Service connections in the Metadata
Manager Console. Also, specify the PowerCenter source files directory in the Metadata
Manager Console. For more information, see “Setting Up the Metadata Manager
Console” in the Metadata Manager Administrator Guide.

Upgrading PowerCenter
You can upgrade PowerCenter from the following previous versions:
♦ PowerCenter 6.x or 7.x. When you upgrade PowerCenter 6.x or 7.x, you install
PowerCenter Services, upgrade existing Repository Agents or PowerCenter Servers,
upgrade the PowerCenter repository content, and install the PowerCenter Client. For
more information about upgrading PowerCenter version 6.x or 7.x, see “PowerCenter
Version 6.x / 7.x Upgrade Steps” on page 24.
♦ PowerCenter 8.0. When you upgrade PowerCenter 8.0, you install PowerCenter 8.1.1 on
the nodes in the current domain. You then upgrade the PowerCenter 8.0 domain and node
metadata and PowerCenter repository, and install the PowerCenter Client. For more
information about upgrading PowerCenter 8.0, see “PowerCenter Version 8.0 Upgrade
Steps” on page 25.
♦ PowerCenter 8.1. When you upgrade PowerCenter 8.1, you install PowerCenter 8.1.1.
The installer upgrades the domain configuration and node configuration for PowerCenter
8.1. You also install the PowerCenter Client. For more information about upgrading
PowerCenter 8.1, see “PowerCenter Version 8.1 Upgrade Steps” on page 27.
Compatible PowerCenter Versions

If you are using a version of PowerCenter that is not supported by the version 8.1.1 upgrade,
you must upgrade your existing version to a supported version before proceeding with the
upgrade. Contact Informatica Global Customer Support to obtain the version of PowerCenter
you need to complete your upgrade.
Table 2-1 describes the compatible upgrades for previous versions of PowerCenter/
PowerMart:
Table 2-1. PowerCenter Compatible Upgrades
Existing Version Compatible Upgrades
PowerMart 3.5 PowerCenter 1.0 PowerMart 4.0
PowerCenter 1.0/4.0 PowerCenter 1.5/1.6 PowerMart 4.5/4.6
PowerCenter 1.5/4.5 PowerCenter 1.6/1.7 PowerMart 4.6/4.7
PowerCenter 1.6/4.6 PowerCenter 1.7/5.0/5.1 PowerMart 4.7/5.0/5.1
PowerCenter 1.7/4.7* PowerCenter 5.0/5.1/6.0/6.1 PowerMart 5.0/5.1/6.0/6.1
PowerCenter 5.0/5.0 PowerCenter 5.1/6.0/6.1/6.2/7.0/7.1 PowerMart 5.1/6.0/6.1/6.2
PowerCenter 5.1/5.1* PowerCenter 6.0/6.1/6.2/7.0/7.1 PowerMart 6.0/6.1/6.2
PowerCenter 6.0/6.0 PowerCenter 6.1/6.2/7.0/7.1/8.0/8.1/8.1.1 PowerMart 6.1/6.2
PowerCenter 6.1/6.1 PowerCenter 6.2/7.0/7.1/8.0/8.1/8.1.1 PowerMart 6.2
PowerCenter 6.2/6.2 PowerCenter 7.0/7.1/8.0/8.1/8.1.1
Upgrading PowerCenter 23
Table 2-1. PowerCenter Compatible Upgrades
Existing Version Compatible Upgrades
PowerCenter 7.0 PowerCenter 7.1/8.0/8.1/8.1.1
PowerCenter 7.1* PowerCenter 8.0/8.1/8.1.1
PowerCenter 8.0 PowerCenter 8.1/8.1.1
PowerCenter 8.1* PowerCenter 8.1.1

* Indicates BTree upgrades in PowerCenter. To retain your existing incremental aggregation files, you must upgrade using the indicated
BTree path, and run a session to realign the files. For example, to upgrade from PowerCenter 5.1.x to PowerCenter 8.1, first upgrade to
PowerCenter 7.1 and then to PowerCenter 8.1. For more information about upgrading incremental aggregation files, see the Post-
Upgrade Reference.
Memory and CPU Resource Usage

Effective in version 8.0, you many notice an increase in memory and CPU resource usage on
machines running PowerCenter Services. The following factors may increase memory and
CPU resource usage:
♦ Updates to Integration Service and Repository Service processes. The pmserver and
pmdtm process for the Integration Service and the pmrepagent process for the Repository
Service include updated functionality that may increase memory and CPU resource usage.
♦ High availability. If you configure a domain for high availability, service restart, failover,
and recovery operations, memory and CPU resource usage may increase.
♦ Java Runtime Environment (JRE). The PowerCenter service-oriented architecture uses
the Java Runtime Environment (JRE) to run the PowerCenter domains and nodes.
Domains and nodes require more memory and CPU resources than when you run a
PowerCenter Server or Repository Server in PowerCenter 6.x/7.x.
♦ Log Manager. If the Log Manager collects and processes a large number of log events, it
may require additional memory and CPU resources to collect and process the log events.
Depending on your configuration, PowerCenter 8.0 may consume up to 5 percent more CPU
resources for each domain than PowerCenter 6.x/7.x. PowerCenter 8.0 may also consume
more memory.
PowerCenter Version 6.x / 7.x Upgrade Steps

Complete the following tasks to upgrade PowerCenter version 6.x or 7.x:
2. Complete the pre-upgrade tasks. Pre-upgrade tasks include establishing the installation
environment, configuring database connectivity, preparing repositories and the Data
Profiling warehouse, backing up and copying PowerCenter configuration files, and
backing up the Web Services Hub configuration. For more information, see
“PowerCenter Version 6.x/7.x Pre-Upgrade Steps” on page 79.

3. Install PowerCenter Services. Install PowerCenter Services and create a domain and
gateway node. You do not need to create a Repository Service and Integration Service if
you install PowerCenter Services without Metadata Manager. The Repository Service and
Integration Service for PowerCenter will be created when you upgrade PowerCenter.
You can also join a domain to add other machines as nodes to an existing domain. Join a
domain if you want the upgraded Repository Services or Integration Services to run on
nodes other than the gateway node for the domain.
For more information about installing PowerCenter Services, see “PowerCenter Custom
Installation in Graphical Mode” on page 153 or “PowerCenter Custom Installation in
4. Upgrade PowerCenter. Use the Upgrade Wizard to upgrade a Repository Agent and
PowerCenter Server configuration to a Repository Service and Integration Service in a
PowerCenter domain. You can also upgrade existing PowerCenter repository content to
the new repository version. You also upgrade the PowerCenter Client and the Data
profiling warehouse. For more information, see “Upgrading PowerCenter” on page 401.
5. Complete the post-upgrade tasks. Post-upgrade tasks include updating $PMRootDir
and moving the Integration Service runtime files. You can also update the shared
directory for the service logs. If you installed PowerCenter Services with Metadata
Manager, you must recreate the Repository Service for the PowerCenter repository for
Metadata Manager. For more information about the post-upgrade tasks, see
“PowerCenter 6.x / 7.x Post-Upgrade Tasks” on page 457.
6. Configure PowerCenter. Configure Informatica Services and the Repository Service and
Integration Service. For more information about configuring PowerCenter, see “After You
Install” on page 323.
7. Install PowerCenter documentation. You can install the documentation on Windows.
8. Complete additional post-upgrade tasks. After you complete the PowerCenter upgrade,
you may need to perform additional tasks to complete the upgrade. For more
information about behavior changes between different versions, changes to repository
objects impacted by the upgrade process, and tasks you may need to perform to maintain
previous behavior or take advantage of new behavior, see the PowerCenter Post-Upgrade
Reference.
PowerCenter Version 8.0 Upgrade Steps

Complete the following tasks to upgrade PowerCenter version 8.0:
2. Complete the pre-upgrade tasks. Pre-upgrade tasks include preparing the repository for
upgrade, noting the domain configuration, stopping Informatica Services, removing
environment variables, and backing up metadata configuration files. For more
information about the pre-upgrade steps, see “PowerCenter Version 8.0 Pre-Upgrade
3. Install PowerCenter Services. Install PowerCenter Services on all the nodes in the
PowerCenter 8.0 domain. You install PowerCenter Services and create a temporary
domain on the node that currently hosts the domain. If you have a domain with multiple
nodes, install PowerCenter Services and add the other nodes in the domain to the
temporary domain.
You must follow specific steps to install PowerCenter Services when you upgrade
PowerCenter 8.0. For more information, see “Installation Steps for Upgrading
PowerCenter 8.0” on page 27.
For more information about installing PowerCenter Services, see “PowerCenter Custom
4. Upgrade PowerCenter. Use infaupgrade to upgrade the existing metadata in the
domainmeta.xml and nodemeta.xml files to the appropriate location in the PowerCenter
domain. Use the PowerCenter Administration Console to upgrade the contents of the
PowerCenter repository. You also upgrade the PowerCenter Client and the Data Profiling
warehouse. For more information, see “Upgrading PowerCenter” on page 401.
5. Complete the post-upgrade tasks. The post-upgrade tasks include registering local
repositories and updating the password environment variable. If you want to use a UTF-
8 repository, back up the existing repository, create a UTF-8 database, and restore the
repository to the new database. You can move the PowerCenter run-time files to the new
installation directory. You can also create and configure a Web Services Hub and update
the client applications. For more information about the post-upgrade tasks, see
“PowerCenter 8.0 Post-Upgrade Tasks” on page 460.
6. Configure PowerCenter. Configure Informatica Services and the Repository Service and
Integration Service. For more information about configuring PowerCenter, see “After You
7. Install PowerCenter documentation. Install the PowerCenter documentation on
Windows. For more information, see “Documentation Installation” on page 291.
information about behavior changes between different versions, changes to repository
objects impacted by the upgrade process, and tasks you may need to perform to maintain
previous behavior or take advantage of new behavior, see the PowerCenter Post-Upgrade
Reference.

Installation Steps for Upgrading PowerCenter 8.0
You must complete the following steps to install PowerCenter Services when you upgrade
PowerCenter 8.0:
1. Install PowerCenter Services and create a domain on the gateway node for the previous
PowerCenter domain. You must use a new installation directory and use the domain
name and gateway node port number from the previous installation.
2. Install PowerCenter Services on the other nodes in the PowerCenter domain and join the
domain you created in step 1. Use the same node names and port numbers from the
previous installation. Do not create application services.
3. Stop Informatica Services on the nodes in the domain.
For more information about the upgrade process, see “Upgrading PowerCenter” on page 401.
PowerCenter Version 8.1 Upgrade Steps

Complete the following tasks to upgrade PowerCenter version 8.1:
2. Complete the pre-upgrade tasks. Pre-upgrade tasks include backing up the domain
configuration, backing up the node configuration for the nodes in the domain, and
stopping PowerCenter Services. For more information about the pre-upgrade tasks, see
“PowerCenter 8.1 Pre-Upgrade Steps” on page 84.
3. Upgrade PowerCenter Services. Install PowerCenter Services on all the nodes in the
PowerCenter 8.1 domain and upgrade the current PowerCenter installation. The installer
upgrades the domain and node when you install PowerCenter Services. You must install
PowerCenter Services on the gateway node for the domain before you install
PowerCenter Services on the worker nodes in the domain.
For more information about upgrading PowerCenter Services with the installer, see
“Upgrading from PowerCenter 8.1” on page 170.
4. Complete the PowerCenter upgrade. Upgrade the PowerCenter Client and the Data
Profiling warehouse. For more information, see “Upgrading PowerCenter” on page 401.
5. Complete the post-upgrade tasks. Post-upgrade tasks include restarting Informatica
Services, updating the repository, and moving Integration Service run-time files. For
more information about the post-upgrade tasks, see “PowerCenter 8.1 Post-Upgrade
Tasks” on page 462.
6. Install PowerCenter documentation. Install the PowerCenter documentation on
Windows. For more information, see “Documentation Installation” on page 291.
information about behavior changes between different versions and tasks you may need
to perform to maintain previous behavior or take advantage of new behavior, see the
PowerCenter Post-Upgrade Reference.
Installer Upgrade Tasks for PowerCenter 8.1

When you upgrade from PowerCenter 8.1 to PowerCenter 8.1.1, you install PowerCenter
8.1.1 into the PowerCenter 8.1 installation directory. When the installer installs PowerCenter
into the previous installation directory, it completes the following tasks:
♦ Renames the previous server directory. The installer renames the previous server directory
to server_810_PC, and installs PowerCenter Services into a new server directory.
♦ Copies configuration files. The installer copies nodemeta.xml, adminconsole.url,
server.xml, and domains.infa from the previous server folder into the new server folder.
♦ Copies log event files. The installer copies the log event files from the previous
server\infa_shared\logs directory into the new server directory.

Upgrading Data Analyzer
You can upgrade Data Analyzer and PowerAnalyzer to Data Analyzer 8.1.1. To upgrade Data
Analyzer 8.0 or earlier, install Data Analyzer 8.1.1 and use the upgrade utility provided with
Data Analyzer to upgrade the repository.
You can upgrade the following versions of PowerAnalyzer and Data Analyzer to Data Analyzer
8.1.1:
♦ PowerAnalyzer 4.1.1 / 5.0 / 5.0.1
♦ Data Analyzer 8.0
To upgrade from Data Analyzer 8.1, install Data Analyzer 8.1.1 and choose the existing Data
Analyzer repository. You do not need to perform an upgrade of the Data Analyzer repository.
Install the new version of Data Analyzer without uninstalling the current working instance of
Data Analyzer. When you install the new version of Data Analyzer, select the option to use an
existing repository. You upgrade the copy of the existing repository to the new version.
To upgrade Data Analyzer 8.0 or earlier to the latest version, complete the following steps:
1. Verify prerequisites. Verify prerequisites for Data Analyzer, including minimum system
requirements and supported repository databases. For more information, see
2. Complete the pre-upgrade tasks. Pre-upgrade tasks include backing up the Data
Analyzer repository, copying the customized files to a temporary directory, and preparing
the Data Analyzer repository. For more information, see “Data Analyzer Pre-Upgrade
3. Install Data Analyzer. Use PowerCenter installer to install Data Analyzer. You can use
the complete or custom installation to install Data Analyzer.
For more information about installing Data Analyzer, see “PowerCenter Custom
4. Upgrade the Data Analyzer repository. If you upgrade from Data Analyzer version 8.0 or
earlier, use the Repository Upgrade utility provided with Data Analyzer 8.1.1 to upgrade
the copy of the existing Data Analyzer repository. Run the Repository Upgrade utility
and provide the connection information for the restored repository database. For more
information about running the upgrade utility, see “Upgrading Data Analyzer” on
page 431.
For information about the changes made to the Data Analyzer repository during the
upgrade process, see “Data Analyzer” in the PowerCenter Post-Upgrade Reference.
5. Complete the post-upgrade tasks. After you upgrade the Data Analyzer repository, you
need to restore any customization you previously made. For more information about the
post-upgrade tasks, see “Data Analyzer Post-Upgrade Tasks” on page 464.
Upgrading Data Analyzer 29

After you complete the upgrade steps, verify that all schemas, dashboards, and reports are
working correctly in Data Analyzer 8.1.1. If the upgrade is successful, you can uninstall the
previous version of Data Analyzer.

Upgrading Metadata Manager
You can upgrade Metadata Manager version 8.1 or earlier and SuperGlue 2.1 and 2.2 to
Metadata Manager 8.1.1. To upgrade SuperGlue or Metadata Manager, install Metadata
Manager, upgrade the Metadata Manager repository, update the PowerCenter repository for
Metadata Manager, and install the Metadata Manager Client.
Metadata Manager Upgrade Steps

To upgrade Metadata Manager, complete the following steps:
1. Verify prerequisites. Verify prerequisites for Metadata Manager, including minimum
system requirements and supported repository databases. For more information, see
2. Complete the pre-upgrade tasks. The pre-upgrade tasks include copying the Metadata
Manager repository and backing up the parameter files. For more information, see
“Metadata Manager Pre-Upgrade Steps” on page 96.
3. Install Metadata Manager. Use the PowerCenter installer to install Metadata Manager.
Use the existing Metadata Manager repository when you install Metadata Manager.
You create a PowerCenter repository for Metadata Manager when you install Metadata
Manager. When you create a PowerCenter repository, the PowerCenter installer creates
the Integration Service and Repository Service for the PowerCenter repository for
Metadata Manager in a PowerCenter domain.
If you do not install PowerCenter Services, you must select the PowerCenter domain
where the installer creates the Integration Service and Repository Service for the
PowerCenter repository for Metadata Manager.
For more information about installing Metadata Manager, see “PowerCenter Custom
4. Stop the Metadata Manager application server. You must stop the Metadata Manager
application server before you upgrade the Metadata Manager repository contents. For
more information about stopping Metadata Manager, see “Starting and Stopping
Application Servers” on page 535.
5. Upgrade the Metadata Manager repository. Use the Metadata Manager upgrade utility
shipped with the latest version of Metadata Manager to upgrade the Metadata Manager
repository. For more information about the Metadata Manager upgrade utility, see
“Upgrading Metadata Manager” on page 441.
6. Upgrade the Metadata Manager Client. For instructions on upgrading the Metadata
Manager Client, see “Upgrading the Metadata Manager Client” on page 453.
7. Complete the post-upgrade tasks. After you upgrade the Metadata Manager repository,
perform tasks such as updating metamodels, refreshing views, and deleting obsolete
Upgrading Metadata Manager 31

objects. For more information about the post-upgrade tasks, see “Metadata Manager
Post-Upgrade Tasks” on page 467.
After you complete the upgrade steps, verify that all dashboards and reports are working
correctly in Metadata Manager. When you are sure that the new version is working properly,
you can delete the old instance of Metadata Manager and switch to the new version.

Chapter 3
PowerCenter
Prerequisites
♦ Overview, 34
♦ Minimum System Requirements, 35
♦ Web Browsers, 37
♦ Database Requirements, 38
♦ Application Servers, 40
♦ Third-Party Software, 43
♦ Code Pages, 45
♦ Working with 32-bit and 64-bit Platforms, 46
33
Overview
Before you install PowerCenter, verify that the environment meets the minimum
requirements. You can verify the prerequisites for the PowerCenter components you install.
Table 3-1 describes the installation prerequisites for the PowerCenter components:
Table 3-1. PowerCenter Component Installation Prerequisites
Prerequisite PowerCenter Component Description and Reference
Minimum System PowerCenter Services Hardware and operating system requirements. For more
Requirements PowerCenter Client information, see “Minimum System Requirements” on
Data Analyzer page 35.
Metadata Manager
Web Browser PowerCenter Services Web browser required to access the PowerCenter
Data Analyzer Administration Console, Data Analyzer and Metadata
Metadata Manager Manager, and the Web Services Hub Console. For more
information, see “Web Browsers” on page 37.
Database PowerCenter Services Repository database, domain configuration database, and

Requirements Data Profiling Data Profiling warehouse requirements, including database
Data Analyzer type and minimum size. For more information, see “Database
Metadata Manager Requirements” on page 38.
Application Server Data Analyzer Required information and setup for installing Data Analyzer
Metadata Manager and Metadata Manager on JBoss Application Server, IBM
WebSphere Application Server, and BEA WebLogic Server.
For more information, see “Application Servers” on page 40.
Third-party PowerCenter Services X Virtual Frame Buffer for PowerCenter Services on UNIX.
Software PowerCenter Client Microsoft Visio 2003 for Data Stencil. Microsoft SOAP Toolkit
Data Analyzer and SVG Viewer for Data Analyzer and Metadata Manager.
Metadata Manager For more information, see “Third-Party Software” on page 43.
Code Pages PowerCenter Services Code page requirements for all PowerCenter components.
PowerCenter Client For more information, see “Code Pages” on page 45.
Data Analyzer
Metadata Manager
32-bit and 64-bit PowerCenter Services 32-bit and 64-bit compatibility between the PowerCenter
Compatibility components. For more information, see “Working with 32-bit
and 64-bit Platforms” on page 46.
34 Chapter 3: PowerCenter Prerequisites

Minimum System Requirements
PowerCenter Components:
PowerCenter Client
Data Analyzer
Metadata Manager
Verify the minimum hardware and operating system requirements before you install
PowerCenter components.
Table 3-2 describes the minimum system requirements to run PowerCenter components:
Table 3-2. Minimum System Requirements
Product Processor RAM Disk Space Operating System
PowerCenter Advanced Edition 4 CPUs 4 GB 2.3 GB Windows 2000 / 2003

complete installation Sun Solaris
HP-UX
IBM AIX
Red Hat Linux
SUSE Linux
PowerCenter Standard Edition 1 CPU 1 GB 1.3 GB Windows 2000 / 2003

complete installation Sun Solaris
HP-UX
IBM AIX
Red Hat Linux
SUSE Linux
PowerCenter Services 1 CPU 1 GB 500 MB Windows 2000 / 2003

Sun Solaris
HP-UX
IBM AIX
Red Hat Linux
SUSE Linux
Data Analyzer 2 CPUs 1 GB 800 MB Windows 2000 / 2003

Sun Solaris
HP-UX
IBM AIX
Red Hat Linux
SUSE Linux
Metadata Manager 2 CPUs 1 GB 1.0 GB Windows 2000 / 2003

Sun Solaris
HP-UX
IBM AIX
Red Hat Linux
SUSE Linux
Minimum System Requirements 35

Table 3-2. Minimum System Requirements
Product Processor RAM Disk Space Operating System
PowerCenter Client 1 CPU 512 MB 300 MB Windows 2000 /

2003 / XP
Metadata Manager Client 2 CPUs 512 MB 200 MB Windows 2000 /

2003 / XP
Note: The server installation for PowerCenter requires 1 GB of disk space for temporary files.
On UNIX, the installer writes the temporary files to the /tmp directory. On Windows, it
writes the files to the default drive. You can set the TMP or the InstallAnywhere
IATEMPDIR environment variable to specify the location of these files.

Web Browsers
Data Analyzer
Metadata Manager
You can use the following browsers to access Data Analyzer, the PowerCenter Administration
Console, and the Web Services Hub Console:
♦ Microsoft Internet Explorer
♦ Mozilla Firefox
You can use the following browser to access Metadata Manager:
♦ Microsoft Internet Explorer
For more information about configuring browsers to use with the Administration Console,
Data Analyzer, and Metadata Manager, see “Step 8. Configure Web Browser” on page 68.
Note: The PowerCenter Client requires Internet Explorer to display the Start Page for the
Designer, Repository Manager, and Workflow Manager.
Web Browsers 37
Database Requirements
Data Profiling
Data Analyzer
Metadata Manager
PowerCenter requires a relational database for the following components:

♦ PowerCenter repository
♦ PowerCenter domain configuration database
♦ Data Profiling warehouse
♦ Data Analyzer repository
♦ Metadata Manager repository
Table 3-3 describes the database requirements for PowerCenter components:
Table 3-3. Database Requirements for PowerCenter Components
PowerCenter Component Database Type Disk Space
PowerCenter repository IBM DB2 UDB 30 MB

Microsoft SQL Server
Oracle
Sybase ASE
PowerCenter domain IBM DB2 UDB 1 MB

configuration database Microsoft SQL Server
Oracle
Sybase ASE
Data Profiling warehouse IBM DB2 UDB 16 MB

Informix
Oracle
Sybase ASE
Teradata
Data Analyzer repository IBM DB2 UDB 60 MB

Oracle
Sybase ASE
Metadata Manager repository IBM DB2 UDB 550 MB

Microsoft SQL Server 2000
Oracle
Sybase ASE
Use the following rules and guidelines when you verify database size requirements:
♦ You can create a PowerCenter repository with a minimum of 30 MB of database space.
Allow up to 150 MB to store metadata.

♦ Assess how much the PowerCenter, Data Analyzer, and Metadata Manager repositories are
likely to grow and plan accordingly.
♦ You can create a Data Profiling warehouse with a minimum database space of 16 MB. You
may need to allocate more space depending on the amount of data you intend to profile,
whether you run profile sessions in verbose or normal mode, whether you use sampling or
full tables, and how often you purge the Data Profiling warehouse.
♦ If you run profile sessions in verbose mode, the Data Profiling warehouse may store all of
the data depending on the functions you use in the data profile. If you run a profile session
in normal mode, the Data Profiling warehouse stores less data.
Database Requirements 39
Application Servers
Data Analyzer
Metadata Manager
If you install Data Analyzer and Metadata Manager on an existing application server instance,
verify the application server installation prerequisites for the following application servers:
♦ JBoss Application Server. You can install Data Analyzer and Metadata Manager on an
existing JBoss Application Server instance. You can also install a new JBoss Application
Server instance with the PowerCenter installer. For more information, see “JBoss
Application Server Prerequisites” on page 41.
♦ IBM WebSphere Application Server. You can install Data Analyzer and Metadata
Manager on an existing instance of WebSphere Application Server. For more information,
see “IBM WebSphere Application Server Prerequisites” on page 41.
♦ BEA WebLogic Server. You can install Data Analyzer and Metadata Manager on an
existing instance of WebLogic Server. For more information, see “BEA WebLogic Server
Prerequisites” on page 42.
If you want to use a new WebSphere Application Server or WebLogic Server instance, you
must install the application server before you install Data Analyzer and Metadata Manager. If
you want to install Data Analyzer and Metadata Manager on a new JBoss Application Server
instance, install JBoss Application Server with the PowerCenter installer. For more
information about installing application servers, see “Step 10. Install the Application Server
(Optional)” on page 70.
You must stop the application server before you install Data Analyzer and Metadata Manager.
For more information about stopping the application server, see “Starting and Stopping
Note: You cannot install multiple instances of Data Analyzer or Metadata Manager on the
same application server. If you want to run multiple instances of Data Analyzer or Metadata
Manager, you must install each instance on a different application server. You can run a single
instance of Data Analyzer and Metadata Manager on the same application server.

JBoss Application Server Prerequisites
Table 3-4 displays the JBoss Application Server prerequisites:
Table 3-4. JBoss Application Server Prerequisites
Prerequisite Description
Server Configuration Verify the name of the server configuration and that it supports all available JBoss
Application Server services.
The PowerCenter installer requires the name of the server configuration on which to install
Data Analyzer and Metadata Manager.
Installation Directory If you use multiple JBoss Application Server instances, verify the correct home and server
configuration directory where you install Data Analyzer or Metadata Manager.
User Account You must install PowerCenter with the user account used to install or run JBoss Application
Server. The user account must have write permissions on the JBoss Application Server
home and server configuration directories.
IBM WebSphere Application Server Prerequisites

Table 3-5 displays IBM WebSphere Application Server prerequisites:
Table 3-5. IBM WebSphere Application Server Prerequisites
Installation Directory Depending on the edition of the WebSphere Application Server where you install Data
Analyzer and Metadata Manager, you must provide the name and location of the
WebSphere Application Server home and Network Deployment directories during Data
Analyzer and Metadata Manager installation.
Server Name You can provide the name of the server and HTTP port number to run Data Analyzer and
Metadata Manager. If you do not provide a server name, the PowerCenter installer
configures Data Analyzer and Metadata Manager to run on the default server, server1, on
port 9080.
padaemon user Account On Windows and UNIX, you log in with the padaemon user account to install Data Analyzer
and Metadata Manager and run WebSphere Application Server. For more information, see
“IBM WebSphere Application Server” on page 71.
User Groups On UNIX, verify that the root account is assigned to the mqm and mqbrkrs user groups. For
more information, see “IBM WebSphere Application Server” on page 71.
WebSphere Application Start the deployment manager, node agent, JMS server, and default server before you
Server Started install Data Analyzer and Metadata Manager. For more information, see “Starting IBM
WebSphere Application Server” on page 542.
Administrator User If you configure security for WebSphere Application Server using the Administration
Name and Password Console, you must provide the administrator user name and password during installation.
Application Servers 41
BEA WebLogic Server Prerequisites
Table 3-6 displays BEA WebLogic Server prerequisites:
Table 3-6. BEA WebLogic Server Prerequisites
Installation Directory You must provide the WebLogic Server installation directory when you install Data Analyzer
and Metadata Manager.
WebLogic Domain If you install Data Analyzer or Metadata Manager on a new domain, the PowerCenter
installer creates the WebLogic domain. You must provide the administrator user name and
password and listening port for the new domain.
If you install Data Analyzer or Metadata Manager on an existing WebLogic domain, you
must create the domain before you install Data Analyzer or Metadata Manager and provide
the administrator user name and password during installation.
For a new or existing WebLogic domain, you must provide the domain name and domain
location during installation.
User Account Log in with the same user account used to install WebLogic Server.

Third-Party Software
PowerCenter Installer
PowerCenter Client
Data Analyzer
Metadata Manager
PowerCenter requires third-party software to use certain features. You must download and
install the third-party software to use the features.
Table 3-7 describes the features and third-party software you may need to install:
Table 3-7. Third-Party Software
PowerCenter
Third-Party Software Description
Component
Java Runtime PowerCenter To run the PowerCenter installer on Windows, you must have the
Environment (JRE) Installer on Java Runtime Environment (JRE), version 1.4.2 or higher, installed on
Windows the machine where you install PowerCenter Services and the
PowerCenter installer.
Microsoft Visio 2003 PowerCenter In PowerCenter, you can use Data Stencil to create PowerCenter
Client (Data mapping templates using Microsoft Office Visio.
Stencil) You must obtain and install Visio 2003 before you can use Data
Stencil.
Microsoft .NET PowerCenter Data Stencil on Windows 2000 requires Microsoft .NET Framework
Framework 1.1 Client (Data 1.1. Service Pack 1. You cannot use other versions of Microsoft .NET
Stencil) Framework.
You can download Microsoft .NET Framework 1.1 from the following
web site:
http://msdn.microsoft.com/netframework/downloads/
framework1_1/
You can download Microsoft .NET Framework 1.1 Service Pack 1
from the following web site:
http://www.microsoft.com/downloads/
details.aspx?familyid=A8F5654F-088E-40B2-BBDB-A833
53618B38&displaylang=en
You must also install the Security Update for Microsoft .NET
Framework, Version 1.1 Service Pack 1 (KB886903).
You can download the security update from the following web site:
http://www.microsoft.com/downloads/
details.aspx?familyid=8EC6FB8A-29EB-49CF-9DBC-1A0D
C2273FF9&displaylang=en
Microsoft SOAP Toolkit Data Analyzer, In Data Analyzer and Metadata Manager, you can export a report to
Metadata Manager an Excel file and refresh the data in Excel directly from the cached
data in Data Analyzer or Metadata Manager or from the data source.
To use the data refresh feature, you must install the Microsoft SOAP
Toolkit. For information about downloading the Microsoft SOAP
Toolkit, see “Working with Microsoft Excel” in the Data Analyzer User
Guide.
Third-Party Software 43
Table 3-7. Third-Party Software
PowerCenter
Third-Party Software Description
Component
Adobe SVG Viewer Data Analyzer, In Data Analyzer and Metadata Manager, you can display interactive
Metadata Manager report charts and chart indicators. You can click on an interactive
chart to drill into the report data and view details and select sections
of the chart.
To view interactive charts on Internet Explorer, you must install Adobe
SVG Viewer. For more information about downloading Adobe SVG
Viewer, see “Managing Account Information” in the Data Analyzer
User Guide.
X Virtual Frame Buffer PowerCenter You can run activity reports to monitor user activity and license usage
Administration in the PowerCenter Administration Console.
Console To display the reports, the gateway node for the domain must be able
to display graphics. If the gateway node is an UNIX machine that
does not have a graphics card or a monitor, you must install and
configure X Virtual Frame Buffer (Xvfb).
For more information about installing Xvfb on UNIX, see “Step 11.
Install X Virtual Frame Buffer (Optional)” on page 73.

Code Pages
PowerCenter Client
Data Analyzer
Metadata Manager
PowerCenter uses code pages for the following components:

♦ PowerCenter Client. You can generate metadata in any language in the PowerCenter
Client. PowerCenter Client includes the Designer, Workflow Manager, Repository
Manager, and Workflow Monitor.
♦ Integration Service. The Integration Service can move data in ASCII mode and Unicode
mode. You set the code page when you configure each Integration Service process.
♦ PowerCenter repository. The PowerCenter repository can store data in any language. You
can use the UTF-8 code page for the repository to store multibyte data in the repository.
The code page for the repository is the same as the database code page. You set a code page
for the machine where Repository Service process runs.
♦ Sources and targets. The sources and targets store data in one or more languages. Use code
pages to specify the type of characters in the sources and targets.
♦ PowerCenter command line programs. You must also ensure that the code page for pmrep
is compatible with the repository code page and the code page for pmcmd is compatible
with the Integration Service process code page.
Verify that the code pages you select for PowerCenter components are compatible. For more
information about code pages, see “Understanding Globalization” in the PowerCenter
Administrator Guide.
Code Pages 45
Working with 32-bit and 64-bit Platforms
You can run PowerCenter Services on 32-bit or 64-bit platforms. A 64-bit architecture
provides a larger memory space that can significantly reduce or eliminate disk input/output.
This can improve session performance in the following areas:
♦ Caching. With a 64-bit platform, the Integration Service is not limited to the 2 GB cache
limit of a 32-bit platform.
♦ Data throughput. With a larger available memory space, the reader, writer, and Data
Transformation Manager (DTM) threads can process larger blocks of data.
You can run the PowerCenter 64-bit application on AIX, HP-UX, Red Hat Linux, SUSE
Linux, Solaris, and Windows.
Note: The PowerCenter 64-bit platform addresses up to 18 million terabytes (2^64 bytes) of
system memory and has up to 256 terabytes (2^48 bytes) available for a single application.
The 32-bit platform addresses up to 4 GB (2^32 bytes) of system memory and has up to 2 GB
available for any single application.
Running PowerCenter on 32-bit and 64-bit Platforms

When running PowerCenter on both 32-bit and 64-bit platforms, you must configure
PowerCenter to use the correct libraries, database clients, and session cache sizes.
Use the following guidelines when working with 32-bit and 64-bit platforms:
♦ Libraries. Link libraries according to the following guidelines:
− Link 32-bit applications with 32-bit libraries. Link 64-bit applications with 64-bit
libraries.
− Link 32-bit machines running an Integration Service with a 32-bit database client. Link
a 64-bit machine running an Integration Service with 64-bit database client.
♦ Database clients. Link 32-bit machines running a Repository Service with 32-bit database
clients. Link 64-bit machines running a Repository Service with 64-bit database clients.
♦ Integration Services and Repository Services. 32-bit and 64-bit machines that run
Integration Services and Repository Services are compatible with each other.
♦ Caching. If the total configured session cache size is 2 GB or greater (2,147,483,648
bytes), you must run the session using an Integration Service running on a 64-bit machine.
The session fails if you run it using an Integration Service running on a 32-bit machine.
♦ Server grids. A server grid can contain both 32-bit and 64-bit machines that run the
Integration Service. If the total configured session cache size is 2 GB (2,147,483,648
bytes) or greater, you must configure the session to run on an Integration Service on a
64-bit machine.

Migrating to a 64-bit Platform
You might want to migrate to a 64-bit platform to improve performance if you process large
volumes of data or perform memory-intensive transformations. Before you migrate, contact
your local sales representative for information about licensing. When you migrate from a
32-bit platform to a 64-bit platform, you must prepare the system and PowerCenter
environments.
Complete the following steps to prepare the system environment:
♦ Install current 64-bit database clients.
♦ Update the system library path to include only the 64-bit application and database client
libraries.
Complete the following steps to prepare the PowerCenter environment:
♦ Recompile procedures for Custom and External Procedure transformations using the
64-bit makefiles generated by the Designer.
♦ Increase cache sizes for Rank, Sorter, Aggregator, Joiner, and Lookup transformations that
may benefit from the increased addressable memory.
♦ Increase DTM buffer size and buffer block size for sessions that may benefit from the
increased memory.
Note: You do not need to update the PowerCenter Client or upgrade the repository if you
install the same product version of PowerCenter Services.
Working with 32-bit and 64-bit Platforms 47

Chapter 4
Before You Install

♦ Pre-Installation Tasks, 50
♦ Step 1. Create Databases, 52
♦ Step 2. Create Database User Accounts, 56
♦ Step 3. Install Database Client Software, 57
♦ Step 4. Create a System User Account, 58
♦ Step 5. Configure Environment Variables, 59
♦ Step 6. Establish Port Numbers, 66
♦ Step 7. Verify License Keys, 67
♦ Step 8. Configure Web Browser, 68
♦ Step 9. Install Languages (Optional), 69
♦ Step 10. Install the Application Server (Optional), 70
♦ Step 11. Install X Virtual Frame Buffer (Optional), 73
♦ Step 12. Prepare for Installation from a Hard Disk (Optional), 74
49
Pre-Installation Tasks
Informatica provides Quick Start guides on the PowerCenter Documentation DVD. You can
use the Quick Start guides to track the required installation information as you complete the
pre-installation steps. The Quick Start guides contain the required information for databases,
user accounts, system accounts, environment variables, and application servers. You will need
this information when you install PowerCenter.
You can get the Quick Start guides from the following location on the PowerCenter
Documentation DVD:
<DVD_Root>\Disk1\InstData\Documentation\PDFs\
For more information about installing PowerCenter documentation, see “Documentation

Installation” on page 291.
Before you install PowerCenter, complete the following tasks:
1. Create the databases. Create the databases for PowerCenter, Data Analyzer, and
Metadata Manager repositories, the PowerCenter domain configuration database, and the
Data Profiling warehouse. For more information, see “Step 1. Create Databases” on
page 52.
2. Create database user accounts. Create user accounts for the repository, domain
configuration, and Data Profiling warehouse databases. You need this user account
information when you install PowerCenter. For more information, see “Step 2. Create
Database User Accounts” on page 56.
3. Install database client software. Install database client software on the machines where
you install PowerCenter. For more information, see “Step 3. Install Database Client
Software” on page 57.
4. Create a system user account for installation. Create a user account to run the
installation. For more information, see “Step 4. Create a System User Account” on
page 58.
5. Configure environment variables. Configure environment variables for PowerCenter
Services, PowerCenter Client, and database connectivity on UNIX. For more
information, see “Step 5. Configure Environment Variables” on page 59.
6. Establish port numbers. Establish the port numbers used by PowerCenter Services on the
nodes in a domain. For more information, see “Step 6. Establish Port Numbers” on
page 66.
7. Verify license keys. Verify that you have the license keys required for installation. For
more information, see “Step 7. Verify License Keys” on page 67.
8. Configure the web browser. Configure the web browser you will use to access the
PowerCenter Administration Console, Data Analyzer, and Metadata Manager. For more
information, see “Step 8. Configure Web Browser” on page 68.
50 Chapter 4: Before You Install

9. Install languages (Optional). You may need to install additional languages on machines
that run the PowerCenter Client. For more information, see “Step 9. Install Languages
(Optional)” on page 69.
10. Install the application servers (Optional). The PowerCenter installer installs JBoss
Application Server during installation. Alternatively, you can install JBoss Application
Server, BEA WebLogic Server, or IBM WebSphere Application Server. For more
information, see “Step 10. Install the Application Server (Optional)” on page 70.
11. Install X Virtual Frame Buffer (Optional). On UNIX, the PowerCenter Administration
Console requires a graphics display server to display graphics for user activity and license
reporting features. You can install X Virtual Buffer on gateway nodes that do not have a
graphics display server. For more information, see “Step 11. Install X Virtual Frame
Buffer (Optional)” on page 73.
12. Configure the installer (Optional). You can install PowerCenter from a hard disk. For
more information, see “Step 12. Prepare for Installation from a Hard Disk (Optional)”
on page 74.
Pre-Installation Tasks 51
Step 1. Create Databases
This section contains guidelines for creating the required databases for PowerCenter
components. Depending on the PowerCenter components you install, you must set up the
required relational databases and user accounts.
You must set up a database for the following PowerCenter components:
♦ PowerCenter domain configuration
For more information about the required databases, database types, and database sizes, see
“Database Requirements” on page 38. For more information about setting up the database
user accounts, see “Step 2. Create Database User Accounts” on page 56.
PowerCenter Domain Configuration

The domain configuration database must be accessible by all gateway nodes in the domain.
You must create the domain configuration database before you install PowerCenter Services.
Use the following rules and guidelines when setting up the domain configuration database:
♦ The PowerCenter installer uses JDBC to communicate with the domain configuration
database. You do not need to configure database connectivity for the database.
♦ If you use a domain configuration database from a previous PowerCenter installation, you
must drop the existing domain configuration database tables from the database before you
install or use a different user account than the previous installation. For more information,
see “Uninstallation Rules and Guidelines” on page 386.
♦ On IBM DB2, make sure the primary tablespace for the domain configuration database
has a default page size of 16K.
♦ You can store the domain configuration database and the PowerCenter repository in one
database if you use the same database user name.
♦ Store the domain configuration database for different domains in separate user accounts.
For more information about the domain configuration database, see “Managing the Domain”
in the PowerCenter Administrator Guide.
Repository on Oracle
To prevent a PowerCenter, Data Analyzer, or Metadata Manager repository from using
excessive amounts of disk space, set the Oracle storage parameters for the tablespace.
When you set up an Oracle database, verify that the storage parameters specified for the
tablespace are not too large. Storage parameters that are set to very large values cause the

repository to use an excessive amount of space. Also verify that the default tablespace for the
user that owns the repository tables is set correctly.
The following example shows how to set the recommended storage parameters, assuming that
the repository is stored in the “REPOSITORY” tablespace:
ALTER TABLESPACE "REPOSITORY" DEFAULT STORAGE ( INITIAL 10K NEXT 10K
MAXEXTENTS UNLIMITED PCTINCREASE 50 );
Verify or change these parameters before you create the repository.
PowerCenter Repository on IBM DB2

When you set up an IBM DB2 database, the database administrator can define the database
on a single node. You can optimize repository performance on an IBM DB2 database when
you store a repository in a single-node tablespace. When the tablespace contains one node, the
PowerCenter Client and Integration Service access the repository faster than if the repository
tables exist on different database nodes.
Specify the single-node tablespace name when you create, copy, or restore a repository. The
Repository Service creates all repository tables in the same tablespace. The repository stores
the tablespace name so that when you upgrade the repository, the Repository Service uses the
same tablespace name.
If you do not specify the tablespace name when you create, copy, or restore a repository, the
DB2 system specifies the default tablespace for each repository table. The DB2 system may or
may not specify a single-node tablespace.
Note: If you have an existing IBM DB2 repository, you can back it up and restore it in a single-
node tablespace.
PowerCenter Repository on Sybase ASE

When you create a PowerCenter repository on Sybase ASE, set the Allow Nulls by Default
parameter to true for the database. When you set this option to true, any table created in the
repository database will have columns with the default value NULL, in compliance with SQL
standard.
Data Profiling Warehouse

You must create a separate Data Profiling warehouse for each PowerCenter repository. You can
create a Data Profiling warehouse on the same database instance as the PowerCenter
repository. When you install a new version of PowerCenter, you must upgrade each Data
Profiling warehouse.
For information about creating and upgrading a Data Profiling warehouse, see “Creating a
Data Profiling Warehouse” on page 331.
Step 1. Create Databases 53

Data Analyzer Repository on Sybase ASE
On Sybase ASE, the database for the Data Analyzer repository requires a page size of at least
8K. If you set up a Data Analyzer database on a Sybase ASE instance with a page size smaller
than 8K, Data Analyzer may generate errors when you run reports.
Typically, Data Analyzer includes a GROUP BY clause in the SQL query for the report.
When you run the report, Sybase ASE stores all GROUP BY and aggregate columns in a
temporary worktable. The maximum index row size of the worktable is limited by the
database page size.
For example, if Sybase ASE is installed with the default page size of 2K, the index row size
cannot exceed 600 bytes. However, the GROUP BY clause in the SQL query for most Data
Analyzer reports generates an index row size larger than 600 bytes.
Sybase ASE relaxes the row size restriction when you increase the page size. A page size of at
least 8K for the Data Analyzer repository is sufficient to handle the Data Analyzer reports.
If Sybase ASE is installed with the default page size of 2K, you must create a new Sybase ASE
instance with a page size of at least 8K. Then, set up the Data Analyzer repository database on
the new instance.
For more information about how Sybase ASE evaluates GROUP BY clauses, see the following
document on the Sybase website:
http://infocenter.sybase.com/help/index.jsp?topic=/
com.sybase.help.ase_15.0.commands/html/commands/commands60.htm
Data Analyzer Repository on Microsoft SQL Server

Install Microsoft SQL Server 2000 or 2005 with case-sensitive collation.
A Data Analyzer repository on Microsoft SQL Server 2005 must have a database
compatibility level of 80 or earlier. Data Analyzer uses several non-ANSI SQL statements that
Microsoft SQL Server supports only on a database with a compatibility level of 80 or earlier.
To set the database compatibility level to 80, run the following query against the database:
sp_dbcmptlevel ‘<DatabaseName>’, 80
Or open the Microsoft SQL Server Enterprise Manager, right-click the database, and select
Properties > Options. Set the Compatibility Level to 80 and click OK.
Data Analyzer and Metadata Manager Repository on Sybase ASE

If you use Sybase ASE for the Data Analyzer or Metadata Manager repository database, the
database server must have the Distributed Transaction Management (DTM) option enabled.
The user account used to create the Data Analyzer or Metadata Manager repository must have
the Sybase role dtm_tm_role.

Metadata Manager Repository and Source Repository on IBM DB2
If the Metadata Manager repository or a source repository resides on an IBM DB2 database,
you need to configure the system temporary tablespaces and reset the minimum heap sizes.
When you create the Metadata Manager repository on a DB2 database, most of the tables are
created with default tablespace page sizes of 4 KB. Other tables require larger page sizes, such
as 8 KB, 16 KB, and 32 KB.
When Metadata Manager sorts rows returned by database queries from tables with tablespace
sizes larger than the default 4 KB, the database uses the System Temporary tablespace with the
same page size as the table being sorted. Metadata Manager uses the System Temporary
tablespace to store the data during the sorting process. If the database server cannot find the
required System Temporary tablespace, the server displays the following error:
SQL 1585N A system temporary table space with sufficient page size does
not exist. SQLSTATE=54048
Before you install PowerCenter, ask the DB2 administrator to create system temporary
tablespaces with 4 KB, 8 KB, 16 KB, and 32 KB page sizes.
The Metadata Manager repository and all Metadata Manager source repositories on IBM
DB2 require minimum heap sizes.
Ask the DB2 database administrator to run the following SQL statements on each database to
configure the system temporary tablespaces and update the heap sizes:
CREATE Bufferpool RBF IMMEDIATE SIZE 1000 PAGESIZE 32 K EXTENDED STORAGE
;
CREATE Bufferpool STBF IMMEDIATE SIZE 2000 PAGESIZE 32 K EXTENDED

STORAGE ;
CREATE REGULAR TABLESPACE REGTS32 PAGESIZE 32 K MANAGED BY SYSTEM USING

('C:\DB2\NODE0000\reg32' ) EXTENTSIZE 16 OVERHEAD 10.5 PREFETCHSIZE 16
TRANSFERRATE 0.33 BUFFERPOOL RBF;
CREATE SYSTEM TEMPORARY TABLESPACE TEMP32 PAGESIZE 32 K MANAGED BY

SYSTEM USING ('C:\DB2\NODE0000\temp32' ) EXTENTSIZE 16 OVERHEAD 10.5
PREFETCHSIZE 16 TRANSFERRATE 0.33 BUFFERPOOL STBF;
GRANT USE OF TABLESPACE REGTS32 TO USER <USERNAME>;
UPDATE DB CFG FOR <DB NAME> USING APP_CTL_HEAP_SZ 16384
UPDATE DB CFG FOR <DB NAME> USING APPLHEAPSZ 16384
UPDATE DBM CFG USING QUERY_HEAP_SZ 8000
UPDATE DB CFG FOR <DB NAME> USING LOGPRIMARY 100
UPDATE DB CFG FOR <DB NAME> USING LOGFILSIZ 2000
UPDATE DB CFG FOR <DB NAME> USING LOCKLIST 1000
UPDATE DB CFG FOR <DB NAME> USING DBHEAP 2400
"FORCE APPLICATIONS ALL"
DB2STOP
DB2START
Step 1. Create Databases 55

Step 2. Create Database User Accounts
Before you install PowerCenter, set up the database user accounts for PowerCenter
components. If you want to use one database for each repository, each repository must have
its own database user account.
You need a database user account for each repository. The database user account must have
permissions to create and drop tables, indexes, and views and to select, insert, update, and
delete data from tables. When you create the password for the account, use 7-bit ASCII only.
Write down the user names and passwords. You need the user names and passwords during
the installation.
Create the following database user accounts for the following PowerCenter components:
♦ Domain configuration
Rules and Guidelines

Use the following rules and guidelines when creating a database user account:
♦ If you use Oracle 10.2 for a repository database, you must also grant create view privileges
to the repository database user. The create view permission is granted independent of the
Connect privilege in Oracle 10.2.
♦ If you use Sybase ASE for the Data Analyzer or Metadata Manager repository, you must
add the role dtm_tm_role to the database user account.

Step 3. Install Database Client Software
Before you install PowerCenter, install and configure the appropriate database client software
on the machine where the Integration Service or Repository Service runs. In a single machine
installation, you must install and configure the appropriate database client software on the
machine where you install PowerCenter Services. In a multiple machine setup, you must
install and configure the appropriate database client software on the machines that run
Repository Service or Integration Service processes.
Install the following database clients on machines that run Repository Service processes:
♦ Oracle client
♦ IBM DB2 Client Application Enabler (CAE)
♦ Microsoft SQL Client, with Microsoft OLE DB provider for Microsoft SQL Server
♦ Sybase Open Client
Install the following database clients on machines that run Integration Service processes:
♦ Oracle client
♦ IBM DB2 Client Application Enabler (CAE)
♦ Informix ESQL for C, Informix Client SDK, or any other Informix client software
♦ Microsoft SQL Client, with Microsoft OLE DB provider for Microsoft SQL Server
♦ Sybase Open Client
♦ Teradata BTEQ client
For more information about connecting to databases in PowerCenter, see “Connecting to
Databases from Windows” on page 487 and “Connecting to Databases from UNIX” on
page 503.
Step 3. Install Database Client Software 57

Step 4. Create a System User Account
Before you install PowerCenter components, you need to create a Windows or UNIX user
account to perform the installation.
Windows User Account

On Windows, you can install PowerCenter Services with the user account logged in to the
machine or you can use another user account. You can create either a local or domain
account. Create a domain account if you want to access a repository on a Microsoft SQL
Server database that uses Windows integrated security.
The permissions required depend on the user account you use to run Informatica Services:
♦ Logged in user account. The user account must be a member of the Administrators group
and have the Log on as a service permission. You must log in with this user account before
you install PowerCenter.
♦ Another user account. The user account must be a member of the Administrators group
and have Log on as a service and Act as operating system permissions. You do not have to log
in with this user account before you install PowerCenter.
If you install Data Analyzer or Metadata Manager on IBM WebSphere Application Server,
you must create a user account named padaemon to install Data Analyzer or Metadata
Manager on IBM WebSphere Application Server. You must then install Data Analyzer or
Metadata Manager using the same user account. For more information about the IBM
WebSphere Application Server requirements, see “IBM WebSphere Application Server
Prerequisites” on page 41.
UNIX User Account

On UNIX, you might want to create a user account specifically to run Informatica Services.
You can also create a new user if you want to restrict the number of users on the UNIX system
who can run the servers.
If you install Data Analyzer or Metadata Manager on IBM WebSphere Application Server,
you must create a user account named padaemon and add the user to the mqm and mqbrkrs
user groups. You must install Data Analyzer or Metadata Manager using this user account. For
more information about the IBM WebSphere Application Server requirements, see “IBM
WebSphere Application Server Prerequisites” on page 41.
Log in with the user account you create in this step before you set the UNIX environment
variables in the next step. For more information about setting the UNIX environment
variables, see “Step 5. Configure Environment Variables” on page 59.

Step 5. Configure Environment Variables
You must configure the database environment on UNIX and Windows to run the
PowerCenter installer. In addition, you can configure other PowerCenter environment
variables before you install PowerCenter.
Table 4-1 describes the required and optional environment variables for UNIX and Windows:
Table 4-1. PowerCenter Environment Variables
Operating Required/
Variable Type Description
System Optional
Database client UNIX Required Location of the database client. For more information, see
“Database Client Environment Variables” on page 60.
Library path UNIX Required Location of the database client libraries. For more information,
see “Library Path Environment Variables” on page 60.
Locale UNIX Required Language setting for UNIX machines. For more information, see
“Locale Environment Variables” on page 61.
Java components AIX Required Java Runtime Environment location for Java-based components.
HP-UX For more information, see “Java Component Variables” on
page 62.
libstdc++.so.5 Linux Required Location of GCC 3.2.x library. For more information, see
“libstdc++.so.5 Library” on page 62.
X Window Server UNIX Optional Location of graphics display server. Configure to use the
PowerCenter graphical mode installer. For more information,
see “X Window Server” on page 63.
PowerCenter Windows Optional You use these variables to configure the following PowerCenter
Services UNIX Services properties:
- Designate the PowerCenter Services installation directory.
- Designate the location of domains.infa.
- PowerCenter Services memory usage.
For more information, see “PowerCenter Services Environment
Variables” on page 63.
Configuring Environment Variables on UNIX

Use the following rules and guidelines when you configure environment variables on UNIX:
♦ The PowerCenter installer relies on the database environment variables to gain access to
the databases. After you install the database client software, verify that the database
environment variables are set to the right values. For more information, see “Testing the
Database Connection on UNIX” on page 65.
♦ Verify that the existing environment variables do not contain earlier versions of
PowerCenter in the PATH or library path environment variables.
Step 5. Configure Environment Variables 59

♦ Log in with the UNIX user account you create for the installation before you configure
environment variables. For more information, see in “Step 4. Create a System User
Account” on page 58.
♦ If you are installing Data Analyzer or Metadata Manager without PowerCenter Services,
you do not need to set the UNIX environment variables.
For more information about configuring database environment variables, see “Connecting to
Databases from UNIX” on page 503.
Database Client Environment Variables

The database client path variable name and requirements vary based on the UNIX platform
and repository database.
Table 4-2 describes the database environment variables you need to set in UNIX:
Table 4-2. UNIX Database Environment Variables
Database Environment Variable Name Value
Oracle ORACLE_HOME Set to: <DatabasePath>

PATH Add: <DatabasePath>/bin
DB2 DB2DIR Set to: <DatabasePath>

DB2INSTANCE Set to: <DB2InstanceName>
PATH Add: <DatabasePath>/bin
Sybase ASE SYBASE12 or SYBASE15 Set to: <DatabasePath>/sybase<version>

SYBASE_ASE Set to: ${SYBASE[12 | 15]}/ASE-<version>
SYBASE_OCS Set to: ${SYBASE[12 | 15]}/OCS-<version>
PATH Add: ${SYBASE_ASE}/bin:${SYBASE_OCS}/bin:$PATH
Library Path Environment Variables

The library path variable name and requirements varies based on the UNIX platform and
database.
Table 4-3 describes the library path environment variables you need to set in UNIX:
Table 4-3. UNIX Library Path Environment Variable
UNIX Platform and

Value for Oracle Value for DB2 Value for Sybase ASE
Variable Name
Solaris and Linux: <DatabasePath>/lib <DatabasePath>/lib "${SYBASE_OCS}/lib:${SYBASE_ASE}/lib:

LD_LIBRARY_PATH ${LD_LIBRARY_PATH}"
AIX: LIBPATH <DatabasePath>/lib <DatabasePath>/lib "${SYBASE_OCS}/lib:

${SYBASE_ASE}/lib:${LIBPATH}"
HP-UX: <DatabasePath>/lib <DatabasePath>/lib "${SYBASE_OCS}/lib:

SHLIB_PATH ${SYBASE_ASE}/lib:${SHLIBPATH}"

Locale Environment Variables
Use LANG, LC_CTYPE, or LC_ALL to set the UNIX code page. The installer uses the value
of the locale environment variable to generate the list of compatible code pages you can use to
create a repository or connect to an existing repository. If the locale is not correctly set, the
installer cannot connect to an existing repository or generates an error when it creates a new
repository.
You can set LANG equal to ‘C’ for US-English systems. If you want to create a repository
when you install PowerCenter, set the locale depending on the type of code page you want for
the repository and the type of data you want to process with the Integration Service. When
you create a Repository Service and repository with the installer, the installer creates the
Integration Service with the same code page as the Repository Service.
If you use an existing repository, make sure the locale setting is compatible with the code page
for the existing repository. If the locale setting is not compatible with the code page for the
existing repository, Repository Service creation fails during installation.
For more information about code pages in PowerCenter, see “Understanding Globalization”
in the PowerCenter Administrator Guide.
For Oracle database clients, set NLS_LANG to the locale (language, territory, and character
set) you want the database client and server to use with the login. The value of this variable
depends on the configuration. For example, if the value is american_america.UTF8, you must
configure the variable as follows in a C shell:
setenv NLS_LANG american_america.UTF8
Note: Each type of UNIX operating system may require a different value for the same locale.
The locale value is case sensitive.
Verifying the Locale Setting

You can verify that the locale settings match the code page settings for your machine by using
the following command:
locale -a
The command returns the languages installed on the UNIX system and the existing locale
settings. Use this command to verify that the value for the locale environment variable is
compatible the language settings for the machine and the type of code page you want to use
for the repository.
Setting the Locale on Linux

All UNIX operating systems, except Linux, have a unique value for each locale. Linux allows
different values to represent the same locale. For example, "utf8," "UTF-8," "UTF8," and
"utf-8” represent the same locale on a Linux machine. PowerCenter requires that you use a
specific value for each locale on a Linux machine. Make sure that you set the LANG string
appropriately for all Linux machines. For more information about valid values for LANG
environment variable, see “LANG Environment Variable for Linux” on page 557.

Java Component Variables
PowerCenter installs the JRE to use with the following Java-based components:
♦ Custom transformation that uses Java coding
♦ Java transformation
♦ PowerCenter Connect for JMS
♦ PowerCenter Connect for Web Services
♦ PowerCenter Connect for webMethods
To use these components on AIX32, AIX64, or HP-UX, you must configure the library path
environment variables to point to the java directory installed with PowerCenter Services. You
need to configure these environment variables on machines where the Integration Service
process runs. You do not need to configure these variables for Linux or Solaris.
Table 4-4 describes the library paths you must configure to use Java-based components:
Table 4-4. AIX and HP-UX Library Path Environment Variables
UNIX Platform Environment Variable Name Value
AIX32 and AIX64 LIBPATH Set to: java/jre/bin

Set to: java/jre/bin/classic
Set to: /usr/lib:/lib
HP-UX SHLIB_PATH Set to: java/jre/lib/PA_RISC2.0/server

Set to: java/jre/lib/PA_RISC2.0
Set to: /usr/lib:/lib
libstdc++.so.5 Library
Before you install PowerCenter Services on Linux, you must install the GCC 3.2.x library
libstdc++.so.5 and add the location of the library to the library path environment variable.
Use the following command to verify that libstdc++ is installed:
$ rpm -q --whatprovides /usr/lib/libstdc++.so.5
If the command returns libstdc++-3.2-7, the library is properly installed. Otherwise, the
command returns error: file /usr/lib/libstdc++.so.5: No such file or directory.
If the library is not installed, you can locate and install the libstdc++.so.5 RPM at the
following URL:
http://rpmfind.net
If you have problems installing PowerCenter after installing the library, contact Global
Customer Support.

X Window Server
The graphical mode PowerCenter installer requires a graphics display server. The graphics
display server enables the installer to display graphics. Without the graphics display server, the
installer generates error messages.
On UNIX, the graphics display server is typically an X Window server. If you do not have the
X Window server installed on the machine where you want to install PowerCenter, you can
install it using an X Window server installed on another machine. You can redirect the
DISPLAY variable to use the X Window server on another UNIX machine.
To redirect the host output, define the environment variable DISPLAY. Use the following
command:
C shell:
setenv DISPLAY=<TCP/IP node of XWindows server>:0
Bash/Korn shell:
export DISPLAY=”<TCP/IP node of XWindows server>:0”
Bourne Shell:
DISPLAY=”<TCP/IP node of XWindows server>:0”
export display
For example, if you have the X Window server installed on a machine with a TCP/IP node of
10.1.50.23, use the following commands:
C shell:
setenv DISPLAY 10.1.50.23:0
Bash/Korn shell:
export DISPLAY=”10.1.50.23:0”
Bourne shell:
DISPLAY=”10.1.50.23:0”
export display
If you do not know the IP address of a UNIX machine where the X Window server is
installed, ask your network administrator. For more information about redirecting the
DISPLAY variable, see the documentation from the UNIX vendor.
If the X Window server does not support the font that the PowerCenter installer uses, the
installer may not display the labels on the buttons correctly. For example, the button labeled
Test Connection may appear with the shortened label Test Connecti....
PowerCenter Services Environment Variables

By default, you do not need to set any environment variable to run PowerCenter Services.
However, depending on your installation and configuration requirements, you may want to
configure environment variables before installing PowerCenter.

You can configure IINFA_JAVA_OPTS and INFA_DOMAINS_FILE. Configure the
environment variables on UNIX or configure the environment variable as a system variable on
Windows. Configure these variables if you install PowerCenter Services or the PowerCenter
Client.
You can also configure the INFA_HOME environment variable after you install PowerCenter
Services. Configure INFA_HOME to the location of the PowerCenter Services installation
directory or the directory where the installed PowerCenter Services files are located. For more
information, see “Configuring INFA_HOME” on page 357.
INFA_JAVA_OPTS
PowerCenter uses the Java Runtime Environment (JRE) to start and run PowerCenter
Services. By default, PowerCenter Services uses a maximum of 512 MB of system memory.
You can configure the amount of system memory used by PowerCenter Services with
INFA_JAVA_OPTS. If you set INFA_JAVA_OPTS after starting PowerCenter Services, you
must restart the node for the changes to take effect.
For example, to configure 1 GB of system memory for PowerCenter Services on UNIX in a C
shell, use the following command:
setenv INFA_JAVA_OPTS -Xmx1024m
Note: If you are using 64-bit HP-UX on Itanium, add the -d64 switch when you set the system
memory using INFA_JAVA_OPTS.
INFA_DOMAINS_FILE
The domains.infa file contains the connectivity information for the gateway nodes in a
domain. The connectivity information includes the domain names, domain host names, and
domain host port numbers. Configure INFA_DOMAINS_FILE as a system variable on
Windows machines. You must include the file name in the path. You can configure this
variable before installation or after installation.
Configure the variable on the machines that will run the following PowerCenter components:
♦ PowerCenter Services. The installer creates domains.infa in the PowerCenter installation
directory when you install PowerCenter Services for use by the infacmd command line
program. You must also set this variable if you run the pmcmd command line program
from a directory other than the server/bin directory.
♦ PowerCenter Client. The PowerCenter Client creates or updates domains.infa when you
add or modify domain connectivity information in any PowerCenter Client application.
If you want to keep the domains.infa file in a location other than PowerCenter Client
installation directory, you can configure INFA_DOMAINS_FILE on the machine where
you install the PowerCenter Client.
For example, you can use a shared location for domains.infa for all PowerCenter Client
installations in a highly available environment. You can set the INFA_DOMAINS_FILE
environment variable to the shared location on each machine where you install the
PowerCenter Client application. Each PowerCenter Client application uses the same
domain connectivity information.

Testing the Database Connection on UNIX
After you configure the database environment variables, you can test the connection to the
database from the database client before you install PowerCenter Services.
Use the following commands to test the database connection:
♦ sqlplus. Use sqlplus to test the connection between the database client and an Oracle
database.
♦ db2 connect. Use db2 connect to test the connection between an IBM DB2 database
client and the database.
♦ isql. Use isql to test the connection between a Sybase ASE database client and the
database.

Step 6. Establish Port Numbers
When you install PowerCenter Services, you must configure the port numbers for the gateway
and worker nodes and the range of port numbers used by application service processes on the
nodes in the domain. Before you install, you must establish the port numbers used by
PowerCenter Services and verify that the ports are available on the machines where you install
PowerCenter Services.
The PowerCenter installer uses default values for PowerCenter Services. You can configure
different port numbers when you install PowerCenter.
Note: When you create a domain, the node port number is the gateway port number. When
you join a domain, the node port number is a worker node port number.
Table 4-5 describes the port numbers used by PowerCenter Services:
Table 4-5. Port Numbers for PowerCenter Services
Port Type Default Value Description
Gateway Node 6001 Port number for a gateway node in a domain. The Service Manager
listens for incoming connection requests on this port. All client
applications communicate with the domain using this port number. The
installer also sets the shutdown port number as the node port number
plus one.
Worker Node 6001 Port number for a worker node in a domain. The Service Manager on the
gateway node communicates with the worker node using this port
number. The installer also sets the shutdown port number as the node
port number plus one.
If you promote a worker node to a gateway node, the port number
becomes a gateway node port number.
Application Service 6005 - 6105 Range of port numbers used by client applications to communicate with
Processes Repository Service, Integration Service, and SAP BW Service processes
on gateway and worker nodes. When the Service Manager starts an
application service, it starts the service process on the first available
port in this range.
At a minimum, the range must be equal to the number of application
service processes that will run on the node. PowerCenter Client
applications and application services communicate with the application
service processes on a node using a port number in this range.
This port range is similar to the PowerCenter Server and Repository
Server port numbers in PowerCenter 6.x/7.x.

Step 7. Verify License Keys
Informatica provides a license key for PowerCenter and a license key for Data Analyzer and
Metadata Manager.
Before you install the software, verify that you have the license keys available. Contact Global
Customer Support if you do not have license keys.
Informatica ships the PowerCenter license keys in different media based on the method that
you obtain the PowerCenter installation files. You can get the PowerCenter installation files in
two ways:
♦ Installation DVD. If you receive the PowerCenter installation files on the PowerCenter
Standard or Advanced Edition DVD, the license key files are included on the PowerCenter
License Key CD.
♦ FTP download. If you download the PowerCenter installation files from the Informatica
FTP site, the license keys are included as part of an email message.
Use the following rules and guidelines when verifying the license key:
♦ If you use an incremental license to install Metadata Manager and join a domain, verify
that the incremental license is an incremental license for an existing domain license object.
Otherwise, the installer cannot create the Repository Service and the installation will fail.
♦ If you have an incremental license key, you can join a domain when you install
PowerCenter. If you want to create a domain, contact Global Customer Support to obtain
a full license key for PowerCenter Services.
Step 7. Verify License Keys 67

Step 8. Configure Web Browser
Configure your browser to properly access the PowerCenter Administration Console, Data
Analyzer, and Metadata Manager. You can use Microsoft Internet Explorer and Mozilla
Firefox to access the Administration Console and Data Analyzer. You can use Internet
Explorer with Metadata Manager.
You must configure the following options in the browser you use to access the Administration
Console, Data Analyzer, and Metadata Manager:
♦ Scripting and ActiveX. Internet Explorer requires the Active scripting, Allow paste
operations, Run ActiveX controls and plug-ins, and Script ActiveX controls marked safe
for scripting controls enabled. Choose Tools > Internet Options > Security > Custom level
to configure the controls.
♦ Javascript. Firefox requires Javascript enabled.
♦ Pop-up blocking utility. To display the Data Analyzer and Metadata Manager pages
properly, disable any pop-up blocking utility on your browser. If a pop-up blocker is
running while you are working with Data Analyzer or Metadata Manager, the Data
Analyzer or Metadata Manager windows may not display properly.

Step 9. Install Languages (Optional)
You may need to install additional languages on Windows for use with the PowerCenter
Client. For example, you may need to install languages to view languages other than the
system locale when working with repositories that use a UTF-8 code page. You also must
install languages to use the Windows Input Method Editor (IME).
To install languages:
1. Click Start > Settings > Control Panel.

2. Click Regional Options.
3. Under Language settings for the system, select the languages you want to install.
4. Click Apply.
Note: Windows may require you to reboot your system.
For more information about IME and code pages, see “Globalization Overview” in the
PowerCenter Administrator Guide.
Step 9. Install Languages (Optional) 69

Step 10. Install the Application Server (Optional)
Data Analyzer and Metadata Manager are web applications that require an application server.
This section lists guidelines to follow when you install the application servers for Data
Analyzer or Metadata Manager.
You can use one of the following application servers:
♦ JBoss Application Server. You can install Data Analyzer and Metadata Manager on a new
or existing instance of JBoss Application Server. For more information about installing
JBoss Application Server, see “JBoss Application Server” on page 70.
♦ BEA WebLogic Server. You can install Data Analyzer and Metadata Manager on a new
WebLogic domain or an existing domain. For more information about installing
WebLogic Server, see “BEA WebLogic Server” on page 71.
♦ IBM WebSphere Application Server. You can install Data Analyzer and Metadata
Manager on an existing WebSphere Application Server instance. For more information
about installing WebSphere Application Server, see “IBM WebSphere Application Server”
on page 71.
If you run Data Analyzer and Metadata Manager on BEA WebLogic Server or IBM
WebSphere Application Server, you must obtain and install the application server before you
install PowerCenter.
You must stop the application server before you install Data Analyzer and Metadata Manager.
For more information about stopping the application server, see “Starting and Stopping
Note: The installer can configure repository authentication for JBoss Application Server, BEA
WebLogic Server, and IBM WebSphere Application Server during installation. If you do not
configure authentication during installation, you must configure authentication before you
install PowerCenter. Otherwise, you cannot log in to Data Analyzer or Metadata Manager
until you configure authentication. For more information about configuring authentication,
see “Configuring Authentication” in the Data Analyzer Administrator Guide and “Managing
Authentication for Metadata Manager” in the Metadata Manager Administrator Guide.
JBoss Application Server

You can install Data Analyzer and Metadata Manager on a new or existing instance of JBoss
Application Server.
If you want to install Data Analyzer or Metadata Manager on an existing instance, you must
install JBoss Application Server and create a server configuration before you install
PowerCenter. The server configuration must support all available JBoss Application Server
services.
JBoss Application Server provides several predefined server configurations. The All server
configuration starts all available services. To create a server configuration for PowerCenter,
you can copy the predefined All server configuration directory in JBoss Application Server
and rename the new configuration directory.

When you install Data Analyzer and Metadata Manager on an existing JBoss Application
Server instance, you provide the location of the application server and the name of the new
server configuration directory during installation.
BEA WebLogic Server

When you install Data Analyzer or Metadata Manager to run on BEA WebLogic Server, you
can choose to install Data Analyzer or Metadata Manager on a new or existing WebLogic
domain. If you install Data Analyzer or Metadata Manager on a new domain, the
PowerCenter installation creates the WebLogic domain with the name you provide. The
default domain name is Informatica.
If you install Data Analyzer or Metadata Manager on an existing domain, you must create the
domain before you install PowerCenter. You can use the BEA WebLogic Server Configuration
Wizard to create a new WebLogic domain.
The PowerCenter installation configures Data Analyzer and Metadata Manager to run on the
default server, myserver, of the domain where the web applications are installed.
IBM WebSphere Application Server

Before you install PowerCenter, you must install one of the following IBM WebSphere
Application Server editions:
♦ IBM WebSphere Application Server Base Edition
♦ IBM WebSphere Application Server Network Deployment Edition
The installer can install Data Analyzer and Metadata Manager on the Network Deployment
edition of IBM WebSphere Application Server. Although the PowerCenter installation does
not set up a WebSphere cluster for Data Analyzer and Metadata Manager, it sets up an
environment that makes it easy to create a cluster later.
During the PowerCenter installation, you can provide the name of the server to run Data
Analyzer and Metadata Manager. If you do not provide a server name, the PowerCenter
installer configures Data Analyzer and Metadata Manager to run on the default server, server1.
Before you install IBM WebSphere Application Server, complete the following tasks:
♦ Create padaemon user account. On Windows and UNIX, create the padaemon user
account to install and run WebSphere Application Server. For more information, see
“Create padaemon User Account” on page 71.
♦ Create user groups. On UNIX, create the mqm and mqbrkrs user groups. For more
information, see “Create User Groups” on page 72.
Create padaemon User Account

You must create the padaemon user account to install and run IBM WebSphere Application
Server. Create the user account with the padaemon/ padaemon user name and password.
Step 10. Install the Application Server (Optional) 71

The padaemon user account must be a member of the Administrators group and have the
following rights:
♦ Act as part of the operating system
♦ Log on as a service
For information about creating a user account with advanced rights, see the Microsoft
Windows documentation.
Create User Groups

Before you install IBM WebSphere Application Server on UNIX, complete the following
tasks:
1. Create the following groups:
mqm
mqbrkrs
2. Add the root account to these groups.

3. Log in as root.
You need to use the root account to install IBM WebSphere Application Server.
For more information about setting up the required UNIX operating system groups before
installing IBM WebSphere Application Server, see platform-specific installation tips on the
IBM Information Center web site:
http://publib.boulder.ibm.com/infocenter/ws51help/index.jsp
Expand WebSphere Application Server, Version 5.1.x > Installing > Getting started >
Installing the product. Click Platform-specific Tips for Installing and Migrating > Tips for
Installing the Embedded Messaging Feature. In the Tips for all Linux and UNIX Platforms
section, click Defining the Prerequisite Linux or UNIX operating System Groups, mqm and
mqbrkrs.

Step 11. Install X Virtual Frame Buffer (Optional)
On UNIX, the PowerCenter Administration Console requires a graphics display server to
display Domain Activity Monitoring reports. If you do not have a graphics display server, you
can install and configure X Virtual Frame Buffer (Xvfb) to display graphics.
The X Virtual Frame Buffer is an X server that renders graphics to virtual memory rather than
to a graphics display device. It can run on a UNIX machine that does not have a graphics card
or monitor.
HP-UX
Xvfb is part of the HP-UX operating system. Depending on when you installed or last
patched the operating system, you might need to download and install HP-UX patches and
graphical packages to run Xvfb. For a description of the steps you need to complete to run
Xvfb on HP-UX, see the instructions on the following web site:
http://publib.boulder.ibm.com/tividd/td/ITM/GI10-5797-01/en_US/HTML/
notesmst20.htm
AIX and Linux

On AIX and Linux, you must download and install X Virtual Frame Buffer. For a description
of the steps you need to complete to run Xvfb on AIX and Linux, see the instructions on the
following web site:
http://publib.boulder.ibm.com/infocenter/iwphelp/v2r5m1/index.jsp?topic=/
com.ibm.wcs.ic.doc_2.5.1/install/i_inst_t_lwpsetup_xfvb_on_unx.html
Solaris
You can download the Xvfb server for Solaris from the following web site:
ftp://www.ferret.noaa.gov/special_request/xvfb/solaris/
To set up the Xvfb server, follow the instructions in the README.XVFB. Or read the
instructions in the following web site:
http://ferret.wrc.noaa.gov/Ferret/FAQ/graphics/Solaris_Xvfb.html
Use the following command to start up the virtual frame buffer:

% /usr/X11R6/bin/Xvfb :1 -screen 0 1152x900x8 &
This sends any graphics output going to display 1 to shared memory.

Use the following command to set the current display to use the frame buffer for graphics
display in a C shell:
% setenv DISPLAY :1.0
Step 11. Install X Virtual Frame Buffer (Optional) 73

Step 12. Prepare for Installation from a Hard Disk
(Optional)
If you want to copy the PowerCenter installation files from the DVD or FTP site and install
from the hard disk, you must use the same directory structure as in the downloaded files or
installation DVD and copy specific files.
Copy the Disk1 directory (including all files and subdirectories) from the download location
or the installation DVD to the hard disk. The /disk1 directory contains all the installation
files required for the PowerCenter installation. The directory in the temporary directory must
match the directory in the download location or installation DVD. In the temporary
directory on the hard disk, locate and run the installation file for your operating system.
Table 4-6 describes the directories, files, and disk space you need to copy to a temporary
directory on the hard disk before you install PowerCenter from the hard drive:
Table 4-6. Directories and Files Required for Installation
PowerCenter
Required Files and Directories Installation File Disk Space
Component
PowerCenter Copy the following directories: Copy lax.jar, install.lax, and 550 MB
(Windows) <DVD_Root>\Server\Windows\Disk1 install.exe from the
<DVD_Root>\jre <DVD_Root> and run
install.exe.
PowerCenter Copy the following directory for the Copy install.sh and 650 MB
(UNIX) platform where you want to install: english.msg from
<DVD_Root>/Server/<platform>/Disk1 <DVD_Root> and run
install.sh.
PowerCenter Copy the following directories: Copy lax.jar, install.lax, and 350 MB
Client <DVD_Root>\Client\Windows\Disk1 install.exe from the
(Windows) <DVD_Root>\jre <DVD_Root> and run
install.exe.
PowerCenter Copy the following directory: Copy lax.jar, install.lax, and 30 MB

Reports <DVD_Root>\Reports\Windows\Disk1 install.exe from the
(Windows) <DVD_Root>\jre <DVD_Root> and run
install.exe.
PowerCenter Copy the following directory for the Copy install_reports.sh and 70 MB
Reports platform where you want to install: english.msg from
(UNIX) <DVD_Root>/Reports/<platform>/Disk1 <DVD_Root> and run
install_reports.sh.
Note: You must keep the same Server, Reports, and Client directory structure as on the DVD. On UNIX, install.sh requires the Server
directory and install_reports.sh requires the Reports directory. On Windows, install.exe requires the Server, Client, and Reports directory.
After you copy the required directories and files, go to the temporary directory and run the
installation file for your operating system.

For example, to install PowerCenter from the hard disk on a Solaris machine:
1. Create a Server directory in a temporary directory:
<Temp_dir>/Server
2. Create a Solaris directory in the /Server temporary directory:

<Temp_dir>/Server/Solaris
3. Copy the <DVD_Root>/Server/Solaris/Disk1 directory from installation DVD to the

temporary directory:
<Temp_dir>/Server/Solaris/Disk1
4. Copy <DVD_Root>/install.sh and <DVD_Root>/english.msg to the temporary

directory:
<Temp_dir>/install.sh
<Temp_dir>/english.msg
5. Run install.sh.
Note: You may experience decreased performance if you run the PowerCenter installer from a
network location. For optimal performance when installing PowerCenter from a network
location, for example, over a WAN, use the console mode installer.
Step 12. Prepare for Installation from a Hard Disk (Optional) 75

Chapter 5
Before You Upgrade

♦ Overview, 78
♦ PowerCenter Version 6.x/7.x Pre-Upgrade Steps, 79
♦ PowerCenter Version 8.0 Pre-Upgrade Steps, 82
♦ PowerCenter 8.1 Pre-Upgrade Steps, 84
♦ Preparing the Repository for Upgrade, 86
♦ Backing Up and Copying Configuration Files, 89
♦ Data Analyzer Pre-Upgrade Steps, 93
♦ Metadata Manager Pre-Upgrade Steps, 96
77
Overview
This chapter includes information about the tasks you must complete before you begin the
upgrade process.
The tasks depend on the PowerCenter component and version you upgrade:
♦ PowerCenter 6.x/7.x. Before you upgrade PowerCenter 6.x/7.x, you must establish the
PowerCenter installation environment, prepare the repository for the upgrade, and back
up files. For more information, see “PowerCenter Version 6.x/7.x Pre-Upgrade Steps” on
page 79.
♦ PowerCenter 8.0. Before you upgrade PowerCenter 8.0, you must prepare the repository,
note the domain configuration and stop Informatica Services, remove environment
variables, and back up files. For more information, see “PowerCenter Version 8.0 Pre-
Upgrade Steps” on page 82.
♦ PowerCenter 8.1. Before you upgrade PowerCenter 8.1, you must back up domain and
node configuration metadata and stop Informatica Services. For more information, see
♦ Data Analyzer version 8.0 or earlier. Before you upgrade Data Analyzer, you must prepare
the repository and back up customized files. For more information, see “Data Analyzer
Pre-Upgrade Steps” on page 93.
♦ Metadata Manager version 8.1 or earlier. Before you upgrade Metadata Manager, you
must prepare the repository database and back up parameter files. For more information,
see “Metadata Manager Pre-Upgrade Steps” on page 96.
78 Chapter 5: Before You Upgrade

PowerCenter Version 6.x/7.x Pre-Upgrade Steps
Before you upgrade PowerCenter 6.x or 7.x, complete the following tasks:
1. Establish the installation environment. The installation environment includes domains
and nodes. The nodes run application services.
2. Configure database connectivity. Configure database connectivity for each repository in
the domain on the gateway node and configure database connectivity on the machines
that run application services and the PowerCenter Client.
3. Prepare the repository for upgrade. Create a repository database and back up or copy
each repository you want to upgrade. Includes upgrading Informix, Teradata, and Oracle
8 repositories.
4. Prepare Informix and Teradata Data Profiling warehouses. If the Data Profiling
warehouse is in the same database as the PowerCenter repository, prepare the Data
Profiling warehouse for upgrade.
5. Back up and copy PowerCenter configuration files. Back up Repository Agent and
PowerCenter Server configuration files and copy them to a node in the domain.
6. Back up and uninstall Web Service Provider. (Optional) If PowerCenter includes the
Web Services Hub, back up the Web Services Hub configuration and uninstall Web
Services Hub.
Step 1. Establish the PowerCenter Installation Environment

Establish the number of PowerCenter domains and the number of nodes in each domain. In a
single machine installation, the domain consists of a single node. In a multiple machine
installation, you can create multiple domains and multiple nodes in each domain. If you
create multiple domains, you must decide which domain will contain your existing
PowerCenter repositories.
When you upgrade an existing PowerCenter installation, you assign the Repository Services
and Integration Services to run on a node in a domain. You need to identify the nodes to run
the application services and install PowerCenter Services on the nodes before you can upgrade
an existing Repository Server or PowerCenter Server.
For more information about single and multiple machine PowerCenter installations, see
“Single or Multiple Machine Installation” on page 17.
Step 2. Configure Database Connectivity

Configure the database connectivity on the machines where you are installing PowerCenter
Services. You must configure database connectivity on each machine that runs an Integration
Service or Repository Service.
You must also configure database connectivity on the gateway node for the repository
database types that you want to upgrade. The repository upgrade process runs on the gateway
nodes in the domain. The upgrade process uses the database client connectivity you configure
PowerCenter Version 6.x/7.x Pre-Upgrade Steps 79

on the gateway nodes to connect to the repository databases during the upgrade. For example,
if you upgrade an Oracle repository, verify that the Oracle database client is correctly
configured on the gateway nodes in the domain. If you have a single gateway node, you only
need to configure the database connectivity on that node.
For more information about configuring database connectivity, see “Connecting to Databases
from Windows” on page 487 and “Connecting to Databases from UNIX” on page 503.
Step 3. Prepare the Repository for Upgrade

Set up a new repository database and create a copy or back up the repository for each
repository you want to upgrade. For more information, see “Preparing the Repository for
Upgrade” on page 86.
Step 4. Prepare the Informix and Teradata Data Profiling

Warehouse
PowerCenter 8.1.1 does not support Informix or Teradata as a repository database. If the Data
Profiling warehouse resides on the same database as a PowerCenter 7.x repository in an
Informix or Teradata database you must recreate the warehouse.
To recreate the warehouse, you must perform one of the following tasks before you can run
existing profile sessions:
♦ Drop the existing warehouse tables and recreate the warehouse on the Informix database
before you move your PowerCenter 7.x repository.
♦ Create the Data Profiling warehouse on a different database.
You can then upgrade the warehouse after you upgrade PowerCenter.
Step 5. Back Up and Copy PowerCenter Configuration Files

Back up existing Repository Agent and PowerCenter Server configuration files if you want to
upgrade them to a Repository Service or Integration Service. If you want to upgrade a
PowerCenter Server on a Windows machine, you must export the configuration to a
configuration file using the pmserverexportreg utility.
After you back up the configuration files, copy them to the global_repo, local_repo, and
PCServer directories in the server/upgrade/cfgfiles directory on one of the nodes in the
domain.
For more information about backing up and copying configuration files and creating a
PowerCenter Server configuration file, see “Backing Up and Copying Configuration Files” on
page 89.
Step 6. Back Up and Uninstall Web Services Provider

If the PowerCenter installation includes the Web Services Hub, you must back up the Web
Services configuration before you upgrade. You create and configure a new Web Services Hub

in the PowerCenter Administration Console after you install PowerCenter. You cannot
upgrade an existing Web Services Hub.
Before you install PowerCenter and create a Web Services Hub, complete the following tasks:
♦ Back up the Web Services Hub configuration file. Back up the Web Services Hub
configuration file to use the settings in the configuration file as reference when you create
another Web Services Hub. The configuration file is named WSHConfig.xml and located
in the WSH_HOME/config directory.
♦ Uninstall Web Services Provider. After you back up the configuration file, you can safely
uninstall Web Services Provider.
PowerCenter Version 6.x/7.x Pre-Upgrade Steps 81

PowerCenter Version 8.0 Pre-Upgrade Steps
Before you upgrade PowerCenter 8.0, complete the following tasks:
1. Prepare the repository for upgrade. Create a repository database and back up or copy
each repository you want to upgrade.
2. Note domain configuration. Note the domain name, node names, and port numbers
used by the nodes in the PowerCenter 8.0 domain.
3. Stop Informatica Services. Stop Informatica Services on each node in the PowerCenter
8.0 domain.
4. Unset environment variables. Unset PowerCenter environment variables configured for
the previous PowerCenter installation.
5. Back up metadata configuration files. Back up the configuration files that contain
domain and node metadata.
After you complete the pre-upgrade steps, upgrade the domain and node metadata from
PowerCenter 8.0 to PowerCenter 8.1. For more information, see “Upgrading PowerCenter”
on page 401.
Step 1. Prepare the Repository for Upgrade

Set up a repository database and create a copy or back up the repository for each repository
you want to upgrade. For more information, see “Preparing the Repository for Upgrade” on
page 86.
Step 2. Note Domain Configuration

When you install PowerCenter Services, you recreate the existing PowerCenter domain. You
must use the same domain name, node names, and port numbers in the PowerCenter 8.1
domain. Write down the domain name, node names, and port numbers for the nodes in the
domain. You will need this information when you upgrade the domain. You can obtain this
information in the Administration Console for the PowerCenter 8.0 domain.
Step 3. Stop Informatica Services

Stop Informatica Services on each node in the PowerCenter 8.0 domain. You must shut down
each node in the domain to avoid port conflicts when you install the new version. For more
information about stopping Informatica Services, see “Starting and Stopping Informatica
Services” on page 529.
On Windows, set the Startup Type for the Informatica Services service to Manual or
Disabled. Otherwise, PowerCenter 8.0 will start before PowerCenter 8.1 if you reboot the
machine. For more information about configuring the Informatica Services service on
Windows, see “Configuring Informatica Services” on page 325.

Step 4. Unset Environment Variables
You must unset PowerCenter environment variables configured during the previous
PowerCenter installation. Incorrectly configured environment variables may cause the
PowerCenter domain or nodes to fail to start or may cause connection problems between the
PowerCenter Client and the domain.
Unset the following PowerCenter environment variables:
♦ INFA_HOME. Designates the PowerCenter Services installation directory.
♦ INFA_DOMAINS_FILE. Designates the location of domains.infa on the machine where
you install PowerCenter Services or the PowerCenter Client.
Step 5. Back Up Metadata Configuration Files

Back up the metadata configuration files used by the domain. When you upgrade to
PowerCenter 8.1.1, you use infaupgrade to upgrade the domain and node metadata in the
configuration files. You can back up the configuration files to any directory accessible by the
machines where you install PowerCenter Services.
PowerCenter stores the domain and node metadata in the following files:
♦ domainmeta.xml. Contains the metadata for the domain. By default, domainmeta.xml is
stored in the server/infa_shared/config directory on the node that hosts the domain. The
domainmeta.xml may be stored in a different location if you configured a shared location
in the Administration Console.
♦ nodemeta.xml. Contains the metadata for a node in a domain. All nodes store
nodemeta.xml in the server/config directory.
If the domain contains multiple nodes and you use the same backup directory for the
metadata configuration files, you must rename nodemeta.xml before copying it to the
backup location. For example, if you back up nodemeta.xml for a node named node01,
you can rename the configuration file node1.xml before copying the file.
♦ domains.infa. Stores the connectivity information for the gateway nodes in a domain. The
connectivity information includes the domain names, domain host names, and domain
host port numbers. On nodes running PowerCenter Services, domains.infa is located in
the PowerCenter installation directory, unless you configured a different location using the
INFA_DOMAINS_FILE environment variable. You copy domains.infa from the backup
location after you upgrade the domain and node metadata.
PowerCenter Version 8.0 Pre-Upgrade Steps 83

PowerCenter 8.1 Pre-Upgrade Steps
Before you upgrade PowerCenter 8.1, complete the following tasks:
1. Back up domain metadata. Backup the domain configuration metadata in the domain
configuration database.
2. Back up configuration metadata. Back up node configuration and connectivity
metadata.
3. Stop Informatica Services. Stop Informatica Services on each node in the PowerCenter
8.1 domain.
Step 1. Back Up Domain Metadata

PowerCenter stores the PowerCenter domain configuration in a relational database. Back up
the domain configuration before you upgrade.
You can back up the domain configuration using following methods:
♦ Run the BackupDomain command. Use the infasetup BackupDomain command to back
up the domain configuration to an XML file. The BackupDomain command uses the
following syntax:
BackupDomain
<-DatabaseAddress|-da> database_hostname:database_port
<-DatabaseUserName|-du> database_user_name
<-DatabasePassword|-dp> database_password
<-DatabaseType|-dt> database_type
[<-DatabaseServiceName|-ds> database_service_name]
<-BackupFile|-bf> backup_file_name
[<-Force|-f>]
<-DomainName|-dn> domain_name
For more information about the BackupDomain command, see "infasetup Command
Reference" the Command Line Reference.
♦ Back up the database tables manually. The BackupDomain command only backs up the
PCSF_DOMAIN domain configuration database table. If you want to back up all domain
configuration information, including information about the gateway nodes, session and
workflow logs, and repository usage information, you can back up the database tables
manually.
If you want to back up the tables manually, back up the following tables:
− PCSF_CPU_USAGE_SUMMARY
− PCSF_DOMAIN
− PCSF_MASTER_ELECTION
− PCSF_MASTER_ELECT_LOCK
− PCSF_REPO_USAGE_SUMMARY
− PCSF_RUN_LOG

Step 2. Back Up Configuration Metadata
Back up the node and connectivity metadata configuration files. Back up the following
metadata configuration files:
♦ nodemeta.xml. Contains the metadata for a node in a domain. All nodes store
nodemeta.xml in the server/config directory.
If the domain contains multiple nodes and you use the same backup directory for the
metadata configuration files, you must rename nodemeta.xml before copying it to the
backup location. For example, if you back up nodemeta.xml for a node named node01,
you can rename the configuration file node1.xml before copying the file.
♦ domains.infa. Stores the connectivity information for the gateway nodes in a domain. The
connectivity information includes the domain names, domain host names, and domain
host port numbers. On nodes running PowerCenter Services, domains.infa is located in
the PowerCenter installation directory, unless you configured a different location using the
INFA_DOMAINS_FILE environment variable. You copy domains.infa from the backup
location after you upgrade the domain and node metadata.
Step 3. Stop Informatica Services

Stop Informatica Services on each node in the PowerCenter 8.1 domain. You must shut down
each node in the domain to avoid port conflicts when you install the new version of
PowerCenter Services. For more information about stopping Informatica Services, see
“Starting and Stopping Informatica Services” on page 529.
On Windows, set the Startup Type for the Informatica Services service to Manual or
Disabled. Otherwise, PowerCenter 8.1 will start before PowerCenter 8.1.1 if you reboot the
machine. For more information about configuring the Informatica Services service on
Windows, see “Configuring Informatica Services” on page 325.
PowerCenter 8.1 Pre-Upgrade Steps 85

Preparing the Repository for Upgrade
PowerCenter versions:
6.x / 7.x / 8.0
When you prepare a repository for upgrade, you optimize the upgrade performance, set up
another repository database, and create a copy of the repository.
When you upgrade a PowerCenter repository, you upgrade a copy of the repository. Make a
copy of all repositories in the existing version of PowerCenter before upgrading to
PowerCenter 8.1.1. Upgrade the copy of the existing PowerCenter repository to evaluate it
without altering the existing repository.
Complete the following steps to prepare a PowerCenter repository for upgrade:
1. Set up a PowerCenter repository database. Set up another database for each
PowerCenter repository you want to upgrade.
2. Optimize repository upgrade performance. You can optimize the repository to increase
performance when you upgrade a repository.
3. Prepare Informix, Teradata, or Oracle 8 Repositories. To upgrade an Informix, Oracle 8,
or Teradata database, you must restore the repository to a supported repository database.
4. Create a copy of the repository. Use the existing version of PowerCenter to create a copy
or restore a backup of the existing repository to the database you created in step 1.
Step 1. Set Up the PowerCenter Repository Database

Set up another database for each PowerCenter repository you want to upgrade. Make sure that
the database user account has privileges to create and drop tables and indexes and to select,
insert, update, or delete data from the tables.
The upgrade process copies metadata from the original tables into temporary tables. Because
these temporary tables are created in the same database as the repository, the upgrade process
requires additional space. You may need to increase the size of the database or add more disk
space. You should allocate up to approximately 50 percent more available disk space and
temporary storage space in the database.
For more information about setting up a PowerCenter repository database, see “Step 1. Create
Databases” on page 52.
Step 2. Optimize Upgrade Performance

You can complete the following tasks to optimize the repository and increase performance
when you upgrade the repository:
♦ Purge versions from the repository. If your repository is enabled for version control, the
repository can quickly grow very large depending on the frequency and number of new
versions added to the repository. Each version of an object occupies the same amount of

space in the repository database. You may want to monitor the size of the repository
database periodically to determine the rate of growth.
♦ Truncate the workflow and session log file. Use the Repository Manager or use the pmrep
TruncateLog command to truncate the workflow and session log file and delete run-time
information you do not need. For example, you can delete all log events older than one
month before upgrading the repository.
♦ Update statistics. PowerCenter identifies and updates the statistics of all repository tables
and indexes when you upgrade a repository. You can update the statistics before upgrading
the repository to increase upgrade performance.
For more information about completing the required tasks for optimizing the repository, see
your existing PowerCenter documentation.
Step 3. Prepare Informix, Teradata, or Oracle 8 Repositories

If you want to upgrade a Teradata or Informix repository, you must back up the repository
and then restore it to an IBM DB2, Sybase ASE, Oracle, or Microsoft SQL Server database
using your current version of PowerCenter. After you restore the repository, upgrade it using
the upgraded version of PowerCenter.
If you upgrade an Oracle 8 repository, you must back up the repository and restore it to a
Oracle 9 or higher database.
For more information about backing up and restoring the repository, see your existing
PowerCenter documentation.
Step 4. Create a Copy of a Repository

You can create a copy of a repository by copying the repository to a new database or by
restoring a backup of the repository to a new database.
Note: If you want to copy or restore a Sybase ASE repository, set allow nulls by default to
TRUE at the database level. Setting this option changes the default null type of the column to
null in compliance with the SQL standard.
Copying a Repository
You can create a copy of your existing repository for upgrade by copying it to a new database.
To copy an existing PowerCenter repository to a another database:
1. Use the existing version of PowerCenter to copy the repository to another database.
2. When you copy multiple repositories in a repository domain, register the local
repositories with the global repository after you copy the repositories.
3. Have all users close all PowerCenter Client repository connections.
4. Release all residual locks.
Preparing the Repository for Upgrade 87

5. If you upgrade from PowerCenter 6.x/7.x, stop the PowerCenter Server and Repository
Server. If you upgrade from PowerCenter 8.0, disable the Integration Service and
Repository Service.
Backing Up a Repository
You can create a copy of your existing repository for upgrade by backing up the repository and
then restoring the backup file to a new database.
Note: In PowerCenter 8.1.1, the Repository Service name cannot contain a tab character,
trailing spaces, any of the following characters: ? " : < > * / \ |, or more than 79 characters. If
the name of the repository you want to upgrade contains any of these characters, back up the
repository, and then restore it using a name that does not contain these characters. For
information about backing up and restoring a repository, see your existing PowerCenter
documentation.
To back up and restore an existing PowerCenter repository:
1. Use the existing version of PowerCenter to back up the existing repository.

2. Use the existing version of PowerCenter to restore the repository backup file to another
database.
3. If you want to restore multiple repositories in a repository domain, register the local
repositories with the global repository after you restore the repositories.
4. Have all users close all PowerCenter Client repository connections.
5. Release all residual locks.
6. If you upgrade from PowerCenter 6.x/7.x, stop the PowerCenter Server and Repository
Server. If you upgrade from PowerCenter 8.0, disable the Integration Service and
Repository Service.

Backing Up and Copying Configuration Files
PowerCenter versions:
6.x / 7.x
You must back up the Repository Agent and PowerCenter Server configuration files from
PowerCenter 6.x or 7.x before you upgrade. When you upgrade the PowerCenter installation,
you can upgrade existing Repository Agent and PowerCenter Server configurations to
Repository Services and Integration Services in PowerCenter 8.1.1.
Use the following steps to back up and copy the configuration files:
1. Create a PowerCenter Server configuration file. If a PowerCenter Server runs on
Windows, create the PowerCenter Server configuration file using the pmserverexportreg
utility and copy the file to the backup directory.
2. Back up configuration files. Back up each configuration file that you want to upgrade.
3. Verify the character set. Verify that the character set for the configuration files are
compatible with the character set used by the gateway nodes in the domain.
4. Copy the configuration files to the domain. Copy configuration files from the backup
directory to the appropriate directory under the server/upgrade/cfgfiles directory on a
node in the PowerCenter domain.
Warning: Do not modify the contents of the configuration files before you upgrade the
Repository Agent or PowerCenter Server to a Repository Service or Integration Service.
Modifying the files may cause the upgrade to fail.
Step 1. Create a PowerCenter Server Configuration File

On Windows, the configuration information for the PowerCenter Server is stored in the
Windows registry. Use the pmserverexportreg utility to create a configuration file from the
configuration information in the Windows registry.
You can get pmserverexportreg from the PowerCenter Utilities zip or tar file on the installation
DVD. To run pmserverexportreg, you must install the required files to a directory on the
machine that hosts the PowerCenter Server. You run pmserverexportreg from the machine
where the PowerCenter Server is installed.
For more information about PowerCenter utilities, see “PowerCenter Utilities Installation” on
page 299.
The pmserverexportreg utility uses the following syntax:
pmserverexportreg <directory path>\<file name>.cfg
Backing Up and Copying Configuration Files 89

Table 5-1 describes pmserverexportreg arguments:
Table 5-1. pmserverexportreg Arguments
Required/
Argument Description
Optional
directory path Required Absolute or relative directory path where you want to store the configuration file.
file name Required File name of the configuration file you want to create.
For example, the following command creates a configuration file named Production.cfg:
pmserverexportreg c:\PMServer\backup\Production.cfg
To use the pmserverexportreg utility to create a configuration file:
1. Copy the PowerCenter utilities to the machine that hosts the PowerCenter Server.
2. From a command prompt, navigate to the location of pmserverexportreg.exe.
3. Run the utility to create the PowerCenter Server configuration file.
For example, use the following command:
pmserverexportreg <file path>\Production.cfg
Note: If you do not configure the file path, the utility creates the configuration file in the
directory where pmserverexportreg runs.
4. Copy the PowerCenter Server configuration file you created to the backup directory for
the PowerCenter Server and Repository Agent configuration files.
Troubleshooting pmserverexportreg
The following error messages may occur when you use pmserverexportreg:
Cannot create configuration file because registry entry [<key name>] does not exist.
PowerCenter Server not installed or registry contains errors.
Cause: The pmserverexportreg utility cannot export the PowerCenter Server values
from the registry on the current machine. A PowerCenter Server is not
installed on the current machine or the registry contains errors.
Action: Verify that you run the utility on a machine where the PowerCenter Server is
installed.
Cannot create file <file name>. The file name is invalid or the file already exists.
Cause: The pmserverexportreg utility cannot create the PowerCenter Server
configuration file. The name for the configuration file is invalid or the file
already exists.
Action: Delete the current file or use a different file name, and run the command
again.

Cannot create file <file name> due to error: <error text>.
Cause: The pmserverexportreg utility did not create the PowerCenter Server
configuration file due to an error.
Action: Correct the error and run the utility again.
Step 2. Back Up the Configuration Files

You can back up the configuration files to any directory accessible by the machines where you
install PowerCenter Services. Back up the configuration file for each Repository Agent and
PowerCenter Server you want to upgrade.
Note: If you change the contents of the configuration files before you upgrade them, the
upgrade fails.
Repository Agent
The Repository Agent configuration file is located in the RepositoryServer/bin/Config
directory machine where the Repository Server runs. Each repository has an associated
Repository Agent configuration file based on the repository name. For example, for the
HR_71 repository, the Repository Agent configuration file is named HR_071-es.cfg.
If your PowerCenter repository domain includes global and local repositories, you must note
which Repository Agent configuration files are associated with the global and local
repositories.
PowerCenter Server
The PowerCenter Server configuration file pmserver.cfg is located in the Server/bin directory
on UNIX machines. On Windows, you must export the PowerCenter Server configuration to
a configuration file. For more information about exporting PowerCenter Server configuration
on Windows, see “Step 1. Create a PowerCenter Server Configuration File” on page 89.
If you upgrade multiple PowerCenter Server configurations, rename each configuration file
before copying them to the backup location. For example, if you back up pmserver.cfg for a
PowerCenter Server named Production, you can rename the configuration file Production.cfg
before copying the file.
Step 3. Verify the Character Set

The character set for a Repository Agent or PowerCenter Server configuration file must be
compatible with the character set used by the gateway nodes in the domain. To make sure the
character sets are compatible, verify that the language setting for the machine where the
Repository Agent ot PowerCenter Server runs is compatible with the language setting on the
gateway nodes for the domain.
On Windows, you can verify the language setting under Regional Options in the Control
Panel. On UNIX, you can verify the languages setting by viewing the setting for the
LANG_C, LC_CTYPE, or LC_ALL environment variable.
Backing Up and Copying Configuration Files 91

If the language settings are not compatible, the upgraded Repository Service or Integration
Service may not start or may contain inconsistent metadata.
Step 4. Copy the Configuration Files to the Domain

After you back up the configuration files, copy them from the backup location to a node in
the domain. Copy the configuration file to the appropriate directory under the server/
upgrade/cfgfiles directory:
♦ local_repo. Directory for Repository Agent configuration files for a local repositories. If
your existing PowerCenter installation does not contain a global repository, copy all
Repository Agent configuration files into this directory.
♦ global_repo. Directory for Repository Agent configuration files for global repositories.
♦ PCServer. Directory for PowerCenter Server configuration files.
If you want to upgrade a single configuration file, copy the configuration file to a directory
that you can access from the node hosting the PowerCenter domain. You can select this file
when you run the Upgrade Wizard.

Data Analyzer Pre-Upgrade Steps
Before you upgrade to Data Analyzer 8.1.1, complete the following tasks:
1. Set up a new Data Analyzer repository database. Set up a new database and user account
for the Data Analyzer repository.
2. Back up the Data Analyzer repository. Use the Data Analyzer Repository Backup utility
to back up the Data Analyzer repository database.
3. Restore the Data Analyzer repository. Use the existing version of the Data Analyzer
Repository Backup Utility to restore the Data Analyzer repository.
4. Copy customized files and shared documents to a temporary directory. Copy the
customized files and shared documents to a temporary directory before you start the
upgrade process.
Step 1. Set Up the Data Analyzer Repository Database

Set up a database and user account for the Data Analyzer repository. Make sure that the
database user account has privileges to create and drop tables and indexes and to select, insert,
update, or delete data from the tables.
For more information about setting up a Data Analyzer repository database and user account,
see “Step 1. Create Databases” on page 52 and “Step 2. Create Database User Accounts” on
page 56.
Step 2. Back Up the Data Analyzer Repository

Use the native database backup or the existing version of the Data Analyzer Repository
Backup utility to back up the Data Analyzer repository database before you start the upgrade
process.
For more information about backing up the Data Analyzer repository, see “Backing up or
Recovering the Repository” in the Data Analyzer Administrator Guide.
Note: The version of the Repository Backup utility you use must match the version of Data
Analyzer repository you are backing up. For example, you must use the Repository Backup
Utility version 4.1.1 to back up or restore a PowerAnalyzer 4.1.1 repository. Likewise, you
must use the Repository Backup Utility version 8.0 to back up a Data Analyzer 8.0 repository
or to restore a Data Analyzer 8.0 repository backup file.
Step 3. Restore the Data Analyzer Repository

Use the correct version of Data Analyzer Repository Backup Utility to restore the Data
Analyzer repository from the repository backup file (created in step 2) into the database set up
in step 1. For more information about restoring the Data Analyzer repository, see “Backing up
or Recovering the Repository” in the Data Analyzer Administrator Guide.
Data Analyzer Pre-Upgrade Steps 93

After you restore the repository from the backup file, the new repository database is an exact
copy of the working repository database. You can now use it as the repository for the new
Data Analyzer installation.
Step 4. Copy Customized Files and Shared Documents

If you customized Data Analyzer, copy the configuration files and color schemes to a
temporary directory. You also copy shared documents to a temporary directory.
Copying Configuration Files

If you have customized Data Analyzer configuration files, copy the Data Analyzer
configuration files to a temporary directory. After the upgrade, update the configuration files
in Data Analyzer 8.1.1 to match the settings in the configuration files for the previous
version.
The Data Analyzer configuration files include the following files:
♦ IAS.properties
♦ web.xml
♦ ldaprealm.properties
Note: In Data Analyzer 8.1 running on JBoss Application Server, the ldaprealm.properties
files is stored in the Data Analyzer EAR file.
♦ DataAnalyzer.properties
Note: The DataAnalyzer.properties configuration file was introduced in Data Analyzer
5.0.2/8.0. You do not have to back up these files in PowerAnalyzer 4.x.
If you updated application server configuration files, you must copy the application server
configuration files in Data Analyzer to a temporary directory.
Table 5-2 describes the application server configuration files:
Table 5-2. Data Analyzer Configuration Files
Application Server File Name
BEA WebLogic Server config.xml

startweblogic.cmd or startweblogic.sh
IBM WebSphere Application Server server.xml
JBoss Application Server login-config.xml
Copying Color Schemes

The Repository Upgrade utility upgrades all repository objects except color schemes. You
must manually back up the color schemes before you upgrade Data Analyzer and then update
the color schemes in the new version.
If you set up a custom color scheme and you want to keep using the color scheme in Data
Analyzer 8.1.1, copy the custom color scheme directory to a temporary location.

If you created custom color schemes or modified a pre-defined color scheme in a previous
version of Data Analyzer, you can keep using them in Data Analyzer 8.1.1. To make sure that
you do not lose your custom color schemes, copy them to a different location before you
upgrade Data Analyzer and then restore them after you upgrade. Or, you can recreate them in
the latest version of Data Analyzer.
Copying Shared Documents

If you have shared documents in Data Analyzer located in the application server directory,
copy the shared document files to a temporary directory.
Data Analyzer Pre-Upgrade Steps 95

Metadata Manager Pre-Upgrade Steps
Before you upgrade to Metadata Manager 8.1.1, complete the following tasks:
1. Set up the repository databases. Set up a database and user account for each repository
database.
2. Copy the Metadata Manager repository. Copy the working Metadata Manager to the
new database.
3. Back up parameter files. Back up the existing parameter files for custom XConnects.
4. Note information for the Business Objects XConnect. You must set up the connection
to the Business Objects source repository and select the universes and documents after
you upgrade Metadata Manager.
Step 1. Set Up the Repository Databases

Set up a database and user account for the Metadata Manager repository and the PowerCenter
repository for Metadata Manager. Make sure that the database user accounts have privileges to
create and drop tables and indexes and to select, insert, update, or delete data from the tables.
For more information about setting up a repository databases and user accounts, see “Step 1.
Create Databases” on page 52 and “Step 2. Create Database User Accounts” on page 56.
Step 2. Copy the Metadata Manager Repository

You can use any backup or copy utility provided with the database to make a copy of the
working Metadata Manager repository database prior to upgrading the Metadata Manager
repository. Use the copy of the repository as the repository for the new Metadata Manager
installation.
Step 3. Back Up Existing Parameter Files

Make a copy of the existing parameter files for custom XConnects. You may need to refer to
these files when you later configure the parameters for the custom XConnects as part of the
Metadata Manager client upgrade.
For PowerCenter 8.1 or earlier, you can find the parameter files in the following directory:
<PowerCenter_Home>\server\infa_shared\SrcFiles
For SuperGlue 2.1 or 2.2, you can find the parameter files in the following directory:
<PowerCenter_Home>\Server\SrcFiles

Step 4. Note Information for the Business Objects XConnect
If you upgrade from version 8.0 or before and you previously set up the Business Objects
XConnect in the Metadata Manager Console, you must set up the Business Objects
XConnect again after the upgrade. You must set up the connection to the Business Objects
source repository and select the universes and documents to load into the Metadata Manager
Warehouse.
Metadata Manager Pre-Upgrade Steps 97

Part II: PowerCenter Installation

♦ PowerCenter Complete Installation in Graphical Mode, 101
♦ PowerCenter Custom Installation in Graphical Mode, 153
♦ PowerCenter Complete Installation in Console Mode, 211
♦ PowerCenter Custom Installation in Console Mode, 237
♦ PowerCenter Client Installation, 265
♦ PowerCenter Reports Installation, 281
♦ Documentation Installation, 291
♦ PowerCenter Utilities Installation, 299
♦ Informatica Development Platform Installation, 315
♦ After You Install, 323
♦ Troubleshooting a PowerCenter Installation, 359
♦ Uninstalling PowerCenter, 385
99
100
Chapter 6
PowerCenter Complete
Installation in Graphical Mode
♦ Overview, 102
♦ Installing PowerCenter Standard Edition, 103
♦ Installing PowerCenter Advanced Edition, 128
101
Overview
This chapter provides instructions on running the PowerCenter graphical mode installer and
installing the complete version of PowerCenter. When you install the complete version of
PowerCenter, the PowerCenter installer determines the components available for installation
based on the license key you provide.
Before you start the installation, complete the pre-installation tasks listed in “Before You
You can install the complete version of the following PowerCenter editions:
♦ PowerCenter Standard Edition. Installs all PowerCenter Standard Edition components.
Standard Edition includes PowerCenter and Data Analyzer for PowerCenter Repository
Reports. For more information, see “Installing PowerCenter Standard Edition” on
page 103.
♦ PowerCenter Advanced Edition. Installs all PowerCenter Advanced components,
including PowerCenter Services, Data Analyzer, and Metadata Manager. For more
information, see “Installing PowerCenter Advanced Edition” on page 128.
After you run the installer, complete the installation or upgrade of PowerCenter components.
For more information, see the steps for your installation or upgrade path in “Installation and
Upgrade Overview” on page 15.
102 Chapter 6: PowerCenter Complete Installation in Graphical Mode

Installing PowerCenter Standard Edition
The PowerCenter installer in graphical mode displays the same windows for UNIX and
Windows. Unless otherwise noted, the following procedure refers to both UNIX and
Windows installation.
To install PowerCenter Standard Edition:
1. Verify that your environment meets the minimum system requirements, and complete
the pre-installation tasks.
For more information about preparing for the PowerCenter installation, see “Before You
Install” on page 49. Verify that you have the PowerCenter Standard Edition license.
2. Log in to the machine as the system user.
3. Close all other applications before running the installation.
4. To start the installer on Windows, insert the DVD into the DVD drive. If the installer
does not start or if you are installing PowerCenter from a hard disk, run install.exe from
the DVD root directory or the root directory in the location where you downloaded the
installer.
-or-
To start the installer on UNIX, run install.sh at a shell command line from the DVD root
directory or the root directory in the location where you downloaded the installer.
On UNIX, the PowerCenter installer checks the operating system and verifies that the
environment variables are correctly set. The environment variables must be specifically
set to enable the PowerCenter installer to run processes and connect to databases and
services. If the environment variables are not set, the PowerCenter installer gives you the
option to stop the installation and modify the environment variables.
5. On UNIX, select the option to use the GUI mode installation.
6. On the main PowerCenter installation window, select Server.
The Welcome window introduces the PowerCenter installation.
7. Click Next.
Installing PowerCenter Standard Edition 103

On UNIX, the Configure Environment Variables window appears.
On UNIX, the PowerCenter installer requires specific environment variable settings.

Read the PowerCenter environment configuration requirements and set the environment
variables before you continue the installation. If you do not set the environment variables
as required, the PowerCenter installation may fail.
8. Click Next.
The PowerCenter License Key window appears.

9. Enter the location and file name of the PowerCenter Standard Edition license key or click
Browse to locate the license key file.
10. Click Next.
The Installation Prerequisites window displays the supported platforms and databases
and the disk space requirements. Verify that all PowerCenter installation requirements are
met before you continue the installation.
11. Click Next.
The Installation Set window displays the PowerCenter installation options.
12. To install the complete set of PowerCenter Standard Edition components, select
Complete and click Next.
To install a custom version of PowerCenter, see “PowerCenter Custom Installation in
Graphical Mode” on page 153.

The Data Analyzer/Metadata Manager License Key window appears.
13. Enter the location and file name of the Data Analyzer license key or click Browse to
locate the license key file.
14. Click Next.
The Installation Directory window appears.
15. Use the default directory or click Browse to select a directory.

The default directory on Windows is C:\Informatica\PowerCenter8.1.1.
The default directory on UNIX is $HOME/Informatica/PowerCenter8.1.1, where
HOME is the user home directory.
Note: The installation directory path must be an absolute path. On Windows, the
installation directory path must be located on the current machine.
16. Click Next.
The Application Server window appears.
17. Select the application server to install Data Analyzer on to run PowerCenter Repository
Reports.
You can select one of the following options:
♦ JBoss Application Server. You can install Data Analyzer on a new or existing instance
of JBoss Application Server. If you select JBoss Application Server, continue to the
next step.
♦ BEA WebLogic Server. You install Data Analyzer on an existing instance of BEA
WebLogic Server. You can create a new WebLogic Server domain or install Data
Analyzer on an existing WebLogic Server domain. If you select WebLogic Server, skip
to step 23.
♦ WebSphere Application Server (Network Deployment). You install Data Analyzer on
an existing WebSphere Application Server Network Deployment Edition instance. If
you select WebSphere Application Server Network Deployment Edition, skip to step
30.
♦ WebSphere Application Server (Base). You install Data Analyzer on an existing
WebSphere Application Server Base Edition instance. If you select WebSphere
Application Server Base Edition, skip to step 30.

18. Click Next.
The JBoss Application Server window appears.
19. Select the option to install a new instance of JBoss Application Server or to use an
existing instance.
If you use an existing instance of JBoss Application Server, verify that the application
server is shut down before you continue the installation.
20. Enter the home directory and the server configuration directory for JBoss Application
Server or click Browse to select the directory.
If you install a new instance of JBoss Application Server, the installer creates a server
configuration in the directory you provide.
If you use an existing instance of JBoss Application Server, you must provide the
directory for an existing server configuration. The server configuration must support all
available JBoss services.
21. To configure the JBoss Application Server ports, click Advanced Configuration.

The Advanced Configuration for JBoss dialog box appears.
You can configure the ports used by JBoss Application Server to avoid port conflicts if
you run multiple instances of JBoss Application Server on the same machine.
22. Click OK. Skip to step 35.
23. Click Next.

The WebLogic Server Directory window appears.
Use the default directory or click Browse to select a directory.

24. Click Next.
The WebLogic Application Server Domain window appears.

25. Choose to install Data Analyzer on a new domain or an existing domain.
Provide the domain name and location. If you are installing Data Analyzer on a new
WebLogic domain, continue to the next step. If you are installing on an existing
WebLogic domain, skip to step 28.
26. Click Next.
The New WebLogic Domain Configuration window appears.
27. Enter the account name and password for the WebLogic Administration Console and the
listening port number for the new domain. Skip to step 35.
28. Click Next.

The Existing WebLogic Server Domain Configuration window appears.
The installer will install Data Analyzer on an existing WebLogic domain in WebLogic
Server.
29. Enter the account name and password for the WebLogic Administration Console for the
existing domain. Skip to step 35.
30. Click Next.
The Existing WebSphere Application Server Directory window appears.

Enter the home directory for WebSphere Base Server or click Browse to locate the
directory. Skip to step 33.
31. Click Next.
32. Enter the home directories for the WebSphere Base Server and the Network Deployment
or click Browse to locate the directory.
33. Click Next.

The WebSphere Application Server Administration Details window appears.
34. Enter the following information:
Property Description
Admin user name User name for the WebSphere Administrative Console administrator.
Admin password Password for the WebSphere Application Server administrator.
Server name Name of the server to run Data Analyzer on. Default is server1.
HTTP port Port number for the WebSphere Application Server server. Default is 9080.
Node name Name of the WebSphere node. This is not a PowerCenter node name. Default is machine
name.
35. Click Next.

The Pre-Installation Summary page appears. Review the pre-installation summary to
verify that the installer will install PowerCenter components in the correct location and
with the options you select.
36. Click Install to continue or click Previous to modify the options.

After you click Install, the installer copies the files for the selected components to the
installation directory. When the file copy process completes, the Create or Join Domain
window appears.
37. Choose to create a domain if you are installing PowerCenter for the first time or you are
installing PowerCenter on a single machine. Skip to step 38.
-or-
Choose to join a domain if you have created a PowerCenter domain on another machine
and you want to add the current machine to the domain. Skip to step 44.
For more information about the available domain options, click the Help Me Select link.
38. Click Next.

The Configure Domain Database window appears.
PowerCenter stores the PowerCenter domain configuration in a relational database. The

domain configuration must be accessible by all gateway nodes in the domain.
Database type Type of database to store the domain configuration. Database type may be Oracle,
Microsoft SQL Server, Sybase ASE, or IBM DB2.
Database URL Host name and port number for the database instance in the format <host
name>:<port>.
Database user ID Domain configuration database account.
Database password Password for the domain configuration database user account.
Database service name Service name for Oracle and IBM DB2 databases or database name for Microsoft SQL
Server or Sybase ASE databases.
40. Click Next.

The Configure Domain window appears.
Domain name Name of the PowerCenter domain to create. The domain name must be in 7-bit ASCII
format and must be less than 79 characters. The domain name cannot contain spaces or
the following characters: \ / : * ? > < " |
Domain host name Host name of the machine on which to create the PowerCenter domain. If you create a
domain on a machine with a single network name, do not change the default host name.
If you create a domain on a machine with multiple network names, you can modify the
default host name to use an alternate network name. Optionally, you can use the IP
address of the machine on which to create the domain.
Node name Node name for the current machine. This node name is the gateway node for the domain.
This is not the host name for the machine.
Domain port no. Port number for the current machine. The installer displays a default port number of
6001. If the port number is not available on the machine, the installer displays the next
available port number.
Domain user name User name of the domain administrator. You use this user name to log in to the
PowerCenter Administration Console. The user name must be less than 79 characters
and can only contain alphanumeric characters.
Domain password Password for the domain administrator. The password must be between 3 and 16
characters.
Confirm password Reenter the password.
Create Repository Allows you to create a Repository Service for the PowerCenter repository. You must
Service select this option to create an Integration Service for the domain during installation. You
can also create a Repository Service after installation.

42. To set the range of port numbers to be used for PowerCenter Services on the node, click
Advanced Configuration.
The Advanced Configuration window appears.
43. Enter the range of port numbers that the PowerCenter installer can use for PowerCenter
Services on the node and click OK.
The default range for the port numbers is 6005 - 6105.
Skip to step 50.
44. Click Next.
The PowerCenter domain that you want to join must be available when you join the
domain. Verify that the gateway node for the domain you want to join is available before
you continue. If the PowerCenter installer cannot connect to the PowerCenter domain,
you cannot continue with the installation.

Domain name Name of the domain you want to join.
Domain host name Host name or IP address of the gateway node for the domain.
Node name Node name for the gateway node.
Domain port no. Port number for the gateway node.
Domain user name User name for the administrator account in the PowerCenter domain to join.
Domain password Password for the domain administrator user account.
46. Click Next.

The Configure Node window appears.
Host name Host name or IP address for the current machine.
Node name Name of the node to create on the PowerCenter domain. The node name must be in 7-bit
ASCII format and must be less than 79 characters. This name is not the host name for the
node. Do not use the following characters: \ / : * ? < > " |
Port number Port number for the current machine. The installer displays a default port number of 6001. If
this port number is not available on the machine where you install PowerCenter, enter a
different port number.

Create Repository Allows you to create a Repository Service for the PowerCenter repository. You must select
Service this option to also create an Integration Service during installation. You can also create a
Repository Service after installation.
Serves as Indicates whether the node can serve as a gateway. If you do not select this option, the
Gateway node is a worker node in the domain you join.
49. Enter the range of port numbers that the PowerCenter installer can use for the
PowerCenter Services on the node and click OK.
50. Click Next.
On Windows, the Configure Informatica Services window appears.

Informatica Services is the Windows service that runs PowerCenter Services on a node in
a PowerCenter domain. Configure the user account if PowerCenter Services need to
access a network location not available to the current Windows user account. If you do
not configure this option, the Informatica Services service uses the current Windows user
account to log on when you start Informatica Services.
Note: You must configure a Windows user account for Informatica Services if you want to
use a trusted connection for authentication with the PowerCenter repository database.
51. To configure the Windows user account, enter the following information:
Install Informatica Services with Select this option and configure the user account and password.
a different user account
User name Windows domain and user account used by the Informatica Services service
to log on when you start Informatica Services. Enter the domain and user
account in the format <domain name>\<user account>. This user
account must have the Act as operating system permission. For more
information, see your Windows documentation.
Password Password for the Windows user account.
52. Click Next.

The PowerCenter Repository Configuration window appears.
The installer requires the database information to create a PowerCenter repository or

connect to an existing PowerCenter repository.
53. Select whether to use a new or existing PowerCenter repository.

To create a PowerCenter repository during the installation, select Create new
PowerCenter Repository. To use an existing PowerCenter repository, select Use existing
PowerCenter repository content. You may need to upgrade the repository after installing
PowerCenter.
54. Select a database type and enter the database information for the PowerCenter repository.
The PowerCenter Repository Configuration window requires different information based
on the database type you select.
Table 6-1 describes the configuration information required for the repository:
Table 6-1. PowerCenter Repository Information
Option Description
Repository name Name for the PowerCenter repository. The name is case sensitive and must be less than
30 characters. The repository name cannot contain spaces or the following characters: \ / :
*?><"|
Code page Repository code page. The Repository Service uses the character set encoded in the
repository code page when it writes data to the repository. Choose a code page that is
compatible with the code page of the machine where you install PowerCenter.
If you use an existing PowerCenter repository, the PowerCenter installer does not validate
the repository code page. You must verify that the code page for the existing repository is
The Integration Service created during installation uses the same code page as the
Repository Service. Verify that the code page for the Repository Service is compatible with
the machine where the services are created.
Database type Type of database for the PowerCenter repository.
Trusted Connection Appears for Microsoft SQL Server only.

If selected, the Repository Service uses Windows authentication to access the Microsoft
SQL Server database. You must configure a Windows user in the Configure Informatica
Services window to enable this option. The user account that runs Informatica Services
must have access to the Microsoft SQL Server database.
Database user ID Name of the user account to connect to the repository database.
Database user Password for the user account to connect to the database. Use 7-bit ASCII.
Password
Connect string Appears for Oracle, Microsoft SQL Server, and Sybase ASE databases only.
Native connect string to access the repository database. Use the syntax appropriate for the
selected database:
- Oracle: Same syntax as the TNSNAMES entry: aliasname.world.
- Microsoft SQL Server: Syntax is SQLServername@dbname, where SQLServername is
the name of the SQL Server instance that contains the dbname database.
- Sybase ASE: Syntax is servername@dbname, where servername is the name of the
Adaptive Server from the interfaces file.
Database name Appears for DB2 databases. DB2 alias name for the repository database.
Tablespace name Appears for DB2 databases. Name of the tablespace in which to create the repository
(Optional) tables. If blank, the installation creates the repository tables in the default tablespace.
55. Click Test Connection to verify the database connection.

The installer verifies that the database connection is valid. If the connection fails, an error
message indicates the reason for the failure. You can continue the installation if the
connection is valid.
If you chose to create a Repository Service when you configured the node, continue to
the next step. If you do not create a Repository Service, skip to step 58.
56. Click Next.
The Configure Integration Service window appears.
Choose the data movement mode. The data movement mode must match the data
movement mode of the associated PowerCenter repository.
Create Integration Enable this option to create an Integration Service.

Service
Service name Name of the Integration Service. The name is not case sensitive and must be unique within
the domain. The characters must be compatible with the code page of the associated
repository. The name cannot have leading or trailing spaces, include carriage returns or
tabs, exceed 79 characters, or contain the following characters: / * ? < > " |
User name User name for the database user account used for the PowerCenter repository database.
This option is available if you select an existing PowerCenter repository.
Password Password for the associated repository database user account.

58. Click Next.
If you selected an existing instance of JBoss Application Server, or you selected WebLogic
Server or WebSphere Application Server, the Data Analyzer and Metadata Manager
Authentication window appears.
Note: WebLogic Server and WebSphere Application Server support one authentication
method for all applications running on the same instance of the application server.
59. Select Yes to overwrite the authentication in the application server with repository
authentication. The new authentication settings will overwrite the security settings on
the application server.
-or-
Select No to keep the current authentication settings in the application server. If you
select No, the application server must be configured with an authentication method that
is compatible with Data Analyzer. Otherwise, you cannot log in to Data Analyzer.
If you install Data Analyzer on WebSphere Application Server, the installer configures
WebSphere Application Server security and Data Analyzer authentication based on your
selection and the WebSphere Application Server setup.

Table 6-2 describes the configuration tasks performed by the installer when you install
Data Analyzer on WebSphere Application Server:
Table 6-2. WebSphere Application Server Security and Repository Authentication
WebSphere Configure
Security Repository Installer Action
Enabled? Authentication?
Yes Yes The installer changes the existing WebSphere Application Server
Console administrator user name to admin and the password to admin
and configures repository authentication for Data Analyzer.
Yes No The installer leaves WebSphere Application Server Console security

settings intact and does not change the administrator user name and
password. The installer does not configure repository authentication.
No Yes The installer enables the WebSphere Application Server Console

security and sets the administrator user name to admin and the
password to admin. The installer configures repository authentication for
Data Analyzer.
No No The installer does not enable WebSphere Application Server Console

security and does not configure repository authentication for Data
Analyzer.
For more information about configuring authentication, see “Configuring

Authentication” in the Data Analyzer Administrator Guide.
60. Click Next.
The installer displays a message about the application server configuration tasks
performed by the installer. Click Cancel to return to the Data Analyzer and Metadata
Manager Authentication window.
Click Continue to continue with the installation.

The Data Analyzer Repository Configuration window appears.
61. Select whether to use a new or existing Data Analyzer repository.

To create a Data Analyzer repository during the installation, select Create new Data
Analyzer repository. To use an existing Data Analyzer repository, select Use Existing Data
Analyzer repository content. To use existing Data Analyzer repository content, you may
need to upgrade the repository after installation.
62. Select a database type and enter the database information for the Data Analyzer
repository.
Table 6-3 describes the information required to for the Data Analyzer repository:
Table 6-3. Data Analyzer Repository Information
Option Description
Database type Type of database for the Data Analyzer repository.
Database URL Database connection string. When you select the database type, the Data Analyzer
Repository Configuration window displays the database URL format for the selected
database type:
Oracle: host_name:port_number;SID=sid
DB2:host_name:port_number;DatabaseName=databasename
Microsoft SQL Server:
host_name:port_number;SelectMethod=cursor;DatabaseName=databasename
Sybase ASE: host_name:port;DatabaseName=database_name
Database Password for the user account to connect to the database.

password

64. Click Next.
The installer configures Data Analyzer and the application server, configures the Data
Analyzer repository, and starts the application server.
The PowerCenter Installation Summary window indicates whether the installation
completed successfully. It also shows the configured properties for PowerCenter
components and the status of installed components.
65. Click Done.
You can view the log files generated by the installer to obtain more information about the
installation tasks performed by the installer and view configuration properties for the installed
components. For more information about the log files generated by the installer, see “Installer
Log Files” on page 362.

Installing PowerCenter Advanced Edition
The PowerCenter installer in graphical mode displays the same windows for UNIX and
Windows. Unless otherwise noted, the following procedure refers to both UNIX and
Windows installation.
The PowerCenter installer creates the Integration Service and Repository Service and
configures the PowerCenter repository for Metadata Manager. After installation, you use the
Administration Console to create a PowerCenter repository and create and configure the
Integration Service and Repository Service for use in PowerCenter.
To install PowerCenter Advanced Edition:
Install” on page 49. Verify that you have the PowerCenter Advanced Edition license.
installer.
-or-
7. Click Next.


8. Click Next.
Installing PowerCenter Advanced Edition 129

9. Enter the location and file name of the PowerCenter Advanced Edition license key or
click Browse to locate the license key file.
10. Click Next.
and the disk space requirements. Verify that all PowerCenter installation requirements are
met before you continue the installation. For more information about the prerequisites,
see “Pre-Installation Tasks” on page 50.
11. Click Next.
12. To install the complete set of PowerCenter Advanced Edition components, select
Complete and click Next.
To install a custom version of PowerCenter, see “PowerCenter Custom Installation in
Graphical Mode” on page 153.

13. Enter the location and file name of the Data Analyzer or Metadata Manager license key
or click Browse to locate the license key file.
14. Click Next.

16. Click Next.
17. Select the application server to install Data Analyzer and Metadata Manager on. The
installer installs Data Analyzer and Metadata Manager on the same application server.
♦ JBoss Application Server. You can install Data Analyzer and Metadata Manager on a
new or existing instance of JBoss Application Server. If you select JBoss Application
Server, continue to the next step.
♦ BEA WebLogic Server. You install Data Analyzer and Metadata Manager on an
existing instance of BEA WebLogic Server. You can create a new WebLogic Server
domain or install Data Analyzer and Metadata Manager on an existing WebLogic
Server domain. If you select WebLogic Server, skip to step 23.
♦ WebSphere Application Server. You install Data Analyzer and Metadata Manager on
32.

♦ WebSphere Application Server (Base). You install Data Analyzer and Metadata
Manager on an existing WebSphere Application Server Base Edition instance. If you
select WebSphere Application Server Base Edition, skip to step 30.
18. Click Next.
The JBoss Application Server Directory window appears.
instance that exists.
If you use an existing instance of JBoss Application Server, verify that the application
server is shutdown before you continue the installation.

You can configure the ports used by the JBoss Application Server to avoid port conflicts if
23. Click Next.


24. Click Next.
25. Choose to install Data Analyzer and Metadata Manager on a new domain or an existing
domain. Provide the domain name and location.

If you are installing Data Analyzer and Metadata Manager on a new WebLogic domain,
continue to the next step. If you are installing on an existing WebLogic domain, skip to
step 28.
26. Click Next.
28. Click Next.

The installer will install Data Analyzer and Metadata Manager on an existing WebLogic
domain in WebLogic Server.
30. Click Next.

31. Enter the home directory for WebSphere Base Server or click Browse to locate the
32. Click Next.
34. Click Next.

Server name Name of the server to run Data Analyzer and Metadata Manager on. Default is server1.
name.
36. Click Next.

After you click Install, the installer copies the files for PowerCenter Advanced Edition to
the installation directory. When the file copy process completes, the Create or Join
Domain window appears.
-or-

39. Click Next.

Database type Type of database you created. Database type may be Oracle, Microsoft SQL Server,
Sybase ASE, or IBM DB2.
name>:<port>.
41. Click Next.

the following characters: \ / : * ? > < " | .
characters.
Note: By default, the installer creates a Repository Service and an Integration Service for
Metadata Manager in the PowerCenter domain. You can create a separate Repository

Service and Integration Service for the PowerCenter repository after you complete the
installation.
Skip to step 51.
45. Click Next.

47. Click Next.

node.Do not use the following characters: \ / : * ? < > " |

Note: By default, the installer creates a Repository Service and Integration Service for
installation.
51. Click Next.
The Configure Informatica Services window appears.
a PowerCenter domain. Configure the user account if PowerCenter Services needs to

information, see the Windows documentation.
53. Click Next.


PowerCenter repository content.

Option Description
Repository name Name for the PowerCenter repository. The name is case sensitive, must be less than 30
character and not contain the following characters: \/:*?<>“|
Note: If you join a domain, the installer creates the Repository Service for the PowerCenter
repository for Metadata Manager on the gateway node for the domain. The installer
includes a generic list of code pages for the PowerCenter repository. Verify that the code
page you select is available on the gateway node for the domain you are joining.

password
selected database:
the name of the Microsoft SQL Server instance that contains the dbname database.
Database name Appears for DB2 database only. DB2 alias name for the repository database.
Tablespace name Appears for DB2 database only. Name of the tablespace in which to create the repository


57. Click Next.
movement mode of the associated PowerCenter repository for Metadata Manager.
Create Integration Enable this option to create an Integration Service. In a complete PowerCenter Advanced
Service Edition installation, the installer creates an Integration Service by default.
This option is available if you select an existing PowerCenter repository for Metadata
Manager.
Password Password for the associated repository database user account.
59. Click Next.

-or-
is compatible with Data Analyzer and Metadata Manager. Otherwise, you cannot log in
to Data Analyzer or Metadata Manager.
If you install Data Analyzer or Metadata Manager on WebSphere Application Server, the
installer configures WebSphere Application Server security and Data Analyzer or
Metadata Manager authentication based on your selection and the WebSphere
Application Server setup.

Data Analyzer and Metadata Manager on WebSphere Application Server:
WebSpher Configure
e Security Repository Installer Action
Yes Yes The installer changes the existing WebSphere Application Server Console
administrator user name to admin and the password to admin and
configures repository authentication for Data Analyzer and Metadata
Manager.

No Yes The installer enables the WebSphere Application Server Console security
and sets the administrator user name to admin and the password to admin.
The installer configures repository authentication for Data Analyzer and
Metadata Manager.

security and does not configure repository authentication for Data Analyzer

Authentication” in the Data Analyzer Administrator Guide and “Managing
61. Click Next.


Analyzer repository. To use an existing Data Analyzer repository, select Use existing Data
Analyzer repository content
repository.
Table 6-6 describes the information required for the Data Analyzer repository:
Option Description
database type:

password

65. Click Next.
The Metadata Manager Repository Configuration window appears.
66. Select whether to use a new or existing Metadata Manager repository.

To create a Metadata Manager repository during the installation, select Create new
Metadata Manager repository. To use an existing Metadata Manager repository, select Use
existing Metadata Manager repository content.
67. Select a database type and enter the database information for the Metadata Manager
repository.
Table 6-7 describes the information required for the Metadata Manager repository:
Table 6-7. Metadata Manager Repository Information
Option Description
Database type Type of database for the Metadata Manager repository.
Database URL Database connection string. When you select the database type, the Metadata Manager
database type:

Option Description

password

69. Click Next.
The installer configures Data Analyzer, Metadata Manager, and the application server. It
configures the Data Analyzer and Metadata Manager repositories and starts the
application server. The PowerCenter Installation Summary window indicates whether the
installation completed successfully. It also shows the configured properties for
PowerCenter components and the status of installed components.
70. Click Done.

Chapter 7
PowerCenter Custom Installation

in Graphical Mode
♦ Overview, 154
♦ Installing PowerCenter Services, 155
♦ Upgrading from PowerCenter 8.1, 170
♦ Installing Data Analyzer, 175
♦ Installing Metadata Manager, 191
153
Overview
This chapter provides instructions on running the PowerCenter graphical mode installer and
installing a custom version of PowerCenter. When you select the custom installation option,
the PowerCenter installer determines the components available for installation based on the
license key you provide.
With the custom installation, you can install the PowerCenter components separately. If you
choose to install more than one component, the PowerCenter installer installs all the selected
components on the same machine in the directory that you provide. You can provide a
different database for each repository.
Before you install PowerCenter, complete the steps listed in “Pre-Installation Tasks” on
page 50.
You can install the following PowerCenter components:
♦ PowerCenter Services. Install only PowerCenter Services. When you install PowerCenter
Services, you can choose the following options:
− Install PowerCenter Services. Install PowerCenter Services if you have not installed
PowerCenter Services or if you are upgrading from version 8.0 or earlier. For more
information about installing PowerCenter, see “Installing PowerCenter Services” on
page 155.
− Upgrade PowerCenter Services. Install PowerCenter Services and upgrade the domain
and node metadata if you upgrade from PowerCenter 8.1. For more information about
upgrading PowerCenter, see “Upgrading from PowerCenter 8.1” on page 170.
♦ Data Analyzer. Install only Data Analyzer. For more information, see “Installing Data
Analyzer” on page 175.
♦ Metadata Manager. Install only Metadata Manager. For more information, see “Installing
Metadata Manager” on page 191.
154 Chapter 7: PowerCenter Custom Installation in Graphical Mode

Installing PowerCenter Services
This section shows how to perform a custom installation of PowerCenter. Use the same
procedure to install PowerCenter Standard or Advanced Edition.
To install PowerCenter Services:
installer.
-or-
The Welcome window introduces the PowerCenter Standard Edition installation.
7. Click Next.
Installing PowerCenter Services 155


8. Click Next.

9. Enter the location and file name of the PowerCenter license key or click Browse to locate
the license key file.
10. Click Next.
and the disk space requirements. Make sure that all PowerCenter installation
requirements are met before you continue the installation.
11. Click Next.
12. To select the PowerCenter components to install, select Custom and click Next.
The PowerCenter installer displays the list of available PowerCenter components. The
type of license key you provide determines the available components.

For the PowerCenter Standard Edition license, the PowerCenter Standard Edition
Components window appears.
-or-
For the PowerCenter Advanced Edition license, the PowerCenter Advanced Edition
13. To install PowerCenter Services, clear all options except PowerCenter Services and click
Next.


installation directory path must be located on the current machine. If the installation
directory contains a Metadata Manager installation, you cannot install PowerCenter
Services in the directory.
15. Click Next.

The Choose Installation Type window appears.
16. Choose Install PowerCenter 8.1.1.

17. Click Next.

After you click Install, the installer copies the files for the selected components. When
the file copy process completes, the Create or Join Domain window appears.
-or-
20. Click Next.


name>:<port>.
22. Click Next.

characters.
Service select this option to create an Integration Service for the domain using the installer. You
can also create a Repository Service after installation.

26. Click Next.

28. Click Next.


Service this option to also create an Integration Service using the installer.
31. Enter the port range and click OK.
32. Click Next.
On Windows, the Configure Informatica Services window appears.
a PowerCenter domain. Configure the user account if PowerCenter Services needs to

information, see your Windows documentation.
34. Click Next.


To create a PowerCenter repository during the installation, select Create New
PowerCenter Repository.
To use an existing PowerCenter repository, select Use existing PowerCenter repository
content. You may need to upgrade the repository after installing PowerCenter.

Option Description
30 characters. It cannot contain spaces or the following characters: \/:*?<>“|
compatible with the code page of the machine where you install PowerCenter. For more
information about code pages, see “Code Pages” on page 45.
the repository code page. You must ensure that the code page for the existing repository is

Password
selected database:
Example: OraDB.world

38. Click Next.

Create Integration Enable this option to create an Integration Service.

Service
Password Password for the PowerCenter repository database user account.
40. Click Next.

When the installation completes, the PowerCenter Installation Summary window
indicates whether the installation completed successfully. It also shows the configured
properties for PowerCenter components and the status of installed components.
41. Click Done.
installation tasks performed by the installer and view configuration properties for the
installed components. For more information about the log files generated by the installer,
see “Installer Log Files” on page 362.

Upgrading from PowerCenter 8.1
This section shows how to perform a custom installation of PowerCenter to upgrade
PowerCenter Services 8.1. Use the same procedure to install and upgrade PowerCenter
Services for PowerCenter Standard and Advanced Edition.
To upgrade PowerCenter Services 8.1:
the pre-upgrade tasks.
For more information about preparing for the PowerCenter installation, see
installer.
-or-
7. Click Next.


8. Click Next.
Upgrading from PowerCenter 8.1 171

10. Click Next.
11. Click Next.
12. Select Custom and click Next.

13. To upgrade PowerCenter Services, clear all options except PowerCenter Services and click
Next.
14. Click Next.
The Choose Installation Type window appears.
15. Choose Upgrade to PowerCenter 8.1.1.

16. Click Next.

You must use the directory where you installed PowerCenter Services 8.1.
The installation directory path must be an absolute path. On Windows, the installation
directory path must be located on the current machine.
18. Click Next.
The installer installs PowerCenter Services and updates the previous installation.
installation tasks performed by the installer. For more information about the log files
generated by the installer, see “Installer Log Files” on page 362.

Installing Data Analyzer
This section shows how to perform a custom installation of PowerCenter to install Data
Analyzer. Use the same procedure to install Data Analyzer for PowerCenter Standard and
Advanced Edition.
To install Data Analyzer:
For information about the user requirements, see “Step 4. Create a System User Account”
on page 58.
installer.
-or-
7. Click Next.
Installing Data Analyzer 175


8. Click Next.

10. Click Next.
11. Click Next.

-or-
For the PowerCenter Advanced Edition license, the PowerCenter Advanced Edition
13. To install Data Analyzer, clear all options except Data Analyzer and click Next.

14. Enter the location and file name of the Data Analyzer license key or click Browse to
15. Click Next.


17. Click Next.
18. Select the application server to install Data Analyzer on. The installer installs Data
Analyzer on the same application server.
♦ JBoss Application Server. You can install Data Analyzer on a new or existing instance
of JBoss Application Server. If you select JBoss Application Server, continue to the
next step.
♦ BEA WebLogic Server. You install Data Analyzer on an existing instance of BEA
WebLogic Server. You can create a new WebLogic Server domain or install Data
Analyzer on an existing WebLogic Server domain. If you select WebLogic Server, skip
to step 24.
♦ WebSphere Application Server (Network Deployment). You install Data Analyzer on
33.
♦ WebSphere Application Server (Base). You install Data Analyzer on an existing
19. Click Next.

The JBoss Application Server Directory window appears.
existing instance.

24. Click Next.


25. Click Next.
26. Choose to install Data Analyzer on a new domain or an existing domain. Provide the
domain name and location. If you are installing Data Analyzer on a new WebLogic
domain, continue to the next step. If you are installing on an existing WebLogic domain,
skip to step 29.

27. Click Next.
29. Click Next.
The installer will install Data Analyzer on an existing WebLogic domain in WebLogic
Server.

31. Click Next.
33. Click Next.

34. Enter the home directories for the WebSphere Base Server and Network Deployment or
click Browse to locate the directory.
35. Click Next.

name.
37. Click Next.

verify that the installer will install Data Analyzer components in the correct location and
After you click Install, the installer copies the files for Data Analyzer to the installation
directory.
Note: WebLogic Server and WebSphere Application Server support only one
authentication method for all applications running on the same instance of the
application server.

-or-
is compatible with Data Analyzer. Otherwise, you cannot log in to Data Analyzer.
WebSphere Configure
configures repository authentication for Data Analyzer.

The installer configures repository authentication for Data Analyzer.

Analyzer.

40. Click Next.
Otherwise, click Continue to continue with the installation.
41. Click Next.


Analyzer repository. To use an existing Data Analyzer repository, select Use Existing Data
Analyzer repository content.
repository.
Option Description
database type:
For more information about the JDBC drivers installed withPowerCenter, see “JDBC Drivers”
on page 553.

password

45. Click Next.
The installer configures the Data Analyzer repository and configures and starts the
application server.
completed successfully. It also shows the configured properties for Data Analyzer
46. Click Done.

Installing Metadata Manager
This section shows how to perform a custom installation of PowerCenter to install Metadata
Manager. You can install Metadata Manager if you have a PowerCenter Advanced Edition
license.
The PowerCenter domain must be available when you install Metadata Manager. Verify that
the gateway node for the domain is available before you continue. The installer creates a
Repository Service and an Integration Service in the domain during installation. If the
PowerCenter installer cannot connect to the PowerCenter domain, you cannot continue with
the installation.
To install Metadata Manager:
installer.
-or-
7. Click Next.
Installing Metadata Manager 191


8. Click Next.

9. Enter the location and file name of the PowerCenter Advanced Edition license key or
click Browse to locate the license key file.
10. Click Next.
11. Click Next.
The Installation Set window displays the PowerCenter Advanced Edition installation
options.

The PowerCenter Advanced Edition Components window appears.
13. To install Metadata Manager, clear all options except Metadata Manager and click Next.
14. Enter the location and file name of the Metadata Manager license key or click Browse to
15. Click Next.


The default directory on Windows is C:\Informatica\PowerCenter8.1.1,
The installation directory path must be an absolute path. On Windows, the installation
directory path must be located on the current machine. If the installation directory
contains a PowerCenter Services installation, you cannot install Metadata Manager in the
directory.
17. Click Next.

18. Select the application server to install Metadata Manager on.

♦ JBoss Application Server. You can install Metadata Manager on a new or existing
instance of JBoss Application Server. If you select JBoss Application Server, continue
to the next step.
♦ BEA WebLogic Server. You can install Metadata Manager on BEA WebLogic Server.
You can create a new WebLogic Server domain with the installer or install Metadata
Manager on an existing WebLogic Server domain. If you select WebLogic Server, skip
to step 24.
♦ WebSphere Application Server (Network Deployment). You install Metadata
Manager on an existing WebSphere Application Server Network Deployment Edition
instance. If you select WebSphere Application Server Network Deployment Edition,
skip to step 33.
♦ WebSphere Application Server (Base). You install Metadata Manager on an existing
19. Click Next.

The JBoss Application Server window appears.
existing instance.

24. Click Next.


25. Click Next.
26. Choose to install Metadata Manager on a new domain or an existing domain. Provide the
domain name and location. If you are installing Metadata Manager on a new WebLogic
domain, continue to the next step. If you are installing on an existing WebLogic domain,
skip to step 29.

27. Click Next.
29. Click Next.
The installer will install Metadata Manager on an existing WebLogic domain in

WebLogic Server.

31. Click Next.
33. Click Next.

35. Click Next.

Server name Name of the server to run Metadata Manager on. Default is server1.
name.
37. Click Next.

verify that the installer will install Metadata Manager components in the correct location
and with the options you select.
After you click Install, the installer copies the Metadata Manager files to the installation
directory. When the file copy process completes, the Configure Domain window appears.
The installer creates the Repository Service and Integration Service for the PowerCenter
repository for Metadata Manager on the gateway node for the domain.

Domain name Name of the PowerCenter domain where the installer creates the Repository
Service and Integration Service for Metadata Manager.
Domain host name Host name of the gateway node for the domain.
Domain port no. Port number for the gateway node for the domain.
Domain user name User name for the administrator account in the domain.
Node name Name of the gateway node for the domain.
40. Click Next.


PowerCenter repository content.

Option Description
character and cannot contain spaces or the following characters: \/:*?<>“|
Note: The installer includes a generic list of code pages for the PowerCenter repository.
Verify that the code page you select is available on the gateway node for the domain. If you
select an existing repository, the code page must also be compatible with the repository. If
you select an invalid code page, the installation will fail.
password
selected database:
Microsoft SQL Server: Syntax is SQLServername@dbname, where SQLServername is

44. Click Next.

Create Integration Enable this option to create an Integration Service. In a Metadata Manager installation, the
Service installer creates an Integration Service by default.
Manager.
46. Click Next.

application server.
-or-
is compatible with Data Analyzer and Metadata Manager. Otherwise, you cannot log in
to Data Analyzer or Metadata Manager.

Metadata Manager on WebSphere Application Server:
WebSphere Configure
configures repository authentication for Metadata Manager.

The installer configures repository authentication for Metadata Manager.

security and does not configure repository authentication for Data Analyzer.
For more information about configuring authentication, see “Managing Authentication

for Metadata Manager” in the Metadata Manager Administrator Guide.
48. Click Next.

The Metadata Manager Repository Configuration window appears.
49. Select whether to use a new or existing Metadata Manager repository.

To create a Metadata Manager repository during the installation, select Create new
Metadata Manager repository. To use an existing Metadata Manager repository, select Use
existing Metadata Manager repository content.
50. Select a database type and enter the database information for the Metadata Manager
repository.
Option Description
Database type Type of database for the Metadata Manager repository.
Database URL Database connection string. When you select the database type, the Metadata Manager
database type:
host_name:port_number;SelectMethod=cursor;DatabaseName=database
name
For more information about the JDBC drivers installed withPowerCenter, see “JDBC
Drivers” on page 553.
Database password Password for the user account to connect to the database.

52. Click Next.
The installer configures Metadata Manager and the application server, configures the
Metadata Manager repository, and starts the application server.
completed successfully. It also shows the configured properties for Metadata Manager
53. Click Done.

Chapter 8
PowerCenter Complete
Installation in Console Mode
♦ Overview, 212
♦ Installing PowerCenter Standard Edition, 213
♦ Installing PowerCenter Advanced Edition, 224
211
Overview
This chapter provides instructions on running the PowerCenter console mode installer and
installing the complete version of PowerCenter. When you install the complete version of
PowerCenter, the PowerCenter installer determines the components available for installation
based on the license key you provide.
The console mode installer is similar to the graphical mode installer. Each panel in the
console mode installer prompts you for the same information as each window in the graphical
mode installer.
page 50.
You can install the complete version of the following PowerCenter editions:
♦ PowerCenter Standard Edition. Installs all PowerCenter Standard Edition components.
Standard Edition includes PowerCenter and Data Analyzer for PowerCenter Repository
Reports. For more information, see “Installing PowerCenter Standard Edition” on
page 213.
♦ PowerCenter Advanced Edition. Installs all PowerCenter Advanced components,
including PowerCenter Services, Data Analyzer, and Metadata Manager. For more
information, see “Installing PowerCenter Advanced Edition” on page 224.
Rules and Guidelines for Using Console Mode

Use the following rules and guidelines when installing PowerCenter with the console mode
installer:
♦ Each panel in the installer prompts for configuration information. After the installer
collects the information and configures PowerCenter, you may not be able to return to a
previous step.
After you install, you can change the PowerCenter services settings in the Administration
Console.
♦ Each prompt displays default values. You can press Enter to accept default values or enter
configuration information at the prompt to change the default value.
♦ To enter multiple values in a prompt that accepts multiple values, separate values with
commas.
♦ Enter quit at any time to quit the installer.
♦ Passwords are not encrypted at the prompt.
♦ If you enter a value for an optional property, such as an IBM DB2 tablespace name, the
installer uses it as the default value if you return to the panel. If you do not want to use the
value you entered, you can remove the default value by entering a space for the property.
212 Chapter 8: PowerCenter Complete Installation in Console Mode

Installing PowerCenter Standard Edition
You can install PowerCenter Standard Edition using console mode on UNIX.
To install PowerCenter Standard Edition:
4. On a shell command line, run install.sh located in the DVD root directory or the root
directory in the location where you downloaded the installer.
The PowerCenter installer checks the operating system and verifies that the environment
variables are correctly set. The environment variables must be specifically set to enable
the PowerCenter installer to run processes and connect to databases and services. If the
environment variables are not set, the PowerCenter installer gives you the option to stop
the installation and modify the environment variables.
5. Select the option to use the Console mode installation.
The Welcome panel introduces the PowerCenter installation.
6. Press Enter.
The Configure Environment Variables panel appears.
The PowerCenter installer requires specific environment variable settings. Read the
PowerCenter environment configuration requirements and set the environment variables
before you continue with the installation. If you do not set the environment variables as
required, the PowerCenter installation may fail.
7. Enter quit to exit the installer if the required environment variables are not set.
-or-
Press Enter to continue with the installation.
The PowerCenter License Key panel appears.
8. Enter the location and file name of the PowerCenter Standard Edition license key.
9. Press Enter.
The Installation Prerequisites panel displays the supported platforms and databases and
the disk space requirements. Verify that all PowerCenter installation requirements are

10. Press Enter.
The Installation Set panel displays the PowerCenter installation options.
11. To install the complete set of PowerCenter Standard Edition components, press Enter.
The Data Analyzer/Metadata Manager License Key panel appears.
12. Enter the location and file name of the Data Analyzer license key.
13. Press Enter.
The Installation Directory panel appears.
Use the default directory or enter the path to a directory. The default directory on UNIX
is $HOME/Informatica/PowerCenter8.1.1, where HOME is the user home directory.
The installation directory path must be an absolute path.
14. Press Enter.
The Application Server panel appears.
Select the application server to install Data Analyzer on to run PowerCenter Repository
Reports.
15. Enter one of the following options:
Option Description
1 - JBoss Application You can install Data Analyzer on a new or existing instance of JBoss Application Server.
Server If you select JBoss Application Server, continue to the next step.
2 - BEA WebLogic You install Data Analyzer on an existing instance of BEA WebLogic Server. You can
Server create a new WebLogic Server domain or install Data Analyzer on an existing WebLogic
3 - IBM WebSphere You can install Data Analyzer on an existing WebSphere Application Server Network
Application Server Deployment Edition instance. If you select WebSphere Application Server Network
(Network Deployment Edition, skip to step 35.
Deployment)
4 - IBM WebSphere You can install Data Analyzer on an existing WebSphere Application Server Base
Application Server Edition instance. If you select WebSphere Application Server Base Edition, skip to step
(Base) 33.
16. Press Enter.

The JBoss Application Server panel appears.
Option Description
1 Install new JBoss Application Server.
2 Use existing JBoss Application Server.

18. Press Enter.
19. Enter the home directory for JBoss Application Server.
20. Press Enter.
21. Enter the server configuration directory.
22. Press Enter.
23. To configure the JBoss Application Server ports, enter Y at the prompt and enter the
values for the JBoss Application Server ports. Enter N to accept the default values.
Table 8-1 describes the JBoss Application Server ports and the default port values:
Table 8-1. JBoss Application Server Default Port Values
Port Name Default Port
HTTP Connector Port 8080
JBoss MQ Service Port 8093
IIOP Port 3538
JMS Server Port 1099
Web Service Port 8093
RMI Services Bind Address Port 1098
RMI Invoker Port 4444
JRMP Invoker Port 4445
HA-JNDI Stub Availability 1100
JRMP Invoker Port for cluster 4446
UDP Binding Port 45566
SNMP Adaptor Port 1161
SNMP Manager Port 1162
Tomcat Cluster Port 40000-50000
Skip to step 39 to continue with the installation.

24. Press Enter.

The WebLogic Server Directory panel appears.
25. Enter the existing WebLogic Server directory.
26. Press Enter.
The WebLogic Application Server Domain panel appears.
Option Description
1 Create a new WebLogic domain.
2 Use an existing WebLogic domain.
28. Enter the WebLogic domain name and location. If you are installing Data Analyzer on a
new WebLogic domain, continue to the next step.
If you are installing on an existing WebLogic domain, skip to step 31.
29. Press Enter.
The New WebLogic Domain Configuration panel appears.
31. Press Enter.
The Existing WebLogic Server Domain Configuration panel appears.
33. Press Enter.
The Existing WebSphere Application Server Directory panel appears.
34. Enter the home directory for the WebSphere Base Server. Skip to step 37.
35. Press Enter.
36. Enter the home directories for the WebSphere Base Server and the Network Deployment.
37. Press Enter.
The WebSphere Application Server Administration Details panel appears.
38. Enter the following information at the prompt:
Prompt Description

Prompt Description
name.
39. Press Enter.

The Pre-Installation Summary panel appears. Review the pre-installation summary to
40. Press Enter to continue or enter back to return and modify the options.
The installer copies the files for the selected components to the installation directory.
When the file copy process completes, the Create or Join Domain panel appears.
41. Enter the appropriate option:
Option Description
1 - Create New Domain Choose this option if you are installing PowerCenter for the first time or you are
installing PowerCenter on a single machine. If you choose to create a domain,
Continue to the next step.
2 - Join Existing Domain Choose Join Existing Domain if a PowerCenter domain already exists on a
PowerCenter instance installed on another machine. If you choose to join a
domain, skip to step 47.
For more information about the available domain options, see “Single or Multiple
Machine Installation” on page 17.
42. Press Enter.
The Configure Domain Database panel appears.
domain configuration database must be accessible by all gateway nodes in the domain.
Prompt Description
name>:<port>.

Prompt Description
44. Press Enter.

The Configure Domain panel appears.
Prompt Description
characters.
Service (Y/N) select this option to create an Integration Service for the domain using the installer.
46. To configure the range of available ports that the PowerCenter installer can use for the
PowerCenter Services that it installs on the node, enter Y at the prompt and enter the
range of available ports. To accept the default values, enter N.
Skip to step 52.
47. Press Enter.

Prompt Description
49. Press Enter.

The Configure Node panel appears.
Prompt Description
Service (Y/N) this option to also create an Integration Service using the installer.
Gateway (Y/N) node is a worker node in the domain you join.
51. To configure the range of available ports that the PowerCenter installer can use for the
PowerCenter Services that it installs on the node, enter Y at the prompt and enter the
range of available ports. To accept the default values, enter N.
52. Press Enter.
The PowerCenter Repository Configuration panel appears.

Option Description
1 Create new PowerCenter repository.
2 Use existing PowerCenter repository content.
To use existing PowerCenter repository content, you may need to upgrade the repository
after installing PowerCenter.
54. Press Enter.
The Configure PowerCenter Repository panel requires different information based on
the database type you select.
Prompt Description
*?><"|
Password
Connect string Appears for Oracle and Sybase ASE databases only.
selected database:
55. Press Enter.

message displays the reason for the failure. You can continue the installation if the
The Configure Integration Service panel appears.
Prompt Description
Create Integration Select Y to create an Integration Service.

Service (Y/N)
tabs, exceed 79 characters, or contain the following characters: \ / * ? < > " |
57. Press Enter.

Authentication panel appears.
58. Enter Y to overwrite the authentication in the application server with repository
-or-
Enter N to keep the current authentication settings in the application server. If you select
No, the application server must be configured with an authentication method that is
compatible with Data Analyzer. Otherwise, you cannot log in to Data Analyzer.

WebSphere Configure


Analyzer.

59. Press Enter.
performed by the installer.
60. Enter N to return to the Data Analyzer and Metadata Manager Authentication panel.
-or-
Enter Y to continue with the installation.
The Data Analyzer Repository Configuration panel appears.
Option Description
1 Create a new Data Analyzer repository.
2 Use existing Data Analyzer repository content.
To use existing Data Analyzer repository content, you may need to upgrade the
repository after installation.
62. Press Enter.
63. Enter the Data Analyzer repository configuration information.

Option Description

Enter the appropriate number for the repository database type.
Database URL Database connection string. Use the following format:


password
64. Press Enter.

The installer configures Data Analyzer and the application server, starts the application
server, and configures the Data Analyzer repository.
The PowerCenter Installation Summary panel indicates whether the installation
65. Press Enter.
You can view the log files generated by the installer to get more information about the

Installing PowerCenter Advanced Edition
You can install PowerCenter Advanced Edition using console mode on UNIX.
The PowerCenter installer creates the Integration Service and Repository Service and
configures the PowerCenter repository for Metadata Manager. After installation, you use the
Administration Console to create a PowerCenter repository and create and configure the
Integration Service and Repository Service for use in PowerCenter.
To install PowerCenter Advanced Edition:
6. Press Enter.
-or-
If the environment variables are set, press Enter.
8. Enter the location and file name of the PowerCenter Advanced Edition license key.
9. Press Enter.

the disk space requirements. Verify that all PowerCenter installation requirements are
10. Press Enter.
11. To install the complete set of PowerCenter Advanced Edition components, press Enter.
13. Press Enter.
Use the default directory or enter the path to a directory. The default directory on UNIX
14. Press Enter.
Select the application server to install Data Analyzer and Metadata Manager on. The
installer installs Data Analyzer and Metadata Manager on the same application server.
Option Description
1 - JBoss Application You can install Data Analyzer and Metadata Manager on a new or existing instance of
Server JBoss Application Server. If you select JBoss Application Server, continue to the next
step.
2 - BEA WebLogic You install Data Analyzer and Metadata Manager on an existing instance of BEA
Server WebLogic Server. You can create a new WebLogic Server domain or install Data
Analyzer on an existing WebLogic Server domain. If you select WebLogic Server, skip to
step 23.
Deployment)
Application Server Edition instance. If you select WebSphere Application Server Base Edition, skip to step
(Base) 32.
16. Press Enter.


Option Description
18. Press Enter.

20. Press Enter.
IIOP Port 3538


23. Press Enter.
25. Press Enter.
Option Description
28. Press Enter.
listening port number for the new domain.
Skip to step 38.
30. Press Enter.
32. Press Enter.
34. Press Enter.

36. Press Enter.
Prompt Description
Server name Name of the server to run Data Analyzer and Metadata Manager on. Default is server1.
name.
38. Press Enter.

Press Enter to continue or enter back to return and modify the options.
After you press Enter, the installer copies the files for PowerCenter Advanced Edition to
the installation directory. When the file copy process completes, the Create or Join
Domain panel appears.
39. Enter the appropriate option.
Option Description
continue to the next step.
40. Press Enter.

Prompt Description
Database type Type of database you created. Database type may be Oracle, Microsoft SQL Server,
Sybase ASE, or IBM DB2.
name>:<port>.
42. Press Enter.

Prompt Description
characters.
Note: By default, the installer creates a Repository Service and Integration Service for
installation.

44. To set the range of port numbers that the PowerCenter installer can use for the
PowerCenter services on the node, enter Y at the prompt and enter the range of available
ports. Enter N to accept the default values.
45. Press Enter.
The PowerCenter domain must be available. Verify that the gateway node for the domain
you want to join is available before you continue. If the PowerCenter installer cannot
connect to the PowerCenter domain, you cannot continue with the installation.
Prompt Description
47. Press Enter.

Prompt Description
ports. Enter N to accept the default values.

50. Press Enter.
Option Description
1 Create a new PowerCenter repository.
52. Press Enter.

The PowerCenter Repository Configuration panel requires different information based
Prompt Description
character and not contain the following characters: \/:*?<>“|
Note: If you join a domain, the installer creates the Repository Service for the PowerCenter
repository for Metadata Manager on the gateway node for the domain. The installer
includes a generic list of code pages for the PowerCenter repository. Verify that the code
page you select is available on the gateway node for the domain you are joining.
Password
Connect string Appears for Oracle and Sybase ASE databases only.
selected database:

Prompt Description
53. Press Enter.

54. Press Enter.
Prompt Description
Manager.
56. Press Enter.

-or-
compatible with Data Analyzer and Metadata Manager. Otherwise, you cannot log in to
Data Analyzer or Metadata Manager.

Data Analyzer and Metadata Manager on WebSphere Application Server:
WebSphere Configure
configures repository authentication for Data Analyzer and Metadata
Manager.

The installer configures repository authentication for Data Analyzer and
Metadata Manager.

security and does not configure repository authentication for Data Analyzer

Authentication” in the Data Analyzer Administrator Guide and “Managing
58. Press Enter.
-or-
Option Description
1 Create new Data Analyzer repository.

61. Press Enter.
Option Description



password
63. Press Enter.

The Metadata Manager Repository Configuration panel appears.
Option Description
1 Create new Metadata Manager repository.
2 Use existing Metadata Manager repository content.
To use existing Metadata Manager repository content, you may need to upgrade the
65. Press Enter.
Enter the Metadata Manager configuration information.

Prompt Description
Database Type Type of database for the Metadata Manager repository.

Database URL Database connection string. Use the following syntax:

Database User ID Name of the user account to connect to the repository database.

Password
66. Press Enter.

The installer configures Data Analyzer, Metadata Manager, and the application server. It
configures the Data Analyzer and Metadata Manager repositories and starts the
application server.
67. Press Enter.
You can view the log files generated by the installer to get more information about the

Chapter 9
PowerCenter Custom Installation

in Console Mode
♦ Overview, 238
♦ Installing PowerCenter Services, 240
♦ Upgrading from PowerCenter 8.1, 246
♦ Installing Data Analyzer, 248
♦ Installing Metadata Manager, 255
237
Overview
This chapter provides instructions on running the PowerCenter console mode installer. When
you select the custom installation option, the PowerCenter installer determines the
components available for installation based on the license key you provide.
With the custom installation, you can install the PowerCenter components separately. If you
choose to install more than one component, the PowerCenter installer installs all the selected
components on the same machine in the directory that you provide. You can provide a
different database for each repository.
mode installer.
page 50.
You can install the following PowerCenter components:
♦ PowerCenter Services. Install only PowerCenter Services. When you install PowerCenter
Services, you can choose the following options:
− Install PowerCenter Services. Install PowerCenter Services if you have not installed
PowerCenter Services or if you are upgrading from version 8.0 or earlier. For more
information about installing PowerCenter, see “Installing PowerCenter Services” on
page 240.
− Upgrade PowerCenter Services. Install PowerCenter Services and upgrade the domain
and node metadata if you upgrade from PowerCenter 8.1. For more information about
upgrading PowerCenter, see “Upgrading from PowerCenter 8.1” on page 246.
♦ Data Analyzer. Install only Data Analyzer. For more information, see “Installing Data
Analyzer” on page 248.
♦ Metadata Manager. Install only Metadata Manager. For more information, see “Installing
Metadata Manager” on page 255.

Use the following rules and guidelines when installing PowerCenter with the console mode
installer:
♦ Each panel in the installer prompts for configuration information. After the installer
collects the information and configures PowerCenter, you may not be able to return to a
previous step.
After you install, you can change the PowerCenter services settings in the Administration
Console.
238 Chapter 9: PowerCenter Custom Installation in Console Mode

♦ To enter multiple values in a prompt that accepts multiple values, separate values with
commas.
♦ Passwords are not encrypted at the prompt.
♦ If you enter a value for an optional property, such as an IBM DB2 tablespace name, the
installer uses it as the default value if you return to the panel. If you do not want to use the
value you entered, you can remove the default value by entering a space for the property.
Overview 239
Installing PowerCenter Services
This section shows how to perform a custom installation of PowerCenter. Use the same
procedure to install PowerCenter Standard or Advanced Edition. You can install PowerCenter
Services using console mode on UNIX.
6. Press Enter.
-or-
8. Enter the location and file name of the PowerCenter Standard or Advanced Edition
license key.
9. Press Enter.

the disk space requirements. Make sure that all PowerCenter installation requirements are
10. Press Enter.
11. Select the Custom option and press Enter.
12. To install PowerCenter Services, enter 1.
13. Use the default directory or enter the path to a directory. The default directory on UNIX
Note: The installation directory path must be an absolute path. If the installation
directory contains a Metadata Manager installation, you cannot install PowerCenter
Services in the directory.
14. Press Enter.
The Choose Installation Type panel appears.
15. Enter 1 to install PowerCenter 8.1.1.
16. Press Enter.
The installer copies the files for the selected components to the installation directory.
When the file copy process completes, the Create or Join Domain panel appears.
18. Enter the appropriate option.
Option Description
continue to the next step.
19. Press Enter.

Prompt Description
name>:<port>.
21. Press Enter.

Prompt Description
characters.
Service (Y/N) choose this option to create an Integration Service for the domain using the installer.

ports. To accept the default values, enter N.
Skip to step 29.
24. Press Enter.
Prompt Description
26. Press Enter.

Prompt Description
Service (Y/N) this option to also create an Integration Service using the installer.

ports. To accept the default values, enter N.
29. Press Enter.
Option Description
1 Create a new PowerCenter repository.
To use existing PowerCenter repository content, you may need to upgrade the repository
after installing PowerCenter.
31. Press Enter.
Prompt Description
*?><"|
Password

Prompt Description
Connect string Appears for Oracle and Sybase ASE databases.

selected database:
- Sybase ASE: Syntax is HostName@dbname.
tables. If blank, the installation creates the repository tables in the default tablespace.
32. Press Enter.

Prompt Description
Create Integration Enter Y to create an Integration Service.

Service (Y/N)
34. Press Enter.

When the installation completes, the PowerCenter Installation Summary panel indicates
whether the installation completed successfully. It also shows the configured properties
for PowerCenter components and the status of installed components.
35. Press Enter.

Upgrading from PowerCenter 8.1
This section shows how to perform a custom installation of PowerCenter to upgrade
PowerCenter Services 8.1. Use the same procedure to install and upgrade PowerCenter
Services for PowerCenter Standard and Advanced Edition. You can install PowerCenter
Services using console mode on UNIX.
the pre-upgrade tasks.
For more information about preparing for the PowerCenter installation, see
6. Press Enter.
-or-
license key.
9. Press Enter.

10. Press Enter.
12. To install PowerCenter Services, enter 1 and press Enter.
You must use the directory where you installed PowerCenter Services 8.1. The
installation directory path must be an absolute path.
14. Press Enter.
The Choose Installation Type panel appears.
15. Enter 2 to upgrade to PowerCenter 8.1.1.
16. Press Enter.
The installer installs PowerCenter Services and updates the previous installation.
installation tasks performed by the installer. For more information about the log files
generated by the installer, see “Installer Log Files” on page 362.

Installing Data Analyzer
You can install Data Analyzer using console mode on UNIX.
To install Data Analyzer:
6. Press Enter.
-or-
license key.
9. Press Enter.

10. Press Enter.
12. To install Data Analyzer, enter 2 and press Enter.
The Data Analyzer license key is required to run PowerCenter Repository Reports on
Data Analyzer.
14. Press Enter.
16. Press Enter.
Select the application server to install Data Analyzer on.
Option Description
1 - JBoss Application You can install Data Analyzer on a new or existing instance of JBoss Application Server.
Server If you select JBoss Application Server, continue to the next step.
2 - BEA WebLogic You install Data Analyzer on an existing instance of BEA WebLogic Server. You can
Server create a new WebLogic Server domain or install Data Analyzer on an existing WebLogic
Deployment)
Application Server Edition instance. If you select WebSphere Application Server, skip to step 33.
(Base)
18. Press Enter.


Option Description
20. Press Enter.

22. Press Enter.
IIOP Port 3538

Skip to step 39.

25. Press Enter.
Enter the existing WebLogic Server directory.
26. Press Enter.
Option Description
29. Press Enter.
31. Press Enter.
33. Press Enter.
35. Press Enter.

37. Press Enter.
Prompt Description
name.
39. Press Enter.

verify that the installer will install Data Analyzer components in the correct location and
The installer copies the files for Data Analyzer to the installation directory.
Authentication panel appears when the file copy process completes.
application server.
-or-
Enter N to keep the current authentication settings in the application server. The
application server must be configured with an authentication method that is compatible
with Data Analyzer. Otherwise, you cannot log in to Data Analyzer.

WebSphere Configure


security and does not configure repository authentication for Data Analyzer.

42. Press Enter.
-or-
Option Description
1 Create new Data Analyzer repository.
45. Press Enter.

Option Description


For more information about the JDBC drivers installed with PowerCenter, see “JDBC

password
47. Press Enter.

The installer configures the Data Analyzer repository and configures and starts the
application server.
completed successfully. It also shows the configured properties for Data Analyzer
48. Press Enter.

Installing Metadata Manager
You can install Metadata Manager using console mode on UNIX.
The PowerCenter domain must be available when you install Metadata Manager. Verify that
the gateway node for the domain is available before you continue. The installer creates a
Repository Service and Integration Service in the domain during installation. If the
PowerCenter installer cannot connect to the PowerCenter domain, you cannot continue with
the installation.
To install Metadata Manager:
6. Press Enter.
-or-
If the environment variables are set, press Enter.
8. Enter the location and file name of the PowerCenter Advanced Edition license key.
9. Press Enter.

10. Press Enter.
12. To install Metadata Manager, enter 2 and press Enter.
13. Enter the location and file name of the Metadata Manager license key.
The installation directory path must be an absolute path. If the installation directory
contains a PowerCenter Services installation, you cannot install Metadata Manager in the
directory.
15. Press Enter.
16. Select the application server to install Metadata Manager on. Enter one of the following
options:
Option Description
1 - JBoss Application You can install Metadata Manager on a new or existing instance of JBoss Application
Server Server. If you select JBoss Application Server, continue to the next step.
2 - BEA WebLogic You can install Metadata Manager on an existing instance of BEA WebLogic Server. You
Server can create a new WebLogic Server domain or install Data Analyzer on an existing
WebLogic Server domain. If you select WebLogic Server, skip to step 24.
3 - IBM WebSphere You can install Metadata Manager on an existing WebSphere Application Server
Application Server Network Deployment Edition instance. If you select WebSphere Application Server
(Network Network Deployment Edition, skip to step 35.
Deployment)
4 - IBM WebSphere You can install Metadata Manager on an existing WebSphere Application Server Base
Application Server Edition instance. If you select WebSphere Application Server Base Edition, skip to
(Base) step 33.
17. Press Enter.


Option Description
19. Press Enter.

21. Press Enter.
IIOP Port 3538

Skip to step 39.

24. Press Enter.
26. Press Enter.
Option Description
new WebLogic domain, continue to the next step. If you are installing on an existing
WebLogic domain, skip to step 31.
29. Press Enter.
31. Press Enter.
33. Press Enter.
35. Press Enter.
37. Press Enter.

Prompt Description
Server name Name of the server to run Metadata Manager on. Default is server1.
name.
39. Press Enter.

verify that the installer will install Metadata Manager components in the correct location
and with the options you select.
After you press Enter, the installer copies the Metadata Manager files to the installation
directory. When the file copy process completes, the Configure Domain panel appears.
The PowerCenter domain must be available. Verify that the gateway node for the domain
is available before you continue. If the PowerCenter installer cannot connect to the
PowerCenter domain, you cannot continue with the installation.
Prompt Description
Domain name Name of the PowerCenter domain where the installer creates the Repository
Service and Integration Service for Metadata Manager.
Domain host name Host name of the gateway node for the domain.
Domain port no. Port number for the gateway node for the domain.
Domain user name User name for the administrator account in the domain.
Node name Name of the gateway node for the domain.
41. Press Enter.

The installer creates a Repository Service for the PowerCenter repository for Metadata
Manager. You must create another repository for use with the PowerCenter Client after
installation.

Option Description
1 Create new PowerCenter repository.
43. Press Enter.

Verify that the code page you select is available on the gateway node for the domain you
are joining. If you select an existing repository, the code page must also be compatible
with the repository. If you select an invalid code page, the installation will fail.
Table 9-6 describes the configuration information required for a repository on the
different databases:
Prompt Description
character and cannot contain spaces or the following characters: \/:*?<>“|
Verify that the code page you select is available on the gateway node for the domain. If you
select an existing repository, the code page must also be compatible with the repository. If
you select an invalid code page, the installation will fail.
Password
Connect string Appears for Oracle, SQL Server, and Sybase ASE databases only.
selected database:
- SQL Server: Syntax is SQLServername@dbname, where SQLServername is the name of
the SQL Server instance that contains the dbname database.

Prompt Description
44. Press Enter.

Prompt Description
Create Integration Enter Y to create an Integration Service. In a complete PowerCenter Advanced Edition
Service (Y/N) installation, the installer creates an Integration Service by default.
Manager.
46. Press Enter.

-or-
compatible with Metadata Manager. Otherwise, you cannot log in to Metadata Manager.

If you install Metadata Manager on WebSphere Application Server, the installer
configures WebSphere Application Server security and Metadata Manager authentication
based on your selection and the WebSphere Application Server setup.
Metadata Manager on WebSphere Application Server:
WebSphere Configure
configures repository authentication for Metadata Manager.

The installer configures repository authentication for Metadata Manager.

security and does not configure repository authentication for Metadata
Manager.
For more information about configuring authentication, see “Managing Authentication

for Metadata Manager” in the Metadata Manager Administrator Guide.
48. Press Enter.
-or-
The Metadata Manager Repository Configuration panel appears.
Option Description
1 Create a new Metadata Manager repository.
2 Use existing Metadata Manager repository content.
To use existing Metadata Manager repository content, you may need to upgrade the
repository.
51. Press Enter.

Enter the Metadata Manager configuration information.
Prompt Description

Database URL Database connection string. Use the following syntax:

For more information about the JDBC drivers installed with PowerCenter, see “JDBC
Database User ID Name of the user account to connect to the repository database.

Password
52. Press Enter.

The installer configures Metadata Manager and the application server, configures the
Metadata Manager repository, and starts the application server.
completed successfully. It also shows the configured properties for Metadata Manager
53. Press Enter.

Chapter 10
PowerCenter Client Installation

♦ Overview, 266
♦ Running the Complete Client Installation, 267
♦ Running the Custom Client Installation, 271
♦ Running a Silent Client Installation, 277
265
Overview
When you install the PowerCenter Client, you install the following PowerCenter Client tools
and components:
♦ PowerCenter Client tools. A set of tools you can use to manage the PowerCenter
repository, mappings, and sessions.
If you install the PowerCenter Client without the Metadata Manager Client, you do not
need to log in with an administrator account.
♦ Metadata Manager Client. A set of applications you can use to configure Metadata
Manager and manage metadata.
You must log in with an administrator account when you install the Metadata Manager
Client for the installer to create the Informatica PowerCenter Metadata Manager
Scheduler service.
♦ DataDirect 5.1 ODBC drivers. Drivers designed for PowerCenter to connect the
PowerCenter Client to data sources and targets. The Metadata Manager Client uses
ODBC for connections to the Metadata Manager repository and PowerCenter repository.
♦ Java Runtime Environment. The Java transformation, PowerCenter Connect for JMS, and
PowerCenter Connect for webMethods require the JRE.
Installation Options
You can install the PowerCenter Client on a Windows machine. When you run the
PowerCenter Client installer, you can select one of the following options:
♦ Complete. Installs the PowerCenter Client and Metadata Manager Client applications on
one machine. For more information, see “Running the Complete Client Installation” on
page 267.
♦ Custom. Installs the PowerCenter Client or Metadata Manager Client applications
separately. You can install the clients on different machines. For more information, see
“Running the Custom Client Installation” on page 271.
♦ Silent. Installs the PowerCenter Client in silent mode. For more information, see
“Running a Silent Client Installation” on page 277.
266 Chapter 10: PowerCenter Client Installation

Running the Complete Client Installation
When you run the complete client installation, the installer installs the PowerCenter Client
and Metadata Manager Client on the same machine.
To run the complete client installation:
3. To run the PowerCenter Client installer from the DVD, run the installer from the
following location:
<DVD_Root>\install.exe
-or-
To run the PowerCenter Client installer if you downloaded the installer, run the installer
from the following location:
<download location>\install.exe
4. On the PowerCenter main installation window, select Client.

The Welcome window introduces the PowerCenter Client installation.
5. Click Next.
Running the Complete Client Installation 267

6. To install the complete set of PowerCenter Client applications, select Complete and click
Next.
7. Use the default directory or click Browse to find a directory.

The default directory is C:\Informatica\PowerCenter8.1.1. The installation directory
path must be an absolute path.
8. Click Next.
The installer generates the list of code pages to use with the Metadata Manager Client.

The Metadata Manager Client Configuration window appears.
9. Select the code page for the machine where you are installing the Metadata Manager
Client.
10. For the Integration repository, enter the name of the PowerCenter repository for
Metadata Manager.
11. Click Next.
The Pre-Installation Summary window summarizes the installation information.
Running the Complete Client Installation 269

12. Review the installation information, and click Install to continue.
The installation process displays several windows that show the progress of the
installation and configuration.
The Installation Complete window displays a message about whether the installation
completed successfully. You can select the PowerCenter Client applications to launch
when the installation completes.
13. Click Done.
After the installation completes, the installer creates installation log files. For more
information about the log files created by the PowerCenter Client installer, see “Installer Log
Files” on page 362.
If this is the first time you installed the Metadata Manager Client on this machine, you must
reboot the client machine after the installation completes.

Running the Custom Client Installation
You can install the following PowerCenter Client components on separate machines:
♦ PowerCenter Client. Install the Designer, Repository Manager, Workflow Manager,
Workflow Monitor, and Data Stencil.
♦ Metadata Manager Client. Install the Configuration Console and Custom Metadata
Configurator.
To install a custom version of the PowerCenter Client:
3. To run the PowerCenter Client installer from the DVD, run the installer from the
following location:
<DVD_Root>\install.exe
-or-
To run the PowerCenter Client installer if you downloaded the installer, run the installer
from the following location:
<download location>\install.exe
4. On the PowerCenter main installation window, select Client.

The Welcome window introduces the PowerCenter Client installation.
5. Click Next.
Running the Custom Client Installation 271

The Installation Set window displays the PowerCenter Client installation options.
6. To select the PowerCenter products to install, select Custom and click Next.
The PowerCenter Client Components window appears.

7. To install only the PowerCenter Client, clear the Metadata Manager option.
-or-
To install only the Metadata Manager Client, clear the PowerCenter option.
8. Click Next.

9. Use the default directory or click Browse to find a directory.

The default directory is C:\Informatica\PowerCenter8.1.1. The installation directory
path must be an absolute path.
If you are installing the PowerCenter Client only, skip to step 13. If you are installing the
Metadata Manager Client only, continue to the next step.
10. Click Next.
The installer generates the list of code pages to use with the Metadata Manager Client.

The Metadata Manager Client Configuration window appears.
11. Enter the code page for the machine where you are installing the Metadata Manager
Client.
12. For the Integration repository, enter the name of the PowerCenter repository for
Metadata Manager.
13. Click Next.

The Pre-Installation Summary window displays the component to be installed and
summarizes the installation information.

The installation process displays several windows that show the progress of the
installation and configuration.
The installer displays a message about whether the installation completed successfully. It
also shows the location of the PowerCenter Client.
15. Click Done.
After the PowerCenter Client installation completes, the installer creates installation log files.
For more information about the log files created by the PowerCenter Client installer, see
“Installer Log Files” on page 362.
If this is the first time you installed the Metadata Manager Client on this machine, you must
reboot the client machine after the installation completes.

Running a Silent Client Installation
You can perform a silent installation when you install the PowerCenter Client or Metadata
Manager. When you perform a silent installation, the installer uses information in a
properties file to locate the installation options. You can also perform a silent installation to
install PowerCenter on remote machines on the network. Perform a silent installation to
install the PowerCenter Client on several machines on the network or to standardize the
installation across all machines in the environment.
Complete the following tasks to install the PowerCenter Client in silent mode:
1. Create the installation properties file. Create the installation properties file to configure
the installation options. For more information, see “Step 1. Create the Properties File” on
page 277.
2. Run the installer. Run the installer batch file with the installation properties file. For
more information, see “Step 2. Run the Installer” on page 278.
Step 1. Create the Properties File

You must create the installer properties file before you begin a silent installation. Informatica
provides a sample properties file that includes the PowerCenter Client installation properties.
Use the sample properties file to create an installer properties file and run the silent
installation.
You can get the sample installer.properties from the Client\Disk1\ directory on the
PowerCenter installation DVD or the Client\Disk1\ directory in the location where you
downloaded the PowerCenter Client installer.
The following example shows a sample properties file:
# Installation mode (Silent)
INSTALLER_UI=SILENT
# Installation directory
# Use "\\" to separate directories.
USER_INSTALL_DIR=C:\\Informatica\\PowerCenter8.1.1
# Installation set (Complete/Custom)
CHOSEN_INSTALL_SET=Complete
# PowerCenter Client components (PowerCenter Client/Metadata Manager

Client)
CHOSEN_INSTALL_BUNDLE_LIST=PowerCenter Client,Metadata Manager Client
# Metadata Manager Integration Repository Code Page (MS1252/Latin1)

CODEPAGE=MS1252
# Metadata Manager Integration Repository Name

INTREPONAME=PowerCenter
Running a Silent Client Installation 277

To create the installation properties file:
1. If you are installing from the PowerCenter installation DVD, copy the sample installer
properties file from the DVD to the hard disk.
2. Open the installer properties file in a text editor.
3. Modify the installation properties in the properties file.
Table 10-1 describes the installation properties:
Table 10-1. Silent Installation Properties
Property Name Description
INSTALLER_UI Installation mode for the installer. Use Silent for silent mode.
USER_INSTALL_DIR PowerCenter Client installation directory. Use \\ to separate directories.
CHOSEN_INSTALL_SET Installation set type. You can configure the following options:
- Complete. Install all PowerCenter Client and Metadata Manager Client
tools.
- Custom. Install only components selected in
CHOSEN_INSTALL_BUNDLE_LIST. Use Custom to install PowerCenter
Client components on different machines.
CHOSEN_INSTALL_BUNDLE_LIST PowerCenter Client components to install. Separate multiple components

with commas. You can configure the following options:
- PowerCenter Client
- Metadata Manager Client
CODEPAGE Code page ID for the PowerCenter repository for Metadata Manager.
INTREPONAME Name of the PowerCenter repository for Metadata Manager.
4. Save the properties file on the machine where you install the PowerCenter Client.
Step 2. Run the Installer

After you create the properties file, run the installer to complete the silent installation. When
you run the installer with the properties file, the program uses the information in the file to
complete the installation.
Complete the following steps to run the installer in silent mode:
1. If you install to a remote machine, verify that you can access and create files on the
remote machine.
2. Copy the Client directory and subdirectories to the hard disk on the PowerCenter Client
machine before running the installation.
3. Open a command window.
4. Use the following command to run the silent installation:
<hard disk location>\Client\Disk1\silentinstall -f "<location of
properties file>\installer.properties"

The installer performs the installation and reports errors. It may report errors if you
incorrectly configured the properties file or the installer could not access the installation
directory. You can correct the errors and run the silent installation again. For more
information about the log files created by the PowerCenter Client installer, see “Installer Log
Running a Silent Client Installation 279

Chapter 11
PowerCenter Reports Installation

♦ Overview, 282
♦ Installing PowerCenter Reports in Graphical Mode, 284
♦ Installing PowerCenter Reports in Console Mode, 288
281
Overview
When you install PowerCenter Reports, you install the following reports on a Data Analyzer
instance:
♦ Administrative reports. A set of prepackaged administrative reports that enable system
administrators to track user activities and monitor processes.
♦ PowerCenter Repository Reports. A set of prepackaged dashboards and reports that allow
you to analyze PowerCenter repository metadata.
♦ Data Analyzer Data Profiling reports. Composite, metadata, and summary reports for a
Data Profiling warehouse.
When you install PowerCenter reports, you can use the complete installation to install
PowerCenter Reports on the same instance of Data Analyzer. You can use the custom
installation to install reports on more than one Data Analyzer instance.
Before you install the PowerCenter Reports, you must install Data Analyzer. You can install
PowerCenter Reports and then set up Data Analyzer to run the PowerCenter Reports and
create dashboards and other reports for other data sources.
After you install the Data Analyzer administrative reports, PowerCenter Repository Reports,
or Data Analyzer Data Profiling reports, you must set up data sources and a data connector in
Data Analyzer before you can run the reports.
For more information about setting up the administrative reports, see “Working with the
Data Analyzer Administrative Reports” in the Data Analyzer Administrator Guide. For more
information about setting up the PowerCenter Repository Reports, see “Setting Up the
PowerCenter Repository Reports” on page 339. For more information about setting up Data
Analyzer Data Profiling Reports, see “Setting Up the Data Analyzer Data Profiling Reports”
on page 351.
Installation Modes
You can run the PowerCenter Report installer in the following modes:
♦ Graphical user interface mode. You can install PowerCenter Reports in graphical user
interface mode on UNIX and Windows. For more information, see “Installing
PowerCenter Reports in Graphical Mode” on page 284.
♦ Console mode. You can install PowerCenter Reports in console mode on UNIX. For more
information, see “Installing PowerCenter Reports in Console Mode” on page 288.

mode installer.
282 Chapter 11: PowerCenter Reports Installation

Use the following rules and guidelines when installing PowerCenter Reports with the console
mode installer:
♦ Each panel in the installer prompts for configuration information. Type back at the
installer prompt return to the previous panel. You can only go back from panel to panel.
You cannot go back to a previous prompt from the same panel.
♦ The installer stores previous entries. For example, if you go back two panels, you can
change configuration information and press Enter at each subsequent prompt to accept the
values you already entered.
Overview 283
Installing PowerCenter Reports in Graphical Mode
You can install PowerCenter Reports on Windows or UNIX in graphical mode.
Note: To view the status of the reports installation on UNIX in graphical mode, set the
LAX_DEBUG environment variable to YES before you proceed with the installation. The installer
progress appears in the shell command window during installation.
To install PowerCenter reports in graphical mode:
1. Verify that the Data Analyzer instance where you want to install the reports is running.
installer.
-or-
To start the installer on UNIX, run install_reports.sh at a shell command line from the
DVD root directory or the root directory in the location where you downloaded the
installer.
5. On the PowerCenter main installation window, select Reports.
The Welcome window introduces the PowerCenter Reports installation.
6. Click Next.
The Important Information window displays installation prerequisites.

7. Click Next.
The Installation Set window displays the PowerCenter Reports installation options.
8. To install the complete set of PowerCenter Reports, select Complete. Skip to step 11.
To select the PowerCenter reports to install, select Custom.
9. Click Next.
The PowerCenter Report 8.1.1 Components window appears.
Installing PowerCenter Reports in Graphical Mode 285

10. Select the components you want to install.
11. Click Next.
The Application Details window appears.
12. Enter the URL and administrator name and password for the Data Analyzer instance
where you want to install the reports. Verify the administrator name and password are
correct before you continue. The installer does not verify the values.
The Data Analyzer instance must be running when you install the reports.
13. Enter the type of database that the reports will use as a data source.
Report Type Data Source
PowerCenter Repository Reports PowerCenter repository
Administrative reports Data Analyzer repository
Data Profiling reports Data Profiling warehouse
14. Click Next.


When the installation finishes, the installer displays a message about whether the
installation completed successfully. It also shows details about the Data Analyzer instance
where the PowerCenter reports are installed.
16. Click Done.
After the PowerCenter Reports installation completes, you can view the log file created during
the installation. For more information about the PowerCenter Reports log files, see “Installer
Installing PowerCenter Reports in Graphical Mode 287

Installing PowerCenter Reports in Console Mode
When you install PowerCenter reports, you install the Data Analyzer administrative reports,
PowerCenter Repository Reports, and Data Analyzer Data Profiling reports on the same
instance of Data Analyzer. You can run the complete or custom installation in console mode
on UNIX.
To install PowerCenter reports in console mode:
1. Verify that the Data Analyzer instance where you want to install the reports is running.
3. On a shell command line, run install_reports.sh located in the DVD root directory or the
root directory in the hard disk location.
4. Press Enter.
The Important Information panel displays installation prerequisites.
5. Press Enter.
The Installation Set panel displays the PowerCenter Reports installation options.
6. To install the complete set of PowerCenter Reports, press 1 and press Enter.
Skip to step 9.
7. To select the PowerCenter reports to install, press 2 and press Enter.
The PowerCenter Report Components panel appears.
You can use the custom installation to install PowerCenter reports on separate Data
Analyzer instances.
8. Enter 1 to install only Administrative Reports, enter 2 to install Repository Reports, and
enter 3 to install Data Profiling Reports. Enter 1,2,3 to install all reports.
9. Press Enter.
The Application Details panel appears.
10. Enter the URL and administrator name and password for the Data Analyzer instance
where you want to install the reports. Verify the administrator name and password are
correct before you continue. The installer does not verify the values.
The Data Analyzer instance must be running when you install the reports.

11. Enter the type of database that the reports will use as a data source.
Report Type Data Source
PowerCenter Repository Reports PowerCenter repository
Administrative reports Data Analyzer repository
Data Profiling reports Data Profiling warehouse
12. Press Enter.

The Pre-Installation Summary panel summarizes the installation information.
13. Review the installation information, and press Enter to install.
The installer displays a status bar that shows the progress of the PowerCenter Reports
installation.
When the installation finishes, the installer displays a message about whether the
installation completed successfully. It also shows details about the Data Analyzer instance
where the PowerCenter reports are installed.
14. Press Enter.
After the PowerCenter Reports installation completes, you can view the log file created during
the installation. For more information about the PowerCenter Reports log files, see “Installer
Installing PowerCenter Reports in Console Mode 289

Chapter 12
Documentation Installation

♦ Overview, 292
♦ Installing PowerCenter Documentation, 293
♦ Viewing PowerCenter Documentation, 295
♦ Updating PowerCenter Online Help, 296
♦ Installing the PowerCenter Web-Based HTML Help, 297
291
Overview
Informatica provides the PowerCenter Documentation DVD to install and view PowerCenter
documentation in PDF format and install online help files for the PowerCenter Client and
Administration Console.
The PowerCenter Documentation DVD includes the following components:
♦ PowerCenter documentation. PowerCenter documentation in PDF format. You can view
the documentation directly from the DVD or you can install the documentation using the
DVD. It also includes the Informatica Documentation Start Page which provides an easy
way to select and view PowerCenter documents. For more information about installing the
PowerCenter documentation, see “Installing PowerCenter Documentation” on page 293.
For more information about viewing the PowerCenter documentation, see “Viewing
PowerCenter Documentation” on page 295.
♦ Online help files. Context-sensitive online help files for the PowerCenter Client and the
PowerCenter Administration Console. The PowerCenter installer installs the online help
files when you install PowerCenter Standard or Advanced Edition. Install updated versions
of the online help files from the Documentation DVD. For more information, see
“Updating PowerCenter Online Help” on page 296.
♦ PowerCenter Web-based HTML documentation. PowerCenter documentation in HTML
format. You can install the PowerCenter documentation web-based help on a non-
Windows machine. Copy and unzip the pc_web.war file to an accessible directory. For
more information, see “Installing the PowerCenter Web-Based HTML Help” on page 297.
Installing from the Hard Disk

If you want to copy the PowerCenter documentation installation files from the DVD to the
hard disk and install from the hard disk, copy the /Disk1 folder (including all files and
subdirectories) from the PowerCenter documentation installation DVD to the hard disk. The
/Disk1 folder contains all the installation files required for the documentation installation.
292 Chapter 12: Documentation Installation

Installing PowerCenter Documentation
PowerCenter provides a separate DVD for PowerCenter documentation.
To install PowerCenter documentation:
1. On the PowerCenter Documentation DVD, locate and run the documentation

installation file:
\Disk1\install.bat
The Welcome window introduces the PowerCenter Documentation installation.

Note: When you insert the PowerCenter Documentation DVD into the DVD drive, the
Informatica Documentation Start Page appears. Click Exit to close the Documentation
Start Page. Run the PowerCenter documentation installer.
2. Click Next.
3. Enter the full path of the folder where you want to install the PowerCenter
documentation.
The PowerCenter documentation installer displays the following default directory:
C:\Informatica\PowerCenter8.1.1

4. Click Next.
Installing PowerCenter Documentation 293

The Pre-Installation Summary window appears.
5. Verify the installation information and click Install.

When the documentation installation completes, the Post-Installation Summary window
indicates whether the installation completed successfully.
6. Click Done.
The PowerCenter documentation installer creates a documentation shortcut in the
Informatica PowerCenter 8.1.1 program group.

Viewing PowerCenter Documentation
You can use Informatica Documentation Start Page to locate and view a document.
To view PowerCenter documentation:
1. To start PowerCenter documentation, complete one of the following tasks:

♦ From the Start menu, choose Programs > Informatica PowerCenter 8.1.1 >
Documentation > Start Documentation.
♦ Insert the PowerCenter Documentation DVD into the DVD drive and run start.bat in
the root directory.
The Informatica Documentation Start Page appears.
2. Click the type of documentation you want to view.
Navigate through the selections to locate the document you want to view.
3. Click the name of the document to view the document.
Tip: If you want to go back to the Informatica Documentation Start Page while viewing a
document, click the last selection in the document bookmarks, Return to Start.
Viewing PowerCenter Documentation 295

Updating PowerCenter Online Help
The context-sensitive online help on the PowerCenter Documentation DVD includes the
following help files:
♦ PowerCenter Client. Online help files for the PowerCenter Designer, Repository Manager,
Workflow Manager, and Workflow Monitor. For more information about copying the
Help files, see “Updating PowerCenter Online Help” on page 296.
♦ PowerCenter Administration Console. HTML help files for the Administration Console.
For more information, see “Updating PowerCenter Online Help” on page 296.
Updating PowerCenter Client Help

The PowerCenter Documentation DVD contains the updated PowerCenter Client help files
in CHM format. You can install the files by copying them from the Documentation DVD to
the location where you install the PowerCenter Client.
To install the PowerCenter Client help files:
Copy the CHM files from the Help_Files directory on the Documentation DVD to the
client\bin directory in the PowerCenter Client installation directory.
When you view online help, the client tool displays the most recent version.
Updating Administration Console Help

The PowerCenter Documentation DVD contains the updated online help for the
Administration Console in WAR format. When you install Administration Console help, you
copy the WAR file from the Documentation DVD to the gateway nodes in the PowerCenter
domain and restart the master gateway node for the domain.
To install the Administration Console online help:
1. Locate the WAR file for the Administration Console in the following location:
<DVD Root>\Help_Files\adminhelp.war
2. Copy the WAR file to the server\tomcat\webapps directory on each gateway node in the
domain.
3. Stop and restart Informatica Services on the master gateway node for the domain. For
more information, see “Starting and Stopping Informatica Services” on page 529.
4. Log in to the Administration Console and click Help in the main window.
Each node that serves as a gateway node for a domain uses a local copy of the HTML help for
the Administration Console. To view the online help on a gateway node, you must copy the
online help file to that node.

Installing the PowerCenter Web-Based HTML Help
The PowerCenter Documentation DVD contains PowerCenter HTML help that you can
view on a non-Windows machine. The HTML files are compressed in a web archive (WAR)
file. When you install the PowerCenter web-based help, you copy the WAR file from the
Documentation DVD to any directory that you want. The PowerCenter web-based HTML
help includes a table of contents and an index. The web-based help not provide context-
sensitive help for the PowerCenter Client.
To install the PowerCenter web-based HTML help:
1. Locate the WAR file for PowerCenter web-based help in the following location:
<DVD Root>\Help_Files\pc_web.war
2. Copy the WAR file to any directory that you want to use.
3. Unzip the WAR file.
If you install the WAR file on a Windows machine, you can use WinZip to unzip the
files.
-or-
You can use the following Java command:
jar xf pc_web.war
4. To view the table of contents and index, double-click the index.html file.
Installing the PowerCenter Web-Based HTML Help 297

Chapter 13
PowerCenter Utilities Installation

♦ Overview, 300
♦ PowerCenter Command Line Programs and Utilities, 301
♦ Data Analyzer Utilities, 302
♦ Metadata Manager Utilities, 311
299
Overview
Informatica includes PowerCenter utilities with the PowerCenter product. PowerCenter
utilities are customer support tools and command line programs and utilities for
PowerCenter, Data Analyzer, and Metadata Manager. You can install and run the programs
and utilities on any machine without installing PowerCenter.
The PowerCenter utilities are included in a ZIP or TAR file on the root of the PowerCenter
installation DVD or in the root directory of the location where you download the installer. To
install the utilities, unzip or untar and configure the utilities on the machine where you want
to run them.
The PowerCenter utilities include the following components:
♦ PowerCenter command line programs and utilities. Command line programs and utilities
for use with PowerCenter Services and the PowerCenter Client. For more information
about the included programs and utilities, see “PowerCenter Command Line Programs
and Utilities” on page 301.
♦ Data Analyzer utilities. Utilities for use with the Data Analyzer application. For more
information about installing and configuring the Data Analyzer utilities, see “Data
Analyzer Utilities” on page 302.
♦ Metadata Manager utilities. Utilities for use with the Metadata Manager application. For
more information about installing and configuring the Metadata Manager utilities, see
“Metadata Manager Utilities” on page 311.
300 Chapter 13: PowerCenter Utilities Installation

PowerCenter Command Line Programs and Utilities
To install the PowerCenter command line programs and utilities, copy the PowerCenter
utilities to the machine where you want to run them. After you unzip or untar the utilities,
the programs and utilities are located in the server\bin directory in following directory:
\Utilities\PC811_Utilities\PowerCenter811\
Table 13-1 describes the PowerCenter command line programs and utilities:
Table 13-1. PowerCenter Command Line Programs and Utilities
Program or Utility Name Description
infacmd Administer PowerCenter domains and services. Use infacmd to administer application
services and processes, the PowerCenter domain, licenses, log events, and grids. For
more information about infacmd, see “infacmd Command Reference” in the Command
Line Reference.
pmcmd Manage workflows. Use pmcmd to start, stop, schedule, and monitor workflows. For
more information about pmcmd, see “pmcmd Command Reference” in the Command
Line Reference.
pmpasswd Encrypt passwords to use with pmcmd and pmrep environment variables. For more
information about pmpasswd, see “Configuring Environment Variables” in the
Command Line Reference.
pmrep Performs repository administration tasks. Use pmrep to list repository objects, create
and edit groups, and restore and delete repositories. For more information about
pmrep, see “pmrep Command Reference” in the Command Line Reference.
pmserverexportreg Export the PowerCenter Server configuration information from the Windows registry
and create a PowerCenter Server configuration file. Use pmserverexportreg to create
configuration files for use with the Upgrade Wizard in the PowerCenter Administration
Console. For more information about pmserverexportreg, see “Backing Up and
Copying Configuration Files” on page 89.
Rules and Guidelines

Use the following rules and guidelines when you run the PowerCenter command line
programs and utilities:
♦ You must preserve the directory structure of the PowerCenter811 directory to run infacmd
and pmserverexportreg. These programs require the java directory.
♦ On UNIX, to run pmrep, pmcmd, and pmpasswd, you must copy domains.infa for the
existing PowerCenter installation directory to the utilities directory, and set
INFA_HOME, the PATH environment variable, and library path environment variable to
the location of the PowerCenter utilities.
PowerCenter Command Line Programs and Utilities 301

Data Analyzer Utilities
To install the Data Analyzer utilities, copy the utilities to the machine where you want to run
them. After you unzip or untar the utilities, the programs and utilities are located in the
following directory:
\Utilities\PC811_Utilities\DataAnalyzer811\
You must configure the utilities before you run them. You configure the variables required by
the utilities in the utility script files. To configure the script files, open the files in a text editor
and modify the variable values required by the script.
Table 13-2 describes the Data Analyzer utilities included in the DataAnalyzer811 directory:
Table 13-2. Data Analyzer Utilities
Utility Name Description
EAR Repackager Utility Unpacks and repackages the customizable files in the Data Analyzer EAR file. For
more information, see “Ear Repackager Utility” on page 302.
Import Export Utility Imports or exports Data Analyzer repository objects. For more information, see
“Import Export Utility” on page 303.
License Update Utility Updates an expired license in a Data Analyzer EAR file. For more information, see
“License Update Utility” on page 303.
PowerCenter Integration Utility Notifies Data Analyzer when a PowerCenter session completes. For more
information, see “PowerCenter Integration Utility” on page 304.
Repository Backup Utility Backs up a Data Analyzer repository to a repository backup file and recovers a
repository from a repository backup file. For more information, see “Repository
Backup Utility” on page 309.
Data Analyzer Repository Upgrades a repository from a previous version of Data Analyzer. For more
Upgrade Utility information, see “Data Analyzer Repository Upgrade Utility” on page 309.
Update System Accounts Updates the system accounts in the Data Analyzer repository. For more information,
see “Update System Accounts Utility” on page 309.
Ear Repackager Utility

You can use the EAR Repackager utility to unpack and repack customizable files in a Data
Analyzer EAR file. To configure the EAR Repackager utility, you must modify the variables in
run.bat or run.sh, located in the following directory in the Data Analyzer utilities directory:
\DataAnalyzer811\ear_repackagerutil

Table 13-3 describes the variables you must configure to run the EAR Repackager utility:
Table 13-3. EAR Repackager Utility Variables
Variable Name Description
ANT_HOME Location of the ANT Java build program used by the EAR Repackager Utility.
The ANT Java build program is located in the following directory:
<PowerCenterUtilityDir>/DataAnalyzer811/
ear_repackagerutil/ant161
JAVA_HOME Location of the Java Runtime Environment. By default, the installer installs the
JRE in the following directory:
PowerCenterInstallationDir>/java
IPA_INSTANCE_NAME Name for the Data Analyzer instance on the application server. For Data
Analyzer, the value is ias.
DEFAULT_IPA_EAR_FILE_NAME Name of the Data Analyzer EAR file. For Data Analyzer, the value is ias.ear.
DEFAULT_EAR_FOLDER_NAME Folder where the Data Analyzer EAR file is located. The EAR file is located in
the following directories:
- <WebLogicInstallationDir>/user_projects/domains/<domain
name>/applications
- <WebSphereInstallationDir>/DeploymentManager/
installableApps
- <JBossInstallationDir>/server/informatica/deploy
For more information about the EAR Repackager utility, see “Accessing the Data Analyzer
EAR file” in the Data Analyzer Administrator Guide.
Import Export Utility

Imports or exports Data Analyzer objects. To configure the Import Export utility, you must
modify the variables in ImportExport.bat or ImportExport.sh, located in the following
directory in the Data Analyzer utilities directory:
\DataAnalyzer811\import-exportutil
Table 13-4 describes the variable you must configure to run the Import Export utility:
Table 13-4. Import Export Utility Variable
JAVA_HOME Location of the Java Runtime Environment. By default, the PowerCenter installer
installs the JRE in the following directory:
<PowerCenterInstallationDir>/java
For more information about using the Import Export utility, see “Using the Import Export
Utility” in the Data Analyzer Administrator Guide.
License Update Utility

You can use the License Update utility to update an expired license in a Data Analyzer EAR
file. To configure the License Update utility, you must modify the variables in
Data Analyzer Utilities 303

updateLicense.bat or updateLicense.sh, located in the following directory in the Data
Analyzer utilities directory:
\DataAnalyzer811\license
For more information about using the License Update utility, see “Updating a Data Analyzer
or Metadata Manager License” on page 337.
Table 13-5 describes the variables you must configure to run the License Update utility:
Table 13-5. License Update Utility Variables
EAR_LOCATION Application server directory where the EAR file for the Data Analyzer application is located.
The EAR file is located in the following directories:
- <WebLogicInstallationDir>/user_projects/domains/<domain name>/
applications
- <WebSphereInstallationDir>/DeploymentManager/installableApps
EAR_FILE Name of the Data Analyzer EAR file. For Data Analyzer, the EAR file name is ias.ear.
LICENSE_LOCATION Location of the Data Analyzer license file to update the expired Data Analyzer license file.
LICENSE_FILE Name of the license file you use to update the expired Data Analyzer license file.
JAVA_HOME Location of the Java Runtime Environment. By default, the PowerCenter installer installs the
PowerCenter Integration Utility

Data Analyzer uses the PowerCenter Integration utility to notify Data Analyzer when a
PowerCenter session completes. The PowerCenter Integration utility is located in the
following directory in the Data Analyzer utilities directory:
\DataAnalyzer811\notifyias
You configure the PowerCenter Integration utility depending on the application server where
you run Data Analyzer. You can run Data Analyzer on the following application servers:
♦ BEA Weblogic Server
Before you configure the PowerCenter Integration utility for Data Analyzer, you must create
an event-based schedule in Data Analyzer. After you configure the schedule, you can
configure the PowerCenter Integration utility to notify Data Analyzer when a PowerCenter
session completes, based on that schedule.
For more information about the PowerCenter Integration Utility and event-based schedules
in Data Analyzer, see “Managing Event-Based Schedules” in the Data Analyzer Administrator
Guide.

To configure the PowerCenter Integration utility for Data Analyzer running on JBoss
Application Server, complete the following steps:
1. Copy jbossall-client.jar from the <JBoss installation directory>\client directory to the
DataAnalyzer811\notifyias\notifyias_JBoss directory.
2. Rename the notifyias_JBoss directory to notifyias.
3. Open notifyias.properties in a text editor and change the values for the following
variables:
logfile.location Location of the notifyias log file for JBoss Application Server. By default, the file is
named notifyias.log and is located in the following directory:
<JBossInstallationDir>/DataAnalyzer/notifyias
java.naming.provider.url Host name and JMS Server port number for the application server instance. For
example, for JBoss Application Server running on host calvin with the default value for
the JMS Server port, enter the following value:
jnp://calvin:1099
4. Open notifyias.bat or notifyias.sh in a text editor and change the values for the following
variables:
NOTIFYIAS_HOME Directory for the PowerCenter Integration Utility. Use the directory where the
notifyias.bat or notifyias.sh file you modify is located.
CLASSPATH Location of jbossall-client.jar in JBoss Application Server installation directory. For

example, enter the following value:
<JBossInstallationDir>/server/client/jbossall-client.jar
5. Enter one of the following commands at a command prompt or shell command line,
where <event name> is the name of the event-based schedule you created in Data
Analyzer:
On UNIX, enter the following command:
sh notifyias.sh <event name>
-or-
On Windows, enter the following command:
notifyias <event name>

WebLogic Server
To configure the PowerCenter Integration utility for Data Analyzer running on WebLogic
Server, complete the following steps:
1. Copy weblogic.jar from the <Weblogic installation directory>\weblogic81\server\lib
directory to the notifyias_Weblogic directory.
2. Rename the notifyias_Weblogic directory to notifyias.
3. Open notifyias.properties in a text editor and change the values for the variables:
logfile.location Location of the notifyias log file for WebLogic Server. By default, the file is named
notifyias.log and is located in the following directory:
<PowerCenterInstallationDir>/DataAnalyzer/notifyias
example, for WebLogic Server running on host calvin with the default value for the
JMS Server port, enter the following value:
t3://calvin:7001
variables:
<PowerCenterInstallationDir>\java
JAVA_CLASS_PATH Replace the value WEBLOGIC_HOME with the WebLogic Server home directory. For
example, enter the following value:
C:\bea\weblogic81
URL URL for the WebLogic Server instance. For example, for a WebLogic Server running
on host calvin, enter the following value:
t3://calvin:7001
5. Open updateNotifyIASEar.bat or updateNotifyIASEar.sh in a text editor and change the

values for the following variables:

6. Add changeJndiNames.jar and PowerCenterIntegration.jar, located in the notifyias
directory, to the system classpath.
Analyzer.
-or-
WebSphere Application Server

To configure the PowerCenter Integration utility for Data Analyzer running on WebSphere
Application Server, complete the following steps:
1. Rename the notifyias_Websphere directory to notifyias.
2. Open notifyias.properties in a text editor and change the values for the following
variables:
logfile.location Location of the notifyias log file for WebSphere Application Server. By default, the file
is named notifyias.log and is located in the following directory:
<PowerCenterInstallationDir>/DataAnalyzer/notifyias
example, for WebSphere Application Server running on host calvin with the default
value for the JMS Server port, enter the following value:
iiop://calvin:2809
3. Open setupClient.bat or setupClient.sh, located in the notifyias\bin directory, in a text

editor and change the values for the following variables:
COMPUTERNAME Host name of the machine where WebSphere Application Server runs.
DEFAULTSERVERNAME Fully qualified host name of the machine where WebSphere Application Server
runs. For example, <machine name>.<domain name>.com
SERVERPORTNUMBER Port number for the WebSphere Application Server.
WAS_HOME Directory where the notifyias utility is located.
JAVA_JDK Java Development Kit (JDK) directory location for WebSphere Application Server.
By default, the JDK is located in the following directory locations:
- <WebSphere installation directory>\DeploymentManager\java
- <WebSphere installation directory>\AppServer\java

variables:
BOOTSTRAP_HOST Host name of the machine where WebSphere Application Server runs.
BOOTSTRAP_PORT Port number for the WebSphere Application Server.
5. Open updateNotifyIASEar.bat or updateNotifyIASEar.sh, located in the notifyias\bin

directory, in a text editor and change the values for the following variables:
<PowerCenterInstallationDir>\java
6. Open sas.client.props, located in the notifyias\properties directory, in a text editor and

change the values for the following variables:
com.ibm.ssl.keyStore Location of DummyClientKeyFile.jks. Set the variable to the following value:

\DataAnalyzer811\notifyias\etc\DummyClientKeyFile.jks
com.ibm.ssl.trustStore Location of DummyClientTrustFile.jks. Set the variable to the following value:

\DataAnalyzer811\notifyias\etc\DummyClientTrustFile.jks
7. Add changeJndiNames.jar and PowerCenterIntegration.jar in the notifyias directory to

the system classpath.
Analyzer.
-or-

Repository Backup Utility
You can use the Repository Backup utility to back up a Data Analyzer repository to a
repository backup file and recover a repository from a repository backup file. To configure the
Repository Backup utility, you must configure the variables in backup.bat or backup.sh and
backupCmdLine.bat or backupCmdLine.sh, located in the following directory in the Data
Analyzer utilities directory:
\DataAnalyzer811\backuputil
Table 13-6 describes the variable you must configure to run the Repository Backup utility:
Table 13-6. Repository Backup Utility Variable
JAVA_HOME Location of the Java Runtime Environment. By default, the PowerCenter installer installs the JRE in
the following directory:
For more information about the Repository Backup Utility, see “Using the Command Line
Repository Backup Utility” in the Data Analyzer Administrator Guide.
Data Analyzer Repository Upgrade Utility

You can use the Data Analyzer Repository Upgrade utility to upgrade the Data Analyzer
repository to the latest version. To configure the Repository Upgrade utility, you must
configure the variables in upgrade.bat or upgrade.sh, located in the following directory in the
Data Analyzer utilities directory:
\DataAnalyzer811\upgradeutil
Table 13-7 describes the variables you must configure to run the Repository Upgrade Utility:
Table 13-7. Repository Upgrade Utility Variables
UTILS_DIR Directory where the Data Analyzer utilities are located.
DOMAIN_PATH Domain path for the application server instance. The domain path depends on the application
server where Data Analyzer runs.
For more information about the Repository Upgrade utility, see “Run the Repository Upgrade
Utility” on page 433.
Update System Accounts Utility

You can use the Update System Accounts utility to change the password for the system
administrator account. To configure the Update System Accounts utility, you must configure

the variables in UpdateSystemAccounts.bat or UpdateSystemAccounts.sh, located in the
following directory in the Data Analyzer utilities directory:
\DataAnalyzer811\adminutil\<application server>
Table 13-8 describes the variables you must configure to run the Update System Accounts
Utility:
Table 13-8. Update System Accounts Variables
DBDRIVER * JDBC driver for the Data Analyzer repository database.
URL * URL for the Data Analyzer repository database,.
DBUSER Administrator user name for the Data Analyzer repository database.
DBPASSWORD Password for the database administrator.
UTILITY_DIR Directory where the Data Analyzer utilities are located.
* For more information about the JDBC drivers and URL for the Data Analyzer repository database, see “JDBC Drivers” on page 553.
For more information about the Update System Accounts utility, see “Working with System
User Accounts” in the Data Analyzer Administrator Guide.

Metadata Manager Utilities
To install the Metadata Manager utilities, copy the utilities to the machine where you want to
run them. After you unzip or untar the utilities, the programs and utilities are located in the
\Utilities\PC811_Utilities\MetadataManager811\
You must configure the utilities before you run them. You configure the variables required by
the utilities in the utility script files. To configure the script files, open the files in a text editor
and modify the variables values required by the script.
Table 13-9 describes the Metadata Manager utilities included in the MetadataManager811
directory:
Table 13-9. Metadata Manager Utilities
Utility Name Description
EAR Repackager Utility Unpacks and repackages the customizable files in the Metadata Manager EAR file.
For more information, see “Ear Repackager Utility” on page 311.
License Update Utility Updates an expired license in a Metadata Manager EAR file. For more information,
see “License Update Utility” on page 312.
Repository Backup Utility Backs up a Metadata Manager repository to a repository backup file and recovers a
repository from a repository backup file. For more information, see “Repository
Backup Utility” on page 313.
Update System Accounts Updates the system accounts in the Metadata Manager repository. For more
information, see “Update System Accounts Utility” on page 313.
Metadata Manager Repository Upgrades a repository from a previous version of Metadata Manager. For more
Upgrade Utility information, see “Upgrading Metadata Manager” on page 441.
Ear Repackager Utility

You can use the EAR Repackager utility to unpack and repack customizable files in a
Metadata Manager EAR file. To configure the EAR Repackager utility, you must configure
the variables in run.bat or run.sh, located in the following directory in the Metadata Manager
utilities directory:
\MetadataManager811\ear_repackagerutil
Metadata Manager Utilities 311

Table 13-10 describes the variables you must configure to run the EAR Repackager utility:
Table 13-10. EAR Repackager Utility Variables
ANT_HOME Location of the ANT Java build program used by the EAR Repackager Utility.
The ANT Java build program is located in the following directory
<PowerCenterUtilityDir>/MetadataManager811/
ear_repackagerutil/ant161
JAVA_HOME Location of the Java Runtime Environment. By default, the installer installs the
IPA_INSTANCE_NAME Name for the Metadata Manager instance on the application server. For
Metadata Manager, the value is imm.
DEFAULT_IPA_EAR_FILE_NAME Name of the Metadata Manager EAR file. For Metadata Manager, the value is
imm.ear.
DEFAULT_EAR_FOLDER_NAME Folder where the Metadata ManagerEAR file is located. The EAR file is located
in the following directories:
- <WebLogicInstallationDir>/user_projects/domains/<domain
name>/applications
- <WebSphereInstallationDir>/DeploymentManager/
installableApps
For more information about the EAR Repackager utility, see “Metadata Manager Utilities” in
the Metadata Manager Administrator Guide.
License Update Utility

You can use the License Update utility to update an expired license in a Metadata Manager
EAR file. To configure the License Update utility, you must configure the variables in
updateLicense.bat or updateLicense.sh, located in the following directory in the Metadata
Manager utilities directory:
\MetadataManager811\license
Table 13-11 describes the variables you must configure to run the License Update utility:
EAR_LOCATION Application server directory where the EAR file for the Metadata Manager application is
located. The EAR file is located in the following directories:
- <WebLogicInstallationDir>/user_projects/domains/<domain name>/
applications
- <WebSphereInstallationDir>/DeploymentManager/installableApps
EAR_FILE Name of the Metadata Manager EAR file. For Metadata Manager, the EAR file name is
imm.ear.

LICENSE_LOCATION Location of the Metadata Manager license file you want to use to update the expired
Metadata Manager license file.
LICENSE_FILE Name of the license file you use to update the expired Metadata Manager license file.
JAVA_HOME Location of the Java Runtime Environment. By default, the PowerCenter installer installs the
For more information about using the License Update utility, see “Updating a Data Analyzer
or Metadata Manager License” on page 337.
Repository Backup Utility

You can use the Repository Backup utility to back up a Metadata Manager repository to a
repository backup file and recover a repository from a repository backup file. To configure the
Repository Backup utility, you must configure the variables in backup.bat or backup.sh and
backupCmdLine.bat or backupCmdLine.sh, located in the following directory in the
Metadata Manager utilities directory:
\MetadataManager811\backuputil
Table 13-12 describes the variables you must configure to run the Repository Backup utility:
Table 13-12. Repository Backup Utility Variables
JAR_DIR Location of backup.bat or backup.sh.
For more information about the Repository Backup Utility, see “Metadata Manager Utilities”
in the Metadata Manager Administrator Guide.
Update System Accounts Utility

You can use the Update System Accounts utility to change the password for the system
administrator account. To configure the Update System Accounts utility, you must configure
the variables in UpdateSystemAccounts.bat or UpdateSystemAccounts.sh, located in the
following directory in the Metadata Manager utilities directory:
\MetadataManager811\adminutil\<application server>
For more information about the Update System Accounts utility, see “Metadata Manager
Utilities” in the Metadata Manager Administrator Guide.
Metadata Manager Utilities 313

Table 13-13 describes the variables you must configure to run the Update System Accounts
Utility:
Table 13-13. Update System Accounts Variables
DBDRIVER * JDBC driver for the Metadata Manager repository database.
URL * URL for the Metadata Manager repository database.
DBUSER Administrator user name for the Metadata Manager repository database.
DBPASSWORD Password for the database administrator.
UTILITY_DIR Directory where the Metadata Manager utilities are located.
* For more information about the JDBC drivers and URL for the Metadata Manager repository database, see “JDBC Drivers” on page 553.

Chapter 14
Informatica Development
Platform Installation
♦ Overview, 316
♦ Installing the Informatica Development Platform, 317
♦ Installation Directories, 321
315
Overview
The Informatica Development Platform provides the following PowerCenter application
programming interfaces (API) and software development kits (SDK):
♦ Custom Function SDK. Provides an interface that allows you to develop functions written
in C and integrate them into PowerCenter. For more information about the Custom
Function SDK, see “Creating Custom Functions” in the PowerCenter Transformation
Language Reference.
♦ Load Manager API (C). Provides a set of interfaces that allows you to write a C
application that accesses the Integration Service and issues commands related to
Integration Service administration, workflow, task, reporting, and log requests.
♦ Load Manager API (Java). Provides a set of interfaces that allows you to write a Java
application to issue commands to the Integration Service to administer the Integration
Service and manage workflow, task, reporting, and log requests. For more information
about the Java Load Manager API, see Getting Started with the Java Load Manager SDK.
♦ Mapping API (Java). Provides a set of interfaces that allows you to generate PowerCenter
XML documents containing mappings, sessions, and workflows.
♦ Metadata Exchange SDK. Provides a set of COM-based APIs for exchanging metadata
with the PowerCenter repository. For more information about the Metadata Exchange
SDK, see the PowerCenter Metadata Exchange SDK Guide.
♦ PowerCenter Connect SDK. Provides a set of interfaces that allows you to create plug-ins
for PowerCenter to extend its functionality. For more information about the PowerCenter
Connect SDK, see the PowerCenter Connect SDK Developer Guide.
♦ Session Log API. Provides an interface that allows you write your own modules to handle
the session log output for PowerCenter.
♦ Transformation SDK. Provides an interface that allows you to create custom
transformations that call procedures outside of PowerCenter. For more information about
the Transformation SDK, see “Custom Transformation” in the Transformation Guide.
316 Chapter 14: Informatica Development Platform Installation

Installing the Informatica Development Platform
When you run the Informatica Development Platform installer, you can install all the SDKs
or install only the SDKs you want to use. To install all the SDKs in one process, select the
Complete installation option. To install specific SDKs, select the Custom installation option.
You can install the Informatica Development Platform on UNIX or Windows.
To install the PowerCenter SDKs:
installer.
-or-
The Welcome window introduces the Informatica Development Platform installation.
2. Click Next.
The License Agreement window displays license agreement for the use of the SDKs. You
must accept the license agreement to be able to continue.
3. Select I accept the terms of the license agreement option and click Next.
The Installation Set window displays the installation options.
4. To install the complete set of PowerCenter SDK, select Complete.
Installing the Informatica Development Platform 317

Skip to step 7.
To select the PowerCenter SDKs to install, select Custom.
5. Click Next.
The Custom Install Set window displays the list of PowerCenter SDK and APIs available
with the Informatica Development Platform.
6. Select the SDKs and APIs you want to install.

7. Click Next.

8. On the Choose Installation Folder window, select enter the folder where you want to
install the PowerCenter SDKs.
9. Click Next.
Installing the Informatica Development Platform 319

11. When the installation completes, the installer displays a message about whether the
installation completed successfully.
12. Click Done.

After the PowerCenter SDK installation completes, you can view the log file created during
the installation. For more information about the PowerCenter log files, see “Installer Log

Installation Directories
The Informatica Development Platform installer installs the PowerCenter SDKs in the
directory you provide. The default Informatica Development Platform installation directory
is c:/InformaticaDeveloperPlatform8.1.1.
The Informatica Development Platform installer installs the APIs and SDKs in the following
subdirectories:
Name Directory
Custom Function SDK <SDKInstallationDir>/EP_AEP_CT
Load Manager API (C) <SDKInstallationDir>/LoadManager_API
Load Manager API (Java) <SDKInstallationDir>/Java_LM_API
Mapping API (Java) <SDKInstallationDir>/Mapping_SDK
Metadata Exchange SDK <SDKInstallationDir>/Metadata_Exchange_SDK
PowerCenter Connect SDK <SDKInstallationDir>/PowerCenter_Connect_SDK
Session Log API <SDKInstallationDir>/SessionLog_API
Transformation SDK <SDKInstallationDir>/Expression_SDK
Installation Directories 321

Chapter 15
After You Install
This chapter contains the following topics:

♦ Overview, 324
♦ Configuring Informatica Services, 325
♦ Configuring Application Services, 328
♦ Configuring the Metadata Manager Scheduler Service, 330
♦ Creating a Data Profiling Warehouse, 331
♦ Configuring the PowerCenter Integration Utility for WebSphere, 334
♦ Updating a Data Analyzer or Metadata Manager License, 337
♦ Configuring Microsoft SQL Server for a Data Analyzer Repository, 338
♦ Setting Up the PowerCenter Repository Reports, 339
♦ Setting Up the Data Analyzer Data Profiling Reports, 351
♦ Configuring INFA_HOME, 357
323
Overview
After you install PowerCenter, you must configure PowerCenter components. The tasks you
must complete depend on he PowerCenter components you install.
Configure the following PowerCenter components after you install PowerCenter:
♦ Informatica Services. Informatica runs as a service on Windows. You can configure the
service to start when the operating system starts, configure the service to automatically
restart if the service fails, and configure the user account that logs on to the service. For
more information, see “Configuring Informatica Services” on page 325.
♦ Application services. Configure application service properties if the installer could not
create or enable a Repository Service during installation or you want to configure
additional properties. For more information about configuring application service during
or after installation, see “Configuring Application Services” on page 328.
♦ Metadata Manager Scheduler service. Configure the Metadata Manager Scheduler service
properties if you want to run the Business Objects XConnect on a schedule. For more
information about configuring the Metadata Manager Scheduler service, see “Configuring
the Metadata Manager Scheduler Service” on page 330.
♦ Data Profiling. Create the Data Profiling warehouse. For more information, see “Creating
a Data Profiling Warehouse” on page 331.
♦ PowerCenter Integration Utility. If you run Data Analyzer on IBM WebSphere
Application Server, you must configure the PowerCenter Integration Utility client resource
(notifyias.ear). For more information, see “Configuring the PowerCenter Integration
Utility for WebSphere” on page 334.
♦ Data Analyzer and Metadata Manager licenses. You can use the License Update utility to
update an expired Data Analyzer or Metadata Manager license. For more information
about updating a license, see “Updating a Data Analyzer or Metadata Manager License” on
page 337.
♦ Microsoft SQL Server for a Data Analyzer repository. If you use a Microsoft SQL Server
database for the Data Analyzer repository, you must configure JDBC distributed
transaction support in the repository database. For more information, see “Configuring
Microsoft SQL Server for a Data Analyzer Repository” on page 338.
♦ PowerCenter Repository Reports. If you installed PowerCenter Repository Reports, you
can set up the reports in Data Analyzer. For more information, see “Setting Up the
PowerCenter Repository Reports” on page 339.
♦ Data Profiling reports. If you installed Data Analyzer Data Profiling reports, you can set
up the reports in Data Analyzer. For more information, see “Setting Up the Data Analyzer
Data Profiling Reports” on page 351.
♦ INFA_HOME. Configure INFA_HOME to the location of the PowerCenter Services
installation directory or the directory where the installed PowerCenter Services files are
located. For more information, see “Configuring INFA_HOME” on page 357.
324 Chapter 15: After You Install

Configuring Informatica Services
PowerCenter Component:
The installer installs and starts Informatica Services. Informatica Services starts the Service
Manager for a node. The Service Manager runs within Informatica Services. Informatica
Services runs as a service on Windows and as a daemon on UNIX. The Service Manager runs
application services on a node.
You can configure the Informatica Services service on Windows. You can configure the service
behavior when the operating system starts or when the service fails, and configure the user
account that logs on to the service. For more information about starting and Stopping
Informatica Services, see “Starting and Stopping Informatica Services” on page 529.
The PowerCenter installer can install the Informatica Services service on the Local System
account on Windows. If you store files on a network drive, use a system account instead of the
Local System account to run Informatica Services. If you want to use the Local System
account, make sure the user starting Informatica Services has access to the network location.
If you configure shared storage on a network drive to store files used by the domain or the
application services that run on the domain, the user account that runs Informatica Services
must have access to the shared location. If the user account used to start Informatica Services
cannot access the shared storage location, service processes on the node fail or the node or
domain will not start.
Note: If you configure a system user account, the user account must have the Act as operating
system permission. For more information, see the Windows documentation.
To configure the Informatica Services service:
1. From the Start Menu, click Administrative Tools > Services.

2. Double-click Informatica Services.
Configuring Informatica Services 325

The Informatica Services Properties dialog box appears.
3. Click the Log On tab.
4. On the Log On tab, select This account.

5. Type the domain and user name or click Browse to locate a system user.
6. Enter and confirm the password for the selected user account.
7. Click the Recovery tab.

8. Select the options to restart Informatica Services if the service fails.
For more information about configuring system accounts for services and service restart
options on Windows, see the Windows documentation.
Configuring Informatica Services 327

Configuring Application Services
You can create and configure application services in a PowerCenter domain during or after
installation. You may need to configure application services during installation if the
application service was not enabled during installation. You may need to create and configure
application services after installation if you require additional application services in the
domain. You use the Administration Console to configure application services.
You can create and configure the following application services during or after installation:
♦ Repository Service. Create or configure a Repository Service for a PowerCenter repository.
For more information about why you might need to create or configure a Repository
Service, see “Creating and Configuring the Repository Service” on page 328.
♦ Integration Service. Create or configure an Integration Service for an associated
Repository Service. For more information about why you might need to create or
configure an Integration Service, see “Creating and Configuring the Integration Service”
on page 329.
Creating and Configuring the Repository Service

You may need to create or configure a Repository Service in the following situations:
♦ The Repository Service could not be created during installation. If you perform a custom
installation of PowerCenter Advanced Edition and install PowerCenter Services or you
perform a complete installation of PowerCenter Standard Edition, the installer allows you
to skip Repository Service creation.
If you choose not to install the Repository Service, or the installer cannot create the
Repository Service due to an error, you can continue with the installation without creating
the service. However, you must create the service after installation completes.
♦ The Repository Service could not be enabled during installation. If the installer cannot
enable a Repository Service during installation, you can correct the Repository Service
configuration in the Administration Console to continue with the installation.
For example, you select an incorrect code page for an existing PowerCenter repository
during installation. The installer creates the Repository Service but cannot enable the
Repository Service process. You can modify the code page for the Repository Service in the
Administration Console, enable the service process, and continue the installation.
♦ You want to configure additional Repository Service properties. The installer creates a
Repository Service with a default set of properties. You can configure additional properties
for the Repository Service in the Administration Console.
For example, you want to enable versioning for a repository. The installer does not enable
versioning when it creates a Repository Service. You can enable versioning for the
Repository Service after installation.

♦ You perform a complete installation of PowerCenter Advanced Edition. The
PowerCenter Advanced Edition installer creates the Repository Service and configures the
PowerCenter repository for Metadata Manager. After installation, you must use the
Administration Console to create a Repository Service to connect to the PowerCenter
repository.
♦ Your installation includes multiple PowerCenter repositories. You can create one
Repository Service with the installer. If you require multiple repositories, you must create
the additional Repository Services for the repositories in the Administration Console.
For more information about creating and configuring a Repository Service, see “Creating and
Configuring the Repository Service” in the Administrator Guide.
Creating and Configuring the Integration Service

You may need to create or configure an Integration Service in the following situations:
♦ The Integration Service could not be created during installation. If you perform a
custom installation of PowerCenter Advanced Edition and install PowerCenter Services or
you perform a complete installation of PowerCenter Standard Edition, the installer allows
you to skip Integration Service creation.
If you choose not to install the Integration Service or the installer cannot create the
Integration Service due to an error, you can continue with the installation without creating
the service. However, you must create the service after installation completes.
♦ The Integration Service could not be enabled during installation. If the installer cannot
enable an Integration Service during installation, you can correct the Integration Service
configuration in the Administration Console to continue with the installation.
♦ The installer skipped Repository Service creation. You need to create an Integration
Service if the installer skipped creating the Repository Service during installation. If you
skip creating a Repository Service, the installer also skips Integration Service creation.
♦ You want to configure additional Integration Service properties. The installer creates an
Integration Service with a default set of properties. You can configure additional properties
for the Integration Service in the Administration Console.
For example, you want to configure $PMRootDir for an Integration Service process. The
installer uses the server/infa_shared directory on the machine where the installer runs as
the location of the Integration Service run-time files. If you want to change the location,
you must configure the Integration Service after installation.
♦ You perform a complete installation of PowerCenter Advanced Edition. The
PowerCenter Advanced Edition installer creates the Integration Service for Metadata
Manager. After installation, you must use the Administration Console to create an
Integration Service.
For more information about creating and configuring an Integration Service, see “Creating
and Configuring the Integration Service” in the Administrator Guide.
Configuring Application Services 329

Configuring the Metadata Manager Scheduler Service
Metadata Manager Client
After you install or upgrade Metadata Manager Client, you must configure the Informatica
PowerCenter Metadata Manager Scheduler service to interact with the desktop if you want to
run the Business Objects XConnect on a schedule.
To configure the service to interact with the desktop:
1. On the Metadata Manager Console machine, navigate to the Services window.

For example, in Windows XP Professional, select Settings > Control Panel >
Administrative Tools > Services.
2. Stop the Informatica PowerCenter Metadata Manager Scheduler service.
To stop the service, right-click the service and click Stop.
3. Right-click Informatica PowerCenter Metadata Manager Scheduler service and select
Properties.
The Informatica PowerCenter Metadata Manager Scheduler Properties window appears.
4. Click the Log On tab.
5. Select the Allow Service to Interact with Desktop option.
6. Click OK to close the Informatica PowerCenter Metadata Manager Scheduler Properties
window.
The Services window appears again.
7. Start the Informatica PowerCenter Metadata Manager Scheduler service.
To start the service, right-click the service and click Start.
8. Click OK to close the Informatica PowerCenter Metadata Manager Scheduler dialog box.
9. Close the Services window.

Creating a Data Profiling Warehouse
Data Profiling
Create a Data Profiling warehouse for each PowerCenter repository in which you want to
store data profiles. You can create a Data Profiling warehouse on any relational database that
PowerCenter supports as a source and target database. You can also create the Data Profiling
warehouse on the same database instance as the PowerCenter repository.
Complete the following steps to create the Data Profiling warehouse:
1. Run scripts to create the Data Profiling warehouse.
2. Create the Data Profiling warehouse views for Data Analyzer (Optional).
3. Configure connectivity to the Data Profiling warehouse.
4. Configure a data source and data connector for Data Analyzer (Optional).
Step 1. Create the Data Profiling Warehouse

To create a Data Profiling warehouse, run a script to create a warehouse schema for the
database type. When you install PowerCenter, the installer places the script in the following
directory:
<PowerCenter Client>\bin\Extensions\DataProfile\ProfileWarehouse
Table 15-1 shows the script you must run for each database type:
Table 15-1. Scripts for Creating a Data Profiling Warehouse
Database Type Script To create the warehouse...
IBM DB2 UDB create_schema_db2.sql Connect to DB2. Enter the following command from the command line:
db2 -tvf create_schema_db2.sql
Informix create_schema_inf.sql Run the dbaccess command line program. Select

create_schema_inf.sql as the file you want to execute. Select Run.
Microsoft SQL create_schema_sql.sql Open Query Analyzer. Run the create_schema_sql.sql script.
Server Note: Use Query Analyzer rather than isql to run the script. Otherwise,
the script may not run successfully.
Oracle create_schema_ora.sql Run the following command from the command line:
sqlplus <user name>/<password>@<database
server> @create_schema_ora.sql
Creating a Data Profiling Warehouse 331

Table 15-1. Scripts for Creating a Data Profiling Warehouse
Database Type Script To create the warehouse...
Sybase ASE create_schema_syb.sql Run the following command from the command line:
isql -U <user name> -P <password> -S <database
server> -i create_schema_syb.sql
Teradata create_schema_ter.sql Open Teradata SQL Assistant. Open the file create_schema_ter.sql and
click Execute. You can also run the script from BTEQWin.
Do not use the Execute Parallel option in Teradata Client 6.2 as this
option produces errors and the Data Profiling warehouse creation fails.
Step 2. Create the Data Profiling Warehouse Views

for Data Analyzer (Optional)
If you want to use Data Analyzer to view Data Profiling reports, you can create views in the
Data Profiling warehouse for Data Analyzer to use. If you create a Data Profiling warehouse
on Informix, you cannot use Data Analyzer to view Data Profiling reports.
After you create the Data Profiling warehouse, you can run a script to create views. When you
install PowerCenter, the installer places the script in the following directory:
<PowerCenter Client>\bin\Extensions\DataProfile\ProfileWarehouse\DA811
\DAViews
Table 15-2 shows the script you must run for each target database type:
Table 15-2. Scripts for Creating the Data Profiling Warehouse Views
Database Type Script To create the Data Profiling warehouse views for Data Analyzer...
IBM DB2 UDB upgrade_05_db2.sql Connect to DB2. Enter the following command from the command line:
db2 -tvf upgrade_05_db2.sql
Microsoft SQL upgrade_05_sql.sql Open Query Analyzer. Run the upgrade_05_sql.sql script.
Server Note: Use Query Analyzer rather than isql to run the script. Otherwise, the
script may not run successfully.
Oracle upgrade_05_ora.sql Run the following command from the command line:
sqlplus <user name>/<password>@<database
server> @upgrade_05_ora.sql
Sybase ASE upgrade_05_syb.sql Run the following command from the command line:
isql -U <user name> -P <password> -S <database server>
-i upgrade_05_syb.sql
Teradata upgrade_05_ter.sql Open Teradata SQL Assistant. Open the file upgrade_05_ter.sql and click
Execute. You can also run the script from BTEQWin.
Do not use the Execute Parallel option in Teradata Client 6.2. This option
produces errors and the Data Profiling warehouse creation fails.

Step 3. Configure Connectivity to the Data Profiling Warehouse
To configure connectivity to the Data Profiling warehouse, you create an ODBC connection
and create a connection object to the Data Profiling warehouse. You must create an ODBC
connection to the Data Profiling warehouse on each PowerCenter Client machine that
accesses the warehouse. After you create the ODBC connection, create a connection object
for the Data Profiling warehouse in the Workflow Manager.
For more information about establishing ODBC connectivity on Windows, see “Connecting
to Databases from Windows” on page 487. For more information about creating a connection
object, see “Managing Connection Objects” in the Workflow Administration Guide.
Step 4. Configure a Data Source and Data Connector

for Data Analyzer (Optional)
To view Data Analyzer Data Profiling reports in PowerCenter 8.1.1, you configure a data
source and data connector in Data Analyzer.
Complete the following steps to configure Data Analyzer Data Profiling reports:
1. Configure a data source for the Data Profiling warehouse in Data Analyzer. You must
configure a data source for each Data Profiling warehouse that contains data profile
results for which you want to view with Data Analyzer Data Profiling reports.
2. Create a data connector in Data Analyzer. If you do not already have a data connector,
you must create one. When you create the data connector, add the Data Profiling
warehouse data source to the data connector.
For information on configuring a data source and data connector, see “Setting Up the Data
Analyzer Data Profiling Reports” on page 351.
Creating a Data Profiling Warehouse 333

Configuring the PowerCenter Integration Utility for
WebSphere
Data Analyzer
If you run Data Analyzer on IBM WebSphere Application Server, you must configure the
PowerCenter Integration Utility client resource (notifyias.ear). Use the IBM WebSphere
Application Server utility called Application Client Resource Configuration Tool to configure
the notifyias.ear file. After you configure the notifyias.ear, you must also update the
notifyias.properties file.
To configure the PowerCenter Integration Utility for Data Analyzer running on IBM
WebSphere Application Server, complete the following steps:
1. Configure the notifyias.ear file.
2. Update the notifyias.properties file.
Step 1. Configure the notifyias.ear File

On Windows, open a command line window to run the program. On UNIX, start the
program from the shell command line.
To configure notifyias.ear:
1. Start the Application Client Resource Configuration Tool.

Go to the /bin directory of the PowerCenter Integration Utility and run the clientconfig
program. By default, the PowerCenter Integration Utility is installed in the following
directory:
/<PowerCenterInstallationDir>/DataAnalyzer/notifyias/
In the /notifyias/bin/ directory, run the following command:

Windows: clientconfig.bat
UNIX: clientConfig.sh
The Application Client Resource Configuration Tool window appears.
2. On the menu, choose File > Open.
3. Navigate to the directory where the PowerCenter Integration Utility is installed and
select the file notifyias.ear.
4. Click Open.
5. On the configuration tool menu, click PowerCenterIntegration.jar > JMS Providers.
6. Right-click WebSphere JMS Providers, and then select Properties.

The JMS Provider Properties window appears.
7. Select the General tab.
8. In the Context Factory Class property, enter the following factory class name:
com.ibm.websphere.naming.WsnInitialContextFactory
9. In the Provider URL property, enter the IBM WebSphere Application Server host name
and JMS server port number.
The machine that hosts Data Analyzer also hosts IBM WebSphere Application Server.
The host name must start with iiop://. The JMS server uses the default port number
9810 to communicate with the PowerCenter Integration Service.
For example, if the Data Analyzer host name is sculder.mully.com and the JMS server
uses the default port, enter the following host name and port:
iiop://sculder.mully.com:9810
10. Click OK.

11. On the configuration tool menu, click PowerCenterIntegration.jar > JMS Providers >
WebSphere JMS Providers > WAS Queue Connection Factories.
12. Right-click jms/QueueConnectionFactory and select Properties.
The Queue Connection Factory Properties window appears.
14. Enter the user name and password: padaemon.
This is the default user name and password used to install IBM WebSphere Application
Server. If you used another user name and password to install IBM WebSphere
Application Server, enter the name you selected.
15. Enter the node name for IBM WebSphere Application Server.
You set the node name when you install IBM WebSphere Application Server. The default
node name is typically the name of the machine hosting IBM WebSphere Application
Server. The node name is case sensitive.
16. Verify that the application server is JMS server.
17. Click OK.
18. On the configuration tool menu, click PowerCenterIntegration.jar > JMS Providers >
WebSphere JMS Providers > WAS Topic Connection Factories.
19. Right-click jms/TopicConnectionFactory and select Properties.
The Topic Connection Factory Properties window appears.
21. Enter the user name and password: padaemon.
Configuring the PowerCenter Integration Utility for WebSphere 335

This is the default user name and password used to install IBM WebSphere Application
Server. If you used another user name and password to install IBM WebSphere
Application Server, enter the name you selected.
22. Enter the node name for IBM WebSphere Application Server.
You set the node name when you install IBM WebSphere Application Server. The default
node name is typically the name of the machine hosting IBM WebSphere Application
Server.
23. Verify that the application server is JMS server.In the Port option, select QUEUED.
24. Click OK.
25. From the menu, choose File > Save.
26. Choose File > Exit to close the Application Client Resource Configuration Tool.
Step 2. Update the notifyias.properties File

Back up the notifyias.properties file before you modify it.
To configure the notifyias.ear:
1. In the PowerCenter Integration Utility folder, locate the notifyias.properties file.

/<PowerCenterInstallationDir>/DataAnalyzer/notifyias/notifyias.properties
2. Open the file with a text editor.

3. Search for the following text:
ProviderURL=
4. Set the provider URL property to the IBM WebSphere Application Server host name:
iiop://<WASHostName>:<JMSPortNumber>
The machine that hosts Data Analyzer also hosts IBM WebSphere Application Server.
The host name must start with iiop://. The JMS server uses the default port number
9810 to communicate with the PowerCenter Integration Service.
The value of the provider URL property in the notifyias.properties file must match the
value of the Provider URL property in the notifyias.ear file. For more information, see
step 9 in “Step 1. Configure the notifyias.ear File” on page 334.
5. Save and close the notifyias.properties file.

Updating a Data Analyzer or Metadata Manager License
Data Analyzer
Metadata Manager
You can use the License Update utility to update the license for Data Analyzer or Metadata
Manager. For example, if the Data Analyzer or Metadata Manager license expires, you can use
the utility to add a new license key.
When you install Data Analyzer or Metadata Manager, the PowerCenter installer adds the
license key to the appropriate EAR file. There is a separate EAR file for Data Analyzer and
Metadata Manager. The EAR file must contain a valid license key file for you to run Data
To update a license, copy the license key file to the License Upgrade utility directory and run
the utility. On Windows, run the License Update utility from the command line. On UNIX,
run the License Update utility as a shell script.
To update a Data Analyzer or Metadata Manager license:
1. Copy the new license key file to the License Update utility directory.
Copy the file to the appropriate directory:
Application License Update Utility Directory
Data Analyzer <Installation directory>\DataAnalyzer\license
Metadata Manager <Installation directory>\MetadataManager\license
2. Run the License Update utility.

For Windows, run the updateLicense.bat utility from the command line.
For UNIX, run the updateLicense.sh utility as a shell script.
3. Restart Data Analyzer or Metadata Manager to apply the new license.
Updating a Data Analyzer or Metadata Manager License 337

Configuring Microsoft SQL Server for a Data Analyzer
Repository
Data Analyzer
Data Analyzer requires JDBC distributed transaction support in the repository database.
When you use Microsoft SQL Server 2000 or 2005 with Data Analyzer, you must configure
distributed transaction support in Microsoft SQL Server. To configure distributed transaction
support on Microsoft SQL Server, you install JDBC XA stored procedures.
Complete the following steps to install JDBC XA stored procedures on Microsoft SQL Server:
1. Back up the master database for the Microsoft SQL Server instance.
2. Copy sqljdbc.dll to the <Microsoft SQL Server installation directory>\Binn directory
from the <PowerCenter installation directory>\DataAnalyzer\SQLServerJTA directory.
3. Use the following command to run instjdbc.sql:
isql
-U <database administrator name>
-P <administrator password>
-S <SQL Server name>
-i <PowerCenter installation
directory>\DataAnalyzer\SQLServerJTA\instjdbc.sql
The script generates a large amount of messages. View the messages for errors generated by
the script to troubleshoot issues with the installation. The script may fail if there is
insufficient space in the master database to store the procedures or log changes to the existing
procedures.

Setting Up the PowerCenter Repository Reports
Data Analyzer
To set up the PowerCenter Repository Reports, complete the following steps:

1. Create a data source to access the metadata for the reports. The PowerCenter
Repository Reports display metadata from a PowerCenter repository. Create a data source
in Data Analyzer to access the metadata from the PowerCenter repository.
2. Add the data source to a data connector. To run the PowerCenter Repository Reports,
you need a data connector that uses the data source to read metadata in the PowerCenter
repository.
3. Set up schedules for cached reports. To regularly update the reports and indicators, run
the PowerCenter Repository Reports on specific schedules.
After you set up the PowerCenter Repository Reports, you can view and use the reports just
like any other Data Analyzer reports. For more information about working with Data
Analyzer reports, see the Data Analyzer User Guide.
Step 1. Create a Data Source

PowerCenter Repository Reports use a data source for the PowerCenter repository.
PowerCenter Repository Reports display information about metadata in a PowerCenter
repository. It requires a JDBC data source that points to a PowerCenter repository database.
If you have more than one PowerCenter repository with metadata that you want to analyze,
you must create a data source for each repository. Create a JDBC data source for each
PowerCenter repository you want to report on.
To create the JDBC data source:
1. In Data Analyzer, click Administration > Schema Design > Data Sources.
2. On the Data Source page, click Add.
Setting Up the PowerCenter Repository Reports 339

3. From the Configure list, select JDBC Data Source.
4. Enter the data source information for the PowerCenter repository.

The following table describes the database information you need to enter to create the
JDBC data source:
Required/
Optional
System Name Required Name of the data source must be unique. The system name can
include any character except a space, tab, newline character, and the
following special characters:
\/:*?“<>|‘&[]
Description Optional Description for the data source. Maximum length for the description of
the data source is 255 characters.
Server Type Required Database type of the PowerCenter repository. You can run
PowerCenter Repository Reports on the following databases:
- Oracle
- Microsoft SQL Server
- IBM DB2
Select the database for the PowerCenter repository you want to report
on.
Driver Name Required JDBC driver name. Data Analyzer supplies the driver name for the
selected database drivers.

Required/
Optional
JDBC Connection String Required JDBC driver connection string. Data Analyzer supplies the connection
string syntax for the selected database driver. The connection string
requires the JDBC driver URL and database server information. Enter
the host name, port, and database information for the PowerCenter
repository database.
User Name Required User name to connect to the PowerCenter repository database.
Password Required Password for the user name to connect to the PowerCenter repository
database.
Test Table Required Table used to test the connection between Data Analyzer and the
PowerCenter repository. When you select the server type, Data
Analyzer supplies the table name. To use another table to test the
connection, enter a table name. Select a small table to test the
connection to avoid a performance impact at run time.
5. Select PowerCenter Repository.

6. Click Test Connection.
If the connection fails, verify that the repository database information is correct. Consult
your database administrator if necessary.
7. Click OK to save the JDBC data source.
Step 2. Add the Data Source to a Data Connector

Data Analyzer uses a data connector to access the data source for a report. The data connector
you use to run PowerCenter Repository Reports must contain the JDBC data source for the
You can add the PowerCenter Repository Reports data source to a data connector in one of
the following ways:
♦ Create a data connector. If Data Analyzer does not have data connectors, create a data
connector and add the PowerCenter Repository Reports data source to it.
♦ Add the data source to the system data connector. If Data Analyzer has data connectors,
you can add the PowerCenter Repository Reports data source to the system data
connector.
Creating a Data Connector for a PowerCenter Repository Reports Data

Source
If you use Data Analyzer only to run the PowerCenter Repository Reports, and Data Analyzer
does not yet have a data connector, create a system data connector for the PowerCenter
Repository Reports data source.

To create a data connector and add the data source:
1. In Data Analyzer, click Administration > Schema Design > Data Connectors.
The list of data connectors defined in the repository appears in the task area. The list is
empty if no data connectors have been defined.
2. Click Add.
The Data Connector page appears.
3. Enter a name and description for the data connector.

4. From the Primary Data Source list, select the PowerCenter repository data source.
This is the JDBC data source you created in “Step 1. Create a Data Source” on page 339.
5. Click OK.
When you create the first data connector in Data Analyzer, Data Analyzer saves the data
connector to the repository as the system data connector, making it available to all users.
All Data Analyzer users can run the PowerCenter Repository Reports.
Adding Data Sources to an Existing Data Connector

Data Analyzer can use one data connector to connect to different data sources for all reports.
With one data connector, there is no need to switch to a specific data connector to run a
report. If Data Analyzer has a system data connector, add the PowerCenter Repository
Reports data source to it.

To add data sources to a data connector:
1. In Data Analyzer, click Administration > Schema Design > Data Connectors.
The list of data connectors defined in the repository appears in the task area.
2. Click the name of the system data connector or the data connector you want to use for
PowerCenter Repository Reports.
The Data Connector page displays the data sources included in the data connector.
3. In Additional Schema Mappings, click Add.

The Additional Schema Mappings section expands to allow you to enter additional data
sources.

4. From the Data Source list, select the PowerCenter repository data source.
5. Add the JDBC data source that you created in “Step 1. Create a Data Source” on
page 339.
6. In the Available Schemas list, select the following schemas:
♦ DEPLOYMENT
♦ LABEL
♦ MAPPING
♦ MAPPLET
♦ METADATA
♦ SECURITY
♦ SESSION
♦ SOURCE
♦ TARGET
♦ TRANSFORM
♦ VERSION
♦ WORKFLOW
♦ WORKLET
7. Click Add >> to move the schemas to the Selected Schemas list.
8. Click Add.
Data Analyzer adds the JDBC data source to the data connector and displays it in the list
of additional schema mappings.
9. Click OK.
If you add the data source for PowerCenter Repository Reports to the system data
connector, you cannot edit the list of users who can use the data connector.

Step 3. Set Up Schedules for Cached Reports
PowerCenter Repository Reports include cached reports that run on specific schedules.
Add PowerCenter Repository Reports cached reports to the imported schedules. Next, run the
schedules to generate the reports for the first time.
Adding Reports to Schedules

To add the PowerCenter Repository Reports to the schedules, edit each report, select a
schedule, and save the report.
To add the PowerCenter Repository Reports to schedules:
1. Click the Find tab.

2. Click Public Folders > PowerCenter Repository Reports.
3. Select one of the cached reports to which you want to add to a schedule.
The reports are organized into folders. Navigate through the folders to locate each cached
report.
Table 15-3 describes the cached reports, their folder location, and associated schedules:
Table 15-3. PowerCenter Repository Reports Cached Report Schedules
Cached Report Report Folder Path Schedule
Average Load Times (Last Month) Operations > Session Execution Monthly
Connection Usage Operations > Session Execution Midnight Daily
Failed Session Statistics (Started Today) Operations > Session Execution Hourly
Invalid Mapping Statistics by Folder PowerCenter Objects > Mappings Midnight Daily
Mapping Statistics by Folder PowerCenter Objects > Mappings Midnight Daily
Server Load (Yesterday) Operations > Session Execution Midnight Daily
Sessions with Rejected Rows (Yesterday) Operations > Session Execution Midnight Daily
Source Statistics by Folder PowerCenter Objects > Sources Midnight Daily
Target Statistics by Folder PowerCenter Objects > Targets Midnight Daily
Top 10 Sessions with Rejected Rows (Yesterday) Operations > Session Execution Midnight Daily

For example, to select the report named Average Load Times (Last Month), click
PowerCenter Repository Reports > Operations > Session Execution. Next, select Average
Load Times (Last Month).
Click Edit to attach a schedule to the report.
4. Click Edit.
The report appears in the Create Report Wizard.
5. Click Publish.

6. On the Properties tab, select the Cached option, and then select the name of a schedule
from the list of schedules.
Select a schedule.
For a list of the cached reports and their assigned schedules, see Table 15-3 on page 345.
7. Click Save to save the report.
8. Click Close after Data Analyzer displays the following message:
The report has been saved successfully.
9. Repeat steps 3 to 8 to associate all other PowerCenter Repository Reports cached reports
to specific schedules.
You might want to review the properties of the cached reports listed in Table 15-3 on
page 345 to verify that the correct schedule has been added to each report.

10. To verify the schedule for a report, select a report and look at the Report Properties
section to identify the attached schedule.
Schedule for the report
Starting Schedules
PowerCenter Repository Reports provides several schedules to run reports. These schedules
run cached reports at regular intervals. After you attach the cached reports to schedules, start
the schedules to generate the cached reports.
Data Analyzer caches the results for the reports when the schedules run. You can open the
report to view the cached data. If you want to update report results before the next scheduled
run, manually start the schedule again.

To manually start PowerCenter Repository Reports schedules:
1. Click Administration > Scheduling > Time-Based Schedules.

A list of schedules appears.
Click Run Now to

run the Midnight
Daily schedule.
2. Click Run Now for the schedule that you want to start.
For example, to start the Midnight Daily schedule, click Run Now next to the Midnight
Daily schedule.
Data Analyzer adds the reports in the schedule to the queue and then runs the scheduled
reports.
3. Click OK to clear the acknowledgement message.
After you run the scheduled reports, click Dashboards to view the report indicators and
access the reports on the dashboards.
Switching PowerCenter Repositories

You can run PowerCenter Repository Reports for different PowerCenter repositories. To
switch to a another PowerCenter repository, use a different JDBC data source for the
PowerCenter Repository Reports. For example, if you first tested PowerCenter Repository
Reports on a development repository and now want to use it on a production repository, you
must switch the data sources.
To run the PowerCenter Repository Reports against a new PowerCenter repository, complete
the following steps:
1. Create a data source for the new PowerCenter repository. Set up a JDBC data source for
the new PowerCenter repository database. For information about setting up a JDBC data
source, see “Step 1. Create a Data Source” on page 339.
2. Edit the PowerCenter Repository Reports data connector and add the new data source.
Modify the data connector that you use to run the PowerCenter Repository Reports and
add the new JDBC data source. For information, see “Step 2. Add the Data Source to a
Data Connector” on page 341.

3. Use the global variables appropriate for the database type. When you install the
PowerCenter Repository Reports, you install global variables specific to the database type
of your PowerCenter repository. If the new repository is of a different database type, you
must delete the existing global variables and import the global variable XML file that is
applicable to the new database type.
By default, the PowerCenter Repository Reports XML files are installed in the following
directory:
/Informatica/PowerCenter8.1.1/DataAnalyzer/RepositoryReports
For more information about deleting global variables, see “Working with Global
Variables” in the Data Analyzer Schema Designer Guide. For more information about
importing global variables, see “Importing Objects to the Repository” in the Data
Analyzer Administrator Guide.
Use this procedure when you run the PowerCenter Repository Reports on a new PowerCenter
repository. If you already have a data source for a repository, you only need to modify the data
connector. If the PowerCenter repositories are of the same database type, you do not need to
update the global variables.

Setting Up the Data Analyzer Data Profiling Reports
Data Analyzer
Data Profiling
If you want to view Data Profiling reports with Data Analyzer, you must install and configure
Data Analyzer. You must be a Data Analyzer user with a System Administrator role to set up
the Data Profiling reports.
To install Data Analyzer Data Profiling reports, complete the following steps:
1. Configure a data source for the Data Profiling warehouse in Data Analyzer. Configure a
data source for each Data Profiling warehouse that contains profiling data for which you
want to view Data Analyzer Data Profiling reports.
2. Create a data connector in Data Analyzer. If you do not have a data connector, you must
create one. When you create the data connector, add the Data Profiling warehouse data
source to the data connector. If you create a data connector, you can skip the next step.
3. Add the Data Profiling warehouse data source to a data connector in Data Analyzer. If
you already have a data connector, add the Data Profiling warehouse data source to the
data connector. If you recently created a data connector, you should have already added
the Data Profiling warehouse data source to the data connector.
Step 1. Configure a Data Source for the Data Profiling Warehouse

You must configure a data source for each Data Profiling warehouse that contains profiling
data for which you want to view Data Analyzer Data Profiling reports.
To create the Data Profiling warehouse data source:
1. In Data Analyzer, click Administration > Schema Design > Data Sources.
2. On the Data Sources page, click Add.
Setting Up the Data Analyzer Data Profiling Reports 351

3. Enter a name and description for the data source.
4. Select the server type of the Data Profiling warehouse.

Data Analyzer provides JDBC drivers to connect to the Data Profiling warehouse. When
you select the server type, Data Analyzer supplies the driver name and connection string
format for the JDBC drivers that Data Analyzer provides.
Note: You cannot create an Informix data source.
5. Customize the JDBC connection string with the information for the warehouse.
6. Enter the user name and password to connect to the warehouse.
7. Test the connection.
If the connection fails, verify that the warehouse information is correct. Consult your
database administrator if necessary.
8. Click OK to save the data source.
For more information about Data Analyzer data sources, see the Data Analyzer Administrator
Guide.
Step 2. Create a Data Connector

You must create a data connector. After you create the data connector, add the data source to
the data connector. You can create data connectors for specific users and groups.
Note: If you have a data connector you want to add the data source to, you can skip this step.
However, you must add the Data Profiling data source to the data connector. For more
information about adding a data source to a data connector, see “Step 3. Add a Data Profiling
Data Source to a Data Connector” on page 354.
To create a data connector:
1. Click Administration > Schema Design > Data Connectors.

The list of data connectors defined in the repository appears in the task area.
2. Click Add.
The Data Connector page appears.
3. Enter the data connector properties listed in Table 15-4:
Table 15-4. Data Connector Properties
Required/
Optional
System Name Required Name of the data connector. The data connector name must be unique.
The system name can include any character except a space, tab, newline
character, and the following special characters:
\ / : * ? “ < > | ‘ &
Description Optional Description for the data connector. The connector description can be
between 1 and 255 characters.
Primary Data Source Required Primary data source from the list of data sources available in Data
Analyzer. Data Analyzer uses this data source to connect to the Data
Profiling warehouse and read the metric and attribute data for a report. For
information about how Data Analyzer connects to the primary and
additional data sources, see the Data Analyzer Administrator Guide.

Table 15-4. Data Connector Properties
Required/
Optional
Primary Time Optional This option does not apply to Data Profiling reports.
Dimension
Additional Schema Optional This option does not apply to Data Profiling reports.
Mappings
4. If you do not want to set up additional data sources, click OK.

If this is the first data connector in Data Analyzer, Data Analyzer saves the data
connector to the repository as the system data connector, making it available to all users.
You cannot edit the list of users who can use this data connector.
If this is not the system data connector, you can edit the list of users who can use this data
connector. You can activate this data connector in addition to the system data connector.
Step 3. Add a Data Profiling Data Source to a Data Connector

Data Analyzer uses a data connector to connect to a data source and read the data for Data
Profiling reports. Typically, Data Analyzer uses the system data connector to connect to all the
data sources required for reports. To run Data Profiling reports in Data Analyzer, add the
Data Profiling data source to the system data connector. If you have several data connectors
and you want to use a specific data connector for Data Profiling reports, add the Data
Profiling data source to the specific data connector.
Note: If you configured a data connector in the previous step, verify that you have added the
Data Profiling data source. Click the data connector name to see if the data source is listed as
the primary data source.
For more information about Data Analyzer data connectors, see the Data Analyzer
To add the Data Profiling warehouse data source to the system data connector:
1. Click Administration > Schema Design > Data Connectors.

The Data Connectors page appears.
2. Click the name of the system data connector.

Data Analyzer displays the properties of the system data connector.
3. In the Additional Schema Mappings, click Add.

Data Analyzer expands the section and displays the available schemas in the repository.
4. In the Data Source list, select the Data Profiling data source you created in “Step 1.
Configure a Data Source for the Data Profiling Warehouse” on page 351.
5. In the Available Schemas section, select the Data Profiling schemas you want to add and
click Add >>.
6. Click Add.

Data Analyzer displays the additional schema mappings for the system data connector.
7. Click OK.
You can now run Data Profiling reports using the system data connector.

Configuring INFA_HOME
Use INFA_HOME to designate the PowerCenter Services installation directory. If you
modify the PowerCenter Services directory structure, you need to configure the environment
variable to the location of the PowerCenter Services installation directory or the directory
where the installed PowerCenter Services files are located.
For example, you use a softlink in UNIX for any of the PowerCenter Services directories. To
configure INFA_HOME so that any PowerCenter Services application or service can locate
the other PowerCenter components it needs to run, configure INFA_HOME to the location
of the PowerCenter Services installation directory.
Configuring INFA_HOME 357

Chapter 16
Troubleshooting a
PowerCenter Installation
♦ Overview, 360
♦ Installer Log Files, 362
♦ Troubleshooting Domains and Nodes, 366
♦ Troubleshooting Application Services, 369
♦ Troubleshooting Data Analyzer and Metadata Manager, 372
♦ Troubleshooting Application Servers, 373
♦ Troubleshooting the PowerCenter Client, 376
♦ Installer Error Messages, 377
359
Overview
The installer configures and starts PowerCenter components, configures the Data Analyzer
and Metadata Manager applications, and starts the application server.
The installer collects information about the PowerCenter components you want to install,
such as the installation directory, license keys, and application server. It copies the
PowerCenter product files to the installation directory.
After the installer copies the files to the installation directory, you configure the PowerCenter
components. The installer may generate errors or warnings based on what you install:
♦ Domain and nodes. The installer creates a domain and gateway node or creates a node and
adds it to a domain. It also starts Informatica Services on a node and adds or updates
license objects in the domain. For more information about troubleshooting domain and
node creation, see “Troubleshooting Domains and Nodes” on page 366.
♦ Application services. The installer creates and enables a Repository Service and
Integration Service during installation. It also creates the content for a PowerCenter
repository or restores the content for the PowerCenter repository for Metadata Manager.
For more information about troubleshooting creation of Repository Services and
Integration Services, see “Troubleshooting Application Services” on page 369.
♦ Data Analyzer and Metadata Manager repositories. If you use a new Data Analyzer or
Metadata Manager repository, the installer creates the repository. It also switches the
database connection in the PowerCenter repository for Metadata Manager. For more
information about troubleshooting creation of the repositories for Data Analyzer and
Metadata Manager, see “Troubleshooting Data Analyzer and Metadata Manager” on
page 372.
♦ Data Analyzer and Metadata Manager applications. The installer deploys the Data
Analyzer and Metadata Manager applications on JBoss Application Server, BEA WebLogic
Server, or IBM WebSphere Application Server. The installer installs and configures Data
Analyzer and Metadata Manager and configures and starts the application server. For more
information about troubleshooting errors during deployment of Data Analyzer and
Metadata Manager on an application server, see “Troubleshooting Application Servers” on
page 373.
♦ PowerCenter Client. You may encounter errors when installing the PowerCenter Client.
For more information about troubleshooting errors during the PowerCenter Client
installation, see “Troubleshooting the PowerCenter Client” on page 376.
Note: Use the information in this chapter to get more information about the installation
process and the cause and resolution of errors that occur during the installation of
PowerCenter. The examples included in this chapter are intended to illustrate general
troubleshooting strategies and are not a comprehensive list of possible causes of installation
issues.
For more information about the error messages generated by the installer, see “Installer Error
Messages” on page 377.
360 Chapter 16: Troubleshooting a PowerCenter Installation

Troubleshooting Process
The PowerCenter installer allows you to incrementally configure PowerCenter components
during installation. The installer prompts for configuration information and then configures
the components. The installer validates the information in the installer window before
proceeding. If the verification passes, the installer configures the component with the
information in the installer window. If the installer fails to validate the information, or fails to
successfully configure or start the component, it generates an error message.
For example, if you create a domain, the installer creates the domain and gateway node and
starts Informatica Services. If the installer cannot start Informatica Services, it generates an
error. After you resolve the error and the installer starts Informatica Services, you can
continue to configure the other PowerCenter components.
Depending on the type of error, you may be able to continue the installation and resolve the
error later. For example, if you install PowerCenter Services without Metadata Manager and
the repository content creations fails for the PowerCenter repository, you can ignore the error,
skip repository content creation, and continue with the installation. Use the PowerCenter
Administration Console to correct the error and create the PowerCenter repository content
after installation completes.
For more information about whether you can skip the configuration of a PowerCenter
component, see “Installer Error Messages” on page 377.
Note: On Windows, if you leave the installer window when an error dialog box is open, you
can press Alt-Tab to return to the installer.
Overview 361
Installer Log Files
You can use the following log files to troubleshoot a PowerCenter installation:
♦ Installation log files. Includes debug, summary, and installation log files. For more
information, see “Installation Log Files” on page 362.
♦ Service Manager log files. Log files for the start up of the Service Manager for a node. For
more information, see “Service Manager Log Files” on page 364.
♦ Services log files. Log events for a PowerCenter domain and application services in a
domain. For more information, see “Services Log Events” on page 365.
Installation Log Files

The installer produces log files during and after the installation. You can use these logs to get
more information about the tasks completed by the installation and errors that occurred
during installation.
The PowerCenter installer uses the same names every time it creates the log files. If you install
the PowerCenter components individually, the installer creates new log files for the latest
installation and overwrites the log files created for a previous installation.
Debug Log Files

The installer writes actions and errors to the debug log file. The name of the log file depends
on the PowerCenter component you install.
Table 16-1 describes the properties of the debug log files:
Table 16-1. Debug Log File Properties
Log File Name - Informatica_Installation_Server_Debug.log

- Informatica_Installation_Client_Debug.log
- Informatica_Installation_Server_Upgrade_Debug.log
- Informatica_Installation_Reports_Debug.log
Location Installation directory. The PowerCenter Reports installation debug is generated in the root directory
on Windows and in the user home directory on UNIX.
Usage Get more information about the actions performed by the installer and get more information about
installation errors. The installer writes information to this file during the installation. If the installer
generates an error, you can use this log to troubleshoot the error.
Contents Detailed summary of each action performed by the installer, the information you entered in the
installer, each command line command used by the installer, and the error code returned by the
command.
The installer uses the PowerCenter infacmd and infasetup commands to create the domain and
node and create and start application services. It uses pmrep commands to create the
PowerCenter repository database tables and create and switch the database connection in the

PowerCenter repository for Metadata Manager. The installation debug log contains the
output of these commands.
For more information about the infacmd, infasetup, and pmrep commands, see the
PowerCenter Command Line Reference. You can find more information about errors generated
by these commands in the PowerCenter Troubleshooting Guide.
Summary Log File

The installer writes summary information about the installation after the installation
completes. The name of the log file depends on the PowerCenter component you install.
Table 16-2 describes the properties of the summary log files:
Table 16-2. Summary Log File Properties
Log File Name - summary_server.htm (Windows)

- summary_client.htm (Windows)
- summary_server.txt (UNIX)
Location Installation directory.
Usage Determine the status of the installation and the installed components. Get more information about
properties for the installed components.
Contents Installation status, date, installation set, installation directory, shortcut folder, configuration
properties (including URLs, user names and passwords), and component status.
The installation summary log includes the following statuses:

♦ SUCCESS. The creation or configuration of the component was successful.
♦ FAILURE. The creation or configuration of the component failed. This may occur if the
installer could not create a domain or node, or the installer could not create or start a
required service.
♦ SKIPPED. The creation or configuration of the component was skipped. This may occur
if a previous required component could not be created or configured, or you choose an
existing repository for PowerCenter, Metadata Manager, or Data Analyzer.
For example, if you choose an existing repository for the PowerCenter repository, the
PowerCenter repository creation status in the installation summary log indicates that
creation was skipped for that component.
The installation summary log might indicate that the configuration of a component was
skipped if creation or configuration of a previous component failed or you chose to ignore
an error generated by the installer. For example, if the installer cannot create a
PowerCenter repository, it skips the creation of the Metadata Manager and Data Analyzer
repositories.
♦ STARTED. Indicates the PowerCenter component was started successfully.
Installer Log Files 363

Note: The creation of some PowerCenter components can have a failure status, but the
installation succeeds with warnings. Use the component status listed in the summary log file
to find out which components you need to configure after installation.
File Installation Log Files

The installer writes information about the installed files to the file installation log file. The
PowerCenter Reports installer does not generate this log file.
Table 16-3 describes the properties of the installation log file:
Table 16-3. Installation Log Properties
Log File Name - PowerCenter_Services_8.1.1_InstallLog.log

- PowerCenter_Client_8.1.1_InstallLog.log
- InformaticaDeveloperPlatform8.1.1_InstallLog.log
Location Installation directory.
Usage Get information about files installed and registry entries created.
Contents Directories created, names of the files installed and commands run, and status for each installed file.
Service Manager Log Files

The installer starts Informatica Services during installation. Informatica Services start the
Service Manager for the node. The Service Manager generates log files that indicate the
startup status of a node. You can use the log events in these files to troubleshoot issues that
occur when the Service Manager on a node fail to start. The Service Manager log files are
located in the server/tomcat/logs directory on each node.
You might use these files to troubleshoot issues when Informatica Services fails to start during
an installation and you cannot log in to the PowerCenter Administration Console.
The Service Manager generates the following files:
♦ catalina.out. Log events from the Java Virtual Machine (JVM) that runs the Service
Manager. For example, if a port is available during installation, but in use when the Service
Manager starts, you can use this log to get more information about which port was
unavailable during startup of the Service Manager.
♦ node.log. Log events generated during the startup of the Service Manager on a node. You
can use this log to get more information about why the Service Manager for a node failed
to start. For example, if the Service Manager cannot connect to the domain configuration
database after 30 seconds, the Service Manager fails to start.
♦ localhost_log.<date>.txt. Internal log events from the Service Manager running on a node.
Log events are written to this file during startup and shutdown of a node.
Note: The Service Manager also uses node.log to log events when the Log Manager is
unavailable. For example, if the machine where the Service Manager runs does not have

enough available disk space to write log event files, the Log Manager is unavailable. For more
information, see “Managing Logs” in the Administrator Guide.
Services Log Events

You can use the Log Viewer in the Administration Console to view log events related to the
creating and enabling of the Repository Service or Integration Service or the creation of the
PowerCenter repository. After Informatica Services starts during installation, you can log in to
the Administration Console to get more information about installation problems.
You can view log events for the following PowerCenter Services components:
♦ Domain. Use the domain log to view log events related to the creation of application
services during installation.
♦ Integration Service. Use the Integration Service log events to troubleshoot issues related to
the startup of Integration Services during installation.
♦ Repository Service. Use the Repository Service log events to troubleshoot issues related to
the startup of Repository Services and the creation of PowerCenter repository content
during installation.
For more information about using the Log Viewer in the Administration Console, see
“Managing Logs” in the Administrator Guide. For more information about logging in to the
Administration Console, see “Logging in to the Administration Console” on page 547.
Installer Log Files 365

Troubleshooting Domains and Nodes
The installer may generate errors when creating and configuring domains and nodes during
the installation of PowerCenter Services. Use the information in this section to help
determine the cause of the error and the appropriate action to correct the error when you
install PowerCenter Services.
You may encounter errors with the following installer tasks:
♦ Creating the domain configuration database. The installer adds the domain configuration
metadata to a database. For more information about troubleshooting errors for the domain
configuration database, see “Creating the Domain Configuration Database” on page 366.
♦ Creating or joining a domain. The installer creates a domain and gateway node or creates
a node and adds it to a domain. For more information about troubleshooting errors when
the installer creates or joins a domain, see “Creating or Joining a Domain” on page 367.
♦ Starting Informatica Services. The installer starts Informatica Services on the node. For
more information about troubleshooting errors when the installer starts Informatica
Services, see “Starting Informatica Services” on page 367.
♦ Pinging the domain. The installer verifies that the domain you created or are joining is
available before it continues the installation. For more information about troubleshooting
errors when the installer pings the domain, see “Pinging the Domain” on page 368.
♦ Adding a license. The installer uses PowerCenter license key that you enter during
installation to create a license object in the PowerCenter domain. For more information
about troubleshooting errors when the installer adds the license to the domain, see
“Adding a License” on page 368.
Note: The installer must successfully complete the PowerCenter Services configuration to
continue with the installation. You cannot continue the installation if any configuration fails.
Creating the Domain Configuration Database

If you create a domain, the installer adds the domain configuration metadata to the domain
configuration database. The installer uses the options you enter in the Configure Domain
Database window to add the domain configuration metadata to the domain configuration
database. You can store the domain configuration database and the PowerCenter repository in
the one database if you use the same database user name. The installer uses JDBC to
communicate with the database. You do not need to configure connectivity on the machine
where you install PowerCenter Services.
The installer creates and drops a table in the domain configuration database to verify the
connection information. The user account you use for the domain configuration database
must have the create privilege on the database. You must store the domain configuration
database for different domains in separate user accounts.
For more information about the tables in the domain configuration database, see “Managing
the Domain” in the Administrator Guide.

Creating or Joining a Domain
The installer completes different tasks depending on whether you create a domain or join a
domain:
♦ Create a domain. The installer runs the infasetup DefineDomain command to create the
domain and the gateway node for the domain on the current machine based on the
information you enter in the Configure Domain window.
♦ Join a domain. The installer runs the infasetup DefineWorkerNode command to create a
node on the current machine, and runs the infacmd AddDomainNode command to add
the node to the domain. The installer uses the information you enter in the Configure
Domain and Configure Node windows to run the commands.
The infasetup and infacmd commands that create a domain or create a worker node and join
the domain fail if the gateway node is unavailable. If you cannot log into the PowerCenter
Administration Console, the gateway node is unavailable.
For example, the DefineDomain command may fail if you click Test Connection and the
connection test passed, but the database became unavailable before you clicked Next. The
DefineDomain command may also fail if the host name or IP address does not belong to the
current machine. Verify that the database for the domain configuration is available and that
the host name is correct and try again.
If the AddDomainNode command fails, verify that Informatica Services is running on the
gateway node and try again.
Starting Informatica Services

On Windows, the installer first removes the Informatica Services 8.1.1 service if it exists. On
Windows and UNIX, the installer runs infaservice to start Informatica Services. To
troubleshoot issues when Informatica Services on a node fails to start, you can use the
information in the installation debug log and the node.log and catalina.out Service Manager
log files to identify the cause of the error.
If you create a domain, you can log in to the PowerCenter Administration Console after
Informatica Services starts to verify the domain is available. If you join a domain, log in to the
Administration Console after Informatica Services starts to verify the node was successfully
created and started. For more information about logging in to the Administration Console,
see “Logging in to the Administration Console” on page 547.
For more information about infaservice, see “Starting and Stopping Informatica Services” on
page 529.
Informatica Services may fail to start for the following reasons:
♦ The Service Manager is out of system memory. The Java Runtime Environment (JRE)
that starts Informatica Services and runs the Service Manager may not have enough system
memory to start. Set the INFA_JAVA_OPTS environment variable to configure the
amount of system memory used by PowerCenter Services. On UNIX, you can set the
memory configuration when you start Informatica Services. For more information, see
“PowerCenter Services Environment Variables” on page 63.
Troubleshooting Domains and Nodes 367

♦ The domain configuration database is not available. Informatica Services fails to start on
a node if the Service Manager on a gateway node cannot connect to the domain
configuration database after 30 seconds. Verify that the domain configuration database is
available.
♦ You incorrectly configure the Informatica Services user account. Informatica Services
fails to start if you incorrectly configure the Windows domain, user name, or password
when you configure the user account to start Informatica Services on Windows. In
addition, the user account must have the Act as operating system permission.
Pinging the Domain

The installer runs the infacmd Ping command to verify that the domain is available before it
continues the installation. The domain must be available to add license objects to the domain,
create and enable the Repository Service and Integration Service, and create PowerCenter
repository content.
If the Ping command fails, you may need to start Informatica Services on the gateway node.
For more information about starting and stopping Informatica Services, see “Starting and
Stopping Informatica Services” on page 529.
Adding a License
The installer runs the infacmd AddLicense command to read the PowerCenter license key file
and create a license object in the domain. A valid license object must exist in the domain to
enable the Repository Service and Integration Service.
If you use an incremental license and join a domain, the serial number of the incremental
license must match the serial number for an existing license object in the domain. If the serial
numbers do not match, the AddLicense command fails.
You can get more information about the contents of the license key file used for installation,
including serial number, version, expiration date, operating systems, and PowerCenter and
connectivity options in the installation debug log. You can get more information about
existing licenses for the domain in the Administration Console.
For more information about licenses and license objects, see “Managing Licenses” in the

Troubleshooting Application Services
The installer may generate errors when creating and enabling Repository Services and
Integration Services during installation of PowerCenter Services and Metadata Manager. The
installer may also generate errors when it creates or restores repository content for the
PowerCenter repository. Use the information in this section to help determine the cause of
the error and the appropriate action to take after correcting the installation errors.
♦ Creating and enabling a Repository Service. The installer creates and enables a Repository
Service for PowerCenter Services or Metadata Manager. For more information about
troubleshooting Repository Service errors, see “Creating and Enabling a Repository
Service” on page 369.
♦ Creating or restoring repository content. The installer creates content for a PowerCenter
repository or restores the content for a PowerCenter repository for Metadata Manager. For
more information about troubleshooting creating or restoring repository content, see
“Creating and Restoring Repository Content” on page 370.
♦ Creating and enabling an Integration Service. The installer creates and enables an
Integration Service for PowerCenter Services or Metadata Manager. For more information
about troubleshooting an Integration Service, see “Creating and Enabling an Integration
Service” on page 371.
Note: If you install PowerCenter Services without Metadata Manager, you can continue the
installation and resolve the errors later. If you install Metadata Manager, the Repository
Service and Integration Service must be successfully created and enabled and the repository
content must be restored to continue with the installation.
Creating and Enabling a Repository Service

The installer runs the infacmd CreateRepositoryService command to create and enable a
Repository Service in the PowerCenter domain. The installer creates a Repository Service
with the same name as the PowerCenter repository. After the command completes, you can
log in to the Administration Console to view the status of the Repository Service. The
installer uses the pmrep connect command to connect to the repository to verify that the
Repository Service was enabled.
The installer verifies the contents of the repository database before it creates the Repository
Service. For example, if you choose a new PowerCenter repository, but select a database that
currently contains repository tables, the installer cannot create the Repository Service. You
must create a new database or use an existing PowerCenter repository.
The installer creates and drops a table in the repository database to verify the connection
information if you use a new or existing PowerCenter repository database. The user account
you use for the repository database must have the create privilege on the database.
If you install PowerCenter Services only, the Repository Service is created to use with the
PowerCenter repository. If you install Metadata Manager, the Repository Service is created to
Troubleshooting Application Services 369

use with the PowerCenter repository for Metadata Manager. The Repository Service uses the
same name as the repository name.
Note: If you install Metadata Manager and join a domain, the installer creates the Repository
Service for the PowerCenter repository for Metadata Manager on the gateway node for the
domain. The installer includes a generic list of code pages for the PowerCenter repository.
Verify that the code page you select is available on the gateway node for the domain you are
joining. If you select an existing repository, the code page must also be compatible with the
repository.
For example, the installer may fail to create the Repository Service if a Repository Service with
the same name as the PowerCenter repository exists in the domain. To correct the error, you
can complete one of the following steps:
♦ Rename the PowerCenter repository. If you create a PowerCenter repository, click Retry
in the error dialog box to return to the installer and enter a different name for the
♦ Remove the Repository Service. In the Administration Console, remove the Repository
Service with the conflicting name.
For more information about creating and enabling a Repository Service in the Administration
Console, see “Creating and Configuring the Repository Service” in the Administrator Guide.
Creating and Restoring Repository Content

The installer runs the pmrep Create and Restore commands to create the repository tables in
the PowerCenter repository database or restore the repository content to the PowerCenter
repository for Metadata Manager. The installer creates the repository tables if you choose a
new repository database in the Configure PowerCenter Repository window. When you choose
a new PowerCenter repository for Metadata Manager, the installer uses a backup repository
file to restore the repository content for the new version.
You can use an existing PowerCenter repository database for Metadata Manager if you have
already installed PowerCenter 8.1.1 using the repository database. For example, if you
uninstall PowerCenter 8.1.1 with Metadata Manager and then reinstall, you can use the
existing PowerCenter repository for Metadata Manager.
Otherwise, you must use a new repository database. The 8.1.1 version of the PowerCenter
repository for Metadata Manager contains updated Metadata Manager XConnect workflows
and mappings.
Note: If you choose an existing PowerCenter repository, you must upgrade the contents before
you can connect to the repository using the PowerCenter Client. For more information, see
“Upgrading PowerCenter” on page 401.
For more information about creating repository content in the Administration Console, see
“Managing the Repository” in the PowerCenter Administrator Guide. For more information
about pmrep, see the PowerCenter Command Line Reference.

Creating and Enabling an Integration Service
The installer uses the infacmd CreateIntegrationService and Ping commands to create and
enable an Integration Service and to verify that the service was enabled. After the commands
complete, you can log in to the Administration Console to view the status of the Integration
Service.
The installer may fail to create or enable the Integration Service for the following reasons:
♦ Name exists in domain. The CreateIntegrationService command fails if another
Integration Service with the same name exists in the domain. Click Retry in the error
dialog box and use another name or remove the existing Integration Service from the
domain.
♦ The associated Repository Service is unavailable. If the Repository Service created by the
installer is unavailable, the Integration Service is not enabled. Enable the Repository
Service and click Retry in the error dialog box.
♦ Incorrect user name or password in Configure Integration Service window. You can enter
the user name and password for the associated repository database if you choose an existing
PowerCenter repository for the Repository Service. Click Retry in the error dialog box and
correct the user name or password.
For more information about creating and enabling an Integration Service in the
Administration Console, see “Creating and Configuring the Integration Service” in the
Troubleshooting Application Services 371

Troubleshooting Data Analyzer and Metadata Manager
The installer may generate errors when creating the Data Analyzer and Metadata Manager
repositories. The installer may also generate errors when it switches connections for the
XConnect workflows in the restored PowerCenter repository for Metadata Manager. Use the
information in this section to help determine the cause of the error and the appropriate action
after correcting the installation errors.
♦ Creating the Data Analyzer repository. The installer creates content for a new Data
Analyzer repository.
♦ Creating or updating a Metadata Manager repository. The installer creates content for a
new Metadata Manager repository. The installer also switches the existing database
connections in the PowerCenter repository for Metadata Manager to a connection to the
Metadata Manager repository.
Creating a Data Analyzer Repository

The installer runs SQL scripts to create the tables in the Data Analyzer repository during
installation. The installer uses JDBC drivers installed during the installation file copy process
to communicate with the repository database. You do not need to configure database
connectivity on the machine where you install Data Analyzer.
For example, the installer may fail to create the Data Analyzer repository content if the user
account does not have permission to create database objects, if the database in unavailable, or
there is not sufficient available space to add the repository tables.
Creating and Updating a Metadata Manager Repository

The installer runs SQL scripts to create a new Metadata Manager repository. The Metadata
Manager repository is referred to as the Metadata Manager warehouse in the Metadata
Manager documentation. The installer uses JDBC drivers installed during the installation file
copy process to communicate with the repository databases. You do not need to configure
database connectivity on the machine where you install Metadata Manager.
Switching Connections
The installer runs the pmrep DeleteConnection, CreateConnection, and SwitchConnection
commands to delete the existing database connection object from the PowerCenter repository,
create a new database connection object, and switch it with the existing database connection
in the PowerCenter repository.
For more information about creating, deleting, and switching connections with pmrep, see the
PowerCenter Command Line Reference.

Troubleshooting Application Servers
You can use the error messages generated during installation, the installation debug log file,
and the application server log files to troubleshoot issues when you install Data Analyzer and
Metadata Manager.
The errors that occur and the steps to troubleshoot errors depend on the application server:
♦ JBoss Application Server. You can use the error message generated by the installer, the
installation debug log file, and the JBoss Application Server log files to troubleshoot issues
with JBoss Application Server.
♦ WebLogic Server. Use the error messages generated by the installer, the installation debug
log file, and the WebLogic Administration Console to troubleshoot issues with WebLogic
Server.
♦ WebSphere Application Server. Use the error messages generated by the installer, the
installation debug log file, WebSphere Application Server log files, and the WebSphere
Administration Console to troubleshoot issues with WebSphere Application Server.
Before you begin troubleshooting issues with application servers, verify that you have
correctly configured the application server. For more information about pre-installation tasks
for application servers, see “Application Servers” on page 40 and “Step 10. Install the
Application Server (Optional)” on page 70.

To troubleshoot issues with JBoss Application Server, use the error message generated by the
installer, the installation debug log file, and the JBoss Application Server startup messages to
troubleshoot errors. During the installation, you may encounter errors if the installer cannot
install the JBoss Application Server service, if JBoss Application Server does not start, or if the
Data Analyzer or Metadata Manager applications do not start.
On Windows, I installed a second instance of JBoss Application Server using the installer. I
used different port numbers than the first instance, but now I cannot start the first instance.
The installer installs the JBoss Application Server service with the following name:
Informatica_811_Jboss_<ServerConfigurationName>
The installer removes any existing JBoss Application Server service and creates a new service
with the new JBoss Application Server installation path. Therefore, the Windows service for
the first JBoss Application Server instance does not exist after installation.
To run two JBoss Application Server instances on a Windows machine, you must start the
instance not associated with the JBoss Application Server service from the command line. For
more information about starting JBoss Application Server from the command line, see
“Starting and Stopping Applications on JBoss Application Server” on page 537.
Troubleshooting Application Servers 373

I installed JBoss Application Server with the installer, but the application server did not
start.
Data Analyzer and Metadata Manager may not start during PowerCenter installation due to a
problem with JBoss Application Server or the Data Analyzer and Metadata Manager
applications.
To troubleshoot startup problems with JBoss Application Server:
1. Verify that the port numbers for JBoss Application Server are not used by any other JBoss
Application Server or other application. The installation debug log file contains a list of
the JBoss Application Server ports configured during installation.
If you find a conflict, you must reconfigure the ports. For more information about
configuring JBoss Application Server ports, see the JBoss documentation.
2. Verify that JBoss Application Server is running.
On UNIX, verify the following process is running:
/bin/sh run.sh -c informatica
On Windows, verify the following service is running:

Informatica_811_JBoss_informatica
3. If JBoss Application Server is running, skip to step 4.

-or-
If JBoss Application Server is not running, start JBoss Application Service. For more
information, see “Starting and Stopping Applications on JBoss Application Server” on
page 537.
4. On Windows, use the Event Viewer to view the event messages from JBoss Application
Server startup to determine why the Data Analyzer and Metadata Manager applications
were not deployed.
5. On UNIX, restart JBoss Application Server and use the console messages to determine
why the Data Analyzer and Metadata Manager applications were not deployed.
6. Correct the errors, make sure no other JBoss Application Server is running, and restart
JBoss Application Server.
For more information about starting and stopping JBoss Application Server, see “Starting and
Stopping Applications on JBoss Application Server” on page 537.
WebLogic Server
To troubleshoot issues with WebLogic Server, use the error messages from the installer, the
installation debug log file, and the WebLogic Administration Console to troubleshoot errors.
During the installation, you may encounter errors if the installer cannot install or configure
Data Analyzer or Metadata Manager, if WebLogic Server does not start, or if the Data
Analyzer or Metadata Manager applications do not start.

You can verify that WebLogic Server started successfully by logging in to the WebLogic
Administration Console. You can also view the log generated by WebLogic Server during
startup. The log file, <server name>.log, is located in the following directory:
<BEA_HOME>/user_projects/domains/<domain name>/<server name>/
After you correct any errors, restart WebLogic Server. For more information, see “Starting and
Stopping Applications on BEA WebLogic Server” on page 540.
After WebLogic Server starts, use the domain and server logs in the WebLogic Administration
Console to troubleshoot issues with Data Analyzer and Metadata Manager. For more
information about domain and server logs, see the BEA WebLogic Server documentation.

To troubleshoot issues with WebSphere Application Server, use the error messages from the
installer, the installation debug log file, and the WebSphere Application Server startup log
files and Administration Console to troubleshoot errors. During the installation, you may
encounter errors if the installer cannot install or configure Data Analyzer or Metadata
Manager, if WebSphere Application Server does not start, or if the Data Analyzer or Metadata
Manager applications do not start.
The installer uses the WebSphere Application Server wsadmin utility to perform configuration
tasks. For more information about the wsadmin utility, see the WebSphere Application Server
documentation.
If WebSphere Application Server fails to start, you can use the logs created during WebSphere
Application Server startup to determine why the application server failed to start. Use the
following log files:
♦ SystemErr.log
♦ SystemOut.log
Table 16-4 describes the locations of the WebSphere Application Server log files:
Table 16-4. WebSphere Application Server Log Files
Server Type Log Files Location
Deployment Manager <WAS_HOME>\DeploymentManager\logs\dmgr\
Node Agent <WAS_HOME>\AppServer\logs\nodeagent\
JMS Server <WAS_HOME>\AppServer\logs\jmsserver\
Server <WAS_HOME>\AppServer\logs\<server name>\
Note: The name of the default server for WebSphere Application Server is server1.
You can manually start WebSphere Application Server and deploy Data Analyzer or Metadata
Manager. For more information about starting WebSphere Application Server, see “Starting
and Stopping Applications on IBM WebSphere Application Server” on page 542.
Troubleshooting Application Servers 375

Troubleshooting the PowerCenter Client
I installed the Metadata Manager Client but the installation completed with the status
“SUCCESS with warnings”.
The installer may install Microsoft Data Access Components (MDAC) during installation of
the Metadata Manager Client. The installer installs MDAC if the version of MDAC on the
machine is not version 2.7 or 2.8. The following error may appear in the installation debug
log:
MDAC is executed with error code 3010. Client installation is completed
with warnings.
The message indicates the installation succeeded. You must restart the machine after the
installation completes.
The messages in the installation debug log indicated that the installer could not remove the
Metadata Manager Client service, but the Metadata Manager Client was not installed on the
machine.
The installation debug log file for the PowerCenter Client installation may contain errors
related to the installation of Windows services for the Metadata Manager Client. The installer
first removes the existing services. If no service exists, the installer may report an error. You
can ignore this error.
I installed the PowerCenter Client, but PowerCenter Data Stencil does not appear in the
Windows Start menu, and the MappingTemplate folder in the client directory is empty.
You must have the correct version and service pack level of the Microsoft .NET Framework
for PowerCenter Data Stencil to install properly.
Uninstall the PowerCenter Client, install the correct version of the Microsoft .NET
Framework, and reinstall the PowerCenter Client. For more information about the correct
version of the Microsoft .NET Framework, see “Third-Party Software” on page 43.

Installer Error Messages
The following error messages may appear in an error dialog box when you install
PowerCenter.
Cannot add license to domain.

Cause: The installer cannot create a license object in the domain or update an existing
license with the selected license key file using the infacmd AddLicense
command.
Action: Use the output of the AddLicense command in the error dialog box and the
installation debug log to identify why the command failed. Verify that the
gateway node for the domain is available by logging in to the Administration
Console. If you use an incremental license, verify that the serial number in the
license key file matches the serial number of an existing domain license object.
For more information, see “Adding a License” on page 368.
Cannot add node to domain.

Cause: The infacmd AddDomainNode command failed. The AddDomainNode
command adds the node name to the domain configuration database. The
node host name and port number is added to the domain configuration
metadata by the Service Manager on the gateway node when Informatica
Services is started on the node.
Action: Use the output of the AddDomainNode command in the error dialog box and
the installation debug log to identify why the command failed. Correct the
error and click Retry.
For more information, see “Creating or Joining a Domain” on page 367.
Cannot configure Data Analyzer on WebLogic Server.

Cause: The installer failed to configure the application server files for Data Analyzer.
Action: Use the message in the error dialog box and the installation debug log to
identify why the Data Analyzer configuration failed. Correct the error and
click Retry in the error dialog box. You must successfully configure the Data
Analyzer application to continue the installation.
For more information, see “WebLogic Server” on page 374.
Cannot configure Data Analyzer on WebSphere Application Server.

Cause: The wsadmin configuration command for Data Analyzer failed.
Action: Use the error message in the error dialog box and the installation debug log to
identify the cause of the error. Correct the error and click Retry. You must
successfully configure Data Analyzer to continue the installation.
For more information, see “WebSphere Application Server” on page 375.
Installer Error Messages 377

Cannot configure Metadata Manager on WebLogic Server.
Cause: The installer failed to configure the application server files for Metadata
Manager.
identify why the Metadata Manager configuration failed. Correct the error and
click Retry in the error dialog box. You must successfully configure the
Metadata Manager application to continue the installation.
Cannot configure Metadata Manager on WebSphere Application Server.

Cause: The wsadmin configuration command for Metadata Manager failed.
identify the cause of the error. Correct the error and click Retry. You must
successfully configure Metadata Manager to continue the installation.
Cannot connect to Repository Service.

Cause: The pmrep Connect command failed to connect to the repository for the
Repository Service. The Repository Service was not enabled.
Action: Use the output of the Connect command in the error dialog box and the log
events in the Administration Console Log Viewer to identify why the
command failed. Log in to the Administration Console and view the log
events for the Repository Service in the domain to determine why the
Repository Service could not be enabled.
Correct the error and click Retry. If you are not installing Metadata Manager,
you can click Ignore to continue the installation and enable the Repository
Service in the Administration Console after installation. If you ignore the
error, you must also create repository content for the repository after
installation.
For more information, see “Creating and Enabling a Repository Service” on
page 369.
Cannot create Data Analyzer repository.

Cause: The installer could not create the tables in the Data Analyzer repository
database.
identify why the repository creation failed. Correct the error and click Retry in
the error dialog box. The installer must successfully create the repository to
continue the installation.
For more information, see “Creating a Data Analyzer Repository” on
page 372.

Cannot create domain.
Cause: The infasetup DefineDomain command failed.
Action: Use the output of the DefineDomain command in the error dialog box to
identify why the command failed. Correct the error and click Retry.
Cannot create Integration Service.

Cause: The infacmd CreateIntegrationService command failed to create the
Integration Service.
Action: Use the output of the CreateIntegrationService command in the error dialog
box and the log events in the Administration Console Log Viewer to identify
why the command failed. Log in to the Administration Console and view the
log events for the domain to determine why the Integration Service could not
be created.
you can click Ignore to continue the installation and create the Integration
Service in the Administration Console after installation.
For more information, see “Creating and Enabling an Integration Service” on
page 371.
Cannot create Metadata Manager repository.

Cause: The installer could not create the tables in the Metadata Manager repository
database.
identify why the repository creation failed. Correct the error and click Retry in
the error dialog box. The installer must successfully create the repository to
For more information, see “Creating and Updating a Metadata Manager
Repository” on page 372.
Cannot create node.

Cause: The infasetup DefineWorkerNode command failed. A domain contains
gateway nodes and worker nodes. When you join a domain, the installer
creates a worker node on the current machine.
Action: Use the output of the DefineWorkerNode command in the error dialog box
and the installation debug log to identify why the command failed. Correct
the error and click Retry.

Cannot create or restore repository content.
Cause: The pmrep Create or Restore command failed to create the repository tables or
restore the PowerCenter repository content.
Action: Use the output of the pmrep command in the error dialog box and the log
events in the Administration Console Log Viewer to identify why the
command failed. Log in to the Administration Console and view the log
events for the Repository Service to determine why the repository contents
could not be created or restored.
you can click Ignore to continue the installation and create repository content
after installation. The pmrep Create command rolls back any changes to the
repository database if content creation is unsuccessful.
For more information, see “Creating and Restoring Repository Content” on
page 370.
Cannot create Repository Service.

Cause: The infacmd CreateRepositoryService command failed to create the
Repository Service.
Action: Use the output of the CreateRepositoryService command in the error dialog
box and the log events in the Administration Console Log Viewer to identify
why the command failed. Log in to the Administration Console and view the
log events for the domain to determine why the Repository Service could not
be created.
you can click Ignore to continue the installation and create the Repository
Service in the Administration Console after installation. If you skip creation of
the Repository Service, the installer also skips creation of the Integration
Service.
For more information, see “Creating and Enabling a Repository Service” on
page 369.
Cannot federate WebSphere node.

Cause: The wsadmin addNode command failed to add the WebSphere node.
identify the cause of the error. Correct the error and click Retry. If you already
added the node, click Ignore.
Cannot install Data Analyzer on WebLogic Server.

Cause: The installer failed to copy application server files and Data Analyzer
configuration files to the application server directory.

identify why the Data Analyzer installation failed. Correct the error and click
Retry in the error dialog box. You must successfully install the Data Analyzer
application to continue the installation.
Cannot install JBoss service.

Cause: The installer could not install the JBoss Application Server service.
Action: Use the installation debug log to identify why the service installation failed.
Correct the error and click Retry in the error dialog box. You must successfully
install the JBoss Application Server service to continue the installation.
For more information, see “JBoss Application Server” on page 373.
Cannot install Metadata Manager on WebLogic Server.

Cause: The installer failed to copy application server files and Metadata Manager
configuration files to the application server directory.
identify why the Metadata Manager installation failed. Correct the error and
click Retry in the error dialog box. You must successfully install the Metadata
Manager application to continue the installation.
Cannot ping domain.

Cause: The infacmd Ping command failed to connect to the PowerCenter domain.
Action: Use the output of the Ping command in the error dialog box and the
installation debug log to identify why the command failed. Verify that the
domain is available and try again. You may need to start Informatica Services
on the gateway node.
For more information, see “Pinging the Domain” on page 368.
Cannot ping Integration Service.

Cause: The infacmd Ping command failed to ping the Integration Service. The
Integration Service was not enabled.
Action: Use the output of the Ping command in the error dialog box and the log events
in the Administration Console Log Viewer to identify why the command
failed. Log in to the Administration Console and view the log events for the
Integration Service in the domain to determine why the Integration Service
could not be enabled.
you can click Ignore to continue the installation and enable the Integration
Service in the Administration Console after installation.

For more information, see “Creating and Enabling an Integration Service” on
page 371.
Cannot remove Informatica Services service.

Cause: On Windows, the installer ran the infaservice remove command to remove an
existing Informatica Services service, but the removal failed.
Action: If you are installing PowerCenter Services on the current machine for the first
time, click Ignore. infaservice reports an error if it could not remove the service
when the service does not exist. If the service currently exists on the machine,
verify that the user account installing PowerCenter Services has permissions to
remove a service and click Retry. You can get more information about the error
in the installation debug log.
For more information, see “Starting Informatica Services” on page 367.
Cannot start Informatica Services.

Cause: The infaservice startup command failed to start Informatica Services.
Action: Use the node.log and catalina.out Service Manager log files to identify the
reason why Informatica Services could not be started on the machine. After
you correct the error, click Retry.
For more information, see “Starting Informatica Services” on page 367.
Cannot stop WebSphere Application Server node.

Cause: The wsadmin stopNode command failed.
identify the cause of the error. Correct the error and click Retry.
Cannot stop WebSphere Manager.

Cause: The wsadmin stopManager command failed.
identify the cause of the error. Correct the error and click Retry. You can also
stop the WebSphere Manager manually and click Ignore.
Cannot Sync Node on WebSphere Application Server.

Cause: The wsadmin syncNode command failed.
identify the cause of the error. Correct the error and click Retry. If you already
synchronized the node, click Ignore.

Cannot switch repository connections.
Cause: The pmrep DeleteConnection, CreateConnection or SwitchConnection
command failed. If the CreateConnection command fails, the
SwitchConnection command fails also.
Action: Use the output of the pmrep command in the error dialog box and the
installation debug log to identify why the command failed. Correct the error
and click Retry in the error dialog box.
You can also click Ignore to continue the installation. You create or switch the
database connection objects in the PowerCenter repository before you can run
XConnect workflows with Metadata Manager after installation.
For more information, see “Switching Connections” on page 372.
Cannot update Metadata Manager repository content.

Cause: The installer could not update the tables in the Metadata Manager repository
database.
identify why the repository update failed. Correct the error and click Retry in
the error dialog box. The installer must successfully update the repository to
For more information, see “Creating and Updating a Metadata Manager

Chapter 17
Uninstalling PowerCenter

♦ Overview, 386
♦ Running the Uninstaller, 388
♦ Complete Uninstallation in Graphical Mode, 390
♦ Partial Uninstallation in Graphical Mode, 392
♦ Uninstallation in Console Mode, 396
385
Overview
When you install PowerCenter Standard Edition or Advanced Edition, the installer creates an
uninstaller. The uninstaller keeps a record of all the files copied to the installation directory.
To uninstall PowerCenter and PowerCenter components, run the uninstaller created by the
installer. On UNIX, run the uninstaller from the command line. On Windows, run the
uninstaller from the Windows Start Menu.
When you run the uninstaller, the uninstaller deletes the PowerCenter files and clears all
configuration. The uninstallation process does not delete files that are not installed by the
installer. For example, the configuration process that happens as part of the installation may
create temporary directories. The uninstaller does not keep a record of these directories and
therefore cannot delete them. You must manually delete these directories for a clean
uninstallation.
When you uninstall a specific PowerCenter component, the uninstaller deletes the files for the
product component. It does not delete files for the other installed PowerCenter components.
The uninstaller allows you to select the component you want to uninstall. You do not need to
uninstall all components at one time. After you run the uninstaller, it keeps a record of the
components that remain installed. The next time you run the uninstaller, the components
that remain installed are available for uninstallation.
Uninstallation Rules and Guidelines

Use the following rules and guidelines when you uninstall PowerCenter components:
♦ Uninstalling PowerCenter does not affect the PowerCenter repositories. The uninstaller
removes the PowerCenter files. It does not remove repositories from the database. If you
need to move the repositories, you can back them up and restore them in another database.
♦ Uninstalling PowerCenter Services does not remove the metadata tables from the domain
configuration database. If you install PowerCenter Services again using the same domain
configuration database and user account, you must manually remove the tables.
If you want to remove the metadata tables manually, drop the following tables:
− PCSF_CPU_USAGE_SUMMARY
− PCSF_DOMAIN
− PCSF_MASTER_ELECTION
− PCSF_MASTER_ELECT_LOCK
− PCSF_REPO_USAGE_SUMMARY
− PCSF_RUN_LOG
If you want to back up the domain configuration database before you remove the metadata
tables, use the infasetup BackupDomain command. For more information, see "infasetup
Command Reference" the Command Line Reference.
386 Chapter 17: Uninstalling PowerCenter

♦ When you uninstall Data Analyzer and Metadata Manager, the uninstaller removes files
installed during the installation of the application. It does not remove files related to the
application server files or those created during configuration. Generally, the uninstaller
also does not remove application server files that may be shared by other applications
running on the application server. You must manually remove the files.
For example, you install Data Analyzer on BEA WebLogic Server and choose to create a
WebLogic domain named Informatica. When you uninstall Data Analyzer, the uninstaller
removes the Data Analyzer files copied into the domain during installation. It does not
remove the Informatica WebLogic domain or application server files and directories
created in the domain. To remove the Informatica WebLogic domain, delete the domain
directory manually.
♦ If you install Data Analyzer and Metadata Manager on the same application server and you
uninstall Data Analyzer or Metadata Manager, the uninstaller removes the application you
select. It does not remove files related to the application you did not uninstall.
♦ The uninstaller removes JBoss Application Server installed with Data Analyzer or
Metadata Manager if no application currently uses JBoss Application Server. For example,
you install Data Analyzer and Metadata Manager on JBoss Application Server. If you
uninstall Data Analyzer, JBoss Application Server remains installed. If you then uninstall
Metadata Manager, the uninstaller removes JBoss Application Server.
♦ The uninstaller does not create a log of the uninstallation process. At the end of the
uninstallation process, the uninstaller displays the names of the files and directories that
could not be removed.
♦ If you run the installer and install one PowerCenter component, and then install another
PowerCenter component in a different directory, the uninstaller available through the
Windows Start menu removes the last installed component. You must run the uninstaller
in the _uninstallServer directory to remove the first installed component.
♦ If you install PowerCenter Services and the PowerCenter Client in the same directory, and
uninstall PowerCenter Services, the uninstaller removes the ODBC5.1 directory. The
ODBC5.1 directory is required by the PowerCenter Client. You must reinstall either the
PowerCenter Client or PowerCenter Services to reinstall the ODBC drivers.
Overview 387
Running the Uninstaller
To uninstall PowerCenter, use the uninstaller created during the PowerCenter installation.
On Windows, do not use the Control Panel to remove the PowerCenter program.
Uninstalling with the Control Panel does not completely remove PowerCenter components.
When you install PowerCenter or PowerCenter components, the installer creates an
uninstallation directory in the PowerCenter installation directory. The uninstallation
directory name depends on the installation you perform.
Table 17-1 describes the uninstall directory for each type of installation:
Table 17-1. PowerCenter Uninstallation Directories
Installation Uninstall Directory Name
PowerCenter <InstallationDirectory>/_uninstallServer
PowerCenter Client <InstallationDirectory>/_uninstallClient
Before You Uninstall

Before you uninstall PowerCenter, stop all its services. The uninstallation process cannot
remove the files that are being used by a service that is running. You must stop Informatica
Services and the application server for Data Analyzer and Metadata Manager.
For more information about stopping Informatica Services, see “Starting and Stopping
Informatica Services” on page 529. For more information about stopping the application
servers, see “Starting and Stopping Application Servers” on page 535.
Uninstallation Options
The method you use to uninstall depends on your operating system:
♦ UNIX. Use the console mode interface or graphical mode interface to uninstall
PowerCenter components.
♦ Windows. Use the graphical mode interface to uninstall PowerCenter components.
Running the Uninstaller on UNIX

To uninstall a PowerCenter component on UNIX, run the uninstaller in the uninstall
directory. For example, you want to uninstall Metadata Manager that you installed in the
Informatica/PowerCenter8.1.1 directory.
To uninstall Metadata Manager, go to the following directory:
Informatica/PowerCenter8.1.1/_uninstallServer
Type the following command to run the uninstaller.

./uninstaller [-console]

For more information about using the console mode interface, see “Uninstallation in Console
Mode” on page 396.
Running the Uninstaller on Windows

The installer creates a shortcut to the uninstaller from the Windows Start menu. To uninstall
PowerCenter Client on Windows, click Start > Program Files > Informatica PowerCenter
8.1.1 > Server | Client > Uninstaller.
Running the Uninstaller 389

Complete Uninstallation in Graphical Mode
When you perform a complete uninstallation, the uninstaller removes all PowerCenter
components from the installation directory.
The server and client uninstallers display similar windows. You can use the following
procedure to uninstall any PowerCenter component.
To perform a complete uninstallation:
1. On UNIX, go to the uninstallation directory for the PowerCenter component you want
to uninstall and type the following command to run the uninstaller:
./uninstaller
For the list of uninstallation directories, see Table 17-1 on page 388.
2. On Windows, click Start > Program Files > Informatica PowerCenter 8.1.1 > Server >
Uninstaller.
The Uninstall PowerCenter 8.1.1 window displays information about the uninstallation
process.
3. Click Next.
The Uninstallation window displays the PowerCenter uninstallation options.
4. To uninstall all the PowerCenter components in the installation directory, select

Uninstall All Components.
5. Click Next.

The uninstaller displays the names of the files as they are deleted. When uninstallation
completes, the uninstaller displays the Uninstall Complete window.
If all files are successfully deleted, the Uninstall Complete window displays a message that
the uninstallation was successful.
If not all files are deleted, the Uninstall Complete window displays the list of files that
were not deleted. You can choose to restart the system now, or restart the system later.
6. Click Done.
7. If the installer does not delete all files, review the files and directories to determine if it is
safe to delete them. Then delete them manually.
Complete Uninstallation in Graphical Mode 391

Partial Uninstallation in Graphical Mode
When you perform a partial uninstallation, the uninstaller removes the PowerCenter
component that you select.
The server and client uninstallers display the similar windows. You can use the following
procedure to uninstall any PowerCenter component.
To perform a partial uninstallation:
1. On UNIX, go to the uninstallation directory for the PowerCenter component you want
to uninstall and type the following command to run the uninstaller:
./uninstaller
2. On Windows, click Start > Program Files > Informatica PowerCenter 8.1.1 > Server |
Client > Uninstaller.
For more information about running the uninstaller, see “Running the Uninstaller” on
page 388.
The Uninstall PowerCenter 8.1.1 window displays information about the uninstallation
process.
3. Click Next.
The Uninstallation window displays the PowerCenter uninstallation options.
4. To uninstall specific PowerCenter components, select Uninstall Specific Components and

click Next.

The Choose Components to Uninstall window displays the installed PowerCenter
components.
5. Select the components you want to uninstall.

You can select any number of components to uninstall.
For example, you can select to uninstall Data Analyzer and Metadata Manager.
6. Click Uninstall.
Partial Uninstallation in Graphical Mode 393

The uninstaller displays the names of the files that are uninstalled. When uninstallation
completes, the uninstaller displays the Uninstall Complete window.
If all files are successfully uninstalled, the Uninstall Complete window displays a message
that the uninstallation was successful.
If not all files are deleted, the Uninstall Complete window displays the list of files that
were not deleted. You can choose to restart the system now, or restart the system later.
7. Click Done.
If the installer does not uninstall all files, review the files and directories to determine if it
is safe to delete them and delete them manually.
If you do not delete all components, you can run the same uninstaller again to remove the
remaining installed components. When you run the uninstaller, you can uninstall those
programs and components that you have not uninstalled previously.

For example, if you uninstall Data Analyzer and Metadata Manager, the next time you run the
uninstaller, the list of installed PowerCenter components available for uninstallation does not
include Data Analyzer and Metadata Manager.
You can run the uninstaller until all PowerCenter components are uninstalled.
Partial Uninstallation in Graphical Mode 395

Uninstallation in Console Mode
Uninstalling in console mode on UNIX is similar to uninstalling in graphical user interface
mode. You can perform a complete or partial uninstallation using console mode on UNIX.
When you perform a complete uninstallation in console mode, the uninstaller removes all
installed components. When you perform a partial uninstallation, the uninstaller removes the
components you choose.
Uninstalling in console mode differs from graphical user interface mode in the following
ways:
♦ Help. There is no associated help for any of the panels. If you need more information,
refer to the relevant section on using graphical user interface mode.
♦ Input method. All input is collected through the keyboard. You cannot select information
from a list, click a button, or select check boxes to enable options.
♦ Quitting the uninstaller. To exit the uninstaller, type quit at any prompt.
To perform a complete or partial uninstallation using console mode:
1. Go to the uninstallation directory for the PowerCenter component you want to uninstall.
2. To start the uninstaller, type the following command:
./uninstaller -console
Use the -console option if you configured X Windows and you want to use console
mode. Otherwise, the uninstaller starts in graphical mode.
The Uninstall PowerCenter Components panel displays information about the
uninstallation process.
3. Press Enter.
4. Enter the number for the type of uninstallation you want to perform and press Enter.
Table 17-2 describes the options you can choose for uninstalling PowerCenter:
Table 17-2. Uninstallation Options
Option Description
1 Completely remove all features and components.
2 Choose specific features installed by InstallAnywhere.
If you enter 1, skip to step 6.

5. Enter the number for the features you want to uninstall. You can enter multiple values
separated by commas. Depending on your installation, you can uninstall the following
features:
♦ PowerCenter Services

♦ PowerCenter Data Analyzer
♦ PowerCenter Metadata Manager
6. Press Enter.
The uninstaller uninstalls the selected components. After uninstallation completes, the
console displays the results of the uninstallation.
Uninstallation in Console Mode 397

Part III: Upgrading PowerCenter

♦ Upgrading PowerCenter, 401
♦ Upgrading Data Analyzer, 431
♦ Upgrading Metadata Manager, 441
♦ After You Upgrade, 455
399
400
Chapter 18
Upgrading PowerCenter

♦ Overview, 402
♦ Validate Configuration Files, 406
♦ Upgrade a Global Repository, 409
♦ Upgrade a Local Repository, 413
♦ Upgrade the PowerCenter Server, 416
♦ View Upgrade Results, 419
♦ Upgrade Domain and Node Metadata, 420
♦ Upgrade the PowerCenter Repository, 424
♦ Upgrade the PowerCenter Client, 426
♦ Upgrade Data Profiling, 427
401
Overview
This chapter describes the tasks you must complete to upgrade PowerCenter. You may need to
perform upgrade tasks depending on the version of PowerCenter you upgrade:
♦ PowerCenter 6.x/7.x. Use the Upgrade Wizard in the PowerCenter Administration
Console to upgrade a Repository Agent and PowerCenter Server configuration in
PowerCenter 6.x or 7.x to a Repository Service and Integration Service in a PowerCenter
8.1.1 domain. You can also upgrade existing PowerCenter repository content to the new
repository version and upgrade PowerCenter Client.
♦ PowerCenter 8.0. Upgrade domain and node metadata, upgrade PowerCenter repository
content and the PowerCenter Client, and upgrade the Data Profiling warehouse.
♦ PowerCenter 8.1. Upgrade the PowerCenter Client and the Data Profiling warehouse. You
use the installer to install PowerCenter and upgrade the domain and nodes when you
upgrade PowerCenter 8.1.
PowerCenter Upgrade Steps

Before you upgrade PowerCenter, you must complete the pre-upgrade steps. For more
information, see “Before You Upgrade” on page 77.
Table 18-1 describes the steps for each version to upgrade an existing PowerCenter
installation:
Table 18-1. PowerCenter Upgrade Steps
6.x / 7.x 8.0 8.1

Description
Step Step Step
1 - - Select the configuration files. Start the Upgrade Wizard and select and validate the
configuration files for the Repository Agent or PowerCenter Server. For more
information, see “Validate Configuration Files” on page 406.
2 - - Upgrade the global repository. Upgrade a Repository Agent configuration to a

Repository Service and upgrade the contents of the global repository. For more
information, see “Upgrade a Global Repository” on page 409.
3 - - Upgrade the local repository. Upgrade a Repository Agent configuration to a Repository

Service and upgrade the contents of the local repository. For more information, see
“Upgrade a Local Repository” on page 413.
4 - - Upgrade the PowerCenter Server configuration. Upgrade a PowerCenter Server

configuration to an Integration Service. For more information, see “Upgrade the
PowerCenter Server” on page 416.
5 - - View the results of the upgrade. The Upgrade Wizard lists the results of all upgrade
activities. For more information, see “View Upgrade Results” on page 419.
- 1 - Upgrade domain and node metadata. Use infaupgrade to upgrade the domain and node
metadata for the domain and the nodes in the domain. For more information, see
“Upgrade Domain and Node Metadata” on page 420.
402 Chapter 18: Upgrading PowerCenter

Table 18-1. PowerCenter Upgrade Steps
6.x / 7.x 8.0 8.1

Description
Step Step Step
6 2 - Upgrade the PowerCenter repository content. If you upgrade from PowerCenter 8.0, you
must upgrade the repository contents in the Administration Console. For more
information, see “Upgrade the PowerCenter Repository” on page 424.
7 3 1 Upgrade the PowerCenter Client. For more information, see “Upgrade the PowerCenter
Client” on page 426.
8 4 2 Upgrade the Data Profiling warehouse. For more information, see “Upgrade Data
Profiling” on page 427.
PowerCenter Repository Upgrade

When you upgrade a PowerCenter repository, you upgrade the repository content.
PowerCenter 8.1 includes a new repository version, 177, and data version, D86, if you
upgrade from PowerCenter 6.x, 7.x, or 8.0. You need to upgrade your existing repository to
incorporate the new features. When you upgrade a repository, the upgrade process modifies
repository tables to accommodate new types of metadata and introduces new objects to the
repository.
The upgrade process proceeds incrementally, one repository version at a time, incorporating
new features with each version. The repository upgrade process stops if it encounters
problems during the upgrade such as lack of disk space. After you identify and fix the
problem, you can continue the upgrade. For more information about changes to the
functionality of existing metadata, see the PowerCenter Post-Upgrade Reference.
During the upgrade, existing data is copied from the original tables into temporary tables.
Because these temporary tables are created in the same database as the repository, the upgrade
process requires additional space.
Table 18-2 describes the increase in repository size from PowerCenter 7.x to PowerCenter
8.1.1:
Table 18-2. PowerCenter 7.x to PowerCenter 8.1.1 Repository Size Increase
PowerCenter 7.x Percentage Increase

Repository Size in PowerCenter 8.1.1
< 1 MB 40%
< 10 MB 6%
> 10 MB 3%
You may need to increase the size of the database or add more disk space. Informatica
recommends that you allocate up to approximately 50 percent more available disk space and
temporary storage space in the database, depending on the version you upgrade from.
Overview 403
Using the Upgrade Wizard
You use the Upgrade Wizard if you upgrade from PowerCenter 6.x or 7.x. The Upgrade
Wizard uses the existing parameters, including repository database connection information,
in the Repository Agent configuration file to create a Repository Service. It uses the existing
parameters in the PowerCenter Server configuration file and the associated PowerCenter
repository to create an Integration Service. Upgrade configuration files to application services
in PowerCenter 8.1.1 to preserve existing server settings and configuration parameters.
You can upgrade multiple Repository Agent configuration files, repositories, and PowerCenter
Server configuration files sequentially. After the upgrade, the PowerCenter domain contains
the new Repository Services and Integration Services created during the upgrade.
Note: You must have permission on the domain or any folder to use the Upgrade Wizard. If
you have permission on a folder, you can upgrade one configuration file at a time. For more
information about domain users and permissions, see “Managing Users and User Accounts” in
the PowerCenter Administrator Guide.
Troubleshooting a PowerCenter 6.x / 7.x Upgrade

The Upgrade Wizard writes upgrade log events to the service logs and writes the status of the
upgrade to the Upgrade Wizard window and the service logs. You can use the status and log
events in the Upgrade Wizard window and the Log Viewer to troubleshoot issues that occur
during an upgrade. The Upgrade Wizard allows you to correct errors and continue the
upgrade without restarting the upgrade process from the beginning.
To access the log events in the Log Viewer, you can choose to view the activity log from the
Upgrade Wizard. You can also click the Log tab in the main Administration Console window
to view log events. If you view log events in the Log Viewer, you can return to the Upgrade
Wizard without losing the current upgrade progress.
For example, the Upgrade Wizard reports that the content upgrade failed. You can view the
log events for the repository upgrade to determine the exact cause of the failure. After fixing
the error, you can restart the upgrade from the last point of failure. In this example, the
upgrade would start from the repository contents upgrade.
Note: During repository content upgrade, there may be a delay between the time that the
upgrade process generates a log event and the time that the log event appears in the Log
Viewer. This delay may be up to several minutes. You can refresh the query in the Log Viewer
to see the log event.
For more information about troubleshooting errors in the Upgrade Wizard, see the
appropriate Upgrade Wizard step. For more information about the errors during the upgrade
process, see “PCSF Messages” in the PowerCenter Troubleshooting Guide.

Rules and Guidelines for Running the Upgrade Wizard
Use the following rules and guidelines when you upgrade PowerCenter with the Upgrade
Wizard:
♦ The Upgrade Wizard maintains the state of the upgrade during the upgrade process. You
can return to any previous step in the Upgrade Wizard to restart an upgrade of a
Repository Agent or PowerCenter Server configuration. If you close the browser or click
Finish Upgrade in the Upgrade Wizard, the previous state of the upgrade is lost and you
must restart the upgrade process.
♦ You must upgrade the contents for a global repository before you upgrade the contents for
any registered local repository. You must also upgrade the contents for a repository before
you can upgrade the PowerCenter Server for that repository.
♦ If you want to change an option after you upgrade a Repository Agent or PowerCenter
Server, you must reconfigure the Repository Service or Integration Service in the
♦ When you restart an upgrade for a Repository Agent or PowerCenter Server, the Upgrade
Wizard restarts the upgrade from the point of failure. To restart the upgrade at Repository
Service creation, you must exit the wizard, remove the Repository Service, and restart the
upgrade process.
♦ You can continue to a subsequent step in the Upgrade Wizard even though some upgrade
activities fail during the previous step. For example, you upgrade two Repository Agents
and two PowerCenter Servers. If one Repository Agent upgrade fails and one succeeds, you
can continue to the next step to upgrade the associated PowerCenter Server for the
successful Repository Agent upgrade.
♦ The Upgrade Wizard reads a configuration file during validation only. If an upgrade fails
because of an error in a configuration file, you must revalidate the configuration file before
you continue with the upgrade.
Overview 405
Validate Configuration Files
Step 1. Versions 6.x / 7.x
To start the upgrade process, select the Repository Agent and PowerCenter Server
configuration files you want to upgrade in the Select Configuration Files page of the Upgrade
Wizard. You can select the configuration files individually or select multiple configuration
files. After you select the configuration files to upgrade, fetch, and validate the files.
When the wizard validates the files, it checks the configuration files for the required
parameters and verifies that the name of the Repository Agent or PowerCenter Server
configuration does not currently exist in the domain. The validation fails if the configuration
file does not meet either of the conditions.
Note: If you want to upgrade multiple files, you must copy the configuration files to a node in
the PowerCenter 8.1.1 domain before you validate the files. For more information, see
“Backing Up and Copying Configuration Files” on page 89.
To select and validate configuration files:
1. Log in to the Administration Console.

For instructions to log in to the Administration Console, see “Logging in to the
Administration Console” on page 547.
2. In the Administration Console, click the Upgrade tab.
The Select Configuration Files page appears.
3. To select a single configuration file:

♦ Click Browse under Configuration File Location.

♦ Select a configuration file.
♦ Select the type of configuration file:
File Type Description
Global Repository Configuration file for a global repository.
Local Repository Configuration file for a local repository. If the local repository is registered to a global
repository, you must upgrade the global repository first.
PowerCenter Server Configuration file for a PowerCenter Server.
4. To select multiple configuration files, select the node where you copied the configuration
files.
5. Click Validate Files.
The Upgrade Wizard reads and validates the configuration files. If a configuration file is
invalid, correct the error and validate the files again. For more information about
troubleshooting validation errors, see “Troubleshooting Configuration File Validation”
on page 407.
6. If the file is valid, click Proceed to Step 2: Upgrade Global Repository.
Troubleshooting Configuration File Validation

You must successfully validate a Repository Agent or PowerCenter Server configuration file
before you can upgrade it to a Repository Service or Integration Service. A configuration file
may fail validation for the following reasons:
♦ Missing required parameters. A configuration file must contain a minimum number of
parameters to be upgraded to a Repository Service or Integration Service. If a
configuration file is missing a required parameter, correct the error in the configuration file
and validate the file again.
Validate Configuration Files 407

Table 18-3 describes the required parameters for Repository Agent and PowerCenter
Server configuration files:
Table 18-3. Required Configuration File Parameters
Configuration File Type Required Parameters
Repository Agent RepositoryName

DatabaseType
ConnectString
DBUser
DBPassword
PowerCenter Server ServerName

RepositoryName
PMUser
PMPassword
♦ Application service with the same name exists. You cannot upgrade a Repository Agent or
PowerCenter Server configuration if a Repository Service or Integration Service with the
same name exists in the domain. If an application service with the same name exists in the
domain, remove the application service from the domain and revalidate the configuration
files.

Upgrade a Global Repository
You can upgrade a Repository Agent configuration for a global repository, enable the
Repository Service created by the Upgrade Wizard, and then upgrade the contents of the
global repository. The Upgrade Wizard can upgrade multiple global repositories during this
step. If you do not have a global repository in your repository domain, skip this step.
The Upgrade Wizard displays the results of the upgrade after the Repository Service has been
created and enabled and the repository contents upgraded. You can view the status of the
Repository Agent upgrade and the repository contents upgrade in the Log Viewer during and
after the upgrade.
Figure 18-1 shows the Upgrade Global Repository page:
Figure 18-1. Upgrade Wizard - Upgrade Global Repository Page
Start upgrade.
Upgrade a Global Repository 409

To upgrade a global repository:
1. Configure the global repository upgrade options for each global Repository Agent
configuration file you want to upgrade.
Table 18-4 describes the global repository upgrade options:
Table 18-4. Upgrade Global Repository Options
Required/
Option Name Description
Optional
License Required Name of the license you want to assign to the Repository Service. You
must assign a license to enable the Repository Service.
Node Required Name of the node that runs the Repository Service.
Location Required Name of the folder in the domain that contains the Repository Service
object. Click Select Folder to change the folder.
Enable the Repository Optional Enables the Repository Service after upgrading the Repository Agent
Service after Upgrade configuration to a Repository Service. You must enable the Repository
Service to upgrade repository contents.
Upgrade Contents Optional Upgrades the repository contents after enabling the Repository
Service. You must upgrade repository contents before upgrading a local
repository registered to the global repository or before upgrading the
PowerCenter Server to which the global repository is associated.
Repository User Name Optional User name of database user account used to create the repository
database.
Password Optional Password for the database user account.
2. Click Start Upgrade.

The Upgrade Wizard begins the upgrade process. Upgrade Status shows the number of
failed, successful, and in-progress Repository Agent upgrades.
3. To view the upgrade activity, click View Activity Log for Upgrade Contents.
4. If the upgrade fails, correct the errors indicated under Upgrade Status and click Restart
Upgrade. The upgrade continues from the point of failure.
For more information about troubleshooting errors that occur during a Repository Agent
upgrade, see “Troubleshooting Creating and Enabling a Repository Service” on page 411
and “Troubleshooting a Repository Upgrade” on page 411.
5. If the upgrade succeeds, the Upgrade Wizard displays the following message for each
global repository:
<repository name> Upgrade Status: Upgrade Complete
6. Click Proceed to Step 3: Upgrade Local Repository.

Troubleshooting Creating and Enabling a Repository Service
An error can occur when the Upgrade Wizard creates the Repository Service for a global or
local repository or when the Upgrade Wizard enables the Repository Service in the domain.
The Upgrade Wizard must successfully create and enable a Repository Service to perform an
upgrade of the repository contents.
The actions necessary to troubleshoot issues related to the Repository Service depend on the
point at which the upgrade activity failed:
♦ Creating a Repository Service. If the Upgrade Wizard cannot create the Repository
Service, correct the error indicated in the Upgrade Status section of the Upgrade Wizard
and restart the upgrade.
If the upgrade error was caused by the Repository Agent configuration file, you must
revalidate the configuration file after fixing the error. For example, the creation of a
Repository Service may fail if the configuration file passed validation but contains another
error not caught by the validation process. Correct the error in the configuration file,
revalidate the configuration file, and then proceed to the appropriate repository upgrade
step. To revalidate the configuration file, see “Validate Configuration Files” on page 406.
♦ Enabling a Repository Service. If the Upgrade Wizard could not enable the Repository
Service, use the log events for the Repository Service in the Log Viewer to identify the
error. After you correct the error, enable the Repository Service in the Administration
Console and use the Actions list in the Administration Console to upgrade the contents
for the repository.
For more information about enabling a Repository Service, see “Managing the Repository”
in the PowerCenter Administrator Guide. For more information about upgrading
repository contents in the Administration Console, see “Upgrade the PowerCenter
Troubleshooting a Repository Upgrade

The repository upgrade process stops if the Upgrade Wizard or the Administration Console
encounters problems during the upgrade, such as lack of disk space. The most common
reasons an upgrade might fail are:
♦ The upgrade process has trouble reading or writing to the repository database.
♦ The repository database has insufficient disk space or temporary storage space.
♦ The client system has insufficient memory.
♦ The repository has inconsistent data.
For information about errors that occur when you upgrade a repository, see “REP Messages”
in the PowerCenter Troubleshooting Guide.
The Upgrade Wizard sends log events to the Log Manager when it performs the upgrade. You
can view the progress of the upgrade by viewing the log events for the upgrade in the Log
Viewer. The Administration Console lists the upgrade activities in the Administration
Console window. Use the Log Viewer or the Administration Console window to determine
the cause of a failure during a repository contents upgrade.
Upgrade a Global Repository 411

After you identify and fix the problem, restart the upgrade in the Upgrade Wizard or the
Administration Console. When you upgrade the repository the second time, the upgrade
process starts at the last successful version number. For example, if the upgrade fails between
version 175 and 176, the upgrade process starts at version 175 when you run upgrade the
second time. However, you should always maintain a copy of the original repository in case
you need to start the upgrade from the beginning.
Note: Depending on the size of the repository, the upgrade process may take several hours to
several days to complete.

Upgrade a Local Repository
You can upgrade a Repository Agent configuration for a local repository, enable the
Repository Service created by the Upgrade Wizard, and then upgrade the contents of the local
repository. The Upgrade Wizard can upgrade multiple local repositories during this step.
The Upgrade Wizard displays the results of the upgrade after the Repository Service is created
and enabled and the repository contents are upgraded. You can view the status of the
Repository Agent upgrade and the repository contents upgrade in the Log Viewer during and
after the upgrade.
Figure 18-2 shows the Upgrade Local Repository page:
Figure 18-2. Upgrade Wizard - Upgrade Local Repository Page
Start upgrade.
Upgrade a Local Repository 413

To upgrade a local repository:
1. Configure the local repository upgrade options for each global Repository Agent
configuration file you want to upgrade.
Table 18-5 describes the local repository upgrade options:
Table 18-5. Upgrade Local Repository Options
Required/
Option Name Description
Optional
License Required Name of the license you want to assign to the Repository Service. You
must assign a license to enable the Repository Service.
object. Click Select Folder to change the folder.
Enable the Repository Optional Enables the Repository Service after upgrading the Repository Agent
Service After Upgrade configuration to a Repository Service. You must enable the Repository
Service to upgrade repository contents.
Upgrade Contents Optional Upgrades the repository contents after enabling the Repository
Service. You must upgrade repository contents before upgrading the
PowerCenter Server to which the local repository is associated.
Repository User Name Optional User name of database user account used to create the repository
database.
Domain for Global Optional PowerCenter domain that contains the Repository Service for the
Repository global repository. You can also choose Manage Domain List to select a
global repository in a different domain.
Global Repository Optional Name of the Repository Service for the global repository.
Global Repository User Optional User name of database user account used to create the repository
Name database.

The Upgrade Wizard begins the upgrade process. The upgrade status shows the number
of failed, successful, and in-progress Repository Agent upgrades.
3. To view the upgrade activity, click View Activity Log for Upgrade Contents.
4. If the upgrade fails, correct the errors indicated under Upgrade status and click Restart
Upgrade. The upgrade continues from the point of failure.
For more information about troubleshooting errors that occur during a Repository Agent
upgrade, see “Troubleshooting Creating and Enabling a Repository Service” on page 411
and “Troubleshooting a Repository Upgrade” on page 411.

5. If the upgrade succeeds, the Upgrade Wizard displays the following message for each local
repository:
<repository name> Upgrade Status: Upgrade Complete
6. Click Proceed to Step 4: Upgrade PowerCenter Server.
Upgrade a Local Repository 415

Upgrade the PowerCenter Server
You can upgrade a PowerCenter Server configuration to an Integration Service and enable the
Integration Service in the domain. The Upgrade Wizard can upgrade a PowerCenter Server
configuration during this step. You must upgrade the contents for the associated repository
for the PowerCenter Server before you can upgrade the PowerCenter Server.
The Upgrade Wizard displays the results of the upgrade after the Integration Service has been
created and enabled. You can view the status of the PowerCenter Server upgrade in the Log
Viewer during and after the upgrade.
Figure 18-3 shows the Upgrade PowerCenter Server page:
Figure 18-3. Upgrade Wizard - Upgrade PowerCenter Server Page
Duplicate settings for Configure Integration Upgrade all Integration Upgrade one
all Integration Services. Service options. Services. Integration Service.

To upgrade a PowerCenter Server configuration:
1. Configure the Integration Service options for the first listed Integration Service.
Table 18-6 describes the Integration Service upgrade options:
Table 18-6. Integration Service Upgrade Options
Required/
Option Description
Optional
Domain for Associated Required Name of the domain that contains the associated Repository Service
Repository Service for the Integration Service. You can choose Manage Domain List to
choose a Repository Service in another domain.
Associated Repository Required Name of the associated Repository Service. You must upgrade a
Service Repository Service and the repository contents or create the
Repository Service in the domain before you can choose a Repository
Service.
License Required Name of the license you want to assign to the Integration Service. You
must assign a license to enable the Integration Service.
object.
Default folder is the top-level folder for the domain. Click Select Folder
to change the folder.
Enable Integration Optional Enables the Integration Service after upgrade.

Service After Upgrade
2. If you want all Integration Services to inherit the same configuration, click Apply
Settings to All Integration Services.
3. To upgrade a single PowerCenter Server, click Start Upgrade.
The Upgrade Wizard begins the upgrade process. Upgrade Status shows the number of
failed, successful, and in-progress PowerCenter Server upgrades.
4. To upgrade all PowerCenter Servers simultaneously, click Start Upgrade for All
Integration Services.
The Upgrade Wizard begins the upgrade process for all PowerCenter Servers. Upgrade
Status shows the number of failed, successful, and in-progress PowerCenter Server
upgrades.
5. To view the upgrade activity, click View Log for Upgrade Service.
6. If the upgrade fails, correct the errors indicated under Upgrade Status and click Restart
Upgrade. The upgrade continues from the last point of failure.
For more information about troubleshooting errors that occur during a PowerCenter
Server upgrade, see “Troubleshooting Creating and Enabling an Integration Service” on
page 418.
Upgrade the PowerCenter Server 417

7. If the upgrade succeeds, the Upgrade Wizard displays the following message for each
PowerCenter Server:
<Integration Service name> Upgrade Status: Upgrade Complete
8. Click Proceed to Step 5: Upgrade Summary.
Troubleshooting Creating and Enabling an Integration Service

An error can occur when the Upgrade Wizard creates the Integration Service from a
PowerCenter Server configuration file or when the Upgrade Wizard enables the Integration
Service in the domain.
The actions necessary to troubleshoot issues related to the Integration Service depend on the
point at which the upgrade failed:
♦ Creating an Integration Service fails. If the Upgrade Wizard could not create the
Integration Service, correct the error indicated in the Upgrade Status section of the
Upgrade Wizard and restart the upgrade.
If the upgrade error was caused by the PowerCenter Server configuration file, you must
revalidate the configuration file after fixing the error. For example, the creation of a
Integration Service may fail if the configuration file passed validation but contains another
error not caught by the validation process. Correct the error in the configuration file and
revalidate it. Then proceed to the Upgrade PowerCenter Server step. For information
about validating the configuration file, see “Validate Configuration Files” on page 406.
♦ Enabling an Integration Service fails. If the Upgrade Wizard could not enable the
Integration Service, use the log events for the Integration Service in the Log Viewer to
identify the error. After you correct the error, enable the Integration Service in the
For more information about enabling an Integration Service, see “Creating and
Configuring the Integration Service” in the PowerCenter Administrator Guide.

View Upgrade Results
View the results of all upgrade activities on the summary page. The summary page contains
upgrade information for the following components:
♦ Repository Services. Includes the name of the Repository Agent configuration file, the
name of the Repository Service, and the results of the upgrade service, enable service, and
upgrade contents actions.
♦ Integration Services. Includes the name of the PowerCenter Server configuration file, the
name of the Integration Service, and the results of the create service and enable service
actions.
Figure 18-4 shows the Upgrade Summary page for an upgrade:
Figure 18-4. Upgrade Wizard - Upgrade Summary Page
After you review the upgrade summary, click Finish Upgrade to complete the upgrade process
or close the browser. After you click Finish Upgrade or close the browser, you must restart the
upgrade process to correct errors that occurred during the upgrade process.
View Upgrade Results 419

Upgrade Domain and Node Metadata
Step 1. Version 8.0
When you upgrade PowerCenter 8.0, you use infaupgrade to upgrade the domain and node
metadata. In PowerCenter 8.1.1, the domain metadata is stored in a domain configuration
database. The node metadata is stored in the domain configuration database and
nodemeta.xml on nodes in the domain. Use infaupgrade to upgrade the existing metadata in
the domainmeta.xml and nodemeta.xml files to the appropriate location in a PowerCenter
8.1.1 domain.
Complete the following tasks to upgrade a PowerCenter 8.0 domain with infaupgrade:
1. Run upgradeGatewayNode on each gateway node in the domain to upgrade
nodemeta.xml for the gateway nodes. For more information, see “Step 1. Upgrade
Gateway Node Metadata” on page 421.
2. Run upgradeDomain on the master gateway node in the domain to upgrade the metadata
in domainmeta.xml to the domain configuration database. For more information, see
“Step 2. Upgrade Domain Metadata” on page 421.
3. Run upgradeWorkerNode on each worker node in the domain to upgrade nodemeta.xml
for the worker nodes in the domain. For more information, see “Step 3. Upgrade Worker
Node Metadata” on page 422.
4. After you run infaupgrade, copy domains.infa from the backup location to the installation
directory on each node in the domain and start Informatica Services on each node in the
domain.
Note: Do not upgrade the gateway node if you did not install PowerCenter Services on all the
nodes in the PowerCenter 8.0 domain. If you upgrade the gateway node before installing
PowerCenter Services on the non-gateway nodes in the domain, the infaupgrade fails because
the node names already exist in the domain.
Running Commands
You invoke infaupgrade from the command line. On Windows, infaupgrade is a batch file with
a .bat extension. On UNIX, infaupgrade is a script file with a .sh extension.
To run infaupgrade commands:
1. At the command prompt, change to the directory where infaupgrade is located.

By default, infaupgrade installs in the server directory.
2. Enter infaupgrade followed by the command name and its required options and
arguments.
3. At the command prompt, type the following command to run infaupgrade:
infaupgrade(.sh) command_name [-option1] argument_1 [-option2]
argument_2...

Step 1. Upgrade Gateway Node Metadata
Use the infaupgrade upgradeGatewayNode command to upgrade the metadata for a gateway
node in a domain.
The upgradeGatewayNode command uses the following syntax:
upgradeGatewayNode
<-databaseaddress|-da> database_hostname:database_port
<-databaseusername|-du> database_username
<-databasepassword|-dp> database_password
<-databasetype|-dt> database_type
[<-databaseservicename|-ds> database_service_name]
<-nodeconfigfile|-nf> node_configuration_file
Table 18-7 describes infaupgrade upgradeGatewayNode options and arguments:
Table 18-7. upgradeGatewayNode Options and Arguments
Required/
Option Argument Description
Optional
-databaseaddress database_hostname: Required Name and port number of the machine hosting
-da port the domain configuration database.
-databaseusername database_username Required Account for the database containing the

-du domain configuration information.
-databasepassword database_password Required Domain configuration database password

-dp corresponding to the database user. Must be in
7-bit ASCII.
-databasetype database_type Required Type of database that stores the domain

-dt configuration metadata. Options are
MSSQLSERVER, DB2, ORACLE, and
SYBASE.
-databaseservicename database_service_name Conditional The database service name.

-ds Required for Oracle and DB2 databases. Enter
the SID for Oracle or the service name for
DB2.
-nodeconfigfile node_configuration_file Required Path and name of the gateway node

-nf configuration file from the PowerCenter 8.0
domain.
Step 2. Upgrade Domain Metadata

Use the infaupgrade upgradeDomain command to upgrade the metadata for a domain and
store it in the domain configuration database.
The upgradeDomain command uses the following syntax:
upgradeDomain
<-databaseaddress|-da> database_hostname:database_port
<-databaseusername|-du> database_username
<-databasepassword|-dp> database_password
<-databasetype|-dt> database_type
Upgrade Domain and Node Metadata 421

[<-databaseservicename|-ds> database_service_name]
<-domainconfig|-dc> domain_config_file
[<-force|-f>]
Table 18-8 describes infaupgrade upgradeDomain options and arguments:
Table 18-8. upgradeDomain Options and Arguments
Required/
Optional
-databaseaddress database_hostname: Required Name and port number of the machine hosting
-da database_port the domain configuration database.
-databaseusername database_username Required Account for the database containing the

-du domain configuration information.
-databasepassword database_password Required Domain configuration database password

-dp corresponding to the database user. Must be
in 7-bit ASCII.
-databasetype database_type Required Type of database that stores the domain

-dt configuration metadata. Options are
MSSQLSERVER, DB2, ORACLE, and
SYBASE.
-databaseservicename database_service_name Conditional The database service name.

-ds Required for Oracle and DB2 databases. Enter
the SID for Oracle or the service name for
DB2.
-domainconfig domain_config_file Required Path and name of the domain configuration file
-dc from the PowerCenter 8.0 domain.
-force n/a Conditional Overwrites an existing domain configuration in

-f a domain configuration database. Use this if
you installed PowerCenter Services and
created a temporary domain.
Step 3. Upgrade Worker Node Metadata

Use the infaupgrade upgradeWorkerNode command to upgrade the node metadata for a
worker node in a domain.
The upgradeWorkerNode command uses the following syntax:
upgradeWorkerNode
<-nodeconfigfile|-nf> node_configuration_file

Table 18-9 describes infaupgrade upgradeWorkerNode options and arguments:
Table 18-9. upgradeWorkerNode Option and Argument
Required/
Optional
-nodeconfigfile node_configuration_file Required Path and name of the worker node

-nf configuration file from the PowerCenter 8.0
domain.
Upgrade Domain and Node Metadata 423

Upgrade the PowerCenter Repository
Step 2. Version 8.0
You can upgrade a repository using the Administration Console if you upgrade from 8.0 and
did not use the Upgrade Wizard or you upgrade from PowerCenter 6.x or 7.x and the
Upgrade Wizard did not successfully enable the Repository Service for the repository.
A Repository Service runs in exclusive mode until you upgrade the repository contents. After
you upgrade the contents, the Repository Service runs in normal mode.
You must create a Repository Service for the repository before you upgrade the repository
contents. For more information about creating a Repository Service, see “Creating and
Configuring the Repository Service” in the PowerCenter Administrator Guide.
For more information about changes the upgrade process makes to the functionality of
existing metadata, see the PowerCenter Post-Upgrade Reference.
To upgrade a repository:
1. Log in to the Administration Console. For information about logging in to the

Administration Console, see “Logging in to the Administration Console” on page 547.
2. In the Navigator, select the Repository Service for the repository you want to upgrade.
The page displays the existing repository and data version and the current repository and
data version.

3. In the Actions list, select Upgrade Contents.
4. Enter the repository administrator user name and password and click OK.
The activity log displays the results of the upgrade operation.
If the upgrade operation fails, view the error messages in the activity log to identify the
problem. After you fix the problem, upgrade the repository again. For more information, see
“Troubleshooting a Repository Upgrade” on page 411.
Upgrade the PowerCenter Repository 425

Upgrade the PowerCenter Client
Step 3. Version 8.0
Step 1. Version 8.1
You can run the PowerCenter Client installer to upgrade the PowerCenter Client. You can
install the complete version of the PowerCenter Client tools or a custom version, depending
on your license. When you install the PowerCenter Client, you install the following
PowerCenter Client tools and components:
♦ PowerCenter Client tools. A set of tools you can use to manage the PowerCenter
repository, mappings, and sessions.
♦ Metadata Manager Client. A set of applications you can use to configure Metadata
Manager and manage metadata.
♦ DataDirect 5.1 ODBC drivers. Drivers designed for PowerCenter to connect the
PowerCenter Client to data sources and targets. The Metadata Manager Client uses
ODBC for connections to the Metadata Manager repository and PowerCenter repository.
♦ Java Runtime Environment. The Java transformation, PowerCenter Connect for JMS, and
PowerCenter Connect for webMethods require the JRE.
The PowerCenter Client installer installs DataDirect 5.1 ODBC drivers. If you upgrade from
PowerCenter 6.x or 7.x, you must recreate ODBC connections to use the new drivers.
For more information, see “Connecting to Databases from Windows” on page 487.

Upgrade Data Profiling
Step 8. Version 7.x
Step 4. Version 8.0
Step 2. Version 8.1
When you upgrade PowerCenter, you must upgrade Data Profiling. Depending on the version
of PowerCenter you upgrade, you backup, restore, and upgrade the Data Profiling warehouse.
If you use Data Analyzer Data Profiling reports, you must also update the warehouse schema
and views to include the new PowerCenter 8.1.1 Data Profiling reports.
Complete the following tasks to upgrade Data Profiling from PowerCenter 7.x or 8.0:
1. Backup and restore the Data Profiling warehouse.
2. Upgrade the Data Profiling warehouse.
3. Upgrade schema and views for Data Analyzer Data Profiling reports (Optional).
4. Recreate ODBC connections (Optional).
If you upgrade from PowerCenter 8.1, you only update the Data Profiling warehouse schema
and views for Data Analyzer Data Profiling reports. You do not upgrade the Data Profiling
warehouse.
Running Data Profiling Upgrade Scripts

When you upgrade the Data Profiling warehouse and the schemas and views, you run scripts
against the Data Profiling warehouse.
Table 18-10 describes the procedure to run the upgrade scripts on each database:
Table 18-10. Procedure for Upgrading a Data Profiling Warehouse to PowerCenter 8.1.1
Database Type To run the upgrade scripts:
IBM DB2 UDB Connect to DB2. Run the following command:

db2 -tvf <upgrade script name>
Informix Run the dbaccess command line program. Select the script and select Run.
Microsoft SQL Server Run the upgrade schema script with Query Analyzer.
Note: Do not use isql to run the script. The script may not run successfully.
Oracle Run the following command from the command line :

sqlplus <user name>/<password>@<database server>
@<upgrade script name>
Sybase ASE Run the following command from the command line:
isql -U <user name> -P <password> -S <database server>
-i <upgrade schema script>
Teradata Open Teradata SQL Assistant. Open the upgrade schema script and click Execute.
Note: The upgrade script fails if you use the Execute Parallel option in Teradata Client 6.2.
Upgrade Data Profiling 427

Step 1. Prepare the Data Profiling Warehouse
Set up another database for the Data Profiling warehouse. Use the database backup utility to
back up the Data Profiling warehouse and the existing data profile results. Restore the backup
to the new database.
Step 2. Upgrade the Data Profiling Warehouse

To upgrade a Data Profiling warehouse, run a script to upgrade the warehouse schema. The
script you run depends on the database type and the version of PowerCenter you upgrade.
When you install PowerCenter, the installer places the script in the following directory:
<PowerCenter Client>\bin\Extensions\DataProfile\ProfileWarehouse
Table 18-11 describes the script you must run for each database type and PowerCenter
version:
Table 18-11. Scripts for Upgrading the Data Profiling Warehouse to PowerCenter 8.1.1
Existing Warehouse Database Type Script
8.0 IBM DB2 UDB upgrade_schema04-05_db2.sql
8.0 Informix upgrade_schema04-05_inf.sql
8.0 Microsoft SQL Server upgrade_schema04-05_sql.sql
8.0 Oracle upgrade_schema04-05_ora.sql
8.0 Sybase ASE upgrade_schema04-05_syb.sql
8.0 Teradata upgrade_schema04-05_ter.sql
7.1.1 / 7.1.2 / 7.1.3 / 7.1.4 IBM DB2 UDB upgrade_schema03-05_db2.sql
7.1.1 / 7.1.2 / 7.1.3 / 7.1.4 Informix upgrade_schema03-05_inf.sql
7.1.1 / 7.1.2 / 7.1.3 / 7.1.4 Microsoft SQL Server upgrade_schema03-05_sql.sql
7.1.1 / 7.1.2 / 7.1.3 / 7.1.4 Oracle upgrade_schema03-05_ora.sql
7.1.1 / 7.1.2 / 7.1.3 / 7.1.4 Sybase ASE upgrade_schema03-05_syb.sql
7.1.1 / 7.1.2 / 7.1.3 / 7.1.4 Teradata upgrade_schema03-05_ter.sql
7.1.0 IBM DB2 UDB upgrade_schema02-05_db2.sql
7.1.0 Informix upgrade_schema02-05_inf.sql
7.1.0 Microsoft SQL Server upgrade_schema02-05_sql.sql
7.1.0 Oracle upgrade_schema02-05_ora.sql
7.1.0 Sybase ASE upgrade_schema02-05_syb.sql
7.1.0 Teradata upgrade_schema02-05_ter.sql
7.0 IBM DB2 UDB upgrade_schema01-05_db2.sql
7.0 Informix upgrade_schema01-05_inf.sql

Table 18-11. Scripts for Upgrading the Data Profiling Warehouse to PowerCenter 8.1.1
Existing Warehouse Database Type Script
7.0 Microsoft SQL Server upgrade_schema01-05_sql.sql
7.0 Oracle upgrade_schema01-05_ora.sql
7.0 Sybase ASE upgrade_schema01-05_syb.sql
7.0 Teradata upgrade_schema01-05_ter.sql
Step 3. Upgrade Schema and Views for Data Analyzer

Data Profiling Reports (Optional)
If you want to view Data Analyzer Data Profiling reports, you must upgrade the Data
Profiling warehouse schema and views. You upgrade the Data Profiling warehouse views for
Data Analyzer reports after you upgrade the Data Profiling schema. The scripts to upgrade
the schema and views have the same name. You must upgrade the schema before you upgrade
the views.
The scripts to upgrade the schema are located in the following PowerCenter Client directory:
\bin\Extensions\DataProfile\ProfileWarehouse\DA811
The scripts to upgrade the views are located in the following PowerCenter Client directory:
\bin\Extensions\DataProfile\ProfileWarehouse\DA811\DAViews
Table 18-12 describes the scripts you must run for each Data Profiling warehouse database
type:
Table 18-12. Scripts for Upgrading the Data Profiling Warehouse Schema and Views
Database Type Script
IBM DB2 UDB upgrade_05_db2.sql
Microsoft SQL Server upgrade_05_sql.sql
Oracle upgrade_05_ora.sql
Sybase ASE upgrade_05_syb.sql
Teradata upgrade_05_ter.sql
After you upgrade the views and schema, you can install the new Data Analyzer Data Profiling
reports. For more information about installing reports, see “PowerCenter Reports
Installation” on page 281.
Upgrade Data Profiling 429

Step 4. Recreate the ODBC Connection to the Data Profiling
Warehouse (Optional)
PowerCenter 8.1.1 includes DataDirect 5.1 ODBC drivers. If the existing PowerCenter
Client connection to the Data Profiling warehouse was created with an earlier version of the
drivers, you must recreate the ODBC connection to each Data Profiling warehouse.

Chapter 19
Upgrading Data Analyzer

♦ Overview, 432
♦ Run the Repository Upgrade Utility, 433
♦ Update Configuration Files, 436
♦ Complete the Repository Upgrade, 437
431
Overview
To upgrade Data Analyzer, you must first install the new version of Data Analyzer. Then use
the Repository Upgrade utility provided with the new version of Data Analyzer to upgrade the
repository of the previous version. After you upgrade the repository, you log in to Data
Analyzer to complete the repository upgrade.
Previous versions of Data Analyzer were named PowerAnalyzer. You can upgrade any version
of PowerAnalyzer 4.1.1 and later to Data Analyzer 8.1.1, and you can upgrade Data Analyzer
8.0 and 8.1 to Data Analyzer 8.1.1.
To upgrade the Data Analyzer repository, complete the following steps:
1. Run the Repository Upgrade utility. Run the Repository Upgrade utility to upgrade the
Data Analyzer repository. For more information, see “Run the Repository Upgrade
Utility” on page 433.
2. Update the configuration files. Update any customized configuration files in the Data
Analyzer 8.1.1 instance. For more information, see “Update Configuration Files” on
page 436.
3. Log in to Data Analyzer and complete the repository upgrade. The repository upgrade
requires you to log in to Data Analyzer to complete the upgrade process. You may need to
increase the transaction timeout for the application server to allow the upgrade to
complete. For more information, see “Complete the Repository Upgrade” on page 437.
432 Chapter 19: Upgrading Data Analyzer

Run the Repository Upgrade Utility
On Windows, open a command window and run the upgrade batch file. On UNIX, run the
upgrade script as a shell command.
If you are upgrading an IBM DB2 repository, you must increase the value of the
DynamicSections property of the JDBC driver to ensure that you have enough resources to
complete the upgrade process. Changing the value of the DynamicSections property requires
database administrator privileges. Therefore, the user account that you use to connect to the
DB2 repository database through the Repository Upgrade utility must have database
administrator privileges, including Grant Package Creation privileges.
To run the Repository Upgrade utility:
1. Complete the pre-upgrade tasks. For more information about the pre-upgrade tasks, see
“Data Analyzer Pre-Upgrade Steps” on page 93.
2. On the machine where you installed Data Analyzer, navigate to the Data Analyzer
utilities directory.
The upgrade utility is installed in the default Data Analyzer utilities directory:
/Informatica/PowerCenter8.1.1/DataAnalyzer/upgradeutil
3. Start the Repository Upgrade utility.

On Windows, start the upgrade utility with the following command:
upgrade.bat
On UNIX, use the following command:

upgrade.sh
The Upgrade PowerCenter Data Analyzer Repository window appears.
Run the Repository Upgrade Utility 433

4. Select the database type of the Data Analyzer repository to upgrade.
The Repository Upgrade utility displays the driver name and the JDBC connection string
syntax for the selected database type.
5. Customize the JDBC connection string for the repository database you want to upgrade.
Note: For an IBM DB2 repository, you must set the JDBC connection string with
additional parameters:
CreateDefaultPackage=TRUE
ReplacePackage=TRUE
DynamicSections=1000
For example, use the following syntax for the connection string to upgrade an IBM DB2
repository:
jdbc:informatica:db2://
host_name:port;DatabaseName=database_name;CreateDefaultPackage=TRUE;
ReplacePackage=TRUE;DynamicSections=1000
6. Enter the user name and password to connect to the Data Analyzer repository database.
Note: For an IBM DB2 repository, the user account must have database administrator
privileges.
7. To ensure that you can connect to the database, click Test Connection.
If an error message displays, verify that the connection information for the database is
correct. Data Analyzer provides the reason for the connection failure. If necessary, check
with the database administrator to resolve any problem.
Note: For an IBM DB2 repository, click Test Connection to ensure that the
DynamicSections property is set to the correct value. After you click Test Connection,
remove the extra parameters from the JDBC connection string so that the

DynamicSections property is not set a second time. Change the connection string to the
default string for a DB2 database connection:
jdbc:informatica:db2://host_name:port;DatabaseName=database_name

The Repository Upgrade utility displays a warning to back up the repository before you
upgrade.
9. Click OK to continue the upgrade.
10. Select the locale you want to use and click OK.
11. Select whether you want to use Smart Sum for all custom metrics.
Select Yes if you enabled this feature in PowerAnalyzer 4.x. Select No if you did not
enable this feature in PowerAnalyzer 4.x. Smart sum is enabled in PowerAnalyzer 4.x if
you set the CustomMetric.UseExpressionForSum property to True in the IAS.properties
file.
When you enable smart sum, Data Analyzer calculates the sum and average of custom
metrics by the base metrics used in the expression. For more information about custom
metrics, see the Data Analyzer User Guide and Schema Designer Guide.
The Repository Upgrade utility upgrades the selected Data Analyzer repository to the
latest version.
If the upgrade fails, Data Analyzer provides the reason for the upgrade failure. If
necessary, check with the database administrator to resolve any problem.
Data Analyzer writes the details of the upgrade process to an upgrade log called
IASUpgrade.log. You can find the upgrade log in the Repository Upgrade utility directory.
After the Repository Upgrade utility completes the upgrade procedure, log in to Data
Analyzer and review all dashboards, reports, and indicators to verify that they were upgraded
properly.
After you log in, allow Data Analyzer to complete the second phase of the upgrade.
Run the Repository Upgrade Utility 435

Update Configuration Files
After you run the Data Analyzer upgrade utility, update the configuration files in Data
Analyzer 8.1.1 to match the settings in the Data Analyzer configuration files you saved before
upgrading. Do not overwrite the Data Analyzer 8.1.1 configuration files with the saved Data
Analyzer configuration files.
Update the configuration files before you start Data Analyzer 8.1.1. If you do not update the
configuration settings before you start Data Analyzer 8.1.1, some of the initial settings in the
Data Analyzer 8.1.1 configuration files can change the objects in the repository and the
behavior of Data Analyzer.
In Data Analyzer 8.1.1 running on JBoss Application Server, use the EAR Repackager utility
to extract the ldaprealm.properties in the Data Analyzer EAR file. Update the configuration
file and then use the EAR Repackager utility to repackage the file back into the Data Analyzer
EAR file.
For more information about using the EAR Repackager utility to access the Data Analyzer
EAR file, see “Accessing the Data Analyzer EAR File” in the Data Analyzer Administrator
Guide.
For more information about the version changes to the Data Analyzer configuration files, see
“Data Analyzer” in the PowerCenter Post-Upgrade Reference.

Complete the Repository Upgrade
When you log in to Data Analyzer after you upgrade the repository, Data Analyzer initiates a
set of processes to complete the upgrade of dashboard objects.
In most cases, the additional upgrade processes complete quickly. Data Analyzer may take a
moment to display the objects on the View tab after you log in. Wait until Data Analyzer fully
displays the View tab before you continue working with Data Analyzer.
Increasing Transaction Timeout

In cases where the upgrade includes a large number of dashboard objects, Data Analyzer may
take a while to complete the additional upgrade processes. If Data Analyzer generates errors
before it completes the upgrade process, raise the transaction timeout in the application server
to provide more time for the process. The procedure to raise the transaction timeout varies for
each application server.
WebLogic Server
Use the WebLogic Administration Console to increase the transaction timeout for Data
Analyzer. For more information about configuring the Java Transactions API (JTA) for BEA
WebLogic Server, see the documentation on the BEA Systems web site:
http://e-docs.bea.com/wls/docs81/ConsoleHelp/jta.html#1112051
To increase the transaction timeout in WebLogic:
1. Start the WebLogic Administration Console and log in with the console system user
name and password.
2. On the left panel of the WebLogic Administration Console, click the name of the domain
for Data Analyzer.
The default WebLogic domain for Data Analyzer is Informatica.
3. On the right panel, click the JTA tab.
4. Set the Timeout Seconds property to a larger value.
By default, the timeout length is 30 seconds. Increase it to at least 300 seconds (5
minutes).
5. Click Apply.
6. Close the WebLogic Administration Console.
7. Restart BEA WebLogic Server.
When you log in to Data Analyzer, Data Analyzer can complete the upgrade process and
display the View tab without errors.
Complete the Repository Upgrade 437

Use the WebSphere Administrative Console to increase the transaction timeout. For more
information about transaction services for IBM WebSphere Application Server, see the
documentation on the IBM web site:
http://publib.boulder.ibm.com/infocenter/ws51help/index.jsp?topic=/
com.ibm.websphere.zseries.doc/info/zseries/ae/udat_contranserv.html
To increase the transaction timeout in WebSphere:
1. Start the WebSphere Administrative Console and log in with the console system user
name and password.
2. On the left panel of the WebSphere Administrative Console, click Servers > Application
Servers.
3. On the Application Servers page, click the name of the server associated with Data
Analyzer.
By default, the name of the server is server1.
4. In the Additional Properties section of the Configuration tab, click Transaction Services.
5. On the Transaction Services page, set the Total Transaction Lifetime Timeout to a larger
value.
By default, the timeout length is 120 seconds (2 minutes). Increase it to at least 300
seconds (5 minutes).
6. Click OK.
7. Save the configuration change and close the WebSphere Administrative Console.
8. Restart IBM WebSphere Application Server.

To increase the transaction time out in JBoss Application Server, update the
TransactionTimeout attribute for the TransactionManager in the transaction-service.xml
configuration file.
To increase the transaction timeout in JBoss:
1. Go to the JBoss deployment directory in the Data Analyzer server configuration.

If you install JBoss Application Server with Data Analyzer, the default deployment
directory is /Informatica/PowerCenter8.1.1/JBoss403/server/informatica/deploy.
2. Locate the transaction-service.xml configuration file.
Back up the transaction-service.xml file into another directory before you modify it. Do
not create the backup file in the /deploy directory.

3. Open the transaction-service.xml file with a text editor.
4. Locate the line with the following text:
TransactionManagerService
5. The transaction-service.xml file contains the following entry:

<mbean code="org.jboss.tm.TransactionManagerService"
name="jboss:service=TransactionManager">
<attribute name="TransactionTimeout">300</attribute>
<depends optional-attribute-name=
"XidFactory">jboss:service=XidFactory</depends>
</mbean>
Typically, the default transaction timeout for JBoss (5 minutes) is high enough for most
situations. However, if you still encounter problems, raise the timeout to 600 seconds (10
minutes).
6. Change the value for the TransactionTimeout attribute to a higher number.
7. Save and close the transaction-service.xml file.
Complete the Repository Upgrade 439

Chapter 20
Upgrading Metadata
Manager
♦ Overview, 442
♦ Running the Metadata Manager Upgrade Utility on Windows, 444
♦ Running the Metadata Manager Upgrade Utility on UNIX, 449
♦ Upgrading the Metadata Manager Client, 453
441
Overview
When you upgrade Metadata Manager, you update the Metadata Manager repository, objects
in the PowerCenter repository for Metadata Manager, Metadata Manager metamodels and
reports, and the Metadata Manager Client. You must upgrade Metadata Manager when you
install Metadata Manager 8.1.1. You can upgrade SuperGlue 2.1 and 2.2 and Metadata
Manager 8.0 and above to Metadata Manager 8.1.1.
To upgrade Metadata Manager, install the current version of Metadata Manager and run the
upgrade utility installed with Metadata Manager. You must run the upgrade utility on the
machine that has access to the Metadata Manager repository and the Metadata Manager
instance. In addition, the Repository Service for the associated PowerCenter repository for
Metadata Manager must be available.
The mode you run the utility in depends on the operating system where you installed
Metadata Manager:
♦ Windows. You can run the upgrade utility in graphical mode on Windows. For more
information, see “Running the Metadata Manager Upgrade Utility on Windows” on
page 444.
♦ UNIX. You can run the upgrade utility in console mode on UNIX. For more information,
see “Running the Metadata Manager Upgrade Utility on UNIX” on page 449.
When you install Metadata Manager, the PowerCenter installer configures the upgrade utility
settings based on the directories and options you select during installation and stores the
values from the installation in sg_upgrade.properties. The upgrade utility reads the values
from the configuration file when you run the utility. You can modify the settings if they do
not match the settings for the Metadata Manager components you want to upgrade.
After you run the upgrade utility and upgrade the Metadata Manager components, upgrade
the Metadata Manager Client. For more information, see “Upgrading the Metadata Manager
Client” on page 453.
Note: The PowerCenter repository for Metadata Manager you upgrade must be version 8.1.1.
You cannot upgrade a previous version of the repository.
Upgrade Process
When you run the upgrade utility, you can choose to upgrade repositories and metamodels
and reports. If you choose not to upgrade a component when you upgrade Metadata
Manager, you can run the utility again to upgrade the component. During the upgrade
process, you need to start or stop Metadata Manager, depending on the component you
upgrade:
♦ Repository. The utility upgrades objects in the Metadata Manager repository and updates
objects in the PowerCenter repository for Metadata Manager. You start the Metadata
Manager server before you upgrade the repositories.
♦ Metamodels and reports. The upgrade utility imports the latest version of the metamodels
and reports into the Metadata Manager. The Metadata Manager server must be running
442 Chapter 20: Upgrading Metadata Manager

when you import metamodels and reports. The utility will prompt you to start the
Metadata Manager server if it is not already running.
Note: The upgrade utility does not import the metamodels for a Metadata Manager repository
into an IBM DB2 database. You must manually import the metamodels for an IBM DB2
Metadata Manager repository. For more information about importing the metamodels, see
“Metadata Manager Post-Upgrade Tasks” on page 467.
Overview 443
Running the Metadata Manager Upgrade Utility on
Windows
On Windows, you start the graphical mode upgrade utility from the command line.
To run the Metadata Manager upgrade utility on Windows:
1. Stop the Metadata Manager server.

2. On the command line, switch to the location of the upgrade utility.
By default, the PowerCenter installer installs the Metadata Manager upgrade utility in the
/Informatica/PowerCenter8.1.1/MetadataManager/upgrade
3. Start the upgrade utility with the following command:

sg_upgrade.bat
The Metadata Manager Upgrade Utility window appears.
4. Under Upgrade Options, select the upgrade tasks that you want to perform.
5. In the Server section, verify the details for the Metadata Manager server.

Verify the following information:
Option Description
Server URL URL of the Metadata Manager instance. Use the following syntax for the URL:
http://<host>:<port>/imm
Server User Name User name to log in to the Metadata Manager server. Default is admin.
Server Password Password for the user name to log in to the Metadata Manager server.
If you are upgrading the repositories, continue with the next step. To import the latest
metamodels and reports, skip to step 8.
6. In the Metadata Manager Repository section, verify the database and directory
information for the Metadata Manager repository you want to upgrade.
If you upgrade a copy of the existing Metadata Manager repository, the Metadata
Manager repository settings displayed on the upgrade utility refer to the original version
of the repository database. You must enter the database information for the copy of the
Metadata Manager repository database.
Option Description
Database User Name User name to connect to the database that contains the Metadata Manager repository.
Database Password Password to connect to the database that contains the Metadata Manager repository.
Database URL JDBC connection string used to connect to the Metadata Manager repository
database. When you select the database type, the Metadata Manager upgrade utility
displays the database URL syntax for the selected database type:
Oracle:
jdbc:informatica:oracle://<host>:<port>;SID=<sid>
DB2:
jdbc:informatica:db2://<host>:<port>;DatabaseName=<database>
jdbc:informatica:sqlserver://
<host>:<port>;DatabaseName=<database>
For more information about the JDBC drivers included in the PowerCenter installation,
see “JDBC Drivers” on page 553.
Database Connect Native connect string to access the repository database. Required for an Oracle or
String IBM DB2 repository database. Use the syntax appropriate for the selected database:
- Oracle: Same syntax as the TNSNAMES entry: aliasname.world. Example:
OraDB.world
- DB2: Syntax is DatabaseName.
Database Code Page Code page for the connection object to the Metadata Manager repository database.
The upgrade utility displays a list of valid code pages. For more information about
these code pages, see “Code Pages” in the PowerCenter Administrator Guide.
Running the Metadata Manager Upgrade Utility on Windows 445

Option Description
SQL Directory Directory where the Metadata Manager upgrade SQL scripts are located. When you
install Metadata Manager, the PowerCenter installer sets the directory to the default
SQL directory:
<PowerCenter_installation_directory>\MetadataManager\
upgrade\upgrade_scripts
By default, you do not need to enter the directory. If the directory is blank, click
Browse to locate the default directory.
Report File Directory Directory where the Metadata Manager objects such as schemas, dashboards, and
reports are located. When you install Metadata Manager, the PowerCenter installer
sets the directory to the default report file directory:
/Informatica/PowerCenter8.1.1/MetadataManager/upgrade/reports
Metamodel File Directory where the Metadata Manager metamodels are located. When you install
Directory Metadata Manager, the PowerCenter installer sets the directory to the default
metamodel file directory:
/Informatica/PowerCenter8.1.1/MetadataManager/upgrade/
metamodel
Report Link Utility Directory where the Metadata Manager report link utility is located. When you install
Directory Metadata Manager, the PowerCenter installer sets the directory to the default report
link utility directory:
reportlink
Metamodel Import Directory where the Metadata Manager metamodel import utility is located. When you
Utility Directory install Metadata Manager, the PowerCenter installer sets the directory to the default
metamodel import utility directory:
/Informatica/PowerCenter8.1.1/MetadataManager/upgrade/sgcmd
7. In the PowerCenter Repository for Metadata Manager section, enter the database and
directory information for the PowerCenter repository for Metadata Manager.
You may need to consult with the PowerCenter administrator to get the PowerCenter
repository for Metadata Manager information.
Windows Option Description
Domain Name Name of the domain of the PowerCenter repository for Metadata Manager.
Domain Host Name of the machine hosting the PowerCenter domain.
Domain Port Port number for the domain where the PowerCenter repository for Metadata Manager
is located.
Domain User Name User name of the domain administrator.

Windows Option Description
Domain Password Password for the domain administrator.
Repository Service Name of the Repository Service associated with the PowerCenter repository for
Name Metadata Manager.
Integration Service Name of the Integration Service associated with the PowerCenter repository.
Name
Repository User Name Repository user name with rights to update repository objects.
Repository Password Password for repository user.
Database User Name Database user name used to create to the PowerCenter repository for Metadata
Manager.
Database Password Password for the database user name used to create the PowerCenter repository for
Metadata Manager.
Database Type Type of database for the PowerCenter repository for Metadata Manager.
Database URL JDBC connection string used to connect to the database that contains the
PowerCenter repository for Metadata Manager. When you select the database type,
the Metadata Manager upgrade utility displays the database URL syntax for the
selected database type.
Oracle:
DB2:
For more information about the JDBC drivers included in the PowerCenter
installation, see “JDBC Drivers” on page 553.
PowerCenter Utility Directory where the PowerCenter utility commands are located. When you install
PowerCenter utility directory:
/Informatica/PowerCenter8.1.1/server/bin
8. Review the upgrade information and click Save Settings to save the upgrade settings to
sg_upgrade.properties file.
9. Click Upgrade.
The upgrade utility starts the repository upgrade process.
If you select the option to upgrade the Metadata Manager metamodels and reports, the
upgrade utility prompts you to start the Metadata Manager server. Start the Metadata
Manager server and verify that it is running before you continue the upgrade process.
If you do not want to upgrade the Metadata Manager metamodels and reports at this
time, click No at the prompt to stop the upgrade utility from upgrading the metamodels
and reports. You can run the upgrade utility again later to upgrade the metamodels and
reports.
Running the Metadata Manager Upgrade Utility on Windows 447

When the upgrade utility completes the upgrade process, it writes information about the
process to a log file with the file name imm_upgrade_<DateTime>.log. You can view the
log file in the Metadata Manager upgrade /Log directory.
10. Click Open Log to view the log file.
The Open Log button displays after the upgrade process completes.
11. Click Exit to close the utility.
When you click Exit, the upgrade utility closes without saving the settings. You must
click Save Settings to save any changes you make to the upgrade settings.

Running the Metadata Manager Upgrade Utility on UNIX
On UNIX, you start and run the upgrade utility in console mode.
When you run the upgrade utility, you can specify whether you want to override the input
values stored in sg_upgrade.properties. If you do not to override the input values and a value
is missing, the upgrade utility prompts you to enter a value for the input. If the upgrade
utility encounters an invalid input and you chose not to override the inputs, the upgrade
utility fails.
After you enter the information for each component, the upgrade utility validates the entries
for the component. If the entries are invalid, the upgrade utility displays an error message and
prompts you to enter all information for the component again.
To run the Metadata Manager upgrade utility on UNIX:
1. Stop the Metadata Manager server.

2. On the command line, switch to the location of the upgrade utility.
By default, the PowerCenter installer installs the Metadata Manager upgrade utility in the
/Informatica/PowerCenter8.1.1/MetadataManager/upgrade
3. Start the upgrade utility with the following command:

sh sg_upgrade.sh
4. Select whether to override the inputs in the properties file.

5. Select the upgrade options. Enter one of the following options:
Option Description
Repository Upgrades a previous version of the Metadata Manager repository and updates the
PowerCenter repository for Metadata Manager.
Metamodels and reports Imports the updated version of Metadata Manager metamodels and reports.
All Upgrades and updates the repositories and imports the updated metamodels and
reports.
6. Enter or verify the following information for the Metadata Manager server:
Option Description
Metadata Manager URL of the Metadata Manager instance. Use the following syntax for the URL:
Database URL http://<host>:<port>/imm
Metadata Manager Server User name to log in to the Metadata Manager server. Default is admin.
User Name
Metadata Manager Server Password for the user name to log in to the Metadata Manager server.
Password
Running the Metadata Manager Upgrade Utility on UNIX 449

If you are upgrading repositories, continue with the next step. To import the latest
metamodels and reports, skip to step 9.
7. In the Metadata Manager Repository section, verify the following database and directory
information for the Metadata Manager repository you want to upgrade.
Option Description
Metadata Manager User name to connect to the database that contains the Metadata Manager repository.
Database User Name
Metadata Manager Password to connect to the database that contains the Metadata Manager repository.
Database Password
Metadata Manager Type of database for the Metadata Manager repository.

Database Type
Metadata Manager JDBC connection string used to connect to the Metadata Manager repository
Database URL database. When you select the database type, the Metadata Manager upgrade utility
displays the database URL syntax for the selected database type.
Oracle:
DB2:
For more information about the JDBC drivers included in the PowerCenter installation,
see “JDBC Drivers” on page 553.
Metadata Manager Native connect string to access the repository database. Required for an Oracle or
Database Connect IBM DB2 repository database. Use the syntax appropriate for the selected database:
String - Oracle: Same syntax as the TNSNAMES entry: aliasname.world. Example:
OraDB.world
- DB2: Syntax is DatabaseName.
Metadata Manager Code page for the connection object to the Metadata Manager repository database.
Database Code Page The upgrade utility displays a list of valid code pages. For more information about
these code pages, see “Code Pages” in the PowerCenter Administrator Guide.
Database SQL Directory where the Metadata Manager upgrade SQL scripts are located. When you
Directory install Metadata Manager, the PowerCenter installer sets the directory to the default
SQL directory:
<PowerCenter_installation_directory>\MetadataManager\
upgrade\upgrade_scripts
Report File Directory Directory where the Metadata Manager objects such as schemas, dashboards, and
reports are located. When you install Metadata Manager, the PowerCenter installer
sets the directory to the default report file directory:
/Informatica/PowerCenter8.1.1/MetadataManager/upgrade/reports

Option Description
Metamodel File Directory where the Metadata Manager metamodels are located. When you install
metamodel file directory:
metamodel
Report Link Utility Directory where the Metadata Manager report link utility is located. When you install
Directory Metadata Manager, the PowerCenter installer sets the directory to the default report
link utility directory:
reportlink
Metamodel Import Directory where the Metadata Manager metamodel import utility is located. When you
Utility Directory install Metadata Manager, the PowerCenter installer sets the directory to the default
metamodel import utility directory:
/Informatica/PowerCenter8.1.1/MetadataManager/upgrade/sgcmd
Note: If you upgrade a copy of the existing Metadata Manager repository, the Metadata
Manager repository settings displayed on the upgrade utility refer to the original version
of the repository database. You must enter the database information for the copy of the
Metadata Manager repository database.
8. In the PowerCenter Repository for Metadata Manager section, enter or verify the
following database and directory information for the PowerCenter repository for
Metadata Manager:
Option Description
PowerCenter Repository Name of the domain of the PowerCenter repository for Metadata Manager.
Domain Name
PowerCenter Repository Name of the machine hosting the PowerCenter domain.

Domain Host
PowerCenter Repository Port number for the domain where the PowerCenter repository for Metadata Manager
Domain Port is located.
PowerCenter Repository User name of the domain administrator.

Domain User Name
PowerCenter Repository Password for the domain administrator.

Domain Password
PowerCenter Repository Name of the Repository Service associated with the PowerCenter repository for
Service Name Metadata Manager.
PowerCenter Integration Name of the Integration Service associated with the PowerCenter repository.
Service Name
Running the Metadata Manager Upgrade Utility on UNIX 451

Option Description
PowerCenter Repository Repository user name with rights to update repository objects.
User Name
PowerCenter Repository Password for repository user.

Password
PowerCenter Repository Database user name used to create the PowerCenter repository for Metadata
Database User Name Manager.
PowerCenter Repository Password of the database user name used to create the PowerCenter repository for
Database Password Metadata Manager.
PowerCenter Repository Type of database for the PowerCenter repository for Metadata Manager.
Database Type
PowerCenter Repository JDBC connection string used to connect to the database that contains the
Database URL PowerCenter repository for Metadata Manager. When you select the database type,
the Metadata Manager upgrade utility displays the database URL syntax for the
selected database type.
Oracle:
DB2:
For more information about the JDBC drivers included in the PowerCenter
installation, see “JDBC Drivers” on page 553.
PowerCenter Utilities Directory where the PowerCenter utility commands are located. When you install
PowerCenter utility directory:
/Informatica/PowerCenter8.1.1/server/bin
Note: You may need to consult with the PowerCenter administrator to get the
PowerCenter repository for Metadata Manager information.
9. When the utility prompts you, start the Metadata Manager server and verify the
application is running before you continue.
The upgrade utility continues the repository upgrade process. When the upgrade utility
completes the upgrade process, it writes information about the process to
imm_upgrade_<DateTime>.log, located in the Metadata Manager upgrade directory.

Upgrading the Metadata Manager Client
To upgrade the client component of Metadata Manager, uninstall the old version of the
Metadata Manager Client and install the new version. Next, update the Metadata Manager
parameter files. Complete the Metadata Manager Client upgrade tasks on the machine where
the Metadata Manager Client is installed.
Note: If you upgrade from SuperGlue version 2.1 or 2.2, update the SuperGlue Client to the
Metadata Manager Client.
Metadata Manager Client Upgrade Steps

To upgrade the Metadata Manager Client, complete the following steps:
1. Back up the existing parameter files. Metadata Manager provides a set of parameter files
that control the behavior of the PowerCenter workflows, worklets, and sessions contained
in the XConnects. Before you upgrade the Metadata Manager Client, back up the
parameter files.
By default, the parameter files are located in the following directory:
\<MetadataManagerHome>\Console\Param_files.
2. Stop the Metadata Manager Scheduler service. To ensure a clean uninstallation of the
Metadata Manager Client, stop the scheduler service. The scheduler service runs on the
Windows machine hosting the Configuration Console. Go to Services in the Control
Panel and stop the service named Informatica PowerCenter Metadata Manager Scheduler.
For SuperGlue 2.1 or 2.2, the service is named Informatica SuperGlue Scheduler.
3. Uninstall the Metadata Manager Client. Run the uninstaller for the Metadata Manager
Client (previously named SuperGlue). Follow the instructions in the uninstaller.
Manually delete any file that was not removed by the uninstaller.
4. Install the latest version of the Metadata Manager Client. For information about
installing the Metadata Manager Client, see “PowerCenter Client Installation” on
page 265.
5. Verify and save the source repository connections for XConnects. Verify and save the
source repository connections for XConnects. Verify and save the source repository
connection information for each XConnect in the Metadata Manager Console. If
password or DSN is blank, enter the password again and select a DSN for PowerCenter,
Data Analyzer, and RDBMS Xconnects. For more information about saving the source
repository connections, see “Setting Up XConnect Source Repository Connections” in
the Metadata Manager Administrator Guide.
6. Configure the parameters for XConnects. Verify the values for the parameters before you
run the upgraded XConnects. Reconfigure the settings if necessary. For more information
about setting the parameters for the packaged XConnects, see “Configuring Parameters
for XConnects” in the Metadata Manager Administrator Guide.
Upgrading the Metadata Manager Client 453

For custom XConnects, manually configure the new parameter files to match the old
parameter files. For more information about configuring parameter files for custom
XConnects, see the “Creating an XConnect Manually” in the Metadata Manager Custom
Metadata Integration Guide.

Chapter 21
After You Upgrade

♦ Overview, 456
♦ PowerCenter 6.x / 7.x Post-Upgrade Tasks, 457
♦ PowerCenter 8.0 Post-Upgrade Tasks, 460
♦ PowerCenter 8.1 Post-Upgrade Tasks, 462
♦ Data Analyzer Post-Upgrade Tasks, 464
♦ Metadata Manager Post-Upgrade Tasks, 467
455
Overview
The post-upgrade tasks you perform depend on the PowerCenter version and component you
upgrade from:
♦ PowerCenter 6.x or 7.x. If you upgrade from PowerCenter 6.x or 7.x, you may need to
register a local repository with a global repository, configure application services, update
password variables, and move PowerCenter run-time files. You can also upgrade to a
UTF-8 repository. For more information, see “PowerCenter 6.x / 7.x Post-Upgrade Tasks”
on page 457.
♦ PowerCenter 8.0. If you upgrade from PowerCenter 8.0, copy domains.infa to the new
installation directory and start Informatica Services. You may need recreate the Repository
Service for Metadata Manager, change $PMRootDir and move Integration Service run-
time files, and reconfigure the shared directory for the Log Manager. For more
information, see “PowerCenter 8.0 Post-Upgrade Tasks” on page 460.
♦ PowerCenter 8.1. If you upgrade from PowerCenter 8.1, reconfigure environment
variables, restart Informatica Services, and run the RegisterPlugin pmrep command to
update the repository. For more information, see “PowerCenter 8.1 Post-Upgrade Tasks”
on page 462.
♦ Data Analyzer. If you upgrade from Data Analyzer version 8.0 or earlier, you must update
configuration files, color schemes, cached reports, location of shared documents, and
refresh PowerCenter table definitions. For more information, see “Data Analyzer Post-
Upgrade Tasks” on page 464.
♦ Metadata Manager. If you upgrade from Metadata Manager 8.1 or earlier, you must
refresh Metadata Manager views. You may also need to delete obsolete Metadata Manager
objects, import metamodels, and update metadata. For more information, see “Metadata
Manager Post-Upgrade Tasks” on page 467.
456 Chapter 21: After You Upgrade

PowerCenter 6.x / 7.x Post-Upgrade Tasks
Perform the following tasks to complete the upgrade process from PowerCenter version 6.x or
7.x:
1. Register local repositories. Unregister and reregister local repositories.
2. Configure application services. Configure the Repository Service and Integration
Service.
3. Update the password environment variable. Use the pmpasswd command line program
to update the password in password environment variables.
4. Upgrade to a Unicode repository. Upgrade an existing repository to a Unicode
repository.
5. Move PowerCenter Server run-time files. Move run-time files used by the PowerCenter
Server to the new installation.
6. Configure the Web Services Hub. Create and configure the Web Services Hub and
update client applications.
7. Install database client software. If you use the DataDirect ODBC drivers installed with
PowerCenter to connect to Oracle, IBM DB2, or Sybase ASE from a UNIX machine,
install database client software and configure native connectivity on the machine where
the Integration Service runs. You can also use a third-party ODBC driver that is level 2 or
above compliant.The ODBC wire protocols do not require database client software to
connect to sources and targets.
Step 1. Register Local Repositories

If you upgrade global and local repositories, unregister each local repository and register it
with the global repository. For more information about registering a local repository, see
“Managing the Repository” in the PowerCenter Administrator Guide.
Step 2. Configure Application Services

Configure the Repository Service and Integration Service. For more information, see
“Creating and Configuring the Repository Service” and “Creating and Configuring the
Integration Service” in the PowerCenter Administrator Guide.
Step 3. Update Password Environment Variable

PowerCenter 8.1 uses a new password encryption algorithm. Use the pmpasswd command line
program to update the password in password environment variables. You use password
environment variables with pmcmd and pmrep. For more information, see the PowerCenter
PowerCenter 6.x / 7.x Post-Upgrade Tasks 457

Step 4. Upgrade to a Unicode Repository
You can store metadata in multiple languages in a Unicode repository. If you want to upgrade
an existing repository to a Unicode repository, back up the upgraded repository. Create a
UTF-8 database and restore the repository backup file to the new database.
For more information about using UTF-8 and code page compatibility, see “Understanding
Globalization” in the PowerCenter Administrator Guide. For more information about backing
up and restoring a repository in PowerCenter, see “Managing the Repository” in the
PowerCenter Administrator Guide.
Step 5. Move PowerCenter Server Run-time Files

When you upgrade a PowerCenter Server to an Integration Service, the upgrade process sets
the value of the $PMRootDir service process variable for the Integration Service process to
the value in the PowerCenter Server configuration file. After you upgrade, complete the
following tasks to access the files within the new installation:
♦ Move the files to server/infa_shared directory under the PowerCenter Services installation
directory.
♦ Update $PMRootDir for the Integration Service process in the Administration Console.
For more information about configuring $PMRootDir, see “Creating and Configuring the
Note: If you upgraded the PowerCenter Server to an Integration Service on the same machine,
the Integration Service can access the files if you do not move them.
Step 6. Configure the Web Services Hub

If the previous PowerCenter installation includes the Web Services Hub, complete the
following tasks to create and configure the Web Services Hub and update client applications:
♦ Create and configure the Web Services Hub. Create the Web Services Hub in the
Administration Console. You must upgrade the associated repository before you create a
new Web Services Hub. Use the settings from the backup version of the configuration file
to duplicate the previous settings. For more information, see “Creating and Configuring
the Web Services Hub” in the PowerCenter Administrator Guide.
♦ Update client applications. The services hosted by the Web Services Hub are stateless. You
must update service workflows and service-enabled objects to use the new URL and user
name and password. The new endpoint for web services consumer applications is WSH.
The client application samples included with PowerCenter include the new URL. For
more information, see the PowerCenter Post-Upgrade Reference and the PowerCenter Web
Services Provider Guide.

If you use the DataDirect ODBC drivers installed by PowerCenter to connect to Oracle, IBM
DB2, or Sybase ASE from a UNIX machine, install database client software and configure
native connectivity on the machine where the Integration Service runs. You can also use a
third-party ODBC driver that is level 2 or above compliant. The ODBC wire protocols do
not require database client software to connect to sources and targets.
Effective in version 8.1, the PowerCenter installer does not include DataDirect ODBC drivers
for Oracle, IBM DB2, or Sybase ASE on a UNIX machine. For more information, see
“Connecting to Databases from UNIX” on page 503.
PowerCenter 6.x / 7.x Post-Upgrade Tasks 459

PowerCenter 8.0 Post-Upgrade Tasks
Perform the following tasks to complete the upgrade process from PowerCenter version 8.0:
1. Reconfigure environment variables. If you unset PowerCenter environment variables
before you installed PowerCenter Services, reconfigure the environment variables.
2. Move Integration Service run-time files. Move the run-time files used by the Integration
Service.
3. Update shared directory for the service logs. Configure the shared directory to point to
the server/infa_shared/logs directory in the new installation directory. For more
information about configuring the service log shared directory, see “Managing Logs” in
the PowerCenter Administrator Guide.
4. Recreate the Repository Service for Metadata Manager. If you installed PowerCenter
Services with Metadata Manager, you must recreate the Repository Service for the
PowerCenter repository you use with Metadata Manager.
5. Install database client software. If you use the DataDirect ODBC drivers installed with
PowerCenter to connect to Oracle, IBM DB2, or Sybase ASE from a UNIX machine,
install database client software and configure native connectivity on the machine where
the Integration Service runs. You can also use a third-party ODBC driver that is level 2 or
above compliant. The ODBC wire protocols do not require database client software to
connect to sources and targets.
Step 1. Reconfigure Environment Variables

If you removed the INFA_HOME or INFA_DOMAINS_FILE environment variables before
you installed PowerCenter Services, reconfigure the environment variables.
For more information about configuring PowerCenter environment variables, see “Step 5.
Configure Environment Variables” on page 59.
Step 2. Move Integration Service Run-time Files

When you upgrade the domain, the $PMRootDir service process variable is set to the
previous location of the Integration Service run-time files. For example, if you used the
server/infa_shared directory for the $PMRootDir value, it points to the previous PowerCenter
Services installation directory.
If you want to use the server/infa_shared directory in the new PowerCenter Services
installation directory, complete the following tasks to access the files within the new
installation:
♦ Move the files to server/infa_shared directory under the PowerCenter Services installation
directory.
♦ Update $PMRootDir for the Integration Service process in the Administration Console.
For more information about configuring $PMRootDir, see “Creating and Configuring the

Step 3. Update Service Logs Directory
When you upgrade the domain, the shared directory location points to the previous location.
For example, if you used server/infa_shared/logs directory to store log event files, the current
setting for the service logs will point to the previous installation directory.
Configure the shared directory to point to the server/infa_shared/logs directory in the new
installation directory. For more information about configuring the service log shared
directory, see “Managing Logs” in the PowerCenter Administrator Guide.
Step 4. Recreate Repository Service for Metadata Manager

If you installed PowerCenter Services with Metadata Manager, the installer creates a
Repository Service to restore the PowerCenter repository for Metadata Manager. When you
upgrade the domain, the Repository Service is removed because it did not exist in the previous
domain configuration. You must recreate the Repository Service for the PowerCenter
repository you use with Metadata Manager. For more information about creating a Repository
Service, see “Creating and Configuring the Repository Service” in the PowerCenter

If you use the DataDirect ODBC drivers installed by PowerCenter to connect to Oracle, IBM
DB2, or Sybase ASE from a UNIX machine, install database client software and configure
native connectivity on the machine where the Integration Service runs. You can also use a
third-party ODBC driver that is level 2 or above compliant. The ODBC wire protocols do
not require database client software to connect to sources and targets.
Effective in version 8.1, the PowerCenter installer does not include DataDirect ODBC drivers
for Oracle, IBM DB2, or Sybase ASE on a UNIX machine. For more information, see
“Connecting to Databases from UNIX” on page 503.
PowerCenter 8.0 Post-Upgrade Tasks 461

PowerCenter 8.1 Post-Upgrade Tasks
Perform the following tasks to complete the upgrade process from PowerCenter 8.1:
1. Restart Informatica Services. Restart Informatica Services on the nodes in the
PowerCenter domain.
2. Update the repository. Use the pmrep RegisterPlugin command to update the repository.
3. Move Integration Service run-time files. If you use the server/infa_shared directory for
the $PMRootDir, move the Integration Service run-time files to the new server directory.
Step 1. Restart Informatica Services

The installer does not start Informatica Services when you upgrade PowerCenter Services 8.1.
After you install PowerCenter Services on the nodes in the domain, you must restart
Informatica Services. Start Informatica Services on the gateway nodes before you start it on
the worker nodes in the domain.
For more information about starting Informatica Services, see “Starting and Stopping
Informatica Services” on page 529.
Step 2. Update the Repository

Update the repository for the following features:
♦ SQL transformation
♦ Unstructured Data Option
♦ PowerExchange Client for PowerCenter
♦ PowerCenter Connect for Saleforce.com
♦ PowerCenter Connect for SAP NetWeaver mySAP Option business content
integration
♦ PowerCenter Connect for Web Services
Complete the following steps to update the repository:
1. Configure the 8.1.1 Repository Service to run in exclusive mode.
2. Connect to the 8.1.1 Repository Service with the pmrep Connect command using a user
account with Admin Repository privilege.
For more information about using the pmrep Connect command, see the PowerCenter
3. Locate the registration file name of the feature that requires a repository content update.
The files are located in $INFA_ROOT\server\bin\native.
Note: $INFA_ROOT is the PowerCenter 8.1.1 installation directory.

The following table lists the registration files for each feature:
Feature Filename
SQL transformation pmsqlt.xml
Unstructured Data Option pmudt.xml
PowerExchange Client for PowerCenter pmpwxclnt.xml
PowerCenter Connect for Salesforce.com pmsfdc.xml
PowerCenter Connect for SAP NetWeaver mySAP lmapitgt.xml

Option business content integration
PowerCenter Connect for Web Services pmwsconsumer.xml
4. Use the pmrep RegisterPlugin command to update the repository.

The RegisterPlugin command uses the following syntax:
registerplugin -i <input_registration_file_name_or_path> -e -N
For more information about the pmrep RegisterPlugin command, see the PowerCenter
5. Repeat steps 3 to 4 for each feature.
Step 3. Move Integration Service Run-time Files

When you upgrade PowerCenter 8.1, the installer renames the server directory in the
PowerCenter 8.1 installation directory to server_810_PC. If you configured the $PMRootDir
variable for Integration Service processes to use the server/infa_shared directory, you must
move the run-time files used by the Integration Service processes to the new server directory.
PowerCenter 8.1 Post-Upgrade Tasks 463

Data Analyzer Post-Upgrade Tasks
Perform the following tasks to complete the upgrade process for Data Analyzer:
1. Update the custom color schemes. Restore the previous color schemes in Data Analyzer
8.1.1 to match the color scheme and logo customization in the previous version.
2. Update the cached reports. To ensure that Data Analyzer has the latest data in the
existing reports and dashboard indicators, log in to Data Analyzer and run the cached
reports to refresh the data for the reports and indicators.
3. Update the location of shared documents. If the location of shared documents has
changed, update the URL address for all shared documents.
4. Refresh the PowerCenter table definitions. If you use PowerCenter table definitions, you
must refresh the table definitions to be able to view information about the attributes and
metrics from PowerCenter in the Data Analyzer reports.
5. Update applications that use the Data Analyzer SDK. The latest version of the Data
Analyzer SDK supports the new features in Data Analyzer. You may need to update your
web application to support the features in the latest version of Data Analyzer.
Step 1. Update the Custom Color Schemes

In Data Analyzer 8.1.1, all custom color schemes are stored in the Data Analyzer EAR file.
After you upgrade to Data Analyzer 8.1.1, you must update the Data Analyzer EAR file with
your custom color schemes.
To keep using custom color schemes after you upgrade to Data Analyzer 8.1.1, complete the
following steps:
1. Use the EAR Repackager utility to extract the default color schemes in Data Analyzer
8.1.1.
2. In the working directory for the EAR Repackager utility, add the customized color
scheme directory to the following directory:
/custom/images/standard/
3. Use the EAR Repackager utility to repackage the color scheme files back into the Data
Analyzer 8.1.1 EAR file.
4. Set up the custom color scheme in the Color Schemes and Logos section of the
Administration tab in Data Analyzer.
For more information about setting up color schemes in Data Analyzer, see the color schemes
section in “Managing System Settings” in the Data Analyzer Administrator Guide.
For more information about using the EAR Repackager utility to access the Data Analyzer
EAR file, see “Accessing the Data Analyzer EAR File” in the Data Analyzer Administrator
Guide.

Step 2. Update the Cached Reports
The Repository Upgrade utility upgrades the Data Analyzer schedules but does not update the
cached reports in the schedules. You must manually update the cached reports.
After you run the Repository Upgrade utility, run the cached reports to update the data for
the reports and indicators in Data Analyzer.
To update the cached reports:
1. Log in to Data Analyzer.

2. Click Administration > Scheduling > Time-Based Schedules.
3. Click Run Now for each time-based schedule in the list.
Data Analyzer queues all the cached reports and runs them on the time-based schedule.
Depending on the number of cached reports, the process may take a while.
4. Click Administration > Scheduling > Event-Based Schedules.
5. Click Run Now for each event-based schedule in the list.
Data Analyzer queues all the reports and runs them on the event-based schedule.
Depending on the number of cached reports, the process may take a while.
6. Verify that the reports display correctly.
Step 3. Update the Location of Shared Documents

After you complete the upgrade process, copy the shared document files you backed up into a
web server directory accessible from the new instance of Data Analyzer. Log in to Data
Analyzer and specify the new file location. Update the URL address for all shared documents
in Data Analyzer.
For more information about the location of shared documents in Data Analyzer, see
“Accessing Data Analyzer Content” in the Data Analyzer User Guide.
Step 4. Refresh the PowerCenter Table Definitions

If you have PowerCenter, you must refresh the table definitions that you import from a
PowerCenter data source after you upgrade the Data Analyzer repository.
If you do not refresh the table definitions, Data Analyzer cannot display attribute and metric
information for any report that uses attributes and metrics from PowerCenter schemas. For
more information about the attribute and metric information displayed for a report, see
“Accessing Data Analyzer Content” in the Data Analyzer User Guide.
To refresh the PowerCenter table definitions:
1. Log in to Data Analyzer with system administrator privileges.

2. Click Administration > Schema Design > Table Definitions.
Data Analyzer Post-Upgrade Tasks 465

The Table Definitions page displays.
3. Click Refresh Tables.
The Refresh Tables page displays the list of data sources available in Data Analyzer. The
pound symbol (#) before the data source name indicates a PowerCenter data source.
4. Select the data source for the PowerCenter tables.
The list of tables definitions from the selected data source appears.
5. Click OK to refresh all the table definitions.
If you do not want to refresh all the table definitions, select only the tables that you want
to refresh and click OK.
Step 5. Update Applications that Use the Data Analyzer SDK

The latest version of the Data Analyzer SDK supports the new features in Data Analyzer. You
may need to update your web application to support the features in the latest version of Data
Analyzer.
If you use the Data Analyzer SDK to display Data Analyzer dashboards and reports in your
own application or web portal, verify that your application code displays the Data Analyzer
dashboards and reports correctly. Read the Data Analyzer SDK Guide to learn how to use the
latest version of the Data Analyzer SDK. You may need to update your web application to
support the features in the latest version of Data Analyzer.
For more information about how to upgrade your portal application to use the Data Analyzer
API 8.x and Portal Integration kit 8.x, see “Upgrading API and Portal Kit Applications” in the
Data Analyzer SDK Guide.

Metadata Manager Post-Upgrade Tasks
Perform the following tasks to complete the upgrade process for Metadata Manager:
1. Refresh Metadata Manager views. If you upgrade from SuperGlue 2.1 or 2.2, you must
refresh the Metadata Manager views to ensure that the Metadata Manager reports use the
latest schema. For more information, see “Step 1. Refresh Metadata Manager Views” on
page 467.
2. If you upgrade from SuperGlue 2.1, delete the obsolete Metadata Manager objects. The
Metadata Manager upgrade utility imports the latest Metadata Manager schemas and
reports. SuperGlue 2.1 uses some folders and reports that are obsolete in the latest
version of Metadata Manager. To maintain a clean Metadata Manager repository, delete
the obsolete schema and report folders. For more information, see “Step 2. Delete
Obsolete Metadata Manager Objects” on page 468.
3. Import metamodels. If you are upgrading a DB2 Metadata Manager repository, you must
manually import the latest metamodels. For more information, see “Step 3. Import
Metamodels for an IBM DB2 Repository” on page 469.
4. Update metadata with latest metamodel information. Run the Business Objects
XConnect and Cognos ReportNet Content Manager XConnect to update the metadata.
For more information about updating the metadata, see “Step 4. Update Metadata” on
page 469.
Step 1. Refresh Metadata Manager Views

Complete this step only if you are upgrading from a SuperGlue 2.1 or 2.2 repository.
The Metadata Manager upgrade utility does not refresh the IMA_REPOSITORY and
IMA_ASSOCIATION views. If you upgrade from SuperGlue 2.1 or 2.2, you must log in to
Metadata Manager and refresh the IMA_REPOSITORY and IMA_ASSOCIATION table
definitions.
To refresh IMA_REPOSITORY and IMA_ASSOCIATION views:
1. Log in to Metadata Manager with the administrator user name and password.
2. Click Administration > Table Definitions.
3. On the Table Definitions page, click Refresh Tables.
4. Select the IMMREPORT data source.
The Refresh Tables page displays the list of table definitions available in the data source.
By default, all tables are selected.
5. Clear all table selections, except IMA_ASSOCIATION and IMA_REPOSITORY.
6. Click OK.
Metadata Manager Post-Upgrade Tasks 467

Step 2. Delete Obsolete Metadata Manager Objects
Complete this step only if you are upgrading from a SuperGlue 2.1 repository.
The new version of Metadata Manager does not require some of the objects in SuperGlue 2.1.
Delete the obsolete folders in the Metadata Manager repository.
To delete obsolete folders:
1. Log in to Metadata Manager with the administrator user name and password.
The default Metadata Manager administrator user name is admin and the default
password is admin.
2. Click Administration > Schema Directory > Metrics.
3. On the Metrics page, select all metric folders.
4. Clear the following options to keep the associated folders:
♦ Impact Analysis
♦ Metamodel
♦ ODS Reporting
♦ Operational
5. Click Remove to delete the selected folders.
6. Click OK to confirm that you want to delete the folders.
Metadata Manager deletes the selected folders. It does not delete the folders that are not
selected.
7. Click Administration > Schema Directory > Attributes.
8. On the Attributes page, select all attribute folders.
9. Clear the following options to keep the associated folders:
♦ ODS Report Attributes
♦ Operational Attributes
♦ Metamodel
♦ Element Association
♦ From Elements
♦ To Elements
♦ Associations
10. Click Remove.
11. Click OK to confirm that you want to delete the folders.
Metadata Manager deletes the selected folders.
12. Click the Find tab.
13. On the Show list, select Information Directory.

14. Under Public Folders, expand Business Intelligence.
15. Select Semantic Exploration.
16. In the Details task area, click Delete.
17. Click OK to confirm that you want to delete the folder.
Metadata Manager deletes the selected folder.
18. Repeat steps 14 to 17 to delete the following folders:
♦ Database Content Exploration (a subfolder in the Database Management folder)
♦ ODS Report Templates
19. Log out and close Metadata Manager.
Step 3. Import Metamodels for an IBM DB2 Repository

If you upgrade an IBM DB2 Metadata Manager repository, you must manually import the
latest version of the Metadata Manager metamodels. You import the metamodels from the
Metamodel Management section of the Administration tab in Metadata Manager.
By default, the PowerCenter installer installs the metamodel files in the following directory:
/Informatica/PowerCenter8.1.1/MetadataManager/upgrade/metamodel
Import all the metamodels in the directory into the upgraded Metadata Manager repository.
You must import the first three metamodels in the following order:
♦ cwm.xml
♦ infacwmx.xml
♦ immrepo.xml
After you import the first three metamodels, you can import the rest of the metamodels in
any order.
Note: You must import the DB2Cubeviews.xml metamodel twice.
For more information about importing metamodels, see “Exchanging Metamodels” in the
Metadata Manager Administrator Guide.
Step 4. Update Metadata

Metadata Manager provides new metamodels for Business Objects and Cognos ReportNet
Content Manager. If you ran a previous version of the Business Objects XConnect or Cognos
ReportNet Content Manager XConnect, you must run the new version of the XConnect to
apply the latest metamodel changes. If you do not run the XConnect, you may not see all the
metadata in the Metadata Directory or in reports. If you loaded custom Business Objects
metadata in the previous version and you rerun the XConnect, you will no longer see the
custom metadata objects.
When you upgrade the metamodel reports, you lose customizations to the existing
metamodel. You can recreate the customizations in the new metamodel.
Metadata Manager Post-Upgrade Tasks 469

Part IV: Configuring Connectivity

♦ Understanding Connectivity, 473
♦ Connecting to Databases from Windows, 487
♦ Connecting to Databases from UNIX, 503
471
472
Chapter 22
Understanding Connectivity

♦ Overview, 474
♦ Domain Connectivity, 477
♦ Native Connectivity, 478
♦ ODBC, 479
♦ PowerCenter Client Connectivity, 481
♦ Repository Service Connectivity, 483
♦ Integration Service Connectivity, 484
♦ Data Analyzer and Metadata Manager Connectivity, 486
473
Overview
PowerCenter uses the TCP/IP network protocol, native database drivers, ODBC, and JDBC
for communication between the following PowerCenter components:
♦ Domain and nodes. Nodes and services within a domain use TCP/IP to communicate
with other nodes and services. For more information, see “Domain Connectivity” on
page 477.
♦ PowerCenter Client. The PowerCenter Client uses ODBC to connect to source and target
databases. The PowerCenter Client uses native protocol to communicate with the
Repository Service and Integration Service. For more information about PowerCenter
Client connectivity, see “PowerCenter Client Connectivity” on page 481.
♦ Repository Service. The Repository Service uses native database drivers to communicate
with the PowerCenter repository. The Repository Service uses TCP/IP to communicate
with other PowerCenter components. For more information about Repository Service
connectivity, see “Repository Service Connectivity” on page 483.
♦ Integration Service. The Integration Service uses native database connectivity and ODBC
to connect to source and target databases. The Integration Service uses TCP/IP to
communicate with other PowerCenter components. For more information about
Integration Service connectivity, see “Integration Service Connectivity” on page 484.
♦ Data Analyzer and Metadata Manager. Data Analyzer and Metadata Manager use JDBC
and ODBC to access data sources and repositories. For more information, see “Data
Analyzer and Metadata Manager Connectivity” on page 486.
Figure 22-1 shows an overview of PowerCenter components and connectivity:
Figure 22-1. PowerCenter Connectivity
Sources/
Targets
Domain
Native drivers/ Node 2

ODBC
ODBC
Integration Service
PowerCenter TCP/IP
Client TCP/IP
Node 1
TCP/IP
Repository Service
Native drivers
Repository
Database
474 Chapter 22: Understanding Connectivity

Connectivity Types
PowerCenter components use the following types of connectivity:
♦ Network protocol. Application services and the Service Managers in a domain use TCP/IP
network protocol to communicate with other nodes and services. The PowerCenter Client
also uses TCP/IP to communicate with application services. You can configure the host
name and port number for TCP/IP communication on a node when you install
PowerCenter Services. You can configure the port numbers used for services on a node
when you install PowerCenter or by using the Administration Console.
♦ Native drivers. Native drivers are packaged with database server and client software. The
Repository Service and Integration Service use the native drivers to communicate with
databases. You must install and configure native database client software on the machines
where the Integration Service and Repository Service run. For more information, see
“Native Connectivity” on page 478.
♦ ODBC. The PowerCenter installer installs ODBC drivers when you install PowerCenter
Services and the PowerCenter Client. For more information about ODBC, see “ODBC”
on page 479.
♦ JDBC. Data Analyzer uses JDBC to communicate with the Data Analyzer repository and
data sources. Metadata Manager uses JDBC to communicate with the Metadata Manager
repository and metadata source repositories. For more information about connectivity
between Data Analyzer and Metadata Manager components, see “Data Analyzer and
Metadata Manager Connectivity” on page 486.
The PowerCenter installer uses JDBC to communicate with the domain configuration
database during installation. The gateway nodes in the PowerCenter domain use JDBC to
connect to the domain configuration database after you install.
Table 22-1 describes the drivers used by PowerCenter components:
Table 22-1. Drivers Used by PowerCenter Components
Component Database Driver
Repository Service PowerCenter Repository Native
Integration Service Source Native

Target ODBC
Stored Procedure
Lookup
Data Analyzer Data Analyzer Repository JDBC
Data Source JDBC

ODBC with JDBC-ODBC bridge
Metadata Manager Metadata Manager Repository JDBC
PowerCenter Client PowerCenter Repository Native
Source ODBC
Target
Stored Procedure
Lookup
Overview 475
Table 22-1. Drivers Used by PowerCenter Components
Component Database Driver
Metadata Manager Configuration Console Metadata Manager Repository ODBC

(Metadata Manager Client)
Metadata Source Repository ODBC
Custom Metadata Configurator Metadata Manager Repository JDBC

(Metadata Manager Client)

Domain Connectivity
Services on a node in a PowerCenter domain use TCP/IP to connect to services on other
nodes. Because services can run on multiple nodes in the domain, services rely on the Service
Manager running on the master gateway node to route requests. The Service Manager on the
master gateway node handles requests for services and responds with the address of the
requested service.
Nodes communicate through TCP/IP on the port you select for a node when you install
PowerCenter Services. When you create a node, you select a port number for the node. The
Service Manager on a node listens for incoming TCP/IP connections on that port.
Figure 22-2 shows the path of a request when you use the PowerCenter Client to connect to
the repository:
Figure 22-2. PowerCenter Repository Connectivity

1
PowerCenter
Client
Node 1 Node 2 (Gateway)
Service Manager Service Manager
Application Services Application Services

2 Repository Service
Repository
Database
The following process describes how a repository client application connects to the repository
database:
1. The PowerCenter Client receives the address of the Repository Service from the master
gateway node.
2. The PowerCenter Client connects to the Repository Service.
Other client applications and nodes use a similar process to establish connections between
other application services and nodes in a domain.
Domain Connectivity 477

Native Connectivity
Native drivers are packaged with database server and client software. The Repository Service
and Integration Service use native drivers to communicate with databases. When
communicating with a database, the services pass database calls directly to the native drivers
installed with the database client software. The client software passes the calls to the database,
and returns information from the database to the service.
For example, the Integration Service writes session data to a DB2 target. When you run the
session, the Integration Service reads target database information from the target database
connection stored in the repository. It uses this information to connect to the target database
through the drivers included with the DB2 Client Application Enabler (CAE) installed on the
Integration Service machine. The Integration Service performs all transactions with the target
database through this client software.
Establishing Native Connectivity

To establish native connectivity between the Repository Service or Integration Service and a
database, you must install the client software packaged with the database platform on the
machine where the service runs.
Native connectivity information includes the database user name, password, and other
configuration options specific to the database platform. It also includes a native connect
string. The native connect string contains the database name and database server name and
allows PowerCenter and the database client to direct calls to the correct database.
Table 22-2 describes the native connect string syntax for each supported RDBMS:
Table 22-2. Native Connect String Syntax
Database Connect String Syntax 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 ASE* servername@dbname sambrown@mydatabase
Teradata** ODBC_data_source_name or TeradataODBC

ODBC_data_source_name@db_name or TeradataODBC@mydatabase
ODBC_data_source_name@db_user_name TeradataODBC@sambrown
*Sybase ASE servername is the name of the Adaptive Server from the interfaces file.
**Use Teradata ODBC drivers to connect to source and target databases.
For more information about establishing native connectivity on Windows, see “Connecting to
Databases from Windows” on page 487.
For more information about establishing native connectivity on UNIX, see “Connecting to

ODBC
Open Database Connectivity (ODBC) provides a common way to communicate with
different database platforms. The PowerCenter Client uses ODBC drivers to connect to
source target, lookup, and stored procedure databases. The Integration Service may also use
ODBC drivers to connect to databases.
When communicating with a database, the PowerCenter application passes all database calls
to the ODBC driver. The driver interprets the information and sends it to the native database
client connectivity software. From there, the information passes to the database that processes
the command and sends the requested information back to the PowerCenter Client tool.
For example, when you import a source definition using the PowerCenter Client, the
PowerCenter Client issues a call to the ODBC driver. The ODBC driver translates the call
and passes it to the native database connectivity software, which in turn passes it to the
database. The database processes the request and sends the information back to the Designer
(passing through the native software layer and ODBC software), which displays the source
definition.
Note: Some ODBC drivers contain wire protocols and do not require database client software
installed on the PowerCenter Client machine or the machine where the Integration Service
process runs. For more information about which ODBC drivers require a database client, see
Table 22-3 on page 480.
Establishing ODBC Connectivity

To establish ODBC connectivity between a database and the PowerCenter Client, Integration
Service, or Repository Service, you must install the following components on the machine
hosting the PowerCenter application:
♦ Database client software. Install the client software included with the database platform.
This installs the client libraries needed to connect to the database.
♦ ODBC drivers. PowerCenter installs DataDirect closed 32-bit ODBC drivers when you
install PowerCenter Services or the PowerCenter Client. Your database platform may also
come with an ODBC driver.
After you install the necessary components you must configure an ODBC data source for each
database you want to connect to. A data source contains information that you need to locate
and access the database, such as database name, user name, and database password. On
Windows, you use the ODBC Data Source Administrator to create a data source name. On
UNIX, you add data source entries to the odbc.ini file found in the system $ODBCHOME
directory.
When you create an ODBC data source, you must also specify the driver that the ODBC
driver manager sends database calls to. For more information about ODBC calls, see “ODBC
Calls” on page 549.
ODBC 479
Table 22-3 shows the recommended ODBC drivers to use with each database:
Table 22-3. Recommended Database ODBC Drivers
Requires Database
Database ODBC Driver
Client Software
IBM DB2 IBM ODBC driver Yes
Informix DataDirect 32-bit closed ODBC driver No
Microsoft Access Microsoft Access driver Yes
Microsoft Excel Microsoft Excel driver Yes
Microsoft SQL Server Microsoft SQL Server ODBC driver Yes
Oracle DataDirect 32-bit closed ODBC driver No
Sybase ASE DataDirect 32-bit closed ODBC driver No
Teradata Teradata ODBC driver n/a
For more information about establishing ODBC connectivity on Windows, see “Connecting
to Databases from Windows” on page 487.
For more information about establishing ODBC connectivity on UNIX, see “Connecting to

PowerCenter Client Connectivity
The PowerCenter Client uses ODBC drivers and native database client connectivity software
to communicate with databases. It uses TCP/IP to communicate with the Integration Service
and with the repository.
Table 22-4 describes the connectivity types required to connect the PowerCenter Client to the
Integration Service, repository, and source and target databases:
Table 22-4. PowerCenter Client Connectivity Requirements
PowerCenter Client Connection Connectivity Requirement
Integration Service TCP/IP
Repository Service TCP/IP
Databases ODBC connection for each database
Connecting to the Repository

You can connect to the repository using the PowerCenter Client tools. All PowerCenter
Client tools use TCP/IP to connect to the repository through the Repository Service each
time you access the repository to perform tasks such as connecting to the repository, creating
repository objects, and running object queries.
Connecting to Databases
To connect the Designer to databases, use the Windows ODBC Data Source Administrator to
create a data source for each database you want to access. Select the data source names in the
Designer when you perform the following tasks:
♦ Import a table or a stored procedure definition from a database. Use the Source Analyzer
or Target Designer to import the table from the database. Use the Transformation
Developer, Mapplet Designer, or Mapping Designer to import a stored procedure or a
table for a Lookup transformation.
To connect to the database, you must also provide your database user name, password, and
table or stored procedure owner name.
♦ Preview data. You can select the data source name when you preview data in the Source
Analyzer or Target Designer. You must also provide your database user name, password,
and table owner name.
Connecting to the Integration Service

The Workflow Manager and Workflow Monitor communicate directly with the Integration
Service over TCP/IP each time you perform session and workflow-related tasks, such as
running a workflow. When you log in to a repository through the Workflow Manager or
Workflow Monitor, the client application lists the Integration Services that are configured for
PowerCenter Client Connectivity 481

that repository in the Administration Console. For more information, see “Using the
Workflow Manager” and “Monitoring Workflows” in the PowerCenter Workflow
Administration Guide.

Repository Service Connectivity
The Repository Service manages the metadata in the PowerCenter repository database. All
applications that connect to the repository must connect to the Repository Service. The
Repository Service uses native drivers to communicate with the repository database.
Table 22-5 describes the connectivity required to connect the Repository Service to the
repository and source and target databases:
Table 22-5. Repository Service Connectivity Requirements
Repository Service Connection Connectivity Requirement
PowerCenter Client TCP/IP
Integration Service TCP/IP
Repository database Native database drivers
Note: The Integration Service connects to the Repository Service to retrieve metadata when it
runs workflows. You configure the associated repository for an Integration Service when you
create or configure an Integration Service in the Administration Console.
Connecting from the PowerCenter Client

You can connect to the Repository Service through PowerCenter Client applications by
adding a domain and repository in the PowerCenter Client application. When you connect to
the repository from a PowerCenter Client application, the client application sends a
connection request to the Service Manager on the gateway node. The Service Manager sends
back the host name and port number of the node running the Repository Service. The
PowerCenter Client connects directly to the Repository Service using TCP/IP.
The Repository Service uses the connection information for the service and native database
drivers to communicate with the repository. To connect a Repository Service to a repository
database, you configure the database properties in the Administration Console. You must
install and configure the native database drivers for the repository database on the machine
where the Repository Service runs.
When you install PowerCenter Services, the installer establishes the connection to the
repository database from the Repository Service. You can create additional repository
databases and create additional Repository Services for repository databases.
Repository Service Connectivity 483

Integration Service Connectivity
The Integration Service connects to the repository to read repository objects. The Integration
Service connects to the repository through the Repository Service. Use the Administration
Console to configure an associated repository for the Integration Service.
Table 22-6 describes the connectivity required to connect the Integration Service to the
platform components, source databases, and target databases:
Table 22-6. Integration Service Connectivity Requirements
Integration Service Connection Connectivity Requirement
PowerCenter Client TCP/IP
Other Integration Service Processes TCP/IP
Repository Service TCP/IP
Source and target databases Native database drivers or ODBC

Note: Both the Windows and UNIX versions of the Integration Service can use ODBC drivers to connect to
databases. You can use native drivers to improve performance.
The Integration Service includes ODBC libraries that you can use to connect to other ODBC
sources. The PowerCenter installer installs ODBC drivers.
For flat file, XML, or COBOL sources, you can either access data with network connections
(such as NFS) or transfer data to the Integration Service machine through FTP software. For
information about connectivity software for other ODBC sources, refer to your database
documentation.
Connecting from the PowerCenter Client

The Workflow Manager communicates with an Integration Service process over a TCP/IP
connection. The Workflow Manager communicates with the Integration Service process each
time you start a workflow or display workflow details.
Connecting to the Repository Service

When you create or configure the Integration Service, you specify the repository associated
with the Integration Service. The Integration Service connects to this Repository Service
using TCP/IP to retrieve metadata when it runs a workflow.
When you install PowerCenter Services, the installer configures the associated repository for
the Integration Service.
Use the Workflow Manager to create connections to databases. You can select native database
drivers for the Integration Service or you can use ODBC. For each connection, you must

specify the database user name, password, and native connect string. The Integration Service
uses this information to connect to the database when it runs the session.
Note: PowerCenter supports ODBC drivers, such as ISG Navigator, that do not need user
names and passwords to connect. To avoid using empty strings or nulls, use the reserved
words PmNullUser and PmNullPasswd for the user name and password when you configure a
database connection. The Integration Service treats PmNullUser and PmNullPasswd as no
user and no password.
Integration Service Connectivity 485

Data Analyzer and Metadata Manager Connectivity
To connect to a Data Analyzer repository, Data Analyzer requires a Java Database
Connectivity (JDBC) driver. To connect to the data source, Data Analyzer can use a JDBC
driver or a JDBC-ODBC bridge with an ODBC driver.
To connect to a Metadata Manager repository, Metadata Manager requires a JDBC driver.
The Metadata Manager Client uses JDBC and ODBC drivers to connect to databases. The
Metadata Manager Configuration Console uses ODBC drivers to connect to the Metadata
Manager repository and metadata source repositories. The Custom Metadata Configurator
uses JDBC drivers to connect to the Metadata Manager repository.
When you install Data Analyzer or Metadata Manager, the PowerCenter installer installs the
JDBC drivers for the following databases:
♦ Oracle
♦ Microsoft SQL Server
♦ Sybase ASE
♦ IBM DB2 UDB
You can use the installed JDBC drivers to connect to the Data Analyzer or Metadata Manager
repository, data source, or to a PowerCenter repository.
The PowerCenter installer does not install ODBC drivers or the JDBC-ODBC bridge for
Data Analyzer or Metadata Manager. It installs ODBC drivers for the Metadata Manager
Client.
For more information on the JDBC drivers installed with Data Analyzer and Metadata
Manager, see “Installed JDBC Drivers” on page 554.

Chapter 23
from Windows
♦ Overview, 488
♦ Connecting to an IBM DB2 Universal Database, 489
♦ Connecting to an Informix Database, 491
♦ Connecting to Microsoft Access and Microsoft Excel, 493
♦ Connecting to a Microsoft SQL Server Database, 494
♦ Connecting to an Oracle Database, 496
♦ Connecting to a Sybase ASE Database, 499
♦ Connecting to a Teradata Database, 501
487
Overview
The Repository Service uses native drivers to communicate with the repository database. The
Integration Service uses either native drivers or ODBC to communicate with databases. To
improve performance, use native database drivers. The PowerCenter Client uses ODBC.
To connect to a database, you must install and configure native database client connectivity
software on the machine where you configure the Repository Service and Integration Service
processes to run. To ensure compatibility between the Integration Service, the Repository
Service, and a repository database, use the appropriate database client libraries. For more
information, see “Working with 32-bit and 64-bit Platforms” on page 46.
PowerCenter 8.1.1 includes DataDirect 5.1 ODBC drivers. If you have existing ODBC data
sources created with an earlier version of the drivers, you must create new ODBC data sources
using the new drivers for all ODBC data sources used by the Integration Service or
PowerCenter Client.
488 Chapter 23: Connecting to Databases from Windows

Connecting to an IBM DB2 Universal Database
You must install and configure database client software on the machines where the Integration
Service and Repository Service process runs. To ensure compatibility between PowerCenter
and databases, use the appropriate database client libraries. For more information, see
“Working with 32-bit and 64-bit Platforms” on page 46.
You must configure connectivity to the following PowerCenter components on Windows:
♦ Integration Service. Install or verify that you have installed IBM DB2 Client Application
Enabler (CAE) on the machine where the Integration Service process runs. The
Integration Service uses either native connectivity or ODBC to communicate with IBM
DB2. For increased performance, use native connectivity.
♦ Repository Service. If you create an IBM DB2 repository, install or verify that you have
installed IBM DB2 Client Application Enabler (CAE) on the machine where the
Repository Service process runs. The Repository Service uses native connectivity to
communicate with IBM DB2.
♦ PowerCenter Client. Install or verify you have installed IBM DB2 Client Application
Enabler (CAE) on each PowerCenter Client machine accessing IBM DB2. The
PowerCenter Client uses ODBC to communicate with IBM DB2. Use the Workflow
Manager to create a database connection object for the IBM DB2 database.
You must install the IBM DB2 Client Application Enabler (CAE) version that is compatible
with the IBM DB2 database server. To verify compatibility, contact IBM.
Configuring Native Connectivity

Use the following steps as a guideline to configure native connectivity. For specific
connectivity instructions, refer to the database documentation.
To connect to an IBM DB2 database:
1. Verify that the following environment variable settings have been established by DB2
Client Application Enabler:
DB2HOME=C:\SQLLIB (directory where the client is installed)
DB2INSTANCE = DB2
DB2CODEPAGE = 437 (Sometimes required. Use only if you encounter problems.

Depends on the locale, you may use other values.)
2. Verify that the PATH environment variable includes the DB2 bin directory. For example:
PATH=C:\WINNT\SYSTEM32;C:\SQLLIB\BIN;...
3. Configure the IBM DB2 client to connect to the database that you want to access.
♦ Launch the Client Configuration Assistant.
♦ Add the database connection and BIND the connection.
4. Verify that you can connect to the DB2 database.
Connecting to an IBM DB2 Universal Database 489

Run the following command in the DB2 Command Line Processor:
CONNECT TO <dbalias> USER <username> USING <password>
If the connection is successful, disconnect and clean up with the TERMINATE

command. If the connection fails, refer to the database documentation.
Configuring ODBC Connectivity

Use the following steps as a guideline to configure ODBC. For specific connectivity
instructions, refer to the database documentation.
To connect to an IBM DB2 database using ODBC:
1. Install the IBM DB2 Client Application Enabler (CAE) and configure native
connectivity.
2. Create an ODBC data source using the driver provided by IBM. Do not use the
DataDirect 32-bit closed ODBC driver for DB2 provided by Informatica.
For specific instructions on creating an ODBC data source using the IBM DB2 ODBC
driver, refer to the database documentation.
3. Verify that you can connect to the DB2 database using the ODBC data source. If the
connection fails, refer to the database documentation.

Connecting to an Informix Database
You must install and configure native client software on the machines where the Integration
Service process runs and the machines where you install the PowerCenter Client. To ensure
compatibility between PowerCenter and databases, use the appropriate database client
libraries. For more information, see “Working with 32-bit and 64-bit Platforms” on page 46.
♦ Integration Service.You must install or verify that you have installed ESQL for C,
Informix Client SDK, or any other Informix client software on the machine where the
Integration Service process runs. Also, install compatible versions of ESQL/runtime or
iconnect. The Integration Service uses either native connectivity or ODBC to
communicate with Informix. Use native connectivity for increased performance.
You must install the ESQL/C version that is compatible with the Informix database server.
To verify compatibility, contact Informix.
♦ PowerCenter Client. Use the Workflow Manager to create a database connection object
for the Informix database.
Note: You do not need to install the database client on PowerCenter Client machines. To
connect to an Informix database using the PowerCenter Client, use the DataDirect 5.1
ODBC drivers provided with PowerCenter. The ODBC wire protocols do not require
database client software to connect to sources and targets.

To connect to an Informix database:
1. Set environment variables for INFORMIXDIR, DBDATE, and DBMONEY:

INFORMIXDIR. Verify that the INFORMIXDIR environment variable is set.
For example:
INFORMIXDIR=C:\Informix
DBDATE. Verify that DBDATE is set to the default value, MDY4/.

DBMONEY. Set DBMONEY environment variable to ensure that Informix does not
prefix the data with the dollar sign ($).
DBMONEY=' .'
2. Verify that the PATH environment variable includes the INFORMIXDIR\bin directory.
For example:
PATH=C:\Informix\bin;....
3. Launch Informix SetNet32, and configure the Informix client to connect to the database
that you want to access.
Connecting to an Informix Database 491

You may need to ask the Informix administrator for the following entries for the Server
Information tab:
♦ Protocol Name. Enter the protocol the Informix database server uses, usually
‘onsoctcp.’
♦ Service Name. Enter the service name the Informix server uses. The Informix server
must also be defined in the services file. You might find the services file in the
following location:
%WINDIR%\System32\Drivers\etc\Services
A sample entry in the services file might look like the following entry:
inflsnr 1525/tcp
4. Verify that you can connect to the Informix database.

To connect to the database, launch dbping and enter the necessary information. If you
fail to connect to the database, verify that you correctly entered all of the connectivity
information. The syntax for the connect string is dbname@servername.
User names and database names may be case sensitive.

To connect to an Informix database using ODBC, create an ODBC data source using the
DataDirect 5.1 ODBC drivers for Informix provided by Informatica. The ODBC wire
protocols do not require database client software to connect to sources and targets.
For specific connectivity instructions, refer to the database documentation.

Connecting to Microsoft Access and Microsoft Excel
♦ Integration Service. Install or verify that you have installed Microsoft Access or Excel on
the machine where the Integration Service process runs. You must also create an ODBC
data source to connect to a database.
♦ PowerCenter Client. Install or verify that you have installed Microsoft Access or Excel on
the machine hosting the PowerCenter Client. You must also create an ODBC data source
to connect to a database.

Use the following steps as a guideline to configure connectivity. For specific connectivity
instructions, refer to the Microsoft Access or Excel documentation.
To connect to an Access or Excel database:
1. Create an ODBC data source using the driver provided by Microsoft.

2. To avoid using empty string or nulls, use the reserved words PmNullUser for the user
name and PmNullPasswd for the password when you create a database connection in the
Workflow Manager.
Connecting to Microsoft Access and Microsoft Excel 493

Connecting to a Microsoft SQL Server Database
Service and Repository Service process runs and the machines where you install the
PowerCenter Client. To ensure compatibility between PowerCenter and databases, use the
appropriate database client libraries. For more information, see “Working with 32-bit and 64-
bit Platforms” on page 46.
♦ Integration Service. Install or verify that you have installed SQL Client, including the
Microsoft OLE DB provider for Microsoft SQL Server, on the machine where the
Integration Service process runs. The Integration Service uses either native connectivity or
ODBC to communicate with Microsoft SQL Server. Use native connectivity for increased
performance.
♦ Repository Service. If you create a Microsoft SQL Server repository, install or verify that
you have installed SQL Client, including the Microsoft OLE DB provider, on the machine
where the Repository Service runs. The Repository Service uses native connectivity to
communicate with Microsoft SQL Server.
♦ PowerCenter Client. Install or verify that you have installed SQL Client, including the
Microsoft OLE DB provider for Microsoft SQL Server, on each PowerCenter Client
machine accessing Microsoft SQL Server. The PowerCenter Client uses ODBC to
communicate with Microsoft SQL Server. Use the Workflow Manager to create a database
connection object for the Microsoft SQL Server database.
You must install an SQL Client version that is compatible with the Microsoft SQL Server
database server. To verify compatibility, contact Microsoft.
Note: PowerCenter can communicate with Microsoft SQL Server 7.0, with Service Pack 1 or
later, and later versions of Microsoft SQL Server.

To connect to a Microsoft SQL Server database:
1. Verify that the Microsoft SQL Server home directory is set.

2. Verify that the PATH environment variable includes the Microsoft SQL Server directory.
For example:
PATH=C:\MSSQL\BIN;C:\MSSQL\BINN;....
3. Configure the Microsoft SQL Server client to connect to the database that you want to
access.
Launch the Client Network Utility. On the General tab, verify that the Default Network
Library matches the default network for the Microsoft SQL Server database.

4. Verify that you can connect to the Microsoft SQL Server database.
To connect to the database, launch ISQL_w, and enter the connectivity information. If
you fail to connect to the database, verify that you correctly entered all of the
connectivity information.

instructions, refer to the Microsoft SQL Server documentation.
To connect to a Microsoft SQL Server database using ODBC:
1. Install the Microsoft SQL Server client and configure native connectivity.
2. Create an ODBC data source using the driver provided by Microsoft. Do not use the
DataDirect 32-bit closed ODBC driver for Microsoft SQL Server provided by
Informatica.
To ensure consistent data in Microsoft SQL Server repositories, clear the Create
temporary stored procedures for prepared SQL statements option in the Create a New
Data Source to SQL Server dialog box.
Figure 23-1 shows the dialog box for the Microsoft SQL Server ODBC setup:
Figure 23-1. ODBC Microsoft SQL Server Setup
Clear Create temporary stored

procedures for prepared SQL
statements and drop the stored
procedures.
If you have difficulty clearing the temporary stored procedures for prepared SQL
statements options, see the Informatica Knowledge Base for more information about
configuring Microsoft SQL Server. You can access the Knowledge Base at
http://my.informatica.com.
3. Verify that you can connect to the Microsoft SQL Server database using the ODBC data
source. If the connection fails, refer to the database documentation.
Connecting to a Microsoft SQL Server Database 495

Connecting to an Oracle Database
You must install and configure native client software on the machines where Integration
Service and Repository Service processes run. To ensure compatibility between PowerCenter
♦ Integration Service. Install or verify that you have installed the Oracle client on the
machine hosting the Integration Service. The Integration Service can use native
connectivity or ODBC to communicate with Oracle. Use native connectivity for increased
performance.
♦ Repository Service. If you create an Oracle repository, install or verify that you have
installed the Oracle client on the machine where Repository Service process runs. The
Repository Service uses native connectivity to communicate with Oracle.
for the Oracle database.
connect to an Oracle database using the PowerCenter Client, use the DataDirect 5.1 ODBC
driver provided with PowerCenter. The ODBC wire protocols do not require database client
software to connect to sources and targets.
You must install compatible versions of the Oracle client and Oracle database server. You
must also install the same version of the Oracle client on each machine where an Integration
Service or Repository Service process runs and hosts the Oracle database server. To verify
compatibility, contact Oracle.

Use the following steps as a guideline to configure native connectivity using Oracle Net
Services or Net8. For specific connectivity instructions, refer to the database documentation.
To connect to an Oracle database:
1. Verify that the Oracle home directory is set.

For example:
ORACLE_HOME=C:\Oracle
2. Verify that the PATH environment variable includes the Oracle bin directory.
For example, if you install Net8, the path might include the following entry:
PATH=C:\ORANT\BIN;
3. Configure the Oracle client to connect to the database that you want to access.
Launch SQL*Net Easy Configuration Utility or edit an existing tnsnames.ora file to the
home directory and modify it.

The tnsnames.ora file is stored in the $ORACLE_HOME\network\admin directory.
Enter the correct syntax for the Oracle connect string, typically databasename.world.
Make sure the SID entered here matches the database server instance ID defined on the
Oracle server.
Following is a sample tnsnames.ora. You need to enter the information for the database.
mydatabase.world =
(DESCRIPTION
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = mycompany.world
(PROTOCOL = TCP)
(Host = mymachine)
(Port = 1521)
)
(CONNECT_DATA =
(SID = MYORA7)
(GLOBAL_NAMES = mydatabase.world)
4. Set the NLS_LANG environment variable to the locale (language, territory, and character
set) you want the database client and server to use with the login.
The value of this variable depends on the configuration. For example, if the value is
american_america.UTF8, you must set the variable as follows:
NLS_LANG=american_america.UTF8;
To determine the value of this variable, contact the database administrator.

5. Verify that you can connect to the Oracle database.
To connect to the database, launch SQL*Plus and enter the connectivity information. If
you fail to connect to the database, verify that you correctly entered all of the
connectivity information.
Use the connect string as defined in tnsnames.ora.
Connecting to an Oracle Database 497

To connect to an Oracle database using ODBC:
1. Create an ODBC data source using the DataDirect 5.1 ODBC driver for Oracle
provided by Informatica.
2. Verify that you can connect to the Oracle database using the ODBC data source.
Troubleshooting Database Connection to Oracle

Use the following guidelines to troubleshoot problems with the PowerCenter Client and an
Oracle database.
PowerCenter Clients do not accurately display non-ASCII characters.

Set the NLS_LANG environment variable to the locale (language, territory, and character set)
you want the database client and server to use with the login.
The value of this variable depends on the configuration. For example, if the value is
american_america.UTF8, you must set the variable as follows:
NLS_LANG=american_america.UTF8;
To determine the value of this variable, contact the database administrator.

Connecting to a Sybase ASE Database
You must install an Open Client version that is compatible with the Sybase ASE database
server. You must also install the same version of Open Client on the machines hosting the
Sybase ASE database and PowerCenter. To verify compatibility, contact Sybase.
♦ Integration Service. Install or verify that you have installed Open Client on the machine
where the Integration Service process runs. The Integration Service uses either native
connectivity or ODBC to communicate with Sybase ASE. You should use native
connectivity.
♦ Repository Service. Install or verify that you have installed Open Client on the machine
where the Repository Service process runs. The Repository Service uses native connectivity
to communicate with Sybase ASE.
If you want to create, restore, or upgrade a Sybase ASE repository, set allow nulls by default
to TRUE at the database level. Setting this option changes the default null type of the
column to null in compliance with the SQL standard.
for the Sybase ASE database.
connect to an Sybase ASE database using the PowerCenter Client, use the DataDirect 5.1
ODBC drivers provided with PowerCenter. The ODBC wire protocols do not require
database client software to connect to sources and targets.

To connect to a Sybase ASE database:
1. Verify that the SYBASE environment variable refers to the Sybase ASE directory.
For example:
SYBASE=C:\SYBASE
2. Verify that the PATH environment variable includes the Sybase ASE directory.
For example:
PATH=C:\SYBASE\BIN;C:\SYBASE\DLL
3. Configure Sybase Open Client to connect to the database that you want to access.
Connecting to a Sybase ASE Database 499

Use SQLEDIT to configure the Sybase client, or copy an existing SQL.INI file (located
in the %SYBASE%\INI directory) and make any necessary changes.
Select NLWNSCK as the Net-Library driver and include the Sybase ASE server name.
Enter the host name and port number for the Sybase ASE server. If you do not know the
host name and port number, check with the system administrator.
4. Verify that you can connect to the Sybase ASE database.
To connect to the database, launch ISQL and enter the connectivity information. If you
fail to connect to the database, verify that you correctly entered all of the connectivity
information.
User names and database names are case sensitive.

To connect to a Sybase ASE database using ODBC:
1. Create an ODBC data source using the DataDirect 32-bit closed ODBC driver for
Sybase provided by Informatica.
2. On the Performance tab, set Prepare Method to 2-Full. This ensures consistent data in
the repository, optimizes performance, and reduces overhead on tempdb.
3. Verify that you can connect to the Sybase ASE database using the ODBC data source.

Connecting to a Teradata Database
Service process runs and where you install the PowerCenter Client. To ensure compatibility
between the Informatica products and databases, use 32-bit database client libraries only. You
must configure connectivity to the following PowerCenter components on Windows:
♦ Integration Service. Install or verify that you have installed the Teradata client, the
Teradata ODBC driver, and any other Teradata client software you might need on the
machine where the Integration Service process runs. You must also configure ODBC
connectivity.
♦ PowerCenter Client. Install or verify that you have installed the Teradata client, the
Teradata ODBC driver, and any other Teradata client software you might need on each
PowerCenter Client machine accessing Teradata. Use the Workflow Manager to create a
database connection object for the Teradata database.
Note: Based on a recommendation from Teradata, Informatica uses ODBC to connect to
Teradata. ODBC is a native interface for Teradata.

To connect to a Teradata database:
1. Create an ODBC data source for each Teradata database that you want to access.
To create the ODBC data source, use the driver provided by Teradata.
Create a System DSN if you start the Informatica Services service with a Local System
account logon. Create a User DSN if you select the This account log in option to start the
Informatica Services service.
2. Enter the name for the new ODBC data source and the name of the Teradata server or its
IP address.
To configure a connection to a single Teradata database, enter the DefaultDatabase name.
To create a single connection to the default database, enter the user name and password.
To connect to multiple databases, using the same ODBC data source, leave the
DefaultDatabase field and the user name and password fields empty.
3. Configure Date Options in the Options dialog box. In the Teradata Options dialog box,
specify AAA for DateTime Format.
4. Configure Session Mode in the Options dialog box.
When you create a target data source, choose ANSI session mode. If you choose ANSI
session mode, Teradata does not roll back the transaction when it encounters a row error.
If you choose Teradata session mode, Teradata rolls back the transaction when it
Connecting to a Teradata Database 501

encounters a row error. In Teradata mode, the Integration Service cannot detect the
rollback and does not report this in the session log.
5. Verify that you can connect to the Teradata database.
To test the connection, use a Teradata client program, such as WinDDI, BTEQ, Teradata
Administrator, or Teradata SQL Assistant.

Chapter 24
from UNIX
♦ Overview, 504
♦ Connecting to an IBM DB2 Universal Database, 505
♦ Connecting to an Informix Database, 508
♦ Connecting to an Oracle Database, 511
♦ Connecting to a Sybase ASE Database, 515
♦ Connecting to a Teradata Database, 518
♦ Connecting to an ODBC Data Source, 522
♦ Sample odbc.ini File, 525
503
Overview
The Repository Service uses native drivers to communicate with the repository database. The
Integration Service can use native drivers or ODBC to communicate with databases. Use
native database drivers to increase performance.
To connect to a database, install and configure native database client connectivity software on
the machine where you configure the Repository Service and Integration Service processes to
run. To ensure compatibility between the Integration Service, the Repository Service, and a
repository database, use the appropriate database client libraries. For more information, see
On Linux, use native drivers to connect to IBM DB2, Oracle, or Sybase ASE databases.You
can connect to other sources and targets using ODBC. The Informix client is not available on
Linux. Use ODBC to connect to Informix from Linux.
Configure ODBC connections using the DataDirect ODBC drivers provided with
PowerCenter or third-party ODBC drivers that are Level 2 or above compliant. The ODBC
wire protocols do not require database client software to connect to sources and targets. For
more information, see “Connecting to an ODBC Data Source” on page 522.
Note: You cannot use Teradata or Informix for a PowerCenter repository.
Connecting to Microsoft SQL Server on UNIX

You must use ODBC to connect to a Microsoft SQL Server database from a UNIX machine.
For more information about setting up ODBC on a UNIX machine, see “Connecting to an
ODBC Data Source” on page 522.
504 Chapter 24: Connecting to Databases from UNIX

Connecting to an IBM DB2 Universal Database
Service and Repository Service processes run. To ensure compatibility between the
PowerCenter and databases, use the appropriate database client libraries. For more
Configure connectivity to the following PowerCenter components on UNIX:
♦ Integration Service. Install IBM DB2 Client Application Enabler (CAE) on the machine
where the Integration Service process runs. The Integration Service can use native
connectivity or ODBC to communicate with IBM DB2. Use native connectivity for
increased performance.
♦ Repository Service. If you create an IBM DB2 repository, install IBM DB2 Client
Application Enabler (CAE) on the machine where the Repository Service process runs.
The Repository Service uses native connectivity to communicate with IBM DB2.
You must install the IBM DB2 Client Application Enabler (CAE) version that is compatible
with the IBM DB2 database server. To verify compatibility, contact IBM.

To connect to a DB2 database:
1. To configure connectivity on the machine where the Integration Service or Repository

Service process runs, log in to the machine as a user who can start a service process.
2. Set the DB2INSTANCE, INSTHOME, DB2DIR, and PATH environment variables.
The UNIX IBM DB2 software always has an associated user login, often db2admin,
which serves as a holder for database configurations. This user holds the instance for
DB2.
DB2INSTANCE. The name of the instance holder.
Using a Bourne shell:
$ DB2INSTANCE=db2admin; export DB2INSTANCE
Using a C shell:
$ setenv DB2INSTANCE db2admin
INSTHOME. This is db2admin home directory path.

$ INSTHOME=~db2admin
Using a C shell:
$ setenv INSTHOME ~db2admin>

DB2DIR. Set the variable to point to the IBM DB2 CAE installation directory. For
example, if the client is installed in the /opt/IBMdb2/v6.1 directory:
$ DB2DIR=/opt/IBMdb2/v6.1; export DB2DIR
Using a C shell:
$ setenv DB2DIR /opt/IBMdb2/v6.1
PATH. To run the IBM DB2 command line programs, set the variable to include the
DB2 bin directory.
$ PATH=${PATH}:$DB2DIR/bin; export PATH
Using a C shell:
$ setenv PATH ${PATH}:$DB2DIR/bin
3. Set the shared library variable to include the DB2 lib directory.
The IBM DB2 client software contains a number of shared library components that the
Integration Service and the Repository Service processes load dynamically. To locate the
shared libraries during run time, set the shared library environment variable.
The shared library path must also include the PowerCenter Services installation directory
(server_dir).
Set the shared library environment variable based on the operating system. The following
table describes the shared library variables for each operating system:
Operating System Variable
Solaris LD_LIBRARY_PATH
Linux LD_LIBRARY_PATH
AIX LIBPATH
HP-UX SHLIB_PATH
For example, use the following syntax for Solaris and Linux:
♦ Using a Bourne shell:
$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/server_dir:$DB2DIR/lib; export
LD_LIBRARY_PATH
♦ Using a C shell:
$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/server_dir:$DB2DIR/lib
For HP-UX:
$ SHLIB_PATH=${SHLIB_PATH}:$HOME/server_dir:$DB2DIR/lib; export
SHLIB_PATH

$ setenv SHLIB_PATH ${SHLIB_PATH}:$HOME/server_dir:$DB2DIR/lib
For AIX:
$ LIBPATH=${LIBPATH}:$HOME/server_dir:$DB2DIR/lib; export LIBPATH
$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$DB2DIR/lib
4. Edit the .cshrc or .profile to include the complete set of shell commands. Save the file and
either log out and log in again or issue the source command.
$ source .profile
Using a C shell:
$ source .cshrc
5. If the DB2 database resides on the same machine on which Integration Service or
Repository Service processes run, configure the DB2 instance as a remote instance.
Run the following command to verify if there is a remote entry for the database:
DB2 LIST DATABASE DIRECTORY
The command lists all the databases that the DB2 client can access and their
configuration properties. If this command lists an entry for “Directory entry type” of
“Remote,” skip to step 6.
If the database is not configured as remote, run the following command to verify whether
a TCP/IP node is cataloged for the host:
DB2 LIST NODE DIRECTORY
If the node name is empty, you can create one when you set up a remote database. Use
the following command to set up a remote database and, if needed, create a node:
db2 CATALOG TCPIP NODE <nodename> REMOTE <hostname_or_address> SERVER
<port number>
Issue the following command to catalog the database:

db2 CATALOG DATABASE <dbname> as <dbalias> at NODE <nodename>
For more information about these commands, refer to the database documentation.
6. Verify that you can connect to the DB2 database. Run the DB2 Command Line
Processor and issue the command:
CONNECT TO <dbalias> USER <username> USING <password>
If the connection is successful, clean up with the CONNECT RESET or TERMINATE

command.

Connecting to an Informix Database
Service process runs. To ensure compatibility between PowerCenter and databases, use the
Install ESQL for C, Informix Client SDK, or any other Informix client software on the
machine where the Integration Service process runs. Also, install compatible versions of
ESQL/runtime or iconnect. The Integration Service uses either native connectivity or ODBC
to communicate with Informix. Use native connectivity for increased performance.
The Informix client is not available on Linux. Use ODBC to connect to Informix from Linux.
You must install the ESQL/C version that is compatible with the Informix database server. To
verify compatibility, contact Informix.

To connect to an Informix database:
1. To configure connectivity for the Integration Service process, log in to the machine as a
user who can start the server process.
2. Set the INFORMIXDIR, INFORMIXSERVER, DBMONEY, and PATH environment
variables.
INFORMIXDIR. Set the variable to the directory where the database client is installed.
For example, if the client is installed in the /databases/informix directory:
$ INFORMIXDIR=/databases/informix; export INFORMIXDIR
Using a C shell:
$ setenv INFORMIXDIR /databases/informix
INFORMIXSERVER. Set the variable to the name of the server. For example, if the
name of the Informix server is INFSERVER:
$ INFORMIXSERVER=INFSERVER; export INFORMIXSERVER
Using a C shell:
$ setenv INFORMIXSERVER INFSERVER
DBMONEY. Set the variable so Informix does not prefix the data with the dollar sign ($)
for money datatypes.

$ DBMONEY=' .'; export DBMONEY
Using a C shell:
$ setenv DBMONEY=' .'
PATH. To run the Informix command line programs, set the variable to include the
Informix bin directory.
$ PATH=${PATH}:$INFORMIXDIR/bin; export PATH
Using a C shell:
$ setenv PATH ${PATH}:$INFORMIXDIR/bin
3. Set the shared library path to include the Informix lib directory.
The Informix client software contains a number of shared library components that the
Integration Service process loads dynamically. To locate the shared libraries during run
time, set the shared library environment variable.
(server_dir).
AIX LIBPATH
HP-UX SHLIB_PATH
For example, use the following syntax for Solaris:

$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/server_dir:$INFORMIXDIR/
lib:$INFORMIXDIR/lib/esql; export LD_LIBRARY_PATH
$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/
server_dir:$INFORMIXDIR/lib:$INFORMIXDIR/lib/esql
For HP-UX
$ SHLIB_PATH=${SHLIB_PATH}:$HOME/server_dir:$INFORMIXDIR/
lib:$INFORMIXDIR/lib/esql; export SHLIB_PATH
Connecting to an Informix Database 509

$ setenv SHLIB_PATH ${SHLIB_PATH}:$HOME/server_dir:$INFORMIXDIR/
lib:$INFORMIXDIR/lib/esql
For AIX
$ LIBPATH=${LIBPATH}:$HOME/server_dir:$INFORMIXDIR/lib:$INFORMIXDIR/lib/
esql; export LIBPATH
$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$INFORMIXDIR/
lib:$INFORMIXDIR/lib/esql
4. Optionally, set the $ONCONFIG environment variable to the Informix configuration

file name.
5. If you plan to call Informix stored procedures in mappings, set all of the date parameters
to the Informix datatype Datetime year to fraction(5).
6. Make sure the DBDATE environment variable is not set. For example, to check if
DBDATE is set, you might type the following at a UNIX prompt:
$ env | grep -i DBDATE
If DBDATE=MDY2/ appears, unset DBDATE by typing:

$ unsetenv DBDATE
either log out and log in again, or issue the source command.
$ source .profile
Using a C shell:
$ source .cshrc
8. Verify that the Informix server name is defined in the $INFORMIXDIR/etc/sqlhosts file.
9. Verify that the Service (last column entry for the server named in the sqlhosts file) is
defined in the services file (usually /etc/services). If not, define the Informix Services
name in the Services file.
Enter the Services name and port number. The default port number is 1525, which
should work in most cases.
See the Informix and UNIX documentation for more information.
10. Verify that you can connect to the Informix database.
If you fail to connect to the database, verify that you have correctly entered all the
information.

Connecting to an Oracle Database
Service and Repository Service processes run. To ensure compatibility between the
PowerCenter and databases, use the appropriate database client libraries. For more
♦ Integration Service. Install the Oracle client on the machine where the Integration Service
process runs. The Integration Service can use native connectivity or ODBC to
communicate with Oracle. Use native connectivity for increased performance.
♦ Repository Service. If you create an Oracle repository, install the Oracle client on the
machine where the Repository Service process runs. The Repository Service uses native
connectivity to communicate with Oracle.
You must install compatible versions of Oracle client and Oracle database server. You must
also install the same version of the Oracle client on the Oracle database server and each
machine where Integration Service or Repository Service processes run. To verify
compatibility, contact Oracle.

Use the following steps as a guideline to connect to an Oracle database through Oracle Net
Services or Net8. For specific connectivity instructions, refer to the database documentation.
To connect to an Oracle database:
1. To configure connectivity for the Integration Service or Repository Service process, log in
to the machine as a user who can start the server process.
2. Set the ORACLE_HOME, NLS_LANG, TNS_ADMIN, and PATH environment
variables.
ORACLE_HOME. Set the variable to the Oracle client installation directory. For
example, if the client is installed in the /HOME2/oracle directory:
$ ORACLE_HOME=/HOME2/oracle; export ORACLE_HOME
Using a C shell:
$ setenv ORACLE_HOME /HOME2/oracle
NLS_LANG. Set the variable to the locale (language, territory, and character set) you
want the database client and server to use with the login. The value of this variable
depends on the configuration. For example, if the value is american_america.UTF8, you
must set the variable as follows:
$ NLS_LANG=american_america.UTF8; export NLS_LANG

Using a C shell:
$ NLS_LANG american_america.UTF8
To determine the value of this variable, contact the Administrator.

TNS_ADMIN. Set the variable to the directory where the tnsnames.ora file resides. For
example, if the file is in the /HOME2/oracle/network/admin directory:
$ TNS_ADMIN=$HOME2/oracle/network/admin; export TNS_ADMIN
Using a C shell:
$ setenv TNS_ADMIN=$HOME2/oracle/network/admin
Setting the TNS_ADMIN is optional, and might vary depending on the configuration.
PATH. To run the Oracle command line programs, set the variable to include the Oracle
bin directory.
$ PATH=${PATH}:$ORACLE_HOME/bin; export PATH
Using a C shell:
$ setenv PATH ${PATH}:ORACLE_HOME/bin
3. Set the shared library environment variable.

The Oracle client software contains a number of shared library components that the
Integration Service and Repository Service processes load dynamically. To locate the
(server_dir).
AIX LIBPATH
HP-UX SHLIB_PATH
$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/server_dir:$ORACLE_HOME/lib;
export LD_LIBRARY_PATH

$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/
server_dir:$ORACLE_HOME/lib
For HP-UX
$ SHLIB_PATH=${SHLIB_PATH}:$HOME/server_dir:$ORACLE_HOME/lib; export
SHLIB_PATH
$ setenv SHLIB_PATH ${SHLIB_PATH}:$HOME/server_dir:$ORACLE_HOME/lib
For AIX
$ LIBPATH=${LIBPATH}:$HOME/server_dir:$ORACLE_HOME/lib; export LIBPATH
$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$ORACLE_HOME/lib
$ source .profile
Using a C shell:
$ source .cshrc
5. Verify that the Oracle client is configured to access the database.

Use the SQL*Net Easy Configuration Utility or copy an existing tnsnames.ora file to the
home directory and modify it.
The tnsnames.ora file is stored in the $ORACLE_HOME/network/admin directory.
Enter the correct syntax for the Oracle connect string, typically databasename.world.
Here is a sample tnsnames.ora. You need to enter the information for the database.
mydatabase.world =
(DESCRIPTION
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = mycompany.world
(PROTOCOL = TCP)
(Host = mymachine)
(Port = 1521)

(CONNECT_DATA =
(SID = MYORA7)
(GLOBAL_NAMES = mydatabase.world)
6. Verify that you can connect to the Oracle database.

To connect to the Oracle database, launch SQL*Plus and enter the connectivity
information. If you fail to connect to the database, verify that you correctly entered all of
the connectivity information.
Enter the correct user name and connect string as defined in tnsnames.ora.

Connecting to a Sybase ASE Database
♦ Integration Service. Install Open Client on the machine where the Integration Service
process runs. The Integration Service can use native connectivity or ODBC to
communicate with Sybase ASE. Use native connectivity for increased performance.
♦ Repository Service. If you create an Sybase ASE repository, install Open Client on the
machine where the Repository Service process runs. The Repository Service uses native
connectivity to communicate with Sybase ASE.
Note: If you want to create, restore, or upgrade a Sybase ASE repository, set allow nulls by
default to TRUE at the database level. Setting this option changes the default null type of the
column to null in compliance with the SQL standard.
You must install Open Client version that is compatible with the Sybase ASE database server.
You must also install the same version of Open Client on the machines hosting the Sybase
ASE database and PowerCenter. To verify compatibility, contact Sybase.

Use the following steps as a guideline to connect to a Sybase ASE database. For specific
To connect to a Sybase ASE database:
1. To configure connectivity to the Integration Service or Repository Service, log in to the

machine as a user who can start the server process.
2. Set the SYBASE and PATH environment variables.
SYBASE. Set the variable to the Sybase Open Client installation directory. For example,
if the client is installed in the /usr/sybase directory:
$ SYBASE=/usr/sybase; export SYBASE
Using a C shell:
$ setenv SYBASE /usr/sybase
PATH. To run the Sybase command line programs, set the variable to include the Sybase
bin directory.
$ PATH=${PATH}:/usr/sybase/bin; export PATH

Using a C shell:
$ setenv PATH ${PATH}:/usr/sybase/bin

The Sybase Open Client software contains a number of shared library components that
the Integration Service and the Repository Service processes load dynamically. To locate
the shared libraries during run time, set the shared library environment variable.
(server_dir).
table describes the shared library variables for each operating system.
AIX LIBPATH
HP-UX SHLIB_PATH
$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/server_dir:$SYBASE/lib; export
LD_LIBRARY_PATH
$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/server_dir:$SYBASE/lib
For HP-UX
$ SHLIB_PATH=${SHLIB_PATH}:$HOME/server_dir:$SYBASE/lib; export
SHLIB_PATH
$ setenv SHLIB_PATH ${SHLIB_PATH}:$HOME/server_dir:$SYBASE/lib
For AIX
$ LIBPATH=${LIBPATH}:$HOME/server_dir:$SYBASE/lib; export LIBPATH
$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$SYBASE/lib
$ source .profile

Using a C shell:
$ source .cshrc
5. Verify the Sybase ASE server name in the Sybase interfaces file (stored in the $SYBASE
directory).
6. Verify that you can connect to the Sybase ASE database.
To connect to the Sybase ASE database, launch ISQL and enter the connectivity
information. If you fail to connect to the database, verify that you correctly entered all of
the connectivity information.
User names and database names are case sensitive.

Connecting to a Teradata Database
Service processes run. To ensure compatibility between PowerCenter and databases, use the
Install the Teradata BTEQ client software, the Teradata ODBC driver, and any other Teradata
client software you may need on the machine where the Integration Service process runs.
Note: Based on recommendation from Teradata, Informatica uses ODBC to connect to
Teradata. ODBC is a native interface for Teradata. Teradata does not have an ODBC driver
for Linux.

To connect to a Teradata database on UNIX:
user who can start a service process.
2. Set the TERADATA_HOME, ODBCHOME, and PATH environment variables.
TERADATA_HOME. Set the variable to the Teradata driver installation directory. The
defaults are as follows:
$ TERADATA_HOME=/teradata/usr; export TERADATA_HOME
Using a C shell:
$ setenv TERADATA_HOME /teradata/usr
ODBCHOME. Set the variable to the ODBC installation directory. For example:
$ ODBCHOME=/usr/odbc; export ODBCHOME
Using a C shell:
$ setenv ODBCHOME /usr/odbc
PATH. To run the ivtestlib utility, to verify that the UNIX ODBC manager can load the
driver files, set the variable as follows:
PATH="${PATH}:$ODBCHOME/bin:$TERADATA_HOME/bin"
Using a C shell:
$ setenv PATH ${PATH}:$ODBCHOME/bin:$TERADATA_HOME/bin

The Teradata software contains a number of shared library components that the
Integration Service process loads dynamically. To locate the shared libraries during run
time, set the shared library environment variable.
(server_dir).
AIX LIBPATH
HP-UX SHLIB_PATH
For example, use the following syntax for Solaris:

$ LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:$HOME/server_dir:$ODBCHOME/
lib:$TERADATA_HOME/lib:$TERADATA_HOME/odbc/lib"; export LD_LIBRARY_PATH
$ setenv LD_LIBRARY_PATH "${LD_LIBRARY_PATH}:$HOME/server_dir:$ODBCHOME/
lib:$TERADATA_HOME/lib:$TERADATA_HOME/odbc/lib"
For HP-UX
$ SHLIB_PATH=${SHLIB_PATH}:$HOME/server_dir:$ODBCHOME/lib; export
SHLIB_PATH
$ setenv SHLIB_PATH ${SHLIB_PATH}:$HOME/server_dir:$ODBCHOME/lib
For AIX
$ LIBPATH=${LIBPATH}:$HOME/server_dir:$ODBCHOME/lib; export LIBPATH
$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$ODBCHOME/lib
4. Edit the existing odbc.ini file or copy the odbc.ini file to the home directory and edit it.
This file exists in $ODBCHOME directory.
$ cp $ODBCHOME/odbc.ini $HOME/.odbc.ini
Add an entry for the Teradata data source under the section [ODBC Data Sources] and
configure the data source.

For example:
MY_TERADATA_SOURCE=Teradata Driver
[MY_TERADATA_SOURCE]
Driver=/u01/app/teradata/td-tuf611/odbc/drivers/tdata.so
Description=NCR 3600 running Teradata V1R5.2
DBCName=208.199.59.208
DateTimeFormat=AAA
SessionMode=ANSI
DefaultDatabase=
Username=
Password=
5. Set the DateTimeFormat to AAA in the Teradata data ODBC configuration.

6. Optionally, set the SessionMode to ANSI. When you use ANSI session mode, Teradata
does not roll back the transaction when it encounters a row error. If you choose Teradata
session mode, Teradata rolls back the transaction when it encounters a row error. In
Teradata mode, the Integration Service process cannot detect the rollback, and does not
report this in the session log.
7. To configure connection to a single Teradata database, enter the DefaultDatabase name.
To create a single connection to the default database, enter the user name and password.
To connect to multiple databases, using the same ODBC DSN, leave the
DefaultDatabase field empty.
For more information about Teradata connectivity, consult the Teradata ODBC driver
documentation.
For a sample odbc.ini file, see “Sample odbc.ini File” on page 525.
8. Verify that the last entry in the odbc.ini is InstallDir and set it to the odbc installation
directory. For example:
InstallDir=/usr/odbc
9. Edit the .cshrc or .profile to include the complete set of shell commands.
10. Save the file and either log out and log in again, or issue the source command.
$ source .profile
Using a C shell:
$ source .cshrc
11. For each data source you use, make a note of the file name under the Driver=<parameter>
in the data source entry in odbc.ini. Use the ivtestlib utility to verify that the UNIX
ODBC manager can load the driver file.

For example, if you have the driver entry:
Driver=/u01/app/teradata/td-tuf611/odbc/drivers/tdata.so
issue the following command:

ivtestlib /u01/app/teradata/td-tuf611/odbc/drivers/tdata.so
12. Test the connection using BTEQ or another Teradata client tool.

Connecting to an ODBC Data Source
To connect the Integration Service process to each ODBC database, you must install and
configure any underlying client access software needed by the ODBC driver. If you want to
access sources in a Windows environment, such as Microsoft Excel or Access, you must install
PowerChannel. For more information about PowerChannel, see the PowerChannel User
Guide.
The PowerCenter Services installer installs ODBC drivers for use with the Integration Service
in the ODBC5.1 directory under the server directory. The Integration Service uses the System
DSN to specify an ODBC data source.
Note: PowerCenter 8.1.1 includes DataDirect 5.1 ODBC drivers. If odbc.ini references an
earlier version, edit odbc.ini to update your existing connections to use the new drivers.
To connect to an ODBC data source:
user who can start a service process.
2. Set the ODBCHOME and PATH environment variables.
ODBCHOME. Set to the DataDirect ODBC installation directory. For example, if the
install directory is /opt/ODBC5.1.
$ ODBCHOME=/opt/ODBC5.1; export ODBCHOME
Using a C shell:
$ setenv ODBCHOME /opt/ODBC5.1
PATH. To run the ODBC command line programs, like ivtestlib, set the variable to
include the odbc bin directory.
$ PATH=${PATH}:$ODBCHOME/bin; export PATH
Using a C shell:
$ setenv PATH ${PATH}:$ODBCHOME/bin
Run the ivtestlib utility to verify that the UNIX ODBC manager can load the driver files.
The ODBC software contains a number of shared library components that the
Integration Service and Repository Service processes load dynamically. To locate the

(server_dir).
AIX LIBPATH
HP-UX SHLIB_PATH
$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/server_dir:$ODBCHOME/lib;
export LD_LIBRARY_PATH
$ setenv LD_LIBRARY_PATH $HOME/server_dir:$ODBCHOME:${LD_LIBRARY_PATH}
For HP-UX
$ SHLIB_PATH=${SHLIB_PATH}:$HOME/server_dir:$ODBCHOME/lib; export
SHLIB_PATH
$ setenv SHLIB_PATH ${SHLIB_PATH}:$HOME/server_dir:$ODBCHOME/lib
For AIX
$ LIBPATH=${LIBPATH}:$HOME/server_dir:$ODBCHOME/lib; export LIBPATH
$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$ODBCHOME/lib
4. Edit the existing odbc.ini file or copy the odbc.ini file to the home directory and edit it.
This file exists in $ODBCHOME directory.
$ cp $ODBCHOME/odbc.ini $HOME/.odbc.ini
Add an entry for the ODBC data source under the section [ODBC Data Sources] and
configure the data source.
For example:
MY_MSSQLSERVER_ODBC_SOURCE=<Driver name or Data source description>
[MY_SQLSERVER_ODBC_SOURCE]
Driver=<path to ODBC drivers>
Description=DataDirect 5.1 SQL Server Wire Protocol
Connecting to an ODBC Data Source 523

Database=<SQLServer_database_name>
LogonID=<username>
Password=<password>
Address=<TCP/IP address>,<port number>
QuoteId=No
AnsiNPW=No
ApplicationsUsingThreads=1
This file might already exist if you have configured one or more ODBC data sources.
For a sample odbc.ini file, see “Sample odbc.ini File” on page 525.
5. Verify that the last entry in the odbc.ini is InstallDir and set it to the odbc installation
directory. For example:
InstallDir=/usr/odbc
6. If you use the odbc.ini file in the home directory, set the ODBCINI environment
variable.
$ ODBCINI=/$HOME/.odbc.ini; export ODBCINI
Using a C shell:
$ setenv ODBCINI $HOME/.odbc.ini
$ source .profile
Using a C shell:
$ source .cshrc
8. Use the ivtestlib utility to verify that the UNIX ODBC manager can load the driver file
you specified for the data source in the odbc.ini file.
For example, if you have the driver entry:
Driver = /opt/odbc/lib/DWxxxx.so
issue the following command:

ivtestlib /opt/odbc/lib/DWxxxx.so
9. Install and configure any underlying client access software needed by the ODBC driver.
Note: While some ODBC drivers are self-contained and have all information inside the
.odbc.ini file, most are not. For example, if you want to use an ODBC driver to access
Oracle, you must install the Oracle SQL*NET software and set the appropriate
environment variables. Verify such additional software configuration separately before
using ODBC.

Sample odbc.ini File
The following example shows a sample odbc.ini file. For a sample ODBC data source entry,
see “Connecting to a Teradata Database” on page 518.
[ODBC Data Sources]
dBase=DataDirect 5.1 dBaseFile(*.dbf)
FoxPro3=DataDirect 5.1 dBaseFile(*.dbf)
Informix Wire Protocol=DataDirect 5.1 Informix Wire Protocol
SQLServer Wire Protocol=DataDirect 5.1 SQL Server Wire Protocol
[dBase]
Driver=/u02/app/ODBC5.1/lib/ivdbf21.so
Description=DataDirect 5.1 dBaseFile(*.dbf)
ApplicationUsingThreads=1
CacheSize=4
CreateType=dBASE5
Database=/u02/app/ODBC5.1/demo
DataFileExtension=DBF
ExtensionCase=UPPER
FileOpenCache=0
IntlSort=0
LockCompatibility=dBASE
Locking=RECORD
UseLongNames=0
UseLongQualifiers=0
[FoxPro3]
Driver=/u02/app/ODBC5.1/lib/ivdbf21.so
Description=DataDirect 5.1 dBaseFile(*.dbf)
CacheSize=4
CreateType=FoxPro30
Database=/u02/app/ODBC5.1/demo
DataFileExtension=DBF
ExtensionCase=UPPER
FileOpenCache=0
IntlSort=0
LockCompatibility=Fox
Locking=RECORD
UseLongNames=0
UseLongQualifiers=0
[Informix Wire Protocol]
Sample odbc.ini File 525

Driver=/u02/app/ODBC5.1/lib/ivifcl21.so
Description=DataDirect 5.1 Informix Wire Protocol
AlternateServers=
CancelDetectInterval=0
ConnectionRetryCount=0
ConnectionRetryDelay=3
Database=<database_name>
HostName=<Informix_host>
LoadBalancing=0
LogonID=
Password=
PortNumber=<Informix_server_port>
ServerName=<Informix_server>
TrimBlankFromIndexName=1
[SQLServer Wire Protocol]

Driver=/u02/app/ODBC5.1/lib/ivmsss21.so
Description=DataDirect 5.1 SQL Server Wire Protocol
Address=<SQLServer_host, SQLServer_server_port>
AlternateServers=
AnsiNPW=Yes
ConnectionRetryCount=0
ConnectionRetryDelay=3
Database=<database_name>
LoadBalancing=0
LogonID=
Password=
QuotedId=No
[ODBC]
IANAAppCodePage=4
InstallDir=/u02/app/ODBC5.1
Trace=0
TraceDll=/u02/app/ODBC5.1/lib/odbctrac.so
TraceFile=odbctrace.out
UseCursorLib=0

Part V: Appendices
This part contains the following appendices:

♦ Starting and Stopping Informatica Services, 529
♦ Starting and Stopping Application Servers, 535
♦ Logging in to the Administration Console, 547
♦ ODBC Calls, 549
♦ JDBC Drivers, 553
♦ LANG Environment Variable for Linux, 557
527
528
Appendix A
Starting and Stopping

Informatica Services
This appendix includes the following topics:
♦ Overview, 530
♦ Starting and Stopping Informatica Services on UNIX, 531
♦ Starting and Stopping Informatica Services on Windows, 532
529
Overview
The method you use to start and stop Informatica Services depends on the operating system:
♦ UNIX. Start and stop Informatica Services from the command line.
♦ Windows. Start and stop Informatica Services from the Windows Start Menu or from
Windows Services.
You can also use the Administration Console to shut down a node. When you shut down a
node, you stop Informatica Services on the node.
Use the following rules and guidelines when starting and stopping Informatica Services on a
node:
♦ When you shut down a node, the node is unavailable to the domain. If you shut down a
gateway node and do not have another gateway node in the domain, the domain is
unavailable.
♦ When you start Informatica Services, verify that the port used by Informatica Services on
the node is available. For example, if you stop Informatica Services on a node and then
restart Informatica Services, verify that another process on the machine is not using the
port. If the port is not available, Informatica Services will fail to start on the node.
♦ If you do not use the Administration Console to shut down a node, any process running
on the node will be aborted. If you want to wait for all processes to complete before
shutting down a node, use the Administration Console.
♦ If you have two nodes in a domain with one node configured as a primary node for an
application service and the other node configured as a backup node, you must start
Informatica Services on the primary node before you start the backup node. Otherwise,
the application service will run on the backup node and not the primary node.
530 Appendix A: Starting and Stopping Informatica Services

Starting and Stopping Informatica Services on UNIX
On UNIX, you use the infaservice command to start and stop Informatica Services. By
default, infaservice is installed in the server/tomcat/bin directory in the PowerCenter Services
installation directory.
To start or stop Informatica Services on UNIX:
1. At the command prompt, switch to the directory where the infaservice executable is
located.
2. At the command prompt, type the following command to start or stop the Service
Manager:
infaservice [startup | shutdown]
Note: If you use a softlink to specify the location of infaservice, you must set the
INFA_HOME environment variable to the location of the PowerCenter Services installation
directory. For more information, see “Configuring INFA_HOME” on page 357.
Starting and Stopping Informatica Services on UNIX 531

Starting and Stopping Informatica Services on Windows
The PowerCenter installer installs Informatica Services as a service with the following name:
Informatica Services 8.1.1
You can start and stop Informatica Services by starting and stopping the service using
Windows Services or by using the Windows shortcut.
To use Windows Services to start or stop the Informatica Services service:
1. From the Start Menu, click Administrative Tools > Services.

2. Double-click Informatica Services.
The Informatica Services 8.1.1 Properties dialog box appears.
3. If the service is running, click Stop.

-or-
If the service is stopped, click Start.
For more information about configuring the Informatica Services service on Windows, see
“Configuring Informatica Services” on page 325.
To start or stop Informatica Service using the Start menu:

Choose Start menu > Informatica PowerCenter 8.1.1 > Server > Stop | Start Informatica
Services.

Stopping Informatica Services Using the Administration Console
When you shut down a node using the Administration Console, you stop Informatica
Services on that node. You can abort the processes that are running or allow them to
complete. If you abort a node running Repository Service processes, you may lose changes
that have not yet been written to the repository. If you abort a node running Integration
Service processes, the workflows will abort.
To shut down a node in the Administration Console:
1. Log in to the Administration Console. For more information, see “Logging in to the
Administration Console” on page 547.
2. Select the node in the Navigator.
3. Click Shutdown in the Main window.
Starting and Stopping Informatica Services on Windows 533

Appendix B
Starting and Stopping Application

Servers

♦ Overview, 536
♦ Starting and Stopping Applications on JBoss Application Server, 537
♦ Starting and Stopping Applications on BEA WebLogic Server, 540
♦ Starting and Stopping Applications on IBM WebSphere Application Server, 542
535
Overview
Data Analyzer and Metadata Manager use JBoss Application Server, BEA WebLogic Server,
and IBM WebSphere Application Server to manage processes and manage application,
network, and system resources.
On UNIX, you start and stop the application servers from the command line. On Windows,
the PowerCenter installer installs the server as a service and provides shortcuts for starting the
server from the Windows Start menu.
The PowerCenter installer starts all servers as part of the installation. Typically, you do not
need to start the servers manually.
To start Data Analyzer or Metadata Manager, you need to start the application server where
you installed them. After you start the application server, use a web browser to access Data
You can start and stop servers depending on the type of application server:
♦ JBoss Application Server. You can start and stop JBoss Application Server from the
command line or the Windows Start menu. For more information, see “Starting and
Stopping Applications on JBoss Application Server” on page 537.
♦ BEA WebLogic Server. You can start and stop BEA WebLogic Server from the command
line. For more information, see “Starting and Stopping Applications on BEA WebLogic
Server” on page 540.
♦ IBM WebSphere Application Server. You can start and stop the deployment manager,
node agent, JMS server, and default server from the command line. For more information,
see “Starting and Stopping Applications on IBM WebSphere Application Server” on
page 542.
536 Appendix B: Starting and Stopping Application Servers

Starting and Stopping Applications on JBoss Application
Server
To start Data Analyzer or Metadata Manager on JBoss Application Server, you need to start
JBoss Application Server with the server configuration on which you installed the
applications.
If you installed Data Analyzer or Metadata Manager on one server configuration on the same
instance of JBoss Application Server, starting JBoss Application Server with the specific server
configuration starts all the applications.
If you installed Data Analyzer or Metadata Manager on different JBoss Application Server
instances or on different server configurations, you need to start the applications individually.
Starting JBoss Application Server

On UNIX or Windows, you can start JBoss Application Server from the command line. On
Windows, you can start JBoss Application Server from the Windows Start menu.
After you start JBoss Application Server, you can use a web browser to access Data Analyzer or
Metadata Manager. For more information about using Data Analyzer, see the Data Analyzer
documentation. For more information about using Metadata Manager, see the Metadata
Manager documentation.
Starting JBoss Application Server from the Command Line

On Windows, open a command window to run the informatica batch file. On UNIX, run the
script as a shell command.
To start JBoss Application Server from the command line:
1. Navigate to the drive and directory where you installed JBoss Application Server and go
to the /bin directory.
The default /bin directory is /Informatica/PowerCenter8.1.1/JBoss403/bin.
2. Run JBoss Application Server with the server configuration parameter.
The default JBoss server configuration for Data Analyzer and Metadata Manager is
informatica.
On Windows, run JBoss Application Server with the following command:
run -c informatica

run.sh -c informatica
When the application server starts its processes, the command prompt stops scrolling. Wait
until JBoss Application Server starts before you access the applications.
Starting and Stopping Applications on JBoss Application Server 537

Starting JBoss Application Server from the Windows Start Menu
On Windows, the PowerCenter installer installs JBoss Application Server as a service with the
following name:
Informatica_811_JBoss_<ServerConfigurationName>
The default JBoss server configuration for Data Analyzer or Metadata Manager is informatica.
The service name for JBoss Application Server is Informatica_811_JBoss_Informatica.
The PowerCenter installer also creates a shortcut on the Windows Start menu to start the
service. You can start JBoss Application Server from Windows Services or from the Windows
Start menu.
To start JBoss Application Server from the Windows Start menu:
1. On the Windows Start menu, select Programs > Informatica PowerCenter 8.1.1 > Server.
2. Select Start JBoss Service.
The JBoss Application Server service takes a moment to start. Wait until JBoss Application
Server starts before you access the applications.
Stopping JBoss Application Server

On UNIX or Windows, you can stop JBoss Application Server from the command line. On
Windows, you can stop JBoss Application Server from the Windows Start menu.
Stopping JBoss Application Server from the Command Line

On Windows, open a command window to run the batch file. On UNIX, run the script as a
shell command.
To stop JBoss Application Server from the command line:
1. Navigate to the drive and directory where you installed JBoss Application Server and go
to the /bin directory.
The default /bin directory is /Informatica/JBoss403/bin.
2. Stop JBoss Application Server with the shutdown parameter.
On Windows, stop JBoss Application Server with the following command:
shutdown --s jnp://<HostName>:<JNP invoker port> --S

shutdown.sh --s jnp://<HostName>:<JNP invoker port> --S
The --s parameter requires the host name of the machine that hosts JBoss Application
Server. It is preceded by two dashes (--).
The --S parameter is also preceded by two dashes (--).
The JBoss Application Server service takes a moment to stop. JBoss Application Server is
stopped when the command prompt stops scrolling and the command line displays again.

Stopping JBoss Application Server from the Windows Start Menu
The PowerCenter installer creates a shortcut on the Windows Start menu to stop the JBoss
service. You can stop JBoss Application Server from the Windows Start menu.
To stop JBoss Application Server from the Windows Start menu:
2. Select Stop JBoss Service.
Starting and Stopping Applications on JBoss Application Server 539

Starting and Stopping Applications on BEA WebLogic
Server
To start Data Analyzer and Metadata Manager on BEA WebLogic Server, you need to start
BEA WebLogic Server in the domain on which you installed the applications.
If you installed Data Analyzer and Metadata Manager in one domain on the same instance of
BEA WebLogic Server, starting BEA WebLogic Server in the specific domain starts all the
applications.
If you installed Data Analyzer and Metadata Manager on different WebLogic instances or on
different domains, you need to start the applications individually.
Starting BEA WebLogic Server

The PowerCenter installer installs Data Analyzer and Metadata Manager to run on the default
application server of BEA WebLogic Server. The default application server name is myserver.
Starting BEA WebLogic Server from the Command Line

On Windows, open a command window to run the batch file. On UNIX, run the script as a
shell command.
To start BEA WebLogic Ser ver from the command line:
1. Navigate to the drive and directory where BEA WebLogic Server is installed and go to the
domain directory for Data Analyzer and Metadata Manager.
In PowerCenter, the default WebLogic domain for Data Analyzer and Metadata Manager
is informatica. The default domain directory is
/bea/user_projects/domains/informatica
2. Start BEA WebLogic Server with the startWebLogic command.

On Windows, start BEA WebLogic Server with the following command:
startWebLogic.cmd

startWebLogic.sh
When the application server successfully starts all its processes, a message similar to the
following displays:
Started WebLogic Admin Server “myserver” for domain “Informatica” running
in Production Mode
Server started in RUNNING mode
The initialization process may take a while. After the initialization process completes, the
command prompt stops scrolling.

Starting BEA WebLogic Server from the Windows Start Menu
On Windows, the PowerCenter installer installs BEA WebLogic Server as a service with the
following name:
beasvc <DomainName>_<ServerName>
In PowerCenter, the default WebLogic domain name for Data Analyzer and Metadata
Manager is informatica. The default application server name is myserver. The service name for
BEA WebLogic Server is beasvc informatica_myserver.
The PowerCenter installer also creates a shortcut on the Windows Start menu to start the
service. You can start BEA WebLogic Server from the Windows Services or from the Windows
Start menu.
To start BEA WebLogic Ser ver from the Windows Start menu:
2. Select Start WebLogic Service.
The BEA WebLogic Server service takes a moment to start. Wait until BEA WebLogic Server
starts before you access the applications.
Stopping BEA WebLogic Server

On UNIX or Windows, you can stop the applications running on BEA WebLogic Server from
the WebLogic Administration Console.
The following instructions assume that Data Analyzer and Metadata Manager are running on
the default server myserver in the informatica domain.
To stop BEA WebLogic Server from the console:
1. Open a web browser and type the URL for the WebLogic Administration Console.
The URL for the BEA WebLogic Server contains the host name and port for BEA
WebLogic Server with the /console context path:
http://MachineName.DomainName.com:7001/console
2. Log in to the WebLogic Administration Console.

3. On the left panel of the WebLogic Administration Console, click Servers under the
Informatica domain to display the available servers.
4. Right-click the default server name and choose Graceful shutdown of this server or Force
shutdown of this server.
5. Click Yes to confirm that you want to stop BEA WebLogic Server.
6. Close the browser.
Starting and Stopping Applications on BEA WebLogic Server 541

Starting and Stopping Applications on IBM WebSphere
Application Server
To start the Data Analyzer and Metadata Manager on IBM WebSphere Application Server,
you need to start the IBM WebSphere Application Server instance on which you installed the
applications.
If you installed Data Analyzer and Metadata Manager on the same instance of IBM
WebSphere Application Server, starting IBM WebSphere Application Server starts all the
applications.
If you installed Data Analyzer and Metadata Manager on separate IBM WebSphere
Application Server instances, you need to start the applications individually.
On Windows and UNIX, you must log in with the padaemon user account to run IBM
WebSphere Application Server.
Starting IBM WebSphere Application Server

If you do not provide a server name during installation, the PowerCenter installer installs
Data Analyzer and Metadata Manager to run on the default application server of IBM
WebSphere Application Server. The default application server name is server1.
If you provide a server name during installation, the PowerCenter installer configures the web
applications to run on the specified server. Start the specified server instead of the default
server.
To start the applications in IBM WebSphere Application Server, complete the following steps:
1. Start the deployment manager.
2. Start the node agent.
3. Start the JMS server.
4. Start the default server (Server1).
You must start the servers in the sequence listed. Wait until a server completes its
initialization processes before you start the next server.

Step 1. Start the Deployment Manager
On Windows, open a command window and run the batch file to start the IBM WebSphere
Application Server deployment manager. On UNIX, run the script as a shell command.
To start the deployment manager:
1. Navigate to the IBM WebSphere Application Server Network Deployment /bin directory.
The default /bin directory for IBM WebSphere Application Server Network Deployment
is:
/WebSphere/DeploymentManager/bin.
2. Start the WebSphere deployment manager with the startManager command.

On Windows, start the deployment manager with the following command:
startManager -username WASAdmin -password WASAdminPassword

startManager.sh -username WASAdmin -password WASAdminPassword
WASAdmin is the user name for the WebSphere Administrative Console administrator.
WASAdminPassword is the password for the WebSphere Administrative Console
administrator.
When the deployment manager successfully starts all its processes, the following message
appears:
Server launched. Waiting for initialization status.
Server dmgr open for e-business;
The initialization process may take a while. You must wait for the message before you start the
other servers. After the initialization process completes, the command prompt stops scrolling.
Step 2. Start the Node Agent

On Windows, open a command window and run the batch file to start the WebSphere node
agent. On UNIX, run the script as a shell command.
To start the WebSphere node agent:
1. Navigate to the IBM WebSphere Application Server /bin directory.

The default /bin directory for IBM WebSphere Application Server is
/WebSphere/AppServer/bin.
2. Start the WebSphere node agent with the startNode command.

On Windows, start the node agent with the following command:
startNode.bat -username WASAdmin -password WASAdminPassword

startNode.sh -username WASAdmin -password WASAdminPassword
Starting and Stopping Applications on IBM WebSphere Application Server 543

administrator.
When the node agent successfully starts all its processes, the following message displays:
Server launched. Waiting for initialization status.
Server nodeagent open for e-business;
The initialization process may take a while. Make sure that the node agent starts before you
start the other servers. After the initialization process completes, the command prompt stops
scrolling.
Step 3. Start the JMS Server

On Windows, open a command window and run the batch file to start the WebSphere JMS
Server. On UNIX, run the script as a shell command.
To start the JMS server:

The default /bin directory for IBM WebSphere Application Server is
/WebSphere/AppServer/bin
2. Start the WebSphere JMS Server with the startServer command.

On Windows, start the JMS Server with the following command:
startServer.bat jmsserver -username WASAdmin -password WASAdminPassword

startServer.sh servername -username WASAdmin -password WASAdminPassword
administrator.
The JMS server is started when the status column displays a green arrow.
The initialization process may take a while. Wait until the JMS server completes its
initialization processes before you start the default server.
Do not close the WebSphere Administrative Console. Start the default WebSphere server on
the same console.
Step 4. Start the Default Server

By default, the PowerCenter installer installs Data Analyzer and Metadata Manager to run on
the default WebSphere server.
If you specified the name of a server to run Data Analyzer and Metadata Manager during
installation, the PowerCenter installer configures the web applications to run on the specified
server. Start the specified server instead of the default server.

The node agent and the JMS server must be running before you start the default server.
To start the WebSphere default server:

The default /bin directory for IBM WebSphere Application Server is:
2. Start the WebSphere default server with the startServer command.

On Windows, start the default server with the following command:
startServer.bat servername -username WASAdmin -password WASAdminPassword

startServer.sh servername -username WASAdmin -password WASAdminPassword
administrator.
The default server is started when the status column displays a green arrow.
The initialization process may take a while. Wait until the default server starts before you
access the applications.
Stopping Applications on IBM WebSphere Application Server

To stop the applications in IBM WebSphere Application Server, complete the following steps:
1. Stop the default WebSphere server, JMS server, and node agent.
2. Stop the WebSphere deployment manager.
Step 1. Stop the Default Server, JMS Server, and Node Agent
On Windows, open a command window and run the batch files to stop the servers. On
UNIX, run the script files as shell commands.
If Data Analyzer and Metadata Manager run on a server other than the default server, stop the
specified server instead of the default server.
To stop the WebSphere servers:

The default /bin directory for IBM WebSphere Application Server is:
2. Stop servers in the following sequence: default server, JMS server, and node agent.
Wait until a server stops and the message Server <ServerType> stop completed before
stopping the next server.
Starting and Stopping Applications on IBM WebSphere Application Server 545

On Windows, stop the servers with the following commands:
stopServer.bat server1 -username WASAdmin -password WASAdminPassword
stopServer.bat jmsserver -username WASAdmin -password WASAdminPassword

stopNode.bat -username WASAdmin -password WASAdminPassword
On UNIX, use the following commands:

stopServer.sh server1 -username WASAdmin -password WASAdminPassword
stopServer.sh jmsserver -username WASAdmin -password WASAdminPassword
stopNode.sh -username WASAdmin -password WASAdminPassword
administrator.
Step 2. Stop the Deployment Manager

On Windows, open a command window and run the batch file to stop IBM WebSphere
Application Server deployment manager. On UNIX, run the script as a shell command.
To stop the WebSphere deployment manager:
1. Navigate to the IBM WebSphere Application Server Network Deployment /bin directory.
The default /bin directory for IBM WebSphere Application Server Network Deployment
is:
/WebSphere/DeploymentManager/bin
2. Stop the WebSphere deployment manager with the stopManager command.

On Windows, stop the deployment manager with the following command:
stopManager -username WASAdmin -password WASAdminPassword

stopManager.sh -username WASAdmin -password WASAdminPassword
administrator.
The message Server dmgr stop completed displays on the command line. The shutdown process
might take a while. After the shutdown process completes, the command prompt stops
scrolling.

Appendix C
Logging in to the
Administration Console
♦ Logging in to the Administration Console, 548
547
Logging in to the Administration Console
When you create a domain, the PowerCenter installer installs the Administration Console on
the gateway node for the domain. You must log in to the Administration Console to configure
application services and nodes in the domain. You may need to log in to the Administration
Console to troubleshoot issues during installation.
To log in to the Administration Console:
1. Open Microsoft Internet Explorer or Mozilla Firefox.

For information about browser configuration, see “Web Browsers” on page 37.
2. In the Address field, enter the following URL for the Administration Console login page:
http://<host>:<port>/adminconsole
In the URL, <host> is the name of the machine that hosts the domain, and <port> is the
gateway port number. If you are not using the Internet Explorer Enhanced Security
Configuration, you can enter the following URL, and the browser is directed to the full
URL for the login page:
http://<host>:<port>
The Informatica PowerCenter Administration Console login page appears.
3. Enter the domain user name and password.

When you log in to the Administration Console for the first time, you use the domain
administrator user name and password you created when you created the domain.
4. Click Login.
5. Create an additional domain user to use when you perform administration tasks in the
For more information about creating users and setting permissions, see “Managing Users
and User Accounts” in the PowerCenter Administrator Guide.
548 Appendix C: Logging in to the Administration Console

Appendix D
ODBC Calls

♦ Client ODBC Calls, 550
♦ Integration Service ODBC Calls, 552
549
Client ODBC Calls
The PowerCenter Client makes function calls when communicating with databases.
Table D-1 describes the core function calls the PowerCenter Client makes to connect to
ODBC drivers:
Table D-1. PowerCenter Client ODBC Function Calls
Function Description
SQLAllocConnect Allocates resources for a connection.
SQLAllocStmt Allocates resources for a statement.
SQLBindCol Binds a result column.
SQLBindParam Binds a parameter.
SQLBindParameter Binds a parameter.
SQLCancel Cancels a query.
SQLColumns Called with the table name and the owner name. NULL is never passed
for the owner name or table name. The owner name is obtained from the
results of SQLTables.
SQLConnect Connects.
SQLDescribe Retrieves column information for a prepared query.
SQLDisconnect Disconnects.
SQLError Errors.
SQLExecDirect Executes a statement.
SQLExecute Executes a statement.
SQLFetch Fetches row by row.
SQLForeignKeys Called with the table name and the owner name. NULL is never passed
results of SQLTables above. This is called twice:
- With the FROM table as NULL
- With the TO table as NULL
SQLFreeConnect Frees the resources allocated by connect.
SQLFreeStmt Frees resources allocated by a statement.
SQLGetFunctions Called to see if the driver supports SQLForeignKeys before calling it.
SQLForeignKeys is called only if the driver supports it. The DataDirect
5.x Informix driver does not support SQLForeignKeys.
SQLNumResultsCols Retrieves specified number of result columns from a query.
SQLPrepare Parses an SQL statement.
550 Appendix D: ODBC Calls

Table D-1. PowerCenter Client ODBC Function Calls
SQLPrimaryKeys Called with the table name and the owner name. NULL is never passed
results of SQLTables.
SQLProcedureColumns Called with the procedure name and the owner name. NULL is never
passed for the owner name or procedure name. The owner name is
obtained from the results of SQLProcedures.
SQLProcedures Called with the supplied owner name or NULL if all owners are
requested.
SQLRowCount Retrieves the number of rows affected by a query.
SQLSetConnectOption Sets connection options.
SQLSetParam Sets a parameter.
SQLTables Called with the supplied owner name or NULL if all owners are
requested.
This is called a total of five times, once for each of the following:
- TABLE
- SYSTEM TABLE
- VIEW
- ALIAS
- SYNONYM
The Import dialog box displays the union of all returned rows.
SQLTransact Turns on/off the auto commit feature.
Client ODBC Calls 551

Integration Service ODBC Calls
The Integration Service on UNIX and Windows can access databases through ODBC drivers.
Note: When you use Stored Procedure and Lookup transformations in a mapping, the
Integration Service uses ODBC calls to communicate with databases.
Table D-2 describes the core function calls the Integration Service makes to connect to
ODBC drivers:
Table D-2. Integration Service ODBC Function Calls
SQLAllocConnect Allocates resources for a connection.
SQLAllocStmt Allocates resources for a statement.
SQLBindCol Binds a result column.
SQLBindParameter Binds a parameter.
SQLConnect Connects.
SQLDisconnect Disconnects.
SQLError Errors.
SQLExecDirect Executes a statement.
SQLExecute Executes a statement.
SQLFetch Fetches row by row.
SQLFreeConnect Frees the resources allocated by connect.
SQLFreeStmt Frees resources allocated by a statement.
SQLParamOptions Sets number of parameter rows to run.
SQLPrepare Parses an SQL statement.
SQLSetConnectOption Sets connection options.
SQLSetParam Sets a parameter.
SQLSetStmtAttr Sets statement handle attributes.
SQLTransact Turns on/off the auto commit feature.
SQLSetStmtOption Sets the options for a statement to control how to read and how many rows to read.
SQLExtendedFetch Fetches arrays.
SQLGetInfo Gets information about the ODBC driver.
SQLGetFunctions Gets supported ODBC driver functions.
SQLGetStmtOptions Gets attributes from the statement in the connection.
SQLRowCount Returns the number of rows affected by the SQLExecute command.
552 Appendix D: ODBC Calls

Appendix E
JDBC Drivers

♦ Installed JDBC Drivers, 554
553
Installed JDBC Drivers
When you install Data Analyzer or Metadata Manager, you must select the type of database
where you want to create the Data Analyzer or Metadata Manager repository. When you select
the database type, the installer provides the syntax for database URL.
Table E-1 describes the details on the JDBC drivers installed with PowerCenter for Data
Analyzer and Metadata Manager:
Table E-1. JDBC Drivers Installed for Supported Databases
Oracle
Vendor: Informatica (Shipped with PowerCenter)
JDBC Driver and Type: DataDirect Connect for JDBC, Type 4

For more information about using the DataDirect Connect for JDBC with Oracle,
see “JDBC Driver for Oracle” on page 555.
JDBC Driver Name: com.informatica.jdbc.oracle.OracleDriver
Database URL: jdbc:informatica:oracle://host_name:port:SID=sid
Default Database Port: 1521
JDBC Driver Name: com.informatica.jdbc.sqlserver.SQLServerDriver
Database URL: jdbc:informatica:sqlserver://host_name:port;

SelectMethod=cursor;DatabaseName=database_name
IBM DB2
JDBC Driver Type: DataDirect Connect for JDBC, Type 4
JDBC Driver Name: com.informatica.jdbc.db2.DB2Driver
Database URL: jdbc:informatica:db2://host_name:port;

DatabaseName=database_name
Sybase ASE
JDBC Driver Name: com.informatica.jdbc.sybase.SybaseDriver
554 Appendix E: JDBC Drivers

Table E-1. JDBC Drivers Installed for Supported Databases
Database URL: jdbc:informatica:sybase://

host_name:port;DatabaseName=database_name
Table E-2 describes the information you need to supply in the database URL for the
supported JDBC drivers:
Table E-2. JDBC Connection String Elements
Element Description
host_name IP address or host name of the machine hosting the database server.
port Port number of the database server.
sid Oracle database only. Unique system identifier that represents an

instance of an Oracle database in a server.
database_name Name of the database to connect to.
For more information about the types of JDBC drivers, visit the Java web site:
http://java.sun.com/products/jdbc/driverdesc.html
JDBC Driver for Oracle

When you use the JDBC driver from Informatica (also known as the DataDirect Connect for
JDBC) to connect to an Oracle database, you must enable the Oracle JServer option on the
Oracle database. You must also make sure that the JAVA_XA package on the Oracle database
is valid and the Data Analyzer repository database account has execute privileges on it. For
more information about the Oracle JServer option, see the FAQ section in the Oracle web
site:
http://www.orafaq.com/faqjdbc.htm#JSERV
Informatica recommends that you use the JDBC driver from Informatica to connect to Oracle
data sources in Data Analyzer. If you use the JDBC driver from Oracle (also known as the
Oracle thin driver) to connect to data sources, you might not be able to use stored procedures
in the SQL queries of your Data Analyzer reports. For more information about using stored
procedures in the SQL query for a report, see “Running a Report” in the Data Analyzer User
Guide.
Installed JDBC Drivers 555

556 Appendix E: JDBC Drivers
Appendix F
LANG Environment
Variable for Linux
This appendix includes the following topic:
♦ Overview, 558
557
Overview
When you set up the locale on a Linux machine, you can specify one of many values for the
locale in the LANG environment variable. PowerCenter accepts a subset of all possible values
that Linux accepts. If you install PowerCenter on a Linux machine, use one of the valid values
for the LANG environment variable.
Table F-1 provides a list of values that PowerCenter accepts for the LANG environment
variable:
Table F-1. Valid Values for the LANG Environment Variable for Linux Machines
Language Territory/Region Locale
CanadianFrench French-Canada fr_CA
Catalan Catalonia ca_ES
Croatian Croatia croatian
Croatian Croatia hr_HR
Czech Czech Republic czech
Czech Czech Republic cs_CZ
Danish Denmark da_DK
Danish Denmark da.ISO8859-15
Danish Denmark danish
Danish Denmark dansk
Dutch Dutch-Belgium nl_BE.ISO8859-15
Dutch Dutch-Belgium nl_BE
Dutch Netherlands dutch
Dutch Netherlands nl
Dutch Netherlands nl_NL
Dutch Netherlands nl.ISO8859-15
English Australia en_AU
English Canada en_CA
English Denmark en_DK
English Ireland en_IE
English United Kingdom en_GB
English United Kingdom en_GB.ISO8859-15
English United Kingdom en_UK
English United States C
558 Appendix F: LANG Environment Variable for Linux

English United States en_US
English United States en_US.utf8
English United States POSIX
English United States en_US.iso88591
Estonian Estonia et
Estonian Estonia et_EE
Faroese Faroes fo_FO
Finnish Finland fi
Finnish Finland fi.ISO8859-15
Finnish Finland fi_FI
Finnish Finland finnish
Finnish Finland su
French France fr
French France français
French France fr.ISO8859-15
French France fr_FR
French France french
French French-Belgium fr_BE
French French-Belgium fr_BE.ISO8859-15
French French-Switzerland fr_CH
French Luxembourg fr_LU
German Austria de_AT
German Austria de_AT.ISO8859-15
German German-Switzerland de_CH
German Germany de
German Germany de_DE
German Germany deutsch
German Germany german
German Luxembourg de_LU
Greek Greece el_GR
Greek Greece el_GR.iso88597
Overview 559
Greek Greece greek
Hebrew Israel hebrew
Hebrew Israel iw_IL
Hungarian Hungary hu
Hungarian Hungary hu_HU
Hungarian Hungary hungarian
Icelandic Iceland icelandic
Icelandic Iceland is
Icelandic Iceland is_IS
Indonesian Indonesia id
Indonesian Indonesia in
Irish Ireland ga_IE
Italian Italian-Switzerland it_CH
Italian Italy it
Italian Italy it.ISO859-15
Italian Italy it.UTF-8
Italian Italy italian
Italian Italy it_IT
Japanese Japan japanese
Japanese Japan japanese.euc
Japanese Japan ja_JP.eucjp
Japanese Japan ja_JP.PCK
Japanese Japan ja_JP.UTF-8
Korean Korea ko
Korean Korea ko_KR.euckr
Latvian Latvia lv_LV
Lithuanian Lithuania lt_LT
Macedonian Macedonia mk_MK
Norwegian Norway no
Norwegian Norway no_NO
Norwegian Norway norwegian

Norwegian Norway no@nynorsk
Polish Poland pl
Polish Poland pl_PL
Polish Poland polish
Portuguese Brazil pt_BR
Portuguese Portugal pt
Portuguese Portugal pt.ISO8859-15
Portuguese Portugal portuguese
Portuguese Portugal pt_PT
Romanian Romania ro
Romanian Romania ro_RO
Romanian Romania romanian
Russian Russia ru
Russian Russia ru_RU
Russian Russia ru_RU.KOI8-R
Russian Ukraine ru_UA
Serbian Yugoslavia sr
Serbian Yugoslavia sr_YU
Simplified Chinese China zh.GBK
Simplified Chinese China zh
Slovak Slovakia sk
Slovak Slovakia sk_SK
Slovak Slovakia slovak
Slovenian Slovenia slovene
Slovenian Slovenia slovenian
Slovenian Slovenia sl_SI
Spanish Dominican Republic es_DO
Spanish El Salvador es_SV
Spanish Guatemala es_GT
Spanish Honduras es_HN
Spanish Mexico es_MX
Overview 561
Spanish Panama es_PA
Spanish Peru es_PE
Spanish Spain es
Spanish Spain spanish
Spanish Spain es.ISO8859-15
Spanish Spain es.UTF-8
Spanish Spain es_ES
Spanish Spain eu_ES
Swedish Finland sv_FI
Swedish Sweden se
Swedish Sweden sv
Swedish Sweden sv.ISO8859-15
Swedish Sweden sv_SE
Swedish Sweden swedish
TraditionalChinese Taiwan zh_TW.Big5
Turkish Turkey tr
Turkish Turkey tr_TR
Turkish Turkey turkish
Ukrainian Ukraine ua
Ukrainian Ukraine uk_UA

Index
A B
AddLicense (infacmd) BEA WebLogic Server
troubleshooting 368 See WebLogic Server
Administration Console
log events 365
logging in 548 C
Upgrade Wizard 402
cached reports
upgrading a repository 424
list for PowerCenter Repository Reports 345
Administrative reports
catalina.out
importing 282
troubleshooting installation 364
installing 282
cfgfiles
AIX
upgrade directory 92
configuring JRE path 62
COBOL
configuring X Virtual Frame Buffer (Xvfb) 73
connectivity 484
Java components 62
code pages
LIBPATH 62
PowerCenter 45
application server
setting for repository configuration 122, 146, 220, 231
See also JBoss Application Server
color schemes
See also WebLogic Server
See also Data Analyzer Administrator Guide
See also WebSphere Application Server
upgrading 464
installation prerequisites 40
configuring Sybase ASE repository 54
installing 70
Connect (pmrep)
troubleshooting 373
troubleshooting 369
uninstalled files 387
connect string
authentication
examples 478
configuring for application server 70
setting for repository configuration 122, 146, 220, 231
syntax 478
563
connecting CreateIntegrationService (infacmd)
Integration Service to IBM DB2 (UNIX) 505 troubleshooting 371
Integration Service to IBM DB2 (Windows) 489 CreateRepositoryService (infacmd)
Integration Service to Informix (UNIX) 508 troubleshooting 369
Integration Service to Informix (Windows) 491 Custom Function SDK
Integration Service to Microsoft Access 493 Informatica Developer Platform 316
Integration Service to Microsoft SQL Server 494 installation directory 321
Integration Service to ODBC data sources (UNIX) installing 317
522
Integration Service to Oracle (UNIX) 511
Integration Service to Oracle (Windows) 496 D
Integration Service to Sybase ASE (UNIX) 515
Data Analyzer
Integration Service to Sybase ASE (Windows) 499
adding data sources 354
Integration Service to Teradata (Windows) 501
components 9
Microsoft Excel to Integration Service 493
configuring a data source 351
PowerCenter Client to Informix 501
configuring authentication 70
to UNIX databases 504
configuring Sybase ASE repository 54
to Windows databases 488
connectivity 486
connecting to databases
creating data connectors 352
JDBC 486
custom installation in console mode 248
connection strings
custom installation in graphical mode 175
JDBC connections 554
database drivers 475
native connectivity 478
EAR Repackager utility 302
connectivity
Import Export utility 303
COBOL 484
installing JDBC XA on Microsoft SQL Server 338
configuring for upgrade 79
installing on JBoss Application Server 4
connect string examples 478
installing on WebLogic Server 4
Data Analyzer 486
installing on WebSphere Application Server 4
diagram of 474
JDBC-ODBC bridge 486
Integration Service 484
License Update utility 303
Metadata Manager 486
minimum system requirements 35
overview 474
ODBC (Open Database Connectivity) 474
PowerCenter Client 481
PowerCenter Integration utility 304, 334
Repository Service 483
repository 372
console mode
Repository Backup utility 309
installing PowerCenter Advanced Edition 224
Repository Upgrade utility 309
installing PowerCenter Reports 288
troubleshooting 372
installing PowerCenter Standard Edition 213
uninstalling 386
rules and guidelines 212, 238
Update System Accounts utility 309
uninstallation 396
updating license 337
using 212, 238
upgrading 29
Create (pmrep)
utilities 300, 302
troubleshooting 370
Data Analyzer Data Profiling reports
create domain
installing 351
guidelines 17
upgrading 429
Create New Domain
Data Analyzer repository
console mode 217, 228
database size 38
graphical mode 115, 139, 161
optimizing for Oracle 52
CreateConnection (pmrep)
optimizing for Sybase 53
troubleshooting 372
data connectors
adding data source for PowerCenter Repository
564 Index
Reports 341 connecting to Sybase ASE 499, 515
adding the Data Profiling data source 354 connecting to Teradata (UNIX) 518
creating for Data Profiling 352 connecting to Teradata (Windows) 501
primary data source 353 creating accounts 56
properties 353 Data Analyzer 52
Data Profiling warehouse Data Profiling warehouse 52
back up 428 domain configuration 52
configuring a data source 351 heap size for IBM DB2 55
creating 331 JDBC connection strings 554
database size 38 Metadata Manager repository 52
restore 428 page size for Sybase 53
upgrading 427 password 56
upgrading Data Analyzer views 429 PowerCenter repository 52
user account privileges 56 privileges for Data Analyzer repositories 56
data sources privileges for Data Profiling warehouse 56
adding to data connector 354 privileges for Metadata Manager repositories 56
adding to data connector for PowerCenter Repository privileges for PowerCenter repositories 56
Reports 341 setting name on IBM DB2 220, 232
configuring for the Data Profiling warehouse 351 setting URL for repository configuration 223, 234, 235
for PowerCenter Repository Reports 339 size for Data Profiling warehouse 38
primary in data connector 353 storage parameters for Oracle 52
using new repository for PowerCenter Repository tablespace name for IBM DB2 53
Reports 349 temporary tablespace for IBM DB2 55
Data Stencil testing connections 65
description 43 DataDirect ODBC drivers
installation prerequisites 43 platform-specific drivers required 480
uninstalling 386 datatypes
database client overview 558
configuring 60 transformation 558
environment variables 60 DB2
database drivers See IBM DB2
Integration Service 474 dbs2 connect
Repository Service 474 testing database connection 65
database type debug log
Data Analyzer repository 126, 150, 223 description 362
Metadata Manager repository 151, 235 DeleteConnection (pmrep)
PowerCenter repository 122, 231 troubleshooting 372
PowerCenter repository for Metadata Manager 146 disk space
setting for repository configuration 234 minimum requirements 35, 37, 38, 40, 43, 45, 46
database user ID DISPLAY variable
setting for repository configuration 122, 146, 220, 231 redirecting graphics on UNIX 63
database user password documentation
setting for repository configuration 122, 146, 220, 231 installed 6
databases installing 293
connecting to (UNIX) 504 installing from the hard disk 292
connecting to (Windows) 488 viewing 295
connecting to IBM DB2 489, 505 Domain Activity Reporting
connecting to Informix 491, 508 setting up on UNIX 73
connecting to Microsoft Access 493 domain configuration database
connecting to Microsoft SQL Server 494 configuring with installer 116, 140, 217, 228
connecting to Oracle 496, 511 database size 38
Index 565
definition 52
setting up 52
G
troubleshooting 366 global repository
uninstalling 386 upgrading 409
domainmeta.xml global_repo
backing up before upgrade 83 upgrade directory 92
upgrading 420, 421 graphical mode
domains configuring 63
See PowerCenter domains installing PowerCenter Advanced Edition 128
See WebLogic domain installing PowerCenter Reports 284
domains.infa installing PowerCenter Standard Edition 103
backing up before upgrade 83, 85 uninstallation 390, 392
description 64
location 64
H
E HP-UX
EAR Repackager utility configuring X Virtual Frame Buffer (Xvfb) 73
See also Data Analyzer Administrator Guide Java components 62
configuring 302, 311 SHLIB_PATH 62
upgrading color schemes 464
environment variables
configuring for PowerCenter 59 I
database client 60 IBM DB2
DISPLAY 63 connect string syntax 478
INFA_DOMAINS_FILE 64 connecting to Integration Service (UNIX) 505
INFA_HOME 357 connecting to Integration Service (Windows) 489
INFA_JAVA_OPTS 64 creating a Data Profiling warehouse 331, 427
Java components 62 creating Data Profiling warehouse views for Data
LANG 61 Analyzer 332
LANG_C 61 importing Metadata Manager metamodels 469
LC_ALL 61 optimizing repositories 53, 55
LC_CTYPE 61 setting DB2CODEPAGE 489
library path 60 setting DB2INSTANCE 489
local 61 setting tablespace name 122, 146, 220, 232
NLS_LANG 61 IBM WebSphere Application Server
UNIX 59 default server 544
UNIX database client 60 Import Export utility
UNIX requirements 104, 129, 176 configuring 303
event-based schedules INFA_DOMAINS_FILE
upgrading 465 environment variable 64
removing before upgrade 83
F INFA_HOME
configuring for PowerCenter utilities 301
Firefox environment variable 357
See Mozilla Firefox 68 removing before upgrade 83
flat files INFA_JAVA_OPTS
connectivity 484 environment variables 64
infacmd
Integration Services, creating 371
566 Index
nodes, adding to domains 367 Integration Service
pinging objects 368 code pages 45
Repository Services, creating 369 connectivity 484
troubleshooting 362 creating in console mode 221, 261
infasetup creating in graphical mode 123, 147
domains, defining 367 database client 57
troubleshooting 362 database drivers 475
worker nodes, defining 367 datatype usage 558
infaupgrade description 7
commands 420 log events 365
description 420 ODBC (Open Database Connectivity) 474
upgradeDomain command 421 troubleshooting 371
upgradeGatewayNode command 421 Integration Service run-time files
upgradeWorkerNode command 422 moving 460
Informatica Developer Platform Internet Explorer
description 316 See Microsoft Internet Explorer 68
list of SDKs and APIs 316 isql
Informatica Development Platform testing database connection 65
installation directories 321
Informatica Services
configuring 325 J
configuring memory 64
Java components
description 7
AIX 62
starting and stopping on UNIX 531
HP-UX 62
starting and stopping on Windows 532
Java transformation
troubleshooting 367
Informix
Javascript
connect string syntax 478
configuring in Firefox 68
connecting to Integration Service (UNIX) 508
connecting to Integration Service (Windows) 491
authentication 70
connecting to PowerCenter Client 501
creating a Data Profiling warehouse 331
installing 70
upgrading repository 87
installing Metadata Manager on 4
installation log
server configuration 70
description 364
service name 374
installing
starting 537
console mode 212
startup command 374
creating a domain 115, 139, 161, 217, 228
stopping 538
creating a user 58
troubleshooting 373, 374
Data Analyzer Data Profiling reports 351
uninstalling 387
graphical mode 102, 154
JDBC drivers
installation and configuration steps 16
connection strings 554
joining a domain 115, 139, 161, 217, 228
Data Analyzer 474
minimum system requirements 35, 37, 38, 40, 43, 45,
Data Analyzer connection to repository 486
46
driver types 555
PowerCenter Advanced Edition 102, 154, 212
installed 9, 11
installed drivers 486
PowerCenter documentation 293
Metadata Manager connection to databases 486
PowerCenter Standard Edition 102, 154, 212
PowerCenter domain 474
shipped with PowerCenter 554
Index 567
JDBC-ODBC bridge installation directory 321
Data Analyzer 486 installing 317
join domain Load Manager API (Java)
guidelines 17 Informatica Developer Platform 316
Join Existing Domain installation directory 321
console mode 217, 228 installing 317
graphical mode 115, 139, 161 local repository
guidelines 17 upgrading 413
local_repo
L locale
configuring 61
LANG
localhost_log.<date>.txt
environment variable 61
languages
log files
installing on Windows 69
catalina.out 364
NLS_LANG 61
debug log 362
LC_ALL
domain log events 365
installation 362
LC_CTYPE
installation log 364
Integration Service log events 365
LD_LIBRARY_PATH
localhost_log.<date>.txt 364
library paths 60
node.log 364
LIBPATH
Repository Service log events 365
AIX 62
summary log 363
library paths 60
types 362
library paths
WebSphere Application Server 375
LD_LIBRARY_PATH 60
Log Manager
LIBPATH 60
upgrading 460, 461
SHLIB_PATH 60
libstdc++.so
library 62
license key
M
description 6 Mapping API (Java)
obtaining 6 Informatica Developer Platform 316
PowerCenter Advanced Edition 6 installation directory 321
PowerCenter Standard Edition 6 installing 317
verifying 67 memory
License Update utility specifying for Informatica Services 64
configuring 303, 312 memory requirements
updating licenses 337 system memory 64
licenses Metadata Exchange SDK
adding 368 Informatica Developer Platform 316
updating 337 installation directory 321
Linux installing 317
configuring locale 61 Metadata Manager
configuring X Virtual Frame Buffer (Xvfb) 73 client upgrade steps 453
database client environment variables 60 components 10
libraries 62 configuring authentication 70
library paths 60 connectivity 486
Load Manager API (C) custom installation in console mode 255
Informatica Developer Platform 316 custom installation in graphical mode 191
568 Index
database drivers 475 Mozilla Firefox
deleting obsolete objects 468 configuring 68
EAR Repackager utility 311 multiple machine installation
importing metamodels 469 guidelines 17
installing on JBoss Application Server 4
installing on WebLogic Server 4
installing on WebSphere Application Server 4 N
License Update utility 312
native connect string
minimum system requirements 35
See connect string
NLS_LANG
post-upgrade tasks 467
refreshing views 467
node.log
repository 372
Repository Backup utility 313
nodemeta.xml
troubleshooting 372
backing up before upgrade 83, 85
uninstalling 386
upgrading 420, 422
Update System Accounts utility 313
nodes
updating license 337
TCP/IP network protocol 474
upgrade utility 442
troubleshooting 367
upgrading 31
normal mode
upgrading the client 453
Data Profiling warehouse size 38
upgrading the repository 442
notifyias
utilities 300, 311
configuring for Data Analyzer 334
Metadata Manager Client
components 12
troubleshooting 376
O
uninstalling 386 ODBC (Open Database Connectivity)
Metadata Manager repository DataDirect driver issues 480
database size 38 drivers 266, 426
optimizing for IBM DB2 55 establishing connectivity 479
optimizing for Sybase 53 Integration Service 474
Microsoft Access Metadata Manager 474
connecting to Integration Service 493 overview 479
Microsoft Excel PowerCenter Client 474
connecting to Integration Service 493 requirement for PowerCenter Client 481
using PmNullPasswd 493 ODBC calls
using PmNullUser 493 Integration Service 552
Microsoft Internet Explorer PowerCenter Client 550
configuring 68 ODBC data sources
Microsoft SQL Server connecting to (UNIX) 522
configuring Data Analyzer repository database 54 connecting to (Windows) 488
connect string syntax 478 odbc.ini file
connecting from UNIX 504 sample 525
connecting to Integration Service 494 optimizing
creating a Data Profiling warehouse 331 IBM DB2 repositories 53, 55
creating Data Profiling warehouse views for Data Oracle repositories 52
Analyzer 332 repositories 86
installing JDBC XA stored procedures 338 Sybase repositories 53
Microsoft Visio Oracle
installation prerequisite 43 connect string syntax 478
Index 569
connecting to Data Analyzer repository 555 pre-installation tasks 50
connecting to Integration Service (UNIX) 511 repository version number 403
connecting to Integration Service (Windows) 496 troubleshooting 361
creating a Data Profiling warehouse 331 upgrading 78
creating Data Profiling warehouse views for Data utilities 300
Analyzer 332 PowerCenter Advanced Edition
displaying non-ASCII characters 498 complete installation in console mode 224
JDBC requirements 555 complete installation in graphical mode 128
NLS_LANG 61 DVD contents 5
optimizing repositories 52 minimum system requirements 35
Oracle Net Services uninstalling 386
using to connect Integration Service to Oracle (UNIX) PowerCenter Client
511 code pages 45
using to connect Integration Service to Oracle components 12
(Windows) 496 connectivity 481
installing complete 267
P installing custom 271
installing languages 69
padaemon user account
configuring for WebSphere 71
password
troubleshooting 376
repository database 56
uninstalling 386
PCServer
PowerCenter Connect for JMS
Ping (infacmd)
PowerCenter Connect for Web Services
troubleshooting 368
PmNullPasswd
PowerCenter Connect for webMethods
reserved word 485
PmNullUser
PowerCenter Connect SDK
reserved word 485
Informatica Developer Platform 316
pmpasswd
installation directory 321
updating password 457
installing 317
pmrep
PowerCenter Documentation DVD
repositories, connecting to 369
description 6
troubleshooting 362
PowerCenter domains
pmserverexportreg
connectivity 477
creating PowerCenter Server configuration file 90
creating 17
troubleshooting 90
description
pmserverexportreg utility
guidelines 17
syntax 89
joining 17
pop-up blocker
log events 365
avoiding in Data Analyzer 68
pinging 368
port numbers
troubleshooting 367
PowerCenter
upgrading 420, 421
complete installation in console mode 212
PowerCenter Integration utility
complete installation in graphical mode 102, 154
configuring 304
configuring 324
PowerCenter Reports
connectivity 474
description 13
post-install tasks 324
installing 282
570 Index
installing in console mode 288
installing in graphical mode 284
R
uninstalling 386 reports
PowerCenter repository adding PowerCenter Repository Reports to schedules
database size 38 345
description 7 cached reports for PowerCenter Repository Reports
optimizing for IBM DB2 53 345
PowerCenter repository for Metadata Manager running schedules for PowerCenter Repository
database type 146 Reports 348
PowerCenter Repository Reports repositories
adding cached reports to schedules 345 backing up 93
importing report objects 282 connectivity requirements 483
installing 13, 282 copying 87
installing in console mode 288 database size 38
installing in graphical mode 284 description 7
running schedules for cached reports 348 optimizing 86
setting up data source 339 password 56
switching repositories 349 supported databases 38
PowerCenter Server switching data sources for PowerCenter Repository
backing up configuration files 89 Reports 349
configuration file location 91 troubleshooting 370
creating configuration file 89 troubleshooting upgrade 411
troubleshooting upgrade 418 upgrading 86, 409, 413
upgrading 416 upgrading in Administration Console 424
PowerCenter Server run-time files upgrading Informix 87
moving 458 upgrading Teradata 87
PowerCenter Services version number 403
components 7 Repository Agent
custom installation in console mode 240 backing up configuration files 89
custom installation in graphical mode 155 configuration file location 91
description troubleshooting upgrade 411
directory structure 8 upgrading 409, 413
multiple machine installation 17 repository authentication
port numbers 66 configuring 70
Service Manager 7 Repository Backup utility
single machine installation 17 backing up the repository 93
uninstalling 386 configuring 309, 313
PowerCenter Standard Edition repository configuration
complete installation in console mode 213 Data Analyzer repository database type 126, 150, 223,
complete installation in graphical mode 103 234
DVD contents 5 Metadata Manager repository database type 151, 235
minimum system requirements 35 PowerCenter repository database type 122
uninstalling 386 PowerCenter repository for Metadata Manager 146
PowerCenter table definitions PowerCenter repository for Metadata Manager
refreshing after upgrade 465 database type 231
PowerCenter utilities setting code page 122, 146, 220, 231
included utilities 300 setting connect string 122, 146, 220, 231
rules and guidelines 301 setting database URL 223, 234, 235
primary data sources setting database user ID 122, 146, 220, 231
data connector 353 setting database user password 122, 146, 220, 231
setting IBM DB2 database name 220, 232
Index 571
setting IBM DB2 tablespace name 122, 146, 220, 232 64-bit platforms
repository name guidelines 46
description 122, 146, 220, 231 supported platforms 46
PowerCenter repository 220 softlinks
setting for repository configuration 122, 146, 231 using with INFA_HOME 357
Repository Server Solaris
troubleshooting upgrade 411 configuring X Virtual Frame Buffer (Xvfb) 73
upgrading 409, 413 source databases
Repository Service connecting through ODBC (UNIX) 522
connectivity 483 sqlplus
connectivity requirements 483 testing database connection 65
creating with installer 117, 120, 163, 166, 218, 219, Start Page
242, 243 Informatica documentation 295
database client 57 summary log
database drivers 475 description 363
description 7 SwitchConnection (pmrep)
log events 365 troubleshooting 372
troubleshooting 369 switching connections
Repository Upgrade utility troubleshooting 372
configuring 309 Sybase ASE
Restore (pmrep) configuring Data Analyzer repository 54
troubleshooting 370 configuring Metadata Manager repository 54
connect string syntax 478
connecting to Integration Service (UNIX) 515
S connecting to Integration Service (Windows) 499
creating a Data Profiling warehouse 332
samples
creating Data Profiling warehouse views for Data
odbc.ini file 525
Analyzer 332
schedules
page size for repositories 53
adding the PowerCenter Repository Reports to the
system requirements
schedules 345
minimum installation requirements 35, 37, 38, 40, 43,
cached reports for PowerCenter Repository Reports
45, 46
345
system user
running for PowerCenter Repository Reports 348
user account 58
upgrading 465
Service Manager
description 7
log files 364
T
service pack target databases
description 6 connecting through ODBC (UNIX) 522
services TCP/IP network protocol
starting and stopping 531, 532 nodes 474
Session Log API PowerCenter Client 474
Informatica Developer Platform 316 PowerCenter domains 474
installation directory 321 requirement for Integration Service 481
installing 317 Teradata
SHLIB_PATH connect string syntax 478
HP-UX 62 connecting to Integration Service (UNIX) 518
library path 60 connecting to Integration Service (Windows) 501
single machine installation creating a Data Profiling warehouse 332
guidelines 17 creating Data Profiling warehouse views for Data
Analyzer 332
572 Index
upgrading repository 87 database client variables 60
time-based schedules environment variables 59
upgrading 465 library paths 60
transformation datatypes user account 58
overview 558 Update System Accounts utility
Transformation SDK configuring 309, 313
Informatica Developer Platform 316 upgrade steps
installation directory 321 Data Analyzer 29, 93
installing 317 Metadata Manager 31, 96
troubleshooting Metadata Manager Client 453
creating a domain 367 PowerCenter 23
domain configuration database 366 upgrade utility
error messages 377 Data Analyzer 432
infacmd 362 Metadata Manager 442
infasetup 362 Upgrade Wizard
Informatica Services 367 description 402
JBoss Application Server 373 rules and guidelines 405
joining a domain 367 selecting configuration files 406
licenses 368 troubleshooting 411, 418
Metadata Manager Client 376 upgrade process 402
pinging a domain 368 upgrading a PowerCenter Server 416
pmrep 362 upgrading a Repository Agent 409, 413
PowerCenter Client 376 viewing results 419
PowerCenter installation 361 upgradeDomain (infaupgrade)
Repository Service 369, 371 usage 421
steps for PowerCenter installation 361 upgradeGatewayNode (infaupgrade)
switching connections 372 usage 421
uninstallation 386 upgradeWorkerNode (infaupgrade)
Upgrade Wizard 411, 418 usage 422
upgrading repositories 411 upgrading
WebLogic Server 374 backing up the repository 93
WebSphere Application Server 375 color schemes 94
compatible PowerCenter upgrades 23
Data Profiling warehouse 427
U deleting obsolete Metadata Manager objects 468
domain 420
Unicode repository
importing Metadata Manager metamodels 469
upgrading 457, 458
Log Manager 460, 461
uninstalling
Metadata Manager Client 453
application server files 387
Metadata Manager repository 442
Data Analyzer 386
post-upgrade tasks for Data Analyzer 464
Metadata Manager Client 386
post-upgrade tasks for Metadata Manager 467
PowerCenter 78
PowerCenter 6.x/7.x 24
PowerCenter 8.0 25
process 388
PowerCenter 8.1 27
rules and guidelines 386
PowerCenter Server 416
troubleshooting 386
pre-upgrade steps for Data Analyzer 93
UNIX
pre-upgrade steps for Metadata Manager 96
connecting to ODBC data sources 522
pre-upgrade steps for PowerCenter 78
database client environment variables 60
Index 573
refreshing Metadata Manager views 467 installing Metadata Manager on 4
repositories 86 starting 540
Repository Agent 409, 413 stopping 541
schedules 94 troubleshooting 374
shared documents 94 WebSphere Application Server
steps for Metadata Manager 31 authentication 70
steps for Metadata Manager client 453 base edition 71
troubleshooting 411, 418 deployment manager 543, 546
troubleshooting repository 411 installation prerequisites 40
Unicode repository 457, 458 installing 70
Upgrade Wizard 402 installing Data Analyzer on 4
using infaupgrade 420 installing Metadata Manager on 4
using pmserverexportreg 89 JMS server 544
Web Services Hub 80, 457, 458 Network Deployment edition 71
user account node agent 543
system user 58 padaemon user account 71
user account privileges PowerCenter Integration Utility 334
Data Analyzer repositories 56 prerequisites for UNIX 71, 72
Data Profiling warehouse 56 prerequisites for Windows 71
Metadata Manager repositories 56 starting 542
PowerCenter repositories 56 stopping 545
user accounts troubleshooting 375
creating on database 56 user groups 72
user groups Windows Event Viewer
creating for WebSphere Application Server 72 troubleshooting JBoss Application Server 374
users
database 56
installation user 58 X
UTF-8 repository
X Virtual Frame Buffer (Xvfb)
upgrading 457, 458
installing on UNIX 73
X Window
V installation requirement on UNIX 63
XConnect
verbose mode description 10
Data Profiling warehouse size 38 installed 10
viewing
PowerCenter documentation 295
W
web browsers
supported browsers 37
Web Services Hub
upgrading 80, 457, 458
WebLogic domain
uninstalling 387
WebLogic Server
authentication 70
installing 70
574 Index

PC 811 InstallationGuide

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

PC 811 InstallationGuide

Caricato da

Copyright:

Formati disponibili

Installation and Configuration

Copyright (c) 1998–2007 Informatica Corporation.

InstallAnywhere is Copyright 2005 Zero G Software, Inc. All Rights Reserved.

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Chapter 1: PowerCenter Installation Components . . . . . . . . . . . . . . . 3

Chapter 2: Installation and Upgrade Overview . . . . . . . . . . . . . . . . . 15

Chapter 3: PowerCenter Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 4: Before You Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Part II: PowerCenter Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Chapter 6: PowerCenter Complete Installation in Graphical

Chapter 7: PowerCenter Custom Installation in Graphical

Chapter 8: PowerCenter Complete Installation in Console

Chapter 9: PowerCenter Custom Installation in Console Mode . . . 237

Chapter 10: PowerCenter Client Installation . . . . . . . . . . . . . . . . . . 265

Table of Contents vii

Chapter 11: PowerCenter Reports Installation . . . . . . . . . . . . . . . . . 281

Chapter 12: Documentation Installation . . . . . . . . . . . . . . . . . . . . . . 291

Chapter 13: PowerCenter Utilities Installation . . . . . . . . . . . . . . . . . 299

viii Table of Contents

Chapter 14: Informatica Development Platform Installation . . . . . . 315

Chapter 15: After You Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Chapter 16: Troubleshooting a PowerCenter Installation . . . . . . . . 359

Chapter 17: Uninstalling PowerCenter . . . . . . . . . . . . . . . . . . . . . . . 385

Part III: Upgrading PowerCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Chapter 18: Upgrading PowerCenter . . . . . . . . . . . . . . . . . . . . . . . . 401

Chapter 20: Upgrading Metadata Manager . . . . . . . . . . . . . . . . . . . . 441

Chapter 21: After You Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455

xii Table of Contents

Part IV: Configuring Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . 471

Chapter 22: Understanding Connectivity . . . . . . . . . . . . . . . . . . . . . 473

Chapter 23: Connecting to Databases from Windows . . . . . . . . . . . 487

Table of Contents xiii

Chapter 24: Connecting to Databases from UNIX . . . . . . . . . . . . . . 503

Part V: Appendices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527

xiv Table of Contents

Appendix B: Starting and Stopping Application Servers . . . . . . . . 535

Appendix C: Logging in to the Administration Console . . . . . . . . . 547

Appendix D: ODBC Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549

Appendix E: JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553

Appendix F: LANG Environment Variable for Linux . . . . . . . . . . . . 557

List of Figures xvii

List of Tables xix

List of Tables xxi

If you see… It means…

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

boldfaced text Emphasized subjects.

Note: The following paragraph provides additional facts.

Tip: The following paragraph provides suggested uses.

monospaced text This is a code example.

Visiting Informatica Customer Portal

Visiting the Informatica Web Site

Visiting the Informatica Knowledge Base

Obtaining Customer Support

Informatica Corporation Informatica Software Ltd. Informatica Business Solutions

Toll Free Toll Free Toll Free

Standard Rate Standard Rate Standard Rate

This part contains the following chapters:

4 Chapter 1: PowerCenter Installation Components

PowerCenter Standard/Advanced Edition 32 bit/64 bit DVD

PowerCenter Documentation DVD

PowerCenter License Key CD

PowerCenter Service Pack