Informatica (Version 9.5.

0)

Administrator Guide

Informatica Administrator Guide Version 9.5.0 June 2012 Copyright (c) 1998-2012 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 and disclosure 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 international Patents 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 in DFARS 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 in writing. 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 Informatica On Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and Informatica Master Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names 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 rights reserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All rights reserved.Copyright © Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright © Meta Integration Technology, Inc. All rights reserved. Copyright © Intalio. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © Adobe Systems Incorporated. All rights reserved. Copyright © DataArt, Inc. All rights reserved. Copyright © ComponentSource. All rights reserved. Copyright © Microsoft Corporation. All rights reserved. Copyright © Rogue 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. Copyright © Thinkmap, Inc. All rights reserved. Copyright © Clearpace Software Limited. All rights reserved. Copyright © Information Builders, Inc. All rights reserved. Copyright © OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo Communications, Inc. All rights reserved. Copyright © International Organization for Standardization 1986. All rights reserved. Copyright © ej-technologies GmbH. All rights reserved. Copyright © Jaspersoft Corporation. All rights reserved. Copyright © is International Business Machines Corporation. All rights reserved. Copyright © yWorks GmbH. All rights reserved. Copyright © Lucent Technologies 1997. All rights reserved. Copyright (c) 1986 by University of Toronto. All rights reserved. Copyright © 1998-2003 Daniel Veillard. All rights reserved. Copyright © 2001-2004 Unicode, Inc. Copyright 1994-1999 IBM Corp. All rights reserved. Copyright © MicroQuill Software Publishing, Inc. All rights reserved. Copyright © PassMark Software Pty Ltd. 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 the License 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 not limited 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 of this software is subject to terms available at http://www.openssl.org and http://www.openssl.org/source/license.html. This product includes Curl software which is Copyright 1996-2007, Daniel Stenberg, <daniel@haxx.se>. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies. The product includes software copyright 2001-2005 (©) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at 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 terms available at http://dojotoolkit.org/license. This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/license.html. This product includes 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 & Wireless Deutschland. 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 subject to 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 terms available 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, http://fusesource.com/downloads/license-agreements/fuse-message-broker-v-5-3- licenseagreement; http://antlr.org/license.html; http://aopalliance.sourceforge.net/; http://www.bouncycastle.org/licence.html; http://www.jgraph.com/jgraphdownload.html; http:// www.jcraft.com/jsch/LICENSE.txt. http://jotm.objectweb.org/bsd_license.html; . http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231; http:// developer.apple.com/library/mac/#samplecode/HelpHook/Listings/HelpHook_java.html; http://www.jcraft.com/jsch/LICENSE.txt; http://nanoxml.sourceforge.net/orig/ copyright.html; http://www.json.org/license.html; http://forge.ow2.org/projects/javaservice/, http://www.postgresql.org/about/licence.html, http://www.sqlite.org/copyright.html, http://www.tcl.tk/software/tcltk/license.html, http://www.jaxen.org/faq.html, http://www.jdom.org/docs/faq.html; http://www.iodbc.org/dataspace/iodbc/wiki/iODBC/License; http://

www.keplerproject.org/md5/license.html; http://www.toedter.com/en/jcalendar/license.html; http://www.edankert.com/bounce/index.html; http://www.net-snmp.org/about/ license.html; http://www.openmdx.org/#FAQ; http://www.php.net/license/3_01.txt; and http://srp.stanford.edu/license.txt; and http://www.schneier.com/blowfish.html; http:// www.jmock.org/license.html; http://xsom.java.net/. This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and Distribution License (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php), the Sun Binary Code License Agreement Supplemental License Terms, the BSD License (http:// www.opensource.org/licenses/bsd-license.php) the MIT License (http://www.opensource.org/licenses/mitlicense.php) and the Artistic License (http://www.opensource.org/licenses/artistic-license-1.0). This product includes software copyright © 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this software are subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab. For further information 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,243,110; 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422; 7,676,516; 7,720,842; 7,721,270; and 7,774,791, international Patents and other Patents Pending. DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject 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 Software Corporation ("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 NOT LIMITED 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 OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS. Part Number: IN-ADG-95000-0001

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi Informatica Customer Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii Informatica Multimedia Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii

Chapter 1: Understanding Domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Understanding Domains Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Gateway Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Worker Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Service Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Application Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Analyst Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Content Management Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Data Director Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Data Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Metadata Manager Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 PowerCenter Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 PowerCenter Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 PowerExchange Listener Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 PowerExchange Logger Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Reporting Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Reporting and Dashboards Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 SAP BW Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Web Services Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 User Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Table of Contents

i

Chapter 2: Managing Your Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Managing Your Account Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Logging In. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Informatica Administrator URL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Changing Your Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Editing Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 3: Using Informatica Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Using Informatica Administrator Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Domain Tab Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Domain Tab - Services and Nodes View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Application Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Grids. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Domain Tab - Connections View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Logs Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Reports Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Monitoring Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Security Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Using the Search Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Using the Security Navigator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Keyboard Shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 4: Domain Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Domain Management Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Alert Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Configuring SMTP Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Subscribing to Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Viewing Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Folder Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Creating a Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Moving Objects to a Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Removing a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Domain Security Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 User Security Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

ii

Table of Contents

Application Service Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Enabling and Disabling Services and Service Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Viewing Service Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Configuring Restart for Service Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Removing Application Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Troubleshooting Application Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Node Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Defining and Adding Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Configuring Node Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Viewing Processes on the Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Shutting Down and Restarting the Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Removing the Node Association. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Removing a Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Gateway Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Domain Configuration Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Backing Up the Domain Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Restoring the Domain Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Migrating the Domain Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Updating the Domain Configuration Database Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Domain Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Managing and Monitoring Application Services and Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Viewing Dependencies for Application Services, Nodes, and Grids. . . . . . . . . . . . . . . . . . . . . . 43 Shutting Down a Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Domain Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 General Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Database Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Gateway Configuration Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Service Level Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 SMTP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Custom Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 5: Application Service Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Application Service Upgrade Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Service Upgrade for Data Quality 9.0.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Service Upgrade for Data Services 9.0.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Service Upgrade for PowerCenter 9.0.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Service Upgrade for PowerCenter 8.6.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Service Upgrade Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Upgrade Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Running the Service Upgrade Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Users and Groups Conflict Resolution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Table of Contents

iii

Chapter 6: Domain Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Domain Security Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Secure Communication Within the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Configuring Secure Communication Within the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 TLS Configuration Using infasetup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Secure Communication with External Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Secure Communication to the Administrator Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Chapter 7: Users and Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Users and Groups Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Default Everyone Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Understanding User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Default Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Domain Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Application Client Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Understanding Authentication and Security Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Native Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 LDAP Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Setting Up LDAP Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Step 1. Set Up the Connection to the LDAP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Step 2. Configure Security Domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Step 3. Schedule the Synchronization Times. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Deleting an LDAP Security Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Using a Self-Signed SSL Certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Using Nested Groups in the LDAP Directory Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Managing Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Adding Native Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Editing General Properties of Native Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Assigning Users to Native Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Enabling and Disabling User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Deleting Native Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 LDAP Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Unlocking a User Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Increasing System Memory for Many Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Managing Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Adding a Native Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Editing Properties of a Native Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Moving a Native Group to Another Native Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Deleting a Native Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 LDAP Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Managing Operating System Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

iv

Table of Contents

Create Operating System Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Properties of Operating System Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Creating an Operating System Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Account Lockout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Configuring Account Lockout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Rules and Guidelines for Account Lockout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Chapter 8: Privileges and Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Privileges and Roles Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Domain Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Security Administration Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Domain Administration Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Monitoring Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Tools Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Analyst Service Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Data Integration Service Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Metadata Manager Service Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Catalog Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Load Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Model Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Security Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Model Repository Service Privilege. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 PowerCenter Repository Service Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Tools Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Folders Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Design Objects Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Sources and Targets Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Run-time Objects Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Global Objects Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 PowerExchange Listener Service Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 PowerExchange Logger Service Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 Reporting Service Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 Administration Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104 Alerts Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Communication Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 Content Directory Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Dashboards Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Indicators Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 Manage Account Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 Reports Privilege Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 Reporting and Dashboards Service Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Table of Contents

v

Managing Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 System-Defined Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Custom Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Managing Custom Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Assigning Privileges and Roles to Users and Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Inherited Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Steps to Assign Privileges and Roles to Users and Groups. . . . . . . . . . . . . . . . . . . . . . . . . . 113 Viewing Users with Privileges for a Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Troubleshooting Privileges and Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Chapter 9: Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Permissions Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Types of Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Permission Search Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Domain Object Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Permissions by Domain Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Permissions by User or Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Operating System Profile Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Connection Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Types of Connection Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Default Connection Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Assigning Permissions on a Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Viewing Permission Details on a Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Editing Permissions on a Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 SQL Data Service Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Types of SQL Data Service Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Assigning Permissions on an SQL Data Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Viewing Permission Details on an SQL Data Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Editing Permissions on an SQL Data Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Denying Permissions on an SQL Data Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Column Level Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Row Level Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Web Service Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Types of Web Service Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Assigning Permissions on a Web Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Viewing Permission Details on a Web Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Editing Permissions on a Web Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Chapter 10: High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
High Availability Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Resilience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Restart and Failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

vi

Table of Contents

High Availability in the Base Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Internal PowerCenter Resilience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 PowerCenter Repository Service Resilience to PowerCenter Repository Database. . . . . . . . . . . 138 Restart Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Manual PowerCenter Workflow and Session Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Multiple Gateway Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Achieving High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Configuring Internal Components for High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Using Highly Available External Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Rules and Guidelines for Configuring High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Managing Resilience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Configuring Service Resilience for the Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Configuring Application Service Resilience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Understanding PowerCenter Client Resilience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Configuring Command Line Program Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Managing High Availability for the PowerCenter Repository Service. . . . . . . . . . . . . . . . . . . . . . . . 144 Resilience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Restart and Failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Managing High Availability for the PowerCenter Integration Service. . . . . . . . . . . . . . . . . . . . . . . . 145 Resilience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Restart and Failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Troubleshooting High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Chapter 11: Analyst Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Analyst Service Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Analyst Service Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Configuration Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Associated Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Staging Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Flat File Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Keystore File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Configure the TLS Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Recycling and Disabling the Analyst Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Properties for the Analyst Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 General Properties for the Analyst Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Model Repository Service Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Data Integration Service Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Metadata Manager Service Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Staging Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Logging Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Custom Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Table of Contents

vii

Process Properties for the Analyst Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Node Properties for the Analyst Service Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Analyst Security Options for the Analyst Service Process. . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Advanced Properties for the Analyst Service Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Custom Properties for the Analyst Service Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Environment Variables for the Analyst Service Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Creating and Deleting Audit Trail Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Creating and Configuring the Analyst Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Creating an Analyst Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Chapter 12: Content Management Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Content Management Service Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Content Management Service Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Creating a Content Management Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Recycling and Disabling the Content Management Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Content Management Service Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 General Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Multi-Service Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Associated Services and Reference Data Location Properties. . . . . . . . . . . . . . . . . . . . . . . . 166 Logging Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Custom Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Content Management Service Process Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Content Management Service Security Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Address Validation Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 NER Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Custom Properties for the Content Management Service Process. . . . . . . . . . . . . . . . . . . . . . 171

Chapter 13: Data Director Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Data Director Service Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Configuration Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Keystore File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Creating a Data Director Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Data Director Service Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 General Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 HT Service Options Property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Custom Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Logging Options Property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Data Director Service Process Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Security Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Advanced Option Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Environment Variable Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Custom Properties for the Data Director Service Process. . . . . . . . . . . . . . . . . . . . . . . . . . . 176 TLS Protocol Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

viii

Table of Contents

Recycle and Disable the Data Director Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Chapter 14: Data Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Data Integration Service Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Data Integration Service Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Data Transformation Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Profiling Service Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Mapping Service Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 REST Web Service Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 SQL Service Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Web Service Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Workflow Service Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Data Object Cache Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Result Set Cache Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Deployment Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Data Integration Service Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Data Integration Service Grid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 HTTP Client Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Creating a Data Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Data Integration Service Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 General Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Model Repository Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Email Server Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Logical Data Object/Virtual Table Cache Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Logging Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Pass-through Security Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 HTTP Proxy Server Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 HTTP Client Filter Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Execution Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Result Set Cache Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Human Task Service Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Mapping Service Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Profiling Warehouse Database Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Advanced Profiling Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 SQL Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Workflow Service Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Web Service Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Custom Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Data Integration Service Process Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Data Integration Service Security Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 HTTP Client Filter Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Result Set Cache Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Table of Contents

ix

. . . . . . . . . . . . . . . . . . . . . . . . . . . 212 SQL Data Service Properties. . . . . . . . . . . . . . . . . . . .209 Refreshing the Applications View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204 Chapter 15: Data Integration Service Applications. . . . . . . . 206 Deploying an Application. . . . . . . . . . . . . . . . . . . . .208 Renaming an Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Starting an Application. . . . . . . . . . . . . . . . . . . . . . . . 201 Troubleshooting the Grid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Advanced Properties. . . . . . . . . . . . . . . . . . . . Disabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Web Service Properties. . . . . . . . . . 198 Execution Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214 Renaming an SQL Data Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217 Workflow Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Enabling a Web Service. . . . . . . . 217 Enabling a Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209 Logical Data Objects. . 205 Data Integration Service Applications Overview. . . . . . . . . . . . . . . . . . 200 Custom Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 x Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217 Workflows. . 209 Restoring an Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . and Recycling the Data Integration Service. . . . . . . . . . . . . . .206 Application State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208 Backing Up an Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Creating and Deleting Profiling Warehouse Content. . . . . . . .217 Renaming a Web Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205 Applications View. . . . . . . . . . . . . . .215 Web Services.203 Result Set Caching. . .210 Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200 Assigning a Data Integration Service to a Grid. . . . 201 Content Management for the Profiling Warehouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212 Enabling an SQL Data Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Logging Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Enabling. . . . . . . . . . . . . . . . 210 SQL Data Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205 Applications. .200 Configuration for the Data Integration Service Grid. . . . . . . . . . . . . . . . 200 Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200 Creating a Grid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202 Web Service Security Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198 SQL Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Application Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Enabling an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Metadata Manager Service Properties. . . . . . . . . . . . . . . . 234 Model Repository Connectivity. . . . . . . . . . . . . . . . . . . . . . . . 225 Restoring the PowerCenter Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Oracle Database Requirements. . 237 Properties for the Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Cache Properties for the Model Repository Service. . . . . . . . . . 236 Microsoft SQL Server Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . 231 Privileges for the Associated PowerCenter Integration Service User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Overriding the Repository Database Code Page. . 233 Model Repository Service Overview. . 233 Model Repository Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Database Connect Strings. . . . . . . . . . . . . . 234 Model Repository Database Requirements. . . . . . . 225 Enabling and Disabling the Metadata Manager Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Connection Pool Properties. . . . . . . . . . . . . . . . . . . . . . . . . . 226 General Properties. . . . . 239 Search Properties for the Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Creating the Metadata Manager Repository. . . . . . . . . . . . . . . 224 Creating and Deleting Repository Content.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Advanced Properties. . . . . . . . . . . . . . . . . . . . 240 Custom Properties for the Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . 233 Model Repository Objects. . . . . . . 235 IBM DB2 Database Requirements. . . . . . . . 230 Custom Properties. 220 Creating a Metadata Manager Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Model Repository Service Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 General Properties for the Model Repository Service. . . . . . . . . . . . . . . . . . . 225 Deleting the Metadata Manager Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Metadata Manager Service Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Repository Performance Properties for the Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Configuring a Metadata Manager Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Advanced Properties for the Model Repository Service. 231 Configuring the Associated PowerCenter Integration Service. . . . .Chapter 16: Metadata Manager Service. . . . . . . . . . . . . . . . . 237 Enabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Chapter 17: Model Repository Service. . . . . . . . . . . . . . 219 Metadata Manager Service Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . and Recycling the Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Table of Contents xi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Configuring the Metadata Manager Service Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 IBM DB2 Version 9. . . . . 228 Configuration Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Database Properties. .

. . . . . . 258 Advanced Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 PowerCenter Integration Service Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Custom Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Troubleshooting Operating System Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 PowerCenter Integration Service Properties. . . . . 241 Model Repository Service Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 xii Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Configuring Operating System Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Creating a PowerCenter Integration Service. . . .Properties for the Model Repository Service Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Repository Log Management for the Model Repository Service. 268 Directories for PowerCenter Integration Service Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Associated Repository for the PowerCenter Integration Service. . . . . . 240 Node Properties for the Model Repository Service Process. . . . . 257 General Properties. . 269 General Properties. . . . . . . . . . . . . . . . . 249 PowerCenter Integration Service Overview. . . . . . 259 Operating Mode Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Model Repository Backup and Restoration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Content Management for the Model Repository Service . . . . . . . . 247 Creating a Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Code Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Enabling and Disabling PowerCenter Integration Services and Processes. . . . . . . . 245 Search Management for the Model Repository Service . . . . . . . . . . . . . 265 Operating System Profile Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Operating Mode. . . . . . . . . . . . 243 Security Management for the Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Running the PowerCenter Integration Service in Safe Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Directories for Java Components. . 256 PowerCenter Integration Service Properties. . . . . . . . . . . . . . . . . . . . . . . . 247 Cache Management for the Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Safe Mode. . . . . . . . . . . . . . . 263 HTTP Proxy Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Chapter 18: PowerCenter Integration Service. . . . . . . . . . . . . . . . . . . . 246 Audit Log Management for Model Repository Service . . . . . . 261 Compatibility and Database Properties. . . . . . . . . . . . . . . . . 252 Enabling or Disabling the PowerCenter Integration Service. . . . . . . . . . . . . . . . . . . . . . 265 Operating System Profiles. . . . . . . . . . . . . . . . . . . 252 Enabling or Disabling a PowerCenter Integration Service Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Configuring the PowerCenter Integration Service Operating Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Custom Properties. . . 253 Normal Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Configuration Properties. . . . . . . .

. . . . . . . . . . . 291 Block Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 Cache Memory. . 293 System Resources. . . . . . . . . . . . 278 Configuring Resources. . . . . . 272 Configuring the PowerCenter Integration Service Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Configuration for the PowerCenter Integration Service Grid. . . . . 272 Configuring the PowerCenter Integration Service to Run on a Grid. . . . . . . . 294 CPU Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Unicode Data Movement Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Session on a Grid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Calculating the CPU Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 Reading Source Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 DTM Buffer Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 PowerCenter Integration Service Architecture Overview. . . . . 272 Creating a Grid. . . . . . . 282 PowerCenter Integration Service Process. . . . . . . . . . . . . . . . . . . . . . . 282 Load Balancer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Service Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 Code Pages and Data Movement Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Chapter 19: PowerCenter Integration Service Architecture. . . . . . . . . . . . . . . . . . . 286 Data Transformation Manager (DTM) Process. . . 287 Processing Threads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Grids. . . . . . . . . . . . . . 296 Output Files and Caches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Table of Contents xiii . . . . . . . . . . . . . . . . . 288 Thread Types. . . 284 Dispatch Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Environment Variables. . . . . . . . . . . . 273 Troubleshooting the Grid. . . . . . . . . . . . . . . . . 296 ASCII Data Movement Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Resources. . . . . . . . . . . . . . . . . 285 Dispatch Mode. . . . . . . . . . . . . . . . . . . . . . . . . 276 Configuring the Dispatch Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Service Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . 289 Pipeline Partitioning. . . . . . . . . . . . . . . . . . 290 DTM Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 Resource Provision Thresholds. . . . . . . . . . . . . . . . . . . 292 Workflow on a Grid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 PowerCenter Integration Service Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 Blocking Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Load Balancer for the PowerCenter Integration Service . . . . . . . . . . . . . . . . . . . . . 279 Defining Resource Provision Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . 314 Running a PowerCenter Repository Service in Exclusive Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 Creating PowerCenter Repository Content. . . . 304 PowerCenter Repository Service Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Session Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 Indicator File. . . . .Workflow Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Database Connect Strings. . 305 Repository Properties. . 298 Recovery Tables Files. . . . 298 Row Error Logs. . . . . . 314 Running a PowerCenter Repository Service in Normal Mode. . . . . . . . . . . . . . . . . . 309 PowerCenter Repository Service Process Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Custom Properties. . . . . . . . . . . . . 299 Cache Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 General Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 PowerCenter Repository Management Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 Deleting PowerCenter Repository Content. . . . . . . . . . . . 298 Reject Files. . . . . . . . . . . . . . . . . . . . . . . . 305 Node Assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 Enabling and Disabling PowerCenter Repository Service Processes. . . . . . . . . 306 Advanced Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Database Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 PowerCenter Repository Service and Service Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 Email. . . . . . . . . . . . . . . . . . . . . 298 Performance Detail File. . . . . . . . . . . . . . . 310 Environment Variables. . . . . . . . . . . . . . . . . . . . . 297 Session Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Creating a PowerCenter Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . 301 PowerCenter Repository Service Overview. . . . . . . . . . . . . . . . . . . . . . . 300 Chapter 20: PowerCenter Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 Control File. . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Creating the PowerCenter Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Operating Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 Creating a Database for the PowerCenter Repository. . . . . . . . . . . . . . . . . . . . . . . . . . 316 xiv Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 Output File. . . . . . . . . . 312 Enabling and Disabling a PowerCenter Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Custom Properties. . . . . . . . . 315 PowerCenter Repository Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 Chapter 21: PowerCenter Repository Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 Metadata Manager Service Properties. . . . . . . . . . . . . . . . . .

. . . . . .Upgrading PowerCenter Repository Content. . . . . . . . . 324 Copying Content from Another Repository. . . 333 Restarting the Listener Service. . . . . . . . 325 Repository Plug-in Registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Viewing Locks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Configuring Listener Service Configuration Properties. . . . . . . . . 332 Disabling the Listener Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 PowerExchange Listener Service Configuration Properties. . . . . . . . . . . . . . 321 Viewing User Connections. . . . . . . 326 Registering a Repository Plug-in. . . . . . . . . . . . . . 320 Managing User Connections and Locks. . . . . . . . 327 Chapter 22: PowerExchange Listener Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 Building a PowerCenter Repository Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 DBMOVER Statements for the Listener Service. . . . . . . . . . . . . . . 318 Promoting a Local Repository to a Global Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Repository Statistics. . . . . 328 PowerExchange Listener Service Overview. . . . . . . . . . 316 Enabling Version Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Listener Service Management. . . . . . . . . 319 Viewing Registered Local and Global Repositories. . . . . . . . 323 Backing Up a PowerCenter Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Table of Contents xv . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Repository Copy. . . . . . . . . . . . . 324 Restoring a PowerCenter Repository. . 318 Registering a Local Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Listener Service Restart and Failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup. . . . . . . . . . . . . 332 Enabling the Listener Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Configuring Listener Service General Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 PowerExchange Listener Service General Properties. . . . . 332 Configuring the Listener Service Process Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 Backing Up and Restoring the PowerCenter Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Repository Performance Tuning. . . . . . . . 333 Listener Service Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 Sending Repository Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Moving Local and Global Repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Unregistering a Repository Plug-in. . . . . . . . . . . . . . . . . . 323 Viewing a List of Backup Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Closing User Connections and Releasing Locks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Managing a Repository Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 Properties of the Listener Service. . . 332 Service Status of the Listener Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 Prerequisites for a PowerCenter Repository Domain. . . . . . . . . . . . . . . . . . . . . and Restore Processes. . . 326 Audit Trails. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 Configuring the Logger Service Process Properties. . . . . 337 Configuring Logger Service General Properties. . . . . . . . . . . . . . . . . . . 339 Logger Service Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 PowerExchange Logger Service General Properties. . . . . . . . . . . . . 347 Deleting Contents from the Data Analyzer Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 Restoring Contents to the Data Analyzer Repository. . . . . . . . . . . . . . . . . . . . 335 Configuration Statements for the Logger Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Metadata Manager Repository Reports. . . . . 346 Backing Up Contents of the Data Analyzer Repository. 349 Repository Properties. . . . . . . . . . . . . . . . 341 Data Profiling Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 Restarting the Logger Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 Data Source Properties. . . . . . . . . . . . . . . 348 Reporting Service Properties. . . . . . . . . . . . . . . . . . . . . . . . 342 Managing the Reporting Service. . . . . . . 344 Configuring the Edit Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 Enabling the Logger Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Granting Users Access to Reports. . . . . 339 Creating a Logger Service. . . . . . . . . . . . . . . 338 Service Status of the Logger Service. . . . . . . . . . . . . . . . . . .Creating a Listener Service. . . . . . . . . 334 PowerExchange Logger Service Overview. . . 348 General Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 Upgrading Contents of the Data Analyzer Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Data Analyzer Repository. . . . . . . 337 Logger Service Management. . . . . . . . . . . . . . . . . . . . . . . 345 Enabling and Disabling a Reporting Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Chapter 23: PowerExchange Logger Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 Chapter 24: Reporting Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Other Reporting Sources. . . . . . . . . . . . . . . . . . . . . . . 336 PowerExchange Logger Service Configuration Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 Configuring Logger Service Configuration Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 Viewing Last Activity Logs. . . . . . . . . . . . . . . . . . . . . 345 Creating Contents in the Data Analyzer Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 Reporting Service Overview. . . . . . 338 Disabling the Logger Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 Configuring the Reporting Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 xvi Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 Creating the Reporting Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Properties of the PowerExchange Logger Service. . . . . . . . . . . . . . . 340 PowerCenter Repository Reports. . 334 Logger Service Restart and Failover.

. . . . . . . 355 Reporting and Dashboards Service Advanced Properties. . . . 358 Enabling and Disabling the Reporting and Dashboards Service. . . . . . . . . . 369 General Properties. . . . . . . . 357 Running Reports. . . . . . 367 Enabling and Disabling the Web Services Hub. . . . . . . . . . . . . . . . . . . . . . . . . 353 Installing Jaspersoft. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 Environment Variables for the Reporting and Dashboards Service. . . . . . . . . . . . . . . . 358 Uninstalling Jaspersoft. . . . . . . . . . . 370 Table of Contents xvii . . . . . . . . . . . . . . 366 Web Services Hub Overview. . . . . . . . . . . . . . . . . . . . 357 Reporting Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 Chapter 26: SAP BW Service. . . . . . . . . 352 Reporting and Dashboards Service Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 Editing a Reporting and Dashboards Service. . . . . 358 Connection to the Jaspersoft Repository from Jaspersoft iReport Designer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Viewing Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 25: Reporting and Dashboards Service. . 353 default_master. . . . . . . . . . . . . . . . 360 Load Balancing for the SAP NetWeaver BI System and the SAP BW Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 JasperReports Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Configuring the SAP BW Service Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 Creating the SAP BW Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 Reporting and Dashboards Service Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Reporting and Dashboards Service General Properties. . . . . . .properties File Configuration. . . . . . 357 Adding a Reporting Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Enabling the SAP BW Service. . . . . 356 Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 SAP BW Service Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 SAP BW Service Overview. . . . . . . . . . . 368 Configuring the Web Services Hub Properties. . . . . . . . . . 363 Configuring the Associated Integration Service. . . . . . . . . . . . . . . 353 Configuration Prerequisites. . . . . . . . . . . . . . . . . . . 356 Creating a Reporting and Dashboards Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Disabling the SAP BW Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Reporting and Dashboards Service Security Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 Enabling and Disabling the SAP BW Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Configuring the SAP BW Service Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Chapter 27: Web Services Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 Creating a Web Services Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 Users and Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 General Properties. . . . . . . . . . . .

. . . . . 375 Tools Reference for Creating and Managing Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 Connection Pooling. . . . . . 396 Chapter 29: Domain Object Export and Import. . . . . . . . . . . . 398 Rules and Guidelines for Exporting Domain Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 Connection Management Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . 398 Export Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 Adding an Associated Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 Import Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Pass-through Security with Data Object Caching. . . . . . . . . . . 390 LinkedIn Connection Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394 Rules and Guidelines to Update Database Connection Properties. . . . . . . . . . . . . . . . . . . . . . . . 396 Pooling Properties. . . . . . . . . . . . . . . . . . . . 394 Web Services Connection Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 Configuring Pooling for a Connection. 405 Rules and Guidelines for Importing Domain Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Editing and Testing a Connection. . . . . . . . . . . 386 DB2 for z/OS Connection Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392 Twitter Connection Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 Editing an Associated Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . 406 Conflict Resolution. . . . . . . . . . . . .Service Properties. . . . . . . . . . . . . . . . 393 Twitter Streaming Connection Properties. . . . . . . . . . . . . . . . . . . 389 Facebook Connection Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 Viewing a Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Relational Database Connection Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Connection Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 Considerations for PowerExchange Connection Pooling. . . . . . . . . . . . . . . . . 391 Nonrelational Database Connection Properties. . . . . . . . . . . . . . . . . . . . 384 DB2 for i5/OS Connection Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Configuring the Associated Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 Adding Pass-Through Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Pass-through Security. . . . . . . . . . 383 Deleting a Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Advanced Properties. . . . . . . . . 399 Viewable Domain Object Names. . . . 371 Custom Properties. . . . . . . . . . . . 378 Creating a Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 Domain Object Export and Import Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 Chapter 28: Connection Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 View Domain Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 xviii Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Refreshing the Connections List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 Metadata Exchange Options. . . . . . . . . . . . . . . . . . . . . . 416 Log Management Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 Log Manager Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 Licensing Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 License Management Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 Troubleshooting the Log Manager. . 413 License Details. . . . . . . . . . . . . . . . . . . . .Chapter 30: License Management. . . . . . . . . . . . . . . 412 License Properties. . 409 Incremental Keys. . . . . . . . . 409 Assigning a License to a Service. . . . . . . . . 414 Repositories. . . . . . . . . . . . . . . . . . . . . . . . 417 PowerCenter Session and Workflow Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409 Creating a License Object. . . . . . . . . . . . . . . . . . 426 Table of Contents xix . . . . . . . . . 424 Log Events. . . . . . . . . . 414 PowerCenter Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 Connections. . . . . . . . 419 Time Zone. . . . . . . . . . . . . . 408 Types of License Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 Updating a License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 Purging Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 Log Manager Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . 420 Viewing Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . 418 Log Management Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 Configuring Log Columns. . . . . . . . . . . . . . . . . . . 413 Supported Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 License Validation. . . . . . . . . . . . . . . . . . 407 License Management Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 Unassigning a License from a Service. . . . . . . . . . . 422 Saving Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425 Domain Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418 Log Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 Using the Logs Tab. . . . . . . . . . 422 Exporting Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . 423 Viewing Administrator Tool Log Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 Configuring Log Management Properties. . . . . . . . . . . . . . . 410 Rules and Guidelines for Assigning a License to a Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 Chapter 31: Log Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409 Original Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 Removing a License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424 Log Event Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 Monitor Logical Data Objects. . . . . 426 Listener Service Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 Chapter 32: Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 Canceling a Job. . . . . . . . . 431 Views in the Monitoring Tab. . . . . . 438 Viewing Logs for a Job. . . . . . . . . . . . . . . . . . . . . . 442 Viewing Logs for Data Object Cache Refresh Runs. . . . . . . . . . . . . . . . . . . . 428 SAP BW Service Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 Metadata Manager Service Log Events. . . . . . .Analyst Service Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . . 428 Reporting Service Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 Monitor Deployed Mapping Jobs. . . . . . . . . . . . . . . . . 439 Properties View for an Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 Canceling a Deployed Mapping Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 Properties View for a Logical Data Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 Reports in the Monitoring Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428 Web Services Hub Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 Model Repository Service Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436 Step 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 User Activity Log Events. . . . . . . . . . . . . . 427 Logger Service Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Requests View for an SQL Data Service. . . . . . . . . . . . . . . . . . . . . . . . . 443 Connections View for an SQL Data Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Global Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 Reissuing a Deployed Mapping Job. 438 Reports View for a Data Integration Service. . 444 xx Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436 Step 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 Viewing Logs for a Deployed Mapping Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430 Monitoring Overview. . . . . . . . . . . . . . . . . . . . . . 437 Properties View for a Data Integration Service. . . . . . . . . . . 433 Monitoring Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 Cache Refresh Runs View for a Logical Data Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 PowerCenter Integration Service Log Events. . . . . . . . . . . . . . . . . . . . . . . 426 Data Integration Service Log Events. . . . . . . . . . . . . . . . 428 PowerCenter Repository Service Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 Monitor SQL Data Services. . . . . . . . . . . . 442 Properties View for an SQL Data Service. . . . . . . . . 438 Monitor Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 Monitor Data Integration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 Reports View for an Application. . . . . . . 430 Navigator in the Monitoring Tab. . . . 439 Monitor Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 Statistics in the Monitoring Tab. . . . . . . . . Configure Monitoring Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . 451 Chapter 33: Domain Reports. . . . . . . . . . . . . . . . . . . . 451 Monitoring an Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 CPU Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457 Node Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455 Repository Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444 Reports View for an SQL Data Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 Workflow Logs. . . . . . . . . . 451 Configuring the Elapsed Time Custom Filter. . . . . 458 Running the License Management Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 Domain Reports Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456 User Summary. . . . . . . . . . . . . . 456 Hardware Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 Configuring the Multi-Select Custom Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 Reports View for a Web Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Virtual Tables View for an SQL Data Service. . . . . . . . . . . . . . . . . 449 Monitoring a Folder of Objects. . . . . 447 Monitor Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463 Web Service Top IP Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 Workflow and Workflow Object States. . . . . . . . 465 Table of Contents xxi . . . . . . . . . . 461 Web Services Historical Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 Requests View for a Web Service. . . . . . . . . . . . . . . . . . . . . . 459 Web Services Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458 Sending the License Management Report in an Email. . . . . . . . . . . . 446 Operations View for a Web Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462 Web Services Run-time Statistics. . . . . . . 447 View Workflow Objects. . . . . . 464 Running the Web Services Report for a Secure Web Services Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445 Monitor Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 CPU Detail. . 447 Canceling or Aborting a Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460 General Properties and Web Services Hub Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 License Management Report. . . . . . . . . . . . . . . 464 Web Service Historical Statistics Table. . . . . . 445 Properties View for a Web Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458 Licensed Options. . . . . . . . . . . . . . . . . 456 User Detail. . . . . . . . . . . . . . . . . . . . . . . . . . 463 Web Service Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464 Running the Web Services Report. . . . . . . . . 450 Configuring the Date and Time Custom Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460 Understanding the Web Services Report. . . . . . . . . . . . . . . . . . 450 Viewing the Context of an Object. . . . . . . . . . . . . . . . . . . .

. . 473 Working with a Unicode PowerCenter Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 Identify Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 Locales. . . . . . . . . . . . . . . . . . . . . . . 481 Metadata Manager Repository Code Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 Troubleshooting for Code Page Relaxation. . . . 470 Analyzing Node Diagnostics. . . . . . . . . . . . . . 468 Generating Node Diagnostics. 487 xxii Table of Contents . 482 PowerCenter Source Code Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484 Code Page Validation. . . . . . . . . . . . . . . . . 467 Node Diagnostics Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474 Input Locale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475 Changing Data Movement Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475 Character Data Movement Modes. . . . . . . . . . . . . . . . . . . . . . . . . . 477 Windows Code Pages. . . . . . . . . . . . . . . 480 Administrator Tool Code Page. . . . . . . . . . 481 PowerCenter Repository Code Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474 User Locale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472 Globalization Overview. . . . . . . . . . . . . . . . . . . . 469 Downloading Node Diagnostics. . . . . . . . . . 471 Identify Bug Fixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 Customer Support Portal Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478 Code Page Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476 Code Page Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . 480 PowerCenter Client Code Page. . . 477 UNIX Code Pages. . . . . . . . . . . . . 480 PowerCenter Integration Service Process Code Page. . . 478 Domain Configuration Database Code Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482 Command Line Program Code Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472 Unicode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 34: Node Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474 System Locale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475 Data Movement Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482 PowerCenter Target Code Page. . . . . . . . 487 Selecting Compatible Source and Target Code Pages. . . . . . . . . . . . . . . . . . . . . . 483 Code Page Compatibility Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469 Uploading Node Diagnostics. . . . . . . . . . . . . . . . . 485 Relaxed Code Page Validation. . 486 Configuring the PowerCenter Integration Service. . . . . . . . . . 471 Chapter 35: Understanding Globalization. . . . . . . . . . . . . . . . . . . 468 Logging In to the Customer Support Portal. . . . 478 Choosing a Code Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541 IBM DB2. . . 533 Reporting Service Custom Roles. . . . . . . . . . . . 542 Table of Contents xxiii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 infacmd rds Commands. . 488 Configuring the ISO 8859-1 Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523 infacmd wfs Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508 infacmd mrs Commands. . . 542 Oracle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494 Supported Code Pages for Sources and Targets. . . . 534 Appendix D: Repository Database Configuration for PowerCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .PowerCenter Code Page Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 Appendix B: Command Line Privileges and Permissions. . . . . . . . . . . 540 Repository Database Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 infacmd sql Commands. . . . . . . . . . . . . . . . . . 487 Choosing Characters for PowerCenter Repository Metadata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541 Data Analyzer Repository Database Requirements. . . . . . . . . . . . . . . . . . . . . 541 Oracle. . . . . . . . . . . . . . . . . . . . . . . . . . 489 Case Study: Processing Unicode UTF-8 Data. . . . . . . . . . . . . . 523 pmcmd Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 Appendix A: Code Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 Case Study: Processing ISO 8859-1 Data. . . . . . . . . . . . . . . . . . . . . . . . . . . 531 Metadata Manager Service Custom Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519 infacmd oie Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520 infacmd pwx Commands. . . . . . . . . . . . . . . . . . . 520 infacmd ps Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506 infacmd as Commands. . . . . . . . . . . . . 541 Sybase ASE. . . . . . . . . . 521 infacmd rtm Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 Configuring the UTF-8 Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 infacmd ms Commands. . . . . . . . . 541 PowerCenter Repository Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540 Guidelines for Setting Up Database User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524 pmrep Commands. . . . . . . . . . . . . . . . . . . . . 531 PowerCenter Repository Service Custom Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494 Supported Code Pages for Application Services. . . . . . . . . . . . . . . . . . . . . . . . . 526 Appendix C: Custom Roles. . . . . . . . . . . . . . . . . . . . 507 infacmd ipc Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506 infacmd dis Commands. . . . . . . . . . . . . . . . . . . . . . 542 Microsoft SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . 508 infacmd isp Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558 Connecting to a Sybase ASE Database from Windows. . . . . . . . . . . . . . . 545 Appendix E: PowerCenter Platform Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547 PowerCenter Connectivity. . . . . . . . . . . . . . . . . 563 Connecting to an IBM DB2 Universal Database from UNIX. . . . . . . . . . . . . . . . . . . 563 Configuring SSL Authentication through ODBC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543 IBM DB2 . 543 Oracle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551 ODBC Connectivity. . . . . . 559 Connecting to a Netezza Database from Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555 Configuring ODBC Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551 Native Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564 xxiv Table of Contents . . . . . 543 Metadata Manager Repository Database Requirements. . . . . . . . . . . . . . . . . . . . . . 555 Configuring Native Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549 PowerCenter Client Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554 Connecting to Databases from Windows Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558 Configuring Native Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . 559 Configuring ODBC Connectivity. . . . . . . . 551 JDBC Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 Connecting to a Teradata Database from Windows. . . . . . . . . 563 Configuring ODBC Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546 Domain Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555 Connecting to a Microsoft SQL Server Database from Windows. . . . . . . . . . . . . . . . 558 Configuring ODBC Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560 Appendix G: Connecting to Databases in PowerCenter from UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546 Connectivity Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560 Configuring ODBC Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544 Microsoft SQL Server. 557 Configuring Native Connectivity. . . . . . . . . . . . . . . . . . . 562 Connecting to Databases from UNIX Overview. . . . . . . . 548 Integration Service Connectivity. . . . . . . . . . . . 550 Reporting Service and Metadata Manager Service Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555 Configuring ODBC Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556 Connecting to an Oracle Database from Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554 Connecting to an IBM DB2 Universal Database from Windows. . . . . . . 547 Repository Service Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Sybase ASE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554 Connecting to Microsoft Access and Microsoft Excel from Windows. . . . . . . . . . . . . . . . . . . 562 Connecting to Microsoft SQL Server from UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552 Appendix F: Connecting to Databases in PowerCenter from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557 Configuring ODBC Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . .ini File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 Connecting to an Oracle Database from UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577 Sample odbc. . . . . . 568 Configuring Native Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring Native Connectivity. . . . . . . 583 Table of Contents xxv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571 Connecting to a Teradata Database from UNIX. . . . . . . . . . 575 Configuring ODBC Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 Configuring Native Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572 Configuring ODBC Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575 Connecting to an ODBC Data Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 Connecting to a Netezza Database from UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . 564 Connecting to an Informix Database from UNIX. . . . . . . . . . . . . . . . . . . . . . . . 571 Configuring Native Connectivity. . . . . . . . . . . . . . . . . 568 Connecting to a Sybase ASE Database from UNIX. . . . . . . 579 Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

informatica.Preface The Informatica Administrator Guide is written for Informatica users.com. contact the Informatica Documentation team through email at infa_documentation@informatica. You will also find product and partner information. and access to the Informatica user community. user group information. xxvi . upcoming events. the Informatica How-To Library.com. newsletters. We will use your feedback to improve our documentation. its background. The site contains product information. To get the latest documentation for your product.com. It contains information you need to manage the domain and security. The How-To Library is a collection of resources to help you learn more about Informatica products and features.informatica. comments. compare features and behaviors. navigate to Product Documentation from http://mysupport. Informatica Documentation The Informatica Documentation team takes every effort to create accurate. The site contains information about Informatica. the Informatica Knowledge Base. Informatica Resources Informatica Customer Portal As an Informatica customer. usable documentation.informatica.com. the Informatica Multimedia Knowledge Base. you can access the Informatica How-To Library at http://mysupport. or ideas about this documentation. you can access the Informatica Customer Portal site at http://mysupport. access to the Informatica customer support case management system (ATLAS). The Documentation team updates documentation as needed. The Informatica Administrator Guide assumes you have basic working knowledge of Informatica.com. and sales offices. If you have questions. and guide you through performing specific real-world tasks. It includes articles and interactive demonstrations that provide solutions to common problems. training and education.informatica. Informatica How-To Library As an Informatica customer. Let us know if we can contact you regarding your comments. Informatica Product Documentation. Informatica Web Site You can access the Informatica corporate web site at http://www. The services area of the site includes important information about technical support. and implementation services.

If you have questions. you can access the Informatica Knowledge Base at http://mysupport. you can access the Informatica Multimedia Knowledge Base at http://mysupport.informatica. Informatica Global Customer Support You can contact a Customer Support Center by telephone or through the Online Support.com. Use the following telephone numbers to contact Informatica Global Customer Support: North America / South America Toll Free Brazil: 0800 891 0202 Mexico: 001 888 209 8853 North America: +1 877 463 2435 Europe / Middle East / Africa Toll Free France: 0805 804632 Germany: 0800 5891281 Italy: 800 915 985 Netherlands: 0800 2300001 Portugal: 800 208 360 Spain: 900 813 166 Switzerland: 0800 463 200 United Kingdom: 0800 023 4632 Standard Rate India: +91 80 4112 5738 Asia / Australia Toll Free Australia: 1 800 151 830 New Zealand: 09 9 128 901 Standard Rate Belgium: +31 30 6022 797 France: +33 1 4138 9226 Germany: +49 1805 702 702 Netherlands: +31 306 022 797 United Kingdom: +44 1628 511445 Preface xxvii . You can request a user name and password at http://mysupport.com. contact the Informatica Knowledge Base team through email at KB_Feedback@informatica. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. technical white papers.com.Informatica Knowledge Base As an Informatica customer. You can also find answers to frequently asked questions. comments.com. Informatica Multimedia Knowledge Base As an Informatica customer.informatica. The Multimedia Knowledge Base is a collection of instructional multimedia files that help you learn about common concepts and guide you through performing specific tasks.com. If you have questions. or ideas about the Multimedia Knowledge Base.informatica. Online Support requires a user name and password. comments. and technical tips. contact the Informatica Knowledge Base team through email at KB_Feedback@informatica. or ideas about the Knowledge Base.

xxviii .

2 ¨ Service Manager. The Informatica domain is the fundamental administrative unit in Informatica. 9 Understanding Domains Overview Informatica has a service-oriented architecture that provides the ability to scale services and share resources across multiple machines. and logging. nodes. The application services that run on a node depend on the way you configure the services. The domain supports the administration of the distributed services. 2 ¨ Application Services. Services and processes run on nodes in a domain. One node in the domain acts as a gateway to receive service requests from clients and route them to the appropriate service and node. The Service Manager manages users and groups that can log in to application clients and authenticates the users who log in to the application clients. Some domain functions include authentication. The Service Manager and application services authorize user requests from application clients. licenses. High availability functionality helps minimize service downtime due to unexpected failures or scheduled maintenance in the Informatica environment. 1 ¨ Nodes. A node is the logical representation of a machine in a domain. You manage the domain and the security of the domain through the Administrator tool. Informatica Administrator (the Administrator tool). 7 ¨ High Availability. The Service Manager and application services control security. such as the Model Repository Service and the Data Integration Service. A domain is a collection of nodes and services that you can group in folders based on administration ownership. authorization. It runs the application services and performs domain functions on each node in the domain. A service that manages all domain operations. consolidates the administrative tasks for domain objects such as services. Services for the domain include the Service Manager and a set of application services: ¨ Service Manager. Services that represent server-based functionality. ¨ Application Services. The availability of a service or process on a node depends on how you configure the service and the node.CHAPTER 1 Understanding Domains This chapter includes the following topics: ¨ Understanding Domains Overview. 1 . and grids. 3 ¨ User Security.

You can subscribe to alerts to receive notification about node events such as node failure or a master gateway election. the node is not available. The operations that the Service Manager performs depend on the type of node. You can configure more than one node to serve as a gateway. The Service Manager performs limited domain operations on a worker node. It runs as a service on Windows and as a daemon on UNIX. A gateway node can run application services. Nodes During installation. The functions that the Service Manager performs on a node depend on the type of node. One node acts as the gateway at any given time. Services can continue running despite temporary network or hardware failures. The Service Manager on the master gateway node performs all domain operations on the master gateway node. and it can serve as a master gateway node. That node is called the master gateway. the domain cannot accept service requests. When you start Informatica services. It starts and stops services and service processes based on requests from clients. Service Manager The Service Manager is a service that manages all domain operations. The Service Manager running on any other node performs some domain functions on that node. A node can be a gateway node or a worker node. If the master gateway node becomes unavailable. The Service Manager on each node starts application services configured to run on that node. Each node in the domain runs a Service Manager that manages domain operations on that node. You can also generate and upload node diagnostics to the Configuration Support Manager and review information such as available EBFs and Informatica recommendations. If the Service Manager is not running. you add the installation machine to the domain as a node. The Service Manager performs functions on each node to support the domain. Gateway Nodes A gateway node is any node that you configure to serve as a gateway for the domain. you start the Service Manager. For example. The Service Managers running on other gateway nodes perform limited domain operations on those nodes. the Service Manager on other gateway nodes elect another master gateway node.If you have the PowerCenter high availability option. A worker node can run application services. you can scale services and eliminate single points of failure for services. 2 Chapter 1: Understanding Domains . If you configure one node to serve as the gateway and the node becomes unavailable. The master gateway node is the entry point to the domain. It also directs service requests to application services. It runs within Informatica services. The Service Manager runs on each node. ¨ Domain support. the Service Manager running on the master gateway node performs all domain functions on that node. The Service Manager uses TCP/IP to communicate with the application services. Worker Nodes A worker node is any node not configured to serve as a gateway. but it cannot serve as a gateway. The Service Manager runs on all nodes in the domain to support application services and the domain: ¨ Application service support. You can add multiple nodes to a domain.

The Service Manager registers license information and verifies license information when you run application services. updates. Domain authorization occurs on the master gateway node. The Service Manager authenticates users who log in to application clients. The Service Manager provides accumulated log events from each service in the domain and for sessions and workflows. Authentication occurs on the master gateway node. and for service process failover for services on the domain. You subscribe to alerts to receive notification for node failure and master gateway election on the domain. When you subscribe to alerts. To perform the logging function. It also manages the creation of roles and the assignment of roles and privileges to native and LDAP users and groups. and publishes run-time statistics for integration objects in the Model repository. The Service Manager manages node configuration metadata in the domain. Domain configuration occurs on the master gateway node. the Service Manager runs a Log Manager and a Log Agent. The Service Manager persists. and permissions assigned to the user. The Log Manager runs on the master gateway node. The Service Manager manages the native and LDAP users and groups that can log in to application clients. Authentication Authorization Domain Configuration Node Configuration Licensing Logging User Management Monitoring Application Services Application services represent server-based functionality. The Service Manager manages the domain configuration metadata. The Service Manager stores the monitoring configuration in the Model repository. roles. you receive notification emails. User management occurs on the master gateway node.The following table describes the domain functions that the Service Manager performs: Function Alerts Description The Service Manager sends alerts to subscribed users. Application services include the following services: ¨ Analyst Service Application Services 3 . The Service Manager authorizes user requests for domain objects based on the privileges. Licensing occurs on the master gateway node. Some application services authorize user requests for other objects. The Log Agent runs on all nodes where the PowerCenter Integration Service runs. Node configuration occurs on all nodes in the domain. Requests can come from the Administrator tool. retrieves.

the Informatica Analyst application. configure a service to run on one node. If you have the high availability option. the Service Manager assigns a port number from the range of port numbers assigned to the node. The Content Management Service also provides Developer tool transformations with information about the address reference data and identity populations installed in the file system. The Analyst Service has connections to a Data Integration Service. 4 Chapter 1: Understanding Domains . Analyst Service The Analyst Service is an application service that runs the Informatica Analyst application in the Informatica domain. It provides reference data information to the Data Integration Service and to the Developer tool.¨ Content Management Service ¨ Data Director Service ¨ Data Integration Service ¨ Metadata Manager Service ¨ Model Repository Service ¨ PowerCenter Integration Service ¨ PowerCenter Repository Service ¨ PowerExchange Listener Service ¨ PowerExchange Logger Service ¨ Reporting Service ¨ Reporting and Dashboards Service ¨ SAP BW Service ¨ Web Services Hub When you configure an application service. If you assign multiple nodes. The Analyst Service manages the connections between service components and the users that have access to Informatica Analyst. You can create and recycle an Analyst Service in the Informatica domain to access the Analyst tool. you designate a node to run the service process. You can use the Administrator tool to administer the Analyst Service. You can subscribe to alerts to receive notification in the event of a service process failover. Content Management Service The Content Management Service is an application service that manages reference data. the service will not start. Model Repository Service. Designate the primary node to run the service. When a service process runs. The Content Management Service provides reference data properties to the Data Integration Service. For example. the service runs on a backup node. staging database. and a flat file cache location. the PowerCenter Integration Service can run multiple service processes at a time when you run it on a grid. The service process is the runtime representation of a service running on a node. The service type determines how many service processes can run at a time. The Developer tool displays the installed identity populations in the Match transformation and Comparison transformation. The Data Integration Service uses these properties when it runs mappings that require address reference data. You can launch the Analyst tool from the Administrator tool. If you do not have the high availability option. All other nodes are backup nodes for the service. The Developer tool displays the installed address reference datasets in the Content Status view within application preferences. If the primary node is not available. you can run a service on multiple nodes.

When you start a command from the command line or an external client to run SQL data services and mappings in an application. web services. If you have the high availability option. The Data Director Service connects to a Data Integration Service. Use Metadata Manager to browse and analyze metadata from disparate source repositories. the task fails if any service process or node becomes unavailable. The Model repository is a relational database that stores the metadata for projects created in Informatica Analyst and Informatica Designer. you can run multiple Model Repository Services on the same node. the command sends the request to the Data Integration Service. The Metadata Manager Service is not a highly available service. Data Integration Service The Data Integration Service is an application service that performs data integration tasks for Informatica Analyst. you can run multiple Metadata Manager Services on the same node. However. When you configure the service to run on a grid. Data integration tasks include previewing data and running profiles. A data analyst uses Informatica Data Director for Data Quality to perform manual review and update operations in database tables. browse. data modelling. You configure a Human Task Service module in the Data Integration Service so that the Data Integration Service can start a Human task in a workflow. If you do not have the high availability option. you can specify where you want it to run: ¨ On a grid. PowerCenter Integration Service The PowerCenter Integration Service runs PowerCenter sessions and workflows. SQL data services. business intelligence. The Model repository also stores run-time and configuration information for applications that are deployed to a Data Integration Service. Metadata Manager Service The Metadata Manager Service is an application service that runs the Metadata Manager application and manages connections between the Metadata Manager components. it can run on multiple nodes at a time. However. You can configure the Metadata Manager Service to run on only one node. data integration.Data Director Service The Data Director Service is an application service that runs the Informatica Data Director for Data Quality web application in the Informatica domain. When you configure the PowerCenter Integration Service. failover and recovery is available if a service process or node becomes unavailable. it automatically restarts on the same node. and mappings. The PowerCenter Integration Service dispatches tasks to available nodes assigned to the grid. and analyze metadata from application. You can load. A data analyst logs in to Informatica Data Director for Data Quality when assigned an instance of a Human task. and relational metadata sources. Informatica Developer. A Human task is a task in a workflow that specifies user actions in an Informatica application. Application Services 5 . Model Repository Service The Model Repository Service is an application service that manages the Model repository. If the Model Repository Service fails. The Model Repository Service is not a highly available service. You can configure the Model Repository Service to run on one node. and external clients.

a new process starts on the same node. Use the Administrator tool to manage the service and view service logs. create the data sources in Data Analyzer. you can run the Logger Service on multiple nodes. Reporting Service The Reporting Service is an application service that runs the Data Analyzer application in an Informatica domain. you can run the Listener Service on multiple nodes. and Windows. Use the Admnistrator tool to manage the service and view service logs. By default. It retrieves. The Reporting Service is not a highly available service. and updates metadata in the repository database tables. Reporting and Dashboards Service You can create the Reporting and Dashboards Service from Informatica Administrator. If you want a Reporting Service to point to different data sources. The PowerExchange Logger captures change data from a data source and writes the data to PowerExchange Logger log files. PowerExchange Logger Service The Logger Service is an application service that manages the PowerExchange Logger for Linux. or Metadata Manager Reports. it fails over to a backup node. 6 Chapter 1: Understanding Domains . If the service process fails or the node becomes unavailable. If the primary node is not available. PowerCenter Repository Service The PowerCenter Repository Service manages the PowerCenter repository. If the service process fails or the node becomes unavailable. the service process runs on the primary node. you can configure the service to run on primary and backup nodes. By default. The PowerCenter Integration Service connects to the PowerExchange Listener through the Listener Service. If the service process fails. If you have the PowerCenter high availability option. it runs on a backup node.¨ On nodes. However. You can also run other reports within your organization. If the Listener Service process fails on the primary node. The PowerExchange Listener manages communication between a PowerCenter or PowerExchange client and a data source for bulk data movement and change data capture. you can run multiple Reporting Services on the same node. You can use the service to create and run reports from the JasperReports application. it fails over to a backup node. a service process starts on one of the backup nodes. If you have the high availability option. inserts. you can configure the service to run on multiple nodes. PowerExchange Listener Service The PowerExchange Listener Service is an application service that manages the PowerExchange Listener. If the Logger Service process fails on the primary node. If the node becomes unavailable. If you have the PowerCenter high availability option. If you do not have the high availability option. you can configure the service to run on one node. If you have the high availability option. JasperReports Server builds on JasperReports and forms a part of the Jaspersoft Business Intelligence suite of products. Data Profiling Reports. the service fails over to another node. UNIX. JasperReports is an open source reporting library that users can embed into any Java application. Configure a Reporting Service for each data source you want to run reports against. You log in to Data Analyzer to create and run reports on data in a relational database or to run the following PowerCenter reports: PowerCenter Repository Reports. it runs on the primary node. the service fails.

Web Services Hub The Web Services Hub receives requests from web service clients and exposes PowerCenter workflows as services. The security domain that you select determines the authentication method that the Service Manager uses to authenticate your user account: ¨ Native. It runs within the Service Manager. and security domain. and PowerCenter Client. The Web Services Hub does not run an associated service process. Authentication When you log in to an application client. the Service Manager encrypts the password. When you log in to an application client as a native user. ¨ Lightweight Directory Access Protocol (LDAP). Informatica Analyst. The Service Manager and application services control user security by performing the following functions: Encryption When you log in to an application client. The first time you log in to an application client. The SAP BW Service is not highly available. You can configure it to run on one node. the Service Manager passes your user name and password to the external LDAP directory service for authentication. Metadata Manager. Application clients include Data Analyzer. User Security The Service Manager and some application services control user security in application clients. you enter a user name. password. Authentication The Service Manager authenticates users who log in to application clients. Informatica uses AES encryption with multiple 128-bit keys to encrypt passwords and stores the encrypted passwords in the domain configuration database. When you log in to an application client as an LDAP user. the Service Manager and some application services authorize the request based on your privileges.SAP BW Service The SAP BW Service listens for RFC requests from SAP NetWeaver BI and initiates workflows to extract from or load to SAP NetWeaver BI. Authorization When you request an object in an application client. Informatica Administrator. roles. the Service Manager authenticates your user name and password against the user accounts in the domain configuration database. and permissions. Configure HTTPS to encrypt passwords sent to the Service Manager from application clients. Informatica Developer. the Service Manager authenticates your user account based on your user name and password or on your user authentication token. Encryption Informatica encrypts passwords sent from application clients to the Service Manager. User Security 7 . A security domain is a collection of user accounts and groups in an Informatica domain.

The authentication token contains your user name.Single Sign-On After you log in to an application client. ¨ You add or remove native users or groups. The first time the Service Manager authenticates your user account. When you launch one application client from another one. the application client passes the authentication token to the next application client. The next application client sends the authentication token to the Service Manager for user authentication. The Service Manager periodically renews the authentication token before the expiration time. ¨ The Service Manager synchronizes the list of LDAP users and groups in the domain configuration database with the list of users and groups in the LDAP directory service. and an expiration time. and permission assignments. the Service Manager allows you to launch another application client or to access multiple repositories within the application client. 8 Chapter 1: Understanding Domains . Authorization The Service Manager authorizes user requests for domain objects. For example. Requests can come from the Administrator tool. role. When you request an object in an application client. the Model Repository Service authorizes your request based on your privilege. it creates an encrypted authentication token for your account and returns the authentication token to the application client. the application service stores the permission assignments with the user and group information in the appropriate repository. The following application services authorize user requests for other objects: ¨ Data Integration Service ¨ Metadata Manager Service ¨ Model Repository Service ¨ PowerCenter Repository Service ¨ Reporting Service When you create native users and groups or import LDAP users and groups. if you try to edit a project in Informatica Developer. When you assign permissions to users and groups in an application client. security domain. You do not need to log in to the additional application client or repository. or Reporting Service. Model Repository Service. the Service Manager stores the information in the domain configuration database into the following repositories: ¨ Data Analyzer repository ¨ Model repository ¨ PowerCenter repository ¨ PowerCenter repository for Metadata Manager The Service Manager synchronizes the user and group information between the repositories and the domain configuration database when the following events occur: ¨ You restart the Metadata Manager Service. the application client sends the authentication token to the Service Manager for user authentication. the appropriate application service authorizes your request. When you access multiple repositories within an application client. PowerCenter Repository Service.

The migration of an application service or task to another node when the node running the service process becomes unavailable. Manual recovery is not part of high availability. ¨ Failover. You can also manually recover PowerCenter Integration Service workflows and sessions. The automatic completion of tasks after a service is interrupted. ¨ Recovery. The ability of application services to tolerate transient network failures until either the resilience timeout expires or the external system failure is fixed. High Availability 9 . Automatic recovery is available for PowerCenter Integration Service and PowerCenter Repository Service tasks.High Availability High availability is an option that eliminates a single point of failure in a domain and provides minimal service interruption in the event of failure. High availability consists of the following components: ¨ Resilience.

In the Address field. change your password the first time you log in to the Administrator tool. The Service Manager uses the user password associated with a worker node to authenticate the node in the domain. 1. Open Microsoft Internet Explorer or Mozilla Firefox. Enter the user name and password. 2. The Service Manager cannot update nodes that are not running.CHAPTER 2 Managing Your Account This chapter includes the following topics: ¨ Managing Your Account Overview. Note: For an LDAP user account. If you have a native user account. 3. the Service Manager updates the password when the nodes restart. 11 ¨ Editing Preferences. Logging In To log in to the Administrator tool. you can change your password at any time. 12 Managing Your Account Overview Manage your account to change your password or edit user preferences. For nodes that are not running. If someone else created your user account. User preferences do not affect the options that appear when another user logs in to the Administrator tool. User preferences control the options that appear in the Administrator tool when you log in. change the password in the LDAP directory service. 10 ¨ Logging In. 10 ¨ Changing Your Password. you must have a user account and the Access Informatica Administrator domain privilege. 10 . If you change a user password that is associated with one or more worker nodes. enter the following URL for the Administrator tool login page: http://<host>:<port>/administrator The Administrator tool login page appears. the Service Manager updates the password for each worker node. 12 ¨ Preferences.

If the Informatica domain contains an LDAP security domain. accept the certificate. change the password the first time you log in to the Administrator tool. Changing Your Password 11 . contact the Informatica domain administrator. select Native or the name of a specific security domain. enter the current password in the Current Password box. the Service Manager updates the password for each worker node. The Change Password dialog box appears. the host name in the Administrator tool URL is equal to the host name of the elected master gateway node. In the Administrator tool header area. <host>:<port> represents the host name of the master gateway node and the Administrator tool port number. click OK. You configure the Administrator tool port when you define the domain. You can define the domain during installation or by running the infasetup DefineDomain command line program. The Security Domain box appears when the Informatica domain contains an LDAP security domain.4. For a user account created by someone else. For nodes that are not running. If you enter the domain port instead of the Administrator tool port in the URL. the browser is directed to the Administrator tool port. Informatica Administrator URL In the Administrator tool URL. Note: If the domain fails over to a different master gateway node. The Service Manager cannot update nodes that are not running. Then. a warning message appears. the URL redirects to the following HTTPS enabled site: https://<host>:<https port>/administrator If the node is configured for HTTPS with a keystore that uses a self-signed certificate. 2. 5. Changing Your Password Change the password for a native user account at any time. and the new password in the New Password and Confirm New Password boxes. If you do not know the security domain to which your user account belongs. you can enter the following URL. the Service Manager updates the password when the nodes restart. 1. If you do not use the Internet Explorer Enhanced Security Configuration. In the Change Password dialog box. Click Log In. If you change a user password that is associated with one or more worker nodes. To enter the site. and the browser is directed to the full URL for the login page: http://<host>:<port> If you configure HTTPS for the Administrator tool. click Manage > Change Password.

click Manage > Preferences. Use custom properties only if Informatica Global Customer Support instructs you to. In the Administrator tool header area. Displays custom properties in the contents panel when you click an object in the Navigator. Preferences Your preferences determine the options that appear in the Administrator tool when you log in. The Edit Preferences dialog box appears. The following table describes the options that you can configure for your preferences: Option Subscribe for Alerts Description Subscribes you to domain and service alerts. You must have a valid email address configured for your user account. Show Custom Properties 12 Chapter 2: Managing Your Account . Your preferences do not affect the options that appear when another user logs in to the Administrator tool. Default is No. 2. 1. Click Edit. You use custom properties to configure Informatica behavior for special cases or to increase performance. Hide the custom properties to avoid inadvertently changing the values. The Preferences window appears.Editing Preferences Edit your preferences to determine the options that appear in the Administrator tool when you log in.

21 ¨ Logs Tab. Manage logs. user permissions. View the status of profile jobs. 14 ¨ Domain Tab . 21 ¨ Reports Tab. Log out of the Administrator tool. The Administrator tool has the following header items: ¨ Log out. 22 ¨ Monitoring Tab. and domain reports. Manage users. ¨ Security administrative tasks. Manage users. and privileges. Access help for the current tab. scorecard jobs. and licenses.Connections View. Monitor jobs and applications that run on the Data Integration Service. preview jobs. database connections. 23 Using Informatica Administrator Overview Informatica Administrator is the administration tool that you use to administer the Informatica domain and Informatica security. ¨ Reports. nodes. roles. groups. and privileges. mapping jobs. operating system profiles. View log events for the domain and services within the domain. Generate and upload node diagnostics. folders. grids. ¨ Monitoring. ¨ Manage. groups. Run a Web Services Report or License Management Report. 13 . ¨ Logs. domain objects. Use the Administrator tool to complete the following types of tasks: ¨ Domain administrative tasks.Services and Nodes View. Domain objects include application services. and SQL data services for each Data Integration Service. roles. 14 ¨ Domain Tab . Manage your account. 13 ¨ Domain Tab Overview. The Administrator tool has the following tabs: ¨ Domain.CHAPTER 3 Using Informatica Administrator This chapter includes the following topics: ¨ Using Informatica Administrator Overview. View and edit the properties of the domain and objects within the domain. ¨ Help. ¨ Security. 22 ¨ Security Tab.

you can delete the object. View and manage connections.Domain Tab Overview On the Domain tab.Services and Nodes View The Services and Nodes view shows all application services and nodes defined in the domain. The Services and Nodes view has the following components: Navigator Appears in the left pane of the Domain tab.Connections View” on page 21 Domain Tab . you can view information about the domain and view and manage objects in the domain. Select an application service to view information about the service and its processes. ¨ Folders.Services and Nodes View” on page 14 ¨ “Domain Tab . which is the highest object in the Navigator hierarchy. View and manage application services and nodes. You can view one domain. you shut down or view logs for the domain. Create a license on the Domain tab based on a license key file provided by Informatica. or refresh the object. An application service represents server-based functionality. You can configure the appearance of these views. Select a license to view services assigned to the license. ¨ Grids. grid. ¨ Licenses. you can create a folder. Use folders to organize domain objects in the Navigator. ¨ Connections. You assign resources to nodes and configure service processes to run on nodes. You can select the following views: ¨ Services and Nodes. service. Select a grid to view nodes assigned to the grid. or license. Create a grid to run the Data Integration Service or PowerCenter Integration Service on multiple nodes. move it to a folder. Contents panel Appears in the right pane of the Domain tab and displays information about the domain or domain object that you select in the Navigator. The Navigator displays the following types of objects: ¨ Domain. The contents that appear and the tasks you can complete on the Domain tab vary based on the view that you select. ¨ Application services. Actions menu on the Domain tab When you select the domain in the Navigator. Actions menu in the Navigator When you select the domain in the Navigator. Select a folder to view information about the folder and the objects in the folder. ¨ Nodes. 14 Chapter 3: Using Informatica Administrator . RELATED TOPICS: ¨ “Domain Tab . When you select a domain object in the Navigator. A node represents a machine in the domain. node.

You can also add folders. ¨ Diagnostics view. You can also recycle application services. or edit customer portal login details. and grids. When you select the domain in the Navigator. Click a node to see its name. status. version. which you use to organize domain objects. To view properties for an application service. you can add a node. nodes. and grids in the domain. Click an application service to see its name. or license to the domain. Nodes. you can remove a node association. ¨ Properties view. To view the dependencies among application services. manage the repository domain. In the Actions menu in the Navigator. right-click an object and click View Properties. or shut down the node. the contents panel shows the following views and buttons. recalculate the CPU profile benchmark. status. You can view statuses of application services and nodes and information about grids. you can add an incremental key to the license. view logs. and Grids” on page 43 Folders You can use folders in the domain to organize objects and to manage security. It is the highest object in the Navigator hierarchy. or access help on the current view. and unavailable. Domain Tab . View or edit domain resilience properties. and view logs. RELATED TOPICS: ¨ “Viewing Dependencies for Application Services. disabled. and view properties about domain objects. application service. The statuses are available. ¨ Permissions view. the number of service processes running on the node. and the name of any grids to which the node belongs. and the names of the nodes in the grid. the Overview view shows an abbreviation of each domain object's name. The contents panel shows the object properties. Domain You can view one domain in the Services and Nodes view on the Domain tab.Services and Nodes View 15 . When you select a service in the Navigator. nodes. you can shut down. grid.When you select a node in the Navigator. which enable you to complete the following tasks: ¨ Overview view. nodes. The View Dependency graph appears. You can also view dependencies among application services. ¨ Plug-ins view. Click a grid to see the name of the grid. When you select a license in the Navigator. generate and upload node diagnostics to Customer Support Manager. and the statuses of its individual processes. organized by object type. node. right-click a service and click Recycle Service. ¨ View Logs for Domain button. View plug-ins registered in the domain. Click the Hide Details button to show abbreviations of the object names. View node diagnostics. right-click an object and click View Dependency. By default. View or edit group and user permissions on the domain. View all application services. ¨ Resources view. the number of service processes running in the grid. Click the Show Details button to show the full names of the objects. View logs for the domain and services within the domain. notify users. view back up files in or back up the repository contents. or grid. In the Actions menu on the Domain tab. you can recycle or disable the service. View available resources for each node in the domain. and grids. To recycle an application service.

logging. View and edit service process properties on each assigned node. Manage general. View or edit group and user permissions on the folder. ¨ Properties view. ¨ Properties view. When you select a Content Management Service in the Navigator. services. Analyst tool. In the Actions menu in the Navigator. Application Services Application services are a group of services that represent Informatica server-based functionality. licenses. View the status of the service and the service process for each node. In the Services and Nodes view on the Domain tab. ¨ Permissions view. View or edit group and user permissions on the Content Management Service. Manage the service. When you select an Analyst Service in the Navigator. View and edit service process properties on each assigned node. or access help on the current tab. refresh the contents on the Domain tab. the contents panel displays the following information: ¨ Service and service process status. Model Repository Service. data integration. View or edit group and user permissions on the Analyst Service. ¨ Properties view. 16 Chapter 3: Using Informatica Administrator .Folders can contain nodes. data integration. ¨ Actions menu. View the status of the service and the service process for each node. model repository. provides the Data Integration Service with address reference data properties. Displays services in the folder and the nodes where the service processes run. and a flat file cache location. Content Management Service Manages reference data. ¨ Permissions view. the Navigator opens to display the objects in the folder. the contents panel displays the following information: ¨ Service and service process status. you can delete the folder. Displays the name and description of the folder. The contents panel also displays the URL of the Analyst Service instance. you can create and manage the following application services: Analyst Service Runs Informatica Analyst in the Informatica domain. and other folders. Manage the service and repository contents. The contents panel displays the following information: ¨ Overview view. The Analyst Service connects to a Data Integration Service. logging. ¨ Actions menu. and provides Informatica Developer with information about the address reference data and identity populations installed in the file system. ¨ Permissions view. staging database. metadata manager. grids. When you select a folder in the Navigator. You can create and recycle the Analyst Service in the Informatica domain to access the Analyst tool. and custom properties. move the folder into another folder. ¨ Processes view. staging database. ¨ Processes view. You can launch the Analyst tool from the Administrator tool. and custom properties. Manage general. The Analyst Service manages the connections between service components and the users that have access to Informatica Analyst.

¨ Properties view. ¨ Associated Services view. View the status of the service and the service process for each node. ¨ Actions menu. View and edit service process properties on each assigned node. The contents panel also displays the URL of the Metadata Manager Service instance. the application sends requests to the Data Integration Service to perform the data integration tasks. Manage the service and repository contents. Data Integration Service Completes data integration tasks for Informatica Analyst. the contents panel displays the following information: ¨ Service and service process status. such as Informatica Developer. ¨ Properties view. Metadata Manager Service Runs the Metadata Manager application and manages connections between the Metadata Manager components. Manage the service. The Model repository stores metadata created by Informatica products. Manage general. and external clients. A data analyst logs in to Informatica Data Director for Data Quality when assigned an instance of a Human task. SQL data services. ¨ Properties view. logging. ¨ Processes view. profiling. ¨ Permissions view. ¨ Applications view. and mappings in Informatica Analyst or Informatica Developer. the contents panel displays the following information: ¨ Service and service process status. When you select a Data Director Service in the Navigator. View or edit group and user permissions on the Metadata Manager Service. Manage application properties. Model Repository Service Manages the Model repository. ¨ Permissions view. Manage the service and repository contents. and custom properties. View or edit group and user permissions on the Analyst Service. logging. Manage general. model repository. and custom properties. Data Integration Service. Domain Tab . When you select a Metadata Manager Service in the Navigator. The Model repository enables collaboration among the products. View the status of the service and the service process for each node. the contents panel displays the following information: ¨ Service and service process status. ¨ Processes view. When you preview or run data profiles. Informatica Developer. Back up applications. ¨ Actions menu. When you start a command from the command line or an external client to run SQL data services and mappings in an application. Set the default deployment option. View and configure the Integration Service associated with the Metadata Manager Service. When you select a Data Integration Service in the Navigator. and Informatica Administrator. Human task. Informatica Analyst. Start and stop applications and SQL data services. View or edit Metadata Manager properties. View and edit service process properties on each assigned node. data object cache. ¨ Actions menu. The contents panel also displays the URL of the Data Director Service instance.Data Director Service Runs the Informatica Data Director for Data Quality web application.Services and Nodes View 17 . View the status of the service and the service process for each node. the command sends the request to the Data Integration Service. logical data object and virtual table cache.

View and terminate repository connections and object locks. ¨ Actions menu. Select a PowerCenter Repository Service in the Navigator to access information about the service. The service status also displays the operating mode for the PowerCenter Repository Service. PowerCenter Repository Service Manages the PowerCenter repository. Manage the contents of the repository and perform other administrative tasks. PowerExchange Listener Service Runs the PowerExchange Listener. View and edit service process properties on each assigned node. View the status of the service and the service process for each node. ¨ Processes view. View the status of the service and the service process for each node. the contents panel displays the following information: ¨ Service and service processes status. View or edit Integration Service properties. the contents panel displays the following information: ¨ Service and service process status. such as viewing logs or enabling and disabling the service. Status of the service and service process for each node. ¨ Actions menu. ¨ Processes view. The contents panel also displays a message if the repository has no content or requires upgrade. Manage general and advanced properties. repository database. View and edit service process properties on each assigned node. ¨ Properties view. View or edit the service process properties on each assigned node. and updates metadata in the repository database tables. The contents panel also displays the URL of the PowerExchange Listener instance. View or edit group and user permissions on the Integration Service. ¨ Associated Repository view. Contains actions that you can perform on the Listener Service. View or edit Listener Service properties. View or edit the repository associated with the Integration Service. ¨ Actions menu. ¨ Permissions view. and custom properties. inserts. search. ¨ Connections and Locks view. When you select a Listener Service in the Navigator. node assignments. ¨ Plug-ins view. the contents panel displays the following information: ¨ Service and service process status. 18 Chapter 3: Using Informatica Administrator . View or edit group and user permissions on the PowerCenter Repository Service. and database properties. When you select a PowerCenter Repository Service in the Navigator.When you select a Model Repository Service in the Navigator. View the status of the service and the service process for each node. Manage general. ¨ Properties view. ¨ Processes view. ¨ Permissions view. ¨ Actions menu. Manage the service. PowerCenter Integration Service Runs PowerCenter sessions and workflows. View and manage registered plug-ins. ¨ Properties view. When you select a PowerCenter Integration Service in the Navigator. It retrieves. the contents panel displays the following information: ¨ Service and service process status. ¨ Properties view. Manage the service and repository contents. Select a PowerCenter Integration Service in the Navigator to access information about the service.

such as viewing logs or enabling and disabling the service. and Windows. When you select a Reporting Service in the Navigator. The Reporting Service properties such as the data source properties or the Data Analyzer repository properties. ¨ Permissions view. View or edit the Integration Service associated with the SAP BW Service. Web Services Hub A web service gateway for external clients. Domain Tab . ¨ Processes view. Reporting and Dashboards Service Runs reports from the JasperReports application. You log in to Data Analyzer to create and run reports on data in a relational database or to run the following PowerCenter reports: PowerCenter Repository Reports. ¨ Properties view. It processes SOAP requests from web service clients that want to access PowerCenter functionality through web services. When you select a Logger Service in the Navigator. ¨ Actions menu. ¨ Actions menu. UNIX. The contents panel also displays the URL of the PowerExchange Logger instance. You can edit some of these properties. the contents panel displays the following information: ¨ Service and service process status. View or edit the directory of the BWParam parameter file. View or edit Web Services Hub properties.Services and Nodes View 19 . ¨ Properties view. the contents panel displays the following information: ¨ Service and service process status. Status of the service and service process for each node. Manage general properties and node assignments. Contains actions that you can perform on the Logger Service. View or edit group and user permissions on the Reporting Service. Manage the service and repository contents. ¨ Properties view. ¨ Properties view. Select an SAP BW Service in the Navigator to access properties and other information about the service. View or edit Logger Service properties. ¨ Actions menu. ¨ Associated Integration Service view. You can also run other reports within your organization. the contents panel displays the following information: ¨ Service and service process status. View the status of the service and the service process. Status of the service and service process for each node. View the status of the service and the service process. Data Profiling Reports. ¨ Permissions view.PowerExchange Logger Service Runs the PowerExchange Logger for Linux. When you select a Web Services Hub in the Navigator. the contents panel displays the following information: ¨ Service and service process status. Manage the service. Reporting Service Runs the Data Analyzer application in an Informatica domain. When you select an SAP BW Service in the Navigator. SAP BW Service Listens for RFC requests from SAP BW and initiates workflows to extract from or load to SAP BW. View or edit group and user permissions on the SAP BW Service. Web service clients access the PowerCenter Integration Service and PowerCenter Repository Service through the Web Services Hub. The contents panel also displays the URL of the Data Analyzer instance. or Metadata Manager Reports.

and licensed options. When you select a node in the Navigator. When you select a license in the Navigator. the contents panel displays the following information: ¨ Properties view. In the Actions menu in the Navigator. View or edit node properties. or shut down the node. ¨ Options view. or access help on the current tab. In the Actions menu in the Navigator. View the status of processes configured to run on the node. When you run a job on a grid. 20 Chapter 3: Using Informatica Administrator . or access help on the current tab. refresh the contents on the Domain tab. you can delete the grid. View or edit node assignments to a grid. You can also edit the license description. View or edit the services assigned to the license. Nodes A node is a logical representation of a physical machine in the domain. you assign resources to nodes and configure service processes to run on nodes. When you select a grid in the Navigator.¨ Associated Repository view. View the PowerCenter Repository Services associated with the Web Services Hub. repositories. when you run a profile on a grid. View or edit resources assigned to the node. you can remove the node association. Manage the service. On the Domain tab. ¨ Permissions view. ¨ Assigned Services view. For example. move the node to a folder. Licenses You create a license object on the Domain tab based on a license key file provided by Informatica. View or edit group and user permissions on the grid. View the status of the node. ¨ Resources view. such as the repository backup directory or range of port numbers for the processes that run on the node. the Integration Service distributes the processing across multiple nodes in the grid. View the licensed PowerCenter options. You assign nodes to the grid in the Services and Nodes view on the Domain tab. such as supported platforms. the Data Integration Service segments the work into multiple jobs and assigns each job to a node in the grid. ¨ Permissions view. you can delete the node. move the grid to a folder. ¨ Permissions view. ¨ Processes view. ¨ Actions menu. View license properties. the contents panel displays the following information: ¨ Properties view. In the Actions menu on the Domain tab. you can assign services to the license. ¨ Properties view. View or edit group and user permissions on the node. View or edit group and user permissions on the Web Services Hub. Grids A grid is an alias assigned to a group of nodes that run PowerCenter Integration Service or Data Integration Service jobs. After you create the license. recalculate the CPU profile benchmark. refresh the contents on the Domain tab. the contents panel displays the following information: ¨ Node status.

or search for specific connections. ¨ Service log. ¨ Permissions view.Connections View The Connections view shows the domain and all connections in the domain. Domain log events are log events generated from the domain functions the Service Manager performs. View or edit group or user permissions on the connection. When you select a connection in the Navigator. The Connections view has the following components: Navigator Appears in the left pane of the Domain tab and displays the domain and the connections in the domain. move the license to a folder.Connections View 21 . Logs Tab The Logs tab shows logs. Actions menu in the Navigator When you select the domain in the Navigator. When you select the domain in the Navigator.¨ Permissions view. you can delete the connection. you can create a connection. the contents panel displays information about the connection and lets you complete tasks for the connection. depending on which of the following views you select: ¨ Properties view. Domain Tab . View or edit connection properties. In the contents panel. you can filter or sort connections. you can delete the license. When you select a connection in the Navigator. View or edit user permissions on the license. you can edit direct permissions or assign permissions to the connection. Also. refresh the contents on the Domain tab. or access help on the current tab. View or edit pooling properties for the connection. you can view the following types of logs: ¨ Domain log. Service log events are log events generated by each application service. Contents panel Appears in the right pane of the Domain tab and displays information about the domain or the connection that you select in the Navigator. Actions menu on the Domain tab When you select a connection in the Navigator. On the Logs tab. In the Actions menu on the Domain tab. the Actions menu lets you test a connection. Domain Tab . ¨ Pooling view. In the Actions menu in the Navigator. the contents panel shows all connections in the domain. you can add an incremental key to a license.

¨ Details panel. If you select a folder in the Navigator. Appears in the right pane of the Monitoring tab. and workflows. Application components include deployed mappings. Reset the filter criteria. abort a selected job. purge. Integration objects include jobs. Run a report to monitor the usage of logical CPUs and PowerCenter Repository Services. and run-time reports about the integration objects. ¨ Contents panel. reset search filters. ¨ Web Services Report. and view logs for a selected object. deployed mappings. The Logs tab displays the following components for each type of log: ¨ Filter. Copy the log text of the selected rows. Contains options to save. If you select an application component in the Navigator. It also contains filter options. User Activity log events monitor user activity in the domain. ¨ Reset filter. ¨ Copy rows. Monitoring Tab On the Monitoring tab. applications. The Monitoring tab contains the following components: ¨ Navigator. Appears below the contents panel in some cases. On the Reports tab.¨ User Activity log. You run the report for a time interval. Configure filter options for the logs. ¨ Log viewer. ¨ Actions menu. ¨ Actions menu. Appears on the Monitoring tab. It contains information about the object that is selected in the Navigator. Appears in the left pane of the Monitoring tab and displays jobs. SQL data services. you can run the following domain reports: ¨ License Management Report. You run the report for a license. Run a report to analyze the performance of web services running on a Web Services Hub. Run a report to monitor the number of software options purchased for a license and the number of times a license exceeds usage limits. and workflows. logical data objects. Displays log events based on the filter criteria. 22 Chapter 3: Using Informatica Administrator . the contents panel lists all objects in the folder. The details panel allows you to view details about the object that is selected in the contents panel. web services. logical data objects. The Monitoring tab displays properties. and manage logs. Allows you to view context. Reports Tab The Reports tab shows domain reports. applications. and application components. you can monitor Data Integration Services and integration objects that run on the Data Integration Service. web services. run-time statistics. multiple views of information about the object appear in the contents panel.

You can use any of the following methods to manage groups. ¨ Contents panel. ¨ Navigator. delete. groups. For example. you can select a user in the Users section of the Navigator and drag the user to a native group in the Groups section. and move options available in the Actions menu. Select an object in the Navigator and click the Actions menu to create. In the Search section. Select a group to view the properties of the group. and the roles and privileges assigned to the group. Contains options to create or delete a group. or roles by name. You can include an asterisk (*) in a name to use a wildcard character in the search. Enter “*ad” to search for all objects ending with “ad”. When you select an object in the Navigator. The Search Results section appears and displays a maximum of 100 objects. to assign a user to a native group. Select an object and drag it to another section of the Navigator to assign the object to another object. users. Enter the name or partial name to search for. select whether you want to search for users. delete. ¨ Users section. enter “ad*” to search for all objects starting with “ad”. users. Select an object in the Search Results section to display information about the object in the contents panel. groups. 2. The contents panel displays properties and options based on the object selected in the Navigator and the tab selected in the contents panel. Search for users. or role. groups. users. Click Go. Select a role to view the properties of the role. and roles: ¨ Click the Actions menu. the users and groups that have the role assigned to them. or roles. the contents panel displays information about the object. and the roles and privileges assigned to the user. user. 4. ¨ Security Actions Menu. ¨ Roles section. The Navigator on the Security tab includes the following sections: ¨ Groups section. Using the Search Section Use the Search section to search for users. or roles. The Navigator appears in the left pane and display groups. For example. and roles. or move groups. and roles by name. or roles. and the privileges assigned to the role. You can also view users that have privileges for a service. ¨ Drag an object from one section to another section. 1. narrow your search criteria to refine the search results. Right-click an object in the Navigator to display the create.Security Tab You administer Informatica security on the Security tab of the Administrator tool. ¨ Right-click an object. users. Security Tab 23 . You can manage LDAP and operating system profiles. the groups the user belongs to. the users assigned to the group. Using the Security Navigator The Navigator appears in the contents panel of the Security tab. Each section of the Navigator includes an Actions menu to manage groups. The Security tab has the following components: ¨ Search section. 3. The Navigator provides different ways to complete a task. Search is not case sensitive. Select a user to view the properties of the user. If your search returns more than 100 objects.

Native authentication uses the Native security domain which contains the users and groups created and managed in the Administrator tool. the contents panel displays the following tabs: ¨ Overview. Groups A group is a collection of users and groups that can have the same privileges. Right-click a group and select Navigate to Item to display the group details in the contents panel. A security domain is a collection of user accounts and groups in an Informatica domain. the contents panel displays the following tabs: ¨ Overview. ¨ Privileges. LDAP authentication uses LDAP security domains which contain users and groups imported from the LDAP directory service. Displays the privileges and roles assigned to the group for the domain and for application services in the domain. Use keyboard shortcuts to move to different sections of the Navigator. Displays general properties of the group and users assigned to the group. you can select the Native folder in the Users section of the Navigator to display all native users in the contents panel. Use the Ctrl or Shift keys to select multiple users and drag the selected users to a native group in the Groups section of the Navigator. Users A user with an account in the Informatica domain can log in to the following application clients: ¨ Informatica Administrator ¨ PowerCenter Client ¨ Metadata Manager ¨ Data Analyzer ¨ Informatica Developer ¨ Informatica Analyst ¨ Jaspersoft The Users section of the Navigator organizes users into security domain folders. and permissions. Displays the privileges and roles assigned to the user for the domain and for application services in the domain. Right-click a user and select Navigate to Item to display the user details in the contents panel. A security domain is a collection of user accounts and groups in an Informatica domain. For example. roles. the contents panel displays all groups belonging to the security domain. Displays general properties of the user and all groups to which the user belongs. LDAP authentication uses LDAP security domains which contain users and groups imported from the LDAP directory service. Select multiple users or roles in the contents panel and drag them to the Navigator to assign the objects to another object. the contents panel displays all users belonging to the security domain. When you select a security domain folder in the Users section of the Navigator. 24 Chapter 3: Using Informatica Administrator . Native authentication uses the Native security domain which contains the users and groups created and managed in the Administrator tool. ¨ Privileges. ¨ Use keyboard shortcuts. The Groups section of the Navigator organizes groups into security domain folders. When you select a group in the Navigator.¨ Drag multiple users or roles from the contents panel to the Navigator. When you select a user in the Navigator. to assign multiple users to a native group. When you select a security domain folder in the Groups section of the Navigator.

Contains roles that you cannot edit or delete. Right-click a role and select Navigate to Item to display the role details in the contents panel. ¨ Custom Roles. On the Security page. ¨ Privileges. When you select a folder in the Roles section of the Navigator. the contents panel displays the following tabs: ¨ Overview. On the Security page. The Administrator tool includes some custom roles that you can edit and assign to users and groups.Roles A role is a collection of privileges that you assign to a user or group. The Roles section of the Navigator organizes roles into the following folders: ¨ System-defined Roles. edit. The following table lists the keyboard shortcuts for the Administrator tool: Shortcut Shift+Alt+G Task On the Security page. Privileges determine the actions that users can perform. and delete. You assign a role to users and groups for the domain and for application services in the domain. Displays the privileges assigned to the role for the domain and application services. the contents panel displays all roles belonging to the folder. Displays general properties of the role and the users and groups that have the role assigned for the domain and application services. Keyboard Shortcuts Use the following keyboard shortcuts to navigate to different components in the Administrator tool. When you select a role in the Navigator. Shift+Alt+U Shift+Alt+R Security Tab 25 . The Administrator role is a system-defined role. move to the Groups section of the Navigator. Contains roles that you can create. move to the Users section of the Navigator. move to the Roles section of the Navigator.

enable. and disable domain and service alerts for users. and shut down nodes. disable. ¨ Configure gateway nodes. 42 ¨ Domain Properties. 38 ¨ Domain Configuration Management. 45 Domain Management Overview An Informatica domain is a collection of nodes and services that define the Informatica environment. ¨ Manage nodes. Shut down the domain to complete administrative tasks on the domain. To manage the domain. ¨ Create folders. 31 ¨ Node Management. ¨ Shut down the domain. Assign privileges and permissions to users and groups. 30 ¨ User Security Management. You might also need to reset the database information for the domain configuration if it changes. Configure node properties. You might need to restore the domain configuration from a backup to migrate the configuration to another database user account. Use the Administrator tool to complete the following tasks: ¨ Manage alerts. Enable. ¨ Manage domain security. Configure. Enable. ¨ Manage user security. and remove application services. such as the backup directory and resources. you manage the nodes and services within the domain. and restart service processes. 26 ¨ Alert Management. 33 ¨ Gateway Configuration. disable. ¨ Manage application services. 38 ¨ Domain Tasks. 28 ¨ Domain Security Management. Configure nodes to serve as a gateway. Create folders to organize domain objects and manage security by setting permission on folders. 26 . 27 ¨ Folder Management. Configure secure communication between domain components.CHAPTER 4 Domain Management This chapter includes the following topics: ¨ Domain Management Overview. ¨ Manage domain configuration. Back up the domain configuration on a regular basis. 30 ¨ Application Service Management.

5. The Edit Preferences dialog box appears. If the email address or the SMTP configuration is not valid. users can subscribe to domain and service alerts. RELATED TOPICS: ¨ “SMTP Configuration” on page 48 Subscribing to Alerts After you complete the SMTP configuration. 2. complete the following tasks: ¨ Configure the SMTP settings for the outgoing email server. select the domain. Domain alerts provide notification about node failure and master gateway election. You can monitor the statuses of all application services and nodes. Configuring SMTP Settings You configure the SMTP settings for the outgoing mail server to enable alerts. click Edit. ¨ Configure domain properties. 2. 4. click Edit. 1. After you configure the SMTP settings. You can share metadata between domains when you register or unregister a local repository in the local Informatica domain with a global repository in another Informatica domain. 1. view dependencies among application services and nodes. Alert Management 27 . ¨ Subscribe to alerts. click the Properties view. SMTP properties for alerts. The Preferences page appears. all nodes and services must be in the same domain. In the Administrator tool. click Manage > Preferences. you can subscribe to alerts. Edit the SMTP settings and click OK. To use the alerts. and shut down the domain. Configure SMTP settings on the domain Properties view. In the Administrator tool header area. In the Navigator. Alert Management Alerts provide users with domain and service alerts. Service alerts provide notification about service process failover. To manage nodes and services through a single interface. For example. the Service Manager cannot deliver the alert notification. click the Domain tab. In the SMTP Configuration area of the. Verify that the domain administrator has entered a valid email address for your user account on the Security page. 3. 3. and domain resiliency properties. You cannot access multiple Informatica domains in the same Administrator tool window. In the User Preferences section. you can change the database properties. In the contents panel.¨ Complete domain tasks.

You can perform the following tasks with folders: ¨ View services and nodes. you can receive domain and service notification emails for certain events. you can create a folder called IntegrationServices and move all Integration Services to the folder. Folder Management Use folders in the domain to organize objects and to manage security. 28 Chapter 4: Domain Management . alert message [alert message]. licenses.4. ¨ The Log Manager logs alert notification delivery success or failure in the domain or service log. The following table lists the alert types and events for notification emails: Alert Type Domain Event Node Failure Master Gateway Election Service Service Process Failover Viewing Alerts When you subscribe to alerts. The service process on node [node01] for service [HR_811] terminated unexpectedly. the Log Manager writes the following message to the service log: ALERT_10009 Alert message [service process failover] of type [service] for object [HR_811] was successfully sent. The Service Manager sends alert notification emails based on your domain privileges and permissions. Select Subscribe for Alerts. such as Sales or Finance. Or. In the domain log. In the service logs. the Service Manager sends the following notification email to all alert subscribers with the appropriate privilege and permission on the service that failed: From: Administrator@<database host> To: Jon Smith Subject: Alert message of type [Service] for object [HR_811]. filter by Alerts as the category. For example. 5. You can review the domain or service logs for undeliverable alert notification emails. with error [error]. and other folders. services. When the Service Manager cannot send an alert notification email. search on the message code ALERT. Click a node or service name to access the properties for that node or service. the following message appears in the related domain or service log: ALERT_10004: Unable to send alert of type [alert type] for object [object name]. For example. you can track the alert status in the following ways: ¨ The Service Manager sends an alert notification email to all subscribers with the appropriate privilege and permission on the domain or service. Click OK. View all services in the folder and the nodes where they run. the user inherits permission on all objects in the folder. Folders can contain nodes. you might want to create folders to group all services for a functional area. Click OK. 6. When you assign a user permission on the folder. When a domain or service event occurs that triggers a notification. grids. You might want to use folders to group services by type. In addition.

In the Informatica tool. and click OK. Click OK. select an object. In the Navigator. On the Navigator Actions menu. select the domain or folder in which you want to create a folder. On the Navigator Actions menu. Location in the Navigator. When you move an object to a folder. Folder Management 29 . The name is not case sensitive and must be unique within the domain. 1. In the Select Folder dialog box. the moved folder becomes a child object of the folder where it resides. 1. Removing a Folder When you remove a folder. select a folder. folder users inherit permission on the object. 2. 2. Moving Objects to a Folder When you move an object to a folder. Edit the following properties: Node Property Name Description Name of the folder. 2. Create folders to group objects in the domain. you can delete the objects in the folder or move them to the parent folder. Confirm that you want to delete the folder. When you move a folder to another folder. The description cannot exceed 765 characters. folder users inherit permission on the object in the folder. Creating a Folder You can create a folder in the domain or in another folder. On the Navigator Actions menu. click New > Folder. ¨ Remove folders. You can delete the contents only if you have the appropriate privileges and permissions on all objects in the folder. you can delete the objects in the folder or move them to the parent folder. When you remove a folder. ¨ Move objects to folders. 3. select Delete. In the Informatica tool.<>|!()][ Description Path Description of the folder. click the Domain tab. the other folder becomes a parent of the moved folder. 4.¨ Create folders. select Move to Folder.:'"/?. In the Administrator tool. select a folder. 3. 4. click the Domain tab. When you move a folder to another folder. In the Navigator. It also cannot contain spaces or the following special characters: `~%^*+={}\. 3. Note: The domain serves as a folder when you move objects in and out of folders. In the Navigator. 1. It cannot exceed 80 characters or begin with @. click the Domain tab. 5. 4..

30 Chapter 4: Domain Management . Privileges determine the actions that users can complete on domain objects. For example. if a user has permission on a node. When you configure secure communication for one set of components. Choose to wait until all processes complete or to abort all processes. operating system profiles. you do not need to configure secure communication for any other set. However. but does not have the Manage Nodes and Grids privilege. the contents panel displays a message indicating that permission on the object is denied. and application services. To log in to the Administrator tool. Domain Security Management You can configure Informatica domain components to use the Secure Sockets Layer (SSL) protocol or the Transport Layer Security (TLS) protocol to encrypt connections with other components. the user can view the node properties but cannot configure. the user may also require permission to complete the action on a particular object. or remove the node. Click OK. Each method of configuring secure communication is independent of the other methods. Between the domain and external components You can configure secure communication between Informatica domain components and web browsers or web service clients. database connections. licenses. When you enable SSL or TLS for domain components. You can configure secure communication in the following ways: Between services within the domain You can configure secure communication between services within the domain. Domain objects include the domain. you ensure secure communication. If a user has the Access Informatica Administrator privilege and permission on an object.5. nodes. a user must have have the Access Informatica Administrator domain privilege. Permissions define the level of access a user has to a domain object. grids. shut down. a user has the Manage Services domain privilege which grants the user the ability to edit application services. 6. User Security Management You manage user security within the domain with privileges and permissions. For example. folders. then the user can view the object. A user with the Manage Services domain privilege and permission on the Development Repository Service but not on the Production Repository Service can edit the Development Repository Service but not the Production Repository Service. but does not have the domain privilege that grants the ability to modify the object type. Even if a user has the domain privilege to complete certain actions. If a user does not have permission on a selected object in the Navigator. the user also must have permission on the application service.

It is on standby to run in case of service failover. ¨ Remove an application service. all service processes run concurrently. You have disabled the service. ¨ Unavailable. The service is not available to process requests. ¨ Disabled. This can be a result of service processes being disabled or failing to start. A service does not start a disabled service process in any situation. A service can have the following states: ¨ Available. the service starts the service process on the primary node. You might want to disable the service process on a node if you need to shut down the node for maintenance. The service is available to process requests. You can disable a service to perform a management task. You have enabled the service and at least one service process is running. When a service is enabled. ¨ If the service is configured to run on a grid. By default. The service process is enabled but is not running because another sevice process is running as the primary service process. ¨ Configure the domain to restart service processes. Enabling and Disabling Services and Service Processes You can enable and disable application services and service processes in the Administrator tool. The following table describes the different states of a service process: Service Process State Running Standing By Process Configuration Description Enabled Enabled The service process is running on the node. You have enabled the service but there are no service processes running. If you run the PowerCenter Integration Service on a grid. but they remain enabled. Note: Service processes cannot have a standby state when the PowerCenter Integration Service runs on a grid. all associated service processes stop. Disabled Disabled Application Service Management 31 . the service starts service processes on all nodes. The state of a service depends on the state of the constituent service processes. The behavior of a service when it starts service processes depends on its configuration: ¨ If the service is configured for high availability. All backup nodes are on standby. When you disable a service. there must be at least one service process enabled and running for the service to be available. such as changing the data movement mode for a PowerCenter Integration Service. The service is enabled but the service process is stopped and is not running on the node.Application Service Management You can perform the following common administration tasks for application services: ¨ Enable and disable services and service processes. ¨ Troubleshoot problems with an application service. all service processes are enabled.

3. Default is 900. In the Properties view. you must disable it. Configuring Restart for Service Processes If an application service process becomes unavailable while a node is running. the domain tries to restart the process on the same node based on the restart options configured in the domain properties. select a service. If you do not disable the service. Default is 3. In the Navigator. 32 Chapter 4: Domain Management . In the contents panel. select the Processes view. Viewing Service Processes You can view the state of a service process on the Processes view of a service. Disable the service before you delete the service to ensure that the service is not running any processes. The Processes view displays the state of the processes. 1. The service and service process are enabled. 2. 2. 3. In the Administrator tool. but the service process could not start. In the Navigator. you may have to choose to wait until all processes complete or abort all processes when you delete the service. To view the state of a service process: 1. select the application service. Note: A service process will be in a failed state if it cannot start on the assigned node. click the Domain tab. click the Domain tab. The value must be greater than or equal to 1. Before removing an application service. In the Administrator tool. configure the following restart properties: Domain Property Maximum Restart Attempts Description Number of times within a specified period that the domain attempts to restart an application service process when it fails.Service Process State Stopped Failed Process Configuration Description Enabled Enabled The service is unavailable. Within Restart Period (sec) Removing Application Services You can remove an application service using the Administrator tool. the service does not restart. click the Domain tab. 2. You can view the state of all service processes on the Overview view of the domain. In the Administrator tool. If a service fails to start after the specified number of attempts within this period of time. 1. select the domain. Maximum period of time that the domain spends attempting to restart an application service process when it fails. In the Navigator.

3. choose to wait until all processes complete or abort all processes. and you can view and edit its properties. After you define a node. the Domain log will display the environment variables that the service is using. In the warning message that appears. verify that all running processes are stopped. Defining and Adding Nodes You must define a node and add it to the domain so that you can start the node. After you add a node to a domain. View inherited permissions for the node and manage the object permissions for the node. Troubleshooting Application Services I think that a service is using incorrect environment variable values. ¨ Edit permissions. If the Disable Service dialog box appears. you must add the node to the domain. Node Management A node is a logical representation of a physical machine in the domain. In the Domain tab Actions menu. including configuring node properties and removing nodes from a domain. such as the repository backup directory and ports used to run processes. You can define other nodes. the node appears in the Navigator. select Delete. Assign connection resources and define custom and file/directory resources on a node. you can configure it to check the resources available on each node. you can start the node. You can define one or more gateway nodes. and then click OK. When the PowerCenter Integration Service runs on a grid. During installation. ¨ Remove a node. When you add a node to the domain. You can define other nodes using the installation program or infasetup command line program. ¨ Configure properties. Node Management 33 . Remove a node from the domain if you no longer need the node. Configure node properties. View the processes configured to run on the node and their status. ¨ View processes. you define at least one node that serves as the gateway for the domain. Adds the node to the domain and enables the domain to communicate with the node. How can I find out which environment variable values are used by a service. Set the error severity level for the node to debug. The other nodes can be gateway nodes or worker nodes. you define at least one node that serves as the gateway for the domain. ¨ Shut down the node. A master gateway node receives service requests from clients and routes them to the appropriate service and node. You perform the following tasks to manage a node: ¨ Define the node and add it to the domain. Use the Domain tab of Administrator tool to manage nodes. 4. click Yes to stop other services that depend on the application service. Before you remove or shut down a node. When you install Informatica services. When the service starts on the node. ¨ Define resources. Shut down the node if you need to perform maintenance on the machine or to ensure that domain configuration changes take effect. 5.

It cannot exceed 128 characters or begin with @. click the Domain tab. select the folder where you want to add the node. 4. 3. A worker node uses the information in nodemeta. A gateway node uses information in the nodemeta. After you define a node. When you add a node to the domain. In the Properties view.xml to connect to the domain. Configuring Node Properties You configure node properties on the Properties view for the node. select the domain. If you do not want the node to appear in a folder. 4. Edit the following properties: Node Property Name Description Name of the node. 6. Run the installer on each machine you want to define as a node.A worker node can run application services but cannot serve as a gateway. 3. The nodemeta. click Select Folder and choose a new folder or the domain. Click the Properties view. Run the infasetup DefineGatewayNode or DefineWorkerNode command on each machine you want to serve as a gateway or worker node. you specify the host name and port number for the machine that hosts the node. To add a node to the domain: 1. It also cannot contain spaces or the following special characters: 34 Chapter 4: Domain Management . You also specify the node name. which is the node configuration file for the node. 1. On the Navigator Actions menu. 2.xml file. The name is not case sensitive and must be unique within the domain. In the Administrator tool. Click Create. The Create Node dialog box appears. This must be the same node name you specified when you defined the node. When you define a node.xml file to connect to the domain configuration database. You can configure properties such as the error severity level. click the Domain tab. you must add it to the domain. 5. the Administrator tool displays a message saying that you need to run the installation program to associate the node with a physical host name and port number. Enter the node name. 5. In the Administrator tool. ¨ infasetup command line program.xml file is stored in the \isp\config directory on each node. click Edit for the section that contains the property you want to set. If you add a node to the domain before you define the node using the installation program or infasetup. the node appears in the Navigator. the installation program or infasetup creates the nodemeta. minimum and maximum port numbers. click New > Node. The Administrator tool uses the node name to identify the node. and the maximum number of Session and Command tasks that can run on a PowerCenter Integration Service process. Use either of the following programs to define a node: ¨ Informatica installer. In the Navigator. 2. The Properties view displays the node properties in separate sections. If you want to change the folder for the node. When you define a node. In the Navigator. You can add a node to the domain using the Administrator tool or the infacmd AddDomainNode command. select a node.

Default is WARNING. Maximum is 1.Debug. Set this threshold to a high number.Info.5. Default is 10. WARNING. Writes WARNING and ERROR code messages to the log. Or. Ranking of the CPU performance of the node compared to a baseline system. Used in adaptive dispatch mode. such as 200.000. Set this threshold to a low number to preserve computing resources for other applications..Node Property Description `~%^*+={}\. Maximum is 1. Maximum CPU Run Queue Length Maximum number of runnable threads waiting for CPU resources on the node. the value of this property is 1. TRACE. Minimum is 0. For example.000. INFO. and ERROR code messages to the log. Port number used by the node. This threshold specifies the maximum number of running Session or Command tasks allowed for each Integration Service process running on the node.000. Set this threshold to a high value. INFO. . Default is 10. restart Informatica services. WARNING. Writes ERROR code messages to the log. The calculation takes approximately five minutes and uses 100% of one CPU on the machine. These messages are written to the Log Manager application service and Service Manager log files.<>|!()][ Description Host Name Port Gateway Node Description of the node.Error.001. Maximum port number used by service processes on the node. To apply changes. The default value is the value entered when the node was defined. Writes INFO. . Backup Directory Error Severity Level Minimum Port Number Minimum port number used by service processes on the node. you can update the value manually.Tracing.000. such as 200.000. restart Informatica services. . Maximum Memory % Maximum percentage of virtual memory allocated on the node relative to the total physical memory size.000.:'"/?. and ERROR code messages to the log. . if the CPU is running 1. The directory must be accessible by the node. You can calculate the benchmark by clicking Actions > Recalculate CPU Profile Benchmark. Ignored in round-robin dispatch mode. To apply changes. Level of error logging for the node. Indicates whether the node can serve as a gateway. then the node is a worker node. If this property is set to No. The default value is the value entered when the node was defined. Minimum is 0. Ignored in round-robin and metric-based dispatch modes. To prevent the Load Balancer from dispatching tasks to this node.5 times as fast as the baseline machine. Maximum Port Number CPU Profile Benchmark Maximum Processes Maximum number of running processes allowed for each PowerCenter Integration Service process that runs on the node. Writes DEBUG. WARNING. Default is 1. Node Management 35 . Host name of the machine represented by the node. and ERROR code messages to the log.0. Directory to store repository backup files. The description cannot exceed 765 characters. to cause the Load Balancer to ignore it. Minimum is 0. set this threshold to 0.000.Warning. Set one of the following message levels: . Maximum is 1. Used in all dispatch modes. Writes TRACE.000. Used in metric-based and adaptive dispatch modes. to cause the Load Balancer to ignore it.

36 Chapter 4: Domain Management . The Administrator tool displays the list of service processes running on that node. 2. such as 1. disable all running processes in complete mode. RELATED TOPICS: ¨ “Defining Resource Provision Thresholds” on page 280 Viewing Processes on the Node You can view the status of all processes configured to run on a node. Before you shut down or remove a node. select the Processes view. you stop Informatica services and abort all processes running on the node. 2. Shutting Down a Node from the Administrator Tool To shut down a node from the Administrator tool: 1. In the Navigator. click the Domain tab.Node Property Description Set this threshold to a value greater than 100% to allow the allocation of virtual memory to exceed the physical memory size when dispatching tasks. Maximum is 1.000. You might also need to shut down and restart a node for some configuration changes to take effect. 3. 3. if you change the shared directory for the Log Manager or domain. For example. To view processes on a node: 1. select a node. Minimum is 0.000. When you shut down a node. 4.000. In the Administrator tool. if you want the Load Balancer to ignore it. To restart a node. you might need to perform maintenance or benchmarking on a machine. you must shut down the node and restart it to update the configuration files. For example. start Informatica services on the node. or click Cancel to cancel the operation. click the Domain tab. select Shutdown. Click OK. The tab displays the status of each process configured to run on the node. Shutting Down and Restarting the Node Some administrative tasks may require you to shut down a node. Click OK to stop all processes and shut down the node. You can shut down a node from the Administrator tool or from the operating system. Note: To avoid loss of data or metadata when you shut down a node. In the content panel. select a node. On the Domain tab Actions menu. In the Navigator. you can view the status of each process to determine which processes you need to disable. Default is 150. 6. Used in metric-based and adaptive dispatch modes. Set this threshold to a high value. Ignored in round-robin dispatch mode.000. In the Administrator tool.

enter the following command to start the daemon: infaservice.sh. you must run the installation program or infasetup DefineGatewayNode or DefineWorkerNode command on the new host machine. In the warning message that appears.sh is installed in the following directory: <InformaticaInstallationDir>/tomcat/bin 1. select a node. it is no longer visible in the Navigator.sh startup Enter the following command to stop the daemon: infaservice. In the Administrator tool. Note: To avoid loss of data or metadata when you remove a node.sh to start and stop the Informatica daemon. Removing the Node Association You can remove the host name and port number associated with a node. Select Services. 2. 2. 4.sh is located. run infaservice. In the Domain tab Actions menu.sh shutdown Note: If you use a softlink to specify the location of infaservice. select Delete. To associate a different host machine with the node. If the service is running. disable all running processes in complete mode. In the Administrator tool. the node shuts down and all service processes are aborted. In the Navigator Actions menu. select a node. Starting or Stopping a Node on UNIX On UNIX. click Start.Starting or Stopping a Node on Windows To start or stop the node on Windows: 1. Select Administrative Tools. If the service is stopped. Open the Windows Control Panel. 1. Removing a Node When you remove a node from a domain. 3. 2. In the Navigator. set the INFA_HOME environment variable to the location of the Informatica installation directory. click OK. In the Navigator. click the Domain tab. Node Management 37 . click Stop. 2. Go to the directory where infaservice. 3. If the node is running when you remove it. 1. At the command prompt. 3. click the Domain tab. Right-click the Informatica9. but it is not associated with a host machine. 5. the node remains in the domain. and then restart the node on the new host machine. 4. By default.0 service. infaservice. select Remove Node Association. When you remove the node association.

You can configure a worker node to serve as a gateway node. The gateway nodes use a JDBC connection to access the domain configuration database. Configure the directory path for the log files. the domain cannot accept service requests. Each time you make a change to the domain. click the Domain tab. The worker node must be running when you configure it to serve as a gateway node. 2. You can perform the following domain configuration management tasks: ¨ Back up the domain configuration. the domain is inoperable. After installation. During installation. the Service Manager adds the node information to the domain configuration. If you have multiple gateway nodes. select the domain. click Edit in the Gateway Configuration Properties section. Otherwise. configure all gateway nodes to point to the same location for log files. In the Navigator. You may need to restore the domain configuration from a backup if the domain configuration in the database becomes corrupt. If you have one gateway node and it becomes unavailable. the node continues as the master gateway node until you restart the node or the node becomes unavailable. You can select multiple nodes to serve as gateway nodes. 1. configure all gateway nodes to write log files to the same directory on a shared disk. If you have multiple gateway nodes. 6.xml file of the new gateway node. the Service Managers on the other gateway nodes elect a new master gateway node. select the Properties view. 4. you must specify the log directory. Click OK. For example. The domain configuration is a set of metadata tables stored in a relational database that is accessible by all gateway nodes in the domain. Select the check box next to the node that you want to serve as a gateway node. Domain Configuration Management The Service Manager on the master gateway node manages the domain configuration. In the contents panel. You might want to create additional gateway nodes as backups. the Service Manager on the master gateway node writes the domain configuration database connection to the nodemeta.Gateway Configuration One gateway node in the domain serves as the master gateway node for the domain. when you add a node to the domain. 5. 3. Only one gateway node can be the master gateway node at any given time. you can create additional gateway nodes. 38 Chapter 4: Domain Management . Note: You can also run the infasetup DefineGatewayNode command to create a gateway node. You must have at least one node configured as a gateway node at all times. The Service Manager on the master gateway node accepts service requests and manages the domain and services in the domain. After you configure the gateway node. Back up the domain configuration on a regular basis. you create one gateway node. In the Administrator tool. If you have multiple gateway nodes and the master gateway node becomes unavailable. The new master gateway node accepts service requests. If you configure a master gateway node to serve as a worker node. 7. In the Properties view. If you do not restart the node. you must restart the node to make the Service Managers elect a new master gateway node. If you configure a worker node to serve as a gateway node. the Service Manager writes the change to the domain configuration.

you must use the earlier version to restore the domain configuration. you must reset the database connections for all gateway nodes. Each node in a domain has a host name and port number. Complete the following tasks to restore the domain: 1. you can assign new host names and port numbers to the nodes. You may need to restore the domain configuration if you migrate the domain configuration to another database user account.¨ Restore the domain configuration. You may need to restore the domain configuration from a backup file if the domain configuration in the database becomes corrupt. You must disable the application services to ensure that no service process is running when you shut down the domain. 2. Each gateway node must have access to the domain configuration database. You may need to restore the domain configuration if the domain configuration in the database becomes inconsistent or if you want to migrate the domain configuration to another database. Or. ¨ Migrate the domain configuration. You must shut down the domain to ensure that no change to the domain occurs while you are restoring the domain. you can disassociate the host names and port numbers for all nodes in the domain. Informatica restores the domain configuration from the current version. You may need to migrate the domain configuration to another database user account. You might do this if you want to run the nodes on different machines. Important: You lose all data in the summary tables when you restore the domain configuration. you must update the database connection information for each gateway node. Backing Up the Domain Configuration Back up the domain configuration on a regular basis. Note: The domain configuration database and the Model repository cannot use the same database user schema. If you change the database connection information or migrate the domain configuration to a new database. You can restore the domain configuration to the same or a different database user account. Shut down the domain. Domain Configuration Management 39 . After you restore the domain configuration. you must configure the command to overwrite the existing domain configuration. Restoring the Domain Configuration You can restore domain configuration from a backup file. When you restore the domain configuration. Disable the application services in complete mode to ensure that you do not abort any running service process. If you do not configure the command to overwrite the existing domain configuration. ¨ Configure the connection to the domain configuration database. Run the infasetup BackupDomain command to back up the domain configuration to a binary file. Run the infasetup DefineGatewayNode or DefineWorkerNode command to assign a new host name and port number to a node. the command fails. Use custom properties only if Informatica Global Customer Support instructs you to do so. ¨ Configure custom properties. If you have a backup file from an earlier product version. you may need to restore the backup domain configuration to a database user account. If you restore the domain configuration to a database user account with existing domain configuration. You configure the database connection when you create a domain. Configure domain properties that are unique to your environment or that apply in special cases. If you restore the domain configuration to another database. Disable the application services.

The RestoreDomain command restores the domain configuration in the backup file to the specified database user account. 4. Reset the database connections for all gateway nodes if you restored the domain configuration to another database. 4. Create the database user account where you want to restore the domain configuration. 12. 5. 8. Enable all application services in the domain. Shut down the application services in the following order: 1.3. if your company requires all departments to migrate to a new database type. Migrating the Domain Configuration You can migrate the domain configuration to another database user account. 2. 4. Shut Down All Application Services You must disable all application services to disable all service processes. 11. Shut down the domain. Assign new host names and port numbers to the nodes in the domain if you disassociated the previous host names and port numbers when you restored the domain configuration. You may need to migrate the domain configuration if you no longer support the existing database user account. For example. Shut down all application services in the domain. the service process changes may be lost and data may become corrupt. you must migrate the domain configuration. 7. 6. 9. 5. 5. 6. Step 1. 1. Run the infasetup DefineGatewayNode or DefineWorkerNode command to assign a new host name and port number to a node. 7. Restore the domain configuration backup to the database user account. Update the database connection for each gateway node. Tip: Shut down the application services in complete mode to ensure that you do not abort any running service processes. Start all nodes in the domain. Important: Summary tables are lost when you restore the domain configuration. 3. 10. 3. All gateway nodes must have a valid connection to the domain configuration database. Run the infasetup RestoreDomain command to restore the domain configuration to a database. 8. Back up the domain configuration. If you do not disable an application service and a user starts running a service process while you are backing up and restoring the domain. Web Services Hub SAP BW Service Metadata Manager Service PowerCenter Integration Service PowerCenter Repository Service Reporting Service Analyst Service Content Management Service Data Director Service Data Integration Service Model Repository Service Reporting and Dashboards Service 40 Chapter 4: Domain Management . 2.

Run the infasetup UpdateGatewayNode command to update the gateway node. Back Up the Domain Configuration Run the infasetup BackupDomain command to back up the domain configuration to a binary file. Step 6. your company may require you to change the password for the domain configuration database every three months. Update the Database Connection If you restore the domain configuration to a different database user account. you must update the database connection for each gateway node. For example. Application services must be enabled to run service processes. Step 5. Also. 1. Shut down the gateway node that you want to update. Updating the Domain Configuration Database Connection All gateway nodes must have a connection to the domain configuration database to retrieve and update domain configuration. You must start the nodes to enable services to run. Gateway nodes must have a connection to the domain configuration database to retrieve and update domain configuration. Create a Database User Account Create a database user account if you want to restore the domain configuration to a new database user account. Shut Down the Domain You must shut down the domain to ensure that users do not modify the domain while you are migrating the domain configuration. 4. Step 3. For example. if you do not shut down the domain and you restore the domain configuration to a different database. users can create new services and objects. Start the gateway node. Domain Configuration Management 41 . including the database user name and password. Step 8. The RestoreDomain command restores the domain configuration in the backup file to the specified database user account. Restore the Domain Configuration Run the infasetup RestoreDomain command to restore the domain configuration to a database. Step 7. as part of a security policy. 3. Step 4. Repeat this process for each gateway node. When you create a gateway node or configure a node to serve as a gateway. 2. If you migrate the domain configuration to a different database or change the database user name or password. Start All Nodes in the Domain Start all nodes in the domain. The gateway nodes shut down because they cannot connect to the domain configuration database. Enable All Application Services Enable all application services that you previously shut down. A domain is inoperative if it has no running gateway node. the domain becomes inoperative. if the domain is running when you are backing up the domain configuration. you specify the database connection. The connections between the gateway nodes and the domain configuration database become invalid.Step 2. you must update the database connection information for each gateway node in the domain.

Impact analysis helps you determine the implications of particular domain actions. you can view dependencies among all application services and nodes. Run the infasetup UpdateGatewayNode command. If this is the only node on which an application service runs. To filter the list of domain objects in the contents panel. Run the infasetup UpdateGatewayNode command. For example. Run the infasetup DefineGatewayNode command. If the Model Repository Service is unavailable. 4. 2. To remove the filter criteria. An application service is dependent on the node on which it runs. 5. The contents panel shows objects that meet the filter criteria.To update the node with the new database connection information. managing logs. you can complete domain tasks such as monitoring application services and nodes. and viewing service and node dependencies. In addition. 2. Before you shut down the node. Domain Tasks On the Domain tab. you want to shut down a node to run maintenance on the node.You can also manage domain objects by moving them into folders or deleting them. Shut down the gateway node. The contents panel shows the objects defined in the domain. You can also recycle. It might also be dependent on another application service. the Data Integration Service does not work. The contents panel shows all objects defined in the domain. or disable application services and view logs for application services. you must redefine the node. Shut down the gateway node. you must update the node. view dependencies among application services and nodes. To perform impact analysis. For example. In the Navigator. 2. the Data Integration Service must be associated with a Model Repository Service. If you change the host name or port number. If you change the user or password. complete the following steps: 1. 1. Shut down the gateway node. click Reset. Managing and Monitoring Application Services and Nodes You can manage and monitor application services and nodes in a domain. In the Administrator tool. that application service is unavailable when you shut down the node. Click the Services and Nodes view. remove the node association. To update the node after you change the user or password. such as shutting down a node or an application service. 3. 42 Chapter 4: Domain Management . enter filter criteria in the filter bar. 2. You can monitor all application services and nodes in a domain. click the Domain tab. To redefine the node after you change the host name or port number. managing domain objects. you must determine all application services that run on the node. select the domain. complete the following steps: 1. enable. 3. complete the following steps: 1. In the Administrator tool.

d. 7. select an application service in the Navigator to view the service version. and last error message for the service. 9. To show the names of the application services and nodes in the contents panel. In the Select Folder dialog box. ¨ To view logs for the application service. click the Enable the Service button. click the Recycle the Service button. you can view dependencies for application services. Click OK. Click Delete. select the object in the Navigator. If you use Internet Explorer. c. Right-click the object in the Navigator. 3.6. right-click the object in the Navigator. enable the Run ActiveX Controls and Plug-ins option. The contents panels shows properties for the object. To view details for an object. 1. In the Navigator. The Create Folder dialog box appears. 10. To view the View Dependency window. The object is moved to the folder that you specify. click the Hide Details button. enable. 2. 12. to create a new folder. The contents panel shows the names of the application services and nodes in the domain. To hide the names of the application services and nodes in the contents panel. Domain Tasks 43 . Object details appear. ¨ To enable the application service. b. Nodes. service status. ¨ To recycle the application service. right-click a domain object and click View Dependencies. click an object in the Navigator. or show logs for an application service. In the contents panel. select the domain. To delete an object. nodes. To view properties for an object. Click Move to Folder. click the Domain tab. 8. click the Disable the Service button. Alternatively.0. To recycle. To move an object to a folder. 11. Click the Services and Nodes view. click the Show Details button. ¨ To disable the application service. Enter the folder name and click OK.0 or later in your browser. 4. disable. double-click the application service in the Navigator. For example. and grids in an Informatica domain. select a folder. The contents panel hides the names of the application services and nodes in the domain. you must install and enable Adobe Flash Player 10. The contents panel displays the objects in the domain. complete the following steps: a. click Create Folder. Viewing Dependencies for Application Services. and Grids In the Services and Nodes view on the Domain tab. The Select Folder dialog box appears. In the Administrator tool. click the View Logs for Service button. process status.

¨ To view the View Dependency window for any object in the window. as follows: ¨ The blue lines represent service-to-node and service-to-grid dependencies. you must first shut down the domain. A downstream dependency is a service that depends on the selected service. place the cursor over the service. When you shut down the domain. you can optionally complete the following actions: ¨ To view additional dependency information for any object. place the cursor over the object. These services appear greyed out because they are secondary dependencies. if you show the dependencies for a Data Integration Service. right-click the object and click Show Dependency.A dependency between node1 and MRS1. to back up and restore a domain configuration. For example. AT1. ¨ To highlight the downstream dependencies and show additional process details for a service. An upstream dependency is a service on which the selected service depends. After you shut down the domain.A secondary dependency between node1 and the DIS1 and AT1 services. you might need to shut down the domain. clear or select the Show Service dependencies option in the View Dependency window. If you want to shut down node1. 44 Chapter 4: Domain Management . and the node on which the service runs. For example. Also shows secondary dependencies. For example. Shows grids assigned to the node. RELATED TOPICS: ¨ “Domain” on page 15 Shutting Down a Domain To run administrative tasks on a domain. . the orange lines disappear but the services are still visible. as well as DIS1 and AT1 due to their dependency on MRS1. restart Informatica services on each node in the domain. In the View Dependency window. retrieve information from MRS1 but run on node2. the Analyst Service downstream dependency. a Model Repository Service. MRS1. the Service Manager on the master gateway node stops all application services and Informatica services in the domain. DIS1. you see the Model Repository Service upstream dependency. Grid Shows the nodes assigned to the grid and the application services running on the grid. The following table describes the information that appears in the View Dependency window based on the object: Object Node View Dependency Window Shows all service processes running on the node and the status of each process. A Data Integration Service.The View Dependency window shows domain objects connected by blue and orange lines. To hide or show the service-to-service dependencies. Service Shows the upstream and downstream dependencies. When you clear this option. which are dependencies that are not directly related to the object for which you are viewing dependencies. The View Dependency window refreshes and shows the dependencies for the selected object. 5. ¨ The orange lines represent service-to-service dependencies. the window indicates that MRS1 is impacted. and the node on which the Data Integration Service runs. and an Analyst Service. The View Dependency window shows the following information: . runs on node1.

click Edit. Configure a node to serve as gateway and specify the location to write log events. The Shutdown dialog box shows a warning message. Use custom properties only at the request of Informatica Global Customer Support. select a domain. Edit the SMTP settings for the outgoing mail server to enable alerts. ¨ Custom properties. 1. any processes running on nodes in the domain are aborted. Note: To avoid a possible loss of data or metadata and allow the currently running processes to complete. including workflows. have completed and no users are logged in to repositories in the domain. General Properties In the General Properties area. verify that all processes. 4. To view and edit properties.When you shut down a domain. Edit general properties. For example. View the database properties. You can also monitor the domain at a high level. In the Navigator. ¨ Database properties. Create and configure service levels. you can view the statuses of the application services and nodes that are defined in the domain. Before you shut down a domain. you can shut down each node from the Administrator tool or from the operating system. Domain Properties On the Domain tab. 3. and service levels. you can configure domain properties including database properties. restart Informatica services on the gateway and worker nodes in the domain. SMTP properties for alerts. The Shutdown dialog box lists the processes that run on the nodes in the domain. Domain Properties 45 . The contents panel shows the properties for the domain. On the Domain tab. such as database name and database host. and the domain resiliency properties. 5. 2. Click the Domain tab. select the domain. you can change the database properties. You can configure the properties to change the domain. The Service Manager on the master gateway node shuts down the application services and Informatica services on each node in the domain. ¨ Service level management. When you create a domain. gateway configuration. it has no custom properties. such as service resilience and dispatch mode. ¨ Gateway configuration. In the Services and Nodes view. click Actions > Shutdown Domain. ¨ SMTP configuration. 6. To edit general properties. To restart the domain. you can configure general properties for the domain such as service resilience and load balancing. You can configure the following domain properties: ¨ General properties. Click Yes. Click Yes. In the Navigator. click the Domain tab. Then click the Properties view in the contents panel. Edit custom properties that are unique to the Informatica environment or that apply in special cases.

services use TLS connections to communicate with other Informatica application services and clients. Enabling TLS for the domain does not apply to PowerCenter application services. The name of the machine hosting the database. Default is 30 seconds. The user account for the database containing the domain configuration information. The following table describes the properties that you can edit in the Database Properties area: Property Database Type Description The type of database that stores the domain configuration metadata.The following table describes the properties that you can edit in the General Properties area: Property Name Resilience Timeout (sec) Limit on Resilience Timeouts (sec) Description Read-only. The port number used by the database. The maximum amount of time in seconds that the domain spends trying to restart an application service process.Adaptive Configures services to use the TLS protocol to transfer data securely within the domain.MetricBased . then the TLS updates cannot be applied to the Service Manager on the unavailable node. Default is 180 seconds. Restart Period Maximum Restart Attempts within Restart Period Dispatch Mode The mode that the Load Balancer uses to dispatch PowerCenter Integration Service tasks to nodes in a grid. Valid values are from 0 to 1000000. Select one of the following dispatch modes: . Valid values are true and false. The amount of time in seconds that a client is allowed to try to connect or reconnect to a service. When you enable TLS for the domain. Database Host Database Port Database Name Database User 46 Chapter 4: Domain Management . The name of the domain. Valid values are from 0 to 1000000. such as database name and database host. If a node is unavailable. A client is a PowerCenter client application or the PowerCenter Integration Service. The amount of time in seconds that a service waits for a client to connect or reconnect to the service. Enable Transport Layer Security (TLS) Database Properties In the Database Properties area. Verify that all domain nodes are available before you enable TLS. Valid values are from 0 to 1000000. The name of the database. Valid values are from 1 to 1000. To apply changes. restart the domain.RoundRobin . you can view or edit the database properties for the domain. The number of times that the domain tries to restart an application service process.

select this option. The following table describes the properties that you can edit in the Gateway Configuration Properties area: Property Node Name Status Gateway Description Read-only. add. The directory path for the log event files. Because service levels are domain properties. < > | ! ( ) ] [ Domain Properties 47 . To delete a service level. Log Directory Path Service Level Management In the Service Level Management area. To sort gateway configuration properties. which has a dispatch priority of 5 and a maximum dispatch wait time of 1800 seconds. the Load Balancer uses service levels to determine the order in which to dispatch tasks from the queue. To edit a service level. and edit service levels. clear this option. the Load Balancer places those tasks in the dispatch queue. To configure the node as a gateway node. : / ? . You can edit but you cannot delete the Default service level. Also. The status of the node. To edit gateway configuration properties. you can configure a node to serve as gateway for a domain and specify the directory where the Service Manager on this node writes the log event files.Gateway Configuration Properties In the Gateway Configuration Properties area. it writes log events to the node. The name of the node. To add a service level. When the Load Balancer has more tasks to dispatch than the PowerCenter Integration Service can run at the time. previous logs do not appear. Service levels set priorities among tasks that are waiting to be dispatched. click Edit. It cannot exceed 128 characters or begin with the @ character.log file on the master gateway node. you can view. If you edit gateway configuration properties. When multiple tasks are in the dispatch queue. click Add. The following table describes the properties that you can edit in the Service Level Management area: Property Name Description The name of the service level. the changed properties apply to restart and failover scenarios only. If the Log Manager cannot write to the directory path. you can use the same service levels for all repositories in a domain. click the link for the service level. The name is not case sensitive and must be unique within the domain. It also cannot contain spaces or the following special characters: ` ~ % ^ * + = { } \ . To configure the node as a worker node. select the service level and click the Delete button. You create and edit service levels in the domain properties or by using infacmd. click in the header for the column by which you want to sort.

Valid values are from 1 to 10. you can configure SMTP settings for the outgoing mail server to enable alerts. it has no custom properties. if required by the outbound mail server. Maximum Dispatch Wait Time (seconds) RELATED TOPICS: ¨ “Creating Service Levels” on page 279 SMTP Configuration In the SMTP Configuration area. Dispatch Priority A number that sets the dispatch priority for the service level. When you create a domain. Valid values are from 1 to 86400. Port User Name Password Sender Email Address RELATED TOPICS: ¨ “Configuring SMTP Settings” on page 27 Custom Properties Custom properties include properties that are unique to your environment or that apply in special cases.Property Description After you add a service level. Dispatch priority 1 is the highest priority. The user password for authentication upon sending. enter the Microsoft Exchange Server for Microsoft Outlook. The user name for authentication upon sending. Port used by the outgoing mail server. If you leave this field blank. if required by the outbound mail server. Valid values are from 1 to 65535. 48 Chapter 4: Domain Management . Define custom properties only at the request of Informatica Global Customer Support. For example. the Service Manager uses Administrator@<host name> as the sender. The Load Balancer dispatches high priority tasks before low priority tasks. Default is 25. The email address that the Service Manager uses in the From field when sending notification emails. you cannot change its name. Default is 1800. Setting this property ensures that no task waits forever in the dispatch queue. Default is 5. The amount of time in seconds that the Load Balancer waits before it changes the dispatch priority for a task to the highest priority. The following table describes the properties that you can edit in the SMTP Configuration area: Property Host Name Description The SMTP outbound mail server host name.

If you use the command line to upgrade services. A user with the Administrator role on the domain.CHAPTER 5 Application Service Upgrade This chapter includes the following topics: ¨ Application Service Upgrade Overview. Service Upgrade for Data Quality 9. ¨ Data Integration Service. ¨ Profiling Service Module for Data Integration Service. upgrade the following object types: ¨ Model Repository Service.0. You must upgrade the Model Repository Service before you upgrade Data Integration Service. verify that the services are enabled. Use the service upgrade wizard. or command line to upgrade services.1 Before you upgrade services. you must also upgrade the dependent services. Some service versions require a service upgrade. After you upgrade the PowerCenter Repository Service. the actions menu of each service. The service upgrade wizard upgrades multiple services in the appropriate order and checks for dependencies. the Model Repository Service. you must restart the service. you must upgrade services in the correct order and verify that you upgrade dependent services. 49 . and the Data Integration Service can upgrade services. When you upgrade a service. To upgrade services. 50 Application Service Upgrade Overview The product and product version determines the service upgrade process. you must restart the service and its dependent services. After you upgrade a service. 49 ¨ Service Upgrade Wizard.

Upgrade Report The upgrade report contains the upgrade start time. upgrade end time. ¨ PowerCenter Repository Services are enabled and running in exclusive mode. upgrade the Profiling Service Module for Data Integration Service. ¨ Enable services before the upgrade. choose one of the following options: 50 Chapter 5: Application Service Upgrade . Before you upgrade PowerCenter 8. ¨ Automatically or manually reconcile user name and group conflicts.6. the Model Repository Service. You must upgrade the Model Repository Service before you upgrade Data Integration Service. You can access the service upgrade wizard from the Manage menu in the header area.1 services. and upgrade processing details. ¨ Automatically restart the services after they have been upgraded. ¨ Reporting Services are disabled.0.1 Services upgrade are not required for this upgrade. upgrade the following object types: ¨ Model Repository Service. The service upgrade wizard provides the following options: ¨ Upgrade multiple services. Service Upgrade Wizard Use the service upgrade wizard to upgrade services.1 You must upgrade the PowerCenter Repository Service and Reporting Service. upgrade status. and the Data Integration Service can upgrade services.1 has the profiling option. ¨ If Data Services 9. A user with the Administrator role on the domain.1 Before you upgrade services.0.Service Upgrade for Data Services 9. To save the upgrade report. verify that the services are enabled. ¨ Data Integration Service. Service Upgrade for PowerCenter 8. Service Upgrade for PowerCenter 9.0. verify the following prerequisites: ¨ You have the Administrator role on the domain.6. ¨ Display upgraded services in a list along with services that require an upgrade. The Services Upgrade Wizard generates the upgrade report. To upgrade services. ¨ Save the current or previous upgrade report.

3. Users and Groups Conflict Resolution When you upgrade PowerCenter Repository Service users and groups. Click Next.Save Report The Save Report option appears on step 4 of the service upgrade wizard. This dialog box appears when you upgrade 8. 12. 6. 13. When the upgrade completes. If you choose not to save the report. If dependency errors exist. In the Informatica Administrator header area click Manage > Upgrade. choose to use the same login information for all repositories. resolve dependency errors and click Next. specify if you want to Automatically recycle services after upgrade. Click each service to view the upgrade details in the Service Details section. Select the objects to upgrade. Review the dependency errors and click OK. select the LDAP security domain and click OK. If you did not save the upgrade report after upgrading services. If you choose to automatically recycle services after upgrade. 9. The service upgrade wizard upgrades each service and displays the status and processing details. the upgrade wizard restarts the services after they have been upgraded. 2. 11. 7. 14.1 PowerCenter Repository Service users and groups and you choose not to automatically reconcile user and group conflicts. you must restart the service and its dependent services. you can select this option to view or save the previous upgrade report. click Save Report to save the upgrade details to a file. If you are upgrading 8. After you upgrade the PowerCenter Repository Service. If you did not choose to automatically recycle services after upgrade. Click Close. Optionally. Then. 8. Running the Service Upgrade Wizard Use the service upgrade wizard to upgrade services. specify a resolution for each conflict and click OK. Optionally. 4. specify if you want to Automatically reconcile user and group name conflicts. Enter the repository login information. Click Next. the Save Previous Report option appears on step 1 of the service upgrade wizard. you can click Save Previous Report the next time you launch the service upgrade wizard. If the Reconcile Users and Groups dialog box appears.1. 10. Use the service upgrade wizard to automatically use the same resolution for all conflicts or manually specify a resolution for each conflict. 5.1 PowerCenter Repository Service users and groups for a repository that uses an LDAP authentication. Save Previous Report The second time you run the service upgrade wizard.1. the Dependency Errors dialog box appears. 1. the Summary section displays the list of services and their upgrade status. Optionally. restart upgraded services. Service Upgrade Wizard 51 . you can select a resolution for user name and group name conflicts. Optionally.

52 Chapter 5: Application Service Upgrade . The new group or user account takes the privileges and properties of the group or user in the repository. The Users and Groups With Conflicts section shows a list of users that are not in the security domain and will not be upgraded. Upgrades user and assign permissions. LDAP user privileges are merged with users in the security domain that have the same name. the list of groups the user belongs to in the repository is merged with the list of groups the user belongs to in the domain. email address. When a group is merged with a domain group. Maintains user and group relationships. including full name. Retains the password and properties of the user account in the domain. the Users and Groups Without Conflicts section of the conflict resolution screen lists the users that will be upgraded. The LDAP user retains the password and properties of the account in the LDAP security domain. and phone. Creates a new group or user account with the group or user name you provide. When a user is merged with a domain user. If you want to upgrade users that are not in the security domain. the list of users the group is merged with the list of users the group has in the domain. use the Security page to update the security domain and synchronize users before you upgrade users. Rename Upgrade When you upgrade a repository that uses LDAP authentication. No conflict. description.The following table describes the conflict resolution options for users and groups: Resolution Merge with or Merge Description Adds the privileges of the user or group in the repository to the privileges of the user or group in the domain. You cannot merge multiple users or groups with one user or group. Retains the parent group and description of the group in the domain.

enable the TLS protocol for the domain. 55 Domain Security Overview You can configure Informatica domain components to use the Secure Sockets Layer (SSL) protocol or the Transport Layer Security (TLS) protocol to encrypt connections with other components. Between the domain and external components You can configure secure communication between Informatica domain components and web browsers or web service clients. you ensure secure communication. 53 ¨ Secure Communication Within the Domain. you secure the communication between the following components: ¨ Between Service Managers on all domain nodes ¨ Between application services ¨ Between application services and application clients 53 . Each method of configuring secure communication is independent of the other methods. When you enable SSL or TLS for domain components. Secure Communication Within the Domain To configure services to use the TLS protocol to transfer data securely within the domain. When you enable the TLS protocol for the domain. 53 ¨ Secure Communication with External Components.CHAPTER 6 Domain Security This chapter includes the following topics: ¨ Domain Security Overview. you do not need to configure secure communication for any other set. When you configure secure communication for one set of components. You can configure secure communication in the following ways: Between services within the domain You can configure secure communication between services within the domain.

TLS Configuration Using infasetup You can use the infasetup command line program to enable or disable the TLS protocol for the domain. enabling TLS for the domain does not apply to the PowerCenter Repository Service. use the UpdateGatewayNode command and set the enable TLS option to true. Reporting Service. To disable the TLS protocol for an existing domain.¨ Between infacmd and Service Managers and application services You cannot enable the TLS protocol for all application service types. Metadata Manager Service. 3. select the domain. click Edit. 2. then use infasetup commands to enable TLS for the Service Manager on the unavailable node. Verify that all domain nodes are available before you enable TLS for the domain. The services use a self-signed keystore file generated by Informatica. Select Enable Transport Layer Security (TLS) and click OK. select the Services and Nodes view. SAP BW Service. 5. use the UpdateGatewayNode command. application clients. UpdateGatewayNode To enable the TLS protocol for an existing domain. The keystore file stores the certificates and keys that authorize the secure connection between the services and other domain components. When you enable the TLS protocol. After you change the TLS protocol for the domain. and command line programs regardless of whether the TLS protocol is enabled for the domain. UpdateWorkerNode To enable or disable the TLS protocol for the Service Manager on a worker node that was unavailable when you changed the TLS protocol for the domain. In the Navigator. If a node is unavailable. use one of the following infasetup commands: DefineDomain To enable the TLS protocol when you create a domain. use the UpdateGatewayNode command and set the enable TLS option to false. You can use the Administrator tool or the infasetup command line program to configure secure communication within the domain. or Web Services Hub. For example. To enable or disable the TLS protocol for the Service Manager on a gateway node that was unavailable when you changed the TLS protocol for the domain. you configure secure communication between services within the domain. In the General Properties area. use the DefineDomain command and set the enable TLS option to true. Shut down and restart the domain to apply the change. 1. you configure secure communication between services within the domain. To configure secure communication within the domain. Verify that all domain nodes are available before you enable TLS for the domain. 54 Chapter 6: Domain Security . On the Domain tab. PowerCenter Integration Service. Note: Passwords are encrypted for all application services. use the UpdateWorkerNode command. When you enable the TLS protocol. 4. Configuring Secure Communication Within the Domain You can use the Administrator tool to enable or disable the TLS protocol for the domain. you must shut down and restart the domain to apply the change.

You can configure secure communication between the following Informatica domain components and external components: Informatica web application and web browser You can configure secure communication for Informatica web applications to transfer data securely between the web browser and the web application. use the DefineWorkerNode command. You can configure HTTPS during installation or using infasetup commands. configure the HTTPS port that the Data Integration Service runs on and enable TLS for the web service.DefineGatewayNode To add a gateway node to a domain that has the TLS protocol enabled. The HTTPS port and keystore file location you configure appear in the Node Properties. When you define the node. Secure Communication with External Components You can configure secure communication between Informatica domain components and web browsers or web service clients. Application services and application clients communicate with the Service Manager using the gateway or worker node port. To configure HTTPS for a node. a warning message appears when you access the Administrator tool. When you configure an HTTPS port. or Web Services Hub Console. A plain-text password for the keystore file. Secure Communication with External Components 55 . Metadata Manager application. You can create the keystore file during installation or you can create a keystore file with a keytool. the Administrator tool URL redirects to the following HTTPS enabled site: https://<host>:<https port>/administrator When the node is enabled for HTTPS with a self-signed certificate. A file that includes private or public key pairs and associated certificates. accept the certificate. enable the TLS protocol for the Service Manager on the node. After you configure the node to use HTTPS. configure the HTTPS port that the web application runs on. Data Analyzer. ¨ Keystore file name and location. To secure the connection to the Analyst tool. The port used by the node for communication to the Administrator tool. When you define the node. To secure the connection to the Administrator tool. Secure Communication to the Administrator Tool To use the SSL protocol for a secure connection to the Administrator tool. DefineWorkerNode To add a worker node to a domain that has the TLS protocol enabled. ¨ Keystore password. define the following information: ¨ HTTPS port. the gateway or worker node port does not change. configure HTTPS for all nodes in the domain. You can use a self-signed certificate or a certificate signed by a certificate authority. configure HTTPS for all nodes in the domain. To enter the site. Data Integration Service and web service client To use the TLS protocol for a secure connection between a web service client and the Data Integration Service. enable the TLS protocol for the Service Manager on the node. use the DefineGatewayNode command.

You can use the self-signed certificate or use a certificate signed by a certificate authority. keytool wraps the public key into a self-signed certificate.com/javase/1. use the infasetup UpdateGatewayNode command. When you update the node. click Tools > Internet Options > Advanced. see the documentation on the appropriate web site: http://download. Internet Explorer requires TLS 1. use the infasetup UpdateWorkerNode command. Use one of the following infasetup commands: ¨ To enable HTTPS support for a worker node. To disable HTTPS support for a node. or DefineWorkerNode command. Find keytool in one of the following directories: ¨ %JAVA_HOME%\jre\bin ¨ java\bin directory of the Informatica installation directory For more information about using keytool.Note: If you configure HTTPS for the Administrator tool on a domain that runs on 64-bit AIX.4.oracle. To enable TLS 1.0.0.0 setting is listed below the Security heading.com/javase/6/docs/technotes/tools/solaris/keytool.html (for UNIX) HTTPS Configuration Using infasetup Use the infasetup command line program to configure HTTPS for the Administrator tool.oracle. set the HTTPS port option to zero. DefineGatewayNode.html (for Windows) http://download. ¨ To enable HTTPS support for a gateway node. The TLS 1. keytool is a utility that generates and stores private or public key pairs and associated certificates in a file called a “keystore. use the infasetup UpdateGatewayNode or UpdateWorkerNode command. Creating a Keystore File You can create the keystore file during installation or you can create a keystore file with a keytool. 56 Chapter 6: Domain Security . use the infasetup DefineDomain. ¨ To create a new worker or gateway node with HTTPS support.” When you generate a public or private key pair.2/docs/tooldocs/windows/keytool.

privileges. ¨ Groups. and other user accounts. A role is a collection of privileges that you can assign to users and groups. 57 . the Service Manager authenticates the user account in the Informatica domain and verifies that the user can use the application client. You can set up different types of user accounts in the Informatica domain. 70 ¨ Managing Operating System Profiles. The Service Manager organizes user accounts and groups by security domain. Privileges determine the actions that users can perform in application clients. ¨ Authentication. and permissions assigned to them. When a user logs in to an application client. privileges.CHAPTER 7 Users and Groups This chapter includes the following topics: ¨ Users and Groups Overview. You can set up groups of users and assign different roles. The Informatica domain can use native or LDAP authentication to authenticate users. 72 ¨ Account Lockout. You assign roles or privileges to users and groups for the domain and for application services in the domain. The roles. 66 ¨ Managing Groups. Use the default administrator account to initially log in to the Informatica domain and create application services. It authenticates users based on the security domain the user belongs to. During installation. privileges. and permissions to each group. change the password to ensure security for the Informatica domain and applications. and permissions assigned to the group determines the tasks that users in the group can perform within the Informatica domain. a default administrator user account is created. User account management in Informatica involves the following key components: ¨ Users. you must have a user account. When you log in to the Informatica domain after installation. The tasks you can perform depend on the type of user account you have. 61 ¨ Managing Users. domain objects. 58 ¨ Understanding Authentication and Security Domains . 57 ¨ Understanding User Accounts. 60 ¨ Setting Up LDAP Authentication. 75 Users and Groups Overview To access the application services and objects in the Informatica domain and to use the application clients. Users can perform tasks based on the roles. ¨ Privileges and roles.

you can simplify user administration tasks. roles. You cannot complete the following tasks for the Everyone group: ¨ Edit or delete the Everyone group. The users inherit the roles and permissions assigned to the group. including nodes. add the user to a group. configure. and manage all objects in the domain. like the Developer tool and Analyst tool. roles. The default administrator is a user account in the native security domain. You do not need to reassign privileges. For more information. application services. ¨ Log in to any application client. the installer creates the default administrator with a user name and password you provide. ¨ Add users to or remove users from the Everyone group. Understanding User Accounts An Informatica domain can have the following types of accounts: ¨ Default administrator ¨ Domain administrator ¨ Application client administrator ¨ User Default Administrator When you install Informatica services. ¨ Move a group to the Everyone group.¨ Operating system profiles. You can also unlock a user account. You can change the default administrator password. If you run the PowerCenter Integration Service on UNIX. The default administrator has administrator permissions and privileges on the domain and all application services. For example. Tip: If you organize users into groups and then assign roles and permissions to the groups. You can assign privileges. The default administrator can perform the following tasks: ¨ Create. Default Everyone Group An Informatica domain includes a default group named Everyone. If a new user joins the organization. You cannot disable or modify the user name or privileges of the default administrator. and permissions. you can configure the PowerCenter Integration Service to use operating system profiles when running workflows. All users in the domain belong to the group. You cannot create a default administrator. You can use the default administrator account to initially log in to the Administrator tool. if a user changes positions within the organization. ¨ Account lockout. 58 Chapter 7: Users and Groups . ¨ Configure and manage all objects and user accounts created by other domain administrators and application client administrators. and permissions to the Everyone group to grant the same access to all users. You can create and manage operating system profiles on the Security tab of the Administrator tool. see the Informatica How-To Library article Using Groups and Roles to Manage Informatica Access Control. You can configure account lockout to lock a user account when the user specifies an incorrect login in the Administrator tool or any application clients. and administrator and user accounts. move the user to another group.

The default administrator must explicitly give a domain administrator full permissions and privileges to the application services so that they can log in and perform administrative tasks in the application clients. Can view all tasks created for Informatica Data Director for Data Quality. ¨ PowerCenter Client administrator. Understanding User Accounts 59 . create a separate administrator account for each application client. Administrator privileges map to the ROLE_ADMINISTRATOR role in Jaspersoft. Has full permissions and privileges in Metadata Manager. ¨ Informatica Data Director for Data Quality administrator. However. assign a user the Administrator role for a PowerCenter Repository Service. assign a user the Administrator role for an Analyst Service and for the associated Model Repository Service. ¨ Informatica Developer administrator. Has full permissions and privileges in Informatica Analyst. Without permissions or privileges on the domain. assign a user the Administrator role for a Metadata Manager Service. ¨ Metadata Manager administrator. The Informatica Developer administrator can log in to Informatica Developer to create and manage projects and objects in projects and perform all tasks in the application client. The PowerCenter Client administrator can log in to the PowerCenter Client to manage the PowerCenter repository objects and perform all tasks in the PowerCenter Client. Has full permissions and privileges in Informatica Developer.Domain Administrator A domain administrator can create and manage objects in the domain. To create an Informatica Analyst administrator. Application Client Administrator An application client administrator can create and manage objects in an application client. The Metadata Manager administrator can log in to Metadata Manager to create and manage Metadata Manager objects and perform all tasks in the application client. The domain administrator can log in to the Administrator tool and create and configure application services in the domain. To create a Data Analyzer administrator. assign a user the Administrator role for a domain. Has full permissions and privileges in Data Analyzer. You must create administrator accounts for the application clients. nodes. including user accounts. and application services. By default. To create a PowerCenter Client administrator. To create a Metadata Manager administrator. by default. To create a domain administrator. assign a user the Administrator role for a Model Repository Service. the application client administrator does not have permissions or privileges on the domain. the domain administrator cannot log in to application clients. To create an Informatica Developer administrator. licenses. and can assign tasks to users and groups. To limit administrator privileges and keep application clients secure. grids. assign a user the Administrator role for a Reporting Service. The Data Analyzer administrator can log in to Data Analyzer to create and manage Data Analyzer objects and perform all tasks in the application client. ¨ Jaspersoft administrator. The PowerCenter Client administrator can also perform all tasks in the pmrep and pmcmd command line programs. the application client administrator cannot log in to the Administrator tool to manage the application service. ¨ Informatica Analyst administrator. The Informatica Analyst administrator can log in to Informatica Analyst to create and manage projects and objects in projects and perform all tasks in the application client. You can set up the following application client administrators: ¨ Data Analyzer administrator. Has full permissions and privileges on all objects in the PowerCenter Client.

You can use more than one type of authentication in an Informatica domain. the Service Manager authenticates the user name and password against the LDAP directory service. By default. The Service Manager uses native and LDAP authentication to authenticate users logging in to the Informatica domain. By default. the Service Manager uses the native security domain to authenticate the user name and password. After you set up the connection to an LDAP directory service.User A user with an account in the Informatica domain can perform tasks in the application clients. If the LDAP server uses the SSL protocol. The Service Manager authenticates users based on their security domain. the Service Manager authenticates the user account in the Informatica domain and verifies that the user can use the application client. If you also have users in an LDAP directory service who use application clients. When a user logs in. An Informatica domain can have multiple LDAP security domains. any user with the required domain privileges and permissions can create a user account and assign roles. LDAP Authentication To enable an Informatica domain to use LDAP authentication. The Service Manager stores user account information for each security domain in the domain configuration database. in the domain configuration database. you can import the users and groups from the LDAP directory service 60 Chapter 7: Users and Groups . A security domain is a collection of user accounts and groups in an Informatica domain. permissions. permissions. The Service Manager organizes user accounts and groups by security domains. you can import the user account information from the LDAP directory service into an LDAP security domain. Understanding Authentication and Security Domains When a user logs in to an application client. The Service Manager stores details of the user accounts. the default administrator or a domain administrator creates and manages user accounts and assigns roles. The native security domain is created at installation and cannot be deleted. When a user logs in. An Informatica domain can have more than one security domain. You can configure the Informatica domain to use LDAP authentication in addition to native authentication. the Informatica domain contains a native security domain. you must also specify the location of the SSL certificate. the Informatica domain uses native authentication. Typically. the Service Manager stores all user account information and performs all user authentication within the Informatica domain. You create and maintain user accounts of the native security domain in the Administrator tool. The authentication method used by an Informatica domain determines the security domains available in an Informatica domain. and privileges in the Informatica domain. you must set up a connection to an LDAP directory service and specify the users and groups that can have access to the Informatica domain. you use the Administrator tool to create users and groups in the native security domain. and privileges. Native Authentication For native authentication. An Informatica domain can have only one native security domain. including passwords and groups. You can set up LDAP security domains in addition to the native security domain. Users can perform tasks in application clients based on the privileges and permissions assigned to them. Set a filter to specify the user accounts to be included in an LDAP security domain. For example. However.

click LDAP Configuration on the Security Actions menu. You can assign LDAP user accounts to native groups to organize them based on their roles in the Informatica domain.and create an LDAP security domain. the Service Manager sends the user account name and password to the LDAP directory service using the appropriate SSL certificates. Step 1. When users log in to application clients. 3. the Service Manager imports users and groups from the LDAP directory service and deletes any user or group that no longer exists in the LDAP directory service. the Service Manager passes the user account name and password to the LDAP directory service for authentication. Create an LDAP security domain and set up a filter to specify the users and groups in the LDAP directory service who can access application clients and be included in the security domain. the Service Manager imports the user accounts of all LDAP security domains from the LDAP server. and permissions to users and groups in an LDAP security domain. Setting Up LDAP Authentication 61 . Configure a security domain. During synchronization. Use the LDAP Configuration dialog box to set up LDAP authentication for the Informatica domain. To display the LDAP Configuration dialog box in the Security tab of the Administrator tool. complete the following steps: 1. 2. You can set up a schedule for the Service Manager to periodically synchronize the list of users and groups in the LDAP security domain with the list of users and groups in the LDAP directory service. Note: The Service Manager requires that LDAP users log in to an application client using a password even though an LDAP directory service may allow a blank password for anonymous mode. the Service Manager authenticates them based on their security domain. You can use the following LDAP directory services for LDAP authentication: ¨ Microsoft Active Directory Service ¨ Sun Java System Directory Service ¨ Novell e-Directory Service ¨ IBM Tivoli Directory Service ¨ Open LDAP Directory Service You create and manage LDAP users and groups in the LDAP directory service. If the LDAP server uses SSL security protocol. Setting Up LDAP Authentication If you have user accounts in an enterprise LDAP directory service that you want to give access to application clients. you can configure the Informatica domain to use LDAP authentication. privileges. You cannot use the Administrator tool to create. When a user in an LDAP security domain logs in to an application client. Set Up the Connection to the LDAP Server When you set up a connection to an LDAP server. edit. The Service Manager imports the users and groups from the LDAP directory service into an LDAP security domain. Set up the connection to the LDAP server. Schedule the synchronization times. To set up LDAP authentication for the domain. You can assign roles. or delete users and groups in an LDAP security domain.

The maximum port number is 65535. the Service Manager may not assign all users to groups in the LDAP directory service. Typically. In the LDAP Configuration dialog box. Listening port for the LDAP server. Leave blank for anonymous login. Name of the attribute that contains group membership information for a user. Leave blank for anonymous login. For more information. and a country (C). the Service Manager verifies that the SSL certificate is signed by a certificate authority before connecting to the LDAP server. Determines whether the Service Manager can trust the SSL certificate of the LDAP server. Select from the following directory services: . ensure that the user and group filters in the LDAP security domains are correct for the new LDAP server and include the users and groups that you want to use in the Informatica domain. the LDAP server port number is 636. The following table describes the LDAP server configuration properties: Property Server name Port Description Name of the machine hosting the LDAP directory service. Type of LDAP directory service. Indicates that the LDAP directory service uses Secure Socket Layer (SSL) protocol.Microsoft Active Directory Service . if the value is set to 100. If selected. The principal user name is an administrative user with access to the directory. specify the truststore file and password to use.Sun Java System Directory Service . If the Service Manager does not ignore case sensitivity. Not Case Sensitive Indicates that the Service Manager must ignore case-sensitivity for distinguished name attributes when assigning users to groups. the LDAP server port number is 389. member or memberof. you can import a maximum of 100 groups and 100 user accounts into the security domain.IBM Tivoli Directory Service .When you configure the LDAP server connection. To set up a connection to the LDAP server: 1. Specify a user that has permission to read other user entries in the LDAP directory service. You may need to consult the LDAP administrator to get the information on the LDAP directory service. LDAP Directory Service Password Use SSL Certificate Trust LDAP Certificate Group Membership Attribute Maximum Size 62 Chapter 7: Users and Groups . This is the attribute in the LDAP group object that contains the DNs of the users or groups who are members of a group. click the LDAP Connectivity tab. Configure the LDAP server properties. Maximum number of groups and user accounts to import into a security domain. If the LDAP server uses SSL. If you modify the LDAP connection properties to connect to a different LDAP server.Novell e-Directory Service . see the documentation for the LDAP directory service. an organization (O). This is the port number to communicate with the LDAP directory service. the Service Manager connects to the LDAP server without verifying the SSL certificate. Enable this option. For example. 2. indicate that the Service Manager must ignore case-sensitivity for distinguished name attributes when it assigns users to their corresponding groups. To enable the Service Manager to recognize a self-signed certificate as valid. The user name often consists of a common name (CN). If not selected. Password for the principal user.Open LDAP Directory Service Name Distinguished name (DN) for the principal user. For example.

The status of the user account in the LDAP directory service affects user authentication in application clients. a user account is enabled in the Informatica domain but disabled in the LDAP directory service. The Service Manager does not import LDAP users or groups if names do not conform to the rules of native user and group names. You must enable or disable an LDAP user account in the Administrator tool. 3. the Service Manager does not delete the existing security domains. then the user can log in to application clients. When you set up the LDAP directory service. The Service Manager uses the user search bases and filters to import user accounts and the group search bases and filters to import groups. The Service Manager requires a particular UID to identify users in each LDAP directory service. It imports the groups that are included in the group filter and the user accounts that are included in the user filter. Note: Unlike native user names. If the LDAP directory service does not allow disabled user accounts to log in. verify that the LDAP directory service uses the required UID. The Service Manager imports groups and the list of users that belong to the groups. you can use different attributes for the unique ID (UID). the Service Manager generates an error message and does not import any user. then the user cannot log in to application clients. Default is 1000. For example. You must ensure that the LDAP security domains are correct for the new LDAP server.Property Description If the number of user and groups to be imported exceeds the value for this property. Configure Security Domains Create a security domain for each set of user accounts and groups you want to import from the LDAP server. The names of users and groups to be imported from the LDAP directory service must conform to the same rules as the names of native users and groups. Before you configure the security domain. Modify the user and group filters in the existing security domains or create security domains so that the Service Manager correctly imports the users and groups that you want to use in the Informatica domain. Click Test Connection to verify that the connection configuration is correct. The following table provides the required UID for each LDAP directory service: LDAP Directory Service IBMTivoliDirectory Microsoft Active Directory NovellE OpenLDAP SunJavaSystemDirectory UID uid sAMAccountName uid uid uid The Service Manager does not import the LDAP attribute that indicates that a user account is enabled or disabled. Set this property to a higher value if you have many users and groups to import. Set up search bases and filters to define the set of user accounts and groups to include in a security domain. click the Security Domains tab. LDAP user names can be case-sensitive. Complete the following steps to add an LDAP security domain: 1. Setting Up LDAP Authentication 63 . In the LDAP Configuration dialog box. If the LDAP directory service allows disabled user accounts to log in. Note: If you modify the LDAP connection properties to connect to a different LDAP server. Step 2.

The time it takes for the synchronization process to complete depends on the number of users and groups to be imported. If the preview does not display the correct set of users and groups. The Service Manager immediately synchronizes all LDAP security domains with the LDAP directory service. You may need to consult the LDAP administrator to get the information on the users and groups available in the LDAP directory service.ou=OrganizationalUnit. where the series of relative distinguished names denoted by dc=DomainName identifies the DNS domain of the object. repeat steps 2 through 4. To ensure that the list of users and groups in the LDAP security domains is accurate. The filter can specify attribute types. Click Preview to view a subset of the list of users and groups that fall within the filter parameters. For example: (objectclass=*) searches all objects. Click OK to save the security domains. An LDAP query string that specifies the criteria for searching for groups in the directory service. User search base Distinguished name (DN) of the entry that serves as the starting point to search for user names in the LDAP directory service. and matching criteria. The following table describes the filter properties that you can set up for a security domain: Property Security Domain Description Name of the LDAP security domain. 5. To immediately synchronize the users and groups in the security domains with the users and groups in the LDAP directory service. 64 Chapter 7: Users and Groups . create a schedule for the Service Manager to synchronize the users and groups. the distinguished name of a user object might be cn=UserName. (&(objectClass=user)(! (cn=susan))) searches all user objects except “susan.\%? The name can contain an ASCII space character except for the first and last character.” For more information about search filters.2. in Microsoft Active Directory. Group filter 4. 3. the Service Manager does not have a scheduled time to synchronize with the LDAP directory service. 7. Click Add. modify the user and group filters and search bases to get the correct users and groups. 6. assertion values. The name is not case sensitive and must be unique within the domain.+/<>@. Group search base Distinguished name (DN) of the entry that serves as the starting point to search for group names in the LDAP directory service.dc=DomainName. All other space characters are not allowed. To add another LDAP security domain. The search finds an object in the directory according to the path in the distinguished name of the object. User filter An LDAP query string that specifies the criteria for searching for users in the directory service. For example. Use LDAP query syntax to create filters to specify the users and groups to be included in this security domain. Schedule the Synchronization Times By default. click Synchronize Now. It cannot exceed 128 characters or contain the following special characters: . Step 3. see the documentation for the LDAP directory service.

The Service Manager synchronizes the LDAP security domains with the LDAP directory service every day during the times you set. Users might not be able to log in to application clients. they might not be able to perform tasks. In the LDAP Configuration dialog box. 1. you can schedule the Service Manager to synchronize multiple times a day.ssl. Click OK to confirm that you want to delete the security domain. On the LDAP Configuration dialog box. click the security domain name to view the filter used to import the users and groups and verify that it is the security domain you want to delete. 4. When you delete an LDAP security domain. If users are logged in to application clients when synchronization starts. Note: During synchronization. Deleting an LDAP Security Domain To permanently prohibit users in an LDAP security domain from accessing application clients. By default. click Synchronize Now. import the self-signed certificate into a truststore file and use the INFA_JAVA_OPTS environment variable to specify the truststore file and password: setenv INFA_JAVA_OPTS -Djavax. configure INFA_JAVA_OPTS as a system variable. Using a Self-Signed SSL Certificate You can connect to an LDAP server that uses an SSL certificate signed by a certificate authority (CA). The LDAP Configuration dialog box displays the list of security domains.trustStore=<TrustStoreFile> -Djavax. 2.net. the added times are lost. 3. The synchronization schedule uses a 24-hour time format. To immediately synchronize the users and groups in the security domains with the users and groups in the LDAP directory service. Setting Up LDAP Authentication 65 . You can add as many synchronization times in the day as you require. The duration of the synchronization process depends on the number of users and groups to be synchronized. you can delete the LDAP security domain. To avoid usage disruption. 3. synchronize the security domains during times when most users are not logged in. click the Schedule tab. the Service Manager does not connect to an LDAP server that uses a self-signed certificate. 2. Click the Delete button next to a security domain to delete the security domain. Restart the node for the change to take effect.trustStorePassword=<TrustStorePassword> On Windows. click the Security Domains tab. Click the Add button (+) to add a time.ssl. The Service Manager uses the truststore file to verify the SSL certificate. Click OK to save the synchronization schedule. Note: If you restart the Informatica domain before the Service Manager synchronizes with the LDAP directory service. To use a self-signed certificate. the Service Manager locks the user account it synchronizes. 4. 1.You can schedule the time of day when the Service Manager synchronizes the list of users and groups in the LDAP security domains with the LDAP directory service. the Service Manager deletes all user accounts and groups in the LDAP security domain from the domain configuration database. If the list of users and groups in the LDAP directory service changes often. To ensure that you are deleting the correct security domain.net.

You can use keytool to create a truststore file or to import a certificate to an existing truststore file. The Service Manager can import nested groups that are created in the following manner: ¨ Create the groups under the same organizational units (OU). or the following special characters: . click the Security tab. and add GroupB as a member. GroupC. ¨ Set the relationship between the groups. and delete users in the native security domain. You can also unlock a user account. The roles. see the documentation on the Sun web site: http://java. 2. You can find the keytool utility in the following directory: <PowerCenterClientDir>\CMD_Utilities\PC\java\bin For more information about using keytool.+"###BOT_TEXT###lt;>. 2. Edit GroupA. 3. or delete native users on the Security tab. Adding Native Users Add. and privileges assigned to the user determines the tasks the user can perform within the Informatica domain.sun.2/docs/tooldocs/windows/keytool. 3. The name is not case sensitive and cannot exceed 128 characters. In the Administrator tool. permissions. and add GroupD as a member. You cannot modify the user assignments to LDAP groups.4. For example.keytool is a key and certificate management utility that allows you to generate and administer keys and certificates for use with the SSL security protocol. You can assign roles. edit. and privileges to a user account in the native security domain or an LDAP security domain. 1.com/j2se/1. Edit GroupC. Managing Users You can create. On the Security Actions menu. and GroupD within the same OU./*%?& 66 Chapter 7: Users and Groups . permissions. 1. newline character. Create GroupA. Enter the following details for the user: Property Login Name Description Login name for the user account. You cannot delete or modify the properties of user accounts in the LDAP security domains. click Create User. edit. GroupB.html Using Nested Groups in the LDAP Directory Service An LDAP security domain can contain nested LDAP groups. It cannot include a tab. You cannot import nested LDAP groups into an LDAP security domain that are created in a different way. The login name for a user account must be unique within the security domain to which it belongs. you want to create a nested grouping where GroupB is a member of GroupA and GroupD is a member of GroupC.

email. @ symbol. the details panel displays the properties of the user account and the groups that the user is assigned to. You can change the password and other details for a native user account. Editing General Properties of Native Users You cannot change the login name of a native user. select Change Password. and last name. Phone Telephone number for the user. In the Users section of the Navigator. Enter a new password and confirm. In the Administrator tool. Password Confirm Password Password for the user account. Modify the full name. Do not copy and paste the password. The telephone number cannot include the following special characters: <>“ 4.Property Description The name can include an ASCII space character except for the first and last character. You must retype the password. Enter the password again to confirm. click the Security tab. The combination of the user name. 3. and phone as necessary. and security domain cannot exceed 128 characters. Click OK to save the changes. description. All other space characters are not allowed. the full name property is equivalent to three separate properties named first name. Managing Users 67 . middle name. 5. select a native user account and click Edit. The full name cannot include the following special characters: <>“ Note: In Data Analyzer. To change the password. 2. The Security tab clears the Password and Confirm Password fields. 4. Click OK to save the user account. 1. Full Name Description Description of the user account. Full name for the user account. The description cannot exceed 765 characters or include the following special characters: <>“ Email Email address for the user. After you create a user account. The email address cannot include the following special characters: <>“ Enter the email address in the format UserName@Domain. 6. The password can be from 1 through 80 characters long. Note: Data Analyzer uses the user account name and security domain in the format UserName@SecurityDomain to determine the length of the user login name.

Use the Ctrl or Shift keys to select multiple groups at the same time. select a user account in the Users section of the Navigator and click Disable. select a group name in the All Groups column and click Add. Enabling and Disabling User Accounts Users with active accounts can log in to application clients and perform tasks based on their permissions and privileges. the name of the deleted user appears prefixed by the word "deleted. 1. right-click the user account name in the Users section of the Navigator and select Delete User. expand each group to show all nested groups. the Security tab displays a message that the user account is disabled. When you log in to the Administrator tool. You can assign a user to more than group. When you select a disabled user account. select a native or LDAP user account and click Edit. the Enable button is available.Assigning Users to Native Groups You can assign native or LDAP user accounts to native groups. To disable a user account. you remove any ownership that the user has over folders. 2. To assign a user to a group. Confirm that you want to delete the user account. deployment groups. During subsequent synchronization with the LDAP server. To remove a user from a group. 6. you cannot delete your user account. the user account retains the enabled or disabled status set in the Administrator tool. Deleting Native Users To delete a native user account. You cannot delete the default administrator account. 4. If nested groups do not display in the All Groups column. When you view the history of a versioned object previously owned by a deleted user. Note: When the Service Manager imports a user account from the LDAP directory service. 5. You must disable an LDAP user account in the Administrator tool if you do not want the user to access application clients. To enable the user account. You can enable or disable user accounts in the native or an LDAP security domain. When you disable a user account. After you delete a user. connection objects. When a user account is disabled. You cannot disable the default administrator account. the user cannot log in to the application clients. In the Users section of the Navigator. you can disable their accounts. The Service Manager imports all user accounts as enabled user accounts. it does not import the LDAP attribute that indicates that a user account is enabled or disabled. click the Security tab. the default administrator becomes the owner of all objects owned by the deleted user. or queries. Click the Groups tab. If you do not want users to access application clients temporarily. In the Administrator tool. select a group in the Assigned Groups column and click Remove. click Enable. labels. Deleting Users of PowerCenter When you delete a user who owns objects in the PowerCenter repository." 68 Chapter 7: Users and Groups . Click OK to save the group assignments. You cannot change the assignment of LDAP user accounts to LDAP groups. 3.

A report that uses user-based security uses the security profile of the user who accesses the report. Deleting Users of Metadata Manager When you delete a user who owns shortcuts and folders. Select Reset Password While Unlock to generate a new password for the user after you unlock the account. and personal folders and dashboards associated with the user. 1. Metadata Manager moves the user's personal folder to a folder named Deleted Users owned by the default administrator. have the other user with the same security profile log in and save those reports to the public folder. In the Administrator tool. 5. edit. For example. When you delete a user. with provider-based security and the same report name. If the user is a native user." LDAP Users You cannot add. alert email accounts. Identify all the reports with provider-based security in the public folder owned by UserA. Select the users that you want to unlock. If the user is also locked out of LDAP. 3. However. Before you delete a user. the reports stay in the public folder with the same security. 2. Metadata Manager names the additional folder "Copy (n) of <username>. A report that uses provider-based security uses the security profile of the user who owns the report. This ensures that after you delete the user. Then. Data Analyzer cannot determine the security profile for a report with provider-based security if the report owner does not exist. Click the Unlock button.Deleting Users of Data Analyzer When you delete a user. The user receives the new password in an email. Any shared folders remain shared after you delete the user. Data Analyzer deletes all reports that a user subscribes to based on the security profile of the report. the LDAP administrator must unlock the LDAP user account. Click Account Management. or delete LDAP users in the Administrator tool. you want to delete UserA who has a report in the public folder with provider-based security. Data Analyzer can run a report with user-based security even if the report owner does not exist. Data Analyzer deletes the alerts. Data Analyzer keeps a security profile for each user who subscribes to the report. Data Analyzer does not delete any report in the public folder owned by the user. the administrator can request that the user reset their password before logging back into the domain. click the Security tab. 4. The deleted user's personal folder contains all shortcuts and folders created by the user. You must manage the LDAP user accounts in the LDAP directory service. verify that the reports with provider-based security have a new owner. Managing Users 69 . The user must have a valid email address configured in the domain to receive notifications when their account password has been reset. If the Deleted Users folder contains a folder with the same user name. Unlocking a User Account The domain administrator can unlock a user account that is locked out of the domain. Create or select a user with the same security profile as UserA.

For example. ExportObjects. edit. configure the following environment variables and specify the value in megabytes: ¨ INFA_JAVA_OPTS. and RestoreDomain ¨ infacmd isp ExportDomainObjects.000 5. restart the node for the changes to take effect. To increase the system memory. ImportDomainObjects.Increasing System Memory for Many Users Processing time for an Informatica domain restart. and some infacmd and infasetup commands increases proportionally with the number of users in the Informatica domain. The following table provides the minimum system memory requirements for different amounts of users: Number of Users 1. Determines the system memory used by infasetup. 70 Chapter 7: Users and Groups . You cannot delete or modify the properties of group accounts in the LDAP security domains. You can assign roles. and privileges assigned to the group determines the tasks that users in the group can perform within the Informatica domain. permissions. Configure on each machine where you run infacmd.000 30. Configure on each machine where you run infasetup. Managing Groups You can create. Determines the system memory used by infacmd. and infacmd when you have a large number of users in the domain. The roles.000 20. infasetup. permissions. and privileges to a group in the native or an LDAP security domain. DeleteDomain.000 10. to configure 2048 MB of system memory on UNIX for the INFA_JAVA_OPTS environment variable. Configure on each node where Informatica Services is installed. The number of users affects the processing time of the following commands: ¨ infasetup BackupDomain.000 Minimum System Memory 512 MB (default) 1024 MB 1024 MB 2048 MB 3072 MB After you configure these environment variables. LDAP user synchronization. use the following command: setenv INFA_JAVA_OPTS "-Xmx2048m" On Windows. Determines the system memory used by Informatica Services. configure the variables as system variables. and ImportObjects ¨ infacmd oie ExportObjects and ImportObjects You may need to increase the system memory used by Informatica Services. and delete groups in the native security domain. ¨ INFA_JAVA_CMD_OPTS. ¨ ICMD_JAVA_OPTS.

1. Managing Groups 71 . For example. To change the list of users in the group. click the Users tab. To assign users to the group. All other space characters are not allowed. The Users tab displays the list of users in the domain and the list of users assigned to the group. Parent Group field displays Native indicating that the new group does not belong to a group. 5.+"###BOT_TEXT###lt;>. It cannot include a tab. select a user account in the Assigned Users column and click Remove. You can create multiple levels of native groups. In the Administrator tool. Description of the group. On the Security Actions menu. 2. Parent Group Group to which the new group belongs. In the Groups section of the Navigator. or the following special characters: ./*%? The name can include an ASCII space character except for the first and last character. 6. or remove native groups on the Security tab. newline character. To change the parent of the group. click the Security tab. select a native group and click Edit. 7. 4. the Finance group contains the AccountsPayable group which contains the OfficeSupplies group. the selected group is the parent group. Click Browse to select a different parent group. You can create more than one level of groups and subgroups. 1. click the Security tab. 3. Otherwise. In the Administrator tool. Click OK to save the changes. Editing Properties of a Native Group After you create a group. The group description cannot exceed 765 characters or include the following special characters: <>“ Description 4. Enter the following information for the group: Property Name Description Name of the group. Click OK to save the group. To remove a user from a group. The name is not case sensitive and cannot exceed 128 characters. 3. you can change the description of the group and the list of users in the group. The Finance group is the parent group of the AccountsPayable group and the AccountsPayable group is the parent group of the OfficeSupplies group. Each group can contain other native groups. edit. click Create Group. A native group can contain native or LDAP user accounts or other native groups. Change the description of the group.Adding a Native Group Add. If you select a native group before you click Create Group. 2. You cannot change the name of the group or the parent of the group. select a user account in the All Users column and click Add. you must move the group to another group. 5.

To display the Operating System Profiles Configuration dialog box. Deleting a Native Group To delete a native group. delete.Moving a Native Group to Another Native Group To organize the groups of users in the native security domain. Assign permissions on operating system profiles. and assign permissions to operating system profiles in the Operating System Profiles Configuration dialog box. The name is not case sensitive and must be unique within the domain. edit. it runs workflows with the settings of the operating system profile assigned to the workflow or to the folder that contains the workflow. Create an operating system profile. You can create. It also cannot contain the following special characters: %*+\/. the users in the group lose their membership in the group and all permissions or privileges inherited from group. click Operating System Profiles Configuration on the Security Actions menu. Complete the following steps to configure an operating system profile: 1. To move a native group to another native group. or delete LDAP groups or modify user assignments to LDAP groups in the Administrator tool. edit. Configure the service process variables and environment variables in the operating system profile properties. Create Operating System Profiles Create operating system profiles if the PowerCenter Integration Service uses operating system profiles. When you delete a group. right-click the group name in the Groups section of the Navigator and select Delete Group. The following table describes the properties you configure to create an operating system profile: Property Name Description Name of the operating system profile. right-click the name of a native group in the Groups section of the Navigator and select Move Group. the Service Manager deletes all groups and subgroups that belong to the group. 3. When you delete a group. you can set up nested groups and move a group to another group.?<> 72 Chapter 7: Users and Groups . 2. Managing Operating System Profiles If the PowerCenter Integration Service uses operating system profiles. LDAP Groups You cannot add. You must manage groups and user assignments in the LDAP directory service. It cannot exceed 128 characters or begin with @.

$PMRootDir You cannot edit the name or the system user name after you create an operating system profile. It cannot include spaces or the following special characters: \ / : * ? " < > | [ ] = + . After you delete an operating system profile. It cannot include the following special characters: *?<>“|. This is the root directory for other service process variables. If you do not want to use the operating system user specified in the operating system profile. You can increase performance when the cache directory is a drive local to the PowerCenter Integration Service process. System User Name Name of an operating system user that exists on the machines where the PowerCenter Integration Service runs. It cannot include the following special characters: *?<>“|. The following table describes the properties of an operating system profile: Property Name Description Read-only name of the operating system profile. This is the root directory for other service process variables. Root directory accessible by the node. It cannot include the following special characters: System User Name $PMRootDir Managing Operating System Profiles 73 . $PMBadFileDir Directory for reject files. delete the operating system profile. $PMCacheDir Directory for index and data cache files. Root directory accessible by the node.Property Description The name can contain an ASCII space character except for the first and last character. Properties of Operating System Profiles After you create an operating system profile. Do not use a mapped or mounted drive for cache files. Read-only name of an operating system user that exists on the machines where the PowerCenter Integration Service runs. . The PowerCenter Integration Service runs workflows using the system access of the system user defined for the operating system profile. To edit the properties of an operating system profile. select the profile in the Operating System Profiles Configuration dialog box and then click Edit. All other space characters are not allowed. It cannot include the following special characters: *?<>“|. The name cannot exceed 128 characters. $PMSessionLogDir Directory for session logs. configure the operating system profile properties. assign another operating system profile to the repository folders that the operating system profile was assigned to. The PowerCenter Integration Service runs workflows using the system access of the system user defined for the operating system profile. Note: Service process variables that are set in session properties and parameter files override the operating system profile settings. Default is $PMRootDir/BadFiles. It cannot include the following special characters: *?<>“|. Default is $PMRootDir/SessLogs.

It cannot include the following special characters: *?<>“|. Default is $PMRootDir/Storage. On the Security Actions menu. It cannot include the following special characters: *?<>“|. After you create the profile. $PMStorageDir Directory for run-time files. the Integration Service uses its LD_LIBRARY_PATH environment variable. Default is $PMRootDir/Temp. Click Create Profile. and $PMRootDir. Creating an Operating System Profile 1. 5. The Operating System Profiles Configuration dialog box appears. 6. Enter the User Name. Environment Variables Name and value of environment variables used by the Integration Service at workflow run time. If you do not specify the LD_LIBRARY_PATH environment variable in the operating system profile properties. click Operating System Profiles Configuration. The Integration Service uses the value of its LD_LIBRARY_PATH environment variable to set the environment variables of the child processes generated for the operating system profile. If you specify the LD_LIBRARY_PATH environment variable in the operating system profile properties. Default is $PMRootDir/Cache. the Integration Service appends the value of this variable to its LD_LIBRARY_PATH environment variable. In the Administrator tool. Default is $PMRootDir/ExtProc.Property Description *?<>“|. Workflow recovery files save to the $PMStorageDir configured in the PowerCenter Integration Service properties. It cannot include the following special characters: *?<>“|. 3. It cannot include the following special characters: *?<>“|. 2. 74 Chapter 7: Users and Groups . $PMLookupFileDir Directory for lookup files. Default is $PMRootDir/TgtFiles. Session recovery files save to the $PMStorageDir configured in the operating system profile. you must configure properties. Click the operating system profile you want to configure. $PMTargetFileDir Directory for target files. $PMSourceFileDir Directory for source files. 4. It cannot include the following special characters: *?<>“|. $PMTempDir Directory for temporary files. $PmExtProcDir Directory for external procedures. System User Name. Default is $PMRootDir/SrcFiles. click the Security tab. Default is $PMRootDir/LkpFiles. It cannot include the following special characters: *?<>“|. Click OK.

the administrator can unlock the account. failed logins. To enable the domain to send emails to users when their passwords are reset. Specify the maximum number of consecutive. Web Services Hub Service. 3. Select Disable to disable account lockout. 1. Configuring Account Lockout To configure account lockout. Set the following properties: Property Account Lockout Description Select Enabled to enable account lockout. 11. click Edit. When the administrator unlocks a user account. or PowerCenter Integration Service continually try to restart after a failed login. account lockout is disabled. the domain will eventually lock the associated user account. Select the Permissions tab. and PowerCenter Integration Service are resilient application services that use a user name and password to authenticate with the Model Repository Service or PowerCenter Repository Service. Max Invalid Login Attempts Rules and Guidelines for Account Lockout Consider the following rules and guidelines for account lockout: ¨ If an application service runs under a user account and the wrong password is provided for the application service. A list of all the users with permission on the operating system profile appears. configure the email server settings for the domain. The administrator can specify the number of failed login attempts before the account is locked. Edit the permission and click OK. If the Data Integration Service. Click Edit. 10. the user account can become locked when the application service tries to start. 8. 2.7. Account Lockout 75 . Edit the properties and click OK. By default. The Data Integration Service. Web Services Hub Service. click Security > Account Management. Select the Properties tab and click Edit. In Account Lockout Configuration section. The domain administrator can enable account lockout to prevent hackers from gaining access to the domain. enable account lockout and specify the threshold for number of consecutive. In the Adminstrator tool. the administrator can request that the user reset their password before logging back into the domain. failed logins before the user account is locked. 9. If the account is locked. Account Lockout The domain administrator can configure account lockout to increase domain security.

but account lockout is not enabled in the domain. 76 Chapter 7: Users and Groups . the domain administrator can unlock the domain account and the LDAP administrator can unlock the LDAP account. ¨ If a user is locked out of the domain. to avoid confusion about the account lockout policy.¨ If an LDAP user is locked out of the domain and LDAP. verify that the user is not locked out of LDAP. configure the same number of failed logins for account lockout in the domain and LDAP. ¨ If you enable account lockout in the domain and LDAP.

114 ¨ Troubleshooting Privileges and Roles. 102 ¨ PowerExchange Logger Service Privileges. 103 ¨ Reporting and Dashboards Service Privileges. 103 ¨ Reporting Service Privileges. Privileges Privileges determine the actions that users can perform in application clients. ¨ Data Integration Service privilege. Informatica includes the following privileges: ¨ Domain privileges. Determines actions that users can perform using Informatica Analyst. 109 ¨ Managing Roles. 86 ¨ Model Repository Service Privilege. 85 ¨ Metadata Manager Service Privileges. 89 ¨ PowerCenter Repository Service Privileges. ¨ Analyst Service privilege. 109 ¨ Assigning Privileges and Roles to Users and Groups. 77 ¨ Domain Privileges. This privilege also determines whether users can drill down and export profile results. 112 ¨ Viewing Users with Privileges for a Service. 114 Privileges and Roles Overview You manage user security with privileges and roles. Determines actions on applications that users can perform using the Administrator tool and the infacmd command line program. 77 . 79 ¨ Analyst Service Privileges. 89 ¨ PowerExchange Listener Service Privileges.CHAPTER 8 Privileges and Roles This chapter includes the following topics: ¨ Privileges and Roles Overview. 84 ¨ Data Integration Service Privileges. Determine actions on the Informatica domain that users can perform using the Administrator tool and the infacmd and pmrep command line programs.

Determine actions that users can perform using Jaspersoft. you can select a privilege group to assign all privileges in the group. For example. ¨ Model Repository Service privilege. You assign privileges to users and groups on the Security tab of the Administrator tool. For more information. Determine actions that users can perform using Metadata Manager. Privilege Groups The domain and application service privileges are organized into privilege groups. Tip: When you assign privileges to users and user groups. and application services. ¨ PowerExchange application service privileges. Tip: If you organize users into groups and then assign roles and permissions to the groups. Includes privileges to manage users. basic user. roles. Includes privileges to log in to the Administrator tool. For example. the domain privileges include the following privilege groups: ¨ Tools. Workflow Monitor. You assign privileges to users and groups for application services. Roles A role is a collection of privileges that you assign to a user or group. groups. You assign a role to users and groups for the domain and for application services in the domain. The Administrator tool organizes privileges into levels. the Administrator tool also assigns any included privileges. move the user to another group. Some privileges include other privileges. Determine PowerCenter repository actions that users can perform using the Repository Manager. grids. nodes. You can assign different privileges to a user for each application service of the same service type. A privilege group is an organization of privileges that define common user actions. the PowerCenter Developer role includes all the PowerCenter Repository Service privileges or actions that a developer performs. see the Informatica How-To Library article Using Groups and Roles to Manage Informatica Access Control. You do not need to reassign privileges. and permissions. administrator. add the user to a group. ¨ Domain Administration. Designer. A privilege is listed below the privilege that it includes. roles. you can simplify user administration tasks. licenses.¨ Metadata Manager Service privileges. Determine actions that users can perform on the PowerExchange Listener Service and PowerExchange Logger Service using the infacmd pwx commands. Includes privileges to manage the domain. or advanced user. ¨ Reporting Service privileges. 78 Chapter 8: Privileges and Roles . and the pmrep and pmcmd command line programs. Determines actions on projects that users can perform using Informatica Analyst and Informatica Developer. When you assign a privilege to users and groups. whether the user is a developer. If a new user joins the organization. ¨ Reporting and Dashboards Service privileges. and privileges. if a user changes positions within the organization. For example. Determine reporting actions that users can perform using Data Analyzer. folders. ¨ Security Administration. Each user within an organization has a specific role. The users inherit the roles and permissions assigned to the group. Workflow Manager. ¨ PowerCenter Repository Service privileges.

folders. to view monitoring for integration objects. nodes. Some security management tasks are determined by the Administrator role. Includes privileges to manage the domain. Domain Privileges 79 . ¨ Delete operating system profiles.Edit and remove the privileges and roles assigned to users and groups. application services. groups. The following table lists the required permissions and the actions that users can perform with the Grant Privileges and Roles privilege: Permission On Domain or application service Grants Users the Ability To . licenses. Note: To complete security management tasks in the Administrator tool. and privileges. and connections. users must also have the Access Informatica Administrator privilege.Domain Privileges Domain privileges determine the actions that users can perform using the Administrator tool and the infacmd and pmrep command line programs. ¨ Grant permission on operating system profiles. Grant Privileges and Roles Privilege Users assigned the Grant Privileges and Roles privilege can assign privileges and roles to users and groups. The following table describes each domain privilege group: Privilege Group Security Administration Description Includes privileges to manage users. and to access monitoring. A user assigned the Administrator role for the domain can complete the following tasks: ¨ Create operating system profiles. Domain Administration Monitoring Tools Security Administration Privilege Group Privileges in the Security Administration privilege group and domain object permissions determine the security management actions users can perform. Includes privileges to configure monitoring preferences. Includes privileges to log in to the Administrator tool. . grids.Assign privileges and roles to users and groups for the domain or application service. not by privileges or permissions. roles.

A user assigned the Administrator role for the domain can complete the following tasks: ¨ Configure domain properties. Edit operating system profile properties. and Roles privilege: Permission On n/a Grants Users the Ability To . View grid properties. ¨ View user activity log events. Groups.Import LDAP users and groups. Users assigned domain object permissions but no privileges can complete some domain management tasks. View application service properties and log events. The following table lists the actions that users can perform when they are assigned domain object permissions only: Permission On Domain Grants Users the Ability To . Groups. ¨ Shut down the domain.Configure LDAP authentication for the domain.Create. . Some domain management tasks are determined by the Administrator role. Groups. . ¨ Receive domain alerts. ¨ Manage and purge log events. The Manage Users. and Roles Privilege Users assigned the Manage Users. not by privileges or permissions. Run the Web Services Report. View node properties.View domain properties and log events. and roles.Configure the global settings. ¨ Grant permission on the domain. and roles. View folder properties. groups. ¨ Run the License Report. and Roles privilege can configure LDAP authentication and manage users. The following table lists the required permissions and the actions that users can perform with the Manage Users. Folder Application service License object Grid Node Web Services Hub 80 Chapter 8: Privileges and Roles . Operating system profile Domain Administration Privilege Group Domain management actions that users can perform depend on privileges in the Domain Administration group and permissions on domain objects. edit. View license object properties. Groups. and Roles privilege includes the Grant Privileges and Roles privilege. groups.Manage Users. . and delete users.

.Grant permission on application services. Move application services or license objects from one folder to another. Manage Service Execution Privilege Users assigned the Manage Service Execution privilege can enable and disable application services and receive application service alerts. move. . .Upgrade the content of the Metadata Manager Service. The Manage Services privilege includes the Manage Service Execution privilege. users must also have the Access Informatica Administrator privilege. Create and delete audit trail tables.Note: To complete domain management tasks in the Administrator tool. node or grid where application service runs. Restore the PowerCenter repository for Metadata Manager. The following table lists the required permissions and the actions that users can perform with the Manage Service Execution privilege: Permission On Application service Grants Users the Ability To . and grant permission on application services and license objects. remove. Create application services.Configure application services.Create and delete Metadata Manager repository content. Original and destination folders Domain or parent folder and application service Analyst Service Metadata Manager Service Metadata Manager Service PowerCenter Repository Service Domain Privileges 81 . Manage Services Privilege Users assigned the Manage Services privilege can create.Enable and disable application services and service processes. configure. . users must also have permission on the associated PowerCenter Integration Service and PowerCenter Repository Service. Remove application services. .Receive application service alerts. The following table lists the required permissions and the actions that users can perform with the Manage Services privilege: Permission On Domain or parent folder Domain or parent folder. license object. To enable and disable a Metadata Manager Service. and any associated application service Application service Grants Users the Ability To Create license objects.

. . Perform an advanced purge of object versions at the repository level in the PowerCenter Repository Manager. . move. and delete reusable metadata extensions in the PowerCenter Repository Manager.Create. Send PowerCenter repository notifications to users. delete.Configure and shut down nodes and grids. and upgrade the PowerCenter repository. . Configure data lineage for the PowerCenter repository. Enable version control for the PowerCenter repository. and grant permission on nodes and grids.Edit license objects. Manage a PowerCenter repository domain. Create and delete PowerCenter repository content. Copy content from another PowerCenter repository.Change the source analyzer. Update PowerCenter repository statistics. The following table lists the required permissions and the actions that users can perform with the Manage Nodes and Grids privilege: Permission On Domain or parent folder Domain or parent folder and nodes assigned to the grid Node or grid Grants Users the Ability To Create nodes. Run the PowerCenter repository in exclusive mode. edit. Back up. Run the PowerCenter Integration Service in safe mode. remove. Assign a license to an application service.Create and delete model repository content. restore. Close user connections and release PowerCenter repository locks. 82 Chapter 8: Privileges and Roles . restore. and upgrade the content of the Data Analyzer repository. shut down. Create grids. Remove license objects.Grant permission on license objects. and re-index the search index. License object License object and application service Domain or parent folder and license object Manage Nodes and Grids Privilege Users assigned the Manage Nodes and Grids privilege can create. . configure. .Back up.Permission On Model Repository Service Grants Users the Ability To . Register and unregister PowerCenter repository plug-ins. .Grant permission on nodes and grids.Create and delete the content of the Data Analyzer repository. Create. PowerCenter Integration Service PowerCenter Repository Service Reporting Service .

.Grant permission on folders. edit. Domain Privileges 83 . move. Developer tool. Remove nodes and grids. Move folders from one parent folder to another. Requires execute permission on connection. and delete connections. The following table lists the required permissions and the actions that users can perform with the Manage Connections privilege: Permission n/a Write on connection Grant on connection Grants Users the Ability To Create connections. or profile. and infacmd command line program. and grant permission on domain folders. Manage Domain Folders Privilege Users assigned the Manage Domain Folders privilege can create. Remove folders. Requires read permission on connection. remove. Analyst tool. Grant and revoke permissions on connections. edit. ¨ Preview data or run a mapping. Original and destination folders Domain or parent folder and folder being removed Manage Connections Privilege Users assigned the Manage Connections privilege can create. Copy. . The following table lists the required permissions and the actions that users can perform with the Manage Domain Folders privilege: Permission On Domain or parent folder Folder Grants Users the Ability To Create folders. Users can also copy connections in the Developer tool and can grant permissions on connections in the Administrator tool and infacmd command line program. scorecard. Monitoring Privilege Group The privileges in the Monitoring group determine which users can view and configure monitoring. edit.Permission On Original and destination folders Domain or parent folder and node or grid Grants Users the Ability To Move nodes and grids from one folder to another. and delete connections in the Administrator tool.Edit folders. Users assigned connection permissions but not the Manage Connections privilege can perform the following connection management actions: ¨ View all connection metadata. except passwords.

The following table lists the required permissions and the actions that users can perform with the privilege in the Tools group: Privilege Access Informatica Administrator Permission n/a Grants Users the Ability To . To run infacmd commands or to access the read-only view of the Monitoring tab. To access the read-only view of the Monitoring tab.Log in to the Administrator tool.Export log events. Access the monitoring feature from the Developer tool. Analyst Service Privileges The Analyst Service privilege determines actions that licensed users can perform on projects using the Analyst tool. Access the monitoring feature from the Administration tool. To complete tasks in the Administrator tool. .Abort jobs. n/a n/a n/a n/a n/a n/a n/a Displays jobs of other users.View logs about a job. . .Manage their own user account in the Administrator tool. Tools Privilege Group The privilege in the domain Tools group determines which users can access the Administrator tool. Access the monitoring feature from the Analyst tool. . View statistics for domain objects.Reissue mapping jobs. users must have the Access Informatica Administrator privilege. users do not need the Access Informatica Administrator privilege. Configure preferences for monitoring statistics and reports. View reports for domain objects. . 84 Chapter 8: Privileges and Roles . users do not need the Access Informatica Administrator privilege.The following table lists the required permissions and the actions that users can perform with the privileges in the Monitoring group: Privilege Configure Global Settings Configure Statistics and Reports View Jobs of Other Users View Statistics View Reports Access from Analyst Tool Access from Developer Tool Access from Administrator Tool Allow Actions for Jobs Permission On Domain Domain Grants Users the Ability To Configure the global settings.

Drill down profiling results.Configure application properties. The following table lists the required permissions and the actions that users can perform with the privilege in the Application Administration privilege group: Privilege Name Manage Applications Permission On Data Integration Service Grants Users the Ability To . Grants Users the Ability to Run profiles and scorecards for licensed users in the Analyst tool. Access mapping specifications for licensed users in the Analyst tool. The following table lists the required permissions and the actions that users can perform with the privilege in the Profiling Administration privilege group: Privilege Name Drilldown and Export Results Permission On Read on project Execute on relational data source connection is also required to drill down on live data Grants Users the Ability To .The following table lists the privileges and permissions required to manage projects and objects in projects: Privilege Run Profiles and Scorecards Permission Read on projects. Load Mapping Specification Results Write on projects.Find an application. .Deploy an application to a Data Integration Service and resolve name conflicts. . Load the results of a mapping specification for licensed users to a table or flat file. Data Integration Service Privileges The Data Integration Service privileges determine actions that users can perform on applications using the Administrator tool and the infacmd command line program.Start an application after deployment.Start or stop objects in an application. Note: Selecting this privilege also grants the Access Mapping Specification privilege by default. Data Integration Service Privileges 85 .Export profiling results. . .Backup and restore an application to a file. Access Mapping Specifications Read on projects. They also determine whether users can drill down and export profile results using the Analyst tool and the Developer tool. . .

and business terms.Run data lineage analysis on metadata objects. Load Model Security Catalog Privilege Group The privileges in the Catalog privilege group determine the tasks that users can perform in the Browse page of the Metadata Manager interface. View profiling information for metadata objects in the catalog from a relational source.Search the metadata catalog. A user with the privilege to perform certain actions requires permissions to perform the action on a particular object. Includes privileges to manage objects in the Model page of the Metadata Manager interface. The following table lists the privileges in the Catalog privilege group and the permissions required to perform a task on an object: Privilege Share Shortcuts Includes Privileges n/a Permission Write Grants Users the Ability to Share a folder that contains a shortcut with other users and groups. Includes privileges to manage objects in the Load page of the Metadata Manager interface. . categories. The following table describes each Metadata Manager privilege group: Privilege Group Catalog Description Includes privileges to manage objects in the Browse page of the Metadata Manager interface. Configure permissions on the Security tab of the Metadata Manager application. categories. . View Metadata Manager reports in Data Analyzer. . and business terms. View related catalogs. Includes privileges to manage objects in the Security page of the Metadata Manager interface.Run data lineage analysis from the PowerCenter Designer. View Lineage n/a Read View Related Catalogs View Reports View Profile Results n/a n/a n/a Read Read Read View Catalog n/a Read View Relationships n/a Read 86 Chapter 8: Privileges and Roles . . Users must also have read permission on the PowerCenter repository folder.Metadata Manager Service Privileges Metadata Manager Service privileges determine the Metadata Manager actions that users can perform using Metadata Manager.View resources and metadata objects in the metadata catalog. View relationships for metadata objects.

edit. . edit. Import related catalog objects and related terms for a business glossary. Manage Objects Write Load Privilege Group The privileges in the Load privilege group determine the tasks users can perform in the Load page of the Metadata Manager interface. Metadata Manager Service Privileges 87 . Add comments for metadata objects.Draft/Propose Business Terms . You cannot configure permissions on resources. . edit. edit.Search business glossaries. . Import and export a business glossary. and business terms. . categories. and business terms. Users must also have the Manage Resource privilege. Users must also have the View Model privilege. and delete relationships for custom metadata objects.Create. and business terms. . and business terms.Privilege Manage Relationships Includes Privileges View Relationships Permission Write Grants Users the Ability to Create. and delete a business glossary. edit. and delete links for metadata objects. and business terms. categories. categories. categories. including categories and business terms. View links for metadata objects.View Comments n/a Write View Links Read Manage Links View Links Write View Glossary n/a Read Draft/Propose Business Terms Manage Glossary View Glossary Write .Post Comments .View Glossary n/a Write Create.Edit metadata objects in the catalog. categories.Create.View business glossaries in the Business Glossary view. Create. Delete comments for metadata objects. Draft and propose business terms. View comments for metadata objects. View Comments n/a Read Post Comments View Comments Write Delete Comments . and delete custom metadata resources. and business terms. categories. and delete custom metadata objects.

edit. and add schedules to resources. The following table lists the privileges required to manage models: Privilege Includes Privileges n/a Permission Grants Users the Ability to View Model n/a Open models and classes. By default.Purge Metadata . the Manage Catalog Permissions privilege in the Security privilege group is assigned to the Administrator.View Resource n/a Model Privilege Group The privileges in the Model privilege group determine the tasks users can perform in the Model page of the Metadata Manager interface.Create links between objects in connected resources for data lineage. . 88 Chapter 8: Privileges and Roles . You can assign the Manage Catalog Permissions privilege to other users. You cannot configure permissions on a model. or a user with the Administrator role on the Metadata Manager Service. .Configure search indexing for resources. Load Resource View Resource n/a Manage Schedules View Resource n/a Purge Metadata View Resource n/a Manage Resource . Create. edit. and delete resources. Remove metadata for a resource from the Metadata Manager warehouse.View resources and resource properties in the Metadata Manager warehouse.Load metadata for a resource into the Metadata Manager warehouse. Import and export custom models and modified packaged models. and delete custom models. Add attributes to packaged models. Create and edit schedules. Create. . and view model and class properties. View relationships and attributes for classes.Download Metadata Manager agent installer. Manage Model View Model n/a Export/Import Models View Model n/a Security Privilege Group The privilege in the Security privilege group determines the tasks users can perform on the Security tab of the Metadata Manager interface.The following table lists the privileges required to manage an instance of a resource in the Metadata Manager warehouse: Privilege View Resource Includes Privileges n/a Permission n/a Grants Users the Ability to . .

and delete data domains in data domain glossary. . view the names of projects for which users do not have read permission. . . categories.Create.Assign users and groups permissions on resources. Grant and revoke permissions on projects for users and groups. Workflow Manager. n/a Manage Data Domains Create Project Grant on project n/a n/a Show Security Details n/a PowerCenter Repository Service Privileges PowerCenter Repository Service privileges determine PowerCenter repository actions that users can perform using the PowerCenter Repository Manager. metadata objects. metadata objects. and the pmrep and pmcmd command line programs. The following table lists the required permissions and the actions that users can perform with the Model Repository Service privilege: Privilege n/a n/a Permission Read on project Write on project Grants Users the Ability To View projects and objects in projects.Edit projects. and delete objects in projects. Model Repository Service Privilege The Model Repository Service privilege determines actions that users can perform on projects using Informatica Analyst and Informatica Developer.Create projects. and business terms.Delete projects.The following table lists the privilege required to manage Metadata Manager security: Privilege Includes Privileges n/a Permission Grants Users the Ability to Manage Catalog Permissions Full control . . Create.Upgrade the Model Repository Service using the Actions menu.Edit permissions on resources. edit. Model Repository Service Privilege 89 . . . In error and warning message details. Workflow Monitor. Designer. and business terms. edit. categories. The Model Repository Service privilege and the model repository object permissions determine the tasks that users can complete on projects and objects in projects.

Connect to the PowerCenter repository using the Workflow Monitor. For example. Includes privileges to manage business components. tasks. .Run pmrep commands. The following table lists the actions that users can perform for the privileges in the Tools group: Privilege Access Designer Access Repository Manager Access Workflow Manager Access Workflow Monitor Permission n/a n/a Grants Users the Ability To Connect to the PowerCenter repository using the Designer. and target definitions. . users must have the Administrator role for the associated PowerCenter Repository Service.Connect to the PowerCenter Integration Service in the Workflow Monitor. workflows. The appropriate privilege in the Tools privilege group is required for all users completing tasks in PowerCenter Client tools and command line programs. n/a n/a Note: When the PowerCenter Integration Service runs in safe mode. edit. mapplets. ¨ Create. . .Connect to the PowerCenter repository using the Workflow Manager. and delete reusable metadata extensions. mappings. . labels. source definitions. and worklets. Folders Design Objects Sources and Targets Run-time Objects Global Objects Users must have the Manage Services domain privilege and permission on the PowerCenter Repository Service to perform the following actions in the Repository Manager: ¨ Perform an advanced purge of object versions at the PowerCenter repository level. they can still perform some actions on the object. Tools Privilege Group The privileges in the PowerCenter Repository Service Tools privilege group determine the PowerCenter Client tools and command line programs that users can access. transformations. a user has 90 Chapter 8: Privileges and Roles . dimensions. For example. Includes privileges to manage connection objects. Includes privileges to manage cubes. Includes privileges to manage session configuration objects. mapping parameters and variables. . to create folders in the Repository Manager. If users have a privilege in the Tools privilege group and permission on a PowerCenter repository object but not the privilege to modify the object type. and user-defined functions. Includes privileges to manage repository folders.The following table describes each privilege group for the PowerCenter Repository Service: Privilege Group Tools Description Includes privileges to access PowerCenter Client tools and command line programs. deployment groups.Connect to the PowerCenter repository using the Repository Manager. a user must have the Create Folders and Access Repository Manager privileges.Remove a PowerCenter Integration Service from the Workflow Manager. and queries.

Users assigned folder permissions but no privileges can perform some folder management actions. ¨ Change the folder owner. ¨ Configure folder permissions. ¨ Delete the folder. ¨ Edit the folder name and description. Some folder management tasks are determined by folder ownership and the Administrator role. ¨ Designate the folder to be shared. Requires permission on the operating system profile. The following table lists the required permissions and the actions that users can perform with the Create Folders privilege: Permission n/a Grants Users the Ability To Create folders. Folders Privilege Group Folder management actions are determined by privileges in the Folders privilege group. Users perform folder management actions in the Repository Manager and with the pmrep command line program. PowerCenter Repository Service Privileges 91 . The user can view objects in the folders and compare the folders. users must also have the Access Repository Manager privilege. The following table lists the actions that users can perform when they are assigned folder permissions only: Permission Read on folder Grants Users the Ability To . . The user does not have any of the privileges in the Folders privilege group. Create Folders Privilege Users assigned the Create Folders privilege can create PowerCenter repository folders. Note: To perform actions on folders. The folder owner or a user assigned the Administrator role for the PowerCenter Repository Service can complete the following folder management tasks: ¨ Assign operating system profiles to folders if the PowerCenter Integration Service uses operating system profiles.View objects in folders.the Access Repository Manager privilege and read permission on some folders.Compare folders. not by privileges or permissions. and domain object permissions. PowerCenter repository object permissions.

The following table lists the required permissions and the actions that users can perform with the Copy Folders privilege: Permission Read on folder Grants Users the Ability To Copy folders within the same PowerCenter repository or to another PowerCenter repository. Manage Folder Versions If you have a team-based development option.Change the status of folders.Perform an advanced purge of object versions at the folder level.Copy Folders Privilege Users assigned the Copy Folders privilege can copy folders within a PowerCenter repository or to another PowerCenter repository. Users can change the status of folders and perform an advanced purge of object versions at the folder level. Design Objects Privilege Group Privileges in the Design Objects privilege group and PowerCenter repository object permissions determine actions users can perform on the following design objects: ¨ Business components ¨ Mapping parameters and variables ¨ Mappings ¨ Mapplets ¨ Transformations ¨ User-defined functions 92 Chapter 8: Privileges and Roles . . Users must also have the Create Folders privilege in the destination repository. assign users the Manage Folder Versions privilege in a versioned PowerCenter repository. The following table lists the required permissions and the actions that users can perform with the Manage Folder Versions privilege: Permission Read and Write on folder Grants Users the Ability To .

Copy design objects to another PowerCenter repository. Edit. Note: To perform actions on design objects. and Delete Design Objects Privilege Users assigned the Create. Generate code for Custom transformation and external procedures. mappings. PowerCenter Repository Service Privileges 93 . edit. users must also have the appropriate privilege in the Tools privilege group. Users must also have the Create. and design object history. mapping variables. Create. mapping parameters.Users assigned permissions but no privileges can perform some actions for design objects. - Read on shared folder Read and Write on destination folder Create shortcuts. Edit. and Delete Design Objects privilege: Permission Read on original folder Grants Users the Ability To . Export design objects. and user-defined functions. Receive PowerCenter repository notification messages. Run data lineage on design objects. Edit.Copy design objects from one folder to another. The following table lists the actions that users can perform when they are assigned permissions only: Permission Read on folder Grants Users the Ability To Compare design objects. View design objects. and Delete Design Objects privilege can create. and Delete Design Objects privilege in the destination repository. transformations. Edit. Search for design objects. Users must also have the View Lineage privilege for the Metadata Manager Service and read permission on the metadata objects in the Metadata Manager catalog. Copy design objects as an image. mapplets. and delete business components. . design object dependencies. The following table lists the required permissions and the actions that users can perform with the Create.

Recover deleted design objects. and Delete Sources and Targets privilege. Edit. Edit.Revert to a previous design object version. and user-defined functions.Generate business content integration mappings. Users must also have the Create. The following table lists the required permissions and the actions that users can perform with the Manage Design Object Versions privilege: Permission Read and Write on folder Grants Users the Ability To . . Edit. . Edit. and delete data profiles and launch the Profile Manager. . . and purge design object versions. .Purge versions of design objects. Users must also have the Create.Change comments for a versioned design object. edit.Check in and undo checkouts of design objects checked out by other users. and Delete Sources and Targets privileges. and Delete Sources and Targets privilege. mapplets. and Delete Run-time Objects and Create. edit. . and Delete Design Objects privilege. The Manage Design Object Versions privilege includes the Create. .Create. .Validate mappings. recover. . . . Users can change the status.Copy and paste design objects in the same folder. Users must also have the Create. Manage Design Object Versions If you have a team-based development option. Users must also have the Create. . . Edit. Users can also check in and undo checkouts made by other users.Generate and clean SAP ABAP programs.Change the status of design objects. Edit.Import design objects using the Repository Manager.Check out design objects. assign users the Manage Design Object Versions privilege in a versioned PowerCenter repository. . Sources and Targets Privilege Group Privileges in the Sources and Targets privilege group and PowerCenter repository object permissions determine actions users can perform on the following source and target objects: ¨ Cubes ¨ Dimensions ¨ Source definitions ¨ Target definitions 94 Chapter 8: Privileges and Roles .Create. and delete design objects. and Delete Run-time Objects privilege.Check in and undo a checkout of design objects checked out by their own user account.Import design objects using the Designer.Permission Read and Write on destination folder Read and Write on folder Grants Users the Ability To .

and Delete Sources and Targets privilege can create. . Read on shared folder Read and Write on destination folder Note: To perform actions on source and target objects. Edit.Change comments for a versioned source or target object. Receive PowerCenter repository notification messages. edit. . Users must also have the Create. edit. . . Edit. and source and target object history. .Check in and undo a checkout of source and target objects checked out by their own user account. The following table lists the actions that users can perform when they are assigned permissions only: Permission Read on folder Grants Users the Ability To Compare source and target objects. .Search for source and target objects. . and Delete Sources and Targets privilege: Permission Read on original folder Read and Write on destination folder Grants Users the Ability To .Generate and execute SQL to create targets in a relational database. . and Delete Sources and Targets Privilege Users assigned the Create. source and target object dependencies.Check out source and target objects.Import SAP functions. and Delete Runtime Objects privileges.Copy source and target objects to another PowerCenter repository. Export source and target objects. Create. . Edit. Users must also have the Create. Users must also have the View Lineage privilege for the Metadata Manager Service and read permission on the metadata objects in the Metadata Manager catalog. users must also have the appropriate privilege in the Tools privilege group. Edit. and target definitions. Edit. dimensions. . Preview source and target data.Import source and target objects using the Designer.Import source and target objects using the Repository Manager. Edit.Users assigned permissions but no privileges can perform some actions for source and target objects. . Read and Write on folder PowerCenter Repository Service Privileges 95 . source definitions. and delete cubes. and Delete Design Objects privilege. Edit. . Run data lineage on source and target objects. and Delete Sources and Targets privilege in the destination repository.Revert to a previous source or target object version. and delete source and target objects. Create shortcuts.Create. and Delete Design Objects and Create.Copy and paste source and target objects in the same folder.View source and target objects. The following table lists the required permissions and the actions that users can perform with the Create. . Users must also have the Create.Copy source and target objects to another folder.

and run-time object history. . Receive PowerCenter repository notification messages. users must have the Administrator role for the associated PowerCenter Repository Service. Users assigned permissions but no privileges can perform some actions for run-time objects. users must also have the appropriate privilege in the Tools privilege group.Check in and undo checkouts of source and target objects checked out by other users. The following table lists the actions that users can perform when they are assigned permissions only: Permission Read on folder Grants Users the Ability To Compare run-time objects. Export run-time objects. Search for run-time objects. and purge versions of source and target objects. and Delete Sources and Targets privilege. The following table lists the required permissions and the actions that users can perform with the Manage Source and Target Versions privilege: Permission Read and Write on folder Grants Users the Ability To . A user assigned the Administrator role for the PowerCenter Repository Service can delete a PowerCenter Integration Service from the Navigator of the Workflow Manager. Use mapping parameters and variables in a session. not by privileges or permissions.Manage Source and Target Versions Privilege If you have a team-based development option. View run-time objects. When the PowerCenter Integration Service runs in safe mode. Note: To perform actions on run-time objects. Run-time Objects Privilege Group Privileges in the Run-time Objects privilege group. Users can change the status. and domain object permissions determine actions users can perform on the following run-time objects: ¨ Session configuration objects ¨ Tasks ¨ Workflows ¨ Worklets Some run-time object tasks are determined by the Administrator role. assign users the Manage Source and Target Versions privilege in a versioned PowerCenter repository. 96 Chapter 8: Privileges and Roles . run-time object dependencies. PowerCenter repository object permissions. Users can also check in and undo checkouts made by other users.Change the status of source and target objects. Edit.Purge versions of source and target objects. Read and Execute on folder Stop and abort tasks and workflows started by their own user account. recover. . The Manage Source and Target Versions privilege includes the Create.Recover deleted source and target objects. .

workflows. . and Delete Design Objects and Create. Edit.Assign a service level to a workflow. workflows. .Copy tasks. tasks. Edit.Check in and undo a checkout of run-time objects checked out by their own user account.Change comments for a versioned run-time object. . workflows. and Delete Run-time Objects privilege can create. edit. and purge run-time object versions. .Replace a relational database connection for all sessions that use the connection. and worklets. Edit. . Users must also have the Create. assign users the Manage Run-time Object Versions privilege in a versioned PowerCenter repository. Users must also have the Create.Import run-time objects using the Repository Manager.Assign a PowerCenter Integration Service to a workflow in the workflow properties.Create and edit tasks. .Copy tasks. workflows. . Edit. Users can also check in and undo checkouts made by other users. The following table lists the required permissions and the actions that users can perform with the Create.Delete and validate tasks. workflows. and Delete Run-time Objects privilege. Edit. and worklets. and delete session configuration objects. and Delete Design Objects privilege.Create. and delete session configuration objects. .Revert to a previous object version. PowerCenter Repository Service Privileges 97 . Edit. Edit. and worklets in the same folder. . and Delete Run-time Objects privilege in the destination repository. Edit.Check out run-time objects. recover.Copy and paste tasks.Import run-time objects using the Workflow Manager. and delete data profiles and launch the Profile Manager. . Users can change the status. . . . edit. and Delete Sources and Targets privileges. and worklets. and Delete Run-time Objects Privilege Users assigned the Create. and Delete Run-time Objects privilege: Permission Read on original folder Read and Write on destination folder Grants Users the Ability To . Read and Write on folder Read and Write on folder Read on connection object Manage Run-time Object Versions Privilege If you have a team-based development option. or worklets to another PowerCenter repository. Users must also have the Create.Create. .Create. or worklets from one folder to another. edit. The Manage Run-time Object Versions privilege includes the Create. workflows. .

View properties of run-time objects in the Workflow Monitor. .The following table lists the required permissions and the actions that users can perform with the Manage Runtime Object Versions privilege: Permission Read and Write on folder Grants Users the Ability To . Write. Read and Execute on folder Debug a mapping by using an existing non-reusable session. Users must also have the Create. The Execute Run-time Objects privilege includes the Monitor Run-time Objects privilege. The following table lists the required permissions and the actions that users can perform with the Execute Runtime Objects privilege: Permission Read and Execute on folder Grants Users the Ability To Assign a PowerCenter Integration Service to a workflow using the Service menu or the Navigator.Recover deleted run-time objects. . users must have the Administrator role for the associated PowerCenter Repository Service. and Execute on folder Read and Execute on connection object 98 Chapter 8: Privileges and Roles .View run-time object and performance details in the Workflow Monitor. When the PowerCenter Integration Service runs in safe mode.View session and workflow logs in the Workflow Monitor. Read. and recover tasks and workflows. Execute Run-time Objects Privilege Users assigned the Execute Run-time Objects privilege can start. Monitor Run-time Objects Privilege Users assigned the Monitor Run-time Objects privilege can Monitor workflows and tasks in the Workflow Monitor. cold start.Check in and undo checkouts of run-time objects checked out by other users. . . Edit.Purge versions of run-time objects. users must have the Administrator role for the associated PowerCenter Repository Service.Change the status of run-time objects. . Debug a mapping by creating a debug session instance or by using an existing reusable session. When the PowerCenter Integration Service runs in safe mode. The following table lists the required permissions and the actions that users can perform with the Monitor Run-time Objects privilege: Permission Read on folder Grants Users the Ability To . and Delete Run-time Objects privilege.

The Manage Run-time Object Execution privilege includes the Execute Run-time Objects privilege and the Monitor Run-time Objects privilege. When the PowerCenter Integration Service runs in safe mode. users must have the Administrator role for the associated PowerCenter Repository Service. Read. users must also have permission on the operating system profile. If the PowerCenter Integration Service uses operating system profiles. Edit. .Unschedule workflows. Read and Execute on folder Read and Execute on connection object Manage Run-time Object Execution Privilege Users assigned the Manage Run-time Object Execution privilege can schedule and unschedule workflows. When the PowerCenter Integration Service runs in safe mode. . abort. PowerCenter Repository Service Privileges 99 .Permission Read and Execute on connection object Grants Users the Ability To When the PowerCenter Integration Service runs in safe mode. Users can also stop.Stop and abort tasks that were recovered automatically. . If the PowerCenter Integration Service uses operating system profiles. users must have the Administrator role for the associated PowerCenter Repository Service. users must also have permission on the operating system profile. users must have the Administrator role for the associated PowerCenter Repository Service. users must also have permission on the operating system profile. .Create and edit a reusable scheduler from the Workflows > Schedulers menu. users must have the Administrator role for the associated PowerCenter Repository Service.Recover tasks that were recovered automatically.Edit a non-reusable scheduler from the workflow properties.Edit a reusable scheduler from the workflow properties. Write.Recover tasks and workflows started by other users.Stop and abort tasks and workflows started by other users. and Delete Runtime Objects privilege. Users must also have the Create. . and restart tasks and workflows. and recover tasks and workflows started by other users.Recover tasks and workflows started by their own user account. Read and Execute on folder Read and Execute on connection object . . . cold start.Start. . When the PowerCenter Integration Service runs in safe mode. and Execute on folder Read and Execute on connection object . If the PowerCenter Integration Service uses operating system profiles. The following table lists the required permissions and the actions that users can perform with the Manage Runtime Object Execution privilege: Permission Read and Execute on folder Read and Execute on folder Grants Users the Ability To Truncate workflow and session log entries.

Edit connection objects. The following table lists the actions that users can perform when they are assigned permissions only: Permission Read on connection object Read on deployment group Read on label Read on query Read and Write on connection object Read and Write on label Read and Write on query Read and Execute on query Read on folder Read and Execute on label Grants Users the Ability To View connection objects. Edit and lock labels. Run object queries. View labels.Permission Grants Users the Ability To When the PowerCenter Integration Service runs in safe mode. 100 Chapter 8: Privileges and Roles . users must also have the appropriate privilege in the Tools privilege group. ¨ Delete the global object. Global Objects Privilege Group Privileges in the Global Objects privilege group and PowerCenter repository object permissions determine actions users can perform on the following global objects: ¨ Connection objects ¨ Deployment groups ¨ Labels ¨ Queries Some global object tasks are determined by global object ownership and the Administrator role. View object queries. Users assigned permissions but no privileges can perform some actions for global objects. users must have the Administrator role for the associated PowerCenter Repository Service. ¨ Change the global object owner. Apply labels and remove label references. View deployment groups. Edit and validate object queries. The global object owner or a user assigned the Administrator role for the PowerCenter Repository Service can complete the following global object tasks: ¨ Configure global object permissions. Note: To perform actions on global objects. not by privileges or permissions.

Create Connections Privilege Users assigned the Create Connections privilege can create connection objects. The following table lists the required permissions and the actions that users can perform with the Create Connections privilege: Permission n/a Grants Users the Ability To Create and copy connection objects.Remove objects from a deployment group. users can create. PowerCenter Repository Service Privileges 101 . and copy deployment groups. In a non-versioned repository. The following table lists the required permissions and the actions that users can perform with the Execute Deployment Groups privilege: Permission Read on original folder Execute on deployment group Grants Users the Ability To Copy deployment groups.Edit deployment groups. Add objects to a deployment group. edit. and roll back deployment groups. edit. . copy. Read on original folder Read and Write on deployment group Read on original folder Read and Write on destination folder Read and Execute on deployment group Read and Write on destination folder Copy deployment groups. Execute Deployment Groups Privilege Users assigned the Execute Deployment Groups privilege can copy a deployment group without write permission on target folders. The following table lists the required permissions and the actions that users can perform with the Manage Deployment Groups privilege: Permission n/a Read and Write on deployment group Grants Users the Ability To Create deployment groups. . Manage Deployment Groups Privilege If you have a team-based development option. users assigned the Manage Deployment Groups privilege in a versioned PowerCenter repository can create. Roll back deployment groups.

The following table describes the PowerExchange Listener Service privilege in the Informational Commands privilege group: Privilege Name listtask Description Run the infacmd pwx ListTaskListener command. PowerExchange Listener Service Privileges The PowerExchange Listener Service privileges determine the infacmd pwx commands that users can run. The following table describes each PowerExchange Listener Service privilege in the Management Commands privilege group: Privilege Name close closeforce stoptask Description Run the infacmd pwx CloseListener command. Create Queries Privilege Users assigned the Create Queries privilege can create object queries. Run the infacmd pwx StopTaskListener command. 102 Chapter 8: Privileges and Roles .Create Labels Privilege If you have a team-based development option. users assigned the Create Labels privilege in a versioned PowerCenter repository can create labels. Run the infacmd pwx CloseForceListener command. The following table lists the required permissions and the actions that users can perform with the Create Queries privilege: Permission n/a Grants Users the Ability To Create object queries. The following table lists the required permissions and the actions that users can perform with the Create Labels privilege: Permission n/a Grants Users the Ability To Create labels.

Run the infacmd pwx DisplayRecordsLogger command. Run the infacmd pwx DisplayStatusLogger command. Includes privileges to manage objects in the Alerts tab of Data Analyzer. Run the infacmd pwx DisplayMemoryLogger command. Run the infacmd pwx ShutDownLogger command. The following table describes each PowerExchange Logger Service privilege in the Informational Commands privilege group: Privilege Name displayall displaycpu displaycheckpoints displayevents displaymemory displayrecords displaystatus Description Run the infacmd pwx DisplayAllLogger command. Includes privileges to share dashboard or report information with other users. Run the infacmd pwx DisplayEventsLogger command.PowerExchange Logger Service Privileges The PowerExchange Logger Service privileges determine the infacmd pwx commands that users can run. The following table describes each PowerExchange Logger Service privilege in the Management Commands privilege group: Privilege Name condense fileswitch shutdown Description Run the infacmd pwx CondenseLogger command. Run the infacmd pwx DisplayCheckpointsLogger command. Reporting Service Privileges Reporting Service privileges determine the actions that users can perform using Data Analyzer. The following table describes each privilege group for the Reporting Service: Privilege Group Administration Description Includes privileges to manage objects in the Administration tab of Data Analyzer. Alerts Communication PowerExchange Logger Service Privileges 103 . Run the infacmd pwx FileSwitchLogger command. Run the infacmd pwx DisplayCPULogger command.

and Delete on: . Access query governing settings. Includes privileges to manage indicators in Data Analyzer. Export/Import XML Files Manage User Access Set Up Schedules and Tasks n/a Export or import metadata as XML files. .Manage System Properties n/a n/a n/a Alerts Privilege Group Privileges in the Alerts privilege group determine the tasks users can perform in the Alerts tab of Data Analyzer. Create and manage schedules and tasks. and Delete on time-based and event-based schedules n/a Manage System Properties Set Up Query Limits Configure Real-Time Message Streams n/a Manage system settings and properties. Write. edit. edit.Attribute . groups. Add. 104 Chapter 8: Privileges and Roles .Template dimension n/a Grants Users the Ability To Create. Manage users. and delete schema tables.Metric .Attribute folder . The following table lists the privileges and permissions in the Administration privilege group: Privilege Maintain Schema Includes Privileges n/a Permission Read. Write. Includes privileges to manage dashboards in Data Analyzer.Template dimension folder . Includes privileges to manage objects in the Manage Account tab of Data Analyzer.Metric folder . and remove real-time message streams. n/a n/a n/a Read. Dashboards Indicators Manage Account Reports Administration Privilege Group Privileges in the Administration privilege group determine the tasks that users can perform in the Administration tab of Data Analyzer.Privilege Group Content Directory Description Includes privileges to manage objects in the Find tab of Data Analyzer. Includes privileges to manage reports in Data Analyzer. and roles.

Export Read on report Read on dashboard .Receive Alerts Permission n/a n/a Grants Users the Ability To Receive and view triggered alerts. Export reports to Excel or commaseparated values files. Send links to reports or dashboards in an email. Delete Comment. Configure alert delivery options.Export .Export to Excel or CSV n/a Read on report Read on dashboard Read on report Read on dashboard Add Discussions . View Discussions Reporting Service Privileges 105 .The following table lists the privileges and permissions in the Alerts privilege group: Privilege Receive Alerts Create Real-time Alerts Set Up Delivery Options Includes Privileges n/a .Receive Alerts n/a Communication Privilege Group Privileges in the Communication privilege group determine the tasks users can perform to share dashboard or report information with other users.Email Object Links Read on report Read on dashboard Export n/a Read on report Read on dashboard Export to Excel or CSV Export to Pivot Table . Add messages to discussions. Create an alert for a real-time report.View Discussions Read on report Read on dashboard Give Feedback n/a Read on report Read on dashboard Delete messages from discussions. The following table lists the privileges and permissions in the Communication privilege group: Privilege Print Includes Privileges n/a Permission Read on report Read on dashboard Email Object Links n/a Read on report Read on dashboard Email Object Contents . Export reports and dashboards. Export reports to Excel pivot tables.View Discussions Read on report Read on dashboard Manage Discussions . Grants Users the Ability To Print reports and dashboards. . Send the contents of a report or dashboard in an email. Read discussions. Create feedback messages.

The following table lists the privileges and permissions in the Content Directory privilege group: Privilege Access Content Directory Includes Privileges n/a Permission Read on folders Grants Users the Ability To . Edit. Manage your own personal dashboard.View Dashboards Delete on dashboards 106 Chapter 8: Privileges and Roles .Content Directory Privilege Group Privileges in the Content Directory privilege group determine the tasks users can perform in the Find tab of Data Analyzer. Manage Personal Dashboard Create.Manage Content Directory Read on folders Write on folders Manage shared documents in the folders. Cut and paste folders. . The following table lists the privileges and permissions in the Dashboards privilege group: Privilege View Dashboards Includes Privileges n/a Permission Read on dashboards Grants Users the Ability To View contents of personal dashboards and public dashboards.Search for items available to users with the Basic Consumer role. . and Delete Dashboards Create. . .Access folders and content on the Find tab. Rename folders.Search for reports by name or search for reports you use frequently. Copy folder. .Search for advanced items.Access Content Directory .Access Content Directory Read on folders Manage Content Directory . .View Dashboards Read and Write on dashboards . . Dashboards Privilege Group Privileges in the Dashboards privilege group determine the tasks users can perform on dashboards in Data Analyzer.View reports from the PowerCenter Designer or Workflow Manager. and Delete Dashboards .View Dashboards Read and Write on dashboards .Search for reports you create or reports used by a specific user. .Edit dashboards.Access Content Directory Read and Write on folders Manage Content Directory Manage Shared Documents . .Access personal folders. Delete dashboards.Access Content Directory Delete on folders Delete folders. Create folders. Access Advanced Search .Create dashboards. Edit.

and animated real-time updates to indicators.Access Basic Dashboard Creation Permission Read and Write on dashboards Grants Users the Ability To . View continuous. Reports Privilege Group Privileges in the Reports privilege group determine the tasks users can perform with reports in Data Analyzer.Create. The following table lists the privileges and permissions in the Indicators privilege group: Privilege Interact with Indicators Create Real-time Indicator Includes Privileges n/a Permission Read on report Write on dashboard n/a Read and Write on report Write on dashboard .Create gauge indicator. The following table lists the privilege and permission in the Manage Account privilege group: Privilege Manage Personal Settings Includes Privileges n/a Permission n/a Grants Users the Ability To Configure personal account preferences.Create.View Dashboards . Grants Users the Ability To Use and interact with indicators. Automatic Real-time Indicator Updates n/a Read on report Manage Account Privilege Group The privilege in the Manage Account privilege group determines the task users can perform in the Manage Account tab of Data Analyzer. Get Continuous. Reporting Service Privileges 107 . Access Advanced Dashboard Creation Read and Write on dashboards Indicators Privilege Group Privileges in the Indicators privilege group determine the tasks users can perform with indicators.Privilege Access Basic Dashboard Creation Includes Privileges .View Dashboards .Broadcast dashboards as links. Edit. Edit.Use basic dashboard configuration options. and Delete Dashboards . Use all dashboard configuration options. automatic. . . and Delete Dashboards .Create an indicator on a real-time report.

Edit reports. . .Interact with Data .View Reports Write on report 108 Chapter 8: Privileges and Roles . .Broadcast report content as an email attachment and link.View Reports . .Broadcast the link to a report in Data Analyzer and edit the SQL query for the report. . Choose any attribute to drill into reports. .Create and manage Excel templates. Promote Custom Metric Write on report Promote custom metrics from reports to schemas.View Reports .Analyze Reports .The following table lists the privileges and permissions in the Reports privilege group: Privilege View Reports Analyze Reports Includes Privileges n/a .View Reports .Analyze reports.Interact with Data .Interact with Data .View Reports .View Reports Read on report Create Filtersets Read and Write on report Create and save filtersets in reports.Archive reports.Interact with Data . . Interact with Data . metadata.Access Basic Report Creation Write on report Save Copy of Reports Edit Reports .View Reports Write on report .View Reports Permission Read on report Read on report Grants Users the Ability To View reports and related metadata.Analyze Reports . View Query Read on report View report queries. .View Reports .Create reports using all available report options.Create and Delete Reports . and charts.Right-click on items on the Analyze tab. Use the Save As function to save the with another name. .Analyze Reports Read and Write on report Drill Anywhere .Interact with Data .View Reports .Analyze Reports . View Life Cycle Metadata Write on report Edit time keys on the Time tab.View report data. .Create and Delete Reports . Create and Delete Reports Access Basic Report Creation Write and Delete on report Write on report Create or delete reports.View Reports . .Set provider-based security for a report.Analyze Reports .View Reports . Access Advanced Report Creation .Access the toolbar on the Analyze tab and perform data-level tasks on the report table and charts.Analyze Reports .Create reports using basic report options.

A domain can contain multiple PowerCenter Repository Services. For more information about the privileges associated with these roles in Jaspersoft.Create. . The following table describes each privilege for the Reporting and Dashboards Service: Privilege Name Administrat or Description Users assigned to the administrator privilege can perform the following tasks in JasperReports Server: . modify. Roles that you can create.Reporting and Dashboards Service Privileges Reporting and Dashboards Service privileges map to roles in Jaspersoft. . edit. You can assign the Developer role to a user for the Development PowerCenter Repository Service. see the Jaspersoft documentation. You assign roles to users or groups for the domain or for each application service in the domain. You can assign a different role to that user for the Production PowerCenter Repository Service. You can view the role assignments by users Reporting and Dashboards Service Privileges 109 .Set access permissions on repository folders and objects. . and delete. A role includes privileges for the domain or an application service type.Assign roles to users.Create. Normal User Users assigned to the normal user privilege can view reports in JasperReports Server. . and delete roles. This privilege maps to the ROLE_USER role in Jaspersoft. This privilege maps to the ROLE_SUPERUSER role in Jaspersoft.Assign the ROLE_SUPERUSER role that grants system administrator privileges. You can assign the following types of roles: ¨ System-defined. . Superuser Users assigned to the superuser privilege can perform all the tasks that a user with the administrator privilege can perform. . The Access Privilege group contains all the Reporting and Dashboards Service privileges.Create. you can create a Developer role that includes privileges for the PowerCenter Repository Service.Create sub-organizations.Set the system-wide configuration parameters. . including the ROLE_ADMINISTRATOR role that grants organization administrator privileges. Managing Roles A role is a collection of privileges that you can assign to users and groups. modify. modify.Log in as any user in the organization. In addition. For example. .Create top-level organizations. you can view all users and groups that have been directly assigned the role for the domain and application services. and delete folders and repository objects of all types. and delete users. users with the superuser privilege can perform the following tasks in JasperReports Server: . When you select a role in the Roles section of the Navigator. ¨ Custom.Create users who can access all organizations. . Roles that you cannot edit or delete. This privilege maps to the ROLE_ADMINISTRATOR role in Jaspersoft.

Data Integration Service. this user or group cannot complete the tasks determined by the Administrator role.Delete a PowerCenter Integration Service from the Navigator of the Workflow Manager.Connect to the PowerCenter Integration Service from the PowerCenter Client when running the PowerCenter Integration Service in safe mode.* .* . When you assign the Administrator role to a user or group for the domain. Shut down the domain. Delete operating system profiles. View user activity log events. or PowerCenter Repository Service and then grant the user or group full permissions on all domain or PowerCenter repository objects. The following table lists the tasks determined by the Administrator role for the domain. Manage and purge log events. Upgrade services using the service upgrade wizard. .Change the owner of folders and global objects. Data Integration Service. Administrator Role When you assign the Administrator role to a user or group for the domain. Data Integration Service. Receive domain alerts.and groups or by services.* . Run the License Report.Configure folder and global object permissions. Data Integration Service. a user assigned the Administrator role for the domain can configure domain properties in the Administrator tool. Analyst Service. Users with the Administrator role can access all objects managed by the service. Grant permission on the domain and operating system profiles. However. Metadata Manager Service. . The Administrator role is a system-defined role. A user assigned all domain privileges and permission on the domain cannot configure domain properties. The Administrator role bypasses permission checking. and PowerCenter Repository Service: Service Domain Tasks Configure domain properties.Delete folders and global objects.* *The PowerCenter repository folder owner or global object owner can also complete these tasks. or PowerCenter Repository Service. System-Defined Roles A system-defined role is a role that you cannot edit or delete.Upgrade the Data Integration Service using the Actions menu. To navigate to a user or group listed in the Assignments section. . For example. You can assign a user or group all privileges for the domain. the user or group can complete some tasks that are determined by the Administrator role. 110 Chapter 8: Privileges and Roles . not by privileges or permissions.Edit the name and description of folders. PowerCenter Repository Service.* . You can search for system-defined and custom roles. Create operating system profiles.Assign operating system profiles to repository folders if the PowerCenter Integration Service uses operating system profiles. or Reporting Service.* . Model Repository Service.Designate folders to be shared. the user or group is granted all privileges for the service. Data Integration Service PowerCenter Repository Service . right-click the user or group and select Navigate to Item.

3. edit. and delete custom roles. Click OK. Change the description of the role and click OK. click the Security tab. Enter the following properties for the role: Property Name Description Name of the role. 1. edit. All other space characters are not allowed. In the Administrator tool. It cannot include a tab. Editing Privileges Assigned to Custom Roles You can change the privileges assigned to a custom role for the domain and for each application service type. Description Description of the role. newline character. Expand the domain or an application service type. you assign privileges to the role for the domain or for an application service type. The Administrator tool includes custom roles for the Metadata Manager Service. select a role. newline character. On the Security Actions menu. and Reporting Service. 2. 6. / * % ? The name can include an ASCII space character except for the first and last character. click the Security tab. click Create Role. Editing Properties for Custom Roles When you edit a custom role. 4. 1. The description cannot exceed 765 characters or include a tab. The role name is case insensitive and cannot exceed 128 characters. Managing Roles 111 . 2. Select the privileges to assign to the role for the domain or application service type. or the following special characters: < > " 4. You cannot change the name of the role. In the Administrator tool. A role can include privileges for one or more services. + " \ < > . In the Roles section of the Navigator. Or you can create custom roles and assign these roles to users and groups. Creating Custom Roles When you create a custom role. select a role. and delete. click the Security tab. Managing Custom Roles You can create. 7.Custom Roles A custom role is a role that you can create. 5. 3. or the following special characters: . you can change the description of the role. You can edit the privileges belonging to these roles and can assign these roles to users and groups. The Create Role dialog box appears. PowerCenter Repository Service. In the Roles section of the Navigator. 2. In the Administrator tool. Click the Privileges tab. 1. Click Edit.

Repeat the steps to change the privileges for each service type. The Edit Roles and Privileges dialog box appears. Use the following rules and guidelines when you assign privileges and roles to users and groups: ¨ You assign privileges and roles to users and groups for the domain and for each application service that is running in the domain. privileges for that application service type are assigned to the user or group. Note: You cannot edit the privileges or roles assigned to the default Administrator user account. 112 Chapter 8: Privileges and Roles . Confirm that you want to delete the role. A role is a collection of privileges. PowerCenter Repository Service. Click OK. To delete a custom role. You cannot assign privileges and roles to users and groups for a Metadata Manager Service. Deleting Custom Roles When you delete a custom role. 8. To remove privileges from the role. clear the privileges for the domain or application service type. . right-click the role in the Roles section of the Navigator and select Delete Role. To assign privileges to the role. ¨ A role can include privileges for the domain and multiple application service types. Assigning Privileges and Roles to Users and Groups You determine the actions that users can perform by assigning the following items to users and groups: ¨ Privileges. Expand the domain or an application service type. If you change the privileges or roles assigned to a user. 5. 4. When you assign a role to a user or group. 9. A privilege determines the actions that users can perform in application clients. Click the Privileges tab. 7. Click Edit.3. ¨ You can assign different privileges and roles to a user or group for each application service of the same service type. you assign the collection of privileges belonging to the role. or Reporting Service in the following situations: . the changed privileges or roles take affect the next time the user logs in. When you assign the role to a user or group for one application service.The PowerCenter Repository Service is running in exclusive mode. 6. select the privileges for the domain or application service type. ¨ Roles.The application service is disabled. the custom role and all privileges that it included are removed from any user or group assigned the role.

You can select any role that includes privileges for the selected domain or application service type. You can assign additional privileges to a user or group that are not inherited from a group or role. Repeat steps 10 through 12 to assign privileges for another service. You cannot revoke privileges inherited from a group or role. select the roles to assign to the user or group for the domain or application service. The tooltip for an inherited privilege displays which role or group the user inherited the privilege from. the group and all subgroups and users belonging to the group inherit the privileges belonging to the role. 4.Inherited Privileges A user or group can inherit privileges from the following objects: ¨ Group. Expand the domain or an application service. To grant privileges. The Privileges tab for a user or group displays all the roles and privileges assigned to the user or group for the domain and for each application service. 11. 5. To assign privileges. 10. When you assign a role to a group. the user inherits the privileges belonging to the role. click the Privileges tab. Click the following items to display additional information about the assigned roles and privileges: ¨ Name of an assigned role. The Edit Roles and Privileges dialog box appears. In the Administrator tool. The subgroups and users do not inherit the role. When you assign a role to a user. click the Security tab. 3. Steps to Assign Privileges and Roles to Users and Groups You can assign privileges and roles to users and groups in the following ways: ¨ Navigate to a user or group and edit the privilege and role assignments. Click Edit. clear the privileges assigned to the user or group. Displays the role details on the details panel. Assigning Privileges and Roles to Users and Groups 113 . 8. select the privileges to assign to the user or group for the domain or application service. 12. 2. To revoke roles. ¨ Drag roles to a user or group. To assign roles. 6. Click the Privileges tab. Highlights all privileges inherited with that role. To revoke privileges. Assigning Privileges and Roles to a User or Group by Navigation 1. 14. Click OK. To grant roles. 9. Privileges that are inherited from a role or group display an inheritance icon. Expand the domain or application service to view the roles and privileges assigned for the domain or service. clear the roles assigned to the user or group. ¨ Role. Repeat steps 5 through 7 to assign roles for another service. ¨ Information icon for an assigned role. select a user or group. 7. When you assign privileges to a group. 13. expand the domain or an application service on the Roles tab. all subgroups and users belonging to the group inherit the privileges. You cannot revoke privileges inherited from a role or group. In the Navigator.

3. or Reporting Service. On the Security Actions menu. The Assign Roles dialog box appears. 4. You cannot assign privileges or roles to a user for a Reporting Service when the combination of the user name. and security domain name exceeds 128 characters. PowerCenter Repository Service. I cannot assign privileges to a user for an enabled Reporting Service. You can use the Ctrl or Shift keys to select multiple roles. click the Security tab. Drag the selected roles to a user or group in the Users or Groups sections of the Navigator. 2. Right-click a user name and click Navigate to Item to navigate to the user. The Services dialog box appears. @ symbol. 6. I removed a privilege from a group. For example. PowerCenter Repository Service. Viewing Users with Privileges for a Service You can view all users that have privileges for the domain or an application service. Troubleshooting Privileges and Roles I cannot assign privileges or roles to users for an existing Metadata Manager Service. Data Analyzer uses the user account name and security domain name in the format UserName@SecurityDomain to determine the length of the user login name. 4. The details panel displays all users that have privileges for the domain or application service. In the Administrator tool. 5. or Reporting Service in the following situations: ¨ The application service is disabled. Select the domain or an application service. In the details panel. 1. ¨ The PowerCenter Repository Service is running in exclusive mode. 2. click the Security tab. click Service User Privileges. you might want to view all users that have privileges on the Development PowerCenter Repository Service. You cannot assign privileges and roles to users and groups for an existing Metadata Manager Service. In the Administrator tool. Why do some users in the group still have that privilege? 114 Chapter 8: Privileges and Roles . Click OK. Select the domain or application services to which you want to assign the role. In the Roles section of the Navigator. select the folder containing the roles you want to assign. select the role you want to assign. 3.Assigning Roles to a User or Group by Dragging 1.

When you have the Administrator role for an application service.You can use any of the following methods to assign privileges to a user: ¨ Assign a privilege directly to a user. I am assigned the Administrator role for the PowerCenter Repository Service. To manage an application service in the Administrator tool. you must have the appropriate domain privileges and permissions. Some of the Administrator tool tasks are determined by the Administrator role. You might not have the required object permissions in the application client. However. ¨ Assign a role to a user. An application client administrator cannot log in to the Administrator tool to manage the service for the application client for which it has administrator privileges. I am assigned all domain privileges and permission on all domain objects. edit. You can be assigned all privileges for the domain and granted full permissions on all domain objects. but I cannot edit any metadata. but I cannot use the Repository Manager to perform an advanced purge of objects or to create reusable metadata extensions. you cannot complete the tasks determined by the Administrator role. ¨ Assign a privilege or role to a group that the user belongs to. Even if you have the privilege to perform certain actions. and execute permission on a folder. I cannot use pmrep to connect to a new PowerCenter Repository Service running in exclusive mode. not by privileges or permissions. To synchronize the list of users and groups. but I cannot complete all tasks in the Administrator tool. restart the PowerCenter Repository Service. However. an application client administrator does not have permissions or privileges on the Informatica domain. I am assigned the Administrator role for an application service. I cannot configure the permissions for the folder. users that belong to that group can be directly assigned the privilege or can inherit the privilege from an assigned role. I am assigned all privileges in the Folders privilege group for the PowerCenter Repository Service and have read. The Service Manager might not have synchronized the list of users and groups in the PowerCenter repository with the list in the domain configuration database. However. write. My privileges indicate that I should be able to edit objects in an application client. You must have the Manage Services domain privilege and permission on the PowerCenter Repository Service in the Administrator tool to perform the following actions in the Repository Manager: ¨ Perform an advanced purge of object versions at the PowerCenter repository level. Troubleshooting Privileges and Roles 115 . An application client administrator has full permissions and privileges in an application client. but I cannot configure the application service in the Administrator tool. you may also require permission to perform the action on a particular object. ¨ Create. you are an application client administrator. and delete reusable metadata extensions. If you remove a privilege from a group.

¨ Delete the folder. ¨ Configure folder permissions. ¨ Edit the folder name and description. ¨ Designate the folder to be shared. Requires permission on the operating system profile.Only the folder owner or a user assigned the Administrator role for the PowerCenter Repository Service can complete the following folder management tasks: ¨ Assign operating system profiles to folders if the PowerCenter Integration Service uses operating system profiles. 116 Chapter 8: Privileges and Roles . ¨ Change the folder owner.

Analyst tool. 119 ¨ Connection Permissions. but not the Production PowerCenter Repository Service. You can assign permissions on Data Analyzer folders. a user has the Manage Services domain privilege and permission on the Development PowerCenter Repository Service.CHAPTER 9 Permissions This chapter includes the following topics: ¨ Permissions Overview. folders. attributes. You can assign permissions on the following domain objects: domain. The user can edit or remove the Development PowerCenter Repository Service. To manage an application service. but not on the Production PowerCenter Repository Service. For example. nodes. 132 Permissions Overview You manage user security with privileges and permissions. and schedules. metrics. Data Analyzer objects Data Analyzer Domain objects Administrator tool 117 . 117 ¨ Domain Object Permissions. You use different tools to configure permissions on the following objects: Object Type Connection objects Tool Administrator tool Analyst tool Developer tool Description You can assign permissions on connections defined in the Administrator tool. grids. 126 ¨ Web Service Permissions. template dimensions. the user may also require permission to perform the action on a particular object. licenses. or Developer tool. a user must have the Manage Services domain privilege and permission on the application service. reports. Even if a user has the privilege to perform certain actions. These tools share the connection permissions. Permissions define the level of access that users and groups have to an object. dashboards. 123 ¨ SQL Data Service Permissions.

Inherited permissions Permissions that users inherit. You can assign permissions on PowerCenter folders. You can assign permissions on web services or web service operations. direct permissions assigned to parent groups. Users with the Administrator role can access all objects. virtual tables. If you assign a group permission on the folder. When groups have permission on a domain object. a domain has a folder named Nodes that contains multiple nodes. such as SQL data services. For example. and virtual stored procedures. queries. You can deny inherited permissions on some object types. and connection objects. Effective permissions Superset of all permissions for a user or group. you configure exceptions to the permissions that users and groups might already have. Metadata Manager catalog objects Metadata Manager You can assign permissions on Metadata Manager folders and catalog objects. and permissions inherited from parent objects. You cannot revoke inherited permissions. all subgroups and users belonging to the group inherit permission on the domain object. they inherit permission on all objects in the domain or the folder. You can assign permissions on projects defined in the Analyst tool and Developer tool. When you deny permissions. When users have permission on a domain or a folder. The Administrator role bypasses permission checking. virtual schemas. When you view permission details. permission details display whether the user or group is assigned the Administrator role which bypasses permission checking. You also cannot revoke permissions from users or groups assigned the Administrator role. deployment groups. you can view the origin of effective permissions. labels. they can perform administrative tasks on that object if they also have the appropriate privilege. Includes direct permissions and inherited permissions. In addition.Object Type Tool Description application services. These tools share project permissions. and operating system profiles. You can assign permissions on SQL data objects. all subgroups and users belonging to the group inherit permission on the folder and on all nodes in the folder. When users and groups have permission on an object. Model repository projects Analyst tool Developer tool PowerCenter repository objects PowerCenter Client SQL data service objects Administrator tool Web service objects Administrator tool Types of Permissions Users and groups can have the following types of permissions in a domain: Direct permissions Permissions that are assigned directly to a user or group. You can edit direct permissions. Permission details display direct permissions assigned to the user or group. 118 Chapter 9: Permissions .

Right-click a column name to sort the column in ascending or descending order. Enables Administrator tool users to access all objects in the folder in the Administrator tool. or edit permissions for a user or group. Enables Administrator tool users to view and edit the node properties. Without permission. or remove the node. Without permission." "daphne. Enables Administrator tool users to view and edit the license properties. Without permission. To log in to the Administrator tool.Permission Search Filters When you assign permissions." You can also sort the list of users or groups. You can configure permissions on the following types of domain objects: Domain Object Type Domain Description of Permission Enables Administrator tool users to access all objects in the domain. The string is not case sensitive. Permissions define the level of access a user has to a domain object. the user can view the node properties. the string "DA" can return "iasdaemon. Enables Administrator tool users to view and edit the grid properties. When you manage permissions for a user or group. a user cannot use the license when creating an application service. For example. but does not have the Manage Nodes and Grids privilege. if a user has permission on a node. but cannot configure. a user cannot assign the grid to a Data Integration Service or PowerCenter Integration Service. When users have permission on a domain. For example. a user cannot use the node when defining an application service or creating a grid. then the user can only view the object. Pattern string Enter a string to search for users or groups. they inherit permission on all objects in the folder. Domain Object Permissions You configure privileges and permissions to manage user security within the domain. The Administrator tool returns all names that contain the search string. If a user has permission on an object. but does not have the domain privilege that grants the ability to modify the object type. When users have permission on a folder." and "DA_AdminGroup. a user must have permission on at least one domain object. Folder Node Grid License Domain Object Permissions 119 . view permission details. you can use search filters to search for a user or group. shut down. they inherit permission on all objects in the domain. you can use the following search filters: Security domain Select the security domain to search for users or groups.

Select a user or group. and click Next. In the contents panel. and edit permissions on the domain object for multiple users or groups. 7. Use the Manage Permissions dialog box to assign and edit permissions on domain objects for a specific user or group. Click the Groups or Users tab. ¨ Manage permissions by user or group. you grant users and groups access to the object. If the user that runs a workflow does not have permission on the operating system profile assigned to the workflow. On the Domain tab. and click the Filter button. 4. select the Permissions view. Viewing Permission Details on a Domain Object When you view permission details. view. In the Navigator. Use the Permissions view of a domain object to assign and edit permissions on the object for multiple users or groups. Select Allow. the workflow fails. 120 Chapter 9: Permissions . In the Navigator. 6. Click Actions > Assign Permission. 3. In the contents panel. and click Finish. 3. 1. select the domain object. Click the Groups or Users tab. select the Services and Nodes view.Domain Object Type Application Service Description of Permission Enables Administrator tool users to view and edit the application service properties. and click the Filter button. Note: You configure permissions on an operating system profile differently than you configure permissions on other domain objects. select the domain object. 8. Select a user or group and click Actions > View Permission Details. select the Permissions view. 4. On the Domain tab. Enables PowerCenter users to run workflows associated with the operating system profile. Enter the filter conditions to search for users and groups. 2. 6. Assigning Permissions on a Domain Object When you assign permissions on a domain object. 5. 1. you can view the origin of effective permissions. Enter the filter conditions to search for users and groups. Operating System Profile You can use the following methods to manage domain object permissions: ¨ Manage permissions by domain object. The Assign Permissions dialog box displays all users or groups that do not have permission on the object. 2. 5. Permissions by Domain Object Use the Permissions view of a domain object to assign. select the Services and Nodes view.

Click the Groups or Users tab. Editing Permissions on a Domain Object You can edit direct permissions on a domain object for a user or group. Or. In the header of Infomatica Administrator. 1. and click the Filter button. select the Services and Nodes view. Click OK. you can view the origin of effective permissions. direct permissions assigned to parent groups. 7. Enter the filter conditions to search for users and groups. 5. select Revoke. To assign permission on the object. Domain Object Permissions 121 . 5. Viewing Permission Details for a User or Group When you view permission details. You cannot revoke inherited permissions or your own permissions. 3. Permissions by User or Group Use the Manage Permissions dialog box to view. 2. In the contents panel. 7.The Permission Details dialog box appears. The dialog box displays direct permissions assigned to the user or group. 6. 6. click Edit Permissions to edit direct permissions. The Permission Details dialog box appears. 8. and permissions inherited from parent objects. 4. direct permissions assigned to parent groups. Or. the user or group might still inherit permission from a parent group or object. Select a user or group. click Manage > Permissions. The dialog box displays direct permissions assigned to the user or group. permission details display whether the user or group is assigned the Administrator role which bypasses permission checking. and click the Filter button. assign. The Manage Permissions dialog box appears. Select a user or group and click Actions > Edit Direct Permissions. In addition. 7. Enter a string to search for users and groups. Click Close. and edit domain object permissions for a specific user or group. and permissions inherited from parent objects. The Edit Direct Permissions dialog box appears. select Allow. select the Permissions view. You can view whether the permission is directly assigned or inherited by clicking View Permission Details. To revoke permission on the object. 8. In addition. select the domain object. 9. 3. Note: If you revoke direct permission on an object. permission details display whether the user or group is assigned the Administrator role which bypasses permission checking. Select a domain object and click the View Permission Details button. Click Close. 4. 1. On the Domain tab. 2. click Edit Permissions to edit direct permissions. Click the Groups or Users tab. In the Navigator.

Assigning Permissions on an Operating System Profile When you assign permissions on an operating system profile. The Manage Permissions dialog box appears. Click OK. 4. 5. click Manage > Permissions. you can view the origin of effective permissions. The Configure Operating System Profiles dialog box appears. 5. click Actions > Configure Operating System Profiles. The Configure Operating System Profiles dialog box appears. the user or group might still inherit permission from a parent group or object. Enter a string to search for users and groups and click the Filter button. and click the Permissions tab. and click Next. and click the Permissions tab.Assigning and Editing Permissions for a User or Group When you edit domain object permissions for a user or group. 8. 2. 1. and click Finish. and click the Assign Permission button. 3. click Actions > Configure Operating System Profiles. 2. On the Security tab. The Edit Direct Permissions dialog box appears. To assign permission on the object. 6. Select a user or group. Enter the filter conditions to search for users and groups. 1. You cannot revoke inherited permissions or your own permissions. Click the Groups or Users tab. Note: If you revoke direct permission on an object. Viewing Permission Details on an Operating System Profile When you view permission details. You can view whether the permission is directly assigned or inherited by clicking View Permission Details. To revoke permission on the object. select Allow. Select the Groups or Users view. you can assign permissions and edit existing direct permissions. 2. 6. 7. select Revoke. On the Security tab. 3. 9. Click Close. Select a user or group. Operating System Profile Permissions Use the Configure Operating System Profiles dialog box to assign. Select Allow. 4. In the header of Infomatica Administrator. and click the Filter button. The Assign Permissions dialog box displays all users or groups that do not have permission on the operating system profile. Select the operating system profile. PowerCenter users can run workflows assigned to the operating system profile. and edit permissions on operating system profiles. 122 Chapter 9: Permissions . view. Select the operating system profile. 1. Select a domain object and click the Edit Direct Permissions button.

You can view whether the permission is directly assigned or inherited by clicking View Permission Details. The Configure Operating System Profiles dialog box appears. Enforces read. 1. Note: If you revoke direct permission on an object. select Allow. ¨ Informatica command line interface. 8. you grant GroupA permission on ConnectionA in the Developer tool. or Administrator tool. Click OK. Select a user or group and click Actions > View Permission Details. The Edit Direct Permissions dialog box appears. The Permission Details dialog box appears. 3. 7. and click the Filter button. Click Close. write. click Actions > Configure Operating System Profiles. The dialog box displays direct permissions assigned to the user or group. 4. direct permissions assigned to parent groups. write. 5. The following Informatica components use the connection permissions: ¨ Administrator tool. and permissions inherited from parent objects. and click the Permissions tab. Any connection permission that is assigned to a user or group in one tool also applies in other tools. Editing Permissions on an Operating System Profile You can edit direct permissions on an operating system profile for a user or group. permission details display whether the user or group is assigned the Administrator role which bypasses permission checking. Or. 6. Enforces read. You can configure permissions on a connection in the Analyst tool. You cannot revoke inherited permissions or your own permissions. click Edit Permissions to edit direct permissions. select Revoke. Enter the filter conditions to search for users and groups. Select a user or group and click Actions > Edit Direct Permissions. ¨ Analyst tool. 6. and execute permissions on connections. the user or group might still inherit permission from a parent group or object. To revoke permission on the operating system profile. write. Connection Permissions 123 . 7. and grant permissions on connections. Select the Groups or Users view. 2. Connection Permissions Permissions control the level of access that a user or group has on the connection. In addition. 5. To assign permission on the operating system profile. and execute permissions on connections. Select the operating system profile. Select the Groups or Users view. Developer tool. Enforces read. Enter the filter conditions to search for users and groups. For example. 4. GroupA has permission on ConnectionA in the Analyst tool and Administrator tool also.3. On the Security tab. and click the Filter button.

¨ Use the connection in mappings in the Developer tool. Delete the connection. ¨ Create profiles in the Analyst tool on objects in the connection. 1. or profile. staging database. Enforces read. 2. Enforces execute permissions when a user tries to preview data or run a mapping. select the Permissions view. select the Connections view. or Model repository. and grant permission on the connection. In the contents panel. Note: You cannot assign permissions on the following connections: profiling warehouse. write. data object cache database.¨ Developer tool. and user names. type. By default. The user that creates a connection has read. scorecard. all users have permission to perform the following actions on connections: ¨ View basic connection metadata. Users can preview data or run a mapping. Users with Write permission inherit Read permission. Access to all physical data in the tables in the connection. Edit all connection metadata. 3. such as connection name. RELATED TOPICS: ¨ “Column Level Security” on page 128 ¨ “ Pass-through Security” on page 381 Types of Connection Permissions You can assign different permission types to users to perform the following actions: Action View all connection metadata. In the Navigator. except passwords. On the Domain tab. such as connection name. 124 Chapter 9: Permissions . type. execute. Grant and revoke permissions on connections. and description. you define the level of access a user or group has to the connection. scorecard. write. connection strings. including passwords. select the connection. Instead. it enforces column-level and pass-through security to restrict access to data. the Developer tool does not enforce connection permissions. or profile. description. Assigning Permissions on a Connection When you assign permissions on a connection. ¨ Data Integration Service. Permission Types Read Write Execute Grant Default Connection Permissions The domain administrator has all permissions on all connections. For SQL data services. and execute permissions on connections.

On the Domain tab. 4. Connection Permissions 125 . Note: If you revoke direct permission on an object. Editing Permissions on a Connection You can edit direct permissions on a connection for a user or group. the user or group might still inherit permission from a parent group or object. Select Allow for each permission type that you want to assign. The dialog box displays direct permissions assigned to the user or group and direct permissions assigned to parent groups. In the contents panel. Select a user or group and click Actions > Edit Direct Permissions. ¨ Select Revoke to revoke all permissions. 9. In the contents panel. ¨ Select Allow to assign a permission. and click the Filter button. 3. 1. 2. 6. Click Close. 7. 7. 6. In the Navigator. You cannot revoke inherited permissions or your own permissions. In the Navigator. Or. On the Domain tab. Choose to allow or revoke permissions. select the Permissions view. 5. 8. 7. 4. and click the Filter button. 2. Click the Groups or Users tab. Select a user or group. 5. 3. Enter the filter conditions to search for users and groups. Select a user or group and click Actions > View Permission Details. and click Next. Click Finish. and click the Filter button. Click the Groups or Users tab. 5. you can view the origin of effective permissions. 8. 8. 6. In addition. The View Permission Details dialog box appears. Viewing Permission Details on a Connection When you view permission details. You can view whether the permission is directly assigned or inherited by clicking View Permission Details.4. click Edit Permissions to edit direct permissions. The Edit Direct Permissions dialog box appears. Click Actions > Assign Permission. ¨ Clear Allow to revoke a single permission. 1. Enter the filter conditions to search for users and groups. select the connection. select the Permissions view. Click OK. Click the Groups or Users tab. select the Connections view. select the Connections view. select the connection. The Assign Permissions dialog box displays all users or groups that do not have permission on the connection. permission details display whether the user or group is assigned the Administrator role which bypasses the permission check. Enter the filter conditions to search for users and groups.

you cannot assign permissions to a column in a virtual table. Users can grant and revoke permissions on the SQL data service objects using the Administrator tool or using the infacmd command line program. you assign a user select permission on an SQL data service. n/a Virtual table n/a Virtual stored procedure Grant and revoke permission on the virtual stored procedure. Users can run SQL SELECT statements on virtual tables in the SQL data service using a JDBC or ODBC client tool. For example. users can run SQL queries against virtual tables in an SQL data service. Grant and revoke permission on the virtual table. Run the virtual stored procedure. ¨ Select permission. 126 Chapter 9: Permissions . Permissions control the level of access that a user has to an SQL data service. You can deny permissions to users and groups on some SQL data service objects. The following table describes the permissions for each SQL data service object: Object SQL data service Grant Permission Grant and revoke permission on the SQL data service and all objects within the SQL data service. For example. The user inherits select permission on all virtual tables in the SQL data service.SQL Data Service Permissions End users can connect to an SQL data service through a JDBC or ODBC client tool. After connecting. ¨ Execute permission. the user or group inherits the same permissions on all objects that belong to the SQL data service object. Run SQL SELECT statements on the virtual table. Users can run virtual stored procedures in the SQL data service using a JDBC or ODBC client tool. Some permissions are not applicable for all SQL data service objects. Select Permission Run SQL SELECT statements on all virtual tables in the SQL data service. Types of SQL Data Service Permissions You can assign the following permissions to users and groups: ¨ Grant permission. You can assign permissions to users and groups on the following SQL data service objects: ¨ SQL data service ¨ Virtual table ¨ Virtual stored procedure When you assign permissions on an SQL data service object. Execute Permission Run all virtual stored procedures in the SQL data service. or users can run a virtual stored procedure in an SQL data service. but you can deny a user from running an SQL SELECT statement that includes the column. you configure exceptions to the permissions that users and groups might already have. When you deny permissions.

In the Navigator. 4. 2. In the contents panel. select the Applications view. and click Next. 9. Or. 7. and permissions inherited from parent objects. the user or group might still inherit permission from a parent group or object. Click Finish. 4. Note: If you revoke direct permission on an object. 3. select a Data Integration Service. 6. you can view the origin of effective permissions. Select a user or group and click the View Permission Details button. 1. select a Data Integration Service. 6. select the Applications view. In addition. The Assign Permissions dialog box displays all users or groups that do not have permission on the SQL data service object. Select Allow for each permission type that you want to assign.Assigning Permissions on an SQL Data Service When you assign permissions on an SQL data service object. In the details panel. 9. Click Close. 3. Enter the filter conditions to search for users and groups. On the Domain tab. permission details display whether the user or group is assigned the Administrator role which bypasses permission checking. and click the Filter button. select the Services and Nodes view. select a Data Integration Service. 4. Select a user or group. select the Applications view. You cannot revoke inherited permissions or your own permissions. Viewing Permission Details on an SQL Data Service When you view permission details. 7. Select the SQL data service object. On the Domain tab. In the Navigator. On the Domain tab. select the Services and Nodes view. select the Group Permissions or User Permissions view. In the contents panel. select the Group Permissions or User Permissions view. 5. In the contents panel. direct permissions assigned to parent groups. and click the Filter button. 2. The Permission Details dialog box appears. Click the Assign Permission button. 8. Enter the filter conditions to search for users and groups. 1. In the details panel. Select the SQL data service object. 1. you define the level of access a user or group has to the object. 2. click Edit Permissions to edit direct permissions. 10. SQL Data Service Permissions 127 . select the Services and Nodes view. Editing Permissions on an SQL Data Service You can edit direct permissions on an SQL data service for a user or group. Select the SQL data service object. The dialog box displays direct permissions assigned to the user or group. 8. In the Navigator. 3. 5.

The Administrator can configure the Data Integration Service behavior for queries against a restricted column. the child objects inherit the permission. When permissions apply to a parent object in an SQL data service. The SetColumnPermissions command does not include the apply permissions option. To deny permissions use one of the following infacmd commands: ¨ infacmd sql SetStoredProcedurePermissions. Denies Execute or Grant permissions at the stored procedure level. Select a user or group and click the Edit Direct Permissions button. Click OK. select the Group Permissions or User Permissions view. ¨ Select Allow to assign a permission. ¨ infacmd sql SetColumnPermissions. you are applying an exception to the effective permission. 9.5. When you deny a permission on an object in an SQL data service. 6. The substitute value replaces the column value through the query. In the details panel. Choose to allow or revoke permissions. The Data Integration Service verifies permissions before running SQL queries and stored procedures against the virtual database. The following results might occur when the user queries a column that the user does not have permissions for: ¨ The query returns a substitute value instead of the data. The Edit Direct Permissions dialog box appears.com/docs/DOC-4507. Each command has options to apply permissions (-ap) and deny permissions (-dp). Enter the filter conditions to search for users and groups. and click the Filter button. You can view whether the permission is directly assigned or inherited by clicking View Permission Details. ¨ Clear Allow to revoke a single permission. Note: You cannot deny permissions from the Administrator tool. 7. The query returns a substitute value in each row that it returns. the results substitute appears in the results. see the Informatica How-To Library article "How to Configure Security for SQL Data Services": http://communities. The Data Integration Service validates the permissions for users or groups starting at the SQL data service level. Denies Select permission at the column level. Column Level Security An Administrator can deny access to columns in a virtual table of an SQL data object. ¨ infacmd sql SetTablePermissions. If the query includes filters or joins. 128 Chapter 9: Permissions .informatica. ¨ Select Revoke to revoke all permissions. ¨ The query fails with an insufficient permission error. Denies Select and Grant permissions at the virtual table level. Denying Permissions on an SQL Data Service You can explicitly deny permissions on some SQL data service objects. 8. For more information about configuring security for SQL data services. The Data Integration Service checks for denied permissions at the column level.

you can choose to substitute the value with NULL or with a constant value. Dept. When the user selects the salary column in an SQL query. To configure a substitute value for a column. The default is an empty string.InsufficientPermissionValue=value Substitutes the restricted column value with a constant. The query runs and the Data Integration Service substitutes the column value with NULL.000 for the salary in each row. but the column is a number or a date. If you do not configure a value for the DenyWith option. default is not to fail the query. If the Data Integration Service substitutes the column with an empty string. you can fail the query if a user selects the restricted column. Run the infacmd sql UpdateColumnOptions command to configure the column options.DenyWith=VALUE ColumnOptions. disable the Data Integration Service and enter an infacmd similar to the following command: infacmd sql SetColumnPermissions -dn empDomain -sn DISService -un Administrator -pd Adminpass -sqlds employee_APP. The Administrator configures a substitute value of 100. Returns null values for a restricted column in each row.employees -t Employee -c Salary gun -Tom -dp SQL_Select The following SQL statements return NULL in the salary column: Select * from Employee Select LastName. You cannot set column level security from the Administrator tool. and Salary columns.RELATED TOPICS: ¨ “ Connection Permissions” on page 123 Restricted Columns When you configure column level security. LastName. To restrict the user from the salary column. Enter one of the following options: ¨ ERROR. If you substitute the column value. the Data Integration Service returns 100. Or. the query returns errors. You can substitute the restricted data with a default value.InsufficientPermissionValue=100000 If you do not configure either option for a restricted column. enter the command with the following syntax: infacmd sql UpdateColumnOptions -dn empDomain -sn DISService -un Administrator -pd Adminpass -sqlds employee_APP.employees_SQL -t Employee -c Salary -o ColumnOptions. Returns a constant value in place of the restricted column in each row. an Administrator denies a user access to the salary column in the Employee table. enter the following options: ColumnOptions. You enable a user to access the Employee table but restrict the user from accessing the salary column. set a column option that determines what happens when a user selects the restricted column in a query.000 for the salary column. An Employee table contains FirstName. Fails the query and returns an error when an SQL query selects a restricted column.InsufficientPermissionValue option. When you run infacmd sql UpdateColumnOptions. ¨ VALUE. You cannot set column options in the Administrator tool. Salary from Employee SQL Data Service Permissions 129 . ColumnOptions. Adding Column Level Security Configure column level security with the infacmd sql SetColumnPermissions command. For example. the Data Integration Service ignores the InsufficientPermissionValue option.DenyWith=option Determines whether to substitute the restricted column value or to fail the query. Configure the constant value in the ColumnOptions. ¨ NULL.

Alice.500 dollars in their region if they are not the owner. the predicate acts as an additional WHERE clause appended to the original query request. Row Level Security Row level security is a level of security that restricts rows of data from users or user groups when they query a virtual table. the Data Integration Service replaces the USER keyword with the name of the user. When a user belongs to a group that has complete access to a table and also belongs to another group that has restricted access to a table. Charlie belongs to the Europe group. the user inherits complete access to the table. Bob. The assigned and inherited predicates determine the effective predicate for the user. 130 Chapter 9: Permissions . The Data Integration Service modifies the query based on security predicates. you can create security predicates that restrict access to rows in the following Employee_Sales table: OrderID 100 101 102 103 Amount 5140 2288 1599 2399 Company Acme FoodBar WonderFull BizTastic Owner Alice Bob Bob Charlie Region USA USA USA Europe RegionID 18 18 18 19 The domain contains groups named Employees. For example. You can assign the following security predicates to restrict access based on the business logic for each group: Group Security Predicate Employees Owner=USER Europe (Amount <2500) AND User IN ( SELECT EmployeeName FROM employees WHERE RegionId = 19) USA (Amount <2500) AND Owner IN ( SELECT EmployeeName FROM Employees WHERE RegionId = 18) You can assign Company != "WonderFull" as the security predicate to the user. Row Level Security Example Employees at Trade Company can only access orders for less than $2. and Europe. In this scenario. Users and groups inherit predicates assigned to their parent groups.The default behavior is to return null values. The security predicate has the same syntax as an SQL WHERE clause. unless the user is assigned a direct security predicate that filters access to specific rows of data. Each security predicate can contain multiple WHERE clauses. If a security predicate references tables that were not explicitly included in the original query. A security predicate is an SQL WHERE clause that filters data out of the result set when you query a virtual table. to ensure she cannot access WonderFull orders. integrated orders view. You cannot use a correlated subquery as part of a security predicate. a financial services company needs to integrate order data that is stored in disparate data sources and provide a single. the Data Integration Service also applies column level security and row level security to the referenced tables. For example. the effective security predicates of the groups do not display in the RLS Predicate field. USA. Alice and Bob belong to the USA group. You can assign a direct security predicate to a user or group. and Charlie belong to the Employees group. Based on the business logic. Alice. Employees can access data for orders that they own and for orders in their region within a specified dollar amount. You can create a security predicate that limits query access to specific rows of data. Alice cannot have access to orders from WonderFull. When you use the reserved word USER in the predicate. An administrator can create a virtual table that combines the order data and then restrict access to the table with security predicates so that users and groups see a particular data set when they query the table. a user can see all rows of data that its parent group can see. You can assign one direct security predicate to each user or group that has permission to access the virtual table. For SELECT statements.

such as hidden columns and data masking. The SQL_SELECT permission manages which users can access tables in the SQL data service. In the Data Integration Service Applications view. 1. Charlie. select the virtual table. SELECT * FROM Employee_Sales. 6. enter the security predicate to restrict user or group access to the table. you assign a security predicate to a user or group in the domain. Select the User Permissions or Group Permissions view. When Alice runs the query. To remove a security predicate. The Data Integration Service uses the security predicate to filter rows of data when a user queries a virtual table. then row level security can only use the mask value. For example. Configuring Row Level Security in Informatica Administrator Configure row level security in Informatica Administrator or with the infacmd sql setTablePermissions command. 2. Users with access to the original data sources can bypass row level security entirely. Column level security. Select the Revoke option for the user or group and click OK. 4. Evaluate column level security. Before you configure row level security for a user or group. delete the security predicate from the RLS Select text box and click OK. 5. it returns the following results: OrderID 103 Amount 2399 Company BizTastic Owner Charlie Region Europe RegionID 19 When Bob runs the same query.When Alice. The Edit Direct Permissions window appears. Click OK. Click RLS Edit icon in the upper right corner of the Edit Direct Permissions window. if column level security masks the value of a cell. Click Edit Direct Permissions. When you configure row level security. is applied before row level security. SQL Data Service Permissions 131 . In the RLS Select field. 3. not the original hidden value. Another Edit Direct Permissions window appears. and Bob run the query. verify that the configuration prerequisites are met and stop the Data Integration Service. it returns the following results: OrderID 100 101 Amount 5140 2288 Company Acme FoodBar Owner Alice Bob Region USA USA RegionID 18 18 When Charlie runs the same query. each person only sees a subset of the table based on the security predicates assigned to them and groups they belong to. A user must have the SQL_SELECT permission assigned before you can assign a row level security predicate. stop the Data Integration Service that the virtual table resides on and review column level security. it returns the following results: OrderID 101 102 Amount 2288 1599 Company FoodBar WonderFull Owner Bob Bob Region USA USA RegionID 18 18 Configuration Prerequisites for Row Level Security Before you configure row level security and assign security predicates to a user or group.

Users can manage permissions on the web service objects using the Administrator tool or using the infacmd command line program. You can deny permissions to users and groups on a web service operation. Web service operation Grant. In the Navigator. Send web service requests and receive web service responses from the web service operation. Assigning Permissions on a Web Service When you assign permissions on a web service object. you configure exceptions to the permissions that users and groups might already have. You can assign permissions to users and groups on the following web service objects: ¨ Web service ¨ Web service operation When you assign permissions on a web service object. Select the web service object. select the Applications view. select the Group Permissions or User Permissions view. Users can send web service requests and receive web service responses. 2. Permissions control the level of access that a user has to a web service. 4. 1. select the Services and Nodes view. In the details panel. 6. For example. Types of Web Service Permissions You can assign the following permissions to users and groups: ¨ Grant permission. When you deny permissions. The following table describes the permissions for each web service object: Object Web service Grant Permission Grant and revoke permission on the web service and all web service operations within the web service.Web Service Permissions End users can send web service requests and receive web service responses through a web service client. select a Data Integration Service. Click the Assign Permission button. 5. On the Domain tab. you assign a user execute permission on a web service. 132 Chapter 9: Permissions . In the contents panel. You can deny a user from running one web service operation that belongs to the web service. you define the level of access a user or group has to the object. a user has execute permissions on a web service which has three operations. The Assign Permissions dialog box displays all users or groups that do not have permission on the SQL data service object. and deny permission on the web service operation. revoke. ¨ Execute permission. the user or group inherits the same permissions on all objects that belong to the web service object. For example. Execute Permission Send web service requests and receive web service responses from all web service operations within the web service. The user inherits execute permission on web service operations in the web service. 3.

and click Next. Select a user or group and click the View Permission Details button. 9. ¨ Clear Allow to revoke a single permission. click Edit Permissions to edit direct permissions. Select a user or group. 5. and click the Filter button. 6. Choose to allow or revoke permissions. In the details panel. 7. In the contents panel. ¨ Select Deny to deny a permission on a web service object. and permissions inherited from parent objects. In the Navigator. you can deny permissions on the object. The Edit Direct Permissions dialog box appears. 3. 7. When you edit permissions on a web service object. Click Finish. direct permissions assigned to parent groups. On the Domain tab. the user or group might still inherit permission from a parent group or object.7. select a Data Integration Service. You can view whether the permission is directly assigned or inherited by clicking View Permission Details. select the Services and Nodes view. In addition. Viewing Permission Details on a Web Service When you view permission details. 9. 5. Select a user or group and click the Edit Direct Permissions button. Enter the filter conditions to search for users and groups. The dialog box displays direct permissions assigned to the user or group. Click Close. Select the web service object. 4. Select the web service object. 6. 9. 2. 8. 4. Enter the filter conditions to search for users and groups. You cannot revoke inherited permissions or your own permissions. Select Allow for each permission type that you want to assign. The Permission Details dialog box appears. select the Applications view. 8. permission details display whether the user or group is assigned the Administrator role which bypasses permission checking. Editing Permissions on a Web Service You can edit direct permissions on a web service for a user or group. you can view the origin of effective permissions. In the Navigator. 1. In the contents panel. Or. Click OK. select the Group Permissions or User Permissionsview. select the Applications view. 8. select the Group Permissions or User Permissions view. 3. 1. In the details panel. and click the Filter button. Note: If you revoke direct permission on an object. ¨ Select Allow to assign a permission. ¨ Select Revoke to revoke all permissions. 2. On the Domain tab. Enter the filter conditions to search for users and groups. 10. Web Service Permissions 133 . and click the Filter button. select the Services and Nodes view. select a Data Integration Service.

When you plan a highly available Informatica environment. and shared storage. hardware. If you do not have the high availability option. or service failures. ¨ Restart and failover. database management systems.CHAPTER 10 High Availability This chapter includes the following topics: ¨ High Availability Overview. the domain can continue running despite temporary network. 137 ¨ Achieving High Availability. The restart of a service or task or the migration to a backup node after the service becomes unavailable on the primary node. the PowerCenter Client. 144 ¨ Managing High Availability for the PowerCenter Integration Service. high availability eliminates a single point of failure in a domain and provides minimal service interruption in the event of failure. hardware. You can achieve high availability with external components based on the availability of those components. it restores the service state and recovers operations. In an Informatica domain. and command line programs. The completion of operations after a service is interrupted. ¨ Recovery. you can achieve some high availability of internal components. The following high availability components make services highly available in an Informatica domain: ¨ Resilience. 134 ¨ High Availability in the Base Product. After a service process restarts or fails over. If you have the high availability option. 150 High Availability Overview The term high availability refers to the uninterrupted availability of computer system resources. Internal components include the Service Manager. application services. 139 ¨ Managing Resilience. FTP servers. consider the differences between internal Informatica components and systems that are external to Informatica. 145 ¨ Troubleshooting High Availability. 141 ¨ Managing High Availability for the PowerCenter Repository Service. The ability of an Informatica domain to tolerate temporary connection failures until either the resilience timeout expires or the failure is fixed. you can achieve full high availability of internal Informatica components. 134 . When you configure high availability for a domain. External systems include the network. message queues.

High Availability Overview 135 . For this type of resilience to work. such as database systems. You configure application service connection resilience at the domain level in the general properties for the domain. the gateway node tries to reconnect until a user or service tries to perform a domain operation. the PowerCenter Integration Service is able to connect. After the PowerCenter Designer reestablishes the connection. the Informatica client tools. If the PowerCenter Repository Service becomes unavailable. Note: You cannot configure resilience properties for the following application services: Analyst Service. The domain resilience properties are the default values for all application services that have internal resilience. FTP servers. The PowerCenter Repository Service starts within the resilience timeout period. you override the resilience values set at the domain level. You can also configure application service connection resilience in the advanced properties for an application service. All clients of PowerCenter components are resilient to service failures. Clients that are resilient to a temporary failure can maintain connection to a service for the duration of the timeout. Content Management Service. and other client applications such as infacmd. and pmcmd. PowerExchange Listener Service. Resilience Resilience is the ability of application service clients to tolerate temporary network failures until the timeout period expires or the system failure is resolved. the master gateway node tries to reconnect. The resilience timeout period depends on user activity and the number of gateway nodes: . and Web Services Hub. the PowerCenter Repository Service becomes unavailable. and the request fails.Example While you are fetching a mapping into the PowerCenter Designer workspace. the request fails. For example. If the domain configuration repository becomes unavailable. The PowerCenter Designer is resilient to temporary failures and tries to establish a connection to the PowerCenter Repository Service. Reporting Service. Data Integration Service. PowerExchange Logger Service. The PowerCenter Repository Service fails over to another node because it cannot restart on the same node. When a user tries to perform a domain operation. The domain resilience timeout determines how long application services try to connect as clients to other application services or the Service Manager. Data Director Service. Model Repository Service. You can configure internal resilience at the following levels: ¨ Domain. The master gateway node maintains a connection to the domain configuration repository. Metadata Manager Service. When you configure connection resilience for an application service. and message queue sources. ¨ Gateway. A client of a service can be any PowerCenter Client tool or PowerCenter service that depends on the service. If the PowerCenter Repository Service is not available within the timeout period. the external systems must be highly available. You need the high availability option or the real-time option to configure resilience to external system failures.Single gateway node. If the domain has one gateway node. If the PowerCenter Repository Service becomes available within the timeout period. and the PowerCenter Designer reestablishes the connection. the PowerCenter Integration Service tries to reestablish the connection. Application services may also be resilient to temporary failures of external systems. pmrep. the master gateway node shuts down. Internal Resilience Internal resilience occurs within the Informatica environment among application services. ¨ Application service. the PowerCenter Repository Service recovers from the failed operation and fetches the mapping into the PowerCenter Designer workspace. the PowerCenter Integration Service is a client of the PowerCenter Repository Service.

or when it writes data to a relational target. the master gateway node shuts down. the Service Manager can restart the process or fail it over to a backup node based on the availability of the node. such as FTP servers and database management systems. The master gateway node can be resilient to temporary unavailability of the domain configuration database. You can configure the following types of external resilience for application services: ¨ Database connection resilience for the Data Integration Service. If the domain has multiple gateway nodes and the master gateway node cannot reconnect. If a database is temporarily unavailable. You configure this type of resilience in the Application connection object. The PowerCenter Repository Service can be resilient to temporary unavailability of the repository database system. The Data Integration Service is resilient if the database supports resilience. If the domain configuration database becomes unavailable. ¨ Database connection resilience for the PowerCenter Integration Service. the master gateway node tries to reconnect. You configure the repository database resilience timeout in the database properties of a PowerCenter Repository Service. when the PowerCenter Integration Service fetches data from a relational source or uncached lookup. the client tools retrieve information about the alternate domain gateways from the domains. the Data Integration Service tries to connect for a specified amount of time. ¨ Database connection resilience for the PowerCenter Repository Service. The PowerCenter Integration Service is resilient when connecting to a database when a session starts. You can configure the connection retry period in the relational connection object for a database. the PowerCenter Integration Service tries to reconnect for the amount of time configured in the FTP connection object. The PowerCenter Integration Service is resilient to interruptions if the FTP server supports resilience.. or start a mapping. You can configure connection resilience for PowerCenter Integration Service clients that are external applications using C/Java LMAPI. the service 136 Chapter 10: High Availability . The PowerCenter Integration Service depends on external database systems to run sessions and workflows. Restart and Failover If a service process becomes unavailable. the domain elects a new master gateway node. External Resilience Application services in the domain can also be resilient to the temporary unavailability of systems that are external to Informatica. ¨ FTP connection resilience. ¨ Client connection resilience. The PowerCenter Repository Service tries to reestablish connections to the database system and complete the interrupted request. ¨ Database connection resilience for the master gateway node.infa file. the PowerCenter Integration Service tries to connect for a specified amount of time. If a connection is lost while the PowerCenter Integration Service is transferring files to or from an FTP server. If a user tries to perform a domain operation while the master gateway node is trying to connect. The domain tries to connect to the domain configuration repository with each gateway node. The timeout period depends on whether the domain has one or multiple gateway nodes.Multiple gateway nodes. When a PowerCenter service process restarts or fails over. A client request to the PowerCenter Repository Service does not necessarily fail if the database system becomes temporarily unavailable. When a master gateway fails over. The Data Integration Service is resilient when connecting to a database to preview data. profile data. then the master gateway node shuts down. The PowerCenter Integration Service is resilient if the database supports resilience. The master gateway node maintains a connection to the domain configuration database. If none of the gateway nodes can connect. If a database is temporarily unavailable. You can configure the connection retry period in the relational database connection. the domain shuts down and all domain operations fail. If another gateway node is available.

the Service Manager may mark the process as failed. The service then fails over to a backup node and starts another process. You can configure multiple nodes as gateway. PowerCenter Client. it does not fail back to the primary node when the node becomes available. application services. ¨ Multiple gateway nodes. The Service Manager. Note: You must have the high availability option for failover and automatic recovery. running. Recovery Recovery is the completion of operations after an interrupted service is restored. The state of operation for a service contains information about the service process. The PowerCenter Integration Service maintains the state of operation in the shared storage configured for the service.restores the state of operation and begins recovery from the point of interruption. ¨ Restart services. it restores the state of operation and continues processing the job from the point of interruption. When a PowerExchange service process restarts or fails over. requests in progress. ¨ PowerCenter Repository Service. The PowerCenter Repository Service maintains the state of operation in the repository. and connected clients. and completed tasks for the service. High Availability in the Base Product 137 . ¨ PowerCenter Repository database resilience. When a service recovers. and command line programs are resilient to temporary unavailability of other PowerCenter internal components. ¨ Manual recovery of PowerCenter workflows and sessions. the service process restarts on the same node or on the backup node. High Availability in the Base Product Informatica provides some high availability functionality that does not require the high availability option. This includes information about repository locks. The primary node might be unavailable if it shuts down or if the connection to the node becomes unavailable. If you configure an application service to run on primary and backup nodes. If the process does not restart. the service fails over to a backup node. ¨ PowerCenter Integration Service. the administrator must enable the process after addressing any configuration problem. one service process can run at a time. The Service Manager for each node in the domain maintains the state of service processes running on that node. ¨ If the primary node running the service process is available. The base product provides the following high availability functionality: ¨ Internal PowerCenter resilience. You can configure backup nodes for PowerCenter application services and PowerExchange application services if you have the high availability option. The following situations describe restart and failover for an application service: ¨ If the primary node running the service process becomes unavailable. the domain tries to restart the process based on the restart options configured in the domain properties. The PowerCenter Integration Service maintains PowerCenter session and workflow state of operation based on the recovery strategy you configure for the session and workflow. This includes information about scheduled. the newly elected master gateway collects the state information from each node to restore the state of the domain. You can disable the service process on the backup node to cause it to fail back to the primary node. If a service process fails over to a backup node. The PowerCenter services include the following states of operation: ¨ Service Manager. The PowerCenter Repository Service is resilient to temporary unavailability of the repository database. The Service Manager can restart application services after a failure. You can manually recover PowerCenter workflows and sessions. If the master gateway shuts down. If the Service Manager marks the process as failed.

If you have multiple gateway nodes and the master gateway node becomes unavailable. the PowerCenter Repository Service can continue processing repository requests. application services. If you have the high availability option. PowerCenter components include the Service Manager. the PowerCenter Integration Service can automatically recover PowerCenter workflows. the Service Managers on the other gateway nodes elect another master gateway node to accept service requests. The PowerCenter Client is resilient to temporary unavailability of the application services. the PowerCenter Repository Service tries to reconnect within the database connection timeout period. You can manually recover a PowerCenter session without the high availability option. the PowerCenter Client. The PowerCenter Integration Service cannot automatically recover failed operations without the high availability option. temporary network failure can cause the PowerCenter Integration Service to be unavailable to the PowerCenter Client. You configure the database connection timeout in the PowerCenter Repository Service database properties. On Windows. you can configure Informatica services to restart when the Service Manager fails or the operating system starts. 138 Chapter 10: High Availability . the PowerCenter Integration Service stores the state of operation that it uses to begin processing from the point of interruption. you must configure the workflow for recovery. PowerCenter Repository Service Resilience to PowerCenter Repository Database The PowerCenter Repository Service is resilient to temporary unavailability of the repository database. Therefore. the domain shuts down and all domain operations fail. application services running on the master gateway node will not fail over when another master gateway node is elected. If none of the gateway nodes can connect. Restart Services If an application service process fails. Manual PowerCenter Workflow and Session Recovery You can manually recover a PowerCenter workflow and all tasks in the workflow without the high availability option. If you have one gateway node and it becomes unavailable. The PowerCenter Client tries to reconnect to the PowerCenter Integration Service during the resilience timeout period. and command line programs. you cannot configure an application service to run on multiple nodes. application services. To recover a workflow.Internal PowerCenter Resilience Internal PowerCenter components are resilient to temporary unavailability of other PowerCenter components. the domain cannot accept service requests. Without the high availability option. the Service Manager restarts the process on the same node. When you configure a workflow for recovery. You can configure the resilience timeout and the limit on resilience timeout for the domain. For example. you must configure the recovery strategy for the session. If the database becomes available and the PowerCenter Repository Service reconnects. To recover a session. If the repository database becomes unavailable. and command line programs. Multiple Gateway Nodes You can define multiple gateway nodes to achieve some resilience between the domain and the master gateway node without the high availability option.

¨ Optimize performance. Data Integration Service. You need to configure access to shared storage when you configure multiple gateway nodes and multiple backup nodes for the PowerCenter Integration Service. each gateway node must have access to the domain configuration database. Configure backup nodes for the PowerCenter Integration Service and the PowerCenter Repository Service. Configure the PowerCenter Integration Service and the PowerCenter Repository Service to run on multiple worker nodes. message queues. Configuring Internal Components for High Availability Internal components include the Service Manager. Metadata Manager Service. Configure one node as the primary node for the PowerCenter Integration Service. Use highly available external systems for hardware. SAP BW Service. Optimizing Performance To optimize performance in a domain. Configure nodes and services for high availability. You can configure the application services to run on multiple nodes in a domain. you can configure the nodes and services to minimize failover or to optimize performance: ¨ Minimize service failover. You can configure multiple nodes in a domain to serve as the gateway. For example. the Service Manager elects another master gateway node. configure the PowerCenter Integration Service and PowerCenter Repository Service to run on opposite primary nodes. Model Repository Service. database systems. configure gateway operations and applications services to run on separate nodes. You can configure nodes and application services to enhance availability: ¨ Configure more than one gateway. and configure the other node as the primary node for the PowerCenter Repository Service. Note: The Analyst Service. When you configure more than one gateway node. Reporting Service. the application services do not interfere with gateway operations when they consume a high level of CPUs. and Web Services Hub cannot be configured for high availability. shared storage. you can achieve a greater degree of availability when you configure more than one node to serve as a gateway and when you configure backup nodes for application services. When you design a highly available environment. When you separate the gateway operations from the application services. When you configure the PowerCenter Integration Service to run on more than one node. ¨ External systems. each node must have access to the run-time files used to process a session or workflow. Achieving High Availability 139 . Only one node serves as the gateway at any given time. nodes. and application services within the Informatica environment. the gateway is a single point of failure. and FTP servers. Configure different primary nodes for each application service. Configure gateway nodes on machines that are dedicated to serve as a gateway. If you configure only one gateway node. Configure two nodes as gateway. Data Director Service. If the gateway node becomes unavailable. Consider internal components and external systems when you are designing a highly available environment: ¨ Internal components. If the master gateway becomes unavailable. ¨ Configure highly available application services to run on multiple nodes.Achieving High Availability You can achieve different degrees of availability depending on factors that are internal and external to the Informatica environment. A service is available if at least one designated node is available. ¨ Configure access to shared storage. Minimizing Service Failover To minimize service failover in a domain with two nodes. the Service Manager cannot accept service requests. That node is called the master gateway. Content Management Service. networks.

¨ Use highly available versions of other external systems. ensure that external systems are also highly available. and targets. configure Informatica Services to restart if it terminates unexpectedly. ¨ For each node. ¨ Make the network highly available by configuring redundant components such as routers. 140 Chapter 10: High Availability . configure at least two nodes to serve as gateway nodes. Follow the guidelines of the database system when you plan redundant components and backup and restore policies. and FTP servers. message queues. ¨ In the Administrator tool. Configure primary and backup nodes or a grid.The following figure shows a domain configuration with two gateway nodes and two worker nodes for the PowerCenter Integration Service and PowerCenter Repository Service: Using Highly Available External Systems Informatica depends on external systems such as file systems and databases for repositories. ¨ Configure the PowerCenter Integration Service to run on multiple nodes. To optimize Informatica availability. and network adapter cards. Rules and Guidelines for Configuring High Availability Use the following rules and guidelines when you set up high availability: ¨ Install and configure highly available application services on multiple nodes. If you configure the PowerCenter Integration Service to run on a grid. ¨ Use a highly available POSIX compliant shared file system for the shared storage used by services in the domain. such as source and target database systems. cables. ¨ Use highly available database management systems for the repository databases associated with PowerCenter Repository Services and the domain configuration database. ¨ Configure the PowerCenter Repository Service to run on at least two nodes. Use the following rules and guidelines to configure external systems: ¨ Use a highly available database management system for the repository and domain configuration database. sources. make resources available to more than one node.

The hardware requirements and configuration of an I/O fencing solution are different for each file system. disable the service process on the node so that the service fails over to a backup node. the shared file system must be configured for I/O fencing. Managing Resilience Resilience is the ability of PowerCenter service clients to tolerate temporary network failures until the resilience timeout period expires or the external system failure is fixed. You can configure the following resilience properties for the domain. the PowerCenter Integration Service tries to reestablish the connection. The amount of time a service waits for a client to connect or reconnect to the service. The default value is 30 seconds. the PowerCenter Integration Service on each node needs to be able to access the log and recovery files within the shared file system. The following shared file systems are certified by Informatica for use in PowerCenter Integration Service failover and session recovery: Storage Array Network Veritas Cluster Files System (VxFS) IBM General Parallel File System (GPFS) Network Attached Storage using NFS v3 protocol EMC UxFS hosted on an EMV Celerra NAS appliance NetApp WAFL hosted on a NetApp NAS appliance Informatica recommends that customers contact the file system vendors directly to evaluate which file system matches their requirements. This is available for the domain and application services. the PowerCenter Integration Service is a client of the PowerCenter Repository Service. the request fails. application services. If the PowerCenter Repository Service becomes available within the timeout period. and command line programs: ¨ Resilience timeout. To be highly available. A client of a service can be any PowerCenter Client or PowerCenter application service that depends on the service. the PowerCenter Integration Service is able to connect. When possible. For example. If the PowerCenter Repository Service becomes unavailable. ¨ Limit on resilience timeout. The amount of time a client tries to connect or reconnect to a service. For example. Managing Resilience 141 .¨ Use a highly available POSIX compliant shared file system that is configured for I/O fencing in order to ensure PowerCenter Integration Service failover and recovery. all PowerCenter nodes within a cluster must be on the cluster file system’s heartbeat network. PowerCenter nodes need to be on the same shared file system so that they can share resources. it is recommended to use hardware I/O fencing. Tip: To perform maintenance on a node without service interruption. Configuring Service Resilience for the Domain The domain resilience timeout determines how long application services try to connect as clients to other services. Clients that are resilient to a temporary failure can try to reconnect to a service for the duration of the timeout. If the PowerCenter Repository Service is not available within the timeout period. A limit on resilience timeouts can override the timeout. Also. This limit can override the client resilience timeouts configured for a connecting client.

or pmrep command line program to connect to the domain or an application service. The default is 180 seconds. You can set the resilience timeout for infacmd by using the -ResilienceTimeout command line option each time you run a command. PowerExchange Logger Service.The limit on resilience timeout is the maximum amount of time that a service allows another service to connect as a client. To use the limit on resilience timeout configured for the domain. ¨ Service limit on timeout. You can configure the resilience timeout for the service in the service properties. ¨ Domain resilience timeout. the connecting service is a client of the other service. Configuring Application Service Resilience When an application service connects to another application service in the domain. When a service connects to another service. This resilience timeout is bound by the service limit on resilience timeout. pmcmd. the resilience timeout is determined by one of the following values: ¨ Command line option. If you perform a PowerCenter Client action that requires connection to the repository while the PowerCenter Client is trying to reestablish the connection. the client is resilient to the interruption in service. set the service resilience limit to blank. To disable resilience for a service. the client uses the limit as the resilience timeout. Content Management Service. A client cannot be resilient to service interruptions if you disable the service in the Administrator tool. You configure the resilience timeout for the SAP BW Service in the general properties for the service. Data Director Service. the resilience timeout is determined by one of the following values: ¨ Service resilience timeout. The PowerCenter Client resilience timeout is 180 seconds and is not configurable. You configure the resilience timeout and resilience timeout limits for the PowerCenter Integration Service and the PowerCenter Repository Service in the advanced properties for the service. Configuring Command Line Program Resilience When you use the infacmd. Reporting Service. If the PowerCenter Client is unable to reestablish the connection during the resilience timeout period. Understanding PowerCenter Client Resilience PowerCenter Client resilience timeout determines the amount of time the PowerCenter Client tries to connect or reconnect to the PowerCenter Repository Service or the PowerCenter Integration Service. The default value is 180 seconds. set the resilience timeout to 0. You can set the resilience timeout for pmcmd or pmrep by using the -timeout command line option each time you run a command. If you disable the service process. The default is 180 seconds. and Web Services Hub. The property for the SAP BW Service is called the retry period. To use the resilience timeout configured for the domain. set the service resilience timeout to blank. PowerExchange Listener Service. This limit overrides the resilience timeout for the connecting service if the resilience timeout is a greater value. Metadata Manager Service. If the service limit on resilience timeout is smaller than the resilience timeout for the connecting client. You can configure resilience properties for each service or you can configure each service to use the domain values. Data Integration Service. Model Repository Service. the PowerCenter Client prompts you to try the operation again after the PowerCenter Client reestablishes the connection. Note: You cannot configure resilience properties for the following application services: Analyst Service. the PowerCenter Client prompts you to reconnect to the repository manually. 142 Chapter 10: High Availability .

It is not bound by the PowerCenter Repository Service limit on resilience timeout of 60 seconds. The Service Manager on Node A uses the domain configuration for resilience timeout. If the limit on resilience timeout for the service is smaller than the command line resilience timeout. the command line program uses the value of the environment variable INFA_CLIENT_RESILIENCE_TIMEOUT that is configured on the client machine.¨ Environment variable. based on the domain resilience timeout. pmcmd is bound by the PowerCenter Integration Service limit on resilience timeout of 180 seconds. Note: PowerCenter does not provide resilience for a repository client when the PowerCenter Repository Service is running in exclusive mode. Example The following figure shows some sample connections and resilience configurations in a domain: The following table describes the resilience timeout and the limits shown in the preceding figure: Connection A Connect From PowerCenter Integration Service Connect To PowerCenter Repository Service Description The PowerCenter Integration Service can spend up to 30 seconds to connect to the PowerCenter Repository Service. If you do not use the command line option or the environment variable. If you do not use the timeout option in the command line syntax. the command line program uses the limit as the resilience timeout. ¨ Limit on timeout. The PowerCenter Client is bound by the PowerCenter Repository Service limit on resilience timeout of 60 seconds. ¨ Default value. Node A can spend up to 30 seconds to connect to Node B. It cannot use the default resilience timeout of 180 seconds. B pmcmd PowerCenter Integration Service C PowerCenter Client PowerCenter Repository Service Node B D Node A Managing Resilience 143 . The Service Manager on Node B uses the domain configuration for limit on resilience timeout. the command line program uses the default resilience timeout of 180 seconds. and it cannot use the 200 second resilience timeout configured in INFA_CLIENT_RESILIENCE_TIMEOUT.

the PowerCenter Repository Service tries to reconnect to the repository database within the period specified by the database connection timeout configured in the PowerCenter Repository Service properties.Managing High Availability for the PowerCenter Repository Service High availability for the PowerCenter Repository Service includes the following behavior: ¨ Resilience. Tip: If the repository database system has high availability features. Test the database system features that you plan to use to determine the optimum database connection timeout. Restart and Failover If the PowerCenter Repository Service process fails. The PowerCenter Repository Service is resilient to temporary unavailability of other services and the repository database. set the database connection timeout to allow the repository database system enough time to become available before the PowerCenter Repository Service tries to reconnect to it. PowerCenter Repository Service clients synchronize and connect to the PowerCenter Repository Service process without loss of service. the Service Manager can restart the process on the same node. the PowerCenter Repository Service can recover operations from the point of interruption. If the repository database becomes unavailable. ¨ You disable the PowerCenter Repository Service process. If the PowerCenter Repository Service fails. You configure the resilience timeout and the limit on resilience timeout for the PowerCenter Repository Service in the advanced properties when you create the PowerCenter Repository Service. ¨ Restart and failover. PowerCenter Repository Service clients are resilient to connections with the PowerCenter Repository Service. PowerCenter Repository Service clients are resilient to temporary unavailability of the PowerCenter Repository Service. based on node availability. 144 Chapter 10: High Availability . The repository database may become unavailable because of network failure or because the repository database system becomes unavailable. Resilience The PowerCenter Repository Service is resilient to temporary unavailability of other services. the PowerCenter Integration Service is a PowerCenter Repository Service client because it depends on the PowerCenter Repository Service for a connection to the repository. the Service Manager can restart the service or fail it over to another node. You can configure the PowerCenter Repository Service to be resilient to temporary unavailability of the repository database. A PowerCenter Repository Service client is any PowerCenter Client or PowerCenter service that depends on the PowerCenter Repository Service. Services can be unavailable because of network failure or because a service process fails. The PowerCenter Repository Service is also resilient to temporary unavailability of the repository database. ¨ The PowerCenter Repository Service process is running on a node that fails. For example. After failover. ¨ Recovery. the PowerCenter Repository Service process fails over to the backup node. After restart or failover. The PowerCenter Repository Service process fails over to a backup node in the following situations: ¨ The PowerCenter Repository Service process fails and the primary node is not available. If the node is not available. You can configure some PowerCenter Repository Service clients to be resilient to connections with the PowerCenter Repository Service. This can occur because of network failure or because the repository database system becomes unavailable. PowerCenter Client resilience timeout is 180 seconds and is not configurable.

Note: You must have the high availability option for resilience when the PowerCenter Integration Service loses connection to an external component. and pmcmd. such as the PowerCenter Designer and the PowerCenter Integration Service ¨ Completes requests in progress. such as saving a mapping ¨ Sends outstanding notifications about metadata changes. Recovery The PowerCenter Repository Service maintains the state of operation in the repository. If you disable a PowerCenter Repository Service process in complete or abort mode. such as workflow schedule changes Managing High Availability for the PowerCenter Integration Service High availability for the PowerCenter Integration Service includes the following behavior: ¨ Resilience. requests in progress. If the PowerCenter Integration Service loses connectivity to other services and PowerCenter Integration Service clients within the PowerCenter Integration Service resilience timeout period. All other PowerCenter Integration Service resilience is part of the base product. PowerCenter Integration Service clients also include applications developed using LMAPI. it restores the state of operation from the repository and recovers operations from the point of interruption. ¨ Restart and failover If the PowerCenter Integration Service process becomes unavailable. Managing High Availability for the PowerCenter Integration Service 145 . This includes information about repository locks. such as mappings and sessions ¨ Reconnects to clients. and external components such databases and FTP servers. it can automatically recover interrupted workflows that are configured for recovery. PowerCenter Integration Service clients. The PowerCenter Integration Service tries to reconnect to external components within the resilience timeout for the database or FTP connection object. This can occur because of network failure or because a PowerCenter Integration Service process fails. When the PowerCenter Integration Service restarts or fails over a service process. the Web Services Hub. the Service Manager can restart the process or fail it over to another node. PowerCenter Integration Service clients include the PowerCenter Client. Resilience The PowerCenter Integration Service is resilient to temporary unavailability of other services.You may want to disable a PowerCenter Repository Service process to shut down a node for maintenance. the Service Manager. Service and Client Resilience PowerCenter Integration Service clients are resilient to temporary unavailability of the PowerCenter Integration Service. ¨ Recovery. the PowerCenter Repository Service process fails over to another node. and connected clients. The PowerCenter Repository Service performs the following tasks to recover operations: ¨ Gets locks on repository objects. After a PowerCenter Repository Service restarts or fails over. A PowerCenter Integration Service process is resilient to connections with PowerCenter Integration Service clients and with external components.

If the PowerCenter Integration Service process loses connection to an external component. and workflows. The PowerCenter Integration Service is resilient to interruptions if the FTP server supports resilience. If a connection is lost when the PowerCenter Integration Service writes data to a target database. it tries to reconnect for the amount of time configured in the database connection object. service requests. If it cannot reconnect to the database and you configure the workflow for automatic recovery. You can configure the retry period when you create or edit the database or FTP server connection object. primary and backup nodes. the service configuration. the task will restart. When the PowerCenter Integration Service fails over. For example. or connectivity fails when the PowerCenter Integration Service reads data from the database. the process stops or fails. If the PowerCenter Integration Service loses the connection when it connects or retrieves data from a database for sources or Lookup transformations. the Service Manager tries to restart it or fails it over to another node based on the shutdown mode. the PowerCenter Integration Service recovers the session.You configure the resilience timeout and the limit on resilience timeout in the PowerCenter Integration Service advanced properties. External components can be temporarily unavailable because of network failure or the component experiences a failure. If it cannot restart the process. the behavior of completed tasks depends on the following situations: ¨ If a completed task reported a completed status to the PowerCenter Integration Service process prior to the PowerCenter Integration Service failure. If PowerCenter Integration Service connectivity to a database fails during the initial connection to the database. the Service Manager tries to restart the service process. the PowerCenter Integration Service tries to reconnect for the amount of time configured in the FTP connection object. Restart and Failover If a PowerCenter Integration Service process becomes unavailable. When you restart the process. External Component Resilience A PowerCenter Integration Service process is resilient to temporary unavailability of external components. and the operating mode for the service. it tries to reconnect for the amount of time configured in the database connection object. it tries to reconnect to the component within the retry period for the connection object. it tries to reconnect for 180 seconds. the session fails. Running on a Single Node The following table describes the failover behavior for a PowerCenter Integration Service if only one service process is running: Source of Shutdown Service Process Restart and Failover Behavior If the service process shuts down unexpectedly. you configure a retry period of 180 for a database connection object. Otherwise. the task will not restart. If the PowerCenter Integration Service loses the connection when it transfers files to or from an FTP server. or on a grid. the PowerCenter Integration Service restores the state of operation for the service and restores workflow schedules. ¨ If a completed task did not report a completed status to the PowerCenter Integration Service process prior to the PowerCenter Integration Service failure. Restart and failover behavior is different for services that run on a single node. 146 Chapter 10: High Availability .

you must enable the service and start the service processes. workflow failover. Service When the PowerCenter Integration Service becomes unavailable. You can manually recover workflows and sessions based on the state and the configured recovery strategy. Service When the PowerCenter Integration Service becomes unavailable. It performs failover and recovers the schedules. automatic workflow recovery. The PowerCenter Integration Service does not run scheduled workflows and it disables schedule failover. requests. based on the operating mode. requests. the workflow does not fail over and the PowerCenter Integration Service does not recover the workflow.Safe. When you restart the process. the service process fails over to a backup node. The PowerCenter Integration Service can recover the workflow based on the workflow state and recovery strategy.Normal. the workflow fails over on the same node. the PowerCenter Integration Service removes the workflow from the schedule. the PowerCenter Integration Service restores the state of operation for the workflow and recovers the workflow from the point of interruption. You must enable the service in normal mode for the scheduled workflows to run. and client request recovery. The PowerCenter Integration Service performs failover and recovers the schedules. You must reschedule all other workflows. You can manually recover workflows and sessions based on the state and Managing High Availability for the PowerCenter Integration Service 147 . the PowerCenter Integration Service removes the workflow from the schedule. Scheduled workflows do not start. If a scheduled workflow is not enabled for HA recovery.Source of Shutdown Restart and Failover Behavior The failover and recovery behavior of the PowerCenter Integration Service after a service process fails depends on the operating mode: . The failover and recovery behavior of the PowerCenter Integration Service after a service process fails depends on the operating mode: . Node When the node becomes unavailable. and workflows. and workflows when you enable the service in normal mode. When the service process on a primary node shuts down unexpectedly. The PowerCenter Integration Service performs failover and recovers the schedules. the PowerCenter Integration Service restores the state of operation for the service and restores workflow schedules. the restart and failover behavior is the same as restart and failover for the service process. and workflows. . If a scheduled workflow is not enabled for HA recovery.Safe. If the workflow was enabled for HA recovery. The workflows that run after you start the service processes depend on the operating mode: . requests.Normal. the Service Manager tries to restart the service process before failing it over to a backup node. Running on a Primary Node The following table describes the failover behavior for a PowerCenter Integration Service configured to run on primary and backup nodes: Source of Shutdown Service Process Restart and Failover Behavior When you disable the service process on a primary node. If the workflow is enabled for HA recovery. the PowerCenter Integration Service restores the state of operation for the workflow and recovers the workflow from the point of interruption. and workflows. . requests.Safe.Normal. Workflows configured to run continuously or on initialization will start. service requests. and workflows when you enable the service in normal mode. The PowerCenter Integration Service can recover the workflow based on the workflow state and recovery strategy. After the service process fails over to a backup node. When you restart the process. It performs failover and recovers the schedules. . you must enable the service and start the service processes.

service requests. The master service process then reconfigures the grid to run on one less node. When the node running the master service process becomes unavailable. After the master service process reconfigures the grid. The PowerCenter Integration Service can recover the workflow based on the workflow state and recovery strategy. the Service Manager tries to restart the process before electing another node to run the master service process. the Service Manager elects another node to run the master service process. You must reschedule all other workflows. If a scheduled workflow is not enabled for HA recovery. 148 Chapter 10: High Availability . Scheduled workflows do not start. The PowerCenter Integration Service restores the state of operation. You can manually recover workflows and sessions based on the state and the configured recovery strategy. the PowerCenter Integration Service removes the workflow from the schedule. Workflows configured to run continuously or on initialization will start. and the workflow fails over to the newly elected master service process. The workflows that run after you start the service processes depend on the operating mode: . Workflows configured to run continuously or on initialization will start. requests. When the PowerCenter Integration Service restores the state of operation for the service. . the failover behavior is the same as the failover for the service process. You must reschedule all other workflows. the failover behavior is the same as the failover for the worker service process. Service When the PowerCenter Integration Service becomes unavailable. Since workflows do not run on the worker service process. When the node running the worker service process becomes unavailable. You must reschedule all other workflows. it restores workflow schedules. Node Note: You cannot configure a PowerCenter Integration Service to fail over in safe mode when it runs on a grid. If the workflow was enabled for HA recovery. the PowerCenter Integration Service restores the state of operation for the workflow and recovers the workflow from the point of interruption. The PowerCenter Integration Service performs failover and recovers the schedules.Safe. You must enable the service in normal mode to run the scheduled workflows. and workflows. Running on a Grid The following table describes the failover behavior for a PowerCenter Integration Service configured to run on a grid: Source of Shutdown Master Service Process Restart and Failover Behavior If you disable the master service process. the failover behavior is the same as the failover for the master service process. Node When the node becomes unavailable. If the worker service process shuts down unexpectedly. If the master service process shuts down unexpectedly. the master service process reconfigures the grid to run on one less node. it can recover tasks based on task state and recovery strategy. based on the operating mode. and workflows. Worker Service Process If you disable a worker service process. you must enable the service and start the service processes. Workflows configured to run continuously or on initialization will start. the Service Manager tries to restart the process before the master service process reconfigures the grid.Source of Shutdown Restart and Failover Behavior the configured recovery strategy.Normal. workflow failover is not applicable.

When you run a workflow that is enabled for HA recovery. It fails the workflow over to another node. Aborted. ¨ Running workflows. Stopped. or terminated status. ¨ Suspended workflows. If the PowerCenter Integration Service cannot recover the task in the configured number of times for recovery. In normal mode. In safe mode. based on the operating mode.Recovery When you have the high availability option. or terminated workflows. and manually recover the workflow. the PowerCenter Integration Service stores the state of operation in the $PMStorageDir directory. the PowerCenter Integration Service can automatically recover the workflow. automatic recovery is disabled until you enable the service in normal mode. Note: The PowerCenter Integration Service does not automatically recover a workflow or task that you stop or abort through the PowerCenter Workflow Monitor or pmcmd. Running Workflows You can configure automatic task recovery in the workflow properties. aborted. Managing High Availability for the PowerCenter Integration Service 149 . The PowerCenter Integration Service behavior for task recovery does not depend on the operating mode. After you enable normal mode. aborted. or terminated status according to the recovery strategy for the task. The PowerCenter Integration Service can restore the workflow state after the workflow fails over to another node if you enable recovery in the workflow properties. The PowerCenter Integration Service can recover a workflow with a stopped. the PowerCenter Integration Service can recover terminated tasks while the workflow is running. the PowerCenter Integration Service can recover stopped. the PowerCenter Integration Service marks the workflow as terminated. The PowerCenter Integration Service behavior for task recovery does not depend on the operating mode. it begins recovery at the point of interruption. the task and the workflow are terminated. In safe mode. When you configure automatic task recovery. and the PowerCenter Integration Service operating mode: ¨ Stopped. or Terminated Workflows When the PowerCenter Integration Service restarts or fails over a service process. the PowerCenter Integration Service can automatically recover workflows and tasks based on the recovery strategy. it restores the state of operation and begins recovery from the point of interruption. or terminated workflows from the point of interruption. Suspended Workflows If a service process shuts down while a workflow is suspended. it can automatically recover interrupted workflows that are configured for recovery. The PowerCenter Integration Service does not recover any workflow task. the PowerCenter Integration Service can recover terminated tasks while the workflow is running. In normal mode. You can fix the errors that caused the workflow to suspend. aborted. You can also configure the number of times that the PowerCenter Integration Service tries to recover the task. the state of the workflows and tasks. the PowerCenter Integration Service automatically recovers the workflow. In normal and safe mode. the PowerCenter Integration Service does not recover the workflow until you enable the service in normal mode When the PowerCenter Integration Service recovers a workflow that failed over. The PowerCenter Integration Service can recover a task with a stopped. When the PowerCenter Integration Service recovers a workflow. aborted. and changes the workflow state to terminated.

If you are using a network switch to connect machines in the domain. To achieve high availability for FTP transmissions.Troubleshooting High Availability The solutions to the following situations might help you with high availability. use the auto-select option for the switch. but the Informatica domain is not resilient when machines are connected through a network switch. I have the high availability option. an error message appears if the connection cannot be established during the timeout period. The FTP server is an external system. You need to wait for the database resilience timeout to expire before you can enable the PowerCenter Repository Service with the updated connection string. I entered the wrong connection string for an Oracle database. the transfer does not necessarily continue as expected. you must use a highly available FTP server. Detailed information about the connection failure appears in the Output window. the connection error information appears at the command line. the error appears in the PowerCenter Integration Service log. I am not sure where to look for status information regarding client connections to the PowerCenter repository. In PowerCenter Client applications such as the PowerCenter Designer and the PowerCenter Workflow Manager. If the write process is more than half complete. For example. I have the high availability option.0 does not natively support the restart of file uploads or file downloads. If the transfer of a file to or from the IIS 6. Microsoft IIS 6. 150 Chapter 10: High Availability . the workflow log. If the PowerCenter Integration Service cannot establish a connection to the repository. and the session log. If you are using pmrep.0 server is interrupted and then reestablished within the client resilience timeout period. but my FTP server is not resilient when the network connection fails. Now I cannot enable the PowerCenter Repository Service even though I edited the PowerCenter Repository Service properties to use the right connection string. File restarts must be managed by the client connecting to the IIS server. the target file may be rejected.

152 ¨ Configuration Prerequisites. 151 . 160 Analyst Service Overview The Analyst Service is an application service that runs Informatica Analyst in the Informatica domain. You manage users. 155 ¨ Process Properties for the Analyst Service. privileges. Model Repository Service. You can use the Administrator tool to administer the Analyst Service. You can create and recycle an Analyst Service in the Informatica domain to access the Analyst tool. 155 ¨ Properties for the Analyst Service. 158 ¨ Creating and Deleting Audit Trail Tables. the Analyst tool. You manage permissions for projects and objects in the Analyst tool. the Service Manager restarts the Analyst Service. 154 ¨ Recycling and Disabling the Analyst Service. You can associate one Data Integration Service with more than one Analyst Service. staging database. and a flat file cache location. 159 ¨ Creating and Configuring the Analyst Service. You can run more than one Analyst Service on the same node. The Analyst Service connects to a Data Integration Service. 151 ¨ Analyst Service Architecture. groups. and roles on the Security tab of the Administrator tool. The Analyst Service manages the connections between service components and the users that have access to the Analyst tool. 152 ¨ Configure the TLS Protocol.CHAPTER 11 Analyst Service This chapter includes the following topics: ¨ Analyst Service Overview. When you recycle the Analyst Service. 160 ¨ Creating an Analyst Service. You can associate one Model Repository Service with an Analyst Service.

and standardize data in an enterprise. You can also manage and provide reference data to developers in a data quality solution. The Data Integration Service and the Model Repository Service must be enabled.Analyst Service Architecture The Analyst Service is an application service that runs the Analyst tool and manages connections between service components and Analyst tool users. The Analyst Service manages the connection to the database that stores bad record and duplicate record tables. you need to complete the prerequisite tasks for the service. ¨ Profiling warehouse database. The following figure shows the Analyst tool components that the Analyst Service manages on a node in the Informatica domain: The Analyst Service manages the connections between the following components: ¨ Data Integration Service. manage scorecards. Configuration Prerequisites Before you configure the Analyst Service. You can perform column and rule profiling. and manage bad records and duplicate records in the Analyst tool. cleanse. The Analyst Service manages the Analyst tool. You can edit the tables in the Analyst tool. The Analyst Service manages the connection to the directory that stores uploaded flat files that you use as imported reference tables and flat file sources in the Analyst tool. You need a database to store the reference tables you create or import in the Analyst tool. update. Use the Analyst tool to analyze. You need a keystore file if you configure the Transport Layer Security protocol for the Analyst Service. The Data Integration Service stores profiling information and scorecard results in the profiling warehouse database. 152 Chapter 11: Analyst Service . The Analyst Service manages the connection to a Data Integration Service for the Analyst tool to run or preview project components in the Analyst tool. ¨ Model Repository Service. and a directory to upload flat files that the Data Integration Service can access. ¨ Staging database. Use the Analyst tool to collaborate with data quality and data integration developers on data quality integration solutions. The Analyst tool connects to the model repository database to create. and delete projects and objects in the Analyst tool. The Analyst Service manages the connection to a Model Repository Service for the Analyst tool. ¨ Informatica Analyst. ¨ Flat file cache location.

Microsoft SQL Server. Database user name. You can use Oracle.:'"/?. ¨ Model Repository Service. Type of relational database.IBM DB2: <database name> . you must also create repository content if no content exists for the model repository. you can specify an existing Data Integration Service and Model Repository Service. It also cannot contain spaces or the following special characters: `~%^*+={}\. you create a database connection that the Data Integration Service uses to connect to the database. The following table describes the database connection options if you create a database: Option Name Description Name of the connection. ¨ Specify a location for the flat file cache.<>|!()][ Description Database Type Username Password Connection String Description of the connection. Password for the database user name. You can edit the tables in the Analyst tool. The name is not case sensitive and must be unique within the domain. It cannot exceed 128 characters or begin with @. When you create the Analyst Service. The description cannot exceed 765 characters. Connection string used to access data from the database. The Analyst Service requires the following associated services: ¨ Data Integration Service. After you create a database. the associated Data Integration Service and the Model Repository Service must be enabled. When you create the Analyst Service. When you create a Data Integration Service you also create a profiling warehouse database to store profiling information and scorecard results. You can select Oracle. Before you create a Model Repository Service you must create a database to store the model repository. Associated Services Before you configure the Analyst Service. . When you create the Model Repository Service.Oracle: <database name listed in TNSNAMES entry> Configuration Prerequisites 153 . or IBM DB2 as staging databases.The Analyst Service requires the following prerequisite tasks: ¨ Create associated services. you must also create content if no content exists for the database.. ¨ Create a staging database. When you create the database connection for the database.Microsoft SQL Server: <server name>@<database name> . Staging Databases The Analyst Service uses a staging database to store bad record and duplicate record tables. Microsoft SQL Server. or IBM DB2. you select an existing database connection or create a database connection.

Code Page Flat File Cache Create a directory to store uploaded flat files from a local machine to a location in the Informatica services installation directory that the Data Integration Service can access. Informatica Analyst uses the files from this directory to create a reference table or file object.Option JDBC URL Description JDBC connection URL used to access metadata from the database. you can create a directory named "flatfilecache" in the following location: <Informatica_services_installation_directory>\server\ Keystore File A keystore file contains the keys and certificates required if you enable Transport Layer Security (TLS) and use the HTTPS protocol for the Analyst Service.Microsoft SQL Server: jdbc:informatica:sqlserver://<host name>:<port>. You can configure the TLS protocol when you create the Analyst Service. security warnings and error messages for the browser appear when you access the Analyst tool.SID=<database name> . If you do not use a certified keystore file.IBM DB2: jdbc:informatica:db2://<host name>:<port>. you can configure the Transport Layer Security (TLS) protocol mode for the Analyst Service. keytool wraps the public key into a self-signed certificate. You can create the keystore file when you install Informatica services or you can create a keystore file with a keytool.DatabaseName=<database name> .DatabaseName=<database name> Code page use to read from a source database or write to a target database or file. Note: You must use a certified keystore file. Configure the TLS Protocol For greater security. You can use the self-signed certificate or use a certificate signed by a certificate authority. Keystore File 154 Chapter 11: Analyst Service . The following table describes the TLS protocol properties that you can configure when you create the Analyst Service: Property HTTPS Port Description HTTPS port number that the Informatica Analyst application runs on when you enable the Transport Layer Security (TLS) protocol. Location of the file that includes private or public key pairs and associated certificates. keytool is a utility that generates and stores private or public key pairs and associated certificates in a file called a “keystore.Oracle: jdbc:informatica:oracle://<host_name>:<port>. . When you import a reference table or flat file source. For example.” When you generate a public or private key pair. Use a different port number than the HTTP port number.

and the node in the Informatica domain that the Analyst Service runs on. ¨ Abort. For each service properties section. you stop and start the service to make the Analyst tool available again. Click the Recycle button to start the service. Recycling and Disabling the Analyst Service Use the Administrator tool to recycle and disable the Analyst Service. Disable an Analyst Service to perform maintenance or temporarily restrict users from accessing Informatica Analyst. Properties for the Analyst Service After you create an Analyst Service. Default is "changeit. In the Navigator." Secure Sockets Layer Protocol for security. You can configure the following types of Analyst Service properties: ¨ General Properties ¨ Model Repository Service Options ¨ Data Integration Service Options ¨ Metadata Manager Service Options ¨ Staging Database ¨ Logging Options ¨ Custom Properties General Properties for the Analyst Service General properties for the Analyst Service include the name and description of the Analyst Service.Property Keystore Password SSL Protocol Description Plain-text password for the keystore file. When you recycle the Analyst Service. Allows the jobs to run to completion before disabling the service. When you disable the Analyst Service. Tries to stop all jobs before aborting them and disabling the service. select the Analyst Service and click the Disable button to stop the service. You can configure Analyst Service properties on the Properties tab in the Administrator tool. Note: The Model Repository Service and the Data Integration Service must be running before you recycle the Analyst Service. You can configure these properties when you create the Analyst Service. Recycling and Disabling the Analyst Service 155 . click Edit to modify the service properties. you must choose the mode to disable it in. When you disable the Analyst Service. You can choose one of the following options: ¨ Complete. you can configure the Analyst Service properties. you also stop the Analyst tool.

The name is not case sensitive and must be unique within the domain. It also cannot contain spaces or the following special characters: `~%^*+={}\. The characters must be compatible with the code page of the associated repository. License assigned to the Analyst Service. You must recycle the Analyst Service if you associate another Model Repository Service with the Analyst Service.:'"/?.The following table describes the general properties for the Analyst Service: Property Name Description Name of the Analyst Service. The following table describes the Data Integration Service properties for the Analyst Service: Property Data Integration Service Name Description Data Integration Service name associated with the Analyst Service.. If you change the node. LDAP Security domain for the user who manages the Model Repository Service. Username Password Security Domain Data Integration Service Options Data Integration Service properties include the Data Integration Service associated with the Analyst Service and the flat file cache location. The name cannot exceed 128 characters or begin with @. The Analyst Service manages the connection to a Data Integration Service for Informatica Analyst. The Analyst Service manages the connections to the Model Repository Service for Informatica Analyst.<>|!()][ Description Node Description of the Analyst Service. Node in the Informatica domain on which the Analyst Service runs. The description cannot exceed 765 characters. Location of the flat file cache where Informatica Analyst stores uploaded flat files. License Model Repository Service Options Model Repository Service property includes the Model Repository Service that is associated with the Analyst Service. When you import a reference table or flat file source. you must recycle the Analyst Service. The following table describes the Model Repository Service properties for the Analyst Service: Property Model Repository Service Description Model Repository Service associated with the Analyst Service. Informatica Analyst uses the files from this Flat File Cache Location 156 Chapter 11: Analyst Service . The database user name for the Model repository. You must recycle the Analyst Service if you associate another Data Integration Service with the Analyst Service. An encrypted version of the database password for the Model repository.

Error. Restart the Analyst Service if you change the flat file location. Metadata Manager Service Options The Metadata Manager Service Options provides the option to select a Metadata Manager Service by name. Staging Database The Staging Database properties include the database connection name and properties for an IBM DB2 EEE database or a Microsoft SQL Server database. the Analyst tool cannot create all the reference tables in the staging database. Default is Info. you must set the tablespace page size to a minimum of 8 KB. Logging Options The logging options include properties for the severity level for Analyst Service Logs. Password for the administrator user name. Username Password Security Domain User name for a Data Integration Service administrator. Trace. The following table describes the staging database properties for the Analyst Service: Property Resource Name Description Database connection name for the staging database. Custom Properties Custom properties include properties that are unique to your environment or that apply in special cases. Tablespace Name Schema Name Owner Name Note: IBM DB2 EEE databases use tablespaces as a container for tablespace pages. The schema name for a Microsoft SQL Server database. Use custom properties only at the request of Informatica Global Customer Support. Warning. Debug. Valid values are Info. Properties for the Analyst Service 157 . If the tablespace page size is less than 8 KB. If you use an IBM DB2 EEE database as the staging database. Database schema owner name for a Microsoft SQL Server database. You must recycle the Analyst Service if you use another database connection name. An Analyst Service does not have custom properties when you initially create it. Name of the security domain that the user belongs to. Tablespace name for an IBM DB2 EEE database with multiple partitions. Fatal.Property Description directory to create a reference table or file object.

Default is 8085.Process Properties for the Analyst Service The Analyst Service runs the Analyst Service process on a node. HTTPS port number that the Analyst tool runs on when you enable the Transport Layer Security (TLS) protocol. The state can be enabled or disabled. When you select the Analyst Service in the Administrator tool. you can view the service processes for the Analyst Service on the Processes tab. Status can be enabled or disabled. The following table describes the security properties for the Analyst Service process: Property HTTP Port Description HTTP port number on which the Analyst tool runs. State of the service process running on the node. You can configure the following types of Analyst Service process properties: ¨ Analyst Security Options ¨ Advanced Properties ¨ Custom Properties ¨ Environment Variables Node Properties for the Analyst Service Process The following table describes the node properties for the Analyst Service process: Property Node Node Status Process Configuration Process State Description Node that the service process runs on. HTTPS Port Keystore File 158 Chapter 11: Analyst Service . Note: You must select the node to view the service process properties in the Service Process Properties panel. Location of the file that includes private or public key pairs and associated certificates. Use a port number that is different from the HTTP port number for the Data Integration Service. Status of the node. You can view the service process properties in the Service Process Properties panel. You must recycle the service if you change the HTTPS port number. Use a differnet port number than the HTTP port number. Analyst Security Options for the Analyst Service Process The Analyst Service Options include security properties for the Analyst Service process. You must recycle the service if you change the HTTP port number. Status of the process configured to run on the node. You can view the node properties for the service process in the service panel.

The following table describes the environment variables for the Analyst Service process: Property Environment Variables Description Environment variables defined for the Analyst Service process. Advanced Properties for the Analyst Service Process Advanced properties include properties for the maximum heap size and the Java Virtual Manager (JVM) memory settings. ." Secure Sockets Layer Protocol for Security.k for kilobytes. Append one of the following letters to the value to specify the units: . Environment Variables for the Analyst Service Process You can edit environment variables for the Analyst Service process. When you configure the JVM options. Use custom properties only at the request of Informatica Global Customer Support. Custom Properties for the Analyst Service Process Custom properties include properties that are unique to your environment or that apply in special cases. An Analyst Service does not have custom properties when you initially create it. Use this property to increase the performance. . The following table describes the advanced properties for the Analyst Service process: Property Maximum Heap Size Description Amount of RAM allocated to the Java Virtual Machine (JVM) that runs the Analyst Service. Default is 512 megabytes. you must set the Java SDK classpath. and Java SDK maximum memory properties. Creating and Deleting Audit Trail Tables 159 .m for megabytes. JVM Command Line Options Java Virtual Machine (JVM) command line options to run Java-based programs. .Property Keystore Password SSL Protocol Description Plain-text password for the keystore file.b for bytes. Creating and Deleting Audit Trail Tables Audit trail tables store the audit trail log events that provide information about the reference tables you manage in the Analyst tool.g for gigabytes. Java SDK minimum memory. Default is "changeit.

3. 1. To create audit trail tables. Enter the Model Repository Service name and the user name and password to connect to the Model Repository Service. 3. Enter the staging database name. 2. select a Metadata Manager Service. You can also associate a Metadata Manager Service to connect to the Metadata Manager Business Glossary when searching for business terms in the Analyst tool. select the Analyst Service. The New Analyst Service window appears. Optionally. Optionally. choose to create content if no content exists under the specified database connection string.Create audit trail tables in the Administrator tool to view the audit trail log events for reference tables in the Analyst tool. Enter the general properties for the service and the location and HTTP port number for the service. click New > Analyst Service. click Delete. to delete the tables. Complete the prerequisite tasks for configuring the Analyst Service. 2. Delete audit trail tables after an upgrade. Enter the Data Integration Service Options properties. In the Administrator tool. you can configure the service properties and service process properties. Configure the Analyst Service process properties. 6. click the Connections tab to create another database connection. Default selects the option to not create content. or to use another database connection for a different reference table. click Actions > Audit Trail tables > Create. click Create Folder to create another folder. Creating an Analyst Service Create an Analyst Service to manage the Informatica Analyst application and to grant users access to Informatica Analyst. 4. 5. 9. Configure the Analyst Service properties. Optionally. 8. You can enable the Analyst Service to make the Analyst tool accessible to users. After you create the Analyst Service. 4. 1. click the Domain tab. Click Next. In the Navigator. Creating and Configuring the Analyst Service Use the Administrator tool to create and configure the Analyst Service. On the Domain Actions menu. Optionally. Create the Analyst Service. Optionally. 5. 160 Chapter 11: Analyst Service . 7. Optionally. 2. click Select to select a staging database. 3. click Browse in the Location field to enter the location for the domain and folder where you want to create the service. Recycle the Analyst Service. 1. Optionally.

select Enable Service to enable the service after you create it.10. 12. Optionally. 11. Optionally. you must recycle the service to start it. RELATED TOPICS: ¨ “Properties for the Analyst Service” on page 155 Creating an Analyst Service 161 . Click Finish. 13. If you did not choose to enable the service earlier. Click Next. select Enable Transport Layer Security (TLS) and enter the TLS protocol properties.

Use the Address Validator transformation to perform address validation. 164 ¨ Recycling and Disabling the Content Management Service. A master Content Management Service also maintains probabilistic model data files across an Informatica domain. 167 Content Management Service Overview The Content Management Service is an application service that manages reference data. 163 ¨ Creating a Content Management Service. Identity populations You use identity population data when you run a mapping to perform duplicate analysis on identity data. Probabilistic models You use probabilistic model data when you run a mapping to perform token parsing or token labeling operations. To update the Data Integration Service with address reference data properties or to provide the Developer tool with information about installed 162 . You use the Administrator tool to administer the Content Management Service. It provides reference data information to the Data Integration Service and to the Developer tool.CHAPTER 12 Content Management Service This chapter includes the following topics: ¨ Content Management Service Overview. A probabilistic model is a reference data object that enables a Parser or Labeler transformation to identify different types of information in input strings. An identity is a set of values within a record that collectively identify a person or business. The Content Management Service manages the following types of reference data: Address reference data You use address reference data when you run a mapping to validate the postal accuracy of an address or fix errors in an address. 164 ¨ Content Management Service Properties. 165 ¨ Content Management Service Process Properties. Reference tables You use reference tables to verify the accuracy or structure of input data values in data quality transformations. 162 ¨ Content Management Service Architecture. Use a Match transformation or Comparison transformation to perform identity duplicate analysis.

you must associate the Data Integration Service with the Content Management Service on the same node. If the Data Integration Service runs a mapping that reads reference data. The Content Management Service is not used in runtime operations. you must create a Content Management Service in the Informatica domain. Reference tables The Content Management Service manages reference tables and data values. Content Management Service Architecture 163 . The Data Integration Service reads the configuration information when it runs a mapping that contains the Address Validator transformation. the Content Management Service updates the files on any other node that is associated with the same Model repository in the domain as the master Content Management Service. The Content Management Service must be available when you update information for the following reference data objects: Address reference data configuration The Content Management Service stores configuration information for the Address Validator transformation. Probabilistic model files The Content Management Service stores the location of the probabilistic model files on the node. The information is saved as metadata with the Address Validator transformation in the Model repository. or reference table. The Data Integration Service reads the population configuration when it runs a mapping that contains a Match transformation or Comparison transformation. Content Management Service Architecture The Developer tool and Analyst tool interact with the Content Management Service to get configuration information for reference data. Use the Reference Data Location property to identify the database that stores the reference table data. run the infacmd cms ResyncData command to update the new node with probabilistic model files from the master Content Management Service machine. Recycle the Content Management Service to start it. When you update a probabilistic model on a master Content Management Service machine. You create a Content Management Service on any node that contains a Data Integration Service. Identity population files The Content Management Service stores the list of installed population files.reference data. You cannot associate a Data Integration Service with more than one Content Management Service. The Content Management Service also stores the path to the address reference data files. If you use the Developer tool or an infacmd command to identify an address reference file. You cannot add a probabilistic model to a transformation if the model is not compiled. probabilistic model file. identity population file. If you add a node to a domain and you create a Content Management Service on the node. It also manages the compilation status of each probabilistic model. you select a population file from the current list. you must have Read access to the master Content Management Service. When you configure a Match transformation or Comparison transformation. The population configuration is saved as metadata with the transformation in the Model repository.

Optionally. select Enable Service to enable the service after you create it. Click Next. the property is set to True. Recycling and Disabling the Content Management Service Recycle the Content Management Service to apply the latest service or service process options. 3. The first Content Management Service you create on a domain is the master Content Management Service. click Create Folder to create another folder. 5. When you create additional Content Management Services on a domain. the property is set to False. 7. On the Domain tab. 1. one service operates as the master Content Management Service. you must recycle the service to start it. Create a Content Management Service to manage reference data properties and to provide the Developer tool with information about installed reference data. click Browse in the Location field to enter the location for the domain and folder where you want to create the service. Note: Do not configure the Transport Layer Security properties. In the Navigator. You can choose one of the following options: ¨ Complete. Optionally. Use the Master CMS property to identify the master Content Management Service.Master Content Management Service When you create multiple Content Management Services on a domain and associate the services with a Model repository. Creating a Content Management Service Before you create a Content Management Service. 4. ¨ Abort. select the Services and Nodes view. select the Content Management Service and click the Disable button to stop the service. you must choose the mode to disable it in. You cannot edit the Master CMS property in the Administrator tool. If you did not choose to enable the service. Use the infacmd cms UpdateServiceoptions command to change the master Content Management Service. Allows the jobs to run to completion before disabling the service. These are reserved for future use. Specify a Data Integration Service to associate with the Content Management Service. Enter the general properties for the service and the location for the service. When you disable the Content Management Service. 2. The New Content Management Service window appears. 6. Disable the Content Management Service to restrict user access to information about reference data in the Developer tool. Tries to stop all jobs before aborting them and disabling the service. Optionally. Click Finish. 164 Chapter 12: Content Management Service . Click Actions > New > Content Management Service. When you create the first Content Management Service on a domain. verify that a Data Integration Service is present in the domain.

. You recycle the Content Management Service in the following cases: ¨ Recycle the Content Management Service after you add or update address reference data. Node License Content Management Service Properties 165 .<>|!()][ Description Description of the Content Management Service. ¨ Recycle the Content Management Service after you change the reference data location on the Content Management Service. you must recycle the Content Management Service.:'"/?. and the node in the Informatica domain that the Content Management Service runs on. License assigned to the Content Management Service. Open a Developer tool or Analyst tool application to update the reference data location stored by the application. select the service in the Domain Navigator and click the Properties view. The name is not case sensitive and must be unique within the domain. If you change the node. The description cannot exceed 765 characters. Node in the Informatica domain on which the Content Management Service runs. Also recycle the Analyst Service associated with the Model Repository Service that the Content Management Service uses. The Data Integration Service must be running before you recycle the Content Management Service. The characters must be compatible with the code page of the domain repository.Click the Recycle button to restart the service. You configure these properties when you create the Content Management Service. ¨ Recycle the Content Management Service and the associated Data Integration Service after you update the address validation properties on the Content Management Service. Content Management Service Properties To view the Content Management Service properties. The following table describes the general properties for the Content Management Service: Property Name Description Name of the Content Management Service. The name cannot exceed 128 characters or begin with @. You can configure the following Content Management Service properties: ¨ General properties ¨ Multi-service options ¨ Associated services and reference data location properties ¨ Logging options ¨ Custom properties General Properties General properties for the Content Management Service include the name and description of the Content Management Service. It also cannot contain spaces or the following special characters: `~%^*+={}\. or after you change the file location for probabilistic model data files.

You specify the local path to the probabilistic model files in the NER options property on each Content Management Service. Associated Services and Reference Data Location Properties The Associated Services and Reference Data Location Properties identify the services associated with the Content Management Service. The Model repository identifies the Content Management Services instances in the domain at domain startup. Therefore. you must verify that a common set of probabilistic model data files is used across the nodes. Use the infacmd cms UpdateServiceoptions command to change the master Content Management Service. restart the domain to add the service to the set of Content Management Services that the master service recognizes. The following table describes the associated services and reference data location properties for the Content Management Service: Property Data Integration Service Description Data Integration Service associated with the Content Management Service. When you create more than one Content Management Service in a domain. Recycle the Content Management Service if you associate another Model Repository Service with the Content Management Service. It also identifies the database that stores reference data values for associated reference data objects. The Master CMS property defaults to True when it is the first Content Management Service on a domain. The master Content Management Service is the first service you create on a domain.Multi-Service Options The Multi-service options indicate whether the current service is the master Content Management Service in a domain. Reference Data Location Database connection name for the database that stores reference data values for the reference data objects defined in the associated Model repository. Note: You cannot edit the Master CMS property in the Administrator tool. If you add a Content Management Service to the domain. The Model repository stores metadata for reference data objects. 166 Chapter 12: Content Management Service . any probabilistic model file that you create or update on the master service host machine is copied from the master service machine to the locations specified by the other Content Management Services in the domain. All nodes that connect to the same Model repository in the domain must use the same probabilistic model data. The Data Integration Service reads reference data configuration information from the Content Management Service. Otherwise. Each Content Management Service reads probabilistic model data files from a local directory. Model Repository Service Model Repository Service associated with the Content Management Service. the Master CMS property defaults to False. The database stores reference data object row values. Recycle the Content Management Service if you associate another Data Integration Service with the Content Management Service. The following table describes the single property under multi-service options: Property Master CMS Description Indicates the master status of the service.

mapping run request failures. Writes FATAL and ERROR code messages to the log. and deployment failures. and ERROR code messages to the log.Logging Options Configure the Log Level property to set the logging level. you can view the service process for the Content Management Service on the Processes tab. . DEBUG messages are user request logs. The following table describes the Log Level properties: Property Log Level Description Level of error messages that the Data Integration Service writes to the Service log. Content Management Service Process Properties 167 . WARNING. You can view the node properties for the service process on the Processes tab. INFO. TRACE. . TRACE. ERROR messages include connection failures. Write FATAL. Writes FATAL.Trace. service errors. and ERROR messages to the log. WARNING.Error. Content Management Service Process Properties The Content Management Service runs the Content Management Service process on the same node as the service. Select the node to view the service process properties. TRACE messages log user request failures such as SQL request failures. failures to save or retrieve metadata. INFO messages include system and service change messages. Custom Properties Custom properties include properties that are unique to your environment or that apply in special cases. Choose one of the following message levels: . and ERROR messages to the log. INFO. A Content Management Service does not have custom properties when you initially create it. WARNING. FATAL messages include nonrecoverable system failures that cause the Data Integration Service to shut down or become unavailable. INFO. Writes FATAL. Use custom properties only at the request of Informatica Global Customer Support. When you select the Content Management Service in the Administrator tool. WARNING errors include recoverable system failures or warnings.Info.Warning. . DEBUG. and ERROR messages to the log. Writes FATAL messages to the log. Write FATAL.Debug.Fatal. WARNING. You can configure the following types of Content Management Service process properties: ¨ Content Management Service Security Options ¨ Address Validation Properties ¨ NER Options ¨ Custom Properties Note: The Content Management Service does not currently use the Content Management Service Security Options properties. . .

HTTPS Port Keystore Password SSL Protocol Address Validation Properties Configure address validation properties to determine how the Data Integration Service and the Developer tool read address reference data files.USA. Secure Sockets Layer Protocol to use with the service. Enter the three-character ISO country codes in a comma-separated list. you must recycle the Content Management Service and the Data Integration Service. such as the United States. Load the full reference database to increase performance. Default is 8105. For example. Some countries. Location of the Address Doctor reference data. Recycle the service if you change the HTTP port number. if you use general address reference data and Geocoding reference data. HTTPS port number that the service runs on when you enable the Transport Layer Security (TLS) protocol.FRA. enter DEU. After you update address validation properties. Use a different port number than the HTTP port number.USA. The following table describes the Content Management Service security options: Property HTTP Port Description Unique HTTP port number for the Reporting and Dashboards Service. Partial Pre-Load Countries List of countries for which batch/interactive metadata and indexing structures will be loaded into memory before address validation begins. The following table describes the address validation properties for the Content Management Service process: Property License Description License key to activate validation reference data. Reference Data Location Full Pre-Load Countries 168 Chapter 12: Content Management Service . Plain-text password for the keystore file. Recycle the service if you change the HTTPS port number. Required if you enable TLS and use HTTPS connections for the service. Enter keys as a comma-delimited list. Enter the full path where you installed the reference data. have large databases that require significant amounts of memory. for example.FRA. You may have more than one key.Content Management Service Security Options You can configure the Content Management Service to communicate with other components in the Informatica domain in secure mode. Enter the three-character ISO country codes in a comma-separated list. Install all Address Doctor data to a single location. enter DEU. List of countries for which all batch/interactive address reference data will be loaded into memory before address validation begins. Enter ALL to load all data sets. For example. for example TLS. Keystore File Path and file name of the keystore file that contains the private or public key pairs and associated certificates. Enter ALL to partially load all data sets.

Enter ALL to load no data sets. Load all reference data for a country to increase performance when processing addresses from that country. the MAP method can share reference data between multiple processes. Enter the three-character ISO country codes in a comma-separated list. Load the full reference database to increase performance. List of countries for which no geocoding reference data will be loaded into memory before address validation begins. Number of megabytes of memory that Address Doctor can allocate. Applies when the Address Validator transformation uses Suggestion List mode. Applies when the Address Validator transformation uses Suggestion List mode. However. Applies when the Address Validator transformation uses Suggestion List mode.FRA. Enter the three-character ISO country codes in a comma-separated list.Property Description Partial preloading increases performance when not enough memory is available to load the complete databases into memory. enter DEU. which generates a list of valid addresses that are possible matches for an input address. Some countries.USA. No Pre-Load Geocoding Countries Full Pre-Load Suggestion List Countries Partial Pre-Load Suggestion List Countries List of countries for which the address reference metadata and indexing structures will be loaded into memory before address validation begins. have large databases that require significant amounts of memory. Default is MAP. Enter ALL to load all data sets.FRA.USA.FRA. enter DEU.FRA. Memory Usage Content Management Service Process Properties 169 . No Pre-Load Countries List of countries for which no batch/interactive address reference data will be loaded into memory before address validation begins. such as the United States. For example. Enter ALL to load no data sets. Enter the three-character ISO country codes in a comma-separated list. Full Pre-Load Geocoding Countries Partial Pre-Load Geocoding Countries List of countries for which geocoding metadata and indexing structures will be loaded into memory before address validation begins.USA. For example. Enter the three-character ISO country codes in a comma-separated list. The MAP method and the LOAD method both allocate a block of memory and then read reference data into this block.USA. Enter ALL to load no data sets. No Pre-Load Suggestion List Countries List of countries for which no address reference data will be loaded into memory before address validation begins.USA. which generates a list of valid addresses that are possible matches for an input address. enter DEU. For example.FRA. Enter the three-character ISO country codes in a commaseparated list. Enter ALL to load all data sets. enter DEU. enter DEU. Partial preloading increases performance when not enough memory is available to load the complete databases into memory.FRA. Some countries. List of countries for which all reference data will be loaded into memory before address validation begins.FRA. which generates a list of valid addresses that are possible matches for an input address. For example. Preloading Method Determines how Address Doctor preloads address reference data into memory.USA. For example. Default is 4096. have large data sets that require significant amounts of memory. For example. enter DEU. List of countries for which all geocoding reference data will be loaded into memory before address validation begins. Enter the three-character ISO country codes in a comma-separated list. Enter the three-character ISO country codes in a commaseparated list. For example. Enter ALL to partially load all data sets. enter DEU.USA. such as the United States. Enter ALL to partially load all data sets.

Property Max Address Object Count Max Thread Count

Description Maximum number of Address Doctor instances to run at the same time. Default is 3. Maximum number of threads that the Address Doctor can use. Set to the total number of cores or threads available on a machine. Default is 2. Size of cache for databases that are not preloaded. Caching reserves memory to increase lookup performance in reference data that has not been preloaded. Set the cache size to LARGE unless all the reference data is preloaded or you need to reduce the amount of memory usage. Enter one of the following options for the cache size in uppercase letters: - NONE. No cache. Enter NONE if all reference databases are preloaded. - SMALL. Reduced cache size. - LARGE. Standard cache size. Default is LARGE.

Cache Size

Address Reference Data Preload Values
If you run a mapping that reads batch/interactive, fast completion, or geocoding reference data, you must specify how the Integration Service loads the reference data. The Integration Service can use a different method to load data for each country. For example, you can specify full preload for United States batch/interactive data and partial preload for United Kingdom batch/interactive data. The Integration Service can also use a different preload method for each type of data. For example, you can specify full preload for United States batch/interactive data and partial preload for United States geocoding data. You must enter at least one country abbreviation as a preload value for each type of reference data that a mapping reads. Enter ALL to apply a preload setting for all countries. Full preload settings supersede partial preload settings, and partial preload settings supersede settings that indicate no data preload. For example, if you enter ALL for no data preload and enter USA for full preload, the Integration Service loads all United States data into memory and does not load data for any other country. If you do not have a preload requirement, enter ALL for no data preload for any type of reference data that you plan to use. You do not specify a preload value for Supplementary data.

NER Options
The NER Options property provides the location of probabilistic model data files on the Informatica services machine. A probabilistic model is a type of reference data set. Use probabilistic models with transformations that perform Named Entity Recognition (NER) analysis. The following table describes the NER Options property:
Property NER File Location Description Path to the probabilistic model files. The property reads a relative path from the following directory in the Informatica installation:
/tomcat/bin

The default value is ./ner, which indicates the following directory:
/tomcat/bin/ner

170

Chapter 12: Content Management Service

Property

Description The file names have the following format:
filename.ner .

Custom Properties for the Content Management Service Process
Custom properties include properties that are unique to your environment or that apply in special cases. A Content Management Service does not have custom properties when you initially create it. Use custom properties only at the request of Informatica Global Customer Support.

Content Management Service Process Properties

171

CHAPTER 13

Data Director Service
This chapter includes the following topics:
¨ Data Director Service Overview, 172 ¨ Configuration Prerequisites, 172 ¨ Creating a Data Director Service, 173 ¨ Data Director Service Properties, 173 ¨ Data Director Service Process Properties, 175 ¨ TLS Protocol Configuration, 176 ¨ Recycle and Disable the Data Director Service, 177

Data Director Service Overview
The Data Director Service is an application service that runs the Informatica Data Director for Data Quality web application in the Informatica domain. A data analyst uses Informatica Data Director for Data Quality to perform manual review and update operations in database tables. A data analyst logs in to Informatica Data Director for Data Quality when assigned an instance of a Human task. A Human task is a task in a workflow that specifies user actions in an Informatica application. The Data Director Service connects to a Data Integration Service. You configure a Human Task Service module in the Data Integration Service so that the Data Integration Service can start a Human task in a workflow. You use the Administrator tool to administer the Data Director Service. You can create and recycle a Data Director Service in the Informatica domain to access Informatica Data Director for Data Quality. When you recycle the Data Director Service, the Service Manager restarts the service. You manage users, groups, privileges, and roles on the Security tab of the Administrator tool. You manage permissions for workflows and tasks in the Developer tool. You can run more than one Data Director Service on the same node.

Configuration Prerequisites
Before you create the Data Director Service, verify that a Data Integration Service is enabled in the domain. If you configure the Transport Layer Security protocol for the Data Director Service, you need a keystore file.

172

Complete the following tasks before you create the service:
¨ Verify that the Data Integration Service you want to associate with the Data Director Service is enabled. The

Data Integration Service must exist in the domain.
¨ If you configure the Transport Layer Security protocol for the Data Director Service, create a keystore file.

Keystore File
A keystore file contains the keys and certificates required if you enable Transport Layer Security (TLS) and use the HTTPS protocol for the Data Director Service. You can create the keystore file when you install Informatica services or you can create a keystore file with a keytool. keytool is a utility that generates and stores private or public key pairs and associated certificates. keytool stores the key pairs and associated certificates in a file called a “keystore.” When you generate a public or private key pair, keytool wraps the public key into a self-signed certificate. You can use the self-signed certificate or use a certificate signed by a certificate authority. Note: You must use a certified keystore file. If you do not use a certified keystore file, security warnings and error messages for the browser appear when you access Informatica Data Director for Data Quality.

Creating a Data Director Service
Create a Data Director Service to enable the Informatica Data Director for Data Quality web application and to grant users access to Informatica Data Director for Data Quality. 1. 2. In the Administrator tool, click the Domain tab. On the Domain Actions menu, click New > Data Director Service. The New Data Director Service window appears. 3. Specify the properties for the service. Optionally, click Browse in the Location field to change the domain location. 4. 5. 6. 7. 8. 9. Select the Data Integration Service on which to activate the Human Task Service Module. Click Next. Enter the HTTP port to use for connection to Informatica Data Director for Data Quality. Optionally, select Enable Transport Layer Security (TLS) and enter the TLS protocol properties. Click Finish. Recycle the service to start it.

Data Director Service Properties
After you create a Data Director Service, you can configure the service properties on the Properties tab in the Administrator tool. You can configure the following types of Data Director Service properties:
¨ General properties

Creating a Data Director Service

173

¨ Human task service properties ¨ Custom properties ¨ Logging properties

General Properties
General properties for the Data Director Service include the name and description of the service and the node in the Informatica domain that the service runs on. You configure the properties when you create the Data Director Service. The following table describes the general properties for the Data Director Service:
Property Name Description Name of the service. The name is not case sensitive and must be unique within the domain. The characters must be compatible with the code page of the domain repository. The name cannot exceed 128 characters or begin with @. It also cannot contain spaces or the following special characters: `~%^*+={}\;:'"/?.,<>|!()][ Description Node Description of the service. The description cannot exceed 765 characters. Node in the Informatica domain on which the service runs. If you change the node, you must recycle the Data Director Service. License assigned to the service.

License

HT Service Options Property
The HT Service Options property identifies the Data Integration Service on which you activate the Human Task Service Module. The following table describes the HT Service Options property:
Property Data Integration Service Description Data Integration Service on which you activate the Human Task Service Module. To apply changes, recycle the Data Director Service.

Custom Properties
Custom properties include properties that are unique to your environment or that apply in special cases. A Data Director Service does not have custom properties when you create it. Use custom properties only at the request of Informatica Global Customer Support.

Logging Options Property
The logging options include a property to set the severity level for Data Director Service logs. Valid values are Info, Error, Warning, Trace, Debug, Fatal. Default is Info.

174

Chapter 13: Data Director Service

Data Director Service Process Properties
The Data Director Service runs the Data Director Service process on the same node as the service. When you select the Data Director Service in the Administrator tool, you can view the service process for the service on the Processes tab You can also view the node properties for the service process on the Processes tab. Select the node to view the service process properties. You can configure the following types of Data Director Service process properties:
¨ Security property ¨ Advanced option properties ¨ Environment variables ¨ Custom properties

Security Properties
You can configure the Transport Layer Security (TLS) protocol mode for the Data Director Service process. The following table describes the security properties for the Data Director Service process:
Property HTTP Port Description HTTP port number on which Informatica Data Director for Data Quality runs. Use a port number that is different from the HTTP port number for the Data Integration Service. Recycle the service if you change the HTTP port number. HTTPS port number that Informatica Data Director for Data Quality runs on when you enable the Transport Layer Security (TLS) protocol. Use a different port number than the HTTP port number. Recycle the service if you change the HTTPS port number. Location of the file that includes private or public key pairs and associated certificates. Plain-text password for the keystore file. Default is "changeit." Secure Sockets Layer Protocol for security.

HTTPS Port

Keystore File

Keystore Password SSL Protocol

Advanced Option Properties
Advanced options include properties for the maximum heap size and the Java Virtual Manager (JVM) memory settings.

Data Director Service Process Properties

175

The following table describes the advanced properties for the Data Director Service process:
Property Max Heap Size Description Amount of RAM allocated to the Java Virtual Machine (JVM) that runs the Data Director Service. Use this property to increase the performance. Append one of the following letters to the value to specify the units: - b for bytes. - k for kilobytes. - m for megabytes. - g for gigabytes. Default is 512 megabytes. JVM Options Java Virtual Machine (JVM) command line options to run Java-based programs. When you configure the JVM options, you must set the Java SDK classpath, Java SDK minimum memory, and Java SDK maximum memory properties.

Environment Variable Properties
You can edit environment variables for the Data Director Service process. No environment variable is set when you create the service.

Custom Properties for the Data Director Service Process
Custom properties include properties that are unique to your environment or that apply in special cases. A Data Director Service process does not have custom properties when you create the service. Use custom properties only at the request of Informatica Global Customer Support.

TLS Protocol Configuration
For greater security, you can configure the Transport Layer Security (TLS) protocol mode for the Data Director Service. You can configure the TLS protocol when you create the service. The following table describes the TLS protocol properties that you can configure when you create the Data Director Service:
Property HTTPS Port Description HTTPS port number that the Informatica Data Director for Data Quality application runs on when you enable the Transport Layer Security (TLS) protocol. Use a different port number than the HTTP port number. Location of the file that includes private or public key pairs and associated certificates. Plain-text password for the keystore file. Default is "changeit." Secure Sockets Layer Protocol for security.

Keystore File

Keystore Password SSL Protocol

176

Chapter 13: Data Director Service

Recycle and Disable the Data Director Service
Use the Administrator tool to recycle and disable the Data Director Service. Disable a Data Director Service to perform maintenance or temporarily restrict user access to Informatica Data Director for Data Quality. Recycle the Data Director Service to stop and start the service. After you recycle the service, users can log in to Informatica Data Director for Data Quality. Select the Data Director Service and click the Disable button to stop the service. Click the Recycle button to stop and start the service. When you disable the Data Director Service, you choose the mode to disable it in. Choose one of the following options:
¨ Complete. Allows the jobs to run to completion before disabling the service. ¨ Abort. Tries to stop all jobs before aborting them and disabling the service.

Note: Verify that the Data Integration Service is running before you recycle the Data Director Service.

Recycle and Disable the Data Director Service

177

CHAPTER 14

Data Integration Service
This chapter includes the following topics:
¨ Data Integration Service Overview, 178 ¨ Data Integration Service Architecture, 179 ¨ Creating a Data Integration Service, 185 ¨ Data Integration Service Properties, 188 ¨ Data Integration Service Process Properties, 196 ¨ Configuration for the Data Integration Service Grid, 200 ¨ Content Management for the Profiling Warehouse, 202 ¨ Web Service Security Management, 202 ¨ Enabling, Disabling, and Recycling the Data Integration Service, 203 ¨ Result Set Caching, 204

Data Integration Service Overview
The Data Integration Service is an application service in the Informatica domain that performs data integration tasks for the Analyst tool, the Developer tool, and external clients. When you preview or run mappings, profiles, SQL data services, and web services in Informatica Analyst or Informatica Developer, the application sends requests to the Data Integration Service to perform the data integration tasks. When you start a command from the command line or an external client to run mappings, SQL data services, web services, and workflows in an application, the command sends the request to the Data Integration Service. The Data Integration Service performs the following tasks:
¨ Runs mappings and generates mapping previews in the Developer tool. ¨ Runs profiles and generates previews for profiles in the Analyst tool and the Developer tool. ¨ Runs scorecards for the profiles in the Analyst tool and the Developer tool. ¨ Runs SQL data services and web services in the Developer tool. ¨ Runs mappings in a deployed application. ¨ Runs workflows in a deployed application. ¨ Caches data objects for mappings and SQL data services deployed in an application. ¨ Runs SQL queries that end users run against an SQL data service through a third-party JDBC or ODBC client

tool.
¨ Runs web service requests against a web service.

178

Create and configure a Data Integration Service in the Administrator tool. You can create one or more Data Integration Services on a node. When a Data Integration Service fails, it automatically restarts on the same node. When you create a Data Integration Service you must associate it with a Model Repository Service. When you create mappings, profiles, SQL data services, web services, and workflows, you store them in a Model repository. When you run or preview the mappings, profiles, SQL data services, and web services in the Analyst tool or the Developer tool, the Data Integration Service associated with the Model repository generates the preview data or target data. When you deploy an application, you must associate it with a Data Integration Service. The Data Integration Service runs the mappings, SQL data services, web services, and workflows in the application. The Data Integration Service also writes metadata to the associated Model repository. During deployment, the Data Integration Service works with the Model Repository Service to create a copy of the metadata required to run the objects in the application. Each application requires its own run-time metadata. Data Integration Services do not share run-time metadata even when applications contain the same data objects.

Data Integration Service Architecture
The Data Integration Service performs the data transformation processes for mappings, profiles, SQL data services, web services, and workflows in a Model repository. Each component in the Data Integration Service performs its role to complete the data transformation process. The Mapping Service Module manages the data transformation for mappings. The Profiling Service Module manages the data transformation for profiles. The SQL Service Module manages the data transformation for SQL data services. The Web Service Module manages the data transformations for web services. The Workflow Service Module manages the running of workflows. The Deployment Manager and Data Object Cache Manager manage application deployment and data caching and ensure that the data objects required to complete data transformation are available. The Result Set Cache Manager manages temporary result set caches when SQL queries are run against an SQL data service and when a web service client sends a request to run a web service operation. The following diagram shows the architecture of the Data Integration Service:

Requests to the Data Integration Service can come from the Analyst tool, the Developer tool, or an external client. The Analyst tool and the Developer tool send requests to preview or run mappings, profiles, SQL data services, and web services. An external client can send a request to run deployed mappings. An external client can send SQL queries to access data in virtual tables of SQL data services, execute virtual stored procedures, and access metadata. An external client can also send a request to run a web service operation to read, transform, or write data.

Data Integration Service Architecture

179

When the Deployment Manager deploys an application, the Deployment Manager works with the Model Repository Service to store run-time metadata in the Model repository for the mappings, SQL data services, web services, and workflows in the application. If you choose to cache the data for an application, the Deployment Manager caches the data in a relational database.

Data Transformation Manager
The Data Transformation Manager (DTM) is the component in the Data Integration Service that extracts, transforms, and loads data to complete a data transformation process. When a service module in the Data Integration Service receives a request for data transformation, the service module calls the DTM to perform the processes required to complete the request. The service module runs multiple instances of the DTM to complete multiple requests for data transformation. For example, the Mapping Service Module runs a separate instance of the DTM each time it receives a request from the Developer tool to preview a mapping. When the DTM runs mappings, it creates data caches to temporarily store data used by the mapping objects. When it processes a large amount of data, the DTM writes the data into cache files. After the Data Integration Service completes the mapping, the DTM releases the data caches and cache files. The DTM consists of the following components:
¨ Logical DTM (LDTM). Compiles and optimizes requests for data transformation. The LDTM filters data at the

start of the process to reduce the number of rows to be processed and optimize the transformation process.
¨ Execution DTM (EDTM). Runs the transformation processes.

The LDTM and EDTM work together to extract, transform, and load data to optimally complete the data transformation.

Profiling Service Module
The Profiling Service Module is the component in the Data Integration Service that manages requests to run profiles and generate scorecards. When you run a profile in the Analyst tool or the Developer tool, the application sends the request to the Data Integration Service. The Profiling Service Module starts a DTM instance to get the profiling rules and run the profile. When you run a scorecard in the Analyst tool or the Developer tool, the application sends the request to the Data Integration Service. The Profiling Service Module starts a DTM instance to generate a scorecard for the profile. To create and run profiles and scorecards, you must associate the Data Integration Service with a profiling warehouse. The Profiling Service Module stores profiling data and metadata in the profiling warehouse.

Mapping Service Module
The Mapping Service Module is the component service in the Data Integration Service that manages requests to preview target data and run mappings. The following table lists the requests that the Mapping Service Module manages from the different client tools:
Request Preview target data based on mapping logic. Run a mapping. Client Tools Developer tool Command line Developer tool

180

Chapter 14: Data Integration Service

Request

Client Tools Third-party client tools

Run a mapping in a deployed application. Run an SQL data service. Run a web service.

Command line Developer tool Developer tool

Sample third-party client tools include SQL SQuirreL Client, DBClient, and MySQL ODBC Client. When you preview or run a mapping, the client tool sends the request and the mapping to the Data Integration Service. The Mapping Service Module starts a DTM instance, which generates the preview data or runs the mapping. If the preview includes a relational or flat file target, the Mapping Service Module writes the preview data to the target. When you preview data contained in an SQL data service in the Developer tool, the Developer tool sends the request and SQL statement to the Data Integration Service. The Mapping Service Module starts a DTM instance, which runs the SQL statement and generates the preview data. When you preview a web service operation mapping in the Developer tool, the Developer tool sends the request to the Data Integration Service. The Mapping Service Module starts a DTM instance, which runs the operation mapping and generates the preview data. Note: To preview relational table data using the Analyst tool or Developer tool, the database client must be installed on the machine on which the Mapping Service Module runs. You must configure the connection to the database in the Analyst tool or Developer tool.

REST Web Service Module
The REST Web Service Module is reserved for future use.

SQL Service Module
The SQL Service Module is the component service in the Data Integration Service that manages SQL queries sent to an SQL data service from a third party client tool. When the Data Integration Service receives an SQL request from a third party client tool, the SQL Service Module starts a DTM instance to run the SQL query against the virtual tables in the SQL data service. If you do not cache the data when you deploy an SQL data service, the SQL Service Module starts a DTM instance to run the SQL data service. Every time the third party client tool sends an SQL query to the virtual database, the DTM instance reads data from the source tables instead of cache tables.

Web Service Module
The Web Service Module is a component in the Data Integration Service that manages web service operation requests sent to a web service from a web service client. When the Data Integration Service receives requests from a web service client, the Web Service Module starts a DTM instance to run the operation mapping. The Web Service Module also sends the operation mapping response to the web service client.

Data Integration Service Architecture

181

When an external client makes the same request before the cache expires. the Result Set Cache Manager returns the cached results. If the application contains an SQL data service. The Result Set Cache Manager caches the results for a specified time period. The Workflow Service Module evaluates expressions in conditional sequence flows to determine whether to run the next task. When a Mapping task runs a mapping.Workflow Service Module The Workflow Service Module is the component in the Data Integration Service that manages requests to run workflows. You can also periodically refresh the cache from a command line program or from the Administrator tool. The Data Object Cache Manager initially caches the data when you enable the SQL data service or the web service. If the expression evaluates to true or if the sequence flow does not include a condition. Result Set Cache Manager The Result Set Cache Manager is the component of the Data Integration Service that manages result set caches. When you enable result set caching. The Workflow Service Module runs and manages the workflow instance. the database user or a third-party tool that you configure populates and refreshes the cache. Data Object Cache Manager When you deploy an application. By default. The Result Set Cache Manager stores the result set cache for SQL data services by user. the task passes output data back to the Workflow Service Module. Optimal performance for the cache depends on the speed and performance of the database. you can specify a cache table name for each data object. The task uses the input data to complete a single unit of work. The Workflow Service Module runs workflow objects in the order that the objects are connected. you can cache logical data objects and virtual tables. When you enable data object caching. If the application contains a web service. If the Result Set Cache Manager requires more space than allocated. it starts a DTM instance to run the mapping. the Data Integration Service receives the request. You can configure the schedule that the Data Object Cache Manager uses to refresh the cached data. When you specify a cache table name. you can cache logical data objects. The Data Object Cache Manager creates the cache tables and refreshes the cache. When the Result Set Cache Manager stores the results by user. the Data Integration Service only returns cached results to the user that ran the SQL query or sent the web service request. If you want to manage the data object cache through the database. it stores the data in cache files. the Data Object Cache Manager manages the data object cache in data object cache database. The Data Object Cache Manager is the component in the Data Integration Service that caches data for an application. the Workflow Service Module starts and passes input data to the connected task. If a cache does not exist or has expired. the Data Integration Service starts a DTM instance to process the request and then it stores the cached the results. You then enable caching for each virtual table and logical data object that you want to cache. The Result Set Cache Manager stores the result set cache for 182 Chapter 14: Data Integration Service . the Data Object Cache Manager ignores it. When you start a workflow instance in a deployed application. All applications that are deployed to a Data Integration Service use the same connection. A result set cache is the result of a DTM process that runs an SQL query against an SQL data service or a web service request against a web service operation. When a task finishes processing a unit of work. you can cache the logical data objects and virtual tables in a database. If you configure a refresh schedule for the cache in the Administrator tool. the Result Set Cache Manager creates in-memory caches to temporarily store the results of a DTM process. you first select the database connection for the database in which to store the data object cache. The Workflow Service Module uses this data to evaluate expressions in conditional sequence flows or uses this data as input for the remaining tasks in the workflow.

Data Integration Service Architecture 183 . All other nodes are worker service processes. After validation. You can view the logs in the log viewer of the Administrator tool. Note: The master service process also acts as a worker service process and completes jobs as well. Deployment Manager The Deployment Manager is the component in Data Integration Service that manages the applications. the Deployment Manager manages the interaction between the Data Integration Service and the Model Repository Service. When you run a job on a grid. The DTM stores the log files in a folder named builtinhandlers in the directory specified in the properties for the Data Integration Service process. When run on a grid. The DTM bypasses the Log Manager and sends the log events to log files. When the Data Integration Service runs mappings. web services. you improve scalability and performance by distributing tasks to service processes running on nodes in the grid. web services. and SQL data services in an application. When the DTM runs. one service process starts on each node in the grid. web services. the master service process runs all jobs that write to the Model repository. When a Mapping task in a workflow starts a DTM instance to run a mapping. When the Workflow Service Module runs workflows. the Data Integration Service remains available if a Data Integration Service node shuts down unexpectedly. it generates log events for the workflow. The Workflow Service Module stores the log files in a folder named workflow in the directory specified in the properties for the Data Integration Service process. it generates log events for the process that it is running. the Deployment Manager retrieves the run-time metadata and makes it available to the DTM. A grid is an alias assigned to a group of nodes that run jobs. If a worker service process is selected to run a job. Data Integration Service Grid You can configure the Data Integration Service to run on a single node or grid. The Workflow Service Module bypasses the Log Manager and sends the log events to log files. workflows. The worker service processes run all other types of jobs. When you enable the Data Integration Service that runs on a grid. The domain designates one service process as the master service process.web services by user when the web service uses WS-Security. it registers itself with the master service process so that the master is aware of the worker. and SQL data services in the application. the Data Integration Service is more resilient when it runs on a grid. workflows. the Deployment Manager works with the Model Repository Service associated with the Data Integration Service to store the run-time metadata required to run the mappings. The Deployment Manager creates a separate set of run-time metadata in the Model repository for each application. and SQL data services in the application and their dependent objects. The Deployment Manager starts and stops an application. The DTM stores the log files in the directory specified in the properties for the Data Integration Service process. Data Integration Service Logs The Data Integration Service generates operational and error log events that are collected by the Log Manager in the domain. To prevent concurrent writes to the Model repository. Also. When a worker service process starts. the Deployment Manager validates the mappings. When you deploy an application to a Data Integration Service. When it starts an application. workflows. then the next worker service process is selected instead. but all the threads of the node are busy. The Result Set Cache Manager stores the cache by the user name that is provided in the username token of the web service request. the DTM generates log events for the mapping.

and the Data Integration Service runs on a grid. Deployed mappings When you run a deployed mapping and the Data Integration Service runs on a grid. When you configure these properties. You can run the following types of jobs on a Data Integration Service grid: Workflows When you run a workflow and the Data Integration Service runs on a grid. the domain dispatches the preview query directly to a worker service process. However. the domain bypasses the master service process. specify the logical URL for the load balancer in the Web Service properties for the Data Integration Service. The master service process runs the workflow and non-mapping tasks. jobs that were running during the failover are not recovered. To ensure faster throughput.When you run a job on a Data Integration Service on a grid. The master service process uses round robin to dispatch each mapping task to a worker service process. To configure the external load balancer. a web service client running on any machine can send requests. the Data Integration Service uses an external HTTP load balancer to assign the request to a worker service process. When you preview multiple objects. When you run multiple queries against SQL data services. the new master service process runs the jobs after the failover. Profiles When you run a profile and the Data Integration Service runs on a grid. the domain uses round robin to dispatch each preview query to a worker service process. When you submit multiple requests against web services. By default. the domain dispatches the workflow to the master service process. the domain dispatches the mapping to a worker service process. the domain uses round robin to dispatch each query to a worker service process. the domain dispatches the query directly to a worker service process. To specify machines that can send web service request to a Data Integration Service. the domain bypasses the master service process. Web services When you submit a web service request and the Data Integration Service runs on a grid. Previews When you preview a mapping. the Data 184 Chapter 14: Data Integration Service . The master service process segments the profiling job into multiple jobs. and the remaining worker service processes register themselves with the new master. the master role fails over to another service process. To ensure faster throughput. all nodes retrieve object state information from the Model repository. You must manually restart these jobs. If you run multiple mappings. If a job was in queue but not started during the failover. HTTP Client Filter An HTTP client filter specifies web services client machine that can send requests to the Data Integration Service. The domain elects a new master from the rest of Data Integration Service processes. configure the HTTP client filter properties in the Data Integration Service properties. SQL data services When you run a query against an SQL data service and the Data Integration Service runs on a grid. or virtual table data. Note: You must configure the external HTTP load balancer. After a master service process failover. and then distributes the jobs across the worker service processes. the domain uses round robin to dispatch each mapping to a worker service process. If the master service process shuts down unexpectedly. The Data Integration Service balances the workload among the nodes based on the type of job. the domain uses round robin to dispatch each query to a worker service process. stored procedure output. the job runs on one or more nodes in the grid. the domain dispatches the profile to the master service process.

It cannot exceed 128 characters or begin with @. The New Data Integration Service . License key assigned to the Data Integration Service. select the grid where the Data Integration Service will run.. 3. Note: You can allow or deny requests from a web service client that runs on the same machine as the Data Integration Service. It also cannot contain spaces or the following special characters: `~%^*+={}\. The name is not case sensitive and must be unique within the domain. The description cannot exceed 765 characters. enter the following expression as an allowed IP Address: “192\. select the node where the Data Integration Service will run. On the Domain tab. Location License Assign Node Grid Creating a Data Integration Service 185 .1\.168\. To configure the Data Integration Service to accept web service requests from machines in a local network. The Data Integration Service either allows the request to continue or refuses to process the request.) as a wildcard character in a value. Click Actions > New > Data Integration Service. Domain where the Data Integration Service will run. If you assigned the Data Integration Service to a grid.Integration Service compares the IP address or host name of machines that submit web service requests against these properties. 2. Enter the following information: Property Name Description Name of the Data Integration Service. Select Single Node to assign the Data Integration Service on a node. Creating a Data Integration Service You can create one or more Data Integration Services for a Model Repository Service. 1.Step 1 of 15 dialog box appears. Select Grid to assign the Data Integration Service on a grid. The Data Integration Service refuses to process requests from machines with IP addresses that do not match this pattern. Example The Finance department wants to configure a web service to accept web service requests from a range of IP addresses. If you assigned the Data Integration Service to a single node.[0-9]*” The Data Integration Service accepts requests from machines with IP addresses that match this pattern. You can use constants or Java regular expressions as values for these properties. Enter the host name of the Data Integration Service machine in the allowed or denied host names property.:'"/?. You can include a period (. select the Services and Nodes view.<>|!()][ Description Description of the Data Integration Service.

User password to access the Model Repository Service. 14. User name to access the Model Repository Service. Click Next. The New Data Integration Service . If you enabled TLS protocol. 9. Enter a unique HTTP port number for the Data Integration Service. The New Data Integration Service . Click Next. Enter the pass through security properties. Select the modules that you want to enable. Default is 8095. When you enable the TLS protocol for the Data Integration Service. 8. The New Data Integration Service . The New Data Integration Service .Step 4 of 15 dialog box appears. LDAP security domain namespace for the Model repository User. Click Next. For more information about email server properties.Step 5 of 15 dialog box appears. 17. see “Deployment Options” on page 190. select Enable Transport Layer Security (TLS). enter the security information. 5.Step 3 of 15 dialog box appears. see “Modules ” on page 190.Step 6 of 15 dialog box appears. web service requests to the Data Integration Service can use the HTTP or HTTPS security protocol. For more information about the logging property. Click Next. 6. 12. see “Data Integration Service Security Properties” on page 196 and “HTTP Client Filter Properties” on page 196. For more information about pass through security properties. 15. see “Logging Properties” on page 190. The New Data Integration Service . Enter the logging property. Optionally. Click Next.Property Model Repository Service Description Model Repository Service that stores run-time metadata required to run the mappings and SQL data services. The namespace field appears when the Informatica domain contains an LDAP security domain. see “Pass-through Security Properties” on page 190. 16. Enter the deployment properties. Enter the logical data object and virtual table cache properties. 7. Username Repository User Password Repository User Namespace 4. 13. Enter the email server properties.Step 2 of 15 dialog box appears. 186 Chapter 14: Data Integration Service . 11. For more information about logical data object and virtual table cache properties. For more information about the modules. For more information about deployment properties. 10. see “Email Server Properties” on page 188. For more information about the security properties. see “Logical Data Object/ Virtual Table Cache Properties” on page 189.

Step 9 of 15 dialog box appears. Enter the HTTP client filter properties. Click Next. For more information about the Mapping Service module properties. Creating a Data Integration Service 187 .Step 11 of 15 dialog box appears. 19. Click Next. 21. 28. For more information about HTTP proxy server properties. the New Data Integration Service . For more information about the execution option property. If you elected to configure the SQL Service module. 20. see “HTTP Client Filter Properties” on page 196. For more information about the SQL Service module properties. If you did not choose to enable the service. Click Next. 27. The New Data Integration Service . Configure the Workflow Service module properties. 23. 33. Enter the HTTP proxy server properties. the New Data Integration Service . 26. see “Result Set Cache Properties” on page 192. see “Workflow Service Module” on page 182. For more information about the result set cache properties. see “HTTP Proxy Server Properties” on page 191. Configure the Mapping Service module properties. For more information about the Workflow Service module properties. 24. Enter the result set cache properties. For more information about HTTP client filter properties. Enter the execution option property. For more information about the Web Service module properties. 29. 31.Step 7 of 15 dialog box appears. 25. The New Data Integration Service . 32.Step 15 of 15 dialog box appears.18. see “Web Service Properties” on page 195. 22. If you elected to configure the Workflow Service module. you must recycle the service to start it. Click Finish. the New Data Integration Service . If you elected to configure the Web Service module. If you elected to configure the Mapping Service module. the New Data Integration Service . see “Mapping Service Module” on page 180. see “SQL Service Module” on page 181.Step 14 of 15 dialog box appears. Configure the SQL Service module properties. Click Next. Select the module plugins to configure. see “Execution Options” on page 192.Step 8 of 15 dialog box appears. Click Next. Configure the Web Service module properties. 30. Click Next.

Grid where the Data Integration Service runs if the service runs on a grid. User password to access the Model repository. Read only. License key that you enter when you create the service. select the service in the Domain Navigator and click the Properties view. You can change the properties while the service is running. User name to access the Model repository. The user must have the Create Project privilege for the Model Repository Service. 188 Chapter 14: Data Integration Service . enter the Microsoft Exchange Server for Microsoft Outlook. Click the grid name to view the grid configuration. but you must restart the service for most properties to take effect. Description Name of the Data Integration Service. Password Email Server Properties The following table describes the email server properties that the Data Integration Service uses to send email notifications from a workflow: Property SMTP Server Host Name Description The SMTP outbound mail server host name. For example. Click the node name to view the node configuration. Short description of the Data Integration Service. Read only. Grid Model Repository Properties The following table describes the Model repository properties for the Data Integration Service: Property Model Repository Service User Name Description Service that stores run-time metadata required to run mappings and SQL data services. General Properties The following table describes general properties of a Data Integration Service: General Property Name Description License Assign Node Node where the Data Integration Service runs if the service runs on a node.Data Integration Service Properties To view the Data Integration Service properties.

If true. Use TLS Security Indicates that the SMTP server uses the Transport Layer Security (TLS) protocol. if required by the outbound SMTP mail server. Sender Email Address Email address that the Data Integration Service uses in the From field when sending notification emails from a workflow.000. Default is admin@example. Use SSL Security Indicates that the SMTP server uses the Secure Sockets Layer (SSL) protocol. Cache Connection Maximum Concurrent Refresh Requests Data Integration Service Properties 189 . SMTP Server Port Port number used by the outbound SMTP mail server. if required by the outbound SMTP mail server. SMTP Authentication Enabled Indicates that the SMTP server is enabled for authentication. Maximum number of cache refreshes that can occur at the same time. Valid values are from 1 to 65535. Default is 25.com. SMTP Server User Name SMTP Server Password SMTP Server Connection Timeout SMTP Server Communication Timeout Maximum number of seconds that the Data Integration Service waits to send an email before it times out.600. Maximum number of seconds that the Data Integration Service waits to connect to the SMTP server before it times out.Property Description Default is localhost. Logical Data Object/Virtual Table Cache Properties The following table describes the data object and virtual table cache properties: Property Cache Removal Time Description The amount of milliseconds the Data Integration Service waits before cleaning up cache storage after a refresh. Default is false. The database connection name for the database that stores the data object cache. Limit the concurrent cache refreshes to maintain system resources. Default is false. Select a valid connection object name. Password for authentication upon sending. Default is 60. Default is 3. Default is false. User name for authentication upon sending. then the outbound mail server requires a user name and password. Default is 60.

Info. Default Deployment mode affects applications that you deploy from the Developer tool. Writes FATAL. INFO. .Enable Only. INFO messages include system and service change messages.Enable and Start. Enable the application but do not start the application. Write FATAL. TRACE messages log user request failures such as SQL request failures. Choose one of the following options: . you might allow users access to data in the cache database that they might not have in an uncached environment. WARNING errors include recoverable system failures or warnings. Modules By default. 190 Chapter 14: Data Integration Service . mapping run request failures. and ERROR messages to the log. and Administrator tool. failures to save or retrieve metadata. DEBUG. Deployment Options The following table describes the deployment options for the Data Integration Service: Property Default Deployment Mode Description Determines whether to enable and start each application after you deploy it to a Data Integration Service. TRACE. . service errors.Disable. command line. INFO. and ERROR messages to the log.Logging Properties The following table describes the log level properties: Property Log Level Description Level of error messages that the Data Integration Service writes to the Service log. Writes FATAL and ERROR code messages to the log.Warning. and deployment failures. and ERROR code messages to the log. Write FATAL. Populates data object cache using the credentials from the connection object. Do not enable the application.Trace. . WARNING. Note: When you enable data object caching with pass-through security. You can disable some of the modules.Error. Writes FATAL messages to the log. and ERROR messages to the log.Debug. . . . . WARNING. Enable the application and start the application. Pass-through Security Properties The following table describes the pass-through security properties: Property Allow Caching Description Allows data object caching for all pass-through connections in the Data Integration Service. Choose one of the following message levels: . Writes FATAL. TRACE. all Data Integration Service modules are enabled. WARNING. FATAL messages include nonrecoverable system failures that cause the Data Integration Service to shut down or become unavailable. DEBUG messages are user request logs. INFO. WARNING.Fatal. ERROR messages include connection failures.

the Data Integration Service accepts requests from IP addresses that match the allowed address pattern. This is required if the proxy server requires authentication. If you configure this property. If you do not configure this Data Integration Service Properties 191 . Default is 8080. Runs workflows. Before you disable a module. HTTP Proxy Server Properties The following table describes the HTTP proxy server properties: Property HTTP Proxy Server Host HTTP Proxy Server Port Description Name of the HTTP proxy server. The following table describes the Data Integration Service modules: Module Web Service Module Human Task Service Module Mapping Service Module Profiling Service Module REST Web Service Module SQL Service Module Workflow Service Module Description Runs web service operation mappings. This is required if the proxy server requires authentication. HTTP Proxy Server Password HTTP Proxy Server Domain HTTP Client Filter Properties The following table describes the HTTP client filter properties: Property Allowed IP Addresses Description List of constants or Java regular expression patterns compared to the IP address of the requesting machine. Runs mappings and previews. HTTP Proxy Server User Authenticated user name for the HTTP proxy server. Domain for authentication. You can save memory by limiting the Data Integration Service functionality. Runs profiles and generate scorecards. This module is reserved for future use. Runs SQL queries from a database client to an SQL data service.You might want to disable a module if you are testing and you have limited resources on the computer. Password for the authenticated user. you must disable the Data Integration Service. Port number of the HTTP proxy server. Use a space to separate multiple constants or expressions. The Service Manager encrypts the password. Runs a Human task in a workflow.

The host names are case sensitive. When you do not run each job as an operating system process. the Data Integration Service uses the Allowed Host Names property to determine which clients can send requests. Allowed Host Names List of constants or Java regular expression patterns compared to the host name of the requesting machine. Default is false. If you do not configure this property. Denied IP Addresses List of constants or Java regular expression patterns compared to the IP address of the requesting machine. the Data Integration Service uses the Allowed IP Addresses property to determine which clients can send requests. without affecting other jobs running on the Data Integration Service. all jobs run under one operating system process. Use a space to separate multiple constants or expressions. Denied Host Names List of constants or Java regular expression patterns compared to the host name of the requesting machine. such as preview. Result Set Cache Properties 192 Chapter 14: Data Integration Service . the Data Integration Service accepts requests from host names that match the allowed host name pattern. the Data Integration Service process. When enabled. If you configure this property.Property Description property. Use this feature for batch jobs and long jobs. the Data Integration Service uses the Denied IP Addresses property to determine which clients can send requests. Execution Options The following table describes the execution option for the Data Integration Service: Property Launch Jobs as Separate Processes Description Runs each Data Integration Service job as a separate operating system process. scorecard. the Data Integration Service accepts requests from IP addresses that do not match the denied IP address pattern. profile. If you configure this property. If you configure this property. The host names are case sensitive. Enable to increase the stability of the Data Integration Service and to isolate batch jobs. the Data Integration Service accepts requests from host names that do not match the denied host name pattern. Use a space to separate multiple constants or expressions. you can manage each job separately. and mapping jobs. If you do not configure this property. the Data Integration Service uses the Denied Host Names property to determine which clients can send requests. Use a space to separate multiple constants or expressions. If you do not configure this property.

Number of minimum and maximum values to display for a profile.The following table describes the result set cache properties: Property File Name Prefix Description The prefix for the names of all result set cache files stored on disk. Maximum number of threads to run profiling. Default is 10. Default is 5. Select the connection object name. Profiling Warehouse Database Properties The following table describes the profiling warehouse database properties: Property Profiling Warehouse Database Maximum Ranks Maximum Patterns Maximum Profile Execution Pool Size Description The connection to the profiling warehouse. Default is 10. Default is RSCACHE. Mapping Service Properties The following table describes Mapping Service Module properties of a Data Integration Service: Property Maximum Notification Thread Pool Size Description The maximum number of concurrent job completion notifications that the Mapping Service Module sends to external clients after the Data Integration Service completes jobs. You select a database that is configured on the Connections view. Data Integration Service Properties 193 . You use the Workflow Service Properties option to identify the Data Integration Service that runs the Human task. Valid values are true or false. This can be a different service to the service that runs the parent workflow for the Human task. Default is true. Maximum number of patterns to display for a profile. Indicates whether result set cache files are encrypted using 128-bit AES encryption. The Mapping Service Module is a component in the Data Integration Service that manages requests sent to run mappings. Default is 5. Enable Encryption Human Task Service Properties The following table describes the Human Task Service properties for the Data Integration Service: Property Connection Description The connection name of the database that stores configuration data for Human tasks that the Data Integration Service runs.

Default is 40. Amount of memory to allow each column for column profiling. Profile Job Queue Size Maximum Concurrent Columns Maximum Concurrent Profile Threads Maximum Column Heap Size Reserved Profile Threads SQL Properties The following table describes the SQL properties: Property DTM Keep Alive Time Description Number of milliseconds that the DTM process stays open after it completes the last request. Otherwise. Default is 1.000. Default is 16. the DTM process terminates. 194 Chapter 14: Data Integration Service . Identical SQL queries can reuse the open process. Maximum number of digits for a numeric value. Use the keepalive time to increase performance when the time required to process the SQL query is small compared to the initialization time for the DTM process. Default is 255.Property Maximum DB Connections Profile Results Export Path Description Maximum number of database connections for each profiling job. Maximum number of profiling jobs that can wait to run. 0 means that the Data Integration Service does not keep the DTM process in memory. the Profiling Service plug-in determines the best number based on the set of running jobs and other environment factors. Advanced Profiling Properties The following table describes the advanced profiling properties: Property Pattern Threshold Percentage Maximum # Value Frequency Pairs Maximum String Length Maximum Numeric Precision Maximum Concurrent Profile Jobs Description Maximum number of values required to derive a pattern. If the query fails. The maximum number of concurrent execution pool threads that can profile flat files. Number of threads of the Maximum Execution Pool Size that are for priority requests. Default is 0. Maximum number of columns that you can combine for profiling flat files in a single execution pool thread. Default is 64 megabytes. Maximum length of a string that the Profiling Service can process. Must be greater than or equal to 0. Maximum number of value-frequency pairs to store in the profiling warehouse. Default is 5. If the Data Integration Service and Analyst Service run on different nodes. The maximum number of concurrent profile threads used for profiling flat files. Default is 5. Default is 1. Location where the Data Integration Service exports profile results file. If left blank. both services must be able to access this location. Default is 38. Default is 5. the export fails.

For example. If the request fails. Default is false. 0 means that the Data Integration Service does not keep the DTM process in memory. the value for the deployed SQL data service overrides the value you set for the Data Integration Service. If you set this property for a deployed web service. Use the keepalive time to increase performance when the time required to process the request is small compared to the initialization time for the DTM process. the value for the deployed web service overrides the value you set for the Data Integration Service. Default is 5000. Default is false.Property Description You can also set this property for each SQL data service that is deployed to the Data Integration Service. Prevents the Data Integration Service from generating log files when the SQL data service request completes successfully and the tracing level is set to INFO or higher. Skip Log Files Prevents the Data Integration Service from generating log files when the web service request completes successfully and the tracing level is set to INFO or higher. Web service requests that are issued against the same operation can reuse the open process. Workflow Service Properties The following table describes the Workflow Service properties for the Data Integration Service: Property Human Task Data Integration Service Description The name of the Data Integration Service that runs a Human task. This property can specify the current Data Integration Service or another Data Integration Service on the domain. Table Storage Connection Skip Log Files Relational database connection that stores temporary tables for SQL data services. Web Service Properties The following table describes the web service properties: Property DTM Keep Alive Time Description Number of milliseconds that the DTM process stays open after it completes the last request. If you set this property for a deployed SQL data service. no connection is selected. you do not need to specify the logical URL. Must be greater than or equal to 0. the DTM process terminates. Logical URL Prefix for the WSDL URL if you use an external HTTP load balancer. If you run the Data Integration Service on a single node. By default. Custom Properties You can edit custom properties for a Data Integration Service. You can also set this property for each web service that is deployed to the Data Integration Service. http://loadbalancer:8080 The Data Integration Service requires an external HTTP load balancer to run a web service on a grid. Data Integration Service Properties 195 .

You can also set properties for the Address Manager. Use custom properties only at the request of Informatica Global Customer Support. The properties also specify the keystore and truststore file to use when you enable the Data Integration Service for TLS. and environment variables. When you enable TLS for the Data Integration Service and do not enable TLS for the web service. You can edit service process properties such as the HTTP port. The following table describes the Data Integration Service Security properties: Property HTTP Port HTTPS Port Description Unique HTTP port number for the Data Integration Service. Maximum Backlog Requests 196 Chapter 14: Data Integration Service . Use a different port number than the HTTP port number. the web service can use an HTTP URL or an HTTPS URL. logs directory. Data Integration Service Process Properties View the Data Integration Service process nodes on the Processes tab. Maximum number of HTTP or HTTPS connections that can wait in a queue for this Data Integration Service process. You can enable the TLS protocol for the Data Integration Service and for each web service. custom properties. Enter the property name and an initial value.The following table describes the custom properties: Property Custom Property Name Description Configure a custom property that is unique to your environment or that you need to apply in special cases. HTTP Client Filter Properties The HTTP configuration properties for a Data Integration Service process specify the maximum number of HTTP or HTTPS connections that can be made to the process. HTTPS port number for the Data Integration Service when you enable the TLS protocol. The following table describes the HTTP configuration properties for a Data Integration Service process: Property Maximum Concurrent Requests Description Maximum number of HTTP or HTTPS connections that can be made to this Data Integration Service process. Data Integration Service Security Properties When you enable the Transport Layer Security (TLS) protocol for the Data Integration Service. When you enable TLS for the Data Integration Service and enable TLS for the web service. Default is 200. web service requests to the Data Integration Service can use an HTTP or an HTTPS URL. Default is 100. the web service uses an HTTPS URL. If you enable TLS for a web service without enabling TLS for the Data Integration Service. the web service will not start.

If you run the Data Integration Service on a grid. Default is 0. Maximum Per Cache Memory Size Maximum number of bytes allocated for a single result set cache instance in memory. Absolute path to the directory that stores result set cache files. Maximum number of bytes allocated for the total result set cache storage in memory. Default is 0. Storage Directory Maximum Total Memory Size Maximum Number of Caches Data Integration Service Process Properties 197 . the keystore file on each node in the grid must contain the same keys. You can use the selfsigned certificate or use a certificate signed by a certificate authority.Property Keystore File Description Path and file name of the keystore file that contains the keys and certificates required if you enable TLS and use HTTPS connections for the Data Integration Service. If the Data Integration Service runs on a grid and you use a shared storage directory among all Data Integration Service processes. Default is 0. Keystore Password Truststore File Password for the keystore file. Secure Sockets Layer protocol to use. the truststore file on each node in the grid must contain the same keys. Default is TLS. If you run the Data Integration Service on a grid. Truststore Password SSL Protocol Password for the truststore file. each service process will maintain its own result set cache. Result Set Cache Properties The following table describes the result set cache properties: Property Maximum Total Disk Size Description Maximum number of bytes allowed for the total result set cache file storage. Maximum number of result set cache instances allowed for this Data Integration Service process. Default is 0. keytool is a utility that generates and stores private or public key pairs and associated certificates in a keystore file. Path and file name of the truststore file that contains authentication certificates trusted by the Data Integration Service. You can create a keystore file with a keytool.

Advanced Properties The following table describes the Advanced properties: Property Maximum Heap Size Description Amount of RAM allocated to the Java Virtual Machine (JVM) that runs the Data Integration Service. Default is 10. Do not use a space after the semicolon. SQL queries. set this threshold to 0. Use a semicolon to separate the paths.g for gigabytes. mappings. Default is <InformaticaInstallationDir>\tomcat\bin\disLogs. Temporary Directories Location of temporary directories for Data Integration Service process on the node. and web service requests. JVM Command Line Options Java Virtual Machine (JVM) command line options to run Java-based programs.m for megabytes. that the Data Integration Service can allocate for running requests. and Java SDK maximum memory properties. the Data Integration Service uses it to calculate the maximum total memory allowed for running all requests concurrently. in bytes. If you do not want to limit the amount of memory the Data Integration Service can allocate. Maximum Memory Size The maximum amount of memory. Java SDK minimum memory. . You cannot use the following characters in the directory path: * ? < > " | . you must set the Java SDK classpath. . Add a second path to this value to provide a dedicated directory for temporary files created in profile operations. . Default is 512 megabytes. When you configure the JVM options. The Data Integration Service calculates the maximum total memory as follows: 198 Chapter 14: Data Integration Service .b for bytes. Requests include data previews. Execution Options The following table describes the execution options for the Data Integration Service process: Property Maximum Execution Pool Size Description The maximum number of requests that the Data Integration Service can run concurrently. Use this property to increase the performance. Default is <home directory>/disTemp. When you set this threshold to a value greater than 0. profiling jobs. Append one of the following letters to the value to specify the units: .k for kilobytes. Logging Options The following table describes the logging options for the Data Integration Service process: Property Logging Directory Description Directory for Data Integration Service node process logs.

The Data Integration Service uses this threshold even if you set Maximum Memory Size to 0 bytes. Source Directory Directory for source flat files used in a mapping.000. If you run the Data Integration Service on a grid. You cannot use the following characters in the directory path: * ? < > " | . Rejected Files Directory Directory for reject files. You can increase performance when the cache directory is a drive local to the Data Integration Service process. ensure that the target files are consistent among all target directories. You cannot use the following characters in the directory path: * ? < > " | . Default is <home directory>/source. ensure that the source files are consistent among all source directories.000.000. If you have a separate directory for each Data Integration Service process. Default is <Informatica Services Installation Directory>/tomcat/bin. you can use a shared home directory to create one directory for target files. set this threshold to a value that exceeds the Maximum Memory Size divided by the Maximum Execution Pool Size. Data Integration Service Process Properties 199 . Default is <home directory>/ target. Maximum Session Size The maximum amount of memory. Do not use a mapped or mounted drive for cache files. Default is 50. If you run the Data Integration Service on a grid. For optimal memory utilization.000. Reject files contain rows that were rejected when running a mapping. Note: If you run profiles or data quality mappings. you can use a shared home directory to create one directory for source files. You cannot use the following characters in the directory path: * ? < > " | . Default is <home directory>/ Cache. Home Directory Root directory accessible by the node. that the Data Integration Service can allocate for any request. in bytes. This is the root directory for other service process variables. set this threshold to 0. Cache Directory Directory for index and data cache files for transformations. Default is <home directory>/reject.Property Description Maximum Memory Size + Maximum Heap Size + memory required for loading program components Default is 512. If you have a separate directory for each Data Integration Service process. Target Directory Default directory for target flat files used in a mapping. You cannot use the following characters in the directory path: * ? < > " | . You cannot use the following characters in the directory path: * ? < > " | .

The following table describes the custom properties: Property Custom Property Name Description Configure a custom property that is unique to your environment or that you need to apply in special cases. Environment Variables You can configure environment variables for the Data Integration Service process.SQL Properties The following table describes the SQL properties: Property Maximum # of Concurrent Connections Description Limits the number of database connections that the Data Integration Service can make for SQL data services. 1. In the domain navigator of the Administrator tool. Custom Properties You can edit custom properties for a Data Integration Service. you can configure an object to run on the Data Integration Service assigned to the grid. Use custom properties only at the request of Informatica Global Customer Support. 2. After you assign the Data Integration Service to run on a grid. Create a grid and assign nodes to the grid. Creating a Grid To create a grid. To assign the Data Integration Service to run on a grid. create the grid object and assign nodes to the grid. Configuration for the Data Integration Service Grid You can assign the Data Integration Service to run on a grid. Default is 100. 200 Chapter 14: Data Integration Service . Assign the Data Integration Service to a grid. select the domain. Click New > Grid. The following table describes the environment variables: Property Environment Variable Description Enter a name and a value for the environment variable. You can assign a node to more than one grid. complete the following tasks: 1. Enter the property name and an initial value. 2.

It cannot exceed 128 characters or begin with @. Select the Properties tab. To assign a Data Integration Service to a grid after you create the Data Integration Service. such as: DomainName/ProductionGrids Nodes Path Assigning a Data Integration Service to a Grid You can assign the Data Integration Service to a grid while you create the Data Integration Service or after you create it.. 3. complete the following tasks: 1. In the Administrator tool. the node appears in the grid. When you change the nodes in a grid. 2. It also cannot contain spaces or the following special characters: `~%^*+={}\. All nodes in the grid appear as service processes for the Integration Service. Troubleshooting the Grid I changed the nodes assigned to the grid.:'"/?. if you add a node. 3. the Service Manager performs the following transactions in the domain configuration database: 1. Configure the following options: Option Assign Grid Description Select Grid. 4. Select the grid to assign to the Data Integration Service.The Create Grid window appears. 2. Select nodes to assign to the grid. Edit the following properties: Property Name Description Name of the grid. Location in the Navigator.<>|!()][ Description Description of the grid. Configuration for the Data Integration Service Grid 201 . Updates the Integration Services to which the grid is assigned. Click OK. The name is not case sensitive and must be unique within the domain. 5. but the Integration Service to which the grid is assigned does not show the latest Integration Service processes. select the Data Integration Service. click Edit. For example. The description cannot exceed 765 characters. Updates the grid based on the node changes. In the General Properties section.

By default. 4. The profiling warehouse stores profiling data and metadata. the Data Integration Service can pass credentials to connections. To delete profiling warehouse content. The Data Integration Service can validate user credentials that are provided as a user name token in the SOAP request. 2. You can specify the profiling warehouse when you create the Data Integration Service or when you edit the Data Integration Service properties. transport layer security.If the Service Manager cannot update an Integration Service and the latest service processes do not appear for the Integration Service. Web Service Security Management An HTTP client filter. You can configure the following security options for a web service: HTTP Client Filter If you want the Data Integration Service to accept requests based on the host name or IP address of the web service client. On the Domain tab. If that does not work. you can use the existing content or delete and create new content. 3. In the Navigator. 1. Message Layer Security If you want the Data Integration Service to authenticate user credentials in SOAP requests. use the Administrator tool to configure an HTTP client filter. the Data Integration Service rejects the request and sends a system-defined fault to the web service client. You may choose to delete the content of a profiling warehouse to delete corrupted data or to increase disk or database space. you must associate the Data Integration Service with a profiling warehouse. the Data Integration Service rejects the request and sends a system-defined fault to the web service client. click the Actions menu on the Domain tab and select Profiling Warehouse Database Contents > Delete. 202 Chapter 14: Data Integration Service . You can create or delete content for a profiling warehouse at any time. a web service client running on any machine can send requests. If you specify an existing profiling warehouse. If a user does not have permission to execute the web service operation. click the Actions menu on the Domain tab and select Profiling Warehouse Database Contents > Create. reassign the grid to the Integration Service. and message layer security can provide secure data transfer and authorized data access for a web service. you must create the profiling content. use the Administrator tool to enable WS-Security and configure web service permissions. Content Management for the Profiling Warehouse To create and run profiles and scorecards. If the user name token is not valid. To create profiling warehouse content. select the Services and Nodes view. When you configure message layer security. select a Data Integration Service that has an associated profiling warehouse. Creating and Deleting Profiling Warehouse Content The Data Integration Service must be running when you create or delete profiling warehouse content. If you specify a new profiling warehouse database. restart the Integration Service.

use the Administrator tool to enable transport layer security (TLS) for a web service. ¨ Abort. Enabling. Enabling. To recycle the service. the Data Integration Service can pass credentials from the user name token in the SOAP request to the connection. and Recycling the Data Integration Service 203 . An HTTPS URL uses SSL to provide a secure connection for data transfer between a web service and a web service client. Disabling. disable. select the service in the Domain Navigator and click Enable the Service. Note: You cannot use pass-through security when the user name token includes a hashed or digested password. Allows the jobs to run to completion before disabling the service. You can choose one of the following options: ¨ Complete. To enable the service. it also restores the state of each application associated with the Data Integration Service. To configure the Data Integration Service to pass credentials to a connection. Tries to stop all jobs before aborting them and disabling the service. you must choose the mode to disable it in. Enable Play Animations in Web Pages in the Internet Options Advanced tab. Disabling. select the service in the Domain Navigator and click Disable the Service. or recycle the Data Integration Service from the Administrator tool. Pass-Through Security If an operation mapping requires connection credentials. the Data Integration Service restarts the service. the progress bar does not animate unless you enable an advanced option in the browser. You might disable a Data Integration Service if you need to perform maintenance or you need to temporarily restrict users from using the service. Note: When you enable or disable a service with Microsoft Internet Explorer. you shut down all Data Integration Service processes that run on the grid. You must recycle the Data Integration Service whenever you change a property for a Data Integration Service process. and Recycling the Data Integration Service You can enable. If you disable the Data Integration Service and the Data Integration Service runs on a grid. The Model Repository Service must be running before you enable the Data Integration Service.Transport Layer Security (TLS) If you want the web service and web service client to communicate using an HTTPS URL. The Data Integration Service that the web service runs on must also use TLS. When you recycle the service. select the service in the Domain Navigator and click Recycle. To disable the service. When the Administrator tool restarts the Data Integration Service. You might recycle a service if you modified a property. use the Administrator tool to configure the Data Integration Service to use pass-through security for the connection and enable WS-Security for the web service. When you disable a Data Integration Service.

the Data Integration Service purges the result set cache for objects in the application. If you want the Data Integration Service to cache the results by user. the Data Integration Service returns the cached results. When you configure result set caching. Configure the result set cache properties in the Data Integration Service process properties.Result Set Caching Result set caching enables the Data Integration Service to use cached results for SQL data service queries and web service requests. 2. The Data Integration Service caches the results for the expiration period that you configure. the Data Integration Service purges the result set cache for objects in applications that run on the Data Integration Service. the Data Integration Service caches the results of the DTM process associated with each SQL data service query and web service request. Do not rename or move the cache files. ¨ When you restart an application or run the infacmd dis purgeResultSetCache command. it stores the data in cache files. ¨ When you restart a Data Integration Service. 204 Chapter 14: Data Integration Service . Configure the cache expiration period in the web service operation properties. the Data Integration Service purges the cache. 3. Users that run identical queries in a short period of time may want to use result set caching to decrease the runtime of identical queries. the Data Integration Service purges the result set cache associated with that user. The Result Set Cache Manager creates in-memory caches to temporarily store the results of the DTM process. If the Result Set Cache Manager requires more space than allocated. The Data Integration Service purges result set caches in the following situations: ¨ When the result set cache expires. Configure the cache expiration period in the SQL data service properties. When an external client makes the same query or request before the cache expires. The Result Set Cache Manager identifies the cache files by file name and location. enable WS-Security in the web service properties. Complete the following steps to configure result set caching for SQL data services and web service operations: 1. ¨ When you change the permissions for a user.

215 ¨ Workflows. you can deploy an application archive file to a Data Integration Service.CHAPTER 15 Data Integration Service Applications This chapter includes the following topics: ¨ Data Integration Service Applications Overview. mappings. You can configure the default deployment mode for a Data Integration Service. To run the application. The Data Integration Service stores the application in the Model repository associated with the Data Integration Service. The connections that are defined in the application must be valid in the domain that you deploy the application to. An application is disabled. 212 ¨ Web Services. A developer can deploy an application to an application archive file or deploy the application directly to the Data Integration Service. When you deploy an application archive file to a Data Integration Service. web services. 205 ¨ Applications. 205 . mapping. the developer must deploy it. Applications View To manage deployed applications. SQL data services. You can enable the application to run and start the application. the Deployment Manager validates the logical data objects. 210 ¨ Mappings. 206 ¨ Logical Data Objects. The deployment fails if errors occur. or workflow and add it to an application in the Developer tool. 210 ¨ SQL Data Services. or running after deployment. web service. The default deployment mode determines the state of each application after deployment. SQL data service. 217 Data Integration Service Applications Overview A developer can create a logical data object. and workflows in the application. As an administrator. stopped. select a Data Integration Service in the Navigator and then click the Applications view.

the bottom panel displays readonly general properties and configurable properties for the selected object. The following table describes the read-only general properties for applications: Property Name Description Type Location Last Modification Date Deployment Date Description Name of the application. ¨ Disabled. ¨ Failed. ¨ Stopped. The administrator started the application. Refresh the Applications view to see the latest applications and their states. An application can have one of the following states: ¨ Running. Valid value is application. start. Expand the application name in the top panel to view the objects in the application. Application Properties Application properties include read-only general properties and a property to configure whether the application starts when the Data Integration Service starts. Applications The Applications view displays the applications that have been deployed to a Data Integration Service. and a web service in the application. Short description of the application. You can view the objects in the application and the properties. an SQL data service. Type of the object. The location of the application. 206 Chapter 15: Data Integration Service Applications . rename. The application is running.The Applications view displays the applications that have been deployed to a Data Integration Service. This includes the domain and Data Integration Service name. and restore an application. You can deploy. You can also back up and restore an application. enable. The application is enabled to run but it is not running. The properties change based on the type of object you select. The Applications view shows the applications in alphabetic order. You can start and stop an application. The application is disabled from running. the application will not start. Application State The Applications view shows the state for each application deployed to the Data Integration Service. The Applications view does not show empty folders. You can view the objects in the application and the properties. Date that the application was deployed. back up. Date that the application was last modified. If you recycle the Data Integration Service. but it failed to start. When you select an application or object in the top panel of the Applications view.

Path in the project that contains the application. select the the box at the top of the list. the application starts by default when you start or recycle the Data Integration Service. 1. 9. Click OK to start the deployment. 8. You can add up to 10 files. The following table describes the configurable application property: Property Startup Type Description Determines whether an application starts when the Data Integration Service starts. Click OK to finish the selection. The Add Files dialog box appears. Select a Data Integration Service. The destination Data Integration Service appears as selected in the Data Integration Services panel. 3. ID that identifies the application in the Model repository. To select additional Data Integration Services. Click Browse to search for an application file. Applications 207 . 6. Domain in which the application was created. User who deployed the application. Click Add More Files if you want to deploy multiple application files. 5. Choose Disabled to prevent the application from starting. select them in the Data Integration Services panel. If no errors are reported. Deploying an Application Deploy an object to an application archive file if you want to check the application into version control or if your organization requires that administrators deploy objects to Data Integration Services. In Domain Actions. click Deploy Application from Files. You cannot manually start an application if it is disabled. To choose all Data Integration Services. The Deploy Application dialog box appears. Date that the application was created. Click Upload Files. Click the Domain tab. 2. 4. The application file names appear in the Uploaded Applications Archive Files panel. and then click the Applications view. 7.Property Created By Unique Identifier Creation Project Path Creation Date Last Modified By Creation Domain Deployed By Description User who created the application. When you enable the application. User who modified the application last. the deployment succeeds and the application starts.

You can also deploy an application file using the infacmd dis deployApplication program. In the Application view. select Enabled and click OK. Click Actions > Rename Application. select the application that you want to enable. The Edit Application Properties dialog box appears. Select the Data Integration Service in the Navigator. 1. You must enable each SQL data service or web service that you want to run. In Application Properties area. 208 Chapter 15: Data Integration Service Applications . 11. You can configure a default deployment mode for a Data Integration Service. 4. you can enable it manually. ¨ Update the existing application with the new application. In the Applications view. When you enable a Data Integration Service. Select the Data Integration Service in the Navigator. click Edit. An application might be enabled or disabled. the SQL data services. Enabling an Application An application must be enabled to run before you can start it. If the application is enabled after deployment. and workflows are also enabled. An application must be running before you can start or access an object in the application. Starting an Application You can start an application from the Administrator tool. After you select an option. the enabled applications start automatically. Select the Data Integration Service in the Navigator. ¨ Rename the new application. select the application that you want to rename. You can rename an application when the application is not running. Enter the new application name if you select this option. Click Close. In the Applications view. You can start the application from the Applications Actions menu if the application is enabled to run. If an application is disabled.10. select the application that you want to start. When you deploy an application to a Data Integration Service. You cannot update or replace an existing application that is running. 1. 2. 2. 3. If a name conflict occurs. choose one of the following options to resolve the conflict: ¨ Keep the existing application and discard the new application. The application is enabled to run. 1. In the Startup Type field. If you replace or update the existing application and the existing application is running. Renaming an Application Rename an application to change the name. web services. ¨ Replace the existing application with the new application. click OK. select the Force Stop the Existing Application if it is Running option to stop the existing application. 4. Enter the name and click OK. 2. the property determines the application state after deployment. 3.

Click Actions > Backup Application. 5. 7. Choose a different name for the application you are restoring. The backup file contains all the property settings for the application. Browse for and select the XML file. 6. Select the application in the Content panel. The application must be an XML backup file that you create with the Backup option. 3. Click Actions > Start Application. The Administrator tool backs up the application to an XML file in the location you choose. select the application to back up. Select the Data Integration Service in the Navigator. Click the Applications view. ¨ Rename the new application. 3. enter an XML file name and choose the location to back up the application. 3.3. The application starts if the default deployment option is set to Enable and Start for the Data Integration Service. You can restore the application to another Data Integration Service. Click Open to view the XML file in a browser. 1. The Administrator tool does not restore the file. Applications 209 . In the Domain Navigator. ¨ Replace the existing application with the new application. The Administrator tool checks for a duplicate application. Backing Up an Application You can back up an application to an XML file. Click the Applications view. 1. remove applications that were recently undeployed. 4. 4. Restoring an Application You can restore an application from an XML backup file. You must stop the application before you back it up. Click OK to restore the application. and update the state of each application. The Administrator tool prompts you for the file to restore. 2. Click OK to start the restore. 2. Click Save to save the XML file. choose one of the following options: ¨ Keep the existing application and discard the new application. If a conflict occurs. Refreshing the Applications View Refresh the Applications view to view newly deployed and restored applications. 1. The Administrator tool restores the backup application to the Data Integration Service. The Administrator tool prompts you to open the XML file or save the XML file. select a Data Integration Service that you want to restore the application to. 5. 2. In the Applications view. Click Actions > Restore Application from File. If you click Save.

The name of the table that the Data Integration Service uses to cache the logical data object. The following table describes the read-only general properties for logical data objects: Property Name Description Type Location Description Name of the logical data object. Valid value is logical data object. Type of the object.4. The Application view refreshes. Mapping properties include read-only general properties and properties to configure the settings the Data Integration Services uses when it runs the mappings in the application. The Data Integration Service caches the logical data object in the database that you select through the cache connection for logical data objects and virtual tables. the Data Integration Service ignores the cache refresh period. The following table describes the configurable logical data object properties: Property Enable Caching Cache Refresh Period Cache Table Name Description Cache the logical data object. If you specify a cache table name. Mappings The Applications view displays mappings included in applications that have been deployed to the Data Integration Service. Logical Data Objects The Applications view displays logical data objects included in applications that have been deployed to the Data Integration Service. Number of minutes between cache refreshes. Click Refresh Application View in the application Actions menu. 210 Chapter 15: Data Integration Service Applications . The location of the logical data object. Short description of the logical data object. Logical data object properties include read-only general properties and properties to configure caching for logical data objects. This includes the domain and Data Integration Service name.

and you require accurate values. and notification of rejected data. The location of the mapping. . and predicate optimization methods to the mapping. . . This includes the domain and Data Integration Service name. Tracing level Overrides the tracing level for each transformation in the mapping. Optimization level Controls the optimization methods that the Data Integration Service applies to a mapping as follows: .Normal. and semi-join optimization methods to the mapping. The Data Integration Service does not optimize the mapping. The following table describes the configurable mapping properties: Property Date format Description Date/time format the Data Integration Services uses when the mapping converts strings to dates. but not at the level of individual rows. . Default is enabled. values with precision of more than 15 digits. The tracing level determines the amount of information the Data Integration Service sends to the mapping log files. the Data Integration Service logs each row that passes into the mapping. for example. The Data Integration Service applies the early projection optimization method to the mapping. The Data Integration Service applies the early projection. The Data Integration Service also notes where it truncates string data to fit the precision of a column and provides detailed transformation statistics.Verbose Data. The Data Integration Service logs initialization and status information.Normal. . Default is MM/DD/YYYY HH24:MI:SS. Type of the object. Choose one of the following tracing levels: . Enable high precision Runs the mapping with high precision. early selection. In addition to verbose initialization tracing. Enable high precision if the mapping produces large numeric values. . errors encountered. The Data Integration Service applies the early projection.None. error messages. the Data Integration Service logs additional initialization details.Verbose Initialization. names of index and data files used.Minimal. The Data Integration Service writes row data for all rows in a block when it processes a transformation.None. predicate optimization. Valid value is mapping. Default is None. Enabling high precision prevents precision loss in large numeric values. Mappings 211 . High precision data values have greater accuracy. The Data Integration Service logs initialization information. It summarizes mapping results. The Data Integration Service uses the tracing levels set in the mapping. In addition to normal tracing. and skipped rows due to transformation row errors. Short description of the mapping.Terse. . early selection.The following table describes the read-only general properties for mappings: Property Name Description Type Location Description Name of the mapping. and detailed transformation statistics.Full.

Default is Binary. Sort order Order in which the Data Integration Service sorts character data in the mapping. virtual columns. SQL Data Service Properties SQL data service properties include read-only general properties and properties to configure the settings the Data Integration Service uses when it runs the SQL data service. SQL Data Services The Applications view displays SQL data services included in applications that have been deployed to a Data Integration Service. You can enable and rename an SQL data service. Type of the selected object. and virtual stored procedures: Property Name Description Type Location Description Name of the selected object. Appears for all object types. JDBC connection string used to access the SQL data service. JDBC URL Column Type 212 Chapter 15: Data Integration Service Applications . virtual tables. When you expand an SQL data service in the top panel of the Applications view. you can access the following objects contained in an SQL data service: ¨ Virtual tables ¨ Virtual columns ¨ Virtual stored procedures The Applications view displays read-only general properties for SQL data services and the objects contained in the SQL data services. The following table describes the read-only general properties for SQL data services. Short description of the selected object. Appears for SQL data services. You can view objects in the SQL data service and configure properties that the Data Integration Service uses to run the SQL data service. Appears for all object types.Property Description Default is Normal. Appears for all object types. Appears for all object types. Properties that appear in the view depend on the object type. The SQL data service contains virtual tables that you can query. It also contains virtual stored procedures that you can run. Appears for virtual columns. This includes the domain and Data Integration Service name. Datatype of the virtual column. The location of the selected object.

Must be an integer. The following table describes the configurable virtual table properties: Property Enable Caching Cache Refresh Period Cache Table Name Description Cache the SQL data service virtual database.ALL Default is INFO. Identical SQL queries can reuse the open process. Sort order that the Data Integration Service uses for sorting and comparing data when running in Unicode mode. Maximum number of active connections to the SQL data service. 0 means that the Data Integration Service does not keep the DTM process in memory. Default is 3. If the query fails.600.INFO .600. A negative integer value means that the DTM Keep Alive Time for the Data Integration Service is used. If set to 0. Changes to the expiration period do not apply to existing caches.The following table describes the configurable SQL data service properties: Property Startup Type Description Determines whether the SQL data service is enabled to run when the application starts or when you start the SQL data service. You can choose the sort order based on your code page. Default is 3.OFF . The name of the table that the Data Integration Service uses to cache the virtual table. If set to -1. If you want all caches to use the same expiration period. Maximum number of milliseconds for an SQL request to wait for an SQL data service response.SEVERE . Number of milliseconds that the DTM process stays open after it completes the last request. Default is binary. Number of minutes between cache refreshes. it ignores the sort order value and uses a binary sort order. Enter ENABLED to allow the SQL data service to run. You must disable the SQL data service before configuring virtual table properties. Enter DISABLED to prevent the SQL data service from running. The Data Integration Service caches the virtual table in the database that you select through the cache SQL Data Services 213 .FINEST . the DTM process terminates. Trace Level Sort Order Maximum Active Connections Result Set Cache Expiration Period The number of milliseconds that the result set cache is available for use. When the Data Integration runs in ASCII mode. purge the result set cache after you change the expiration period. Default is -1. Connection Timeout Request Timeout Maximum number of milliseconds to wait for a connection to the SQL data service. result set caching is disabled.000.WARNING . Default is 0. Level of error written to the log files. DTM Keep Alive Time Virtual Table Properties Configure whether to cache virtual tables for an SQL data service and configure how often to refresh the cache.FINE .000. the cache never expires. Choose one of the following message levels: . Use the keepalive time to increase performance when the time required to process the SQL query is small compared to the initialization time for the DTM process.

. Enabling an SQL Data Service Before you can start an SQL data service. Returns a constant value for a restricted column in each row. purge the result set cache after you change the expiration period. Returns a null value for a restricted column in each row. Default is 0.Property Description connection for logical data objects and virtual tables. you must also enable each SQL data service in the application. 3.VALUE. When a deployed application is disabled by default. the SQL data services in the application are also enabled. When you enable the application manually. If you substitute the column value. .NULL. 2. click Edit. the cache never expires. In the Applications view. 1. If you want all caches to use the same expiration period. Insufficient Permission Value The constant that the Data Integration Service returns for a restricted column. The Edit Properties dialog box appears. you can choose to substitute the value with NULL or with a constant value. result set caching is disabled. Virtual Column Properties Configure the properties for the virtual columns included in an SQL data service. the SQL data services are also disabled. select the SQL data service that you want to enable. Virtual Stored Procedure Properties Configure the property for the virtual stored procedures included in an SQL data service. Changes to the expiration period do not apply to existing caches.ERROR. this property determines whether to substitute the restricted column value or to fail the query. The following table describes the configurable virtual column properties: Property Deny With Description When you use column level security. If set to 0. the Data Integration Service ignores the cache refresh period. Fails the query and returns an error when an SQL query selects a restricted column. 214 Chapter 15: Data Integration Service Applications . If set to -1. In SQL Data Service Properties area. Select one of the following options: . Select the Data Integration Service in the Navigator. If you specify a cache table name. the Data Integration Service must be running and the SQL data service must be enabled. The following table describes the configurable virtual stored procedure property: Property Result Set Cache Expiration Period Description The number of milliseconds that the result set cache is available for use. When a deployed application is enabled by default.

In the Application view. You can view the operations in the web service and configure properties that the Data Integration Service uses to run a web service. WSDL URL Web Services 215 . When you expand a web service in the top panel of the Applications view. Web Service Properties Web service properties include read-only general properties and properties to configure the settings that the Data Integration Service uses when it runs a web service. The following table describes the read-only general properties for web services and web service operations: Property Name Description Type Location Description Name of the selected object. You can rename an SQL data service when the SQL data service is not running. Select the Data Integration Service in the Navigator. Appears for all object types. Short description of the selected object. Properties that appear in the view depend on the object type. Type of the selected object. 2. Click Actions > Rename SQL Data Service. You can enable and rename a web service. select Enabled and click OK. This includes the domain and Data Integration Service name. Appears for all objects. Appears for all objects. Web Services The Applications view displays web services included in applications that have been deployed to a Data Integration Service.4. Renaming an SQL Data Service Rename an SQL data service to change the name of the SQL data service. WSDL URL used to connect to the web service. Appears for web services. The location of the selected object. The Applications view displays read-only general properties for web services and web service operations. Enter the name and click OK. you can access web service operations contained in the web service. 3. 4. Appears for all objects. select the SQL data service that you want to rename. In the Startup Type field. 1.

000. The web service request fails when the request message exceeds the SOAP input precision. Default is 3. WARNING and SEVERE messages to the web service run-time log.ALL. Trace Level Maximum Concurrent Requests Sort Order Enable Transport Layer Security Enable WSSecurity DTM Keep Alive Time Sort order that the Data Integration Service to sort and compare data when running in Unicode mode.The following table describes the configurable web service properties: Property Startup Type Description Determines whether the web service is enabled to run when the application starts or when you start the web service. the web service will not start. Default is -1. INFO. Choose one of the following message levels: . Indicates that the web service must use HTTPS. If the Data Integration Service is not configured to use HTTPS. Level of error messages written to the run-time web service log. WARNING and SEVERE messages to the web service run-time log. WARNING and SEVERE messages to the web service run-time log. The DTM process writes WARNING and SEVERE messages to the web service run-time log. WARNING and SEVERE messages to the web service run-time log. INFO. The DTM process writes INFO.000. The Data Integration Service truncates the response message when the response message exceeds the SOAP output precision.WARNING.000.FINE.600. INFO. Maximum number of characters that the Data Integration Service generates for the response message. . Request Timeout Maximum number of milliseconds that the Data Integration Service runs an operation mapping before the web service request times out. . The DTM process writes FINEST. The DTM process writes FINEST. Maximum number of characters that the Data Integration Service parses in the request message. Default is 200.FINEST. . Use the keepalive time to increase performance when the time required to process the request is small compared to the initialization time for the DTM process.OFF. 216 Chapter 15: Data Integration Service Applications . Web service requests that are issued against the same operation can reuse the open process.SEVERE. the DTM process terminates. Enables the Data Integration Service to validate the user credentials and verify that the user has permission to run each web service operation. The DTM process writes FINE. Must be an integer. SEVERE messages include errors that might cause the web service to stop running. A negative integer value means that the DTM Keep Alive Time for the Data Integration Service is used. WARNING messages include recoverable failures or warnings. SOAP Output Precision SOAP Input Precision Web Service Operation Properties Configure the settings that the Data Integration Service uses when it runs a web service operation. Default is 10. If the request fails. FINEST message are used for debugging. FINE. . Default is INFO. Default is 200. . 0 means that the Data Integration Service does not keep the DTM process in memory. The DTM process does not write messages to the web service run-time logs.INFO. FINE. . Maximum number of requests that a web service can process at one time. FINE messages include data processing errors for the web service request. Number of milliseconds that the DTM process stays open after it completes the last request. INFO messages include web service status messages.

Workflows The Applications view displays workflows included in applications that have been deployed to a Data Integration Service. Workflows 217 . select the web service that you want to rename. Enter the web service name and click OK. 3. the cache never expires. Renaming a Web Service Rename a web service to change the service name of a web service. In Web Service Properties section of the Properties view. In the Startup Type field. Workflow Properties Workflow properties include read-only general properties. Enabling a Web Service Enable a web service so that you can start the web service. 4. Select the Data Integration Service in the Navigator. result set caching is disabled. 1. 3. The Edit Properties dialog box appears. Default is 0. If set to 0. The Rename Web Service dialog box appears.The following tables describes the configurable web service operation property: Property Result Set Cache Expiration Period Description The number of milliseconds that the result set cache is available for use. click Edit. 2. Click Actions > Rename Web Service. If set to -1. If you want all caches to use the same expiration period. In the Application view. You can rename a web service when the web service is stopped. select the web service that you want to enable. Changes to the expiration period do not apply to existing caches. You can view workflow properties and enable a workflow. select Enabled and click OK. 4. purge the result set cache after you change the expiration period. Before you can start a web service. Select the Data Integration Service in the Navigator. 1. 2. In the Application view. the Data Integration Service must be running and the web service must be enabled.

the Data Integration Service must be running and the workflow must be enabled. Enabling a Workflow Before you can run instances of the workflow. select the workflow that you want to enable. When a deployed application is disabled by default. When you enable the application manually. 218 Chapter 15: Data Integration Service Applications . Enable a workflow to allow users to run instances of the workflow. In the Applications view. Select the Data Integration Service in the Navigator. each workflow in the application is also enabled. The location of the workflow. 2. the workflows in the application are also enabled. When you disable a workflow. When a deployed application is enabled by default. 1.The following table describes the read-only general properties for workflows: Property Name Description Type Location Description Name of the workflow. the Data Integration Service aborts any running instances of the workflow. the workflows are also disabled. This includes the domain and Data Integration Service name. Valid value is workflow. Short description of the workflow. Type of the object. 3. Disable a workflow to prevent users from running instances of the workflow. Click Actions > Enable Workflow.

219 . 219 ¨ Configuring a Metadata Manager Service. 224 ¨ Enabling and Disabling the Metadata Manager Service.CHAPTER 16 Metadata Manager Service This chapter includes the following topics: ¨ Metadata Manager Service Overview. 226 ¨ Configuring the Metadata Manager Service Properties. 231 Metadata Manager Service Overview The Metadata Manager Service is an application service that runs the Metadata Manager application in an Informatica domain. The Metadata Manager application manages access to metadata in the Metadata Manager repository. 226 ¨ Configuring the Associated PowerCenter Integration Service. 221 ¨ Creating and Deleting Repository Content. Create a Metadata Manager Service in the domain to access the Metadata Manager application. 220 ¨ Creating a Metadata Manager Service.

Set up a database for the Metadata Manager repository. ¨ Metadata Manager repository. The Metadata Manager application is a web-based application. You supply the database information when you create the Metadata Manager Service. Manages connections to the PowerCenter repository for Metadata Manager. and analyze metadata from application. You can use an existing PowerCenter Repository Service and PowerCenter Integration Service. business intelligence. 1. ¨ PowerCenter repository for Metadata Manager. and workflows. The Metadata Manager warehouse is a centralized metadata warehouse that stores the metadata from metadata sources. data modeling. If 220 Chapter 16: Metadata Manager Service . ¨ PowerCenter Integration Service. ¨ PowerCenter Repository Service. and relational metadata sources. Set up the Metadata Manager repository database. The application. Models define the metadata that Metadata Manager extracts from metadata sources. business intelligence. Use Metadata Manager to browse and analyze metadata from disparate source repositories. Configuring a Metadata Manager Service You can create and configure a Metadata Manager Service and the related components in the Administrator tool. Contains the Metadata Manager warehouse and models. targets. The metadata objects include sources. sessions. ¨ Metadata sources. data integration. data integration. You can load. or you can create them.The following figure shows the Metadata Manager components managed by the Metadata Manager Service on a node in an Informatica domain: The Metadata Manager Service manages the following components: ¨ Metadata Manager application. and database management sources that Metadata Manager extracts metadata from. browse. Create a PowerCenter Repository Service and PowerCenter Integration Service (Optional). data modeling. 2. Runs the workflows in the PowerCenter repository to read from metadata sources and load metadata into the Metadata Manager warehouse. Contains the metadata objects used by the PowerCenter Integration Service to load metadata into the Metadata Manager warehouse.

and click Next. Note: You can use a Metadata Manager Service and the associated Metadata Manager repository in one Informatica domain. After you create the Metadata Manager Service and Metadata Manager repository in one domain. Enter values for the Metadata Manager Service database properties. 3. Create repository contents. Configure the Metadata Manager Service. To run reports on the Metadata Manager repository. click the Domain tab. 4. Create users and assign them privileges for the Metadata Manager Service. ¨ PowerCenter Integration Service. 5. Use the Administrator tool to create the Metadata Manager Service. 6. Use the Metadata Manager Service Actions menu to create the contents for both repositories. Enter values for the Metadata Manager Service security properties. In the Administrator tool.want to create the application services to use with Metadata Manager. Start the PowerCenter Repository Service in exclusive mode. you can log in to Data Analyzer and run reports against the Metadata Manager repository. After you create the Reporting Service. 2. 5. Enable the associated PowerCenter Integration Service for the Metadata Manager Service. Configure the properties for the Metadata Manager Service. Enable the PowerCenter Integration Service. create the services in the following order: ¨ PowerCenter Repository Service. Create the PowerCenter Integration Service. Click Actions > New Metadata Manager Service. Create or assign users. 7. 9. and click Next. Create contents for the Metadata Manager repository and restore the PowerCenter repository. Create a PowerCenter Repository Service but do not create contents. you cannot create a second Metadata Manager Service to use the same Metadata Manager repository. After you create the Metadata Manager Service. The service will not start because the PowerCenter Repository Service does not have content. Enable the Metadata Manager Service in the Informatica domain. create a Reporting Service. Create the Metadata Manager Service. create the Metadata Manager repository contents and PowerCenter repository contents to enable the service. The New Metadata Manager Service dialog box appears. Creating a Metadata Manager Service Use the Administrator tool to create the Metadata Manager Service. You enable the PowerCenter Integration Service after you create and configure the Metadata Manager Service. Enter values for the Metadata Manager Service general properties. or assign existing users privileges for the Metadata Manager Service. 4. Create a Reporting Service (Optional). 3. and click Finish. 8. Creating a Metadata Manager Service 221 . Enable the Metadata Manager Service. 1. You also cannot back up and restore the repository to use with a different Metadata Manager Service in a different domain.

Metadata Manager Service Properties The following table describes the properties that you configure for the Metadata Manager Service: Property Name Description Name of the Metadata Manager Service. and the code page for any database management and PowerCenter resources that you load into the Metadata Manager warehouse must be the same.<>|!()][ Description Location The description cannot exceed 765 characters. Type of database for the Metadata Manager repository. Password for the Metadata Manager repository database user. Domain and folder where the service is created. Repository Password Security Domain Database Type Security domain that contains the user account you configured for the PowerCenter Repository Service. Use the repository user account you configured for the PowerCenter Repository Service. License object that allows use of the service. restart the Metadata Manager Service. Code Page Connect String Database User Database Password 222 Chapter 16: Metadata Manager Service . Native connect string to the Metadata Manager repository database. restart the Metadata Manager Service. restart the Metadata Manager Service. The Metadata Manager Service uses the connect string to create a connection object to the Metadata Manager repository in the PowerCenter repository. restart the Metadata Manager Service. Note: The Metadata Manager repository code page. Click Browse to choose a different folder. Must be in 7-bit ASCII. To apply changes. The name is not case sensitive and must be unique within the domain. To apply changes. Set up this account using the appropriate database client tools. To apply changes. restart the Metadata Manager Service.. To apply changes. PowerCenter Integration Service used by Metadata Manage to load metadata into the Metadata Manager warehouse. To apply changes.” Password for the PowerCenter repository user. the code page on the machine where the associated PowerCenter Integration Service runs.:'"/?. It also cannot contain spaces or the following special characters: `~%^*+={}\. You can move the Metadata Manager Service after you create it. It cannot exceed 128 characters or begin with @. Metadata Manager repository code page. The Metadata Manager Service and Metadata Manager application use the character set encoded in the repository code page when writing data to the Metadata Manager repository. User account for the Metadata Manager repository database. see “Privileges for the Associated PowerCenter Integration Service User. For a list of the required privileges for this user. License Node Associated Integration Service Repository User Name User account for the PowerCenter repository. Node in the Informatica domain that the Metadata Manager Service runs on.

For example. To improve repository performance on IBM DB2 EEE repositories.AuthenticationMethod=ntlm. Port Number Port number the Metadata Manager application runs on.LoadLibraryPath=[directory containing DDJDBCx64Auth04. When you specify the tablespace name. restart the Metadata Manager Service. To apply changes. Additional JDBC options. Default is 10250. Metadata Manager uses port 10254 for HTTP. Indicates whether the Database Name property contains an Oracle full service name or SID. Port number for the Metadata Manager repository database. specify a connect string for that connection.Property Tablespace Name Description Tablespace name for Metadata Manager repositories on IBM DB2.dll]. Enable Secured Socket Layer Keystore File Keystore file that contains the keys and certificates required if you use the SSL security protocol with the Metadata Manager application. configure the Windows service properties to log on using a trusted user account. Database Hostname Database Port SID/Service Name Database Name Additional JDBC Parameters Host name for the Metadata Manager repository database. verify that the port number one less than the HTTPS port is also available. To authenticate the user credentials using Windows authentication and establish a trusted connection to a Microsoft SQL Server repository. To start the Metadata Manager Service as a Windows service using a trusted connection.dll] When you use a trusted connection to connect to a Microsoft SQL Server database. jdbc:informatica:sqlserver://[host]:[port]. specify a tablespace name with one node. Indicates that you want to configure SSL security protocol for the Metadata Manager application. enter the following text: AuthenticationMethod=ntlm. Required if you select Enable Secured Socket Layer.DatabaseName=[DB name]. The Metadata Manager Service uses the connect string to create a connection object to the Metadata Manager repository database in the PowerCenter repository. if you configure 10255 for the HTTPS port number. If you configure HTTPS. Full service name or SID for Oracle databases. the Metadata Manager Service connects to the repository with the credentials of the user logged in to the machine on which the service is running. the Metadata Manager Service creates all repository tables in the same tablespace. Keystore Password Database Connect Strings When you create a database connection. Service name for IBM DB2 databases. You cannot use spaces in the tablespace name.LoadLibraryPath=[directory containing DDJDBCx64Auth04. you must verify that 10254 is also available. Note: The Metadata Manager Service does not support the alternateID option for DB2. Password for the keystore file. Database name for Microsoft SQL Server databases. Creating a Metadata Manager Service 223 . Required if you select Enable Secured Socket Layer.

No action. Specify a code page that is compatible with the default repository database code page. ¨ PowerCenter repository. add the CODEPAGEOVERRIDE parameter to the Additional JDBC Options property. The repository backup file includes the metadata objects used by Metadata Manager to load metadata into the Metadata Manager warehouse. and workflows. Override the code page if the Metadata Manager repository contains characters that the database code page does not support. For example. When you restore the repository. use the following parameter to override the default Shift-JIS code page with MS932: CODEPAGEOVERRIDE=MS932. The tasks you complete depend on whether the Metadata Manager repository contains contents or if the PowerCenter repository contains the PowerCenter objects for Metadata Manager. sessions. The following table describes the tasks you must complete for each repository: Repository Metadata Manager repository Metadata Manager repository PowerCenter repository Condition Does not have content. Restore a repository backup file packaged with PowerCenter to the PowerCenter repository database. Does not have content. targets. 224 Chapter 16: Metadata Manager Service .The following table lists the native connect string syntax for each supported database: Database IBM DB2 Microsoft SQL Server Oracle Connect String Syntax dbname servername@dbname dbname.world Overriding the Repository Database Code Page You can override the default database code page for the Metadata Manager repository database when you create or configure the Metadata Manager Service. To override the code page. the Service Manager creates a folder named Metadata Load in the PowerCenter repository. Restore the PowerCenter repository if the PowerCenter Repository Service runs in exclusive mode. Create the Metadata Manager warehouse tables and import models for metadata sources into the Metadata Manager repository.world (same as TNSNAMES entry) Example mydatabase sqlserver@mydatabase oracle. PowerCenter repository Has content. Action Create the Metadata Manager repository. The Metadata Load folder contains the metadata objects. No action if the PowerCenter repository has the objects required for Metadata Manager in the Metadata Load folder. Has content. Creating and Deleting Repository Content You can create and delete contents for the following repositories used by Metadata Manager: ¨ Metadata Manager repository. including sources.

The activity log displays the results of the restore repository operation. 4. 2. choose to restore the PowerCenter repository. 1. 4. In the Navigator. Click OK. you create the Metadata Manager warehouse tables and import models for metadata sources.Repository Condition Action The Service Manager imports the required objects from an XML file when you enable the service. 3. choose to restart the PowerCenter Repository Service in normal mode. Click OK. select the Metadata Manager Service for which the PowerCenter repository has no contents. In the Navigator. Deleting the Metadata Manager Repository Delete Metadata Manager repository content when you want to delete all metadata and repository database tables from the repository. Optionally. back up the repository before you delete it. 1. Creating the Metadata Manager Repository When you create the Metadata Manager repository. Enter the user name and password for the database account. Click Actions > Repository Contents > Delete. The activity log displays the results of the create contents operation. Click OK. Click Actions > Repository Contents > Create. If the repository contains information that you want to save. Click Actions > Restore PowerCenter Repository. 2. 2. Restoring the PowerCenter Repository Restore the repository backup file for the PowerCenter repository to create the objects used by Metadata Manager in the PowerCenter repository database. Optionally. 4. select the Metadata Manager Service for which the Metadata Manager repository has no content. Delete the repository content if the metadata is obsolete. You can restore the repository if the PowerCenter Repository Service runs in exclusive mode and the repository does not contain contents. Use the database client or the Metadata Manager repository backup utility to back up the database before you delete contents. In the Navigator. 3. Creating and Deleting Repository Content 225 . 1. The activity log displays the results of the delete contents operation. select the Metadata Manager Service for which you want to delete Metadata Manager repository content. 3.

and then click Edit in the General Properties section. and the node where the service runs. Include the HTTP security protocol and keystore file. When you disable the Metadata Manager Service. disable. Configuring the Metadata Manager Service Properties After you create a Metadata Manager Service. Metadata Manager maintains a connection pool for connections to the Metadata Manager repository. and recycle the Metadata Manager Service from the Actions menu. or recycle the Metadata Manager Service. the Metadata Manager Service is disabled and enabled. you also stop Metadata Manager. you can configure it. and Metadata Manager Browse and Load tab options. the Service Manager starts the Metadata Manager application on the node where the Metadata Manager Service runs. When you recycle the service. Include properties for the Java Virtual Manager (JVM) memory settings. ODBC connection mode. the license object for the service. ¨ Database properties. Include database properties for the Metadata Manager repository. To view or update properties: u Select the Metadata Manager Service in the Navigator. select the Metadata Manager Service in the Navigator. Include port numbers for the Metadata Manager application and the Metadata Manager Agent. Note: The PowerCenter Repository Service for Metadata Manager must be enabled and running before you can enable the Metadata Manager Service. select the Properties view. ¨ Metadata Manager Service properties. and maximum concurrent and queued requests to the Metadata Manager application. You can enable. Connection pool properties include the number of active available connections to the Metadata Manager repository database and the amount of time that Metadata Manager holds database connection requests in the connection pool. 226 Chapter 16: Metadata Manager Service . Use custom properties if Informatica Global Customer Support instructs you to do so.Enabling and Disabling the Metadata Manager Service Use the Administrator tool to enable. ¨ Custom properties. A Metadata Manager Service does not have custom properties when you initially create it. and the Metadata Manager file location. After you configure Metadata Manager Service properties. Disable a Metadata Manager Service to perform maintenance or to temporarily restrict users from accessing Metadata Manager. Include the name and description of the service. You might recycle a service if you modified a property. ¨ Configuration properties. ¨ Connection pool properties. ¨ Advanced properties. Use the Administrator tool to configure the following types of Metadata Manager Service properties: ¨ General properties. Configure repository properties that are unique to your environment or that apply in special cases. disable. you must disable and enable the Metadata Manager Service for the changes to take effect. General Properties To edit the general properties. the Administrator tool imports the metadata objects required by Metadata Manager into the PowerCenter repository. When you enable the Metadata Manager Service. If the PowerCenter repository does not contain the Metadata Load folder.

Copy the contents of the Metadata Manager file location directory on the original node to the location on the new node. select the Metadata Manager Service in the Navigator. Agent Port Metadata Manager File Location Configuring the Metadata Manager Service Properties 227 . and then click OK. Default is 10251. you must make sure 10254 is also available. Change the Keystore File location to a location that is accessible from the new node. select the Properties view. Files include the following file types: . Default is 10250. Log files generated by Metadata Manager when you load resources. make sure that the port number one less than the HTTPS port is also available. 2. Select another node for the Node property. . and then click OK. If you configure HTTPS. License object you assigned the Metadata Manager Service to when you created the service. 4. The following table describes the Metadata Manager Service properties: Property Port Number Description Port number that the Metadata Manager application runs on. Node in the Informatica domain that the Metadata Manager Service runs on. 7.Parameter files. For example. Index files created by Metadata Manager required to search the Metadata Manager warehouse. if you configure 10255 for the HTTPS port number. You cannot edit this property. Click Edit in the Metadata Manager Service Properties section. You cannot edit this property. 5. Location of the files used by the Metadata Manager application.Index files. The agent uses this port to communicate with metadata source repositories. Files generated by Metadata Manager and used by PowerCenter workflows. 3. Metadata Manager Service Properties To edit the Metadata Manager Service properties. and then click OK. Disable the Metadata Manager Service.The following table describes the general properties for a Metadata Manager Service: Property Name Description License Description Name of the Metadata Manager Service. Enable the Metadata Manager Service. Change the Metadata Manager File Location property to a location that is accessible from the new node. Description of the Metadata Manager Service. Click Edit in the General Properties section. . Node Assigning the Metadata Manager Service to a Different Node 1. To assign the Metadata Manager Service to a different node.Log files. 6. and then click Edit in the Metadata Manager Service Properties section. Port number for the Metadata Manager Agent. you must first disable the service. Metadata Manager uses port 10254 for HTTP. 8. If the Metadata Manager Service is running in HTTPS security mode. click Edit in the Configuration Properties section.

the location must be accessible to all nodes running a Metadata Manager Service and to all users of the Metadata Manager application. Database Properties To edit the Metadata Manager repository database properties. restart the Metadata Manager Service. The Metadata Manager Service and Metadata Manager use the character set encoded in the repository code page when writing data to the Metadata Manager repository. Native connect string to the Metadata Manager repository database. Note: If you set the ODBC Connection Mode property to True. The Metadata Manager Service uses the connection string to create a target connection to the Metadata Manager repository in the PowerCenter repository. restart the Metadata Manager Service. restart the Metadata Manager Service. To apply changes. To apply changes. You cannot use spaces in the tablespace name. and then click Edit in the Database Properties section. the Metadata Manager Service creates all repository tables in the same tablespace. Tablespace name for the Metadata Manager repository on IBM DB2. restart the Metadata Manager Service. To improve repository performance on IBM DB2 EEE repositories. restart the Metadata Manager Service. Code Page Connect String Database Password Tablespace Name 228 Chapter 16: Metadata Manager Service . ¨ If you configure a shared file location. select the Metadata Manager Service in the Navigator. restart the Metadata Manager Service. Must be in 7-bit ASCII. Metadata Manager repository code page. restart the Metadata Manager Service. and the code page for any database management and PowerCenter resources you load into the Metadata Manager warehouse must be the same. The following table describes the database properties for a Metadata Manager repository database: Property Database Type Description Type of database for the Metadata Manager repository. select the Properties view. Set up this account using the appropriate database client tools. the code page on the machine where the associated PowerCenter Integration Service runs. copy the contents of the directory to the new location. To apply changes. Database Hostname Host name for the Metadata Manager repository database. use the ODBC connection name for the connect string.Property Description By default. Metadata Manager stores the files in the following directory: <Informatica installation directory>\server\tomcat\mm_files###BOT_TEXT###lt;service name> Configuring the Metadata Manager File Location Use the following rules and guidelines when you configure the Metadata Manager file location: ¨ If you change this location. To apply changes. Database User User account for the Metadata Manager repository database. When you specify the tablespace name. To apply changes. To apply changes. specify a tablespace name with one node. To apply changes. Password for the Metadata Manager repository database user. Note: The Metadata Manager repository code page.

Connection Pool Properties To edit the connection pool properties. If you increase the values. you can use this option to specify the location of a backup server if you are using a database server that is highly available such as Oracle RAC. Keystore file that contains the keys and certificates required if you use the SSL security protocol with the Metadata Manager application. For example. select the Properties view. Service name for IBM DB2 databases. The following table describes the configuration properties for a Metadata Manager Service: Property URLScheme Description Indicates the security protocol that you configure for the Metadata Manager application: HTTP or HTTPS. Additional JDBC options. Maximum queue length for incoming connection requests when all possible request processing threads are in use by the Metadata Manager application. Password for the keystore file. Default is 100. Keystore File Keystore Password MaxConcurrentRequests MaxQueueLength You can use the MaxConcurrentRequests property to set the number of clients that can connect to Metadata Manager. Configuring the Metadata Manager Service Properties 229 . Database name for Microsoft SQL Server databases. but the connections might use more system resources. To apply changes. select the Metadata Manager Service in the Navigator. which determines the maximum number of client requests that Metadata Manager can handle simultaneously.Property Database Port Description Port number for the Metadata Manager repository database. In a production environment. Indicates whether the Database Name property contains an Oracle full service name or an SID. Maximum number of request processing threads available. restart the Metadata Manager Service. you can increase the values. and then click Edit in the Configuration Properties section. and then click Edit in the Connection Pool Properties section. you can use smaller values in a test environment. You can change the parameter values based on the number of clients that you expect to connect to Metadata Manager. To apply changes. select the Properties view. Full service name or SID for Oracle databases. Default is 500. select the Metadata Manager Service in the Navigator. Metadata Manager refuses client requests when the queue is full. For example. more clients can connect to Metadata Manager. You must use the same security protocol for the Metadata Manager Agent if you install it on another machine. SID/Service Name Database Name Additional JDBC Parameters Configuration Properties To edit the configuration properties. You can use the MaxQueueLength property to set the number of client requests Metadata Manager can process at one time. restart the Metadata Manager Service.

If Metadata Manager cannot process the connection request to the repository within the wait time. select the Properties view. the log includes all errors at that level and above. select the Metadata Manager Service in the Navigator. and then click Edit in the Advanced Properties section.Warning . logical groups. the connection fails. Metadata Manager adds the eight loads to the load queue in a random order. The child objects can include folders. Metadata Manager adds the resource loads to the load queue in a random order. For example. if the severity level is Warning. you can use this value to increase the performance of Metadata Manager during indexing. Default is 100. error.Fatal .Debug When you specify a severity level. Maximum Catalog Child Objects Number of child objects that appear in the Metadata Manager metadata catalog for any parent object. The last three resource loads wait in the load queue. Metadata Manager adds resource loads to the load queue in the order that you request the loads. you set the property to 5 and schedule eight resource loads to run at the same time. The Metadata Manager application maintains a connection pool for connections to the repository database. Specify one of the following message levels: . Error Severity Level Level of error messages written to the Metadata Manager Service log. If you simultaneously load more than the maximum. The following table describes the advanced properties for a Metadata Manager Service: Property Max Heap Size Description Amount of RAM in megabytes allocated to the Java Virtual Manager (JVM) that runs Metadata Manager. Default is Error.Error . and metadata objects. Default is 180. Maximum Wait Time Advanced Properties To edit the advanced properties.Trace . Use this option to limit the number of child objects that appear in the metadata catalog for any parent object. Maximum is 5. Amount of time in seconds that Metadata Manager holds database connection requests in the connection pool.The following table describes the connection pool properties for a Metadata Manager Service: Property Maximum Active Connections Description Number of active connections to the Metadata Manager repository database available. Metadata Manager simultaneously processes the first five resource loads in the queue. For example. For example. Use this property to increase the performance of Metadata Manager. Default is 20.Info . the log includes fatal. Use Trace or Debug if Informatica Global Customer Support instructs you to use that logging level for troubleshooting purposes. Max Concurrent Resource Load Maximum number of resources that Metadata Manager can load simultaneously. Default is 1024. and warning messages. 230 Chapter 16: Metadata Manager Service .

Custom Properties The following table describes the custom properties: Property Custom Property Name Description Configure a custom property that is unique to your environment or that you need to apply in special cases. Metadata Manager removes the resource load from the queue. The PowerCenter Integration Service uses ODBC. Timeout Interval Amount of time in minutes that Metadata Manager holds a resumable resource load in the load queue. To apply changes. If you do not resume a failed load within the timeout period. To edit the associated PowerCenter Integration Service properties. You can select one of the following options: . Enter the property name and an initial value.Property Description If a resource load succeeds.True. Note: If a resource load fails during the path building task. Metadata Manager removes the resource from the load queue. the resource load is resumable. you can resume the failed load at any time. select the Metadata Manager Service in the Navigator. You must set this property to True if the PowerCenter Integration Service runs on a UNIX machine and you want to extract metadata from or load metadata to a Microsoft SQL Server database or if you use a Microsoft SQL Server database for the Metadata Manager repository. Metadata Manager keeps the resumable load in the load queue until the timeout interval is exceeded or until you resume the failed load.False. Use custom properties only if Informatica Global Customer Support instructs you to do so. The PowerCenter Integration Service uses native connectivity. You can resume a resource load within the timeout period if the load fails when PowerCenter runs the workflows and the workflows can be resumed. Configuring the Associated PowerCenter Integration Service You can configure or remove the PowerCenter Integration Service that Metadata Manager uses to load metadata into the Metadata Manager warehouse. If a resource load fails when the PowerCenter Integration Service runs the workflows and the workflows can be resumed. Metadata Manager starts processing the next load waiting in the queue. If you remove the PowerCenter Integration Service. Default is 30. fails and cannot be resumed. . select the Associated Services view. Metadata Manager includes a resumable load due to a failure during workflow processing in the concurrent load count. Default is 3. and click Edit. Configuring the Associated PowerCenter Integration Service 231 . configure another PowerCenter Integration Service to enable the Metadata Manager Service. restart the Metadata Manager Service. or fails during the path building task and can be resumed. ODBC Connection Mode Connection mode that the PowerCenter Integration Service uses to connect to metadata sources and the Metadata Manager repository when loading resources.

Read. If you change the associated PowerCenter Integration Service user.Access Informatica Administrator . Write. and Execute on the Metadata Load folder and all folders created to extract profiling data from the Metadata Manager source n/a PowerCenter Repository Service Metadata Manager Service Load Resource In the PowerCenter repository. and Delete Sources and Targets Create. ¨ Create. Edit. To perform these tasks. and Delete Design Objects Create.Manage Services Access Repository Manager Create Folders Create. Password for the PowerCenter repository user. the user must have the required privileges and permissions for the domain. PowerCenter Repository Service. Security domain for the PowerCenter repository user. the user who creates a folder or connection object is the owner of the object. ¨ Import and export PowerCenter repository objects. The following table lists the required privileges and permissions that the PowerCenter repository user for the associated PowerCenter Integration Service must have: Service Domain Privileges . and Metadata Manager Service. The object owner or a user assigned the Administrator role for the PowerCenter Repository Service can delete repository folders and connection objects. you must assign this user as the owner of the following repository objects in the PowerCenter Client: ¨ All connection objects created by the Metadata Manager Service ¨ The Metadata Load folder and all profiling folders created by the Metadata Manager Service 232 Chapter 16: Metadata Manager Service . and Execute on all connection objects created by the Metadata Manager Service . and Delete Run-time Objects Manage Run-time Object Execution Create Connections Permissions Permission on PowerCenter Repository Service .Read. The Security Domain field appears when the Informatica domain contains an LDAP security domain. Repository User Name Repository Password Security Domain Privileges for the Associated PowerCenter Integration Service User The PowerCenter repository user for the associated PowerCenter Integration Service must be able to perform the following tasks: ¨ Restore the PowerCenter repository. edit. Edit. and delete connection objects in the PowerCenter repository.The following table describes the associated PowerCenter Integration Service properties: Property Associated Integration Service Description Name of the PowerCenter Integration Service that you want to use with Metadata Manager. Name of the PowerCenter repository user that has the required privileges. Write. ¨ Create folders in the PowerCenter repository. Edit. ¨ Load metadata into the Metadata Manager warehouse.

Use the Administrator tool or the infacmd command line program to administer the Model Repository Service. inserts. 234 ¨ Model Repository Database Requirements. and updates metadata in the Model repository database tables. The Model repository stores metadata created by Informatica products in a relational database to enable collaboration among the products. 233 . A Model Repository Service process is an instance of the Model Repository Service on the node where the Model Repository Service runs. groups. 248 Model Repository Service Overview The Model Repository Service manages the Model repository. Model Repository Architecture The Model Repository Service process fetches. 238 ¨ Properties for the Model Repository Service Process.CHAPTER 17 Model Repository Service This chapter includes the following topics: ¨ Model Repository Service Overview. 233 ¨ Model Repository Architecture. and roles on the Security tab of the Administrator tool. you assign each Model Repository Service to run on one node. you can create a Model repository or use an existing Model repository. it restarts on the same node. You can run multiple Model Repository Services on the same node. When you create a Model Repository Service. Data Integration Service. 240 ¨ Model Repository Service Management. 237 ¨ Properties for the Model Repository Service. Informatica Developer. privileges. 243 ¨ Creating a Model Repository Service. 235 ¨ Model Repository Service Status. Informatica Analyst. and the Administrator tool store metadata in the Model repository. If the Model Repository Service fails. Manage users. Manage permissions for Model repository objects in the Informatica Developer and the Informatica Analyst. Create one Model Repository Service for each Model repository. Because the Model Repository Service is not a highly available service and does not run on a grid. 233 ¨ Model Repository Connectivity.

If you rename an application. update. The Data Integration Service creates and manages run-time objects and metadata in the Model repository. Note: A Model Repository Service can be associated with one Analyst Service and multiple Data Integration Services. When you start a Data Integration Service. The Developer and Analyst tools create. update. Run-time metadata generated during deployment are stored in the Model repository. ¨ Informatica Analyst. Informatica Analyst. the Deployment Manager copies application objects to the Model repository associated with the Data Integration Service. The Model repository stores the run-time metadata for each Data Integration Service separately. Informatica Analyst. and manage the design-time objects in the Model repository. and the Data Integration Service communicate with the Model Repository Service over TCP/IP. update. The Data Integration Service connects to the Model Repository Service to run or preview project components. the previous version is deleted from the repository. the previous application remains in the Model repository. and delete objects. Informatica Administrator. Informatica Developer connects to the Model Repository Service to create. and delete objects. Informatica Analyst connects to the Model Repository Service to create. Model Repository Objects The Model Repository Service stores design-time and run-time objects in the Model repository. Model Repository Connectivity The Model Repository Service connects to the Model repository using JDBC drivers. Informatica Developer. Informatica Developer and Informatica Analyst share objects in the Model repository. and Data Integration Service are Model repository clients. 234 Chapter 17: Model Repository Service . ¨ Data Integration Service. it connects to the Model Repository Service. When you deploy an application to the Data Integration Service.The Model Repository Service receives requests from the following client applications: ¨ Informatica Developer. Data Integration Services cannot share run-time metadata. The Data Integration Service also connects to the Model Repository Service to store run-time metadata in the Model repository. Application configuration and objects within an application are examples of run-time metadata. Informatica Developer and Informatica Analyst client applications share objects in the Model repository. Informatica Developer. If you replace or redeploy an application.

Informatica is not responsible for corrupted data that is caused by customer alteration of the repository tables or data within those tables. Model Repository Database Requirements Before you create a repository. The repository client establishes a TCP/IP connection with the Model Repository Service process on node A. ¨ Each Model repository must have a unique database name.The following figure shows how a Model repository client connects to the Model repository database: 1. you need a database to store repository tables. The Model Repository Service process stores objects in or retrieves objects from the Model repository database based on requests from the Model repository client. Note: The Model repository tables have an open architecture. Each Model repository must meet the following requirements: ¨ Each Model repository must have its own schema. each Model repository must meet database-specific requirements. The Model Repository Service process communicates with the Model repository database over JDBC. Two Model repositories or the Model repository and the domain configuration database cannot share the same schema. never manually edit them through other utilities. Model Repository Database Requirements 235 . 4. Although you can view the repository tables. In the diagram. you can use the Administrator tool to create a Model Repository Service. the Model Repository Service is running on node A. After you create a database. Use the database client to create the database. In addition. The Service Manager sends back the host name and port number of the node running the Model Repository Service. A Model repository client sends a repository connection request to the master gateway node. which is the entry point to the domain. 2. 3.

1 If the Model repository is in an IBM DB2 9. ¨ Set the tablespace pageSize parameter to 32768 bytes.DB2_SKIPINSERTED . Use the following command: REORGCHK UPDATE STATISTICS on SCHEMA <SchemaName> Run the command on the database after you create the repository content. you must specify a tablespace that meets the pageSize requirements. When you set up the DB2 database for the domain configuration repository or a Model repository. and BINDADD privileges. CONNECT. specify a tablespace that meets the pageSize requirements. The reorgchk command generates the database statistics used by the DB2 optimizer in queries and updates. set the following configuration parameters: Parameter applheapsz appl_ctl_heap_sz logfilsiz DynamicSections maxlocks locklist auto_stmt_stats Value 8192 8192 8000 3000 98 50000 ON For IBM DB2 9.1 database.DB2_SKIPDELETED . run the DB2 reorgchk command to optimize database operations.5 only. Informatica requires a larger DB2 package than the default. you can encounter problems when you install or run Informatica. If the DynamicSections parameter is set to a lower number. In a single-partition database. ¨ Verify the database user has CREATETAB. set the following parameters to ON: . the default tablespace must meet the pageSize requirements. Please recreate your package with a larger dynamicSections value.IBM DB2 Database Requirements Use the following guidelines when you set up the repository on IBM DB2: ¨ On the IBM DB2 instance where you create the database.DB2_EVALUNCOMMITTED . Define the tablespace on a single node. In a multi-partition database. The following error message can appear: [informatica][DB2 JDBC Driver]No more available statements. you must set the DynamicSections parameter to at least 3000. Note: The default value for DynamicSections in DB2 is too low for the Informatica repositories. If you do not specify a tablespace. 236 Chapter 17: Model Repository Service . IBM DB2 Version 9.AUTO_RUNSTATS ¨ On the database.

you must choose the mode to disable it in. CREATE TABLE. You can enable the Model Repository Service after you create it. the Administrator tool requires at least 256 MB of free memory. Tries to stop all jobs before aborting them and disabling the service. run the following command: SELECT is_read_committed_snapshot_on FROM sys. restore. a service process starts on a node designated to run the service and the service is available to perform repository transactions. and CREATE VIEW privileges. ¨ Abort.databases WHERE name = DatabaseName ¨ The database user account must have the CONNECT. run the following command: ALTER DATABASE DatabaseName SET READ_COMMITTED_SNAPSHOT ON To verify that the isolation level for the database is correct. Model Repository Service Status Use the Administrator tool to enable or disable a service. and delete Model repository content. These settings make sure that the Profiling Service Module does not truncate the Unicode characters: ¨Set NLS_CHARACTERSET to AL32UTF8. back up. and recycle the Model Repository Service in the Administrator tool. and CREATE VIEW permissions. RESOURCE. ¨ Configure the NLS_CHARACTERSET and NLS_LENGTH_SEMANTICS parameters using the setenv command if you need to profile a data source that supports the Unicode character set. ¨ Create and delete Model repository index. It may require up to one GB of free memory. When you enable the Model Repository Service. Disabling. Oracle Database Requirements Use the following guidelines when you set up the repository on Oracle: ¨ ¨ Verify the database user has CONNECT. the service may fail to start. Model Repository Service Status 237 . You can also enable a disabled service to make the service or application available again. Allows the jobs to run to completion before disabling the service. If enough free memory is not available. You can disable the service to perform maintenance or to temporarily restrict users from accessing the Model Repository Service or Model repository. Enabling. When you disable the Model Repository Service. ¨Set NLS_LENGTH_SEMANTICS to CHAR. You must enable the Model Repository Service to perform the following tasks in the Administrator tool: ¨ Create.Microsoft SQL Server Database Requirements Use 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. disable. To set the isolation level for the database. ¨ Manage permissions on the Model repository. You can choose one of the following options: ¨ Complete. and Recycling the Model Repository Service You can enable. When you enable the service.

select the Model Repository Service. The Enable option does not appear when the service is enabled. click Recycle Service to restart the Model Repository Service. Properties for the Model Repository Service Use the Administrator tool to configure the following service properties: ¨ General properties ¨ Repository performance properties ¨ Search properties ¨ Advanced properties ¨ Cache properties ¨ Custom properties General Properties for the Model Repository Service The following table describes the general properties for the Model Repository Service: Property Name Description Name of the Model Repository Service. 238 Chapter 17: Model Repository Service . 3.<>|!()][ Description License Node Description of the Model Repository Service. On the Domain Actions menu. The description cannot exceed 765 characters..:'"/?. click Disable Service to disable the Model Repository Service. 4. The Disable option does not appear when the service is disabled. In the Navigator. Displays the node on which the Model Repository Service runs. In the Administrator tool. 5. click Enable Service to enable the Model Repository Service. Or. It cannot exceed 128 characters or begin with @. click the Domain tab. To enable or disable the Model Repository Service: 1. Or. on the Domain Actions menu.When you recycle the Model Repository Service. the Service Manager restarts the Model Repository Service. The name is not case sensitive and must be unique within the domain. 2. Not applicable to the Model Repository Service. It also cannot contain spaces or the following special characters: `~%^*+={}\. on the Domain Actions menu.

jdbc. enter the name of either the search analyzer class or the search analyzer factory class. Search Properties for the Model Repository Service The following table describes the search properties for the Model Repository Service: Property Search Analyzer Description Fully qualified Java class name of the search analyzer. For a multi-partition IBM DB2 database.provider.oracle. The database user name for the Model repository. If you use a custom search analyzer.CatalogOptions=0 Dialect The SQL dialect for a particular database.service. For example: org.search.repository.hibernate.SID=DatabaseName.CJKAnalyzer Or. For example: com. Properties for the Model Repository Service 239 . the Model Repository Service uses the following search analyzer for English: com. Search Analyzer Factory Fully qualified Java class name of the factory class if you used a factory class when you created a custom search analyzer. By default.analysis.informatica.cjk. the connection string for an Oracle database can have the following syntax: jdbc:informatica:oracle:// HostName:PortNumber.lucene. For example. An encrypted version of the database password for the Model repository.OracleDriver Database Schema Database Tablespace The schema name for a Microsoft SQL Server database.analysis. the tablespace must span a single node and a single partition.Oracle9Dialect Driver The Data Direct driver used to connect to the database. Japanese and Korean languages: org. The JDBC connection string used to connect to the Model repository database.MaxPooledStatements=20.informatica.Repository Performance Properties for the Model Repository Service The following table describes the performance properties for the Model repository: Property Database Type Username Password JDBC Connect String Description The type of database. you can create and specify a custom search analyzer. The tablespace name for an IBM DB2 database.apache.MMStandardAnalyzer You can specify the following Java class name of the search analyzer for Chinese. The dialect maps java objects to database objects.dialect.

Cache JVM Options Custom Properties for the Model Repository Service Custom properties include properties that are unique to your environment or that apply in special cases. The options you configure in this field do not apply to the JVM that runs the Model Repository Service. Default value is 256 m. restart the Model Repository Service.k for kilobytes. Properties for the Model Repository Service Process The Model Repository Service runs the Model Repository Service process on one node. JVM Command Line Options Java Virtual Machine (JVM) command line options to run Java-based programs. and Java SDK maximum memory properties. You must set the following JVM command line options: . To configure the amount of memory allocated to cache. To apply changes. you must set the Java SDK classpath.Advanced Properties for the Model Repository Service The following table describes the Advanced properties for the Model Repository Service: Property Maximum Heap Size Description Amount of RAM allocated to the Java Virtual Machine (JVM) that runs the Model Repository Service. When you configure the JVM options. .Dfile. JVM options for the Model Repository Service cache. This field must include the maximum heap size.Xms. The options you configure apply when Model Repository Service cache is enabled. Cache Properties for the Model Repository Service The following table describes the cache properties for the Model Repository Service: Property Enable Cache Description Enables the Model Repository Service to store Model repository objects in cache memory. Default is UTF-8. Use custom properties only at the request of Informatica Global Customer Support. configure the maximum heap size. . Java SDK minimum memory. you can view information about the Model Repository Service 240 Chapter 17: Model Repository Service . . File encoding.MaxPermSize. To apply changes. When you select the Model Repository Service in the Administrator tool. Default is 1024 megabytes. Use this property to increase the performance. . Maximum permanent generation size. restart the Model Repository Service. specified by the -Xmx option. A Model Repository Service process does not have custom properties when you initially create it. Append one of the following letters to the value to specify the units: . Default is 128 m.encoding. The default value and minimum value for the maximum heap size is -Xmx128m.b for bytes. .g for gigabytes. Minimum heap size.m for megabytes.

The Model Repository Service uses an open source object-relational mapping tool called Hibernate to map and store data objects and metadata to the Model repository database.connection. Hibernate c3p0 Maximum Statements Properties for the Model Repository Service Process 241 . The following table describes the search properties for the Model Repository Service process: Property Search Index Root Directory Description The directory that contains the search index files. Minimum number of connections a pool will maintain at any given time. Equivalent to the c3p0 minPoolSize property. The Model Repository Service uses the value of this property to set the c3p0 maxStatementsPerConnection property based on the number of connections set in the Hibernate Connection Pool Size property.pool_size property. Default is 10.process on the Processes tab. Repository Database Properties for the Model Repository Service Process Performance tuning properties for storage of data objects in the Model Repository Service. You can also configure search and logging for the Model Repository Service process. Default is: <Informatica_Installation_Directory>/tomcat/bin/target/repository/ <system_time>/<service_name>/index system_time is the system time when the directory is created. Default is 500. Note: You must select the node to view the service process properties in the Service Process Properties section. Node Properties for the Model Repository Service Process Use the Administrator tool to configure the following types of Model Repository Service process properties: ¨ Search properties ¨ Repository database properties ¨ Audit properties ¨ Repository properties ¨ Custom Properties ¨ Environment variables Search Properties for the Model Repository Service Process Search properties for the Model Repository Service process. Equivalent to the hibernate. Default is 1. The following table describes the connection properties for the Model Repository Service process: Property Hibernate Connection Pool Size Hibernate c3p0 Minimum Size Description The maximum number of pooled connections in the Hibernate internal connection pooling. For each service process. This property controls the total number of statements cached. Equivalent to the c3p0 maxStatements property. Size of the c3p0 global cache for prepared statements. you can set Hibernate options to configure connection and statement pooling for the Model repository.

or upgraded. The following table describes the audit properties for the Model Repository Service process: Property Audit Enabled Description Displays audit logs in the Log Viewer. and debug. You must disable and re-enable the Model Repository Service after you change this option. the Model Repository Service does not generate the log files. The Model Repository Service logs information about the database schema. The Model Repository Service stores the logs in the specified repository logging directory. Default is blank. object relational mapping. repository schema change audit log. trace. Environment Variables for the Model Repository Service Process You can edit environment variables for a Model Repository Service process. warning. Default is info. If a repository logging directory is not specified. If a repository logging directory is not specified. The following table describes the environment variables for the Model Repository Service process: Property Environment Variables Description Environment variables defined for the Model Repository Service process. Indicates whether to write parameterized SQL statements to a log file in the specified repository logging directory. and registered IMF packages. Valid values are: fatal. The severity level for repository logs. the Model Repository Service does not generate the log files. info. To disable the logs. Default is False. The following table describes the repository log properties for the Model Repository Service process: Property Repository Logging Directory Description The directory that stores logs for Log Persistence Configuration or Log Persistence SQL. You must disable and re-enable the Model Repository Service after you change this option. Default is False. The Model Repository Service creates the log file when the Model repository is enabled.Audit Properties for the Model Repository Service Process Audit properties for the Model Repository Service process. Default is False. Repository Logs for the Model Repository Service Process Repository log properties for the Model Repository Service process. A Model Repository Service process does not have custom properties when you initially create it. Use custom properties only at the request of Informatica Global Customer Support. Indicates whether to write persistence configuration to a log file. created. These logs are not the repository logs that appear in the Log Viewer. error. Log Level Log Persistence Configuration to File Log Persistence SQL to File Custom Properties for the Model Repository Service Process Custom properties include properties that are unique to your environment or that apply in special cases. do not specify a logging directory. 242 Chapter 17: Model Repository Service .

The repository name is the same as the name of the Model Repository Service. the Model Repository Service saves the repository to a file. the backup operation blocks all other repository operations until the backup completes. select the Model Repository Service. 3. For example. 1. In the Navigator. the Model Repository Service writes the file to the service backup directory. click Repository Contents > Back Up. For example. Creating and Deleting Repository Content 1. a Model Repository Service named MRS writes repository backup files to the following location: <node_backup_directory>\MRS You specify the node backup directory when you set up the node.mrep for all Model repository backup files. Alternatively. To create the repository content. to delete repository content. on the Domain Actions menu. you can create the repository content. Or. 3. click Repository Contents > Create. you can create the Model Repository Service using existing repository content. The Back Up Repository Contents dialog box appears. 4. Model Repository Backup and Restoration Regularly back up repositories to prevent data loss due to hardware or software problems. When you back up a repository. Backing Up the Repository Content You can back up the content of a Model repository to restore the repository content to another repository or to retain a copy of the repository. search. The Model Repository Service uses the extension . You may choose to delete repository content to delete a corrupted repository or to increase disk or database space. you can use the Administrator tool to manage repository content. 2. To ensure that the Model Repository Service creates a consistent backup file. In the Navigator. on the Domain Actions menu. Model Repository Service Management 243 . On the Domain tab. click Repository Contents > Delete. On the Domain tab. If you need to recover the repository. you can restore the content of the repository from this file. You can also delete the repository content. 2. including the repository objects and the search index. Content Management for the Model Repository Service When you create the Model Repository Service. select the Services and Nodes view. The service backup directory is a subdirectory of the node backup directory with the name of the Model Repository Service. and repository logs.Model Repository Service Management Use the Administrator tool to manage the Model Repository Service and the Model repository content. select the Services and Nodes view. You might want to schedule repository backups when users are not logged in. select the Model Repository Service. When you back up a repository. On the Domain Actions menu. View the general properties of the node to determine the path of the backup directory.

The Model Repository Service writes the backup file to the service backup directory. 1. Domain to which the domain user belongs. 2. Default is Native. 244 Chapter 17: Model Repository Service . 6. Restoring the Repository Content You can restore repository content to a Model repository from a repository backup file. Enter the following information: Option Username Password SecurityDomain Description User name of any user in the domain. select the Services and Nodes view. On the Domain Actions menu. 3. Default is Native. In the Navigator. the restore option is disabled. The Restore Repository Contents dialog box appears. Description of the contents of the output file. 4. select the Services and Nodes view.4. Password of the domain user. select the Model Repository Service. Click OK. 5. click Repository Contents > View Backup Files. click Repository Contents > Restore. Domain to which the domain user belongs. 1. On the Domain Actions menu. On the Domain tab. The View Repository Backup Files dialog box appears and shows the backup files for the Model Repository Service. On the Domain tab. Click Overwrite to overwrite a file with the same name. In the Navigator. 5. Enter the following information: Option Username Password SecurityDomain Output File Name Description Description User name of any user in the domain. select the Model Repository Service. 2. Select a backup file to restore. 3. If the repository contains content. Click OK. 6. Viewing Repository Backup Files You can view the repository backup files written to the Model Repository Service backup directory. Name of the output file. Verify that the repository is empty. Password of the domain user.

You must manually update the search index after an upgrade. If you use a factory class when you extend the Analyzer class. you can create a custom search analyzer. Default search analyzer for English. ¨ org. The owner can assign permissions to users or groups in the repository.apache. which you cannot change. Place the custom search analyzer and required . To correctly index the metadata. and roles on the Security tab of the Administrator tool.informatica.lucene. In the Navigator. In the Administrator tool.MMStandardAnalyzer.Security Management for the Model Repository Service You manage users. you can create a project and assign permissions to it.Analyzer createAnalyzer(Properties settings) The Model Repository Service uses the factory to connect to the search analyzer. the Model Repository Service uses a search analyzer appropriate for the language of the metadata that you are indexing.repository.lucene. and Korean. The owner has all permissions. 3. When users perform a search in the Developer tool or Analyst tool.analysis. You can use a packaged search analyzer or you can create and use a custom search analyzer. When you create a project. Extend the following Apache Lucene Java class: org. the Model Repository Service searches for metadata objects in the index files instead of the Model repository. privileges. Permissions control access to projects in the repository. Search Management for the Model Repository Service The Model Repository Service uses a search engine to create search index files. You manage permissions for repository objects in Informatica Developer and Informatica Analyst. you are the owner of the project by default. The Model Repository Service stores the index files in the search index root directory that you define for the service process. The Model Repository Service includes the following packaged search analyzers: ¨ com.analysis. Creating a Custom Search Analyzer If you do not want to use one of the packaged search analyzers. 1.CJKAnalyzer. 1. You can use a packaged search analyzer or you can create and use a custom search analyzer. Even if a user has the privilege to perform certain actions.apache.service.cjk. select the Model Repository Service.analysis. The Model Repository Service updates the search index files each time a user saves an object to the Model repository. or if the search index files become corrupted.provider. Search analyzer for Chinese.jar files in the following directory: <Informatica_Installation_Directory>/tomcat/bin Changing the Search Analyzer You can change the default search analyzer that the Model Repository Service uses. select the Services and Nodes view on the Domain tab. 2.search. the factory class implementation must have a public method with the following signature: public org.lucene. Model Repository Service Management 245 . To secure data in the repository.apache.analysis. Japanese. after changing the search analyzer.Analyzer 2. the user may also require permission to perform the action on a particular object. groups. You can change the default search analyzer.

click Search Index > Re-Index on the Domain Actions menu. 6. specify the fully qualified java class name of either the search analyzer or the search analyzer factory in the Model Repository Service search properties. To correct corrupted search index files. 2. Configuring Repository Logging 1. You can configure the level of detail that appears in the repository log files. Click Search Index > Delete to delete the corrupted search index. Select the node. Click Edit in the Repository section. select the Model Repository Service. specify the fully qualified java class name of the search analyzer in the Model Repository Service search properties. Users in the Developer tool and Analyst tool can view design-time objects but cannot edit or create design-time objects. For example. In the Administrator tool. Click Search Index > Create to create a search index. On the Domain Actions menu. To use a custom search analyzer. If you re-index after an upgrade or after changing the search analyzer. and then re-index the search index. design-time objects in the Model repository are read-only. The repository logs contain repository messages of different severity levels. 4. You can also configure where the Model Repository Service stores the log files. you must delete. search index files can become corrupted due to insufficient disk space in the search index root directory. During the reindexing process. The amount of time needed to re-index depends on the number of objects in the Model repository. users cannot perform a search until the re-indexing process finishes. 4. select the Model Repository Service. 4. In the Navigator. 5. such as fatal. In the Navigator. 246 Chapter 17: Model Repository Service . create. To use one of the packaged search analyzers.3. any subsequent user search request uses the new index. and debug. or when the search index files become corrupted. 1. 3. In the Administrator tool. select the Services and Nodes view on the Domain tab. When the re-indexing process completes. When you delete and create a search index. Repository Log Management for the Model Repository Service The Model Repository Service generates repository logs. warning. b. You might want to manually update the search index files during a time when most users are not logged in. trace. c. Manually Updating Search Index Files You manually update the search index after an upgrade. users can perform searches on the existing index while the re-indexing process runs. select the Processes view. Click Search Index > Re-Index to re-index the search index. The service process details appear in the Service Process Properties section. click Search Index > Re-Index to re-index the search index. In the contents panel. To re-index after an upgrade or after changing the search analyzer. error. 3. info. 2. To correct corrupted search index files. Recycle the Model Repository Service to apply the changes. complete the following steps on the Domain Actions menu: a. 5. click the Domain tab. after you change the search analyzer.

audit logging is disabled. Click Edit in the Audit section. In the contents panel. click the Domain tab. you can configure the Model Repository Service to use cache memory. the Model Repository Service stores each object it reads in memory. 7. select the Model Repository Service. the Model Repository Service compares the object in memory with the object in the repository. 3. select the Processes view. ¨ False. Reading objects from memory reduces the load on the database server and improves response time. The service process details appear in the Service Process Properties section. Click OK. Enter one of the following values in the Audit Enabled field.The Edit Processes page appears. Disables audit logging. 8. Enabling and Disabling Audit Logging 1. Cache Management for the Model Repository Service To improve Model Repository Service performance. Click OK. ¨ True. Model Repository Cache Processing When the cache process starts. The Edit Processes page appears. 6. If the latest version of the object is not in memory. In the Navigator. When you configure the Model Repository Service to use cache memory. The audit log provides information about the following types of operations performed on the Model repository: ¨ Logging in and out of the Model repository ¨ Creating a project ¨ Creating a folder By default. Enter the directory path in the Repository Logging Directory field. the Model Repository Service stores objects that it reads from the Model repository in memory. In the Administrator tool. Default is false. Select the node. Model Repository Service Management 247 . Enables audit logging. 7. 5. 6. 2. When the Model Repository Service gets a request for an object from a client application. The Model Repository Service can read the repository objects from memory instead of the Model repository. 4. the Model repository updates the cache and then returns the object to the client application that requested the object. When the amount of memory allocated to cache is full. Specify the level of logging in the Repository Logging Severity Level field. Audit Log Management for Model Repository Service The Model Repository Service can generate audit logs in the Log Viewer. the Model Repository Service deletes the cache for least recently used objects to allocate space for another object.

3. Select this option to create content for the Model repository in the specified database. Click Test Connection to test the connection to the database. 3. Select one of the following options: ¨ Do Not Create New Content. On the Domain Actions menu. enter the general properties for the Model Repository Service. 6. click the Domain tab. Click Finish. Configuring Cache 1. The Java Virtual Manager (JVM) that runs the Model Repository Service is not affected by the JVM options you configure for the Model Repository Service cache. click the Domain tab. 4. In the Navigator. Select this option if the specified database already contains content for the Model repository. In the Administrator tool. The Model Repository Service logs display the following message when the cache process is running: MRSI_35204 "Caching process has started on host [host name] at port [port number] with JVM options [JVM options]. 8. Verify that the cache process is running. 4. 5." Creating a Model Repository Service 1. Create a database for the Model repository. select the Model Repository Service. ¨ Create New Content. 5. In the Administrator tool. Restart the Model Repository Service. 7. click New > Model Repository Service. Enter the database properties for the Model Repository Service. This is the default. 9. Click Edit in the Cache Properties section.The Model Repository Service cache process runs as a separate process. Specify the amount of memory allocated to cache in the Cache JVM Options field. 2. 7. 248 Chapter 17: Model Repository Service . In the properties view. 6. 2. Select Enable Cache. Click Next.

You must associate a repository with a PowerCenter Integration Service. 257 ¨ Operating System Profiles. 267 ¨ PowerCenter Integration Service Processes. 265 ¨ Associated Repository for the PowerCenter Integration Service. ¨ Configure permissions on the PowerCenter Integration Service. 250 ¨ Enabling and Disabling PowerCenter Integration Services and Processes. ¨ Configure the PowerCenter Integration Service processes. The PowerCenter Integration Service uses the mappings in the repository to run sessions and workflows. 249 ¨ Creating a PowerCenter Integration Service. ¨ Configure the PowerCenter Integration Service properties. 253 ¨ PowerCenter Integration Service Properties. ¨ Enable or disable the PowerCenter Integration Service.Configure the PowerCenter Integration Service to run in normal or safe mode. You can use the Administrator tool to complete the following configuration tasks for the PowerCenter Integration Service: ¨ Create a PowerCenter Integration Service. such as the code page and service process variables. 249 .CHAPTER 18 PowerCenter Integration Service This chapter includes the following topics: ¨ PowerCenter Integration Service Overview. Configure service process properties for each node. 267 ¨ Configuration for the PowerCenter Integration Service Grid. 252 ¨ Operating Mode. ¨ Configure normal or safe mode. 276 PowerCenter Integration Service Overview The PowerCenter Integration Service is an application service that runs sessions and workflows. You might disable the PowerCenter Integration Service to prevent users from running sessions and workflows while performing maintenance on the machine or modifying the repository. Enable the PowerCenter Integration Service to run sessions and workflows. Use the Administrator tool to manage the PowerCenter Integration Service. Configure the PowerCenter Integration Service properties to change behavior of the PowerCenter Integration Service. 272 ¨ Load Balancer for the PowerCenter Integration Service . Create a PowerCenter Integration Service to replace an existing PowerCenter Integration Service or to use multiple PowerCenter Integration Services. ¨ Configure the associated repository.

you must start the node and configure $PMRootDir for the service process before you run workflows with the PowerCenter Integration Service. 2.<>|!()][ Description Description of the PowerCenter Integration Service. The New Integration Service dialog box appears. Creating a PowerCenter Integration Service You can create a PowerCenter Integration Service when you configure Informatica application services. If you do not select a license now. It also cannot contain spaces or the following special characters: `~%^*+={}\. You can also move the PowerCenter Integration Service to a different folder after you create it. You must assign a PowerCenter repository to the PowerCenter Integration Service. such as workflows and mappings. You may need to remove a PowerCenter Integration Service if it becomes obsolete. You must assign a repository before you can run the PowerCenter Integration Service. 3. You can assign the repository when you create the PowerCenter Integration Service or after you create the PowerCenter Integration Service. The name is not case sensitive and must be unique within the domain. The following table describes the PowerCenter Integration Service options: Property Name Description Name of the PowerCenter Integration Service. Click Browse to choose a different folder. License to assign to the PowerCenter Integration Service. You must select the associated repository before you can select the code page for a PowerCenter Integration Service process. In the Administrator tool.:'"/?. click the Domain tab. Note: If you configure a PowerCenter Integration Service to run on a node that is unavailable. you must assign a code page for each PowerCenter Integration Service process. 1. click New > PowerCenter Integration Service. The characters must be compatible with the code page of the associated repository. The PowerCenter Repository Service must be enabled to set up a code page for a PowerCenter Integration Service process. Enter values for the following PowerCenter Integration Service options. The repository that you assign to the PowerCenter Integration Service is called the associated repository. Domain and folder where the service is created. On the Navigator Actions menu. The code page for each PowerCenter Integration Service process must be a subset of the code page of the associated repository. Required if you want to enable the PowerCenter Integration Service. from the associated repository.¨ Remove a PowerCenter Integration Service. you can assign a license to the service later. It cannot exceed 128 characters or begin with @. The description cannot exceed 765 characters. The PowerCenter Integration Service retrieves metadata.. The options allowed in your license determine the properties you must set for the PowerCenter Integration Service. Location License 250 Chapter 18: PowerCenter Integration Service . You may need to create an additional PowerCenter Integration Service to replace an existing one or create multiple PowerCenter Integration Services. After you create a PowerCenter Integration Service.

You cannot enable the PowerCenter Integration Service until you assign the code page for each PowerCenter Integration Service process node. Nodes used as backup to the primary node. Displays if you configure the PowerCenter Integration Service to run on mutiple nodes and you have the high availability option. Required if you assign the PowerCenter Integration Service to run on a grid. Choose ASCII or Unicode. To apply changes. Unicode mode passes 8-bit ASCII and multibyte character data from sources to targets. You must select the PowerCenter Repository Service before you run the PowerCenter Integration Service. 4. 5. Assign Grid Primary Node Primary node on which the PowerCenter Integration Service runs. Required if you do not select a license or your license does not include the high availability option. Repository User Name User name to access the repository. If you do not select the associated PowerCenter Repository Service now. Indicates whether the PowerCenter Integration Service runs on a grid or nodes. Security Domain Data Movement Mode Mode that determines how the PowerCenter Integration Service handles character data. Available if your license includes the high availability option. To apply changes. you can select it later. Repository Password Password for the user. Required when you select an associated PowerCenter Repository Service. Required when you select an associated PowerCenter Repository Service. If you do not specify the code page information now. ASCII mode passes 7-bit ASCII or EBCDIC character data. Click Finish. you can specify it later. restart the PowerCenter Integration Service. Required if you assign the PowerCenter Integration Service to run on nodes. You must specify a PowerCenter Repository Service before you can enable the PowerCenter Integration Service. To apply changes. To apply changes. Click Finish.Property Node Description Node on which the PowerCenter Integration Service runs. Security domain for the user. restart the PowerCenter Integration Service. You can specify the code page for each PowerCenter Integration Service process node and select the Enable Service option to enable the service. Backup Nodes Associated Repository Service PowerCenter Repository Service associated with the PowerCenter Integration Service. The Security Domain field appears when the Informatica domain contains an LDAP security domain. Creating a PowerCenter Integration Service 251 . Default is ASCII. restart the PowerCenter Integration Service. restart the PowerCenter Integration Service. Click Select to choose the nodes to use for backup. restart the PowerCenter Integration Service. To apply changes. Name of the grid on which the PowerCenter Integration Service run.

go to the Domain tab Actions menu and select Disable Process. ¨ Stop. To disable a service process. Tries to stop all sessions and workflows before aborting them and disabling the service process. Select a process On the Domain tab Actions menu. In the Navigator. If you run the PowerCenter Integration Service on a grid or with the high availability option. go to the Domain tab Actions menu and select Enable Process. ¨ Abort. Stops all sessions and workflows and then disables the service process. click the Processes view. If you are running a PowerCenter Integration Service on a grid. Choose the disable mode and click OK. 252 Chapter 18: PowerCenter Integration Service . you must choose the mode to disable it in. the PowerCenter Integration Service runs all enabled PowerCenter Integration Service processes. you disable all service processes on the grid. Allows the sessions and workflows to run to completion before shutting down the service. ¨ Stop. select the PowerCenter Integration Service. Tries to stop all sessions and workflows before aborting them and shutting down the service. In the contents panel. You may want to disable the service process on a node to perform maintenance on that node or to enable safe mode for the PowerCenter Integration Service. You must choose one of the following options: ¨ Complete. To enable or disable a PowerCenter Integration Service process: 1. You can enable a disabled PowerCenter Integration Service to make it available again. With high availability. ¨ Abort. You can choose one of the following options: ¨ Complete. you shut down the PowerCenter Integration Service and disable all service processes for the PowerCenter Integration Service. 5. To enable a service process. select Disable Process to disable the service process or select Enable Process to enable the service process. the PowerCenter Integration Service runs the PowerCenter Integration Service process on the primary node.Enabling and Disabling PowerCenter Integration Services and Processes You can enable and disable a PowerCenter Integration Service process or the entire PowerCenter Integration Service. you have one PowerCenter Integration Service process configured for each node. 3. 2. 7. click the Domain tab. Stops all sessions and workflows and then shuts down the service. Each service process runs on one node. For a grid. 4. When you disable the PowerCenter Integration Service. you must choose what to do if a process or workflow is running. When you disable the PowerCenter Integration Service. 6. Enabling or Disabling the PowerCenter Integration Service Use the Administrator tool to enable and disable a PowerCenter Integration Service. You must enable the PowerCenter Integration Service process if you want the node to perform PowerCenter Integration Service tasks. Allows the sessions and workflows to run to completion before disabling the service process. Enabling or Disabling a PowerCenter Integration Service Process Use the Administrator tool to enable and disable a PowerCenter Integration Service process. When you disable a PowerCenter Integration Service process. You may want to disable a PowerCenter Integration Service if you need to perform maintenance or if you want temporarily restrict users from using the service. In the Administrator tool.

If you enable a PowerCenter Integration Service when the associated PowerCenter Repository Service is not running. 2. click the Domain tab In the Navigator. When you enable the PowerCenter Integration Service to run in safe mode or when the PowerCenter Integration Service fails over in safe mode. Safe mode limits user access to the PowerCenter Integration Service and workflow activity during environment migration or PowerCenter Integration Service maintenance activities. For example. If the service fails to start. The domain keeps trying to start the service until it reaches the maximum number of attempts. the Service Manager keeps trying to start the service until it reaches the maximum restart attempts defined in the domain properties. In normal mode.When you enable the PowerCenter Integration Service. It also completes workflow failover for any workflows that failed while in safe Operating Mode 253 . 3. you must disable and re-enable the PowerCenter Integration Service to start it. it limits access and workflow activity to allow administrators to perform migration or maintenance activities. If the PowerCenter Integration Service is unable to start. select Recycle. users with workflow privileges can run workflows and get session and workflow information for workflows assigned to the PowerCenter Integration Service. The service does not start without specifying a valid code page for each PowerCenter Integration Service process. To enable or disable a PowerCenter Integration Service: 1. the service starts. review the logs for this PowerCenter Integration Service to determine the reason for failure and fix the problem. Normal Mode When you enable a PowerCenter Integration Service to run in normal mode. if you try to start the PowerCenter Integration Service without specifying the code page for each PowerCenter Integration Service process. Run the PowerCenter Integration Service in safe mode to control which workflows a PowerCenter Integration Service runs and which users can run workflows during migration and maintenance activities. users that have the Administrator role for the associated PowerCenter Repository Service can run workflows and get information about sessions and workflows assigned to the PowerCenter Integration Service. The associated PowerCenter Repository Service must be started before you can enable the PowerCenter Integration Service. select the PowerCenter Integration Service. In safe mode. Operating Mode You can run the PowerCenter Integration Service in normal or safe operating mode. In the Administrator tool. To disable and immediately enable the PowerCenter Integration Service. Normal mode provides full access to users with permissions and privileges to use a PowerCenter Integration Service. Run the PowerCenter Integration Service in normal mode during daily operations. the domain tries to start the service. the following error appears: The Service Manager could not start the service due to the following error: [DOM_10076] Unable to enable service [<Integration Service] because of dependent services [<PowerCenter Repository Service>] are not initialized. 4. manage workflow schedules. Run in safe mode to verify a production environment. or maintain a PowerCenter Integration Service. select Disable Service to disable the service or select Enable Service to enable the service. You can configure the PowerCenter Integration Service to run in safe mode or to fail over in safe mode. the PowerCenter Integration Service begins running scheduled workflows. After you fix the problem. On the Domain tab Actions menu.

or stop running workflows. you can correct the error that caused the PowerCenter Integration Service process to fail over and restart the service in normal mode. In addition. abort. You can manually recover the workflow. including workflows scheduled to run continuously or start on service initialization. access to the PowerCenter Integration Service is limited. The behavior of the PowerCenter Integration Service when it fails over in safe mode is the same as when you enable the PowerCenter Integration Service in safe mode. and the workflows recovered by the PowerCenter Integration Service. and the privileges required to run and monitor workflows in safe mode. Enable the PowerCenter Integration Service in safe mode to perform migration or maintenance activities. All scheduled workflows. unschedule the workflow. You can configure the PowerCenter Integration Service to run in safe mode or to fail over in safe mode: ¨ Enable in safe mode. do not run. During migration. Configure the PowerCenter Integration Service process to fail over in safe mode during migration or maintenance activities. ¨ Fail over in safe mode. it restarts in safe mode and limits workflow activity and access to the PowerCenter Integration Service. When you change the operating mode from safe to normal. but does not fail over or automatically recover the workflows. Users with workflow privileges can run workflows and get session and workflow information for workflows assigned to the PowerCenter Integration Service. ¨ Manage workflow schedules. the workflows that failed over. The PowerCenter Integration Service does not fail over schedules or workflows. Run the PowerCenter Integration Service in safe mode to limit access to the PowerCenter Integration Service when you run the test sessions and command tasks. and does not recover client requests. Performing Migration or Maintenance You might want to run a PowerCenter Integration Service in safe mode for the following reasons: ¨ Test a development environment. You can enable the PowerCenter Integration Service in safe mode. you can choose to have the PowerCenter Integration Service complete. When you enable the PowerCenter Integration Service in safe mode. the operating mode on failover also changes to safe. You can run workflows that contain session and command tasks to test the environment. you limit access to the PowerCenter Integration Service. and 254 Chapter 18: PowerCenter Integration Service . The PowerCenter Integration Service restores the state of operations for any workflows that were running when the service process failed over. When the PowerCenter Integration Service process fails over to a backup node. Running the PowerCenter Integration Service in Safe Mode This section describes the specific migration and maintenance activities that you can complete in the PowerCenter Workflow Manager and PowerCenter Workflow Monitor. does not automatically recover workflows. the behavior of the PowerCenter Integration Service in safe mode. recovers client requests. the PowerCenter Integration Service begins running scheduled workflows and completes workflow failover and workflow recovery for any workflows configured for automatic recovery. Run the PowerCenter Integration Service in safe mode to test a development environment before migrating to production. When you enable a PowerCenter Integration Service in safe mode. You can use the Administrator tool to view the log events about the scheduled workflows that started. and recovers any workflows configured for automatic recovery that failed in safe mode. you can unschedule workflows that only run in a development environment. After the PowerCenter Integration Service fails over in safe mode during normal operations. Safe Mode In safe mode.mode.

When you enable the PowerCenter Integration Service in normal mode. This includes workflows scheduled to run continuously and run on service initialization. abort. and recover workflows. Configure the PowerCenter Integration Service to fail over in safe mode and troubleshoot errors when you migrate or test a production environment configured for high availability. session. Connect to the PowerCenter Integration Service in the PowerCenter Workflow Monitor and get task. Workflow schedules do not fail over when a PowerCenter Integration Service fails over in safe mode. Monitor PowerCenter Integration Service properties. workflows do not fail over. Unschedule workflows in the PowerCenter Workflow Manager. The PowerCenter Integration Service does not complete the remaining workflows when it fails over to the backup node. Scheduled workflows remain scheduled. and verify the PowerCenter Integration Service functionality before allowing other users to run workflows. Unschedule workflows. you can limit the users who can run workflows. When a PowerCenter Integration Service process fails over in safe mode. Recover workflows. PowerCenter Integration Service Behavior Safe mode affects PowerCenter Integration Service behavior for the following workflow and high availability functionality: ¨ Workflow schedules. ¨ Perform maintenance on the PowerCenter Integration Service. The PowerCenter Integration Service restores the state of operations for the workflow. Monitor workflow and task details. For example. and workflow details. the workflows that you unscheduled do not run. but they do not run if the PowerCenter Integration Service is running in safe mode. you configure a PowerCenter Integration Service to fail over in safe mode. Manually recover failed workflows. The workflows may contain session or command tasks required to test a development or production environment. After you enable the service in normal mode. The PowerCenter Integration Service completes the workflows when you enable the PowerCenter Integration Service in safe mode. Task Description Start. the PowerCenter Integration Service fails over the workflow and recovers it based on the recovery strategy for the workflow. For example. Connect to the PowerCenter Integration Service in the PowerCenter Workflow Monitor. You can enable the PowerCenter Integration Service in safe mode.then enable the PowerCenter Integration Service in normal mode. you can correct the error that caused the PowerCenter Integration Service to fail over. change PowerCenter Integration Service properties. ¨ Workflow failover. and it fails over after it runs the workflow three times. Get PowerCenter Integration Service details and monitor information. ¨ Troubleshoot the PowerCenter Integration Service. The PowerCenter Integration Service process fails for a workflow scheduled to run five times. After the PowerCenter Integration Service fails over in safe mode. Workflow Tasks The following table describes the tasks that users with the Administrator role can perform when the PowerCenter Integration Service runs in safe mode: Task Run workflows. Operating Mode 255 . When you perform maintenance on a PowerCenter Integration Service. you can use safe mode to test changes to the paths for PowerCenter Integration Service files for PowerCenter Integration Service processes. stop.

¨ Workflow recovery. run in normal mode. set OperatingModeOnFailover to Safe. you stop a workflow and the PowerCenter Integration Service process fails over before the workflow stops. 2. For example. select a PowerCenter Integration Service. set OperatingMode to Safe. 6. the workflow is not recovered while the PowerCenter Integration Service runs in safe mode. The PowerCenter Integration Service recovers a workflow that failed over in safe mode when you change the operating mode from safe to normal. Note: When you change the operating mode on fail over from safe to normal. If the PowerCenter Integration Service process fails over. The PowerCenter Integration Service does not recover client requests when it fails over in safe mode. For example. You can recover the workflow after the resilience timeout for the PowerCenter Integration Service expires. 5. 3. it recovers the client requests. or run in safe or normal mode on failover. The PowerCenter Integration Service starts in the selected mode. the workflow fails over and the PowerCenter Integration Service recovers it. Restart the PowerCenter Integration Service. Click OK. RELATED TOPICS: ¨ “Managing High Availability for the PowerCenter Integration Service” on page 145 Configuring the PowerCenter Integration Service Operating Mode You can use the Administrator tool to configure the PowerCenter Integration Service to run in safe mode. ¨ Client request recovery. The service status at the top of the content pane indicates when the service has restarted. When you enable the PowerCenter Integration Service in normal mode. 7. set OperatingMode to Normal. To run the service in safe mode on failover. click the Domain tab. set OperatingModeOnFailover to Normal. 4. To run the service in safe mode. In the Administrator tool. The PowerCenter Integration Service process does not recover your request to stop the workflow when the workflow fails over. Go to the Operating Mode Configuration section and click Edit. the change takes effect immediately. When you enable the PowerCenter Integration Service in normal mode. In the Navigator. To run the PowerCenter Integration Service in normal mode. To run the service in normal mode on failover.The PowerCenter Integration Service does not recover workflows when it runs in safe mode or when the operating mode changes from normal to safe. 1. Click the Properties view. You can manually recover the workflow if the workflow fails over in safe mode. you must have the high availability option. 256 Chapter 18: PowerCenter Integration Service . depending on the recovery strategy for the workflow. you configure a workflow for automatic recovery and you configure the PowerCenter Integration Service to fail over in safe mode. To configure the operating mode on failover. 8.

¨ HTTP proxy properties. Configure the connection to the HTTP proxy server. The following table describes the general properties: Property Name Description Description Name of the PowerCenter Integration Service. PowerCenter Integration Service Properties 257 . restart the PowerCenter Integration Service.PowerCenter Integration Service Properties Use the Administrator tool to configure the following PowerCenter Integration Service properties: ¨ General properties. You can configure a PowerCenter Integration Service to run on a grid or on nodes. To edit the general properties. select the PowerCenter Integration Service in the Navigator. Configure the source and target database properties. such the maximum number of connections. To view the properties. Edit the section General Properties section. To apply changes. You must create the grid before you can select the grid. Assign a license and configure the PowerCenter Integration Service to run on a grid or nodes. You must have the server grid option to run the PowerCenter Integration Service on a grid. Description of the PowerCenter Integration Service. To modify the properties. If you have only one node and it becomes unavailable. Configure the configuration properties. choose one or more PowerCenter Integration Service process nodes. If you configure the PowerCenter Integration Service to run on nodes. General Properties The amount of system resources that the PowerCenter Integration Services uses depends on how you set up the PowerCenter Integration Service. you can run the PowerCenter Integration Service on multiple nodes. ¨ Custom properties. the PowerCenter Integration Service distributes workflow tasks and session threads across multiple nodes. When you use a grid. the domain cannot accept service requests. You can override some of the custom properties at the session level. You can increase performance when you run sessions and workflows on a grid. With the high availability option. ¨ Configuration properties. and then click the Properties view. To run the service on multiple nodes. Configure advanced properties that determine security and control the behavior of sessions and logs ¨ Operating mode configuration. select the grid. Use custom properties only if Informatica Global Customer Support instructs you to. select the PowerCenter Integration Service in the Navigator and click Properties view. ¨ Advanced properties. such as the data display format. edit the section for the property you want to modify. Set the PowerCenter Integration Service to start in normal or safe mode and to fail over in normal or safe mode. Custom properties include properties that are unique to your Informatica environment or that apply in special cases. ¨ Compatibility and database properties. You can view the system resource usage of the PowerCenter Integration Service using the PowerCenter Workflow Monitor. Set the values for the PowerCenter Integration Service variables. choose the primary and backup nodes. ¨ PowerCenter Integration Service properties. If you choose to run the PowerCenter Integration Service on a grid. and configure properties to enable compatibility with previous versions of PowerCenter. A PowerCenter Integration Service has no custom properties when you create it.

Required if you run the PowerCenter Integration Service on nodes and you specify at least one backup node. Primary node on which the PowerCenter Integration Service runs. To edit the service properties. Name of the grid on which the PowerCenter Integration Service runs. To apply changes. If multiple email addresses are associated with a single user. Use this variable for the Email User Name attribute for failure email. $PMSuccessEmailUser Service variable that specifies the email address of the user to receive email messages when a session completes successfully. Primary Node Backup Node PowerCenter Integration Service Properties You can set the values for the service variables at the service level. The following table describes the service properties: Property DataMovementMode Description Mode that determines how the PowerCenter Integration Service handles character data. the PowerCenter Integration Service recognizes multibyte character sets as defined by supported code pages.Property License Assign Grid Description License assigned to the PowerCenter Integration Service. configure the properties for the session or workflow. and then click the Properties view. Use ASCII mode when all sources and targets are 7-bit ASCII or EBCDIC character sets. If the primary node becomes unavailable. Indicates whether the PowerCenter Integration Service runs on a grid or on nodes. You can select any node in the domain. Available if you have the high availability option and you run the PowerCenter Integration Service on nodes. If the Integration Service runs on UNIX. The PowerCenter Integration Service does not expand this variable when you use it for any other email type. You can override some of the PowerCenter Integration Service variables at the session level or workflow level. If multiple email addresses are associated with a single user. 258 Chapter 18: PowerCenter Integration Service . Edit the PowerCenter Integration Service Properties section. you can enter multiple email addresses separated by a comma. Required if you run the PowerCenter Integration Service on a grid. messages are sent to all of the addresses. the PowerCenter Integration Service runs on a backup node. Use Unicode mode when sources or targets use 8-bit or multibyte character sets and contain character data. Use this variable for the Email User Name attribute for success email. select the PowerCenter Integration Service in the Navigator. Default is ASCII. You can select multiple nodes as backup nodes. Backup node on which the PowerCenter Integration Service can run on. $PMFailureEmailUser Service variable that specifies the email address of the user to receive email messages when a session fails to complete. In Unicode mode. To override the properties. you can enter multiple email addresses separated by a semicolon or use a distribution list. the PowerCenter Integration Service recognizes 7-bit ASCII and EBCDIC characters and stores each character in a single byte. messages are sent to all of the addresses. If the Integration Service runs on Windows. In ASCII mode. restart the PowerCenter Integration Service.

you can enter multiple email addresses separated by a semicolon or use a distribution list. If you want to stop the session on errors. Writes ERROR code messages to the log. INFO. Specify one of the following message levels: . Limit on Resilience Timeouts Number of seconds that the service holds on to resources for resilience purposes.Debug. Timestamp Workflow Log Messages Appends a timestamp to messages that are written to the workflow log. and transformation. The PowerCenter Integration Service maintains an independent error count for each source. WARNING. and logs. the value is derived from the domain-level settings.Property Description If the Integration Service runs on UNIX. and then click the Properties view. Writes INFO. $PMWorkflowLogCount Service variable that specifies the number of workflow logs the PowerCenter Integration Service archives for the workflow. non-fatal errors do not cause the session to stop. $PMSessionLogCount Service variable that specifies the number of session logs the PowerCenter Integration Service archives for the session. target. and ERROR code messages to the log. inclusive. Writes DEBUG. This property places a restriction on clients that connect to the service. Minimum value is 0. writer. The PowerCenter Integration Service does not expand this variable when you use it for any other email type. Edit the Advanced Properties section. Minimum value is 0. Any resilience timeouts that exceed the limit are cut off at the limit. TRACE. INFO. PowerCenter Integration Service Properties 259 .592. Valid values are between 0 and 2.000.Warning. Default is 0. Writes WARNING and ERROR code messages to the log. If you use the default setting 0. you can enter multiple email addresses separated by a comma. $PMSessionErrorThreshold Service variable that specifies the number of non-fatal errors the PowerCenter Integration Service allows before failing the session. These messages are written to the Log Manager and log files. Default is No. .592. If blank. . and DTM errors. the value is derived from the domain-level settings. Writes TRACE. Defaults to 0. . Default is 0. WARNING. Valid values are between 0 and 2. WARNING. inclusive.000. Default is INFO. .Tracing. Use to configure the Stop On option in the session properties. select the PowerCenter Integration Service in the Navigator.Error. To edit the advanced properties. Non-fatal errors include reader. If blank. enter the number of non-fatal errors you want to allow before stopping the session. Default is 180 seconds.Information. and ERROR code messages to the log. Advanced Properties You can configure the properties that control the behavior of PowerCenter Integration Service security. Resilience Timeout Number of seconds that the service tries to establish or reestablish a connection to another service. If the Integration Service runs on Windows. sessions. The following table describes the advanced properties: Property Error Severity Level Description Level of error logging for the domain. Default is 180 seconds. and ERROR code messages to the log.

Level of run-time information stored in the repository. This option is available when you configure the PowerCenter Integration Service to run in Unicode mode. task details. When running in Unicode data movement mode. Disable this option to write to the logs using the PowerCenter Integration Service code page. When you modify a dependent object. Run sessions impacted by dependency updates Runs sessions that are impacted by dependency updates. To apply changes.provider. Use Operating System Profiles Enables the use of operating system profiles. Default is Yes. restart the PowerCenter Integration Service. Enable this option to cause the Load Balancer to ignore task resource requirements. Used when the PowerCenter Integration Service runs on a grid. PowerCenter Integration Service does not store any session or workflow run-time information in the repository. Persist Run-time Statistics to Repository 260 Chapter 18: PowerCenter Integration Service . When running in ASCII data movement mode.unix.crypto. Default is Normal. source and target statistics.Property Allow Debugging LogsInUTF8 Description Allows you to run debugger sessions from the Designer. You can select this option if the PowerCenter Integration Service runs on UNIX.UnixJCE. Ignored when the PowerCenter Integration Service runs on a node. It distributes tasks to available nodes whether or not the nodes have the resources required to run the tasks. PowerCenter Integration Service stores workflow details. session statistics. the parent object can become invalid.keystore JCEProvider Enter the JCEProvider class name to support NTLM authentication. and performance details in the repository. The PowerCenter client marks a session with a warning if the session is impacted.keystore ClientStore Enter the value for ClientStore using the following syntax: <path>/<filename > For example: . ./Certs/client. Enter the value for TrustStore using the following syntax: <path>/<filename > TrustStore For example: ./Certs/trust. . It distributes tasks to nodes that have the required resources. the PowerCenter Integration Service fails the session if it detects errors.Verbose. PowerCenter Integration Service stores workflow details. Disable this option to cause the Load Balancer to match task resource requirements with node resource availability when distributing tasks. To store session performance details in the repository. default is No. Writes to all logs using the UTF-8 character set. session statistics. the PowerCenter Integration Service does not run impacted sessions. Default is Yes.None. Specify one of the following levels: . task details. By default. you must also configure the session to collect performance details and write them to the repository. partition details. and source and target statistics in the repository. default is Yes. At run time. For example: com. IgnoreResourceRequirements Ignores task resource requirements when distributing tasks across the nodes of a grid.Normal.

the PowerCenter Integration Service flushes the recovery data after each commit interval or user-defined commit. Compatibility and Database Properties You can configure properties to reinstate previous Informatica behavior or to configure database behavior. . You can set the service to run in normal mode to allow users full access or in safe mode to limit access. the PowerCenter Integration Service flushes the recovery data after each flush latency interval. Use this property to prevent data loss if the PowerCenter Integration Service is not able to write recovery data for the recovery file to the disk. update.Property Description The PowerCenter Workflow Monitor shows run-time statistics stored in the repository. Required if you enable session recovery. PowerCenter Integration Service does not flush recovery data.No. Disable this option to treat null values as NULL and perform aggregate calculations based on the Update Strategy transformation.Auto. PowerCenter Integration Service flushes recovery data for all real-time sessions with a JMS or WebSphere MQ source and a non-relational target. For all other sessions. You can also set how the services operates when it fails over to another node.Yes. The following table describes the operating mode properties: Property OperatingMode OperatingModeOnFailover Description Mode in which the PowerCenter Integration Service runs. The PowerCenter Integration Service treats null values as zeros in aggregate calculations and performs aggregate calculations before flagging records for insert.5. Note: If you select Yes or Auto. select the PowerCenter Integration Service in the Navigator. PowerCenter Integration Service flushes recovery data for all sessions. PowerCenter Integration Service Properties 261 . Operating mode of the PowerCenter Integration Service when the service process fails over to another node. Flush Session Recovery Data Flushes session recovery data for the recovery file from the operating system buffer to the disk. and then click the Properties view > Compatibility and Database Properties > Edit. Select this option if you have highly available external systems or if you need to optimize performance. This overrides both Aggregate treat nulls as zero and Aggregate treat rows as insert. Default is Auto. To edit the compatibility and database properties. delete. Operating Mode Configuration The operating mode determines how much user access and workflow activity the PowerCenter Integration Service allows when runs. . or reject in Update Strategy expressions. For real-time sessions. Specify one of the following levels: . The following table describes the compatibility and database properties: Property PMServer3XCompatibility Description Handles Aggregator transformations as it did in version 3. you might impact performance.

Max Lookup SP DB Connections Max Sybase Connections Maximum number of connections to a Sybase ASE database when you start a session. the PowerCenter Integration Service uses the update strategy of rows when it performs aggregate calculations. Default is No. Multiple input group transformations require the PowerCenter Integration Service to read sources concurrently. but the database user does not have permission for the number of connections required by the session. AggregateTreatRowAsInsert When enabled. This can result in decreased performance. If the number of connections required by the session is greater than this value. Default is 100. You cannot. Maximum number of connections to a lookup or stored procedure database when you start a session.You configure any Joiner transformation with transaction level transformation scope. DateHandling40Compatibility Handles dates as in version 4. Disable this option to treat null values as NULL in aggregate calculations.Property Description Default is No.5.0 behavior. This option ignores sorted input option of the Aggregator transformation. 262 Chapter 18: PowerCenter Integration Service . Minimum value is 100. however. the PowerCenter Integration Service processes the detail pipelines sequentially. TreatCHARasCHARonRead If you have PowerExchange for PeopleSoft. JoinerSourceOrder6xCompatibility Processes master and detail pipelines sequentially as it did in versions prior to 7. If the number of connections needed exceeds this value. Default is No. Disable this option to handle dates as defined in the current version of PowerCenter. Disable this option to process the master and detail pipelines concurrently. Maximum value is 2147483647. use this option for PeopleSoft sources on Oracle. the session fails. the session fails. session threads must share connections. Enable this option to revert to version 4. Date handling significantly improved in version 4. AggregateTreatNullAsZero Treats null values as zero in Aggregator transformations. Default is No. such as the Custom transformation. the PowerCenter Integration Service ignores the update strategy of rows when it performs aggregate calculations. When the target load order group contains multiple Joiner transformations.0. When disabled. If blank. The PowerCenter Integration Service fails sessions when the mapping meets any of the following conditions: . If the PowerCenter Integration Service allows an unlimited number of connections. Default is 0.The mapping contains a multiple input group transformation. . use it for PeopleSoft lookup tables on Oracle or PeopleSoft sources on Microsoft SQL Server.0. The PowerCenter Integration Service processes all data from the master pipeline before it processes the detail pipeline. Default is No. the PowerCenter Integration Service allows an unlimited number of connections to the lookup or stored procedure database. Minimum value is 0.

000. and then click the Properties view > Configuration Properties > Edit. such as whether to enforce code page compatibility. Default is 10. NumOfDeadlockRetries Number of times the PowerCenter Integration Service retries a target write on a database deadlock. OutputMetaDataForFF Writes column headers to flat file targets. Default is No. ExportSessionLogLibName Name of an external shared library to handle session event messages. Maximum value is 1. Maximum value is 2147483647. select the PowerCenter Integration Service in the Navigator. shared libraries have a file name extension of . If you specify a shared library and the PowerCenter Integration Service encounters an error when loading the library or getting addresses to the functions in the shared library. Enable this option if you specify Database Partitioning for a non-DB2 target. If the number of connections required by the session is greater than this value. To edit the configuration properties. Typically.000. The following table describes the configuration properties: Property XMLWarnDupRows Description Writes duplicate row warnings and duplicate rows for XML targets to the session log. the PowerCenter Integration Service retries the target write immediately. the PowerCenter Integration Service will PowerCenter Integration Service Properties 263 . Configuration Properties You can configure session and miscellaneous properties. starting with the # symbol. Default is 0. The PowerCenter Integration Service writes the target definition port names to the flat file target in the first line. Minimum value is 100. Default is No. CreateIndicatorFiles Creates indicator files when you run a workflow with a flat file target.sl. Minimum value is 0. TreatDBPartitionAsPassThrough Uses pass-through partitioning for non-DB2 targets when the partition type is Database Partitioning. The library name you specify can be qualified with an absolute path. the PowerCenter Integration Service fails the session. Otherwise. If you do not provide the path for the shared library. then the session will fail.Property Max MSSQL Connections Description Maximum number of connections to a Microsoft SQL Server database when you start a session.dll. DeadlockSleep Number of seconds before the PowerCenter Integration Service retries a target write on database deadlock. Minimum value is 10. In UNIX. Maximum value is 2147483647. shared libraries in Windows have a file name extension of .000. Default is No. the session fails. Default is 100. If set to 0 seconds. Default is Yes.

To edit the HTTP proxy properties. Default is DY MON DD HH24:MI:SS YYYY. When you choose Low. and session sort order selection. Maximum value is 2147483647.The PowerCenter Integration Service has not issued a commit. The PowerCenter Integration Service may commit to the target before or after the configured commit interval. Option disabled if you run the PowerCenter Integration Service in ASCII data movement mode. the PowerCenter Integration Service treats them as equal. If you configure the timeout to be 0 or a negative number. the result is NULL. WriterWaitTimeOut In target-based commit mode. the amount of time in seconds the writer remains idle before it issues a commit when the following conditions are true: . The PowerCenter Integration Service evaluates null values as greater than non-null values in comparison expressions. the PowerCenter Integration Service uses the default date display format. MSExchangeProfile Microsoft Exchange profile used by the Service Start Account to send postsession email.Property Description locate the shared library based on the library path environment variable specific to each platform. stored procedure and lookup database code page selection. The PowerCenter Integration Service evaluates null values as less than non-null values in comparison expressions. Default is Yes. . If both operands are NULL. If the date display format is invalid. 264 Chapter 18: PowerCenter Integration Service . comparison expressions never result in NULL. The PowerCenter Integration Service performs data code page validation in Unicode data movement mode only.Low. Default is 60.Null. the PowerCenter Integration Service evaluates them as equal. HTTP Proxy Properties You can configure properties for the HTTP proxy server for Web Services and the HTTP transformation. If both operands are NULL. Specify one of the following options: . Minimum value is 60. Option available if you run the PowerCenter Integration Service in Unicode data movement mode. If either operand is NULL. select the PowerCenter Integration Service in the Navigator. Default is NULL. The PowerCenter Integration Service validates the date format you enter.The PowerCenter Integration Service has written data to the target. . comparison expressions never result in NULL. The Service Start Account must be set up as a Domain account to use this feature. When you choose High. The PowerCenter Integration Service evaluates null values as NULL in comparison expressions. the PowerCenter Integration Service defaults to 60 seconds.High. TreatNullInComparisonOperatorsAs Determines how the PowerCenter Integration Service evaluates null values in comparison operations. . Date format the PowerCenter Integration Service uses in log entries. DateDisplayFormat ValidateDataCodePages Enforces data code page compatibility. Disable this option to lift restrictions for source and target data code page selection. and click the Properties view > HTTP Proxy Properties > Edit.

HttpProxyPassword HttpProxyDomain Custom Properties Custom properties include properties that are unique to your environment or that apply in special cases. Operating System Profiles By default. When you configure the PowerCenter Integration Service to use operating system profiles. Authenticated user name for the HTTP proxy server. The operating system profile contains the operating system user name. Operating System Profiles 265 . For example. When you configure operating system profiles on UNIX. This must be a number. the PowerCenter Integration Service process runs all workflows using the permissions of the operating system user that starts Informatica Services. This is required if the proxy server requires authentication. Port number of the HTTP proxy server. the PowerCenter Integration Service process runs workflows with the permission of the operating system user you define in the operating system profile. The PowerCenter Integration Service stores the output files for workflow A in a location specified in the $PMRootDir service process variable that the profile can access. assign the profile to a repository folder or assign the profile to a workflow when you start a workflow. you must enable setuid for the file system that contains the Informatica installation. Configure the operating system user that the PowerCenter Integration Service uses to run workflows. The PowerCenter Integration Service writes output files to a single shared location specified in the $PMRootDir service process variable. The user that runs workflow A must also have permissions to use operating system profile Sales. The operating system user must have access to the directories you configure in the profile and the directories the PowerCenter Integration Service accesses at run time. you assign operating system profile Sales to workflow A. You can use operating system profiles for a PowerCenter Integration Service that runs on UNIX.The following table describes the HTTP proxy properties: Property HttpProxyServer HttpProxyPort HttpProxyUser Description Name of the HTTP proxy server. service process variables. Use custom properties only at the request of Informatica Global Customer Support. Password for the authenticated user. To use an operating system profile. A PowerCenter Integration Service does not have custom properties when you initially create it. and environment variables. Operating System Profile Components Configure the following components in an operating system profile: ¨ Operating system user name. You must have permission on the operating system profile to assign it to a folder or workflow. This is required if the proxy server requires authentication. Domain for authentication. To manage permissions for operating system profiles. go to the Security page of the Administrator tool.

pmimpprocess was not configured. Enable operating system profiles in the advanced properties section of the PowerCenter Integration Service properties. Or. pmimpprocess is a tool that the DTM process. 266 Chapter 18: PowerCenter Integration Service . restart Informatica services. Configure service process variables in the operating system profile to specify different output file locations based on the profile assigned to the workflow. At the command prompt. On UNIX. switch to the following directory: <Informatica installation directory>/server/bin Enter the following information at the command line to log in as the administrator user: su <administrator user name> For example. remount the file system with setuid enabled. select Confgure operating system profiles 6. Configure pmimpprocess on every node where the PowerCenter Integration Service runs. Enter the following commands to set the setuid bit: chmod +g chmod +s pmimpprocess pmimpprocess Troubleshooting Operating System Profiles After I selected Use Operating System Profiles. 2. Set umask to 000 on every node where the PowerCenter Integration Service runs. Assign permissions on operating system profiles to users or groups. if the administrator user name is root enter the following command: su root 3. complete the following steps: 1. You can enable operating system profiles on PowerCenter Integration Services that run on UNIX. To configure pmimpprocess: 1. ¨ Environment variables. You can assign operating system profiles to repository folders or to a workflow. 2. command tasks. the PowerCenter Integration Service failed to start. On the Security tab Actions menu. Configure permissions for users to use operating system profiles.¨ Service process variables. 5. Configure environment variables that the PowerCenter Integration Services uses at run time. To use operating system profiles. If necessary. Enter the following commands to set the owner and group to the administrator user: chown <administrator user name> pmimpprocess chgrp <administrator user name> pmimpprocess 4. and parameter files use to switch between operating system users. 3. Configuring Operating System Profiles To use operating system profiles to run workflows. The PowerCenter Integration Service will not start if operating system profiles is enabled on Windows or a grid that includes a Windows node. 4. 7. you must set the owner and group of pmimpprocess to administrator and enable the setuid bit for pmimpprocess. ¨ Permissions. verify that setuid is enabled on the file system that contains the Informatica installation. Create the operating system profiles on the Security page of the Administrator tool. To apply changes.

you can view the PowerCenter Integration Service process nodes on the Processes tab. restart the PowerCenter Integration Service. When you select a PowerCenter Integration Service process. To apply changes. restart the PowerCenter Integration Service. For example. and then click the Properties view > Associated Repository Properties > Edit. User name to access the repository. When you update or choose a new repository. The Security Domain field appears when the Informatica domain contains an LDAP security domain. you need to update the connection information if the repository is moved to another database. To configure the properties. restart the PowerCenter Integration Service. To apply changes. the detail panel displays the properties for the service process. Associated Repository for the PowerCenter Integration Service 267 . you specify the repository associated with the PowerCenter Integration Service. select the PowerCenter Integration Service in the Domain tab of the Administrator tool. To apply changes. you must specify the PowerCenter Repository Service and the user account used to access the repository.Associated Repository for the PowerCenter Integration Service When you create the PowerCenter Integration Service. The following table describes the associated repository properties: Property Associated Repository Service Repository User Name Description PowerCenter Repository Service name to which the PowerCenter Integration Service connects. You may need to choose a different repository when you move from a development repository to a production repository. Password for the user. To edit the associated repository properties. The Administrator tool lists the PowerCenter Repository Services defined in the same domain as the PowerCenter Integration Service. Security domain for the user. You can change the following properties to configure the way that a PowerCenter Integration Service process runs on a node: ¨ General properties ¨ Custom properties ¨ Environment variables General properties include the code page and directories for PowerCenter Integration Service files and Java components. restart the PowerCenter Integration Service. select the PowerCenter Integration Service in the Administrator tool and click the Processes view. When you select the PowerCenter Integration Service in the Administrator tool. To apply changes. You may need to change the repository connection information. Repository Password Security Domain PowerCenter Integration Service Processes The PowerCenter Integration Service can run each PowerCenter Integration Service process on a different node.

scheduled tasks. all codes pages for the PowerCenter Integration Service process nodes must be compatible. The syntax for $PMRootDir is different for Windows and UNIX: ¨ On Windows. and completed and running processes. the installation program creates a set of PowerCenter Integration Service directories in the server \infa_shared directory. Each PowerCenter Integration Service can use a separate shared location. For example: C:\Informatica###BOT_TEXT###lt;infa_vesion>\server\infa_shared ¨ On UNIX: Enter an absolute path beginning with a slash. RELATED TOPICS: ¨ “Understanding Globalization” on page 472 Directories for PowerCenter Integration Service Files PowerCenter Integration Service files include run-time files. cache files. input files. set the $PMSessionLogDir service process variable to $PMRootDir/SessLogs. state of operation files. the field displays code pages that are a subset of the associated PowerCenter Repository Service code page. colon. The PowerCenter Integration Service process uses run-time files to run workflows and sessions. and backslash. The node where the process runs uses the code page when it extracts. The state of operations includes information such as the active service requests. the operating system user specified in the profile must have access to the run-time files. all PowerCenter Integration Service processes associated with a PowerCenter Integration Service must use the same shared directories for PowerCenter Integration Service files. For example. The code page for each PowerCenter Integration Service process node must be a subset of the repository code page. The PowerCenter Integration Service creates files to store the state of operations for the service. you must select an associated repository for the PowerCenter Integration Service. Set the root directory in the $PMRootDir service process variable. If the service fails. By default. You can specify an absolute directory for the service process variables. Configuring $PMRootDir When you configure the PowerCenter Integration Service process variables. Make sure all directories specified for service process variables exist before running a workflow. you can use a different code page for each PowerCenter Integration Service process node. enter a path beginning with a drive letter. Before you can select a code page for a PowerCenter Integration Service process. or loads data. You can set the shared location for these directories by configuring the service process variable $PMRootDir to point to the same location for each PowerCenter Integration Service process.Code Pages You must specify the code page of each PowerCenter Integration Service process node. transforms. If the PowerCenter Integration Service uses operating system profiles. Run-time files include parameter files. 268 Chapter 18: PowerCenter Integration Service . When you configure the PowerCenter Integration Service to run on a grid or a backup node. However. the PowerCenter Integration Service can restore the state and recover operations from the point of interruption. and output files. For example: /Informatica/<infa_vesion>/server/infa_shared You can use $PMRootDir to define subdirectories for other service process variable values. Configuring Service Process Variables for Multiple Nodes When you configure the PowerCenter Integration Service to run on a grid or a backup node. you specify the paths for the root directory and its subdirectories. When you edit this property. and session log files.

if you have a primary and a backup node for the PowerCenter Integration Service. both nodes must use the same drive. This is the root directory for other service process variables. the absolute path to the shared location must also be identical. Root directory accessible by the node. recovery fails when nodes use the following drives for the storage directory: ¨ Mapped drive on node1: F:\shared\Informatica###BOT_TEXT###lt;infa_version>\infa_shared\Storage ¨ Mapped drive on node2: G:\shared\Informatica###BOT_TEXT###lt;infa_version>\infa_shared\Storage Recovery also fails when nodes use the following drives for the storage directory: ¨ Mounted drive on node1: /mnt/shared/Informatica/<infa_version>/infa_shared/Storage ¨ Mounted drive on node2: /mnt/shared_filesystem/Informatica/<infa_version>/infa_shared/Storage To use the mapped or mounted drives successfully. It cannot include the following special characters: *?<>“|. Define the other service process variables within each operating system profile. It cannot include the following special characters: PowerCenter Integration Service Processes 269 . For example. the $PMRootDir is not updated to the upgraded service version installation directory.Configure service process variables with identical absolute paths to the shared directories on each node that is configured to run the PowerCenter Integration Service. Directories for Java Components You must specify the directory containing the Java components. When you upgrade the PowerCenter Integration Service. The PowerCenter Integration Service uses the Java components for the following PowerCenter components: ¨ Custom transformation that uses Java code ¨ Java transformation ¨ PowerExchange for JMS ¨ PowerExchange for Web Services ¨ PowerExchange for webMethods General Properties The following table describes the general properties: Property Codepage $PMRootDir Description Code page of the PowerCenter Integration Service process node. You configure $PMStorageDir in the PowerCenter Integration Service properties and the operating system profile. define absolute directory paths for $PMWorkflowLogDir and $PMStorageDir in the PowerCenter Integration Service properties. Configuring Service Process Variables for Operating System Profiles When you use operating system profiles. Default is <Installation_Directory>\server\infa_shared. If you use a mounted drive or a mapped drive. The PowerCenter Integration Service saves workflow recovery files to the $PMStorageDir configured in the PowerCenter Integration Service properties and saves the session recovery files to the $PMStorageDir configured in the operating system profile. The installation directory is based on the service version of the service that you created. $PMSessionLogDir Default directory for session logs.

It cannot include the following special characters: *?<>“|. Default is $PMRootDir/Cache.Property Description *?<>“|. Default is $PMRootDir/LkpFiles. $PMWorkflowLogDir Default directory for workflow logs. It cannot include the following special characters: *?<>“|. These files store the state of each workflow and session operation. $PMExtProcDir Default directory for external procedures. $PMTempDir Default directory for temporary files. You can increase performance when the cache directory is a drive local to the PowerCenter Integration Service process. $PMBadFileDir Default directory for reject files. It cannot include the following special characters: *?<>“|. You can set the classpath to any JAR files you need to run a session that require java components. For more information. $PMTargetFileDir Default directory for target files. $PMCacheDir Default directory for index and data cache files. Default is $PMRootDir/ExtProc. Default is $PMRootDir/Temp. The PowerCenter Integration Service uses these files for recovery if you have the high availability option or if you enable a workflow for recovery. Minimum amount of memory the Java SDK uses during a session. If the session fails due to a lack of memory. The PowerCenter Integration Service appends the values you set to the system CLASSPATH. you may want to increase this value. $PMLookupFileDir Default directory for lookup files. It cannot include the following special characters: *?<>“|. $PMStorageDir Default directory for state of operation files. It cannot include the following special characters: *?<>“|. Do not use a mapped or mounted drive for cache files. It cannot include the following special characters: *?<>“|. It cannot include the following special characters: *?<>“|. see “Directories for Java Components” on page 269. It cannot include the following special characters: *?<>“|. Java SDK ClassPath Java SDK classpath. It cannot include the following special characters: *?<>“|. $PMSourceFileDir Default directory for source files. Default is $PMRootDir/SrcFiles. Default is $PMRootDir/WorkflowLogs. Default is $PMRootDir/BadFiles. Java SDK Minimum Memory 270 Chapter 18: PowerCenter Integration Service . Default is $PMRootDir/TgtFiles. Default is $PMRootDir/Storage. Default is $PMRootDir/SessLogs.

Java SDK Maximum Memory Maximum amount of memory the Java SDK uses during a session. environment variables configured in the operating system profile override the environment variables set in the general properties for the PowerCenter Integration Service process. You might want to configure the code page environment variable for a PowerCenter Integration Service process for the following reasons: ¨ A PowerCenter Integration Service and PowerCenter Repository Service running on the node require different database client code pages. For optimal performance. Then add the environment variable to the PowerCenter Integration Service process properties and set the value to UTF-8. you have a Shift-JIS repository that requires that the code page environment variable be set to Shift-JIS. For example. For example. the PowerCenter Integration Service running in ASCII mode requires that the code page environment variable be set to 7-bit ASCII. If the PowerCenter Integration Service uses operating system profiles. Then add the environment variable to the properties of the PowerCenter Integration Service process running in ASCII mode and set the value to 7-bit ASCII. A PowerCenter Integration Service process has no custom properties when you create it. You can configure a PowerCenter Integration Service process to use a different value for the database client code page environment variable than the value set for the node. the PowerCenter Integration Service reads from and writes to databases using the UTF-8 code page. and IBM DB2 uses DB2CODEPAGE. Use custom properties only at the request of Informatica Global Customer Support. Set the database client path environment variable for the PowerCenter Integration Service process if the PowerCenter Integration Service process requires a different database client than another PowerCenter Integration Service process that is running on the same node. Custom properties include properties that are unique to your Informatica environment or that apply in special cases. All PowerCenter Integration Services and PowerCenter Repository Services that run on this node use the same environment variable. You can configure each PowerCenter Integration Service process to use a different value for the database client environment variable. The PowerCenter Integration Service requires that the code page environment variable be set to UTF-8. you have one PowerCenter Integration Service running in Unicode mode and another running in ASCII mode on the same node. Default is 64 MB. Oracle uses NLS_LANG. For example. Custom Properties You can configure custom properties for each node assigned to the PowerCenter Integration Service. The PowerCenter Integration Service running in Unicode mode requires that the code page environment variable be set to UTF-8. PowerCenter Integration Service Processes 271 . Set the environment variable on the node to UTF-8.Property Description Default is 32 MB. If the session fails due to a lack of memory. For example. you may want to increase this value. Environment Variables The database client path on a node is controlled by an environment variable. The database client code page on a node is usually controlled by an environment variable. the service version of each PowerCenter Integration Service running on the node requires a different database client version. ¨ Multiple PowerCenter Integration Services running on the node use different data movement modes. However. Set the environment variable on the node to Shift-JIS.

2. create the grid object and assign nodes to the grid. Configure the PowerCenter Integration Service to run on a grid. The description cannot exceed 765 characters. To run a workflow or session on a grid. you configure a workflow to run on the PowerCenter Integration Service assigned to a grid. you improve scalability and performance by distributing session threads to multiple DTM processes running on nodes in the grid. It also cannot contain spaces or the following special characters: `~%^*+={}\. Configure the PowerCenter Integration Service processes for the nodes in the grid.. Create a grid and assign nodes to the grid. complete the following tasks: 1. If the PowerCenter Integration Service uses operating system profiles. Creating a Grid To create a grid. Location in the Navigator. and configure the PowerCenter Integration Service to run on a grid. You assign resources to a node to allow the PowerCenter Integration Service to match the resources required to run a task or session thread with the resources available on a node. 4. Assign resources to nodes. 3. It cannot exceed 128 characters or begin with @. create and configure the grid. you assign resources to nodes. all nodes on the grid must run on UNIX. 1. When you run a workflow on a grid. In the domain navigator of the Administrator tool. Click New > Grid. 3.<>|!()][ Description Description of the grid. When you run a session on a grid. You can assign a node to more than one grid. select the domain. The name is not case sensitive and must be unique within the domain. Edit the following properties: Property Name Description Name of the grid. such as: DomainName/ProductionGrids Nodes Path Configuring the PowerCenter Integration Service to Run on a Grid You configure the PowerCenter Integration Service by assigning the grid to the PowerCenter Integration Service. 2.:'"/?. To configure a grid. you improve scalability and performance by distributing Session and Command tasks to service processes running on nodes in the grid. 272 Chapter 18: PowerCenter Integration Service . The Create Grid window appears. Select nodes to assign to the grid. After you configure the grid and PowerCenter Integration Service.Configuration for the PowerCenter Integration Service Grid A grid is an alias assigned to a group of nodes that run sessions and workflows.

When you configure the session. Verify that the shared storage location is accessible to each node in the grid. Select the grid you want to assign to the PowerCenter Integration Service. Point to the same Java directory to ensure that java components are available to objects that access Java. The Load Balancer dispatches the Session task to a node that has the parameter file resource. For example. You can configure the PowerCenter Integration Service to check resources. You create a resource for the parameter file and make it available to one or more nodes. Complete the following process to configure the service processes: 1. Configuring the PowerCenter Integration Service Processes When you run a session or a workflow on a grid. The operating system user must have access to the $PMRootDir configured in the operating system profile on every node in the grid. a service process runs on each node in the grid. and select Grid. The tab displays the service process for each node assigned to the grid. When you do this. Click the Processes tab. node names. 3. It must also have access to the directories and input files used by the PowerCenter Integration Service. Configure $PMRootDir to the shared location on each node in the grid. the operating system user must have access to the shared storage location. In the Administrator tool. To ensure consistent results.To assign the grid to a PowerCenter Integration Service: 1. Each service process running on a node must be compatible or configured the same. Configure $PMRootDir to point to the shared location. 4. Configuration for the PowerCenter Integration Service Grid 273 . the service process variables you define in the operating system profile override the service process variable setting for every node. Configure service process variables with identical absolute paths to the shared directories on each node in the grid. the Load Balancer matches the resources available to nodes in the grid with the resources required by the workflow. directories. ¨ Configure the service process. For accurate data movement and transformation. If the PowerCenter Integration Service uses operating system profiles. and operating system types required by a task. 2. you assign the parameter file resource as a required resource. 3. Edit the grid and node assignments. It dispatches tasks in the workflow to nodes where the required resources are available. Resources Informatica resources are the database connections. select the PowerCenter Integration Service Properties tab. complete the following tasks: ¨ Verify the shared storage location. if a session uses a parameter file. the setting for $PMCacheDir must be identical on each node in the grid. 2. If no node has the parameter file resource available. Select the PowerCenter Integration Service in the Navigator. such as Custom transformations that use Java coding. ¨ Directories for Java components. the session fails. Configure the following service process settings for each node in the grid: ¨ Code pages. verify that the code pages are compatible for each service process. If the PowerCenter Integration Service is not configured to run on a grid. Use the same code page for each node where possible. the Load Balancer ignores resource requirements. Configure the service process variables the same for each service process. If the PowerCenter Integration Service uses operating system profiles. it must run on a node that has access to the file. files. ¨ Service process variables. For example.

The Workflow Manager assigns connection resources to the session by default. Note: When you define a resource for a node. For example. or queue connection. You can view the resources available to all nodes in a domain on the Resources view of the domain. File/Directory User-defined Any resource for files or directories. Use custom resources for any other resources available to the node. 274 Chapter 18: PowerCenter Integration Service . The following table lists the types of resources you use in Informatica: Type Predefined/ User-Defined Predefined Description Connection Any resource installed with PowerCenter. such as a parameter file or a file server directory. Informatica creates predefined resources during installation. Predefined resources include the connections available on a node. A connection object may be a relational. you must verify that the resource is available to the node. all connection resources are available by default. disable the Oracle Application connections. external loader. It displays a checkmark when a resource is available for a node Assigning Connection Resources You can assign the connection resources available to a node in the Administrator tool. In the Administrator tool. 1. If the Load Balancer dispatches a task to a node where the required resources are not available.Resources for a node can be predefined or user-defined. such as database client version. such as a specific database client version. You define resources available to a node on the Resources tab of the node in the Administrator tool. You configure resources required by Session. application. You cannot disable or remove node name or operating system type resources. Disable the connection resources that are not available on the node. If the resource is not available and the PowerCenter Integration Service runs a task that requires the resource. Custom User-defined Any resource for all other resources available to the node. Operating System Type Predefined A resource for the type of operating system on the node. such as a plug-in or a connection object. click the Domain tab. a Session task requires a custom resource if it accesses a Custom transformation shared library or if it requires a specific database client version. Disable the connection resources that are not available to the node. Command. Node Name Predefined A resource for the name of the node. Command. A Session or Command task requires an operating system type resource if it must run a specific operating system. For example. or predefined Event-Wait task requires a node name resource if it must run on a specific node. FTP. When you create a node. Any Session task that reads from or writes to a relational database requires one or more connection resources. User-defined resources include file/directory and custom resources. if the node does not have Oracle client libraries. and operating system type. the task fails. all connection resources are available by default. and predefined Event-Wait tasks in the task properties. When you create a node. The Administrator tool displays a column for each node. node name. A Session. a Session task requires a file resource if it accesses a session parameter file. Use file/directory resources for parameter files or file server directories. the task fails. For example.

Use the following naming convention: resourcetype_description For example. In the Administrator tool. Configuration for the PowerCenter Integration Service Grid 275 . 5. click the Domain tab. click the Resources view. select a node. Select a resource type. the Load Balancer distributes the session assigned the sessionparamfile_sales1 resource to nodes that have the resource defined. 2. When you define a custom or file/directory resource. but the Integration Service to which the grid is assigned does not show the latest Integration Service processes. You assign the resource to a PowerCenter task or PowerCenter mapping object instance using this name. The resource name is a logical name that you create to identify the resource. 3. : / ? . 5. Click OK. In the contents panel. Enter a name for the resource.txt. click New Resource. and predefined Event-Wait tasks. It cannot exceed 128 characters or begin with @. To coordinate resource usage. Create a file resource for it named sessionparamfile_sales1 on each node that contains the file. The name is not case sensitive and must be unique within the domain. To coordinate resource usage. 7. It also cannot contain spaces or the following special characters: ` ~ % ^ * + = { } \ . 3. To define a custom or file/directory resource: 1. 4. On the Domain tab Actions menu. In the Navigator. multiple nodes in a grid contain a session parameter file called sales1. select a node. click the Resources view. click Enable Selected Resource or Disable Selected Resource. Command. Troubleshooting the Grid I changed the nodes assigned to the grid. . A workflow developer creates a session that uses the parameter file and assigns the sessionparamfile_sales1 file resource to the session. In the Navigator. On the Domain tab Actions menu. When the PowerCenter Integration Service runs the workflow on the grid.2. 4. you may want to use a naming convention for file/directory and custom resources. you can use a naming convention for file/directory and custom resources. select a resource and click Delete Selected Resource on the Domain tab Actions menu. Defining Custom and File/Directory Resources You can define custom and file/directory resources available to a node in the Administrator tool. In the contents panel. The workflow developer assigns resources required by Session. Click on a resource that you want to edit. The domain administrator defines resources available to nodes. < > |!()][ 6. Resource Naming Conventions Using resources with PowerCenter requires coordination and communication between the domain administrator and the workflow developer. To remove a custom or file/directory resource. you assign a resource name.

When the PowerCenter Integration Service runs on a grid. or to the node with the most available computing resources. All nodes in the grid appear as service processes for the Integration Service. It can dispatch tasks on a single node or across nodes. ¨ Service level. When you change the dispatch mode for a domain. the Load Balancer uses the CPU profile to rank the computing throughput of each CPU and bus architecture in a grid. 276 Chapter 18: PowerCenter Integration Service . The settings you configure for the domain apply to all PowerCenter Integration Services in the domain. reassign the grid to the Integration Service. It uses this value to ensure that more powerful nodes get precedence for dispatch. The Load Balancer checks one or more resource provision thresholds to determine if it can dispatch a task. the node appears in the grid. Load Balancer for the PowerCenter Integration Service The Load Balancer is a component of the PowerCenter Integration Service that dispatches tasks to PowerCenter Integration Service processes running on nodes in a grid. The dispatch mode determines how the Load Balancer dispatches tasks.When you change the nodes in a grid. If the Service Manager cannot update an Integration Service and the latest service processes do not appear for the Integration Service. the Load Balancer can compare the resources required by a task with the resources available on each node. You assign required resources in the task properties. all PowerCenter Integration Services in a domain use the same dispatch mode. You configure the following Load Balancer settings for each node: ¨ Resources. Updates the Integration Services to which the grid is assigned. You configure the dispatch mode in the domain properties. Service levels establish dispatch priority among tasks that are waiting to be dispatched. the Service Manager performs the following transactions in the domain configuration database: 1. The previous dispatch mode remains in effect until you restart the PowerCenter Integration Service. The Load Balancer checks different thresholds depending on the dispatch mode. You configure available resources using the Administrator tool or infacmd. in a round-robin fashion using node load metrics. Therefore. You can create different service levels that a workflow developer can assign to workflows. You can configure Load Balancer settings for the domain and for nodes in the domain. In adaptive dispatch mode. restart the Integration Service. 2. ¨ CPU profile. You can configure the Load Balancer to dispatch tasks in a simple round-robin fashion. you must restart each PowerCenter Integration Service in the domain. if you add a node. It matches task requirements with resource availability to identify the best PowerCenter Integration Service process to run a task. The Load Balancer dispatches tasks to nodes that have the required resources. If that does not work. You configure the following settings for the domain to determine how the Load Balancer dispatches tasks: ¨ Dispatch mode. Updates the grid based on the node changes. ¨ Resource provision thresholds. For example. You configure the dispatch mode for the domain. Configuring the Dispatch Mode The Load Balancer uses the dispatch mode to select a node to run a task.

if a resource-intensive task is first in the dispatch queue. This mode prevents overloading nodes when tasks have uneven computing requirements. It compares these statistics with the resource provision thresholds defined for the node. the Load Balancer dispatches tasks to nodes in a round-robin fashion. It checks all resource provision thresholds on each available node and excludes a node if dispatching a task causes the thresholds to be exceeded. It continues to evaluate nodes until it finds a node that can accept the task. the Load Balancer evaluates the next node. the Load Balancer evaluates the next node. It checks the Maximum Processes threshold on each available node and excludes a node if dispatching a task causes the threshold to be exceeded. If no statistics exist in the repository. Therefore. It dispatches the task to this node if dispatching the task causes none of the thresholds to be exceeded. ¨ Metric-based. Uses task statistics? No Yes Yes Uses CPU profile? No No Yes Allows bypass in dispatch queue? No No Yes Round-Robin Metric-Based Adaptive Round-Robin Dispatch Mode In round-robin dispatch mode. or if the node is out of free swap space. The Load Balancer does not bypass any tasks in the dispatch queue. the Load Balancer evaluates nodes in a round-robin fashion until it finds a node that can accept the task. if a resource intensive task is first Load Balancer for the PowerCenter Integration Service 277 . The Load Balancer checks the Maximum Processes resource provision threshold on the first available node. It continues to evaluate nodes until it finds a node that can accept the task. ¨ Adaptive. Therefore. It checks all resource provision thresholds on each available node and excludes a node if dispatching a task causes the thresholds to be exceeded. Checks all thresholds.The Load Balancer uses the following dispatch modes: ¨ Round-robin. If dispatching the task causes this threshold to be exceeded. The Load Balancer continues to evaluate nodes until it finds a node that can accept the task. The Load Balancer does not bypass any task in the dispatch queue. The Load Balancer ranks nodes according to current CPU availability. Checks all thresholds. the Load Balancer collects and stores statistics from the last three runs of the task. The Load Balancer checks the resource provision thresholds on the first available node. The Load Balancer evaluates nodes in a round-robin fashion. the Load Balancer uses the following default values: ¨ 40 MB memory ¨ 15% CPU The Load Balancer dispatches tasks for execution in the order the Workflow Manager or scheduler submits them. Metric-Based Dispatch Mode In metric-based dispatch mode. all other tasks with the same service level must wait in the queue until the Load Balancer dispatches the resource-intensive task. This mode prevents overloading nodes and ensures the best performance on a grid that is not heavily loaded. The Load Balancer dispatches tasks for execution in the order the Workflow Manager or scheduler submits them. It dispatches the task to this node if dispatching the task does not cause this threshold to be exceeded. If dispatching the task causes any threshold to be exceeded. This mode is the least compute-intensive and is useful when the load on the grid is even and the tasks to dispatch have similar computing requirements. The Load Balancer dispatches tasks to available nodes in a round-robin fashion. To determine whether a task can run on a particular node. The following table compares the differences among dispatch modes: Dispatch Mode Checks resource provision thresholds? Checks maximum processes.

RELATED TOPICS: ¨ “Service Level Management” on page 47 278 Chapter 18: PowerCenter Integration Service . all other tasks with the same service level must wait in the queue until the Load Balancer dispatches the resource intensive task. When multiple tasks are waiting in the dispatch queue. If no statistics exist in the repository. Adaptive Dispatch Mode In adaptive dispatch mode. you create two service levels: ¨ Service level “Low” has dispatch priority 10 and maximum dispatch wait time 7. the Load Balancer uses service levels to determine the order in which to dispatch tasks from the queue. if multiple tasks with the same service level are waiting in the dispatch queue and adequate computing resources are not available to run a resource intensive task. the Load Balancer dispatches tasks with service level High before tasks with service level Low because service level High has a higher dispatch priority. but you cannot delete it. ¨ Service level “High” has dispatch priority 2 and maximum dispatch wait time 1. When the Load Balancer has more tasks to dispatch than the PowerCenter Integration Service can run at the time. You create and edit service levels in the domain properties or using infacmd.800 seconds. For example. For example. All tasks in a workflow have the same service level. the Load Balancer dispatches the tasks with the default service level. the Load Balancer uses the following default values: ¨ 40 MB memory ¨ 15% CPU In adaptive dispatch mode. The Administrator tool provides a default service level named Default with a dispatch priority of 5 and maximum dispatch wait time of 1800 seconds. The Load Balancer does not dispatch a task to a node that is out of free swap space. When you create a service level. It dispatches the task if doing so does not cause any threshold to be exceeded. the Load Balancer changes its dispatch priority to the maximum priority so that the task does not remain in the dispatch queue indefinitely. the order in which the Load Balancer dispatches tasks from the dispatch queue depends on the task requirements and dispatch priority.in the dispatch queue. The Load Balancer uses service levels to dispatch tasks from the dispatch queue. Therefore. a workflow developer can assign it to a workflow in the Workflow Manager. In adaptive dispatch mode. You can update the default service level.200 seconds. It identifies the node with the most available CPU and checks the resource provision thresholds on the node. When multiple tasks are in the dispatch queue. you can use the same service levels for all repositories in a domain. the Load Balancer reserves a node for the resource intensive task and keeps dispatching less intensive tasks to other nodes. If a workflow service level does not exist in the domain. Service levels are domain properties. To identify the best node to run a task. If a task with service level Low waits in the dispatch queue for two hours. the Load Balancer can use the CPU profile to rank nodes according to the amount of computing resources on the node. the Load Balancer evaluates the computing resources on all available nodes. When you remove a service level. the Load Balancer also collects and stores statistics from the last three runs of the task and compares them with node load metrics. Service Levels Service levels establish priorities among tasks that are waiting to be dispatched. the Workflow Manager does not update tasks that use the service level. the Load Balancer places those tasks in the dispatch queue.

4 GHz computer running Windows 2000. Click OK. calculate the CPU profile when the node is idle. click Add. For example. select the node in the Navigator and click Actions > Recalculate CPU Profile Benchmark. A user-defined resource that identifies any other resources available to the node. To get the most accurate value.Creating Service Levels Create service levels in the Administrator tool. When you create a node. The CPU profile is an index of the processing power of a node compared to a baseline system. This value is not used in round-robin or metric-based dispatch modes. The calculation takes approximately five minutes and uses 100% of one CPU on the machine. 1. To remove a service level. Calculating the CPU Profile In adaptive dispatch mode. You can also calculate the CPU profile using infacmd. In the Administrator tool. select a domain in the Navigator. Define the following types of resources: ¨ Connection.28. You assign resources required by a task in the task properties in the PowerCenter Workflow Manager. the CPU profile for the SPARC computer should be set to 0. 4. The baseline system is a Pentium 2. 3. click the Remove button for the service level you want to remove. Enter values for the service level properties. Any resource installed with PowerCenter.0. you can edit the node properties and update the value manually. You define the resources available to each node in the Administrator tool. the CPU profile is set to 1. the Load Balancer dispatches tasks to nodes based on the resources available on each node. if a SPARC 480 MHz computer is 0. RELATED TOPICS: ¨ “Service Level Management” on page 47 Configuring Resources When you configure the PowerCenter Integration Service to run on a grid and to check resource requirements. Load Balancer for the PowerCenter Integration Service 279 . In the Service Level Management area. such as a plug-in or a connection object. By default. For example. the Load Balancer uses the CPU profile to rank the computing throughput of each CPU and bus architecture in a grid. Enable and disable available resources on the Resources tab for the node in the Administrator tool or using infacmd. 5. such as parameter files or file server directories. all connection resources are available by default. Disable the connection resources that are not available to the node. ¨ Custom. 2. A user-defined resource that defines files or directories available to the node.28 times as fast as the baseline computer. you may use a custom resource to identify a specific database client version. You configure the PowerCenter Integration Service to check available resources in the PowerCenter Integration Service properties in Informatica Administrator. To calculate the CPU profile for a node. ¨ File/Directory. This ensures that nodes with higher processing power get precedence for dispatch. 6. Click the Properties tab. Or.

¨ Maximum memory %. If you set this threshold to 2 on a 4-CPU node that has four threads running and two runnable threads waiting. If you set this threshold to 120% on a node. set this threshold to 0. if you set this threshold to 10 when two PowerCenter Integration Services are running on the node. This threshold limits context switching overhead. set it to a high number such as 200. It can continue to dispatch tasks to a node as long as the resource provision thresholds defined for the node are not exceeded. such as 200. The Load Balancer uses this threshold in metric-based and adaptive dispatch modes.Defining Resource Provision Thresholds The Load Balancer dispatches tasks to PowerCenter Integration Service processes running on a node. If you want the Load Balancer to ignore this threshold. You can define the following resource provision thresholds for each node in a domain: ¨ Maximum CPU run queue length. You can set this threshold to a low value to preserve computing resources for other applications. If you want the Load Balancer to ignore this threshold. Set this threshold to a high number. It dispatches tasks from the queue when a PowerCenter Integration Service process becomes available. ¨ Maximum processes. The default value for this threshold is 10. the maximum number of Session tasks allowed for the node is 20 and the maximum number of Command tasks allowed for the node is 20. The Load Balancer uses this threshold in metric-based and adaptive dispatch modes. The Load Balancer does not count threads that are waiting on disk or network I/Os. When the Load Balancer has more Session and Command tasks to dispatch than the PowerCenter Integration Service can run at a time. This threshold specifies the maximum number of running Session or Command tasks allowed for each PowerCenter Integration Service process that runs on the node. the Load Balancer places the tasks in the dispatch queue. To prevent the Load Balancer from dispatching tasks to the node. to cause the Load Balancer to ignore it. and virtual memory usage on the node is above 120%. The maximum number of runnable threads waiting for CPU resources on the node. The default value for this threshold is 150%. 280 Chapter 18: PowerCenter Integration Service . For example. Set this threshold to a value greater than 100% to allow the allocation of virtual memory to exceed the physical memory size when dispatching tasks. the Load Balancer does not dispatch new tasks to this node. the Load Balancer does not dispatch new tasks to the node. Therefore. The maximum percentage of virtual memory allocated on the node relative to the total physical memory size. The default value is 10. The maximum number of running processes allowed for each PowerCenter Integration Service process that runs on the node. the maximum number of processes that can run simultaneously is 40.000. You define resource provision thresholds in the node properties. set it to a high number such as 1. The Load Balancer uses this threshold in all dispatch modes.

It extracts data from the mapping sources and stores the data in memory while it applies the transformation rules configured in the mapping. When a workflow starts. 282 ¨ Load Balancer. The PowerCenter Integration Service uses the Load Balancer to dispatch tasks. 281 . the PowerCenter Integration Service retrieves mapping. The PowerCenter Integration Service loads the transformed data into one or more targets. The Load Balancer dispatches tasks to achieve optimal performance. 294 ¨ Code Pages and Data Movement Modes. 282 ¨ PowerCenter Integration Service Process. 296 PowerCenter Integration Service Architecture Overview The PowerCenter Integration Service moves data from sources to targets based on PowerCenter workflow and mapping metadata stored in a PowerCenter repository. workflow.CHAPTER 19 PowerCenter Integration Service Architecture This chapter includes the following topics: ¨ PowerCenter Integration Service Architecture Overview. 287 ¨ Processing Threads. 292 ¨ System Resources. the PowerCenter Integration Service process starts and locks the workflow. and session metadata from the repository. The PowerCenter Integration Service starts one or more PowerCenter Integration Service processes to run and monitor workflows. ¨ Load Balancer. and starts the process to run sessions. 296 ¨ Output Files and Caches. runs the workflow tasks. the PowerCenter Integration Service uses the following components: ¨ PowerCenter Integration Service process. 284 ¨ Data Transformation Manager (DTM) Process. 288 ¨ DTM Processing. 291 ¨ Grids. 281 ¨ PowerCenter Integration Service Connectivity. When you run a workflow. It may dispatch tasks to a single node or across the nodes in a grid. To move data from sources to targets.

It connects to the PowerCenter Repository Service to retrieve workflow and mapping metadata from the repository database. You can optionally set a parameter to limit the database connections. source databases. which sends back PowerCenter Repository Service information to the PowerCenter Integration Service process. and transform data.¨ Data Transformation Manager (DTM) process.and post. PowerCenter Integration Service Process The PowerCenter Integration Service starts a PowerCenter Integration Service process to run and monitor workflows. The PowerCenter Integration Service process connects to the source or target database using ODBC or native drivers. It can start and run multiple tasks concurrently. When the PowerCenter Integration Service process requests a repository connection. creates threads to initialize the session. The PowerCenter Integration Service process allows an unlimited number of connections to lookup or stored procedure databases. It also transforms and loads the data in parallel. the PowerCenter Integration Service creates multiple database connections to a single source and extracts a separate range of data for each connection. The PowerCenter Integration Service can achieve high performance using symmetric multi-processing systems. and request workflow and session logs. the session fails. If a database user does not have permission for the number of connections a session requires.session operations. The DTM process performs session validations. display workflow details. It performs the following tasks: ¨ Manage workflow scheduling. The PowerCenter Integration Service process maintains a database connection pool for stored procedures or lookup databases in a workflow. The PowerCenter Workflow Manager communicates with the PowerCenter Integration Service process each time you schedule or edit a workflow. For a session. the request is routed through the master gateway. It can also concurrently process partitions within a single session. PowerCenter Integration Service Connectivity The PowerCenter Integration Service is a repository client. read. the PowerCenter Integration Service process holds the connection as long as it needs to read data from source tables or write data to target tables. and handles pre. and target databases: Note: Both the Windows and UNIX versions of the PowerCenter Integration Service can use ODBC drivers to connect to databases. The following table summarizes the software you need to connect the PowerCenter Integration Service to the platform components. The PowerCenter Integration Service process accepts requests from the PowerCenter Client and from pmcmd. The PowerCenter Repository Service connects to the repository and performs repository metadata transactions for the client application. Use the connection information defined for the domain to access the PowerCenter Integration Service from the PowerCenter Workflow Manager. write. The PowerCenter Workflow Manager communicates with the PowerCenter Integration Service process over a TCP/ IP connection. ¨ Lock and read the workflow. The PowerCenter Integration Service process connects to the PowerCenter Repository Service. When you create multiple partitions within a session. Use native drivers to improve performance. 282 Chapter 19: PowerCenter Integration Service Architecture . The PowerCenter Integration Service process is also known as the pmserver process. The PowerCenter Integration Service starts a DTM process to run each Session and Command task within a workflow.

Run the PowerCenter Workflows Across the Nodes in a Grid When you run a PowerCenter Integration Service on a grid. When a task in the workflow completes. You can use information in the workflow log in conjunction with the PowerCenter Integration Service log and session log to troubleshoot system. ¨ Start the DTM process or processes to run the session. workflow task status. ¨ Run workflow tasks and evaluates the conditional links connecting tasks. it queries the repository for a list of workflows configured to run on it. The master service PowerCenter Integration Service Process 283 . Manage PowerCenter Workflow Scheduling The PowerCenter Integration Service process manages workflow scheduling in the following situations: ¨ When you start the PowerCenter Integration Service. Based on the result of the evaluation. the PowerCenter Integration Service process reads the parameter file and expands the variable values for the workflow and any worklets invoked by the workflow. the service processes run workflow tasks across the nodes of the grid. the PowerCenter Integration Service process cannot start the workflow. the PowerCenter Integration Service process adds the workflow to or removes the workflow from the schedule queue. the PowerCenter Integration Service process evaluates the completed task according to specified conditions.¨ Read the parameter file. The execute lock allows the PowerCenter Integration Service process to run the workflow and prevents you from starting the workflow again until it completes. ¨ When you save a workflow. The parameter file can also contain mapping parameters and variables and session parameters for sessions in the workflow. Create the PowerCenter Workflow Log The PowerCenter Integration Service process creates a log for the PowerCenter workflow. and error messages. When you start the PowerCenter Integration Service. When you save a workflow assigned to a PowerCenter Integration Service to the repository. or session problems. The workflow log contains a history of the workflow run. Links define the order of execution for workflow tasks. The PowerCenter Integration Service process reads all links and tasks in the workflow except sessions and worklet instances. If the workflow is already locked. such as success or failure. the PowerCenter Integration Service process passes the parameter file name to the DTM. The domain designates one service process as the master service process. If the workflow uses a parameter file. The DTM retrieves the session and mapping from the repository at session run time. workflow. it requests an execute lock on the workflow from the repository. ¨ Send post-session email in the event of a DTM failure. The PowerCenter Integration Service process also reads the workflow from the repository at workflow run time. The PowerCenter Integration Service process reads worklets from the repository when the worklet starts. the PowerCenter Integration Service process runs successive links and tasks. the PowerCenter Integration Service process checks the workflow properties for use of a parameter file. Run the PowerCenter Workflow Tasks The PowerCenter Integration Service process runs workflow tasks according to the conditional links connecting the tasks. ¨ Create the workflow log. including initialization. Read the Parameter File When the workflow starts. The PowerCenter Integration Service process reads session instance information from the repository. as well as service and service process variables for the service process that runs the workflow. A workflow may be locked if it is already running. ¨ Write historical run information to the repository. When starting the DTM. Lock and Read the PowerCenter Workflow When the PowerCenter Integration Service process starts a workflow.

the PowerCenter Integration Services starts the DTM process with the system user account you specify in the operating system profile. The worker service processes run workflows across the nodes in a grid. When nodes become available. ¨ Resource provision thresholds. the worker service process starts multiple DTM processes that run groups of session threads. Send Post-Session Email The PowerCenter Integration Service process sends post-session email if the DTM terminates abnormally. Dispatch Process The Load Balancer uses different criteria to dispatch tasks depending on whether the PowerCenter Integration Service runs on a node or a grid. You can view this information using the PowerCenter Workflow Monitor. When the Load Balancer needs to dispatch more Session and Command tasks than the PowerCenter Integration Service can run. The PowerCenter Integration Service process provides the DTM process with session and parameter file information that allows the DTM to retrieve the session and mapping metadata from the repository. The dispatch mode determines how the Load Balancer selects nodes for dispatch. the Load Balancer dispatches the Session. When multiple tasks are waiting in the dispatch queue. When you run a workflow. The Load Balancer dispatches tasks in the order it receives them. Command. Historical run information for tasks includes start and completion times and completion status. ¨ Service levels. 284 Chapter 19: PowerCenter Integration Service Architecture . and predefined Event-Wait tasks within the workflow. Start the DTM Process When the workflow reaches a session. When you run a session on a grid. ¨ Dispatch mode. The Load Balancer can use PowerCenter resources to determine if it can dispatch a task to a node. It may dispatch tasks to a single node or across nodes. Write Historical Information The PowerCenter Integration Service process monitors the status of workflow tasks during the workflow run. Historical run information for sessions also includes source read statistics. The DTM sends post-session email in all other cases. The Load Balancer uses resource provision thresholds to determine whether it can start additional tasks on a node. the Load Balancer dispatches tasks from the queue in the order determined by the workflow service level. the Load Balancer uses service levels to determine the order in which to dispatch tasks from the queue. it places the tasks it cannot run in a queue. When you use operating system profiles.process monitors the worker service processes running on separate nodes. ¨ Resources. The Load Balancer performs several steps to dispatch tasks. the PowerCenter Integration Service process starts the DTM process. and number of errors. The Load Balancer matches task requirements with resource availability to identify the best node to run a task. It dispatches the task to a PowerCenter Integration Service process running on the node. The following concepts describe Load Balancer functionality: ¨ Dispatch process. target load statistics. When workflow tasks start or finish. Load Balancer The Load Balancer dispatches tasks to achieve optimal performance and scalability. the PowerCenter Integration Service process writes historical run information to the repository.

If no available node has the required resources. The Load Balancer checks different thresholds depending on the dispatch mode. the Load Balancer dispatches the session only to nodes where the SAP client is installed. You define resources available to a node in the Administrator tool. If you configure the PowerCenter Integration Service to run on a grid and to check resources. the Load Balancer places the task in the dispatch queue. If dispatching the task causes any threshold to be exceeded. If you configure the PowerCenter Integration Service to check resource requirements. 2. The Load Balancer checks the following thresholds: ¨ Maximum CPU Run Queue Length. The Load Balancer can dispatch a task to a node when dispatching the task does not cause the resource provision thresholds to be exceeded. Dispatch Tasks Across a Grid When the PowerCenter Integration Service runs on a grid. Resources You can configure the PowerCenter Integration Service to check the resources available on each node and match them with the resources required to run the task. The Load Balancer dispatches all tasks to the node that runs the master PowerCenter Integration Service process. the Load Balancer identifies nodes that have the PowerCenter resources required by the tasks in the workflow. The Load Balancer verifies which nodes are currently running and enabled. 4. the Load Balancer performs the following steps to dispatch a task: 1. and it dispatches the task later. For example. The Load Balancer verifies that the resource provision thresholds on each candidate node are not exceeded. You configure the PowerCenter Integration Service to check resources in the Administrator tool. If dispatching the task causes a threshold to be exceeded. The Load Balancer checks resource provision thresholds on the node. The Load Balancer checks this threshold in metric-based and adaptive dispatch modes. The Load Balancer selects a node based on the dispatch mode. 2. the Load Balancer dispatches a task to a node where the required PowerCenter resources are available. Resource Provision Thresholds The Load Balancer uses resource provision thresholds to determine the maximum load acceptable for a node. 3. the Load Balancer places the task in the dispatch queue.Dispatch Tasks on a Node When the PowerCenter Integration Service runs on a node. the PowerCenter Integration Service fails the task. You assign resources required by a task in the task properties. the Load Balancer performs the following steps to determine on which node to run a task: 1. and it dispatches the task later. Load Balancer 285 . The maximum number of runnable threads waiting for CPU resources on the node. The Load Balancer excludes the node if the maximum number of waiting threads is exceeded. if a session uses an SAP source. The Load Balancer checks thresholds based on the dispatch mode. The PowerCenter Integration Service writes resource requirements and availability information in the workflow log.

The Load Balancer excludes the node if dispatching the task causes this threshold to be exceeded. You configure the dispatch mode in the domain properties. The maximum percentage of virtual memory allocated on the node relative to the total physical memory size. It checks all resource provision thresholds on each available node and excludes a node if dispatching a task causes the thresholds to be exceeded. ¨ Adaptive. The Load Balancer uses service levels to determine the order in which to dispatch tasks from the queue. When nodes become available. the Load Balancer places the tasks in the dispatch queue. If no statistics exist in the repository. ¨ Maximum Processes. RELATED TOPICS: ¨ “Defining Resource Provision Thresholds” on page 280 Dispatch Mode The dispatch mode determines how the Load Balancer selects nodes to distribute workflow tasks. the Load Balancer uses default values. It checks all resource provision thresholds on each available node and excludes a node if dispatching a task causes the thresholds to be exceeded. This mode is the least compute-intensive and is useful when the load on the grid is even and the tasks to dispatch have similar computing requirements. The maximum number of running processes allowed for each PowerCenter Integration Service process that runs on the node. The Load Balancer checks this threshold in metric-based and adaptive dispatch modes. The Load Balancer averages statistics from the last three runs of the task to estimate the computing resources required to run the task. the Load Balancer can use the CPU profile for the node to identify the node with the most computing resources. You define resource provision thresholds in the node properties. it uses task statistics to determine whether a task can run on a node. This mode prevents overloading nodes and ensures the best performance on a grid that is not heavily loaded. In adaptive dispatch mode. It checks the Maximum Processes threshold on each available node and excludes a node if dispatching a task causes the threshold to be exceeded. When the Load Balancer has more Session and Command tasks to dispatch than the PowerCenter Integration Service can run at the time. When the Load Balancer runs in metric-based or adaptive mode. The Load Balancer dispatches tasks to available nodes in a round-robin fashion. Service Levels Service levels establish priority among tasks that are waiting to be dispatched. The Load Balancer checks this threshold in all dispatch modes. The Load Balancer excludes the node if dispatching the task causes this threshold to be exceeded. This mode prevents overloading nodes when tasks have uneven computing requirements. 286 Chapter 19: PowerCenter Integration Service Architecture . The Load Balancer ranks nodes according to current CPU availability. ¨ Metric-based. the Load Balancer dispatches tasks from the queue. If all nodes in the grid have reached the resource provision thresholds before any PowerCenter task has been dispatched. The Load Balancer evaluates nodes in a round-robin fashion. The Load Balancer uses the following dispatch modes: ¨ Round-robin. The Load Balancer continues to evaluate nodes until it finds a node that can accept the task.¨ Maximum Memory %. the Load Balancer dispatches tasks one at a time to ensure that PowerCenter tasks are still executed.

The DTM process forms partition groups and distributes them to worker DTM processes running on nodes in the grid. The DTM scales the number of session partitions based on factors such as source database partitions or the number of nodes in a grid. When you disable data code page validation. If the PowerCenter Integration Service encounters an error when converting data. writer. target query. Create Dynamic Partitions The DTM adds partitions to the session if you configure the session for dynamic partitioning. The DTM verifies that the user who started or scheduled the workflow has execute permissions for connection objects associated with the session. Validate Code Pages The PowerCenter Integration Service processes data internally using the UCS-2 character set. The DTM retrieves the mapping and session metadata from the repository and validates it. Expand Variables and Parameters If the workflow uses a parameter file. The session log contains a complete history of the session run. service-level.You create and edit service levels in the domain properties in the Administrator tool. The DTM process is also known as the pmdtm process. including initialization. You can use information in the session log in conjunction with the PowerCenter Integration Service log and the workflow log to troubleshoot system or session problems. Form Partition Groups If you run a session on a grid. Perform Pushdown Optimization If the session is configured for pushdown optimization. You assign service levels to workflows in the workflow properties in the PowerCenter Workflow Manager. Read the Session Information The PowerCenter Integration Service process provides the DTM with session instance information when it starts the DTM. the DTM runs an SQL statement to push transformation logic to the source or target database. Data Transformation Manager (DTM) Process 287 . Data Transformation Manager (DTM) Process The PowerCenter Integration Service process starts the DTM process to run a session. and transformation threads that runs in a single DTM process. lookup. status. The DTM creates and expands session-level. Verify Connection Object Permissions After validating the session code pages. lookup database query. the PowerCenter Integration Service verifies that the source query. the DTM verifies permissions for connection objects used in the session. transformation. and stored procedure call text convert from the source. The DTM is the process associated with the session task. the PowerCenter Integration Service process sends the parameter file to the DTM when it starts the DTM. or stored procedure data code page to the UCS-2 character set without loss of data in conversion. target. Create the Session Log The DTM creates logs for the session. and mapping-level variables and parameters. the PowerCenter Integration Service runs the DTM process as the operating system user you specify in the operating system profile. the DTM forms partition groups. A partition group is a group of reader. and error messages. it writes an error message to the session log. Note: If you use operating system profiles.

the DTM composes and sends email that reports session completion or failure. The master thread for a session can create mapping. reader. 3. The number of threads depends on the partitioning information for each target load order group in the mapping. If the DTM terminates abnormally. For each target load order group in a mapping. transformation. The number of threads the DTM uses to run the session depends on the number of partitions configured for the session. the PowerCenter Integration Service process sends post-session email. the master thread creates one reader. the master thread can create several threads. The DTM uses multiple threads to process data in a session. the DTM runs pre-session shell commands. it runs post-session SQL commands and stored procedures. The reader thread controls how the PowerCenter Integration Service 288 Chapter 19: PowerCenter Integration Service Architecture . Run Post-Session Operations After the DTM runs the processing threads. This is also known as buffer memory. and writer threads to extract. The types of threads depend on the session properties and the transformations in the mapping. Send Post-Session Email When the session finishes. In this case. The master thread creates and manages other threads. 2. transform. One writer thread. Run Pre-Session Operations After verifying connection object permissions. the DTM uses reader. one transformation. and load data. and writer threads. post-session. One reader thread. The following figure shows the threads the master thread creates for a simple mapping that contains one target load order group: 1. One transformation thread.Start Worker DTM Processes The DTM sends a request to the PowerCenter Integration Service process to start worker DTM processes on other nodes when the session is configured to run on a grid. Run the Processing Threads After initializing the session. and one writer thread to process the data. presession. transformation. The DTM then runs post-session shell commands. The mapping contains a single partition. The DTM then runs presession stored procedures and SQL commands. Processing Threads The DTM allocates process memory for the session and divides it into buffers. The main DTM thread is called the master thread.

Bypassed transformation thread.and Post-Session Threads The master thread creates one pre-session and one post-session thread to perform pre.and post-session properties. the data bypasses the transformation threads. Relational sources use relational reader threads. One writer thread. source qualifier. One reader thread. The following figure shows the threads for a pass-through pipeline with one partition: 1.process extracts source data and passes it to the source qualifier.and post-session threads ¨ Reader threads ¨ Transformation threads ¨ Writer threads Mapping Threads The master thread creates one mapping thread for each session. This type of pipeline is a passthrough pipeline. Processing Threads 289 . The mapping thread fetches session and mapping information. 3. Pre. proceeding directly from the reader buffers to the writer. compiles the mapping. The types of threads the master thread creates depend on the pre. The number of reader threads equals the number of partitions. 2.and post-session operations. The number of reader threads depends on the partitioning information for each pipeline. The PowerCenter Integration Service creates an SQL statement for each reader thread to extract data from a relational source. For file sources. Thread Types The master thread creates different types of threads for a session. the PowerCenter Integration Service can create multiple threads to read a single source. Reader Threads The master thread creates reader threads to extract source data. and file sources use file reader threads. and cleans up after session execution. and a target definition. the transformation thread controls how the PowerCenter Integration Service process handles the data. The master thread can create the following types of threads: ¨ Mapping threads ¨ Pre. and the writer thread controls how the PowerCenter Integration Service process loads data to the target. When the pipeline contains only a source definition. as well as the types of transformations in the mapping.

¨ Install the PowerCenter Integration Service on a machine with multiple CPUs. the PowerCenter Integration Service scales the number of session partitions based on factors such as the source database partitions or the number of nodes in a grid. such as a Transaction Control transformation. the transformation threads use double bytes to move character data. If the transformation thread requires more space. When you enable dynamic partitioning. database partitioning. or the number of rows that pass through a transformation that generates transactions. and load for each partition in parallel. When loading targets. You can also configure a session for dynamic partitioning to enable the PowerCenter Integration Service to set partitioning at run time. it pages to local cache files to hold additional data. the transformation thread uses cache memory until it reaches the configured cache size limits. For relational sources. Aggregator. the writer thread takes data from buffers and commits it to session targets. When the PowerCenter Integration Service runs in ASCII mode. The PowerCenter Integration Service can partition data using round-robin. key-range. 290 Chapter 19: PowerCenter Integration Service Architecture . If it contains multiple partitions. To accomplish this. the master thread creates one writer thread. each writer thread creates a separate file. The number of writer threads depends on the partitioning information for each pipeline. You can configure the partition type at most transformations in the pipeline. When the PowerCenter Integration Service runs in Unicode mode. If the pipeline contains a Rank. and create memory caches when necessary. When the PowerCenter Integration Service loads relational data. it creates a separate file for each partition.Transformation Threads The master thread creates one or more transformation threads for each partition. Each writer thread creates connections to the target databases to load data. the PowerCenter Integration Service creates multiple database connections to a single source and extracts a separate range of data for each connection. Transformation threads process data according to the transformation logic in the mapping. hash. the writer commits data based on the commit interval in the session properties. The PowerCenter Integration Service transforms the partitions concurrently. Writer Threads The master thread creates writer threads to load target data. When the PowerCenter Integration Service loads data to file targets. Transformation threads store transformed data in a buffer drawn from the memory pool for subsequent access by the writer thread. the transformation threads pass character data in single bytes. If the target is a file. You can configure the session to merge these files. the PowerCenter Integration Service process can achieve high performance by partitioning the pipeline and performing the extract. Pipeline Partitioning When running sessions. You can configure a session to commit data based on the number of source rows read. The number of transformation threads depends on the partitioning information for each pipeline. If the pipeline contains one partition. it passes data between the partitions as needed to perform operations such as aggregation. move the data from transformation to transformation. the number of rows written to the target. use the following session and PowerCenter Integration Service configuration: ¨ Configure the session with multiple partitions. transformation. Joiner. The master thread creates transformation threads to transform data received in buffers by the reader thread. or pass-through partitioning. the master thread creates multiple writer threads. You can choose to merge the target files. it creates multiple database connections to the target and loads partitions of data concurrently. or a cached Lookup transformation. If the target is relational. Sorter.

the DTM begins to process Target Load Order Group 2 by reading Source C. it does not read more source rows until the transformation logic allows the DTM to stop blocking the source. transformations. After the DTM fills the buffers. and targets linked together in a mapping. When the DTM blocks data. The DTM sometimes blocks the flow of data at a transformation in the mapping while it processes a row of data from a different source. ¨ Blocking data. After the DTM reads and processes the row it needs.DTM Processing When you run a session. The DTM reads the sources in a mapping at different times depending on how you configure the sources. and it processes target load order groups sequentially. the DTM process reads source data and passes it to the transformations for processing. and targets in the mapping. Each target load order group contains one or more source pipelines. When the DTM stops blocking a source. ¨ Block processing. When it finishes processing Target Load Order Group 1. the DTM processes the target load order groups sequentially. DTM Processing 291 . Reading Source Data Mappings contain one or more target load order groups. The following figure shows a mapping that contains two target load order groups and three source pipelines: In the mapping. The DTM passes data to the input groups concurrently. it stops blocking the source. The DTM blocks data at one input group when it needs a specific row from a different input group to perform the transformation logic. it reads data from the source connected to the input group until it fills the reader and transformation buffers. A source pipeline consists of a source qualifier and all of the transformations and target instances that receive data from that source qualifier. By default. A target load order group is the collection of source qualifiers. It first processes Target Load Order Group 1 by reading Source A and Source B at the same time. However. the DTM reads sources in a target load order group concurrently. Blocking Data You can include multiple input group transformations in a mapping. sometimes the transformation logic of a multiple input group transformation requires that the DTM block data on one input group while it waits for a row from a different input group. it processes the data in the buffers and continues to read from the source. transformations. The DTM reads and processes a block of rows at a time. Blocking is the suspension of the data flow into an input group of a multiple input group transformation. You can configure the order that the DTM processes target load order groups. To help understand DTM processing. consider the following DTM process actions: ¨ Reading source data.

The master service process can run on any node in the grid. Worker service processes running on other nodes act as Load Balancer agents. the DTM processes one row in a block. The master service process receives requests. runs the workflow and workflow tasks including the Scheduler. The master service process can also act as a worker service process. the PowerCenter Integration Service designates one service process as the master service process. the Scheduler uses the date and time for the master service process node to start scheduled workflows. Command. For optimal performance. Command. Workflow on a Grid When you run a workflow on a grid. A DTM process runs on each node where a session runs. Grids When you run a PowerCenter Integration Service on a grid. a worker service process can run multiple DTM processes on different nodes to distribute session threads.Block Processing The DTM reads and processes a block of rows at a time. Because it runs on the master service process node. a Command task. and communicates with worker service processes on other nodes. When you connect the CURRVAL port in a Sequence Generator transformation. the DTM processes one row in a block. ¨ Configure array-based mode for Custom transformation procedure. and predefined Event-Wait tasks to the node that runs the master service process or to other nodes. In the following circumstances. For example. and the service processes on other nodes as worker service processes. a master service process runs on one node and worker service processes run on the remaining nodes in the grid. which dispatches tasks to nodes in the grid. and predefined Event-Wait tasks to itself and other nodes. the DTM processes one row in a block: ¨ Log row errors. The worker service process runs predefined Event-Wait tasks within its process. and a predefined Event-Wait task. So the Load Balancer can distribute Session. When you configure the data access mode for a Custom transformation procedure to be row-based. you have a workflow that contains two Session tasks. It starts a process to run Command tasks and a DTM process to run Session tasks. The master service process also runs the Load Balancer. If you run a session on a grid. and it distributes the Session. The number of rows in the block depend on the row size and the DTM buffer size. and the DTM processes multiple rows in a block. the data access mode is array-based. The master service process runs the workflow and workflow tasks. the session processes one row in a block. By default. ¨ Connect CURRVAL. 292 Chapter 19: PowerCenter Integration Service Architecture . connect only the NEXTVAL port in mappings. When you log row errors.

The worker service processes start the worker DTM processes on other nodes. the worker service process starts a process to run a Command task and starts a DTM process to run Session task 1. The Load Balancer distributes Command tasks as it does when you run a workflow on a grid. and predefined Event-Wait tasks to other nodes. The master service process starts a temporary preparer DTM process that fetches the session and prepares it to run. ¨ On Node 2. you run a workflow on a grid that contains one Session task and one Command task. In addition.The following figure shows an example of service process distribution when you run the workflow on a grid with three nodes: When you run the workflow on a grid. Multiple worker DTM processes running on a node might be running multiple sessions or multiple partition groups from a single session depending on the session configuration. and predefined Event-Wait tasks. it distributes the session threads to separate DTM processes. including the Scheduler. the Scheduler uses the date and time for the master service process node to start scheduled workflows. the PowerCenter Integration Service process distributes the tasks in the following way: ¨ On Node 1. The worker DTM runs the session. Session on a Grid When you run a session on a grid. You also configure the session to run on the grid. Command. Grids 293 . the worker service process runs a predefined Event-Wait task and starts a DTM process to run Session task 2. the master service process runs the workflow and workflow tasks. which monitors the DTM processes running on other nodes. For example. The Load Balancer dispatches the Session. when the Load Balancer dispatches a Session task. Command. ¨ On Node 3. After the preparer DTM process prepares the session. it acts as the master DTM process. Because it runs on the master service process node. the master service process starts the workflow and runs workflow tasks other than the Session.

This provides increased performance. the worker service process runs the Command task and starts the worker DTM processes that run the session threads. so there is no parallelism. The number of CPUs used depends on factors such as the number of partitions. which becomes the master DTM process. It also starts a temporary preparer DTM process. the number of available CPUs. ¨ On Node 3. transformation. The PowerCenter Integration Service uses the following system resources: ¨ CPU usage ¨ DTM buffer memory ¨ Cache memory CPU Usage The PowerCenter Integration Service process performs read. and write processing for a pipeline in parallel. it performs the following tasks: ¨ On Node 1. the worker service process starts the worker DTM processes that run the session threads. ¨ On Node 2. On a single processor platform. The PowerCenter Integration Service process can use multiple CPUs to process a session that contains multiple partitions. The Load Balancer dispatches the Command task and session threads to nodes in the grid. and it can process multiple sessions in parallel. System Resources To allocate system resources for read.The following figure shows the service process and DTM distribution when you run a session on a grid on three nodes: When the PowerCenter Integration Service process runs the session on a grid. transformation. 294 Chapter 19: PowerCenter Integration Service Architecture . It can process multiple partitions of a pipeline within a session. the number of threads. these tasks share the CPU. and amount or resources required to process the mapping. the master service process runs workflow tasks. If you have a symmetric multi-processing (SMP) platform. you should understand how the PowerCenter Integration Service allocates and uses system resources. as true parallelism is achieved. and write processing. you can use multiple CPUs to concurrently process session data or partitions of data.

if the local directory for cache files runs out of disk space.DTM Buffer Memory The PowerCenter Integration Service launches the DTM process. By default. so increasing buffer memory might improve session performance. By default. the PowerCenter Integration Service determines the amount of memory to allocate for caches. the session cannot initialize. The DTM allocates buffer memory to the session based on the DTM Buffer Size setting in the session properties. if the session is configured to perform incremental aggregation or if a Lookup transformation is configured for a persistent lookup cache. the PowerCenter Integration Service calculates the size of the buffer memory and the buffer block size. the DTM releases memory used by the index and data caches and deletes any index and data files. You configure the memory size for the cache in the transformation properties. the PowerCenter Integration Service uses double bytes to move characters.760 bytes for the XML target.777. the DTM may create multiple index and data files. By default. System Resources 295 . When processing large amounts of data. the DTM creates cache files in the directory configured for the $PMCacheDir service process variable.485. The DTM process also creates an in-memory cache to store data for the Sorter transformations and XML targets. The DTM divides the memory into buffer blocks as configured in the Buffer Block Size setting in the session properties. It does fail. If the DTM requires more cache space than it allocates. If the DTM requires more space than it allocates. and writer threads use buffer blocks to move data from sources and to targets. By default. transformation.216 bytes for the Sorter transformation cache and 10. it pages to local index and data files. the PowerCenter Integration Service determines the cache size for the Sorter transformation and XML target at run time. If the DTM cannot allocate the configured amount of buffer memory for the session. The reader. Cache Memory The DTM process creates in-memory index and data caches to temporarily store data used by the following transformations: ¨ Aggregator transformation (without sorted input) ¨ Rank transformation ¨ Joiner transformation ¨ Lookup transformation (with caching enabled) You can configure memory size for the index and data cache in the transformation properties. In Unicode mode. the DTM saves all index and data cache information to disk for the next session run. You may want to configure the buffer memory and buffer block size manually. however. it pages to local cache files. you can manually configure a cache size for the data and index caches. However. After the session completes. The DTM creates cache files in the directory configured for the $PMTempDir service process variable. The PowerCenter Integration Service allocates a minimum value of 16. However. Informatica recommends you allocate no more than 1 GB for DTM buffer memory. The session does not fail if it runs out of cache memory and pages to the cache files.

If you configure the PowerCenter Integration Service for relaxed data code page validation. These modes determine how the PowerCenter Integration Service handles character data. PowerCenter Integration Service properties. Generate output files and caches in a specified directory by setting service process variables in the session or workflow properties. It reads all character data as ASCII characters and does not perform code page conversions. Log event files are binary files that the Log Manager uses to display log events. In Unicode mode. In ASCII mode. the PowerCenter Integration Service logs status and error messages to log event files. Depending on transformation cache settings and target types. you must also choose the appropriate code pages for your connections. processes the data. To ensure that characters are not lost during conversion from one code page to another.Code Pages and Data Movement Modes You can configure PowerCenter to move single byte and multibyte data. It also treats all numerics as U. ASCII Data Movement Mode Use ASCII data movement mode when all sources and targets are 7-bit ASCII or EBCDIC character sets. the PowerCenter Integration Service may create additional files as well. the PowerCenter Integration Service also creates a reject file. it does not validate session code pages. The PowerCenter Integration Service allots two bytes for each character when moving data through a mapping. The PowerCenter Integration Service converts data from the source character set to UCS-2 before processing. the PowerCenter Integration Service recognizes 7-bit ASCII and EBCDIC characters and stores each character in a single byte. a parameter file.S. By default. and then converts the UCS-2 data to the target code page character set before loading the data. choose Unicode data movement mode. If you want to move multibyte data. the PowerCenter Integration Service lifts source and target compatibility restrictions. It also treats all numerics as U. Standard and all dates as binary data. or an operating system profile. the PowerCenter Integration Service validates source and target code page compatibility when you run a session. When the PowerCenter Integration Service runs in ASCII mode. The PowerCenter Integration Service can move data in either ASCII or Unicode data movement mode. Output Files and Caches The PowerCenter Integration Service process generates output files when you run workflows and sessions. You can also use ASCII data movement mode when sources and targets are 8-bit ASCII. 296 Chapter 19: PowerCenter Integration Service Architecture . Unicode Data Movement Mode Use Unicode data movement mode when sources or targets use 8-bit or multibyte character sets and contain character data. the PowerCenter Integration Service recognizes multibyte character sets as defined by supported code pages.S. The PowerCenter Integration Service stores output files and caches based on the service process variable settings. Standard and all dates as binary data. During each session. The PowerCenter Integration Service code page must be a subset of the PowerCenter repository code page. If you configure the PowerCenter Integration Service to validate data code pages. You choose the data movement mode in the PowerCenter Integration Service configuration settings.

Service process variables set in the session or workflow properties override service process variables set in the PowerCenter Integration Service properties.permissions. Workflow Log The PowerCenter Integration Service process creates a workflow log for each workflow it runs. the PowerCenter Integration Service uses the location specified in the session properties. or an operating system profile. Parameter file. Operating system profile. errors encountered. Service process variables set in parameter files override service process variables set in the PowerCenter Integration Service process properties or an operating system profile. 4. You can also configure the workflow to write events to a log file in a specified directory. It writes information in the workflow log such as initialization of processes. Service process variables set in the PowerCenter Integration Service process properties contain the default setting. Session or workflow properties. you must change the umask of the shell that starts the PowerCenter Integration Service process and then restart it. You can view workflow logs from the PowerCenter Workflow Monitor. The PowerCenter Integration Service process on Windows creates files with read and write permissions. Workflow log error messages are categorized into severity levels. The PowerCenter Integration Service process on UNIX creates recovery files with rw------. workflow task run information. PowerCenter Integration Service process properties. 3. To change the file permissions. when the umask of the shell that starts the PowerCenter Integration Service process is 022. and workflow run summary. The PowerCenter Integration Service creates the following output files: ¨ Workflow log ¨ Session log ¨ Session details file ¨ Performance details file ¨ Reject files ¨ Row error logs ¨ Recovery tables and files ¨ Control file ¨ Post-session email ¨ Output file ¨ Cache files When the PowerCenter Integration Service process on UNIX creates any file other than a recovery file. the PowerCenter Integration Service process creates files with rw-r--r-. If you use operating system profiles.If you define service process variables in more than one place. if you set the $PMSessionLogFile in the operating system profile and in the session properties. the PowerCenter Integration Service saves workflow recovery files to the $PMStorageDir configured in the PowerCenter Integration Service process properties. As with PowerCenter Integration Service logs and session logs. Service process variables set in an operating system profile override service process variables set in the PowerCenter Integration Service properties. it sets the file permissions according to the umask of the shell that starts the PowerCenter Integration Service process. For example. the PowerCenter Integration Service process enters a code number into the workflow log file message along with message text. The PowerCenter Integration Service saves session recovery files to the $PMStorageDir configured in the operating system profile.permissions. You can configure the PowerCenter Integration Service to suppress writing messages to the workflow log file. 2. a parameter file. Output Files and Caches 297 . the PowerCenter Integration Service reviews the precedence of each setting to determine which service process variable setting to use: 1. For example.

timestamp. Session Details When you run a session. and load summary. session name. folder name. The writer may reject a row in the following circumstances: ¨ It is flagged for reject by an Update Strategy or Custom transformation. and names the reject file target_table_name. The reject file contains rows of data that the writer does not write to targets. error message. current row data. The PowerCenter Integration Service process writes the performance details to a file. transformation. The PowerCenter Integration Service process logs information such as source name. the PowerCenter Integration Service process saves the reject file in the directory entered for the service process variable $PMBadFileDir in the PowerCenter Workflow Manager. ¨ It violates a database constraint such as primary key constraint. 298 Chapter 19: PowerCenter Integration Service Architecture . you can choose to log row errors in a central location. and the target database is configured to reject truncated or overflowed data. The amount of detail in the session log depends on the tracing level that you set. and mapping information. You can monitor session details during the session or after the session completes. repository name. You can review a performance details file to determine where session performance can be improved. Reject Files By default. By default.bad. errors encountered. You can also configure the session to write the log information to a log file in a specified directory. the PowerCenter Integration Service process creates a reject file for each target in the session. Note: If you enable row error logging. When a row error occurs. the PowerCenter Integration Service process does not create a reject file. You can view the session log from the PowerCenter Workflow Monitor.Session Log The PowerCenter Integration Service process creates a session log for each session it runs. error code. ¨ A field in the row was truncated or overflowed. As with PowerCenter Integration Service logs and workflow logs. creation of SQL commands for reader and writer threads. Performance Detail File The PowerCenter Integration Service process generates performance details for session runs. and read and write throughput. the PowerCenter Integration Service process logs error information that allows you to determine the cause and source of the error. Performance details provide transformation-by-transformation information on the flow of data through the session. the PowerCenter Workflow Manager creates session details that provide load statistics for each target in the mapping. You can also view performance details in the PowerCenter Workflow Monitor if you configure the session to collect performance details. session validation. Session details include information such as table name. double-click the session in the PowerCenter Workflow Monitor. the PowerCenter Integration Service process enters a code number along with message text. Row Error Logs When you configure a session. row ID. To view session details. number of rows written or rejected. It writes information in the session log such as initialization of processes. The file stores performance details for the last session run.

by default. When the PowerCenter Integration Service process performs recovery. By default. by default. Indicator File If you use a flat file as a target. Control File When you run a session that uses an external loader. the PowerCenter Integration Service process names the target files based on the target instance name. Email You can compose and send email messages by creating an Email task in the Workflow Designer or Task Developer. the other if the session fails. Recovery Tables Files The PowerCenter Integration Service process creates recovery tables on the target database system when it runs a session enabled for recovery. Email tasks in the workflow send email depending on the conditional links connected to the task. Output Files and Caches 299 . by default. If a mapping contains multiple instances of the same target. $PMTargetFileDir. you can configure the PowerCenter Integration Service to create an indicator file for target row type information. the PowerCenter Integration Service process creates the target file based on a file target definition. workflow variable values. The PowerCenter Integration Service process names this file target_name.ind and stores it in the PowerCenter Integration Service variable directory. For post-session email. or you can associate it with a session. you can create two different messages. The Email task allows you to automatically communicate information about a workflow or session run to designated recipients. delete. by default. You can place the Email task in a workflow. $PMTargetFileDir. The PowerCenter Integration Service process creates this file in the PowerCenter Integration Service variable directory. The PowerCenter Integration Service process creates the control file and the target flat file in the PowerCenter Integration Service variable directory. $PMTargetFileDir.When you enable flat file logging. update. the PowerCenter Integration Service process saves the file in the directory entered for the service process variable $PMBadFileDir. status. For each target row. running workflows and sessions. When you run a session in recovery mode. the PowerCenter Integration Service process names the target file based on the target definition name. You can also use variables to generate information about the session name. and workflow schedules. it restores the state of operations to recover the workflow from the point of interruption. and total rows loaded. The workflow state of operations includes information such as active service requests. the PowerCenter Integration Service process creates a control file and a target flat file. or reject. the PowerCenter Integration Service process uses information in the recovery tables to complete the session. Output File If the session writes to a target file. completed and running status.ctl. the indicator file contains a number to indicate whether the row was marked for insert. The control file has an extension of . one to be sent if the session completes successfully. The control file contains information about the target flat file such as data format and loading instructions for the external loader.

and then uses this lookup cache during subsequent session runs. you can configure the transformation to use a persistent lookup cache. the PowerCenter Integration Service process uses this historical information to perform the incremental aggregation.Cache Files When the PowerCenter Integration Service process creates memory cache.idx. The PowerCenter Integration Service process names the index file PMAGG*. The PowerCenter Integration Service process creates the cache file for a Sorter transformation in the $PMTempDir service process variable directory. Persistent Lookup Cache If a session uses a Lookup transformation. and Lookup transformations and XML targets in the directory configured for the $PMCacheDir service process variable. the DTM creates the index and data files in the directory configured for the $PMCacheDir service process variable. Incremental Aggregation Files If the session performs incremental aggregation. Joiner.dat. the DTM creates the index and data files in the directory configured for the $PMCacheDir service process variable. the PowerCenter Integration Service process saves the lookup cache to disk the first time it runs the session. the DTM creates the index and data files for Aggregator. Rank.idx and PMLKUP*. it also creates cache files. The next time the session runs. and the data file PM*. By default.idx. By default.dat and the data file PMAGG*. The PowerCenter Integration Service process names the index file PM*. the PowerCenter Integration Service process saves index and data cache information to disk when the session finished. The PowerCenter Integration Service process creates cache files for the following mapping objects: ¨ Aggregator transformation ¨ Joiner transformation ¨ Rank transformation ¨ Lookup transformation ¨ Sorter transformation ¨ XML target By default.dat. 300 Chapter 19: PowerCenter Integration Service Architecture . With this option selected. If you do not name the files in the transformation properties. these files are named PMLKUP*.

When you create a PowerCenter Repository Service. as long as it meets the minimum requirements for a repository database. ¨ Configure the PowerCenter Repository Service. After you create a PowerCenter Repository Service.CHAPTER 20 PowerCenter Repository Service This chapter includes the following topics: ¨ PowerCenter Repository Service Overview. Each PowerCenter Repository Service manages a single repository. you need to create a database to store the tables. you can choose to create the repository tables. Create the PowerCenter Repository Service to manage the repository. If you do not create the repository tables. Create a PowerCenter Repository Service to manage the metadata in repository database tables. 305 ¨ PowerCenter Repository Service Process Configuration. If you create a PowerCenter Repository Service for an existing repository. you can configure its properties. You need to create a unique PowerCenter Repository Service for each repository in a Informatica domain. 301 ¨ Creating a Database for the PowerCenter Repository. you can create them later or you can associate the PowerCenter Repository Service with an existing repository. 301 . Creating and configuring a PowerCenter Repository Service involves the following tasks: ¨ Create a database for the repository tables. You can configure properties such as the error severity level or maximum user connections. It performs all metadata transactions between the repository database and repository clients. You can use the existing database. 302 ¨ Creating the PowerCenter Repository Service. 302 ¨ PowerCenter Repository Service Configuration. ¨ Create the PowerCenter Repository Service. Before you can create the repository tables. A PowerCenter Repository Service manages the repository. you do not need to create a new database. 309 PowerCenter Repository Service Overview A PowerCenter repository is a collection of database tables containing metadata.

Although you can create a PowerCenter Repository Service without a license. Determine the code page to use for the PowerCenter repository. you need a license to run the service. In the Domain Actions menu.Creating a Database for the PowerCenter Repository Before you can manage a repository with a PowerCenter Repository Service. click New > PowerCenter Repository Service. When setting up an IBM DB2 EEE database. When you create the new PowerCenter Repository Service. Tip: You can optimize repository performance on IBM DB2 EEE databases when you store a PowerCenter repository in a single-node tablespace. you can move the PowerCenter Repository Service into a folder after you create it. click the Domain tab. the database administrator must define the database on a single node. complete the following tasks: ¨ Determine repository requirements. 3. global. In the Navigator. you need a database to hold the repository database tables. do not create the repository on an overloaded machine. Tip: After you create the PowerCenter Repository Service. The PowerCenter Repository Service uses the character set encoded in the repository code page when writing data to the repository. Creating a PowerCenter Repository Service 1. ¨ Determine code page. If you create a repository in a database with an existing repository. the create operation fails. 302 Chapter 20: PowerCenter Repository Service . You can create the repository on any supported database system. Determine whether the repository needs to be version-enabled and whether it is a local. you can specify a compatible code page. or standalone repository. The Create New Repository Service dialog box appears. you need a license to configure some options related to version control and high availability. 2. Use the database management system client to create the database. In the Administrator tool. The repository code page must be compatible with the code pages for the PowerCenter Client and all application services in the Informatica domain. The repository database name must be unique. you cannot change the code page in the PowerCenter Repository Service properties. You must delete the existing repository in the target database before creating the new repository. To change the repository code page after you create the PowerCenter Repository Service. To protect the repository and improve performance. ¨ Verify license. The machine running the repository database system must have a network connection to the node that runs the PowerCenter Repository Service. back up the repository and restore it to a new PowerCenter Repository Service. Before You Begin Before you create a PowerCenter Repository Service. Creating the PowerCenter Repository Service Use the Administrator tool to create a PowerCenter Repository Service. In addition. Verify that you have a valid license to run application services. Note: If you do not select a folder. select the folder where you want to create the PowerCenter Repository Service.

To apply changes. restart the PowerCenter Repository Service. If you select a license with the high availability option. restart the PowerCenter Repository Service. Type of database storing the repository. Also. For example. You can also move the PowerCenter Repository Service to a different folder after you create it. License Primary Node Backup Nodes Database Type Code Page Connect String Username Password TablespaceName Creating the PowerCenter Repository Service 303 . Required if you do not select a license with the high availability option. Repository code page. It also cannot contain spaces or the following special characters: `~%^*+={}\. Node on which the service process runs by default. It cannot exceed 128 characters or begin with @.:'"/?. To apply changes. Node Node on which the service process runs. Click Select Folder to choose a different folder. The PowerCenter Repository Service uses the character set encoded in the repository code page when writing data to the repository. the PowerCenter Repository Service creates all repository tables in the same tablespace. Must be in 7-bit ASCII. To apply changes. The name is not case sensitive and must be unique within the domain. Set up this account using the appropriate database client tools.world for Oracle. you can assign a license later. restart the PowerCenter Repository Service. To apply changes. restart the PowerCenter Repository Service.<>|!()][ The PowerCenter Repository Service and the repository have the same name. The description cannot exceed 765 characters. Enter values for the following PowerCenter Repository Service options. Required if you select a license with the high availability option.4. You cannot change the code page in the PowerCenter Repository Service properties after you create the PowerCenter Repository Service. you must have the team-based development option to create a versioned repository. Optional if you select a license with the high availability option. Tablespace name for IBM DB2 and Sybase repositories. this property does not appear.. This property appears if you select a license with the high availability option. The options included in the license determine the selections you can make for the repository. Nodes on which the service process can run if the primary node is unavailable. Native connection string the PowerCenter Repository Service uses to access the repository database. License that allows use of the service. Description Location Description of PowerCenter Repository Service. Domain and folder where the service is created. Account for the repository database. use servername@dbname for Microsoft SQL Server and dbname. If you do not select a license when you create the service. Repository database password corresponding to the database user. The following table describes the PowerCenter Repository Service options: Property Name Description Name of the PowerCenter Repository Service. When you specify the tablespace name. For example. you need the high availability option to run the PowerCenter Repository Service on more than one node. To apply changes. This property appears if you select a license with the high availability option. You cannot use spaces in the tablespace name. restart the PowerCenter Repository Service. The characters must be compatible with the code page of the repository.

world Sybase sybaseserver@mydatabase 304 Chapter 20: PowerCenter Repository Service . If you do not select these options during service creation.Property Description To improve repository performance on IBM DB2 EEE repositories. Otherwise. specify a connect string for that connection. To apply changes. or both. Select one of the following options: . Enable the Repository Service Enables the service. verify that users and groups with privileges for the PowerCenter Repository Service exist in the current domain. During synchronization. you cannot later convert the repository to a local repository or to a nonversioned repository. specify a tablespace name with one node.Do not create repository content. When you select this option. However. Database Connect Strings When you create a database connection. If you create a PowerCenter Repository Service for a repository with existing content and the repository existed in a different Informatica domain. The following table lists the native connect string syntax for each supported database: Database IBM DB2 Microsoft SQL Server Oracle Connect String Syntax <database name> <server name>@<database name> <database name>. Click OK. The option to enable version control appears if you select a license with the high availability option.world (same as TNSNAMES entry) <server name>@<database name> Example mydatabase sqlserver@mydatabase oracle. 5. Select if content exists in the database or if you plan to create the repository content later. You can use infacmd to export users and groups from the source domain and import them into the target domain. you can select them later. Optionally. . you need to click the Enable button to run the service. users and groups that do not exist in the current domain are deleted from the repository. enable version control. choose to create a global repository. The PowerCenter Repository Service uses native connectivity to communicate with the repository database. restart the PowerCenter Repository Service. the service starts running when it is created. The Service Manager periodically synchronizes the list of users and groups in the repository with the users and groups in the domain configuration database. if you select the options during service creation. Select if no content exists in the database. You need a valid license to run a PowerCenter Repository Service.Create repository content. Creation Mode Creates or omits new repository content. 6.

¨ Database properties. License object you assigned the PowerCenter Repository Service to when you created the service. The following table describes the general properties for a PowerCenter Repository Service: Property Name Description License Description Name of the PowerCenter Repository Service. select the Properties view. and then click Edit in the General Properties section. If the node becomes unavailable. you can designate primary and backup nodes to run the service. Node in the Informatica domain that the PowerCenter Repository Service runs on. password. ¨ Node assignments. the service runs on the primary node. Node Assignments If you have the high availability option. the service fails over to a backup node. Configure repository properties. ¨ Custom properties. You cannot edit this property. Primary Node Repository Properties You can configure some of the repository properties when you create the service. The Properties tab for the service appears. Use the Administrator tool to configure the following types of PowerCenter Repository Service properties: ¨ Repository properties. such as the database user name. PowerCenter Repository Service Configuration 305 . select the PowerCenter Repository Service in the Navigator. Configure repository database properties. If you have the high availability option. To view and update properties. select the PowerCenter Repository Service in the Navigator. such as the Operating Mode. ¨ Advanced properties. such as the maximum connections and locks on the repository. General Properties To edit the general properties. you must first disable the service. and connection string.PowerCenter Repository Service Configuration After you create a PowerCenter Repository Service. You cannot edit this property. configure the primary and backup nodes to run the service. Configure repository properties that are unique to your Informatica environment or that apply in special cases. you can configure it. By default. To assign the PowerCenter Repository Service to a different node. Description of the PowerCenter Repository Service. Configure advanced repository properties. Use custom properties only if Informatica Global Customer Support instructs you to do so.

groups. the PowerCenter Repository Service creates all repository tables in the same tablespace. you might need to change the database user name and password. To improve repository performance on IBM DB2 EEE repositories. For example. restart the PowerCenter Repository Service. Creates a global repository. the PowerCenter Repository Service must be running in exclusive mode. Security Audit Trail Global Repository Version Control Database Properties Database properties provide information about the database that stores the repository metadata. The following table describes the database properties: Property Database Type Description Type of database storing the repository. If the repository is a global repository. Code Page 306 Chapter 20: PowerCenter Repository Service . restart the PowerCenter Repository Service. Tracks changes made to users. After you enable a repository for version control. such as promoting a local repository to a global repository or enabling version control. Table Space Name Tablespace name for IBM DB2 and Sybase repositories. you may need to modify some of these properties. To enable a repository for version control. You cannot use spaces in the tablespace name. you must run the PowerCenter Repository Service in exclusive mode. When you specify the tablespace name. For example. This property appears if you have the team-based development option. To promote a local repository to a global repository. and permissions. Repository code page. This is a read-only field. You specify the database properties when you create the PowerCenter Repository Service. You cannot change the tablespace name in the repository database properties after you create the service. privileges. specify a tablespace name with one node. use servername@dbname for Microsoft SQL Server and dbname. To apply changes. restart the PowerCenter Repository Service. restart the PowerCenter Repository Service. you cannot revert back to a local repository. To apply changes. Run the PowerCenter Repository Service in exclusive mode to perform some administrative tasks. To apply changes. To apply changes. If you create a PowerCenter Repository Service with the wrong tablespace name.The following table describes the repository properties: Property Operating Mode Description Mode in which the PowerCenter Repository Service is running.world for Oracle. Connect String Native connection string the PowerCenter Repository Service uses to access the database containing the repository. The Log Manager tracks the changes. The PowerCenter Repository Service uses the character set encoded in the repository code page when writing data to the repository. or you might want to adjust the database connection timeout. delete the PowerCenter Repository Service and create a new one with the correct tablespace name. Values are Normal and Exclusive. you cannot disable the version control. Creates a versioned repository. You cannot change the code page in the PowerCenter Repository Service properties after you create the PowerCenter Repository Service. After you create a repository.

Number of rows to fetch each time an array database operation is issued. If the PowerCenter Repository Service tries to establish more connections than specified for DatabasePoolSize. When you enable this option. Database Username Account for the database containing the repository. To apply changes. Default is 180 seconds. Default is disabled. restart the PowerCenter Repository Service. . Default is 100. the repository database must meet the following page size requirements: . restart the PowerCenter Repository Service.Microsoft SQL Server: Database page size 8 KB or greater. such as insert or fetch. The user name that starts the PowerCenter Repository Service must be a valid Windows user with access to the Microsoft SQL Server database. it times out the connection after the number of seconds specified for DatabaseConnectionTimeout.Property Optimize Database Schema Description Enables optimization of repository database schema when you create repository contents or back up and restore an IBM DB2 or Microsoft SQL Server repository. To use this option. To apply changes. Using Varchar columns improves repository performance because it reduces disk input and output and because the database buffer cache can cache Varchar columns. Database Password Database Connection Timeout Database Array Operation Size Database Pool Size Maximum number of connections to the repository database that the PowerCenter Repository Service can establish. To apply changes. Repository database password corresponding to the database user.IBM DB2: Database page size 4 KB or greater. Default is 500. restart the PowerCenter Repository Service. Period of time that the PowerCenter Repository Service tries to establish or reestablish a connection to the database system. Must be in 7-bit ASCII. Required Comments for Checkin PowerCenter Repository Service Configuration 307 . restart the PowerCenter Repository Service. Set up this account using the appropriate database client tools. the Repository Service creates repository tables using Varchar(2000) columns instead of CLOB columns wherever possible. To apply changes. restart the PowerCenter Repository Service. Name of the owner of the repository tables for a DB2 repository. Table Owner Name Advanced Properties Advanced properties control the performance of the PowerCenter Repository Service and the repository database. Requires users to add comments when checking in repository objects. Minimum is 20. To apply changes. Note: You can use this option for DB2 databases only. At least one temporary tablespace with page size 16 KB or greater. The following table describes the advanced properties: Property Authenticate MS-SQL User Description Uses Windows authentication to access the Microsoft SQL Server database.

at which the PowerCenter Repository Service checks for idle database connections. When you enable repository agent caching. Maximum number of connections the repository accepts from repository clients. If a resilience timeout exceeds the limit. Specify one of the following message levels: . Minimum is 3. the log includes all errors at that level and above. Default is 50. the service uses the domain resilience timeout.Debug When you specify a severity level. For example. restart the PowerCenter Repository Service. Default is 180 seconds. in seconds. Default is Yes.Fatal . Minimum number of idle database connections allowed by the PowerCenter Repository Service. Maximum amount of time that the service holds on to resources to accommodate resilience timeouts. You can increase the number of objects if there is available memory on the machine where the PowerCenter Repository Service process runs. Interval. Allows you to modify metadata in the repository when repository agent caching is enabled.Property Minimum Severity for Log Entries Description Level of error messages written to the PowerCenter Repository Service log. If a connection is idle for a period of time greater than this Agent Cache Capacity Allow Writes With Agent Caching Heart Beat Interval Maximum Active Users Maximum Object Locks Database Pool Expiration Threshold Database Pool Expiration Timeout 308 Chapter 20: PowerCenter Repository Service . If blank.Trace .000. You might want to disable writes to improve performance in a production environment where the PowerCenter Integration Service makes all changes to repository metadata. Maximum number of locks the repository places on metadata objects. fatal. Repository agent caching provides optimal performance of the repository when you run workflows. and you set this threshold to 5. if there are 20 idle connections. the limit takes precedence. Default is 5. Default is 60 seconds. Default is Yes. Use Trace or Debug if Informatica Global Customer Support instructs you to use that logging level for troubleshooting purposes.Error . When you allow writes. error. For example. The value must not be less than 100. Resilience Timeout Period of time that the service tries to establish or reestablish a connection to another service.Warning . Number of objects that the cache can contain when repository agent caching is enabled. If blank. Default is INFO.000. To apply changes. This property limits the resilience timeouts for client applications connecting to the service.Info . Default is 200. if the severity level is Warning. and warning messages are logged. Default is 10. the PowerCenter Repository Service process caches metadata requested by the PowerCenter Integration Service. the PowerCenter Repository Service closes no more than 15 connections. Interval at which the PowerCenter Repository Service verifies its connections with clients of the service. the PowerCenter Repository Service process flushes the cache each time you save metadata through the PowerCenter Client tools. Default is 180 seconds. Limit on Resilience Timeout Repository Agent Caching Enables repository agent caching. the service uses the domain limit on resilience timeouts.

Configure PowerCenter Repository Service process properties that are unique to your Informatica environment or that apply in special cases. To view and update properties. complete the following tasks: ¨ Make sure Metadata Manager is running.600 (1 hour). The following table describes the Metadata Manager Service properties: Property Metadata Manager Service Resource Name Description Name of the Metadata Manager Service used to run data lineage. Default is 3. ¨ Load the PowerCenter repository metadata.592. To access data lineage from the Designer. the PowerCenter Repository Service deletes MX data for old versions of mappings when you check in a new version. Maximum is 2. Default is disabled. Before you configure data lineage for a PowerCenter repository. Configure environment variables for each PowerCenter Repository Service process. Minimum is 300. A PowerCenter Repository Service does not have custom properties when you initially create it. Use custom properties only at the request of Informatica Global Customer Support. Create a Metadata Manager Service in the Administrator tool or verify that an enabled Metadata Manager Service exists in the domain that contains the PowerCenter Repository Service for the PowerCenter repository. PowerCenter Repository Service Process Configuration Use the Administrator tool to configure the following types of PowerCenter Repository Service process properties: ¨ Custom properties. Custom Properties Custom properties include properties that are unique to your Informatica environment or that apply in special cases. ¨ Environment variables. PowerCenter Repository Service Process Configuration 309 . When disabled. Select from the available Metadata Manager Services in the domain. select a PowerCenter Repository Service in the Navigator and click the Processes view. Name of the PowerCenter resource in Metadata Manager. Create a resource for the PowerCenter repository in Metadata Manager and load the PowerCenter repository metadata into the Metadata Manager warehouse.Property Description value. Metadata Manager Service Properties You can access data lineage analysis for a PowerCenter repository from the PowerCenter Designer. the PowerCenter Repository Service can close the connection. you configure the Metadata Manager Service properties for the PowerCenter Repository Service.000 (30 days). Preserve MX Data for Old Mappings Preserves MX data for old versions of mappings.

the PowerCenter Integration Service reads from and writes to databases using the UTF-8 code page. However. you have a Shift-JIS repository that requires that the code page environment variable be set to Shift-JIS. All PowerCenter Integration Services and PowerCenter Repository Services that run on this node use the same environment variable. Use custom properties only at the request of Informatica Global Customer Support. and IBM DB2 uses DB2CODEPAGE. Set the environment variable on the node to UTF-8. Oracle uses NLS_LANG. For example. You can configure a PowerCenter Repository Service process to use a different value for the database client code page environment variable than the value set for the node. Set the database client path environment variable for the PowerCenter Repository Service process if the PowerCenter Repository Service process requires a different database client than another PowerCenter Repository Service process that is running on the same node. Environment Variables The database client path on a node is controlled by an environment variable. For example. The database client code page on a node is usually controlled by an environment variable. The PowerCenter Integration Service requires that the code page environment variable be set to UTF-8. A PowerCenter Repository Service process does not have custom properties when you initially create it. Then add the environment variable to the PowerCenter Repository Service process properties and set the value to Shift-JIS. You can configure the code page environment variable for a PowerCenter Repository Service process when the PowerCenter Repository Service process requires a different database client code page than the PowerCenter Integration Service process running on the same node. 310 Chapter 20: PowerCenter Repository Service .Custom Properties Custom properties include properties that are unique to the Informatica environment or that apply in special cases.

restore. 312 ¨ Operating Mode. ¨ Register and unregister a local repository. 323 ¨ Copying Content from Another Repository. ¨ Back up. 311 ¨ PowerCenter Repository Service and Service Processes. 315 ¨ Enabling Version Control. 325 ¨ Repository Plug-in Registration. A PowerCenter Repository Service manages a single repository. You can use the Administrator tool to complete the following repository tasks: ¨ Enable and disable a PowerCenter Repository Service or service process.CHAPTER 21 PowerCenter Repository Management This chapter includes the following topics: ¨ PowerCenter Repository Management Overview. 320 ¨ Sending Repository Notifications. 326 ¨ Audit Trails. ¨ Create and delete repository content. and delete a repository. ¨ Promote a local repository to a global repository. copy. 323 ¨ Backing Up and Restoring the PowerCenter Repository. ¨ Manage user connections and locks. 311 . 314 ¨ PowerCenter Repository Content. 316 ¨ Managing a Repository Domain. 317 ¨ Managing User Connections and Locks. ¨ Change the operating mode of a PowerCenter Repository Service. 327 PowerCenter Repository Management Overview You use the Administrator tool to manage PowerCenter Repository Services and repository content. 327 ¨ Repository Performance Tuning.

¨ Upgrade a repository. ¨ Upgrade content. PowerCenter Repository Service and Service Processes When you enable a PowerCenter Repository Service. If you have the high availability option. In the Administrator tool . In the Navigator. Enabling a PowerCenter Repository Service 1. as long as the node is available. The PowerCenter Repository Service continues to run on another node that is designated to run the service. If you disable a PowerCenter Repository Service process. You must disable the PowerCenter Repository Service to run it in it exclusive mode. the service can fail over to another node if the current node becomes unavailable. the service process is available to run. ¨ Copy content from another PowerCenter repository. 312 Chapter 21: PowerCenter Repository Management . Enabling and Disabling a PowerCenter Repository Service You can enable the PowerCenter Repository Service when you create it or after you create it. verify that all users are disconnected from the repository. If you disable the PowerCenter Repository Service. the service cannot run on any node until you reenable the service. the PowerCenter Repository Service cannot run on the particular node of the service process.¨ Send repository notification messages. ¨ Back up or restore content. ¨ Register plug-ins. ¨ Create or delete content. if you have the high availability option and you configure a PowerCenter Repository Service to run on a primary node and two backup nodes. 2. ¨ Register or unregister a local repository with a global repository. you enable PowerCenter Repository Service processes on all three nodes. but it may not start. Note: Before you disable a PowerCenter Repository Service. You can send a repository notification to inform users that you are disabling the service. A single process runs at any given time. a service process starts on a node designated to run the service. select the PowerCenter Repository Service. and the other processes maintain standby status. click the Domain tab. ¨ Manage repository plug-ins. ¨ Promote a local repository to a global repository. You need to enable the PowerCenter Repository Service to perform the following tasks in the Administrator tool: ¨ Assign privileges and roles to users and groups for the PowerCenter Repository Service. ¨ Configure permissions on the PowerCenter Repository Service. For example. ¨ Manage user connections and locks. The service is available to perform repository transactions. ¨ Send repository notifications. ¨ Upgrade a PowerCenter Repository Service and its dependent services to the latest service version. When you enable a service process.

5. 2. 3.3. click the Domain tab. select the PowerCenter Repository Service associated with the service process you want to disable. select the PowerCenter Repository Service associated with the service process you want to enable. you can configure the service to run on multiple nodes. PowerCenter Repository Service and Service Processes 313 . disabling a service process does not disable the service if the service is configured to run on multiple nodes. Disabling a PowerCenter Repository Service Process 1. You disable and enable service processes on the Processes view. only one service process is running for the service in the domain. 2. a single process is running for the PowerCenter Repository Service. 4. When you create a PowerCenter Repository Service. In the Disable Repository Service. With the high availability option. 7. Enabling and Disabling PowerCenter Repository Service Processes A service process is the physical representation of a service running on a node. In the Navigator. select to abort service processes immediately or allow service processes to complete. In the Domain tab Actions menu. 4. In the Navigator. In the Administrator tool. In the dialog box that appears. select the PowerCenter Repository Service. On the Domain tab Actions menu. 3. In the Administrator tool . 3. click the Domain tab. service processes are enabled by default on the designated nodes. click the Processes view. Disabling a PowerCenter Repository Service 1. Select the process you want to disable. In the contents panel. click Enable Process to enable the service process on the node. 5. click the Domain tab. select Disable Service. click Enable The status indicator at the top of the contents panel indicates when the service is available. Click OK. 5. If you have the high availability option. even if you do not enable the service. select to abort all service processes immediately or allow services processes to complete. At any given time. 6. In the Domain tab Actions menu. Disabling a service process that is running causes the service to fail over to another node. At any given time. In the contents panel. On the Domain tab Actions menu. 2. In the Navigator. Click OK. In the Administrator tool. The process for a PowerCenter Repository Service is the pmrepagent process. click the Processes view. Enabling a PowerCenter Repository Service Process 1. select Disable Process. Select the process you want to enable. You may want to disable a service process to perform maintenance on the node or to tune performance. 4. The service continues to be available as long as one of the designated nodes for the service is available.

If you have the team-based development option. Upgrade the repository metadata. The Administrator tool prompts you to restart the PowerCenter Repository Service. When you run the PowerCenter Repository Service in exclusive mode. it accepts connection requests from the Administrator tool and pmrep. 5. 6. and click Yes if you want to log out users who are still connected. Set the operating mode to Exclusive. In the Administrator tool. A warning message appears. Register a local repository with a global repository to create a repository domain. A versioned repository can store multiple versions of an object. verify that all users are disconnected from the repository. When the PowerCenter Repository Service runs in exclusive mode. Before running a PowerCenter Repository Service in exclusive mode. you can enable version control for the repository. Promote a local repository to a global repository to build a repository domain. repository agent caching is disabled.Operating Mode You can run the PowerCenter Repository Service in normal or exclusive operating mode. 2. click Edit in the repository properties section. 3. When you run the PowerCenter Repository Service in normal mode. ¨ Register a plug-in. 4. To synchronize the list of users and groups. Register or unregister a repository plug-in that extends PowerCenter functionality. You must stop and restart the PowerCenter Repository Service to change the operating mode. restart the PowerCenter Repository Service. Set the operating mode to exclusive to perform administrative tasks that require a single user to access the repository and update the configuration. ¨ Register a local repository. Running a PowerCenter Repository Service in Exclusive Mode 1. Note: You cannot use pmrep to log in to a new PowerCenter Repository Service running in exclusive mode if the Service Manager has not synchronized the list of users and groups in the repository with the list in the domain configuration database. In the Properties view. Run a PowerCenter Repository Service in exclusive mode to perform the following administrative tasks: ¨ Delete repository content. ¨ Upgrade the PowerCenter repository. click the Domain tab. and you cannot assign privileges and roles to users and groups for the PowerCenter Repository Service. Verify that you have notified users to disconnect from the repository. you allow only one user to access the repository. If a PowerCenter Repository Service has no content associated with it or if a PowerCenter Repository Service has content that has not been upgraded. ¨ Enable version control. Click OK. Delete the repository database tables for the PowerCenter repository. you allow multiple users to access the repository to update content. In the Navigator. select the PowerCenter Repository Service. the PowerCenter Repository Service runs in exclusive mode only. When you run a PowerCenter Repository Service in exclusive mode. ¨ Promote a PowerCenter repository. 314 Chapter 21: PowerCenter Repository Management .

5. On the Domain tab Actions menu. PowerCenter Repository Content 315 . but you cannot convert a global repository to a local repository. enable version control. 4. The Administrator tool prompts you to restart the PowerCenter Repository Service. You can convert a non-versioned repository to a versioned repository at any time. 1. Choose to allow processes to complete or abort all processes. 3. PowerCenter Repository Content Repository content are repository tables in the database. 4. Click OK. Optionally. Enable version control if you are certain you want to use a versioned repository. You can create or delete repository content for a PowerCenter Repository Service. Note: PowerCenter does not provide resilience for a repository client when the PowerCenter Repository Service runs in exclusive mode. Select Normal as the operating mode. In the Navigator. and then click OK. Running a PowerCenter Repository Service in Normal Mode 1. Note: You can also use the infacmd UpdateRepositoryService command to change the operating mode. In the Properties view. In the Administrator tool. 6. Select this option if you are certain you want to create a global repository. click the Domain tab. select Repository Content > Create. choose to create a global repository. You must have the team-based development option to enable version control. In the Administrator tool. select a PowerCenter Repository Service that has no content associated with it. Creating PowerCenter Repository Content You can create repository content for a PowerCenter Repository Service if you did not create content when you created the service or if you deleted the repository content. Optionally. Click OK. The Disable button for the service appears when the service is enabled and running. click Edit in the repository properties section. 5. but you cannot convert a versioned repository to a non-versioned repository. You can promote a local repository to a global repository at any time. In the Navigator. The PowerCenter Repository Service stops and then restarts. select the PowerCenter Repository Service. 2.7. click the Domain tab. 3. The page displays the options to create content. You cannot create content for a PowerCenter Repository Service that already has content. 2. The service status at the top of the right pane indicates when the service has restarted.

In the Administrator tool. 4. choose to unregister local repositories when you delete the content. A versioned repository can store multiple versions of objects. click Repository Content > Delete. 3. In the Navigator. When you delete repository content. After you enable version control for a repository. you can enable version control for a new or existing repository. 3. back up the repository before you delete it. If you enable version control. For example.Deleting PowerCenter Repository Content Delete repository content when you want to delete all metadata and repository database tables from the repository. Note: You can also use the pmrep Delete command to delete repository content. you cannot disable it. you must run the PowerCenter Repository Service in exclusive mode to delete repository content. The activity log displays the results of the delete operation. Change the operating mode of the PowerCenter Repository Service to exclusive. You can also use labels and deployment groups to associate groups of objects and copy them from one repository to another. Upgrading PowerCenter Repository Content You can upgrade a repository to version 9. you also delete all privileges and roles assigned to users for the PowerCenter Repository Service. Click OK. If the repository contains information that you might need later. You might delete the repository content if the metadata is obsolete. password. select the PowerCenter Repository Service from which you want to delete the content. click the Domain tab. In the Administrator tool. 7. When you enable version control for a repository. control development of the object. and track changes. you can maintain multiple versions of an object. On the Domain tab Actions menu. If the repository is a global repository. the repository assigns all versioned objects version number 1. select the PowerCenter Repository Service for the repository you want to upgrade. click the Domain tab. 1. click Repository Contents > Upgrade. The options is available for previous versions of the repository. 2. you must unregister all local repositories. if a Repository Service for one of the local repositories is running in exclusive mode.0. 316 Chapter 21: PowerCenter Repository Management . To delete a global repository. 4. The activity log displays the results of the upgrade operation. 1. 5. 5. Click OK. 6. Enabling Version Control If you have the team-based development option. and security domain. and each object has an active status. Also. On the Domain tab Actions menu. The delete operation does not proceed if it cannot unregister the local repositories. Enter the repository administrator user name and password. In the Navigator. The Security Domain field appears when the Informatica domain contains an LDAP security domain. Enter your user name. Deleting repository content is an irreversible action. you may need to unregister that repository before you delete the global repository. 2.

4. To copy objects from the local repository to the global repository. In the repository properties section of the Properties view. You group repositories in a repository domain to share data and metadata between repositories. ¨ Network connections between the PowerCenter Repository Services and PowerCenter Integration Services. ¨ A PowerCenter Repository Service created and configured to manage each repository. In the Navigator. 6. making it accessible to all local repositories in the repository domain. click the Domain tab. and security domain. 10. Enable the PowerCenter Repository Service. ¨ Copy objects from or create shortcuts to metadata in the global repository. Enter your user name. A PowerCenter Repository Service accesses the repository faster if the PowerCenter Repository Service process runs on the machine where the repository database resides. Select Version Control. When working in a repository domain. you can perform the following tasks: ¨ Promote metadata from a local repository to a global repository. Managing a Repository Domain 317 . ¨ A license for each local repository you want to create. Ensure that all users disconnect from the PowerCenter repository. the code page of the global repository must be a subset of each local repository code page in the repository domain. click Edit. ¨ Copy objects from the local repository to the global repository. ¨ A database created and configured for each repository. 2. To register a local repository. 8. Click OK. 1. Change the operating mode of the PowerCenter Repository Service to exclusive. 3. ¨ Compatible repository code pages. The Repository Authentication dialog box appears. The repository is now versioned. select the PowerCenter Repository Service. 9. Prerequisites for a PowerCenter Repository Domain Before building a repository domain. Change the operating mode of the PowerCenter Repository Service to normal. the code pages of the local and global repository must be compatible. The Security Domain field appears when the Informatica domain contains an LDAP security domain. 7. In the Administrator tool.You must run the PowerCenter Repository Service in exclusive mode to enable version control for the repository. Managing a Repository Domain A repository domain is a group of linked PowerCenter repositories that consists of one global repository and one or more local repositories. verify that you have the following required elements: ¨ A licensed copy of Informatica to create the global repository. 5. password.

When registering local repositories with a global repository. Create a repository and configure it as a global repository. you cannot change it to a local or standalone repository. Before promoting a repository to a global repository. and security domain must be the same. When the global and local repositories exist in different Informatica domains. To run a session that uses a global shortcut. If the PowerCenter Repository Service is running in normal mode. Alternatively. the PowerCenter Integration Service must access the repository in which the mapping is saved and the global repository with the shortcut information. you can promote an existing local repository to a global repository. 4. After you promote a repository. 3. This user account must have privileges for the following services: ¨ The local PowerCenter Repository Service associated with the PowerCenter Integration Service ¨ The global PowerCenter Repository Service in the domain 2. select the PowerCenter Repository Service for the repository you want to promote. 6. Although the user name. Click OK. 2. If users are connected to the repository. Register local repositories with the global repository. 3. and click OK. If the PowerCenter Repository Service is not enabled. Configure the user account used to access the repository associated with the PowerCenter Integration Service. the user must have an identical user name. Enter your user name. To promote a repository to a global repository. click the Domain tab. you can register local repositories to create a repository domain. In the repository properties section for the service. 4. password. Create user accounts for users performing cross-repository work. password. change the operating mode to exclusive. click Edit. In the Navigator. The Repository Authentication dialog box appears. and security domain in each Informatica domain. make sure the repository code page is compatible with each local repository you plan to register. After a local repository is registered. you can connect to the global repository from the local repository and you can connect to the local repository from the global repository. Promoting a Local Repository to a Global Repository You can promote an existing repository to a global repository.Building a PowerCenter Repository Domain Use the following steps as a guideline to connect separate PowerCenter repositories into a repository domain: 1. After you promote a repository to a global repository. A user who needs to connect to multiple repositories must have privileges for each PowerCenter Repository Service. Select Global Repository. You enable this behavior by configuring the user account used to access the repository associated with the PowerCenter Integration Service. password. 8. the value of the GlobalRepository property is true in the general properties for the PowerCenter Repository Service. the global and local repository code pages must be compatible. click Enable. 5. In the Administrator tool. the user can be a member of different user groups and can have a different set of privileges for each PowerCenter Repository Service. You can specify that a repository is the global repository when you create the PowerCenter Repository Service. and security domain. 318 Chapter 21: PowerCenter Repository Management . The Security Domain field appears when the Informatica Domain contains an LDAP security domain. After you promote a local repository. you need to change the operating mode of the PowerCenter Repository Service to exclusive. 1. 7. have them disconnect before you run the repository in exclusive mode.

password. on the Domain Actions menu. To edit the connection information for a linked domain. To unregister a local repository. click Repository Domain > Register Local Repository. and security domain for the user who manages the global PowerCenter Repository Service. Click Add to add more than one domain to the list. change the operating mode to exclusive. 1. if a repository domain has three local repositories and one global repository. enter the following information: Field Domain Name Host Name Description Name of a Informatica Domain that you want to link to. Click Done to save the list of domains. click Enable. If the PowerCenter Repository Service is in a domain that does not appear in the list of Informatica domains. Managing a Repository Domain 319 . 6. If the PowerCenter Repository Service is not enabled. To register a local repository. 4. you can register all local repositories with the copy of the global repository. Host Port 7. Enter the user name. go to the section for the domain you want to update and click Edit. click Repository Domain > Unregister Local Repository. Skip to step 10. it must have four PowerCenter Repository Services. the code pages of the local and global repositories must be compatible. 2. In the Navigator. The Manage List of Domains dialog box appears. go to the section for the domain you want to remove and click Delete. Machine hosting the master gateway node for the linked domain. You can copy objects from the local repository to the global repository and create shortcuts. Gateway port number for the linked domain.When you register a local repository. 5. 3. The machine hosting the master gateway for the local Informatica Domain must have a network connection to this machine. For example. 9. If the PowerCenter Repository Service is running in normal mode. Select the PowerCenter Repository Service for the global repository. and repeat step 6 for each domain. Continue to the next step. on the Domain Actions menu. You can move a registered local or global repository to a different PowerCenter Repository Service in the repository domain or to a different Informatica domain. select the PowerCenter Repository Service associated with the local repository. The PowerCenter Repository Service reestablishes all global shortcuts unless you delete objects from the copied repository.Registering a Local Repository You can register local repositories with a global repository to create a repository domain. To add a domain to the list. the PowerCenter Repository Service re-establishes global shortcuts. 8. You can also copy objects from the global repository to the local repository. if you create a copy of the global repository and delete the original. The Security Domain field appears when the Informatica Domain contains an LDAP security domain. If you unregister a repository from the global repository and register it again. A separate PowerCenter Repository Service manages each repository. Select the Informatica domain of the PowerCenter Repository Service for the global repository. The PowerCenter Repository Services and repository databases do not need to run on the same machine. To remove a linked domain from the list. For example. 10. click Manage Domain List to update the list. you improve performance for repository transactions if the PowerCenter Repository Service process runs on the same machine where the repository database resides. However.

320 Chapter 21: PowerCenter Repository Management . For each local repository. Unregister the local repositories. you can view the name of the global repository and the Informatica domain where it resides. Enter the user name. Click OK. The repository creates different types of locks depending on the task. Viewing Registered Local and Global Repositories For a global repository. View object locks and lock type. 1. To move a global repository to another Informatica domain. Create the PowerCenter Repository Services using existing content. View all user connections to the repository. For a local repository. password. you can view a list of all the registered local repositories. Register the local repositories. Moving Local and Global Repositories If you need to move a local or global repository to another Informatica domain. The PowerCenter repository locks repository objects and folders by user. follow the procedure to create a PowerCenter Repository Service using the existing repository content in the source Informatica domain. a list of local repositories appears. For each repository in the target domain. A PowerCenter Repository Service manages a single repository. On the Domain tab Actions menu.11. The name of a repository is the same as the name of the PowerCenter Repository Service that manages it. Note: The Administrator tool displays a message if a local repository is not registered with a global repository or if a global repository has no registered local repositories. 2. complete the following steps: 1. Likewise. follow the procedure to register a local repository with a global repository. The repository uses locks to prevent users from duplicating or overwriting work. 3. You can use infacmd to export users and groups from the source domain and import them into the target domain. if a local repository is registered with a global repository. The Service Manager periodically synchronizes the list of users and groups in the repository with the users and groups in the domain configuration database. click Repository Domain > View Registered Repositories. For each local repository in the target Informatica domain. For a global repository. Managing User Connections and Locks You can use the Administrator tool to manage user connections and locks and perform the following tasks: ¨ View locks. and security domain for the user who manages the local PowerCenter Repository Service. During synchronization. users and groups that do not exist in the target domain are deleted from the repository. follow the procedure to unregister a local repository from a global repository. unregister all local repositories associated with the global repository. select the PowerCenter Repository Service that manages the local or global repository. 12. In the Navigator. 2. ¨ View user connections. Verify that users and groups with privileges for the source PowerCenter Repository Service exist in the target domain. the name of the global repository appears.

In the Administrator tool. Folder in which the locked object is saved. version. In the details panel. Terminate residual connections and locks. Name assigned to the lock. Connection status. 3. Repository client associated with the connection. click the Domain tab. Type of object. write-intent. To view user connection details: 1. click the Properties view. mapping. click the Connections & Locks view. In the details panel. You might want to view user connections to verify all users are disconnected before you disable the PowerCenter Repository Service. Managing User Connections and Locks 321 . 3. The following table describes the object lock information: Column Name Server Thread ID Folder Object Type Object Name Lock Type Lock Name Description Identification number assigned to the repository connection. 4. In the Navigator. In the contents panel. click the Locks view. or source. or execute. In the Navigator. click the Connections & Locks view. 1. you release all locks associated with that connection. select the PowerCenter Repository Service with the locks that you want to view. click the Domain tab. 4. In the contents panel. Name of the locked object. Security domain of the user. Type of lock: in-use. Viewing User Connections You can view user connection details in the Administrator tool. User name associated with the connection.¨ Close connections and release locks. such as folder. 2. select the PowerCenter Repository Service with the locks that you want to view. The following table describes the user connection information: Property Connection ID Status Username Security Domain Application Description Identification number assigned to the repository connection. When you close a connection. In the Administrator tool. 2. Viewing Locks You can view locks and identify residual locks in the Administrator tool.

Important: Closing an active connection can cause repository inconsistencies. Port number of the machine hosting the repository client used to communicate with the repository. 3. Name of the machine running the application. the PowerCenter Repository Service detects and closes the residual connection. you close all connections for that service. ¨ A PowerCenter Client. In the contents panel. The Delete Selected Connection dialog box appears. and security domain. 7. select a connection. If an object or folder is locked when one of these events occurs. the PowerCenter Repository Service does not immediately disconnect a user from the repository. To close a connection and release locks: 1. PowerCenter Integration Service. Enter a user name. This can happen in the following situations: ¨ Network problems occur. In the Domain tab Actions menu. When the PowerCenter Repository Service closes the connection. it also releases all repository locks associated with the connection. You can enter the login information associated with a particular connection. 6. 4. Click OK. Closing User Connections and Releasing Locks Sometimes. In the contents panel. select the PowerCenter Repository Service with the connection you want to close. In the Navigator. or database machine shuts down improperly. Identifier assigned to the PowerCenter Repository Service process.Property Service Host Name Host Address Host Port Process ID Login Time Last Active Time Description Service that connects to the PowerCenter Repository Service. Time of the last metadata transaction between the repository client and the repository. 2. Close residual connections only. A PowerCenter Integration Service may have multiple connections open to the repository. 5. select Delete User Connection. PowerCenter Repository Service. The repository has a residual connection when the repository client or machine is shut down but the connection remains in the repository. A residual repository connection also retains all repository locks associated with the connection. The Security Domain field appears when the Informatica domain contains an LAP security domain. password. IP address for the host machine. In the Administrator tool. This lock is called a residual lock. or you can enter the login information for the user who manages the PowerCenter Repository Service. click the Domain tab. click the Connections & Locks view. If a system or network problem causes a repository client to lose connectivity to the repository. The details panel displays connection properties in the properties view and locks in the locks view. Time when the user connected to the repository. If you close one PowerCenter Integration Service connection to the repository. the repository does not release the lock. 322 Chapter 21: PowerCenter Repository Management .

1. The PowerCenter Repository Service sends the notification message to the PowerCenter Client users. 3. you must assign the operating system profiles to the folders. the PowerCenter Repository Service does not back up the folder assignments. View the general properties of the node to determine the path of the backup directory. users and groups that do not exist in the target domain are deleted from the repository. select Notify Users. the PowerCenter Repository Service stores the file in the backup location you specify for the node. the PowerCenter Repository Service saves the repository in a binary file. 3. The message text appears on the Notifications tab of the PowerCenter Client Output window. verify that users and groups with privileges for the source PowerCenter Repository Service exist in the target domain. 2. 1. During synchronization. In the Domain tab Actions menu. Backing Up and Restoring the PowerCenter Repository Regularly back up repositories to prevent data loss due to hardware or software problems. 4. In the Navigator. The Notify Users window appears. For example. you might send a notification message to ask users to disconnect before you promote a local repository to a global repository.The PowerCenter Repository Service closes connections and releases all locks associated with the connections. Sending Repository Notifications 323 .rep for all repository backup files. Click OK. select the PowerCenter Repository Service for the repository you want to back up. The PowerCenter Repository Service uses the extension . and code page information. connection information. In the Administrator tool. On the Domain tab Actions menu. you can restore the content of the repository from this binary file. You specify the backup location when you set up the node. The Service Manager periodically synchronizes the list of users and groups in the repository with the users and groups in the domain configuration database. Select the PowerCenter Repository Service in the Navigator. If you need to recover the repository. A message box informs users that the notification was received. including the repository objects. click the Domain tab. When you back up a repository. Before you back up a repository and restore it in a different domain. You can use infacmd to export users and groups from the source domain and import them into the target domain. select Repository Contents > Back Up. 2. If you back up a repository that has operating system profiles assigned to folders. Sending Repository Notifications You create and send notification messages to all users connected to a repository. You might want to send a message to notify users of scheduled repository maintenance or other tasks that require you to disable a PowerCenter Repository Service or run it in exclusive mode. After you restore the repository. Backing Up a PowerCenter Repository When you back up a repository. Enter the message text.

You might want to skip these operations to increase performance when you restore the repository. 4. 1. If you do not include the . The results of the backup operation appear in the activity log. Verify that the repository license includes the license keys necessary to restore the repository backup file. If you back up a repository through pmrep.rep. password. If you use the same file name that you used for a previous backup file. Choose to skip or back up workflow and session logs. On the Domain tab Actions menu. For example. If a repository exists at the target database location. The list of the backup files shows the repository version and the options skipped during the backup. In the Navigator. 7. Click OK. To overwrite an existing repository backup file. Select a backup file to restore. You can also view a list of existing backup files in the Administrator tool. For example. If you specify a file name that already exists in the repository backup directory and you do not choose to replace the existing file. you must provide a file extension of . Use an easily distinguishable name for the file. When you restore a repository. In the Administrator tool. 6. click the Domain tab. 2. the PowerCenter Repository Service restores the repository with a new repository ID and deletes the log event files. On the Domain tab Actions menu. click Repository Contents > Restore. The Restore Repository Contents options appear. and security domain. select whether or not to replace the existing file with the new backup file. select the PowerCenter Repository Service that manages the repository content you want to restore. select Repository Contents > View Backup Files. you must have a database available for the repository. Enter your user name. if the name of the repository is DEVELOPMENT. 5. 1. deployment group history. You can restore the repository in a database that has a compatible code page with the original database. select Replace Existing File. you must use the earlier product version to restore the repository. you must delete it before you restore a repository backup file. Viewing a List of Backup Files You can view the backup files you create for a repository in the backup directory where they are saved. 3. you might name the file DEVELOPMENTMay07.4. Select whether or not to restore the repository as new. the PowerCenter Repository Service appends that extension to the file name. 8. select the PowerCenter Repository Service for a repository that has been backed up. 3.rep to view it in the Administrator tool. In the Navigator. Informatica restores repositories from the current product version. If you have a backup file from an earlier product version. When you restore a repository as new. and MX data. and the backup occurs on May 7. 2.rep extension. Restoring a PowerCenter Repository You can restore metadata from a repository binary backup file. 324 Chapter 21: PowerCenter Repository Management . you must have the team-based development option to restore a versioned repository. The Security Domain field appears when the Informatica domain contains an LDAP security domain. Enter a file name and description for the repository backup file. the PowerCenter Repository Service does not back up the repository.

the copy operation fails. 2. Alternatively. Skipping this data can increase performance.Note: When you copy repository content. click the Domain tab. You can copy repository content to preserve the original repository before upgrading. Click OK. If repository in the target database already has content. deployment group history. Click OK. Copying Content from Another Repository 325 . In the Administrator tool. you need to promote it to a global repository. After restoring the repository. you can delete the content from a PowerCenter Repository Service that already has content associated with it. You must back up the repository the target database and delete its content before copying the repository content. choose to skip restoring the workflow and session logs. You must copy content into an empty repository. 3. 6. In the Navigator. set the creation mode to create the PowerCenter Repository Service without content. You can also copy repository content when you need to move a repository from development into production. The dialog box displays the options for the Copy From operation. When you create the PowerCenter Repository Service. 7. 6. password. Note: When you restore a global repository. 1. To copy repository content. click Repository Contents > Copy From. Copying repository content provides a quick way to copy the metadata that you want to use as a basis for a new repository. To skip copying the workflow and session logs. 5. the repository becomes a standalone repository. Also. you must select a code page that is compatible with the original repository. and Metadata Exchange (MX) data. you create the repository as new. and security domain for the user who manages the repository from which you want to copy content. select the check boxes in the advanced options. back up and delete existing repository content before copying in the new content. Enter a user name. select the PowerCenter Repository Service to which you want to add copied content. Copying Content from Another Repository Copy content into a repository when no content exists for the repository and you want to use the content from a different repository. deployment group history. If necessary. and Metadata Exchange (MX) data to improve performance. 5. The source PowerCenter Repository Service and the PowerCenter Repository Service to which you want to add copied content must be in the same domain and it must be of the same service version. Select the name of the PowerCenter Repository Service. Optionally. The activity log indicates whether the restore operation succeeded or failed. On the Domain Actions menu. you must create the PowerCenter Repository Service for the target repository. The Security Domain field appears when the Informatica domain contains an LDAP security domain. You cannot copy content to a repository that has content. 4. The activity log displays the results of the copy operation.

1. 7. In the Navigator. and security domain. The list of registered plug-ins for a PowerCenter Repository Service appears on the Plug-ins tab. the Remove buttons for plug-ins are disabled. Enter your user name. 2. password. 8. For installation issues specific to the plug-in. The list of registered plug-ins appears. select the PowerCenter Repository Service to which you want to add the plug-in. If the PowerCenter Repository Service is not running in exclusive mode. 2. The results of the registration operation appear in the activity log. For example. 4. click the Browse button to locate the plug-in file. consult the plug-in documentation. 5. The Security Domain field appears when the Informatica Domain contains an LDAP security domain. Repository plug-ins are third-party or other Informatica applications that extend PowerCenter functionality by introducing new repository metadata. password. Run the PowerCenter Repository Service in normal mode. The Security Domain field appears when the Informatica Domain contains an LDAP security domain. Run the PowerCenter Repository Service in normal mode. 6. 9. Registering a Repository Plug-in Register a repository plug-in to add its functionality to the repository. 3. If the plug-in was registered previously and you want to overwrite the registration. and security domain. 6. 4. you can select this option when you upgrade a plug-in to the latest version. Click OK. 326 Chapter 21: PowerCenter Repository Management . the PowerCenter Repository Service must be running in exclusive mode. Run the PowerCenter Repository Service in exclusive mode. Verify that all users are disconnected from the repository before you unregister a plug-in. click the Plug-ins view. 5.Repository Plug-in Registration Use the Administrator tool to register and remove repository plug-ins. Click OK. You can also update an existing repository plug-in. select Register Plug-in. Click the Plug-ins view. select the PowerCenter Repository Service from which you want to remove the plug-in. Enter your user name. In the Navigator. In the Domain tab Actions menu. Run the PowerCenter Repository Service in exclusive mode. select the check box to update the existing plug-in registration. 1. Unregistering a Repository Plug-in To unregister a repository plug-in. 3. On the Register Plugin page. 7. In the contents panel. Select a plug-in and click the unregister Plug-in button. The PowerCenter Repository Service registers the plug-in with the repository.

Backup. ¨ Changing the owner or permissions for a deployment group. these statistics can quickly become outdated. Informatica identifies and updates the statistics of all repository tables and indexes when you copy. You can also skip this information when you use the pmrep commands. When you back up. upgrade. and SQL query optimizers may not choose the best query plan. Repository Statistics Almost all PowerCenter repository tables use at least one index to speed up queries. repository operations gradually become slower. Repository Performance Tuning Informatica includes features that allow you improve the performance of the repository. and Restore Processes Large repositories can contain a large volume of log and historical information that slows down repository service performance. The audit trail logs the following operations: ¨ Changing the owner or permissions for a folder or connection object. back up. In frequently used repositories. You can also update statistics using the pmrep UpdateStatistics command. The audit trail does not log the following operations: ¨ Changing your own password. ¨ Adding or removing a user or group.Audit Trails You can track changes to users. and restore repositories. Over time. Most databases keep and use column distribution statistics to determine which index to use to execute SQL queries optimally. Audit Trails 327 . groups. You can update statistics and skip information when you copy. In large repositories. This information is not essential to repository service operation. label. you reduce the time it takes to copy. choosing a sub-optimal query plan can have a negative impact on performance. or restore a repository. and permissions on repository objects by selecting the SecurityAuditTrail configuration option in the PowerCenter Repository Service properties in the Administrator tool. or query. Repository Copy. Database servers do not update these statistics continuously. the PowerCenter Repository Service logs security changes to the PowerCenter Repository Service log. restore. When you enable the audit trail. back up. or restore the repository. you can choose to skip the following types of information: ¨ Workflow and session logs ¨ Deployment group history ¨ Metadata Exchange (MX) data By skipping this information. or copy a repository.

Before you create a Listener Service. the PowerExchange client on the PowerCenter Integration Service or Data Integration Service node connects to the PowerExchange Listener through the Listener Service. 331 ¨ Service Status of the Listener Service. Use the Administrator tool to manage the service and view service logs. UNIX. 333 PowerExchange Listener Service Overview The PowerExchange Listener Service is an application service that manages the PowerExchange Listener. The Service Manager. the Service Manager 328 . the PowerExchange Listener is also called the Listener Service process. Perform the following tasks to manage the Listener Service: ¨ Create a service.CHAPTER 22 PowerExchange Listener Service This chapter includes the following topics: ¨ PowerExchange Listener Service Overview. 333 ¨ Creating a Listener Service. 329 ¨ Properties of the Listener Service. ¨ Enable. 330 ¨ Listener Service Management. 329 ¨ DBMOVER Statements for the Listener Service. 328 ¨ Listener Service Restart and Failover. disable. you can use the Listener Service to manage the PowerExchange Listener process instead of issuing PowerExchange commands such as DTLLST to start the Listener process or CLOSE to stop the Listener process. or Windows machine. When managed by the Listener Service. You can use the Administrator tool or the infacmd command line program to administer the Listener Service. ¨ View the service properties. and restart the service. Listener Service. You can define a PowerExchange Listener service so that when you run a workflow. The PowerExchange Listener manages communication between a PowerExchange client and a data source for bulk data movement and change data capture. install PowerExchange and configure a PowerExchange Listener on the node where you want to create the Listener Service. and PowerExchange Listener process must reside on the same node in the Informatica domain. 332 ¨ Listener Service Logs. ¨ View service logs. On a Linux. When you create a Listener Service.

PWXPC performs warm start processing. and you must restart it. DBMOVER Statements for the Listener Service Before you create a Listener Service. in seconds. SERVICE_TIMEOUT Optional. the session fails. If the Listener Service or the Listener Service process fails on the primary node. if one is defined. For more information. UNIX. If the PowerExchange Listener fails during a PowerCenter session. For the PowerExchange service to fail over successfully. SVCNODE Required. Default is 5. Defines the TCP/IP port on which a named PowerExchange Listener process listens for work requests. the Service Manager restarts the service on the primary node. the backup node must be able to connect to the data source or target. if applicable. the PowerExchange Logger for Linux. If the primary node fails. define statements in the DBMOVER file on the appropriate machines to configure one or more PowerExchange Listener processes and configure the PowerCenter Integration Service to connect to a PowerExchange Listener process through a Listener Service. Use the same port number that you specify for the SVCNODE Port Number configuration property for the service. the Listener Service provides restart and failover capabilities. Listener Service Restart and Failover If you have the PowerCenter high availability option. Specifies the time. see the PowerExchange Interfaces Guide for PowerCenter. Specifies the TCP/IP port on which the PowerExchange Listener process listens for commands from the Listener Service. you also start or stop the PowerExchange Listener. The following table describes the DBMOVER statements that you define on all machines where a PowerExchange Listener process runs: Statement LISTENER Description Required. the Service Manager synchronizes and connects to the PowerExchange Listener on the backup node. and Windows on the backup node as you do on the primary node. the Listener Service fails over to the backup node. After failover.associates it with the PowerExchange Listener on the node. When you start or stop the Listener Service. For CDC sessions. Configure the PowerExchange Listener and. The node name in the LISTENER statement must match the name that you provide in the Start Parameters configuration property when you define the Listener Service. Listener Service Restart and Failover 329 . that a PowerExchange Listener waits to receive heartbeat data from the associated Listener Service before shutting down and issuing an error message.

select the service in the Navigator and click the Properties tab.<>|!()][ Description Location Node Short description of the Listener Service. You can change the properties while the service is running.The following table describes the DBMOVER statement that you define on the PowerCenter Integration Service or Data Integration Service node: Statement NODE Description Configures the PowerCenter Integration Service or Data Integration Service to connect to the PowerExchange Listener process directly or through a Listener Service. the PowerCenter Integration Service or Data Integration Service connects directly to the Listener. the Integration Service connects to the Listener through the Listener Service. . It cannot exceed 128 characters or begin with @. When you run a PowerExchange session. It does not connect through the Listener Service. It also cannot contain spaces or the following special characters: `~%^*+={}\. The NODE statement provides the host name and port number. PowerExchange Listener Service General Properties The following table describes the general properties of a Listener Service: General Property Name Description Read-only. The name is not case sensitive and must be unique within the domain. Name of the Listener Service.If the NODE statement on a PowerCenter Integration Service or Data Integration Service node includes the service_name parameter.If the NODE statement does not include the service_name parameter. 330 Chapter 22: PowerExchange Listener Service . Primary node to run the Listener Service. UNIX. Domain in which the Listener Service is created. The description cannot exceed 765 characters. For more information about customizing the DBMOVER configuration file for bulk data movement or CDC sessions. and Windows Properties of the Listener Service To view the properties of a Listener Service. The service_name parameter identifies the node. and the port parameter in the NODE statement identifies the port number.. the PowerCenter Integration Service or Data Integration Service connects to the PowerExchange Listener based on the way you configure the NODE statement: .:'"/?. but you must restart the service for the properties to take effect. see the following guides: ¨ PowerExchange Bulk Data Movement Guide ¨ PowerExchange CDC Guide for Linux.

This name must match the name in the LISTENER statement in the DBMOVER configuration file. You can include the following parameters: .node_name Required. Nodes used as a backup to the primary node. For the Listener Service. Parameters to include when you start the Listener Service. Specifies the full path and file name for a DBMOVER configuration file that overrides the default dbmover. Listener Service Management 331 . Backup Nodes PowerExchange Listener Service Configuration Properties The following table describes the configuration properties of a Listener Service: General Property Service Process Description Read only.cfg file in the installation directory. This property appears only if you have the PowerCenter high availability option.config=directory Optional. Specifies the full path and file name for any license key file that you want to use instead of the default license. This override license key file must have a file name or path that is different from that of the default file. the service process is Listener. This override file takes precedence over any other override license key file that you optionally specify with the PWX_LICENSE environment variable. Type of PowerExchange process that the service manages. Node name that identifies the Listener Service. Note: In the config and license parameters.license=directory/license_key_file Optional. This override file takes precedence over any other override configuration file that you optionally specify with the PWX_CONFIG environment variable. . Required before you can enable the service. you can assign a license to the service later. you must define a unique SVCNODE port number for each service. SVCNODE Port Number Specifies the port on which the PowerExchange Listener process listens for commands from the Listener Service.key file in the installation directory. This port number must uniquely identify the PowerExchange Listener process to its Listener Service. Include quotes around any path and file name that contains spaces. Use the same port number that you specify in the SVCNODE statement of the DBMOVER file. If you define more than one Listener Service to run on a node. If you do not select a license now. The node_name parameter is required. . Start Parameters Listener Service Management Use the Properties tab in the Administrator tool to configure general or configuration properties for the Listener Service. you must provide the full path only if the file does not reside in the installation directory. Separate the parameters with the space character.General Property License Description License to assign to the service.

or restart a Listener Service from the Administrator tool. Edit the general properties of the service. Configuring the Listener Service Process Properties Use the Processes tab in the Administrator tool to configure the environment variables for each service process. Service Status of the Listener Service You can enable. The PowerExchange Listener Service properties window appears. Edit the configuration properties. Environment Variables for the Listener Service Process You can edit environment variables for a Listener Service process. 2. The following table describes the environment variables for the Listener Service process: Property Environment Variables Description Environment variables defined for the Listener Service process. In the General Properties area of the Properties tab. click Edit.Configuring Listener Service General Properties Use the Properties tab in the Administrator tool to configure Listener Service general properties. Enabling the Listener Service To enable the Listener Service. Click OK. In the Configuration Properties area of the Properties tab. 2. 3. 3. The Edit PowerExchange Listener Service dialog box appears. select the PowerExchange Listener Service. select the service in the Domain Navigator and click Enable the Service. disable. click Edit. 332 Chapter 22: PowerExchange Listener Service . You might disable the Listener Service if you need to temporarily restrict users from using the service. 1. The Edit PowerExchange Listener Service dialog box appears. 1. Configuring Listener Service Configuration Properties Use the Properties tab in the Administrator tool to configure Listener Service configuration properties. select the PowerExchange Listener Service. You might restart a service if you modified a property. In the Navigator. In the Navigator. 4.

Corresponds to the PowerExchange Listener CLOSE FORCE command. Click Actions > New > PowerExchange Listener Service. Note: After you select an option and click OK. 3. optionally select the name of the service. 2. Creating a Listener Service 1. In the Service Name list. 2. You can view Listener Service logs by performing one of the following actions in the Administrator tool: ¨ In the Logs tab. 3.Disabling the Listener Service If you need to temporarily restrict users from using a Listener Service. 4. Stops all processes immediately and shuts down the service. Select one of the following options: ¨ Complete. and click Disable the Service. If you select the Complete option but then want to disable the service more quickly with the Stop or Abort option. Click OK. ¨ Stop. ¨ Abort. Click OK. the Administrator tool displays a busy icon until the service stops. you can disable it. select PowerExchange Listener Service. Click the Domain tab of the Administrator tool. Waits up to 30 seconds for subtasks to complete. ¨ In the Domain tab. In the Service Type column. you must issue the infacmd isp disableService command. 1. see the PowerExchange Command Reference. You can filter on any of the columns. ¨ In the Logs tab. with the most recent messages on top. select the service in the Navigator and click Restart. Messages appear by default in time stamp order. Allows all Listener subtasks to run to completion before shutting down the service and the Listener Service process. and then shuts down the service and the Listener Service process. The Service view of the Logs tab appears. Listener Service Logs 333 . Corresponds to the PowerExchange Listener CLOSE command. Enter the properties for the service. select the Domain view. select Actions > View Logs for Service. Select the service in the Domain Navigator. For more information about the CLOSE and CLOSE FORCE commands. click the Service view. To restart the Listener Service. Restarting the Listener Service You can restart a Listener Service that you previously disabled. The New PowerExchange Listener Service dialog box appears. Enable the Listener Service to make it available. Listener Service Logs The Listener Service generates operational and error log events that the Log Manager collects in the domain.

336 ¨ Logger Service Management. 337 ¨ Service Status of the Logger Service. UNIX. You can run multiple Logger Services on the same node. the PowerExchange Logger is also called the Logger Service process. you can use the Logger Service to manage the PowerExchange Logger process instead of issuing PowerExchange commands such as PWXCCL to start the Logger process or SHUTDOWN to stop the Logger process. and restart the service. and PowerExchange Logger must reside on the same node in the Informatica domain. The Service Manager. 338 ¨ Logger Service Logs. Use the Administrator tool to manage the service and view service logs. ¨ View the service properties.CHAPTER 23 PowerExchange Logger Service This chapter includes the following topics: ¨ PowerExchange Logger Service Overview. You must run one PowerExchange Logger process for each source type and instance. You can use the Administrator tool or the infacmd command line program to administer the Logger Service. When managed by the Logger Service. The PowerExchange Logger captures change data from a data source and writes the data to PowerExchange Logger log files. 339 ¨ Creating a Logger Service. and Windows. 335 ¨ Properties of the PowerExchange Logger Service. On a Linux. ¨ View service logs ¨ Enable. 335 ¨ Configuration Statements for the Logger Service. as defined in a PowerExchange registration group. UNIX. disable. 334 . Create a Logger Service for each PowerExchange Logger process that you want to manage on the node. 334 ¨ Logger Service Restart and Failover. Logger Service. 339 PowerExchange Logger Service Overview The Logger Service is an application service that manages the PowerExchange Logger for Linux. Perform the following tasks to manage the Logger Service: ¨ Create a service. or Windows machine.

Include the same statements in the DBMOVER and PowerExchange Logger configuration files on each node. Logger Service Restart and Failover If you have the PowerCenter high availability option. Default is 5 Logger Service Restart and Failover 335 .cfg file. After failover. The port number must match the port number that you specify for the SVCNODE Port Number configuration property for the service. If the primary node fails. the Service Manager associates it with the PowerExchange Logger that you specify. the Logger Service provides restart and failover capabilities. if one is defined. For the Logger Service to fail over successfully. Optonally.Before you create a Logger Service. When you start or stop the Logger Service. install PowerExchange and configure a PowerExchange Logger on the node where you want to create the Logger Service. in seconds. the Service Manager restarts the service on the primary node. the Service Manager synchronizes and connects to the Logger Service process on the backup node. define the following statement in the DBMOVER file on each node that you configure to run the Logger Service: Statement SERVICE_TIMEOUT Description Specifies the time. you also start or stop the Logger Service process.cfg) files. If the Logger Service or the Logger Service process fails on the primary node. Define the following statement in the DBMOVER file on each node that you configure to run the Logger Service: Statement SVCNODE Description Service name and TCP/IP port on which the PowerExchange Logger process listens for commands from the Logger Service. The service name must match the service name that you specify in the associated CONDENSENAME statement in the pwxccl. Configuration Statements for the Logger Service The Logger Service reads configuration information from the DBMOVER and PowerExchange Logger Configuration (pwxccl. that a PowerExchange Logger waits to receive heartbeat data from the associated Logger Service before shutting down and issuing an error message. When you create a Logger Service. the Logger Service fails over to the backup node. the Logger Service process on the backup node must be able to connect to the data source.

If you do not select a license now. Domain in which the Logger Service is created. select the service in the Navigator and click the Properties tab. The description cannot exceed 765 characters. It also cannot contain spaces or the following special characters: `~%^*+={}\. Enter a service name up to 64 characters in length.. Required before you can enable the service. Name of the Logger Service. PowerExchange Logger Service General Properties The following table describes the properties of a Logger Service: General Property Name Description Read only. UNIX.cfg file. but you must restart the service for the properties to take effect. you can assign a license to the service later. see the PowerExchange CDC Guide for Linux. and Windows. No default is available. For more information about customizing the DBMOVER and PowerExchange Logger Configuration files for CDC sessions. The service name must match the service name that is specified in the associated SVCNODE statement in the dbmover. You can change the properties while the service is running.Define the following statement in the PowerExchange Logger configuration file on each node that you configure to run the Logger Service: Statement CONDENSENAME Description Name for the command-handling service for a PowerExchange Logger process to which commands are issued from the Logger Service.:'"/?. Primary node to run the Logger Service.<>|!()][ Description Location Node License Short description of the Logger Service. The name is not case sensitive and must be unique within the domain. Backup Nodes 336 Chapter 23: PowerExchange Logger Service . This property appears only if you have the PowerCenter high availability option. License to assign to the service. Nodes used as a backup to the primary node. Properties of the PowerExchange Logger Service To view the properties of a PowerExchange Logger Service. It cannot exceed 128 characters or begin with @.

Include quotes around any path and file name that contains spaces. Separate the parameters with the space character. SVCNODE Port Number Specifies the port on which the PowerExchange Logger process listens for commands from the Logger Service. the Logger Service deletes these records. The absence of checkpoint files does not trigger a cold start. you must provide the full path only if the file does not reside in the installation directory. Parameters to include when you start the Logger Service. you must define a unique SVCNODE port number for each service. Logger Service Management 337 . If the CDCT file contains records.cfg configuration file that you want to use instead of the default dbmover.license=directory/license_key_file Specifies the full path and file name for any license key file that you want to use instead of the default license. For the Logger Service. This alternative configuration file takes precedence over any alternative configuration file that you specify in the PWX_CONFIG environment variable. Note: In the config. the Logger Service ends. Optional. The alternative license key file must have a file name or path that is different from that of the default file. Start Parameters Logger Service Management Use the Properties tab in the Administrator tool to configure general or configuration properties for the Logger Service. The override file must have a path or file name that is different from that of the default file. and license parameters. If you specify Y and checkpoint files exist.PowerExchange Logger Service Configuration Properties The following table describes the configuration properties of a Logger Service: General Property Service Process Description Read only. Type of PowerExchange process that the service manages.key file. . Enter N to warm start the Logger Service from the restart point that is indicated in the last checkpoint file. Default is N.cfg file. the Logger Service ignores the files. Use the same port number that you specify in the SVCNODE statement of the DBMOVER file. If you define more than one Logger Service to run on a node.coldstart={Y|N} Indicates whether to cold start or warm start the Logger Service. If no checkpoint file exists in the CHKPT_BASENAME directory. the service process is Logger. You can include the following parameters: . This alternative license key file takes precedence over any alternative license key file that you specify in the PWX_LICENSE environment variable. cs. This port number must uniquely identify the PowerExchange Logger process to its Logger Service. You can also use the cs parameter to specify a Logger Service configuration file that overrides the default pwxccl. . Enter Y to cold start the Logger Service.cs=directory/pwxlogger_config_file Specifies the path and file name for the Logger Service configuration file.cfg file. .config=directory/pwx_config_file Specifies the full path and file name for any dbmover.

3. 1. 338 Chapter 23: PowerExchange Logger Service . The PowerExchange Logger Service properties window appears. 4. Configuring the Logger Service Process Properties Use the Processes tab in the Administrator tool to configure the environment variables for each service process. In the Navigator. The Edit PowerExchange Logger Service dialog box appears. Edit the configuration properties for the service.Configuring Logger Service General Properties Use the Properties tab in the Administrator tool to configure Logger Service general properties. You can disable a PowerExchange service if you need to temporarily restrict users from using the service. In the Configuration Properties area of the Properties tab. In the Navigator. disable. 1. click Edit. 2. You might restart a service if you modified a property. The following table describes the environment variables for the Logger Service process: Property Environment Variables Description Environment variables defined for the Logger Service process. The PowerExchange Logger Service properties window appears. Configuring Logger Service Configuration Properties Use the Properties tab in the Administrator tool to configure Logger Service configuration properties. Enabling the Logger Service To enable the Logger Service. click Edit. 3. select the service in the Navigator and click Enable the Service. Environment Variables for the Logger Service Process You can edit environment variables for a Logger Service process. select the PowerExchange Logger Service. Click OK. 2. or restart a PowerExchange Logger Service by using the Administrator tool. In the General Properties area of the Properties tab. Service Status of the Logger Service You can enable. Edit the general properties of the service. The Edit PowerExchange Logger Service dialog box appears. select the PowerExchange Logger Service.

Click Actions > New > PowerExchange Logger Service. 2. You can view Logger Service logs by performing one of the following actions in the Administrator tool: ¨ In the Logs tab. The Service view of the Logs tab appears. Restarting the Logger Service You can restart a Logger Service that you previously disabled. ¨ Abort. In the Service Type column. 3. Enable the Logger Service to make it available. 4. you can disable it. select Actions > View Logs for Service. Logger Service Logs 339 . select the service in the Navigator and click Restart.Disabling the Logger Service If you need to temporarily restrict users from using the Logger Service. Select one of the following options: ¨ Complete. 1. select the Domain view. 5. click the Service view. To restart the Logger Service. Corresponds to the PowerExchange SHUTDOWN command. Click OK. Creating a Logger Service 1. Enter the service properties. Messages appear by default in time stamp order. ¨ In the Logs tab. 3. Logger Service Logs The Logger Service generates operational and error log events that the Log Manager in the domain collects. Click the Domain tab of the Administrator tool. Stops all processes immediately and shuts down the service. Click OK. with the most recent messages on top. 2. and click Disable the Service. ¨ In the Domain tab. optionally select the name of the service. Initiates a controlled shutdown of all processes and shuts down the service. select PowerExchange Logger Service. In the Service Name list. You can filter on any of the columns. Select the service in the Domain Navigator. The New PowerExchange Logger Service dialog box appears.

To use multiple data sources with a single Reporting Service. create additional data sources in Data Analyzer. Specify a data source for each Reporting Service. 344 ¨ Configuring the Reporting Service. The name of the Reporting Service is the name of the Data Analyzer instance and the context path for the Data Analyzer URL. Data Analyzer stores metadata for schemas. 348 ¨ Granting Users Access to Reports. follow the instructions in the Data Analyzer Schema Designer Guide to import table definitions and create metrics and attributes for the reports. Choose the Other Reporting Sources option and specify the data warehouse details to run custom reports.CHAPTER 24 Reporting Service This chapter includes the following topics: ¨ Reporting Service Overview. hyphens (-). and other objects in the Data Analyzer repository. 350 Reporting Service Overview The Reporting Service is an application service that runs the Data Analyzer application in an Informatica domain. ¨ Data Profiling warehouse. The Reporting Service configures the Data Analyzer repository with the metadata corresponding to the selected data source. Choose the Data Profiling option and specify the data profiling warehouse details to run Data Profiling Reports. metrics and attributes. ¨ Metadata Manager warehouse. 342 ¨ Managing the Reporting Service. ¨ Other reporting sources. Click the URL in the Properties view to access Data Analyzer. Choose the associated Metadata Manager Service and specify the Metadata Manager warehouse details to run Metadata Manager Reports. Choose the associated PowerCenter Repository Service and specify the PowerCenter repository details to run PowerCenter Repository Reports. and underscores (_). specify the Data Analyzer repository details. The Data Analyzer context path can include only alphanumeric characters. 340 ¨ Creating the Reporting Service. queries. choose the data source to report against: ¨ PowerCenter repository. Create and enable a Reporting Service on the Domain tab of the Administrator tool. PowerCenter replaces the 340 . the Administrator tool starts Data Analyzer. If the name of the Reporting Service includes any other character. You can create multiple Reporting Services on the same node. When you enable the Reporting Service. reports. When you create a Reporting Service. After you create the data sources. When you create a Reporting Service. user profiles.

¨ Summary reports. instances. Use the Data Profiling dashboard to access the Data Profiling reports. Display data profile results for source-level and column-level functions in a data profile. Data Analyzer provides the following types of reports: ¨ Composite reports. The sub-reports can be multiple report types in Data Analyzer. and corresponding database names and field- level attributes. descriptions. events. if the name of the Reporting Service is ReportingService#3. ¨ Mapping and mapplet metadata. Create the reports in Data Analyzer and save them in the Data Analyzer repository. Display basic metadata about a data profile. ¨ Operational metadata. you can run the Data Profiling reports from Data Analyzer. For example: http://<HostName>:<PortNumber>/ReportingService_353 PowerCenter Repository Reports When you choose the PowerCenter repository as a data source. targets. ¨ Workflow and worklet metadata. ¨ Metadata reports. the context path of the Data Analyzer URL is the Reporting Service name with the # character replaced with _35. and historic statistics on previous runs of the same data profile. For example. and dependencies for each mapping. you can run the Metadata Manager Repository Reports from Data Analyzer. Other Reporting Sources When you choose other warehouses as data sources. Includes session execution details and metadata extensions defined for each session. you can run the PowerCenter Repository Reports from Data Analyzer. Display a set of sub-reports and the associated metadata. Includes port-level details for each transformation. Includes run-time statistics. Includes versions of sources. labels. ¨ Transformation metadata in mappings and mapplets. ¨ Session metadata. Metadata Manager Repository Reports When you choose the Metadata Manager warehouse as a data source.invalid characters with an underscore and the Unicode value of the character. and label properties. Reporting Service Overview 341 . ¨ Change management metadata. Includes shortcuts. Metadata Manager is the PowerCenter metadata management and analysis tool. transformations. you can run other reports from Data Analyzer. PowerCenter Repository Reports are prepackaged dashboards and reports that allow you to analyze the following types of PowerCenter repository metadata: ¨ Source and target metadata. and variables. Includes schedules. You can create a single Reporting Service for a Metadata Manager warehouse. Data Profiling Reports When you choose the Data Profiling warehouse as a data source. Includes the targets. The Metadata reports provide the source-level and column-level functions in a data profile.

3. When you enable a Reporting Service that uses an existing Data Analyzer repository. The following table describes the Reporting Service general properties: Property Name Description Name of the Reporting Service. queries. To create a Reporting Service for the PowerCenter Repository Service or Metadata Manager Service. complete the following tasks: ¨ Create the Data Analyzer repository. Click Browse to choose a different folder. PowerCenter does not import the metadata for the prepackaged reports. and other objects to the repository tables. create the application service in the domain. ¨ Create PowerCenter Repository Services and Metadata Manager Services. In the Administrator tool. Enter the general properties for the Reporting Service. Default value is 16080. License Primary Node Enable HTTP on port 342 Chapter 24: Reporting Service .. Since the Reporting Service is not highly available. click Actions > New Reporting Service. Use the database management system client to create the Data Analyzer repository database.:'"/?. Select from the list of licenses available in the domain. metrics and attributes. you can use the existing database. The TCP port that the Reporting Service uses. When you create the Reporting Service. The New Reporting Service dialog box appears. You can move the Reporting Service after you create it. Enter a value between 1 and 65535. click the Domain tab. In the Navigator. If you create a Reporting Service for an existing Data Analyzer repository. Creating the Reporting Service Before you create a Reporting Service. When you enable the Reporting Service. Note: If you create a Reporting Service for another reporting source. The name is not case sensitive and must be unique within the domain. Node on which the service process runs. Data Analyzer uses the metadata in the Data Analyzer repository to determine the location from which to retrieve the data for the report and how to present the report. Domain and folder where the service is created. user profiles. Create a database for the