In 1053 UpgradingFromVersion1040AndLater en

Informatica®
10.5.3
Upgrading from Version

10.4.0 and Later (10.5.3)
Informatica Upgrading from Version 10.4.0 and Later (10.5.3)
10.5.3
November 2022
© Copyright Informatica LLC 2006, 2023
This software and documentation are provided only under a separate license agreement containing restrictions on use and disclosure. 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 LLC.
Informatica, the Informatica logo, PowerCenter, and PowerExchange are trademarks or registered trademarks of Informatica LLC in the United States and many
jurisdictions throughout the world. A current list of Informatica trademarks is available on the web at https://www.informatica.com/trademarks.html. Other company
and product names may be trade names or trademarks of their respective owners.
Subject to your opt-out rights, 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 available at https://www.informatica.com/in/
privacy-policy.html. You may disable usage collection in Administrator tool.
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial
computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such,
the use, duplication, disclosure, modification, and adaptation is subject to the restrictions and license terms set forth in the applicable Government contract, and, to the
extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License.
Portions of this software and/or documentation are subject to copyright held by third parties. Required third party notices are included with the product.
See patents at https://www.informatica.com/legal/patents.html.
The information in this documentation is subject to change without notice. If you find any problems in this documentation, report them to us at
[email protected].
Informatica products are warranted according to the terms and conditions of the agreements under which they are provided. INFORMATICA PROVIDES THE
INFORMATION IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT.
Publication Date: 2023-01-16

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Informatica Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica Product Availability Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 1: Upgrade Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Informatica Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Upgrade Paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Upgrade Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 2: Apply the hotfix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Hotfix installation and rollback overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Applying the services hotfix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Before you apply the hotfix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Apply the services hotfix in graphical mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Apply the services hotfix in console mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Apply the services hotfix in silent mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
After you apply the hotfix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Rolling back the services hotfix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Roll back the services hotfix in graphical mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Roll back the services hotfix in console mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Roll back the services hotfix in silent mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Applying the client hotfix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Apply the client hotfix in graphical mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Apply the client hotfix in silent mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Remove the distribution packages from the backup location. . . . . . . . . . . . . . . . . . . . . . . 25
Rolling back the client hotfix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Rolling back the client hotfix in graphical mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Rolling back the client hotfix in silent mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Chapter 3: Before You Upgrade the Domain on Linux. . . . . . . . . . . . . . . . . . . . . . . . . 28

Read the Release Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Verify System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Verify Temporary Disk Space and Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Verify the Domain Upgrade Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table of Contents 3
Review Patch Requirements on Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Verify Distribution Package Requirements (Linux and UNIX). . . . . . . . . . . . . . . . . . . . . . . 31
Review the Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Download and Extract the Installer Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Verify Installer Package Checksum on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Run the Informatica Upgrade Advisor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Back Up the Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Chapter 4: Before You Upgrade the Domain on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . 36

Review Patch Requirements on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Install the Java Runtime Environment for AIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Verify the Domain Upgrade Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Temporary Disk Space Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Verify Site Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Verify Distribution Package Requirements (Linux and UNIX). . . . . . . . . . . . . . . . . . . . . . . . . . 38
Review the Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Review the Maximum Heap Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Verify Installer Package Checksum on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Chapter 5: Before You Upgrade the Domain on Windows. . . . . . . . . . . . . . . . . . . . . 44

Verify the Domain Upgrade Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Verify Temporary Disk Space and Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Verify Site Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Verify Distribution Package Requirements (Windows). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Review the Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Review the Maximum Heap Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Verify Installer Package Checksum on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Chapter 6: Prepare for the Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Back Up the Data Transformation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Prepare the PowerCenter Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Back Up the Model Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Prepare the Data Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4 Table of Contents
Prepare the Profiling Warehouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Prepare the Reference Data Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Prepare Metadata Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Back Up the Metadata Manager Warehouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Back Up the Metadata Manager Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Back Up Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Prepare the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Shut Down the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Back Up the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Chapter 7: Upgrade the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Upgrade the Informatica Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Upgrade in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Upgrade in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Upgrade in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Encrypting Passwords in the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Creating the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Troubleshooting the Domain Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Chapter 8: Upgrade the Domain with Changes to Node Configuration. . . . . . . . . 74

Upgrade the Domain with Changes to Node Configuration Overview. . . . . . . . . . . . . . . . . . . . . 74
Migrating to a Different Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Migrating the Installation to a Different Machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Copy the Installation Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Determine Port Availability on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Step 3. Create a System User Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Step 4. Configure Native Connectivity on Service Machines. . . . . . . . . . . . . . . . . . . . . . . . 77
Step 5. Install Database Client Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Step 6. Configure Database Client Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . 78
Step 6. Configure Database Client Environment Variables on UNIX. . . . . . . . . . . . . . . . . . . 79
Upgrade in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Upgrading in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Upgrading in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Complete Changing the Node Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Clear the Browser Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Configure Locale Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Configure Library Path Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Verify the Range of Dynamic Port Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Verify the Node Backup Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Configure PowerExchange Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Table of Contents 5
Chapter 9: Before You Upgrade the Application Services. . . . . . . . . . . . . . . . . . . 102
Configure Informatica Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Configure Locale Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Verify the Keystore File Location for the Administrator Tool. . . . . . . . . . . . . . . . . . . . . . . . . . 103
Clear the Browser Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Chapter 10: Application Service Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Application Service Upgrade Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Privileges to Upgrade Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Service Upgrade from Previous Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Run the Upgrade Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Verify the Model Repository Service Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Object Dependency Graph. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Advanced Properties for the Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . 108
Chapter 11: Informatica Client Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Informatica Client Upgrade Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Verify Installer Package Checksum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Informatica Client Upgrade Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Upgrading in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Creating the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Chapter 12: After You Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Informatica Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Update the Log Events Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Enable Transport Layer Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Upgrade the Informatica Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Migrating to a Different Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Secure Client Connections to the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Upgrade the Connection Provider Type for Microsoft SQL Server. . . . . . . . . . . . . . . . . . . . . . 117
PowerCenter Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
PowerCenter Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Data Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Update the Log Events Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Update Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Analyst Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Verify the Flat File Cache Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Verify the Temporary Export File Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Recycle the Analyst Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Metadata Manager Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
6 Table of Contents
Metadata Manager Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Update the Metadata Manager Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Verify the ODBCINST Environment Variable on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Purge and Reload Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Upgrade Informatica Platform Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Copy the Data Transformation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Read What's New and Changed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Appendix A: Upgrade Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Upgrade Checklist Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Before You Upgrade the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Domain Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Before You Upgrade the Application Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Application Service Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Informatica Client Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
After You Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Appendix B: Managing Distribution Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Managing Distribution Packages Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Install or Remove Distribution Packages in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Install or Remove Distribution Packages in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
After You Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Table of Contents 7
Preface
Follow the instructions in this upgrade guide to upgrade the product.
Review the upgrade guide to upgrade the services and clients for the Informatica domain. Verify the database
requirements and set up the databases for the domain. You can verify the distributions for the supported
products in the native and non-native environments. Verify that your environment meets the minimum system
requirements for the installation process, temporary disk space, port availability, databases, and application
service hardware.
You can upgrade the product services and clients on one or more machines. Run the server installer to
upgrade on all nodes. After you upgrade the domain, you must log into the Administrator tool and upgrade
the application services. You can then upgrade the Informatica clients on all machines.
Informatica Resources
Informatica provides you with a range of product resources through the Informatica Network and other online
portals. Use the resources to get the most from your Informatica products and solutions and to learn from
other Informatica users and subject matter experts.
Informatica Network
The Informatica Network is the gateway to many resources, including the Informatica Knowledge Base and
Informatica Global Customer Support. To enter the Informatica Network, visit
https://network.informatica.com.
As an Informatica Network member, you have the following options:
• Search the Knowledge Base for product resources.

• View product availability information.
• Create and review your support cases.
• Find your local Informatica User Group Network and collaborate with your peers.
Informatica Knowledge Base

Use the Informatica Knowledge Base to find product resources such as how-to articles, best practices, video
tutorials, and answers to frequently asked questions.
To search the Knowledge Base, visit https://search.informatica.com. If you have questions, comments, or
ideas about the Knowledge Base, contact the Informatica Knowledge Base team at
[email protected].
8
Informatica Documentation
Use the Informatica Documentation Portal to explore an extensive library of documentation for current and
recent product releases. To explore the Documentation Portal, visit https://docs.informatica.com.
If you have questions, comments, or ideas about the product documentation, contact the Informatica
Documentation team at [email protected].
Informatica Product Availability Matrices

Product Availability Matrices (PAMs) indicate the versions of the operating systems, databases, and types of
data sources and targets that a product release supports. You can browse the Informatica PAMs at
https://network.informatica.com/community/informatica-network/product-availability-matrices.
Informatica Velocity
Informatica Velocity is a collection of tips and best practices developed by Informatica Professional Services
and based on real-world experiences from hundreds of data management projects. Informatica Velocity
represents the collective knowledge of Informatica consultants who work with organizations around the
world to plan, develop, deploy, and maintain successful data management solutions.
You can find Informatica Velocity resources at http://velocity.informatica.com. If you have questions,
comments, or ideas about Informatica Velocity, contact Informatica Professional Services at
[email protected].
Informatica Marketplace
The Informatica Marketplace is a forum where you can find solutions that extend and enhance your
Informatica implementations. Leverage any of the hundreds of solutions from Informatica developers and
partners on the Marketplace to improve your productivity and speed up time to implementation on your
projects. You can find the Informatica Marketplace at https://marketplace.informatica.com.
Informatica Global Customer Support

You can contact a Global Support Center by telephone or through the Informatica Network.
To find your local Informatica Global Customer Support telephone number, visit the Informatica website at
the following link:
https://www.informatica.com/services-and-training/customer-success-services/contact-us.html.
To find online support resources on the Informatica Network, visit https://network.informatica.com and
select the eSupport option.
Preface 9
Chapter 1
Upgrade Overview
This chapter includes the following topics:
• Informatica Upgrade, 10
• Upgrade Paths, 10
• Upgrade Process, 11
Informatica Upgrade
The Informatica platform consists of a server component and one or more client components. Informatica
provides separate installers to upgrade the Informatica services and clients.
When you upgrade each node in the domain, you can choose to change the node configuration to allow
changes to the node host name, port numbers, or domain configuration repository database.
Upgrade Paths
The upgrade path that you take depends on the products that you upgrade. If you are on a version that
doesn't support a direct upgrade, you must first upgrade to a supported version.
The following table lists the upgrade paths for each product that the installer supports.
Product Versions
PowerCenter You can apply the 10.5.3 hotfix to version 10.5, 10.5.1, and 10.5.2 including any service pack or
cumulative patch.
You can upgrade to version 10.5.3 from the following previous versions:
- 10.2 including any hotfix, service pack, or cumulative patch
- 10.4 including any service pack or cumulative patch
- 10.4.1 including any service pack or cumulative patch
Informatica Data You can apply the 10.5.3 hotfix to version 10.5, 10.5.1, and 10.5.2 including any service pack or
Quality cumulative patch.
- 10.2 including any hotfix, service pack, or cumulative patch
10
Product Versions
Data Engineering You can apply the 10.5.3 hotfix to version 10.5, 10.5.1, and 10.5.2 including any service pack or
Integration cumulative patch.
Data Engineering You can upgrade to version 10.5.3 from the following previous versions:
Quality - 10.2 including any hotfix, service pack, or cumulative patch
- 10.2.1 including any hotfix, service pack, or cumulative patch
Important: If Data Engineering is in the same domain as any other product supported by the
Informatica installer, verify that all products are upgraded to the same supported upgrade version
before you upgrade to 10.5.3.
Data Engineering You can apply the 10.5.3 hotfix to version 10.5, 10.5.1, and 10.5.2 including any service pack or
Streaming cumulative patch.
Data Privacy You can apply the 10.5.3 hotfix to versions 10.5, 10.5.1, and 10.5.2 including any service pack or
Management cumulative patch.
Enterprise Data You can apply the 10.5.3 hotfix to version 10.5, 10.5.1, and 10.5.2 including any service pack or
Catalog cumulative patch.
Important: If Enterprise Data Catalog and Data Engineering are in the same domain of a version
earlier than 10.4, upgrade them both to version 10.4 or 10.4.1 before you upgrade to 10.5.3.
Enterprise Data You can apply the 10.5.3 hotfix to version 10.5, 10.5.1, and 10.5.2 including any service pack or
Preparation cumulative patch.
Important: If Data Engineering, Enterprise Data Catalog, and Enterprise Data Preparation are in
the same domain of a version earlier than 10.4, upgrade them all to version 10.4 or 10.4.1 before
you upgrade to 10.5.3.
Test Data You can apply the 10.5.3 hotfix to versions 10.5, 10.5.1, and 10.5.2 including any service pack or
Management cumulative patch.
Upgrade Process
The upgrade of the Informatica services and Informatica clients consists of multiple phases.
The upgrade consists of the following phases:
1. Complete the pre-upgrade tasks for the domain to ensure that you can successfully run the installer.
Upgrade Process 11
2. Upgrade the domain. To upgrade the domain, run the Informatica server installer and select the upgrade
option. The domain upgrade wizard installs the server files and configures the domain. If the domain has
multiple nodes, you must upgrade all nodes. When you upgrade each node in the domain, you can
choose to change the node configuration to allow changes to the node host name, port numbers, or
domain configuration repository database.
The following table describes the actions that the installer performs when you upgrade the domain:
Tasks Descriptions
Runs Informatica Upgrade Installer runs the pre-upgrade to validate the services and checks for
Advisor. obsolete services, supported database, and supported operating system in
the domain.
Resolve the conflicts before you proceed with the upgrade.
Installs Informatica. Installs Informatica directories and files into the new directory.
Copies infa_shared directory. Copies the contents of the infa_shared directory from the existing
installation directory into the new installation directory.
Copies the encryption key file. Copies the domain encryption key file from the existing installation
directory into the directory that you specify when you upgrade.
If the existing domain uses Copies the Kerberos configuration file from the existing installation
Kerberos authentication, copies directory into the new installation directory. Copies the keytab files from
the Kerberos configuration file the existing installation directory into the encryption key directory that you
and keytab files. specify when you upgrade.
If the existing domain uses the Copies the contents of the mm_files directory from the default location in
Metadata Manager Service, copies the existing installation directory into the new installation directory.
mm_files directory.
Upgrades the domain. The upgrade retains the user and administrator accounts in the domain.
Starts Informatica Services. Starts Informatica Services on the node.
3. Upgrade the application services. After you upgrade the domain, log in to the Administrator tool and
upgrade the application services. The service upgrade wizard provides a list of all application services
that must be upgraded. It upgrades the services based on the order required by the dependent objects.
4. Upgrade the Informatica clients. Use the client installer to upgrade the following Informatica client tools:
• PowerCenter Client
• Informatica Developer
To upgrade Informatica clients, run the Informatica client installer and select the upgrade option. If the
clients are installed on multiple machines, upgrade the clients on all machines.
5. Perform the post-upgrade tasks.
Note: If you upgrade the Informatica installation on more than one machine, complete the first upgrade
with the detailed instructions in this guide. You can use the upgrade checklist in the appendix to perform
subsequent upgrades.
12 Chapter 1: Upgrade Overview

Chapter 2
Apply the hotfix

• Hotfix installation and rollback overview, 13

• Applying the services hotfix, 13
• Rolling back the services hotfix, 21
• Applying the client hotfix, 23
• Rolling back the client hotfix, 26
Hotfix installation and rollback overview

When you apply the hotfix, the installer backs up existing directories, applies the new version of the product,
and restores or updates required configuration and run-time files.
Informatica provide installers to apply hotfixes to the Informatica services and clients.
To apply or roll back the Informatica hotfix, perform the following steps:
1. Complete the preliminary tasks. Before you apply or rollback the hotfix, ensure that you shut down the
domain. For a multi-node configuration, you also need to shut down all the nodes.
2. Apply or roll back the hotfix to the Informatica services in graphical, console, or silent mode.
3. Complete the final tasks for the Informatica services. After you install the server components, start the
domain on the gateway node.
4. Apply the hotfix to the Informatica clients in graphical or silent mode. If you are applying the hotfix to
Informatica Developer, verify that the Informatica client hotfix version matches the Informatica services
hotfix version.
Note: If the Informatica client hotfix version does not match the Informatica services hotfix version,
Informatica Developer cannot connect to the domain.
When you roll back a hotfix, the installer restores Informatica to the previously installed version.
Applying the services hotfix

When you apply the hotfix, the installer backs up existing directories, applies the new version of the product,
You can run the installers to apply hotfixes to Informatica services and clients.
13
Before you apply the hotfix
Before you run the installer to apply the hotfix, perform the following prerequisite tasks:
Verify distribution package requirements

The Informatica domain and client require the distribution packages to process complex files within the
Informatica domain, or to connect to Hadoop or Databricks environment when you process within the
Informatica domain, or to push processing to Hadoop or Databricks environment.
If you need a distribution package, you can install it through the installer or through Integration Package
Manager (the package manager) at any time.
You can use the same distribution package that you used in the previous Informatica version to process
complex files within the Informatica domain or to connect to the Hadoop or Databricks environment when
you process within the Informatica domain.
For the supported distribution packages when you push processing to Hadoop or Databricks environment,
see the Product Availability Matrix.
Download and extract the installer files

The installer files are distributed as compressed files. You can get the Informatica installation file and
distribution packages from the FTP link contained in your fulfillment email. Download the Informatica
installation tar file from the Informatica Electronic Software Download site to a directory on your machine.
Note: Make sure that you download the file to a local directory or a shared network drive that is mapped on
your machine. You can then extract the installer files. However, you cannot run the installer from a mapped
file. Copy the extracted files to a local drive and then run the installer.
1. Download the hotfix package for your product.

2. Unzip or untar the contents of the hotfix package.
Note: On Windows, the length of the installation path, including the .zip file name, must be 60 characters
or fewer. On UNIX, use the native tar or GNU tar command to extract the installer files. The user that runs
the installer must have read and write permissions on the directory that contains the installer files and
execute permissions on install.sh.
3. If you want to install distribution packages, download the ZIP files of the distribution packages.
4. Copy the ZIP files of the distribution packages to the location: <Informatica installer files>/source
Note: The installer fails if the ZIP files for distribution packages aren't available in the source directory.
Prepare for hotfix installation

1. Stop all processes that access the installation directory and subdirectories, including command prompts
and command line programs.
2. Close the Informatica clients on all machines where you want to apply the hotfix.
3. Close the Informatica directory and the subdirectories.
4. Back up the repository and warehouse files. Ensure that you back up the required repositories from the
Administrator tool. These backup files are required if you roll back the hotfix. Back up the following
databases and files in your environment:
• PowerCenter repository
• Model repository
• Metadata Manager imm.properties file
• Metadata Manager warehouse
14 Chapter 2: Apply the hotfix

• Data Transformation ServiceDB directory
5. Stop the Informatica services on all nodes in the domain.
6. Shut down the Informatica domain using the infaservice shutdown command. By default, the infaservice
executable file is located in the following directory: <Informatica installation directory>/
tomcat/bin.
7. If the machine uses HTTPS to connect to Informatica Administrator, verify that the keystore file is in the
default location and that it uses the default file name. The default location for the keystore file is
<Informatica installation directory>/tomcat/conf. The default file name for the keystore file is
Default.keystore.
8. Set the SKIP_VENDOR_CHECK environment variable to true to remove the sudo prompt from the hotfix
installation on UNIX.
Note: If you don't have sudo privileges, set the environment variable to true before you apply or roll back
a hotfix. If you have sudo privileges, you don't need to set the environment variable.
Apply the services hotfix in graphical mode

