DQ 951 Upgrade950 En

Informatica Data Quality (Version 9.5.1)

Upgrade Guide for Version 9.5.0

Informatica Data Quality Upgrade Guide for Version 9.5.0

Version 9.5.1December 2012

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

This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use anddisclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form,by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or internationalPatents and other Patents Pending.

Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided inDFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013©(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.

The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us inwriting.

Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange,PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange 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. Copyright © is International Business Machines Corporation. All rights reserved. Copyright © yWorks GmbH. All rights reserved. Copyright ©Lucent Technologies. All rights reserved. Copyright (c) University of Toronto. All rights reserved. Copyright © Daniel Veillard. All rights reserved. Copyright © Unicode, Inc.Copyright IBM Corp. All rights reserved. Copyright © MicroQuill Software Publishing, Inc. All rights reserved. Copyright © PassMark Software Pty Ltd. All rights reserved.Copyright © LogiXML, Inc. All rights reserved. Copyright © 2003-2010 Lorenzi Davide, All rights reserved. Copyright © Red Hat, Inc. All rights reserved. Copyright © The Boardof Trustees of the Leland Stanford Junior University. All rights reserved. Copyright © EMC Corporation. All rights reserved. Copyright © Flexera Software. 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://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, http://www.slf4j.org/license.html; http://www.iodbc.org/dataspace/iodbc/wiki/iODBC/License; http://www.keplerproject.org/md5/license.html; http://www.toedter.com/en/jcalendar/license.html; http://www.edankert.com/bounce/index.html; http://www.net-snmp.org/about/license.html; http://www.openmdx.org/#FAQ; http://www.php.net/license/3_01.txt; http://srp.stanford.edu/license.txt; http://www.schneier.com/blowfish.html;http://www.jmock.org/license.html; http://xsom.java.net; and http://benalman.com/about/license/.

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 product includes software developed by Andrew Kachites McCallum. "MALLET: A Machine Learning for Language Toolkit." http://mallet.cs.umass.edu (2002).

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,243,110, 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422;7676516; 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-95100-0001

Table of Contents

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

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

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

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

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

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

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

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

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

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

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

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

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

Review the Windows Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Review the Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Review the Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Review the Maximum Heap Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Review the UNIX Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Install Java Development Kit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Review the Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Review the Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Set the File Descriptor Limit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Review the Maximum Heap Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Set Up the X Window Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Uninstall Data Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Backing Up Essential Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Uninstalling Previous Versions of Data Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Prepare the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Back Up the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Verify Database User Account Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Prepare the Model Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Back Up the Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Verify the Database User Account Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Table of Contents i

Verify the Maximum Heap Size Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Prepare the Profiling Warehouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Back Up the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Verify Database User Account Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Prepare the Staging Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Shut Down the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Prepare to Change the Node Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Configure the Windows Machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Configure the UNIX Machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Copy the Installation Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Verify Keystore File Name and Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

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

Upgrading in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

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

Upgrading in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Creating the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

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

Upgrading in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Upgrading in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Upgrading in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Troubleshooting the Domain Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

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

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

Configure Locale Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Clear Browser Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Change the Node Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Install the Database Client Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Configure Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

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

Update Port Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Verify the Node Backup Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Update Keystore File Name and Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Configure PowerExchange Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

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

Service Upgrade for Data Quality 9.5.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Service Upgrade Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

ii Table of Contents

Upgrade Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Running the Service Upgrade Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Informatica Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

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

Update the Log Events Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

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

Data Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Update the Profiling Warehouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Reset the HTTP Proxy Server Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Analyst Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Verify Directories and Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Restart the Analyst Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Assign Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Content Management Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Data Director Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Informatica Analyst. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Scorecards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Upgrade the Informatica Drivers for SQL Data Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Merge the Address Doctor Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Appendix A: Upgrade Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Upgrade Checklist Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

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

Domain and Server Files Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Before You Upgrade the Application Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Application Service Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Informatica Client Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

After You Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Table of Contents iii

PrefaceThe Upgrade Guide for Version 9.5.0 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.

iv

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

Preface v






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 UpgradeThe Informatica platform consists of a server component and one or more client components. Informatica providesseparate installers to upgrade the Informatica services and clients.

If the product version that is currently installed cannot be upgraded to Informatica 9.5.1, you must first upgrade toa supported version. To determine the Informatica product version that is currently installed, click Help > AboutInformatica Administrator in the Informatica Administrator header area.

You can upgrade the following Informatica product versions to version 9.5.1:

Informatica Product Version Comments

PowerCenter 8.1.x You must first upgrade to PowerCenter 8.6.1.

PowerCenter 8.5.x You must first upgrade to PowerCenter 8.6.1.

PowerCenter 8.6 You must first upgrade to PowerCenter 8.6.1.

PowerCenter 8.6.1 If the PowerCenter 8.6.1 domain includes the Metadata ManagerService, you must first upgrade to Informatica 9.1.0.If the PowerCenter 8.6.1 domain does not include the MetadataManager Service, upgrade to Informatica 9.5.1. Effective in version 9.0.1, the Reference Table Manager functionality is available throughthe 9.0.1 Analyst Service. When you upgrade, you will perform thesteps to migrate the PowerCenter 8.6.1 reference table data to theInformatica 9.5.1 Analyst tool.

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

Data Explorer Advanced Edition 9.0 You must first upgrade to Informatica Data Explorer AdvancedEdition 9.0.1. See the Informatica Data Quality 9.0.1 upgradedocumentation. Complete the steps to upgrade Informatica DataQuality 9.0.1 unless an exception is specified.

1

Informatica Product Version Comments

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

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

Data Transformation 9.0.1 or earlier versions You must uninstall Data Transformation and then install InformaticaData Transformation 9.5.1. See the Data Transformation 9.5.1installation and upgrade documentation.

PowerCenter 9.0 If the PowerCenter 9.0 domain includes the Metadata ManagerService, you must first upgrade to Informatica 9.1.0.If the PowerCenter 8.6.1 domain does not include the MetadataManager Service, 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 If the PowerCenter 9.0.1 domain includes the Metadata ManagerService, you must first upgrade to Informatica 9.1.0.

Informatica Data Explorer 9.1.0



Informatica Data Transformation 9.1.0

Informatica PowerCenter 9.1.0

Informatica Data Explorer 9.5.0



Informatica Data Transformation 9.5.0

Informatica PowerCenter 9.5.0

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.

2 Chapter 1: Upgrade Overview

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.5.1 applicationservices.The upgrade retains the user and administrator accounts inthe domain.

Starts Informatica Services. Starts Informatica Services on the node.

¨ Upgrading the application services. After you upgrade the domain and server files, log in to the Administratortool and upgrade the application services. The service upgrade wizard provides a list of all application 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.

Upgrade TasksTo upgrade Data Quality, 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.

Upgrade Tasks 3

Note: When you upgrade the application services that Data Quality uses, you can optionally create a DataDirector Service and Reporting and Dashboards Service. The Data Director Service runs the Informatica DataDirector for Data Quality web application in an Informatica domain. The Reporting and Dashboards Serviceruns the JasperReports application in an Informatica domain.

5. Create a Content Management Service. The Content Management Service manages reference data, addressvalidation options, and probabilistic models. The service provides reference data, address validation port lists,identity population information and probabilistic model information to the client applications.

6. Upgrade Informatica Developer. Use the client installer to upgrade Informatica Developer. UpgradingInformatica Developer also installs or upgrades Data Transformation Studio. If you have Data Transformation9.1.0 installed, upgrading Informatica Developer also upgrades Data Transformation Studio. If you do nothave Data Transformation installed, upgrading Informatica Developer installs Data Transformation Studio.

Note: You cannot connect to the Informatica domain using the Developer tool from a previous version.

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

4 Chapter 1: Upgrade Overview

C H A P T E R 2

Before You Upgrade the Domainand Server Files

This chapter includes the following topics:

¨ Pre-Upgrade Tasks, 5

¨ Review the Windows Requirements, 6

¨ Review the UNIX Requirements, 8

¨ Uninstall Data Transformation, 12

¨ Prepare the Domain, 14

¨ Prepare the Model Repository, 15

¨ Prepare the Profiling Warehouse, 16

¨ Prepare the Staging Database, 16

¨ Shut Down the Domain, 17

¨ Prepare to Change the Node Configuration, 17

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

1. Review the operating system specific requirements.

2. Uninstall Data Transformation.

3. Prepare the domain.

4. Prepare the Model repository.

5. Prepare the profiling warehouse.

6. Prepare the staging database.

7. Shut down the domain.

8. Prepare to change the node configuration.

5

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

1. Review the prerequisites.

2. Review the environment variables.

3. Review the maximum heap size.

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 8 GB 20 GB

Domain with Data Quality and Data Servicesapplication services running on one node:- Data Integration Service- Model Repository Service- Analyst Service- Content Management Service- Data Director Service

4 CPU 8 GB 20 GB

The installer requires an additional 10 MB disk space for each domain and each instance of the following servicetypes:

¨ Model Repository Service

¨ Data Integration Service

¨ Analyst Service

¨ Content Management Service

¨ Data Director Service

For example, if you have one domain with five Model Repository Services and three Data Integration Servicesrunning on one node, add 90 MB of disk space to the minimum requirement.

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 Informatica Developer:

Client Processor RAM Disk Space

Informatica Developer 1 CPU 512 MB 2.5 GB

Data Transformation Studio 1 CPU 512 MB 708 MB

For more information about product requirements and supported platforms, see the Product Availability Matrix onthe Informatica Customer Portal: https://communities.informatica.com/community/my-support/tools/product-availability-matrices

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

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

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

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

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 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. Install the Java Development Kit.

2. Review the prerequisites.

3. Review the environment variables.

4. Verify the file descriptor settings.

5. Review the maximum heap size.

6. Set up the X Windows server.


Install Java Development KitIf you are upgrading Informatica on AIX, HP-UX, or zLinux, verify that the Informatica version you are upgrading tosupports the version of Java Development Kit (JDK) that is installed on your machine. If you do not have asupported version of JDK installed, uninstall the current version, and then download and install the supportedversion.

¨ For AIX: http://www.ibm.com/developerworks/java/jdk/aix/service.html#java6

¨ For HP-UX: https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=HPUXJDKJRE60

¨ For zLinux: http://www.ibm.com/developerworks/java/jdk/linux/download.html#java6

Informatica is certified with a specific JDK version. To determine which JDK version to install, see the InformaticaRelease Notes. If you have problems installing JDK, contact the JDK vendor.

The software available for download at the referenced links belongs to a third party or third parties, not InformaticaCorporation. The download links are subject to the possibility of errors, omissions or change. Informatica assumesno responsibility for such links and/or such software, disclaims all warranties, either express or implied, includingbut not limited to, implied warranties of merchantability, fitness for a particular purpose, title and non-infringement,and disclaims all liability relating thereto.

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 8 GB 20 GB

Domain with Data Quality and Data Servicesapplication services running on one node:- Data Integration Service- Model Repository Service- Analyst Service- Content Management Service- Data Director Service

4 CPU 8 GB 20 GB

The installer requires an additional 10 MB disk space for each domain and each instance of the following servicetypes:

¨ Model Repository Service

¨ Data Integration Service

¨ Analyst Service

¨ Content Management Service

¨ Data Director Service

For example, if you have one domain with five Model Repository Services and three Data Integration Servicesrunning on one node, add 90 MB of disk space to the minimum requirement.

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 product requirements and supported platforms, see the Product Availability Matrix onthe Informatica Customer Portal: https://communities.informatica.com/community/my-support/tools/product-availability-matrices

Review the UNIX Requirements 9

http://www.ibm.com/developerworks/java/jdk/aix/service.html#java6

https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=HPUXJDKJRE60

http://www.ibm.com/developerworks/java/jdk/linux/download.html#java6



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

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

Set the environment variables before you install Informatica. The following table describes the environmentvariables to review on UNIX:


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.

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

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

INFA_JDK_HOME Location of the folder containing the supported Java Development Kit (JDK). Set theINFA_JDK_HOME environment variable if you are installing Informatica on AIX, HP-UX, or zLinux.In the configuration file for your shell, for example the .bashrc file, set theINFA_JDK_HOME environment variable to the directory that contains the JDK. Verifythat the login shell can access the INFA_JDK_HOME environment variable.

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.

LANG and LC_ALL Change the locale to set the appropriate character encoding for the terminal session.For example, set the encoding to Latin1 or ISO-8859-1 for French, EUC-JP or ShiftJIS for Japanese, or UTF-8 for Chinese or Korean. The character encodingdetermines the types of characters that appear in the UNIX terminal.

LD_PRELOAD On HP-UX, the environment variable selects the Data Transformation libjvm sharedobject of the JRE.Unset the LD_PRELOAD environment variable, if you are upgrading Informatica onHP-UX.



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

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

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

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.

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 Data Transformation 9.0.1 or earlier versions, you must uninstall it before you install theInformatica services or clients. The Informatica installation overwrites the Data Transformation configuration file.Before you upgrade the Informatica services or clients, back up the essential Data Transformation files anduninstall 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(Data Transformationclient only)

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


Directory Default Location

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

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 Versions of Data TransformationThe installer cannot upgrade Data Transformation directly from 9.0.1 or previous versions.

If you have Data Transformation 9.0.1 or previous versions installed, you must uninstall it before you install thecurrent version.

1. Close all applications that use Data Transformation services.

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

3. To run the uninstaller, perform one of the following actions:

Operating System Action

Windows XP/2008/Vista In the Windows Control Panel, select Add or Remove Programs, and then select the optionto remove Data Transformation.

Windows 7 In the Windows Control Panel, select Programs and Features, and then select the option toremove Data Transformation.

The Uninstallation window appears.

4. Click Uninstall.

The system prompts you to shut down all services.

5. Click Continue.

Uninstall Data Transformation 13

Data Transformation files are removed from the computer, essential customer customized files are backed upin the <INSTALL_DIR>/DataTransformation_<VERSION>_Backup directory, and the system displays the followingmessage:Uninstallation completed.Note: There is no log file containing the details of the uninstall operation.

6. Click Done.

7. When the uninstallation is complete, move the <INSTALL_DIR>/DataTransformation_<VERSION>_Backup directory,and then delete the installation directory and all files remaining in it.

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

1. Back up the domain.

2. Verify the domain configuration repository requirements.

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 isp/config directoryon each node in the domain.If you use the same backupdirectory name on all the nodes,rename nodemeta.xml beforecopying it to the backup location.For example, you back upnodemeta.xml to the /nodebakdirectory on nodeA and nodeB.Rename the configuration files sothat on nodeA the file is backedup to /nodebak/nodemeta_A.xml,and on nodeB the file is backedup to /nodebak/nodemeta_B.xml.

domains.infa Contains connectivity information for the gatewaynodes.

Stored in one of the followinglocations:- The Informatica installation

directory on the client andserver machines.

- The location configuredthrough theINFA_DOMAINS_FILEenvironment variable.

Verify Database User Account RequirementsIf the domain configuration repository database is on Oracle, set the OPEN_CURSORS parameter to 4000 orhigher.

If the domain configuration repository database is on IBM DB2, set the DynamicSections parameter to 3000 orhigher.

Prepare the Model RepositoryBefore you upgrade the domain, complete the steps to prepare the Model repository.

1. Back up the repository.

2. Verify the database user account requirements.

3. Verify the maximum heap size.

Back Up the RepositoryBefore you upgrade the domain, back up the Model repository.

To back up each Model repository, select the Model Repository Service in the Administrator tool. Then, on theDomain Actions menu, click Repository Contents > Backup.

Prepare the Model Repository 15

Verify the Database User Account RequirementsIf the Model repository database is on Oracle, set the OPEN_CURSORS parameter to 4000 or higher.

If the Model repository database is on IBM DB2, set the DynamicSections parameter to 3000 or higher.

Verify the Maximum Heap Size SettingIf the Model repository is large, increase the maximum heap size.

For example, if the Model repository is 3 GB, increase the maximum heap size to 2048 MB.

To increase the maximum heap size, select the Model Repository Service in the Administrator tool, select theProperties view, click Edit in the Advanced Properties section, and then edit the Maximum Heap Size property.

Prepare the Profiling WarehouseBefore you upgrade the domain, prepare the profiling warehouse.

1. Back up the database.

2. Verify database user account permissions.

Back Up the DatabaseBefore you upgrade the domain, back up the profiling warehouse.

Use the native database back up option to back up the profiling warehouse.

Verify Database User Account PermissionsThe profiling warehouse user account for an IBM DB2 or Microsoft SQL Server database requires the CreateFunction privilege.

To grant the Create Function privilege for an IBM DB2 database, you can use the following syntax:

grant dbadm, createtab, bindadd, connect, implicit_schema, load on database to <DATABASEUSER>

To grant the Create Function privilege for a Microsoft SQL Server database, you can use the following syntax:

USE <DatabaseName>;GRANT CREATE FUNCTION TO <DatabaseUser>;GO

Prepare the Staging DatabaseBefore you upgrade the domain, back up the staging database.

Use the native database back up option to back up the staging 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.

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

Shut Down the Domain 17

The following table describes the ports used by Informatica:

Port Type Description

Domain port Port number for the node created during installation. Default is 6005.

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.

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

Informatica Administrator port Port number used by Informatica Administrator. Default is 6008.

Informatica Administratorshutdown port

Port number that controls server shutdown for Informatica Administrator. InformaticaAdministrator listens 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:

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.


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

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


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\9.0.1, copy theC:\Informatica\9.0.1 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.

Prepare to Change the Node Configuration 19

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>/tomcat/conf. The default file name for thekeystore file is Default.keystore.

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


C H A P T E R 3

Domain and Server Files UpgradeThis chapter includes the following topics:

¨ Domain and Server Files Upgrade Overview, 21

¨ Upgrading in Graphical Mode, 22

¨ Upgrading in Console Mode, 26

¨ Upgrading in Silent Mode, 29

¨ Upgrading with Changes to the Node Configuration, 31

¨ Troubleshooting the Domain Upgrade, 43

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

The upgrade wizard installs Informatica 9.5.1 in the installation directory you specify. It does not modify the files inthe 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.5.1. It upgrades the tables of the domain configurationrepository in the same database as the previous version.

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

You can perform the upgrade from a DVD or from the root of the directory where you download the installationfiles.

On Windows, the length of the entire installation directory path, including the zip file name, must be 60 charactersor less. Verify that the zip utility version is compatible with the Windows operating system version. When you unzipthe file, verify that the zip utility also extracts empty folders.

On UNIX, use native tar or GNU tar to extract the installer files. The user that runs the installer must have readand write permissions on the installer files directory and execute permissions on install.sh.

21

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

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.

5. Select Run the Pre-Installation (i9Pi) System Check Tool to verify whether the machine meets the systemrequirements for the upgrade.

6. Click Start.

7. If you selected Run the Pre-Installation (i9Pi) System Check Tool, complete the following steps:

a. From the Informatica Pre-Installation (i9Pi) System Check Tool Welcome page, click Next.

The System Information page appears.

b. Enter the absolute path for the installation directory. The default directory is C:\.

The directory names in the path must not contain spaces or the following special characters: @ | * $ # !% ( ) { } [ ] , ; 'On Windows, the installation directory path must be on the machine where you are installing Informatica.

c. Enter the starting port number for the node that is being created on the machine. The default port numberfor the node is 6005.

d. Click Next.

The Database and JDBC Connection Information page appears.

e. Enter the domain configuration repository database information:

Prompt Description

Database type Type of database for the domain configuration repository. Select from the followingoptions:1 - Oracle2 - Microsoft SQL Server3 - IBM DB2

22 Chapter 3: Domain and Server Files Upgrade

Prompt Description

4 - Sybase ASE

Database user ID Name for the domain configuration database user account.

Database user password Password for the domain configuration database user account.

The domain configuration repository must be accessible to all gateway nodes in the domain.

f. Enter the JDBC connection information.

¨ To enter the connection information using the JDBC URL information, select Specify the JDBCconnection properties and specify the JDBC URL properties.

Property Description

Database host name Host name for the database.

Database port number Port number for the database.

Database service name Service name for Oracle and IBM DB2 databases or database name forMicrosoft SQL Server and Sybase ASE.

¨ To enter the connection information using a custom JDBC connection string, select Custom JDBCconnection string and type the connection string.IBM DB2: jdbc:Informatica:db2://host_name:port_no;DatabaseName=Oracle: jdbc:Informatica:oracle://host_name:port_no;ServiceName=SQL Server: jdbc:Informatica:sqlserver://host_name:port_no;SelectMethod=cursor;DatabaseName=Sybase: jdbc:Informatica:sybase://host_name:port_no;DatabaseName=Verify that the connection string contains all the connection parameters required by your databasesystem.

g. Click Test Connection to verify that you can connect to the database.

h. Click Next to start the system check.

The tool checks the settings of the hard drive, the availability of the ports, and the configuration of thedatabase. After the system check is complete, the System Check Summary page appears, displayingthe results of the system check.

i. Analyze the results of the system check.

Each requirement is listed, along with one of the following check statuses:

¨ [Pass] - The requirement meets the criteria for the Informatica installation or upgrade.

¨ [Fail] - The requirement does not meet the criteria for the Informatica installation or upgrade. Resolvethe issue before proceeding with the installation or upgrade.

¨ [Information] - Verify the information and perform any additional tasks as outlined in the details.

The results of the system check are saved to the following file: \Server\I9PI\I9PI\en\i9Pi_summary.html.

j. Click Done to close the Pre-Installation (i9Pi) System Check Tool.

The Installation Type page appears.

Upgrading in Graphical Mode 23

k. If the Pre-Installation (i9Pi) System Check Tool finishes with failed requirements, click Cancel to quit theinstallation or upgrade. Resolve the failed requirements, and run the installation or upgrade again.

Note: If the Informatica Pre-Installation (i9Pi) System Check Tool check finishes with failed requirements,you can still perform the Informatica installation or upgrade. However, it is highly recommended that youresolve the failed requirements before proceeding.

8. If the Pre-Installation (i9Pi) System Check Tool finished with failed requirements, click Cancel to quit theupgrade. Resolve the failed requirements, and run the upgrade again.

If the Pre-Installation (i9Pi) System Check Tool finished and all of the requirements meet the criteria for theInformatica upgrade, select Upgrade to Informatica 9.5.1 to proceed with the upgrade.

9. Click Next.

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

10. Verify the requirements before you continue the upgrade.

11. Click Next.

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

Directory Description

Directory of the Informaticaproduct to upgrade

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

Directory for Informatica 9.5.1 Directory in which to install Informatica 9.5.1.Enter the absolute path for the installation directory. The directory cannot be the sameas the directory that contains the previous version of Data Quality.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.

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

14. Click Next.

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

15. Click OK.

16. 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.5.1 installation directory.

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


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.

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

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

You cannot specify additional JDBC parameters.

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

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.

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

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

You cannot specify additional JDBC parameters.

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

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

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

Upgrading in Graphical Mode 25


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.

22. Click Next.

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

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


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.

6. Enter y to run the Pre-Installation (i9Pi) System Check Tool to verify whether the machine meets the systemrequirements for the installation or upgrade.

7. Enter C for console mode installation.

8. If you entered y to run the Pre-Installation (i9Pi) System Check Tool, complete the following steps:

a. From the Informatica Pre-Installation (i9Pi) System Check Tool Welcome section, press Enter.

The System Information section appears.

b. Type the absolute path for the installation directory.

The directory names in the path must not contain spaces or the following special characters: @|* $ # ! %( ) { } [ ] , ; ' Default is /home/toolinst.

c. Press Enter.


d. Type the starting port number for the node that is being created or upgrade on the machine. Default is6005.

e. Press Enter.

f. To enter the JDBC connection information using a custom JDBC connection string, press 1. To enter theJDBC connection information using the JDBC URL information, press 2.

g. Enter the JDBC connection information.

¨ To enter the connection information using a custom JDBC connection string, type the connectionstring.IBM DB2: jdbc:Informatica:db2://host_name:port_no;DatabaseName=Oracle: jdbc:Informatica:oracle://host_name:port_no;ServiceName=SQL Server: jdbc:Informatica:sqlserver://host_name:port_no;SelectMethod=cursor;DatabaseName=Sybase: jdbc:Informatica:sybase://host_name:port_no;DatabaseName=Verify that the connection string contains all the connection parameters required by your databasesystem.

¨ To enter the connection information using the JDBC URL information, specify the JDBC URLproperties.

Prompt Description

Database type Type of database for the domain configuration repository. Select from the followingoptions:1 - Oracle2 - Microsoft SQL Server3 - IBM DB24 - Sybase ASE





Database service name Password for the domain configuration database user account.Service name for Oracle and IBM DB2 databases or database name for MicrosoftSQL Server and Sybase ASE.

The tool checks the settings of the hard drive, the availability of the ports, and the configuration of thedatabase. After the system check is complete, the System Check Summary section appears, displayingthe results of the system check.

h. Analyze the results of the system check.

Each requirement is listed in the table, along with one of the following check statuses:


Upgrading in Console Mode 27

¨ [Fail] - The requirement does not meet the criteria for the Informatica installation or upgrade. Resolvethe issue before proceeding.


The results of the system check are saved to the following file: /Server/I9PI/I9PI/en/i9Pi_summary.txt.

i. Press Enter to close the Pre-Installation (i9Pi) System Check Tool.

j. If the Pre-Installation (i9Pi) System Check Tool finishes with failed requirements, press n to quit theinstallation or upgrade. Resolve the failed requirements, and run the installation or upgrade again.



If the Pre-Installation (i9Pi) System Check Tool finished and all of the requirements meet the criteria for theInformatica upgrade, enter 2 to proceed with the upgrade.


11. Press Enter.

12. At the prompt, enter the following directories:




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

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

14. Press Enter.

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

The installer copies the server files to the Informatica 9.5.1 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.

16. Press Enter.

17. If you use a JDBC URL, you can specify additional parameters to include in the connection string.

If you use a custom connection string, you cannot specify additional parameters.

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 Data Quality. The directory cannot bethe same as the directory that contains the previous version of Data Quality.

UPG_BACKUP_DIR Directory that contains the previous version of Data Quality 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-

Upgrading in Silent Mode 29


partition database, the tablespace page size must be 32 K. Define the database in asingle-node tablespace to optimize performance.Set this parameter only if you are upgrading from PowerCenter 8.x.

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.Set this parameter only if you are upgrading from PowerCenter 8.x.

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.Set this parameter only if you are upgrading from PowerCenter 8.x.

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.Set this parameter only if you are upgrading from PowerCenter 8.x.

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.Set this parameter only if you are upgrading from PowerCenter 8.x.

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.

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

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.

Upgrading with Changes to the Node Configuration 31

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.

5. Select Run the Pre-Installation (i9Pi) System Check Tool to verify whether the machine meets the systemrequirements for the installation or upgrade.

6. Click Start.

7. If you selected Run the Pre-Installation (i9Pi) System Check Tool, complete the following steps:

a. From the Informatica Pre-Installation (i9Pi) System Check Tool Welcome page, click Next.

The System Information page appears.

b. Enter the absolute path for the installation directory. The default directory is C:\.

The directory names in the path must not contain spaces or the following special characters: @ | * $ # !% ( ) { } [ ] , ; 'On Windows, the installation directory path must be on the machine where you are installing Informatica.

c. Enter the starting port number for the node that is being created on the machine. The default port numberfor the node is 6005.

d. Click Next.

The Database and JDBC Connection Information page appears.

e. Enter the domain configuration repository database information:

Prompt Description




The domain configuration repository must be accessible to all gateway nodes in the domain.


f. Enter the JDBC connection information.

¨ To enter the connection information using the JDBC URL information, select Specify the JDBCconnection properties and specify the JDBC URL properties.




Database service name Service name for Oracle and IBM DB2 databases or database name forMicrosoft SQL Server and Sybase ASE.

¨ To enter the connection information using a custom JDBC connection string, select Custom JDBCconnection string and type the connection string.IBM DB2: jdbc:Informatica:db2://host_name:port_no;DatabaseName=Oracle: jdbc:Informatica:oracle://host_name:port_no;ServiceName=SQL Server: jdbc:Informatica:sqlserver://host_name:port_no;SelectMethod=cursor;DatabaseName=Sybase: jdbc:Informatica:sybase://host_name:port_no;DatabaseName=Verify that the connection string contains all the connection parameters required by your databasesystem.

g. Click Test Connection to verify that you can connect to the database.

h. Click Next to start the system check.

The tool checks the settings of the hard drive, the availability of the ports, and the configuration of thedatabase. After the system check is complete, the System Check Summary page appears, displayingthe results of the system check.

i. Analyze the results of the system check.

Each requirement is listed, along with one of the following check statuses:


¨ [Fail] - The requirement does not meet the criteria for the Informatica installation or upgrade. Resolvethe issue before proceeding with the installation or upgrade.


The results of the system check are saved to the following file: \Server\I9PI\I9PI\en\i9Pi_summary.html.

j. Click Done to close the Pre-Installation (i9Pi) System Check Tool.

The Installation Type page appears.

k. If the Pre-Installation (i9Pi) System Check Tool finishes with failed requirements, click Cancel to quit theinstallation or upgrade. Resolve the failed requirements, and run the installation or upgrade again.



If the Pre-Installation (i9Pi) System Check Tool finished and all of the requirements meet the criteria for theInformatica upgrade, select Upgrade to Informatica 9.5.1 to proceed with the upgrade.

9. Click Next.


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


11. Click Next.

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




Directory for Informatica 9.5.1 Directory in which to install Informatica 9.5.1.Enter the absolute path for the installation directory. The directory cannot be the sameas the directory that contains the previous version of Data Quality.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.

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

14. Click Next.

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

15. Click OK.

16. 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.5.1 installation directory.

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

18. Click Next.

The installer displays the domain and node properties.

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

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.

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

21. Click Next.

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

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

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

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

25. Click Next.

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

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


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.

6. Enter y to run the Pre-Installation (i9Pi) System Check Tool to verify whether the machine meets the systemrequirements for the installation or upgrade.

7. Enter C for console mode installation.

8. If you entered y to run the Pre-Installation (i9Pi) System Check Tool, complete the following steps:

a. From the Informatica Pre-Installation (i9Pi) System Check Tool Welcome section, press Enter.

The System Information section appears.

b. Type the absolute path for the installation directory.

The directory names in the path must not contain spaces or the following special characters: @|* $ # ! %( ) { } [ ] , ; ' Default is /home/toolinst.


c. Press Enter.

d. Type the starting port number for the node that is being created or upgrade on the machine. Default is6005.

e. Press Enter.

f. To enter the JDBC connection information using a custom JDBC connection string, press 1. To enter theJDBC connection information using the JDBC URL information, press 2.

g. Enter the JDBC connection information.

¨ To enter the connection information using a custom JDBC connection string, type the connectionstring.IBM DB2: jdbc:Informatica:db2://host_name:port_no;DatabaseName=Oracle: jdbc:Informatica:oracle://host_name:port_no;ServiceName=SQL Server: jdbc:Informatica:sqlserver://host_name:port_no;SelectMethod=cursor;DatabaseName=Sybase: jdbc:Informatica:sybase://host_name:port_no;DatabaseName=Verify that the connection string contains all the connection parameters required by your databasesystem.

¨ To enter the connection information using the JDBC URL information, specify the JDBC URLproperties.

Prompt Description






Database service name Password for the domain configuration database user account.Service name for Oracle and IBM DB2 databases or database name for MicrosoftSQL Server and Sybase ASE.

The tool checks the settings of the hard drive, the availability of the ports, and the configuration of thedatabase. After the system check is complete, the System Check Summary section appears, displayingthe results of the system check.

h. Analyze the results of the system check.

Each requirement is listed in the table, along with one of the following check statuses:



¨ [Fail] - The requirement does not meet the criteria for the Informatica installation or upgrade. Resolvethe issue before proceeding.


The results of the system check are saved to the following file: /Server/I9PI/I9PI/en/i9Pi_summary.txt.

i. Press Enter to close the Pre-Installation (i9Pi) System Check Tool.

j. If the Pre-Installation (i9Pi) System Check Tool finishes with failed requirements, press n to quit theinstallation or upgrade. Resolve the failed requirements, and run the installation or upgrade again.



If the Pre-Installation (i9Pi) System Check Tool finished and all of the requirements meet the criteria for theInformatica upgrade, enter 2 to proceed with the upgrade.


11. Press Enter.

12. At the prompt, enter the following directories:




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

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

14. Press Enter.

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

The installer copies the server files to the Informatica 9.5.1 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.

16. Press Enter.

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

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

The installer displays the domain and node properties.

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

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

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

The following table describes the ports that you can specify:

Port Description

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


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.


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

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.

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, restore the domain configuration repository database from backup and run the installer again.

Troubleshooting the Domain Upgrade 43

C H A P T E R 4

Before You Upgrade theApplication Services

This chapter includes the following topics:

¨ Pre-Upgrade Tasks, 44

¨ Configure Informatica Environment Variables, 44

¨ Configure Locale Environment Variables, 45

¨ Clear Browser Cache, 45

¨ Change the Node Configuration, 46

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

1. Configure Informatica environment variables.

2. Configure locale environment variables.

3. Clear browser cache.

4. Tasks for changing the node configuration.

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.

44

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

INFA_HOME

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

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

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

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

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

locale -a

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

Locale on Linux

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

Locale for Oracle Database Clients

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

setenv NLS_LANG american_america.UTF8

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 Locale Environment Variables 45

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 SoftwareBased on the types of databases that the Data Integration Service will access, install the following databaseclients and configure connectivity on the machine where the Data 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 (OCS)

¨ Teradata BTEQ client

Database Client Environment VariablesConfigure database client environment variables on the machines that run the Data Integration Service. Thedatabase client path variable name and requirements depend 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 on 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

46 Chapter 4: Before You Upgrade the Application Services

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 Variables

Configure library path environment variables on the machines that run the Data Integration Service processes. Thelibrary path variable name and requirements depend on the UNIX platform and database.

Solaris and Linux

On Solaris and Linux, configure the LD_LIBRARY_PATH environment variable.

The following table describes the values that 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 that you set for the LIBPATH for the different databases:

Database Value



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




Change the Node Configuration 47

HP-UX

On HP-UX, configure the SHLIB_PATH environment variable.

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

Database Value



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




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. Use the following command to start the virtual frame buffer and sendgraphics outputs going to display 1 to shared memory:

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

48 Chapter 4: Before You Upgrade the Application Services

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.

Change the Node Configuration 49

C H A P T E R 5

Application Service UpgradeThis chapter includes the following topics:

¨ Application Service Upgrade Overview, 50

¨ Service Upgrade Wizard, 50

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.

Service Upgrade for Data Quality 9.5.0Before you upgrade services, verify that the services are enabled. You must upgrade the Model RepositoryService before you upgrade Data Integration Service. Upgrade the Data Integration Service before you upgradethe Content Management Service.

A user with the Administrator role on the domain, the Model Repository Service, the Data Integration Service, andthe Content Management Service can upgrade services.

To upgrade services, upgrade the following object types:

¨ Model Repository Service.

¨ Data Integration Service.

¨ Content Management Service.

¨ Profiling Service Module for Data Integration Service.

Service Upgrade WizardUse the service upgrade wizard to upgrade services.

50

The service upgrade wizard provides the following options:

¨ Upgrade multiple services.

¨ Enable services before the upgrade.

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

¨ Save the current or previous upgrade report.

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

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

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

7. Click Next.

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

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

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

10. Click Close.

11. If you did not choose to automatically recycle services after upgrade, restart upgraded services.

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 client tools areinstalled on the installation directory you specify. The client installer configures the newly installed client tools withthe same settings as the previous version. The client installer does not modify the files of the previous version ofthe 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 Data Quality, you can upgrade Informatica Developer. The Developer tool is a client application that you useto create and run mappings, data objects, and virtual databases. Objects created in the Developer tool are storedin a Model repository and are run by a Data Integration Service.

By default, the when you upgrade Informatica Developer, the following components are also upgraded:

¨ JDBC and ODBC drivers to connect to SQL data services.

¨ DataDirect ODBC drivers

¨ Java Runtime Environment libraries

You can perform the upgrade from a DVD or from the root of the directory where you download the installationfiles.

On Windows, the length of the entire installation directory path, including the zip file name, must be 60 charactersor less. Verify that the zip utility version is compatible with the Windows operating system version. When you unzipthe file, verify that the zip utility also extracts empty folders.

On UNIX, use native tar or GNU tar to extract the installer files. The user that runs the installer must have readand write permissions on the installer files directory and execute permissions on install.sh.

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

¨ Data Transformation

If you have Data Transformation 9.1.0 installed, upgrading Informatica Developer also upgrades DataTransformation Studio. If you do not have Data Transformation installed, upgrading Informatica Developerinstalls Data Transformation Studio.

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.5.1 client tools

Directory in which to install the Informatica 9.5.1 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.

Informatica Client Upgrade Options 53

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

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 Data Transformation Studio.

54 Chapter 6: Informatica Client Upgrade


If the value is 1, Data Transformation Studio will be installed. If the value is 0,Data Transformation Studio will not be installed.If DXT_COMP=1, set this parameter to 1.

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

¨ Informatica Domain, 56

¨ Data Integration Service, 57

¨ Analyst Service, 57

¨ Content Management Service, 58

¨ Data Director Service, 58

¨ Informatica Analyst, 58

¨ Upgrade the Informatica Drivers for SQL Data Services, 59

¨ Merge the Address Doctor Configuration Files, 59

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.

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.

56

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

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

Update the Profiling WarehouseIf the profiling warehouse is in an IBM DB2 9.1 database, run the DB2 REORGCHK command to optimize databaseoperations. The REORGCHK command generates the database statistics used by the DB2 optimizer in queries andupdates.

Use the following command:

REORGCHK UPDATE STATISTICS on SCHEMA <SchemaName>

Reset the HTTP Proxy Server PasswordIf the Data Integration Service runs Web Service Consumer transformations and is configured to use an HTTPproxy server with authentication, reset the HTTP proxy server password.

If you do not reset the password, then the Data Integration Service cannot successfully process Web ServiceConsumer transformations.

Reset the HTTP Proxy Server Password for the Data Integration Service in the Administrator tool.

Analyst ServiceAfter you upgrade, complete the post-upgrade tasks for each Analyst Service.

Verify Directories and FilesIf you have an Analyst Service in your Informatica domain, you must verify the accuracy of the flat file cachedirectory and keystore file location, as the installer does not update these locations.

If flat file cache or keystore locations point to the previous Informatica installation directory structure, copy the filesto the new Informatica installation directory. If the files are located outside the Informatica installation directorystructure, verify that the machine that runs Informatica can access the files.

To verify the location of the flat file cache, view Flat File Cache Location in the Data Integration Service Optionsection of the Analyst Service.

To verify the location of the keystore, view Keystore File in the Analyst Security Options section of the AnalystService Processes view.

Restart the Analyst Service

Data Integration Service 57

To access the Analyst tool after you upgrade, restart the Analyst Service. Before you restart the Analyst Service,complete the upgrade and post-upgrade steps for the Model Repository Service and Data Integration Service.

Verify that the following tasks are complete before you restart the Analyst Service:

¨ Upgrade the Model Repository Service

¨ Upgrade the Data Integration Service

Assign PrivilegesIf you have an Analyst Service in your Informatica domain, grant the Access Mapping Specifications and LoadMapping Specification Results privileges to users.

Content Management ServiceAfter you upgrade, complete the post-upgrade steps for each Content Management Service. You must configurethe Content Management Service before you can use reference data, address reference data, identity populationdata, or probabilistic models.

You create a Content Management Service on any node that contains a Data Integration Service. If the DataIntegration Service runs a mapping that reads reference data, associate the Data Integration Service with theContent Management Service on the same node. You cannot associate a Data Integration Service with more thanone Content Management Service.

Note: If you create multiple Content Management Services in a domain, the first service that you create becomesthe master Content Management Service.

If the domain does not specify a master Content Management Service, the upgrade process sets the currentservice as the master Content Management Service.

Data Director ServiceAfter you upgrade, optionally create a Data Director Service. The Data Director Service is an application servicethat runs the Informatica Data Director for Data Quality web application in the Informatica domain.

A data analyst uses Informatica Data Director for Data Quality when assigned an instance of a Human task. AHuman task is a task in a workflow that specifies user actions in an Informatica application.

The Data Director Service connects to a Data Integration Service. You configure a Human Task Service module inthe Data Integration Service so that the Data Integration Service can start a Human task in a workflow.

Informatica AnalystAfter you upgrade, complete the post-upgrade task for the Analyst tool.

58 Chapter 7: After You Upgrade

ScorecardsIf you created scorecards in Informatica Analyst, run the infacmd ps migrateScorecards command to migrate theresults of scorecards.

Upgrade the Informatica Drivers for SQL Data ServicesUpgrade the Informatica JDBC or ODBC drivers for SQL data services.

Upgrade the Informatica ODBC or JDBC driver on the machine from which you connect to the SQL data service.To upgrade the driver, run the Informatica JDBC/ODBC driver installation program and select the upgrade option.

Merge the Address Doctor Configuration FilesIf you use Address Doctor address validation reference data in PowerCenter, merge the contents of the AD50.cfgand AD50.cfg.bak files to maintain your Address Doctor settings.

During the upgrade process, the installer renames the original AD50.cfg file to AD50.cfg.bak and installs a newAD50.cfg file in the same folder. The AD50.cfg and AD50.cfg.bak files are stored in the<InformaticaInstallationDir>/server/bin directory.

Upgrade the Informatica Drivers for SQL Data Services 59

A P P E N D I X A

Upgrade ChecklistThis appendix includes the following topics:

¨ Upgrade Checklist Overview, 60

¨ Before You Upgrade the Domain and Server Files, 60

¨ Domain and Server Files Upgrade, 61

¨ Before You Upgrade the Application Services, 61

¨ Application Service Upgrade, 61

¨ Informatica Client Upgrade, 62

¨ After You Upgrade, 62

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.

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

60

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

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 21

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

1. Configure Informatica environment variables.

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

3. Clear browser cache.

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

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 44

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

Domain and Server Files Upgrade 61

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

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.The Informatica installation includes DataDirect 6.0 SP3 ODBC drivers. Re-create each ODBC data source touse the new drivers.

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

62 Appendix A: Upgrade Checklist

I N D E X

AAIX

configuring X Virtual Frame Buffer (Xvfb) 48

Ddatabase client

configuring 46environment variables 46install for Informatica client tools 46

databasestesting connections 46

dbs2 connecttesting database connection 46

disk space requirementsinstallation requirements 10

DISPLAYenvironment variables 7

Domain Activity Reportingsetting up on UNIX 48

Eenvironment variables

database client 46DISPLAY 12installation 7, 10library path 47UNIX database client 46

Ggraphical mode

installation requirements 12

HHP-UX

configuring X Virtual Frame Buffer (Xvfb) 48

IIATEMPDIR

environment variables 7, 10installation requirements

disk space 10environment variables 7, 10X Window Server 12

isqltesting database connection 46

JJRE_HOME

environment variables 7, 10

LLANG

locale environment variables 7, 10LC_ALL

locale environment variables 7, 10library path

environment variables 10Linux

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

PPATH

environment variables 10

SService Upgrade Wizard

upgrading services 51services

Service Upgrade Wizard 51Solaris

configuring X Virtual Frame Buffer (Xvfb) 48sqlplus

testing database connection 46

Uuninstalling

before upgrade or migration 13Data Transformation 12

UNIXdatabase client environment variables 46database client variables 46library paths 47user account 19

upgradingService Upgrade Wizard 51

user accountUNIX 19

63

XX Virtual Frame Buffer (Xvfb)

installing on UNIX 48

X Window Serverinstallation requirements 12

64 Index

DQ 951 Upgrade950 En

Documents

Transcript of DQ 951 Upgrade950 En