Informatica (Version 9.0.1)

Upgrade Guide for PowerCenter 8.1.x

Informatica Upgrade Guide for PowerCenter 8.1.x

Version 9.0.1June 2010

Copyright (c) 1998-2010 Informatica. All rights reserved.

This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use anddisclosure 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. This Software may be protected by U.S. and/or internationalPatents and other Patents Pending.

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 inDFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013©(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 product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us inwriting.

Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange,PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange and InformaticaOn Demand are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and productnames 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. All rightsreserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All rightsreserved.Copyright © Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright 2007 Isomorphic Software. All rights reserved. Copyright © MetaIntegration Technology, Inc. All rights reserved. Copyright © Intalio. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © Adobe Systems Incorporated. Allrights reserved. Copyright © DataArt, Inc. All rights reserved. Copyright © ComponentSource. All rights reserved. Copyright © Microsoft Corporation. All rights reserved.Copyright © Rouge Wave Software, Inc. All rights reserved. Copyright © Teradata Corporation. All rights reserved. Copyright © Yahoo! Inc. All rights reserved. Copyright ©Glyph & Cog, LLC. All rights reserved.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and other software which is licensed under the Apache License,Version 2.0 (the "License"). You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing,software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See theLicense for the specific language governing permissions and limitations under the License.

This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software copyright ©1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under the GNU Lesser General Public License Agreement, which may be found at http://www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but notlimited to the implied warranties of merchantability and fitness for a particular purpose.

The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine,and Vanderbilt University, Copyright (©) 1993-2006, all rights reserved.

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution ofthis software is subject to terms available at http://www.openssl.org.

This product includes Curl software which is Copyright 1996-2007, Daniel Stenberg, . All Rights Reserved. Permissions and limitations regarding thissoftware are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software for any purpose with or withoutfee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

The product includes software copyright 2001-2005 (©) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms availableat http://www.dom4j.org/ license.html.

The product includes software copyright © 2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to termsavailable at http:// svn.dojotoolkit.org/dojo/trunk/LICENSE.

This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding thissoftware are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/license.html.

This product includes software copyright © 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at http://www.gnu.org/software/ kawa/Software-License.html.

This product includes OSSP UUID software which is Copyright © 2002 Ralf S. Engelschall, Copyright © 2002 The OSSP Project Copyright © 2002 Cable & WirelessDeutschland. Permissions and limitations regarding this software are subject to terms available at http://www.opensource.org/licenses/mit-license.php.

This product includes software developed by Boost (http://www.boost.org/) or under the Boost software license. Permissions and limitations regarding this software are subjectto terms available at http:/ /www.boost.org/LICENSE_1_0.txt.

This product includes software copyright © 1997-2007 University of Cambridge. Permissions and limitations regarding this software are subject to terms available at http://www.pcre.org/license.txt.

This product includes software copyright © 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to termsavailable at http:// www.eclipse.org/org/documents/epl-v10.php.

This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?License, http://www.stlport.org/doc/license.html, http://www.asm.ow2.org/license.html, http://www.cryptix.org/LICENSE.TXT, http://hsqldb.org/web/hsqlLicense.html, http://httpunit.sourceforge.net/doc/license.html, http://jung.sourceforge.net/license.txt , http://www.gzip.org/zlib/zlib_license.html, http://www.openldap.org/software/release/license.html, http://www.libssh2.org,http://slf4j.org/license.html, http://www.sente.ch/software/OpenSourceLicense.html, and http://fusesource.com/downloads/license-agreements/fuse-message-broker-v-5-3-license-agreement.

This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and DistributionLicense (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php) and the BSD License (http://www.opensource.org/licenses/bsd-license.php).

This product includes software copyright © 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this softwareare subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab. For furtherinformation please visit http://www.extreme.indiana.edu/.

This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775;6,640,226; 6,789,096; 6,820,077; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,254,590; 7,281,001; 7,421,458; and 7,584,422, international Patents and otherPatents Pending.

DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the impliedwarranties of non-infringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. Theinformation provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation issubject to change at any time without notice.

NOTICES

This Informatica product (the “Software”) includes certain drivers (the “DataDirect Drivers”) from DataDirect Technologies, an operating company of Progress SoftwareCorporation (“DataDirect”) which are subject to the following terms and conditions:

1.THE DATADIRECT DRIVERS ARE PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OFTHE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACHOF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

Part Number: PC-UPG-90100-0001

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ivInformatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Informatica Customer Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Multimedia Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Chapter 1: Upgrade Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Informatica Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Upgrade Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Upgrade Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2: Before You Upgrade the Domain and Server Files. . . . . . . . . . . . . . . . . . . . . . 4Pre-Upgrade Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Review the Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Temporary Disk Space Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Verify the File Descriptor Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Verify Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Locale Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

JRE_HOME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Set Up the X Window Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Clear Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Prepare the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Migrate to a Supported Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Back Up the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Verify the Domain Configuration Repository Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Run infasetup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Prepare the PowerCenter Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Optimize Upgrade Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Configure PowerCenter Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Migrate to a Supported Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Back Up the Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Prepare the PowerCenter Profiling Warehouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Shut Down the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Table of Contents i

Chapter 3: Domain and Server Files Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Domain and Server Files Upgrade Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Upgrading in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Upgrading in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Upgrading in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Creating the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Troubleshooting the Domain Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 4: Before You Upgrade the Application Services. . . . . . . . . . . . . . . . . . . . . . . . . 23Configure POSIX Asynchronous I/O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Configure Informatica Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Configure Locale Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Clear Browser Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Configure Browser Bookmarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Prepare to Upgrade LDAP Users and Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 5: Application Service Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Application Service Upgrade Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Service Upgrade for PowerCenter 8.1.x. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Service Upgrade Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Running the Service Upgrade Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Users and Groups Conflict Resolution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 6: Informatica Client Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Informatica Client Upgrade Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Informatica Client Upgrade Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Upgrading in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Upgrading in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Creating the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 7: After You Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Informatica Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Configure LDAP Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Update the Log Events Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Update ODBC Data Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Update Statistics for the Domain Configuration Repository. . . . . . . . . . . . . . . . . . . . . . . . . . 36

View Log Events from the Previous Informatica Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

PowerCenter Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

PowerCenter Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Associate Linked Domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

ii Table of Contents

Rename PowerCenter Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Verify PowerCenter Repository Database User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Web Services Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Associate Linked Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Verify PowerCenter Repository Database User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Table of Contents iii

PrefaceThe Upgrade Guide for PowerCenter 8.1.x is written for the system administrator who is responsible for upgradingthe Informatica product. This guide assumes that you have knowledge of operating systems, relational databaseconcepts, and the database engines, flat files, or mainframe systems in your environment. This guide alsoassumes that you are familiar with the interface requirements for your supporting applications.

Informatica Resources

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

Informatica DocumentationThe Informatica Documentation team takes every effort to create accurate, usable documentation. If you havequestions, comments, or ideas about this documentation, contact the Informatica Documentation team throughemail at infa_documentation@informatica.com. We will use your feedback to improve our documentation. Let usknow if we can contact you regarding your comments.

The Documentation team updates documentation as needed. To get the latest documentation for your product,navigate to Product Documentation from http://mysupport.informatica.com.

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

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

iv

http://mysupport.informatica.commailto:infa_documentation@informatica.comhttp://mysupport.informatica.comhttp://www.informatica.comhttp://mysupport.informatica.com

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

Informatica Multimedia Knowledge BaseAs an Informatica customer, you can access the Informatica Multimedia Knowledge Base at http://mysupport.informatica.com. The Multimedia Knowledge Base is a collection of instructional multimedia filesthat help you learn about common concepts and guide you through performing specific tasks. If you havequestions, comments, or ideas about the Multimedia Knowledge Base, contact the Informatica Knowledge Baseteam through email at KB_Feedback@informatica.com.

Informatica Global Customer SupportYou can contact a Customer Support Center by telephone or through the Online Support. Online Support requiresa user name and password. You can request a user name and password at http://mysupport.informatica.com.

Use the following telephone numbers to contact Informatica Global Customer Support:

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

Toll FreeBrazil: 0800 891 0202Mexico: 001 888 209 8853North America: +1 877 463 2435 Standard RateNorth America: +1 650 653 6332

Toll FreeFrance: 00800 4632 4357Germany: 00800 4632 4357Israel: 00800 4632 4357Italy: 800 915 985Netherlands: 00800 4632 4357Portugal: 800 208 360Spain: 900 813 166Switzerland: 00800 4632 4357 or 0800 463200United Kingdom: 00800 4632 4357 or 0800023 4632 Standard RateBelgium: +32 15 281 702France: 0805 804632Germany: +49 1805 702 702Netherlands: +31 306 022 797

Toll FreeAustralia: 1 800 151 830New Zealand: 1 800 151 830Singapore: 001 800 4632 4357 Standard RateIndia: +91 80 4112 5738

Preface v

http://mysupport.informatica.commailto:KB_Feedback@informatica.comhttp://mysupport.informatica.commailto:KB_Feedback@informatica.comhttp://mysupport.informatica.com

vi

C H A P T E R 1

Upgrade OverviewThis chapter includes the following topics:

¨ Informatica Upgrade, 1

¨ Upgrade Process, 2

¨ Upgrade Tasks, 3

Informatica UpgradeYou can upgrade the following Informatica product versions to version 9.0.1:

Informatica Product Version Comments

Informatica PowerCenter 8.1.x If the PowerCenter 8.1.x domain includes Metadata Manager or DataAnalyzer, you must upgrade to PowerCenter 8.6.1 before youupgrade to Informatica PowerCenter 9.0.1.

Informatica PowerCenter 8.5.x If the PowerCenter 8.5.x domain includes the Metadata ManagerService or Reporting Service, you must upgrade to PowerCenter8.6.1 before you upgrade to Informatica PowerCenter 9.0.1.

Informatica PowerCenter 8.6 If the PowerCenter 8.6 domain includes the Metadata ManagerService, Reporting Service, or Reference Table Manager Service,you must upgrade to PowerCenter 8.6.1 before you upgrade toInformatica PowerCenter 9.0.1.

Informatica PowerCenter 8.6.1 Effective in version 9.0.1, the Reference Table Manager functionalityis available through the 9.0.1 Analyst Service. See the PowerCenter8.6.1 upgrade documentation for the steps to migrate thePowerCenter 8.6.1 reference table data to the Informatica 9.0.1Analyst tool.

Informatica Data Quality 8.6.2 You can migrate the contents of the Informatica Data Quality 8.6.2repository to the Informatica 9.0.1 Model repository. See the 9.0.1Data Quality migration documentation for details.

Informatica PowerCenter 9.0

Informatica Data Quality 9.0

1

Informatica Product Version Comments

Informatica Data Services 9.0

Informatica Data Explorer Advanced Edition 9.0 See the Informatica Data Quality 9.0 upgrade documentation.Complete the steps to upgrade Informatica Data Quality 9.0 unlessan exception is specified.

If the product version you use cannot be upgraded to Informatica 9.0.1, you must first upgrade to a supportedversion.

Upgrade ProcessThe upgrade consists of the following phases:

¨ Upgrading the domain and server files. To upgrade the domain and server files, run the Informatica serverinstaller and select the upgrade option. The domain upgrade wizard installs the server files and configures thedomain. If the domain has multiple nodes, you must upgrade on all the nodes.The following table describes the actions that the installer performs when you upgrade Informatica:

Tasks Description

Installs Informatica. Installs Informatica directories and files into the newdirectory.

Copies infa_shared directory. Copies the contents of the infa_shared directory from theexisting installation directory into the new installationdirectory.

Upgrades the domain. Upgrades the domain to run version 9.0.1 applicationservices.The upgrade creates a new default Administrator useraccount in the domain.

Starts Informatica Services. Starts Informatica Services on the node.

¨ Upgrading the application services. After you upgrade the domain and server files, log in to the Administratortool and upgrade the application services. The service upgrade wizard provides a list of all application thatmust be upgraded. It upgrades the services based on the order required by the dependent objects.

¨ Upgrading the Informatica client. To upgrade the Informatica client, run the Informatica client installer andselect the upgrade option. If the client is installed on multiple machines, upgrade the client on all machines.

2 Chapter 1: Upgrade Overview

Upgrade TasksTo upgrade PowerCenter, complete the following tasks:

1. Complete the pre-upgrade tasks for the domain and server files to ensure that you can successfully run theinstaller.

2. Upgrade Informatica domain and server files. Use the server installer to upgrade Informatica domain andupgrade the server files on each node. If the domain contains multiple nodes, upgrade a gateway node beforeyou upgrade the worker nodes. After you upgrade the first gateway node, verify that the upgrade wassuccessful before you upgrade the other nodes in the domain.

3. Complete the pre-upgrade tasks for the application services.

4. Upgrade the application services. After installation, log in to the Administrator tool and upgrade theapplication services.

5. Upgrade the PowerCenter Client. Use the client installer to upgrade the Informatica client.

6. Perform the post-upgrade tasks.

Upgrade Tasks 3

C H A P T E R 2

Before You Upgrade the Domainand Server Files

This chapter includes the following topics:

¨ Pre-Upgrade Tasks, 4

¨ Review the Prerequisites, 5

¨ Verify the File Descriptor Settings, 6

¨ Verify Environment Variables, 6

¨ Clear Environment Variables, 8

¨ Prepare the Domain, 8

¨ Prepare the PowerCenter Repository, 12

¨ Prepare the PowerCenter Profiling Warehouse, 14

¨ Shut Down the Domain, 14

Pre-Upgrade TasksBefore you upgrade the domain and server files, complete the following tasks:

1. Review the prerequisites.

2. Verify the file descriptor settings.

3. Verify the configuration of the environment variables used by the installer.

4. Clear the configuration of environment variables that pertain to previous installations of Informatica.

5. Prepare the domain.

6. Prepare the PowerCenter repository.

7. Prepare the PowerCenter Profiling warehouse.

8. Shut down the domain.

4

Review the PrerequisitesVerify that your system meets the upgrade requirements.

The following table describes the minimum system requirements for a domain with different node configurations:

Component Processor RAM DiskSpace

Operating System

Domain with all Data Quality, DataServices, and PowerCenter servicesrunning on one node

4 CPU 8 GB 20 GB Windows 2003 / 2008Sun SolarisHP-UXIBM AIXRed Hat LinuxSUSE Linux

Domain with all PowerCenter servicesrunning on one node

2 CPU 4 GB 4 GB

Domain with all PowerCenter servicesrunning on one node except MetadataManager Service and Reporting Service

1 CPU 2 GB 3 GB

Metadata Manager Service running ona separate node

2 CPU 2 GB 3 GB

Reporting Service running on aseparate node

1 CPU 512 MB 3 GB

Orchestration Server running on aseparate node

1 CPU 512 MB 3 GB

Metadata Manager Agent 1 CPU 512 MB 220 MB Windows 2003 / 2008

Note: When you upgrade, the installer requires an additional 4 GB disk space plus the amount of disk space usedby the existing infa_shared directory.

The following table describes the minimum system requirements to run PowerCenter Client:

Client Processor RAM DiskSpace

Operating System

PowerCenter Client 1 CPU 512 MB 1.2 GB Windows 2003 / 2008 / XP / 7

For more details, see the Product Availability Matrix at http://mysupport.informatica.com.

Temporary Disk Space RequirementsThe installer writes temporary files to the hard disk. Verify that you have enough available disk space on themachine to support the installation. When the installation completes, the installer deletes the temporary files andreleases the disk space.

Review the Prerequisites 5

http://mysupport.informatica.com

The following table describes the temporary disk space requirements during installation:

Product Operating System Disk Space

Installer Windows or UNIX 1 GB

Informatica Services UNIX 2 GB

Windows 605 MB

Informatica Clients Windows 550 MB

Verify the File Descriptor SettingsOn UNIX or Linux, verify that the operating system meets the file descriptor requirement.

Informatica service processes can use a large number of files. Set the file descriptor limit per process to 3000 orhigher.

Verify Environment VariablesConfigure the environment variables to work with the Informatica installation. Incorrectly configured environmentvariables can cause the Informatica installation to fail.

The installer appends file paths required by Informatica to the PATH environment variable. Verify that the length ofthe PATH environment variable does not exceed the system limits and that the variable does not contain doublequotes.

On UNIX, create the environment variables with the system user account that you will use for installation. Log inwith the account that you plan to use to install Informatica, and then create the environment variables.

The following table describes environment variables you configure before you install:

Variable OperatingSystem

Description

IATEMPDIR (InstallAnywhere) WindowsUNIX

Location of temporary files created during installation. Informaticarequires 1 GB disk space for temporary files.Configure the environment variable if you do not want to createtemporary files in the following locations:- /tmp directory on UNIX- default drive on Windows

JRE_HOME SUSE LinuxLinux EMT64

Clear the JRE_HOME environment variable.

Locale environment variables UNIX Use LANG and LC_ALL to set the UNIX code page.

DISPLAY UNIX Location of the graphics display server such as X Window Server.Required to install in graphical mode.

6 Chapter 2: Before You Upgrade the Domain and Server Files

Locale Environment VariablesUse LANG and LC_ALL to set the UNIX code page for the installer.

Set the LANG and LC_ALL environment variables to the following values for the language that you use:

Language Value

English C

Japanese ja_JP.SJIS or ja_JP.PCK

Portuguese pt_BR.ISO8859-1, pt_BR.8859-15, or pt_BR

After you install, update the locale setting to one that is compatible with the code page of the repository.

JRE_HOMEIf you install Informatica Services on a machine with 32-bit or 64-bit SUSE Linux or Linux EMT64 operatingsystem, clear the JRE_HOME environment variable before you start the installation.

Set Up the X Window ServerWhen you run the Informatica installer in graphical mode, you must use a graphics display server. On UNIX, thegraphics display server is typically an X Window server. If you do not have the X Window server installed on themachine where you want to install Informatica, you can install Informatica using an X Window server installed onanother machine. Use the DISPLAY variable to redirect output of the X Window server to another UNIX machine.

The following table lists the commands to set the DISPLAY environment variable:

Shell Command Example

C setenv DISPLAY :0 setenv DISPLAY 10.1.50.23:0

Bash/Korn export DISPLAY=”:0” export DISPLAY=”10.1.50.23:0”

Bourne DISPLAY=”:0”export display

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 networkadministrator. For more information about redirecting the DISPLAY variable, see the documentation from the UNIXvendor.

If the X Window server does not support the font that the Informatica installer uses, the installer can displayincorrect labels on the buttons. For example, the button labeled Test Connection can appear as Test Connecti....

Verify Environment Variables 7

Clear Environment VariablesClear environment variables from previous Informatica versions before you upgrade.

Incorrectly configured environment variables can cause the domain or nodes to fail to start or can causeconnection problems between Informatica clients and the domain.

Clear PATH statementsVerify that the existing environment variables do not contain earlier versions of Informatica in the PATH or librarypath environment variables and that the path does not contain double quotes.

Clear INFA_HOMEDesignates the Informatica installation directory.

Clear INFA_DOMAINS_FILEDesignates the location of domains.infa on the machine where you install the Informatica server components orthe Informatica clients.

Prepare the DomainBefore you upgrade the domain, complete the steps to prepare the domain.

1. Migrate to a supported database.

2. Back up the domain.

3. Verify the domain configuration repository requirements.

Migrate to a Supported DatabaseIf the domain configuration is in a Sybase ASE database, you must migrate the domain configuration to an IBMDB2 UDB, Microsoft SQL Server, or Oracle database.

1. Shut down all application services in the domain.

2. Shut down the domain.

3. Back up the domain configuration.Run the infasetup BackupDomain command to back up the domain configuration to an XML file.

4. Create a database user account in a supported database.

5. Restore the domain configuration backup to the database user account.Run the infasetup RestoreDomain command to restore the domain configuration to the new database. TheRestoreDomain command restores the domain configuration in the backup XML file to the specified databaseuser account.

6. Update the database connection for each gateway node.Gateway nodes must have a connection to the domain configuration repository to retrieve and update domainconfiguration. Run the infasetup UpdateGatewayNode command on each gateway node to update thegateway node to reflect the new database details.

7. Start all nodes in the domain.

8. Enable all application services in the domain.

8 Chapter 2: Before You Upgrade the Domain and Server Files

Back Up the DomainBefore you upgrade the domain, you must back up the domain.

Complete the following steps to back up the domain:

¨ Run the infasetup BackupDomain command to back up the domain configuration repository to a file.

¨ Back up the metadata configuration files to any directory accessible by the machines where you installInformatica.

The following table describes the metadata files and the locations where you can find them:

Metadata File Description Location

nodemeta.xml Contains metadata for a node. Stored in the server/configdirectory on each node in thedomain.If you use the same backupdirectory name on all the nodes,rename nodemeta.xml beforecopying it to the backup location.For example, you back upnodemeta.xml to the /nodebakdirectory on nodeA and nodeB.Rename the configuration files sothat on nodeA the file is backedup to /nodebak/nodemeta_A.xml,and on nodeB the file is backedup to /nodebak/nodemeta_B.xml.

domains.infa Contains connectivity information for the gatewaynodes.

Stored in one of the followinglocations:- The Informatica installation

directory on the client andserver machines.

- The location configuredthrough theINFA_DOMAINS_FILEenvironment variable.

Verify the Domain Configuration Repository RequirementsUse the following rules and guidelines to verify the domain configuration repository database and user accountrequirements:

¨ The database must be accessible to all gateway nodes in the Informatica domain.

¨ The domain configuration can be in the same database schema as the PowerCenter, Metadata Manager, orData Analyzer repositories.

¨ If you create more than one domain, each domain configuration database must have a separate user account.

Oracle Database RequirementsUse the following guidelines when you set up the database on Oracle:

¨ Set the open_cursors parameter to 1000.

¨ The database user account must have the CONNECT, RESOURCE, and CREATE VIEW privileges.

Prepare the Domain 9

IBM DB2 Database RequirementsUse the following guidelines when you set up the repository on IBM DB2:

¨ On the IBM DB2 instance where you create the database, set the following parameters to ON:

- DB2_SKIPINSERTED

- DB2_EVALUNCOMMITTED

- DB2_SKIPDELETED

- AUTO_RUNSTATS

¨ On the database, set the following configuration parameters:

Parameter Value

applheapsz 8192

appl_ctl_heap_sz 8192

logfilsiz 8000

DynamicSections 1000

maxlocks 98

locklist 50000

auto_stmt_stats ONNote: For IBM DB2 9.5 only

¨ Set the tablespace pageSize parameter to 32768.

In a single-partition database, specify a tablespace that meets the pageSize requirements. If you do not specifya tablespace, the default tablespace must meet the pageSize requirements.

In a multi-partition database, you must specify a tablespace that meets the pageSize requirements.

Define the tablespace on a single node.

¨ The database user account must have the CREATETAB and CONNECT privileges.

Note: The default value for DynamicSections in DB2 is too low for the Informatica domain configuration repositoryand Model repository. Informatica requires a larger DB2 package than the default. When you set up the DB2database for the domain configuration repository or a Model repository, you must set the DynamicSectionsparameter to at least 1000. If the DynamicSections parameter is set to a lower number, you can encounterproblems when you install Informatica or when you work with the Analyst tool or Developer tool. The followingerror message can appear:

[informatica][DB2 JDBC Driver]No more available statements. Please recreate your package with a larger dynamicSections value.

10 Chapter 2: Before You Upgrade the Domain and Server Files

Microsoft SQL Server Database RequirementsUse the following guidelines when you set up the repository on Microsoft SQL Server:

¨ Set the read committed isolation level to READ_COMMITTED_SNAPSHOT to minimize locking contention.

To set the isolation level for the database, run the following command:

ALTER DATABASE DatabaseName SET READ_COMMITTED_SNAPSHOT ONTo verify that the isolation level for the database is correct, run the following command:

SELECT is_read_committed_snapshot_on FROM sys.databases WHERE name = DatabaseName¨ The database user account must have the CONNECT, CREATE TABLE, and CREATE VIEW permissions.

Run infasetupInformatica infasetup includes command line programs to back up, restore, and update gateway nodes. infasetupis located in the following directory:

\server

To back up the domain with infasetup, use the following syntax:

BackupDomain

database_user_name

database_password

database_type

[ database_service_name]

backup_file_name

[]

domain_name

[ schema_name Microsoft SQL Server only]

To restore the domain with infasetup, use the following syntax:

RestoreDomain

database_user_name

database_password

database_type

[ database_service_name]

backup_file_name

[]

[]

[ tablespace_name]

[ schema_name Microsoft SQL Server only]

Prepare the Domain 11

To update the gateway node with infasetup, use the following syntax:

UpdateGatewayNode[ database_hostname:database_port

database_connection_string]

[ database_user_name]

[ database_password]

[ database_type]

[ database_service_name]

[ domain_name]

[ node_name]

[ node_host:port]

[ previous_infa_home]

[ https_port]

[ keystore_file_location]

[ keystore_password]

[ log_service_directory]

[ server_admin_port_number]

[ schema_name Microsoft SQL Server only]

Prepare the PowerCenter Repository1. Optimize repository upgrade performance. You can optimize the repository to increase performance when you

upgrade a repository.

2. Configure PowerCenter sessions that contain custom transformations.

3. Migrate the repository to a supported database.

4. Back up the repository.

Optimize Upgrade PerformanceComplete the following tasks to optimize the repository and increase performance when you upgrade:

¨ Purge unnecessary versions from the repository. If your repository is enabled for version control, the repositorycan quickly grow very large depending on the frequency and number of versions added to the repository. Eachversion of an object occupies the same amount of space in the repository database. If the repository is verylarge, determine if there are versions that you do not need and purge these versions.

¨ Truncate the workflow and session log file. Use the Repository Manager or the pmrep TruncateLog commandto truncate the workflow and session log file and delete run-time information you do not need. For example, youcan 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 whenyou upgrade a repository. You can update the statistics before upgrading the repository to increase upgradeperformance.

12 Chapter 2: Before You Upgrade the Domain and Server Files

Configure PowerCenter SessionsIf the PowerCenter repository contains sessions with Custom transformations and if the deterministic property forthe transformation and the session recovery strategy are not configured correctly, the sessions will not run afteryou upgrade. Sessions that will not run meet the following conditions:

¨ The session contains a Custom transformation or a transformation built on the Custom transformation.Transformations built on the Custom transformation include Complex Data Exchange, HTTP, Java, SQL,Union, Web Services Consumer, XML Generator, and XML Parser transformations.

¨ The Output is Deterministic property for a Custom transformation is not enabled.

¨ The session is configured to resume from last checkpoint.

To resume a session, a recovery session must be able to produce the same data in the same order as the originalsession from the resume checkpoint. If a session can be resumed, and you do not enable the Output isDeterministic property for a Custom transformation, the sessions will not run after you upgrade.

To correctly configure the session recovery strategy and deterministic property, complete the following tasksbefore you upgrade:

1. Get the nondeterministic_resumable_pre860.sql SQL script from Informatica Global Customer Support.

2. Run the SQL script on the PowerCenter repository that you want to upgrade.

The script generates a list of sessions that contain Custom transformations with the Output is Deterministicproperty disabled and the session recovery strategy configured to resume from last checkpoint.

3. For each session, determine if the output is deterministic.

Make the following changes on the PowerCenter repository objects:

¨ If the output is deterministic, enable the Output is Deterministic property in the custom transformations forthe session.

¨ If the output is not deterministic, configure the session recovery strategy to restart or fail the session andcontinue the workflow.

Migrate to a Supported DatabaseIf the PowerCenter repository is in a Sybase ASE database, you must migrate it to an IBM DB2 UDB, MicrosoftSQL Server, or Oracle database.

1. Back up the database contents.Select the service in the Administration Console and in the Actions lists select Backup Contents.

2. Disable the service.

3. Create a database user account in a supported database.

4. Update the database connection properties, such as the database type, connect string, database username,and database password.

5. Restore the database backup to the database user account.In the Administration Console, select the service that manages the content that you want to restore and in theActions lists select Restore Contents.

6. Restart the service.

Note: When you restore multiple repositories in a repository domain, register the local repositories with theglobal repository after you restore the repositories.

Prepare the PowerCenter Repository 13

Back Up the RepositoryBack up the PowerCenter repository.

You cannot upgrade a repository or Repository Service that has the same name as the domain or that uses thefollowing characters in the name: ? " : < > * / \ |

If you are upgrading a repository that has the same name as the domain or that has any of these characters in thename, back up the repository and restore it using a different name.

To back up a PowerCenter repository, select the service in the Administration Console and on the Actions listselect Backup Contents.

Prepare the PowerCenter Profiling WarehouseBefore you upgrade the domain, back up the PowerCenter Profiling warehouse.

Use the native database backup option to back up the PowerCenter Profiling warehouse database.

Shut Down the DomainYou must shut down the domain before you upgrade it.

To shut down the domain, stop the Informatica service process on each node in the domain.

You can stop the Informatica service process on each node using one of the following methods:

¨ To stop Informatica from the Windows Start menu, click Programs > Informatica[Version] > Server > StopInformatica Services.

¨ To stop Informatica on UNIX, you use the infaservice command. By default, the infaservice executable file isinstalled in the following directory:

/tomcat/bin Enter the following command to stop the daemon:

infaservice shutdown

You can also stop the Informatica service from the Windows control panel or from the Administrator tool.

14 Chapter 2: Before You Upgrade the Domain and Server Files

C H A P T E R 3

Domain and Server Files UpgradeThis chapter includes the following topics:

¨ Domain and Server Files Upgrade Overview, 15

¨ Upgrading in Graphical Mode, 15

¨ Upgrading in Console Mode, 18

¨ Upgrading in Silent Mode, 19

¨ Troubleshooting the Domain Upgrade, 22

Domain and Server Files Upgrade OverviewUse the server installer to upgrade the server files and domain of a previous version of your Informatica product.The server installer provides a domain upgrade wizard to guide you through the upgrade process.

The upgrade wizard installs the Informatica 9.0.1 files in the installation directory you specify. It does not modifythe files in the directory of the previous version.

The upgrade wizard reads the domain information from files in the previous version and uses the same settings toconfigure the domain and server files for Informatica 9.0.1. It upgrades the tables of the domain configurationrepository in the same database as the previous version.

Complete the pre-upgrade tasks before you start the upgrade. Run the installer on all machines that host previousversions of Informatica that you want to upgrade. On Windows, you can upgrade in graphical or silent mode. OnUNIX, you can upgrade in graphical, console, or silent mode.

Note: On UNIX, use GNU tar to extract the installation files. If the install.sh file does not have sufficientpermissions to run after you extract the installation files, use the chmod command to add execute permissions tothe file. Then run the file with the command ./install.sh.

Upgrading in Graphical ModeYou can upgrade the Informatica domain and server files in graphical mode on Windows or UNIX.

1. Verify that your environment meets the minimum system requirements and complete the pre-upgrade tasks.

2. Log in to the machine with the same user account that you used to install the previous version.

3. Close all other applications.

15

4. To begin the upgrade on Windows, run install.bat from the root directory.

To begin the upgrade on UNIX, use a shell command line to run install.sh from the root directory, and thenselect the option for graphical mode installation.

5. In the Installation Type window, select Upgrade to Informatica 9.0.1 and click Next.

The Upgrade Pre-Requisites window displays the upgrade system requirements. Verify that all requirementsare met before you continue the upgrade.

6. Click Next.

7. In the Upgrade Directory window, enter the following directories:

Directory Description

Directory of the Informaticaproduct to upgrade

Directory that contains the previous version of PowerCenter that you want to upgrade.

Directory for Informatica 9.0.1 Directory in which to install Informatica 9.0.1.Enter the absolute path for the installation directory. The directory cannot be the sameas the directory that contains the previous version of PowerCenter.The directory namesin the path must not contain spaces or the following special characters: @|* $ # ! % ( ){ } [ ] , ; 'On Windows, the installation directory must be on the current machine.

8. Click Next.

The upgrade wizard displays a warning to shut down the Informatica domain before you continue the upgrade.

9. Click OK.

10. In the Pre-Installation Summary window, review the upgrade information, and click Install to continue.

The upgrade wizard installs the Informatica server files to the Informatica 9.0.1 installation directory.

11. In the Domain Configuration Upgrade window, the upgrade wizard displays the database and user accountinformation for the domain configuration repository to be upgraded.

The following table describes the properties that the installer displays for the domain configuration repository:

Property Description

Database type Database for the domain configuration repository.

Database user ID Database user account for the domain configuration repository.

User password Password for the database user account.

Tablespace Displayed for IBM DB2 only. Name of the tablespace for the upgraded domainconfiguration repository tables.If the database of the domain configuration repository that you are upgrading does notuse a 32 K tablespace, this property is blank. Enter the name of a tablespace with apage size of 32 K. In a single-partition database, if you do not specify a tablespacename, the installer writes the upgraded tables in the default tablespace. The defaulttablespace must be 32 K. In a multi-partition database, you must specify a 32 Ktablespace.

16 Chapter 3: Domain and Server Files Upgrade

The upgrade wizard displays the database connection string for the domain configuration repository based onhow the connection string of the previous version was created at installation:

¨ If the previous version used a JDBC URL at installation, the upgrade wizard displays the JDBC connectionproperties, including the database address and service name.

¨ If the previous version used a custom JDBC connection string at installation, the upgrade wizard displaysthe custom connection string.

Optionally, you can specify additional JDBC parameters to include in the connection string. To provideadditional JDBC parameters, select JDBC parameters and enter a valid JDBC parameter string.

12. Click Test Connection to verify that you can connect to the database, and then click OK to continue.

13. Click Next.

On the Port Configuration Upgrade window, the upgrade wizard displays the default port numbers assigned tothe domain and node components.

14. You can specify new port numbers or use the default port numbers.

The following table describes the ports that you can specify:

Port Description

Service Manager port Port number used by the Service Manager in the node. Client applications and theInformatica command line programs use this port to communicate to the services in thedomain.

Informatica Administrator port Port number used by the Administrator tool.Available if you upgrade a gateway node.

Informatica Administratorshutdown port

Port number used by the Administrator tool to listen for shut down commands.Available if you upgrade a gateway node.

15. Click Next.

On Windows, the upgrade wizard creates a service to start Informatica. By default, the service runs under thesame user account as the account used for installation. You can run the Windows service under a differentuser account.

16. Select whether to run the Windows service under a different user account.

The following table describes the properties that you set:

Property Description

Run Informatica under adifferent user account

Indicates whether to run the Windows service under a different user account.

User name User account with which to run the Informatica Windows service.Use the following format:DomainName\UserAccountThis user account must have the Act as operating system permission.

Password Password for the user account with which to run the Informatica Windows service.

17. Click Next.

The Post-Upgrade Summary window indicates whether the upgrade completed successfully.

18. Click Done.

Upgrading in Graphical Mode 17

You can view the upgrade log files to get more information about the tasks performed by the upgrade wizard andto view the configuration of installed components.

Upgrading in Console ModeYou can upgrade the Informatica domain and server files in console mode on UNIX.

When you run the installer in console mode, the words Quit and Back are reserved words. Do not use them asinput text.

Note: When the installer starts in console mode, it displays a message that it is preparing for silent modeinstallation. On Linux IA-64, it displays a message that it cannot find the libc.so.6 file. You can ignore thesemessages.

1. Verify that your environment meets the minimum system requirements, and complete the pre-upgrade tasks.

2. Log in to the machine with the same user account that you used to install the previous version.

3. Stop all processes that access the directory and subdirectories of the Informatica product to upgrade,including command prompts and tail logs.

4. On a shell command line, run the install.sh file located in the root directory.

The installer displays the message to verify that the locale environment variables are set.

5. If the environment variables are not set, enter N to exit the installer and set them as required.

If the environment variables are set, enter Y to continue.

6. Enter C for console mode installation.

7. Enter 2 to upgrade to Informatica 9.0.1.

Review the system requirements and pre-upgrade tasks. Verify that all upgrade requirements are met beforeyou continue.

8. Press Enter.

9. At the prompt, enter the following directories:

Directory Description

Directory of the Informaticaproduct to upgrade

Directory that contains the previous version of PowerCenter that you want to upgrade.

Directory for Informatica 9.0.1 Directory in which to install Informatica 9.0.1. The directory cannot be the same as thedirectory that contains the previous version of PowerCenter.

The installer displays a warning to shut down the Informatica domain that you want to upgrade before youcontinue the upgrade.

10. Press Enter.

11. Review the upgrade information and press Enter to continue.

The installer copies the server files to the Informatica 9.0.1 installation directory.

18 Chapter 3: Domain and Server Files Upgrade

The installer displays the database and user account information for the domain configuration repository toupgrade. It displays the database connection string for the domain configuration repository based on how theconnection string of the previous version was created at installation:

¨ If the previous version used a JDBC URL at installation, the installer displays the JDBC connectionproperties, including the database address and service name.

¨ If the previous version used a custom JDBC connection string at installation, the installer displays thecustom connection string.

12. Press Enter.

13. If the domain configuration repository is in DB2, enter the name of the tablespace.

14. You can specify additional parameters to include in the connection string.

15. The installer displays the default port numbers assigned the domain and node components.

You can specify new port numbers or use the default port numbers.

The following table describes the ports that you can specify:

Port Description

Service Manager port Port number used by the Service Manager in the node. Client applications and theInformatica command line programs use this port to communicate to the services in thedomain.

Informatica Administrator port Port number used by the Administrator tool.Available if you upgrade a gateway node.

Informatica Administratorshutdown port

Port number used by the Administrator tool to listen for shut down commands.Available if you upgrade a gateway node.

The Post-Installation Summary window indicates whether the upgrade completed successfully. It also shows thestatus of the installed components and their configuration.

You can view the upgrade log files to get more information about the upgrade tasks performed by the installer andto view the configuration properties for the installed components.

Upgrading in Silent ModeTo upgrade the Informatica services without user interaction, upgrade in silent mode. Use a properties file tospecify the upgrade options. The installer reads the file to determine the upgrade options. You can use silentmode upgrade to upgrade the Informatica services on multiple machines on the network or to standardize theupgrade process across machines.

Copy the Informatica installation files to the hard disk on the machine that hosts the Informatica instance you planto upgrade.

To upgrade in silent mode, complete the following tasks:

1. Create the upgrade properties file and specify the upgrade options.

2. Run the installer with the upgrade properties file.

Upgrading in Silent Mode 19

Creating the Properties FileInformatica provides a sample properties file that includes the upgrade parameters that are required by theinstaller. You can customize the sample properties file to specify the options for your upgrade.

The sample upgrade properties file is named SilentInput_upgrade.properties and is located in the root directory ofthe installation DVD or the installer download location. After you customize the file, save it with the file nameSilentInput.properties.

1. Go to the root of the directory that contains the installation files.

2. Locate the file named SilentInput_upgrade.properties.

Back up the file before you modify it.

3. Use a text editor to open the file and modify the values of the upgrade parameters.

The following table describes the upgrade parameters that you can modify:

Property Name Description

INSTALL_TYPE Indicates whether to install or upgrade Informatica.If the value is 0, the installer performs a fresh installation of Informatica 9.0.1. If thevalue is 1, the installer upgrades a previous version of Informatica to version 9.0.1.

USER_INSTALL_DIR Directory in which to install Informatica 9.0.1. The directory cannot be the same as thedirectory that contains the previous version of PowerCenter.

UPG_BACKUP_DIR Directory that contains the previous version of PowerCenter that you want to upgrade.

DB2_TABLESPACE For IBM DB2 only. Name of the tablespace in which to create the tables. If thisparameter is empty, the installer creates the tables in the default tablespace. In a multi-partition database, the tablespace page size must be 32 K. Define the database in asingle-node tablespace to optimize performance.

ADVANCE_JDBC_PARAM You can set this parameter if DB_CUSTOM_STRING_SELECTION=0.Optional parameters to include in the JDBC URL connection string. Verify that theparameter string is valid. The installer does not validate the parameter string before itadds the string to the JDBC URL. If this parameter is empty, the installer creates theJDBC URL without additional parameters.

ADVANCE_PORT_CONFIG Indicates whether to display the list of port numbers for the domain and nodecomponents. If the value is 0, the installer assigns default port numbers to the domainand node components. If the value is 1, you can set the port numbers for the domainand node components.

TOMCAT_PORT You can set this parameter if ADVANCE_PORT_CONFIG=1.Port number used by the Service Manager on the node. The Service Manager listensfor incoming connection requests on this port. Client applications use this port tocommunicate with the services in the domain. This is the port that the Informaticacommand line programs use to communicate to the domain. This is also the port forthe SQL data service JDBC/ODBC driver.

AC_PORT You can set this parameter if ADVANCE_PORT_CONFIG=1.Port number used by the Administrator tool.

20 Chapter 3: Domain and Server Files Upgrade

Property Name Description

AC_SHUTDWN_PORT You can set this parameter if ADVANCE_PORT_CONFIG=1.Port number that controls server shutdown for the Administrator tool. The Administratortool listens for shutdown commands on this port.

FORCE_UPGRADE For upgrades from version 8.x. You can set this option when you run the installer againafter a failed upgrade.The installer starts the domain upgrade process from the beginning and overrides allprevious upgrades to the domain. It also overrides any upgrade contention if otheradministrators are upgrading nodes in the domain at the same time.

4. On Windows, specify whether to run the Informatica service under the same user account as the accountused for upgrade.

Set the following parameters:

Property Description

USE_LOGIN_DETAILS Indicates whether to run the Windows service under a different user account. If the valueis 0, the installer configures the service to run under the current user account. If the valueis 1, the installer configures the service to run under a different user account.

WIN_USER_ID User account with which to run the Informatica Windows service.Use the following format:DomainName\UserAccount This user account must have the Act as operating system permission.

WIN_USER_PSSWD Password for the user account with which to run the Informatica Windows service.

5. Save the properties file with the name SilentInput.properties.

Running the Silent InstallerAfter you create the properties file, open a command window to start the silent upgrade.

1. Open a command window.

2. Go to the root of the server installer directory.

3. Verify that the directory contains the file SilentInput.properties with the upgrade options.

4. To start the silent upgrade process, double click the file silentinstall.bat.

The silent upgrade runs in the background. The process can take a while. The silent upgrade process is completewhen the Informatica_9.0.1_Services_InstallLog.log is created in the installation directory.

The silent upgrade fails if you incorrectly configure the properties file or if the installation directory is notaccessible. If the upgrade fails, view the installation log files and correct the errors. Then run the silent installeragain.

Upgrading in Silent Mode 21

Troubleshooting the Domain UpgradeIf the upgrade does not complete successfully, review log files to determine the cause of the failure. The upgradelog files are in the root of the directory where the new version of Informatica is installed. Review the following logfile: Informatica__Services_Upgrade.log

If the upgrade fails, it can result in an inconsistent domain configuration. You can run the installer again to resolvethe inconsistent configuration and complete the upgrade process. When you run the installer again, select theRestart the Domain Configuration Upgrade option. The domain upgrade wizard starts the domain upgrade processfrom the beginning and overrides all previous upgrades to the domain. It also overrides any upgrade contention ifother administrators are upgrading other nodes in the domain at the same time.

Use the following guidelines when you run the installer after a failed upgrade:

¨ Resolve the problem indicated in the upgrade logs before you run the installer again.

¨ Verify that there are no other administrators upgrading other nodes in the domain when you run the installer.

¨ If errors persist after you run the installer with the Restart the Domain Configuration Upgrade option, restorethe domain configuration repository database from backup and run the installer again.

22 Chapter 3: Domain and Server Files Upgrade

C H A P T E R 4

Before You Upgrade theApplication Services

This chapter includes the following topics:

¨ Configure POSIX Asynchronous I/O, 23

¨ Configure Informatica Environment Variables, 23

¨ Configure Locale Environment Variables, 24

¨ Clear Browser Cache, 25

¨ Configure Browser Bookmarks, 25

¨ Prepare to Upgrade LDAP Users and Groups, 25

Configure POSIX Asynchronous I/OIf you install Informatica on IBM AIX, make POSIX Asynchronous I/O available on any node where you want to runa PowerCenter Integration Service. A PowerCenter Integration Service running on an IBM AIX machine can fail tostart if POSIX Asynchronous I/O is not available.

Configure Informatica Environment VariablesYou can configure the INFA_JAVA_OPTS, INFA_DOMAINS_FILE, and INFA_HOME environment variables tostore memory, domain, and location settings.

INFA_JAVA_OPTS

By default, Informatica uses a maximum of 512 MB of system memory. You can use the INFA_JAVA_OPTSenvironment variable to configure the amount of system memory used by Informatica. For example, toconfigure 1 GB of system memory for the Informatica daemon on UNIX in a C shell, use the followingcommand:

setenv INFA_JAVA_OPTS “-Xmx1024m”

On Windows, configure INFA_JAVA_OPTS as a system variable.

On 64-bit HP-UX on Itanium, add the -d64 switch.

Restart the node for the changes to take effect.

23

INFA_DOMAINS_FILE

The installer creates a domains.infa file in the Informatica installation directory. The domains.infa file containsthe connectivity information for the gateway nodes in a domain, including the domain names, domain hostnames, and domain host port numbers.

Set the value of the INFA_DOMAINS_FILE variable to the path and file name of the domains.infa file. If youconfigure the INFA_DOMAINS_FILE variable, you can run infacmd and pmcmd from a directory otherthan /server/bin.

Configure the INFA_DOMAINS_FILE variable on the machine where you install the Informatica services. OnWindows, configure INFA_DOMAINS_FILE as a system variable.

INFA_HOME

Use INFA_HOME to designate the Informatica installation directory. If you modify the Informatica directorystructure, you need to set the environment variable to the location of the Informatica installation directory orthe directory where the installed Informatica files are located.

For example, you use a softlink in UNIX for any of the Informatica directories. To configure INFA_HOME sothat any Informatica application or service can locate the other Informatica components it needs to run, setINFA_HOME to the location of the Informatica installation directory.

Configure Locale Environment VariablesUse LANG, LC_CTYPE, or LC_ALL to set the UNIX code page. Verify that the locale setting is compatible with thecode page for the repository. If the locale setting is not compatible with the repository code page, you cannotcreate a repository service.

Different UNIX operating systems require different values for the same locale. The value for the locale variable iscase sensitive.

Use the following command to verify that the value for the locale environment variable is compatible with thelanguage settings for the machine and the type of code page you want to use for the repository:

locale -a

The command returns the languages installed on the UNIX operating system and the existing locale settings.

Locale on Linux

All UNIX operating systems except Linux have a unique value for each locale. Linux allows different values torepresent the same locale. For example, “utf8,” “UTF-8,” “UTF8,” and “utf-8” represent the same locale on aLinux machine. Informatica requires that you use a specific value for each locale on a Linux machine. Makesure that you set the LANG environment variable appropriately for all Linux machines.

Locale for Oracle Database Clients

For Oracle database clients, set NLS_LANG to the locale you want the database client and server to use withthe login. A locale setting consists of the language, territory, and character set. The value of NLS_LANGdepends on the configuration. For example, if the value is american_america.UTF8, set the variable in a Cshell with the following command:

setenv NLS_LANG american_america.UTF8

24 Chapter 4: Before You Upgrade the Application Services

Clear Browser CacheBefore you access the Administrator tool, clear the browser cache.

On Windows Internet Explorer, delete the browsing history, including temporary files, cookies, and history. OnMozilla Firefox, clear the offline storage.

If you do not clear the browser cache, the previous Administrator tool URL is not redirected to the latest URL andsome menu options may not appear.

Configure Browser BookmarksEffective in version 9.0.1, the Administrator tool URL has changed.

After you upgrade the domain, bookmarks to the Administrator tool are not valid.

Configure bookmarks with one of the following URLs:

¨ http://:

¨ http://:/administrator

Prepare to Upgrade LDAP Users and GroupsIf you upgrade from PowerCenter 8.1.1 and the PowerCenter Repository Service uses LDAP authentication,complete the following steps:

1. In the Administrator tool, configure the LDAP Directory Service property on the LDAP Connectivity tab ofthe LDAP Configuration dialog box.Use the Actions menu on the Security tab to access the LDAP Configuration dialog box.

2. On the Security Domain tab of the LDAP Configuration dialog box, create a security domain and clickSynchronize Now to import the LDAP users into the domain.

3. Run infacmd isp SetRepositoryLDAPConfiguration command to update LDAP configuration properties.Run infacmd from the following location:\server\bin

4. Restart the PowerCenter Repository Service.

Run infacmd SetRepositoryLDAPConfigurationThe infacmd isp SetRepositoryLDAPConfiguration command uses the following syntax:

SetRepositoryLDAPConfiguration

domain_name

user_name

[ password]

[ security_domain]

[ gateway_host1:port gateway_host2:port...]

[ timeout_period_in_seconds]

ldap_server_address

Clear Browser Cache 25

search base

search scope

ldap_principal

ldap_credential

login attribute

login filter

[ use_ssl]

[ certificate database for ssl]

26 Chapter 4: Before You Upgrade the Application Services

C H A P T E R 5

Application Service UpgradeThis chapter includes the following topics:

¨ Application Service Upgrade Overview, 27

¨ Service Upgrade Wizard, 28

Application Service Upgrade OverviewThe product and product version determines the service upgrade process.

Some service versions require a service upgrade. When you upgrade a service, you must also upgrade thedependent services.

Use the service upgrade wizard, the actions menu of each service, or command line to upgrade services. Theservice upgrade wizard upgrades multiple services in the appropriate order and checks for dependencies. If youuse the command line to upgrade services, you must upgrade services in the correct order and verify that youupgrade dependent services.

After you upgrade the PowerCenter Repository Service, you must restart the service and its dependent services.

Note: A user with the Administrator role can upgrade services.

Service Upgrade for PowerCenter 8.1.xBefore you upgrade PowerCenter 8.1.x services, verify the following prerequisites:

¨ If you upgrade a repository that uses LDAP authentication, run the infacmd ispSetRepositoryLDAPConfiguration command to update LDAP configuration properties. Optionally, run infacmdisp ListRepoLDAPConfiguration to list LDAP configuration parameters.

¨ PowerCenter Repository Services are enabled and running in exclusive mode.

To upgrade services, upgrade the following object types:

1. PowerCenter Repository Service

2. Users and groups of each PowerCenter Repository Service

Upgrading Users and GroupsWhen you upgrade the PowerCenter Repository Service users and groups, the Service Manager moves the usersand groups to the domain. You can assign permissions to users after you upgrade users and groups.

You can upgrade users and groups one time for each repository.

27

Rules and Guidelines for Upgrading Native UsersReview the following rules and guidelines before you upgrade users in a repository:

¨ The default repository administrator in the repository is merged with the existing default Administrator useraccount in the domain. The password for the default repository administrator is not merged. You can changethe password for the Administrator user account after you complete the user upgrade process.

¨ The names of upgraded users and groups must conform to the same rules as the names of users and groups inthe domain. During the upgrade, the names of users and groups that are not valid are modified to conform tothe following rules:

- Any character in the user or group name that is not valid is replaced with an underscore. A numeric suffix isadded to the name. For example, the user name Tom*Jones is modified to Tom_Jones0. The followingcharacters are not valid for user or group names: , + " \ < > ; / * % ?

- If the new name with underscore and suffix exists in the native security domain, the suffix is increased by one.

- If a user or group name exceeds 80 characters, the name is shortened to 75 characters plus a numeric suffix.If the new name exists in the security domain, the suffix is increased by one. If the modified name exceeds 80characters, the user account is not upgraded.

¨ During the upgrade, any tab, carriage return, or character that is not valid in user or group descriptions isreplaced with a space. The characters < > “ are not valid in user and group descriptions. For example, thedescription [An example] is modified to [ title An example /title ].

¨ The user and group names are not case sensitive. A user account in the PowerCenter repository with the nameJSmith is a duplicate of a user account in the domain with the name jsmith.

Rules and Guidelines for Upgrading LDAP UsersReview the following rules and guidelines before you upgrade users in a repository that uses LDAP authentication:

¨ If the repository uses LDAP authentication, native users in the repository are not valid and will not be upgraded.

¨ The repository administrator user does not retain Administrator privileges. After you upgrade, use the username Administrator to perform domain administrator tasks. The Administrator user can assign privileges to theprevious repository administrator user after you upgrade users.

¨ If the repository you upgrade uses LDAP authentication, you must create a security domain and import LDAPusers into the domain before you upgrade users and groups. The domain does not verify that upgraded LDAPusers are associated with the LDAP server that PowerCenter used for LDAP.

¨ LDAP users that are not part of a security domain are not upgraded. The Administrator is granted permissionon all repository objects owned by LDAP users that are not upgraded.

Service Upgrade WizardUse the service upgrade wizard to upgrade services.

The service upgrade wizard provides the following options:

¨ Upgrade multiple services.

¨ Enable services before the upgrade.

¨ Automatically or manually reconcile user name and group conflicts.

¨ Display upgraded services in a list along with services that require an upgrade.

¨ Save the current or previous upgrade report.

You can access the service upgrade wizard from the Manage menu in the header area.

28 Chapter 5: Application Service Upgrade

Upgrade ReportThe upgrade report contains the upgrade start time, upgrade end time, upgrade status, and upgrade processingdetails. To save the upgrade report, choose one of the following options:

Save Report

The Save Report option appears on step 4 of the service upgrade wizard.

Save Previous Report

The second time you run the service upgrade wizard, the Save Previous Report option appears on step 1 ofthe service upgrade wizard. If you did not save the upgrade report after upgrading services, you can selectthis option to view or save the previous upgrade report.

Running the Service Upgrade WizardUse the service upgrade wizard to upgrade services.

1. In the Informatica Administrator header area click Manage > Upgrade.

2. Select the objects to upgrade.

3. Optionally, specify if you want to Automatically reconcile user and group conflicts.

4. Click Next.

5. If dependency errors exist, the Dependency Errors dialog box appears. Review the dependency errors andclick OK. Then, resolve dependency errors and click Next.

6. Enter the repository login information. Optionally, choose to use the same login information for allrepositories.

7. Click Next.

The service upgrade wizard upgrades each service and displays the status and processing details.

8. If you are upgrading 8.1.1 PowerCenter Repository Service users and groups for a repository that uses anLDAP authentication, select the LDAP security domain and click Next.

9. If the Reconcile Users and Groups dialog box appears, specify a resolution for each conflict and click Next.

This dialog box appears when you upgrade 8.1.1 PowerCenter Repository Service users and groups and youchoose not to automatically reconcile user and group conflicts.

10. When the upgrade completes, the Summary section displays the list of services and their upgrade status.Click each service to view the upgrade details in the Service Details section.

11. Optionally, click Save Report to save the upgrade details to a file.

If you choose not to save the report, you can click Save Previous Report the next time you launch theservice upgrade wizard.

12. Click Close.

13. Restart upgraded services.

After you upgrade the PowerCenter Repository Service, you must restart the service and its dependentservices.

Users and Groups Conflict ResolutionWhen you upgrade PowerCenter Repository Service users and groups, you can select a resolution for user nameand group name conflicts.

Use the service upgrade wizard to automatically use the same resolution for all conflicts or manually specify aresolution for each conflict.

Service Upgrade Wizard 29

The following table describes the conflict resolution options for users and groups:

Resolution Description

Merge with orMerge

Adds the privileges of the user or group in the repository to the privileges of the user or group in the domain.Retains the password and properties of the user account in the domain, including full name, description,email address, and phone. Retains the parent group and description of the group in the domain. Maintainsuser and group relationships. When a user is merged with a domain user, the list of groups the user belongsto in the repository is merged with the list of groups the user belongs to in the domain. When a group ismerged with a domain group, the list of users the group is merged with the list of users the group has in thedomain. You cannot merge multiple users or groups with one user or group.

Rename Creates a new group or user account with the group or user name you provide. The new group or useraccount takes the privileges and properties of the group or user in the repository.

Upgrade No conflict. Upgrades user and assign permissions.

When you upgrade a repository that uses LDAP authentication, the Users and Groups Without Conflicts sectionof the conflict resolution screen lists the users that will be upgraded. LDAP user privileges are merged with usersin the security domain that have the same name. The LDAP user retains the password and properties of theaccount in the LDAP security domain.

The Users and Groups With Conflicts section shows a list of users that are not in the security domain and willnot be upgraded. If you want to upgrade users that are not in the security domain, use the Security page to updatethe security domain and synchronize users before you upgrade users.

30 Chapter 5: Application Service Upgrade

C H A P T E R 6

Informatica Client UpgradeThis chapter includes the following topics:

¨ Informatica Client Upgrade Overview, 31

¨ Informatica Client Upgrade Options, 32

¨ Upgrading in Graphical Mode, 32

¨ Upgrading in Silent Mode, 33

Informatica Client Upgrade OverviewUse the client installer to upgrade a previous version of the Informatica client tools. The Informatica 9.0.1 clienttools are installed on the installation directory you specify. The client installer configures the newly installed clienttools with the same settings as the previous version. The client installer does not modify the files of the previousversion of the client tools.

Complete the pre-upgrade tasks before you start the upgrade. Run the installer on all machines that host previousversions of the Informatica client tools that you want to upgrade. You can upgrade the Informatica clients ingraphical or silent mode.

When you run the client installer, select the Informatica client tool to upgrade.

For PowerCenter, you can upgrade the PowerCenter Client tools. PowerCenter Client is a set of tools you can useto manage the PowerCenter repository, mappings, and sessions. The client upgrade also upgrades the followingclient tools:

¨ Custom Metadata Configurator

¨ Orchestration Designer

¨ Mapping Architect for Visio

¨ Mapping Analyst for Excel

By default, the when you upgrade PowerCenter Client, the following components are also upgraded:

¨ DataDirect ODBC drivers

¨ Java Runtime Environment libraries

31

Informatica Client Upgrade OptionsYou can upgrade the Informatica client tools in one of the following ways:

¨ Upgrade in Graphical Mode. Upgrades the Informatica client tools in graphical mode. The installer guides youthrough the upgrade process.

¨ Upgrade in Silent Mode. Upgrades the Informatica client tools using a properties file that contains the upgradeoptions.

Upgrading in Graphical Mode1. Close all applications.

2. Run i