Advanced Upgrade for Informatica 9.0.

1:
Changing the Node Configuration

2011 Informatica

Abstract
When you upgrade Informatica, you can change the location of the domain configuration database, the host name of a node,
and the port number of a node. This article explains when you might want to change these properties, how it works, and
information about the additional upgrade steps associated with making the changes. This articles reviews how to upgrade a
node that runs on an unsupported operation system and how to upgrade a clone of a domain.

Table of Contents
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Use Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Upgrade Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Step 1. Prepare for Domain and Server Files Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Determine the Availability of Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Create a System User Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Copy Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Step 2. Upgrade the Domain and Server Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Step 3. Prepare for Application Service Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Install Database Client Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Configure the UNIX Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Copy Required Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Update Port Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Verify the Node Backup Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Update Keystore File Name and Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Configure PowerExchange Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Create License Object for Upgrade to 64-bit Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Step 4. Complete the Remaining Upgrade Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Appendix: Create a Script to Copy Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Overview
Effective in version 9.0.1 HotFix 1, Informatica provides an upgrade option to change the node configuration. You can
change the node configuration when you upgrade from PowerCenter 8.1.x, PowerCenter 8.5.x, or PowerCenter 8.6.x.
When you change the node configuration, you can change the connection to the domain configuration repository, the node
host name, and the node port numbers. You cannot change the node name and domain name. If you want to change node
names in a domain, upgrade one node with the same name and then add nodes with different names to the domain.
If you choose to change the node configuration, you need to perform additional upgrade steps before you upgrade the
domain and server files, and before you upgrade the application services.

Use Cases
You may want to change the node configuration during an upgrade when you upgrade a node that is currently running on an
unsupported operating system or to test the upgrade on a clone of the domain.

Upgrade a Node that Runs on an Unsupported Operating System

Use the upgrade option to change the host name when a node runs on an operating system version that is no longer
supported by Informatica. Select a machine on supported operating system to run the upgraded node and complete the
steps to upgrade the domain.
The following figure shows an example of an domain that has been upgraded to Informatica 9.0.1 HotFix 1 using the option
to change the node host name:

Upgrade a Clone of the Domain

Use the upgrade option to change the node host name and the connection to the domain configuration repository, when you
want to perform an upgrade without altering the production environment. Select machines to run the domain clone, restore
copies of the domain configuration repository and other repositories to new database schemas, and complete the steps to
upgrade the domain.
The following figure shows an example of a cloned domain that was upgraded to Informatica 9.0.1 HotFix 1 using the option
to change the node host name and the connection to the domain configuration repository:

If the production environment cannot be shutdown during an upgrade, you can create a clone of the production environment,
perform an upgrade on the clone, test the upgraded clone, and then use the clone as the production environment.

Upgrade Process
The installer upgrades the node based on the information you enter and the files you provide on the new machine. When
you upgrade with changes to the node configuration, you must complete additional upgrade steps before you upgrade the
domain and server files, and before you upgrade the application services.

Installer Process
Before you run the installer, copy files from the previous installation directory to the new machine. The installer uses the files
from the previous installation directory and the information that you enter to update the node configuration on the new
machine. If the installation directory you specify when you run the installer does not have the files required to update the
node configuration, the upgrade will not complete successfully. For example, the installer requires the domain details from
nodemeta.xml and requires port information from server.xml.
When you run the installer, select the option to allow changes to the node configuration. This upgrade option appears in the
graphical mode and console mode of the server installer. When you select the option to allow changes to the node
configuration, the installer allows you to update the database connection to the domain configuration repository, update the
host name, and update port numbers.
Before you upgrade the application services, configure connectivity on the new machine and copy files that you require from
the previous installation directory. You may also need to reinstall some components, such as PowerExchange adapters. The
installer does not copy the infa_shared directory to the new installation directory and it does not update configuration files or
custom files that are located in previous installation directory on the new machine.

User Upgrade Steps

To upgrade with change to the node configuration, complete the following upgrade steps:
1.

Prepare for the domain and server file upgrade.

2.

Upgrade the domain and server files using the installer.

3.

Prepare for the application service upgrade.

4.

Complete the remaining upgrade steps.

Step 1. Prepare for Domain and Server Files Upgrade

Before you run the installer to upgrade the domain and server files, complete the pre-upgrade steps.
Complete the pre-upgrade steps to upgrade without changes to the node configuration. Then, complete the pre-upgrade
steps to upgrade with changes to the node configuration.
For more information about the pre-upgrade steps to upgrade without changes to node configuration, see the Informatica
upgrade guide for the version that you upgrade from.
Complete the following pre-upgrade steps for upgrading with changes to the node configuration:
1.

Determine port availability.

2.

Create a system user account.

3.

Copy the installation files.

Note: If you plan to clone the domain, restore backups of the domain configuration and other Informatica databases to new
database schemas.

Determine the Availability of Ports

