Академический Документы
Профессиональный Документы
Культура Документы
Informatica® PowerCenter®
(Version 8.6.1)
Informatica PowerCenter Installation Guide
Version 8.6.1
January 2009
Copyright (c) 1998–2009 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(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.
The information in this 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, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer,
Informatica B2B Data Exchange and Informatica On Demand 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 © 2007
Adobe Systems Incorporated. All rights reserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All
rights reserved. Copyright © Platon Data Technology GmbH. All rights reserved. Copyright © Melissa Data Corporation. All rights reserved. Copyright © Aandacht c.v. All rights reserved. Copyright
1996-2007 ComponentSource®. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright 2007 Isomorphic Software. All rights reserved. Copyright © Meta Integration Technology,
Inc. All rights reserved. Copyright © Microsoft. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © AKS-Labs. All rights reserved. Copyright © Quovadx, Inc. All rights reserved.
Copyright © SAP. All rights reserved. Copyright 2003, 2007 Instantiations, Inc. All rights reserved. Copyright © Intalio. All rights reserved.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/), software copyright 2004-2005 Open Symphony (all rights reserved) and other software which is
licensed under the Apache License, Version 2.0 (the “License”). You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in
writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the
specific language governing permissions and limitations under the License.
This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software copyright, Red Hat Middleware, LLC,
all rights reserved; software copyright © 1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under the GNU Lesser General Public License Agreement, which may be
found at http://www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, “as-is”, without warranty of any kind, either express or implied, including but 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 (c) 1993-2006, all rights reserved.
This product includes software copyright (c) 2003-2007, Terence Parr. All rights reserved. Your right to use such materials is set forth in the license which may be found at http://www.antlr.org/
license.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.
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.
This product includes Curl software which is Copyright 1996-2007, 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 (C) 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 (c) 2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://
svn.dojotoolkit.org/dojo/trunk/LICENSE.
This product includes ICU software which is copyright (c) 1995-2003 International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software
are subject to terms available at http://www-306.ibm.com/software/globalization/icu/license.jsp
This product includes software copyright (C) 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 (c) 2002 Ralf S. Engelschall, Copyright (c) 2002 The OSSP Project Copyright (c) 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 (c) 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.
The product includes the zlib library copyright (c) 1995-2005 Jean-loup Gailly and Mark Adler.
This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php). 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 Software is protected by U.S. Patent Numbers 6,208,990; 6,044,374; 6,014,670; 6,032,158; 5,794,246; 6,339,775; 6,850,947; 6,895,471; 7,254,590 and other U.S. 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 non-
infringement, 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.
iii
Step 3. Configure PowerCenter Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Step 4. Create a Copy of a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Step 5. Stop Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Creating a System User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Windows User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
UNIX User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Configuring Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
JRE_HOME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Locale Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
X Window Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Clearing Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Version 7.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Version 8.1.1, 8.5.x, or 8.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Setting Up the Keystore File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Using the Keystore File when Upgrading PowerCenter . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Generating a Keystore File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Backing Up and Uninstalling the Web Services Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Stopping Informatica Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
iv Table of Contents
Service Manager Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Troubleshooting Domains and Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Creating the Domain Configuration Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Creating or Joining a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Starting Informatica Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Pinging the Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Adding a License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Troubleshooting the PowerCenter Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Installation Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Table of Contents v
vi Table of Contents
Preface
The Installation Guide is written for the system administrators who are responsible for installing the
PowerCenter product. This guide assumes 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 you are familiar with the interface requirements for your supporting applications.
Informatica Resources
Informatica Customer Portal
As an Informatica customer, you can access the Informatica Customer Portal site at http://my.informatica.com.
The site contains product information, user group information, newsletters, access to the Informatica customer
support case management system (ATLAS), the Informatica How-To Library, the Informatica Knowledge Base,
Informatica Documentation Center, 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 the Informatica Documentation Center from http://my.informatica.com.
vii
Informatica Knowledge Base
As an Informatica customer, you can access the Informatica Knowledge Base at http://my.informatica.com. Use
the Knowledge Base to search for documented solutions to known technical issues about Informatica products.
You can also find answers to frequently asked questions, technical white papers, and technical tips.
North America / South America Europe / Middle East / Africa Asia / Australia
viii Preface
CHAPTER 1
Overview
Use the PowerCenter installer to install PowerCenter for the first time or to upgrade from a previous version.
The following table describes how you can use the installer for installation or upgrade:
Version Task
Installing for the first time Use the installer to perform an installation. Run the PowerCenter installer
and select the option to install PowerCenter.
Upgrading PowerCenter to run a Use the installer to upgrade the PowerCenter 8.1.1, 8.5.x, or 8.6 to run
single version of application version 8.6.1 of application services. You can upgrade PowerCenter to the
services same directory or a different directory.
Upgrading PowerCenter to run Use the installer to upgrade the PowerCenter 8.6 to run version 8.6 and
multiple versions of application 8.6.1 of application services.You must upgrade PowerCenter to a different
services directory. If the PowerCenter domain contains multiple nodes, you must
upgrade a gateway node before you upgrade the worker nodes.
Upgrading from PowerCenter 7.x Use the installer to perform a complete installation. Run the PowerCenter
installer and select the option to install PowerCenter. Then use the
Administration Console to upgrade the PowerCenter Server and
Repository Server. For more information, see the PowerCenter
Configuration Guide.
1
Before you start the installation, verify that your system meets the prerequisites and that you complete the pre-
installation steps.
To install PowerCenter, complete the following tasks:
1. Complete the pre-installation tasks. The pre-installation tasks include verifying prerequisites, creating the
domain configuration database, and setting up a database user. For more information, see “Before You
Install” on page 9.
2. Install PowerCenter. You can install PowerCenter on more than one Windows or UNIX machine. For
more information, see “PowerCenter Installation” on page 23.
3. Install the PowerCenter Client. Install the PowerCenter Client on a Windows machine. For more
information, see “Client Installation” on page 37.
4. Create repositories and configure services. Complete the post-installation and configuration tasks. For
more information, see the PowerCenter Configuration Guide.
You can also install Informatica documentation, PowerCenter and Metadata Manager command line utilities,
and the Informatica Development Platform (IDP).
Upgrading PowerCenter
To upgrade PowerCenter 7.x, use the installer to perform a new installation of PowerCenter and then upgrade
the server and repository in the Administration Console.
Use the installer to upgrade from PowerCenter 8.1.1, 8.5.x, or 8.6. If the PowerCenter domain contains
multiple nodes, you must upgrade each node separately.
You can select the following upgrade options:
♦ Upgrade the node to run a single service version.
♦ Upgrade the node to multiple service versions.
Action Description
Install PowerCenter. Copies directories and files into the installation directory.
Set up the domain. Adds the domain configuration metadata to a database that you specify.
Create or join a domain. Creates a domain and gateway node or creates a node and adds it to a
domain.
Ping the domain. Verifies that the domain you created or are joining is available before it
continues the installation.
Add a license object to the Uses the PowerCenter license key that you enter during installation to
domain. create a license object in the PowerCenter domain.
Action Description
Rename the java directory. Renames the existing /java directory to java_Bak_From_<NewVersion>
and installs new libraries into the new /java directory.
Removes the Windows service. Removes the existing Informatica Services <version> service.
Install PowerCenter. Installs the new version of PowerCenter files and directories in to the
installation directory. Also installs a new version of the Apache Tomcat
server.
Copy infa_shared directory. Copies the infa_shared directory from the backed up server directory into
the new server directory.
Copy nodemeta.xml and creates Copies nodemeta.xml into the new server directory and creates
server.xml. server.xml in the new server directory.
Upgrade domain. Upgrades the domain to run version 8.6.1 application services. The
upgrade creates a new default Administrator account to the domain.
The following table describes the actions that the installer performs when you upgrade PowerCenter to a
different directory:
Tasks Description
Installs PowerCenter. Installs PowerCenter directories and files into the new directory.
Copies infa_shared directory. Copies the infa_shared directory from the existing server directory into
the new server directory.
Copies nodemeta.xml and creates Copies nodemeta.xml into the new server directory and creates
server.xml. server.xml in the new server directory.
Upgrades domain. Upgrades the domain to run version 8.6.1 application services.
- Upgrade from 8.1.1. The upgrade creates a new default Administrator
user account in the domain.
- Upgrade from 8.5.x or 8.6. The upgrade retains the user and
administrator accounts in the domain.
Tasks Description
Installs PowerCenter. Installs PowerCenter directories and files into the new directory.
Keeps the infa_shared directory as Leaves the infa_shared directory in the PowerCenter 8.6 server
is. directory.
Copies nodemeta.xml and creates Copies nodemeta.xml into the new server directory and creates
server.xml. server.xml in the new server directory.
Removes the infacmd and Removes the infacmd and infasetup commands from the PowerCenter
infasetup commands from the 8.6 8.6 directory and replaces them with placeholder files that direct users to
directory run the 8.6.1 version of the commands. You cannot run the 8.6 version of
the infacmd and infasetup commands.
Upgrades domain. The installer upgrades the domain to run version 8.6 and 8.6.1
application services. The upgrade retains the user and administrator
accounts in the domain. If the domain contains a Metadata Manager
Service, Reference Table Manager, Reporting Service, or SAP BW
Service, the installer upgrades all application services in the domain to
version 8.6.1.
Component Description
Informatica Services Starts the Service Manager on a node. Installed as a service on Windows and
as a daemon on UNIX.
Integration Service An application service that extracts, transforms, and loads data to
PowerCenter targets. If Metadata Manager is installed, the Integration Service
extracts and loads metadata based on Metadata Exchange workflows.
Metadata Manager Service An application service that runs the Metadata Manager application in a
PowerCenter domain and manages access to metadata in the Metadata
Manager warehouse.
Reporting Service An application service that runs the Data Analyzer application in a
PowerCenter domain. Use Data Analyzer to create and run reports on data in a
relational database or to run PowerCenter reports.
Web Services Hub An application service that allows client applications to access PowerCenter
workflows as web services.
SAP BW Service An application service that listens for RFC requests from SAP BW, initiates
workflows to extract from or load to SAP BW, and sends log events to the
PowerCenter Log Manager.
Reference Table Manager An application service that runs the Reference Table Manager application in a
Service PowerCenter domain.
PowerCenter Orchestration* Application that models business processes with standard Business Process
Modeling Notation (BPMN). Includes the Orchestration server, Human
Workflow, Administration Console, and run-time repository components.
Java Runtime Environment Required by the Service Manager and some PowerCenter components.
DataDirect ODBC Drivers ODBC drivers used by the Integration Service and the PowerCenter Client.
DataDirect JDBC Drivers JDBC drivers used by the Reporting Service to connect to the Data Analyzer
repository and used by the Metadata Manager Service to verify metadata
source connection information.
* If you have PowerCenter Real Time Edition, configure the Orchestration Server after you install PowerCenter or upgrade
PowerCenter from a previous version. For more information, see the PowerCenter Orchestration Guide.
Component Description
PowerCenter Client Use the PowerCenter Client to define sources and targets, create
transformations and build mappings, and create workflows to run the
mappings.
The PowerCenter Client installation includes the following tools:
- Designer
- Repository Manager
- Workflow Manager
- Workflow Monitor
- Data Stencil
- Custom Metadata Configurator
DataDirect ODBC Drivers ODBC drivers for use with the PowerCenter Client.
Pre-Installation Tasks
The following table describes the pre-installation steps to perform based on your PowerCenter installation
requirements:
9
Upgrade Upgrade Upgrade Upgrade
Install Description
7.x 8.1.1 8.5.x 8.6
Verifying Prerequisites
Step 1. Install
Step 1. Upgrade 7.x
Step 1. Upgrade 8.1.1
Step 1. Upgrade 8.5.x
Step 1. Upgrade 8.6
Verify that you meet the prerequisites to install the PowerCenter services and the PowerCenter Client.
Disk
Component Processor RAM Operating System
Space
Verifying Prerequisites 11
Database Requirements
The following table lists the database requirements for the PowerCenter components:
PowerCenter Disk
Database Type Comments
Component Space
PowerCenter Repository IBM DB2 UDB 35 MB Allocate more space based on the
Microsoft SQL Server amount of metadata you want to store.
Oracle
Sybase ASE
Data Profiling Warehouse IBM DB2 UDB 256 MB Allocate more space based on the
Informix following factors:
Microsoft SQL Server - The amount of data you intend to
Oracle profile.
Sybase ASE - Mode you run profile sessions: verbose
Teradata or normal.
- Types of tables: full or sampling.
- Frequency you purge the Data Profiling
warehouse.
Third-Party
Description
Software
Microsoft Visio 2003 Mapping Architect for Visio allows you to create PowerCenter mapping templates in
Microsoft Office Visio.
Microsoft .NET Mapping Architect for Visio on Windows 2000 requires Microsoft .NET Framework 1.1.
Framework 1.1 Service Pack 1.
Download Microsoft .NET Framework 1.1 from the following web site:
http://msdn2.microsoft.com/en-us/netframework/aa569264.aspx
Download Microsoft .NET Framework 1.1 Service Pack 1 from the following web site:
http://www.microsoft.com/downloads/details.aspx?familyid=A8F56
54F-088E-40B2-BBDB-A83353618B38&displaylang=en
Install the Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1
(KB886903).
If Microsoft Visio and .NET are not available when you install the PowerCenter Client, Mapping Architect for
Visio is not installed. You can run the PowerCenter Client installation again after you install the required third-
party software.
Create a domain configuration database and set up a database user account. The domain configuration database
stores metadata for the domain.
Use the following rules and guidelines when you set up the domain configuration database:
♦ The database must be accessible by all gateway nodes in the PowerCenter domain.
♦ The database code page must be compatible with the code page of the PowerCenter repository and the
Metadata Manager repository.
♦ The PowerCenter installer uses JDBC to communicate with the domain configuration database.
♦ On IBM DB2, make sure the primary tablespace for the domain configuration database has a default page
size of 16k and a temp tablespace size of 16k.
♦ On Sybase ASE, enable the ‘DDL in trans’ option for the database.
Use the following rules and guidelines when you set up a database user account:
♦ The database user account must have permissions to create and drop tables, indexes, and views, and to select,
insert, update, and delete data from tables.
♦ When you create the password for the account, use 7-bit ASCII.
♦ You can store the domain configuration in the same database as the PowerCenter, Metadata Manager, or
Data Analyzer repository if you use the same database user name.
♦ If you create more than one domain, each domain configuration database must have a separate user account.
Note: Write down the database and user account information for reference during the installation.
Complete the following tasks to prepare the PowerCenter domain for upgrade:
♦ Back up the domain configuration database. To back up the domain configuration, use the infasetup
BackupDomain command.
♦ Back up the metadata configuration files. Back up the configuration files to any directory accessible by the
machines where you install PowerCenter.
The following table describes the metadata files and the locations where you can find them:
For each domain you create, establish the number of nodes in the domain and the port numbers available on
each node. The domain and services in the domain must have unique names.
Note for 7.x upgrade: The new domain cannot have the same name as any PowerCenter Server you upgrade.
When you create a domain, verify that it does not use the same name as the PowerCenter Server.
Default
Port Type Description
Value
Node 6001 Port for a gateway node or a worker node in a domain. When you create a
domain, the node port is the gateway port. When you join a domain, the node
port is a worker node port. If you promote a worker node to a gateway node,
the gateway port retains the node port number.
If the node is a gateway node, the Service Manager listens for incoming
connection requests on this port. All client applications use this port to
communicate with the domain.
If the node is a worker node, the Service Manager on the gateway node uses
this port to communicate with the worker node.
To update the port number after the installation, use the infasetup
UpdateGatewayNode or UpdateWorkerNode command.
Application 6005 - 6105 Range of port numbers used by client applications to communicate with the
Service Repository Service, Integration Service, and SAP BW Service processes on
Processes gateway and worker nodes. When the Service Manager starts an application
service, it starts the service process on the first available port in this range.
At a minimum, the range must be equal to the number of application service
processes that will run on the node.
This port range is similar to the PowerCenter Server and Repository Server
port numbers in PowerCenter 7.x.
Service 6002 TCP/IP port used by the Service Manager. The Service Manager listens for
Manager shutdown commands on this port. The installer sets the shutdown port
number to the node port number plus one.
Parameter Value
Node Name
If you are upgrading a repository that has the same name as the domain or that has any of these characters in the
name, back up the repository and restore it using a different name.
Note: To copy or restore a Sybase ASE repository, set allow nulls by default to TRUE at the database level. Set this
option to change the default null type of the column to null in compliance with the SQL standard.
Create a system user account to perform the installation and to run the Informatica Services service or daemon.
Note: When you upgrade PowerCenter, use the same account to upgrade and run the new version as the
accounts that you used to install and run the previous version.
Configure the environment variables before you install the PowerCenter server components. When you upgrade
PowerCenter server components, verify that the environment variables are configured correctly before you start
the upgrade process. When you install PowerCenter, the installer appends variable\folder\files to the PATH
environment variable. Make sure that the length of the PATH environment variable does not meet or exceed the
system limits.
Operating
Variable Description
System
Locale Environment Variables UNIX Use LANG and LC_ALL to set the UNIX code page.
When you configure environment variables on UNIX, create the environment variables with the system user
account you will use for installation:
♦ For new installations, log on with the account you created for the installation. For more information, see
“Creating a System User Account” on page 18.
♦ For upgrades, log on with the account that was used to install the previous version.
JRE_HOME
If you install or upgrade the PowerCenter server components on a machine with 32-bit or 64-bit SUSE Linux
or Linux EMT64 operating system, clear the JRE_HOME environment variable before you start the
installation or upgrade process.
LANG English C
After you install, update the locale setting to one that is compatible with the code page of the repository.
X Window Server
When you install in graphical mode, you must use a graphics display server. On UNIX, the graphics display
server is typically an X Window server. If you do not have the X Window server installed on the machine where
you want to install PowerCenter, you can install PowerCenter using an X Window server installed on another
machine. Use the DISPLAY variable to redirect output of the X Window server to another UNIX machine.
If you do not know the IP address of a UNIX machine where the X Window server is installed, ask your
network administrator. For more information about redirecting the DISPLAY variable, see the documentation
from the UNIX vendor.
If the X Window server does not support the font that the PowerCenter installer uses, the installer can display
incorrect labels on the buttons. For example, the button labeled Test Connection can appear as Test Connecti....
Clear environment variables from previous PowerCenter versions before you install or upgrade.
Note: Incorrectly configured environment variables can cause the PowerCenter domain or nodes to fail to start
or can cause connection problems between the PowerCenter Client and the domain.
Version 7.x
♦ Clear PATH statements. Verify that the existing environment variables do not contain earlier versions of
PowerCenter in the PATH or library path environment variables and that the path does not contain double
quotes.
During installation, you can configure PowerCenter to use SSL certificates for secure communication between
the Administration Console and the Service Manager. The installer can generate a self-signed certificate, or you
can provide a certificate signed by a certification authority. You can use the keytool utility to generate a keystore
file to store the SSL keys and certificates. For more information about the keytool utility, see “Generating a
Keystore File” on page 22.
Note: The installer can set up a secure connection for the Administration Console. To set up a secure connection
for Data Analyzer, Metadata Manager, and the Web Services Hub, use the Administration Console to specify
the keystore files for the Reporting Service, Metadata Manager Service, and the Web Services Hub. For more
information, see the PowerCenter Administrator Guide.
3. Use a text editor to open server.xml and update the attributes for the Connector element.
If the Administration Console uses a secure connection, the connector element contains the keystorePass
and keystoreFile attributes:
<Connector port="PortNumber" scheme="https" secure="true" clientAuth="false"
sslProtocol="TLS" URIEncoding="UTF-8" acceptCount="500" connectionTimeout="40000"
debug="0" disableUploadTimeout="true" enableLookups="false" maxSpareThreads="75"
maxThreads="150" minSpareThreads="25" keystorePass="KeystorePassword"
keystoreFile="AbsolutePathToKeystoreFile" />
Attribute Description
keystoreFile Absolute path and file name for the keystore file.
5. Save server.xml.
If the PowerCenter 7.x installation includes the Web Services Hub, back up the Web Services configuration
before you upgrade. You create and configure a Web Services Hub in the PowerCenter Administration Console
after you install PowerCenter. You cannot upgrade an existing Web Services Hub.
Before you install PowerCenter, complete the following tasks:
♦ Back up the Web Services Hub configuration file. Copy the Web Services Hub configuration file to a
temporary directory. Then use the settings in the configuration file as reference when you create another
Web Services Hub. The configuration file is named WSHConfig.xml and is located in the
WSH_HOME/config directory.
♦ Uninstall the Web Services Provider. After you back up the configuration file, you can uninstall the Web
Services Provider.
Use the settings in the Web Services Hub configuration file of PowerCenter 7.x as reference when you configure
the new Web Services Hub.
Stop Informatica Services on each node in the PowerCenter domain. Shut down each node in the domain to
avoid port conflicts when you install. For more information about stopping Informatica Services, see the
PowerCenter Configuration Guide.
On Windows, set the Startup Type for the Informatica Services service to Manual or Disabled. Otherwise, the
previous version of PowerCenter will start before PowerCenter 8.6.1 if you reboot the machine. For more
information about configuring the Informatica Services service on Windows, see the PowerCenter Configuration
Guide.
Stop all processes that access the PowerCenter directory and subdirectories, including command prompts and
tail logs.
PowerCenter Installation
This chapter includes the following topics:
♦ Overview, 23
♦ Installing in Graphical Mode, 24
♦ Installing in Console Mode, 28
♦ Upgrading in Graphical Mode, 32
♦ Upgrading in Console Mode, 34
Overview
This chapter provides instructions for the following procedures:
♦ Performing a new installation of PowerCenter
♦ Upgrading from PowerCenter 8.1.1, 8.5.x, or 8.6
Note: If you are upgrading from PowerCenter 7.x, you must perform a new installation. After installation,
upgrade the PowerCenter servers in the Administration Console.
Before you start the installation, complete the pre-installation tasks listed in “Before You Install” on page 9.
Run the PowerCenter installer to perform the following tasks:
♦ Install in graphical mode. Install PowerCenter in graphical mode on UNIX or Windows. For more
information, see “Installing in Graphical Mode” on page 24.
♦ Install in console mode. Install PowerCenter in console mode on UNIX. For more information, see
“Installing in Console Mode” on page 28.
♦ Upgrade in graphical mode. Upgrade PowerCenter in graphical mode on UNIX or Windows. For more
information, see “Upgrading in Graphical Mode” on page 32.
♦ Upgrade in console mode. Upgrade PowerCenter in console mode on UNIX. For more information, see
“Upgrading in Console Mode” on page 34.
After you run the installer, complete the steps to install or upgrade PowerCenter components. For more
information, see the steps for your installation or upgrade in “Overview” on page 1.
23
Installing in Graphical Mode
New Installation
Upgrade 7.x
UNIX or Windows
Use this procedure to install PowerCenter 8.6.1 or to upgrade from PowerCenter 7.x.
To install PowerCenter:
1. Verify that your environment meets the minimum system requirements and complete the pre-installation
tasks.
For more information, see “Before You Install” on page 9.
2. Log on to the machine with the user account you want to use to install PowerCenter.
3. Close all other applications.
4. To begin the installation on Windows from a DVD, insert the DVD into the DVD drive. Run install.bat
from the DVD root directory.
-or-
To begin the installation on Windows from a hard disk, run install.bat from the root directory in the
location where you copied the installer.
-or-
To begin the installation on UNIX, use a shell command line to run install.sh from the DVD root directory
or the root directory in the location where you downloaded the installer.
5. On UNIX, select the option for GUI mode installation.
6. Select the language to use during installation and click OK.
The Welcome window introduces the PowerCenter installation.
7. Click Next.
On UNIX, the Configure Environment Variables window appears. Verify that you have configured the
required environment variables. The PowerCenter installer gives you the option to stop the installation and
modify the environment variables. For more information, see “Configuring Environment Variables” on
page 18.
8. Click Next.
The Choose Installation Type window appears.
9. Choose Install PowerCenter 8.6.1
10. Click Next.
The PowerCenter License Key window appears.
11. Enter the location and file name of the PowerCenter license key or click Browse to locate the license key
file.
12. Click Next.
The Installation Prerequisites window displays the platforms and databases you can use and the disk space
requirements. Verify that all PowerCenter installation requirements are met before you continue the
installation. For more information, see “Pre-Installation Tasks” on page 9.
13. Click Next.
The Installation Directory window appears.
Option Description
Use a Keystore Generated by the Select this option to use a self-signed keystore file generated by
Installer the PowerCenter installer. Specify the port number to use.
Use an Existing Keystore File Select this option to use a keystore file you specify. The keystore
file can be self signed or signed by a certification authority. Specify
the port number and the location and password of the keystore.
HTTPS Port Number Port used by the node to communicate between the Administration
Console and the Service Manager.
Keystore Password A plain-text password for the keystore file. Disabled when you use
a keystore generated by the installer.
Keystore File Location Path and file name of the keystore file. You can use a self-signed
certificate or a certificate signed by a certification authority.
Disabled when you use a keystore generated by the installer.
If you use a generated keystore, the installer creates the keystore file in the following directory:
<PowerCenterInstallationDirectory>\server\tomcat\conf
Property Description
Database Type Database for the domain configuration. Select Oracle, Microsoft SQL
Server, Sybase ASE, or IBM DB2.
Database URL Host name and port number for the database instance in the format
<host name>:<port number>.
Database User Password Password for the domain configuration database user account.
Database Service Name Service name for Oracle and IBM DB2 databases or database name for
Microsoft SQL Server or Sybase ASE databases. Use the following
guidelines:
- If you want to use an Oracle SID, you can use the Custom String option.
- If you want to use another database other than the default Sybase ASE
database for the user account, use the Custom String option.
Custom String JDBC connect string. Select the option and enter custom database URL
string.
- To use an Oracle SID instead of an Oracle service name, use the following
JDBC connect string:
jdbc:informatica:oracle://host_name:port;SID=sid
- To specify a non-default Sybase database, use the following JDBC
connect string:
DatabaseName=<name of database>
Tablespace (optional) Name of the tablespace in which to create the repository tables. If blank,
the installation creates the repository tables in the default tablespace.
Define the repository database in a single-node tablespace to optimize
performance. Enabled if you select IBM DB2.
23. Click Test Connection to verify that you can connect to the domain configuration database.
24. Click Next.
The Configure Domain window appears.
25. Enter the following information:
Property Description
Domain Name Name of the PowerCenter domain to create. The domain name must be in
7-bit ASCII format and less than 79 characters. The domain name cannot
contain spaces or the following characters: \ / : * ? > < " |
Note: If you are upgrading from PowerCenter 7.x, the name of the
PowerCenter domain cannot be the same as the name of the PowerCenter
Server in 7.x.
Domain Host Name Host name of the machine on which to create the PowerCenter domain. If
you create a domain on a machine with a single network name, use the
default host name. If you create a domain on a machine with multiple
network names, you can modify the default host name to use an alternate
network name. Optionally, you can use the IP address of the machine on
which to create the domain.
Node Name Node name for the current machine. This is the name of the gateway node
for the domain. This is not the host name for the machine.
Domain Port No. Port number for the current machine. The installer displays a default port
number of 6001. If the port number is not available on the machine, the
installer displays the next available port number.
Domain User Name User name of the domain administrator. Use this name to log in to the
PowerCenter Administration Console. The user name must be less than 79
alphanumeric characters and cannot contain special characters. Do not use
Administrator or administrator as the domain user name. Default is admin.
Domain Password Password for the domain administrator. The password must be between 3
and 16 characters.
To set the range of port numbers for PowerCenter on the node, click Advanced Configuration.
26. Enter the range of port numbers that the PowerCenter installer can use for PowerCenter on the node and
click OK.
The default range for the port numbers is 6005 - 6105.
Skip to step 29.
27. Click Next.
The Configure Domain window appears.
Verify that the gateway node for the domain you want to join is available before you continue.
28. Enter the following information:
Property Description
Domain Host Name Host name or IP address of the gateway node for the domain.
Domain User Name User name for a domain administrator in the PowerCenter domain you want
to join.
Property Description
Run Informatica Services Indicates whether the current Windows user account that installs
with a different user Informatica Services also runs Informatica Services. If selected, enter the
account user name and password of the user account to run Informatica Services.
Use a different account to run Informatica Services if PowerCenter needs to
access a network location not available to the current Windows user
account. You must also use a different account to run Informatica Services
to use a trusted connection for authentication with the PowerCenter
repository database.
If not selected, the current user account that installs Informatica Services
also runs Informatica Services.
User name User account used to run the Informatica Services service. Enter the
Windows domain and user account in the format
<DomainName>\<UserAccount>. This user account must have the Act
as operating system permission. For more information, see “Creating a
System User Account” on page 18.
Password Password for the Windows user account to run Informatica Services.
Use this procedure to install PowerCenter 8.6 or upgrade from PowerCenter 7.x.
To install PowerCenter:
1. Verify that your environment meets the minimum system requirements, and complete the pre-installation
tasks.
For more information, see “Before You Install” on page 9.
2. Log on to the machine as the system user.
3. Close all other applications.
4. On a shell command line, run install.sh located in the root directory of the DVD or the root directory in
the location where you downloaded the PowerCenter installation files.
5. Select the option for Console mode installation.
6. Select the language for installation.
The Welcome panel introduces the PowerCenter installation.
7. Press Enter.
The Configure Environment Variables panel appears.
The installer requires specific environment variable settings. Verify that you have configured the required
environment variables. For more information, see “Configuring Environment Variables” on page 18.
8. If the environment variables are not set, enter quit to exit the installer and set them as required.
-or-
If the environment variables are set, press Enter.
The Choose Installation Type panel appears.
9. Enter 1 to install PowerCenter 8.6.1
The PowerCenter License Key panel appears.
10. Enter the location and file name of the PowerCenter license key and press Enter.
The Installation Prerequisites panel displays the supported platforms and databases and the disk space
requirements. Verify that all PowerCenter installation requirements are met before you continue the
installation. For more information, see “Pre-Installation Tasks” on page 9.
11. Press Enter.
The Installation Directory panel appears.
Option Description
2 - Use a Keystore Generated by the Installer If you generate a keystore, continue to the next step.
3 - Use Existing Keystore File If you use an existing keystore, continue to the next
step.
Prompt Description
HTTPS Port Number Port used by the node to communicate between the Administration Console
and the Service Manager.
Keystore Password A plain-text password for the keystore file. Not available when you use a
keystore generated by the installer.
Keystore File Location Path and file name of the keystore file. You can use a self-signed certificate
or a certificate signed by a certification authority. Not available when you
use a keystore generated by the installer.
If you use a generated keystore, the installer creates the keystore in the following default directory:
<PowerCenter installation directory>/server/tomcat/conf
Option Description
1 - Create New Domain Choose this option if you are installing PowerCenter for the first time or if
you are installing PowerCenter on a single machine. If you create a domain,
continue to the next step.
2 - Join Existing Domain Choose this option if a PowerCenter domain exists on another machine. If
you choose to join a domain, skip to step 25.
Prompt Description
Database type Type of database for the domain configuration. Select from the following
options:
1 - Oracle
2 - DB2
3 - SQLServer
4 - Sybase
20. Select how you want to specify the database connection URL:
Option Description
1 - Default Choose this option to enter the host name, port, user ID, password and
database name.
2 - Custom String Choose this option to enter a user ID, password, and custom JDBC string.
21. Based on your selection, enter the following information at the prompt:
Prompt Description
Database URL Host name and port number for the database instance in the format
<host name>:<port>.
Database password Password for the domain configuration database user account.
Database service Service name for Oracle and IBM DB2 databases or database name for
name Microsoft SQL Server or Sybase ASE databases. Use the following guidelines:
- If you want to use an Oracle SID, you can use the Custom String option.
- If you want to use another database other than the default Sybase ASE
database for the user account, use the Custom String option.
Tablespace (optional) Name of the tablespace in which to create the repository tables. If blank, the
installation creates the repository tables in the default tablespace. Define the
repository database in a single-node tablespace to optimize performance.
Available if you select IBM DB2.
Prompt Description
Domain name Name of the PowerCenter domain to create. The domain name must be in 7-bit
ASCII format and must be less than 79 characters. The domain name cannot
contain spaces or the following characters: \ / : * ? > < " |
Note: If you are upgrading from PowerCenter 7.x, the name of the PowerCenter
domain cannot be the same as the name of the PowerCenter Server in 7.x.
Domain host name Host name of the machine on which to create the PowerCenter domain. If you
create a domain on a machine with a single network name, do not change the
default host name. If you create a domain on a machine with multiple network
names, you can modify the default host name to use an alternate network name.
Optionally, you can use the IP address of the machine on which to create the
domain.
Node name Node name for the current machine. This is the name of the gateway node for
the domain. This is not the host name for the machine.
Domain port no. Port number for the current machine. The installer displays a default port
number of 6001. If the port number is not available on the machine, the installer
displays the next available port number.
Domain user name User name of the domain administrator. Use this name to log in to the
PowerCenter Administration Console. The user name must be less than 79
alphanumeric characters and cannot contain special characters. Do not use
Administrator or administrator as the domain user name. Default is admin.
Domain password Password for the domain administrator. The password must be between 3 and
16 characters.
Property Description
Domain Host Name Host name or IP address of the gateway node for the domain.
Domain User Name User name for a domain administrator in the PowerCenter domain you want to
join.
Use this procedure to upgrade from PowerCenter 8.1.1, 8.5.x, or 8.6. If the PowerCenter domain contains
multiple nodes, upgrade a gateway node before you upgrade the worker nodes.
To upgrade PowerCenter:
1. Verify that your environment meets the minimum system requirements, and complete the pre-installation
tasks.
For more information, see “Before You Install” on page 9.
2. Log on to the machine with the same user account you that you used to install the previous version of
PowerCenter.
If this is the first node you upgrade, verify that it is a gateway node.
3. Close all other applications.
4. To begin the upgrade on Windows from a DVD, insert the DVD into the DVD drive. Run install.bat from
the DVD root directory.
-or-
To begin the upgrade on Windows from a hard disk, run install.bat from the root directory in the location
where you copied the installer.
-or-
To begin the upgrade on UNIX, use a shell command line to run install.sh from the DVD root directory or
the root directory in the location where you downloaded the installer.
5. On UNIX, select the option for GUI mode installation.
6. Select the language to use during installation and click OK.
The Welcome window introduces the PowerCenter installation.
7. Click Next.
On UNIX, the Configure Environment Variables window appears. Verify that you have configured the
required environment variables. The PowerCenter installer gives you the option to stop the installation and
modify the environment variables. For more information, see “Configuring Environment Variables” on
page 18.
8. Click Next.
The Choose Installation Type window appears.
9. Choose Upgrade to PowerCenter 8.6.1.
10. Click Next.
The warning to stop Informatica Services appears. Verify that the Informatica Services service in Windows
or the Informatica Services daemon in UNIX is shut down.
11. Click OK.
Property Description
Run Informatica Indicates whether the current Windows user account that upgrades
Services with a Different Informatica Services also runs Informatica Services. If selected, enter the
User Account user name and password of the user account to run Informatica Services.
Use the same user account to run the upgraded PowerCenter as the account
that ran the previous version.
If not selected, the current user account that installs Informatica Services
also runs Informatica Services.
User name User account used to run the Informatica Services service. Enter the
Windows domain and user account in the format
<DomainName>\<UserAccount>. This user account must have the Act
as operating system permission. For more information, see “Creating a
System User Account” on page 18.
Password Password for the Windows user account to run Informatica Services.
Use this procedure to upgrade from PowerCenter 8.1.1, 8.5.x, or 8.6. If the PowerCenter domain contains
multiple nodes, upgrade a gateway node before you upgrade the worker nodes.
To upgrade PowerCenter:
1. Verify that your environment meets the minimum system requirements, and complete the pre-installation
tasks.
For more information, see “Before You Install” on page 9.
2. Log on to the machine with the same user account you that you used to install the previous version of
PowerCenter.
3. Stop all processes that access the PowerCenter directory and subdirectories, including command prompts
and tail logs.
4. On a shell command line, run install.sh located in the root directory of the DVD or the root directory in
the location where you downloaded the PowerCenter installation files.
5. Select the option for Console mode upgrade.
6. Select the language for installation.
The Welcome panel introduces the PowerCenter upgrade.
7. Press Enter.
The Configure Environment Variables panel appears.
Option Description
1 - Upgrade the node to If you upgrade the node to run a single version of services, you can run only
run a single version of the 8.6.1 version of application services in the domain. You can select this
the application services option if you upgrade from PowerCenter 8.1.1, 8.5.x, or 8.6.
2 - Upgrade the node to If you upgrade the node to run mixed versions of application services, you
run multiple versions of can run 8.6 or 8.6.1 versions of application services in the same domain. You
the application services can select this option if you upgrade from PowerCenter 8.6.
Option Description
1 - Upgrade to Existing Choose this option to install PowerCenter in the same installation directory as
Directory the previous version. If you choose this option, skip to step 20.
If the previous installation directory contains spaces, the installer does not
upgrade into the previous installation directory.
2 - Upgrade to Different Choose this option to install PowerCenter in a different directory. If you choose
Location this option, continue to the next step.
Client Installation
This chapter includes the following topics:
♦ Overview, 37
♦ Installing in Graphical Mode, 38
♦ Installing in Silent Mode, 39
♦ Upgrading in Graphical Mode, 40
♦ Upgrading in Silent Mode, 41
Overview
When you install the PowerCenter Client, you install the following PowerCenter Client tools and components:
♦ PowerCenter Client tools. A set of tools you can use to manage the PowerCenter repository, mappings, and
sessions. The PowerCenter Client installation also includes the Custom Metadata Configurator, the
Orchestration Designer, and Mapping Architect for Visio.
♦ DataDirect ODBC drivers. Drivers designed for PowerCenter and Metadata Manager to connect the
PowerCenter Client to data sources and targets.
♦ Java Runtime Environment. Software that PowerCenter uses for the Java transformation, PowerExchange
for JMS, and PowerExchange for webMethods.
The PowerCenter Client tools requires the Windows operating system.
37
♦ Upgrade in Silent Mode. Upgrades the PowerCenter Client from 8.5 or 8.5.1 to 8.6 using a properties file
that contains the upgrade options. For more information, see “Upgrading in Silent Mode” on page 41.
1. Verify that your environment meets the minimum system requirements, and complete the pre-installation
tasks.
For more information, see “Before You Install” on page 9.
2. Close all other applications before running the installation.
3. To install the PowerCenter Client from the DVD, run the installer from the following location:
<DVD_Root>\install.bat
-or-
To install the PowerCenter Client from a download, run the installer from the following location:
<DownloadLocation>\install.bat
1. If you are installing from the PowerCenter installation DVD, copy the sample properties file from the
DVD to the hard disk.
2. Use a text editor to open and modify the values of the properties in the file.
The following table describes the installation properties to modify:
INSTALLER_UI Installation mode for the installer. Set the value to Silent for silent mode.
CHOSEN_INSTALL_SET Install or upgrade option for the installer. Set the value to Complete.
3. To uninstall the current version of Mapping Architect for Visio and install the 8.6.1 version, add the
following line to the properties file:
VISIO_INSTALL=true
4. Save the properties file on the machine where you install the PowerCenter Client.
Note: Include the absolute path before the installer.properties file. If you do not include the absolute path
for the properties file, the graphical client installation starts.
The silent installer runs in the background. The process may take a while. The silent installation is complete
when the summary_client.htm is created in the installation directory.
The silent installation fails if you incorrectly configure the properties file or if the installation directory is not
accessible. View the installation log files and correct the errors. Then run the silent installation again. For more
information, see “Installation Log Files” on page 46.
1. Verify that your environment meets the minimum system requirements, and complete the pre-installation
tasks.
For more information, see “Before You Install” on page 9.
1. If you are upgrading from the PowerCenter installation DVD, copy the sample properties file from the
DVD to the hard disk.
2. Use a text editor to open the properties file.
3. Modify the values of the properties in the file and set it for upgrade.
The following table describes the properties to modify for upgrade:
INSTALLER_UI Upgrade mode for the installer. Set the value to Silent for silent mode.
USER_INSTALL_DIR PowerCenter Client installation directory. Set this property to the directory
where the previous version of PowerCenter is installed.
Use \\ to separate directories. For example:
C:\\Informatica\\PowerCenter8.6.1
CHOSEN_INSTALL_SET Install or upgrade option for the installer. Set the value to Upgrade.
4. Save the properties file on the machine where you are upgrading the PowerCenter Client.
Troubleshooting a PowerCenter
Installation
This chapter includes the following topics:
♦ Overview, 45
♦ Installation Log Files, 46
♦ Troubleshooting Domains and Nodes, 47
♦ Troubleshooting the PowerCenter Client, 49
♦ Installation Error Messages, 49
Overview
This chapter provides information about the PowerCenter installation process and the cause and resolution of
errors that occur during the installation of PowerCenter. The examples included in this chapter are intended to
describe general troubleshooting strategies and are not a comprehensive list of possible causes of installation
issues.
This chapter provides information on the following topics:
♦ Installation logs. For more information about the logs generated during the PowerCenter installation, see
“Installation Log Files” on page 46.
♦ PowerCenter domain and nodes. For more information about troubleshooting problems related to domain
and node creation, see “Troubleshooting Domains and Nodes” on page 47.
♦ PowerCenter Client. For more information about troubleshooting problems during the PowerCenter Client
installation, see “Troubleshooting the PowerCenter Client” on page 49.
♦ Installation error messages. For more information about the error messages generated by the installer, see
“Installation Error Messages” on page 49.
45
Installation Log Files
You can use the following log files to troubleshoot a PowerCenter installation:
♦ Installation log files. The installer produces log files during and after the installation. You can use these logs
to get more information about the tasks completed by the installation and errors that occurred during
installation. The installation log files include the following logs:
− Debug logs. For more information, see “Debug Log Files” on page 46.
− Summary logs. For more information, see “Summary Log File” on page 46.
− File installation logs. For more information, see “File Installation Log File” on page 47.
♦ Service Manager log files. Log files generated when the Service Manager starts on a node. For more
information, see “Service Manager Log Files” on page 47.
Property Description
Usage Get more information about the actions performed by the installer and get more information about
installation errors. The installer writes information to this file during the installation. If the installer
generates an error, you can use this log to troubleshoot the error.
Contents Detailed summary of each action performed by the installer, the information you entered in the
installer, each command line command used by the installer, and the error code returned by the
command.
The debug log contains output from the infacmd and infasetup commands used to create the domain, node, and
application services. It also contains information about starting the application services. You can find more
information about errors generated by these commands in the PowerCenter Message Reference.
Property Description
Usage Determine the status of the installation and the installed components. Get more information about
properties for the installed components.
Contents Installation status, date, installation set, installation directory, shortcut folder, and configuration
properties. The configuration properties include URLs, user names, and passwords.
Property Description
Usage Get information about files installed and registry entries created.
Contents Directories created, names of the files installed and commands run, and status for each installed file.
Property Description
catalina.out Log events from the Java Virtual Machine (JVM) that runs the Service Manager. For
example, a port is available during installation, but is in use when the Service Manager
starts. Use this log to get more information about which port was unavailable during startup
of the Service Manager.
node.log Log events generated during the startup of the Service Manager on a node. You can use this
log to get more information about why the Service Manager for a node failed to start. For
example, if the Service Manager cannot connect to the domain configuration database after
30 seconds, the Service Manager fails to start.
localhost_log.<date>.txt Internal log events from the Service Manager running on a node. Log events are written to
this file during startup and shutdown of a node.
Note: The Service Manager also uses node.log to record events when the Log Manager is unavailable. For
example, if the machine where the Service Manager runs does not have enough available disk space to write log
event files, the Log Manager is unavailable. For more information, see the PowerCenter Administrator Guide.
Adding a License
The installer runs the infacmd AddLicense command to read the PowerCenter license key file and create a
license object in the domain. To enable the Repository Service and Integration Service in the Administration
Console, a valid license object must exist in the domain.
If you use an incremental license and join a domain, the serial number of the incremental license must match
the serial number for an existing license object in the domain. If the serial numbers do not match, the
AddLicense command fails.
You can get more information about the contents of the license key file used for installation, including serial
number, version, expiration date, operating systems, and PowerCenter and connectivity options in the
installation debug log. You can get more information about existing licenses for the domain in the
Administration Console. For more information, see the PowerCenter Administrator Guide.
Uninstalling PowerCenter
This chapter includes the following topics:
♦ Overview, 53
♦ Running the Uninstaller, 54
♦ Uninstalling in Graphical Mode, 55
♦ Uninstalling in Console Mode, 56
Overview
On UNIX, uninstall PowerCenter from the command line. On Windows, uninstall PowerCenter from the
Windows Start menu.
When you uninstall PowerCenter, files are deleted and all configuration is cleared. The process does not delete
files that are not installed with PowerCenter. For example, the installation process creates temporary directories.
The uninstaller does not keep a record of these directories and therefore cannot delete them. You must manually
delete these directories for a clean uninstallation.
53
− PCSF_REPO_USAGE_SUMMARY
− PCSF_ROLE
− PCSF_RUN_LOG
− PCSF_SOURCE_AND_TARGET_USAGE
− PCSF_USER
To back up the domain configuration database before you remove the metadata tables, use the infasetup
BackupDomain command.
♦ The uninstaller does not create a log of the uninstallation process. At the end of the uninstallation process,
the uninstaller displays the names of the files and directories that could not be removed.
♦ If you install the PowerCenter server component and the PowerCenter Client in the same directory, and then
uninstall the PowerCenter server component, the uninstaller removes the ODBC directory. The ODBC
directory is required by the PowerCenter Client. You must reinstall the PowerCenter server component or
the PowerCenter Client to reinstall the ODBC drivers.
Uninstallation Options
The method you use to uninstall depends on your operating system:
♦ UNIX. Use the console mode interface or graphical mode interface to uninstall PowerCenter.
♦ Windows. Use the graphical mode to uninstall PowerCenter or the PowerCenter Client components.
For more information about using the console mode interface, see “Uninstalling in Console Mode” on page 56.
1. On UNIX, go to the uninstallation directory of the PowerCenter component you want to uninstall and
type the following command to run the uninstaller:
./uninstaller
- or -
On Windows, click Start > Program Files > Informatica PowerCenter [Version] > Services > Uninstaller.
For the list of uninstallation directories, see Table 6-1 on page 54.
The Uninstall PowerCenter window displays information about the uninstallation process.
2. Click Next.
The uninstaller displays the names of the files as they are deleted. When uninstallation completes, the
uninstaller displays the Uninstall Complete window.
If all files are successfully deleted, the Uninstall Complete window displays a message that the
uninstallation was successful.
If not all files are deleted, the Uninstall Complete window displays the list of files that were not deleted.
On Windows, when you uninstall PowerCenter, you must restart the machine to complete the
uninstallation. When you uninstall the PowerCenter Client you do not need to restart.
3. Select to restart immediately or later and click Done.
If the uninstaller does not delete all files, review the files and directories to determine if it is safe to delete them.
Then delete them manually.
Use the -console option if you are running X Window and you want to use console
mode. Otherwise, the uninstaller starts in graphical mode.
3. Press Enter.
After the uninstallation completes, the console displays the results of the uninstallation.
PowerCenter Documentation
Installation
This chapter includes the following topics:
♦ Overview, 57
♦ Installing PowerCenter Documentation, 57
♦ Viewing PowerCenter Documentation, 58
Overview
Informatica provides the PowerCenter Documentation DVD to install and view PowerCenter documentation
in PDF format and install online help files for the PowerCenter Client and Administration Console.
The PowerCenter Documentation DVD includes the following components:
♦ PowerCenter documentation. PowerCenter documentation in PDF format. It also includes the Informatica
Documentation Start Page which provides an easy way to select and view PowerCenter documents.
♦ PowerCenter Quick Start guides. Diagram and brief descriptions of the PowerCenter installation and
upgrade steps. Use the Quick Start guides to track the required installation information as you complete the
installation and upgrade of PowerCenter.
1. On the PowerCenter Documentation DVD or the location where you downloaded the documentation,
locate and run the documentation installation file:
\Disk1\install.bat
57
The Installation Directory window appears.
3. Enter the full path of the folder where you want to install the PowerCenter documentation.
The PowerCenter documentation installer displays the following default directory:
C:\Informatica\PowerCenter8.6.1
Overview
Informatica includes PowerCenter utilities with the PowerCenter product. PowerCenter utilities are customer
support tools and command line programs and utilities for PowerCenter and Metadata Manager. You can install
and run the programs and utilities on any machine without installing PowerCenter.
The PowerCenter utilities are included in a ZIP or TAR file. To install the utilities, unzip or untar and
configure the utilities on the machine where you want to run them.
The PowerCenter utilities include the following components:
♦ PowerCenter command line programs and utilities. Command line programs and utilities for use with
PowerCenter Services and the PowerCenter Client. For more information about the included programs and
utilities, see “PowerCenter Command Line Programs and Utilities” on page 59.
♦ Metadata Manager utilities. Utilities for use with the Metadata Manager application. For more information
about installing and configuring the Metadata Manager utilities, see “Metadata Manager Command Line
Programs” on page 60.
Note: Data Analyzer command line programs and utilities are installed when you install PowerCenter Services.
For more information, see the Data Analyzer documentation.
59
The following table describes the PowerCenter command line programs and utilities:
pmcmd Manage workflows. Use pmcmd to start, stop, schedule, and monitor workflows.
For more information about pmcmd, see the PowerCenter Command Reference.
pmpasswd Encrypt passwords to use with pmcmd and pmrep environment variables. For
more information about pmpasswd, see the PowerCenter Command Reference.
pmrep Performs repository administration tasks. Use pmrep to list repository objects,
create and edit groups, and restore and delete repositories. For more
information about pmrep, see the PowerCenter Command Reference.
pmserverexportreg Export the PowerCenter Server configuration information from the Windows
registry and create a PowerCenter Server configuration file. Use
pmserverexportreg to create configuration files for use with the Upgrade Wizard
in the PowerCenter Administration Console. For more information about
pmserverexportreg, see the PowerCenter Configuration Guide.
mmcmd Load resources, resume failed resource loads, get the status of a resource load,
and import and export models in Metadata Manager.
mmwfrundetails Get details about the PowerCenter sessions that load metadata into the
Metadata Manager warehouse.
For more information about running the Metadata Manager command line programs, see the Metadata
Manager Administrator Guide.
Overview
The Informatica Development Platform (IDP) makes the PowerCenter application programming interfaces
(APIs) available so you can integrate PowerCenter functionality with any application. You can use the
PowerCenter APIs to perform the following tasks:
♦ Create plug-ins for PowerCenter to extend its functionality.
♦ Create custom transformations that call procedures outside of PowerCenter.
♦ Access the Integration Service from a Java or C application and manage workflow, task, reporting, and log
requests.
♦ Generate PowerCenter metadata and XML documents containing mappings, sessions, and workflows.
♦ Develop functions written in C and add them to the Expression and Aggregator transformations.
For more information, see the Informatica Development Platform Developer Guide.
You can install the Informatica Development Platform APIs from the following sources:
♦ Informatica Development Platform installation DVD. Run the Informatica Development Platform installer
to install the PowerCenter APIs. You can install all the APIs or install only the APIs that you want to use.
♦ Informatica electronic software download site. When you purchase PowerCenter and choose to download
the software, you receive a site link, user ID, and password to access the Informatica electronic software
download site. Follow the instructions in the download site to download the Informatica Development
Platform installation file.
♦ Informatica Technology Network. If you are a registered user of the Informatica Technology Network, you
can download the Informatica Development Platform installation file from the Informatica Development
Platform page. When you download the file, the Informatica Development Network provides you with a
password. Use this password when you extract the files from the download file.
61
Installing the Informatica Development Platform
When you run the Informatica Development Platform installer, you can install all the APIs or install only the
APIs you want to use. To install all the APIs in one process, select the Complete installation option. To install
specific APIs, select the Custom installation option.
You can install the Informatica Development Platform on UNIX or Windows.
1. To start the installer on Windows, insert the DVD into the DVD drive. Run install.bat from the DVD root
directory or the root directory in the location where you downloaded the installer.
-or-
To start the installer on UNIX, run install.sh at a shell command line from the DVD root directory or the
root directory in the location where you downloaded the installer.
The Welcome window introduces the Informatica Development Platform installation.
2. Click Next.
The License Agreement window displays the license agreement for APIs. You must accept the license
agreement to continue.
3. Select I accept the terms of the license agreement option and click Next.
The Installation Set window displays the installation options.
4. To install the complete set of PowerCenter APIs, select Complete.
Skip to step 7.
To select PowerCenter APIs to install, select Custom.
5. Click Next.
The Custom Install Set window displays the list of PowerCenter APIs available with the Informatica
Development Platform.
6. Select the APIs you want to install.
7. Click Next.
8. On the Choose Installation Folder window, select the folder where you want to install the PowerCenter
APIs.
9. Click Next.
The Pre-Installation Summary window summarizes the installation information.
10. Review the installation information, and click Install to continue.
When the installation completes, the installer displays a message about whether the installation completed
successfully.
11. Click Done.
A uninstalling 53
domainmeta.xml
AddLicense (infacmd) backing up before upgrade 14
troubleshooting 49 domains
See PowerCenter domains
domains.infa
B backing up before upgrade 14
backupCmdLine
Metadata Manager 60
E
environment variables
C configuring for installation 19
catalina.out DISPLAY 19
troubleshooting installation 47 JRE_HOME 19
command line programs LANG 19
installing for Metadata Manager 60 LANG_C 19
installing for PowerCenter 59 LC_ALL 19
connect string LC_CTYPE 19
setting for database configuration 30 local 19
console mode temporary disk space 19
installing PowerCenter 28 UNIX requirements 24, 32
uninstallation 56 upgrade requirements 20
Create New Domain
console mode 29
graphical mode 25 G
graphical mode
installation requirements 19
D installing PowerCenter 24, 32
Data Analyzer uninstallation 55
utilities 59
database configuration
setting connect string 30 H
database requirements HTTPS
installation requirements 12 installation requirements 21
debug log
description 46
disk space requirements I
installation requirements 12
INFA_DOMAINS_FILE
documentation
removing before upgrade 20
installing 57
INFA_HOME
viewing 58
configuring for PowerCenter utilities 60
domain configuration database
removing before upgrade 20
See also PowerCenter Administrator Guide
infacmd
accounts 13
nodes, adding to domains 48
configuring with installer 25, 29
pinging objects 49
installation requirements 13, 14
PowerCenter command line program 60
requirements 12
troubleshooting 46
troubleshooting 48
63
infasetup localhost_log.<date>.txt
domains, defining 48 troubleshooting installation 47
troubleshooting 46 log files
worker nodes, defining 48 catalina.out 47
Informatica Developer Platform debug log 46
installing 62 installation 46
Informatica Development Platform installation log 47
download and installation 61 localhost_log.<date>.txt 47
Informatica Services node.log 47
description 6 summary log 46
troubleshooting 48 types 46
installation log
description 47
installation requirements M
database requirements 12
Mapping Architect for Visio
disk space 12
description 13
domain configuration database 13, 14
installation prerequisites 13
keystore file 21
installation requirements 13
Mapping Architect for Visio 13
Metadata Manager
minimum system requirements 11
backupCmdLine 60
system user account 18
installing command line programs 60
temporary disk space 19
mmcmd 60
third-party software 13
mmwfrundetails 60
X Window Server 19
utilities 59, 60
installing
Metadata Manager Client
creating a domain 25, 29
components 7
graphical mode 23
troubleshooting 49
joining a domain 25, 29
mmcmd
PowerCenter 23
Metadata Manager 60
PowerCenter Client 37
mmwfrundetails
PowerCenter documentation 57
Metadata Manager 60
Integration Service
description 6
N
J node.log
troubleshooting installation 47
Join Existing Domain
nodemeta.xml
console mode 29
backing up before upgrade 14
graphical mode 25
nodes
JRE_HOME
troubleshooting 48
environment variables 19
K O
ODBC (Open Database Connectivity)
keystore file
drivers 37
installation requirements 21
optimizing
repositories 16
L
LANG P
environment variable 19
permissions
LC_ALL
See Administrator Guide
environment variable 19
See also Repository Guide
LC_CTYPE
Ping (infacmd)
environment variable 19
troubleshooting 49
license key
pmcmd
verifying 11
PowerCenter command line program 60
licenses
pmrep
adding 49
PowerCenter command line program 60
locale
troubleshooting 46
configuring 19
64 Index
pmserverexportreg SUSE Linux
PowerCenter command line program 60 JRE_HOME 19
port numbers system requirements
PowerCenter Services 14 minimum installation requirements 11
PowerCenter system user account
complete installation in graphical mode 23 installation requirements 18
infacmd 60
installation in console mode 28
installation in graphical mode 24, 32 T
installing command line programs 59
temporary disk space
pmcmd 60
environment variables 19
pmrep 60
third-party software
pmserverexportreg 60
installation requirements 13
utilities 59
troubleshooting
PowerCenter Advanced Edition
creating a domain 48
complete installation in console mode 34
domain configuration database 48
uninstalling 53
error messages 49
PowerCenter APIs
infacmd 46
installing 62
infasetup 46
PowerCenter Client
Informatica Services 48
components 7
joining a domain 48
installing complete 38, 40
licenses 49
troubleshooting 49
Metadata Manager Client 49
PowerCenter domains
pinging a domain 49
description
pmrep 46
pinging 49
PowerCenter Client 49
troubleshooting 48
uninstallation 53
PowerCenter repository
updating before upgrade 16
PowerCenter Services
components 6
U
description uninstalling
port numbers 14 process 54
Service Manager 6 rules and guidelines 53
PowerCenter Standard Edition troubleshooting 53
uninstalling 53 UNIX
PowerCenter utilities user account 18
included utilities 59 upgrading
rules and guidelines 60 Web Services Hub 22
privileges user account
See Administrator Guide system user 18
R V
repositories viewing
copying 17 PowerCenter documentation 58
optimizing 16
Repository Service
description 6 W
Web Services Hub
S upgrading 22
Service Manager
description 6 X
log files 47 X Window Server
sessions installation requirements 19
configuring 16
Start Page
Informatica documentation 58
summary log
description 46
Index 65
66 Index
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.