Upgrading from Versions 10.4.0 and 10.4.1 (10.5.2)

10.5.2
- 10.5.4
- 10.5.3
- 10.5.1
- 10.5

Back Next

Upgrading in Console Mode

When you upgrade in console mode, you can change the node configuration to upgrade the domain to a different machine or to a different domain configuration repository database. You can upgrade the domain in console mode on Linux or UNIX.

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

On a shell command line, run the install.sh file from the root directory.

The installer displays the message to verify that the locale environment variables are set.

If the environment variables are not set, press

to exit the installer and set them as required.

If the environment variables are set, press

to continue.

Press

to upgrade Informatica.

Informatica provides utilities to facilitate the Informatica services installation process. You can run the following utility before you upgrade Informatica services:

Informatica Upgrade Advisor.: Validates the services and checks for obsolete services in the domain before you perform an upgrade.

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

Press

to upgrade to

Informatica 10.5.2

Read the terms and conditions of Informatica product usage toolkit and press

to continue the upgrade.

Subject to your opt-out rights described below, the software will automatically transmit to Informatica in the USA information about the computing and network environment in which the Software is deployed and the data usage and system statistics of the deployment. This transmission is deemed part of the Services under the Informatica privacy policy and Informatica will use and otherwise process this information in accordance with the Informatica privacy policy. You can disable usage collection in the Administrator tool.

The Upgrade Prerequisites
page displays the upgrade system requirements.

Verify the requirements before you continue the upgrade.

At the prompt, enter the directory of the Informatica version that you want to upgrade and the directory where you want to install

Informatica 10.5.2

The following table describes the directories you must specify:

Directory	Description
Directory of the Informatica product to upgrade	Directory that contains the version of Informatica services that you want to upgrade.
Directory for Informatica 10.5.2	Directory in which to install Informatica 10.5.2 . Enter the absolute path for the installation directory. The directory cannot be the same as the directory that contains the previous version of Informatica services.The directory names in the path must not contain spaces or the following special characters: @\|* $ # ! % ( ) { } [ ] , ; ' Informatica recommends using alphanumeric characters in the installation directory path. If you use a special character such as á or €, unexpected results might occur at run time. On Windows, the installation directory must be on the current machine.

Directory

Description

Directory of the Informatica product to upgrade

Directory that contains the version of Informatica services that you want to upgrade.

Directory for Informatica

10.5.2

Directory in which to install Informatica

10.5.2

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

Informatica recommends using alphanumeric characters in the installation directory path. If you use a special character such as á or €, unexpected results might occur at run time.

On Windows, the installation directory must be on the current machine.

Enter

to allow changes to the node host name and port number.

Use this option to change the configuration of the Informatica installation that you upgrade. If you are upgrading to a different machine, change the node configuration to match the configuration of the new machine. If you are upgrading to a different domain configuration repository database, change the node configuration to match the configuration of the new database.

Enter the directory for the encryption key for the informatica domain.

Informatica uses an encryption key to secure sensitive data, such as passwords, that are stored in the Informatica domain. When you upgrade, you must enter the directory in which to store the encryption key on the node that you are upgrading.

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

Property	Description
Encryption key directory	Directory in which to store the encryption key for the domain. By default, the encryption key is created in the following directory: <Informatica installation directory>/isp/config/keys

Enter the user name and password for the informatica domain.

Review the upgrade information and press

Enter

to continue.

The installer copies the server files to the

Informatica 10.5.2

installation directory.

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

Press

Enter

If you are upgrading a gateway node, select the database to use for the domain configuration repository.

If you are upgrading a worker node, the domain configuration repository information does not appear. You cannot modify the database connection information. Skip to step 16.

The following table lists the databases you can use for the domain configuration repository:

Prompt	Description
Database type	Type of database for the domain configuration repository. Select from the following options: 1 - Oracle 2 - Microsoft SQL Server 3 - IBM DB2 4 - Sybase ASE 5 - PostgreSQL

Enter the properties for the database user account.

The following table lists the properties for the database user account:

Property	Description
Database user ID	Name for the domain configuration database user account.
User password	Password for the domain configuration database user account.

Enter the parameters for the database. If you do not create a secure domain configuration repository, enter the parameters for the database.

If you select IBM DB2, select whether to configure a tablespace and enter the tablespace name.

The following table describes the properties that you must configure for the IBM DB2 database:

Property	Description
Configure tablespace	In a single-partition database, if you select No, the installer creates the tables in the default tablespace. In a multi-partition database, you must select Yes. Select whether to specify a tablespace: 1 - No 2 - Yes
Tablespace	Name of the tablespace in which to create the tables. Specify a tablespace that meets the pageSize requirement of 32768 bytes. In a single-partition database, enter the name of the tablespace in which to create the tables. In a multipartition database, specify the name of the non-partitioned tablespace that resides in the catalog partition of the database.

If you select Microsoft SQL Server, enter the schema name for the database.

The following table describes the properties that you must configure for the Microsoft SQL Server database:

Property	Description
Schema name	Name of the schema that will contain domain configuration tables. If this parameter is blank, the installer creates the tables in the default schema.

To enter the JDBC connection information using the JDBC URL information, press

. To enter the JDBC connection information using a custom JDBC connection string, press