Before you upgrade with changes to the node configuration, verify that the ports used by Informatica are available on the
machine where you want the node to run. If the ports are not available, you must configure different port numbers.
You can configure the port number for some ports when you upgrade the node. You can update the Service Manager
shutdown port and the range of ports for application services after you upgrade the node.
Note: The domain fails to start if the Service Manager shutdown port on the master gateway node has a port conflict. Verify
that the Service Manager shutdown port will not have a port conflict on the machine where you want the node to run. A node
will fail to start if there is a port conflict for any port used by Informatica.
The following table describes the ports you can configure in the server installer when you upgrade with changes to the node
configuration:
Port Type

Description

Node port

Port number for the node created during installation. Default is the pre-upgrade node port number.

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. The Informatica command line programs use this port to communicate to the
domain. This is also the port for the SQL data service JDBC/ODBC driver. Default is the node port
number plus 2000.

Informatica Administrator port

Port number used by the Administrator tool. Default is the node port number plus 2001. This option
appears when you upgrade a gateway node.

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 the node port number plus 2002. This option
appears when you upgrade a gateway node.

The following table describes the ports you can configure after you upgrade the domain:
Port Type

Description

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 the pre-upgrade Service Manager shutdown
port number. Use infasetup UpdateGatewayNode or UpdateWorkerNode to update the service
manager shutdown port.

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 the pre-upgrade range of ports for application services. Use the Administrator tool to
update the minimum and maximum port number for the node.

Create a System User Account

Create a system user account and verify that the user account you use to install Informatica has write permission on the
installation directory.
For more information, see the Informatica upgrade guide for the version that you upgrade from.

Copy Installation Files

Before you run the installer, copy Informatica installation files to the machine where you want the upgraded node to run.
Copy the entire Informatica Installation directory to the machine where you want the upgraded node to run or copy the
required files to the machine where you want the upgraded node to run. Although it is recommended, it is not a requirement
to copy the entire installation directory to the machine where you want the upgraded node to run. If you copy only the
required files to the machine where you want the upgraded node to run, the files must be in a specific directory structure.
Note: The upgrade fails if the required files are not available in the directory structure that the installer expects.
The server installer requires the following files to upgrade a node with changes to the node configuration:
File

Description

nodemeta.xml

Contains metadata about the node such as the domain name,

node name, and node address.

server.xml

Contains server port and keystore file details.

PC_DEFAULT.keystore

Includes private or public key pairs and associated certificates.

This file is required when the node uses HTTPS.

To copy the required files to the other machine, create the required directory structure to contain the files and then copy the
directory to the machine where you want to run the upgraded node to run. For example, create a directory named INFA_COPY.
1.

Create the following directory structure on the existing node:

INFA_COPY/
INFA_COPY/server/config
INFA_COPY/tomcat/conf

2.

Copy the following files from the Informatica installation directory to INFA_COPY:
Copy nodemeta.xml to INFA_COPY/server/config/.
Copy server.xml to INFA_COPY/tomcat/conf/.
If the node uses HTTPS, copy the keystore file to INFA_COPY/tomcat/conf/ and rename the keystore file to

PC_DEFAULT.keystore.
3.

Copy the INFA_COPY directory to the machine where you want to run the upgraded node to run.

To create a script to copy the directory structure to the other machine, see Appendix: Create a Script to Copy Installation
Files on page 11.

Step 2. Upgrade the Domain and Server Files

Use the server installer to upgrade the server files and domain of a previous version of Informatica. Run the server installer
on the machine where you want the upgraded node to run.
The server installer provides the option to allow changes to the node host name and port numbers. When you select the
option to upgrade with changes to the node configuration, you configure the following node properties:

Property

Description

Node host name

You can update the node host name. The name defaults to the existing node name.

Node port number

You can change the node port number. The default value is the pre-upgrade port
number.

Property

Description

Database connection to the domain

configuration repository

You must configure the database connection to the domain configuration repository.
The installer does not retain the database connection information from the previous
version of Informatica.

Service Manager port number

You can change the Service Manager port number. The default value is the node port
number plus 2000.

Informatica Administrator port

You can change the Informatica Administrator port number. The default value is the
node port number plus 2001.

Informatica Administrator shutdown port

You can change the Informatica Administrator shutdown port number. The default
value is the node port number plus 2002.

The following figure shows the upgrade option to change the node host name and port numbers:

The following figure shows the fields where you can configure the host name and port number for the node:

Note: You cannot change the node name or the domain name.
The following figure shows the fields where you can configure the Service Manager and Administrator tool port numbers for
the gateway node:

For more information, see the Informatica upgrade guide for the version that you upgrade from.

Step 3. Prepare for Application Service Upgrade

Before you upgrade the application services, complete the pre-upgrade steps.
Complete the pre-upgrade steps to upgrade without changes to the node configuration. Then, complete the pre-upgrade
steps to upgrade with changes to the node configuration.

For more information on the pre-upgrade steps to upgrade without changes to node configuration, see the Informatica
upgrade guide for the version that you upgrade from.
To upgrade with changes to the node configuration, complete the following tasks:
1.