When you apply the hotfix in graphical mode, a console window opens and runs in the background. If you
close this window, the installation stops.
1. Log in to the machine with a system user account. The user account must be the same account used to
install the previous version of Informatica services.
2. Close all other applications.
3. To begin the installation on Windows, run install.bat as administrator from the root directory where
you unzipped or untarred the hotfix package. To run the file as administrator, right-click install.bat and
select Run as administrator.
4. On the Informatica 10.5.3 page, select Apply hotfix to Informatica 10.5, 10.5.1, or 10.5.2, and then click
Start.
The Installation Type page appears.
5. Select Apply the hotfix to apply the hotfix.
6. Read the terms and conditions of Informatica product usage toolkit and select I agree to the terms and
conditions, and then click Next.
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 available at
https://www.informatica.com/in/privacy-policy.html. You may disable usage collection in Administrator
tool.
The Installation Prerequisites page appears.
7. Verify that all requirements are met before you apply the hotfix, and then click Next.
The Installation Directory page appears.
8. Enter the absolute path for the directory in which the current version of Informatica services is installed
and specify the installation environment.
9. If you want to install distribution packages through the Informatica installer, select the check box.
10. If you choose to install distribution packages, select one or more packages from the list that you want to
install.
Applying the services hotfix 15

11. Click Next.
The Pre-Installation Summary page appears.
12. Review the installation information, and then click Install to apply the hotfix.
The installer copies the Informatica files to the installation directory.
13. Complete the post-installation tasks. Verify that the hotfix completed successfully by reviewing the log
file or the Post-Installation Summary page.
Apply the services hotfix in console mode

Run the 10.5.3 installer to apply the hotfix to version 10.5 or 10.5.x.
When you apply the hotfix in console mode, the words Help, Quit, and Back are reserved words. Do not use
them as input text.
1. Run the installer using the ./install.sh command.

2. Press Y to confirm that you want to proceed with the installation.
3. Press 5 to select the option to apply the hotfix.
4. Press 1 to apply the hotfix.
5. Press 2 to agree to the terms and conditions and apply the license.
6. Verify that all installation requirements are met before you continue to apply the hotfix.
7. Press Enter.
8. Enter the directory where you installed Informatica 10.5 or 10.5.x.
The directory names in the path must not contain spaces or the following special characters: @|* $ # ! %
( ){ } [ ] , ; '
9. Select one of the following options based on the type of installation:
• Press 1 to set Sandbox environment for a basic environment used for proof of concept with minimal
users.
• Press 2 to set Development environment for the design environment.
• Press 3 to set Test environment for high volume processing that is closest to a production
environment.
• Press 4 to set Production environment for high volume processing with high levels of concurrency
meant for end users. Advanced production environments are typically multi-node setups.
Default is 1 for Sandbox.
10. Choose whether you want to install distribution packages through the Informatica installer.
• Press 1 if you don't need distribution packages or if you want to install them later.
• Press 2 if you want to install distribution packages through the installer.
Default is 1.
install. Separate multiple packages with a comma.
Default is 1.
12. Press Enter.
13. At the Pre-Installation Summary, review the installation information and press Enter to apply the hotfix.
14. At the Post-Installation Summary, verify that the hotfix application completed successfully and press
Enter to exit the installer.

Apply the services hotfix in silent mode
To apply the hotfix in silent mode, create the SilentInput.properties file and then run the installer.
Informatica provides a sample properties file, called SilentInput_hotFix.properties, that includes the
parameters that the installer requires.
1. Go to the root of the directory that contains the installation files.

2. Locate the SilentInput_hotFix.properties file.
3. Back up the file before you modify it.
4. Use a text editor to open the file and modify the values. The following table describes the installation
properties that you can modify:
Property Name Description
INSTALL_TYPE Indicates whether to apply the hotfix or roll back the hotfix. If the value is 0,
the installer applies the hotfix to the current Informatica installation. If the
value is 1, the installer rolls back the current hotfix.
Set the value to 0 to apply the hotfix.
USER_INSTALL_DIR Directory for the Informatica installation where you want to apply or roll back
the hotfix.
To apply the hotfix to Informatica services, enter the absolute path for the
directory in which the current version of Informatica services is installed.
ENABLE_USAGE_COLLECTION Enables the software to 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
https://www.informatica.com/in/privacy-policy.html. You may disable usage
collection in Administrator tool. For more information about how to disable
sending usage statistics, see the Informatica Administrator Guide.
You must set the value to 1 to apply the hotfix.
INSTALLATION_ENVIRONMENT If you apply the hotfix, specify the environment type associated with the
Informatica services installation.
• Press 1 to set Sandbox environment for a basic environment used for proof
of concept with minimal users.
• Press 2 to set Development environment for the design environment.
• Press 3 to set Test environment for high volume processing that is closest
to a production environment.
• Press 4 to set Production environment for high volume processing with high
levels of concurrency meant for end users. Advanced production
environments are typically multi-node setups.
Default is 1 for Sandbox.
EDC_CATALOG_INST Required for Enterprise Data Catalog, Data Privacy Management, and
Enterprise Data Preparation installations. Set the property to true if the
Catalog Service runs on the node on which you want to apply the hotfix.

EDC_HF_BACKUP Required for Enterprise Data Catalog, Data Privacy Management, and
Enterprise Data Preparation installations, if you have set
EDC_CATALOG_INST=true. Set the property to true if you have taken a backup
of the catalog.
EDC_BACK_UP_DIR Required for Enterprise Data Catalog, Data Privacy Management, and
Enterprise Data Preparation installations, if you set the EDC_CATALOG_INST
and EDC_HF_BACKUP properties to true. Enter the location of the catalog data
backup file.
INSTALL_HADOOP_LIBRARIES Determines whether to install distribution packages through the installer. Set
the value to true if you want to install distribution packages through the
installer. Set the value to false if you don't need distribution packages or if
you want to install them later.
SELECTED_HADOOP_LIBRARIES Determines the distribution packages that you want to install from the
supported packages list. Enter the distribution packages that you want to
install, separating multiple packages with a comma.
5. Save the properties file with the name SilentInput.properties in the same folder.
6. Go to the root of the services installer directory.
7. Verify that the directory contains the SilentInput.properties file that you edited and saved.
8. Begin the installation from Windows, UNIX, or Linux.
• To apply the hotfix on Windows, run the silentInstallHotFix.bat file as administrator. To run the file as
administrator, right-click the file and select Run as administrator.
• To apply the hotfix on UNIX or Linux, double-click the silentInstallHotFix.sh file.
Sample silent input properties

The following example shows the contents of the SilentInput.properties file when you apply or roll back
the hotfix in silent mode.
##########################################################
# Informatica Installer Build Details
# Copyright (c) 1993-2021 Informatica LLC
# This software contains confidential and proprietary
# information of Informatica LLC.
# All Rights Reserved.
##########################################################
# Use the following guidelines when editing this file

# * Use this file to install without user interaction.
# * After you create the properties file, save the file with the name
SilentInput.properties
# * Any error condition that leads to failure, such as an invalid
# installation directory, generates a log file in the user home directory.
# For example: c:\silentErrorLog<time_stamp>.log
##########################################################
# Set ENABLE_USAGE_COLLECTION to 1 to accept the product usage toolkit end user license
agreement.

# You must set the value as 1 to install the Informatica platform.
# The product usage toolkit end user license agreement is available at: http://
www.informatica.com/us/eula/en-support-eula.aspx.
# As further described in the EULA, your use of the Informatica platform will enable the
product usage toolkit
# to collect certain product usage and failure information. You may disable this feature
at any time.
# For more information on how to disable this feature refer the Informatica
Administrator Guide.
ENABLE_USAGE_COLLECTION=0
## *INSTALL_TYPE - Set this value to '0' to apply the hotfix. Set this value to '1' to
roll back the hotfix.
INSTALL_TYPE=0
# * The USER_INSTALL_DIR variable must point to a valid directory with write

# permissions enabled.
USER_INSTALL_DIR=c:\Informatica\10.5
#The INSTALLATION_ENVIRONMENT property represents the installation environment

# Set the property to one of the following installation environment types: Sandbox,
Development, Test, or Production. Values are case-sensitive.
# Set to Sandbox for a basic environment used for proof of concept with minimal
users.
# Set to Development for the design environment.
# Set to Test for high volume processing that is closest to a production environment.
# Set to Production for high volume processing with high levels of concurrency meant for
end users. Advanced production environments are typically multi-node setups.
INSTALLATION_ENVIRONMENT=
# Required only for EDC installation.

# Set EDC_CATALOG_INST=true if the Catalog Service is running on the node on which you
want to apply or roll back the hotfix.EDC_CATALOG_INST=true
# Required only for EDC installation.

