Upgrade Guide for Version 8.1 - Informatica · PowerMart, Metadata Manager, Informatica Data...

Informatica PowerCenter (Version 9.1.0 HotFix 6)

Upgrade Guide for Version 8.1.x

Informatica PowerCenter Upgrade Guide for Version 8.1.x

Version 9.1.0 HotFix 6January 2013

Copyright (c) 1998-2013 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), asapplicable.

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 Informatica OnDemand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and InformaticaMaster Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other companyand 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. 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 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 © Rogue 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. Copyright © Thinkmap, Inc. All rights reserved. Copyright © Clearpace Software Limited. All rights reserved. Copyright © InformationBuilders, Inc. All rights reserved. Copyright © OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo Communications, Inc. All rightsreserved. Copyright © International Organization for Standardization 1986. All rights reserved. Copyright © ej-technologies GmbH . All rights reserved. Copyright © JaspersoftCorporation. 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 and http://www.openssl.org/source/license.html.

This product includes Curl software which is Copyright 1996-2007, Daniel Stenberg, <[email protected]>. 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://dojotoolkit.org/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, http://fusesource.com/downloads/license-agreements/fuse-message-broker-v-5-3- license-agreement; http://antlr.org/license.html; http://aopalliance.sourceforge.net/; http://www.bouncycastle.org/licence.html; http://www.jgraph.com/jgraphdownload.html; http://www.jcraft.com/jsch/LICENSE.txt. http://jotm.objectweb.org/bsd_license.html; http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231; http://www.slf4j.org/license.html; http://developer.apple.com/library/mac/#samplecode/HelpHook/Listings/HelpHook_java.html; http://www.jcraft.com/jsch/LICENSE.txt; http://nanoxml.sourceforge.net/orig/copyright.html; http://www.json.org/license.html; http://forge.ow2.org/projects/javaservice/, http://www.postgresql.org/about/licence.html, http://www.sqlite.org/copyright.html, http://www.tcl.tk/software/tcltk/license.html, http://www.jaxen.org/faq.html, http://www.jdom.org/docs/faq.html, and http://www.slf4j.org/license.html.

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), the Sun Binary Code LicenseAgreement Supplemental License Terms, the BSD License (http:// www.opensource.org/licenses/bsd-license.php) the MIT License (http://www.opensource.org/licenses/mit-license.php) and the Artistic License (http://www.opensource.org/licenses/artistic-license-1.0).

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; 7,496,588; 7,523,121; 7,584,422, 7,720,842;7,721,270; and 7,774,791 , international Patents and other Patents Pending.

DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the impliedwarranties of noninfringement, 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-91000-HF6-0001

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vInformatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Customer Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Informatica Multimedia Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

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

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

Changing the Node Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Upgrading Data Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

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

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

Review the Windows Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

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

Review the Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Review the Maximum Heap Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Review the UNIX Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Review the Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Review the Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Set the File Descriptor Limit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Review the Maximum Heap Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Set Up the X Window Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Uninstall Data Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Backing Up Essential Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Uninstalling Previous Version of Data Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Prepare the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Migrate to a Supported Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Truncate the Domain Configuration Database Table Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Back Up the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Verify the Domain Configuration Repository Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Prepare the PowerCenter Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Table of Contents i

Gather User Privilege Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Optimize Upgrade Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Configure PowerCenter Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Migrate to a Supported Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Back Up the Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Prepare the PowerCenter Profiling Warehouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Shut Down the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Prepare to Change the Node Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configure the Windows Machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configure the UNIX Machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Copy the Installation Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Verify Keystore File Name and Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

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

Upgrading in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Upgrading in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Upgrading in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Creating the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Upgrading with Changes to the Node Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Upgrading in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Upgrading in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Upgrading in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Troubleshooting the Domain Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 4: Before You Upgrade the Application Services. . . . . . . . . . . . . . . . . . . . . . . . . . 40Pre-Upgrade Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Configure POSIX Asynchronous I/O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Configure Informatica Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Configure Locale Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Clear Browser Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Configure Browser Bookmarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

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

Change the Node Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Install the Database Client Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Configure Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Verify that a Graphics Display Server is Available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Update Port Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Verify the Node Backup Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Update Keystore File Name and Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configure PowerExchange Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

ii Table of Contents

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

Service Upgrade for PowerCenter 8.1.x. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Service Upgrade Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Upgrade Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Running the Service Upgrade Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Users and Groups Conflict Resolution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

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

Informatica Client Upgrade Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Upgrading in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Upgrading in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Creating the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Chapter 7: After You Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56After You Upgrade Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Informatica Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Configure LDAP Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Update the Log Events Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Update ODBC Data Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

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

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

PowerCenter Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Operating Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Reassign Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

PowerCenter Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Associate Linked Domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Re-create PowerCenter Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Verify PowerCenter Repository Database User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Web Services Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Associate Linked Domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Verify PowerCenter Repository Database User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Grant Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Export Consolidation Transformation Objects to PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Appendix A: Upgrade Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Upgrade Checklist Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Before You Upgrade the Domain and Server Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Domain and Server Files Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Table of Contents iii

Before You Upgrade the Application Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Application Service Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Informatica Client Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

After You Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

iv Table of Contents

PrefaceThe Upgrade Guide for Version 8.1.x is written for the system administrator who is responsible for upgrading theInformatica 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 [email protected]. 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.

v

http://mysupport.informatica.com

mailto:[email protected]


http://www.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 [email protected].

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 [email protected].

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

Toll FreeFrance: 0805 804632Germany: 0800 5891281Italy: 800 915 985Netherlands: 0800 2300001Portugal: 800 208 360Spain: 900 813 166Switzerland: 0800 463 200United Kingdom: 0800 023 4632

Standard RateBelgium: +31 30 6022 797France: +33 1 4138 9226Germany: +49 1805 702 702Netherlands: +31 306 022 797United Kingdom: +44 1628 511445

Toll FreeAustralia: 1 800 151 830New Zealand: 09 9 128 901

Standard RateIndia: +91 80 4112 5738

vi Preface






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.1.0 HotFix 6:

Informatica Product Version Comments

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

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

Informatica PowerCenter 8.6 If the PowerCenter 8.6 domain includes the Metadata ManagerService, Reporting Service, or Reference Table Manager Service,you must first upgrade to PowerCenter 8.6.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 Data Explorer Advanced Edition 9.0 You must first upgrade to Data Explorer Advanced Edition 9.0.1. Seethe Informatica Data Quality 9.0 upgrade documentation. Completethe steps to upgrade Informatica Data Quality 9.0 unless anexception is specified.

Informatica Data Quality 9.0 You must first upgrade to Data Quality 9.0.1.

1

Informatica Product Version Comments

Informatica Data Services 9.0 You must first upgrade to Data Services 9.0.1.

Informatica PowerCenter 9.0 You must first upgrade to PowerCenter 9.0.1.

Informatica Data Explorer Advanced Edition 9.0.1

Informatica Data Quality 9.0.1

Informatica Data Services 9.0.1

Informatica PowerCenter 9.0.1

Informatica Data Explorer 9.1.0 or 9.1.0 HotFix Release For information about applying the hotfix, see the Release Notes.

Informatica Data Quality 9.1.0 or 9.1.0 HotFix Release For information about applying the hotfix, see the Release Notes.

Informatica Data Services 9.1.0 or 9.1.0 HotFix Release For information about applying the hotfix, see the Release Notes.

Informatica PowerCenter 9.1.0 or 9.1.0 HotFix Release For information about applying the hotfix, see the Release Notes.

If the product version you use cannot be upgraded to Informatica 9.1.0 HotFix 6, you must first upgrade to asupported version.

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 all 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.1.0 applicationservices.The upgrade creates a new default Administrator useraccount in the domain.

Starts Informatica Services. Starts Informatica Services on the node.

2 Chapter 1: Upgrade Overview

¨ 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 servicesthat must 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.

Changing the Node ConfigurationThe installer provides the option to allow changes to node host name and port number. When you select thisoption you can change the node configuration. Change the node configuration when you move the Informaticainstallation to a different machine.

If you choose the option to update the node configuration on one gateway node, you must use this option on allgateway nodes in the domain.

If you choose the option to update the node configuration, you need to perform additional upgrade steps. Thereare additional steps before you upgrade the domain and server files, and before you upgrade the applicationservices.

Upgrading Data TransformationIf you want to upgrade Data Transformation Engine and Data Transformation Studio on the same machine,upgrade the client before you upgrade the domain and server files. The client and server upgrades must be 32-bit.

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 the 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 the gateway nodebefore you 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 PowerCenter Client.

6. Perform the post-upgrade tasks.

Note: If you upgrade more than one Informatica product or if you upgrade the Informatica product on more thanone machine, complete the first upgrade using the detailed instructions in this guide. You can use the upgradechecklist in the appendix to perform subsequent upgrades.

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 Windows Requirements, 4

¨ Review the UNIX Requirements, 7

¨ Uninstall Data Transformation, 10

¨ Prepare the Domain, 11

¨ Prepare the PowerCenter Repository, 16

¨ Prepare the PowerCenter Profiling Warehouse, 18

¨ Shut Down the Domain, 18

¨ Prepare to Change the Node Configuration, 19

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

1. Review the operating system specific requirements.

2. Uninstall Informatica B2B Data Transformation.

3. Prepare the domain.

4. Prepare the PowerCenter repository.

5. Prepare the PowerCenter profiling warehouse.

6. Shut down the domain.

7. Prepare to change the node configuration.

Review the Windows RequirementsBefore you upgrade the domain, review the following Windows requirements:

1. Review the prerequisites.

4

2. Review the environment variables.

Review the PrerequisitesVerify that your system meets the upgrade requirements.

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

Component Processor RAM Disk Space

Domain with all Data Quality, Data Services, andPowerCenter services running on one node

4 CPU 10 GB 12 GB

Domain with all PowerCenter services running on onenode

2 CPU 4 GB 10 GB

Domain with all PowerCenter services running on onenode except Metadata Manager Service and ReportingService

1 CPU 2 GB 10 GB

Metadata Manager Service running on a separate node 2 CPU 4 GB 10 GB

Reporting Service running on a separate node 1 CPU 512 MB 10 GB

Metadata Manager Agent 1 CPU 512 MB 220 MB

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 lists the minimum system requirements to run PowerCenter Client:

Client Processor RAM Disk Space

PowerCenter Client 1 CPU 512 MB 1.2 GB

For more information about Informatica platform support, see the Product Availability Matrix at https://communities.informatica.com/community/my-support/tools/product-availability-matrices.

Temporary Disk Space Requirements for InstallationThe 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.

The following table lists the temporary disk space requirements during installation of Informatica services:

Product Disk Space

Installer 1 GB

Informatica Services 605 MB

Review the Windows Requirements 5

https://communities.informatica.com/community/my-support/tools/product-availability-matrices

The following table lists the temporary disk space requirements during installation of Informatica clients:

Product Disk Space

Installer 1 GB

Informatica Clients 550 MB

Review the Environment VariablesConfigure the environment variables to work with the Informatica installation.

The following table describes environment variables to review on Windows:

Variable Description

%TEMP% Location of the temporary files created during installation. Informatica requires 1 GBdisk space for temporary files.Configure the environment variable if you do not want to create temporary files in thedefault drive.

PATH Verify that the PATH environment variables do not contain earlier versions ofInformatica.

Library path Verify that the library path environment variables do not contain earlier versions ofInformatica.

INFA_HOME Contains the location of the Informatica installation directory. Clear this variablebefore you start the upgrade.

INFA_DOMAINS_FILE Contains the location of the domains.infa file. Clear this variable before you start theupgrade.

Review the Maximum Heap SizeVerify that Informatica Services uses the required maximum heap size for the number of users in the domain.

The following table lists the minimum requirement for the maximum heap size settings, based on the number ofusers and services in the domain:

Number of Domain Users Maximum Heap Size(1-5 Services)

Maximum Heap Size(6-10 Services)

1,000 or less 512 MB (default) 1024 MB

5,000 2048 MB 3072 MB

10,000 3072 MB 5120 MB

20,000 5120 MB 6144 MB

30,000 5120 MB 6144 MB

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

Note: The maximum heap size settings in the table are based on the number of PowerCenter Repository Servicesin the domain.

If the domain has more than 1,000 users, update the maximum heap size based on the number of users in thedomain.

1. Extract the installation files.

2. Go to the following directory:<installer>\source\tomcat\bin.

3. Use a text editor to open the infaservice.bat file.

4. Search for the following text: INFA_JAVA_OPTS=% INFA_JAVA_OPTS% -XX.

5. Set the value for -Xmx to the maximum heap size required for the number of Informatica domain users.For example, to set the maximum heap size to 3072 MB, use the following configuration:

set INFA_JAVA_OPTS=% INFA_JAVA_OPTS% -XX:GCTimeRatio=9 -Xmx3072m

Review the UNIX RequirementsBefore you upgrade the domain, review the following UNIX requirements:

1. Review the prerequisites.

2. Review the environment variables.

3. Verify the file descriptor settings.

4. Set up the X Windows server.

Review the PrerequisitesThe following table lists the minimum system requirements for a domain with different node configurations:

Component Processor RAM Disk Space

Domain with all Data Quality, Data Services, andPowerCenter services running on one node

4 CPU 10 GB 12 GB

Domain with all PowerCenter services running on onenode

2 CPU 4 GB 10 GB

Domain with all PowerCenter services running on onenode except Metadata Manager Service and ReportingService

1 CPU 2 GB 10 GB

Metadata Manager Service running on a separate node 2 CPU 4 GB 10 GB

Reporting Service running on a separate node 1 CPU 512 MB 10 GB

Metadata Manager Agent 1 CPU 512 MB 220 MB

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.

For more information about Informatica platform support, see the Product Availability Matrix at https://communities.informatica.com/community/my-support/tools/product-availability-matrices.

Review the UNIX Requirements 7

https://communities.informatica.com/community/my-support/tools/product-availability-matrices

Temporary Disk Space Requirements for InstallationThe 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.

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

Product Disk Space

Installer 1 GB

Informatica Services 2 GB

Review the Environment VariablesConfigure the environment variables to work with the Informatica installation.

Create the environment variables with the system user account that you will use for installation. Log in with theaccount that you plan to use to install Informatica, and then set the environment variables.

The following table describes environment variables to review on UNIX:

Variable Description

IATEMPDIR Location of the temporary files created during installation. Informatica requires 1 GBdisk space for temporary files.Configure the environment variable if you do not want to create temporary files in the /tmp directory.

PATH Verify that the PATH environment variables do not contain earlier versions ofInformatica.

Library path Verify that the library path environment variables do not contain earlier versions ofInformatica.

JRE_HOME If you install the Informatica services on a machine with 32-bit or 64-bit SUSE Linuxor Linux EMT64 operating system, clear the JRE_HOME environment variable beforeyou start the installation.

Locale environment variables Use 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 thelanguage that you use:- English: C- Japanese: ja_JP.SJIS or ja_JP.PCK- Portuguese: pt_BR.ISO8859-1, pt_BR.8859-15, or pt_BRAfter you install, update the locale setting to one that is compatible with the codepage of the repository.

INFA_HOME Contains the location of the Informatica installation directory. Clear this variablebefore you start the upgrade.

INFA_DOMAINS_FILE Contains the location of the domains.infa file. Clear this variable before you start theupgrade.


Set the File Descriptor LimitVerify 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 8,000 orhigher. The recommended limit is 16,000 file descriptors per process.

Review the Maximum Heap SizeVerify that Informatica Services uses the required maximum heap size for the number of users in the domain.

The following table lists the minimum requirement for the maximum heap size settings, based on the number ofusers and services in the domain:

Number of Domain Users Maximum Heap Size(1-5 Services)

Maximum Heap Size(6-10 Services)

1,000 or less 512 MB (default) 1024 MB

5,000 2048 MB 3072 MB

10,000 3072 MB 5120 MB

20,000 5120 MB 6144 MB

30,000 5120 MB 6144 MB

Note: The maximum heap size settings in the table are based on the number of PowerCenter Repository Servicesin the domain.

If the domain has more than 1,000 users, update the maximum heap size based on the number of users in thedomain.

1. Extract the installation files.

2. Go to the following directory:<installer>\source\tomcat\bin.

3. Use a text editor to open the infaservice.bat file.

4. Search for the following text: INFA_JAVA_OPTS=% INFA_JAVA_OPTS% -XX.

5. Set the value for -Xmx to the maximum heap size required for the number of Informatica domain users.For example, to set the maximum heap size to 3072 MB, use the following configuration:

set INFA_JAVA_OPTS=% INFA_JAVA_OPTS% -XX:GCTimeRatio=9 -Xmx3072m

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

Review the UNIX Requirements 9

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

Shell Command Example

C setenv DISPLAY <TCP/IP node of XWindow server>:0 setenv DISPLAY 10.1.50.23:0

Bash/Korn export DISPLAY=”<TCP/IP node of XWindow server>:0” export DISPLAY=”10.1.50.23:0”

Bourne DISPLAY=”<TCP/IP node of XWindow server>: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 installer uses, the installer can display incorrect labels onthe buttons.

Uninstall Data TransformationIf your machine has a previous version of Data Transformation, you must uninstall it before you upgradeInformatica services or clients:

¨ Back up essential files on your design and production environments.

¨ Uninstall the previous version of Data Transformation.

Backing Up Essential FilesBefore you install a new version of Data Transformation, you must back up the following essential files that werecreated under previous versions:

Directory Default Location

Workspace(design environmentonly)(rev. 9.0.1.1 and earlier)

C:\Documents and Settings\<user>\My Documents\Informatica\DataTransformation\<version_number>\workspace

Repository <INSTALL_DIR>/DataTransformation/ServiceDB

Custom GlobalComponents directory(TGP files)

<INSTALL_DIR>/DataTransformation/autoInclude/user

Custom GlobalComponents directory(DLL and JAR files)

<INSTALL_DIR>/DataTransformation/externLibs/user

Configuration file <INSTALL_DIR>/DataTransformation/CMConfig.xml

License file <INSTALL_DIR>/DataTransformation/CDELicense.cfg


Directory Default Location

Library files <INSTALL_DIR>\DataTransformation\Libraries

Library files The following files under <INSTALL_DIR>\DataTransformation\eclipse3_3\plugins:- com.informatica.libeditor.compare_<version>.jar- com.informatica.libeditor.DigesterWrap_<version>.jar- com.informatica.libeditor.gen_wiz_<version>.jar- com.informatica.libeditor.launcher_<version>.jar- com.informatica.libeditor.run_validations_<version>.jar- com.informatica.libeditor_<version>.jar- All other plugins with names that start with com.informatica.libeditor_

SWIFT library files com.informatica.libeditor.BicLookup_<version>.jar

FpML or SEPA libraryfiles

- com.informatica.libeditor.propertypages_<version>.jar- com.informatica.libeditor_xsd_<version>.jar

Uninstalling Previous Version of Data TransformationThe installer cannot upgrade Data Transformation directly from version 9.0.1.1 or earlier.

If you have Data Transformation version 9.0.1.1 or earlier, you must uninstall it before you install the currentversion.

If you have 32-bit Data Transformation, you must uninstall it before you migrate to 64-bit Data Transformation.

1. Close all applications that use Data Transformation services.

2. If you are uninstalling version 4.x, uninstall all libraries.

3. Uninstall Data Transformation.

For more information about uninstalling version 9.1.0, see Uninstalling Data Transformation. For moreinformation about uninstalling previous versions, see the Data Transformation Administrator Guide for yourversion.

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

1. Migrate to a supported database.

2. Truncate the domain configuration database table data.

3. Back up the domain.

4. Verify the domain configuration repository requirements.

Migrate to a Supported DatabaseIf the domain configuration repository is in a Sybase database version that is not supported, you must migrate to adatabase version that is supported. For example, if the domain configuration repository is in a Sybase ASE 12database, upgrade to Sybase ASE 15.0.3.

1. Shut down all application services in the domain.

Prepare the Domain 11

2. Shut down the domain.

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

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

5. Restore the domain configuration backup to the database schema.Run the infasetup RestoreDomain command to restore the domain configuration in the backup file to thespecified database schema.

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. When you run the installer on each gateway node, select the option to Allow changes to thehost name and port number. When you select this option you can update the location of the domainconfiguration repository.

Truncate the Domain Configuration Database Table DataBefore you upgrade the domain, truncate the domain configuration database table data to reduce the upgrade time.

Complete the following steps to truncate the domain configuration database table data:

¨ Run infasetup backupdomain and then restoredomain to truncate the following domain configuration databasetables.

¨ Delete the log files from the Informatica installation directories.

Run infasetup backupdomain and then restoredomain to truncate the following domain configuration databasetables:

¨ PCSF_RUN_LOG¨ PCSF_CPU_USAGE_SUMMARY¨ PCSF_REPO_USAGE_SUMMARY¨ PCSF_SOURCE_AND_TARGET_USAGE

Delete the log files from the following Informatica installation directories:

¨ <PowerCenterInstallationDir>/server/tomcat/logs¨ <PowerCenterInstallationDir>/server/infa_shared/logs

Truncate Domain Configuration Database Table Data LimitationsConsider the following limitations when you truncate the domain configuration database tables:

¨ When you truncate the PCSF_RUN_LOG table, you cannot fetch logs for sessions and workflows that ran priorto the upgrade. The PCSF_RUN_LOG table contains a large amount of data.

¨ When you truncate the PCSF_CPU_USAGE_SUMMARY table, the License Management Report does notshow CPU usage information prior to the upgrade.

¨ When you truncate the PCSF_REPO_USAGE_SUMMARY table, the License Management Report does notshow repository usage information prior to the upgrade.

¨ When you truncate the PCSF_SOURCE_AND_TARGET_USAGE table, the License Management Report doesnot show source and target connectivity information prior to the upgrade.


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.

Informatica infasetup includes command line programs to back up and restore the domain. infasetup is located inthe following directory:

<Informatica Installation Directory>\server

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

BackupDomain <<-DatabaseAddress|-da> database_hostname:database_port|

<-DatabaseConnectionString|-cs> database_connection_string>

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

[<-SchemaName|-sc> schema_name Microsoft SQL Server only]

Back up the metadata configuration files to any directory accessible by the machines where you install Informatica.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,


Metadata File Description Location

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 repository on Oracle:

¨ Set the open_cursors parameter to 1000 or higher.

¨ Verify the database user has CONNECT, RESOURCE, and CREATE VIEW privileges.

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


Parameter Value

DynamicSections 1000

maxlocks 98

locklist 50000

auto_stmt_stats ONFor 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.

¨ Verify the database user has CREATETAB and CONNECT privileges.

Note: The default value for DynamicSections in DB2 is too low for the Informatica repositories. Informaticarequires a larger DB2 package than the default. When you set up the DB2 database for the domain configurationrepository or a Model repository, you must set the DynamicSections parameter to at least 1000. If theDynamicSections parameter is set to a lower number, you can encounter problems when you install or runInformatica. The following error message can appear:

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

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.

Sybase ASE Database RequirementsUse the following guidelines when you set up the repository on Sybase ASE:

¨ Set the database server page size to 16K or higher. You must set the page size to 16K as this is a one-timeconfiguration and cannot be changed afterwards.

¨ Set the following database locking configuration to use row-level locking:

Database Configuration Sybase System Procedure Value

Lock scheme sp_configure "lock scheme" 0, datarows

¨ Set the Sybase database option ddl in tran to TRUE.


¨ Turn ON the Sybase database option select into/bulkcopy/pllsort.

¨ Enable the "select" privilege for the sysobjects sytem table.

¨ Create the following login script to disable the default VARCHAR truncation:

create procedure dbo.sp_string_rtrunc_proc as set string_rtruncation onsp_modifylogin "user_name", "login script", sp_string_rtrunc_proc

The login script is executed every time the user logs into the Sybase instance. The stored procedure sets theparameter at the session level. The sp_modifylogin system procedure updates "user_name" with the storedprocedure as its "login script". The user must have permission to invoke the stored procedure.

¨ Verify the database user has CREATE DEFAULT, CREATE PROCEDURE, CREATE RULE, CREATE TABLE,and CREATE VIEW privileges.

¨ Set the following database memory configurations to the recommended baseline values:

Database Configuration Sybase System Procedure Value

Maximum amount of total physicalmemory

sp_configure "max memory" 2097151

Procedure cache size sp_configure "procedure cache size" 500000

Number of open objects sp_configure "number of open objects" 5000

Number of open indexes sp_configure "number of open indexes" 5000

Number of open partitions sp_configure "number of open partitions" 5000

Heap memory per user sp_configure "heap memory per user" 49152

Number of locks sp_configure "number of locks" 100000

Adjust the above recommended values according to what operations are performed on the database.

Prepare the PowerCenter RepositoryBefore you upgrade the domain, prepare the PowerCenter repository for upgrade.

1. Optimize repository upgrade performance. You can optimize the repository to increase performance when youupgrade a repository.

2. Configure PowerCenter sessions that contain custom transformations.

3. Migrate to a supported database.

4. Back up the repository.

Gather User Privilege InformationIf the domain uses LDAP authentication, make a list of users with each of the following PowerCenter 8.1.1repository privileges:

¨ Admin Integration Service


¨ Admin Repository

¨ Super User

After the upgrade, you will reassign the privileges.

Optimize Upgrade PerformanceOptimize the repository and increase performance when you upgrade.

Complete the following tasks to optimize performance:

¨ 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, purge versions that you do not need.

¨ 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 that you do not need. Forexample, you can delete all log events older than one month before you upgrade the repository.

¨ Update statistics. PowerCenter identifies and updates the statistics of all repository tables and indexes whenyou upgrade a repository. To increase upgrade performance, you can update the statistics before you upgradethe repository.

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.

Prepare the PowerCenter Repository 17

Migrate to a Supported DatabaseIf the PowerCenter repository is in a Sybase database version that is not supported, you must migrate to adatabase version that is supported. For example, if the PowerCenter repository is in a Sybase ASE 12 database,upgrade to Sybase ASE 15.0.3.

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

2. Disable the service.

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

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

5. Enable the service in exclusive mode.

6. Restore the repository backup to the database schema.In the Administration Console, select the service that manages the content that you want to restore and in theActions lists select Restore Contents.

7. Change the operating mode of the service to normal and 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.

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:

<InformaticaInstallationDir>/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.

Prepare to Change the Node ConfigurationBefore you change the node configuration, complete the following steps on the machine where you want the newversion of Informatica to run:

1. Review the operating system specific requirements.

2. Copy the installation directory.

3. Verify the keystore file name and location.

Configure the Windows MachineBefore you upgrade the domain and server files, complete the following Windows tasks:

1. Determine port availability.

2. Create a system user account.

Note: Services may fail to start if there is a port number conflict.

Determine Port AvailabilityThe installer sets up the ports for components in the Informatica domain, and it designates the ports to use forapplication service processes that run on the node where you install Informatica.

You can specify the port numbers to use for the components and a range of port numbers to use for theapplication services. Or you can use the default port numbers provided by the installer. Verify that the portnumbers are available on the machines where you install the Informatica services.

The following table describes the ports used by Informatica:

Port Type Description

Domain port Port number for the node created during installation.

Service Manager port Port number used by the Service Manager on the node. The Service Manager listens forincoming connection requests on this port. Client applications use this port to communicatewith the services in the domain. This is the port that the Informatica command line programsuse to communicate to the domain. This is also the port for the SQL data service JDBC/ODBCdriver. Default is 6006.

Prepare to Change the Node Configuration 19


Service Manager shutdownport

Port number that controls server shutdown for the domain Service Manager. The ServiceManager listens for shutdown commands on this port. Default is 6008.

Informatica Administrator port Port number used by the Administrator tool. Default is 6007.

Informatica Administratorshutdown port

Port number that controls server shutdown for the Administrator tool. The Administrator toollistens for shutdown commands on this port. Default is 6009.

Range of ports forapplication services

Range of port numbers that can be assigned to the application service processes that run onthe node. When you create an application service in the domain, the Service Manager assignsthe first available port in this range to the service process. At a minimum, the number of portsin the range must be at least twice the number of application service processes that will run onthe node. Default is 6013 to 6113.

Note: Services and nodes can fail to start if there is a port conflict. You can update the range of ports forapplication services after you upgrade.

Create a System User AccountCreate a system user account to perform the installation and to run the Informatica service. Verify that the useraccount that you use to install the Informatica services has write permission on the installation directory.

You can install Informatica with the user account logged in to the machine and run it under another user account.You can create a local account or a domain account to install Informatica or run the Informatica Windows service.

Note: To access a repository on Microsoft SQL Server that uses a Windows trusted connection, create a domainaccount.

The user accounts require the following permissions to run the installer or to run the Informatica Windows service:

¨ Logged in user account. The user account must be a member of the Administrators group and have the Logon as a service permission. Log in with this user account before you install Informatica.

¨ Another user account. The user account must be a member of the Administrators group and have Log on asa service and Act as operating system permissions. You do not have to log in with this user account before youinstall Informatica. During installation, you can specify the user account to run the Informatica Windows service.

Configure the UNIX MachineBefore you upgrade the domain and server files, complete the following UNIX tasks:

1. Determine port availability.

2. Create a system user account.

Note: Services may fail to start if there is a port number conflict.

Determine Port AvailabilityThe installer sets up the ports for components in the Informatica domain, and it designates the ports to use forapplication service processes that run on the node where you install Informatica.

You can specify the port numbers to use for the components and a range of port numbers to use for theapplication services. Or you can use the default port numbers provided by the installer. Verify that the portnumbers are available on the machines where you install the Informatica services.


The following table describes the ports used by Informatica:


Domain port Port number for the node created during installation.

Service Manager port Port number used by the Service Manager on the node. The Service Manager listens forincoming connection requests on this port. Client applications use this port to communicatewith the services in the domain. This is the port that the Informatica command line programsuse to communicate to the domain. This is also the port for the SQL data service JDBC/ODBCdriver. Default is 6006.


Port number that controls server shutdown for the domain Service Manager. The ServiceManager listens for shutdown commands on this port. Default is 6008.

Informatica Administrator port Port number used by the Administrator tool. Default is 6007.


Port number that controls server shutdown for the Administrator tool. The Administrator toollistens for shutdown commands on this port. Default is 6009.

Range of ports forapplication services

Range of port numbers that can be assigned to the application service processes that run onthe node. When you create an application service in the domain, the Service Manager assignsthe first available port in this range to the service process. At a minimum, the number of portsin the range must be at least twice the number of application service processes that will run onthe node. Default is 6013 to 6113.

Note: Services and nodes can fail to start if there is a port conflict. You can update the range of ports forapplication services after you upgrade.

Create a System User AccountCreate a user account specifically to run the Informatica daemon.

Verify that the user account you use to install Informatica has write permission on the installation directory.

Copy the Installation DirectoryCopy the directory of the previous version of Informatica to the machine where you want the new version ofInformatica to run. For example, if the previous version of Informatica is installed in C:\Informatica\861, copy the C:\Informatica\861 directory and subdirectories to the new machine.

When you run the upgrade installer, specify the Informatica installation directory on the new machine as the onethat you want to upgrade.

Verify Keystore File Name and LocationIf the node uses HTTPS, verify that the keystore file is in the default location and that it uses the default file name.If the keystore file uses a different file name or directory, the Administrator tool fails to start after you upgrade thedomain.

The default location for the keystore file is <InformaticaInstallationDir>/server/tomcat/conf. The default filename for the keystore file is PC_Default.keystore.

After you upgrade, you can use infasetup UpdateGatewayNode or UpdateWorkerNode to update the keystore filename and location.

Prepare to Change the Node Configuration 21

C H A P T E R 3

Domain and Server Files UpgradeThis chapter includes the following topics:

¨ Domain and Server Files Upgrade Overview, 22

¨ Upgrading in Graphical Mode, 23

¨ Upgrading in Console Mode, 26

¨ Upgrading in Silent Mode, 28

¨ Upgrading with Changes to the Node Configuration, 30

¨ Troubleshooting the Domain Upgrade, 39

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

The upgrade wizard installs Informatica 9.1.0 HotFix 6 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.1.0 HotFix 6. It upgrades the tables of the domainconfiguration repository 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.

If you want to upgrade Data Transformation Engine and Data Transformation Studio on the same machine,upgrade the client before you upgrade the domain and server files. The client and server upgrades must be 32-bit.

You can upgrade Informatica from a DVD or from the root of the directory where you download the installer files.On Windows, the length of the entire installer directory path, including the zip file name, must be 60 characters orless. On UNIX, use native tar or GNU tar to extract the installer files. The user that runs the installer must haveread and write permissions on the installer files directory and execute permissions on install.sh.

22

Upgrading in Graphical ModeUse this procedure to upgrade the domain and server files on the same machine. You can upgrade the domainand server files in graphical mode on Windows or UNIX. If you install Informatica on the SUSE Linux Enterprise 11platform, perform the installation in console mode or silent mode.

To upgrade the domain and server files to another machine and modify the node configuration, see “ Upgradingwith Changes to the Node Configuration” on page 30.

On Windows, if you encounter problems when you run the install.bat file from the root directory, run the followingfile:

<InformaticaInstallationDir>/server/install.exe

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

2. Close all other applications.

3. Begin the upgrade from Windows or UNIX:

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

4. Select Install or upgrade Informatica and click Start.

If you are upgrading from Informatica 9.1.0, select Apply HotFix 6 to Informatica 9.1.0. See theInformatica 9.1.0 HotFix 6 Release Notes for information about applying the hotfix.

5. On the Installation Type page, select Upgrade to Informatica 9.1.0 with HotFix 6 and click Next.

The Upgrade Pre-Requisites page displays the upgrade system requirements.

6. Verify the requirements before you continue the upgrade.

7. Click Next.

8. On the Upgrade Directory page, 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.1.0HotFix 6

Directory in which to install Informatica 9.1.0 HotFix 6.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.

9. Verify that the Allow changes to the node host name and port numbers option is not selected.

10. Click Next.

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

11. Click OK.

12. On the Pre-Installation Summary page, review the upgrade information, and click Install to continue.

The upgrade wizard installs the Informatica server files to the Informatica 9.1.0 HotFix 6 installation directory.

13. If you are upgrading a gateway node, the upgrade wizard displays the database and user account informationfor the domain configuration repository to be upgraded.

Upgrading in Graphical Mode 23

If you are upgrading a worker node, the upgrade wizard does not display the domain configuration repositoryinformation. You cannot modify the database connection information.

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. Name of the tablespace for the upgraded domain configurationrepository 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.

Schema Name Displayed for Microsoft SQL Server. Name of the schema that will contain domainconfiguration tables. If not selected, the installer creates the tables in the defaultschema.

Trusted Connection Displayed for Microsoft SQL Server. Indicates whether to connect to Microsoft SQLServer through a trusted connection. Trusted authentication uses the securitycredentials of the current user to make the connection to Microsoft SQL Server. If notselected, the installer uses Microsoft SQL Server authentication.

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.

14. If you are upgrading a gateway node, the upgrade wizard displays the database and user account informationfor the domain configuration repository to be upgraded.

If you are upgrading a worker node, the upgrade wizard does not display the domain configuration repositoryinformation. You cannot modify the database connection information.

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


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.

24 Chapter 3: Domain and Server Files Upgrade


Tablespace Displayed for IBM DB2. Name of the tablespace for the upgraded domain configurationrepository 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.

Schema Name Displayed for Microsoft SQL Server. Name of the schema that will contain domainconfiguration tables. If not selected, the installer creates the tables in the defaultschema.

Trusted Connection Displayed for Microsoft SQL Server. Indicates whether to connect to Microsoft SQLServer through a trusted connection. Trusted authentication uses the securitycredentials of the current user to make the connection to Microsoft SQL Server. If notselected, the installer uses Microsoft SQL Server authentication.

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.

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

16. Click Next.

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

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


Port number that controls server shutdown for the domain Service Manager. TheService Manager listens for shutdown commands on this port.

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


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

18. Click Next.

Upgrading in Graphical Mode 25

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.

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

The following table describes the properties that you set:


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.

20. Click Next.

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

21. Click Done.

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 ModeUse this procedure to upgrade the domain and server files on the same machine. You can upgrade the Informaticadomain 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.

When the installer starts in console mode, it displays a message that it is preparing for silent mode installation. OnSolaris, it displays a message that it cannot find the install.bin file. You can ignore these messages.


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

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

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

5. Enter 1 to install or upgrade Informatica.

If you are upgrading from Informatica 9.1.0, enter 3 to apply Informatica 9.1.0 HotFix 6. See the Informatica9.1.0 HotFix 6 Release Notes for information about applying the hotfix.


6. Enter C for console mode installation.

7. Enter 2 to upgrade to Informatica 9.1.0 HotFix 6.

Review the system requirements and pre-upgrade tasks.

8. Verify the upgrade requirements before you continue.

9. Press Enter.

10. At the prompt, enter the following directories:





Directory in which to install Informatica 9.1.0 HotFix 6. The directory cannot be thesame as the directory that contains the previous version of PowerCenter.

11. Enter 1 to use the same node configuration as the previous version.

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

12. Press Enter.

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

The installer copies the server files to the Informatica 9.1.0 HotFix 6 installation directory.

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.

14. Press Enter.

15. If the domain configuration repository is in IBM DB2, enter the name of the tablespace. If the domainconfiguration repository is in Microsoft SQL Server, enter the Schema Name and indicate whether to connectto Microsoft SQL Server through a trusted connection.

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

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


Port Description




Informatica Administrator port Port number used by the Administrator tool.

Upgrading in Console Mode 27

Port Description

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 ModeUse this procedure to upgrade the domain and server files on the same machine.


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

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. Find 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. If the value is1, the installer upgrades a previous version of Informatica.

USER_INSTALL_DIR Directory in which to install the new version of PowerCenter. The directory cannot bethe same as the directory 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 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.You can set this parameter if DB_CUSTOM_STRING_SELECTION=0.

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 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.You can set this parameter if ADVANCE_PORT_CONFIG=1.

SERVER_PORT Port number that controls server shutdown for the domain Service Manager. TheService Manager listens for shutdown commands on this port. You can set thisparameter if ADVANCE_PORT_CONFIG=1.

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

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

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.

Upgrading in Silent Mode 29

Set the following parameters:


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_<Version>_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 silent upgrade log file and correct the errors. Then run the silent installeragain. The silent upgrade log file name is silentErrorLog.log. The installer creates it in the root directory onWindows and in the user home directory on UNIX.

Upgrading with Changes to the Node ConfigurationThe installer provides the option to allow changes to the node host name and port numbers. Select this option toupgrade the server files and change the configuration the node.

Complete the pre-upgrade tasks before you run the installer. On Windows, you can run the installer in graphical orsilent mode. On UNIX, you can run the installer in graphical, console, or silent mode.

Upgrading in Graphical ModeUse this procedure to upgrade the domain and server files to another machine and modify the node configuration.To upgrade the domain and server files on the same machine, see “Upgrading in Graphical Mode” on page 23.

You can upgrade the Informatica domain and server files in graphical mode on Windows or UNIX. If you upgradeInformatica on the SUSE Linux Enterprise 11 platform, perform the upgrade in console mode or silent mode.


On Windows, if you encounter problems when you run the install.bat file from the root directory, run the followingfile:

<InformaticaInstallationDir>/server/install.exe


2. Close all other applications.

3. Begin the upgrade from Windows or UNIX:

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

4. Select Install or upgrade Informatica and click Start.

If you are upgrading from Informatica 9.1.0, select Apply HotFix 6 to Informatica 9.1.0. See theInformatica 9.1.0 HotFix 6 Release Notes for information about applying the hotfix.

5. On the Installation Type page, select Upgrade to Informatica 9.1.0 with HotFix 6 and click Next.

The Upgrade Pre-Requisites page displays the upgrade system requirements.


7. Click Next.

8. On the Upgrade Directory page, enter the following directories:





Directory in which to install Informatica 9.1.0 HotFix 6.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.

9. Select Allow changes to the node host name and port numbers.

Use this option to change the configuration of the Informatica product that you upgrade. If you are upgradingto a different machine, you can change the node configuration to match the new machine.

10. Click Next.

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

11. Click OK.

12. On the Pre-Installation Summary page, review the upgrade information, and click Install to continue.

The upgrade wizard installs the Informatica server files to the Informatica 9.1.0 HotFix 6 installation directory.

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

14. Click Next.

The installer displays the domain and node properties.

15. Modify the node host name and port number to match the configuration of the new version of Informatica.

Upgrading with Changes to the Node Configuration 31

The following table describes the domain and node properties that you can specify:


Domain name Name of the domain. The default domain name is Domain_<MachineName>. The namemust not exceed 128 characters and must be 7-bit ASCII only. It cannot contain a spaceor any of the following characters: ` % * + ; " ? , < > \ /

Node name Name of the node that you are upgrading.

Node host name Host name of the machine that hosts the node you are upgrading. If the machine has asingle network name, use the default host name. If the machine has multiple networknames, you can modify the default host name to use an alternate network name.Optionally, you can use the IP address.Note: Do not use localhost. The host name must explicitly identify the machine.

Node port number Port number for the node you are upgrading. The default port number for the node is6005.

Gateway node host name Host name of the machine that hosts the gateway node for the domain.Available if you upgrade a worker node.

Gateway node port number Port number of the gateway node.Available if you upgrade a worker node.

16. If you are using a custom keystore file and you are upgrading to a different gateway node configuration,specify the custom keystore file password and location.

The following table describes the properties for the custom keystore file password and location:


Custom Keystore Password Plain text password for the custom keystore file.

Custom Keystore File Path and file name of the custom keystore file. If you leave this field blank, the installerlooks for the keystore file in the following directory:<InformaticaInstallationDir>\server\tomcat\conf\

17. Click Next.

On the Port Configuration Upgrade page, the upgrade wizard displays the port numbers assigned to thedomain and node components.

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


Port Description





Port Description




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

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

The following table describes the properties that you set:


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.

21. Click Next.

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

22. Click Done.

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 ModeUse this procedure to upgrade the domain and server files to another machine and modify the node configuration.To upgrade the domain and server files on the same machine, see “Upgrading in Console Mode” on page 26.

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

When the installer starts in console mode, it displays a message that it is preparing for silent mode installation. OnSolaris, it displays a message that it cannot find the install.bin file. You can ignore these messages.


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

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


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

5. Enter 1 to install or upgrade Informatica.

If you are upgrading from Informatica 9.1.0, enter 3 to apply Informatica 9.1.0 HotFix 6. See the Informatica9.1.0 HotFix 6 Release Notes for information about applying the hotfix.

6. Enter C for console mode installation.

7. Enter 2 to upgrade to Informatica 9.1.0 HotFix 6.

Review the system requirements and pre-upgrade tasks.


9. Press Enter.

10. At the prompt, enter the following directories:





Directory in which to install Informatica 9.1.0 HotFix 6. The directory cannot be thesame as the directory that contains the previous version of PowerCenter.

11. Enter 2 to allow changes to the node host name and port number.

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

12. Press Enter.

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

The installer copies the server files to the Informatica 9.1.0 HotFix 6 installation directory.

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.

14. Press Enter.

15. If the domain configuration repository is in DB2, you can specify the name of the tablespace.

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

The installer displays the domain and node properties.

17. Modify the node host name and port number to match the configuration of the new version of Informatica.


The following table describes the domain and node properties that you can specify:


Domain name Name of the domain. The default domain name is Domain_<MachineName>. The namemust not exceed 128 characters and must be 7-bit ASCII only. It cannot contain a spaceor any of the following characters: ` % * + ; " ? , < > \ /

Node name Name of the node that you are upgrading.

Node host name Host name of the machine that hosts the node you are upgrading. If the machine has asingle network name, use the default host name. If the machine has multiple networknames, you can modify the default host name to use an alternate network name.Optionally, you can use the IP address.Note: Do not use localhost. The host name must explicitly identify the machine.

Custom keystore password Plain text password for the custom keystore file. Enter the custom keystore password ifyou are using a custom keystore file and you are upgrading to a different gateway nodeconfiguration.

Custom keystore file Path and file name of the custom keystore file. Enter the custom keystore file if you areusing a custom keystore file and you are upgrading to a different gateway nodeconfiguration.If you leave this field blank, the installer looks for the keystore file in the followingdirectory:<InformaticaInstallationDir>\server\tomcat\conf\

Node port number Port number for the node you are upgrading. The default port number for the node is6005.

Gateway node host name Host name of the machine that hosts the gateway node for the domain.Available if you upgrade a worker node.

Gateway node port number Port number of the gateway node.Available if you upgrade a worker node.

18. The installer displays the port numbers assigned the domain components.

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


Port Description






Port number used by the Administrator tool to listen for shut down commands.


Port Description

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 ModeUse this procedure to upgrade the domain and server files to another machine and modify the node configuration.To upgrade the domain and server files on the same machine, see “Upgrading in Silent Mode” on page 28.

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





The sample upgrade properties file is named SilentInput_Upgrade_NewConfig.properties and is located in the rootdirectory of the installation DVD or the installer download location. After you customize the file, save it with the filename SilentInput.properties.

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

2. Find the file named SilentInput_Upgrade_NewConfig.properties.



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

Parameter Name Description

INSTALL_TYPE Indicates whether to install or upgrade Informatica.To upgrade from a previous version of Informatica, set the value to 1.

UPG_DIFF_CONFIG Indicates whether to change the node configuration for the new version of Informatica.To upgrade a previous version of Informatica to a different machine configuration, setthis parameter to 1.



USER_INSTALL_DIR Directory in which to install Informatica the new version of Informatica. The directorycannot be the same as the directory that contains the previous version.

UPG_BACKUP_DIR Directory that contains the previous version of Informatica product that you want toupgrade.

DB_TYPE Database for the domain configuration repository. The value can be one of thefollowing databases:- Oracle- MSSQLServer- DB2- Sybase

DB_UNAME Database user account name for the domain configuration repository.

DB_PASSWD Password for the database user account.

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.

SQLSERVER_SCHEMA_NAME

For Microsoft SQL Server. Name of the schema that will contain domain configurationtables. If this parameter is empty, the installer creates the tables in the default schema.

TRUSTED_CONNECTION For Microsoft SQL Server. Indicates whether to connect to Microsoft SQL Serverthrough a trusted connection. If this parameter is empty, the installer uses MicrosoftSQL Server authentication.Set this parameter only if you are installing on Windows.

DB_CUSTOM_STRING_SELECTION

Determines whether to use a JDBC URL or a custom connection string to connect tothe domain configuration repository database.If the value is 0, the installer creates a JDBC URL from the database properties youprovide. If the value is 1, the installer uses the custom connection string you provide.

DB_SERVICENAME Required if DB_CUSTOM_STRING_SELECTION=0.Service name for Oracle and IBM DB2 databases or database name for Microsoft SQLServer.

DB_ADDRESS Required if DB_CUSTOM_STRING_SELECTION=0.Host name and port number for the database instance in the format HostName:Port.

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.

DB_CUSTOM_STRING Required if DB_CUSTOM_STRING_SELECTION=1.Valid custom JDBC connection string.

DOMAIN_HOST_NAME Host name of the machine that hosts the node that you are upgrading. If the machinehas a single network name, use the default host name. If the machine has multiplenetwork names, you can modify the default host name to use an alternate networkname. Optionally, you can use the IP address.Note: Do not use localhost. The host name must explicitly identify the machine.



DOMAIN_PORT Port number for the node that you are upgrading.

GATEWAYNODE_HOST Required if you upgrade a worker node.Host name of the machine that hosts the gateway node.

GATEWAYNODE__PORT Required if you upgrade a worker node.Port number for the gateway node.

CUSTOM_KEYSTORE_FILE_UPGRADE

Path and file name of the custom keystore file. Enter the custom keystore file if you areusing a custom keystore file and you are upgrading to a different gateway nodeconfiguration.If you leave this field blank, the installer looks for the keystore file in the followingdirectory:<InformaticaInstallationDir>\server\tomcat\conf\

CUSTOM_KEYSTORE_PSSWD_UPGRADE

Plain text password for the custom keystore file. Enter the custom keystore password ifyou are using a custom keystore file and you are upgrading to a different gatewaynode configuration.

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

SERVER_PORT You can set this parameter if ADVANCE_PORT_CONFIG=1.Port number that controls server shutdown for the domain Service Manager. TheService Manager listens for shutdown commands on this port. Default is 6008.

AC_PORT Port number used by the Administrator tool.

AC_SHUTDWN_PORT 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:


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.



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



The silent upgrade runs in the background. The process can take a while. The silent upgrade process is completewhen the Informatica_<Version>_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 silent upgrade log file and correct the errors. Then run the silent installeragain. The silent upgrade log file name is silentErrorLog.log. The installer creates it in the root directory onWindows and in the user home directory on UNIX.

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_<Version>_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.

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

Troubleshooting the Domain Upgrade 39

C H A P T E R 4

Before You Upgrade theApplication Services

This chapter includes the following topics:

¨ Pre-Upgrade Tasks, 40

¨ Configure POSIX Asynchronous I/O, 40

¨ Configure Informatica Environment Variables, 41

¨ Configure Locale Environment Variables, 41

¨ Clear Browser Cache, 42

¨ Configure Browser Bookmarks, 42

¨ Prepare to Upgrade LDAP Users and Groups, 42

¨ Change the Node Configuration, 43

Pre-Upgrade TasksBefore you upgrade the application services, complete the following tasks:

1. Configure POSIX Asynchronous I/O.

2. Configure Informatica environment variables.

3. Configure locale environment variables.

4. Clear browser cache.

5. Configure browser bookmarks.

6. Prepare to upgrade LDAP users and groups.

7. Tasks for changing the node configuration.

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.

40

Configure Informatica Environment VariablesYou can configure the INFA_DOMAINS_FILE and INFA_HOME environment variables to store the domain andinstallation location settings.

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 other than /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_LANG

Configure Informatica Environment Variables 41

depends 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

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 BookmarksAfter you upgrade the domain, bookmarks to the Administrator tool are not valid.

Configure bookmarks with one of the following URLs:

¨ http://<host>:<port>

¨ http://<host>:<administrator_port>/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:<9.1.0 InformaticaInstallationDir>\server\bin

4. Restart the PowerCenter Repository Service.

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

SetRepositoryLDAPConfiguration

<-DomainName|-dn> domain_name

<-UserName|-un> user_name

[<-Password|-pd> password]

42 Chapter 4: Before You Upgrade the Application Services

[<-SecurityDomain|-sdn> security_domain]

[<-Gateway|-hp> gateway_host1:port gateway_host2:port...]

[<-ResilienceTimeout|-re> timeout_period_in_seconds]

<-LDAPAddress|-la> ldap_server_address

<-SearchBase|-sb> search base

<-SearchScope|-ss> search scope

<-LDAPPrincipal|-lp> ldap_principal

<-LDAPCredential|-lc> ldap_credential

<-LoginAttribute|-lt> login attribute

<-LoginFilter|-lf> login filter

[<-UseSSL|-us> use_ssl]

[<-CertificateDatabase|-cd> certificate database for ssl]

Change the Node ConfigurationIf you chose the option to update the node configuration, before you upgrade the application services, you mustcomplete the following additional steps:

1. Install the database client software.

2. Configure the environment variables.

3. Verify that a graphics display server is available.

4. Update port numbers.

5. Verify the location of the node backup directory.

6. Update the keystore file name and location.

7. Configure PowerExchange Adapters.

Install the Database Client SoftwareInstall database client software and configure connectivity on the gateway node and on the nodes that will run thePowerCenter Integration Service and PowerCenter Repository Service processes.

PowerCenter Integration ServiceDepending on the types of databases that the PowerCenter Integration Service will access, install the followingdatabase clients on the machine where the PowerCenter Integration Service runs:

¨ Oracle client

¨ IBM DB2 Client Application Enabler (CAE)

¨ Microsoft SQL Client, with Microsoft OLE DB provider for Microsoft SQL Server

¨ Sybase Open Client

¨ Teradata BTEQ client

Change the Node Configuration 43

PowerCenter Repository ServiceBased on the repository database, install the following database clients on the machine where the PowerCenterRepository Service runs:

¨ Oracle client

¨ IBM DB2 Client Application Enabler (CAE)

¨ Microsoft SQL Client, with Microsoft OLE DB provider for Microsoft SQL Server

¨ Sybase Open Client (OCS)

Database Client Environment VariablesConfigure database client environment variables on the machines that run the PowerCenter Integration Serviceand the PowerCenter Repository Service processes. The database client path variable name and requirementsdepend on the UNIX platform and repository database.

After you configure the database environment variables, you can test the connection to the database from thedatabase client.

The following table describes the database environment variables you need to set in UNIX:

Database Environment VariableName

DatabaseUtility

Value

Oracle ORACLE_HOMEPATH

sqlplus Set to: <DatabasePath>Add: <DatabasePath>/bin

IBM DB2 DB2DIRDB2INSTANCEPATH

db2connect Set to: <DatabasePath>Set to: <DB2InstanceName>Add: <DatabasePath>/bin

Sybase ASE SYBASE12 or SYBASE15SYBASE_ASESYBASE_OCSPATH

isql Set to: <DatabasePath>/sybase<version>Set to: ${SYBASE[12 | 15]}/ASE-<version>Set to: ${SYBASE[12 | 15]}/OCS-<version>Add: ${SYBASE_ASE}/bin:${SYBASE_OCS}/bin:$PATH

Teradata PATH bteq Add: <DatabasePath>/bin

Configure Environment VariablesInformatica uses environment variables to store configuration information when it runs the application services andconnects to the clients. Configure the environment variables to meet the Informatica requirements. Incorrectlyconfigured environment variables can cause the Informatica domain or nodes to fail to start or can causeconnection problems between the Informatica clients and the domain.

To configure environment variables on UNIX, log in with the system user account you used to install Informatica.

Library Path Environment VariablesConfigure library path environment variables on the machines that run the PowerCenter Integration Service andPowerCenter Repository Service processes. The library path variable name and requirements depend on theUNIX platform and database.


Solaris and Linux

On Solaris and Linux, configure the LD_LIBRARY_PATH environment variable.

The following table describes the values you set for the LD_LIBRARY_PATH for the different databases:

Database Value

Oracle <DatabasePath>/lib

IBM DB2 <DatabasePath>/lib

Sybase ASE “${SYBASE_OCS}/lib:${SYBASE_ASE}/lib:${LD_LIBRARY_PATH}”

Informix <DatabasePath>/lib

Teradata <DatabasePath>/lib

ODBC <CLOSEDODBCHOME>/lib

AIX

On AIX, configure the LIBPATH environment variable.

The following table describes the values you set for the LIBPATH for the different databases:

Database Value



Sybase ASE “${SYBASE_OCS}/lib:${SYBASE_ASE}/lib:${LIBPATH}”




HP-UX

On HP-UX, configure the SHLIB_PATH environment variable.

The following table describes the values you set for the SHLIB_PATH for the different databases:

Database Value



Sybase ASE "${SYBASE_OCS}/lib:${SYBASE_ASE}/lib:${SHLIBPATH}"



Database Value



Java Component VariablesInformatica installs the JRE to use with the following Java-based components:

¨ Custom transformations that use Java

¨ Java transformations

¨ PowerExchange for JMS

¨ PowerExchange for Web Services

¨ PowerExchange for webMethods

To use these components on AIX64, or HP-UX, configure the library path environment variables to point to thejava directory installed with Informatica. Configure these environment variables on machines where thePowerCenter Integration Service process runs.

The following table describes the library paths you configure to use Java-based components:

UNIX Platform Environment Variable Name Value

AIX64 LIBPATH Set to: java/jre/binSet to: java/jre/bin/classicSet to: /usr/lib:/lib

HP-UX SHLIB_PATH Set to: java/jre/lib/PA_RISC2.0/serverSet to: java/jre/lib/PA_RISC2.0Set to: /usr/lib:/lib

Verify that a Graphics Display Server is AvailableThe gateway nodes on UNIX require a graphics display server to run domain reports in Informatica Administrator.If you do not have a graphics display server, you can install and configure X Virtual Frame Buffer (Xvfb). Xvfb is anX server that renders graphics to virtual memory rather than to a graphics display device.

You can download and install Xvfb for the following operating systems:

¨ HP-UX. Xvfb is part of the HP-UX operating system. Install HP-UX patches and graphical packages to run Xvfbbased on when you installed or last patched the operating system. For instructions to run Xvfb on HP-UX, seethe following web site:

http://publib.boulder.ibm.com/tividd/td/ITM/GI10-5797-01/en_US/HTML/notesmst20.htm¨ AIX and Linux. Download and install Xvfb. For instructions to run Xvfb on AIX and Linux, see 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 Xvfb for Solaris from the following web site:http://ferret.pmel.noaa.gov/FERRET_17sep07/FAQ/graphics/Solaris_Xvfb.html


Download and set up Xvfb for Solaris and use the following command to start 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

Update Port NumbersTo avoid startup failure, update port numbers for service processes and service manager shutdown.

Services can fail to start if there are port conflicts with the service process port numbers. You can configure theminimum and maximum port numbers for service processes in the Advanced Properties section of the nodeProperties view.

To update the service process port numbers for a node, configure the following advanced properties:

¨ Minimum Port Number

¨ Maximum Port Number

Verify the Node Backup DirectoryVerify that the backup directory for the node is accessible by the node. View the Backup Directory configurationin the Advanced Properties section of the node Properties view.

Update Keystore File Name and LocationIf the node uses HTTPS and you moved the keystore file or renamed the keystore file before you upgraded thedomain, you can update the file name and location to match your previous configuration.

Use infasetup UpdateGatewayNode or UpdateWorkerNode to update the keystore file name and location.

Configure PowerExchange AdaptersIf your previous installation included PowerExchange adapters, configure the PowerExchange adapters on themachine that runs the new version of Informatica. If the PowerExchange adapter has an installer, re-install thePowerExchange adapter.


C H A P T E R 5

Application Service UpgradeThis chapter includes the following topics:

¨ Application Service Upgrade Overview, 48

¨ Service Upgrade Wizard, 49

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.

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.

¨ You have the Administrator role on the domain.

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.

48

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 [<title>An example</title>] 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.

Service Upgrade Wizard 49

¨ Automatically restart the services after they have been upgraded.

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

Upgrade ReportThe upgrade report contains the upgrade start time, upgrade end time, upgrade status, and upgrade processingdetails. The Services Upgrade Wizard generates the upgrade report.

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 recycle services after upgrade.

If you choose to automatically recycle services after upgrade, the upgrade wizard restarts the services afterthey have been upgraded.

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

5. Click Next.

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

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

8. Click Next.

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

9. 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 OK.

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

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.

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

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

13. Click Close.

50 Chapter 5: Application Service Upgrade

14. If you did not choose to automatically recycle services after upgrade, 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.

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

Resolution Description

Merge with or Merge Adds the privileges of the user or group in the repository tothe privileges of the user or group in the domain. Retains thepassword 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 thedomain. Maintains user and group relationships. When a useris merged with a domain user, the list of groups the userbelongs to in the repository is merged with the list of groupsthe user belongs to in the domain. When a group is mergedwith a domain group, the list of users the group is mergedwith the list of users the group has in the domain. You cannotmerge multiple users or groups with one user or group.

Rename Creates a new group or user account with the group or username you provide. The new group or user account takes theprivileges 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.

Service Upgrade Wizard 51

C H A P T E R 6

Informatica Client UpgradeThis chapter includes the following topics:

¨ Informatica Client Upgrade Overview, 52

¨ Informatica Client Upgrade Options, 53

¨ Upgrading in Graphical Mode, 53

¨ Upgrading in Silent Mode, 54

Informatica Client Upgrade OverviewUse the client installer to upgrade a previous version of the Informatica client tools. The Informatica 9.1.0 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

¨ 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

Upgrade the Informatica client tools from a DVD or from the root of the directory where you download the installerfiles. On Windows, the length of the entire installer directory path, including the zip file name, must be 60characters or less.

52

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 ModeIf you encounter problems when you run the install.bat file from the root directory, run the following file:

<InformaticaInstallationDir>/client/install.exe

1. Close all applications.

2. Run install.bat from the root directory.

3. Select Install or Upgrade Informatica and click Start.

4. On the Installation Type page, select Upgrade to Informatica 9.1.0 Clients with HotFix 6 and click Next.

5. On the Upgrade Pre-Requisites page, verify the system requirements before you continue the installationand click Next.

6. On the Select Client Tool Selection page, select the Informatica client you want to upgrade.

You can upgrade the following Informatica client applications:

¨ Informatica Developer

¨ PowerCenter Client

7. Click Next.

8. On the Select Directory page, enter the following directories:


Directory of the Informaticaclient to upgrade

Directory that contains the previous version of the Informatica client tool that you wantto upgrade.

Directory for the Informatica 9.1.0 HotFix 6 client tools

Directory in which to install the Informatica 9.1.0 HotFix 6 client tools.Enter the absolute path for the installation directory. The installation directory must beon the current machine. The directory names in the path must not contain spaces or thefollowing special characters: @|* $ # ! % ( ) { } [ ] , ; '

9. Click Next.

10. On the Pre-Installation Summary page, review the installation information and click Install.

The installer copies the Informatica client files to the installation directory.

11. On the Post-installation Summary page, verify whether the upgrade completed successfully and click Done.

You can view the installation log files to get more information about the upgrade tasks performed by the installer.

Informatica Client Upgrade Options 53

Upgrading in Silent ModeTo upgrade the Informatica client tools 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 client tools 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 client you plan toupgrade.





The sample properties file is named SilentInput.properties and is located in the root of the client installer directory.

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

2. Locate the file named SilentInput.properties.



The following table describes the upgrade parameters you can modify:


INSTALL_TYPE Indicates whether to install or upgrade the Informatica client tools.To upgrade from a previous version of Informatica, set the value to 1.

UPG_BACKUP_DIR Directory of the previous version of the Informatica tools that you want toupgrade.

USER_INSTALL_DIR Directory in which to install the new version of the Informatica client tools.

DXT_COMP Indicates whether to install Informatica Developer.If the value is 1, the Developer tool will be installed. If the value is 0, theDeveloper tool will not be installed.Default is 1.

CLIENT_COMP Indicates whether to install the PowerCenter Client.If the value is 1, the PowerCenter Client will be installed. If the value is 0, thePowerCenter Client will not be installed.Default is 1.

DT_COMP Indicates whether to install the Data Transformation Studio. If the value is 0, theData Transformation Studio will not be installed. Default is 1. Set this value to 0.

NEW_ECLIPSE_SELECTION You can set this parameter if DT_COMP=1. Indicates whether to install the copyof Eclipse that is bundled with the installer or use an Eclipse developmentenvironment that is already installed on your machine.

54 Chapter 6: Informatica Client Upgrade


If the value is 0, the installer uses the Eclipse development environment that isalready installed on your machine. Set the ECLIPSE_LOCATION property.If the value is 1, the setup installs the copy of Eclipse that is bundled with theinstaller.Default is 1.

ECLIPSE_LOCATION Required if NEW_ECLIPSE_SELECTION=0.Absolute path of the existing eclipse.exe file.

4. Save the properties file.



2. Go to root of the client installer directory.



The silent upgrade runs in the background. The process can take a while. The silent upgrade process is completewhen the Informatica_<Version>_Client_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 55

C H A P T E R 7

After You UpgradeThis chapter includes the following topics:

¨ After You Upgrade Overview, 56

¨ Informatica Domain, 56

¨ PowerCenter Repository Service, 57

¨ PowerCenter Integration Service, 58

¨ Web Services Hub, 59

¨ Grant Permissions, 59

¨ Export Consolidation Transformation Objects to PowerCenter, 60

After You Upgrade OverviewAfter you run the installer, you need to perform additional tasks to complete the upgrade. Additional tasks mightinclude the upgrade of services or the update of the database and driver infrastructures. Work with the domain andservice administrators to complete the post-upgrade tasks.

Informatica DomainAfter you upgrade, complete the post-upgrade tasks for the domain.

Configure LDAP ConnectivityIf the domain uses LDAP authentication, update the LDAP configuration after you upgrade.

The default maximum size for user import is set to 1000. Previously, the default value was set to 0, whichindicated that there was no maximum value.

When you upgrade, all users are imported into the domain. However, all users over 1,000 will be dropped inreverse alphabetic order the next time the Service Manager synchronizes with the LDAP service directory.

To avoid dropping users, reset the maximum size in the LDAP connectivity configuration.

56

Update the Log Events DirectoryWhen you upgrade the domain, the log events directory points to the location you specified in the previousversion. When you upgrade the domain with changes to the node configuration, the log events directory points tothe isp/logs directory in the new installation directory.

To use a different directory for the logs, update the Log Directory Path property for the domain in the Administratortool. You can also use infasetup updateGatewaynode to update the directory. For example, you can configure thelog events directory as the server/infa_shared/logs directory in the new installation directory.

Update ODBC Data SourcesThe Informatica installation includes DataDirect ODBC drivers. Re-create each ODBC data source to use the newdrivers.

Update Statistics for the Domain Configuration RepositoryIf the domain configuration repository is in an IBM DB2 9.1 database, run the DB2 reorgchk command to optimizedatabase operations. The reorgchk command generates the database statistics used by the DB2 optimizer inqueries and updates.

Use the following command:

REORGCHK UPDATE STATISTICS on SCHEMA SchemaName

View Log Events from the Previous Informatica VersionYou can view the log events from the previous Informatica version to troubleshoot domain issues.

Use infacmd isp ConvertLogFile command to view log files from PowerCenter 8.1.1, 8.5.x and 8.6.x.

The infacmd isp ConvertLogFile command uses the following syntax:

ConvertLogFile

<-InputFile|-in> input_file_name

[<-Format|-fm> format_TEXT_XML]

[<-OutputFile|-lo> output_file_name]

PowerCenter Repository ServiceAfter you upgrade, complete the post-upgrade tasks for the PowerCenter Repository Service.

Operating ModeAfter you upgrade the PowerCenter Repository Service, the service remains in Exclusive mode.

Change the operating mode of the PowerCenter Repository Service to Normal mode and restart the service.

Reassign PrivilegesIf the domain uses LDAP authentication, reassign privileges to users.

PowerCenter Repository Service 57

Referring to the list of users with PowerCenter 8.1.1 repository privileges you wrote down before you performedthe domain and server upgrade, reassign the following privileges:

¨ If the user had the Admin Integration Service privilege, assign the Manage Services and Access InformaticaAdministrator privileges.

¨ If the user had the Admin Repository, assign the Grant Privileges and Roles, Manage Users, Groups, andRoles, Manage Service Execution, Manage Services, and Access Informatica Administrator privileges.

¨ If the user had the Super User privilege, assign all privileges.

PowerCenter Integration ServiceAfter you upgrade, complete the post-upgrade tasks for the PowerCenter Integration Service.

Associate Linked DomainsIf you used a linked domain repository in the previous installation, specify a repository that exists in the domain forthe associated repository of the PowerCenter Integration Service.

You cannot associate a PowerCenter Integration Service in the local domain with a PowerCenter RepositoryService in another domain. When you upgrade a domain, the PowerCenter Integration Service loses the linkeddomain repository association.

To apply changes, restart the PowerCenter Integration Service.

Re-create PowerCenter Integration ServiceIf the PowerCenter Integration Service has the same name as the domain, re-create the PowerCenter IntegrationService. You cannot have services in the domain that have the same name as the domain.

Verify PowerCenter Repository Database UserVerify the repository database user information for each PowerCenter Integration Service. When you upgradeusers, you can change user information or associate LDAP users with a security domain. Verify that the repositoryuser information specified for the associated repository of the PowerCenter Integration Service is still valid.

Complete one of the following tasks for the repository user based on the repository user type and upgrade method:

User Type Upgrade Method Task Description

LDAP User Upgraded Specify the security domain for therepository user.

LDAP User Skipped Specify a new repository user for theassociated repository.

Repository User Merged Update the repository user name andpassword.

Repository User Renamed Update the repository user name.

To apply changes, restart the PowerCenter Integration Service.

58 Chapter 7: After You Upgrade

Web Services HubAfter you upgrade, complete the post-upgrade tasks for the Web Services Hub:

Associate Linked DomainsIf you used a linked domain repository in the previous installation, specify a repository that exists in the domain forthe associated repository of the Web Service Hub.

You cannot associate the Web Service Hub in the local domain with a PowerCenter Repository Service in anotherdomain. When you upgrade a domain, the Web Services Hub loses the linked domain repository association.

To apply changes, restart the Web Services Hub Service.

Verify PowerCenter Repository Database UserVerify the repository database user information for each Web Services Hub Service. When you upgrade users, youcan change user information or associate LDAP users with a security domain. Verify that the repository userinformation specified for the associated repository of the Web Services Hub Service is still valid.

Complete one of the following tasks for the repository user based on the repository user type and upgrade method:

User Type Upgrade Method Task Description

LDAP User Upgraded Specify the security domain for therepository user.

LDAP User Skipped Specify a new repository user for theassociated repository.

Repository User Merged Update the repository user name andpassword.

Repository User Renamed Update the repository user name.

To apply changes, restart the Web Service Hub Service.

Grant PermissionsGrant the necessary permissions to the folders in the Informatica installation directory.

PowerCenterGrant the Execute permission on the following folders in the <InformaticaInstallationDir>/tools/pcutilsdirectory:

¨ 8.6.1

¨ 9.0.1

¨ 9.1.0

Web Services Hub 59

If the folders do not have the Execute permission, you cannot export mapping specifications from the Analyst toolto PowerCenter.

Export Consolidation Transformation Objects toPowerCenter

Data Quality and PowerCenter version 9.1.0 updated the binary files associated with the Consolidationtransformation. A Consolidation transformation that you exported from an earlier version of Data Quality cannotwork in a current version of PowerCenter.

If a PowerCenter 9.1.0 repository contains a mapping that includes a Consolidation transformation, export themapping to PowerCenter again after you upgrade Data Quality.

You do not need to update a Consolidation transformation in an upgraded Model repository.

60 Chapter 7: After You Upgrade

A P P E N D I X A

Upgrade ChecklistThis appendix includes the following topics:

¨ Upgrade Checklist Overview, 61

¨ Before You Upgrade the Domain and Server Files, 61

¨ Domain and Server Files Upgrade, 62

¨ Before You Upgrade the Application Services, 62

¨ Application Service Upgrade, 63

¨ Informatica Client Upgrade, 63

¨ After You Upgrade, 63

Upgrade Checklist OverviewThe upgrade checklist summarizes the tasks that you must perform to complete an upgrade. If you upgrade theInformatica product on more than one machine, complete the first upgrade using the detailed instructions in thisguide. You can use this checklist to perform subsequent upgrades.

Before You Upgrade the Domain and Server FilesBefore you upgrade the domain and server files, complete the following pre-upgrade tasks:

1. Review the operating system specific requirements.Review the prerequisites and environment variable configuration.

2. Uninstall Informatica B2B Data Transformation.

3. Prepare the domain.Back up the domain and verify database requirements.

4. Prepare the PowerCenter repository.Back up the PowerCenter repository.

If the domain uses LDAP authentication, make a list of users with each of the following PowerCenter 8.1.1repository privileges: Admin Integration Service, Prepare the PowerCenter Repository, Admin Repository, andSuper User.

5. Prepare the PowerCenter Profiling warehouse.Back up the PowerCenter Profiling warehouse.

61

6. Shut down the domain.You must shut down the domain before you upgrade it. To shut down the domain, stop the Informatica serviceprocess on each node in the domain.

7. Prepare to change the node configuration.Complete the additional pre-upgrade tasks if you choose to change the node configuration.

a. Review the operating system specific requirements.

b. Copy the installation directory.

c. Verify the keystore file name and location.

RELATED TOPICS:¨ “Before You Upgrade the Domain and Server Files” on page 4

Domain and Server Files UpgradeUse the server installer to upgrade the domain and server files. The server installer provides a domain upgradewizard to guide you through the upgrade process.

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

RELATED TOPICS:¨ “Domain and Server Files Upgrade” on page 22

Before You Upgrade the Application ServicesBefore you upgrade application services, complete the following pre-upgrade tasks:

1. Configure POSIX Asynchronous I/O.If you install Informatica on IBM AIX, make POSIX Asynchronous I/O available on any node where you wantto run a PowerCenter Integration Service.

2. Configure Informatica environment variables.

3. Configure locale environment variables.Verify that the locale setting is compatible with the code page for the repository.

4. Clear browser cache.

5. Prepare to upgrade LDAP users and groups.If the PowerCenter Repository Service uses LDAP authentication, complete the LDAP configuration steps.

6. If you chose the option to update the node configuration, complete the following steps:

a. Install the database client software.

b. Configure the environment variables.

c. Verify that a graphics display server is available.

d. Copy the required files.

62 Appendix A: Upgrade Checklist

e. Update port numbers.

f. Verify the location of the node backup directory.

g. Update the keystore file name and location.

h. Configure PowerExchange Adapters.

RELATED TOPICS:¨ “Before You Upgrade the Application Services” on page 40

Application Service UpgradeSome service versions require a service upgrade. You can use the service upgrade wizard to upgrade services.

To upgrade application services for PowerCenter 8.1.x, complete the following upgrade tasks:

1. Before you upgrade a PowerCenter repository that uses LDAP authentication, run the infacmd ispSetRepositoryLDAPConfiguration command to update LDAP configuration properties.

2. Upgrade each PowerCenter Repository Service.

3. Upgrade the users and groups of each PowerCenter Repository Service.

RELATED TOPICS:¨ “Application Service Upgrade” on page 48

Informatica Client UpgradeUse the client installer to upgrade the client tools. The client tools are installed in the installation directory youspecify. The client installer configures the newly installed client tools with the same settings as the previousversion.

RELATED TOPICS:¨ “Informatica Client Upgrade” on page 52

After You UpgradeAfter you upgrade the domain, server files, application services, and client files, complete the following post-upgrade tasks:

1. Configure LDAP connectivity.The default maximum size for user import is set to 1000. Increase the value if you have more than 1000 users.

2. Verify that the log events directory is correct.To use a different directory for the logs, update the Log Directory Path property for the domain.

3. Update ODBC data sources.

Application Service Upgrade 63

The Informatica installation includes DataDirect 6.0 SP3 ODBC drivers. Re-create each ODBC data source touse the new drivers.

4. Update statistics for the domain configuration repository.If the domain configuration repository is in an IBM DB2 9.1 database, run the DB2 reorgchk command tooptimize database operations.

5. View log events from previous Informatica installations to troubleshoot domain issues.

6. After you upgrade the PowerCenter Repository Service, the service remains in Exclusive mode. Change theoperating mode of each PowerCenter Repository Service to Normal mode and restart the service.

7. If the domain uses LDAP authentication, referring to the list of users with PowerCenter 8.1.1 repositoryprivileges you wrote down before you performed the domain and server upgrade, reassign privileges to users.

8. Complete the following post-upgrade tasks for each PowerCenter Integration Service:

a. Associate linked domains.

b. If the PowerCenter Integration Service has the same name as the domain, re-create the PowerCenterIntegration Service.

c. Verify that the repository user information specified for the associated repository of the PowerCenterIntegration Service is still valid.

9. Complete the following post-upgrade tasks for each Web Services Hub Service:

a. Associate linked domains.

b. Verify that the repository user information specified for the associated repository of the Web ServicesHub Service is still valid.

10. Grant the necessary permissions to the folders in the Informatica installation directory.

RELATED TOPICS:¨ “After You Upgrade” on page 56

64 Appendix A: Upgrade Checklist

I N D E X

AAIX

configuring JRE path 46configuring X Virtual Frame Buffer (Xvfb) 46Java components 46LIBPATH 46

CConsolidation transformation object upgrade 60

Ddatabase client

configuring 44environment variables 44

databasestesting connections 44

dbs2 connecttesting database connection 44

disk space requirementsinstallation requirements 8

DISPLAYenvironment variables 6

Domain Activity Reportingsetting up on UNIX 46

Eenvironment variables

database client 44DISPLAY 9installation 6, 8Java components 46library path 44UNIX database client 44

Ggraphical mode

installation requirements 9

HHP-UX

configuring JRE path 46configuring X Virtual Frame Buffer (Xvfb) 46Java components 46SHLIB_PATH 46

IIATEMPDIR

environment variables 6, 8installation requirements

disk space 8environment variables 6, 8X Window Server 9

Integration Servicedatabase client 43

isqltesting database connection 44

JJava components

AIX 46HP-UX 46

Java transformationconfiguring JRE path 46

JRE_HOMEenvironment variables 6, 8

LLANG

locale environment variables 6, 8LC_ALL

locale environment variables 6, 8LIBPATH

AIX 46library path

environment variables 8Linux

configuring X Virtual Frame Buffer (Xvfb) 46database client environment variables 44library paths 44

PPATH

environment variables 8PowerExchange for JMS

configuring JRE path 46PowerExchange for Web Services

configuring JRE path 46PowerExchange for webMethods

configuring JRE path 46

65

RRepository Service

database client 44

SService Upgrade Wizard

upgrading services 49, 50upgrading users 49, 50

servicesService Upgrade Wizard 49, 50

SHLIB_PATHHP-UX 46

Solarisconfiguring X Virtual Frame Buffer (Xvfb) 46

sqlplustesting database connection 44

Uuninstalling

before upgrade or migration 11

UNIXdatabase client environment variables 44database client variables 44library paths 44user account 21

upgradingConsolidation transformation objects 60Service Upgrade Wizard 49, 50

user accountUNIX 21

XX Virtual Frame Buffer (Xvfb)

installing on UNIX 46X Window Server

installation requirements 9

66 Index

Date post:	21-Aug-2020
Category:	Documents
Upload:	others
View:	13 times
Download:	0 times