Install the database client software.

2.

Configure the UNIX environment.

3.

Copy the required files.

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.

8.

Create a license object for upgrade to 64-bit nodes.

Install Database Client Software

When you change the machine that runs an Informatica node you must reconfigure connectivity to database clients.
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.
For more information, see the Informatica upgrade guide for the version that you upgrade from.

Configure the UNIX Environment

On a UNIX or Linux operating system, configure the library path environment variables and verify that a graphics display
server is available.
For more information, see the Informatica upgrade guide for the version that you upgrade from.

Copy Required Files

When you choose to update the node configuration, the installer does not copy files from the previous installation directory.
Copy the following files from the previous installation directory to the new installation directory:

File or Folder

Locations

Infa_Shared folder

Previous Installation directory:

<InformaticaInstallationDir>/server/infa_shared
New installation directory:
<InformaticaInstallationDir>/server/infa_shared

mm_files folder

Previous installation directory:

<8.6.1 InformaticaInstallationDir>\server\tomcat\mm_files
New installation directory:
<InformaticaInstallationDir>\services\MetadataManagerService\mm_files

reswords.txt

Previous installation directory:

<InformaticaInstallationDir>/server/bin
New installation directory:
<InformaticaInstallationDir>/server/bin
Note: Copy this file if it exists in the previous installation directory.

odbc.ini

If the previous Informatica installation used odbc.ini to connect to databases, you can copy
the odbc.ini to the new machine to retain the existing configuration.

Update Port Numbers

To avoid startup failure, update port numbers for service processes and service manager shutdown.

Service Process Port Numbers

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

Service Manager Shutdown Port

Nodes fail to start if there is a Service Manager Shutdown port conflict. Use infasetup UpdateGatewayNode or
UpdateWorkerNode to update the service manager shutdown port.

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.

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, re-install the PowerExchange adapter.

PowerExchange for SAP NetWeaver for PowerCenter

If your previous installation included PowerExchange for SAP NetWeaver you must also copy the saprfc.ini file from the
previous server/bin directory to the latest server/bin directory.

Create License Object for Upgrade to 64-bit Nodes

Create a License object if the machine that runs the Informatica node is a 64-bit machine and the previous machine was a 32bit machine.
Assign a 64-bit license object to application services that run on 64-bit nodes.
1.

In the Administrator tool, create a License object for the 64-bit license key.

2.

Assign the License object to the application services that run on 64-bit nodes.

Note: An application service that runs on 64-bit node will fail to start until it is assigned to the 64-bit license object.

Step 4. Complete the Remaining Upgrade Steps

After you prepare the node for application service upgrade, complete the remaining upgrade steps.
Complete the following steps to complete the upgrade:
1.

10

Upgrade the application services.

2.

Upgrade the client.

3.

Complete post-upgrade steps.

For more information, see the Informatica upgrade guide for the version that you upgrade from.

Appendix: Create a Script to Copy Installation Files

You can use a script to copy the entire installation directory or you can use a script to copy the required files.

Use a Script to Copy the Entire Installation Directory

1.

On the machine that runs the existing Informatica node, verify that the Informatica installation directory contains
the required files in the following structure:
$INFA_HOME/
$INFA_HOME/server/config/nodemeta.xml
$INFA_HOME/tomcat/conf/server.xml
$INFA_HOME/tomcat/conf/PC_DEFAULT.keystore

Note: PC_DEFAULT.keystore is required when the node uses HTTPS.

2.

On the machine that runs the existing Informatica node, execute a command to compress the Informatica directory
structure and files.

3.

Transfer the compressed file to the machine where you want the upgraded node to run.

4.

On the machine where you want the upgraded node to run, execute a command to decompress the compressed
file.

Note: Preserve the directory structure when you compress and decompress the files.

Use a Script to Copy the Required Files

If you have performance or system disk space concerns, you can copy the required files to the machine where you want the
upgraded node to run.
1.

Using files from the existing Informatica installation directory, create a directory with the required files in the
require structure. For example, create INFA_COPY with the following directory structure and files:
INFA_COPY/
INFA_COPY/server/config/nodemeta.xml
INFA_COPY/tomcat/conf/server.xml
INFA_COPY/tomcat/conf/PC_DEFAULT.keystore

Note: PC_DEFAULT.keystore is required when the node uses HTTPS.

2.

Execute a command to compress the directory structure and files.

3.

Transfer the compressed file to the machine where you want the upgraded node to run.

4.

On the machine where you want the upgraded node to run, execute a command to decompress the compressed
file.

Note: Preserve the directory structure when you compress and decompress the files.
For more information about the required files, see Copy Installation Files on page 6.

Author
Padma Heid
Senior Technical Writer

11

Acknowledgements
The author would like to acknowledge Sean Ma, the Informatica Quality Assurance team, and the Informatica
Development team for their contributions to this article.

12