# Set EDC_HF_BACKUP=true if you have set EDC_CATALOG_INST=true and you have taken a
backup of the catalog.
# Run the infacmd ldm backupContents command before you apply the hotfix (INSTALL_TYPE=0)
# Run the infacmd ldm restoreContents command before you rollback the hotfix
(INSTALL_TYPE=1
EDC_HF_BACKUP=true
# Enter the location of the backup file.

# Required for Enterprise Data Catalog installation when the EDC_CATALOG_INST and
EDC_HF_BACKUP parameters are set to true
EDC_BACK_UP_DIR=/home/ilmsatsqe/CSBackup/export.zip
# The INSTALL_HADOOP_LIBRARIES property determines whether to install packages to

integrate the domain with Hadoop or Databricks.
# Set INSTALL_HADOOP_LIBRARIES=true if you want to install integration packages along
with Informatica domain services.
# Set INSTALL_HADOOP_LIBRARIES property only if INSTALL_TYPE=0
# If you don't install the integration packages now, you can install them later through
Integration Package Manager.
INSTALL_HADOOP_LIBRARIES=false
# The SELECTED_HADOOP_LIBRARIES property determines the integration packages that you

want to install.
# Lists the supported integration packages and their versions.
# Set SELECTED_HADOOP_LIBRARIES property only if INSTALL_TYPE=0
# Enter the integration package that you want to install. Separate multiple packages
with a comma.
# You can choose from the following options:

# 1->Azure HDInsight 4.0
# 2->Cloudera 6.3
# 3->Cloudera 7.1
# 4->Cloudera 7.2
# 5->Databricks 7.2
# 6->Databricks 9.1
# 7->Dataproc 2.0
# 8->Elastic MapReduce 5.29
# 11->MapR 6.1
# 12->Select all
SELECTED_HADOOP_LIBRARIES=3
After you apply the hotfix

After you run the installer to apply the hotfix, start the domain and perform the post requisite tasks to
complete the hotfix application.
Complete the configuration for upgrade or apply hotfix

If you previously edited the odbc.ini, odbcinst.ini, sapnwrfc.ini, or infaservice.sh files, manually merge the
changes from the backup files into the latest installed files. Check with your administrator for any
customization to the *.ini files in the previous Informatica version. For example, if an administrator added
some variables or java options to the infaservice.sh script before you applied a hotfix or upgrade, manually
merge the changes to the latest install file paths.
Manually merge the latest configuration changes into the following install file paths after applying hotfix or
upgrade:
• <Informatica installation directory>/ODBC7.1/odbc.ini

• <Informatica installation directory> /ODBC7.1/odbcinst.ini
• <Informatica installation directory>/server/bin/sapnwrfc.ini
• <Informatica installation directory>/tomcat/bin/infaservice.sh
Remove the distribution packages from the backup location

After you apply the hotfix, remove the distribution packages from the backup folder to mitigate the security
vulnerabilities.
When you apply the hotfix, all the existing files in the Informatica installation directory are backed up. You
need to remove the distribution packages backup from the following location: <Informatica installation
directory>\BACK_FROM_<hotfix version number>\services\shared\hadoop\<distribution
package_version>
The following example shows the backup location for a distribution package when you apply the 10.5.3
hotfix: C:\Informatica\BACK_FROM_3\services\shared\hadoop\EMR_6.4
Note: The deletion process doesn't remove all files of the distribution packages from the backup folder.
Some files might still exist in the following location: <Informatica installation directory>
\BACK_FROM_<hotfix version number>\services\shared\ You can delete these files manually.
Important: When you roll back the hotfix, distribution packages are not restored. You can't enable the
functionalities associated with the Hadoop or Databricks distribution packages in the rolled-back version. To
install the distribution packages, contact Informatica Global Customer Support.

Rolling back the services hotfix
You can roll back the hotfix if required. To roll back the hotfix, run the installer.
Roll back the services hotfix in graphical mode

When you roll back the hotfix in graphical mode, a console window opens and runs in the background. If you
close this window, the rollback stops.
3. To begin the installation on Windows, run install.bat as administrator from the root directory where
you unzipped or untarred the hotfix package. To run the file as administrator, right-click install.bat and
select Run as administrator.
4. On the Informatica 10.5.3 page, select Apply the hotfix to Informatica 10.5, 10.5.1, or 10.5.2, and then
click Start.
5. Select Roll back the hotfix to roll back the hotfix.
conditions, and then click Next.
https://www.informatica.com/in/privacy-policy.html. You may disable usage collection in Administrator
tool.
The Installation Prerequisites page appears.
7. Verify that all requirements are met before you roll back the hotfix, and then click Next.
8. Enter the absolute path for the directory in which the current version of Informatica services is installed,
and then click Next.
9. Review the installation information, and then click Install to roll back the hotfix.
The installer removes the hotfix and restores Informatica to the previous version.
10. Complete the post-installation tasks. Verify that the rollback completed successfully by reviewing the log
functionalities associated with the Hadoop or Databricks distribution packages in the rolled-back
version. To install the distribution packages, contact Informatica Global Customer Support.
Roll back the services hotfix in console mode

You can roll back the hotfix that you applied. To roll back the hotfix in console mode, run the installer.
1. Run the installer using the ./install.sh command.
Rolling back the services hotfix 21

2. Press Y to confirm that you want to proceed with the installation.
3. Press 5 to roll back the hotfix.
4. Press 2 to roll back the hotfix.
5. Press 2 to accept the license.
6. Verify the prerequisites and press Enter.
7. Enter the directory where you installed Informatica and press Enter.
8. At the Pre-Installation Summary, press Enter to continue.
9. Press Enter to exit the installer when the rollback completes successfully.
Roll back the services hotfix in silent mode

To roll back the hotfix in silent mode, update the SilentInput.properties file and then run the silent installer.
parameters that are required by the installer.

INSTALL_TYPE Indicates whether to apply the hotfix or roll back the hotfix.
Set the value to 1 to roll back the current hotfix.
USER_INSTALL_DIR Directory for the Informatica installation where you want to roll back the hotfix.
ENABLE_USAGE_COLLECTION Enables the software to 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
https://www.informatica.com/in/privacy-policy.html. You may disable usage
collection in Administrator tool. For more information about how to disable
sending usage statistics, see the Informatica Administrator Guide.
You must set the value to 1 to roll back the hotfix.
INSTALLATION_ENVIRONMENT You can ignore the property during rollback.
EDC_CATALOG_INST Required for Enterprise Data Catalog, Data Privacy Management, and
Enterprise Data Preparation installations. Set the property to true if the Catalog
Service runs on the node on which you want to apply the hotfix.

EDC_HF_BACKUP Required for Enterprise Data Catalog, Data Privacy Management, and
Enterprise Data Preparation installations, if you have set
EDC_CATALOG_INST=true. Set the property to true if you have taken a backup
of the catalog.
EDC_BACK_UP_DIR Required for Enterprise Data Catalog, Data Privacy Management, and
Enterprise Data Preparation installations, if you set the EDC_CATALOG_INST
and EDC_HF_BACKUP properties to true. Enter the location of the catalog data
backup file.
5. Save the properties file with the name SilentInput.properties.

6. Go to root of the Informatica services installer directory.
7. Verify that the directory contains the SilentInput.properties file that you edited and saved.
8. Begin the installation from Windows, UNIX, or Linux.
• To roll back the hotfix on Windows, run the silentInstallHotFix.bat as administrator. To run the file as
administrator, right-click the file and select Run as administrator.
• To roll back the hotfix on UNIX or Linux, double-click silentInstallHotFix.sh.
The installer removes the last hotfix and restores the previous version of Informatica services.
9. Complete the post rollback tasks. Verify that the rollback completed successfully by reviewing the log
Applying the client hotfix

When you apply the hotfix, the installer backs up existing directories, applies the new version of the client,
You can run the client installer to apply a hotfix to Informatica clients that you use. After you apply the hotfix,
you can remove the backup files of the distribution packages from the backup folder.
Apply the client hotfix in graphical mode

When you run the installer in graphical mode, a console window opens and runs in the background. If you
close this window, the installation stops.
3. To begin the installation, run install.bat from the root directory where you unzipped or untarred the
client hotfix installation package.
4. On the Informatica 10.5.3 page, select Apply the hotfix to version 10.5, 10.5.1, or 10.5.2 or roll back the
hotfix, and then click Start.
Applying the client hotfix 23

5. Select Apply the hotfix to choose to apply the hotfix.
6. Verify that all requirements are met before you continue the hotfix, and then click Next.
7. Enter the absolute path for the directory in which the current version of the Informatica client is installed
and specify the installation environment.
install.
10. Click Next.
11. Review the installation information, and then click Install to apply the hotfix.
Apply the client hotfix in silent mode

To apply the hotfix in silent mode, create the SilentInput.properties file and then run the installer.
1. Go to the root of the directory that contains the client installation files.
INSTALL_TYPE Indicates whether to apply the hotfix or roll back the hotfix. If the value is 0,
the installer applies the hotfix to the current Informatica client installation. If
the value is 1, the installer rolls back the current hotfix.
Set the value to 0 to apply the hotfix.
USER_INSTALL_DIR Directory for the Informatica client installation where you want to apply or roll
back the hotfix.
To apply the hotfix, enter the absolute path for the directory in which the
current version of the Informatica clients is installed.

6. Double-click the silentInstallHotFix.bat to apply the hotfix.
The installer copies the Informatica client files to the installation directory.
Sample silent input properties

The following example shows the contents of the SilentInput.properties file when you apply or roll back
the hotfix client in silent mode.
##########################################################
# Informatica Installer Build Details
# Copyright (c) 1993-2021 Informatica LLC
# This software contains confidential and proprietary
# information of Informatica LLC.
# All Rights Reserved.
##########################################################
# Use the following guidelines when editing this file

# * Use this file to install without user interaction.
# * After you create the properties file, save the file with the name
SilentInput.properties
# * Any error condition that leads to failure, such as an invalid
# installation directory, generates a log file in the user home directory.
# For example: c:\silentErrorLog<time_stamp>.log
##########################################################
#######
## *INSTALL_TYPE - Set this value to '0' to apply the hotfix. Set this value to '1' to
roll back the hotfix.
INSTALL_TYPE=0
# * The USER_INSTALL_DIR variable must point to a valid directory with write

# permissions enabled.
USER_INSTALL_DIR=c:\Informatica\10.5
#######
# After you create the properties file, save the file with the name
SilentInput.properties and
# run the silent installer to perform the Informatica client installation.
#######
Remove the distribution packages from the backup location

After you apply the hotfix, remove the distribution packages from the backup folder to mitigate the security
vulnerabilities.
When you apply the hotfix, all the existing files in the Informatica installation directory are backed up. You
need to remove the distribution packages backup from the following location: <Informatica installation
directory>\BACK_FROM_<hotfix version number>\clients\DeveloperClient\hadoop\<distribution
package_version>
The following example shows the backup location for a distribution package when you apply the 10.5.3
hotfix: C:\Informatica\BACK_FROM_3\clients\DeveloperClient\hadoop\EMR_6.4
Note: The deletion process doesn't remove all files of the distribution packages from the backup folder.
Some files might still exist in the following location: <Informatica installation directory>
\BACK_FROM_<hotfix version number>\clients\DeveloperClient\ You can delete these files manually.
Applying the client hotfix 25

functionalities associated with the Hadoop or Databricks distribution packages in the rolled-back version. To
install the distribution packages, contact Informatica Global Customer Support.
Rolling back the client hotfix

You can roll back the hotfix if required. To roll back the hotfix, perform the required prerequisite tasks and
then run the installer.
Rolling back the client hotfix in graphical mode

When you run the installer in graphical mode, a console window opens and runs in the background. If you
close this window, the rollback stops.
3. To begin the installation, run install.bat from the root directory where you unzipped or untarred the
client hotfix installation package.
4. On the Informatica 10.5.3 page, select Apply the hotfix to version 10.5, 10.5.1, or 10.5.2 or roll back the
hotfix, and then click Start.
5. Select Roll back the hotfix to choose to roll back the hotfix.
6. Verify that all requirements are met before you continue the rollback, and then click Next.
7. Enter the absolute path for the directory in which the current version of Informatica clients is installed,
and then click Next.
8. Review the installation information, and then click Install to roll back the hotfix.
The installer removes the last hotfix and restores Informatica clients to the previous version.
Rolling back the client hotfix in silent mode

To roll back the hotfix in silent mode, create the SilentInput.properties file and then run the installer with the
file.

INSTALL_TYPE Indicates whether to apply the hotfix or roll back the hotfix. If the value is 0, the installer
applies the hotfix to the current Informatica client installation. If the value is 1, the
installer rolls back the current hotfix.
Set the value to 1 to roll back the hotfix.
USER_INSTALL_DIR Directory for the Informatica client installation where you want to roll back the hotfix.
Enter the absolute path for the directory in which the current version of the Informatica
clients is installed.
6. To roll back the hotfix on Windows, double-click the silentInstallHotFix.bat file.
The installer removes the last hotfix and restores the previous version of Informatica clients.
Rolling back the client hotfix 27

Chapter 3
Before You Upgrade the Domain

on Linux
• Read the Release Notes, 28

• Verify System Requirements, 28
• Download and Extract the Installer Files, 33
• Run the Informatica Upgrade Advisor, 34
• Back Up the Configuration Files, 35
Read the Release Notes

Read the Release Notes for updates to the installation and upgrade process. You can also find information
about known and fixed issues for the release.
Find the Release Notes on the Informatica documentation portal.
Verify System Requirements

Verify that your environment meets the minimum system requirements for the installation process, temporary
disk space, port availability, databases, and application service hardware.
For more information about product requirements and supported platforms, see the
Product Availability Matrix.
Verify Temporary Disk Space and Permissions

Verify that your environment meets the minimum system requirements for the temporary disk space,
permissions for the temporary files, and the Informatica client tools.
Disk space for the temporary files
The installer writes temporary files to the hard disk. Verify that you have 1 GB disk space on the machine
to support the installation. When the installation completes, the installer deletes the temporary files and
releases the disk space.
28
The following table describes the minimum disk space and memory requirements for PowerCenter or
Data Engineering product installation:
Options Minimum Requirements
Temporary disk space to run the 1 GB disk space

installer
Install with application services for 50 GB disk space, 8 GB RAM, and 8 cores. Out of the 50 GB, 25 GB is for
Data Engineering products the product installation binaries.
Install with application services for 50 GB disk space, 6 GB RAM, and 4 cores, Out of the 50 GB, 25 GB is for
PowerCenter the product installation binaries.
Permissions for the temporary files
Verify that you have read, write, and execute permissions on the /tmp directory.
Verify the Domain Upgrade Requirements

Complete the pre-upgrade tasks before you start the upgrade. Run the installer on all machines that host
previous versions of Informatica that you want to upgrade. In a multi-node domain, upgrade the gateway
nodes before you upgrade the worker nodes. Before you perform the upgrade, verify that the Informatica
domain truststore file contains only the TrustedCertEntry. You must delete all the PrivateKeyEntry entries
from the file.
Verify that your machine meets the minimum system requirements to upgrade the Informatica domain.
Ensure that you have a minimum disk space of 50 GB and a RAM of 6 GB to upgrade the Informatica domain.
Note: When you upgrade, the installer requires an additional disk space used by the existing infa_shared
directory.
Effective in version 10.5, Informatica increased the site key size from 128 bit to 256 bit. When you run the
Informatica installer, you also need to back up the site key generated since you cannot recover the generated
site key. You also do not need to provide the keyword and domain name when you generate the encryption
key. The generated site key should be copied to each node or should be placed at shared location, which is
accessible by each node. You must upgrade with the older site key when you run the upgrade installer.
Ensure that you migrate the site key after domain upgrade.
Verify Site Key

Verify the site key before you upgrade. Back up the generated site key and run the upgrade installer with the
older site key. After the domain upgrade, migrate the site key.
Effective in version 10.5, Informatica increased the site key size from 128 bit to 256 bit.
When you run the Informatica installer, back up the site key generated since you cannot recover the
generated site key. You do not need to provide the keyword and domain name when you generate the
encryption key.
Verify System Requirements 29

Copy the generated site key to each node or place the site key generated at shared location, which is
accessible by each node. When you run the upgrade installer. upgrade with the older site key.
After the domain upgrade, migrate the site key.
Review Patch Requirements on Linux

Before you install the Informatica services, verify that the machine has the required operating system
patches and libraries.
PowerCenter on Linux
The following table lists the patches and libraries that the Informatica services require for PowerCenter on
Linux:
Platform Operating System Operating System Patch
AWS Linux Linux 2 - 2.0.20220805.0 All of the following packages:

- e2fsprogs-libs-1.42.9-19.amzn2.x86_64
- keyutils-libs-1.5.8-3.amzn2.0.2.x86_64
- libsepol-2.5-8.1.amzn2.0.2.x86_64
- libselinux-2.5-12.amzn2.0.2.x86_64
Ubuntu 20.04.1 All of the following packages:

- e2fsprogs/focal,now 1.45.5-2ubuntu1 amd64 [installed]
- libkeyutils1/focal,now 1.6-6ubuntu1 amd64 [installed,automatic]
- libselinux1/focal,now 3.0-1build2 amd64 [installed,automatic]
- libsepol1/focal,now 3.0-1 amd64 [installed,automatic]
Ubuntu 18.04 All of the following packages:

- libkeyutils1/focal,now 1.5.9-9.2ubuntu2 amd64 [installed,automatic]
- libsepol1/focal,now 2.7-1ubuntu0.1 amd64 [installed,automatic]
Linux-x64 Red Hat Enterprise Linux All of the following packages, where <version> is any version of the
7.3 package:
- e2fsprogs-libs-<version>.el7
- keyutils-libs-<version>.el7
- libselinux-<version>.el7
- libsepol-<version>.el7
8 package:
Linux-x64 SUSE Linux Enterprise Service Pack 2

Server 12
Linux-x64 SUSE Linux Enterprise Service Pack 0 and Service Pack 1.

Server 15
30 Chapter 3: Before You Upgrade the Domain on Linux

Data Engineering on Linux
The following table lists the patches and libraries that the Informatica services require on Linux:
Platform Operating System Operating System Patch
AWS Linux Linux 2 - 2.0.20220805.0 All of the following packages:

- e2fsprogs-libs-1.42.9-12.amzn2.0.2.x86_64
- keyutils-libs-1.5.8-3.amzn2.0.2.x86_64
- libselinux-2.5-12.amzn2.0.2.x86_64
- libsepol-2.5-8.1.amzn2.0.2.x86_64
Ubuntu 20.04.1 All of the following packages:

- libkeyutils1/focal,now 1.6-6ubuntu1 amd64 [installed,automatic]
- libsepol1/focal,now 3.0-1 amd64 [installed,automatic]
Ubuntu 18.04 All of the following packages:

- libkeyutils1/focal,now 1.5.9-9.2ubuntu2 amd64 [installed,automatic]
- libsepol1/focal,now 2.7-1ubuntu0.1 amd64 [installed,automatic]
6.7 package:
7.3 package:
8 package:
Linux-x64 SUSE Linux Enterprise Service Pack 2

Server 12
Linux-x64 SUSE Linux Enterprise Service Pack 0 and Service Pack 1.

Server 15
Verify Distribution Package Requirements (Linux and UNIX)

You can use third-party distribution packages to integrate the Informatica domain with the Hadoop or
Databricks environment.
Verify System Requirements 31

Process within the Informatica domain

The following adapters require distribution packages for processing within the Informatica domain:
• PowerExchange for Amazon S3

• PowerExchange for Google Cloud Storage
• PowerExchange for Google Cloud Storage for PowerCenter
• PowerExchange for Hadoop for PowerCenter
• PowerExchange for HBase
• PowerExchange for HDFS
• PowerExchange for Hive
• PowerExchange for JDBC V2
• PowerExchange for Kafka for PowerCenter
• PowerExchange for MapR-DB
• PowerExchange for Microsoft Azure Blob Storage
• PowerExchange for Microsoft Azure Data Lake Storage Gen1
Process with Hadoop or Databricks environment

When you push processing to the Hadoop or Databricks environment, the Informatica domain and client
require distribution packages. For more information about the supported distribution packages, see the
Review the Environment Variables

Configure the environment variables to work with the Informatica installation.
The following table describes the environment variables to review:
Variable Description
IATEMPDIR Location of the temporary files created during installation. Informatica

requires 1 GB disk space for temporary files.
Configure the environment variable if you do not want to create temporary files
in the /tmp directory.
INFA_DOMAINS_FILE Contains the location of the domains.infa file. Clear this variable before you
start the upgrade.
INFA_HOME Contains the location of the Informatica installation directory. Clear this
variable before you start the upgrade.

LANG and LC_ALL Change the locale to set the appropriate character encoding for the terminal
session. For example, set the encoding to Latin1 or ISO-8859-1 for French,
EUC-JP or Shift JIS for Japanese, or UTF-8 for Chinese or Korean. The
character encoding determines the types of characters that appear in the UNIX
terminal.
DISPLAY Unset the DISPLAY environment before you run the installer. Installation might
fail if the DISPLAY environment variable has some value.
Library path Verify that the library path environment variables do not contain earlier
versions of Informatica.
PATH Verify that the PATH environment variables do not contain earlier versions of
Informatica.
SKIP_VENDOR_CHECK Configure the environment variable to remove the sudo prompt from the
installer on Linux or AIX.
Set the environment variable to true to remove the sudo prompt from the
upgrade installer on Linux or AIX.
Note: If you don't have sudo privileges, set the environment variable to true
before you upgrade. If you have sudo privileges, you don't need to set the
environment variable.
Download and Extract the Installer Files

distribution packages from the FTP link contained in your fulfillment email.
Download the Informatica installation tar file and the required distribution package ZIP files from the
Informatica Electronic Software Download site. You can download them to a local directory or a shared
network drive that is mapped on your machine.
Extract the Informatica installer files to a directory on your machine. The user that runs the installer must
have read and write permissions on the installer files directory and execute permissions on the executable
file.
Note: Ensure that you extract the installer files to a local directory as you can't run the installer from a
mapped file.
Copy the ZIP files of the distribution packages to the following location: <Informatica installer files>/
source
Verify Installer Package Checksum on Linux

Before you run the upgrade installer for the Informatica services, verify the install package integrity through
the cksum command. The cksum command calculates the checksum value for the installer.
Verify the checksum for the specific installer files against the checksum of the installation files downloaded
from the Informatica Electronic Software Download site.
Download and Extract the Installer Files 33

The following table lists the checksum and file size for the Informatica services installer for Linux:
File Checksum Value File Size
informatica_1053_server_linux-x64.tar 2154528627 11639828480
A checksum mismatch can occur when there are data errors during download due to network issues or when
data corruption occurs in the file on disk. For more information about the checksum errors, see
HOW TO: Identify file errors after downloading Informatica installation files.
Run the Informatica Upgrade Advisor

Before you perform an upgrade, run the Informatica Upgrade Advisor to validate the services and check for
obsolete services, supported database, and supported operating system in the domain.
Note: If you do not change the node configuration, you can run the Informatica Upgrade Advisor before you
upgrade. If you run Informatica Upgrade Advisor before you migrate to a node with a different configuration,
you might notice some database or node configuration failures that you can ignore.
Before you upgrade with changes to the domain configuration repository database, run i10Pi from the
Informatica installer to review the installation support for the new database type, database version, operating
system, or machine. For more information about the i10Pi configuration, see the Informatica Installation
Guide.
1. Log in to the machine with a system user account.

2. Verify that the domain and the services are running before you run the Informatica Upgrade Advisor.
3. On a shell command line, run the install.sh file from the root directory.
The installer displays the message to verify that the locale environment variables are set.
4. If the environment variables are not set, press n to exit the installer and set them as required.
If the environment variables are set, press y to continue.
5. Press 2 to Upgrade Informatica.
6. Press 1 to run the Informatica Upgrade Advisor.
The Welcome section appears.
7. Press Enter.
The Installation Directory section appears.
8. Enter the current installation directory.
9. Press Enter.
The Domain and Node Configuration section appears.

10. Enter the following domain information:
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: ` % * + ; " ? , < > \ /
Gateway node Host name of the machine that hosts the gateway node for the domain.
host name
Gateway node Port number of the gateway node.

port name
Domain user User name for the domain administrator. You can use this user name to initially log in to
name Informatica Administrator. Use the following guidelines:
The name is not case sensitive and cannot exceed 128 characters.
The name cannot include a tab, newline character, or the following special characters: % *
+ / ? ; < >-
The name can include an ASCII space character except for the first and last character. Other
space characters are not allowed.
Domain Password for the domain administrator. The password must be more than 2 characters and
password must not exceed 16 characters.
Not available if you configure the Informatica domain to run on a network with Kerberos
authentication.
11. Press Enter.

The Infomatica Upgrade Advisor Summary section appears.
12. Review the results of the advisor in the following log file: Summary_<timestamp>.log
13. Press Enter to close the Informatica Upgrade Advisor.
Back Up the Configuration Files

If any of the configuration files contain customization, updated, or new properties, back up the installation
configuration files.
Back Up the Configuration Files 35

Chapter 4

on UNIX

• Review Patch Requirements on UNIX, 37
• Install the Java Runtime Environment for AIX, 37
• Verify the Domain Upgrade Requirements, 37
• Verify Distribution Package Requirements (Linux and UNIX), 38
• Review the Environment Variables, 39
• Review the Maximum Heap Size , 40


36
Review Patch Requirements on UNIX
Before you install the Informatica services, verify that the machine has the required operating system
patches and libraries.
PowerCenter on UNIX
The following table lists the patches and libraries that the Informatica services require for PowerCenter on
UNIX:
Platform Compiler Version Operating System Operating System Patch
AIX 16 7.1 TL5 OS level: 7100-05

bos.adt.debug Version 7.1.5.32
AIX 16 7.2 TL4 OS level: 7200-04

bos.adt.debug Version 7.2.4.0
Install the Java Runtime Environment for AIX

Informatica doesn't ship the Java libraries for AIX. Before you install Informatica on AIX, you must download
the Java Runtime Environment build 8.0.7.11 - pap6480sr7fp11-20220601_01(SR7 FP11)
Download the following file: Java8_64_installp_8.0.0.711.tar.gz
If you have problems installing the JRE, contact the JRE vendor.
The software available for download at the referenced links belongs to a third party or third parties, not
Informatica. The download links are subject to the possibility of errors, omissions or change. Informatica
assumes no responsibility for such links and/or such software, disclaims all warranties, either express or
implied, including but not limited to, implied warranties of merchantability, fitness for a particular purpose,
title and non-infringement, and disclaims all liability relating thereto.

from the file.
Ensure that you have a minimum disk space of 50 GB and a RAM of 6 GB to upgrade the Informatica domain.
directory.
Review Patch Requirements on UNIX 37

Temporary Disk Space Requirements
The installer writes temporary files to the hard disk. Verify that you have enough available disk space on the
machine to support the installation. When the installation completes, the installer deletes the temporary files
and releases the disk space.
The installer requires 1 GB of temporary disk space.
Verify Site Key

encryption key.
Verify Distribution Package Requirements (Linux and

UNIX)
You can use third-party distribution packages to integrate the Informatica domain with the Hadoop or
Databricks environment.
Process within the Informatica domain


• PowerExchange for Hadoop for PowerCenter
• PowerExchange for HBase
• PowerExchange for HDFS
• PowerExchange for Hive
38 Chapter 4: Before You Upgrade the Domain on UNIX

• PowerExchange for JDBC V2
• PowerExchange for MapR-DB
Process with Hadoop or Databricks environment

When you push processing to the Hadoop or Databricks environment, the Informatica domain and client
require distribution packages. For more information about the supported distribution packages, see the

The following table describes the environment variables to review on UNIX:
IATEMPDIR Location of the temporary files created during installation. Informatica

in the /tmp directory.
start the upgrade.
INFA_JRE_HOME Location of the folder containing the supported Java Runtime Environment
(JRE).If you are installing Informatica on AIX, set the INFA_JRE_HOME
In the configuration file for your shell, for example the .bashrc file, set the
INFA_JRE_HOME environment variable to the directory that contains the JRE.
Verify that the login shell can access the INFA_JRE_HOME environment
variable.
JRE_HOME If you install the Informatica services on a UNIX machine, clear the JRE_HOME
environment variable before you start the installation.
LANG and LC_ALL Change the locale to set the appropriate character encoding for the terminal
session. For example, set the encoding to Latin1 or ISO-8859-1 for French,
EUC-JP or Shift JIS for Japanese, or UTF-8 for Chinese or Korean. The
character encoding determines the types of characters that appear in the UNIX
terminal.
Review the Environment Variables 39

Informatica.
SKIP_VENDOR_CHECK Configure the environment variable to remove the sudo prompt from the
installer on UNIX.
Set the environment variable to true to remove the sudo prompt from the
upgrade installer on UNIX.
Note: If you don't have sudo privileges, set the environment variable to true
before you upgrade. If you have sudo privileges, you don't need to set the
Review the Maximum Heap Size

Verify that Informatica Services uses the required maximum heap size for the number of users in the domain.
The following table lists the minimum requirement for the maximum heap size settings, based on the number
of users and services in the domain:
Number of Domain Users Maximum Heap Size Maximum Heap Size

(1-5 Services) (6-10 Services)
1,000 or less 512 MB (default) 1024 MB
5,000 2048 MB 3072 MB
10,000 3072 MB 5120 MB
20,000 5120 MB 6144 MB
30,000 5120 MB 6144 MB
Note: The maximum heap size settings in the table are based on the number of application services in the
domain.
If the domain has more than 1,000 users, update the maximum heap size based on the number of users in the
domain.
1. Extract the installation files.

2. Go to the following directory:<installer files directory>/source/tomcat/bin.
3. Use a text editor to open the infaservice file.
4. Search for the following text: INFA_JAVA_OPTS=% INFA_JAVA_OPTS% -XX.
5. Set the value for -Xmx to the maximum heap size required for the number of Informatica domain users.
For example, to set the maximum heap size to 3072 MB, use the following configuration:
set INFA_JAVA_OPTS=% INFA_JAVA_OPTS% -XX:GCTimeRatio=9 -Xmx3072m

file.
mapped file.
source
Verify Installer Package Checksum on UNIX

Before you run the services installer, verify the install package integrity through the cksum command. The
cksum command calculates the checksum value for the installers.
The following table lists the checksum and file size for the Informatica services for UNIX:
informatica_1053_server_linux-x64.tar 2154528627 11639828480
informatica_1053_server_aix-ppc64.tar 561493064 10006200320

Download and Extract the Installer Files 41

Guide.
1. Log in to the machine with a system user account.

5. Press 2 to Upgrade Informatica.
The Welcome section appears.
7. Press Enter.
The Installation Directory section appears.
9. Press Enter.
The Domain and Node Configuration section appears.
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: ` % * + ; " ? , < > \ /
Gateway node Host name of the machine that hosts the gateway node for the domain.
host name
Gateway node Port number of the gateway node.

port name
Domain user User name for the domain administrator. You can use this user name to initially log in to
name Informatica Administrator. Use the following guidelines:
The name is not case sensitive and cannot exceed 128 characters.
The name cannot include a tab, newline character, or the following special characters: % *
+ / ? ; < >-
The name can include an ASCII space character except for the first and last character. Other
space characters are not allowed.
Domain Password for the domain administrator. The password must be more than 2 characters and
password must not exceed 16 characters.
Not available if you configure the Informatica domain to run on a network with Kerberos
authentication.
11. Press Enter.

The Infomatica Upgrade Advisor Summary section appears.
13. Press Enter to close the Informatica Upgrade Advisor.

Back Up the Configuration Files 43

Chapter 5

on Windows

• Verify the Domain Upgrade Requirements, 45
• Verify Distribution Package Requirements (Windows), 46
• Review the Environment Variables, 46
• Review the Maximum Heap Size, 47


44
from the file.
The following table lists the minimum memory and disk space required to upgrade the Informatica domain:
RAM Disk Space
6 GB 50 GB
directory.
The following table lists the minimum system requirements to run the Informatica client tools:
Effective in version 10.5, Informatica increased the site key size from 128 bit to 256 bit. When you run the
Informatica installer, you also need to back up the site key generated since you cannot recover the generated
site key. You also do not need to provide the keyword and domain name when you generate the encryption
key. The generated site key should be copied to each node or should be placed at shared location, which is
accessible by each node. You must upgrade with the older site key when you run the upgrade installer.
Ensure that you migrate the site key after domain upgrade.
Verify Temporary Disk Space and Permissions

Verify that your environment meets the minimum system requirements for the temporary disk space,
permissions for the temporary files, and the Informatica client tools.
Disk space for the temporary files
The installer writes temporary files to the hard disk. Verify that you have 1 GB disk space on the machine
to support the installation. When the installation completes, the installer deletes the temporary files and
releases the disk space.
The following table describes the minimum disk space and memory requirements for PowerCenter or
Data Engineering product installation:
Options Minimum Requirements
Temporary disk space to run the 1 GB disk space

installer
Install with application services for 50 GB disk space, 8 GB RAM, and 8 cores. Out of the 50 GB, 25 GB is for
Data Engineering products the product installation binaries.
Install with application services for 50 GB disk space, 6 GB RAM, and 4 cores, Out of the 50 GB, 25 GB is for
PowerCenter the product installation binaries.
Verify the Domain Upgrade Requirements 45

Permissions for the temporary files
Verify that you have read, write, and execute permissions on the /tmp directory.
Verify Site Key

encryption key.
Verify Distribution Package Requirements (Windows)

domain or to connect to Hadoop or Databricks environment when you process within the domain.


46 Chapter 5: Before You Upgrade the Domain on Windows

The following table describes environment variables to review on Windows:
%TEMP% Location of the temporary files created during installation. Informatica

in the default drive.
Informatica.
start the upgrade.
Review the Maximum Heap Size

Verify that Informatica Services uses the required maximum heap size for the number of users in the domain.
The following table lists the minimum requirement for the maximum heap size settings, based on the number
of users and services in the domain:
Number of Domain Users Maximum Heap Size Maximum Heap Size

(1-5 Services) (6-10 Services)
1,000 or less 512 MB (default) 1024 MB
5,000 2048 MB 3072 MB
10,000 3072 MB 5120 MB
20,000 5120 MB 6144 MB
30,000 5120 MB 6144 MB
Note: The maximum heap size settings in the table are based on the number of application services in the
domain.
If the domain has more than 1,000 users, update the maximum heap size based on the number of users in the
domain.
1. Extract the installation files.

2. Go to the following directory:<installer files directory>/source/tomcat/bin.
Review the Maximum Heap Size 47

3. Use a text editor to open the infaservice file.
4. Search for the following text: INFA_JAVA_OPTS=% INFA_JAVA_OPTS% -XX.
5. Set the value for -Xmx to the maximum heap size required for the number of Informatica domain users.
For example, to set the maximum heap size to 3072 MB, use the following configuration:
set INFA_JAVA_OPTS=% INFA_JAVA_OPTS% -XX:GCTimeRatio=9 -Xmx3072m

file.
mapped file.
source
Verify Installer Package Checksum on Windows

Before you run the services installer, verify the install package integrity through the cksum command. The
cksum command calculates the checksum value for the installer.
The following table lists the checksum and file size for Informatica services on Windows:
informatica_1053_server_winem-64t. 3333101514 10112422360

zip

Guide.
1. Log in to the machine with the same user account that you used to install the previous version.
3. Go to the root of the directory for the installation files and run install.bat as administrator. To run the
file as administrator, right-click the install.bat file and select Run as administrator.
The Informatica 10.5.3 page appears.
4. Select Upgrade to Informatica 10.5.3
By default, the installer selects Run the Informatica Upgrade Advisor to validate the services and check
for obsolete services, supported database, and supported operating system in the domain before you
perform an upgrade.
5. Click Start.
The Welcome page appears.
6. Click Next.
8. Click Next.
The Domain and Node Configuration page appears.
Domain name Name of the domain.
Gateway node host name Host name of the machine that hosts the gateway node for the domain.
Gateway node port name Port number of the gateway node.
Domain user name User name for the domain administrator.
Domain password Password for the domain administrator.
10. Click Next.

The Infomatica Upgrade Advisor Summary page appears.
12. Click Done to close the Informatica Upgrade Advisor.
Run the Informatica Upgrade Advisor 49


Chapter 6
Prepare for the Upgrade

• Back Up the Data Transformation Files, 51

• Prepare the PowerCenter Repository, 52
• Back Up the Model Repository, 52
• Prepare the Data Integration Service, 52
• Prepare the Profiling Warehouse, 52
• Prepare the Reference Data Directories, 52
• Prepare Metadata Manager, 53
• Back Up Databases, 53
• Prepare the Domain, 54
Back Up the Data Transformation Files

Before you upgrade, you must back up the Data Transformation files that were created under previous
versions. After you complete the upgrade, copy the files to the new installation directories to get the same
custom global components as in the previous version.
The following table lists the files or directories that you must back up:
File or Directory Default Location
Repository <Informatica installation directory>\DataTransformation\ServiceDB
Custom Global <Informatica installation directory>\DataTransformation\autoInclude\user

Components directory
(TGP files)
Custom Global <Informatica installation directory>\DataTransformation\externLibs\user

(DLL and JAR files)
Configuration file <Informatica installation directory>\DataTransformation\CMConfig.xml
License file <Informatica installation directory>\DataTransformation\CDELicense.cfg
Do not copy the Data Transformation Library files. Instead, install the Data Transformation Libraries again.
51
Prepare the PowerCenter Repository
Before you upgrade the domain, back up the PowerCenter repository.
To back up a PowerCenter repository, select the PowerCenter Repository Service in the Administrator tool. On
the Domain actions menu, select Repository Contents > Backup.
Back Up the Model Repository

Back up the contents of the Model repository using the Administrator tool.
To back up the Model repository, select the Model Repository Service in the Administrator tool. Then, on the
Domain Actions menu, click Repository Contents > Backup.
Prepare the Data Integration Service

Before you upgrade the domain, verify that all the running jobs are complete. The Data Integration Service
cannot recover a workflow that you interrupt during the upgrade process.
Prepare the Profiling Warehouse

Before you upgrade the domain, back up the profiling warehouse.
Use the native database backup option to back up the profiling warehouse.
Prepare the Reference Data Directories

If you install or copy any reference data file to a non-default directory, back up the directory before you
upgrade.
If you install or copy any reference data file to a directory outside the installation directory structure, you do
not need to back up the directory.
By default, the upgrade operation preserves the contents of the following reference data directories:
• <Informatica installation directory>/services/DQContent/INFA_Content/dictionaries/

Parent directory for the reference dictionary files.
• <Informatica installation directory>/services/DQContent/INFA_Content/av/
Parent directory for the address reference data files.
• <Informatica installation directory>/services/DQContent/INFA_Content/identity/
Parent directory for the identity population data files.
52 Chapter 6: Prepare for the Upgrade

Record the directory location, so that you can restore the directory to the directory structure after you
upgrade.
Prepare Metadata Manager

Before you upgrade the domain, prepare Metadata Manager.
1. Back up the Metadata Manager warehouse.

2. Disable the Metadata Manager Service.
3. Back up the Metadata Manager properties file.
Back Up the Metadata Manager Warehouse

Before you upgrade the domain, back up the Metadata Manager warehouse.
Use the native database backup option or the Metadata Manager mmRepoCmd command line program to
back up the Metadata Manager warehouse.
mmRepoCmd includes commands to back up and restore the Metadata Manager warehouse. mmRepoCmd is
in the following directory:
<Informatica services installation directory>\services\MetadataManagerService\utilities

\mmrepocmd
To back up the Metadata Manager warehouse, use the mmRepoCmd backupRepository command. The
backupRepository command uses the following syntax:
mmRepoCmd backupRepository
[<-dn|--domainName> domainName]
[<-hp|--gateway> gateway_host1:port gateway_host2:port...]
[<-mm|--mmServiceName> mmServiceName]
<<-url> http(s)://<host>:<port>>
<<-u|--user> user>
[-ep|--encryptedPassword]
[<-pw|--password> password]
[<-n|--namespace> namespace]
[<-kt|--keyTab> keyTab]
<<-f|--file> file>
[<-nt|--numThreads> numThreads]
Back Up the Metadata Manager Properties File

Before you upgrade the domain, back up the Metadata Manager properties file.
The imm.properties file is in the following directory:
<Informatica installation directory>\services\shared\jars\pc\classes
Back Up Databases
Before you upgrade the domain, back up the profiling warehouse, reference data warehouse, and workflow
databases.
Prepare Metadata Manager 53

Prepare the Domain
Before you upgrade the domain, complete the steps to prepare the domain.
Shut Down the Domain

You can stop all the application services before you shut down the domain.You must shut down the domain
before you back up domain and then upgrade the domain.
To shut down the domain, stop the Informatica service process on each node in the domain.
You can stop the Informatica service process on each node using one of the following methods based on the
supported environment:
• To stop the Informatica from the Windows Start menu, click Programs > Informatica[Version] > Server >
Stop Informatica Services.
• To stop Informatica on UNIX, you use the infaservice command. By default, the infaservice executable file
is installed in the following directory:
<Informatica installation directory>/tomcat/bin
Enter the following command to stop the daemon:
infaservice shutdown
You can also stop the Informatica service from the Windows control panel or from the Administrator tool
based on the supported environment.
Back Up the Domain

Before you upgrade the domain, you must back up the configuration metadata for the domain.
Complete the following steps to back up the domain:
• Run the infasetup BackupDomain command to back up the domain configuration database tables to a file.
• Back up the metadata configuration files to any directory accessible by the machines where you install
Informatica.
Informatica infasetup includes command line programs to back up and restore the domain. infasetup is
located in the following directory:
<Informatica installation directory>/isp/bin
To back up the domain with infasetup, use the following syntax:
BackupDomain
<<-DatabaseAddress|-da> database_hostname:database_port|
<-DatabaseConnectionString|-cs> database_connection_string>
<-DatabaseUserName|-du> database_user_name
<-DatabasePassword|-dp> database_password
<-DatabaseType|-dt> database_type
[<-DatabaseServiceName|-ds> database_service_name]
<-BackupFile|-bf> backup_file_name
[<-Force|-f>]
<-DomainName|-dn> domain_name
54 Chapter 6: Prepare for the Upgrade

[<-Tablespace|-ts> tablespace_name (used for IBM DB2 only)]
[<-SchemaName|-sc> schema_name (used for Microsoft SQL Server only)]
[<-DatabaseTlsEnabled|-dbtls> database_tls_enabled]
[<-DatabaseTruststorePassword|-dbtp> database_truststore_password]
[<-TrustedConnection|-tc> trusted_connection (used for Microsoft SQL Server only)]
[<-EncryptionKeyLocation|-kl> encryption_key_location]
Back up the metadata configuration files to any directory accessible by the machines where you install
Informatica. The following table describes the metadata files and the locations where you can find them:
Metadata File Description
nodemeta.xml Contains metadata for a node.

Stored in the isp/config directory on each node in the domain.
If you use the same backup directory name on all the nodes, rename nodemeta.xml before copying it
to the backup location.
For example, you back up nodemeta.xml to the /nodebak directory on nodeA and nodeB. Rename the
configuration files so that on nodeA the file is backed up to /nodebak/nodemeta_A.xml, and on
nodeB the file is backed up to /nodebak/nodemeta_B.xml.
domains.infa Contains connectivity information for the gateway nodes.

Stored in one of the following locations:
- The Informatica installation directory on the client and server machines.
- The location configured through the INFA_DOMAINS_FILE environment variable.
Prepare the Domain 55

Chapter 7
Upgrade the Domain

• Upgrade the Informatica Domain , 56

• Upgrade in Graphical Mode, 56
• Upgrade in Console Mode, 67
• Upgrade in Silent Mode, 69
• Troubleshooting the Domain Upgrade, 72
Upgrade the Informatica Domain

The upgrade wizard reads the domain information from files in the previous version and uses the same
settings to configure the domain and server files for the upgrade. It upgrades the tables of the domain
configuration repository in the same database as the previous version. You can upgrade in graphical,
console, or silent mode.
You can perform the upgrade from the directory where you downloaded the installation files.
Upgrade in Graphical Mode

You can upgrade the domain in graphical mode on Windows.
2. Stop all processes that access the directory and subdirectories of the Informatica product to upgrade,
including command prompts and tail logs.
3. Go to the root of the directory for the installation files and run install.bat as administrator.
To run the file as administrator, right-click the install.bat file and select Run as administrator.
On Windows, if you encounter problems when you run the install.bat file from the root directory, run
install.exe from the following location:
<Informatica installation directory>/server/install.exe
Note: If you do not run the installer as administrator, the Windows system administrator might not be
able to access files in the Informatica installation directory.
56
4. Select Upgrade to Informatica 10.5.3.
Informatica provides utilities to facilitate the Informatica services installation process. You must run the
Informatica Upgrade Advisor utility before you upgrade. Informatica Upgrade Advisor validates the
services and checks for obsolete services in the domain before you perform an upgrade. For more
information about the Informatica Upgrade Advisor, see “Run the Informatica Upgrade Advisor” on page
49.
5. Click Start.
conditions. Subject to your opt-out rights described below, the software will automatically transmit to
Informatica in the USA the 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 available at https://
www.informatica.com/in/privacy-policy.html. You can disable usage collection in the Administrator tool.
Upgrade in Graphical Mode 57

Informatica DiscoveryIQ is a product usage tool that sends routine reports on data usage and system
statistics to Informatica. Informatica DiscoveryIQ uploads data to Informatica 15 minutes after you
install and configure Informatica domain. Thereafter, the domain sends the data every 30 days. You can
choose to disable usage statistics from the Administrator tool.
7. The Upgrade Prerequisites page appears.
58 Chapter 7: Upgrade the Domain

Verify the requirements before you continue the upgrade.
8. Click Next.

The Upgrade Directory page appears.
9. Enter the directory of the Informatica version that you want to upgrade and the directory where you want
to install Informatica 10.5.3
The following table describes the directories that you must specify:
Directory Description
Directory of the Informatica Directory that contains the version of Informatica services that you want to
product to upgrade upgrade.
Directory for Informatica Directory in which to install Informatica .

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: @|* $ # ! % ( ) { } [ ] , ; '
Note: 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.
10. Verify that the Allow changes to the node host name and port numbers option is not selected.
install.

13. Click Next.
The Domain Security - Encryption Key page appears.
14. 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.
Note: All nodes in an Informatica domain use the same keyword and encryption key. You must keep the
name of the domain, the keyword for the encryption key, and the encryption key file in a secure location.
The encryption key is required when you change the encryption key of the domain or move a repository
to another domain.
Encryption key Directory in which to store the encryption key for the domain. By default, the encryption
directory key is created in the following directory: <Informatica installation
directory>/isp/config/keys.
15. Enter the user name and password for the Informatica domain.
16. Click Next.

17. Review the upgrade information, and click Install to continue.

The upgrade wizard installs the Informatica server files to the Informatica 10.5.3 installation directory.
The upgrade wizard displays a warning to shut down the Informatica domain before you continue the
upgrade.
18. Click OK.

The Domain Configuration Repository Upgrade page appears.
If you are upgrading a gateway node, the upgrade wizard displays the database and user account
information for the domain configuration repository to be upgraded.
If you are upgrading a worker node, the upgrade wizard does not display the domain configuration
repository information. You cannot modify the database connection information.
The following table describes the properties that the installer displays for the domain configuration
repository:
Database type Database for the domain configuration repository.
Database user ID Database user account for the domain configuration repository.
User password Password for the database user account.
The upgrade wizard displays the database connection string for the domain configuration repository
based on how the connection string of the previous version was created at installation:
• If the previous version used a JDBC URL at installation, the upgrade wizard displays the JDBC
connection properties, including the database address and service name.
Optionally, you can specify additional JDBC parameters to include in the JDBC URL. To provide
additional JDBC parameters, select JDBC parameters and enter a valid JDBC parameter string.

• If the previous version used a custom JDBC connection string at installation, the upgrade wizard
displays the custom connection string.
You cannot specify additional JDBC parameters.
19. Click Test Connection to verify that you can connect to the database, and then click OK to continue.
20. On the Domain and Node Configuration page, enter the domain name, node name, node host name, and
node port number. If you use a custom keystore file for HTTPS configuration, enter the custom keystore
password and keystore file.
21. Click Next.

The Port Configuration Upgrade page appears.
22. On the Port Configuration Upgrade page, enter the start and shutdown port numbers for the Service
Manager and Administrator tool.

23. Click Next.

The Windows Service Configuration page appears.
On Windows, the upgrade wizard creates a service to start Informatica. By default, the service runs under
the same user account as the account used for installation. You can run the Windows service under a
different user account.
24. Select to run the Windows service or under a different user account.
Enter the following user account information:
Run Informatica under a Indicates whether to run the Windows service under a different user account.
different user account
User name User account with which to run the Informatica Windows service.
Use the following format:
<domain name>\<user account>
This user account must have the Act as operating system permission.
Password Password for the user account with which to run the Informatica Windows service.
25. Click Next.

The Post-Installation Summary page appears.
26. Click Done to complete the installation procedure and exit the installer.
Review the upgrade.log file to get more information about the tasks performed by the upgrade wizard and to
view the configuration of installed components.

Upgrade in Console Mode
You can upgrade in console mode on UNIX or Linux.
When you run the installer in console mode, the words quit, back, and help are reserved words. Do not use
them as input text.
3. On a shell command line, run the install file.
5. Press 2 to upgrade Informatica.
Informatica provides utilities to facilitate the Informatica services installation process. You can run the
utility before you upgrade Informatica services. The Informatica Upgrade Advisor helps to validate 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.
7. Read the terms and conditions of Informatica product usage toolkit and press 2 to continue the upgrade.
the USA the 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
https://www.informatica.com/in/privacy-policy.html. You can disable usage collection in the
Administrator tool.
8. The Upgrade Prerequisites page displays the upgrade system requirements.
9. Review the upgrade information and press Enter to continue.
The Upgrade Directory panel appears.
10. At the prompt, enter the directory of the Informatica version you want to upgrade and the directory in
which you want to upgrade to Informatica 10.5.3.
Upgrade in Console Mode 67

The following table describes the directories you must specify:
Directory for Informatica Directory in which to install Informatica 10.5.3.

10.5.3 Enter the absolute path for the installation directory. The directory cannot be the
Note: If you use a special character such as á or €, unexpected results might
occur at run time.
11. From the following installation options, select the upgrade environment based on your requirement:
• Sandbox. Used for proof of concepts or as a sandbox with minimal users.
• Development. Used for a design environment.
• Test. Used for high-volume processing environment that resembles a production environment.
• Production. Used for production environments with high-volume processing and high levels of
concurrency meant for end users.
12. Select if you want to change the node host name, port numbers, or domain configuration repository.
Press 1 to use the same node configuration as the previous version. Press 2 to change the node
configuration.
The Component Selection panel appears.
13. Press 1 to upgrade Informatica services.
Default is 1.
Default is 1.
16. Press Enter.
The Domain Security Encryption Key panel appears.
17. Enter the directory for the encryption key for the Informatica domain.

to another domain.
18. Enter the user name and password for the Informatica domain.
The Pre-installation Summary page appears.
After the domain upgrade completes, the Domain Configuration Repository panel appears.
20. Press Enter to continue the upgrade.
The installer copies the server files to the Informatica 10.5.3 installation directory.
The installer displays the database and user account information for the domain configuration repository
to upgrade. It displays the database connection string for the domain configuration repository based on
how the connection string of the previous version was created at installation:
• If the previous version used a JDBC URL at installation, the installer displays the JDBC connection
properties, including the database address and service name.
• If the previous version used a custom JDBC connection string at installation, the installer displays the
custom connection string.
21. If you use a JDBC URL, you can specify additional parameters to include in the connection string.
If you use a custom connection string, you cannot specify additional parameters.
22. Review the information and press Enter.
The upgrade completes and the Post-installation Summary panel appears.
23. Press Enter to complete the installation procedure and exit the installer.
Upgrade in Silent Mode

You can upgrade in silent mode without user interaction.
You can upgrade in silent mode to upgrade the domain on the same machine and on the same domain
configuration repository database.
To upgrade the Informatica domain services without user interaction, upgrade in silent mode. Use a
properties file to specify the upgrade options. The installer reads the file to determine the upgrade options.
You can use silent mode upgrade to upgrade the Informatica domain services on multiple machines on the
network or to standardize the upgrade process across machines.
Copy the Informatica installation files to the machine that hosts the Informatica instance you plan to
upgrade.
Upgrade in Silent Mode 69

To upgrade in silent mode, complete the following tasks:
1. Create the upgrade properties file and specify the upgrade options.
2. Run the installer with the upgrade properties file.
3. Secure the passwords in the upgrade properties file.
Encrypting Passwords in the Properties File

The installer includes a utility that you can use to encrypt passwords you set in the properties file you use to
specify options when you run the installer in silent mode. Informatica uses AES encryption with multiple 256-
bit keys to encrypt passwords.
You run the utility for each password you want to encrypt. When you run the utility, you specify the value of
the password in plain text at the command prompt. The utility generates the password in encrypted format as
output. The output includes the following prefix: =INSTALLER:CIPHER:AES:256=
Copy the complete output string, including the prefix, and then paste it into the properties file as the value for
the password property. When you run the installer in silent mode, the installation framework decrypts the
password.
1. Go to the utility directory:

<Installer directory>/properties/utils/passwd_encryption
2. Run the utility. Specify the plain text password you want to encrypt as the value for <password>.
• On Linux and UNIX, run the following command:
sh install.sh <password>
• On Windows, run the following command:
install.bat <password>
3. Copy the encrypted password string from the output, and then paste the string into the .properties file as
the value for the corresponding password.
The following example shows the encrypted password set as the value for the DOMAIN_PSSWD
property:
DOMAIN_PSSWD==INSTALLER:CIPHER:AES:256=mjkjmDR2kzFJiizfRWIOPg==
Creating the Properties File

Informatica provides two versions of the properties file. Use either file to specify options for your installation.
Silent input upgrade new config properties file
Use the silent input upgrade new configuration properties file to upgrade Informatica domain services
with changes to the node configuration and without user interaction.
The silent input upgrade new configuration properties file contains the configuration properties required
to upgrade the Informatica domain services in silent mode. Use the file if you want to consider the
appropriate value to set for each property in the file.
Default silent input upgrade properties file
Use the silent input upgrade properties file to upgrade Informatica domain services without user
interaction.
The default silent input properties file contains default values for many configuration properties. Use the
file if you plan to upgrade the Informatica domain services using the default property values.

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

2. Find the file named SilentInput_upgrade.properties.
Back up the file before you modify it.
3. Use a text editor to open the file and modify the values of the upgrade parameters.
The following table describes the upgrade parameters that you can modify:
INSTALL_TYPE Indicates whether to install or upgrade Informatica.

If the value is 0, the installer performs a fresh installation of Informatica. If
the value is 1, the installer upgrades a previous version of Informatica.
USER_INSTALL_DIR Directory in which to install the new version of Informatica services. The
directory cannot be the same as the directory that contains the previous
version of Informatica services.
UPG_BACKUP_DIR Directory that contains the previous version of Informatica services that you
want to upgrade.
KEY_DEST_LOCATION Directory in which to store the encryption key for the node created during the
installation.
DOMAIN_USER User name for the Informatica domain.
DOMAIN_PSSWD Password for the Informatica domain.
ENABLE_USAGE_COLLECTION Enables Informatica DiscoveryIQ, a product usage tool that sends routine
reports on data usage and system statistics to Informatica. Informatica
DiscoveryIQ uploads data to Informatica 15 minutes after you install and
configure Informatica domain. Thereafter, the domain sends the data every 30
days. You can choose to not send any usage statistics to Informatica. For
more information on how to disable sending usage statistics, see the
Informatica Administrator Guide.
You must set the value to 1 to upgrade.
4. Save the properties file with the name SilentInput.properties.
Upgrade in Silent Mode 71

Running the Silent Installer
After you create the properties file, open a command prompt to start the silent upgrade.
1. Open a command prompt.

On Windows, open the command prompt as administrator. If you do not open the command prompt as
administrator, the Windows system administrator might encounter issues when accessing files in the
Informatica installation directory.
2. Go to the root of the server installer directory.
3. Verify that the directory contains the file SilentInput.properties with the upgrade options.
4. Run the silentInstall executable.
The silent upgrade runs in the background. The process can take a while. The silent upgrade process is
complete when the Informatica_<Version>_Services_InstallLog<timestamp>.log is created in the installation
directory.
The silent upgrade fails if you incorrectly configure the properties file or if the installation directory is not
accessible. If the upgrade fails, view the silent upgrade log file and correct the errors. Then run the silent
installer again. The silent upgrade log file name is silentErrorLog.log.
The installer creates the log file in the root directory on Windows and in the user home directory on UNIX.
Troubleshooting the Domain Upgrade

Consider the following troubleshooting tips when you face any issue during or after the domain upgrade:
The domain upgrade fails.

If the upgrade does not complete successfully, review log files to determine the cause of the failure. The
upgrade log files are in the root of the directory where the new version of Informatica is installed. Review the
following log file: Informatica_<Version>_Services_Upgrade.log.
If the upgrade continues to fail, restore the domain configuration repository database from the backup and
run the installer again.
404 error message appears when you access the Administrator tool.
If the Administrator tool is configured for secure communication, you might receive a 404 Not Found
message when you access the Administrator tool. This issue occurs when the machine that runs the gateway
node cannot access the keystore file used for the HTTPS connection to the Administrator tool. Copy the file
to an accessible location, and then shut down the domain. Run the infasetup UpdateGatewayNode command
to update the gateway node with the location of the keystore file. You must run the command on each
gateway node in the domain.
The domain crashes during or after the upgrade.

If the domain crashes during or after the upgrade, restore the siteKey file from the domain backup or
generate the encryption key using the same keyword and domain name that you specified while generating
the sitekey in the previous version of the domain.

In a multi-node configuration, errors might occur when you use a different site key than the
master node.
If you have a multi-node configuration and when you use a different site key, you might run into the following
errors:
021-03-03 12:51:44,795 FATAL [Domain Monitor] [DOM_10061] Cannot register node
[newISPNode1]
with the domain because the master gateway node is not running or is not connected to the
domain. Verify that all gateway nodes are running on the domain.
com.informatica.isp.corecommon.exceptions.ISPException: [CCM_10342] The following

exception
occurred: [[FrameworkUtils_0018] The encryption key for the node is different from the
encryption for the domain. All the nodes in a domain must use the same encryption key. To
change the encryption key for the domain, run the infasetup migrateEncryptionKey command
on
all nodes in the domain.].)
To resolve this issue, ensure that you use the same site key as in the master node.
Troubleshooting the Domain Upgrade 73

