Вы находитесь на странице: 1из 95

Informatica PowerCenter (Version 9.6.

0)

Upgrade Guide for Version


9.5.1

Informatica PowerCenter Upgrade Guide for Version 9.5.1


Version 9.6.0
January 2014
Copyright (c) 1998-2014 Informatica Corporation. All rights reserved.
This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use
and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in
any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S.
and/or international Patents 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 in DFARS 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
in writing.
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
On Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and
Informatica Master Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world.
All other company and product names may be trade names or trademarks of their respective owners.
Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights
reserved. Copyright Sun Microsystems. All rights reserved. Copyright RSA Security Inc. All Rights Reserved. Copyright Ordinal Technology Corp. All rights
reserved.Copyright Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright Meta
Integration Technology, Inc. All rights reserved. Copyright Intalio. All rights reserved. Copyright Oracle. All rights reserved. Copyright Adobe Systems
Incorporated. All rights 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 Information Builders, Inc. All rights reserved. Copyright OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved.
Copyright Cleo Communications, Inc. All rights reserved. Copyright International Organization for Standardization 1986. All rights reserved. Copyright ejtechnologies GmbH. All rights reserved. Copyright Jaspersoft Corporation. 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 Board of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright
EMC Corporation. All rights reserved. Copyright Flexera Software. All rights reserved. Copyright Jinfonet Software. All rights reserved. Copyright Apple Inc. All
rights reserved. Copyright Telerik Inc. All rights reserved. Copyright BEA Systems. All rights reserved. Copyright PDFlib GmbH. All rights reserved. Copyright
Orientation in Objects GmbH. All rights reserved. Copyright Tanuki Software, Ltd. All rights reserved. Copyright Ricebridge. All rights reserved. Copyright Sencha,
Inc. All rights reserved.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and/or other software which is licensed under various versions
of the Apache License (the "License"). You may obtain a copy of these Licenses at http://www.apache.org/licenses/. Unless required by applicable law or agreed to in
writing, software distributed under these Licenses is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied. See the Licenses for the specific language governing permissions and limitations under the Licenses.
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 various versions of 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 not limited 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 of this 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-2013, Daniel Stenberg, <daniel@haxx.se>. All Rights Reserved. Permissions and limitations regarding this
software 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
without fee 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
available at 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
terms available 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 this software 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 & Wireless
Deutschland. 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
subject to 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 terms
available at http:// www.eclipse.org/org/documents/epl-v10.php and at http://www.eclipse.org/org/documents/edl-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:// 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/licenseagreements/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://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; http://benalman.com/about/license/; https://github.com/CreateJS/EaselJS/blob/master/src/easeljs/display/Bitmap.js;
http://www.h2database.com/html/license.html#summary; http://jsoncpp.sourceforge.net/LICENSE; http://jdbc.postgresql.org/license.html; http://
protobuf.googlecode.com/svn/trunk/src/google/protobuf/descriptor.proto; https://github.com/rantav/hector/blob/master/LICENSE; http://web.mit.edu/Kerberos/krb5current/doc/mitK5license.html; http://jibx.sourceforge.net/jibx-license.html; and https://github.com/lyokato/libgeohash/blob/master/LICENSE.
This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and Distribution
License (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php), the Sun Binary Code License
Agreement Supplemental License Terms, the BSD License (http:// www.opensource.org/licenses/bsd-license.php), the new BSD License (http://opensource.org/
licenses/BSD-3-Clause), the MIT License (http://www.opensource.org/licenses/mit-license.php), the Artistic License (http://www.opensource.org/licenses/artisticlicense-1.0) and the Initial Developers Public License Version 1.0 (http://www.firebirdsql.org/en/initial-developer-s-public-license-version-1-0/).
This product includes software copyright 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this
software are subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab.
For further information please visit http://www.extreme.indiana.edu/.
This product includes software Copyright (c) 2013 Frank Balluffi and Markus Moeller. All rights reserved. Permissions and limitations regarding this software are subject
to terms of the MIT license.
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,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;
7,676,516; 7,720,842; 7,721,270; 7,774,791; 8,065,266; 8,150,803; 8,166,048; 8,166,071; 8,200,622; 8,224,873; 8,271,477; 8,327,419; 8,386,435; 8,392,460;
8,453,159; 8,458,230; and RE44,478, 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
implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is
error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and
documentation is subject 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 Software
Corporation ("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 NOT
LIMITED 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 OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT
LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.
Part Number: PC-UPG-96000-0002

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Informatica My Support Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Informatica Support YouTube Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Informatica Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Informatica Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

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


Informatica Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Upgrade Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Changing the Node Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Upgrade Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

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


Read the Release Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Pre-Upgrade Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Review the UNIX Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Install Java Development Kit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Verify the Minimum System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Verify the System Requirements for the Domain and Application Services. . . . . . . . . . . . . . . 7
Review the Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Set the File Descriptor Limit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Review the Maximum Heap Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Install the bos.adt.debug Fileset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Extract the Installer Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Run the Pre-Installation (i9Pi) System Check Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Review the Windows Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Review the System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Verify the System Requirements for the Domain and Application Services. . . . . . . . . . . . . . 13
Review the Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Review the Maximum Heap Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Extract the Installer Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Run the Pre-Installation (i9Pi) System Check Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Back Up the Data Transformation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Prepare the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Table of Contents

Back Up the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18


Verify Database User Account Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Migrate to a Supported Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Migrate to a Supported Operating System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Prepare the PowerCenter Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Export the Jaspersoft Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Prepare the Reporting and Dashboard Service for Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . 21
Prepare Metadata Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Back Up the Metadata Manager Warehouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Export and Delete Business Glossaries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Back Up the Metadata Manager Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Prepare Data Analyzer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Assign Roles to Users and Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Back Up the Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Shut Down the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Prepare to Change the Node Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Configure the Windows Machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Configure the UNIX Machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Copy the Installation Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Verify Keystore File Name and Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Chapter 3: Domain and Server Files Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29


Domain and Server Files Upgrade Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Secure Directory for the Encryption Key and Configuration Files. . . . . . . . . . . . . . . . . . . . 30
Upgrading in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Upgrading in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Upgrading in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Creating the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Upgrading with Changes to the Node Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Upgrading in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Upgrading in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Upgrading in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Troubleshooting the Domain Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 4: Before You Upgrade the Application Services. . . . . . . . . . . . . . . . . . . . . . 52


Pre-Upgrade Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Configure POSIX Asynchronous I/O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Configure Informatica Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Configure Locale Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Clear Browser Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Change the Node Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Install the Database Client Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

ii

Table of Contents

Configure Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55


Verify that a Graphics Display Server is Available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Update Port Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Verify the Node Backup Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Update Keystore File Name and Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Configure PowerExchange Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 5: Application Service Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59


Application Service Upgrade Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Service Upgrade for PowerCenter 9.5.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Service Upgrade Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Upgrade Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Running the Service Upgrade Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Chapter 6: Informatica Client Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61


Informatica Client Upgrade Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Informatica Client Upgrade Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Upgrading in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Upgrading in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Creating the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Chapter 7: After You Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65


Informatica Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Configure LDAP Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Update the Log Events Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Update ODBC Data Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Remove Migrated Installation Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
PowerCenter Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Configure Umask for Operating System Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Business Glossary Desktop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Changing the Business Glossary Desktop Port Number. . . . . . . . . . . . . . . . . . . . . . . . . . 66
Search Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Business Glossaries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Step 1. Create Glossaries in the Analyst Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Step 2. Import the Metadata Manager Model Export File. . . . . . . . . . . . . . . . . . . . . . . . . . 67
Step 3. Add Custom Attributes to Business Term Templates. . . . . . . . . . . . . . . . . . . . . . . 68
Step 4. Import Business Glossary Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Metadata Manager Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Update the Metadata Manager Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Create Business Glossary Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Metadata Manager Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Reporting and Dashboards Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Table of Contents

iii

Upgrade to Jaspersoft 4.7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71


Changing to Kerberos Authentication after Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Verify the Domain and Service Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Verify the Kerberos Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Create the Service Principal Names and Keytab Files. . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Change the Domain Authentication to Kerberos Network Authentication. . . . . . . . . . . . . . . 76
Update All Nodes in the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Update the Client Machines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Start the Informatica Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Appendix A: Upgrade Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80


Upgrade Checklist Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Before You Upgrade the Domain and Server Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Domain and Server Files Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Before You Upgrade the Application Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Application Service Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Informatica Client Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
After You Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

iv

Table of Contents

Preface
The Upgrade Guide for Version 9.5.1 is written for the system administrator who is responsible for upgrading
the Informatica product. This guide assumes that you have knowledge of operating systems, relational
database concepts, and the database engines, flat files, or mainframe systems in your environment. This
guide also assumes that you are familiar with the interface requirements for your supporting applications.

Informatica Resources
Informatica My Support Portal
As an Informatica customer, you can access the Informatica My Support Portal 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, Informatica Product Documentation, and access to the Informatica user community.

Informatica Documentation
The Informatica Documentation team takes every effort to create accurate, usable documentation. If you
have questions, comments, or ideas about this documentation, contact the Informatica Documentation team
through email at infa_documentation@informatica.com. We will use your feedback to improve our
documentation. Let us know 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 Site


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

Informatica How-To Library


As 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. It includes articles and interactive demonstrations that provide

solutions to common problems, compare features and behaviors, and guide you through performing specific
real-world tasks.

Informatica Knowledge Base


As 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 Informatica products. You can also find answers to frequently asked questions,
technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge
Base, contact the Informatica Knowledge Base team through email at KB_Feedback@informatica.com.

Informatica Support YouTube Channel


You can access the Informatica Support YouTube channel at http://www.youtube.com/user/INFASupport. The
Informatica Support YouTube channel includes videos about solutions that guide you through performing
specific tasks. If you have questions, comments, or ideas about the Informatica Support YouTube channel,
contact the Support YouTube team through email at supportvideos@informatica.com or send a tweet to
@INFASupport.

Informatica Marketplace
The Informatica Marketplace is a forum where developers and partners can share solutions that augment,
extend, or enhance data integration implementations. By leveraging any of the hundreds of solutions
available on the Marketplace, you can improve your productivity and speed up time to implementation on
your projects. You can access Informatica Marketplace at http://www.informaticamarketplace.com.

Informatica Velocity
You can access Informatica Velocity at http://mysupport.informatica.com. Developed from the real-world
experience of hundreds of data management projects, Informatica Velocity represents the collective
knowledge of our consultants who have worked with organizations from around the world to plan, develop,
deploy, and maintain successful data management solutions. If you have questions, comments, or ideas
about Informatica Velocity, contact Informatica Professional Services at ips@informatica.com.

Informatica Global Customer Support


You can contact a Customer Support Center by telephone or through the Online Support.
Online Support requires a user name and password. You can request a user name and password at
http://mysupport.informatica.com.
The telephone numbers for Informatica Global Customer Support are available from the Informatica web site
at http://www.informatica.com/us/services-and-training/support-services/global-support-centers/.

vi

Preface

CHAPTER 1

Upgrade Overview
This chapter includes the following topics:

Informatica Upgrade, 1

Upgrade Process, 3

Upgrade Tasks, 4

Informatica Upgrade
The Informatica platform consists of a server component and one or more client components. Informatica
provides separate installers to upgrade the Informatica services and clients.
If the product version that is currently installed cannot be upgraded to Informatica 9.6.0, you must first
upgrade to a supported version. To determine the Informatica product version that is currently installed, click
Help > About Informatica Administrator in the Informatica Administrator header area.
The following table describes the Informatica product versions from which you can upgrade:
Informatica Product Version

Comments

PowerCenter 8.1.x

You must first upgrade to Informatica PowerCenter 9.1.0.


If the PowerCenter 8.1.x domain includes Metadata Manager or Data
Analyzer, you must first upgrade to PowerCenter 8.6.1 and then upgrade to
Informatica PowerCenter 9.1.0.

PowerCenter 8.5.x

You must first upgrade to Informatica PowerCenter 9.1.0.


If the PowerCenter 8.5.x domain includes the Metadata Manager Service or
Reporting Service, you must first upgrade to PowerCenter 8.6.1 and then
upgrade to Informatica PowerCenter 9.1.0.

PowerCenter 8.6

You must first upgrade to Informatica PowerCenter 9.1.0.


If the PowerCenter 8.6 domain includes the Metadata Manager Service,
Reporting Service, or Reference Table Manager Service, you must first
upgrade to PowerCenter 8.6.1 and then upgrade to Informatica PowerCenter
9.1.0.

PowerCenter 8.6.1

You must first upgrade to Informatica PowerCenter 9.1.0.

Informatica Product Version

Comments

Data Quality 8.6.2

You can migrate the contents of the Informatica Data Quality 8.6.2 repository
to the Informatica Data Quality 9.0.1 Model repository. See the 9.0.1 Data
Quality migration documentation for details.
After you migrate the contents to the Informatica 9.0.1 Model repository,
upgrade to Informatica Data Quality 9.0.1 and then upgrade to Informatica
Data Quality 9.1.0.

Data Explorer Advanced Edition


9.0

You must first upgrade to Data Explorer Advanced Edition 9.0.1. See the
Informatica Data Quality 9.0.1 upgrade documentation. Complete the steps to
upgrade Informatica Data Quality 9.0 unless an exception is specified.
After you upgrade to Informatica Data Explorer Advanced Edition 9.0.1,
upgrade to Informatica Data Explorer 9.1.0.

Data Quality 9.0

You must first upgrade to Informatica Data Quality 9.0.1, and then upgrade to
Informatica Data Quality 9.1.0.

Data Services 9.0

You must first upgrade to Informatica Data Services 9.0.1, and then upgrade
to Informatica Data Services 9.1.0.

Data Transformation 9.0.1 or


earlier versions

You must uninstall Data Transformation and then install Informatica Data
Transformation 9.6.0. See the Data Transformation 9.6.0 installation and
upgrade documentation.

PowerCenter 9.0

You must first upgrade to Informatica PowerCenter 9.1.0.

Informatica Data Explorer


Advanced Edition 9.0.1

You must first upgrade to Informatica Data Explorer 9.1.0.

Informatica Data Quality 9.0.1

You must first upgrade to Informatica Data Quality 9.1.0.

Informatica Data Services 9.0.1

You must first upgrade to Informatica Data Services 9.1.0.

Informatica PowerCenter 9.0.1

You must first upgrade to Informatica PowerCenter 9.1.0.

Informatica Data Explorer 9.1.0

Informatica Data Quality 9.1.0

Informatica Data Services 9.1.0

Informatica Data Transformation


9.1.0

Informatica PowerCenter 9.1.0

If the PowerCenter 9.1.0 domain includes the Metadata Manager Service,


and Metadata Manager contains business glossaries, you must first upgrade
to PowerCenter 9.5.0, and then upgrade to Informatica PowerCenter 9.6.0.

Informatica Data Explorer 9.5.0

Informatica Data Quality 9.5.0

Informatica Data Services 9.5.0

Informatica Data Transformation


9.5.0

Chapter 1: Upgrade Overview

Informatica Product Version

Comments

Informatica PowerCenter 9.5.0

Informatica Data Explorer 9.5.1

Informatica Data Quality 9.5.1

Informatica Data Services 9.5.1

Informatica Data Transformation


9.5.1

Informatica PowerCenter 9.5.1

Upgrade Process
The upgrade consists of the following phases:

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

Description

Installs Informatica.

Installs Informatica directories and files into the new


directory.

Copies infa_shared directory.

Copies the contents of the infa_shared directory from


the existing installation directory into the new
installation directory.

Copies mm_files directory.

Copies the contents of the mm_files directory from


the default location in the existing installation
directory into the new installation directory.

Upgrades the domain.

Upgrades the domain to run version 9.6.0 application


services.

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
Administrator tool and upgrade the application services. The service upgrade wizard provides a list of all
application services that 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 and
select the upgrade option. If the client is installed on multiple machines, upgrade the client on all
machines.

Upgrade Process

Changing the Node Configuration


The installer provides the option to allow changes to node host name and port number. When you select this
option you can change the node configuration. Change the node configuration when you move the
Informatica installation to a different machine.
If you choose the option to update the node configuration on one gateway node, you must use this option on
all gateway nodes in the domain.
If you choose the option to update the node configuration, you need to perform additional upgrade steps.
There are additional steps before you upgrade the domain and server files, and before you upgrade the
application services.

Upgrade Tasks
To upgrade PowerCenter, complete the following tasks:
1.

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

2.

Upgrade the Informatica domain and server files. Use the server installer to upgrade Informatica domain
and upgrade the server files on each node. If the domain contains multiple nodes, upgrade the gateway
node before you upgrade the worker nodes. After you upgrade the first gateway node, verify that the
upgrade was successful 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 the
application services.

5.

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

6.

Perform the post-upgrade tasks.

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

Chapter 1: Upgrade Overview

CHAPTER 2

Before You Upgrade the Domain


and Server Files
This chapter includes the following topics:

Read the Release Notes, 5

Pre-Upgrade Tasks, 5

Review the UNIX Requirements, 6

Review the Windows Requirements, 12

Back Up the Data Transformation Files, 17

Prepare the Domain, 18

Prepare the PowerCenter Repository, 20

Export the Jaspersoft Resources, 20

Prepare the Reporting and Dashboard Service for Upgrade, 21

Prepare Metadata Manager, 22

Prepare Data Analyzer, 24

Shut Down the Domain, 25

Prepare to Change the Node Configuration, 25

Read the Release Notes


Read the Informatica Release Notes for updates to the installation and upgrade process and to verify domain
patches and libraries. You can also find information about known and fixed limitations for the release.

Pre-Upgrade Tasks
Before you upgrade Informatica services, set up the machine to meet the requirements to upgrade
Informatica. If the machine where you upgrade Informatica is not configured correctly, the upgrade can fail.

Review the UNIX Requirements


Before you upgrade the domain, review the following UNIX requirements:
1.

Install the Java Development Kit.

2.

Review the system requirements.

3.

Review the upgrade memory requirements.

4.

Review the environment variables.

5.

Verify the file descriptor settings.

6.

Review the maximum heap size.

7.

Set up the X Windows server.

Install Java Development Kit


If you are upgrading Informatica on AIX, verify that the Informatica version you are upgrading to supports the
version of Java Development Kit (JDK) that is installed on your machine. If you do not have a supported
version of JDK installed, uninstall the current version, and then download and install the supported version.
You can download the JDK for AIX from the following web site:
http://www.ibm.com/developerworks/java/jdk/aix/service.html#java7
Informatica is certified with a specific JDK version. To determine which JDK version to install, see the
Informatica Release 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
Informatica Corporation. The download links are subject to the possibility of errors, omissions or change.
Informatica assumes no responsibility for such links and/or such software, disclaims all warranties, either
express or implied, including but not limited to, implied warranties of merchantability, fitness for a particular
purpose, title and non-infringement, and disclaims all liability relating thereto.

Verify the Minimum System Requirements


Verify that your machine meets the minimum system requirements to upgrade the Informatica server
component.
For more information about product requirements and supported platforms, see the Product Availability Matrix
on the Informatica My Support Portal:
https://mysupport.informatica.com/community/my-support/product-availability-matrices
The following table lists the minimum disk space and memory required to upgrade the Informatica server
component:
RAM

Disk Space

4 GB

8 GB

Temporary Disk Space Requirements


The installer writes temporary files to the hard disk. Verify that you have enough available disk space on the
machine to support the installation. When the installation completes, the installer deletes the temporary files
and releases the disk space.

Chapter 2: Before You Upgrade the Domain and Server Files

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

Disk Space

Installer

1 GB

Informatica Services

2 GB

Verify the System Requirements for the Domain and Application


Services
The Informatica version to which you are upgrading requires more memory and disk space than previous
versions.
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, and


PowerCenter services running on one node

4 CPU

10GB

20 GB

Domain with all PowerCenter services running on


one node

2 CPU

4 GB

10 GB

Domain with all PowerCenter services running on


one node except Metadata Manager Service and
Reporting Service

1 CPU

4 GB

10 GB

Metadata Manager Service running on a separate


node

2 CPU

4 GB

10 GB

Reporting Service running on a separate node

1 CPU

512 MB

10 GB

Metadata Manager Agent

1 CPU

512 MB

400 MB

Review the Environment Variables


Configure the environment variables to work with the Informatica installation.
Set the environment variables before you install Informatica.
The following table describes the environment variables to review on UNIX:
Variable

Description

IATEMPDIR

Location of the temporary files created during installation. Informatica


requires 1 GB disk 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 the upgrade.

Review the UNIX Requirements

Variable

Description

INFA_HOME

Contains the location of the Informatica installation directory. Clear this


variable before you start the upgrade.

INFA_JDK_HOME

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

JRE_HOME

If you install the Informatica services on a Linux machine, clear the


JRE_HOME environment variable before you 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 Shift JIS for Japanese, or UTF-8 for Chinese or
Korean. The character encoding determines the types of characters that
appear in the UNIX terminal.

Library path

Verify that the library path environment variables do not contain earlier
versions of Informatica.

PATH

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

Set the File Descriptor Limit


Verify that the operating system meets the file descriptor requirement.
Informatica service processes can use a large number of files. Set the file descriptor limit per process to
16,000 or higher. The recommended limit is 32,000 file descriptors per process.
To verify the file descriptor limit, run the following command:
C Shell
limit
Bash Shell
ulimit -a

Chapter 2: Before You Upgrade the Domain and Server Files

Review the Maximum Heap Size


Verify 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
of users and services in the domain:
Number of Domain Users

Maximum Heap Size

Maximum Heap Size

(1-5 Services)

(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 application services in the
domain.
If the domain has more than 1,000 users, update the maximum heap size based on the number of users in
the domain.
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

Install the bos.adt.debug Fileset


If you are upgrading to Informatica on IBM AIX 6.1, install the bos.adt.debug Version 6.1.8.0 Fix Pack
6100-08 fileset. If you are upgrading to Informatica on IBM AIX 7.1, install the bos.adt.debug Version
7.1.2.0 Fix Pack 7100-02 fileset.
You can download the fileset from the IBM web site:
http://www-01.ibm.com/support/docview.wss?uid=isg1fileset2055455918.

Extract the Installer Files


The installer files are compressed and distributed as a tar file.
Use a native tar or GNU tar utility to extract the installer files to a directory on your machine.
You can extract the installer files in the following ways:

Installation DVD. Download the Informatica tar file from the installation DVD to a directory on your
machine and then extract the installer files, or extract the installer files directly from the DVD to a directory
on your machine.

Review the UNIX Requirements

FTP download. Download the Informatica installation tar file from the Informatica Electronic Software
Download (ESD) site to a directory on your machine and then extract the installer files.

Run the Pre-Installation (i9Pi) System Check Tool


Run the Pre-installation (i9Pi) System Check Tool to verify whether the machine meets the system
requirements for installation or upgrade.
1.

Log in to the machine with a system user account.

2.

Close all other applications.

3.

On a shell command line, run the install.sh file from 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, press n to exit the installer and set them as required.
If the environment variables are set, press y to continue.

5.

Press 1 to install or upgrade Informatica.

6.

Press 1 to run the Pre-Installation (i9Pi) System Check Tool that verifies whether the machine meets the
system requirements for the installation or upgrade.

7.

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

8.

Type the absolute path for the installation directory.


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

9.

Press Enter.

10.

Enter the starting port number for the node that you will create or upgrade on the machine. The default
port number for the node is 6005.

11.

Press Enter.
The Database and Connection Information section appears.

12.

To enter the JDBC connection information using a custom JDBC connection string, press 1. To enter the
JDBC connection information using the JDBC URL information, press 2.
To connect to a secure database, you must enter the JDBC connection using a custom JDBC connection
string.

10

Chapter 2: Before You Upgrade the Domain and Server Files

13.

Enter the JDBC connection information.

To enter the connection information using a custom JDBC connection string, type the connection
string and specify the connection parameters.
The following list shows the syntax of the JDBC connection string for the databases:
IBM DB2
jdbc:Informatica:db2://host_name:port_no;DatabaseName=
Oracle
jdbc:Informatica:oracle://host_name:port_no;ServiceName=
Microsoft 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 database
system.

To enter the connection information using the JDBC URL information, specify the JDBC URL
properties.
The following table describes the connection information:
Prompt

Description

Database type

Type of database for the domain configuration repository. Select from the
following database types:
-

1 - Oracle
2 - Microsoft SQL Server
3 - IBM DB2
4 - Sybase ASE

Database user ID

User ID for the database user account for the domain configuration repository.

Database user
password

Password for the database user account.

Database host name

Host name for the database server.

Database port number

Port number for the database.

Database service
name

Service name for Oracle and IBM DB2 databases or database name for
Microsoft SQL Server and Sybase ASE.

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

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. Resolve
the issue before you proceed with the installation or upgrade.

Review the UNIX Requirements

11

[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.txt
15.

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


You can continue to the Informatica service installation or upgrade immediately or end the system check
and continue with the installation or upgrade later. If you continue to the installation or upgrade
immediately, you do not have to restart the installer.

16.

To continue to the Informatica service installation or upgrade immediately, press y.


To end the system check and continue with the installation or upgrade later, press n.

If the Pre-Installation (i9Pi) System Check Tool finishes with failed requirements, resolve the failed
requirements and run the Pre-Installation (i9Pi) System Check Tool 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, Informatica highly recommends that you
resolve the failed requirements before you proceed.

Review the Windows Requirements


Before you upgrade the domain, review the following Windows requirements:
1.

Review the system requirements.

2.

Review the upgrade memory requirements.

3.

Review the environment variables.

4.

Review the maximum heap size.

Review the System Requirements


Verify that your system meets the upgrade requirements.
Verify that your machine meets the minimum system requirements to upgrade the Informatica server
component.
The following table lists the minimum system requirements:
RAM

Disk Space

4 GB

5 GB

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

12

Chapter 2: Before You Upgrade the Domain and Server Files

The following table lists the minimum system requirements to run the Informatica client tools:
Client

Processor

RAM

Disk Space

PowerCenter Client

1 CPU

512 MB

1.6 GB

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
on the Informatica My Support Portal:
https://mysupport.informatica.com/community/my-support/product-availability-matrices

Temporary Disk Space Requirements


The installer writes temporary files to the hard disk. Verify that you have enough available disk space on the
machine to support the installation. When the installation completes, the installer deletes the temporary files
and releases 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

2 GB

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

Disk Space

Installer

1 GB

Informatica Clients

550 MB

Verify the System Requirements for the Domain and Application


Services
The Informatica version to which you are upgrading requires more memory and disk space than previous
versions.
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, and


PowerCenter services running on one node

4 CPU

10GB

20 GB

Domain with all PowerCenter services running on


one node

2 CPU

4 GB

10 GB

Review the Windows Requirements

13

Component

Processor

RAM

Disk Space

Domain with all PowerCenter services running on


one node except Metadata Manager Service and
Reporting Service

1 CPU

4 GB

10 GB

Metadata Manager Service running on a separate


node

2 CPU

4 GB

10 GB

Reporting Service running on a separate node

1 CPU

512 MB

10 GB

Metadata Manager Agent

1 CPU

512 MB

400 MB

Review the Environment Variables


Configure the environment variables to work with the Informatica installation.
The following table describes environment variables to review on Windows:
Variable

Description

%TEMP%

Location of the temporary files created during installation. Informatica


requires 1 GB disk space for temporary files.
Configure the environment variable if you do not want to create temporary
files in the default drive.

PATH

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

Library path

Verify that the library path environment variables do not contain earlier
versions of Informatica.

INFA_HOME

Contains the location of the Informatica installation directory. Clear this


variable before you start the upgrade.

INFA_DOMAINS_FILE

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

Review the Maximum Heap Size


Verify 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
of users and services in the domain:
Number of Domain Users

14

Maximum Heap Size

Maximum Heap Size

(1-5 Services)

(6-10 Services)

1,000 or less

512 MB (default)

1024 MB

5,000

2048 MB

3072 MB

10,000

3072 MB

5120 MB

Chapter 2: Before You Upgrade the Domain and Server Files

Number of Domain Users

Maximum Heap Size

Maximum Heap Size

(1-5 Services)

(6-10 Services)

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 application services in the
domain.
If the domain has more than 1,000 users, update the maximum heap size based on the number of users in
the domain.
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

Extract the Installer Files


The installer files are compressed and distributed as a zip file.
Use a zip utility to extract the installer files to a directory on your machine. Verify the zip utility version is
compatible with the Windows operating system version. When you unzip the file, verify that the zip utility also
extracts empty folders.
You can extract the installer files in the following ways:

Installation DVD. Download the Informatica zip file from the installation DVD to a directory on your
machine and then extract the installer files, or extract the installer files directly from the DVD to a directory
on your machine. If you download the zip file to a directory on your machine, verify the length of the entire
installation directory path, including the zip file name, is 60 characters or less.

FTP download. Download the Informatica installation zip file from the Informatica Electronic Software
Download (END) site to a directory on your machine and then extract the installer files.

Run the Pre-Installation (i9Pi) System Check Tool


Run the Pre-installation (i9Pi) System Check Tool to verify whether the machine meets the system
requirements for installation or upgrade.
1.

Log in to the machine with a system user account.

2.

Close all other applications.

3.

Go to the root of the directory for the installation files and run install.bat as administrator.
To run the file as administrator, right-click the install.bat file and select Run as administrator.
The Informatica 9.6.0 page appears.

4.

Select Install or upgrade Informatica.

Review the Windows Requirements

15

5.

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

6.

Click Start.
The Informatica Pre-Installation (i9Pi) System Check Tool Welcome page appears.

7.

Click Next.
The System Information page appears.

8.

Enter the absolute path for the installation directory.


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

9.
10.

Enter the starting port number for the node that you will create or upgrade on the machine. The default
port number for the node is 6005.
Click Next.
The Database and JDBC Connection Information page appears.

11.

Enter the information for the domain configuration repository database.


The following table describes the database information for the domain configuration repository:
Prompt

Description

Database type

Database for the domain configuration repository. Select Oracle, IBM DB2,
Microsoft SQL Server, or Sybase ASE.

Database user ID

User ID for the database user account for the domain configuration repository.

Database user
password

Password for the database user account.

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

Enter the JDBC connection information.

16

To enter the connection information using the JDBC URL information, select Specify the JDBC
connection properties and specify the JDBC URL properties.
The following table describes the JDBC URL properties:
Property

Description

Database host name

Host name for the database server.

Database port number

Port number for the database server.

Database service name

Service name for Oracle and IBM DB2 databases or database name for
Microsoft SQL Server and Sybase ASE.

Chapter 2: Before You Upgrade the Domain and Server Files

To enter the connection information using a custom JDBC connection string, select Custom JDBC
connection string and type the connection string.
The following list shows the syntax of the JDBC connection string for the databases:
IBM DB2
jdbc:Informatica:db2://host_name:port_no;DatabaseName=
Oracle
jdbc:Informatica:oracle://host_name:port_no;ServiceName=
Microsoft 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 database
system.

13.

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

14.

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 the
database. After the system check is complete, the System Check Summary page appears, displaying
the results of the system check.

15.

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. Resolve
the issue before you proceed 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.txt
16.

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

If the Pre-Installation (i9Pi) System Check Tool finishes with failed requirements, resolve the failed
requirements and run the Pre-Installation (i9Pi) System Check Tool 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, Informatica highly recommends that you
resolve the failed requirements before you proceed.

Back Up the Data Transformation Files


Before you upgrade a new version of Data Transformation, you must back up the Data Transformation files
that were created under previous versions.

Back Up the Data Transformation Files

17

The following table lists the files or directories that you must back up:
File or Directory

Default Location

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

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

Prepare the Domain


Before you upgrade the domain, complete the steps to prepare the domain.

Back Up the Domain


Before 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 install
Informatica.

Informatica infasetup includes command line programs to back up and restore the domain. infasetup is
located in the 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

18

Chapter 2: Before You Upgrade the Domain and Server Files

[<-Force|-f>]
<-DomainName|-dn> domain_name
[<-Tablespace|-ts> tablespace_name (used for IBM DB2 only)]
[<-SchemaName|-sc> schema_name (used for Microsoft SQL Server only)]
[<-TrustedConnection|-tc> trusted_connection (used for 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 directory on each node in the domain.


If you use the same backup directory name on all the nodes, rename
nodemeta.xml before copying it to the backup location. For example, you
back up nodemeta.xml to the /nodebak directory on nodeA and nodeB.
Rename the configuration files so that on nodeA the file is backed up to /
nodebak/nodemeta_A.xml, and on nodeB the file is backed up to /
nodebak/nodemeta_B.xml.

domains.infa

Contains
connectivity
information for the
gateway nodes.

Stored in one of the following locations:


- The Informatica installation directory on the client and server machines.
- The location configured through the INFA_DOMAINS_FILE environment
variable.

Verify Database User Account Requirements


If the domain configuration repository database is on Oracle, set the OPEN_CURSORS parameter to 4000 or
higher.
If the domain configuration repository database is on IBM DB2, set the DynamicSections parameter to 3000
or higher.

Migrate to a Supported Database


If the domain configuration repository is in a database version that is not supported, you must migrate to a
database version that is supported. Migrate the repository in the existing Informatica instance before you
upgrade.
For example, if the domain configuration repository is in a Sybase ASE 15.0.3 database, migrate the
repository to a Sybase ASE 15.7 database.
1.

Shut down all application services in the domain.

2.

Shut down the domain.

3.

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

4.

Restore the domain configuration backup to the database schema.


Run the infasetup RestoreDomain command to restore the domain configuration in the backup file to the
specified database schema.

5.

Update the database connection for each gateway node.


Gateway nodes must have a connection to the domain configuration repository to retrieve and update
domain configuration. When you run the installer on each gateway node, select the option to Allow
changes to the host name and port number. When you select this option you can update the location
of the domain configuration repository.

Prepare the Domain

19

Migrate to a Supported Operating System


If a node is installed on an operating system that is not supported, you must migrate the installation to a
supported operating system before you upgrade.
For example, effective in 9.6.0, Informatica dropped support for 32-bit Linux. If any node in the domain is on
32-bit Linux, you must migrate the installation to a supported operating system before upgrading the node to
9.6.0.
1.

Shut down the node.


To shutdown the node, run the command INFA_HOME/tomcat/bin/infaservice.sh shutdown.

2.

Back up the installation directory, INFA_HOME. If the domain has TLS enabled, backup the keystore
files as well.

3.

Move the installation backup to a supported operating system.

When you upgrade the node on the supported operating system, provide the restored installation, and
choose to allow changes to the node host name and port numbers. After you upgrade the node on the
supported operating system, remove the restored installation directory.

Prepare the PowerCenter Repository


Before you upgrade the domain, back up the PowerCenter repository.
To back up a PowerCenter repository, select the PowerCenter Repository Service in the Administrator tool.
On the Domain actions menu, select Repository Contents > Back Up.

Export the Jaspersoft Resources


If you are upgrading Informatica and you have a Reporting and Dashboards Service, export the Jaspersoft
repository resources before you upgrade the domain.
Verify that the default_master.properties file contains valid data.
1.

When you upgrade from 9.1.0 HotFix 1 or 9.1.0 HotFix 2, navigate to the following directory:
<InformaticaInstallationDir>\jasperreports-server-4.0.1-bin\buildomatic. When you upgrade
from 9.1.0 HotFix 3 or later, navigate to the following directory: <InformaticaInstallationDir>
\jasperreports-server\buildomatic

2.

Export the Jaspersoft repository resources.

If you are upgrading from Informatica 9.5.0 or previous versions, enter the following command to
export the Jaspersoft repository resources:
js-ant export DexportArgs=--roles <role name> --roles-users <user name>
--uris /<Report_Folder_Name> --repository-permissions --report-jobs
--include-access-events -DexportFile=<File_Name>.zip

If you are upgrading from Informatica 9.5.1, enter the following command to export the Jaspersoft
repository resources:
js-ant export DexportArgs=--roles <role name> --roles-users <user name>
--uris /<Report_Folder_Name> --repository-permissions --report-jobs

20

Chapter 2: Before You Upgrade the Domain and Server Files

--include-access-events -DdatabaseUser=<username> -DdatabasePass=<password> DexportFile=<File_Name>.zip


The following table describes the options and arguments in the export command:

3.

Option

Argument

Description

--roles

role name

Comma-separated list of roles that you want to export. If you do


not specify a value, all roles are exported.

--roles-users

user name

Comma-separated list of users that you want to export. If you do


not specify a value, all roles are exported.

--uris

/folder name

Name of the folder in the repository.

--repository-permissions

The permissions associated with the folder that you want to


export.

--report-jobs

The scheduled jobs associated with the reports that you want to
export.

--include-access-events

The access events that you want to export.

-DdatabaseUser

username

User account for the database.

-DdatabasePass

password

Password of the database user account.

Repeat this process for all report folders that you want to export.
Note: After you export the Jaspersoft repository resources in Informatica 9.5.1, add the valid database
user and password in the default_master.properties file.

Prepare the Reporting and Dashboard Service for


Upgrade
Before you upgrade the domain, you need to prepare the Reporting and Dashboard Service.
Before you install Jaspersoft and import repository data from the previous JasperReports Server installation,
ensure that the data source configured is available for the upgrade process.
1.

Ensure that you have exported the Jaspersoft repository resources in the Reporting and Dashboard
Service before you upgrade the domain.

2.

Prepare the Reporting and Dashboard Service.

If you are upgrading from Informatica 9.1.0 HotFix 1 or 9.1.0 HotFix 2, complete the following steps:
1.

Uninstall the Reporting and Dashboard Service.

2.

Navigate to the <InformaticaInstallationDir>\tomcat\temp directory and delete the


Reporting and Dashboards Service <service name> directory.

3.

If the database user name in the Jaspersoft repository is the same in Jaspersoft 4.0.1 and 4.2,
delete the database contents. Instead of using the same database user name, you might want to
use different database user names.

Prepare the Reporting and Dashboard Service for Upgrade

21

4.

On UNIX, assign read and execute permissions on the <InformaticaInstallationDir>/


jasperreports-server directory.

If you are upgrading from Informatica 9.1.0 HotFix 3 or later, and you have a Reporting and
Dashboards Service, complete the following steps:
1.

Disable the Reporting and Dashboard Service.

2.

Navigate to the following directory: <InformaticaInstallationDir>\jasperreports-server


\buildomatic directory.

3.

Add the valid database user and password in the default_master.properties file.

Prepare Metadata Manager


Before you upgrade the domain, prepare Metadata Manager.
1.

Back up the Metadata Manager warehouse.

2.

Export and delete business glossaries.

3.

Disable the Metadata Manager Service.

4.

Back up the Metadata Manager properties file.

Back Up the Metadata Manager Warehouse


Before you upgrade the domain, back up the Metadata Manager warehouse.
Use the native database backup option or the Metadata Manager backupCmdLine command line program to
back up the Metadata Manager warehouse.
Metadata Manager backupCmdLine includes command line programs to back up and restore the Metadata
Manager warehouse. The backupCmdLine command line program is in the following directory:
<InformaticaInstallationDir>\services\MetadataManagerService\utilities\mmBackupUtil
To back up the Metadata Manager warehouse with the backupCmdLine command line program, use the
following syntax:
backupCmdLine.(bat | sh) backup <DBType> "<JDBCConnectionString>" <DBUserName>
<DBPassword> <FileName.bkp>

Export and Delete Business Glossaries


Before you upgrade the domain, you must export and delete business glossaries.

22

1.

Export the Business Glossary model.

2.

Export each business glossary to a Microsoft Excel file.

3.

Update each Microsoft Excel file.

4.

Purge and delete business glossaries.

Chapter 2: Before You Upgrade the Domain and Server Files

Step 1. Export the Business Glossary Model


Before you export business glossaries, export the Business Glossary model. The Analyst tool uses the model
export XML file to create properties that you can add to the business term template.
The Analyst tool extracts attributes for business terms, including attributes in custom classes. It creates a
property for each attribute that does not exist in the business term template by default. It does not extract
custom attributes or usage context for categories.
For example, the business glossary that you export from Metadata Manager contains a custom attribute
called "Citation ID." This attribute does not exist by default in the Analyst tool business term template. When
you import the model export XML file into the Analyst tool after upgrade, the Analyst tool extracts the
"Citation ID" attribute from the model export file. It creates a business term template property called "Citation
ID" that you can add to the business term template.
1.

In Metadata Manager, click the Model tab.

2.

Select Actions > Export Models.


The Export Model dialog box appears.

3.

In the Available Models list, select the Business Glossary model, and click Add.
You do not have to include the rule set definitions.

4.

Click Export.
The options to save the model export XML file depend on the browser.

Step 2. Export Business Glossaries to Microsoft Excel Files


Before you upgrade the domain, export all business glossaries to Microsoft Excel (.xlsx) files. You cannot
export business glossaries after you upgrade.
Export each business glossary that you want to upgrade. You import the business glossary Microsoft Excel
files into the Analyst tool after upgrade.
1.

In Metadata Manager, click the Browse tab.

2.

From the Show list in the Glossary view, select a business glossary.

3.

Click Actions > Export > Glossary to Excel.

Metadata Manager exports the business glossary to a Microsoft Excel file.

Step 3. Update Microsoft Excel Files


After you export business glossaries to Microsoft Excel files, update each Microsoft Excel file, and add a
worksheet that contains the Metadata Manager Service name.
The Analyst tool uses the Metadata Manager Service name to create an internal ID for the business glossary.
If you do not add the worksheet to the Excel file, the Analyst tool sets the Metadata Manager Service name to
"MM."
1.

Open the Microsoft Excel file.

2.

Create a worksheet called MMServiceName.

3.

Enter the name of the Metadata Manager Service in cell A1 of the MMServiceName worksheet.

4.

Save the file.

Prepare Metadata Manager

23

Step 4. Purge and Delete Business Glossaries


Purge business glossary metadata and delete business glossaries from the Metadata Manager repository
before you upgrade.
If you do not purge and delete business glossaries, the business glossaries remain in the Metadata Manager
repository. You can view the business glossaries, but you cannot perform the following tasks:

Add categories or terms.

Export or email glossary metadata.

Synchronize the glossaries with Analyst tool business glossaries because the internal IDs for the previous
and upgraded glossaries are different.

1.

In Metadata Manager, click the Load tab.

2.

Select the business glossary resource for which you want to purge metadata.

3.

Click Actions > Purge Resource Metadata.


Metadata Manager purges the metadata from the Metadata Manager warehouse and displays the result
of the purge operation in the Resources panel.

4.

Click Actions > Delete Resource.


Metadata Manager deletes the business glossary.

Back Up the Metadata Manager Properties File


Before you upgrade the domain, back up the Metadata Manager properties file.
The imm.properties file is in the following directory:
<InformaticaInstallationDir>\services\shared\jars\pc\classes

Prepare Data Analyzer


Before you upgrade the domain, prepare the Data Analyzer repository.
1.

Assign roles to users and groups.

2.

Back up the Data Analyzer repository.

Assign Roles to Users and Groups


Create roles for Reporting Service privileges and assign the roles to users and groups. If you do not use roles
to assign Reporting Service privileges, users and groups lose privilege assignments after you upgrade.

Back Up the Repository


Back up each Data Analyzer repository.
To back up each Data Analyzer repository, select the service in the Administrator tool. Then, on the Domain
Actions menu, click Repository Contents > Backup.

24

Chapter 2: Before You Upgrade the Domain and Server Files

Shut Down the Domain


You 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 >
Stop Informatica Services.

To stop Informatica on UNIX, you use the infaservice command. By default, the infaservice executable file
is installed 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 Configuration


Before you change the node configuration, complete the following steps on the machine where you want the
new version of Informatica to run:
1.

Configure the Windows or UNIX machine.

2.

Copy the installation directory.

3.

Verify the keystore file name and location.

Configure the Windows Machine


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


The installer sets up the ports for components in the Informatica domain, and it designates the ports to use
for application 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 the
application services. Or you can use the default port numbers provided by the installer. Verify that the port
numbers are available on the machines where you install the Informatica services.

Shut Down the Domain

25

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 for incoming connection requests on this port. Client applications use this
port to communicate with the services in the domain. This is the port that the
Informatica command line programs use to communicate to the domain. This is also
the port for the SQL data service JDBC/ODBC driver. Default is 6006.

Service Manager
shutdown port

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

Informatica Administrator
port

Port number used by Informatica Administrator. Default is 6008.

Informatica Administrator
shutdown port

Port number that controls server shutdown for Informatica Administrator. Informatica
Administrator listens for shutdown commands on this port. Default is 6009.

Range of ports for


application services

Range of port numbers that can be assigned to the application service processes
that run on the node. When you create an application service in the domain, the
Service Manager assigns the first available port in this range to the service process.
At a minimum, the number of ports in the range must be at least twice the number of
application service processes that will run on the 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 for
application services after you upgrade.

Create a System User Account


Create a system user account to perform the installation and to run the Informatica service. Verify that the
user account 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
domain account.
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
Log on 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 as a service and Act as operating system permissions. You do not have to log in with this user account
before you install Informatica. During installation, you can specify the user account to run the Informatica
Windows service.

Configure the UNIX Machine


Before you upgrade the domain and server files, complete the following UNIX tasks:
1.

26

Determine port availability.

Chapter 2: Before You Upgrade the Domain and Server Files

2.

Create a system user account.

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

Determine Port Availability


The installer sets up the ports for components in the Informatica domain, and it designates the ports to use
for application 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 the
application services. Or you can use the default port numbers provided by the installer. Verify that the port
numbers 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 for incoming connection requests on this port. Client applications use this
port to communicate with the services in the domain. This is the port that the
Informatica command line programs use to communicate to the domain. This is also
the port for the SQL data service JDBC/ODBC driver. Default is 6006.

Service Manager
shutdown port

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

Informatica Administrator
port

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

Informatica Administrator
shutdown port

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

Range of ports for


application services

Range of port numbers that can be assigned to the application service processes
that run on the node. When you create an application service in the domain, the
Service Manager assigns the first available port in this range to the service process.
At a minimum, the number of ports in the range must be at least twice the number of
application service processes that will run on the 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 for
application services after you upgrade.

Create a System User Account


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


Copy the directory of the previous version of Informatica to the machine where you want the new version of
Informatica to run. For example, if the previous version of Informatica is installed in C:\Informatica\9.1.0,
copy the C:\Informatica\9.1.0 directory and subdirectories to the new machine.
When you run the upgrade installer, specify the Informatica installation directory on the new machine as the
one that you want to upgrade.

Prepare to Change the Node Configuration

27

Verify Keystore File Name and Location


If 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 the domain.
The default location for the keystore file is <InformaticaInstallationDir>/tomcat/conf. The default file
name for the keystore file is Default.keystore.
After you upgrade, you can use infasetup UpdateGatewayNode or UpdateWorkerNode to update the keystore
file name and location.

28

Chapter 2: Before You Upgrade the Domain and Server Files

CHAPTER 3

Domain and Server Files Upgrade


This chapter includes the following topics:

Domain and Server Files Upgrade Overview, 29

Upgrading in Graphical Mode, 31

Upgrading in Console Mode, 34

Upgrading in Silent Mode, 37

Upgrading with Changes to the Node Configuration, 39

Troubleshooting the Domain Upgrade, 51

Domain and Server Files Upgrade Overview


Use the server installer to upgrade the server files and domain of a previous version of PowerCenter. The
server installer provides a domain upgrade wizard to guide you through the upgrade process.
The upgrade wizard installs Informatica 9.6.0 in the installation directory you specify. It does not modify the
files in the directory of the previous version.
The upgrade wizard reads the domain information from files in the previous version and uses the same
settings to configure the domain and server files for Informatica 9.6.0. It upgrades the tables of the domain
configuration repository in the same database as the previous version.
Complete the pre-upgrade tasks before you start the upgrade. Run the installer on all machines that host
previous versions of Informatica that you want to upgrade. On Windows, you can upgrade in graphical or
silent mode. On UNIX, you can upgrade in console or silent mode.
Note: In a multinode domain, upgrade the master gateway node before you upgrade other nodes.
You can perform the upgrade from a DVD or from the root of the directory where you download the
installation files.
On Windows, the length of the entire installation directory path, including the zip file name, must be 60
characters or less. Verify that the zip utility version is compatible with the Windows operating system version.
When you unzip the 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
read and write permissions on the installer files directory and execute permissions on install.sh.

29

Secure Directory for the Encryption Key and Configuration Files


When you install or upgrade Informatica, the installer creates directories to store Informatica files that require
restricted access, such as the domain encryption key file and the nodemeta.xml. On UNIX, the installer
assigns different permissions for the directories and the files in the directories.
By default, the installer creates the following directories within the Informatica installation directory:
<InstallationDir>/isp/config
Contains the nodemeta.xml file. Also contains the /secret directory where the encryption key file is
stored. If you configure the domain to use Kerberos authentication, the /secret directory also contains
the Kerberos keytab files. You can specify a different directory in which to store the files. The installer
assigns the same permissions to the specified directory as the default directory.
<InstallationDir>/services/shared/security
If you enable secure communication for the domain, the /security directory contains the keystore and
truststore files for the default SSL certificates.
The installer assigns the following permissions to the directories and the files in the directories:
Directory Permissions
The owner of the directory has -wx permissions to the directory but no r permission. The owner of the
directory is the user account used to run the installer. The group to which the owner belongs also has wx permissions to the directory but no r permission.
For example, the user account ediqa owns the directory and belongs to the infaadmin group. The ediqa
user account and the infaadmin group have the following permissions: -wx-wx--The ediqa user account and the infaadmin group can write to and run files in the directory. They cannot
display the list of files in directory but they can list a specific file by name.
If you know the name of a file in the directory, you can copy the file from the directory to another
location. If you do not know the name of the file, you must change the permission for the directory to
include the read permission before you can copy the file. You can use the command chmod 730 to give
read permission to the owner of the directory and subdirectories.
For example, you need to copy the encryption key file named siteKey to a temporary directory to make it
accessible to another node in the domain. Run the command chmod 730 on the
<InstallationDir>/isp/config directory to assign the following permissions: rwx-wx---. You can then
copy the encryption key file from the /secret subdirectory to another directory.
After you complete copying the files, change the permissions for the directory back to write and execute
permissions. You can use the command chmod 330 to remove the read permission.
Note: Do not use the -R option to recursively change the permissions for the directory and files. The
directory and the files in the directory have different permissions.
File Permissions
The owner of the files in the directory has rwx permissions to the files. The owner of the files in the
directory is the user account used to run the installer. The group to which the owner belongs also has
rwx permissions to the files in the directory.
The owner and group have full access to the file and can display or edit the file in the directory.
Note: The owner and group must know the name of the file to be able to list or edit the file.

30

Chapter 3: Domain and Server Files Upgrade

Upgrading in Graphical Mode


Use this procedure to upgrade the domain and server files on the same machine. You can upgrade the
domain and server files in graphical mode on Windows. If you install Informatica on the SUSE Linux
Enterprise 11 platform, 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
Upgrading with Changes to the Node Configuration on page 39.
On Windows, if you encounter problems when you run the install.bat file from the root directory, run the
following file:
<InformaticaInstallationDir>/server/install.exe
1.

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

2.

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

3.

Go to the root of the directory for the installation files and run install.bat as administrator.
To run the file as administrator, right-click the install.bat file and select Run as administrator.
The Informatica 9.6.0 page appears.

4.

Select Install or upgrade to Informatica 9.6.0.


Informatica provides utilities to facilitate the Informatica services installation process.

Run the Pre-Installation (i9Pi) System Check tool to verify whether the machine on which you are
upgrading Informatica services meets the system requirements. For more information about the PreInstallation (i9Pi) System Check tool, see Run the Pre-Installation (i9Pi) System Check Tool on
page 15.

You do not have to run the Informatica Kerberos SPN Format Generator before you upgrade to
Informatica 9.6.0. If you plan to configure the Informatica domain with Kerberos authentication after
you upgrade to Informatica 9.6.0, you can use the Informatica command line program to generate the
list of Kerberos principal names and keytab file names required for the Informatica domain.

5.

Click Start.

6.

Select Upgrade to Informatica <Version>.


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

7.

Verify the requirements before you continue the upgrade.

8.

Click Next.

9.

On the Upgrade Directory page, enter the directory of the Informatica version you want to upgrade and
the directory in which you want to install Informatica 9.6.0.

Upgrading in Graphical Mode

31

The following table describes the directories that you must specify:
Directory

Description

Directory of the
Informatica product to
upgrade

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

Directory for Informatica


9.6.0

Directory in which to install Informatica 9.6.0.


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

10.

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

11.

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

12.

Click OK.

13.

Enter the keyword and directory for the encryption key for the Informatica domain.
Informatica uses an encryption key to secure sensitive data, such as passwords, that are stored in the
Informatica domain. When you upgrade a domain with a single node, you must specify a keyword to use
to create an encryption key for the domain.
When you upgrade a domain with multiple nodes, the installer determines the type of node you are
upgrading and displays a different screen based on the type of node. When you upgrade the master
gateway node, you must specify a keyword to create an encryption key for the domain. When you
subsequently upgrade other nodes, you must specify the encryption key created for the domain when
you upgraded the master gateway node.

The following table describes the encryption key parameters that you specify when you upgrade a
domain with a single node or when you upgrade the master gateway node of a multinode domain:
Property

Description

Keyword

Keyword to use to create a custom encryption key to secure sensitive data


in the domain. The keyword must meet the following criteria:
-

Encryption key directory

32

Chapter 3: Domain and Server Files Upgrade

From 8 to 20 characters long


Includes at least one uppercase letter
Includes at least one lowercase letter
Includes at least one number
Does not contain spaces

Directory in which to store the encryption key on the master gateway node.

The following table describes the encryption key parameters that you specify when you upgrade a
node other than the master gateway node:
Property

Description

Select the encryption key

Path and file name of the encryption key for the Informatica domain of the
node that you are upgrading. If you copied the encryption key file to a
temporary directory to make it accessible to the nodes in the domain,
specify the path and file name of the encryption key file in the temporary
directory.

Encryption key directory

Directory in which to store the encryption key on the node that you are
upgrading.

Note: All nodes in an Informatica domain use the same keyword and encryption key. You must keep the
name of the domain, the keyword for the encryption key, and the encryption key file in a secure location.
The encryption key is required when you change the encryption key of the domain or move a repository
to another domain. If you do not have the encryption key, you must have the domain name and the
keyword used to generate the encryption key.
14.

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.6.0 installation directory.

15.

If you are upgrading a gateway node, the upgrade wizard displays the database and user account
information for the domain configuration repository to be upgraded.
If you are upgrading a worker node, the upgrade wizard does not display the domain configuration
repository information. You cannot modify the database connection information.
The following table describes the properties that the installer displays for the domain configuration
repository:
Property

Description

Database type

Database for the domain configuration repository.

Database user ID

Database user account for the domain configuration repository.

User password

Password for the database user account.

The upgrade wizard displays the database connection string for the domain configuration repository
based on how 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
connection properties, including the database address and service name.
Optionally, you can specify additional JDBC parameters to include in the JDBC URL. To provide
additional JDBC 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
displays the custom connection string.
You cannot specify additional JDBC parameters.

16.

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

17.

Click Next.

Upgrading in Graphical Mode

33

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

Select whether to run the Windows service under a different user account.
The following table describes the properties that you set:
Property

Description

Run Informatica under a


different 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\UserAccount
This user account must have the Act as operating system permission.

Password

19.

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

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

20.

Click Done.

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

Upgrading in Console Mode


Use this procedure to upgrade the domain and server files on the same machine. You can upgrade the
Informatica domain and server files in console mode on UNIX.
To upgrade the domain and server files to another machine and modify the node configuration, see
Upgrading with Changes to the Node Configuration on page 39.
When you run the installer in console mode, the words Quit and Back are reserved words. Do not use them
as input text.
1.

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

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 from 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, press n to exit the installer and set them as required.
If the environment variables are set, press y to continue.

5.

34

Press 1 to install or upgrade Informatica.

Chapter 3: Domain and Server Files Upgrade

Informatica provides utilities for facilitate the Informatica upgrade process.

Run the Pre-Installation (i9Pi) System Check tool to verify whether the machine on which you are
upgrading Informatica services meets the system requirements. For more information about the PreInstallation (i9Pi) System Check tool, see Run the Pre-Installation (i9Pi) System Check Tool on
page 10.

You do not have to run the Informatica Kerberos SPN Format Generator before you upgrade to
Informatica 9.6.0. If you plan to configure the Informatica domain with Kerberos authentication after
you upgrade to Informatica 9.6.0, you can use the Informatica command line program to generate the
list of Kerberos principal names and keytab file names required for the Informatica domain.

6.

Press 3 to run the Informatica services installation.

7.

Press y to continue the installation.

8.

Press c for console mode.

9.

Press 2 to upgrade to Informatica 9.6.0.

10.

Press Enter.

11.

At the prompt,enter the directory of the Informatica version you want to upgrade and the directory in
which you want to install Informatica 9.6.0.
The following table describes the directories you must specify:

12.

Directory

Description

Directory of the
Informatica product to
upgrade

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

Directory for Informatica


9.6.0

Directory in which to install Informatica 9.6.0. The directory cannot be the


same as the directory that contains the previous version of PowerCenter.

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
you continue the upgrade.

13.

Press Enter.

14.

Enter the keyword and directory for the encryption key for the Informatica domain.
Informatica uses an encryption key to secure sensitive data, such as passwords, that are stored in the
Informatica domain. When you upgrade a domain with a single node, you must specify a keyword to use
to create an encryption key for the domain.
When you upgrade a domain with multiple nodes, the installer determines the type of node you are
upgrading and displays a different screen based on the type of node. When you upgrade the master
gateway node, you must specify a keyword to create an encryption key for the domain. When you
subsequently upgrade other nodes, you must specify the encryption key created for the domain when
you upgraded the master gateway node.
If the location of the encryption key in the gateway node is not accessible to the current node, copy the
encryption key file to an accessible directory. The name of the encryption key file is siteKey. You might
need to add read permission to the directory that contains the encryption key file before you can copy

Upgrading in Console Mode

35

the file. For more information about the permissions for the encryption key file and directory, see Secure
Directory for the Encryption Key and Configuration Files on page 30.

The following table describes the encryption key parameters that you specify when you upgrade a
domain with a single node or when you upgrade the master gateway node of a multinode domain:
Property

Description

Keyword

Keyword to use to create a custom encryption key to secure sensitive data


in the domain. The keyword must meet the following criteria:
-

Encryption key directory

From 8 to 20 characters long


Includes at least one uppercase letter
Includes at least one lowercase letter
Includes at least one number
Does not contain spaces

Directory in which to store the encryption key on the master gateway node.

The following table describes the encryption key parameters that you specify when you upgrade a
node other than the master gateway node:
Property

Description

Select the encryption key

Path and file name of the encryption key for the Informatica domain of the
node that you are upgrading. If you copied the encryption key file to a
temporary directory to make it accessible to the nodes in the domain,
specify the path and file name of the encryption key file in the temporary
directory.

Encryption key directory

Directory in which to store the encryption key on the node that you are
upgrading.

Note: All nodes in an Informatica domain use the same keyword and encryption key. You must keep the
name of the domain, the keyword for the encryption key, and the encryption key file in a secure location.
The encryption key is required when you change the encryption key of the domain or move a repository
to another domain. If you do not have the encryption key, you must have the domain name and the
keyword used to generate the encryption key.
15.

Review the upgrade information and press Enter to continue.


The installer copies the server files to the Informatica 9.6.0 installation directory.
The installer displays the database and user account information for the domain configuration repository
to upgrade. It displays the database connection string for the domain configuration repository based on
how the connection string of the previous version was created at installation:

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

If the previous version used a custom JDBC connection string at installation, the installer displays the
custom 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
the status of the installed components and their configuration.

36

Chapter 3: Domain and Server Files Upgrade

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

Upgrading in Silent Mode


Use this procedure to upgrade the domain and server files on the same machine.
To upgrade the domain and server files to another machine and modify the node configuration, see
Upgrading with Changes to the Node Configuration on page 39.
To upgrade the Informatica services without user interaction, upgrade in silent mode. Use a properties file to
specify the upgrade options. The installer reads the file to determine the upgrade options. You can use silent
mode upgrade to upgrade the Informatica services on multiple machines on the network or to standardize the
upgrade process across machines.
Copy the Informatica installation files to the hard disk on the machine that hosts the Informatica instance you
plan to 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 File


Informatica provides a sample properties file that includes the upgrade parameters that are required by the
installer. 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 of the installation DVD or the installer download location. After you customize the file, save it with
the file name SilentInput.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 is 1, the installer upgrades a previous version of Informatica.

USER_INSTALL_DIR

Directory in which to install the new version of PowerCenter. The directory


cannot be the same as the directory that contains the previous version of
PowerCenter.

UPG_BACKUP_DIR

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

Upgrading in Silent Mode

37

Property Name

Description

KEY_DEST_LOCATION

Directory in which to store the encryption key for the node created during the
installation.

PASS_PHRASE_PASSWD

Keyword to use to create an encryption key to secure sensitive data in the


domain. The keyword must meet the following criteria:
-

From 8 to 20 characters long


Includes at least one uppercase letter
Includes at least one lowercase letter
Includes at least one number
Does not contain spaces

KEY_SRC_LOCATION

Directory that contains the encryption key for the master gateway node of the
Informatica domain. Set this property when you upgrade a node other than
the master gateway node.

DB2_TABLESPACE

This parameter is obsolete. Do not set it.

ADVANCE_JDBC_PARAM

This parameter is obsolete. Do not set it.

ADVANCE_PORT_CONFIG

This parameter is obsolete. Do not set it.

TOMCAT_PORT

This parameter is obsolete. Do not set it.

SERVER_PORT

Port number that controls server shutdown for the domain Service Manager.
The Service Manager listens for shutdown commands on this port. You can
set this parameter 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
Administrator tool listens for shutdown commands on this port.
You can set this parameter if ADVANCE_PORT_CONFIG=1.

FORCE_UPGRADE
4.

38

This parameter is obsolete. Do not set it.

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

Chapter 3: Domain and Server Files Upgrade

The following table describes the properties that you set:


Property

Description

USE_LOGIN_DETAILS

Indicates whether to run the Windows service under a different user account. If
the value is 0, the installer configures the service to run under the current user
account. If the value is 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
5.

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

Save the properties file with the name SilentInput.properties.

Running the Silent Installer


After 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
complete when 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 not
accessible. If the upgrade fails, view the silent upgrade log file and correct the errors. Then run the silent
installer again. The silent upgrade log file name is silentErrorLog.log. The installer creates it in the root
directory on Windows and in the user home directory on UNIX.

Upgrading with Changes to the Node Configuration


The installer provides the option to allow changes to the node host name and port numbers. Select this
option to upgrade 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 or silent mode. On UNIX, you can run the installer in console or silent mode.

Upgrading in Graphical Mode


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

Upgrading with Changes to the Node Configuration

39

You can upgrade the Informatica domain and server files in graphical mode on Windows. If you upgrade
Informatica on the SUSE Linux Enterprise 11 platform, perform the upgrade in console mode or silent mode.
On Windows, if you encounter problems when you run the install.bat file from the root directory, run the
following file:
<InformaticaInstallationDir>/server/install.exe
1.

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

2.

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

3.

Go to the root of the directory for the installation files and run install.bat as administrator.
To run the file as administrator, right-click the install.bat file and select Run as administrator.
The Informatica 9.6.0 page appears.

4.

Select Install or upgrade to Informatica 9.6.0.


Informatica provides utilities to facilitate the Informatica services installation process.

Run the Pre-Installation (i9Pi) System Check tool to verify whether the machine on which you are
upgrading Informatica services meets the system requirements. For more information about the PreInstallation (i9Pi) System Check tool, see Run the Pre-Installation (i9Pi) System Check Tool on
page 15.

You do not have to run the Informatica Kerberos SPN Format Generator before you upgrade to
Informatica 9.6.0. If you plan to configure the Informatica domain with Kerberos authentication after
you upgrade to Informatica 9.6.0, you can use the Informatica command line program to generate the
list of Kerberos principal names and keytab file names required for the Informatica domain.

5.

Click Start.

6.

Select Upgrade to Informatica <Version>.


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

7.

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

8.

Verify the requirements before you continue the upgrade.

9.

Click Next.

10.

On the Upgrade Directory page, enter the directory of the Informatica version you want to upgrade and
the directory in which you want to install Informatica 9.6.0.
The following table describes the directories you must specify:
Directory

Description

Directory of the
Informatica product to
upgrade

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

Directory for Informatica


9.6.0

Directory in which to install Informatica 9.6.0.


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

11.

40

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

Chapter 3: Domain and Server Files Upgrade

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

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

13.

Click OK.

14.

Enter the keyword and directory for the encryption key for the Informatica domain.
Informatica uses an encryption key to secure sensitive data, such as passwords, that are stored in the
Informatica domain. When you upgrade a domain with a single node, you must specify a keyword to use
to create an encryption key for the domain.
When you upgrade a domain with multiple nodes, the installer determines the type of node you are
upgrading and displays a different screen based on the type of node. When you upgrade the master
gateway node, you must specify a keyword to create an encryption key for the domain. When you
subsequently upgrade other nodes, you must specify the encryption key created for the domain when
you upgraded the master gateway node.

The following table describes the encryption key parameters that you specify when you upgrade a
domain with a single node or when you upgrade the master gateway node of a multinode domain:
Property

Description

Keyword

Keyword to use to create a custom encryption key to secure sensitive data


in the domain. The keyword must meet the following criteria:
-

Encryption key directory

From 8 to 20 characters long


Includes at least one uppercase letter
Includes at least one lowercase letter
Includes at least one number
Does not contain spaces

Directory in which to store the encryption key on the master gateway node.

The following table describes the encryption key parameters that you specify when you upgrade a
node other than the master gateway node:
Property

Description

Select the encryption key

Path and file name of the encryption key for the Informatica domain of the
node that you are upgrading. If you copied the encryption key file to a
temporary directory to make it accessible to the nodes in the domain,
specify the path and file name of the encryption key file in the temporary
directory.

Encryption key directory

Directory in which to store the encryption key on the node that you are
upgrading.

Note: All nodes in an Informatica domain use the same keyword and encryption key. You must keep the
name of the domain, the keyword for the encryption key, and the encryption key file in a secure location.
The encryption key is required when you change the encryption key of the domain or move a repository
to another domain. If you do not have the encryption key, you must have the domain name and the
keyword used to generate the encryption key.
15.

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

Upgrading with Changes to the Node Configuration

41

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

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

17.

Click Next.
The installer displays the domain and node properties.

18.

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

Description

Domain name

Name of the domain. The default domain name is Domain_<MachineName>.


The name must not exceed 128 characters and must be 7-bit ASCII only. It
cannot contain a space or 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 a single network name, use the default host name. If the
machine has multiple network names, 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 is 6005.

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

19.

Port number of the gateway node.


Available if you upgrade a worker node.

If you are securing the Informatica Administrator with 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 Informatica Administrator custom keystore:

20.

Property

Description

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
installer looks for the keystore file in the following directory:
<InformaticaInstallationDir>\tomcat\conf\

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

21.

42

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

Chapter 3: Domain and Server Files Upgrade

The following table describes the ports that you can specify:

22.

Port

Description

Service Manager port

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

Service Manager
shutdown port

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

Informatica Administrator
port

Port number used by the Administrator tool.

Informatica Administrator
shutdown port

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

Available if you upgrade a gateway node.

Available if you upgrade a gateway node.

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

23.

Select whether to run the Windows service under a different user account.
The following table describes the properties that you set:
Property

Description

Run Informatica under a


different 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\UserAccount
This user account must have the Act as operating system permission.

Password

24.

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

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

25.

Click Done.

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

Upgrading in Console Mode


Use 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 34.
You can upgrade the Informatica domain and server files in console mode on UNIX.

Upgrading with Changes to the Node Configuration

43

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

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

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 from 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, press n to exit the installer and set them as required.
If the environment variables are set, press y to continue.

5.

Press 1 to install or upgrade Informatica.


Informatica provides utilities for facilitate the Informatica upgrade process.

Run the Pre-Installation (i9Pi) System Check tool to verify whether the machine on which you are
upgrading Informatica services meets the system requirements. For more information about the PreInstallation (i9Pi) System Check tool, see Run the Pre-Installation (i9Pi) System Check Tool on
page 10.

You do not have to run the Informatica Kerberos SPN Format Generator before you upgrade to
Informatica 9.6.0. If you plan to configure the Informatica domain with Kerberos authentication after
you upgrade to Informatica 9.6.0, you can use the Informatica command line program to generate the
list of Kerberos principal names and keytab file names required for the Informatica domain.

6.

Press 3 to run the Informatica service installation.

7.

Press y to continue the installation.

8.

Enter c for console mode.

9.

Press 2 to upgrade to Informatica 9.6.0.

10.

Press Enter.

11.

At the prompt, enter the directory of the Informatica version you want to upgrade and the directory in
which you want to install Informatica 9.6.0.
The following table describes the directories you must specify:

12.

Directory

Description

Directory of the
Informatica product to
upgrade

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

Directory for Informatica


9.6.0

Directory in which to install Informatica 9.6.0. The directory cannot be the


same as the directory that contains the previous version of PowerCenter.

If you migrated from another server, provide the path to the restored backup.

Enter 2 to allow changes to the node host name and port number. Select this option if you migrated to a
different server.
The installer displays a warning to shut down the Informatica domain that you want to upgrade before
you continue the upgrade.

44

13.

Press Enter.

14.

Enter the keyword and directory for the encryption key for the Informatica domain.

Chapter 3: Domain and Server Files Upgrade

Informatica uses an encryption key to secure sensitive data, such as passwords, that are stored in the
Informatica domain. When you upgrade a domain with a single node, you must specify a keyword to use
to create an encryption key for the domain.
When you upgrade a domain with multiple nodes, the installer determines the type of node you are
upgrading and displays a different screen based on the type of node. When you upgrade the master
gateway node, you must specify a keyword to create an encryption key for the domain. When you
subsequently upgrade other nodes, you must specify the encryption key created for the domain when
you upgraded the master gateway node.
If the location of the encryption key in the gateway node is not accessible to the current node, copy the
encryption key file to an accessible directory. The name of the encryption key file is siteKey. You might
need to add read permission to the directory that contains the encryption key file before you can copy
the file. For more information about the permissions for the encryption key file and directory, see Secure
Directory for the Encryption Key and Configuration Files on page 30.

The following table describes the encryption key parameters that you specify when you upgrade a
domain with a single node or when you upgrade the master gateway node of a multinode domain:
Property

Description

Keyword

Keyword to use to create a custom encryption key to secure sensitive data


in the domain. The keyword must meet the following criteria:
-

Encryption key directory

From 8 to 20 characters long


Includes at least one uppercase letter
Includes at least one lowercase letter
Includes at least one number
Does not contain spaces

Directory in which to store the encryption key on the master gateway node.

The following table describes the encryption key parameters that you specify when you upgrade a
node other than the master gateway node:
Property

Description

Select the encryption key

Path and file name of the encryption key for the Informatica domain of the
node that you are upgrading. If you copied the encryption key file to a
temporary directory to make it accessible to the nodes in the domain,
specify the path and file name of the encryption key file in the temporary
directory.

Encryption key directory

Directory in which to store the encryption key on the node that you are
upgrading.

Note: All nodes in an Informatica domain use the same keyword and encryption key. You must keep the
name of the domain, the keyword for the encryption key, and the encryption key file in a secure location.
The encryption key is required when you change the encryption key of the domain or move a repository
to another domain. If you do not have the encryption key, you must have the domain name and the
keyword used to generate the encryption key.
15.

Review the upgrade information and press Enter to continue.


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

Upgrading with Changes to the Node Configuration

45

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

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

If the previous version used a custom JDBC connection string at installation, the installer displays the
custom 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:
Property

Description

Domain name

Name of the domain. The default domain name is Domain_<MachineName>.


The name must not exceed 128 characters and must be 7-bit ASCII only. It
cannot contain a space or 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 a single network name, use the default host name. If the
machine has multiple network names, 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 if you are securing the Informatica Administrator with a custom
keystore file and you are upgrading to a different gateway node configuration.

Custom keystore file

Path and file name of the custom keystore file. Enter the custom keystore file
if you are securing the Informatica Administrator with a custom keystore file
and you are upgrading to a different gateway node configuration.
If you leave this field blank, the installer looks for the keystore file in the
following directory:
<InformaticaInstallationDir>\tomcat\conf\

Node port number

Port number for the node you are upgrading. The default port number for the
node is 6005.

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

20.

46

Port number of the gateway node.


Available if you upgrade a worker node.

The installer displays the port numbers assigned the domain components.

Chapter 3: Domain and Server Files Upgrade

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
the Informatica command line programs use this port to communicate to the
services in the domain.

Service Manager
shutdown port

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

Informatica Administrator
port

Port number used by the Administrator tool.

Informatica Administrator
shutdown port

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

Available if you upgrade a gateway node.

Available if you upgrade a gateway node.

The Post-Installation Summary window indicates whether the upgrade completed successfully. It also shows
the status 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
and to view the configuration properties for the installed components.

Upgrading in Silent Mode


Use 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 37.
To upgrade the Informatica services without user interaction, upgrade in silent mode. Use a properties file to
specify the upgrade options. The installer reads the file to determine the upgrade options. You can use silent
mode upgrade to upgrade the Informatica services on multiple machines on the network or to standardize the
upgrade process across machines.
Copy the Informatica installation files to the hard disk on the machine that hosts the Informatica instance you
plan to 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 File


Informatica provides a sample properties file that includes the upgrade parameters that are required by the
installer. You can customize the sample properties file to specify the options for your upgrade.
The sample upgrade properties file is named SilentInput_Upgrade_NewConfig.properties and is located in
the root directory of the installation DVD or the installer download location. After you customize the file, save
it with the file name SilentInput.properties.
1.

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

2.

Find the file named SilentInput_Upgrade_NewConfig.properties.


Back up the file before you modify it.

Upgrading with Changes to the Node Configuration

47

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:
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, set this parameter to 1.

USER_INSTALL_DIR

Directory in which to install Informatica the new version of


Informatica. The directory cannot 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 to upgrade.

KEY_DEST_LOCATION

Directory in which to store the encryption key for the node


created during the installation.

PASS_PHRASE_PASSWD

Keyword to use to create an encryption key to secure


sensitive data in the domain. The keyword must meet the
following criteria:
-

KEY_SRC_LOCATION

Directory that contains the encryption key for the master


gateway node of the Informatica domain. Set this property
when you upgrade a node other than the master gateway
node.

DB_TYPE

Database for the domain configuration repository. The value


can be one of the following databases:
-

48

From 8 to 20 characters long


Includes at least one uppercase letter
Includes at least one lowercase letter
Includes at least one number
Does not contain spaces

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

This parameter is obsolete. Do not set it.

SQLSERVER_SCHEMA_NAME

For Microsoft SQL Server. Name of the schema that will


contain domain configuration tables. If this parameter is
empty, the installer creates the tables in the default schema.

Chapter 3: Domain and Server Files Upgrade

Parameter Name

Description

TRUSTED_CONNECTION

For Microsoft SQL Server. Indicates whether to connect to


Microsoft SQL Server through a trusted connection. If this
parameter is empty, the installer uses Microsoft SQL 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 to the domain configuration
repository database.
If the value is 0, the installer creates a JDBC URL from the
database properties you provide. 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 SQL Server.

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

This parameter is obsolete. Do not set it.

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 machine has a single network name, use
the default host name. If the machine has multiple network
names, 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.

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 are securing the Informatica
Administrator with a custom keystore file and you are
upgrading to a different gateway node configuration.
If you leave this field blank, the installer looks for the
keystore file in the following directory:
<InformaticaInstallationDir>\tomcat\conf\

Upgrading with Changes to the Node Configuration

49

Parameter Name

Description

CUSTOM_KEYSTORE_PSSWD_UPGRADE

Plain text password for the custom keystore file. Enter the
custom keystore password if you are securing the
Informatica Administrator with a custom keystore file and
you are upgrading to a different gateway node configuration.

ADVANCE_PORT_CONFIG

This parameter is obsolete. Do not set it.

TOMCAT_PORT

This parameter is obsolete. Do not set it.

SERVER_PORT

You can set this parameter if ADVANCE_PORT_CONFIG=1.


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

4.

AC_PORT

Port number used by the Administrator tool.

AC_SHUTDWN_PORT

Port number that controls server shutdown for the


Administrator tool. The Administrator tool listens for
shutdown commands on this port.

FORCE_UPGRADE

This parameter is obsolete. Do not set it.

On Windows, specify whether to run the Informatica service under the same user account as the account
used for upgrade.
The following table describes the properties that you set:
Property

Description

USE_LOGIN_DETAILS

Indicates whether to run the Windows service under a different user account. If
the value is 0, the installer configures the service to run under the current user
account. If the value is 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

5.

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

Save the properties file with the name SilentInput.properties.

Running the Silent Installer


After you create the properties file, open a command window to start the silent upgrade.

50

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.

Chapter 3: Domain and Server Files Upgrade

The silent upgrade runs in the background. The process can take a while. The silent upgrade process is
complete when 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 not
accessible. If the upgrade fails, view the silent upgrade log file and correct the errors. Then run the silent
installer again. The silent upgrade log file name is silentErrorLog.log. The installer creates it in the root
directory on Windows and in the user home directory on UNIX.

Troubleshooting the Domain Upgrade


If the upgrade does not complete successfully, review log files to determine the cause of the failure. The
upgrade log files are in the root of the directory where the new version of Informatica is installed. Review the
following log file: Informatica_<Version>_Services_Upgrade.log.
If the upgrade fails, restore the domain configuration repository database from backup and run the installer
again.
If the machine uses HTTPS to connect to Informatica Administrator and you receive a 404 Not Found
message when you try to connect to the domain, verify that the Default.keystore file is in the following
default location for the keystore file: <InformaticaInstallationDir>/tomcat/conf. If the Default.kestore file
is not in the default location, stop the Informatica services, copy the file from the backup location to the
default location, and then restart the Informatica services.

Troubleshooting the Domain Upgrade

51

CHAPTER 4

Before You Upgrade the


Application Services
This chapter includes the following topics:

Pre-Upgrade Tasks, 52

Configure POSIX Asynchronous I/O, 52

Configure Informatica Environment Variables, 53

Configure Locale Environment Variables, 53

Clear Browser Cache, 54

Change the Node Configuration, 54

Pre-Upgrade Tasks
Before you upgrade the application services, complete the following tasks:
1.

Configure POSIX Asynchronous I/O.

2.

Configure Informatica environment variables.

3.

Configure locale environment variables.

4.

Clear browser cache.

5.

Tasks for changing the node configuration.

Configure POSIX Asynchronous I/O


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

52

Configure Informatica Environment Variables


You can configure the INFA_DOMAINS_FILE and INFA_HOME environment variables to store the domain
and installation location settings.
INFA_DOMAINS_FILE
The installer creates a domains.infa file in the Informatica installation directory. The domains.infa file
contains the connectivity information for the gateway nodes in a domain, including the domain names,
domain host names, 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.
Configure the INFA_DOMAINS_FILE variable on the machine where you install the Informatica services.
On Windows, configure INFA_DOMAINS_FILE as a system variable.
INFA_HOME
Use INFA_HOME to designate the Informatica installation directory. If you modify the Informatica
directory structure, you need to set the environment variable to the location of the Informatica installation
directory or the 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
so that any Informatica application or service can locate the other Informatica components it needs to
run, set INFA_HOME to the location of the Informatica installation directory.

Configure Locale Environment Variables


Use LANG, LC_CTYPE, or LC_ALL to set the UNIX code page. Verify that the locale setting is compatible
with the code page for the repository. If the locale setting is not compatible with the repository code page,
you cannot create a repository service.
Different UNIX operating systems require different values for the same locale. The value for the locale
variable is case sensitive.
Use the following command to verify that the value for the locale environment variable is compatible with the
language 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 to represent the same locale. For example, utf8, UTF-8, UTF8, and utf-8 represent the
same locale on a Linux machine. Informatica requires that you use a specific value for each locale on a
Linux machine. Make sure 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
with the login. A locale setting consists of the language, territory, and character set. The value of
NLS_LANG depends on the configuration. For example, if the value is american_america.UTF8, set the
variable in a C shell with the following command:
setenv NLS_LANG american_america.UTF8

Configure Informatica Environment Variables

53

Clear Browser Cache


Before you access the Administrator tool, clear the browser cache.
On Windows Internet Explorer, delete the browsing history, including temporary files, cookies, and history.
If you do not clear the browser cache, the previous Administrator tool URL is not redirected to the latest URL
and some menu options may not appear.

Change the Node Configuration


If you chose the option to update the node configuration, before you upgrade the application services, you
must complete 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 Software


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

PowerCenter Integration Service


Depending on the types of databases that the PowerCenter Integration Service will access, install the
following database clients on the machine where the PowerCenter Integration Service runs:

Oracle client

IBM DB2 Client Application Enabler (CAE)

Microsoft SQL Server 2012 Native Client

Sybase Open Client (OCS)

Teradata BTEQ client

PowerCenter Repository Service


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

54

Oracle client

IBM DB2 Client Application Enabler (CAE)

Microsoft SQL Server 2012 Native Client

Sybase Open Client (OCS)

Chapter 4: Before You Upgrade the Application Services

Database Client Environment Variables


Configure database client environment variables on the machines that run PowerCenter Integration Service
and PowerCenter Repository Service processes. The database 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 the
database client.
The following table describes the database environment variables you need to set in UNIX:
Database

Environment Variable
Name

Database
Utility

Oracle

ORACLE_HOME

sqlplus

PATH
IBM DB2

Sybase
ASE

Teradata

DB2DIR

Value

Set to: <DatabasePath>


Add: <DatabasePath>/bin

db2connect

Set to: <DatabasePath>

DB2INSTANCE

Set to: <DB2InstanceName>

PATH

Add: <DatabasePath>/bin

SYBASE15

isql

Set to: <DatabasePath>/sybase<version>

SYBASE_ASE

Set to: ${SYBASE15}/ASE-<version>

SYBASE_OCS

Set to: ${SYBASE15}/OCS-<version>

PATH

Add: ${SYBASE_ASE}/bin:${SYBASE_OCS}/bin:
$PATH

PATH

bteq

Add: <DatabasePath>/bin

Configure Environment Variables


Informatica uses environment variables to store configuration information when it runs the application
services and connects to the clients. Configure the environment variables to meet the Informatica
requirements. Incorrectly configured environment variables can cause the Informatica domain or nodes to fail
to start or can cause connection 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 PowerCenter Integration Service
and PowerCenter Repository Service processes. The library 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.

Change the Node Configuration

55

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

Oracle

<DatabasePath>/lib

IBM DB2

<DatabasePath>/lib

Sybase ASE

${SYBASE_OCS}/lib:${SYBASE_ASE}/lib:${LIBPATH}

Informix

<DatabasePath>/lib

Teradata

<DatabasePath>/lib

ODBC

<CLOSEDODBCHOME>/lib

Java Component Variables


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

Custom transformations that use Java

Java transformations

PowerExchange for JMS

PowerExchange for Web Services

PowerExchange for webMethods

To use these components on AIX, configure the library path environment variable to point to the installed
Java directory. Configure this environment variable on machines where the PowerCenter Integration Service
process runs.

56

Chapter 4: Before You Upgrade the Application Services

The following table describes the library path you configure to use Java-based components:
UNIX Platform

Environment Variable Name

Value

AIX

LIBPATH

JAVA_HOME/java/jre/bin
JAVA_HOME/java/jre/bin/classic
JAVA_HOME/usr/lib:/lib

Verify that a Graphics Display Server is Available


The 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 an X 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:

AIX and Linux. Download and install Xvfb for AIX and Linux.

Solaris. Download and install Xvfb for Solaris. Use the following command to start the virtual frame buffer
and send graphics 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 Numbers


To 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
the minimum and maximum port numbers for service processes in the Advanced Properties section of the
node Properties view.
To update the service process port numbers for a node, configure the following advanced properties:

Minimum Port Number

Maximum Port Number

Verify the Node Backup Directory


Verify that the backup directory for the node is accessible by the node. View the Backup Directory
configuration in the Advanced Properties section of the node Properties view.

Update Keystore File Name and Location


If the node uses HTTPS and you moved the keystore file or renamed the keystore file before you upgraded
the domain, 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.

Change the Node Configuration

57

Configure PowerExchange Adapters


If your previous installation included PowerExchange adapters, configure the PowerExchange adapters on
the machine that runs the new version of Informatica. If the PowerExchange adapter has an installer, reinstall the PowerExchange adapter.

58

Chapter 4: Before You Upgrade the Application Services

CHAPTER 5

Application Service Upgrade


This chapter includes the following topics:

Application Service Upgrade Overview, 59

Service Upgrade Wizard, 59

Application Service Upgrade Overview


The 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 the
dependent services.
Use the service upgrade wizard, the actions menu of each service, or command line to upgrade services. The
service upgrade wizard upgrades multiple services in the appropriate order and checks for dependencies. If
you use the command line to upgrade services, you must upgrade services in the correct order and verify that
you upgrade dependent services.

Service Upgrade for PowerCenter 9.5.1


You must upgrade the PowerCenter Repository Service before you upgrade the Metadata Manager Service.
A user with the Administrator role on the domain, the PowerCenter Repository Service, and the Metadata
Manager Service can upgrade services.
To upgrade services, upgrade the following object types:

PowerCenter Repository Service. Before you upgrade a PowerCenter Repository Service, verify that the
service is enabled.

Metadata Manager Service. Before you upgrade a Metadata Manager Service, verify that the service is
disabled.

Service Upgrade Wizard


Use the service upgrade wizard to upgrade services.

59

The service upgrade wizard provides the following options:

Upgrade multiple services.

Enable services before the upgrade.


Note: The Metadata Manager Service must be disabled before the upgrade. All other services must be
enabled 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 Report
The upgrade report contains the upgrade start time, upgrade end time, upgrade status, and upgrade
processing details. 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 of the service upgrade wizard. If you did not save the upgrade report after upgrading services, you can
select this option to view or save the previous upgrade report.

Running the Service Upgrade Wizard


Use 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
after they have been upgraded.

4.

Click Next.

5.

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

6.

Enter the repository login information.

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 the
service upgrade wizard.

60

10.

Click Close.

11.

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

Chapter 5: Application Service Upgrade

CHAPTER 6

Informatica Client Upgrade


This chapter includes the following topics:

Informatica Client Upgrade Overview, 61

Informatica Client Upgrade Options, 62

Upgrading in Graphical Mode, 62

Upgrading in Silent Mode, 63

Informatica Client Upgrade Overview


Use the client installer to upgrade a previous version of the Informatica client tools. The Informatica client
tools are installed on the installation directory you specify. The client installer configures the newly installed
client tools with the same settings as the previous version. The client installer does not modify the files of the
previous version of the client tools.
Complete the pre-upgrade tasks before you start the upgrade. Run the installer on all machines that host
previous versions of the Informatica client tools that you want to upgrade. You can upgrade the Informatica
clients in graphical or silent mode.
When you run the client installer, select the Informatica client tool to upgrade.
For PowerCenter, you can upgrade the PowerCenter Client tools. PowerCenter Client is a set of tools you
can use to manage the PowerCenter repository, mappings, and sessions. The client upgrade also upgrades
the following client tools:

Custom Metadata Configurator

Mapping Architect for Visio

Mapping Analyst for Excel

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

DataDirect ODBC drivers

Java Runtime Environment libraries

You can perform the upgrade from a DVD or from the root of the directory where you download the
installation files.
On Windows, the length of the entire installation directory path, including the zip file name, must be 60
characters or less. Verify that the zip utility version is compatible with the Windows operating system version.
When you unzip the file, verify that the zip utility also extracts empty folders.

61

Informatica Client Upgrade Options


You 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
you through the upgrade process.

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

Upgrading in Graphical Mode


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

On the Installation Type page, select Upgrade to Informatica 9.6.0 Clients and click Next.

4.

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

5.

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 Data
Transformation Studio. If you do not have Data Transformation installed, upgrading Informatica
Developer installs Data Transformation Studio.
6.

Click Next.

7.

On the Select Directory page, enter the directory of the Informatica version you want to upgrade and
the directory in which you want to install Informatica 9.6.0.
The following table describes the directories you must specify:

62

Directory

Description

Directory of the
Informatica client to
upgrade

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

Directory for the


Informatica 9.6.0 client
tools

Directory in which to install the Informatica 9.6.0 client tools.


Enter the absolute path for the installation directory. The installation directory
must be on the current machine. The directory names in the path must not
contain spaces or the following special characters: @|* $ # ! % ( ) { } [ ] , ; '

8.

Click Next.

9.

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

Chapter 6: Informatica Client Upgrade

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

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

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

Upgrading in Silent Mode


To upgrade the Informatica client tools without user interaction, upgrade in silent mode. Use a properties file
to specify the upgrade options. The installer reads the file to determine the upgrade options. You can use
silent mode upgrade to upgrade the Informatica client tools on multiple machines on the network or to
standardize the upgrade process across machines.
Copy the Informatica installation files to the hard disk on the machine that hosts the Informatica client you
plan to 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 File


Informatica provides a sample properties file that includes the upgrade parameters that are required by the
installer. You can customize the sample properties file to specify the options for your upgrade.
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.


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 you can modify:
Property Name

Description

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.

USER_INSTALL_DIR

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

UPG_BACKUP_DIR

Directory of the previous version of the Informatica tools that you want to
upgrade.

Upgrading in Silent Mode

63

Property Name

Description

DXT_COMP

Indicates whether to install Informatica Developer.


If the value is 1, the Developer tool will be installed. If the value is 0, the
Developer 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,
the PowerCenter Client will not be installed.
Default is 1.

DT_COMP

Indicates whether to install Data Transformation Studio.


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
copy of Eclipse that is bundled with the installer or use an Eclipse
development environment that is already installed on your machine.
If the value is 0, the installer uses the Eclipse development environment
that is already 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
the installer.
Default is 1.

ECLIPSE_LOCATION

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

4.

Save the properties file.

Running the Silent Installer


After you create the properties file, open a command window to start the silent upgrade.
1.

Open a command window.

2.

Go to root of the client 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
complete when 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 not
accessible. If the upgrade fails, view the installation log files and correct the errors. Then run the silent
installer again.

64

Chapter 6: Informatica Client Upgrade

CHAPTER 7

After You Upgrade


This chapter includes the following topics:

Informatica Domain, 65

PowerCenter Integration Service, 66

Business Glossary Desktop, 66

Search Service, 67

Business Glossaries, 67

Metadata Manager Service, 68

Metadata Manager Agent, 70

Reporting and Dashboards Service, 71

Changing to Kerberos Authentication after Upgrade, 71

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

Configure LDAP Connectivity


If 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, which
indicated 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 in
reverse 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 Directory


When you upgrade the domain, the log events directory points to the location you specified in the previous
version. When you upgrade the domain with changes to the node configuration, the log events directory
points to the 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
Administrator tool. You can also use infasetup updateGatewaynode to update the directory. For example, you
can configure the log events directory as the server/infa_shared/logs directory in the new installation
directory.
65

Update ODBC Data Sources


The Informatica installation includes DataDirect 7.1 ODBC drivers. Re-create each ODBC data source to use
the new drivers.

Remove Migrated Installation Directory


If you migrated the node to a supported operating system, you restored the directory from the previous
installation. After you upgrade the node, remove the restored installation directory.

PowerCenter Integration Service


After you upgrade, complete the post-upgrade task for the PowerCenter Integration Service.

Configure Umask for Operating System Profiles


If you upgraded from a version that used operating system profiles, set the umask setting to change the
security on files that the DTM writes.
For example, you can change umask to 077 for maximum security. You must restart Informatica services if
you change the umask setting.

Business Glossary Desktop


Change the Business Glossary Desktop application port number to reference glossaries on a machine that
hosts the Analyst Service.

Changing the Business Glossary Desktop Port Number


Change the port number in the Business Glossary Desktop server settings to establish a connection to the
business glossary on the machine on which the Analyst Service runs.
1.

In the Business Glossary Desktop application, click Edit > Settings.


The Informatica Business Glossary Settings window appears.

66

2.

Click the Server tab.

3.

In the Port field, enter the port number of the machine on which the Analyst Service runs.

4.

Click Test to test the connection to the business glossary.

5.

Click OK.

Chapter 7: After You Upgrade

Search Service
Create the Search Service in the Informatica domain to enable search in the Analyst tool and Business
Glossary Desktop. Start the Search Service after you start the Model Repository Service, Data Integration
Service, and Analyst Service.

Business Glossaries
If you exported business glossaries from Metadata Manager, import the glossaries into the Analyst tool after
you upgrade. Enable the Analyst Service, the Model Repository Service, and the Data Integration Service
before you import the glossaries.
To import business glossaries into the Analyst tool, complete the following tasks:
1.

Create empty glossaries in the Analyst tool.

2.

Import the Metadata Manager model export file.

3.

Add custom attributes to each business term template.

4.

Import business glossary files.

Step 1. Create Glossaries in the Analyst Tool


Create one glossary for each business glossary that you exported from Metadata Manager to a Microsoft
Excel file.
When you create a glossary in the Analyst tool, the glossary name must match the glossary name in the
Parent Glossary column of the Category and BusinessTerm worksheets in the Microsoft Excel file. If the
names do not match, you cannot import the glossary.
1.

In the Analyst tool, open the Glossary workspace.

2.

Click New > Glossary.

3.

Enter the glossary name, optional description, owner, and steward.


The glossary name must match the glossary name in the Parent Glossary column of the Category and
BusinessTerm worksheets in the Microsoft Excel file.

4.

Click Save > Save and Finish.

Step 2. Import the Metadata Manager Model Export File


You must import the Metadata Manager model export file into the Analyst tool. The Analyst tool uses the
model export file to create properties for attributes that do not exist in the business term template by default.
Use the glossary Import wizard to import the model export XML file. The Import wizard instructs you to import
a Microsoft Excel file, but you can use it to import the model export XML file.
1.

In the Analyst tool, click Open to open the Library workspace.

2.

In the Library Navigator, click the Glossaries section.

3.

Right-click any glossary and click Import.


The Import wizard appears.

Search Service

67

4.

Click Browse and select the model export XML file for the business glossary.
Note: The Import wizard asks you to import a Microsoft Excel (.xlsx) file, but you can select and import
an XML file.

5.

Click Next to import the file.

6.

Click Save.

The Analyst tool adds the attributes to the Business Term Template panel in the Glossary workspace.

Step 3. Add Custom Attributes to Business Term Templates


After you import the model export XML file, update each business term template to include custom attributes
for business terms.
The Analyst tool creates a property for each attribute that does not exist in the business term template by
default. It does not extract custom attributes or usage context for categories.
1.

Open the glossary in which you want to add custom attributes.

2.

Click Edit to edit the glossary.

3.

Click the Business Term Template panel.

4.

In the Available Business Term Template Properties panel, select an attribute that you want to add to
the business term template.
The Analyst tool lists Metadata Manager business term attributes as properties in the All Properties list.

5.

Drag the attribute from the Available Business Term Template Properties panel to the template.

6.

Repeat steps 4 through 5 until you have added all required attributes to the business term template.

7.

Click Save.

Step 4. Import Business Glossary Files


After you create glossaries and update the term templates, import each business glossary file into the Analyst
tool.
1.

In the Analyst tool, open the Library workspace.

2.

In the Library navigator, click Glossaries.

3.

Right-click the glossary and click Import.


The Import wizard appears.

4.

Click Browse and select the Microsoft Excel file that contains the glossary.

5.

Click Next to import the file.


The Analyst tool displays a summary of data in the Microsoft Excel file.

6.

Click Save.

Metadata Manager Service


After you upgrade, complete the following post-upgrade tasks for each Metadata Manager Service:

68

1.

Update the Metadata Manager properties file to include any customization.

2.

Enable the Metadata Manager Service.

Chapter 7: After You Upgrade

3.

Create business glossary resources based on the business glossaries that you imported into the Analyst
tool.

Update the Metadata Manager Properties File


Compare the imm.properties file in the previous installation directory with the 9.6.0 version. Update the 9.6.0
version of the imm. properties file as required.
The 9.6.0 version of the imm.properties file is in the following directory:
<Informatica installation directory>\services\shared\jars\pc\classes
The 9.5.1 version of the imm.properties file is in the following directory:
<9.5.1 InformaticaInstallationDir>\services\shared\jars\pc\classes
The changes take effect when you enable the Metadata Manager Service.

Create Business Glossary Resources


After you upgrade, create business glossary resources in Metadata Manager. Create one resource for each
Analyst tool business glossary that you want to view in Metadata Manager.
Before you log in to Metadata Manager and create Business Glossary resources, clear the browser cache to
ensure that Metadata Manager displays information for the upgraded glossaries only.
Complete the following tasks for each business glossary:
1.

Create a business glossary resource.

2.

Load the resource.

3.

Restore relationship information.

Step 1. Create a Business Glossary Resource


In Metadata Manager, create one business glossary resource for each Analyst tool business glossary that
you want to view in Metadata Manager.
1.

In Metadata Manager, click the Load tab.

2.

Click Actions > New Resource.


The Resource Selection window appears.

3.

Click Business Glossary > Business Glossary.

4.

Click Next.
The Properties page appears.

5.

Enter the glossary name and optional description.

6.

Click Next.
The Configuration page appears.

7.

Enter the connection properties.

8.

Click Test Connection to test the connection to the Analyst tool.


If Metadata Manager cannot connect to the Analyst tool, an error message appears. Correct the error
and test the connection again.

9.

Click Next.
The Enumerated Links window appears.

Metadata Manager Service

69

10.

Optionally, add or upload enumerated links files.

11.

Click Next.
The Schedules window appears.

12.

Optionally, attach a schedule.

13.

Click Finish.

Step 2. Load the Resource


After you create the business glossary resource, load the resource to extract business glossary metadata
from the Analyst tool and load it into the Metadata Manager repository.
1.

In Metadata Manager, click the Load tab.

2.

In the Resources panel, select the business glossary resource that you want to load.

3.

Click Actions > Start Load.


Metadata Manager adds the resource to the load queue, and then starts the load process.

4.

To view the load progress, click Actions > View Load Details.

Step 3. Restore Relationship Information


After you load the business glossary resource, run the mmcmd migrateBGLinks command to restore the
related catalog objects for terms and categories in the glossary.
Run the migrateBGLinks command one time on each business glossary that you exported from a previous
version of Metadata Manager. Do not run this command on business glossaries that you did not export from a
previous version of Metadata Manager.
The command uses the following syntax:
mmcmd migrateBGLinks
[<-dn|--domainName> domainName]
[<-hp|--gateway> gateway_host1:port gateway_host2:port...]
[<-mm|--mmServiceName> mmServiceName]
<<-url> http(s)://<host>:<port>>
<<-u|--user> user>
[-ep|--encryptedPassword]
[<-pw|--password> password]
[<-n|--namespace> namespace]
[<-kt|--keyTab> keyTab]
<<-g|--Glossary> Glossary>
For more information about the mmcmd migrateBGLinks command, see the Informatica PowerCenter
Metadata Manager Administrator Guide.

Metadata Manager Agent


After you complete the post-upgrade tasks for each Metadata Manager Service and configure each Metadata
Manager Service in the Administrator tool, you must uninstall and reinstall each Metadata Manager Agent.
1.

Stop the Metadata Manager Agent.

2.

Reinstall the Metadata Manager Agent so that Metadata Manager can extract metadata from the
metadata sources.

For information about installing the Metadata Manager Agent, see the Informatica PowerCenter Metadata
Manager Administrator Guide.

70

Chapter 7: After You Upgrade

Reporting and Dashboards Service


After you upgrade, complete the post-upgrade tasks for each Reporting and Dashboards Service.

Upgrade to Jaspersoft 4.7


After you upgrade, install or upgrade the Jaspersoft application and assign the iReport Designer license.
Upgrading from Informatica 9.1.0 HotFix 1 or 9.1.0 HotFix 2 to Jaspersoft 4.7
Install the Jaspersoft application. You can run the following command to import the Jaspersoft repository
resource that you exported before you upgraded the domain.
js-ant import DimportFile=<File_Name>.zip -DdatabaseUser=<username> DdatabasePass=<password>
For more information about installing Jaspersoft, see the Informatica Administrator Guide.
Upgrading from Informatica 9.1.0 HotFix 3 or later to Jaspersoft 4.7
Upgrade the Jaspersoft repository with the existing contents on the Actions tab of the Administrator tool.
You can also run the following command to import the Jaspersoft repository resource that you exported
before you upgraded the domain.
js-ant import DimportFile=<File_Name>.zip -DdatabaseUser=<username> DdatabasePass=<password>
Assign the iReport License
1.

Select Start > Informatica > Jaspersoft iReport Designer.

2.

Select Help > License Manager.

3.

Select Install License.

4.

Navigate to the <InformaticaInstallationDir>\clients\iReport-Professional directory and


select the jasperserver.license.

Changing to Kerberos Authentication after Upgrade


You can configure the Informatica domain to use Kerberos authentication to authenticate users, services, and
nodes in a network.
Kerberos is a network authentication protocol which uses tickets to authenticate access to services and
nodes in a network. Kerberos uses a trusted third party arbitrator, known as a Key Distribution Center (KDC),
to validate the identity of users and services and to grant tickets to authenticated user and service accounts.
In the Kerberos protocol, users and services are known as principals. The KDC has a database of principals
and their associated secret keys that are used as proof of identity. Kerberos can use an LDAP directory
service as a principal database.
To use Kerberos authentication, the Informatica domain must be on a network that uses Kerberos
authentication. Informatica services can run on a network that uses Kerberos authentication with Microsoft
Active Directory service as the principal database.
The Informatica domain requires keytab files to authenticate nodes and services in the domain without
transmitting passwords over the network. The keytab files contain the service principal names (SPN) and
associated encrypted keys. Create the keytab files before you create nodes and services in the Informatica
domain.

Reporting and Dashboards Service

71

You can use the Informatica command line programs to change the Informatica domain to use Kerberos
authentication. Ensure that the domain works correctly with Native or LDAP authentication before you change
the domain to use Kerberos authentication.
After you change to Kerberos authentication, you cannot use Native user accounts. Only the user accounts
that you import from the Kerberos principal database into an LDAP security domain are valid in an
Informatica domain that uses Kerberos authentication.
To configure Kerberos authentication for the Informatica domain at the command prompt, perform the
following steps:
1.

Verify that the upgrade is successful and the upgraded domain is working properly.

2.

Verify the Kerberos configuration and copy the configuration file to the Informatica directory.

3.

Create the SPNs and keytab files that are required by the Informatica domain.

4.

Change the Informatica domain to use Kerberos authentication.

5.

Update the nodes in the Informatica domain.

6.

Update the client machines.

7.

Start the Informatica domain and verify that the domain runs with Kerberos authentication properly.

Note: The steps provided are based on the assumption that you have upgraded the Informatica services and
clients successfully. You must verify that the upgrade is complete before you configure the domain to use
Kerberos network authentication. Back up the domain before you change the domain authentication.

Verify the Domain and Service Upgrade


Before you configure the Informatica domain to use Kerberos authentication, verify that the upgraded domain
and services are working properly.
Verify the following components in the domain:

All application service upgrades required for your product are complete. For more information about
upgrading the application services, see Chapter 5, Application Service Upgrade on page 59.
Note: Change the domain authentication only after you have completed the application service upgrade
process. If you change to Kerberos authentication before you upgrade the application services, the
upgrade process can fail.

All domain functionality work as expected. You can enable all upgraded services and run all operations in
the domain.

The domain user accounts have been imported from a Microsoft Active Directory directory service into an
LDAP security domain.
Note: You cannot access or use Native user accounts when the domain uses Kerberos authentication.

The user accounts have the proper groups, privileges, and permissions.

Verify the Kerberos Configuration File


Kerberos stores configuration information in a file named krb5.conf. Informatica requires specific properties in
the Kerberos configuration file to be set so that the Informatica domain can use Kerberos authentication
correctly. You must set the properties in the krb5.conf configuration file.
You might need to request the Kerberos administrator to modify the Kerberos configuration file or send you a
copy of the file.
1.

Edit the krb5.conf file.


Back up the configuration file before you make any changes.

72

Chapter 7: After You Upgrade

2.

In the libdefaults section, set or add the properties required by Informatica.


The following table lists the values to which you must set properties In the libdefaults section:
Property

Value

default_realm

Name of the service realm for the Informatica


domain.

forward

True

forwardable

True

default_tkt_enctypes

Encryption type for the session key in the ticketgranting ticket (TGT). The default value for the
default_tkt_enctypes property in Active Directory is
rc4-hmac.

3.

Save the krb5.conf file.

4.

Copy the file to the Informatica directory.


You must copy the krb5.conf to the following directory: <INFA_HOME>/services/shared/security
If the domain has multiple nodes, copy the krb5.conf to all the nodes in the domain.

The following example shows the content of a krb5.conf with the required properties set:
[libdefaults]
default_realm = AFNIKRB.AFNIDEV.COM
forward = true
forwardable = true
default_tkt_enctypes = rc4-hmac
[realms]
AFNIKRB.AFNIDEV.COM = {
admin_server = SMPL8KERDC01.AFNIKRB.AFNIDEV.COM
kdc = SMPL8KERDC01.AFNIKRB.AFNIDEV.COM
}
[domain_realm]
afnikrb.afnidev.com = AFNIKRB.AFNIDEV.COM
.afnikrb.afnidev.com = AFNIKRB.AFNIDEV.COM
For more information about the Kerberos configuration file, see the Kerberos network authentication
documentation.

Create the Service Principal Names and Keytab Files


Kerberos requires keytab files to authenticate services in the network. You must create keytab files for the
SPNs of the nodes and services in the domain.
The Informatica domain requires SPNs for the services and nodes in the Informatica domain. Keytab files for
the SPN of a node must be available on the machine that hosts the node and service. Keytab files for the
SPN of a service must be available on the node that hosts the service. You must add the SPNs to the
principal database and create the keytab files before you configure the Informatica domain to use Kerberos
authentication.
The Informatica domain requires principal names and keytab file names to follow a specific format. You can
use infacmd to generate a file with the list of SPNs and keytab file names in the Informatica format. The SPN
and keytab file names are case sensitive.

Changing to Kerberos Authentication after Upgrade

73

The Informatica domain requires SPNs in the Kerberos principal database for the following components:
Node
Principal name for the Informatica node that is used to initiate or accept authentication calls.
Informatica Administrator service
Principal name for the Informatica Administrator service that is used to authenticate with other services
in the Informatica domain. The name of the keytab file must be_AdminConsole.keytab.
HTTP process for the Informatica Administrator service.
Principal name for the Informatica Administrator service that the browser uses to authenticate with the
Informatica Administrator service. The name of the keytab file must be webapp_http.keytab.
Principal DN for the LDAP directory service.
Principal name for the bind user DN that is used to search the LDAP directory service. The name of the
keytab file must be infa_ldapuser.keytab.
Service
Principal name for a service in the Informatica domain.
The Informatica domain requires a keytab file for each SPN. You might need to ask the Kerberos
administrator to add the SPNs to the principal database and create the keytab files.
Note: The SPN must be the same as the user principal name (UPN) for any principal that you use in the
Informatica domain. You must also enable delegation for all principals used in the Informatica domain. In the
Microsoft Active Directory Service, set the Trust this user for delegation to any service (Kerberos only)
option.
Informatica provides a command to generate a file that shows the correct format for the SPNs and keytab file
names required in the Informatica domain. To generate a list of SPNs and keytab files in the correct format,
run the following command:
infacmd printSPNAndKeytabNames
The infacmd printSPNAndKeytabNames requires the fully qualified host name for a node. You must run the
command on a machine that can resolve the host name from the domain name system (DNS).
To generate a list of SPNs and keytab files correctly formatted for the Informatica domain, perform the
following steps:
1.

At the command prompt, go to the Informatica directory where the command line programs are installed.
By default, the command line programs are installed in the following directory: <INFA_HOME>/isp/bin

2.

74

Enter infacmd on Windows or infacmd.sh on UNIX followed by the required options and arguments.

Chapter 7: After You Upgrade

The following table describes the options and arguments that are required for the infacmd
printSPNAndKeytabNames command:
Option

Argument

Description

-DomainName

domain_name

Name of the domain. The name must not exceed


128 characters and must be 7-bit ASCII only. The
name cannot contain a space or any of the
following characters: ` % * + ; " ? , < > \ /

-srn

realm
_name_of_node_spn

Name of the Kerberos realm to which the


Informatica domain service belongs. The realm
name must be in uppercase and is case-sensitive.

-Format

format_TEXT_CSV

Format of the file that is generated by the


command. The command can have the following
formats:

-dn

-ServiceRealmName

-fn

- TEXT. File with the SPNs and keytab file names in


separate columns.
- CSV. File with the SPNs and keytab file names
separated by commas.

-OutputFile

output_file_name

Path and file name for the file generated by the


command.

NodeName:HostNam
e
[NodeName:Hostnam
e]

Name of a node and the fully qualified host name


of the machine that hosts the node. Use the
following format: NodeName:HostName

-of
-DomainNodes
-dns

-ServiceProcesses
-sps

ServiceName:Noden
ame
[ServiceName:Noden
ame]

You can generate SPNs and keytab file names for


multiple nodes. Separate each node name and
host name pair with a space.
Name of a service in the Informatica domain and
the name of the node on which the service runs.
Use the following format:
ServiceName:NodeName
You can generate SPNs and keytab file names for
multiple services. Separate each service name and
node name pair with a space.

The command creates a file that contains the list of SPNs and keytab file names in the format required
by the Informatica domain.
3.

Send the file to the Kerberos administrator with a request to add the SPNs to the principal database and
to create a keytab file for each SPN.
Use the ktpass utility provided by Microsoft to create the keytab file. The ktpass utility configures the
user and service principal names for the services in Active Directory and generates .keytab files for the
services.
The Kerberos administrator might take some time to complete this task. You must wait until you receive
the keytab files from the Kerberos administrator before you can change the Informatica domain
authentication.

4.

After the Kerberos administrator creates the keytab files, copy the keytab files to the Informatica
directory.
Copy all keytab files to the directory where the encryption key for the domain is stored. By default,
encryption key is stored in the following directory: <INFA_HOME>/isp/config/secret

Changing to Kerberos Authentication after Upgrade

75

In a domain with multiple nodes, copy the following keytab files to the associated node:

Keytab file for the node.

Keytab files for the services that run on the node.

Change the Domain Authentication to Kerberos Network


Authentication
Run the infasetup command to change the authentication for the Informatica domain to Kerberos network
authentication.
Verify that all domain objects are checked in and back up the domain before you make any changes the
domain authentication.
When you change the domain authentication to Kerberos authentication, you create the following LDAP
security domains:

Internal security domain. The internal security domain is an LDAP security domain with the name
_infaInternalNamespace. The _infaInternalNamespace security domain contains the default administrator
user account created during the change to Kerberos authentication. After the change to Kerberos
authentication, you cannot add users to the _infaInternalNamespace security domain or delete the
security domain.

User realm security domain. The user realm security domain is an empty LDAP security domain with the
same name as the Kerberos user realm. After the change to Kerberos authentication, you can import
users from the Kerberos principal database into the user realm security domain. You cannot delete the
user realm security domain.

You also create an administrator user account. You specify the user name for the administrator user. After
the change to Kerberos authentication, the administrator user account is included in the
_infaInternalNamespace security domain.
To change to Kerberos authentication, run the following command:
infasetup switchToKerberosMode

1.

On a gateway node, run the infasetup command to change the authentication for the domain.
At the command prompt, go to the directory where the Informatica command line programs are located.
By default, the command line programs are installed in the following directory:
<InformaticaInstallationDir>/isp/bin

2.

76

Enter infasetup on Windows or infasetup.sh on UNIX followed by switchToKerberosMode and the


required options and arguments.

Chapter 7: After You Upgrade

The following table describes the options for the switchToKerberosMode command:
Option

Argument

Description

-administratorName

administrator_name

User name for the domain administrator account


that will be created during the change to Kerberos
authentication. The user account must be in the
Kerberos principal database.

-ad

After the change to Kerberos authentication, this


user is included in the _infaInternalNamespace
security domain.
-ServiceRealmName
-srn

realm
_name_of_node_spn

Name of the Kerberos realm to which the


Informatica domain services belong. The realm
name must be in uppercase and is case-sensitive.
The service realm name and the user realm name
must be the same.

-UserRealmName
-urn

realm
_name_of_user_spn

Name of the Kerberos realm to which the


Informatica domain users belong. The realm name
must be in uppercase and is case-sensitive.
The service realm name and the user realm name
must be the same.

The switchToKerberosMode command changes the authentication mode for the domain from native or LDAP
user authentication to Kerberos network authentication.

Update All Nodes in the Domain


Run the infasetup command to update all other nodes in the domain.
Update all gateway and worker nodes with the Kerberos authentication server information except the
gateway node on which you ran the switchToKerberosMode command.
To update the gateway and worker nodes, use the following commands:
infasetup UpdateGatewayNode
Use the UpdateGatewayNode command to set the Kerberos authentication parameters on a gateway
node in the domain. If the domain has multiple gateway nodes, run the UpdateGatewayNode command
on each gateway node.
infasetup UpdateWorkerNode
Use the UpdateWorkerNode command to set the Kerberos authentication parameters on a worker node
in the domain. If the domain has multiple worker nodes, run the UpdateWorkerNode command on each
worker node.
1.

Run the infasetup commands to update nodes.


At the command prompt, go to the directory where the Informatica command line programs are located.
By default, the command line programs are installed in the following directory:
<InformaticaInstallationDir>/isp/bin

2.

Enter infasetup on Windows or infasetup.sh on UNIX followed by UpdateGatewayNode or


UpdateWorkerNode and the required options and arguments.

Changing to Kerberos Authentication after Upgrade

77

The following table describes options for the UpdateGatewayNode or UpdateWorkerNode:


Option

Argument

Description

-EnableKerberos

enable_kerberos

Configures the Informatica domain to use Kerberos


authentication.

realm
_name_of_node_spn

Name of the Kerberos realm to which the


Informatica domain services belong. The realm
name must be in uppercase and is case-sensitive.

-krb
-ServiceRealmName
-srn

The service realm name and the user realm name


must be the same.
-UserRealmName
-urn

realm
_name_of_user_spn

Name of the Kerberos realm to which the


Informatica domain users belong. The realm name
must be in uppercase and is case-sensitive.
The service realm name and the user realm name
must be the same.

Update the Client Machines


Set Informatica and Kerberos environment variables on the machines that host the Informatica clients. You
must also configure the browser to access the Informatica web applications.
After you configure the Informatica domain to run with Kerberos authentication, complete the following postupgrade tasks for the Informatica client tools:
Set the KRB5_CONFIG environment variables with the Kerberos configuration file.
Use the KRB5_CONFIG environment variable to store the path and file name of the Kerberos
configuration file. The name of the Kerberos configuration file is krb5.conf. You must set the
KRB5_CONFIG environment variable on each machine that hosts an Informatica client.
Configure the web browser.
If the Informatica domain runs on a network with Kerberos authentication, you must configure the
browser to allow access to the Informatica web applications. In Microsoft Internet Explorer, add the URL
of the Informatica web application to the list of trusted sites. In Google Chrome, add the host name of the
Informatica web application to the whitelist of trusted sites.

Start the Informatica Domain


After you configure the Informatica domain to run with Kerberos authentication, start the domain and the
Administrator tool. Verify that the Informatica domain correctly runs with Kerberos authentication.
1.

On Windows, you can start the Informatica service from the Control Panel or the Start menu.
To start Informatica from the Windows Start menu, click Programs > Informatica [Version] > Server .
Right-click Start Informatica Services and select Run as Administrator.
On UNIX, run the following command to start the Informatica daemon:
infaservice.sh startup
By default, infaservice.sh is installed in the following directory: <INFA_HOME>/tomcat/bin

2.

78

Start the Informatica Administrator.

Chapter 7: After You Upgrade

Use the following URL to start the Administrator tool: http://<fully qualified hostname>:<http
port>/administrator. If you configured the Administrator tool to use a secure connection, use the
HTTPS protocol and the HTTPS port.
When you start the Administrator tool, you must add the URL to the list of trusted sites for the browser.
3.

Select the security domain for your user account.


If you successfully configured the Informatica domain to use Kerberos authentication, then you can use
single sign on. You do not need to log in to the Administrator tool with a user name and password.

Changing to Kerberos Authentication after Upgrade

79

APPENDIX A

Upgrade Checklist
This appendix includes the following topics:

Upgrade Checklist Overview, 80

Before You Upgrade the Domain and Server Files, 80

Domain and Server Files Upgrade, 81

Before You Upgrade the Application Services, 82

Application Service Upgrade, 82

Informatica Client Upgrade, 83

After You Upgrade, 83

Upgrade Checklist Overview


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

Before You Upgrade the Domain and Server Files


Before you upgrade the domain and server files, perform the following pre-upgrade tasks:

Read the Informatica Release Notes.

Review the operating system specific requirements.


Review the prerequisites and environment variable configuration.

If you have a previous version of Data Transformation installed, back up the essential Data
Transformation files.

Perform the following tasks to prepare the domain:


Back

up the domain.

Verify
If

user account requirements for the domain configuration repository database.

the domain configuration repository is in a database version that is not supported, you must migrate
to a database version that is supported.

80

If

the node is installed on an operating system that is not supported, you must migrate the installation to
a supported operating system.

Prepare the PowerCenter repository.


Back up the PowerCenter repository.

Export the Jaspersoft resources.

Prepare the Reporting and Dashboards Service.


Configure the database user for the Jaspersoft repository.

Prepare Metadata Manager:


Back

up the Metadata Manager warehouse.

Export,

purge, and delete business glossaries.

Disable

the Metadata Manager service.

Back

up the Metadata Manager properties file.

Prepare the Data Analyzer repository.


Assign roles to users and groups and back up the Data Analyzer repository.

Shut down the domain.


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

Prepare to change the node configuration.


Perform the additional pre-upgrade tasks if you choose to change the node configuration.
Review
Copy
Verify

the operating system specific requirements.

the installation directory.


the keystore file name and location.

RELATED TOPICS:

Before You Upgrade the Domain and Server Files on page 5

Domain and Server Files Upgrade


Use the server installer to upgrade the domain and server files. The server installer provides a domain
upgrade wizard 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 files in the directory of the previous version.

Domain and Server Files Upgrade

81

RELATED TOPICS:

Domain and Server Files Upgrade on page 29

Before You Upgrade the Application Services


Before you upgrade application services, perform the following pre-upgrade tasks:

Configure POSIX Asynchronous I/O.


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

Configure Informatica environment variables.

Configure locale environment variables.


Verify that the locale setting is compatible with the code page for the repository.

Clear the browser cache.

If you chose the option to update the node configuration, perform the following tasks:
Install

the database client software.

Configure
Verify

that a graphics display server is available.

Update
Verify

the environment variables.

port numbers.

the location of the node backup directory.

Update

the keystore file name and location.

Configure

PowerExchange Adapters.

RELATED TOPICS:

Before You Upgrade the Application Services on page 52

Application Service Upgrade


Some service versions require a service upgrade. You can use the service upgrade wizard to upgrade
services.
To upgrade application services for PowerCenter 9.5.1, perform the following upgrade tasks:

82

Upgrade each PowerCenter Repository Service.

Upgrade each Metadata Manager Service.

Appendix A: Upgrade Checklist

RELATED TOPICS:

Application Service Upgrade on page 59

Informatica Client Upgrade


Use the client installer to upgrade the client tools. The client tools are installed in the installation directory you
specify. The client installer configures the newly installed client tools with the same settings as the previous
version.

RELATED TOPICS:

Informatica Client Upgrade on page 61

After You Upgrade


After you upgrade the domain, server files, application services, and client files, perform the following postupgrade tasks:

Configure LDAP connectivity.


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

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.

Update ODBC data sources.


The Informatica installation includes new DataDirect ODBC drivers. Re-create each ODBC data source to
use the new drivers.

If you migrated the node to a supported operating system, you restored the directory from the previous
installation. After you upgrade the node, remove the restored installation directory.

If you upgraded from a version that used operating system profiles, set the umask setting to change the
security on files that the DTM writes.

Change the Business Glossary Desktop application port number to the Analyst tool port number to
reference glossaries on a machine that hosts the Analyst Service.

To enable search in the Analyst tool and Business Glossary Desktop, create the Search Service.

If you exported business glossaries from Metadata Manager, import the glossaries into the Analyst tool.

Perform the following post-upgrade tasks for each Metadata Manager Service:
Update

the Metadata Manager properties file to include any customization.

Enable

the Metadata Manager Service.

Create

business glossary resources based on the business glossaries that you imported into the
Analyst tool.

Uninstall and reinstall the Metadata Manager Agent after you configure the Metadata Manager Service.

Informatica Client Upgrade

83

If you use the Reporting and Dashboards Service, upgrade to Jaspersoft 4.7.

To move to Kerberos authentication, perform the following tasks:


Verify

that the upgrade is successful and the upgraded domain is working properly.

Verify

the Kerberos configuration and copy the configuration file to the Informatica directory.

Create

the SPNs and keytab files that are required by the Informatica domain.

Change

the authentication for the Informatica domain to Kerberos network authentication.

Update

the nodes in the domain with the Kerberos authentication server information.

Update

the client machines.

Start

the Informatica domain and verify that the domain runs with Kerberos authentication properly.

RELATED TOPICS:

84

After You Upgrade on page 65

Appendix A: Upgrade Checklist

INDEX

A
AIX
configuring JRE path 56
configuring X Virtual Frame Buffer (Xvfb) 57
Java components 56
LIBPATH 56
authentication
Kerberos 71

installing
file backup before 17
Integration Service
database client 54
isql
testing database connection 55

backing up files
before installation 17
before upgrade 17

Java components
AIX 56
Java transformation
configuring JRE path 56
JRE_HOME
environment variables 7, 14

database client
configuring 55
environment variables 55
databases
testing connections 55
dbs2 connect
testing database connection 55
disk space requirements
installation requirements 6
DISPLAY
environment variables 14
domain
patches and libraries 5
Domain Activity Reporting
setting up on UNIX 57

Kerberos authentication
description 71

E
environment variables
database client 55
installation 7, 14
Java components 56
library path 55
UNIX database client 55

I
IATEMPDIR
environment variables 7, 14
installation requirements
disk space 6
environment variables 7, 14
minimum system requirements 6

L
LANG
locale environment variables 7, 14
LC_ALL
locale environment variables 7, 14
LDAP security domain
description 71
LIBPATH
AIX 56
libraries
required for domain 5
library path
environment variables 7
Linux
configuring X Virtual Frame Buffer (Xvfb) 57
database client environment variables 55
library paths 55

P
patches
required for domain 5
PATH
environment variables 7
PowerExchange for JMS
configuring JRE path 56
PowerExchange for Web Services
configuring JRE path 56
PowerExchange for webMethods
configuring JRE path 56

85

Repository Service
database client 54

UNIX
database client environment variables 55
database client variables 55
library paths 55
user account 27
upgrading
file backup before 17
Service Upgrade Wizard 60
user account
UNIX 27

S
security domains
LDAP 71
Service Upgrade Wizard
upgrading services 60
services
Service Upgrade Wizard 60
Solaris
configuring X Virtual Frame Buffer (Xvfb) 57
sqlplus
testing database connection 55
system requirements
minimum installation requirements 6

86

Index

X
X Virtual Frame Buffer (Xvfb)
installing on UNIX 57