Download pdf - Informatica 9.0 Installation and Configuration Guide Documentation/3/IN_90... · Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter

Informatica (Version 9.0)

Installation and Configuration Guide

Informatica Installation and Configuration Guide

Version 9.0December 2009

Copyright (c) 1998-2009 Informatica. All rights reserved.

This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use anddisclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form,by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or internationalPatents and other Patents Pending.

Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided inDFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013©(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.

The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us inwriting.

Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange,PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange and InformaticaOn Demand are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and productnames may be trade names or trademarks of their respective owners.

Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rightsreserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All rightsreserved.Copyright © Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright 2007 Isomorphic Software. All rights reserved. Copyright © MetaIntegration Technology, Inc. All rights reserved. Copyright © Intalio. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © Adobe Systems Incorporated. Allrights reserved. Copyright © DataArt, Inc. All rights reserved. Copyright © ComponentSource. All rights reserved. Copyright © Microsoft Corporation. All rights reserved.Copyright © Rouge Wave Software, Inc. All rights reserved. Copyright © Teradata Corporation. All rights reserved. Copyright © Yahoo! Inc. All rights reserved. Copyright ©Glyph & Cog, LLC. All rights reserved.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and other software which is licensed under the Apache License,Version 2.0 (the "License"). You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing,software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See theLicense for the specific language governing permissions and limitations under the License.

This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software copyright ©1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under the GNU Lesser General Public License Agreement, which may be found at http://www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but notlimited to the implied warranties of merchantability and fitness for a particular purpose.

The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine,and Vanderbilt University, Copyright (©) 1993-2006, all rights reserved.

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution ofthis software is subject to terms available at http://www.openssl.org.

This product includes Curl software which is Copyright 1996-2007, Daniel Stenberg, <[email protected]>. All Rights Reserved. Permissions and limitations regarding thissoftware 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 withoutfee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

The product includes software copyright 2001-2005 (©) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms availableat http://www.dom4j.org/ license.html.

The product includes software copyright © 2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to termsavailable at http:// svn.dojotoolkit.org/dojo/trunk/LICENSE.

This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding thissoftware are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/license.html.

This product includes software copyright © 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at http://www.gnu.org/software/ kawa/Software-License.html.

This product includes OSSP UUID software which is Copyright © 2002 Ralf S. Engelschall, Copyright © 2002 The OSSP Project Copyright © 2002 Cable & WirelessDeutschland. Permissions and limitations regarding this software are subject to terms available at http://www.opensource.org/licenses/mit-license.php.

This product includes software developed by Boost (http://www.boost.org/) or under the Boost software license. Permissions and limitations regarding this software are subjectto terms available at http:/ /www.boost.org/LICENSE_1_0.txt.

This product includes software copyright © 1997-2007 University of Cambridge. Permissions and limitations regarding this software are subject to terms available at http://www.pcre.org/license.txt.

This product includes software copyright © 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to termsavailable at http:// www.eclipse.org/org/documents/epl-v10.php.

This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?License, http://www.stlport.org/doc/license.html, http://www.asm.ow2.org/license.html, http://www.cryptix.org/LICENSE.TXT, http://hsqldb.org/web/hsqlLicense.html, http://httpunit.sourceforge.net/doc/license.html, http://jung.sourceforge.net/license.txt , http://www.gzip.org/zlib/zlib_license.html, http://www.openldap.org/software/release/license.html, http://www.libssh2.org,http://slf4j.org/license.html, http://www.sente.ch/software/OpenSourceLicense.html, and http://fusesource.com/downloads/license-agreements/fuse-message-broker-v-5-3-license-agreement.

This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and DistributionLicense (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php) and the BSD License (http://www.opensource.org/licenses/bsd-license.php).

This product includes software copyright © 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this softwareare subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab. For furtherinformation please visit http://www.extreme.indiana.edu/.

This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775;6,640,226; 6,789,096; 6,820,077; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,254,590; 7,281,001; 7,421,458; and 7,584,422, international Patents and otherPatents Pending.

DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the impliedwarranties of non-infringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. Theinformation provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation issubject to change at any time without notice.

NOTICES

This Informatica product (the “Software”) includes certain drivers (the “DataDirect Drivers”) from DataDirect Technologies, an operating company of Progress SoftwareCorporation (“DataDirect”) which are subject to the following terms and conditions:

1.THE DATADIRECT DRIVERS ARE PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OFTHE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACHOF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

Part Number: PC-ICG-90000-0003

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Chapter 1: Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Informatica Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Informatica Data Quality and Informatica Data Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Informatica Services and Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Informatica Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Informatica Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2: Before You Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Quick Start Guides. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Minimum System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Informatica Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Informatica Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Database Schemas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Temporary Disk Space Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Before You Install Informatica Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Verify the License Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Create a System User Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Set Up the Domain Configuration Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Determine Port Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Verify Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Set Up the X Window Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Set Up a Keystore File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Before You Install Informatica Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

PowerCenter Mapping Architect for Visio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 3: Informatica Services Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Informatica Services Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installing in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installing in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 4: Informatica Clients Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Informatica Clients Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Installing in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Installing in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Table of Contents i

Step 1. Create the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Step 2. Run the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 5: After You Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Informatica Platform Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Verify Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Update Statistics for the Domain Configuration Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Configure POSIX Asynchronous I/O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Set Up the Graphics Display Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Configure the Web Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Install Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Data Quality and Data Services Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Verify the Setup for 32-bit and 64-bit Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Install the Database Client Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

PowerCenter Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Verify the Setup for 32-bit and 64-bit Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Verify Code Page Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Install the Database Client Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Verify Third-Party Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Verify the Data Transformation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 6: Repository Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Repository Database Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Data Quality and Data Services Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Oracle Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

IBM DB2 Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Microsoft SQL Server Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

PowerCenter Repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Rules and Guidelines for Database and User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Oracle (Metadata Manager). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Oracle (PowerCenter, Data Analyzer, Metadata Manager). . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

IBM DB2 (PowerCenter). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

IBM DB2 (Metadata Manager). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Microsoft SQL Server (Data Analyzer). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Microsoft SQL Server (Metadata Manager). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Chapter 7: Starting Informatica. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Starting Informatica Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Starting Informatica Data Services and Data Quality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Starting Informatica PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Starting and Stopping Informatica. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Starting and Stopping Informatica on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

ii Table of Contents

Starting and Stopping Informatica on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Stopping Informatica in the Administrator Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Rules and Guidelines for Starting or Stopping Informatica. . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Logging in to the Administrator Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Creating the Application Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Creating Application Services for Data Services and Data Quality. . . . . . . . . . . . . . . . . . . . . . . 51

Creating Application Services for PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Starting the Developer Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Logging in to the Analyst Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Starting the PowerCenter Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configuring the Informatica Windows Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 8: PowerCenter Data Profiling and Data Masking. . . . . . . . . . . . . . . . . . . . . . . . . . 55Setting Up a Data Profiling Warehouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Step 1. Create a Data Profiling Warehouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Step 2. Configure Connectivity to the Data Profiling Warehouse. . . . . . . . . . . . . . . . . . . . . . . . 56

Setting up the Data Masking Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Step 1. Register the Plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Step 2. Apply the Data Masking License Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Chapter 9: Troubleshooting an Informatica Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Installation Troubleshooting Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Installation Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Debug Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Summary Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

File Installation Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Service Manager Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Troubleshooting Domains and Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Creating the Domain Configuration Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Creating or Joining a Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Starting Informatica9.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Pinging the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Adding a License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Troubleshooting the PowerCenter Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Installation Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Chapter 10: JDBC and ODBC Driver Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64JDBC and ODBC Driver Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

JDBC Driver Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Installing the Informatica JDBC Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Updating the CLASSPATH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

ODBC Driver Installation on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Installing the Informatica ODBC Driver on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Table of Contents iii

Updating the System Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Configuring the Informatica ODBC Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

ODBC Driver Installation on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Installing the Informatica ODBC Driver on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Updating the Shared Library Environment Variable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Updating odbc.ini. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 11: Informatica Utilities Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Informatica Utilities Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Command Line Programs and Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Configuring the PowerCenter Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Configuring the Metadata Manager Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Chapter 12: Informatica Documentation Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Documentation Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Installing the Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Viewing Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Chapter 13: Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Uninstallation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Rules and Guidelines for Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Running the Uninstaller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Before You Uninstall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Uninstallation Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Running the Uninstaller on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Running the Uninstaller on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Uninstalling in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Uninstalling in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Chapter 14: Informatica Platform Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Connectivity Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Domain Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Informatica Data Quality and Informatica Data Services Connectivity. . . . . . . . . . . . . . . . . . . . . . . . 77

Model Repository Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

PowerCenter Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Repository Service Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Integration Service Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

PowerCenter Client Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Data Analyzer and Metadata Manager Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Native Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Establishing Native Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

ODBC Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

iv Table of Contents

Establishing ODBC Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

JDBC Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Appendix A: Connecting to Databases from Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Connecting to Databases from Windows Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Connecting to an IBM DB2 Universal Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Configuring Native Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Configuring ODBC Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Connecting to Microsoft Access and Microsoft Excel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87


Connecting to a Microsoft SQL Server Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88



Connecting to an Oracle Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89



Connecting to a Sybase ASE Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90



Connecting to a Teradata Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91


Appendix B: Connecting to Databases from UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Connecting to Databases from UNIX Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Connecting to Microsoft SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Connecting to an IBM DB2 Universal Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94


Connecting to an Informix Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96


Connecting to an Oracle Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98


Connecting to a Sybase ASE Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Configuring Native Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Connecting to a Teradata Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Configuring ODBC Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Connecting to an ODBC Data Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Sample odbc.ini File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Appendix C: LANG Environment Variable for Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111LANG Environment Variable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Table of Contents v

PrefaceThe Installation and Configuration Guide is written for the system administrator who is responsible for installing theInformatica product. This guide assumes you have knowledge of operating systems, relational database concepts,and the database engines, flat files, or mainframe systems in your environment. This guide also assumes you arefamiliar with the interface requirements for your supporting applications.

vi

C H A P T E R 1

Installation OverviewThis chapter includes the following topics:

¨ Informatica Installation, 1

¨ Informatica Services and Clients, 2

Informatica InstallationThe Informatica platform consists of a server component (Informatica Services) and a client component(Informatica Clients). Informatica provides separate installers to install Informatica Services and InformaticaClients.

When you install the Informatica platform, you install the components for the following products:

¨ Informatica Data Quality

¨ Informatica Data Services

¨ PowerCenter

The Informatica platform also includes components for PowerExchange.

Informatica Data Quality and Informatica Data ServicesData Quality and Data Services use the same services and client applications. The installation for Data Qualityand Data Services follow the same procedure.

To install Data Quality or Data Services, complete the following tasks:

1. Complete the pre-installation tasks. Complete the pre-installation tasks to ensure that you can successfullyrun the installers and create and run the services on the domain.

2. Install Informatica Services. Use the server installer to install Informatica Services on one or more Windowsor UNIX machines. Create a node and configure the domain. Specify the database to store the domainconfiguration information.

3. Perform the post-installation configuration tasks. Prepare the database and user account for the Modelrepository and configure the machine to ensure that you can run the domain services and components.

4. Install Informatica Developer. Use the client installer to install Informatica Developer. You can install theDeveloper tool on one or more Windows machines.

After installation, log in to the Administrator tool and create and configure the following services:

¨ Model Repository Service

¨ Data Integration Service

1

¨ Analyst Sevice

PowerCenterTo install PowerCenter, complete the following tasks:

1. Complete the pre-installation tasks. Complete the pre-installation tasks to ensure that you can successfullyrun the installers and create and run the services on the domain.

2. Install Informatica Services. Use the server installer to install Informatica Services on one or more Windowsor UNIX machines. Create a node and configure the domain. Specify the database to store the domainconfiguration information.

3. Perform the post-installation configuration tasks. Prepare the database and user account for thePowerCenter repository and configure the machine to ensure that you can run the domain services andcomponents.

4. Install the PowerCenter Client. Use the client installer to install the PowerCenter Client. You can installthePowerCenter Client on one or more Windows machines.

After installation, log in to the Administrator tool and create and configure the following services:

¨ PowerCenter Repository Service

¨ PowerCenter Integration Service

Optionally, you can create a Metadata Manager Service to run Metadata Manager and Business Glossary and aReporting Service to run reports in Data Analyzer.

Informatica Services and ClientsThe Informatica platform supports the service-oriented architecture of Informatica products. When you run theserver installer, all the services and components required by the Informatica products are installed. The clientinstaller allows you to select the client application to install for your product.

Informatica ServicesThe domain is the main administrative unit for the informatica platform. The Informatica domain is a collection ofnodes that represent the machines on which the application services run. The Informatica domain has a ServiceManager to manage operations and services in the domain and perform domain operations on each node. You usethe Administrator tool to manage the Informatica domain.

You can run the server installer multiple times to install on more than one machine.

If you install on a single machine, you create a domain and a node on the machine. If you install on multiplemachines, you can create multiple domains with one or more nodes in each domain or you can create one domainfor all nodes.

If you install on multiple machines, you must create an Informatica domain and a node when you installInformatica Services for the first time. When you install on another machine, you can create another domain andnode, or you can create a node and join the node to an existing domain. You manage each domain through aseparate Administrator tool.

You can install Informatica Services in graphical mode on Windows and in graphical mode or console mode onUNIX. The installation process creates a service named Informatica9.0 that runs as a service on Windows and asa daemon on UNIX. When you start Informatica9.0, it starts the Service Manager, which manages all domainoperations.

2 Chapter 1: Installation Overview

Informatica Data Quality and Informatica Data ServicesThe Informatica domain has the following application services for Data Quality and Data Services:

¨ Data Integration Service. Performs data integration tasks for the Analyst tool and and the Developer tool andstores metadata in a Model repository.

¨ Model Repository Service. Manages connections to the Model repository.

¨ Analyst Service. Runs Informatica Analyst.

PowerCenterThe Informatica domain has the following application services for PowerCenter:

¨ PowerCenter Integration Service. Runs sessions and workflows created in the PowerCenter Client andstored in the PowerCenter repository.

¨ PowerCenter Repository Service. Manages connections to the PowerCenter repository.

¨ Metadata Manager Service. Runs the Metadata Manager application and manages access to metadata in theMetadata Manager warehouse.

¨ Reporting Service. Runs the Data Analyzer application. Use Data Analyzer to create and run Informaticareports.

¨ Web Services Hub. Allows client applications to access PowerCenter workflows as web services.

¨ SAP BW Service. Listens for RFC requests from SAP BW, initiates workflows to extract from or load to SAPBW, and sends log events to the Log Manager.

¨ PowerCenter Orchestration. Application that models business processes with standard Business ProcessModeling Notation (BPMN). Includes the Orchestration server, Human Workflow, Administration Console, andrun-time repository components.

Informatica ClientsInformatica Clients consist of client applications and web applications that you use to access the services in thedomain. You can install Informatica Clients on Windows in graphical mode or silent mode.

Informatica Data Quality and Informatica Data ServicesData Quality and Data Services have the following clients:

¨ Informatica Developer. Use the client installer to install Informatica Developer. The Developer tool is a clientapplication that you use to create and run mappings, data objects, and virtual databases. Objects created inthe Developer tool are stored in a Model repository and are run by a Data Integration Service.

¨ Informatica Analyst. After you install Informatica Services, you can log in to the Administrator tool to create anAnalyst Service to run the Analyst tool. The Analyst tool is a web application that you use to create profiles andscorecards. Objects created in the Analyst tool are stored in a Model repository and are run by a DataIntegration Service.

PowerCenterUse the client installer to install the following client applications for PowerCenter:

¨ PowerCenter Client. Use the PowerCenter Client to define sources and targets, create transformations andbuild mappings, and create workflows to run mappings. The objects are stored in a PowerCenter repository andrun by a PowerCenter Integration Service.

Informatica Services and Clients 3

¨ Metadata Manager Custom Metadata Configurator. Use the Custom Metadata Configurator to create custommodels to generate PowerCenter objects from new metadata source files. This application is installed with thePowerCenter Client by default.

¨ Orchestration Designer. Use the Orchestration Designer to define business processes, interface businessprocesses with web services, and generate Business Process Executable Language (BPEL) processes for usewith the Orchestration Server. This application is installed with the PowerCenter Client by default.

After you install Informatica Services, you can log in to the Administrator tool to create application services to runthe following web applications:

¨ Metadata Manager and Business Glossary. Use Metadata Manager to browse and analyze metadata fromdisparate metadata repositories. It includes a business glossary for consistency in the definition of the businessterms in the metadata. The Metadata Manager Service runs the Metadata Manager and Business Glossaryapplication.

¨ Data Analyzer. Use Data Analyzer to run reports to analyze PowerCenter metadata. The Reporting Serviceruns the Data Analyzer application.

¨ Web Services Hub Console. Use the Web Services Hub Console to manage the web services you create inPowerCenter. The Web Services Hub runs the Web Services Hub Console.

4 Chapter 1: Installation Overview

C H A P T E R 2

Before You InstallThis chapter includes the following topics:

¨ Pre-Installation Tasks, 5

¨ Minimum System Requirements, 6

¨ Database Schemas, 7

¨ Temporary Disk Space Requirements, 8

¨ Before You Install Informatica Services, 8

¨ Before You Install Informatica Clients, 14

Pre-Installation TasksBefore you start the installation, set up the machine so it meets the requirements for installing and running theInformatica platform.

Review the installation pre-requisites and ensure that the machine meets the requirements. Verify that thedatabase server has adequate disk space for the domain configuration.

Before you install Informatica Services, complete the following pre-installation steps:

¨ Verify that you have the license key for the product you want to install.

¨ Create a system user account to run the installer.

¨ Set up the database and user account for the Informatica domain configuration.

¨ Determine which port numbers to use for the node and domain application services.

¨ Set up the environment variables used by Informatica.

¨ If you install on UNIX, set up the X Window server.

¨ Optionally, set up a keystore file for a secure connection.

Before you install the PowerCenter Client, verify that Microsoft Visio is installed on the machine.

Quick Start GuidesInformatica provides Quick Start guides for the Informatica installation. You can use the installation Quick Startguides to track the information you will need when you install Informatica, such as database names andconnection strings, user accounts, and port numbers.

You can get the Quick Start guides from the Documentation Center at http://my.informatica.com or by installing theInformatica documentation.

5

RELATED TOPICS:¨ “Installing the Informatica Documentation” on page 71

Minimum System RequirementsThe minimum requirements for Informatica Services depends on the domain components and application servicesyou use. The requirements for Informatica Clients depend on the client application you install.

Informatica ServicesYou can create an Informatica domain with one node and run all application services on the same node. If youcreate an Informatica domain with multiple nodes, you can run the application services on separate nodes.

The following table describes the minimum system requirements for a domain with different node configurations:

Component Processor RAM DiskSpace

Operating System

Domain with all Data Quality, DataServices, and PowerCenter servicesrunning on one node

4 CPU 8 GB 20 GB Windows 2003 / 2008Sun SolarisHP-UXIBM AIXRed Hat LinuxSUSE Linux

Domain with Data Quality and DataServices application services runningon one node:- Data Integration Service- Model Repository Service- Analyst Service

2 CPU 4 GB 20 GB

Domain with all PowerCenter servicesrunning on one node

2 CPU 4 GB 4 GB

Domain with all PowerCenter servicesrunning on one node except MetadataManager Service and Reporting Service

1 CPU 2 GB 3 GB

Metadata Manager Service running ona separate node

2 CPU 2 GB 3 GB

Reporting Service running on aseparate node

1 CPU 512 3 GB

Orchestration Server running on aseparate node

1 CPU 512 MB 3 GB

Metadata Manager Agent 1 CPU 512 MB 220 MB Windows 2003 / 2008

6 Chapter 2: Before You Install

Informatica ClientsYou can install Informatica Developer and the PowerCenter Client on the same machine or on separate machines.You can also install the clients on multiple machines.

The following table describes the minimum system requirements to run Informatica Clients:

Client Processor RAM DiskSpace

Operating System

PowerCenter Client 1 CPU 512 MB 1.2 GB Windows 2003 / 2008 / XP

Informatica Developer 1 CPU 512 MB 900 MB Windows 2003 / 2008 / XP

Database SchemasInformatica components store metadata in relational database repositories. The domain also stores configurationinformation in a domain configuration database. The database requirements depend on the application servicesyou create in the domain and the number of data integration objects you build and store in the repositories.

You must set up the database for the domain configuration before you start the installation process. You specifythe database connection information during installation.

After installation, set up the database for a repository before you create the application service in the domain. Youspecify the database connection information when you create the service.

The following table describes the database requirements for the Informatica components:

Informatica Component Database Type DiskSpace

Comments

Informatica domainconfiguration repository

IBM DB2 UDBMicrosoft SQL ServerOracle

200 MB Set up the database schema before you startthe installation process.

Model repository IBM DB2 UDBMicrosoft SQL ServerOracle

200 MB Set up the database before you create theModel Repository Service. Allocate morespace based on the amount of metadata youwant to store.

PowerCenter repository IBM DB2 UDBMicrosoft SQL ServerOracle

35 MB Set up the database before you create thePowerCenter Repository Service. Allocatemore space based on the amount of metadatayou want to store.

PowerCenter Data profilingwarehouse

IBM DB2 UDBMicrosoft SQL ServerOracle

256 MB Set up the database before you create theMetadata Manager Service.Allocate more space based on the followingfactors:- The amount of data you intend to profile.- Mode you run profile sessions: verbose or

normal.- Types of tables: full or sampling.- Frequency you purge the Data Profiling

warehouse.

Database Schemas 7

Informatica Component Database Type DiskSpace

Comments

Data Analyzer repository IBM DB2 UDBMicrosoft SQL ServerOracle

60 MB Set up the database before you create theReporting Service.

Metadata Manager repository IBM DB2 UDBMicrosoft SQL ServerOracle

1 GB Set up the database before you create theMetadata Manager Service.

Data object cache database IBM DB2 UDBMicrosoft SQL ServerOracle

200 MB Set up the database if you enable data objectcaching. Create a connection object andassociate with a Data Integration Service.Allocate more space based on the amount ofdata you want to cache.

Staging database IBM DB2 UDBMicrosoft SQL ServerOracle

200 MB Set up the database before you create theAnalyst Service. Allocate more space based onthe amount of metadata you want to store.

Temporary Disk Space RequirementsThe installer writes temporary files to the hard disk. Verify that you have enough available disk space on themachine to support the installation. When the installation completes, the installer deletes the temporary files andreleases the disk space.

The following table describes the temporary disk space requirements during installation:

Product Operating System Disk Space

Installer Windows or UNIX 1 GB

Informatica Services UNIX 2 GB

Windows 605 MB

Informatica Clients Windows 550 MB

Before You Install Informatica ServicesVerify that the prerequisites and minimum requirements for installation are met. If the machine where you installInformatica Services is not configured correctly, the installation can fail.


Verify the License KeyBefore you install the software, verify that you have the license key available. You can get the license key in thefollowing ways:

¨ Installation DVD. If you receive the Informatica installation files in a DVD, the license key file is included in theInformatica License Key CD.

¨ FTP download. If you download the Informatica installation files from the Informatica Electronic SoftwareDownload (ESD) site, the license key is in an email message from Informatica. Copy the license key file to adirectory accessible to the user account that installs Informatica.

Contact Informatica Global Customer Support if you do not have a license key or if you have an incrementallicense key and you want to create a domain.

PowerCenter Real-Time EditionIf you purchase PowerCenter Real-Time Edition, you receive two license keys. The PowerCenter Real-TimeEdition requires a license key for the PowerCenter real-time components and a separate license key for thePowerCenter Orchestration Server.

During installation, use the PowerCenter Real-Time Edition license key.

After installation, copy the Orchestration Server license key file to the following directory:

<InformaticaInstallationDir>/OrchestrationServer/var/config

Create a System User AccountCreate a system user account to perform the installation and to run the Informatica9.0 service or daemon. Verifythat the user account you use to install Informatica has write permission to the installation directory.

Windows User AccountOn Windows, you can install Informatica with the user account logged in to the machine and run it under anotheruser account. You can create a local account or a domain account to install Informatica or run the Informatica9.0service.

Note: To access a repository on Microsoft SQL Server that uses Windows integrated security, create a domainaccount.

The user accounts require the following permission to run the installer or run the Informatica9.0 service:

¨ Logged in user account. The user account must be a member of the Administrators group and have the Logon 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 asa service and Act as operating system permissions. You do not have to log in with this user account before youinstall Informatica. During installation, you can specify the user account to run the Informatica9.0 service.

UNIX User AccountOn UNIX, create a user account specifically to run the Informatica9.0 daemon.

Set Up the Domain Configuration DatabaseSet up a database and user account for the domain configuration information. The domain configuration databasestores metadata for the domain. When you install Informatica, you provide the database and user account

Before You Install Informatica Services 9

information for the domain configuration database. The Informatica installer uses JDBC to communicate with thedomain configuration database.

For more information about configuring the database, see the documentation for your database system.

Use the following rules and guidelines when you set up the domain configuration database and user account:

¨ The database must be accessible to all gateway nodes in the Informatica domain.

¨ The domain configuration can be in the same database schema as the PowerCenter, Metadata Manager, orData Analyzer repositories. Likewise, the Model repository can be in the same database schema as thePowerCenter, Metadata Manager, or Data Analyzer repositories. However, the domain configuration and theModel repository cannot be in the same database schema.

¨ If you create more than one domain, each domain configuration database must have a separate user account.

Oracle Database RequirementsUse the following guidelines when you set up the database on Oracle:

¨ Set the open_cursors parameter to 1000.

¨ The database user account must have the CONNECT, RESOURCE, and CREATE VIEW privileges.

IBM DB2 Database RequirementsUse the following guidelines when you set up the repository on IBM DB2:

¨ 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 following configuration parameters:

Parameter Value

applheapsz 8192

appl_ctl_heap_sz 8192

logfilsiz 8000

DynamicSections 1000

maxlocks 98

locklist 50000

auto_stmt_stats ONNote: For IBM DB2 9.5 only

¨ Set the tablespace pageSize parameter to 32768.

In a single-partition database, specify a tablespace that meets the pageSize requirements. If you do not specifya tablespace, the default tablespace must meet the pageSize requirements.

In a multi-partition database, you must specify a tablespace that meets the pageSize requirements.


Define the tablespace on a single node.

¨ The database user account must have the CREATETAB and CONNECT privileges.

Note: The default value for DynamicSections in DB2 is too low for the Informatica domain configuration repositoryand Model repository. Informatica requires a larger DB2 package than the default. When you set up the DB2database for the domain configuration repository or a Model repository, you must set the DynamicSectionsparameter to at least 1000. If the DynamicSections parameter is set to a lower number, you can encounterproblems when you install Informatica or when you work with the Analyst tool or Developer tool. The followingerror message can appear:

[informatica][DB2 JDBC Driver]No more available statements. Please recreate your package with a larger dynamicSections value.

Microsoft SQL Server Database RequirementsUse the following guidelines when you set up the repository on Microsoft SQL Server:

¨ Set the read committed isolation level to READ_COMMITTED_SNAPSHOT to minimize locking contention.

To set the isolation level for the database, run the following command:

ALTER DATABASE DatabaseName SET READ_COMMITTED_SNAPSHOT ONTo verify that the isolation level for the database is correct, run the following command:

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 permissions.

Determine Port AvailabilityThe installer sets up the ports for components in the Informatica domain, and it designates the ports to use forapplication service processes that run on the node where you install Informatica.

You can specify the port numbers to use for the components and a range of port numbers to use for theapplication services, or you can use the default port numbers provided by the installer. Verify that the portnumbers are available on the machines where you install Informatica Services.

The following table describes the ports you specify during installation:

Port Type Description

Domain port Port number used by the domain. Default is 6005.

Service Manager port Port number used by the Service Manager on the node. The Service Manager listens forincoming connection requests on this port. Client applications use this port to communicatewith the services in the domain. This is the port that the Informatica command line programsuse to communicate to the domain. This is also the port for the SQL data service JDBC/ODBCdriver. Default is 6006.

Service Manager shutdownport

Port number that controls server shutdown for the domain Service Manager. The ServiceManager listens for shutdown commands on this port. Default is 6008.

Informatica Administrator port Port number used by the Administrator tool. Default is 6007.


Port Type Description

Informatica Administratorshutdown port

Port number that controls server shutdown for the Administrator tool. The Administrator toollistens for shutdown commands on this port. Default is 6009.

Range of ports forapplication services

Range of port numbers that can be assigned to the application service processes that run onthe node. When you create an application service in the domain, the Service Manager assignsthe first available port in this range to the service process. At a minimum, the number of portsin the range must be equal to the number of application service processes that will run on thenode. Default is 6013 to 6113.

Guidelines for Port ConfigurationThe 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 thatyou specify for the application service processes.

¨ The highest number in the range of port numbers that you specify must be at least three numbers higher thanthe lowest port number. For example, if the minimum port number in the range is 6400, the maximum portnumber must be at least 6403.

¨ The port numbers that you specify for the domain, domain and node components, and application serviceprocesses cannot be lower than 1025 or higher than 65535.

Verify Environment VariablesConfigure the environment variables to work with Informatica. Incorrectly configured environment variables cancause the Informatica domain or nodes to fail to start or can cause connection problems between the Informaticaclients and the domain.

The installer appends file paths required by Informatica to the PATH environment variable. Verify that the length ofthe PATH environment variable does not exceed the system limits and that the variable does not contain doublequotes.

On UNIX, create the environment variables with the system user account you will use for installation. Log in withthe account you plan to use to install Informatica and then create the environment variables.

The following table describes environment variables you configure before you install:

Variable OperatingSystem

Description

IATEMPDIR (InstallAnywhere) WindowsUNIX

Location of temporary files created during installation. Informaticarequires 1 GB disk space for temporary files.Configure the environment variable if you do not want to createtemporary files in the following locations:- /tmp directory on UNIX- default drive on Windows

JRE_HOME SUSE LinuxLinux EMT64

Clear the JRE_HOME environment variable.


Variable OperatingSystem

Description

Locale Environment Variables UNIX Use LANG and LC_ALL to set the UNIX code page.

X Window Server UNIX Location of the graphics display server. Required to install ingraphical mode.

JRE_HOMEIf you install Informatica Services on a machine with 32-bit or 64-bit SUSE Linux or Linux EMT64 operatingsystem, clear the JRE_HOME environment variable before you start the installation.

Locale Environment VariablesUse LANG and LC_ALL to set the UNIX code page for the installer.

Set the LANG and LC_ALL environment variables to the following values for the language that you use:

Language Value

English C

Japanese ja_JP.SJIS or ja_JP.PCK

Portuguese pt_BR.ISO8859-1, pt_BR.8859-15, or pt_BR

After you install, update the locale setting to one that is compatible with the code page of the repository.

Set Up the X Window ServerWhen you run the Informatica installer in graphical mode, you must use a graphics display server. On UNIX, thegraphics display server is typically an X Window server. If you do not have the X Window server installed on themachine where you want to install Informatica, you can install Informatica using an X Window server installed onanother machine. Use the DISPLAY variable to redirect output of the X Window server to another UNIX machine.

The following table lists the commands to set the DISPLAY environment variable:

Shell Command Example

C setenv DISPLAY <TCP/IP node of XWindow server>:0 setenv DISPLAY 10.1.50.23:0

Bash/Korn export DISPLAY=”<TCP/IP node of XWindow server>:0” export DISPLAY=”10.1.50.23:0”

Bourne DISPLAY=”<TCP/IP node of XWindow server>:0”export display

DISPLAY=”10.1.50.23:0”export display

If you do not know the IP address of a UNIX machine where the X Window server is installed, ask your networkadministrator. For more information about redirecting the DISPLAY variable, see the documentation from the UNIXvendor.

If the X Window server does not support the font that the Informatica installer uses, the installer can displayincorrect labels on the buttons. For example, the button labeled Test Connection can appear as Test Connecti....


Set Up a Keystore FileDuring installation, you can configure Informatica to use SSL certificates for secure communication between theAdministrator tool and the Service Manager. The installer can generate a self-signed certificate, or you can providea certificate signed by a certification authority.

When you create application services in the domain, you can also configure secure connection for Data Analyzer,Metadata Manager, and the Web Services Hub. Use the Administrator tool to specify the keystore files for theapplication services.

You can use the keytool utility to generate a keystore file to store the SSL keys and certificates for a secureconnection. Keytool is a key and certificate management utility to generate and administer SSL keys andcertificates. The keys and certificates are stored in a keystore file. You can use a self-signed certificate or onesigned by a certification authority (CA). To use a certificate signed by a CA, use keytool to generate a CertificateSigning Request (CSR) and apply for a digital identity certificate from a CA.

You can find the keytool utility in one of the following directories:

¨ %JAVA_HOME%\jre\bin¨ InformaticaInstallDir\java\binFor more information about using keytool, see the documentation on the Sun web site:

http://java.sun.com/javase/6/docs/technotes/tools/windows/keytool.html

Before You Install Informatica ClientsVerify that the prerequisites and minimum requirements for installation are met. If the machine where you installInformatica Clients is not configured correctly, the installation can fail.

PowerCenter Mapping Architect for VisioThe PowerCenter Client installation includes Mapping Architect for Visio, which requires Microsoft Visio andthe .NET Framework. The machine where you install the PowerCenter Client must have Microsoft Visio version2003 or 2007 installed before you start the installation.


C H A P T E R 3

Informatica Services InstallationThis chapter includes the following topics:

¨ Informatica Services Installation Overview, 15

¨ Installing in Graphical Mode, 15

¨ Installing in Console Mode, 20

Informatica Services Installation OverviewYou can install Informatica Services on a Windows or UNIX machine. On Windows, you can run the installer ingraphical mode. On UNIX, you can run the installer in graphical or console mode.

Complete the pre-installation tasks to prepare for the installation. You can install Informatica Services on multiplemachines. After installation, use the Administrator tool to log in to the domain and create and configure theapplication services.

You can install Informatica from a DVD or from the root of the directory where you download the installation files.

Note: Use the GNU Tar program to extract the installation files in Linux and UNIX. All Linux versions ship with theGNU Tar program even if it is not explicitly documented.

Installing in Graphical ModeYou can install Informatica Services in graphical mode on Windows or UNIX.

1. Verify that your environment meets the minimum system requirements and complete the pre-installationtasks.

2. Log in to the machine with a system user account.

3. Close all other applications.

4. To begin the installation on Windows, run install.bat from the root directory.

To begin the installation on UNIX, use a shell command line to run install.sh from the root directory, and thenselect the option for graphical mode installation.

Note: On UNIX, if the install.sh file does not have sufficient permissions to execute after you extract theinstallation files, use the chmod command to add execute permissions to the file. Then run the file with thecommand ./install.sh

15

The Installation Pre-Requisites window displays the system requirements and the tasks to perform beforeinstallation. Verify that all installation requirements are met before you continue the installation.

5. Click Next.

6. On the License and Installation Directory window, enter the path and file name of the Informatica license key.

7. Enter the absolute path for the installation directory.

The directory names in the path must not contain spaces or the following especial characters: @|* $ # ! % ( ){ } [ ] , ; '

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

8. Click Next.

9. On the Pre-Installation Summary window, review the installation information, and click Install to continue.

The installer copies the Informatica files to the installation directory.

10. On the Domain Selection window, select whether to create or join a domain.

If you create a domain, the node on the current machine becomes a gateway node on the domain. Thegateway node contains a Service Manager that manages all domain operations.

11. If you join a domain, select the type of node you want to create on this machine.

To create a gateway node, select Configure this node as a gateway. To create a worker node, clear the option.

12. To set up a secure connection between the Service Manager and the Administrator tool, select EnableHTTPS for Informatica Administrator .

The following table describes the properties you set for an HTTPS connection:

Property Description

Enable HTTPS for InformaticaAdministrator

Set up a secure connection between Informatica Administrator and the ServiceManager. To use HTTP connection, clear this option.

Port The port to use for communication between Informatica Administrator and the ServiceManager.

Use a keystore generated bythe installer

Use a self-signed keystore file generated by the installer. The installer creates akeystore file named DEFAULT.keystore in the following location: InstallationDirectory\tomcat\conf\

Use an existing keystore Use a keystore file you create. You can use a keystore file with a self-signed certificateor a certificate signed by a certification authority.

Keystore password A plain-text password for the keystore file. Required if you use a keystore file you create.

Keystore file directory Location of the keystore file. Required if you use a keystore file you create.

13. Click Next.

If you create a domain, the Domain Configuration Database window appears.

If you join a domain, the Domain Configuration window appears. Skip to step 21.

14. On the Domain Configuration Database window, enter the database and user account information for thedomain configuration database.

The Informatica domain configuration database stores metadata for domain operations and userauthentication. The domain configuration database must be accessible to all gateway nodes in the domain.

16 Chapter 3: Informatica Services Installation

The following table describes the properties you specify for the database user account:


Database type Database for the domain configuration. Select Oracle, Microsoft SQL Server, or IBMDB2.

Database user ID Name for the domain configuration database user account.

User password Password for the domain configuration database user account

Tablespace Available for IBM DB2 only. Name of the tablespace in which to create the repositorytables. If blank, the installation creates the repository tables in the default tablespace.Define the repository database in a single-node tablespace to optimize performance.

You can provide the JDBC connection string in one of the following ways:

¨ Enter the JDBC connection properties from which the installer can create the JDBC URL.

¨ Enter a complete and valid JDBC connection string.

15. To provide the connection properties, select the JDBC URL option.

The installer displays optional parameters that you can use to optimize the database connection. You can usethe parameters provided or enter your own parameters. The installer adds the parameters to the JDBC URLto create the connection string and connect to the database.

The following table describes the properties you specify for the JDBC URL:


Database Address Host name and port number for the database instance in the format host name:port.

Database service name Service name for Oracle and IBM DB2 databases or database name for Microsoft SQLServer.

JDBC parameters Optional parameters to include in the database connection string. Use the parametersto optimize database operations for the configuration database. You can use the defaultparameters or add or modify the parameters based on your database requirements. Ifnot selected, the installer creates the JDBC connection string without parameters. If youmodify the default parameters, you can click Default to revert back to the defaultparameter string provided by the installer.

16. To provide a complete JDBC connection string, select Custom JDBC Connection String and enter a validconnection string.

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

17. Click Test Connection to verify that you can connect to the domain configuration database and then click OKto continue.

18. Click Next.

The Domain and Node Configuration Window appears.

19. On the Domain and Node Configuration window, enter the information for the domain and the node you wantto create.

Installing in Graphical Mode 17

The following table describes the properties you set for the domain and gateway node:


Domain name Name of the domain to create. The default domain name is Domain_<MachineName>.The name cannot exceed 128 characters and and must be 7-bit ASCII only. Do not usethe following characters: \\ / : * ? > < " | .

Domain host name Host name of the machine on which to create the Informatica domain. If you create adomain on a machine with a single network name, use the default host name. If youcreate a domain on a machine with multiple network names, you can modify the defaulthost name to use an alternate network name. Optionally, you can use the IP address ofthe machine on which to create the domain.Note: Do not use localhost.

Node name Name of the node to create on this machine. The node name is not the host name forthe machine.

Domain port number Port number for the domain. The default port number for the Informatica domain is6005. If the port number is not available on the machine, the installer displays the nextavailable port number.

Domain user name User name for the domain administrator. You can use this user name to initially log in tothe Administration Console. The user name must be less than 79 characters and cancontain only alphanumeric characters.

Domain user password User name for the domain administrator. You can use this user name to initially log in tothe Administrator tool. 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.

Confirm password Enter the password again to confirm.

Display advanced portconfiguration page

Indicates whether the installer displays the list of port numbers for the domaincomponents and the node. If selected, the installer displays the default port numbersassigned to the domain components. You can modify the port numbers and specify adifferent range of port numbers for the application service processes. If not selected,the installer does not display the default port numbers and you cannot modify theassigned port numbers.

20. Click Next.

Skip to step 25.

21. In the Domain Configuration window, enter the information for the domain that you want to join.

The following table describes the properties you specify for the domain:


Domain name Name of the domain to join.

Domain host name Host name of the machine that hosts the Informatica domain you want to join.

Domain port number Port number for the domainyou want to join.



Domain user name User name for the domain administrator.

Domain user password Password for the domain administrator.

22. Click Next.

23. On the Join Domain Node Configuration window, enter the information for the node you want to create.

The following table describes the properties you set for the node:


Host name Host name for the node.Note: Do not use localhost.


Port no Port number for the node.

Display advanced portconfiguration page

Indicates whether the installer displays the list of port numbers for the domaincomponents and the node. If selected, the installer displays the default port numbersassigned to the domain components. You can modify the port numbers and specify adifferent range of port numbers for the application service processes. If not selected,the installer does not display the default port numbers and you cannot modify theassigned port numbers.

24. Click Next.

25. On the Port Configuration window, enter the port numbers to use for the Informatica domain components.

Note: This window appears only if you select to display the advanced port configuration window.

Specify the ports to use for the domain components. Also specify a range of port numbers to use for theapplication services that you create on this node. Verify that the port numbers you enter are not used by otherapplications.

The following table describes the ports you specify:


Service Manager port Port number for the Service Manager in the domain. This is the port that the Informaticacommand line programs use to communicate to the domain. This is also the port for theSQL Data Service JDBC/ODBC driver.


Port number that controls server shutdown for the domain Service Manager.

Informatica Administrator port Port number for Informatica Administrator. Informatica Administrator is the Administratortool for the Informatica domain. Not available if you join a domain.


Port number that controls server shutdown for the Administrator tool. Not available ifyou join a domain.

Installing in Graphical Mode 19


Minimum port number Lowest port number in the range of port numbers that will be used when you createapplication services that run on this node in the domain.

Maximum port number Highest port number in the range of port numbers that will be used when you createapplication services that run on this node in the domain.

26. Click Next.

On Windows, the installer creates a Windows service to start Informatica. By default, the service runs underthe same user account as the account used for installation. You can run the Windows service under adifferent user account.

27. To run the Windows service under a different user account, enter the Windows domain and user account inthe following format:

DomainName\UserAccount This user account must have the Act as operating system permission.

28. Click Next.

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

29. Click Done.

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

Installing in Console ModeYou can install Informatica Services in console mode on UNIX.

Note: When the console mode installation starts, the installer displays an incorrect message that it is preparingfor silent mode installation. You can ignore the message. In the console installation, the words Quit and Back arereserved words. Do not use them as input text.

To install in console mode:

1. Verify that your environment meets the minimum system requirements, and complete the pre-installationtasks.

2. Log in to the machine as the system user.


4. On a shell command line, run the install.sh file located in the root directory.

Note: If the install.sh file does not have sufficient permissions to execute after you extract the installation files,use the chmod command to add execute permissions to the file. Then run the file with the command ./install.sh

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

5. If the environment variables are not set, enter N to exit the installer and set them as required.

If the environment variables are set, enter Y to continue.

6. Enter C for console mode installation.

The installer displays the system requirements and the tasks to perform before installation. Verify that allinstallation requirements are met before you continue the installation.


7. Press Enter.

8. Enter the path and file name of the Informatica license key.

9. Enter an absolute path for the installation directory or press Enter to use the default directory.

The directory names in the path must not contain spaces or the following special characters: @|* $ # ! % ( ) { }[ ] , ; '

10. Review the installation information, and press Enter to continue.

The installer copies the Informatica files to the installation directory.

11. Select whether to create or join a domain.

Option Description

1 - Create a domain Create a domain and a gateway node on this machine.

2 - Join a domain Create a node on this machine and join the node to a domain.

If you create a domain, the node on the current machine becomes a gateway node on the domain. Thegateway node contains a Service Manager that manages all domain operations.

12. If you join a domain, select whether to configure the node as a gateway.

Enter Y to configure a gateway node and N to configure a worker node.

13. If you create a domain, select whether to use a secure connection for Informatica Administrator:

Option Description

1 - Enable HTTPS forInformatica Administrator

Set up a secure connection between Informatica Administrator and the Service Manager.

2 - Disable HTTPS Do not set up a secure connection between Informatica Administrator and the ServiceManager. Use HTTP connection.

14. For a gateway node, enter the port number for the HTTPS connection or press Enter to use the default port.

15. For a gateway node, select the type of keystore to use for the HTTPS connection:

Option Description

1 - Use a keystore generatedby the installer

Use a self-signed keystore file generated by the installer. The installer creates akeystore file named DEFAULT.keystore in the following location: InstallationDirectory\tomcat\conf\

2 - Use an existing keystore Use a keystore file you create. You can use a keystore file with a self-signed certificateor a certificate signed by a certification authority.

16. If you use an existing keystore, enter the password and location of the keystore file.

Installing in Console Mode 21

17. Select the database to use for the domain configuration:

Prompt Description

Database type Type of database for the domain configuration. Select from the following options:1 - Oracle2 - SQL Server3 - IBM DB2

The Informatica domain configuration database stores metadata for domain operations and userauthentication. The domain configuration must be accessible to all gateway nodes in the domain.

18. Enter the following information at the prompt:


Database user ID Name for the domain configuration database User account.

User password Password for the domain configuration database user account

19. If you create the domain configuration database in IBM DB2, select whether to configure a tablespace andenter the tablespace name:


Configure Tablespace Select from the following options:1 - No2 - Yes

Tablespace Name of the tablespace in which to create the repository tables. If blank, the installationcreates the repository tables in the default tablespace. Define the repository database ina single-node tablespace to optimize performance.

20. Select how you want to specify the database connection URL:

Option Description

1 - JDBC URL If you select this option, enter the host name, port number, and database name for thedomain configuration database.

2 - Custom JDBC ConnectionString

If you select this option, enter a connection string that includes all JDBC elements andparameters based on your database requirements.


21. If you select JDBC URL, enter the properties for the JDBC URL at the prompt:


Database Address Host name and port number for the database instance in the format Host name:Port.

Database service name Service name for Oracle and IBM DB2 databases or database name for Microsoft SQLServer.

Configure JDBC parameters Select from the following options:1 - Yes2 - NoIf you select Yes, enter the parameters or press enter to accept the default. If you selectNo, the installer creates the JDBC connection string without parameters.

If you select Custom JDBC Connection String, enter a valid connection string.

22. If the database already contains configuration data for a previous domain, select to overwrite the data or setup another database:

Option Description

1 - OK If you select this option, enter the connection information for a new database.

2 - Continue If you select this option, the installer overwrites the data in the database with newdomain configuration.

23. Enter the following information at the prompt:


Domain name Name of the domain to create. The name cannot exceed 128 characters and and mustbe 7-bit ASCII only. Do not use the following characters: \\ / : * ? > < " | .

Domain host name Host name of the machine on which to create the Informatica domain. If you create adomain on a machine with a single network name, use the default host name. If youcreate a domain on a machine with multiple network names, you can modify the defaulthost name to use an alternate network name. Optionally, you can use the IP address ofthe machine on which to create the domain.Note: Do not use localhost.


Domain port number Port number for the domain. The default port number for the Informatica domain is6005. If the port number is not available on the machine, the installer displays the nextavailable port number.

Installing in Console Mode 23


Domain user name User name for the domain administrator. You can use this user name to initially log in tothe Administrator tool. 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 user password Password for the domain administrator. The password must be between 3 and 16characters. Enter the password again to confirm.

24. Select whether to display the advanced list of port numbers for the domain components.

If you display page, the installer displays the default port numbers assigned to the domain components. Youcan modify the port numbers and specify a different range of port numbers for the application serviceprocesses.

Enter Y to display the port configuration page and N to skip the page.

25. If you display the port configuration page, enter new the port numbers at the prompt or press Enter to use thedefault port numbers:


Service Manager port Port number for the Service Manager in the domain. This is the port that the Informaticacommand line programs use to communicate to the domain. This is also the port for theSQL Data Service JDBC/ODBC driver. Default is 6006.


Port number that controls server shutdown for the domain Service Manager. Default is6008.

Informatica Administrator port Port number for Informatica Administrator. If you join a domain, you do not need toconfigure this port number. Default is 6007.


Port number that controls server shutdown for the Administrator tool. If you join adomain, you do not need to configure this port number. Default is 6009.

Minimum port number Lowest port number in the range of port numbers that will be used when you createapplication services in the domain that run on this node. Default is 6013.

Maximum port number Highest port number in the range of port numbers that will be used when you createapplication services in the domain that run on this node. Default is 6113.

The Post-installation Summary indicates whether the installation completed successfully. You can view theinstallation log files to get more information about the tasks performed by the installer and to view configurationproperties for the installed components.


C H A P T E R 4

Informatica Clients InstallationThis chapter includes the following topics:

¨ Informatica Clients Installation Overview, 25

¨ Installing in Graphical Mode, 25

¨ Installing in Silent Mode, 26

Informatica Clients Installation OverviewYou can install Informatica Clients on Windows. You can install on multiple machines in graphical or silent mode.

Install the Informatica client applications from a DVD or from the root of the directory where you download theinstallation files.

Installing in Graphical ModeTo install in graphical mode:


2. Run install.bat from the root directory.

The Installation Pre-Requisites window displays the system requirements. Verify that all installationrequirements are met before you continue the installation.

3. Click Next.

On the Select Component window, select the Informatica client you want to install.

You can install the following Informatica client applications on the same machine:

¨ Informatica Developer

¨ PowerCenter Client

4. On the Installation Directory window, enter the absolute path for the installation directory.

The installation directory must be on the current machine. The directory names in the path must not containspaces or the $ symbol.

5. Click Next.

6. On the Pre-Installation Summary window, review the installation information, and click Install.

25

The installer copies the Informatica client files to the installation directory.

The Post-installation Summary window indicates whether the installation completed successfully.

7. Click Done.

You can view the installation log files to get more information about the tasks performed by the installer.

Installing in Silent ModeTo install the Informatica clients without user interaction, install in silent mode using a properties file that containsthe installation options. The Informatica client installer reads the file to determine the installation options.

Use the silent mode installation to install the Informatica clients on multiple machines on the network or tostandardize the installation across machines.

To install in silent mode, complete the following tasks:

1. Create the installation properties file and specify the installation options in the properties file.

2. Run the installer with the installation properties file.

Step 1. Create the Properties FileInformatica provides a sample properties file that includes the properties required by the installer. Customize thesample properties file to create a properties file and specify the options for your installation. Then run the silentinstallation.

The sample installer.properties is located in the root directory of the DVD or the installer download location.

To create the installer.properties file:

1. Copy the sample installer.properties file to the hard disk.

2. Use a text editor to open and modify the values of the properties in the file.

The following table describes the installation properties you can modify:

Property Name Description

USER_INSTALL_DIR Informatica client installation directory. Use \\ to separate directories.For example: C:\\Informatica\\ver9.0

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 Developertool will not be installed.Default is 1.

CLIENT_COMP Indicates whether to install the PowerCenter Client.If the value is 1, the PowerCenter Client will be installed. If the value is 0, thePowerCenter Client will not be installed.Default is 1.

3. Save the properties file on the machine where you install Informatica Clients.

26 Chapter 4: Informatica Clients Installation

Sample Properties FileThe following example shows the contents of the sample installer.properties file:

########################################################### Informatica Installer Build details# Copyright (c) Informatica Corporation 1998 - 2009# This software contains confidential and proprietary# information of Informatica Corporation# All Rights Reserved. ##########################################################

# Use the following guidelines when editing this file:# * Any error condition that leads to failure, such as an invalid installation # directory, generates a log file SYSTE_DRIVE_ROOT. For example: # c:\Informatica90_Silent_Installer_Debug.log # * The USER_INSTALL_DIR variable must point to a valid directory with write# permissions enabled.# * Use "\\" to separate directory names in the installation directory path. # For example: c:\\ProgramFiles\\Informatica

USER_INSTALL_DIR=c:\\Informatica\\9.0

# The DXT_COMP variable indicates whether to install Informatica Developer # Value 1 Install Informatica Developer# Value 0 Do not install Informatica DeveloperDXT_COMP=1

# The CLIENT_COMP variable indicates whether to install the PowerCenter Client # Value 1 Install the PowerCenter Client# Value 0 Do not install the PowerCenter ClientCLIENT_COMP=1

################################################################## DO NOT EDIT THE VARIABLES BELOW THIS LINE.# The following variables sets the installation mode to SILENT. INSTALLER_UI=SILENTINSTALLER_MODE=SILENT_INSTALLER

Step 2. Run the InstallerAfter you create the properties file, open a command window to start the silent installation.

1. Copy the client installation files to the hard disk on the machine where you plan to install the Informaticaclients.

If you install on a remote machine, verify that you can access and create files on the remote machine.

2. Open a command window.

3. Go to root of the client installer directory.

4. To run the silent installation, double click the file silentinstall.bat or use the following command:silentinstall -f "<PropertiesFileAbsolutePath>\installer.properties"

Include the absolute path before the installer.properties file. If you do not include the absolute path for theproperties file, the graphical client installation starts.

The silent installer runs in the background. The process can take a while. The silent installation is complete whenthe summary_client.htm is created in the installation directory.

The silent installation fails if you incorrectly configure the properties file or if the installation directory is notaccessible. View the installation log files and correct the errors. Then run the silent installation again.

Installing in Silent Mode 27

C H A P T E R 5

After You InstallThis chapter includes the following topics:

¨ Post-Installation Tasks, 28

¨ Informatica Platform Configuration, 28

¨ Data Quality and Data Services Configuration, 34

¨ PowerCenter Configuration, 36

Post-Installation TasksAfter installation, configure the environment for the new installation. Perform the post-installation tasks to ensurethat you can run Informatica properly.

Perform all configuration tasks that affect the Informatica domain. Additionally, if you install Informatica DataQuality or Informatica Data Services, complete the tasks that affect these products. If you install PowerCenter,complete the PowerCenter configuration tasks.

Informatica Platform ConfigurationBefore you start using Informatica, complete the platform configuration tasks to ensure that the products runproperly. The platform configuration tasks affect the domain, Data Quality, Data Services, and PowerCenter.

Complete the following tasks:

¨ Configure the environment variables. Verify that the following variables are set correctly:

- Informatica environment variables

- Locale environment variables

- Library path environment variables

¨ If you created the domain configuration database in IBM DB2 version 9.1, update the statistics for the DB2optimizer.

¨ On UNIX, verify that a graphics display server is available.

¨ Configure the browser to use with the web client applications.

¨ Install languages for the Informatica client applications.

28

Verify Environment VariablesInformatica uses environment variables to store configuration information when it runs the application services andconnects to the clients. Configure the environment variables to meet the Informatica requirements.

To configure environment variables on UNIX, log in with the system user account you used to install Informatica.

The following table describes the environment variables you configure:

Variable Type OperatingSystem

Description

Informatica WindowsUNIX

Configure variables for the following Informatica properties:- Designate the Informatica installation directory.- Designate the location of domains.infa.- Informatica memory usage.To apply changes, restart the node.

Database client UNIX Location of the database client.

Locale environmentvariables

UNIX Use LANG or LC_ALL to set the UNIX code page for the repository.

Java components AIXHP-UX

Java Runtime Environment location for Java-based components.

Library path UNIX Location of the database client libraries.

Informatica Environment VariablesYou can configure the INFA_JAVA_OPTS, INFA_DOMAINS_FILE, and INFA_HOME environment variables tostore memory, domain, and location settings.

INFA_JAVA_OPTS

Informatica uses JRE to start and run the Informatica9.0 service. By default, Informatica9.0 uses a maximumof 512 MB of system memory. You can configure the amount of system memory used by Informatica withINFA_JAVA_OPTS. For example, to configure 1 GB of system memory for the Informatica9.0 daemon onUNIX in a C shell, use the following command:

setenv INFA_JAVA_OPTS “-Xmx1024m”

On Windows, configure INFA_JAVA_OPTS as a system variable.

On 64-bit HP-UX on Itanium, add the -d64 switch.

Restart the node for the changes to take effect.

INFA_DOMAINS_FILE

The domains.infa file contains the connectivity information for the gateway nodes in a domain. Theconnectivity information includes the domain names, domain host names, and domain host port numbers.Include the file name in the path. On Windows, configure INFA_DOMAINS_FILE as a system variable.

Configure the INFA_DOMAINS_FILE variable on the machine where you install Informatica Services. Theinstaller creates the Informatica9.0 on these machines.

The installer creates domains.infa in the Informatica installation directory. You can configureINFA_DOMAINS_FILE to run infacmd and pmcmd from a directory other than server/bin.

Informatica Platform Configuration 29

INFA_HOME

Use INFA_HOME to designate the Informatica installation directory. If you modify the Informatica directorystructure, you need to configure the environment variable to the location of the Informatica installationdirectory or the directory where the installed Informatica files are located.

For example, you use a softlink in UNIX for any of the Informatica directories. To configure INFA_HOME sothat any Informatica application or service can locate the other Informatica components it needs to run,configure INFA_HOME to the location of the Informatica installation directory.

Locale Environment VariablesUse LANG, LC_CTYPE, or LC_ALL to set the UNIX code page. Verify that the locale setting is compatible with thecode page for the repository. If the locale setting is not compatible with the repository code page, you cannotcreate a repository service.

Different UNIX operating systems require different values for the same locale. The value for the locale variable iscase sensitive.

Use the following command to verify that the value for the locale environment variable is compatible with thelanguage settings for the machine and the type of code page you want to use for the repository:

locale -a

The command returns the languages installed on the UNIX operating system and the existing locale settings.

Locale on Linux

All UNIX operating systems except Linux have a unique value for each locale. Linux allows different values torepresent the same locale. For example, “utf8,” “UTF-8,” “UTF8,” and “utf-8” represent the same locale on aLinux machine. Informatica requires that you use a specific value for each locale on a Linux machine. Makesure 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 you want the database client and server to use withthe login. A locale setting consists of the language, territory, and character set. The value of NLS_LANGdepends on the configuration. For example, if the value is american_america.UTF8, set the variable in a Cshell with the following command:

setenv NLS_LANG american_america.UTF8

Locale for Sybase Database Clients on HP-UX

Sybase uses a file named locales.dat to map the locales supported by the operating system to the localessupported by Sybase.

For Sybase database clients on HP-UX, if you set LANG to a locale supported by the operating system, youmust verify that locales.dat includes an entry for the locale name. If locales.dat does not include an entry forthe locale name, add the locale to the file. For more information about editing the locales.dat file, see theSybase documentation.

Library Path Environment VariablesConfigure library path environment variables on the machines that run the Data Integration Service, PowerCenterIntegration Service, and PowerCenter Repository Service processes. The library path variable name andrequirements depend on the UNIX platform and database.

Solaris and Linux

On Solaris and Linux, configure the LD_LIBRARY_PATH environment variable.

30 Chapter 5: After You Install

The following table describes the values you set for the LD_LIBRARY_PATH for the different databases:

Database Value

Oracle <DatabasePath>/lib

IBM DB2 <DatabasePath>/lib

Sybase ASE “${SYBASE_OCS}/lib:${SYBASE_ASE}/lib:${LD_LIBRARY_PATH}”

Informix <DatabasePath>/lib

Teradata <DatabasePath>/lib

ODBC <CLOSEDODBCHOME>/lib

AIX

On AIX, configure the LIBPATH environment variable.

The following table describes the values you set for the LIBPATH for the different databases:

Database Value



Sybase ASE “${SYBASE_OCS}/lib:${SYBASE_ASE}/lib:${LIBPATH}”



ODBC <CLOSEDODBCHOME>/lib

HP-UX

On HP-UX, configure the SHLIB_PATH environment variable.

The following table describes the values you set for the SHLIB_PATH for the different databases:

Database Value



Sybase ASE "${SYBASE_OCS}/lib:${SYBASE_ASE}/lib:${SHLIBPATH}"




Java Component VariablesInformatica installs the JRE to use with the following Java-based components:

¨ Custom transformation that uses Java

¨ Java transformation

¨ PowerExchange for JMS

¨ PowerExchange for Web Services

¨ PowerExchange for webMethods

To use these components on AIX32, AIX64, or HP-UX, configure the library path environment variables to point tothe java directory installed with Informatica. Configure these environment variables on machines where thePowerCenter Integration Service process runs.

The following table describes the library paths you configure to use Java-based components:

UNIX Platform Environment Variable Name Value

AIX32AIX64

LIBPATH Set to: java/jre/binSet to: java/jre/bin/classicSet to: /usr/lib:/lib

HP-UX SHLIB_PATH Set to: java/jre/lib/PA_RISC2.0/serverSet to: java/jre/lib/PA_RISC2.0Set to: /usr/lib:/lib

Update Statistics for the Domain Configuration DatabaseIf you create the domain configuration database in IBM DB2 version 9.1, run the DB2 reorgchk command afterinstallation. The reorgchk command generates the database statistics used by the DB2 optimizer in queries andupdates.

Use the following command:

REORGCHK UPDATE STATISTICS on SCHEMA SchemaName

Configure POSIX Asynchronous I/OIf you install Informatica on IBM AIX, make POSIX Asynchronous I/O available on any node where you want to runa PowerCenter Integration Service. A PowerCenter Integration Service running on an IBM AIX machine can fail tostart if POSIX Asynchronous I/O is not available.

Set Up the Graphics Display ServerThe gateway nodes on UNIX require a graphics display server to run domain reports in Informatica Administrator.If you do not have a graphics display server, you can install and configure X Virtual Frame Buffer (Xvfb). Xvfb is anX server that renders graphics to virtual memory rather than to a graphics display device.

You can download and install Xvfb for the following operating systems:

¨ HP-UX. Xvfb is part of the HP-UX operating system. Install HP-UX patches and graphical packages to run Xvfbbased on when you installed or last patched the operating system. For instructions to run Xvfb on HP-UX, seethe following web site:

http://publib.boulder.ibm.com/tividd/td/ITM/GI10-5797-01/en_US/HTML/notesmst20.htm


¨ AIX and Linux. Download and install Xvfb. For instructions to run Xvfb on AIX and Linux, see the following website:

http://publib.boulder.ibm.com/infocenter/iwphelp/v2r5m1/index.jsp?topic=/com.ibm.wcs.ic.doc_2.5.1/install/i_inst_t_lwpsetup_xfvb_on_unx.html

¨ Solaris. You can download Xvfb for Solaris from the following web site:http://ferret.pmel.noaa.gov/FERRET_17sep07/FAQ/graphics/Solaris_Xvfb.html

Download and set up Xvfb for Solaris and use the following command to start the virtual frame buffer:% /usr/X11R6/bin/Xvfb :1 -screen 0 1152x900x8 &

This sends any graphics output going to display 1 to shared memory.

Use the following command to set the current display to use the frame buffer for graphics display in a C shell:% setenv DISPLAY :1.0

Configure the Web BrowserYou can use Microsoft Internet Explorer or Mozilla Firefox to launch the web client applications in the Informaticaplatform.

The following table describes the browser you can use with the web applications:

Component Web Browser

Informatica Administrator Microsoft Internet Explorer, Mozilla Firefox

Web Services Hub Console Microsoft Internet Explorer, Mozilla Firefox

Metadata Manager Microsoft Internet Explorer, Mozilla Firefox

Data Analyzer Microsoft Internet Explorer, Mozilla Firefox

Informatica Analyst Microsoft Internet Explorer, Mozilla Firefox

PowerCenter Client Microsoft Internet ExplorerNote: Required to display the Start Page for the Designer, Repository Manager, andWorkflow Manager.

Configure the following options in the browser to access the applications:

¨ Scripting and ActiveX. Internet Explorer requires the Active scripting, Allow paste operations, Run ActiveXcontrols and plug-ins, and Script ActiveX controls marked safe for scripting controls enabled. To configure thecontrols, click Tools > Internet Options > Security > Custom level.

¨ Javascript. Enable Javascript to use Firefox.

¨ Pop-up blocking utility. To display the Data Analyzer and Metadata Manager pages, disable any pop-upblocking utility on your browser.

¨ TLS 1.0. If you configure HTTPS for Informatica Administrator on a domain that runs on 64-bit AIX, InternetExplorer requires TLS 1.0. To enable TLS 1.0, click Tools > Internet Options > Advanced. The TLS 1.0 settingis listed below the Security heading.

¨ Browser cache. On Internet Explorer, to make sure Metadata Manager properly caches pages and appliesuser privileges, set the browser cache options. Click Tools > Internet Options. Under Browsing history, clickSettings. Under Check for newer versions of stored pages, select Every time I visit the webpage.


¨ Context menus. On Firefox, to make sure Metadata Manager properly displays the shortcut menu in MetadataManager, set the context menu option. Click Tools > Options. On the Content tab, click Advanced next to theEnable JavaScript option. In the Advanced JavaScript Settings dialog box, select Disable or replace contextmenus.

Install LanguagesIf you need to view languages other than the system locale and you work with repositories that use a UTF-8 codepage, install additional languages on Windows for use with the Informatica clients. You also must install languagesto use the Windows Input Method Editor (IME).

To install languages:

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.

Windows might require you to restart the system.

Data Quality and Data Services ConfigurationBefore you start using Data Quality or Data Services, complete the configuration tasks to ensure that the productsrun properly.


¨ If your environment includes 32-bit and 64-bit machines, follow the guidelines for running Data Quality or DataServices on 32-bit and 64-bit machines.

¨ Install and configure the database client software.

¨ Configure the Informatica environment variables.

Verify the Setup for 32-bit and 64-bit PlatformsYou can run Informatica Data Quality or Data Services on 32-bit or 64-bit platforms. A 64-bit architecture provideslarger memory space that can significantly reduce or eliminate disk input and output. This can increase sessionperformance in the following areas:

¨ Caching. With a 64-bit platform, the Data Integration Service is not limited to the 2 GB cache limit of a 32-bitplatform.

¨ Data throughput. With a larger available memory space, the reader, writer, and Data Transformation Manager(DTM) threads can process larger blocks of data.

The Informatica 64-bit platform addresses up to 18 million terabytes (2^64 bytes) of system memory and has up to256 terabytes (2^48 bytes) available for a single application. The 32-bit platform addresses up to 4 GB (2^32bytes) of system memory and has up to 2 GB available for any single application.

When you run Informatica on both 32-bit and 64-bit platforms, configure the correct libraries, database clients, andsession cache sizes.


Use the following guidelines when you work with 32-bit and 64-bit platforms:

¨ Libraries. Link libraries according to the following guidelines:

- Link 32-bit applications with 32-bit libraries. Link 64-bit applications with 64-bit libraries.

- Link 32-bit machines running a Data Integration Service with a 32-bit database client. Link a 64-bit machinerunning a Data Integration Service with 64-bit database client.

¨ Database clients. Link a 32-bit machine running a Model Repository Service with 32-bit database clients. Linka 64-bit machine running a Model Repository Service with 64-bit database clients.

¨ Data Integration Service and Model Repository Service. 32-bit and 64-bit machines that run DataIntegration Services and Model Repository Services are compatible with each other.

Install the Database Client SoftwareBased on the types of databases that the Data Integration Service will access, install the following databaseclients and configure connectivity on the machine where the Data Integration Service runs:

¨ Oracle client

¨ IBM DB2 Client Application Enabler (CAE)

¨ Microsoft SQL Client, with Microsoft OLE DB provider for Microsoft SQL Server

¨ Sybase Open Client

¨ Teradata BTEQ client

Database Client Environment VariablesConfigure database client environment variables on the machines that run the Data Integration Service. Thedatabase client path variable name and requirements depend on the UNIX platform and repository database.

After you configure the database environment variables, you can test the connection to the database from thedatabase client.

The following table describes the database environment variables you need to set in UNIX:

Database Environment VariableName

DatabaseUtility

Value

Oracle ORACLE_HOMEPATH

sqlplus Set to: <DatabasePath>Add: <DatabasePath>/bin

IBM DB2 DB2DIRDB2INSTANCEPATH

db2connect Set to: <DatabasePath>Set to: <DB2InstanceName>Add: <DatabasePath>/bin

Sybase ASE SYBASE12 or SYBASE15SYBASE_ASESYBASE_OCSPATH

isql Set to: <DatabasePath>/sybase<version>Set to: ${SYBASE[12 | 15]}/ASE-<version>Set to: ${SYBASE[12 | 15]}/OCS-<version>Add: ${SYBASE_ASE}/bin:${SYBASE_OCS}/bin:$PATH

Teradata PATH bteq Add: <DatabasePath>/bin

Data Quality and Data Services Configuration 35

PowerCenter ConfigurationBefore you start using PowerCenter, complete the configuration tasks to ensure that the PowerCenter runsproperly.


¨ If your environment includes 32-bit and 64-bit machines, follow the guidelines for running PowerCenter on 32-bit and 64-bit machines.

¨ Verify that the code pages you use for the services and components in the domain are compatible.

¨ Install and configure the database client software.

¨ Verify that the third-party software required by PowerCenter services are installed.

¨ Configure the Informatica environment variables.

¨ If you plan to use Unstructured Data transformations, install and configure the Data Transformation Engine.

Verify the Setup for 32-bit and 64-bit PlatformsYou can run Informatica on 32-bit or 64-bit platforms. A 64-bit architecture provides larger memory space that cansignificantly reduce or eliminate disk input and output. This can increase session performance in the followingareas:

¨ Caching. With a 64-bit platform, the PowerCenter Integration Service is not limited to the 2 GB cache limit of a32-bit platform.

¨ Data throughput. With a larger available memory space, the reader, writer, and Data Transformation Manager(DTM) threads can process larger blocks of data.

The Informatica 64-bit platform addresses up to 18 million terabytes (2^64 bytes) of system memory and has up to256 terabytes (2^48 bytes) available for a single application. The 32-bit platform addresses up to 4 GB (2^32bytes) of system memory and has up to 2 GB available for any single application.

When you run Informatica on both 32-bit and 64-bit platforms, configure Informatica to use the correct libraries,database clients, and session cache sizes.

Use the following guidelines when you work with 32-bit and 64-bit platforms:

¨ Libraries. Link libraries according to the following guidelines:

- Link 32-bit applications with 32-bit libraries. Link 64-bit applications with 64-bit libraries.

- Link 32-bit machines running a PowerCenter Integration Service with a 32-bit database client. Link a 64-bitmachine running a PowerCenter Integration Service with 64-bit database client.

¨ Database clients. Link 32-bit machines running a PowerCenter Repository Service with 32-bit databaseclients. Link 64-bit machines running a PowerCenter Repository Service with 64-bit database clients.

¨ PowerCenter Integration Service and PowerCenter Repository Service. 32-bit and 64-bit machines that runPowerCenter integration services and repository services are compatible with each other.

¨ Caching. If the total configured session cache size is 2 GB or greater (2,147,483,648 bytes), run the sessionusing a PowerCenter Integration Service running on a 64-bit machine. The session fails if the PowerCenterIntegration Service runs on a 32-bit machine.

¨ Server grids. A server grid can contain both 32-bit and 64-bit machines that run the PowerCenter IntegrationService. If the total configured session cache size is 2 GB (2,147,483,648 bytes) or greater, configure thesession to run on a PowerCenter Integration Service on a 64-bit machine.


Verify Code Page CompatibilityInformatica requires that code pages for application services are compatible with code pages in the domain. Thelocale settings on machines that access the Informatica client applications or Informatica Administrator must alsobe compatible with the code pages of in the domain.

Application ServicesThe domain configuration database must be compatible with the code pages of the repository services you createin the domain.

The Service Manager synchronizes the list of users in the domain with the list of users and group in eachapplication service. If a user name in the domain has characters that the code page of the application service doesnot recognize, characters do not convert correctly and inconsistencies occur.

Locale SettingsThe locale settings on machines that access the Informatica client tools or Administrator tool must be compatiblewith code pages of repositories in the domain. On Windows, verify the locale settings in the Regional Options ofthe Control Panel. For more information, see the Windows documentation.

Install the Database Client SoftwareInstall database client software and configure connectivity on the gateway node and on the nodes that will run thePowerCenter Integration Service and PowerCenter Repository Service processes.

RELATED TOPICS:¨ “Connecting to Databases from Windows” on page 86

¨ “Connecting to Databases from UNIX” on page 93

PowerCenter Integration ServiceBased on the database types that the Integration Service will access, install the following database clients andconfigure connectivity on the machine where the Integration Service runs:

¨ Oracle client



¨ Sybase Open Client

¨ Teradata BTEQ client

PowerCenter Repository ServiceBased on the repository database, install the following database clients and configure connectivity on the machinewhere the Repository Service runs:

¨ Oracle client



PowerCenter Configuration 37

Database Client Environment VariablesConfigure database client environment variables on the machines that run the PowerCenter Integration Serviceand the PowerCenter Repository Service processes. The database client path variable name and requirementsdepend on the UNIX platform and repository database.

After you configure the database environment variables, you can test the connection to the database from thedatabase client.

The following table describes the database environment variables you need to set in UNIX:

Database Environment VariableName

DatabaseUtility

Value

Oracle ORACLE_HOMEPATH

sqlplus Set to: <DatabasePath>Add: <DatabasePath>/bin

IBM DB2 DB2DIRDB2INSTANCEPATH

db2connect Set to: <DatabasePath>Set to: <DB2InstanceName>Add: <DatabasePath>/bin

Sybase ASE SYBASE12 or SYBASE15SYBASE_ASESYBASE_OCSPATH

isql Set to: <DatabasePath>/sybase<version>Set to: ${SYBASE[12 | 15]}/ASE-<version>Set to: ${SYBASE[12 | 15]}/OCS-<version>Add: ${SYBASE_ASE}/bin:${SYBASE_OCS}/bin:$PATH

Teradata PATH bteq Add: <DatabasePath>/bin

Verify Third-Party Software RequirementsInformatica requires third-party software to run Data Analyzer, Metadata Manager, and Informatica Administrator.

Microsoft SOAP Toolkit (Data Analyzer)In Data Analyzer, you can export a report to an Excel file and refresh the data in Excel directly from the cacheddata in Data Analyzer or from the data source. To use the data refresh feature, install the Microsoft SOAP Toolkit.

Adobe SVG Viewer (Data Analyzer)In Data Analyzer, you can display interactive report charts and chart indicators. Click on an interactive chart to drillinto the report data and view details and select sections of the chart. To view interactive charts on InternetExplorer, install Adobe SVG Viewer.

Adobe Flash Player Plug-In (Metadata Manager)Metadata Manager requires the Adobe Flash Player plug-in version 9 or later to upload PowerCenter parameterfiles and to display data lineage. To upload PowerCenter parameter files or to run data lineage analysis inMetadata Manager or from the Designer, download and install the Flash Player plug-in on the web browser. Getthe Flash Player plug-in from the following web site:

http://www.adobe.com/products/flashplayer/


Verify the Data Transformation RequirementsUnstructured Data transformations require the Data Transformation Engine. The Data Transformation Engine is acomponent of the Informatica B2B Data Exchange. Install the Data Transformation Engine on the machine wherethe PowerCenter Integration Service runs.

To use an Unstructured Data transformation in PowerCenter mappings, configure the Java environment for DataTransformation and ensure that the latest version of the PowerCenter ICU libraries are available.

JVM LocationIf the PowerCenter Integration Service is running on UNIX, ensure that Data Transformation Studio uses the sameJava Virtual Machine (JVM) as Informatica. If Data Transformation Studio uses a different JVM than Informatica,the session may shut down unexpectedly.

The following table shows the JVM location in PowerCenter for UNIX platforms:

Operating System JVM Location Settings

AIX 64-bit <InformaticaInstallationDir>/java/jre/bin/classic

HP-UX <InformaticaInstallationDir>/java/jre/lib/PA_RISC2.0/server

Linux.x86 <InformaticaInstallationDir>/java/jre/lib/i386/server

Linux.x64 <InformaticaInstallationDir>/java/jre/lib/amd64/server

Solaris 64-bit <InformaticaInstallationDir>/java/jre/lib/sparcv9/server

Solaris <InformaticaInstallationDir>/java/jre/lib/sparc/server

HP-PARISC <InformaticaInstallationDir>/java/jre/lib/PA_RISC2.0W/server

HP-IPF <InformaticaInstallationDir>/java/jre/lib/IA64W/hotspot

Set the CMJAVA_PATH environment variable to point to the JVM location in the Informatica installation directory.You must also include the JVM location in the CMConfig.xml file.

CMConfig.xml is in the Data Transformation installation directory.

To configure JVM settings in Data Transformation running on UNIX:

1. Go to the Data Transformation installation directory.

2. In the setEnv.csh or setEnv.sh environment variable, add the following entry:setenv CMJAVA_PATH “<InformaticaJVMLocation>”

<InformaticaJVMLocation> is the directory of the JVM installed with Informatica on the machine where thePowerCenter Integration Service runs.

3. In CMConfig.xml, set the Java home element to the Informatica JVM location.

For example, if the PowerCenter Integration Service is installed on 64 bit AIX, set the Java home element tothe following value:

<Java> <Home>InformaticaInstallationDir/java/jre/bin/classic</Home> <MaxHeapSize>64</MaxHeapSize></Java>

<InformaticaInstallationDir> is the Informatica installation directory.

PowerCenter Configuration 39

ICU Library Files on UNIXData Transformation must use the latest version of the International Component for Unicode (ICU) library fromInformatica. The ICU library is packaged and installed with Data Transformation. If Informatica is installed afterData Transformation and contains a later version of the ICU library, set the library path so that DataTransformation uses the Informatica ICU library.

On UNIX, set the library path to the following value:

UNIX Platform Variable Name Value

Solaris andLinux

LD_LIBRARY_PATH “<InformaticaInstallationDir>/server/bin:<CDEInstallationDir>/bin”

AIX LIBPATH “<InformaticaInstallationDir>/server/bin:<CDEInstallationDir>/bin”

HP-UX SHLIB_PATH “<InformaticaInstallationDir>/server/bin:<CDEInstallationDir>/bin”


C H A P T E R 6

Repository DatabasesThis chapter includes the following topics:

¨ Repository Database Overview, 41

¨ Data Quality and Data Services Repository, 41

¨ PowerCenter Repositories, 43

Repository Database OverviewThe Informatica platform uses repositories to store metadata created in the Informatica products. Each repositoryhas its own required parameters. Before you create a service that has an associated repository, set up a databasewith the required parameters.

Data Quality and Data Services RepositoryData Quality and Data Services store data and metadata in the Model repository. Before you create the ModelRepository Service, set up a database and database user account for the Model repository.

You can create the Model repository in the following relational database systems:

¨ Oracle

¨ IBM DB2

¨ Microsoft SQL Server

For more information about configuring the database, see the documentation for your database system.

Use the following guidelines when you set up the Model repository database and user account:

¨ The database must be accessible to all gateway nodes in the Informatica domain.

¨ The Model repository can be in the same database schema as the PowerCenter, Metadata Manager, or DataAnalyzer repositories. However, the Model repository cannot be in the same database schema as the domainconfiguration repository.

Oracle Database RequirementsUse the following guidelines when you set up the database on Oracle:

¨ Set the open_cursors parameter to 1000.

41

¨ The database user account must have the CONNECT, RESOURCE, and CREATE VIEW privileges.

IBM DB2 Database RequirementsUse the following guidelines when you set up the repository on IBM DB2:

¨ 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 following configuration parameters:

Parameter Value

applheapsz 8192

appl_ctl_heap_sz 8192

logfilsiz 8000

DynamicSections 1000

maxlocks 98

locklist 50000

auto_stmt_stats ONNote: For IBM DB2 9.5 only

¨ Set the tablespace pageSize parameter to 32768.

In a single-partition database, specify a tablespace that meets the pageSize requirements. If you do not specifya tablespace, the default tablespace must meet the pageSize requirements.

In a multi-partition database, you must specify a tablespace that meets the pageSize requirements.

Define the tablespace on a single node.

¨ The database user account must have the CREATETAB and CONNECT privileges.

Note: The default value for DynamicSections in DB2 is too low for the Informatica domain configuration repositoryand Model repository. Informatica requires a larger DB2 package than the default. When you set up the DB2database for the domain configuration repository or a Model repository, you must set the DynamicSectionsparameter to at least 1000. If the DynamicSections parameter is set to a lower number, you can encounterproblems when you install Informatica or when you work with the Analyst tool or Developer tool. The followingerror message can appear:

[informatica][DB2 JDBC Driver]No more available statements. Please recreate your package with a larger dynamicSections value.

IBM DB2 Version 9.1If the Model repository is in an IBM DB2 9.1 database, run the DB2 reorgchk command to optimize databaseoperations. The reorgchk command generates the database statistics used by the DB2 optimizer in queries andupdates.

42 Chapter 6: Repository Databases

Use the following command:

REORGCHK UPDATE STATISTICS on SCHEMA <SchemaName>

Run the command on the database after you create the repository content.

Microsoft SQL Server Database RequirementsUse the following guidelines when you set up the repository on Microsoft SQL Server:

¨ Set the read committed isolation level to READ_COMMITTED_SNAPSHOT to minimize locking contention.

To set the isolation level for the database, run the following command:

ALTER DATABASE DatabaseName SET READ_COMMITTED_SNAPSHOT ONTo verify that the isolation level for the database is correct, run the following command:

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 permissions.

PowerCenter RepositoriesPowerCenter stores data and metadata in repositories in the domain. Before you create the PowerCenterapplication services, set up the databases and database user accounts for the repositories.

You can create the repositories in the following relational database systems:

¨ Oracle

¨ IBM DB2

¨ Microsoft SQL Server

Set up a database and user account for the following repositories:

¨ PowerCenter repository

¨ Data Profiling warehouse

¨ Data Analyzer repository

¨ Metadata Manager repository

Rules and Guidelines for Database and User AccountsEach repository has specific requirements for optimal processing. Configure the database for the type of repositoryon the database.

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 toselect, insert, update, and delete data from tables.

¨ Use 7-bit ASCII to create the password for the account.

¨ You can store the following repositories in the same database schema and use the same database useraccount:

- PowerCenter repository

- Data Analyzer repository

- Metadata Manager repository

PowerCenter Repositories 43

¨ If you use Oracle 10.2 for a repository database, grant Resource permission to the user. The Resourcepermission is granted independent of the Connect privilege in Oracle 10.2.

Oracle (Metadata Manager)Configure the following properties for a Metadata Manager repository on Oracle:

Property Setting Oracle Version Notes

pga_aggregate_target 100 - 200 MB All Configure pga_aggregate_target andsort_area_size in ora.init

sort_area_size 50 MB Oracle 9i Configure pga_aggregate_target andsort_area_size in ora.init

Temp tablespace(minimum requirement)

2 GB All

Rollback/undo tablespace 1 - 2 GB All Undo is available in Oracle 10g and higher.

If a Metadata Manager repository on Oracle needs to store metadata in a multibyte language, set theNLS_LENGTH_SEMANTICS parameter to CHAR in the Metadata Manager repository database. Default is BYTE.

Oracle (PowerCenter, Data Analyzer, Metadata Manager)Configure parameters in the Oracle database based on the type of repository you create.

Storage Parameters (PowerCenter, Data Analyzer)To prevent a PowerCenter or Data Analyzer repository from using excessive disk space, set the Oracle storageparameters for the tablespace.

When you set up an Oracle database, verify that the storage parameters specified for the tablespace are not toolarge. Storage parameters that are set to very large values cause the repository to use an excessive amount ofspace. Also verify that the default tablespace for the user that owns the repository tables is set correctly.

The following example shows how to set the recommended storage parameters, assuming that the repository isstored in the “REPOSITORY” tablespace:

ALTER TABLESPACE "REPOSITORY" DEFAULT STORAGE ( INITIAL 10K NEXT 10K MAXEXTENTS UNLIMITED PCTINCREASE 50 );

Verify or change these parameters before you create the repository.

Permissions (PowerCenter, Data Analyzer, Metadata Manager)If you use Oracle 10.2 for a PowerCenter, Data Analyzer, or Metadata Manager repository, grant Resourcepermission to the user. The Resource permission is granted independent of the Connect privilege in Oracle 10.2.

IBM DB2 (PowerCenter)When you set up an IBM DB2 database, the database administrator can define the database on a single node.You can optimize repository performance on an IBM DB2 database when you store a repository in a single-nodetablespace. When the tablespace contains one node, the PowerCenter Client and PowerCenter IntegrationService 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. The PowerCenterRepository Service creates all repository tables in the same tablespace. The PowerCenter repository stores thetablespace name so that when you upgrade the repository, the Repository Service uses the same tablespacename.

If you do not specify the tablespace name when you create, copy, or restore a repository, the IBM DB2 systemspecifies the default tablespace for each repository table.

IBM DB2 (Metadata Manager)When you configure a Metadata Manager repository on IBM DB2 or use IBM DB2 as a metadata source, configurethe following settings:

¨ Temporary tablespace and heap sizes

¨ Locking parameters

Temporary Tablespace and Heap SizesIf the Metadata Manager repository or the metadata source resides on an IBM DB2 database, configure thesystem temporary tablespaces and reset the minimum heap sizes.

When you create the Metadata Manager repository on an IBM DB2 database, most of the tables are created withdefault tablespace page sizes of 4 KB. Other tables require larger page sizes, such as 8 KB, 16 KB, and 32 KB.

When Metadata Manager sorts rows returned by database queries from tables with tablespace sizes larger thanthe default 4 KB, the database uses the System Temporary tablespace with the same page size as the table beingsorted. Metadata Manager uses the System Temporary tablespace to store the data during the sorting process. Ifthe database server cannot find the required System Temporary tablespace, the server displays the following error:

SQL 1585N A system temporary table space with sufficient page size does not exist. SQLSTATE=54048

Ask the IBM DB2 administrator to create system temporary tablespaces with 4 KB, 8 KB, 16 KB, and 32 KB pagesizes. Also, ask the IBM DB2 database administrator to run the following SQL statements on each database toconfigure 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 16384UPDATE DB CFG FOR <DB NAME> USING APPLHEAPSZ 16384UPDATE DBM CFG USING QUERY_HEAP_SZ 8000UPDATE DB CFG FOR <DB NAME> USING LOGPRIMARY 100UPDATE DB CFG FOR <DB NAME> USING LOGFILSIZ 2000UPDATE DB CFG FOR <DB NAME> USING LOCKLIST 1000UPDATE DB CFG FOR <DB NAME> USING DBHEAP 2400"FORCE APPLICATIONS ALL"DB2STOPDB2START

PowerCenter Repositories 45

Locking ParametersThe following table describes the general locking parameters you can configure to avoid deadlocks when you loadmetadata into a Metadata Manager repository on IBM DB2:

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, set the DB2_RR_TO_RS parameter to YES to change the read policy from Repeatable Read to ReadStability.

Microsoft SQL Server (Data Analyzer)Install Microsoft SQL Server 2000 or 2005 with case-sensitive collation.

A Data Analyzer repository on Microsoft SQL Server 2005 must have a database compatibility level of 80 orearlier. Data Analyzer uses non-ANSI SQL statements that Microsoft SQL Server supports only on a database witha compatibility level of 80 or earlier.

To set the database compatibility level to 80, run the following query against the database:

sp_dbcmptlevel ‘<DatabaseName>’, 80

Or open the Microsoft SQL Server Enterprise Manager, right-click the database, and select Properties > Options.Set the compatibility level to 80 and click OK.

Microsoft SQL Server (Metadata Manager)If the Metadata Manager repository needs to store metadata in a multibyte language, set the Microsoft SQL Serverdatabase collation to that multibyte language when you install the database or the database instance.

Note: You cannot change the database collation after you set it.


C H A P T E R 7

Starting InformaticaThis chapter includes the following topics:

¨ Starting Informatica Overview, 47

¨ Starting and Stopping Informatica, 48

¨ Logging in to the Administrator Tool, 50

¨ Creating the Application Services, 50

¨ Starting the Developer Tool, 51

¨ Logging in to the Analyst Tool, 52

¨ Starting the PowerCenter Client, 53

¨ Configuring the Informatica Windows Service, 53

Starting Informatica OverviewOn each node where you install Informatica, the installer creates a Windows service or UNIX daemon namedInformatica9.0 to run Informatica Services. When the installation completes successfully, the installer startsInformatica9.0.

You can configure the behavior of the Informatica9.0 Windows service.

Informatica9.0 runs the Service Manager on the node. The Service Manager runs the application services on thenode. The method you use to start or stop Informatica9.0 depends on the operating system. You can also use theAdministrator tool to shut down a node. When you shut down a node, you stop Informatica9.0 on the node.

Informatica9.0 also runs the Administrator tool. The Administrator tool is the administration tool you use toadminister the Informatica domain objects and user accounts. Log in to the Administrator tool to create the useraccounts for users of Informatica and to create and configure the application services in the domain.

Starting Informatica Data Services and Data QualityAfter you install and configure Informatica, you can start Informatica Data Services and Data Quality.

1. Start Informatica9.0.

2. Log in to the Administrator tool to create and manage the Informatica application services and components.

3. Create the application services, including the Model Repository Service, Data Integration Service, and AnalystService.

4. Start the Developer tool.

5. Launch a browser and log in to the Analyst tool.

47

Starting Informatica PowerCenterAfter you install and configure Informatica Services, you can start Informatica PowerCenter.

1. Start Informatica9.0.

2. Log in to the Administrator tool to create and manage the PowerCenter application services and components.

3. Create the application services, including the PowerCenter Repository Service and PowerCenter IntegrationService.

4. If you run the Metadata Manager application, create the Metadata Manager Service.

5. If you run the Data Analyzer application, create the Reporting Service.

6. Start the PowerCenter Client.

Starting and Stopping InformaticaOn UNIX, use a command line program to start or stop the Informatica9.0 daemon. On Windows, you can start orstop Informatica9.0 from the Control Panel or the Start menu.

Starting and Stopping Informatica on UNIXOn UNIX, you use the infaservice command to start and stop the Informatica9.0 daemon. By default, theinfaservice executable file is installed in the following directory:

<InformaticaInstallationDir>/tomcat/bin

1. Go to the directory where infaservice is located.

2. At the command prompt, enter the following command to start the daemon:infaservice startup

Enter the following command to stop the daemon:infaservice shutdown

Note: If you use a softlink to specify the location of infaservice, set the INFA_HOME environment variable tothe location of the Informatica installation directory.

Starting and Stopping Informatica on WindowsYou can use the Services window in the Control Panel or the Start menu shortcut to start or stop InformaticaServices.

Starting or Stopping Informatica from the Start MenuTo start Informatica from the Windows Start menu, click Programs > Informatica[Version] > Server > StartInformatica Services.

To stop Informatica from the Windows Start menu, click Programs > Informatica[Version] > Server > StopInformatica Services.

After you start the Windows service, configure the firewall to allow client machines to access the Service Managerin the domain.

48 Chapter 7: Starting Informatica

Starting or Stopping Informatica from the Control PanelThe 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. Select Services.

4. Right-click the Informatica9.0 service.

5. If the service is running, click Stop.

If the service is stopped, click Start.

After you start the Windows service, configure the firewall to allow client machines to access the Service Managerin the domain.

Windows Firewall ConfigurationWhen you start the Informatica Windows service,the machines where you install the Informatica clients cannotaccess the Service Manager in the Informatica domain. To allow the clients access to the Service Manager, youmust configure the firewall to the grant client machines access to the domain.

On the machine where you created the Informatica domain, add the client machines to the list of firewallexceptions.

1. On the Windows Control Panel, open Windows Firewall.

2. On the Windows Firewall window, click the Exceptions tab.

3. Click Add Program.

4. On the Add a Program window, click Browse.

The infasvcs.exe file runs the Service Manager in the domain.

5. Go to the following directory in the Informatica installation directory:

InformatcaInstallationDirectory\tomcat\bin

6. Select infasvcs.exe and click Open.

The infasvcs.exe file appears in the list of programs.

You can click Change Scope to specify the machines that you want to access Informatica.

7. Verify that the infasvcs.exe file appears in the list of programs and services and that it is enabled.

8. Click OK.

Stopping Informatica in the Administrator ToolWhen you shut down a node using the Administrator tool, you stop the Informatica9.0 service on that node. Youcan abort the processes that are running or allow them to complete before the service shuts down. If you abort anode running Repository Service processes, 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 the Administrator tool.

2. In the Navigator, select the node to shut down.

3. On the Domain tab Actions menu, select Shutdown Node.

Starting and Stopping Informatica 49

Rules and Guidelines for Starting or Stopping InformaticaUse 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 donot 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, ifyou stop Informatica on a node, verify that the port is not used by any other process on the machine before yourestart Informatica. If the port is not available, Informatica will fail to start.

¨ If you do not use the Administrator tool 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 the Administrator tool.

¨ If you have two nodes in a domain with one node configured as a primary node for an application service andthe other node configured as a backup node, start Informatica on the primary node before you start the backupnode. Otherwise, the application service will run on the backup node and not the primary node.

Logging in to the Administrator ToolYou must have a user account to log in to the Administrator tool.

1. Start a Microsoft Internet Explorer or Mozilla Firefox browser.

2. In the Address field, enter the URL for the Administrator tool:http://<host>:<port>/adminconsole

The host and port in the URL represent the host name of the master gateway node and the InformaticaAdministrator port number. If you configure HTTPS for Informatica Administrator, the URL redirects to theHTTPS site:

https://<host>:<https port>/adminconsole3. On the login page, enter the user name and password.

4. Select Native or the name of a specific security domain.

The Security Domain field appears when the Informatica domain contains an LDAP security domain. If youdo not know the security domain that your user account belongs to, contact the Informatica domainadministrator.

5. Click Login.

6. 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.

Creating the Application ServicesBefore you can use the Developer tool, Analyst tool, or PowerCenter, you must create the application services.


Creating Application Services for Data Services and Data QualityBefore you can use the Developer tool and the Analyst tool, log in to the Administrator tool and create theapplication services in the following order:

1. Model Repository Service. This service manages the Model repository that stores metadata created by theDeveloper tool and the Analyst tool. When you create the Model Repository Service, specify the database inwhich to create the Model repository.

2. Data Integration Service. This service performs data integration tasks for the Analyst tool, the Developertool, and external clients. When you create the Data Integration Service, you must associate it with a ModelRepository Service. If you use the Analyst tool, specify the database to use for the Profiling Warehouse.

3. Analyst Service. This service runs the Analyst tool web application. If you want to use the Analyst tool tocreate and run profiles and scorecards, you must create an Analyst Service. When you create the AnalystService, specify the Model Repository Service and Data Integration Service to associate with it. You must alsospecify a staging database and a flat file cache location.

Creating Application Services for PowerCenterBefore you can use PowerCenter, log in to the Administrator tool and create the application services in thefollowing order:

1. PowerCenter Repository Service. This service manages the PowerCenter repository. It retrieves, inserts,and updates metadata in the PowerCenter repository database tables. When you create the PowerCenterRepository Service, specify the database in which to create the PowerCenter repository.

2. PowerCenter Integration Service. This service runs PowerCenter sessions and workflows. When you createthe PowerCenter Integration Service, you must associate it with a PowerCenter Repository Service.

3. Metadata Manager Service. This service runs the Metadata Manager application and manages connectionsbetween the Metadata Manager components. If you want to use Metadata Manager to browse and analyzemetadata from disparate source repositories, you must create a Metadata Manager Service. When you createthe Metadata Manager Service, specify the PowerCenter Integration Service to associate with it. When youcreate the Metadata Manager Service, specify the database in which to create the Metadata Managerrepository.

4. Reporting Service. This service runs the Data Analyzer application in an Informatica domain. If you want touse Data Analyzer to create and run reports, you must create a Reporting Service. When you create theReporting Service, specify the reporting source to associate with it. When you create the Reporting Service,specify the database in which to create the Data Analyzer repository.

Starting the Developer ToolWhen you start the Developer tool, you connect to a Model repository. The Model repository stores metadatacreated in the Developer tool. The Model Repository Service manages the Model repository. Connect to therepository 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 doesnot appear when you run the Developer tool subsequently.

2. Click Workbench.

Starting the Developer Tool 51

The first time you start the Developer tool, you must select the repository in which to save the objects youcreate.

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.

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 toolthe next time, you can connect to the same repository.

Logging in to the Analyst ToolThe Analyst Service runs the the Analyst tool web client. You must create an Analyst Service in the Administratortool before you start the Analyst tool.

1. Start a Microsoft Internet Explorer or Mozilla Firefox browser

2. In the Address field, enter the URL for the Analyst tool:http://<host>:<port>/AnalystTool

3. On the login page, enter the user name and password.

4. Select Native or the name of a specific security domain.

The Security Domain field appears when the Informatica domain contains an LDAP security domain. If youdo not know the security domain that your user account belongs to, contact the Informatica domainadministrator.

5. Click Login.

You can also use the Service URL link for the Analyst Service to start the the Analyst tool web client from theAdministrator tool.


Starting the PowerCenter ClientWhen you start the PowerCenter Client, you connect to a PowerCenter repository. The PowerCenter repositorystores metadata created in the PowerCenter client. The PowerCenter Repository Service manages thePowerCenter repository. Connect to the repository before you create objects.

1. From the Windows Start menu, click Programs > Informatica[Version] > Client > [Client Application Name].

The first time you run a PowerCenter client application, 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.

Configuring the Informatica Windows ServiceYou can configure the behavior of the Informatica9.0 Windows service when the operating system starts or whenthe service fails, and configure the user account that logs on to the service.

Use the following rules and guidelines when you configure the user account that logs on to the service:

¨ If you store files on a network drive, use a system account instead of the Local System account to runInformatica9.0.

¨ If you configure shared storage on a network drive to store files used by the domain or the application servicesthat run on the domain, the user account that runs Informatica9.0 must have access to the shared location.

¨ If you want to use the Local System account, verify that the user starting Informatica9.0 has access to thenetwork location.

¨ If the user that starts Informatica9.0 cannot access the shared storage location, service processes on the nodefail or the node or domain will not start.

¨ If you configure a system user account, the user account must have the Act as operating system permission.For more information, see the Windows documentation.

To configure the Informatica9.0 service:

1. Open the Windows Control Panel.

Starting the PowerCenter Client 53

2. Select Administrative Tools.

3. Select Services.

4. Double-click Informatica9.0.

The Informatica9.0 Properties dialog box appears.

5. Click the Log On tab.

6. Select This account.

7. Enter the domain and user name or click Browse to locate a system user.

8. Enter and confirm the password for the selected user account.

9. Click the Recovery tab. Select the options to restart Informatica9.0 if the service fails.

For more information about configuring system accounts for services and service restart options on Windows, seethe Windows documentation.


C H A P T E R 8

PowerCenter Data Profiling andData Masking

This chapter includes the following topics:

¨ Setting Up a Data Profiling Warehouse, 55

¨ Setting up the Data Masking Option, 57

Setting Up a Data Profiling WarehouseYou can use PowerCenter Data Profiling to create data profiles of the source data you use in mappings and detectpatterns and exceptions in the data. To use PowerCenter Data Profiling, you must create a Data Profilingwarehouse. The Data Profiling warehouse stores the data profiles and reports.

After you install Informatica, complete the following steps to set up the Data Profiling warehouse:

1. Create a Data Profiling warehouse. Use the Data Profiling warehouse utility to create the Data Profilingwarehouse.

2. Configure connectivity to the Data Profiling warehouse. Create an ODBC connection and create aconnection object to the Data Profiling warehouse.

Step 1. Create a Data Profiling WarehouseCreate a Data Profiling warehouse for each PowerCenter repository in which you want to store data profiles. Youcan create a Data Profiling warehouse on any relational database that Informatica supports as a source or targetdatabase. You can also create the Data Profiling warehouse on the same database instance as the PowerCenterrepository.

Use the Data Profiling warehouse utility to create a Data Profiling warehouse. The utility also creates the DataProfiling warehouse schema and views for Data Analyzer. These views are required if you use Data Analyzer toview Data Profiling reports.

1. At the command prompt, switch to the directory where the Data Profiling warehouse utility is located.

By default, the Data Profiling warehouse utility installs in the following directory:<PowerCenterClientDirectory>\bin\Extensions\DataProfile\ProfileWarehouse

2. Enter DPWarehouseUtil.bat to start the Data Profiling warehouse utility.

55

3. Enter the following command:DPWarehouseUtil createwh

The command uses the following syntax:DPWarehouseUtil createwh<-dbtype|-dbt> database_type<-dburl> database_URL<-dbuser|-dbu> database_user_name<-dbpassword|-dbp> database_password

The following table describes the options and arguments for the Data Profiling warehouse utility:

Option Argument Description

-dbtype-dbt

database_type

Type of database for the Data Profiling warehouse.Specify one of the following values:- ORACLE- SQLSERVER- DB2- SYBASE- INFORMIX- TERADATA

-dburl database_URL

Database connection string. Use the following format:Oracle:jdbc:informatica:oracle://host_name:port;SID=sidOracle RAC:jdbc:informatica:oracle://host_name:port; ServiceName=[Service Name];AlternateServers=(server2:port);LoadBalancing=trueMicrosoft SQL Server:jdbc:informatica:sqlserver://host_name:port;SelectMethod=cursor;DatabaseName=db_nameDB2:jdbc:informatica:db2://host_name:port;DatabaseName=db_nameSybase:jdbc:informatica:sybase://host_name:port;DatabaseName=db_nameInformix:jdbc:informatica:informix://host_name:port;InformixServer=informix_server;DatabaseName=db_nameTeradata:jdbc:teradata://DatabaseServerName/DATABASE=db_name

-dbuser-dbu

database_user_name

User name for the Data Profiling warehouse database.

-dbpassword-dbp

database_password

Password for the Data Profiling warehouse database.

Step 2. Configure Connectivity to the Data Profiling WarehouseCreate an ODBC connection to the Data Profiling warehouse on each PowerCenter Client machine that accessesthe Data Profiling warehouse. After you create the ODBC connection, create a connection object for the DataProfiling warehouse in the Workflow Manager.

56 Chapter 8: PowerCenter Data Profiling and Data Masking


Setting up the Data Masking OptionTo use the Data Masking transformation in a mapping, you must register the Data Masking plug-in and apply theData Masking license to the Informatica license.

Verify that you have the Data Masking incremental license key available. When you add the license, you must beable to access the license key file from the Administration Console. If you do not have a license for Data Masking,contact Informatica Global Technical Support.

To set up Data Masking option, complete the following steps:

1. Register the plug-in.

2. Apply the Data Masking license.

Step 1. Register the Plug-inRegister the Data Masking plug-in with the PowerCenter repository.

The Data Masking plug-in is an XML file that defines the functionality of Data Masking. To register the plug-in, thePowerCenter Repository Service must be running in exclusive mode. Use the Administrator tool or the pmrepRegisterPlugin command to register the plug-in.

The plug-in file for Data Masking is pmdatamasking.xml. When you install Informatica Services, the installer copiespmdatamasking.xml to the following directory:

<InformaticaInstallDir>\server\bin

If you do not have the correct privileges to register the plug-in, contact the domain administrator.

Step 2. Apply the Data Masking License KeyApply the Data Masking license key to the Informatica license. When you apply the incremental license key, theService Manager adds the Data Masking option to the Informatica license and updates the license expiration date.

Use Administrator tool to add the Data Masking license, or use the infacmd UpdateLicense command.

Setting up the Data Masking Option 57

C H A P T E R 9

Troubleshooting an InformaticaInstallation


¨ Installation Troubleshooting Overview, 58

¨ Installation Log Files, 58

¨ Troubleshooting Domains and Nodes, 60

¨ Troubleshooting the PowerCenter Client, 62

¨ Installation Error Messages, 62

Installation Troubleshooting OverviewThis chapter provides information about the Informatica installation process and the cause and resolution of errorsthat occur during installation. The examples included in this chapter describe general troubleshooting strategiesand are not a comprehensive list of possible causes of installation issues.

This chapter provides information on the following topics:

¨ Installation logs. Logs generated during the Informatica installation.

¨ Informatica domain and nodes. Troubleshooting problems related to domain and node creation.

¨ PowerCenter Client. Troubleshooting problems during the PowerCenter Client installation.

¨ Installation error messages. Error messages generated by the installer.

Installation Log FilesYou 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 logsto 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

- Summary logs

- File installation logs

58

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

Debug Log FilesThe installer writes actions and errors to the debug log file. The name of the log file depends on the Informaticacomponent you install.

The following table describes the properties of the debug log files:


Log File Name - Informatica_9.0_Server_Debug.log- Informatica_9.0_Client_Debug.log- Informatica_Installation_Server_Upgrade_Debug.log- Informatica_Installation_Client_Upgrade_Debug.log

Location Installation directory.

Usage Get more information about the actions performed by the installer and get more information aboutinstallation errors. The installer writes information to this file during the installation. If the installergenerates an error, you can use this log to troubleshoot the error.

Contents Detailed summary of each action performed by the installer, the information you entered in the installer,each command line command used by the installer, and the error code returned by the command.

The debug log contains output from the infacmd and infasetup commands used to create the domain, node, andapplication services. It also contains information about starting the application services. You can find moreinformation about errors generated by these commands in the Informatica Message Reference.

Summary Log FileThe summary log file contain summary information about the Informatica component you install.

The following table describes the properties of the summary log files:


Log File Name - summary_server.htm (Windows)- summary_client.htm (Windows)- summary_server.txt (UNIX)


Usage Determine the status of the installation and the installed components. Get more information aboutproperties for the installed components.

Contents Installation status, date, installation set, installation directory, shortcut folder, and configuration properties.The configuration properties include URLs, user names, and passwords.

File Installation Log FileThe file installation log file contains information about the installed files.

Installation Log Files 59

The following table describes the properties of the installation log file:


Log File Name - Informatica_9.0_Server_InstallLog.log- Informatica_9.0_Client_InstallLog.log


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 FilesThe installer starts the Informatica9.0 service. The Informatica9.0 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 troubleshootissues when Informatica9.0 fails to start and you cannot log in to Informatica Administrator. The Service Managerlog files are created on each node.

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, aport is available during installation, but is in use when the Service Manager starts. Use this log toget more information about which port was unavailable during startup of the Service Manager. Thenode.log is in the /tomcat/logs directory.

node.log Log events generated during the startup of the Service Manager on a node. You can use this logto get more information about why the Service Manager for a node failed to start. For example, ifthe Service Manager cannot connect to the domain configuration database after 30 seconds, theService Manager fails to start. The node.log is in the /server/tomcat/logs directory.

Note: The Service Manager also uses node.log to record events when the Log Manager is unavailable. Forexample, if the machine where the Service Manager runs does not have enough available disk space to write logevent files, the Log Manager is unavailable.

Troubleshooting Domains and NodesThe installer can generate errors when creating and configuring domains and nodes during the Informaticainstallation.

You can encounter errors with the following installer tasks:

¨ Adding the domain configuration database

¨ Creating or joining a domain

¨ Starting Informatica9.0

¨ Pinging the domain

¨ Adding a license

60 Chapter 9: Troubleshooting an Informatica Installation

Creating the Domain Configuration DatabaseIf you create a domain, the installer adds the domain configuration metadata to the domain configurationdatabase. The installer uses the options you enter in the Configure Domain Database window to add the domainconfiguration metadata to the domain configuration database. You can store the domain configuration databaseand the PowerCenter repository in one database if you use the same database user name. The installer usesJDBC to communicate with the database. You do not need to configure ODBC or native connectivity on themachine where you install the Informatica server component.

The installer creates and drops a table in the domain configuration database to verify the connection information.The user account for the domain configuration database must have Create privileges on the database. You mustuse a separate user account to store the configuration of each domain in the database.

Creating or Joining a DomainThe 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 thegateway node for the domain on the current machine based on the information you enter in the ConfigureDomain window.

¨ Joining a domain. The installer runs the infasetup DefineWorkerNode command to create a node on thecurrent machine, and runs the infacmd AddDomainNode command to add the node to the domain. The installeruses 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.

For example, the DefineDomain command fails if you click Test Connection and the connection test passes but thedatabase becomes unavailable before you click Next. The DefineDomain command can also fail if the host nameor IP address does not belong to the current machine. Verify that the database for the domain configuration isavailable and that the host name is correct and try again.

If the AddDomainNode command fails, verify that Informatica9.0 is running on the gateway node and try again.

Starting Informatica9.0On Windows, the installer first removes the Informatica9.0 service if it exists. On Windows and UNIX, the installerruns infaservice to start Informatica9.0. To troubleshoot issues when Informatica9.0 fails to start, use theinformation in the installation debug log and the node.log and catalina.out Service Manager log files to identify thecause of the error.

If you create a domain, log in to Informatica Administrator after Informatica9.0 starts to verify that the domain isavailable. If you join a domain, log in to Informatica Administrator after Informatica9.0 starts to verify that the nodewas successfully created and started.

Informatica9.0 can fail to start for the following reasons:

¨ The Service Manager is out of system memory. The Java Runtime Environment (JRE) that startsInformatica9.0 and runs the Service Manager may not have enough system memory to start. Set theINFA_JAVA_OPTS environment variable to configure the amount of system memory used by Informatica. OnUNIX, you can set the memory configuration when you start Informatica9.0.

¨ The domain configuration database is not available. Informatica9.0 fails to start on a node if the ServiceManager on a gateway node cannot connect to the domain configuration database within 30 seconds. Verifythat the domain configuration database is available.

Troubleshooting Domains and Nodes 61

¨ You incorrectly configure the Informatica9.0 user account. Informatica9.0 fails to start if you incorrectlyconfigure the Windows domain, user name, or password when you configure the user account to startInformatica9.0 on Windows. In addition, the user account must have the Act as operating system permission.

Pinging the DomainThe installer runs the infacmd Ping command to verify that the domain is available before it continues theinstallation. The domain must be available so that license objects can be added to the domain. If the Pingcommand fails, start Informatica9.0 on the gateway node.

Adding a LicenseThe installer runs the infacmd AddLicense command to read the Informatica license key file and create a licenseobject in the domain. To enable the PowerCenter Repository Service and PowerCenter Integration Service inInformatica 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 theserial number for an existing license object in the domain. If the serial numbers do not match, the AddLicensecommand fails.

You can get more information about the contents of the license key file used for installation, including serialnumber, version, expiration date, operating systems, and connectivity options in the installation debug log. Youcan get more information about existing licenses for the domain in Informatica Administrator.

Troubleshooting the PowerCenter Client

I installed the PowerCenter Client, but Mapping Architect for Visio does not appear in the Windows Startmenu, and the MappingTemplate folder in the client directory is empty.

You must have the correct version and service pack level of the Microsoft .NET Framework for Mapping Architectfor Visio to install properly.

Uninstall the PowerCenter Client, install the correct version of the Microsoft .NET Framework, and reinstall thePowerCenter Client.

RELATED TOPICS:¨ “PowerCenter Mapping Architect for Visio” on page 14

Installation Error MessagesCannot add license to domain.

Explanation: The installer cannot create a license object in the domain or update an existing license withthe selected license key file using the infacmd AddLicense command.

62 Chapter 9: Troubleshooting an Informatica Installation

User Response: Review the output message in the error dialog box and the installation debug log to identifywhy the command failed. Log in to the Administrator tool to verify that the gateway node forthe domain is available. If you use an incremental license, verify that the serial number in thelicense key file matches the serial number of an existing domain license object.

Cannot add node to domain.

Explanation: The infacmd AddDomainNode command failed. The AddDomainNode command adds thenode name to the domain configuration database. The node host name and port number isadded to the domain configuration metadata by the Service Manager on the gateway nodewhen Informatica9.0 is started on the node.

User Response: Review the output message in the error dialog box and the installation debug log to identifywhy the command failed. Correct the error and click Retry.

Cannot create domain.

Explanation: The infasetup DefineDomain command failed.

User Response: Review the output message in the error dialog box to identify why the command failed.Correct the error and click Retry.

Cannot create node.

Explanation: The infasetup DefineWorkerNode command failed. A domain contains gateway nodes andworker nodes. When you join a domain, the installer can create a worker node on the currentmachine.

User Response: Review the output message in the error dialog box and the installation debug log to identifywhy the command failed. Correct the error and click Retry.

Cannot ping domain.

Explanation: The infacmd Ping command failed to connect to the Informatica domain.

User Response: Review the output message in the error dialog box and the installation debug log to identifywhy the command failed. Verify that the domain is available and try again. StartInformatica9.0 on the gateway node.

Cannot remove Informatica Services service.

Explanation: On Windows, the installer ran the infaservice remove command to remove an existingInformatica9.0 service, but the removal failed.

User Response: If you are installing Informatica on the current machine for the first time, click Ignore.infaservice reports an error if it could not remove the service when the service does not exist.If the service exists on the machine, verify that the user account installing Informatica haspermission to remove a service and click Retry. You can get more information about the errorin the installation debug log.

Cannot start Informatica Services.

Explanation: The infaservice startup command failed to start Informatica9.0.

User Response: Use the node.log and catalina.out Service Manager log files to identify the reason whyInformatica9.0 could not be started on the machine. After you correct the error, click Retry.

Installation Error Messages 63

C H A P T E R 1 0

JDBC and ODBC Driver InstallationThis chapter includes the following topics:

¨ JDBC and ODBC Driver Installation Overview, 64

¨ JDBC Driver Installation, 64

¨ ODBC Driver Installation on Windows, 65

¨ ODBC Driver Installation on UNIX, 66

JDBC and ODBC Driver Installation OverviewTo connect to an SQL data service through a third-party client tool, you must you must install the database driverson the machine that you want to connect from. Download the JDBC and ODBC drivers and configure theconnection based on whether you connect through a JDBC or ODBC client tool.

When you install Informatica Services or Informatica Clients, the installers copy the JDBC and ODBC drivers tothe Informatica installation directory by default. Informatica provides a separate driver installer to install the JDBCand ODBC drivers on a machine that does not have Informatica Services or Informatica Clients.

JDBC Driver InstallationYou can connect to an SQL data service through a JDBC client tool such as the SQL SQuirreL Client or DBClient.

Before you can connect to an SQL data service through a JDBC client tool, you must perform the following tasks:

1. Install the Informatica JDBC driver.

2. Update the CLASSPATH environment variable.

Installing the Informatica JDBC DriverInstall the Informatica JDBC driver on the machine you connect to the SQL data service from. To install the driver,run the Informatica JDBC/ODBC driver installation program.

Updating the CLASSPATHUpdate the CLASSPATH environment variable to include the JDBC driver. The JDBC driver is compiled with Java6.

64

The JDBC driver is installed in the following location:

<Informatica 9.0 Installation Directory>\jdbcdrv\infadsjdbc.jar

ODBC Driver Installation on WindowsYou can connect to an SQL data service through an ODBC client tool such as the MySQL ODBC Client.

Before you can connect to an SQL data service through an ODBC client tool on Windows, you must perform thefollowing tasks:

1. Install the Informatica ODBC driver.

2. Update the system path to include the Java Virtual Machine (JVM) directory.

3. Configure the Informatica ODBC driver.

Installing the Informatica ODBC Driver on WindowsInstall the Informatica ODBC driver on the machine you connect to the SQL data service from. To install the driver,run the Informatica JDBC/ODBC driver installation program.

Updating the System PathUpdate the PATH environment variable to include the Java Virtual Machine (jvm.dll) directory or the Java 6 path.

By default, the jvm.dll file is installed in the following location:

<Informatica 9.0 Installation Directory>\java\jre\bin\server

Note: If you install the ODBC driver on a machine with a Windows 64-bit operating system, you must restart themachine after you update the system path.

Configuring the Informatica ODBC DriverBefore you can connect to an SQL data service through an ODBC client tool on Windows, you must configure theInformatica ODBC driver.

1. Open the Administrative Tools from the Windows Control Panel.

2. Open the Data Sources (ODBC) shortcut.

The ODBC Data Source Administrator appears.

3. Click Add.

4. Select the Informatica Data Services ODBC Driver.

5. Click Finish.

ODBC Driver Installation on Windows 65

6. Configure the driver with the following options:

Option Value

DSN name Any valid data source name.

Connect string jdbc:informatica:sqlds/<optional security domain\><optional user name>/<optional user password>@<domain host name>:<domain HTTP port>?dis=<Data Integration Service name>&sqlds=<runtime SQL data service name>

JDBC Jar <Informatica 9.0 Installation Directory>\jdbcdrv\infadsjdbc.jar

Multi-threaded application Enabled

ODBC Driver Installation on UNIXYou can connect to an SQL data service through an ODBC client tool such as the MySQL ODBC Client.

Before you can connect to an SQL data service through an ODBC client tool on UNIX, you must perform thefollowing tasks:

1. Install the Informatica ODBC driver.

2. Update the shared library environment variable.

3. Update odbc.ini.

Installing the Informatica ODBC Driver on UNIXInstall the Informatica ODBC driver on the machine you connect to the SQL data service from. To install the driver,run the Informatica JDBC/ODBC driver installation program.

Updating the Shared Library Environment VariableSet the shared library environment variable based on the operating system.

Update the shared library environment variable to include the directories where the Java Virtual Machine andDriver Manager library files exist.

The following table describes the shared library environment variable for each operating system:

Operating System Shared Library Environment Variable

AIX LIBPATH

Linux LD_LIBRARY_PATH

Solaris LD_LIBRARY_PATH

Update the shared library environment variable to include the following directories:

¨ The directory where the platform libjvm library resides.

66 Chapter 10: JDBC and ODBC Driver Installation

¨ The directory where the libodbc and libodbcinst libraries reside. This is usually the Driver Manager lib directory.

Updating odbc.iniBefore you can connect to an SQL data service through an ODBC client tool on UNIX, you must update odbc.ini.

1. Edit odbc.ini or copy odbc.ini to the home directory and edit it. This file exists in the $ODBCHOME directory.$ cp $ODBCHOME/odbc.ini $HOME/.odbc.ini

2. Add an entry for the ODBC user under the section [<user name>_odbc]. For example:[<user name>_odbc]ConnectionString=jdbc:informatica:sqlds/<optional security domain\><optional user name>/<optional user password>@<domain host name>:<domain HTTP port>?dis=<Data Integration Service name>&sqlds=<runtime SQL data service name>Driver=$ODBC_DRIVER_INSTALL_LOCATION/bin/$OS/libinfadsodbc.soIsMultiThreaded=trueJDBCDriverLocation=$INFA_HOME/jdbcdrv/infadsjdbc.jarUseDetach=falseWCHARLengthInChars=true

Configure WCHARLengthInChars only for Microstrategy.

ODBC Driver Installation on UNIX 67

C H A P T E R 1 1

Informatica Utilities InstallationThis chapter includes the following topics:

¨ Informatica Utilities Installation Overview, 68

¨ Command Line Programs and Utilities, 68

¨ Configuring the PowerCenter Utilities, 69

¨ Configuring the Metadata Manager Utilities, 70

Informatica Utilities Installation OverviewThe Informatica installation includes customer support tools and command line programs and utilities for thefollowing products:

¨ PowerCenter

¨ Data Services

¨ Data Quality

¨ Metadata Manager

¨ PowerExchange

When you install Informatica Services or the PowerCenter Client, the command line programs and utilities areinstalled by default.

You can also install and run the programs and utilities on any machine without installing the Informatica products.Informatica provides a separate ZIP file to install the command line programs and utilities on a machine that doesnot have Informatica products installed.

The Informatica utilities are included in a ZIP file. Download the following file for your operating system:

Informatica_9.0_cmd_utilities_<OperatingSystem>.zip

To install the utilities, extract the utilities from the file on the machine where you want to run them. Configure thepath and environment variables as required by the command line utilities.

Command Line Programs and UtilitiesYou can use the Informatica utilities to manage the Informatica domain, application services, and objects from thecommand line on any machine that can access the Informatica domain.

68

The following table describes the Informatica command line programs:

Command Line Program Product Description

infacmd PowerCenterData ServicesData QualityPowerExchange

Administer the Informatica domain andapplication services and processes,including the repository and integrationservices. You can also use infacmd toaccess and administer licenses and logevents and export and import objectsand user accounts. For moreinformation about infacmd, see theInformatica Command Reference.

pmcmd PowerCenter Manage workflows. Use pmcmd to start,stop, schedule, and monitor workflows.For more information about pmcmd, seethe Informatica Command Reference .

pmpasswd PowerCenter Encrypt passwords to use with pmcmdand pmrep environment variables. Formore information about pmpasswd, seethe Informatica Command Reference.

pmrep PowerCenter Performs repository administrationtasks. Use pmrep to list repositoryobjects, create and edit groups, andrestore and delete repositories. Formore information about pmrep, see theInformatica Command Reference.

mmcmd Metadata Manager Load and manage resources, importand export models, custom resources,and business glossaries. Create anddelete Metadata Manager repositorycontent, and restore PowerCenterrepository content.

backupCmdLine Metadata Manager Back up and restore the MetadataManager repository.

Configuring the PowerCenter UtilitiesThe PowerCenter utilities are installed in the following directory:

<UtilitiesInstallationDir>/PowerCenter/server/bin

In addition, the infacmd command line program is installed in the following directory:

<UtilitiesInstallationDir>/PowerCenter/isp/bin

Before you run the PowerCenter utilities, use the following guidelines to configure the program files and variables:

¨ infacmd requires the Java directory.

¨ To run pmrep, pmcmd, and pmpasswd on UNIX, you must copy the domains.infa file for the Informatica domainto the utilities directory. You must also set INFA_HOME, the PATH environment variable, and the library pathenvironment variable to the location of the utilities.

Configuring the PowerCenter Utilities 69

Configuring the Metadata Manager UtilitiesThe Metadata Manager utilities require access to the Informatica domain and services. Modify the utility programsand configure the environment variables with the location of the JVM and Informatica libraries.

Note: You cannot use mmcmd installed with Informatica utilities or with the PowerCenter Client to create, update,or delete Metadata Manager repository content or to restore PowerCenter repository content. You must usemmcmd installed with Informatica Services.

1. Go to the directory where you extracted the utility files.

The Metadata Manager utilities are in the following directory:<UtilitiesInstallationDir>\MetadataManager\utilities

2. With a text editor, open the mmcmd.bat file on Windows or the mmcmd.sh file on UNIX.

3. Set the JAVA_HOME environment variable to the PowerCenter java directory in the command line utilitiesinstallation.

For example:set JAVA_HOME=<UtilitiesInstallationDir>\PowerCenter\java

4. Set the INFA_HOME environment variable to the PowerCenter directory in the command line utilitiesinstallation.

For example:set INFA_HOME=<UtilitiesInstallationDir>\PowerCenter

5. On Solaris, verify that the LD_LIBRARY_PATH environment variable contains the following directories:

¨ Solaris x86 64 bit${JAVA_HOME}/jre/lib/amd64/server:${JAVA_HOME}/jre/lib/amd64/jli

¨ Solaris Sparc 64 bit${JAVA_HOME}/jre/lib/sparcv9/server:${JAVA_HOME}/jre/lib/sparcv9/jli

¨ Solaris Sparc${JAVA_HOME}/jre/lib/sparc/server

6. Save the mmcmd.bat or mmcmd.sh file.

7. Use a text editor to open the backupCmdLine.bat file on Windows or the backupCmdLine.sh file on UNIX.

8. Repeat steps 3 through 6 for the backupCmdLine.bat or backupCmdLine.sh file.

70 Chapter 11: Informatica Utilities Installation

C H A P T E R 1 2

Informatica DocumentationInstallation


¨ Documentation Installation Overview, 71

¨ Installing the Informatica Documentation, 71

¨ Viewing Informatica Documentation, 72

¨ Troubleshooting, 72

Documentation Installation OverviewThe Informatica Documentation DVD contains the Informatica documentation in PDF format.

Use the Informatica Documentation DVD to install the PDFs and the application used to view PDFs.

The Informatica Documentation DVD includes the following components:

¨ Informatica documentation. Informatica documentation in PDF format. It includes an application that providesan easy way to select and view Informatica documents.

¨ Informatica Quick Start guides. Brief descriptions of the Informatica installation steps. Use the Quick Startguides to track the required installation information as you complete the installation process.

Installing the Informatica DocumentationTo install Informatica documentation:

1. On the Informatica Documentation DVD or the location where you downloaded the documentation, locate andrun the documentation installation file from the root directory:

install.batThe Welcome window introduces the Informatica Documentation installation.

2. Click Next.

The Installation Directory window appears.

3. Enter the full path of the folder where you want to install the Informatica documentation.

71

4. Click Next.

The Pre-Installation Summary window appears.

The Informatica documentation and the application is installed in the following directory:C:\Informatica\[Version]\Documentation

5. Click Install.

When the documentation installation completes, the Post-Installation Summary window indicates whether theinstallation completed successfully.

6. Click Done.

The Informatica documentation installer creates a documentation shortcut in the Informatica program group.

Viewing Informatica DocumentationYou can navigate through the menu pages of the Informatica documentation viewer to find the documentation youneed. The documentation are grouped by product.

To view Informatica documentation:

1. To start the Informatica documentation application, choose Start > Programs > Informatica PowerCenter[Version] > Documentation > Start Documentation.

The Informatica Documentation window appears.

2. Click the name of the product for the documentation that you want to view. The name of the books appear inthe left pane.

3. Click the name of the document to view the document.

To go back to the previous window, click Back. Click Main Page to view the start page.

Troubleshooting

When I try to view a PDF, I get the following error:Install Adobe Reader to view the document.

Use the following methods in the following order to resolve the error:

¨ Make sure Adobe Reader is installed on your machine.

¨ If Adobe Reader is installed, open Adobe Reader and click Help > Check for Updates. Install any updates.

¨ Install the latest version of Adobe Reader.

72 Chapter 12: Informatica Documentation Installation

C H A P T E R 1 3

UninstallationThis chapter includes the following topics:

¨ Uninstallation Overview, 73

¨ Running the Uninstaller, 74

¨ Uninstalling in Graphical Mode, 75

¨ Uninstalling in Console Mode, 75

Uninstallation OverviewOn UNIX, uninstall Informatica from the command line. On Windows, uninstall Informatica from the Windows Startmenu.

When you uninstall Informatica, files are deleted and all configuration is cleared. The process does not delete filesthat are not installed with Informatica. For example, the installation process creates temporary directories. Theuninstaller does not keep a record of these directories and therefore cannot delete them. You must manuallydelete these directories for a clean uninstallation.

Rules and Guidelines for UninstallationUse the following rules and guidelines when you uninstall Informatica components:

¨ Uninstalling Informatica does not affect the Informatica repositories. The uninstaller removes the Informaticafiles. It does not remove repositories from the database. If you need to move the repositories, you can backthem up and restore them to another database.

¨ Uninstalling Informatica does not remove the metadata tables from the domain configuration database. If youinstall Informatica again using the same domain configuration database and user account, you must manuallyremove the tables or choose to overwrite the tables. You can use the infasetup BackupDomain command toback 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 theuninstaller.

¨ The uninstaller does not create a log of the uninstallation process. At the end of the uninstallation process, theuninstaller displays the names of the files and directories that could not be removed.

¨ If you install Informatica Services and the Informatica Clients in the same directory, and then uninstallInformatica Services, the uninstaller removes the ODBC directory. The ODBC directory is required byInformatica Clients. You must reinstall Informatica Services or Informatica Clients to reinstall the ODBC drivers.

73

Running the UninstallerTo uninstall Informatica services or the Informatica clients, use the uninstaller created during the installation. OnWindows, do not use the Control Panel to remove the Informatica program. Uninstalling with the Control Paneldoes not completely remove Informatica components.

When you install Informatica Services or Informatica Cients, the installer creates an uninstallation directory in theInformatica installation directory. The uninstallation directory name depends on the installation you perform.

The following table lists the uninstallation directory for each type of installation:

Installation Uninstallation Directory Name

Informatica Services <InstallationDirectory>/Uninstaller_Server

Informatica Clients <InstallationDirectory>/Uninstaller_Client

Before You UninstallBefore you uninstall Informatica, stop all Informatica services. The uninstallation process cannot remove the filesthat are being used by a service that is running.

Uninstallation OptionsThe method you use to uninstall depends on your operating system:

¨ UNIX. Use the console mode interface or graphical mode interface to uninstall Informatica.

¨ Windows. Use the graphical mode to uninstall the Informatica server or client components.

Running the Uninstaller on UNIXTo uninstall Informatica, run the uninstaller in the uninstallation directory.

For example, you want to uninstall Informatica components that you installed in the /Informatica/Version9.0directory. To uninstall Informatica components, go to the following directory:

/Informatica/Version9.0/Uninstaller_Server

Type the following command to run the uninstaller:

./uninstaller [-console]

Running the Uninstaller on WindowsThe installer creates a shortcut to the uninstaller from the Windows Start menu.

To uninstall Informatica Services on Windows, click Start > Program Files > Informatica [Version] > Server >Uninstaller.

To uninstall Informatica Clients on Windows, click Start > Program Files > Informatica [Version] > Client >Uninstaller.

74 Chapter 13: Uninstallation

Uninstalling in Graphical ModeThe uninstallers for Informatica Services and Informatica Clients display similar windows. You can use thefollowing procedure to uninstall any Informatica component.

1. On UNIX, go to the uninstallation directory of the Informatica component that you want to uninstall and typethe following command to run the uninstaller:

./uninstallerOn Windows, click Start > Program Files > Informatica [Version] > Server > Uninstaller.

The Uninstall Informatica window displays information about the uninstallation process.

2. Click Next.

The uninstaller displays the names of the files as they are deleted. When the uninstallation processcompletes, the uninstaller displays the Uninstallation Complete window.

If not all files are deleted, the Uninstallation Complete window displays the list of files that were not deleted.

On Windows, when you uninstall Informatica, you must restart the machine to complete the uninstallation.When you uninstall the Informatica clients you do not need to restart.

3. Select to restart immediately or later and click Done.

If the uninstaller does not delete all files, review the files and directories to determine if it is safe to delete them.Then delete them manually.

Uninstalling in Console ModeUninstalling in console mode on UNIX is similar to uninstalling in graphical mode. When you uninstall in consolemode, the uninstaller removes the installed Informatica files.

To exit the uninstaller running in console mode, enter quit at any prompt.

1. Go to the uninstallation directory for the Informatica components that you want to uninstall.

2. To start the uninstaller, type the following command:./uninstaller -console

Use the -console option if you are running X Window and you want to use console mode. Otherwise, theuninstaller starts in graphical mode.

3. Press Enter.

After the uninstallation process completes, the console displays the results of the uninstallation.

Uninstalling in Graphical Mode 75

C H A P T E R 1 4

Informatica Platform ConnectivityThis chapter includes the following topics:

¨ Connectivity Overview, 76

¨ Domain Connectivity, 77

¨ Informatica Data Quality and Informatica Data Services Connectivity, 77

¨ PowerCenter Connectivity, 79

¨ Native Connectivity, 83

¨ ODBC Connectivity, 84

¨ JDBC Connectivity, 85

Connectivity OverviewThe Informatica platform uses the following types of connectivity communicate between clients, services, andother components in the domain:

¨ TCP/IP network protocol. Application services and the Service Managers in a domain use TCP/IP networkprotocol to communicate with other nodes and services. The clients also use TCP/IP to communicate withapplication services. You can configure the host name and port number for TCP/IP communication on a nodewhen you install Informatica Services. You can configure the port numbers used for services on a node whenduring installation or in the Administrator tool.

¨ Native drivers. Native drivers are packaged with the database server and client software. The Data IntegrationService, PowerCenter Integration Service, and the PowerCenter Repository Service use native drivers tocommunicate with databases. You must install and configure native database client software on the machineswhere the integration services and the PowerCenter Repository Service run.

¨ ODBC. The ODBC drivers are installed with both Informatica Services and Informatica Clients. The integrationservices use ODBC drivers to communicate with databases.

¨ JDBC. The Model Repository Service uses JDBC to connect to the Model repository database. The ReportingService uses JDBC to connect to the Data Analyzer repository and data sources. The Metadata ManagerService uses JDBC to connect to the Metadata Manager repository and metadata source repositories.

The server installer uses JDBC to connect to the domain configuration database during installation. Thegateway nodes in the Informatica domain use JDBC to connect to the domain configuration database.

76

Domain ConnectivityServices on a node in an Informatica domain use TCP/IP to connect to services on other nodes. Because servicescan run on multiple nodes in the domain, services rely on the Service Manager to route requests. The ServiceManager on the master gateway node handles requests for services and responds with the address of therequested service.

Nodes communicate through TCP/IP on the port you select for a node when you install Informatica Services.When you create a node, you select a port number for the node. The Service Manager listens for incoming TCP/IPconnections on that port.

Informatica Data Quality and Informatica Data ServicesConnectivity

Data Quality and Data Services use TCP/IP to connect between services and clients. The services and clients useJDBC, ODBC, or native drivers to connect to databases.

The following figure shows an overview of the connectivity for components in Informatica Data Quality andInformatica Data Services:

Data Quality and Data Services uses connection objects to define connectivity information for source and targetdatabases. The connection objects can use native or ODBC connectivity. The Data Integration Service usesconnection objects to connect to sources and targets.

The services and clients connect in the following ways:

¨ Model Repository Service. The Model Repository Service uses TCP/IP to read or write data and metadata inthe Model repository. It uses TCP/IP to communicate with the Data Integration Service and the clients.

¨ Data Integration Service. The Data Integration Service uses ODBC or native drivers to connect and read datafrom the source database or or write data to target database. It uses TCP/IP to communicate with ModelRepository Service and the clients.

¨ Informatica Developer. The Developer tool uses TCP/IP to send data transformation requests to the DataIntegration Service. When you preview mappings or data objects in the Developer tool, it uses JDBC or ODBCdrivers to connect to the source or target database to fetch the metadata required for preview.

Domain Connectivity 77

¨ Informatica Analyst. The Analyst tool uses TCP/IP to send requests to the Data Integration Service. Whenyou preview profiles or objects in the Analyst tool, it uses JDBC or ODBC drivers to connect to the source ortarget database to fetch the metadata required for preview.

If you use ODBC to connect to the source or target database, install the ODBC driver on the node where theAnalyst Service runs.

Model Repository ConnectivityThe Model Repository Service connects to the Model repository using JDBC drivers. Informatica Developer,Informatica Analyst, Informatica Administrator, and the Data Integration Service communicate with the ModelRepository Service over TCP/IP. Informatica Developer, Informatica Analyst, and Data Integration Service areModel repository clients.

The following figure shows how a Model repository client connects to the Model repository database:

1. A Model repository client sends a repository connection request to the master gateway node, which is the entry point to the domain.2. The Service Manager sends back the host name and port number of the node running the Model Repository Service. In the diagram, the

Model Repository Service is running on node A.3. The repository client establishes a TCP/IP connection with the Model Repository Service process on node A.4. The Model Repository Service process communicates with the Model repository database and performs repository metadata transactions

for the client. This communication occurs over JDBC.

Note: The Model repository tables have an open architecture. Although you can view the repository tables, nevermanually edit them through other utilities. Informatica is not responsible for corrupted data that is caused bycustomer alteration of the repository tables or data within those tables.

78 Chapter 14: Informatica Platform Connectivity

PowerCenter ConnectivityPowerCenter uses the TCP/IP network protocol, native database drivers, ODBC, and JDBC for communicationbetween the following PowerCenter components:

¨ PowerCenter Repository Service. The PowerCenter Repository Service uses native database drivers tocommunicate with the PowerCenter repository. The Repository Service uses TCP/IP to communicate with otherPowerCenter components.

¨ PowerCenter Integration Service. The PowerCenter Integration Service uses native database connectivityand ODBC to connect to source and target databases. The Integration Service uses TCP/IP to communicatewith other PowerCenter components.

¨ Data Analyzer and Metadata Manager. Data Analyzer and Metadata Manager use JDBC and ODBC toaccess data sources and repositories.

¨ PowerCenter Client. The PowerCenter Client uses ODBC to connect to source and target databases. ThePowerCenter Client uses native protocol to communicate with the PowerCenter Repository Service andIntegration Service.

The following figure shows an overview of PowerCenter components and connectivity:

The following table lists the drivers used by PowerCenter components:

Component Database Driver

PowerCenter Repository Service PowerCenter Repository Native

PowerCenter Integration Service SourceTargetStored ProcedureLookup

NativeODBC

Data Analyzer Data Analyzer Repository JDBC

Data Analyzer Data Source JDBCODBC with JDBC-ODBC bridge

Metadata Manager Metadata Manager Repository JDBC

PowerCenter Connectivity 79

Component Database Driver

PowerCenter Client PowerCenter Repository Native

PowerCenter Client SourceTargetStored ProcedureLookup

ODBC

Custom Metadata Configurator(Metadata Manager Client)

Metadata Manager Repository JDBC

Repository Service ConnectivityThe PowerCenter Repository Service manages the metadata in the PowerCenter repository database. Allapplications that connect to the repository must connect to the PowerCenter Repository Service. The PowerCenterRepository Service uses native drivers to communicate with the repository database.

The following table describes the connectivity required to connect the Repository Service to the repository andsource and target databases:

Repository Service Connection Connectivity Requirement

PowerCenter Client TCP/IP

PowerCenter Integration Service TCP/IP

PowerCenter Repository database Native database drivers

The PowerCenter Integration Service connects to the Repository Service to retrieve metadata when it runsworkflows.

Connecting from the PowerCenter ClientYou can connect to the PowerCenter Repository Service through PowerCenter Client applications by adding adomain and repository in the PowerCenter Client application. When you connect to the repository from aPowerCenter Client application, the client application sends a connection request to the Service Manager on thegateway node. The Service Manager returns the host name and port number of the node running the PowerCenterRepository Service. The PowerCenter Client connects directly to the PowerCenter Repository Service using TCP/IP.

Connecting to DatabasesThe PowerCenter Repository Service uses the connection information for the service and native database driversto communicate with the repository. To connect a PowerCenter Repository Service to a repository database, youconfigure the database properties in the Administrat tool. You must install and configure the native databasedrivers for the repository database on the machine where the PowerCenter Repository Service runs.


Integration Service ConnectivityThe PowerCenter Integration Service connects to the repository to read repository objects. The PowerCenterIntegration Service connects to the repository through the PowerCenter Repository Service. Use the Administratortool to configure an associated repository for the Integration Service.

The following table describes the connectivity required to connect the PowerCenter Integration Service to theplatform components, source databases, and target databases:

PowerCenter Integration ServiceConnection

Connectivity Requirement

PowerCenter Client TCP/IP

Other PowerCenter Integration ServiceProcesses

TCP/IP

Repository Service TCP/IP

Source and target databases Native database drivers or ODBCNote: The PowerCenter Integration Service on Windows and UNIX can useODBC drivers to connect to databases. You can use native drivers to improveperformance.

The PowerCenter Integration Service includes ODBC libraries that you can use to connect to other ODBC sources.The Informatica installation includes ODBC drivers.

For flat file, XML, or COBOL sources, you can either access data with network connections, such as NFS, ortransfer data to the PowerCenter Integration Service node through FTP software. For information aboutconnectivity software for other ODBC sources, refer to your database documentation.

Connecting from the PowerCenter ClientThe Workflow Manager communicates with a PowerCenter Integration Service process over a TCP/IP connection.The Workflow Manager communicates with the PowerCenter Integration Service process each time you start aworkflow or display workflow details.

Connecting to the PowerCenter Repository ServiceWhen you create or configure the PowerCenter Integration Service, you specify the repository associated with theIntegration Service. The PowerCenter Integration Service connects to this PowerCenter Repository Service usingTCP/IP to retrieve metadata when it runs a workflow.

When you install PowerCenter Services, the installer configures the associated repository for the PowerCenterIntegration Service.

Connecting to DatabasesUse the Workflow Manager to create connections to databases. You can select native database drivers for theIntegration Service or you can use ODBC. For each connection, you must specify the database user name,password, and native connect string. The Integration Service uses this information to connect to the databasewhen it runs the session.

Note: PowerCenter supports ODBC drivers, such as ISG Navigator, that do not need user names and passwordsto connect. To avoid using empty strings or nulls, use the reserved words PmNullUser and PmNullPasswd for theuser name and password when you configure a database connection. The Integration Service treats PmNullUserand PmNullPasswd as no user and no password.

PowerCenter Connectivity 81

PowerCenter Client ConnectivityThe PowerCenter Client uses ODBC drivers and native database client connectivity software to communicate withdatabases. It uses TCP/IP to communicate with the Integration Service and with the repository.

The following table describes the connectivity types required to connect the PowerCenter Client to the IntegrationService, repository, and source and target databases:

PowerCenter Client Connection Connectivity Requirement

Integration Service TCP/IP

Repository Service TCP/IP

Databases ODBC connection for each database

Connecting to the RepositoryYou can connect to the repository using the PowerCenter Client tools. All PowerCenter Client tools use TCP/IP toconnect to the repository through the Repository Service each time you access the repository to perform taskssuch as connecting to the repository, creating repository objects, and running object queries.

Connecting to DatabasesTo connect to databases from the Designer, use the Windows ODBC Data Source Administrator to create a datasource for each database you want to access. Select the data source names in the Designer when you performthe following tasks:

¨ Import a table or a stored procedure definition from a database. Use the Source Analyzer or TargetDesigner to import the table from a database. Use the Transformation Developer, Mapplet Designer, orMapping Designer to import a stored procedure or a table for a Lookup transformation.

To connect to the database, you must also provide your database user name, password, and table or storedprocedure owner name.

¨ Preview data. You can select the data source name when you preview data in the Source Analyzer or TargetDesigner. You must also provide your database user name, password, and table owner name.

Connecting to the Integration ServiceThe Workflow Manager and Workflow Monitor communicate directly with the Integration Service over TCP/IP eachtime you perform session and workflow-related tasks, such as running a workflow. When you log in to a repositorythrough the Workflow Manager or Workflow Monitor, the client application lists the Integration Services that areconfigured for that repository in the Administrator tool.

Data Analyzer and Metadata Manager ConnectivityTo connect to a Data Analyzer repository, Data Analyzer requires a Java Database Connectivity (JDBC) driver. Toconnect to the data source, Data Analyzer can use a JDBC driver or a JDBC-ODBC bridge with an ODBC driver.

To connect to a Metadata Manager repository, Metadata Manager requires a JDBC driver. The Custom MetadataConfigurator uses JDBC drivers to connect to the Metadata Manager repository.

JDBC drivers are installed with Informatica Services and Informatica Clients. You can use the installed JDBCdrivers to connect to the Data Analyzer or Metadata Manager repository, data source, or to a PowerCenterrepository.


The Informatica installers do not install ODBC drivers or the JDBC-ODBC bridge for Data Analyzer or MetadataManager.

Native ConnectivityNative drivers are packaged with database server and client software. The Data Integration Service and thePowerCenter Repository Service and Integration Service use native drivers to communicate with databases. Whencommunicating with a database, the services pass database calls directly to the native drivers installed with thedatabase client software. The client software passes the calls to the database, and returns information from thedatabase to the service.

For example, the PowerCenter Integration Service writes session data to a DB2 target. When you run the session,the PowerCenter Integration Service reads target database information from the target database connection storedin the repository. It uses this information to connect to the target database through the drivers included with theDB2 Client Application Enabler (CAE) installed on the PowerCenter Integration Service node. The PowerCenterIntegration Service performs all transactions with the target database through this client software.

Establishing Native ConnectivityTo establish native connectivity between the application services and a database, you must install the clientsoftware packaged with the database platform on the machine where the service runs.

Native connectivity information includes the database user name, password, and other configuration optionsspecific to the database platform. It also includes a native connect string. The native connect string contains thedatabase name and database server name and allows the application services and the database client to directcalls to the correct database.

The following table describes the native connect string syntax for each supported database system:

Database Connect String Syntax Example

IBM DB2 dbname mydatabase

Informix dbname@servername mydatabase@informix

Microsoft SQL Server servername@dbname sqlserver@mydatabase

Oracle dbname.world (same as TNSNAMES entry) oracle.world

Sybase ASE servername@dbname sambrown@mydatabaseNote: Sybase ASE servername is the nameof the Adaptive Server from the interfacesfile.

Teradata ODBC_data_source_name orODBC_data_source_name@db_name orODBC_data_source_name@db_user_name

TeradataODBCTeradataODBC@mydatabaseTeradataODBC@sambrownNote: Use Teradata ODBC drivers toconnect to source and target databases.

Native Connectivity 83



ODBC ConnectivityOpen Database Connectivity (ODBC) provides a common way to communicate with different database platforms.The PowerCenter Client uses ODBC drivers to connect to source target, lookup, and stored procedure databases.The Data Integration Service and the PowerCenter Integration Service can also use ODBC drivers to connect todatabases.

When communicating with a database, an application passes all database calls to the ODBC driver. The driverinterprets the information and sends it to the native database client connectivity software. From there, theinformation passes to the database that processes the command and sends the requested information back to theapplication.

For example, when you import a source definition using the PowerCenter Client, the PowerCenter Client issues acall to the ODBC driver. The ODBC driver translates the call and passes it to the native database connectivitysoftware, which in turn passes it to the database. The database processes the request and sends the informationback to the Designer, which displays the source definition.

Note: Some ODBC drivers contain wire protocols and do not require the database client software.

Establishing ODBC ConnectivityTo use ODBC connectivity, you must install the following components on the machine hosting the PowerCenterapplication:

¨ Database client software. Install the client software included with the database platform. This installs theclient libraries needed to connect to the database.

¨ ODBC drivers. PowerCenter installs DataDirect closed 32-bit ODBC drivers when you install PowerCenterServices or the PowerCenter Client. Your database platform may also come with an ODBC driver.

After you install the necessary components you must configure an ODBC data source for each database you wantto connect to. A data source contains information that you need to locate and access the database, such asdatabase name, user name, and database password. On Windows, you use the ODBC Data Source Administratorto create a data source name. On UNIX, you add data source entries to the odbc.ini file found in the system$ODBCHOME directory.

When you create an ODBC data source, you must also specify the driver that the ODBC driver manager sendsdatabase calls to.

The following table shows the recommended ODBC drivers to use with each database:

Database ODBC Driver Requires Database Client Software

IBM DB2 IBM ODBC driver Yes

Informix DataDirect 32-bit closed ODBC driver No

Microsoft Access Microsoft Access driver No


Database ODBC Driver Requires Database Client Software

Microsoft Excel Microsoft Excel driver No

Microsoft SQL Server Microsoft SQL Server ODBC driver No

Oracle DataDirect 32-bit closed ODBC driver No

Sybase ASE DataDirect 32-bit closed ODBC driver No

Teradata Teradata ODBC driver Yes

HP Neoview HP ODBC driver No

Netezza Netezza SQL No



JDBC ConnectivityJDBC (Java Database Connectivity) is a Java API that provides connectivity to relational databases. Java-basedapplications can use JDBC drivers to connect to databases.

The following services and clients use JDBC to connect to databases:

¨ Model Repository Service

¨ Informatica Developer

¨ Informatica Analyst

¨ Metadata Manager Service

¨ Reporting Service

¨ Custom Metadata Configurator

When you install the Informatica platform, the server and client installers install the JDBC drivers.

JDBC Connectivity 85

A P P E N D I X A

Connecting to Databases fromWindows

This appendix includes the following topics:

¨ Connecting to Databases from Windows Overview, 86

¨ Connecting to an IBM DB2 Universal Database, 86

¨ Connecting to Microsoft Access and Microsoft Excel, 87

¨ Connecting to a Microsoft SQL Server Database, 88

¨ Connecting to an Oracle Database, 89

¨ Connecting to a Sybase ASE Database, 90

¨ Connecting to a Teradata Database, 91

Connecting to Databases from Windows OverviewTo use native connectivity, you must install and configure the database client software for the database you wantto access. To ensure compatibility between the application service and the database, install a client software thatis compatible with the database version and use the appropriate database client libraries. To improveperformance, use native connectivity.

The Informatica installation includes DataDirect 6.0 ODBC drivers. If you have existing ODBC data sourcescreated 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 ODBCdrivers that are Level 2 compliant or higher.

RELATED TOPICS:¨ “Verify the Setup for 32-bit and 64-bit Platforms” on page 36

Connecting to an IBM DB2 Universal DatabaseFor native connectivity, install the version of IBM DB2 Client Application Enabler (CAE) appropriate for the IBMDB2 database server version. For ODBC connectivity, use the DataDirect 6.0 ODBC drivers installed withInformatica. To ensure compatibility between Informatica and databases, use the appropriate database clientlibraries.

86

Configuring Native ConnectivityUse the following procedure as a guideline to configure native connectivity. For specific connectivity instructions,see the database documentation.

To connect to an IBM DB2 database:

1. Verify that the following environment variable settings have been established by DB2 Client ApplicationEnabler:

DB2HOME=C:\SQLLIB (directory where the client is installed)DB2INSTANCE = DB2DB2CODEPAGE = 437 (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 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.

¨ Launch the Client Configuration Assistant.

¨ Add the database connection and BIND the connection.

4. Verify that you can connect to the DB2 database.

Run the following command in the DB2 Command Line Processor:CONNECT TO <dbalias> USER <username> USING <password>

If the connection is successful, disconnect and clean up with the TERMINATE command. If the connectionfails, see the database documentation.

Configuring ODBC ConnectivityUse the following procedure as a guideline to configure ODBC. For specific connectivity instructions, see thedatabase documentation.

To connect to an IBM DB2 database using ODBC:

1. Install the IBM DB2 Client Application Enabler (CAE) and configure native connectivity.

2. Create an ODBC data source using the driver provided by IBM. Do not use the DataDirect 32-bit closedODBC driver for DB2 provided by Informatica.

For specific instructions on creating an ODBC data source using the IBM DB2 ODBC driver, see the databasedocumentation.

3. Verify that you can connect to the DB2 database using the ODBC data source. If the connection fails, see thedatabase documentation.

Connecting to Microsoft Access and Microsoft ExcelConfigure connectivity to the following Informatica components on Windows:

¨ PowerCenter Integration Service. Install Microsoft Access or Excel on the machine where the PowerCenterIntegration Service processes run. Create an ODBC data source for the Microsoft Access or Excel data youwant to access.

¨ PowerCenter Client. Install Microsoft Access or Excel on the machine hosting the PowerCenter Client. Createan ODBC data source for the Microsoft Access or Excel data you want to access.

Connecting to Microsoft Access and Microsoft Excel 87

Configuring ODBC ConnectivityUse the following procedure as a guideline to configure connectivity. For specific connectivity instructions, see theMicrosoft Access or Excel documentation.

To connect to an 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 andPmNullPasswd for the password when you create a database connection in the Workflow Manager.

Connecting to a Microsoft SQL Server DatabaseFor native connectivity, install SQL Client, including the Microsoft OLE DB provider for Microsoft SQL Server.Verify that the version of of SQL Client is compatible with your Microsoft SQL Server version. For ODBCconnectivity, use the DataDirect 6.0 ODBC drivers installed with Informatica. To ensure compatibility betweenInformatica and databases, use the appropriate database client libraries.


To connect to a Microsoft SQL Server database:

1. Verify that the Microsoft SQL Server home directory is set.

2. Verify that the PATH environment variable includes the Microsoft SQL Server directory.

For example:PATH=C:\MSSQL\BIN;C:\MSSQL\BINN;....

3. Configure the Microsoft SQL Server client to connect to the database that you want to access.

Launch the Client Network Utility. On the General tab, verify that the Default Network Library matches thedefault network for the Microsoft SQL Server database.

4. Verify that you can connect to the Microsoft SQL Server database.

To connect to the database, launch ISQL_w, and enter the connectivity information. If you fail to connect tothe database, verify that you correctly entered all of the connectivity information.

Configuring ODBC ConnectivityUse the following procedure as a guideline to configure ODBC. For specific connectivity instructions, see theMicrosoft SQL Server documentation.

To connect to a Microsoft SQL Server database using ODBC:

1. Install the Microsoft SQL Server client and configure native connectivity.

2. Create an ODBC data source using the driver provided by Microsoft.

Do not use the DataDirect 32-bit closed ODBC driver for Microsoft SQL Server provided by Informatica.

To ensure consistent data in Microsoft SQL Server repositories, clear the Create temporary stored proceduresfor prepared SQL statements option in the Create a New Data Source to SQL Server dialog box.

88 Appendix A: Connecting to Databases from Windows

If you have difficulty clearing the temporary stored procedures for prepared SQL statements options, see theInformatica Knowledge Base for more information about configuring Microsoft SQL Server. Access theKnowledge Base at http://my.informatica.com.

3. Verify that you can connect to the Microsoft SQL Server database using the ODBC data source. If theconnection fails, see the database documentation.

Connecting to an Oracle DatabaseFor native connectivity, install the version of Oracle client appropriate for the Oracle database server version. ForODBC connectivity, use the DataDirect 6.0 ODBC drivers installed with Informatica. To ensure compatibilitybetween 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 thesame version of the Oracle client on all machines that require it. To verify compatibility, contact Oracle.

Note: If you use the DataDirect ODBC driver provided by Informatica, you do not need the database client. TheODBC wire protocols do not require the database client software to connect to the database.

Configuring Native ConnectivityUse the following procedure as a guideline to configure native connectivity using Oracle Net Services or Net8. Forspecific connectivity instructions, see the database documentation.

To connect to an Oracle database:

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 andmodify it.

The tnsnames.ora file is stored in the $ORACLE_HOME\network\admin directory.

Enter the correct syntax for the Oracle connect string, typically databasename .world. Make sure the SIDentered here matches the database server instance ID defined on the Oracle server.

Following is a sample tnsnames.ora. You need to 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)

Connecting to an Oracle Database 89

http://my.informatica.com

4. Set the NLS_LANG environment variable to the locale (language, territory, and character set) you want thedatabase 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. 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 connect tothe database, verify that you correctly entered all of the connectivity information.

Use the connect string as defined in tnsnames.ora.


To connect to an Oracle database using ODBC:

1. Create an ODBC data source using the DataDirect ODBC driver for Oracle provided by Informatica.

2. Verify that you can connect to the Oracle database using the ODBC data source.

Locale Environment VariableIf the PowerCenter Client does not accurately display non-ASCII characters, set the NLS_LANG environmentvariable to the locale you want the database client and server to use with the login. The locale includes language,territory, and character set.

The value of the NLS_LANG environment variable depends on the configuration. For example, if the value isamerican_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.

Connecting to a Sybase ASE DatabaseFor native connectivity, install the version of Open Client appropriate for your database version. For ODBCconnectivity, use the DataDirect 6.0 ODBC drivers installed with Informatica. To ensure compatibility betweenInformatica 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 thesame version of Open Client on the machines hosting the Sybase ASE database and Informatica. To verifycompatibility, contact Sybase.

If you want to create, restore, or upgrade a Sybase ASE repository, set allow nulls by default to TRUE at thedatabase level. Setting this option changes the default null type of the column to null in compliance with the SQLstandard.




To connect to a Sybase ASE database:

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 ASE directory.

For example:PATH=C:\SYBASE\BIN;C:\SYBASE\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%\INIdirectory) 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 portnumber, 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 thedatabase, verify that you correctly entered all of the connectivity information.

User names and database names are case sensitive.


To connect to a Sybase ASE database using ODBC:

1. Create an ODBC data source using the DataDirect 32-bit closed ODBC driver for Sybase provided byInformatica.

2. On the Performance tab, set Prepare Method to 2-Full. This ensures consistent data in the repository,optimizes performance, and reduces overhead on tempdb.

3. Verify that you can connect to the Sybase ASE database using the ODBC data source.

Connecting to a Teradata DatabaseInstall and configure native client software on the machines where the PowerCenter Integration Service processruns and where you install the PowerCenter Client. To ensure compatibility between the Informatica products anddatabases, use 32-bit database client libraries only. You must configure connectivity to the following Informaticacomponents on Windows:

¨ PowerCenter Integration Service and Data Integration Service. Install Teradata client, the Teradata ODBCdriver, and any other Teradata client software you might need on the machine where the Integration Serviceprocess runs. You must also configure ODBC connectivity.

Connecting to a Teradata Database 91

¨ PowerCenter Client. Install Teradata client, the Teradata ODBC driver, and any other Teradata client softwareyou might need on each PowerCenter Client machine accessing Teradata. Use the Workflow Manager tocreate a database connection object for the Teradata database.

Note: Based on a recommendation from Teradata, Informatica uses ODBC to connect to Teradata. ODBC is anative interface for Teradata. To process Teradata bigint data, use the Teradata ODBC driver version 03.06.00.02or later.

Configuring ODBC ConnectivityUse the following procedure as a guideline to configure connectivity. For specific connectivity instructions, see thedatabase documentation.

To connect 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 Services service with a Local System account logon. Createa User DSN if you select the This account log in option to start the Informatica Services 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 singleconnection 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 fieldsempty.

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 sessionmode, Teradata rolls back the transaction when it encounters a row error. In Teradata mode, the IntegrationService 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, orTeradata SQL Assistant.


A P P E N D I X B

Connecting to Databases from UNIXThis appendix includes the following topics:

¨ Connecting to Databases from UNIX Overview, 93

¨ Connecting to Microsoft SQL Server, 94

¨ Connecting to an IBM DB2 Universal Database, 94

¨ Connecting to an Informix Database, 96

¨ Connecting to an Oracle Database, 98

¨ Connecting to a Sybase ASE Database, 101

¨ Connecting to a Teradata Database, 103

¨ Connecting to an ODBC Data Source, 105

¨ Sample odbc.ini File, 108

Connecting to Databases from UNIX OverviewTo use native connectivity, you must install and configure the database client software for the database you wantto access. To ensure compatibility between the application service and the database, install a client software thatcompatible with the database version and use the appropriate database client libraries. To improve performance,use native connectivity.

The Informatica installation includes DataDirect 6.0 ODBC drivers. If you have existing ODBC data sourcescreated 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 ODBCdrivers that are Level 2 compliant or higher.

On Linux, use native drivers to connect to IBM DB2, Oracle, or Sybase ASE databases.You can connect to othersources and targets using ODBC. The Informix client is not available on Linux. Use ODBC to connect to Informixfrom Linux.

Note: You cannot use Teradata or Informix for a PowerCenter repository.

93


Connecting to Microsoft SQL ServerUse ODBC to connect to a Microsoft SQL Server database from a UNIX machine.

RELATED TOPICS:¨ “Connecting to an ODBC Data Source” on page 105

Connecting to an IBM DB2 Universal DatabaseFor native connectivity, install the version of IBM DB2 Client Application Enabler (CAE) appropriate for the IBMDB2 database server version. For ODBC connectivity, use the DataDirect 6.0 ODBC drivers installed withInformatica. To ensure compatibility between Informatica and databases, use the appropriate database clientlibraries.

Configuring Native ConnectivityUse the following procedure as a guideline to configure connectivity. For specific connectivity instructions, see thedatabase documentation.

To connect to a DB2 database:

1. To configure connectivity on the machine where the PowerCenter Integration Service or Repository Serviceprocess 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 holderfor 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.

Using a Bourne shell:$ 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 isinstalled in the /opt/IBMdb2/v6.1 directory:

94 Appendix B: Connecting to Databases from UNIX

Using a Bourne shell:$ DB2DIR=/opt/IBMdb2/v6.1; export DB2DIR

Using a C shell:$ setenv DB2DIR /opt/IBMdb2/v6.1

PATH. To run the IBM DB2 command line programs, set the variable to include the DB2 bin directory.

Using a Bourne shell:$ PATH=${PATH}:$DB2DIR/bin; export PATH

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 PowerCenterIntegration Service and Repository Service processes load dynamically. To locate the shared libraries duringrun time, set the shared library environment variable.

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 theshared library variables for each operating system:

Operating System Variable



AIX LIBPATH

HP-UX SHLIB_PATH

For example, use the following syntax for Solaris and 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 HP-UX:

¨ Using a Bourne shell:$ SHLIB_PATH=${SHLIB_PATH}:$HOME/server_dir:$DB2DIR/lib; export SHLIB_PATH

¨ Using a C shell:$ setenv SHLIB_PATH ${SHLIB_PATH}:$HOME/server_dir:$DB2DIR/lib

For AIX:

¨ Using a Bourne shell:$ LIBPATH=${LIBPATH}:$HOME/server_dir:$DB2DIR/lib; export LIBPATH

¨ Using a C shell:$ 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 andlog in again or run the source command.

Connecting to an IBM DB2 Universal Database 95

Using a Bourne shell:$ source .profile

Using a C shell:$ source .cshrc

5. If the DB2 database resides on the same machine on which PowerCenter Integration Service or RepositoryService processes run, 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 thiscommand lists an entry for “Directory entry type” of “Remote,” skip to step 6.

If the database is not configured as remote, run the following command to verify whether a TCP/IP node iscataloged for the host:

DB2 LIST NODE DIRECTORYIf the node name is empty, you can create one when you set up a remote database. Use the followingcommand 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.

6. Verify that you can connect to the DB2 database. Run the DB2 Command Line Processor and run thecommand:

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 DatabaseFor native connectivity, install ESQL for C, Informix Client SDK, or any other Informix client software. Also, installcompatible versions of ESQL/runtime or iconnect. For ODBC connectivity, use the DataDirect 6.0 ODBC driversinstalled with Informatica. To ensure compatibility between Informatica and databases, use the appropriatedatabase client libraries.

You must install the ESQL/C version that is compatible with the Informix database server. To verify compatibility,contact Informix.


Configuring Native ConnectivityUse the following procedure as a guideline to configure connectivity. For specific connectivity instructions, see thedatabase documentation.

To connect to an Informix database:

1. To configure connectivity for the Integration Service process, log in to the machine as a user who can startthe server process.

2. Set the INFORMIXDIR, INFORMIXSERVER, DBMONEY, and PATH environment variables.


INFORMIXDIR. Set the variable to the directory where the database client is installed. For example, if theclient is installed in the /databases/informix directory:

Using a Bourne shell:$ INFORMIXDIR=/databases/informix; export INFORMIXDIR

Using a C shell:$ setenv INFORMIXDIR /databases/informix

INFORMIXSERVER. Set the variable to the name of the server. For example, if the name of the Informixserver is INFSERVER:

Using a Bourne shell:$ INFORMIXSERVER=INFSERVER; export INFORMIXSERVER

Using a C shell:$ setenv INFORMIXSERVER INFSERVER

DBMONEY. Set the variable so Informix does not prefix the data with the dollar sign ($) for money datatypes.

Using a Bourne shell:$ DBMONEY=' .'; export DBMONEY

Using a C shell:$ setenv DBMONEY=' .'

PATH. To run the Informix command line programs, set the variable to include the Informix bin directory.

Using a Bourne shell:$ PATH=${PATH}:$INFORMIXDIR/bin; export PATH

Using a C shell:$ setenv PATH ${PATH}:$INFORMIXDIR/bin

3. Set the shared library path to include the Informix lib directory.

The Informix client software contains a number of shared library components that the Integration Serviceprocess loads dynamically. To locate the shared libraries during run time, set the shared library environmentvariable.






AIX LIBPATH

HP-UX SHLIB_PATH

For example, use the following syntax for Solaris:

¨ Using a Bourne shell:$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/server_dir:$INFORMIXDIR/lib: $INFORMIXDIR/lib/esql; export LD_LIBRARY_PATH

Connecting to an Informix Database 97

¨ Using a C shell:$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/server_dir:$INFORMIXDIR/lib:$INFORMIXDIR/lib/esql

For HP-UX:

¨ Using a Bourne shell:$ SHLIB_PATH=${SHLIB_PATH}:$HOME/server_dir:$INFORMIXDIR/lib:$INFORMIXDIR/lib/esql; export SHLIB_PATH

¨ Using a C shell:$ setenv SHLIB_PATH ${SHLIB_PATH}:$HOME/server_dir:$INFORMIXDIR/lib:$INFORMIXDIR/lib/esql

For AIX:

¨ Using a Bourne shell:$ LIBPATH=${LIBPATH}:$HOME/server_dir:$INFORMIXDIR/lib:$INFORMIXDIR/lib/esql; export LIBPATH

¨ Using a C shell:$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$INFORMIXDIR/lib:$INFORMIXDIR/lib/esql

4. Optionally, set the $ONCONFIG environment variable to the Informix configuration file name.

5. If you plan to call Informix stored procedures in mappings, set all of the date parameters to the Informixdatatype Datetime year to fraction(5).

6. Make sure the DBDATE environment variable is not set.

For example, to check if DBDATE is set, you might enter the following at a UNIX prompt:$ env | grep -i DBDATE

If DBDATE=MDY2/ appears, unset DBDATE by typing:$ unsetenv DBDATE

7. Edit the .cshrc or .profile to include the complete set of shell commands. Save the file and either log out andlog in again, or run the source command.



8. Verify that the Informix server name is defined in the $INFORMIXDIR/etc/sqlhosts file.

9. Verify that the Service (last column entry for the server named in the sqlhosts file) is defined in the servicesfile (usually /etc/services).

If not, define the Informix Services name in the Services file.

Enter the Services name and port number. The default port number is 1525, which should work in most cases.

For more information, see the Informix and UNIX documentation.

10. Verify that you can connect to the Informix database.

If you fail to connect to the database, verify that you have correctly entered all the information.

Connecting to an Oracle DatabaseFor native connectivity, install the version of Oracle client appropriate for the Oracle database server version. ForODBC connectivity, use the DataDirect 6.0 ODBC drivers installed with Informatica. To ensure compatibilitybetween 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 thesame version of the Oracle client on all machines that require it. To verify compatibility, contact Oracle.

Configuring Native ConnectivityUse the following procedure as a guideline to connect to an Oracle database through Oracle Net Services or Net8.For specific connectivity instructions, see the database documentation.

To connect to an Oracle database:

1. To configure connectivity for the PowerCenter Integration Service or Repository Service process, log in to themachine 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 isinstalled in the /HOME2/oracle directory:

Using a Bourne shell:$ ORACLE_HOME=/HOME2/oracle; export ORACLE_HOME

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 databaseclient and server to use with the login. The value of this variable depends on the configuration. For example, ifthe value is american_america.UTF8, you must set the variable as follows:

Using a Bourne shell:$ 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.

TNS_ADMIN. Set the variable to the directory where the tnsnames.ora file resides. For example, if the file isin the /HOME2/oracle/network/admin directory:

Using a Bourne shell:$ TNS_ADMIN=$HOME2/oracle/network/admin; export TNS_ADMIN

Using a C shell:$ setenv TNS_ADMIN=$HOME2/oracle/network/admin

Setting the TNS_ADMIN is optional, and might vary depending on the configuration.

PATH. To run the Oracle command line programs, set the variable to include the Oracle bin directory.

Using a Bourne shell:$ PATH=${PATH}:$ORACLE_HOME/bin; export PATH

Using a C shell:$ setenv PATH ${PATH}:ORACLE_HOME/bin

3. Set the shared library environment variable.

The Oracle client software contains a number of shared library components that the PowerCenter IntegrationService and Repository Service processes load dynamically. To locate the shared libraries during run time,set the shared library environment variable.


Connecting to an Oracle Database 99





AIX LIBPATH

HP-UX SHLIB_PATH


¨ Using a Bourne shell:$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/server_dir:$ORACLE_HOME/lib; export LD_LIBRARY_PATH

¨ Using a C shell:$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/server_dir:$ORACLE_HOME/lib

For HP-UX

¨ Using a Bourne shell:$ SHLIB_PATH=${SHLIB_PATH}:$HOME/server_dir:$ORACLE_HOME/lib; export SHLIB_PATH

¨ Using a C shell:$ setenv SHLIB_PATH ${SHLIB_PATH}:$HOME/server_dir:$ORACLE_HOME/lib

For AIX

¨ Using a Bourne shell:$ LIBPATH=${LIBPATH}:$HOME/server_dir:$ORACLE_HOME/lib; export LIBPATH

¨ Using a C shell:$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$ORACLE_HOME/lib




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 andmodify it.

The tnsnames.ora file is stored in the $ORACLE_HOME/network/admin directory.

Enter the correct syntax for the Oracle connect string, typically databasename .world.

Here is a sample tnsnames.ora. You need to 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 toconnect to the database, verify that you correctly entered all of the connectivity information.

Enter the user name and connect string as defined in tnsnames.ora.

Connecting to a Sybase ASE DatabaseFor native connectivity, install the version of Open Client appropriate for your database version. For ODBCconnectivity, use the DataDirect 6.0 ODBC drivers installed with Informatica. To ensure compatibility betweenInformatica 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 thesame version of Open Client on the machines hosting the Sybase ASE database and Informatica. To verifycompatibility, contact Sybase.

If you want to create, restore, or upgrade a Sybase ASE repository, set allow nulls by default to TRUE at thedatabase level. Setting this option changes the default null type of the column to null in compliance with the SQLstandard.


Configuring Native ConnectivityUse the following procedure as a guideline to connect to a Sybase ASE database. For specific connectivityinstructions, see the database documentation.

To connect to a Sybase ASE database:

1. To configure connectivity to the Integration Service or Repository Service, log in to the machine as a user whocan 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 isinstalled in the /usr/sybase directory:

Using a Bourne shell:$ 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 bin directory.

Using a Bourne shell:$ PATH=${PATH}:/usr/sybase/bin; export PATH

Using a C shell:$ setenv PATH ${PATH}:/usr/sybase/bin


Connecting to a Sybase ASE Database 101

The Sybase Open Client software contains a number of shared library components that the PowerCenterIntegration Service and the Repository Service processes load dynamically. To locate the shared librariesduring run time, set the shared library environment variable.

The shared library path must also include the Informatica Services installation directory (server_dir) .

Set the shared library environment variable based on the operating system. The following table describes theshared library variables for each operating system.




AIX LIBPATH

HP-UX SHLIB_PATH


¨ Using a Bourne shell:$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/server_dir:$SYBASE/lib; export LD_LIBRARY_PATH

¨ Using a C shell:$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/server_dir:$SYBASE/lib

For HP-UX

¨ Using a Bourne shell:$ SHLIB_PATH=${SHLIB_PATH}:$HOME/server_dir:$SYBASE/lib; export SHLIB_PATH

¨ Using a C shell:$ setenv SHLIB_PATH ${SHLIB_PATH}:$HOME/server_dir:$SYBASE/lib

For AIX

¨ Using a Bourne shell:$ LIBPATH=${LIBPATH}:$HOME/server_dir:$SYBASE/lib; export LIBPATH

¨ Using a C shell:$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$SYBASE/lib




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 toconnect 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 DatabaseInstall and configure native client software on the machines where PowerCenter Integration Service or DataIntegration Service processes run. To ensure compatibility between Informatica and databases, use theappropriate database client libraries.

Install the Teradata BTEQ client software, the Teradata ODBC driver, and any other Teradata client software youneed on the machine where the Integration Service process runs.

Note: Based on recommendation from Teradata, Informatica uses ODBC to connect to Teradata. ODBC is anative interface for Teradata. To process Teradata bigint data, use the Teradata ODBC driver version 03.06.00.02or later. Teradata does not have an ODBC driver for Linux.

Configuring ODBC ConnectivityUse the following procedure as a guideline to configure connectivity. For specific connectivity instructions, see thedatabase documentation.

To connect to a Teradata database on UNIX:

1. To configure connectivity for the PowerCenter Integration Service process, log in to the machine as a userwho 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:

Using a Bourne shell:$ TERADATA_HOME=/teradata/usr; export TERADATA_HOME

Using a C shell:$ setenv TERADATA_HOME /teradata/usr

ODBCHOME. Set the variable to the ODBC installation directory. For example:

Using a Bourne shell:$ ODBCHOME=/usr/odbc; export ODBCHOME

Using a C shell:$ setenv ODBCHOME /usr/odbc

PATH. To run the ivtestlib utility, to verify that the UNIX ODBC manager can load the driver files, set thevariable as follows:

Using a Bourne shell:PATH="${PATH}:$ODBCHOME/bin:$TERADATA_HOME/bin"

Using a C shell:$ setenv PATH ${PATH}:$ODBCHOME/bin:$TERADATA_HOME/bin


The Teradata software contains a number of shared library components that the PowerCenter IntegrationService process loads dynamically. To locate the shared libraries during run time, set the shared libraryenvironment variable.

The shared library path must also include the Informatica Services installation directory (server_dir) .

Connecting to a Teradata Database 103





AIX LIBPATH

HP-UX SHLIB_PATH

For example, use the following syntax for Solaris:

¨ Using a Bourne shell:$ LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:$HOME/server_dir:$ODBCHOME/lib:

$TERADATA_HOME/lib:$TERADATA_HOME/odbc/lib";

export LD_LIBRARY_PATH¨ Using a C shell:

$ setenv LD_LIBRARY_PATH "${LD_LIBRARY_PATH}:$HOME/server_dir:$ODBCHOME/lib:$TERADATA_HOME/lib:

$TERADATA_HOME/odbc/lib"For HP-UX

¨ Using a Bourne shell:$ SHLIB_PATH=${SHLIB_PATH}:$HOME/server_dir:$ODBCHOME/lib; export SHLIB_PATH

¨ Using a C shell:$ setenv SHLIB_PATH ${SHLIB_PATH}:$HOME/server_dir:$ODBCHOME/lib

For AIX

¨ Using a Bourne shell:$ LIBPATH=${LIBPATH}:$HOME/server_dir:$ODBCHOME/lib; export LIBPATH

¨ Using a C shell:$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$ODBCHOME/lib

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.$ cp $ODBCHOME/odbc.ini $HOME/.odbc.ini

Add an entry for the Teradata data source under the section [ODBC Data Sources] and configure the datasource.

For example:MY_TERADATA_SOURCE=Teradata Driver[MY_TERADATA_SOURCE]Driver=/u01/app/teradata/td-tuf611/odbc/drivers/tdata.soDescription=NCR 3600 running Teradata V1R5.2DBCName=208.199.59.208DateTimeFormat=AAASessionMode=ANSIDefaultDatabase=Username=Password=

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 thetransaction when it encounters a row error.

If you choose Teradata session mode, Teradata rolls back the transaction when it encounters a row error. InTeradata mode, the Integration Service process cannot detect the rollback, and does not report this in thesession log.

7. To configure connection to a single Teradata database, enter the DefaultDatabase name. To create a singleconnection 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=/usr/odbc

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.



11. For each data source you use, make a note of the file name under the Driver=<parameter> in the data sourceentry in odbc.ini. Use the ivtestlib utility to verify that the UNIX ODBC 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:ivtestlib /u01/app/teradata/td-tuf611/odbc/drivers/tdata.so

12. Test the connection using BTEQ or another Teradata client tool.

RELATED TOPICS:¨ “Sample odbc.ini File” on page 108

Connecting to an ODBC Data SourceInstall and configure native client software on the machines where PowerCenter Integration Service andRepository Service and the Data Integration Service processes run. To ensure compatibility between Informaticaand databases, use the appropriate database client libraries.

To connect a PowerCenter Integration Service or Data Integration Service process to each ODBC database, youmust install and configure any underlying client access software needed by the ODBC driver. To access sources ina Windows environment, such as Microsoft Excel or Access, you must install PowerChannel.

The Informatica installation includes DataDirect 6.0 ODBC drivers. If odbc.ini references an earlier version, editodbc.ini to update your existing connections to use the new drivers. Use the System DSN to specify an ODBCdata source.

To connect to an ODBC data source:

1. To configure connectivity for the PowerCenter Integration Service process, log in to the machine as a userwho can start a service process.

Connecting to an ODBC Data Source 105

2. Set the ODBCHOME and PATH environment variables.

ODBCHOME. Set to the DataDirect ODBC installation directory. For example, if the install directory is /opt/ODBC5.2.

Using a Bourne shell:$ ODBCHOME=/opt/ODBC5.2; export ODBCHOME

Using a C shell:$ setenv ODBCHOME /opt/ODBC5.2

PATH. To run the ODBC command line programs, like ivtestlib, set the variable to include the odbc bindirectory.

Using a Bourne shell:$ PATH=${PATH}:$ODBCHOME/bin; export PATH

Using a C shell:$ setenv PATH ${PATH}:$ODBCHOME/bin

Run the ivtestlib utility to verify that the UNIX ODBC manager can load the driver files.


The ODBC software contains a number of shared library components that the service processes loaddynamically. To locate the shared libraries during run time, set the shared library environment variable.






AIX LIBPATH

HP-UX SHLIB_PATH


¨ Using a Bourne shell:$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/server_dir:$ODBCHOME/lib; export LD_LIBRARY_PATH

¨ Using a C shell:$ setenv LD_LIBRARY_PATH $HOME/server_dir:$ODBCHOME:${LD_LIBRARY_PATH}

For HP-UX

¨ Using a Bourne shell:$ SHLIB_PATH=${SHLIB_PATH}:$HOME/server_dir:$ODBCHOME/lib; export SHLIB_PATH

¨ Using a C shell:$ setenv SHLIB_PATH ${SHLIB_PATH}:$HOME/server_dir:$ODBCHOME/lib

For AIX

¨ Using a Bourne shell:$ LIBPATH=${LIBPATH}:$HOME/server_dir:$ODBCHOME/lib; export LIBPATH


¨ Using a C shell:$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$ODBCHOME/lib

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.$ cp $ODBCHOME/odbc.ini $HOME/.odbc.ini

Add an entry for the ODBC data source under the section [ODBC Data Sources] and configure the datasource.

For example:MY_MSSQLSERVER_ODBC_SOURCE=<Driver name or Data source description>[MY_SQLSERVER_ODBC_SOURCE]Driver=<path to ODBC drivers>Description=DataDirect 5.2 SQL Server Wire ProtocolDatabase=<SQLServer_database_name>LogonID=<username>Password=<password>Address=<TCP/IP address>,<port number>QuoteId=NoAnsiNPW=NoApplicationsUsingThreads=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=/usr/odbc

6. If you use the odbc.ini file in the home directory, set the ODBCINI environment variable.

Using a Bourne shell:$ ODBCINI=/$HOME/.odbc.ini; export ODBCINI

Using a C shell:$ setenv ODBCINI $HOME/.odbc.ini




8. Use the ivtestlib utility to verify that the UNIX ODBC manager can load the driver file you specified for thedata source in the odbc.ini file.

For example, if you have the driver entry:Driver = /opt/odbc/lib/DWxxxx.so

run the following command:ivtestlib /opt/odbc/lib/DWxxxx.so

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 arenot. For example, if you want to use an ODBC driver to access Oracle, you must install the Oracle SQL*NETsoftware and set the appropriate environment variables. Verify such additional software configurationseparately before using ODBC.

Connecting to an ODBC Data Source 107


Sample odbc.ini File[ODBC Data Sources]DB2 Wire Protocol=DataDirect 5.2 DB2 Wire ProtocolInformix Wire Protocol=DataDirect 5.2 Informix Wire ProtocolOracle Wire Protocol=DataDirect 5.2 Oracle Wire ProtocolOracle=DataDirect 5.2 OracleSQLServer Wire Protocol=DataDirect 5.2 SQL Server Wire ProtocolSybase Wire Protocol=DataDirect 5.2 Sybase Wire Protocol

[DB2 Wire Protocol]Driver=/home/ksuthan/odbc/52/solaris32/installed/lib/dddb222.soDescription=DataDirect 5.2 DB2 Wire ProtocolAddStringToCreateTable=AlternateID=AlternateServers=ApplicationUsingThreads=1CatalogSchema=CharsetFor65535=0#Collection applies to OS/390 and AS/400 onlyCollection=ConnectionRetryCount=0ConnectionRetryDelay=3#Database applies to DB2 UDB onlyDatabase=<database_name>DynamicSections=200GrantAuthid=PUBLICGrantExecute=1IpAddress=<DB2_server_host>LoadBalancing=0#Location applies to OS/390 and AS/400 onlyLocation=<location_name>LogonID=Password=PackageOwner=ReportCodePageConversionErrors=0SecurityMechanism=0TcpPort=<DB2_server_port>UseCurrentSchema=1WithHold=1

[Informix Wire Protocol]Driver=/home/ksuthan/odbc/52/solaris32/installed/lib/ddifcl22.soDescription=DataDirect 5.2 Informix Wire ProtocolAlternateServers=ApplicationUsingThreads=1CancelDetectInterval=0ConnectionRetryCount=0ConnectionRetryDelay=3Database=<database_name>HostName=<Informix_host>LoadBalancing=0LogonID=Password=PortNumber=<Informix_server_port>ReportCodePageConversionErrors=0ServerName=<Informix_server>TrimBlankFromIndexName=1

[Test]Driver=/home/ksuthan/odbc/52/solaris32/installed/lib/ddora22.soDescription=DataDirect 5.2 Oracle Wire ProtocolAlternateServers=ApplicationUsingThreads=1ArraySize=60000


CachedCursorLimit=32CachedDescLimit=0CatalogIncludesSynonyms=1CatalogOptions=0ConnectionRetryCount=0ConnectionRetryDelay=3DefaultLongDataBuffLen=1024DescribeAtPrepare=0EnableDescribeParam=0EnableNcharSupport=0EnableScrollableCursors=1EnableStaticCursorsForLongData=0EnableTimestampWithTimeZone=0HostName=herculesLoadBalancing=0LocalTimeZoneOffset=LockTimeOut=-1LogonID=ksuthanPassword=an3d45jkPortNumber=1531ProcedureRetResults=0ReportCodePageConversionErrors=0ServiceType=0ServiceName=SID=SUN10GTimeEscapeMapping=0UseCurrentSchema=1

[Oracle]Driver=/home/ksuthan/odbc/52/solaris32/installed/lib/ddor822.soDescription=DataDirect 5.2 OracleAlternateServers=ApplicationUsingThreads=1ArraySize=60000CatalogIncludesSynonyms=1CatalogOptions=0ClientVersion=9iR2 ConnectionRetryCount=0ConnectionRetryDelay=3DefaultLongDataBuffLen=1024DescribeAtPrepare=0EnableDescribeParam=0EnableNcharSupport=0EnableScrollableCursors=1EnableStaticCursorsForLongData=0EnableTimestampWithTimeZone=0LoadBalancing=0LocalTimeZoneOffset=LockTimeOut=-1LogonID=OptimizeLongPerformance=0Password=ProcedureRetResults=0ReportCodePageConversionErrors=0ServerName=<Oracle_server>TimestampEscapeMapping=0UseCurrentSchema=1

[SQLServer Wire Protocol]Driver=/home/ksuthan/odbc/52/solaris32/installed/lib/ddmsss22.soDescription=DataDirect 5.2 SQL Server Wire ProtocolAddress=<SQLServer_host, SQLServer_server_port>AlternateServers=AnsiNPW=YesConnectionRetryCount=0ConnectionRetryDelay=3Database=<database_name>LoadBalancing=0LogonID=Password=QuotedId=NoReportCodePageConversionErrors=0

[Sybase Wire Protocol]Driver=/home/ksuthan/odbc/52/solaris32/installed/lib/ddase22.soDescription=DataDirect 5.2 Sybase Wire Protocol

Sample odbc.ini File 109

AlternateServers=ApplicationName=ApplicationUsingThreads=1ArraySize=50Charset=ConnectionRetryCount=0ConnectionRetryDelay=3CursorCacheSize=1Database=<database_name>DefaultLongDataBuffLen=1024EnableDescribeParam=0EnableQuotedIdentifiers=0InitializationString=Language=LoadBalancing=0LogonID=NetworkAddress=<Sybase_host, Sybase_server_port>OptimizePrepare=1PacketSize=0Password=RaiseErrorPositionBehavior=0ReportCodePageConversionErrors=0SelectMethod=0TruncateTimeTypeFractions=0WorkStationID=

[ODBC]IANAAppCodePage=4InstallDir=/home/ksuthan/odbc/52/solaris32/installedTrace=0TraceDll=/home/ksuthan/odbc/52/solaris32/installed/lib/odbctrac.soTraceFile=odbctrace.outUseCursorLib=0


A P P E N D I X C

LANG Environment Variable forLinux

This appendix includes the following topic:

¨ LANG Environment Variable, 111

LANG Environment VariableWhen you set up the locale on a Linux machine, you can specify one of many values for the locale in the LANGenvironment variable. Informatica accepts a subset of all possible values that Linux accepts. If you installInformatica on a Linux machine, use one of the valid values for the LANG environment variable.

The following table provides a list of values that Informatica accepts for the LANG environment variable:

Language Territory/Region Locale

Basque Spain eu_ES

CanadianFrench French-Canada fr_CA

Catalan Catalonia ca_ES

Croatian Croatia croatian

Croatian Croatia hr_HR

Czech Czech Republic czech

Czech Czech Republic cs_CZ

Danish Denmark da_DK

Danish Denmark da_DK.iso885915

Danish Denmark danish

Danish Denmark dansk

Dutch Dutch-Belgium nl_BE.iso885915

111


Dutch Dutch-Belgium nl_BE

Dutch Netherlands dutch

Dutch Netherlands nl_NL

Dutch Netherlands nl_NL.iso885915

English Australia en_AU

English Canada en_CA

English Denmark en_DK

English Ireland en_IE

English United Kingdom en_GB

English United Kingdom en_GB.iso885915

English United States C

English United States en_US

English United States en_US.utf8

English United States POSIX

English United States en_US.iso88591

Estonian Estonia et_EE

Faroese Faroes fo_FO

Finnish Finland fi_FI

Finnish Finland fi_FI.iso885915

Finnish Finland finnish

French France fr_FR

French France fr_FR.iso885915

French France french

French French-Belgium fr_BE

French French-Belgium fr_BE.iso885915

French French-Switzerland fr_CH

French Luxembourg fr_LU

112 Appendix C: LANG Environment Variable for Linux


German Austria de_AT

German Austria de_AT.iso885915

German German-Switzerland de_CH

German Germany de_DE

German Germany deutsch

German Germany german

German Luxembourg de_LU

Greek Greece el_GR

Greek Greece el_GR.iso88597

Greek Greece greek

Hebrew Israel hebrew

Hebrew Israel iw_IL

Hungarian Hungary hu_HU

Hungarian Hungary hungarian

Icelandic Iceland icelandic

Icelandic Iceland is_IS

Indonesian Indonesia id_ID

Irish Ireland ga_IE

Italian Italian-Switzerland it_CH

Italian Italy it_IT

Italian Italy it_IT.iso885915

Italian Italy it_IT.utf8

Italian Italy italian

Japanese Japan ja_JP.eucjp

Japanese Japan ja_JP.sjis

Japanese Japan ja_JP.utf8

Korean Korea ko_KR

LANG Environment Variable 113


Korean Korea ko_KR.euckr

Latvian Latvia lv_LV

Lithuanian Lithuania lt_LT

Macedonian Macedonia mk_MK

Norwegian Norway no_NO

Norwegian Norway norwegian

Norwegian Norway nynorsk

Polish Poland pl_PL

Polish Poland polish

Portuguese Brazil pt_BR

Portuguese Portugal portuguese

Portuguese Portugal pt_PT

Portuguese Portugal pt_PT.iso885915

Romanian Romania ro_RO

Romanian Romania romanian

Russian Russia ru_RU

Russian Russia ru_RU.koi8r

Russian Ukraine ru_UA

Serbian Yugoslavia sr

Serbian Yugoslavia sr_YU

Simplified Chinese China zh_CN.gbk

Simplified Chinese China zh_CN

Slovak Slovakia sk_SK

Slovak Slovakia slovak

Slovenian Slovenia slovene

Slovenian Slovenia slovenian

Slovenian Slovenia sl_SI

114 Appendix C: LANG Environment Variable for Linux


Spanish Dominican Republic es_DO

Spanish El Salvador es_SV

Spanish Guatemala es_GT

Spanish Honduras es_HN

Spanish Mexico es_MX

Spanish Panama es_PA

Spanish Peru es_PE

Spanish Spain spanish

Spanish Spain es_ES.iso885915

Spanish Spain es_ES.utf8

Spanish Spain es_ES

Swedish Finland sv_FI

Swedish Sweden sv_SE

Swedish Sweden sv_SE.iso885915

Swedish Sweden swedish

TraditionalChinese Taiwan zh_TW.big5

Ukrainian Ukraine uk_UA

LANG Environment Variable 115

I N D E X

AActiveX

Microsoft Internet Explorer 33AddLicense (infacmd)

troubleshooting 62AIX

configuring JRE path 32configuring X Virtual Frame Buffer (Xvfb) 32Java components 32LIBPATH 32

Ccatalina.out

troubleshooting installation 60CLASSPATH

updating 65COBOL

connectivity 81code page compatibility

locale 37services 37

code pageslanguages on PowerCenter Client 34

Complex Data transformationprerequisites 39

connect stringexamples 83syntax 83

connectingIntegration Service to IBM DB2 (Windows) 86, 94Integration Service to Informix (Windows) 96Integration Service to Microsoft Access 87Integration Service to Microsoft SQL Server 88Integration Service to ODBC data sources (UNIX) 105Integration Service to Oracle (UNIX) 98Integration Service to Oracle (Windows) 89Integration Service to Sybase ASE (Windows) 90, 101Integration Service to Teradata (Windows) 91Microsoft Excel to Integration Service 87PowerCenter Client to Informix 91to UNIX databases 93to Windows databases 86

connecting to databasesJDBC 82

connection objectsconnectivity 77

connection stringsnative connectivity 83

connectivityCOBOL 81connect string examples 83Data Analyzer 82Data Integration Service 77

diagram of 76Informatica Analyst 77Informatica Developer 77Integration Service 81Metadata Manager 82Model Repository Service 77overview 76PowerCenter Client 82PowerCenter Repository Service 80

console modeuninstallation 75

DData Analyzer

connectivity 82JDBC-ODBC bridge 82ODBC (Open Database Connectivity) 76

Data Analyzer repositoryoptimizing for Oracle 44

Data Integration Serviceconnectivity 77

Data Maskingregistering the plug-in 57

Data Profiling warehousecreating 55user account privileges 43

database clientconfiguring 35, 38environment variables 35, 38install for Informatica client tools 35

database driversIntegration Service 76Repository Service 76

database requirementsinstallation requirements 7

databasesconnecting to (UNIX) 93connecting to (Windows) 86connecting to IBM DB2 86, 94connecting to Informix 96connecting to Microsoft Access 87connecting to Microsoft SQL Server 88connecting to Oracle 89, 98connecting to Sybase ASE 90, 101connecting to Teradata (UNIX) 103connecting to Teradata (Windows) 91heap size for IBM DB2 45password 43privileges for Data Analyzer repositories 43privileges for Data Profiling warehouse 43privileges for Metadata Manager repositories 43storage parameters for Oracle 44tablespace name for IBM DB2 44temporary tablespace for IBM DB2 45

116

testing connections 35, 38DataDirect ODBC drivers

platform-specific drivers required 84dbs2 connect

testing database connection 35, 38debug log

description 59disk space requirements

installation requirements 8documentation

installing 71viewing 72

Domain Activity Reportingsetting up on UNIX 32

domain configuration databaseinstallation requirements 9requirements 7troubleshooting 61uninstalling 73

Eenvironment variables

configuring for installation 12configuring for PowerCenter 29database client 35, 38DISPLAY 13Java components 32JRE_HOME 13LANG 13, 30LANG_C 13, 30LC_ALL 13, 30LC_CTYPE 13, 30library path 30local 13locale 30temporary disk space 12UNIX 29UNIX database client 35, 38

Fflat files

connectivity 81

Ggraphical mode

installation requirements 13uninstallation 75

HHP-UX

configuring JRE path 32configuring X Virtual Frame Buffer (Xvfb) 32Java components 32SHLIB_PATH 32

HTTPSinstallation requirements 14

IIBM DB2

connect string syntax 83connecting to Integration Service (Windows) 86, 94optimizing repositories 44, 45setting DB2CODEPAGE 87setting DB2INSTANCE 87single-node tablespace 44

infacmdnodes, adding to domains 61pinging objects 62troubleshooting 59

infasetupdomains, defining 61troubleshooting 59worker nodes, defining 61

Informatica Administratorlogging in 50

Informatica Analystconnectivity 77

Informatica Data Qualityconnectivity 77

Informatica Data Servicesconnectivity 77

Informatica Developerconnectivity 77installing languages 34

Informatica domaindescription 2, 3

Informatica JDBC driverinstalling 64

Informatica ODBC driverconfiguring 65installing on UNIX 66installing on Windows 65

Informatica Servicesconfiguring 53starting and stopping on UNIX 48troubleshooting 61

Informixconnect string syntax 83connecting to Integration Service (Windows) 96connecting to PowerCenter Client 91

installation logdescription 59

installation requirementsdatabase requirements 7disk space 8domain configuration database 9keystore file 14Mapping Architect for Visio 14minimum system requirements 6system user account 9temporary disk space 12third-party software 14X Window Server 13

installingPowerCenter documentation 71

Integration Serviceconnectivity 81database client 37ODBC (Open Database Connectivity) 76

isqltesting database connection 35, 38

Index 117

JJava components

AIX 32HP-UX 32

Java transformationconfiguring JRE path 32

Javascriptconfiguring in Firefox 33

JDBC (Java Database Connectivity)overview 85

JDBC client connectionsinstalling the driver 64updating the CLASSPATH 65

JDBC driversData Analyzer 76Data Analyzer connection to repository 82installed drivers 82Metadata Manager 76Metadata Manager connection to databases 82PowerCenter domain 76Reference Table Manager 76

JDBC-ODBC bridgeData Analyzer 82

JRE_HOMEenvironment variables 13

Kkeystore file

installation requirements 14

LLANG

environment variable 13, 30environment variable on Linux 111

languagesinstalling on PowerCenter Client 34installing on Windows 34

LC_ALLenvironment variable 13, 30

LC_CTYPEenvironment variable 13, 30

LD_LIBRARY_PATHlibrary paths 40updating 66

LIBPATHAIX 32library paths 40

library pathsLD_LIBRARY_PATH 40LIBPATH 40SHLIB_PATH 40

license keyverifying 9

licensesadding 62

Linuxconfiguring X Virtual Frame Buffer (Xvfb) 32database client environment variables 35, 38LANG environment variable 111library paths 30

localeconfiguring 13

locale environment variablesconfiguring 30

log filescatalina.out 60debug log 59installation 58installation log 59node.log 60summary log 59types 58

MMapping Architect for Visio

description 14installation prerequisites 14installation requirements 14

Metadata Managerconnectivity 82ODBC (Open Database Connectivity) 76

Metadata Manager Clienttroubleshooting 62

Metadata Manager repositoryoptimizing for IBM DB2 45optimizing for Oracle 44

Microsoft Accessconnecting to Integration Service 87

Microsoft Excelconnecting to Integration Service 87using PmNullPasswd 88using PmNullUser 88

Microsoft SQL Serverconfiguring Data Analyzer repository database 46connect string syntax 83connecting from UNIX 94connecting to Integration Service 88

Model Repository Serviceconnectivity 77

Mozilla Firefoxconfiguring 33

Nnode.log

troubleshooting installation 60nodes

TCP/IP network protocol 76troubleshooting 61

OODBC (Open Database Connectivity)

DataDirect driver issues 84establishing connectivity 84Integration Service 76Metadata Manager 76overview 84PowerCenter Client 76requirement for PowerCenter Client 82

ODBC client connections on UNIXinstalling the driver 66updating odbc.ini 67updating the shared library 66

ODBC client connections on Windowsconfiguring the driver 65

118 Index

installing the driver 65updating the system path 65

ODBC data sourcesconnecting to (UNIX) 105connecting to (Windows) 86

odbc.iniupdating 67

odbc.ini filesample 108

optimizingIBM DB2 repositories 44, 45Oracle repositories 44

Oracleconnect string syntax 83connecting to Integration Service (UNIX) 98connecting to Integration Service (Windows) 89optimizing repositories 44

Oracle Net Servicesusing to connect Integration Service to Oracle (UNIX) 98using to connect Integration Service to Oracle (Windows) 89

Ppassword

repository database 43PATH environment variable

updating 65Ping (infacmd)

troubleshooting 62plug-ins

registering Data Masking 57PmNullPasswd

reserved word 81PmNullUser

reserved word 81pmrep

troubleshooting 59pop-up blocker

avoiding in Data Analyzer 33PowerCenter

after you configure 55connectivity 76

PowerCenter Advanced Editionuninstalling 73

PowerCenter Clientconnectivity 82installing languages 34ODBC (Open Database Connectivity) 76TCP/IP network protocol 76troubleshooting 62

PowerCenter domainsconnectivity 77, 79pinging 62TCP/IP network protocol 76troubleshooting 61

PowerCenter repositoryoptimizing for IBM DB2 44

PowerCenter Repository Serviceconnectivity requirements 80

PowerCenter Standard Editionuninstalling 73

PowerExchange for JMSconfiguring JRE path 32

PowerExchange for Web Servicesconfiguring JRE path 32

PowerExchange for webMethodsconfiguring JRE path 32

prerequisitesComplex Data transformation 39third-party requirements 38

Rrepositories

password 43Repository Service

database client 37

Ssamples

odbc.ini file 108server component

Informatica 2, 3Service Manager

log files 60services

starting and stopping 48shared library environment variable

updating 66SHLIB_PATH

HP-UX 32library path 40

64-bit platformsguidelines 34, 36supported platforms 34, 36

Solarisconfiguring X Virtual Frame Buffer (Xvfb) 32

source databasesconnecting through ODBC (UNIX) 105

SQL data servicesJDBC client connections 64ODBC client connections on UNIX 66ODBC client connections on Windows 65

sqlplustesting database connection 35, 38

Start PageInformatica documentation 72

summary logdescription 59

SUSE LinuxJRE_HOME 13

Sybase ASEconnect string syntax 83connecting to Integration Service (Windows) 90, 101

system pathupdating 65

system requirementsComplex Data Exchange 39minimum installation requirements 6

system user accountinstallation requirements 9

Ttablespaces

single node 44target databases

connecting through ODBC (UNIX) 105TCP/IP network protocol

nodes 76PowerCenter Client 76

Index 119

PowerCenter domains 76requirement for Integration Service 82

temporary disk spaceenvironment variables 12

Teradataconnect string syntax 83connecting to Integration Service (UNIX) 103connecting to Integration Service (Windows) 91

third-party requirementsprerequisites 38

third-party softwareinstallation requirements 14

troubleshootingcreating a domain 61domain configuration database 61infacmd 59infasetup 59Informatica Services 61joining a domain 61licenses 62Metadata Manager Client 62pinging a domain 62pmrep 59PowerCenter Client 62uninstallation 73

Uuninstalling

process 74rules and guidelines 73troubleshooting 73

UNIXconnecting to ODBC data sources 105database client environment variables 35, 38database client variables 35, 38environment variables 29library paths 30user account 9

user accountsystem user 9

user account privilegesData Analyzer repositories 43Data Profiling warehouse 43Metadata Manager repositories 43

usersdatabase 43

Vviewing

PowerCenter documentation 72

Wweb browser

configuring 33

XX Virtual Frame Buffer (Xvfb)

installing on UNIX 32X Window Server

installation requirements 13

120 Index