Chapter 8
Upgrade the Domain with

Changes to Node Configuration
• Upgrade the Domain with Changes to Node Configuration Overview, 74

• Migrating to a Different Database, 75
• Migrating the Installation to a Different Machine, 75
• Upgrade in Graphical Mode, 81
• Upgrading in Console Mode, 92
• Upgrading in Silent Mode, 98
• Complete Changing the Node Configuration, 99
Upgrade the Domain with Changes to Node

Configuration Overview
Before you upgrade the domain with changes to the node configuration, you must perform steps to prepare
for the upgrade. The steps that you perform depend on the kind of change that you plan to make to the node
configuration. You can migrate the domain configuration repository to a different database. Or, you can
migrate the Informatica services installation to a different machine.
When you upgrade the domain, you can choose to change the node configuration to allow changes to the
node host name, port numbers, or domain configuration repository database.
If you migrated an Informatica services installation to a different machine, choose to change the node
configuration to upgrade the domain and configure the node on the new machine. If you migrated the domain
configuration repository to a different database, choose to change the node configuration to upgrade the
domain and configure the new database.
Complete the pre-upgrade tasks before you run the installer.
Guide.
On Windows, you can run the installer in graphical or silent mode. On UNIX or Linux, you can run the installer
in console or silent mode.
74
Migrating to a Different Database
If the domain configuration repository database type or version is no longer supported, you must migrate the
repository to a different supported database. Migrate the repository in the previous Informatica instance
before you upgrade the domain.
If you want to migrate to a different database, run i10Pi available from the Informatica installer to test the
installation support of the new database type or version. For more information about the i10Pi configuration,
see the Informatica Installation Guide.
1. Shut down the domain.