Enter the JDBC connection information.

To enter the connection information using the JDBC URL information, specify the JDBC URL properties.

The following table describes the database connection information:

Prompt	Description
Database host name	Host name for the database.
Database port number	Port number for the database.
Database service name	Service or database name: Oracle: Enter the service name. Microsoft SQL Server: Enter the database name. IBM DB2: Enter the service name. Sybase ASE: Enter the database name. PostgreSQL: Enter the database name.
Configure JDBC Parameters	Select whether to add additional JDBC parameters to the connection string: 1 - Yes 2 - No If you select Yes, enter the parameters or press Enter to accept the default. If you select No, the installer creates the JDBC connection string without parameters.

To enter the connection information using a custom JDBC connection string, type the connection string.

Use the following syntax in the JDBC connection string:

IBM DB2: jdbc:Informatica:db2://<host name>:<port number>;DatabaseName=
Oracle: jdbc:Informatica:oracle://<host name>:<port number>;ServiceName=; Use the following connection string to connect to the Oracle database through the Oracle Connection Manager:

jdbc:Informatica:oracle:TNSNamesFile=<fully qualified path to the tnsnames.ora file>;TNSServerName=<TNS name>;
Microsoft SQL Server: jdbc:Informatica:sqlserver://<host name>:<port number>;SelectMethod=cursor;DatabaseName=
Microsoft SQL Server with Windows NT credentials: If you specified the Windows NT credentials for the Model repository database on Microsoft SQL Server, specify the connection string syntax to include the authentication method as NTLM.

Microsoft SQL Server that uses the default instance with Windows NT credentials:

"jdbc:informatica:sqlserver://<host name>:<port number>;DatabaseName=<database name>;SnapshotSerializable=true;authenticationMethod=NTLM"

Microsoft SQL Server that uses a named instance with Windows NT credentials:

"jdbc:informatica:sqlserver://<host name>\<named instance name>;DatabaseName=<database name>;SnapshotSerializable=true;authenticationMethod=NTLM"
Microsoft Azure SQL: jdbc:Informatica:sqlserver://<host name>:<port number>;SelectMethod=cursor;DatabaseName=<database name>;SnapshotSerializable=true;EncryptionMethod=SSL;HostNameInCertificate=*.database.windows.net;ValidateServerCertificate=false
Azure SQL Database with Active Directory authentication: jdbc:informatica: sqlserver://<host_name>:<port_number>;database=<database_name>;encrypt=true;AuthenticationMethod=ActiveDirectoryPassword;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;loginTimeout=<seconds>
PostgreSQL: jdbc:Informatica:postgresql://<host name>:<port number>;DatabaseName=
Azure PostgreSQL: jdbc:Informatica:postgresql://<host name>:<port number>;DatabaseName=<database name>;EncryptionMethod=SSL;ValidateServerCertificate=true;CryptoProtocolVersion=TLSv1.2;
Sybase: jdbc:Informatica:sybase://<host name>:<port number>;DatabaseName=

Verify that the connection string contains all the connection parameters required by your database system.

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

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

Property	Description
Domain name	Name of the domain. The default domain name is Domain_<MachineName>. The name must not exceed 128 characters and must be 7-bit ASCII only. It cannot contain a space or any of the following characters: ` % * + ; " ? , < > \ /
Node name	Name of the node that you are upgrading.
Node host name	Host name of the machine that hosts the node you are upgrading. If the machine has a single network name, use the default host name. If the machine has multiple network names, you can modify the default host name to use an alternate network name. Optionally, you can use the IP address. Note: Do not use localhost. The host name must explicitly identify the machine.
Custom keystore password	Plain text password for the custom keystore file. Enter the custom keystore password if you are securing the Informatica Administrator with a custom keystore file and you are upgrading to a different gateway node configuration.
Custom keystore file	Path and file name of the custom keystore file. Enter the custom keystore file if you are securing the Informatica Administrator with a custom keystore file and you are upgrading to a different gateway node configuration. If you leave this field blank, the installer looks for the keystore file in the following directory: <Informatica installation directory>\tomcat\conf\
Node port number	Port number for the node you are upgrading. The default port number for the node is 6005.
Gateway node host name	Host name of the machine that hosts the gateway node for the domain. Available if you upgrade a worker node.
Gateway node port number	Port number of the gateway node. Available if you upgrade a worker node.

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

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

The following table describes the ports that you can specify:

Port	Description
Service Manager port	Port number used by the Service Manager in the node. Client applications and the Informatica command line programs use this port to communicate to the services in the domain.
Service Manager Shutdown port	Port number that controls server shutdown for the domain Service Manager. The Service Manager listens for shutdown commands on this port.
Informatica Administrator port	Port number used by the Administrator tool. Available if you upgrade a gateway node.
Informatica Administrator shutdown port	Port number used by the Administrator tool to listen for shut down commands. Available if you upgrade a gateway node.

The Post-Installation Summary window indicates whether the upgrade completed successfully. It also shows the status of the installed components and their configuration.

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

Rename Saved Search

Table of Contents

Upgrading from Versions 10.4.0 and 10.4.1 (10.5.2)

Upgrading from Versions 10.4.0 and 10.4.1 (10.5.2)

Upgrading in Console Mode

Upgrading in Console Mode