In 1040 InstallationForPowerCenterAndDataQuality en

Informatica®
10.4.0
Installation for PowerCenter

and Data Quality
Informatica Installation for PowerCenter and Data Quality
10.4.0
© Copyright Informatica LLC 1998, 2020
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.
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.
The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California,
Irvine, and Vanderbilt University, Copyright (©) 1993-2006, all rights reserved.
This product includes Curl software which is Copyright 1996-2013, Daniel Stenberg, <[email protected]>. All Rights Reserved. Permissions and limitations regarding this
software are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software for any purpose with or
without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations
regarding this software are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/license.html.
This product includes OSSP UUID software which is Copyright © 2002 Ralf S. Engelschall, Copyright © 2002 The OSSP Project Copyright © 2002 Cable & Wireless
Deutschland. Permissions and limitations regarding this software are subject to terms available at http://www.opensource.org/licenses/mit-license.php.
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.
Portions of this software and/or documentation are subject to copyright held by third parties. Required third party notices are included with the product.
Publication Date: 2020-04-20

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Informatica Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Informatica Product Availability Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Informatica Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Informatica Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Part I: Installation Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Chapter 1: Installation Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Checklist to Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Plan the Installation Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Service Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Application Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
User Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Secure Data Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Domain Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Informatica Client Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Part II: Before You Install the Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Chapter 2: Before You Install the Services on UNIX or Linux. . . . . . . . . . . . . . . 21

Before You Begin Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Read the Release Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Verify System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Verify Temporary Disk Space and Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Review Patch Requirements on UNIX or Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Verify Port Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Verify the File Descriptor Limit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Verify Application Service Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Back Up the Data Transformation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Configure POSIX Asynchronous I/O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Review the Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Table of Contents 3
Create a System User Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Set Up a Keystore File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Extract the Installer Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Installer Code Signing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Verify the License Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Run the Pre-Installation (i10Pi) System Check Tool in Console Mode. . . . . . . . . . . . . . . . . . . . . 32
Run the Pre-Installation (i10pi) System Check Tool in Silent Mode. . . . . . . . . . . . . . . . . . . . . . 34
Chapter 3: Before You Install the Services on Windows. . . . . . . . . . . . . . . . . . . 36

Before You Install the Services on Windows Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Read the Release Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Verify System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Verify Temporary Disk Space and Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Review the Patch Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Verify Port Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Verify the File Descriptor Limit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Verify Application Service Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Back Up the Data Transformation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Review the Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Create a System User Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Set Up Keystore and Truststore Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Extract the Installer Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Installer Code Signing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Verify the License Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Run the Pre-Installation (i10Pi) System Check Tool in Graphical Mode. . . . . . . . . . . . . . . . . . . . 45
Run the Pre-Installation (i10pi) System Check Tool in Silent Mode. . . . . . . . . . . . . . . . . . . . . . 50
Chapter 4: Prepare for Application Services and Databases. . . . . . . . . . . . . . . 52

Checklist to Prepare for Application Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Prepare for Application Services and Databases Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Set Up Database User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Identify Application Services by Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Domain Configuration Repository Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . 54
IBM DB2 Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Microsoft SQL Server Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Oracle Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
PostgreSQL Database Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Sybase Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Analyst Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Content Management Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Reference Data Warehouse Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Data Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Data Object Cache Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4 Table of Contents
Profiling Warehouse Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Workflow Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Metadata Manager Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Metadata Manager Repository Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . 66
Split Domain for Metadata Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Model Repository Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
PostgreSQL Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Monitoring Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
PowerCenter Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
PowerCenter Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
PowerCenter Repository Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Microsoft Azure SQL Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
PostgreSQL Database Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Sybase ASE Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Search Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Configure Native Connectivity on Service Machines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Install Database Client Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Configure Database Client Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Chapter 5: Prepare for Kerberos Authentication. . . . . . . . . . . . . . . . . . . . . . . . . 82

Checklist to Prepare for Kerberos Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Prepare for Kerberos Authentication Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Set Up the Kerberos Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Generate the Service Principal and Keytab File Name Format. . . . . . . . . . . . . . . . . . . . . . . . . . 84
Service Principal Requirements at Node Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Service Principal Requirements at Process Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Running the SPN Format Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Review the SPN and Keytab Format Text File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Create the Service Principal Names and Keytab Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Troubleshooting the Service Principal Names and Keytab Files. . . . . . . . . . . . . . . . . . . . . 89
Chapter 6: Record Information for Installer Prompts. . . . . . . . . . . . . . . . . . . . . 92

Checklist to Record Installer Prompts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Table of Contents 5
Record Information for Installer Prompts Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Application Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Connection String to a Secure Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Secure Data Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Kerberos. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Chapter 7: Introduction to the Services Installer. . . . . . . . . . . . . . . . . . . . . . . 100

Services Installer Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Pre-install Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Secure Files and Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Part III: Run the Services Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Chapter 8: Install Informatica Services in Console Mode. . . . . . . . . . . . . . . . 103

Informatica Services Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Create a Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Run the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Welcome to the Informatica Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Welcome - Accept Terms and Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Component Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
License and Installation Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Network Security - Service Principal Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Network Security - Kerberos Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Domain Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Domain Security - Secure Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Domain Configuration Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Domain Security - Encryption Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Domain and Node Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Configure Informatica Application Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Configure the Model Repository Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Configure the Monitoring Model Repository Database. . . . . . . . . . . . . . . . . . . . . . . . . . 120
Data Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Content Management Service Parameters and Database. . . . . . . . . . . . . . . . . . . . . . . . 124
Profiling Warehouse Connection Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
PowerCenter Repository Service and PowerCenter Integration Service. . . . . . . . . . . . . . . . 127
Join a domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Run the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Welcome - Accept Terms and Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Installation Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
License and Installation Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
6 Table of Contents
Service Principal Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Domain Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Domain Security - Secure Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Domain Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Domain Security - Encryption Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Join Domain Node Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Port Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Chapter 9: Install Informatica Services in Graphical Mode. . . . . . . . . . . . . . . 135

Install the Services in Graphical Mode Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Creating a Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Joining a Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Chapter 10: Run the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Installing the Informatica Services in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Encrypting Passwords in the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Configure the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Run the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Chapter 11: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Installation Troubleshooting Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Resuming a Failed Installer Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Before You Resume the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Resume the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Troubleshooting with Installation Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Debug Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
File Installation Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Service Manager Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Troubleshooting Domains and Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Creating the Domain Configuration Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Creating or Joining a Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Starting Informatica. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Pinging the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Adding a License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Part IV: After You Install the Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Chapter 12: Complete the Domain Configuration. . . . . . . . . . . . . . . . . . . . . . . 188

Checklist to Complete the Domain Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Complete the Domain Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Verify Locale Settings and Code Page Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Configure Locale Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Configure Environment Variables on UNIX or Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Table of Contents 7
Configure Informatica Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Configure Library Path Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Configure Kerberos Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Chapter 13: Prepare to Create the Application Services. . . . . . . . . . . . . . . . . 193

Checklist for Preparing to Create Application Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Create Directories for the Analyst Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Create a Keystore for a Secure Connection to a Web Application Service. . . . . . . . . . . . . . . . . 194
Log In to Informatica Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Troubleshooting the Login to Informatica Administrator. . . . . . . . . . . . . . . . . . . . . . . . . 195
Create Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
IBM DB2 Connection Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Microsoft SQL Server Connection Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Oracle Connection Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Creating a Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Chapter 14: Create and Configure Application Services. . . . . . . . . . . . . . . . . 201

Checklist to Create and Configure Application Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Create and Configure the Application Services Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Create and Configure the Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Create the Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
After You Create the Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Create and Configure the Data Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Create the Data Integration Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
After You Create the Data Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Create and Configure the PowerCenter Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . 210
Create the PowerCenter Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
After You Create the PowerCenter Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Create and Configure the PowerCenter Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . 213
Create the PowerCenter Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
After You Create the PowerCenter Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . 215
Create and Configure the Metadata Manager Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Create the Metadata Manager Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
After You Create the Metadata Manager Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Create and Configure the Content Management Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Create the Content Management Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Create and Configure the Analyst Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Create the Analyst Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
After You Create the Analyst Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Create and Configure the Search Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Create the Search Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
8 Table of Contents
Part V: Informatica Client Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Chapter 15: Install the Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Install the Clients Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Before You Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Verify System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Verify Third-party Requirements for Informatica Developer. . . . . . . . . . . . . . . . . . . . . . . 229
Verify Third-party Requirements for the PowerCenter Client. . . . . . . . . . . . . . . . . . . . . . . 229
Install the Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
After You Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Install Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Configure the Client for a Secure Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Configure the Developer Tool Workspace Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Starting the PowerCenter Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Starting the Developer Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Chapter 16: Install in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Overview of Install in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Configure the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Run the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Part VI: Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Chapter 17: Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Informatica Uninstallation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Rules and Guidelines for Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Uninstalling the Informatica Server in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Uninstalling Informatica Server in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Uninstalling the Informatica Server in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Informatica Client Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Uninstalling Informatica Clients in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Uninstalling Informatica Clients in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Appendix A: Starting and Stopping Informatica Services. . . . . . . . . . . . . . . . . . . . 243

Starting and Stopping Informatica Services Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Starting and Stopping the Informatica Services from the Console. . . . . . . . . . . . . . . . . . . . . . 243
Stopping Informatica in Informatica Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Starting or Stopping Informatica from the Control Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Starting or Stopping Informatica from the Start Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Starting or Stopping Informatica from a Command Prompt. . . . . . . . . . . . . . . . . . . . . . . . . . 245
Rules and Guidelines for Starting or Stopping Informatica. . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Table of Contents 9
Appendix B: Connecting to Databases from UNIX or Linux. . . . . . . . . . . . . . . . . . 246
Connecting to Databases from UNIX or Linux Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Connecting to an IBM DB2 Universal Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Configuring Native Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Connecting to an Informix Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Configuring ODBC Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Connecting to a Microsoft SQL Server Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Configuring SSL Authentication through ODBC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Configuring Custom Properties for Microsoft SQL Server. . . . . . . . . . . . . . . . . . . . . . . . 251
Connecting to a Netezza Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Connecting to an Oracle Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Connecting to a PostgreSQL Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Connecting to a Sybase ASE Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Connecting to a Teradata Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Connecting to a JDBC Data Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Connecting to an ODBC Data Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Sample odbc.ini File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Appendix C: Connecting to Databases from Windows. . . . . . . . . . . . . . . . . . . . . . . 271

Connecting to Databases from Windows Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Connecting to an IBM DB2 Universal Database from Windows. . . . . . . . . . . . . . . . . . . . . . . . 272
Connecting to an Informix Database from Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Connecting to Microsoft Access and Microsoft Excel from Windows. . . . . . . . . . . . . . . . . . . . 273
Connecting to a Microsoft SQL Server Database from Windows. . . . . . . . . . . . . . . . . . . . . . . 273
Configuring Custom Properties for Microsoft SQL Server. . . . . . . . . . . . . . . . . . . . . . . . 275
Connecting to a Netezza Database from Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Connecting to an Oracle Database from Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Connecting to a PostgreSQL Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Connecting to a Sybase ASE Database from Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
10 Table of Contents
Connecting to a Teradata Database from Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Appendix D: Updating the DynamicSections Parameter of a DB2 Database. . 281

DynamicSections Parameter Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Setting the DynamicSections Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Downloading and Installng the DDconnect JDBC Utility . . . . . . . . . . . . . . . . . . . . . . . . . 281
Running the Test for JDBC Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Table of Contents 11
Preface
Follow the instructions in Installation for PowerCenter and Data Quality to install Informatica services and the
PowerCenter and Informatica Data Quality products. You can install Informatica services and clients on one
or more machines. The guide includes pre- and post-requisite tasks and steps to install the Informatica
services and clients for the Informatica domain. Prerequisite tasks include planning the environment, setting
up databases, and verifying system requirements. Post-requisite tasks include additional application services
and configuring environment variables.
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].
12
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 13
Part I: Installation Getting Started
This part contains the following chapter:
• Installation Getting Started, 15
14
Chapter 1
Installation Getting Started

This chapter includes the following topics:
• Checklist to Getting Started , 15

• Installation Overview, 15
• Installation Process, 16
• Plan the Installation Components, 16
Checklist to Getting Started

This chapter contains high-level concepts and planning information related to installation. Use this checklist
to track the completion of preliminary tasks.
 Understand high-level concepts:

• The installer description and process.
• Informatica domain terminology and components.
 Start high-level planning:

• Installation options. Review the installation options to know the product and options for installation.
• Installation components. Review the description of the installation components and the planning notes.
Installation Overview
Welcome to the Informatica installer Informatica domain services and clients. The Informatica domain
services consist of core services to support the domain and of application services. The Informatica clients
consist of thick client applications and web client applications.
When you install the Informatica domain services, you are prompted to create a domain or to join a domain.
The domain is a collection of nodes that represent the machines on which the application services run. The
first time you run the installer, you must create the domain. If you install on a single machine, you create the
Informatica domain and a gateway node on the machine. If you install on multiple machines, you create an
Informatica domain and a gateway node during the first installation. During the installation on the additional
machines, you create gateway or worker nodes that you join to the domain.
When you run the installer, it installs files for services. You can optionally create application services during
the installation process, or you can manually create application services when the installation completes.
15
Installation Process
The installation of the Informatica domain services and Informatica clients consists of multiple phases.
The installation process varies based on the products that you install. Consider the following high-level tasks
of the installation process:
Perform pre-installation tasks.
1. Plan the Informatica installation. Determine the products that you want to run in your environment.
If you are creating a domain, consider the number of nodes in the domain, the application services
that will run on each node, the system requirements, and the type of user authentication that the
domain will use.
2. Prepare the databases required for repositories, warehouses, and catalogs. Verify the database
requirements and set up the databases.
3. Set up the machines to meet system requirements to ensure that you can successfully install and
run the Informatica services.
4. Determine security requirements for the domain, services, and databases.
Run the installer.
When you run the installer, you can choose from different options based on your requirements.
Complete the configuration.
1. Verify code page compatibility.

2. Configure environment variables.
3. Complete tasks required by the type of user authentication used by the domain.
4. Optionally, configure secure communication for the domain.
5. Create and configure application services.
6. Configure connections required by the application services.
7. Create the users and connections required by the application services.
Install the Informatica client tools.
1. Verify the installation and third-party software requirements for the clients.
2. Use the client installer to install on Windows machines.
3. Configure required environment variables, and optionally install additional languages.
Plan the Installation Components

An Informatica domain is a collection of nodes and services. A node is the logical representation of a
machine in a domain. Services include the Service Manager that manages all domain operations and a set of
16 Chapter 1: Installation Getting Started

application services that represent server-based functionality. The domain and some services require
databases to write metadata and run-time results.
The following image shows a high-level architecture of a domain on multiple nodes:
Nodes
The first time that you install the domain services, you create the Informatica domain and a gateway node.
When you install the domain services on other machines, you create additional nodes that you join to the
domain.
The domain has the following types of nodes:
• Gateway node. A gateway node is any node that you configure to serve as a gateway for the domain. A
gateway node can run application services and it can serve as a master gateway node. The master
gateway node is the entry point to the domain. You can configure more than one node as a gateway node,
but only gateway node acts as the master gateway node at any given time.
• Worker node. A worker node is any node that you do not configure to serve as a gateway for the domain. A
worker node can run application services, but it cannot serve as a gateway.
When you plan the installation: You need to plan the number and type of nodes that you need based on your
service and processing requirements. If you have high availability, you will want to create more than one
gateway node for fail-over functionality.
Service Manager
The Service Manager is a service that manages all domain operations. The Service Manager runs on each
node in the domain and performs domain functions, such as authentication, logging and application service
management. The Service Manager on a gateway node performs more tasks than the Service Manager on a
worker node.
When you plan the installation: Note that the Service Manager functionality is associated with the type of
node.
Application Services
Application services represent server-based functionality. An application service might be required or
optional, and it might require access to a database.
When you run the installer, you can choose to create some services. After you complete the installation, you
create other application services based on the license key generated for your organization.
Plan the Installation Components 17

When you plan the installation: When you plan the application services, you must account for the associated
services that connect to the application service. You also must plan the relational databases that are
required to create the application service.
Databases
Some application services require databases to store metadata and to write run-time results. You need to
create databases for the application services in the domain.
When you plan the installation: You need to create databases and database users required by application
services.
User Authentication
When you run the installer, you can choose the authentication to use for the domain.
The Informatica domain can use the following types of authentication to authenticate uses in the domain:
• Native. Native user accounts are stored in the domain and can only be used within the domain. Native
authentication is default.
• LDAP. LDAP user accounts are stored in an LDAP directory service and are shared by applications within
the enterprise. You can configure LDAP authentication after you run the installer.
• SAML. You can configure Security Assertion Markup Language (SAML) authentication for the
Administrator tool, the Analyst tool, and the Monitoring tool. You can configure SAML authentication after
you run the installer.
• Kerberos. Kerberos user accounts are stored in an LDAP directory service and are shared by applications
within the enterprise. If you enable Kerberos authentication during installation, you must configure the
Informatica domain to work with the Kerberos Key Distribution Center (KDC).
When you plan the installation: You need to plan the type of authentication that you want to use in the
domain. If you want the installer to configure Kerberos authentication, you must prepare the network prior to
installation. You can also configure Kerberos after installation. Note that you cannot configure both SAML
and Kerberos authentication.
Secure Data Storage

Informatica encrypts sensitive data before it stores the data in the Informatica repositories. Informatica uses
a keyword to create an encryption key with which to encrypt sensitive data.
When you create a domain, you must specify a keyword for the installer to use to generate the encryption key
for the domain. Based on the keyword, the installer generates an encryption key file named siteKey and
stores it in a default directory or the directory you specify. All nodes in a domain must use the same
encryption key.
You must specify a keyword even if you do not enable secure communication for the domain or use Kerberos
authentication.
Important: Secure the domain name, the keyword, and the encryption key file location. This information is
required when you change the encryption key or move a repository to another domain.
When you plan the installation: Determine if you want to use a custom siteKey or if you want the installer to
generate one.
18 Chapter 1: Installation Getting Started

Domain Security
When you create a domain, you can enable options to configure security in the domain.
You can configure secure communication for the following domain components:
• Administrator tool. Configure a secure HTTPS connection for the Administrator tool. During installation,
you can provide the keystore file to use for the HTTPS connection.
• Service Manager. Configure a secure connection between the Service Manager and other domain
services. During installation, you can provide keystore and truststore files containing SSL certificates that
you want to use.
• Domain configuration repository. You can secure the domain configuration repository with SSL protocol.
During installation, you can provide the truststore file containing the SSL certificate that you want to use.
When you plan the installation: Determine the level of security that you want to configure for the domain
components. If you decide to configure security for the domain, you must know the location and password
for the keystore and truststore files. If you decide to use Kerberos authentication for the Informatica domain,
you must work with the Kerberos administrator to set up the user and service principals required by the
domain.
Informatica Client Tools

You use Informatica clients to access underlying Informatica functionality in the domain. The clients make
requests to the Service Manager and to application services.
The Informatica clients consist of thick client applications and thin or web client applications that you use to
access services and repositories in the domain.
The following table describes the tools for PowerCenter:
Informatica Client Description
Informatica Developer (the Developer A thick client application to create and run data objects, mappings, profiles,
tool) and workflows.
Informatica Administrator (the A web application to manage the domain and application services.
Administrator tool)
Informatica Analyst (the Analyst tool) A web application to analyze, cleanse, integrate, and standardize data in an
enterprise.
PowerCenter Client A thick client application to create and run mappings, sessions, and
workflows.
When you plan the installation: Determine how many instances of the PowerCenter Client and the Developer
tool that you want to install. You do not need to plan for the web client applications.
Plan the Installation Components 19

Part II: Before You Install the
Services
This part contains the following chapters:
• Before You Install the Services on UNIX or Linux, 21

• Before You Install the Services on Windows, 36
• Prepare for Application Services and Databases, 52
• Prepare for Kerberos Authentication, 82
• Record Information for Installer Prompts, 92
• Introduction to the Services Installer, 100
20
Chapter 2
Before You Install the Services on

UNIX or Linux
• Before You Begin Checklist , 21

• Read the Release Notes, 22
• Verify System Requirements, 22
• Back Up the Data Transformation Files, 27
• Configure POSIX Asynchronous I/O, 28
• Review the Environment Variables, 28
• Create a System User Account, 29
• Set Up a Keystore File, 29
• Extract the Installer Files, 31
• Verify the License Key, 32
• Run the Pre-Installation (i10Pi) System Check Tool in Console Mode, 32
• Run the Pre-Installation (i10pi) System Check Tool in Silent Mode, 34
Before You Begin Checklist

This chapter contains preliminary tasks that you must complete. Use this checklist to track preliminary tasks
before you prepare for services.
 Read the Informatica Release Notes for updates to the installation and upgrade process.
 Verify system requirements:

• Verify the Hadoop distribution.
• Verify sizing requirements based upon your processing and concurrency requirements.
• Review the patch requirements to verify that the machine has the required operating system patches
and libraries.
• Verify
that the port numbers to use for application service processes are available on the machines
where you install the Informatica services.
• Verify that the operating system meets the file descriptor limit.
21
 Back up the Data Transformation files that were created in a previous installation.
 Review system environment variables.
 Create a system user account to run the installer.
 Set up keystore and truststore files if you want to configure secure communication for the domain and
set up a secure connection to web client applications.
 Extract the installer files.
 Verify the license key.
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 limitations 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 on Informatica Network:
https://network.informatica.com/community/informatica-network/product-availability-matrices
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.
To install Informatica with the application services enabled, verify a minimum disk space of 18 GB and a
memory of 6 GB RAM. Out of the 18 GB disk space, 14 GB disk space is required for the product
installation binaries. Based on the runtime configurations that you perform, the Informatica services
might use a disk space around 13,846 MB. 1 GB disk space is the temporary disk space used.
Permissions for the temporary files
Verify that you have read, write, and execute permissions on the /tmp directory.
22 Chapter 2: Before You Install the Services on UNIX or Linux

Review Patch Requirements on UNIX or Linux
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 Operating System Operating System Patch
AIX 7.1 TL4 OS level: 7100-04

bos.adt.debug Version 7.1.2.0
AIX 7.2 TL0 OS level: 7200-00

bos.adt.debug Version 7.2.0.0
PowerCenter on Linux
The following table lists the patches and libraries that the Informatica services require for PowerCenter on
Linux:
zLinux Red Hat Enterprise Linux All of the following packages, where <version> is any version of the
6.9 package:
- e2fsprogs-libs-<version>.el6.s390
- keyutils-libs-<version>.el6.s390
- libselinux-<version>.el6.s390
- libsepol-<version>.el6.s390
AWS Linux AWS Linux release 2 All of the following packages:

(Karoo) - 2.0.20190618 - 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 16.04.5 All of the following packages:

- e2fsprogs-1.42.13-1ubuntu1-amd64-ext2/ext3/ext4 file system utilities
- libkeyutils1:amd64-1.5.9-8ubuntu1-amd64-Linux Key Management
Utilities (library)
- libselinux1:amd64-2.4-3build2-amd64-SELinux runtime shared libraries
- libsepol1:amd64-2.4-2-amd64-SELinux library for manipulating binary
security policies.
Linux-x64 Red Hat Enterprise Linux All of the following packages, where <version> is any version of the
6.7 package:
- e2fsprogs-libs-<version>.el6
- keyutils-libs-<version>.el6
- libselinux-<version>.el6
- libsepol-<version>.el6
Verify System Requirements 23

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
Linux-x64 SUSE Linux Enterprise Service Pack 4

Server 11
Linux-x64 SUSE Linux Enterprise Service Pack 2

Server 12
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 run the installer.
Note: Services and nodes can fail to start if there is a port conflict.
The following table describes the port requirements for installation:
Port Description
Node port Port number for the node created during installation. Default is 6005.
Service Manager port Port number used by the Service Manager on the node. The Service Manager listens for
incoming connection requests on this port. Client applications use this port to communicate
with the services in the domain. 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 Port number that controls server shutdown for the domain Service Manager. The Service
Shutdown port Manager listens for shutdown commands on this port. Default is 6007.
Informatica Port number used by Informatica Administrator. Default is 6008.

Administrator port
Informatica Port number that controls server shutdown for Informatica Administrator. Informatica
Administrator Administrator listens for shutdown commands on this port. Default is 6009.
shutdown port
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 Highest port number in the range of dynamic port numbers that can be assigned to the
number application service processes that run on this node. Default is 6114.

Port Description
Range of dynamic Range of port numbers that can be dynamically assigned to application service processes as
ports for application they start up. When you start an application service that uses a dynamic port, the Service
services Manager dynamically assigns the first available port in this range to the service process. The
number of ports in the range must be at least twice the number of application service
processes that run on the node. Default is 6014 to 6114.
The Service Manager dynamically assigns port numbers from this range to the Model
Repository Service.
Static ports for Static ports have dedicated port numbers assigned that do not change. When you create the
application services application service, you can accept the default port number, or you can manually assign the
port number.
The following services use static port numbers:
- Content Management Service. Default is 8105 for HTTP.
- Data Integration Service. Default is 8095 for HTTP.
Guidelines for Port Configuration

The installer validates the port numbers that you specify to ensure that there will be no port conflicts in the
domain.
Use the following guidelines to determine the port numbers:
• The port number you specify for the domain and for each component in the domain must be unique.
• The port number for the domain and domain components cannot be within the range of the port numbers
that you specify for the application service processes.
• The highest number in the range of port numbers that you specify for the application service processes
must be at least three numbers higher than the lowest port number. For example, if the minimum port
number in the range is 6400, the maximum port number must be at least 6403.
• The port numbers that you specify cannot be lower than 1025 or higher than 65535.
Verify the File Descriptor Limit

Verify that the operating system meets the file descriptor requirement.
Informatica service processes can use a large number of files. To prevent errors that result from the large
number of files and processes, you can change system settings with the limit command if you use a C shell,
or the ulimit command if you use a Bash shell.
List Operating System Settings

To get a list of the operating system settings, including the file descriptor limit, run the following command:
With C shell, run limit

With Bash shell, run ulimit -a
Set the File Descriptor Limit

Informatica service processes can use a large number of files. Set the file descriptor limit per process to
16,000 or higher. The recommended limit is 32,000 file descriptors per process.
To change system settings, run the limit or ulimit command with the pertinent flag and value. For example, to
set the file descriptor limit, run the following command:
With C shell, run limit -h filesize <value>

With Bash shell, run ulimit -n <value>
Set Max User Processes

Informatica services use a large number of user processes. Use the ulimit -u command to adjust the max
user processes setting to a level that is high enough to account for all the processes required by the Blaze
engine.
To set the max user processes, run the following command: Run the following command to set the max user
processes setting:
With C shell, run limit -u processes <value>

With Bash shell, run ulimit -u <value>
Verify Application Service Hardware Requirements

Verify that the nodes in the domain have adequate hardware for the Service Manager and the application
services that run on the nodes.
You can create an Informatica domain with one node and run all application services on the same node. If
you create an Informatica domain with multiple nodes, you can run the application services on separate
nodes. When you plan the application services for the domain, consider system requirements based on the
services that you run on a node.
Note: Based on workload and concurrency requirements, you might need to optimize performance by adding
cores and memory on a node.
The following table lists the minimum system requirements for a node based on some common configuration
scenarios. Use this information as a guideline for other configurations in your domain.
Services Processor Memory Disk Space
One node runs the following services: 2 CPUs with 12 GB 20 GB

- Analyst Service multiple cores
- Content Management Service
- Data Integration Service
- Metadata Manager Service
- Model Repository Service
- PowerCenter Integration Service
- PowerCenter Repository Service
- Search Service
- Web Services Hub

- Search Service
One node runs the following service: 1 CPU with multiple 4 GB n/a
- Analyst Service cores
One node runs the following service: 1 CPU with multiple 4 GB 10 GB

- Search Service cores

One node runs the following services: 1 CPU with multiple 4 GB 10 GB

- Search Service

- Metadata Manager Service multiple cores


- PowerCenter Integration Service cores

- Data Integration Service cores


- Metadata Manager Service cores
One node runs the following service component: 1 CPU with multiple 4 GB 400 MB
- Metadata Manager Agent cores

- Web Services Hub cores
Back Up the Data Transformation Files

Before installation, you must back up the Data Transformation files that were created under previous
versions. After you complete the installation, copy the files to the new installation directories to get the same
repository and 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)
Back Up the Data Transformation Files 27

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.
Configure POSIX Asynchronous I/O

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

Configure environment variables for 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.
If you want to change the default /tmp directory, you must set IATEMPDIR and _JAVA_OPTIONS
environment variables to the new directory.
For example, set the variable to export IATEMPDIR=/home/user.
Note: Unset the IATEMPDIR variable after the installation.
_JAVA Configure the environment variable to change the temporary directory.

_OPTIONS If you want to change the default /tmp directory, you must set IATEMPDIR and _JAVA_OPTIONS the
environment variables to the new directory.
For example, set the variable to export _JAVA_OPTIONS=-Djava.io.tmpdir=/home/user.
Note: Unset the JAVA _OPTIONS variable after the installation.
LANG and Change the locale to set the appropriate character encoding for the terminal session. For example,
LC_ALL 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.

Note: Make sure that the NOEXEC flag is not set for the file system mounted on the /tmp directory.
Create a System User Account

Create a user account specifically to run the Informatica service.
Verify that the user account you use to install Informatica has write permission on the installation directory.
Set Up a Keystore File

When you install the Informatica services, you can configure secure communication for the domain and set
up a secure connection to Informatica Administrator (the Administrator tool). If you configure these security
options, you must set up keystore and truststore files.
Before you install the Informatica services, set up the files for secure communication within the Informatica
domain or for a secure connection to the Administrator tool. To create the required files, you can use the
following programs:
keytool
You can use keytool to create an SSL certificate or a Certificate Signing Request (CSR) as well as
keystores and truststores in JKS format.
OpenSSL
You can use OpenSSL to create an SSL certificate or CSR as well as convert a keystore in JKS format to
PEM format.
For more information about OpenSSL, see the documentation on the following website:
https://www.openssl.org/docs/
For a higher level of security, send your CSR to a Certificate Authority (CA) to get a signed certificate.
The software available for download at the referenced links belongs to a third party or third parties, not
Informatica LLC. 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.
Secure Communication Within the Informatica domain

Before you enable secure communication within the Informatica domain, verify that the following
requirements are met:
You created a certificate signing request (CSR) and private key.
You can use keytool or OpenSSL to create the CSR and private key.
If you use RSA encryption, you must use more than 512 bits.
You have a signed SSL certificate.
The certificate can be self-signed or CA signed. Informatica recommends a CA signed certificate.
Create a System User Account 29

You imported the certificate into keystores.
You must have a keystore in PEM format named infa_keystore.pem and a keystore in JKS format
named infa_keystore.jks.
The keystore files must contain the root and intermediate SSL certificates.
Note: The password for the keystore in JKS format must be the same as the private key pass phrase
used to generate the SSL certificate.
You imported the certificate into truststores.
You must have a truststore in PEM format named infa_truststore.pem and a truststore in JKS format
named infa_truststore.jks.
The truststore files must contain the root, intermediate, and end user SSL certificates.
Important: Import the certificate files one time and then copy them to all machines that host the Data
Integration Service and Metadata Access Service. If the Data Integration Service runs on a grid, mappings
that you push to the Hadoop environment can fail with initialization errors due to inconsistent binary hex
values.
The keystores and truststores are in the correct directory.
The keystore and truststore must be in a directory that is accessible to the installer.
For more information about how to create a custom keystore and truststore, see the Informatica How-To
Library article "How to Create Keystore and Truststore Files for Secure Communication in the Informatica
Domain": https://kb.informatica.com/h2l/HowTo%20Library/1/0700-CreateKeystoresAndTruststores-H2L.pdf
Secure Connection to the Administrator tool

Before you secure the connection to the Administrator tool, verify that the following requirements are met:
You imported the certificate into a keystore in JKS format.
A keystore must contain only one certificate. If you use a unique certificate for each web application
service, create a separate keystore for each certificate. Alternatively, you can use a shared certificate
and keystore.
If you use the installer-generated SSL certificate for the Administrator tool, you do not need to import the
certificate into a keystore in JKS format.
The keystore is in the correct directory.

The keystore must be in a directory that is accessible to the installer.

Extract the Installer Files
The installer files are compressed and distributed as a compressed file.
You can get the installation file 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 and then extract the installer files.
Extract the 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: 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.
Installer Code Signing

You can verify the signature of the Informatica software code.
Informatica uses a certificate based digital signature to sign the Informatica software code. The code signing
helps to validate the authenticity of the code and ensures that there has been no changes or corruptions to
the code after Informatica signs the code. You can determine whether to trust the software based on whether
the code sign is present or not.
You can request a code signing certificate that contains information that fully identifies Informatica LLC and
a Certificate Authority (CA) that issues the certificate. The digital certificate binds the identity of Informatica
to a public key and to a private key.
Digital signing of software begins with the creation of a cryptographic hash, or a digest. The digest has a one
to one correspondence with the original data. Use the digest as there are no hints on how to recreate the
original data, and even a small change in the original data results in a change in the hash value. Informatica
uses its private key to sign the digest, or generates a signature in the form of a string of bits. Good digital
signature algorithms allow a user with the public key to verify the creator of the signature.
To Verify the Signed Code is Authentic

After Informatica signs the software bundle, you can contact Informatica Global Customer Support to access
the code signing certificate. Informatica ships the installer along with the signature file that contains the
hash of the installer binary encrypted with Informatica's private key. You can validate the integrity of digitally
signed binaries using any available tools, such as OpenSSL.
For instance, if you have to verify the package authentication and confirm the code security, enter the
following OpenSSL commands:
openssl base64 -d -in $signature -out /tmp/sign.sha256
openssl dgst -sha256 -verify <(openssl x509 -in <cert> -pubkey -noout) -signature /tmp/
sign.sha256 <file>
Where <signature> is the file containing the signature in Base64, <cert> is the code signing certificate, and
<file> is the file to verify.
Based on verification process, OpenSSL displays a success or error message to validate if the installer code
is genuine or not. Note that the verification for the installer might take around two minutes.
Extract the Installer Files 31

Verify the License Key
Before you install the software, verify that you have the license key available.
When you download the installation files from the Informatica Electronic Software Download (ESD) site, the
license key is in an email message from Informatica. Copy the license key file to a directory accessible to the
user account that installs the product.
Contact Informatica Global Customer Support if you do not have a license key or if you have an incremental
license key and you want to create a domain.
Run the Pre-Installation (i10Pi) System Check Tool in

Console Mode
Run the Pre-installation (i10Pi) System Check Tool to verify whether the machine meets the system
requirements for installation or upgrade.
Ensure that you verified the system requirements and prepared the domain configuration repository
database.
1. Log in to the machine with a system user account.

2. Close all other applications.
3. On a shell command line, run the install file from the root directory.
The installer displays the message to verify that the locale environment variables are set.
4. If the environment variables are not set, press n to exit the installer and set them as required.
If the environment variables are set, press y to continue.
5. Press 1 to install or upgrade Informatica.
6. Press 1 to run the Pre-Installation (i10Pi) System Check Tool that verifies whether the machine meets
the system requirements for the installation or upgrade.
7. From the Informatica Pre-Installation (i10Pi) System Check Tool Welcome section, press Enter.
The System Information section appears.
8. Type the absolute path for the installation directory.
The directory names in the path must not contain spaces or the following special characters: @|* $ # ! %
(){}[],;'
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.
9. Press Enter.
10. Enter the starting port number for the node that you will create or upgrade on the machine. The default
port number for the node is 6005.
11. Press Enter.
The Database and Connection Information section appears.
12. To enter the JDBC connection information using a custom JDBC connection string, press 1. To enter the
JDBC connection information using the JDBC URL information, press 2.

To connect to a secure database, you must enter the JDBC connection using a custom JDBC connection
string.
13. Enter the JDBC connection information.
• To enter the connection information using a custom JDBC connection string, type the connection
string and specify the connection parameters.
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=
Microsoft SQL Server

jdbc:Informatica:sqlserver://<host name>:<port
number>;SelectMethod=cursor;DatabaseName=
Microsoft Azure SQL Database

number>;SelectMethod=cursor;DatabaseName=<database
name>;SnapshotSerializable=true;EncryptionMethod=SSL;HostNameInCertificate=*.datab
ase.windows.net;ValidateServerCertificate=false
PostgreSQL
jdbc:Informatica:postgresql://<host name>:<port number>;DatabaseName=
Sybase
jdbc:Informatica:sybase://<host name>:<port number>;DatabaseName=
Verify that the connection string contains all the connection parameters required by your database
system.
• To enter the connection information using the JDBC URL information, specify the JDBC URL
properties.
The following table describes the connection information:
Prompt Description
Database type Type of database for the domain configuration repository. Select from the
following database types:
- 1 - Oracle
- 2 - Microsoft SQL Server
- 3 - IBM DB2
- 4 - Sybase ASE
- 5 - PostgreSQL
Database user ID User ID for the database user account for the domain configuration repository.
Database user Password for the database user account.

password
Database host name Host name for the database server.
Run the Pre-Installation (i10Pi) System Check Tool in Console Mode 33

Prompt Description
Database port number Port number for the database.
Database service name Service name for Oracle and IBM DB2 databases, or database name for
PostgreSQL, Microsoft SQL Server, and Sybase ASE.
• To connect to a secure database, select 1 to use a custom string and type the connection string.
You must include the security parameters in addition to the connection parameters. For information
about the security parameters you must include in the JDBC connection for a secure database, see
“Connection String to a Secure Database” on page 97.
The tool checks the settings of the hard drive, the availability of the ports, and the configuration of the
database. After the system check is complete, the System Check Summary section displays the results
of the system check.
14. Analyze the results of the system check.

Each requirement is listed, along with one of the following check statuses:
• [Pass] - The requirement meets the criteria for the Informatica installation or upgrade.
• [Fail] - The requirement does not meet the criteria for the Informatica installation or upgrade. Resolve
the issue before you proceed with the installation or upgrade.
• [Information] - Verify the information and perform any additional tasks as outlined in the details.
The results of the system check are saved to the following file: .../Server/i10Pi/i10Pi/en/
i10Pi_summary.txt
15. Press Enter to close the Pre-Installation (i10Pi) System Check Tool.
You can continue to the Informatica service installation or upgrade immediately or end the system check
and continue with the installation or upgrade later. If you continue to the installation or upgrade
immediately, you do not have to restart the installer.
16. To continue to the Informatica service installation or upgrade immediately, press y.
To end the system check and continue with the installation or upgrade later, press n.
If the Pre-Installation (i10Pi) System Check Tool finishes with failed requirements, resolve the failed
requirements and run the Pre-Installation (i10Pi) System Check Tool again.
Note: If the Informatica Pre-Installation (i10Pi) System Check Tool check finishes with failed requirements,
you can still perform the Informatica installation or upgrade. However, Informatica highly recommends that
you resolve the failed requirements before you proceed.
Run the Pre-Installation (i10pi) System Check Tool in

Silent Mode
Run the Pre-installation (i10Pi) System Check Tool in silent mode to verify system requirements for
installation without user intervention.
1. Extract the Informatica services installer file.

2. Navigate to the following location:
<Informatica installer directory>/server/I10PI

3. To specify the properties for the i10pi system check tool in silent mode, update the
SilentInput.properties file in the I10PI folder.
4. To run the i10pi in silent mode, run the silentInstall file in the I10PI folder.
You can view the results of the i10pi system check tool in silent mode from the i10pi_summary.txt file in the
following location:
<Informatica installer directory>/server/I10PI/en
Run the Pre-Installation (i10pi) System Check Tool in Silent Mode 35

Chapter 3
Before You Install the Services on

Windows
• Before You Install the Services on Windows Overview, 36

• Read the Release Notes, 36
• Verify System Requirements, 37
• Back Up the Data Transformation Files, 41
• Review the Environment Variables, 41
• Create a System User Account, 42
• Set Up Keystore and Truststore Files, 42
• Extract the Installer Files, 44
• Verify the License Key, 45
• Run the Pre-Installation (i10Pi) System Check Tool in Graphical Mode, 45
• Run the Pre-Installation (i10pi) System Check Tool in Silent Mode, 50
Before You Install the Services on Windows Overview

Before you install the Informatica services, set up the machine to meet the requirements to install and run the
Informatica platform. If the machine where you install the Informatica services is not configured correctly,
the installation can fail.
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 limitations for the release.
Find the release notes on the Informatica documentation portal.
36
Verify that your environment meets the minimum system requirements for the installation process, temporary
disk space, port availability, databases, and application service hardware.
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.
To install Informatica with the application services enabled, verify a minimum disk space of 18 GB and a
memory of 6 GB RAM. Out of the 18 GB disk space, 14 GB disk space is required for the product
installation binaries. Based on the runtime configurations that you perform, the Informatica services
might use a disk space around 13,846 MB. 1 GB disk space is the temporary disk space used.
Permissions for the temporary files
Verify that you have read, write, and execute permissions on the /tmp directory.
Review the Patch Requirements

Before you install the Informatica services, verify that the machine has the required operating system
patches and libraries.
The following table lists the patches and libraries that the Informatica services require on a Windows
platform:
Windows x64 2016 64-bit None required
Windows x64 2012 R2 64-bit None required
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 run the installer.

Note: Services and nodes can fail to start if there is a port conflict.
The following table describes the port requirements for installation:
Port Description
Node port Port number for the node created during installation. Default is 6005.
Service Manager port Port number used by the Service Manager on the node. The Service Manager listens for
incoming connection requests on this port. Client applications use this port to communicate
with the services in the domain. 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 Port number that controls server shutdown for the domain Service Manager. The Service
Shutdown port Manager listens for shutdown commands on this port. Default is 6007.
Informatica Port number used by Informatica Administrator. Default is 6008.

Administrator port
Informatica Port number that controls server shutdown for Informatica Administrator. Informatica
Administrator Administrator listens for shutdown commands on this port. Default is 6009.
shutdown port
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 Highest port number in the range of dynamic port numbers that can be assigned to the
number application service processes that run on this node. Default is 6114.
Range of dynamic Range of port numbers that can be dynamically assigned to application service processes as
ports for application they start up. When you start an application service that uses a dynamic port, the Service
services Manager dynamically assigns the first available port in this range to the service process. The
number of ports in the range must be at least twice the number of application service
processes that run on the node. Default is 6014 to 6114.
The Service Manager dynamically assigns port numbers from this range to the Model
Repository Service.
Static ports for Static ports have dedicated port numbers assigned that do not change. When you create the
application services application service, you can accept the default port number, or you can manually assign the
port number.
The following services use static port numbers:
- Content Management Service. Default is 8105 for HTTP.
- Data Integration Service. Default is 8095 for HTTP.
Guidelines for Port Configuration

The installer validates the port numbers that you specify to ensure that there will be no port conflicts in the
domain.
Use the following guidelines to determine the port numbers:
• The port number you specify for the domain and for each component in the domain must be unique.
• The port number for the domain and domain components cannot be within the range of the port numbers
that you specify for the application service processes.
38 Chapter 3: Before You Install the Services on Windows

• The highest number in the range of port numbers that you specify for the application service processes
must be at least three numbers higher than the lowest port number. For example, if the minimum port
number in the range is 6400, the maximum port number must be at least 6403.
• The port numbers that you specify cannot be lower than 1025 or higher than 65535.
Verify the File Descriptor Limit

Verify that the operating system meets the file descriptor requirement.
Informatica service processes can use a large number of files. To prevent errors that result from the large
number of files and processes, you can change system settings with the limit command if you use a C shell,
or the ulimit command if you use a Bash shell.
List Operating System Settings

To get a list of the operating system settings, including the file descriptor limit, run the following command:
With C shell, run limit

With Bash shell, run ulimit -a
Set the File Descriptor Limit

Informatica service processes can use a large number of files. Set the file descriptor limit per process to
16,000 or higher. The recommended limit is 32,000 file descriptors per process.
To change system settings, run the limit or ulimit command with the pertinent flag and value. For example, to
set the file descriptor limit, run the following command:
With C shell, run limit -h filesize <value>

With Bash shell, run ulimit -n <value>
Set Max User Processes

Informatica services use a large number of user processes. Use the ulimit -u command to adjust the max
user processes setting to a level that is high enough to account for all the processes required by the Blaze
engine.
To set the max user processes, run the following command: Run the following command to set the max user
processes setting:
With C shell, run limit -u processes <value>

With Bash shell, run ulimit -u <value>
Verify Application Service Hardware Requirements

Verify that the nodes in the domain have adequate hardware for the Service Manager and the application
services that run on the nodes.
You can create an Informatica domain with one node and run all application services on the same node. If
you create an Informatica domain with multiple nodes, you can run the application services on separate
nodes. When you plan the application services for the domain, consider system requirements based on the
services that you run on a node.
Note: Based on workload and concurrency requirements, you might need to optimize performance by adding
cores and memory on a node.

The following table lists the minimum system requirements for a node based on some common configuration
scenarios. Use this information as a guideline for other configurations in your domain.

- Search Service
- Web Services Hub

- Search Service
One node runs the following service: 1 CPU with multiple 4 GB n/a

- Search Service cores

- Search Service



- PowerCenter Integration Service cores



- Metadata Manager Service cores

One node runs the following service component: 1 CPU with multiple 4 GB 400 MB
- Metadata Manager Agent cores

- Web Services Hub cores
Back Up the Data Transformation Files

Before installation, you must back up the Data Transformation files that were created under previous
versions. After you complete the installation, copy the files to the new installation directories to get the same
repository and custom global components as in the previous version.
The following table lists the files or directories that you must back up:
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)
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.
Review the Environment Variables

Configure the environment variables to work with the Informatica installation.
Back Up the Data Transformation Files 41

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

requires 1 GB disk space for temporary files.
Configure the environment variable if you do not want to create temporary files
in the default drive.
PATH The installer appends file paths required by Informatica to the PATH
environment variable. Verify that the length of the PATH environment variable
does not exceed the system limits.
Create a System User Account

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

When you install the Informatica services, you can configure secure communication for the domain and set
up a secure connection to Informatica Administrator (the Administrator tool). If you configure these security
options, you must set up keystore and truststore files.
Before you install the Informatica services, set up the files for secure communication within the Informatica
domain or for a secure connection to the Administrator tool. To create the required files, you can use the
following programs:
keytool
You can use keytool to create an SSL certificate or a Certificate Signing Request (CSR) as well as
keystores and truststores in JKS format.

For more information about using keytool, see the documentation on the following web site:
http://docs.oracle.com/javase/7/docs/technotes/tools/windows/keytool.html.
OpenSSL
You can use OpenSSL to create an SSL certificate or CSR as well as convert a keystore in JKS format to
PEM format.
For more information about OpenSSL, see the documentation on the following website:
https://www.openssl.org/docs/
For a higher level of security, send your CSR to a Certificate Authority (CA) to get a signed certificate.
The software available for download at the referenced links belongs to a third party or third parties, not
Informatica LLC. 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.
Secure Communication Within the Informatica domain

Before you enable secure communication within the Informatica domain, verify that the following
requirements are met:
You imported the certificate into keystores.
You must have a keystore in PEM format named infa_keystore.pem and a keystore in JKS format
The keystore files must contain the root and intermediate SSL certificates.
Note: The password for the keystore in JKS format must be the same as the private key pass phrase
used to generate the SSL certificate.
You imported the certificate into truststores.
You must have a truststore in PEM format named infa_truststore.pem and a truststore in JKS format
named infa_truststore.jks.
The truststore files must contain the root, intermediate, and end user SSL certificates.
The keystores and truststores are in the correct directory.

The keystore and truststore must be in a directory that is accessible to the installer.
Secure Connection to the Administrator tool

Before you secure the connection to the Administrator tool, verify that the following requirements are met:
Set Up Keystore and Truststore Files 43

and keystore.
The keystore is in the correct directory.
The keystore must be in a directory that is accessible to the installer.
Extract the Installer Files

The installer files are compressed and distributed as a compressed file.
You can get the installation file 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 and then extract the installer files.
Extract the 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: 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.
Installer Code Signing

You can verify the signature of the Informatica software code.
Informatica uses a certificate based digital signature to sign the Informatica software code. The code signing
helps to validate the authenticity of the code and ensures that there has been no changes or corruptions to
the code after Informatica signs the code. You can determine whether to trust the software based on whether
the code sign is present or not.
You can request a code signing certificate that contains information that fully identifies Informatica LLC and
a Certificate Authority (CA) that issues the certificate. The digital certificate binds the identity of Informatica
to a public key and to a private key.
Digital signing of software begins with the creation of a cryptographic hash, or a digest. The digest has a one
to one correspondence with the original data. Use the digest as there are no hints on how to recreate the
original data, and even a small change in the original data results in a change in the hash value. Informatica
uses its private key to sign the digest, or generates a signature in the form of a string of bits. Good digital
signature algorithms allow a user with the public key to verify the creator of the signature.
To Verify the Signed Code is Authentic

After Informatica signs the software bundle, you can contact Informatica Global Customer Support to access
the code signing certificate. Informatica ships the installer along with the signature file that contains the
hash of the installer binary encrypted with Informatica's private key. You can validate the integrity of digitally
signed binaries using any available tools, such as OpenSSL.

For instance, if you have to verify the package authentication and confirm the code security, enter the
following OpenSSL commands:
openssl base64 -d -in $signature -out /tmp/sign.sha256
openssl dgst -sha256 -verify <(openssl x509 -in <cert> -pubkey -noout) -signature /tmp/
sign.sha256 <file>
Where <signature> is the file containing the signature in Base64, <cert> is the code signing certificate, and
<file> is the file to verify.
Based on verification process, OpenSSL displays a success or error message to validate if the installer code
is genuine or not. Note that the verification for the installer might take around two minutes.
Verify the License Key

Before you install the software, verify that you have the license key available.
When you download the installation files from the Informatica Electronic Software Download (ESD) site, the
license key is in an email message from Informatica. Copy the license key file to a directory accessible to the
user account that installs the product.
Contact Informatica Global Customer Support if you do not have a license key or if you have an incremental
license key and you want to create a domain.
Run the Pre-Installation (i10Pi) System Check Tool in

Graphical Mode
Run the Pre-installation (i10Pi) System Check Tool to verify whether the machine meets the system
requirements for installation or upgrade.
Ensure that you verified the system requirements and prepared the domain configuration repository
database.

3. Go to the root of the directory that contains the installation files and run install.bat as administrator.
4. Select Install Informatica 10.4.0.
Verify the License Key 45

5. Select Run the Pre-Installation (i10Pi) System Check Tool to verify whether the machine meets the
system requirements for the installation or upgrade.
6. Click Start.

The Informatica Pre-Installation (i10Pi) System Check Tool Welcome page appears.
7. Click Next.
The System Information page appears.
8. Enter the absolute path for the installation directory.
Run the Pre-Installation (i10Pi) System Check Tool in Graphical Mode 47

The directory names in the path must not contain spaces or the following special characters: @ | * $ # !
%(){}[],;'
9. Enter the starting port number for the node that you will create or upgrade on the machine. The default
port number for the node is 6005.
10. Click Next.
The Database and JDBC Connection Information page appears.
11. Enter the information for the domain configuration repository database.
The following table describes the properties that you specify for the database and user account:
Property Description
Database type Database for the repository. Select one of the following databases:
- Oracle
- IBM DB2
- Microsoft SQL Server
- PostgreSQL
- Sybase ASE
Database user ID User account for the repository database.
User password Password for the database user account.
The domain configuration repository must be accessible to all gateway nodes in the domain.
12. If you plan to use a secure database for the domain configuration repository, select the Secure database
option.

13. Enter the database 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 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.
IBM DB2
Oracle


name>;SnapshotSerializable=true;EncryptionMethod=SSL;HostNameInCertificate=*.datab
ase.windows.net;ValidateServerCertificate=false
PostgreSQL
Sybase
system.
Run the Pre-Installation (i10Pi) System Check Tool in Graphical Mode 49

• If you select the Secure database option, select Custom JDBC connection string and type the
connection string.
You must include the security parameters in addition to the connection parameters. For information
about the security parameters you must include in the JDBC connection for a secure database, see
“Connection String to a Secure Database” on page 97.
14. Click Test Connection to verify that you can connect to the database, and then click OK to continue.
15. Click Next to start the system check.
The tool checks the settings of the hard drive, the availability of the ports, and the configuration of the
database. After the system check is complete, the System Check Summary page appears, displaying the
results of the system check.
16. Analyze the results of the system check.
Each requirement is listed, along with one of the following check statuses:
• [Pass] - The requirement meets the criteria for the Informatica installation or upgrade.
• [Fail] - The requirement does not meet the criteria for the Informatica installation or upgrade. Resolve
the issue before you proceed with the installation or upgrade.
• [Information] - Verify the information and perform any additional tasks as outlined in the details.
The results of the system check are saved to the following file: .../Server/i10Pi/i10Pi/en/
i10Pi_summary.txt
17. Click Done to close the Pre-Installation (i10Pi) System Check Tool.
Run the Pre-Installation (i10pi) System Check Tool in

Silent Mode
Run the Pre-installation (i10Pi) System Check Tool in silent mode to verify system requirements for
installation without user intervention.
1. Extract the Informatica services installer file.

2. Navigate to the following location:
<Informatica installer directory>/server/I10PI
3. To specify the properties for the i10pi system check tool in silent mode, update the
SilentInput.properties file in the I10PI folder.
4. To run the i10pi in silent mode, run the silentInstall file in the I10PI folder.
You can view the results of the i10pi system check tool in silent mode from the i10pi_summary.txt file in the
following location:
<Informatica installer directory>/server/I10PI/en

Run the Pre-Installation (i10pi) System Check Tool in Silent Mode 51

Chapter 4
Prepare for Application Services

and Databases
• Checklist to Prepare for Application Services , 52

• Prepare for Application Services and Databases Overview, 53
• Set Up Database User Accounts, 53
• Identify Application Services by Product, 53
• Domain Configuration Repository Database Requirements, 54
• Analyst Service , 58
• Content Management Service, 59
• Data Integration Service, 61
• Metadata Manager Service, 65
• Model Repository Service, 71
• Monitoring Model Repository Service, 74
• PowerCenter Integration Service, 74
• PowerCenter Repository Service, 75
• Search Service, 78
• Configure Native Connectivity on Service Machines, 78
Checklist to Prepare for Application Services

This chapter contains information about application services and databases for the Informatica environment.
Use this checklist to track service planning and database preparation.
 Identify the application services that you need in your environment.
 Identify the application services that you want the installer to create.
 Prepare databases for the services:

• Create the database.
• Create a user for the database.
• Create environment variables.
52
• Configure connectivity.
Prepare for Application Services and Databases

Overview
When you plan the application services, you must account for the associated services that connect to the
application service. You also must plan the relational databases that the application service requires.
The installer prompts you to optionally create some services during the installation. Some service properties
require database information. If you want the installer to create a service that requires a database, you must
prepare the database before you run the installer. To prepare the databases, verify the data base
requirements, set up the database, and set up a user account. The database requirements depend on the
application services that you create.
If you do not create services during installation, you can create them manually after you install.
Set Up Database User Accounts

Set up a database and user account for the repository databases.
Use the following rules and guidelines when you set up the user accounts:
• The database user account must have permissions to create and drop tables, indexes, and views, and to
select, insert, update, and delete data from tables.
• Use 7-bit ASCII to create the password for the account.
• To prevent database errors in one repository from affecting any other repository, create each repository in
a separate database schema with a different database user account. Do not create a repository in the
same database schema as the domain configuration repository or any other repository in the domain.
Identify Application Services by Product

Each application service provides different functionality within the Informatica domain. You create
application services based on the license key generated for your organization.
Prepare for Application Services and Databases Overview 53

The following table lists the application services that each product uses:
Product Application Services
PowerCenter - Analyst Service

- Content Management Service *
- Data Integration Service *
- Model Repository Service *
- monitoring Model Repository Service *
- PowerCenter Integration Service *
- PowerCenter Repository Service *
- Search Service
- Web Services Hub Service
Informatica Data Quality - Analyst Service

- Content Management Service *
- Data Integration Service *
- Model Repository Service *
- monitoring Model Repository Service *
- PowerCenter Integration Service *
- PowerCenter Repository Service *
- Search Service
* You can create these services when you install the product.
Note that services might vary depending on the product edition you have.
Domain Configuration Repository Database

Requirements
Informatica components store metadata in relational database repositories. The domain stores configuration
and user information in a domain configuration repository.
You must set up a database and user account for the domain configuration repository before you run the
installation. The database must be accessible to all gateway nodes in the Informatica domain.
When you install Informatica, you provide the database and user account information for the domain
configuration repository. The Informatica installer uses JDBC to communicate with the domain configuration
repository.
The domain configuration repository supports the following database types:
• IBM DB2 UDB

• Microsoft SQL Server
• Microsoft Azure SQL Database
• Oracle
• PostgreSQL
• Sybase ASE
Allow 200 MB of disk space for the database.
54 Chapter 4: Prepare for Application Services and Databases

IBM DB2 Database Requirements
Use the following guidelines when you set up the repository on IBM DB2:
• If the repository is in an IBM DB2 database, verify that IBM DB2 Version 10.5 is installed.
• On the IBM DB2 instance where you create the database, set the following parameters to ON:
- DB2_SKIPINSERTED
- DB2_EVALUNCOMMITTED
- DB2_SKIPDELETED
- AUTO_RUNSTATS
• On the database, set the configuration parameters.
The following table lists the configuration parameters that you must set:
Parameter Value
logfilsiz 8000
maxlocks 98
locklist 50000
auto_stmt_stats ON
• Set the tablespace pageSize parameter to 32768 bytes.

In a single-partition database, specify a tablespace that meets the pageSize requirements. If you do not
specify a tablespace, the default tablespace must meet the pageSize requirements.
In a multi-partition database, specify a tablespace that meets the pageSize requirements. Define the
tablespace in the catalog partition of the database.
• Set the NPAGES parameter to at least 5000. The NPAGES parameter determines the number of pages in
the tablespace.
• Verify that the database user has CREATETAB, CONNECT, and BINDADD privileges.
• Informatica does not support IBM DB2 table aliases for repository tables. Verify that table aliases have
not been created for any tables in the database.
• In the DataDirect Connect for JDBC utility, update the DynamicSections parameter to 3000.
The default value for DynamicSections is too low for the Informatica repositories. Informatica requires a
larger DB2 package than the default. When you set up the DB2 database for the domain configuration
repository or a Model repository, you must set the DynamicSections parameter to at least 3000. If the
DynamicSections parameter is set to a lower number, you can encounter problems when you install or run
Informatica services.
Domain Configuration Repository Database Requirements 55

Microsoft SQL Server Database Requirements
Use the following guidelines when you set up the repository:
• Set the allow snapshot isolation and read committed isolation level to ALLOW_SNAPSHOT_ISOLATION
and READ_COMMITTED_SNAPSHOT to minimize locking contention.
To set the isolation level for the database, run the following commands:
ALTER DATABASE DatabaseName SET ALLOW_SNAPSHOT_ISOLATION ON
ALTER DATABASE DatabaseName SET READ_COMMITTED_SNAPSHOT ON
To verify that the isolation level for the database is correct, run the following commands:
SELECT snapshot_isolation_state FROM sys.databases WHERE name=[DatabaseName]
SELECT is_read_committed_snapshot_on FROM sys.databases WHERE name = DatabaseName
• The database user account must have the CONNECT, CREATE TABLE, and CREATE VIEW privileges.
Oracle Database Requirements

Use the following guidelines when you set up the repository on Oracle:
• Set the open_cursors parameter to 4000 or higher.

• Set the permissions on the view $parameter for the database user.
• Set the privileges for the database user to run show parameter open_cursors in the Oracle database.
When you run the pre-installation (i10Pi) system check tool, i10Pi runs the command against the database
to identify the OPEN_CURSORS parameter with the domain database user credentials.
You can run the following query to determine the open cursors setting for the domain database user
account:
SELECT VALUE OPEN_CURSORS FROM V$PARAMETER WHERE UPPER(NAME)=UPPER('OPEN_CURSORS')
• Verify that the database user has the following privileges:
CREATE SEQUENCE
CREATE SESSION
CREATE SYNONYM
CREATE TABLE
CREATE VIEW
• Informatica does not support Oracle public synonyms for repository tables. Verify that public synonyms
have not been created for any tables in the database.
PostgreSQL Database Requirements

Use the following guidelines when you set up the repository on PostgreSQL:
• Verify that the database user account has CONNECT, CREATE TABLE, and CREATE VIEW privileges.
• Specify the database schema name when you use PostgreSQL as the database.
• Ensure that PostgreSQL has sufficient disk space for the data files. By default, the data files are present in
the following location:
<PostgreSQL installation directory>/data

The following table lists the minimum and recommended values for the configuration parameters that you
must set:
Parameter Minimum Value Recommended Value
max_connections 200 4000
shared_buffers 2 GB 16 GB
max_locks_per_transaction 1024 1024
Sybase Database Requirements

Use the following guidelines when you set up the repository on Sybase ASE:
• Set the database server page size to 16K or higher. You must set the page size to 16K as this is a one-
time configuration and cannot be changed afterwards.
• Set the database locking configuration to use row-level locking.
The following table describes the database locking configuration that you must set:
Database Configuration Sybase System Procedure Value
Lock scheme sp_configure "lock scheme" 0, datarows
• Set the Sybase database option "ddl in tran" to TRUE.

• Set "allow nulls by default" to TRUE.
• Turn ON the Sybase database option select into/bulkcopy/pllsort.
• Enable the "select" privilege for the sysobjects system table.
• Create the following login script to disable the default VARCHAR truncation:
create procedure dbo.sp_string_rtrunc_proc as set string_rtruncation on
sp_modifylogin "user_name", "login script", sp_string_rtrunc_proc
The login script is executed every time the user logs into the Sybase instance. The stored procedure sets
the parameter at the session level. The sp_modifylogin system procedure updates "user_name" with the
stored procedure as its "login script". The user must have permission to invoke the stored procedure.
• Verify that the database user has CREATE DEFAULT, CREATE PROCEDURE, CREATE RULE, CREATE
TABLE, and CREATE VIEW privileges.
• Set the database configurations to the recommended baseline values.
The following table lists the database memory configuration parameters that you must set:
Maximum amount of total sp_configure "max memory" 2097151

physical memory
Procedure cache size sp_configure "procedure cache size" 500000
Number of open objects sp_configure "number of open objects" 5000
Number of open indexes sp_configure "number of open indexes" 5000
Domain Configuration Repository Database Requirements 57

Number of open partitions sp_configure "number of open partitions" 5000
Heap memory per user sp_configure "heap memory per user" 49152
Number of locks sp_configure "number of locks" 100000
Analyst Service
The Analyst service runs the Analyst tool. It manages the connections between service components and the
user that have access to the Analyst tool. When you create the service, you need to associate other
application services with it.
The following table summarizes some dependencies that are associated with the Analyst Service:
Dependency Summary
Products The following products use the Analyst Service:

- Data Engineering Integration
- Data Engineering Quality
- Data Engineering Streaming
- Enterprise Data Catalog
- Informatica Data Quality
- PowerCenter
Services The Analyst Service requires a direct association with the following services:
Databases The Analyst Service does not have any associated database.
Installer You cannot create the Analyst Service during installation.

Content Management Service
The Content Management Service manages reference data for data domains that use reference tables. It
uses the Data Integration Service to run mappings to transfer data between reference tables and external
data sources. When you create the service, you need to associate other application services with it.
The following table summarizes the dependencies for products, services, and databases that are associated
with the Content Management Service:
Dependency Summary
Products The following products use the Content Management Service:

- Enterprise Data Preparation
Services The Content Management Service requires a direct association with the following services:
Databases The Content Management Service uses the following database:

- Reference data warehouse. Stores data values for the reference table objects that you define in the
Model repository. When you add data to a reference table, the Content Management Service writes
the data values to a table in the reference data warehouse.
Installer You can create the Content Management Service when you run the installer.
Note: You must create the Content Management Service on the same node as the Data Integration
Service.
Reference Data Warehouse Requirements

The reference data warehouse stores the data values for reference table objects that you define in a Model
repository. You configure a Content Management Service to identify the reference data warehouse and the
Model repository.
You associate a reference data warehouse with a single Model repository. You can select a common
reference data warehouse on multiple Content Management Services if the Content Management Services
identify a common Model repository. The reference data warehouse must support mixed-case column
names.
The reference data warehouse supports the following database types:
• IBM DB2 UDB

• Oracle
Note: Ensure that you install the database client on the machine on which you want to run the Content
Management Service.
Content Management Service 59

• Verify that the database user account has CREATETAB and CONNECT privileges.
• Verify that the database user has SELECT privileges on the SYSCAT.DBAUTH and SYSCAT.DBTABAUTH
tables.
the tablespace.

• Verify that the database user account has CONNECT and CREATE TABLE privileges.

ALTER SEQUENCE
ALTER TABLE
CREATE SEQUENCE
CREATE SESSION
CREATE TABLE
CREATE VIEW
DROP SEQUENCE
DROP TABLE

Data Integration Service
The Data Integration Service receives requests from Informatica client tools to run integration, profile, and
data preparation jobs. It writes results to different databases, and it writes run-time metadata to the Model
repository. When you create the service, you need to associate another application service with it.
The following table lists the dependencies for products, services, and databases that are associated with the
Data Integration Service.
Dependency Summary
Products The following products use the Data Integration Service:

- PowerCenter
Services The Data Integration Service requires a direct association with the following service:
Databases The Data Integration Service uses the following databases:

- Data object cache. Stores cached logical data objects and virtual tables.
- Profiling warehouse. Stores profiling information, such as profile and scorecard results.
- Workflow database. Stores run-time metadata for workflows.
Installer You can create the Data Integration Service when you run the installer.
Data Object Cache Database Requirements

The data object cache database stores cached logical data objects and virtual tables for the Data Integration
Service. You specify the data object cache database connection when you create the Data Integration
Service.
The data object cache database supports the following database types:
• IBM DB2 UDB

• Oracle
Note: Ensure that you install the database client on the machine on which you want to run the Data
Integration Service.

Data Integration Service 61

the tablespace.


CREATE INDEX
CREATE SESSION
CREATE SYNONYM
CREATE TABLE
CREATE VIEW
DROP TABLE
INSERT INTO TABLE
UPDATE TABLE
Profiling Warehouse Requirements

The profiling warehouse database stores profiling and scorecard results. You specify the profiling warehouse
connection when you create the Data Integration Service.
The profiling warehouse supports the following database types:
• IBM DB2 UDB

• Oracle
Allow 10 GB of disk space for the database.
Integration Service. You can specify a JDBC connection as the profiling warehouse connection for IBM DB2
UDB, Microsoft SQL Server, and Oracle database types.
For more information about configuring the database, see the documentation for your database system.

• The database user account must have the CREATETAB, CONNECT, CREATE VIEW, and CREATE FUNCTION
privileges.

the tablespace.
Note: Informatica does not support the partitioned database environment for IBM DB2 databases when you
use a JDBC connection as the profiling warehouse connection.

• The database user account must have the CONNECT, CREATE TABLE, CREATE VIEW, and CREATE
FUNCTION privileges.

ALTER TABLE
CREATE ANY INDEX
CREATE PROCEDURE
CREATE SESSION
CREATE TABLE
CREATE VIEW
DROP TABLE
UPDATE TABLE
• Set the following parameters to the Informatica recommended values:
Parameter Recommended Value
open_cursors 4000
Sessions 1000
Processes 1000
Workflow Database Requirements

The Data Integration Service stores run-time metadata for workflows in the workflow database. Before you
create the workflow database, set up a database and database user account for the workflow database.
You specify the workflow database connection when you create the Data Integration Service.
Data Integration Service 63

The workflow database supports the following database types:
• IBM DB2 UDB

• Oracle

the tablespace.
• Set the connection pooling parameters.
The following table lists the connection pooling parameters that you must set:
Parameter Value
Maximum Connection Pool Size 128
Minimum Connection Pool Size 0
Maximum Idle Time 120 seconds

Parameter Value

ALTER TABLE
ALTER VIEW
CREATE SEQUENCE
CREATE SESSION
CREATE SYNONYM
CREATE TABLE
CREATE VIEW
DROP TABLE
DROP VIEW
Parameter Value
Metadata Manager Service

The Metadata Manager Service runs the Metadata Manager web client in the Informatica domain. The
Metadata Manager Service manages the connections between service components and the users that have
access to Metadata Manager.
with the Metadata Manager Service.
Dependency Summary
Products The following products use the Metadata Manager Service:

- PowerCenter
Services The Metadata Manager Service requires a direct association with the following services:
Metadata Manager Service 65

Dependency Summary
Databases The Metadata Manager Service uses the following database:

- Metadata Manager repository. Stores the Metadata Manager warehouse and metadata models.
Installer You cannot create the Metadata Manager Service when you run the installer. You must create the
service after the installation completes.
Metadata Manager Repository Database Requirements

The Metadata Manager repository is a centralized location in a relational database that stores metadata from
disparate metadata sources. It also stores the Metadata Manager warehouse and the models for each
metadata source type. Each Metadata Manager application is configured to run with one Metadata Manager
repository.
The Metadata Manager repository supports the following database types:
• IBM DB2 UDB

• Oracle
Allow 1 GB of disk space for the database.

• The database user account that creates the repository must have privileges to perform the following
operations:
ALTER TABLE
CREATE FUNCTION
CREATE INDEX
CREATE PROCEDURE
CREATE TABLE
CREATE VIEW
DROP PROCEDURE
DROP TABLE
INSERT INTO
• The database user that creates the repository must be able to create tablespaces with page sizes of 32
KB.
• Set up system temporary tablespaces larger than the default page size of 4 KB and update the heap sizes.
Queries running against tables in tablespaces defined with a page size larger than 4 KB require system
temporary tablespaces with a page size larger than 4 KB. If there are no system temporary table spaces
defined with a larger page size, the queries can fail. The server displays the following error:
SQL 1585N A system temporary table space with sufficient page size does not exist.
SQLSTATE=54048

Create system temporary tablespaces with page sizes of 8 KB, 16 KB, and 32 KB. Run the following SQL
statements on each database to configure the system temporary tablespaces and update the heap sizes:
CREATE Bufferpool RBF IMMEDIATE SIZE 1000 PAGESIZE 32 K EXTENDED STORAGE ;
CREATE Bufferpool STBF IMMEDIATE SIZE 2000 PAGESIZE 32 K EXTENDED STORAGE ;
CREATE REGULAR TABLESPACE REGTS32 PAGESIZE 32 K MANAGED BY SYSTEM USING ('C:
\DB2\NODE0000\reg32' ) EXTENTSIZE 16 OVERHEAD 10.5 PREFETCHSIZE 16 TRANSFERRATE 0.33
BUFFERPOOL RBF;
CREATE SYSTEM TEMPORARY TABLESPACE TEMP32 PAGESIZE 32 K MANAGED BY SYSTEM USING
('C:\DB2\NODE0000\temp32' ) EXTENTSIZE 16 OVERHEAD 10.5 PREFETCHSIZE 16 TRANSFERRATE
0.33 BUFFERPOOL STBF;
GRANT USE OF TABLESPACE REGTS32 TO USER <USERNAME>;
UPDATE DB CFG FOR <DB NAME> USING APP_CTL_HEAP_SZ 16384
UPDATE DB CFG FOR <DB NAME> USING APPLHEAPSZ 16384
UPDATE DBM CFG USING QUERY_HEAP_SZ 8000
UPDATE DB CFG FOR <DB NAME> USING LOGPRIMARY 100
UPDATE DB CFG FOR <DB NAME> USING LOGFILSIZ 2000
UPDATE DB CFG FOR <DB NAME> USING LOCKLIST 1000
UPDATE DB CFG FOR <DB NAME> USING DBHEAP 2400
"FORCE APPLICATIONS ALL"
DB2STOP
DB2START
• Set the locking parameters to avoid deadlocks when you load metadata into a Metadata Manager
repository on IBM DB2.
The following table lists the locking parameters you can configure:
Parameter Name Value IBM DB2 Description
LOCKLIST 8192 Max storage for lock list (4KB)
MAXLOCKS 10 Percent of lock lists per application
LOCKTIMEOUT 300 Lock timeout (sec)
DLCHKTIME 10000 Interval for checking deadlock (ms)
Also, for IBM DB2 9.7 and earlier, set the DB2_RR_TO_RS parameter to YES to change the read policy from
Repeatable Read to Read Stability.
Note: If you use IBM DB2 as a metadata source, the source database has the same configuration
requirements.

• The database user account that creates the repository must have privileges to perform the following
operations:
ALTER TABLE
CREATE CLUSTERED INDEX
CREATE INDEX
CREATE PROCEDURE
CREATE TABLE
CREATE VIEW
DROP PROCEDURE
DROP TABLE
INSERT INTO
• If the repository must store metadata in a multibyte language, set the database collation to that multibyte
language when you install Microsoft SQL Server. For example, if the repository must store metadata in
Japanese, set the database collation to a Japanese collation when you install Microsoft SQL Server. This
is a one-time configuration and cannot be changed.

ALTER TABLE
CREATE CLUSTER
CREATE INDEX
CREATE OR REPLACE FORCE VIEW
CREATE OR REPLACE PROCEDURE
CREATE OR REPLACE VIEW
CREATE SESSION
CREATE TABLE
DROP TABLE
INSERT INTO TABLE
• Set the following parameters for the tablespace on Oracle:
<Temporary tablespace>
Resize to at least 2 GB.
CURSOR_SHARING
Set to FORCE.
MEMORY_TARGET
Set to at least 4 GB.
Run SELECT * FROM v$memory_target_advice ORDER BY memory_size; to determine the optimal

MEMORY_SIZE.

MEMORY_MAX_TARGET
Set to greater than the MEMORY_TARGET size.
If MEMORY_MAX_TARGET is not specified, MEMORY_MAX_TARGET defaults to the

MEMORY_TARGET setting.
OPEN_CURSORS
Set to 3000 shared.
Monitor and tune open cursors. Query v$sesstat to determine the number of currently-opened
cursors. If the sessions are running close to the limit, increase the value of OPEN_CURSORS.
UNDO_MANAGEMENT
Set to AUTO.
• If the repository must store metadata in a multibyte language, set the NLS_LENGTH_SEMANTICS
parameter to CHAR on the database instance. Default is BYTE.
Split Domain for Metadata Manager

If your product bundle includes Metadata Manager, you must decide whether to create one domain or a split
domain. In a split domain, the application services associated with the primary components of your product
bundle run in one domain, and the application services associated with Metadata Manager run in a separate
domain.
When you configure a split domain, you can upgrade Metadata Manager without having to upgrade the
primary components of your product bundle. Metadata Manager can run on a more recent product version
than the other components.
For example, your product bundle includes PowerCenter and Metadata Manager. In a split domain, the
application services associated with PowerCenter run in the primary domain, while the application services
associated with Metadata Manager run in the secondary domain. To upgrade Metadata Manager, you
upgrade the product components in the secondary domain. You can upgrade Metadata Manager without
having to upgrade PowerCenter at the same time.
To create each domain, you run the Informatica services installer separately. You can create each domain on
a separate machine or you can create both domains on one machine.
Split Domain Considerations

Before you decide to create a split domain, consider the advantages and potential issues.
The primary advantage of a split domain is that it supports frequent upgrades for Metadata Manager. You
can upgrade Metadata Manager without having to upgrade other components of your product bundle at the
same time. Therefore, you can take advantage of Metadata Manager new features and bug fixes without
affecting activities in the primary domain such as data integration operations. The primary domain remains
fully operational while you upgrade Metadata Manager.
However, you should also consider the following issues:
A split domain configuration is more complex than a single domain configuration.
In a split domain, you must create duplicate services, repositories, and users. If you install both domains
on the same machine, you must ensure that there are no port conflicts for the components in each
domain. When you run different Informatica versions in each domain, you must also consider possible
database version conflicts. For example, you create PowerCenter repositories for different Informatica

product versions in the same Oracle database. You must ensure that both Informatica product versions
support the Oracle database version.
There might be license implications.
If you use Informatica products for data integration, your license agreement usually limits data
integration activities to one domain. Your license agreement might limit the number of machines on
which you can create application services or the types of services that you can duplicate. You might also
need a separate license file for each domain.
For questions about licensing, contact your Informatica products representative.
You need additional database schemas and user accounts.
In a split domain, you must create duplicate repositories. For example, you create a domain
configuration repository in each domain. If you run PowerCenter and Metadata Manager in separate
domains, you also create a PowerCenter repository in each domain.
Each repository must be in a separate schema. You also need a separate database user account for
each domain configuration repository.
You need additional RAM and disk space.
When you install Informatica services, the amount of required RAM and disk space for two domains is
twice the required amount for one domain.
There are product version restrictions.
In a split domain, the components in the secondary domain can run the same version or a later version
of Informatica products than the components in the primary domain. Therefore, you can run a later
version of Metadata Manager than PowerCenter. However, you cannot run a later version of PowerCenter
than Metadata Manager.
You might need to run a different version of the PowerCenter Client in each domain.
For example, you run the PowerCenter Client in the primary domain to perform data integration
operations. In the secondary domain, you run a later version of Metadata Manager. To view session logs
from Metadata Manager resource loads, you must run a later version of the PowerCenter Client in the
secondary domain.
You cannot access Metadata Manager data lineage from the PowerCenter Designer.
In a split domain, the PowerCenter services in the primary domain do not communicate with the
Metadata Manager Service in the secondary domain. Therefore, you cannot access Metadata Manager
data lineage from the PowerCenter Designer.

Model Repository Service
The Model Repository Service manages the Model repository. It receives requests from Informatica clients
and application services to store or access metadata in the Model repository.
with the Model Repository Service.
Dependency Summary
Products The following products use the Model Repository Service:

- PowerCenter
Services The Model Repository Service does not require an association with another application service.
Databases The Model Repository Service uses the following database:

- Model repository. Stores metadata created by Informatica clients and application services.
Installer You can create the Model Repository Service when you run the installer.
Model Repository Database Requirements

Informatica services and clients store data and metadata in the Model repository. Configure a monitoring
Model repository to store statistics for ad hoc jobs, applications, logical data objects, SQL data services, web
services, and workflows. Before you create the Model Repository Service, set up a database and database
user account for the Model repository. It is recommended that you use different database configuration for
Model repository and monitoring Model repository.
The Model repository supports the following database types:
• IBM DB2 UDB

• Oracle
• PostgreSQL
Allow 3 GB of disk space for DB2. Allow 200 MB of disk space for all other database types.
When you configure Microsoft SQL Server, you can choose to configure the Microsoft Azure SQL Database as
the Model repository.

• Specify the tablespace name when you use IBM DB2 as the Model Repository database.
• If the repository is in an IBM DB2 database, verify that IBM DB2 Version 10.5 is installed.
Model Repository Service 71

• On the IBM DB2 instance where you create the database, set the following parameters to ON:
- DB2_SKIPINSERTED
- DB2_EVALUNCOMMITTED
- DB2_SKIPDELETED
- AUTO_RUNSTATS
The following table lists the configuration parameters that you must set:
Parameter Value
logfilsiz 8000
maxlocks 98
locklist 50000
auto_stmt_stats ON

In a single-partition database, specify a tablespace that meets the pageSize requirements. If you do not
specify a tablespace, the default tablespace must meet the pageSize requirements.
In a multi-partition database, specify a tablespace that meets the pageSize requirements. Define the
tablespace in the catalog partition of the database.
the tablespace.
• Verify that the database user has CREATETAB, CONNECT, and BINDADD privileges.
• In the DataDirect Connect for JDBC utility, update the DynamicSections parameter to 3000.
The default value for DynamicSections is too low for the Informatica repositories. Informatica requires a
larger DB2 package than the default. When you set up the DB2 database for the domain configuration
repository or a Model repository, you must set the DynamicSections parameter to at least 3000. If the
DynamicSections parameter is set to a lower number, you can encounter problems when you install or run

• Specify the database schema name when you use Microsoft SQL Server as the Model Repository
database.
• Set the allow snapshot isolation and read committed isolation level to ALLOW_SNAPSHOT_ISOLATION
and READ_COMMITTED_SNAPSHOT to minimize locking contention.
To set the isolation level for the database, run the following commands:
ALTER DATABASE DatabaseName SET ALLOW_SNAPSHOT_ISOLATION ON
ALTER DATABASE DatabaseName SET READ_COMMITTED_SNAPSHOT ON
To verify that the isolation level for the database is correct, run the following commands:

SELECT snapshot_isolation_state FROM sys.databases WHERE name=[DatabaseName]
SELECT is_read_committed_snapshot_on FROM sys.databases WHERE name = DatabaseName
• The database user account must have the CONNECT, CREATE TABLE, and CREATE VIEW privileges.

• Set the OPEN_CURSORS parameter to 4000 or higher.

Verify that the database user has the following privileges:
CREATE SEQUENCE
CREATE SESSION
CREATE SYNONYM
CREATE TABLE
CREATE VIEW

• Verify that the database user account has CONNECT, CREATE TABLE, and CREATE VIEW privileges.
• Specify the database schema name when you use PostgreSQL as the database.
must set:
Model Repository Service 73

Monitoring Model Repository Service
The monitoring Model Repository Service is a Model Repository Service that monitors statistics for Data
Integration Service jobs. You configure the monitoring Model Repository Service in the domain properties.
Note: If you want to generate monitoring statistics, you must create a dedicated Model Repository Service for
monitoring. You cannot store run-time monitoring statistics in the same repository where you store object
metadata.
with the monitoring Model Repository Service:
Dependency Summary
Products The following products use the monitoring Model Repository Service:
- PowerCenter
Services The monitoring Model Repository Service does not require an association with another application
service.
Databases The monitoring Model Repository Service uses the following database:
- Model repository. Stores run-time monitoring statistics that you can view in the Administrator tool.
Installer You can create the monitoring Model Repository Service when you run the installer.
PowerCenter Integration Service

The PowerCenter Integration Service receives requests from PowerCenter client tools to run data integration
jobs. It writes results to different databases, and it writes run-time metadata to the PowerCenter repository.
When you create the service, you need to associate another application service with it.
The following table lists the dependencies for products, services, and databases that are associated with the
PowerCenter Integration Service.
Dependency Summary
Products The following products use the PowerCenter Integration Service:

- PowerCenter
Services The Data Integration Service requires a direct association with the following service:
Databases The PowerCenter Integration Service does not have any associated database.
Installer You can create the PowerCenter Integration Service when you run the installer.

PowerCenter Repository Service
The PowerCenter Repository Service manages the PowerCenter repository. It receives requests from
Informatica clients and application services to store or access metadata in the Model repository.
with the PowerCenter Repository Service.
Dependency Summary
Products The following products use the PowerCenter Repository Service:

- PowerCenter
- Metadata Manager
Services The PowerCenter Repository Service does not require an association with another application service.
Databases The PowerCenter Repository Service uses the following database:

- PowerCenter repository. Stores metadata created by Informatica clients and application services.
Installer You can create the PowerCenter Repository Service when you run the installer.
PowerCenter Repository Database Requirements

A PowerCenter repository is a collection of database tables containing metadata. A PowerCenter Repository
Service manages the repository and performs all metadata transactions between the repository database and
repository clients.
The PowerCenter repository supports the following database types:
• IBM DB2 UDB

• Oracle
• PostgreSQL
• Sybase ASE
Note: To install the PowerCenter Repository Service with the 10.4.0 installer, you can use the Oracle,
Microsoft SQL Server, or the PostgreSQL database. If you want to install the PowerCenter Repository Service
on any of the other databases, you create the service with the required database after you run the installer.
Note: Ensure that you install the database client on the machine on which you want to run the PowerCenter
Repository Service.
PowerCenter Repository Service 75

• To optimize repository performance, set up the database with the tablespace on a single node. When the
tablespace is on one node, PowerCenter Client and PowerCenter Integration Service access the repository
faster than if the repository tables exist on different database nodes.
Specify the single-node tablespace name when you create, copy, or restore a repository. If you do not
specify the tablespace name, DB2 uses the default tablespace.

• Set the database server page size to 8K or higher. This is a one-time configuration and cannot be changed
afterwards.
• Verify that the database user account has the CONNECT, CREATE TABLE, and CREATE VIEW privileges.
Microsoft Azure SQL Database Requirements

afterwards.
• Verify that the database user account has the CONNECT, CREATE TABLE, and CREATE VIEW privileges.

• Set the storage size for the tablespace to a small number to prevent the repository from using an
excessive amount of space. Also verify that the default tablespace for the user that owns the repository
tables is set to a small size.
The following example shows how to set the recommended storage parameter for a tablespace named
REPOSITORY:
ALTER TABLESPACE "REPOSITORY" DEFAULT STORAGE ( INITIAL 10K NEXT 10K MAXEXTENTS
UNLIMITED PCTINCREASE 50 );
Verify or change the storage parameter for a tablespace before you create the repository.
CREATE SEQUENCE
CREATE SESSION
CREATE SYNONYM
CREATE TABLE
CREATE VIEW

• Verify that the database user account has CREATE TABLE and CREATE VIEW privileges.
must set:
• To install PostgreSQL database for the PowerCenter repository, set values for the PostgreSQL database
host, port, and service name for the pg_service.conf file in the following format:
[PCRS_DB_SERVICE_NAME]
host=Database host IP
port=Database port
dbname=PowerCenter Repository Service database service name
To securely connect to PostgreSQL for the PowerCenter repository, set the sslmode to require along with
the remaining required database properties in the pg_service.conf file in the following format:
sslmode=require
• Set the PGSERVICEFILE environment variable to the location of the pg_service.conf file in the
Informatica installation directory.
Sybase ASE Database Requirements

Use the following guidelines when you set up the repository on Sybase ASE:
afterwards.
• Set the Sybase database option "ddl in tran" to TRUE.
• Set "allow nulls by default" to TRUE.
• Verify the database user has CREATE TABLE and CREATE VIEW privileges.
• Set the database memory configuration requirements.
The following table lists the memory configuration requirements and the recommended baseline values:
Number of open objects sp_configure "number of open objects" 5000
Number of open indexes sp_configure "number of open indexes" 5000
PowerCenter Repository Service 77

Number of open partitions sp_configure "number of open partitions" 8000
Number of locks sp_configure "number of locks" 100000
Search Service
The Search Service manages searches in the Analyst tool and returns search results from the Model
repository. When you create the service, you need to associate another application service with it.
with the Search Service:
Dependency Summary
Products The following products use the Search Service:

- PowerCenter
Services The Search Service requires a direct association with the following service:
Databases The Search Service is not associated with any database.
Installer You cannot create the Search Service when you run the installer.
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 following services use native connectivity to connect to different databases:

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.
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.
The PowerCenter Repository Service uses native database drivers to connect to the PowerCenter
repository database.
Install database client software and configure connectivity on the machines where the PowerCenter
Repository Service and the PowerCenter Repository Service processes run.
The PowerCenter Integration Service uses native database drivers to connect to the following databases:
• Source and target databases. Reads from the source databases and writes to the target databases.
• Metadata Manager source databases. Loads the relational data sources in Metadata Manager.
Install database client software associated with the relational data sources and the repository databases
on the machines where the PowerCenter Integration Service runs.
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.
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
Microsoft SQL Server 2014 Native Client
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.
Configure Native Connectivity on Service Machines 79

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.
PostgreSQL client (psql)
Install and run the PostgreSQL interactive terminal program called psql, which allows you to interactively
enter, edit, and run SQL commands.
psql is a terminal-based front-end to PostgreSQL. You can type in queries interactively, issue the queries
to PostgreSQL, and check the query results. Or, the input can be from a file or from command line
arguments.
You can install psql client application for PostgreSQL to work only on Linux or Windows.
Install and run the required software dependency packages to build PostgreSQL, such as GCC compiler
package, readline and readline-devel packages, and zlib-devel compression library package. After you
install the packages from the GNU Readline library, psql remembers each command you type, and you
can use arrow keys to recall and edit previous commands.
You can also run the required library files with the yum install commands.
PostgreSQL on Windows
On Windows, download the psql client from the following link:
https://www.enterprisedb.com/downloads/postgres-postgresql-downloads
You must verify that PostgreSQL libraries are present in the following directories on Windows:
• Installation directory: C:\Program Files\PostgreSQL\10

• Command line tools installation directory: C:\Program Files\PostgreSQL\10
• pgAdmin4 installation directory: C:\Program Files\PostgreSQL\10\pgAdmin 4
PostgreSQL on Linux
On Linux, you also need to install the required postgreSQL libraries,

postgresql10-10.10-1PGDG.rhel7.x86_64 and postgresql10-libs-10.10-1PGDG.rhel7.x86_64
For more information about psql, see the psql client documentation in the following link:
https://www.postgresql.org/docs/10/app-psql.html
Configure Database Client Environment Variables

Configure database client environment variables on the machines that run the Data Integration Service,
PowerCenter Integration Service, and PowerCenter Repository Service processes.
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 Database Value

Variable 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
IBM DB2 DB2DIR db2connect Set to: <database path>

DB2INSTANCE Set to: <DB2InstanceName>
PATH Add: <database path>/bin
Sybase ASE SYBASE15 isql Set to: <database path>/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
PostgreSQL PGSERVICEFILE Set to the location of the pg_service.conf file:

PGHOME <pg_service.conf file directory>/pg_service.conf
PATH Set to: /usr/pgsql -10
LD_LIBRARY_PATH Add to: $PGHOME:${PATH}
INFA_TRUSTSTORE Add to: $PGHOME/lib:${LD_LIBRARY_PATH}
For default SSL domain, add to: <InstallationDirectory>/
services/shared/security
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
Configure Native Connectivity on Service Machines 81

Chapter 5
Prepare for Kerberos

Authentication
• Checklist to Prepare for Kerberos Authentication , 82

• Prepare for Kerberos Authentication Overview, 82
• Set Up the Kerberos Configuration File, 83
• Generate the Service Principal and Keytab File Name Format, 84
• Review the SPN and Keytab Format Text File, 87
• Create the Service Principal Names and Keytab Files, 89
Checklist to Prepare for Kerberos Authentication

This chapter contains tasks to perform if you want the installer to enable Kerberos during installation. Use
this checklist to track tasks required to prepare for Kerberos authentication.
 Set up the Kerberos configuration file.
 Generate the service principal and keytab name file format.
 Review the SPN and keytab format text file.
 Create the SPN and keytab files.
Prepare for Kerberos Authentication Overview

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

Kerberos stores configuration information in a file named krb5.conf. Informatica requires specific properties
set in the Kerberos configuration file so that the Informatica domain can use Kerberos authentication
correctly. You must set the properties in the krb5.conf configuration file.
The configuration file contains the information about the Kerberos server, including the Kerberos realm and
the address of the KDC. You can request the Kerberos administrator to set the properties in the configuration
file and send you a copy of the file.
1. Back up the krb5.conf file before you make any changes.

2. Edit the krb5.conf file.
3. In the libdefaults section, set or add the properties required by Informatica.

The following table lists the values to which you must set properties In the libdefaults section:
Parameter Value
default_realm Name of the service realm for the Informatica domain.
forwardable Allows a service to delegate client user credentials to another service. Set this parameter
to True. The Informatica domain requires application services to authenticate the client
user credentials with other services.
default_tkt_enctypes Encryption types for the session key in ticket-granting tickets (TGT). Set this parameter
only if session keys must use specific encryption types.
udp_preference_limit Determines the protocol that Kerberos uses when it sends a message to the KDC. Set
udp_preference_limit = 1 to always use TCP. The Informatica domain supports only the
TCP protocol. If the udp_preference_limit is set to any other value, the Informatica
domain can shut down unexpectedly.
4. In the realms section, include the port number in the address of the KDC separated by a colon.
For example, if the KDC address is kerberos.example.com and the port number is 88, set the kdc
parameter to the following:
kdc = kerberos.example.com:88
5. Save the krb5.conf file.
6. Store the krb5.conf file in a directory that is accessible to the machine where you plan to install the
Set Up the Kerberos Configuration File 83

The following example shows the content of a krb5.conf with the required properties:
[libdefaults]
default_realm = AFNIKRB.AFNIDEV.COM
forwardable = true
udp_preference_limit = 1
[realms]
AFNIKRB.AFNIDEV.COM = {
admin_server = SMPLKERDC01.AFNIKRB.AFNIDEV.COM
kdc = SMPLKERDC01.AFNIKRB.AFNIDEV.COM:88
}
[domain_realm]
afnikrb.afnidev.com = AFNIKRB.AFNIDEV.COM
.afnikrb.afnidev.com = AFNIKRB.AFNIDEV.COM
For more information about the Kerberos configuration file, see the Kerberos network authentication
documentation.
Generate the Service Principal and Keytab File Name

Format
If you run the Informatica domain with Kerberos authentication, you must associate Kerberos service
principal names (SPN) and keytab files with the nodes and processes in the Informatica domain. Informatica
requires keytab files to authenticate services without requests for passwords.
Based on the security requirements for the domain, you can set the service principal level to one of the
following levels:
Node Level
If the domain is used for testing or development and does not require a high level of security, you can set
the service principal at the node level. You can use one SPN and keytab file for the node and all the
service processes on the node. You must also set up a separate SPN and keytab file for the HTTP
processes on node.
Process Level
If the domain is used for production and requires a high level of security, you can set the service
principal at the process level. Create a unique SPN and keytab file for each node and each process on
the node. You must also set up a separate SPN and keytab file for the HTTP processes on node.
The Informatica domain requires the service principal and keytab file names to follow a specific format. To
ensure that you follow the correct format for the service principal and keytab file names, use the Informatica
Kerberos SPN Format Generator to generate a list of the service principal and keytab file names in the format
required by the Informatica domain.
The Informatica Kerberos SPN Format Generator is shipped with the Informatica services installer.
Service Principal Requirements at Node Level

If the Informatica domain does not require a high level of security, the node and service processes can share
the same SPNs and keytab files. The domain does not require a separate SPN for each service process in a
node.
The Informatica domain requires SPNs and keytab files for the following components at node level:
84 Chapter 5: Prepare for Kerberos Authentication

Principal distinguished name (DN) for the LDAP directory service
Principal name for the bind user DN that is used to search the LDAP directory service. The name of the
keytab file must be infa_ldapuser.keytab.
Node process
Principal name for the Informatica node that initiates or accepts authentication calls. The same principal
name is used to authenticate the services in the node. Each gateway node in the domain requires a
separate principal name.
HTTP processes in the domain

Principal name for all web application services in the Informatica domain, including Informatica
Administrator. The browser uses this principal name to authenticate with all HTTP processes in the
domain. The name of the keytab file must be webapp_http.keytab.
Service Principal Requirements at Process Level

If the Informatica domain requires a high level of security, create a separate SPN and keytab file for each
node and each service in the node.
The Informatica domain requires SPNs and keytab files for the following components at process level:
Principal distinguished name (DN) for the LDAP directory service
Principal name for the bind user DN that is used to search the LDAP directory service. The name of the
keytab file must be infa_ldapuser.keytab.
Node process
Principal name for the Informatica node that initiates or accepts authentication calls.
Informatica Administrator service
Principal name for the Informatica Administrator service that authenticates the service with other
services in the Informatica domain. The name of the keytab file must be_AdminConsole.keytab.
HTTP processes in the domain
Principal name for all web application services in the Informatica domain, including Informatica
Administrator. The browser uses this principal name to authenticate with all HTTP processes in the
domain. The name of the keytab file must be webapp_http.keytab.
Service process
Principal name for the service that runs on a node in the Informatica domain. Each service requires a
unique service principal and keytab file name.
You do not need to create the SPNs and keytab files for the services before you run the installer. You can
create the SPN and keytab file for a service when you create the service in the domain. The SPN and
keytab file for a service must be available when you enable the service.
Running the SPN Format Generator

You can run the Informatica Kerberos SPN Format Generator to generate a file that shows the correct format
for the SPNs and keytab file names required in the Informatica domain.
You can run the SPN Format Generator from the command line or from the Informatica installer. The SPN
Format Generator generates a file with the names of the service principal and keytab files based on the
parameters you provide.
Generate the Service Principal and Keytab File Name Format 85

Note: Verify that the information you provide is correct. The SPN Format Generator does not validate the
values you enter.
1. On the machine where you extracted the installation files, go to the following directory: <Informatica
installation files directory>/Server/Kerberos
2. On a shell command line, run the SPNFormatGenerator file.
3. Press Enter to continue.
4. In the Service Principal Level section, select the level at which to set the Kerberos service principals for
the domain.
The following table describes the levels you can select:
Level Description
Process Level Configures the domain to use a unique service principal name (SPN) and keytab
file for each node and each application service on a node.
The number of SPNs and keytab files required for each node depends on the
number of application service processes that run on the node. Use the process
level option for domains that require a high level of security, such as productions
domains.
Node Level Configures the domain to share SPNs and keytab files on a node.
This option requires one SPN and keytab file for the node and all application
services that run on the node. It also requires a separate SPN and keytab file for
all HTTP processes on the node.
Use the node level option for domains that do not require a high level of security,
such as test and development domains.
5. Enter the domain and node parameters required to generate the SPN format.
The following table describes the parameters you must specify:
Prompt Description
Domain Name Name of the domain. 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 Informatica node.
Node host name Fully qualified host name or the IP address of the machine on which to create the
node. The node host name cannot contain the underscore (_) character.
Note: Do not use localhost. The host name must explicitly identify the machine.
Service Realm Name Name of the Kerberos realm for the Informatica domain services. The realm name
must be in uppercase.
If you set the service principal at node level, the prompt Add Node? appears. If you set the service
principal at process level, the prompt Add Service? appears.
6. At the Add Node? prompt, enter 1 to generate the SPN format for an additional node. Then enter the
node name and node host name.
To generate the SPN formats for multiple nodes, enter 1 at each Add Node? prompt and enter a node
name and node host name.

7. At the Add Service? prompt, enter 1 to generate the SPN format for a service that will run on the
preceding node. Then enter the service name.
To generate the SPN formats for multiple services, enter 1 at each Add Service? prompt and enter a
service name.
8. Enter 2 to end the Add Service? or Add Node? prompts.
The SPN Format Generator displays the path and file name of the file that contains the list of service
principal and keytab file names.
9. Press Enter to exit the SPN Format Generator.
The SPN Format Generator generates a text file that contains the SPN and keytab file names in the format
required for the Informatica domain.
Review the SPN and Keytab Format Text File

The Kerberos SPN Format Generator generates a text file named SPNKeytabFormat.txt that lists the format
for the service principal and keytab file names required by the Informatica domain. The list includes the SPN
and keytab file names based on the service principal level you select.
Review the text file and verify that there are no error messages.
The text file contains the following information:

Entity Name
Identifies the node or service associated with the process.
SPN
Format for the SPN in the Kerberos principal database. The SPN is case sensitive. Each type of SPN has
a different format.
An SPN can have one of the following formats:
Keytab type SPN Format
NODE_SPN isp/<NodeName>/<DomainName>@<REALMNAME>
NODE_AC_SPN _AdminConsole/<NodeName>/<DomainName>@<REALMNAME>
NODE_HTTP_SPN HTTP/<NodeHostName>@<REALMNAME>
Note: The Kerberos SPN Format Generator validates the node host
name. If the node host name is not valid, the utility does not generate an
SPN. Instead, it displays the following message: Unable to resolve host
name.
SERVICE_PROCESS_SPN <ServiceName>/<NodeName>/<DomainName>@<REALMNAME>
Keytab File Name
Format for the name of the keytab file to be created for the associated SPN in the Kerberos principal
database. The keytab file name is case sensitive.
Review the SPN and Keytab Format Text File 87

The keytab file names use the following formats:
Keytab type Keytab File Name
NODE_SPN <NodeName>.keytab
NODE_AC_SPN _AdminConsole.keytab
NODE_HTTP_SPN webapp_http.keytab
SERVICE_PROCESS_SPN <ServiceName>.keytab
Keytab Type
Type of the keytab. The keytab type can be one of the following types:
• NODE_SPN. Keytab file for a node process.

• NODE_AC_SPN. Keytab file for the Informatica Administrator service process.
• NODE_HTTP_SPN. Keytab file for HTTP processes in a node.
• SERVICE_PROCESS_SPN. Keytab file for a service process.
Service Principals at Node Level

The following example shows the contents of the SPNKeytabFormat.txt file generated for service principals
at the node level:
ENTITY_NAME SPN KEY_TAB_NAME
KEY_TAB_TYPE
Node01 isp/Node01/[email protected] Node01.keytab
NODE_SPN
Node01 HTTP/[email protected] webapp_http.keytab
NODE_HTTP_SPN
NODE_SPN
NODE_HTTP_SPN
NODE_SPN
NODE_HTTP_SPN
Service Principals at Process Level

The following example shows the contents of the SPNKeytabFormat.txt file generated for service principals
at the process level:
ENTITY_NAME SPN
KEY_TAB_NAME KEY_TAB_TYPE
Node01 isp/Node01/[email protected]
Node01.keytab NODE_SPN
Node01 _AdminConsole/Node01/[email protected]
_AdminConsole.keytab NODE_AC_SPN
Node01 HTTP/[email protected]
webapp_http.keytab NODE_HTTP_SPN
Node02 isp/Node02/[email protected]
Node02.keytab NODE_SPN
Node02 _AdminConsole/Node02/[email protected]
_AdminConsole.keytab NODE_AC_SPN
Node02 HTTP/[email protected]
webapp_http.keytab NODE_HTTP_SPN
Service10:Node01 Service10/Node01/[email protected]
Service10.keytab SERVICE_PROCESS_SPN

Create the Service Principal Names and Keytab Files

After you generate the list of SPN and keytab file names in Informatica format, send a request to the
Kerberos administrator to add the SPNs to the Kerberos principal database and create the keytab files.
Use the following guidelines when you create the SPN and keytab files:
The user principal name (UPN) must be the same as the SPN.
When you create a user account for the service principal, you must set the UPN with the same name as
the SPN. The application services in the Informatica domain can act as a service or a client depending
on the operation. You must configure the service principal to be identifiable by the same UPN and SPN.
A user account must be associated with only one SPN. Do not set multiple SPNs for one user account.
Enable delegation in Microsoft Active Directory.
You must enable delegation for all user accounts with service principals used in the Informatica domain.
In the Microsoft Active Directory Service, set the Trust this user for delegation to any service (Kerberos
only) option for each user account that you set an SPN.
Delegated authentication happens when a user is authenticated with one service and that service uses
the credentials of the authenticated user to connect to another service. Because services in the
Informatica domain need to connect to other services to complete an operation, the Informatica domain
requires the delegation option to be enabled in Microsoft Active Directory.
Use the ktpass utility to create the service principal keytab files.
Microsoft Active Directory supplies the ktpass utility to create keytab files. Informatica supports
Kerberos authentication only on Microsoft Active Directory and has certified only keytab files that are
created with ktpass.
The keytab files for a node must be available on the machine that hosts the node. By default, the keytab files
are stored in the following directory: <Informatica installation directory>/isp/config/keys. During
installation, you can specify a directory on the node to store the keytab files.
When you receive the keytab files from the Kerberos administrator, copy the keytab files to a directory that is
accessible to the machine where you plan to install the Informatica services. When you run the Informatica
installer, specify the location of the keytab files. The Informatica installer copies the keytab files to the
directory for keytab files on the Informatica node.
Troubleshooting the Service Principal Names and Keytab Files

You can use Kerberos utilities to verify that the service principal and keytab file names created by the
Kerberos administrator match the service principal and keytab file names that you requested. You can also
use the utilities to determine the status of the Kerberos key distribution center (KDC).
You can use Kerberos utilities such as setspn, kinit and klist to view and verify the SPNs and keytab files. To
use the utilities, ensure that the KRB5_CONFIG environment variable contains the path and file name of the
Kerberos configuration file.
Note: The following examples show ways to use the Kerberos utilities to verify that SPNs and keytab files are
valid. The examples might be different than the way that the Kerberos administrator uses the utilities to
Create the Service Principal Names and Keytab Files 89

create the SPNs and keytab files required for the Informatica domain. For more information about running the
Kerberos utilities, see the Kerberos documentation.
Use the following utilities to verify the SPNs and keytab files:
klist
You can use klist to list the Kerberos principals and keys in a keytab file. To list the keys in the keytab file
and the time stamp for the keytab entry, run the following command:
klist -k -t <keytab_file>
The following output example shows the principals in a keytab file:
Keytab name: FILE:int_srvc01.keytab
KVNO Timestamp Principal
---- ----------------- --------------------------------------------------------
3 12/31/69 19:00:00 int_srvc01/node01_vMPE/Domn96_vMPE@REALM
kinit
You can use kinit to request a ticket-granting ticket for a user account to verify that the KDC is running
and can grant tickets. To request a ticket-granting ticket for a user account, run the following command:
kinit <user_account>
You can also use kinit to request a ticket-granting ticket and verify that the keytab file can be used to
establish a Kerberos connection. To request a ticket-granting ticket for an SPN, run the following
command:
kinit -V -k -t <keytab_file> <SPN>
The following output example shows the ticket-granting ticket created in the default cache for a
specified keytab file and SPN:
Using default cache: /tmp/krb5cc_10000073
Using principal: int_srvc01/node01_vMPE/Domn96_vMPE@REALM
Using keytab: int_srvc01.keytab
Authenticated to Kerberos v5
setspn
You can use setspn to view, modify, or delete the SPN of an Active Directory service account. On the
machine that hosts the Active Directory service, open a command line window and run the command.
To view the SPNs that are associated with a user account, run the following command:
setspn -L <user_account>
The following output example shows the SPN associated with the user account is96svc:
Registered ServicePrincipalNames for CN=is96svc,OU=AllSvcAccts,OU=People,
DC=ds,DC=intrac0rp,DC=zec0rp:
int_srvc01/node02_vMPE/Domn96_vMPE
To view the user accounts associated with an SPN, run the following command:
setspn -Q <SPN>
The following output example shows the user account associated with the SPN int_srvc01/
node02_vMPE/Domn96_vMPE:
Checking domain DC=ds,DC=intrac0rp,DC=zec0rp
CN=is96svc,OU=AllSvcAccts,OU=People,DC=ds,DC=intrac0rp,DC=zec0rp
int_srvc01/node02_vMPE/Domn96_vMPE
Existing SPN found!

To search for duplicate SPNs, run the following command:
setspn -X
The following output example shows multiple user accounts associated with one SPN:
Checking domain DC=ds,DC=intrac0rp,DC=zec0rp
Processing entry 1125
HOST/mtb01.REALM is registered on these accounts:
CN=Team1svc,OU=AllSvcAccts,OU=People,DC=ds,DC=intrac0rp,DC=zec0rp
CN=MTB1svc,OU=IIS,OU=WPC960K3,OU=WINServers,DC=ds,DC=intrac0rp,DC=zec0rp
Note: Searching for duplicate SPNs can take a long time and a large amount of memory.
kdestroy
You can use kdestroy to delete the active Kerberos authorization tickets and the user credentials cache
that contains them. If you run kdestroy without parameters, you delete the default credentials cache.
Create the Service Principal Names and Keytab Files 91

Chapter 6
Record Information for Installer

Prompts
• Checklist to Record Installer Prompts, 92

• Record Information for Installer Prompts Overview, 93
• Domain, 93
• Nodes, 94
• Application Services, 94
• Databases , 95
• Connection String to a Secure Database, 97
• Secure Data Storage, 98
• Kerberos, 99
Checklist to Record Installer Prompts

This chapter contains information that you need to enter when you run the installer. Use this checklist to
track the recording tasks before you run the installer.
 Record the names of nodes that you want to create and the services that you want to create on each
node.
 Record basic database information for each database associated with a service that you are creating.
 If the domain configuration and Model repository databases are secure, record the JDBC connection
string with required security parameters.
 Record the keyword for the installer to generate an encryption key for the domain.
 If you want to enable Kerberos authentication when you run the installer, record Kerberos information for
each node in the domain.
 If you install Enterprise Data Catalog, record cluster information.
92
Record Information for Installer Prompts Overview
When you install the Informatica services, you need to know information about the domain, nodes,
application services, and databases that you plan to create.
This section lists information that you need to provide when you run the installer. Informatica recommends
recording installer prompts before you start the installation process. For example, you might want to create a
text file of information so you can copy into the installer.
Domain Object Naming Conventions

You cannot change domain, node, and application service names. Use names that continue to work if you
migrate a node to another machine or if you add additional nodes and services to the domain. In addition, use
names that convey how the domain object is used. Naming conventions are provided in applicable topics.
For more information about domain object naming conventions, see the following Informatica Velocity Best
Practice article available on the Informatica Network:
http://velocity.informatica.com/index.php/best-practices-all/139-configuration-management-and-security/
708-infa-nam-conv.
Domain
When you create a domain, you must provide a domain name and gateway node name.
The following table describes the domain information that you need to enter during the installation process:
Domain Information Description
Domain name Name of the domain that you plan to create. 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: ` % * + ; " ? , < > \ /
Consider one of the following naming conventions: DMN, DOM, DOMAIN,
_<ORG>_<ENV>
Master gateway node host name Fully qualified host name of the machine on which to create the master
gateway node. If the machine has a single network name, use the default
host name. The node host name cannot contain the underscore (_)
character.
If the machine has multiple network names, you can modify the default host
name to use an alternate network name. If the machine has a single network
name, use the default host name.
Note: Do not use localhost. The host name must explicitly identify the
machine.
Master gateway node name Name of the master gateway node that you plan to create on this machine.
The node name is not the host name for the machine.
Consider the following naming convention: Node<node##>_<ORG>_<optional
distinguisher>_<ENV>
Record Information for Installer Prompts Overview 93

Nodes
When you install the Informatica services, you add the installation machine to the domain as a node. You can
add multiple nodes to a domain.
The following table describes the node information that you need to enter when you join a domain.
Node Information Description
Node host name Fully qualified host name of the machine on which to create nodes. If the machine
has a single network name, use the default host name. The node host name cannot
contain the underscore (_) character.
If the machine has multiple network names, you can modify the default host name
to use an alternate network name. If the machine has a single network name, use
the default host name.
Node name Name of the nodes that you plan to create on this machine. The node name is not
the host name for the machine.
Consider the following naming convention: Node<node##>_<ORG>_<optional
distinguisher>_<ENV>
Application Services
Record the application service names and the nodes where you want to create them.
The following table lists the application services that you can create when you run the installer:
Application Service Naming Convention
Catalog Service CS_<ORG>_<ENV>
Content Management CMS_<ORG>_<ENV>
Data Integration Service DIS_<ORG>_<ENV>
Interactive Data Preparation Service DPS_<ORG>_<ENV>
Enterprise Data Preparation Service EDLS_<ORG>_<ENV>
Informatica Cluster Service ICS_<ORG>_<ENV>
Model Repository Service MRS_<ORG>_<ENV>
monitoring Model Repository Service mMRS_<ORG>_<ENV>
PowerCenter Repository Service PCRS, RS _<ORG>_<ENV>
PowerCenter Integration Service PCIS, IS _<ORG >_<ENV>
For more information about all service naming conventions, see the following Informatica Velocity Best
Practice article available on the Informatica Network:
94 Chapter 6: Record Information for Installer Prompts

http://velocity.informatica.com/index.php/best-practices-all/139-configuration-management-and-security/
708-infa-nam-conv.
Important: If you plan to use Kerberos authentication, you must know the application service and node name
before you create the keytab files.
Databases
When you plan the installation, you also need to plan the required relational databases. The domain requires
a database to store configuration information and user account privileges and permissions. Some application
services require databases to store information processed by the application service.
Domain
The following table describes the information that you need to enter during the installation process:
Database Information Description
Domain configuration database type Database type for the domain configuration repository. The domain
configuration repository supports IBM DB2 UDB, Microsoft SQL Server,
Oracle, PostgreSQL, or Sybase ASE.
Domain configuration database host The name of the machine hosting the database.
name
Content Management Service

Reference data warehouse database Database type for the reference data warehouse. The reference data
type warehouse supports IBM DB2 UDB, Microsoft SQL Server, or Oracle.
Reference data warehouse database The name of the machine hosting the database.
host name

Data object cache database type Database type for the data object cache database. The data object cache
database supports IBM DB2 UDB, Microsoft SQL Server, or Oracle.
Data object cache database host The name of the machine hosting the database.
name
Profiling warehouse database type Database type for the profiling warehouse. The profiling warehouse supports
IBM DB2 UDB, Microsoft SQL Server, or Oracle.
Databases 95
Profiling warehouse database host The name of the machine hosting the database.
name
Workflow database type Database type for the workflow database. The workflow database supports
IBM DB2 UDB, Microsoft SQL Server, or Oracle.
Workflow database host name The name of the machine hosting the database.
Data Preparation Service

Data Preparation repository database Database type for the Data Preparation repository. The Data Preparation
type repository supports MySQL, MariaDB, or Oracle.
Data Preparation repository database The name of the machine hosting the database.
host name

Model repository database type Database type for the Model repository. The Model repository supports IBM
DB2 UDB, Microsoft SQL Server, PostgreSQL, or Oracle.
Model repository database host name The name of the machine hosting the database.

PowerCenter repository database type Database type for the PowerCenter repository. The PowerCenter repository
supports IBM DB2 UDB, Microsoft SQL Server, Oracle, PostgreSQL, or Sybase
ASE.
PowerCenter repository database host The name of the machine hosting the database.
name

Connection String to a Secure Database
If you create a repository on a secure database, you must provide the truststore information for the database
and a JDBC connection string that includes the security parameters for the database.
During installation, you can create the domain configuration repository in a secure database. You can also
create the Model repository and PowerCenter repository in a secure database.
You can configure a secure connection to the following databases:
• IBM DB2 UDB

• PostgreSQL
• Oracle
Note: You cannot configure a secure connection to a Sybase database.
When you configure the connection to the secure database, you must specify the connection information in a
JDBC connection string. In addition to the host name and port number for the database server, the
connection string must include security parameters.
The following table describes the security parameters that you must include in the JDBC connection string:
Parameter Description
EncryptionMethod Required. Indicates whether data is encrypted when transmitted over the network.
This parameter must be set to SSL.
ValidateServerCertificate Optional. Indicates whether Informatica validates the certificate that is sent by the
database server.
If this parameter is set to True, Informatica validates the certificate that is sent by
the database server. If you specify the HostNameInCertificate parameter, Informatica
also validates the host name in the certificate.
If this parameter is set to false, Informatica does not validate the certificate that is
sent by the database server. Informatica ignores any truststore information that you
specify.
HostNameInCertificate Optional. Host name of the machine that hosts the secure database. If you specify a
host name, Informatica validates the host name included in the connection string
against the host name in the SSL certificate.
If SSL encryption and validation is enabled and this property is not specified, the
driver uses the server name specified in the connection URL or data source of the
connection to validate the certificate.
cryptoProtocolVersion Required. Specifies the cryptographic protocol to use to connect to a secure

database. You can set the parameter to cryptoProtocolVersion=TLSv1.1 or
cryptoProtocolVersion=TLSv1.2 based on the cryptographic protocol used by
the database server.
You can use the following syntax in the JDBC connection string to connect to a secure database:
IBM DB2
jdbc:Informatica:db2://<host name>:<port number>;DatabaseName=<database
name>;EncryptionMethod=SSL;HostNameInCertificate=<database host
name>;ValidateServerCertificate=<true or false>
Connection String to a Secure Database 97

Oracle
jdbc:Informatica:oracle://<host name>:<port number>;ServiceName=<service

PostgreSQL
jdbc:Informatica:postgresql://<host name>:<port number>;DatabaseName=<database

name>;SnapshotSerializable=true;EncryptionMethod=SSL;HostNameInCertificate=*.database.win
dows.net;ValidateServerCertificate=false
Note: The installer does not validate the connection string. Verify that the connection string contains all the
connection parameters and security parameters required by your database.
Secure Data Storage

When you install the Informatica services, you must provide a keyword for the installer to use to generate the
encryption key for the domain.
Use the following table to record the information that you need to configure secure data storage:
Keyword Keyword to use to create a custom encryption key to secure sensitive data in the
domain. The keyword must meet the following criteria:
- From 8 to 20 characters long
- Includes at least one uppercase letter
- Includes at least one lowercase letter
- Includes at least one number
- Does not contain spaces
The encryption key is created based on the keyword that you provide when you create
the Informatica domain.
Encryption key directory Directory in which to store the encryption key for the domain. By default, the
encryption key is created in the following directory: <Informatica installation
directory>/isp/config/keys.

Kerberos
When you install the Informatica application services, you can enable options in the Informatica domain to
configure security for the domain, services and databases.
If you want to enable Kerberos authentication and you do not want to use the default file, you need to provide
information such as keystore and truststore directories. Each node needs to contain a keystore and
truststore that is used by all services on that node.
The following table describes security information to provide during installation:
Security Information Description
Service realm name Name of the Kerberos realm to which the Informatica domain services belong.
The realm name must be in uppercase.
The service realm name and the user realm name must be the same.
User realm name Name of the Kerberos realm to which the Informatica domain users belong.
Location of the Kerberos Directory where the Kerberos configuration file named krb5.conf is stored.
configuration file Informatica requires specific properties to be set in the configuration file. If
you do not have permission to copy or update the Kerberos configuration file,
you might have to request the Kerberos administrator to update the file.
Keystore file directory Directory that contains the keystore files. The directory must contain files
named infa_keystore.jks and infa_keystore.pem.
Keystore password A plain-text password for the keystore infa_keystore.jks.
Truststore file directory Directory that contains the truststore files. The directory must contain files
named infa_truststore.jks and infa_truststore.pem.
Truststore password Password for the infa_truststore.jks file.
Kerberos 99
Chapter 7
Introduction to the Services

Installer
• Services Installer Tasks, 100

• Pre-install Utilities, 100
• Secure Files and Directories, 101
Services Installer Tasks

The installer performs install tasks based on the product or products that you install.
The installer can perform the following tasks:
1. Perform pre-install validation and system check.

2. Create a domain or join a node to an existing domain.
3. Install binaries for service support.
4. Create application services.
5. Configure security between the domain and services.
6. Start the domain and application services that you created.
7. Write message to the log file.
Pre-install Utilities
Informatica provides utilities to facilitate the Informatica services installation process. You can use the
Informatica installer to run the utilities.
Run the following utilities before you install Informatica services:
Pre-Installation (i10Pi) System Check Tool
The Pre-Installation (i10Pi) System Check Tool verifies whether a machine meets the system
requirements for the Informatica installation. Informatica recommends that you verify the minimum
system requirements before you start the installation. When you run the system check tool before you
100
perform the installation, the installer sets fields for certain fields, such as the database connection and
domain port numbers, based on the information that you enter during the system check.
Informatica Kerberos SPN Format Generator
The Informatica Kerberos SPN Format Generator generates a list of Kerberos service principal names
(SPN) and keytab file names in the format required by Informatica. If you install Informatica on a
network that uses Kerberos authentication, run this utility to generate the service principal and keytab
file names in the informatica format. Then request the Kerberos administrator to add the SPNs to the
Kerberos principal database and create the keytab files before you start the installation.
Secure Files and Directories

When you install or upgrade Informatica, the installer creates directories to store Informatica files that
require restricted access, such as the domain encryption key file and the nodemeta.xml. The installer assigns
different permissions for the directories and the files in the directories.
By default, the installer creates the following directories within the Informatica installation directory:
<Informatica installation directory>/isp/config
Contains the nodemeta.xml file. Also contains the /keys directory where the encryption key file is stored.
If you configure the domain to use Kerberos authentication, the /keys directory also contains the
Kerberos keytab files. You can specify a different directory in which to store the files. The installer
assigns the same permissions to the specified directory as the default directory.
<Informatica installation directory>/services/shared/security
If you enable secure communication for the domain, the /security directory contains the keystore and
truststore files for the default SSL certificates.
To maintain the security of the directories and files, the installer restricts access to the directories and the
files in the directories. The installer assigns specific permissions to the group and user account that own the
directories and files.
For more information about permissions assigned to the directories and files, see the Informatica Security
Guide.
Secure Files and Directories 101

Part III: Run the Services Installer
• Install Informatica Services in Console Mode, 103

• Install Informatica Services in Graphical Mode, 135
• Run the Silent Installer, 179
• Troubleshooting , 182
102
Chapter 8
Install Informatica Services in

Console Mode
• Informatica Services Installation Overview, 103

• Create a Domain, 103
• Join a domain, 128
Informatica Services Installation Overview

You can install the Informatica services on multiple machines. The installation process creates a service
named Informatica that runs as a daemon.
The first time you run the installer, you create a domain. If you are installing on multiple machines and you
have created a domain, you join the domain.
When you create a domain, the node on the machine where you install becomes a gateway node in the
domain. You can choose to set up secure communication between services within the domain. You can also
choose to create some application services during the installation process.
When you join a domain, you can configure the node that you create to be a gateway node. When you create a
gateway node, you can select enable a secure HTTPS connection to Informatica Administrator.
Follow the installation instructions in this chapter when you install Informatica domain services for traditional
products, such as PowerCenter and Informatica Data Quality.
Note: When you run the installer in console mode, the words Quit and Back are reserved words. Do not use
them as input text.
Create a Domain
Create a domain if you are installing for the first time or if you want to administer nodes in separate domains.
103
Run the Installer
Perform the following steps to run the installer:

3. On a shell command line, run the install.sh file from the root directory.
Welcome to the Informatica Installer

u Press 1 to run the installer.
The installer displays different options based on the platform you are installing on.
The following options appear:
a. Press 1 to run the Pre-Installation System Check Tool.
For more information about running the Pre-Installation (i10Pi) System Check Tool, see “Run the
Pre-Installation (i10Pi) System Check Tool in Console Mode” on page 32.
b. Press 2 to run the Informatica Kerberos SPN Format Generator.
For more information about running the Informatica Kerberos SPN Format Generator, see “Running
the SPN Format Generator ” on page 85.
c. Press 3 to run the installer.
The Welcome section appears.
Welcome - Accept Terms and Conditions

u Read the terms and conditions for Informatica installation and the product usage toolkit and select I
agree to the terms and conditions.
a. Press 1 if you do not want to accept the terms and conditions.
b. Press 2 to accept the terms and conditions.
The Component Selection sections appears.
Component Selection
After you accept terms and conditions, you can install Informatica domain services.
1. Press 1 to install Informatica domain services.

This option installs version 10.4.0 domain services and the application service binaries.
2. Choose whether you want to run the installer on a network that uses Kerberos authentication.
a. Press 1 to configure the Informatica domain to run on a network that does not use Kerberos
authentication.
b. Press 2 to configure the Informatica domain to run on a network with Kerberos authentication.
The Installation Prerequisites section displays the installation requirements. Verify that all requirements are
met before you continue the installation.
104 Chapter 8: Install Informatica Services in Console Mode

License and Installation Directory
After you verify the installation prerequisites, you can specify the installation directory.
1. Enter the path and file name of the Informatica license key and press Enter.
( ) { } [ ] , ; ' Default is /home/toolinst.
If you enabled Kerberos network authentication, the Service Principal Level section appears.
If you did not enable Kerberos network authentication, the Pre-Installation Summary section appears. Review
the installation information and press Enter to continue. Skip to “Domain Selection” on page 106.
Network Security - Service Principal Level

After you specify the installation directory, you can configure security level.
u In the Service Principal Level section, select the level at which to set the Kerberos service principals for
the domain.
Note: All nodes in the domain must use the same service principal level. When you join a node to a
domain, select the same service principal level used by the gateway node in the domain.
The following table describes the levels that you can select:
Level Description
domains.
The Network Security - Kerberos Authentication section appears.
Network Security - Kerberos Authentication

After you configure the security level, you can configure Keberos authentication.
u In the Network Security - Kerberos Authentication section, enter the parameters required for Kerberos
authentication.
Create a Domain 105

The following table describes the Kerberos authentication parameters that you must set:
Domain name Name of the domain. The name must not exceed 128 characters and must be 7-
bit ASCII only. The name cannot contain a space or any of the following
characters: ` % * + ; " ? , < > \ /
Node name Name of the Informatica node.
Node host name Fully qualified host name or the IP address of the machine on which to create the
node. The node host name cannot contain the underscore (_) character.
Service realm name Name of the Kerberos realm to which the Informatica domain services belong.
User realm name Name of the Kerberos realm to which the Informatica domain users belong. The
realm name must be in uppercase.
Keytab directory Directory where all keytab files for the Informatica domain are stored. The name
of a keytab file in the Informatica domain must follow a format set by
Informatica.
Fully qualified path to the Path and file name of the Kerberos configuration file. Informatica requires the
kerberos configuration file following name for the Kerberos configuration file: krb5.conf
Important: If you configure the domain to run with Kerberos authentication, the domain and node name
and the node host name must match the names you specified when you ran the Informatica Kerberos
SPN Format Generator to generate SPN and keytab file names. If you use a different domain, node, or
host name, generate the SPN and keytab file names again and ask the Kerberos administrator to add the
new SPN to the Kerberos principal database and create the keytab files.
The Pre-Installation Summary section appears. Review the installation information.
Domain Selection
After you review the Pre-Installation summary, you can enter the domain information.
1. Press 1 to create a domain.

When you create a domain, the node that you create becomes a gateway node in the domain. The
gateway node contains a Service Manager that manages all domain operations.
2. Select whether you want to enable secure communication for services in the domain.
a. Press 1 to disable secure communication for the domain.
b. Press 2 to enable secure communication for the domain.
By default, if you enable secure communication for the domain, the installer sets up an HTTPS
connection for the Informatica Administrator. You can also create a domain configuration repository on
a secure database.

3. Specify the connection details for Informatica Administrator.
a. If you do not enable secure communication for the domain, you can specify whether to set up a
secure HTTPS connection for the Informatica Administrator.
The following table describes the options available to enable or disable a secure connection to
Informatica Administrator:
Option Description
Enable HTTPS for Set up a secure connection to Informatica Administrator.

Informatica Administrator
Disable HTTPS Do not set up a secure connection to Informatica Administrator.
b. If you enable secure communication for the domain or if you enable HTTPS connection for the
Informatica Administrator, enter the keystore file and port number for the HTTPS connection to
Informatica Administrator.
The following table describes the connection information you must enter if you enable HTTPS:
Option Description
Port Port number for the HTTPS connection.
Keystore file Select whether to use a keystore file generated by the installer or a keystore
file you create. You can use a keystore file with a self-signed certificate or a
certificate signed by a certification authority.
1 - Use a keystore generated by the installer
2 - Specify a keystore file and password
If you select to use a keystore file generated by the installer, the installer
creates a self-signed keystore file named Default.keystore in the following
location: <Informatica installation directory>/tomcat/conf/
c. If you specify the keystore, enter the password and location of the keystore file.
d. If you enabled secure communication for the domain, the Domain Security - Secure Communication
section appears.
e. If you did not enable secure communication for the domain, the Domain Configuration Repository
section appears. Skip to “Domain Configuration Repository” on page 109.
4. Select whether to enable SAML authentication to configure Security Assertion Markup Language
(SAML)-based single sign-on (SSO) support for web-based Informatica applications in an Informatica
domain.
Create a Domain 107

The following table describes the information you must enter to enable SAML authentication:
Prompt Description
Enable SAML Select whether to enable SAML authentication:

authentication 1 - No
If you select No, skip to “Domain Security - Secure Connection” on page 108 .
2 - Yes
If you select Yes, configure the SAML authentication.
5. Enter the Identity Provider URL for the domain.

6. Enter the identity provider assertion signing certificate alias name.
7. Select whether to use the default Informatica SSL certificates or to use your SSL certificates to enable
SAML authentication in the domain.
The following table describes the SSL certificate options for SAML authentication:
Option Description
Use the default Informatica SSL Select to use the default Informatica truststore file for SAML authentication.
certificate file.
Enter the location of the SSL Select to use a custom truststore file for SAML authentication. Specify the
certificate file. directory containing the custom truststore file on gateway nodes within the
domain. Specify the directory only, not the full path to the file.
8. If you provide the security certificates, specify the location and passwords of the keystore and truststore
files.
The following table describes the location and password of the truststore file:
Truststore Directory Specify the directory containing the custom truststore file on gateway nodes within the
Truststore Password The password for the custom truststore file.
The Domain Security - Secure Connection section appears.
Domain Security - Secure Connection

After you configure the domain, you can configure domain security.
u In the Domain Security - Secure Communication section, specify whether to use the default Informatica
SSL certificates or to use your SSL certificates to secure domain communication.
a. Select the type of SSL certificates to use.

The following table describes the options for the SSL certificates that you can use to secure the
Informatica domain:
Option Description
Use the default Use the default SSL certificates contained in the default keystore and
Informatica SSL truststore.
certificates Note: If you do not provide an SSL certificate, Informatica uses the same
default private key for all Informatica installations. If you use the default
Informatica keystore and truststore files, the security of your domain could be
compromised. To ensure a high level of security for the domain, select the
option to specify the location of the SSL certificate files.
Use custom SSL Specify the path for the keystore and truststore files that contain the SSL
certificates certificates. You must also specify the keystore and truststore passwords.
You can provide a self-signed certificate or a certificate issued by a certificate
authority (CA). You must provide SSL certificates in PEM format and in Java
Keystore (JKS) files. Informatica requires specific names for the SSL
certificate files for the Informatica domain. You must use the same SSL
certificates for all nodes in the domain. Store the truststore and keystore files
in a directory accessible to all the nodes in the domain and specify the same
keystore file directory and truststore file directory for all nodes in the same
domain.
b. If you provide the SSL certificate, specify the location and passwords of the keystore and truststore
files.
The following table describes the parameters that you must enter for the SSL certificate files:
Keystore password Password for the keystore infa_keystore.jks.
The Domain Configuration Repository section appears.
Domain Configuration Repository

After you configure domain security, you can configure domain repository details.
1. Select the database to use for the domain configuration repository details.
Create a Domain 109

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
The Informatica domain configuration repository stores metadata for domain operations and user
authentication. The domain configuration repository must be accessible to all gateway nodes in the
domain.
2. 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.
3. Select whether to create a secure domain configuration repository.

You can create a domain configuration repository in a database secured with the SSL protocol. To create
a domain configuration repository in a secure database, press 1 and skip to step to create a domain
configuration repository.
To create a domain configuration repository in an unsecure database, press 2.
4. 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 Select whether to specify a tablespace:

1 - No
2 - Yes
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.
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, if you select Yes to configure the tablespace,
enter the name of the tablespace in which to create the tables.
In a multi-partition database, specify the name of the tablespace that resides
in the catalog partition of the database.

b. If you select Microsoft SQL Server or PostgreSQL, enter the schema name for the database.
The following table describes the properties that you must configure for the 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.
properties.
The following table describes the database connection information:
Prompt Description
Database host name Host name for the database.
Database service Service or database name :

name - Oracle: Enter the service 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.
string.
IBM DB2
Oracle

Create a Domain 111

name>;SnapshotSerializable=true;EncryptionMethod=SSL;HostNameInCertificate=*.d
atabase.windows.net;ValidateServerCertificate=false
PostgreSQL
Sybase
Verify that the connection string contains all the connection parameters required by your
database system.
5. If you create a secure domain configuration repository, enter the parameters for the secure database.
If you create the domain configuration repository on a secure database, you must provide the truststore
information for the database. You must also provide a JDBC connection string that includes the security
parameters for the database.
The following table describes the options available to create a secure domain configuration repository
database:
Database truststore file Path and file name of the truststore file for the secure database.
Database truststore Password for the truststore file.

password
Custom JDBC Connection JDBC connection string to connect to the secure database, including the host
String name and port number and the security parameters for the database.
In addition to the host name and port number for the database server, you must include the following
secure database parameters: You can use the following syntax for the connection strings:
EncryptionMethod
Required. Indicates whether data is encrypted when transmitted over the network. This parameter
must be set to SSL.
ValidateServerCertificate
Optional. Indicates whether Informatica validates the certificate that the database server sends.
If this parameter is set to True, Informatica validates the certificate that the database server sends.
If you specify the HostNameInCertificate parameter, Informatica also validates the host name in the
certificate.
If this parameter is set to False, Informatica does not validate the certificate that the database
server sends. Informatica ignores any truststore information that you specify
Default is True.

HostNameInCertificate
Optional. Host name of the machine that hosts the secure database. If you specify a host name,
Informatica validates the host name included in the connection string against the host name in the
SSL certificate.
cryptoProtocolVersion
Required. Specifies the cryptographic protocol to use to connect to a secure database. You can set
the parameter to cryptoProtocolVersion=TLSv1.1 or cryptoProtocolVersion=TLSv1.2 based on
the cryptographic protocol used by the database server:
• Oracle: jdbc:Informatica:oracle://<host name>:<port number>;ServiceName=<service
• IBM DB2: jdbc:Informatica:db2://<host name>:<port number>;DatabaseName=<database
• Microsoft SQL Server: jdbc:Informatica:sqlserver://<host name>:<port
• PostgreSQL: jdbc:Informatica:postgresql://<host name>:<port
number>;DatabaseName=<database
Note: The installer does not validate the connection string. Verify that the connection string contains all
the connection parameters and security parameters required by your database.
6. If the database contains a domain configuration repository for a previous domain, select to overwrite the
data or set up another database.
The following table describes the options of overwriting the data or setting up another database when
you create a domain configuration repository for a previous domain:
Option Description
1 - OK Enter the connection information for a new database.
2 - Continue The installer overwrites the data in the database with new domain configuration.
The Domain Security - Encryption Key section appears.
Domain Security - Encryption Key

After you configure domain repository, you can configure encryption key.
u In the Domain Security - Encryption Key section, enter the keyword and directory for the encryption key
for the Informatica domain.
Create a Domain 113

The following table describes the encryption key parameters that you must specify when you create a
domain:
The encryption key is created based on the keyword that you provide when you
create the Informatica domain.
encryption key is created in the following directory: <Informatica
installation directory>/isp/config/keys.
The installer sets different permissions to the directory and the files in the directory. For more
information about the permissions for the encryption key file and directory, see “Secure Files and
Directories” on page 101.
The Domain and Node Configuration section appears.
Domain and Node Configuration

After you configure the encryption key, you can configure the domain and node.
1. Enter the information for the domain and the node that you want to create.
The following table describes the properties that you set for the domain and gateway node.
Domain name Name of the Informatica domain to create. The default domain name is
Domain_<MachineName>.
The name must not exceed 128 characters and must be 7-bit ASCII only. The
name cannot contain a space or any of the following characters: ` % * + ;
" ? , < > \ /
Node name Name of the node to create.
Node host name Host name or IP address of the machine on which to create the node.
If the machine has a single network name, use the default host name. If the a
machine has multiple network names, you can modify the default host name to
use an alternate network name.
Note: The node host name cannot contain the underscore (_) character. Do not
use localhost. The host name must explicitly identify the machine.

Node port number Port number for the node. The default port number for the node is 6005. If the
port number is not available on the machine, the installer displays the next
available port number.
Domain user name User name for the domain administrator. You can use this user name to initially
log in to 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.
2. Select whether you want to enable password complexity to secure sensitive data in the domain.
The following table describes the password complexity:
Prompt Description
Password complexity Select whether you want to enable password complexity.

1 - Yes
2 - No
If you select Yes, the password must meet the following requirements:
It must be at least eight characters long and contain at least one alpha character,
one numeric character, and one special character.
Domain password Password for the domain administrator. The password must be more than 2
characters and must not exceed 16 characters.
Not available if you configure the Informatica domain to run on a network with
Kerberos authentication.
Confirm password Enter the password again to confirm.

3. Select whether to display the default ports for the domain and node components assigned by the
installer.
The following table describes the advanced port configuration page:
Prompt Description
Display advanced port Select whether to display the port numbers for the domain and node components
configuration page assigned by the installer:
1 - No
2 - Yes
If you select Yes, the installer displays the default port numbers assigned to the
domain components. You can specify the port numbers to use for the domain and
node components. You can also specify a range of port numbers to use for the
service process that will run on the node. You can use the default port numbers or
specify new port numbers. Verify that the port numbers you enter are not used by
other applications.
Create a Domain 115

4. If you display the port configuration page, enter new port numbers at the prompt or press Enter to use
the default port numbers.
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.
HTTPS port Setting this port to 0 disables an HTTPS connection to the Administrator tool.
Informatica Administrator Port number that controls server shutdown for Informatica Administrator.
shutdown port Informatica 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.
5. Select if you want to configure the services and connection.

If you select Yes, you can configure the Model Repository Service, Data Integration Service, Content
Management Service, PowerCenter Repository Service, and PowerCenter Integration Service, as well as
the profiling warehouse connection and the connections associated with the cluster configuration.
If you select No, you can configure the application services from the Administrator tool.
If you choose to configure the services and connections, the Configure Informatica application services
section appears. If you choose not to configure the services and connections, the Post-Installation Summary
section indicates whether the installation completed successfully. The summary also shows the status of the
installed components and their configuration.
Configure Informatica Application Services

1. Select if you want to configure the Model Repository Service and Data Integration Service.
2. Select if you want to configure the monitoring Model Repository Service.
3. Select if you want to configure the Content Management Service.
4. Select if you want to configure the profiling warehouse connection.
5. Select if you want to create a PowerCenter Repository Service and a PowerCenter Integration Service.

Configure the Model Repository Database
After you configure the domain and the node, you can configure the Model repository database properties.
1. Enter the Model Repository Service name.

Enter the name of the service. The name is not case sensitive and must be unique within the domain. It
cannot exceed 128 characters or begin with @. It also cannot contain spaces or the following special
characters:
` ~ % ^ * + = { } \ ; : ' " / ? . , < > | ! ( ) ] [
You cannot change the name of the service after you create it.
If you selected process level SPN, specify the Model Repository Service keytab file. The keytab file for
the Model Repository Service process. The keytab file must have the following name: .keytab
2. Select the database to configure Model repository.
The following table lists the databases you can configure Model repository:
Prompt Description
Database type Type of database for the Model repository. Select from the following options:
1 - Oracle
3 - IBM DB2
4 - PostgreSQL

Database user ID Name for the Model repository database user account.
4. Select whether to create a secure Model repository database.

You can create a model repository service in a database secured with the SSL protocol. To create a
model repository service in a secure database, press 1 and skip to step to enter the JDBC information.
To create a model repository service in an unsecured database, press 2.
5. If you chose not to create a secured Model repository, enter the parameters for the database.
Create a Domain 117


1 - No
2 - Yes
properties.
Prompt Description

Prompt Description

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.
string.
IBM DB2
Oracle


PostgreSQL
Sybase
database system.
The Service Parameters section appears.
Create a Domain 119

Configure the Monitoring Model Repository Database
After you configure Model Repository database, you can configure the monitoring Model repository database
properties.
1. Enter the monitoring Model Repository Service name.

Enter the name of the service. The name is not case sensitive and must be unique within the domain. It
cannot exceed 128 characters or begin with @. It also cannot contain spaces or the following special
characters:
` ~ % ^ * + = { } \ ; : ' " / ? . , < > | ! ( ) ] [
You cannot change the name of the service after you create it.
If you selected process level SPN, specify the monitoring Model Repository Service keytab file. The
keytab file for the monitoring Model Repository Service process. The keytab file must have the following
name: .keytab
2. Select the database type for the monitoring Model repository.
The following table lists the databases for the monitoring Model repository.
Prompt Description
Database type Type of database for the monitoring Model repository. Select from the following
options:
1 - Oracle
3 - IBM DB2
4 - PostgreSQL

Database user ID Name for the monitoring Model repository database user account.
User password Password for the monitoring Model repository user account.
4. Select whether to create a secure monitoring Model repository database.

You can create a monitoring Model repository in a database secured with the SSL protocol. To create a
monitoring Model repository in a secure database, press 1 and skip to step to enter the JDBC
information.
To create a monitoring Model repository in an unsecured database, press 2.
5. If you do not create a secure monitoring Model repository, enter the parameters for the database.


1 - No
2 - Yes
properties.
Prompt Description
Create a Domain 121

Prompt Description

Parameters 1 - Yes
2 - No
parameters.
string.
IBM DB2
Oracle


PostgreSQL
Sybase
database system.
The Service Parameters section appears.

After you configure the Model Repository database, you can configure the service parameters for the
application services.
1. Enter the following service parameter information:
Port Description
Data Integration Service Name of the Data Integration Service to create in the Informatica domain.
name
HTTP protocol type Type of connection to the Data Integration Service. Select one of the following
options:
- HTTP. Requests to the service uses an HTTP connection.
- HTTPS. Requests to the service uses a secure HTTP connection.
- HTTP&HTTPS. Requests to the service can use either an HTTP or HTTPS
connection.
HTTP port Port number to use for the Data Integration Service. Default is 9085.
HTTPS port Port number to use for the Data Integration Service. Default is 9085.
2. Select the SSL certificates to use to secure the Data Integration Service.
Option Description
Use the default Informatica Use the default Informatica SSL certificates contained in the default keystore and
SSL certificate files truststore.
Note: If you do not provide an SSL certificate, Informatica uses the same default
private key for all Informatica installations. If you use the default Informatica
keystore and truststore files, the security of your domain could be compromised.
To ensure a high level of security for the domain, select the option to specify the
location of the SSL certificate files.
Use custom SSL certificates Use custom SSL certificates. You must specify the location of the keystore and
truststore files.
Keystore (JKS) files. Informatica requires specific names for the SSL certificate
files for the Informatica domain. You must use the same SSL certificates for all
nodes in the domain. Store the truststore and keystore files in a directory
accessible to all the nodes in the domain and specify the same keystore file
directory and truststore file directory for all nodes in the same domain.
If you choose to use custom SSL certificates, enter the following information.
Keystore file directory Directory that contains the keystore files. The directory must contain files named
infa_keystore.jks and infa_keystore.pem.
Create a Domain 123

Content Management Service Parameters and Database

After you configure the Data Integration Service, you can configure the parameters for the Content
Management Service.
1. Enter the following service parameter information:
Content Management Name of the Content Management Service to create in the Informatica domain.
Service name
HTTP protocol type Type of connection to the Content Management Service. Select one of the
following options:
HTTP port Port number to use for the Data Integration Service. Default is 9085.
2. Select the database type for the reference data warehouse.

The following table lists the databases for the reference data warehouse.
Prompt Description
Database type Type of database for the monitoring Model repository. Select from the following
options:
- Oracle
- IBM DB2

Database user ID Name for the reference data warehouse user account.
Database user password Password for the reference data warehouse user account.

4. 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.
a. Enter the JDBC connection information.
properties.
Prompt Description

Parameters 1 - Yes
2 - No
parameters.
string.
IBM DB2
Oracle

database system.
Profiling Warehouse Connection Database

After you configure the Content Management Service, you can you can configure the data profiling
warehouse connection database.
1. Select the database type for the data profiling warehouse.
Create a Domain 125

The following table lists the databases for the data profiling warehouse.
Prompt Description
Database type Type of database for the data profiling warehouse. Select from the following
options:
- Oracle
- IBM DB2

Database user ID Name for the reference data warehouse user account.
Database user password Password for the reference data warehouse user account.
3. 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.
a. Enter the JDBC connection information.
properties.
Prompt Description

Parameters 1 - Yes
2 - No
parameters.

string.
IBM DB2
Oracle

database system.
PowerCenter Repository Service and PowerCenter Integration

Service
After you create the cluster configuration, you can configure the PowerCenter Repository Service and the
PowerCenter Integration Service.
1. Select the database to configure for the PowerCenter repository.

The following table lists the databases you can configure for the PowerCenter repository:
Prompt Description
Database type Type of database for the PowerCenter repository. Select from the following options:
1 - Oracle
4 - PostgreSQL

Database user ID Name for the Model repository database user account.

3. Enter the name of the PowerCenter Repository Service to create.

4. Enter the name of the PowerCenter Integration Service to create.
The Post-Installation Summary section indicates whether the installation completed successfully. The
summary also shows the status of the installed components and their configuration.
Create a Domain 127

Join a domain
You can join a domain if you are installing on multiple machines and you have created a domain on another
machine.
Run the Installer

Perform the following steps to run the installer:

3. On a shell command line, run the install.sh file from the root directory.
Welcome - Accept Terms and Conditions

u Read the terms and conditions for Informatica installation and the product usage toolkit and select I
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.
a. Press 1 to not accept the terms and conditions
If you choose to not accept the terms and condition, the installer prompts you to accept the terms and
conditions.
The Installation Prerequisites section displays the installation requirements. Verify that all requirements are
met before you continue the installation.
Installation Prerequisites
Verify the disk space and memory required for installation and complete the pre-installation tasks.
1. Verify that you have the required disk space and memory (RAM) available for installation.
2. Verify the database requirements for the domain configuration repository.
3. Complete the pre-installation tasks, including getting your Informatica license key, setting environment
variables, and verifying port availability.
The License and Installation Directory section appears.

License and Installation Directory
After you verify the installation prerequisites, you can specify the installation directory.

( ) { } [ ] , ; ' Default is /home/toolinst.
2. Enter the path and file name of the Informatica license key and press Enter.
3. Choose whether you want to run the installer on a network that uses Kerberos authentication.
a. Press 1 to configure the Informatica domain to run on a network that does not use Kerberos
authentication.
b. Press 2 to configure the Informatica domain to run on a network with Kerberos authentication.
If you enabled Kerberos network authentication, the Service Principal Level section appears.
If you did not enable Kerberos network authentication, the Pre-Installation Summary section appears. Review
the installation information and press Enter to continue. Skip to “Domain Selection” on page 129.
Service Principal Level

After you specify the installation directory, you can configure security level.
u Select the level at which to set the Kerberos service principals for the domain.
The following table describes the levels that you can select:
Level Description
domains.
The Pre-Installation Summary section appears. Press Enter to continue.
Domain Selection
After you review the Pre-Installation summary, you can enter the domain information.
1. Press 2 to join a domain.

The installer joins a node on the machine where you install.
Join a domain 129

2. Specify whether the domain you want to join has the secure communication option enabled.
Press 1 to join an unsecure domain or press 2 to join a secure domain.
3. Select the type of node you want to create.
Press 1 to configure a gateway node or 2 to configure a worker node.
If you configure the node as a gateway, you can enable a secure HTTPS connection to the Informatica
Administrator.
4. If you enable HTTPS connection for the Informatica Administrator, enter an HTTPS port number to use to
secure the connection.
5. Select whether to use the default Informatica SSL certificates or to use your SSL certificates to enable
SAML authentication in the domain.
Option Description
certificate file.
6. Select whether to enable Security Assertion Markup Language (SAML) authentication to configure
SAML-based single sign-on (SSO) support for web-based Informatica applications in an Informatica
domain.
The following table describes the information you must enter to enable SAML authentication:
Prompt Description
Does the domain use Select if the domain uses SAML authentication:
SAML authentication? 1 - No
If you select No, skip to “ Domain Security - Secure Communication” on page 130
2 - Yes
If you select Yes, configure the SAML authentication.
The Domain Security - Secure Communication appears.
Domain Security - Secure Communication

After you select the domain, you can configure domain security.
u Specify whether to use the default Informatica SSL certificates or to use your SSL certificates to secure
domain communication.
a. Select the type of SSL certificates to use.

The following table describes the options for the SSL certificates that you can use to secure the
Informatica domain:
Option Description
Use the default Use the default SSL certificates contained in the default keystore and
Informatica SSL truststore.
certificates Note: If you do not provide an SSL certificate, Informatica uses the same
default private key for all Informatica installations. If you use the default
Informatica keystore and truststore files, the security of your domain could be
compromised. To ensure a high level of security for the domain, select the
option to specify the location of the SSL certificate files.
Use custom SSL Specify the path for the keystore and truststore files that contain the SSL
certificates certificates. You must also specify the keystore and truststore passwords.
Keystore (JKS) files. Informatica requires specific names for the SSL
certificate files for the Informatica domain. You must use the same SSL
certificates for all nodes in the domain. Store the truststore and keystore files
in a directory accessible to all the nodes in the domain and specify the same
keystore file directory and truststore file directory for all nodes in the same
domain.
b. If you provide the SSL certificate, specify the location and passwords of the keystore and truststore
files.
The Domain Configuration section appears.
Domain Configuration
After you configure domain security, you can configure domain repository connection details.
u Enter the information for the domain that you want to join.
Join a domain 131

The following table describes the properties that you specify for the domain:
Domain name Name of the domain to join.
Gateway node host Host name of the machine that hosts the gateway node for the domain.
Gateway node port Port number of the gateway node.
Domain user name User name of the administrator for the domain you want to join.
Domain password Password for the domain administrator.
Security domain name Name of the secure domain.
The Domain Security - Encryption Key section appears.
Domain Security - Encryption Key

After you configure the domain repository, you can configure the encryption key.
u Enter the directory for the encryption key for the Informatica domain.
The following table describes the encryption key parameters that you must specify when you join a
domain:
Prompt Description
Select the Path and file name of the encryption key for the Informatica domain that you want to join. All
encryption key nodes in the Informatica domain use the same encryption key. You must specify the
encryption key file created on the gateway node for the domain that you want to join.
If you copied the encryption key file to a temporary directory to make it accessible to the
nodes in the domain, specify the path and file name of the encryption key file in the temporary
directory.
Encryption key Directory in which to store the encryption key on the node created during this installation. The
directory installer copies the encryption key file for the domain to the encryption key directory on the
new node.
The installer sets different permissions to the directory and the files in the directory. For more
information about the permissions for the encryption key file and directory, see “Secure Files and
Directories” on page 101.
The Join Domain Node Configuration section appears.
Join Domain Node Configuration

After you configure the encryption key, you can configure the join domain and node.
1. Enter the information for the domain and the node that you want to join.

The following table describes the properties that you set for the current node.
Node host name Host name or IP address of the machine on which to join the node.
Node name Name of the node to join.
2. Select whether to display the advanced port configurations for the domain and node components
assigned by the installer.
If you select Yes, the Port Configuration section appears. The installer displays the default port numbers
assigned to the domain components. You can specify the port numbers to use for the domain and node
components. You can also specify a range of port numbers to use for the service process that will run on
the node. You can use the default port numbers or specify new port numbers. Verify that the port
numbers you enter are not used by other applications.
If you select No, the Post-Installation Summary section appears. The Post-Installation Summary section
indicates whether the installation completed successfully. The summary also shows the status of the
installed components and their configuration.
Port Configuration
If you chose to display the advanced port configuration page, you can set the ports for the domain
components.
u Enter new port numbers at the prompt or press Enter to use the default port numbers.
Port Description

port
Join a domain 133

Port Description
6009.
The Post-Installation Summary section appears. The Post-Installation Summary section indicates whether
the installation completed successfully. The summary also shows the status of the installed components and
their configuration.

Chapter 9
Install Informatica Services in

Graphical Mode
• Install the Services in Graphical Mode Overview, 135

• Creating a Domain, 135
• Joining a Domain, 158
Install the Services in Graphical Mode Overview

You can install the Informatica services in graphical mode on Windows.
When you run the Pre-Installation (i10Pi) System Check Tool before you perform the installation, the installer
sets the values for certain fields, such as the database connection and domain port numbers, based on the
information you entered during the system check.
On Windows, if you encounter problems when you run the install.bat file from the root directory, run the
following file: <installer files directory>\server\install.exe.
Important: If you install the Informatica services and the PowerCenter Client in the same install directory, the
service binaries will be uninstalled when you uninstall the PowerCenter Client.
Creating a Domain
Create a domain if you are installing for the first time or if you want to administer nodes in separate domains.

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.
Note: If you do not run the installer as administrator, the Windows system administrator might encounter
issues when accessing files in the Informatica installation directory.
The Informatica 10.4.0 page appears.
135
Informatica provides utilities to facilitate the Informatica services installation process. Run the following
utilities before you install 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.
For more information about running the Pre-Installation (i10Pi) System Check Tool, see “Run the Pre-
Installation (i10Pi) System Check Tool in Graphical Mode” on page 45.
• Informatica Kerberos SPN Format Generator. Creates a list of the Kerberos service principal names
and keytab file names required to run Informatica services on a network with Kerberos
authentication.
You can use the installer to run the utilities before you install informatica services. After you finish
running a utility, restart the installer to run the next utility or install informatica services.
5. Click Start.
136 Chapter 9: Install Informatica Services in Graphical Mode

6. Read the terms and conditions for Informatica installation and the product usage toolkit and select I
7. Click Next.
The Installation Prerequisites page displays the installation requirements. Verify that all requirements
are met before you continue the installation.
8. Click Next.
Creating a Domain 137

The License and Installation Directory page appears.
9. Enter the Informatica license key and the installation directory.

The following table describes the license key and directory that you specify for the informatica services
installation:
License key file Path and file name of the Informatica license key.
Installation directory Absolute path for the installation directory. The installation directory must be on
the machine where you are installing Informatica. 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.
10. To configure the Informatica domain to run on a network with Kerberos authentication, select Enable
Kerberos Network Authentication.
11. Click Next.

If you enabled Kerberos network authentication, the Network Security - Service Principal Level page
appears.
If you do not enable Kerberos network authentication, the Pre-Installation Summary page appears. Skip
to 16
12. On the Network Security - Service Principal Level page, select the level at which to set the Kerberos
service principals for the domain.
The following table describes the service principal levels that you can select:
Level Description
domains.
13. Click Next.

The Network Security - Kerberos Authentication page appears.
14. Enter the domain and keytab information required for Kerberos authentication.
The following table describes the Informatica domain and node information that you must provide:
Domain name Name of the domain to create.

" ? , < > \ /
Node host name Fully qualified host name or IP address of the machine on which to create the
node.

The following table describes the Kerberos realm and keytab information that you must provide:
Service realm name Name of the Kerberos realm that the domain uses to authenticate users. The
realm name must be in uppercase and is case-sensitive.
To configure Kerberos cross realm authentication, specify the name of each
Kerberos realm that the domain uses to authenticate users, separated by a
comma. For example:
COMPANY.COM,EAST.COMPANY.COM,WEST.COMPANY.COM
Use an asterisk as a wildcard character before a realm name to include all realms
that include the name. For example:
*EAST.COMPANY.COM
User realm name Name of the Kerberos realm that the domain uses to authenticate users. The
comma. For example:
*EAST.COMPANY.COM
Informatica.
Kerberos configuration file Path and file name of the Kerberos configuration file. Informatica requires the
following name for the Kerberos configuration file: krb5.conf
Important: If you configure the domain to run with Kerberos authentication, the domain and node name
and the node host name must match the names you specified when you ran the Informatica Kerberos
SPN Format Generator to generate SPN and keytab file names. If you use a different domain, node, or
host name, generate the SPN and keytab file names again and ask the Kerberos administrator to add the
new SPN to the Kerberos principal database and create the keytab files.
15. Click Next.

The Pre-Installation Summary page appears .
16. Review the installation information, and click Install to continue.

The installer copies the Informatica files to the installation directory. After the installer copies the files,
the Domain Selection page appears.
17. Select Create a domain.

When you create a domain, the node that you create becomes a gateway node in the domain. The
gateway node contains a Service Manager that manages all domain operations.
18. To set up secure communication between services in the domain, select Enable secure communication
for the domain.
By default, if you enable secure communication for the domain, the installer sets up an HTTPS
connection for the Informatica Administrator. You can also create a domain configuration repository on
a secure database.
19. To secure the connection to Informatica Administrator, select Enable HTTPS for Informatica
Administrator.
The following table describes the properties that you set for a secure connection to the Administrator
tool:
Enable HTTPS for Select this option to secure the connection to Informatica Administrator. To use
Informatica Administrator an unsecure HTTP connection, clear the option.
By default, if secure communication is enabled for the domain, the installer
enables this option. You can also enable this option even if you do not enable
secure communication for the domain.
Port The port to use for communication between Informatica Administrator and the
Service Manager.

Use a keystore file Use a self-signed keystore file generated by the installer. The installer creates a
generated by the installer keystore file named Default.keystore in the following location: <Informatica
installation directory>\tomcat\conf\
Specify a keystore file and Use a keystore file that you create. You can use a keystore file with a self-signed
password certificate or a certificate signed by a certification authority.
Keystore password A plain-text password for the keystore file. Required if you use a keystore file that
you create.
Keystore file Path and file name of the keystore file. Required if you use a keystore file that you
create.
20. To configure Security Assertion Markup Language (SAML)-based single sign-on (SSO) support for web-
based Informatica applications in an Informatica domain, Enable SAML authentication.
Note: If you enabled Kerberos network authentication, you cannot configure SAML authentication.
21. Click Next.
If you selected the Enable SAML authentication option, the SAML Authentication page appears.

24. Specify whether to use the default Informatica SSL certificates or to use your SSL certificates to enable
secure communication in the domain.

Option Description
certificate file.
files.
26. Click Next.

If you selected the Enable secure communication for the domain option, the Domain Security - Secure
Communication page appears.
If you did not enable secure communication for the domain, the Domain Configuration Repository page
appears. Skip to step 30.

27. On the Domain Security - Secure Communication page, specify whether to use the default Informatica
SSL certificates or to use your SSL certificates to enable secure communication in the domain.
The following table describes the SSL certificate options for securing the Informatica domain:
Option Description
Use the default Informatica Use the default SSL certificates provided by Informatica.
SSL certificate files Note: If you do not provide an SSL certificate, Informatica uses the same default
Specify the location of the Use SSL certificates that you provide. You must specify the location of the
SSL certificate files keystore and truststore files.
Keystore (JKS) files. Informatica requires specific names for the SSL certificate
files for the Informatica domain. You must use the same SSL certificates for all
nodes in the domain. Store the truststore and keystore files in a directory
accessible to all the nodes in the domain and specify the same keystore file
directory and truststore file directory for all nodes in the same domain.
files.
29. Click Next.

The Domain Configuration Repository page appears.
30. On the Domain Configuration Repository page, enter the database and user account information for the
domain configuration repository.
The domain configuration repository stores metadata for domain operations and user authentication.
The database must be accessible to all gateway nodes in the domain.
- Oracle
- IBM DB2
- PostgreSQL
- Sybase ASE

If you select IBM DB2, specify the tablespace for the repository tables:
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, 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
tablespace that resides in the catalog partition of the database.
If you select Microsoft SQL Server or PostgreSQL, specify the schema for the repository tables and
database connection:
Schema name Name of the schema that will contain the repository tables. If not selected, the
installer creates the tables in the default schema.
Trusted connection 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.
If you enabled secure communication for the domain, you can create the domain configuration
repository in a database secured with the SSL protocol. To create a secure domain configuration
repository, select Secure Database and skip to step 32.
Note: You cannot configure a secure connection to a Sybase database.

If you do not create a secure domain configuration repository, you can specify the connection properties
for the JDBC URL or provide the JDBC connection string.
• To enter the connection information using the JDBC URL, select JDBC URL and specify the database
connection properties.


32. If you selected the Secure database option to create a secure domain configuration repository, enter the
connection information using a custom JDBC connection string.
If you create the repository on a secure database, you must provide the truststore information for the
database. You must also provide a JDBC connection string that includes the security parameters for the
database.
The following table describes the properties you must set for a secure database:

password
For information about the security parameters you must include in the JDBC connection for a secure
database, see “Connection String to a Secure Database” on page 97.
34. Click Next.

The Domain Security - Encryption Key page appears.
35. Enter the keyword and directory for the encryption key of the Informatica domain.
The following table describes the encryption key parameters that you must specify:
The encryption key is created based on the keyword that you provide when you
create the Informatica domain.
encryption key is created in the following directory: <Informatica
installation directory>/isp/config/keys.
36. Click Next.

The Domain and Node Configuration page appears.
37. Enter the information for the domain and the node that you want to create.
The following table describes the properties that you set for the domain and gateway node:
Domain name Name of the Informatica domain to create. The default domain name is
Domain_<MachineName>.
" ? , < > \ /
Node host name Host name or IP address of the machine on which to create the node.

Domain user name User name for the domain administrator. You can use this user name to initially
log in to 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 Password for the domain administrator. The password must be more than 2
characters and must not exceed 16 characters.
Confirm password Enter the password again to confirm.

38. To display the default ports for the domain and node components assigned by the installer, enable
Display advanced port configuration page.
If you display the port configuration page, the installer displays the default port numbers assigned to the
domain and node. You can modify the port numbers or specify a different range of port numbers for the
application service processes. If you do not select the display the port configuration page, the installer
does not display the default port numbers and you cannot modify the assigned port numbers.
39. To create a Model Repository Service and a Data Integration Service during the installation, enable
Configure Model Repository Service and Data Integration Service.
If you select to configure the services, the installer creates a Model Repository Service and a Data
Integration Service in the new domain. You must specify the database for the Model repository and
configure the connection to the Data Integration Service. By default, the installer starts the services
when the installation completes.
If you do not configure the services, the installer does not create a Model Repository Service or a Data
Integration Service in the new domain. You can create the services in the Administrator tool after
installation.
40. Click Next.

If you selected to display the port configuration page, the installer displays the Port Configuration page
appears.
If you did not select to display the port configuration page, the installer displays the Windows Service
Configuration page. Skip to step 43.
41. On the Port Configuration page, enter the port numbers to use for the domain service manager and
service processes that will run on the node.
Verify that the port numbers you enter are not used by other applications.
Port Description

port
6009.

Port Description
42. Click Next.

The installer displays the Windows Service Configuration page.
43. On the Windows Service Configuration page, select whether to run the Windows service under a
different user account.
The installer 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.
The following table describes the properties that you set to run Informatica under a different account:
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.

44. Click Next.
If you selected to configure the Informatica application services, the installer displays the Model
Repository Service Database page appears.
If you did not select to create the services, the installer displays the Post-Installation Summary page.
The Post-Installation Summary page indicates whether the installation completed successfully. Skip to
step 53.
45. On the Model Repository Service Database page, enter the database and user account information for
the Model repository.
- Oracle
- IBM DB2
- PostgreSQL
- Sybase ASE

If you select IBM DB2, specify the tablespace for the repository tables:
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, 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
tablespace that resides in the catalog partition of the database.
If you select Microsoft SQL Server or PostgreSQL, specify the schema for the repository tables and
database connection:
Schema name Name of the schema that will contain the repository tables. If not selected, the
installer creates the tables in the default schema.
Trusted connection 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.
If you enabled secure communication for the domain, you can create the Model repository in a database
secured with the SSL protocol. To create a secure Model repository, skip to step 47.

If you do not create a secure Model repository, you can specify the connection properties for the JDBC
URL or provide the JDBC connection string.
• To enter the connection information using the JDBC URL, select JDBC URL and specify the database
connection properties.


IBM DB2
Oracle

PostgreSQL
system.
47. To create a secure Model repository, enable Secure database.

If you create the repository on a secure database, you must provide the truststore information for the
database. You must also provide a JDBC connection string that includes the security parameters for the
database.
The following table describes the properties you must set for a secure database:

password
For information about the security parameters you must include in the JDBC connection for a secure
database, see “Connection String to a Secure Database” on page 97.
49. Click Next.

The Application Service Parameters page appears.
50. On the Application Service Parameters page, enter the name of the Model Repository Service and
configure the Data Integration Service properties.
The following table describes services parameters that you must set:
Port Description
Model Repository Service Name of the Model Repository Service to create in the Informatica domain.
name
Data Integration Service Name of the Data Integration Service to create in the Informatica domain.
name
HTTP protocol type Type of connection to the Data Integration Service. Select one of the following
options:
- HTTP&HTTPS. Requests to the service can use either an HTTP or HTTPS
connection.
HTTP port Port number to used for the Data Integration Service. Default is 6030.
51. If you select an HTTPS connection, specify whether to use the default Informatica SSL certificates or to
use your SSL certificates to secure the connection to the Data Integration Service.

The following table describes the SSL certificate options for securing the Data Integration Service:
Option Description
Use the default Informatica Use the default SSL certificates provided by Informatica.
SSL certificate files Note: If you do not provide an SSL certificate, Informatica uses the same default
Enter the location of the Use SSL certificates that you provide. You must specify the location of the
SSL certificate files keystore and truststore files.
If you provide the certificate, specify the location and passwords of the keystore and truststore files.
Keystore file Required. Path and file name of the keystore file that contains the private keys
and SSL certificates for the database.
Keystore password Required. Password for the keystore file for the secure database.
Truststore file Required. Path and file name of the truststore file that contains the public key for
the database.
Truststore password Required. Password for the truststore file for the secure database.
52. Click Next.

The installer creates the Model Repository Service and Data Integration Service and starts the services.
The Post-Installation Summary page indicates whether the installation completed successfully. The
53. Click Done to close the installer.
You can view the files to get more information about the tasks performed by the installer and to view
configuration properties for the installed components.
Joining a Domain
You can join a domain if you are installing on multiple machines and you have created a domain on another
machine.


The Informatica 10.4.0 page appears.
Informatica provides utilities to facilitate the Informatica services installation process. Run the following
utilities before you install 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.
For more information about running the Pre-Installation (i10Pi) System Check Tool, see “Run the Pre-
Installation (i10Pi) System Check Tool in Graphical Mode” on page 45.
• Informatica Kerberos SPN Format Generator. Creates a list of the Kerberos service principal names
and keytab file names required to run Informatica services on a network with Kerberos
authentication.
If you plan to join a domain that uses Kerberos authentication, you must generate the service
principal names and keytab files for the node you create and service that will run on the node.
You can use the installer to run the utilities before you install informatica services. After you finish
running a utility, restart the installer to run the next utility or install informatica services.
5. Click Start.
Joining a Domain 159

7. Click Next.

The Installation Prerequisites page displays the installation requirements. Verify that all requirements
are met before you continue the installation.
8. Click Next.

The License and Installation Directory page appears.
9. Enter the Informatica license key and the installation directory.

The following table describes the license key and directory that you specify for the informatica services
installation:
License key file Path and file name of the Informatica license key.
Installation directory Absolute path for the installation directory. The installation directory must be on
the machine where you are installing Informatica. 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.
10. To join an Informatica domain that runs on a network with Kerberos authentication, select Enable
Kerberos Network Authentication.
11. Click Next.

If you enabled Kerberos network authentication, the Network Security - Service Principal Level page
appears.
If you did not enable Kerberos network authentication, the Pre-Installation Summary page appears. Skip
to step 16
12. On the Network Security - Service Principal Level page, select the service principal level of the domain
that you plan to join.
The following table describes the service principal levels that you can select:
Level Description
domains.
13. Click Next.

The Network Security - Kerberos Authentication page appears.
14. Enter the domain and keytab information required for Kerberos authentication.
The following table describes the information you must provide about the domain that you plan to join
and the node to create during installation:

" ? , < > \ /
Node host name Fully qualified host name or IP address of the machine on which to create the
node.

The following table describes the Kerberos realm and keytab information that you must provide:
Service realm name Name of the Kerberos realm that the domain uses to authenticate users. The
comma. For example:
*EAST.COMPANY.COM
User realm name Name of the Kerberos realm that the domain uses to authenticate users. The
comma. For example:
*EAST.COMPANY.COM
Informatica.
Kerberos configuration file Path and file name of the Kerberos configuration file. Informatica requires the
following name for the Kerberos configuration file: krb5.conf
15. Click Next.

The Pre-Installation Summary page appears.
16. Review the installation information, and click Install to continue.

The installer copies the Informatica files to the installation directory. After the installer copies the files,
the Domain Selection page appears.
17. Select Join a Domain.

18. Specify whether the domain you want to join has secure communication enabled.
To join a domain with secure communication enabled, select Join a secure domain. To join a domain
that does not have secure communication enabled, clear the option.
19. Select the type of node that you want to create.
To create a gateway node, select Configure this node as a gateway. To create a worker node, clear the
option.
If you configure the node as a gateway, you can enable a secure connection to the Informatica
Administrator.
20. To secure the connection to Informatica Administrator, select Enable HTTPS for Informatica
Administrator.

The following table describes the properties that you set for a secure connection to the Administrator
tool:
Enable HTTPS for Select this option to secure the connection to Informatica Administrator. To use
Informatica Administrator an unsecure HTTP connection, clear the option.
By default, if secure communication is enabled for the domain, the installer
enables this option. You can also enable this option even if you do not enable
secure communication for the domain.
Port The port to use for communication between Informatica Administrator and the
Service Manager.
Use a keystore file Use a self-signed keystore file generated by the installer. The installer creates a
generated by the installer keystore file named Default.keystore in the following location: <Informatica
installation directory>\tomcat\conf\
Specify a keystore file and Use a keystore file that you create. You can use a keystore file with a self-signed
password certificate or a certificate signed by a certification authority.
Keystore password A plain-text password for the keystore file. Required if you use a keystore file that
you create.
Keystore file Path and file name of the keystore file. Required if you use a keystore file that you
create.
21. To configure Security Assertion Markup Language (SAML)-based single sign-on (SSO) support for web-
based Informatica applications in an Informatica domain, Enable SAML authentication.
Note: If you enabled Kerberos network authentication, you cannot configure SAML authentication.
22. Click Next.

If you selected the Enable SAML authentication option, the SAML Authentication page appears.

25. Specify whether to use the default Informatica SSL certificates or to use your SSL certificates to enable
secure communication in the domain.
Option Description
certificate file.
files.

27. Click Next.

If the domain you want to join is secure, the Domain Security - Secure Communication page appears.

If the domain you want to join is not secure, the Domain Configuration page appears.
Skip to step 29.

28. On the Domain Security - Secure Communication page, specify whether to use the default Informatica
SSL certificates or to use your SSL certificates to enable secure communication in the domain.
To use the default SSL certificates provided by Informatica, select Use the default Informatica SSL
certificate files.
To use your SSL certificate, select Specify the location of the SSL certificate files and specify the
directories where the SSL certificate files are located.
Note: All nodes in the domain must use the same SSL certificates. When you join a node to a domain,
specify the same SSL certificates used by the gateway node in the domain.

Click Next.
29. Enter the information for the domain that you want to join.
The following table describes the properties that you specify for the domain:
Gateway node host Host name of the machine that hosts the gateway node for the domain.
Gateway node port Port number of the gateway node.
Domain user name User name of the administrator for the domain you want to join.
Domain password Password for the domain administrator.
30. Click Next.

The Domain Security - Encryption Key page appears.
31. Enter the encryption key information for the Informatica domain that you want to join.
The following table describes the encryption key parameters that you must specify when you join a
domain:
Select the encryption key Path and file name of the encryption key for the Informatica domain that you want
to join. All nodes in the Informatica domain use the same encryption key. You
must specify the encryption key file created on the gateway node for the domain
that you want to join.
If you copied the encryption key file to a temporary directory to make it
accessible to the nodes in the domain, specify the path and file name of the
encryption key file in the temporary directory.
Encryption key directory Directory in which to store the encryption key on the node created during this
installation. The installer copies the encryption key file for the domain to the
encryption key directory on the new node. By default, the encryption key is
created in the following directory: <Informatica installation
directory>/isp/config/keys.
32. Click Next.

The Join Domain Node Configuration page appears.
33. Enter the information for the node you want to create.
The following table describes the properties that you set for the node:
Node Host name Host name for the node. The node host name cannot contain the underscore (_)
character.
Node name Name of the Informatica node to create on this machine. The node name is not
the host name for the machine.
Node port number Port number for the node.

Database truststore file Path and file name of the truststore file for the secure database. Select the same
database truststore file used by the master gateway node in the domain.
Required if you join a gateway node to a domain that uses a secure domain
configuration repository database.
Truststore password Password for the database truststore file for the secure database.
Required if you join a gateway node to a domain that uses a secure domain
configuration repository database.
34. To display the default ports for the domain and node components assigned by the installer, select
Display advanced port configuration page.
If you display the port configuration page, the installer displays the default port numbers assigned to the
domain and node. You can modify the port numbers or specify a different range of port numbers for the
application service processes. If you do not select the display the port configuration page, the installer
does not display the default port numbers and you cannot modify the assigned port numbers.
35. Click Next.
If you selected to display the port configuration page, the installer displays the Port Configuration page.
If you did not select to display the port configuration page, the installer displays the Windows Service
Configuration page. Skip to step 38 .

36. On the Port Configuration page, enter the port numbers to use for the domain service manager and
service processes that will run on the node.
Verify that the port numbers you enter are not used by other applications.
Port Description
37. Click Next.

38. On the Windows Service Configuration page, select whether to run the Windows service under a
different user account.
The installer 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.
The following table describes the properties that you set to run Informatica under a different account:
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.
39. Click Next.

The Post-Installation Summary page indicates whether the installation completed successfully. The

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

Chapter 10
Run the Silent Installer

• Installing the Informatica Services in Silent Mode, 179

• Encrypting Passwords in the Properties File, 179
• Configure the Properties File, 180
• Run the Installer, 181
Installing the Informatica Services in Silent Mode

To install the Informatica services without user interaction, install in silent mode. Use a properties file to
specify the installation options. The installer reads the file to determine the installation options. You can use
silent mode installation to install the Informatica services on multiple machines on the network or to
standardize the installation across machines.
Copy the Informatica installation files to the hard disk on the machine where you plan to install the
Informatica. If you install on a remote machine, verify that you can access and create files on the remote
machine.
To install in silent mode, complete the following tasks:
1. Run the password encryption utility to encrypt the passwords in the installation properties file.
2. Configure the installation properties file and specify the installation options in the properties file.
3. Run the installer with the installation 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 128-
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:128=
179
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:128=mjkjmDR2kzFJiizfRWIOPg==
Configure the Properties File

Configure the properties file that contains the configuration properties required to install the Informatica
services in silent mode.
Informatica provides two versions of the properties file. Use either file to specify the options for your
installation.
Silent input properties file
The silent input properties file contains the configuration properties required to install the Informatica
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 properties file
The default silent input properties file contains default values for many configuration properties. The
properties are listed in the bottom portion of the file. Use the file if you plan to install the Informatica
services using the default property values.
The file contains properties set to the default value for the following options:
• Application service names.

• Secure Sockets Layer authentication.
• Kerberos authentication.
• Port number assignment for domain and node components.
To configure the properties file that contains the configuration properties required to install the Informatica
services in silent mode, complete the following steps:
1. Go to the root of the directory that contains the installation files.

2. Create a backup copy of the SilentInput.properties file.
3. Open either the SilentInput.properties file or the SilentInput_Default.properties file.
180 Chapter 10: Run the Silent Installer

4. Configure the properties in the file.
5. Save the file with the name SilentInput.properties.
Run the Installer

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

3. Verify that the directory contains the file SilentInput.properties that you edited and resaved.
4. Run the silent installation. On Linux, run silentInstall.sh.
The silent installer runs in the background. The process can take a while. The silent installation is complete
when the Informatica_<Version>_Services_InstallLog<timestamp>.log file is created in the installation
directory.
The silent installation fails if you incorrectly configure the properties file or if the installation directory is not
accessible. View the installation log files and correct the errors. Then run the silent installation again.
Run the Installer 181

Chapter 11
Troubleshooting
• Installation Troubleshooting Overview, 182

• Resuming a Failed Installer Process, 182
• Troubleshooting with Installation Log Files, 183
• Troubleshooting Domains and Nodes, 185
Installation Troubleshooting Overview

The topics in this section provides you information on troubleshooting probable issues that you might
encounter during Informatica installation process. The examples included in the topics describe general
troubleshooting strategies and are not a comprehensive list of possible causes of installation issues.
Resuming a Failed Installer Process

When the installation process stops midway, you can resume the installation from the point of failure or exit.
When the service installation process fails on UNIX or Linux, you can resume from the previous service
configuration and recover the last entered details for that service installation. The install process might fail
for reasons such as network outage, when you exit the installation before completing the entire installation
process, or because of incorrect information entered.
Consider the following guidelines for resuming the installation:

You can resume the installer
If a service fails or if the installation process fails during a service creation, you can resume the
installation process with the server installer. To resume the installation process, ensure that at least one
of the services is created and that the domain is up and running from the installation log. For example, if
you want to check whether the Model Repository Service is created, check if you have a service creation
success text in the server log in the following format:
SUCCESS: MRS Service [mrs_name] is created. Command ran successfully.
To resume the installation, run the installer again.
When you resume the installer while creating a service, the installer retains all the service and database
specific information, such as the create service status, service name, service enabled or disabled status.
182
You can confirm and use the previously entered values or specify new values for the service and resume
the installation process.
You cannot resume the installer
You cannot resume the installer in the following situations:
• You run installer to configure services after the services are created.
• You run the service configuration wizard.
• You join a domain.
Before You Resume the Installer

When the installation process stops midway, you can resume the installation from the point of failure or exit.
Before you can resume the installer, complete the following prerequisites:
1. In the installation log file present in the installation directory, verify that at least the domain and one
service is created. The installer log file name appears in the following syntax:
Informatica_<Version>_Services_<timestamp>.log
2. Ensure that you do not delete the installInst.obj object file present in the tools folder of the user
installation directory.
3. If you are going to resume through the silent installer, ensure that RESUME_INSTALLATION is set to true
in the SilentInput.properties file.
Resume the Installer

After you complete prerequisite tasks, you can resume the installer.
1. Open a command prompt and navigate to the location of the installation files.
2. Run the console installer or the silent installer.
3. When the regular installer runs, you might get a prompt confirming whether you want to resume previous
installer or not.
• If you do not want to resume installation, enter 1 for No. Default is 1.
• If you want to resume installation, enter 2 for Yes.
Before you can resume the installation, the services get validated.
Troubleshooting with Installation Log Files

You can use the following log files to troubleshoot an Informatica installation:
Installation log files
The installer produces log files during and after the installation. You can use these logs to get more
information about the tasks completed by the installer and errors that occurred during installation. The
installation log files include the following logs:
• Debug logs
• File installation logs
Troubleshooting with Installation Log Files 183

Service Manager log files
Log files generated when the Service Manager starts on a node.
Debug Log Files

The installer writes actions and errors to the debug log file. The name of the log file depends on the
Informatica component you install.
The debug log contains output from the infacmd and infasetup commands used to create the domain, node,
and application services. It also contains information about starting the application services.
The following table describes the properties of the debug log files:
Log File Name - Informatica_<Version>_Services.log

- Informatica_<Version>_Client.log
- Informatica_<Version>_Services_Upgrade.log
- Informatica_<Version>_Client_Upgrade.log
Location Installation directory.
Usage Get more information about the actions performed by the installer and get more information about
installation errors. The installer writes information to this file during the installation. If the installer
generates an error, you can use this log to troubleshoot the error.
Contents Detailed summary of each action performed by the installer, the information you entered in the
installer, each command line command used by the installer, and the error code returned by the
command.
File Installation Log File

The file installation log file contains information about the installed files.
The following table describes the properties of the installation log file:
Log File Name - Informatica_<Version>_Services_InstallLog.log

- Informatica_<Version>_Client_InstallLog.log
Location Installation directory.
Usage Get information about the files installed and registry entries created.
Contents Directories created, names of the files installed and commands run, and status for each installed
file.
Service Manager Log Files

The installer starts the Informatica service. The Informatica service starts the Service Manager for the node.
The Service Manager generates log files that indicate the startup status of a node. Use these files to
troubleshoot issues when the Informatica service fails to start and you cannot log in to Informatica
Administrator. The Service Manager log files are created on each node.
184 Chapter 11: Troubleshooting

The following table describes the files generated by the Service Manager:
catalina.out Log events from the Java Virtual Machine (JVM) that runs the Service Manager. For
example, a port is available during installation, but is in use when the Service Manager
starts. Use this log to get more information about which port was unavailable during
startup of the Service Manager.
The catalina.out file is in the following directory: <Informatica installation
directory>/logs/<node name>/catalina.out
node.log Log events generated during the startup of the Service Manager on a node. You can use
this log to get more information about why the Service Manager for a node failed to start.
For example, if the Service Manager cannot connect to the domain configuration database
after 30 seconds, the Service Manager fails to start. The node.log file is in the /tomcat/
logs directory.
Note: The Service Manager also uses node.log to record events when the Log Manager is unavailable. For
example, if the machine where the Service Manager runs does not have enough available disk space to write
log event files, the Log Manager is unavailable.
Troubleshooting Domains and Nodes

The installer can generate errors when creating and configuring domains and nodes during the Informatica
installation.
Creating the Domain Configuration Repository

If you create a domain, the installer creates a domain configuration repository to store domain metadata. The
installer uses the options you enter during installation to add configuration metadata to the domain
configuration repository. The installer uses JDBC to communicate with the database. You do not need to
configure ODBC or native connectivity on the machine where you install the Informatica services.
The installer creates and drops a table in the domain configuration repository database to verify the
connection information. The user account for the database must have create privileges on the database.
Each domain must have a separate domain configuration repository.
Creating or Joining a Domain

The installer completes different tasks depending on whether you create a domain or join a domain:
• Creating a domain. The installer runs the infasetup DefineDomain command to create the domain and the
gateway node for the domain on the current machine based on the information you enter in the Configure
Domain window.
• Joining a domain. The installer runs the infasetup DefineWorkerNode command to create a node on the
current machine, and runs the infacmd AddDomainNode command to add the node to the domain. The
installer uses the information you enter in the Configure Domain window to run the commands.
The infasetup and infacmd commands fail if the gateway node is unavailable. If the gateway node is
unavailable, you cannot log in to Informatica Administrator.
Troubleshooting Domains and Nodes 185

For example, the DefineDomain command fails if you click Test Connection and the connection test passes
but the database becomes unavailable before you click Next. The DefineDomain command can also fail if the
host name or IP address does not belong to the current machine. Verify that the database for the domain
configuration is available and that the host name is correct and try again.
If the AddDomainNode command fails, verify that the Informatica service is running on the gateway node and
try again.
Starting Informatica
The installer runs infaservice to start the Informatica service. To troubleshoot issues when Informatica fails
to start, use the information in the installation debug log and the node.log and catalina.out Service Manager
log files to identify the cause of the error.
If you create a domain, log in to Informatica Administrator after the Informatica service starts to verify that
the domain is available. If you join a domain, log in to Informatica Administrator after the Informatica service
starts to verify that the node was successfully created and started.
Informatica can fail to start for the following reasons:
• The Service Manager is out of system memory. The Java Runtime Environment (JRE) that starts
Informatica and runs the Service Manager may not have enough system memory to start. Set the
INFA_JAVA_OPTS environment variable to configure the amount of system memory used by Informatica.
On UNIX, you can set the memory configuration when you start Informatica.
• The domain configuration database is not available. Informatica fails to start on a node if the Service
Manager on a gateway node cannot connect to the domain configuration database within 30 seconds.
Verify that the domain configuration repository is available.
• Some of the folders in the Informatica installation directory do not have the appropriate execute
permissions. Grant execute permission on the Informatica installation directory.
Pinging the Domain

The installer runs the infacmd Ping command to verify that the domain is available before it continues the
installation. The domain must be available so that license objects can be added to the domain. If the Ping
command fails, start Informatica on the gateway node.
Adding a License
The installer runs the infacmd AddLicense command to read the Informatica license key file and create a
license object in the domain. To run the application services in Informatica Administrator, a valid license
object must exist in the domain.
If you use an incremental license and join a domain, the serial number of the incremental license must match
the serial number for an existing license object in the domain. If the serial numbers do not match, the
AddLicense command fails.
You can get more information about the contents of the license key file used for installation, including serial
number, version, expiration date, operating systems, and connectivity options in the installation debug log.
You can get more information about existing licenses for the domain in Informatica Administrator.
186 Chapter 11: Troubleshooting

Part IV: After You Install the
Services
• Complete the Domain Configuration, 188

• Prepare to Create the Application Services, 193
• Create and Configure Application Services, 201
187
Chapter 12
Complete the Domain

Configuration
• Checklist to Complete the Domain Configuration, 188

• Complete the Domain Configuration Overview, 189
• Verify Locale Settings and Code Page Compatibility, 189
• Configure Environment Variables on UNIX or Linux, 190
Checklist to Complete the Domain Configuration

This chapter contains information about domain configuration tasks that you need to complete after
installation. Use this checklist to track domain configuration tasks.
 Verify locale settings and code page compatibility:

• Verify
that the domain configuration database is compatible with the code pages of the application
services that you create in the domain.
• Verifythat the locale settings on machines that access the Administrator tool and the Informatica client
tools is compatible with the code pages of repositories in the domain.
• Configure the locale environment variables.
 Configure the following environment variables:

• Informatica environment variables to store memory, domain, and location settings.
• Library path environment variables on the machines that run the Data Integration Service.
• Kerberosenvironment variables if you configure the Informatica domain to run on a network with
188
Complete the Domain Configuration Overview
After you install Informatica services and before you create the application services, complete the
configuration for the domain services.
Domain configuration includes tasks such as verifying code pages, configuring the environment variables for
the domain, and configuring the firewall.
Verify Locale Settings and Code Page Compatibility

The code pages for application services must be compatible with code pages in the domain.
Verify and configure the locale settings and code pages:
Verify that the domain configuration database is compatible with the code pages of the application services that you
create in the domain.
The Service Manager synchronizes the list of users in the domain with the list of users and group in each
application service. If a user name in the domain has characters that the code page of the application
service does not recognize, characters do not convert correctly and inconsistencies occur.
Verify that the locale settings on machines that access the Administrator tool and the Informatica client tools are
compatible with code pages of repositories in the domain.
If the locale setting is not compatible with the repository code page, you cannot create an application
service.
Configure Locale Environment Variables

Verify that the locale setting is compatible with the code page for the repository. If the locale setting is not
compatible with the repository code page, you cannot create an application service.
Use LANG, LC_CTYPE, or LC_ALL to set the UNIX or Linux code page.
Different 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 operating system and the existing locale settings.
Set the following locale environment variables:
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.
Complete the Domain Configuration Overview 189

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 Environment Variables on UNIX or Linux

Informatica uses environment variables to store configuration information when it runs the application
services and connects to the clients. Configure the environment variables to meet the Informatica
requirements.
Incorrectly configured environment variables can cause the Informatica domain or nodes to fail to start or
can cause connection problems between the Informatica clients and the domain.
To configure environment variables, log in with the system user account you used to install Informatica.
Configure Informatica Environment Variables

You can configure Informatica environment variables to store memory, domain, and location settings.
Set the following environment variables:
INFA_JAVA_OPTS
By default, Informatica uses a maximum of 512 MB of system memory.
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.
190 Chapter 12: Complete the Domain Configuration

You can use the INFA_JAVA_OPTS environment variable to configure the amount of system memory
used by Informatica. For example, to configure 1 GB of system memory for the Informatica daemon in a
C shell, use the following command:
setenv INFA_JAVA_OPTS “-Xmx1024m”
Restart the node for the changes to take effect.
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.
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.
INFA_TRUSTSTORE
If you enable secure communication for the domain, set the INFA_TRUSTSTORE variable with the
directory that contains the truststore files for the SSL certificates. The directory must contain truststore
files named infa_truststore.jks and infa_truststore.pem.
You must set the INFA_TRUSTSTORE variable if you use the default SSL certificate provided by
Informatica or a certificate that you provide.
If you enable secure communication for the domain and you specify the SSL certificate to use, set the
INFA_TRUSTSTORE_PASSWORD variable with the password for the infa_truststore.jks that contains the
SSL certificate. The password must be encrypted. Use the command line program pmpasswd to encrypt
the password.
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}”
Configure Environment Variables on UNIX or Linux 191

Database Value
Informix <Database path>/lib
Teradata <Database path>/lib
ODBC <CLOSEDODBCHOME>/lib
PostgreSQL $PGHOME/lib:$ {LD_LIBRARY_PATH}
Configure Kerberos Environment Variables

If you configure the Informatica domain to run on a network with Kerberos authentication, you must set the
Kerberos configuration and credential cache environment variables.
Set the following environment variables:
KRB5_CONFIG
Use the KRB5_CONFIG environment variable to store the path and file name of the Kerberos
configuration file. The name of the Kerberos configuration file is krb5.conf. You must set the
KRB5_CONFIG environment variable on each node in the Informatica domain.
KRB5CCNAME
Set the KRB5CCNAME environment variable with the path and file name of the Kerberos user credential
cache. Kerberos single sign-on requires Kerberos credential cache for user accounts.
When you cache the user credential, you must use the forwardable option. For example, if you use kinit to
get and cache the user credential, you must use the -f option to request forwardable tickets.
192 Chapter 12: Complete the Domain Configuration

Chapter 13
Prepare to Create the Application

Services
• Checklist for Preparing to Create Application Services, 193

• Create Directories for the Analyst Service, 194
• Create a Keystore for a Secure Connection to a Web Application Service, 194
• Log In to Informatica Administrator, 195
• Create Connections, 196
Checklist for Preparing to Create Application

Services
This chapter contains tasks that you need to complete before you create or configure the Analyst Service, the
Data Integration Service, and the Content Management Service. When you configure the services you
configure properties based on the connections and directories that you create. Use this checklist to track the
configuration tasks.
 Create the following directories for the Analyst Service:

• Flat file caches
• Temporary business glossary files
• Glossary assets
 Create the following connections for the Data Integration Service:

• Data object cache database
• Workflow database
• Profiling warehouse
 Create the following connection for the Content Management Service:

• Reference data warehouse
193
Create Directories for the Analyst Service
Before you create the Analyst Service, you must create directories for the Analyst tool to store temporary
files.
Create the following directories on the node that runs the Analyst Service:
Flat file cache directory
Create a directory for the flat file cache where the Analyst tool stores uploaded flat files. The Data
Integration Service must also be able to access this 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.
For example, you can create a directory named "flatfilecache" in the following mapped drive that all
Analyst Service and Data Integration Service processes can access:
F:\shared\<Informatica installation directory>\server
When you import a reference table or flat file source, the Analyst tool uses the files from this directory to
create a reference table or flat file data object.
Temporary export file directory
Create a directory to store the temporary business glossary files that the business glossary export
process creates. Create the directory on the node that runs the Analyst Service.
For example, you can create a directory named "exportfiledirectory" in the following location:
<Informatica installation directory>/server
Asset attachments directory
Create a directory to store the files that content managers add as attachments to Glossary assets.
Create the directory on the node that runs the Analyst Service.
For example, you can create a directory named "attachmentdirectory" in the following location:
<Informatica installation directory>/server
Create a Keystore for a Secure Connection to a Web

Application Service
You can secure the connection between the Informatica domain and a web application service, such as the
Analyst service. Informatica uses the SSL/TLS protocol to encrypt network traffic. To secure the connection,
you must create the required files.
Before you can secure the connection to a web application service, verify that the following requirements are
met:
194 Chapter 13: Prepare to Create the Application Services

and keystore.
The keystore is in an accessible directory.
The keystore must be in a directory that is accessible to the Administrator tool.
Log In to Informatica Administrator

You must have a user account to log in to the Informatica Administrator web application.
If the Informatica domain runs on a network with Kerberos authentication, you must configure the browser to
allow access to the Informatica web applications. In Microsoft Internet Explorer and Google Chrome, add the
URL of the Informatica web application to the list of trusted sites. If you are using Chrome version 41 or later,
you must also set the AuthServerWhitelist and AuthNegotiateDelegateWhitelist policies.
1. Start a Microsoft Internet Explorer or Google Chrome browser.

2. In the Address field, enter the URL for the Administrator tool:
• If the Administrator tool is not configured to use a secure connection, enter the following URL:
http://<fully qualified hostname>:<http port>/administrator/
• If the Administrator tool is configured to use a secure connection, enter the following URL:
https://<fully qualified hostname>:<http port>/administrator/
Host name and port in the URL represent the host name and port number of the master gateway node. If
you configured secure communication for the domain, you must use HTTPS in the URL to ensure that
you can access the Administrator tool.
If you use Kerberos authentication, the network uses single sign on. You do not need to log in to the
Administrator tool with a user name and password.
3. If you do not use Kerberos authentication, enter the user name, password, and security domain for your
user account, and then click Login.
The Security Domain field appears when the Informatica domain contains an LDAP security domain. If
you do not know the security domain that your user account belongs to, contact the Informatica domain
administrator.
Note: If this is the first time you log in with the user name and password provided by the domain
administrator, change your password to maintain security.
Troubleshooting the Login to Informatica Administrator

If the Informatica domain uses Kerberos authentication, you might encounter the following issues when
logging in to the Administrator tool:
I cannot log in to the Administrator tool from the same machine where I created the domain gateway node.
After installation, if you cannot log in to the Administrator tool from the same machine where you
created the domain gateway node, clear the browser cache. When you initially log in to the Administrator
Log In to Informatica Administrator 195

tool after installation, you can only log in with the Administrator user account created during installation.
If a different user credential is stored in the browser cache, the login can fail.
A blank page appears after I log in to the Administrator tool.
If a blank page appears after you log in to the Administrator tool, verify that you enabled delegation for
all user accounts with service principals used in the Informatica domain. To enable delegation, in the
Microsoft Active Directory Service, set the Trust this user for delegation to any service (Kerberos only)
option for each user account that you set an SPN.
Create Connections
In the Administrator tool, create connections to the databases that the application services use. You need to
specify the connection details while you configure the application service.
When you create the database connection, specify the database connection properties and test the
connection.
The following table describes the database connections that you need to create before the application
services can access the associated databases.
Database Description
Connection
Data object cache To access the data object cache, create the data object cache connection for the Data
database Integration Service.
Workflow database To store run-time metadata for workflows, create the workflow database connection for the
Data Integration Service.
Profiling warehouse To create and run profiles and scorecards, create the profiling warehouse database
database connection for the Data Integration Service. Use this instance of the Data Integration Service
when you configure the run-time properties of the Analyst Service.
Note: To use the Microsoft SQL Server database as the profiling warehouse, choose ODBC as
the provider type, and clear the use DSN option in the Microsoft SQL Server connection
properties dialog box when you configure the Microsoft SQL Server connection.
Reference data To store reference table data, create the reference data warehouse connection for the
warehouse Content Management Service.
IBM DB2 Connection Properties

Use a DB2 for LUW connection to access tables in a DB2 for LUW database.
The following table describes the DB2 for LUW connection properties:
User name Database user name.
Password Password for the user name.

Connection String for metadata access Connection string to import physical data objects. Use the following
connection string: jdbc:informatica:db2://<host>:
50000;databaseName=<dbname>
Connection String for data access Connection string to preview data and run mappings. Enter dbname from
the alias configured in the DB2 client.
Code Page Database code page.
Environment SQL Optional. Enter SQL commands to set the database environment when you
connect to the database. The Data Integration Service executes the
connection environment SQL each time it connects to the database.
Transaction SQL Optional. Enter SQL commands to set the database environment when you
transaction environment SQL at the beginning of each transaction.
Retry Period This property is reserved for future use.
Tablespace Tablespace name of the DB2 for LUW database.
SQL Identifier Character The type of character used to identify special characters and reserved SQL
keywords, such as WHERE. The Data Integration Service places the
selected character around special characters and reserved SQL keywords.
The Data Integration Service also uses this character for the Support
Mixed-case Identifiers property.
Support Mixed-case Identifiers When enabled, the Data Integration Service places identifier characters
around table, view, schema, synonym, and column names when generating
and executing SQL against these objects in the connection. Use if the
objects have mixed-case or lowercase names. By default, this option is not
selected.
Microsoft SQL Server Connection Properties

Use a Microsoft SQL Server connection to access tables in a Microsoft SQL Server database.
The following table describes the Microsoft SQL Server connection properties:
Use Trusted Connection Optional. When enabled, the Data Integration Service uses Windows
authentication to access the Microsoft SQL Server database. The user
name that starts the Data Integration Service must be a valid Windows
user with access to the Microsoft SQL Server database.
connection string: jdbc:informatica:sqlserver://
<host>:<port>;databaseName=<dbname>
Create Connections 197

Connection String for data access Connection string to preview data and run mappings. Enter
<ServerName>@<DBName>
Domain Name Optional. Name of the domain where Microsoft SQL Server is running.
Packet Size Required. Optimize the ODBC connection to Microsoft SQL Server. Increase
the packet size to increase performance. Default is 0.
Owner Name Name of the schema owner. Specify for connections to the profiling
warehouse database or data object cache database.
Schema Name Name of the schema in the database. Specify for connections to the
profiling warehouse or data object cache database. You must specify the
schema name for the profiling warehouse if the schema name is different
from the database user name. You must specify the schema name for the
data object cache database if the schema name is different from the
database user name and you manage the cache with an external tool.
selected.
Note: When you use a Microsoft SQL Server connection to access tables in a Microsoft SQL Server database,
the Developer tool does not display the synonyms for the tables.

Oracle Connection Properties
Use an Oracle connection to access tables in an Oracle database.
The following table describes the Oracle connection properties:
connection string: jdbc:informatica:oracle://<host>:
1521;SID=<sid>
Connection String for data access Connection string to preview data and run mappings. Enter dbname.world
from the TNSNAMES entry.
Parallel Mode Optional. Enables parallel processing when loading data into a table in
bulk mode. Default is disabled.
selected.
Creating a Connection
In the Administrator tool, you can create relational database, social media, and file systems connections.
1. In the Administrator tool, click the Manage tab.

2. Click the Connections view.
3. In the Navigator, select the domain.
4. In the Navigator, click Actions > New > Connection.
The New Connection dialog box appears.
Create Connections 199

5. In the New Connection dialog box, select the connection type, and then click OK.
The New Connection wizard appears.
6. Enter the connection properties.
The connection properties that you enter depend on the connection type. Click Next to go to the next
page of the New Connection wizard.
7. When you finish entering connection properties, you can click Test Connection to test the connection.
8. Click Finish.

Chapter 14
Create and Configure Application

Services
• Checklist to Create and Configure Application Services, 201

• Create and Configure the Application Services Overview, 202
• Create and Configure the Model Repository Service, 202
• Create and Configure the Data Integration Service, 206
• Create and Configure the PowerCenter Repository Service, 210
• Create and Configure the PowerCenter Integration Service, 213
• Create and Configure the Metadata Manager Service, 215
• Create and Configure the Content Management Service, 220
• Create and Configure the Analyst Service, 222
• Create and Configure the Search Service, 224
Checklist to Create and Configure Application

Services
This chapter contains instructions to create and configure application services. Even if you created services
during installation, you might still need to configure some services. Use this checklist to track completion of
application service configuration.
 Review your notes for planning the application services.
 Identify the services that you created during installation, and complete additional configuration for the
service.
 Create and configure other services that you want in the domain.
201
Create and Configure the Application Services
Overview
If you did not create services with you ran the installer, use the Administrator tool to create the application
services.
Some application services depend on other application services. When you create these dependent
application services, you must provide the name of other running application services. Review the application
service dependencies to determine the order that you must create the services. For example, you must create
a Model Repository Service before you create a Data Integration Service.
Before you create the application services, verify that you have completed the prerequisite tasks required by
the installation and configuration process.
Create and Configure the Model Repository Service

The Model Repository Service is an application service that manages the Model repository. The Model
repository stores metadata created by Informatica clients and application services in a relational database to
enable collaboration among the clients and services.
When you access a Model repository object from an Informatica client tool or application service, the client
or service sends a request to the Model Repository Service. The Model Repository Service process fetches,
inserts, and updates the metadata in the Model repository database tables.
Create the Model Repository Service

Use the service creation wizard in the Administrator tool to create the service.

2. Click Actions > New > Model Repository Service.
The New Model Repository Service dialog box appears.
3. On the New Model Repository Service - Step 1 of 2 page, enter the following properties:
Name Name of the service. The name is not case sensitive and must be unique within the domain. It
cannot exceed 128 characters or begin with @. It also cannot contain spaces or the following
special characters:
`~%^*+={}\;:'"/?.,<>|!()][
Description Description of the service. The description cannot exceed 765 characters.
Location Domain and folder where the service is created. Click Browse to choose a different folder. You
can move the service after you create it.
License License object that allows use of the service.
202 Chapter 14: Create and Configure Application Services

Node Node on which the service runs.
Backup Nodes If your license includes high availability, nodes on which the service can run if the primary node
is unavailable.
4. Click Next.
The New Model Repository Service - Step 2 of 2 page appears.
5. Enter the following properties for the Model repository database:
Database Type The type of the repository database.
Username The database user name for the repository.
Password Repository database password for the database user.
Database Schema Available for Microsoft SQL Server and PostgreSQL. Name of the schema that will
contain Model repository tables.
Database Available for IBM DB2. Name of the tablespace in which to create the tables. For a multi-
Tablespace partition IBM DB2 database, the tablespace must span a single node and a single
partition.
6. Enter the JDBC connection string that the service uses to connect to the Model repository database.
Use the following syntax for the connection string for the selected database type:
Database Type Connection String Syntax
IBM DB2 jdbc:informatica:db2://<host name>:<port

number>;DatabaseName=<database
name>;BatchPerformanceWorkaround=true;DynamicSections=3000
Microsoft SQL Server - Microsoft SQL Server that uses the default instance
jdbc:informatica:sqlserver://<host name>:<port
number>;DatabaseName=<database name>;SnapshotSerializable=true
- Microsoft SQL Server that uses a named instance
jdbc:informatica:sqlserver://<host name>\<named instance
name>;DatabaseName=<database name>;SnapshotSerializable=true
- Azure SQL Server. jdbc:informatica:sqlserver://
<host_name>:<port_number>;DatabaseName=<database_name>;Snapsho
tSerializable=true;
SnapshotSerializable=true;EncryptionMethod=SSL;HostNameInCerti
ficate=*.<hostnameincertificate>;ValidateServerCertificate=tru
e
Create and Configure the Model Repository Service 203

Database Type Connection String Syntax
Oracle jdbc:informatica:oracle://<host name>:<port

number>;SID=<database
name>;MaxPooledStatements=20;CatalogOptions=0;BatchPerformanceWo
rkaround=true
PostgreSQL jdbc:informatica:postgresql://<host name>:<port

number>;DatabaseName=
7. If the Model repository database is secured with the SSL protocol, you must enter the secure database
parameters in the Secure JDBC Parameters field.
Enter the parameters as name=value pairs separated by semicolon characters (;). For example:
param1=value1;param2=value2
Enter the following secure database parameters:
Secure Database Description

Parameter
EncryptionMethod Required. Indicates whether data is encrypted when transmitted over the network.
This parameter must be set to SSL.
ValidateServerCertificate Optional. Indicates whether Informatica validates the certificate that the database
server sends.
If this parameter is set to True, Informatica validates the certificate that the
database server sends. If you specify the HostNameInCertificate parameter,
Informatica also validates the host name in the certificate.
If this parameter is set to False, Informatica does not validate the certificate that
the database server sends. Informatica ignores any truststore information that you
specify.
HostNameInCertificate Optional. Host name of the machine that hosts the secure database. If you specify
a host name, Informatica validates the host name included in the connection string
against the host name in the SSL certificate.
cryptoProtocolVersion Required. Specifies the cryptographic protocol to use to connect to a secure

database. You can set the parameter to cryptoProtocolVersion=TLSv1.1 or
cryptoProtocolVersion=TLSv1.2 based on the cryptographic protocol used by
the database server.
TrustStore Required. Path and file name of the truststore file that contains the SSL certificate
for the database.
If you do not include the path for the truststore file, Informatica looks for the file in
the following default directory: <Informatica installation directory>/
tomcat/bin
TrustStorePassword Required. Password for the truststore file for the secure database.
Note: Informatica appends the secure JDBC parameters to the JDBC connection string. If you include the
secure JDBC parameters directly in the connection string, do not enter any parameter in the Secure
JDBC Parameters field.
8. Click Test Connection to verify that you can connect to the database.
9. Select No content exists under specified connection string. Create new content.

10. Click Finish.
The domain creates the Model Repository Service, creates content for the Model repository in the
specified database, and enables the service.
Note: When you update the Model Repository Service properties, you must restart the Model Repository
Service for the modifications to take effect.
After you create the service through the wizard, you can edit the properties or configure other properties.
After You Create the Model Repository Service

After you create the Model Repository Service, perform the following tasks:
• Create the Model repository user if the domain does not use Kerberos authentication.
• Create other application services.
Create the Model Repository User

When you create an application service that depends on the Model Repository Service, you provide the name
of the Model Repository Service and of this Model repository user.
If the domain does not use Kerberos authentication, the domain uses a user account to authenticate other
application services that make requests to the Model Repository Service. You must create a user account
and assign the user the Administrator role for the Model Repository Service.
1. In the Administrator tool, click the Security tab.

2. On the Security Actions menu, click Create User to create a native user account.
Note: If you set up LDAP authentication in the domain, you can use an LDAP user account for the Model
repository user.
3. Enter the following properties for the user:
Login Name Login name for the user account. The login name for a user account must be unique
within the security domain to which it belongs.
The name is not case sensitive and cannot exceed 128 characters. It 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. All
other space characters are not allowed.
Password Password for the user account. The password can be from 1 through 80 characters long.
Confirm Password Enter the password again to confirm. You must retype the password. Do not copy and
paste the password.
Create and Configure the Model Repository Service 205

Full Name Full name for the user account. The full name cannot include the following special
characters:
<>“
Description Description of the user account. The description cannot exceed 765 characters or include
the following special characters:
<>“
4. Click OK.
The user properties appear.
5. Click the Privileges tab.
6. Click Edit.
The Edit Roles and Privileges dialog box appears.
7. On the Roles tab, expand the Model Repository Service.
8. Under System Defined Roles, select Administrator and click OK.
Create Other Services

After you create the Model Repository Service, create the application services that depend on the Model
Repository Service.
Create the dependent services in the following order:
1. Data Integration Service

2. Analyst Service
3. Content Management Service
4. Search Service
Create and Configure the Data Integration Service

When you preview or run data profiles, SQL data services, and mappings in the Analyst tool or the Developer
tool, the client tool sends requests to the Data Integration Service to perform the data integration jobs. When
you run SQL data services, mappings, and workflows from the command line program or an external client,
the command sends the request to the Data Integration Service.
Create the Data Integration Service

Before you create the Data Integration Service, verify that you have created the following service:

2. Click the Services and Nodes view.

3. In the Domain Navigator, select the domain.
4. Click Actions > New > Data Integration Service.
The New Data Integration Service wizard appears.
5. On the New Data Integration Service - Step 1 of 14 page, enter the following properties:
special characters:
`~%^*+={}\;:'"/?.,<>|!()][
Location Domain and folder where the service is created. Click Browse to choose a different folder.
You can move the service after you create it.
Assign Select Node to configure the service to run on a node. If your license includes grid, you can
create a grid and assign the service to run on the grid after you create the service.
Backup Nodes If your license includes high availability, nodes on which the service can run if the primary
node is unavailable.
Model Model Repository Service to associate with the service.

Repository
Service
Username User name that the service uses to access the Model Repository Service. Enter the Model
repository user that you created.
Password Password for the Model repository user.
Security Domain LDAP security domain for the Model repository user. The field appears when the Informatica
domain contains an LDAP security domain. Not available for a domain with Kerberos
authentication.
6. Click Next.
The New Data Integration Service - Step 2 of 14 page appears.
7. Enter the HTTP port number to use for the Data Integration Service.
8. Accept the default values for the remaining security properties. You can configure the security properties
after you create the Data Integration Service.
9. Select Enable Service.
The Model Repository Service must be running to enable the Data Integration Service.
10. Verify that the Move to plugin configuration page is not selected.
11. Click Next.
12. Set the Launch Job Options property to one of the following values:
Create and Configure the Data Integration Service 207

• In the service process. Configure when you run SQL data service and web service jobs. SQL data
service and web service jobs typically achieve better performance when the Data Integration Service
runs jobs in the service process.
• In separate local processes. Configure when you run mapping, profile, and workflow jobs. When the
Data Integration Service runs jobs in separate local processes, stability increases because an
unexpected interruption to one job does not affect all other jobs.
If you configure the Data Integration Service to run on a grid after you create the service, you can
configure the service to run jobs in separate remote processes.
13. Accept the default values for the remaining execution options and click Next.
14. If you created the data object cache database for the Data Integration Service, click Select to select the
cache connection. Select the data object cache connection that you created for the service to access the
database.
15. Accept the default values for the remaining properties on this page and click Next.
16. For optimal performance, enable the Data Integration Service modules that you plan to use.
The following table lists the Data Integration Service modules that you can enable:
Module Description
Web Service Module Runs web service operation mappings.
Mapping Service Module Runs mappings and previews.
Profiling Service Module Runs profiles and scorecards.
SQL Service Module Runs SQL queries from a third-party client tool to an SQL data service.
Workflow Orchestration Service Module Runs workflows.
17. Click Next.

You can configure the HTTP proxy server properties to redirect HTTP requests to the Data Integration
Service. You can configure the HTTP configuration properties to filter the web services client machines
that can send requests to the Data Integration Service. You can configure these properties after you
create the service.
18. Accept the default values for the HTTP proxy server and HTTP configuration properties and click Next.
The Data Integration Service uses the result set cache properties to use cached results for SQL data
service queries and web service requests. You can configure the properties after you create the service.
19. Accept the default values for the result set cache properties and click Next.
20. If you created the profiling warehouse database for the Data Integration Service, select the Profiling
Service module.
21. If you created the workflow database for the Data Integration Service, select the Workflow Orchestration
Service module.

22. Verify that the remaining modules are not selected.
You can configure properties for the remaining modules after you create the service.
23. Click Next.
24. If you created the profiling warehouse database for the Data Integration Service, click Select to select
the database connection. Select the profiling warehouse connection that you created for the service to
access the database.
25. Select whether or not content exists in the profiling warehouse database.
If you created a new profiling warehouse database, select No content exists under specified connection
string.
26. Click Next.
27. Accept the default values for the advanced profiling properties and click Next.
28. If you created the workflow database for the Data Integration Service, click Select to select the database
connection. Select the workflow database connection that you created for the service to access the
database.
29. Click Finish.
The domain creates and enables the Data Integration Service.
After You Create the Data Integration Service

After you create the Data Integration Service, perform the following tasks:
• Verify the host file configuration.

Verify the Host File Configuration

If you configured the Data Integration Service on UNIX or Linux to launch jobs as separate processes, verify
that the host file on the node that runs the service contains a localhost entry. Otherwise, jobs fail when the
Launch Jobs as Separate Processes property for the Data Integration Service is enabled.

After you create the Data Integration Service, create the application services that depend on the Data
Create the dependent services in the following order:
1. Analyst Service
2. Content Management Service
3. Search Service
Create and Configure the Data Integration Service 209

Create and Configure the PowerCenter Repository
Service
The PowerCenter Repository Service is an application service that manages the PowerCenter repository. The
PowerCenter repository stores metadata created by the PowerCenter Client and application services in a
relational database.
When you access a PowerCenter repository object from the PowerCenter Client or the PowerCenter
Integration Service, the client or service sends a request to the PowerCenter Repository Service. The
PowerCenter Repository Service process fetches, inserts, and updates metadata in the PowerCenter
repository database tables.
Create the PowerCenter Repository Service


2. Click Actions > New > PowerCenter Repository Service.
The New PowerCenter Repository Service dialog box appears.
3. On the New PowerCenter Repository Service - Step 1 of 2 page, enter the following properties:
Name Name of the service. The name is not case sensitive and must be unique within the domain.
It cannot exceed 128 characters or begin with @. It also cannot contain spaces or the
following special characters:
`~%^*+={}\;:'"/?.,<>|!()][
Primary Node If your license includes high availability, node on which the service runs by default. Required
if you select a license that includes high availability.
4. Click Next.
The New PowerCenter Repository Service - Step 2 of 2 page appears.

5. Enter the following properties for the PowerCenter repository database:
Username The database user name for the repository.
Password Password for the PowerCenter repository database user. Must be in 7-bit ASCII.
Connection String Native connection string the PowerCenter Repository Service uses to access the repository
database. Use the following native connect string syntax for each supported database:
- servername@databasename for Microsoft SQL Server and Sybase.
- databasename.world for Oracle.
- databasename for IBM DB2.
Code Page Repository database code page. The PowerCenter Repository Service uses the character set
encoded in the database code page to write data.
You cannot change the code page in the PowerCenter Repository Service properties after
you create the PowerCenter Repository Service.
Tablespace Name Name of the tablespace in which to create all the repository database tables. You cannot
use spaces in the tablespace name.
Available for IBM DB2 and Sybase databases.
To improve repository performance on IBM DB2 EEE repositories, specify a tablespace
name with one node.
6. Select No content exists under specified connection string. Create new content.
7. Optionally, choose to create a global repository.
After you create the service, you can promote a local repository to a global repository, but you cannot
change a global repository to a local repository.
8. If your license has the team-based development option, you can optionally enable version control of the
repository.
After you create the service, you can convert a non-versioned repository to a versioned repository, but
you cannot convert a versioned repository to a non-versioned repository.
9. Click Finish.
The domain creates the PowerCenter Repository Service, starts the service, and creates content for the
PowerCenter repository.
After You Create the PowerCenter Repository Service

After you create the PowerCenter Repository Service, perform the following tasks:
• Configure the PowerCenter Repository Service to run in the Normal mode.

• Create the PowerCenter repository user if the domain does not use Kerberos authentication.
Create and Configure the PowerCenter Repository Service 211

Run the PowerCenter Repository Service in Normal Mode
After you create the PowerCenter Repository Service, it starts in exclusive mode and access is restricted to
the administrator. Edit the service properties to run the service in normal operating mode to provide access
to other users.

2. In the Navigator, select the PowerCenter Repository Service.
3. Click Properties.
4. Click Edit Repository Properties.
5. In the Operating Mode field, select Normal.
6. Click OK.
You must recycle the PowerCenter Repository Service for the changes to take effect.
7. Select Actions > Recycle Service.
Create the PowerCenter Repository User

If the domain does not use Kerberos authentication, the domain uses a user account to authenticate other
application services that make requests to the PowerCenter Repository Service. You must create a user
account and assign the user the Administrator role for the PowerCenter Repository Service.
When you create an application service that depends on the PowerCenter Repository Service, you provide the
name of the PowerCenter Repository Service and of this PowerCenter repository user.
1. In the Administrator tool, click the Security tab.

2. On the Security Actions menu, click Create User to create a native user account.
Note: If you set up LDAP authentication in the domain, you can use an LDAP user account for the
PowerCenter repository user.
3. Enter the following properties for the user:
Login Name Login name for the user account. The login name for a user account must be unique
within the security domain to which it belongs.
The name is not case sensitive and cannot exceed 128 characters. It 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. All
other space characters are not allowed.
Password Password for the user account. The password can be from 1 through 80 characters long.
Confirm Password Enter the password again to confirm. You must retype the password. Do not copy and
paste the password.

Full Name Full name for the user account. The full name cannot include the following special
characters:
<>“
Description Description of the user account. The description cannot exceed 765 characters or include
the following special characters:
<>“
4. Click OK.
The user properties appear.
5. Click the Privileges tab.
6. Click Edit.
The Edit Roles and Privileges dialog box appears.
7. On the Roles tab, expand the PowerCenter Repository Service.
8. Under System Defined Roles, select Administrator and click OK.

After you create the PowerCenter Repository Service, create the application services that depend on the
PowerCenter Repository Service.
You can create the following application services:
1. PowerCenter Integration Service

2. Metadata Manager Service
3. Web Services Hub Service
Create and Configure the PowerCenter Integration

Service
The PowerCenter Integration Service is an application service that runs workflows and sessions for the
PowerCenter Client.
When you run a workflow in the PowerCenter Client, the client sends the requests to the PowerCenter
Integration Service. The PowerCenter Integration Service connects to the PowerCenter Repository Service to
fetch metadata from the PowerCenter repository, and then runs and monitors the sessions and workflows.
Create the PowerCenter Integration Service

Before you create the PowerCenter Integration Service, verify that you created the following service:
Create and Configure the PowerCenter Integration Service 213

2. Click Actions > New > PowerCenter Integration Service.
The New PowerCenter Integration Service dialog box appears.
3. On the New PowerCenter Integration Service - Step 1 of 2 page, enter the following properties:
`~%^*+={}\;:'"/?.,<>|!()][
Assign Select Node to configure the service to run on a node. If your license includes grid, you can
create a grid and assign the service to run on the grid after you create the service.
Primary Node If your license includes high availability, node on which the service runs by default. Required
if you select a license that includes high availability.
4. Click Next.
5. On the New PowerCenter Integration Service - Step 2 of 2 page, enter the following properties:
PowerCenter Repository PowerCenter Repository Service you want to associate with the service.
Service
Username User name that the service uses to access the PowerCenter Repository Service.
Enter the PowerCenter repository user that you created. Required when you
associate a PowerCenter Repository Service with the service.
Not available for a domain with Kerberos authentication.
Password Password associated with the PowerCenter repository user.

Security Domain LDAP security domain for the PowerCenter repository user. The Security Domain
field appears when the Informatica domain contains an LDAP security domain.
Required when you associate a PowerCenter Repository Service with the service.
6. Select the data movement mode that determines how the PowerCenter Integration Service handles
character data. Choose ASCII or Unicode. Default is ASCII.

In ASCII mode, the PowerCenter Integration Service recognizes 7-bit ASCII and EBCDIC characters and
stores each character in a single byte. In Unicode mode, the PowerCenter Integration Service recognizes
multibyte character sets as defined by the supported code pages. Use Unicode mode when the sources
or targets use 8-bit or multibyte character sets and contain character data.
7. Click Finish.
8. On the Specify Code Pages dialog box, assign a code page for the PowerCenter Integration Service.
The code page for the PowerCenter Integration Service must be compatible with the code page of the
associated repository.
9. Click OK.
The domain creates the PowerCenter Integration Service. The domain does not enable the PowerCenter
Integration Service during the service creation process.
10. To enable the PowerCenter Integration Service, select the service in the Navigator, and click Actions >
Enable Service. The PowerCenter Repository Service must be running to enable the PowerCenter
After You Create the PowerCenter Integration Service

After you create the PowerCenter Integration Service, create the Metadata Manager Service that depends on
the PowerCenter Integration Service.
Create and Configure the Metadata Manager Service

The Metadata Manager Service is an application service that runs the Metadata Manager web client in the
Informatica domain. The Metadata Manager Service manages the connections between service components
and the users that have access to Metadata Manager.
When you load metadata into the Metadata Manager warehouse, the Metadata Manager Service connects to
the PowerCenter Integration Service. The PowerCenter Integration Service runs workflows in the PowerCenter
repository to read from metadata sources and load metadata into the Metadata Manager warehouse. When
you use Metadata Manager to browse and analyze metadata, the Metadata Manager Service accesses the
metadata from the Metadata Manager repository.
Create the Metadata Manager Service

Before you create the Metadata Manager Service, verify that you created and enabled the following services:


2. Click Actions > New > Metadata Manager Service.
The New Metadata Manager Service dialog box appears.
Create and Configure the Metadata Manager Service 215

3. On the New Metadata Manager Service - Step 1 of 3 page, enter the following properties:
Name Name of the service. The name is not case sensitive and must be unique within the
domain. It cannot exceed 128 characters or begin with @. It also cannot contain spaces
or the following special characters:
`~%^*+={}\;:'"/?.,<>|!()][
Location Domain and folder where the service is created. Click Browse to choose a different
folder. You can move the service after you create it.
4. Specify the following properties of the associated repository service:
Associated Integration Select the PowerCenter Integration Service used by Metadata Manager to load
Service metadata into the Metadata Manager warehouse.
Repository User Name User name that the service uses to access the PowerCenter Repository Service.
Enter the PowerCenter repository user that you created. Required when you
associate a PowerCenter Repository Service with the service.
Repository Password Password associated with the PowerCenter repository user.

Security Domain LDAP security domain for the PowerCenter repository user. The Security Domain
field appears when the Informatica domain contains an LDAP security domain.
Required when you associate a PowerCenter Repository Service with the service.
5. Click Next.
The New Metadata Manager Service - Step 2 of 3 page appears.
6. Enter the following database properties for the Metadata Manager repository:
Code Page Metadata Manager repository code page. The Metadata Manager Service and the Metadata
Manager application use the character set encoded in the repository code page when
writing data to the Metadata Manager repository.
You can enable the Metadata Manager Service only after you specify the code page.

Connect String Native connect string to the Metadata Manager repository database. The Metadata
Manager Service uses the connect string to create a connection object to the Metadata
Manager repository in the PowerCenter repository.
Use the following native connect string syntax for each supported database:
- servername@databasename for Microsoft SQL Server.
- databasename.world for Oracle.
- databasename for IBM DB2.
Database User The database user name for the repository.
Database Password for the Metadata Manager repository database user. Must be in 7-bit ASCII.
Password
Tablespace Name Name of the tablespace in which to create all the repository database tables. You cannot
use spaces in the tablespace name.
Available for IBM DB2 databases.
To improve repository performance on IBM DB2 EEE repositories, specify a tablespace
name with one node.
Database The name of the machine that hosts the database server.
Hostname
Database Port The port number on which you configure the database server listener service.
SID/Service Name For Oracle databases. Indicates whether to use the SID or service name in the JDBC
connection string. For Oracle RAC databases, select from Oracle SID or Oracle service
name. For other Oracle databases, select Oracle SID.
Database Name The name of the database server.

Specify the full service name or SID for Oracle databases, service name for IBM DB2
databases, and database name for Microsoft SQL Server databases.
7. If you want to append parameters to the database connection URL, configure additional parameters in
the Additional JDBC Parameters field. Enter the parameters as name=value pairs separated by
semicolon characters (;). For example: param1=value1;param2=value2

You can use this property to specify the following parameters:
Backup server If you use a database server that is highly available such as Oracle RAC, enter the
location location of a backup server.
Oracle Advanced If the Metadata Manager repository database is an Oracle database that uses ASO, enter
Security Option the following additional parameters:
(ASO) parameters
EncryptionLevel=[encryption level];EncryptionTypes=[encryption
types];DataIntegrityLevel=[data integrity
level];DataIntegrityTypes=[data integrity types]
Note: The parameter values must match the values in the sqlnet.ora file on the
machine where the Metadata Manager Service runs.
Authentication To authenticate the user credentials with Windows authentication and establish a trusted
information for connection to a Microsoft SQL Server repository, enter the following text:
Microsoft SQL
AuthenticationMethod=ntlm;LoadLibraryPath=[directory containing
Server DDJDBCx64Auth04.dll].
jdbc:informatica:sqlserver://[host]:[port];DatabaseName=[DB name];
AuthenticationMethod=ntlm;LoadLibraryPath=[directory containing
DDJDBCx64Auth04.dll]
When you use a trusted connection to connect to a Microsoft SQL Server database, the
Metadata Manager Service connects to the repository with the credentials of the user
logged in to the machine on which the service is running.
To start the Metadata Manager Service as a Windows service with a trusted connection,
configure the Windows service properties to log on with a trusted user account.
8. If the Metadata Manager repository database is configured for secure communication, you can configure
additional JDBC parameters in the Secure JDBC Parameters field.
Use this property to specify secure connection parameters such as passwords. The Administrator tool
does not display secure parameters or parameter values in the Metadata Manager Service properties.
Enter the parameters as name=value pairs separated by semicolon characters (;). For example:
param1=value1;param2=value2.
Enter the following secure database parameters:
Secure Database Parameter Description
EncryptionMethod Required. Indicates whether data is encrypted when transmitted over the
network. This parameter must be set to SSL.
TrustStore Required. Path and file name of the truststore file that contains the SSL
certificate of the database server.
TrustStorePassword Required. Password used to access the truststore file.
HostNameInCertificate Host name of the machine that hosts the secure database. If you specify a host
name, the Metadata Manager Service validates the host name included in the
connection string against the host name in the SSL certificate.

Secure Database Parameter Description
ValidateServerCertificate Optional. Indicates whether Informatica validates the certificate that the
database server sends.
If this parameter is set to True, Informatica validates the certificate that the
database server sends. If you specify the HostNameInCertificate parameter,
Informatica also validates the host name in the certificate.
If this parameter is set to False, Informatica does not validate the certificate
that the database server sends. Informatica ignores any truststore information
that you specify.
KeyStore Path and file name of the keystore file that contains the SSL certificates that
the Metadata Manager Service sends to the database server.
KeyStorePassword Password used to access the keystore file.
9. Click Next.
The New Metadata Manager Service - Step 3 of 3 page appears.
10. Enter the HTTP port number to use for the service.
11. To enable secure communications with the Metadata Manager Service, select Enable Secured Socket
Layer.
Enter the following properties to configure secure communication for the service:
HTTPS Port Port number to use for a secure connection to the service. Use a different port number
than the HTTP port number.
Keystore File Path and file name of the keystore file that contains the private or public key pairs and
associated certificates. Required if you use HTTPS connections for the service.
Keystore Password Plain-text password for the keystore file.
12. Click Finish.

The domain creates the Metadata Manager Service. The domain does not enable the Metadata Manager
Service during the service creation process.
13. To enable the Metadata Manager Service, select the service in the Navigator and click Actions > Enable
Service. The PowerCenter Repository Service and PowerCenter Integration Service must be running to
enable the Metadata Manager Service.
After You Create the Metadata Manager Service

After you create the Metadata Manager Service, perform the following tasks:
• Create the contents for the Metadata Manager repository.


When you create the Metadata Manager Service, you create the repository tables and import models for
metadata sources.
1. In the Navigator, select the Metadata Manager Service.

2. Click Actions > Repository Contents > Create.
3. Click OK.
After you create the Metadata Manager Service, create the application services that depend on the Metadata
Manager Service.
Create and Configure the Content Management

Service
The Content Management Service is an application service that manages reference data. A reference data
object contains a set of data values that you can search while performing data quality operations on source
data. The Content Management Service also compiles rule specifications into mapplets. A rule specification
object describes the data requirements of a business rule in logical terms.
The Content Management Service uses the Data Integration Service to run mappings to transfer data
between reference tables and external data sources. The Content Management Service also provides
transformations, mapping specifications, and rule specifications with the following types of reference data:
• Address reference data

• Identity populations
• Probabilistic models and classifier models
• Reference tables
Create the Content Management Service

Before you create the Content Management Service, verify that you have created and enabled the following
services:


2. Click Actions > New > Content Management Service.
The New Content Management Service dialog box appears.

3. On the New Content Management Service - Step 1 of 2 page, enter the following properties:
`~%^*+={}\;:'"/?.,<>|!()][
HTTP Port HTTP port number to use for the Content Management Service.
Data Integration Data Integration Service to associate with the service. The Data Integration Service and the
Service Content Management Service must run on the same node.
Model Repository Model Repository Service to associate with the service.

Service
Username User name that the service uses to access the Model Repository Service. Enter the Model
Security Domain LDAP security domain for the Model repository user. The field appears when the Informatica
domain contains an LDAP security domain. Not available for a domain with Kerberos
authentication.
Reference Data Reference data warehouse connection that you created for the Content Management Service
Location to access the reference data warehouse. Click Select to select the connection.
4. Click Next.
The New Content Management Service - Step 2 of 2 page appears.
5. Accept the default values for the security properties.
The Model Repository Service and Data Integration Service must be running to enable the Content
Management Service.
7. Click Finish.
The domain creates and enables the Content Management Service.
Create and Configure the Content Management Service 221

Create and Configure the Analyst Service
The Analyst Service is an application service that runs the Analyst tool in the Informatica domain. The
Analyst Service manages the connections between service components and the users that have access to
the Analyst tool.
Create the Analyst Service

Before you create the Analyst Service, verify that you have created and enabled the following services:


2. Click Actions > New > Analyst Service.
The New Analyst Service dialog box appears.
3. On the New Analyst Service - Step 1 of 6 page, enter the following properties:
special characters:
`~%^*+={}\;:'"/?.,<>|!()][
Location Domain and folder where the service is created. Click Browse to choose a different folder. You can
move the service after you create it.
4. Click Next.
The New Analyst Service - Step 2 of 6 page appears.
5. Enter the HTTP port number to use for communication from the Analyst tool to the Analyst Service.
6. To enable secure communication from the Analyst tool to the Analyst Service, select Enable Secure
Communication.

Enter the following properties to configure secure communication for the Analyst Service:
HTTPS Port Port number that the Analyst tool runs on when you enable secure communication. Use a
different port number than the HTTP port number.
Keystore File Directory where the keystore file that contains the digital certificates is stored.
Keystore Plain-text password for the keystore file. If this property is not set, the Analyst Service
Password uses the default password changeit.
SSL Protocol Optional. Indicates the protocol to be used. Set this property to SSL.

The Model Repository Service and the Data Integration Service must be running to enable the Analyst
Service.
8. Click Next.
9. Enter the following properties to associate the Model Repository Service with the Analyst Service:
Description Property

Service
User name User name that the service uses to access the Model Repository Service. Enter the
Model repository user that you created.
Security Domain LDAP security domain for the Model repository user. The field appears when the
Informatica domain contains an LDAP security domain. Not available for a domain with
10. To enable Analyst tool users to work on Human task data, set the Data Integration Service property to
the Data Integration Service that you configure to run workflows.
If Analyst tool users do not need to work on Human task records, do not configure this property.
11. Click Next.
Create and Configure the Analyst Service 223

12. Enter the following run-time properties for the Analyst Service:
Data Data Integration Service to associate with the service. The Analyst Service manages the
Integration connection to the Data Integration Service that enables users to perform data preview,
Service mapping specification, scorecard, and profile jobs in the Analyst tool.
You can associate the Analyst Service with the Data Integration Service that you configured to
run workflows. Or, you can associate the Analyst Service with different Data Integration
Services for the different operations.
Flat File Cache Directory of the flat file cache where the Analyst tool stores uploaded flat files. The Data
Directory Integration Service must also be able to access this directory. If the Analyst Service and the
Data Integration Service run on different nodes, configure the flat file directory to use a
shared directory.
13. Click Next.

14. Enter the directory to store the temporary business glossary files that the business glossary export
process creates and the directory to store files that content managers attach to the Glossary assets.
These directories must be on the node that runs the Analyst Service.
15. Click Finish.
The domain creates and enables the Analyst Service.
After You Create the Analyst Service

After you create the Analyst Service, create the Search Service that depends on the Analyst Service.
Create and Configure the Search Service

The Search Service performs searches in the Analyst tool. It returns search results from the profiling
warehouse and the Model repository, including data objects, mapping specifications, and scorecards
By default, the Search Service returns search results from a Model repository, such as data objects, mapping
specifications, profiles, reference tables, rules, scorecards, and business glossary terms. The search results
can also include column profile results and domain discovery results from a profiling warehouse.
Create the Search Service

Before you create the Search Service, verify that you have created and enabled the following services:

Analyst Service

2. Click Actions > New > Search Service.
The New Search Service dialog box appears.
3. On the New Search Service - Step 1 of 2 page, enter the following properties:
special characters:
`~%^*+={}\;:'"/?.,<>|!()][
Location Domain and folder where the service is created. Click Browse to choose a different folder. You can
move the service after you create it.
4. Click Next.
The New Search Service - Step 2 of 2 page appears.
5. Enter the following search properties for the Search Service:
Description Property
Port Number Port number to use for the Search Service.
Index Location Directory that contains the search index files. Enter a directory on the machine that runs
the Search Service. If the directory does not exist, Informatica creates the directory when
it creates the Search Service.
Extraction Interval Interval in seconds at which the Search Service extracts and indexes updated content.
Default is 60 seconds.

Service
User Name User name that the service uses to access the Model Repository Service. Enter the Model
Security Domain LDAP security domain for the Model repository user. The field appears when the
Informatica domain contains an LDAP security domain. Not available for a domain with
6. Click Finish.
The domain creates the Search Service. The domain does not enable the Search Service during the
creation process. You must enable the Search Service before users can perform searches in the Analyst
tool and Business Glossary Desktop.
Create and Configure the Search Service 225

7. To enable the Search Service, select the service in the Navigator, and then click Actions > Enable
Service.
The Model Repository Service, Data Integration Service, and Analyst Service must be running to enable
the Search Service.

Part V: Informatica Client
Installation
• Install the Clients, 228

• Install in Silent Mode , 235
227
Chapter 15
Install the Clients

• Install the Clients Overview, 228

• Before You Install, 229
• Install the Clients, 230
• After You Install, 231
• Starting the PowerCenter Client, 232
• Starting the Developer Tool, 233
Install the Clients Overview

You can install the Informatica clients on Windows in graphical or silent mode.
Complete the pre-installation tasks to prepare for the installation. You can install the Informatica clients on
multiple machines.
When you run the client installer, you can select the following Informatica client tools:
Informatica Developer
Informatica Developer is a client application that you use to create data objects, create and run
mappings, and create virtual databases.
PowerCenter Client
The PowerCenter Client is a set of tools you can use to manage the PowerCenter repository, mappings,
and sessions.
Note: Informatica recommends that you install the Informatica services and the PowerCenter Client in
different install directories. If you install the Informatica services and the PowerCenter Client in the same
install directory, the service binaries will be uninstalled when you uninstall the PowerCenter Client.
228
Before You Install
Before you install the Informatica clients on Windows, verify that the minimum system and third-party
software requirements are met. If the machine where you install the Informatica clients is not configured
correctly, the installation can fail.

Before you install the client, verify the following installation requirements to install and run the client are met:
Permissions to install
Verify that the user account that you use to install the client has write permission on the installation
directory and Windows registry.
Minimum system requirements
The following table lists the minimum system requirements to run the client:
Processor RAM Disk Space
1 CPU 1GB 6 GB
Verify Third-party Requirements for Informatica Developer

If you plan to use Data Processor or Hierarchical-To-Relational transformations, install .NET Framework 4.0
or later before you install the Developer tool.
Verify Third-party Requirements for the PowerCenter Client

The PowerCenter Client installation includes Mapping Architect for Visio and Mapping Analyst for Excel.
Verify third-party requirements for both Mapping Architect for Visio and Mapping Analyst for Excel before you
install the PowerCenter Client.
Verify Third-party Requirements for Mapping Architect for Visio

If you plan to use Mapping Architect for Visio, install the following third-party software before you install the
PowerCenter Client:
• Microsoft Visio version 2007 or 2010

• Microsoft .NET Framework 3.5.1
• Microsoft .NET Framework 4.0
Important: If you do not install the correct version and service pack level of Microsoft .NET Framework,
Mapping Architect for Visio will not install properly.
Before You Install 229

Verify Third-party Requirements for Mapping Analyst for Excel
Mapping Analyst for Excel includes an Excel add-in that adds a Metadata menu or ribbon to Microsoft Excel.
You can install the add-in only for Excel 2016. If you plan to use Mapping Analyst for Excel, install the
following third-party software before you install the PowerCenter Client:
• Microsoft Office Excel version 2016

• Java version 1.8 or later
Install the Clients

Perform the following steps to install the client tool:

If you encounter problems when you run the install.bat file from the root directory, run the following file:
<installer files directory>\client\install.exe
3. Select Install Informatica <Version> Clients and click Next.
a. Press 1 if you do not want to accept the terms and conditions.
5. Version 10.4.0 is for installing Informatica 10.4.0 products.
a. Press 1 and type quit to quit the installation.
b. Press 2 to continue the installation.
If you choose to not accept the terms and condition, the installer prompts you to accept the terms and
conditions.
6. The Installation Pre-requisites page displays the system requirements. Verify that all installation
requirements are met before you continue the installation.
7. On the Installation Directory page, enter the absolute path for the installation directory.
The installation directory must be on the current computer. The maximum length of the path must be
less than 260 characters. The directory names in the path must not contain spaces or the following
special characters: @|* $ # ! % ( ) { } [ ] , ; '
8. Click Next.
9. On the Pre-Installation Summary page, review the installation information, and click Install.
The installer copies the Developer tool files to the installation directory.
The Post-installation Summary page indicates whether the installation completed successfully.
You can view the installation log files to get more information about the tasks performed by the installer.
230 Chapter 15: Install the Clients

After You Install
After you install the client tools, you can install other languages, enable secure communication within the
domain and start the tool.
Install Languages
To view languages other than the system locale and to work with repositories that use a UTF-8 code page,
install additional languages on Windows for use with the Informatica clients.
Note: If you installed the PowerCenter clients and performed this install languages task, you do not need to
repeat the task.
You also must install languages to use the Windows Input Method Editor (IME).
1. Click Start > Settings > Control Panel.

2. Click Regional Options.
3. Under Language settings for the system, select the languages you want to install.
4. Click Apply.
If you change the system locale when you install the language, restart the Windows machine.
Configure the Client for a Secure Domain

When you enable secure communication within the domain, you also secure connections between the domain
and Informatica client applications. Based on the truststore files used, you might need to specify the location
and password for the truststore files in environment variables on each client host.
You might need to set the following environment variables on each client host:
INFA_TRUSTSTORE
Set this variable to the directory that contains the truststore files for the SSL certificates. The directory
must contain truststore files named infa_truststore.jks and infa_truststore.pem.
Set this variable to the password for the infa_truststore.jks file. The password must be encrypted.
Use the command line program pmpasswd to encrypt the password.
Informatica provides an SSL certificate that you can use to secure the domain. When you install the
Informatica clients, the installer sets the environment variables and installs the truststore files in the
following directory by default: <Informatica installation directory>\clients\shared\security
If you use the default Informatica SSL certificate, and the infa_truststore.jks and infa_truststore.pem
are in the default directory, you do not need to set the INFA_TRUSTSTORE or INFA_TRUSTSTORE_PASSWORD
environment variables.
You must set the INFA_TRUSTSTORE and INFA_TRUSTSTORE_PASSWORD environment variables on each
client host in the following scenarios:
You use a custom SSL certificate to secure the domain.
If you provide an SSL certificate to use to secure the domain, copy the infa_truststore.jks and
infa_truststore.pem truststore files to each client host. You must specify the location of the files and
the truststore password.
After You Install 231

You use the default Informatica SSL certificate, but the truststore files are not in the default Informatica directory.
If you use the default Informatica SSL certificate, but the infa_truststore.jks and
infa_truststore.pem truststore files are not in the default Informatica directory, you must specify the
location of the files and the truststore password.
Configure the Developer Tool Workspace Directory

Configure Informatica Developer to write the workspace metadata to the machine where the user is logged
in.
Note: If you have installed the PowerCenter clients and performed this task, you do not need to repeat this
task.
1. Go to the following directory: <Informatica installation directory>\clients\DeveloperClient

\configuration\
2. Locate the config.ini file.
3. Create a backup copy of the config.ini file.
4. Use a text editor to open the config.ini file.
5. Add the osgi.instance.area.default variable to the end of the config.ini file and set the variable to the
directory location where you want to save the workspace metadata. The file path cannot contain non-
ANSI characters. Folder names in the workspace directory cannot contain the number sign (#) character.
If folder names in the workspace directory contain spaces, enclose the full directory in double quotes.
• If you run Informatica Developer from the local machine, set the variable to the absolute path of the
workspace directory:
osgi.instance.area.default=<Drive>/<WorkspaceDirectory>
or
osgi.instance.area.default=<Drive>\\<WorkspaceDirectory>
• If you run Informatica Developer from a remote machine, set the variable to the directory location on
the local machine:
osgi.instance.area.default=\\\\<LocalMachine>/<WorkspaceDirectory>
or
osgi.instance.area.default=\\\\<LocalMachine>\\<WorkspaceDirectory>
The user must have write permission to the local workspace directory.
Informatica Developer writes the workspace metadata to the workspace directory. If you log into Informatica
Developer from a local machine, Informatica Developer writes the workspace metadata to the local machine.
If the workspace directory does not exist on the machine from which you logged in, Informatica Developer
creates the directory when it writes the files.
You can override the workspace directory when you start Informatica Developer.
Starting the PowerCenter Client

When you start PowerCenter Client, you connect to a PowerCenter repository.
1. From the Windows Start menu, click Programs > Informatica[Version] > Client > [Client Tool Name].
The first time you run a PowerCenter Client tool, you must add a repository and connect to it.

2. Click Repository > Add Repository.
The Add Repository dialog box appears.
3. Enter the repository and user name.
4. Click OK.
The repository appears in the Navigator.
5. Click Repository > Connect.
The Connect to Repository dialog box appears.
6. In the connection settings section, click Add to add the domain connection information.
The Add Domain dialog box appears.
7. Enter the domain name, gateway host, and gateway port number.
8. Click OK.
9. In the Connect to Repository dialog box, enter the password for the Administrator user.
10. Select the security domain.
11. Click Connect.
After you connect to the repository, you can create objects.
Starting the Developer Tool

When you start the Developer tool, you connect to a Model repository. The Model repository stores metadata
created in the Developer tool. The Model Repository Service manages the Model repository. Connect to the
repository before you create a project.
1. From the Windows Start menu, click Programs > Informatica[Version] > Client > Developer Client >
Launch Informatica Developer.
The first time you run the Developer tool, the Welcome page displays several icons. The Welcome page
does not appear when you run the Developer tool subsequently.
2. Click Workbench.
The first time you start the Developer tool, you must select the repository in which to save the objects
you create.
3. Click File > Connect to Repository.
The Connect to Repository dialog box appears.
4. If you have not configured a domain in the Developer tool, click Configure Domains to configure a
domain.
You must configure a domain to access a Model Repository Service.
5. Click Add to add a domain.
The New Domain dialog box appears.
6. Enter the domain name, host name, and port number.
7. Click Finish.
8. Click OK.
9. In the Connect to Repository dialog box, click Browse and select the Model Repository Service.
10. Click OK.
Starting the Developer Tool 233

11. Click Next.
12. Enter a user name and password.
13. Click Finish.
The Developer tool adds the Model repository to the Object Explorer view. When you run the Developer
tool the next time, you can connect to the same repository.

Chapter 16
Install in Silent Mode

• Overview of Install in Silent Mode, 235

• Configure the Properties File, 235
• Run the Silent Installer, 236
Overview of Install in Silent Mode

To install the Informatica clients without user interaction, install in silent mode.
Use a properties file to specify the installation options. The installer reads the file to determine the
installation options. You can use silent mode installation to install the Informatica clients on multiple
machines on the network or to standardize the installation across machines.
To install in silent mode, complete the following tasks:
1. Configure the installation properties file and specify the installation options in the properties file.
2. Run the installer with the installation properties file.
Configure the Properties File

Informatica provides a sample properties file that includes the properties required by the installer. Customize
the sample properties file to create a properties file and specify the options for your installation. Then run the
silent installation.
The sample SilentInput.properties file is stored in the installer download location.

2. Locate the sample SilentInput.properties file.
4. Use a text editor to open and modify the values of the properties in the file.
235
The following table describes the installation properties that you can modify:
Property Name Description
INSTALL_TYPE Indicates whether to install or upgrade the Informatica clients.

If the value is 0, the Informatica clients are installed in the
directory you specify. If the value is 1, the Informatica clients
are upgraded.
Default is 0.
USER_INSTALL_DIR Informatica client installation directory.
DXT_COMP Indicates whether to install Informatica Developer.

If the value is 1, the Developer tool will be installed. If the
value is 0, the Developer tool will not be installed.
Default is 1.
5. Save the properties file.
Run the Silent Installer

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

3. Verify that the directory contains the file SilentInput.properties that you edited and resaved.
4. To run the silent installation, run silentInstall.bat.
The silent installer runs in the background. The process can take a while. The silent installation is
complete when the Informatica_<Version>_Client_InstallLog<timestamp>.log file is created in the
installation directory.
The silent installation fails if you incorrectly configure the properties file or if the installation directory is
not accessible. View the installation log files and correct the errors. Then run the silent installation
again.
236 Chapter 16: Install in Silent Mode

Part VI: Uninstallation
This part contains the following chapter:
• Uninstallation, 238
237
Chapter 17
Uninstallation
• Informatica Uninstallation Overview, 238

• Rules and Guidelines for Uninstallation, 238
• Uninstalling the Informatica Server in Console Mode, 239
• Uninstalling Informatica Server in Silent Mode, 239
• Uninstalling the Informatica Server in Graphical Mode, 240
• Informatica Client Uninstallation, 240
Informatica Uninstallation Overview

Uninstall Informatica to remove the Informatica server or clients from a machine.
The Informatica uninstallation process deletes all Informatica files and clears all Informatica configurations
from a machine. The uninstallation process does not delete files that are not installed with Informatica. For
example, the installation process creates temporary directories. The uninstaller does not keep a record of
these directories and therefore cannot delete them. You must manually delete these directories for a clean
uninstallation.
Rules and Guidelines for Uninstallation

Use the following rules and guidelines when you uninstall Informatica components:
• The Informatica server uninstallation mode depends on the mode you use to install Informatica server.
For example, you install Informatica server in console mode. When you run the uninstaller, it runs in
console mode. The Informatica clients uninstallation mode does not depend on the mode you use to
install Informatica clients. For example, you install Informatica clients in silent mode. When you run the
uninstaller, it can run in graphical or silent mode.
• Uninstalling Informatica does not affect the Informatica repositories. The uninstaller removes the
Informatica files. It does not remove repositories from the database. If you need to move the repositories,
you can back them up and restore them to another database.
• Uninstalling Informatica does not remove the metadata tables from the domain configuration database. If
you install Informatica again using the same domain configuration database and user account, you must
manually remove the tables or choose to overwrite the tables. You can use the infasetup BackupDomain
238
command to back up the domain configuration database before you overwrite the metadata tables. To
remove the metadata tables manually, use the infasetup DeleteDomain command before you run the
uninstaller.
• Uninstalling Informatica removes all installation files and subdirectories from the Informatica installation
directory. Before you uninstall Informatica, stop all Informatica services and processes and verify that all
of the files in the installation directory are closed. At the end of the uninstallation process, the uninstaller
displays the names of the files and directories that could not be removed.
• The Informatica server installation creates the following folder for the files and libraries required by third
party adapters built using the Informatica Development Platform APIs:
<Informatica installation directory>/services/shared/extensions
Uninstalling the Informatica server deletes this folder and any subfolders created under it. If you have
adapter files stored in the /extensions folder, back up the folder before you start uninstallation.
• If you perform the uninstallation on a machine, you must back up the ODBC folder before you uninstall.
Restore the folder after the uninstallation completes.
Uninstalling the Informatica Server in Console Mode

If you installed the Informatica server in console mode, uninstall the Informatica server in console mode.
Before you run the uninstaller, stop all Informatica services and processes and verify that all files in the
installation directory are closed. The uninstallation process cannot remove files that are open or are being
used by a service or process that is running.
1. Go to the following directory:

<Informatica installation directory>/Uninstaller_Server
2. Type the following command to run the uninstaller:
./uninstaller
If you installed the Informatica server in console mode, the uninstaller launches in console mode.
Uninstalling Informatica Server in Silent Mode

If you installed the Informatica server in silent mode, uninstall the Informatica server in silent mode.
1. Go to the following directory:

<Informatica installation directory>/Uninstaller_Server
2. Type the following command to run the silent uninstaller:
./uninstaller.sh
If you installed the Informatica server in silent mode, the uninstaller launches in silent mode. The silent
uninstaller runs in the background. The process can take a while. The silent uninstallation fails if the
installation directory is not accessible.
Uninstalling the Informatica Server in Console Mode 239

After you uninstall the the Informatica server, delete any remaining folders and files from the Informatica
installation directory. For example:
• Informatica _<Version>_Services_InstallLog.log file

• Informatica_<Version>_Services_<timestamp>.log file
Uninstalling the Informatica Server in Graphical Mode

1. Click Start > Program Files > Informatica [Version] > Server > Uninstaller.
The Uninstallation page appears.
2. Click Uninstall to begin the uninstallation.
After the installer deletes all of the Informatica files from the directory, the Post-Uninstallation Summary
page appears.
3. Click Done to close the uninstaller.
After you uninstall the the Informatica server, delete any remaining folders and files from the Informatica
• Informatica _<Version>_Client_InstallLog.log file

• Informatica_<Version>_Client.log file
Log out of the machine and log back in. Then clear the Informatica-specific CLASSPATH and PATH
Informatica Client Uninstallation

You can uninstall the Informatica clients in graphical mode and silent mode on Windows.
When you uninstall Informatica clients, the installer does not remove the environment variables,
INFA_TRUSTSTORE, that it creates during installation. When you install a later version of Informatica clients,
you must edit the environment variable to point to the new value of the SSL certificate.
Uninstalling Informatica Clients in Graphical Mode

If you installed the Informatica clients in graphical mode, uninstall the Informatica clients in graphical mode.
1. Click Start > Program Files > Informatica [Version] > Client > Uninstaller.
The Uninstallation page appears.
2. Click Next.
The Application Client Uninstall Selection page appears.
3. Select the client applications you want to uninstall and click Uninstall.
240 Chapter 17: Uninstallation

4. Click Done to close the uninstaller.
After the uninstallation is complete, the Post-Uninstallation Summary page appears, displaying the
results of the uninstallation.
After you uninstall the Informatica clients, delete any remaining folders and files from the Informatica

Uninstalling Informatica Clients in Silent Mode

If you installed the Informatica clients in silent mode, uninstall the Informatica clients in silent mode.
Creating the Properties File

Informatica provides a sample properties file that includes the properties required by the installer.
Customize the sample properties file to create a properties file and specify the options for your
uninstallation. Then run the silent uninstallation.
1. Go to <Informatica installation directory>/Uninstaller_Client.

2. Locate the sample SilentInput.properties file.
4. Use a text editor to open and modify the values of the properties file.
The following table describes the properties that you can modify:
Property Name Description
DXT_COMP Indicates whether to uninstall Informatica Developer.

If the value is 1, the Developer tool will be uninstalled. If the value is 0, the Developer tool will
not be uninstalled.
Default is 1.
5. Save the SilentInput.properties file.
Running the Silent Uninstaller

After you configure the properties file, run the silent uninstallation.
1. Go to <Informatica installation directory>/Uninstaller_Client.

2. To run the silent installation, double-click the uninstaller.bat or uninstaller.exe file.
The silent uninstaller runs in the background. The process can take a while. The silent uninstallation fails
if you incorrectly configure the properties file or if the installation directory is not accessible.
After you uninstall the Informatica clients, delete any remaining folders and files from the Informatica
Informatica Client Uninstallation 241

242 Chapter 17: Uninstallation

Appendix A
Starting and Stopping Informatica

Services
This appendix includes the following topics:
• Starting and Stopping Informatica Services Overview , 243

• Starting and Stopping the Informatica Services from the Console, 243
• Stopping Informatica in Informatica Administrator, 244
• Starting or Stopping Informatica from the Control Panel, 244
• Starting or Stopping Informatica from the Start Menu, 244
• Starting or Stopping Informatica from a Command Prompt, 245
• Rules and Guidelines for Starting or Stopping Informatica, 245
Starting and Stopping Informatica Services Overview

The Informatica service runs the Service Manager on the node. The Service Manager manages all domain
functions and starts application services configured to run on the node. The method you use to start or stop
Informatica depends on the operating system. You can use Informatica Administrator to shut down a node.
When you shut down a node, you stop Informatica on the node.
The Informatica service also runs Informatica Administrator. You use Informatica Administrator to
administer the Informatica domain objects and user accounts. Log in to Informatica Administrator to create
the user accounts for users of Informatica and to create and configure the application services in the
domain.
Starting and Stopping the Informatica Services from

the Console
Run infaservice.sh to start and stop the Informatica daemon. By default, infaservice.sh is installed in the
following directory:
<Informatica installation directory>/tomcat/bin
1. Go to the directory where infaservice.sh is located.
243
2. At the command prompt, enter the following command to start the daemon:
infaservice.sh startup
Enter the following command to stop the daemon:
infaservice.sh shutdown
Note: If you use a softlink to specify the location of infaservice.sh, set the INFA_HOME environment
variable to the location of the Informatica installation directory.
Stopping Informatica in Informatica Administrator

When you shut down a node using Informatica Administrator, you stop the Informatica service on that node.
You can abort the processes that are running or allow them to complete before the service shuts down. If you
shut down a node and abort the repository service processes running on the node, you can lose changes that
have not yet been written to the repository. If you abort a node running integration service processes, the
workflows will abort.
1. Log in to Informatica Administrator.

2. In the Navigator, select the node to shut down.
3. On the Domain tab Actions menu, select Shutdown Node.
Starting or Stopping Informatica from the Control

Panel
The procedure to start or stop the Informatica Windows service is the same as for all other Windows
services.
1. Open the Windows Control Panel.

2. Select Administrative Tools.
3. Right-click Services and select Run as Administrator.
4. Right-click the Informatica service.
5. If the service is running, click Stop.
If the service is stopped, click Start.
Starting or Stopping Informatica from the Start Menu

To start Informatica from the Windows Start menu, click Programs > Informatica[Version] > Server. Right-
click Start Informatica Services and select Run as Administrator.
To stop Informatica from the Windows Start menu, click Programs > Informatica[Version] > Server. Right-
click Stop Informatica Services and select Run as Administrator.
244 Appendix A: Starting and Stopping Informatica Services

Starting or Stopping Informatica from a Command
Prompt
You can run infaservice.bat from the command line to start and stop the Informatica services on Windows.
By default, infaservice.bat is installed in the following directory:
<Informatica installation directory>\tomcat\bin
1. Open a command prompt as administrator.

2. Go to the directory where infaservice.bat is located.
3. Enter the following command to start the Informatica services:
infaservice.bat startup
Enter the following command to stop the Informatica services:
infaservice.bat shutdown
Rules and Guidelines for Starting or Stopping

Informatica
Consider the following rules and guidelines when starting and stopping Informatica on a node:
• When you shut down a node, the node is unavailable to the domain. If you shut down a gateway node and
do not have another gateway node in the domain, the domain is unavailable.
• When you start Informatica, verify that the port used by the service on the node is available. For example,
if you stop Informatica on a node, verify that the port is not used by any other process on the machine
before you restart Informatica. If the port is not available, Informatica will fail to start.
• If you do not use Informatica Administrator to shut down a node, any process running on the node will be
aborted. If you want to wait for all processes to complete before shutting down a node, use Informatica
Administrator.
• If you have two nodes in a domain with one node configured as a primary node for an application service
and the other node configured as a backup node, start Informatica on the primary node before you start
the backup node. Otherwise, the application service will run on the backup node and not the primary node.
Starting or Stopping Informatica from a Command Prompt 245

Appendix B
Connecting to Databases from

UNIX or Linux
• Connecting to Databases from UNIX or Linux Overview, 246

• Connecting to an IBM DB2 Universal Database, 247
• Connecting to an Informix Database, 249
• Connecting to a Microsoft SQL Server Database, 250
• Connecting to a Netezza Database, 251
• Connecting to an Oracle Database, 253
• Connecting to a PostgreSQL Database, 255
• Connecting to a Sybase ASE Database, 257
• Connecting to a Teradata Database, 259
• Connecting to a JDBC Data Source, 261
• Connecting to an ODBC Data Source, 262
• Sample odbc.ini File, 264
Connecting to Databases from UNIX or Linux

Overview
To use native connectivity, you must install and configure the database client software for the database that
you want to access. 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. To
increase performance, use native connectivity.
The Informatica installation includes DataDirect ODBC drivers. If you have existing ODBC data sources
created with an earlier version of the drivers, you must create new ODBC data sources using the new drivers.
Configure ODBC connections using the DataDirect ODBC drivers provided by Informatica or third party ODBC
drivers that are Level 2 compliant or higher.
You must configure a database connection for the following services in the Informatica domain:
• PowerCenter Repository Service

• Model Repository Service
246
• Data Integration Service
• Analyst Service
When you connect to databases from Linux or UNIX, use native drivers to connect to IBM DB2, Oracle, or
Sybase ASE databases. You can use ODBC to connect to other sources and targets.
Connecting to an IBM DB2 Universal Database

For native connectivity, install the version of IBM DB2 Client Application Enabler (CAE) appropriate for the
IBM DB2 database server version. To ensure compatibility between Informatica and databases, use the
appropriate database client libraries.
Configuring Native Connectivity

You can configure native connectivity to an IBM DB2 database to increase performance.
The following steps provide a guideline for configuring native connectivity. For specific instructions, see the
database documentation.
1. To configure connectivity on the machine where the Data Integration Service, PowerCenter Integration
Service, or PowerCenter Repository Service process runs, log in to the machine as a user who can start a
service process.
2. Set the DB2INSTANCE, INSTHOME, DB2DIR, and PATH environment variables.
The UNIX IBM DB2 software always has an associated user login, often db2admin, which serves as a
holder for database configurations. This user holds the instance for DB2.
DB2INSTANCE. The name of the instance holder.
Using a Bourne shell:
$ DB2INSTANCE=db2admin; export DB2INSTANCE
Using a C shell:
$ setenv DB2INSTANCE db2admin
INSTHOME. This is db2admin home directory path.
$ INSTHOME=~db2admin
Using a C shell:
$ setenv INSTHOME ~db2admin>
DB2DIR. Set the variable to point to the IBM DB2 CAE installation directory. For example, if the client is
installed in the /opt/IBM/db2/V9.7 directory:
$ DB2DIR=/opt/IBM/db2/V9.7; export DB2DIR
Using a C shell:
$ setenv DB2DIR /opt/IBM/db2/V9.7
PATH. To run the IBM DB2 command line programs, set the variable to include the DB2 bin directory.
$ PATH=${PATH}:$DB2DIR/bin; export PATH
Connecting to an IBM DB2 Universal Database 247

Using a C shell:
$ setenv PATH ${PATH}:$DB2DIR/bin
3. Set the shared library variable to include the DB2 lib directory.
The IBM DB2 client software contains a number of shared library components that the Data Integration
Service, PowerCenter Integration Service, and PowerCenter Repository Service processes load
dynamically. Set the shared library environment variable so that the services can find the shared libraries
at run time.
The shared library path must also include the Informatica installation directory (server_dir).
Set the shared library environment variable based on the operating system.
The following table describes the shared library variables for each operating system:
Operating System Variable
Linux LD_LIBRARY_PATH
AIX LIBPATH
For example, use the following syntax for Linux:

• Using a Bourne shell:
$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/server_dir:$DB2DIR/lib; export
LD_LIBRARY_PATH
• Using a C shell:
$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/server_dir:$DB2DIR/lib
For AIX:
$ LIBPATH=${LIBPATH}:$HOME/server_dir:$DB2DIR/lib; export LIBPATH
$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$DB2DIR/lib
4. Edit the .cshrc or .profile to include the complete set of shell commands. Save the file and either log out
and log in again or run the source command.
$ source .profile
Using a C shell:
$ source .cshrc
5. If the DB2 database resides on the same machine on which the Data Integration Service, PowerCenter
Integration Service, or PowerCenter Repository Service process runs, configure the DB2 instance as a
remote instance.
Run the following command to verify if there is a remote entry for the database:
DB2 LIST DATABASE DIRECTORY
The command lists all the databases that the DB2 client can access and their configuration properties. If
this command lists an entry for “Directory entry type” of “Remote,” skip to 7.
6. If the database is not configured as remote, run the following command to verify whether a TCP/IP node
is cataloged for the host:
DB2 LIST NODE DIRECTORY
248 Appendix B: Connecting to Databases from UNIX or Linux

If the node name is empty, you can create one when you set up a remote database. Use the following
command to set up a remote database and, if needed, create a node:
db2 CATALOG TCPIP NODE <nodename> REMOTE <hostname_or_address> SERVER <port number>
Run the following command to catalog the database:
db2 CATALOG DATABASE <dbname> as <dbalias> at NODE <nodename>
For more information about these commands, see the database documentation.
7. Verify that you can connect to the DB2 database. Run the DB2 Command Line Processor and run the
command:
CONNECT TO <dbalias> USER <username> USING <password>
If the connection is successful, clean up with the CONNECT RESET or TERMINATE command.
Connecting to an Informix Database

Use ODBC to connect to an Informix database on UNIX or Linux.
Configuring ODBC Connectivity

You can configure ODBC connectivity to an Informix database.
The following steps provide a guideline for configuring ODBC connectivity. For specific instructions, see the
1. Set the ODBCHOME environment variable to the ODBC installation directory. For example:
$ ODBCHOME=<Informatica server home>/ODBC7.1; export ODBCHOME
Using a C shell:
$ setenv ODBCHOME <Informatica server home>/ODBC7.1
2. Set the ODBCINI environment variable to the location of the odbc.ini file. For example, if the odbc.ini file
is in the $ODBCHOME directory:
ODBCINI=$ODBCHOME/odbc.ini; export ODBCINI
Using a C shell:
$ setenv ODBCINI $ODBCHOME/odbc.ini
3. Edit the existing odbc.ini file in the $ODBCHOME directory or copy this odbc.ini file to the UNIX home
directory and edit it.
$ cp $ODBCHOME/odbc.ini $HOME/.odbc.ini
4. Add an entry for the Informix data source under the section [ODBC Data Sources] and configure the data
source. For example:
[Informix Wire Protocol]
Driver=/export/home/Informatica/10.0.0/ODBC7.1/lib/DWifcl27.so
Description=DataDirect 7.1 Informix Wire Protocol
AlternateServers=
ApplicationUsingThreads=1
CancelDetectInterval=0
ConnectionRetryCount=0
ConnectionRetryDelay=3
Database=<database_name>
Connecting to an Informix Database 249

HostName=<Informix_host>
LoadBalancing=0
LogonID=
Password=
PortNumber=<Informix_server_port>
ReportCodePageConversionErrors=0
ServerName=<Informix_server>
TrimBlankFromIndexName=1
5. Set the PATH and shared library environment variables by executing the script odbc.sh or odbc.csh in
the $ODBCHOME directory.
sh odbc.sh
Using a C shell:
source odbc.csh
6. Verify that you can connect to the Informix database using the ODBC data source. If the connection fails,
see the database documentation.
Connecting to a Microsoft SQL Server Database

Use the Microsoft SQL Server connection to connect to a Microsoft SQL Server database from a UNIX or
Linux machine.
Configuring SSL Authentication through ODBC

You can configure SSL authentication for Microsoft SQL Server through ODBC using the DataDirect New SQL
Server Wire Protocol driver.
1. Open the odbc.ini file and add an entry for the ODBC data source and DataDirect New SQL Server Wire
Protocol driver under the section [ODBC Data Sources].
2. Add the attributes in the odbc.ini file for configuring SSL.
The following table lists the attributes that you must add to the odbc.ini file when you configure SSL
authentication:
Attribute Description
EncryptionMethod The method that the driver uses to encrypt the data sent between the driver and the
database server. Set the value to 1 to encrypt data using SSL.
ValidateServerCertificate Determines whether the driver validates the certificate sent by the database server
when SSL encryption is enabled. Set the value to 1 for the driver to validate the
server certificate.
TrustStore The location and name of the trust store file. The trust store file contains a list of
Certificate Authorities (CAs) that the driver uses for SSL server authentication.

Attribute Description
TrustStorePassword The password to access the contents of the trust store file.
HostNameInCertificate Optional. The host name that is established by the SSL administrator for the driver to
validate the host name contained in the certificate.
Configuring Custom Properties for Microsoft SQL Server

You can configure custom properties for Microsoft SQL Server to improve bulk load performance.
1. Launch the PowerCenter client and connect to Workflow Manager.

2. Open a workflow and select a session that you want to configure.
3. Click the Config Object tab.
4. Change the value of the Default Buffer Block size to 5 MB. You can also use the following command:
$INFA_HOME/server/bin/./pmrep massupdate -t session_config_property -n "Default buffer
block size" -v "5MB" -f $<folderName>
To get optimum throughput for a row size of 1 KB, you must set the Buffer Block size to 5 MB.
5. Click the Properties tab.
6. Change the Commit Interval to 100000 if the session contains a relational target.
7. Set the DTM Buffer Size. The optimum DTM Buffer Size is ((10 x Block Buffer size) x number of
partitions).
Connecting to a Netezza Database

Install and configure Netezza ODBC driver on the machine where the PowerCenter Integration Service
process runs. Use the DataDirect Driver Manager in the DataDirect driver package shipped with the
Informatica product to configure the Netezza data source details in the odbc.ini file.

You can configure ODBC connectivity to a Netezza database.
1. To configure connectivity for the integration service process, log in to the machine as a user who can
start a service process.
2. Set the ODBCHOME, NZ_ODBC_INI_PATH, and PATH environment variables.
ODBCHOME. Set the variable to the ODBC installation directory. For example:
$ ODBCHOME=<Informatica server home>/ODBC7.1; export ODBCHOME
Using a C shell:
$ setenv ODBCHOME =<Informatica server home>/ODBC7.1
Connecting to a Netezza Database 251

PATH. Set the variable to the ODBCHOME/bin directory. For example:
PATH="${PATH}:$ODBCHOME/bin"
Using a C shell:
$ setenv PATH ${PATH}:$ODBCHOME/bin
NZ_ODBC_INI_PATH. Set the variable to point to the directory that contains the odbc.ini file. For
example, if the odbc.ini file is in the $ODBCHOME directory:
NZ_ODBC_INI_PATH=$ODBCHOME; export NZ_ODBC_INI_PATH
Using a C shell:
$ setenv NZ_ODBC_INI_PATH $ODBCHOME
3. Set the shared library environment variable.
The shared library path must contain the ODBC libraries. It must also include the Informatica services
installation directory (server_dir).
Set the shared library environment variable based on the operating system. Set the Netezza library folder
to <NetezzaInstallationDir>/lib64.
AIX LIBPATH

$ LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:$HOME/server_dir:$ODBCHOME/
lib:<NetezzaInstallationDir>/lib64”
export LD_LIBRARY_PATH
$ setenv LD_LIBRARY_PATH "${LD_LIBRARY_PATH}:$HOME/server_dir:$ODBCHOME/
lib:<NetezzaInstallationDir>/lib64"
For AIX
$ LIBPATH=${LIBPATH}:$HOME/server_dir:$ODBCHOME/lib:<NetezzaInstallationDir>/
lib64; export LIBPATH
$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$ODBCHOME/
lib:<NetezzaInstallationDir>/lib64
4. Edit the existing odbc.ini file or copy the odbc.ini file to the home directory and edit it.
This file exists in $ODBCHOME directory.
Add an entry for the Netezza data source under the section [ODBC Data Sources] and configure the data
source.

For example:
[NZSQL]
Driver = /export/home/appsqa/thirdparty/netezza/lib64/libnzodbc.so
Description = NetezzaSQL ODBC
Servername = netezza1.informatica.com
Port = 5480
Database = infa
Username = admin
Password = password
Debuglogging = true
StripCRLF = false
PreFetch = 256
Protocol = 7.0
ReadOnly = false
ShowSystemTables = false
Socket = 16384
DateFormat = 1
TranslationDLL =
TranslationName =
TranslationOption =
NumericAsChar = false
For more information about Netezza connectivity, see the Netezza ODBC driver documentation.
5. Verify that the last entry in the odbc.ini file is InstallDir and set it to the ODBC installation directory.
For example:
InstallDir=<Informatica install directory>/<ODBCHOME directory>
6. Edit the .cshrc or .profile file to include the complete set of shell commands.
7. Restart the Informatica services.
Connecting to an Oracle Database

For native connectivity, install the version of Oracle client appropriate for the Oracle database server version.
To ensure compatibility between Informatica and databases, use the appropriate database client libraries.
You must 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.

You can configure native connectivity to an Oracle database to increase performance.
The following steps provide a guideline for configuring native connectivity through Oracle Net Services or
Net8. For specific instructions, see the database documentation.
1. To configure connectivity for the Data Integration Service, PowerCenter Integration Service, or
PowerCenter Repository Service process, log in to the machine as a user who can start the server
process.
2. Set the ORACLE_HOME, NLS_LANG, TNS_ADMIN, and PATH environment variables.
ORACLE_HOME. Set the variable to the Oracle client installation directory. For example, if the client is
installed in the /HOME2/oracle directory. set the variable as follows:
$ ORACLE_HOME=/HOME2/oracle; export ORACLE_HOME
Connecting to an Oracle Database 253

Using a C shell:
$ setenv ORACLE_HOME /HOME2/oracle
NLS_LANG. Set the variable to the locale (language, territory, and character set) you want the database
client and server to use with the login. The value of this variable depends on the configuration. For
example, if the value is american_america.UTF8, set the variable as follows:
$ NLS_LANG=american_america.UTF8; export NLS_LANG
Using a C shell:
$ NLS_LANG american_america.UTF8
To determine the value of this variable, contact the administrator.
ORA_SDTZ. To set the default session time zone when the Data Integration Service reads or writes the
Timestamp with Local Time Zone data, specify the ORA_SDTZ environment variable.
You can set the ORA_SDTZ environment variable to any of the following values:
• Operating system local time zone ('OS_TZ')
• Database time zone ('DB_TZ')
• Absolute offset from UTC (for example, '-05:00')
• Time zone region name (for example, 'America/Los_Angeles')
You can set the environment variable at the machine where Informatica server runs.
TNS_ADMIN. If the tnsnames.ora file is not in the same location as the Oracle client installation location,
set the TNS_ADMIN environment variable to the directory where the tnsnames.ora file resides. For
example, if the file is in the /HOME2/oracle/files directory, set the variable as follows:
$ TNS_ADMIN=$HOME2/oracle/files; export TNS_ADMIN
Using a C shell:
$ setenv TNS_ADMIN=$HOME2/oracle/files
Note: By default, the tnsnames.ora file is stored in the following directory: $ORACLE_HOME/network/
admin.
PATH. To run the Oracle command line programs, set the variable to include the Oracle bin directory.
$ PATH=${PATH}:$ORACLE_HOME/bin; export PATH
Using a C shell:
$ setenv PATH ${PATH}:ORACLE_HOME/bin
The Oracle client software contains a number of shared library components that the Data Integration
Service, PowerCenter Integration Service, and PowerCenter Repository Service processes load
dynamically. To locate the shared libraries during run time, set the shared library environment variable.
Set the shared library environment variable to LD_LIBRARY_PATH.
For example, use the following syntax:
$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/server_dir:$ORACLE_HOME/lib; export
LD_LIBRARY_PATH

$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/server_dir:$ORACLE_HOME/lib
and log in again, or run the source command.
$ source .profile
Using a C shell:
$ source .cshrc
5. Verify that the Oracle client is configured to access the database.
Use the SQL*Net Easy Configuration Utility or copy an existing tnsnames.ora file to the home directory
and modify it.
The tnsnames.ora file is stored in the following directory: $ORACLE_HOME/network/admin.
Enter the correct syntax for the Oracle connect string, typically databasename.world.
Here is a sample tnsnames.ora file. Enter the information for the database.
mydatabase.world =
(DESCRIPTION
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = mycompany.world
(PROTOCOL = TCP)
(Host = mymachine)
(Port = 1521)
)
)
(CONNECT_DATA =
(SID = MYORA7)
(GLOBAL_NAMES = mydatabase.world)
6. Verify that you can connect to the Oracle database.
To connect to the Oracle database, launch SQL*Plus and enter the connectivity information. If you fail to
connect to the database, verify that you correctly entered all of the connectivity information.
Enter the user name and connect string as defined in the tnsnames.ora file.
Connecting to a PostgreSQL Database

For native connectivity, install the version of PostgreSQL client appropriate for the PostgreSQL database
server version.
You must install compatible versions of the PostgreSQL client and PostgreSQL database server. You must
also install the same version of the PostgreSQL client on all machines that require it. To verify compatibility,
contact PostgreSQL.
Connecting to a PostgreSQL Database 255

You can configure native connectivity to an PostgreSQL database to increase performance.
The following steps provide a guideline for configuring native connectivity through PostgreSQL. For specific
instructions, see the database documentation.
1. To configure connectivity for the PowerCenter Integration Service and PowerCenter Repository Service
process, log in to the machine as a user who can start the server process.
2. To install PostgreSQL database for the PowerCenter repository, set values for the PostgreSQL database
port=Database port
To securely connect to PostgreSQL for the PowerCenter repository, set the sslmode to require along
with the remaining required database properties in the pg_service.conf file in the following format:
sslmode=require
3. Set the PGSERVICEFILE, PGHOME, and PATH environment variables.
PGSERVICEFILE. Set the variable to the pg_service.conf file that contains the connection parameters
for PostgreSQL database connection. For example, set the variable as follows:
$ export PGSERVICEFILE; PGSERVICEFILE=<pg_service.conf file
directory>/pg_service.conf
Using a C shell:
$ setenv PGSERVICEFILE <pg_service.conf file
directory>/pg_service.conf
PGHOME. Set the variable to the PostgreSQL installation path where you have installed the PostgreSQL
client. For example, set the variable as follows:
$ export PGHOME; PGHOME=/usr/pgsql-10
Using a C shell:
$ setenv PGHOME /usr/pgsql-10
PATH. To run the PostgreSQL command line programs, set the variable to include the PostgreSQL client
directory, psql. For example, set the variable as follows:
$ export PATH; PATH=${PATH}:${PGHOME}
Using a C shell:
$ setenv PATH ${PGHOME}:${PATH}
The PostgreSQL client software contains a number of shared library components that the PowerCenter
Integration Service and PowerCenter Repository Service processes load dynamically. To locate the
shared libraries during run time, set the shared library environment variable.
Set the shared library environment variable to LD_LIBRARY_PATH.

For example, use the following syntax:
$ export LD_LIBRARY_PATH; LD_LIBRARY_PATH $PGHOME/lib
$ LD_LIBRARY_PATH <InstallationDirectory>/server/bin:${LD_LIBRARY_PATH}
$ setenv LD_LIBRARY_PATH $PGHOME/lib
$ setenv LD_LIBRARY_PATH <InstallationDirectory>/server/bin:${LD_LIBRARY_PATH}
5. Verify that you can connect to the PostgreSQL database.
To connect to the PostgreSQL database, launch the psql utility and enter the connectivity information.
Connecting to a Sybase ASE Database

For native connectivity, install the version of Open Client appropriate for your database version. To ensure
compatibility between Informatica and databases, use the appropriate database client libraries.
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.
If you want to create, restore, or upgrade a Sybase ASE repository, set allow nulls by default to TRUE at the
database level. Setting this option changes the default null type of the column to null in compliance with the
SQL standard.

You can configure native connectivity to a Sybase ASE database to increase performance.
1. To configure connectivity to the Data Integration Service, PowerCenter Integration Service, or

PowerCenter Repository Service process, log in to the machine as a user who can start the server
process.
2. Set the SYBASE and PATH environment variables.
SYBASE. Set the variable to the Sybase Open Client installation directory. For example if the client is
installed in the /usr/sybase directory:
$ SYBASE=/usr/sybase; export SYBASE
Using a C shell:
$ setenv SYBASE /usr/sybase
PATH. To run the Sybase command line programs, set the variable to include the Sybase OCS bin
directory.
$ PATH=${PATH}:/usr/sybase/OCS-15_0/bin; export PATH
Using a C shell:
$ setenv PATH ${PATH}:/usr/sybase/OCS-15_0/bin
Connecting to a Sybase ASE Database 257

The Sybase Open Client software contains a number of shared library components that the Data
Integration Service, PowerCenter Integration Service, and PowerCenter Repository Service processes
load dynamically. Set the shared library environment variable so that the services can find the shared
libraries at run time.
The shared library path must also include the installation directory of the Informatica services
(server_dir).
The following table describes the shared library variables for each operating system.
AIX LIBPATH

$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/server_dir:$SYBASE/OCS-15_0/lib;
$SYBASE/OCS-15_0/lib3p;$SYBASE/OCS-15_0/lib3p64; export LD_LIBRARY_PATH
$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/server_dir:$SYBASE/OCS-15_0/lib;
$SYBASE/OCS-15_0/lib3p;$SYBASE/OCS-15_0/lib3p64;
For AIX
$ LIBPATH=${LIBPATH}:$HOME/server_dir:$SYBASE/OCS-15_0/lib;$SYBASE/OCS-15_0/lib3p;
$SYBASE/OCS-15_0/lib3p64; export LIBPATH
$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$SYBASE/OCS-15_0/lib;$SYBASE/
OCS-15_0/lib3p;$SYBASE/OCS-15_0/lib3p64;
$ source .profile
Using a C shell:
$ source .cshrc
5. Verify the Sybase ASE server name in the Sybase interfaces file stored in the $SYBASE directory.
6. Verify that you can connect to the Sybase ASE database.
To connect to the Sybase ASE database, launch ISQL and enter the connectivity information. If you fail to
User names and database names are case sensitive.

Connecting to a Teradata Database
Install and configure native client software on the machines where the Data Integration Service or
PowerCenter Integration Service process runs. To ensure compatibility between Informatica and databases,
use the appropriate database client libraries.
Install the Teradata client, the Teradata ODBC driver, and any other Teradata client software that you might
need on the machine where the Data Integration Service or PowerCenter Integration Service runs. You must
also configure ODBC connectivity.
Note: Based on a recommendation from Teradata, Informatica uses ODBC to connect to Teradata. ODBC is a
native interface for Teradata.

You can configure ODBC connectivity to a Teradata database.
1. To configure connectivity for the integration service process, log in to the machine as a user who can
start a service process.
2. Set the TERADATA_HOME, ODBCHOME, and PATH environment variables.
TERADATA_HOME. Set the variable to the Teradata driver installation directory. The defaults are as
follows:
$ TERADATA_HOME=/opt/teradata/client/<version>; export TERADATA_HOME
Using a C shell:
$ setenv TERADATA_HOME /opt/teradata/client/<version>
ODBCHOME. Set the variable to the ODBC installation directory. For example:
$ ODBCHOME=$INFA_HOME/ODBC<version>; export ODBCHOME
Using a C shell:
$ setenv ODBCHOME $INFA_HOME/ODBC<version>
PATH. To run the ddtestlib utility, to verify that the DataDirect ODBC driver manager can load the driver
files, set the variable as follows:
PATH="${PATH}:$ODBCHOME/bin:$TERADATA_HOME/bin"
Using a C shell:
$ setenv PATH ${PATH}:$ODBCHOME/bin:$TERADATA_HOME/bin
The Teradata software contains multiple shared library components that the integration service process
loads dynamically. Set the shared library environment variable so that the services can find the shared
libraries at run time.
The shared library path must also include installation directory of the Informatica service (server_dir).
Connecting to a Teradata Database 259

AIX LIBPATH

$ LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:$HOME/server_dir:$ODBCHOME/lib:
$TERADATA_HOME/lib64:$TERADATA_HOME/odbc_64/lib";
export LD_LIBRARY_PATH
$ setenv LD_LIBRARY_PATH "${LD_LIBRARY_PATH}:$HOME/server_dir:$ODBCHOME/lib:
$TERADATA_HOME/lib64:
$TERADATA_HOME/odbc_64/lib"
For AIX
$ LIBPATH=${LIBPATH}:$HOME/server_dir:$ODBCHOME/lib:$TERADATA_HOME/
lib64:$TERADATA_HOME/odbc_64/lib; export LIBPATH
$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$ODBCHOME/lib:$TERADATA_HOME/lib64:
$TERADATA_HOME/odbc_64/lib
Add an entry for the Teradata data source under the section [ODBC Data Sources] and configure the data
source.
For example, for Teradata Parallel Transporter utilities, version 15.10:
MY_TERADATA_SOURCE=Teradata Driver
[MY_TERADATA_SOURCE]
Driver=/opt/teradata/client/15.10/lib64/tdata.so
Description=NCR 3600 running Teradata V1R5.2
DBCName=208.199.59.208
DateTimeFormat=AAA
SessionMode=ANSI
DefaultDatabase=
Username=
Password=
For example, for Teradata Parallel Transporter utilities, version 16.20:
MY_TERADATA_SOURCE=Teradata Driver
[dwtera]
Driver=/opt/teradata/client/16.20/lib64/tdataodbc_sb64.so
Description=NCR 3600 running Teradata V1R5.2
DBCName=tdvbe1510
LastUser=
Username=
Password=
Database=

DefaultDatabase=
UseNativeLOBSupport=Yes
CharacterSet=UTF8
SessionMode=ANSI
5. Set the DateTimeFormat to AAA in the Teradata data ODBC configuration.
6. Optionally, set the SessionMode to ANSI. When you use ANSI session mode, Teradata does not roll back
the transaction when it encounters a row error.
If you choose Teradata session mode, Teradata rolls back the transaction when it encounters a row
error. In Teradata mode, the integration service process cannot detect the rollback, and does not report
this in the session log.
7. To configure connection to a single Teradata database, enter the DefaultDatabase name. To create a
single connection to the default database, enter the user name and password. To connect to multiple
databases, using the same ODBC DSN, leave the DefaultDatabase field empty.
For more information about Teradata connectivity, see the Teradata ODBC driver documentation.
8. Verify that the last entry in the odbc.ini is InstallDir and set it to the odbc installation directory.
For example:
InstallDir=<Informatica installation directory>/ODBC<version>
9. Edit the .cshrc or .profile to include the complete set of shell commands.
10. Save the file and either log out and log in again, or run the source command.
$ source .profile
Using a C shell:
$ source .cshrc
11. For each data source you use, make a note of the file name under the Driver=<parameter> in the data
source entry in odbc.ini. Use the ddtestlib utility to verify that the DataDirect ODBC driver manager can
load the driver file.
For example, if you have the driver entry:
Driver=/u01/app/teradata/td-tuf611/odbc/drivers/tdata.so
run the following command:
ddtestlib /u01/app/teradata/td-tuf611/odbc/drivers/tdata.so
12. Test the connection using BTEQ or another Teradata client tool.
Connecting to a JDBC Data Source

To enable the the Data Integration Service to write to relational targets, download JDBC driver .jar files to the
Data Integration Service host and to all client machines that run mappings that have relational targets.
Obtain the driver .jar file from the database vendor. For example, to access an Oracle database, download the
file ojdbc.jar from the Oracle website.
1. Place the JDBC driver .jar file in the following directory on the Data Integration Service machine
<Informatica installation directory>/externaljdbcjars. Then recycle the Data Integration
Service.
2. Place the JDBC driver .jar file in the following directory on machines that host the Developer tool:
<Informatica installation directory>/clients/externaljdbcjars. Then recycle the Developer
tool.
Connecting to a JDBC Data Source 261

Connecting to an ODBC Data Source
Install and configure native client software on the machine where the Data Integration Service, PowerCenter
Integration Service, and PowerCenter Repository Service run. Also install and configure any underlying client
access software required by the ODBC driver. To ensure compatibility between Informatica and the
databases, use the appropriate database client libraries.
The Informatica installation includes DataDirect ODBC drivers. If the odbc.ini file contains connections that
use earlier versions of the ODBC driver, update the connection information to use the new drivers. Use the
System DSN to specify an ODBC data source on Windows.
1. On the machine where the application service runs, log in as a user who can start a service process.
2. Set the ODBCHOME and PATH environment variables.
ODBCHOME. Set to the DataDirect ODBC installation directory. For example, if the install directory is /
export/home/Informatica/10.0.0/ODBC7.1.
$ ODBCHOME=/export/home/Informatica/10.0.0/ODBC7.1; export ODBCHOME
Using a C shell:
$ setenv ODBCHOME /export/home/Informatica/10.0.0/ODBC7.1
PATH. To run the ODBC command line programs, like ddtestlib, set the variable to include the odbc bin
directory.
$ PATH=${PATH}:$ODBCHOME/bin; export PATH
Using a C shell:
$ setenv PATH ${PATH}:$ODBCHOME/bin
Run the ddtestlib utility to verify that the DataDirect ODBC driver manager can load the driver files.
The ODBC software contains a number of shared library components that the service processes load
dynamically. Set the shared library environment variable so that the services can find the shared libraries
at run time.
AIX LIBPATH

$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/server_dir:$ODBCHOME/lib; export
LD_LIBRARY_PATH
$ setenv LD_LIBRARY_PATH $HOME/server_dir:$ODBCHOME:${LD_LIBRARY_PATH}

For AIX
$ LIBPATH=${LIBPATH}:$HOME/server_dir:$ODBCHOME/lib; export LIBPATH
$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$ODBCHOME/lib
Add an entry for the ODBC data source under the section [ODBC Data Sources] and configure the data
source.
For example:
MY_MSSQLSERVER_ODBC_SOURCE=<Driver name or data source description>
[MY_SQLSERVER_ODBC_SOURCE]
Driver=<path to ODBC drivers>
Description=DataDirect 8.0 SQL Server Wire Protocol
Database=<SQLServer_database_name>
LogonID=<username>
Password=<password>
Address=<TCP/IP address>,<port number>
QuoteId=No
AnsiNPW=No
ApplicationsUsingThreads=1
This file might already exist if you have configured one or more ODBC data sources.
5. Verify that the last entry in the odbc.ini is InstallDir and set it to the odbc installation directory.
For example:
InstallDir=/export/home/Informatica/10.0.0/ODBC7.1
6. If you use the odbc.ini file in the home directory, set the ODBCINI environment variable.
$ ODBCINI=/$HOME/.odbc.ini; export ODBCINI
Using a C shell:
$ setenv ODBCINI $HOME/.odbc.ini
$ source .profile
Using a C shell:
$ source .cshrc
8. Use the ddtestlib utility to verify that the DataDirect ODBC driver manager can load the driver file you
specified for the data source in the odbc.ini file.
For example, if you have the driver entry:
Driver = /export/home/Informatica/10.0.0/ODBC7.1/lib/DWxxxxnn.so
run the following command:
ddtestlib /export/home/Informatica/10.0.0/ODBC7.1/lib/DWxxxxnn.so
Connecting to an ODBC Data Source 263

9. Install and configure any underlying client access software needed by the ODBC driver.
Note: While some ODBC drivers are self-contained and have all information inside the .odbc.ini file, most
are not. For example, if you want to use an ODBC driver to access Sybase IQ, you must install the Sybase
IQ network client software and set the appropriate environment variables.
To use the Informatica ODBC drivers (DWxxxxnn.so), manually set the PATH and shared library path
environment variables. Alternatively, run the odbc.sh or odbc.csh script in the $ODBCHOME folder. This
script will set the required PATH and shared library path environment variables for the ODBC drivers
provided by Informatica.
Sample odbc.ini File

The following sample shows the entries for the ODBC drivers in the ODBC.ini file:
[ODBC Data Sources]
SQL Server Legacy Wire Protocol=DataDirect 7.1 SQL Server Legacy Wire Protocol
DB2 Wire Protocol=DataDirect 7.1 DB2 Wire Protocol
Informix Wire Protocol=DataDirect 7.1 Informix Wire Protocol
Oracle Wire Protocol=DataDirect 8.0 Oracle Wire Protocol
Sybase Wire Protocol=DataDirect 7.1 Sybase Wire Protocol
SQL Server Wire Protocol=DataDirect 8.0 SQL Server Wire Protocol
MySQL Wire Protocol=DataDirect 7.1 MySQL Wire Protocol
PostgreSQL Wire Protocol=DataDirect 7.1 PostgreSQL Wire Protocol
Greenplum Wire Protocol=DataDirect 7.1 Greenplum Wire Protocol
[ODBC]
IANAAppCodePage=4
InstallDir=/<Informatica installation directory>/ODBC7.1
Trace=0
TraceFile=odbctrace.out
TraceDll=/<Informatica installation directory>/ODBC7.1/lib/DWtrc27.so
[DB2 Wire Protocol]

Driver=/<Informatica installation directory>/ODBC7.1/lib/DWdb227.so
Description=DataDirect 7.1 DB2 Wire Protocol
AccountingInfo=
AddStringToCreateTable=
AlternateID=
AlternateServers=
ApplicationName=
AuthenticationMethod=0
BulkBinaryThreshold=32
BulkCharacterThreshold=-1
BulkLoadBatchSize=1024
BulkLoadFieldDelimiter=
BulkLoadRecordDelimiter=
CatalogSchema=
CharsetFor65535=0
ClientHostName=
ClientUser=
#Collection applies to z/OS and iSeries only
Collection=
ConcurrentAccessResolution=0
ConnectionReset=0
CurrentFuncPath=
#Database applies to DB2 UDB only
DefaultIsolationLevel=1
DynamicSections=1000
EnableBulkLoad=0

EncryptionMethod=0
FailoverGranularity=0
FailoverMode=0
FailoverPreconnect=0
GrantAuthid=PUBLIC
GrantExecute=1
GSSClient=native
HostNameInCertificate=
IpAddress=<DB2_server_host>
KeyPassword=
KeyStore=
KeyStorePassword=
LoadBalanceTimeout=0
LoadBalancing=0
#Location applies to z/OS and iSeries only
Location=<location_name>
LogonID=
MaxPoolSize=100
MinPoolSize=0
Password=
PackageCollection=NULLID
PackageNamePrefix=DD
PackageOwner=
Pooling=0
ProgramID=
QueryTimeout=0
TcpPort=50000
TrustStore=
TrustStorePassword=
UseCurrentSchema=0
ValidateServerCertificate=1
WithHold=1
XMLDescribeType=-10
[Informix Wire Protocol]

Driver=/<Informatica installation directory>/ODBC7.1/lib/DWifcl27.so
Description=DataDirect 7.1 Informix Wire Protocol
AlternateServers=
CancelDetectInterval=0
HostName=<Informix_host>
LoadBalancing=0
LogonID=
Password=
PortNumber=<Informix_server_port>
ServerName=<Informix_server>
TrimBlankFromIndexName=1
UseDelimitedIdentifiers=0
[Oracle Wire Protocol]

Driver=/<Informatica installation directory>/ODBC7.1/lib/DWora28.so
Description=DataDirect 8.0 Oracle Wire Protocol
AlternateServers=
AccountingInfo=
Action=
ApplicationName=
ArraySize=60000
CachedCursorLimit=32
CachedDescLimit=0
CatalogIncludesSynonyms=1
Sample odbc.ini File 265

CatalogOptions=0
ClientHostName=
ClientID=
ClientUser=
ConnectionReset=0
DataIntegrityLevel=0
DataIntegrityTypes=MD5,SHA1
DefaultLongDataBuffLen=1024
DescribeAtPrepare=0
EditionName=
EnableBulkLoad=0
EnableDescribeParam=0
EnableNcharSupport=0
EnableScrollableCursors=1
EnableStaticCursorsForLongData=0
EnableTimestampWithTimeZone=0
EncryptionLevel=0
EncryptionMethod=0
EncryptionTypes=AES128,AES192,AES256,DES,3DES112,3DES168,RC4_40,RC4_56,RC4_128,
RC4_256
FailoverMode=0
FetchTSWTZasTimestamp=0
GSSClient=native
HostName=<Oracle_server>
InitializationString=
KeyPassword=
KeyStore=
KeyStorePassword=
LoadBalancing=0
LocalTimeZoneOffset=
LockTimeOut=-1
LoginTimeout=15
LogonID=
MaxPoolSize=100
MinPoolSize=0
Module=
Password=
Pooling=0
PortNumber=<Oracle_server_port>
ProcedureRetResults=0
ProgramID=
QueryTimeout=0
ReportRecycleBin=0
ServerName=<server_name in tnsnames.ora>
ServerType=0
ServiceName=
SID=<Oracle_System_Identifier>
TimestampeEscapeMapping=0
TNSNamesFile=<tnsnames.ora_filename>
TrustStore=
TrustStorePassword=
UseCurrentSchema=1
WireProtocolMode=2
[Sybase Wire Protocol]

Driver=/<Informatica installation directory>/ODBC7.1/lib/DWase27.so
Description=DataDirect 7.1 Sybase Wire Protocol
AlternateServers=
ApplicationName=
ArraySize=50

Charset=
ConnectionReset=0
CursorCacheSize=1
EnableBulkLoad=0
EnableQuotedIdentifiers=0
EncryptionMethod=0
FailoverMode=0
GSSClient=native
Language=
LoadBalancing=0
LoginTimeout=15
LogonID=
MaxPoolSize=100
MinPoolSize=0
NetworkAddress=<Sybase_host,Sybase_server_port>
OptimizePrepare=1
PacketSize=0
Password=
Pooling=0
QueryTimeout=0
RaiseErrorPositionBehavior=0
SelectMethod=0
ServicePrincipalName=
TruncateTimeTypeFractions=0
TrustStore=
TrustStorePassword=
WorkStationID=
[SQL Server Wire Protocol]

Driver=/<Informatica installation directory>/ODBC7.1/lib/DWsqls28.so
Description=DataDirect 8.0 SQL Server Wire Protocol
AlternateServers=
AlwaysReportTriggerResults=0
AnsiNPW=1
ApplicationName=
BulkLoadOptions=2
ConnectionReset=0
EnableBulkLoad=0
EnableQuotedIdentifiers=0
EncryptionMethod=0
FailoverMode=0
FetchTWFSasTime=1
GSSClient=native
HostName=<SQL_Server_host>

Language=
LoadBalancing=0
LoginTimeout=15
LogonID=
MaxPoolSize=100
MinPoolSize=0
PacketSize=-1
Password=
Pooling=0
PortNumber=<SQL_Server_server_port>
QueryTimeout=0
SnapshotSerializable=0
TrustStore=
TrustStorePassword=
WorkStationID=
XML Describe Type=-10
[MySQL Wire Protocol]

Driver=/<Informatica installation directory>/ODBC7.1/lib/DWmysql27.so
Description=DataDirect 7.1 MySQL Wire Protocol
AlternateServers=
ConnectionReset=0
EncryptionMethod=0
FailoverMode=0
HostName=<MySQL_host>
InteractiveClient=0
LicenseNotice=You must purchase commercially licensed MySQL database software or
a MySQL Enterprise subscription in order to use the DataDirect Connect for ODBC
for MySQL Enterprise driver with MySQL software.
KeyStore=
KeyStorePassword=
LoadBalancing=0
LogonID=
LoginTimeout=15
MaxPoolSize=100
MinPoolSize=0
Password=
Pooling=0
PortNumber=<MySQL_server_port>
QueryTimeout=0
ReportCodepageConversionErrors=0
TreatBinaryAsChar=0
TrustStore=
TrustStorePassword=
[PostgreSQL Wire Protocol]

Driver=/<Informatica installation directory>/ODBC7.1/lib/DWpsql27.so
Description=DataDirect 7.1 PostgreSQL Wire Protocol
AlternateServers=
ConnectionReset=0

EncryptionMethod=0
ExtendedColumnMetadata=0
FailoverMode=0
FetchTWFSasTime=0
HostName=<PostgreSQL_host>
KeyPassword=
KeyStore=
KeyStorePassword=
LoadBalancing=0
LoginTimeout=15
LogonID=
MaxPoolSize=100
MinPoolSize=0
Password=
Pooling=0
PortNumber=<PostgreSQL_server_port>
QueryTimeout=0
TransactionErrorBehavior=1
TrustStore=
TrustStorePassword=
XMLDescribeType=-10
[Greenplum Wire Protocol]

Driver=/<Informatica installation directory>/ODBC7.1/lib/DWgplm27.so
Description=DataDirect 7.1 Greenplum Wire Protocol
AlternateServers=
ConnectionReset=0
EnableKeysetCursors=0
EncryptionMethod=0
ExtendedColumnMetadata=0
FailoverMode=0
FetchTWFSasTime=0
HostName=<Greenplum_host>
KeyPassword=
KeysetCursorOptions=0
KeyStore=
KeyStorePassword=
LoadBalancing=0
LoginTimeout=15
LogonID=
MaxPoolSize=100
MinPoolSize=0
Password=
Pooling=0
PortNumber=<Greenplum_server_port>
QueryTimeout=0
TransactionErrorBehavior=1
XMLDescribeType=-10

Note: You might have to customize the DSN entries in the ODBC.ini file based on the third-party driver that
you use. For more information about the DSN entries, see the corresponding third-party driver
documentation.

Appendix C
Connecting to Databases from

Windows
• Connecting to Databases from Windows Overview, 271

• Connecting to an IBM DB2 Universal Database from Windows, 272
• Connecting to an Informix Database from Windows, 272
• Connecting to Microsoft Access and Microsoft Excel from Windows, 273
• Connecting to a Microsoft SQL Server Database from Windows, 273
• Connecting to a Netezza Database from Windows, 275
• Connecting to an Oracle Database from Windows, 276
• Connecting to a PostgreSQL Database, 277
• Connecting to a Sybase ASE Database from Windows, 278
• Connecting to a Teradata Database from Windows, 279
Connecting to Databases from Windows Overview

Configure connectivity to enable communication between clients, services, and other components in the
domain.
To use native connectivity, you must install and configure the database client software for the database that
you want to access. 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. To
increase performance, use native connectivity.
The Informatica installation includes DataDirect ODBC drivers. If you have existing ODBC data sources
created with an earlier version of the drivers, you must create new ODBC data sources using the new drivers.
Configure ODBC connections using the DataDirect ODBC drivers provided by Informatica or third party ODBC
drivers that are Level 2 compliant or higher.
The Informatica installation includes DataDirect JDBC drivers. You can use these drivers without performing
additional steps. You can also download JDBC Type 4 drivers from third-party vendors to connect to sources
and targets. You can use any third-party JDBC driver that is JDBC 3.0 or later.
You must configure a database connection for the following services in the Informatica domain:
• PowerCenter Repository Service
271
• Model Repository Service
• Data Integration Service
• Analyst Service
Connecting to an IBM DB2 Universal Database from

Windows
For native connectivity, install the version of IBM DB2 Client Application Enabler (CAE) appropriate for the
IBM DB2 database server version. To ensure compatibility between Informatica and databases, use the
appropriate database client libraries.

You can configure native connectivity to an IBM DB2 database to increase performance.
1. Verify that the following environment variable settings have been established by IBM DB2 Client
Application Enabler (CAE):
DB2HOME=C:\IBM\SQLLIB
DB2INSTANCE=DB2
DB2CODEPAGE=1208 (Sometimes required. Use only if you encounter problems. Depends on
the locale, you may use other values.)
2. Verify that the PATH environment variable includes the IBM DB2 bin directory. For example:
PATH=C:\WINNT\SYSTEM32;C:\SQLLIB\BIN;...
3. Configure the IBM DB2 client to connect to the database that you want to access. To configure the IBM
DB2 client:
a. Launch the IBM DB2 Configuration Assistant.
b. Add the database connection.
c. Bind the connection.
4. Run the following command in the IBM DB2 Command Line Processor to verify that you can connect to
the IBM DB2 database:
CONNECT TO <dbalias> USER <username> USING <password>
5. If the connection is successful, run the TERMINATE command to disconnect from the database. If the
connection fails, see the database documentation.
Connecting to an Informix Database from Windows

Use ODBC to connect to an Informix database on Windows. Create an ODBC data source by using the
DataDirect ODBC drivers installed with Informatica. To ensure compatibility between Informatica and
databases, use the appropriate database client libraries.
Note: If you use the DataDirect ODBC driver provided by Informatica, you do not need the database client. The
ODBC wire protocols do not require the database client software to connect to the database.
272 Appendix C: Connecting to Databases from Windows

You can configure ODBC connectivity to an Informix database.
1. Create an ODBC data source using the DataDirect ODBC Wire Protocol driver for Informix provided by
Informatica.
2. Verify that you can connect to the Informix database using the ODBC data source.
Connecting to Microsoft Access and Microsoft Excel

from Windows
Configure connectivity to the Informatica components on Windows.
Install Microsoft Access or Excel on the machine where the Data Integration Service and PowerCenter
Integration Service processes run. Create an ODBC data source for the Microsoft Access or Excel data you
want to access.

You can configure ODBC connectivity to a Microsoft Access or Excel database.
1. Create an ODBC data source using the driver provided by Microsoft.

2. To avoid using empty string or nulls, use the reserved words PmNullUser for the user name and
PmNullPasswd for the password when you create a database connection.
Connecting to a Microsoft SQL Server Database from

Windows
You can connect to a Microsoft SQL Server database through the ODBC or the OLEDB provider type.

You can configure native connectivity to the Microsoft SQL Server database by using the ODBC (default) or
OLEDB provider types.
If you choose the ODBC provider type, you can enable the Use DSN option to use the DSN configured in the
Microsoft ODBC Administrator as the connect string. If you do not enable the Use DSN option, you must
specify the server name and database name in the connection properties.
Connecting to Microsoft Access and Microsoft Excel from Windows 273

If you choose the OLEDB provider type, you must install the Microsoft SQL Server 2012 Native Client to
configure native connectivity to the Microsoft SQL Server database. If you cannot connect to the database,
verify that you correctly entered all of the connectivity information.
You can download the Microsoft SQL Server 2012 Native Client from the following Microsoft website:
http://www.microsoft.com/en-in/download/details.aspx?id=29065.
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 following
commands:
• If you are using PowerCenter, run the following command: pmrep upgradeSqlServerConnection
• If you are using the Informatica platform, run the following command: infacmd.sh isp
upgradeSQLSConnection
For specific connectivity instructions, see the database documentation.
Rules and Guidelines for Microsoft SQL Server

Consider the following rules and guidelines when you configure ODBC connectivity to a Microsoft SQL Server
database on Windows:
• If you want to use a Microsoft SQL Server connection without using a Data Source Name (DSN less
connection), you must configure the odbcinst.ini environment variable.
• If you are using a DSN connection, you must add the entry "EnableQuotedIdentifiers=1" to the ODBC DSN.
If you do not add the entry, data preview and mapping run fail.
• When you use a DSN connection, you can configure the DataDirect specific properties. For more
information about how to configure and use the Data Direct specific properties, see the DataDirect
documentation.
• You can use the Microsoft SQL Server NTLM authentication on a DSN less Microsoft SQL Server
connection on the Microsoft Windows platform.
• If the Microsoft SQL Server table contains a UUID data type and if you are reading data from an SQL table
and writing data to a flat file, the data format might not be consistent between the OLE DB and ODBC
connection types.
• You cannot use SSL connection on a DSN less connection. If you want to use SSL, you must use the DSN
connection. Enable the Use DSN option and configure the SSL options in the odbc.ini file.
• If the Microsoft SQL Server uses Kerberos authentication, you must set the GSSClient property to point to
the Informatica Kerberos libraries. Use the following path and filename: <Informatica installation
directory>/server/bin/libgssapi_krb5.so.2.Create an entry for the GSSClient property in the DSN
entries section in odbc.ini for a DSN connection or in the SQL Server wire protocol section in
odbcinst.ini for a connection that does not use DSN.
• If you use the DataDirect ODBC driver to connect to Microsoft SQL Server, the Decimal data rounds off
within the target database based on the scale values in the database tables. For example, if the scale is 5,
the target Decimal data round-off occurs after the fifth digit that follows the decimal point. When the
scale is 5, the input value 12.3456789 rounds off to a target Decimal value of 12.34568.
• If you use Microsoft SQL Sever Native client to configure native connectivity to Microsoft SQL Server
databases, the Decimal data truncates based on the specified scale in the target database tables. For
example, if the scale is 5, the Decimal data truncation occurs after the fifth digit that follows the decimal
point. When the scale is 5, the input value 12.3456789 truncates to a target Decimal value of 12.34567.

Configuring Custom Properties for Microsoft SQL Server
You can configure custom properties for Microsoft SQL Server to improve bulk load performance.
1. Launch the PowerCenter client and connect to Workflow Manager.

2. Open a workflow and select a session that you want to configure.
3. Click the Config Object tab.
4. Change the value of the Default Buffer Block size to 5 MB. You can also use the following command:
$INFA_HOME/server/bin/./pmrep massupdate -t session_config_property -n "Default buffer
block size" -v "5MB" -f $<folderName>
To get optimum throughput for a row size of 1 KB, you must set the Buffer Block size to 5 MB.
5. Click the Properties tab.
6. Change the Commit Interval to 100000 if the session contains a relational target.
7. Set the DTM Buffer Size. The optimum DTM Buffer Size is ((10 x Block Buffer size) x number of
partitions).
Connecting to a Netezza Database from Windows

Install and configure ODBC on the machines where the PowerCenter Integration Service process runs and
where you install the PowerCenter Client. You must configure connectivity to the following Informatica
components on Windows:
• PowerCenter Integration Service. Install the Netezza ODBC driver on the machine where the PowerCenter
Integration Service process runs. Use the Microsoft ODBC Data Source Administrator to configure ODBC
connectivity.
• PowerCenter Client. Install the Netezza ODBC driver on each PowerCenter Client machine that accesses
the Netezza database. Use the Microsoft ODBC Data Source Administrator to configure ODBC
connectivity. Use the Workflow Manager to create a database connection object for the Netezza
database.

You can configure ODBC connectivity to a Netezza database.
1. Create an ODBC data source for each Netezza database that you want to access.
To create the ODBC data source, use the driver provided by Netezza.
Create a System DSN if you start the Informatica service with a Local System account logon. Create a
User DSN if you select the This account log in option to start the Informatica service.
After you create the data source, configure the properties of the data source.
2. Enter a name for the new ODBC data source.
3. Enter the IP address/host name and port number for the Netezza server.
4. Enter the name of the Netezza schema where you plan to create database objects.
5. Configure the path and file name for the ODBC log file.
Connecting to a Netezza Database from Windows 275

6. Verify that you can connect to the Netezza database.
You can use the Microsoft ODBC Data Source Administrator to test the connection to the database. To
test the connection, select the Netezza data source and click Configure. On the Testing tab, click Test
Connection and enter the connection information for the Netezza schema.
Connecting to an Oracle Database from Windows

For native connectivity, install the version of Oracle client appropriate for the Oracle database server version.
You must 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.

You can configure native connectivity to an Oracle database to increase performance.
The following steps provide a guideline for configuring native connectivity using Oracle Net Services or Net8.
For specific connectivity instructions, see the database documentation.
1. Verify that the Oracle home directory is set.

For example:
ORACLE_HOME=C:\Oracle
2. Verify that the PATH environment variable includes the Oracle bin directory.
For example, if you install Net8, the path might include the following entry:
PATH=C:\ORANT\BIN;
3. Configure the Oracle client to connect to the database that you want to access.
Launch SQL*Net Easy Configuration Utility or edit an existing tnsnames.ora file to the home directory
and modify it.
Note: By default, the tnsnames.ora file is stored in the following directory: <OracleInstallationDir>
\network\admin.
Enter the correct syntax for the Oracle connect string, typically databasename.world. Make sure the SID
entered here matches the database server instance ID defined on the Oracle server.
Here is a sample tnsnames.ora file. Enter the information for the database.
mydatabase.world =
(DESCRIPTION
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = mycompany.world
(PROTOCOL = TCP)
(Host = mymachine)
(Port = 1521)
)
)
(CONNECT_DATA =
(SID = MYORA7)
(GLOBAL_NAMES = mydatabase.world)
4. Set the NLS_LANG environment variable to the locale, including language, territory, and character set,
you want the database client and server to use with the login.

The value of this variable depends on the configuration. For example, if the value is
american_america.UTF8, you must set the variable as follows:
NLS_LANG=american_america.UTF8;
To determine the value of this variable, contact the database administrator.
5. To set the default session time zone when the Data Integration Service reads or writes the Timestamp
with Local Time Zone data, specify the ORA_SDTZ environment variable.
You can set the ORA_SDTZ environment variable to any of the following values:
• Operating system local time zone ('OS_TZ')
• Database time zone ('DB_TZ')
• Absolute offset from UTC (for example, '-05:00')
• Time zone region name (for example, 'America/Los_Angeles')
You can set the environment variable at the machine where Informatica server runs.
6. If the tnsnames.ora file is not in the same location as the Oracle client installation location, set the
TNS_ADMIN environment variable to the directory where the tnsnames.ora file resides.
For example, if the tnsnames.ora file is in the C:\oracle\files directory, set the variable as follows:
TNS_ADMIN= C:\oracle\files
7. Verify that you can connect to the Oracle database.
To connect to the database, launch SQL*Plus and enter the connectivity information. If you fail to
Use the connect string as defined in the tnsnames.ora file.
Connecting to a PostgreSQL Database

For native connectivity, install the version of PostgreSQL client appropriate for the PostgreSQL database
server version.
You must install compatible versions of the PostgreSQL client and PostgreSQL database server. You must
also install the same version of the PostgreSQL client on all machines that require it. To verify compatibility,
contact PostgreSQL.

You can configure native connectivity to an PostgreSQL database to increase performance.
The following steps provide a guideline for configuring native connectivity through PostgreSQL. For specific
instructions, see the database documentation.
1. To configure connectivity for the PowerCenter Integration Service and PowerCenter Repository Service
process, log in to the machine as a user who can start the server process.
2. To install PostgreSQL database for the PowerCenter repository, set values for the PostgreSQL database
Connecting to a PostgreSQL Database 277

port=Database port
To securely connect to PostgreSQL for the PowerCenter repository, set the sslmode to require along
with the remaining required database properties in the pg_service.conf file in the following format:
sslmode=require
3. Set the PGSERVICEFILE, PGHOME, and PATH environment variables.
PGSERVICEFILE. Set the variable to the pg_service.conf file that contains the connection parameters
for PostgreSQL database connection. For example, set the variable as follows:
$ export PGSERVICEFILE; PGSERVICEFILE=<InstallationDirectory>/pg_service.conf
Using a C shell:
$ setenv PGSERVICEFILE <InstallationDirectory>/pg_service.conf
PGHOME. Set the variable to the PostgreSQL installation path where you have installed the PostgreSQL
client. For example, set the variable as follows:
$ export PGHOME; PGHOME=/usr/pgsql-10
Using a C shell:
$ setenv PGHOME /usr/pgsql-10
PATH. To run the PostgreSQL command line programs, set the variable to include the PostgreSQL client
directory, psql. For example, set the variable as follows:
$ export PATH; PATH=${PATH}:${PGHOME}
Using a C shell:
$ setenv PATH ${PGHOME}:${PATH}
4. Verify that you can connect to the PostgreSQL database.
To connect to the PostgreSQL database, launch the psql utility and enter the connectivity information.
Connecting to a Sybase ASE Database from Windows

For native connectivity, install the version of Open Client appropriate for your database version. To ensure
compatibility between Informatica and databases, use the appropriate database client libraries.
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.
If you want to create, restore, or upgrade a Sybase ASE repository, set allow nulls by default to TRUE at the
database level. Setting this option changes the default null type of the column to null in compliance with the
SQL standard.

You can configure native connectivity to a Sybase ASE database to increase performance.
1. Verify that the SYBASE environment variable refers to the Sybase ASE directory.
For example:
SYBASE=C:\SYBASE
2. Verify that the PATH environment variable includes the Sybase OCS directory.
For example:
PATH=C:\SYBASE\OCS-15_0\BIN;C:\SYBASE\OCS-15_0\DLL
3. Configure Sybase Open Client to connect to the database that you want to access.
Use SQLEDIT to configure the Sybase client, or copy an existing SQL.INI file (located in the %SYBASE%
\INI directory) and make any necessary changes.
Select NLWNSCK as the Net-Library driver and include the Sybase ASE server name.
Enter the host name and port number for the Sybase ASE server. If you do not know the host name and
port number, check with the system administrator.
4. Verify that you can connect to the Sybase ASE database.
To connect to the database, launch ISQL and enter the connectivity information. If you fail to connect to
the database, verify that you correctly entered all of the connectivity information.
User names and database names are case sensitive.
Connecting to a Teradata Database from Windows

Install and configure native client software on the machines where the Data Integration Service and
PowerCenter Integration Service process runs and where you install Informatica Developer and the
PowerCenter Client. To ensure compatibility between Informatica and databases, use the appropriate
database client libraries. You must configure connectivity to the following Informatica components on
Windows:
• Integration Service. Install the Teradata client, the Teradata ODBC driver, and any other Teradata client
software that you might need on the machine where the Data Integration Service and PowerCenter
Integration Service run. You must also configure ODBC connectivity.
• Informatica Developer. Install the Teradata client, the Teradata ODBC driver, and any other Teradata client
software that you might need on each machine that hosts a Developer tool that accesses Teradata. You
must also configure ODBC connectivity.
• PowerCenter Client. Install the Teradata client, the Teradata ODBC driver, and any other Teradata client
software that you might need on each PowerCenter Client machine that accesses Teradata. Use the
Workflow Manager to create a database connection object for the Teradata database.
Note: Based on a recommendation from Teradata, Informatica uses ODBC to connect to Teradata. ODBC is a
native interface for Teradata.
Connecting to a Teradata Database from Windows 279

You can configure ODBC connectivity to a Teradata database.
1. Create an ODBC data source for each Teradata database that you want to access.
To create the ODBC data source, use the driver provided by Teradata.
Create a System DSN if you start the Informatica service with a Local System account logon. Create a
User DSN if you select the This account log in option to start the Informatica service.
2. Enter the name for the new ODBC data source and the name of the Teradata server or its IP address.
To configure a connection to a single Teradata database, enter the DefaultDatabase name. To create a
single connection to the default database, enter the user name and password. To connect to multiple
databases, using the same ODBC data source, leave the DefaultDatabase field and the user name and
password fields empty.
3. Configure Date Options in the Options dialog box.
In the Teradata Options dialog box, specify AAA for DateTime Format.
4. Configure Session Mode in the Options dialog box.
When you create a target data source, choose ANSI session mode. If you choose ANSI session mode,
Teradata does not roll back the transaction when it encounters a row error. If you choose Teradata
session mode, Teradata rolls back the transaction when it encounters a row error. In Teradata mode, the
Integration Service cannot detect the rollback and does not report this in the session log.
5. Verify that you can connect to the Teradata database.
To test the connection, use a Teradata client program, such as WinDDI, BTEQ, Teradata Administrator, or
Teradata SQL Assistant.

Appendix D
Updating the DynamicSections

Parameter of a DB2 Database
• DynamicSections Parameter Overview, 281

• Setting the DynamicSections Parameter, 281
DynamicSections Parameter Overview

IBM DB2 packages contain the SQL statements to be executed on the database server. The DynamicSections
parameter of a DB2 database determines the maximum number of executable statements that the database
driver can have in a package. You can raise the value of the DynamicSections parameter to allow a larger
number of executable statements in a DB2 package. To modify the DynamicSections parameter, connect to
the database using a system administrator user account with BINDADD authority.
Setting the DynamicSections Parameter

Use the DataDirect Connect for JDBC utility to raise the value of the DynamicSections parameter in the DB2
database.
To use the DataDirect Connect for JDBC utility to update the DynamicSections parameter, complete the
following tasks:
• Download and install the DataDirect Connect for JDBC utility.

• Run the Test for JDBC tool.
Downloading and Installng the DDconnect JDBC Utility

Download the DataDirect Connect for JDBC utility from the DataDirect download web site to a machine that
has access to the DB2 database server. Extract the contents of the utility file and run the installer.
1. Go to the DataDirect download site:

http://www.datadirect.com/support/product-documentation/downloads
2. Choose the Connect for JDBC driver for an IBM DB2 data source.
281
3. Register to download the DataDirect Connect for JDBC Utility.
4. Download the utility to a machine that has access to the DB2 database server.
5. Extract the contents of the utility file to a temporary directory.
6. In the directory where you extracted the file, run the installer.
The installation program creates a folder named testforjdbc in the installation directory.
Running the Test for JDBC Tool

After you install the DataDirect Connect for JDBC Utility, run the Test for JDBC tool to connect to the DB2
database. You must use a system administrator user account with the BINDADD authority to connect to the
database.
1. In the DB2 database, set up a system adminstrator user account with the BINDADD authority.
2. In the directory where you installed the DataDirect Connect for JDBC Utility, run the Test for JDBC tool
(testforjdbc).
3. On the Test for JDBC Tool window, click Press Here to Continue.
4. Click Connection > Connect to DB.
5. In the Database field, enter the following text:
jdbc:datadirect:db2://
HostName:PortNumber;databaseName=DatabaseName;CreateDefaultPackage=TRUE;ReplacePackag
e=TRUE;DynamicSections=3000
HostName is the name of the machine hosting the DB2 database server.
PortNumber is the port number of the database.
DatabaseName is the name of the DB2 database.
6. In the User Name and Password fields, enter the system administrator user name and password you use
to connect to the DB2 database.
7. Click Connect, and then close the window.
282 Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Index
A connecting (continued)
Integration Service to Oracle (UNIX) 253
AddLicense (infacmd) Integration Service to Oracle (Windows) 276
troubleshooting 186 Integration Service to PostgreSQL (UNIX) 255
Analyst Service Integration Service to PostgreSQL (Windows) 277
after creating 224 Integration Service to Sybase ASE (UNIX) 257
configuring 222 Integration Service to Sybase ASE (Windows) 278
creating 222 Microsoft Excel to Integration Service 273
prerequisites 194 UNIX databases 246
temporary directories 194 Windows databases 271
application services Windows using JDBC 271
Content Management Service 59 connections
Analyst Service 58 creating database connections 196, 199
Data Integration Service 61, 74 IBM DB2 properties 196
installation requirements 26, 39 Microsoft SQL Server properties 197
Metadata Manager Service 65 Oracle properties 199
Model Repository Service 71, 75 Content Management Service
monitoring Model Repository Service 74 configuring 220
ports 24, 37 creating 220
products 53
Search Service 78
D
B Data Integration Service
after creating 209
back up files configuring 206
before installing 27, 41 creating 206
before upgrading 27, 41 host file configuration 209
before installing the clients data object cache
overview 229 database requirements 61
verifying installation requirements 229 IBM DB2 database requirements 61
verifying minimum system requirements 229 Microsoft SQL Server database requirements 62
Oracle database requirements 62
database clients
C configuring 80
environment variables 80
catalina.out IBM DB2 client application enabler 79
troubleshooting installation 184 Microsoft SQL Server native clients 79
clients Oracle clients 79
configuring for secure domains 231 PostgreSQL client 79
code page compatibility Sybase open clients 79
application services 189 database connections
locale 189 creating 196
configuration database preparations
domains 189 repositories 53
environment variables 190 database requirements
environment variables on UNIX 191 data object cache 61
Kerberos files 83 Model repository 71
connecting PowerCenter repository 75
Integration Service to IBM DB2 (Windows) 247, 272 profiling warehouse 62
Integration Service to Informix (UNIX) 249 reference data warehouse 59
Integration Service to Informix (Windows) 272 workflow database 63
Integration Service to JDBC data sources (UNIX) 261 database user accounts
Integration Service to Microsoft Access 273 guidelines for setup 53
Integration Service to Microsoft SQL Server 273 databases
Integration Service to ODBC data sources (UNIX) 262 connecting to (UNIX) 246
283
databases (continued)
connecting to (Windows) 271 H
connecting to IBM DB2 247, 272 host file
connecting to Informix 249, 272 Data Integration Service 209
connecting to Microsoft Access 273 HTTPS
connecting to Microsoft SQL Server 273 installation requirements 29, 42
connecting to Netezza (UNIX) 251
connecting to Netezza (Windows) 275
connecting to Oracle 253, 276
connecting to PostgreSQL 255, 277 I
connecting to Sybase ASE 257, 278 i10Pi
connecting to Teradata (UNIX) 259 UNIX 32
connecting to Teradata (Windows) 279 Windows 45
repository 53 IATEMPDIR
testing connections 80 environment variables 28, 41
dbs2 connect IBM DB2
testing database connections 80 connecting to Integration Service (Windows) 247, 272
debug logs setting DB2CODEPAGE 272
troubleshooting the installation 184 setting DB2INSTANCE 272
Developer tool single-node tablespaces 76
third-party software requirements 229 IBM DB2 database requirements
DISPLAY data object cache 61
environment variables 41 domain repository 55, 71
domain configuration repository Metadata Manager repository 66
IBM DB2 database requirements 55, 71 Model repository database 55, 71
Microsoft SQL Server database requirements 56, 72 PowerCenter repository 76
Oracle database requirements 56 profiling warehouse 62
preparing databases 54 reference data warehouse 60
Sybase ASE database requirements 57 workflow repository 64
troubleshooting 185 infacmd
Domain configuration repository adding nodes to domains 185
PostgreSQL database requirements 56 pinging objects 186
domains infasetup
configuring 189 defining domains 185
overview 17 defining worker nodes 185
ports 24, 37 Informatica Administrator
logging in 195
Informatica clients
E installing in graphical mode 230
installing in silent mode 235
environment variables uninstalling 238, 240
configuring 190 Informatica Developer
configuring clients 231 configuring local workspace directory 232
configuring on UNIX 191 installing languages 231
database clients 80 local machines 232
INFA_TRUSTSTORE 231 remote machines 232
INFA_TRUSTSTORE_PASSWORD 231 Informatica server
installation 28, 41 uninstalling 238
LANG 189 Informatica services
LANG_C 189 installing in graphical mode 135
LC_ALL 189 installing in silent mode 179
LC_CTYPE 189 starting and stopping on UNIX 243
library paths on UNIX 191 troubleshooting 186
locale 189 Informix
UNIX 190 connecting to Integration Service (UNIX) 249
UNIX database clients 80 connecting to Integration Service (Windows) 272
installation
backing up files before 27, 41
G installation logs
descriptions 184
graphical mode installation requirements
installing Informatica clients 230 application service requirements 26, 39
installing Informatica services 135 environment variables 28, 41
keystore files 29, 42
port requirements 24, 37
truststore files 29, 42
isql
testing database connections 80
284 Index
J Metadata Manager repository (continued)
Microsoft SQL Server database requirements 68
JDBC optimizing IBM DB2 databases 66
connecting to (Windows) 271 Oracle database requirements 68
JDBC data sources system temporary tablespaces 66
connecting to (UNIX) 261 Metadata Manager Service
JRE_HOME after creating 219
environment variables 28, 41 configuring 215
creating 215
creating repository contents 219
K split domain 69
split domain considerations 69
Kerberos authentication Microsoft Access
configuration files 83 connecting to Integration Service 273
creating keytab files 89 Microsoft Azure SQL database requirements
creating service principal names 89 PowerCenter repository 76
generating keytab file name formats 84 Microsoft Excel
generating SPN formats 84 connecting to Integration Service 273
troubleshooting 195 using PmNullPasswd 273
Kerberos SPN Format Generator 85 using PmNullUser 273
keystore files Microsoft SQL Server
installation requirements 29, 42 connecting from UNIX 250
keytab files connecting to Integration Service 273
Kerberos authentication 84, 89 Microsoft SQL Server database requirements
data object cache 62
domain configuration repository 56, 72
L Metadata Manager repository 68

PowerCenter repository 76
LANG profiling warehouse 63
environment variables 189 reference data warehouse 60
locale environment variables 28, 41 workflow repository 64
languages minimum system requirements
client tools 231 nodes 26, 39
LC_ALL Model repository
environment variables 189 database requirements 71
locale environment variables 28, 41 IBM DB2 database requirements 55, 71
LC_CTYPE Oracle database requirements 73
environment variables 189 PostgreSQL database requirements 73
library paths users 205
environment variables 28 Model Repository Service
library requirements after creating 205
Windows 37 configuring 202
license keys creating 202
verifying 32, 45
licenses
adding 186
Linux
N
database client environment variables 80 Netezza
locale environment variables connecting from Informatica clients(Windows) 275
configuring 189 connecting from Integration Service (Windows) 275
localhost connecting to Informatica clients (UNIX) 251
Data Integration Service 209 connecting to Integration Service (UNIX) 251
log files node.log
catalina.out 184 troubleshooting installation 184
debug logs 184 nodes
installation 183 troubleshooting 185
installation logs 184 normal mode
node.log 184 PowerCenter Repository Service 212
types 183
login
troubleshooting 195 O
ODBC data sources
M connecting to (UNIX) 262

connecting to (Windows) 271
Metadata Manager repository odbc.ini file
heap sizes 66 sample 264
IBM DB2 database requirements 66
Index 285
operating mode PowerCenter Repository Service
PowerCenter Repository Service 212 after creating 211
optimization configuring 210
PowerCenter repository 76 creating 210
Oracle normal mode 212
connecting to Integration Service (UNIX) 253 pre-installation
connecting to Integration Service (Windows) 276 i10Pi on UNIX 32
Oracle database requirements i10Pi on Windows 45
data object cache 62 services on Windows 36
domain configuration repository 56 profiling warehouse
Metadata Manager repository 68 database requirements 62
Model repository 73 IBM DB2 database requirements 62
PowerCenter repository 76 Microsoft SQL Server database requirements 63
profiling warehouse 63 Oracle database requirements 63
reference data warehouse 60
workflow repository 65
Oracle Net Services
using to connect Integration Service to Oracle (UNIX) 253
R
using to connect Integration Service to Oracle (Windows) 276 reference data warehouse
overview database requirements 59
before installing the clients 229 IBM DB2 database requirements 60
Microsoft SQL Server database requirements 60
Oracle database requirements 60
P repositories
configuring native connectivity 78
patch requirements installing database clients 79
installation 23 preparing databases 53
Windows 37 repository content creation
PATH Metadata Manager Service 219
environment variables 28
pg_service.conf
PostgreSQL database requirements 77
PGSERVICEFILE environment variable
S
PostgreSQL database requirements 77 samples
Ping (infacmd) odbc.ini file 264
troubleshooting 186 Search Service
port requirements configuring 224
installation requirements 24, 37 creating 224
ports secure domains
application services 24, 37 configuring clients 231
domains 24, 37 Service Manager
requirements 24, 37 log files 184
PostgreSQL service principal names
connecting to Integration Service (UNIX) 255 creating 89
connecting to Integration Service (Windows) 277 Kerberos authentication 84
PostgreSQL database requirements services
Domain configuration repository 56 pre-installation tasks on Windows 36
Model repository 73 silent mode
pg_service.conf 77 installing Informatica clients 235
PGSERVICEFILE environment variable 77 installing Informatica services 179
PowerCenter repository 77 source databases
PowerCenter Client connecting through JDBC (UNIX) 261
third-party software requirements 229 connecting through ODBC (UNIX) 262
PowerCenter Integration Service split domain for Metadata Manager
after creating 215 considerations 69
configuring 213 definition 69
creating 213 SPN 84
PowerCenter repository sqlplus
database requirements 75 testing database connections 80
IBM DB2 database requirements 76 Sybase ASE
Microsoft Azure SQL database requirements 76 connecting to Integration Service (UNIX) 257
Microsoft SQL Server database requirements 76 connecting to Integration Service (Windows) 278
optimizing IBM DB2 databases 76 Sybase ASE database requirements
Oracle database requirements 76 domain configuration repository 57
PostgreSQL database requirements 77 PowerCenter repository 77
Sybase ASE database requirements 77 system requirements
users 212 application services 26, 39
minimum 22, 37
286 Index
T UNIX (continued)
database client variables 80
tablespaces environment variables 190
single nodes 76 i10Pi 32
target databases Kerberos SPN Format Generator 85
connecting through JDBC (UNIX) 261 library paths 191
connecting through ODBC (UNIX) 262 pre-installation 32
Teradata starting and stopping Informatica services 243
connecting to Informatica clients (UNIX) 259 user accounts 29
connecting to Informatica clients (Windows) 279 upgrades
connecting to Integration Service (UNIX) 259 backing up files before 27, 41
connecting to Integration Service (Windows) 279 user accounts
third-party software requirements Model repository 205
Developer tool 229 PowerCenter repository 212
PowerCenter Client 229 UNIX 29
troubleshooting Windows 42
creating domains 185 user principal names
domain configuration repository 185 formatting 89
Informatica services 186
joining domains 185
Kerberos authentication 195
licenses 186
W
logging in 195 Windows
pinging domains 186 i10Pi 45
truststore files installing Informatica clients in graphical mode 230
installation requirements 29, 42 installing Informatica services in graphical mode 135
library requirements 37
patch requirements 37
U pre-installation 45
user accounts 42
uninstallation workflow
rules and guidelines 238 IBM DB2 database requirements 64
UNIX Microsoft SQL Server database requirements 64
connecting to JDBC data sources 261 Oracle database requirements 65
connecting to ODBC data sources 262 workflows
database client environment variables 80 database requirements 63
Index 287

In 1040 InstallationForPowerCenterAndDataQuality en

Uploaded by

Copyright:

Available Formats

In 1040 InstallationForPowerCenterAndDataQuality 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 1040 InstallationForPowerCenterAndDataQuality en

Uploaded by

Copyright:

Available Formats

Informatica®

Installation for PowerCenter

Publication Date: 2020-04-20

Part I: Installation Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 1: Installation Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Part II: Before You Install the Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 2: Before You Install the Services on UNIX or Linux. . . . . . . . . . . . . . . 21

Chapter 3: Before You Install the Services on Windows. . . . . . . . . . . . . . . . . . . 36

Chapter 4: Prepare for Application Services and Databases. . . . . . . . . . . . . . . 52

Chapter 5: Prepare for Kerberos Authentication. . . . . . . . . . . . . . . . . . . . . . . . . 82

Chapter 6: Record Information for Installer Prompts. . . . . . . . . . . . . . . . . . . . . 92

Chapter 7: Introduction to the Services Installer. . . . . . . . . . . . . . . . . . . . . . . 100

Part III: Run the Services Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Chapter 8: Install Informatica Services in Console Mode. . . . . . . . . . . . . . . . 103

Chapter 9: Install Informatica Services in Graphical Mode. . . . . . . . . . . . . . . 135

Chapter 10: Run the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Chapter 11: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Part IV: After You Install the Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Chapter 12: Complete the Domain Configuration. . . . . . . . . . . . . . . . . . . . . . . 188

Chapter 13: Prepare to Create the Application Services. . . . . . . . . . . . . . . . . 193

Chapter 14: Create and Configure Application Services. . . . . . . . . . . . . . . . . 201

Chapter 15: Install the Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Chapter 16: Install in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Part VI: Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Chapter 17: Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Appendix A: Starting and Stopping Informatica Services. . . . . . . . . . . . . . . . . . . . 243

Appendix C: Connecting to Databases from Windows. . . . . . . . . . . . . . . . . . . . . . . 271

Appendix D: Updating the DynamicSections Parameter of a DB2 Database. . 281

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

• Installation Getting Started, 15

Installation Getting Started

• Checklist to Getting Started , 15

Checklist to Getting Started

 Understand high-level concepts:

 Start high-level planning:

Perform pre-installation tasks.

Run the installer.

Complete the configuration.

1. Verify code page compatibility.

Install the Informatica client tools.

Plan the Installation Components

16 Chapter 1: Installation Getting Started

The following image shows a high-level architecture of a domain on multiple nodes:

The domain has the following types of nodes:

Plan the Installation Components 17

Secure Data Storage

18 Chapter 1: Installation Getting Started

Informatica Client Tools

The following table describes the tools for PowerCenter:

Informatica Client Description

Plan the Installation Components 19

• Before You Install the Services on UNIX or Linux, 21

Before You Install the Services on

• Before You Begin Checklist , 21

Before You Begin Checklist