2. Verify that you have backed up the domain configuration database tables to a file with the infasetup
BackupDomain command.
3. Create a database schema and a user account in a supported database.
4. Run the i10Pi available from the Informatica installer with the database user account created to test the
installation supported for a different database. Ensure that i10pi shows the database users as supported
for the version in which you are about to upgrade.
5. Restore the domain configuration in the backup file to the specified database schema with the infasetup
RestoreDomain command.
6. Run the upgrade installer.
7. When you upgrade a gateway node, select the Allow changes to the node host name and port number
option. When you select this option, you can configure the gateway node to connect to the new domain
configuration repository database. All gateway nodes must have a connection to the domain
configuration repository to retrieve and update domain configuration. When you upgrade a worker node,
clear the Allow changes to the node host name and port number option.
Migrating the Installation to a Different Machine

If the Informatica services are installed on a machine with an operating system that is no longer supported,
you must migrate the installation to a different machine before you upgrade the domain.
Before you upgrade the domain, complete the following steps on the machine where you want the new
version of Informatica to run:
1. Run the i10Pi available from the Informatica installer to test the installation support of the new machine.
2. Copy the installation directory with all the installation binaries from the previous machine to the new
machine.
3. Verify port requirements.
4. Create a system user account.
Migrating to a Different Database 75

5. Configure native connectivity for all services that require access to databases.
6. Run the upgrade installer in the new supported machine.
When you upgrade the migrated node, select the Allow changes to the node host name and port number
option. When you select this option, you can update the configuration of the node on the new machine. When
you upgrade other nodes in the domain that you did not migrate to different machines, clear the Allow
changes to the node host name and port number option.
Step 1. Copy the Installation Directory

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

The installer sets up the ports for components in the Informatica domain, and it designates a range of
dynamic ports to use for some application services.
You can specify the port numbers to use for the components and a range of dynamic port numbers to use for
the application services. Or you can use the default port numbers provided by the installer. Verify that the
port numbers are available on the machines where you install the Informatica services.
The following table describes the ports that you can set:
Port Description
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 6006.
Service Manager Shutdown Port number that controls server shutdown for the domain Service Manager. The
port Service Manager listens for shutdown commands on this port. Default is 6007.
Informatica Administrator Port number used by Informatica Administrator. Default is 6008.

port
Informatica Administrator No default port. Enter the required port number when you create the service. Setting
HTTPS port this port to 0 disables an HTTPS connection to the Administrator tool.
Informatica Administrator Port number that controls server shutdown for Informatica Administrator. Informatica
shutdown port Administrator listens for shutdown commands on this port. Default is 6009.
Minimum port number Lowest port number in the range of dynamic port numbers that can be assigned to the
application service processes that run on this node. Default is 6014.
Maximum port number Highest port number in the range of dynamic port numbers that can be assigned to
the application service processes that run on this node. Default is 6114.
76 Chapter 8: Upgrade the Domain with Changes to Node Configuration

Note: Services and nodes can fail to start if there is a port conflict. You can update the range of ports for
application services after you upgrade.
Step 3. Create a System User Account

You can create a system user account on Windows or on UNIX.
On Windows
Create a system user account to perform the installation and to run the Informatica service. Verify that the
user account that you use to install the Informatica services has write permission on the installation
directory.
You can install Informatica with the user account logged in to the machine and run it under another user
account. You can create a local account or a domain account to install Informatica or run the Informatica
Windows service.
Note: To access a repository on Microsoft SQL Server that uses a Windows trusted connection, create a
domain account.
The user accounts require the following permissions to run the installer or to run the Informatica Windows
service:
• Logged in user account. The user account must be a member of the Administrators group and have the
Log on as a service permission. Log in with this user account before you install Informatica.
• Another user account. The user account must be a member of the Administrators group and have Log on
as a service and Act as operating system permissions. You do not have to log in with this user account
before you install Informatica. During installation, you can specify the user account to run the Informatica
Windows service.
On UNIX
Verify that the user account you use to install Informatica has write permission on the installation directory.
Step 4. Configure Native Connectivity on Service Machines

To establish native connectivity between an application service and a database, install the database client
software for the database that you want to access.
Native drivers are packaged with the database server and client software. Configure connectivity on the
machines that need to access the databases. To ensure compatibility between the application service and
the database, install a client software that is compatible with the database version and use the appropriate
database client libraries.
The Data Integration Service uses native database drivers to connect to the following databases:
• Source and target databases. Reads data from source databases and writes data to target databases.
• Data object cache database. Stores the data object cache.
• Profiling source databases. Reads from relational source databases to run profiles against the sources.
• Profiling warehouse. Writes the profiling results to the profiling warehouse.
• Reference tables. Runs mappings to transfer data between the reference tables and the external data
sources.
When the Data Integration Service runs on a single node or on primary and back-up nodes, install database
client software and configure connectivity on the machines where the Data Integration Service runs.
Migrating the Installation to a Different Machine 77

When the Data Integration Service runs on a grid, install database client software and configure connectivity
on each machine that represents a node with the compute role or a node with both the service and compute
roles.
Step 5. Install Database Client Software

You must install the database clients on the required machines based on the types of databases that the
application services access.
To ensure compatibility between the application service and the database, use the appropriate database
client libraries and install a client software that is compatible with the database version.
When you upgrade Informatica services, ensure that you install the appropriate database client on the
machine that runs the Data Integration Service.
Install the following database client software based on the type of database that the application service
accesses:
IBM DB2 Client Application Enabler (CAE)
Configure connectivity on the required machines by logging in to the machine as the user who starts
Informatica services.
Microsoft SQL Server 2014 Native Client
You must install the Microsoft SQL Server 2014 Native Client for the existing mappings to work.
Download the client from the following Microsoft website:

http://www.microsoft.com/en-in/download/details.aspx?id=42295.
Oracle client
Install compatible versions of the Oracle client and Oracle database server. You must also install the
same version of the Oracle client on all machines that require it. To verify compatibility, contact Oracle.
Sybase Open Client (OCS)
Install an Open Client version that is compatible with the Sybase ASE database server. You must also
install the same version of Open Client on the machines hosting the Sybase ASE database and
Informatica. To verify compatibility, contact Sybase.
Step 6. Configure Database Client Environment Variables

Configure database client environment variables on the machines that run the Data Integration Service
process.
After you configure the database environment variables, you can test the connection to the database from
the database client.

The following table lists the database environment variables you need to set:
Database Environment Variable Database Value

Name Utility
Oracle ORACLE_HOME sqlplus Set to: <DatabasePath>

PATH Add: <DatabasePath>/bin
IBM DB2 DB2DIR db2connect Set to: <DatabasePath>

DB2INSTANCE Set to: <DB2InstanceName>
PATH Add: <DatabasePath>/bin
Sybase ASE SYBASE15 isql Set to: <DatabasePath>/sybase<version>

SYBASE_ASE Set to: ${SYBASE15}/ASE-<version>
SYBASE_OCS Set to: ${SYBASE15}/OCS-<version>
PATH Add: ${SYBASE_ASE}/bin:${SYBASE_OCS}/bin:$PATH
Step 6. Configure Database Client Environment Variables on UNIX

Configure database client environment variables on the machines that run the PowerCenter Integration
Service process.
After you configure the database environment variables, you can test the connection to the database from
the database client.
Migrating the Installation to a Different Machine 79

The following table lists the database environment variables you need to set:
Database Environment Variable Database Value

Name Utility
Oracle ORACLE_HOME sqlplus Set to: <Client InstallDatabasePath>

PATH Add: <DatabasePath>/bin and USER_INSTALL_DIR/
LD_LIBRARY_PATH server/bin:$PATH
TNS_ADMIN Set to: $Oracle_HOME/lib and USER_INSTALL_DIR/
server/bin:$LD_LIBRARY_PATH
INFA_TRUSTSTORE
Set to location of the tnsnames.ora file:
$ORACLE_HOME/network/admin
For default SSL domain, add to: USER_INSTALL_DIR/
services/shared/security
For custom SSL domain, set INFA_TRUSTSTORE and
INFA_TRUSTSTORE_PASSWORD
To set the private truststore files, you must manually
import the certificates. Run the keytool command in
the <INFA_JDK_HOME> directory to import the private
truststore certificates. For example, use the following
keytool command:
keytool -noprompt -importkeystore -
srckeystore <source truststore file path>
-srcstorepass <source truststore file
password> -srcalias <alias> -srcstoretype
JKS -destkeystore <destination truststore
file path> -deststorepass <destination
truststore file password> -keypass
<private key password> -deststoretype JKS
SQL Server ODBCHOME Set to: USER_INSTALL_DIR/ODBC7.1

ODBCINI Set to: $ODBCHOME/odbc.ini
ODBCINST Set to: $ODBCHOME/odbcinst.ini
PATH Add to: /opt/mssql-tools/bin:$PATH
LD_LIBRARY_PATH $PATHUSER_INSTALL_DIR/
ODBC7.1:$PATHUSER_INSTALL_DIR/server/bin:$PATH
INFA_TRUSTSTORE
Add to: $ODBCHOME/lib
USER_INSTALL_DIR/server/bin:$LD_LIBRARY_PATH
For default SSL domain, add to: USER_INSTALL_DIR/
services/shared/security
For custom SSL domain, set INFA_TRUSTSTORE and
INFA_TRUSTSTORE_PASSWORD
To set the private truststore files, you must manually
import the certificates. Run the keytool command in
the <INFA_JDK_HOME> directory to import the private
truststore certificates. For example, use the following
keytool command:
keytool -noprompt -importkeystore -
srckeystore <source truststore file path>
-srcstorepass <source truststore file
password> -srcalias <alias> -srcstoretype
JKS -destkeystore <destination truststore
file path> -deststorepass <destination
truststore file password> -keypass
<private key password> -deststoretype JKS

Upgrade in Graphical Mode
When you upgrade in graphical 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
graphical mode on Windows.
On Windows, if you encounter problems when you run the install.bat file from the root directory, run the
following file:
3. Go to the root of the directory for the installation files and run install.bat as administrator.
To run the file as administrator, right-click the install.bat file and select Run as administrator.
On Windows, if you encounter problems when you run the install.bat file from the root directory, run
install.exe from the following location:
Note: If you do not run the installer as administrator, the Windows system administrator might not be
able to access files in the Informatica installation directory.
4. Select Upgrade to Informatica 10.5.3.

following utility before you upgrade Informatica services:
Pre-Installation (i10Pi) System Check Tool.
Verifies whether the machine on which you are installing Informatica services meets the system
requirements for installation.
Informatica Upgrade Advisor.
Validates the services and checks for obsolete services in the domain before you perform an
upgrade.
5. Click Start.
conditions.
https://www.informatica.com/in/privacy-policy.html. You can disable usage collection in Administrator
tool.

7. The Upgrade Prerequisties page appears.

8. Click Next.

The Upgrade Directory page appears.
9. Enter the directory of the Informatica version you want to upgrade and the directory in which you want to
install Informatica 10.5.3
The following table describes the directories that you must specify:

10. Select Allow changes to the node host name and port numbers.
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.

install.
13. Click Next.
The Domain Security - Encryption Key page appears.
14. Enter the directory for the encryption key for the informatica domain.
to another domain.
15. Enter the user name and password for the informatica domain.
16. Click Next.

17. Review the upgrade information, and click Install to continue.
The upgrade wizard installs the Informatica server files to theInformatica 10.5.3 installation directory.
The upgrade wizard displays a warning to shut down the Informatica domain before you continue the
upgrade.
18. Click OK.
19. If you are upgrading a gateway node, enter the database and user account information for the domain
configuration repository on the Domain Configuration Repository Upgrade page.
If you are upgrading a worker node, the upgrade wizard does not display the domain configuration
repository information. You cannot modify the database connection information. Skip to step 21on page
89.
Enter the following database and user account :
Database type Database for the domain configuration repository. Select Oracle, IBM DB2,
Microsoft SQL Server, PostgreSQL, or Sybase ASE.
Database user ID Database user account for the domain configuration repository.
User password Password for the database user account.

Tablespace Available for IBM DB2. 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, if this option is not selected, the installer creates
the tables in the default tablespace.
In a multipartition database, select this option and specify the name of the non-
partitioned tablespace that resides in the catalog partition of the database.
Schema name Available for Microsoft SQL Server or PostgreSQL. Name of the schema that will
contain domain configuration tables. If not selected, the installer creates the
tables in the default schema.
Trusted connection Available for Microsoft SQL Server. Indicates whether to connect to Microsoft
SQL Server through a trusted connection. Trusted authentication uses the security
credentials of the current user to make the connection to Microsoft SQL Server. If
not selected, the installer uses Microsoft SQL Server authentication.
20. Enter the JDBC connection information.

• To enter the connection information using the JDBC URL information, select JDBC URL and specify
the JDBC URL properties.
The following table describes the JDBC URL properties that you must specify:
Database address Host name and port number for the database in the format host_name:port.
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.
JDBC parameters Optional parameters to include in the database connection string. Use the
parameters to optimize database operations for the database. Verify that the
parameter string is valid. The installer does not validate the parameter string
before it adds the string to the JDBC URL. If not selected, the installer creates
the JDBC URL string without additional parameters.
• To enter the connection information using a custom JDBC connection string, select Custom JDBC
connection string and 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
Microsoft Azure SQL

number>;SelectMethod=cursor;DatabaseName=<database
name>;SnapshotSerializable=true;EncryptionMethod=SSL;HostNameInCertificate=*.datab
ase.windows.net;ValidateServerCertificate=false
Azure SQL Database with Active Directory authentication

jdbc:informatica: sqlserver://
<host_name>:<port_number>;database=<database_name>;encrypt=true;AuthenticationMeth
od=ActiveDirectoryPassword;trustServerCertificate=false;hostNameInCertificate=*.da
tabase.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=TL
Sv1.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.
21. Click Test Connection to verify that you can connect to the database, and then click OK to continue.
22. Click Next.
The Domain and Node Configuration page appears.
23. Modify the node host name and port number to match the configuration of the new version of
Informatica.

The following table describes the domain and node properties that you can specify:
Domain name Name of the domain. The default domain name is Domain_<MachineName>. The
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 for the new version of Informatica.
If the machine has a single network name, use the default host name. If the
machine has multiple network names, you can modify the default host name to
use an alternate network name. Optionally, you can use the IP address.
Note: Do not use localhost. The host name must explicitly identify the machine.
Node port number Port number for the node you are upgrading. The default port number for the node
is 6005.
Available if you upgrade a worker node.
Gateway node port number Port number of the gateway node.

24. Enter the custom keystore file password and location if you are securing the Informatica Administrator
with a custom keystore file and you are upgrading to a different gateway node configuration.
The following table describes the properties for the Informatica Administrator custom keystore:
Custom Keystore Password Plain text password for the custom keystore file.
Custom Keystore File Path and file name of the custom keystore file. If you leave this field blank, the
installer looks for the keystore file in the following directory:
<Informatica installation directory>\tomcat\conf\
25. Click Next.

The Port Configuration Upgrade page appears.
26. Enter the new port numbers or use the default port numbers.
The following table describes the ports that you can specify:
Port Description
Service Manager port Port number used by the Service Manager in the node. Client applications and the
Informatica command line programs use this port to communicate to the services
in the domain.
port Service Manager listens for shutdown commands on this port.

Port Description
Informatica Administrator Port number used by the Administrator tool.

port Available if you upgrade a gateway node.
Informatica Administrator Port number used by the Administrator tool to listen for shut down commands.
shutdown port Available if you upgrade a gateway node.
27. Click Next.

The Windows Service Configuration page appears.
On Windows, the upgrade wizard creates a service to start Informatica. By default, the service runs under
the same user account as the account used for installation. You can run the Windows service under a
different user account.
28. Select whether to run the Windows service under a different user account.

Enter the following user account information:
Run Informatica under a Indicates whether to run the Windows service under a different user account.
different user account
User name User account with which to run the Informatica Windows service.
Use the following format:
<domain name>\<user account>
This user account must have the Act as operating system permission.
Password Password for the user account with which to run the Informatica Windows service.
29. Click Next.

The Post-Installation Summary page appears.
30. Click Done to complete the installation procedure and exit the installer.
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.
3. Press 2 to upgrade Informatica.
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.
4. Press 2 to upgrade to Informatica 10.5.3.
5. Read the terms and conditions of Informatica product usage toolkit and press 2 to continue the upgrade.

information in accordance with the Informatica privacy policy. You can disable usage collection in the
Administrator tool.
6. The Upgrade Prerequisites page displays the upgrade system requirements.
7. 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.3.
The following table describes the directories you must specify:

8. Enter 2 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.
Default is 1.
Default is 1.
11. Enter the directory for the encryption key for the informatica domain.
Upgrading in Console Mode 93

to another domain.
directory>/isp/config/keys
12. Enter the user name and password for the informatica domain.
The installer copies the server files to the Informatica 10.5.3 installation directory.
14. Press Enter.
15. 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 18.
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
16. Enter the properties for the database user account.

The following table lists the properties for the database user account:
Database user ID Name for the domain configuration database user account.
User password Password for the domain configuration database user account.
17. Enter the parameters for the database. If you do not create a secure domain configuration repository,
enter the parameters for the database.
a. 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:
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.
b. 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:
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.
c. To enter the JDBC connection information using the JDBC URL information, press 1. To enter the
JDBC connection information using a custom JDBC connection string, press 2.
d. 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.

Prompt Description
Database service Service or database name:

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 Select whether to add additional JDBC parameters to the connection string:
Parameters 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

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
Microsoft SQL Server that uses a named instance with Windows NT credentials:
"jdbc:informatica:sqlserver://<host name>\<named instance
name>;DatabaseName=<database

Microsoft Azure SQL
number>;SelectMethod=cursor;DatabaseName=<database
name>;SnapshotSerializable=true;EncryptionMethod=SSL;HostNameInCertificate=*.d
atabase.windows.net;ValidateServerCertificate=false
Azure SQL Database with Active Directory authentication

jdbc:informatica: sqlserver://
<host_name>:<port_number>;database=<database_name>;encrypt=true;Authentication
Method=ActiveDirectoryPassword;trustServerCertificate=false;hostNameInCertific
ate=*.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;CryptoProtocolVersio
n=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.
18. Modify the node host name and port number to match the configuration of the new version of
Informatica.
The following table describes the domain and node properties that you can specify:
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 port number Port number of the gateway node.

19. 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.
port Service Manager listens for shutdown commands on this port.
Informatica Administrator Port number used by the Administrator tool.

port Available if you upgrade a gateway node.
Informatica Administrator Port number used by the Administrator tool to listen for shut down commands.
shutdown port Available if you upgrade a gateway node.
The Post-Installation Summary window indicates whether the upgrade completed successfully. It also shows
the status of the installed components and their configuration.
You can view the upgrade log files to get more information about the upgrade tasks performed by the
installer and to view the configuration properties for the installed components.
Upgrading in Silent Mode

When you upgrade in silent mode, you can change the node configuration to upgrade the domain to a
different machine or to a different domain configuration repository database.
To upgrade the Informatica services without user interaction, upgrade in silent mode. Use a properties file to
specify the upgrade options. The installer reads the file to determine the upgrade options. You can use silent

mode upgrade to upgrade the Informatica services on multiple machines on the network or to standardize
the upgrade process across machines.
Copy the Informatica installation files to the machine that hosts the Informatica instance you plan to
upgrade.
3. Secure the passwords in the upgrade properties file.
Complete Changing the Node Configuration

If you chose to change the node configuration during the domain upgrade because you migrated the
Informatica services installation to a different machine, you must perform additional tasks before you
upgrade the application services.
You must perform the following additional tasks:
1. Configure the environment variables.

2. Verify the range of dynamic port numbers.
3. Verify the location of the node backup directory.
4. Configure PowerExchange® adapters.
Note: If you chose to change the node configuration during the domain upgrade because you migrated the
domain configuration repository to a different database, you do not need to perform additional tasks.
Clear the Browser Cache

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

Use LANG, LC_CTYPE, or LC_ALL to set the UNIX code page.
Different UNIX operating systems require different values for the same locale. The value for the locale
variable is case sensitive.
Use the following command to verify that the value for the locale environment variable is compatible with the
language settings for the machine and the type of code page you want to use for the repository:
locale -a
The command returns the languages installed on the UNIX operating system and the existing locale settings.
Complete Changing the Node Configuration 99

Locale on Linux
All UNIX operating systems except Linux have a unique value for each locale. Linux allows different
values to represent the same locale. For example, “utf8,” “UTF-8,” “UTF8,” and “utf-8” represent the same
locale on a Linux machine. Informatica requires that you use a specific value for each locale on a Linux
machine. Make sure that you set the LANG environment variable appropriately for all Linux machines.
Locale for Oracle database clients
For Oracle database clients, set NLS_LANG to the locale that you want the database client and server to
use with the login. A locale setting consists of the language, territory, and character set. The value of
NLS_LANG depends on the configuration.
For example, if the value is american_america.UTF8, set the variable in a C shell with the following
command:
setenv NLS_LANG american_america.UTF8
To read multibyte characters from the database, set the variable with the following command:
setenv NLS_LANG=american_america.AL32UTF8
You must set the correct variable on the Data Integration Service machine so that the Data Integration
Service can read the Oracle data correctly.
Configure Library Path Environment Variables

Configure library path environment variables on the machines that run the Data Integration Service
processes. The variable name and requirements depend on the platform and database.
Configure the LD_LIBRARY_PATH environment variable.
The following table describes the values that you set for the LD_LIBRARY_PATH for the different databases:
Database Value
Oracle <Database path>/lib
IBM DB2 <Database path>/lib
Sybase ASE “${SYBASE_OCS}/lib:${SYBASE_ASE}/lib:${LD_LIBRARY_PATH}”
Informix <Database path>/lib
Teradata <Database path>/lib
ODBC <CLOSEDODBCHOME>/lib
PostgreSQL $PGHOME/lib:$ {LD_LIBRARY_PATH}
Verify the Range of Dynamic Port Numbers

When you upgrade a migrated node, the upgrade wizard assigns a default range of port numbers that can be
dynamically assigned to application service processes that run on the node.
The default range of dynamic port numbers is 6013 to 6113. Verify that the default range of port numbers are
available on the machine that runs the new version of Informatica. If the range of port numbers are not
available, use the Administrator tool to update the range. Configure the minimum and maximum dynamic port
numbers for service processes in the Advanced Properties section of the node Properties view.

Verify the Node Backup Directory
Verify that the backup directory for the node is accessible by the machine that runs the new version of
Informatica. In the Administrator tool, view the Backup Directory property in the Advanced Properties section
of the node Properties view.
Configure PowerExchange Adapters

If your previous installation included PowerExchange adapters, configure the PowerExchange adapters on
the machine that runs the upgraded version of Informatica. If the PowerExchange adapter has an installer, re-
install the PowerExchange adapter.
Complete Changing the Node Configuration 101

Chapter 9
Before You Upgrade the

Application Services
• Configure Informatica Environment Variables, 102

• Configure Locale Environment Variables, 103
• Verify the Keystore File Location for the Administrator Tool, 103
• Clear the Browser Cache, 104
Configure Informatica Environment Variables

You can configure the INFA_DOMAINS_FILE and INFA_HOME environment variables to store the domain and
installation location settings.
INFA_DOMAINS_FILE
The installer creates a domains.infa file in the Informatica installation directory. The domains.infa file
contains the connectivity information for the gateway nodes in a domain, including the domain names,
domain host names, and domain host port numbers.
Set the value of the INFA_DOMAINS_FILE variable to the path and file name of the domains.infa file.
Configure the INFA_DOMAINS_FILE variable on the machine where you install the Informatica services.
On Windows, configure INFA_DOMAINS_FILE as a system variable.
INFA_HOME
Use INFA_HOME to designate the Informatica installation directory. If you modify the Informatica
directory structure, you need to set the environment variable to the location of the Informatica
installation directory or the directory where the installed Informatica files are located.
For example, you use a softlink for any of the Informatica directories. To configure INFA_HOME so that
any Informatica application or service can locate the other Informatica components it needs to run, set
INFA_HOME to the location of the Informatica installation directory.
102
Configure Locale Environment Variables
Use LANG, LC_CTYPE, or LC_ALL to set the UNIX code page.
Different UNIX operating systems require different values for the same locale. The value for the locale
variable is case sensitive.
Use the following command to verify that the value for the locale environment variable is compatible with the
language settings for the machine and the type of code page you want to use for the repository:
locale -a
The command returns the languages installed on the UNIX operating system and the existing locale settings.
Locale on Linux
All UNIX operating systems except Linux have a unique value for each locale. Linux allows different
values to represent the same locale. For example, “utf8,” “UTF-8,” “UTF8,” and “utf-8” represent the same
locale on a Linux machine. Informatica requires that you use a specific value for each locale on a Linux
machine. Make sure that you set the LANG environment variable appropriately for all Linux machines.
Locale for Oracle database clients
For Oracle database clients, set NLS_LANG to the locale that you want the database client and server to
use with the login. A locale setting consists of the language, territory, and character set. The value of
NLS_LANG depends on the configuration.
For example, if the value is american_america.UTF8, set the variable in a C shell with the following
command:
setenv NLS_LANG american_america.UTF8
To read multibyte characters from the database, set the variable with the following command:
setenv NLS_LANG=american_america.AL32UTF8
You must set the correct variable on the Data Integration Service machine so that the Data Integration
Service can read the Oracle data correctly.
Verify the Keystore File Location for the

Administrator Tool
If you used a keystore file that you created to secure the connection to the Administrator tool, you must verify
the keystore file location before you access the Administrator tool. The upgrade process does not update this
location.
If you used the default keystore file generated by the installer in the previous domain, you do not need to
verify the keystore file location.
The tasks that you must perform depend on the following locations where you previously stored the keystore
file:
A location inside the previous Informatica installation directory structure
If you stored the keystore file in a location inside the previous Informatica installation directory structure,
perform the following steps:
1. Copy the file to another location.
Configure Locale Environment Variables 103

2. Update the gateway node with the copied keystore file location.
Run the infasetup UpdateGatewayNode command to update the gateway node with the location of
the keystore file. You must run the command on each gateway node in the domain.
A location outside the previous Informatica installation directory structure
If you stored the keystore file in a location outside the previous Informatica installation directory
structure, verify that the machine that runs the gateway node can access the file.
Clear the Browser Cache

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

Chapter 10
Application Service Upgrade

• Application Service Upgrade Overview, 105

• Run the Upgrade Wizard, 106
• Verify the Model Repository Service Upgrade, 107
Application Service Upgrade Overview

Informatica services version that you upgrade from determines the application service upgrade process.
Informatica services versions require that you upgrade the application services. When you upgrade an
application service, you must also upgrade the dependent services. When you upgrade an application service,
the upgrade process upgrades the database contents of the databases associated with the service.
Use the service upgrade wizard, the actions menu of each service, or the command line to upgrade
application services. The service upgrade wizard upgrades multiple services in the appropriate order and
checks for dependencies. If you use the actions menu of each service or the command line to upgrade
application services, you must upgrade the application services in the correct order and verify that you
upgrade dependent services.
The privileges required to upgrade application services depend on the service.
Privileges to Upgrade Services

The privileges required to upgrade application services depend on the application service.
A user with the Administrator role on the domain can access the service upgrade wizard.
A user must have these roles, privileges, and permissions to upgrade the following application services:
Model Repository Service
To upgrade the Model Repository Service using the service upgrade wizard, a user must have the
following credentials:
• Administrator role on the domain.

• Create, Edit, and Delete Projects privilege for the Model Repository Service and write permission on
projects.
105
To upgrade the Model Repository Service from the Actions menu or from the command line, a user must
have the following credentials:
• Manage Services privilege for the domain and permission on the Model Repository Service.
• Create, Edit, and Delete Projects privilege for the Model Repository Service and write permission on
projects.
Data Integration Service
To upgrade the Data Integration Service, a user must have the Administrator role on the Data Integration
Service.
Content Management Service
To upgrade the Content Management Service, a user must have the Administrator role on the Content
Management Service.
PowerCenter Repository Service
To upgrade the PowerCenter Repository Service, a user must have the Manage Services privilege for the
domain and permission on the PowerCenter Repository Service.
Metadata Manager Service
To upgrade the Metadata Manager Service, a user must have the Manage Services privilege for the
domain and permission on the Metadata Manager Service.
Service Upgrade from Previous Versions

When you upgrade from a previous version, some application services require an upgrade. Upgrade the
application services that you used in the previous version.
Before you upgrade, verify that the Metadata Manager Service is disabled. Verify that all other application
services are enabled.
To upgrade application services, upgrade the following services and associated databases in this order:
1. Model Repository Service

2. Data Integration Service
3. Profiling warehouse for the Data Integration Service
4. Metadata Manager Service
5. PowerCenter Repository Service
Note: When you upgrade all other application services, the upgrade process upgrades the database contents
of the databases associated with the service.
Run the Upgrade Wizard

Use the service upgrade wizard to upgrade application services and the database contents of the databases
associated with the services. The service upgrade wizard displays upgraded services in a list along with
106 Chapter 10: Application Service Upgrade

services and associated databases that require an upgrade. You can also save the current or previous
upgrade report.
Note: The Metadata Manager Service must be disabled before the upgrade. All other services must be
enabled before the upgrade.
1. In the Informatica Administrator header area click Manage > Upgrade.

2. Select the application services and associated databases to upgrade.
3. Optionally, specify if you want to Automatically recycle services after upgrade.
If you choose to automatically recycle application services after the upgrade, the upgrade wizard
restarts the services after they have been upgraded.
4. Click Next.
5. If dependency errors exist, the Dependency Errors dialog box appears. Review the dependency errors
and click OK. Then, resolve dependency errors and click Next.
6. Enter the repository login information.
7. Click Next.
The service upgrade wizard upgrades each application service and associated database and displays the
status and processing details.
8. When the upgrade completes, the Summary section displays the list of application services and their
upgrade status. Click each service to view the upgrade details in the Service Details section.
9. Optionally, click Save Report to save the upgrade details to a file.
If you choose not to save the report, you can click Save Previous Report the next time you launch the
service upgrade wizard.
10. Click Close.
11. If you did not choose to automatically recycle application services after the upgrade, restart the
upgraded services.
You can view the upgrade report and save the upgrade report. The second time you run the service upgrade
wizard, the Save Previous Report option appears in the service upgrade wizard. If you did not save the
upgrade report after upgrading services, you can select this option to view or save the previous upgrade
report.
Verify the Model Repository Service Upgrade

After you upgrade the Model Repository Service, check the Model Repository Service log to verify that the
upgrade completed successfully.
Object Dependency Graph

When you upgrade a Model Repository Service, the upgrade process upgrades the contents of the Model
repository and rebuilds the object dependency graph.
If the upgrade process encounters a fatal error while upgrading the Model repository contents, then the
service upgrade fails. The Administrator tool or the command line program informs you that you must
perform the upgrade again.
Verify the Model Repository Service Upgrade 107

If the upgrade process encounters a fatal error while rebuilding the object dependency graph, then the
upgrade of the service succeeds. You cannot view object dependencies in the Developer tool until you rebuild
the object dependency graph.
After you upgrade the Model Repository Service, verify that the Model Repository Service log includes the
following message:
MRS_50431 "Finished rebuilding the object dependency graph for project group '<project
group>'."
If the message does not exist in the log, run the infacmd mrs rebuildDependencyGraph command to rebuild
the object dependency graph. Users must not access Model repository objects until the rebuild process
completes, or the object dependency graph might not be accurate. Ask the users to log out of the Model
Repository Service before service upgrade.
The infacmd mrs rebuildDependencyGraph command uses the following syntax:

rebuildDependencyGraph
<-DomainName|-dn> domain_name
[<-SecurityDomain|-sdn> security_domain]
<-UserName|-un> user_name
<-Password|-pd> password
<-ServiceName|-sn> service_name
[<-ResilienceTimeout|-re> timeout_period_in_seconds]
Advanced Properties for the Model Repository Service

You can configure the Maximum Heap Size and MaxMetaspaceSize values after Model Repository Service
upgrade. Set the -Xss value before you upgrade the service. You need to reset the -Xss value after you
upgrade the service.
Configure the following advanced properties for the Model Repository Service:
Maximum Heap Size
Before the upgrade process, you can configure the Maximum Heap Size property value for the Model
Repository Service to 4GB if the property value is lower than 4GB. After the upgrade, reset the property
value to the previous value before the upgrade or to a value that Global Customer Support recommends
for your environment.
JVM Command Line Options
Configure the -Xss JVM command line option. Configure the -Xss value to 1m before you upgrade the
Model Repository Service upgrade. After the upgrade, reset the -Xss option back to the value before
upgrade. The default value is 512k.
To configure the advanced properties for a Model Repository Service, navigate to Manage > Services and
Nodes, select a Model Repository Service, and edit the Properties > Advanced Properties section.
108 Chapter 10: Application Service Upgrade

Chapter 11
Informatica Client Upgrade

• Informatica Client Upgrade Overview, 109

• Verify Installer Package Checksum , 110
• Informatica Client Upgrade Options, 111
• Profiles, 111
• Upgrading in Silent Mode, 111
Informatica Client Upgrade Overview

Use the client installer to upgrade a previous version of Informatica Developer. Informatica Developer is
installed on the installation directory you specify. The client installer configures the newly installed
Informatica Developer with the same settings as the previous version. The client installer does not modify the
files of the previous version of the client tools.
previous versions of Informatica Developer that you want to upgrade. You can upgrade the Informatica
clients in graphical or silent mode.
When you upgrade the Informatica client tools, the following components are also upgraded:
• DataDirect ODBC drivers

• Java Runtime Environment libraries
You can perform the upgrade from the root of the directory where you download the installation files.
When you run the client installer, you can select the following Informatica client tools to upgrade:
Informatica Developer
Informatica Developer is a client application that you use to create and run mappings, data objects, and
virtual databases. Objects created in Informatica Developer are stored in a Model repository and are run by a
Data Integration Service. If you upgrade Informatica Developer, verify that the Informatica version, including
the hotfix version, matches the version of the domain upgrade.
When you run the client installer, you can upgrade Informatica Developer.
The following entries describe the minimum system requirements to run the Informatica Developer:
Processor
Requires at least 1 CPU.
109
RAM
Requires at least 1 GB.
Disk Space
Requires at least 8.505 GB.
If you upgrade Informatica Developer, verify that the Informatica version exactly matches the version of the
domain upgrade.
PowerCenter Client
The PowerCenter Client is a set of tools you can use to manage the PowerCenter repository, mappings, and
sessions. The client upgrade also upgrades the following client tools:
• Mapping Architect for Visio

• Mapping Analyst for Excel
The following entries describe the minimum system requirements to run the PowerCenter Client:
Processor
Requires at least 1 CPU.
RAM
Requires at least 1 GB.
Disk Space
Requires at least 4.255 GB.
On Windows, the length of the entire installation directory path, including the zip file name, must be 60
characters or less. Verify that the zip utility version is compatible with the Windows operating system
version. When you unzip the file, verify that the zip utility also extracts empty folders.
Verify Installer Package Checksum

Before you run the client installer, verify the install package integrity through the cksum command. The
cksum command calculates the checksum value for the installer.
The following table lists the checksum and file size for Informatica client on Windows:
informatica_1053_client_winem-64t.z 590321451 3139423400

ip
110 Chapter 11: Informatica Client Upgrade

Informatica Client Upgrade Options
You can upgrade the Informatica client tools in one of the following ways:
• Upgrade in graphical mode. Upgrades the Informatica client tools in graphical mode. The installer guides
you through the upgrade process.
• Upgrade in silent mode. Upgrades the Informatica client tools using a properties file that contains the
upgrade options.
Profiles
After you upgrade, import the data domains for the profiles.
To add predefined data domain groups and related data domains to the data domain glossary, import the
Informatica_IDE_DataDomain.xml file into the Developer tool using the Windows > Preferences >
Informatica > Data Domain Glossary > Import menu option.
To view and make changes to rules associated with data domains, import the
Informatica_IDE_DataDomainRule.xml file using the File > Import menu option in the Developer tool.
Upgrading in Silent Mode

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

Informatica provides a sample properties file that includes the upgrade parameters that are required by the
installer. You can customize the sample properties file to specify the options for your upgrade.
The sample properties file is named SilentInput.properties and is located in the root of the client installer
directory.
2. Locate the file named SilentInput.properties.
Back up the file before you modify it.
3. Use a text editor to open the file and modify the values of the upgrade parameters.
Informatica Client Upgrade Options 111

The following table describes the upgrade parameters you can modify:
INSTALL_TYPE Indicates whether to install or upgrade the Informatica client tools.

To upgrade from a previous version of Informatica, set the value to 1.
USER_INSTALL_DIR Directory in which to install the new version of the Informatica client tools.
UPG_BACKUP_DIR Directory of the previous version of the Informatica tools that you want to
upgrade.
4. Save the properties file.
Running the Silent Installer

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

2. Go to root of the client installer directory.
3. Verify that the directory contains the file SilentInput.properties with the upgrade options.
4. To start the silent upgrade process, run silentInstall.bat.
The silent upgrade runs in the background. The process can take a while. The silent upgrade process is
complete when the Informatica_<Version>_Client_InstallLog.log is created in the installation directory.
The silent upgrade fails if you incorrectly configure the properties file or if the installation directory is not
accessible. If the upgrade fails, view the installation log files and correct the errors. Then run the silent
installer again.
5. After you complete an upgrade of Informatica Developer, log off the Windows machine and then log back
on to complete the system configurations.
112 Chapter 11: Informatica Client Upgrade

Chapter 12
After You Upgrade

• Informatica Domain, 113

• Migrating to a Different Database , 114
• Secure Client Connections to the Domain, 115
• Upgrade the Connection Provider Type for Microsoft SQL Server, 117
• PowerCenter Repository Service, 117
• PowerCenter Integration Service, 117
• Data Integration Service, 117
• Update the Log Events Directory, 118
• Update Configuration Files, 118
• Analyst Service, 118
• Metadata Manager Agent, 119
• Metadata Manager Service, 120
Informatica Domain
After you upgrade, complete the post-upgrade tasks for the domain.
Update the Log Events Directory

After you upgrade, you might want to update the log events directory for the domain.
The default value of the log events directory after an upgrade depends on the following upgrade types:
Upgrade the domain without changes to the node configuration.
The log events directory points to the location that you specified in the previous version.
Upgrade the domain with changes to the node configuration.
The log events directory points to the isp/logs directory in the new installation directory.
To use a different directory for the logs, update the Log Directory Path property for the domain in the
Administrator tool. You can also use the infasetup updateGatewaynode command to update the directory.
For example, you can configure the log events directory as the server/infa_shared/logs directory in the
new installation directory.
113
Enable Transport Layer Security
After you upgrade, the Transport Layer Security (TLS) versions 1 and 1.1 are disabled by default. Perform the
following steps to enable TLS versions 1 and 1.1.
1. Go to $INFA_HOME/Java/jre/lib/security/java.security.
2. Edit the java.security configuration file.
3. Locate the jdk.tls.disabledAlgorithms setting in the java.security configuration file.
4. Remove TLSv1 and TLSv1.1 from the list of disabled algorithms.
5. Save and close the java.security configuration file.
6. Restart the domain.
TLS versions 1 and 1.1 are enabled.
Upgrade the Informatica Client

After you upgrade the domain, upgrade the Informatica client tool to the same Informatica version.
Migrating to a Different Database

After you upgrade the domain and services, configure the supported database for the existing services.
1. Create a supported database. For more information about creating a database, see the Informatica
Application Service Guide.
2. Back up the domain and repositories.
• To back up the domain, enter the following command:
infasetup BackupDomain
• To back up the PowerCenter repository, enter the following command:
pmrep backup
• To back up the Model Repository Service, enter the following command:
infacmd mrs BackupContents
3. Restore, update, and start the domain.
• To restore the domain to a supported database, enter the following command and update the
database type and schema name:
infasetup RestoreDomain
• To update the domain name, node name, and the supported database name, enter the following
command:
infacmd isp UpdateGatewayNode
• To start the domain, enter the following command: infaservice Startup
4. Update the database for the PowerCenter Repository Service, recycle, and restore the PowerCenter
repository.
• To update the PowerCenter Repository Service with the supported database, enter the following
command:
infacmd isp UpdateRepositoryService
114 Chapter 12: After You Upgrade

• To recycle the service, enter the following command:
infacmd isp EnableService
• To restore the PowerCenter repository with the supported database type, enter the following
command:
pmrep restore
5. Update the database for the Model Repository Service, recycle, and restore the Model Repository
Service.
• To update the Model Repository Service with the supported database, enter the following command:
infacmd mrs UpdateServiceOptions
• To recycle the service, enter the following command:
infacmd isp EnableService
• To restore the Model Repository Service with the supported database type, enter the following
command:
infacmd mrs restoreContents
6. Set the database-specific environment variables for the required service.
For example, set the following environment variable for PostgreSQL for the PowerCenter Repository
Service:
PGSERVICE: Set to the location of the pg_service.conf file:
<pg_service.conf file directory>/pg_service.conf
PGHOME: Set to PostgreSQL client install location. For example, /usr/pgsql -10
Add to PATH: $PGHOME/bin:${PATH}
Add to LD_LIBRARY_PATH: $PGHOME/lib:${LD_LIBRARY_PATH}
For Oracle, set the following environment variable for Oracle for the PowerCenter Repository Service:
ORACLE_HOME: Set to Oracle client install location. For example, /u01/app/oracle/
product/19.0.0.0
Add to PATH: $ORACLE_HOME/bin:${PATH}
Add to LD_LIBRARY_PATH: $ORACLE_HOME/lib:${LD_LIBRARY_PATH}
Add TNS_ADMIN. The TNS entries are in the oratns folder. For example, /misc/platqa/
ISPAutomation/oratns
For DB2, set the following environment variable for DB2 for the PowerCenter Repository Service:
DB2DIR: Set to DB2 client install location. For example, /opt/ibm/db2/V11.1
DB2INSTANCE: Instance name of the DB2 client.
Add to PATH: $DB2DIR/bin:${PATH}
Add to LD_LIBRARY_PATH: $DB2DIR/lib:${LD_LIBRARY_PATH} OR $DB2DIR/lib64:$
{LD_LIBRARY_PATH}
For SQL Server with DSN, create the DSN entry on the machine where you run the Informatica services.
You can enable the DSN and specify the DSN name in the Administrator tool.
For SQL Server on Linux, set the following environment variable for SQL Server for the PowerCenter
Repository Service:
ODBCHOME=$INFA_HOME/ODBC<version>
ODBCINI=$INFA_HOME/ODBC<version>/odbc.ini
ODBCINST=$INFA_HOME/ODBC<version>/odbcinst.ini
Secure Client Connections to the Domain

If you enabled secure communication between client applications and the Informatica domain in the previous
version, you must verify the keystore file locations or generate a new keystore after you upgrade. If you use
Secure Client Connections to the Domain 115

Metadata Manager, you must generate a new keystore file after you upgrade. If you use other client
applications, you must verify the keystore file locations after you upgrade
When you configure a secure connection between a client application and a service, you specify the keystore
file that contains the keys and certificates for the secure HTTPS connection. After you upgrade, you must
generate a new keystore file or verify the keystore file locations. The upgrade process does not update the
keystore file or locations.
Note: If you used RSA encryption with fewer than 512 bits to create the private key and SSL certificate, you
must create new SSL certificate files. Due to the FREAK vulnerability, Informatica does not support RSA
encryption with fewer than 512 bits.
The tasks that you must perform depend on which client applications you use.
Metadata Manager
If you use Metadata Manager, generate a new keystore file after you upgrade. Regenerate the keystore
file to ensure that the Java version used to generate the keystore file matches the Java version installed
with Informatica. If the Java versions do not match, users that perform operations in Metadata Manager
might get a "Cannot connect to Metadata Manager Service" error.
To generate a new keystore file, perform the following steps:
1. Generate a new keystore file that contains the keys and certificates required to secure the
connection for the Metadata Manager web application. Use the keytool utility installed with the
current version of Informatica to generate the keystore file.
Note: The Metadata Manager Service uses RSA encryption. Therefore, Informatica recommends that
you use a security certificate that was generated with the RSA algorithm.
2. Save the keystore file in a directory that can be accessed from the machine where the Metadata
Manager Service runs.
3. Use the Administrator tool to update the keystore file for the Metadata Manager Service.
Other Web Client Applications
If you use other web client applications, the tasks that you must perform depend on the following locations
where you previously stored the keystore files:
A location inside the previous Informatica installation directory structure
If you stored the keystore file in a location inside the previous Informatica installation directory structure,
perform the following steps:
1. Copy the file to another location.

2. Update the application service with the copied keystore file location.
Use the Administrator tool to update the location of the keystore file for the appropriate application
service. For example, if the keystore file is used for Analyst tool security, update the keystore file
location in the Analyst Service properties.
A location outside the previous Informatica installation directory structure
If you stored the keystore file in a location outside the previous Informatica installation directory
structure, verify that the keystore file can be accessed from the machine where the application service
runs.

Upgrade the Connection Provider Type for Microsoft
SQL Server
After you upgrade, the Microsoft SQL Server connection is set to the OLEDB provider type by default.
It is recommended that you upgrade all your Microsoft SQL Server connections to use the ODBC provider
type. You can upgrade all your Microsoft SQL Server connections to the ODBC provider type by using the
Informatica services in the following format:
ODBCINST=<INFA_HOME>/ODBC7.1/odbcinst.ini
After you set the environment variable, you must restart the node that hosts the Informatica services.
PowerCenter Repository Service

After you upgrade, run the PowerCenter Repository Service in exclusive mode to upgrade the repository
metadata.
After you upgrade the repository metadata, change the mode to Normal mode and restart the PowerCenter
Repository Service.
PowerCenter Integration Service

After you upgrade, configure Umask for the Operating System profiles for the PowerCenter Integration
Service.
If you upgraded from a version that used operating system profiles, set the umask setting to change the
security on files that the DTM writes.
For example, you can change umask to 077 for maximum security. You must restart Informatica services if
you change the umask setting.
Data Integration Service

After you upgrade, reset the HTTP Proxy Server Password for the Data Integration Service.
If the Data Integration Service runs Web Service Consumer transformations and is configured to use an HTTP
proxy server with authentication, reset the HTTP proxy server password.
If you do not reset the password, then the Data Integration Service cannot successfully process Web Service
Consumer transformations.
Reset the HTTP Proxy Server Password for the Data Integration Service in the Administrator tool.
Upgrade the Connection Provider Type for Microsoft SQL Server 117
Update the Log Events Directory
After you upgrade, you might want to update the log events directory for the domain.
The default value of the log events directory after an upgrade depends on the following upgrade types:
Upgrade the domain without changes to the node configuration.
The log events directory points to the location that you specified in the previous version.
Upgrade the domain with changes to the node configuration.
The log events directory points to the isp/logs directory in the new installation directory.
To use a different directory for the logs, update the Log Directory Path property for the domain in the
Administrator tool. You can also use the infasetup updateGatewaynode command to update the directory.
For example, you can configure the log events directory as the server/infa_shared/logs directory in the
new installation directory.
Update Configuration Files

When you upgrade, the installer overwrites configuration files, such as odbc.ini, odbcinst.ini, sapnwrfc.ini, or
infaservice.sh. If any of the configuration files contain customization, updated, or new properties, ensure that
you have backed up the installation configuration files. You can then manually merge the changes from the
backup files into the latest installed file. For instance, if infaservice.sh contains some variables or java
options, you need to manually merge the changes to the latest install file paths.
Manually merge the latest configuration changes into the following install file paths after you upgrade:
$INFA_HOME/ODBC7.1/odbc.ini
$INFA_HOME /ODBC7.1/odbcinst.ini
$INFA_HOME/server/bin/sapnwrfc.ini
$INFA_HOME/tomcat/bin/infaservice.sh
Analyst Service
After you upgrade, complete the post-upgrade tasks for each Analyst Service.
Verify the Flat File Cache Location

You must verify the location of the flat file cache directory after you upgrade. The upgrade process does not
update this location.
If you created the flat file cache directory within the previous Informatica installation directory, copy the
directory to the upgraded Informatica installation directory and update the Analyst Service property with the
new location.
If you created the directory outside of the previous Informatica installation directory, verify that both the
Analyst Service and the Data Integration Service can access the directory.

If the Analyst Service and the Data Integration Service run on different nodes, configure the flat file directory
to use a shared directory. If the Data Integration Service runs on primary and back-up nodes or on a grid, each
Data Integration Service process must be able to access the files in the shared directory.
To verify the location of the flat file cache directory, view the Flat File Cache Location property in the run-time
properties for the Analyst Service.
Verify the Temporary Export File Location

You must verify or provide the location of the temporary export file directory after you upgrade. The Analyst
tool uses this location to store business glossaries that you export. The upgrade process does not update
this location.
If you created the temporary export file directory within the previous Informatica installation directory, copy
the directory to the upgraded Informatica installation directory and update the Analyst Service property with
the new location. If you created the directory outside of the previous Informatica installation directory, verify
that the machine that runs the Analyst Service can access the directory. If you have not configured the
location of the temporary export file directory, provide a location where the Analyst tool can store glossaries
during export.
To verify or provide the location of the temporary export file directory, view the Temporary Export File
Directory property in the Business Glossary properties for the Analyst Service.
Recycle the Analyst Service

To access the Analyst tool after you upgrade, recycle the Analyst Service. Before you recycle the Analyst
Service, complete the upgrade and post-upgrade steps for the Model Repository Service and Data Integration
Service.
After you recycle the Analyst Service, wait for at least 10 minutes before you access the Glossary workspace.
Before you recycle the Analyst Service, verify that you have performed the following tasks:
• Upgrade the Model Repository Service.

• Upgrade the Data Integration Service.
Note: The Model Repository Service and the Data Integration Service must be running before you recycle the
Analyst Service.
Metadata Manager Agent

After you upgrade, you must uninstall and reinstall each Metadata Manager Agent so that Metadata Manager
can extract metadata from the metadata sources. Install the latest version of the Metadata Manager Agent
before you migrate resources.
1. Stop the Metadata Manager Agent.

2. Reinstall the Metadata Manager Agent.
For information about installing the Metadata Manager Agent, see the Metadata Manager Administrator
Guide.
Metadata Manager Agent 119

Metadata Manager Service
After you reinstall the Metadata Manager Agent, perform the following post-upgrade tasks for each Metadata
Manager Service:
1. Update the Metadata Manager properties file to include any customization.

2. If the Metadata Manager repository is a Microsoft SQL Server database and the Metadata Manager
Service runs on UNIX, verify that the ODBCINST environment variable is set.
3. Enable the Metadata Manager Service.
4. Re-create Netezza resources.
5. If you set the Worker Threads configuration property for any Business Intelligence resource in the
previous version, set the Multiple Threads configuration property to the same value.
Update the Metadata Manager Properties File

Compare the imm.properties file in the previous installation directory with the current version. Update the
current version of the imm.properties file as required.
The imm.properties file is in the following directory:
<Informatica installation directory>\services\shared\jars\pc\classes
The changes take effect when you enable the Metadata Manager Service.
Verify the ODBCINST Environment Variable on UNIX

If the Metadata Manager repository is a Microsoft SQL Server database and the Metadata Manager Service
runs on UNIX, verify that the ODBCINST environment variable is set on the machine that runs the
PowerCenter Integration Service.
The PowerCenter Integration Service runs the workflows that extract metadata from the IME-based files and
load it into the Metadata Manager warehouse. The PowerCenter Integration Service uses ODBC to connect to
the Microsoft SQL Server database. On UNIX, the ODBCINST environment variable must be set to the location
of the odbcinst.ini file. Otherwise, the PowerCenter Integration Service cannot access the ODBC driver.
On the machine that runs the PowerCenter Integration Service, verify that the ODBCINST environment variable
is set to the following value:
ODBCINST=<INFA_HOME>/ODBC7.1/odbcinst.ini
If the environment variable is not set, set the environment variable, and then restart the domain.

Purge and Reload Resources
Some models are changed between Metadata Manager versions. If a model has minor changes, such as new
class attributes, you must purge and reload the resources that are based on the model.
The following table lists the resources that you must purge and reload:
Metadata Source Type Resource Type
Business Intelligence Business Objects

Oracle Business Intelligence Enterprise Edition
Data Modeling SAP Power Designer
To prevent the loss of connection information for business intelligence and database management
resources, purge and reload resources in the following order:
1. Database management resources

2. Tableau resources
3. PowerCenter resources
Upgrade Informatica Platform Resources

If you created an Informatica Platform resource that extracts metadata from an Informatica application, you
must upgrade the resource. To upgrade the resource, you either re-create the resource or configure the
resource to use the command line utilities.
When you upgrade PowerCenter, the Data Integration Service and Model Repository Service are also
upgraded. But when you upgrade only the Metadata Manager, the Data Integration Service and Model
Repository Service are not upgraded by default. You can upgrade the services in the Administrator tool, if
necessary.
You upgrade the Informatica Platform resource differently based on whether you upgraded the services on
which the application is based:
You upgraded PowerCenter.
If you upgraded the services on which the application is based, you must re-create the resource after
upgrade. After you create the new resource, you can purge and delete the old resource.
You upgraded only the Metadata Manager.
If you did not upgrade the services on which the application is based, you must configure the resource to
use the command line utilities.
To configure the resource to use the command line utilities, perform the following steps:
1. Contact Informatica Global Customer Support to get the Command Line Utilities zip file for the
version you upgrade to.
2. Extract the files to a directory that the Metadata Manager Service can access.
For best performance, extract the files to a directory on the machine that runs the Metadata
Manager Service. If you extract the files to a different machine, the Metadata Manager Service can
take several minutes to access the directory.
3. Edit the resource and configure the <current_version> Command Line Utilities Directory property.
Set the property to the directory where you installed the command line utilities, for example,
C:\Informatica\1041_CLU.
Metadata Manager Service 121

4. In Metadata Manager, load the resource.
For more information about creating Informatica Platform resources and installing the command line utilities
for Informatica Platform resources, see the "Data Integration Resources" chapter in the Metadata Manager
Administrator Guide.
Copy the Data Transformation Files

After you upgrade Data Transformation, copy the files from the previous installation directories to the new
installation directories, to get the same workspace, repository, and custom global components as in the
previous version.
File or Directory Default Location
Repository <Informatica installation directory>\DataTransformation\ServiceDB
Custom Global <Informatica installation directory>\DataTransformation\autoInclude\user

(TGP files)
Custom Global <Informatica installation directory>\DataTransformation\externLibs\user

(DLL and JAR files)
Do not copy the Data Transformation Library files. Instead, install the Data Transformation Libraries again.
Read What's New and Changed

Informatica What's New and Changed lists new features and enhancements, behavior changes between
versions, and tasks that you might need to perform after you upgrade. Read Informatica What's New and
Changed to view the list of new functionality that you might want to implement or new options that you might
want to enable.

Appendix A
Upgrade Checklist
This appendix includes the following topics:
• Upgrade Checklist Overview, 123

• Before You Upgrade the Domain, 123
• Domain Upgrade, 124
• Before You Upgrade the Application Services, 125
• Application Service Upgrade, 125
• Informatica Client Upgrade, 126
• After You Upgrade, 126
Upgrade Checklist Overview

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

Before you upgrade the domain, perform the following pre-upgrade tasks:
 Read the Informatica Release Notes.
 Perform the following tasks to set up the machine to meet the operating system requirements:
• Verify that the machine has the required operating system patches and libraries.
• Verify that the machine meets the minimum system requirements to upgrade the domain.
• Verify that the machine meets the hardware requirements to upgrade the application services.
• Verify the distributions for the non-native environments.
• Review the environment variables.
• Review the maximum heap size setting.
• Extract the installer files.
• Run the Informatica Upgrade Advisor.
123
• Back up the configuration files.
 Back up the Data Transformation Files.
 Disable the Analyst Service through Administrator tool or through infacmd DisableService.
 Perform the following tasks to prepare the PowerCenter repository:

• Back up the PowerCenter repository.
• Verify the user account requirements for the PowerCenter repository database.
 Perform the following tasks to prepare the Model repository:

• Back up the Model repository.
• Verify the user account requirements for the Model repository database.
 Perform the following tasks to prepare the Data Integration Service:

• Record the execution options for each Data Integration Service process.
• Verify that all workflows are complete.
 Perform the following tasks to prepare the profiling warehouse:

• Use the native database back up option to back up the profiling warehouse.
• Verify the user account permissions for the database.
 Perform the following tasks to prepare the Reference Data Directories:

• Back up the reference data directory.
• Record the directory location.
 Perform the following tasks to prepare Metadata Manager:

• Back up the Metadata Manager warehouse.
• Disable the Metadata Manager service.
• Back up the Metadata Manager properties file.
 Use the native database back-up option to back up profiling warehouse, reference data warehouse, and
workflow database.
 Perform the following tasks to prepare the domain:

• Verify database user account requirements.
• Shutdown the domain. To shut down the domain, stop the Informatica service process on each node in
the domain.
• Back up the domain.
 Prepare to change the node configuration.

Perform the additional pre-upgrade tasks if you choose to change the node configuration.
Domain Upgrade
Use the server installer to upgrade the domain. The server installer provides a domain upgrade wizard to
guide you through the upgrade process.
124 Appendix A: Upgrade Checklist

The upgrade wizard installs the Informatica files in the installation directory that you specify. It does not
modify the files in the directory of the previous version.
When you run the upgrade wizard, select the option to change the node configuration if you upgrade the
domain to a different machine or to a different domain configuration repository database.
Before You Upgrade the Application Services

Before you upgrade application services, perform the following pre-upgrade tasks:
 Configure locale environment variables.

Verify that the locale setting is compatible with the code page for the repository.
 Clear the browser cache.
 If you chose the option to change the node configuration to migrate the Informatica installation to a
different machine, perform the following tasks:
• Configure the environment variables.
• Configure Library Path Environment Variables.
• Verify
the range of port numbers that can be dynamically assigned to application service processes that
run on the node.
• Verify that the backup directory for the node is accessible by the node.
• Configure
PowerExchange adapters. If the PowerExchange adapter has an installer, re-install the
PowerExchange adapter.
Application Service Upgrade

Service versions require a service upgrade. You can use the service upgrade wizard to upgrade services.
 Verify the privileges required to upgrade for the following application services:
• PowerCenter Repository Service
• Model Repository Service
• PowerCenter Integration Service
• Data Integration Service
• Content Management Service
• Scheduler Service
• Analyst Service
• Metadata Manager Service
 Upgrade the following services and associated databases:

• PowerCenter Repository Service
• PowerCenter Integration Service
• Model Repository Service
Before You Upgrade the Application Services 125

• Data Integration Service
• Profiling warehouse for the Data Integration Service
• Scheduler Service
• Analyst Service
• Metadata Manager Service
 Run the Service Upgrade Wizard to upgrade application services and the database contents of the
databases associated with the services.
 Verify the Model Repository Service upgrade.

• Object dependency graph.
• Maximum heap size
Informatica Client Upgrade

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

After you upgrade the domain, application services, and client files, perform the following post-upgrade
tasks:
 Perform the following tasks for the domain:

• If
you used your SSL certificate files to enable secure communication in the previous domain, verify the
keystore and truststore file locations. The upgrade process does not update these locations.
• Youcan optionally configure the domain configuration repository on a database that is secured with the
SSL protocol.
 Perform the following tasks for each Data Integration Service:

• Reset the HTTP proxy server password.
If the Data Integration Service runs Web Service Consumer transformations and is configured to use an
HTTP proxy server with authentication, reset the HTTP proxy server password.
• If
the Data Integration Service runs on multiple nodes and you configured the execution options
differently for each service process, verify that the Execution Options on the Properties view use the
correct values.
• If
you work with rule specifications in the Analyst tool or the Developer tool, verify the Maximum Heap
Size value.
• Verify
that the Maximum Memory Per Request property uses the correct value for each Data Integration
Service module.
126 Appendix A: Upgrade Checklist

 Perform the following tasks for each Analyst Service:
• If
you use Business Glossary approval workflow in a domain with Kerberos authentication, enter the
user name and password for the Model Repository Service.
• Verify the location of the flat file cache directory. The upgrade process does not update this location.
• Verify
or configure the location of the temporary export file directory for Business Glossary files. The
upgrade process does not update this location.
• Verify
or configure the location of the asset attachment directory for Business Glossary files. The
upgrade process does not update this location.
• Recyclethe Analyst Service.
Before you recycle the Analyst Service, complete the upgrade and post-upgrade steps for the Model
Repository Service, Data Integration Service, and Content Management Service.
 Perform the following tasks for profiles and scorecards:

• Importdata domain groups and related data domains to the data domain glossary. If you want to add
predefined data domain groups and their related data domains to the data domain glossary, import the
Informatica_IDE_DataDomain.xml file.
• Runinfacmd ps restoreProfilesAndScorecards command to restore the profiles and scorecards from a
previous version to the current version.
• Runthe scorecards to view the statistics in the Cumulative Metrics Trend pane for the scorecards that
you had created.
 Upgrade all your Microsoft SQL Server connections to use the ODBC provider type.
 Upgrade the Informatica drivers for SQL data service.
 Copy the Data Transformation files from the previous installation directories to the new installation
directories, to get the same workspace, repository, and custom global components as in the previous
version.
 Read Informatica What's New and Changed to view the list of new functionality that you might want to
implement or new options that you might want to enable.
After You Upgrade 127

Appendix B
Managing Distribution Packages

This appendix includes the following topics:
• Managing Distribution Packages Overview, 128

• Before You Begin, 128
• Install or Remove Distribution Packages in Console Mode, 129
• Install or Remove Distribution Packages in Silent Mode, 130
• After You Install, 130
Managing Distribution Packages Overview

You can use Integration Package Manager (the package manager) to install and remove distribution
packages from the Informatica service and client machines.
A distribution package is a set of distribution binaries that you install within the domain for the following
processing requirements:
• To push processing to the Hadoop or Databricks environment.

• To process complex files within the Informatica domain.
• To connect to the Hadoop or Databricks environment when you process within the Informatica domain.
You can install distribution packages if you didn't do so during the upgrade or install process or if you want to
add a distribution package. You can remove a distribution package if you want to use a different package or
if you installed a package that you don't use.
When you install or remove distribution packages, verify that you perform the operation on all service and
client machines.
Before You Begin

Before you run the package manager, perform tasks such as setting environment variables and downloading
files.
1. Shut down the Informatica services.
128
2. Set one of the following environment variables:
INFA_JDK_HOME Location of the folder containing the supported Java Development Kit (JDK). Set the
INFA_JDK_HOME environment variable in the following scenarios:
- Informatica domain is on Windows or Linux
- Informatica client
INFA_JRE_HOME Location of the folder containing the supported Java Runtime Environment (JRE). If the
Informatica domain is on AIX, set the INFA_JRE_HOME environment variable.
3. Verify that the user that runs the package manager has read and write permissions on the Informatica
installation directory and execute permissions on the executable file.
4. Download the following files from the Informatica Electronic Software Download site:
• Integration Package Manager
• Distribution packages
5. Extract the Integration Package Manager ZIP files to a local drive.
6. Copy the ZIP files of distribution packages that you need to the following location: <Integration
Package Manager directory>/source
Note: The package manager fails if the ZIP files for distribution packages aren't available in the source
directory.
Install or Remove Distribution Packages in Console

Mode
You can run the package manager in console mode to install or remove distribution packages.
1. From the package manager directory, run one of the following commands:
• ./Server.sh console for Linux or UNIX
• Server.bat console for Windows
• Client.bat console for client
Note: To run the command on Windows, use the administrator command prompt.
2. Enter the installation directory of the services or client and press Enter.
3. Choose the operation type and press Enter.
• Select 1 to remove existing distribution packages.
• Select 2 to install one or more distribution packages.
The console lists the distribution packages that you can install or remove.
4. Enter the distribution packages that you want to install or remove, separating multiple packages with a
comma, and press Enter.
5. Verify the installation or removal status in the package manager log file.
You can find the log file in the following location: <Integration Package Manager directory>/
IntegrationPackageManager_<date and timestamp>.log
Install or Remove Distribution Packages in Console Mode 129

Install or Remove Distribution Packages in Silent
Mode
You can run the package manager in silent mode to install or remove distribution packages. The silent input
properties file contains the properties for the package manager to run in silent mode for service and clients.
Set the appropriate value for each property in the file.
1. Find the IntegrationPackageManager.properties file in the following location: <Integration Package

Manager directory>/
2. Edit the properties file in a text editor.
The following table describes the properties that you can modify:
USER_INSTALL_DIR The installation directory of the service or client.
OPERATION_TYPE The operation that you want to perform:

- Set to DELETE to remove existing distribution packages.
- Set to EXTRACT to install one or more distribution packages.
SELECTED_HADOOP_LIBRARIES Lists the distribution packages and versions.

Enter the distribution packages that you want to install or remove. Separate
multiple packages with a comma.
3. Save the properties file.

4. From the package manager directory, run one of the following commands:
• ./Server.sh silent for Linux or UNIX
• Server.bat silent for Windows
• Client.bat silent for client
Note: To run the command on Windows, use the administrator command prompt.
5. Verify the installation or removal status in the package manager log file.
You can find the log file in the following location: <Integration Package Manager directory>/
IntegrationPackageManager_<date and timestamp>.log
After You Install

To use the distribution packages that are installed using the package manager, configure the property or
environment variable in service and client machines.
Configure the Developer Tool

After you install the distribution packages in the Developer tool, update the developerCore.ini file with the
installed distribution package.
1. Find the developerCore.ini file in the following location: <Informatica installation directory>
\clients\DeveloperClient
130 Appendix B: Managing Distribution Packages

2. Edit the file to update the following property:
-DINFA_HADOOP_DIST_DIR=hadoop\<Hadoop distribution name>_<version>
For example,
-DINFA_HADOOP_DIST_DIR=hadoop\CDH_7.1
3. Restart the Developer tool.
Configure Environment Variables

Some adapters require environment variables for the Data Integration Service and Metadata Access Service
to access the distribution packages. For more information, see
Configure environment variables to process complex files.
After You Install 131

Index
A environment variables (continued)

installation 32, 39, 46
AIX library paths on UNIX 100
Java Cryptography Extension 37 UNIX database clients 78, 79
Java Runtime Environment 37
application service upgrade
privileges 105
application services
G
ports 76 graphical mode
upgrading Informatica services 56
B I
back up files
before installing 51 IATEMPDIR
before upgrading 51 environment variables 32, 39, 46
Informatica process
user accounts 77
C Informatica services
upgrading in console mode 67
configuration upgrading in console mode with changes to node 92
environment variables on UNIX 100 upgrading in graphical mode 56
console mode upgrading in silent mode 69
upgrading Informatica services 67, 92 installation
copy files backing up files before 51
after upgrade 122 installation requirements
disk space 38
environment variables 32, 39, 46
D minimum system requirements 29, 37

port requirements 76
database clients isql
configuring 78, 79 testing database connections 78, 79
environment variables 78, 79
IBM DB2 client application enabler 78
Microsoft SQL Server native clients 78
Oracle clients 78
J
Sybase open clients 78 JRE_HOME
databases environment variables 32, 39, 46
testing connections 78, 79
dbs2 connect
testing database connections 78, 79
dependency graph
L
rebuilding 107 LANG
disk space requirements locale environment variables 32, 39, 46
installation requirements 38 LC_ALL
DISPLAY locale environment variables 32, 39, 46
environment variables 46 library paths
domains environment variables 32, 39
ports 76 Linux
database client environment variables 78, 79
E M
environment variables
configuring on UNIX 100 Model Repository Service
database clients 78, 79 upgrade error 107
132
N sqlplus
testing database connections 78, 79
node system requirements
migrating during upgrade 99 minimum 28, 45
node configuration minimum installation requirements 29, 37
completing the change process 99
U
O UNIX
object dependency graph database client environment variables 78, 79
rebuilding 107 database client variables 78, 79
operating system library paths 100
dropped support 75 upgrading in console mode with changes to node 92
upgrading Informatica services in console mode 67
upgrade
P copying files after 122

upgrade error
patch requirements Model Repository Service 107
installation 30, 37 upgrades
PATH backing up files before 51
environment variables 32, 39 user accounts
port requirements Informatica process 77
installation requirements 76 Windows 77
ports
application services 76
domains 76
requirements 76
W
windows
upgrading Informatica services in graphical mode 56
R Windows
user accounts 77
repositories
installing database clients 78
S
silent mode
upgrading Informatica services 69
Index 133

In 1053 UpgradingFromVersion1040AndLater en

Uploaded by

Copyright:

Available Formats

In 1053 UpgradingFromVersion1040AndLater en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

In 1053 UpgradingFromVersion1040AndLater en

Uploaded by

Copyright:

Available Formats

Informatica®

Upgrading from Version

See patents at https://www.informatica.com/legal/patents.html.

Publication Date: 2023-01-16

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

Chapter 2: Apply the hotfix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 3: Before You Upgrade the Domain on Linux. . . . . . . . . . . . . . . . . . . . . . . . . 28

Chapter 4: Before You Upgrade the Domain on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 5: Before You Upgrade the Domain on Windows. . . . . . . . . . . . . . . . . . . . . 44

Chapter 6: Prepare for the Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 7: Upgrade the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Chapter 8: Upgrade the Domain with Changes to Node Configuration. . . . . . . . . 74

Chapter 10: Application Service Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Chapter 11: Informatica Client Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Chapter 12: After You Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Appendix A: Upgrade Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Appendix B: Managing Distribution Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

As an Informatica Network member, you have the following options:

• Search the Knowledge Base for product resources.

Informatica Knowledge Base

Informatica Product Availability Matrices

Informatica Global Customer Support

The upgrade consists of the following phases:

Starts Informatica Services. Starts Informatica Services on the node.

12 Chapter 1: Upgrade Overview

Apply the hotfix

• Hotfix installation and rollback overview, 13

Hotfix installation and rollback overview

Applying the services hotfix

Verify distribution package requirements

Download and extract the installer files

1. Download the hotfix package for your product.

Prepare for hotfix installation

14 Chapter 2: Apply the hotfix

Apply the services hotfix in graphical mode

Applying the services hotfix 15

Apply the services hotfix in console mode

1. Run the installer using the ./install.sh command.

16 Chapter 2: Apply the hotfix

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

Property Name Description

ENABLE_USAGE_COLLECTION Enables the software to automatically transmit to Informatica in the USA

Applying the services hotfix 17

Sample silent input properties

# Use the following guidelines when editing this file

18 Chapter 2: Apply the hotfix

# * The USER_INSTALL_DIR variable must point to a valid directory with write

#The INSTALLATION_ENVIRONMENT property represents the installation environment

# Required only for EDC installation.

# Required only for EDC installation.

# Enter the location of the backup file.

# The INSTALL_HADOOP_LIBRARIES property determines whether to install packages to

# The SELECTED_HADOOP_LIBRARIES property determines the integration packages that you

Applying the services hotfix 19

After you apply the hotfix

Complete the configuration for upgrade or apply hotfix

• <Informatica installation directory>/ODBC7.1/odbc.ini

Remove the distribution packages from the backup location

20 Chapter 2: Apply the hotfix