In 100 CommandReference en

Informatica (Version 10.
0)
Command Reference
Informatica Command Reference

Version 10.0
November 2015
Copyright (c) 1993-2015 Informatica LLC. All rights reserved.
This software and documentation contain proprietary information of Informatica LLC 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 LLC. 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 LLC 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 ejtechnologies GmbH. All rights reserved. Copyright Jaspersoft Corporation. All rights reserved. Copyright International Business Machines Corporation. All rights
reserved. Copyright yWorks GmbH. All rights reserved. Copyright Lucent Technologies. All rights reserved. Copyright (c) University of Toronto. All rights reserved.
Copyright Daniel Veillard. All rights reserved. Copyright Unicode, Inc. Copyright IBM Corp. All rights reserved. Copyright MicroQuill Software Publishing, Inc. All
rights reserved. Copyright PassMark Software Pty Ltd. All rights reserved. Copyright LogiXML, Inc. All rights reserved. Copyright 2003-2010 Lorenzi Davide, All
rights reserved. Copyright Red Hat, Inc. All rights reserved. Copyright The Board of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright
EMC Corporation. All rights reserved. Copyright Flexera Software. All rights reserved. Copyright Jinfonet Software. All rights reserved. Copyright Apple Inc. All
rights reserved. Copyright Telerik Inc. All rights reserved. Copyright BEA Systems. All rights reserved. Copyright PDFlib GmbH. All rights reserved. Copyright
Orientation in Objects GmbH. All rights reserved. Copyright Tanuki Software, Ltd. All rights reserved. Copyright Ricebridge. All rights reserved. Copyright Sencha,
Inc. All rights reserved. Copyright Scalable Systems, Inc. All rights reserved. Copyright jQWidgets. All rights reserved. Copyright Tableau Software, Inc. All rights
reserved. Copyright MaxMind, Inc. All Rights Reserved. Copyright TMate Software s.r.o. All rights reserved. Copyright MapR Technologies Inc. All rights reserved.
Copyright Amazon Corporate LLC. All rights reserved. Copyright Highsoft. All rights reserved. Copyright Python Software Foundation. All rights reserved.
Copyright BeOpen.com. All rights reserved. Copyright CNRI. All rights reserved.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and/or other software which is licensed under various versions
of the Apache License (the "License"). You may obtain a copy of these Licenses at http://www.apache.org/licenses/. Unless required by applicable law or agreed to in
writing, software distributed under these Licenses is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied. See the Licenses for the specific language governing permissions and limitations under the Licenses.
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 various versions of 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-2013, 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 and at http://www.eclipse.org/org/documents/edl-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://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/licenseagreements/fuse-message-broker-v-5-3- license-agreement; 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://www.slf4j.org/license.html; 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.slf4j.org/license.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; http://srp.stanford.edu/license.txt; http://www.schneier.com/blowfish.html; http://
www.jmock.org/license.html; http://xsom.java.net; http://benalman.com/about/license/; https://github.com/CreateJS/EaselJS/blob/master/src/easeljs/display/Bitmap.js;
http://www.h2database.com/html/license.html#summary; http://jsoncpp.sourceforge.net/LICENSE; http://jdbc.postgresql.org/license.html; http://
protobuf.googlecode.com/svn/trunk/src/google/protobuf/descriptor.proto; https://github.com/rantav/hector/blob/master/LICENSE; http://web.mit.edu/Kerberos/krb5current/doc/mitK5license.html; http://jibx.sourceforge.net/jibx-license.html; https://github.com/lyokato/libgeohash/blob/master/LICENSE; https://github.com/hjiang/jsonxx/
blob/master/LICENSE; https://code.google.com/p/lz4/; https://github.com/jedisct1/libsodium/blob/master/LICENSE; http://one-jar.sourceforge.net/index.php?
page=documents&file=license; https://github.com/EsotericSoftware/kryo/blob/master/license.txt; http://www.scala-lang.org/license.html; https://github.com/tinkerpop/
blueprints/blob/master/LICENSE.txt; http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html; https://aws.amazon.com/asl/; https://github.com/
twbs/bootstrap/blob/master/LICENSE; https://sourceforge.net/p/xmlunit/code/HEAD/tree/trunk/LICENSE.txt; https://github.com/documentcloud/underscore-contrib/blob/
master/LICENSE, and https://github.com/apache/hbase/blob/master/LICENSE.txt.
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 new BSD License (http://opensource.org/
licenses/BSD-3-Clause), the MIT License (http://www.opensource.org/licenses/mit-license.php), the Artistic License (http://www.opensource.org/licenses/artisticlicense-1.0) and the Initial Developers Public License Version 1.0 (http://www.firebirdsql.org/en/initial-developer-s-public-license-version-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 product includes software Copyright (c) 2013 Frank Balluffi and Markus Moeller. All rights reserved. Permissions and limitations regarding this software are subject
to terms of the MIT license.
See patents at https://www.informatica.com/legal/patents.html.
DISCLAIMER: Informatica LLC 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 LLC 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-CLR-10000-0001
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Informatica My Support Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Informatica Product Availability Matrixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Informatica Support YouTube Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Informatica Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Informatica Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Chapter 1: Command Line Programs and Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Command Line Programs and Utilities Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Chapter 2: Installing and Configuring Command Line Utilities. . . . . . . . . . . . . . . . . 28

Installing and Configuring Command Line Utilities Overview. . . . . . . . . . . . . . . . . . . . . . . . . . 28
Installing the Command Line Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Installation Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Configuring the Command Line Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Configure the Informatica Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Configure the PowerCenter Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Configure the Metadata Manager Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Create the domains.infa File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Security Configuration for Informatica Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 3: Using the Command Line Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Using the Command Line Programs Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Entering Options and Arguments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Syntax Notation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Running Commands in a Secure Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Running Commands on UNIX with Kerberos Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . 35
Running Commands on UNIX with Single Sign-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Running Commands on UNIX Without Single Sign-On. . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Running Commands on Windows with Kerberos Authentication. . . . . . . . . . . . . . . . . . . . . . . . 37
Chapter 4: Environment Variables for Command Line Programs. . . . . . . . . . . . . . . 38

Environment Variables for Command Line Programs Overview. . . . . . . . . . . . . . . . . . . . . . . . 39
ICMD_JAVA_OPTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Table of Contents
Configuring ICMD_JAVA_OPTS on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Configuring ICMD_JAVA_OPTS on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
INFA_CLIENT_RESILIENCE_TIMEOUT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Configuring INFA_CLIENT_RESILIENCE_TIMEOUT on UNIX. . . . . . . . . . . . . . . . . . . . . . 41
Configuring INFA_CLIENT_RESILIENCE_TIMEOUT on Windows. . . . . . . . . . . . . . . . . . . 42
INFA_CODEPAGENAME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Configuring INFA_CODEPAGENAME on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Configuring INFA_CODEPAGENAME on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
INFA_DEFAULT_DATABASE_PASSWORD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Configuring INFA_DEFAULT_DATABASE_PASSWORD on UNIX. . . . . . . . . . . . . . . . . . . 43
Configuring INFA_DEFAULT_DATABASE_PASSWORD on Windows. . . . . . . . . . . . . . . . . 43
INFA_DEFAULT_DB_TRUSTSTORE_PASSWORD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Configuring INFA_DEFAULT_DB_TRUSTSTORE_PASSWORD on UNIX. . . . . . . . . . . . . . 44
Configuring INFA_DEFAULT_DB_TRUSTSTORE_PASSWORD on Windows. . . . . . . . . . . . 44
INFA_DEFAULT_DOMAIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Configuring INFA_DEFAULT_DOMAIN on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Configuring INFA_DEFAULT_DOMAIN on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
INFA_DEFAULT_DOMAIN_PASSWORD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Configuring INFA_DEFAULT_DOMAIN_PASSWORD on UNIX. . . . . . . . . . . . . . . . . . . . . 45
Configuring INFA_DEFAULT_DOMAIN_PASSWORD on Windows. . . . . . . . . . . . . . . . . . . 45
INFA_DEFAULT_DOMAIN_USER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Configuring INFA_DEFAULT_DOMAIN_USER on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . 46
Configuring INFA_DEFAULT_DOMAIN_USER on Windows. . . . . . . . . . . . . . . . . . . . . . . 46
INFA_DEFAULT_PWX_OSEPASSWORD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Configuring INFA_DEFAULT_PWX_OSEPASSWORD on UNIX. . . . . . . . . . . . . . . . . . . . . 47
Configuring INFA_DEFAULT_PWX_OSEPASSWORD on Windows. . . . . . . . . . . . . . . . . . 47
INFA_DEFAULT_PWX_OSPASSWORD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Configuring INFA_DEFAULT_PWX_OSPASSWORD on UNIX. . . . . . . . . . . . . . . . . . . . . . 47
Configuring INFA_DEFAULT_PWX_OSPASSWORD on Windows. . . . . . . . . . . . . . . . . . . 48
INFA_DEFAULT_SECURITY_DOMAIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Configuring INFA_DEFAULT_SECURITY_DOMAIN on UNIX. . . . . . . . . . . . . . . . . . . . . . 48
Configuring INFA_DEFAULT_SECURITY_DOMAIN on Windows. . . . . . . . . . . . . . . . . . . . 48
INFA_JAVA_CMD_OPTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Configuring INFA_JAVA_CMD_OPTS on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Configuring INFA_JAVA_CMD_OPTS on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
INFA_PASSWORD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Configuring INFA_PASSWORD on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Configuring INFA_PASSWORD on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
INFA_NODE_KEYSTORE_PASSWORD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Configuring INFA_NODE_KEYSTORE_PASSWORD on UNIX. . . . . . . . . . . . . . . . . . . . . . 50
Configuring INFA_NODE_KEYSTORE_PASSWORD on Windows. . . . . . . . . . . . . . . . . . . 51
INFA_NODE_TRUSTSTORE_PASSWORD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Table of Contents
Configuring INFA_NODE_TRUSTSTORE_PASSWORD on UNIX. . . . . . . . . . . . . . . . . . . . 51

Configuring INFA_NODE_TRUSTSTORE_PASSWORD on Windows. . . . . . . . . . . . . . . . . 51
INFA_REPCNX_INFO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Configuring INFA_REPCNX_INFO on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Configuring INFA_REPCNX_INFO on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
INFA_REPOSITORY_PASSWORD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Configuring INFA_REPOSITORY_PASSWORD on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . 53
Configuring INFA_REPOSITORY_PASSWORD on Windows. . . . . . . . . . . . . . . . . . . . . . . 53
INFATOOL_DATEFORMAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Configuring INFATOOL_DATEFORMAT on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Configuring INFATOOL_DATEFORMAT on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Encrypting Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Using a Password as an Environment Variable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Setting the User Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Configuring a User Name as an Environment Variable on UNIX. . . . . . . . . . . . . . . . . . . . . 55
Configuring a User Name as an Environment Variable on Windows. . . . . . . . . . . . . . . . . . 56
Chapter 5: Using infacmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Using infacmd Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
infacmd Command Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
infacmd ListPlugins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Running Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
infacmd Return Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
infacmd UpdateGatewayInfo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Chapter 6: infacmd as Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

CreateService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
CreateAuditTables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
DeleteAuditTables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
ListServiceOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
ListServiceProcessOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
UpdateServiceOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
UpdateServiceProcessOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Chapter 7: infacmd aud Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

getDomainObjectPermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
getPrivilegeAssociation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
getUserGroupAssociation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
getUserGroupAssociationForRoles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
getUsersPersonalInfo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Chapter 8: Infacmd bg Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

upgradeRepository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Table of Contents
Chapter 9: infacmd cms Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

CreateAuditTables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
CreateService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
DeleteAuditTables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
ListServiceOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Purge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
RemoveService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
ResyncData. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
UpdateServiceOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
UpdateServiceProcessOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Chapter 10: infacmd dis Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

AddParameterSetEntries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
BackupApplication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
CancelDataObjectCacheRefresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
CreateService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
DeleteParameterSetEntries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
DeployApplication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
ListApplications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
ListApplicationObjects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
ListApplicationOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
ListComputeOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
ListDataObjectOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
ListParameterSetEntries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
ListParameterSetObjects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
ListParameterSets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
ListSequenceObjectProperties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
ListSequenceObjects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
ListServiceOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
PurgeDataObjectCache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
PurgeResultSetCache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
RefreshDataObjectCache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
RenameApplication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
RestoreApplication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
SetSequenceState. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
StartApplication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
StopApplication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
stopBlazeService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
UndeployApplication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Table of Contents
UpdateApplication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
UpdateApplicationOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
UpdateComputeOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
UpdateDataObjectOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Data Object Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
UpdateParameterSetEntries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
UpdateServiceOptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Data Integration Service Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
UpdateServiceProcessOptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Data Integration Service Process Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Chapter 11: Infacmd es Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

UpdateSMTPOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Chapter 12: infacmd ipc Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

ExportToPC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
ImportFromPC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Chapter 13: infacmd isp Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

AddAlertUser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
AddConnectionPermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
AddDomainLink. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
AddDomainNode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
AddGroupPrivilege. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
AddLicense. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
AddNamespace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
AddNodeResource. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
AddRolePrivilege. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
AddServiceLevel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
AddUserPrivilege. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
AddUserToGroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
AssignedToLicense. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
AssignGroupPermission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
AssignISToMMService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
AssignLicense. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
AssignRoleToGroup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
AssignRoleToUser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
AssignRSToWSHubService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
AssignUserPermission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
BackupDARepositoryContents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
ConvertLogFile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Table of Contents
convertUserActivityLogFile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
CreateConnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Adabas Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
DataSift Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
DB2 for i5/OS Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Facebook Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Greenplum Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
HBase Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
HDFS Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Hadoop Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Hive Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
DB2 for z/OS Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
IBM DB2 Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
IMS Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
JDBC Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
LinkedIn Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Microsoft SQL Server Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Netezza Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
OData Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
ODBC Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Oracle Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Salesforce Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
SAP Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Sequential Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Teradata Parallel Transporter Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Twitter Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Twitter Streaming Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
VSAM Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Web Content-Kapow Katalyst Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
CreateDARepositoryContents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
CreateFolder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
CreateGrid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
CreateGroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
CreateIntegrationService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Integration Service Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Integration Service Process Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
CreateMMService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Metadata Manager Service Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
CreateOSProfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Integration Service Process Options for Operating System Profiles. . . . . . . . . . . . . . . . . . 318
CreateReportingService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Reporting Service Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Table of Contents
Reporting Source Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Lineage Service Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
CreateRepositoryService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
CreateRole. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
CreateSAPBWService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
SAP BW Service Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
SAP BW Service Process Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
CreateUser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
CreateWSHubService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Web Services Hub Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
DeleteDARepositoryContents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
DeleteNamespace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
DisableNodeResource. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
DisableService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
DisableServiceProcess. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
DisableUser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
EditUser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
EnableNodeResource. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
EnableService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
EnableServiceProcess. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
EnableUser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
ExportDomainObjects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
ExportUsersAndGroups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
GetFolderInfo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
GetLastError. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
GetLog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
GetNodeName. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
GetServiceOption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
GetServiceProcessOption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
GetServiceProcessStatus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
GetServiceStatus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
GetSessionLog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
GetSystemLogDirectory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
getUserActivityLog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
GetWorkflowLog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
ImportDomainObjects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
ImportUsersAndGroups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
ListAlertUsers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
ListAllGroups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
ListAllRoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
ListAllUsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
10
Table of Contents
ListConnectionPermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
ListConnectionPermissionsByGroup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
ListConnectionPermissionsByUser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
ListConnections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
ListConnectionOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
ListDomainLinks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
ListDomainOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
ListFolders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
ListGridNodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
ListGroupPermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
ListGroupPrivileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
ListGroupsForUser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
ListLDAPConnectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
ListLicenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
ListMonitoringOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
ListNodeOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
ListNodeResources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
ListNodeRoles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
ListNodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
ListOSProfiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
ListRepositoryLDAPConfiguration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
ListRolePrivileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
ListSecurityDomains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
ListServiceLevels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
ListServiceNodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
ListServicePrivileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
ListServices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
ListSMTPOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
ListUserPermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
ListUserPrivileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
migrateUsers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
MoveFolder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
MoveObject. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Ping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
PrintSPNAndKeytabNames. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
PurgeLog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
PurgeMonitoringData. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
RemoveAlertUser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
RemoveConnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
RemoveConnectionPermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
RemoveDomainLink. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
RemoveFolder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Table of Contents
11
RemoveGrid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
RemoveGroup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
RemoveGroupPermission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
RemoveGroupPrivilege. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
RemoveLicense. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
RemoveNode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
RemoveNodeResource. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
RemoveOSProfile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
RemoveRole . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
RemoveRolePrivilege . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
RemoveService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
RemoveServiceLevel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
RemoveUser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
RemoveUserFromGroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
RemoveUserPermission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
RemoveUserPrivilege . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
RenameConnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
ResetPassword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
RestoreDARepositoryContents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
RunCPUProfile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
SetConnectionPermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
SetLDAPConnectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
SetRepositoryLDAPConfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
ShowLicense. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
ShutdownNode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
SwitchToGatewayNode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
SwitchToWorkerNode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
SyncSecurityDomains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
UnassignISMMService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
UnassignLicense. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
UnassignRoleFromGroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
UnassignRoleFromUser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
UnassignRSWSHubService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
UnassociateDomainNode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
UpdateConnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
UpdateDomainOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
UpdateFolder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
UpdateGatewayInfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
UpdateGrid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
UpdateIntegrationService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
UpdateLicense. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
UpdateMMService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
12
Table of Contents
UpdateMonitoringOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
UpdateNamespace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
UpdateNodeOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
UpdateNodeRole. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
UpdateOSProfile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
UpdateReportingService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
UpdateRepositoryService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
UpdateSAPBWService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
UpdateServiceLevel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
UpdateServiceProcess. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
UpdateSMTPOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
UpdateWSHubService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
UpgradeDARepositoryContents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
UpgradeDARepositoryUsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
validateFeature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
Chapter 14: infacmd mrs Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572

BackupContents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
CheckInObject. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
CreateContents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
CreateFolder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
CreateProject. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
CreateService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
DeleteContents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
DeleteFolder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
DeleteProject. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
ListBackupFiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
ListCheckedOutObjects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
listFolders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
ListLockedObjects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
ListProjects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
PopulateVCS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
ReassignCheckedOutObject. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
rebuildDependencyGraph. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
RenameFolder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
RestoreContents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
UndoCheckout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
UnlockObject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
Model Repository Service Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
Table of Contents
13
UpgradeContents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Chapter 15: infacmd ms Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622

GetRequestLog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
ListMappingParams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
ListMappingParams Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
ListMappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
RunMapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
UpgradeMappingParameterFile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
Chapter 16: infacmd oie Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634

DeployApplication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
ExportObjects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
exportResources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
ImportObjects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
Chapter 17: infacmd ps Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644

cancelProfileExecution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
CreateWH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
DropWH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Execute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
executeProfile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
getExecutionStatus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
getProfileExecutionStatus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
migrateProfileResults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
migrateScorecards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
Purge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
synchronizeProfile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
Chapter 18: infacmd pwx Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665

CloseForceListener. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
CloseListener. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
CondenseLogger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
createdatamaps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
CreateListenerService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
CreateLoggerService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
DisplayAllLogger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
DisplayCPULogger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
DisplayEventsLogger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
DisplayMemoryLogger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
DisplayRecordsLogger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
14
Table of Contents
displayStatsListener. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
DisplayStatusLogger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
FileSwitchLogger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
ListTaskListener. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
ShutDownLogger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
StopTaskListener. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
UpgradeModels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
UpdateListenerService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
UpdateLoggerService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Chapter 19: infacmd rms Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721

ListComputeNodeAttributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
SetComputeNodeAttributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
Resource Manager Service Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728
Chapter 20: infacmd rtm Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729

DeployImport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
Chapter 21: infacmd sch Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736

CreateSchedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
DeleteSchedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
ListSchedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
PauseAll. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
PauseSchedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
ResumeAll. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
ResumeSchedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
UpdateSchedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
Scheduler Service Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
Scheduler Service Process Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
Chapter 22: infacmd search Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . 763

CreateService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
Table of Contents
15
Chapter 23: infacmd sql Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773

ExecuteSQL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
ListColumnOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
ListSQLDataServiceOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776
ListSQLDataServicePermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
ListSQLDataServices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
ListStoredProcedurePermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
ListTableOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
ListTablePermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783
PurgeTableCache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
RefreshTableCache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
RenameSQLDataService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788
SetColumnPermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
SetSQLDataServicePermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
SetStoredProcedurePermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
SetTablePermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
StartSQLDataService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
StopSQLDataService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
UpdateColumnOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
Column Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804
UpdateSQLDataServiceOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
SQL Data Service Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
UpdateTableOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
Virtual Table Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
Chapter 24: infacmd tdm Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811

CreateService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
CreateContents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
EnableService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
DisableService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
Chapter 25: infacmd wfs Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822

abortWorkflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
bulkComplete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824
cancelWorkflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
createTables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828
dropTables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
listActiveWorkflowInstances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
listMappingPersistedOutputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
listWorkflowParams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
16
Table of Contents
listWorkflowParams Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836

listWorkflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
recoverWorkflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
setMappingPersistedOutputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
startWorkflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
upgradeParameterFile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
Chapter 26: infacmd ws Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847

ListOperationOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
ListOperationPermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
ListWebServiceOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
ListWebServicePermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852
ListWebServices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
RenameWebService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
SetOperationPermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
SetWebServicePermissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
StartWebService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
StopWebService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
UpdateOperationOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
Operation Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
UpdateWebServiceOptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868
Web Service Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
Chapter 27: infacmd xrf Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872

generateReadableViewXML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
updateExportXML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
Chapter 28: infacmd Control Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874

infacmd Control Files Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874
Control File Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874
Control File Naming Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
Export Control Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
Export Control File Parameters for Domain Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
Export Control File Parameters for Model Repository Objects. . . . . . . . . . . . . . . . . . . . . 877
Import Control Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
Import Control File Parameters for Domain Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
Import Control File Parameters for Model Repository Objects. . . . . . . . . . . . . . . . . . . . . 882
Rules and Guidelines for Control Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
Control File Examples for Domain Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
Control File Examples for Model Repository Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888
Chapter 29: infasetup Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891

Using infasetup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891
Table of Contents
17
Running Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892

Command Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
infasetup Return Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
Using Database Connection Strings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
BackupDomain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
DefineDomain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895
DefineGatewayNode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
DefineWorkerNode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 912
DeleteDomain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915
GenerateEncryptionKey. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
MigrateEncryptionKey. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
RestoreDomain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
SwitchToKerberosMode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
UpdateGatewayNode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
UpdateKerberosAdminUser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 928
UpdateKerberosConfig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 928
UpdateWorkerNode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 929
UnlockUser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
ValidateandRegisterFeature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 932
Chapter 30: pmcmd Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933

Using pmcmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 934
Running Commands in Command Line Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 934
Running Commands in Interactive Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
Running in Wait Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
Scripting pmcmd Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
Entering Command Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
AbortTask. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939
abortworkflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941
Connect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 942
Disconnect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
Exit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
GetRunningSessionsDetails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
GetServiceDetails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945
GetServiceProperties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 947
getsessionstatistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
GetTaskDetails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 950
GetWorkflowDetails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952
Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 955
PingService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956
RecoverWorkflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956
ScheduleWorkflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 958
18
Table of Contents
SetFolder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 960
SetNoWait. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 960
SetWait. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 960
ShowSettings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961
StartTask. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961
Using Parameter Files with starttask. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
StartWorkflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964
Using Parameter Files with startworkflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966
StopTask. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967
StopWorkflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969
UnscheduleWorkflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971
UnsetFolder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
WaitTask. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
WaitWorkflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975
Chapter 31: pmrep Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977

Using pmrep. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Running Commands in Command Line Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
Running Commands in Interactive Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
Running Commands in Normal Mode and Exclusive Mode. . . . . . . . . . . . . . . . . . . . . . . 979
pmrep Return Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
Using Native Connect Strings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
Scripting pmrep Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
AddToDeploymentGroup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
ApplyLabel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
AssignPermission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984
Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
BackUp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
ChangeOwner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
CheckIn. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
CleanUp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
ClearDeploymentGroup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
Connect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
Create. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
CreateConnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
Specifying the Database Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994
Specifying the Database Code Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996
CreateDeploymentGroup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
CreateFolder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
Assigning Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
CreateLabel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999
Delete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999
Table of Contents
19
DeleteConnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000
DeleteDeploymentGroup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000
DeleteFolder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001
DeleteLabel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001
DeleteObject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001
DeployDeploymentGroup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
DeployFolder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
ExecuteQuery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005
Exit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007
FindCheckout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007
GetConnectionDetails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
GenerateAbapProgramToFile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009
Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1011
InstallAbapProgram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1011
KillUserConnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013
ListConnections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
ListObjectDependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
ListObjects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017
Listing Object Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1019
Listing Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
Listing Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
ListTablesBySess. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
ListUserConnections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023
MassUpdate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023
Session Property Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025
Rules and Guidelines for MassUpdate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1028
Sample Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
ModifyFolder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
Notify. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1030
ObjectExport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031
Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
ObjectImport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033
PurgeVersion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033
Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035
Register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036
RegisterPlugin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
Registering a Security Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038
Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039
Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039
Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040
RollbackDeployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040
Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
20
Table of Contents
Run. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
ShowConnectionInfo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042
SwitchConnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042
TruncateLog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043
UndoCheckout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044
Unregister. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045
UnregisterPlugin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046
Unregistering an External Security Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047
Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
UpdateConnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
UpdateEmailAddr. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049
UpdateSeqGenVals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
UpdateSrcPrefix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1051
UpdateStatistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1052
UpdateTargPrefix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1052
Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053
UninstallAbapProgram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054
Validate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055
Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057
Chapter 32: Working with pmrep Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059

Working with pmrep Files Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059
Using the Persistent Input File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059
Creating a Persistent Input File with pmrep. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1060
Creating a Persistent Input File Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1060
Using the Object Import Control File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1061
Object Import Control File Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063
Object Import Control File Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1066
Importing Source Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1066
Importing Multiple Objects into a Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1067
Checking In and Labeling Imported Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1067
Retaining Sequence Generator and Normalizer Values. . . . . . . . . . . . . . . . . . . . . . . . . 1067
Importing Objects and Local Shortcut Objects to the Same Repository. . . . . . . . . . . . . . . 1068
Importing Shortcut Objects from Another Repository. . . . . . . . . . . . . . . . . . . . . . . . . . 1068
Importing Objects to Multiple Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1069
Importing Specific Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1069
Reusing and Replacing Dependent Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1069
Replacing Invalid Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1070
Renaming Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1070
Copying SAP Mappings and SAP Program Information. . . . . . . . . . . . . . . . . . . . . . . . . 1071
Applying Default Connection Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1071
Resolving Object Conflicts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1071
Using the Deployment Control File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1072
Table of Contents
21
Deployment Control File Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074

Deployment Control File Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1077
Deploying the Latest Version of a Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1077
Deploying the Latest Version of a Deployment Group. . . . . . . . . . . . . . . . . . . . . . . . . . 1077
Listing Multiple Source and Target Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078
Tips for Working with pmrep Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1079
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1080
22
Table of Contents
Preface
The Informatica Command Reference is written for Informatica administrators and developers who manage
the repositories and administer the domain and services. This guide assumes you have knowledge of the
operating systems in your environment. This guide also assumes you are familiar with the interface
requirements for the supporting applications.
Informatica Resources
Informatica My Support Portal
As an Informatica customer, the first step in reaching out to Informatica is through the Informatica My Support
Portal at https://mysupport.informatica.com. The My Support Portal is the largest online data integration
collaboration platform with over 100,000 Informatica customers and partners worldwide.
As a member, you can:
Access all of your Informatica resources in one place.
Review your support cases.
Search the Knowledge Base, find product documentation, access how-to documents, and watch support
videos.
Find your local Informatica User Group Network and collaborate with your peers.
Informatica Documentation
The Informatica Documentation team makes every effort to create accurate, usable documentation. If you
have questions, comments, or ideas about this documentation, contact the Informatica Documentation team
through email at infa_documentation@informatica.com. We will use your feedback to improve our
documentation. Let us know if we can contact you regarding your comments.
The Documentation team updates documentation as needed. To get the latest documentation for your
product, navigate to Product Documentation from https://mysupport.informatica.com.
Informatica Product Availability Matrixes

Product Availability Matrixes (PAMs) indicate the versions of operating systems, databases, and other types
of data sources and targets that a product release supports. You can access the PAMs on the Informatica My
Support Portal at https://mysupport.informatica.com.
23
Informatica Web Site

You can access the Informatica corporate web site at https://www.informatica.com. The site contains
information about Informatica, its background, upcoming events, and sales offices. You will also find product
and partner information. The services area of the site includes important information about technical support,
training and education, and implementation services.
Informatica How-To Library

As an Informatica customer, you can access the Informatica How-To Library at
https://mysupport.informatica.com. The How-To Library is a collection of resources to help you learn more
about Informatica products and features. It includes articles and interactive demonstrations that provide
solutions to common problems, compare features and behaviors, and guide you through performing specific
real-world tasks.
Informatica Knowledge Base

As an Informatica customer, you can access the Informatica Knowledge Base at
https://mysupport.informatica.com. Use the Knowledge Base to search for documented solutions to known
technical issues about Informatica products. You can also find answers to frequently asked questions,
technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge
Base, contact the Informatica Knowledge Base team through email at KB_Feedback@informatica.com.
Informatica Support YouTube Channel

You can access the Informatica Support YouTube channel at http://www.youtube.com/user/INFASupport. The
Informatica Support YouTube channel includes videos about solutions that guide you through performing
specific tasks. If you have questions, comments, or ideas about the Informatica Support YouTube channel,
contact the Support YouTube team through email at supportvideos@informatica.com or send a tweet to
@INFASupport.
Informatica Marketplace
The Informatica Marketplace is a forum where developers and partners can share solutions that augment,
extend, or enhance data integration implementations. By leveraging any of the hundreds of solutions
available on the Marketplace, you can improve your productivity and speed up time to implementation on
your projects. You can access Informatica Marketplace at http://www.informaticamarketplace.com.
Informatica Velocity
You can access Informatica Velocity at https://mysupport.informatica.com. Developed from the real-world
experience of hundreds of data management projects, Informatica Velocity represents the collective
knowledge of our consultants who have worked with organizations from around the world to plan, develop,
deploy, and maintain successful data management solutions. If you have questions, comments, or ideas
about Informatica Velocity, contact Informatica Professional Services at ips@informatica.com.
Informatica Global Customer Support

You can contact a Customer Support Center by telephone or through the Online Support.
Online Support requires a user name and password. You can request a user name and password at
http://mysupport.informatica.com.
24
Preface
The telephone numbers for Informatica Global Customer Support are available from the Informatica web site
at http://www.informatica.com/us/services-and-training/support-services/global-support-centers/.
Preface
25
CHAPTER 1
Command Line Programs and

Utilities
This chapter includes the following topic:
Command Line Programs and Utilities Overview, 26
Command Line Programs and Utilities Overview

The Informatica installation includes customer support tools and command line programs and utilities. Use
the command line programs and utilities to manage the Informatica domain, application services, and objects.
You can run the command line programs and utilities on any machine that can access the Informatica
domain.
When you install the Informatica services or the Informatica clients, the command line programs and utilities
are installed by default. You can also install and run the programs and utilities on other machines by installing
the Informatica utilities.
The following table describes the Informatica utilities:
26
Command
Line Program
Description
infacmd
Administer the Informatica domain and application services and processes, including the
repository and integration services. You can also use infacmd to access and administer
licenses and log events and export and import objects and user accounts.
infasetup
Administer domains and nodes.
The following table describes the PowerCenter utilities:

Command
Line Program
Description
pmcmd
Manage workflows. Use pmcmd to start, stop, schedule, and monitor workflows.
pmpasswd
Encrypt passwords to use with pmcmd and pmrep environment variables.
pmrep
Performs repository administration tasks. Use pmrep to list repository objects, create and edit
groups, and restore and delete repositories.
The following table describes the Metadata Manager utilities:

Command
Line Program
Description
mmcmd
Load and manage resources. Import and export models and custom resources.
mmRepoCmd
Create, delete, back up, and restore Metadata Manager repository contents. Restore a
PowerCenter repository back-up file that contains Metadata Manager objects to the
PowerCenter repository database.
rmu
Migrate resources from a previous version of Metadata Manager to the current version.
rcfmu
Migrate a resource configuration file from a previous version of Metadata Manager to the
current version.
Command Line Programs and Utilities Overview
27
CHAPTER 2
Installing and Configuring

Command Line Utilities
This chapter includes the following topics:
Installing and Configuring Command Line Utilities Overview, 28
Installing the Command Line Utilities, 28
Configuring the Command Line Utilities, 29
Security Configuration for Informatica Utilities , 31
Installing and Configuring Command Line Utilities

Overview
When you install the Informatica services or the Informatica clients, the command line utilities are installed by
default. You can also install and run the command line programs on any machine without installing the
Informatica products.
When you enable secure communication for the domain or when the domain users Kerberos authentication,
perform security configuration on the machines where you installed the command line utilities.
Installing the Command Line Utilities

Install and configure the command line utilities to manage the Informatica domain, application services, and
objects.
Informatica provides a separate ZIP file to install command line utilities on a machine that does not have
Informatica products installed. To get the ZIP file, contact Informatica Global Customer Support.
Extract the files to the machine where you want to run the command line utilities.
Before you run the command line programs, you must configure the environment variables for the command
line programs. You must also grant run permission on the utility files to user accounts that run the
commands.
28
Installation Directories
The installation directories of the command line utilities vary based on whether the utilities are installed with
Informatica services installation, Informatica client installation, or standalone command line utilities
installation.
Informatica Services Installation
The Informatica utilities are installed in the following directory:
<Informatica installation directory>/isp/bin
The PowerCenter utilities are installed in the following directory:
<Informatica installation directory>/server/bin
The Metadata Manager utilities are installed in the following directory:
<Informatica installation directory>/services/MetadataManagerService/utilities
Informatica Client Installation
When you install the Developer tool, the Informatica utilities are installed in the following directory:
<Informatica installation directory>/clients/DeveloperClient/infacmd
When you install the PowerCenter client, the PowerCenter utilities are installed in the following directory:
<Informatica installation directory>/clients/PowerCenterClient/CommandLineUtilities/PC/
server/bin
When you install the PowerCenter client, the Metadata Manager utilities are installed in the following
directory:
<Informatica installation directory>/clients/PowerCenterClient/CommandLineUtilities/MM
Command Line Utilities Installation
The Informatica utilities are installed in the following directory:
<Utilities installation directory>/PowerCenter/isp/bin
The PowerCenter utilities are installed in the following directory:
<Utilities installation directory>/PowerCenter/server/bin
The Metadata Manager utilities are installed in the following directory:
<Utilities installation directory>/MetadataManager/utilities
Configuring the Command Line Utilities

Configure the path and environment variables as required by the command line utilities. Grant execute
permission on the utility files to user accounts that run the commands.
Configure the Informatica Utilities

Configure the environment variables required for the infacmd and infasetup command line programs.
To run infacmd, set the ICMD_JAVA_OPTS environment variable.
To run infasetup, set the INFA_JAVA_CMD_OPTS environment variable.
Configuring the Command Line Utilities
29
Configure the PowerCenter Utilities

Before you run the PowerCenter utilities, use the following guidelines to configure the program files and
variables:
To run pmrep, pmcmd, and pmpasswd, copy the domains.infa file for the Informatica domain to the utilities
directory.
To run pmrep, pmcmd, and pmpasswd on UNIX, set the INFA_HOME, PATH, and library path
environment variables to the location of the utilities.
For example, if the command line utilities are installed in the /data/Informatica_cmd_utilities/ folder,
then the PowerCenter utilities are located in the /data/Informatica_cmd_utilities/PowerCenter/
server/bin folder. On Linux, you can set the environment variables at the command prompt as follows:
setenv INFA_HOME /data/Informatica_cmd_utilities/PowerCenter/
setenv PATH .:/data/Informatica_cmd_utilities/PowerCenter/server/bin:$PATH
setenv LD_LIBRARY_PATH .:/data/Informatica_cmd_utilities/PowerCenter/server/bin:
$LD_LIBRARY_PATH
Note: Restart the machine after you configure the INFA_HOME or library path environment variable.
Configure the Metadata Manager Utilities

To configure the Metadata Manager utilities, configure environment variables that specify the location of the
Java Virtual Machine and the Informatica root directory. You must also verify the shared library location for
Solaris.
If the domain uses Kerberos authentication, create the domains.infa file. Metadata Manager command line
programs use the domains.infa file to get gateway connectivity information for the domain.
Configure the following environment variables:
JAVA_HOME
Specifies the location of the Java Virtual Machine. Set JAVA_HOME to the PowerCenter Java directory
in the command line utilities installation. For example:
<Utilities installation directory>\PowerCenter\java
Set this environment variable in each Metadata Manager command line program as follows:
1.
Open the batch file or shell script with a text editor.
2.
Find the line that sets JAVA_HOME to @INFA_JDK_HOME@.
3.
Replace the string @INFA_JDK_HOME@ with the PowerCenter Java directory. For example:
set JAVA_HOME=C:\InfaUtilities\PowerCenter\java
4.
Save and close the batch file or shell script.
INFA_HOME
Specifies the Informatica root directory so that any Informatica application or service can find the other
Informatica components that it needs to run. Set INFA_HOME to the PowerCenter directory in the
command line utilities installation. For example:
<Utilities installation directory>\PowerCenter
Set this environment variable on each machine where you installed the Informatica utilities.
LD_LIBRARY_PATH
Required for Solaris. Specifies the shared library location. Verify that the LD_LIBRARY_PATH
environment variable contains the following directories:
30
Chapter 2: Installing and Configuring Command Line Utilities
${JAVA_HOME}/jre/lib/sparcv9/server:${JAVA_HOME}/jre/lib/sparcv9/jli
Set this environment variable on each machine where you installed the Informatica utilities.
Note: Restart the machine after you configure the INFA_HOME or LD_LIBRARY_PATH environment
variable.
Create the domains.infa File

The domains.infa file contains the gateway connectivity information for the domain. When the domain uses
Kerberos authentication, create the domains.infa file so that the command line programs can get the gateway
connectivity information for the domain.
If the domain uses Kerberos authentication, you must enter domain connectivity information when you run the
command line program commands. You enter domain connectivity information through the --domainName
option or the --gateway option. To use the --domainName option, the domains.infa file must contain the
domain gateway connectivity information. If the domains.infa file does not exist or the information in the file is
out of date, you must use the --gateway option when you run any command that connects to the domain.
When you install Informatica services, the domains.infa file is available in the INFA_HOME directory. For any
other installation, create the file and verify that it is available on the machine from which you want to run the
commands.
To create the domains.infa file, run the infacmd isp UpdateGatewayInfo command. The command creates or
updates the domains.infa file in the PowerCenter directory in the command line utilities installation, for
example, <Utilities installation directory>\PowerCenter.
Security Configuration for Informatica Utilities

When you install Informatica utilities, you might need to configure the machines based on the domain security
configuration. If you do not configure the machines correctly, the command line programs might not be able
to authenticate users with the domain.
Configure the machines where you installed the Informatica utilities when the domain uses the following
security configurations:
Secure communication
If secure communication is enabled for the domain, you might need to configure the machines to use the
truststore file. If you use a custom truststore file, you must configure environment variables that specify
the truststore file directory and the truststore password.
Kerberos authentication
If the domain uses Kerberos authentication, you must copy the Kerberos configuration file to the
machines where you installed the Informatica utilities. You must also configure the machines to locate
the Kerberos configuration file for the domain.
Related Topics:
Running Commands in a Secure Domain on page 35
Running Commands on UNIX with Kerberos Authentication on page 35
Running Commands on Windows with Kerberos Authentication on page 37
Security Configuration for Informatica Utilities
31
CHAPTER 3
Using the Command Line

Programs
Using the Command Line Programs Overview, 32
Entering Options and Arguments, 33
Syntax Notation, 34
Running Commands in a Secure Domain, 35
Running Commands on UNIX with Kerberos Authentication, 35
Running Commands on Windows with Kerberos Authentication, 37
Using the Command Line Programs Overview

Informatica includes command line programs that you use to complete tasks from any machine in the
Informatica environment. The command line programs allow you to run a subset of tasks that you can
complete in Informatica Administrator.
For example, you can enable or disable a Repository Service from the Administrator tool or the infacmd
command line program.
Informatica includes the following command line programs:
32
infacmd. Use infacmd to access the Informatica application services.
infasetup. Use infasetup to complete installation tasks such as defining a node or a domain.
pmcmd. Use pmcmd to manage workflows. You can start, stop, schedule, and monitor workflows using
pmcmd.
pmrep. Use pmrep to complete repository administration tasks such as listing repository objects, creating
and editing groups, and restoring and deleting repositories.
mmcmd. Use mmcmd to load and manage resources and to import and export models and custom
resources.
mmRepoCmd. Use mmRepoCmd to create, delete, back up, and restore Metadata Manager repository
contents. You can also restore a PowerCenter repository back-up file that contains Metadata Manager
objects to the PowerCenter repository database.
rmu. Use rmu to migrate resources from a previous version of Metadata Manager to the current version.
rcfmu. Use rcfmu to migrate a resource configuration file from a previous version of Metadata Manager to
the current version.
To run command line programs on UNIX, you may need to set the library path environment variable to the
location of the Informatica utilities.
For ease of use, you can configure environment variables that apply each time you run the command line
programs.
For example, you can set an environment variable for the default domain name, user, and password to avoid
typing the options at the command line.
Entering Options and Arguments

Each command line program requires a set of options and arguments. These include user name, password,
domain name, and connection information.
Use the following rules when you enter command options and arguments:
To enter options, type a hyphen followed by one letter, two letters, or a word, depending on the program
syntax for the command.
For example, the pmrep Connect command uses a single letter option for the repository name:
Connect -r <repository_name>
Enter options in any order.
If any option that you specify from the command line contains spaces, enclose the option in double
quotes.
The first word after the option is the argument.
Most options require arguments.

You must separate options from arguments with a single space when using pmcmd or infacmd. You do
not have to separate options from arguments when using pmrep.
If any argument contains more than one word, enclose the argument in double quotes.
For pmrep and pmcmd, you can also use single quotes.
Unmatched quotes result in an error.
For infacmd or pmcmd, the command line programs ignore quotes that do not enclose an argument.
For pmrep, you can use space characters in an argument. To specify an argument containing space
characters, enclose the argument with either single or double quote characters. When you use either
single or double quotation marks in the argument, ensure that you precede the required quotation marks
with a backslash.
Entering Options and Arguments
33
Syntax Notation
The following table describes the notation used in this book to show the syntax for all Informatica command
line programs:
Convention
Description
-x
Option placed before a argument. This designates the parameter you enter.
For example, to enter the user name for pmcmd, type -u or -user followed by the
user name.
<x>
Required option. If you omit a required option, the command line program
returns an error message.
<x | y >
Select between required options. For the command to run, you must select from
the listed options. If you omit a required option, the command line program
returns an error message.
{x | y}
In pmrep, curly brackets denote groupings of required options, as in the

following example:
KillUserConnection
{-i <connection_id> |
-n <user_name> |
-a (kill all)}
If a pipe symbol (|) separates options, you must specify exactly one option. If
options are not separated by pipe symbols, you must specify all the options.
[x]
Optional parameter. The command runs whether or not you enter optional
parameters. For example, the Help command has the following syntax:
Help [Command]
If you enter a command, the command line program returns information on that
command only. If you omit the command name, the command line program
returns a list of all commands.
[x|y]
Select between optional parameters.

For example, many commands in pmcmd run in either the wait or nowait mode.
[-wait|-nowait]
If you specify a mode, the command runs in the specified mode. The command
runs whether or not you enter the optional parameter.
If you do not specify a mode, pmcmd runs the command in the default nowait
mode.
< < x | y> | <a | b> >
When a set contains subsets, the superset is indicated with bold brackets < > .
A bold pipe symbol ( | ) separates the subsets.
(text)
34
In pmrep, parentheses surround descriptive text, such as the list of the possible
values for an argument or an explanation for an option that does not take an
argument.
Chapter 3: Using the Command Line Programs
Running Commands in a Secure Domain

If the Informatica domain has secure communication enabled, you must set environment variables on the
machine that hosts the command line programs to run the commands securely. You must set the
environment variables before you run the infacmd, pmrep, mmcmd, mmRepoCmd, and pmcmd commands.
Set the following environment variables before you run the commands:
INFA_TRUSTSTORE
Set the INFA_TRUSTSTORE environment variable with the directory that contains the truststore files for
the SSL certificates. The directory must contain truststore files named infa_truststore.jks and
infa_truststore.pem. You must set the INFA_TRUSTSTORE variable whether you use the default SSL
certificate from Informatica or you specify a SSL certificate.
INFA_TRUSTSTORE_PASSWORD
If you specify the SSL certificate to enable secure communication in the domain, set the
INFA_TRUSTSTORE_PASSWORD environment variable with the password for the infa_truststore.jks
that contains the SSL certificate. You do not need to set this variable if you use the default SSL
certificate from Informatica.
Note: The password must be encrypted. Use the command line program pmpasswd to encrypt the
password with encryption type CRYPT_SYSTEM. For more information, see Encrypting Passwords on
page 54.
Running Commands on UNIX with Kerberos

Authentication
If the Informatica domain uses Kerberos authentication, set the Kerberos configuration environment variable
before you run the command line programs. If you run the command line programs with single sign-on, you
must generate a credential cache file and specify the path and file name in an environment variable.
You must set the environment variables before you run the infacmd, pmrep, mmcmd, mmRepoCmd, and
pmcmd commands on UNIX.
Running Commands on UNIX with Single Sign-On

If you run the command line programs with single sign-on, you must generate a credentials cache file to
authenticate the user account running the commands on the Kerberos network. Use the kinit utility to
generate the credentials cache file.
If you have a credentials cache file, you can run the commands without the user name and password options.
To run commands on UNIX with single sign-on, perform the following tasks:
1.
Set the Kerberos environment variables.
2.
Download the kinit utility and generate a credentials cache file.
Running Commands in a Secure Domain
35
Setting the Kerberos Environment Variables

On the machine that hosts the command line programs, specify the location of the credential cache and
configuration file in the Kerberos environment variables.
Set the following environment variables:
KRB5CCNAME
Stores the default path and filename for the Kerberos credentials cache. When you run the kinit utility to
generate the user credential cache, kinit stores the credential cache in the default file that you set in the
KRB5CCNAME environment variable.
KRB5_CONFIG
Stores the path and file name of the Kerberos configuration file. The name of the Kerberos configuration
file is krb5.conf. For information about the contents of the krb5.conf file, see the Informatica Security
Guide.
Generating the Credentials Cache File

Use the Kerberos kinit utility to generate the credentials cache file for the user account that runs the
command line programs. The utility is available with the MIT Kerberos V5 download package.
To generate the credentials cache file, perform the following tasks:
1.
Download and install MIT Kerberos V5.

You can download MIT Kerberos V5 from the following website:
http://web.mit.edu/Kerberos/dist/#krb5-1.12
2.
Run the kinit utility and specify the user principal name.
When you create the user credentials cache, you must use the forwardable (-f) or proxiable (-p) option.
On Solaris 10, use the proxiable option. On other UNIX platforms, use the forwardable option. You can
use the following command syntax:
Solaris 10
kinit -p <principal name>
Other UNIX platforms
kinit -f <principal name>
The format for the principal name is <username>@<realmname.com>. Enter the realm name in
uppercase letters.
Note: If you set the KRB5CCNAME environment variable before you run the kinit utility, kinit stores the
credentials cache in the location specified in the environment variable.
3.
Enter the password for the user account.
Running Commands on UNIX Without Single Sign-On

To run commands on UNIX without single sign-on, set the KRB5_CONFIG environment variable to the path
and file name of the Kerberos configuration file. Include the user name and password when you run the
command or set the user name and password in environment variables.
The commands determine the user credentials based on how you specify the user name and password. The
commands check the credentials in the following order:
1.
36
Command options. If you include the user name option (-un) and the password option (-pd) in the
command, the command uses the user name and password specified for the options.
Chapter 3: Using the Command Line Programs
2.
Environment variables. If you do not include the user name and password options in the command, the
command uses the user name and password specified in the environment variables
INFA_DEFAULT_DOMAIN_USER and INFA_DEFAULT_DOMAIN_PASSWORD.
Note: If you do not set the credentials in the command options or environment variables, the command
checks for a credential cache file. If a credential cache is available, the command runs with single sign-on.
Running Commands on Windows with Kerberos

Authentication
On Windows, the infacmd, pmrep, mmcmd, mmRepoCmd, and pmcmd commands use the logged in
credentials for single sign-on. You do not have to generate a credential cache file.
If you do not use single sign-on on Windows, set the KRB5_CONFIG environment variable to the path and
file name of the Kerberos configuration file. The name of the configuration file is krb5.conf.
The commands determine the user credentials based on how you specify the user name and password. The
commands check the credentials in the following order:
1.
Command options. If you include the user name option (-un) and the password option (-pd) in the
command, the command uses the user name and password specified for the options.
2.
Environment variables. If you do not include the user name and password options in the command, the
command uses the user name and password specified in the environment variables
INFA_DEFAULT_DOMAIN_USER and INFA_DEFAULT_DOMAIN_PASSWORD.
Note: If you do not set the credentials in the command options or environment variables, the command uses
the logged-in credentials and runs the command with single sign-on.
Running Commands on Windows with Kerberos Authentication
37
CHAPTER 4
Environment Variables for

Command Line Programs
38
Environment Variables for Command Line Programs Overview, 39
ICMD_JAVA_OPTS, 40
INFA_CLIENT_RESILIENCE_TIMEOUT, 41
INFA_CODEPAGENAME, 42
INFA_DEFAULT_DATABASE_PASSWORD, 42
INFA_DEFAULT_DB_TRUSTSTORE_PASSWORD, 43
INFA_DEFAULT_DOMAIN, 44
INFA_DEFAULT_DOMAIN_PASSWORD, 45
INFA_DEFAULT_DOMAIN_USER, 46
INFA_DEFAULT_PWX_OSEPASSWORD, 46
INFA_DEFAULT_PWX_OSPASSWORD, 47
INFA_DEFAULT_SECURITY_DOMAIN, 48
INFA_JAVA_CMD_OPTS, 48
INFA_PASSWORD, 49
INFA_NODE_KEYSTORE_PASSWORD, 50
INFA_NODE_TRUSTSTORE_PASSWORD, 51
INFA_REPCNX_INFO, 52
INFA_REPOSITORY_PASSWORD, 52
INFATOOL_DATEFORMAT, 53
Encrypting Passwords, 54
Setting the User Name, 55
Environment Variables for Command Line Programs

Overview
You can configure optional environment variables for the command line programs. For example, you can set
environment variables to encrypt passwords, configure time and date display options, or store the default
login information for a domain.
If you are run pmcmd or pmrep in interactive mode, you must exit the command line program and then
reconnect to use changed environment variables.
On Windows, you can configure these environment variables as either user or system variables. For
information about setting environment variables on Windows, see the Windows documentation.
Note: The environment variables that you configure apply to command line programs that run on the node.
To apply changes, restart the node.
The following table describes environment variables you can configure to use with the command line
programs:
Environment Variable
Command
Line
Programs
Description
ICMD_JAVA_OPTS
infacmd
Sets Java options.
INFA_CLIENT_RESILIENCE_TIMEOUT
infacmd
Limits the number of seconds you want

the command line programs to spend
establishing a connection to the domain
or service.
pmcmd
pmrep
INFA_CODEPAGENAME
pmcmd
Configures the character set pmcmd and

pmrep use.
pmrep
INFA_DEFAULT_CONNECTION_PASSWORD
infacmd
Stores the database truststore file

password for the secure database.
INFA_DEFAULT_DATABASE_PASSWORD
infasetup
Stores the default user name password

for the domain configuration database.
INFA_DEFAULT_DB_TRUSTSTORE_PASSWORD
infasetup
Stores the database truststore

password.
INFA_DEFAULT_DOMAIN
infacmd
Stores the default domain name.
pmcmd
pmrep
INFA_DEFAULT_DOMAIN_PASSWORD
infacmd
Stores the default user name password

for the domain.
Environment Variables for Command Line Programs Overview
39
Environment Variable
Command
Line
Programs
Description
INFA_DEFAULT_DOMAIN_USER
infacmd
Stores the default user name for the

domain.
INFA_DEFAULT_PWX_OSEPASSWORD
infacmd pwx
Stores an encrypted password for the

operating system.
INFA_DEFAULT_PWX_OSPASSWORD
infacmd pwx
Stores a plain text password for the

operating system.
INFA_DEFAULT_SECURITY_DOMAIN
infacmd
Stores the security domain for LDAP

authentication.
INFA_JAVA_CMD_OPTS
infasetup
Sets Java options.
INFA_NODE_KEYSTORE_PASSWORD
infasetup
Stores the password for the

infa_keystore.jks file.
INFA_NODE_TRUSTSTORE_PASSWORD
infasetup
Stores the password for the

infa_truststore.jks file.
INFA_PASSWORD
infacmd
Stores the default password for the

user.
INFA_REPCNX_INFO
pmrep
Stores the name of the repository

connection file.
INFA_REPOSITORY_PASSWORD
infacmd
Stores the default PowerCenter

Repository password for the user.
INFATOOL_DATEFORMAT
pmcmd
Configures the way pmcmd displays the

date and time.
<Password_Environment_Variable>
pmcmd
Encrypts and stores the password.
pmrep
<User_Name_Environment_Variable>
pmcmd
Stores the user name.
pmrep
Related Topics:
Encrypting Passwords on page 54
Setting the User Name on page 55
ICMD_JAVA_OPTS
ICMD_JAVA_OPTS environment variable applies to the infacmd command line program.
40
Chapter 4: Environment Variables for Command Line Programs
You can configure the environment variable ICMD_JAVA_OPTS to set the Java options such as -Xmx values
and system properties. To set a system property, pass the value in the following format:
-Dproperty.name=property.value
For example, you might want to increase the system memory used by infacmd. The default system memory
for infacmd is 512 MB. To configure 1024 MB of system memory in a UNIX C shell environment, type:
setenv ICMD_JAVA_OPTS "-Xmx1024m"
Configuring ICMD_JAVA_OPTS on UNIX

To configure ICMD_JAVA_OPTS on UNIX:
u
In a UNIX C shell environment, type:

setenv ICMD_JAVA_OPTS <Java_Options>
In a UNIX Bourne shell environment, type:
ICMD_JAVA_OPTS = <Java_Options>
export ICMD_JAVA_OPTS
Configuring ICMD_JAVA_OPTS on Windows

To configure ICMD_JAVA_OPTS on Windows:
u
Enter the environment variable ICMD_JAVA_OPTS, and set the Java options such as the -Xmx values
and system properties.
For information about setting environment variables on Windows, consult the Windows documentation.
INFA_CLIENT_RESILIENCE_TIMEOUT environment variable applies to the infacmd, pmcmd, and pmrep
command line programs.
You can set the environment variable INFA_CLIENT_RESILIENCE_TIMEOUT to limit the number of seconds
the command line programs spend establishing connections to the domain or service. The default time is 180
seconds if you do not set this environment variable.
Configuring INFA_CLIENT_RESILIENCE_TIMEOUT on UNIX

To configure INFA_CLIENT_RESILIENCE_TIMEOUT on UNIX:
u

setenv INFA_CLIENT_RESILIENCE_TIMEOUT <number of seconds>
INFA_CLIENT_RESILIENCE_TIMEOUT = <number of seconds>
export INFA_CLIENT_RESILIENCE_TIMEOUT
41
Configuring INFA_CLIENT_RESILIENCE_TIMEOUT on Windows

To configure INFA_CLIENT_RESILIENCE_TIMEOUT on Windows:
u
Enter the environment variable INFA_CLIENT_RESILIENCE_TIMEOUT, and set the value to the number
of seconds you want the command line programs to spend establishing a connection to the domain or
service.
INFA_CODEPAGENAME
INFA_CODEPAGENAME environment variable applies to the pmcmd and pmrep command line programs.
pmcmd and pmrep send commands in Unicode and use the code page of the host machine unless you set
the code page environment variable, INFA_CODEPAGENAME, to override it. If you set
INFA_CODEPAGENAME for pmcmd, the code page must be compatible with the Integration Service code
page. If you set INFA_CODEPAGENAME for pmrep, the code page name must be compatible with the
repository code page. If you set INFA_CODEPAGENAME on the machine where you run pmcmd and pmrep,
the code page must be compatible with the Integration Service and the repository code pages.
If the code pages are not compatible, the command might fail.
Configuring INFA_CODEPAGENAME on UNIX

To configure INFA_CODEPAGENAME on UNIX:
u

setenv INFA_CODEPAGENAME <code page name>
INFA_CODEPAGENAME = <code page name>
export INFA_CODEPAGENAME
Configuring INFA_CODEPAGENAME on Windows

To configure INFA_CODEPAGENAME on Windows:
u
Enter the environment variable INFA_CODEPAGENAME, and set the value to the code page name.
INFA_DEFAULT_DATABASE_PASSWORD environment variable applies to the infasetup command line
program.
Some infasetup commands require a domain configuration database password. You can provide this
password as an option with infasetup, or you can store it as the environment variable
INFA_DEFAULT_DATABASE_PASSWORD.
42
Use the following steps as a guideline to use an encrypted password as an environment variable:
1.
Use the command line program pmpasswd to encrypt the database user password.
pmpasswd generates and displays the encrypted password. For example, if you enter the password
monday, it encrypts to f/wRb5PZsZnqESTDPeos7Q==.
2.
Configure the password environment variable to set the encrypted value.
Related Topics:
Configuring INFA_DEFAULT_DATABASE_PASSWORD on UNIX

To configure INFA_DEFAULT_DATABASE_PASSWORD on UNIX:
1.
At the command line, type:

pmpasswd <database password>
pmpasswd returns the encrypted password.
2.

setenv INFA_DEFAULT_DATABASE_PASSWORD <encrypted password>
INFA_DEFAULT_DATABASE_PASSWORD = <encrypted password>
export INFA_DEFAULT_DATABASE_PASSWORD
Configuring INFA_DEFAULT_DATABASE_PASSWORD on
Windows
To configure INFA_DEFAULT_DATABASE_PASSWORD on Windows:
1.

2.
Enter the environment variable INFA_DEFAULT_DATABASE_PASSWORD, and set the value to the
encrypted password.
INFA_DEFAULT_DB_TRUSTSTORE_PASSWORD environment variable applies to the infasetup command
line program.
Some infasetup commands configure secure communication for the domain. You can provide the password
for the database truststore file for the secure database as an option with infasetup, or you can store it as the
environment variable INFA_DEFAULT_DB_TRUSTSTORE_DATABASE_PASSWORD.
1.
43
2.
Configuring INFA_DEFAULT_DB_TRUSTSTORE_PASSWORD
on UNIX
To configure INFA_DEFAULT_DB_TRUSTSTORE_PASSWORD on UNIX:
1.

2.

setenv INFA_DEFAULT_DB_TRUSTSTORE_PASSWORD <encrypted password>
INFA_DEFAULT_DB_TRUSTSTORE_PASSWORD = <encrypted password>
export INFA_DEFAULT_DB_TRUSTSTORE_PASSWORD
Configuring INFA_DEFAULT_DB_TRUSTSTORE_PASSWORD
on Windows
To configure INFA_DEFAULT_DB_TRUSTSTORE_PASSWORD on Windows:
1.

2.
Enter the environment variable INFA_DEFAULT_DB_TRUSTSTORE_PASSWORD, and set the value to

the encrypted password.
INFA_DEFAULT_DOMAIN
INFA_DEFAULT_DOMAIN environment variable applies to the infacmd, pmcmd, and pmrep command line
programs.
The command line programs require a domain name. You can provide the domain name as an option with the
command line programs, or you can store it as the environment variable INFA_DEFAULT_DOMAIN. If you
have more than one domain, choose a default domain.
Configuring INFA_DEFAULT_DOMAIN on UNIX

To configure INFA_DEFAULT_DOMAIN on UNIX:
u

setenv INFA_DEFAULT_DOMAIN <domain name>
INFA_DEFAULT_DOMAIN = <domain name>
export INFA_DEFAULT_DOMAIN
44
Configuring INFA_DEFAULT_DOMAIN on Windows

To configure INFA_DEFAULT_DOMAIN on Windows:
u
Enter the environment variable INFA_DEFAULT_DOMAIN, and set the value to the domain name.
INFA_DEFAULT_DOMAIN_PASSWORD environment variable applies to the infacmd command line program.
Most infacmd commands require a user password. You can provide a user password as an option with
infacmd, or you can store it as the environment variable INFA_DEFAULT_DOMAIN_PASSWORD.
1.
Use the command line program pmpasswd to encrypt the user password.
2.
Related Topics:
Configuring INFA_DEFAULT_DOMAIN_PASSWORD on UNIX

To configure INFA_DEFAULT_DOMAIN_PASSWORD on UNIX:
1.

pmpasswd <password>
2.

setenv INFA_DEFAULT_DOMAIN_PASSWORD <encrypted password>
INFA_DEFAULT_DOMAIN_PASSWORD = <encrypted password>
export INFA_DEFAULT_DOMAIN_PASSWORD
Configuring INFA_DEFAULT_DOMAIN_PASSWORD on Windows

To configure INFA_DEFAULT_DOMAIN_PASSWORD on Windows:
1.

pmpasswd <password>
2.
Enter the environment variable INFA_DEFAULT_DOMAIN_PASSWORD, and set the value to the
encrypted password.
45
INFA_DEFAULT_DOMAIN_USER environment variable applies to the infacmd command line program.
Most infacmd commands require a user name. You can provide a user name as an option with infacmd, or
you can store it as the environment variable INFA_DEFAULT_DOMAIN_USER.
Configuring INFA_DEFAULT_DOMAIN_USER on UNIX

To configure INFA_DEFAULT_DOMAIN_USER on UNIX:
u

setenv INFA_DEFAULT_DOMAIN_USER <user name>
INFA_DEFAULT_DOMAIN_USER = <user name>
export INFA_DEFAULT_DOMAIN_USER
Configuring INFA_DEFAULT_DOMAIN_USER on Windows

To configure INFA_DEFAULT_DOMAIN_USER on Windows:
u
Enter the environment variable INFA_DEFAULT_DOMAIN_USER, and set the value to the default user
name.
INFA_DEFAULT_PWX_OSEPASSWORD environment variable applies to the infacmd pwx command line
program.
Some infacmd pwx commands require an operating system password. You can provide an encrypted
password as an option with infacmd pwx, or you can store it as the environment variable
INFA_DEFAULT_PWX_OSEPASSWORD.
1.
To encrypt the password, use the pmpasswd command line program.

The pmpasswd program generates and displays the encrypted password. For example, if you enter the
password monday, it encrypts to f/wRb5PZsZnqESTDPeos7Q==.
2.
46
Related Topics:
Configuring INFA_DEFAULT_PWX_OSEPASSWORD on UNIX

To configure INFA_DEFAULT_PWX_OSEPASSWORD on UNIX:
1.

pmpasswd password
The pmpasswd program returns the encrypted password.
2.

setenv INFA_DEFAULT_PWX_OSEPASSWORD encrypted_password
INFA_DEFAULT_PWX_OSEPASSWORD = encrypted_password
export INFA_DEFAULT_PWX_OSEPASSWORD
Configuring INFA_DEFAULT_PWX_OSEPASSWORD on
Windows
To configure INFA_DEFAULT_PWX_OSEPASSWORD on Windows:
1.

pmpasswd password
The pmpasswd program returns the encrypted password.
2.
Enter the environment variable INFA_DEFAULT_PWX_OSEPASSWORD, and set the value to the
encrypted password.
For information about setting environment variables on Windows, see the Windows documentation.
INFA_DEFAULT_PWX_OSPASSWORD environment variable applies to the infacmd pwx command line
program.
Some infacmd pwx commands require an operating system password. You can provide a plain text password
as an option with infacmd pwx, or you can store it as the environment variable
INFA_DEFAULT_PWX_OSPASSWORD.
Configuring INFA_DEFAULT_PWX_OSPASSWORD on UNIX

To configure INFA_DEFAULT_PWX_OSPASSWORD on UNIX:
u

setenv INFA_DEFAULT_PWX_OSPASSWORD password
INFA_DEFAULT_PWX_OSPASSWORD = password
export INFA_DEFAULT_PWX_OSPASSWORD
47
Configuring INFA_DEFAULT_PWX_OSPASSWORD on Windows

To configure INFA_DEFAULT_PWX_OSPASSWORD on Windows, set the value to the plain text password.
For information about setting environment variables on Windows, see the Windows documentation.
INFA_DEFAULT_SECURITY_DOMAIN environment variable applies to the infacmd command line program.
The infacmd commands require a security domain if you use LDAP authentication and you specify an
Informatica user. You can set the environment variable INFA_DEFAULT_SECURITY_DOMAIN to the native
security domain or to an LDAP security domain name.
Configuring INFA_DEFAULT_SECURITY_DOMAIN on UNIX

To configure INFA_DEFAULT_SECURITY_DOMAIN on UNIX:
u

setenv INFA_DEFAULT_SECURITY_DOMAIN <security domain name>
INFA_DEFAULT_SECURITY_DOMAIN = <security domain name>
export INFA_DEFAULT_SECURITY_DOMAIN
Configuring INFA_DEFAULT_SECURITY_DOMAIN on Windows

To configure INFA_DEFAULT_SECURITY_DOMAIN on Windows:
u
Enter the environment variable INFA_DEFAULT_SECURITY_DOMAIN and set the value to the name of
the security domain.
INFA_JAVA_CMD_OPTS
INFA_JAVA_CMD_OPTS environment variable applies to the infasetup command line program.
You can configure the environment variable INFA_JAVA_CMD_OPTS to set the Java options such as -Xmx
values and system properties. To set a system property, pass the value in the following format:
-Dproperty.name=property.value
For example, you might want to increase the system memory used by infasetup. The default system memory
for infasetup is 512 MB. To configure 1024 MB of system memory in a UNIX C shell environment, type:
setenv INFA_JAVA_CMD_OPTS "-Xmx1024m"
48
Configuring INFA_JAVA_CMD_OPTS on UNIX

To configure INFA_JAVA_CMD_OPTS on UNIX:
u

setenv INFA_JAVA_CMD_OPTS <Java_Options>
INFA_JAVA_CMD_OPTS = <Java_Options>
export INFA_JAVA_CMD_OPTS
Configuring INFA_JAVA_CMD_OPTS on Windows

To configure INFA_JAVA_CMD_OPTS on Windows:
u
Enter the environment variable INFA_JAVA_CMD_OPTS, and set the Java options such as the -Xmx
values and system properties.
INFA_PASSWORD
INFA_PASSWORD environment variable applies to the infacmd and infasetup command line programs.
Some infacmd and infasetup commands require a user password. You can provide a user password as an
option with these commands, or you can store it as the environment variable INFA_PASSWORD.
You can use the INFA_PASSWORD environment variable to store different types of passwords. For example
in the infasetup DefineDomain command, you can use the variable to set the keystore password. In the
infacmd isp SetLDAPConnectivity command, you can use the variable to set the LDAP credential password.
You may need to change the value of this variable based on the commands that you run.
1.
2.
Related Topics:
Configuring INFA_PASSWORD on UNIX

To configure INFA_PASSWORD on UNIX:
1.

pmpasswd <password>
2.

setenv INFA_PASSWORD <encrypted password>
INFA_PASSWORD
49

INFA_PASSWORD = <encrypted password>
export INFA_PASSWORD
Configuring INFA_PASSWORD on Windows

To configure INFA_PASSWORD on Windows:
1.

pmpasswd <password>
2.
Enter the environment variable INFA_PASSWORD, and set the value to the encrypted password.
The INFA_NODE_KEYSTORE_PASSWORD environment variable applies to the infasetup command line
program.
for the informatica Java Keystore (JKS) file as an option with infasetup, or you can store it as the
environment variable INFA_NODE_KEYSTORE_PASSWORD.
1.
2.
Configuring INFA_NODE_KEYSTORE_PASSWORD on UNIX

To configure INFA_NODE_KEYSTORE_PASSWORD on UNIX:
1.

2.

setenv INFA_NODE_KEYSTORE_PASSWORD
<encrypted password>

INFA_NODE_KEYSTORE_PASSWORD = <encrypted password>
export INFA_NODE_KEYSTORE_PASSWORD
50
Configuring INFA_NODE_KEYSTORE_PASSWORD on Windows

To configure INFA_NODE_KEYSTORE_PASSWORD on Windows:
1.

2.
Enter the environment variable INFA_NODE_KEYSTORE_PASSWORD , and set the value to the
encrypted password.
The INFA_NODE_TRUSTSTORE_PASSWORD environment variable applies to the infasetup command line
program.
for the infa_truststore.jks file as an option with infasetup, or you can store it as the environment variable
INFA_NODE_TRUSTSTORE_PASSWORD.
1.
2.
Configuring INFA_NODE_TRUSTSTORE_PASSWORD on UNIX

To configure INFA_NODE_TRUSTSTORE_PASSWORD on UNIX:
1.

2.

setenv INFA_NODE_TRUSTSTORE_PASSWORD
<encrypted password>

INFA_NODE_TRUSTSTORE_PASSWORD = <encrypted password>
export INFA_NODE_TRUSTSTORE_PASSWORD
Configuring INFA_NODE_TRUSTSTORE_PASSWORD on
Windows
To configure INFA_NODE_TRUSTSTORE_PASSWORD on Windows:
1.

51
2.
Enter the environment variable INFA_NODE_TRUSTSTORE_PASSWORD , and set the value to the
encrypted password.
INFA_REPCNX_INFO
The INFA_REPCNX_INFO environment variable applies to the pmrep command line program.
When you run pmrep in command line mode or from a script, it stores repository connection information in a
file, pmrep.cnx. pmrep uses the information in this file to reconnect to the repository. The
INFA_REPCNX_INFO environment variable stores the file name and file path for the repository connection
file. Each time you run pmrep connect, the command deletes the pmrep.cnx file. If the pmrep connect
command succeeds, the command replaces the pmrep.cnx file with the repository connection information.
Use this variable when scripts that issue pmrep commands run simultaneously, and the scripts connect to
different repositories. In each shell, specify a different repository connection file. This prevents a script from
overwriting the connection information used by another script.
If you do not set this environment variable, pmrep stores connection information in pmrep.cnx in the home
directory. If you want to set the pmrep.cnx file in another location, specify the file path using the
INFA_REPCNX_INFO environment variable.
Configuring INFA_REPCNX_INFO on UNIX

To configure INFA_REPCNX_INFO on UNIX:
u

setenv INFA_REPCNX_INFO <file name>
INFA_REPCNX_INFO = <file name>
export INFA_REPCNX_INFO
Configuring INFA_REPCNX_INFO on Windows

To configure INFA_REPCNX_INFO on Windows:
u
In a DOS shell, type:

set INFA_REPCNX_INFO = <file name>
Note: If you run multiple pmrep scripts, set this environment variable for the DOS shell, not for the
machine.
INFA_REPOSITORY_PASSWORD environment variable applies to the infacmd command line program.
Some infacmd commands require a PowerCenter repository password. You can provide a user password as
an option with infacmd, or you can store it as the environment variable INFA_REPOSITORY_PASSWORD.
52
1.
2.
Related Topics:
Configuring INFA_REPOSITORY_PASSWORD on UNIX

To configure INFA_REPOSITORY_PASSWORD on UNIX:
1.

pmpasswd <password>
2.

setenv INFA_REPOSITORY_PASSWORD <encrypted password>
INFA_REPOSITORY_PASSWORD = <encrypted password>
export INFA_REPOSITORY_PASSWORD
Configuring INFA_REPOSITORY_PASSWORD on Windows

To configure INFA_REPOSITORY_PASSWORD on Windows:
1.

pmpasswd <repository password>
2.
Enter the environment variable INFA_REPOSITORY_PASSWORD, and set the value to the encrypted
password.
INFATOOL_DATEFORMAT
INFATOOL_DATEFORMAT environment variable applies to the pmcmd command line program.
Use this environment variable to customize the way pmcmd displays the date and time. Enter the date format
string in DY MON DD HH24:MI:SS YYYY format. pmcmd verifies that the string is a valid format. If the format
string is not valid, the Integration Service generates a warning message and displays the date in the format
DY MON DD HH24:MI:SS YYYY.
INFATOOL_DATEFORMAT
53
Configuring INFATOOL_DATEFORMAT on UNIX

To configure INFATOOL_DATEFORMAT on UNIX:
u

setenv INFATOOL_DATEFORMAT <date/time format string>
INFATOOL_DATEFORMAT = <date/time format string>
export INFATOOL_DATEFORMAT
Configuring INFATOOL_DATEFORMAT on Windows

To configure INFATOOL_DATEFORMAT on Windows:
u
Enter the environment variable INFATOOL_DATEFORMAT, and set the value to the display format
string.
Encrypting Passwords
You can encrypt passwords to create an environment variable to use with infacmd, infasetup, pmcmd, and
pmrep or to define a password in a parameter file.
For example, you can encrypt the repository and database passwords for pmrep to maintain security when
using pmrep in scripts. Then you can create an environment variable to store the encrypted password. Or,
you can define a password for a relational database connection object in a parameter file.
Use the command line program pmpasswd to encrypt passwords. The pmpasswd utility installs in the
following directory:
<InformaticaInstallationDir>/server/bin
The pmpasswd utility uses the following syntax:
pmpasswd <password> [-e (CRYPT_DATA | CRYPT_SYSTEM)]
The following table describes pmpasswd options and arguments:
Option
Argument
Description
password
Required. The password to encrypt.
-e
CRYPT_DATA,
Optional. Encryption type:
CRYPT_SYSTEM
- CRYPT_DATA. Use to encrypt connection object passwords

that you define in a parameter file.
- CRYPT_SYSTEM. Use for all other passwords.
Default is CRYPT_SYSTEM.
54
Using a Password as an Environment Variable

1.
Use the command line program pmpasswd to encrypt the password.

monday, the password encrypts to f/wRb5PZsZnqESTDPeos7Q==.
2.
Configuring a Password as an Environment Variable on UNIX

To configure a password as an environment variable on UNIX:
1.

pmpasswd <password>
2.

setenv <Password_Environment_Variable> <encrypted password>
<Password_Environment_Variable> = <encrypted password>
export <Password_Environment_Variable>
You can assign the environment variable any valid UNIX name.
Configuring a Password as an Environment Variable on Windows

To configure a password as an environment variable on Windows:
1.

pmpasswd <password>
2.
Enter the password environment variable in the Variable field. Enter the encrypted password in the Value
field.
Setting the User Name

For pmcmd and pmrep, you can create an environment variable to store the user name.
Configuring a User Name as an Environment Variable on UNIX

To configure a user name as an environment variable on UNIX:
u

setenv <User_Name_Environment_Variable> <user name>
<User_Name_Environment_Variable> = <user name>
export <User_Name_Environment_Variable>
You can assign the environment variable any valid UNIX name.
Setting the User Name
55
Configuring a User Name as an Environment Variable on Windows

To configure a user name as an environment variable on Windows:
u
Enter the user name environment variable in the Variable field. Enter the user name in the Value field.
56
CHAPTER 5
Using infacmd
Using infacmd Overview, 57
infacmd Command Programs, 58
Running Commands, 59
infacmd Return Codes, 59
infacmd UpdateGatewayInfo, 60
Using infacmd Overview

infacmd is a command line program that allows you to administer domains, users, and services. Use infacmd
to administer the following objects and services:
Application services and processes. Create, enable, disable, remove, and get the status of application
services and the associated service processes. Ping services. List services and the nodes that run them.
Update service processes and service process options. You cannot use infacmd to create services of a
previous version.
Domain gateway. Update the gateway node connectivity information.
Domains. Link domains and remove domain links. Change the domain administrator password. Update
domain options. Add and remove service levels.
Folders. Create, move, list, update, and remove folders. Move objects between folders.
Grids. Create and remove grids. List nodes in a grid.
Licenses. Add, remove, assign, unassign, and list licenses. Show license information.
Log events. Get and purge log events. Get session and workflow logs. Convert log files from binary to
text format.
Nodes. Update, ping, shut down, and remove nodes. List node names and options. Update the node role.
Add, enable, list, disable, and remove node resources. Change a node from a gateway node to a worker
node or from a worker node to a gateway node. Calculate the CPU profile for a node.
Users. Create and remove users. Reset user passwords. Subscribe to and unsubscribe users from alerts.
Assign users permission on objects. Enable user account lockout and unlock user accounts.
57
infacmd Command Programs

The infacmd program supports all Informatica application services. The Informatica domain has a separate
infacmd programs to support each application service.
The command line interface has the following infacmd programs:
infacmd advanced manages advanced features like account lockout and plug-in validation.
infacmd as manages Analyst Services.
infacmd cms manages Content Management Services.
infacmd csm manages the CSM diagnostics.
infacmd dis manages Data Integration Services.
infacmd ide migrates Data Explorer Legacy objects to Informatica Data Explorer.
infacmd ipc exports mappings from the Model repository to the PowerCenter repository.
infacmd isp administers the domain, security, and PowerCenter application services.
infacmd mrs manages Model Repository Services.
infacmd ms lists and runs deployed mappings.
infacmd oie manages exporting objects from the Model repository and importing objects into the Model
repository.
infacmd ps manages the profiling warehouse contents, profiles, and scorecards.
infacmd pwx manages PowerExchange Listener and Logger Services.
infacmd rds manages the Reporting and Dashboards Service.
infacmd rms manages the Resource Manager Service.
infacmd rtm manages import and export operations for reference table data.
infacmd sch manages the Scheduler Service.
Infacmd search manages the Search Service.
infacmd sql manages SQL data services that you deploy to the Data Integration Service.
infacmd wfs manages workflows that you deploy to the Data Integration Service.
infacmd ws manages web services that you deploy to the Data Integration Service.
infacmd xrf manages XML files exported from the Model repository.
infacmd ListPlugins
Each infacmd program has a plugin identifier. When you run the program, you include the plugin ID as part of
the program name.
For example, dis is the plugin ID for the Data Integration Services infacmd program.
For example, to run a command that lists deployed applications, run the infacmd dis ListApplications
command:
infacmd dis ListApplications -dn domain_name -un user_name -d password -sn
Data_Integration_Service_Name
To list the plugin IDs, enter the following command:
infacmd (.sh) ListPlugins
To list the valid commands for a plugin, enter the following command:
58
Chapter 5: Using infacmd
infacmd(.sh) plugin_ID Help

To display help for one command, enter the following command:
infacmd(.sh) plugin_ID CommandName Help
Running Commands
Invoke infacmd from the command line. You can issue commands directly or from a script, batch file, or other
program.
To run infacmd commands:
1.
At the command prompt, switch to the directory where the infacmd executable is located.
By default, infacmd installs in the following directory of the Informatica services installation:
<Informatica installation directory>/isp/bin
You can also install infacmd from the Informatica Installation DVD.
2.
Enter infacmd on Windows or infacmd.sh on UNIX followed by the plugin ID, the command name, and
the required options and arguments. The command names are not case sensitive.
For example:
infacmd(.sh) plugin_ID CommandName [-option1] argument_1 [-option2]
argument_2...Command Options
When you run infacmd, you enter options for each command, followed by the required arguments. For
example, most commands require that you enter the domain name, user name, and password using
command options. Command options are preceded with a hyphen and are not case sensitive. Arguments
follow the option.
To enter an argument that is preceded with a hyphen, enclose the argument in quotation marks using the
backslash (\) as an escape character before each quotation mark. For example, the following command
writes the log for the mapping run with the job ID "-qnLI7G_TEeW9olHBkc9hoA" to the file "MyLog.log" within
the infacmd directory on Windows:
infacmd ms GetRequestLog -dn MyDomain -sn MyDIS -un AdminUser -pd password -id \"qnLI7G_TEeW9olHBkc9hoA\" -f MyLog.log
If you omit or incorrectly enter one of the required options, the command fails and infacmd returns an error
message.
You can use environment variables for some command options with infacmd. For example, you can store the
default user name and password for a domain as environment variables so that you do not have to enter
them using command options. Configure these variables before you use infacmd.
infacmd Return Codes

The infacmd program indicates the success or failure of a command with the following return codes:
0 indicates that the command succeeded.
-1 indicates that the command failed.
Running Commands
59
Use the DOS or UNIX echo command immediately after running an infacmd command to see the return code
for the command:
In a DOS shell: echo %ERRORLEVEL%
In a UNIX Bourne or Korn shell: echo $?
In a UNIX C shell: echo $status
infacmd UpdateGatewayInfo
Updates the domain information file from the command line.
Run infacmd isp UpdateGatewayInfo to create a domains.infa file or update a domains.infa file. The
domains.infa file contains the connectivity information for a gateway node in a domain along with the TLS and
Kerberos configuration of the domain. The connectivity information includes the domain name, domain host
name, and domain host HTTP port.
You might need to generate a domains.infa file to run infacmd oie commands on a client machine. To
generate the domains.infa file, run infacmd isp UpdateGatewayInfo. The updateGatewayInfo command
generates a domains.infa file in the DeveloperClient directory. Define the domain gateway host name and
port when you run the command.
The infacmd UpdateGatewayInfo command uses the following syntax:
UpdateGatewayInfo
<-DomainName|-dn> domain_name
<-GatewayAddress|-dg> domain_gateway_host:port
[<-Force|-f>]
The following table describes infacmd UpdateGatewayInfo options and arguments:
Option
Argument
Description
-DomainName
domain_name
Required. Name of the Informatica domain. You can set

the domain name with the -dn option or the
environment variable INFA_DEFAULT_DOMAIN. If you
set a domain name with both methods, the -dn option
takes precedence.
domain_gateway_h
ost:port
Required. Enter the gateway address in the following

format:
-dn
-GatewayAddress
-dg
domain_gateway_host:port
-Force
-f
60
Chapter 5: Using infacmd
Optional. Updates or creates the domains.infa file even

when the connection to the domain fails. The Force
option sets the Kerberos and TLS enabled options as
false in the domains.infa file if the connection to
domain fails. If you do not specify the Force option,
the command does not update the domains.infa file if
the connection to the domain fails.
CHAPTER 6
infacmd as Command Reference

CreateService, 61
CreateAuditTables, 64
DeleteAuditTables, 66
ListServiceOptions, 67
ListServiceProcessOptions, 68
UpdateServiceOptions, 70
UpdateServiceProcessOptions, 72
CreateService
Creates an Analyst Service in a domain. Also associates a Model Repository Service, Data Integration
Services, and Metadata Manager Service with the Analyst Service.
The infacmd as CreateService command uses the following syntax:
CreateService
<-NodeName|-nn> node_name
<-ServiceName|-sn> service_name
<-UserName|-un> user_name
<-Password|-pd> password
[<-SecurityDomain|-sdn> security_domain]
[<-ResilienceTimeout|-re> timeout_period_in_seconds]
[<-RepositoryService|-rs> model_repository_service_name]
[<-DataIntegrationService|-ds> data_integration_service_name]
[<-HumanTaskDataIntegrationService|-htds> human_task_data_integration_service_name]
[<-MetadataManagerService|-mm> metadata_manager_service_name]
[<-FlatFileCacheLocation|-ffl> flat_file_location]
[<-RepositoryUsername|-au> model_repository_user_name]
61
[<-RepositorySecurityDomain|-rssdn> model_repository_security_domain]
[<-RepositoryPassword|-ap> model_repository_password]
[<-BusinessGlossaryExportFileDirectory|-bgefd> business_glossary_export_file_directory]
<-HttpPort> http_port
The following table describes infacmd as CreateService options and arguments:
Option
Argument
Description
-DomainName
domain_name
Required. Name of the Informatica domain. You can

set the domain name with the -dn option or the
environment variable INFA_DEFAULT_DOMAIN. If
you set a domain name with both methods, the -dn
option takes precedence.
node_name
Required. Name of the node where the Analyst

Service will run.
-dn
-NodeName
-nn
-ServiceName
service_name
-sn
Required. Name of the Analyst 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 associated repository. The
name cannot exceed 230 characters, have leading or
trailing spaces, or contain carriage returns, tabs, or
the following characters:
/ * ? < > " |
-UserName
user_name
-un
Required if the domain uses Native or LDAP

authentication. User name to connect to the domain.
You can set the user name with the -un option or the
environment variable
INFA_DEFAULT_DOMAIN_USER. If you set a user
name with both methods, the -un option takes
precedence.
Optional if the domain uses Kerberos authentication.
To run the command with single sign-on, do not set
the user name. If you set the user name, the command
runs without single sign-on.
-Password
password
-pd
62
Chapter 6: infacmd as Command Reference
Required if you specify the user name. Password for

the user name. The password is case sensitive. You
can set a password with the -pd option or the
INFA_DEFAULT_DOMAIN_PASSWORD. If you set a
password with both methods, the password set with
the -pd option takes precedence.
Option
Argument
Description
-SecurityDomain
security_domain
Required if the domain uses LDAP authentication.

Optional if the domain uses native authentication or
Kerberos authentication. Name of the security domain
to which the domain user belongs. You can set a
security domain with the -sdn option or the
INFA_DEFAULT_SECURITY_DOMAIN. If you set a
security domain name with both methods, the -sdn
option takes precedence. The security domain name is
case sensitive.
-sdn
If the domain uses native or LDAP authentication, the

default is Native. If the domain uses Kerberos
authentication, the default is the LDAP security
domain created during installation. The name of the
security domain is the same as the user realm
specified during installation.
-ResilienceTimeout
-re
-RepositoryService
-rs
timeout_period_in_secon
ds
model_repository_service
_name
Optional. Amount of time in seconds that infacmd

attempts to establish or re-establish a connection to
the domain. You can set the resilience timeout period
with the -re option or the environment variable
INFA_CLIENT_RESILIENCE_TIMEOUT. If you set a
the resilience timeout period with both methods, the re option takes precedence. Default is 180 seconds.
Optional. Name of the Model Repository Service.
/ * ? < > " |
-DataIntegrationService
-ds
HumanTaskDataIntegratio
nService
data_integration_service_
name
Optional. Data Integration Service name associated

with the Analyst Service.
human_task_data_integra
tion_service_name
Optional. Data Integration Service that runs Human

tasks.
metadata_manager_servi
ce_name
Optional. Metadata Manager Service name associated

with the Analyst Service.
flat_file_location
Optional. Full path, excluding the domain name, to the

folder in which you want to cache the flat files. Must be
in the following format:
-htds
MetadataManagerService
-mm
-FlatFileCacheLocation
-ffl
/parent_folder/child_folder
CreateService
63
Option
Argument
Description
-RepositoryUserName
model_repository_user_n
ame
Required if you specify a Model Repository Service.

User name to connect to the Model repository.
-au
If you enter a user name that contains a space or

other non-alphanumeric character, enclose the name
in quotation marks.
RepositorySecurityDomai
n
model_repository_securit
y_domain
Required if you use LDAP authentication. Name of the

security domain to which the Administrator user
belongs.
model_repository_passw
ord
Required if you specify a Model Repository Service.

User password for the Model Repository Service.
business_glossary_expor
t_file_directory
Optional. Location of the directory to export business

glossary files.
http_port
Required. Port number for the Analyst Service.
-rssdn
-RepositoryPassword
-ap
BusinessGlossaryExportFi
leDirectory
-bgefd
-HttpPort
CreateAuditTables
Creates audit tables that contain audit trail log events for bad record tables and duplicate tables in
Informatica Analyst.
The infacmd as CreateAuditTables command uses the following syntax:
CreateAuditTables
64
The following table describes infacmd as CreateAuditTables options and arguments:

Option
Argument
Description
-DomainName
domain_name

service_name
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

security domain that the user belongs to. You can set
a security domain with the -sdn option or the
option takes precedence. Security domain is case
sensitive. Default is Native.
ds

INFA_CLIENT_RESILIENCE_TIMEOUT. If you set the
resilience timeout period with both methods, the -re
-pd
-SecurityDomain
-sdn
-ResilienceTimeout
-re
CreateAuditTables
65
DeleteAuditTables
Deletes audit tables that contain audit trail log events for bad record tables and duplicate tables in Informatica
Analyst.
The infacmd as DeleteAuditTables command uses the following syntax:
DeleteAuditTables
The following table describes infacmd as DeleteAuditTables options and arguments:
Option
Argument
Description
-DomainName
domain_name

-dn
-ServiceName
service_name
-sn
-UserName

The name is not case sensitive.
user_name
-un

precedence.
-Password
password
-pd
66

Option
Argument
Description
-SecurityDomain
security_domain

security domain that the user belongs to. You can set
a security domain with the -sdn option or the
ds

-sdn
-ResilienceTimeout
-re
ListServiceOptions
Lists Analyst Service options. Lists the values for each Analyst Service option.
The infacmd as ListServiceOptions command uses the following syntax:
ListServiceOptions
The following table describes infacmd as ListServiceOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
Required. Name of the Analyst Service. The name is

not case sensitive.
-dn
-ServiceName
-sn
ListServiceOptions
67
Option
Argument
Description
-UserName
user_name

precedence.
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
ds

ListServiceProcessOptions
Lists the Analyst Service process options.
The infacmd as ListServiceProcessOptions command uses the following syntax:
68
The following table describes infacmd as ListServiceProcessOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
Required. Name of the Analyst Service. The name is

not case sensitive.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
-pd
password

69
Option
Argument
Description
-SecurityDomain
security_domain

case sensitive.
-sdn

-ResilienceTimeout
-re
ds
-ResilienceTimeout
-NodeName
node_name
-nn

Required. Node where the Analyst Service process
runs.
UpdateServiceOptions
Updates Analyst Service options. To view current option values, run infacmd as ListServiceOptions.
Enter connection options in the following format:
... -o option_name=value option_name=value ...
Separate multiple options with a space. To enter a value that contains a space or other non-alphanumeric
character, enclose the value in quotation marks.
The infacmd as UpdateServiceOptions command uses the following syntax:
[<-Options |-o> options]
70
The following table describes infacmd as UpdateServiceOptions options and arguments:

Option
Argument
Description
-DomainName
domain_name

service_name
-dn
-ServiceName
-sn
-UserName
The name is not case sensitive.

user_name
-un

precedence.
-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

71
Option
Argument
Description
-ResilienceTimeout
-re
ds

-Options
options
Optional. List of options to configure. Separate each

option with a space. To view options, run the infacmd
as ListServiceOptions command.
-o
UpdateServiceProcessOptions
Updates options for the Analyst Service process. To view options, run the infacmd as
ListServiceProcessOptions command.
The infacmd as UpdateServiceProcessOptions command uses the following syntax:
<-Options|-o> options
The following table describes infacmd as UpdateServiceProcessOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name
Required. Name of the Informatica domain. You can set the

domain name with the -dn option or the environment variable
INFA_DEFAULT_DOMAIN. If you set a domain name with
both methods, the -dn option takes precedence.
service_name
-dn
-ServiceName
-sn
72
Option
Argument
Description
-UserName
user_name
Required if the domain uses Native or LDAP authentication.

User name to connect to the domain. You can set the user
name with the -un option or the environment variable
INFA_DEFAULT_DOMAIN_USER. If you set a user name
with both methods, the -un option takes precedence.
-un
Optional if the domain uses Kerberos authentication. To run

the command with single sign-on, do not set the user name.
If you set the user name, the command runs without single
sign-on.
-Password
password
Required if you specify the user name. Password for the user
name. The password is case sensitive. You can set a
password with the -pd option or the environment variable
password with both methods, the password set with the -pd
security_domain
Required if the domain uses LDAP authentication. Optional if

the domain uses native authentication or Kerberos
authentication. Name of the security domain to which the
domain user belongs. You can set a security domain with the
-sdn option or the environment variable
INFA_DEFAULT_SECURITY_DOMAIN. If you set a security
domain name with both methods, the -sdn option takes
precedence. The security domain name is case sensitive.
-pd
-SecurityDomain
-sdn
If the domain uses native or LDAP authentication, the default

is Native. If the domain uses Kerberos authentication, the
default is the LDAP security domain created during
installation. The name of the security domain is the same as
the user realm specified during installation.
-ResilienceTimeout
-re
timeout_period_in_sec
onds
Optional. Amount of time in seconds that infacmd attempts to

establish or re-establish a connection to the domain. You can
set the resilience timeout period with the -re option or the
INFA_CLIENT_RESILIENCE_TIMEOUT. If you set a the
resilience timeout period with both methods, the -re option
takes precedence.
-NodeName
node_name
Required. Node where the Analyst Service process runs.
options
Required. List of options to configure. Separate each option

with a space. To view options, run the infacmd as
-nn
-Options
-o
73
CHAPTER 7
infacmd aud Command Reference

getDomainObjectPermissions, 74
getPrivilegeAssociation, 76
getUserGroupAssociation, 78
getUserGroupAssociationForRoles, 80
getUsersPersonalInfo, 82
getDomainObjectPermissions
Gets the list of domain objects to which the specified users or groups have permission. You can generate
reports for the specified users or groups.
Users with the administrator role can run this command.
The infacmd aud getDomainObjectPermissions command uses the following syntax:
[<-Gateway|-hp> gateway_host1:port gateway_host2:port...]
<<-ExistingUserNames|-eu> existing_user_names|
<-ExistingGroupNames|-eg> existing_group_names>
[<-ExistingSecurityDomain|-esd> existing_security_domain]
[<-Format|-fm> format_TEXT_CSV]
[<-OutputFile|-lo> output_file_name]
74
The following table describes infacmd aud getDomainObjectPermissions options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain
Name of the security domain that you want to create to

which the domain user belongs. You can set a security
domain with the -sdn option or the environment
variable INFA_DEFAULT_SECURITY_DOMAIN. If you
set a security domain name with both methods, the sdn option takes precedence. The security domain
name is case sensitive.
-pd
-SecurityDomain
-sdn
You can specify a value for sdn or use the default

based on the authentication mode:
- Required if the domain uses LDAP authentication.
Default is Native. To work with LDAP authentication,
you need to specify the value for -sdn.
- Optional if the domain uses native authentication or
Kerberos authentication. Default is native for native
authentication. If the domain uses Kerberos
authentication, the default is the LDAP security domain
created during installation. The name of the security
domain is the same as the user realm specified during
installation.
-Gateway
-hp
gateway_host1:port
gateway_host2:port ...
Required if the gateway connectivity information in the

domains.infa file is out of date. Specify the host names
and port numbers for the gateway nodes in the
domain.
75
Option
Argument
Description
-ResilienceTimeout
-re
ds

-ExistingUserNames
existing_user_names
Required if you do not use ExistingGroupNames (eg). Name of the user or a list of users to run the
reports. For multiple users, separate each user by a
comma at the command line.
existing_group_names
Required if you do not use ExistingUserName (-eu).

Name of the group or a list of groups to run the
reports. For multiple groups, separate each group by a
existing_security_domain
Required if you use LDAP authentication. Security

domain to which the user or group belongs. Default is
Native.
-eu
-ExistingGroupNames
-eg
-ExistingSecurityDomain
-esd
-Format
format_TEXT_CSV
Optional. Output file format. Valid types include:

- Text
- CSV
-fm
If you do not specify a format, infacmd uses text

format with lines wrapped at 80 characters.
-OutputFile
output_file_name
-lo
Optional. Name and file path for the output file.

If you do not specify an output file name, infacmd
displays the log events on the screen.
getPrivilegeAssociation
Gets privileges assigned to the users or groups. You can select the users or groups for which you want to
generate report.
The infacmd aud getPrivilegeAssociation command uses the following syntax:
76
Chapter 7: infacmd aud Command Reference
The following table describes infacmd aud getPrivilegeAssociation options and arguments:
Option
Argument
Description
-DomainName
domain_name

takes precedence.
user_name

precedence.
-dn
-UserName
-un

To run the command with single sign-on, do not set the
user name. If you set the user name, the command
-Password
password

password with both methods, the password set with the
-pd option takes precedence.
security_domain

security domain with the -sdn option or the environment
-pd
-SecurityDomain
-sdn

authentication, the default is the user realm name
-Gateway
-hp
gateway_host1:port

domains.infa file is out of date. The host names and
port numbers for the gateway nodes in the domain.
77
Option
Argument
Description
-ResilienceTimeout
-re
timeout_period_in_seco
nds

attempts to establish or re-establish a connection to the
domain. You can set the resilience timeout period with
the -re option or the environment variable
-ExistingUserNames
existing_user_names
Required if you do not use ExistingGroupNames (-eg).

Name of the user or a list of users to run the reports.
For multiple users, separate each user by a comma at
the command line.

Name of the group or a list of groups to run the reports.
For multiple groups, separate each group by a comma
at the command line.
-esd
existing_security_domai
n

Native.
-Format
format_TEXT_CSV
-eu
-ExistingGroupNames
-eg

- Text
- CSV
-fm
If you do not specify a format, infacmd uses text format

with lines wrapped at 80 characters.
-OutputFile
output_file_name
-lo

getUserGroupAssociation
Gets list of users that belong to the group or a list of groups associated with specified users. You can select
the users or groups for which you want to generate report.
The infacmd aud getUserGroupAssociation command uses the following syntax:
78
The following table describes infacmd aud getUserGroupAssociation options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
-hp
gateway_host1:port

79
Option
Argument
Description
-ResilienceTimeout
-re
ds

-ExistingUserNames
existing_user_names


Native.
-eu
-ExistingGroupNames
-eg
-esd
-Format
format_TEXT_CSV

- Text
- CSV
-fm

-OutputFile
output_file_name
-lo

getUserGroupAssociationForRoles
Gets list of roles assigned to users and groups. You can select the roles for which you want to generate
report.
The infacmd aud getUserGroupAssociationForRoles command uses the following syntax:
80
<-RoleNames|-en> role_names
The following table describes infacmd aud getUserGroupAssociationForRoles options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
-hp
gateway_host1:port

81
Option
Argument
Description
-ResilienceTimeout
-re
ds

-RoleNames
role_names
Required. Name of the role assigned for users or

groups in the domain for which you want to generate
the report. For multiple roles, separate each role by a
-en
-Format
format_TEXT_CSV

- Text
- CSV
-fm

-OutputFile
output_file_name
-lo

getUsersPersonalInfo
Gets user information in the domain. The report displays the full name, security domain, description, contact
details, and user status. If you run the report for users, the report displays the user information for the
specified users. If you run the report for groups, the report organizes user information for all users in the
specified group. The report displays nested groups separately.
The infacmd aud getUsersPersonalInfo command uses the following syntax:
82
The following table describes infacmd aud getUsersPersonalInfo options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
-hp
-ResilienceTimeout
-re
gateway_host1:port

ds

83
Option
Argument
Description
-ExistingUserNames
existing_user_names


Native.
-eu
-ExistingGroupNames
-eg
-esd
-Format
format_TEXT_CSV

- Text
- CSV
-fm

-OutputFile
output_file_name
-lo
84

CHAPTER 8
Infacmd bg Command Reference

This chapter includes the following topic:
upgradeRepository, 85
upgradeRepository
Upgrades the Business Glossary data in the Model repository. Run this command after you upgrade the
domain.
The infacmd bg upgradeRepository command uses the following syntax:
upgradeRepository
<-Password|-pd> Password
<-AtServiceName|-atn> Analyst_service_name
The following table describes infacmd bg upgradeRepository options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

85
Option
Argument
Description
-Password
Password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

AtServiceName
Analyst_service_name
-atn

/ * ? < > " |
86
Chapter 8: Infacmd bg Command Reference
CHAPTER 9
infacmd cms Command

Reference
CreateAuditTables, 87
CreateService, 89
DeleteAuditTables, 91
Purge, 96
RemoveService, 97
ResyncData, 99
Upgrade, 105
CreateAuditTables
Creates audit tables that contain audit trail log events for reference tables managed by the specified Content
Management Service.
The infacmd cms CreateAuditTables command uses the following syntax:
CreateAuditTables
87
The following table describes infacmd cms CreateAuditTables options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
Required. Name of the Content Management Service.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

the -pd option takes precedence..
security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
88
ds
Chapter 9: infacmd cms Command Reference

CreateService
Creates a Content Management Service in a domain.
The infacmd cms CreateService command uses the following syntax:
CreateService
<-DataServer|-ds> data_service_name
<-RepositoryService|-rs> repository_service_name
<-RepositoryUsername|-rsu> repository_user_name
<-RepositoryPassword|-rsp> repository_password
[<-RepositorySecurityDomain|-rssd> repository_security_domain]
<-ReferenceDataLocation|-rdl> reference_data_location
[<-HttpPort> http_port]
[<-HttpsPort> https_port]
[<-KeystoreFile|-kf> keystore_file_location]
[<-KeystorePassword|-kp> keystore_password]
The following table describes infacmd cms CreateService options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
-dn
-ServiceName
-sn

/ * ? < > " |
CreateService
89
Option
Argument
Description
-UserName
user_name

precedence.
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
ds

-NodeName
node_name
Required. Name of the node where the Content

Management Service will run.
data_service_name
Required. Data Integration Service name associated

with the Content Management Service.
repository_service_name
Required. Model Repository Service to associate with

the Content Management Service.
-nn
-DataServer
-ds
-RepositoryService
-rs
90
Option
Argument
Description
-RepositoryUsername
repository_user_name
Required. User name to connect to the Model

Repository Service.
-rsu
To perform reference table management tasks in the

Model repository, the user identified in the property
must have the Model Repository Service Administrator
role. The reference table management tasks include
purge operations on orphaned reference tables.
-RepositoryPassword
repository_password
Required. Password to connect to the Model

Repository Service.
repository_security_doma
in

security domain that the user belongs to. Security
domain is case sensitive. Default is Native.
reference_data_location
Required. Connection name for the database that

stores data values for the reference tables defined in
the Model repository. The specified database stores
reference data values. The Model repository stores
metadata for the reference tables.
-HttpPort
http_port
Required. Unique HTTP port number for the Content

Management Service.
-HttpsPort
https_port
Optional. HTTPS port number that the service runs on

when you enable the Transport Layer Security (TLS)
protocol.
-KeystoreFile
keystore_file_location
Path and file name of the keystore file that contains

the keys and certificates required if you enable TLS
and use the HTTPS protocol for the service.
keystore_password
Required if you enable TLS and use HTTPS

connections for the service. A plain-text password for
the keystore file.
-rsp
RepositorySecurityDomai
n
-rssd
-ReferenceDataLocation
-rdl
-kf
-KeystorePassword>
-kp
DeleteAuditTables
Deletes the audit trail tables for the specified Content Management Service.
The infacmd cms DeleteAuditTables command uses the following syntax:
DeleteAuditTables
DeleteAuditTables
91
The following table describes infacmd cms DeleteAuditTables options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
92
ds

ListServiceOptions
Lists the options for a Content Management Service.
The infacmd cms ListServiceOptions command uses the following syntax:
ListServiceOptions
The following table describes infacmd cms ListServiceOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
-pd
password

ListServiceOptions
93
Option
Argument
Description
-SecurityDomain
security_domain

case sensitive.
-sdn

-ResilienceTimeout
-re
ds

Lists the options for a Content Management Service process.
The infacmd cms ListServiceProcessOptions command uses the following syntax:
94
The following table describes cms ListServiceProcessOptions options and arguments:

Option
Argument
Description
-DomainName
domain_name

service_name
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
ds

NodeName
node_name
Required. Name of the node where the service

process runs.
-nn
95
Purge
Deletes from the reference data warehouse any reference table that is no longer associated with a reference
table object in the Model repository.
When you run infacmd cms Purge, the Content Management Service identifies the tables that store data for
reference table objects in the associated Model repository. The Content Management Service deletes all
other tables from the warehouse and generates a list of the deleted tables. Run infacmd cms Purge on the
master Content Management Service for the Model repository.
Note: To prevent accidental data loss, the purge operation does not delete tables if the Model repository
does not contain a reference table object.
Before you run infacmd cms Purge, verify the following prerequisites:
The user name that you specify in the command has the Manage Service privilege on the domain.
The Model repository user that the Content Management Service specifies has the Administrator role on
the Model Repository Service.
All Data Integration Services associated with the Model repository are available.
There are no data operations in progress on the reference data warehouse.
The reference data warehouse stores data for the reference table objects in a single Model repository.
The infacmd cms Purge command uses the following syntax:

Purge
The following table describes infacmd cms Purge options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
-dn
-ServiceName
-sn

/ * ? < > " |
96
Option
Argument
Description
-UserName
user_name

precedence.
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
ds

RemoveService
Removes the Content Management Service from the domain. Before you remove the service, you must
disable it.
The infacmd cms RemoveService command uses the following syntax:
RemoveService
RemoveService
97
The following table describes infacmd cms RemoveService options and arguments:
Option
Argument
Description
-DomainName
domain_name

INFA_DEFAULT_DOMAIN. If you set a domain name with both
methods, the -dn option takes precedence.
service_name
Required. Name of the service you want to remove. To enter a

name that contains a space or other non-alphanumeric
character, enclose the name in quotation marks.
user_name

INFA_DEFAULT_DOMAIN_USER. If you set a user name with
both methods, the -un option takes precedence.
-dn
-ServiceName
-sn
-UserName
-un
Optional if the domain uses Kerberos authentication. To run the

command with single sign-on, do not set the user name. If you
set the user name, the command runs without single sign-on.
-Password
password
name. The password is case sensitive. You can set a password
with the -pd option or the environment variable
INFA_DEFAULT_DOMAIN_PASSWORD. If you set a password
with both methods, the password set with the -pd option takes
precedence.
security_domain

domain user belongs. You can set a security domain with the sdn option or the environment variable
-pd
-SecurityDomain
-sdn
If the domain uses native or LDAP authentication, the default is

Native. If the domain uses Kerberos authentication, the default
is the LDAP security domain created during installation. The
name of the security domain is the same as the user realm
-ResilienceTimeout
-re
98
timeout_period_in_se
conds

establish or reestablish a connection to the domain. If you omit
this option, infacmd uses the timeout value specified in the
INFA_CLIENT_RESILIENCE_TIMEOUT environment variable. If
no value is specified in the environment variable, the default of
180 seconds is used.
ResyncData
Synchronizes probabilistic model files or classifier model files between a specified Content Management
Service machine and the master Content Management Service machine in the domain. The ResyncData
command updates the files on the Content Management Service machine that you specify with the files from
the master Content Management Service machine.
The command synchronizes any file saved on the master Content Management Service machine after a time
and date that you specify. You run the ResyncData command for a single type of model file. To synchronize
probabilistic model files and classifier model files, you must run the command twice.
When you run infacmd cms ResyncData, you must have access permissions on both Content Management
Service machines. Informatica Administrator sets the access permissions on the services.
The infacmd cms ResyncData command uses the following syntax:
ResyncData
<-Type|-t> type
<-StartTime|-st> start_time
The following table describes infacmd cms resyncData options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

The command copies files to the machine that hosts
the service.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

ResyncData
99
Option
Argument
Description
-Password
password

the -pd option takes precedence
.
security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
ds

-Type
type
Required. Identifies the type of data file to copy from

the master Content Management Service machine.
Enter one of the following options:
-t
- NER. Specifies probabilistic model data files.

- Classifier. Specifies classifier model data files.
-StartTime
start_time
-st
Required. Identifies the files to copy from the master

Content Management Service machine to the Content
Management Service machine that you specify in the
ServiceName property. The command does not copy
any file with a time stamp earlier than the StartTime
value. The command uses the system clock on the
master Content Management Service machine to
determine the time.
Enter the date in the default locale format.
100
Updates the Content Management Service with options that are introduced in the current release. To view
current options, run the infacmd cms ListServiceOptions command.
The infacmd cms UpdateServiceOptions command uses the following syntax:
The following table describes infacmd cms UpdateServiceOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
-pd
password

101
Option
Argument
Description
-SecurityDomain
security_domain

case sensitive.
-sdn

-ResilienceTimeout
-re
ds

-Options
options
Required. Enter each option and value to update.

Separate each option by a space. To view application
options, run the infacmd cms ListServiceOptions
command.
-o
Username and Password Options

You can use the UpdateServiceProcessOptions -o option to update the user name and password that the
Content Management Service uses to connect to the Model Repository Service.
Use the DataServiceOptions.RepositoryUsername and DataServiceOptions.RepositoryPassword options to
update the user name and password values. You can also set the values in Informatica Administrator.
Reference Data Location Option

You can use the UpdateServiceProcessOptions -o option to update the path to the reference data staging
directory. The Content Management Service uses the directory to stage data that it adds to a reference table.
Use the FileTransferOptions.TempLocation option to update the staging directory location. You can also set
the location in Informatica Administrator.
102
Updates options for a Content Management Service process. To view current options, run the infacmd cms
The infacmd cms UpdateServiceProcessOptions command uses the following syntax:
The following table describes infacmd cms UpdateServiceProcessOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
-pd
password

103
Option
Argument
Description
-SecurityDomain
security_domain

case sensitive.
-sdn

-ResilienceTimeout
-re
ds

NodeName
node_name

process runs.
options

options, run the infacmd cms
-nn
-Options
-o
Identity Match Analysis Options

You can use the UpdateServiceProcessOptions -o option to update the following properties for identity match
analysis:
IdentityOptions.IdentityReferenceDataLocation. Specifies the location of identity population files.
IdentityOptions.IdentityCacheDir. Specifies the location of the cache directory used in identity match
analysis.
IdentityOptions.IdentityIndexDir. Specifies the location of the index key directory used in identity match
analysis.
You can also set the properties in Informatica Administrator.
104
Upgrade
Upgrades the Content Management Service configuration. Run infacmd cms Upgrade when you upgrade to
the current version of Informatica Data Quality.
The infacmd cms Upgrade command uses the following syntax:
Upgrade
The infacmd cms Upgrade command checks the service configuration on the domain and verifies the
following service options:
Master Content Management Service
The Upgrade command verifies that the Model repository in the domain uses a master Content
Management Service. If the Model Repository Service does not specify a master Content Management
Service, the Upgrade command sets the current service as the master Content Management Service .
By default, the first Content Management Service to connect to a Model Repository Service becomes the
master Content Management Service.
Model Repository Service
The Upgrade command uses the Data Integration Service associated with the Content Management
Service to identify the Model Repository Service in the domain.
The Upgrade command verifies that the Content Management Service has a valid username, password,
and security domain to connect to the Model Repository Service. If these options are not set, the
Upgrade command uses the username, password, and security domain values on the associated Data
Integration Service to connect to the Model Repository Service.
Reference Data Location
The Upgrade command verifies that the Content Management Service specifies a reference data
location. If the service does not specify a reference data location, the Upgrade command sets the
location to the staging database defined on the Analyst Service.
The following table describes infacmd cms Upgrade options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
-dn
-ServiceName
-sn
Upgrade
105
Option
Argument
Description
-UserName
user_name

precedence.
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
106
ds

CHAPTER 10
infacmd dis Command Reference

AddParameterSetEntries, 108
BackupApplication, 110
CancelDataObjectCacheRefresh, 111
CreateService, 113
DeleteParameterSetEntries, 116
DeployApplication, 118
ListApplications, 120
ListApplicationObjects, 122
ListApplicationOptions, 124
ListComputeOptions, 125
ListDataObjectOptions, 127
ListParameterSetEntries, 129
ListParameterSetObjects, 130
ListParameterSets, 132
ListSequenceObjectProperties, 133
ListSequenceObjects, 135
PurgeDataObjectCache, 140
PurgeResultSetCache, 142
RefreshDataObjectCache, 144
RenameApplication, 145
RestoreApplication, 147
SetSequenceState, 149
StartApplication, 151
StopApplication, 153
stopBlazeService, 154
UndeployApplication, 156
UpdateApplication, 157
UpdateApplicationOptions, 159
107
UpdateComputeOptions, 161
UpdateDataObjectOptions, 163
UpdateParameterSetEntries, 165
UpdateServiceOptions , 167
UpdateServiceProcessOptions , 177
AddParameterSetEntries
Adds entries to a parameter set. Run this command to add parameters from a mapping or workflow that has
been deployed as an application.
The infacmd dis AddParameterSetEntries command uses the following syntax:
<-Application|-a> application
<-parameterSetName|-ps> parameter set name
<-projectScope|-prs> path to the mapping or workflow that contains the parameters. For
a mapping, M1, in project P1 and folder F1, the path is P1/F1/mapping/M1.
<-paramNameValues|-pnv> parameter name-value pairs, separated by space
The following table describes infacmd dis AddParameterSetEntries options and arguments:
Option
Argument
Description
-DomainName
domain_name

the domain name with the -dn option or the environment
variable INFA_DEFAULT_DOMAIN. If you set a domain
name with both methods, the -dn option takes
precedence.
service_name
Required. Name of the Data Integration Service that the

application is deployed to.
-dn
-ServiceName
-sn
108
Chapter 10: infacmd dis Command Reference
Option
Argument
Description
-UserName
user_name

authentication. User name to connect to the domain. You
can set the user name with the -un option or the
environment variable INFA_DEFAULT_DOMAIN_USER. If
you set a user name with both methods, the -un option
takes precedence.
-un
Optional if the domain uses Kerberos authentication. To

run the command with single sign-on, do not set the user
name. If you set the user name, the command runs
without single sign-on.
-Password
password
Required if you specify the user name. Password for the

user name. The password is case sensitive. You can set a
password with both methods, the password set with the pd option takes precedence.
security_domain

Kerberos authentication. Name of the security domain to
domain with the -sdn option or the environment variable
security domain name with both methods, the -sdn option
takes precedence. The security domain name is case
sensitive.
-pd
-SecurityDomain
-sdn

installation.
-ResilienceTimeout
-re
conds

domain. You can set the resilience timeout period with the
-re option or the environment variable
takes precedence.
-Application
application
Required. Name of the application that contains the

parameter set.
parameterset name
Required. Parameter set name.
-a
parametersetname
- ps
109
Option
Argument
Description
-projectScope
project scope
Required. Path to the mapping or workflow that contains

the parameters. For a mapping, M1, in project P1 and
folder F1, the path is P1/F1/mapping/M1.
parameter names
Required. Parameter name-value pairs separated by

space. Enclose name-value pairs in double quotes.
Enclose each value in single quotes. Use the following
syntax:
"parm1='valueA'" "parm2='valueB'"
"parm3='valueC" . You can include spaces in a
parameter value. You can include an apostrophe (') or a
colon (:) in the value if you escape the character with a
backslash (\). 'C:\directory'
-prs
-paramNames
-pnv
BackupApplication
Backs up a deployed application from a Data Integration Service to an XML file.
The backup file contains all the properties settings for the application. You can restore the application to
another Data Integration Service. You must stop the application before you back it up.
The infacmd dis BackupApplication command uses the following syntax:
BackupApplication
<-FileName|-f> file_name
The following table describes infacmd dis BackupApplication options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

-dn
-ServiceName
-sn
110
Option
Argument
Description
-UserName
user_name

-un

-Password
password
precedence.
security_domain

-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
timeout_period_in_s
econds

environment variable INFA_CLIENT_RESILIENCE_TIMEOUT. If
you set the resilience timeout period with both methods, the -re
-Application
application
Required. Name of the application to back up.
file_name
Required. Name and file path of the application backup file.
-a
Filename
-f
CancelDataObjectCacheRefresh
Stops the last request to refresh the logical data object cache. If the cache mapping is running, the command
stops the current request to refresh the logical data object cache. Future periodic requests to refresh the
logical data object cache are not affected.
The infacmd dis CancelDataObjectCacheRefresh command uses the following syntax:
111
<-Folder|-f> folder
<-DataObject|-do> data_model.data_object
The following table describes infacmd dis CancelDataObjectCacheRefresh options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password
-pd
112

Option
Argument
Description
-SecurityDomain
security_domain

case sensitive.
-sdn

-ResilienceTimeout
-re
ds

-ServiceName
service_name
Required. Name of the Data Integration Service.
application
Required. Name of the application.
folder
Folder in the application that contains the data object.
data_model.data_object
Required. Name of the logical data object. The name

must be in the following syntax:
-sn
Application
-a
-Folder
-f
-DataObject
-do
<data_model>.<data_object>
CreateService
Creates a Data Integration Service. By default, the Data Integration Service is enabled when you create it.
The infacmd dis CreateService command uses the following syntax:
CreateService
CreateService
113
<-NodeName|-nn> node_name | <-GridName|-gn> grid_name
[<-BackupNodes|-bn> node_name1,node_name2,...]
<-RepositoryService|-rs> model_repository_service_name
<-RepositoryUserName|-rsun> model_repository_user_name
<-RepositoryPassword|-rspd> model_repository_password
[<-RepositorySecurityDomain|-rssdn> model_repository_security_domain]
[<-httpProtocolType|-pt> http_protocol_type]
The following table describes infacmd dis CreateService options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
-dn
-ServiceName
-sn
The name is not case sensitive and must be unique within

the domain. The characters must be compatible with the
code page of the associated repository. The name cannot
exceed 230 characters, have leading or trailing spaces, or
contain carriage returns, tabs, or the following characters:
/ * ? < > " |
-UserName
user_name
-un

sign-on.
-Password
password
-pd
114
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-ResilienceTimeout
-re
timeout_period_i
n_seconds

takes precedence.
-NodeName
node_name
Required if you do not specify grid name. Node where the

Data Integration Service runs. You can run the Data
Integration Service on a node or grid.
grid_name
Required if you do not specify node name. Grid where the

Data Integration Service runs. You can run the Data
Integration Service on a node or grid.
node_name1,nod
e_name2,...
Optional. Nodes on which the service can run if the primary

node is unavailable. You can configure backup nodes if you
have high availability.
model_repository
_service_name
Model Repository Service that stores run-time metadata

required to run the mappings and SQL data services.
model_repository
_user_name
User name to access the Model Repository Service.
model_repository
_password
User password to access the Model Repository Service.
-rssdn
model_repository
_security_domai
n

security domain that the Model repository user belongs to.
-HttpPort
http_port
Required if you do not specify an HTTPS port. Unique HTTP

port number used for each Data Integration Service process.
After you create the service, you can define different port
numbers for each Data Integration Service process.
-nn
-GridName
-gn
-BackupNodes
-bn
-RepositoryService
-rs
-RepositoryUserName
-rsun
-RepositoryPassword
-rspd
-RepositorySecurityDomain
Default is 8095.
CreateService
115
Option
Argument
Description
-HttpsPort
https_port
Required if you do not specify an HTTP port. Unique HTTPS

port number used for each Data Integration Service process.
After you create the service, you can define different port
numbers for each Data Integration Service process.
-KeystoreFile
keystore_file_loc
ation
Path and file name of the keystore file that contains the keys
and certificates required if you use the HTTPS protocol for
the Data Integration Service. 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 in a
keystore file. You can use the self-signed certificate or use a
certificate signed by a certificate authority.
-kf
If you run the Data Integration Service on a grid, the keystore

file on each node in the grid must contain the same keys.
-KeystorePassword
-kp
-httpProtocolType
-pt
keystore_passwo
rd
Password for the keystore file.
http_protocol_typ
e
Security protocol that the Data Integration Service uses.

Enter one of the following values:
- HTTP. Requests to the service must use an HTTP URL.
- HTTPS. Requests to the service must use an HTTPS URL.
- Both. Requests to the service can use either an HTTP or an
HTTPS URL.
When you set the HTTP protocol type to HTTPS or Both, you
enable Transport Layer Security (TLS) for the service.
You can also enable TLS for each web service deployed to
an application. When you enable HTTPS for the Data
Integration Service and enable TLS for the web service, the
web service uses an HTTPS URL. When you enable HTTPS
for the Data Integration Service and do not enable TLS for
the web service, the web service can use an HTTP URL or
an HTTPS URL. If you enable TLS for a web service and do
not enable HTTPS for the Data Integration Service, the web
service does not start.
Default is HTTP.
DeleteParameterSetEntries
Deletes entries from a parameter set. Run this command to delete parameter set entries for a mapping or
workflow that has been deployed as an application. You can delete specific parameter set entries or you can
delete all of the parameter set entries.
If any parameter that you want to delete does not exist in the parameter set, the infacmd returns a warning
message. The message indicates the parameter is not deleted because it is not in the parameter set.
The infacmd dis DeleteParameterSetEntries command uses the following syntax:
116
<-projectScope|-prs> path to the mapping or workflow that contains the parameters
<-paramNames|-pnv> parameter names to delete, separated by spaces. For a mapping, M1,
in project P1 and folder F1, the path is P1/F1/mapping/M1.
<-all|> Delete all the parameters in the project scope.
The following table describes infacmd dis DeleteParameterSetEntries options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
service_name

user_name

takes precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
-pd
password

117
Option
Argument
Description
-SecurityDomain
security_domain

sensitive.
-sdn

installation.
-ResilienceTimeout
-re
conds

takes precedence.
-Application
application

parameter set.
parameterset name
project scope

parameter names
Required. Parameter set entry names to delete, separated

by spaces. To delete all the parameters, use the -all
option instead of this option.
all
Delete all of the parameters in the parameter set.
-a
parametersetname
- ps
-projectScope
-prs
-paramNames
-pnv
-all
DeployApplication
Deploys an application to a Data Integration Service.
The infacmd dis DeployApplication command uses the following syntax:
DeployApplication
118
The following table describes infacmd dis DeployApplication options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
service_name

user_name

takes precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
DeployApplication
119
Option
Argument
Description
-ResilienceTimeout
-re
conds

takes precedence.
Filename
file_name
Required. Name of the application file.
application
Required. Name of the application to deploy. If there is a

name conflict, the deploy fails.
-f
-Application
-a
ListApplications
Lists the applications that are deployed to a Data Integration Service.
The infacmd dis ListApplications command uses the following syntax:
ListApplications
120
The following table describes infacmd dis ListApplications options and arguments:
Option
Argument
Description
-DomainName
domain_name

takes precedence.
user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

-pd
-SecurityDomain
-sdn

installation.
-ResilienceTimeout
-re
nds

-ServiceName
service_name
Required. Name of the Data Integration Service for

which to list applications.
-sn
ListApplications
121
ListApplicationObjects
Lists the objects that an application contains.
When you use the -ListObjectTypes option, the command also lists the type of each object.
The infacmd dis ListApplicationObjects command uses the following syntax:
<-ServiceName|-sn> Data_Integration_Service_name
[<-ObjectType|-t> object_type]
[<-ListObjectType|-lt> list_object_type]
[<-PageSize|-ps> page_size]
[<-PageIndex|-pi> page_index]
The following table describes infacmd dis ListApplicationObjects options and arguments:
Option
Argument
Description
-DomainName
domain_name

Data_Integration_Service
_name
-sn
-UserName
user_name

precedence.
-dn
-ServiceName
-un

-Password
password
-pd
122

Option
Argument
Description
-SecurityDomain
security_domain

case sensitive.
-sdn

-ResilienceTimeout
-re
ds

-Application
application
-a
-ObjectType
object_type
-t
-ListObjectType
true | false
page_size
Optional. The number of results to display in each

group, or page. When you specify a page size, you
organize command results in groups. For example, if
you specify -PageSize 5, then the command
returns results in groups of five or fewer.
page_index
Optional. Starting with 0, the page of results to

display. For example, if you specify -PageSize 5 PageIndex 0, then the command returns the first
page of five results, results 1 through 5.
-ps
-PageIndex
-pi
Optional. Enter one of the following values:

- true
- false
-lt
-PageSize
Optional. Type of object you want to list.

You can use this option to filter the results by object
type.
If you omit PageIndex, the command returns the first

PageSize of results.
Default is 0.
123
ListApplicationOptions
Lists the properties for an application.
The infacmd dis ListApplicationOptions command uses the following syntax:
ListApplicationOptions
The following table describes infacmd dis ListApplicationOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
Required. Name of the Data Integration Service that

the application is deployed to.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password
-pd
124

Option
Argument
Description
-SecurityDomain
security_domain

case sensitive.
-sdn

-ResilienceTimeout
-re
ds

-Application
application
-a
ListComputeOptions
List Data Integration Service properties for a node with the compute role.
The infacmd dis ListComputeOptions command uses the following syntax:
ListComputeOptions
ListComputeOptions
125
The following table describes infacmd dis ListComputeOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

126
Option
Argument
Description
-ResilienceTimeout
-re
ds

NodeName
node_name
Required. Node with the compute role that is assigned

to the Data Integration Service or to the Data
Integration Service grid.
-nn
ListDataObjectOptions
Lists properties of a data object.
The infacmd dis ListDataObjectOptions command uses the following syntax:
<-Folder|-f> folder
The following table describes infacmd dis ListDataObjectOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
-dn
-ServiceName
-sn
127
Option
Argument
Description
-UserName
user_name

precedence.
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
ds

-Application
application
folder
Required. Repository folder that contains the data

object.
Required. Data object name.
-a
-Folder
-f
DataObject
-do
128
ListParameterSetEntries
Lists the entries in a parameter set.
The infacmd dis ListParameterSetEntries command uses the following syntax:
The following table describes infacmd dis ListParameterSetEntries options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
service_name

user_name

takes precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
-pd
password

129
Option
Argument
Description
-SecurityDomain
security_domain

sensitive.
-sdn

installation.
-ResilienceTimeout
-re
conds

takes precedence.
-Application
application

parameter set.
parameterset name
project scope

-a
parametersetname
- ps
-projectScope
-prs
ListParameterSetObjects
List the objects in a specific parameter set.
The infacmd dis ListParameterSetObjects command uses the following syntax:
<-Password|-ps> parameter set
130
<-Application|-a> application that contains the parameter set

The following table describes infacmd dis ListParameterSetObjects options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
service_name

user_name

takes precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-ResilienceTimeout
-re
conds

takes precedence.
131
Option
Argument
Description
-parameterset
parameter set
Required. The name of the parameter set that you want to

view.
application

parameter set.
-ps
-Application
-a
ListParameterSets
List the parameter sets in an application.
The infacmd dis ListParameterSets command uses the following syntax:
ListParameterSets
The following table describes infacmd dis ListParameterSets options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
service_name

user_name

takes precedence.
-dn
-ServiceName
-sn
-UserName
-un

132
Option
Argument
Description
-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-ResilienceTimeout
-re
conds

takes precedence.
-Application
application

parameter sets.
-a
ListSequenceObjectProperties
Lists the properties for a sequence data object.
The infacmd dis listsequenceobjectproperties command uses the following syntax:
<-SequenceObjectPath|-sop> sequence_object_path
133
The following table describes infacmd dis ListSequenceObjectProperties options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
Required. Name of the Integration Service.
-dn
-ServiceName
-sn
-UserName

the following characters: / * ? < > " |
user_name
-un

precedence.
-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

134
Option
Argument
Description
-ResilienceTimeout
-re
ds

-Application
application
sequence object path
Required. Path to the sequence data object. The path

must include the following objects, in order, and where
applicable:
-a
-SequenceObjectPath
-sop
Project
Folders
SQL data service or web service
Mapping
Sequence Generator transformation
Sequence data object
If the sequence data object is in a mapping, SQL data

service, or web service, you must use a prefix before
the mapping name, SQL data service name, or web
service name. Use the following prefixes with options
in the command:
- Mapping:<mapping name>
- SQLDS:<SQL data service name>
- WS:<web service name>
Separate the options with a slash (/). For example:

<project name>/<folder>/SQLDS:<SQL
Data Service Name>/Mapping:<virtual
table mapping>/<Sequence Generator
transformation>/<sequence data object
name>
.
ListSequenceObjects
Lists the sequence data objects deployed to an application.
The infacmd dis ListSequenceObjects command uses the following syntax:
ListSequenceObjects
ListSequenceObjects
135
The following table describes infacmd dis ListSequenceObjects options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
-dn
-ServiceName
-sn
-UserName

user_name
-un

precedence.
-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

136
Option
Argument
Description
-ResilienceTimeout
-re
ds

-Application
application
-a
.
ListServiceOptions
Lists the properties for a Data Integration Service.
The infacmd dis ListServiceOptions command uses the following syntax:
ListServiceOptions
The following table describes infacmd dis ListServiceOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
-dn
-ServiceName
-sn
ListServiceOptions
137
Option
Argument
Description
-UserName
user_name

precedence.
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
ds

Lists the properties of a Data Integration Service process.
The infacmd dis ListServiceProcessOptions command uses the following syntax:
138
The following table describes infacmd dis ListServiceProcessOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
-pd
password

139
Option
Argument
Description
-SecurityDomain
security_domain

case sensitive.
-sdn

-ResilienceTimeout
-re
ds

-NodeName
node_name
Required. Name of node where the service process

runs.
-nn
.
PurgeDataObjectCache
Purges the cache for a logical data object. If caching for logical data objects is enabled, this command
deletes all cache for a logical data object except the latest cache run. If the latest cache run is older than the
time set in the Cache Refresh Period property, the latest cache run is also deleted. If caching for logical data
objects is not enabled, this command deletes all cache for the logical data object.
You must disable the application for a logical data object before you purge the data object cache.
The infacmd dis PurgeDataObjectCache command uses the following syntax:
140
<-Folder|-f> folder
[<-PurgeAll|-pa> true|false]
The following table describes infacmd dis PurgeDataObjectCache options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

141
Option
Argument
Description
-ResilienceTimeout
-re
ds

-ServiceName
service_name

application
Name of the application that contains the data object.
folder
Name of the folder that contains the data object

model.
Name of the data object with the cache you need to

purge.
true | false
Optional. Deletes all cache for a logical data object.
-sn
Application
-a
Folder
-f
DataObject
-do
-PurgeAll
-pa
PurgeResultSetCache
Purges the result set caches for an application. You can purge the cache for an application when you do not
need the existing result set caches for the SQL data services and the web services in the application.
The infacmd dis PurgeResultSetCache command uses the following syntax:
PurgeResultSetCache
142
The following table describes infacmd dis PurgeResultSetCache options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
ds

-ServiceName
service_name

application
Name of the application that you want to purge the

result set cache for.
-sn
Application
-a
PurgeResultSetCache
143
RefreshDataObjectCache
Refreshes a data object cache.
The infacmd dis RefreshDataObjectCache command uses the following syntax:
RefreshDataObjectCache
<-Folder|-f> folder
The following table describes infacmd dis RefreshDataObjectCache options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password
-pd
144

Option
Argument
Description
-SecurityDomain
security_domain

case sensitive.
-sdn

-ResilienceTimeout
-re
ds

-ServiceName
service_name

you want to list the applications for.
application

data object.
folder
Required. Name of the folder that contains the data

object.
Required. Name of the data object that has cache to

refresh.
-sn
-Application
-a
-Folder
-f
-DataObject
-do
RenameApplication
Renames a deployed application. Before you rename an application, run infacmd dis StopApplication to stop
it.
The infacmd dis RenameApplication command uses the following syntax:
RenameApplication
<-SecurityDomain|-sdn> security_domain]
RenameApplication
145
<-NewName|-n> new_name
The following table describes infacmd dis RenameApplication options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

146
Option
Argument
Description
-ResilienceTimeout
-re
ds

-ServiceName
service_name
Required. Name of the Data Integration Service where

the application is deployed.
application
Required. Current application name.
new_name
Required. New name for the application.
-sn
-Application
-a
-NewName
-n
RestoreApplication
Restores an application from a backup file. When you deploy a restored application, the application state
depends on the default deployment mode. The application properties are retained in the restored application.
The infacmd dis RestoreApplication command uses the following syntax:
RestoreApplication
[<-Application|-a> application]
RestoreApplication
147
The following table describes infacmd dis RestoreApplication options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
Required. Name of the Data Integration Service to

restore the application to.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
148
ds

Option
Argument
Description
-FileName
file_name
Required. Name of the application backup file.
application
Optional. Name of the application after after you

deploy it. If there is a name conflict, the deploy fails.
-f
-Application
-a
SetSequenceState
Updates the current value of a sequence data object.
The infacmd dis setsequencestate command uses the following syntax:
SetSequenceState
<-SequenceObjectPath|-sop> sequence_object_path
<-SequenceValue|-sv> sequence_value
The following table describes infacmd dis SetSequenceState options and arguments:
Option
Argument
Description
-DomainName
domain_name

-dn
-ServiceName
service_name
-sn
-UserName
-un

user_name

precedence.
SetSequenceState
149
Option
Argument
Description
-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
ds

-Application
application
-a
150
Option
Argument
Description
-SequenceObjectPath
sequence object path
Required. Path to the sequence data object. The path

must include the following objects, in order, and where
applicable:
-sop
Project
Folders
SQL data service or web service
Mapping
Sequence Generator transformation
Sequence data object
If the sequence data object is in a mapping, SQL data

service, or web service, you must use a prefix before
the mapping name, SQL data service name, or web
service name. Use the following prefixes with options
in the command:
- Mapping:<mapping name>
- SQLDS:<SQL data service name>
- WS:<web service name>
Separate the options with a slash (/). For example:

<project name>/<folder>/SQLDS:<SQL
Data Service Name>/Mapping:<virtual
table mapping>/<Sequence Generator
transformation>/<sequence data object
name>
-SequenceValue
sequence_value
-sv
Required. The new value for sequence data object.

Enter a value that is greater than or equal to the start
value of the sequence data object and less than or
equal to the end value.
StartApplication
Starts a deployed application. You must enable the application before you can start it. The Data Integration
Service must be running.
The infacmd dis StartApplication command uses the following syntax:
StartApplication
StartApplication
151
The following table describes infacmd dis StartApplication options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
ds

-Application
application
Required. Name of the application to start.
-a
152
StopApplication
Stops an application from running. You might stop an application if you need to back it up or if you want to
prevent users from accessing it.
The infacmd dis StopApplication command uses the following syntax:
StopApplication
The following table describes infacmd dis StopApplication options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
-pd
password

StopApplication
153
Option
Argument
Description
-SecurityDomain
security_domain

case sensitive.
-sdn

-ResilienceTimeout
-re
ds

-ServiceName
service_name

application
Required. Name of the application to stop.
-sn
-Application
-a
stopBlazeService
Stops the components of the Blaze engine from running. You might stop the Blaze engine components from
running if you want to perform maintenance on the Hadoop cluster such as cleaning up resources or applying
software patches.
The infacmd dis stopBlazeService command uses the following syntax:
stopBlazeService
154
The following table describes infacmd dis stopBlazeService options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
ds

stopBlazeService
155
UndeployApplication
Removes an application from a Data Integration Service.
The infacmd dis UndeployApplication command uses the following syntax:
UndeployApplication
The following table describes infacmd dis UndeployApplication options and arguments:
Option
Argument
Description
-DomainName
domain_name

the domain name with the -un option or the environment
name with both methods, the -dn option takes precedence.
user_name

takes precedence.
-dn
-UserName
-un

name. If you set the user name, the command runs without
single sign-on.
-Password
password
-pd
156

Option
Argument
Description
-SecurityDomain
security_domain
Required if the domain uses LDAP authentication. Optional

if the domain uses native authentication or Kerberos
domain user belongs. You can set a security domain with
the -sdn option or the environment variable
sensitive.
-sdn

installation.
-ResilienceTimeout
-re
onds
Optional. Amount of time in seconds that infacmd attempts

to establish or re-establish a connection to the domain.
You can set the resilience timeout period with the -re
option or the environment variable
takes precedence.
-ServiceName
service_name
Required. Name of the Data Integration Service to remove

the application from.
application
Required. Name of the application to remove from the Data

Integration Service.
-sn
-Application
-a
UpdateApplication
Updates an application from an application file and maintains the configuration. The application must be
deployed to a Data Integration Service. End users can access the latest version of the application.
The infacmd dis UpdateApplication command uses the following syntax:
UpdateApplication
UpdateApplication
157
The following table describes infacmd dis UpdateApplication options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
158
ds

Option
Argument
Description
-FileName
file_name
Required. Name and path of the application file to

update the deployed application with.
application
Optional. Name of the deployed application.
-f
-Application
-a
UpdateApplicationOptions
Updates application properties.
Separate each option and value with a space. To view current properties, run infacmd dis
ListApplicationOptions.
The infacmd dis UpdateApplicationOptions command uses the following syntax:
The following table describes infacmd dis UpdateApplicationOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

-dn
-ServiceName
-sn
159
Option
Argument
Description
-UserName
user_name

precedence.
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
ds

-Application
application
Required. Name of the application to update.
options

options, run the infacmd dis ListApplicationOptions
command.
-a
-Options
-o
160
UpdateComputeOptions
Updates Data Integration Service properties for a node with the compute role. Use the command to override
Data Integration Service properties for a specific compute node.
Enter options in the following format:
The infacmd dis UpdateComputeOptions command uses the following syntax:
The following table describes infacmd dis UpdateComputeOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

161
Option
Argument
Description
-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
ds

NodeName
node_name
Required. Node with the compute role that is assigned

to the Data Integration Service or to the Data
Integration Service grid.
options
Required. Enter each option separated by a space. To

view the options, run the infacmd dis
ListComputeOptions command.
-nn
-Options
-o
You can update the following Data Integration Service

options:
-
162
ExecutionOptions.TemporaryDirectories
ExecutionOptions.DISHomeDirectory
ExecutionOptions.CacheDirectory
ExecutionOptions.SourceDirectory
ExecutionOptions.TargetDirectory
ExecutionOptions.RejectFilesDirectory
UpdateDataObjectOptions
Updates data object properties. To view the current options, run the infacmd dis ListDataObjectOptions
command.
The infacmd dis UpdateDataObjectOptions command uses the following syntax:
<-Folder|-f> folder
The following table describes infacmd dis UpdateDataObjectOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

163
Option
Argument
Description
-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
ds

-Application
application
Required. Application that contains the data object.
Folder
Required. Name of the folder that contains the data

object model.
Required. Name of the data object that you want to

update.
options
Required. Enter options and values separated by

spaces. To view the current options, run the infacmd
dis ListDataObjectOptions command.
-a
-Folder
-f
-DataObject
-do
-Options
-o
Data Object Options

Use the data object options to configure caching for a logical data object. Use the data object options with the
infacmd dis UpdateDataObjectOptions command.
Enter data object options in the following format:
... -o option_type.option_name=value ...
To enter multiple options, separate them with a space. To enter a value that contains a space or other nonalphanumeric character, enclose the value in quotation marks.
164
The following table describes data object options:

Option
Description
DataObjectOptions.CachingEnabled
Cache the logical data object in the data object cache database. True
or false. Default is true.
DataObjectOptions.CacheRefreshPeriod
Number of minutes between cache refreshes. Default is zero.
DataObjectOptions.CacheTableName
The name of the user-managed table from which the Data Integration
Service accesses the logical data object cache. A user-managed
cache table is a table in the data object cache database that you
create, populate, and manually refresh when needed.
If you specify a cache table name, the Data Object Cache Manager
does not manage the cache for the object and ignores the cache
refresh period. If you do not specify a cache table name, the Data
Object Cache Manager manages the cache for the object.
UpdateParameterSetEntries
Updates entries from a parameter set. Run this command to update the values in parameter set entries for a
mapping or workflow in an application.
The infacmd dis UpdateParameterSetEntries command uses the following syntax:
<-paramNames|-pnv> parameter name-value pairs, separated by double quotes
165
The following table describes infacmd dis UpdateParameterSetEntries options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
service_name

user_name

takes precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-ResilienceTimeout
-re
conds

takes precedence.
-Application
application

parameter set.
-a
166
Option
Argument
Description
parametersetname
parameterset name
project scope

parameter names
Required.Required. Parameter name-value pairs

separated by space. Enclose name-value pairs in double
quotes. Enclose each value in single quotes. Use the
following syntax: "parm1='valueA'"
"parm2='valueB'" "parm3='valueC'" . You can
include spaces in a parameter value. You can include an
apostrophe (') or a colon (:) in the value if you escape the
character with a backslash (\). 'C:\directory'
- ps
-projectScope
-prs
-paramNames
-pnv
Updates Data Integration Service properties. To view current properties run the infacmd dis
ListServiceOptions command.
You can change the properties while the service is running, but you must recycle the service for the changed
properties to take effect.
The infacmd dis UpdateServiceOptions command uses the following syntax:
[<-Options|-o> options]
[<-NodeName|-nn> node_name | <-GridName|-gn> grid_name]
167
The following table describes infacmd dis UpdateServiceOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
168
ds

Option
Argument
Description
-Options
options
Optional. Enter each option separated by a space. To

view options, run the infacmd dis ListServiceOptions
command.
-NodeName
node_name
-nn
grid_name
Optional. Enter the node or grid where the Data

Integration Service will run. The Data Integration
Service can run on a node or grid.
-o
-GridName
-gn
-BackupNodes
-bn
node_name1,node_name
2,...
Optional. Nodes on which the service can run if the

primary node is unavailable. You can configure
backup nodes if you have high availability.
Data Integration Service Options

Use the Data Integration Service options with the infacmd dis UpdateServiceOptions command.
Enter Data Integration Service options in the following format:
... -o option_type.option_name=value
The following table describes Data Integration Service options:
Option
Description
LoggingOptions.LogLevel
Level of error messages that the Data Integration Service writes to

the Service log. Choose one of the following message levels: Fatal,
Error, Warning, Info, Trace, or Debug.
ExecutionOptions.OutOfProcessExecution
Runs jobs in the Data Integration Service process, in separate DTM

processes on the local node, or in separate DTM processes on
remote nodes. Configure the property based on whether the Data
Integration Service runs on a single node or a grid and based on the
types of jobs that the service runs.
- IN_PROCESS. Runs jobs in the Data Integration Service process.
Configure when you run SQL data service and web service jobs on a
single node or on a grid where each node has both the service and
compute roles.
- OUT_OF_PROCESS. Runs jobs in separate DTM processes on the
local node. Configure when you run mapping, profile, and workflow
jobs on a single node or on a grid where each node has both the
service and compute roles.
- OUT_OF_PROCESS_REMOTE. Runs jobs in separate DTM processes
on remote nodes. Configure when you run mapping, profile, and
workflow jobs on a grid where nodes can have a different combination
of roles. If you configure this option when the Data Integration Service
runs on a single node, then the service runs jobs in separate local
processes.
Default is OUT_OF_PROCESS.
169
Option
Description
ExecutionOptions.MaxExecutionPoolSize
Maximum number of jobs that each Data Integration Service process

can run concurrently. Jobs include data previews, mappings, profiling
jobs, SQL queries, and web service requests. For example, a Data
Integration Service grid includes three running service processes. If
you set the value to 10, each Data Integration Service process can
run up to 10 jobs concurrently. A total of 30 jobs can run concurrently
on the grid. Default is 10.
ExecutionOptions.MaxMemorySize
Maximum amount of memory, in bytes, that the Data Integration

Service can allocate for running all requests concurrently when the
service runs jobs in the Data Integration Service process. When the
Data Integration Service runs jobs in separate local or remote
processes, the service ignores this value. If you do not want to limit
the amount of memory the Data Integration Service can allocate, set
this property to 0.
If the value is greater than 0, the Data Integration Service uses the
property to calculate the maximum total memory allowed for running
all requests concurrently. The Data Integration Service calculates the
maximum total memory as follows:
Maximum Memory Size + Maximum Heap Size + memory required for
loading program components
Default is 0.
Note: If you run profiles or data quality mappings, set this property to
0.
ExecutionOptions.MaxMappingParallelism
Maximum number of parallel threads that process a single mapping

pipeline stage.
When you set the value greater than one, the Data Integration
Service enables partitioning for mappings and for mappings
converted from profiles. The service dynamically scales the number
of partitions for a mapping pipeline at run time. Increase the value
based on the number of CPUs available on the nodes where
mappings run.
In the Developer tool, developers can change the maximum
parallelism value for each mapping. When maximum parallelism is set
for both the Data Integration Service and the mapping, the Data
Integration Service uses the minimum value when it runs the
mapping.
Default is 1. Maximum is 64.
ExecutionOptions.DisHadoopPrincipal
Service Principal Name (SPN) of the Data Integration Service to

connect to a Hadoop cluster that uses Kerberos authentication.
ExecutionOptions.DisHadoopKeytab
The file path to the Kerberos keytab file on the machine on which the
Data Integration Service runs.
ExecutionOptions.TemporaryDirectories
Directory for temporary files created when jobs are run. Default is
<home directory>/disTemp.
Enter a list of directories separated by semicolons to optimize
performance during profile operations and during cache partitioning
for Sorter transformations.
You cannot use the following characters in the directory path:
* ? < > " | , [ ]
170
Option
Description
ExecutionOptions.DISHomeDirectory
Root directory accessible by the node. This is the root directory for
other service directories. Default is <Informatica
installation directory>/tomcat/bin. If you change the
default value, verify that the directory exists.
* ? < > " | ,
ExecutionOptions.CacheDirectory
Directory for index and data cache files for transformations. Default is
<home directory>/cache.
Enter a list of directories separated by semicolons to increase
performance during cache partitioning for Aggregator, Joiner, or Rank
transformations.
* ? < > " | ,
ExecutionOptions.SourceDirectory
Directory for source flat files used in a mapping. Default is <home

directory>/source.
If the Data Integration Service runs on a grid, you can use a shared
directory to create one directory for source files. If you configure a
different directory for each node with the compute role, ensure that
the source files are consistent among all source directories.
* ? < > " | ,
ExecutionOptions.TargetDirectory
Default directory for target flat files used in a mapping. Default is

<home directory>/target.
Enter a list of directories separated by semicolons to increase
performance when multiple partitions write to the flat file target.
If the Data Integration Service runs on a grid, you can use a shared
directory to create one directory for target files. If you configure a
different directory for each node with the compute role, ensure that
the target files are consistent among all target directories.
* ? < > " | ,
ExecutionOptions.RejectFilesDirectory
Directory for reject files. Reject files contain rows that were rejected
when running a mapping. Default is <home directory>/reject.
* ? < > " | ,
ExecutionOptions.HadoopInfaHomeDir
The PowerCenter Big Data Edition home directory on every data

node created by the Hadoop RPM install. Type /
<PowerCenterBigDataEditionInstallationDirectory>/
Informatica.
171
Option
Description
ExecutionOptions.HadoopDistributionDir
The directory containing a collection of Hive and Hadoop JARS on

the cluster from the RPM Install locations. The directory contains the
minimum set of JARS required to process Informatica mappings in a
Hadoop environment. Type /
<PowerCenterBigDataEditionInstallationDirectory>/
Informatica/services/shared/hadoop/
[Hadoop_distribution_name].
ExecutionOptions.DisHadoopDistributionDir
The Hadoop distribution directory on the Data Integration Service

node. The contents of the Data Integration Service Hadoop
distribution directory must be identical to Hadoop distribution
directory on the data nodes. Type <Informatica
Installation directory/Informatica/services/
shared/hadoop/[Hadoop_distribution_name].
RepositoryOptions.RepositoryServiceName
Service that stores run-time metadata required to run mappings and

SQL data services.
RepositoryOptions.RepositoryUserName
User name to access the Model repository. The user must have the
Create Project privilege for the Model Repository Service.
RepositoryOptions.RepositoryPassword
User password to access the Model repository.
RepositoryOptions.RepositorySecurityDomain
LDAP security domain name if you are using LDAP. If you are not
using LDAP the default domain is native.
DataObjectCacheOptions.CacheRemovalTime
The number of milliseconds the Data Integration Service waits before

cleaning up cache storage after a refresh. Default is 3,600,000.
DataObjectCacheOptions.CacheConnection
The database connection name for the database that stores the data
object cache. Enter a valid connection object name.
DataObjectCacheOptions.MaxConcurrentRefreshRequests
Maximum number of cache refreshes that can occur at the same

time.
DataObjectCacheOptions.EnableNestedLDOCache
Indicates that the Data Integration Service can use cache data for a
logical data object used as a source or a lookup in another logical
data object during a cache refresh. If false, the Data Integration
Service accesses the source resources even if you enabled caching
for the logical data object used as a source or a lookup.
For example, logical data object LDO3 joins data from logical data
objects LDO1 and LDO2. A developer creates a mapping that uses
LDO3 as the input and includes the mapping in an application. You
enable caching for LDO1, LDO2, and LDO3. If you enable nested
logical data object caching, the Data Integration Service uses cache
data for LDO1 and LDO2 when it refreshes the cache table for LDO3.
If you do not enable nested logical data object caching, the Data
Integration Service accesses the source resources for LDO1 and
LDO2 when it refreshes the cache table for LDO3.
Default is false.
172
Option
Description
DeploymentOptions.DefaultDeploymentMode
Determines whether to enable and start each application after you

deploy it to a Data Integration Service.
- EnableandStart. Enable the application and start the application.
- EnableOnly. Enable the application but do not start the application.
- Disable. Do not enable the application.
PassThroughSecurityOptions.AllowCaching
Allows data object caching for all pass-through connections in the

Data Integration Service. Populates data object cache using the
credentials in the connection object.
Note: When you enable data object caching with pass-through
security, you might allow unauthorized access to some data.
HttpProxyServerOptions.HttpProxyServerHost
Name of the HTTP proxy server.
HttpProxyServerOptions.HttpProxyServerPort
Port number of the HTTP proxy server.

Default is 8080.
HttpProxyServerOptions.HttpServerUser
Authenticated user name for the HTTP proxy server. This is required
if the proxy server requires authentication.
HttpProxyServerOptions.HttpProxyServerPassword
Password for the authenticated user. The Service Manager encrypts

the password. This is required if the proxy server requires
authentication.
HttpProxyServerOptions.HttpProxyServerDomain
Domain for authentication.
HttpConfigurationOptions.AllowedIPAddresses
List of constants or Java regular expression patterns compared to the

IP address of the requesting machine. Use a space to separate
multiple constants or expressions.
If you configure this property, the Data Integration Service accepts
requests from IP addresses that match the allowed address pattern. If
you do not configure this property, the Data Integration Service uses
the Denied IP Addresses property to determine which clients can
send requests.
HttpConfigurationOptions.AllowedHostNames

host name of the requesting machine. The host names are case
sensitive. Use a space to separate multiple constants or expressions.
requests from host names that match the allowed host name pattern.
If you do not configure this property, the Data Integration Service
uses the Denied Host Names property to determine which clients can
send requests.
HttpConfigurationOptions.DeniedIPAddresses

IP address of the requesting machine. Use a space to separate
multiple constants or expressions.
requests from IP addresses that do not match the denied IP address
pattern. If you do not configure this property, the Data Integration
Service uses the Allowed IP Addresses property to determine which
clients can send requests.
173
Option
Description
HttpConfigurationOptions.DeniedHostNames

host name of the requesting machine. The host names are case
sensitive. Use a space to separate multiple constants or expressions.
requests from host names that do not match the denied host name
pattern. If you do not configure this property, the Data Integration
Service uses the Allowed Host Names property to determine which
clients can send requests.
HttpConfigurationOptions.HTTPProtocolType
Security protocol that the Data Integration Service uses. Enter one of
the following values:
- HTTP. Requests to the service must use an HTTP URL.
- HTTPS. Requests to the service must use an HTTPS URL.
- Both. Requests to the service can use either an HTTP or an HTTPS
URL.
When you set the HTTP protocol type to HTTPS or Both, you enable
Transport Layer Security (TLS) for the service.
You can also enable TLS for each web service deployed to an
application. When you enable HTTPS for the Data Integration Service
and enable TLS for the web service, the web service uses an HTTPS
URL. When you enable HTTPS for the Data Integration Service and
do not enable TLS for the web service, the web service can use an
HTTP URL or an HTTPS URL. If you enable TLS for a web service
and do not enable HTTPS for the Data Integration Service, the web
service does not start.
Default is HTTP.
ResultSetCacheOptions.FileNamePrefix
The prefix for the names of all result set cache files stored on disk.
Default is RSCACHE.
ResultSetCacheOptions.EnableEncryption
Indicates whether result set cache files are encrypted using 128-bit
AES encryption. Valid values are true or false. Default is true.
MappingServiceOptions.MaxNotificationThreadPoolSize
Allocates the number of threads that send notifications to the client.
MappingServiceOptions.MaxMemPerRequest
The behavior of Maximum Memory Per Request depends on the

following Data Integration Service configurations:
- The service runs jobs in separate local or remote processes, or the
service property Maximum Memory Size is 0 (default).
Maximum Memory Per Request is the maximum amount of memory, in
bytes, that the Data Integration Service can allocate to all
transformations that use auto cache mode in a single request. The
service allocates memory separately to transformations that have a
specific cache size. The total memory used by the request can exceed
the value of Maximum Memory Per Request.
- The service runs jobs in the Data Integration Service process, and the
service property Maximum Memory Size is greater than 0.
bytes, that the Data Integration Service can allocate to a single
request. The total memory used by the request cannot exceed the
value of Maximum Memory Per Request.
Default is 536,870,912.
ProfilingServiceOptions.ProfileWarehouseConnectionName
174
Connection object name for the connection to the profiling

warehouse.
Option
Description
ProfilingServiceOptions.MaxRanks
Number of minimum and maximum values to display for a profile.

Default is 5. Default is 10.
ProfilingServiceOptions.MaxPatterns
Maximum number of patterns to display for a profile.
ProfilingServiceOptions.MaxProfileExecutionPoolSize
Maximum number of threads to run profiling.
ProfilingServiceOptions.MaxExecutionConnections
Maximum number of database connections for each profiling job.
ProfilingServiceOptions.ExportPath
Location to export profile results. Enter the file system path. Default
is ./ProfileExport.
AdvancedProfilingServiceOptions.MinPatternFrequency
Minimum number of patterns to display for a profile.
AdvancedProfilingServiceOptions.MaxValueFrequencyPairs
Maximum number of value/frequency pairs to store in the profiling

warehouse. Default is 16,000.
AdvancedProfilingServiceOptions.MaxStringLength
Maximum length of a string that the profiling service can process.
AdvancedProfilingServiceOptions.MaxNumericPrecision
Maximum number of digits for a numeric value.
AdvancedProfilingServiceOptions.ExecutionPoolSize
Maximum number of threads to run mappings.
AdvancedProfilingServiceOptions.ColumnsPerMapping
Limits the number of columns that can be profiled in a single mapping

due to save memory and disk space. Default is 5. If you profile a
source with over 100 million rows decrease the value to as low as 1.
AdvancedProfilingServiceOptions.MaxParallelColumnBatches
Number of threads that can run mappings at the same time. Default is
1.
AdvancedProfilingServiceOptions.ValueFrequencyMemSize
Amount of memory to allow for value-frequency pairs. Default is 64

megabytes.
AdvancedProfilingServiceOptions.ReservedThreads
Number of threads of the Maximum Execution Pool Size that are for
priority requests. Default is 1.
AdvancedProfilingServiceOptions.MaxMemPerRequest
Maximum amount of memory, in bytes, that the Data Integration

Service can allocate for each mapping run for a single profile request.
Default is 536,870,912.
SQLServiceOptions.DTMKeepAliveTime
Number of milliseconds that the DTM process stays open after it

completes the last request. Identical SQL queries can reuse the open
process. 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. If the query fails, the DTM
process terminates. Must be greater than or equal to 0. 0 means that
the Data Integration Service does not keep the DTM process in
memory. Default is 0.
You can also set this property for each SQL data service that is
deployed to the Data Integration Service. If you set this property for a
deployed SQL data service, the value for the deployed SQL data
service overrides the value you set for the Data Integration Service.
SQLServiceOptions.TableStorageConnection
Relational database connection that stores temporary tables for SQL

data services. By default, no connection is selected.
175
Option
Description
SQLServiceOptions.SkipLogFiles
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. Default is false.
SQLServiceOptions.MaxMemPerRequest

Default is 50,000,000.
WorkflowOrchestrationServiceOptions.DBName
Connection name of the database that stores run-time metadata for

workflows.
WSServiceOptions.DTMKeepAliveTime
Number of milliseconds that the DTM process stays open after it

completes the last request. Web service requests that are issued
against the same operation can reuse the open process. 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. If the request fails, the DTM process terminates. Must
be greater than or equal to 0. 0 means that the Data Integration
Service does not keep the DTM process in memory. Default is 5000.
You can also set this property for each web service that is deployed
to the Data Integration Service. If you set this property for a deployed
web service, the value for the deployed web service overrides the
value you set for the Data Integration Service.
WSServiceOptions.WSDLLogicalURL
Prefix for the WSDL URL if you use an external HTTP load balancer.
For example,
http://loadbalancer:8080
The Data Integration Service requires an external HTTP load
balancer to run a web service on a grid. If you run the Data
Integration Service on a single node, you do not need to specify the
logical URL.
WSServiceOptions.SkipLogFiles
176
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. Default is false.
Option
Description
WSServiceOptions.MaxMemPerRequest

Default is 50,000,000.
Modules.MappingService
Enter false to disable the module that runs mappings and previews.
Default is true.
Modules.ProfilingService
Enter false to disable the module that runs profiles and generates
scorecards. Default is true.
Modules.SQLService
Enter false to disable the module that runs SQL queries against a
SQL data service. Default is true.
Modules.WebService
Enter false to disable the module that runs web service operation
mappings. Default is true.
Modules.WorkflowOrchestrationService
Enter false to disable the module that runs workflows. Default is true.
Updates properties for a Data Integration Service process. To view current properties, run the infacmd dis
The infacmd dis UpdateServiceProcessOptions command uses the following syntax:
177
The following table describes infacmd dis UpdateServiceProcessOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

178
Option
Argument
Description
-ResilienceTimeout
-re
ds

NodeName
node_name
Required. Node where the Data Integration Service

runs.
options

view the options, run the infacmd dis
-nn
-Options
-o
Data Integration Service Process Options

Use the Data Integration Service process options with the infacmd dis UpdateServiceProcessOptions
command.
Enter Data Integration Service process options in the following format:
The following table describes Data Integration Service process options:
Option
Description
GeneralOptions.JVMOptions
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.
GeneralOptions.HttpPort
Unique HTTP port number for the Data Integration Service

process when the service uses the HTTP protocol.
GeneralOptions.HttpsPort
Unique HTTPS port number for the Data Integration

Service process when the service uses the HTTPS
protocol.
LoggingOptions.LogDirectory
Directory for Data Integration Service node process logs.

Default is <INFA_HOME>\logs\dislogs.
If the Data Integration Service runs on a grid, use a shared
directory to create one directory for log files. Use a shared
directory to ensure that if the master service process fails
over to another node, the new master service process can
access previous log files.
ResultSetCacheOptions.MaxTotalDiskSize
Maximum number of bytes allowed for the total result set

cache file storage. Default is 0.
179
Option
Description
ResultSetCacheOptions.MaxPerCacheMemorySize
Maximum number of bytes allocated for a single result set

cache instance in memory. Default is 0.
ResultSetCacheOptions.MaxTotalMemorySize
Maximum number of bytes allocated for the total result set

cache storage in memory. Default is 0.
ResultSetCacheOptions.MaxNumCaches
Maximum number of result set cache instances allowed for

this Data Integration Service process. Default is 0.
HttpConfigurationOptions.MaxConcurrentRequests
Maximum number of HTTP or HTTPS connections that can

be made to this Data Integration Service process. Default is
200.
HttpConfigurationOptions.MaxBacklogRequests
Maximum number of HTTP or HTTPS connections that can

wait in a queue for this Data Integration Service process.
Default is 100.
HttpConfigurationOptions.KeyStoreFile
Path and file name of the keystore file that contains the
keys and certificates required if you use the HTTPS
protocol for the Data Integration Service. 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 in a keystore file. You can use the
self-signed certificate or use a certificate signed by a
certificate authority.
If you run the Data Integration Service on a grid, the
keystore file on each node in the grid must contain the
same keys.
HttpConfigurationOptions.KeyStorePassword
HttpConfigurationOptions.TrustStoreFile
Path and file name of the truststore file that contains

authentication certificates trusted by the Data Integration
Service.
If you run the Data Integration Service on a grid, the
truststore file on each node in the grid must contain the
same keys.
180
HttpConfigurationOptions.TrustStorePassword
Password for the truststore file.
HttpConfigurationOptions.SSLProtocol
Secure Sockets Layer protocol to use. Default is TLS.
SQLServiceOptions.MaxConcurrentConnections
Limits the number of database connections that the Data

Integration Service can make for SQL data services.
Default is 100.
CHAPTER 11
Infacmd es Command Reference

UpdateSMTPOptions, 184
ListServiceOptions
Returns a list of properties that are configured for the Email Service. To configure Email Service properties,
run infacmd es updateServiceOptions. To configure Email Service email server properties, run infacmd es
updateSMTPOptions.
The infacmd es listServiceOptions command uses the following syntax:
ListServiceOptions
[<-ServiceName|-sn> service_name]
181
Option
Argument
Description
-DomainName
domain_name

domain name with the -dn option or the environment
security_domain

-dn
-SecurityDomain
-sdn

created during installation. The name of the security domain
is the same as the user realm specified during installation.
-UserName
user_name
-un

sign-on.
-Password
password

service_name
Optional. Enter Email_Service.
timeout_period_in_seconds

to establish or re-establish a connection to the domain. If
you omit this option, infacmd uses the timeout value
specified in the INFA_CLIENT_RESILIENCE_TIMEOUT
environment variable. If no value is specified in the
environment variable, the default of 180 seconds is used.
-pd
-ServiceName
-sn
-ResilienceTimeout
-re
Updates Email Service properties. Run this command to configure domain properties and nodes for the Email
Service. To view current Email Service properties, run infacmd es listServiceOptions.
182
Chapter 11: Infacmd es Command Reference
The infacmd es updateServiceOptions command uses the following syntax:

[<-NodeName|nn> primary node name]
[<-BackupNodes|-bn> backup node names]
Option
Argument
Description
-DomainName
domain_name

security_domain

-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

sign-on.
-Password
password

service_name
-pd
-ServiceName
-sn
183
Option
Argument
Description
ResilienceTimeout

options
-re
-Options
-o
OptionGroupName.OptionName=OptionValue
OptionGroupName2.OptionName2=OptionValue2
To view valid options, run infacmd isp ListServiceOptions.
-NodeName
primary node name
Optional. Primary node on which the service runs.
backup node names

node is unavailable.
-nn
-BackupNodes
-bn
UpdateSMTPOptions
Updates the SMTP properties for the Email Service. Business glossaries and workflows use the Email
Service SMTP configuration to email notifications.
The following notifications use the Email Service SMTP configuration to send emails:
Business glossary notifications.
Workflow notifications. Workflow notifications include emails sent from Human tasks and Notification tasks
in workflows that the Data Integration Service runs.
The infacmd es updateSMTPOptions command uses the following syntax:

UpdateSMTPOptions
[<-SMTPServerHostName|-sa> smtp_host]
[<-SMTPUsername|-su> smtp_email_password]
[<-SMTPEmailPassword|-se> smtp_email_password]
[<-SMTPEmailAddress|-ss> smtp_email_address]
184
[<-SMTPPort|-sp> smtp_port]
[<-SMTPAuthEnabled|-sau> smtp_auth_enabled]
[<-SMTPTLSEnabled|-stls> smtp_tls_enabled]
[<-SMTPSSLEnabled|-sssl> smtp_ssl_enabled]
Option
Argument
Description
-DomainName
domain_name

takes precedence.
user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

-pd
-SecurityDomain
-sdn

installation.
-ServiceName
service_name
-sn
UpdateSMTPOptions
185
Option
Argument
Description
-ResilienceTimeout

domain. If you omit this option, infacmd uses the
timeout value specified in the
INFA_CLIENT_RESILIENCE_TIMEOUT environment
variable. If no value is specified in the environment
variable, the default of 180 seconds is used.
smtp_host
Optional. The SMTP outbound mail server host name.

For example, enter the Microsoft Exchange Server for
Microsoft Outlook. Default is localhost.
smtp_user
Optional. User name for authentication upon sending.
smtp_email_password
Optional. Password for authentication upon sending, if

required by the outbound SMTP mail server.
smtp_email_address
Optional. Email address that the Email Service uses in

the From field when sending notification emails from a
workflow. Default is admin@example.com.
smtp_port
Optional. Port number used by the outbound SMTP

mail server. Valid values are from 1 to 65535. Default is
25.
smtp_auth_enabled
Optional. Indicates that the SMTP server is enabled for

authentication. If true, the outbound mail server
requires a user name and password. If true, you must
select whether the server uses the Transport Layer
Security (TLS) protocol or the Secure Sockets Layer
(SSL) protocol. Enter true or false. Default is false.
smtp_tls_enabled
Optional. Indicates that the SMTP server uses the TLS

protocol. If true, enter the TLS port number for the
SMTP server port property. Enter true or false.
Default is false.
smtp_ssl_enabled
Optional. Indicates that the SMTP server uses the SSL

protocol. If true, enter the SSL port number for the
SMTP server port property. Enter true or false.
Default is false.
-re
-SMTPServerHostName
-sa
-SMTPUsername
-su
-SMTPEmailPassword
-se
-SMTPEmailAddress
-ss
SMTPPort
-sp
-SMTPAuthEnabled
-sau
-SMTPTLSEnabled
-stls
-SMTPSSLEnabled
-sssl
186
CHAPTER 12
infacmd ipc Command Reference

ExportToPC, 187
ImportFromPC, 190
ExportToPC
Exports objects from the Model repository or an export file and converts them to PowerCenter objects.
The ExportToPC command converts objects from the Model repository or from an XML file that you exported
from the Model repository. You must choose either a Model repository or a source file for export. If you
choose both options, the source file option takes precedence. Run ExportToPC command to create an XML
file that you can import into PowerCenter with the pmrep program.
The infacmd ipc ExportToPC command uses the following syntax:
ExportToPC
<-Release|-rel> release_number
[<-SourceFile|-sf> source_file]
[<-SourceRepository|-sr> source_repository]
[<-SourceFolders|-f> folder1 folder2|<-SourceObjects|-so> object1 object2]
[<-Recursive|-r>]
[<-TargetLocation|-tl> target_location]
[<-TargetFolder|-tf> target_folder_name]
[<-CodePage|-cp> target_code_page]
[<-Check|-c>]
[<-ReferenceDataLocation|-rdl> reference_data_output_location]
[<-ConvertMappletTargets|-cmt>]
[<-ConvertMappingsToMapplets|-cmm>]
[<-NoValidation|-nv>]
[<-DSTErrorFormat|-def>]
187
The following table describes infacmd ipc ExportToPC command options and arguments:
Option
Argument
Description
-Release
release_numb
er
Required. The PowerCenter release number.
-rel
-SourceFile
source_file
Optional. The full path to an XML file containing source objects that you
exported with the Developer tool.
source_reposit
ory
Optional. The Model repository that contains the objects to export to

PowerCenter.
-sf
SourceRepositor
y
-sr
To specify the gateway host and port to connect to the Model Repository
Service, use the following command syntax in a non-Kerberos domain:
<Model repository name>@<host>:<port>#<projectname>
?
user=<username>[&namespace=<namespace>]&password=<pa
ssword>
To specify the domain name when you have multiple gateway nodes, use
the following command syntax to establish a resilient connection to the
Model Repository Service in a non-Kerberos domain:
<Model repository name>@<domainname>#<projectname>
?
user=<username>[&namespace=<namespace>]&password=<pa
ssword>
To specify the domain name with the logged-in credentials, use the
following command syntax to run the command with single sign on:
?isloggedinuser=true[&namespace=<namespace>]
To specify the gateway host and port with the logged-in credentials, use
the following command syntax to run the command with single sign on:
?isloggedinuser=true[&namespace=<namespace>]
To specify the gateway host and port with the user credentials you specify
instead of the logged-in credentials, use the following command syntax in
a Kerberos domain:
?
iskerberos=true&user=<username>[&namespace=<namespac
e>]&password=<password>
&Kerberosrealm=<kerberosrealm>
To specify the domain name with the user credentials you specify instead
of the logged-in credentials, use the following command syntax in a
Kerberos domain:
?
iskerberos=true&user=<username>[&namespace=<namespac
e>]&password=<password>
&Kerberosrealm=<kerberosrealm>
The port parameter is the HTTP port. The &namespace parameter is
optional. The default namespace is native.
188
Chapter 12: infacmd ipc Command Reference
Option
Argument
Description
-SourceFolders
source_folders
If you use -sr, you must use -f or -so.
-f
SourceObjects
List of source folders that you want to export from the Model repository.
You can export mapplets, mappings, and logical data object models from
the source folders to PowerCenter. If you export more than one object,
you must separate each object in the list with a space.
source_objects
-so
If you use -sr, you must use -f or -so.

List of source objects that you want to export from the Model repository.
You can export mapplets, mappings, and logical data object models to
PowerCenter. You can describe the object as a name.
Use the following syntax:
name=/<path>/<objectname>[&type=<typename>]
You must include the full path of the object. If you export more than one
object, you must separate each object in the list with a space.
You can enter the following types:
- Mapping. Use to export mapping and mapplets.
- DataObjectModel. Use to export logical data object models.
The type is not case sensitive. Default is Mapping.

-Recursive
Optional. Exports all mappings and logical data object models from the
source folders. Exports each subfolder below the objects, and any
subfolders below that.
target_location
Optional. The full path to the target XML file.
target_folder_n
ame
Optional. The PowerCenter folder to export the objects to. The

ExportToPC command places the folder name in the target XML file. If
you do not configure a folder name, the ExportToPC command creates a
folder name.
target_code_p
age
Optional. Code page of the PowerCenter repository. Default is UTF-8.
-cp
-Check
Optional. Tests the conversion without creating a target file.
reference_data
_output_locatio
n
Optional. Location where you want to save reference table data. The
ExportToPC command saves the reference table data as one or more
dictionary .dic files.
Optional. Converts targets in mapplets to output transformations in the

PowerCenter mapplet.
-r
-TargetLocation
-tl
-TargetFolder
-tf
-CodePage
-c
ReferenceDataLo
cation
-rdl
ConvertMappletT
argets
PowerCenter mapplets cannot contain targets. If the export includes a

mapplet that contains a target and you do not select this option, the export
fails.
-cmt
ConvertMappings
toMapplets
Optional. Converts Developer tool mappings to PowerCenter mapplets.

The Developer tool converts sources and targets in the mappings to Input
and Output transformations in a PowerCenter mapplet.
-cmm
ExportToPC
189
Option
Argument
Description
-NoValidation
Optional. The ExportToPC command does not validate source objects

before converting them.
Optional. The error messages appear in a format that the Developer tool
can parse. The full path of each object displays in the error messages.
Default is to display errors in a user-friendly format.
-nv
-DSTErrorFormat
-def
ImportFromPC
Converts a PowerCenter repository object XML file to a Model repository object XML file. Export
PowerCenter repository objects to an XML file. Run the importFromPC command to create a target XML file
with objects that you can import into a Model repository.
You can import the target XML file to a Model respository with the infacmd oie ImportObjects command or
from the Developer tool. If you use the command line to import the target XML file, ImportFromPC does not
assign connections to the Model repository objects in the target XML file. You can assign connections with
the infacmd oie ImportObjects command or from the Developer tool.
The infacmd ipc importFromPC command uses the following syntax:
importFromPC
<-Release|-rel> release_number
[<-SourceFile|-sf> source_file]
[<-TargetFile|-tf> target_location]
[<-Check|-c>]
[<-Db2Type|-dt> default_db2_type]
[<-Db2TypesFile|-df> db2_types_file]
[<-DefaultLookUpConType|-dl> default_lookup_con_type]
[<-LookUpConTypesFile|-lcf> lookup_connection_types_file]
[<-ConvertOverriddenProps|-orprops> recreate_transformation_with_overridden_properties_
in_mappings]
[<-LogFile|-lf> log_file]
The following table describes infacmd ipc ImportFromPC command options and arguments:
Option
Argument
Description
-Release
release_numb
er
Required. The version of the Model repository.
-rel
-SourceFile
source_file
Required. The full path to a PowerCenter XML file containing the source
objects.
-sf
190
Chapter 12: infacmd ipc Command Reference
Option
Argument
Description
-TargetFile
target_location
Required. The full path to a target XML file.
-tf
-Check
-c
-Db2Type
-dt
Optional. Tests the conversion without creating a target file.

When you test object conversion, you do not require target location.
default_db2_ty
pe
Optional. The DB2 subsystem type used for conversion.

You can specify either Db2Type or Db2TypesFile, or both. If you specify
both Db2Type and Db2TypesFile for IBM DB2 objects, the DB2 source
and target that are not listed in the Db2TypesFile gets converted to the
Db2Type.
If you do not specify a DB2 subsystem type, the default DB2 subsystem
type is used. Default is LUW.
-Db2TypesFile
db2_types_file
-df
Optional. A property file that contains the PowerCenter DB2 source and
Db2 subsystem type. You can use a Db2 types file if the Db2 source and
target are from different subsystems such as LUW, z/OS, or i/OS.
You can specify either Db2Type or Db2TypesFile, or both. If you specify
both Db2Type and Db2TypesFile for IBM DB2 objects, the DB2 source
and target that are not listed in the Db2TypesFile gets converted to the
Db2Type.
If you do not specify the DB2 subsystem type, the default DB2 subsystem
type is used. Default is LUW.
DefaultLookUpC
onType
default_lookup
_con_type
-dl
Optional. The lookup connection type used for conversion.

You can specify either DefaultLookUpConType or LookUpConTypesFile,
or both. If you specify both DefaultLookUpConType and
LookUpConTypesFile for the lookup objects, the Lookup transformations
that are not listed in the LookUpConTypesFile are converted to the
DefaultLookUpConType.
If you do not specify the DefaultLookUpConType for a lookup object
during conversion, the default connection type is used. Default is ODBC.
LookUpConType
sFile
lookup_connec
tion_type_file
-lcf
Optional. A property file that contains the lookup source and the lookup
connection type. You can use a lookup connection type file if the lookup
objects are from different databases, such as Oracle or IBM DB2.
You can specify either DefaultLookUpConType or LookUpConTypesFile,
or both. If you specify both DefaultLookUpConType and
LookUpConTypesFile for the lookup objects, the Lookup transformations
that are not listed in the LookUpConTypesFile are converted to the
DefaultLookUpConType.
If you do not specify the DefaultLookUpConType for a lookup object
during conversion, the default connection type is used. Default is ODBC.
ConvertOverride
nprops
True|False
Optional. Preserves override properties for reusable PowerCenter source,

target, and transformations during conversion.
The command creates nonreusable transformations for PowerCenter
transformations with override properties. It also creates reusable data
objects for PowerCenter sources and targets with override properties.
-orprops
Valid values are True or False. Default is True.

-LogFile
log_file
Optional. Path and file name of the output log file. Default is STDOUT.
-lf
ImportFromPC
191
CHAPTER 13
infacmd isp Command Reference

The infacmd isp program administers the Informatica domain, the security, and the PowerCenter application
services. You can enable and disable Informatica services with infacmd isp commands.
This chapter includes the commands that you can use with the infacmd isp program.
AddAlertUser
Subscribes a user to alert notification emails. Before you can subscribe any user to alerts, you must configure
SMTP settings for the outgoing mail server. You can run infacmd isp AddAlertUser for any user.
When you subscribe to alerts, you receive domain and service notification emails for the objects on which
you have permission.
The infacmd isp AddAlertUser command uses the following syntax:
AddAlertUser
<-AlertUser|-au> user_name
192
The following table describes infacmd isp AddAlertUser options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

the command with single sign-on, do not set the user name. If
you set the user name, the command runs without single signon.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
-ResilienceTimeout
-re
-AlertUser
gateway_host1:port
gateway_host2:port
...

domains.infa file is out of date.The host names and port
numbers for the gateway nodes in the domain.
conds

establish or re-establish a connection to the domain. If you
omit this option, infacmd uses the timeout value specified in
the INFA_CLIENT_RESILIENCE_TIMEOUT environment
variable. If no value is specified in the environment variable,
the default of 180 seconds is used.
user_name
Required. Name of user you want to subscribes to alerts.
-au
AddAlertUser
193
Related Topics:
UpdateSMTPOptions on page 563
AddConnectionPermissions
Assigns connection permissions to a user or group.
The infacmd isp AddConnectionPermissions command uses the following syntax:
<<-RecipientUserName|-run> recipient_user_name|<RecipientGroupName|-rgn>
recipient_group_name>
<-RecipientSecurityDomain|-rsd> recipient_security_domain]
<-ConnectionName|-cn> connection_name
[<-Permission|-p> permission_READ|WRITE|EXECUTE|GRANT|ALL
The following table describes infacmd isp AddConnectionPermissions options and arguments:
Option
Argument
Description
-DomainName
domain_name
Required. Name of the Informatica domain. You

can set the domain name with the -dn option or
the environment variable
INFA_DEFAULT_DOMAIN. If you set a domain
precedence.
user_name

authentication. User name to connect to the
domain. You can set the user name with the -un
INFA_DEFAULT_DOMAIN_USER. If you set a
user name with both methods, the -un option
takes precedence.
-dn
-UserName
-un
Optional if the domain uses Kerberos

authentication. To run the command with single
sign-on, do not set the user name. If you set the
user name, the command runs without single
sign-on.
194
Chapter 13: infacmd isp Command Reference
Option
Argument
Description
-Password
password
Required if you specify the user name. Password

for the user name. The password is case
sensitive. You can set a password with the -pd
INFA_DEFAULT_DOMAIN_PASSWORD. If you
set a password with both methods, the password
set with the -pd option takes precedence.
security_domain
Required if the domain uses LDAP

authentication. Optional if the domain uses
native authentication or Kerberos authentication.
Name of the security domain to which the
domain user belongs. You can set a security
variable INFA_DEFAULT_SECURITY_DOMAIN.
If you set a security domain name with both
methods, the -sdn option takes precedence. The
security domain name is case sensitive.
-pd
-SecurityDomain
-sdn
If the domain uses native or LDAP

authentication, the default is Native. If the
domain uses Kerberos authentication, the default
is the LDAP security domain created during
installation. The name of the security domain is
the same as the user realm specified during
installation.
-ResilienceTimeout
-re
ds

attempts to establish or re-establish a connection
to the domain. If you omit this option, infacmd
uses the timeout value specified in the
environment variable. If no value is specified in
the environment variable, the default of 180
seconds is used.
-RecipientUserName
recipient_user_name
Required if you do not specify the recipient group

name. Name of the user to whom the connection
permission is assigned.
recipient_group_name
Required if you do not specify the recipient user

name. Name of the group to whom the
connection permission is assigned.
recipient_security_domai
n_name
Required if recipient belongs to an LDAP

security domain. Name of the security domain
that the recipient belongs to. Default is Native.
-run
-RecipientGroupName
-rgn
-RecipientSecurityDomain
-rsd
195
Option
Argument
Description
-ConnectionName
connection_name_securi
ty_domain
Required. Name of the connection
-cn
-Permission
permission
-p
Required. Type of permission to assign.

Enter one or more of the following values
separated by spaces:
-
READ
WRITE. Read and Write
EXECUTE
GRANT. Read and Grant
ALL. Read, Write, Execute Grant
AddDomainLink
Adds a link to a domain. records connection properties to a remote, or linked, domain so that you can
exchange repository metadata between the local domain and the linked domain.
You may want to add a link to a domain if you need to access a PowerCenter Repository Service in that
domain.
You can add a link to another Informatica domain when you register or unregister a local repository with a
global repository in another Informatica domain.
The infacmd isp AddDomainLink command uses the following syntax:
AddDomainLink
<-LinkedDomainName|-ld> linked_domain_name
<-DomainLink|-dl> domain_host1:port domain_host2:port...
196
The following table describes infacmd isp AddDomainLink options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
-ResilienceTimeout
-re
-LinkedDomainName
gateway_host1:port
gateway_host2:port
...

domains.infa file is out of date. The host names and port
numbers for the gateway nodes in the local domain.
conds

to establish or re-establish a connection to the local domain.
If you omit this option, infacmd uses the timeout value
linked_domain_name
Required. Name of the domain that you want to establish a

connection with.
gateway_host1:port
gateway_host2:port
...
Required. The host names and port numbers for the

gateway nodes in the linked domain.
-ld
-DomainLink
-dl
AddDomainLink
197
AddDomainNode
Adds a node to the domain. Before you can start the node, you must define it by running infasetup
DefineGatewayNode or DefineWorkerNode on the node.
The infacmd isp AddDomainNode command uses the following syntax:
AddDomainNode
[<-FolderPath|-fp> full_folder_path]
[<-EnableServiceRole|-esr> true|false]
[<-EnableComputeRole|-ecr> true|false]
The following table describes infacmd isp AddDomainNode options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

you set the user name, the command runs without single
sign-on.
-Password
password
-pd
198
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-NodeName
node_name
Required. Name of the node you want to add to the domain.
full_folder_path
Optional. Full path, excluding the domain name, to the folder

in which you want to add the node. Must be in the following
format:
-hp
-ResilienceTimeout
-nn
-FolderPath
-fp
Default is / (the domain).
-EnableServiceRole
true | false
-esr
Optional. Enables the service role on the node. If true,

application services can run on the node. If false, application
services cannot run on the node. Set to false only if the node
is assigned to a Data Integration Service grid and you want to
dedicate the node to running mappings.
Default is true.
-EnableComputeRole
-esr
true | false
Optional. Enables the compute role on the node. If true, the

node can perform computations requested by remote
application services. If false, the node cannot perform
computations requested by remote application services.
A node requires the compute role when the Data Integration
Service runs jobs on the node.
If the Data Integration Service does not run jobs on the node,
you can disable the compute role. However, enabling or
disabling the compute role does not have a performance
impact.
Default is true.
AddDomainNode
199
AddGroupPrivilege
Assigns a privilege to a group in the domain. You can assign privileges to a group for the domain. You can
also assign group privileges for each application service in the domain.
The infacmd isp AddGroupPrivilege command uses the following syntax:
AddGroupPrivilege
<-Gateway|-hp> gateway_host1:port gateway_host2:port...]
<-GroupName|-gn> group_name
[<-GroupSecurityDomain|-gsf> group_security_domain]
<-PrivilegePath|-pp> path_of_privilege
The following table describes infacmd isp AddGroupPrivilege options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

environment variable INFA_DEFAULT_DOMAIN_USER.
If you set a user name with both methods, the -un option
takes precedence.
-dn
-UserName
-un

-Password
password
-pd
200

user name. The password is case sensitive. You can set
a password with the -pd option or the environment
variable INFA_DEFAULT_DOMAIN_PASSWORD. If you
set a password with both methods, the password set with
Option
Argument
Description
-SecurityDomain
security_domain

security domain that the user belongs to. You can set a
set a security domain name with both methods, the -sdn
gateway_host1:port

-re
conds

attempts to establish or reestablish a connection to the
domain. If you omit this option, infacmd uses the timeout
value specified in the
-GroupName
group_name
Required. Name of the group to which you are assigning

the privilege. To enter a name that contains a space or
other non-alphanumeric character, enclose the name in
quotation marks.
-gsf
group_security_domai
n

security domain that the group to which you are assigning
the privilege belongs to. Default is Native.
-ServiceName
service_name
Required. Domain or application service name for which

you want to view privileges.
path_of_privilege
Required. Fully-qualified name of the privilege you want

to assign to the group. A fully-qualified name includes
privilege group name and privilege name. For example, a
fully-qualified privilege name for the Repository Service is
folder/create. If the privilege name includes spaces,
enclose the path in quotation marks as follows:
-sdn
-Gateway
-hp
-ResilienceTimeout
-gn
-GroupSecurityDomain
-sn
-PrivilegePath
-pp
Runtime Objects/Monitor/Execute/Manage
Execution
If the privilege name includes the special character /,
add the escape character \ before it as follows:
Model/View Model/Export\/Import Models
AddGroupPrivilege
201
AddLicense
Adds a license to the domain. After you add a license, you can assign it to an application service using the
AssignLicense command. You must assign a license to a service before you can use the service.
The infacmd isp AddLicense command uses the following syntax:
AddLicense
[<-SecurityDomain|-sdn> securitydomain]
<-LicenseName|-ln> license_name
<-LicenseKeyFile|-lf> license_key_file
The following table describes infacmd isp AddLicense options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name
Required if the domain uses Native or LDAP authentication. User

name to connect to the domain. You can set the user name with
the -un option or the environment variable
-dn
-UserName
-un

-Password
password
-pd
202
precedence.
Option
Argument
Description
-SecurityDomain
security_domain
Required if the domain uses LDAP authentication. Optional if the

domain uses native authentication or Kerberos authentication.
Name of the security domain to which the domain user belongs.
You can set a security domain with the -sdn option or the
environment variable INFA_DEFAULT_SECURITY_DOMAIN. If
you set a security domain name with both methods, the -sdn
option takes precedence. The security domain name is case
sensitive.
-sdn

Native. If the domain uses Kerberos authentication, the default is
the LDAP security domain created during installation. The name
of the security domain is the same as the user realm specified
during installation.
-Gateway
gateway_host1:port
gateway_host2:port
...

-re
timeout_period_in_s
econds

establish or re-establish a connection to the domain. If you omit
-LicenseName
license_name
Required. Name of the license. The name is not case sensitive

and must be unique within the domain. The name cannot exceed
79 characters, have leading or trailing spaces, or contain
carriage returns, tabs, or the following characters:
-hp
-ResilienceTimeout
-ln
/ * ? < > " |

-LicenseKeyFile
license_key_file
Required. Path to the license key file.
full_folder_path
Optional. Full path, excluding the domain name, to the folder in

which you want to add the license. Must be in the following
format:
-lf
-FolderPath
-fp
AddNamespace
Creates an LDAP security domain and sets the filters to search for users or groups in the directory service.
Creates the LDAP security domain if the Informatica domain uses LDAP or Kerberos authentication.
The infacmd isp AddNamespace command uses the following syntax:
AddNamespace
AddNamespace
203
<-NameSpace|-ns> namespace
[<-UserSearchBase|-usb> usersearchbase]
[<-UserFilter|-uf> userfilter]
[<-GroupSearchBase|-gsb> groupsearchbase]
[<-GroupFilter|-gf> groupfilter]
The following table describes infacmd isp AddNamespace options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

single sign-on.
-Password
password
-pd
204

Option
Argument
Description
-SecurityDomain
security_domain
Name of the security domain to which the domain user

belongs. You can set a security domain with the -sdn
sensitive.
-sdn
You can specify a value for sdn or use the default based
on the authentication mode:
- Required if the domain uses LDAP authentication. Default is
Native. To work with LDAP authentication, you need to
specify the value for -sdn.
authentication. If the domain uses Kerberos authentication,
the default is the LDAP security domain created during
-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds
Optional. Amount of time in seconds that infacmd tries to

establish a connection to the domain. If you omit this
option, infacmd uses the timeout value specified in the
variable. If you do not specify the environment variable, the
default value used is 180 seconds.
-NameSpace
namespace
Required. Name of the LDAP or Kerberos security domain

that you want to add. The name is not case sensitive and
must be unique within the domain. The name cannot
contain spaces or any of the following special characters:
-hp
-ResilienceTimeout
-ns
,+/<>@;\%?
The name cannot exceed 128 characters. The name can
contain an ASCII space character except for the first and
last character. You cannot use any other space characters.
-UserSearchBase
-usb
usersearchbase
Distinguished name (DN) of the entry that serves as the

starting point to search for user names in the LDAP
directory service. The LDAP directory service searches for
an object in the directory according to the path in the
distinguished name of the object.
For example, in Microsoft Active Directory, the
distinguished name of a user object might be
cn=UserName,ou=OrganizationalUnit,dc=DomainName.
The series of relative distinguished names denoted by
dc=DomainName identifies the DNS domain of the object.
AddNamespace
205
Option
Argument
Description
-UserFilter
userfilter
An LDAP query string that specifies the search criteria to

search for users in the directory service. The filter can
specify attribute types, assertion values, and matching
criteria.
-uf
For example: The filter (objectclass=*)searches all

objects. The filter(&(objectClass=user)(!
(cn=susan)))searches all user objects except susan.
For more information about search filters, see the
documentation for the LDAP directory service.
-GroupSearchBase
groupsearchbase

starting point to search for group names in the LDAP
directory service.
groupfilter
An LDAP query string that specifies the criteria for

searching for groups in the directory service.
-gsb
-GroupFilter
-gf
AddNodeResource
Adds a custom resource or a file directory resource to a node.
When a PowerCenter Integration Service runs on a grid, the Load Balancer can use resources to distribute
Session, Command, and predefined Event-Wait tasks. If the PowerCenter Integration Service is configured to
check resources, the Load Balancer distributes tasks to nodes where the resources are added and enabled.
The infacmd isp AddNodeResource command uses the following syntax:
AddNodeResource
[<-ResourceCategory|-rc> resource_category ("PCIS", "DIS")]
<-ResourceType|-rt> resource_type("Custom", "File Directory")
<-ResourceName|-rn> resource_name
[<-ResourceValue|-rv> resource_value]
206
The following table describes infacmd isp AddNodeResource options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

establish or reestablish a connection to the domain. If you
-NodeName
node_name
Required. Name of the node where you want to add a

resource.
-hp
-ResilienceTimeout
-nn
-ResourceCategory
-rc
resource_category
Optional. Category of the resource. Valid categories include:

- PCIS. Resource for the PowerCenter Integration Service.
- DIS. Reserved for future use.
Default is PCIS.
AddNodeResource
207
Option
Argument
-ResourceType
resource_type
Description
Required. Type of resource. Valid types include:
- Custom
- File Directory
-rt
-ResourceName
resource_name
-rn
Required. Name of the resource. The name cannot exceed 79

characters, have leading or trailing spaces, or contains
carriage returns, tabs, or the following characters:
\ / * ? < > " | $
-ResourceValue
resource_value
Optional. Reserved for future use.
-rv
AddRolePrivilege
Assigns a privilege to a role in the domain. You can assign privileges to a role for the domain. You can also
assign role privileges for each application service in the domain.
The infacmd isp AddRolePrivilege command uses the following syntax:
AddRolePrivilege
<-RoleName|-rn> role_name
<-ServiceType|-st> service_type AS|CMS|MM|MRS|RPS|RS|DOMAIN
208
The following table describes infacmd isp AddRolePrivilege options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port

-re
nds

-RoleName
role_name
Required. Name of the role to which you are assigning the

privilege. To enter a name that contains a space or other
non-alphanumeric character, enclose the name in quotation
marks.
-hp
-ResilienceTimeout
-rn
AddRolePrivilege
209
Option
Argument
Description
-ServiceType
service_type
Required. Domain or application service type to which you

assign the privilege for the role.
-st
Service types include:

-
-PrivilegePath
path_of_privilege
-pp
AS. Analyst Service

CMS. Content Management Service
MM. Metadata Manager Service
MRS. Model Repository Service
RPS. Reporting Service
RS. PowerCenter Repository Service
DOMAIN. Domain
Required. Fully-qualified name of the privilege you want to

assign to the group. A fully-qualified name includes privilege
group name and privilege name. For example, a fullyqualified privilege name for the Repository Service is folder/
create. If the privilege name includes spaces, enclose the
path in quotation marks as follows:
Execution
If the privilege name includes the special character /, add
the escape character /before it as follows:
AddServiceLevel
Adds a service level.
Service levels establish priority among tasks that are waiting to be dispatched. You can create different
service levels that a task developer can assign to workflows.
Each service level you create has a name, dispatch priority, and maximum dispatch wait time. The dispatch
priority is a number that establishes the priority for dispatch. The Load Balancer dispatches high priority tasks
before low priority tasks. The maximum dispatch wait time specifies the amount of time the Load Balancer
waits before it changes the dispatch priority for a task to the highest priority.
The infacmd isp AddServiceLevel command uses the following syntax:
AddServiceLevel
<-ServiceLevelName|-ln> service_level_name
<-ServiceLevel|-sl> option_name=value ...
210
The following table describes infacmd isp AddServiceLevel options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
-ResilienceTimeout
-re
gateway_host1:port
gateway_host2:port
...

conds

AddServiceLevel
211
Option
Argument
Description
-ServiceLevelName
service_level_name
Required. Name of the service level.
option_name=value
Required. The service level properties. You can set the

following properties:
-ln
-ServiceLevel
-sl
- DispatchPriority. The initial priority for dispatch. Smaller

numbers have higher priority. Priority 1 is the highest priority.
Default is 5.
- MaxDispatchWaitTime. The amount of time in seconds that can
elapse before the Load Balancer changes the dispatch priority
for a task to the highest priority. Default is 1800.
AddUserPrivilege
Assigns a privilege to a user in the domain. You can assign user privileges for each application in the
domain.
The infacmd isp AddUserPrivilege command uses the following syntax:
AddUserPrivilege
<-ExistingUserName|-eu> existing_user_Name
[<-ExistingUserSecurityDomain|-esd> existing_user_security_domain]
212
The following table describes infacmd isp AddUserPrivilege options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

sign-on.
-Password
password

security_domain

authentication. Optional if the domain uses native
authentication or Kerberos authentication. Name
of the security domain to which the domain user
belongs. You can set a security domain with the sdn option or the environment variable
INFA_DEFAULT_SECURITY_DOMAIN. If you
set a security domain name with both methods,
the -sdn option takes precedence. The security
domain name is case sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port
Required if the gateway connectivity information

in the domains.infa file is out of date. The host
names and port numbers for the gateway nodes
in the domain.
AddUserPrivilege
213
Option
Argument
Description
-ResilienceTimeout
-re
onds

seconds is used.
-ExistingUserName
existing_user_name
Required. User account to which you are

assigning the privilege. To enter a name that
contains a space or other non-alphanumeric
-esd
existing_user_security_
domain
Required if you use LDAP authentication. Name

of the security domain that the user to which you
are assigning the privilege belongs to. Default is
Native.
-ServiceName
service_name
Required. Domain or application service name for

which you want to view privileges.
path_of_privilege
Required. Fully-qualified name of the privilege

you want to assign to the group. A fully-qualified
name includes privilege group name and
privilege name. For example, a fully-qualified
privilege name for the Repository Service is
folder/create. If the privilege name includes
spaces, enclose the path in quotation marks as
follows:
-eu
-ExistingUserSecurityDomain
-sn
-PrivilegePath
-pp
Runtime Objects/Monitor/Execute/
Manage Execution
If the privilege name includes the special
character /, add the escape character \ before
it as follows:
Model/View Model/Export\ /Import
Models
AddUserToGroup
Adds a native or LDAP user to a native group in the domain. The user inherits all permissions and privileges
associated with the group.
The infacmd isp AddUserToGroup command uses the following syntax:
AddUserToGroup
214

The following table describes infacmd isp AddUserToGroup options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

user name, the command runs without single signon.
-Password
password

for the user name. The password is case sensitive.
You can set a password with the -pd option or the
INFA_DEFAULT_DOMAIN_PASSWORD. If you set
a password with both methods, the password set
with the -pd option takes precedence.
security_domain

Kerberos authentication. Name of the security
domain to which the domain user belongs. You can
set a security domain with the -sdn option or the
option takes precedence. The security domain
-pd
-SecurityDomain
-sdn
If the domain uses native or LDAP authentication,

the default is Native. If the domain uses Kerberos
AddUserToGroup
215
Option
Argument
Description
-Gateway
gateway_host1:port
gateway_host2:port...
Required if the gateway connectivity information in

the domains.infa file is out of date. The host names
domain.
-re
onds

the domain. If you omit this option, infacmd uses the
environment variable, the default of 180 seconds is
used.
-ExistingUserName
existing_user_Name
Required. Name of the user you want to add.
-esd
domain
Required if you use LDAP authentication. Name of

the security domain that the user you want to add
belongs to. Default is Native.
-GroupName
group_name
Required. Name of the group to which you want to

add the user.
-hp
-ResilienceTimeout
-eu
-gn
AssignedToLicense
Lists the services assigned to a license. You can list services currently assigned to a license.
The infacmd isp AssignedToLicense command uses the following syntax:
AssignedToLicense
216
The following table describes infacmd isp AssignedToLicense options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

INFA_CLIENT_RESILIENCE_TIMEOUT environment variable.
If no value is specified in the environment variable, the default
of 180 seconds is used.
-LicenseName
license_name
Required. Name of the license.
-hp
-ResilienceTimeout
-ln
AssignedToLicense
217
AssignGroupPermission
Assigns a group permission on an object.
Permissions allow a group to access objects in a domain. Objects include the domain, folders, nodes, grids,
licenses, and application services. For example, if you assign a group permission on a folder, the group
inherits permission on all objects in the folder.
The infacmd isp AssignGroupPermission command uses the following syntax:
<-ExistingGroup|-eg> existing_group_name
<-ObjectName|-on> object_name
<-ObjectType|-ot> object_type_SERVICE_LICENSE_NODE_GRID_FOLDER_OSPROFILE
The following table describes infacmd isp AssignGroupPermission options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

sign-on.
-Password
-pd
218
password

Option
Argument
Description
-SecurityDomain
security_domain

-sdn

installation.
-Gateway
gateway_host1:port

in the domain.
-re
ds

seconds is used.
-ExistingGroup
existing_group_name
Required. Name of the group to which you want

to assign a permission on an object.
group_security_domain

of the security domain that the group to which
you want to assign a permission belongs to.
Default is Native.
object_name
Required. Name of the object that you want to

assign the group access permission.
-hp
-ResilienceTimeout
-eg
-gsf
-ObjectName
-on
-ObjectType
-ot
object_type_SERVICE_L
ICENSE_NODE_GRID_
FOLDER_OSPROFILE
Required. Type of object.

-
Service
License
Node
Grid
Folder
OSProfile
219
AssignISToMMService
Assigns the associated PowerCenter Integration Service for a Metadata Manager Service.
The infacmd isp AssignISToMMService command uses the following syntax:
AssignISToMMService
<-IntegrationService|-is> integration_service_name
[<-RepositoryUserSecurityDomain|-rsdn> repository_user_security_domain]
<-RepositoryUser|-ru> repository_user
<-RepositoryPassword|-rp> repository_password
The following table describes infacmd isp AssignISToMMService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
-pd
220
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-ServiceName
service_name
Required. Name of the Metadata Manager Service to which

you want to assign the Integration Service.
integration_service_n
ame
Required. Name of the PowerCenter Integration Service that

you want to associate with the Metadata Manager Service.
repository_user_secu
rity_domain
Required if the domain uses LDAP authentication or Kerberos

PowerCenter repository user belongs.
-hp
-ResilienceTimeout
-sn
-IntegrationService
-is
RepositoryUserSecurit
yDomain
-rsdn
The security domain name is case sensitive.

If you do not specify this option, the command sets the
repository user security domain to the security domain you
specify in the -sdn option.
-RepositoryUser
repository_user
Required. Name of the PowerCenter repository user.
repository_password
Required. Password for the PowerCenter repository user.

User password. You can set a password with the -rp option or
the environment variable INFA_REPOSITORY_PASSWORD.
If you set a password with both methods, the password set
with the -rp option takes precedence.
-ru
-RepositoryPassword
-rp
AssignISToMMService
221
AssignLicense
Assigns a license to an application service. You must assign a license to an application service before you
can enable the service.
Note: You cannot assign a license to a service if the service is assigned to another license. To assign a
different license to a service, use the RemoveLicense command to remove the existing license from the
service, and then assign the new license to the service.
The infacmd isp AssignLicense command uses the following syntax:
AssignLicense
<-ServiceNames|-sn> service1_name service2_name ...
The following table describes infacmd isp AssignLicense options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
-pd
222
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

default is the LDAP security domain created during installation.
The name of the security domain is the same as the user
realm specified during installation.
-Gateway
gateway_host1:port

-re
conds

-LicenseName
license_name
Required. Name of the license you want to assign to a service.
service_name1
service_name2 ...
Required. Names of the services for which you want to assign

a license. To enter a name that contains a space or other nonalphanumeric character, enclose the name in quotation marks.
Restart the service to apply changes.
-hp
-ResilienceTimeout
-ln
-ServiceNames
-sn
AssignRoleToGroup
Assigns a role to a group for a domain or an application service.
The infacmd isp AssignRoleToGroup command uses the following syntax:
AssignRoleToGroup
AssignRoleToGroup
223
The following table describes infacmd isp AssignRoleToGroup options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

single sign-on.
-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
-ResilienceTimeout
-re
224
gateway_host1:port
gateway_host2:port
...

conds

Option
Argument
Description
-GroupName
group_name
Required. Name of the group to which you are assigning

the role. To enter a name that contains a space or other
non-alphanumeric character, enclose the name in
quotation marks.
-gsf
group_security_doma
in
Required if you use LDAP authentication.Name of the

security domain that the group to which you are assigning
the role belongs to. Default is Native.
-RoleName
role_name
Required. Name of the role you want to assign to the

group.
service_name

you want to assign the role. To enter a name that contains
a space or other non-alphanumeric character, enclose the
name in quotation marks.
-gn
-rn
-ServiceName
-sn
AssignRoleToUser
Assigns a role to a user for a domain or an application service.
The infacmd isp AssignRoleToUser command uses the following syntax:
AssignRoleToUser
AssignRoleToUser
225
The following table describes infacmd isp AssignRoleToUser options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

You can set the user name with the -un option or
precedence.
-dn
-UserName
-un

-Password
password

security_domain

option takes precedence. The security domain name
is case sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
-hp
226
gateway_host1:port

the domains.infa file is out of date.The host names
domain.
Option
Argument
Description
-ResilienceTimeout
-re
onds

used.
-ExistingUserName
existing_user_Name
Required. User account to which you are assigning

the role. To enter a name that contains a space or
other non-alphanumeric character, enclose the
-esd
domain
Required if you use LDAP authentication.Name of

the security domain that the user to which you are
assigning the role belongs to. Default is Native.
-RoleName
role_name
Required. Name of the role you want to assign to

the user.
service_name

which you want to assign the role. To enter a name
that contains a space or other non-alphanumeric
-eu
-rn
-ServiceName
-sn
AssignRSToWSHubService
Associates a PowerCenter repository with a Web Services Hub in the domain.
The infacmd isp AssignRSToWSHubService command uses the following syntax:
<-RepositoryUser|-ru> user
<-RepositoryPassword|-rp> password
227
The following table describes infacmd isp AssignRSToWSHubService options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
gateway_host1:port

-re
onds

-ServiceName
service_name
Required. Name of the Web Services Hub with which you

want to associate a repository.
-hp
-ResilienceTimeout
-sn
228
Option
Argument
Description
-NodeName
node_name
Required. Name of the node where you want the Web

Services Hub process to run. If the PowerCenter
environment is configured for high availability, this option
specifies the name of the primary node.
repository_service_na
me
Required. Name of the PowerCenter Repository Service

that the Web Services Hub depends on.
-nn
-RepositoryService
-rs
To enter a name that contains a space or other nonalphanumeric character, enclose the name in quotation
marks.
-RepositoryUser
user
-ru
Required. User name used to connect to the repository.

marks.
-RepositoryPassword
password
-rp
Required. User password. User password. You can set a

password with the -rp option or the environment variable
INFA_REPOSITORY_PASSWORD. If you set a password
with both methods, the password set with the -rp option
takes precedence.
AssignUserPermission
Assigns a user permission on an object.
Permissions allow a user to access objects in a domain. Objects include the domain, folders, nodes, grids,
licenses, and application services. For example, if you assign a user permission on a folder, the user inherits
permission on all objects in the folder.
The infacmd isp AssignUserPermission command uses the following syntax:
[[<-ResilienceTimeout|-re> timeout_period_in_seconds]
<-ExistingUserName|-eu> existing_user_name
229
The following table describes infacmd isp AssignUserPermission options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

the user name. If you set the user name, the
command runs without single sign-on.
-Password
password

security_domain

is case sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
-hp
-ResilienceTimeout
-re
230
gateway_host1:port

domain.
onds

environment variable.
Option
Argument
Description
-ExistingUserName
existing_user_name
Required. Name of the user to which you want to

assign a permission on an object.
-esd
existing_user_security
_domain

the security domain that the user to which you want
to assign a permission belongs to. Default is Native.
-ObjectName
object_name
Required. Name of the object that you want to

assign the user access permission.
-eu
-on
-ObjectType
-ot
object_type_SERVICE
_LICENSE_NODE_GR
ID_FOLDER_OSPROF
ILE

-
Service
License
Node
Grid
Folder
OSProfile
BackupDARepositoryContents
Backs up content for a Data Analyzer repository to a binary file. When you back up the content, the Reporting
Service saves the Data Analyzer repository including the repository objects, connection information, and
code page information. Run infacmd isp RestoreDARepositoryContents to restore the repository content.
The infacmd isp BackupDARepositoryContents command uses the following syntax:
<-fileName|-f> file_name
[<-overwrite|-o> overwrite_file]
231
The following table describes infacmd isp BackupDARepositoryContent options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

User name to connect to the domain. You can set the user name
with the -un option or the environment variable
-dn
-UserName
-un

-Password
password
precedence.
security_domain

sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
timeout_period_in_s
econds

-ServiceName
service_name
Required. Name of the Reporting Service for which you want to

back up contents.
file_name
Required. Name and file path where you want to write the
backup file.
overwrite_file
Overwrites the backup file if a file with the same name already
exists.
-hp
-ResilienceTimeout
-sn
-fileName
-f
-overwrite
-o
Required if a file with the same name exists.
232
ConvertLogFile
Converts binary log files to text files, XML files, or readable text on the screen.
The infacmd isp ConvertLogFile command uses the following syntax:
ConvertLogFile
<-InputFile|-in> input_file_name
[<-Format|-fm> format_TEXT_XML]
The following table describes infacmd isp ConvertLogFile options and arguments:
Option
Argument
Description
-InputFile
input_file_name
Required. Name and path for the log file you want to convert.
-in
By default, the Service Manager writes log files to the server

\infa_shared\log directory on the master gateway node.
-Format
format

- Text
- XML
-fm
If you do not specify a format, infacmd uses text format with lines
wrapped at 80 characters.
-OutputFile
output_file_name
-lo

If you do not specify an output file name, infacmd displays the log
events on the screen.
convertUserActivityLogFile
Converts a binary user activity log file retrieved with the getUserActivityLog command to text or XML format.
The infacmd isp convertUserActivityLogFile command uses the following syntax:
convertUserActivityLogFile
<-InputFile|-in> input_file_name
ConvertLogFile
233
The following table describes infacmd isp convertUserActivityLogFile options and arguments:
Option
Argument
Description
-InputFile
input_file_name
Required. Name of the log file to convert.
-in
-Format
format_TEXT_XML
Optional. Output file format. Valid formats include:

- Text
- XML
-fm
Default is text.
-OutputFile
output_file_name
-lo
Optional. Name of the output file. If you do not specify an

output file name, the command displays the log on the
command line.
CreateConnection
Defines a connection and the connection options.
To list connection options for an existing connection, run infacmd isp ListConnectionOptions.
The infacmd isp CreateConnection command uses the following syntax:
CreateConnection
[<-ConnectionId|-cid> connection_id]
<-ConnectionType|-ct> connection_type
[<-ConnectionUserName|-cun> connection_user_name]
[<-ConnectionPassword|-cpd> connection_password]
[<-VendorId|-vid> vendor_id]
[-o options] (name-value pairs separated by space)
234
The following table describes infacmd isp CreateConnection options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

single sign-on.
-Password
password

security_doma
in

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-ResilienceTimeout
-re
-ConnectionName
-cn
timeout_perio
d_in_seconds

connection_na
me
Name of the connection. The name is not case sensitive

and must be unique within the domain. It cannot exceed
128 characters, contain spaces, or contain the following
special characters:
~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ;
" ' < , > . ? /
CreateConnection
235
Option
Argument
Description
- ConnectionId
connection_id
String that the Data Integration Service uses to identify the

connection. The ID is not case sensitive. It must be 255
characters or less and must be unique in the domain. You
cannot change this property after you create the
connection. Default value is the connection name.
connection_ty
pe
Required. Type of connection. Use one of the following

connection types:
-cid
-ConnectionType
-ct
ADABAS
DATASIFT
DB2
DB2I
DB2Z
FACEBOOK
GreenplumPT
HADOOP
HIVE
HadoopFileSystem
IMS
JDBC
LINKEDIN
ODBC
ORACLE
SAP
SEQ
SFDC
SQLSERVER
TWITTER
TWITTERSTREAMING
VSAM
WEBCONTENT - KAPOWKATALYST
You can use the infacmd isp ListConnections command to

view connection types.
ConnectionUserName
-cun
236
connection_us
er_name
Required. Database user name.
Option
Argument
Description
-ConnectionPassword
connection_pa
ssword
Required. Password for the database user name. You can

set a password with the -cpd option or the environment
variable INFA_DEFAULT_CONNECTION_PASSWORD, lf
you set the password with both options, the -cpd option
takes precedence.
-cpd
If you are creating an ADABAS, DB2I, DB2Z, IMS, SEQ, or

VSAM connection, you can enter a valid PowerExchange
passphrase instead of a password. Passphrases for
access to databases and data sets on z/OS can be from 9
to 128 characters in length. Passphrases for access to
DB2 for i5/OS can be up to 31 characters in length.
Passphrases can contain the following characters:
- Uppercase and lowercase letters
- The numbers 0 to 9
- Spaces
- The following special characters:
- ; # \ , . / ! % & * ( ) _ + { } : @
| < > ?
Note: The first character is an apostrophe.
Passphrases cannot include single quotation marks (),

double quotation marks (), or currency symbols.
If a passphrase contains spaces, you must enclose it with
double-quotation marks ("), for example, "This is an
example passphrase". If a passphrase contains
special characters, you must enclose it with triple doublequotation characters ("""), for example, """This
passphrase contains special characters !
% & *.""". If a passphrase contains only alphanumeric
characters without spaces, you can enter it without
delimiters.
Note: On z/OS, a valid RACF passphrase can be up to 100
characters in length. PowerExchange truncates
passphrases longer than 100 characters when passing
them to RACF for validation.
To use passphrases, ensure that the PowerExchange
Listener runs with a security setting of SECURITY=(1,N) or
higher in the DBMOVER member. For more information,
see "SECURITY Statement" in the PowerExchange
Reference Manual.
To use passphrases for IMS connections, ensure that the
following additional requirements are met:
- You must configure ODBA access to IMS as described in
the PowerExchange Navigator User Guide.
- You must use IMS data maps that specify IMS ODBA as the
access method. Do not use data maps that specify the DL/1
BATCH access method because this access method
requires the use of netport jobs, which do not support
passphrases.
- The IMS database must be online in the IMS control region
to use ODBA access to IMS.
CreateConnection
237
Option
Argument
Description
-VendorId
vendor_id
Optional. ID of the external partner who built the adapter.
options
Required. Enter name-value pairs separated by spaces.

The connection options are different for each connection
type.
-vid
-Options
-o
Adabas Connection Options

Use connection options to define an Adabas connection.
The following table describes Adabas connection options:
Option
Description
CodePage
Required. Code to read from or write to the database. Use the ISO code page name, such
as ISO-8859-6. The code page name is not case sensitive.
ArraySize
Optional. Determines the number of records in the storage array for the threads when the
worker threads value is greater than 0. Valid values are from 1 through 100000. Default is
25.
Compression
Optional. Compresses the data to decrease the amount of data Informatica applications
write over the network. True or false. Default is false.
EncryptionLevel
Optional. Level of encryption for RC2 or DES for encryption types. Enter one of the
following values for the encryption level:
- 1. Use a 56-bit encryption key for DES and RC2.
- 2. Use a 168-bit triple DES encryption key for DES or a 64-bit encryption keyfor RC2.
- 3. Use a 168-bit triple DES encryption key for DES or a 128-bit encryption key for RC2.
Default is 1.
Note: If you select None for encryption type, the Data Integration Service ignores the
encryption level value.
EncryptionType
Optional. Enter one of the following values for the encryption type:
- None
- RC2
- DES
Default is None.
238
InterpretAsRows
Optional. If true, the pacing size value represents a number of rows. If false, the pacing
size represents kilobytes. Default is false.
Location
Location of the PowerExchange Listener node that can connect to the database. The
location is defined in the first parameter of the NODE statement in the PowerExchange
dbmover.cfg configuration file.
Option
Description
OffLoadProcessing
Optional. Moves bulk data processing from the source machine to the Data Integration
Service machine.
- Auto. The Data Integration Service determines whether to use offload processing.
- Yes. Use offload processing.
- No. Do not use offload processing.
Default is Auto.
PacingSize
Optional. Slows the data transfer rate in order to reduce bottlenecks. The lower the value,
the greater the session performance. Minimum value is 0. Enter 0 for optimal
performance. Default is 0.
WorkerThread
Optional. Number of threads that the Data Integration Service uses to process bulk data
when offload processing is enabled. For optimal performance, this value should not
exceed the number of available processors on the Data Integration Service machine. Valid
values are 1 through 64. Default is 0, which disables multithreading.
WriteMode
Enter one of the following write modes:

- CONFIRMWRITEON. Sends data to the PowerExchange Listener and waits for a success/no
success response before sending more data.
- CONFIRMWRITEOFF. Sends data to the PowerExchange Listerner without waiting for a
success/no success response. Use this option when the target table can be reloaded if an
error occurs.
- ASYNCHRONOUSWITHFAULTT. Sends data to the PowerExchangeListener
asynchronously with the ability to detect errors.
Default is CONFIRMWRITEON.
EnableConnectionP
ool
Optional. Enables connection pooling. When you enable connection pooling, the
connection pool retains idle connection instances in memory. When you disable
connection pooling, the Data Integration Service stops all pooling activity. True or false.
Default is false.
ConnectionPoolSize
Optional. Maximum number of idle connections instances that the Data Integration Service
maintains for a database connection. Set this value to be more than the minimum number
of idle connection instances. Default is 15.
ConnectionPoolMax
IdleTime
Optional. Number of seconds that a connection exceeding the minimum number of

connection instances can remain idle before the connection pool drops it. The connection
pool ignores the idletime when it does not exceed the minimum number of idle connection
instances. Default is 120.
ConnectionPoolMin
Connections
Optional. Minimum number of idle connection instances that the pool maintains for a
database connection. Set this value to be equal to or less than the idle connection pool
size. Default is 0.
Related Topics:
DataSift Connection Options on page 240
DB2 for i5/OS Connection Options on page 241
Facebook Connection Options on page 244
Greenplum Connection Options on page 245
HBase Connection Options on page 247
HDFS Connection Options on page 249
Hadoop Connection Options on page 250
CreateConnection
239
Hive Connection Options on page 257
DB2 for z/OS Connection Options on page 262
IBM DB2 Connection Options on page 264
IMS Connection Options on page 267
JDBC Connection Options on page 269
LinkedIn Connection Options on page 272
Microsoft SQL Server Connection Options on page 273
Netezza Connection Options on page 276
OData Connection Options on page 277
ODBC Connection Options on page 279
Oracle Connection Options on page 281
Salesforce Connection Options on page 284
SAP Connection Options on page 285
Sequential Connection Options on page 286
Teradata Parallel Transporter Connection Options on page 289
Twitter Connection Options on page 291
Twitter Streaming Connection Options on page 292
VSAM Connection Options on page 293
Web Content-Kapow Katalyst Connection Options on page 295
DataSift Connection Options

Use connection options to define a DataSift connection.
The following table describes DataSift connection options for infacmd isp CreateConnection and
UpdateConnection commands:
Option
Description
userName
DataSift username for the DataSift user account.
apiKey
API key. The Developer API key is displayed in the Dashboard or

Settings page in the DataSift account.
Related Topics:
240
Adabas Connection Options on page 238
DB2 for i5/OS Connection Options

Use DB2I connection options to define the DB2 for i5/OS connection.
The following table describes DB2 for i5/OS connection options for infacmd isp CreateConnection and
Option
Description
DatabaseName
Database instance name.
EnvironmentSQL
Optional. SQL commands to set the database environment when you connect to the
database. The Data Integration Service executes the connection environment SQL
each time it connects to the database.
Note: Enclose special characters in double quotes.
CodePage
Required. Code page used to read from a source database or write to a target
database or file.
CreateConnection
241
Option
Description
ArraySize
Optional. Determines the number of records in the storage array for the threads when
the worker threads value is greater than 0. Valid values are from 1 through 100000.
Default is 25.
Compression
Optional. Compresses the data to decrease the amount of data to write over the
network. Default is false.
EncyptionLevel
Default is 1.
EncryptionType
Optional. Type of encryption. Enter one of the following values for the encryption type:
- None
- RC2
- DES
Default is None.
InterpretAsRows
Optional. Represent pacing size as a number of rows. If false, the pacing size
represents kilobytes. Default is false.
Location
location is defined in the first parameter of the NODE statement in the
PowerExchange dbmover.cfg configuration file.
PacingSize
Optional. Amount of data the source system can pass to the PowerExchange
Listener. Configure the pacing size if an external application, a database, or the Data
Integration Service node is a bottleneck. The lower the value, the faster the
performance.
Minimum value is 0. Enter 0 for maximum performance. Default is 0.
RejectFile
WriteMode
Optional. Enter the reject file name and path. Reject files contain rows that were not
written to the database.
- CONFIRMWRITEON. Sends data to the PowerExchange Listener and waits for a
success/no success response before sending more data.
- CONFIRMWRITEOFF. Sends data to the PowerExchange Listener without waiting for a
success/no success response. Use this option when the target table can be reloaded if
an error occurs.
- ASYNCHRONOUSWITHFAULTT. Sends data to the PowerExchange Listener
242
Option
Description
DatabaseFileOverrides
Specifies the i5/OS database file override. The format is:

from_file/to_library/to_file/to_member
Where:
- from_file is the file to be overridden
- to_library is the new library to use
- to_file is the file in the new library to use
- to_member is optional and is the member in the new library and file to use. *FIRST is
used if nothing is specified.
You can specify up to 8 unique file overrides on a single connection. A single override
applies to a single source or target. When you specify more than one file override,
enclose the string of file overrides in double quotes and include a space between
each file override.
Note: If both LibraryList and DatabaseFileOverrides are specified and a table exists in
both, DatabaseFileOverrides takes precedence.
IsolationLevel
Commit scope of the transaction. Select one of the following values:

- None
- CS. Cursor stability.
- RR. Repeatable Read.
- CHG. Change.
- ALL
Default is CS.
LibraryList
List of libraries that PowerExchange searches to qualify the table name for Select,
Insert, Delete, or Update statements. PowerExchange searches the list if the table
name is unqualified.
Separate libraries with semicolons.
Note: If both LibraryList and DatabaseFileOverrides are specified and a table exists in
both, DatabaseFileOverrides takes precedence.
EnableConnectionPool
Optional. Enables parallel processing when loading data into a table in bulk mode.
Used for Oracle. True or false. Default is true.
ConnectionPoolSize
Optional. Maximum number of idle connections instances that the Data Integration
Service maintains for a database connection. Set this value to be more than the
minimum number of idle connection instances.
ConnectionPoolMaxIdle
Time

connection instances can remain idle before the connection pool drops it. The
connection pool ignores the idletime when it does not exceed the minimum number of
idle connection instances.
ConnectionPoolMinConn
ections
database connection. Set this value to be equal to or less than the idle connection
pool size. Default is 0.
Related Topics:
CreateConnection
243
Facebook Connection Options

Use connection options to define a Facebook connection.
The following table describes Facebook connection options for infacmd isp CreateConnection and
244
Option
Description
ConsumerKey
The App ID that you get when you create the application in
Facebook. Facebook uses the key to identify the application.
ConsumerSecret
The App Secret that you get when you create the application in
Facebook. Facebook uses the secret to establish ownership of the
consumer key.
Option
Description
AccessToken
Access token that the OAuth Utility returns. Facebook uses this
token instead of the user credentials to access the protected
resources.
AccessSecret
Access secret is not required for Facebook connection.
Scope
Permissions for the application. Enter the permissions you used to

configure OAuth.
Related Topics:
Greenplum Connection Options

Use connection options to define a Greenplum connection.
CreateConnection
245

The following table describes the Greenplum connection options for infacmd isp CreateConnection and
Option
Description
UserName
Required. User name with permissions to access the Greenplum database.
Password
Required. Password to connect to the Greenplum database.
driverName
Required. Name of the Greenplum JDBC driver.

For example:com.pivotal.jdbc.GreenplumDriver
For more information about the driver, see the Greenplum documentation.
connectionString
Required. Greenplum JDBC connection URL.

For example: jdbc:pivotal:greenplum://
<hostname>:<port>;DatabaseName=<database_name>
For more information about the connection URL, see the Greenplum documentation.
hostName
Required. Host name or IP address of the Greenplum server.
portNumber
Required. Greenplum server port number.

If you enter 0, the gpload utility reads from the environment variable $PGPORT.
Default is 5432.
databaseName
Required. Name of the database that you want to connect to.
enableSSL
Optional. Set this option to true to establish secure communication between the gpload
utility and the Greenplum server over SSL.
SSLCertificatePath
Required if you enable SSL. Path where the SSL certificates for the Greenplum server are
stored.
Related Topics:
246
HBase Connection Options

Use connection options to define an Hbase connection.
The following table describes the HBase connection options for infacmd isp CreateConnection and
Property
Description
Name
The name of the connection. The name is not case sensitive and must be
unique within the domain. You can change this property after you create the
connection. The name cannot exceed 128 characters, contain spaces, or
contain the following special characters:
~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < ,
> . ? /
ID
String that the Data Integration Service uses to identify the connection. The ID
is not case sensitive. It must be 255 characters or less and must be unique in
the domain. You cannot change this property after you create the connection.
Default value is the connection name.
Description
The description of the connection. The description cannot exceed 4,000

characters.
Location
The domain where you want to create the connection.
Type
The connection type. Select HBase.
CreateConnection
247
Property
Description
ZooKeeper Host(s)
Name of the machine that hosts the ZooKeeper server. The name is case
sensitive.
When the ZooKeeper runs in the replicated mode, specify a comma-separated
list of servers in the ZooKeeper quorum servers. If the TCP connection to the
server breaks, the client connects to a different server in the quorum.
ZooKeeper Port
Port number of the machine that hosts the ZooKeeper server.
Enable Kerberos Connection
Enables the Informatica domain to communicate with the HBase master server
or region server that uses Kerberos authentication.
HBase Master Principal
Service Principal Name (SPN) of the HBase master server. Enables the
ZooKeeper server to communicate with an HBase master server that uses
Kerberos authentication.
Enter a string in the following format:
hbase/<domain.name>@<YOUR-REALM>
Where:
- domain.name is the domain name of the machine that hosts the HBase master
server.
- YOUR-REALM is the Kerberos realm.
HBase Region Server Principal
Service Principal Name (SPN) of the HBase region server. Enables the
ZooKeeper server to communicate with an HBase region server that uses
Enter a string in the following format:
hbase_rs/<domain.name>@<YOUR-REALM>
Where:
- domain.name is the domain name of the machine that hosts the HBase master
server.
- YOUR-REALM is the Kerberos realm.
Related Topics:
248
HDFS Connection Options

Use connection options to define an HDFS connection.
The following table describes the HDFS connection options for infacmd isp CreateConnection and
Option
Description
userName
User name to access HDFS.
nameNodeURI
The URI to access HDFS. The URI must be in the following format:
hdfs://<namenode>:<port>
Where
- <namenode> is the host name or IP address of the NameNode.
- <port> is the port that the NameNode listens for remote procedure
calls (RPC).
Related Topics:
CreateConnection
249
Hadoop Connection Options

Use connection options to define a Hive connection.
... -o option_name='value' option_name='value' ...
To enter multiple options, separate them with a space.
The following table describes Hadoop connection options for infacmd isp CreateConnection and
UpdateConnection commands that you configure when you want to use the Hadoop connection:
250
Option
Description
connectionId
String that the Data Integration Service uses to identify the connection. The ID
is not case sensitive. It must be 255 characters or less and must be unique in
the domain. You cannot change this property after you create the connection.
Default value is the connection name.
connectionType
Required. Type of connection is Hadoop.
name
~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < ,
> . ? /
Option
Description
RMAddress
The service within Hadoop that submits requests for resources or spawns
YARN applications.
Use the following format:
<hostname>:<port>
Where
- <hostname> is the host name or IP address of the Yarn resource manager.
- <port> is the port on which the Yarn resource manager listens for remote
procedure calls (RPC).
For example, enter: myhostame:8032

You can also get the Resource Manager Address property from yarn-site.xml
located in the following directory on the Hadoop cluster: /etc/hadoop/
conf/
The Resource Manager Address appears as the following property in yarnsite.xml:
<property>
<name>yarn.resourcemanager.address</name>
<value>hostname:port</value>
<description>The address of the applications manager
interface in the Resource Manager.</description>
</property>
Optionally, if the yarn.resourcemanager.address property is not
configured in yarn-site.xml, you can find the host name from the
yarn.resourcemanager.hostname or
yarn.resourcemanager.scheduler.address properties in yarnsite.xml. You can then configure the Resource Manager Address in the Hadoop
connection with the following value: hostname:8032
cadiAppYarnQueueName
The YARN scheduler queue name used by the Blaze engine that specifies
available resources on a cluster. The name is case sensitive.
cadiExecutionParameterList
Custom properties that are unique to the Blaze engine.

You can specify multiple properties.
<property1>=<value>
Where
- <property1> is a Blaze engine optimization property.
- <value> is the value of the Blaze engine optimization property.
To specify multiple properties use &: as the property separator.

Use custom properties only at the request of Informatica Global Customer
Support.
cadiMaxPort
The maximum value for the port number range for the Blaze engine.
cadiMinPort
The minimum value for the port number range for the Blaze engine.
cadiUserName
The operating system profile user name for the Blaze engine.
cadiWorkingDirectory
The HDFS file path of the directory that the Blaze engine uses to store
temporary files. Verify that the directory exists. The YARN user, Blaze engine
user, and mapping impersonation user must have write permission on this
directory.
databaseName
Namespace for tables. Use the name default for tables that do not have a
specified database name.
CreateConnection
251
Option
defaultFSURI
Description
The URI to access the default Hadoop Distributed File System.
Use the following connection URI:
hdfs://<node name>:<port>
Where
- <node name> is the host name or IP address of the NameNode.
- <port> is the port on which the NameNode listens for remote procedure calls
(RPC).
For example, enter: hdfs://myhostname:8020/

You can also get the Default File System URI property from core-site.xml
located in the following directory on the Hadoop cluster: /etc/hadoop/
conf/
Use the value from the fs.defaultFS property found in core-site.xml.
For example, use the following value:
<property>
<name>fs.defaultFS</name>
<value>hdfs://localhost:8020</value>
</property>
If the Hadoop cluster runs MapR, use the following URI to access the MapR
File system: maprfs:///.
engineType
The engine that the Hadoop environment uses to run a mapping on the Hadoop
cluster. Select a value from the drop down list.
For example select: MRv2
To set the engine type in the Hadoop connection, you must get the value for the
mapreduce.framework.name property from mapred-site.xml located in the
following directory on the Hadoop cluster: /etc/hadoop/conf/
If the value for mapreduce.framework.name is classic, select mrv1 as
the engine type in the Hadoop connection.
If the value for mapreduce.framework.name is yarn, you can select the
mrv2 or tez as the engine type in the Hadoop connection. Do not select Tez if
Tez is not configured for the Hadoop cluster.
You can also set the value for the engine type in hive-site.xml. The engine type
appears as the following property in hive-site.xml:
<property>
<name>hive.execution.engine</name>
<value>tez</value>
<description>Chooses execution engine. Options are: mr
(MapReduce, default) or tez (Hadoop 2 only)</
description>
</property>
252
Option
Description
environmentSQL
SQL commands to set the Hadoop environment. The Data Integration Service
executes the environment SQL at the beginning of each Hive script generated
in a Hive execution plan.
The following rules and guidelines apply to the usage of environment SQL:
- Use the environment SQL to specify Hive queries.
- Use the environment SQL to set the classpath for Hive user-defined functions and
then use environment SQL or PreSQL to specify the Hive user-defined functions.
You cannot use PreSQL in the data object properties to specify the classpath.
The path must be the fully qualified path to the JAR files used for user-defined
functions. Set the parameter hive.aux.jars.path with all the entries in
infapdo.aux.jars.path and the path to the JAR files for user-defined functions.
- You can use environment SQL to define Hadoop or Hive parameters that you
want to use in the PreSQL commands or in custom queries.
hadoopExecEnvExecutionPara
meterList
Custom properties that are unique to the Hadoop environment.

You can specify multiple properties.
<property1>=<value>
Where
- <property1> is a Hadoop environment optimization property.
- <value> is the value of the Hadoop environment optimization property.
To specify multiple properties use &: as the property separator.

Use custom properties only at the request of Informatica Global Customer
Support.
hiveWarehouseDirectoryOnHD
FS
The absolute HDFS file path of the default database for the warehouse that is
local to the cluster. For example, the following file path specifies a local
warehouse: /user/hive/warehouse
For Cloudera CDH, if the Metastore Execution Mode is remote, then the file
path must match the file path specified by the Hive Metastore Service on the
Hadoop cluster.
You can get the value for the Hive Warehouse Directory on HDFS from the
hive.metastore.warehouse.dir property in hive-site.xml located in the
following directory on the Hadoop cluster: /etc/hadoop/conf/
For example, use the following value:
<property>
<name>hive.metastore.warehouse.dir</name>
<value>/usr/hive/warehouse </value>
<description>location of the warehouse directory</
description>
</property>
For MapR, hive-site.xml is located in the following direcetory: /opt/
mapr/hive/<hive version>/conf.
CreateConnection
253
Option
Description
jobMonitoringURL
The URL for the MapReduce JobHistory server. You can use the URL for the
JobTracker URI if you use MapReduce version 1.
<hostname>:<port>
Where
- <hostname> is the host name or IP address of the JobHistory server.
- <port> is the port on which the JobHistory server listens for remote procedure
calls (RPC).
For example, enter: myhostname:8021

You can get the value for the Job Monitoring URL from mapred-site.xml. The
Job Monitoring URL appears as the following property in mapred-site.xml:
<property>
<name>mapred.job.tracker</name>
<value>myhostname:8021 </value>
<description>The host and port that the MapReduce job
tracker runs at.</description>
</property>
metastoreDatabaseDriver
Driver class name for the JDBC data store. For example, the following class
name specifies a MySQL driver:
com.mysql.jdbc.Driver
You can get the value for the Metastore Database Driver from hive-site.xml.
The Metastore Database Driver appears as the following property in hivesite.xml:
<property>
<name>javax.jdo.option.ConnectionDriverName</name>
<value>com.mysql.jdbc.Driver</value>
</property>
metastoreDatabasePassword
The password for the metastore user name.

You can get the value for the Metastore Database Password from hive-site.xml.
The Metastore Database Password appears as the following property in hivesite.xml:
<property>
<name>javax.jdo.option.ConnectionPassword</name>
<value>password</value>
</property>
254
Option
Description
metastoreDatabaseURI
The JDBC connection URI used to access the data store in a local metastore
setup. Use the following connection URI:
jdbc:<datastore type>://<node name>:<port>/<database
name>
where
- <node name> is the host name or IP address of the data store.
- <data store type> is the type of the data store.
- <port> is the port on which the data store listens for remote procedure calls
(RPC).
- <database name> is the name of the database.
For example, the following URI specifies a local metastore that uses MySQL as
a data store:
jdbc:mysql://hostname23:3306/metastore
You can get the value for the Metastore Database URI from hive-site.xml. The
Metastore Database URI appears as the following property in hive-site.xml:
<property>
<name>javax.jdo.option.ConnectionURL</name>
<value>jdbc:mysql://MYHOST/metastore</value>
</property>
metastoreDatabaseUserName
The metastore database user name.

You can get the value for the Metastore Database User Name from hivesite.xml. The Metastore Database User Name appears as the following property
in hive-site.xml:
<property>
<name>javax.jdo.option.ConnectionUserName</name>
<value>hiveuser</value>
</property>
metastoreMode
Controls whether to connect to a remote metastore or a local metastore. By

default, local is selected. For a local metastore, you must specify the Metastore
Database URI, Metastore Database Driver, Username, and Password. For a
remote metastore, you must specify only the Remote Metastore URI.
You can get the value for the Metastore Execution Mode from hive-site.xml.
The Metastore Execution Mode appears as the following property in hivesite.xml:
<property>
<name>hive.metastore.local</name>
<value>true</true>
</property>
Note: The hive.metastore.local property is deprecated in hive-site.xml
for Hive server versions 0.9 and above. If the hive.metastore.local
property does not exist but the hive.metastore.uris property exists, and
you know that the Hive server has started, you can set the connection to a
remote metastore.
CreateConnection
255
Option
Description
remoteMetastoreURI
The metastore URI used to access metadata in a remote metastore setup. For
a remote metastore, you must specify the Thrift server details.
Use the following connection URI:
thrift://<hostname>:<port>
Where
- <hostname> is name or IP address of the Thrift metastore server.
- <port> is the port on which the Thrift server is listening.
For example, enter: thrift://myhostname:9083/

You can get the value for the Remote Metastore URI from hive-site.xml. The
Remote Metastore URI appears as the following property in hive-site.xml:
<property>
<name>hive.metastore.uris</name>
<value>thrift://<n.n.n.n>:9083</value>
<description> IP address or fully-qualified domain
name and port of the metastore host</description>
</property>
stgDataCompressionCodecCla
ss
Codec class name that enables data compression and improves performance
on temporary staging tables.
stgDataCompressionCodecTyp
e
Hadoop compression library for a compression codec class name.
Related Topics:
256
Hive Connection Options

Use connection options to define a Hive connection.
To enter multiple options, separate them with a space.
The following table describes Hive connection options for infacmd isp CreateConnection and
UpdateConnection commands that you configure when you want to use the Hive connection:
Option
Description
connectionType
Required. Type of connection is HIVE.
name
~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < ,
> . ? /
relationalSourceAndTarget
Hive connection mode. Set this option to true if you want to use the connection
to access the Hive data warehouse. If you want to access Hive target, you need
to enable the same connection or another Hive connection to run the mapping
in the Hadoop cluster.
If you enable relational source and target, you must provide the
metadataDatabaseString option.
pushDownMode
Hive connection mode. Set this option to true if you want to use the connection
to run mappings in the Hadoop cluster.
If you enable the connection for pushdown mode, you must provide the options
to run the Informatica mappings in the Hadoop cluster.
CreateConnection
257
Option
Description
environmentSQL
SQL commands to set the Hadoop environment. In native environment type, the
Data Integration Service executes the environment SQL each time it creates a
connection to Hive metastore. If the Hive connection is used to run mappings in
the Hadoop cluster, the Data Integration Service executes the environment
SQL at the beginning of each Hive session.
The following rules and guidelines apply to the usage of environment SQL in
both the connection modes:
- Use the environment SQL to specify Hive queries.
- Use the environment SQL to set the classpath for Hive user-defined functions and
then use either environment SQL or PreSQL to specify the Hive user-defined
functions. You cannot use PreSQL in the data object properties to specify the
classpath. The path must be the fully qualified path to the JAR files used for userdefined functions. Set the parameter hive.aux.jars.path with all the entries in
infapdo.aux.jars.path and the path to the JAR files for user-defined functions.
- You can also use environment SQL to define Hadoop or Hive parameters that you
intend to use in the PreSQL commands or in custom queries.
If the Hive connection is used to run mappings in the Hadoop cluster, only the
environment SQL of the Hive connection is executed. The different environment
SQL commands for the connections of the Hive source or target are not
executed, even if the Hive sources and targets are on different clusters.
enableQuotes
258
Encloses all database reserved words in quotes. Default is false.
Properties to Access Hive as Source or Target

The following table describes the mandatory options for infacmd isp CreateConnection and
UpdateConnection commands that you configure when you want to use the Hive connection to access Hive
data:
Property
Description
metadataConnString
The JDBC connection URI used to access the metadata from the Hadoop
server.
The connection string uses the following format:
jdbc:hive://<hostname>:<port>/<db>
Where
- hostname is name or IP address of the machine on which the Hive server is
running.
- port is the port on which the Hive server is listening.
- db is the database to which you want to connect. If you do not provide the
database details, the Data Integration Service uses the default database details.
bypassHiveJDBCServer
JDBC driver mode. Enable this option to use the embedded JDBC driver
(embedded mode).
To use the JDBC embedded mode, perform the following tasks:
- Verify that Hive client and Informatica Services are installed on the same
machine.
- Configure the Hive connection properties to run mappings in the Hadoop cluster.
If you choose the non-embedded mode, you must configure the Data Access
Connection String.
The JDBC embedded mode is preferred to the non-embedded mode.
connectString
The connection string used to access data from the Hadoop data store. The
non-embedded JDBC mode connection string must be in the following format:
jdbc:hive://<hostname>:<port>/<db>
Where
- hostname is name or IP address of the machine on which the Hive server is
running.
- port is the port on which the Hive server is listening. Default is 10000.
- db is the database to which you want to connect. If you do not provide the
database details, the Data Integration Service uses the default database details.
CreateConnection
259
Properties to Run Mappings in the Hadoop Cluster

The following table describes the mandatory options for infacmd isp CreateConnection and
UpdateConnection commands that you configure when you want to use the Hive connection to run
Informatica mappings in the Hadoop cluster:
Property
Description
databaseName
Namespace for tables. Use the name default for tables that do not have
a specified database name.
defaultFSURI
The URI to access the default Hadoop Distributed File System.

The FS URI must be in the following format:
hdfs://<node name>:<port>
Where
- node name is the host name or IP address of the NameNode.
- port is the port on which the NameNode listens for remote procedure calls
(RPC).
jobTrackerURI
The service within Hadoop that submits the MapReduce tasks to specific
nodes in the cluster.
JobTracker URI must be in the following format:
<jobtrackername>:<port>
Where
- jobtrackername is the host name or IP address of the JobTracker.
- port is the port on which the JobTracker listens for remote procedure calls
(RPC).
hiveWarehouseDirectoryOnHDFS
The absolute HDFS file path of the default database for the warehouse,
which is local to the cluster. For example, the following file path specifies a
local warehouse:
/user/hive/warehouse
metastoreExecutionMode
Controls whether to connect to a remote metastore or a local metastore.

For a local metastore, you must specify the Metastore Database URI,
Driver, Username, and Password. For a remote metastore, you must
specify only the Remote Metastore URI.
metastoreDatabaseURI
The JDBC connection URI used to access the data store in a local
metastore setup. The URI must be in the following format:
jdbc:<datastore type>://<node name>:<port>/<database
name>
where
- node name is the host name or IP address of the data store.
- data store type is the type of the data store.
- port is the port on which the data store listens for remote procedure calls
(RPC).
- database name is the name of the database.
For example, the following URI specifies a local metastore that uses
MySQL as a data store:
jdbc:mysql://hostname23:3306/metastore
metastoreDatabaseDriver
260
Driver class name for the JDBC data store. For example, the following
class name specifies a MySQL driver:
com.mysql.jdbc.Driver
Property
Description
metastoreDatabaseUserName
The metastore database user name.
metastoreDatabasePassword
The password for the metastore user name.
remoteMetastoreURI
The metastore URI used to access metadata in a remote metastore setup.

For a remote metastore, you must specify the Thrift server details.
The URI must be in the following format:
thrift://<hostname>:<port>
Where
- hostname is name or IP address of the Thrift metastore server.
- port is the port on which the Thrift server is listening.
Related Topics:
CreateConnection
261
DB2 for z/OS Connection Options

Use DB2Z connection options to define the IBM for DB2 z/OS connection.
The following table describes DB2Z connection options for infacmd isp CreateConnection and
Option
Description
DataAccessConnectStri
ng
Connection string used to access data from the database.
EnvironmentSQL
CodePage
database or file.
ArraySize
Default is 25.
Compression
Optional. Compresses the data to decrease the amount of data to write over the
network. Default is false.
CorrelationID
Optional. Label to apply to a DB2 task or query to allow DB2 for z/OS to account for
the resource. Enter up to 8 bytes of alphanumeric characters.
EncyptionLevel
<database name>

Default is 1.
EncryptionType
Optional. Type of encryption. Enter one of the following values for the encryption type:
- None
- RC2
- DES
Default is None.
262
InterpretAsRows
Optional. Represent pacing size as a number of rows. If false, the pacing size
represents kilobytes. Default is false.
Location
Location of the PowerExchange listener node that can connect to the database. The
node is defined in the PowerExchange dbmover.cfg configuration file.
Option
Description
OffloadProcessing
Optional. Moves bulk data processing from the VSAM source to the Data Integration
Service machine.
Default is Auto.
PacingSize
Optional. Amount of data the source system can pass to the PowerExchange
Listener. Configure the pacing size if an external application, a database, or the Data
Integration Service node is a bottleneck. The lower the value, the faster the
performance.
Minimum value is 0. Enter 0 for maximum performance. Default is 0.
RejectFile
Optional. Enter the reject file name and path. Reject files contain rows that were not
written to the database.
WorkerThread
Optional. Number of threads that the Data Integration Service uses to process bulk
data when offload processing is enabled. For optimal performance, this value should
not exceed the number of available processors on the Data Integration Service
machine. Valid values are 1 through 64. Default is 0, which disables multithreading.
WriteMode

- CONFIRMWRITEON. Sends data to the PowerExchange Listener and waits for a
- CONFIRMWRITEOFF. Sends data to the PowerExchange Listener without waiting for a
success/no success response. Use this option when the target table can be reloaded if
an error occurs.
- ASYNCHRONOUSWITHFAULTT. Sends data to the PowerExchange Listener
Optional. Enables parallel processing when loading data into a table in bulk mode.
Used for Oracle. True or false. Default is true.
ConnectionPoolSize
Time

idle connection instances.
ConnectionPoolMinConn
ections
database connection. Set this value to be equal to or less than the idle connection
pool size. Default is 0.
Related Topics:
CreateConnection
263
IBM DB2 Connection Options

Use connection options to define the IBM DB2 connection.
The following table describes IBM DB2 connection options for infacmd isp CreateConnection and
264
Option
Description
PassThruEnabled
Optional. Enables pass-through security for the connection. When you enable passthrough security for a connection, the domain uses the client user name and password
to log into the corresponding database, instead of the credentials defined in the
connection object.
MetadataAccessConne
ctString
JDBC connection URL used to access metadata from the database.

jdbc:informatica:db2://<host name>:<port>;DatabaseName=<database name>
Option
Description
AdvancedJDBCSecurit
yOptions
Optional. Database parameters for metadata access to a secure database. Informatica

treats the value of the AdvancedJDBCSecurityOptions field as sensitive data and
encrypts the parameter string.
To connect to a secure database, include the following parameters:
- EncryptionMethod. Required. Indicates whether data is encrypted when transmitted over
the network. This parameter must be set to SSL.
- ValidateServerCertificate. Optional. Indicates whether Informatica validates the certificate
that is sent by the database server.
If this parameter is set to True, Informatica validates the certificate that is sent by the
database server. If you specify the HostNameInCertificate parameter, Informatica also
validates the host name in the certificate.
If this parameter is set to false, Informatica does not validate the certificate that is sent by
the database server. Informatica ignores any truststore information that you specify.
- HostNameInCertificate. Optional. Host name of the machine that hosts the secure
database. If you specify a host name, Informatica validates the host name included in the
connection string against the host name in the SSL certificate.
- TrustStore. Required. Path and file name of the truststore file that contains the SSL
certificate for the database.
- TrustStorePassword. Required. Password for the truststore file for the secure database.
Note: For a complete list of the secure JDBC parameters, see the DataDirect JDBC
documentation.
Informatica appends the secure JDBC parameters to the connection string. If you
include the secure JDBC parameters directly in the connection string, do not enter any
parameters in the AdvancedJDBCSecurityOptions field.
DataAccessConnectStri
ng
CodePage
database.
EnvironmentSQL
Enter the connection string in the following format:

<database name>
For example, ALTER SESSION SET CURRENT_SCHEMA=INFA_USR;

TransactionSQL
Optional. SQL commands to execute before each transaction. The Data Integration
Service executes the transaction SQL at the beginning of each transaction.
For example, SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;
Tablespace
Optional. The tablespace name of the database.
QuoteChar
Optional. The character that you will use for quotes in this connection.
The type of character used to identify special characters and reserved SQL keywords,
such as WHERE. The Data Integration Service places the selected character around
special characters and reserved SQL keywords. The Data Integration Service also
uses this character for the QuoteChar property. Default is 0.
CreateConnection
265
Option
EnableQuotes
Description
Optional. Select to enable quotes or not for this connection.
When enabled, the Data Integration Service places identifier characters around table,
view, schema, synonym, and column names when generating and executing SQL
against these objects in the connection. Use if the objects have mixed-case or
lowercase names. Valid values are True or False. Default is True.
connection pooling, the Data Integration Service stops all pooling activity. Valid values
are True or False. Default is True.
ConnectionPoolSize
minimum number of idle connection instances. Default is 15.
Time

idle connection instances. Default is 120.
ConnectionPoolMinCon
nections
size. Default is 0.
Related Topics:
266
IMS Connection Options

Use connection options to define an IMS connection.
The following table describes IMS connection options:
Option
Description
CodePage
Required. Code to read from or write to the database. Use the ISO code page name, such
as ISO-8859-6. The code page name is not case sensitive.
ArraySize
Optional. Determines the number of records in the storage array for the threads when the
worker threads value is greater than 0. Valid values are from 1 through 100000. Default is
25.
Compression
EncryptionLevel
Default is 1.
EncryptionType
- None
- RC2
- DES
Default is None.
InterpretAsRows
Location
CreateConnection
267
Option
Description
OffLoadProcessing
Optional. Moves bulk data processing from the source machine to the Data Integration
Service machine.
Default is Auto.
PacingSize
Optional. Slows the data transfer rate in order to reduce bottlenecks. The lower the value,
the greater the session performance. Minimum value is 0. Enter 0 for optimal
WorkerThread
Optional. Number of threads that the Data Integration Service uses to process bulk data
when offload processing is enabled. For optimal performance, this value should not
exceed the number of available processors on the Data Integration Service machine. Valid
values are 1 through 64. Default is 0, which disables multithreading.
WriteMode

- CONFIRMWRITEON. Sends data to the PowerExchange Listener and waits for a success/no
success response before sending more data.
- CONFIRMWRITEOFF. Sends data to the PowerExchange Listerner without waiting for a
error occurs.
- ASYNCHRONOUSWITHFAULTT. Sends data to the PowerExchangeListener
EnableConnectionP
ool
Default is false.
ConnectionPoolSize
Optional. Maximum number of idle connections instances that the Data Integration Service
maintains for a database connection. Set this value to be more than the minimum number
ConnectionPoolMax
IdleTime

connection instances can remain idle before the connection pool drops it. The connection
pool ignores the idletime when it does not exceed the minimum number of idle connection
instances. Default is 120.
ConnectionPoolMin
Connections
size. Default is 0.
Related Topics:
268
JDBC Connection Options

Use connection options to define a JDBC connection.
To enter multiple options, separate options with spaces. To enter a value that contains a space or other nonalphanumeric character, enclose the value in quotation marks.
CreateConnection
269
The following table describes JDBC connection options for infacmd isp CreateConnection and
Option
Description
JDBCDriverClassName
The Java class that you use to connect to the database.

The following list provides the driver class name that you can enter
for the applicable database type:
- DataDirect JDBC driver class name for Oracle:
com.informatica.jdbc.oracle.OracleDriver
- DataDirect JDBC driver class name for IBM DB2:
com.informatica.jdbc.db2.DB2Driver
- DataDirect JDBC driver class name for Microsoft SQL Server:
com.informatica.jdbc.sqlserver.SQLServerDriver
- DataDirect JDBC driver class name for Sybase ASE:
com.informatica.jdbc.sybase.SybaseDriver
- DataDirect JDBC driver class name for Informix:
com.informatica.jdbc.informix.InformixDriver
- DataDirect JDBC driver class name for MySQL:
com.informatica.jdbc.mysql.MySQLDriver
For more information about which driver class to use with specific
databases, see the vendor documentation.
MetadataConnString
The URL that you use to connect to the database.

The following list provides the connection string that you can enter
for the applicable database type:
- DataDirect JDBC driver for Oracle:
jdbc:informatica:oracle://
<hostname>:<port>;SID=<sid>
- DataDirect JDBC driver for IBM DB2:
jdbc:informatica:db2://
<hostname>:<port>;DatabaseName=<database name>
- DataDirect JDBC driver for Microsoft SQL Server:
jdbc:informatica:sqlserver://
<host>:<port>;DatabaseName=<database name>
- DataDirect JDBC driver for Sybase ASE:
jdbc:informatica:sybase://
- DataDirect JDBC driver for Informix:
jdbc:informatica:informix://
<host>:<port>;informixServer=<informix server
name>;databaseName=<dbName>
- DataDirect JDBC driver for MySQL:
jdbc:informatica:mysql://
For more information about the connection string to use for specific
databases, see the vendor documentation for the URL syntax.
EnvironmentSQL
Optional. SQL commands to set the database environment when you

connect to the database. The Data Integration Service executes the
connection environment SQL each time it connects to the database.
For example, ALTER SESSION SET
CURRENT_SCHEMA=INFA_USR;
Note: Enclose special characters in double quotation marks.
270
Option
Description
TransactionSQL
Optional. SQL commands to execute before each transaction. The

Data Integration Service executes the transaction SQL at the
beginning of each transaction.
For example, SET TRANSACTION ISOLATION LEVEL
SERIALIZABLE;
QuoteChar
Optional. The character that you will use for quotes in this
connection.
The type of character used to identify special characters and
reserved SQL keywords, such as WHERE. The Data Integration
Service places the selected character around special characters and
reserved SQL keywords. The Data Integration Service also uses this
character for the QuoteChar property. Default is DOUBLE_QUOTE.
EnableQuotes
Optional. Select to enable quotes or not for this connection.

When enabled, the Data Integration Service places identifier
characters around table, view, schema, synonym, and column
names when generating and executing SQL against these objects in
the connection. Use if the objects have mixed-case or lowercase
names. Valid values are True or False. Default is True.
Related Topics:
CreateConnection
271
LinkedIn Connection Options

Use connection options to define a LinkedIn connection.
The following table describes LinkedIn connection options for infacmd isp CreateConnection and
Option
Description
ConsumerKey
The API key that you get when you create the application in
LinkedIn. LinkedIn uses the key to identify the application.
ConsumerSecret
The Secret key that you get when you create the application in
LinkedIn. LinkedIn uses the secret to establish ownership of the
consumer key.
AccessToken
Access token that the OAuth Utility returns. The LinkedIn application
uses this token instead of the user credentials to access the
protected resources.
AccessSecret
Access secret that the OAuth Utility returns. The secret establishes
ownership of a token.
Related Topics:
272
Microsoft SQL Server Connection Options

Use connection options to define the Microsoft SQL Server connection.
The following table describes Microsoft SQL Server connection options for infacmd isp CreateConnection or
UpdateConnection:
Option
Description
UseTrustedConnection
Optional. The Integration Service uses Windows authentication to access the

Microsoft SQL Server database. The user name that starts the Integration Service
must be a valid Windows user with access to the Microsoft SQL Server database.
True or false. Default is false.
PassThruEnabled
Optional. Enables pass-through security for the connection. When you enable passthrough security for a connection, the domain uses the client user name and
password to log into the corresponding database, instead of the credentials defined
in the connection object.
MetadataAccessConnectSt
ring
JDBC connection URL to access metadata from the database.

jdbc:informatica:sqlserver://<host name>:<port>;DatabaseName=<database name>
CreateConnection
273
Option
Description
AdvancedJDBCSecurityOp
tions
Optional. Database parameters for metadata access to a secure database.

Informatica treats the value of the AdvancedJDBCSecurityOptions field as sensitive
data and encrypts the parameter string.
- EncryptionMethod. Required. Indicates whether data is encrypted when transmitted
over the network. This parameter must be set to SSL.
- ValidateServerCertificate. Optional. Indicates whether Informatica validates the
certificate that is sent by the database server.
If this parameter is set to True, Informatica validates the certificate that is sent by the
database server. If you specify the HostNameInCertificate parameter, Informatica also
validates the host name in the certificate.
If this parameter is set to false, Informatica does not validate the certificate that is
sent by the database server. Informatica ignores any truststore information that you
specify.
- HostNameInCertificate. Optional. Host name of the machine that hosts the secure
database. If you specify a host name, Informatica validates the host name included in
the connection string against the host name in the SSL certificate.
- TrustStore. Required. Path and file name of the truststore file that contains the SSL
certificate for the database.
- TrustStorePassword. Required. Password for the truststore file for the secure
database.
Note: For a complete list of the secure JDBC parameters, see the DataDirect JDBC
documentation.
Informatica appends the secure JDBC parameters to the connection string. If you
include the secure JDBC parameters directly to the connection string, do not enter
any parameters in the AdvancedJDBCSecurityOptions field.
DataAccessConnectString
Required. Connection string used to access data from the database.

<server name>@<database name>
DomainName
Optional. The name of the domain where Microsoft SQL Server is running.
PacketSize
Optional. Increase the network packet size to allow larger packets of data to cross
the network at one time.
CodePage
Required. Code to read from or write to the database. Use the ISO code page
name, such as ISO-8859-6. The code page name is not case sensitive.
OwnerName
Optional. The table owner name.
SchemaName
Optional. The name of the schema in the database. You must specify the schema
name for the Profiling Warehouse if the schema name is different from the
database user name. You must specify the schema name for the data object cache
database if the schema name is different from the database user name and if you
configure user-managed cache tables.
EnvironmentSQL
Optional. SQL commands to set the database environment when you connect to
the database. The Data Integration Service executes the connection environment
SQL each time it connects to the database.
274
Option
Description
TransactionSQL
Optional. SQL commands to execute before each transaction. The Data Integration
Service executes the transaction SQL at the beginning of each transaction.
For example, SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;
QuoteChar
The type of character used to identify special characters and reserved SQL
keywords, such as WHERE. The Data Integration Service places the selected
character around special characters and reserved SQL keywords. The Data
Integration Service also uses this character for the QuoteChar property. Default is
0.
EnableQuotes
Optional. Choose to enable quotes or not for this connection.

When enabled, the Data Integration Service places identifier characters around
table, view, schema, synonym, and column names when generating and executing
SQL against these objects in the connection. Use if the objects have mixed-case or
lowercase names. Valid values are True or False. Default is True.
connection pooling, the Data Integration Service stops all pooling activity. Valid
values are True or False. Default is True.
ConnectionPoolSize
ConnectionPoolMaxIdleTi
me

connection pool ignores the idletime when it does not exceed the minimum number
ConnectionPoolMinConnec
tions
Optional. Minimum number of idle connection instances that the pool maintains for
a database connection. Set this value to be equal to or less than the idle
connection pool size. Default is 0.
Related Topics:
CreateConnection
275
Netezza Connection Options

Use connection options to define a Netezza connection.
The following table describes the Netezza connection options for infacmd isp CreateConnection and
Option
Description
connectionString
Required. Name of the ODBC data source that you create to connect to the Netezza
database.
jdbcUrl
Required. JDBC URL that the Developer tool must use when it connects to the Netezza
database. Use the following format:
jdbc:netezza://<hostname>:<port>/<database name>
username
Required. User name with the appropriate permissions to access the Netezza database.
password
Required. Password for the database user name.
timeout
Required. Number of seconds that the Developer tool waits for a response from the Netezza
database before it closes the connection.
Related Topics:
276
OData Connection Options

Use connection options to define an OData connection.
The following table describes the OData connection options for infacmd isp CreateConnection and
Property
Description
URL
Required. OData service root URL that exposes the data that you want to read.
securityType
Optional. Security protocol that the Developer tool must use to establish a secure
connection with the OData server.
- None
- SSL
- TLS
CreateConnection
277
Property
trustStoreFileName
Description
Required if you enter a security type.
Name of the truststore file that contains the public certificate for the OData server.
trustStorePassword

Password for the truststore file that contains the public certificate for the OData server.
keyStoreFileName

Name of the keystore file that contains the private key for the OData server.
keyStorePassword

Password for the keystore file that contains the private key for the OData server.
Related Topics:
278
ODBC Connection Options

Use connection options to define the ODBC connection.
The following table describes ODBC connection options for infacmd isp CreateConnection and
Option
Description
PassThruEnabled
Optional. Enables pass-through security for the connection. When you

enable pass-through security for a connection, the domain uses the
client user name and password to log into the corresponding database,
instead of the credentials defined in the connection object.

<database name>
CodePage
Required. Code page used to read from a source database or write to a

target database or file.
EnvironmentSQL

For example, ALTER SESSION SET
CURRENT_SCHEMA=INFA_USR;
TransactionSQL
Optional. SQL commands to execute before each transaction. The Data

Integration Service executes the transaction SQL at the beginning of
each transaction.
SERIALIZABLE;
QuoteChar
The type of character used to identify special characters and reserved
SQL keywords, such as WHERE. The Data Integration Service places
the selected character around special characters and reserved SQL
keywords. The Data Integration Service also uses this character for the
QuoteChar property. Default is 4.
CreateConnection
279
Option
Description
ODBC Provider
Optional. The type of database to which the Data Integration Service

connects using ODBC. For pushdown optimization, specify the
database type to enable the Data Integration Service to generate native
database SQL. The options are as follows:
-
Other
Sybase
Microsoft_SQL_Server
Teradata
Netezza
Greenplum
Default is Other.
EnableQuotes

When enabled, the Data Integration Service places identifier characters
around table, view, schema, synonym, and column names when
generating and executing SQL against these objects in the connection.
Use if the objects have mixed-case or lowercase names. Valid values
are True or False. Default is False.
Optional. Enables connection pooling. When you enable connection

pooling, the connection pool retains idle connection instances in
memory. When you disable connection pooling, the Data Integration
Service stops all pooling activity. Valid values are True or False. Default
is True.
ConnectionPoolSize
Optional. Maximum number of idle connections instances that the Data

Integration Service maintains for a database connection. Set this value
to be more than the minimum number of idle connection instances.
Default is 15.
ConnectionPoolMaxIdleTime
Optional. Number of seconds that a connection exceeding the minimum

number of connection instances can remain idle before the connection
pool drops it. The connection pool ignores the idle time when it does not
exceed the minimum number of idle connection instances. Default is
120.
ConnectionPoolMinConnections
Optional. Minimum number of idle connection instances that the pool

maintains for a database connection. Set this value to be equal to or
less than the idle connection pool size. Default is 0.
Related Topics:
280
Oracle Connection Options

Use connection options to define the Oracle connection.
The following table describes Oracle connection options for infacmd isp CreateConnection and
Option
Description
PassThruEnabled
Optional. Enables pass-through security for the connection. When you

enable pass-through security for a connection, the domain uses the client
user name and password to log into the corresponding database, instead of
the credentials defined in the connection object.
MetadataAccessConnectString
JDBC connection URL used to access metadata from the database.

jdbc:informatica:oracle://<host_name>:<port>;SID=<database name>
CreateConnection
281
Option
Description
AdvancedJDBCSecurityOptions
Optional. Database parameters for metadata access to a secure database.

Informatica treats the value of the AdvancedJDBCSecurityOptions field as
sensitive data and encrypts the parameter string.
- EncryptionMethod. Required. Indicates whether data is encrypted when
transmitted over the network. This parameter must be set to SSL.
- ValidateServerCertificate. Optional. Indicates whether Informatica validates the
certificate that is sent by the database server.
If this parameter is set to true, Informatica validates the certificate that is sent
by the database server. If you specify the HostNameInCertificate parameter,
Informatica also validates the host name in the certificate.
If this parameter is set to false, Informatica does not validate the certificate that
is sent by the database server. Informatica ignores any truststore information
that you specify.
- HostNameInCertificate. Optional. Host name of the machine that hosts the
secure database. If you specify a host name, Informatica validates the host
name included in the connection string against the host name in the SSL
certificate.
- TrustStore. Required. Path and file name of the truststore file that contains the
SSL certificate for the database.
- TrustStorePassword. Required. Password for the truststore file for the secure
database.
Note: For a complete list of the secure JDBC parameters, see the DataDirect
JDBC documentation.
Informatica appends the secure JDBC parameters to the connection string. If
you include the secure JDBC parameters directly to the connection string, do
not enter any parameters in the AdvancedJDBCSecurityOptions field.

Enter the connection string in the following format from the TNSNAMES
entry:
<database name>
CodePage
Required. Code page used to read from a source database or write to a

target database or file.
EnvironmentSQL

TransactionSQL
Optional. SQL commands to execute before each transaction. The Data

Integration Service executes the transaction SQL at the beginning of each
transaction.
SERIALIZABLE;
EnableParallelMode
282
Optional. Enables parallel processing when loading data into a table in bulk
mode. Used for Oracle. True or false. Default is false.
Option
Description
QuoteChar
The type of character used to identify special characters and reserved SQL
keywords, such as WHERE. The Data Integration Service places the
selected character around special characters and reserved SQL keywords.
The Data Integration Service also uses this character for the QuoteChar
property. Default is 0.
EnableQuotes

When enabled, the Data Integration Service places identifier characters
around table, view, schema, synonym, and column names when generating
and executing SQL against these objects in the connection. Use if the
objects have mixed-case or lowercase names. Valid values are True or
False. Default is True.
Optional. Enables connection pooling. When you enable connection pooling,

the connection pool retains idle connection instances in memory. When you
disable connection pooling, the Data Integration Service stops all pooling
activity. Valid values are True or False. Default is True.
ConnectionPoolSize
Optional. Maximum number of idle connections instances that the Data

Integration Service maintains for a database connection. Set this value to be
more than the minimum number of idle connection instances. Default is 15.
ConnectionPoolMaxIdleTime
Optional. Number of seconds that a connection exceeding the minimum

number of connection instances can remain idle before the connection pool
drops it. The connection pool ignores the idletime when it does not exceed
the minimum number of idle connection instances. Default is 120.
ConnectionPoolMinConnections
Optional. Minimum number of idle connection instances that the pool

maintains for a database connection. Set this value to be equal to or less
than the idle connection pool size. Default is 0.
Related Topics:
CreateConnection
283
Salesforce Connection Options

Use connection options to define a Salesforce connection.
For example,
infacmd createConnection -dn DomainName -un Domain_UserName -pd Domain_Pwd -cn conname cid conname -ct SFDC -o userName=salesforceUserName password=salesforcePWD
serviceURL=https://login.salesforce.com/services/Soap/u/26.0
The following table describes Salesforce connection options for infacmd isp CreateConnection and
Option
Description
userName
Salesforce user name.
password
Password for the Salesforce user name. The password is case sensitive.
To access Salesforce outside the trusted network of your organization, you must
append a security token to your password to log in to the API or a desktop client.
To receive or reset your security token, log in to Salesforce and click Setup > My
Personal Information > Reset My Security Token.
serviceURL
URL of the Salesforce service that you want to access. In a test or development
environment, you might want to access the Salesforce Sandbox testing
environment. For more information about the Salesforce Sandbox, see the
Salesforce documentation.
Related Topics:
284
SAP Connection Options

Use connection options to define the SAP connection.
The following table describes SAP connection options for infacmd isp CreateConnection and
Option
Description
UserName
Required. SAP system user name.
Password
Required. Password for the user name.
HostName
Required. Host name of the SAP application.
ClientNumber
Required. SAP client number.
CreateConnection
285
Option
Description
SystemNumber
Required. SAP system number.
Language
Optional. SAP Logon language.
Related Topics:
Sequential Connection Options

Use SEQ connection options to define a connection to a sequential z/OS data set.
286
The following table describes SEQ connection options for infacmd isp CreateConnection and
Option
Description
CodePage
Required. Code to read from or write to the sequential file. Use the ISO code page
name, such as ISO-8859-6. The code page name is not case sensitive.
ArraySize
Default is 25.
Compression
Optional. Compresses the data to decrease the amount of data that Informatica
applications write over the network. True or false. Default is false.
EncryptionLevel
Default is 1.
EncryptionType
- None
- RC2
- DES
Default is None.
InterpretAsRows
Location
Location of the PowerExchange Listener node that can connect to the data source. The
OffLoadProcessing
Optional. Moves bulk data processing from the data source machine to the Data
Integration Service machine.
Default is Auto.
PacingSize
Optional. Slows the data transfer rate in order to reduce bottlenecks. The lower the
value, the greater the session performance. Minimum value is 0. Enter 0 for optimal
WorkerThread
CreateConnection
287
Option
WriteMode
Description
- CONFIRMWRITEON. Sends data to the Data Integration Service and waits for a
- CONFIRMWRITEOFF. Sends data to the Data Integration Service without waiting for a
error occurs.
- ASYNCHRONOUSWITHFAULTT. Sends data to the Data Integration Service
Default is false.
ConnectionPoolSize
ConnectionPoolMaxIdl
eTime

ConnectionPoolMinCo
nnections
size. Default is 0.
Related Topics:
288
Teradata Parallel Transporter Connection Options

Use connection options to define a Teradata PT connection.
The following table describes Teradata PT connection options for infacmd isp CreateConnection and
Option
Description
UserName
Required. Teradata database user name with the appropriate write

permissions to access the database.
Password
Required. Password for the Teradata database user name.
DriverName
Required. Name of the Teradata JDBC driver.
ConnectionString
Required. JDBC URL to fetch metadata.
TDPID
Required. Name or IP address of the Teradata database machine.
databaseName
Required. Teradata database name.

If you do not enter a database name, Teradata PT API uses the default
login database name.
DataCodePage
Optional. Code page associated with the database.

When you run a mapping that loads to a Teradata target, the code page
of the Teradata PT connection must be the same as the code page of the
Teradata target.
Default is UTF-8.
Tenacity
Optional. Number of hours that Teradata PT API continues trying to log

on when the maximum number of operations run on the Teradata
database.
Must be a positive, non-zero integer. Default is 4.
MaxSessions
Optional. Maximum number of sessions that Teradata PT API establishes

with the Teradata database.
CreateConnection
289
Option
Description
MinSessions
Optional. Minimum number of Teradata PT API sessions required for the

Teradata PT API job to continue.
Must be a positive integer between 1 and the Max Sessions value.
Default is 1.
Sleep
Optional. Number of minutes that Teradata PT API pauses before it

retries to log on when the maximum number of operations run on the
Teradata database.
useMetadataJdbcUrl
Optional.
Set this option to true to Indicate that the Teradata Connector for Hadoop
(TDCH) must use the JDBC URL that you specified in the connection
string.
Set this option to false to specify a different JDBC URL that TDCH must
use when it runs the mapping.
tdchJdbcUrl
Optional.
JDBC URL that TDCH must use when it runs the mapping.
dataEncryption
Optional.
Enables full security encryption of SQL requests, responses, and data on
Windows.
To enable data encryption on Unix, add the command
UseDataEncryption=Yes to the DSN in the odbc.ini file.
Related Topics:
290
Twitter Connection Options

Use connection options to define a Twitter connection.
The following table describes Twitter connection options for infacmd isp CreateConnection and
Option
Description
ConsumerKey
The consumer key that you get when you create the application in
Twitter. Twitter uses the key to identify the application.
ConsumerSecret
The consumer secret that you get when you create the Twitter
application. Twitter uses the secret to establish ownership of the
consumer key.
AccessToken
Access token that the OAuth Utility returns. Twitter uses this token
instead of the user credentials to access the protected resources.
AccessSecret
Access secret that the OAuth Utility returns. The secret establishes
ownership of a token.
Related Topics:
CreateConnection
291
Twitter Streaming Connection Options

Use connection options to define a Twitter Streaming connection.
The following table describes Twitter Streaming connection options for infacmd isp CreateConnection and
Option
HoseType
Description
Streaming API methods. You can specify the following methods:
- Filter. The Twitter statuses/filter method returns public
statuses that match the search criteria.
- Sample. The Twitter statuses/sample method returns a random
sample of all public statuses.
UserName
Twitter user screen name.
Password
Twitter password.
Related Topics:
292
VSAM Connection Options

Use connection options to define a VSAM connection.
The following table describes VSAM connection options for infacmd isp CreateConnection and
Option
Description
CodePage
Required. Code to read from or write to the VSAM file. Use the ISO code page name,
such as ISO-8859-6. The code page name is not case sensitive.
ArraySize
Default is 25.
Compression
CreateConnection
293
Option
Description
EncryptionLevel
Default is 1.
EncryptionType
- None
- RC2
- DES
Default is None.
InterpretAsRows
Location
Location of the PowerExchange listener node that can connect to VSAM. The node is
defined in the PowerExchange dbmover.cfg configuration file.
OffLoadProcessing
Optional. Moves bulk data processing from the VSAM source to the Data Integration
Service machine.
Default is Auto.
PacingSize
Optional. Slows the data transfer rate in order to reduce bottlenecks. The lower the
value, the greater the session performance. Minimum value is 0. Enter 0 for optimal
WorkerThread
WriteMode

- CONFIRMWRITEON. Sends data to the Data Integration Service and waits for a
- CONFIRMWRITEOFF. Sends data to the Data Integration Service without waiting for a
error occurs.
- ASYNCHRONOUSWITHFAULTT. Sends data to the Data Integration Service
294
Default is false.
ConnectionPoolSize
Option
Description
ConnectionPoolMaxIdl
eTime

ConnectionPoolMinCo
nnections
size. Default is 0.
Related Topics:
Web Content-Kapow Katalyst Connection Options

Use connection options to define a Web Content-Kapow Katalyst connection.
CreateConnection
295

The following table describes Web Content-Kapow Katalyst connection options for infacmd isp
CreateConnection and UpdateConnection commands:
Option
Description
ManagementConsoleURL
URL of the Local Management Console where the robot is uploaded.

The URL must start with http or https. For example, http://localhost:
50080.
RQLServicePort
The port number where the socket service listens for the RQL service.
Enter a value from 1 through 65535. Default is 50000.
Username
User name required to access the Local Management Console.
Password
Password to access the Local Management Console.
Related Topics:
296
CreateDARepositoryContents
Creates content for a Data Analyzer repository. You add repository content when you create the Reporting
Service or delete the repository content. You cannot create content for a repository that already includes
content.
The infacmd isp CreateDARepositoryContents command uses the following syntax:
<-initialAdmin|-ia> initial_administrator
The following table describes infacmd isp CreateDARepositoryContents options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
-pd
password
precedence.
297
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-ServiceName
service_name
Required. Name of the service for which you want to create

content.
initial_administrator
Required. Name of the administrator of the Reporting Service.
-hp
ResilienceTimeout
-sn
-initialAdmin
-ia
CreateFolder
Creates a folder in the domain. When you create a folder, infacmd creates the folder in the domain or folder
you specify.
You can use folders to organize objects and to manage security. Folders can contain nodes, services, grids,
licenses, and other folders.
The infacmd isp CreateFolder command uses the following syntax:
CreateFolder
298
<-FolderName|-fn> folder_name
<-FolderPath|-fp> full_folder_path
[<-FolderDescription|-fd> description_of_folder]
The following table describes infacmd isp CreateFolder options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-FolderName
folder_name
Required. Name of the folder. Folder names must be unique

within a folder or the domain. It cannot contain spaces or
exceed 79 characters in length.
-hp
-ResilienceTimeout
-fn
CreateFolder
299
Option
Argument
Description
-FolderPath
full_folder_path
Required. Full path, excluding the domain name, where you

want to create the folder. Must be in the following format:
-fp
-FolderDescription
description_of_folder
-fd
Optional. Description of the folder. If the folder description

contains spaces or other non-alphanumeric characters,
enclose it in quotation marks.
CreateGrid
Creates a grid in the domain and assigns nodes to the grid. Create a grid to distribute jobs to service
processes running on nodes in the grid.
The infacmd isp CreateGrid command uses the following syntax:
CreateGrid
<-GridName|-gn> grid_name
<-NodeList|-nl> node1 node2 ...
The following table describes infacmd isp CreateGrid options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

300
Option
Argument
Description
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-GridName
grid_name
Required. Name of the grid.
node1 node2 ...
Required. Names of the nodes you want to assign to the grid.
full_folder_path

in which you want to create the grid. Must be in the following
format:
-hp
-ResilienceTimeout
-gn
-NodeList
-nl
-FolderPath
-fp
CreateGrid
301
CreateGroup
Creates a group in the native security domain. You can assign roles, permissions, and privileges to a group
in the native or an LDAP security domain. The roles, permissions, and privileges assigned to the group
determines the tasks that users in the group can perform within the domain.
The infacmd isp CreateGroup command uses the following syntax:
CreateGroup
[<-GroupDescription|-ds> group_description]
The following table describes infacmd isp CreateGroup options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
-pd
302
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-GroupName
group_name
Required. Name of the group. The group name is not case

sensitive and can be between 1 and 80 characters long. It
cannot include a tab, newline character, or the following
special characters:
-hp
-ResilienceTimeout
-gn
, + " \ < > ; / * % ?

The name can include an ASCII space character except for
the first and last character. All other space characters are not
allowed.
-GroupDescription
group_description
-ds
Optional. Description of the group. To enter a description that

The description cannot include the following special
characters:
< >
CreateIntegrationService
Creates a PowerCenter Integration Service in a domain.
By default, the PowerCenter Integration Service is enabled when you create it.
The infacmd isp CreateIntegrationService command uses the following syntax:
303
<<-NodeName|-nn> node_name|<-GridName|-gn> grid_name>
[<-BackupNodes|-bn> node1 node2 ...]
[<-RepositoryUser|-ru> repository_user]
[<-RepositoryPassword|-rp> repository_password]
[<-ServiceDisable|-sd>]
[<-ServiceOptions|-so> option_name=value ...]
[<-ServiceProcessOptions|-po> option_name=value ...]
[<-EnvironmentVariables|-ev> name=value ...]
[<-LicenseName|-ln> license_name]
Note: For infacmd isp CreateIntegrationService, you must not use the -ru, -rp, and the -rsdn options in
Kerberos authentication. If you use these options in Kerberos mode, the command will fail.
The following table describes infacmd isp CreateIntegrationService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

304
Option
Argument
Description
-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

authentication, the default is the user realm specified
-Gateway
-hp
gateway_host1:port
gateway_host2:port
...
-ResilienceTimeout

-re
timeout_period_in_second
s

-ServiceName
service_name
Required. Name of the PowerCenter Integration

Service.
-sn

name cannot have leading or trailing spaces, include
carriage returns or tabs, exceed 79 characters, or
contain the following characters:
/ * ? < > " |
-FolderPath
-fp
full_folder_path

folder in which you want to create the Integration
Service. Must be in the following format:
305
Option
Argument
Description
-NodeName
node_name
Required if you do not specify the grid name. Name of

the node where you want the PowerCenter Integration
Service process to run. If the PowerCenter
environment is configured for high availability, this
option specifies the name of the primary node.
-nn
To apply changes, restart the Integration Service.

-GridName
grid_name
-gn
Required if you do not specify the node name. Name

of the grid where you want the PowerCenter
Integration Service process to run.
To apply changes, restart the PowerCenter Integration
Service.
-BackupNodes
node1 node2 ...

Required. Name of the PowerCenter Repository

Service that the PowerCenter Integration Service
depends on.
-bn
-RepositoryService
-rs
To enter a name that contains a space or other nonalphanumeric character, enclose the name in
quotation marks.
Service.
-RepositoryUser
repository_user
-ru
Required for native or LDAP authentication. User

name used to connect to the PowerCenter repository.
quotation marks.
Service.
-RepositoryPassword
repository_password
-rp
Required for native or LDAP authentication. User

password. You can set a password with the -rp option
or the environment variable
INFA_REPOSITORY_PASSWORD. If you set a
the -rp option takes precedence.
Service.
RepositoryUserSecurityD
omain
repository_user_security_
domain
-rsdn
-ServiceDisable
The security domain name is case sensitive. If you do

not specify this option, the command sets the
repository user security domain to native.
-
-sd
306
Required for LDAP. Optional if the domain uses native

authentication. Name of the security domain to which
the PowerCenter repository user belongs.
Optional. Creates a disabled service. You must enable

the service before you can run it.
Option
Argument
Description
-ServiceOptions
option_name=value
Optional. Service properties that define how the

PowerCenter Integration Service runs.
option_name=value
Optional. Service process properties for the

PowerCenter Integration Service. In a grid or multinode environment, infacmd applies these properties to
the primary node, grid, and backup node.
name=value
Optional. Specify environment variables as

PowerCenter Integration Service process options. You
may want to include additional variables that are
unique to your PowerCenter environment.
-so
ServiceProcessOptions
-po
-EnvironmentVariables
-ev
To apply changes, restart the node.

-LicenseName
license_name
-ln
Required if you create an enabled service. Name of

the license you want to assign to the PowerCenter
Integration Service.
Service.
Integration Service Options

Enter Integration Service options in the following format:
infacmd CreateIntegrationService ... -so option_name=value option_name=value ...
The following table describes Integration Service options:
Option
Description
$PMFailureEmailUser
Optional. Email address of the user to receive email when a

session fails to complete. To enter multiple addresses on
Windows, use a distribution list. To enter multiple addresses on
UNIX, separate them with a comma.
$PMSessionErrorThreshold
Optional. Number of non-fatal errors the Integration Service

allows before failing the session. Default is 0 (non-fatal errors do
not cause the session to stop).
$PMSessionLogCount
Optional. Number of session logs the Integration Service

archives for the session. Minimum value is 0. Default is 0.
$PMSuccessEmailUser
Optional. Email address of the user to receive email when a

session completes successfully. To enter multiple addresses on
Windows, use a distribution list. To enter multiple addresses on
UNIX, separate them with a comma.
$PMWorkflowLogCount
Optional. Number of workflow logs the Integration Service

archives for the workflow. Minimum value is 0. Default is 0.
307
Option
Description
AggregateTreatNullAsZero
Optional. Treats nulls as zero in Aggregator transformations.

Default is No.
AggregateTreatRowAsInsert
Optional. Performs aggregate calculations before flagging

records for insert, update, delete, or reject in Update Strategy
expressions. Default is No.
ClientStore
Optional. Enter the value for ClientStore using the following

syntax:
<path>/<filename>
For example:
./Certs/client.keystore
CreateIndicatorFiles
Optional. Creates indicator files when you run a workflow with a

flat file target. Default is No.
DataMovementMode
Optional. Mode that determines how the Integration Service

handles character data:
- ASCII
- Unicode
Default is ASCII.
DateDisplayFormat
Optional. Date format the Integration Service uses in log entries.

Default is DY MON DD HH 24:MI:SS YYYY.
DateHandling40Compatibility
Optional. Handles dates as in PowerCenter 1.0/PowerMart 4.0.

Default is No.
DeadlockSleep
Optional. Number of seconds before the Integration Service

retries writing to a target on database deadlock. Minimum value
is 0. Maximum value is 2,147,483,647. Default is 0 (retry the
target write immediately).
ErrorSeverityLevel
Optional. Minimum level of error logging for the Integration

Service logs:
- Fatal
- Error
- Warning
- Info
- Trace
- Debug
Default is Info.
ExportSessionLogLibName
308
Optional. Name of an external library file to write session log

messages.
Option
Description
FlushGMDWrite
Required if you enable session recovery. Flushes session

recovery data for the recovery file from the operating system
buffer to the disk. Specify one of the following levels:
- Auto. Flushes recovery data for all real-time sessions with a JMS
or WebSphere MQ source and a non-relational target.
- Yes. Flushes recovery data for all sessions.
- No. Does not flush recovery data. Select this option if you have
highly available external systems or if you need to optimize
performance.
Default is Auto.
HttpProxyDomain
Optional. Domain for authentication.
HttpProxyPassword
Required if the proxy server requires authentication. Password

for the authenticated user.
HttpProxyPort
Optional. Port number of the HTTP proxy server.
HttpProxyServer
Optional. Name of the HTTP proxy server.
HttpProxyUser
Required if the proxy server requires authentication.

Authenticated user name for the HTTP proxy server.
IgnoreResourceRequirements
Optional. Ignores task resource requirements when distributing

tasks across the nodes of a grid. Default is Yes.
JCEProvider
Optional. JCEProvider class name to support NTLM

authentication.
For example:
com.unix.crypto.provider.UnixJCE.
JoinerSourceOrder6xCompatibility
Optional. Processes master and detail pipelines sequentially as

in PowerCenter versions prior to 7.0. Default is No.
LoadManagerAllowDebugging
Optional. Allows you to use this Integration Service to run

debugger sessions from the Designer. Default is Yes.
LogsInUTF8
Optional. Writes all logs using the UTF-8 character set. Default
is Yes (Unicode) or No (ASCII).
MSExchangeProfile
Optional. Microsoft Exchange profile used by the Service Start

Account to send post-session email.
MaxLookupSPDBConnections
Optional. Maximum number of connections to a lookup or stored

procedure database when you start a session. Minimum value is
0. Default is 0.
MaxMSSQLConnections
Optional. Maximum number of connections to a Microsoft SQL

Server database when you start a session. Minimum value is
100. Maximum value is 2,147,483,647. Default is 100.
MaxResilienceTimeout
Optional. Maximum amount of time in seconds that the service

holds on to resources for resilience purposes. Default is 180.
309
Option
Description
MaxSybaseConnections
Optional. Maximum number of connections to a Sybase

database when you start a session. Minimum value is 100.
Maximum value is 2,147,483,647. Default is 100.
NumOfDeadlockRetries
Optional. Number of times the Integration Service retries writing

to a target on a database deadlock. Minimum value is 10.
Maximum value is 1,000,000,000. Default is 10.
OperatingMode
Optional. Operating mode for the Integration Service:

- Normal
- Safe
Default is Normal.
OperatingModeOnFailover
Optional. Operating mode for the Integration Service when the

service process fails over:
- Normal
- Safe
Default is Normal.
OutputMetaDataForFF
Optional. Writes column headers to flat file targets. Default is

No.
PersistRuntimeStatsToRepo
Optional. Level of run-time information stored in the repository.

Specify one of the following levels:
- None. Integration Service does not store any session or workflow
run-time information in the repository.
- Normal. Integration Service stores workflow details, task details,
session statistics, and source and target statistics in the
repository.
- Verbose. Integration Service stores workflow details, task details,
session statistics, source and target statistics, partition details,
and performance details in the repository.
Default is Normal.
310
Pmserver3XCompatibility
Optional. Handles Aggregator transformations as the PowerMart

Server did in PowerMart 3.5. Default is No.
RunImpactedSessions
Optional. Runs sessions that are impacted by dependency

updates. Default is No.
ServiceResilienceTimeout
Optional. Amount of time in seconds that the service tries to

establish or reestablish a connection to another service. Default
is 180.
StoreHAPersistenceInDB
Optional. Stores process state information in persistence

database tables in the associated PowerCenter repository
database. Default is no.
TimestampWorkflowLogMessages
Optional. Appends a timestamp to messages written to the

workflow log. Default is No.
TreatCharAsCharOnRead
Optional. Keeps trailing spaces when reading SAP or

PeopleSoft CHAR data. Default is Yes.
Option
Description
TreatDBPartitionAsPassThrough
Optional. Uses pass-through partitioning for non-DB2 targets

when the partition type is Database Partitioning. Default is No.
TreatNullInComparisonOperatorsAs
Optional. Determines how the Integration Service evaluates null

values in comparison operations:
- Null
- Low
- High
Default is Null.
TrustStore
Optional. Enter the value for TrustStore using the following

syntax:
<path>/<filename>
For example:
./Certs/trust.keystore
UseOperatingSystemProfiles
Optional. Enables use of operating system profiles. Use this

option if the Integration Service runs on UNIX.
ValidateDataCodePages
Optional. Enforces data code page compatibility. Default is Yes.
WriterWaitTimeOut
Optional. In target-based commit mode, the amount of time in

seconds the writer remains idle before it issues a commit.
Minimum value is 60. Maximum value is 2,147,483,647. Default
is 60.
XMLWarnDupRows
Optional. Writes duplicate row warnings and duplicate rows for

XML targets to the session log. Default is Yes.
Integration Service Process Options

Enter service process options in the following format:
infacmd CreateIntegrationService ... -po option_name=value option_name=value ...
The following table describes Integration Service process options:
Option
Description
$PMBadFileDir
Optional. Default directory for reject files. It cannot include the following special
characters:
*?<>"|,
Default is $PMRootDir/BadFiles.
$PMCacheDir
Optional. Default directory for index and data cache files. It cannot include the
following special characters:
*?<>"|,
Default is $PMRootDir/Cache.
311
Option
Description
$PMExtProcDir
Optional. Default directory for external procedures. It cannot include the following
special characters:
*?<>"|,
Default is $PMRootDir/ExtProc.
$PMLookupFileDir
Optional. Default directory for lookup files. It cannot include the following special
characters:
*?<>"|,
Default is $PMRootDir/LkpFiles.
$PMRootDir
Optional. Root directory accessible by the node. It cannot include the following
special characters:
*?<>"|,
Default is C:\Informatica\PowerCenter8.6\server\infa_shared.
$PMSessionLogDir
Optional. Default directory for session logs. It cannot include the following special
characters:
*?<>"|,
Default is $PMRootDir/SessLogs.
$PMSourceFileDir
Optional. Default directory for source files. It cannot include the following special
characters:
*?<>"|,
Default is $PMRootDir/SrcFiles.
$PMStorageDir
Optional. Default directory for run-time files. It cannot include the following special
characters:
*?<>"|,
Default is $PMRootDir/Storage.
$PMTargetFileDir
Optional. Default directory for target files. It cannot include the following special
characters:
*?<>"|,
Default is $PMRootDir/TgtFiles.
$PMTempDir
Optional. Default directory for temporary files. It cannot include the following special
characters:
*?<>"|,
Default is $PMRootDir/Temp.
$PMWorkflowLogDir
Optional. Default directory for workflow logs. It cannot include the following special
characters:
*?<>"|,
Default is $PMRootDir/WorkflowLogs.
312
Codepage_ID
Required. Code page ID number for the Integration Service process.
JVMClassPath
Optional. Java SDK classpath.
Option
Description
JVMMaxMemory
Optional. Maximum amount of memory the Java SDK uses during a PowerCenter
session. Default is 64 MB.
JVMMinMemory
Optional. Minimum amount of memory the Java SDK uses during a PowerCenter
session. Default is 32 MB.
CreateMMService
Creates a Metadata Manager Service in the domain. By default, the Metadata Manager Service is disabled
when you create it. Run infacmd EnableService to enable the Metadata Manager Service.
The infacmd isp CreateMMService command uses the following syntax:
CreateMMService
<-ServiceOptions|-so> option_name=value ...>
The following table describes infacmd isp CreateMMService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
CreateMMService
313
Option
Argument
Description
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port

-re
ds

-ServiceName
service_name
-hp
-ResilienceTimeout
-sn
Required. Name of the Metadata Manager Service.

the domain. The name cannot have contain spaces, include
carriage returns or tabs, exceed 79 characters, or contain the
following characters:
/ * ? < > " |
-NodeName
node_name
Required. Name of the node where you want the Metadata

Manager application to run.
option_name=value
Optional. Service properties that define how the Metadata

Manager Service runs.
license_name
Required. Name of the license you want to assign to the

Metadata Manager Service.
full_folder_path

in which you want to create the Metadata Manager Service.
Must be in the following format:
-nn
-ServiceOptions
-so
-LicenseName
-ln
-FolderPath
-fp
314
Metadata Manager Service Options

Enter Metadata Manager Service options in the following format:
infacmd isp CreateMMService ... -so option_name=value option_name=value ...
The following table describes the Metadata Manager Service options:
Option
Description
AgentPort
Required. Port number for the Metadata Manager Agent. The agent uses this
port to communicate with metadata source repositories. Default is 10251.
CodePage
Required. Code page description for the Metadata Manager repository. To enter
a code page description that contains a space or other non-alphanumeric
ConnectString
Required. Native connect string for the Metadata Manager repository database.
DBUser
Required. User account for the Metadata Manager repository database.
DBPassword
Required. Password for the Metadata Manager repository database user. User
password. You can set a password with the -so option or the environment
variable INFA_DEFAULT_DATABASE_PASSWORD. If you set a password with
both methods, the password set with the -so option takes precedence.
DatabaseHostname
Required. Host name for the Metadata Manager repository database.
DatabaseName
Required. Full service name or SID for Oracle databases. Service name for IBM
DB2 databases. Database name for Microsoft SQL Server database.
DatabasePort
Required. Port number for the Metadata Manager repository database.
DatabaseType
Required. Type of database for the Metadata Manager repository.
ErrorSeverityLevel
Optional. Level of error messages written to the Metadata Manager Service log.
Default is ERROR.
FileLocation
Required. Location of the files used by the Metadata Manager application.
JdbcOptions
Optional. Additional JDBC options.

You can use this property to specify the following information:
-
Backup server location

Oracle Advanced Security Option (ASO) parameters
Microsoft SQL Server authentication parameters
Additional JDBC parameters when secure communication is enabled for the
Metadata Manager repository database
For more information about these parameters, see the Informatica Application
Service Guide.
MaxConcurrentRequests
Optional. Maximum number of request processing threads available, which

determines the maximum number of client requests that Metadata Manager can
handle simultaneously. Default is 100.
MaxHeapSize
Optional. Amount of RAM in megabytes allocated to the Java Virtual Manager

(JVM) that runs Metadata Manager. Default is 512.
CreateMMService
315
Option
Description
MaxQueueLength
Optional. Maximum queue length for incoming connection requests when all
possible request processing threads are in use by the Metadata Manager
application. Default is 500.
MaximumActiveConnections
Optional. Number of active connections to the Metadata Manager repository

database available. The Metadata Manager application maintains a connection
pool for connections to the repository database. Default is 20.
MaximumWaitTime
Optional. Amount of time in seconds that Metadata Manager holds database

connection requests in the connection pool. Default is 180.
MetadataTreeMaxFolderChilds
Optional. Number of child objects that appear in the Metadata Manager

metadata catalog for any parent object. Default is 100.
ODBCConnectionMode
Connection mode the Integration Service uses to connect to metadata sources

and the Metadata Manager repository when loading resources. Value can be
true or false.
You must set this property to True if the Integration Service runs on a UNIX
machine and you want to load metadata from a Microsoft SQL Server database
or if you use a Microsoft SQL Server database for the Metadata Manager
repository.
OracleConnType
Required if you select Oracle for the DatabaseType. Oracle connection type.
You can enter one of the following options:
- OracleSID
- OracleServiceName
316
PortNumber
Required. Port number the Metadata Manager application runs on. Default is
10250.
StagePoolSize
Optional. Maximum number of resources that Metadata Manager can load

simultaneously. Default is 3.
TablespaceName
Tablespace name for the Metadata Manager repository on IBM DB2.
TimeoutInterval
Optional. Amount of time in minutes that Metadata Manager holds a failed

resource load in the load queue. Default is 30.
URLScheme
Required. Indicates the security protocol that you configure for the Metadata
Manager application: HTTP or HTTPS.
keystoreFile
Required if you use HTTPS. Keystore file that contains the keys and certificates
required if you use the SSL security protocol with the Metadata Manager
application.
CreateOSProfile
Creates an operating system profile in the domain. Before you run workflows that use operating system
profiles, you must configure the PowerCenter Integration Service to use operating system profiles.
The infacmd isp CreateOSProfile command uses the following syntax:
CreateOSProfile
<-OSProfileName|-on> OSProfile_name
<-SystemName|-sn> system_username
[<-IntegrationServiceProcessOptions|-po> option_name=value ...
[<-EnvironmentVariables|-ev> name=value ...]
The following table describes infacmd isp CreateOSProfile options and arguments:
Option
Argument
Description
-DomainName
domain_name

can set the domain name with the -dn option or the
user_name

precedence.
-dn
-UserName
-un

-Password
-pd
password

CreateOSProfile
317
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:p
ort
gateway_host2:p
ort ...

domain.
-re
timeout_period_i
n_seconds

attempts to establish or reestablish a connection to
the domain. If you omit this option, infacmd uses
the timeout value specified in the
used.
-OSProfileName
OSProfile_name
Required. Name of the operating system profile.

The operating system profile name can be up to 80
characters. It cannot include spaces or the
-hp
-ResilienceTimeout
-on
\ / : * ? " < > | [ ] = + ; ,

-SystemName
system_usernam
e
Required. Name of an operating system user that

exists on the machines where the Integration
Service runs. The Integration Service runs
workflows using the system access of the system
user defined for the operating system profile.
-po
option_name=val
ue
Optional. Service process properties that define

how the Integration Service runs.
-EnvironmentVariables
name=value
Optional. Name and value of environment variables

used by the Integration Service at run time.
-sn
-IntegrationServiceProcessOptions
-ev
Integration Service Process Options for Operating System Profiles

Enter Integration Service process options in the following format:
infacmd CreateOSProfile ... -po option_name=value option_name=value ...
318
The following table describes Integration Service process options:
Option
Description
$PMBadFileDir
Optional. Directory for reject files. It cannot include the following special characters:
*?<>"|,
Default is $PMRootDir/BadFiles.
$PMCacheDir
Optional. Directory for index and data cache files. It cannot include the following
special characters:
*?<>"|,
Default is $PMRootDir/Cache.
$PMExtProcDir
Optional. Directory for external procedures. It cannot include the following special
characters:
*?<>"|,
Default is $PMRootDir/ExtProc.
$PMLookupFileDir
Optional. Directory for lookup files. It cannot include the following special
characters:
*?<>"|,
Default is $PMRootDir/LkpFiles.
$PMRootDir
Optional. Root directory accessible by the node. It cannot include the following
special characters:
*?<>"|,
Default is C:\Informatica\PowerCenter\server\infa_shared.
$PMSessionLogDir
Optional. Directory for session logs. It cannot include the following special
characters:
*?<>"|,
Default is $PMRootDir/SessLogs.
$PMSourceFileDir
Optional. Directory for source files. It cannot include the following special
characters:
*?<>"|,
Default is $PMRootDir/SrcFiles.
$PMStorageDir
Optional. Directory for run-time files. It cannot include the following special
characters:
*?<>"|,
Default is $PMRootDir/Storage.
$PMTargetFileDir
Optional. Directory for target files. It cannot include the following special characters:
*?<>"|,
Default is $PMRootDir/TgtFiles.
$PMTempDir
Optional. Directory for temporary files. It cannot include the following special
characters:
*?<>"|,
Default is $PMRootDir/Temp.
CreateOSProfile
319
CreateReportingService
Creates a Reporting Service in the domain. Run infacmd isp EnableService to enable the Reporting Service.
The infacmd isp CreateReportingService command uses the following syntax:
<-ServiceOptions|-so> option_name=value ...
<-ReportingSource|-rs> option_name=value ...
[<-LineageService|-ls> option_name=value ...]
The following table describes infacmd isp CreateReportingService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password
-pd
320

Option
Argument
Description
-SecurityDomain
security_domain

case sensitive.
-sdn

-Gateway
-hp
gateway_host1:port
gateway_host2:port
...
-ResilienceTimeout

-re
s

-ServiceName
service_name
Required. Name of the Reporting Service.
-sn

within the domain. The name cannot have leading or
trailing spaces, include carriage returns or tabs,
exceed 79 characters, or contain the following
characters:
/ * ? < > " |
-NodeName
node_name
Required. Name of the node where you want the

Reporting Service process to run.
license_name
Required. Name of the license you want to assign to

the ReportingService.
full_folder_path

folder in which you want to create the Reporting
-nn
-LicenseName
-ln
-FolderPath
-fp
-ServiceOptions
-so
option_name=value
Required. Service properties that define how the

Reporting Service runs.
321
Option
Argument
Description
-ReportingSource
option_name=value
Required. Specify the name and type of the data

source.
option_name=value
Optional. Lineage properties required to perform

lineage analysis for data in Data Analyzer.
-rs
-LineageService
-ls
Reporting Service Options

Enter Reporting Service options in the following format:
infacmd CreateReportingService ... -so option_name=value option_name=value ...
The following table describes Reporting Service options:
Option
Description
AdditionalJdbcParams
Optional. Enter additional JDBC options. Use this option to specify

character encoding or the location of a server if you are using a database
server that is highly available such as Oracle RAC.
DatabaseDriver
Required. JDBC driver that the Reporting Service uses to connect to the
Data Analyzer repository database.
DatabaseHost
Required. Name of the machine that hosts the database server.
DatabaseName
Required. Full service name or SID for Oracle databases. Service name for
IBM DB2 databases. Database name for Microsoft SQL Server or Sybase
ASE databases. Use DatabaseNameInterpretation option to specify
whether the DatabaseName option contains a service name, SID, or
database name.
DatabaseNameInterpretation
Required if the DatabaseName option contains a full Oracle service name.

Type of DatabaseName option. You can use the following values:
- DatabaseName. The DatabaseName option contains a database name for
Microsoft SQL Server or Sybase ASE databases, or a service name for IBM
DB2 databases.
- OracleSID. The DatabaseName option contains an Oracle SID.
- OracleServiceName. The DatabaseName option contains a full Oracle
service name.
By default, infacmd uses DatabaseName for all non-Oracle databases.
322
DatabasePassword
Required. Data Analyzer repository database password corresponding to

the database user. You can set a password with the -so option or the
environment variable INFA_DEFAULT_DATABASE_PASSWORD. If you
set a password with both methods, the password set with the -so option
takes precedence.
DatabasePort
Required. Port number for the repository database.
Option
Description
DatabaseTablespaceName
Required if you choose an IBM DB2 database. Tablespace name for IBM
DB2 repositories. When you specify the tablespace name, the Reporting
Service creates all repository tables in the same tablespace.
DatabaseUser
Required. User account for the repository database.
DatasourceDriver
Optional. The driver that the Reporting Service uses to connect to the data
source.
DatasourcePassword
Required. Password corresponding to the data source user. You can set a
password with the -so option or the environment variable
INFA_PASSWORD. If you set a password with both methods, the
password set with the -so option takes precedence.
DatasourceTestTable
Required. Test table that the Reporting Service uses to verify the
connection to the data source.
DatasourceURL
Required. JDBC connection string that the Reporting Service uses to

connect to the data source.
DatasourceUser
Required. User account for the data source database.
HttpPort
Required if you do not use the SslPort option. TCP port that the Reporting
Service uses.
SslPort
Required if you do not use the HttpPort option. SSL port that the Reporting
Service uses for secure connections.
DataSourceAdvancedMode
Edit mode that determines where you can edit Datasource properties.
When enabled, the edit mode is advanced, and the value is true. In
advanced edit mode, you can edit Datasource and Dataconnector
properties in the Data Analyzer instance.
When disabled, the edit mode is basic, and the value is false. In basic edit
mode, you can edit Datasource properties in the Administrator tool.
Note: After you enable the Reporting Service in advanced edit mode, you
cannot change it back to basic edit mode.
Reporting Source Options

Enter Reporting source options in the following format:
infacmd CreateReportingService ... -rs option_name=value option_name=value
323
The following table describes Reporting Source options:

Option
Description
DatasourceName
Required. Name of the service for reporting.
DatasourceType
Required. Type of service. Service types include:

- Dataprofiling
- MM
- PCRR
- Other
Lineage Service Options

Enter lineage service options in the following format:
infacmd CreateReportingService ... -ls option_name=value option_name=value
The following table describes Lineage Service options:
Option
Description
MetadataManagerService
Optional. Name of the Metadata Manager Service to which you want to connect to
perform data lineage.
ResourceName
Optional. Name of the resource in the Metadata Manager for which you loaded the
Data Analyzer metadata.
CreateRepositoryService
Creates a PowerCenter Repository Service in a domain.
By default, the PowerCenter Repository Service is enabled when you create it.
A PowerCenter Repository Service manages one repository. It performs all metadata transactions between
the repository and repository clients.
The infacmd isp CreateRepositoryService command uses the following syntax:
324
<-ServiceOptions|-so> option_name=value ...
The following table describes infacmd isp CreateRepositoryService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
-hp
gateway_host1:port
gateway_host2:port
...

325
Option
Argument
Description
-ResilienceTimeout
-re
conds

-ServiceName
service_name
Required. Name of the PowerCenter Repository 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 associated repository. The name cannot have leading or
trailing spaces, include carriage returns or tabs, exceed 79
characters, or contain the following characters:
-sn
\ / : * ? < > " |

-NodeName
node_name
Required. Name of the node where you want the PowerCenter

Repository Service process to run. If the PowerCenter
node1 node2 ...

Optional. Creates a disabled service. You must enable the

service before you can run it.
option_name=value
Required. Service properties that define how the PowerCenter

Repository Service runs.
license_name
Required if you create an enabled service. Name of the license

you want to assign to the PowerCenter Repository Service.
full_folder_path
Optional. Full path, excluding the domain name, to the folder in

which you want to create the PowerCenter Repository Service.
Must be in the following format:
-nn
-BackupNodes
-bn
-ServiceDisable
-sd
-ServiceOptions
-so
-LicenseName
-ln
-FolderPath
-fp
Repository Service Options (-so)

Enter Repository Service options in the following format:
infacmd CreateRepositoryService ... -so option_name=value option_name=value ...
326
The following table describes Repository Service options:

Option
Description
AllowWritesWithRACaching
Optional. Uses PowerCenter Client tools to modify metadata in the repository

when repagent caching is enabled. Default is Yes.
CheckinCommentsRequired
Optional. Requires users to add comments when checking in repository

objects. Default is Yes. To apply changes, restart the PowerCenter Repository
Service.
CodePage
Required. Code page description for the database. To enter a code page
description that contains a space or other non-alphanumeric character, enclose
the name in quotation marks.
ConnectString
Required. Database connection string specified during PowerCenter Repository

Service setup. To apply changes, restart the PowerCenter Repository Service.
DBPassword
Required. Repository database password corresponding to the database user.

You can set a password with the -so option or the environment variable
INFA_DEFAULT_DATABASE_PASSWORD. If you set a password with both
methods, the password set with the -so option takes precedence.
To apply changes, restart the PowerCenter Repository Service.
DBPoolExpiryThreshold
Optional. The minimum number of idle database connections allowed by the

PowerCenter Repository Service. For example, if there are 20 idle connections,
and you set this threshold to 5, the PowerCenter Repository Service closes no
more than 15 connections. Minimum is 3. Default is 5.
DBPoolExpiryTimeout
Optional. The interval, in seconds, at which the PowerCenter Repository

Service checks for idle database connections. If a connection is idle for a
period of time greater than this value, the PowerCenter Repository Service can
close the connection. Minimum is 300. Maximum is 2,592,000 (30 days).
Default is 3,600 (1 hour).
DBUser
Required. Account for the database containing the repository. To apply

changes, restart the PowerCenter Repository Service.
DatabaseArrayOperationSize
Optional. Number of rows to fetch each time an array database operation is

issued, such as insert or fetch. Default is 100. To apply changes, restart the
PowerCenter Repository Service.
DatabaseConnectionTimeout
Optional. Amount of time in seconds that the PowerCenter Repository Service

attempts to establish a connection to the database management system.
Default is 180.
DatabasePoolSize
Optional. Maximum number of connections to the repository database that the

PowerCenter Repository Service can establish. Minimum is 20. Default is 500.
DatabaseType
Required. Type of database that stores the repository metadata. To apply

EnableRepAgentCaching
Optional. Enables the repository agent caching feature. Default is Yes.
327
Option
Description
ErrorSeverityLevel
Optional. Minimum level of error messages written to the PowerCenter

Repository Service log:
- Fatal
- Error
Warning
- Info
- Trace
- Debug
Default is Info.
HeartBeatInterval
Optional. Interval at which the PowerCenter Repository Service verifies its

connections with clients of the service. Default is 60 seconds.
Optional. Maximum amount of time in seconds that the service holds on to

resources for resilience purposes. Default is 180.
MaximumConnections
Optional. Maximum number of connections the repository accepts from

repository clients. Default is 200.
MaximumLocks
Optional. Maximum number of locks the repository places on metadata objects.

Default is 50,000.
OperatingMode
Optional. Mode in which the PowerCenter Repository Service is running:

- Normal
- Exclusive
Default is Normal. To apply changes, restart the PowerCenter Repository

Service.
OptimizeDatabaseSchema
Optional. Optimizes the repository database schema when you create

repository contents or back up and restore an IBM DB2 or Microsoft SQL
Server repository. When enabled, the PowerCenter Repository Service tries to
create repository tables that contain Varchar columns with a precision of 2000
instead of CLOB columns. Use Varchar columns to increase repository
performance. When you use Varchar columns, you reduce disk input and
output, and the database can cache the columns.
To use this option, verify the page size requirements for the following repository
databases:
- IBM DB2. Database page size 4 KB or greater. At least one temporary tablespace
with page size 16 KB or greater.
- Microsoft SQL Server. Database page size 8 KB or greater.
Default is disabled.
328
PreserveMXData
Optional. Preserves MX data for prior versions of mappings. Default is

disabled.
RACacheCapacity
Optional. Number of objects that the cache can contain when repository agent
caching is enabled. Default is 10,000.
SecurityAuditTrail
Optional. Tracks changes made to users, groups, privileges, and permissions.

Default is No.
Optional. Amount of time in seconds that the service tries to establish or

reestablish a connection to another service. Default is 180. To apply changes,
restart the PowerCenter Repository Service.
Option
Description
TableOwnerName
Optional. Name of the owner of the repository tables for an IBM DB2 repository.
TablespaceName
Optional. Tablespace name for IBM DB2 repositories. To apply changes, restart
the PowerCenter Repository Service.
TrustedConnection
Optional. Uses Windows authentication to access the Microsoft SQL Server

database. Default is No. To apply changes, restart the PowerCenter Repository
Service.
CreateRole
Creates a custom role in the domain. You can then assign privileges to the role for the domain or for an
application service type. You cannot create system-defined roles.
The infacmd isp CreateRole command uses the following syntax:
CreateRole
[<-RoleDescription|-rd> role_description]
The following table describes infacmd isp CreateRole options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

CreateRole
329
Option
Argument
Description
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-RoleName
role_name
Required. Name of the role. The role name is case insensitive

and can be between 1 and 80 characters long. It cannot
include a tab, newline character, or the following special
characters:
-hp
-ResilienceTimeout
-rn
, + " \ < > ; / * % ?

the first and last character. All other space characters are not
allowed.
-RoleDescription
role_description
-rd
Optional. Description of the role. The description can have a

maximum of 1,000 characters and cannot include a tab,
newline character, or the following special characters:
< > "
To enter a description that contains spaces or other nonalphanumeric characters, enclose it in quotation marks.
330
CreateSAPBWService
Creates an SAP BW Service in the domain. By default, the SAP BW Service is enabled when you create it.
The infacmd isp CreateSAPBWService command uses the following syntax:
CreateSAPBWService
<-RepositoryUser|-ru> user
<-RepositoryPassword|-rp> password
The following table describes infacmd isp CreateSAPBWService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

CreateSAPBWService
331
Option
Argument
Description
-Password
password

security_domain

is case sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
-hp
gateway_host1:port
gateway_host2:port
...
-ResilienceTimeout
-re
ds
-ServiceName
service_name
-sn

domain.
Required. Name of the SAP BW Service.
within the domain. The characters must be
compatible with the code page of the associated
repository. The name cannot have leading or trailing
spaces, include carriage returns or tabs, exceed 79
characters, or contain the following characters:
/ * ? < > " |
-NodeName
node_name
-nn
332
Required. Name of the node where you want the SAP

BW Service process to run. If the PowerCenter
environment is configured for high availability, this
option specifies the name of the primary node.
Option
Argument
Description
-IntegrationService
integration_service_nam
e
Required. Name of the Integration Service to which

the SAP BW Service connects.
-is
quotation marks.
-RepositoryUser
user
-ru
Required. User name used to connect to the

repository.
quotation marks.
-RepositoryPassword
password
-rp
Required if secure communication is not enabled for

the domain. Optional if secure communication is
enabled for the domain.
User password. You can set a password with the -rp
INFA_REPOSITORY_PASSWORD. If you set a
the -rp option takes precedence.
-ServiceOptions
option_name=value
Optional. Service properties that define how the SAP

BW Service runs.
option_name=value
Optional. Service process properties for the SAP BW

Service.
Optional. Creates a disabled service. You must

enable the service before you can run it.
license_name
Required if you create an enabled service. Name of

the license you want to assign to the SAP BW
Service.
full_folder_path
Optional. Full path, excluding the domain name, to

the folder in which you want to create the SAP BW
-so
ServiceProcessOptions
-po
-ServiceDisable
-sd
-LicenseName
-ln
-FolderPath
-fp
SAP BW Service Options

Enter SAP BW Service options in the following format:
infacmd CreateSAPBWService ... -so option_name=value option_name=value ...
CreateSAPBWService
333
The following table describes SAP BW Service options:

Option
Description
BWSystemConxString
Optional. DEST entry defined in the sapnwrfc.ini file for a connection

to an RFC server program. Edit this property if you have created a different
DEST entry in the sapnwrfc.ini file for the SAP BW Service.
RetryPeriod
Optional. Number of seconds the SAP BW Service waits before trying to

connect to the BW system if a previous connection attempt failed. Default
is 5.
SAP BW Service Process Option

Enter the service process option in the following format:
infacmd CreateSAPBWService ... -po option_name=value
To enter a value that contains a space or other non-alphanumeric character, enclose the value in quotation
marks.
The following table describes the SAP BW Service process option:
Option
Description
ParamFileDir
Optional. Temporary parameter file directory. Default is /Infa_Home/server/

infa_shared/BWParam.
CreateUser
Creates a user account in the native security domain. You can then assign roles, permissions, and privileges
to a user account. The roles, permissions, and privileges assigned to the user determine the tasks that the
user can perform within the domain.
The infacmd isp CreateUser command uses the following syntax:
CreateUser
<-NewUserName|-nu> new_user_name
<-NewUserPassword|-np> new_user_password
[<-NewUserFullName|-nf> new_user_full_name]
[<-NewUserDescription|-ds> new_user_description]
334
[<-NewUserEMailAddress|-em> new_user_email_address]
[<-NewUserPhoneNumber|-pn> new_user_phone_number]
The following table describes infacmd isp CreateUser options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

single sign-on.
-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
-ResilienceTimeout
-re
gateway_host1:port
gateway_host2:port
...

conds

CreateUser
335
Option
Argument
Description
-NewUserName
new_user_name
Required. Login name for the user account. The login

name for a user account must be unique within the security
domain to which it belongs.
-nu
The login name is not case sensitive and can be between 1

and 80 characters long. It cannot include a tab, newline
character, or the following special characters:
, + " \ < > ; / * & % ?
the first and last character. All other space characters are
not allowed.
-NewUserPassword
new_user_password
-np
Required. Password for the user account. You can set a

password with the -np option or the environment variable
INFA_PASSWORD. If you set a password with both these
methods, the password set with the -np option takes
precedence.
The password is case-sensitive and can be between 1 and
80 characters long.
-NewUserFullName
new_user_full_name
-nf
Optional. Full name for the user account. To enter a name

that contains spaces or other non-alphanumeric
characters, enclose the name in quotation marks. The full
name cannot include the following special characters:
< >
-NewUserDescription
new_user_description
-ds
Optional. Description of the user account. To enter a

description that contains spaces or other non-alphanumeric
characters, enclose it in quotation marks.
The description cannot include the following special
characters:
< >
-NewUserEMailAddress
-em
new_user_email_add
ress
Optional. Email address for the user. To enter an address

that contains spaces or other non-alphanumeric
The email address cannot include the following special
characters:
< >
Enter the email address in the format
UserName@Domain.
-NewUserPhoneNumber
-pn
new_user_phone_nu
mber
Optional. Telephone number for the user. To enter a

telephone number that contains spaces or other nonalphanumeric characters, enclose it in quotation marks.
The telephone number cannot include the following special
characters:
< >
336
CreateWSHubService
Creates a Web Services Hub in the domain. By default, the Web Services Hub is enabled when you create it.
The infacmd isp CreateWSHubService command uses the following syntax:
CreateWSHubService
[<-ServiceOptions|-so> option_name=value ...
The following table describes infacmd isp CreateWSHubService options and arguments:
Option
Argument
Description
-DomainName
domain_name
Required. Name of the domain.
user_name

-dn
-UserName
-un

-Password
-pd
password
CreateWSHubService
337
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-ServiceName
service_name
-hp
-ResilienceTimeout
-sn
Name of the Web Services Hub you want to create.

The name is not case sensitive and must be unique within the
domain. The characters must be compatible with the code
page of the associated repository. The name cannot have
leading or trailing spaces, include carriage returns or tabs,
exceed 79 characters, or contain the following characters:
/ * ? < > " |
-FolderPath
full_folder_path
-fp

in which you want to create the Web Services Hub. Must be in
the following format:
-NodeName
node_name
Required. Name of the node where you want to run the Web
Services Hub process.
RepositoryService
repository_service_
-rs
name
Required. Name of the Repository Service that the Web

Services Hub depends on.
-nn
To enter a name that contains a space or other nonalphanumeric character, enclose the name in quotation marks.
-RepositoryUser
repository_user
-ru
338
Required. User name used to connect to the repository.

Option
Argument
Description
-RepositoryPassword
repository_password
Required. User password. You can set a password with the rp option or the environment variable
INFA_REPOSITORY_PASSWORD. If you set a password with
both methods, the password that you set with the -rp option
takes precedence.
repository_user_secu
rity_domain
Required if the domain uses LDAP authentication or Kerberos

PowerCenter repository user belongs.
-rp
yDomain
-rsdn
The security domain name is case sensitive. If the domain

uses native or LDAP authentication, the default is Native. If
the domain uses Kerberos authentication, the default is the
LDAP security domain created during installation. The name
-ServiceDisable
Optional. Creates a disabled service. You must enable the

service before you can run it.
-so
option_name=value
...
Optional. Service properties that define how the Web Services

Hub runs.
-LicenseName
license_name
Required. Name of the license you want to assign to the Web

Services Hub.
-sd
-ServiceOptions
-ln
Web Services Hub Options

Enter Web Services Hub options in the following format:
infacmd CreateWSHubService ... -so option_name=value option_name=value ...
The following table describes Web Services Hub options:
Option
Description
DTMTimeout
Optional. Amount of time in seconds that infacmd attempts to establish or

reestablish a connection to the DTM. Default is 60.
ErrorSeverityLevel
Optional. Minimum level of error logging for the Web Services Hub logs:
- Fatal
- Error
- Warning
- Info
- Trace
- Debug
Default is Info.
CreateWSHubService
339
Option
Description
HubHostName
Optional. Name of the machine hosting the Web Services Hub. Default is
localhost. To apply changes, restart the Web Services Hub.
HubPortNumber(http)
Optional. Port number on which the Web Services Hub runs in Tomcat. Default
is 7333. To apply changes, restart the Web Services Hub.
HubPortNumber (https)
Port number on which the Web Services Hub runs in Tomcat. Required if you
choose to run the Web Services Hub on HTTPS. Default is 7343.
InternalHostName
Optional. Host name at which the Web Services Hub listens for connections
from the Integration Service. Default is localhost. To apply changes, restart the
Web Services Hub.
InternalPortNumber
Optional. Port number at which the Web Services Hub listens for connections
from the Integration Service. Default is 15555. To apply changes, restart the
Web Services Hub.
MaxConcurrentRequests
Optional. Maximum number of request processing threads available, which

determines the maximum number of simultaneous requests that can be
handled. Default is 100.
MaxLMConnections
Optional. Maximum number of connections to the Integration Service that can

be open at one time for the Web Services Hub. Default is 20.
MaxQueueLength
Optional. Maximum queue length for incoming connection requests when all
possible request processing threads are in use. Default is 5000.
SessionExpiryPeriod
Optional. Number of seconds that a session can remain unused before its
session ID becomes invalid. Default is 3600 seconds.
URLScheme
Optional. Security protocol that you configure for the Web Services Hub: HTTP
or HTTPS. Default is HTTP. To apply changes, restart the Web Services Hub.
WSH_ENCODING
Optional. Character encoding for the Web Services Hub. Default is UTF-8. To
apply changes, restart the Web Services Hub.
KeystoreFile
Optional. Keystore file that contains the keys and certificates required if you
use the SSL security protocol with the Web Services Hub.
DeleteDARepositoryContents
Deletes repository content from a Data Analyzer repository. When you delete repository content, you also
delete all privileges and roles assigned to users for the Reporting Service.
The infacmd isp DeleteDARepositoryUsers command uses the following syntax:
340
The following table describes infacmd isp DeleteDARepositoryUsers options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

run the command with single sign-on, do not set the
user name. If you set the user name, the command runs
-Password
password

set a password with both methods, the password set
security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port

341
Option
Argument
Description
-ResilienceTimeout
-re
ds

-ServiceName
service_name
Required. Name of the Reporting Service for which you

want to delete contents.
-sn
DeleteNamespace
Deletes an LDAP security domain and the users and groups in the security domain. Deletes the LDAP
security domain if the Informatica domain uses LDAP or Kerberos authentication.
The infacmd isp DeleteNamespace command uses the following syntax:
DeleteNamespace
The following table describes infacmd isp DeleteNamespace options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

single sign-on.
342
Option
Argument
Description
-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn
-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-NameSpace
namespace
Required. Name of the LDAP or Kerberos security domain.

the domain. The name cannot contain spaces or any of the
-hp
-ResilienceTimeout
-ns
,+/<>@;\%?
DisableNodeResource
Disables an Informatica resource. Informatica resources include file directory resources, custom resources,
and connection resources. Disable the resources that are not available to prevent the Load Balancer from
dispatching a task to a node that does not have the required resources.
You can disable file directory resources, custom resources, and connection resources.
DisableNodeResource
343
check resources, the Load Balancer distributes tasks to nodes with available resources.
By default, all connection resources are enabled on a node.
The infacmd isp DisableNodeResource command uses the following syntax:
DisableNodeResource
<-ResourceType|-rt> resource_type ("Custom", "File Directory", "Connection")
The following table describes infacmd isp DisableNodeResource options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
-pd
344
precedence.
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-NodeName
node_name
Required. Name of the node where the resource is defined.
-hp
-ResilienceTimeout
-nn
-ResourceCategory
resource_category

-rc
Default is PCIS.
-ResourceType
resource_type
-rt

- Custom
- File Directory
- Connection
-ResourceName
-rn
resource_name
Required. Entire name of the resource.

To list the names of all resources available to a node, run the
infacmd isp ListNodeResources command.
DisableService
Disables the application service corresponding to the service name. When you disable a service, all service
processes stop.
Disables any application service type, including system services.
The infacmd isp DisableService command uses the following syntax:
DisableService
DisableService
345
<-Mode|-mo> disable_mode
The following table describes infacmd isp DisableService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name
Required. User name to connect to the domain. You can set the
user name with the -un option or the environment variable
password
precedence.
security_domain

sensitive.
-dn
-UserName
-un
-Password
-pd
-SecurityDomain
-sdn

-Gateway
-hp
-ResilienceTimeout
-re
346
gateway_host1:port
gateway_host2:port
...

timeout_period_in_s
econds

Option
Argument
Description
-ServiceName
service_name
Required. Name of the service you want to disable. To enter a

disable_mode
Required. Defines how the service is disabled:
-sn
-Mode
-mo
- Complete. Disables the service after all service processes stop.

- Stop. If the service is a PowerCenter Integration Service, stops all
running workflows, and then disables the PowerCenter Integration
Service.
If the service is an Analyst Service, stops all the jobs, and then
disables the service.
- Abort. Stops all processes immediately, and then disables the
service.
Note: If you specify a disable mode of Stop for a Listener Service, the command waits up to 30 seconds for
Listener subtasks to complete and then shuts down the service and the Listener Service process.
DisableServiceProcess
Disables the service process on a specified node.
You can disable a service process on a specified node if the node requires maintenance.
The infacmd isp DisableServiceProcess command uses the following syntax:
<-Mode|-mo> disable_mode
347
The following table describes infacmd isp DisableServiceProcess options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-ServiceName
service_name
Required. Name of the service associated with the process you

want to disable. To enter a name that contains a space or other
marks.
-hp
ResilienceTimeout
-sn
348
Option
Argument
Description
-NodeName
node_name
Required. Name of the node where the service process is

running.
disable_mode
Required. Defines how the service process is disabled:
-nn
-Mode
-mo
- Complete. Allows the service process to complete the current

tasks before disabling.
- Stop. If the process is an Integration Service process, stops all
running workflows, and then disables the Integration Service
process.
- Abort. Disables the service process before the current task
completes.
DisableUser
Disables a user account in the domain. If you do not want a user to access the domain temporarily, you can
disable the user account.
When you disable a user account, the user cannot log in to the PowerCenter applications.
The infacmd isp DisableUser command uses the following syntax:
DisableUser
DisableUser
349
The following table describes infacmd isp DisableUser options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

user name with both methods, the -un option takes
precedence.
-dn
-UserName
-un

-Password
password

security_domain

Optional if the domain uses native authentication
or Kerberos authentication. Name of the security
domain to which the domain user belongs. You
can set a security domain with the -sdn option or
INFA_DEFAULT_SECURITY_DOMAIN. If you set
a security domain name with both methods, the sdn option takes precedence. The security domain
-pd
-SecurityDomain
-sdn

domain created during installation. The name of
the security domain is the same as the user realm
-Gateway
-hp
350
gateway_host1:port

the domains.infa file is out of date. The host
names and port numbers for the gateway nodes in
the domain.
Option
Argument
Description
-ResilienceTimeout
-re
ds

attempts to establish or reestablish a connection
environment variable, the default of 180 seconds
is used.
ExistingUserName
existing_user_name
Required. User account you want to disable. To

enter a name that contains a space or other nonalphanumeric character, enclose the name in
quotation marks.
existing_user_security_d
omain

the security domain that the user you want to
disable belongs to. Default is Native.
-eu
-esd
EditUser
Edits the general properties for a user account in the native security domain.
You cannot modify the properties of user accounts in the LDAP security domains.
You cannot change the login name of a native user.
The infacmd isp EditUser command uses the following syntax:
EditUser
[<-ExistingUserFullName|-ef> Existing_user_full_name]
[<-ExistingUserDescription|-ds> Existing_user_description]
[<-ExistingUserEMailAddress|-em> Existing_user_email_address]
[<-ExistingUserPhoneNumber|-pn> Existing_user_phone_number]
EditUser
351
The following table describes infacmd isp EditUser options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

domain. You can set the user name with the un option or the environment variable
takes precedence.
-dn
-UserName
-un

sign-on, do not set the user name. If you set
the user name, the command runs without
single sign-on.
-Password
password
Required if you specify the user name.

Password for the user name. The password is
case sensitive. You can set a password with
the -pd option or the environment variable
set a password with both methods, the
password set with the -pd option takes
precedence.
security_domain

native authentication or Kerberos
authentication. Name of the security domain to
which the domain user belongs. You can set a
-pd
-SecurityDomain
-sdn

domain uses Kerberos authentication, the
default is the LDAP security domain created
during installation. The name of the security
domain is the same as the user realm specified
-Gateway
-hp
352
gateway_host1:port
Required if the gateway connectivity

information in the domains.infa file is out of
date. The host names and port numbers for the
gateway nodes in the domain.
Option
Argument
Description
ResilienceTimeout
Optional. Amount of time in seconds that

infacmd attempts to establish or re-establish a
connection to the domain. If you omit this
option, infacmd uses the timeout value
specified in the
seconds is used.
existing_user_name
Required. User account you want to edit.
existing_user_full_name
Optional. Changed full name for the user

account. To enter a name that contains spaces
or other non-alphanumeric characters, enclose
the name in quotation marks. The full name
cannot include the following special characters:
< >
existing_user_description
Optional. Changed description for the user

account. To enter a description that contains
spaces or other non-alphanumeric characters,
-re
-ExistingUserName
-eu
-ExistingUserFullName
-sf
-ExistingUserDescription
-ds
The description cannot include the following

special characters:
< >
-ExistingUserEMailAddress
-em
existing_user_email_addres
s
Optional. Changed email address for the user.

To enter an address that contains spaces or
other non-alphanumeric characters, enclose it
in quotation marks.
The email address cannot include the following
special characters:
< >
-ExistingUserPhoneNumber
-pn
existing_user_phone_numbe
r
Optional. Changed telephone number for the

user. To enter a telephone number that
contains spaces or other non-alphanumeric
The phone number cannot include the following
special characters:
< >
EditUser
353
EnableNodeResource
Enables an Informatica resource. Informatica resources include file or directory, custom, and connection
resources. When you enable a resource on a node, you allow the Load Balancer to distribute tasks that
require the resource to that node.
The infacmd isp EnableNodeResource command uses the following syntax:
EnableNodeResource
<-ResourceType|-rt> resource_type ("Custom", "File Directory", "Connection")
The following table describes infacmd isp EnableNodeResource options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
-pd
354
precedence.
Option
Argument
Description
-SecurityDomain
security_domain

sensitive.
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-NodeName
node_name
Required. Name of the node where the resource is defined.
-hp
-ResilienceTimeout
-nn
-ResourceCategory
resource_category

-rc
Default is PCIS.
-ResourceType
resource_type
-rt

- Custom
- File Directory
- Connection
-ResourceName
-rn
resource_name
Required. Entire name of the resource.

ListNodeResources command.
EnableService
Enables the application service corresponding to the service name.
Enables any application service type, including system services. You can also enable the Informatica
Administrator.
The infacmd isp EnableService command uses the following syntax:
EnableService
EnableService
355
The following table describes infacmd isp EnableService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
-hp
356
gateway_host1:port
gateway_host2:port
...

Option
Argument
Description
-ResilienceTimeout
-re
timeout_period_in_s
econds

-ServiceName
service_name
Required. Name of the service you want to enable. To enter a

name that contains a space or other non-alphanumeric character,
enclose the name in quotation marks.
-sn
To start the Administrator tool, enter _adminconsole.
EnableServiceProcess
Enables a service process on a specified node.
The infacmd isp EnableServiceProcess command uses the following syntax:
The following table describes infacmd isp EnableServiceProcess options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

357
Option
Argument
Description
-Password
password
precedence.
security_domain

sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
timeout_period_in_s
econds

-ServiceName
service_name
Required. Name of the service associated with the process you

want to enable. To enter a name that contains a space or other
marks.
node_name
Required. Name of the node where you want to enable a service

process.
-hp
-ResilienceTimeout
-sn
-NodeName
-nn
EnableUser
Enables a user account in the domain.
The infacmd isp EnableUser command uses the following syntax:
EnableUser
358

The following table describes infacmd isp EnableUser options and arguments:
Option
Argument
Description
-DomainName
domain_name
Required. Name of the Informatica domain.

You can set the domain name with the -dn
INFA_DEFAULT_DOMAIN. If you set a
domain name with both methods, the -dn
user_name

INFA_DEFAULT_DOMAIN_USER. If you set
a user name with both methods, the -un
-dn
-UserName
-un

authentication. To run the command with
single sign-on, do not set the user name. If
you set the user name, the command runs
-Password
password

Password for the user name. The password
is case sensitive. You can set a password
with the -pd option or the environment
variable
INFA_DEFAULT_DOMAIN_PASSWORD. If
you set a password with both methods, the
precedence.
security_domain

authentication. Name of the security domain
to which the domain user belongs. You can
set a security domain with the -sdn option or
INFA_DEFAULT_SECURITY_DOMAIN. If
you set a security domain name with both
methods, the -sdn option takes precedence.
-pd
-SecurityDomain
-sdn

domain is the same as the user realm
EnableUser
359
Option
Argument
Description
-Gateway
-hp
gateway_host1:port

date. The host names and port numbers for
the gateway nodes in the domain.
-ResilienceTimeout

infacmd attempts to establish or re-establish
a connection to the domain. If you omit this
specified in the
environment variable. If no value is specified
in the environment variable, the default of
existing_user_name
Required. User account you want to enable.

To enter a name that contains a space or
other non-alphanumeric character, enclose
existing_user_security_domai
n
Required if you use LDAP authentication.

Name of the security domain that the user
you want to enable belongs to. Default is
Native.
-re
ExistingUserName
-eu
-esd
ExportDomainObjects
Exports native users, native groups, roles, and connections from the Informatica domain to an XML file.
If you do not want to export all objects in the domain, use an infacmd export control file to filter the objects
that you want to export.
Use the ExportDomainObjects and ImportDomainObjects commands to migrate objects between two different
domains of the same version. To export native users and groups from domains of different versions, use the
infacmd isp ExportUsersAndGroups command.
When you export a group, you export all subgroups and users in the group.
You cannot export the Administrator user, the Administrator group, users in the Administrator group, the
Everyone group, or the LDAP users or groups. To replicate LDAP users and groups in an Informatica domain,
import the LDAP users and groups directly from the LDAP directory service.
If the command fails with a Java memory error, increase the system memory available for infacmd. To
increase the system memory, set the -Xmx value in the ICMD_JAVA_OPTS environment variable.
The infacmd isp ExportDomainObjects command uses the following syntax:
ExportDomainObjects
360

<-ExportFile|-fp> export_file_name
[<-ExportControlFile|-cp> export_control_file_name]
[<-RetainPassword|-rp> retain_password]
[<-Force|-f>]
The following table describes infacmd isp ExportDomainObjects options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

is case sensitive.
-pd
-SecurityDomain
-sdn

ExportDomainObjects
361
Option
Argument
Description
-Gateway
gateway_host1:port
gateway_host2:port
...

domain.
-re
timeout_period_in_s
econds

used.
-ExportFile
export_file_name
-hp
-ResilienceTimeout
-fp
Required. Path and file name of the export file.

If you do not specify the file path, infacmd creates
the file in the directory where you run infacmd.
-ExportControlFile
export_control_file
Optional.Name and path for the export control file

that filters the objects that are exported.
retain_password
Optional. Set to true to retain encrypted passwords

for users and connections in the exported file. When
set to false, user and connection passwords are
exported as empty strings. Default is false.
Optional. Overwrites the export file if a file with the

same name already exists. If you omit this option,
the command prompts you for a confirmation before
it overwrites the file.
-cp
-RetainPassword
-rp
-Force
-f
ExportUsersAndGroups
Exports native users and groups to an XML file.
The infacmd isp ExportUsersAndGroups command uses the following syntax:
<-ExportFile|-ef> export_file_name
362
[<-Force|-f>]
The following table describes infacmd isp ExportUsersAndGroups options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port

ResilienceTimeout

-re
363
Option
Argument
Description
-ExportFile
export_file_name
Required. Name and file path where you want to write the
export file.
-ef
If you do not specify the file path, infacmd creates the

backup file in the directory where you run infacmd.
-Force
-f
Optional. Overwrites the export file, if a file with the same

name already exists. If you omit this option, the
command prompts you for a confirmation before it
deletes the file.
Related Topics:
ImportUsersAndGroups on page 391
GetFolderInfo
Gets folder information. Folder information includes folder path, name, and description.
To run the infacmd isp GetFolderInfo command, you must have permission on the folder.
The infacmd isp GetFolderInfo command uses the following syntax:
GetFolderInfo
364
The following table describes infacmd isp GetFolderInfo options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

single sign-on.
-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
gateway_host1:port

-re
nds

-FolderPath
full_folder_path
Required. Full path, excluding the domain name, to the

folder. Must be in the format:
-hp
-ResilienceTimeout
-fp
GetFolderInfo
365
GetLastError
Gets the most recent error messages for an application service running on a node.
The error messages are log events that have a severity level of error or fatal. This command does not return
errors that occurred before Informatica Services were last started.
You can fetch error messages in a file or display them on the screen.
The infacmd isp GetLastError command uses the following syntax:
GetLastError
[<-MaxEvents|-me> maximum_number_of_error_events]
The following table describes infacmd isp GetLastError options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
-pd
366
precedence.
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-ServiceName
service_name
Optional. Name of the service for which you want to fetch error
messages. To enter a name that contains a space or other nonalphanumeric character, enclose the name in quotation marks.
node_name
Required. Name of the node where the service runs.
format
Optional. Format for error messages. Valid types include:
-hp
ResilienceTimeout
-sn
-NodeName
-nn
-Format
- Text
- XML
-fm
If you do not specify a format, infacmd displays the messages

in text format with lines wrapped at 80 characters.
-MaxEvents
-me
maximum_number_of
_error_events
Optional. Maximum number of error messages to fetch. Default

is 1. Maximum value is 20.
GetLog
Gets log events. You can get log events for a domain or services. You can write log events to a file or display
them on the screen.
To fetch log events for a domain, you must have permission on the domain. To fetch log events for a service,
you must have permission on the service.
The infacmd isp GetLog command uses the following syntax:
GetLog
GetLog
367
[<-StartDate|-sd> start_date_time]
[<-EndDate|-ed> end_date_time]
[<-ReverseOrder|-ro>]
[<-Format|-fm> format_TEXT_XML_BIN]
[<-ServiceType|-st> service_type AS|BW|CMS|DIS|IS|MM|MRS|RPS|RS|WS|ES|SCH|RMS|DOMAIN|
SEARCH|]
[<-Severity|-svt> FATAL_ERROR_WARNING_INFO_TRACE_DEBUG]
The following table describes infacmd isp GetLog options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
-pd
368
precedence.
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-StartDate
start_date_time
Optional. Returns log events starting from this date and time.
Enter date and time in one of the following formats:
-hp
ResilienceTimeout
-sd
- MM/dd/yyyy_hh:mm:ssa_Z
- MM/dd/yyyy_hh:mma_Z
- MM/dd/yyyy_hh:mm:ssa
- MM/dd/yyyy_hh:mma
- yyyy-MM-dd_HH:mm:ss_Z
- yyyy-MM-dd_HH:mm_Z
- yyyy-MM-dd_HH:mm:ss
- yyyy-MM-dd_HH:mm
- MM/dd/yyyy hh:mm:ssa Z
- MM/dd/yyyy hh:mma Z
- MM/dd/yyyy hh:mm:ssa
- MM/dd/yyyy hh:mma
- yyyy-MM-dd HH:mm:ss_Z
- yyyy-MM-dd HH:mm_Z
- yyyy-MM-dd HH:mm:ss
- yyyy-MM-dd HH:mm
- MM/dd/yyyy
- yyyy-MM-dd
Where a is an am/pm marker (a for a.m. and p for p.m.)

and Z is a time zone marker (for example,-0800 or GMT).
GetLog
369
Option
Argument
Description
-EndDate
end_date_time
Optional. Returns log events ending by this date and time. Enter
date and time in the same format as the StartDate option.
-ed
If you enter an end date that is before the start date, GetLog
returns no log events.
-ReverseOrder
Optional. Fetches log events according to most recent

timestamp.
format
Optional. Format for log events. Valid types include:
-ro
-Format
-fm
- Text
- XML
- Bin (binary)
If you choose binary, then you must specify a file name using
the OutputFile option.
If you do not specify a format, infacmd uses text format with
lines wrapped at 80 characters.
-OutputFile
output_file_name
-lo
Name and file path where you want to write the log file. By
default, the Service Manager uses the server\infa_shared\log
directory on the master gateway node.
Omit this option to display the log events on the screen.
If you choose binary as the output file type, you must specify a
file name using this option.
-ServiceType
service_type
-st
Optional. Type of service for which you want to fetch log events.
You can specify one service type.
Omit this option to fetch log events for all service types.
-
370
AS. Analyst Service

BW. SAP BW Service
DIS. Data Integration Service
IS. PowerCenter Integration Service
WS. Web Services Hub
ES. Email Service
SCH. Scheduler Service
RMS. Resource Manager Service
DOMAIN. Domain
SEARCH. Search Service
Option
Argument
Description
-ServiceName
service_name
Optional. Name of the service for which you want to fetch log
events. To enter a name that contains a space or other nonalphanumeric character, enclose the name in quotation marks.
severity_level
Optional. Message severity. Severity types include:
-sn
-Severity
-svt
- Fatal
- Error
- Warning
- Info
- Trace
- Debug
GetNodeName
Returns the name of a node.
Gets the node name from the nodemeta.xml file on the node. You must enter this command on the node for
which you want to fetch the name.
The infacmd isp GetNodeName command uses the following syntax:
GetNodeName
[<-OutputFile|-o>] output_file
When you use the command without the -o option, the command prints the node name to the command
window. When you use the -o option to specify an output file, you provide the file name and path. For
example:
isp\bin\infacmd.bat getNodeName -o c:\node_name.txt
The command creates a file, node_name.txt, in the path that you specify. It prints the node name in the file. If
the file exists, the command overwrites the file.
GetServiceOption
Gets the value of a service property for a PowerCenter Integration Service, PowerCenter Repository Service,
SAP BW Service, or Web Services Hub. For Data Integration Service or Analyst Service options, run infacmd
dis or infacmd as ListServiceOptions.
For example, you can retrieve the repository database type.
The infacmd isp GetServiceOption command uses the following syntax:
GetServiceOption
GetNodeName
371
<-OptionName|-op> option_name
The following table describes infacmd isp GetServiceOption options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
-hp
ResilienceTimeout
-re
372
gateway_host1:port
gateway_host2:port
...

timeout_period_in_s
econds

Option
Argument
Description
-ServiceName
service_name
Required. Name of the service for which you want to fetch a

value. To enter a name that contains a space or other nonalphanumeric character, enclose the name in quotation marks.
option_name
Required. Name of the option for which you want to retrieve a

value. The options you specify depend on the service type:
-sn
-OptionName
-op
- For more information about Integration Service options, see

Integration Service Options on page 307.
- For an SAP BW Service, specify BWSystemConXString (the SAP
Destination R type) or RetryPeriod (the retry period in seconds).
- For more information about Web Services Hub options, see Web
Services Hub Options on page 339.
GetServiceProcessOption
Gets the value for a property on a PowerCenter Integration Service process running on a node.
The infacmd isp GetServiceProcessOption command uses the following syntax:
<-OptionName|-op> option_name
373
The following table describes infacmd isp GetServiceProcessOption options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
timeout_period_in_s
econds

-ServiceName
service_name
Required. Name of the service for which you want to fetch a

value. To enter a name that contains a space or other nonalphanumeric character, enclose the name in quotation marks.
node_name

running.
option_name
Required. Name of the option for which you want to retrieve a

value.
-hp
ResilienceTimeout
-sn
-NodeName
-nn
-OptionName
-op
374
Related Topics:
Integration Service Process Options on page 311
GetServiceProcessStatus
Gets the status of an application service process on a node. A service process can be enabled or disabled.
The infacmd isp GetServiceProcessStatus command uses the following syntax:
The following table describes infacmd isp GetServiceProcessStatus options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
-pd
password
precedence.
375
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
timeout_period_in_s
econds

-ServiceName
service_name
Required. Name of the service running the process for which

you want the status. To enter a name that contains a space or
quotation marks.
node_name

running.
-hp
-ResilienceTimeout
-sn
-NodeName
-nn
GetServiceStatus
Gets the status of an application service.
You can fetch the status of a service such as the Repository Service, Data Integration Service, Analyst
Service, Integration Service, Web Services Hub, or SAP BW Service. A service can be enabled or disabled.
The infacmd isp GetServiceStatus command uses the following syntax:
GetServiceStatus
376
The following table describes infacmd isp GetServiceStatus options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
timeout_period_in_s
econds

-ServiceName
service_name
Required. Name of the service for which you want the status. To
enter a name that contains a space or other non-alphanumeric
-hp
ResilienceTimeout
-sn
GetServiceStatus
377
GetSessionLog
Gets log events for the most recent run of a session. The PowerCenter Repository Service must be running
when you run this command.
The infacmd isp GetSessionLog command uses the following syntax:
GetSessionLog
[<-UserName|-un> user_name]
[<-Password|-pd> password]
[<-RepositoryDomain|-rd> domain_of_repository]
<-RepositoryUser|-ru> repository_user]
<-RepositoryPassword|-rp> repository_password]
<-FolderName|-fn> repository_folder_name
<-Workflow|-wf> workflow_name
[<-RunInstance|-in> run_instance_name] | <-RunId|-id> workflow_run_id]
<-Session|-ss> session_name
Note: If you do not specify -un, -pd, and -sdn options, the infacmd isp GetSessionLog command uses the
corresponding values from the -ru, -rp, and the -rsdn options.
378
The following table describes infacmd isp GetSessionLog options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

authentication, the default is the user realm specified during
installation.
-Gateway
-hp
gateway_host1:port
gateway_host2:port
...
-ResilienceTimeout

-re
onds

to establish or reestablish a connection to the domain. If
-Format
format
Optional. Format for the session log. Valid types include:
-fm
- Text
- XML
- Bin (binary)
If you choose binary, then you must specify a file name

using the OutputFile option.
GetSessionLog
379
Option
Argument
Description
-OutputFile
output_file_name
Name and file path for the session log file. By default, the
Service Manager uses the server\infa_shared\log directory
on the master gateway node.
-lo
Omit this option to display the log events on the screen.

If you choose binary as the output file type, you must
specify a file name using this option.
IntegrationService
-is
integration_service_na
me
Required. Name of the Integration Service that runs the

session.
marks.
-RepositoryService
-rs
me
Required. Name of the Repository Service that contains the

session.
marks.
-RepositoryDomain
domain_of_repository
Required if the repository is in a domain other than the local

domain. Domain of the Repository Service. To enter a name
that contains a space or other non-alphanumeric character,
repository_user
Required for native or LDAP authentication. Optional if the

domain uses Kerberos authentication. User name used to
connect to the repository. To enter a name that contains a
space or other non-alphanumeric character, enclose the
repository_password

domain uses Kerberos authentication. User password. You
can set a password with the -rp option or the environment
variable INFA_REPOSITORY_PASSWORD. If you set a
password with both methods, the password set with the -rp
repository_user_securit
y_domain
Required for LDAP or Kerberos authentication. Optional if

the domain uses native authentication. Name of the security
domain to which the PowerCenter repository user belongs.
-rd
-RepositoryUser
-ru
-RepositoryPassword
-rp
yDomain
-rsdn
-FolderName
The security domain name is case sensitive. If you do not

specify this option, the command sets the repository user
security domain to native.
-fn
repository_folder_nam
e
Required. Name of the folder containing the session. To

enter a name that contains a space or other nonalphanumeric character, enclose the name in quotation
marks.
-Workflow
workflow_name
Required. Name of the workflow containing the session. To

marks.
-wf
380
Option
Argument
Description
-RunInstance
run_instance_name
Name of the workflow run instance that contains the

session. Use this option if you are running concurrent
workflows. Use the -in or the -id option, not both.
workflow_run_id
Run identifier number (Run ID) of the workflow run instance

that contains the session. Use this option if you are running
concurrent workflows. Use the -in or the -id option, not both.
Note: Use this option if the workflow does not have a unique
run instance name.
session_name
Required. Session name. To enter a name that contains a

-in
-RunId
-id
-Session
-ss
GetSystemLogDirectory
Returns the path of the system log directory.
You must enter this command on the domain for which you want to fetch the system log directory path.
The infacmd isp GetSystemLogDirectory command uses the following syntax:
[<-OutputFile|-o> output_file]
When you use the command without the -o option, the command prints the directory path to the command
window. When you use the -o option to specify an output file, you provide the file name and path for the
output file. For example:
isp\bin\infacmd.bat getSystemLogDirectory -o c:\sys_log_dir.txt
The command creates a file, sys_log_dir.txt, in the path that you specify, and prints the path of the system
log directory in the file. If the file exists, the command overwrites the file.
getUserActivityLog
Gets user activity logs for a single user or multiple users. You can write user activity logs to a file or display
them in the console.
The infacmd isp getUserActivityLog command uses the following syntax:
getUserActivityLog
[<-Gateway|-hp> gateway_host1:port]
381
[<-Users|-usrs> user1:[securitydomain] user2:[securitydomain]...
[<-StartDate|-sd> start_date]
[<-EndDate|-ed> end_date]
[<-ActivityCode|-ac> activity_code]
[<-ActivityText|-atxt> activity_text]
[<-ReverseOrder|-ro> true]
[<-Format|-fm> output_format_BIN_TEXT_XML]
The following table describes infacmd isp getUserActivityLog options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name
Required if the domain uses Native or

LDAP authentication. User name to connect
to the domain. You can set the user name
with the -un option or the environment
variable INFA_DEFAULT_DOMAIN_USER.
If you set a user name with both methods,
the -un option takes precedence.
-dn
-UserName
-un

-Password
password
-pd
382

variable
precedence.
Option
Argument
Description
-SecurityDomain
security_domain

authentication. Name of the security
domain to which the domain user belongs.
You can set a security domain with the -sdn
The security domain name is case
sensitive.
-sdn

-Gateway
gateway_host1:port
-hp
gateway_host2:port
...
-ResilienceTimeout

infacmd attempts to establish or reestablish
a connection to the domain. If you omit this
specified in the
environment variable. If no value is
specified in the environment variable, the
default of 180 seconds is used.
user1:[securitydomain] user2:
[securitydomain]
Optional. The list of users that you want to

get log events for. Separate multiple users
with a space. Use the wildcard symbol (*) to
view logs for multiple users on a single
security domain or all security domains. For
example, the following strings are valid
values for the option:
-re
-Users
-usrs

...
user:Native
"user:*"
"user*"
"*_users_*"
"*:Native"
If you use the wildcard symbol, enclose the
argument in quotation marks.
If you do not enter a user, the command
retrieves the log events for all users.
getUserActivityLog
383
Option
Argument
Description
-StartDate
start_date
Optional. Returns log events starting from

the date and time that you specify.
-sd
Enter the date and time in one of the

following formats:
-
-EndDate
end_date
-ed
MM/dd/yyyy
MM/dd/yyyy HH:mm:ss
yyyy-MM-dd
yyyy-MM-dd HH:mm:ss
Optional. Returns log events ending by the

date and time. Enter the date and time in
the same format as the StartDate option.
If you enter an end date that is before the
start date, the command returns no log
events.
-ActivityCode
activity_code
-ac
Optional. Returns log events based on the

activity code.
Use the wildcard symbol (*) to retrieve log
events for multiple activity codes. Valid
activity codes include:
- CCM_10437. Indicates that an activity
succeeded.
- CCM_10438. Indicates that an activity
failed.
-ActivityText
activity_text
-atxt
Optional. Returns log events based on a

string found in the activity text.
Use the wildcard symbol (*) to retrieve logs
for multiple events. For example, the
following parameter returns all log events
that contain the phrase "Enabling service"
in their description:
"*Enabling service*"
If you use the wildcard symbol, enclose the
argument in quotation marks.
-ReverseOrder
true
Optional. Prints log events in reverse

chronological order. If you do not specify
this parameter, the command displays log
events in chronological order.
output_file_name
Optional. Name of the output file. If you do

not specify this parameter, the command
displays the log on the command line.
-ro
-OutputFile
-lo
-Format
output_format_BIN_TEXT_XML
-fm
Optional. Format of the log output file.

Valid formats include:
- Bin (binary)
- Text
- XML
Default format is text. If you set the format

to binary, then you must specify a file name
using the -OutputFile option.
384
GetWorkflowLog
Gets log events for the most recent run of a workflow. The PowerCenter Repository Service must be running
when you run this command.
The infacmd isp GetWorkflowLog command uses the following syntax:
GetWorkflowLog
[<-RepositoryDomain|-rd> domain_of_repository]
<-FolderName|-fn> repository_folder_name
[<-RunInstance|-in> run_instance_name] | <-RunId|-id> workflow_run_id]
Note: If you do not specify -un, -pd, and -sdn options, the infacmd isp GetWorkflowLog command uses the
corresponding values from the -ru, -rp, and the -rsdn options.
The following table describes infacmd isp GetWorkflowLog options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
GetWorkflowLog
385
Option
Argument
Description
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port
gateway_host2:port
...
ResilienceTimeout

-re
onds

to establish or reestablish a connection to the domain. If you
-Format
format
Optional. Format for the session log. Valid types include:
-fm
- Text
- XML
- Bin (binary)
If you choose binary, then you must specify a file name

using the OutputFile option.
-OutputFile
output_file_name
Name and file path for the workflow log file. By default, the
Service Manager uses the server\infa_shared\log directory
on the master gateway node. Omit this option to display the
log events on the screen. If you choose binary as the output
file type, you must specify a file name using this option.
integration_service_na
me
Required. Name of the Integration Service that runs the

workflow. To enter a name that contains a space or other
marks.
me
Required. Name of the Repository Service that contains the

workflow. To enter a name that contains a space or other
marks.
-lo
IntegrationService
-is
-RepositoryService
-rs
386
Option
Argument
Description
-RepositoryDomain
domain_of_repository
Required if the repository is in a domain other than the local

domain. Domain of the Repository Service. To enter a name
that contains a space or other non-alphanumeric character,
user

domain uses Kerberos authentication. User name used to
connect to the repository. To enter a name that contains a
password

domain uses Kerberos authentication. User password. You
can set a password with the -rp option or the environment
variable INFA_REPOSITORY_PASSWORD. If you set a
password with both methods, the password set with the -rp
repository_user_securit
y_domain
Required for LDAP or Kerberos authentication. Optional if

the domain uses native authentication. Name of the security
domain to which the PowerCenter repository user belongs.
-rd
-RepositoryUser
-ru
-RepositoryPassword
-rp
yDomain
-rsdn
-FolderName

repository_folder_name
Required. Name of the folder containing the workflow. To

marks.
workflow_name
Required. Name of the workflow. To enter a name that

contains a space or other non-alphanumeric character,
run_instance_name
Name of the workflow run instance. Use this option if you

are running concurrent workflows. Use the -in or the -id
option, not both.
workflow_run_id
Run identifier number (Run ID) of the workflow run instance.

Use this option if you are running concurrent workflows. Use
the -in or the -id option, not both.
Note: Use this option if the workflow does not have a unique
run instance name.
-fn
-Workflow
-wf
-RunInstance
-in
-RunId
-id
Help
Displays the options and arguments for an infacmd command.
If you omit the command name, infacmd lists all commands.
The infacmd Help command uses the following syntax:
Help <-plugin_ID> [command]
Help
387
For example, if you type infacmd isp Help GetServiceStatus, infacmd returns the following options and
arguments for the infacmd isp GetServiceStatus command:
GetServiceStatus
<-DomainName|-dn> domain_name <-UserName|-un> user_name <-Password|-pd> password [<Gateway|-hp> gateway_host1:port gateway_host2:port...]
[<-ResilienceTimeout|-re> timeout_period_in_seconds] <-ServiceName|-sn> service_name
The following table describes the infacmd Help option and arguments:
Option
Argument
Description
plugin_ID
Optional. Describes which infacmd program to display help for. Default is isp.
command
Optional. Name of command. If you omit the command name, infacmd lists all
commands.
ImportDomainObjects
Imports native users, native groups, roles, and connections from an XML file into an Informatica domain.
If you do not want to import all objects in the file, use an infacmd import control file to filter the objects that
you want to import.
Use the ExportDomainObjects and ImportDomainObjects commands to migrate objects between two different
domains of the same version. To import native users and groups from domains of different versions, use the
infacmd isp ImportUsersAndGroups command.
When you import a group, you import all subgroups and users in the group.
The infacmd isp ImportDomainObjects command uses the following syntax:
ImportDomainObjects
<-ImportFilePath|-fp> import_file_path
[<-ImportControlFile|-cp> import_control_file]
[<-ConflictResolution|-cr> resolution_type]
388
The following table describes infacmd isp ImportDomainObjects options and arguments:
Option
Argument
Description
-DomainName
domain_name
Required. Name of the

Informatica domain. You
can set the domain name
with the -dn option or the
INFA_DEFAULT_DOMAI
N. If you set a domain
name with both methods,
the -dn option takes
precedence.
user_name
Required if the domain

uses Native or LDAP
authentication. User
name to connect to the
domain. You can set the
user name with the -un
option or the environment
variable
INFA_DEFAULT_DOMAI
N_USER. If you set a
user name with both
methods, the -un option
takes precedence.
-dn
-UserName
-un
Optional if the domain

uses Kerberos
authentication. To run the
command with single
sign-on, do not set the
user name. If you set the
user name, the command
runs without single signon.
-Password
-pd
password
Required if you specify

the user name. Password
for the user name. The
password is case
sensitive. You can set a
password with the -pd
variable
INFA_DEFAULT_DOMAI
N_PASSWORD. If you
set a password with both
methods, the password
set with the -pd option
takes precedence.
ImportDomainObjects
389
Option
Argument
Description
-SecurityDomain
security_domain
Required if the domain

uses LDAP
authentication. Optional if
the domain uses native
authentication or
Name of the security
domain to which the
domain user belongs.
You can set a security
domain with the -sdn
variable
INFA_DEFAULT_SECUR
ITY_DOMAIN. If you set
a security domain name
with both methods, the sdn option takes
precedence. The security
domain name is case
sensitive.
-sdn
If the domain uses native

or LDAP authentication,
the default is Native. If
the domain uses
Kerberos authentication,
the default is the LDAP
security domain created
during installation. The
name of the security
domain is the same as
the user realm specified
-Gateway
gateway_host1:port gateway_host2:port ...
Required if the gateway

connectivity information
in the domains.infa file is
out of date. The host
names and port numbers
for the gateway nodes in
the domain.
Optional. Amount of time

in seconds that infacmd
attempts to establish or
re-establish a connection
to the domain. If you omit
this option, infacmd uses
the timeout value
specified in the
INFA_CLIENT_RESILIE
NCE_TIMEOUT
environment variable. If
no value is specified in
the environment variable,
the default of 180
seconds is used.
-hp
-ResilienceTimeout
-re
390
Option
Argument
Description
-ImportFilePath
import_file_path
Required. Path and file

name of the XML file
from which you import
the objects.
import_control_file
Optional. Path and file

name of the import
control file that filters the
objects that are imported.
resolution_type
Optional. Conflict
resolution strategy. You
can specify one of the
following options:
-fp
-ImportControlFile
-cp
-ConflictResolution
-cr
- rename
- replace
- reuse
The option is ignored if

you specify a conflict
resolution strategy in the
import control file. If you
do not define a conflict
resolution strategy and a
conflict occurs, the
import fails.
ImportUsersAndGroups
Imports native users and groups into the domain.
Run infacmd isp ImportUsersAndGroups to import users and groups from an XML file.
The infacmd isp ImportUsersAndGroups command uses the following syntax:
<-ExportFile|-ef> export_file_name
[<-ReuseDomainUsersAndGroups|-rd> If there is a conflict use the users and groups
defined in the target domain]
391
[<-exportedFromPowercenter|-epc> The export file containing users and groups has been
exported from an Informatica PowerCenter 8.6.1 domain]
The following table describes infacmd isp ImportUsersAndGroups options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

sign-on, do not set the user name. If you set
the user name, the command runs without
single sign-on.
-Password
password

case sensitive. You can set a password with
the -pd option or the environment variable
precedence.
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
392
gateway_host1:port

date. The host names and port numbers for the
gateway nodes in the domain.
Option
Argument
Description
-ResilienceTimeout

connection to the domain. If you omit this
specified in the
seconds is used.
export_file_name
Required. Name and file path of the export file

that contains the information about the users
and groups.
Optional. If there is a name conflict, infacmd

retains the users and groups defined in the
target domain. By default, the command fails if
it encounters a conflict.
Required if the export file was exported from a

PowerCenter version 8.6.1 domain.
-re
-ExportFile
-ef
ReuseDomainUsersAndGroups
-rd
-exportedFromPowercenter
-epc
Related Topics:
ExportUsersAndGroups on page 362
ListAlertUsers
Lists users that subscribe to alerts.
The infacmd isp ListAlertUsers command uses the following syntax:
ListAlertUsers
ListAlertUsers
393
The following table describes infacmd isp ListAlertUsers options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
-ResilienceTimeout
-re
394
gateway_host1:port
gateway_host2:port
...

conds

ListAllGroups
Lists all the groups in the native security domain.
The infacmd isp ListAllGroups command uses the following syntax:
ListAllGroups
The following table describes the infacmd isp ListAllGroups options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

ListAllGroups
395
Option
Argument
Description
-Gateway
gateway_host1:port

onds

-hp
-ResilienceTimeout
-re
ListAllRoles
Lists all the roles in the domain.
The infacmd isp ListAllRoles command uses the following syntax:
ListAllRoles
The following table describes the infacmd isp ListAllRoles options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

396
Option
Argument
Description
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
-ResilienceTimeout
-re
gateway_host1:port

onds

ListAllUsers
Lists all the user accounts in the domain.
The infacmd isp ListAllUsers command uses the following syntax:
ListAllUsers
ListAllUsers
397
The following table describes the infacmd isp ListAllUsers options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-ResilienceTimeout

-re
398
ListConnectionPermissions
Lists the permissions that a user or group has for a connection.
The infacmd isp ListConnectionPermissions command uses the following syntax:
The following table describes infacmd isp ListConnectionPermissions options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

sign-on.
-Password
-pd
password

399
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

installation.
-ResilienceTimeout
-re
ds

seconds is used.
-RecipientUserName
recipient_user_name

name. Name of the user to list permissions for.

name. Name of the group to list permissions for.
nth_name

ty_domain
Required. Name of the connection.
-run
-RecipientGroupName
-rgn
-rsd
-ConnectionName
-cn
ListConnectionPermissionsByGroup
Lists all groups that have permissions on a connection and lists the type of permissions.
The infacmd isp ListConnectionPermissionsByGroup command uses the following syntax:
400
The following table describes infacmd isp ListConnectionPermissionsByGroup options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

sign-on.
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

installation.
401
Option
Argument
Description
-ResilienceTimeout
ds

seconds is used.
ty_domain
-re
-ConnectionName
-cn
ListConnectionPermissionsByUser
Lists the users that have permissions for a connection and lists the type of permissions.
The infacmd isp ListConnectionPermissionsByUser command uses the following syntax:
402
The following table describes infacmd isp ListConnectionPermissionsByUser options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

sign-on.
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

installation.
403
Option
Argument
Description
-ResilienceTimeout
ds

seconds is used.
ty_domain
-re
-ConnectionName
-cn
ListConnections
Lists each connection type and the connection object names for each connection type. Lists all valid
connection types.
The infacmd isp ListConnections command uses the following syntax:
ListConnections
404
The following table describes infacmd isp ListConnections options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

sign-on.
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

installation.
-ResilienceTimeout
-re
ds

seconds is used.
ListConnections
405
ListConnectionOptions
Lists options for a connection. Run this command to view available options to configure when you update a
connection.
The infacmd isp ListConnectionOptions command uses the following syntax:
ListConnectionOptions
The following table describes infacmd isp ListConnectionOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

sign-on.
-Password
-pd
406
password

Option
Argument
Description
-SecurityDomain
security_domain

-sdn

installation.
-ResilienceTimeout
-re
-ConnectionName
-cn
ds

seconds is used.
ty_domain
ListDomainLinks
Lists the domains to which the local domain can connect. You establish links between two domains if you
want to exchange repository metadata between them.
The infacmd isp ListDomainLinks command uses the following syntax:
ListDomainLinks
ListDomainLinks
407
The following table describes infacmd isp ListDomainLinks options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
-ResilienceTimeout
-re
408
gateway_host1:port
gateway_host2:port
...

conds

establish or re-establish a connection to the local domain. If
you omit this option, infacmd uses the timeout value specified
in the INFA_CLIENT_RESILIENCE_TIMEOUT environment
ListDomainOptions
Lists general properties of the domain. Properties include resilience timeout, limit on resilience timeouts,
maximum restart attempts, restart period, SSL mode, and dispatch mode.
To run the infacmd isp ListDomainOptions command, you must have permission on the domain.
The infacmd isp ListDomainOptions command uses the following syntax:
ListDomainOptions
The following table describes infacmd isp ListDomainOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
-pd
password
ListDomainOptions
409
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
-hp
-ResilienceTimeout
-re
gateway_host1:port
gateway_host2:port
...

conds

ListFolders
Lists the folders in the domain.
The infacmd isp ListFolders command uses the following syntax:
ListFolders
410
The following table describes infacmd isp ListFolders options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
-ResilienceTimeout
-re
gateway_host1:port
gateway_host2:port
...

conds

ListGridNodes
Lists the nodes assigned to a grid.
To run the infacmd isp ListGridNodes command, you must have permission on the grid.
ListGridNodes
411
The infacmd isp ListGridNodes command uses the following syntax:

ListGridNodes
The following table describes infacmd isp ListGridNodes options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
412
gateway_host1:port
gateway_host2:port
...

Option
Argument
Description
-ResilienceTimeout
-re
conds

-GridName
grid_name
-gn
ListGroupPermissions
Lists group permissions on an object.
The infacmd isp ListGroupPermissions command uses the following syntax:
[<-ExistingGroupSecurityDomain|-egn> existing_group_security_domain]
[<-ObjectType|-ot> object_type_SERVICE_LICENSE_NODE_GRID_FOLDER_OSPROFILE]
413
The following table describes infacmd isp ListGroupPermissions options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

sign-on.
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

installation.
414
-Gateway
gateway_host1:port
-hp

in the domains.infa file if out of date. The host
in the domain.
Option
Argument
Description
-ResilienceTimeout
-re
ds

seconds is used.
-ExistingGroup
existing_group_name

-egn
existing_group_security_
domainth_name

Default is Native.
-ObjectType
object_type
Required. Type of object you want to list:
-eg
-ExistingGroupSecurityDomain
-ot
Service
License
Node
Grid
Folder
OSProfile
ListGroupPrivileges
Lists privileges assigned to a group in the domain. You can list group privileges for each application in the
domain.
The infacmd isp ListGroupPrivileges command uses the following syntax:
ListGroupPrivileges
ListGroupPrivileges
415
The following table describes infacmd isp ListGroupPrivileges options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
gateway_host1:port

-re
nds

-GroupName
group_name
Required. Name of the group for which you want to list

privileges.
-hp
-ResilienceTimeout
-gn
416
Option
Argument
Description

security domain that the group for which you want to list
privileges belongs to. Default is Native.
service_name

you want to view privileges.
-gsf
-ServiceName
-sn
ListGroupsForUser
Lists the native groups to which the user is assigned.
The infacmd isp ListGroupsForUser command uses the following syntax:
ListGroupsForUser
The following table describes infacmd isp ListGroupsForUser options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

ListGroupsForUser
417
Option
Argument
Description
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port

domain.
-re
onds

used.
-ExistingUserName
existing_user_Name
Required. Name of the user for which you want to

list the groups.
domain

the security domain to which the user belongs.
Default is Native.
-hp
-ResilienceTimeout
-eu
-esd
ListLDAPConnectivity
Lists the connection information for an LDAP server.
The infacmd isp ListLDAPConnectivity command uses the following syntax:
418
The following table describes infacmd isp ListLDAPConnectivity options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
419
Option
Argument
Description
-Gateway
gateway_host1:port

nds

-hp
-ResilienceTimeout
-re
ListLicenses
Lists the licenses in the domain. You can display the license name and serial number for each license.
To run the infacmd isp ListLicenses command, you must have permission on the licenses.
The infacmd isp ListLicenses command uses the following syntax:
ListLicenses
[<-Gateway|-hp> gateway_host1:port gateway_host2:port ...]
The following table describes infacmd isp ListLicenses options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

420
Option
Argument
Description
-Password
password
precedence.
security_domain

sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
-hp
-ResilienceTimeout
-re
gateway_host1:port
gateway_host2:port
...

timeout_period_in_s
econds

ListMonitoringOptions
List monitoring general properties.
The infacmd isp listMonitoringOptions command uses the following syntax:
listMonitoringOptions
ListMonitoringOptions
421
The following table describes infacmd isp listMonitoringOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-ResilienceTimeout
Optional. Amount of seconds that infacmd attempts to

establish a connection to the domain. You can set the
resilience timeout period with the -re option or the
takes precedence. Default is 180 seconds.
-re
422
ListNodeOptions
Lists general properties for a node. General properties include backup directory, CPU profile, error severity
level, maximum and minimum process ports, and resource provision thresholds.
To run the infacmd isp ListNodeOptions command, you must have permission on the node.
The infacmd isp ListNodeOptions command uses the following syntax:
ListNodeOptions
The following table describes infacmd isp ListNodeOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
-pd
password
ListNodeOptions
423
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-NodeName
node_name
Required. Name of the node for which you want to list the
options.
-hp
-ResilienceTimeout
-nn
ListNodeResources
Lists all resources defined for a node. For each resource, this command returns the resource type and
whether the resource is available.
To run the infacmd isp ListNodeResources command, you must have permission on the node.
The infacmd isp ListNodeResources command uses the following syntax:
ListNodeResources
424
The following table describes infacmd isp ListNodeResources options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
timeout_period_in_s
econds

-NodeName
node_name
Required. Name of the node for which you want to list the
resources.
resource_category
Optional. Category of resources that you want to list. Valid

categories include:
-hp
-ResilienceTimeout
-nn
-ResourceCategory
-rc

Default is PCIS.
ListNodeResources
425
ListNodeRoles
Lists all roles on a node in the domain.
The infacmd isp ListNodeRoles command uses the following syntax:
ListNodeRoles
The following table describes infacmd isp ListNodeRoles options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

426
Option
Argument
Description
-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-NodeName
node_name
Required. Name of the node.
-hp
-ResilienceTimeout
-nn
ListNodes
Lists the nodes in the domain. If you do not use the node role option, the command lists all the nodes in the
domain. If you use the node role option, the command lists the nodes with the specified role.
The infacmd isp ListNodes command uses the following syntax:
ListNodes
[<-NodeRole|-nr> node_role SERVICE|COMPUTE|SERVICE_COMPUTE]
ListNodes
427
The following table describes infacmd isp ListNodes options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-NodeRole
node_role
Optional. Role enabled on the nodes that you want to list.

-hp
-ResilienceTimeout
-nr
- Service. Lists nodes with at least the service role.

- Compute. Lists nodes with at least the compute role.
- Service_compute. Lists nodes with both the service and
compute roles.
If you omit the option, the command lists all nodes in the
domain.
428
ListOSProfiles
Lists the operating system profiles in the domain.
The infacmd isp ListOSProfile command uses the following syntax:
ListOSProfiles
The following table describes infacmd isp ListOSProfile options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

-pd
-SecurityDomain
-sdn

ListOSProfiles
429
Option
Argument
Description
-Gateway
gateway_host1:port
gateway_host2:port
...

conds

-hp
-ResilienceTimeout
-re
ListRepositoryLDAPConfiguration
Lists the LDAP server configuration options such as LDAP server address, search scope, and login
attributes.
Use this command after you install Informatica to verify the connection between the domain and the LDAP
external directory service.
Use infacmd isp SetRepositoryLDAPConfiguration to update the LDAP server configuration options for an
Informatica domain. You use this command when you upgrade a repository that uses LDAP authentication.
The infacmd isp ListRepositoryLDAPConfiguration command uses the following syntax:
430
The following table describes infacmd isp ListRepositoryLDAPConfiguration options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
-ResilienceTimeout
-re
gateway_host1:port

nds

431
ListRolePrivileges
Lists privileges assigned to a role in the domain. You can list role privileges for each application service in
the domain.
You can list privileges assigned to a role for the domain and for each application service type in the domain.
The infacmd isp ListRolePrivileges command uses the following syntax:
ListRolePrivileges
The following table describes ListRolePrivileges options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

single sign-on.
-Password
password
-pd
432

Option
Argument
Description
-SecurityDomain
security_domain

sensitive.
-sdn

installation.
-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-RoleName
role_name
Required. Name of the role to list privileges for. To enter a

-hp
-ResilienceTimeout
-rn
ListSecurityDomains
Lists the native and LDAP security domains in the domain.
The infacmd isp ListSecurityDomains command uses the following syntax:
ListSecurityDomains
ListSecurityDomains
433
The following table describes the infacmd isp ListSecurityDomains options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
-ResilienceTimeout
-re
434
gateway_host1:port

onds

ListServiceLevels
Lists the service levels defined for the domain. You can list the name, dispatch priority, and maximum
dispatch wait time for each service level.
The infacmd isp ListServiceLevels command uses the following syntax:
ListServiceLevels
The following table describes infacmd isp ListServiceLevels options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

ListServiceLevels
435
Option
Argument
Description
-Gateway
gateway_host1:port
gateway_host2:port
...

conds

-hp
-ResilienceTimeout
-re
ListServiceNodes
Lists the nodes or grid assigned to a service.
If this command returns a grid name, you can run the infacmd isp ListGridNodes command to list the nodes in
the grid.
To run the infacmd isp ListServiceNodes command, you must have permission on the service.
The infacmd isp ListServiceNodes command uses the following syntax:
ListServiceNodes
436
The following table describes infacmd isp ListServiceNodes options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-ServiceName
service_name
Required. Name of the service.
-hp
-ResilienceTimeout
-sn
ListServiceNodes
437
Related Topics:
ListGridNodes on page 411
ListServicePrivileges
Lists the privileges for a domain or application service type.
The infacmd isp ListServicePrivileges command uses the following syntax:
ListServicePrivileges
[<-ServiceType|-st> service_type AS|CMS|MM|MRS|RPS|RS|DOMAIN]
The following table describes infacmd isp ListServicePrivileges options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
-pd
438
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-ServiceType
service_type
Optional. Domain or application service type for which you

want to view privileges.
-hp
ResilienceTimeout
-st

-
AS. Analyst Service

DOMAIN. Domain
ListServices
Lists the services in the domain.
The infacmd isp ListServices command uses the following syntax:
ListServices
ListServices
439
[<-ServiceType|-st> service_type AS|BW|CMS|DIS|IS|MM|MRS|RPS|RS|WS|ES|SCH|RMS|SEARCH]

The following table describes infacmd isp ListServices options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

command with single sign-on, do not set the user name. If you set
the user name, the command runs without single sign-on.
-Password
password
precedence.
gateway_host1:port
gateway_host2:port
...

domains.infa file is out of date. The host names and port numbers
for the gateway nodes in the domain.
-pd
-Gateway
-hp
440
Option
Argument
Description
-ResilienceTimeout
-re
timeout_period_in_s
econds

-ServiceType
service_type
-st
Optional. List all services of a specific type.

-
AS. Analyst Service

BW. SAP BW Service
DIS. Data Integration Service
IS. PowerCenter Integration Service
WS. Web Service Hub
ES. Email Service
SCH. Scheduler Service
RMS. Resource Manager Service
SEARCH. Search Service
ListSMTPOptions
Lists the SMTP configuration properties for the domain. The SMTP configuration is used to send domain
alerts and scorecard notifications.
The infacmd isp ListSMTPOptions command uses the following syntax:
ListSMTPOptions
ListSMTPOptions
441
The following table describes infacmd isp ListSMTPOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
-ResilienceTimeout
-re
442
gateway_host1:port
gateway_host2:port
...

conds

Related Topics:
UpdateSMTPOptions on page 563
ListUserPermissions
Lists the domain objects on which a user has permissions.
The infacmd isp ListUserPermissions command uses the following syntax:
ListUserPermissions
[<-ObjectType|-ot> object_type_SERVICE_LICENSE_NODE_GRID_FOLDER_OSPROFILE]
The following table describes infacmd isp ListUserPermissions options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

sign-on.
ListUserPermissions
443
Option
Argument
Description
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

installation.
-Gateway
gateway_host1:port
-hp
-ResilienceTimeout
-re
ds

seconds is used.
-ExistingUserName
existing_user_name
Required. User account for which you want to list

privileges. To enter a name that contains space
or other non-alphanumeric character, enclose
-esd
existing_user_security_d
omainth_name

of the security domain that the user for which
you want to list privileges belongs to. Default is
Native.
-ObjectType
object_type
Required. Type of object you want to list:
-eu
-ot
444

in the domains.infa file if out of date. The host
in the domain.
Service
License
Node
Grid
Folder
OSProfile
ListUserPrivileges
Lists privileges assigned to a user in the domain. You can list user privileges for each application service in
the domain.
The infacmd isp ListUserPrivileges command uses the following syntax:
ListUserPrivileges
The following table describes the infacmd isp ListUserPrivileges options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
-pd
password

ListUserPrivileges
445
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port

domain.
-re
nds

used.
ExistingUserName
existing_user_name
Required. User account for which you want to list

privileges. To enter a name that contains a space or
other non-alphanumeric character, enclose the
-esd
domain

the security domain that the user for which you want
to list privileges belongs to. Default is Native.
-ServiceName
service_name

-hp
-ResilienceTimeout
-eu
-sn
migrateUsers
Migrates the groups, roles, privileges, and permissions of users in the native security domain to users in one
or more LDAP security domains. Before you configure a domain to use Kerberos authentication, you must
migrate the users to an LDAP security domain.
For more information about the migrateUsers command, see the Informatica Security Guide.
446
The infacmd isp migrateUsers command uses the following syntax:

migrateUsers
<-UserName|-un> administrator_user_name
<-Password|-pd> administrator_password
[<-SecurityDomain|-sdn>|security_domain]
[<-Gateway|-hp>|gateway_host1:port gateway_host2:port...]
[<-ResilienceTimeout|-re> timeout_period_in_seconds ]
<-UserMigrationFile|-umf> user_migration_file
The following table describes infacmd isp migrateUsers options and arguments:
Option
Argument
Description
-DomainName
domain_name

administrator_user_na
me
Required. User name to connect to the domain. You can set

the user name with the -un option or the environment
variable INFA_DEFAULT_DOMAIN_USER. If you set a user
name with both methods, the -un option takes precedence.
-pd
administrator_passwor
d
Required. Password for the user name. The password is

case sensitive. You can set a password with the -pd option
-SecurityDomain
security_domain
Optional. Name of the security domain to which the domain

user belongs. You can set a security domain with the -sdn
Note: This security domain is the security domain of the user
account used to connect to the domain, not the security
domain to which the users will be migrated.
-Gateway
gateway_host1:port
-hp
gateway_host2:port
Optional. Use if the gateway connectivity information in the

-dn
-UserName
-un
-Password
-sdn
...
migrateUsers
447
Option
Argument
Description
-ResilienceTimeout
-re
onds

to establish or re-establish a connection to the domain. You
can set the resilience timeout period with the -re option or
takes precedence.
-UserMigrationFile
user_migration_file
Required. Path and file name of the user migration file. The
user migration file is a text file that contains the list of native
users and the corresponding LDAP users. Entries must be in
-umf
Native/<SourceUserName>,LDAP/
<TargetUsername>
For example, to migrate a user named User1 from the native
security domain to a user named User1 in an LDAP security
domain, add the following line to the user migration file:
Native/User1,LDAP/User1
The command skips entries with a duplicate source user
name or target user name.
MoveFolder
Moves a folder.
The infacmd isp MoveFolder command uses the following syntax:
MoveFolder
<-OriginalPath|-op> original_folder_path
448
The following table describes infacmd isp MoveFolder options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-OriginalPath
original_folder_path
Required. Full path, excluding the domain name, to the folder

you want to move. Must be in the following format:
-hp
-ResilienceTimeout
-op
-FolderPath
-fp
full_folder_path
Required. Full path, excluding the domain name, to the target

folder location. Must be in the following format:
MoveFolder
449
MoveObject
Moves an object to another folder.
The infacmd isp MoveObject command uses the following syntax:
MoveObject
<-ObjectType|-ot> object_type_SERVICE_LICENSE_NODE_GRID
The following table describes infacmd isp MoveObject options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
-pd
450
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-ObjectName
object_name
Required. Name of the object you want to move.
-hp
-ResilienceTimeout
-on
-ObjectType
object_type
-ot
Required. Type of object you want to move:

- Service
- License
- Node
- Grid
-FolderPath
-fp
full_folder_path

into which you want to move the object. Must be in the
following format:
Ping
Pings a domain, service, domain gateway host, or node. If the object is available, this command displays a
message that the object is available at a specific port on the gateway host machine. If the object is
unavailable, this command displays a message saying that it failed to receive a response from the object.
Use this command to troubleshoot network connections. To run the infacmd isp Ping command, you must
have permission on the object you want to ping.
The infacmd isp Ping command does not display results for individual service processes.
Ping
451
The infacmd isp Ping command uses the following syntax:

Ping
[<-DomainName|-dn> domain_name]
[<-GatewayAddress|-dg> domain_gateway_host:port]
[<-NodeName|-nn> node_name]
The following table describes infacmd isp Ping options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
Optional. Name of the service you want to ping. To enter a

-dg
domain_gateway_host:
port
Required if you do not specify the -DomainName option, or if

you need to ping another domain. Gateway host machine
name and port number.
-NodeName
node_name
Optional. Name of the node.
onds

-dn
-ServiceName
-sn
-GatewayAddress
-nn
-ResilienceTimeout
-re
PrintSPNAndKeytabNames
Generates the list of SPN and keytab file names for the nodes and services in the domain. The Informatica
domain requires a keytab file for each SPN. You might need to ask the Kerberos administrator to add the
SPNs to the principal database and create the keytab files. The SPN and keytab file names are case
sensitive.
The infacmd isp PrintSPNAndKeytabNames command uses the following syntax:
<-ServiceRealmName|-srn> realm_name_of_node_spn
[<-OutputFile|-of> output_file_name]
452
[<-DomainNodes|-dns> Node1:HostName1 Node2:HostName2 ...]

[<-ServiceProcesses|-sps> ServiceName1:NodeName1 ServiceName2:NodeName2...]
[<-SPNShareLevel|-spnSL> SPNShareLevel PROCESS|NODE]
The following table describes infacmd isp PrintSPNAndKeytabNames options and arguments:
Option
Argument
Description
-DomainName
domain_name

-srn
realm_name_of_node
_spn
Required. Name of the Kerberos realm to which the

Informatica domain services belong. The realm name must be
in uppercase and is case sensitive.
-Format
format_TEXT_CSV
-dn
-ServiceRealmName

- Text
- CSV
-fm

-OutputFile
output_file_name
-of
-DomainNodes
-dns

If you do not specify an output file name, infacmd displays the
log events on the screen.
NodeName:HostNam
e
[NodeName:Hostnam
e]
Name of the node and the fully qualified host name of the
machine that hosts the node. Use the following format:
NodeName:HostName
You can generate SPNs and keytab file names for multiple
nodes. Separate each node name and host name pair with a
space.
453
Option
Argument
Description
-ServiceProcesses
ServiceName:Noden
ame
Optional. Name of the service that you want to create in the

Informatica domain and the name of the node on which the
service will run. Use the following format:
ServiceName:NodeName
-sps
[ServiceName:Noden
ame]
You can generate SPNs and keytab file names for multiple
services. Separate each service name and node name pair
with a space.
Note: The keytab files for application services in the domain
do not have to be available when you configure the domain to
use Kerberos authentication. You can add the service SPN to
the principal database and create the keytab after you change
the Informatica domain authentication but before you enable
the service.
SPNShareLevel
SPNShareLevel
-spnSL
PROCESS|NODE]
Optional. Indicates the service principal level for the domain.

Set the property to one of the following levels:
- Process. The domain requires a unique service principal name
(SPN) and keytab file for each node and each service on a
node. The number of SPNs and keytab files required for each
node depends on the number of service processes that run on
the node. Recommended for production domains.
- Node. The domain uses one SPN and keytab file for the node
and all services that run on the node. It also requires a
separate SPN and keytab file for all HTTP processes on the
node. Recommended for test and development domains.
Recommended for test and development domains.
Default is process.
PurgeLog
Purges log events. You can purge log events for a domain or for application services, such as the
PowerCenter Integration Service, the Data Integration Service, and the Web Services Hub.
The infacmd isp PurgeLog command uses the following syntax:
PurgeLog
<-BeforeDate|-bd> before_date
[<-LicenseUsage|-lu>]
454
The following table describes infacmd isp PurgeLog options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-BeforeDate
before_date
Required. Purges log events that occurred before this date and
time. Enter date and time in one of the following formats:
-hp
-ResilienceTimeout
-bd
-LicenseUsage
-lu
- MM/dd/yyyy
- yyyy-MM-dd
Optional. Purges log events and database records for license

usage.
PurgeLog
455
PurgeMonitoringData
Purges monitoring data from the Model repository.
The infacmd isp purgeMonitoringData command uses the following syntax:
purgeMonitoringData
[<-NumDaysToRetain|-ndr> num_days_to_retain]
[<-NumDaysToRetainDetailedStat|-ndrds> num_days_to_retain_detailed_stat]
The following table describes infacmd isp purgeMonitoringData options and arguments:
Option
Argument
Description
-DomainName
domain_name
Required. Name of the Informatica

domain. You can set the domain name
with the -dn option or the environment
variable INFA_DEFAULT_DOMAIN. If
you set a domain name with both
methods, the -dn option takes
precedence.
user_name

LDAP authentication. User name to
connect to the domain. You can set the
user name with the -un option or the
INFA_DEFAULT_DOMAIN_USER. If you
set a user name with both methods, the un option takes precedence.
-dn
-UserName
-un

single sign-on, do not set the user name.
If you set the user name, the command
-Password
-pd
456
password

Password for the user name. The
password is case sensitive. You can set
a password with the -pd option or the
INFA_DEFAULT_DOMAIN_PASSWORD.
If you set a password with both methods,
the password set with the -pd option
takes precedence.
Option
Argument
Description
-SecurityDomain
security_domain

authentication. Optional if the domain
uses native authentication or Kerberos
domain to which the domain user
belongs. You can set a security domain
with the -sdn option or the environment
variable
INFA_DEFAULT_SECURITY_DOMAIN.
If you set a security domain name with
both methods, the -sdn option takes
precedence. The security domain name
is case sensitive.
-sdn

authentication, the default is Native. If
the domain uses Kerberos
authentication, the default is the user
realm specified during installation.
-Gateway
-hp
gateway_host1:port

information in the domains.infa file is out
of date. The host names and port
numbers for the gateway nodes in the
domain.
-ResilienceTimeout
Optional. Amount of seconds that

infacmd attempts to establish a
connection to the domain. You can set
the resilience timeout period with the -re
INFA_CLIENT_RESILIENCE_TIMEOUT.
If you set the resilience timeout period
with both methods, the -re option takes
precedence. Default is 180 seconds.
-re
PurgeMonitoringData
457
Option
Argument
Description
-NumDaysToRetain
num_days_to_retain
Optional. Number of days of averaged

data to retain in the Model repository.
-ndr
For example, if you enter 180, then the

Model Repository Service purges all
averaged data that is older than 180
days.
If you do not configure this option, then
PurgeMonitoringData purges all of the
averaged monitoring data in the Model
repository.
Minimum is 0. Maximum is 366.
NumDaysToRetainDetailedStat
num_days_to_retain_detailed_stat
-ndrds
Optional. Number of days of per-minute

data to retain in the Model repository.
For example, if you enter 7, then the
Model Repository Service purges all
averaged data that is older than 7 days.
If you do not configure this option, then
PurgeMonitoringData purges all of the
per-minute monitoring data in the Model
repository.
Minimum is 0. Maximum is 14.
RemoveAlertUser
Unsubscribes a user from alert notification emails. You can run infacmd isp RemoveAlertUser for any user.
The infacmd isp RemoveAlertUser command uses the following syntax:
RemoveAlertUser
<-AlertUser|-au> user_name
458
The following table describes infacmd isp RemoveAlertUser options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-AlertUser
user_name
Required. Name of user you want to unsubscribes from alerts.
-hp
-ResilienceTimeout
-au
RemoveAlertUser
459
RemoveConnection
Removes a connection from the domain.
The infacmd isp RemoveConnection command uses the following syntax:
RemoveConnection
The following table describes infacmd isp RemoveConnection options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

sign-on.
-Password
-pd
460
password

Option
Argument
Description
-SecurityDomain
security_domain

-sdn

installation.
-ResilienceTimeout
-re
ds

seconds is used.
-ConnectionName
connection_name
Name of the connection to remove.
-cn
RemoveConnectionPermissions
Removes connection permissions for a user or group.
The infacmd isp RemoveConnectionPermissions command uses the following syntax:
<<-RecipientUserName|-run> recipient_user_name|<ReceipeintGroupName|-rgn>
recipeint_group_name>
461
The following table describes infacmd isp RemoveConnectionPermissions options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

sign-on.
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

installation.
-ResilienceTimeout
-re
462
ds

seconds is used.
Option
Argument
Description
-RecipientUserName
recipient_user_name

name. Name of the user to remove permissions
from.

name. Name of the group to remove permissions
for the connection.
nth_name

ty_domain
-run
-RecipientGroupName
-rgn
-rsd
-ConnectionName
-cn
RemoveDomainLink
Removes a linked domain. When you remove a linked domain, you cannot exchange repository metadata
between the local and linked domains. You might want to do this if you no longer need to access a
PowerCenter Repository Service in another domain.
The infacmd isp RemoveDomainLink command uses the following syntax:
RemoveDomainLink
<-LinkedDomainName|-ld> linked_domain_name
RemoveDomainLink
463
The following table describes infacmd isp RemoveDomainLink options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

establish or re-establish a connection to the local domain. If
you omit this option, infacmd uses the timeout value specified
in the INFA_CLIENT_RESILIENCE_TIMEOUT environment
-LinkedDomainName
linked_domain_name
Required. Name of the domain from which you want to

remove a connection.
-hp
-ResilienceTimeout
-ld
464
RemoveFolder
Removes a folder from the domain. Before you remove a folder, make sure that the folder is empty.
The folder must be empty.
The infacmd isp RemoveFolder command uses the following syntax:
RemoveFolder
The following table describes infacmd isp RemoveFolder options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
-pd
password
RemoveFolder
465
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-FolderPath
full_folder_path

you want to remove. Must be in the following format:
-hp
-ResilienceTimeout
-fp
RemoveGrid
Removes a grid from the domain. Before you can remove a grid, you must unassign the grid from the
PowerCenter Integration Service or Data Integration Service.
The infacmd isp RemoveGrid command uses the following syntax:
RemoveGrid
466
The following table describes infacmd isp RemoveGrid options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name
Required. User name to connect to the domain. You can set

the user name with the -un option or the environment variable
password
Required. Password for the user name. The password is case

sensitive. You can set a password with the -pd option or the
security_domain

-dn
-UserName
-un
-Password
-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-GridName
grid_name
Required. Name of the grid you want to remove.
-hp
-ResilienceTimeout
-gn
RemoveGroup
Removes a group from the native security domain.
The infacmd isp RemoveGroup command uses the following syntax:
RemoveGroup
RemoveGroup
467
The following table describes infacmd isp RemoveGroup options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
468
gateway_host1:port
gateway_host2:port
...

Option
Argument
Description
ResilienceTimeout
-re
conds

-GroupName
group_name
Required. Name of the group you want to remove.
-gn
RemoveGroupPermission
Removes a group permission on an object.
The infacmd isp RemoveGroupPermission command uses the following syntax:
469
The following table describes infacmd isp RemoveGroupPermission options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

sign-on.
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
470
gateway_host1:port

in the domain.
Option
Argument
Description
-ResilienceTimeout
-re
ds

seconds is used.
-ExistingGroup
existing_group_name


Default is Native.
object_name
Name of the object that you want to remove the

group access permission.
-eg
-gsf
-ObjectName
-on
-ObjectType
-ot
object_type_SERVICE_L
ICENSE_NODE_GRID_
FOLDER_OSPROFILE

-
Service
License
Node
Grid
Folder
OSProfile
RemoveGroupPrivilege
Removes a privilege from a group in the domain. You can remove a privilege from a group for the domain or
an application service in the domain.
The infacmd isp RemoveGroupPrivilege command uses the following syntax:
471
The following table describes infacmd isp RemoveGroupPrivilege options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-GroupName
group_name
Required. Name of the group from which you are removing

quotation marks.
-hp
-ResilienceTimeout
-gn
472
Option
Argument
Description
-gsf
group_security_doma
in

security domain that the group from which you are removing
privileges belongs to. Default is Native.
-ServiceName
service_name
Required. Domain or application service name for which you

want to view privileges.
path_of_privilege

assign to the group. A fully-qualified name includes privilege
group name and privilege name. For example, a fullyqualified privilege name for the Repository Service is folder/
create. If the privilege name includes spaces, enclose the
path in quotation marks as follows:
-sn
-PrivilegePath
-pp
Execution
the escape character \ before it as follows:
RemoveLicense
Removes a license from the domain. Before you run this command, you must first disable the services
assigned to the license.
Removes a license from a domain when it expires or when you want to move the license to another domain.
The infacmd isp RemoveLicense command uses the following syntax:
RemoveLicense
RemoveLicense
473
The following table describes infacmd isp RemoveLicense options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-LicenseName
license_name
Required. Name of the license you want to remove.
-hp
ResilienceTimeout
-ln
Related Topics:
474
DisableService on page 345
UnassignLicense on page 517
RemoveNode
Removes a node from the domain. If the node is running, you must shut it down first.
The infacmd isp RemoveNode command uses the following syntax:
RemoveNode
The following table describes infacmd isp RemoveNode options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

-pd
-SecurityDomain
-sdn

RemoveNode
475
Option
Argument
Description
-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-NodeName
node_name
Required. Name of the node you want to remove.
-hp
-ResilienceTimeout
-nn
RemoveNodeResource
Removes a resource from a node. You can remove a custom or file or directory resource from a node. You
cannot remove a connection resource from a node.
If you remove a resource that is required by the Session or Command task, the task can no longer run on that
node.
The infacmd isp RemoveNodeResource command uses the following syntax:
RemoveNodeResource
<-ResourceType|-rt> resource_type("Custom", "File Directory")
476
The following table describes infacmd isp RemoveNodeResource options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
timeout_period_in_s
econds

-NodeName
node_name
Required. Name of the node that has the resource you want to
remove.
resource_category
Optional. Category of resource you want to remove. Valid

categories include:
-hp
-ResilienceTimeout
-nn
-ResourceCategory
-rc

Default is PCIS.
RemoveNodeResource
477
Option
Argument
Description
-ResourceType
resource_type
Required. Type of resource you want to remove. Valid types

include:
-rt
- Custom
- File Directory
-ResourceName
resource_name
-rn
Required. Entire name of the resource you want to remove.

infacmd isp ListNodeResources command.
RemoveOSProfile
Removes an operating system profile from the domain.
The infacmd isp RemoveOSProfile command uses the following syntax:
RemoveOSProfile
The following table describes infacmd isp RemoveOSProfile options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

478
Option
Argument
Description
-Password
password
precedence.
security_domain

sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-OSProfileName
OSProfile_name
Required. Name of the operating system profile you want to

remove.
-hp
-ResilienceTimeout
-on
RemoveRole
Removes a custom role from the domain. When you remove a custom role, the custom role and all privileges
that it included are removed from any user or group assigned the role.
The infacmd isp RemoveRole command uses the following syntax:
RemoveRole
RemoveRole
479
The following table describes infacmd isp RemoveRole options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-RoleName
role_name
Required. Name of the role you want to remove.
-hp
-ResilienceTimeout
-rn
480
RemoveRolePrivilege
Removes a privilege from a role in the domain or from a role in an application service within the domain.
The infacmd isp RemoveRolePrivilege command uses the following syntax:
RemoveRolePrivileges
<-ServiceType|-st> service_type AS|CMS|MM|MRS|RPS|RS|DOMAIN
The following table describes infacmd isp RemoveRolePrivilege options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

single sign-on.
-Password
-pd
password

RemoveRolePrivilege
481
Option
Argument
Description
-SecurityDomain
security_domain

sensitive.
-sdn

installation.
-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-RoleName
role_name
Required. Name of the role from which you are removing

quotation marks.
service_type
Required. Domain or application service type from which

you want to remove the privilege for the role.
-hp
-ResilienceTimeout
-rn
-ServiceType
-st

-
-PrivilegePath
path_of_privilege
-pp>
AS. Analyst Service

DOMAIN. Domain

assign to the group. A fully-qualified name includes
privilege group name and privilege name. For example, a
fully-qualified privilege name for the Repository Service is
folder/create. If the privilege name includes spaces,
enclose the path in quotation marks as follows:
Execution
the escape character \ before it as follows:
482
RemoveService
Removes an application service from the domain. Before you remove a service, you must disable it.
The infacmd isp RemoveService command uses the following syntax:
RemoveService
The following table describes infacmd isp RemoveService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

-pd
-SecurityDomain
-sdn

RemoveService
483
Option
Argument
Description
-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-ServiceName
service_name
Required. Name of service you want to remove. To enter a

-hp
-ResilienceTimeout
-sn
RemoveServiceLevel
Removes a service level. When you remove a service level, the Workflow Manager does not update tasks
that use the service level. If a workflow service level does not exist in the domain, the Load Balancer
dispatches the tasks with the default service level.
The infacmd isp RemoveServiceLevel command uses the following syntax:
RemoveServiceLevel
484
The following table describes infacmd isp RemoveServiceLevel options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-ServiceLevelName
service_level_name
Required. Name of the service level you want to remove.
-hp
-ResilienceTimeout
-ln
RemoveServiceLevel
485
RemoveUser
Removes a user account from the native security domain. You cannot remove user accounts in the LDAP
security domains.
The infacmd isp RemoveUser command uses the following syntax:
RemoveUser
The following table describes infacmd isp RemoveUser options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
-pd
486
precedence.
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
timeout_period_in_s
econds

-ExistingUserName
existing_user_name
Required. User account you want to remove.
-hp
-ResilienceTimeout
-eu
RemoveUserFromGroup
Removes a native or LDAP user from a native group in the domain.
The infacmd isp RemoveUserFromGroup command uses the following syntax:
RemoveUserFromGroup
RemoveUserFromGroup
487
The following table describes infacmd isp RemoveUserFromGroup options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
488
gateway_host1:port

domain.
Option
Argument
Description
-ResilienceTimeout
-re
onds

used.
-ExistingUserName
existing_user_name
Required. Name of the user you want to remove.
-esd
_domain

the security domain that the user you want to
remove belongs to. Default is Native.
-GroupName
group_name
Required. Name of the group from which you want

to remove the user.
-eu
-gn
RemoveUserPermission
Removes a user permission on an object.
The infacmd isp RemoveUserPermission command uses the following syntax:
489
The following table describes infacmd isp RemoveUserPermission options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

is case sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
-hp
-ResilienceTimeout
-re
490
gateway_host1:port

domain.
onds

Option
Argument
Description
-ExistingUserName
existing_user_name
Required. Name of the user to which you want to

assign a permission on an object.
-esd
_domain

the security domain that the user to which you want
to assign a permission belongs to. Default is Native.
-ObjectName
object_name
Name of the object that you want to remove the user

access permission.
-eu
-on
-ObjectType
-ot
object_type_SERVICE
_LICENSE_NODE_GR
ID_FOLDER_OSPROF
ILE

-
Service
License
Node
Grid
Folder
OSProfile
RemoveUserPrivilege
Removes a privilege from a user in the domain or from a user in an application service within the domain.
The infacmd isp RemoveUserPrivilege command uses the following syntax:
RemoveUserPrivilege
[<-ExistingUserSecurityDomain|-esd> existing_user_security
RemoveUserPrivilege
491
The following table describes infacmd isp RemoveUserPrivilege options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

is case sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
-hp
-ResilienceTimeout
-re
492
gateway_host1:port

domain.
onds

Option
Argument
Description
ExistingUserName
existing_user_name
Required. User account from which you are

removing the privilege. To enter a name that
contains a space or other non-alphanumeric
-esd
_domain

the security domain that the user from which you are
removing the privilege belongs to. Default is Native.
-ServiceName
service_name

path_of_privilege
Required. Fully-qualified name of the privilege you

want to assign to the group. A fully-qualified name
includes privilege group name and privilege name.
For example, a fully-qualified privilege name for the
Repository Service is folder/create. If the privilege
name includes spaces, enclose the path in quotation
marks as follows:
-eu
-sn
-PrivilegePath
-pp
Runtime Objects/Monitor/Execute/
Manage Execution
If the privilege name includes the special character
/, add the escape character \ before it as follows:
Model/View Model/Export\ /Import
Models
RenameConnection
Renames a connection. When you rename a connection, the Developer tool and the Analyst tool update the
jobs that use the connection.
Note: Deployed applications and parameter files identify a connection by name, not by connection ID.
Therefore, when you rename a connection, you must redeploy all applications that use the connection. You
must also update all parameter files that use the connection parameter.
The infacmd isp RenameConnection command uses the following syntax:
RenameConnection
<-NewConnectionName|-ncn> new_connection_name
RenameConnection
493
The following table describes infacmd isp RenameConnection options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

sign-on.
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

installation.
-ResilienceTimeout
-re
494
timeout_period_in
_seconds

seconds is used.
Option
Argument
Description
-ConnectionName
connection_name
Required. Existing connection name.
new_connection_
name
Required. New connection name. The name is

not case sensitive and must be unique within the
domain. It cannot exceed 128 characters,
contain spaces, or contain the following special
characters:
~ ` ! $ % ^ & * ( ) - + = { [ } ]
| \ : ; " ' < , > . ? /
-cn
-NewConnectionName
-ncn
ResetPassword
Resets the password for a user in the domain.
The infacmd isp ResetPassword command uses the following syntax:
ResetPassword
<-ResetUserName|-ru> reset_user_name
<-ResetUserPassword|-rp> reset_user_password
The following table describes infacmd isp ResetPassword options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

ResetPassword
495
Option
Argument
Description
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-ResetUserName
reset_user_name
Required. Name of the user whose password you want to

reset.
reset_user_password
Required. New password for the user. You can set a

password with the -rp option or the environment variable
INFA_PASSWORD. If you set a password with both methods,
the password set with the -rp option takes precedence.
-hp
-ResilienceTimeout
-ru
-ResetUserPassword
-rp
The password is case sensitive and must be between 1 and

80 characters long. To enter a password that contains spaces
or other non-alphanumeric characters, enclose it in quotation
marks.
RestoreDARepositoryContents
Restores content for a Data Analyzer repository from a binary file. You can restore metadata from a
repository backup file to a database. If you restore the backup file on an existing database, you overwrite the
existing content.
The infacmd isp RestoreDARepositoryContents command uses the following syntax:
496
<-fileName|-f> file_name
The following table describes infacmd isp RestoreDARepositoryContents options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
-hp
gateway_host1:port
gateway_host2:port
...

497
Option
Argument
Description
-ResilienceTimeout
-re
timeout_period_in_s
econds

-ServiceName
service_name

restore contents.
file_name
Required. Name and file path of the file to which you backed up
the content.
-sn
-fileName
-f
RunCPUProfile
Calculates the CPU profile for a node.
Note: This command takes approximately five minutes and uses 100% of one CPU on the machine.
The infacmd isp RunCPUProfile command uses the following syntax:
RunCPUProfile
498
The following table describes infacmd isp RunCPUProfile options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-NodeName
node_name
Required. Name of the node for which you want to calculate

the CPU profile.
-hp
-ResilienceTimeout
-nn
RunCPUProfile
499
SetConnectionPermissions
Assigns permissions on connection to a user or a group after removing previous permissions.
The infacmd isp SetConnectionPermissions command uses the following syntax:
[<-Permission|-p> permission_READ|WRITE|EXECUTE|GRANT|ALL
The following table describes infacmd isp SetConnectionPermissions options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

sign-on.
-Password
-pd
500
password

Option
Argument
Description
-SecurityDomain
security_domain

-sdn

installation.
-ResilienceTimeout
-re
ds

seconds is used.
-RecipientUserName
recipient_user_name

name. Name of the user to assign permissions
for the connection

name. Name of the group to assign permissions
for the connection.
nth_name

ty_domain
-cn
-Permission
permission
-run
-RecipientGroupName
-rgn
-rsd
-ConnectionName
-p
Required. Type of permission to assign.

Enter one or more of the following values
separated by spaces:
-
READ
WRITE. Read and Write.
EXECUTE
GRANT. Read and Grant.
ALL. Read, Write, Execute, Grant
501
SetLDAPConnectivity
Sets up the connection to an LDAP server. When you set up a connection to an LDAP server, the Service
Manager imports the user accounts of all LDAP security domains from the LDAP server.
The infacmd isp SetLDAPConnectivity command uses the following syntax:
SetLDAPConnectivity
<-LDAPAddress|-la> ldap_server_address
[<-LDAPPrincipal|-lp> ldap_principal]
[<-LDAPCredential|-lc> ldap_credential]
[<-UseSSL|-us> use_ssl]
[<-TrustLDAPCertificate|-tc> trust_ldap_certificate]
<-LDAPType|-lt> ldap_types=MicrosoftActiveDirectory, SunJavaSystemDirectory, NovellEDirectory, IBMTivoliDirectory, OpenLDAP
[<-MaxSecurityDomainSize|-ms> Max_Security_Domain_size]
[<-GroupMembershipAttr|-gm> LDAP_Group_Membership_Attribute]
[<-LDAPNotCaseSensitive|-lnc> ldap_not_case_sensitive]
The following table describes infacmd isp SetLDAPConnectivity options and arguments:
Option
Argument
Description
-DomainName
domain_name

takes precedence.
user_name

precedence.
-dn
-UserName
-un

502
Option
Argument
Description
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

installation.
-Gateway
gateway_host1:port

-re
nds

domain. If you omit this option, infacmd uses the
-LDAPAddress
ldap_server_address
Required. Host name and port number for the machine

hosting the LDAP directory service. Typically, the LDAP
server port number is 389. If the LDAP server uses
SSL, the LDAP server port number is 636.
ldap_principal
Optional. Distinguished name (DN) for the principal

user. Omit this option to log in as an anonymous user.
-hp
ResilienceTimeout
-la
-LDAPPrincipal
-lp
For more information, refer to the documentation for the

LDAP directory service.
-LDAPCredential
ldap_credential
-lc
Optional. Password for the principal user. You can set

a password with the -lc option or the environment
variable INFA_PASSWORD. If you set a password with
both methods, the password set with the -lc option
takes precedence.
Omit this option to log in as an anonymous user.
-UseSSL
-us
use_ssl
Optional. If you include the option, the LDAP directory

service uses Secure Socket Layer (SSL) protocol.
SetLDAPConnectivity
503
Option
Argument
Description
-TrustLDAPCertificate
trust_ldap_certificate
Optional. If you include the option, PowerCenter

connects to the LDAP server without verifying the SSL
certificate.
-tc
If you do not include the option, PowerCenter verifies

that the SSL certificate is signed by a Certificate
Authority before connecting to the LDAP server
-LDAPType
ldap_types=value
-lt
Required. Type of LDAP directory service. Directory

services include:
- MicrosoftActiveDirectory
- SunJavaSystemDirectory
- NovellE-Directory
- IBMTivoliDirectory
- OpenLDAP
-MaxSecurityDomainSize
-ms
Max_Security_Domain_s
ize
Optional. Maximum number of user accounts to import

into a security domain.
Default is 1000.
-GroupMembershipAttr
-gm
-LDAPNotCaseSensitive
-lnc
LDAP_Group_Members
hip_Attribute
Optional. Name of the attribute that contains group

membership information for a user.
LDAP_Not_Case_Sensit
ive
Optional. Indicates that the user names from the LDAP

directory service are not case sensitive.
Default is false.
SetRepositoryLDAPConfiguration
Updates the LDAP server configuration options for a PowerCenter repository.
You may need to update the connection information between the repository and the LDAP external directory
service after you install Informatica.
Use infacmd isp ListRepositoryLDAPConfiguration to view the current values for LDAP server configuration
options.
The infacmd isp SetRepositoryLDAPConfiguration command uses the following syntax:
<-LDAPAddress|-la> ldap_server_address
504
<-SearchBase|-sb> search base

<-SearchScope|-ss> search scope
<-LDAPPrincipal|-lp> ldap_principal
<-LDAPCredential|-lc> ldap_credential
<-LoginAttribute|-lt> login attribute
<-LoginFilter|-lf> login filter
[<-UseSSL|-us> use_ssl]
[<-CertificateDatabase|-cd> certificate database for ssl]
The following table describes infacmd isp SetRepositoryLDAPConfiguration options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
gateway_host1:port

505
Option
Argument
Description
-ResilienceTimeout
-re
nds

-LDAPAddress
ldap_server_address

hosting the LDAP directory service. Typically, the LDAP
server port number is 389.
search base
Required. Distinguished name (DN) of the entry that serves

as the starting point to search for user names in the LDAP
directory tree. LDAP finds an object in the directory
according to the path in the distinguished name of the
object. For example, in Microsoft Active Directory, the
cn=UserName,ou=OrganizationalUnit,dc=DomainName,
where the series of relative distinguished names denoted by
search scope
Required. Scope of the user search. Choose one of the

following options:
-la
-SearchBase
-sb
-SearchScope
-ss
- Base. Search the entry identified by search base.

- One level. Search all entries one level beneath the search
base entry but not including the search base entry.
- Subtree. Search the entire subtree at all levels beneath the
search base entry.
-LDAPPrincipal
ldap_principal
Required. Distinguished name (DN) for the principal user.

The user name often consists of a common name (CN), an
organization (O), and a country (C). The Principal User
Name is an administrative user with access to the directory
and is not the name to authenticate. Specify a user who has
permission to read other user entries in the LDAP server.
Omit this option to log in as an anonymous user. For more
information, refer to the LDAP Server documentation.
ldap_credential
Required. Password for the principal user. You can set a

password with the -lc option or the environment variable
INFA_PASSWORD. If you set a password with both
methods, the password set with the -lc option takes
precedence.
-lp
-LDAPCredential
-lc
Omit this option to log in as an anonymous user.

-LoginAttribute
login_attribute
Required. Directory attribute that contains login names.
login_filter
Required. An LDAP query string to filter results for user

search. The filter can specify attribute types, assertion
values, and matching criteria. For example: (objectclass=*)
searches all objects. (&(objectClass=user)(!(cn=susan)))
searches all user objects except susan. For more
information about search filters, see the LDAP server
documentation.
-lt
-LoginFilter
-lf
506
Option
Argument
Description
-UseSSL
use_ssl
Do not use this option. Informatica does not support an

LDAP server that uses SSL for versions 8.1.1 .
certificate_database_for
_ssl
Do not use this option. Informatica does not support an

LDAP server that uses SSL for versions 8.1.1 .
-us
-CertificateDatabase
-cd
ShowLicense
Displays license details. The license details you see are a cumulative result of all license keys applied. The
Service Manager updates the existing license details when you add an incremental key to the license.
To run the infacmd isp ShowLicense command, you must have permission on the license.
The infacmd isp ShowLicense command uses the following syntax:
ShowLicense
The following table describes infacmd isp ShowLicense options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

ShowLicense
507
Option
Argument
Description
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port

-re
onds

-LicenseName
license_name
Required. Name of the license.
-hp
-ResilienceTimeout
-ln
ShutdownNode
Shuts down a node. After you shut down a node, you can restart the node by starting the Informatica service
on the machine. You cannot restart a node using infacmd.
The infacmd isp ShutdownNode command uses the following syntax:
ShutdownNode
508
The following table describes infacmd isp ShutdownNode options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-NodeName
node_name
Required. Name of the node you want to shut down.
-hp
-ResilienceTimeout
-nn
ShutdownNode
509
SwitchToGatewayNode
Converts an existing worker node to a gateway node. The worker node must have the service role enabled.
The infacmd isp SwitchToGatewayNode command uses the following syntax:
SwitchToGatewayNode
[<-AdminconsolePort|-ap> admin_tool_port]
[<-AdminconsoleShutdownPort|-asp> admin_tool_shutdown_port]
<-LogServiceDirectory|-ld> log_service_directory
[<-DatabaseTruststorePassword|-dbtp> database_truststore_password]
[<-DatabaseTruststoreLocation|-dbtl> database_truststore_location]
The following table describes infacmd isp SwitchToGatewayNode options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
-pd
510
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-NodeName
node_name
Required. Name of the node you want to make a gateway

node.
admin_tool_port
Port to access Informatica Administrator.
admin_tool_shutdown
_port
Port number that controls shutdown for Informatica

Administrator.
log_service_directory
Required. Shared directory path used by the Log Manager to

store log event files.
database_truststore_
password
Optional. Password for the database truststore file for the

secure database. Required if you configure a secure domain
repository database for the domain.
database_truststore_l
ocation
Path and file name of the truststore file for the secure
database. Required if you configure a secure domain
repository database for the domain.
-hp
-ResilienceTimeout
-nn
-AdminconsolePort
-ap
AdminconsoleShutdow
nPort
-asp
-LogServiceDirectory
-ld
DatabaseTruststorePa
ssword
-dbtp
DatabaseTruststoreLo
cation
-dbtl
SwitchToGatewayNode
511
SwitchToWorkerNode
Converts a gateway node to a worker node. The command fails if the node you want to switch is the only
gateway node in the domain.
If the node serves as the master gateway node, you must shut down the node before you can convert it to a
worker node. Shut down the node and wait for the master gateway to fail over to another node. You can then
restart the node and run the infacmd isp SwitchToWorkerNode command.
The infacmd isp SwitchToWorkerNode command uses the following syntax:
SwitchToWorkerNode
The following table describes infacmd isp SwitchToWorkerNode options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
-pd
512
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-NodeName
node_name
Required. Name of the node you want to make a worker node.
-hp
-ResilienceTimeout
-nn
SyncSecurityDomains
Synchronizes users and groups in a security domain with the users and groups in the LDAP directory service.
The infacmd isp SyncSecurityDomains command uses the following syntax:
SyncSecurityDomains
<-SynchronizingNamespace|-sn> namespace_to_sync
SyncSecurityDomains
513
The following table describes infacmd isp SyncSecurityDomain options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

Optional if the domain uses native authentication
or Kerberos authentication. Name of the security
INFA_DEFAULT_SECURITY_DOMAIN. If you set
a security domain name with both methods, the sdn option takes precedence. The security domain
-pd
-SecurityDomain
-sdn

domain created during installation. The name of
the security domain is the same as the user realm
-Gateway
-hp
514
gateway_host1:port

the domains.infa file is out of date. The host
names and port numbers for the gateway nodes in
the domain.
Option
Argument
Description
-ResilienceTimeout
-re
nds

to the domain. If you omit this option, infacmd uses
the timeout value specified in the
used.
<-SynchronizingNamespace
namespace_to_sync
Name of the security domain you want to

synchronize with the LDAP directory service.
-sn
UnassignISMMService
Disassociates a PowerCenter Integration Service from a Metadata Manager Service. If you remove a
PowerCenter Integration Service, you must associate another PowerCenter Integration Service before you
load resources.
The infacmd isp UnassignISMMService command uses the following syntax:
UnassignISMMService
UnassignISMMService
515
The following table describes infacmd isp UnassignISMMService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-ServiceName
service_name
Required. Name of the Metadata Manager Service for which

you want to unassign the Integration Service.
integration_service_n
ame
Required. Name of the Integration Service you want to

unassociate from the Metadata Manager Service.
-hp
-ResilienceTimeout
-sn
-IntegrationService
-is
516
UnassignLicense
Removes a license from an application service. The service must be stopped. After you remove the license
from the service, you must assign a valid license to re-enable the service.
The UnassignLicense command uses the following syntax:
UnassignLicense
<-ServiceNames|-sn> service1_name service2_name ...
The following table describes infacmd isp UnassignLicense options and arguments:
Option
Arguments
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
-pd
password
precedence.
UnassignLicense
517
Option
Arguments
Description
-SecurityDomain
security_domain

sensitive.
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
timeout_period_in_s
econds

-LicenseName
license_name
Required. Name of the license you want to unassign.
service_name1
service_name2 ...
Required. Names of the services for which you want to remove

the license. To enter a name that contains a space or other nonalphanumeric character, enclose the name in quotation marks.
-hp
-ResilienceTimeout
-ln
-ServiceNames
-sn
UnassignRoleFromGroup
Removes a role from a group for a domain or an application service.
The infacmd isp UnassignRoleFromGroup command uses the following syntax:
518
The following table describes infacmd isp UnassignRoleFromGroup options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

single sign-on.
-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
-ResilienceTimeout
-re
gateway_host1:port
gateway_host2:port
...

conds

519
Option
Argument
Description
-GroupName
group_name
Required. Name of the group from which you want to

remove a role. To enter a name that contains a space or
quotation marks.
-gsf
group_security_doma
in

security domain that the group from which you are
removing the role belongs to. Default is Native.
-RoleName
role_name
Required. Name of the role you want to remove from the

group.
service_name
Required. Domain or application service name from which

you want to remove the role. To enter a name that contains
a space or other non-alphanumeric character, enclose the
-gn
-rn
-ServiceName
-sn
UnassignRoleFromUser
Removes a role from a user for a domain or an application service.
The infacmd isp UnassignRoleFromUser command uses the following syntax:
[<-ExistingUserSecurityDomain|-esd> existing_user_securit
520
The following table describes infacmd isp UnassignRoleFromUser options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

is case sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
-hp
gateway_host1:port

domain.
521
Option
Argument
Description
-ResilienceTimeout
-re
onds

used.
-ExistingUserName
existing_user_Name
Required. User account from which you are

removing the role. To enter a name that contains a
space or other non-alphanumeric character, enclose
-esd
domain

the security domain that the user from which you
are removing the role belongs to. Default is Native.
-RoleName
role_name
Required. Name of the role you want to remove

from the user.
service_name
Required. Domain or application service name from

which you want to remove the role. To enter a name
that contains a space or other non-alphanumeric
-eu
-rn
-ServiceName
-sn
UnassignRSWSHubService
Disassociates a PowerCenter repository from a Web Services Hub in the domain.
The infacmd isp UnassignRSWSHubService command uses the following syntax:
522
The following table describes infacmd isp UnassignRSWSHubService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

single sign-on.
-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port
gateway_host2:port
...
-ResilienceTimeout

-re
s

-ServiceName
service_name
Required. Name of the Web Services Hub from which you

want to disassociate a repository.
-sn
523
Option
Argument
Description
-NodeName
node_name
Required. Name of the node where the Web Services Hub

process runs. If the Informatica environment is configured
for high availability, this option specifies the name of the
primary node.
Required. Name of the Repository Service that the Web

Services Hub depends on.
-nn
-RepositoryService
-rs
marks.
UnassociateDomainNode
Disassociates a node in a domain from its address. The node name remains part of the domain, but it has no
physical address.
For example, in a domain, Node1 is associated with machine MyHost:9090. When you run this command,
the connection between the name Node1 and the host address MyHost:9090 is removed. You can then
associate Node1 with a new host. You must run the infasetup DefineGatewayNode or DefineWorkerNode
command on the new host to define Node1 on that machine.
The infacmd isp UnassociateDomainNode command uses the following syntax:
524
The following table describes infacmd isp UnassociateDomainNode options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-NodeName
node_name
Required. Name of the node you want to disassociate from the

domain.
-hp
-ResilienceTimeout
-nn
525
UpdateConnection
Updates a connection. To list connection options, run infacmd isp ListConnectionOptions.
The infacmd isp UpdateConnection command uses the following syntax:
UpdateConnection
[<-ConnectionUserName|-cun> connection_user_name]
[<-ConnectionPassword|-cpd> connection_password]
[-o options] (name-value pairs separated by space)
The following table describes infacmd isp UpdateConnection options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

sign-on.
-Password
-pd
526
password

Option
Argument
Description
-SecurityDomain
security_domain

-sdn

installation.
-ResilienceTimeout
-re
-ConnectionName
-cn
ConnectionUserName
-cun
timeout_period_in
_seconds

seconds is used.
connection_name
_security_domain
Required. Name of the connection to update.
connection_user_
name
Required. Database user name.
UpdateConnection
527
Option
Argument
-ConnectionPassword
connection_pass
word
-cpd
Description
Required. Password for the database user name.
If you are updating an ADABAS, DB2I, DB2Z,
IMS, SEQ, or VSAM connection, you can enter a
valid PowerExchange passphrase instead of a
password. Passphrases for access to databases
and data sets on z/OS can be from 9 to 128
characters in length. Passphrases for access to
DB2 for i5/OS can be up to 31 characters in
length. Passphrases can contain the following
characters:
- Spaces
- ; # \ , . / ! % & * ( ) _ +
{ } : @ | < > ?
Passphrases cannot include single quotation

marks (), double quotation marks (), or currency
symbols.
If a passphrase contains spaces, you must
enclose it with double-quotation marks ("), for
example, "This is an example
passphrase". If a passphrase contains special
characters, you must enclose it with triple
double-quotation characters ("""), for example,
"""This passphrase contains
special characters ! % & *.""". If a
passphrase contains only alphanumeric
characters without spaces, you can enter it
without delimiters.
Note: On z/OS, a valid RACF passphrase can be
up to 100 characters in length. PowerExchange
truncates passphrases longer than 100
characters when passing them to RACF for
validation.
To use passphrases, ensure that the
PowerExchange Listener runs with a security
setting of SECURITY=(1,N) or higher in the
DBMOVER member. For more information, see
"SECURITY Statement" in the PowerExchange
Reference Manual.
To use passphrases for IMS connections, ensure
that the following additional requirements are
met:
- You must configure ODBA access to IMS as
described in the PowerExchange Navigator User
Guide.
- You must use IMS data maps that specify IMS
ODBA as the access method. Do not use data
maps that specify the DL/1 BATCH access
method because this access method requires the
use of netport jobs, which do not support
passphrases.
528
Option
Argument
Description
- The IMS database must be online in the IMS
control region to use ODBA access to IMS.
- Options
options
Enter name-value pairs separated by spaces. To

view valid options, run infacmd isp
ListConnectionOptions.
-o
UpdateDomainOptions
Updates domain properties. Domain properties include resilience timeout, limit on resilience timeouts,
maximum restart attempts, restart period, TLS mode, and dispatch mode.
The infacmd isp UpdateDomainOptions command uses the following syntax:
UpdateDomainOptions
<-DomainOptions|-do> option_name=value ...
The following table describes infacmd isp UpdateDomainOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

UpdateDomainOptions
529
Option
Argument
Description
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-DomainOptions
option_name=value
Required. Domain properties you want to update. You can

update the following properties:
-hp
-ResilienceTimeout
-do
- LicenseUsageDetailMinDays. Minimum number of days the Log

Manager keeps log events for license usage.
- LicenseUsageSummaryMinDays. Minimum number of days the
Log Manager keeps database records for license usage.
- ResilTimeout. Amount of time in seconds services attempt to
connect as clients to other services.
- RestartsMaxAttempts. Number of times within a specified
period that the domain attempts to restart an application
service process when it fails.
- RestartsWithinSeconds. Maximum period of time in seconds
that the domain spends attempting to restart an application
service process when it fails.
- ServiceResilTimeout. Amount of time in seconds that a service
tries to establish or reestablish a connection to another service.
- TaskDispatchMode. Load Balancer dispatch mode for tasks:
RoundRobin, MetricBased, or Adaptive. Restart the Integration
Service to apply changes.
- TLSMode. Configures secure communication between services
within the domain. To apply changes, restart the domain. Valid
values are true or false.
530
UpdateFolder
Updates the folder description.
The infacmd isp UpdateFolder command uses the following syntax:
UpdateFolder
<-FolderDescription|-fd> description_of_folder
The following table describes infacmd isp UpdateFolder options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
gateway_host1:port
gateway_host2:port
...

-pd
-Gateway
-hp
UpdateFolder
531
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-ResilienceTimeout
-re
conds

-FolderPath
full_folder_path

you want to update. Must be in the following format:
-fp
-FolderDescription
description_of_folder
-fd
Required. Description of the folder. If the folder description

UpdateGatewayInfo
Updates gateway node connectivity information in the domains.infa file.
The infacmd isp UpdateGatewayInfo command uses the following syntax:
UpdateGatewayInfo
[<-Force|-f>]
532
The following table describes infacmd isp UpdateGatewayInfo options and arguments:
Option
Argument
Description
-DomainName
domain_name
domain_gateway_host:p
ort
Required. Gateway host machine name and port number.
-dg
-Force
Optional. Updates or creates the domains.infa file even when

the connection to the domain fails. The Force option sets the
Kerberos and TLS enabled options as false in the
domains.infa file if the connection to domain fails. If you do
not specify the Force option, the command does not update
the domains.infa file if the connection to the domain fails.
-dn
-GatewayAddress
-f
UpdateGrid
Updates the list of nodes assigned to a grid.
The infacmd isp UpdateGrid command uses the following syntax:
UpdateGrid
<-NodeList|-nl> node1 node2 ...
[<-UpdateNodeList|-ul> true|false]
UpdateGrid
533
The following table describes infacmd isp UpdateGrid options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-GridName
grid_name
-hp
-ResilienceTimeout
-gn
534
Option
Argument
Description
-NodeList
node1 node2 ...
Required. Names of the nodes that you want to assign to the

grid. This list of nodes replaces or updates the list of nodes
previously assigned to the grid based on the -ul option
defined.
-nl
If you specify the -ul option, the -nl option updates the list of
nodes previously assigned to the grid. If you do not specify
the -ul option, the -nl option replaces the list of nodes
previously assigned to the grid.
-UpdateNodeList
true|false
-ul
Optional. Updates the current node list with the values in the nl option instead of replacing the list of nodes previously
assigned to the grid. If true, infacmd updates the node list with
the list of nodes specified using the -nl option along with the
nodes previously assigned to the grid. If false, infacmd
replaces the node list with the list of nodes specified using the
-nl option. Default is false.
UpdateIntegrationService
Updates the configuration properties for the PowerCenter Integration Service.
The infacmd isp UpdateIntegrationService command uses the following syntax:
[<-NodeName|-nn> node_name|<-GridName|-gn> grid_name]
[<-RepositoryService|-rs> repository_service_name]
[<-RepositoryUser|-ru> repository_user]
[<-RepositoryPassword|-rp> repository_password]
Note: For infacmd isp UpdateIntegrationService, you must not use the -ru, -rp, and the -rsdn options in
Kerberos authentication. If you use these options in Kerberos mode, the command will fail.
535
The following table describes infacmd isp UpdateIntegrationService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

installation.
-Gateway
gateway_host1:port

-re
onds

to establish a connection to the domain. If you omit this
-ServiceName
service_name
Required. Integration Service name. To enter a name that

node_name
Optional. Name of the node where the Integration Service

process runs. If the PowerCenter environment is configured
for high availability, this option specifies the name of the
primary node.
-hp
-ResilienceTimeout
-sn
-NodeName
-nn
Do not enter a value for this option if you specify the grid
name.
536
Option
Argument
Description
-GridName
grid_name
Optional. Name of the grid where the Integration Service

process runs.
-gn
Do not enter a value for this option if you specify the node
name.
-BackupNodes
node1 node2 ...

me
Optional. Name of the Repository Service that the

Integration Service depends on.
-bn
-RepositoryService
-rs
marks.
-RepositoryUser
user
-ru
Required for native or LDAP authentication. User name used

to connect to the repository.
marks.
-RepositoryPassword
password
Required for native or LDAP authentication. User password.

You can set a password with the -rp option or the
environment variable INFA_REPOSITORY_PASSWORD. If
you set a password with both methods, the password set
with the -rp option takes precedence.
repository_user_securi
ty_domain
Required for LDAP authentication. Optional if the domain

uses native authentication. Name of the security domain to
which the PowerCenter repository user belongs.
-rp
yDomain
-rsdn
-ServiceOptions

option_name=value
-so
Optional. Service properties that define how the

PowerCenter Integration Service runs.
UpdateLicense
Updates license information for the domain. Run this command to upgrade your license using an incremental
license key. You use the key to add or remove licensed options.
When you add an incremental key to a license, the Service Manager updates the license expiration date if the
expiration date on the incremental key is later than the original key.
The infacmd isp UpdateLicense command uses the following syntax:
UpdateLicense
UpdateLicense
537
<-LicenseKeyFile|-lf> license_key_file
The following table describes infacmd isp UpdateLicense options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
-ResilienceTimeout
-re
538
gateway_host1:port
gateway_host2:port
...

conds

Option
Argument
Description
-LicenseName
license_name
Required. Name of the license object you want to update.
license_key_file
Required. Name and path to the file that contains the

incremental keys.
-ln
-LicenseKeyFile
-lf
UpdateMMService
Updates or creates the service options for a Metadata Manager Service. To update or create the service
options, disable the Metadata Manager Service, update the options, and re-enable the service.
The infacmd isp UpdateMMService command uses the following syntax:
UpdateMMService
<-ServiceOptions|-so> option_name=value ...>
The following table describes infacmd isp UpdateMMService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
UpdateMMService
539
Option
Argument
Description
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port

-re
nds

-ServiceName
service_name
Required. Name of the Metadata Manager Service you want

to update.
license_name
Required. Name of the license you want to assign to the

Metadata Manager Service.
option_name=value
Optional. Service properties that define how the Metadata

-hp
-ResilienceTimeout
-sn
-LicenseName
-ln
-ServiceOptions
-so
UpdateMonitoringOptions
Updates general properties to monitor actions in the domain.
When you specify a Model Repository Service with the -ModelRepositoryService option, you must also enter
values for the -RepositoryUserName and -RepositoryPassword options. You must include values for all three
options or for none of them.
The infacmd isp UpdateMonitoringOptions command uses the following syntax:
540
[<-ModelRepositoryService|-rs> model_repository_service]
[<-RepositoryUserName|-rsun> model_repository_user_name]
[<-RepositoryPassword|-rspd> model_repository_password]
[<-RepositorySecurityDomain|-rsdn> model_repository_security_domain]
[<-AdministratorOptions|-ao> option_name=value ...(MaxSortedRecords, ShowMilliSeconds)]
[<-CachingOption|-co> option_name=value ...(DefaultNotificationDelay)]
[<-PurgeOptions|-po> option_name=value ...(PurgeScheduleTime, PurgeTaskFrequency,
StatisticsExpiryTime, DetailedStatisticsExpiryTime)]
The following table describes infacmd isp UpdateMonitoringOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

domain. You can set the user name with the
-un option or the environment variable
-dn
-UserName
-un

-Password
-pd
password

variable
precedence.
541
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

default is the user realm specified during
installation.
-Gateway
-hp
gateway_host1:port

-ResilienceTimeout
Optional. Amount of seconds that infacmd

attempts to establish a connection to the
domain. You can set the resilience timeout
period with the -re option or the environment
variable
INFA_CLIENT_RESILIENCE_TIMEOUT. If
you set the resilience timeout period with
both methods, the -re option takes
precedence. Default is 180 seconds.
model_repository_service
Optional. Name of the Model Repository

Service that stores the historical information.
model_repository_user_name
Required for native or LDAP authentication.

authentication. User name to access the
Model Repository Service.
model_repository_password
Required for native or LDAP authentication.

authentication. User password to access the
Model Repository Service.
model_repository_security_domain
Required for LDAP or Kerberos

native authentication. Name of the security
domain to which the PowerCenter repository
user belongs. The security domain is case
sensitive. If you do not specify this option,
the command sets the repository user
-re
-ModelRepositoryService
-rs
-RepositoryUserName
-rsun
-RepositoryPassword
-rspd
RepositorySecurityDomain
-rsdn
542
Option
Argument
Description
-AdministratorOptions
option_name=value
Optional. General administrative settings for

records and monitoring reports. You can set
the following options:
-ao
- MaxSortedRecords. Maximum number of

records that can be sorted. Default is 3,000.
- ShowMilliseconds. Include milliseconds for
date and time field in monitoring reports. You
can set to true or false. Default is false.
-CachingOption
option_name=value
-co
Optional. Settings for caching statistics. You

can set the following options:
- DefaultNotificationDelay. Maximum number
of seconds that the Data Integration Service
buffers the statistics before persisting the
statistics in the Model Repository and writing
them to a monitoring report. Default is 10.
-PurgeOptions
option_name=value
-po
Optional. Settings for purging statistics. You

can set the following options:
- PurgeScheduleTime. Time of day when the
Model Repository Service purges statistics.
Default is 1:00 a.m.
- PurgeTaskFrequency. Interval, in days, at
which the Model Repository Service purges
statistics that are older than the values
configured for the ExpiryTime options.
Default is 1.
- StatisticsExpiryTime. Number of days that
the Model repository saves averaged
statistics. If purging is disabled, then the
Model repository saves the statistics
indefinitely. Default is 180. Minimum is 0.
Maximum is 366.
- DetailedStatisticsExpiryTime. Number of
days that the Model repository saves perminute statistics. If purging is disabled, then
Model repository saves the statistics
indefinitely. Default is 14. Minimum is 0.
Maximum is 14.
UpdateNamespace
Updates an LDAP security domain with the filters provided for the user and group. Updates the LDAP
security domain if the Informatica domain uses LDAP or Kerberos authentication.
The infacmd isp UpdateNamespace command uses the following syntax:
UpdateNamespace
UpdateNamespace
543

[<-UserSearchBase|-usb> usersearchbase]
[<-UserFilter|-uf> userfilter]
[<-GroupSearchBase|-gsb> groupsearchbase]
[<-GroupFilter|-gf> groupfilter]
The following table describes infacmd isp UpdateNamespace options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

single sign-on.
-Password
password

security_domain
Name of the security domain to which the domain user

belongs. You can set a security domain with the -sdn
sensitive.
-pd
-SecurityDomain
-sdn
544
Option
Argument
Description
-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-NameSpace
namespace
Required. Name of the LDAP or Kerberos security domain.

the domain. The name cannot contain spaces or any of the
-hp
-ResilienceTimeout
-ns
,+/<>@;\%?
-UserSearchBase
usersearchbasesu
-usb

starting point to search for user names in the LDAP
directory service. The LDAP directory service searches for
an object in the directory according to the path in the
distinguished name of the object.
For example, in Microsoft Active Directory, the
cn=UserName,ou=OrganizationalUnit,dc=DomainName.
The series of relative distinguished names denoted by
-UserFilter
userfilter
-uf
An LDAP query string that specifies the search criteria to

search for users in the directory service. The filter can
specify attribute types, assertion values, and matching
criteria.
For example: The filter(objectclass=*)searches all
objects. The filter(&(objectClass=user)(!
(cn=susan)))searches all user objects except susan.
For more information about search filters, see the
documentation for the LDAP directory service.
-GroupSearchBase
groupsearchbase

starting point to search for group names in the LDAP
directory service.
groupfilter
An LDAP query string that specifies the criteria for

searching for groups in the directory service.
-gsb
-GroupFilter
-gf
UpdateNamespace
545
UpdateNodeOptions
Updates node general properties such as backup directory, CPU profile, error severity level, service process
ports, and resource provision thresholds.
The infacmd isp UpdateNodeOptions command uses the following syntax:
UpdateNodeOptions
[<-NodeOptions|-no> option_name=value ...]
[<-ResourceProvision|-rp> option_name=value ...]
The following table describes infacmd isp UpdateNodeOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
-pd
546
precedence.
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port

-re
onds

-NodeName
node_name
Optional. Name of the node whose resource provision

thresholds you want to update.
-hp
-ResilienceTimeout
-nn
UpdateNodeOptions
547
Option
Argument
Description
-NodeOptions
option_name=value
Optional. The node options you want to update. You can

update the following options:
-no
- BackupDir. Directory to store repository backup files.

- CPUProfile. Ranking of the CPU performance of the node
compared to a baseline system. ErrorSeverityLevel. Level of
error logging for the node: error, warning, info, trace, debug.
- MaxProcessPort. Maximum port number used by service
processes on the node.
- MinProcessPort. Minimum port number used by service
The following example sets MaxProcessPort to 1515:

infacmd UpdateNodeOptions ... -no
MaxProcessPort=1515
-ResourceProvision
option_name=value
-rp
Optional. The resource provision thresholds you want to

update. You can update the following thresholds:
- MaxCPURunQueueLength. The maximum number of runnable
threads waiting for CPU resources on the node.
- MaxMemoryPercent. The maximum percentage of virtual
memory allocated on the node relative to the total physical
memory size.
- MaxProcesses. The maximum number of Session and Command
tasks that can run on each Integration Service running on the
node.
The following example sets MaxProcesses to 15:

infacmd UpdateNodeOptions ... -rp
MaxProcesses=15
UpdateNodeRole
Updates the role on a node in the domain. You can enable or disable the service role or the compute role on
a node.
By default, each node has both the service and compute roles. If a node is assigned to a Data Integration
Service grid, you might want to update the node role. Enable only the service role to dedicate the node to
running the Data Integration Service process. Enable only the compute role to dedicate the node to running
Data Integration Service mappings.
If you update the role on a node assigned to a Data Integration Service or a Data Integration Service grid,
you must recycle the Data Integration Service for the changes to take effect.
The infacmd isp UpdateNodeRole command uses the following syntax:
UpdateNodeRole
548
[<-EnableServiceRole|-esr> true|false]
[<-EnableComputeRole|-ecr> true|false]
[<-disableComputeRoleMode|-mo> disable_mode]
The following table describes infacmd isp UpdateNodeRole options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
gateway_host1:port
gateway_host2:port
...

UpdateNodeRole
549
Option
Argument
Description
-ResilienceTimeout
-re
conds

-NodeName
node_name
Required. Name of the node that you want to update.
true | false
Optional. Enables the service role on the node. If true,

application services can run on the node. If false, application
services cannot run on the node. Set to false only if the node
is assigned to a Data Integration Service grid and you want to
dedicate the node to running mappings.
-nn
-EnableServiceRole
-esr
Default is true.
-EnableComputeRole
true | false
-esr
Optional. Enables the compute role on the node. If true, the

node can perform computations requested by remote
application services. If false, the node cannot perform
computations requested by remote application services.
A node requires the compute role when the Data Integration
Service runs jobs on the node.
If the Data Integration Service does not run jobs on the node,
you can disable the compute role. However, enabling or
disabling the compute role does not have a performance
impact.
Default is true.
disableComputeRoleM
ode
disable_mode
-mo
Optional. Defines how the compute role is disabled:

- Complete. Allows computations to run to completion before
disabling the compute role.
- Stop. Stops all running computations and then disables the
compute role.
- Abort. Tries to stop all running computations before aborting
them and disabling the compute role.
Default is abort.
UpdateOSProfile
Updates properties for an operating system profile in the domain.
Note: To run workflows that use operating system profiles, you must have the operating system profiles
option.
The infacmd isp UpdateOSProfile command uses the following syntax:
UpdateOSProfile
550
[<-IntegrationServiceProcessOptions|-po> option_name=value ...
The following table describes infacmd isp UpdateOSProfile options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

sign-on.
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

UpdateOSProfile
551
Option
Argument
Description
-Gateway
gateway_host1:port
gateway_host2:port
...

in the domain.
-re
timeout_period_in_s
econds

connection to the domain. If you omit this option,
infacmd uses the timeout value specified in the
seconds is used.
-OSProfileName
OSProfile_name
Required. Name of the operating system profile.
option_name=value
Optional. Service process properties that define

how the Integration Service runs.
-hp
-ResilienceTimeout
-on
-IntegrationServiceProcessOptions
-po
UpdateReportingService
Updates or creates the service and lineage options for the Reporting Service.
The infacmd isp UpdateReportingService command uses the following syntax:
[<-ServiceOptions|-so> option_name=value]
[<-LineageService|-ls> option_name=value ]
552
The following table describes infacmd isp UpdateReportingService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
precedence.
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
timeout_period_in_s
econds

-ServiceName
service_name
Required. Name of the Reporting Service you want to update.

option_name=value
Optional. Service properties that define how the Reporting

Service runs.
option_name=value
Optional. Lineage properties required to perform lineage

analysis for data in Data Analyzer.
-hp
-ResilienceTimeout
-sn
-ServiceOptions
-so
-LineageService
-ls
553
UpdateRepositoryService
Updates or creates service options for the PowerCenter Repository Service.
For example, you can update the PowerCenter Repository Service operating mode, which you can set to
normal or exclusive. Normal mode allows multiple users to access the PowerCenter Repository Service and
update repository contents. Exclusive mode allows a single user to access the PowerCenter Repository
Service and update repository contents. Set the operating mode to exclusive when you perform
administrative tasks that require a single user to log in and update the configuration. To update the
PowerCenter Repository Service operating mode, disable the PowerCenter Repository Service, update the
operating mode, and then re-enable the PowerCenter Repository Service.
The infacmd isp UpdateRepositoryService command uses the following syntax:
The following table describes infacmd isp UpdateRepositoryService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
-pd
554
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
gateway_host1:port

-re
onds

-ServiceName
service_name
Required. Name of the PowerCenter Repository Service you

want to update. To enter a name that contains a space or
quotation marks.
node_name
Optional. Name of the node where the PowerCenter

Repository Service process runs. If the PowerCenter
node1 node2 ...

option_name=value
Required. Service properties that define how the PowerCenter

Repository Service runs.
-hp
-ResilienceTimeout
-sn
-NodeName
-nn
-BackupNodes
-bn
-ServiceOptions
-so
Repository Service Options (-so)

Enter Repository Service options in the following format:
infacmd CreateRepositoryService ... -so option_name=value option_name=value ...
555
The following table describes Repository Service options:

Option
Description
AllowWritesWithRACaching
Optional. Uses PowerCenter Client tools to modify metadata in the repository

when repagent caching is enabled. Default is Yes.
CheckinCommentsRequired
Optional. Requires users to add comments when checking in repository

objects. Default is Yes. To apply changes, restart the PowerCenter Repository
Service.
CodePage
Required. Code page description for the database. To enter a code page
description that contains a space or other non-alphanumeric character, enclose
ConnectString
Required. Database connection string specified during PowerCenter Repository

Service setup. To apply changes, restart the PowerCenter Repository Service.
DBPassword
Required. Repository database password corresponding to the database user.

You can set a password with the -so option or the environment variable
INFA_DEFAULT_DATABASE_PASSWORD. If you set a password with both
methods, the password set with the -so option takes precedence.
To apply changes, restart the PowerCenter Repository Service.
556
DBPoolExpiryThreshold
Optional. The minimum number of idle database connections allowed by the

PowerCenter Repository Service. For example, if there are 20 idle connections,
and you set this threshold to 5, the PowerCenter Repository Service closes no
more than 15 connections. Minimum is 3. Default is 5.
DBPoolExpiryTimeout
Optional. The interval, in seconds, at which the PowerCenter Repository

Service checks for idle database connections. If a connection is idle for a
period of time greater than this value, the PowerCenter Repository Service can
close the connection. Minimum is 300. Maximum is 2,592,000 (30 days).
Default is 3,600 (1 hour).
DBUser
Required. Account for the database containing the repository. To apply

DatabaseArrayOperationSize
Optional. Number of rows to fetch each time an array database operation is

issued, such as insert or fetch. Default is 100. To apply changes, restart the
PowerCenter Repository Service.
DatabaseConnectionTimeout
Optional. Amount of time in seconds that the PowerCenter Repository Service

attempts to establish a connection to the database management system.
Default is 180.
DatabasePoolSize
Optional. Maximum number of connections to the repository database that the

PowerCenter Repository Service can establish. Minimum is 20. Default is 500.
DatabaseType
Required. Type of database that stores the repository metadata. To apply

EnableRepAgentCaching
Optional. Enables the repository agent caching feature. Default is Yes.
Option
Description
ErrorSeverityLevel
Optional. Minimum level of error messages written to the PowerCenter

Repository Service log:
- Fatal
- Error
Warning
- Info
- Trace
- Debug
Default is Info.
HeartBeatInterval
Optional. Interval at which the PowerCenter Repository Service verifies its

connections with clients of the service. Default is 60 seconds.
Optional. Maximum amount of time in seconds that the service holds on to

resources for resilience purposes. Default is 180.
MaximumConnections
Optional. Maximum number of connections the repository accepts from

repository clients. Default is 200.
MaximumLocks
Optional. Maximum number of locks the repository places on metadata objects.

Default is 50,000.
OperatingMode
Optional. Mode in which the PowerCenter Repository Service is running:

- Normal
- Exclusive
Default is Normal. To apply changes, restart the PowerCenter Repository

Service.
OptimizeDatabaseSchema
Optional. Optimizes the repository database schema when you create

repository contents or back up and restore an IBM DB2 or Microsoft SQL
Server repository. When enabled, the PowerCenter Repository Service tries to
create repository tables that contain Varchar columns with a precision of 2000
instead of CLOB columns. Use Varchar columns to increase repository
performance. When you use Varchar columns, you reduce disk input and
output, and the database can cache the columns.
To use this option, verify the page size requirements for the following repository
databases:
- IBM DB2. Database page size 4 KB or greater. At least one temporary tablespace
with page size 16 KB or greater.
- Microsoft SQL Server. Database page size 8 KB or greater.
Default is disabled.
PreserveMXData
Optional. Preserves MX data for prior versions of mappings. Default is

disabled.
RACacheCapacity
Optional. Number of objects that the cache can contain when repository agent
caching is enabled. Default is 10,000.
SecurityAuditTrail
Optional. Tracks changes made to users, groups, privileges, and permissions.

Default is No.
Optional. Amount of time in seconds that the service tries to establish or

reestablish a connection to another service. Default is 180. To apply changes,
restart the PowerCenter Repository Service.
557
Option
Description
TableOwnerName
Optional. Name of the owner of the repository tables for an IBM DB2 repository.
TablespaceName
Optional. Tablespace name for IBM DB2 repositories. To apply changes, restart
the PowerCenter Repository Service.
TrustedConnection
Optional. Uses Windows authentication to access the Microsoft SQL Server

database. Default is No. To apply changes, restart the PowerCenter Repository
Service.
UpdateSAPBWService
Updates the service and service process options for the SAP BW Service.
The infacmd isp UpdateSAPBWService command uses the following syntax:
UpdateSAPBWService
558
The following table describes infacmd isp UpdateSAPBWService options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
gateway_host1:port

-re
onds

-ServiceName
service_name
Required.SAP BW Service name. To enter a name that

-hp
-ResilienceTimeout
-sn
UpdateSAPBWService
559
Option
Argument
Description
-NodeName
node_name
Optional. Name of the node where the SAP BW Service

process runs. If the PowerCenter environment is
configured for high availability, this option specifies the
name of the primary node.
option_name=value
Optional. Service properties that define how the SAP BW

Service runs.
option_name=value
Optional. Service process properties that define how the

SAP BW Service process runs.
-nn
-ServiceOptions
-so
-ServiceProcessOptions
-po
UpdateServiceLevel
Updates service level properties. You can update the dispatch priority and maximum dispatch wait time.
The infacmd isp UpdateServiceLevel command uses the following syntax:
UpdateServiceLevel
<-ServiceLevel|-sl> option_name=value ...
The following table describes infacmd isp UpdateServiceLevel options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

560
Option
Argument
Description
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-ServiceLevelName
service_level_name
Required. Name of the service level you want to update.
option_name=value
Required. The service level properties you want to update.

You can update the following properties:
-hp
-ResilienceTimeout
-ln
-ServiceLevel
-sl
- DispatchPriority. The initial priority for dispatch. Smaller

numbers have higher priority. Priority 1 is the highest priority.
- MaxDispatchWaitTime. The amount of time in seconds that can
elapse before the Load Balancer escalates the dispatch priority
for a task to the highest priority.
UpdateServiceProcess
Updates the values of the PowerCenter Integration Service process options.
The infacmd isp UpdateServiceProcess command uses the following syntax:
561
<-ServiceProcessOptions|-po> option_name=value
[<-ProcessEnvironmentVariables|-ev> option_name=value ...]
The following table describes infacmd isp UpdateServiceProcess options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
562
gateway_host1:po
rt
gateway_host2:po
rt ...

Option
Argument
Description
-ResilienceTimeout
-re
timeout_period_in
_seconds

-ServiceName
service_name
Required. Name of the service. To enter a name that

node_name
Required. Name of the node where you want to update

configuration information.
option_name=val
ue
Name and new values of the options whose values you want
to update. You can specify multiple option_name=value
pairs. You can use a process variable in the value.
-sn
-NodeName
-nn
-ServiceProcessOptions
-po
For example, the following command sets the cache

directory to $PMRootDir/NewCache and the reject file
directory to $PMRootDir/NewBadFiles:
infacmd UpdateServiceProcess ... -po
$PMCacheDir=$PMRootDir/NewCache
$PMBadFileDir=$PMRootDir/NewBadFiles
Required if you do not specify
ProcessEnvironmentVariables.
ProcessEnvironmentVariabl
es
option_name=val
ue
-ev
Environment variables for the service process. You can

specify multiple environment variables.
For example, the following command adds or updates the
JAVA_HOME directory to "$HOME/java" and the
INFA_HOME directory to $HOME/Informatica/9.0.1/install
for the specified service process:
infacmd ProcessEnvironmentVariables ... ev JAVA_HOME=$HOME/java INFA_HOME=$HOME/
Informatica/9.0.1/install
Required if you do not specify ServiceProcessOptions.
UpdateSMTPOptions
Updates the domain SMTP configuration. The SMTP configuration is used to send domain alerts and
scorecard notifications.
After you configure the SMTP settings, you must subscribe the user to alerts using the AddAlertUser
command.
The infacmd isp UpdateSMTPOptions command uses the following syntax:
UpdateSMTPOptions
UpdateSMTPOptions
563
<-SMTPAddress|-sa> smtp_server_address
[<-SMTPUsername|-su> user_name]
[<-SMTPPassword|-sp> password]
[<-SMTPSenderAddress|-ss> sender_email_address]
The following table describes infacmd isp UpdateSMTPOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name
Required. User name to connect to the domain. You can

set the user name with the -un option or the environment
variable INFA_DEFAULT_DOMAIN_USER. If you set a
precedence.
password
Required. Password for the user name. The password is

case sensitive. You can set a password with the -pd option
security_domain

security domain that the user belongs to. You can set a
variable INFA_DEFAULT_SECURITY_DOMAIN. If you set
a security domain name with both methods, the -sdn option
takes precedence. Security domain is case sensitive.
Default is Native.
gateway_host1:port

onds

SMTP_server_addres
s
Required. The host name and port number for the SMTP
outbound mail server. Enter this information in the following
format:
-dn
-UserName
-un
-Password
-pd
-SecurityDomain
-sdn
-Gateway
-hp
-ResilienceTimeout
-re
-SMTPAddress
-sa
host_name:port_number
564
Option
Argument
Description
-SMTPUserName
user_name
User name for authentication upon sending, if required by

the outbound mail server.
password
User password for authentication upon sending, if required

by the outbound mail server. You can set a password with
the -sp option or the environment variable
INFA_PASSWORD. If you set a password with both
methods, the password set with the -sp option takes
precedence.
sender_email_address
Optional. Email address the Service Manager uses to send

notification emails. If you leave this field blank, the Service
Manager uses the default Administrator@<host> as the
sender.
-su
-SMTPPassword
-sp
-SMTPSenderAddress
-ss
Related Topics:
AddAlertUser on page 192
UpdateWSHubService
Updates a Web Services Hub in the domain.
The infacmd isp UpdateWSHubService command uses the following syntax:
UpdateWSHubService
UpdateWSHubService
565
The following table describes infacmd isp UpdateWSHubService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
gateway_host2:port
...

-re
conds

-ServiceName
service_name
Required. Name of the Web Services Hub you want to update.
node_name
Optional. Name of the node where the Web Services Hub

process runs.
option_name=value
...
Optional. Service properties that define how the Web Services

Hub runs.
-hp
-ResilienceTimeout
-sn
-NodeName
-nn
-ServiceOptions
-so
566
UpgradeDARepositoryContents
Upgrades content for a Data Analyzer repository.
You upgrade the contents of the repository to ensure that the metadata in a previous version of the Data
Analyzer repository is compatible with the Reporting Service.
The infacmd isp UpgradeDARepositoryContents command uses the following syntax:
UpgradeDARepositoryContents
The following table describes infacmd isp UpgradeDARepositoryContents options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name
Required. User name to connect to the domain. You can set the
user name with the -un option or the environment variable
password
Required. Password for the user name. The password is case

sensitive. You can set a password with the -pd option or the
environment variable INFA_DEFAULT_DOMAIN_PASSWORD. If
you set a password with both methods, the password set with the
security_domain
Required if you use LDAP authentication. Name of the security

domain that the user belongs to. You can set a security domain
with the -sdn option or the environment variable
precedence. Security domain is case sensitive. Default is Native.
gateway_host1:port
gateway_host2:port
...

-dn
-UserName
-un
-Password
-pd
-SecurityDomain
-sdn
-Gateway
-hp
UpdateWSHubService
567
Option
Argument
Description
-ResilienceTimeout
-re
timeout_period_in_s
econds

-ServiceName
service_name

upgrade contents.
-sn
UpgradeDARepositoryUsers
Upgrades users and groups in a Data Analyzer repository. When you upgrade the users and groups in the
Data Analyzer repository, the Service Manager moves them to the Informatica domain.
The infacmd isp UpgradeDARepositoryUsers command uses the following syntax:
<-MigrateSecurityDomain|-msd> migrate_securitydomain
568
The following table describes infacmd isp UpgradeDARepositoryUsers options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
user_name

takes precedence.
-dn
-UserName
-un

run the command with single sign-on, do not set the
user name. If you set the user name, the command runs
-Password
password

set a password with both methods, the password set
security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
-ResilienceTimeout
-re
gateway_host1:port

ds

569
Option
Argument
Description
-ServiceName
service_name
Required. Name of the Reporting Service for the

repository for which you want to upgrade the users and
groups.
migrate_securitydomain
Required. Name of the security domain to which you are

moving the uses and groups.
-sn
-MigrateSecurityDomain
-msd
validateFeature
Validates that the feature in the specified plug-in file is registered in the domain.
The infacmd isp validateFeature command uses the following syntax:
validateFeature
<-FeatureFilename|-ff> feature_filename
The following table describes infacmd isp validateFeature options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

570
Option
Argument
Description
-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
gateway_host1:port
-hp
-ResilienceTimeout
-re
ds

-FeatureFilename
feature_filename
Required. Path and file name of the plug-in xml file of

the registered feature that you want to validate.
-ff

domains.infa file is out of date.The host names and
Version
Displays the PowerCenter version and Informatica trademark and copyright information.
The version command uses the following syntax:
infacmd version
Version
571
CHAPTER 14
infacmd mrs Command Reference

572
BackupContents, 573
CheckInObject, 575
CreateContents, 577
CreateFolder, 579
CreateProject, 580
CreateService, 582
DeleteContents, 585
DeleteFolder, 587
DeleteProject, 588
ListBackupFiles, 590
ListCheckedOutObjects, 592
listFolders, 593
ListLockedObjects , 595
ListProjects, 597
PopulateVCS, 602
ReassignCheckedOutObject, 603
rebuildDependencyGraph, 605
RenameFolder, 607
RestoreContents, 608
UndoCheckout, 610
UnlockObject , 611
UpgradeContents, 620
BackupContents
Backs up the Model repository content to a file. If the repository content does not exist, the command fails.
To ensure that a consistent backup file is created, the backup operation blocks all other repository operations
until the backup completes.
The infacmd mrs BackupContents command uses the following syntax:
BackupContents
<-OutputFileName|-of> output_file_name
[<-OverwriteFile|-ow> overwrite_file]
[<-Description|-ds> description]
[<-BackupSearchIndices|-bsi> backup search index]
BackupContents
573
The following table describes infacmd mrs BackupContents options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
Required. Name of the Model Repository Service.
output_file_name
Required. Name of the backup file.
overwrite_file
You must include this option to overwrite a backup file

that has the same name.
description
Description of backup file. If the description contains

spaces or other non-alphabetic characters, enclose
the description in quotation marks.
-pd
-ServiceName
-sn
OutputFileName
-of
OverwriteFile
-ow
Description
-ds
574
Chapter 14: infacmd mrs Command Reference
Option
Argument
Description
-BackupSearchIndices
Optional. Set to true to save the search index to the

backup file and reduce the amount of time needed to
restore the file. Set to false to not save the search
index to the backup file. When you restore the file, the
Model Repository Service re-indexes the search index.
Default is true.
nds

-bsi
-ResilienceTimeout
-re
CheckInObject
Checks in a single object that is checked out. The object is checked in to the Model repository.
The infacmd mrs CheckInObject command uses the following syntax:
infacmd mrs checkInObject
<-ObjectPathandName|-opn> object_path_and_name
[<-Description|-ds> description]
CheckInObject
575
The following table describes infacmd mrs CheckInObject options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
Required. Model Repository Service name.
ds

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
576
Option
Argument
Description
-ObjectPathAndName
MRS_object_path
Required. Path to the Model repository object,

including the object name.
-opn
Enclose the path in double quotes. Use the following

syntax:
"ProjectName/FolderName/.../
SubFolder_Name/{ObjectName|
ProjectName/ObjectName}"
-Description
description
-ds
Optional. You can use this parameter for the check-in

description or comments.
CreateContents
Creates repository content for a Model repository. The command fails if the content exists for the Model
repository.
The infacmd mrs CreateContents command uses the following syntax:
CreateContents
CreateContents
577
The following table describes infacmd mrs CreateContents options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
ds

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
578
CreateFolder
Creates a folder in a project in a Model repository.
The infacmd mrs CreateFolder command uses the following syntax:
infacmd mrs createFolder
<-ProjectName|-pn> project_name
<-Path|-p> folder_path_and_name
[<-CreatePath|-cp> true|false]
The following table describes infacmd mrs CreateFolder options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
security_domain

sensitive.
-dn
-SecurityDomain
-sdn

installation.
-UserName
user_name
-un

takes precedence.
-Password
-pd
password

CreateFolder
579
Option
Argument
Description
-ServiceName
service_name
project_name
Required. Name of the project to create the folder in.
-sn
-ProjectName
-pn
The project name is not case sensitive.
-Path
-p
folder_path_and_nam
e
Required. Path and name of the folder to create.

The path name must start with a forward slash (/). The
name is not case sensitive. The name cannot exceed 128
characters or contain carriage returns, tabs, spaces, or
/ * ? < > " |
-CreatePath
true|false
Optional. If true, creates the folder in the specified path.

Default is false.
conds

takes precedence.
-cp
-ResilienceTimeout
-re
CreateProject
Creates a project in a Model repository.
The infacmd mrs CreateProject command uses the following syntax:
infacmd mrs createProject
580
The following table describes infacmd mrs CreateProject options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
security_domain

sensitive.
-dn
-SecurityDomain
-sdn

installation.
-UserName
user_name
-un

takes precedence.
-Password
password

service_name
-pd
-ServiceName
-sn
CreateProject
581
Option
Argument
-ProjectName
project_name
-pn
Description
Required. Name of the project to create.
The project name is not case sensitive. The name cannot
exceed 128 characters or contain carriage returns, tabs,
spaces, or the following characters:
/ * ? < > " |
-ResilienceTimeout
-re
conds

takes precedence.
CreateService
Creates a Model Repository Service. Before you create the Model Repository Service, you need to create a
database to store repository tables. Use the database client to create the database.
Each Model repository must meet the following database requirements:
The Model repository must have a unique schema. Two Model repositories or the Model repository and
the domain configuration database cannot share the same schema.
The Model repository must have a unique repository database name.
The infacmd mrs CreateService command uses the following syntax:

CreateService
<-DbUser|-du> db_user
<-DbPassword|-dp> db_password
<-DbUrl|-dl> db_url
[<-DbDriver|-dr> db_driver]
[<-DbDialect|-dd> db_dialect]
[<-SearchIndexRoot|-si> search_index_root]
[<-DbType|-dt> db_type]
[<-DbSchema|-ds> db_schema]
582
[<-DbTablespace|-db> db_tablespace (used for DB2 only)]

[<-BackupNodes|-bn> nodename1,nodename2,...]
The following table describes infacmd mrs CreateService options and arguments:
Option
Argument
Description
-DomainName
domain_name

node_name
Required. Node where you want to run the Model

Repository Service to run.
security_domain

case sensitive.
-dn
NodeName
-nn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
-pd
password

CreateService
583
Option
Argument
Description
-ServiceName
service_name
db_user
Required. Account for the repository database. Set up

this account using the database client.
db_password
Required. Repository database password for the

database user.
db_url
Required.
-sn
-DbUser
-du
-DbPassword
-dp
-DbUrl
-dl
The JDBC connection string used to connect to the

Model repository database.
Use the following JDBC connect string syntax for each
supported database:
- IBM DB2. jdbc:informatica:db2://
<host_name>:<port_number>;DatabaseNa
me=<database_name>;BatchPerformanceW
orkaround=true;DynamicSections=3000
- Microsoft SQL Server that uses the default instance.
<host_name>:<port_number>;DatabaseNa
me=<database_name>;SnapshotSerializa
ble=true
- Microsoft SQL Server that uses a named instance.
<host_name>
\<named_instance_name>;DatabaseName=
<database_name>;SnapshotSerializable
=true
- Oracle. jdbc:informatica:oracle://
<host_name>:<port_number>;SID=<datab
ase_name>;MaxPooledStatements=20;Cat
alogOptions=0;BatchPerformanceWorkar
ound=true
-DbDriver
db_driver
-dr
Optional. The Data Direct driver to connect to the

database. For example:
com.informatica.jdbc.oracle.OracleDriver
-DbDialect
db_dialect
-dd
Optional. The SQL dialect for a particular database.

The dialect maps java objects to database objects.
For example:
org.hibernate.dialect.Oracle9Dialect
-SearchIndexRoot
search_index_root
Optional. Changes the directory for the search index.

Enter the full path to the directory. Default is the
Informatica installation directory.
db_type
Optional. Values are Oracle, SQL Server, or DB2.
db_schema
Optional. The schema name for a Microsoft SQL

Server database.
-si
-DbType
-dt
-DbSchema
-ds
584
Option
Argument
Description
-DbTablespace
db_tablespace
Required for a DB2 database only. When you

configure a tablespace name, the Model Repository
Service creates all repository tables in the same
tablespace. You cannot use spaces in the tablespace
name.
-re
ds

-FolderPath
full_folder_path

folder in which you want to create the service. Must be
in the following format:
-dt
-ResilienceTimeout
-fp
-BackupNodes
-bn
nodename1,nodename2,.
..

DeleteContents
Deletes the Model repository content. The command fails if the content does not exist for the Model
repository.
The infacmd mrs DeleteContents command uses the following syntax:
DeleteContents
DeleteContents
585
The following table describes infacmd mrs DeleteContents options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
ds

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
586
DeleteFolder
Deletes a folder from a project in a Model repository.
To delete a folder that contains objects, set the -ForceDelete option to true.
The infacmd mrs DeleteFolder command uses the following syntax:
infacmd mrs deleteFolder
<-Path|-p> folder_path_and_name
[<-ForceDelete|-f> true|false]
The following table describes infacmd mrs DeleteFolder options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
security_domain

sensitive.
-dn
-SecurityDomain
-sdn

installation.
-UserName
-un
user_name

takes precedence.
DeleteFolder
587
Option
Argument
Description
-Password
password

service_name
project_name
Required. Name of the project that contains the folder.
-p
folder_path_and_nam
e
Required. Path and name of the folder to delete. Path

must start with a forward slash (/).
-ForceDelete
true|false
Optional. If true, deletes a folder that contains objects.

Default is false.
conds

takes precedence.
-pd
-ServiceName
-sn
-ProjectName
-pn
-Path
-f
-ResilienceTimeout
-re
DeleteProject
Deletes a project in a Model repository.
To delete a project that contains folders and objects, set the -ForceDelete option to true.
The infacmd mrs DeleteProject command uses the following syntax:
infacmd mrs deleteProject
[<-ForceDelete|-f> true|false]
588
The following table describes infacmd mrs DeleteProject options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
security_domain

sensitive.
-dn
-SecurityDomain
-sdn

installation.
-UserName
user_name
-un

takes precedence.
-Password
password

service_name
project_name
Required. Name of the project to delete.
-pd
-ServiceName
-sn
-ProjectName
-pn
DeleteProject
589
Option
Argument
Description
-ForceDelete
true|false
Optional. If true, deletes a project that contains folders

and objects. Default is false.
conds

takes precedence.
-f
-ResilienceTimeout
-re
ListBackupFiles
Lists files in the backup folder.
The infacmd mrs ListBackupFiles command uses the following syntax:
ListBackupFiles
590
The following table describes infacmd mrs ListBackupFiles options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
ds

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
ListBackupFiles
591
ListCheckedOutObjects
Displays a list of objects that are checked out by a user. Run this command against a repository that is
integrated with a version control system.
The infacmd mrs listCheckedOutObjects command uses the following syntax:
infacmd mrs listCheckedOutObjects
[<-ByUser|-bu> by_user_name]
[<-ByUserSecurityDomain|-bsd> by_user_security_domain]
[<-ObjectType|-ot> object_type]
[<-ByObjectPathandName|-bopn> object_path_and_name]
[<-objectName|-objn> object_name]
[<-operationType|-optype> operation_type]
The following table describes infacmd mrs listCheckedOutObjects options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
592
Option
Argument
Description
-Password
password

service_name
-re
ds

-ByUser
checkedout_by_user
Optional. User account that has checked out objects in

the Model repository.
object_type
Optional. Type of the object to search. For example,

mapping.
object_path_and_name
Optional. Path and name of the object to search.
object_name
Optional. Name of the object to search.
operation_type
Optional. Type of the operation to search. Enter one of

-pd
-ServiceName
-sn
-ResilienceTimeout
-bu
-ObjectType
-ot
-ByObjectPathandName
-bopn
-ObjectName
-objn
-LastOperationType
-optype
ADD_OP
EDIT_OP
MOVE_OP
DELETE_OP
listFolders
Lists the names of all of the folders in the project folder path that you specify.
Use the -Path option to list all the folders in a project, or all the folders that a subfolder contains. Use a slash
character (/) to specify the top level of a project.
For example, the following command lists all the folders in /MRS_1/Project_A/:
infacmd mrs listFolders ... -sn MRS_1 -pn Project_A -p /
If the contents of Project _A are Folder_1 and Folder_2, then the following command lists all the subfolders in
Folder_1:
infacmd mrs listFolders ... -sn MRS_1 -pn Project_A -p /Folder_1/
listFolders
593
The infacmd mrs ListFolders command uses the following syntax:

infacmd mrs listFolders
<-Path|-p> path
The following table describes infacmd mrs ListFolders options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
-pd
-ServiceName
-sn
594
Option
Argument
Description
-Path
path
Required. Path to the parent folder in which you want

to list folder contents.
-p
The path must start with a slash (/). The name is not
case sensitive.
-ResilienceTimeout
-re
ds

ListLockedObjects
Displays a list of objects that are locked by a user. Run this command against a repository that is not
Note: If you run this command against a versioned repository, the command fails.
The infacmd mrs listLockedObjects command uses the following syntax:
infacmd mrs listLockedObjects
[<-ByUser|-bu> user_name]
[<-ByUserSecurityDomain|-bsd> by_user_security_domain]
[<-ObjectType|-ot> object_type]
[<-ByObjectPathandName|-bopn> object_path_and_name]
[<-objectName|-objn> object_name]
[<-lastOperationType|-optype> operation_type]
ListLockedObjects
595
The following table describes infacmd mrs listLockedObjects options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
ds

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
596
Option
Argument
Description
-ByUser
locked_by_user
Optional. User account that owns the lock on objects

in the Model repository. Default is objects locked by all
users.
object_type
Optional. Type of the object to search. You can run

the command against one object type. If you omit the
parameter, the command runs against all object types.
object_path_and_name
Optional. Model repository path and name of the

object to search.
object_name
Optional. Name of the object to search.
operation_type
Optional. Type of the operation to search. Enter one of

-bu
-ObjectType
-ot
-ByObjectPathAndName
-bopn
-ObjectName
-objn
-LastOperationType
-optype
ADD_OP
EDIT_OP
MOVE_OP
DELETE_OP
ListProjects
Lists projects in the Model repository. The command fails if the Model repository does not have repository
content.
The infacmd mrs ListProjects command uses the following syntax:
ListProjects
ListProjects
597
The following table describes infacmd mrs ListProjects options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
ds

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
598
ListServiceOptions
Lists options for the Model Repository Service.
The infacmd mrs ListServiceOptions command uses the following syntax:
ListServiceOptions
The following table describes infacmd mrs ListServiceOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
-un
user_name

precedence.
ListServiceOptions
599
Option
Argument
Description
-Password
password

service_name
ds

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
Lists service process options for the Model Repository Service.
The infacmd mrs ListServiceProcessOptions command uses the following syntax:
ListServiceOptions
600
The following table describes infacmd mrs ListServiceProcessOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
ds

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
601
PopulateVCS
Synchronizes the Model repository with a version control system. Before you synchronize the Model
repository with a version control system, you configure versioning properties.
When you configure versioning properties, you restart the Model repository, and then you run the
PopulateVCS command.
Note: After you run the command, the Model repository is unavailable until synchronization completes.
The infacmd mrs populateVCS command uses the following syntax:
infacmd mrs populateVcs
The following table describes infacmd mrs populateVCS options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
602
Option
Argument
Description
-Password
password

service_name
ds

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
ReassignCheckedOutObject
Reassigns the ownership of a checked-out object to another user. If the owner of a checked-out object saved
changes, the changes are retained when you reassign the object. If the changes are not saved, the changes
are lost when you reassign the object.
The infacmd mrs reassignCheckedOutObject command uses the following syntax:
<-ObjectPathandName|-opn> object_path_and_name
<-ToUser|-tu> to_user
[<-ToUserSecurityDomain|-tsd> to_user_security_domain]
ReassignCheckedOutObject
603
The following table describes infacmd mrs reassignCheckedOutObject options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
ds

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
604
Option
Argument
Description
-ObjectPathAndName
MRS_object_path
Required. Use the following syntax:

ProjectName/FolderName/.../
ProjectName/ObjectName}
Username
Required. Username of the user who you want to own

the object checked-out state.
Security domain
Optional. Security domain of the user who you want to

own the object checked-out state.
-opn
-ToUser
-tu
-ToUserSecurityDomain
-tsd
rebuildDependencyGraph
Rebuilds the object dependency graph so that you can view object dependencies after an upgrade. Run this
command if the upgrade of the Model Repository Service failed to rebuild the object dependency graph.
Users must not access Model repository objects until the rebuild process completes, or the object
dependency graph might not be accurate. You might want to run the command when users are not logged in.
The infacmd mrs rebuildDependencyGraph command uses the following syntax:
605
The following table describes infacmd mrs rebuildDependencyGraph options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
ds

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
606
RenameFolder
Renames a folder in a project.
The infacmd mrs RenameFolder command uses the following syntax:
infacmd mrs renameFolder
<-SourceFolder|-sf> source_folder
<-TargetFolder|-tf> target_folder
The following table describes infacmd mrs RenameFolder options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
security_domain

sensitive.
-dn
-SecurityDomain
-sdn

installation.
-UserName
user_name
-un

takes precedence.
-Password
-pd
password

RenameFolder
607
Option
Argument
Description
-ServiceName
service_name
project_name
Required. Name of the project that contains the folder to

rename.
source_folder_path_a
nd_name
Required. Path and name of the folder to rename. Path

must start with a forward slash (/).
-sn
-ProjectName
-pn
-SourceFolder
-sf
-TargetFolder
-tf
-ResilienceTimeout
-re
target_folder_path_an
d_name
conds
Required. New name for the folder.

You can specify a folder name, or a path and folder name.
The path must start with a forward slash (/).
takes precedence.
RestoreContents
Restores content of a Model repository from a backup file.
The infacmd mrs RestoreContents command uses the following syntax:
RestoreContents
<-InputFileName|-if> input_file_name
[<-ResilienceTimeout|-re> timeout_period_in_seconds
608
The following table describes infacmd mrs RestoreContents options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
Required. Name of the Model RepositoryService to

back up.
input_file_name
Required. Name of the backup file to restore.
ds

-pd
-ServiceName
-sn
InputFileName
-if
-ResilienceTimeout
-re
RestoreContents
609
UndoCheckout
Reverts the checkout of a Model repository object. The object is checked in to the Model repository. The
Model repository discards any changes to the object since it was checked out. The version control system
does not increment the version number or add to the version history.
The infacmd mrs undoCheckout command uses the following syntax:
infacmd mrs undoCheckout
<-ObjectPathAndName|-opn> Object_path_and_name
The following table describes infacmd mrs undoCheckout options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
610
Option
Argument
Description
-Password
password

service_name
-re
ds

-ObjectPathAndName
MRS_object_path

-pd
-ServiceName
-sn
-ResilienceTimeout
-opn
Enclose the path in double quotes. Use the following

syntax:
"ProjectName/FolderName/.../
ProjectName/ObjectName}"
UnlockObject
Unlocks a Model repository object that is locked by a user. Run this command against a repository that is not
Note: If you run this command against a versioned repository, the command fails.
You can unlock one object at a time.
The infacmd mrs unlockObject command uses the following syntax:
infacmd mrs unlockObject
<-ObjectPathAndName|-opn> Object_path_and_name
UnlockObject
611
The following table describes infacmd mrs unlockObject options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
-pd
-ServiceName
-sn
612
Option
Argument
Description
-ResilienceTimeout
-re
ds

-ObjectPathAndName
MRS_object_path

-opn
For example, use the following syntax:

ProjectName/FolderName/SubFolder_Name/
ObjectName
Updates options for the Model Repository Service. Separate multiple options with a space. To enter a value
that contains a space or other non-alphanumeric character, enclose the value in quotation marks.
The infacmd mrs UpdateServiceOptions command uses the following syntax:
[<-PrimaryNode|-nn> primary node name]
[<-BackupNode|-bn> nodename1,nodename2,...]
[<-SearchIndexRoot|-si> search_index_root]
613
The following table describes infacmd mrs UpdateServiceOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
-re
ds

-Options
options
Required. Enter name-value pair separated by spaces.
-pd
-ServiceName
-sn
-ResilienceTimeout
-o
614
Option
Argument
Description
-PrimaryNode
primary node name
Optional. Node where you want to run the Model

Repository Service to run.
nodename1,nodename2,.
..

-nn
-BackupNodes
-bn
-SearchIndexRoot
Optional. Changes the directory for the search index.

Enter the full path to the directory. Default is the
-si
Model Repository Service Options

Use the Model Repository Service options with the infacmd mrs UpdateServiceOptions command.
Enter Model Repository Service options in the following format:
The following table describes Model Repository Service options:
Option
Argument
Description
CACHE.EnableCache
true | false
Enables the Model Repository Service to store Model

repository objects in cache memory. To apply
changes, restart the Model Repository Service.
CACHE.CacheJVMOptions
-Xmx[heap_size]
JVM options for the Model Repository Service cache.

To configure the amount of memory allocated to
cache, configure the maximum heap size. This field
must include the maximum heap size, specified by
the -Xmx option. The default value and minimum
value for the maximum heap size is -Xmx128m.
The options you configure apply when Model
Repository Service cache is enabled. To apply
changes, restart the Model Repository Service. The
options you configure in this field do not apply to the
JVM that runs the Model Repository Service.
PERSISTENCE_DB.Usernam
e
db_user
Required. Account for the repository database. Set

up this account using the database client.
PERSISTENCE_DB.Password
db_password
Required. Repository database password for the

database user.
PERSISTENCE_DB.Database
Schema
db_schema
Optional. The schema name for a particular

database.
615
Option
Argument
Description
Tablespace
db_tablespace

configure a tablespace name, the Model Repository
Service creates all repository tables in the same
tablespace. You cannot use spaces in the tablespace
name.
For a multi-partition IBM DB2 database, the
tablespace must span a single node and a single
partition.
Type
DatabaseType
PERSISTENCE_DB.JDBCCon
nectString
JDBC Connect String
Required. Database types include:

-
db2
oracle
mssqlserver
sybase
The JDBC connection string used to connect to the

Model repository database.
Use the following JDBC connect string syntax for
each supported database:
- IBM DB2. jdbc:informatica:db2://
<host_name>:<port_number>;DatabaseN
ame=<database_name>;BatchPerformanc
eWorkaround=true;DynamicSections=30
00
- Microsoft SQL Server that uses the default instance.
<host_name>:<port_number>;DatabaseN
ame=<database_name>;SnapshotSeriali
zable=true
- Microsoft SQL Server that uses a named instance.
<host_name>
\<named_instance_name>;DatabaseName
=<database_name>;SnapshotSerializab
le=true
- Oracle. jdbc:informatica:oracle://
<host_name>:<port_number>;SID=<data
base_name>;MaxPooledStatements=20;C
atalogOptions=0;BatchPerformanceWor
karound=true
PERSISTENCE_DB.SecureJD
BCParameters
Secure JDBC
Parameters
If the Model repository database is secured with the

SSL protocol, you must enter the secure database
parameters.
Enter the parameters as name=value pairs
separated by semicolon characters (;). For example:
param1=value1;param2=value2
PERSISTENCE_DB.Dialect
Dialect
The SQL dialect for a particular database. The

dialect maps java objects to database objects.
For example:
org.hibernate.dialect.Oracle9Dialect
616
Option
Argument
Description
PERSISTENCE_DB.Driver
Driver
The Data Direct driver used to connect to the

database.
For example:
com.informatica.jdbc.oracle.OracleDri
ver
SEARCH.SearchAnalyzer
Fully qualified Java

class name
Fully qualified Java class name of the search

analyzer.
By default, the Model Repository Service uses the
following search analyzer for English:
com.informatica.repository.service.pr
ovider.search.analysis.MMStandardAnal
yzer
You can specify the following Java class name of the
search analyzer for Chinese, Japanese and Korean
languages:
org.apache.lucene.analysis.cjk.CJKAna
lyzer
Or, you can create and specify a custom search
analyzer.
SEARCH.SearchAnalyzerFact
ory
Fully qualified Java

class name
Fully qualified Java class name of the factory class if

you used a factory class when you created a custom
search analyzer.
If you use a custom search analyzer, enter the name
of either the search analyzer class or the search
analyzer factory class.
VCS.Host
IP_address or host
name
Required to configure versioning properties for the

Model repository on Perforce.
The URL, IP address, or host name of the machine
where the Perforce version control system runs.
Do not use this option when you configure SVN as
the version control system.
VCS.URL
URL of the Subversion

repository

Model repository on SVN.
URL of the Subversion repository. For example:
VCS.URL=https://
myserver.company.com/svn/
Do not use this option when you configure Perforce
as the version control system.
VCS.Port
VCS_port

Model repository.
Port number that the version control system host
uses to listen for packets from the Model repository.
617
Option
Argument
Description
VCS.User
VCS_user

Model repository.
User account for the version control system user.
This account must have write permissions on the
version control system. After you configure the
connection with this single version control system
user and password, all Model repository users
connect to the version control system through this
account.
For the Perforce version control system, the account
type must be a Standard user.
VCS.Password
VCS_password

Model repository.
Password for the version control system user.
VCS.Type
VCS_type

Model repository.
The supported version control system that you want
to connect to. You can choose Perforce or SVN.
VCS.MRSPath
MRS_path

Model repository with Perforce.
Path to the root directory of the version control
system copy of Model repository objects.
Note: When you run the command, the Model
repository connects to the version control system and
generates the specified directory if the directory does
not exist yet.
Only one Model Repository Service can use this
directory.
For Perforce, use the syntax:
//directory/path
where directory is the Perforce directory root,
and path is the remainder of the path to the root
directory of Model repository objects.
Example:
//depot/Informatica/repository_copy
Do not use this option when you configure SVN as
the version control system.
Updates service process options for the Model Repository Service. Separate multiple options with a space.
To enter a value that contains a space or other nonalphanumeric character, enclose the value in quotation
marks.
Enter service process options in the following format:
618
The infacmd mrs UpdateServiceProcessOptions command uses the following syntax:

The following table describes infacmd mrs UpdateServiceProcessOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
-un
user_name

precedence.
619
Option
Argument
Description
-Password
password

service_name
-re
ds

-Options
options
Required. Enter name-value pair separated by spaces.
-pd
-ServiceName
-sn
-ResilienceTimeout
-o
UpgradeContents
Upgrades the contents of the Model repository. The command fails if the Model repository does not have
repository content.
The infacmd mrs UpgradeContents command uses the following syntax:
UpgradeContents
620
The following table describes infacmd mrs UpgradeContents options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
ds

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
UpgradeContents
621
CHAPTER 15
infacmd ms Command Reference

GetRequestLog, 622
ListMappingParams, 624
ListMappings, 626
RunMapping, 628
UpgradeMappingParameterFile, 632
GetRequestLog
Writes the mapping log to the specified file. Enter the job ID returned by the infacmd ms RunMapping
command.
The infacmd ms GetRequestLog command uses the following syntax:
GetRequestLog
<-RequestId|-id> request_id
622
The following table describes infacmd ms GetRequestLog options and arguments:

Option
Argument
Description
-DomainName
domain_name

service_name

ran the mapping.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

is case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
s

the resilience timeout perioud with both methods, the
-re option takes precedence.
GetRequestLog
623
Option
Argument
Description
-RequestId
request_id
Required. The job ID for the mapping that you want to

write the log file for. Enter the job ID returned by the
infacmd ms RunMapping command.
file_name
Required. Name and file path where you want to write

the log file.
-id
-FileName
-f
ListMappingParams
Lists the parameters for a mapping and creates a mapping parameter file that you can use when you run a
mapping. The command returns an XML file with default values that you can update. Enter the parameter file
name when you run the mapping with infacmd ms RunMapping.
The infacmd ms ListMappingParams command uses the following syntax:
ListMappingParams
<-Application|-a> application_name
<-Mapping|-m> mapping_name
[<-OutputFile|-o> output file_to_write_to]
The following table describes infacmd ms ListMappingParams options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
Required. Name of the Data Integration Service to run

the mapping. The application that contains the
mapping must be deployed to a Data Integration
Service.
-dn
-ServiceName
-sn
624
Chapter 15: infacmd ms Command Reference
Option
Argument
Description
-UserName
user_name

precedence.
-un

-Password
password

security_domain

is case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
s

-Application
application_name

mapping.
mapping_name
Required. Name of the mapping.
output file_to_write_to
Optional. Path and file name of the parameter file to

create. If you do not specify a file, the command
displays the parameters in the command prompt.
-a
-Mapping
-m
- OutputFile
-o
ListMappingParams
625
ListMappingParams Output
The ListMappingParams command returns a parameter file as an XML file with default values that you can
update.
For example, you run the ListMappingParams command on application "MyApp" and mapping "MyMapping."
Mapping "MyMapping" has one parameter "MyParameter." The ListMappingParams command returns an
XML file in the following format:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<root xmlns="http://www.informatica.com/Parameterization/1.0" xmlns:xsi="http://
www.w3.org/2001/XMLSchema">
<!-<application name="MyApp">
<mapping name="MyMapping">

</mapping>
</application>
-->
<project name="MyProject">
<mapping name="MyMapping">
<parameter name="MyParameter">DefaultValue</parameter>
</mapping>
</project>
</root>
The output XML file has the following top-level elements:
Application element
When you define a parameter within the application top-level element, the Data Integration Service
applies the parameter value when you run the specified mapping in the specified application. You must
include at least one project element within an application/mapping element.
By default, this top-level element is in comments. Remove the comments (!-- and -->) to use this
element.
Project element
When you define a parameter within a project top-level element, the Data Integration Service applies the
parameter value to the specified mapping in the project in any deployed application. The service also
applies the parameter value to any mapping that uses the objects in the project.
If you define the same parameter in a project and an application top-level element in the same parameter file,
the parameter value defined in the application element takes precedence.
ListMappings
Lists the mappings in an application.
The infacmd ms ListMappings command uses the following syntax:
ListMappings
626
The following table describes infacmd ms ListMappings options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

is case sensitive.
-pd
-SecurityDomain
-sdn

ListMappings
627
Option
Argument
Description
-ResilienceTimeout
-re
s

the resilience timeout perioud with both these
methods, the -re option takes precedence.
-ServiceName
service_name

Service.
application_name

mapping.
-sn
-Application
-a
RunMapping
Runs a mapping that is deployed to a Data Integration Service. You can run the mapping with a parameter
set or a parameter file.
To create a parameter file for a mapping, run infacmd ms ListMappingParams. Before you run infacmd ms
ListMappingParams, run the infacmd dis StartApplication command for the application.
To view the parameters and values for a parameter set, run the command infacmd dis
ListParameterSetEntries.
The infacmd ms RunMapping command uses the following syntax:
RunMapping
[<-Wait|-w> true|false]
[<-ParameterFile|-pf> parameter_file_path]
[<-ParameterSet|-ps> parameter_set_name]
[<-OptimizationLevel|-ol> optimization_level]
628
[<-PushdownType|-pt> pushdown_type]
[<-CustomProperties|-cp> custom_properties]
The command returns the job ID for the mapping run.
The following table describes infacmd ms RunMapping options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

Service.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

is case sensitive.
-pd
-SecurityDomain
-sdn

RunMapping
629
Option
Argument
Description
-ResilienceTimeout
-re
s

-Application
application_name

mapping.
mapping_name
Required. Name of the mapping to run.
true|false
Optional. Indicates whether infacmd waits for the

mapping to complete before returning to the shell or
command prompt. If true, infacmd returns to the shell
or command prompt after the mapping completes.
You cannot run subsequent commands until the
mapping completes. If false, infacmd returns to the
shell or command prompt immediately. You do not
have to wait for the mapping to complete before
running the next command. Default is false.
parameter_file_path
Optional. Name and path of the parameter file. Do not

enter a parameter file and a parameter set.
parameter_set_name
Optional. Name of a parameter set to use at run time.

The parameter set option overrides any parameter set
deployed with the application. Do not enter a
parameter set and a parameter file.
node_name
Optional. Name of the node in a Data Integration

Service grid to dispatch the mapping job to. A Data
Integration Service process must be running on the
node.
-a
-Mapping
-m
-Wait
-w
-ParameterFile
-pf
-ParameterSet
-ps
-NodeName
-nn
If you do not use this option, the mapping job is

dispatched to the node where the master Data
Integration Service process runs.
630
Option
Argument
Description
-OptimizationLevel
optimization_level
Optional. Controls the optimization methods that the

Data Integration Service applies to the mapping.
Enter the numeric value that is associated with the
optimization level that you want to configure. Enter
one of the following numeric values:
-ol
- 0 (None). The Data Integration Service does not apply

any optimization.
- 1 (Minimal). The Data Integration Service applies the
early projection optimization method.
- 2 (Normal). The Data Integration Service applies the
early projection, early selection, branch pruning, pushinto, pushdown, and predicate optimization methods.
Normal is the default optimization level.
- 3 (Full). The Data Integration Service applies the costbased, early projection, early selection, branch
pruning, predicate, push-into, pushdown, and semijoin optimization methods.
If you do not use this option, the Data Integration

Service applies the optimization level configured in
the mapping properties for the deployed application in
the Administrator tool.
-PushdownType
pushdown_type
-pt
Optional. Controls the pushdown type that the Data

Integration Service applies to a mapping. Enter one of
- None. Select no pushdown type for the mapping.
- Source. The Data Integration Service tries to push
down as much transformation logic as it can to the
source database.
- Full. The Data Integration Service pushes the full
transformation logic to the source database.
This option overrides the pushdown type set in the

mapping run-time properties or in a parameter file or
parameter set.
If you do not use this option, the Data Integration
Service applies the pushdown type set in the mapping
run-time properties or in a parameter file or parameter
set.
-CustomProperties
-cp
custom_properties
Optional. Define custom properties for a mapping at

the request of Informatica Global Customer Support.
Enter custom properties as name-value pairs
separated by semicolons. For example:
... -cp custom_property_name=value
To enter a value that contains a space or other nonalphanumeric character, enclose the value in
quotation marks.
RunMapping
631
UpgradeMappingParameterFile
Converts a parameter file you created in a previous Informatica version to a parameter file format that is valid
for Informatica version 10.0.
In Informatica version 10.0, a parameter file can contain mapping parameters and workflow parameters, but it
no longer contains transformation parameters. When you run a mapping or workflow with the previous
version parameter file, the Data Integration Service must convert the parameter file to the Informatica 10.0
version at run time. You can increase performance by converting parameter files to the Informatica 10.0
format.
The infacmd ms upgradeMappingParameterFile command uses the following syntax:
<-ParameterFile|-pf> parameter_file_to_upgrade
The following table describes infacmd ms upgradeMappingParameterFile options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

Service.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

632
Option
Argument
Description
-Password
password

security_domain

is case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
s

-Application
application_name

mapping.
mapping_name

parameter_file_to_upgrad
e
Required. The name of the parameter file to upgrade.
-a
-Mapping
-m
- OutputFile
-o
-ParameterFile
-pf
633
CHAPTER 16
infacmd oie Command Reference

DeployApplication, 634
ExportObjects, 635
exportResources, 637
ImportObjects, 639
DeployApplication
Deploys an application to an .iar file.
Deploy an application to a file when the application contains a large number of objects. After you run the
infacmd oie deployApplication command, run the infacmd dis DeployApplication command to deploy the
application to a Data Integration Service.
The infacmd oie DeployApplication command uses the following syntax:
DeployApplication
<-DomainName|-dn> Domain name
<-UserName|-un> User name
<-ModelRepositoryService|-rs> Model Repository Service
<-OutputDirectory|-od> Output directory
<-ApplicationPath|-ap> Application path
634
The following table describes infacmd oie DeployApplication options and arguments:
Option
Argument
Description
-DomainName
Domain name

User name

-dn
-UserName
-un

sign-on.
-Password
Password
Model Repository
Service
Output Directory
Required. Directory where you want to write the .iar file.
Application Path
Required. Application path, starting with the project name,

folder names, and followed by the application name.
Separate the project name, folder names, and the application
name with a slash (/). For example, "Project/Folder1/Folder2/
Application".
-pd
ModelRepositoryService
-rs
- OutputDirectory
-od
- ApplicationPath
-ap
ExportObjects
Exports objects from a project in the Model repository to an XML file.
If you do not want to export all objects in the project, use an infacmd export control file to filter the Model
repository objects that you want to export.
If the project being exported contains reference tables, you must run the command from the Informatica
services installation directory. The command exports the reference table metadata from the Model repository
to the XML file. The command exports the reference table data to a zip file. When you run the command,
specify the path and file name of both the XML and zip files to be created.
The command does not export empty folders.
increase system memory, set the -Xmx value in the ICMD_JAVA_OPTS environment variable.
ExportObjects
635
The infacmd oie ExportObjects command uses the following syntax:

ExportObjects
[<-SecurityDomain|-sdn> Security domain]
<-ProjectName|-pn> Project name
<-RepositoryService|-rs> Model Repository Service name
<-ExportFilePath|-fp> Path of file to export to
[<-OverwriteExportFile|-ow> Set to "true" to overwrite export file if it exists.]
[<-ControlFilePath|-cp> Path of export control file]
[<-OtherOptions|-oo>]
The following table describes infacmd oie ExportObjects options and arguments:
Option
Argument
Description
-DomainName
Domain name

User name

-dn
-UserName
-un

sign-on.
-Password
Password
Security domain

-pd
-SecurityDomain
-sdn

636
Chapter 16: infacmd oie Command Reference
Option
Argument
Description
-ProjectName
Project name
Required. Name of the project from which you export the

objects.
Model Repository
Service name
Path of file to export

to
Required. Path and XML file name of the export file to be

created. You can specify an absolute path or a relative path
to the file name.Use an easily distinguishable name for the
file. For example, use the following suggested naming
convention:
-pn
-RepositoryService
-rs
-ExportFilePath
-fp
exp_<project_name>.xml
-OverwriteExportFile
Set to "true" to
overwrite export file
if it exists.
Optional. Set to true to overwrite an existing export file. If an

export file exists and this option is set to false, the export
fails. Default is false.
-cp
Path of export
control file
Optional. Path and file name of the export control file that
filters the objects that are exported. You can specify an
absolute path or a relative path to the file name.
-OtherOptions
Required if the project being exported contains reference

tables. Additional options to export reference table data to a
zip file. Enter options using the following format:
-ow
-ControlFilePath
-oo
rtm:<option_name>=<value>,<option_name>=<va
lue>
Required option names include:
- disName. Name of the Data Integration Service.
- codePage. Code page of the reference data.
- refDataFile. Path and file name of the zip file where you want
to export the reference table data.
For example:
rtm:disName=ds,codePage=UTF-8,refDataFile=/
folder1/data.zip
exportResources
Exports the scorecard objects and lineage information in a project or folder to an XML file that you use in
Metadata Manager.
If you do not want to export all objects in the project, use an infacmd export control file to filter the objects
that you want to export. The command does not export empty folders.
increase system memory, set the -Xmx value in the ICMD_JAVA_OPTS environment variable.
exportResources
637
The infacmd oie exportResources command uses the following syntax:

exportResources
<-RepositoryService|-rs> model_repository_service_name
<-ExportFilePath|-fp> export_file_path
[<-OverwriteExportFile|-ow> overwrite_export_file]
[<-ControlFilePath|-cp> control_file_path]
The following table describes infacmd oie exportResources options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

638
Option
Argument
Description
-ProjectName
project_name
Required. Name of the project from which you export the

objects.
model_repository_se
rvice_name
-rs
-ExportFilePath
export_file_path
Required. Path and XML file name of the export file the
command line program creates when you run the command.
You can specify an absolute path or a relative path to the file
name. Use an easily distinguishable name for the file. For
example, use the following suggested naming convention:
-pn
-RepositoryService
-fp
exp_<project_name>.xml
-OverwriteExportFile
overwrite_export_file
Optional. Set to true to overwrite an existing export file. If an

export file exists and you set this option to false, the export
fails. Default is false.
control_file_path
Optional. Path and file name of the export control file that
filters the objects that the command line program exports.
You can specify an absolute path or a relative path to the file
name.
-ow
-ControlFilePath
-cp
ImportObjects
Imports objects from an XML file into an existing project in the Model repository.
If you do not want to import all objects in the file, use an infacmd import control file to filter the Model
repository objects that you want to import.
If the file being imported contains reference tables, you must run the command from the Informatica services
installation directory. The command imports the reference table metadata from the XML file into the Model
repository. The command imports the reference table data from a zip file. When you run the command,
specify the path and file name of both the XML and zip files to be imported.
The infacmd oie ImportObjects command uses the following syntax:
ImportObjects
[<-SecurityDomain|-sdn> Security domain]
[<-TargetProject|-tp> Target project name <ignored if control file is specified>]
<-ImportFilePath|-fp> import_file_path
ImportObjects
639
[<-SourceProject|-sp> Source project name in import file <ignored if control file is

specified>]
[<-TargetFolder|-tf> Target folder to import to <omit for root, ignored if control file
is specified>]
[<-SkipCRC|-sc> Set to "true" to skip CRC check on imported file.]
[<-ConflictResolution|-cr> Resolution type]
[<-ControlFilePath|-cp> Path of import control file]
[<-SkipCnxValidation|-scv> Set to "true" to skip connection validation.]
[<-OtherOptions|-oo>]
The following table describes infacmd oie ImportObjects options and arguments:
Option
Argument
Description
-DomainName
Domain name

User name

domain. You can set the user name with the
-un option or the environment variable
-dn
-UserName
-un

-Password
Password
-pd
640

variable
precedence.
Option
Argument
Description
-SecurityDomain
Security domain

-sdn

-TargetProject
Target Project name <ignored

if control file is specified>
Optional. Name of the project into which you

want to import the objects. The project must
exist in the repository before you import the
objects. The option is ignored if you use an
import control file.

name
- rs
-ImportFilePath
import_file_path
Required. Path and file name of the XML file

to import the objects from. You can specify
an absolute path or a relative path to the file
name.
Source project name in import

file <ignored if control file is
specified>
Optional. Source project name in the file to

import. The option is ignored if you use an
import control file.
Target folder to import to <omit

for root, ignored if control file is
specified>
Optional. Target folder into which you want

to import the objects. If you do not specify a
target folder, the objects are imported into
the target project. The folder must exist in
the repository before you import the objects.
The option is ignored if you use an import
control file.
Set to "true" to skip CRC check

on imported file.
Indicates whether to skip the cyclic

redundancy check (CRC) that detects
whether the file to import was modified. Set
to true to skip the check. Default is false.
-tp
-RepositoryService
-fp
-SourceProject
-sp
-TargetFolder
-tf
-SkipCRC
-sc
ImportObjects
641
Option
Argument
Description
-ConflictResolution
Resolution type specified
Optional. Conflict resolution strategy. You

can specify one of the following options for
all objects being imported:
-cr
rename
replace
reuse
none
The option is ignored if you use an import

control file. If the conflict resolution strategy
is set to none and a conflict occurs, the
import fails. Default is none.
-ControlFilePath
Path of import control file
-cp
642
Optional. Path and file name of the import

control file that filters the objects that are
imported. You can specify an absolute path
or a relative path.
Option
Argument
Description
-SkipCnxValidation
Set to "true" to skip connection

validation.
Optional. Indicates whether to skip target

connection validation during the import. By
default, the import process verifies that
connections used by the imported objects
exist in the target repository. If the
connections do not exist, the import fails.
-scv
To skip target connection validation and

continue with the import, set this option to
true. If the imported objects use connections
that do not exist in the target repository, the
import process imports the objects with an
"Unspecified" connection. Use the Developer
tool to select the correct connection after the
import process has completed.
Default is false.
Note: If an import control file specifies a
source connection that does not exist in the
file that you are importing, the import
process fails regardless of the value for this
option. To correct the error, verify that the
connection rebind element in the import
control file includes source connections that
exist in the file that you are importing.
-OtherOptions
-oo
Required if the import file contains reference

tables. Additional options to import reference
table data from a zip file. Enter options using
rtm:<option_name>=<value>,<opti
on_name>=<value>
Required option names include:
- disName. Name of the Data Integration
Service.
- codePage. Code page of the reference data.
- refDataFile. Path and file name of the zip file
from where you want to import the reference
table data.
For example:
rtm:disName=ds,codePage=UTF-8,r
efDataFile=/folder1/data.zip
ImportObjects
643
CHAPTER 17
infacmd ps Command Reference

cancelProfileExecution, 644
CreateWH, 646
DropWH, 647
Execute, 649
executeProfile, 651
getExecutionStatus, 652
getProfileExecutionStatus, 654
List, 656
migrateProfileResults, 657
migrateScorecards, 659
Purge, 660
synchronizeProfile, 663
cancelProfileExecution
Stops all the profile runs including profiles and enterprise discovery profile.
The infacmd ps cancelProfileExecution command uses the following syntax:
[<-Gateway|-hp> gateway_name]
<-MrsServiceName|-msn> MRS_name
<-DsServiceName|-dsn> data_integration_service_name
<-ObjectPathAndName|-opn> MRS_object_path
644
The following table describes infacmd ps cancelProfileExecution options and arguments:

Option
Argument
Description
-DomainName
domain_name

gateway_host1:p
ort

-dn
-Gateway
-hp
gateway_host2:p
ort...
-NodeName
node_name
Optional. Name of the node where the Data Integration

Service runs.
user_name

takes precedence.
-nn
-UserName
-un

-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-MrsServiceName
MRS_name
-msn
645
Option
Argument
Description
-DsServiceName
data_integration_
service_name
Required. Data Integration Service name.
-dsn
-ObjectPathAndName
MRS_object_path

SubFolder_Name/{ObjectName|ProjectName/
ObjectName}
-opn
CreateWH
Creates the content of the profiling warehouse.
The infacmd ps CreateWH command uses the following syntax:
CreateWH
[<-Gateway|-hp>] gateway_name]
The following table describes infacmd ps CreateWH options and arguments:
Option
Argument
Description
-DomainName
domain_name

gateway_name
Optional. Use this option if the gateway connectivity

information in the domains.infa file is out of date. Enter the
host name and port number for the gateway node in the
domain. Use the following syntax: gateway_hostname:port.
user_name

-dn
-Gateway
-hp
-UserName
-un

sign-on.
646
Chapter 17: infacmd ps Command Reference
Option
Argument
Description
-Password
Password
security_domain

-pd
-SecurityDomain
-sdn

-DsServiceName
-dsn
data_integration_servi
ce_name
DropWH
Removes the content of the profiling warehouse.
The infacmd ps DropWH command uses the following syntax:
DropWH
[<-Gateway|-hp>] gateway_name]
DropWH
647
The following table describes infacmd ps DropWH options and arguments:

Option
Argument
Description
-DomainName
domain_name

gateway_name
Optional. Use this option if the gateway connectivity

information in the domains.infa file is out of date. Enter the
host name and port number for the gateway node in the
domain. Use the following syntax: gateway_hostname:port.
user_name

-dn
-Gateway
-hp
-UserName
-un

sign-on.
-Password
Password
security_domain

-pd
-SecurityDomain
-sdn

-DsServiceName
-dsn
data_integration_ser
vice_name
648
Execute
Runs a profile or scorecard.
The infacmd ps Execute command uses the following syntax:
Execute
<-ObjectType|-ot> object_type
[<-ProfileTaskName|-pt> profile_task_name]
[<-wait|-w> true|false]
The following table describes infacmd ps Execute options and arguments:
Option
Argument
Description
-DomainName
domain_name

gateway_host1:p
ort

-dn
-Gateway
-hp
gateway_host2:p
ort...
-NodeName
node_name

Service runs.
user_name

takes precedence.
-nn
-UserName
-un

Execute
649
Option
Argument
Description
-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-MrsServiceName
MRS_name
data_inetgration_
service_name
-dsn
-ObjectType
object_type
Required. Enter profile or scorecard.
-msn
-DsServiceName
-ot
-ObjectPathandName
MRS_object_path
-opn
-ProfileTaskName
-pt
profile_task_nam
e
Optional. Name of a profile task in the enterprise

discovery profile.
-Wait
true|false
Optional. If true, waits until the command completes

before returning the command prompt. If false, returns the
command prompt before the command completes. Default
is false.
-w
650

ObjectName}
executeProfile
Runs an enterprise discovery profile.
The infacmd ps executeProfile command uses the following syntax:
executeProfile
The following table describes infacmd ps executeProfile options and arguments:
Option
Argument
Description
-DomainName
domain_name

gateway_host1:p
ort

-dn
-Gateway
-hp
gateway_host2:p
ort...
-NodeName
node_name

Service runs.
user_name

takes precedence.
-nn
-UserName
-un

-Password
-pd
password

executeProfile
651
Option
Argument
Description
-SecurityDomain
security_domain

sensitive.
-sdn

installation.
-MrsServiceName
MRS_name
data_inetgration_
service_name
-dsn
-ObjectPathandName
MRS_object_path
-msn
-DsServiceName
-opn

ObjectName}
getExecutionStatus
Gets the run-time status of profile tasks in an enterprise discovery profile.
The infacmd ps getExecutionStatus command uses the following syntax:
getExecutionStatus
<-ProfileTaskName|-pt> profile_task_name
652
The following table describes infacmd ps getExecutionStatus options and arguments:

Option
Argument
Description
-DomainName
domain_name

gateway_host1:p
ort

-dn
-Gateway
-hp
gateway_host2:p
ort...
-NodeName
node_name

Service runs.
user_name

takes precedence.
-nn
-UserName
-un

-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-MrsServiceName
MRS_name
data_integration_
service_name
-msn
-DsServiceName
-dsn
getExecutionStatus
653
Option
Argument
Description
-ObjectType
object_type
MRS_object_path

ObjectName}
profile_task_nam
e
Optional. Name of a profile task in the enterprise

discovery profile.
-ot
-ObjectPathAndName
-opn
-ProfileTaskName
-pt
getProfileExecutionStatus
Gets the run-time status of an enterprise discovery profile. The command also lists all the profile tasks in the
enterprise discovery profile and their run-time statuses.
The infacmd ps getProfileExecutionStatus command uses the following syntax:
The following table describes infacmd ps getProfileExecutionStatus options and arguments:
Option
Argument
Description
-DomainName
domain_name

gateway_host1:p
ort

-dn
-Gateway
-hp
gateway_host2:p
ort...
654
Option
Argument
Description
-NodeName
node_name

Service runs.
user_name

takes precedence.
-nn
-UserName
-un

-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-MrsServiceName
MRS_name
data_integration_
service_name
-dsn
-ObjectPathAndName
MRS_object_path

ObjectName}
-msn
-DsServiceName
-opn
655
List
Lists profiles or scorecards.
The infacmd ps List command uses the following syntax:
List
[<-NodeName|-nn>] node_name
<-ObjectType|-ot>
[<-Recursive|-r>]
The following table describes infacmd ps List options and arguments:
Option
Argument
Description
-DomainName
domain_name

node_name

Service runs.
MRS_name
user_name

-dn
-NodeName
-nn
-MrsServiceName
-msn
-UserName
-un

sign-on.
-Password
password
-pd
656
Option
Argument
Description
-SecurityDomain
security_domai
n

-sdn

-ObjectType
full_folder_path
Required. Enter the path of the folder that contains the

objects you want to list.
-ot
-FolderPath
-fp

Project_name/folder_name/../SubFolderName
-Recursive
-r
Optional. Applies the command to objects in the folder that

you specify and its subfolders.
migrateProfileResults
Migrates column profile results and data domain discovery results from version 9.1.0, 9.5.0, or 9.5.1.
The infacmd ps migrateProfileResults command uses the following syntax:
657
The following table describes infacmd ps migrateProfileResults options and arguments:

Option
Argument
Description
-DomainName
domain_name

gateway_host1:p
ort

-dn
-Gateway
-hp
gateway_host2:p
ort...
-NodeName
node_name

Service runs.
user_name

takes precedence.
-nn
-UserName
-un

-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-MrsServiceName
MRS_name
data_integration_
service_name
-msn
-DsServiceName
-dsn
658
migrateScorecards
Migrates scorecard results from Informatica 9.1.0 or 9.5.0 to 9.5.1.
The infacmd ps migrateScorecards command uses the following syntax:
migrateScorecards
<-migrateFrom|-mfr> migrate_from_release
The following table describes infacmd ps migrateScorecards options and arguments:
Option
Argument
Description
-DomainName
domain_name

gateway_host1:p
ort

-dn
-Gateway
-hp
gateway_host2:p
ort...
-NodeName
node_name

Service runs.
user_name

takes precedence.
-nn
-UserName
-un

-Password
-pd
password

migrateScorecards
659
Option
Argument
Description
-SecurityDomain
security_domain

sensitive.
-sdn

installation.
-MrsServiceName
MRS_name
data_integration_
service_name
migrate_from_rel
ease
Required. Version of Data Explorer migrating from. The

version can be either 9.1.0 or 9.5.0.
-msn
-DsServiceName
-dsn
-migrateFrom
-mfr
Purge
Purges profile and scorecard results from the profiling warehouse.
The infacmd ps Purge command uses the following syntax:
Purge
[<-NodeName|-nn>] node_name
[<-RetainDays|-rd> results_retain_days]
[<-ProjectFolderPath|-pf> project_folder_path]
660
[<-ProfileTaskName|-pt> profile_task_name]
[<-Recursive|-r> recursive]
[<-PurgeAllResults|-pa> purge_all_results]
The following table describes infacmd ps Purge options and arguments:
Option
Argument
Description
-DomainName
domain_name
Required. The name of the Informatica domain.
-dn
-Gateway
-hp
You can set the domain name with the -dn option or the
environment variable INFA_DEFAULT_DOMAIN. If you set a
domain name with both methods, the -dn option takes
precedence.
gateway_nam
e
Optional if you run the command from the Informatica

installation \bin directory. Required if you run the command
from another location.
The gateway node name.
[Domain_Host]:[HTTP_Port]
-NodeName
node_name
Required. The name of the node where the Data Integration

Service runs.
user_name

-nn
-UserName
-un

sign-on.
-Password
Password
security_doma
in

-pd
-SecurityDomain
-sdn

Purge
661
Option
Argument
Description
-MrsServiceName
MRS_name
Required. The Model Repository Service name.
data_integrati
on_service_na
me
Required. The Data Integration Service name
-dsn
-ObjectType
MRS_object_p
ath
Optional. Do not use with ProjectFolderPath or Recursive.

The path to the profile or scorecard in the Model repository.
-msn
-DsServiceName
-ot
-ObjectPathAndName
-opn *

ProjectName/FolderName/.../{SubFolder_Name/
ObjectName|ProjectName/ObjectName}
-RetainDays
-rd
-ProjectFolderPath
-pf *
results_retain
_days
Optional. The number of days that the profiling warehouse

stores profile or scorecard results before it purges the
results.
project_folder
_path
Optional. Do not use with ObjectPathAndName or

ProfileTaskName.
The names of the project and folder where the profile or
scorecard is stored.
ProjectName/FolderName
-ProfileTaskName
-pt *
profile_task_n
ame
-Recursive
recursive
-r
-PurgeAllResults
-pa
Optional. The name of the profile task that you want to

purge. If you specified the ProjectFolderPath, you do not
need to specify this option because the ProjectFolderPath
includes the name of the enterprise discovery profile that
contains the profile task.
Optional. Do not use with ObjectPathAndName.
Applies the command to objects in the folder that you specify
and its subfolders.
purge_all_res
ults
Optional. Set this option to purge all results for the profile or
scorecard object.
Use with the -recursive option to apply the command to
profile and scorecard results in the folder that you specify
and its subfolders.
* To run the command, you need to specify ObjectPathAndName or ProjectFolderPath or ProfileTaskName.
662
synchronizeProfile
Migrates documented, user-defined, and committed primary keys and foreign keys for all the profiles in a
project from version 9.1.0, 9.5.0, or 9.5.1.
The infacmd ps synchronizeProfile command uses the following syntax:
synchronizeProfile
The following table describes infacmd ps synchronizeProfile options and arguments:
Option
Argument
Description
-DomainName
domain_name

gateway_host1:p
ort

-dn
-Gateway
-hp
gateway_host2:p
ort...
-NodeName
node_name

Service runs.
user_name

takes precedence.
-nn
-UserName
-un

-Password
-pd
password

synchronizeProfile
663
Option
Argument
Description
-SecurityDomain
security_domain

sensitive.
-sdn

installation.
-MrsServiceName
MRS_name
data_integration_
service_name
-dsn
-ProjectName
project_name
Required. Project name.
-msn
-DsServiceName
-pn
664
CHAPTER 18
infacmd pwx Command

Reference
CloseForceListener, 666
CloseListener, 668
CondenseLogger, 671
createdatamaps, 673
CreateListenerService, 676
CreateLoggerService, 678
DisplayAllLogger, 683
DisplayCPULogger, 685
DisplayEventsLogger, 688
DisplayMemoryLogger, 690
DisplayRecordsLogger, 692
displayStatsListener, 695
DisplayStatusLogger, 698
FileSwitchLogger, 701
ListTaskListener, 703
ShutDownLogger, 705
StopTaskListener, 708
UpgradeModels, 710
665
UpdateListenerService, 712
UpdateLoggerService, 715
CloseForceListener
Forces the cancellation of long-running subtasks on the PowerExchange Listener Service and stops the
Listener Service.
When you issue the infacmd pwx CloseForceListener command, PowerExchange completes the following
actions:
1.
Checks if any subtasks on the Listener Service are active.
2.
If active subtasks exist, polls the number of active subtasks every second until 30 seconds have
elapsed.
3.
During this period, stops any subtask that is waiting for TCP/IP network input.
4.
Cancels any remaining active subtasks.
5.
Stops the Listener Service.
The infacmd pwx CloseForceListener command uses the following syntax:

CloseForceListener
[<-OSUser|-oun> OS_user_name]
[<-OSPassword|-oup> OS_password]
[<-OSEPassword|-ouep> OS_epassword]
666
Chapter 18: infacmd pwx Command Reference
The following table describes infacmd pwx CloseForceListener options and arguments:
Option
Argument
Description
-DomainName
domain_name
Name of the Informatica domain. You can set the domain

name with the -dn option or the environment variable
user_name

takes precedence.
-dn
-UserName
-un

-Password
password

service_name
Required. Name of the Listener Service.

takes precedence.
security_domain

sensitive.
-pd
-ServiceName
-sn
-ResilienceTimeout
-re
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port

CloseForceListener
667
Option
Argument
Description
-OSUser
OS_user_name
Required if you enable operating system security. User

name for the operating system.
-oun
Enable operating system security as follows:

- To require users to enter a valid operating system user ID
and password on the command, specify 1 or 2 for the first
parameter of the SECURITY statement in the DBMOVER
configuration file on each Linux, UNIX, or Windows system
that is the target of the command. PowerExchange uses
operating system facilities on the target system to
authenticate the user ID and password for use of the
infacmd pwx program.
- To authorize users to run specific infacmd pwx commands,
specify 2 for the first parameter of the SECURITY
statement and define AUTHGROUP and USER statements
in the PowerExchange sign-on file on each Linux, UNIX, or
Windows system that is the target of the command.
PowerExchange checks the sign-on file to determine
whether to allow the user ID supplied on the infacmd pwx
program to run commands.
For more information, see the PowerExchange Reference

Manual.
-OSPassword
OS_password
-oup
Required if you specify a user name and do not specify an

encrypted password. Password for the operating system.
You can set a plain text password with the -p option or the
INFA_DEFAULT_PWX_OSPASSWORD. If you set a
password with both methods, the password set with the -p
-OSEPassword
OS_epassword
-ouep
Required if you specify a user name and do not specify a

plain text password. Encrypted password for the operating
system.
You can set an encrypted password with the -e option or
INFA_DEFAULT_PWX_OSEPASSWORD. If you set a
password with both methods, the password set with the -e
CloseListener
Stops the PowerExchange Listener Service after waiting for all outstanding subtasks on the Listener Service
to complete.
Note: If you have long-running subtasks on the Listener Service, issue the infacmd pwx closeforceListener
command instead to force the cancellation of all user subtasks and stop the Listener Service.
The infacmd pwx CloseListener command uses the following syntax:
CloseListener
668
The following table describes infacmd pwx CloseListener options and arguments:
Option
Argument
Description
-DomainName
domain_name

INFA_DEFAULT_DOMAIN. If you set a domain name
with both methods, the -dn option takes precedence.
user_name

takes precedence.
-dn
-UserName
-un

-Password
password

service_name

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
CloseListener
669
Option
Argument
Description
-SecurityDomain
security_domain

sensitive.
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-OSUser
OS_user_name

-oun

configuration file on each Linux, UNIX, or Windows
system that is the target of the command.
PowerExchange uses operating system facilities on the
target system to authenticate the user ID and password
for use of the infacmd pwx program.
- To authorize users to run specific infacmd pwx
commands, specify 2 for the first parameter of the
SECURITY statement and define AUTHGROUP and
USER statements in the PowerExchange sign-on file on
each Linux, UNIX, or Windows system that is the target of
the command. PowerExchange checks the sign-on file to
determine whether to allow the user ID supplied on the
infacmd pwx program to run commands.
-OSPassword
OS_password
-oup
Required if you specify a user name and do not specify

an encrypted password. Password for the operating
system.
You can set a plain text password with the -p option or
password with both methods, the password set with the p option takes precedence.
-OSEPassword
OS_epassword
-ouep

plain text password. Encrypted password for the
operating system.
password with both methods, the password set with the e option takes precedence.
670
CondenseLogger
Starts another logging cycle before the wait period for starting another cycle has elapsed when the
PowerExchange Logger Service is running in continuous mode. Specify the wait period in the
NO_DATA_WAIT parameter of the pwxccl.cfg configuration file.
The infacmd pwx CondenseLogger command uses the following syntax:
CondenseLogger
The following table describes infacmd pwx CondenseLogger options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

-Password
password

service_name
Required. Name of the Logger Service.
-pd
-ServiceName
-sn
CondenseLogger
671
Option
Argument
Description
-ResilienceTimeout

takes precedence.
security_domain

sensitive.
-re
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-OSUser
OS_user_name

-oun

672
Option
Argument
Description
-OSPassword
OS_password

-oup
-OSEPassword
OS_epassword
-ouep

system.
createdatamaps
Creates data maps for bulk data movement operations.
Use the createdatamaps command to generate data maps for IMS, SEQ, and VSAM data sources from the
command line. This command provides an alternative to using the PowerExchange Navigator in certain cases
and allows you to generate or regenerate data maps noninteractively.
increase the system memory, set the -Xmx value in the ICMD_JAVA_OPTS environment variable. For more
information, see ICMD_JAVA_OPTS on page 40.
The infacmd pwx createdatamaps command uses the following syntax:
createdatamaps
[<-pwxLocation|-loc> pwx_location]
[<-pwxUserName|-pun> pwx_user_name]
[<-pwxPassword|-ppd> pwx_password]
[<-pwxEncryptedPassword|-epwd> pwx_encrypted_password]
[<-datamapOutputDir|-dod> datamap_output_directory]
[<-replace|-r> replace_existing_datamaps
<-controlFile|-cf> file_path_for_control_file
[<-logFile|-lf> file_path_for_log_file]
[<-verbosity|-v> logging_verbosity]
createdatamaps
673
The following table describes infacmd pwx createdatamaps options and arguments:
Option
Argument
Description
-pwxLocation
pwx_location
Optional. The location of the data source as specified

in a NODE statement in the PowerExchange dbmover
configuration file. If pwxLocation is not specified, the
createdatamaps utility accesses the copybook and
DBD metadata on the local file system.
-loc
If you configure the control file to find record IDs,

pwxLocation is required.
-pwxUserName
pwx_user_name
Optional. The user ID for connecting to the

PowerExchange Listener, if pwxLocation is specified.
pwx_password
Optional. Password for connecting to the

-pun
-pwxPassword
-ppd
Instead of a password, you can enter a valid

PowerExchange passphrase. Passphrases for
accessing a PowerExchange Listener on z/OS can be
from 9 to 128 characters in length and can contain the
- Spaces
- ; # \ , . / ! % & * ( ) _ +
{ } : @ | < > ?
Passphrases cannot include single quotation marks (),

double quotation marks (), or currency symbols.
If a passphrase contains spaces, you must enclose it
with double-quotation marks ("), for example, "This
is an example passphrase". If a passphrase
contains special characters, you must enclose it with
triple double-quotation characters ("""), for example,
"""This passphrase contains special
characters ! % & *.""". If a passphrase
contains only alphanumeric characters without spaces,
you can enter it without delimiters.
Note: On z/OS, a valid RACF passphrase can be up to
100 characters in length. PowerExchange truncates
passphrases longer than 100 characters when passing
them to RACF for validation.
To use passphrases, ensure that the PowerExchange
Listener runs with a security setting of
SECURITY=(1,N) or higher in the DBMOVER member.
For more information, see "SECURITY Statement" in
the PowerExchange Reference Manual.
674
Option
Argument
Description
-pwxEncryptedPassword
pwx_encrypted_password
Optional. Encrypted password for connecting to the

-epwd
If the PowerExchange Listener runs on a z/OS or

i5/OS system, you can enter an encrypted
PowerExchange passphrase instead of an encrypted
password. Do not encrypt a passphrase that contains
characters that are not valid, such as double-quotation
marks, single quotation marks, or currency symbols.
-datamapOutputDir
datamap_output_directory
Optional. The local file directory to which to write the

output data maps. Default is the current working
directory.
replace_existing_datamaps
Optional. Specifies whether to replace existing data

maps.
-dod
-replace
-r
If replace=Y, replaces any data maps in

datamap_output_directory that have the same name
as the data map that you are creating.
If replace=N, skips the creation of a data map if a data
map with the same name already exists in
datamap_output_directory.
Default is N.
-controlFile
file_path_for_control_file
Required. Path and file name of the control file that

controls data map generation.
file_path_for_log_file
Optional. Path and file name of the output log file.

Default is STDOUT.
logging_verbosity
Optional. Verbosity for log files. Default is INFO. Valid

values:
-cf
-logFile
-lf
-verbosity
-v
- DEBUG. Most detailed logging. Might show stack

traces.
- INFO. Informational messages.
- WARN. Indicates a potential problem.
- ERROR. Indicates a failure. Processing continues.
- FATAL. Indicates a fatal condition. Process terminates.
The PowerExchange node name and credentials are optional. If you do not include the pwxLocation option,
the command accesses the local file system directly to read metadata. In this case, PowerExchange does not
need to be installed on the machine on which you run createdatamaps.
For more information about the createdatamaps command, see the PowerExchange Utilities Guide.
createdatamaps
675
CreateListenerService
Creates a PowerExchange Listener Service in a domain. By default, the Listener Service is disabled when
you create it. Run the infacmd isp EnableService command to enable the service.
The infacmd pwx CreateListenerService command uses the following syntax:
[<-BackupNode|-bn> backup_node]
<-StartParameters|-sp> start_parameters
<-SvcPort|-sp> service_port
The following table describes infacmd pwx CreateListenerService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password
-pd
676

Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
-hp
gateway_host1:port
Required if -DomainName is not specified. The host names

and port numbers for the gateway nodes in the domain.
ResilienceTimeout

takes precedence.
service_name
-re
-ServiceName
-sn
The name is not case sensitive. The name cannot exceed

128 characters or contain carriage returns, tabs, spaces, or
/ * ? < > " |
-NodeName
node_name
Required. Name of the node where you want the Listener

Service to run.
license_name
Optional. License to assign to the service. If you do not

select a license now, you can assign a license to the service
later. Required before you can enable the service.
backup_node
Optional. If the PowerCenter environment is configured for

high availability, this option specifies the name of the
backup node.
-nn
-LicenseName
-ln
-BackupNode
-bn
677
Option
Argument
Description
-StartParameters
start_parameters
Parameters to include when you start the Listener Service.

Separate the parameters with the space character.
-sp
The node_name parameter is required.

You can include the following parameters:
- node_name
Required. Node name that identifies the Listener Service.
This name must match the name in the LISTENER statement
in the DBMOVER configuration file.
- config=directory
Optional. Specifies the full path and file name for any
dbmover.cfg configuration file that you want to use instead of
the default dbmover.cfg file. This alternative configuration file
takes precedence over any alternative configuration file that
you specify in the PWX_CONFIG environment variable.
- license=directory/license_key_file
Optional. Specifies the full path and file name for any license
key file that you want to use instead of the default license.key
file. The alternative license key file must have a file name or
path that is different from that of the default file. This
alternative license key file takes precedence over any
alternative license key file that you specify in the
PWX_LICENSE environment variable.
Note: In the config and license parameters, you must

provide the full path only if the file does not reside in the
installation directory. Include quotes around any path and
file name that contains spaces.
-SvcPort
service_port
-sp
Required. Port on which the Listener Service listens for

commands from the Service Manager.
CreateLoggerService
Creates a PowerExchange Logger Service in a domain. By default, the Logger Service is disabled when you
create it. Run the infacmd isp EnableService command to enable the service.
The infacmd pwx CreateLoggerService command uses the following syntax:
CreateLoggerService
678
[<-StartParameters|-sp> start_parameters>]
<-SvcPort|-sp> service_port
The following table describes infacmd pwx CreateLoggerService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

the command with single sign-on, do not set the user
single sign-on.
-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port
Optional. If -DomainName is not specified. The host names

and port numbers for the gateway nodes in the domain.
-ResilienceTimeout

takes precedence.
-re
CreateLoggerService
679
Option
Argument
-ServiceName
service_name
-sn
Description
The name is not case sensitive. The name cannot exceed
128 characters or contain carriage returns, tabs, spaces, or
/ * ? < > " |
-NodeName
node_name
Required. Name of the node where you want the Logger

Service to run.
license_name
Optional. License to assign to the service. If you do not

select a license now, you can assign a license to the
service later. Required before you can enable the service.
backup_node

backup node.
-nn
-LicenseName
-ln
-BackupNode
-bn
680
Option
Argument
Description
-StartParameters
start_parameters
Optional. Parameters to include when you start the Logger

Service. Separate the parameters with the space character.
-sp

- coldstart={Y|N}
Indicates whether to cold start or warm start the Logger
Service. Enter Y to cold start the Logger Service. If the
CDCT file contains log records, the Logger Service deletes
these records. Enter N to warm start the Logger Service
from the restart point that is indicated in the CDCT file.
Default is N.
- config=directory/pwx_config_file
Specifies the full path and file name for any dbmover.cfg
configuration file that you want to use instead of the default
dbmover.cfg file. This alternative configuration file takes
precedence over any alternative configuration file that you
specify in the PWX_CONFIG environment variable.
- cs=directory/pwxlogger_config_file
Specifies the path and file name for the Logger Service
configuration file. You can also use the cs parameter to
specify a Logger Service configuration file that overrides the
default pwxccl.cfg file. The override file must have a path or
file name that is different from that of the default file.
- encryptepwd=encrypted_password
A password in encrypted format for enabling the encryption
of PowerExchange Logger log files. With this password, the
PowerExchange Logger can generate a unique encryption
key for each Logger log file. The password is stored in the
CDCT file in encrypted format. For security purposes, the
password is not stored in CDCT backup files and is not
displayed in the CDCT reports that you can generate with
the PowerExchange PWXUCDCT utility.
If you specify this parameter, you must also specify
coldstart=Y.
If you specify this parameter and also specify the
ENCRYPTEPWD parameter in the PowerExchange Logger
configuration file, pwxccl.cfg, the parameter in the
configuration file takes precedence. If you specify this
parameter and also specify the ENCRYPTPWD parameter in
the PowerExchange Logger configuration file, an error
occurs.
You can set the AES algorithm to use for log file encryption
in the ENCRYPTOPT parameter of the pwxccl.cfg file. The
default is AES128.
Tip: For optimal security, Informatica recommends that you
specify the encryption password when cold starting the
PowerExchange Logger rather than in the pwxccl.cfg
configuration file. This practice can reduce the risk of
malicious access to the encryption password for the
following reasons: 1) The encryption password is not stored
in the pwxccl.cfg file, and 2) You can remove the password
from the command line after a successful cold start. If you
specify the encryption password for a cold start and then
need to restore the CDCT file later, you must enter the same
CreateLoggerService
681
Option
Argument
Description
encryption password in the RESTORE_CDCT command of
the PWXUCDCT utility.
To not encrypt PowerExchange Logger log files, do not
enter an encryption password.
Specifies the full path and file name for any license key file
that you want to use instead of the default license.key file.
The alternative license key file must have a file name or
- specialstart={Y|N}
Indicates whether to perform a special start of the
PowerExchange Logger. A special start begins
PowerExchange capture processing from the point in the
change stream that you specify in the pwxccl.cfg file. This
start point overrides the restart point from the CDCT file for
the PowerExchange Logger run. A special start does not
delete any content from the CDCT file.
Use this parameter to skip beyond problematic parts in the
source logs without losing captured data. For example, use
a special start in the following situations:
- You do not want the PowerExchange Logger to capture
an upgrade of an Oracle catalog. In this case, stop the
PowerExchange Logger before the upgrade. After the
upgrade is complete, generate new sequence and restart
tokens for the PowerExchange Logger based on the postupgrade SCN. Enter these token values in the
SEQUENCE_TOKEN and RESTART_TOKEN parameters
in the pwxccl.cfg, and then special start the
PowerExchange Logger.
- You do not want the PowerExchange Logger to reprocess
old, unavailable logs that were caused by outstanding
UOWs that are not of CDC interest. In this case, stop the
PowerExchange Logger. Edit the RESTART_TOKEN
value to reflect the SCN of the earliest available log, and
then perform a special start. If any of the outstanding
UOWs that started before this restart point are of CDC
interest, data might be lost.
Valid values:
- Y. Perform a special start of the PowerExchange Logger
from the point in the change stream that is defined by the
SEQUENCE_TOKEN and RESTART_TOKEN parameter
values in the pwxccl.cfg configuration file. You must
specify valid token values in the pwxccl.cfg file to perform
a special start. These token values override the token
values from the CDCT file. Ensure that the
SEQUENCE_TOKEN value in the pwxccl.cfg is greater
than or equal to the current sequence token from the
CDCT file.
Do not also specify the coldstart=Y parameter. If you do,
the coldstart=Y parameter takes precedence.
- N. Do not perform a special start. Perform a cold start or
warm start as indicated by the coldstart parameter.
Default is N.
682
Option
Argument
Description
Note: In the config, cs, and license parameters, the full
path is required only if the file does not reside in the
-SvcPort
service_port
-sp
Optional. Port on which the Logger Service listens for

commands from the Service Manager.
DisplayAllLogger
Displays all messages that can be produced by the other PowerExchange Logger Service display commands,
arranged by command.
The infacmd pwx DisplayAllLogger command displays the consolidated output for the following commands:
DisplayCPULogger
DisplayEventsLogger
DisplayMemoryLogger
DisplayRecordsLogger
DisplayStatusLogger
The infacmd pwx DisplayAllLogger command uses the following syntax:

DisplayAllLogger
DisplayAllLogger
683
The following table describes infacmd pwx DisplayAllLogger options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

-Password
password

service_name

takes precedence.
security_domain

sensitive.
-pd
-ServiceName
-sn
-ResilienceTimeout
-re
-SecurityDomain
-sdn

installation.
-Gateway
-hp
684
gateway_host1:port

Option
Argument
Description
-OSUser
OS_user_name

-oun

-OSPassword
OS_password
-oup

-OSEPassword
OS_epassword
-ouep

system.
DisplayCPULogger
Displays the amount of CPU time, in microseconds, that the PowerExchange Logger Service spends for each
phase of processing during the current logging cycle. Also includes the total CPU time for all Logger Service
processing.
For example, the infacmd pwx DisplayCPULogger command might report the amount of CPU time that the
Logger Service spent to complete the following actions:
Read source data
Write data to Logger Service log files
Perform file switches
Perform other processing, such as initialize and process commands
DisplayCPULogger
685
The infacmd pwx DisplayCPULogger command uses the following syntax:

DisplayCPULogger
The following table describes infacmd pwx DisplayCPULogger options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

-Password
password

service_name

takes precedence.
-pd
-ServiceName
-sn
-ResilienceTimeout
-re
686
Option
Argument
Description
-SecurityDomain
security_domain

sensitive.
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-OSUser
OS_user_name

-oun

-OSPassword
OS_password
-oup

-OSEPassword
-ouep
OS_epassword

system.
DisplayCPULogger
687
DisplayEventsLogger
Displays events that the Controller, Command Handler, and Writer tasks for the PowerExchange Logger
Service are waiting on. Also indicates if the Writer is processing data or is in a sleep state waiting for an
event or timeout to occur.
The infacmd pwx DisplayEventsLogger command uses the following syntax:
DisplayEventsLogger
The following table describes infacmd pwx DisplayEventsLogger options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

-Password
password

service_name
-pd
-ServiceName
-sn
688
Option
Argument
Description
-ResilienceTimeout

security_domain

sensitive.
-re
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-OSUser
OS_user_name

-oun

system that is the target of the command. PowerExchange
uses operating system facilities on the target system to
DisplayEventsLogger
689
Option
Argument
Description
-OSPassword
OS_password

system.
-oup

-OSEPassword
OS_epassword
-ouep

operating system.
DisplayMemoryLogger
Displays memory use, in bytes, for each PowerExchange Logger Service task and subtask, with totals for the
entire Logger Service process.
PowerExchange reports memory use for the following categories:
Application. Memory that the Logger Service application requested for its own use.
Total. Total memory in use for the Logger Service application and for related header overhead. This value
fluctuates as PowerExchange allocates and frees memory during Logger Service processing.
Maximum. The largest memory amount that has been recorded for the Total category up to the point in
time when this command runs.
The infacmd pwx DisplayMemoryLogger command uses the following syntax:

DisplayMemoryLogger
690
The following table describes infacmd pwx DisplayMemoryLogger options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

-Password
password

service_name

security_domain

sensitive.
-pd
-ServiceName
-sn
-ResilienceTimeout
-re
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port

DisplayMemoryLogger
691
Option
Argument
Description
-OSUser
OS_user_name

-oun

-OSPassword
OS_password
-oup

system.
-OSEPassword
OS_epassword
-ouep

operating system.
Displays counts of change records that the PowerExchange Logger Service processed during the current
processing cycle. If the Logger Service did not receive changes in the current cycle, displays counts of
change records for the current set of Logger Service log files.
The infacmd pwx DisplayRecordsLogger command displays counts of records for each type of change record
processed and for total records processed. Change record types include Delete, Insert, Update, and Commit.
692
Depending on whether the command displays counts for the current cycle or the current log files, the output
includes all or some of the following types of information:
Cycle. Counts of change records for the current Logger Service processing cycle. The Logger Service
resets these counts to zero when the wait interval that is specified in the NO_DATA_WAIT2 parameter of
the pwxccl.cfg file expires and no change data has been received.
File. Counts of change records for the current set of PowerExchange log files. The Logger Service resets
these counts to zero when a file switch occurs.
Total. Counts of change records that the Logger Service received since it started. PowerExchange does
not reset these counts to zero.
The infacmd pwx DisplayRecordsLogger command uses the following syntax:

The following table describes infacmd pwx DisplayRecordsLogger options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

-Password
-pd
password

693
Option
Argument
Description
-ServiceName
service_name

security_domain

sensitive.
-sn
-ResilienceTimeout
-re
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-OSUser
OS_user_name

-oun

694
Option
Argument
Description
-OSPassword
OS_password

system.
-oup

-OSEPassword
OS_epassword
-ouep

operating system.
displayStatsListener
Displays monitoring statistics for a PowerExchange Listener on Linux, UNIX, or Windows that the
PowerExchange Listener Service manages. Also displays statistics for the client tasks and source or target
connections that are associated with the Listener.
The command can print the following types of statistics, depending on the -type option that you specify:
PowerExchange Listener summary statistics on memory usage, CPU processing time, and activity on
behalf of client requests. These statistics include counts of client tasks, connections, messages sent and
received, and bytes of data sent and received.
Message and data volumes that client tasks sent and received for client requests, by task ID and access
method. The message and data volumes are totals as of the time the statistics are generated.
Information about the active tasks that are running under the Listener to process client requests. These
statistics include the task start time, CPU processing time, access method, read or write mode, and
associated process and session IDs. Also includes the port number and IP address of the client that
issued the request to the PowerExchange Listener.
Important: For PowerExchange to collect PowerExchange Listener monitoring statistics, you must specify the
MONITOR parameter in the STATS statement in the DBMOVER configuration file where the Listener runs.
The infacmd pwx displayStatsListener command uses the following syntax:
695
[<-Gateway|-hp> domain_host1:port domain_host2:port...]
[<-Type|-tp> report_type]
The following table describes infacmd pwx displayStatsListener options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password

service_name

takes precedence.
-pd
-ServiceName
-sn
-ResilienceTimeout
-re
696
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-Gateway
-hp
gateway_host1:port

-OSUser
OS_user_name

-oun

specify 2 for the first parameter of the SECURITY statement
and define AUTHGROUP and USER statements in the
PowerExchange sign-on file on each Linux, UNIX, or
-OSPassword
-oup
OS_password

697
Option
Argument
Description
-OSEPassword
OS_epassword

system.
-ouep

-type
report_type
-tp
Optional. The type of monitoring statistics to report for the

PowerExchange Listener and its client tasks and
connections. The report_type must be one of the following
values:
- listener. For a specific PowerExchange Listener, reports
memory usage, CPU processing time, total number of client
tasks, active tasks, high-watermark tasks, maximum allowed
tasks, total number of connections attempted, connections
accepted, active connections, number of messages sent and
received, and bytes of data sent and received.
- accessmethods. For each access method of each active
task, reports the number of rows read and written, bytes of
data read and written, the source or target file name or data
map file name depending on the access method, and the
CPU processing time.
- clients. For each active task, reports the task ID, status,
access method, read or write mode, process and session
IDs if available, CPU processing time, and start date and
time. Also reports the port number and IP address of the
client that issued the request for which the task was created.
If the client is PowerCenter, reports the PowerCenter
session ID and the application name for CDC.
Default is listener.
Note: In these reports, an access method can be a source
type such as NRDB. A client task might be associated with
multiple access methods: one for reading the source data,
and one for mapping nonrelational data to a relational
format.
DisplayStatusLogger
Displays the status of the Writer subtask for a PowerExchange Logger Service.
For example, the infacmd pwx DisplayStatusLogger command can report when the Writer completes the
following actions:
698
Initializes
Reads or waits for source data
Writes source data to a Logger Service log file
Writes CDCT records during a file switch
Deletes of expired CDCT records
Shuts down
The infacmd pwx DisplayStatusLogger command uses the following syntax:

DisplayStatusLogger
The following table describes infacmd pwx DisplayStatusLogger options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

-Password
password

service_name

takes precedence.
-pd
-ServiceName
-sn
-ResilienceTimeout
-re
DisplayStatusLogger
699
Option
Argument
Description
-SecurityDomain
security_domain

sensitive.
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-OSUser
OS_user_name

-oun

-OSPassword
OS_password
-oup

-OSEPassword
OS_epassword
-ouep

system.
700
FileSwitchLogger
Closes open log files for the PowerExchange Logger Service and then switches to a new set of log files. If
the open log files do not contain any data, the file switch does not occur.
Note: If you use continuous extraction mode, you generally do not need to complete file switches manually.
The infacmd pwx FileSwitchLogger command uses the following syntax:
FileSwitchLogger
The following table describes infacmd pwx FileSwitchLogger options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

-Password
password

service_name
-pd
-ServiceName
-sn
FileSwitchLogger
701
Option
Argument
Description
-ResilienceTimeout

takes precedence.
security_domain

sensitive.
-re
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-OSUser
OS_user_name

-oun

702
Option
Argument
Description
-OSPassword
OS_password

-oup
-OSEPassword
OS_epassword
-ouep

system.
ListTaskListener
Displays information about each active task for the PowerExchange Listener Service, including the TCP/IP
address, port number, application name, access type, and status.
The infacmd pwx ListTaskListener command uses the following syntax:
ListTaskListener
ListTaskListener
703
The following table describes infacmd pwx ListTaskListener options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

-Password
password

service_name

takes precedence.
security_domain

sensitive.
-pd
-ServiceName
-sn
-ResilienceTimeout
-re
-SecurityDomain
-sdn

installation.
-Gateway
-hp
704
gateway_host1:port

Option
Argument
Description
-OSUser
OS_user_name

-oun

-OSPassword
OS_password
-oup

-OSEPassword
OS_epassword
-ouep

system.
ShutDownLogger
Stops the PowerExchange Logger Service in a controlled manner. The command closes the Logger Service
log files and then writes the latest restart position to the CDCT file.
Use this command to stop a PowerExchange Logger Service that is running in continuous mode.
During shutdown processing, the Logger Service completes the following actions:
Closes open log files
Writes updated information to the CDCT file, including restart and sequence tokens
Closes the CAPI
Stops the Writer and Command Handler subtasks
Ends the pwxccl program
ShutDownLogger
705
Reports CPU usage
The infacmd pwx ShutDownLogger command uses the following syntax:

ShutDownLogger
The following table describes infacmd pwx ShutDownLogger options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

-Password
password

service_name

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
706
Option
Argument
Description
-SecurityDomain
security_domain

sensitive.
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-OSUser
OS_user_name

-oun

-OSPassword
OS_password
-oup

system.
-OSEPassword
-ouep
OS_epassword

operating system.
ShutDownLogger
707
StopTaskListener
Stops a PowerExchange Listener Service task based on an application name or task ID that you specify.
During change data extraction, infacmd pwx StopTaskListener waits to stop the task until either the end UOW
is encountered or the commit threshold is reached.
The infacmd pwx StopTaskListener command uses the following syntax:
StopTaskListener
[<-applicationid|-a> appname]
[<-taskid|-t> taskid]
The following table describes infacmd pwx StopTaskListener options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

takes precedence.
-dn
-UserName
-un

-Password
password
-pd
708

Option
Argument
Description
-ServiceName
service_name

takes precedence.
security_domain

sensitive.
-sn
-ResilienceTimeout
-re
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-OSUser
OS_user_name

-oun

StopTaskListener
709
Option
Argument
Description
-OSPassword
OS_password

-oup
-OSEPassword
OS_epassword
-ouep

system.
-applicationid
appname
-a
Required if you do not specify -taskid.

Application name. The name for the active extraction
process that you want to stop. The PWX-00712 message
of the infacmd pwx listtaskListener command output
displays this name.
-taskid
taskid
-t
Required if you do not specify -application.

Task ID of the Listener Service. The numeric identifier for
the Listener Service task that you want to stop.
Tip: To determine the name of the active task, issue the
infacmd pwx listtaskListener command. In the command
output, the name value in the PWX-00712 message
shows the task ID.
UpgradeModels
Upgrades PowerExchange 9.0.1 nonrelational data objects. You must upgrade the data objects before you
can use them.
The command displays the results of the upgrade, sorted by connection name and then schema and map
name. You can run the UpgradeModels command multiple times if some objects are not upgraded the first
time.
The command verifies that the data map is consistent with the nonrelational operations that were defined for
it when the nonrelational object was imported. If discrepancies exist, the nonrelational operations are deleted
and re-created to match the data map. You must modify any affected mappings or mapplets to use the recreated nonrelational operations.
The infacmd pwx UpgradeModels command uses the following syntax:
UpgradeModels
710
<-MrsServiceName|-msn> mrs_service_name
<-DataObjectSchemaName|ds> data_object_schema_name
<-DataObjectName|do> data_object_name
<-Preview|pr> preview
The following table describes infacmd pwx UpgradeModels options and arguments:
Option
Argument
Description
-DomainName
domain_name
Name of the Informatica domain. You can set the domain name
with the -dn option or the environment variable
user_name

-dn
-UserName
-un

-Password
password
-pd
-MrsServiceName
mrs_service_name
-msn
precedence.
The name is not case sensitive and must be unique within the
domain. The characters must be compatible with the code page
of the associated repository. The name cannot exceed 230
characters, have leading or trailing spaces, or contain carriage
returns, tabs, or the following characters:
/ * ? < > " |
-ConnectionName
connection_name
Required. Name of the connection that contains the nonrelational

data objects that you want to upgrade. To specify all connections
or all connections with the same initial name pattern, include the
asterisk (*) wildcard character in double quotes, for example "*"
or ABC"*".
data_object_schema
_name
Required. Name of the schema that contains the data maps of

the nonrelational data objects that you want to upgrade. To
specify all schemas or all schemas with the same initial name
pattern, include the asterisk (*) wildcard character in double
quotes, for example "*" or ABC"*".
-cn
DataObjectSchema
Name
-ds
UpgradeModels
711
Option
Argument
Description
-DataObjectName
data_object_name
Required. Name of the data map of the nonrelational data object

that you want to upgrade. To specify all data maps or all data
maps with the same initial name pattern, include the asterisk (*)
wildcard character in double quotes, for example "*" or ABC"*".
preview
Required. Specify Y to preview the upgrade results without

committing them or N to upgrade the objects. To verify that the
command will run successfully, run the UpgradeModels
command with Preview set to Y before performing the actual
upgrade.
security_domain

sensitive.
-do
-Preview
-pr
-SecurityDomain
-sdn

-ResilienceTimeout
-re
timeout_period_in_s
econds
-ServiceName
service_name
-sn

establish or re-establish a connection to the domain. You can set
the resilience timeout period with the -re option or the
environment variable INFA_CLIENT_RESILIENCE_TIMEOUT. If
you set a the resilience timeout period with both methods, the -re
Optional. Name of the Listener Service.
The command first uses the connection name to retrieve the
specified data maps. If the attempt fails, the command uses the
Listener Service name to retrieve the data maps.
The name is not case sensitive. The name cannot exceed 128
characters or contain carriage returns, tabs, spaces, or the
/ * ? < > " |
UpdateListenerService
Updates the properties of a PowerExchange Listener Service.
The infacmd pwx UpdateListenerService command uses the following syntax:
712
[<-SvcPort|-sp> service_port]
The following table describes infacmd pwx UpdateListenerService options and arguments:
Option
Argument
Description
-DomainName
domain_name
Name of the Informatica domain. You can

set the domain name with the -dn option
user_name

-dn
-UserName
-un

-Password
-pd
password

password is case sensitive. You can set a
password with the -pd option or the
the password set with the -pd option takes
precedence.
713
Option
Argument
Description
-SecurityDomain
security_domain

You can set a security domain with the sdn option or the environment variable
methods, the -sdn option takes
precedence. The security domain name is
case sensitive.
-sdn

default is the LDAP security domain
created during installation. The name of
the security domain is the same as the
user realm specified during installation.
-Gateway
-hp
gateway_host1:port

information in the domains.infa file is out
of date. The host names and port
numbers for the gateway nodes in the
domain.
-ResilienceTimeout

infacmd attempts to establish or reestablish a connection to the domain. You
can set the resilience timeout period with
If you set a the resilience timeout period
precedence.
service_name
license_name
Optional. License to assign to the service.

If not already provided, required before
you can enable the service.
node_name
Required. Name of the node where you

want the Listener Service to run.
backup_node
Optional. If the PowerCenter environment

is configured for high availability, this
option specifies the name of the backup
node.
-re
-ServiceName
-sn
-LicenseName
-ln
-NodeName
-nn
-BackupNode
-bn
714
Option
Argument
Description
-StartParameters
start_parameters
Optional. Parameters to include when you

start the Listener Service. Separate the
parameters with the space character.
-sp

- node_name
Node name that identifies the Listener
Service. This name must match the name
in the LISTENER statement in the
DBMOVER configuration file.
- config=directory
Specifies the full path and file name for
any dbmover.cfg configuration file that
you want to use instead of the default
dbmover.cfg file. This alternative
configuration file takes precedence over
any alternative configuration file that you
specify in the PWX_CONFIG environment
variable.
Specifies the full path and file name for
any license key file that you want to use
instead of the default license.key file. The
alternative license key file must have a
file name or path that is different from that
of the default file. This alternative license
key file takes precedence over any
alternative license key file that you
specify in the PWX_LICENSE
Note: In the config and license

parameters, you must provide the full path
only if the file does not reside in the
installation directory. Include quotes
around any path and file name that
contains spaces.
-SvcPort
service_port
-sp
Optional. Port on which the Listener

Service listens for commands from the
Service Manager.
UpdateLoggerService
Updates the properties of a PowerExchange Logger Service.
The infacmd pwx UpdateLoggerService command uses the following syntax:
UpdateLoggerService
UpdateLoggerService
715
[<-SvcPort|-sp> service_port]
The following table describes infacmd pwx UpdateLoggerService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

the command with single sign-on, do not set the user
single sign-on.
-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
716
Option
Argument
Description
-Gateway
-hp
gateway_host1:port

-ResilienceTimeout

takes precedence.
service_name
node_name
Required. Name of the node where you want the Logger

Service to run.
license_name
License to assign to the service. If not already provided,

required before you can enable the service.
backup_node

backup node.
-re
-ServiceName
-sn
-NodeName
-nn
-LicenseName
-ln
-BackupNode
-bn
UpdateLoggerService
717
Option
Argument
Description
-StartParameters
start_parameters
Optional. Parameters to include when you start the Logger

Service. Separate the parameters with the space character.
-sp

- coldstart={Y|N}
Indicates whether to cold start or warm start the Logger
Service. Enter Y to cold start the Logger Service. If the
CDCT file contains log records, the Logger Service deletes
these records. Enter N to warm start the Logger Service
from the restart point that is indicated in the CDCT file.
Default is N.
- config=directory/pwx_config_file
Specifies the full path and file name for any dbmover.cfg
configuration file that you want to use instead of the default
dbmover.cfg file. This alternative configuration file takes
precedence over any alternative configuration file that you
specify in the PWX_CONFIG environment variable.
- cs=directory/pwxlogger_config_file
Specifies the path and file name for the Logger Service
configuration file. You can also use the cs parameter to
specify a Logger Service configuration file that overrides the
default pwxccl.cfg file. The override file must have a path or
file name that is different from that of the default file.
- encryptepwd=encrypted_password
A password in encrypted format for enabling the encryption
of PowerExchange Logger log files. With this password, the
PowerExchange Logger can generate a unique encryption
key for each Logger log file. The password is stored in the
CDCT file in encrypted format. For security purposes, the
password is not stored in CDCT backup files and is not
displayed in the CDCT reports that you can generate with
the PowerExchange PWXUCDCT utility.
If you specify this parameter, you must also specify
coldstart=Y.
If you specify this parameter and also specify the
ENCRYPTEPWD parameter in the PowerExchange Logger
configuration file, pwxccl.cfg, the parameter in the
configuration file takes precedence. If you specify this
parameter and also specify the ENCRYPTPWD parameter in
the PowerExchange Logger configuration file, an error
occurs.
You can set the AES algorithm to use for log file encryption
in the ENCRYPTOPT parameter of the pwxccl.cfg file. The
default is AES128.
Tip: For optimal security, Informatica recommends that you
specify the encryption password when cold starting the
PowerExchange Logger rather than in the pwxccl.cfg
configuration file. This practice can reduce the risk of
malicious access to the encryption password for the
following reasons: 1) The encryption password is not stored
in the pwxccl.cfg file, and 2) You can remove the password
from the command line after a successful cold start. If you
specify the encryption password for a cold start and then
need to restore the CDCT file later, you must enter the same
718
Option
Argument
Description
encryption password in the RESTORE_CDCT command of
the PWXUCDCT utility.
To not encrypt PowerExchange Logger log files, do not
enter an encryption password.
Specifies the full path and file name for any license key file
that you want to use instead of the default license.key file.
The alternative license key file must have a file name or
- specialstart={Y|N}
Indicates whether to perform a special start of the
PowerExchange Logger. A special start begins
PowerExchange capture processing from the point in the
change stream that you specify in the pwxccl.cfg file. This
start point overrides the restart point from the CDCT file for
the PowerExchange Logger run. A special start does not
delete any content from the CDCT file.
Use this parameter to skip beyond problematic parts in the
source logs without losing captured data. For example, use
a special start in the following situations:
- You do not want the PowerExchange Logger to capture
an upgrade of an Oracle catalog. In this case, stop the
PowerExchange Logger before the upgrade. After the
upgrade is complete, generate new sequence and restart
tokens for the PowerExchange Logger based on the postupgrade SCN. Enter these token values in the
SEQUENCE_TOKEN and RESTART_TOKEN parameters
in the pwxccl.cfg, and then special start the
PowerExchange Logger.
- You do not want the PowerExchange Logger to reprocess
old, unavailable logs that were caused by outstanding
UOWs that are not of CDC interest. In this case, stop the
PowerExchange Logger. Edit the RESTART_TOKEN
value to reflect the SCN of the earliest available log, and
then perform a special start. If any of the outstanding
UOWs that started before this restart point are of CDC
interest, data might be lost.
Valid values:
- Y. Perform a special start of the PowerExchange Logger
from the point in the change stream that is defined by the
SEQUENCE_TOKEN and RESTART_TOKEN parameter
values in the pwxccl.cfg configuration file. You must
specify valid token values in the pwxccl.cfg file to perform
a special start. These token values override the token
values from the CDCT file. Ensure that the
SEQUENCE_TOKEN value in the pwxccl.cfg is greater
than or equal to the current sequence token from the
CDCT file.
Do not also specify the coldstart=Y parameter. If you do,
the coldstart=Y parameter takes precedence.
- N. Do not perform a special start. Perform a cold start or
warm start as indicated by the coldstart parameter.
Default is N.
UpdateLoggerService
719
Option
Argument
Description
Note: In the config, cs, and license parameters, you must
provide the full path only if the file does not reside in the
-SvcPort
service_port
-sp
720
Port on which the Logger Service listens for commands

from the Service Manager.
CHAPTER 19
infacmd rms Command Reference

ListComputeNodeAttributes, 721
SetComputeNodeAttributes, 724
ListComputeNodeAttributes
Lists the compute node attributes that have been overridden for the specified node or for all nodes. Use the
infacmd rms SetComputeNodeAttributes command to override compute node attributes.
The default values for the attributes are the actual number of cores and memory available on the machine. If
the infacmd rms ListComputeNodeAttributes command does not list a value for an attribute, then the
Resource Manager Service is using the default values.
The infacmd rms ListComputeNodeAttributes command uses the following syntax:
ListComputeNodeAttributes
721
The following table describes infacmd rms ListComputeNodeAttributes options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

node_name
Optional. Name of the compute node that you want to

list the attributes for.
-pd
-NodeName
-nn
If you omit the option, the command lists the attributes

set for all compute nodes in the domain.
-ServiceName
service_name
-sn
722
Chapter 19: infacmd rms Command Reference
Optional. Enter Resource_Manager_Service.
ListServiceOptions
Lists the properties for the Resource Manager Service.
The infacmd rms ListServiceOptions command uses the following syntax:
ListServiceOptions
The following table describes infacmd rms ListServiceOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
-un
user_name

precedence.
ListServiceOptions
723
Option
Argument
Description
-Password
password

service_name
ds

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
SetComputeNodeAttributes
Overrides the compute node attributes for the specified node.
The default values for the attributes are the actual number of cores and memory available on the machine. To
reset an option to its default value, specify -1 as the value.
The infacmd rms SetComputeNodeAttributes command uses the following syntax:
[<-MaxCores|-mc> max_number_of_cores_to_allocate]
[<-MaxMem|-mm> max_memory_in_mb_to_allocate]
724
The following table describes infacmd rms SetComputeNodeAttributes options and arguments:
Option
Argument
Description
-DomainName
domain_name

takes precedence.
security_domain

-dn
-SecurityDomain
-sdn

installation.
-UserName
user_name
-un

precedence.
-Password
password

node_name
Required. Name of the compute node that you want to

set attributes for.
max_number_of_cores_to_allocate
Optional. Maximum number of cores that the Resource

Manager Service can allocate for jobs that run on the
compute node. A compute node requires at least five
available cores to initialize a container to start a DTM
process. If any compute node assigned to the grid has
fewer than five cores, then that number is used as the
minimum number of cores required to initialize a
container.
-pd
-NodeName
-nn
-MaxCores
-mc
By default, the maximum number of cores is the actual

number of cores available on the machine.
725
Option
Argument
Description
-MaxMem
max_memory_in_mb_to_allocate
Optional. Maximum amount of memory in megabytes

that the Resource Manager Service can allocate for
jobs that run on the compute node. A compute node
requires at least 2.5 GB of memory to initialize a
container to start a DTM process.
-mm
By default, the maximum memory is the actual memory

available on the machine.
-ServiceName
service_name
-sn
Updates Resource Manager Service properties. Run this command to configure the primary and back-up
nodes for the Resource Manager Service.
You can change the properties while the service is running, but you must recycle the service for the changed
properties to take effect.
The infacmd rms UpdateServiceOptions command uses the following syntax:
[<-NodeName|-nn> primary_node_name]
[<-BackupNodes|-bn> backup_node_name1,backup_node_name2,...]
726
The following table describes infacmd rms UpdateServiceOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
-re
ds

-Options
options
Optional. Enter each option separated by a space.
-pd
-ServiceName
-sn
-ResilienceTimeout
-o
727
Option
Argument
Description
-NodeName
primary_node_name
Optional. Primary node on which the Resource

backup_node_name1,bac
kup_node_name2,...

primary node is unavailable.
-nn
-BackupNodes
-bn
Resource Manager Service Options

Use the Resource Manager Service options with the infacmd rms UpdateServiceOptions command.
Enter Resource Manager Service options in the following format:
The following table describes Resource Manager Service options:
728
Option
Description
ResourceManagerServiceOptions.Log_Level
Level of error messages that the Resource Manager Service

writes to the service log. Choose one of the following message
levels: Fatal, Error, Warning, Info, Trace, or Debug.
CHAPTER 20
infacmd rtm Command Reference

DeployImport, 729
Export, 731
Import, 733
DeployImport
Imports content from an application file to the database that is read by the Model repository.
The infacmd rtm DeployImport command uses the following syntax:
DeployImport
<-securityDomain|-sdn> Security domain
[<-Gateway|-hp> Domain gateway host:port]
[<-NodeName|-nn> Node name]
<-DataIntegrationService|-ds> Data Integration Service name
<-CodePage|-cp> Code page
<-Folder|-f> The folder to import from
<-MetadataFile|-mf> Metadata file
729
The following table describes infacmd rtm DeployImport options and arguments:
Option
Argument
Description
-DomainName
Domain name
-dn
-UserName
precedence.
User name
-un

sign-on.
-Password
Password
Security
domain

-pd
-securityDomain
-sdn

-Gateway
-hp
Domain
gateway
host:port

domains.infa file is out of date. Enter the host name and port
number for the gateway node in the domain. Use the
following syntax:
gateway_hostname:HttpPort
-NodeName
Node name
Optional. Name of the gateway node for the Model

Repository Service.
Data
Integration
Service name
-ds
-CodePage
Code page
Required. Code page for the reference data to import.
-nn
-DataIntegrationService
-cp
730
Chapter 20: infacmd rtm Command Reference
Option
Argument
-Folder
-f
The folder to
import from
-MetadataFile
Metadata file
-mf
Description
Required. Path to the folder that contains the files to import.
You run the DeployImport command on the machine that
stores the folder. The folder option describes a path on the
machine that runs the command.
Required. Full name and path for the application file that you
apply the command to.
Export
Exports data from reference tables. You can export reference table objects or just the data. You can export
data from managed and unmanaged reference tables.
Define the export data with one of the following options:
ProjectFolder. Name of a project or folder to export.
MetadataFile. Name of a metadata.xml file that refers to the reference tables to export.
ObjectList. Full path to a text file that contains a list of objects to export.
When you configure an object list, create a text file that contains a list of objects with the following syntax:
ProjectName/FolderName/reference_table_object1
Note: You must configure each path in the object list to have slashes. Do not use backslash in the path.
The infacmd rtm Export command uses the following syntax:
Export
<-SecurityDomain|-sdn> Security domain
<-CodePage|-cp> Code Page
<-Folder|-f> The folder to export to
[<-ObjectList|-ol> List of Obects to export]
[<-ProjectFolder|-pf> Name of the project folder to export]
[<-metadataFile|-mf> Metadata file]
[<-Recursive|-r> Include subfolders when exporting project folder]
[<-SkipDatGeneration|-sdg> Skip Data Generation]
Export
731
The following table describes infacmd rtm Export options and arguments:
Option
Argument
Description
-DomainName
Domain name
-dn
-UserName
precedence.
User name
-un

sign-on.
-Password
Password
Security
domain

-pd
-SecurityDomain
-sdn

-Gateway
-hp
Domain
gateway
hostname:portn
umber

domains.infa file is out of date. Enter the host name and port
number for the gateway node in the domain. Use the
following syntax:
-NodeName
Node name

Repository Service.
Model
Repository
Service name
Model Repository Service name.
-rs
-CodePage
Code Page
Required. Code page for the reference data.
-nn
-RepositoryService
-cp
732
Option
Argument
Description
-Folder
The folder to
export to
Required. Target location for the export file.
List of Obects
to export
Fully qualified file name containing the list of reference table

objects.
Do not configure this option with the ProjectFolder or
metadataFile option.
Name of the
project folder to
export
Name of the project and folder to export. Use the following

syntax:
ProjectName/FolderName
-f
-ObjectList
-ol
-ProjectFolder
-pf
Do not configure with the metadataFile or ObjectList option.

-metadataFile
Metadata file
-mf
Required for object export. Full path and name for a

metadata.xml file that you want to apply the command to.
Exports all reference tables that the metadata. xml file
contains.
Do not configure this option with the ProjectFolder or
ObjectList option.
-Recursive
-r
-SkipDatGeneration
-sdg
Include
subfolders
when exporting
project folder
Optional. Use with the ProjectFolder option. Export more

than one level of object. Default is not recursive.
Skip Data
Generation
Optional. Writes a .dat file that describes the reference table

structure to the directory set in the folder property. The
reference table import process does not use this file. Default
is False.
Import
Performs a metadata and data import from object export files. Imports reference table metadata into the
Model repository and imports the data into the reference data database. Also imports reference data without
the metadata.
Before you import reference table data, the project must exist in the Model repository.
The infacmd rtm Import command uses the following syntax:
Import
<-securityDomain|-sdn> Security domain
Import
733

<-CodePage|-cp> Code page
<-ConflictResolution|-cr> Conflict resolution
<-ImportType|-it> Import type
<-Folder|-f> The folder to import from
[<-FileName|-fn> Required only for importing a single dictionary]
[<-MetadataFile|-mf> Required only for Object import]
[<-ProjectFolder|-pf> Name of the project folder to import into]
[<-NotRecursive|-nr> Don't include subfolders]
The following table describes infacmd rtm Import options and arguments:
Option
Argument
Description
-DomainName
Domain name
-dn
-UserName
precedence.
User name
-un

sign-on.
-Password
Password
Security
domain

-pd
-securityDomain
-sdn

734
Option
Argument
Description
-Gateway
-hp
Domain
gateway
host:port

domains.infa file is out of date. Host name and port number
for the gateway node in the domain. Use the following
syntax:
-NodeName
Node name

Repository Service.
Model
Repository
Service name
-rs
-CodePage
Code page
Required. Code page for the reference data.
-cr
Conflict
resolution
Required. Defines behavior when a name conflict occurs.

Enter one of the following arguments:
-ImportType
Import type
Required. The type of content to import. Enter

MetadataAndData for metadata and data import.
The folder to
import from
Required for metadata and data import. Full path to the

folder that contains the reference data file you want to
import.
Required only
for importing a
single
dictionary
Required for metadata and data import if you are importing

data from a single file. Name of the file that contains the
reference data you want to to import. The file name is
relative to the folder path.
Required only
for Object
import
Required when you import reference data values only. Full

path and name for the metadata.xml file that you apply the
command to. The metadata.xml file contains the metadata
associated with the reference data values. Do not use with
the ProjectFolder option.
Name of the
project folder to
import into
Required when you import reference data and metadata.

Name of the Model repository project that you want to import
into. Do not use with the MetadataFile option.
- Don't include
subfolders
Optional. Use with metadata and data import. Import one

level of objects only. Default is recursive.
-nn
-RepositoryService
-cp
-ConflictResolution
- Replace. Drop the existing reference table from the database

and create a new reference table.
- Rename. Create a new reference table with a different name.
- Skip. Do not import the reference table.
-it
-Folder
-f
-FileName
-fn
-MetadataFile
-mf
-ProjectFolder
-pf
-NotRecursive
-nr
Import
735
CHAPTER 21
infacmd sch Command Reference

CreateSchedule, 736
DeleteSchedule, 739
ListSchedule, 741
PauseAll, 746
PauseSchedule, 748
ResumeAll, 749
ResumeSchedule, 751
UpdateSchedule, 752
Upgrade, 761
CreateSchedule
Creates a schedule for deployed mappings or workflows that the Data Integration Service runs.
The infacmd sch CreateSchedule command uses the following syntax:
CreateSchedule
<-ScheduleName|-scn> schedule_name
[<-ScheduleDescription|-scd> schedule_description]
<-Recurrence|-r> once|daily|weekly|monthly
736
<-StartTime|-st> yyyy-MM-dd HH:mm

[<-EndTime|-et> yyyy-MM-dd HH:mm]
[<StartTimeTimeZone|-stz> start_time_timezone
[<-EndTimeTimeZone|-etz> end_time_time_zone]
[<-DailyRunEvery|-dre> daily_run_every]
[<-RunDaysOfWeek|-rdw> mon|tue|wed|thu|fri|sat|sun]
[<-RunDayOfWeekMonth|-rdwm> monday|tuesday|wednesday|thursday|friday|saturday|sunday]
[<-RunDayOfMonth|-rdm> 1-30|LAST_DAY_OF_MONTH]
[<-RepeatCount|-rc> repeat_count]
[<-RunnableObjects|-ro> runnable_objects]
[<-Status|-ss> SCHEDULED|SUSPENDED]
[<-RunNow|-rn> true|false]
To configure multiple values for an argument, separate the values with commas.
The following table describes infacmd sch CreateSchedule options and arguments:
Option
Argument
Description
-DomainName
domain_name
Required. Name of the Informatica domain. You can set the domain name with the -dn option
INFA_DEFAULT_DOMAIN. If you set a domain name with both methods, the -dn option takes
user_name
Required if the domain uses Native or LDAP authentication. User name to connect to the dom
option or the environment variable INFA_DEFAULT_DOMAIN_USER. If you set a user name
precedence.
-dn
-UserName
-un
Optional if the domain uses Kerberos authentication. To run the command with single sign-on
name, the command runs without single sign-on.
-Password
password
Required if you specify the user name. Password for the user name. The password is case se
option or the environment variable INFA_DEFAULT_DOMAIN_PASSWORD. If you set a pass
security_domain
Required if the domain uses LDAP authentication. Optional if the domain uses native authent
security domain to which the domain user belongs. You can set a security domain with the -sd
INFA_DEFAULT_SECURITY_DOMAIN. If you set a security domain name with both methods
-pd
-SecurityDomain
-sdn
If the domain uses native or LDAP authentication, the default is Native. If the domain uses Ke
security domain created during installation. The name of the security domain is the same as t
-Gateway
-hp
gateway_host1:port
Required if the gateway connectivity information in the domains.infa file is out of date. The ho
in the domain.
-ResilienceTimeout
Optional. Amount of time in seconds that infacmd attempts to establish or re-establish a conn
infacmd uses the timeout value specified in the INFA_CLIENT_RESILIENCE_TIMEOUT envir
schedule_name
Required. Name of the schedule. The schedule name is case sensitive.
-re
-ScheduleName
-scn
CreateSchedule
737
Option
Argument
Description
-Description
schedule_description
Optional. Schedule description.
once|daily|weekly|monthly
Required. Specify whether the schedule runs once or recurs.
yyyy-MM-dd HH:mm
Required. Date and time that the recurrence starts.
yyyy-MM-dd HH:mm
Optional. Date and time that the recurrence ends.
start_time_timezone
Optional. Time zone that the Scheduler Service uses to run objects. Default is GMT +00:00. C
-scd
-Recurrence
-r
-StartTime
-st
-EndTime
-et
-StartTimeTimeZone
-stz
-EndTimeTimeZone
GMT (+/) hh:mm

end_time_time_zone
-etz
-DailyRunEvery
Optional. Time zone that the Scheduler Service uses to run objects. Default is GMT +00:00. C
GMT (+/) hh:mm
daily_run_every
-dre
Optional. Run the schedule on an interval.

The following list describes the options that you can configure:
-
-RunDaysOfWeek
minute(s). Run the schedule daily every n minutes.

hour(s). Run the schedule daily every n hours.
day(s). Run the schedule every n days.
week(s). Run the schedule every n weeks.
month(s). Run the schedule every n months.
year(s). Run the schedule every n years.
FIRST. Run the schedule every first n day of the month. Use the -rdwm option to specify the day
SECOND. Run the schedule every second n day of the month. Use the -rdwm option to specify t
THIRD. Run the schedule every third n day of the month. Use the -rdwm option to specify the da
FOURTH. Run the schedule every fourth n day of the month. Use the -rdwm option to specify the
LAST. Run the schedule every last n day of the month. Use the -rdwm option to specify the day o
mon|tue|wed|thu|fri|sat|sun
Optional. Run the schedule on certain days of the week.
monday|tuesday|
wednesday|thursday|friday|
saturday|sunday
Optional. Run the schedule on certain days of the week every month. Use the -dre options to
or last n day of the month.
Optional. Run the schedule on day n of the month.
-rdm
1-30|
LAST_DAY_OF_MONTH
-RepeatCount
repeat_count
Optional. End the recurrence after a number of runs instead of on a date.
-rdw
RunDayOfWeekMonth
-rdwm
-RunDayofMonth
-rc
738
Chapter 21: infacmd sch Command Reference
Option
Argument
Description
-RunnableObjects
runnableObjects
Optional. Objects that you would like to schedule. Enter the object type, followed by the path
example:
-ro
"mapping:DIS_1234/Application_mapping/Mapping_abc"
Optionally, use the following arguments to configure a parameter file, parameter set, or run as
- parameterFilePath=PATH_TO_PARAMETER_FILE
- parameterSet=PARAMETER_SET_NAME
- runAsUser=USER_NAME&runAsUserSecurityDomain=SECURITY_DOMAIN&runAsUserPasswo
For example:
"workflow:DIS_1234/Application_workflow/Workflow_abc?parameterFile
Files/
Parameter.xml&runAsUser=Administrator&runAsUserSecurityDomain=Nati
-Status
SCHEDULED|PAUSED
Optional. Create the schedule in scheduled or paused state.
true|false
Run the schedule immediately.
-ss
-RunNow
-rn
DeleteSchedule
Deletes one or more schedules that the Scheduler Service manages.
The infacmd sch DeleteSchedule command uses the following syntax:
DeleteSchedule
DeleteSchedule
739
The following table describes infacmd sch DeleteSchedule options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
-hp
740
gateway_host1:port

Option
Argument
Description
-ResilienceTimeout
-re
ds

-ScheduleName
schedule_name
Name of the schedule that you want to delete.
-scn
ListSchedule
Lists schedules or scheduled objects that the Scheduler Service manages. The command returns schedules
or scheduled objects that meet all of the entered options.
The infacmd sch ListSchedule command uses the following syntax:
ListSchedule
[<-ScheduleName|-scn> schedule_name]
[<-Description|-scd> description]
[<-RunnableObjects|-ro> runnable_objects]
[<-ScheduleStatus|-ss> created|scheduled|paused|complete]
[<-NumberOfFireTimes|-n> number_of_fire_times]
[<-MaxResults|-m> max_results]
ListSchedule
741
The following table describes infacmd isp ListSchedule options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-Gateway
-hp
-ResilienceTimeout
-re
742
gateway_host1:port

ds

Option
Argument
Description
ScheduleName
schedule_name
Optional. Returns schedules with n name.
description
Optional. Returns schedules with n description.
runnableObjects
Optional. Lists the schedules that run an object. Enter

the object type and path on the Data Integration
Service in the following format:
-scn
Description
-scd
RunnableObjects
-ro
'{mapping|workflow}://dis_name/
app_name/obj_name'
For example,
'mapping://dis_demo/app_demo/
mapping_demo'
created|scheduled|
paused|completed
Optional. Returns schedules with n status.
-ss
ScheduleStatus
NumberOfFireTimes
number_of_fire_times
Optional. Returns schedules that have run n number

of times.
max_results
Optional. Maximum number of schedules you would

like the command to return.
-n
Maxresults
-m
ListServiceOptions
Returns a list of the properties that are configured for the Scheduler Service.
The infacmd sch ListServiceOptions command uses the following syntax:
ListServiceOptions
ListServiceOptions
743
The following table describes infacmd sch ListServiceOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
Required. Enter Scheduler_Service.
user_name

-dn
-ServiceName
-sn
-UserName
-un

sign-on.
-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-ResilienceTimeout

-re
744
Returns a list of the properties that are configured for a Scheduler Service process.
The infacmd sch ListServiceProcessOptions command uses the following syntax:
The following table describes infacmd sch ListServiceProcessOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
user_name

-dn
-ServiceName
-sn
-UserName
-un

sign-on.
-Password
-pd
password

745
Option
Argument
Description
-SecurityDomain
security_domain

sensitive.
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-ResilienceTimeout

node_name
Name of the node on which the service process runs.
-re
-NodeName
-nn
PauseAll
Pauses all schedules that the Scheduler Service manages. When you pause the schedules, the objects that
run on the schedules stop running until you resume the schedules.
The infacmd sch PauseAll command uses the following syntax:
PauseAll
746
The following table describes infacmd sch PauseAll options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-ResilienceTimeout

-re
PauseAll
747
PauseSchedule
Pauses a schedule that the Scheduler Service manages. When you a pause a schedule, the objects that run
on the schedule stop running until you resume the schedule.
The infacmd sch PauseSchedule command uses the following syntax:
PauseSchedule
The following table describes infacmd sch PauseSchedule options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password
-pd
748

Option
Argument
Description
-SecurityDomain
security_domain

case sensitive.
-sdn

-Gateway
gateway_host1:port

-re
ds

-ScheduleName
schedule_name
Name of the schedule that you want to pause. The

schedule name is case sensitive.
-hp
-ResilienceTimeout
-scn
ResumeAll
Resumes all paused schedules that the Scheduler Service manages.
The infacmd sch ResumeAll command uses the following syntax:
ResumeAll
ResumeAll
749
The following table describes infacmd sch ResumeAll options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password

security_domain

-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-ResilienceTimeout

-re
750
ResumeSchedule
Resumes a paused schedule that the Scheduler Service manages.
The infacmd sch ResumeSchedule command uses the following syntax:
ResumeSchedule
The following table describes infacmd sch ResumeSchedule options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
-pd
password

ResumeSchedule
751
Option
Argument
Description
-SecurityDomain
security_domain

case sensitive.
-sdn

-Gateway
gateway_host1:port

-re
ds

ScheduleName
schedule_name
Name of the paused schedule that you want to

resume.
-hp
-ResilienceTimeout
-scn
UpdateSchedule
Updates a schedule that the Scheduler Service manages. Update a schedule to change the start or end
times, recurrence, or objects that run on the schedule. To view the current options, run the infacmd sch
ListSchedule command.
The infacmd sch UpdateSchedule command uses the following syntax:
UpdateSchedule
752
[<-ScheduleDescription|-scd> schedule_description]
<-Recurrence|-r> once|daily|weekly|monthly
<-StartTime|-st> yyyy-MM-dd HH:mm
[<-EndTime|-et> yyyy-MM-dd HH:mm]
[<StartTimeTimeZone|-stz> start_time_timezone
[<-EndTimeTimeZone|-etz> end_time_time_zone]
[<-DailyRunEvery|-dre> daily_run_every]
[<-RunDaysOfWeek|-rdw> mon|tue|wed|thu|fri|sat|sun]
[<-RunDayOfWeekMonth|-rdwm> monday|tuesday|wednesday|thursday|friday|saturday|sunday]
[<-RunDayOfMonth|-rdm> 1-30|LAST_DAY_OF_MONTH]
[<-RepeatCount|-rc> repeat_count]
[<-RemoveRunnableObjects|-rro> removeRunnableObjects]
[<-AddRunnableObjects|-aro> addRunnableObjects]
To configure multiple values for an argument, separate the values with commas.
The following table describes infacmd sch UpdateSchedule options and arguments:
Option
Argument
Description
-DomainName
domain_name
Required. Name of the Informatica domain. You can set the domain name with the -dn opt
user_name
Required if the domain uses Native or LDAP authentication. User name to connect to the d
INFA_DEFAULT_DOMAIN_USER. If you set a user name with both methods, the -un optio
-dn
-UserName
-un
Optional if the domain uses Kerberos authentication. To run the command with single sign
single sign-on.
-Password
password
Required if you specify the user name. Password for the user name. The password is case
INFA_DEFAULT_DOMAIN_PASSWORD. If you set a password with both methods, the pa
security_domain
Required if the domain uses LDAP authentication. Optional if the domain uses native auth
domain user belongs. You can set a security domain with the -sdn option or the environme
with both methods, the -sdn option takes precedence. The security domain name is case s
-pd
-SecurityDomain
-sdn
If the domain uses native or LDAP authentication, the default is Native. If the domain uses
installation. The name of the security domain is the same as the user realm specified durin
-Gateway
Required if the gateway connectivity information in the domains.infa file is out of date. The
-hp
gateway_host1:port
-ResilienceTimeout
Optional. Amount of time in seconds that infacmd attempts to establish or re-establish a co

specified in the INFA_CLIENT_RESILIENCE_TIMEOUT environment variable. If no value
schedule_name
Required. Name of the schedule. The schedule name is case sensitive.
schedule_description
Optional. Schedule description.
-re
-ScheduleName
-scn
-Description
-scd
UpdateSchedule
753
Option
Argument
Description
-Recurrence
once|daily|weekly|monthly
Required. Specify whether the schedule runs once or recurs.
yyyy-MM-dd HH:mm
Required. Date and time that the recurrence starts.
yyyy-MM-dd HH:mm
Optional. Date and time that the recurrence ends.
start_time_timezone
Optional. Time zone that the Scheduler Service uses to run objects. Default is GMT +00:0
-r
-StartTime
-st
-EndTime
-et
-StartTimeTimeZone
-stz
-EndTimeTimeZone
GMT (+/) hh:mm

end_time_time_zone
-etz
-DailyRunEvery
Optional. Time zone that the Scheduler Service uses to run objects. Default is GMT +00:0
GMT (+/) hh:mm
daily_run_every
-dre
Optional. Run the schedule on an interval.

The following list describes the options that you can configure:
-
-RunDaysOfWeek
minute(s). Run the schedule daily every n minutes.

hour(s). Run the schedule daily every n hours.
day(s). Run the schedule every n days.
week(s). Run the schedule every n weeks.
month(s). Run the schedule every n months.
year(s). Run the schedule every n years.
FIRST. Run the schedule every first n day of the month. Use the -rdwm option to specify the
SECOND. Run the schedule every second n day of the month. Use the -rdwm option to speci
THIRD. Run the schedule every third n day of the month. Use the -rdwm option to specify the
FOURTH. Run the schedule every fourth n day of the month. Use the -rdwm option to specify
LAST. Run the schedule every last n day of the month. Use the -rdwm option to specify the d
mon|tue|wed|thu|fri|sat|sun
Optional. Run the schedule on certain days of the week.
monday|tuesday|
wednesday|thursday|friday|
saturday|sunday
Optional. Run the schedule on certain days of the week every month. Use the -dre options
1-30|
LAST_DAY_OF_MONTH
Optional. Run the schedule on day n of the month.
-rdm
-RepeatCount
repeat_count
Optional. End the recurrence after a number of runs instead of on a date.
-rdw
-RunDayOfWeekMonth
-rdwm
-RunDayofMonth
-rc
754
Option
Argument
Description
RemoveRunnableObjects
removeRunnableObjects
Optional. Removes objects from the schedule. Enter objects in the following format:
-rro
"{mapping|workflow}:Data Integration Service/Application/{Mappi

parameterSet=PARAMETER_SET_NAME]&[runAsUser=USER_NAME&runAsUser
AddRunnableObjects
addRunnableObjects
-aro
Optional. Adds objects to the schedule. Objects that you would like to schedule. Enter the
example:
"mapping:DIS_1234/Application_mapping/Mapping_abc"
Optionally, use the following arguments to configure a parameter file, parameter set, or run
- parameterFilePath=PATH_TO_PARAMETER_FILE
- parameterSet=PARAMETER_SET_NAME
- runAsUser=USER_NAME&runAsUserSecurityDomain=SECURITY_DOMAIN&runAsUserPass
For example:
"workflow:DIS_1234/Application_workflow/Workflow_abc?parameterF
Parameter.xml&runAsUser=Administrator&runAsUserSecurityDomain=N
Updates the properties for the Scheduler Service. To view the current options, run the infacmd sch
The infacmd sch UpdateServiceOptions command uses the following syntax:
<-DomainName:-dn> domain_name
[<-Gateway|-hp> gatway_host1:port gateway_host2:port...]
[<-NodeName|-nn> primary node name]
755
The following table describes infacmd sch UpdateServiceOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
service_name
user_name

takes precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-ResilienceTimeout

-re
756
Option
Argument
Description
-NodeName
primary node name
Optional. Primary node on which the service runs.
node_name1,node_name2,...

primary node is unavailable.
options
-nn
-BackupNodes
-bn
Options
-o
Scheduler Service Options

Use the Scheduler Service options with the infacmd sch UpdateServiceOptions command.
Enter Scheduler Service options in the following format:
The following table describes Scheduler Service options:
Option
Description
SchedulerPersistenceOptions.SchedulerRepositoryServiceName
Model Repository Service associated with

the Scheduler Service.
SchedulerPersistenceOptions.SchedulerRepositoryUsername
User name of an administrator user in the

Informatica domain. Not available for a
domain with Kerberos authentication.
SchedulerPersistenceOptions.SchedulerRepositoryPassword
Password of the administrator user in the

Informatica domain. Not available for a
domain with Kerberos authentication.
SchedulerPersistenceOptions.SchedulerRepositorySecurityDomain
LDAP security domain for the user who

manages the Scheduler Service. The
security domain field does not appear for
users with Native or Kerberos
authentication.
757
Option
Description
SchedulerLoggingOptions.SchedulerLogLevel
Determines the default severity level for the

service logs. Choose one of the following
options:
- Fatal. Writes FATAL messages to the log.
FATAL messages include nonrecoverable
system failures that cause the service to
shut down or become unavailable.
- Error. Writes FATAL and ERROR code
messages to the log. ERROR messages
include connection failures, failures to save
or retrieve metadata, service errors.
- Warning. Writes FATAL, WARNING, and
ERROR messages to the log. WARNING
errors include recoverable system failures
or warnings.
- Info. Writes FATAL, INFO, WARNING, and
ERROR messages to the log. INFO
messages include system and service
change messages.
- Trace. Write FATAL, TRACE, INFO,
WARNING, and ERROR code messages to
the log. TRACE messages log user request
failures.
- Debug. Write FATAL, DEBUG, TRACE,
INFO, WARNING, and ERROR messages
to the log. DEBUG messages are user
request logs.
SchedulerStorageOptions.SchedulerTempFileLocation
Path to the directory where parameter files

are read from and written to. Configure the
temporary file location to a directory that is
accessible to all of the nodes in the
domain.
Updates the properties for a Scheduler Service process. To view the current process configuration, run the
infacmd sch ListServiceProcessOptions command.
The infacmd sch UpdateServiceProcessOptions command uses the following syntax:
758
The following table describes infacmd sch UpdateServiceProcessOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
user_name

-dn
-ServiceName
-sn
-UserName
-un

sign-on.
-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-ResilienceTimeout

-re
759
Option
Argument
Description
NodeName
node_name
Name of the node on which the service process runs.
options
-nn
Options
-o
Scheduler Service Process Options

Use the Scheduler Service options with the infacmd sch UpdateServiceOptions command.
Enter Scheduler Service options in the following format:
The following table describes Scheduler Service options:
Option
Description
SchedulerServiceAdvancedOptions.JVMOptions
Java Virtual Machine (JVM) command line options to run Javabased programs. When you configure the JVM options, you
must set the Java SDK classpath, Java SDK minimum
memory, and Java SDK maximum memory properties.
You must set the following JVM command line options:
- Xms. Minimum heap size. Default value is 256 m.
- MaxPermSize. Maximum permanent generation size. Default is
128 m.
- Dfile.encoding. File encoding. Default is UTF-8.
760
HttpConfigurationOptions.KeyStoreFile
Path and file name of the keystore file that contains the keys
and certificates. Required if you use HTTPS connections for
the service. 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 in a keystore file. You
can use the self-signed certificate or use a certificate signed
by a certificate authority.
HttpConfigurationOptions.KeyStorePassword
HttpConfigurationOptions.TrustStoreFile
Path and file name of the truststore file that contains

authentication certificates trusted by the service.
HttpConfigurationOptions.TrustStorePassword
HttpConfigurationOptions.SSLProtocol
Secure Sockets Layer protocol to use. Default is TLS.
Option
Description
SchedulerServiceSecurityOptions.HttpPort
Unique HTTP port number for the Scheduler Service process

when the service uses the HTTP protocol.
Default is 6211.
SchedulerServiceSecurityOptions.HttpsPort
Unique HTTPS port number for the Scheduler Service process

when the service uses the HTTPS protocol.
When you set an HTTPS port number, you must also define
the keystore file that contains the required keys and
certificates.
Upgrade
Upgrades the Scheduler Service configuration. Run sch Upgrade when you upgrade to the current version of
Informatica.
The infacmd sch Upgrade command uses the following syntax:
Upgrade
The following table describes infacmd sch Upgrade options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
-dn
-ServiceName
-sn
Upgrade
761
Option
Argument
Description
-UserName
user_name

-un

sign-on.
-Password
password

security_domain

sensitive.
-pd
-SecurityDomain
-sdn

installation.
-Gateway
-hp
gateway_host1:port

-ResilienceTimeout

-re
762
CHAPTER 22
infacmd search Command

Reference
CreateService, 763
CreateService
Creates a Search Service. By default, the Search Service is enabled when you create it.
The infacmd search CreateService command uses the following syntax:
CreateService
<-SearchServicePort|-sp> search_service_port_number
<-IndexLocation|-il> search_index_location
<-ExtractionInterval|-ei> search_extraction_interval
<-RepositoryService|-rsn> model_repository_service_name
763
<-searchUserName|-sun> username_for_search_repositories
<-searchPassword|-spd> password_for_search_repositories
[<-searchSecurityDomain|-ssd> security_domain_of_search_repositories]
The following table describes infacmd search CreateService options and arguments:
Option
Argument
Description
-DomainName
domain_name

node_name
Required. Node where the Search Service runs.
security_domain

-dn
-NodeName
-nn
-SecurityDomain
-sdn

-UserName
user_name
-un

sign-on.
-Password
password
-pd
-ServiceName
service_name
-sn
Required. Name of the Search Service.
the domain. The characters must be compatible with the
code page of the associated repository. The name cannot
exceed 230 characters, have leading or trailing spaces, or
contain carriage returns, tabs, or the following characters:
/ * ? < > " |
764
Chapter 22: infacmd search Command Reference
Option
Argument
Description
-ResilienceTimeout
-re
timeout_period_i
n_seconds

takes precedence.
-FolderPath
full_folder_path

in which you want to add the Search Service. Must be in the
following format:
-fp
-BackupNodes
-bn
-SearchServicePort
-sp
-IndexLocation
-il
-ExtractionInterval
-ei
-RepositoryService
-rsn
-searchUserName
-sun
-searchPassword
-spd
-searchSecurityDomain
-ssdn
node_name1,nod
e_name2,...

search_service_
port_number
Required. Port on which the Search Service runs.
search_index_loc
ation
Directory that contains the search index files.
search_extractio
n_interval
Interval in seconds at which the Search Service updates the

search index.
model_repository
_service_name
Model Repository Service to associate with the Search

Service. The Model Repository Service cannot be assigned
to another Search Service.
username_for_se
arch_repositories
User name to access the Model Repository Service. The

Model repository user must have the Administrator role.
password_for_se
arch_repositories
User password to access the Model Repository Service.
security_domain
_of_search_repo
sitories

Model repository user belongs. You can set a security
CreateService
765
ListServiceOptions
Lists the properties for a Search Service.
The infacmd search ListServiceOptions command uses the following syntax:
ListServiceOptions
The following table describes infacmd search ListServiceOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

node_name
security_domain

case sensitive.
-dn
-NodeName
-nn
-SecurityDomain
-sdn

766
Option
Argument
Description
-UserName
user_name

precedence.
-un

-Password
password

service_name
ds

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
Lists the properties of a Search Service process.
The infacmd search ListServiceProcessOptions command uses the following syntax:
767
The following table describes infacmd search ListServiceProcessOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

node_name
Required. Name of node where the service process

runs.
security_domain

case sensitive.
-dn
-NodeName
-nn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
ds

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
768
Updates Search Service properties. To view current properties run the infacmd search ListServiceOptions
command.
You can change the properties while the service is running. However, you must recycle the service for
changes to take effect.
The infacmd search UpdateServiceOptions command uses the following syntax:
[<-NodeName|-nn> node name]
The following table describes infacmd search UpdateServiceOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

769
Option
Argument
Description
-UserName
user_name

precedence.
-un

-Password
password

service_name
-re
ds

-Options
options

Include an option value within double quotes if it has a
space. To view options, run the infacmd search
node name
Optional. Node on which the Search Service runs.
node_name1,node_name
2,...

-pd
-ServiceName
-sn
-ResilienceTimeout
-o
-NodeName
-nn
-BackupNodes
-bn
Updates properties for a Search Service process. To view current properties, run the infacmd search
770
The infacmd search UpdateServiceProcessOptions command uses the following syntax:

The following table describes infacmd search UpdateServiceProcessOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

node_name
security_domain

case sensitive.
-dn
NodeName
-nn
-SecurityDomain
-sdn

-UserName
-un
user_name

precedence.
771
Option
Argument
Description
-Password
password

service_name
-re
ds

-Options
options

view the options, run the infacmd search
-pd
-ServiceName
-sn
-ResilienceTimeout
-o
772
CHAPTER 23
infacmd sql Command Reference

ExecuteSQL, 773
ListColumnOptions, 774
ListSQLDataServiceOptions, 776
ListSQLDataServicePermissions, 777
ListSQLDataServices, 779
ListStoredProcedurePermissions, 780
ListTableOptions, 782
ListTablePermissions, 783
PurgeTableCache, 785
RefreshTableCache , 787
RenameSQLDataService, 788
SetColumnPermissions, 790
SetSQLDataServicePermissions, 792
SetStoredProcedurePermissions, 794
SetTablePermissions, 797
StartSQLDataService, 800
StopSQLDataService, 801
UpdateColumnOptions, 803
UpdateSQLDataServiceOptions, 805
UpdateTableOptions, 808
ExecuteSQL
Runs SQL statements that access an SQL data service.
Run infacmd sql ExecuteSQL in interactive or non-interactive mode. When you run ExecuteSQL in interactive
mode, you can enter SQL statements without writing a script. When you use the interactive mode, enter the
connect string without the -Sql option. You can run subsequent SQL statements without entering the
connection information for each statement.
773
The infacmd sql ExecuteSQL command uses the following syntax:

ExecuteSQL
<-ConnectString|-cs> connection_string
[<-Sql> sql_statement]
The following table describes infacmd sql ExecuteSQL options and arguments:
Option
Argument
Description
-ConnectString
connection_string
Required. Enter an SQL data service connect string with the

following syntax:
-cs
jdbc:informatica:sqlds/
<optional security domain\>
<optional user name>/
<optional user password>@
<domain host name>:
<domain HTTP port>?dis=
<Data Integration Service name>&sqlds=
<runtime SQL data service name>
Optionally, add options in the following format:
...
&<option_name>=<option_value>
The connect string has the following option and value:

SQLDataServiceOptions.disableResultSetCache=true
Disables result set caching for a SQL data service query when
the SQL data service is configured to cache the result set.
-Sql
sql_statement
Optional. Enter an SQL statement if you do not want to run in

interactive mode.
ListColumnOptions
Lists the properties for columns in a virtual table.
The infacmd sql ListColumnOptions command uses the following syntax:
ListColumnOptions
<-SQLDataService|-sqlds> sql_data_service
<-Table|-t> schema.table
<-Column|-c> column
774
Chapter 23: infacmd sql Command Reference
The following table describes infacmd sql ListColumnOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
Required. Name of the Data Integration Service where the

application is deployed.
user_name

-dn
-ServiceName
-sn
-UserName
-un

sign-on.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
onds

takes precedence.
SQLDataService
sql_data_service
Required. Name of the SQL data service.
-sqlds
ListColumnOptions
775
Option
Argument
Description
-Table
schema.table
Required. Name of the table. Define the table with the

following syntax:
-t
<schema_name>.<table_name>
-Column
column
Required. Name of the column.
-c
ListSQLDataServiceOptions
Lists the properties of an SQL data service that is deployed to a Data Integration Service.
The infacmd sql ListSQLDataServiceOptions command uses the following syntax:
ListSQLDataServiceOptions
The following table describes infacmd sql ListSQLDataServiceOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

user_name

-dn
-ServiceName
-sn
-UserName
-un

sign-on.
776
Option
Argument
Description
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
onds

takes precedence.
-SQLDataService
sql_data_service
-sqlds
ListSQLDataServicePermissions
Lists the permissions for an SQL data service.
The infacmd sql ListSQLDataServicePermissions command uses the following syntax:
<<-Direct> direct_permission_only|<-Effective> effective_permission_only>
777
The following table describes infacmd sql ListSQLDataServicePermissions options and arguments:
Option
Argument
Description
-DomainName
domain_name

takes precedence.
service_name

user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

installation.
-ResilienceTimeout
-re
778
s

Option
Argument
Description
SQLDataService
sql_data_service
direct | effective
Required. Level of permissions to list. Direct

permissions are permissions assigned directly to the
user or group. Effective permissions include direct
permissions and inherited permissions.
-sqlds
-Direct |
-Effective>
ListSQLDataServices
Lists the SQL data services for a Data Integration Service.
The infacmd sql ListSQLDataServices command uses the following syntax:
ListSQLDataServices
The following table describes infacmd sql ListSQLDataServices options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
-pd
password
ListSQLDataServices
779
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-ResilienceTimeout
-re
onds

takes precedence.
-ServiceName
service_name
Required. Data Integration Service where the application is

deployed.
-sn
ListStoredProcedurePermissions
Lists the permissions for a stored procedure.
The infacmd sql ListStoredProcedurePermissions command uses the following syntax:
<-StoredProcedure|-sp> stored_procedure
780
The following table describes infacmd sql ListStoredProcedurePermissions options and arguments:
Option
Argument
Description
-DomainName
domain_na
me

-sn
service_na
me

-UserName
user_name

-dn
-ServiceName
-un

sign-on.
-Password
password
security_do
main

-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
SQLDataService
-sqlds
timeout_pe
riod_in_sec
onds

takes precedence.
sql_data_s
ervice
781
Option
Argument
Description
StoredProcedure
stored_pro
cedure
Required. Stored procedure name.
direct |
effective
Required. Level of permissions to list. Direct permissions are

permissions assigned directly to the user or group. Effective
permissions include direct permissions and inherited
permissions.
-sp
-Direct |
-Effective>
ListTableOptions
Lists the properties for a virtual table.
The infacmd sql ListTableOptions command uses the following syntax:
ListTableOptions
The following table describes infacmd sql ListTableOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

user_name

-dn
-ServiceName
-sn
-UserName
-un

sign-on.
782
Option
Argument
Description
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
onds

takes precedence.
SQLDataService
sql_data_service
schema.table

following syntax:
-sqlds
-Table
-t
ListTablePermissions
Lists user and group permissions for a virtual table.
The infacmd sql ListTablePermissions command uses the following syntax:
783
The following table describes infacmd sql ListTablePermissions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

user_name

-dn
-ServiceName
-sn
-UserName
-un

sign-on.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
784
onds

takes precedence.
Option
Argument
Description
SQLDataService
sql_data_service
schema.table

following syntax:
-sqlds
-Table
-t
-Direct |
direct | effective
-Effective>
Required. Enter either direct or effective. Direct permissions

are permissions assigned directly to the user or group.
Effective permissions include direct permissions and
inherited permissions.
PurgeTableCache
Purges virtual table cache.
The infacmd sql PurgeTableCache command uses the following syntax:
PurgeTableCache
<-Table|-t> table
PurgeTableCache
785
The following table describes infacmd sql PurgeTableCache options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
onds

takes precedence.
-ServiceName
service_name

sql_data_service
table
Required. Name of virtual table cache to delete.
-sn
-SQLDataService
-sqlds
-Table
-t
.
786
RefreshTableCache
Refreshes a virtual table cache.
The infacmd sql RefreshTableCache command uses the following syntax:
RefreshTableCache
<-Table|-t> table
The following table describes infacmd sql RefreshTableCache options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
-pd
password
RefreshTableCache
787
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-ResilienceTimeout
-re
onds

takes precedence.
-ServiceName
service_name

sql_data_service
table
Required. Name of virtual table cache to refresh.
-sn
-SQLDataService
-sqlds
-Table
-t
RenameSQLDataService
Renames a SQL data service that is deployed to a Data Integration Service.
The infacmd sql RenameSQLDataService command uses the following syntax:
788
The following table describes infacmd sql RenameSQLDataService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
onds

takes precedence.
-ServiceName
service_name

SQL data service is deployed.
sql_data_service
Required. Name of the SQL data service to rename.
new_name
Required. New name for the SQL data service.
-sn
-SQLDataService
-sqlds
NewName
-n
789
SetColumnPermissions
Denies a group or user from accessing a column in a SQL query.
The infacmd sql SetColumnPermissions command uses the following syntax:
<-Column|-c> column_name
<<-GranteeUserName|-gun> grantee_user_name|<-GranteeGroupName|-ggn> grantee_group_name>
[<-GranteeSecurityDomain|-gsdn> grantee_security_domain]
<-DeniedPermissions|-dp> denied_permissions
The following table describes infacmd sql SetColumnPermissions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

user_name

takes precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password
-pd
790

Option
Argument
Description
-SecurityDomain
security_domain

sensitive.
-sdn

installation.
-ResilienceTimeout
-re
s

takes precedence.
-SQLDataService
sql_data_service
Required. Name of the SQL data service with the virtual

table.
schema.table
Required. Name of the virtual table. Enter table in the

following format:
-sqlds
-Table
-t
-Column
column
Name of the column to update.
grantee_user_name|
Required. User name or group name to set or deny

permissions for.
-c
-GranteeUserName|
GranteeGroupName
grantee_group_name
-gun|-ggn
GranteeSecurityDom
ain
grantee_security_domain
Required if you use LDAP authentication and you are

granting user permissions. Name of the security domain
that the user belongs to.
denied_permissions
Required. Enter SQL_Select to restrict a user from

including the column in a SELECT.
-gsdn
-DeniedPermissions
-dp
791
SetSQLDataServicePermissions
Sets permissions to groups or users for an SQL data service. You can also deny permissions.
The infacmd sql SetSQLDataServicePermissions command uses the following syntax:
<-AllowedPermissions|-ap> allowed_permissions
The following table describes infacmd sql SetSQLDataServicePermissions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
Required. Name of the Data Integration Service

where the application is deployed.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password
-pd
792

Option
Argument
Description
-SecurityDomain
security_domain

is case sensitive.
-sdn

-ResilienceTimeout

attempts to establish or reestablish a connection to
the resilience timeout period with both methods, the re option takes precedence.
sql_data_service
grantee_user_name|
Required. User name or group name to set or deny

permissions for.
-re
-SQLDataService
-sqlds
-GranteeUserName|
GranteeGroupName
-gun|-ggn
-GranteeSecurityDomain
grantee_group_name
Required if you use LDAP authentication and you are

granting user permissions. Name of the security
domain that the user belongs to.
allowed_permissions
Required. List of permissions separated by spaces.

Enter any of the following permissions:
-gsdn
-AllowedPermissions
-ap
-DeniedPermissions
-dp
- Grant. Users can grant and revoke permissions on the

SQL data service using the Administrator tool or using
the infacmd command line program.
- Execute. Users can run all virtual stored procedures
in the SQL data service using a JDBC or ODBC client
tool.
- SQL_Select. Users can run SQL SELECT statements
on virtual tables in the SQL data service using a
JDBC or ODBC client tool.
denied_permissions
Optional. List of permissions to deny users. Separate

each parameter by a space. Enter any of the
following permissions:
- EXECUTE. Users cannot run any virtual stored
procedure in the SQL data service.
- SQL_SELECT. Users cannot run SELECT statements
on any table in the SQL data service.
793
SetStoredProcedurePermissions
Sets user and group permissions for a stored procedure. You can also deny permissions.
The infacmd sql SetStoredProcedurePermissions command uses the following syntax:
<-StoredProcedure|-sp> stored_procedure
The following table describes infacmd sql SetStoredProcedurePermissions options and arguments:
Option
Argument
Description
-DomainName
domain_name

domain. You can set the domain
name with the -dn option or the
INFA_DEFAULT_DOMAIN. If you
set a domain name with both
precedence.
service_name
Required. Name of the Data

Integration Service where the
-dn
-ServiceName
-sn
794
Option
Argument
Description
-UserName
user_name
Required if the domain uses Native

or LDAP authentication. User name
to connect to the domain. You can
set the user name with the -un
INFA_DEFAULT_DOMAIN_USER. If
you set a user name with both
methods, the -un option takes
precedence.
-un
Optional if the domain uses

Kerberos authentication. To run the
command with single sign-on, do not
set the user name. If you set the
user name, the command runs
-Password
password
Required if you specify the user

name. Password for the user name.
The password is case sensitive. You
can set a password with the -pd
INFA_DEFAULT_DOMAIN_PASSW
ORD. If you set a password with
both methods, the password set with
security_domain

authentication. Optional if the
domain uses native authentication
or Kerberos authentication. Name of
the security domain to which the
domain user belongs. You can set a
security domain with the -sdn option
INFA_DEFAULT_SECURITY_DOM
AIN. If you set a security domain
name with both methods, the -sdn
option takes precedence. The
security domain name is case
sensitive.
-pd
-SecurityDomain
-sdn

authentication, the default is Native.
If the domain uses Kerberos
authentication, the default is the
LDAP security domain created
during installation. The name of the
security domain is the same as the
user realm specified during
installation.
795
Option
Argument
Description
-ResilienceTimeout
Optional. Amount of time in seconds

that infacmd attempts to establish or
re-establish a connection to the
domain. You can set the resilience
timeout period with the -re option or
INFA_CLIENT_RESILIENCE_TIME
OUT. If you set the resilience
timeout period with both methods,
the -re option takes precedence.
sql_data_service
Required. Name of the SQL data

service with the stored procedure.
stored_procedure
Required. Name of the stored

procedure.
grantee_user_name|
Required. User name or group name

to set or deny permissions for.
-re
-SQLDataService
-sqlds
-StoredProcedure
-sp
-GranteeUserName|
GranteeGroupName
grantee_group_name
-gun|-ggn
GranteeSecurityDomai
n
Required if you use LDAP

authentication and you are granting
user permissions. Name of the
security domain that the user
belongs to.
list_of_allowed_permissions_separated_by_sp
ace
Required. List of permissions to

allow. Enter any of the following
parameters separated by a space:
-gsdn
-AllowedPermissions
-ap
- Grant. Users can grant and revoke

permissions on the stored
procedure objects using the
Administrator tool or using the
infacmd command line program
- Execute. Users can run virtual
stored procedures in the SQL data
service using a JDBC or ODBC
client tool.
-DeniedPermissions
denied_permissions
-dp
Optional. List of permissions to deny

users. Enter any of the following
parameters separated by a space:
- GRANT. Users cannot grant and
revoke permissions on the stored
procedure objects.
- EXECUTE. Users can not run a
stored procedure in the SQL data
service.
796
SetTablePermissions
Sets group and user permissions on a virtual table.
The infacmd sql SetTablePermissions command uses the following syntax:
SetTablePermissions
[<-RLSPredicate|-rls> row_level_security_predicate]
The following table describes infacmd sql SetTablePermissions options and arguments:
Option
Argument
Description
-DomainName
domain_name

domain. You can set the domain
name with the -dn option or the
INFA_DEFAULT_DOMAIN. If you
set a domain name with both
precedence.
service_name

Integration Service where the
-dn
-ServiceName
-sn
SetTablePermissions
797
Option
Argument
Description
-UserName
user_name
Required if the domain uses Native

or LDAP authentication. User name
to connect to the domain. You can
set the user name with the -un
precedence.
-un
Optional if the domain uses

Kerberos authentication. To run the
command with single sign-on, do not
set the user name. If you set the
user name, the command runs
-Password
password
Required if you specify the user

name. Password for the user name.
The password is case sensitive. You
can set a password with the -pd
INFA_DEFAULT_DOMAIN_PASSW
ORD. If you set a password with
both methods, the password set with
security_domain

authentication. Optional if the
domain uses native authentication
or Kerberos authentication. Name of
the security domain to which the
domain user belongs. You can set a
security domain with the -sdn option
INFA_DEFAULT_SECURITY_DOM
AIN. If you set a security domain
name with both methods, the -sdn
option takes precedence. The
security domain name is case
sensitive.
-pd
-SecurityDomain
-sdn

authentication, the default is Native.
If the domain uses Kerberos
authentication, the default is the
LDAP security domain created
during installation. The name of the
security domain is the same as the
user realm specified during
installation.
798
Option
Argument
Description
-ResilienceTimeout

INFA_CLIENT_RESILIENCE_TIME
OUT. If you set a the resilience
timeout period with both methods,
sql_data_service
Required. Name of the SQL data

service with the virtual table.
schema.table
Required. Name of the virtual table.

Enter table in the following format:
-re
-SQLDataService
-sqlds
-Table
-t
<schema_name>.<table_name
>
-GranteeUserName|
GranteeGroupName
grantee_user_name|
grantee_group_name
Required. User name or group name

to set or deny permissions for.
-gun|-ggn

user permissions. Name of the
security domain that the user
belongs to.
list_of_allowed_permissions
Required. List of permissions to

allow. Enter any of the following
parameters separated by space:
-gsdn
-AllowedPermissions
-ap
- Grant. Users can grant and revoke

permissions on the stored
procedure objects using the
Administrator tool or using the
infacmd command line program.
- SQL_Select. Users can run SQL
queries against the table.
-DeniedPermissions
denied_permissions
-dp

revoke permissions on the table.
- SQL_SELECT. Users can not run
SQL queries against the table.
-RLSPredicate
-rls
row_level_security_predicate
Optional. Lists the row level security

predicate to apply to SELECT
statements.
SetTablePermissions
799
StartSQLDataService
Starts an SQL data service.
The infacmd sql StartSQLDataService command uses the following syntax:
StartSQLDataServiceOptions
The following table describes infacmd sql StartSQLDataService options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

user_name

-dn
-ServiceName
-sn
-UserName
-un

sign-on.
-Password
password
-pd
800
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-ResilienceTimeout
-re
onds

takes precedence.
-SQLDataService
sql_data_service
-sqlds
StopSQLDataService
Stops an SQL data service from running.
The infacmd sql StopSQLDataService command uses the following syntax:
StopSQLDataService
StopSQLDataService
801
The following table describes infacmd sql StopSQLDataService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
onds

takes precedence.
-ServiceName
service_name

SQL data service is deployed.
sql_data_service
Required. Name of the SQL data service to stop.
-sn
-SQLDataService
-sqlds
802
UpdateColumnOptions
Sets column options to determine what happens when a user selects a restricted column in a query. You can
substitute the value with NULL or with a constant value.
The infacmd sql UpdateColumnOptions command uses the following syntax:
UpdateColumnOptions
<-Column|-c> column_name
The following table describes infacmd sql UpdateColumnOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

user_name

-dn
-ServiceName
-sn
-UserName
-un

sign-on.
-Password
-pd
password

UpdateColumnOptions
803
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-ResilienceTimeout
-re
timeout_period_in_s
econds

takes precedence.
-SQLDataService
sql_data_service
Required. Name of the SQL data service with the virtual

table.
schema.table
Required. Name of the virtual table. Enter table in the

following format:
-sqlds
-Table
-t
-Column
column
Column name.
options
Required. Enter each option separated by a space. To view

current options, run the infacmd sql ListColumnOptions
command.
-c
-Options
-o
Column Options
Use column options to update a column. Use the column options with the infacmd sql UpdateColumnOptions
command.
Enter column options in the following format:
... -o UpdateColumnOptions.option_name=value ...
804
The following table describes column options:

Options
Description
ColumnOptions.DenyWith
When you use column level security, this property determines

whether to substitute the restricted column value or to fail the
query. If you substitute the column value, you can choose to
substitute the value with NULL or with a constant value.
Select one of the following options:
- ERROR. Fails the query and returns an error.
- NULL. Returns null values for a restricted column in each row.
- VALUE. Returns a constant value in place of the restricted column
in each row. Configure the constant value in the
InsufficientPermissionValue option.
ColumnOptions.InsuffiicientPermissionValue
Substitutes the restricted column value with a constant value. The

default is an empty string. If you do not configure
ColumnOptions.DenyWith the Data Integration Service ignores the
InsufficientPermissionValue option.
UpdateSQLDataServiceOptions
Updates SQL data service properties. You must stop the SQL data service before you update the properties.
The infacmd sql UpdateSQLDataServiceOptions command uses the following syntax:
The following table describes infacmd sql UpdateSQLDataServiceOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

-dn
-ServiceName
-sn
805
Option
Argument
Description
-UserName
user_name

-un

sign-on.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
onds

takes precedence.
-SQLDataService
sql_data_service
options
Required. List of options to update. Enter options and values

separated by spaces. To view options for a SQL data
service, run infacmd sql ListSQLDataServiceOptions.
-sqlds
options
-o
SQL Data Service Options

Use SQL data service options to update a SQL data service. Use the SQL data service options with the
infacmd sql UpdateSQLDataServiceOptions command.
Enter SQL data service options in the following format:
... -o SQLDataServiceOptions.option_name=value ...
806
The following table describes connection options for infacmd sql UpdateSQLDataServiceOptions:
Option
Description
SQLDataServiceOptions.startupType
Determines whether the SQL data service is enabled

to run when the application starts or when you start
the SQL data service. Enter ENABLED to allow the
SQL data service to run. Enter DISABLED to prevent
the SQL data service from running.
SQLDataServiceOptions.traceLevel
Level of error messages written to the session log.

Specify one of the following message levels:
-
Fatal
Error
Info
Trace
Debug
SQLDataServiceOptions.connectionTimeout
Maximum number of milliseconds to wait for a

connection to the SQL data service. Default is
3,600,000.
SQLDataServiceOptions.requestTimeout
Maximum number of milliseconds for a SQL request

to wait for a SQL Data Service response. Default is
3,600,000.
SQLDataServiceOptions.sortOrder
Sort order that the Data Integration Service uses for

sorting and comparing data when running in Unicode
mode. You can choose the sort order based on your
code page. When the Data Integration runs in ASCII
mode, it ignores the sort order value and uses a
binary sort order. Default is binary.
SQLDataServiceOptions.maxActiveConnections
Maximum number of active connections to the SQL

data service. Default is 10.
SQLDataServiceOptions.ResultSetCacheExpirationPeriod
The number of milliseconds that the result set cache

is available for use. If set to -1, the cache never
expires. If set to 0, result set caching is disabled.
Changes to the expiration period do not apply to
existing caches. If you want all caches to use the
same expiration period, purge the result set cache
after you change the expiration period. Default is 0.
807
Option
Description
SQLDataServiceOptions.DTMKeepAliveTime
Number of milliseconds that the DTM instance stays

open after it completes the last request. Identical
SQL queries can reuse the open instance. Use the
keep alive time to increase performance when the
time required to process the SQL query is small
compared to the initialization time for the DTM
instance. If the query fails, the DTM instance
terminates.
Must be an integer. A negative integer value means
that the DTM Keep Alive Time for the Data
Integration Service is used. 0 means that the Data
Integration Service does not keep the DTM instance
in memory. Default is -1.
SQLDataServiceOptions.optimizeLevel
The optimizer level that the Data Integration Service

applies to the object. Enter the numeric value that is
associated with the optimizer level that you want to
configure. You can enter one of the following
numeric values:
- 0. The Data Integration Service does not apply
optimization.
- 1. The Data Integration Service applies the early
projection optimization method.
- 2. The Data Integration Service applies the early
projection, early selection, push-into, and predicate
optimization methods.
- 3. The Data Integration Service applies the costbased, early projection, early selection, push-into,
predicate, and semi-join optimization methods.
UpdateTableOptions
Updates virtual table properties. You must stop the SQL data service before you update the properties.
The infacmd sql UpdateTableOptions command uses the following syntax:
UpdateTableOptions
808
The following table describes infacmd sql UpdateTableOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

user_name

-dn
-ServiceName
-sn
-UserName
-un

sign-on.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
onds

takes precedence.
SQLDataService
sql_data_service
-sqlds
UpdateTableOptions
809
Option
Argument
Description
-Table
schema.table
Required. Name of the table. Use the following syntax:
-t
Options
options
Required. Enter the name-value pair separated by spaces.
-o
Virtual Table Options

Use the virtual table options to configure caching for a virtual table. Use the virtual table options with the
infacmd sql UpdateTableOptions command.
Enter virtual table options in the following format:
... -o option_type.option_name=value ...
The following table describes virtual table options:
Option
Description
VirtualTableOptions.CachingEnabled
Cache the virtual table in the data object cache database. True or
false. Default is true.
VirtualTableOptions.CacheRefreshPeriod
Number of minutes between cache refreshes. Default is zero.
VirtualTableOptions.CacheTableName
The name of the user-managed table from which the Data Integration
Service accesses the virtual table cache. A user-managed cache
table is a table in the data object cache database that you create,
populate, and manually refresh when needed.
If you specify a cache table name, the Data Object Cache Manager
does not manage the cache for the object and ignores the cache
refresh period. If you do not specify a cache table name, the Data
Object Cache Manager manages the cache for the object.
810
CHAPTER 24
infacmd tdm Command Reference

The infacmd tdm program administers the Test Data Manager Service. You can create the service, add
content to the service, enable the service and disable the service with the infacmd tdm commands.
This chapter includes the commands that you can use with the infacmd tdm program. Run the commands
from the <INFA_HOME\isp\bin path.
Note: You do not need to add the UserName and Password options when you run the commands in Kerberos
network authentication mode.
CreateService
Creates a Test Data Manager Service in a domain.
The infacmd tdm CreateService command uses the following syntax:
CreateService
<-PCRSServiceName|-pcrs> power_center_repo_service
<-PCISServiceName|-pcis> power_center_int_service
<-MRSServiceName|-mrs> model_repo_service
<-MRSUserName|-rsun> model_repo_service_username
<-MRSPassword|-rspd> model_repo_service_password
[<-MRSSecurityDomain|-rsdn> model_repo_security_domain]
<-AnalystService|-at> analyst_service
<-EnableProfiling|-ep> enable_profiling
811
<-EnableTDWService|-ets> enable_tdwservice
<-DISServiceName|-dis> data_integration_service
<-db_type|-dt> database_type (ORACLE, DB2, SQLSERVER or CUSTOM)
[<-customDriver|-cd> custom_driver_name]
<-DBUsername|-du> db_user
<-DBPassword|-dp> db_password
<-DBUrl|-dl> db_url
<-DBConnString|-dc> db_conn_string
[<-DbSchema|-ds> db_schema (used for SQL Server only)]
[<-DbTablespace|-db> db_tablespace (used for DB2 only)]
[<-httpProtocolType|-pt> http_protocol_type]
[<-jvmParams|-jp> jvmParameters]
[<-connPoolSize|-cp> conn_pool_size]
[<-jmxPort> jmx_port]
[<-shutdownPort> shutdown_port]
The following table describes infacmd tdm CreateService options and arguments:
Option
Argument
Description
-DomainName
domain_name

precedence.
service_name
Required. Name of the Test Data Manager

Service.
-dn
-ServiceName
-sn
The name is not case sensitive and must be

unique within the domain. The characters must
be compatible with the code page of the
associated repository. The name cannot exceed
230 characters, have leading or trailing spaces,
or contain carriage returns, tabs, or the
/ * ? < > " |
812
Chapter 24: infacmd tdm Command Reference
Option
Argument
Description
-UserName
user_name

takes precedence.
-un

sign-on.
-Password
password

case sensitive. You can set a password with the
-pd option or the environment variable
precedence.
security_domain

-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
conds

connection to the domain. You can set the
resilience timeout period with the -re option or
INFA_CLIENT_RESILIENCE_TIMEOUT. If you
set a the resilience timeout period with both
methods, the -re option takes precedence.
Default is 180 seconds.
-NodeName
node_name

will run.
-nn
CreateService
813
Option
Argument
Description
-LicenseName
license_name
Required. Name of the license. The name is not

case sensitive and must be unique within the
domain. The name cannot exceed 79
characters, have leading or trailing spaces, or
contain carriage returns, tabs, or the following
characters:
-ln
/*?<>"|
-PCRSServicename
power_center_repo_s
ervice
Name of the PowerCenter Repository Service to

which TDM connects.
-pcis
power_center_int_ser
vice
Name of the PowerCenter Integration Service to

which TDM connects.
-MRSServiceName
model_repo_service
Name of the Model Repository Service to which

TDM connects.
model_repo_service_
username
Required. User name to connect to the Model

repository.
-rspd
model_repo_service_
password
Required. Password for the user name to

connect to the Model repository. The password
is case sensitive.
-AnalystService
analyst_service
Optional. Name of the Analyst Service that TDM

uses for asset linking. Required if you use the
asset linking feature to link TDM global objects
to the Business Glossary objects.
model_repo_security_
domain

of the security domain that the user belongs to.
Security domain is case sensitive.
-pcrs
-PCISServicename
-mrs
-MRSUserName
-rsun
-MRSPassword
-at
-MRSSecurityDomain
-rsdn
Default is Native.
-EnableProfiling
enable_profiling
Indicates data discovery settings. Set to true to

enable data discovery. Set to false to disable
data discovery.
enable_tdwservice
Indicates test data warehouse settings. Set to

true if you plan to configure a test data
repository and test data mart. Set to false if you
do not need to create a test data warehouse.
-ep
-EnableTDWService
ets
Default is false.
-DISServiceName
-dis
data_integration_servi
ce
Name of the Data Integration Service to which

TDM connects.
-db_type
database_type
Type of TDM repository database. Values are

Oracle, SQL Server, DB2, or Custom.
custom_driver_name
Custom JDBC driver parameters. Required if

you want to use a custom database type.
-dt
-customDriver
-cd
814
Option
Argument
Description
-DBUsername
db_user
Required. Account for the repository database.

Use the database client to set up this account.
db_password
Required. Repository database password for

the database user.
db_url
Required. JDBC connect string to the database

for the TDM repository. Use one of the following
syntaxes:
-du
-DBPassword
-dp
-DBUrl
-dl
Oracle:
jdbc:informatica:oracle: //
<machineName>:<PortNo>;ServiceNam
e= <DBName>;
MaxPooledStatements=20;
CatalogOptions=0;
EnableServerResultCache=true
DB2:
jdbc:informatica:db2: //
<host>:<port>;
DatabaseName=<dbname>;
BatchPerformanceWorkaround=true;D
ynamicSections=1000
SQLServer:
jdbc:informatica:sqlserver: //
<host>:<port>;
DatabaseName=<dbname>;
SnapshotSerializable=true
-DBConnString
db_conn_string
Native connect string to the TDM repository

database. The service uses the connect string
to create a connection object to the Test Data
Manager repository and the PowerCenter
repository.
db_schema
Optional. The schema name for a Microsoft

SQL Server database.
db_tablespace

configure a tablespace name, the Test Data
Manager Service creates all repository tables in
the same tablespace. You cannot use spaces in
the tablespace name.
-dc
-DbSchema
-ds
-DbTablespace
-db
The tablespace must be defined on a single

node and the page size must be 32 KB. In a
multipartition database, you must select this
option. In a single-partition database, if you do
not select this option, the installer creates the
tables in the default tablespace.
-HttpPort
http_port
Required. Port number for the service.
-HttpsPort
https_port
Optional. Port number to secure the connection

to the Administrator tool. Set this port number if
you want to configure HTTPS for a node.
CreateService
815
Option
Argument
Description
-KeystoreFile
keystore_file_location]
Optional. Keystore file that contains the keys

and certificates required if you use the SSL
security protocol with PowerCenter.
keystore_password
Optional. If TLS is enabled, you must specify a

password.
http_protocol_type
Security protocol that the service uses. Enter

one of the following values:
-kf
-KeystorePassword
-kp
-httpProtocolType
-pt
- HTTP. Requests to the service must use an

HTTP URL
- HTTPS. Requests to the service must use an
HTTPS URL.
- Both. Requests to the service can use either an
HTTP or an HTTPS URL.
When you set the HTTP protocol type to HTTPS

or Both, you enable Transport Layer Security
(TLS) for the service.
You can also enable TLS for each web service
deployed to an application. When you enable
HTTPS for the service and enable TLS for the
web service, the web service uses an HTTPS
URL. When you enable HTTPS for the service
and do not enable TLS for the web service, the
web service can use an HTTP URL or an
HTTPS URL. If you enable TLS for a web
service and do not enable HTTPS for the
service, the web service does not start.
Default is HTTP.
-jvmParams
-jp
jvmParameters
JVM parameters to set:

- The heap size allocated for Test Data Manager.
- The time after which database connections are
renewed if the TDM UI remains idle. Required if
you have modified the database configuration
settings to values less than the TDM defaults.
Edit the values in TDM such that the values are
less than the database values.
Include the JVM parameters in single quotes

and then in double quotes. For example, 'value'
and then "'value'".
The -Xms option is case sensitive. For example:
"'- Xms512m - Xmx1024m XX:MaxPermSize=512m'"
- IDLE_TIME.
-DIDLE_TIME=<seconds>. Default is 300

seconds.
- CONNECT_TIME.
-DCONNECT_TIME=<seconds>. Default is
5000 seconds.
816
Option
Argument
Description
-connPoolSize
conn_pool_size
Optional. The maximum number of idle

connection instances that a pool maintains for a
database connection before the maximum idle
time is met. Set this value to be more than the
Default is 15.
-jmxPort
jmx_port
Port number for the JMX/RMI connections to

TDM. Default is 6675.
-shutdownPort
shutdown_port
Port number that controls shutdown for TDM.
-cp
CreateContents
Creates repository content for the Test Data Manager repository.
The infacmd tdm CreateContents command uses the following syntax:
CreateContents
817
The following table describes infacmd tdm CreateContents options and arguments:
Option
Argument
Description
-DomainName
domain_name

security_domain

case sensitive.
-dn
-SecurityDomain
-sdn

-UserName
user_name
-un

precedence.
-Password
password

service_name
Required. The Test Data Manager Service name.
conds

-pd
-ServiceName
-sn
-ResilienceTimeout
-re
818
EnableService
Enables the Test Data Manager Service.
The infacmd tdm EnableService command uses the following syntax:
The following table describes infacmd tdm EnableService options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
Required. Name of the service you want to run the command

against. To enter a name that contains a space or other nonalphanumeric character, enclose the name in quotation marks.
user_name

-dn
-ServiceName
-sn
-UserName
-un

-Password
-pd
password
precedence.
EnableService
819
Option
Argument
Description
-SecurityDomain
security_domain

sensitive.
-sdn

-ResilienceTimeout
-re
timeout_period_in_s
econds

DisableService
Disables the Test Data Manager Service. When you disable the Test Data Manager Service, all the service
processes stop.
The infacmd tdm DisableService command uses the following syntax:
<-DisableMode|-dm> disable_mode: COMPLETE|ABORT|STOP
The following table describes infacmd tdm DisableService options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name
Required. Name of the service you want to run the command

against. To enter a name that contains a space or other nonalphanumeric character, enclose the name in quotation marks.
-dn
-ServiceName
-sn
820
Option
Argument
Description
-UserName
user_name

-un

-Password
password
precedence.
security_domain

sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
timeout_period_in_s
econds

-DisableMode
disable_mode
Required. Defines how the service is disabled:
-dm
- Complete. Disables the service after all service processes stop.

- Abort. Stops all processes immediately, and then disables the
service.
- Stop. Stops all running workflows, and then disables the service.
DisableService
821
CHAPTER 25
infacmd wfs Command Reference

abortWorkflow, 822
bulkComplete, 824
cancelWorkflow, 826
createTables, 828
dropTables, 830
listActiveWorkflowInstances, 831
listMappingPersistedOutputs, 833
listWorkflowParams, 834
listWorkflows, 837
recoverWorkflow, 838
setMappingPersistedOutputs, 840
startWorkflow, 842
upgradeParameterFile, 844
abortWorkflow
Aborts a running workflow instance.
If an Assignment task or an Exclusive gateway is running, the Data Integration Service completes the task or
gateway. After the task aborts or completes, the service aborts the workflow instance. The service does not
start running any subsequent workflow objects.
The infacmd wfs abortWorkflow command uses the following syntax:
abortWorkflow
<-InstanceId|-iid> instance_id
822
The following table describes infacmd wfs abortWorkflow options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

running the workflow instance.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password
-pd
-InstanceId
-iid
instance ID of the
workflow to be aborted

Required. Workflow instance ID to abort.
You can read the workflow instance ID from the
workflow properties on the Monitoring tab of the
Administrator tool. Or, run infacmd wfs
ListActiveWorkflowInstances to find the workflow
instance ID.
abortWorkflow
823
Option
Argument
Description
-SecurityDomain
security_domain

is case sensitive.
-sdn

-ResilienceTimeout
-re
s

INFA_CLIENT_RESILIENCE_TIMEOUT. If you set
bulkComplete
Stops all operations for a Human task in a workflow that you specify, and passes the records that the task
identifies to the next stage in the workflow. The bulkComplete command updates the status of the steps in
the Human task to indicate that the steps are complete. The command does not edit or update the status of
the records that the task identifies.
The bulkComplete command uses the following syntax:
bulkComplete
<-InstanceId|-iid> Instance_id
824
Chapter 25: infacmd wfs Command Reference
The following table describes infacmd wfs bulkComplete options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

runs the workflow instance.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

Instance_ID
Required. Unique identifier for the workflow that runs

the Human task that you want to complete.
-pd
InstanceID
-iid

instance ID.
bulkComplete
825
Option
Argument
Description
-SecurityDomain
security_domain

case sensitive.
-sdn

-ResilienceTimeout
-re
ds

cancelWorkflow
Cancels a running workflow instance. When you cancel a workflow instance, the Data Integration Service
finishes processing any running task and then stops processing the workflow instance. The service does not
start running any subsequent objects.
The infacmd wfs cancelWorkflow command uses the following syntax:
cancelWorkflow
<-InstanceID|-iid> instance_ID
826
The following table describes infacmd wfs cancelWorkflow options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

running the workflow instance.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

is case sensitive.
-pd
-SecurityDomain
-sdn

cancelWorkflow
827
Option
Argument
-InstanceID
instance_ID
-iid
Description
Required. Workflow instance ID to cancel.
instance ID.
-ResilienceTimeout
-re
s

createTables
Creates the database tables that store run-time metadata for the workflow. The command creates empty
tables. Identify the service that runs the workflows when you run the command.
Before you create the database tables, verify the following options on the Data Integration Service that runs
the workflows:
The Workflow Orchestration Service module is active on the Data Integration Service.
The Workflow Orchestration Service properties identify the connection for the database that stores the
workflow metadata.
The createTables command uses the following syntax:

createTables
828
The following table describes infacmd wfs createTables options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ServiceName
service_name

the workflows that write metadata to the tables.
ds

-sn
-ResilienceTimeout
-re
createTables
829
dropTables
Drops the database tables that store run-time metadata for the workflow.
The dropTables command uses the following syntax:
dropTables
The following table describes infacmd wfs dropTables options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

precedence.
-dn
-UserName
-un

-Password
Password
-pd
830

Option
Argument
Description
-SecurityDomain
security_domain

case sensitive.
-sdn

-ServiceName
service_name
Required. Name of the service that runs the workflows

for which you want to delete data.
ds

-sn
-ResilienceTimeout
-re
listActiveWorkflowInstances
Lists active workflow instances. An active workflow instance is an instance on which an action can be
performed. Lists the state, workflow instance ID, workflow name, and application name for each active
workflow instance.
Active workflow instances include workflow instances that are running and workflow instances enabled for
recovery that are canceled.
The infacmd wfs listActiveWorkflowInstances command uses the following syntax:
831
The following table describes infacmd wfs listActiveWorkflowInstances options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

running the workflow instances.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

is case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
832
s

listMappingPersistedOutputs
Lists the state of each mapping output that is persisted. You can update the persisted mapping output values
with the infacmd wfs setMappingPersistedOutputs command.
The infacmd wfs listMappingPersistedOutputs command uses the following syntax:
<-MappingTaskInstance|-mti> mapping_task_instance_name
The following table describes infacmd wfs listMappingPersistedOutputs options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

the workflow. The application that contains the
workflow must be deployed to a Data Integration
Service.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
-pd
password

833
Option
Argument
Description
-SecurityDomain
security_domain

is case sensitive.
-sdn

-ResilienceTimeout
-re
s

-Application
application_name

workflow.
workflow_name
Required. Name of the workflow.
MappingTaskInstance
Required. The name of a mapping task that created

the mapping outputs.
-a
-Workflow
-wf
- mti
listWorkflowParams
Lists the parameters for a workflow and creates a parameter file that you can use when you run a workflow.
The command returns an XML file with default values that you can update. Enter the parameter file name
when you run the workflow with infacmd wfs startWorkflow.
The infacmd wfs listWorkflowParams command uses the following syntax:
listWorkflowParams
834
The following table describes infacmd wfs listWorkflowParams options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

Service.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

is case sensitive.
-pd
-SecurityDomain
-sdn

listWorkflowParams
835
Option
Argument
Description
-ResilienceTimeout
-re
s

-Application
application_name

workflow.
workflow_name

-a
-Workflow
-wf
- OutputFile
-o
listWorkflowParams Output
The listWorkflowParams command returns a parameter file as an XML file with default values that you can
update.
For example, you run the listWorkflowParams command on application "MyApp" and workflow "MyWorkflow."
Workflow "MyWorkflow" has one parameter, "MyParameter."
The listWorkflowParams command returns an XML file in the following format:
<?xml version="1.0" encoding="UTF-8"?>
<root xmlns="http://www.informatica.com/Parameterization/1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema"
version="2.0"><!-<application name="MyApp">
<workflow name="MyWorkflow"/>
</application>--><project name="MyProject">
<workflow name="MyWorkflow">
<parameter name="MyParameter">Default</parameter>
</workflow>
</project>
</root>
The output XML file has the following top-level elements:
Application element
When you define a parameter within the application top-level element, the Data Integration Service
applies the parameter value when you run the specified workflow in the specified application. You must
include at least one project element within an application/workflow element.
By default, this top-level element is in comments. Remove the comments (!-- and -->) to use this
element.
Project element
When you define a parameter within a project top-level element, the Data Integration Service applies the
parameter value to the specified workflow in the project in any deployed application. The service also
applies the parameter value to any workflow that uses the objects in the project.
If you define the same parameter in a project and an application top-level element in the same parameter file,
the parameter value defined in the application element takes precedence.
836
listWorkflows
Lists the workflows in an application.
The infacmd wfs listWorkflows command uses the following syntax:
listWorkflows
The following table describes infacmd wfs listWorkflows options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

the workflows. The application that contains the
workflows must be deployed to a Data Integration
Service.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
-pd
password

listWorkflows
837
Option
Argument
Description
-SecurityDomain
security_domain

is case sensitive.
-sdn

-ResilienceTimeout
-re
s

the resilience timeout period with both these methods,
-Application
application_name

workflows.
-a
recoverWorkflow
Recovers a workflow instance. You can recover a workflow instance that you canceled or that was interrupted
by a recoverable error. When you recover a workflow instance, the Data Integration Service restarts the
workflow instance at the task that was interrupted and reruns the interrupted task.
The infacmd wfs recoverWorkflow command uses the following syntax:
recoverWorkflow
<-InstanceID|-iid> instance_ID
838
The following table describes infacmd wfs recoverWorkflow options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

ran the original workflow instance.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password
-pd
-InstanceID
-iid
instance ID of the
workflow to be recovered
-Wait
true|false
-w

Required. Workflow instance ID to recover.
instance ID.
workflow instance to recover before returning to the
shell or command prompt. If true, infacmd returns to
the shell or command prompt after the workflow
instance recovers. You cannot run subsequent
commands until the workflow instance recovers. If
false, infacmd returns to the shell or command prompt
immediately. You do not have to wait for the workflow
instance to recover before running the next command.
Default is false.
recoverWorkflow
839
Option
Argument
Description
-SecurityDomain
security_domain

is case sensitive.
-sdn

-ResilienceTimeout
-re
s

setMappingPersistedOutputs
Updates the persisted mapping outputs for a Mapping task instance in a workflow. Or, sets the persisted
mapping outputs to null values. The command options specify the Mapping task instance name, the
application name, and the workflow name.
To update a value, enter a name-value pair that contains the mapping output name and the value to change it
to. To reset a persisted value to null values, use the reset option. You can reset some of the mapping outputs
or you can reset all of the mapping outputs for a Mapping task instance. To view persisted mapping outputs,
use the infacmd listMappingPersistedOutputs command.
The infacmd wfs setMappingPersistedOutputs command uses the following syntax:
840
<-MappingTaskInstance|-mti> mapping_task_instance_name]
<-outputValues|-onvp> space_separated_output_value_pairs
[<-resetOutputs |-reset> reset_outputs]
The following table describes infacmd wfs setMappingPersistedOutputs options and arguments:
Option
Argument
Description
-DomainName
domain_name

takes precedence.
service_name

Service.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

installation.
841
Option
Argument
Description
-ResilienceTimeout
-re
ds

-Application
application_name

workflow.
workflow_name
mappingTaskInstancena
me
Required. The name of a mapping task that created

the mapping outputs.
-onvp
space_separated_output
_value_pairs
Optional. Changes the persisted value of specific

mapping outputs. Enter space-separated name-value
pairs in the following syntax: output_name=value
output2_name=value output3_name=value
-ResetOutputs
reset_outputs
Optional. Removes the mapping output value from the

repository. To reset specific mapping outputs, enter
the reset option with mapping output names separated
by spaces in the following syntax:
-a
-Workflow
-wf
-MappingTaskInstance
-mti
-outputvalues
-reset
-reset mapping_output_name mapping_output2_name

mapping_output3_name
startWorkflow
Starts an instance of a workflow. You can run multiple instances of a workflow at the same time. You can use
a parameter file for the workflow or a parameter set.
The infacmd wfs startWorkflow command uses the following syntax:
startWorkflow
842
[<-ParameterFile|-pf> parameter file path]

[<-ParameterSet|-ps> ParameterSet name. Both ParameterFile and ParameterSet should not
be given]
The command returns the workflow instance ID.
The following table describes infacmd wfs startWorkflow options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

Service.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
password

security_domain

is case sensitive.
-pd
-SecurityDomain
-sdn

startWorkflow
843
Option
Argument
Description
-ResilienceTimeout
-re
s

-Application
application_name

workflow.
workflow_name
Required. Name of the workflow to start.
true|false

workflow instance to complete before returning to the
instance completes. You cannot run subsequent
commands until the workflow instance completes. If
instance to complete before running the next
command. Default is false.
-a
-Workflow
-wf
-Wait
-w
-ParameterFile
parameter file path
-pf
Optional. Name and path of the parameter file.

Do not enter a parameter file name and a parameter
set name in the same command.
-ParameterSet
parameter set
-ps
Optional. Name of parameter set to use at run time.

The parameter set option overrides any parameter set
deployed with the application.
Do not enter a parameter file name and a parameter
set name in the same command.
upgradeParameterFile
Upgrades the values in a parameter file to verify that the parameter values in the file are valid in the current
release. When you run the command, you identify a parameter file to upgrade and you specify a target file to
contain the valid parameter values.
The infacmd wfs upgradeParameterFile command uses the following syntax:
844
<-ParameterFile|-pf> parameter file path
<-TargetOutputFile|-of> output_file_path
The following table describes infacmd wfs upgradeParameterFile options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

Service.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

-Password
-pd
password

845
Option
Argument
Description
-SecurityDomain
security_domain

is case sensitive.
-sdn

-ResilienceTimeout
-re
s

-Application
application_name

workflow.
workflow_name
Required. Name of the workflow that reads the values

parameter file.
true|false

workflow instance to complete before returning to the
instance completes. You cannot run subsequent
commands until the workflow instance completes. If
instance to complete before running the next
command. Default is false.
parameter file path
Required. Name and location of the parameter file

that contains the values to upgrade.
parameter file path
Required. Name and location of the output file from

the command. The output file contains the valid
parameters for the current release.
-a
-Workflow
-wf
-Wait
-w
-ParameterFile
-pf
-TargetOutputFile
-of
846
CHAPTER 26
infacmd ws Command Reference

ListOperationOptions, 847
ListOperationPermissions, 849
ListWebServiceOptions, 851
ListWebServicePermissions, 852
ListWebServices, 854
RenameWebService, 855
SetOperationPermissions, 857
SetWebServicePermissions, 860
StartWebService, 863
StopWebService, 865
UpdateOperationOptions, 866
UpdateWebServiceOptions, 868
ListOperationOptions
Lists the properties of a web service operation that is deployed to a Data Integration Service.
The infacmd ws ListOperationOptions command uses the following syntax:
<-WebService|-ws> web_service
<-Operation|-op> operation
847
The following table describes infacmd ws ListOperationOptions options and arguments:

Option
Argument
Description
-DomainName
domain_name

service_name

web service is deployed.
user_name

-dn
-ServiceName
-sn
-UserName
-un

sign-on.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
onds

takes precedence.
-WebService
web_service
Required. Name of the web service.
operation
Required. Name of the web service operation to list

properties for.
-ws
Operation
-op
848
Chapter 26: infacmd ws Command Reference
ListOperationPermissions
Lists user and group permissions for a web service operation. You must indicate direct or effective
permissions.
The infacmd ws ListOperationPermissions command uses the following syntax:
<<-Direct> direct_permission_only|<-Effective> effective_permission_only
The following table describes infacmd ws ListOperationPermissions options and arguments:
Option
Argument
Description
-DomainName
domain_name

variable INFA_DEFAULT_DOMAIN. If you
set a domain name with both methods,
the -dn option takes precedence.
service_name
Required. Name of the Data Integration

Service where the web service is
deployed.
user_name

-dn
-ServiceName
-sn
-UserName
-un

849
Option
Argument
Description
-Password
password

precedence.
security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

-ResilienceTimeout

precedence.
web_service
operation
Required. Name of the web service

operation to list properties for.
-Direct or
direct_permission_only
-Effective
effective_permission_only
Required. Enter Direct to list assigned

permissions. Enter Effective to list
-re
-WebService
-ws
-Operation
-op
850
ListWebServiceOptions
List the properties of a web service that is deployed to a Data Integration Service. You can configure the
properties using the Administrator tool or infacmd ws UpdateWebServiceOptions.
The infacmd ws ListWebServiceOptions command uses the following syntax:
The following table describes infacmd ws ListWebServiceOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

user_name

-dn
-ServiceName
-sn
-UserName
-un

sign-on.
-Password
-pd
password
851
Option
Argument
Description
-SecurityDomain
security_domain

-sdn

-ResilienceTimeout
-re
onds

takes precedence.
-WebService
web_service
-ws
ListWebServicePermissions
Lists group and user permissions for a web service that is deployed to a Data Integration Service. You must
indicate direct or effective permissions.
The following table describes infacmd ws ListWebServicePermissions options and arguments:
<<-Direct> direct_permission_only|<-Effective> effective_permission_only
852
The following table describes infacmd ws ListWebServicePermissions options and arguments:

Option
Argument
Description
-DomainName
domain_name

variable INFA_DEFAULT_DOMAIN. If you
set a domain name with both methods,
the -dn option takes precedence.
service_name
Required. Name of the Data Integration

Service where the web service is
deployed.
user_name

-dn
-ServiceName
-sn
-UserName
-un

-Password
password

precedence.
security_domain

case sensitive.
-pd
-SecurityDomain
-sdn

853
Option
Argument
Description
-ResilienceTimeout

precedence.
web_service
-Direct or
direct_permission_only
-Effective
effective_permission_only
Required. Enter Direct to list assigned

permissions. Enter Effective to list
-re
-WebService
-ws
ListWebServices
Lists the web services for an application. If you do not enter an application name, infacmd lists all the web
services for a Data Integration Service.
The infacmd ws ListWebServices command uses the following syntax:
ListWebServices
The following table describes infacmd ws ListWebServices options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

web services are deployed.
-dn
-ServiceName
-sn
854
Option
Argument
Description
-UserName
user_name

-un

sign-on.
-Password
password
option takes precedence
security_domain

-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
onds

takes precedence.
-application
application
Optional. Name of the application to list web services for.
-ap
RenameWebService
Rename a web service.
The infacmd ws RenameWebService command uses the following syntax:
RenameWebService
RenameWebService
855
The following table describes infacmd ws RenameWebService options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

user_name

-dn
-ServiceName
-sn
-UserName
-un

sign-on.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

856
Option
Argument
Description
-ResilienceTimeout
-re
onds

takes precedence.
-WebService
web_service
new_name
Required. New name for the web service.
-ws
-NewName
-n
SetOperationPermissions
Sets the user or group permissions for a web service operation. You can set permissions or deny
permissions for a user or group.
The infacmd ws SetOperationPermissions command uses the following syntax:
<-GranteeUserName|-gun> grantee_user_name|
<-GranteeGroupName|-ggn> grantee_group_name>
[<-AllowedPermissions|-ap> list_of_allowed_permissions_separated_by_space]
[<-DeniedPermissions|-dp> list_of_denied_permissions_separated_by_space]
857
The following table describes infacmd ws SetOperationPermissions options and arguments:

Option
Argument
Description
-DomainName
domain_name

precedence.
service_name

Integration Service where the web
service is deployed.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

authentication. To run the command
with single sign-on, do not set the user
name. If you set the user name, the
-Password
-pd
858
password

password is case sensitive. You can
set a password with the -pd option or
INFA_DEFAULT_DOMAIN_PASSWOR
D. If you set a password with both
methods, the password set with the -pd
Option
Argument
Description
-SecurityDomain
security_domain

belongs. You can set a security
domain with the -sdn option or the
. If you set a security domain name
with both methods, the -sdn option
takes precedence. The security domain
-sdn

authentication, the default is the LDAP
security domain created during
installation. The name of the security
-ResilienceTimeout

INFA_CLIENT_RESILIENCE_TIMEOU
T. If you set the resilience timeout
period with both methods, the -re
web_service

service.
operation

operation.
grantee_user_name|
Required. User name or group name to

set or deny permissions for.
-re
-WebService
-ws
-Operation
-op
-GranteeUserName|
GranteeGroupName
grantee_group_name
-gun|-ggn
-gsdn

user permissions. Name of the security
859
Option
Argument
Description
-AllowedPermissions
list_of_allowed_permissions_
separated_by_spac e
Required. List of permissions to allow.

Enter any of the following parameters
separated by space:
-ap
- GRANT. Users can grant and revoke

permissions on the operation using the
Administrator tool or using the infacmd
command line program.
- EXECUTE. Users can run the
operation.
-DeniedPermissions
-dp
list_of_denied_permissions_s
eparated_by_space

revoke permissions on the operation.
- EXECUTE. Users cannot run the
operation.
SetWebServicePermissions
Sets user or group permissions for a web service. You can set permissions or deny the permissions for one
user or group.
The infacmd ws SetWebServicePermissions command uses the following syntax:
<-GranteeUserName|-gun> grantee_user_name|
<-GranteeGroupName|-ggn> grantee_group_name>
[<-AllowedPermissions|-ap> list_of_allowed_permissions_separated_by_space]
[<-DeniedPermissions|-dp> list_of_denied_permissions_separated_by_space]
860
The following table describes infacmd ws SetWebServicePermissions options and arguments:

Option
Argument
Description
-DomainName
domain_name

precedence.
service_name

Integration Service where the web
service is deployed.
user_name

precedence.
-dn
-ServiceName
-sn
-UserName
-un

authentication. To run the command
with single sign-on, do not set the user
name. If you set the user name, the
-Password
-pd
password

password is case sensitive. You can
set a password with the -pd option or
INFA_DEFAULT_DOMAIN_PASSWOR
D. If you set a password with both
methods, the password set with the -pd
861
Option
Argument
Description
-SecurityDomain
security_domain

belongs. You can set a security
domain with the -sdn option or the
. If you set a security domain name
with both methods, the -sdn option
takes precedence. The security domain
-sdn

authentication, the default is the LDAP
security domain created during
installation. The name of the security
-ResilienceTimeout

INFA_CLIENT_RESILIENCE_TIMEOU
T. If you set the resilience timeout
period with both methods, the -re
web_service
grantee_user_name|
Required. User name or group name to

set or deny permissions for.
-re
-WebService
-ws
-GranteeUserName|
GranteeGroupName
grantee_group_name
-gun|-ggn
-gsdn
862

user permissions. Name of the security
Option
Argument
Description
-AllowedPermissions
list_of_allowed_permissions_
separated_by_spac e
Required. List of permissions to allow.

Enter any of the following parameters
separated by space:
-ap
- GRANT. Users can grant and revoke

permissions on the web service using
the Administrator tool or using the
infacmd command line program.
- EXECUTE. Users can run the web
service.
-DeniedPermissions
-dp
list_of_denied_permissions_s
eparated_by_space

revoke permissions on the web
service.
- EXECUTE. Users cannot run the web
service.
StartWebService
Starts a web service that is deployed to a Data Integration Service.
The infacmd ws StartWebService command uses the following syntax:
StartWebService
StartWebService
863
The following table describes infacmd ws StartWebService options and arguments:

Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
onds

takes precedence.
-ServiceName
service_name
Data Integration Service name where the web service is

deployed.
web_service
Required. Name of the web service to start.
-sn
-WebService
-ws
864
StopWebService
Stops a running web service.
The infacmd ws StopWebService command uses the following syntax:
StopWebService
The following table describes infacmd ws StopWebService options and arguments:
Option
Argument
Description
-DomainName
domain_name

user_name

-dn
-UserName
-un

sign-on.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

StopWebService
865
Option
Argument
Description
-ResilienceTimeout
-re
onds

takes precedence.
-ServiceName
service_name
Data Integration Service name where the web service is

deployed.
web_service
Required. Name of the web service service to stop.
-sn
-WebService
-ws
UpdateOperationOptions
Updates properties for a web service operation that is deployed to a Data Integration Service.
The infacmd ws UpdateOperationOptions command uses the following syntax:
The following table describes infacmd ws UpdateOperationOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

-dn
-ServiceName
-sn
866
Option
Argument
Description
-UserName
user_name

-un

sign-on.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

ResilienceTimeou
t
s

takes precedence.
web_service
operation
Required. Name of the web service operation to update.
-re
-WebService
-ws
Operation
-op
-Options
options
-o> options
Enter the web service option in the following format:

Operation Options
Use operation options to update a web service operation. Use the operation options with infacmd ws
UpdateOperationOptions.
867
Enter operation options in the following format:

... -o OperationOptions.option_name=value ...
The following table describes an option for infacmd ws UpdateOperationOptions:
Option
Description
WebServiceOperationOptions.ResultSetCacheExpirationPeriod
Amount of time in milliseconds that the result

set cache is available for use. If set to -1, the
cache never expires. If set to 0, result set
caching is disabled. If you want all caches to
use the same expiration period, purge the
result set cache after you change the expiration
period. Default is 0.
UpdateWebServiceOptions
Update the properties for a web service that is deployed to a Data Integration Service. To view the properties
for the web service you can use infacmd ws ListWebServiceOptions.
The infacmd ws UpdateWebServiceOptions command uses the following syntax:
The following table describes infacmd ws UpdateWebServiceOptions options and arguments:
Option
Argument
Description
-DomainName
domain_name

service_name

-dn
-ServiceName
-sn
868
Option
Argument
Description
-UserName
user_name

-un

sign-on.
-Password
password
security_domain

-pd
-SecurityDomain
-sdn

-ResilienceTimeout
-re
onds

takes precedence.
-WebService
web_service
options
Enter each option separated by a space.
-ws
-Options
-o> options
Web Service Options

Use a specific syntax to enter web service options.
Enter web service options in the following format:
869
The following table describes web service options:

Option
Description
WebServiceOptions.startupType
Determines whether the web service is enabled to run when

the application starts or when you start the web service.
Enter enabled or disabled.
WebServiceOptions.traceLevel
Level of error messages written to the run-time web service

log. Enter one of the following message levels:
-
870
OFF
SEVERE
WARNING
INFO
FINE
FINEST
ALL
WebServiceOptions.requestTimeout
Maximum number of milliseconds that the Data Integration

Service runs an operation mapping before the web service
request times out. Default is 3,600,000.
WebServiceOptions.maxConcurrentRequests
Maximum number of requests that a web service can

process at one time. Default is 10.
WebServiceOptions.sortOrder
Sort order that the Data Integration Service uses to sort and
compare data when running in Unicode mode. Default is
binary.
WebServiceOptions.EnableTransportLayerSecurit
y
Indicates that the web service must use HTTPS. If the Data
Integration Service is not configured to use HTTPS, the web
service will not start. Enter true or false.
WebServiceOptions.EnableWSSecurity
Enables the Data Integration Service to validate the user

credentials and verify that the user has permission to run
each web service operation. Enter true or false.
Option
Description
WebServiceOptions.optimizeLevel
The optimizer level that the Data Integration Service applies

to the object. Enter the numeric value that is associated with
the optimizer level that you want to configure. You can enter
one of the following numeric values:
- 0. The Data Integration Service does not apply optimization.
- 1. The Data Integration Service applies the early projection
optimization method.
- 2. The Data Integration Service applies the early projection,
early selection, push-into, and predicate optimization
methods.
- 3. The Data Integration Service applies the cost-based, early
projection, early selection, push-into, predicate, and semi-join
optimization methods.
WebServiceOptions.DTMKeepAliveTime
Number of milliseconds that the DTM instance stays open

after it completes the last request. Web service requests that
are issued against the same operation can reuse the open
instance. Use the keep alive time to increase performance
when the time required to process the request is small
compared to the initialization time for the DTM instance. If
the request fails, the DTM instance terminates.
Must be an integer. A negative integer value means that the
DTM Keep Alive Time for the Data Integration Service is
used. 0 means that the Data Integration Service does not
keep the DTM instance in memory. Default is -1.
871
CHAPTER 27
infacmd xrf Command Reference

generateReadableViewXML, 872
updateExportXML, 872
generateReadableViewXML
Generates a readable XML file from an export XML file. The export XML file can contain exported domain or
Model repository contents.
The infacmd xrf generateReadableViewXML command uses the following syntax:
<-SourceExportFile|-sxf> source_export_file
<-TargetFile|-tf> target_file_Name
The following table describes infacmd xrf generateReadableViewXML options and arguments:
Option
Argument
Description
-SourceExportFile
source_export_file
Required. Path and file name of the export XML file.
target_file_Name
Required. Path and file name of the readable XML file.
-sxf
-TargetFile
-tf
updateExportXML
Updates an export XML file with the changes made to the corresponding readable XML file. You can update a
readable XML file that contains Model repository contents and regenerate the export XML file with the
changes.
The infacmd xrf updateExportXML command uses the following syntax:
updateExportXML
<SourceExportFile|-sxf> source_file
872
<generatedViewFile|-vf> view_file
<TargetFile|-tf> target_file_Name
The following table describes infacmd xrf updateExportXML options and arguments:
Option
Argument
Description
-SourceExportFile
source_file
Required. Path and file name of the export XML file.
view_file
Required. Path and file name of the readable XML file that
contains the required changes.
target_file_Name
Required. Path and file name of the updated export XML file.
-sxf
-generatedViewFile
-vf
-TargetFile
-tf
updateExportXML
873
CHAPTER 28
infacmd Control Files

infacmd Control Files Overview, 874
Control File Configuration, 874
Export Control Files, 875
Import Control Files, 880
Rules and Guidelines for Control Files, 887
Control File Examples for Domain Objects, 887
Control File Examples for Model Repository Objects, 888
infacmd Control Files Overview

When you use the infacmd command line program to export and import objects, you can use a control file to
filter the objects that the command exports or imports.
You can use the following control files with infacmd:
Export control file. Use an export control file to specify the objects to export from the domain or Model
repository to an export file.
Import control file. Use an import control file to specify the objects to import from the export file into the
domain or Model repository.
If you do not use an export control file during export, infacmd does not filter the objects exported from the
domain or the specified Model repository project. If you do not use an import control file during import into the
domain, infacmd imports all objects included in the export file. If you do not use an import control file during
import into the Model repository, infacmd imports all objects included in the specified project in the export file.
Control File Configuration

A control file is an XML file based on an export or import schema file. You can create a control file based on
the following schema files:
exportControl.xsd. Defines the layout and syntax of export control files.
importControl.xsd. Defines the layout and syntax of import control files.
You can access the schema files as part of the oie-util.jar in the following installation directory:
874
<InformaticaInstallationDir>/services/shared/jars/shapp
To access exportControl.xsd and importControl.xsd from the command line, navigate to the oie-util.jar
location and extract the jar file with the following command:
jar -xvf <jar_name>
Also, you can extract the oie-util jar with decompression software, such as WinRAR, or view the xsd files
from the oie-util jar with the Java decompiler to access the schema files.
To create an export control file, create an XML file based on the exportControl.xsd schema file. The file must
begin with an XML declaration and the location of the hosted schema file in the exportParams root element.
Include the following lines in the file:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<exportParams xmlns="http://www.informatica.com/oie/exportControl/9">
...
</exportParams>
To create an import control file, create an XML file based on the importControl.xsd schema file. The file must
begin with an XML declaration and the location of the hosted schema file in the importParams root element.
Include the following lines in the file:
<importParams xmlns="http://www.informatica.com/oie/importControl/9">
...
</importParams>
Include the remaining elements and attributes in the XML file based on the objects that you want to export or
import.
Control File Naming Conventions

Use an easily distinguishable file name for the control files.
Add a prefix to each file name to indicate whether it is an export or import control file. For example, use the
following suggested naming conventions:
ecf_<file_name>.xml for export control files
icf_<file_name>.xml for import control files
For control files for domain objects, you might also include the object type considered for export or import in
the file name.
Export Control Files

An export control file is an XML file that you use with infacmd commands. The control file filters the objects
that infacmd exports from a domain or Model repository.
You can use an export control file with the following commands:
infacmd isp ExportDomainObjects
Exports native users, native groups, roles, and connections from the domain to an export file in XML
format. When you specify an export control file for the command, you filter the objects that you want to
export. For example, use a control file to export all objects created after a certain date or to export
connections but no other object types.
875
infacmd oie ExportObjects

Exports all Model repository object types from a specified project to an export file in XML format. When
you specify an export control file for the command, you filter the objects that you want to export. For
example, use a control file to export all objects created by a specific user or to export specific object
types in the project.
Infacmd does not export empty folders. When you export Model repository objects, infacmd also exports
the dependent objects. A dependent object is an object that is used by another object. Dependent
objects can be in the same or different projects.
An export control file uses different parameters based on whether you configure the file to export domain
objects or Model repository objects.
Export Control File Parameters for Domain Objects

Use the export control file parameters to configure the objects that you want to export from the domain.
An export control file for domain objects can contain the following elements:
exportParams. Can contain multiple objectList elements.
objectList. Contains attributes to filter objects by type. Can contain multiple object elements.
object. Contains an attribute to filter objects by name.
The following table lists the export control file elements that have configurable attributes:
Element
Attribute Name
Attribute Description
objectList
type
Required. Type of domain object to export. Specify one of the following

values:
-
User
Group
Role
Connection
The value is not case sensitive.

objectList
createdBefore
Optional. Date and time. Exports objects of the specified type created
before this date and time. Enter the date and time in the following format:
yyyy-MM-dd HH:mm:ssZ
objectList
createdAfter
Optional. Date and time. Exports objects of the specified type created
after this date and time. Enter the date and time in the following format:
objectList
lastUpdatedBefo
re
Optional. Date and time. Exports objects of the specified type updated
before this date and time. Enter the date and time in the following format:
876
Chapter 28: infacmd Control Files
Element
Attribute Name
objectList
lastUpdatedAfter
Optional. Date and time. Exports objects of the specified type updated
after this date and time. Enter the date and time in the following format:
object
name
Required. Name of the object to export. If the containing objectList

element includes a time attribute, infacmd exports objects that match
both the specified object name and the time filter. The value is not case
sensitive.
Export Control File Sample for Domain Objects

The following code shows an example export control file for domain objects:

<objectList type="connection" >
<object name="connection1" />
</objectList>

<objectList type="group" createdBefore="2010-11-12 10:00:00 +0530" />

<objectList type="role" createdAfter="2010-12-25 10:00:00 +0530">
<object name="role1" />
<object name="role2" />
</objectList>

<objectList type="user" />
</exportParams>
Export Control File Parameters for Model Repository Objects

Use the export control file parameters to configure the objects that you want to export from the Model
repository.
An export control file for Model repository objects can contain the following elements:
exportParams. Can contain a single folders element.
folders. Can contain multiple folder elements.
folder. Contains attributes to filter objects in a specific folder. Can contain multiple objectList elements.
object. Contains an attribute to filter objects by name.
877
The following table describes the configurable attributes for the folder element in the export control file:
Attribute Name
path
Optional. Path of the folder that contains the objects you want to export. Use the following
format:
"/<folder_name>/<folder_name>"
For example, if a project contains a folder named F1, then the folder path of F1 is "/F1." To
export all objects in the project, specify "/." The value is not case sensitive. Default is "/."
recursive
Optional. Indicates whether to export objects from subfolders of the specified folder. Set to
true to export from subfolders. Valid values are true and false. The value is case sensitive.
Default is true.
select
Optional. Indicates whether infacmd exports all remaining objects in the specified folder when
you define an objectList element for the folder. Set to all to export all remaining objects. For
example, the following lines export mappings that were created by user1. The lines export all
remaining objects in the specified folder:
<folder path="/Testfolder" select="all">
<objectList type="Mapping" createdBy="user1" />
</folder>
If you define an objectList element and do not use the select attribute, then infacmd exports
objects that satisfy the attributes defined in objectList. For example, the following lines export
mappings that were created by user1 in the specified folder:
<folder path="/Testfolder">
</folder>
If you do not define an objectList element for the folder, then the default value of the select
attribute is all. For example, the following line exports all objects in the specified folder:
<folder path="/Testfolder" />
Valid value is all.
createdBy
Optional. User name. Exports objects created by this user. The value is not case sensitive.
createdBefore
Optional. Date and time. Exports objects created before this date and time. Enter the date
and time in the following format:
createdAfter
Optional. Date and time. Exports objects created after this date and time. Enter the date and
time in the following format:
lastUpdatedBefo
re
Optional. Date and time. Exports objects updated before this date and time. Enter the date
and time in the following format:
lastUpdatedAfter
Optional. Date and time. Exports objects updated after this date and time. Enter the date and
time in the following format:
lastUpdatedBy
878
Optional. User name. Exports objects that were last updated by this user. The value is not
case sensitive.
The following table describes the configurable attributes for the objectList element in the export control file:
Attribute Name
type
Required. Type of Model repository object to export from the specified folder path. Valid
values include all object types present in the Model repository. You can view the type of the
object in the Properties view in the Developer tool. For example, you can enter "Relational
Data Object" or "Profile." The value is not case sensitive.
createdBy
Optional. User name. Exports objects of the specified type created by this user. The value is
not case sensitive.
createdBefore
Optional. Date and time. Exports objects of the specified type created before this date and
time. Enter the date and time in the following format:
createdAfter
Optional. Date and time. Exports objects of the specified type created after this date and time.
Enter the date and time in the following format:
lastUpdatedBefo
re
Optional. Date and time. Exports objects of the specified type updated before this date and
lastUpdatedAfter
Optional. Date and time. Exports objects of the specified type updated after this date and
lastUpdatedBy
Optional. User name. Exports objects of the specified type that were last updated by this user.
The following table describes the configurable attribute for the object element in the export control file:
Attribute Name
name
Required. Name of the object to export. If the containing objectList element includes a user or
time attribute, infacmd exports objects that match both the specified object name and the user
or time filter. The value is case sensitive.
Export Control File Sample for Model Repository Objects

The following code shows an example export control file for Model repository objects:
<folders>
>

<objectList type="Mapping" createdBy="user1">
<object name="mapping1"/>

</objectList>
879


<objectList type="Aggregator" createdBy="user1" />

</folder>
</folders>
</exportParams>
Import Control Files

An import control file is an XML file that you use with infacmd commands. The control file filters the objects
that infacmd imports from an export file into a domain or Model repository.
You can use an import control file with the following commands:
infacmd isp ImportDomainObjects
Imports native users, native groups, roles, and connections from an export file into a domain. When you
specify an import control file for the command, you can complete the following tasks:
Filter the objects that you want to import. For example, use the control file to import a specific object
type.
Configure conflict resolution strategies for specific object types or objects.
infacmd oie ImportObjects

Imports Model repository objects from an export file into a Model repository. When you specify an import
control file for the command, you can complete the following tasks:
Filter the objects that you want to import. For example, use the control file to import a specific object
type.
Configure conflict resolution strategies for specific object types or objects.
Map connections in the source repository to connections in the target repository.
Dependent Model repository objects may exist in different folders or projects. You must include all
dependent objects using folderMap elements in the import control file. Otherwise, the import might fail
with an error message because a dependent object does not exist in the target repository.
You can define a conflict resolution strategy through the command line or control file when you import the
objects. The control file takes precedence if you define conflict resolution in the command line and control
file. The import fails if there is a conflict and you did not define a conflict resolution strategy.
If you define the rename conflict resolution strategy, you can specify a name in the control file for a specific
object. Or, infacmd can generate a name by appending a sequential number to the end of the name.
An import control file uses different parameters based on whether you configure the file to import domain
objects or Model repository objects.
Import Control File Parameters for Domain Objects

Use the import control file parameters to configure the objects that you want to import from an XML file into
the domain.
An import control file for domain objects can contain the following elements:
880
importParams. Can contain multiple objectList elements.
objectList. Contains attributes to filter the objects by type. Can contain multiple object elements.
object. Contains attributes to filter the objects by name.
The following table lists the import control file elements that have configurable attributes:
Element
Attribute Name
objectList
type
Required. Type of domain object that you want to import. Specify one of
-
User
Group
Role
Connection

objectList
select
Optional. Indicates whether infacmd imports all remaining objects of the

specified type when you define an object element for the objectList. Set
to all to import all remaining objects. For example, the following lines
import Group1 with a Reuse resolution strategy. The lines import all
remaining groups with a Merge resolution strategy:
<objectList type="group" select="all"
resolution="merge">
<object name="Group1" resolution="reuse" />
</objectList>
If you define an object element and do not use the select attribute, then
infacmd imports objects that satisfy the attributes defined in the object
element. For example, the following lines import Group1 with a Merge
resolution strategy:
<objectList type="group" resolution="merge">
<object name="Group1" />
</objectList>
If you do not define an object element for the objectList, then the default
value of the select attribute is all. For example, the following line imports
all groups with a Merge resolution strategy:
<objectList type="group" resolution="merge" />
Valid value is all.
objectList
resolution
Optional. Resolution strategy when a name conflict occurs. Applies to all

objects of the specified type. Specify one of the following values:
- Replace. Replace target object with the source object.
- Rename. Rename source object using a generated name, and then import
it.
- Reuse. Reuse object in the target domain.
- Merge. Merge the objects into one object. This option is applicable for
groups.
The values are not case sensitive.

object
name
Required. Name of a specific object to import of the specified object type.

881
Element
Attribute Name
object
resolution
Optional. Resolution strategy when a name conflict occurs for this object.
Specify one of the following values:
-
Replace. Replace target object with the source object.

Rename. Rename source object, and then import it.
Reuse. Reuse object in the target domain.
Merge. Merge the objects into one object. This option is applicable for
groups.
The values are not case sensitive.

object
renameTo
Optional. Name to use when the conflict resolution strategy is Rename. If

you do not specify a name, then infacmd generates a name by appending
a number to the end of the name. Infacmd ignores the value if there are
no conflicts or if the conflict resolution strategy is not Rename.
object
renameIdTo
Optional. ID string to use when you import a connection object and the
conflict resolution strategy is Rename. If you do not specify a connection
ID, then infacmd generates an ID by appending a number to the end of
the connection ID. Infacmd ignores the value if there are no conflicts or if
the conflict resolution strategy is not Rename.
Import Control File Sample for Domain Objects

The following code shows an example import control file for domain objects:
<! -- Import all connections, roles, and users. -->
<objectList type="connection" resolution="replace" />
<objectList type="role" resolution="reuse" />
<objectList type="user" resolution="rename" />
<! -- Import specific groups. -->
<objectList type="group">
<object name="g1" resolution="replace" />
<object name="g2" resolution="merge" />
</objectList>
</importParams>
Import Control File Parameters for Model Repository Objects

Use the import control file parameters to configure the objects that you want to import from an XML file into
the Model repository.
An import control file for Model repository objects can contain the following elements:
882
importParams. Can contain a single folderMaps element and a single connectionInfo element.
folderMaps. Can contain multiple folderMap elements.
folderMap. Contains attributes to filter objects in a specific folder. Can contain multiple objectList
elements.
object. Contains attributes to filter objects by name.
connectionInfo. Can contain a single rebindMap element.
rebindMap. Can contain multiple rebind elements.
rebind. Contains attributes to map connections in the source repository to connections in the target
repository.
The following table describes the configurable attributes for the folderMap element in the import control file:
Attribute Name
sourceProject
Required. Name of the source project in the export file that contains the objects you want to
import. The value is not case sensitive.
sourceFolderPath
Optional. Path of the source folder in the export file that contains the objects you want to
import. Use the following format:
consider importing all objects in the project, specify "/." The value is not case sensitive.
Default is "/."
targetProject
Required. Name of the project in the target repository into which you want to import objects.
The project must exist in the repository before you import the objects. The value is not case
sensitive.
targetFolderPath
Optional. Path of the folder in the target repository into which you want to import objects.
import all objects into the target project, specify "/." The folder must exist in the repository
before you import the objects. The value is not case sensitive. Default is "/."
recursive
Optional. Indicates whether to import objects from subfolders of the specified folder. Set to
true to import from subfolders. Valid values are true and false. The value is case sensitive.
Default is true.
883
Attribute Name
select
Optional. Indicates whether infacmd imports all remaining objects in the specified project
when you define an objectList element for the folderMap. Set to all to import all remaining
objects. For example, the following lines import mappings with a Reuse resolution strategy.
The lines import all remaining objects with a Replace resolution strategy:
<folderMap sourceProject="p1" targetProject="p2" select="all"
resolution="replace">
<objectList type="Mapping" resolution="reuse" />
</folderMap>
If you define an objectList element and do not use the select attribute, then infacmd imports
objects that satisfy the attributes defined in objectList. For example, the following lines
import mappings with a Replace resolution strategy:
<folderMap sourceProject="p1" targetProject="p2"
resolution="replace">
<objectList type="Mapping" />
</folderMap>
If you do not define an objectList element for the folderMap, then the default value is all. For
example, the following line imports all objects with a Replace resolution strategy:
<folderMap sourceProject="p1" targetProject="p2"
resolution="replace" />
Valid value is all.
resolution
Optional. Resolution strategy when a name conflict occurs. Applies to all objects in this
folder. Specify one of the following values:
-
Rename. Rename source object using a generated name, and then import it.
Reuse. Reuse object in the target Model repository.
None.
The values are not case sensitive. Default is none.
884
The following table describes the configurable attributes for the objectList element in the import control file:
Attribute Name
type
Required. Type of Model repository object to import to the specified folder path. Valid values
include all object types present in the Model repository. You can view the type of the object
in the Properties view in the Developer tool. For example, you can enter "Relational Data
Object" or "Profile." The value is not case sensitive.
select
Optional. Indicates whether infacmd imports all remaining objects of the specified type when
you define an object element for the objectList. Set to all to import all remaining objects. For
example, the following lines import MyMapping with a Reuse resolution strategy. The lines
import all remaining mappings with a Replace resolution strategy:
<folderMap sourceProject="p1" targetProject="p2">
<objectList type="Mapping" select="all" resolution="replace">
<object name="MyMapping" resolution="reuse" />
</objectList>
</folderMap>
If you define an object element and do not use the select attribute, then infacmd imports
objects that satisfy the attributes defined in the object element. For example, the following
lines import the mapping named MyMapping with a Replace resolution strategy:
<objectList type="Mapping" resolution="replace">
<object name="MyMapping"/>
</objectList>
</folderMap>
If you do not define an object element for the objectList, then the default value is all. For
example, the following lines import all mappings with a Replace resolution strategy:
<objectList type="Mapping" resolution="replace" />
</folderMap>
Valid value is all.
resolution
Optional. Resolution strategy when a name conflict occurs. Applies to all objects of the
specified type. Specify one of the following values:
-
Rename. Rename source object using a generated name, and then import it.
None.

The following table describes the configurable attributes for the object element in the import control file:
Attribute Name
name
Required. Name of a specific object to import of the specified object type. The value is not
case sensitive.
resolution
Optional. Resolution strategy when a name conflict occurs for this object. Specify one of the
following values:
-
Rename. Rename source object, and then import it.

None.
885
Attribute Name
renameTo
Optional. Name to use when the conflict resolution strategy is Rename. If you do not
specify a name, then infacmd generates a name by appending a number to the end of the
name. Infacmd ignores the value if there are no conflicts or if the conflict resolution strategy
is not Rename.
renameIdTo
Optional. ID string to use when you import a connection object and the conflict resolution
strategy is Rename. If you do not specify a connection ID, then infacmd generates an ID by
appending a number to the end of the connection ID. Infacmd ignores the value if there are
no conflicts or if the conflict resolution strategy is not Rename.
The following table describes the configurable attributes for the rebind element in the import control file:
Attribute Name
source
Required. Name of a source connection in the file that you are importing. The value is not
case sensitive.
target
Required. Name of a connection in the target Model repository to map to the source
connection. By default, the connection must exist in the target repository before you import
the objects. If the connection does not exist, the import fails. When you run infacmd, you
can choose to skip target connection validation during the import. When you skip target
connection validation, the import succeeds if a connection does not exist in the target
repository. The value is not case sensitive.
Import Control File Sample for Model Repository Objects

The following code shows an example import control file for Model Repository objects:
<folderMaps>
<folderMap sourceProject="project1" sourceFolderPath="/f1" targetProject="project2"
targetFolderPath="/f1" recursive="true">
<! -- Import mapping1 with the Rename resolution strategy. -->
<objectList type="Mapping" select="all" resolution="replace">
<object name="mapping1" resolution="rename" renameTo="mapping1_new"/>
<! -- Import all remaining mappings with the Replace resolution strategy. -->
</objectList>
>
<! -- Import all Aggregator transformations with the Replace resolution strategy. -<objectList type="Aggregator" resolution="replace"/>
<! -- Import all Filter transformations with no resolution strategy. -->
<objectList type="Filter" resolution="none"/>
</folderMap>
</folderMaps>
<! -- Map connections in the source repository to connections in the target

repository. -->
<connectionInfo>
<rebindMap>
<rebind source="src_Conn1" target="tgt_Conn1"/>
<rebind source="src_Conn2" target="tgt_Conn2"/>
</rebindMap>
</connectionInfo>
</importParams>
886
Rules and Guidelines for Control Files

Review the following rules and guidelines before you create control files:
Element and attribute names are case sensitive.
Control files contain a hierarchy of XML elements. Elements at different levels can contain the same
attribute. A child element inherits an attribute value defined for the parent element when the same
attribute is not defined for the child element. The attribute values defined for a child element override the
value of the same attribute defined for the parent element.
When an element defines multiple attributes, infacmd exports or imports objects that match all attribute
filters. For example, you define the createdBefore and lastUpdatedAfter attributes for an objectList
element in an export control file. Infacmd exports objects of the specified type created before the specified
date and last updated after the specified date.
The values of time attributes are not inclusive. For example, you set createdAfter to 2011-02-01
16:00:00-0800 in an export control file. Infacmd considers exporting all objects created after 4 p.m. on
February 1, 2011. Infacmd does not export objects created at 4 p.m. on February 1, 2011.
You can specify an objectList of a specific type once in a control file for domain objects. For example, you
specify an objectList where type is "connection." You cannot specify another objectList of type
"connection" in the same file.
You can specify an objectList of a specific type once in a folder or folderMap element for Model repository
objects. For example, you specify an objectList where type is "Flat File Data Object." You cannot specify
another objectList of the "Flat File Data Object" type in the same folder or folderMap element.
Control File Examples for Domain Objects

You can filter domain objects to export by time. You can filter domain objects to export and import by object
type or object name.
Export Domain Objects by Time
To export users created after 2010-12-25 10:00:00 +0530, you might create the following control file:
<objectList type="user" createdAfter="2010-12-25 10:00:00 +0530" />
</exportParams>
Export and Import Domain Objects by Type
To export all users, groups, and roles but not connections from a domain, you might create the following
control file:
<objectList type="group"/>
<objectList type="role" />
</exportParams>
To import the users and groups but not roles into the target domain, you might create the following
control file:
<objectList type="group" resolution="merge"/>
Rules and Guidelines for Control Files
887
<objectList type="user" resolution="replace" />

</importParams>
Export and Import Domain Objects by Name
You want to export all users and groups and the Developer and Analyst roles from the source domain.
You want to export specific connections if they were created after 2011-02-01 16:00:00-0800. You might
create the following control file:
<objectList type="group"/>
<objectList type="role">
<object name="Developer" />
<object name="Analyst" />
</objectList>
<objectList type="connection" createdAfter="2011-02-01 16:00:00-0800">
<object name="Connection1" />
</objectList>
</exportParams>
To import all users and groups and specific roles and connections into the target domain, you might
<objectList type="group" resolution="reuse" />
<objectList type="user" resolution="reuse" />
<objectList type="role">
<object name="Developer" resolution="replace" />
<object name="Analyst" resolution="replace" />
</objectList>
<objectList type="connection">
<object name="Connection1" resolution="rename" renameTo="ProdConnection1" />
</objectList>
</importParams>
Control File Examples for Model Repository Objects

You can filter the export of Model repository objects by time or user. You can filter the export or import of
Model repository objects by object type or object name.
Export Model Repository Objects by Time
To export all objects in a folder named Folder1 that were created before 2011-02-01 16:00:00-0800, you
might create the following control file:
<folders>
<folder path="/Folder1" createdBefore="2011-02-01 16:00:00-0800" />
</folders>
</exportParams>
888
Export Model Repository Objects by User

To export all objects in the project last updated by Administrator, you might create the following control
file:
<folders>
<folder lastUpdatedBy="Administrator" />
</folders>
</exportParams>
Export and Import Model Repository Objects by Type
To export all mappings from a folder named Folder1, you might create the following control file:
<folders>
<folder path="/Folder1" />
</folder>
</folders>
</exportParams>
You want to export all mappings created by user2 and export all remaining objects created by user1. The
createdBy attribute defined for the child objectList element overrides the same attribute defined for the
parent folder element. You might create the following control file:
<folders>
<folder path="/Folder1" select="all" createdBy="user1" />
</folder>
</folders>
</exportParams>
You want to import all mappings from the export file. Some of the mappings exported from Folder1
contain dependent objects that existed in Folder2 in the source repository. To import dependent objects,
you must include all dependent objects using folderMap elements in the import control file. You also
want to map the connections in the source repository to connections in the target repository. You might
<folderMaps>
<folderMap sourceProject="DevProject" sourceFolderpath="/Folder1"
targetProject="TestProject" targetFolderPath="/TestFolder1" resolution="reuse">
</folderMap>
<folderMap sourceProject="DevProject" sourceFolderpath="/Folder2"
targetProject="TestProject" targetFolderPath="/TestFolder2" resolution="reuse" />
</folderMaps>
<connectionInfo>
<rebindMap>
<rebind source="src_connection1" target="tgt_connection1" />
<rebind source="src_connection2" target="tgt_connection2" />
</rebindMap>
</connectionInfo>
</importParams>
Export and Import Model Repository Objects by Name
You want to export a mapping named TestMapping that was created after 2010-11-11 23:59:59-0800.
You want to export all remaining objects in the same folder. You might create the following control file:
<folders>
Control File Examples for Model Repository Objects
889
<folder path="/Folder1" select="all" />

<objectList type="Mapping" createdAfter="2010-11-11 23:59:59-0800" >
<object name="TestMapping" />
</objectList>
</folder>
</folders>
</exportParams>
An export file contains flat file and relational data objects. You want to import the flat file data object
named NewFlatFileDataObject and all relational data objects from the export file. You might create the
following control file:
<folderMaps>
<folderMap sourceProject="SampleProject" targetProject="SampleProject"
targetFolderPath="/TestFolder">
<objectList type="Flat File Data Object" resolution="replace" >
<object name="NewFlatFileDataObject" />
</objectList>
<objectList type="Relational Data Object" resolution="replace" />
</folderMap>
</folderMaps>
</importParams>
890
CHAPTER 29
infasetup Command Reference

Using infasetup, 891
BackupDomain, 893
DefineDomain, 895
DefineGatewayNode, 906
DefineWorkerNode, 912
DeleteDomain, 915
GenerateEncryptionKey, 918
Help, 918
MigrateEncryptionKey, 919
RestoreDomain, 920
SwitchToKerberosMode, 922
UpdateGatewayNode, 923
UpdateKerberosAdminUser, 928
UpdateKerberosConfig, 928
UpdateWorkerNode, 929
UnlockUser, 931
ValidateandRegisterFeature, 932
Using infasetup
infasetup is a command line program that you use to administer PowerCenter domains and nodes.
Use infasetup to modify domain and node properties after you install PowerCenter Services with the
PowerCenter installation program. For example, you can use infasetup to change the port number for a node
after you install PowerCenter Services.
You can use infasetup to back up, restore, define, and delete domains, and to define and update nodes.
891
Running Commands
You invoke infasetup from the command line. You can issue commands directly or from a script, batch file, or
other program. On Windows, infasetup is a batch file with a .bat extension. On UNIX, infasetup is a script file
with a .sh extension.
To run infasetup commands:
1.
Open a command prompt.

On Windows, open the command prompt as administrator. If you do not open the command prompt as
administrator, the Windows system administrator might encounter issues when accessing files in the
2.
At the command prompt, switch to the directory where the infasetup executable is located.
By default, infasetup installs in the <InformaticaInstallationDir>/isp/bin directory.
3.
Enter infasetup on Windows or infasetup.sh on UNIX followed by the command name and its required
options and arguments. The command names are not case sensitive.
For example:
infasetup(.sh) command_name [-option1] argument_1 [-option2] argument_2...
Command Options
When you run infasetup, you enter options for each command, followed by the required arguments.
Command options are preceded by a hyphen and are not case sensitive. Arguments follow the option.
For example, the following command updates a worker node with the name Node1 and the address
Host1:9090:
infasetup UpdateWorkerNode -nn Node1 -na Host1:9090
If you omit or incorrectly enter one of the required options, the command fails, and infasetup returns an error
message.
infasetup Return Codes

infasetup indicates the success or failure of a command with a return code. Return code (0) indicates that the
command succeeded. Return code (-1) indicates that the command failed.
Use the DOS or UNIX echo command immediately after running an infasetup command to see the return
code for the command:
Using Database Connection Strings

Some infasetup commands use connection strings to connect to the domain configuration database. Specify
the database host, database port, and database service name as part of the connection string.
You can use connection strings with the following infasetup commands:
892
BackupDomain
DefineDomain
DefineGatewayNode
Chapter 29: infasetup Command Reference
DeleteDomain
RestoreDomain
UpdateGatewayNode
The following table lists the connection string syntax for each supported database:
Database Name
Connection String
Oracle
Oracle:
jdbc:informatica:oracle://host_name:port;SID=sid
Oracle RAC:
jdbc:informatica:oracle://host_name:port;
ServiceName=[Service
Name];AlternateServers=(server2:port);LoadBalancing=true
Microsoft SQL Server
jdbc:informatica:sqlserver://host_name:port;
SelectMethod=cursor;DatabaseName=database_name
IBM DB2
jdbc:informatica:db2://host_name:port;
DatabaseName=database_name
BackupDomain
Backs up the configuration metadata for the domain. infasetup stores the backup domain metadata in a
backup file with an extension of .mrep.
When you run this command, infasetup backs up the domain configuration database tables. To restore the
domain to another database, you must back up the ISP_RUN_LOG table contents manually to get the
previous workflow and session logs.
If the command fails with a Java memory error, increase the system memory available for infasetup. To
increase the system memory, set the -Xmx value in the INFA_JAVA_CMD_OPTS environment variable.
The BackupDomain command uses the following syntax:
BackupDomain
<<-DatabaseAddress|-da> database_hostname:database_port|
<-DatabaseConnectionString|-cs> database_connection_string>
[<-DatabaseUserName|-du> database_user_name]
[<-DatabasePassword|-dp> database_password]
<-DatabaseType|-dt> database_type
[<-DatabaseServiceName|-ds> database_service_name]
<-BackupFile|-bf> backup_file_name
[<-Force|-f> overwrite_file]
[<-Tablespace|-ts> tablespace_name]
[<-SchemaName|-sc> schema_name (used for Microsoft SQL Server only)]
BackupDomain
893
[<-DatabaseTlsEnabled|-dbtls> database_tls_enabled]
[<-TrustedConnection|-tc> trusted_connection (used for Microsoft SQL Server only)]
[<-EncryptionKeyLocation|-kl> encryption_key_location]
The following table describes infasetup BackupDomain options and arguments:
Option
Argument
Description
-DatabaseAddress
database_hostname:d
atabase_port
Required if you do not use -DatabaseConnectionString

(-cs) option. Name and port number of the machine
hosting the domain configuration database.
-cs
database_connection_
string
Required if you do not use -DatabaseAddress (-da)

and -DatabaseServiceName (-ds) options. Connection
string used to connect to the domain configuration
database. Specify the database host, database port,
and the database service name as part of the
connection string. Enclose the connection string in
quotes.
-DatabaseUserName
database_user_name
Required if you do not use -TrustedConnection (-tc)

option. Account for the database containing the
domain configuration information.
database_password
Domain configuration database password

corresponding to the database user. If you omit this
option, infasetup uses the password specified in the
environment variable, you must enter a password
using this option.
database_type
Required. Type of database that stores the domain

configuration metadata. Database types include:
-da
-DatabaseConnectionString
-du
-DatabasePassword
-dp
-DatabaseType
-dt
-DatabaseServiceName
-ds
database_service_na
me
Required if you do not use -DatabaseConnectionString

(-cs) option. The database service name. Required for
Oracle, IBM DB2, and Microsoft SQL Server
databases. Enter the SID for Oracle, the service name
for IBM DB2, or the database name for Microsoft SQL
Server.
-BackupFile
backup_file_name
Required. Name and path for the backup file. If you do

not specify a file path, infasetup creates the backup
file in the current directory.
Optional. Overwrites the backup file if a file with the

same name already exists.
-bf
-Force
-f
894
db2
oracle
mssqlserver
sybase
Option
Argument
Description
-DomainName
domain_name
tablespace_name
Required for an IBM DB2 database. Name of the

tablespace where the domain configuration database
tables reside.
schema_name
Optional. Name of the Microsoft SQL Server schema.

Enter a schema name if you are not using the default
schema.
database_tls_enabled
Optional. Indicates whether the Informatica domain

database is secure with TLS or SSL. Set this option to
True for the secure database. Default is false. If you
specify the dbtls option without a value, the
Informatica domain uses secure communication to the
Informatica domain database.
database_truststore_p
assword
Optional. Password for the database truststore file for

the secure database.
Optional. Connect to the Microsoft SQL Server

database through a trusted connection. Trusted
authentication uses the Windows security credentials
of the current user to connect to Microsoft SQL Server.
encryption_key_locatio
n
Directory that contains the current encryption key. The

name of the encryption file is sitekey.
database_truststore_lo
cation
domain repository database. Required if you configure
a secure domain repository database for the domain.
-dn
-Tablespace
-ts
-SchemaName
-sc
-DatabaseTlsEnabled
-dbtls
DatabaseTruststorePasswor
d
-dbtp
-TrustedConnection
-tc
-EncryptionKeyLocation
-kl
-DatabaseTruststoreLocation
-dbtl
DefineDomain
Creates a domain on the current machine. If you define a domain on a machine that hosts a domain, you
must first stop the Informatica services on the machine. infasetup removes the existing domain and node
settings. After you define the new domain, restart Informatica services.
To create a domain on a Windows machine, you must first open the host port or disable the firewall.
Do not include any characters after the option (-f) in the DefineDomain command. If you include extra
characters, infasetup might fail with an unexpected error.
The DefineDomain command uses the following syntax:
DefineDomain
<-DatabaseType|-dt> database_type ORACLE|DB2|MSSQLSERVER|SYBASE
DefineDomain
895
[<-SchemaName|-sc> schema_name (used for MSSQLServer only)]
[<-DomainDescription|-de> domain_description]
<-AdministratorName|-ad> administrator_name
[<-LicenseKeyFile|-lf> license_key_file]
[<-SystemLogDirectory|-sld> system_log_directory]
<-NodeAddress|-na> node_host:port
[<-ServiceManagerPort|-sp> service_manager_port]
[<-EnableTLS|-tls> enable_tls]
[<-NodeKeystore|-nk> node_keystore_directory]
[<-NodeKeystorePass|-nkp> node_keystore_password]
[<-NodeTruststore|-nt> node_truststore_directory]
[<-NodeTruststorePass|-ntp> node_truststore_password]
[<-EnableKerberos|-krb> enable_kerberos]
[<-ServiceRealmName|-srn> realm_name_of_node_spn]
[<-UserRealmName|-urn> realm_name_of_user_spn]
[<-KeysDirectory|-kd> Infa_keys_directory_location]
[<-HttpsPort|-hs> admin_tool_https_port]
[<-KeystoreFile|-kf> admin_tool_file_location]
[<-KeystorePass|-kp> admin_tool_keystore_password]
<-MinProcessPort|-mi> minimum_port
<-MaxProcessPort|-ma> maximum_port
[<-ServerPort|-sv> server_shutdown_port]
[<-BackupDirectory|-bd> backup_directory]
[<-ServiceResilienceTimeout|-sr> timeout_period_in_seconds]
[<-ErrorLogLevel|-el> FATAL_ERROR_WARNING_INFO_TRACE_DEBUG]
<-ResourceFile|-rf> resource_file
[<-Timezone|-tz> log_service_timezone_GMT+00:00]
[<-Force|-f>]
[<-TrustedConnection|-tc> trusted_connection (used for MSSQLServer only)]
896
The following table describes infasetup DefineDomain options and arguments:

Option
Argument
Description
-DatabaseAddress
database_hostname:database_port
Required if you do not use

DatabaseConnectionStrin
g (-cs) option. Name and
port number of the
machine hosting the
domain configuration
database.
database_connection_string

-DatabaseAddress (-da)
and DatabaseServiceName (ds) options. Connection
string used to connect to
the domain configuration
database. Specify the
database host, database
port, and the database
service name as part of
the connection string.
Enclose the connection
string in quotes.
database_user_name

-TrustedConnection (-tc)
option. Account for the
database containing the
information.
database_password
Domain configuration
database password
corresponding to the
database user. If you omit
this option, infasetup uses
the password specified in
the
INFA_DEFAULT_DATAB
ASE_PASSWORD
you do not see a value
specified in the
environment variable, you
must enter a password
using this option.
database_type
Required. Type of
database that stores the
metadata. Database types
include:
-da
-cs
-DatabaseUserName
-du
-DatabasePassword
-dp
-DatabaseType
-dt
db2
oracle
mssqlserver
sybase
DefineDomain
897
Option
Argument
Description
database_service_name

g (-cs) option. The
database service name.
Required for Oracle, IBM
DB2, and Microsoft SQL
Server databases. Enter
the SID for Oracle, the
service name for IBM
DB2, or the database
name for Microsoft SQL
Server.
tablespace_name
Required for an IBM DB2

database. Name of the
tablespace where the
database tables reside.
schema_name
Optional. Name of the

schema. Enter a schema
name if you are not using
the default schema.
Optional. Indicates
whether the Informatica
domain database is
secure with TLS or SSL.
Set this option to True for
Default is false. If you
specify the dbtls option
without a value, the
Informatica domain uses
secure communication to
the Informatica domain
database.
database_truststore_password
Optional. Password for

the database truststore
file for the secure
database.
domain_name

domain. Domain names
must be between 1 and
79 characters and cannot
contain spaces or the
following characters: / * ?
<>"|
domain_description
Optional. Description of
the domain.
-ds
-Tablespace
-ts
-SchemaName
-sc
-DatabaseTlsEnabled
-dbtls
-DatabaseTruststorePassword
-dbtp
-DomainName
-dn
-DomainDescription
-de
898
Option
Argument
Description
-AdministratorName
administrator_name
Required. Domain
administrator user name.
password
Optional for Kerberos

domain. Domain
administrator password.
You can set a password
with the -pd option or the
INFA_DEFAULT_DOMAI
N_PASSWORD. If you set
a password with both
set with the -pd option
takes precedence.
license_name

license. The name is not
case sensitive and must
be unique within the
domain. The name cannot
exceed 79 characters,
have leading or trailing
spaces, or contain
carriage returns, tabs, or
-ad
-Password
-pd
-LicenseName
-ln
/*?<>"|
-LicenseKeyFile
license_key_file
Optional. Path to the

license key file.
Required. Shared
directory path used by the
Log Manager to store log
event files.
system_log_directory
Optional. Directory path to

store system log files.
Default is <INFA_home>/
logs.
node_name

node. Node names must
be between 1 and 79
characters and cannot
contain spaces or the
following characters: \ /
*?<>"|
node_host:port
Required. Host name and

port number for the
machine hosting the node.
Choose an available port
number.
-lf
-ld
-SystemLogDirectory
-sld
-NodeName
-nn
-NodeAddress
-na
DefineDomain
899
Option
Argument
Description
-ServiceManagerPort
service_manager_port
Optional. Port number

used by the Service
Manager to listen for
incoming connection
requests.
enable_tls
Optional. Configures
secure communication
among the services in the
Informatica domain.
-sp
-EnableTLS
-tls
If you use the default SSL

certificates provided by
Informatica, you do not
need to specify the
keystore and truststore
options. If you do not use
the default SSL
certificate, you must
specify the keystore and
truststore options. Valid
values are true or false.
Default is false. If you
specify the -tls option
without a value, the
secure communication
among the services.
To enable secure
communication for the
associated services or
web applications, such as
Administrator tool, Analyst
tool, or Web Services
Hub, configure the secure
communication separately
within the applications.
900
Option
Argument
Description
-NodeKeystore-
node_keystore_directory
Optional if you use the

default SSL certificates
from Informatica.
Required if you use your
SSL certificates. Directory
that contains the keystore
files. The Informatica
domain requires the SSL
certificates in PEM format
and in Java Keystore
(JKS) files. The directory
must contain keystore
files in PEM and JKS
formats.
-nk
The keystore files must be

named infa_keystore.jks
and infa_keystore.pem. If
the keystore file that you
receive from the
certificate authority (CA)
has a different name, you
must rename it to
infa_keystore.jks and
infa_keystore.pem.
You must use the same
keystore file for all the
nodes in the domain.
-NodeKeystorePass
-nkp
node_keystore_password

from Informatica.
SSL certificates.
Password for the keystore
DefineDomain
901
Option
Argument
Description
-NodeTruststore
node_truststore_directory

from Informatica.
Directory that contains the
truststore files. The
Informatica domain
requires the SSL
certificates in PEM format
and in Java Keystore
(JKS) files. The directory
must contain truststore
files in PEM and JKS
formats.
-nt
The truststore files must

be named
infa_truststore.jks and
infa_truststore.pem. If the
truststore file that you
receive from the
certificate authority (CA)
has a different name, you
must rename it to
infa_truststore.jks and
infa_truststore.pem.
-NodeTruststorePass
node_truststore_password

from Informatica.
SSL certificates.
Password for the
infa_truststore.jks file.
enable_kerberos
Optional. Configures the

Informatica domain to use
Valid values are true or
false. If true, the domain
uses Kerberos
authentication, and you
cannot later change the
authentication mode. After
you enable Kerberos
authentication, you cannot
disable it. Default is false.
If you specify the -krb
option without a value, the
realm_name_of_node_spn

Kerberos realm to which
services belong. Ensure
that you enter the same
value as -urn for Kerberos
authentication.
-ntp
-EnableKerberos
-krb
-ServiceRealmName
-srn
902
Option
Argument
Description
-UserRealmName
realm_name_of_user_spn

Kerberos realm to which
users belong. Ensure that
you enter the same value
as -srn for Kerberos
authentication.
Infa_keys_directory_location
Optional. Directory where

all keytab files and the
encryption key for the
Informatica domain are
stored. Default is
<InformaticaInstal
lationDir>/isp/
config/keys.
-SPNShareLevel
SPNShareLevel
-spnSL
PROCESS|NODE
Optional. Indicates the

service principal level for
the domain. Set the
property to one of the
following levels:
-urn
-KeysDirectory
-kd
- Process. The domain

requires a unique service
principal name (SPN)
and keytab file for each
node and each service
on a node. The number
of SPNs and keytab files
required for each node
depends on the number
of service processes that
run on the node. Use the
node level option if the
domain does not require
a high level of security.
- Node. The domain uses
one SPN and keytab file
for the node and all
services that run on the
node. It also requires a
separate SPN and
keytab file for all HTTP
Default is process.
-AdminconsolePort
admin_tool_port
Port to access Informatica

Administrator.
admin_tool_https_port
Optional. Port number to

secure the connection to
the Administrator tool. Set
this port number if you
want to configure HTTPS
for a node.
-ap
-HttpsPort
-hs
DefineDomain
903
Option
Argument
Description
-KeystoreFile
admin_tool_file_location
Optional. Keystore file

that contains the keys and
certificates required if you
use the SSL security
protocol.
admin_tool_keystore_password
Optional. A plain-text
password for the keystore
file. You can set a
password with the -kp
variable
INFA_PASSWORD. If you
set a password with both
set with the -kp option
takes precedence.
minimum_port
Required. Minimum port

number for application
service processes that run
on the node.
maximum_port
Required. Maximum port

number for application
service processes that run
on the node.
server_shutdown_port
Optional. TCP/IP port

number used by the
Service Manager. The
Service Manager listens
for shutdown commands
from domain components
on this port. Set this port
number if you have
multiple nodes on one
machine or if the default
port number is in use.
Default is the node port
number plus one.
admin_tool_shutdown_port
Port number that controls

shutdown for Informatica
Administrator.
backup_directory
Optional. Directory to
store repository backup
files. The directory must
be accessible by the
node.
-kf
-KeystorePass
-kp
-MinProcessPort
-mi
-MaxProcessPort
-ma
-ServerPort
-sv
-AdminconsoleShutdownPort
-asp
-BackupDirectory
-bd
904
Option
Argument
Description
-ServiceResilienceTimeout
Optional. Amount of time

in seconds that infasetup
tries to establish or
reestablish a connection
to the local domain. If you
omit this option, infasetup
uses the timeout value
specified in the
INFA_CLIENT_RESILIEN
CE_TIMEOUT
you do not see a value
specified in the
environment variable, the
default of 180 seconds is
used.
-ErrorLogLevel
fatal
-el
error
Optional. Severity level

for log events in the
domain log. Default is
info.
-sr
warning
info
trace
debug
-ResourceFile
resource_file
Required. File that

contains the list of
available resources for
the node. Use the file,
nodeoptions.xml, located
in the following location:
<INFA_HOME>/isp/bi
n
log_service_timezone_GMT+00:00
Optional. Time zone used

by the Log Manager when
it generates log event
files. Default is GMT
+00:00. Configure the
time zone in the following
format:
-rf
-TimeZone
-tz
GMT(+/-)hh:mm
-Force
-f
Optional. Overwrites the

database if a database
with the same name
already exists. Do not
include any characters
after this option.
DefineDomain
905
Option
Argument
Description
-TrustedConnection
Optional. Connect to the

database through a
trusted connection.
Trusted authentication
uses the Windows
security credentials of the
current user to connect to
Microsoft SQL Server.
-tc
Note: If you use a trusted

connection, configure the
g option.
database_truststore_location
-dbtl
Path and file name of the

truststore file for the
secure domain repository
database. Required if you
configure a secure
domain repository
database for the domain.
If you run DefineDomain on a node that currently hosts a domain, reconfigure the following domain
properties:
Application services. Recreate any application service that ran on the domain.
Users. Recreate users.
Gateway nodes. Configure the gateway nodes in the domain.
General domain properties. Configure resilience timeout and maximum restart attempts for the domain.
Grids. Recreate any grid in the domain.
LDAP authentication. Configure LDAP authentication for the domain.
Log Manager properties. Configure the Log Manager shared directory path, purge properties, and time
zone.
If you change the gateway node host name or port number, you must also add each node to the domain
using the infacmd AddDomainNode command.
DefineGatewayNode
Defines a gateway node on the current machine. This command overwrites the nodemeta.xml file that stores
the configuration metadata for the node. After you define the node, run the infacmd isp AddDomainNode
command to add it to the domain.
The DefineGatewayNode command uses the following syntax:
DefineGatewayNode
<-DatabaseAddress|-da> database_hostname:database_port|
906

[<-KeystoreFile|-kf> admin_tool_keystore_file_location]
[<-MinProcessPort|-mi> minimum_port]
[<-MaxProcessPort|-ma> maximum_port]
The following table describes infasetup DefineGatewayNode options and arguments:
Option
Argument
Description
-DatabaseAddress
database_hostname:da
tabase_port
Required if you do not use DatabaseConnectionString (-cs) option. Name and

port number of the machine hosting the domain
configuration database.
-cs
string

and -DatabaseServiceName (-ds) options.
Connection string used to connect to the domain
configuration database. Specify the database host,
database port, and the database service name as
part of the connection string. Enclose the connection
string in quotes.
-DatabaseUserName
database_user_name

database_password

using this option.
-da
-du
-DatabasePassword
-dp
DefineGatewayNode
907
Option
Argument
Description
-DatabaseType
database_type

-dt
- db2
- oracle
- mssqlserver
- sybase
-ds
database_service_nam
e
Required if you do not use DatabaseConnectionString (-cs) option. The

database service name. Required for Oracle, IBM
DB2, and Microsoft SQL Server databases. Enter the
SID for Oracle, the service name for IBM DB2, or the
database name for Microsoft SQL Server.
-DomainName
domain_name
node_name
Optional. Name of the node. Node names must be

between 1 and 79 characters and cannot contain
spaces or the following characters: \ / * ? < > " |
node_host:port
Optional. Host name and port number for the

machine hosting the node. Choose an available port
number.
Optional. Port number used by the Service Manager

to listen for incoming connection requests.
enable_tls
Optional. Configures secure communication among

the services in the Informatica domain.
-dn
-NodeName
-nn
-NodeAddress
-na
-ServiceManagerPort
-sp
-EnableTLS
-tls
If you use the default SSL certificates provided by

Informatica, you do not need to specify the keystore
and truststore options. If you do not use the default
SSL certificate, you must specify the keystore and
truststore options. Valid values are true or false.
Default is false. If you specify the -tls option without a
value, the Informatica domain uses secure
communication among the services.
To enable secure communication for the associated
services or web applications, such as Administrator
tool, Analyst tool, or Web Services Hub, configure the
secure communication separately within the
applications.
908
Option
Argument
Description
-NodeKeystore
node_keystore_directo
ry
Optional if you use the default SSL certificates from

Informatica. Required if you use your SSL
certificates. Directory that contains the keystore files.
The Informatica domain requires the SSL certificates
in PEM format and in Java Keystore (JKS) files. The
directory must contain keystore files in PEM and JKS
formats.
-nk
The keystore files must be named infa_keystore.jks

and infa_keystore.pem. If the keystore file that you
receive from the certificate authority (CA) has a
different name, you must rename it to
infa_keystore.jks and infa_keystore.pem.
You must use the same keystore file for all the nodes
in the domain.
-NodeKeystorePass
-nkp
-NodeTruststore
-nt
node_keystore_passw
ord

certificates. Password for the keystore
node_truststore_direct
ory

certificates. Directory that contains the truststore
files. The Informatica domain requires the SSL
certificates in PEM format and in Java Keystore
(JKS) files. The directory must contain truststore files
in PEM and JKS formats.
The truststore files must be named infa_truststore.jks
and infa_truststore.pem. If the truststore file that you
infa_truststore.jks and infa_truststore.pem.
-ntp
-NodeTruststorePass
node_truststore_passw
ord

certificates. Password for the infa_truststore.jks file.
-EnableKerberos
enable_kerberos
Optional. Configures the Informatica domain to use

Kerberos authentication. Valid values are true or
false. If true, the domain uses Kerberos
authentication, and you cannot later change the
authentication mode. After you enable Kerberos
authentication, you cannot disable it. Default is false.
If you specify the -krb option without a value, the
Informatica domain uses Kerberos authentication.
realm_name_of_node_
spn
Optional. Name of the Kerberos realm to which the

Informatica domain services belong. Ensure that you
enter the same value as -urn for Kerberos
authentication.
realm_name_of_user_
spn

Informatica domain users belong. Ensure that you
enter the same value as -srn for Kerberos
authentication.
-krb
-ServiceRealmName
-srn
-UserRealmName
-urn
DefineGatewayNode
909
Option
Argument
Description
-KeysDirectory
-kd
Infa_keys_directory_lo
cation
Optional. Directory where all keytab files and the

encryption key for the Informatica domain are stored.
Default is
<InformaticaInstallationDir>/isp/
config/keys.
-AdminconsolePort
admin_tool_port
Optional. Port to access Informatica Administrator.
Optional. Port number that the node uses for

communication between the Administrator tool and
the Service Manager. Set this port number if you
want to configure HTTPS for a node.
-ap
-HttpsPort
-hs
To disable HTTPS support for a node, set this port

number to zero.
-KeystoreFile
admin_tool_keystore_fi
le_location
Optional. Keystore file that contains the keys and

certificates required if you use the SSL security
protocol.
-kp
admin_tool_keystore_p
assword
Optional. A plain-text password for the keystore file.

You can set a password with the -kp option or the
environment variable INFA_PASSWORD. If you set a
the -kp option takes precedence.
-MinProcessPort
minimum_port
Optional. Minimum port number for application

service processes that run on the node. Default is
11000.
maximum_port
Optional. Maximum port number for application

service processes that run on the node. Default is
11999.
Optional. Shared directory path used by the Log

Manager to store log event files.
Optional. Directory path to store system log files.

Default is <INFA_home>/logs.
Optional. TCP/IP port number used by the Service

Manager. The Service Manager listens for shutdown
commands from PowerCenter components on this
port. Set this port number if you have multiple nodes
on one machine or if the default port number is in
use. Default is 8005.
-asp
admin_tool_shutdown_
port
Optional. Port number that controls shutdown for

Informatica Administrator.
-BackupDirectory
backup_directory
Optional. Directory to store repository backup files.

The directory must be accessible by the node.
-kf
-KeystorePass
-mi
-MaxProcessPort
-ma
-ld
-SystemLogDirectory
-sld
-ServerPort
-sv
-bd
910
Option
Argument
Description
-ErrorLogLevel
fatal
-el
error
Optional. Severity level for log events in the domain

log. Default is info.
warning
info
trace
debug
-ResourceFile
resource_file
Required. File that contains the list of available

resources for the node. Use the file, nodeoptions.xml,
located in the server\tomcat\bin directory.
tablespace_name

tables reside.
schema_name

schema.

database is secure with TLS or SSL. Set this option
to True for the secure database. Default is false. If
you specify the dbtls option without a value, the
Informatica domain uses secure communication to
the Informatica domain database.
assword

n/a

of the current user to connect to Microsoft SQL
Server.
cation
domain repository database. Required if you
configure a secure domain repository database for
the domain.
-rf
-Tablespace
-ts
-SchemaName
-sc
-DatabaseTlsEnabled
-dbtls
DatabaseTruststorePassword
-dbtp
-TrustedConnection
-tc
-dbtl
DefineGatewayNode
911
Related Topics:
AddDomainNode on page 198
DefineWorkerNode
Defines a worker node on the current machine. infasetup creates the nodemeta.xml file that stores the
configuration metadata for the node. If you run this command on an existing node, it overwrites the node
configuration metadata. After you define the node, run infacmd isp AddDomainNode to add it to the domain.
The DefineWorkerNode command uses the following syntax:
DefineWorkerNode
[<-NodeKeystoreFile|-kf> admin_tool_keystore_file_location]
[<-SecurityDomain|-sdn> security domain]
[<-MinProcessPort|-mi> minimum_port]
[<-MaxProcessPort|-ma> maximum_port]
The following table describes infasetup DefineWorkerNode options and arguments:
Option
Argument
Description
-DomainName
domain_name
Required. Name of the domain the worker node links to.
node_name
Required. Name of the node. Node names must be between

1 and 79 characters and cannot contain spaces or the
following characters: \ / * ? < > " |
node_host:port

hosting the node. Choose an available port number.
Optional. Port number used by the Service Manager to listen

for incoming connection requests.
-dn
-NodeName
-nn
-NodeAddress
-na
-ServiceManagerPort
-sp
912
Option
Argument
Description
-EnableTLS
enable_tls
Optional. Configures secure communication among the

services in the Informatica domain.
-tls

Informatica, you do not need to specify the keystore and
truststore options. If you do not use the default SSL
certificate, you must specify the keystore and truststore
options. Valid values are true or false. Default is false. If you
specify the -tls option without a value, the Informatica
domain uses secure communication among the services.
To enable secure communication for the associated services
or web applications, such as Administrator tool, Analyst tool,
or Web Services Hub, configure the secure communication
separately within the applications.
-NodeKeystore
-nk
node_keystore_directo
ry

Informatica. Required if you use your SSL certificates.
Directory that contains the keystore files. The Informatica
domain requires the SSL certificates in PEM format and in
Java Keystore (JKS) files. The directory must contain
keystore files in PEM and JKS formats.
The keystore files must be named infa_keystore.jks and
infa_keystore.pem. If the keystore file that you receive from
the certificate authority (CA) has a different name, you must
rename it to infa_keystore.jks and infa_keystore.pem.
You must use the same keystore file for all the nodes in the
domain.
-NodeKeystorePass
-nkp
-NodeTruststore
-nt
node_keystore_passw
ord

Password for the keystore infa_keystore.jks file.
node_truststore_direct
ory

Informatica. Directory that contains the truststore files. The
Informatica domain requires the SSL certificates in PEM
format and in Java Keystore (JKS) files. The directory must
contain truststore files in PEM and JKS formats.
The truststore files must be named infa_truststore.jks and
infa_truststore.pem. If the truststore file that you receive
from the certificate authority (CA) has a different name, you
must rename it to infa_truststore.jks and infa_truststore.pem.
-NodeTruststorePass
-ntp
ord

Password for the infa_truststore.jks file.
-EnableKerberos
enable_kerberos
Optional. Configures the Informatica domain to use Kerberos

authentication. Valid values are true or false. If true, the
domain uses Kerberos authentication, and you cannot later
change the authentication mode. After you enable Kerberos
authentication, you cannot disable it. Default is false. If you
specify the -krb option without a value, the Informatica
domain uses Kerberos authentication.
realm_name_of_node_
spn

Informatica domain services belong. Ensure that you enter
the same value as -urn for Kerberos authentication.
-krb
-ServiceRealmName
-srn
DefineWorkerNode
913
Option
Argument
Description
-UserRealmName
realm_name_of_user_
spn

Informatica domain users belong. Ensure that you enter the
same value as -srn for Kerberos authentication.
-kd
cation
Optional. Directory where all keytab files and the encryption

key for the Informatica domain are stored. Default is
<InformaticaInstallationDir>/isp/config/
keys.
-HttpsPort
Optional. Port number that the node uses for communication

between the Administrator tool and the Service Manager. Set
this port number if you want to configure HTTPS for a node.
-urn
-KeysDirectory
-hs
To disable HTTPS support for a node, set this port number

to zero.
-NodeKeystoreFile
admin_tool_keystore_fi
le_location
Optional. Keystore file that contains the keys and certificates

required if you use the SSL security protocol.
assword
Optional. A plain-text password for the keystore file. You can

set a password with the -kp option or the environment
variable INFA_PASSWORD. If you set a password with both
methods, the password set with the -kp option takes
precedence.
domain_gateway_host:
port
-dg
-UserName
user_name

-kf
-KeystorePass
-kp
-GatewayAddress
-un

sign-on.
-SecurityDomain
security domain
-sdn

You can specify a value for sdn or use the default based on
the authentication mode:
- Optional if the domain uses native authentication or Kerberos
authentication. Default is native for native authentication. If
914
Option
Argument
Description
-Password
password

minimum_port
Optional. Minimum port number for application service

processes that run on the node. Default is 11000.
maximum_port
Optional. Maximum port number for application service

processes that run on the node. Default is 11999.
Optional. TCP/IP port number used by the Service Manager.

The Service Manager listens for shutdown commands from
PowerCenter components on this port. Set this port number
if you have multiple nodes on one machine or if the default
port number is in use. Default is 8005.
backup_directory
Optional. Directory to store repository backup files. The

directory must be accessible by the node.
-ErrorLogLevel
fatal
-el
error
Optional. Severity level for log events in the domain log.

Default is info.
-pd
-MinProcessPort
-mi
-MaxProcessPort
-ma
-ServerPort
-sv
-BackupDirectory
-bd
warning
info
trace
debug
-ResourceFile
resource_file
Required. File that contains the list of available resources for

the node. Use the file, nodeoptions.xml, located in the server
\tomcat\bin directory.
Optional. Directory path to store system log files. Default is

<INFA_home>/logs.
-rf
-SystemLogDirectory
-sld
DeleteDomain
Deletes domain metadata tables. Before you run this command, you must stop the Informatica services on
the machine. To delete a domain on a Windows machine, you must also open the host port or disable the
firewall.
The DeleteDomain command uses the following syntax:
DeleteDomain
DeleteDomain
915
[<-SchemaName|-sc> schema_name (used for Microsoft SQL Server only)]
[<-TrustedConnection|-tc> trusted_connection (used for Microsoft SQL Server only)]
The following table describes infasetup DeleteDomain options and arguments:
Option
Argument
Description
-DatabaseAddress
-da
database_hostname:database
_port
Required if you do not use DatabaseConnectionString (-cs) option. Name

and port number of the machine hosting the
domain configuration database.
database_connection_string
Required if you do not use -DatabaseAddress

(-da) and -DatabaseServiceName (-ds)
options. Connection string used to connect to
the domain configuration database. Specify
the database host, database port, and the
database service name as part of the
connection string. Enclose the connection
string in quotes.
database_user_name
Required if you do not use TrustedConnection (-tc) option. Account for

the database containing the domain
configuration information.
database_password

corresponding to the database user. If you
omit this option, infasetup uses the password
specified in the
environment variable. If no value is specified
in the environment variable, you must enter a
password using this option.
database_type
Required. Type of database that stores the

domain configuration metadata. Database
types include:
-cs
-DatabaseUserName
-du
-DatabasePassword
-dp
-DatabaseType
-dt
916
db2
oracle
mssqlserver
sybase
Option
Argument
Description
database_service_name

database service name. Required for Oracle,
IBM DB2, and Microsoft SQL Server
databases. Enter the SID for Oracle, the
service name for IBM DB2, or the database
name for Microsoft SQL Server.
tablespace_name
Required for an IBM DB2 database. Name of

the tablespace where the domain
configuration database tables reside.
schema_name
Optional. Name of the Microsoft SQL Server

schema. Enter a schema name if you are not
using the default schema.
Optional. Indicates whether the Informatica

domain database is secure with TLS or SSL.
Set this option to True for the secure
database. Default is false. If you specify the
dbtls option without a value, the Informatica
domain uses secure communication to the
Informatica domain database.
database_truststore_password
Optional. Password for the database

truststore file for the secure database.
Optional. Connect to the Microsoft SQL

Server database through a trusted
connection. Trusted authentication uses the
Windows security credentials of the current
user to connect to Microsoft SQL Server.
encryption_key_location
Directory that contains the current encryption

key. The name of the encryption file is
sitekey.
-ds
-Tablespace
-ts
SchemaName
-sc
-DatabaseTlsEnabled
-dbtls
-dbtp
-TrustedConnection
-tc
-kl
Informatica renames the current sitekey file to

sitekey_old and generates an encryption key
in a new file named sitekey in the same
directory.
-dbtl
database_truststore_location
Path and file name of the truststore file for the

secure domain repository database. Required
if you configure a secure domain repository
database for the domain.
DeleteDomain
917
GenerateEncryptionKey
Generate an encryption key to secure sensitive data, such as passwords, in the Informatica domain.
The GenerateEncryptionKey command uses the following syntax:
GenerateEncryptionKey
<-Keyword|-kw> keyword
The following table describes infasetup GenerateEncryptionKey options and arguments:
Option
Argument
Description
-Keyword
keyword
Required. The text string used as the base

word from which to generate an encryption
key.
-kw
The keyword must meet the following criteria:

-
-DomainName
From 8 to 20 characters long

Includes at least one uppercase letter
Includes at least one lowercase letter
Includes at least one number
Does not contain spaces
domain_name
encryption_key_location
Optional. Directory that contains the current

encryption key. The name of the encryption file
is sitekey.
-dn
-kl
Informatica renames the current sitekey file to

sitekey_old and generates an encryption key in
a new file named sitekey in the same directory.
To run the command again when there are at
least two sitekey files in the directory, ensure
that you back up the sitekey files. You can
then run the command to create the sitekey file
before you restore the backup sitekey files.
Help
The Help command displays the options and arguments for a command. If you omit the command name,
infasetup lists all commands.
The Help command uses the following syntax:
Help [command]
For example, if you type infasetup Help UpdateWorkerNode, infasetup returns the following options and
arguments for the UpdateWorkerNode command:
UpdateWorkerNode [<-DomainName|-dn> domain_name] <-NodeName|-nn> node_name][<NodeAddress|-na> node_host:port]
918
[<-GatewayAddress|-dg> domain_gateway_host:port][<-UserName|-un> user_name][<-Password|pd> password][<-ServerPort|-sv> server_admin_port_number]

The following table describes the infasetup Help option and argument:
Option
Argument
Description
command
Optional. Name of command. If you omit the command name, infasetup lists all
commands.
MigrateEncryptionKey
Change the encryption key used to secure sensitive data, such as passwords, in the Informatica domain.
<-LocationOfEncryptionKeys|-loc> location_of_encryption_keys
[<-IsDomainMigrated|-mig> is_domain_migrated]
Note: If the domain contains a Reporting Service, do not change the encryption key. The
migrateEncryptionKey command fails if the domain contains a Reporting Service.
The following table describes infasetup MigrateEncryptionKey options and arguments:
Option
Argument
Description
-LocationOfEncryptionKeys
location_of_encryption
_keys
Required. Directory in which the old encryption key

file named siteKey_old and the new encryption key
file named siteKey are stored.
-loc
The directory must contain the old and new

encryption key files. If the old and new encryption key
files are stored in different directories, copy the
encryption key files to the same directory.
If the domain has multiple nodes, this directory must
be accessible to any node in the domain where you
run the migrateEncryptionKey command.
-IsDomainMigrated
-mig
is_domain_migrated
Optional. Indicates whether the domain has been

updated to use the latest encryption key.
When you run the migrateEncryptionKey command
for the first time, set this option to False to indicate
that the domain uses the old encryption key.
After the first time, when you run the
migrateEncryptionKey command to update other
nodes in the domain, set this option to True to
indicate that the domain has been updated to use the
latest encryption key. Or you can run the
migrateEncryptionKey command without this option.
Default is True.
919
RestoreDomain
Restores the configuration metadata for the domain from a backup .mrep file. If you have a backup file from
an earlier version of Informatica, you must use the earlier version to restore the domain.
You must shut down the domain before you run this command.
If you restore the domain into a database other than the original backup database, you must restore the
ISP_RUN_LOG table contents to get the previous workflow and session logs.
The RestoreDomain command uses the following syntax:
RestoreDomain
<-DatabaseType|-dt> database_type
<-BackupFile|-bf> backup_file_name
[<-Force|-f>]
[<-ClearNodeAssociation|-ca>]
920
The following table describes infasetup RestoreDomain options and arguments:

Option
Argument
Description
-DatabaseAddress
database_hostname:d
atabase_port

-cs
string

string in quotes.
-DatabaseUserName
database_user_name

database_password

using this option.
database_type

-da
-du
-DatabasePassword
-dp
-DatabaseType
-dt
db2
oracle
mssqlserver
sybase
-ds
database_service_na
me

-BackupFile
backup_file_name
Required. Name and path for the backup file. If you

do not specify a file path, infasetup creates the
backup file in the current directory.
Optional. Overwrites the database if a database with

the same name already exists. Do not include any
characters after this option.
-bf
-Force
-f
RestoreDomain
921
Option
Argument
Description
-ClearNodeAssociation
Optional. Clears node associations when restoring

the domain. For example, a backed up domain
contains node Node1 on machine MyHost:9090. If
you specify this option, the connection between the
node name Node1 and the address MyHost:9090
is broken when you restore the domain. You can then
associate another node with MyHost:9090.
-ca
If you do not specify this option, Node1 retains its

connection to MyHost:9090. If you restore the
domain and associate another node with MyHost:
9090, the node does not start.
-Tablespace
tablespace_name

tables reside.
schema_name

schema.

-dbtp
assword

-TrustedConnection

Server.
encryption_key_locati
on
Optional. Directory that contains the current

encryption key. The name of the encryption file is
sitekey.
database_truststore_l
ocation
Optional. Path and file name of the truststore file for

the secure database. Required if you configure a
secure domain repository database for the domain.
-ts
-SchemaName
-sc
-DatabaseTlsEnabled
-dbtls
-DatabaseTruststorePassword
-tc
-kl
-dbtl
SwitchToKerberosMode
Configure the Informatica domain to use Kerberos authentication.
The SwitchToKerberosMode command uses the following syntax:
SwitchToKerberosMode
<-administratorName|-ad> administrator_name
922
<-ServiceRealmName|-srn> realm_name_of_node_spn
<-UserRealmName|-urn> realm_name_of_user_spn
The following table describes infasetup SwitchToKerberosMode options and arguments:
Option
Argument
Description
-administratorName
administrator_name
Required. Name of the user to select as the default

administrator.
realm_name_of_node_
spn

authentication.
-urn
realm_name_of_user_
spn

authentication.
SPNShareLevel
SPNShareLevel
-spnSL
PROCESS|NODE]
Optional. Indicates the service principal level for the

domain. Set the property to one of the following
levels:
-ad
-ServiceRealmName
-srn
-UserRealmName
- Process. The domain requires a unique service

principal name (SPN) and keytab file for each node
and each service on a node. The number of SPNs
and keytab files required for each node depends on
the number of service processes that run on the node.
Recommended for production domains.
- Node. The domain uses one SPN and keytab file for
the node and all services that run on the node. It also
requires a separate SPN and keytab file for all HTTP
processes on the node. Recommended for test and
development domains. Recommended for test and
development domains.
Default is process.
UpdateGatewayNode
Updates connectivity information for a gateway node on the current machine. Before you update the gateway
node, run the infacmd isp ShutDownNode command to shut down the node.
The UpdateGatewayNode command uses the following syntax:
UpdateGatewayNode
[<-DatabaseAddress|-da> database_hostname:database_port|<-DatabaseConnectionString|-cs>
database_connection_string]
[<-DatabaseType|-dt> database_type ORACLE|DB2|MSSQLSERVER|SYBASE]
[<-NodeAddress|-na> node_host:port]
UpdateGatewayNode
923
[<-LogServiceDirectory|-ld> log_service_directory]
[<-resetHostPort|-rst> resetHostPort]
The following table describes infasetup UpdateGatewayNode options and arguments:
Option
Argument
Description
-DatabaseAddress
database_hostname:da
tabase_port

-cs
database_connection_s
tring

string in quotes.
-DatabaseUserName
database_user_name

database_password

using this option.
database_type
ORACLE|DB2|
MSSQLSERVER|
SYBASE

-da
-du
-DatabasePassword
-dp
-DatabaseType
-dt
- db2
- oracle
- mssqlserver
- sybase
924
Option
Argument
Description
-ds
database_service_nam
e

-DomainName
domain_name
node_name
Optional. Name of the node. Node names must be

between 1 and 79 characters and cannot contain
spaces or the following characters: \ / * ? < > " |
node_host:port
Optional. Host name and port number for the

machine hosting the node. Choose an available port
number.
Optional. Port number used by the Service Manager

to listen for incoming connection requests.
enable_tls
Optional. Configures secure communication among

the services in the Informatica domain.
-dn
-NodeName
-nn
-NodeAddress
-na
-ServiceManagerPort
-sp
-EnableTLS
-tls

Informatica, you do not need to specify the keystore
and truststore options. If you do not use the default
SSL certificate, you must specify the keystore and
truststore options. Valid values are true or false.
Default is false. If you specify the -tls option without a
value, the Informatica domain uses secure
communication among the services.
To enable secure communication for the associated
services or web applications, such as Administrator
tool, Analyst tool, or Web Services Hub, configure the
secure communication separately within the
applications.
-NodeKeystore
-nk
node_keystore_director
y

certificates. Directory that contains the keystore files.
The Informatica domain requires the SSL certificates
in PEM format and in Java Keystore (JKS) files. The
directory must contain keystore files in PEM and JKS
formats.
The keystore files must be named infa_keystore.jks
and infa_keystore.pem. If the keystore file that you
infa_keystore.jks and infa_keystore.pem.
You must use the same keystore file for all the nodes
in the domain.
-NodeKeystorePass
-nkp
node_keystore_passwo
rd

certificates. Password for the keystore
UpdateGatewayNode
925
Option
Argument
Description
-NodeTruststore
node_truststore_directo
ry

certificates. Directory that contains the truststore
files. The Informatica domain requires the SSL
certificates in PEM format and in Java Keystore
(JKS) files. The directory must contain truststore files
in PEM and JKS formats.
-nt
The truststore files must be named infa_truststore.jks

and infa_truststore.pem. If the truststore file that you
infa_truststore.jks and infa_truststore.pem.
-ntp
-NodeTruststorePass
ord

certificates. Password for the infa_truststore.jks file.
-EnableKerberos
enable_kerberos
Optional. Configures the Informatica domain to use

Kerberos authentication. Valid values are true or
false. If true, the domain uses Kerberos
authentication, and you cannot later change the
authentication mode. After you enable Kerberos
authentication, you cannot disable it. Default is false.
If you specify the -krb option without a value, the
Informatica domain uses Kerberos authentication.
realm_name_of_node_
spn

authentication.
realm_name_of_user_s
pn

authentication.
-kd
Infa_keys_directory_loc
ation
Optional. Directory where all keytab files and the

encryption key for the Informatica domain are stored.
Default is
<InformaticaInstallationDir>/isp/
config/keys.
-AdminconsolePort
admin_tool_port
Optional. Port to access Informatica Administrator.
Optional. Port number to secure the connection to the

Administrator tool. Set this port number if you want to
configure HTTPS for a node.
-krb
-ServiceRealmName
-srn
-UserRealmName
-urn
-KeysDirectory
-ap
-HttpsPort
-hs
To disable HTTPS support for a node, set this port

number to zero.
-KeystoreFile
-kf
926
admin_tool_keystore_fil
e_location
Optional. Keystore file that contains the keys and

certificates required if you use the SSL security
protocol.
Option
Argument
Description
-KeystorePass
-kp
assword
Optional. A plain-text password for the keystore file.

You can set a password with the -kp option or the
environment variable INFA_PASSWORD. If you set a
the -kp option takes precedence.
Optional. Shared directory path used by the Log

Manager to store log event files.
Optional. Directory path to store system log files.

Default is <INFA_home>/logs.
Optional. TCP/IP port number used by the Service

Manager. The Service Manager listens for shutdown
commands from PowerCenter components on this
port. Set this port number if you have multiple nodes
on one machine or if the default port -number is in
use. Default is 8005.
-asp
admin_tool_shutdown_
port
Optional. Port number that controls shutdown for

Informatica Administrator.
-Tablespace
tablespace_name

tables reside.
-sc
schema_name <used
for MSSQLServer only>

schema.
-DatabaseTlsEnabled

database_truststore_pa
ssword

-tc
trusted_connection
<used for
MSSQLServer only>

Server.
-resetHostPort
resetHostPort
Required if you specify the NodeAddress or

ServiceManager option. Resets the host port number.
cation
Optional. Path and file name of the truststore file for

the gateway node.
-ld
-SystemLogDirectory
-sld
-ServerPort
-sv
-ts
-SchemaName
-dbtls
-dbtp
-TrustedConnection
-rst
-dbtl
UpdateGatewayNode
927
UpdateKerberosAdminUser
Updates the default Kerberos administrator user in the domain repository.
The UpdateKerberosAdminUser command uses the following syntax:
UpdateKerberosAdminUser
<-KerberosAdminName|-kan> kerberos_admin_name
The following table describes infasetup UpdateKerberosAdminUser options and arguments:
Option
Argument
Description
-KerberosAdminName
kerberos_admin_name
Required. Name of the user to select as the default

administrator.
-kan
UpdateKerberosConfig
Use the UpdateKerberosConfig command to correct the realm name or service realm name in the Informatica
configuration. You can change the user realm that the Informatica domain users belong to. You can change
the service realm that the Informatica domain services belong to.
Note: This command does not change the Kerberos configuration. You cannot use this command to migrate
users from one user realm or service realm to another user realm or service realm.
The UpdateKerberosConfig command uses the following syntax:
UpdateKerberosConfig
[<-ServiceRealmName|-srn>] realm_name_of_node_spn
[<-UserRealmName|-urn>] realm_name_of_user_spn
The following table describes infasetup UpdateKerberosConfig options and arguments:
Option
Argument
Description
-ServiceRealmName
realm_name_of_node_
spn

Informatica domain services belong. The service
realm name must be the same as the user realm
name.
realm_name_of_user_
spn

Informatica domain users belong. The user realm
name must be the same as the service realm name.
-srn
-UserRealmName
-urn
928
UpdateWorkerNode
Updates connectivity information for a worker node on the current machine. Before you update the worker
node, run the infacmd isp ShutDownNode command to shut down the node.
The UpdateWorkerNode command uses the following syntax:
UpdateWorkerNode
[<-NodeAddress|-na> node_host:port]
[<-GatewayAddress|-dg> domain_gateway_host:port]
[<-SecurityDomain|-sdn> security domain]
[<-resetHostPort|-rst> resetHostPort]
The following table describes infasetup UpdateWorkerNode options and arguments:
Option
Argument
Description
-DomainName
domain_name
node_name
Optional. Name of the node. Node names must be between 1

and 79 characters and cannot contain spaces or the following
characters: \ / * ? < > " |
node_host:port
Optional. Host name and port number for the machine

hosting the node. Choose an available port number.
Optional. Port number used by the Service Manager to listen

for incoming connection requests.
-dn
-NodeName
-nn
-NodeAddress
-na
-ServiceManagerPort
-sp
UpdateWorkerNode
929
Option
Argument
Description
-EnableTLS
enable_tls
Optional. Configures secure communication among the

services in the Informatica domain.
-tls

Informatica, you do not need to specify the keystore and
truststore options. If you do not use the default SSL
certificate, you must specify the keystore and truststore
options. Valid values are true or false. Default is false. If you
specify the -tls option without a value, the Informatica domain
uses secure communication among the services.
To enable secure communication for the associated services
or web applications, such as Administrator tool, Analyst tool,
or Web Services Hub, configure the secure communication
separately within the applications.
-ServiceRealmName
realm_name_of_node
_spn

Informatica domain services belong. Ensure that you enter
the same value as -urn for Kerberos authentication.
realm_name_of_user_
spn

Informatica domain users belong. Ensure that you enter the
same value as -srn for Kerberos authentication.
-kd
cation
Optional. Directory where all keytab files and the encryption

key for the Informatica domain are stored. Default is
<InformaticaInstallationDir>/isp/config/
keys.
-HttpsPort
Optional. Port number to secure the connection to the

Administrator tool. Set this port number if you want to
configure HTTPS for a node.
admin_tool_keystore_f
ile_location
Optional. Keystore file that contains the keys and certificates

required if you use the SSL security protocol.
admin_tool_keystore_
password
Optional. A plain-text password for the keystore file. You can

set a password with the -kp option or the environment
variable INFA_PASSWORD. If you set a password with both
methods, the password set with the -kp option takes
precedence.
domain_gateway_host
:port
-dg
-UserName
user_name

-srn
-UserRealmName
-urn
-KeysDirectory
-hs
-NodeKeystoreFile
-kf
-KeystorePass
-kp
-GatewayAddress
-un

sign-on.
930
Option
Argument
Description
-SecurityDomain
security domain
Name of the security domain that you want to create to which

the domain user belongs. You can set a security domain with
-sdn
You can specify a value for sdn or use the default based on
the authentication mode:
Native. To work with LDAP authentication, you need to specify
the value for -sdn.
- Optional if the domain uses native authentication or Kerberos
authentication. Default is native for native authentication. If
-Password
password
Optional. TCP/IP port number used by the Service Manager.

The Service Manager listens for shutdown commands from
PowerCenter components on this port. Set this port number if
you have multiple nodes on one machine or if the default port
number is in use.
true | false
Required if you specify the NodeAddress or ServiceManager

option. Resets the host port number.
Optional. Directory path to store system log files. Default is

<INFA_home>/logs.
-pd
-ServerPort
-sv
-resetHostPort
-rst
-SystemLogDirectory
-sld
UnlockUser
Unlocks a native or an LDAP user account. When you unlock a native user account, you can also provide a
new password for the account.
You can unlock a user account after you shut down the domain from the gateway node.
The infasetup UnlockUser command uses the following syntax:
UnlockUser
[<-SecurityDomain|-sdn] security domain]
[<-NewPassword|-np] new_password]
UnlockUser
931
The following table describes the infasetup UnlockUser options and arguments:
Option
Argument
Description
-UserName
user_name
Required. User name of the locked account. The value is case sensitive.
security domain
Required if the domain uses LDAP authentication. Optional if the domain

uses native authentication or Kerberos authentication. Name of the
security domain to which the domain user belongs. You can set a security
INFA_DEFAULT_SECURITY_DOMAIN. If you set a security domain name
with both methods, the -sdn option takes precedence. The security domain
-un
-SecurityDomain
-sdn
If the domain uses native or LDAP authentication, the default is Native. If

the domain uses Kerberos authentication, the default is the LDAP security
domain created during installation. The name of the security domain is the
same as the user realm specified during installation.
-NewPassword
new_password
Optional. New password for the locked native account.
-np
ValidateandRegisterFeature
Validates and registers the feature in the domain.
The ValidateandRegisterFeature command uses the following syntax:
ValidateandRegisterFeature
<-FeatureFilename|-ff> feature_filename
<-IsUpgrade|-up> is_upgrade
The following table describes infasetup ValidateandRegisterFeature options and arguments:
Option
Argument
Description
-FeatureFilename
feature_filename
Required. Location of the xml file for the plugin.
is_upgrade
Required. Indicates whether to upgrade the plug-in to

the specified version in the feature file. Valid values
are true and false. Default is true.
-ff
-IsUpgrade
-up
932
CHAPTER 30
pmcmd Command Reference

Using pmcmd, 934
AbortTask, 939
abortworkflow, 941
Connect, 942
Disconnect, 944
Exit, 944
GetRunningSessionsDetails, 944
GetServiceDetails, 945
GetServiceProperties, 947
getsessionstatistics, 948
GetTaskDetails, 950
GetWorkflowDetails, 952
Help, 955
PingService, 956
RecoverWorkflow, 956
ScheduleWorkflow, 958
SetFolder, 960
SetNoWait, 960
SetWait, 960
ShowSettings, 961
StartTask, 961
StartWorkflow, 964
StopTask, 967
StopWorkflow, 969
UnscheduleWorkflow, 971
UnsetFolder, 972
Version, 973
933
WaitTask, 973
WaitWorkflow, 975
Using pmcmd
pmcmd is a program you use to communicate with the Integration Service. With pmcmd, you can perform
some of the tasks that you can also perform in the Workflow Manager, such as starting and stopping
workflows and sessions.
Use pmcmd in the following modes:
Command line mode. You invoke and exit pmcmd each time you issue a command. You can write scripts
to schedule workflows with the command line syntax. Each command you write in command line mode
must include connection information to the Integration Service.
Interactive mode. You establish and maintain an active connection to the Integration Service. This lets
you issue a series of commands.
You can use environment variables for user names and passwords with pmcmd. You can also use
environment variables to customize the way pmcmd displays the date and time on the machine running the
Integration Service process. Before you use pmcmd, configure these variables on the machine running the
Integration Service process. The environment variables apply to pmcmd commands that run on the node.
Note: If the domain is a mixed-version domain, run pmcmd from the installation directory of the Integration
Service version.
Running Commands in Command Line Mode

Command line mode invokes and exits pmcmd each time you issue a command. Command line mode is
useful if you want to run pmcmd commands through batch files, scripts, or other programs.
Use pmcmd commands with operating system scheduling tools like cron, or you can embed pmcmd
commands into shell or Perl scripts.
When you run pmcmd in command line mode, you enter connection information such as domain name,
Integration Service name, user name and password in each command. For example, to start the workflow
wf_SalesAvg in folder SalesEast, use the following syntax:
pmcmd startworkflow -sv MyIntService -d MyDomain -u seller3 -p jackson f SalesEast
wf_SalesAvg
The user, seller3, with the password jackson sends the request to start the workflow.
If you omit or incorrectly enter one of the required options, the command fails, and pmcmd returns a non-zero
return code. For more information about all the return codes, see pmcmd Return Codes on page 935.
To run pmcmd commands in command line mode:
1.
At the command prompt, switch to the directory where the pmcmd executable is located.
By default, the PowerCenter installer installs pmcmd in the \server\bin directory.
2.
Enter pmcmd followed by the command name and its required options and arguments:
pmcmd command_name [-option1] argument_1 [-option2] argument_2...
934
Chapter 30: pmcmd Command Reference
pmcmd Return Codes

In command line mode, pmcmd indicates the success or failure of a command with a return code. Return
code 0 indicates that the command succeeded. Any other return code indicates that the command failed.
Use the DOS or UNIX echo command immediately after running a pmcmd command to see the return code
for the command:
The following table describes the return codes for pmcmd:

Code
Description
For all commands, a return value of zero indicates that the command ran successfully. You can
issue the following commands in the wait or nowait mode: starttask, startworkflow, aborttask, and
abortworkflow. If you issue a command in the wait mode, a return value of zero indicates the
command ran successfully. If you issue a command in the nowait mode, a return value of zero
indicates that the request was successfully transmitted to the Integration Service, and it
acknowledged the request.
Integration Service is not available, or pmcmd cannot connect to the Integration Service. There is a
problem with the TCP/IP host name or port number or with the network.
Task name, workflow name, or folder name does not exist.
An error occurred starting or running the workflow or task.
Usage error. You passed the wrong options to pmcmd.
An internal pmcmd error occurred. Contact Informatica Global Customer Support.
You used an invalid user name or password.
You do not have the appropriate permissions or privileges to perform this task.
Connection to the Integration Service timed out while sending the request.
12
Integration Service cannot start recovery because the session or workflow is scheduled, waiting for
an event, waiting, initializing, aborting, stopping, disabled, or running.
13
User name environment variable is set to an empty value.
14
Password environment variable is set to an empty value.
15
User name environment variable is missing.
16
Password environment variable is missing.
17
Parameter file does not exist.
18
Integration Service found the parameter file, but it did not have the initial values for the session
parameters, such as $input or $output.
19
Integration Service cannot resume the session because the workflow is configured to run
continuously.
Using pmcmd
935
Code
Description
20
A repository error has occurred. Make sure that the Repository Service and the database are running
and the number of connections to the database is not exceeded.
21
Integration Service is shutting down and it is not accepting new requests.
22
Integration Service cannot find a unique instance of the workflow/session you specified. Enter the
command again with the folder name and workflow name.
23
There is no data available for the request.
24
Out of memory.
25
Command is cancelled.
Running Commands in Interactive Mode

Use pmcmd in interactive mode to start and stop workflows and sessions without writing a script. When you
use the interactive mode, you enter connection information such as domain name, Integration Service name,
user name, and password. You can run subsequent commands without entering the connection information
for each command.
For example, the following commands invoke the interactive mode, establish a connection to Integration
Service MyIntService, and start workflows wf_SalesAvg and wf_SalesTotal in folder SalesEast:
pmcmd
pmcmd>
pmcmd>
pmcmd>
pmcmd>
connect -sv MyIntService -d MyDomain -u seller3 -p jackson

setfolder SalesEast
startworkflow wf_SalesAvg
startworkflow wf_SalesTotal
To run pmcmd commands in interactive mode:

1.
At the command prompt, switch to the directory where the pmcmd executable is located.
By default, the PowerCenter installer installs pmcmd in the \server\bin directory.
2.
At the command prompt, type pmcmd.

This starts pmcmd in interactive mode and displays the pmcmd> prompt. You do not have to type pmcmd
before each command in interactive mode.
3.
Enter connection information for the domain and Integration Service. For example:
connect -sv MyIntService -d MyDomain -u seller3 -p jackson
4.
Type a command and its options and arguments in the following format:
command_name [-option1] argument_1 [-option2] argument_2...
pmcmd runs the command and displays the prompt again.
5.
Type exit to end an interactive session.
Setting Defaults
After you connect to an Integration Service using pmcmd, you can designate default folders or conditions to
use each time the Integration Service executes a command. For example, if you want to issue a series of
commands or tasks in the same folder, specify the name of the folder with the setfolder command. All
subsequent commands use that folder as the default.
936
The following table describes the commands that you use to set defaults for subsequent commands:
Command
Description
setfolder
Designates a folder as the default folder in which to execute all subsequent commands.
setnowait
Executes subsequent commands in the nowait mode. The pmcmd prompt is available after
the Integration Service receives the previous command. The nowait mode is the default
mode.
setwait
Executes subsequent commands in the wait mode. The pmcmd prompt is available after the
Integration Service completes the previous command.
unsetfolder
Reverses the setfolder command.
You can use pmcmd ShowSettings command to display the default settings.
Running in Wait Mode

You can run pmcmd in wait or nowait mode. In wait mode, pmcmd returns to the shell or command prompt
after the command completes. You cannot run subsequent commands until the previous command
completes.
For example, if you enter the following command, pmcmd starts the workflow wf_SalesAvg and does not
return to the prompt until the workflow completes:
pmcmd startworkflow -sv MyIntService -d MyDomain -u seller3 -p jackson f SalesEast wait wf_SalesAvg
In nowait mode, pmcmd returns to the shell or command prompt immediately. You do not have to wait for one
command to complete before running the next command.
For example, if you enter the following commands, pmcmd starts workflow wf_SalesTotal even if workflow
wf_SalesAvg is still running:
wf_SalesAvg
wf_SalesTotal
By default, pmcmd executes commands in nowait mode.
You can configure the wait mode when you run in command line or interactive mode. In command line mode,
use the -wait option to run a command in wait mode. In interactive mode, use the setwait or setnowait
command before entering subsequent commands.
Scripting pmcmd Commands

When you use pmcmd, you might use some commands with specific options and arguments on a regular
basis. For example, you might use pmcmd to check the status of the Integration Service. In this case, you
can create a script or batch file to call one or more pmcmd commands including its options and arguments.
You can run scripts in command line mode. You cannot run pmcmd scripts in interactive mode.
For example, the following UNIX shell script checks the status of Integration Service testService, and if it is
running, gets details for session s_testSessionTask:
#!/usr/bin/bash
# Sample pmcmd script
# Check if the service is alive
Using pmcmd
937
pmcmd pingservice -sv testService -d testDomain

if [ "$?" != 0 ]; then
# handle error
echo "Could not ping service"
exit
fi
# Get service properties
pmcmd getserviceproperties
if [ "$?" != 0 ]; then
-sv testService -d testDomain
# handle error
echo "Could not get service properties"
exit
fi
# Get task details for session task "s_testSessionTask" of workflow
# "wf_test_workflow" in folder "testFolder"
pmcmd gettaskdetails -sv testService -d testDomain -u Administrator -p adminPass folder testFolder -workflow wf_test_workflow s_testSessionTask
if [ "$?" != 0 ]; then
# handle error
echo "Could not get details for task s_testSessionTask"
exit
fi
Entering Command Options

pmcmd provides multiple ways to enter some of the command options and arguments. For example, to enter
a password, use the following syntax:
<<-password|-p> password|<-passwordvar|-pv> passwordEnvVar>
To enter a password, precede the password with the -password or -p option:
-password ThePassword
or
-p ThePassword
If you use a password environment variable, precede the variable name with the -pv or passwordvar option:
-passwordvar PASSWORD
or
-pv PASSWORD
If a command option contains spaces, use single or double quotation marks to enclose the option. For
example, use single quotes in the following syntax to enclose the folder name:
abortworkflow -sv MyIntService -d MyDomain -u seller3 -p jackson f 'quarterly sales' wait wf_MyWorkflow
To denote an empty string, use two single quotes ('') or two double quotes ("").
938
AbortTask
Aborts a task. Issue this command only if the Integration Service fails to stop the task when you issue the
stoptask command.
The AbortTask command uses the following syntax in the command line mode:
pmcmd AbortTask
<<-service|-sv> service [<-domain|-d> domain] [<-timeout|-t> timeout]>
<<-user|-u> username|<-uservar|-uv> userEnvVar>
[<<-usersecuritydomain|-usd> usersecuritydomain|<-usersecuritydomainvar|-usdv>
userSecuritydomainEnvVar>]
[<-folder|-f> folder]
<-workflow|-w> workflow
[<-runinsname|-rin> runInsName]
[-wfrunid workflowRunId]
[-wait|-nowait]
taskInstancePath
The AbortTask command uses the following syntax in the interactive mode:
AbortTask
[-wait|-nowait]
taskInstancePath
The following table describes pmcmd AbortTask options and arguments:
Option
Argument
Description
-service
service
Required in command line mode. Integration Service name.

Not used in interactive mode.
domain
Optional in command line mode. Domain name. Not used in

interactive mode.
timeout
Optional in command line mode. Amount of time, in

seconds, pmcmd attempts to connect to the Integration
Service. Not used in interactive mode.
-sv
-domain
-d
-timeout
-t
If the -timeout option is omitted, pmcmd uses the timeout

value specified in the environment variable
INFA_CLIENT_RESILIENCE_TIMEOUT. If the environment
variable is not set, pmcmd uses the default timeout value.
Default is 180.
AbortTask
939
Option
Argument
Description
-user
username
Required in command line mode if you do not specify the

user name environment variable. User name. Not used in
interactive mode.
userEnvVar

user name. Specifies the user name environment variable.
password

password environment variable. Password. Not used in
interactive mode.
passwordEnvVar

password. Password environment variable. Not used in
interactive mode.
usersecuritydomain
Optional in command line mode. Required if you use LDAP

authentication. Name of the security domain that the user
belongs to. Not used in interactive mode. Default is Native.
-usdv
userSecuritydomainE
nvVar
Optional in command line mode. Security domain

environment variable. Not used in interactive mode.
-folder
folder
Required if the task name is not unique in the repository.

Name of the folder containing the task.
workflow
Optional. Configures the wait mode:
-u
-uservar
-uv
-password
-p
-passwordvar
-pv
-usersecuritydomain
-usd
-usersecuritydomainvar
-f
-workflow
-w
-wait
- wait. You can enter a new pmcmd command only after the
- nowait. You can enter a new pmcmd command after the
Integration Service receives the previous command.
-nowait
Default is nowait.
-runinsname
runInsName
Name of the workflow run instance that contains the task

you want to abort. Use this option if you are running
concurrent workflows.
-wfrunid
workflowRunId

that contains the task you want to abort. Use this option if
you are running concurrent workflows.
Note: Use this option if the workflow does not have a
unique run instance name.
taskInstancePath
Specifies a task name and where it appears within the

workflow. If the task is within a workflow, enter the task
name alone. If the task is within a worklet, enter
WorkletName.TaskName. Enter the taskInstancePath as a
fully qualified string.
-rn
940
abortworkflow
Aborts a workflow. Issue this command only if the Integration Service fails to stop the workflow when you
issue the stopworkflow command.
The abortworkflow command uses the following syntax in the command line mode:
pmcmd abortworkflow
[-wait|-nowait]
workflow
The abortworkflow command uses the following syntax in the interactive mode:
abortworkflow
[-wait|-nowait]
workflow
The following table describes pmcmd abortworkflow options and arguments:
Option
Argument
Description
-service
service
Required in command line mode. Integration Service name.

domain
Optional in command line mode. Domain name. Not used in

interactive mode.
timeout
Optional in command line mode. Amount of time, in

seconds, pmcmd attempts to connect to the Integration
Service. Not used in interactive mode.
-sv
-domain
-d
-timeout
-t

Default is 180.
abortworkflow
941
Option
Argument
Description
-user
username

interactive mode.
userEnvVar
Specifies the user name environment variable.
-u
-uservar
-uv

user name. Not used in interactive mode.
-password
password

interactive mode.
passwordEnvVar

interactive mode.
usersecuritydomain

-usdv
userSecuritydomainE
nvVar

-folder
folder
Required if the workflow name is not unique in the

repository. Name of the folder containing the workflow.
-p
-passwordvar
-pv
-usersecuritydomain
-usd
-f
-wait
-nowait
Default is nowait.
-runinsname
runInsName
Name of the workflow run instance you want to abort. Use

this option if you are running concurrent workflows.
-wfrunid
workflowRunId

you want to abort. Use this option if you are running
workflow
-rin
Connect
Connects the pmcmd program to the Integration Service in the interactive mode. If you omit connection
information, pmcmd prompts you to enter the correct information. Once pmcmd successfully connects, you
can issue commands without reentering the connection information.
Connect
942

Note: Use this command in the pmcmd interactive mode only.
The following table describes pmcmd Connect options and arguments:
Option
Argument
Description
-service
service
Required. Integration Service name.
domain
Optional. Domain name.
timeout
Optional. Amount of time, in seconds, pmcmd attempts to

connect to the Integration Service.
-sv
-domain
-d
-timeout
-t

Default is 180.
-user
username
-u
-uservar
userEnvVar
-uv
-password
password

interactive mode.
passwordEnvVar

interactive mode.
usersecuritydomain

userSecuritydomainE
nvVar

-pv
-usersecuritydomain
-usd
-usdv

-p
-passwordvar

interactive mode.
Connect
943
Disconnect
Disconnects pmcmd from the Integration Service. It does not close the pmcmd program. Use this command
when you want to disconnect from an Integration Service and connect to another in the interactive mode.
The Disconnect command uses the following syntax in the interactive mode:
Disconnect
Exit
Disconnects pmcmd from the Integration Service and closes the pmcmd program.
The Exit command uses the following syntax in the interactive mode:
Exit
GetRunningSessionsDetails
Returns the following details for all sessions currently running on an Integration Service:
Integration Service status, startup time, and current time
Folder and workflow name
Worklet and session instance
For each running session: task type, start time, run status, first error code, associated Integration Service,
run mode, and node name
For the mapping in a running session: mapping name, session log file, first error code and error message,
number of source and target success and failed rows, and number of transformation error messages
Number of sessions running on the Integration Service
The GetRunningSessionsDetails command uses the following syntax in the command line mode:
pmcmd GetRunningSessionsDetails
The GetRunningSessionsDetails command uses the following syntax in the interactive mode:
GetRunningSessionsDetails
944
The following table describes pmcmd GetRunningSessionsDetails options and arguments:

Option
Argument
Description
-service
service
domain
timeout

-sv
-domain
-d
-timeout
-t

Default is 180.
-user
username

interactive mode.
userEnvVar
-u
-uservar
-uv
-password

password

interactive mode.
passwordEnvVar

interactive mode.
usersecuritydomain

userSecuritydomainE
nvVar

-p
-passwordvar
-pv
-usersecuritydomain
-usd
-usdv
GetServiceDetails
Returns the following details about an Integration Service:
Integration Service name, status, startup time, and current time
For each active workflow: folder name, workflow name, version, run status, first error code, start time, log
file, run type, user that runs the workflow
For each active task: folder name, workflow name and version, task instance name and version, task type,
start and end time, run status, first error code, error message, associated Integration Service, run mode,
names of nodes where the task runs
Number of scheduled, active, and waiting workflows and sessions
GetServiceDetails
945
The GetServiceDetails command uses the following syntax in the command line mode:
pmcmd GetServiceDetails
[-all|-running|-scheduled]
The GetServiceDetails command uses the following syntax in the interactive mode:
GetServiceDetails
[-all|-running|-scheduled]
The following table describes pmcmd GetServiceDetails options and arguments:
Option
Argument
Description
-service
service
domain
timeout

-sv
-domain
-d
-timeout
-t

Default is 180.
-user
username
-u
-uservar
userEnvVar
-uv
-password
password

interactive mode.
passwordEnvVar

interactive mode.
usersecuritydomain

-pv
-usersecuritydomain
-usd
946

-p
-passwordvar

interactive mode.
Option
Argument
Description
-usdv
userSecuritydomainE
nvVar

-all
-running
-scheduled
Optional. Specifies the workflows to return details for:

- all. Returns status details on the scheduled and running
workflows.
- running. Returns status details on active workflows. Active
workflows include running, suspending, and suspended
workflows.
- scheduled. Returns status details on the scheduled
workflows.
Default is all.
GetServiceProperties
Returns the following information about the PowerCenter Integration Service:
Domain in which the PowerCenter Integration Service runs
PowerCenter Integration Service name and version
Whether the PowerCenter Integration Service allows running debug mappings
Data movement mode
Associated repository service
Current timestamp and startup time
Grid name
Names, nodes, and code pages for the associated PowerCenter Integration Service processes
Operating mode for the PowerCenter Integration Service
The GetServiceProperties command uses the following syntax in the command line mode:
pmcmd GetServiceProperties
The GetServiceProperties command uses the following syntax in the interactive mode:
947
The following table describes pmcmd GetServiceProperties options and arguments:

Option
Argument
Description
-service
service
Required. PowerCenter Integration Service name.
domain
timeout

connect to the PowerCenter Integration Service.
-sv
-domain
-d
-timeout
-t

Default is 180.
getsessionstatistics
Returns session details and statistics. The command returns the following information:
Folder name, workflow name, worklet or session instance, and mapping name
Session log file name and location
Number of source and target success and failure rows
Number of transformation errors
First error code and error message
Task run status
Name of associated Integration Service
Grid and node names where the session runs
The command also returns the following information for each partition:
Partition name
For each transformation within a partition: transformation instance, transformation name, number of
applied, affected, and rejected rows, throughput, last error code, start and end time
The getsessionstatistics command uses the following syntax in the command line mode:
pmcmd getsessionstatistics
948
taskInstancePath
The getsessionstatistics command uses the following syntax in the interactive mode:
taskInstancePath
The following table describes pmcmd getsessionstatistics options and arguments:
Option
Argument
Description
-service
service
domain
timeout

-sv
-domain
-d
-timeout
-t

Default is 180.
-user
username
-u
-uservar
userEnvVar
-uv
-password
password

interactive mode.
passwordEnvVar

interactive mode.
usersecuritydomain
Required if you use LDAP authentication. Optional in

command line mode. Name of the security domain that the
user belongs to. Not used in interactive mode. Default is
Native.
userSecuritydomainE
nvVar

-pv
-usersecuritydomain
-usd
-usdv

-p
-passwordvar

interactive mode.
949
Option
Argument
Description
-folder
folder

runInsName
Name of the workflow run instance that contains the task.

Use this option if you are running concurrent workflows.
-wfrunid
workflowRunId

that contains the task. Use this option if you are running
-workflow
workflow
taskInstancePath
Required. Specifies a task name and where it appears

within the workflow. If the task is within a workflow, enter
the task name alone. If the task is within a worklet, enter
-f
-runinsname
-rn
-w
-
GetTaskDetails
Returns the following information about a task:
Folder name, workflow name, task instance name, and task type
Last execution start and complete time
Task run status, first error code, and error message
Grid and node names where the task runs
Task run mode
If the task is a session, the command also returns the following details:
Mapping and session log file name
First error code and message
Source and target success and failed rows
Number of transformation errors
The GetTaskDetails command uses the following syntax in the command line mode:
pmcmd GetTaskDetails
<<-service|-sv> service [<-domain|-d> domain] [<-timeout|-t> timeout]> <<-user|-u>
username|<-uservar|-uv> userEnvVar>
950
taskInstancePath
The GetTaskDetails command uses the following syntax in the interactive mode:
GetTaskDetails
taskInstancePath
The following table describes pmcmd GetTaskDetails options and arguments:
Option
Argument
Description
-service
service
domain
timeout

-sv
-domain
-d
-timeout
-t

Default is 180.
-user
username

interactive mode.
userEnvVar
-u
-uservar
-uv
-password

password

interactive mode.
passwordEnvVar

interactive mode.
usersecuritydomain

userSecuritydomainE
nvVar

-p
-passwordvar
-pv
-usersecuritydomain
-usd
-usdv
GetTaskDetails
951
Option
Argument
Description
-folder
folder

workflow

runInsName

taskInstancePath

-f
-workflow
-w
-runinsname
-rn
-
GetWorkflowDetails
Returns the following information about a workflow:
Folder and workflow names
Workflow run status
First error code and error message
Start and end times
Log file name
Workflow run type
Name of user that last ran the workflow
The GetWorkflowDetails command uses the following syntax in the command line mode:
pmcmd GetWorkflowDetails
workflow
The GetWorkflowDetails command uses the following syntax in the interactive mode:
GetWorkflowDetails
952
workflow
The following table describes pmcmd GetWorkflowDetails options and arguments:
Option
Argument
Description
-service
service
domain
timeout

-sv
-domain
-d
-timeout
-t

Default is 180.
-user
username
-u
-uservar
userEnvVar
-uv
-password

interactive mode.
password

interactive mode.
passwordEnvVar

interactive mode.
usersecuritydomain

-usdv
userSecuritydomainE
nvVar

-folder
folder

runInsName

are running concurrent workflows.
-p
-passwordvar
-pv
-usersecuritydomain
-usd
-f
-runinsname
-rin
GetWorkflowDetails
953
Option
Argument
Description
-wfrunid
workflowRunId
Run identifier number (Run ID) of the workflow run

instance. Use this option if you are running concurrent
workflows.
workflow
Name of the workflow.
The following table describes the different statuses for workflows:
954
Status Name
Description
Aborted
You choose to abort the workflow or task in the Workflow Monitor or through pmcmd. The
Integration Service kills the DTM process and aborts the task. You can recover an aborted
workflow if you enable the workflow for recovery.
Aborting
The Integration Service is in the process of aborting the workflow.
Disabled
You select the Disabled option in the workflow properties. The Integration Service does not run
the disabled workflow until you clear the Disabled option.
Failed
The Integration Service fails the workflow because it encountered errors. You cannot recover a
failed workflow.
Preparing to
Run
The Integration Service is waiting for an execution lock for the workflow.
Running
The Integration Service is running the workflow.
Scheduled
You schedule the workflow to run at a future date. The Integration Service runs the workflow for
the duration of the schedule.
Stopped
You choose to stop the workflow or task in the Workflow Monitor or through pmcmd. The
Integration Service stops processing the task and all other tasks in its path. The Integration
Service continues running concurrent tasks. You can recover a stopped workflow if you enable
the workflow for recovery.
Stopping
The Integration Service is in the process of stopping the workflow.
Succeeded
The Integration Service successfully completes the workflow.
Suspended
The Integration Service suspends the workflow because a task failed and no other tasks are
running in the workflow. This status is available when you select the Suspend on Error option.
You can recover a suspended workflow.
Suspending
A task fails in the workflow when other tasks are still running. The Integration Service stops
running the failed task and continues running tasks in other paths. This status is available when
you select the Suspend on Error option.
Terminated
The Integration Service shuts down unexpectedly when running this workflow or task. You can
recover a terminated workflow if you enable the workflow for recovery.
Terminating
The Integration Service is in the process of terminating the workflow or task.
Status Name
Unknown
Status
Description
This status displays in the following situations:
- The Integration Service cannot determine the status of the workflow or task.
- The Integration Service does not respond to a ping from the Workflow Monitor.
- The Workflow Monitor cannot connect to the Integration Service within the resilience timeout
period.
Unscheduled
You remove a workflow from the schedule.
Waiting
The Integration Service is waiting for available resources so it can run the workflow or task. For
example, you may set the maximum number of running Session and Command tasks allowed
for each Integration Service process on the node to 10. If the Integration Service is already
running 10 concurrent sessions, all other workflows and tasks have the Waiting status until the
Integration Service is free to run more tasks.
The GetWorkflowDetails command displays the last workflow run type details. Workflow run types refers to
the method used to start the workflow.
The following table describes the different workflow run types with the GetWorkflowDetails command:
Workflow Run
Types
Description
User Request
Manually started a workflow.
Schedule
Workflow runs at the scheduled time.
Help
Returns the syntax for the command you specify. If you omit the command name, pmcmd lists all commands
and their syntax.
The Help command uses the following syntax in the command line mode:
pmcmd Help [command]
The Help command uses the following syntax in the interactive mode:
Help [command]
The following table describes the pmcmd Help option and argument:
Option
Argument
Description
command
Optional. Name of command. If you omit the command

name, pmcmd lists all commands and their syntax.
Help
955
PingService
Verifies that the Integration Service is running.
The PingService command uses the following syntax in the command line mode:
pmcmd PingService
The PingService command uses the following syntax in the interactive mode:
PingService
The following table describes pmcmd PingService options and arguments:
Option
Argument
Description
-service
service
domain
timeout

-sv
-domain
-d
-timeout
-t

Default is 180.
RecoverWorkflow
Recovers suspended workflows. To recover a workflow, specify the folder and workflow name. The
Integration Service recovers the workflow from all suspended and failed worklets and all suspended and
failed Command, Email, and Session tasks.
The RecoverWorkflow command uses the following syntax in the command line mode:
pmcmd RecoverWorkflow
[<-paramfile> paramfile]
[<-localparamfile|-lpf> localparamfile]
[-wait|-nowait]
956
workflow
The RecoverWorkflow command uses the following syntax in the interactive mode:
RecoverWorkflow
[-wait|-nowait]
workflow
The following table describes pmcmd RecoverWorkflow options and arguments:
Option
Argument
Description
-service
service
domain
timeout

-sv
-domain
-d
-timeout
-t

Default is 180.
-user
username

interactive mode.
userEnvVar
-u
-uservar
-uv
-password

password

interactive mode.
passwordEnvVar

interactive mode.
usersecuritydomain

-p
-passwordvar
-pv
-usersecuritydomain
-usd
RecoverWorkflow
957
Option
Argument
Description
-usdv
userSecuritydomainE
nvVar

-folder
folder

-paramfile
paramfile
Optional. Determines which parameter file to use when a

task or workflow runs. It overrides the configured parameter
file for the workflow or task.
-localparamfile
localparamfile
Optional. Specifies the parameter file on a local machine

that pmcmd uses when you start a workflow.
-f
-lpf
-wait
-nowait
Default is nowait.
-runinsname
runInsName
Name of the workflow run instance you want to recover.

-wfrunid
workflowRunId

you want to recover. Use this option if you are running
workflow
-rin
ScheduleWorkflow
Instructs the Integration Service to schedule a workflow. Use this command to reschedule a workflow that has
been removed from the schedule.
The ScheduleWorkflow command uses the following syntax in the command line mode:
pmcmd ScheduleWorkflow
workflow
958
The ScheduleWorkflow command uses the following syntax in the interactive mode:
ScheduleWorkflow
workflow
The following table describes pmcmd ScheduleWorkflow options and arguments:
Option
Argument
Description
-service
service
domain
timeout

-sv
-domain
-d
-timeout
-t

Default is 180.
-user
username
-u
-uservar
userEnvVar
-uv
-password

interactive mode.
password

interactive mode.
passwordEnvVar

interactive mode.
usersecuritydomain

-usdv
userSecuritydomainE
nvVar

-folder
folder

workflow
-p
-passwordvar
-pv
-usersecuritydomain
-usd
-f
-
ScheduleWorkflow
959
SetFolder
Designates a folder as the default folder in which to execute all subsequent commands. After issuing this
command, you do not need to enter a folder name for workflow, task, and session commands. If you enter a
folder name in a command after the SetFolder command, that folder name overrides the default folder name
for that command only.
The SetFolder command uses the following syntax in the interactive mode:
SetFolder folder
The following table describes pmcmd SetFolder option and argument:
Option
Argument
Description
folder
Required. Name of the folder.
SetNoWait
completes. In nowait mode, pmcmd returns to the shell or command prompt immediately. You do not have to
wait for one command to complete before running the next command.
The SetNoWait command runs pmcmd in nowait mode. The nowait mode is the default mode.
The SetNoWait command uses the following syntax in the interactive mode:
SetNoWait
When you set nowait mode, use the pmcmd prompt after the Integration Service executes the previous
command.
SetWait
completes. In nowait mode, pmcmd returns to the shell or command prompt immediately. You do not have to
wait for one command to complete before running the next command.
The SetWait command runs pmcmd in wait mode. The pmcmd prompt is available after the Integration
Service completes the previous command.
The SetWait command uses the following syntax in the interactive mode:
SetWait
960
ShowSettings
Returns the name of the domain, Integration Service, and repository to which pmcmd is connected. It
displays the user name, wait mode, and default folder.
The ShowSettings command uses the following syntax in the interactive mode:
ShowSettings
StartTask
Starts a task.
The StartTask command uses the following syntax in the command line mode:
pmcmd StartTask
[-wait|-nowait]
[<-recovery|-norecovery>]
taskInstancePath
The StartTask command uses the following syntax in the interactive mode:
pmcmd StartTask
<-paramfile> paramfile]
[-wait|-nowait]
taskInstancePath
ShowSettings
961
The following table describes pmcmd StartTask options and arguments:

Option
Argument
Description
-service
service
domain
timeout

-sv
-domain
-d
-timeout
-t

Default is 180.
-user
username

interactive mode.
userEnvVar
-u
-uservar
-uv
-password

password

interactive mode.
passwordEnvVar

interactive mode.
usersecuritydomain

-usdv
userSecuritydomainE
nvVar

-folder
folder

workflow
-paramfile
paramfile

task or workflow runs. It overrides the configured parameter
file for the workflow or task.
-wait
-p
-passwordvar
-pv
-usersecuritydomain
-usd
-f
-workflow
-w
-nowait
Default is nowait.
962
Option
Argument
Description
-recovery
Optional. If the task is a session, the Integration Service

runs the session based on the configured recovery
strategy.
-norecovery
- recovery. For real-time sessions that are enabled for

recovery, the Integration Service recovers the failed session
and stops running the rest of the tasks in the workflow.
The recovery option is the same as the Recover Task option
in the Workflow Manager. This option is not applicable for
sessions that do not have recovery enabled.
- norecovery. For real-time sessions that are enabled for
recovery, the Integration Service does not process recovery
data. The Integration Service clears the state of operation
and the recovery file or table before it restarts the task. For
the sessions that do not have recovery enabled, the
Integration Service clears the state of operation and restarts
the task.
The norecovery option is the same as the Cold Start Task
option in the Workflow Manager.
If you do not provide any option for recovery enabled

sessions, the Integration Service runs the session in
recovery mode. If you do not provide any option for the
sessions that do not have recovery enabled, the Integration
Service runs the session in norecovery mode.
-runinsname
runInsName

you want to start. Use this option if you are running
taskInstancePath

-rn
-
Using Parameter Files with starttask

When you start a task, you can optionally enter the directory and name of a parameter file. The Integration
Service runs the task using the parameters in the file you specify.
For UNIX shell users, enclose the parameter file name in single quotes:
-paramfile '$PMRootDir/myfile.txt'
For Windows command prompt users, the parameter file name cannot have beginning or trailing spaces. If
the name includes spaces, enclose the file name in double quotes:
-paramfile "$PMRootDir\my file.txt"
When you write a pmcmd command that includes a parameter file located on another machine, use the
backslash (\) with the dollar sign ($). This ensures that the machine where the variable is defined expands
the process variable.
pmcmd starttask -sv MyIntService -d MyDomain -uv USERNAME -pv PASSWORD f east -w
wSalesAvg -paramfile '\$PMRootDir/myfile.txt' taskA
StartTask
963
StartWorkflow
Starts a workflow.
The StartWorkflow command uses the following syntax in the command line mode:
pmcmd StartWorkflow
[<-startfrom> taskInstancePath]
[<-osprofile|-o> OSUser]
[-wait|-nowait]
workflow
The StartWorkflow command uses the following syntax in the interactive mode:
pmcmd StartWorkflow
[<-startfrom> taskInstancePath [<-recovery|-norecovery>]]
[<-osprofile|-o> osProfile]
[-wait|-nowait]
workflow
The following table describes pmcmd StartWorkflow options and arguments:
Option
Argument
Description
-service
service
domain
-sv
-domain
-d
964
Option
Argument
Description
-timeout
timeout

-t

INFA_CLIENT_RESILIENCE_TIMEOUT. If the
environment variable is not set, pmcmd uses the default
timeout value. Default is 180.
-user
username
-u
-uservar
userEnvVar
-uv
-password

interactive mode.
password

interactive mode.
passwordEnvVar

interactive mode.
usersecuritydomain
Optional in command line mode. Required if you use

LDAP authentication. Name of the security domain that
the user belongs to. Not used in interactive mode. Default
is Native.
-usdv
userSecuritydomainEn
vVar

-folder
folder

taskInstancePath
Optional. Starts a workflow from a specified task,

taskInstancePath. If the task is within a workflow, enter
-p
-passwordvar
-pv
-usersecuritydomain
-usd
-f
-startfrom
If you do not specify a starting point, the workflow starts at

the Start task.
If the task is a session, specify -recovery or -norecovery
option to run the session based on the configured
recovery strategy.
-paramfile
paramfile

task or workflow runs. It overrides the configured
parameter file for the workflow or task.
StartWorkflow
965
Option
Argument
Description
-recovery
Optional. The Integration Service runs the session based

on the configured recovery strategy.
-norecovery
- recovery. For real-time sessions that are enabled for

recovery, the Integration Service recovers the failed
session and stops running the rest of the tasks in the
workflow.
The recovery option is the same as the Recover Workflow
option in the Workflow Manager. This option is not
applicable for sessions that do not have recovery enabled.
- norecovery. For real-time sessions that are enabled for
recovery, the Integration Service does not process
recovery data. The Integration Service clears the state of
operation and the recovery file or table before it restarts the
task. For the sessions that do not have recovery enabled,
the Integration Service clears the state of operation and
restarts the task.
The norecovery option is the same as the Cold Start
Workflow option in the Workflow Manager.
If you do not provide any option for recovery enabled

sessions, the Integration Service runs the session in
recovery mode. If you do not provide any option for the
sessions that do not have recovery enabled, the
Integration Service runs the session in norecovery mode.
-localparamfile
localparamfile
Optional. Specifies the parameter file on a local machine

that pmcmd uses when you start a workflow.
osProfile
Optional. Specifies the operating system profile assigned

to the workflow.
-lpf
-osprofile
-o
-wait
-nowait
Default is nowait.
-runinsname
runInsName
Name of the workflow run instance you want to start. Use

workflow
-rin
-
Using Parameter Files with startworkflow

When you start a workflow, you can optionally enter the directory and name of a parameter file. The
Integration Service runs the workflow using the parameters in the file you specify. For UNIX shell users,
enclose the parameter file name in single quotes. For Windows command prompt users, the parameter file
name cannot have beginning or trailing spaces. If the name includes spaces, enclose the file name in double
quotes.
966
Use parameter files on the following machines:
Node running the Integration Service. When you use a parameter file located on the Integration Service
machine, use the -paramfile option to indicate the location and name of the parameter file.
On UNIX, use the following syntax:
-paramfile '$PMRootDir/myfile.txt'
On Windows, use the following syntax:
-paramfile "$PMRootDir\my file.txt"
Local machine. When you use a parameter file located on the machine where pmcmd is invoked, pmcmd
passes variables and values in the file to the Integration Service. When you list a local parameter file,
specify the absolute path or relative path to the file. Use the -localparamfile or -lpf option to indicate the
location and name of the local parameter file.
On UNIX, use the following syntax:
-lpf 'param_file.txt'
-lpf 'c:\Informatica\parameterfiles\param file.txt'
-localparamfile 'c:\Informatica\parameterfiles\param file.txt'
On Windows, use the following syntax:
-lpf param_file.txt
-lpf "c:\Informatica\parameterfiles\param file.txt
-localparamfile param_file.txt
Shared network drives. When you use a parameter file located on another machine, use the backslash
(\) with the dollar sign ($). This ensures that the machine where the variable is defined expands the
process variable.
-paramfile '\$PMRootDir/myfile.txt'
StopTask
Stops a task.
The StopTask command uses the following syntax in the command line mode:
pmcmd StopTask
[-wait|-nowait]
taskInstancePath
StopTask
967
The StopTask command uses the following syntax in the interactive mode:
pmcmd StopTask
[-wait|-nowait]
taskInstancePath
The following table describes pmcmd StopTask options and arguments:
Option
Argument
Description
-service
service
domain
timeout

-sv
-domain
-d
-timeout
-t

Default is 180.
-user
username
-u
-uservar
userEnvVar
-uv
-password

password

interactive mode.
passwordEnvVar

interactive mode.
usersecuritydomain

-usdv
userSecuritydomainE
nvVar

-folder
folder

-p
-passwordvar
-pv
-usersecuritydomain
-usd
-f
968

interactive mode.
Option
Argument
Description
-workflow
workflow
runInsName

you want to stop. Use this option if you are running
-wfrunid
workflowRunId

that contains the task you want to stop. Use this option if
you are running concurrent workflows.
-wait
-w
-runinsname
-rn
-nowait
Default is nowait.
-
taskInstancePath

StopWorkflow
Stops a workflow.
The StopWorkflow command uses the following syntax in the command line mode:
pmcmd StopWorkflow
[-wait|-nowait]
workflow
The StopWorkflow command uses the following syntax in the interactive mode:
pmcmd StopWorkflow
StopWorkflow
969
[-wait|-nowait]
workflow
The following table describes pmcmd StopWorkflow options and arguments:
Option
Argument
Description
-service
service
domain
timeout

-sv
-domain
-d
-timeout
-t

Default is 180.
-user
username
-u
-uservar
userEnvVar
-uv
-password

password

interactive mode.
passwordEnvVar

interactive mode.
usersecuritydomain

-usdv
userSecuritydomainE
nvVar

-folder
folder

runInsName
Name of the workflow run instance you want to stop. Use

-p
-passwordvar
-pv
-usersecuritydomain
-usd
-f
-runinsname
-rin
970

interactive mode.
Option
Argument
Description
-wfrunid
workflowRunId

you want to stop. Use this option if you are running
-wait

-nowait
Default is nowait.
-
workflow
UnscheduleWorkflow
Removes a workflow from a schedule.
The UnscheduleWorkflow command uses the following syntax in the command line mode:
pmcmd UnscheduleWorkflow
workflow
The UnscheduleWorkflow command uses the following syntax in the interactive mode:
UnscheduleWorkflow
workflow
The following table describes pmcmd UnscheduleWorkflow options and arguments:
Option
Argument
Description
-service
service
domain
-sv
-domain
-d
UnscheduleWorkflow
971
Option
Argument
Description
-timeout
timeout

-t

Default is 180.
-user
username
-u
-uservar
userEnvVar
-uv

interactive mode.
-password
password

interactive mode.
passwordEnvVar

interactive mode.
usersecuritydomain

-usdv
userSecuritydomainE
nvVar

-folder
folder

workflow
-p
-passwordvar
-pv
-usersecuritydomain
-usd
-f
-
UnsetFolder
Removes the designation of a default folder. After you issue this command, you must specify a folder name
each time you enter a command for a session, workflow, or task.
The UnsetFolder command uses the following syntax in the interactive mode:
UnsetFolder
972
Version
The Version command uses the following syntax in the command line mode:
pmcmd Version
The Version command uses the following syntax in the interactive mode:
Version
WaitTask
Instructs the Integration Service to complete the task before returning the pmcmd prompt to the command
prompt or shell.
The WaitTask command uses the following syntax in the command line mode:
pmcmd WaitTask
taskInstancePath
The WaitTask command uses the following syntax in the interactive mode:
WaitTask
taskInstancePath
Version
973
The following table describes pmcmd WaitTask options and arguments:

Option
Argument
Description
-service
service
domain
timeout

-sv
-domain
-d
-timeout
-t

Default is 180.
-user
username

interactive mode.
userEnvVar
-u
-uservar
-uv
-password

password

interactive mode.
passwordEnvVar

interactive mode.
usersecuritydomain

-usdv
userSecuritydomainE
nvVar

-folder
folder

workflow
runInsName

-p
-passwordvar
-pv
-usersecuritydomain
-usd
-f
-workflow
-w
-runinsname
-rn
974
Option
Argument
Description
-wfrunid
workflowRunId

that contains the task. Use this option if you are running
taskInstancePath

WaitWorkflow
Causes pmcmd to wait for a workflow to complete before it executes subsequent commands. Use this
command in conjunction with the return code when you run pmcmd from a script. For example, you may want
to check the status of a critical workflow before starting another workflow. Use the WaitWorkflow command to
wait for the critical workflow to complete, and then check the pmcmd return code. If the return code is 0
(successful), start the next workflow.
The WaitWorkflow command returns the prompt when a workflow completes.
The WaitWorkflow command uses the following syntax in the command line mode:
pmcmd WaitWorkflow
workflow
The WaitWorkflow command uses the following syntax in the interactive mode:
WaitWorkflow
workflow
WaitWorkflow
975
The following table describes pmcmd WaitWorkflow options and arguments:

Option
Argument
Description
-service
service
domain
timeout

-sv
-domain
-d
-timeout
-t

Default is 180.
-user
username

interactive mode.
userEnvVar
-u
-uservar
-uv
-password

password

interactive mode.
passwordEnvVar

interactive mode.
usersecuritydomain

-usdv
userSecuritydomainE
nvVar

-folder
folder

runInsName

are running concurrent workflows.
-wfrunid
workflowRunId
Run identifier number (Run ID) of the workflow run

instance. Use this option if you are running concurrent
workflows.
workflow
-p
-passwordvar
-pv
-usersecuritydomain
-usd
-f
-runinsname
-rin
976
CHAPTER 31
pmrep Command Reference

Using pmrep, 978
AddToDeploymentGroup, 981
ApplyLabel, 982
AssignPermission, 984
BackUp, 986
ChangeOwner, 987
CheckIn, 988
CleanUp, 988
ClearDeploymentGroup, 989
Connect, 989
Create, 991
CreateConnection, 991
CreateDeploymentGroup, 997
CreateFolder, 997
CreateLabel, 999
Delete, 999
DeleteConnection, 1000
DeleteDeploymentGroup, 1000
DeleteFolder, 1001
DeleteLabel, 1001
DeleteObject , 1001
DeployDeploymentGroup, 1002
DeployFolder, 1004
ExecuteQuery, 1005
Exit, 1007
FindCheckout, 1007
GetConnectionDetails, 1008
GenerateAbapProgramToFile, 1009
Help, 1011
InstallAbapProgram, 1011
977
KillUserConnection, 1013
ListConnections, 1014
ListObjectDependencies , 1014
ListObjects, 1017
ListTablesBySess, 1022
ListUserConnections, 1023
MassUpdate, 1023
ModifyFolder, 1029
Notify, 1030
ObjectExport, 1031
ObjectImport , 1033
PurgeVersion, 1033
Register, 1036
RegisterPlugin, 1037
Restore, 1039
RollbackDeployment , 1040
Run, 1041
ShowConnectionInfo, 1042
SwitchConnection, 1042
TruncateLog, 1043
UndoCheckout, 1044
Unregister, 1045
UnregisterPlugin, 1046
UpdateConnection, 1048
UpdateEmailAddr, 1049
UpdateSeqGenVals, 1050
UpdateSrcPrefix, 1051
UpdateStatistics , 1052
UpdateTargPrefix, 1052
Upgrade, 1053
UninstallAbapProgram, 1054
Validate, 1055
Version, 1057
Using pmrep
pmrep is a command line program that you use to update repository information and perform repository
functions. pmrep is installed in the PowerCenter Client and PowerCenter Services bin directories.
978
Chapter 31: pmrep Command Reference
Use pmrep to perform repository administration tasks such as listing repository objects, creating and editing
groups, restoring and deleting repositories, and updating session-related parameters and security information
in the PowerCenter repository.
When you use pmrep, you can enter commands in the following modes:
Command line mode. You can issue pmrep commands directly from the system command line. Use
command line mode to script pmrep commands.
Interactive mode. You can issue pmrep commands from an interactive prompt. pmrep does not exit after
it completes a command.
You can use environment variables to set user names and passwords for pmrep. Before you use pmrep,
configure these variables. The environment variables apply to pmrep commands that run on the node.
All pmrep commands require a connection to the repository except for the following commands:
Help
ListAllPrivileges
Use the pmrep Connect command to connect to the repository before using other pmrep commands.
Note: If the domain is a mixed-version domain, run pmrep from the installation directory of the Repository
Service version.
Running Commands in Command Line Mode

Command line mode invokes and exits pmrep each time you issue a command. Command line mode is
useful if you want to run pmrep commands through batch files, scripts, or other programs.
To run pmrep commands in command line mode:
1.
At the command prompt, change to the directory where the pmrep executable is located.
2.
Enter pmrep followed by the command name and its options and arguments:
pmrep command_name [-option1] argument_1 [-option2] argument_2...
Running Commands in Interactive Mode

Interactive mode invokes pmrep. You can issue a series of commands from a pmrep prompt without exiting
after each command.
To run pmrep commands in interactive mode:
1.
At the command prompt, enter pmrep to invoke interactive mode.

This starts pmrep in interactive mode and displays a pmrep> prompt. You do not have to type pmrep
before each command in interactive mode.
2.
Enter a command and its options and arguments.

At the prompt, enter:
command_name [-option1] argument_1 [-option2] argument_2...
pmrep runs the command and displays the prompt again.
3.
Type exit to end an interactive session.
Running Commands in Normal Mode and Exclusive Mode

The Repository Service runs in normal or exclusive mode. Run the Repository Service in exclusive mode to
perform tasks that permit only one user connection to the repository.
Using pmrep
979
Run the Repository Service in exclusive mode to use the following pmrep commands:
Create
Delete
Register
RegisterPlugin
Unregister
UnregisterPlugin
You can use the Administrator tool or infacmd to run the Repository Service in exclusive mode.
pmrep Return Codes

pmrep indicates the success or failure of a command with a return code. Return code 0 indicates that the
command succeeded. Return code 1 indicates that the command failed. Some commands perform multiple
operations. For example, AddToDeploymentgroup adds multiple objects to a deployment group. In these
cases, a Return code 0 indicates that the command was executed successfully even if only some of the
objects were deployed successfully.
Enter one of the following DOS or UNIX echo commands immediately after running the pmrep command:
In a DOS shell, enter echo %ERRORLEVEL%
In a UNIX Bourne or Korn shell, enter echo $?
In a UNIX C shell, enter echo $status
Using Native Connect Strings

Some pmrep commands, such as CreateConnection and Restore, require a native connect string.
The following table describes the native connect string syntax for each supported repository database:
Database
Connect String Syntax
Example
IBM DB2
dbname
mydatabase
servername@dbname
sqlserver@mydatabase
Oracle
dbname.world (same as TNSNAMES entry)
oracle.world
Sybase ASE
servername@dbname
sambrown@mydatabase
Scripting pmrep Commands

When you use pmrep, you might use some commands with specific options and arguments on a regular
basis. For example, you might use pmrep to perform a daily backup of a production repository. In this case,
you can create a script file to call one or more pmrep commands including its options and arguments.
For example, the following Windows batch file, backupproduction.bat, connects to and backs up a
repository called Production:
backupproduction.bat
REM This batch file uses pmrep to connect to and back up the repository Production on
the server ServerName
@echo off
echo Connecting to repository Production...
980
c:\PowerCenter\pmrep\pmrep connect -r Production -n Administrator -x Adminpwd -d

MyDomain -h Machine -o 8080
echo Backing up repository Production...
c:\PowerCenter\pmrep\pmrep backup -o c:\backup\Production_backup.rep
You can run script files from the command interface. You cannot run pmrep batch files in interactive mode.
Tips for Scripting pmrep Commands

Use the following tips when you create and run pmrep scripts:
Include a Connect command as the first command called by the script file. This helps ensure that you
perform tasks on the correct repository.
To run pmrep scripts that connect to different repositories simultaneously, set the INFA_REPCNX_INFO
environment variable in each environment to store the name and file path for the repository connection
file. This prevents a script from overwriting the connection information used by another script.
AddToDeploymentGroup
Adds objects to a deployment group. Use AddToDeploymentGroup to add source, target, transformation,
mapping, session, worklet, workflow, scheduler, session configuration, and task objects.
You cannot add checked out objects to a deployment group. You can specify objects using command options
or you can use a persistent input file. If you use a persistent input file, you can enter the deployment group
name option.
Use AddToDeploymentGroup to add reusable input objects. If you want to add non-reusable input objects,
you must use a persistent input file that contains encoded object IDs.
If AddToDeploymentGroup runs successfully, it either sends back no status information, or it returns a list of
objects that are already in the deployment group. If the command fails, it displays the reason for failure.
The AddToDeploymentGroup command uses the following syntax:
addtodeploymentgroup
-p <deployment_group_name>
{{-n <object_name>
-o <object_type>
-t <object_subtype>]
[-v <version_number>]
[-f <folder_name>]} |
[-i <persistent_input_file>]}
[-d <dependency_types (all, "non-reusable", or none)>]
[-s dbd_separator]
AddToDeploymentGroup
981
The following table describes pmrep AddToDeploymentGroup options and arguments:

Option
Argument
Description
-p
deployment_group_name
Required. Name of the deployment group to add objects to.
-n
object_name
Required when you add a specific object. Name of the object you are
adding to the deployment group. You cannot enter the name of a
checked out object. You cannot use the -n option if you use the -i
option.
-o
object_type
Required when adding a specific object. Type of object you are

adding. You can specify source, target, transformation, mapping,
session, worklet, workflow, scheduler, session configuration, task,
cube, and dimension.
-t
object_subtype
Required when using valid subtypes. Type of task or transformation

you are adding. For more information about valid subtypes, see
Listing Object Types on page 1019 .
-v
version_number
Optional. Version of the object to add. Default is the latest version of

the object. The command fails if you specify a version number for a
non-versioned repository.
-f
folder_name
Required when you enter an object name. Folder that contains the
object you are adding.
-i
persistent_input_file
A text file generated from ExecuteQuery, Validate, or

ListObjectDependencies that contains a list of object records with
encoded IDs. If you use this parameter, pmrep does not allow the -n,
-o, and -f options.
-d
dependency_types
Optional. Dependent objects to add to the deployment group with the

object. Enter one of the following:
- all. pmrep adds the objects and all dependent objects, reusable and
non-reusable, to the deployment group.
- non-reusable. pmrep adds the objects and the corresponding nonreusable dependent objects to the deployment group.
- none. pmrep does not add dependent objects to the deployment group.
If you omit this parameter, pmrep adds the objects and all dependent
objects to the deployment group.
Note: Use double quotes around arguments that contain spaces or
non-alphanumeric characters.
-s
dbd_separator
Optional. If an ODBC source has a period (.) in the name, define a

different separator character when you define the source object. For
example, instead of database_name.source_name, define the source
object as database_name\source_name, and define the
dbd_separator as backslash (\).
ApplyLabel
Applies a label to an object or a set of objects in a folder. If you enter a folder name, all the objects in the
folder receive the label. You can apply the label to dependent objects. If you use the
dependency_object_types option, pmrep labels all dependent objects. To apply a label to selected
982
dependent objects, separate each object type name by a comma with no spaces between them on the
command line.
Use ApplyLabel to label reusable input objects. If you want to label non-reusable input objects, you must use
a persistent input file that contains encoded object IDs.
If ApplyLabel succeeds, pmrep displays either no status information or a list of objects that already have the
label. If the command fails, pmrep displays the reason for the failure.
The ApplyLabel command uses the following syntax:
applylabel
-a <label_name>
{{-n <object_name>
-o <object_type>
[-t <object_subtype>]
[-f <folder_name>] } |
-i <persistent_input_file>}
[-d <dependency_object_types>]
[-p <dependency_direction (children, parents, or both)>]
[-s (include pk-fk dependency)]
[-g (across repositories)]
[-m (move label)]
[-c <comments>]
[-e dbd_separator]
The following table describes pmrep ApplyLabel options and arguments:
Option
Argument
Description
-a
label_name
Required. Label name to apply to the object.
-n
object_name
Required if you are updating a specific object. Name of the object to

receive the label. You cannot enter object names if you use the -i
option.
-o
object_type
Type of object to apply the label to. You can specify source, target,
transformation, mapping, session, worklet, workflow, scheduler,
session config, task, cube, or dimension. Required when applying a
label to a specific object.
-t
object_subtype
Required. Type of task or transformation you are labeling. pmrep

ignores other object types. For more information about valid
subtypes, see Listing Object Types on page 1019 .
-v
version_number
Optional. Version of the object to apply the label to. The command
fails if the version is checked out. Applies the label to the latest
version of the object by default.
ApplyLabel
983
Option
Argument
Description
-f
folder_name
Optional. Folder that contains the objects. If you enter a folder name
but no object name, pmrep applies the label to all objects in the
folder. If you enter a folder name with an object name, pmrep
searches the folder for the object. You cannot use the -f option if you
use the -i option.
-i
Optional. Name of a text file generated from ExecuteQuery,

ListObjectDependency, or Validate. Contains a list of objects to
receive the label. If you use this option, do not use the object name,
object type, or folder name to specify objects.
-d
dependency_object_types
Optional. Dependent object types to label. Valid dependent object

types include shortcuts, mappings, mapplets, sessions, workflows,
worklets, target definitions, source definitions, and foreign key
dependencies.
Use this option with option -p. If you enter an object type, the label
applies to dependent objects of that object type.
-p
dependency_direction
Optional. Dependent parents or children to apply the label to. You

can specify parents, children, or both. If you do not enter option -d,
all dependent objects receive the label.
If you do not enter this option, the label applies to the specified
object.
-s
Optional. Include the primary key-foreign key dependency objects

regardless of the direction of the dependency.
-g
Optional. Find object dependencies across repositories.
-m
Optional. Move a label from the current version to the latest version
of an object. Use this argument when the label type is
one_per_object.
-c
comments
Optional. Comments about the label.
-e
dbd_separator

AssignPermission
Allows you to add, remove, or update permissions on a global object for a user, group, or the Others default
group.
Note: Only the administrator or the current owner of the object can manage permissions on the object.
The AssignPermission command uses the following syntax:
AssignPermission
-o <object_type>
984
-n <object_name>
{-u <user_name> | -g <group_name>}
[-s <security_domain>]
-p <permission>
The following table describes pmrep AssignPermission options and arguments:
Option
Argument
Description
-o
object_type
Required. Type of the object for which you want to manage

permissions. You can specify folder, label, deploymentgroup, query,
or connection.
-t
object_subtype
Optional. Type of connection object or query. Not required for other

object types. For more information about valid subtypes, see
AssignPermission on page 984.
-n
object_name
Required. Name of the object for which you want to manage

permissions. You can use special characters for the object name.
-u
user_name
Required if you do not use the -g option. Name of the user for whom
you want to add, remove, or update permissions. Use the -u or -g
option, not both.
-g
group_name
Name of the group for which you want to add, remove, or update
permissions. Specify Others as the group name to change
permissions for the Others default group.
Use the -u or -g option, but not both.
You can use special characters for the group name.
-s
security_domain

domain that the user or group belongs to. Default is Native.
-p
permission
Required. Permissions you want to add, remove, or update. You

assign read, write and execute permission on a global object. Use
the characters r, w, and x to assign read, write, and execute
permissions.
The following table describes the object types and values to use with pmrep commands:
Object Type
Object Subtype
Query
Shared
Query
Personal
Connection
Application
Connection
FTP
Connection
Loader
AssignPermission
985
Object Type
Object Subtype
Connection
Queue
Connection
Relational
Example
You can add, remove, or update permissions with the -p option.
For example, to add read and write permissions on a folder, enter the following text at the prompt:
pmrep AssignPermission -o folder -n Sales -u Admin -p rw
You can also update permissions on an object. For example, you assigned permission to read on a folder
and need to include permission to write. To update permissions, enter the following text at the prompt:
pmrep AssignPermission -o folder -n Sales -u Admin -p rw
To remove all permissions, enter the following text at the prompt:
pmrep AssignPermission -o folder -n Sales -u Admin -p ""
BackUp
Backs up the repository to the file specified with the -o option. You must provide the backup file name. Use
this command when the repository is running. You must be connected to a repository to use this command.
The BackUp command uses the following syntax:
backup
-o <output_file_name>
[-d <description>]
[-f (overwrite existing output file)]
[-b (skip workflow and session logs)]
[-j (skip deploy group history)]
[-q (skip MX data)]
[-v (skip task statistics)]
The following table describes pmrep BackUp options and arguments:
986
Option
Argument
Description
-o
output_file_name
Required. Name and path of the file for the repository backup. When you view
the list of repository backup files in the Administrator tool, you can see only
files with an extension of .rep.
-d
description
Optional. Creates a description of the backup file based on the string that
follows the option. The backup process truncates any character beyond
2,000.
Option
Argument
Description
-f
Optional. Overwrites an existing file with the same name.
-b
Optional. Skips tables related to workflow and session logs during backup.
-j
Optional. Skips deployment group history during backup.
-q
Optional. Skips tables related to MX data during backup.
-v
Optional. Skips task statistics during backup.
To restore the backup file, use the Administrator tool, or use the pmrep Restore command.
ChangeOwner
Changes the owner name for a global object.
Note: Only the administrator or current owner of the object have the permission to change ownership for an
object.
The ChangeOwner command uses the following syntax:
ChangeOwner
-o <object_type>
-n <object_name>
-u <new_owner_name>
[-s <security_domain>]
The following table describes pmrep ChangeOwner options and arguments:
Option
Argument
Description
-o
object_type
Required. Type of the object. You can specify folder, label,

deploymentgroup, query, or connection.
-t
object_subtype
Optional. Type of object query or connection object. Not required for other
object types. For more information about valid subtypes, see
AssignPermission on page 984.
-n
object_name
Required. Name of the object. You can use special characters for the object
name.
-u
new_owner_name
Required. Name of the changed owner. The changed owner name must be a
valid user account in the domain.
-s
security_domain
Required if you use LDAP authentication. Name of the security domain that
the new owner belongs to. Default is Native.
ChangeOwner
987
CheckIn
Checks in an object that you have checked out. When you check in an object, the repository creates a new
version of the object and assigns it a version number. The version number is one number greater than the
version number of the last checked-in version.
The CheckIn command uses the following syntax:
checkin
-o <object_type>
-n <object_name>
-f <folder_name>
[-c <comments>]
[-s dbd_separator]
The following table describes pmrep CheckIn options and arguments:
Option
Argument
Description
-o
object_type
Required. Type of object you are checking in: source, target, transformation,
mapping, session, worklet, workflow, scheduler, session config, task, cube,
or dimension.
-t
object_subtype
Optional. Type of task or transformation to check in. Not required for other
object types. For more information about valid subtypes, see Listing Object
Types on page 1019 .
-n
object_name
Required. Name of the object that you are checking in.
-f
folder_name
Required. Folder to contain the new object version.
-c
comments
Optional. Comments about the check in.
-s
dbd_separator
Optional. If an ODBC source has a period (.) in the name, define a different
separator character when you define the source object. For example,
instead of database_name.source_name, define the source object as
database_name\source_name, and define the dbd_separator as backslash
(\).
CleanUp
Cleans up any persistent resource created by pmrep. This command also cleans up any connection
information from previous sessions of pmrep. Calling CleanUp as the first command in a session always
returns an error.
If you call CleanUp in the interactive mode, pmrep disconnects any repository you are connected to.
The CleanUp command uses the following syntax:
cleanup
988
ClearDeploymentGroup
Clears all objects from a deployment group. Use this command to retain the deployment group but remove
the objects.
The ClearDeploymentGroup command uses the following syntax:
cleardeploymentgroup
[-f (force clear)]
The following table describes pmrep ClearDeploymentGroup options and arguments:
Option
Argument
Description
-p
Required. Name of the deployment group that you want to clear.
-f
Optional. Remove objects without confirmation. If you omit this

argument, the command prompts you for a confirmation before it
clears the objects.
Connect
Connects to a repository. The first time you use pmrep in either command line or interactive mode, you must
use the Connect command. All commands require a connection to the repository except for the following
commands:
Exit
Help
ListAllPrivileges
In the command line mode, pmrep uses the information specified by the last call to connect to the repository.
If pmrep is called without a successful connection, it returns an error. In command line mode, pmrep
connects to and disconnects from the repository with every command.
To use pmrep to perform tasks in multiple repositories in a single session, you must issue the Connect
command each time you want to switch to a different repository. In the interactive mode, pmrep retains the
connection until you exit pmrep or connect again. If you call Connect again, pmrep disconnects from the first
repository and then connects to the second repository. If the second connection fails, the previous connection
remains disconnected and you will not be connected to any repository. If you issue a command that requires
a connection to the repository, and you are not connected to that repository, pmrep uses the connection
information specified in the last successful connection made to the repository from any previous session of
pmrep. pmrep retains information from the last successful connection until you use the Cleanup command.
The Connect command uses the following syntax:
connect
-r <repository_name>
{-d <domain_name> |
{-h <portal_host_name>
ClearDeploymentGroup
989
-o <portal_port_number>}}
[{ <user_name>
[-s <user_security_domain>]
[-x <password> |
-X <password_environment_variable>]} |
-u <connect_without_user_in_kerberos_mode>]
[-t <client_resilience>]
The following table describes pmrep Connect options and arguments:
Option
Argument
Description
-r
repository_name
Required. Name of the repository you want to connect to.
-d
domain_name
Required if you do not use -h and -o. Name of the domain for the
repository. If you use the -d option, do not use the -h and -o options.
-h
portal_host_name
Required if you do not use -d. If you use the -h option, then you must
also use the -o option. Gateway host name.
-o
portal_port_number
Required if you do not use -d. If you use the -o option, then you must
also use the -h option. Gateway port number.
-n
user_name
Optional. User name used to connect to the repository.
-s
user_security_domain
Required if you use LDAP authentication. Name of the security domain

that the user belongs to. Default is Native.
-x
password
Required if you use the -n option and you do not use the -X option.
Password for the user name. The password is case sensitive. Use the -x
or -X option, but not both.
-X
password_
Required if you use the -n option and you do not use the -x option.
Password environment variable. Use the -x or -X option, but not both.
environment_variable
990
-u
connect_without _user_
in_kerberos_mode
Required. Connects to a Repository Service without a user name and

password when the Informatica domain uses Kerberos authentication.
Use the -u option to connect to the Repository Service if the repository
has no content.
-t
client_resilience
Optional. Amount of time in seconds that pmrep attempts to establish or

reestablish a connection to the repository. If you omit the t option,
pmrep uses the timeout value specified in the
INFA_CLIENT_RESILIENCE_TIMEOUT environment variable. If no
value is specified in the environment variable, the default of 180 seconds
is used.
Create
Creates the repository tables in the database. Before you can create the repository tables, you must
complete these tasks:
Create and configure the database to contain the repository.
Create the Repository Service in either the Administrator tool or infacmd.
Run the Repository Service in exclusive mode in either the Administrator tool or infacmd.
Connect to the repository in pmrep.
You cannot use the Create command if the repository database already contains repository tables.
To use the Create command, you must have permission on the Repository Service in the domain.
The Create command uses the following syntax:
create
-u <domain_user_name>
[-s <domain_user_security_domain>]
[-p <domain_password> |
-P <domain_password_environment_variable>]
[-g (create global repository)]
[-v (enable object versioning)]
The following table describes pmrep Create options and arguments:
Option
Argument
Description
-u
domain_user_name
Required. User name.
-s
domain_user_security_domain

domain that the user belongs to. Default is Native.
-p
domain_password
Optional. Password. Use either the -p or -P option, but not both.

If you do not use either the -p or -P option, pmrep prompts you
to enter the password.
-P
domain_password_
Optional. Password environment variable. Use either the -p or P option, but not both. If you do not use either the -p or -P
option, pmrep prompts you to enter the password.
-g
Optional. Promotes the repository to a global repository.
-v
Optional Enables object versioning for the repository.
CreateConnection
Creates a source or target connection in the repository. The connection can be a relational or application
connection. Relational database connections for each relational subtype require a subset of all
Create
991
CreateConnection options and arguments. For example, Oracle connections do not accept the -z, -d, or -t
options. Use the -k option to specify attributes for application connections.
The CreateConnection command uses the following syntax:
createconnection
-s <connection_type>
-n <connection_name>
[{-u <user_name>
[-p <password> |
-P <password_environment_variable>}]|
-K <connection_to_the_Kerberos_server>]
[-c <connect string> (required for Oracle, Informix, DB2, ODBC, and NetezzaRelational)]
-l <code_page>
[-r <rollback_segment> (valid for Oracle connection only)]
[-e <connection_environment_SQL>]
[-f <transaction_environment_SQL>]
[-z <packet_size> (valid for Sybase ASE and MS SQL Server connection)]
[-b <database_name> (valid for Sybase ASE, Teradata and MS SQL Server connection)]
[-v <server_name> (valid for Sybase ASE and MS SQL Server connection)]
[-d <domain name> (valid for MS SQL Server connection only)]
[-t (enable_trusted_connection, valid for MS SQL Server connection only)]
[-a <data_source_name> (valid for Teradata connection only)]
[-x (enable advanced security, lets users give Read, Write and Execute
permissions only for themselves.)]
[-k <connection_attributes> (attributes have the format
name=value;name=value; and so on)]
[- y <Provider Type, valid for MS SQL Server connection only>]
[- m <Use DSN, valid for MS SQL Server connection only>]
The following table describes pmrep CreateConnection options and arguments:
Option
Argument
Description
-s
connection_type
Required. Type of connection. For example, to create a

Salesforce connection, use the following syntax:
-s "salesforce connection"
992
-n
connection_name
-u
user_name
Required for some connection types. User name used for

authentication.
Option
Argument
Description
-p
password
Required for some connection types. Password used for

authentication when you connect to the relational database.
Use the -p or -P option, but not both. If you specify a user
name and you do not specify -p or -P, pmrep prompts you for
the password.
-P
password_
Optional. Password environment variable used for

authentication when you connect to the relational database.
Use the -p or -P option, but not both. If you do not use the -p or
-P option, pmrep prompts you for the password.
-K
connection_to_the_Kerberos_server
Optional. Indicates that the database that you are connecting

to runs on a network that uses Kerberos authentication.
-c
connect_string
Connect string the Integration Service uses to connect to the

relational database.
-l
code_page
Required for some connection types. Code page associated

with the connection.
-r
rollback_segment
Optional. Valid for Oracle connections. The name of the

rollback segment. A rollback segment records database
transactions that allow you to undo the transaction.
-e
connection_
Optional. Enter SQL commands to set the database

environment when you connect to the database. The
Integration Service executes the connection environment SQL
environment_sql
-f
transaction_
environment_sql
Optional. Enter SQL commands to set the database

environment when you connect to the database. The
Integration Service executes the transaction environment SQL
at the beginning of each transaction.
-z
packet_size
Optional. Valid for Sybase ASE and Microsoft SQL Server

connections. Optimizes the ODBC connection to Sybase ASE
and Microsoft SQL Server.
-b
database_name
Optional. Name of the database. Valid for Sybase ASE and

Microsoft SQL Server connections.
-v
server_name
Optional Name of the database server. Valid for Sybase ASE

and Microsoft SQL Server connections.
-d
domain_name
Optional Valid for Microsoft SQL Server connections. The

name of the domain. Used for Microsoft SQL Server.
-t
Optional. Valid for Microsoft SQL Server connections. If

enabled, the Integration Service uses Windows authentication
to access the Microsoft SQL Server database. The user name
that starts the Integration Service must be a valid Windows
user with access to the Microsoft SQL Server database.
-a
data_source_name
Optional Teradata ODBC data source name. Valid for Teradata

connections.
CreateConnection
993
Option
Argument
Description
-x
Enables enhanced security. Grants you read, write, and

execute permissions. Public and world groups are not granted
any permissions. If this option is not enabled, all groups and
users are granted read, write, and execute permissions.
-k
connection_attributes
Enables user-defined connection attributes. Attributes have the

format <name>=<value>;<name>=<value>.
Note: Do not add a space before the attribute name.
-y
Enables the provider type value. You can specify the following
provider types:
- 1 for ODBC
- 2 for Oledb(Deprecated)
-m
Enables the Use DSN attribute.

The PowerCenter Integration Service retrieves the database
and server names from the DSN.
Specifying the Database Type

When you create a connection, you must enter a database type using the string associated with that
database type in pmrep. The strings are not case sensitive. Use quotes when entering a string with spaces in
an argument.
The following table describes the required pmrep database type strings according to database:
994
Database
Database Type String
HTTP Transformation
Http Transformation
IBM DB2 for Linux, UNIX, and Windows
DB2
Informix
Informix
JMS
JMS Connection
JNDI
JNDI Connection
LMAPI Target
LMAPITarget
ODBC
ODBC
Oracle
Oracle
PeopleSoft DB2
PeopleSoft DB2
PeopleSoft Informix
PeopleSoft Informix
PeopleSoft MS SQL Server
PeopleSoft MsSqlserver
Database
PeopleSoft Oracle
PeopleSoft Oracle
PeopleSoft Sybase
PeopleSoft Sybase
PowerChannel for DB2
PowerChannel for DB2
PowerChannel for MS SQL Server
PowerChannel for MS SQL Server
PowerChannel for ODBC
PowerChannel for ODBC
PowerChannel for Oracle
PowerChannel for Oracle
DB2 for i5/OS, PowerExchange bulk data movement
PWX DB2i5OS
DB2 for i5/OS, PowerExchange change data capture
PWX DB2i5OS CDC Change
DB2 for i5/OS, PowerExchange change data capture
PWX DB2i5OS CDC Real Time
DB2 for Linux, UNIX, and Windows, PowerExchange

bulk data movement
PWX DB2LUW

change data capture
PWX DB2LUW CDC Change

change data capture
PWX DB2LUW CDC Real Time
DB2 for z/OS, PowerExchange bulk data movement
PWX DB2zOS
DB2 for z/OS, PowerExchange change data capture
PWX DB2zOS CDC Change
DB2 for z/OS, PowerExchange change data capture
PWX DB2zOS CDC Real Time
Microsoft SQL Server, PowerExchange bulk data

movement
PWX MSSQLServer
Microsoft SQL Server, PowerExchange change data

capture
PWX MSSQL CDC Change
Microsoft SQL Server, PowerExchange change data

capture
PWX MSSQL CDC Real Time
Nonrelational, PowerExchange bulk data movement
PWX NRDB Batch
Nonrelational, PowerExchange change data capture
PWX NRDB CDC Change
Nonrelational, PowerExchange change data capture
PWX NRDB CDC Real Time
Nonrelational Lookup, PowerExchange
PWX NRDB Lookup
Oracle, PowerExchange bulk data movement
PWX Oracle
Oracle, PowerExchange change data capture
PWX Oracle CDC Change
CreateConnection
995
Database
Oracle, PowerExchange change data capture
PWX Oracle CDC Real Time
Sybase, PowerExchange bulk data movement
PWX Sybase
Salesforce
Salesforce Connection
SAP BW
SAP BW
SAP BWOHS READER
SAP_BWOHS_READER
SAP R3
SAP R3
SAP RFC/BAPI Interface
SAP RFC/BAPI Interface
SAP/ALE IDoc Reader
SAP_ALE_IDoc_Reader
SAP/ALE IDoc Writer
SAP_ALE_IDoc_Writer
Siebel DB2
Siebel DB2
Siebel Informix
Siebel Informix
Siebel MS SQL Server
Siebel MsSqlserver
Siebel Oracle
Siebel Oracle
Siebel Sybase
Siebel Sybase
Sybase
Sybase
Teradata
Teradata
Teradata FastExport
Teradata FastExport Connection
Web Services Consumer
Web Services Consumer
webMethods Broker
webMethods Broker
Specifying the Database Code Page

The -l option specifies the code page for the database connection. Enter the code page name you want to
assign to the database connection. For example, to assign the US-ASCII code page to the database
connection, enter the code page name US-ASCII.
Changing the database connection code page can cause data inconsistencies if the new code page is not
compatible with the source or target database connection code pages. Also, if you configure the Integration
Service for data code page validation, changing the database connection code page can cause sessions to
fail if the source database connection code page is not a subset of the target database connection code
page.
996
CreateDeploymentGroup
Creates a deployment group. You can create a dynamic or static deployment group. To create a dynamic
deployment group, you must supply a query name, and indicate whether the query is private or public.
The CreateDeploymentGroup command uses the following syntax:
createdeploymentgroup
[-t <deployment_group_type (static or dynamic)>]
[-q <query_name>]
[-u <query_type (shared or personal)>]
[-c <comments>]
The following table describes pmrep CreateDeploymentGroup options and arguments:
Option
Argument
Description
-p
Required. Name of the deployment group to create.
-t
deployment_group_type
Optional. Create a static group or use a query to dynamically create

the group. You can specify static or dynamic. Default is static.
-q
query_name
Required if the deployment group is dynamic, but ignored if the group

is static. Name of the query associated with the deployment group.
-u
query_type
Required if the deployment group is dynamic, but ignored if the group

is static. Type of query to create a deployment group. You can specify
shared or personal.
-c
comments
Optional. Comments about the new deployment group.
CreateFolder
Creates a folder in the repository.
The CreateFolder command uses the following syntax:
createfolder
-n <folder_name>
[-d <folder_description>]
[-o <owner_name>]
[-a <owner_security_domain>]
[-s (shared_folder)]
[-p <permissions>]
[-f <active | frozendeploy | frozennodeploy>]
CreateDeploymentGroup
997
The following table describes pmrepCreateFolder options and arguments:

Option
Argument
Description
-n
folder_name
Required. Folder name.
-d
folder_description
Optional. Description of the folder that appears in the Repository

Manager. If the folder description contains spaces or other nonalphanumeric characters, enclose it in quotation marks.
-o
owner_name
Optional. Owner of the folder. Any user in the repository can be the
folder owner. Default owner is the user creating the folder.
-a
owner_security_domain

that the owner belongs to. Default is Native.
-s
Optional. Makes the folder shared.
-p
permissions
Optional. Access rights for the folder. If omitted, the Repository

Service assigns default permissions.
-f
active
Optional. Changes the folder status to one of the following statuses:
frozendeploy
- active. This status allows users to check out versioned objects in the
folder.
- frozendeploy (Frozen, Allow Deploy to Replace). This status prevents
users from checking out objects in the folder. Deployment into the folder
creates new versions of the objects.
frozennodeploy
- frozennodeploy (Frozen, Do Not Allow Deploy to Replace). This status

prevents users from checking out objects in the folder. You cannot
deploy objects into this folder.
Note: You can add, remove, or update permissions on a folder by using the AssignPermission command.
Assigning Permissions
You can assign owner, group, and repository permissions by entering three digits when you use the -p option.
The first digit corresponds to owner permissions, the second corresponds to the permissions of the group
that the user belongs to, and the third corresponds to all other permissions.
Enter one number for each set of permissions. Each permission is associated with a number. Designate 4 for
read permission, 2 for write permission, and 1 for execute permission. To assign permissions, you enter 4, 2,
1, or the sum of any of those numbers.
For example, if you want to assign default permissions, use the following command syntax:
-p 764
This gives the folder owner read, write, and execute permissions (7 = 4+2+1). The owners group has read
and write permissions (6 = 4+2). All others have read permission.
The command returns createfolder successfully completed or returns createfolder failed message. The
creation might fail for the following reasons:
998
The folder already exists.
The owner does not exist or does not belong to the group.
CreateLabel
Creates a label that you use to associate groups of objects during development. You can associate a label
with any versioned object or group of objects in a repository.
The CreateLabel command uses the following syntax:
createlabel
-a <label_name>
[-c <comments>]
The following table describes pmrep CreateLabel options and arguments:
Option
Argument
Description
-a
label_name
Required. Name of the label you are creating.
-c
comments
Optional. Comments about the label.
Delete
Deletes the repository tables from the repository database.
Before you use the Delete command, you must connect to the repository and provide a user name and
password or password environment variable.
When you use the Delete command, the Repository Service must be running in exclusive mode. You can
configure the Repository Service to run in exclusive mode in the Administrator tool or you can use the
infacmd UpdateRepositoryService command.
The Delete command uses the following syntax:
delete
[-x <repository_password_for_confirmation> |
-X <repository_password_environment_variable_for_confirmation>]
[-f (forceful delete: unregisters local repositories and deletes)]
The following table describes pmrep Delete options and arguments:
Option
-x
Argument
Description
repository_password_for_
Optional. Password. You can use the -x or -X option, but not both. If
you do not use the -x or -X option, pmrep prompts you to enter the
password for confirmation.
confirmation
-X
repository_password_
environment_variable_for_
confirmation
-f
Optional. Password environment variable. You can use the -x or -X

option, but not both. If you do not use the -x or -X option, pmrep
prompts you to enter the password for confirmation.
Optional. Deletes a global repository and unregisters local
repositories. All registered local repositories must be running.
CreateLabel
999
DeleteConnection
Deletes a relational connection from the repository.
The DeleteConnection command uses the following syntax:
deleteconnection
[-f (force delete)]
[-s <connection type application, relational, ftp, loader or queue>]
The following table describes pmrep DeleteConnection options and arguments:
Option
Argument
Description
-n
connection_name
Required. Name of the connection to delete.
-f
Optional. Connection will be deleted without further confirmation.
-s
connection type application,

relational, ftp, loader or
queue
Optional. Type of connection. A connection can be one of the

following types:
- Application
- FTP
- Loader
- Queue
- Relational
Default is relational.
DeleteDeploymentGroup
Deletes a deployment group. If you delete a static deployment group, you also remove all objects from the
deployment group.
The DeleteDeploymentGroup command uses the following syntax:
deletedeploymentgroup
[-f (force delete)]
The following table describes pmrep DeleteDeploymentGroup options and arguments:
1000
Option
Argument
Description
-p
Required. Name of the deployment group to delete.
-f
Optional. Deletes the deployment group without confirmation. If you

omit this argument, pmrep prompts you for a confirmation before it
deletes the deployment group.
DeleteFolder
Deletes a folder from the repository.
The DeleteFolder command uses the following syntax:
deletefolder
-n <folder_name>
The following table describes pmrep DeleteFolder option and argument:
Option
Argument
Description
-n
folder_name
Required. Name of the folder.
DeleteLabel
Deletes a label and removes the label from all objects that use it. If the label is locked, the delete fails.
The DeleteLabel command uses the following syntax:
deletelabel
-a <label_name>
[-f (force delete)]
The following table describes pmrep DeleteLabel options and arguments:
Option
Argument
Description
-a
label_name
Required. Name of the label to delete.
-f
Optional. Delete the label without confirmation. If you omit this

argument, the command prompts you for a confirmation before it
deletes the label.
DeleteObject
Deletes an object. Use DeleteObject to delete a source, target, user-defined function, mapplet, mapping,
session, worklet or workflow.
The DeleteObject command uses the following syntax:
DeleteObject
-o <object_type>
-f <folder_name>
-n <object_name>
[-s dbd_separator]
DeleteFolder
1001
The following table describes pmrep DeleteObject options and arguments:

Option
Argument
Description
-o
object_type
Required Type of the object you are deleting: source, target, mapplet,
mapping, session, user defined function, worklet, workflow.
-f
folder_name
Required Name of the folder that contains the object.
-n
object_name
Required. Name of the object you are deleting. If you delete a source
definition you must prepend the database name. For example,
DBD.sourcename.
-s
dbd_separator
Optional. If an ODBC source has a period (.) in the name, define a different
separator character when you define the source object. For example,
instead of database_name.source_name, define the source object as
database_name\source_name, and define the dbd_separator as backslash
(\).
Note: You can run the DeleteObject command against a non-versioned repository. If you run the
DeleteObject command against a versioned repository, pmrep returns the following error:
This command is not supported because the versioning is on for the repository
<Repository name>.
Failed to execute DeleteObject
DeployDeploymentGroup
Deploys a deployment group. You can use this command to copy a deployment group within a repository or
to a different repository.
To use this command, you must create a control file with all the specifications that the Copy Wizard requires.
The control file is an XML file defined by the depcntl.dtd file.
If pmrep cannot immediately acquire object locks in the target repository, by default it waits indefinitely to
acquire the locks.
You can use the deployment control file parameters to specify a deployment timeout. The deployment
timeout is the period of time (in seconds) that pmrep waits to acquire locks. A value of 0 fails the deployment
if pmrep cannot immediately acquire locks. The default value is -1, which instructs pmrep to wait indefinitely
to acquire the locks.
Press Ctrl+C to cancel the deployment during the deployment operation or while pmrep is waiting to acquire
object locks.
The DeployDeploymentGroup command uses the following syntax:
deploydeploymentgroup
-c <control_file_name>
-r <target_repository_name>
[-n <target_repository_user_name>
[-s <target_repository_user_security_domain>]
1002
[-x <target_repository_password> |
-X <target_repository_password_environment_variable>]
[-d <target_domain_name> |
{-h <target_portal_host_name>
-o <target_portal_port_number>}]] (only if target is in a different domain)
[-l <log_file_name>]
The following table describes pmrep DeployDeploymentGroup options and arguments:
Option
Argument
Description
-p
Required. Name of the group to deploy.
-c
control_file_name
Required. Name of the XML file containing the Copy Wizard

specifications. The deployment control file is required.
-r
target_repository_name
Required. Name of the target repository where you are copying the
deployment group.
-n
target_repository_user_
Required if you copy the deployment group to a different

repository. Login user name for the target repository.
name
-s
security_domain
-x
-X

target_repository_password
Optional. Login password for the target repository. You use the -x
or -X option, but not both. If you copy the deployment group to a
different repository and you do not use the x or -X option, pmrep
prompts you for the password.
target_repository_password_
Optional. Login password environment variable for the target

repository. You use the -x or -X option, but not both. If you copy
the deployment group to a different repository and you do not use
the x or -X option, pmrep prompts you for the password.
-d
target_domain_name
Required if you copy the deployment group to a different repository

and you do not use the -h and -o options. Name of the domain for
repository.
-h
target_portal_host_name

and you do not use the -d option. Machine name for the node that
hosts the domain of the target repository.
-o
target_portal_port_number

and you do not use the -d option. Port number for the node that
hosts the domain of the target repository.
-l
log_file_name
Optional. Log file that records each deployment step. If you omit
this option, pmrep outputs the deployment steps to the command
line window.
DeployDeploymentGroup
1003
DeployFolder
Deploys a folder. You can use this command to copy a folder within a repository or to a different repository.
To use this command, you must create a control file with all the specifications that the Copy Wizard requires.
The control file is an XML file defined by the depcntl.dtd file.
If pmrep cannot immediately acquire object locks in the target repository, by default it waits indefinitely to
acquire the locks.
You can use the deployment control file parameters to specify a deployment timeout. The deployment
timeout is the period of time (in seconds) that pmrep waits to acquire locks. A value of 0 fails the deployment
if pmrep cannot immediately acquire locks. The default value is -1, which instructs pmrep to wait indefinitely
to acquire the locks.
Press Ctrl+C to cancel the deployment during the deployment operation or while pmrep is waiting to acquire
object locks.
The DeployFolder command uses the following syntax:
deployfolder
-f <folder_name>
-r <target_repository_name>
[-n <target_repository_user_name>
[-s <target_repository_user_security_domain>]
[-x <target_repository_password> |
-X <target_repository_password_environment_variable>]
[-d <target_domain_name> |
{-h <target_portal_host_name>
-o <target_portal_port_number>}]] (only if target is in a different domain)
The following table describes pmrep DeployFolder options and arguments:
Option
Argument
Description
-f
folder_name
Required. Name of the folder to deploy.
-c
control_file_name
Required. Name of the XML file containing the Copy Wizard

specifications.
-r
target_repository_name
Required. Name of the target repository you are copying the

folder to.
-n
target_repository_user_name
Required if you copy the folder to another repository. Login user

name for the target repository.
-s

security_domain
1004
Option
-x
Argument
Description
Optional. Login password for the target repository. Use the -x or X option, but not both. If you copy the folder to a different
repository and you do not use the -x or -X option, pmrep prompt
you for the password.
password
-X
target_repository_password_
Optional. Login password environment variable for the target

repository. Use the -x or -X option, but not both. If you copy the
folder to a different repository and you do not use the -x or -X
option, pmrep prompt you for the password.
-d
target_domain_name
Required if you copy the folder to a different repository and you

do not use the -h and -o options. Name of the domain for the
repository.
-h
target_portal_host_name

do not use the -d option. Machine name for the node that hosts
the domain of the target repository.
-o
target_portal_port_number

do not use the -d option. Port number for the node that hosts the
domain of the target repository.
-l
log_file_name
Optional. Log file that records each deployment step. If you omit
this option, pmrep outputs the deployment steps to the command
line window.
ExecuteQuery
Runs a query. You can choose to display the result or write the result to a persistent input file. If the query is
successful, it returns the total number of qualifying records.
Use the persistent input file with the ApplyLabel, AddToDeploymentGroup, MassUpdate, and Validate
commands.
The ExecuteQuery command uses the following syntax:
executequery
-q <query_name>
[-t <query_type (shared or personal)>]
[-u <output_persistent_file_name>]
[-a (append)]
[-c <column_separator]
[-r <end-of-record_separator>]
[-l <end-of-listing_indicator>]
[-b (verbose)]
[-y (print database type)]
[-n (do not include parent path)]
ExecuteQuery
1005
[-s <dbd_separator>]
The following table describes pmrep ExecuteQuery options and arguments:
Option
Argument
Description
-q
query_name
Required. Name of the query to run.
-t
query_type
Optional. Type of query to run. You can specify public or private. If

not specified, pmrep searches all the private queries first to find
the matching query name. Then it searches the public queries.
-u
persistent_output_file_name
Optional. Send the query result to a text file. If you do not enter a
file name, the query result goes to stdout.
-a
Optional. Appends the query results to the persistent output file. If

you do not enter this option, pmrep overwrites the file content.
-c
column_separator
Optional. Character or set of characters used to separate object

metadata columns. Use a character or set of characters that is not
used in repository object names. If any repository object name
contains spaces, you might want to avoid using a space as a
column separator.
If you omit this option, pmrep uses a single space.
-r
end-of-record_separator
Optional. Character or set of characters used to specify the end of

the object metadata. Use a character or set of characters that is
not used in repository object names. If you omit this option, pmrep
uses a new line.
-l
end-of-listing_indicator

the object list. Enter a character or set of characters that is not
used in repository object names. If you omit this option, pmrep
uses a period.
-b
Optional. Verbose. Displays more than the minimum information

about the objects. If you omit this option, pmrep prints a shorter
format including the object type, the word reusable or nonreusable, the object name and path. Verbose format includes the
object status, version number, folder name, and checked out
information.
The short format for global objects, such as label, query,
deployment group, and connection, includes the object type and
object name. Verbose format includes the label type, query type,
deployment group type, creator name, and creation time.
-y
1006
Optional. Displays the database type of sources and targets.
Option
Argument
Description
-n
Optional. Does not include the full parent path of non-reusable

objects in the query result. For example, if you use this option and
the result includes a non-reusable transformation, pmrep prints
transformation_name instead of
mapping_name.transformation_name. This option can improve
pmrep performance.
-s
dbd_separator

different separator character when you define the source object.
For example, instead of database_name.source_name, define the
source object as database_name\source_name, and define the
Exit
Exits from the pmrep interactive mode.
The command line mode invokes and exits pmrep each time you issue a command.
The Exit command uses the following syntax:
exit
FindCheckout
Displays a list of checked out objects in the repository. The listing contains the checked-out items unless you
enter all users.
If you choose an object type, then you can list checked-out objects in a specific folder or across all folders. If
you do not specify an object type, pmrep returns all the checked-out objects in the repository.
The FindCheckout command uses the following syntax:
findcheckout
[-o <object_type>]
[-f <folder_name>]
[-u (all_users)]
[-c <column_separator>]
[-b (verbose)]
Exit
1007
The following table describes pmrep FindCheckout options and arguments:

Option
Argument
Description
-o
object_type
Object type you want to list. You can specify source, target,
transformation, mapping, session, worklet, workflow, scheduler,
session config, task, cube, or dimension. If you do not use this
option, pmrep ignores the -f and -u options and the command returns
all checked-out objects in the repository.
-f
folder_name
Optional if you specify an object type. Return a list of checked out

objects for the object type in the specified folder. The default is to list
objects for the object type across folders.
-u
Optional. List the checked out objects by all users. The default is to
list checked out objects by the current user.
-c
column_separator

metadata columns.
Use a character or set of characters that is not used in repository
object names. If any repository object name contains spaces, you
might want to avoid using a space as a column separator.
-r

the object metadata. Use a character or set of characters that is not
used in repository object names. Default is newline /n.
-l

the object list. Use a character or set of characters that is not used in
repository object names. If you omit this option, pmrep uses a period.
-b

about the objects. If you omit this option, pmrep prints a shorter
format including the object type, the word reusable or non-reusable,
the object name and path. Verbose format includes the version
number and folder name.
The short format for global objects such as label, query, deployment
group, and connection, includes the object type and object name.
Verbose format includes the creator name and creation time.
-y
-s
dbd_separator

GetConnectionDetails
Lists the properties and attributes of a connection object as name-value pairs.
To use the GetConnectionDetails command, you need read permission on the connection object.
1008
The GetConnectionDetails command uses the following syntax:

getconnectiondetails
-t <connection_type>
The following table describes pmrep GetConnectionDetails options and arguments:
Option
Argument
Description
-n
connection_name
Required. Name of the connection to list details for.
-t
connection_type
Required. Type of connection. A connection can be one of the following

types:
- Application
- FTP
- Loader
- Queue
- Relational
GenerateAbapProgramToFile
Generates the ABAP program for a mapping with SAP table as the source and saves the program as a file.
The GenerateAbapProgramToFile command generates the ABAP program for a mapping in the PowerCenter
repository. The generated program is saved as a file. You can use the GenerateAbapProgramToFile
command for mappings that use SAP tables as the source.
The naming convention for the file is mappingname_<version>_<program_mode>.ab4. You must enclose the
path and the file name in double quotes. After you generate the ABAP program and save it to a file, use the
InstallAbapProgram command to install it on an SAP system.
The GenerateAbapProgramToFile command uses the following syntax:
generateabapprogramtofile
-s <folder_name>
-m <mapping_name>
[-l <log_filename>]
-u <user_name>
-x <password>
-c <connect_string>
-t <client>
[-y <language>]
-p <program_mode (file, stream)>
-f <output_file_location>
GenerateAbapProgramToFile
1009
{-e (enable override)

-o <override_name> }
[-a (authority check)]
[-n (use namespace)]
The following table describes pmrep GenerateAbapProgramToFile options and arguments:
Option
Argument
Description
-s
folder_name
Required. The name of the folder that contains the mapping for which the
ABAP program needs to be generated.
-m
mapping_name
-v
version_number
Optional. Version number of the mapping. Default is the latest version.
-l
log_filename
Optional. Name of the log file where the information or error messages are
written. By default, the log file is created in the directory where you run the
command.
-u
user_name
Required. SAP source system connection user name. Must be a user for
which you have created a source system connection.
-x
password
Required. Password for the user name. Use the command line program
pmpasswd to encrypt the user password.
-c
connect_string
Required. DEST entry defined in the sapnwrfc.ini file for a connection to

a specific SAP application server or for a connection that uses SAP load
balancing.
-t
client
-y
language
Optional. SAP Logon language. Must be compatible with the PowerCenter

Client code page. Default is the language of the SAP system.
-p
program_mode
(file, stream)
Required. Mode in which the PowerCenter Integration Service extracts data

from the SAP system. Select file or stream.
-f
output_file_locatio
n
Required. Location in the local machine where you want to save the ABAP
program file.
-e
Optional. Overrides the default ABAP program file name.
-o
override_name
Required if you enable override. ABAP program file name.
-a
Optional. Adds authority checks to the ABAP program.
-n
Optional. Appends a namespace that you registered with SAP to the ABAP
program name.
Example
The following example generates an ABAP program and saves it to a file:
generateabapprogramtofile -s folder_name -m mapping_name -l logfile_name -u user_name x password -c connect_string -t 800 -y EN -p stream -e -o program_name -n -a -f "C:
\<informatica_installation_dir>\ABAP_prog"
1010
Help
Returns the syntax for the command you specify. If you do not specify a command, then syntax for all of the
pmrep commands is displayed.
For the Help command, use one of the following syntax structures:
help [command]
-help [command]
InstallAbapProgram
Installs an ABAP program in the SAP system. Use the InstallAbapProgram command to generate and install
the ABAP program directly onto the SAP system. You can use this command to install an ABAP program
from a file onto the SAP system. You can use the InstallAbapProgram command for mappings that use SAP
tables as the source.
The InstallAbapProgram command gets the mapping information from the PowerCenter repository for a
mapping and generates the ABAP program. The command installs the generated ABAP program in the SAP
system. The first time you install the ABAP program onto the SAP system, the command generates a
program name. Subsequent installations uses the same program name if you are using the same program
mode.
When you install an ABAP program to the SAP system from a file, you must provide the full path and file
name of the ABAP program you want to install. Enclose the path and the file name in double quotes. You
must provide the folder name and mapping information for which you generated the ABAP program. The
InstallAbapProgram command gets the description of the mapping and appends it to the ABAP program when
it is installed onto the SAP system.
The InstallAbapProgram command uses the following syntax:
installabapprogram
-s <folder_name>
-m <mapping_name>
[-l <log_filename>]
-u <user_name>
-x <password>
-c <connect_string>
-t <client>
[-y <language>]
{-f <input_file_name> |
{-e (enable override)
-o <override_name> }
[-a (authority check)]
Help
1011
[-n (use namespace)]}

[-d <development_class_name>]
The following table describes pmrep InstallAbapProgram options and arguments:
1012
Option
Argument
Description
-s
folder_name
Required. The name of the folder that contains the mapping for which the
ABAP program needs to be generated. If you are installing from a file, the
name of the folder that contains the mapping for which you generated the
ABAP program.
-m
mapping_name
Required. Name of the mapping. If you are installing from a file, the name of
the mapping for which you generated the ABAP program.
-v
version_number
Optional. Version number of the mapping. Default is the latest version. If you
are installing from a file, the version of the mapping for which you generated
the ABAP program.
-l
log_filename
Optional. Name of the log file where the information or error messages are
written. By default, the log file is stored in the directory where you run the
command.
-u
user_name
-x
password
-c
connect_string

balancing.
-t
client
-y
language

-f
input_file_name
Required if you are installing the ABAP program from a file. Name of the
ABAP program file from where you want to install the ABAP program into the
SAP system.
-p
program_mode
(file, stream)
Required if you are generating and installing the ABAP program directly onto
the SAP system. Optional if you are installing the ABAP program from a file.
Mode in which the PowerCenter Integration Service extracts data from the
SAP system. Select file or stream.
-e
Optional if you are generating and installing the ABAP program directly onto
the SAP system. Overrides the default ABAP program file name.
-o
override_name
Required if you enable override. ABAP program file name.
-a
the SAP system. Adds authority checks to the ABAP program.
Option
Argument
Description
-n
the SAP system. Appends a namespace that you registered with SAP to the
ABAP program name.
-d
development_class
_name
Optional. Package or the development class name where the PowerCenter

Repository Service installs the ABAP program. Default development class is
$TMP.
Examples
The following example installs the ABAP program directly onto the SAP system:
installabapprogram -s folder_name -m mapping_name -l logfile_name -u user_name -x
password -c connect_string -t 800 -y EN -p file e o zabc -a -n -d development_class
The following example installs the ABAP program from a file onto the SAP system:
installabapprogram -s folder_name -m mapping_name -l logfile_name -u user_name -x
password -c connect_string -t 800 -y EN -p file v 1 -f "C:
\mapping_name_version_file.ab4"
KillUserConnection
Terminates user connections to the repository. You can terminate user connections based on the user name
or connection ID. You can also terminate all user connections to the repository.
The KillUserConnection command uses the following syntax:
killuserconnection
{-i <connection_id> |
-n <user_name> |
-a (kill all)}
The following table describes pmrep KillUserConnection options and arguments:
Option
Argument
Description
-i
connection_id
Repository connection ID.
-n
user_name
User name.
-a
Terminates all connections.
KillUserConnection
1013
ListConnections
Lists all connection objects in the repository and their respective connection types. A connection can be one
of the following types:
Application
FTP
Loader
Queue
Relational
The ListConnections command uses the following syntax:

listconnections
[-t (output includes connection subtype)]
The following table describes the pmrep ListConnections option:
Option
Argument
Description
-t
Optional. Displays the connection subtype. For example, for a Relational

connection, connection subtypes include Oracle, Sybase, and Microsoft SQL
Server. You can only view the subtype for connections that you have read
permission on.
ListObjectDependencies
Lists dependency objects for reusable and non-reusable objects. If you want to list dependencies for nonreusable objects, you must use a persistent input file containing object IDs. You can create this file by
running a query and choosing to create a text file.
ListObjectDependencies accepts a persistent input file and it can create a persistent output file. These files
are the same format. If you create an output file, use it as input to the ApplyLabel, AddToDeployment Group,
or Validate pmrep commands.
ListObjectDependencies returns the number of records if the command runs successfully.
The ListObjectDependencies command uses the following syntax:
listobjectdependencies
{{-n <object_name>
-o <object_type>
[-f <folder_name>] } |
[-d <dependency_object_types>]
[-p <dependency_direction (children, parents, or both)>]
1014
[-s (include pk-fk dependency)]

[-g (across repositories)]
[-u <persistent_output_file_name>
[-a (append)]]
[-b (verbose)]
[-e <dbd_separator>]
The following table describes pmrep ListObjectDependencies options and arguments:
Option
Argument
Description
-n
object_name
Required. Name of a specific object to list dependencies for.
-o
object_type
Required. Object type to list dependencies for. You can specify source,
target, transformation, mapping, session, worklet, workflow, scheduler,
session, session config, task, cube, and dimension.
-t
object_subtype
Type of transformation or task. Ignored for other object types. For more
information about valid subtypes, see Listing Object Types on page
1019 .
-v
version_number
Optional. List dependent objects for an object version other than the
latest version. You must use this option only for versioned repositories. It
does not apply to non-versioned repositories.
-f
folder_name
Folder containing object name. Folder is required if you do not use the -i
option.
-i
Optional. Text file of objects generated from ExecuteQuery or Validate

commands. You must use this file if you want to list dependencies for
non-reusable objects.
If you use this option, then you cannot use the -n, -o, -f options to specify
objects.
-d
dependency_object_typ
es
Optional. Type of dependent objects to list. You can enter ALL or one or
more object types. Default is ALL.
If ALL, then pmrep lists all supported dependent objects. If you choose
one or more objects, then pmrep lists dependent objects for these types.
To enter multiple object types, separate them by commas without
spaces.
-p
dependency_direction
Required if you do not use the -s option. Parents or children dependent

objects to list. You can specify parents, children, or both. If you do not
use the -p option, pmrep does not list parent or child dependencies.
ListObjectDependencies
1015
Option
Argument
Description
-s
Required if you do not use the -p option. Include the primary key-foreign
key dependency object regardless of the direction of the dependency. If
you do not use the -s option, pmrep does not list primary-key/foreign-key
dependencies.
-g
Optional. Find object dependencies across repositories.
-u
persistent_output_file_n
ame
Send the dependency result to a text file. Use the text file as input to the
ApplyLabel, AddToDeployment Group, or Validate pmrep commands.
The default sends the query result to stdout. You cannot use the -b and c options with this option.
-a
Append the result to the persistent output file instead of overwriting it.
-c
column_separator
Character or set of characters used to separate object metadata

columns. Use a character or set of characters that is not used in
repository object names. If any repository object name contains spaces,
you might want to avoid using a space as a column separator. You
cannot use this option with the -u option.
-r
end-of-record_
separator
Character or set of characters used to specify the end of the object

metadata. Use a character or set of characters that is not used in
repository object names.
Default is newline /n.
-l
Character or set of characters used to specify the end of the object list.
Enter a character or set of characters that is not used in repository object
names.
If you omit this option, pmrep uses a period.
-b
Verbose. Displays more than the minimum information about the objects.
If you omit this option, pmrep displays a shorter format including the
object type, the word reusable or non-reusable, the object name and
path. Verbose format includes the version number and folder name.
The short format for global objects, such as label, query, deployment
Verbose format includes the creator name and creation time. You cannot
use this option with the -u option.
1016
-y
-e
dbd_separator

object as database_name\source_name, and define the dbd_separator
as backslash (\).
ListObjects
Returns a list of objects in the repository. When you list objects, pmrep returns object metadata. Use the
following list operations:
List object types. Define the objects you want to list.
List folders. List all the folders in the repository.
List objects. List reusable and non-reusable objects in the repository or in a folder.
Use ListObjects in a shell script to return the object metadata, parse the metadata, and then use the parsed
data in another pmrep command.
For example, use ListObjects to list all Sequence Generator transformations in the repository. Create a shell
script that uses ListObjects to return Sequence Generator transformation information, parse the data
ListObjects returns, and use UpdateSeqGenVals to update the sequence values.
pmrep returns each object in a record and returns the metadata of each object in a column. It separates
records by a new line by default. You can enter the characters to use to separate records and columns. You
can also enter the characters to indicate the end of the listing.
Tip: When you enter characters to separate records and columns and to indicate the end of the listing, use
characters that are not used in repository object names. This helps you use a shell script to parse the object
metadata.
The ListObjects command uses the following syntax:
listobjects
-o <object_type>
[-f <folder_name>]
[-r <end-of-record_indicator>]
[-b (verbose)]
ListObjects
1017
The following table describes pmrep ListObjects options and arguments:

Option
Argument
-o
object_type
Description
Required. Type of object to list.
- When you enter folder, you do not need to include any other option.
pmrep ignores the -t and -f options.
- When you enter objects other than folders, you must include the -f option.
- When you enter transformation or task, you must include the -f option,
and you can optionally include the -t option.
For more information about object types to use with ListObjects, see
-t
object_subtype
Optional. Type of transformation or task to list. When you enter

transformation or task for the object type, you can include this option to
return a specific type.
For more information about object types to use with ListObjects, see
-f
folder_name
Required if you list objects other than folders. Folder to search. Use this
option for all object types except deployment group, folder, label, and
query.
-c
column_separator

metadata columns. Use a character or set of characters that is not used
in repository object names. If any repository object name contains
spaces, you might want to avoid using a space as a column separator.
-r
end-of-record_indicator
Optional. Character or set of characters used to specify the end of the

object metadata. Use a character or set of characters that is not used in
-l
end_of_listing_indicator
Optional. Character or set of characters used to specify the end of the

object list. Enter a character or set of characters that is not used in
-b
Optional. Verbose. Display more than the minimum information about

the objects. If you omit this option, you display a shorter format
including the object type, the word reusable or non-reusable, the object
name and path. Verbose format includes the object status, version
number, folder name, and checked out information.
The short format for global objects, such as label, query, deployment
Verbose format includes the label type, query type, deployment group
type, creator name, and creation time.
1018
-y
-s
dbd_separator

as backslash (\).
Listing Object Types

Use the object_type option to define the objects you want to list. The command lists the latest versions or
checked out versions of objects, including shortcuts, but excluding objects according to the rules for object
types.
The following table describes the object types and rules you use with ListObjects:
Object Type
Rule
Deploymentgroup
List deployment groups in the repository.
Folder
List folders in the repository.
Label
List labels in the repository.
Mapplet
List mapplets with latest or checked out version in a folder, including shortcuts but
excluding instances of reusable mapplets.
Mapping
List mappings with latest or checked out version in a folder, including shortcuts but
excluding instances of reusable mapplets.
Query
List queries in the repository.
Scheduler
List reusable and non-reusable schedulers with latest or checked out version in a
folder.
Session
List reusable and non-reusable sessions with latest or checked out version in a
folder, excluding instances of reusable sessions.
Sessionconfig
List the session configurations with latest or checked out version in a folder.
Source
List sources with latest or checked out version in a folder, including shortcuts but
excluding source instances.
Target
List targets with latest or checked out version in a folder, including shortcuts but
excluding target instances.
Task
List reusable and non-reusable tasks with latest or checked out version in a folder.
Transformation
List reusable and non-reusable transformations with latest or checked out version in
a folder, including shortcuts and excluding instances of reusable transformations.
User Defined Function
List user-defined functions in the repository.
Workflow
List the workflows with latest version or checked out version in a folder.
Worklet
List reusable and non-reusable worklets with latest version or checked out version
in a folder, excluding instances of reusable worklets.
ListObjects
1019
The following table describes the object types and values to use with pmrep commands:
1020
Object Type
Subtype Value
Description
Task
assignment
Assignment
Task
command
Command
Task
control
Control
Task
decision
Decision
Task
email
Email
Task
event_raise
Event-raise
Task
event_wait
Event-wait
Task
start
Start
Task
timer
Timer
Transformation
aggregator
Aggregator
Transformation
application_source_qualifier
Application Source Qualifier
Transformation
app_multi-group_source_qualifier
Application Multi-Group Source Qualifier
Transformation
custom_transformation
Custom
Transformation
HTTP
Transformation
SQL
Transformation
Union
Transformation
XML Generator
Transformation
XML Parser
Transformation
expression
Expression
Transformation
external_procedure
External Procedure
Transformation
filter
Filter
Transformation
input_transformation
Input
Transformation
java
Java
Transformation
joiner
Joiner
Transformation
lookup_procedure
Lookup
Transformation
mq_source_qualifier
MQ Source Qualifier
Transformation
normalizer
Normalizer
Object Type
Subtype Value
Description
Transformation
output_transformation
Output
Transformation
rank
Rank
Transformation
router
Router
Transformation
sequence
Sequence Generator
Transformation
sorter
Sorter
Transformation
source_qualifier
Source Qualifier
Transformation
stored_procedure
Stored Procedure
Transformation
transaction_control
Transaction Control
Transformation
update_strategy
Update Strategy
Transformation
xml_source_qualifier
XML Source Qualifier
Listing Folders
Use ListObjects to return each folder in the repository. When you enter folder for the object type, pmrep
ignores the subtype and folder name.
For example, to list all folders in the repository, use the following syntax:
listobjects -o folder
Alternatively, you can enter a different column separator and end of listing indicator:
ListObjects -o folder -c ** -l #
Listing Objects
Use ListObjects to list reusable and non-reusable objects in the repository or in a folder. pmrep does not
include instances of reusable objects. When you list objects, you must include the folder name for all objects
that are associated with a folder.
pmrep returns the name of the object with the path when applicable. For example, when a transformation is in
a mapping or mapplet, pmrep returns mapping_name.transformation_name or
mapplet_name.transformation_name.
For more information about a list of transformation or task return values, see Listing Object Types on page
1019.
For example, to list all transformation types in a folder, enter the following text at the prompt:
listobjects -o transformation -f myfolder
pmrep returns the following information:
stored_procedure reusable sp_sproc1
expression reusable exp1
stored_procedure non-reusable mapping1.sp_nsproc
sequence non-reusable smallmapplet.seqgen_empid
.listobjects completed successfully.
ListObjects
1021
To list all Stored Procedure transformations in a folder, enter the following text at the prompt:
listobjects -o transformation -t stored_procedure -f myfolder
stored_procedure reusable sp_sproc1
stored_procedure non-reusable mapping1.sp_nsproc
To list all sessions in a folder, enter the following text at the prompt:
listobjects -o session -f myfolder
session reusable s_sales_by_CUSTID
session non-reusable wf_sales.s_sales_Q3
session non-reusable wf_orders.wl_shirt_orders.s_shirt_orders
ListTablesBySess
Returns a list of sources or targets used in a session. When you list sources or targets, pmrep returns source
or target instance names to the window. Use ListTablesBySess in a shell script with other pmrep commands.
For example, you can create a shell script that uses ListTablesBySess to return source instance names and
uses Updatesrcprefix to update the source owner name.
When you use ListTablesBySess, pmrep returns source and target instance names as they appear in the
session properties. For example, if the mapping contains a mapplet with a source, pmrep returns the source
instance name in the following format:
mapplet_name.source_name
The ListTablesBySess command uses the following syntax:
listtablesbysess
-f <folder_name>
-s [<qualifying_path>.]<session_name>
-t <object_type_listed> (source or target)
The following table describes pmrep ListTablesBySess options and arguments:
Option
Argument
Description
-f
folder_name
Required. Name of the folder containing the session.
-s
session_name
Required. Name of the session containing the sources or targets. You can
enter a reusable or non-reusable session name. However, you cannot enter
an instance of a reusable session name.
To enter a non-reusable session name in a workflow, enter the workflow
name and the session name as workflow_name.session_name.
-t
object_type_listed
Required. Enter source to list sources, or enter target to list targets.
For example, to list all sources in a reusable session, enter the following text at the prompt:
listtablesbysess -f myfolder -s s_reus_sess1 -t source
1022

ITEMS
mapplet1.ORDERS
Shortcut_To_ITEM_ID
listtablesbysess completed successfully.
When the mapping contains a mapplet with a source, pmrep includes the mapplet name with the source,
such as mapplet1.ORDERS.
For example, you can list all targets in a non-reusable session in a workflow:
listtablesbysess -f myfolder -s wf_workkflow1.s_nrsess1 -t target
target1_inst
ORDERS_BY_CUSTID
Shortcut_To_tgt2_inst
listtablesbysess completed successfully.
ListUserConnections
Lists information for each user connected to the repository.
The ListUserConnections command uses the following syntax:
listuserconnections
MassUpdate
Updates session properties for a set of sessions that meet specified conditions. You can update all sessions
in a folder or a list of sessions. To update a list of sessions, create a persistent input file. The list can contain
a specific list of sessions, or it can contain conditions such as a name pattern or a property value. Use
ExecuteQuery to generate a persistent input file.
When you run MassUpdate, you can view information such as the folder name, the number of sessions that
are successfully updated or failed, and the names of the sessions that are updated. You can view the status
of the update in the command line window or in a log file that the command generates. You specify the name
and path for the log file when you run the command. By default, the log file is stored in the directory where
you run the command.
Use MassUpdate to update a session property across multiple sessions when a PowerCenter version
changes a default value.
Note: You cannot update dependent session properties.
Before you update the sessions, you can also run MassUpdate in a test mode to view changes. To view a
sample log file, see Sample Log File on page 1029.
The MassUpdate command uses the following syntax:
pmrep massupdate
-t <session_property_type (session_property, session_config_property,
transformation_instance_attribute, session_instance_runtime_option)>
-n <session_property_name>
ListUserConnections
1023
-v <session_property_value>
[-w <transformation_type>]
{-i <persistent_input_file> | -f <folder_name> }
[-o <condition_operator (equal, unequal, less, greater)>]
[-l <condition_value>]
[-g <update_session_instance_flag>]
[-m <test_mode>]
[-u <output_log_file_name>]
The following table describes pmrep MassUpdate options and arguments:
Option
Argument
Description
-t
session_property_type
Required. Session property type to update. Session properties are of

the following types:
- session_property
- session_config_property
- transformation_instance_attribute
- session_instance_runtime_option
-n
session_property_name
Required. Name of the attribute or property to update.
-v
session_property_value
Required. Value that you want to assign to the property followed by

a semicolon.
For example, to assign a value to the property, use the following
syntax: -v "IgnoreNULLInExpressionComparison=Yes;"
Note: Enclose the session property value in double quotes.
-w
transformation_type
Required if you update a transformation instance attribute.

Transformation type to update. You can update the following
transformation types: aggregator, joiner, lookup procedure, rank,
sorter, source definition, and target definition.
-i
Required if you do not use the -f option. Name of the file that
contains the selected list of sessions to update. You can use the
pmrep ExecuteQuery command to run a query and generate this file.
MassUpdate returns an error if you specify an object that is not a
session. You must use the -i option or the -f option, but not both.
-f
folder_name
Required if you do not use the -i option. Name of the folder. Use to
update all sessions in a folder. You must use the -i option or the -f
option, but not both.
-o
condition_operator
Required if you use condition_value. Part of the condition that

defines the session set.
The attribute of a session or session instance is updated when the
condition is met.
You can use the following condition operators to update a string:
equal or unequal.
You can use the following condition operators to update an integer:
equal, unequal, less, or greater.
1024
Option
Argument
Description
-l
condition_value
Required if you use a condition operator. Part of the condition. The

condition appears as follows:
<session_property_value> <condition operator> <condition_value>
-g
update_session_instance_f
lag
Required if you update a session instance run-time option.

Optional for the following session property types: session property,
session configuration attribute, and transformation instance attribute.
Updates session instances.
You can update an attribute in a session instance if the session
instance overrides the attribute.
-m
test_mode
Optional. Runs MassUpdate in test mode. View sessions that will be

impacted by the command before you commit changes. You can see
the following details in the command line window:
- Session name
- Type of session: reusable or non-reusable
- Current value of the session property
- Sessions for which the attribute has the same value and are not
affected by the command.
-u
output_log_file_name
Optional. Name of the log file that stores the status of the update
and basic information about the sessions or session instances.
Previous attribute values are also written to this file. If you do not
use this option, the details appear in the command line window.
The MassUpdate command returns massupdate successfully completed or returns failed to execute
massupdate message. The update might fail for the following reasons:
You did not specify a valid attribute value pertaining to the attribute name.
You specified the correct session property name and the wrong session property type along with it.
You did not specify the -v option that ends with a semicolon while updating a session property value.
You did not specify the -w option while updating a transformation instance attribute.
You did not specify the -g option while updating a session instance run-time option.
You do not have the Repository Services Administrator role.
Session Property Types

When you run MassUpdate, specify the session property type and the name. You specify the following
session property types:
Session properties
Session configuration attributes
Transformation instance attributes
Session instance run time options
Note: You must enclose the session property in quotes.
MassUpdate
1025
The following table lists the session properties that you can update and the session property types:
Session Property
Session Property Type
$Source connection value
session_property
$Target connection value
session_property
Additional Concurrent Pipelines for Lookup

Cache Creation
session_config_property
Aggregator Data Cache Size
transformation_instance_attribute
The transformation_type argument must be aggregator.
Aggregator Index Cache Size
The transformation_type argument must be aggregator.
Allow Temporary Sequence for Pushdown
session_property
Allow Temporary View for Pushdown
session_property
Cache Directory
The transformation_type argument must be aggregator, joiner,
or rank.
1026
Cache LOOKUP( ) function
Collect performance data
session_property
Commit Interval
session_property
Commit Type
session_property
Constraint based load ordering
Custom Properties
DateTime Format String
Default buffer block size
Disable this task
session_instance_runtime_option
DTM buffer size
session_property
Enable high precision
session_property
Enable Test Load
session_property
Fail parent if this task does not run
Fail parent if this task fails
Incremental Aggregation
session_property
Is Enabled
Session Property
Java Classpath
session_property
Joiner Data Cache Size
The transformation_type argument must be joiner.
Joiner Index Cache Size
The transformation_type argument must be joiner.
Line Sequential buffer length

Lookup cache directory name
The transformation_type argument must be lookup procedure.
Lookup Data Cache Size
Lookup Index Cache Size
Maximum Memory Allowed For Auto Memory

Attributes
Maximum Percentage of Total Memory Allowed

For Auto Memory Attributes
On Pre-Post SQL error
On Pre-session command task error
On Stored Procedure error
Output file directory
The transformation_type argument must be target definition.
Override tracing
Parameter Filename
session_property
Pre 85 Timestamp Compatibility
Pre-build lookup cache
Pushdown Optimization
session_property
Rank Data Cache Size
The transformation_type argument must be rank.
Rank Index Cache Size
The transformation_type argument must be rank.
Recovery Strategy
session_property
MassUpdate
1027
Session Property
Reject file directory

The transformation_type argument must be target definition.
Rollback Transactions on Errors
session_property
Save session log by
Session Log File directory
session_property
Session retry on deadlock
session_property
Session Sort Order
session_property
When the Integration Service runs in Unicode mode, you can
choose the sort order to sort character data in the session. You
can configure the following values for the sort order:
- 0. BINARY
- 2. SPANISH
- 3. TRADITIONAL_SPANISH
- 4. DANISH
- 5. SWEDISH
- 6. FINNISH
Sorter Cache Size
The transformation_type argument must be sorter.
Source file directory
The transformation_type argument must be source definition.
Stop on errors
Treat source rows as
session_property
Treat the input link as AND
Write Backward Compatible Session Log File
session_property
Rules and Guidelines for MassUpdate

Use the following rules and guidelines when you run MassUpdate:
1028
If the node running the Repository Service process has limited memory, disable repository agent caching
before you run MassUpdate or restart the Repository Service after you run MassUpdate.
You can update reusable and non-reusable sessions.
You cannot revert property values after you run MassUpdate.
You cannot update sessions that are checked out.
You cannot update sessions in frozen folders.
Sample Log File

The following text shows a sample log file generated by pmrep MassUpdate:
cases_auto,s_test_ff,reusable,0
s_test_ff was successfully checked out.
-----------------------------------------------------------------------------11/10/2008 11:12:55 ** Saving... Repository test_ver_MU, Folder cases_auto
-----------------------------------------------------------------------------Session s_test_ff updated.
Checking-in saved objects...done
-----------------------------------------------------------------------------cases_auto,wf_non_reusable_test_ff.s_test_ff_non_reusable,non-reusable,0
wf_non_reusable_test_ff was successfully checked out.
-----------------------------------------------------------------------------11/10/2008 11:12:57 ** Saving... Repository test_ver_MU, Folder cases_auto
-----------------------------------------------------------------------------Validating the flow semantics of Workflow wf_non_reusable_test_ff...
...flow semantics validation completed with no errors.
Validating tasks of Workflow wf_non_reusable_test_ff...
...Workflow wf_non_reusable_test_ff tasks validation completed with no errors.
Workflow wf_non_reusable_test_ff updated.
Checking-in saved objects...done
-----------------------------------------------------------------------------Massupdate Summary:
Number of reusable sessions that are successfully updated: 1.
Number of non-reusable sessions that are successfully updated: 1.
Number of session instances that are successfully updated: 0.
Number of reusable sessions that fail to be updated: 0.
Number of non-reusable sessions that fail to be updated: 0.
Number of session instances that fail to be updated: 0.
------------------------------------------------------------------------------
ModifyFolder
Modifies folder properties. You modify a folder in a non-versioned repository.
The command returns ModifyFolder successfully completed or returns ModifyFolder Failed message. The
modification might fail for the following reasons:
The folder does not exist.
The new owner does not exist or does not belong to the group.
A folder with the new folder name already exists.
The ModifyFolder command uses the following syntax:

modifyFolder
-n <folder_name>
[-d <folder_description>]
[-o <owner_name>]
[-a <owner_security_domain>]
[-s (shared folder)]
ModifyFolder
1029
[-p <permissions>]
[-r <new_folder_name>]
[-f <folder_status> (active, frozendeploy, or frozennodeploy)]
[-u <os_profile>]
The following table describes the pmrepModifyFolder options and arguments:
Option
Argument
Description
-n
folder_name
Required. New folder name.
-d
folder_description
Optional. Description of the folder that displays in the Repository

Manager.
-o
owner_name
Optional. Current owner of the folder. Any user in the repository can be
the folder owner. Default owner is the current user.
-a
owner_security_domain

that the owner belongs to. Default is Native.
-s
shared_folder
Optional. Makes the folder shared.
-p
permissions
Optional. Access rights for the folder. If omitted, the Repository Service
uses existing permissions.
-r
new_folder_name
Optional. New name of the folder.
-f
folder_status
Optional. Change the folder status to one of the following status:

- active. This status allows users to check out versioned objects in the
folder.
- frozendeploy (Frozen, Allow Deploy to Replace). This status prevents
users from checking out objects in the folder. Deployment into the folder
creates new versions of the objects.
- frozennodeploy (Frozen, Do Not Allow Deploy to Replace). This status
prevents users from checking out objects in the folder. You cannot deploy
objects into this folder.
-u
os_profile
Optional. Assigns an operating system profile to the folder.
Notify
Sends notification messages to users connected to a repository or users connected to all repositories
managed by a Repository Service.
The Notify command uses the following syntax:
notify
-m <message>
1030
The following table describes pmrep Notify option and argument:

Option
Argument
Description
-m
message
Required. Message you want to send.
The command returns notify successfully completed or returns failed to execute notify message. The
notification might fail for the following reasons:
The message you entered is invalid.
You failed to connect to the Repository Service.
The Repository Service failed to notify users.
ObjectExport
Exports objects to an XML file defined by the powrmart.dtd file. You export an object by name. If you enter an
object, you must enter the name of the folder that contains it. If you do not enter a version number, you
export the latest version of the object.
Use a persistent input file to specify different objects to export at one time. You can create this file by using
the ExecuteQuery, Validate, or ListObjectDependencies pmrep commands. If you use the persistent input
file, do not use the other parameters to specify objects.
If you export a mapping, by default PowerCenter exports the mapping and its instances. If you want to
include dependent objects, you must add the appropriate pmrep options. You can optionally include reusable
and non-reusable dependent objects, objects referenced by shortcuts, and related objects in a primary keyforeign key relationship.
To export mapping dependencies, you must use the -b and -r options.
The ObjectExport command uses the following syntax:
objectexport
{{-n <object_name>
-o <object_type>
[-m (export pk-fk dependency)]
[-s (export objects referred by shortcut)]
[-b (export non-reusable dependents)]
[-r (export reusable dependents)]
-u <xml_output_file_name>
[-e dbd_separator]
ObjectExport
1031
The following table describes pmrep ObjectExport options and arguments:

Option
Argument
Description
-n
object_name
Required if you do not use the -i option. Name of a specific object to

export. If you do not enter this option, pmrep exports all the latest or
checked out objects in the folder. Use the -n option or the -i option, but
not both.
-o
object_type
Object type of the object name. You can specify source, target,
transformation, mapping, mapplet, session, worklet, workflow, scheduler,
session config, or task. If you use this option, you cannot use the -i
option.
-t
object_subtype
Type of transformation or task. This argument is ignored for other object

types. For more information about valid subtypes, see Listing Object
Types on page 1019.
-v
version_number
Optional. Exports the version of the object that you enter.
-f
folder_name
Name of the folder containing the object to export. If you do not enter an
object name, pmrep exports all the objects in this folder. If you use this
option, you cannot use the -i option.
-i
Required if you do not use the -n option. Text file list of objects
generated from ExecuteQuery, Validate, or ListObjectDependencies. It
contains object records with encoded IDs. If you use this parameter, you
cannot use the -n, -o, or -f options.
-m
Required to export dependent objects. Exports primary key table

definitions when you export sources or targets with foreign keys.
-s
Required to export dependent objects. Exports the original object

referenced by the shortcut.
-b
Required to export dependent objects. Exports non-reusable objects

used by the object.
-r
Required to export dependent objects. Exports reusable objects used by

the object.
-u
xml_output_file_name
Required. Name of the XML file to contain the object information.
-l
log_file_name
Optional. Log file that records each export step. If you omit this option,
status messages output to the window.
-e
dbd_separator

as backslash (\).
Examples
The following example exports a mapping named map, which is located in folder1, to a file named map.xml:
objectexport
1032
-n map -o mapping -f folder1 -u map.xml
The following example exports the objects identified in a persistent input file named persistent_input.xml to a
file named map.xml:
objectexport
-i persistent_input.txt -u map.xml
Note: If you use a manually created persistent input file, since you enter none for the encoded ID, the
following message appears: Ids are invalid. Trying with names for [none,folder1,map,mapping,none,1].
ObjectImport
Imports objects from an XML file. This command requires a control file to specify the objects to import and
how to resolve conflicts. The control file is an XML file defined by the impcntl.dtd file.
The ObjectImport command uses the following syntax:
objectimport
-i <input_xml_file_name>
[-p (retain persistent value)]
The following table describes pmrep ObjectImport options and arguments:
Option
Argument
Description
-i
input_XML_file_name
Required. Name of the XML file to import.
-c
control_file_name
Required. Name of the control file that defines import options.
-l
log_file_name
Optional. Log file that records each export step. If you omit this option,
status messages output to the window.
-p
Optional. Retains persistent values for mapping variables.
Note: The ObjectImport command does not create a folder if the folder name you enter does not exist in the
repository.
PurgeVersion
Purges object versions from the repository database. You can purge versions of deleted objects and active
objects. An object is a deleted object if the latest version is checked in and it has the version status Deleted.
Other objects are active objects.
When you purge versions of deleted objects, you purge all versions. The deleted objects must be checked in.
You can purge versions for all deleted objects or for objects deleted before a specified end time. You can
specify the end time as a date and time, a date only, or a number of days before the current date.
ObjectImport
1033
When you purge versions of active objects, you can specify purge criteria. You can specify the number of
versions to keep and purge the previous versions, and you can purge versions that are older than a specified
purge cutoff time. You cannot purge a checked-out version or the latest checked-in version.
If you purge versions of a composite object, consider which versions of the dependent objects are purged.
You can use the -k option to display the objects that do not purge and the reason object versions do not
purge. For example, you might not have permission to purge an object version. You cannot purge object
versions that are part of a deployment group.
The PurgeVersion command uses the following syntax:
purgeversion
{-d <all | time_date | num_day> |
{-n <last_n_versions_to_keep> |
-t <time_date | num_day>}}
[-f <folder_name>]
[-q <query_name>]
[-o <output_file_name>]
[-p (preview purged objects only)]
[-b (verbose)]
[-c (check deployment group reference)]
[-s dbd_separator]
[-k (log objects not purged)]
The following table describes pmrep PurgeVersion options and arguments:
Option
Argument
Description
-d
all
Required if you do not use -n or -t. Purges all versions of checked-in

deleted objects. You can specify all for all deleted objects, or you
can specify an end time to purge all versions of objects that were
deleted before the end time. You specify the end time in MM/DD/
YYYY HH24:MI:SS format, MM/DD/YYYY format, or as the number of
days before the current date. If you specify a number of days, the
value must be an integer greater than 0.
time_date
num_day
1034
-n
last_n_versions_to_keep
Required if you do not use -d or -t. Number of latest checked-in

object versions to keep for an active object. The value must be an
integer greater than 0. For example, enter 6 to purge all versions
except the last six checked-in versions. If the object is checked out,
you also retain the checked-out version.
Note: After you purge object versions, you cannot retrieve them. To
ensure that you can revert to past versions, avoid purging all
versions of an object.
-t
purge_cutoff_time
Required if you do not use -d or -n. Cutoff time for purging object
versions of active objects. Purges versions that were checked in
before the cutoff time. You can specify the purge cutoff time in
MM/DD/YYYY HH24:MI:SS format, MM/DD/YYYY format, or as a
number of days before the current date. If you specify a number of
days, the value must be an integer greater than 0. When you use the
t option, you retain the latest checked-in version even if it was
checked in after the purge cutoff time.
-f
folder_name
Optional. Folder from which object versions are purged. If you do not
specify a folder, you purge object versions from all folders in the
repository.
Option
Argument
Description
-q
query_name
Optional. Query used to purge object versions from a particular query

result set.
Note: If you use the -d option, you purge all versions of the deleted
objects. To keep recent versions of deleted objects and purge older
versions, you can define a query that returns the deleted objects and
then use the -q option with -n, -t, or both.
-o
outputfile_name
Optional. Output file for saving information about purged object

versions.
-p
Optional. Previews the PurgeVersion command. pmrep displays the

purge results without actually purging object versions.
-b
Optional. Displays or saves purge information in verbose mode.

Verbose mode provides detailed information about object versions,
including repository name, folder name, version number, and status.
You can use the -b option with -o and -p.
-c
Optional. Checks deployment groups in the repository for references

to the object versions returned in a purge preview. If a purge preview
contains an object version in a deployment group, pmrep displays a
warning.
When you use the -c option with the -p option, the command lists
objects that purge, then lists which object versions are contained in
deployment groups. When you use the -c option without the -p
option, the command does not purge object versions that are part of
deployment groups.
Note: The -c option can have a negative impact on performance.
-s
dbd_separator

-k
Optional. Lists all the object names and versions that do not purge
although they match the purge criteria. The -k option also lists the
reason that the object versions do not purge. For example, an object
version does not purge if you do not have sufficient privileges to
purge the object.
Note: An object version does not purge when it belongs to a
deployment group. When an object is a member of more than one
deployment group, the reason lists the first deployment group that
causes the object not to purge.
Examples
The following example purges all versions of all deleted objects in the repository:
pmrep purgeversion -d all
Note: For optimal performance, purge at the folder level or use purge criteria to reduce the number of purged
object versions. Avoid purging all deleted objects or all older versions at the repository level.
The following example purges all but the latest checked-in version of objects in the folder1 folder:
pmrep purgeversion -n 1 -f folder1
PurgeVersion
1035
The following example previews a purge of all object versions that were checked in before noon on January
5, 2005, and outputs the results to the file named purge_output.txt:
pmrep purgeversion -t '01/05/2005 12:00:00' -o purge_output.txt -p
Register
Registers a local repository with a connected global repository. You must connect to the global repository
before you register the local repository.
Also, you must run the Repository Service for the local repository in exclusive mode. You can configure the
Repository Service to run in exclusive mode in the Administrator tool or you can use the infacmd
UpdateRepositoryService command.
The command returns register successfully completed or returns failed to execute register message. The
registration might fail for the following reasons:
The local repository is not running in exclusive mode.
The Repository Service failed to initialize information about the global repository.
The Repository Service failed to register the local repository with the global repository.
The Register command uses the following syntax:

register
-r <local_repository_name>
-n <local_repository_user_name>
[-s <local_repository_user_security_domain>]
[-x <local_repository_password> |
-X <local_repository_password_environment_variable>]
[-d <local_repository_domain_name> |
{-h <local_repository_portal_host_name>
-o <local_repository_portal_port_number>}] (if local repository is in a different
domain)
The following table describes pmrep Register options and arguments:
Option
Argument
Description
-r
local_repository_name
Required. Name of the local repository to register.
-n
local_repository_user_name
Required. Local user name.
-s
local_repository_user_security_

security domain that the user belongs to. Default is Native.
domain
-x
1036
local_repository_password
Optional. Login password for the local target repository. You

use the -x or -X option, but not both. If you do not use the -x
or -X option, pmrep prompts you for the password.
Option
Argument
Description
-X
Optional. Login password environment variable for the local

target repository. You use the -x or -X option, but not both. If
you do not use the -x or -X option, pmrep prompts you for the
password.
-d
local_repository_domain_name
Required if the local repository is in a different domain and

you do not use the -h and -o options. Name of the Informatica
domain for the repository.
-h
local_repository_portal_host_

you do not use -d. Machine name of the domain where the
local repository is located. If you use this option, you must
also use the -o option.
name
-o
local_repository_portal_port_
number

you do not use -d. Port number for the domain where the local
repository is located. If you use this option, you must also use
the -h option.
RegisterPlugin
Registers an external plug-in to a repository. Registering a plug-in adds its functionality to the repository. Use
the RegisterPlugin command to update existing plug-ins.
When you use this command, the Repository Service must be running in exclusive mode. You can configure
the Repository Service to run in exclusive mode in the Administrator tool or you can use the infacmd
The RegisterPlugin command uses the following syntax:
registerplugin
-i <input_registration_file_name_or_path>
[-e (update plug-in)]
[-l <NIS_login>
{-w <NIS_password> |
-W <NIS_password_environment_variable>}
[-k (CRC check on security library)]]
[-N (is native plug-in)]
RegisterPlugin
1037
The following table describes pmrep RegisterPlugin options and arguments:

Option
-i
Argument
Description
input_registration_file_name_or_
Required. Name or path of the registration file for the plug-in.
path
-e
Optional. Update an existing plug-in. Not applicable for

authentication modules.
-l
NIS login
Optional. Registers security module components. Provide the

NIS login of the user registering an external security module.
If the plug-in contains an authentication module, you must
supply the external login name, or the registration fails. This
login becomes the administrator user name in the repository.
Do not use this option for other plug-ins.
-w
NIS password
Optional. Use to register authentication module components.

External directory password of the user registering the
module. If the plug-in contains an authentication module, you
must supply the user password from the external directory or
the registration fails. Do not use this option for other plug-ins.
Use the -w or -W option, but not both. If you do not supply a
password or password environment variable, pmrep prompts
you for a password.
-W
NIS_password_environment_
Optional. Use to register authentication module components.
variable
External directory password environment variable of the user

registering the module. If the plug-in contains an
authentication module you must supply the user password
from the external directory or the registration fails. Do not use
this option for other plug-ins.
Use the -w or -W option, but not both. If you do not supply a
password or password environment variable, pmrep prompts
you for a password.
-k
Optional. Stores the CRC of the plug-in library in the

repository. When the Repository Service loads the module, it
checks the library against the CRC.
-N
Registers a plug-in. Required when the following conditions

are true:
- You upgrade PowerCenter.
- The PowerCenter upgrade does not have a new repository
version.
- The plug-in contains updated functionality.
- The plug-in is registered by default with a new PowerCenter
installation.
For information about plug-ins that you need to register when

you upgrade, see the PowerCenter Release Guide.
Registering a Security Module

If you want to use an external directory service to maintain users and passwords for a repository, you must
register the security module with the repository. Use the Registerplugin command to register the security
plug-in.
1038
Example
You administer PowerCenter for an organization that has a centralized LDAP NIS for user authentication.
When you upgrade PowerCenter, you decide to use the LDAP for user authentication. The upgrade installs
the LDAP security module in the repository security folder. After connecting to the repository with the
Connect command, the administrator runs the pmrep command to register the new external module with the
repository:
pmrep registerplugin -i security/ldap_authen.xml -l adminuser -w admnpass
The -l login name and -w login password options contain the valid NIS login information for the user running
the pmrep command. After registration, you must use this login name and password to access the repository.
Note: The login name and password must be valid in the external directory, or the administrator cannot
access the repository using LDAP.
The -i option contains the XML file name that describes the security module.
Restore
Restores a repository backup file to a database. The target database must be empty.
The pmrep Restore command uses the following syntax:
restore
-u <domain_user_name>
[-s <domain_user_security_domain>]
[-p <domain_password> |
-P <domain_password_environment_variable>]
-i <input_file_name>
[-g (create global repository)]
[-y (enable object versioning)]
[-b (skip workflow and session logs)]
[-j (skip deployment group history)]
[-q (skip MX data)]
[-f (skip task statistics)]
[-a (as new repository)]
[-e (exit if domain name in the binary file is different from current domain name)]
The following table describes pmrep Restore options and arguments:
Option
Argument
Description
-u
domain_user_name
Required. User name.
-s
domain_user_security_domain

Restore
1039
Option
Argument
Description
-p
domain_password
Optional. Password. You can use the -p or P option, but not

both. If you do not use the -p or -P option, pmrep prompts you
for the password.
-P
domain_password_
Optional. Password environment variable. You can use the -p

or P option, but not both. If you do not use the -p or -P option,
pmrep prompts you for the password.
-i
input_file_name
Required. Name of the repository backup file. Use a file name

and path local to the Repository Service.
-g
Optional. Promotes the repository to a global repository.
-y
Optional. Enables object versioning for the repository.
-b
Optional. Skips tables related to workflow and session logs

during restore.
-j
Optional. Skips deployment group history during restore.
-q
Optional. Skips tables related to MX data during restore.
-f
Optional. Skips task statistics during restore.
-a
Optional. Creates new internal folder IDs for folders in the

restored repository. This enables you to copy folders and
deployment groups between the original repository and the
restored repository. If you do not use -a, you cannot copy
folders and deployment groups between the original and
restored repositories.
-e
Optional. Exits if domain name in the binary file is different

from current domain name
Example
The following example restores a repository as a versioned repository and specifies the administrator user
name and password to retain the LDAP security module registration:
restore -u administrator -p password -i repository1_backup.rep -y
RollbackDeployment
Rolls back a deployment to purge deployed versions of objects from the target repository. Use this command
to roll back all the objects in a deployment group that you deployed at a specific date and time.
You cannot roll back part of the deployment. To roll back, you must connect to the target repository. You
cannot roll back a deployment from a non-versioned repository.
To initiate a rollback, you must roll back the latest version of each object.
1040
The RollbackDeployment command uses the following syntax:

pmrep rollbackdeployment -p <deployment_group_name> -t <nth_latest_deploy_run> -r
<repository_name> -v <nth_latest_version_of_deployment_group>
The following table describes the pmrep RollbackDeployment options and arguments:
Option
Argument
Description
-p
Required. Name of the deployment group to roll back.
-t
nth_latest_deploy_run
Required. Version of the deployment you want to roll back.
-r
repository_name
Optional. Name of the source repository from where you deploy

the deployment group.
-v
nth_latest_version_of_deploymen
t_group
Optional. Version of the deployment group you want to roll

back.
Example
You have a deployment with five versions and want to rollback the last two versions. To do this, you must first
roll back the latest deployment. Enter the following text at the prompt to roll back once and purge the last
deployment:
rollbackdeployment -p Deploy_sales -t 1
Next, enter the following text to roll back the next to last deployment:
rollbackdeployment -p Deploy_sales -t 2
Run
Opens a script file containing multiple pmrep commands, reads each command, and runs them. If the script
file is UTF-8 encoded, you must use the -u option and the repository code page must be UTF-8. If you run a
UTF-8 encoded script file that includes the Connect command against a repository that does not have a
UTF-8 code page, the Run command will fail.
If the script file is not UTF-8 encoded, omit the -u option. If you use the -o option and the -u option, pmrep
generates the output file in UTF-8. If you use the -o option and omit the -u option, pmrep generates the
output file based on the system locale of the machine where you run pmrep.
The command returns run successfully completed or returns run failed message. The run might fail if the
Repository Service cannot open the script file or output file.
The Run command uses the following syntax:
run
-f <script_file_name>
[-o <output_file_name>]
[-e (echo commands)]
[-s (stop at first error)]
[-u (UTF-8 encoded script file and output file)]
Run
1041
The following table describes pmrep Run options and arguments:

Option
Argument
Description
-f
script file name
Required. Name of the script file.
-o
output file name
Optional. Name of the output file. This option writes all messages generated by
the commands in the script file into the output file. If you use the -u option and
the -o option, pmrep generates a UTF-8 encoded output file. If you use the -o
option without the -u option, pmrep encodes the output file based on the
system locale of the machine running pmrep.
-e
Optional. Commands are echoed back to the script.
-s
Optional. Stops running the script after the first error.
-u
Optional. Encodes the output file in UTF-8 format. If you use the -u option and
the -o option, pmrep also encodes the output file in UTF-8 format. Use this
option only if the repository code page is UTF-8.
ShowConnectionInfo
Returns the repository name and user information for the current connection.
Use the ShowConnectionInfo command in interactive mode. When you connect to a repository in interactive
mode, pmrep keeps the connection information in memory until you exit the repository or connect to a
different repository.
When you use the ShowConnectionInfo command in command line mode, a message indicating failure to
execute the command is given. pmrep does not keep connection information in command line mode. The
ShowConnectionInfo command does not connect to the repository.
The ShowConnectionInfo command uses the following syntax:
showconnectioninfo
It returns information similar to the following:
Connected to Repository MyRepository in MyDomain as user MyUserName
SwitchConnection
Changes the name of an existing connection. When you use SwitchConnection, the Repository Service
replaces the relational database connections for all sessions using the connection in one of the following
locations:
1042
Source connection
Target connection
Connection Information property in Lookup transformations
Connection Information property in Stored Procedure transformations
$Source Connection Value session property
$Target Connection Value session property
If the repository contains both relational and application connections with the same name and you specified
the connection type as relational in all locations in the repository, the Repository Service replaces the
relational connection.
For example, you have a relational and an application source, each called ITEMS. In a session, you specified
the name ITEMS for a relational source connection instead of Relational:ITEMS. When you use
SwitchConnection to replace the relational connection ITEMS with another relational connection, pmrep does
not replace any relational connection in the repository because it cannot determine the connection type for
the source connection entered as ITEMS.
The SwitchConnection command uses the following syntax:
switchconnection
-o <old_connection_name>
-n <new_connection_name>
The following table describes pmrep SwitchConnection options and arguments:
Option
Argument
Description
-o
old_connection_name
Required. Name of the connection you want to change.
-n
new_connection_name
Required. New connection name.
TruncateLog
Deletes details from the repository. You can delete all logs, or delete logs for a folder or workflow. You can
also enter a date and delete all logs older than that date.
The command returns truncatelog completed successfully or returns a Failed to execute truncatelog
message. The truncate operation might fail for the following reasons:
The folder name is not valid.
The workflow does not exist in the given folder.
You specified a workflow, but no folder name.
The TruncateLog command uses the following syntax:

truncatelog
-t <logs_truncated (all or up to end time in MM/DD/YYYY HH24:MI:SS format or as number
of days before current date)>
[-f <folder_name>]
[-w <workflow_name>]
TruncateLog
1043
The following table describes pmrep TruncateLog options and arguments:

Option
Argument
Description
-t
logs_truncated
Required. Use all to delete all logs, or enter an end time. pmrep
deletes all logs older than the end time. You can enter the end time with
the format MM/DD/YYYY HH24:MI:SS, or you can specify the number
of days before the current date. If you specify the number of days, the
end time must be an integer greater than 0.
-f
folder_name
Optional. Deletes logs associated with the folder. If you do not give both
the folder name and the workflow name, then pmrep deletes all logs
from the repository.
-w
workflow_name
Optional. Deletes logs associated with the workflow. The Repository

Service deletes all logs from the repository if you do not give both the
folder name and the workflow name. If you give both the folder name
and workflow name, the Repository Service deletes logs associated
with the workflow. If you enter the workflow name, you must also
provide the folder name.
UndoCheckout
Reverses the checkout of an object. When you undo a checkout, the repository releases the write-intent lock
on the object and reverts to the most recently checked in version of the object. If you want to modify the
object again, you must check it out.
The UndoCheckout command uses the following syntax:
undocheckout
-o <object_type>
-n <object_name>
-f <folder_name>
[-s dbd_separator]
The following table describes pmrep UndoCheckout options and arguments:
1044
Option
Argument
Description
-o
object_type
Required. Type of object. You can specify source, target,

transformation, mapping, session, worklet, workflow, scheduler, session
config, task, cube, and dimension.
-t
object_subtype
Optional. Type of transformation or task. Ignored for other object types.

For more information about valid subtypes, see Listing Object Types on
page 1019.
-n
object_name
Required. Name of the checked out object.
Option
Argument
Description
-f
folder_name
Required. Name of the folder containing the object.
-s
dbd_separator

as backslash (\).
Unregister
Unregisters a local repository from a connected global repository.
To use this command, you must run the Repository Service for the local repository in exclusive mode. You
can configure the Repository Service to run in exclusive mode in the Administrator tool or you can use the
infacmd UpdateRepositoryService command.
The command returns unregister successfully completed or returns failed to execute unregister message.
The registration might fail for the following reasons:
The Repository Service for the local repository is not running in exclusive mode.
The Repository Service failed to initialize information about the global repository.
The Unregister command uses the following syntax:

unregister
-r <local_repository_name>
-n <local_repository_user_name>
[-s <local_repository_user_security_domain>]
[-x <local_repository_password> |
-X <repository_password_environment_variable>]
[-d <local_repository_domain_name> |
{-h <local_repository_portal_host_name>
-o <local_repository_portal_port_number>}] (if local repository is in a different
domain)
The following table describes pmrep Unregister options and arguments:
Option
Argument
Description
-r
local_repository_name
Required. Name of the local repository to unregister.
-n
local_repository_user_name
Required. Local user name.
local_repository_user_

-s
security_domain
Unregister
1045
Option
Argument
Description
-x
local_repository_password
Required if you do not use the -X option. Login password for the
local target repository. You must use the -x or -X option, but not
both.
-X
local_repository_password_
Required if you do not use the -x option. Login password

environment variable for the local target repository. You must
use the -x or -X option, but not both.
-d
local_repository_domain_
name
-h
local_repository_portal_host_
name
-o
local_repository_portal_port_
number
Required if the local repository is in a different domain and you

do not use the -h and -o options. Name of the Informatica
domain for repository.
do not use the -d option. Machine name of the domain where the
local repository is located. If you use this option, you must also
use the -o option.
do not use the -d option. Port number for the domain where the
local repository is located. If you use this option, you must also
use the -h option.
UnregisterPlugin
Removes a plug-in from a repository. You can add and remove plug-ins to extend system functionality. A
plug-in is a software module that introduces new repository metadata.
When you use this command, the Repository Service must be running in exclusive mode. You can configure
the Repository Service to run in exclusive mode in the Administrator tool or you can use the infacmd
The UnregisterPlugin command uses the following syntax:
unregisterplugin
-v <vendor_id>
-l <plug-in_id>
[-s (is security module)
[-g (remove user-name-login mapping)]
{-w <new_password> |
-W <new_password_environment_variable>}]
1046
The following table describes pmrep UnregisterPlugin options and arguments:

Option
Argument
Description
-v
vendor_id
Required. Identifies the security plug-in by vendor identification

number. You define this number when you register the plug-in.
-l
plug-in_id
Required. Identifies the plug-in by identification number. You

define this identification number when you register the plug-in.
-s
Optional. Indicates whether the module is an external security

module.
-g
Optional. Applicable when registering an external security

module.
Removes the association between user names and login names
in the repository when you unregister an external security
module. If you omit this option, you retain the association in the
repository, but the Repository Manager does not display it
anywhere.
Use this option when you are unregistering a security module.
-w
new_password
Required when the plug-in contains a security module.

Required if you do not use the -W option. You must use the -w
or -W option, but not both.
Specifies a new password for the user running the
UnregisterPlugin command. When you unregister an external
authentication module, all user passwords reset to the values in
the repository. You must enter a new password to access the
repository.
-W
new_password_environment_
Required when the plug-in contains a security module.
variable
Required if you do not use the -w option. You must use the -w or
-W option, but not both.
Specifies a new password environment variable for the user
running the unregister command. When you unregister an
external authentication module, all user passwords reset to the
values in the repository. You must enter a new password to
access the repository.
Unregistering an External Security Module

Use the UnregisterPlugin command to discontinue using an external security module with a repository. If you
unregister the external security module, PowerCenter switches to repository authentication mode. All user
passwords reset to the values in the repository instead of the values in the external directory. When you
unregister the security module, you do not lose the mapping between the user names and the external
security login names unless you enter the -g option. Use the mapping again if you register a new security
module.
Note: Although you can save the associations between external logins and user names, the Repository
Manager does not display the external logins while running under user authentication.
You must use the -w or -W option to create a new password when you unregister the security module.
UnregisterPlugin
1047
Example
As an administrator, you decide to switch from the LDAP security module back to repository authentication.
You remove the user name-login mapping. Any users that you added to the system under repository
authentication can log in with their old user names and passwords. Any users you added to the repository
under the LDAP security cannot log in until you enable their user names.
Note: You must provide the LDAP NIS login and password to use the UnregisterPlugin command. You must
also provide a new password to use after you switch back to user authentication.
UpdateConnection
Updates the user name, password, connect string, and attributes for a database connection.
The command returns an operation successfully completed or returns operation failed message. A failure
might occur for the following reasons:
The database type is not supported.
The connection object does not exist.
pmrep cannot acquire a lock on the object.
One of the required parameters is missing.
The UpdateConnection command uses the following syntax:

updateconnection
-t <connection_subtype >
-d <connection_name>
[{-u <new_user_name>
[-p <new_password>|-P <new_password_environment_variable>]}|
-K <connection_to_the_Kerberos_server>]
[-c <new_connection_string>]
[-a <attribute_name>
-v <new_attribute_value>]
[-s <connection type application, relational, ftp, loader or queue > ]
[-l <code page>]
The following table describes pmrep UpdateConnection options and arguments:
1048
Option
Argument
Description
-t
connection_subtype
Required. Type of relational connection.
-d
connection_name
Required. Database connection name.
-u
new_user_name
Optional. User name used for authentication when you connect to the
Option
Argument
Description
-p
new_password
Optional. Password used for authentication when you connect to the

relational database. Use the -p or -P option, but not both.
new_password_
Optional. Password environment variable used for authentication when

you connect to the relational database. Use the -p or -P option, but not
both.
-K
connection_to_the_Ker
beros_server
Optional. Indicates that the database that you are connecting to runs on a
network that uses Kerberos authentication.
-c
new_connection_string
Optional. Connect string the Integration Service uses to connect to the

-a
attribute_name
Optional. Name of the attribute.
-v
new_attribute_value
Required if you use the -a option. New attribute value of the connection.
Enter yes to enable new attributes, and no to disable new attributes.
-s
connection type
application, relational,
ftp, loader or queue
Optional. Type of connection. A connection can be one of the following

types:
-P
- Application
- FTP
- Loader
- Queue
- Relational
-l
code page
Optional. Code page associated with the connection.
UpdateEmailAddr
Updates the session notification email addresses associated with the Email tasks assigned to the session. If
you did not previously enter a success or failure Email task for the session, the command does not update
the email addresses. You can update the email notification addresses for a non-reusable session with a
unique name in the folder. You can enter different addresses to receive either success or failure notifications.
This command requires you to connect to a repository.
The UpdateEmailAddr command uses the following syntax:
updateemailaddr
-d <folder_name>
-s <session_name>
-u <success_email_address>
-f <failure_email_address>
UpdateEmailAddr
1049
The following table describes pmrep UpdateEmailAddr options and arguments:

Option
Argument
Description
-d
folder_name
Required. Name of the session folder.
-s
session_name
Required. Name of the session.
-u
success_email_address
Required. Email address to send session success notifications.
-f
failure_email_address
Required. Email address to send session failure notifications.
UpdateSeqGenVals
Updates one or more of the following properties for the specified Sequence Generator transformation:
Start Value
End Value
Increment By
Current Value
You might want to update sequence values when you move a mapping from a development environment to a
production environment. Use the UpdateSeqGenVals command to update reusable and non-reusable
Sequence Generator transformations. However, you cannot update values for instances of reusable
Sequence Generator transformations or shortcuts to Sequence Generator transformations.
The UpdateSeqGenVals command uses the following syntax:
updateseqgenvals
-f <folder_name>
[-m <mapping_name>]
-t <sequence_generator_name>
[-s <start_value>]
[-e <end_value>]
[-i <increment_by>]
[-c <current_value>]
The following table describes pmrep UpdateSeqGenVals options and arguments:
1050
Option
Argument
Description
-f
folder_name
Required. Folder name.
-m
mapping_name
Mapping name. When you update values for a non-reusable

Sequence Generator transformation, you must include the
mapping name.
-t
sequence_generator_name
Required. Sequence Generator transformation name.
Option
Argument
Description
-s
start_value
Optional. Start value of the generated sequence you want the

Integration Service to use if the Sequence Generator
transformation uses the Cycle property. If you select Cycle in the
transformation properties, the Integration Service cycles back to
this value when it reaches the end value.
If you designate an invalid value, pmrep gives an error message
and does not update the Sequence Generator transformation.
-e
end_value
Optional. Maximum value the Integration Service generates. If the

Integration Service reaches this value during the session and the
sequence is not configured to cycle, it fails the session.
If you designate an invalid value, pmrep displays an error message
-i
increment_by
Optional. Difference between two consecutive values from the

NEXTVAL port.
If you designate an invalid value, pmrep displays an error message
-c
current_value
Optional. Current value of the sequence. Enter the value you want
the Integration Service to use as the first value in the sequence. If
you want to cycle through a series of values, the current value
must be greater than or equal to the start value and less than the
end value.
If you designate an invalid value, pmrep gives an error message
UpdateSrcPrefix
Updates the owner name for session source tables. You can update the owner name for one or all sources in
a session. Updatesrcprefix updates the owner name for source tables at the session level.
pmrep updates source table owner names if you previously edited the source table name in the session
properties.
The UpdateSrcPrefix command uses the following syntax:
updatesrcprefix
-f <folder_name>
[-t <source_name>]
-p <prefix_name>
[-n (use source instance name; not using -n gives old, deprecated behavior)]
UpdateSrcPrefix
1051
The following table describes the pmrep UpdateSrcPrefix options and arguments:
Option
Argument
Description
-f
folder_name
-s
session_name
Required. Name of the session containing the sources to update.

For reusable sessions, enter the session name.
For non-reusable sessions, you must also enter the session path,
such as worklet_name.session_name or
workflow_name.session_name.
-t
source_name
Optional. Name of the source to update.

If you omit this option, pmrep updates all source table owner
names in the session.
When you include the -n option, you enter the name of the source
instance as displayed in the session properties or as output by the
ListTablesBySess command.
Although the UpdateSrcPrefix command will run without the -n
option, include the -n option to use the source instance name.
If you omit the -n option, you must enter the dbd name and the
source table name as dbd_name.source_name. You can find the
source dbd name in the Designer Navigator. The Designer
generates the dbd name from the source type or data source name
when you create a source definition in the repository.
-p
prefix_name
Required. Owner name you want to update in the source table.
-n
Optional. Matches the source_name argument with source

instance names.
Although the UpdateSrcPrefix command will run without the -n
option, include the -n option to use the source instance name.
When you do not include this option, pmrep matches the
source_name argument with the source table names.
UpdateStatistics
Updates statistics for repository tables and indexes.
The command returns updatestatistics completed successfully or returns updatestatistics failed."
The UpdateStatistics command uses the following syntax:
updatestatistics
UpdateTargPrefix
Updates the table name prefix for session target tables. The table name prefix specifies the owner of the
table in the database. You can update the owner name for one or all targets specified in a session.
UpdateTargPrefix updates the target table name prefix at the session level.
1052
pmrep updates table name prefixes if you previously edited the table name prefix at the session level.
The UpdateTargPrefix command uses the following syntax:
updatetargprefix
-f <folder_name>
[-t <target_name>]
-p <prefix_name>
[-n (use target instance name; not using -n gives old, deprecated behavior)]
The following table describes the pmrep UpdateTargPrefix options and arguments:
Option
Argument
Description
-f
folder_name
-s
session_name
Required. Name of the session containing the targets to update.

For reusable sessions, enter the session name.
For non-reusable sessions, enter the session name and session
path, such as worklet_name.session_name or
workflow_name.session_name.
-t
target_name
Optional. Name of the target to update.

If you omit this option, pmrep updates all target table name
prefixes in the session.
When you include the -n option, you can enter the name of the
target instance as displayed in the session properties or as output
by the ListTablesBySess command.
Although the UpdateTargPrefix command will run without the -n
option, include the -n option to use the target instance name.
When you omit the -n option, you must enter the target table name
instead of the target instance name.
-p
prefix_name
Required. Table name prefix you want to update in the target table.
-n
Optional. Matches the target name argument with target instance

names.
Although the UpdateTargPrefix command will run without the -n
option, include the -n option to use the target instance name.
When you omit this option, pmrep matches the target name
argument with the target table names.
Upgrade
Upgrades a repository to the latest version.
The Upgrade command uses the following syntax:
upgrade
[-x <repository_password_for_confirmation> |
Upgrade
1053
-X <repository_password_environment_variable_for_confirmation>]
The following table describes pmrep Upgrade options and arguments:
Option
Argument
Description
-x
repository_ password_for_
Optional. Password. You can use the -x or -X option, but not both.
If you do not use the -x or -X option, pmrep prompts you to enter
the password for confirmation.
confirmation
-X
environment_variable_for_
Required if you do not use the -x option. Password environment

variable. You must use the -x or -X option, but not both.
confirmation
UninstallAbapProgram
Uninstalls the ABAP program. Uninstall an ABAP program when you no longer want to associate the program
with a mapping. The command uninstalls the programs from the SAP system and removes the corresponding
program information from the PowerCenter repository.
The UninstallAbapProgram command uses the following syntax:
uninstallabapprogram
-s <folder_name>
-m <mapping_name>
[-l <log_filename>]
-u <user_name>
-x <password>
-c <connect_string>
-t <client>
[-y <language>]
The following table describes pmrep UninstallAbapProgram options and arguments:
1054
Option
Argument
Description
-s
folder_name
Required. The name of the folder that contains the mapping of the ABAP
program that you want to uninstall.
-m
mapping_name
-v
version_number
Optional. Version number of the mapping. Default is the latest version.
Option
Argument
Description
-l
log_filename
Optional. Name of the log file where the command writes the information or
error messages. By default, the log file is stored in the directory where you
run the command.
-u
user_name
-x
password
-c
connect_string

balancing.
-t
client
-y
language

-p
program_mode
(file, stream)
Required. Mode in which the PowerCenter Integration Service extracts data

from the SAP system. Select file or stream.
Example
The following example uninstalls the ABAP program:
uninstallabapprogram -s folder_name -m mapping_name -l logfile_name -u user_name -x
password -c connect_string -t 800 -y EN -p stream
Validate
Validates objects. You can output the results to a persistent output file or standard output.
It also displays a validation summary to stdout. The summary includes the number of valid objects, invalid
objects, and skipped objects. The persistent output file contains standard information, encoded IDs, and a
CRC check. You can save and check in the objects that change from invalid to valid.
You can validate the following types of objects:
Mappings
Mapplets
Sessions
Workflows
Worklet objects
If you use another type of object in the input parameter, pmrep returns an error. If you use the wrong type of
object in a persistent input file, pmrep reports an error and skips the object.
Note: The pmrep Validate command does not validate shortcuts.
When you run Validate, you can output information about object status:
valid. Objects successfully validated.
Validate
1055
saved. Objects saved after validation.
skipped. Shortcuts and object types that do not require validation.
save_failed. Objects that did not save because of lock conflicts or they were checked out by another
user.
invalid_before. Objects invalid before the validation check.
invalid_after. Objects invalid after the validation check.
It is not possible to save a non-reusable object unless you save the reusable parent of the object. When you
use the -s option, the command does not save validated non-reusable objects unless, as part of the same
command, you list reusable objects that are the parents of the non-reusable objects.
The Validate command uses the following syntax:
validate
{{-n <object_name>
-o <object_type (mapplet, mapping, session, worklet, workflow)>
[-s (save upon valid)
[-k (check in upon valid)
[-m <check_in_comments>]]]
[-p <output_option_types (valid, saved, skipped, save_failed, invalid_before,
invalid_after, or all)>]
[-u <persistent_output_file_name>
[-a (append)]]
[-b (verbose)]
The following table describes pmrep Validate options and arguments:
Option
Argument
Description
-n
object_name
Required. Name of the object to validate. Do not use this option if

you use the -i argument. When you validate a non-reusable
session, include the workflow name. Enter the workflow name and
the session name in the following format:
<workflow name>.<session instance name>
1056
-o
object_type
Required if you are not using a persistent input file. Type of object
to validate. You can specify mapplet, mapping, session, worklet,
and workflow.
-v
version_number
Optional. Version of the object to validate. Default is the latest or

checked out version of the object.
-f
folder_name
Required. Name of the folder containing the object.
-i
Optional. Text file from ExecuteQuery, Validate, or

ListObjectDependencies commands. Contains a list of object
records. You cannot use this file if you specify objects using the -n,
-o, or -f arguments.
-s
Optional. Save objects that change from invalid to valid to the

repository.
-k
Required if you use -s. Check in saved objects.
Option
Argument
Description
-m
check_in_comments
Required if you use the -k option, and the current repository

requires checkin comments. Add comments when you check in an
object.
-p
output_option_types
Required if you use the -u argument. Type of object you want to

output to the persistent output file or stdout after validation. You
can specify valid, saved, skipped, save_failed, invalid_before, or
invalid_after. To enter one or more options, separate them by
commas.
-u
persistent_output_file_name
Required if you use the - p argument. Name of an output text file. If

you enter a file name, the query writes the results to a file.
-a
append
Optional. Append the results to the persistent output file instead of

overwriting it.
-c
column_separator

metadata columns.
object names. If any repository object name contains spaces, you
might want to avoid using a space as a column separator.
-r

the object metadata.
object names.
-l

the object list. Enter a character or set of characters that is not
used in repository object names.
-b

about the objects. If you omit this option, pmrep displays a shorter
format including the object type, the word reusable or nonreusable, the object name and path. Verbose format includes the
version number and folder name.
The short format for global objects such as label, query,
deployment group, and connection, includes the object type and
object name. Verbose format includes the creator name and
creation time.
-y
Version
Version
1057
The Version command uses the following syntax:

version
1058
CHAPTER 32
Working with pmrep Files

Working with pmrep Files Overview, 1059
Using the Persistent Input File , 1059
Using the Object Import Control File, 1061
Object Import Control File Examples, 1066
Using the Deployment Control File , 1072
Deployment Control File Examples, 1077
Tips for Working with pmrep Files, 1079
Working with pmrep Files Overview

pmrep includes a set of control files that you use to define how to import objects into the repository. The
control file parameters use the same parameters in the control file that you use in the PowerCenter Client.
You can use the following control files:
Persistent input file. Use a persistent input file to specify repository objects that you want to process.
Object import control file. Use the object import control file and specify a set of questions to help define
how objects are imported.
Deployment control file. You can copy the objects in a dynamic or static deployment group to multiple
target folders in the target repository.
Using the Persistent Input File

When you run pmrep with some tasks, use a persistent input file to specify repository objects that you want to
process. The persistent input file represents objects already in the repository. You can create a persistent
input file manually or by using pmrep.
Use a persistent input file with the following pmrep commands:
AddToDeploymentGroup. Add objects to a deployment group.
ApplyLabel. Label objects.
ExecuteQuery. Run a query to create a persistent input file. Use the file for other pmrep commands.
1059
ListObjectDependencies. List dependency objects. This command can use a persistent input file for
processing, and it can create one.
MassUpdate. Updates session properties for a set of sessions.
ObjectExport. Export objects to an XML file.
Validate. Validate objects. This command can use a persistent input file for processing, and it can create
one.
The persistent input file uses the following format:

encoded ID, foldername, object_name, object_type, object_subtype, version_number,
reusable|non-reusable
Creating a Persistent Input File with pmrep

You can create a persistent input file using the pmrep ExecuteQuery, Validate, or ListObjectDependencies
commands. These commands create files that contain a list of objects with encoded IDs and a cyclic
redundancy check (CRC) value. It also contains an encrypted repository GID. This ID identifies which
repository the record comes from.
The pmrep commands that use a persistent input file get object information from the encoded IDs. The
encoded IDs enable pmrep to process the input file quickly.
When you create a persistent input file with pmrep, it creates the file in the pmrep installation directory. You
can specify a different path.
The following text shows a sample persistent input file:
2072670638:57bfc2ff-df64-40fc-9cd4a15cb489bab8:3538944199885:138608640183285:1376256153425:131072168215:65536142655:028823
5:088154:65536122855,EXPORT,M_ITEMS,mapping,none,2
1995857227:57bfc2ff-df64-40fc-9cd4a15cb489bab8:3538944135065:13867417666804:1376256233835:19660880104:65536271545:0319425:
017154:6553644164,EXPORT,M_ITEMS_2,mapping,none,3
1828891977:57bfc2ff-df64-40fc-9cd4a15cb489bab8:3538944279765:138739712184505:137625613474:65536221345:65536133675:091734:0
9053:65536156675,EXPORT,M_NIELSEN,mapping,none,1
3267622055:57bfc2ff-df64-40fc-9cd4a15cb489bab8:353894462954:138805248300075:1376256151365:6553675414:65536174015:0273455:0
241435:65536261685,EXPORT,M_OS1,mapping,none,1
Example
You can use the ExecuteQuery command to create a persistent input file of objects to process in another
pmrep command. For example, you want to export all logically deleted objects from the repository. You might
create a query called find_deleted_objects. When you run the query with pmrep, as shown here, it finds all
the deleted objects in the repository and outputs the results to a persistent input file:
ExecuteQuery -q find_deleted_objects -t private -u deletes_workfile
You can then use deletes_workfile as the persistent input file to ObjectExport:
ObjectExport -i deletes_workfile -u exported_del_file
ObjectExport exports all the referenced objects to an XML file called exported_del_file.
Creating a Persistent Input File Manually

If you want to run pmrep commands against a set of objects that you cannot identify through commands such
as ExecuteQuery, you can manually create an input file.
1060
Chapter 32: Working with pmrep Files
Use the following rules and guidelines when you create a persistent input file:
Enter none for the encoded ID. The pmrep commands get the object information from the other
arguments in the records.
For source objects, enter the object name as <DBD_name>.<source_name>.
For objects, such as mappings, that do not have a sub_type, enter none as object_subtype, or leave it
blank. For more information about valid transformations and task types, see Listing Object Types on
page 1019.
For versioned repositories, enter the version number of the object you want, or enter LATEST to use the
latest version of the object.
For non-versioned repositories, leave the version_number argument blank.
For object types, such as targets, that are not reusable or non-reusable, drop the argument.
You cannot include non-reusable objects. You can specify the reusable parent of the non-reusable object.
For example, you want to list the object dependencies for a non-reusable Filter transformation. You can
specify the mapping that is the parent object of the transformation:
none,CAPO,m_seqgen_map,mapping,none,1,reusable
The mapping m_seqgen_map is the reusable parent of the Filter transformation. The command runs
successfully when you specify the reusable parent.
Note: When you use a manually created persistent input file, the Repository Service returns a message
indicating that the ID is not valid. This is an informational message. The Repository Service recognizes that
this is a manually created input file and can process the command with none as the ID.
Example
The following example shows a manually created persistent input file:
none,EXPORT,CustTgt,target,none,2
none,EXPORT,S_Orders,session,,2,reusable
none,EXPORT,EXP_CalcTot,transformation,expression,LATEST,reusable
In the first record, CustTgt is a target definition. Targets have no subtype, so you enter none for the
object_subtype argument. A target cannot be reusable or non-reusable, so you drop the reusable argument.
Note that the record has six arguments instead of seven.
In the second record, S_Orders is a session. Sessions have no subtype, so you leave the argument blank.
In the third record, you want the latest version of the transformation, so you enter LATEST for the
version_number argument.
Using the Object Import Control File

When you use the pmrep ObjectImport command, you can supply a control file to answer questions that you
normally address when you import objects with the Import Wizard. To create a control file, you must create an
XML file defined by impcntl.dtd. The import control file is installed with the PowerCenter Client, and you must
include its location in the input XML file.
The following is a sample of the impcntl.dtd file:



1061





<!ELEMENT IMPORTPARAMS (FOLDERMAP*, TYPEFILTER*, RESOLVECONFLICT?)>
<!ATTLIST IMPORTPARAMS
CHECKIN_AFTER_IMPORT
(YES | NO) "NO"
CHECKIN_COMMENTS
CDATA
#IMPLIED
APPLY_LABEL_NAME
CDATA
#IMPLIED
RETAIN_GENERATED_VALUE
(YES | NO) "NO"
COPY_SAP_PROGRAM
(YES | NO) "YES"
APPLY_DEFAULT_CONNECTION (YES | NO) "NO"
>

<!ELEMENT FOLDERMAP EMPTY>
<!ATTLIST FOLDERMAP
SOURCEFOLDERNAME
CDATA
#REQUIRED
SOURCEREPOSITORYNAME CDATA
#REQUIRED
TARGETFOLDERNAME
CDATA
#REQUIRED
TARGETREPOSITORYNAME CDATA
#REQUIRED
>


<!ELEMENT TYPEFILTER EMPTY>
<!ATTLIST TYPEFILTER
TYPENAME
CDATA
#REQUIRED
>

<!ELEMENT RESOLVECONFLICT (LABELOBJECT | QUERYOBJECT | TYPEOBJECT | SPECIFICOBJECT)*>

<!ELEMENT LABELOBJECT EMPTY>
<!ATTLIST LABELOBJECT
LABELNAME
CDATA
#REQUIRED
RESOLUTION
(REPLACE | REUSE | RENAME)
#REQUIRED
>

<!ELEMENT QUERYOBJECT EMPTY>
<!ATTLIST QUERYOBJECT
QUERYNAME
CDATA
#REQUIRED
RESOLUTION
#REQUIRED
>

<!ELEMENT TYPEOBJECT EMPTY>
<!ATTLIST TYPEOBJECT
OBJECTTYPENAME
CDATA
#REQUIRED
RESOLUTION
REPLACE | REUSE | RENAME)
#REQUIRED
>







<!ELEMENT SPECIFICOBJECT EMPTY>
<!ATTLIST SPECIFICOBJECT
1062
NAME
CDATA
DBDNAME
CDATA
OBJECTTYPENAME CDATA
FOLDERNAME
CDATA
REPOSITORYNAME CDATA
RESOLUTION
#REQUIRED
#IMPLIED
#REQUIRED
#REQUIRED
#REQUIRED
#REQUIRED>
Object Import Control File Parameters

The following table lists pmrep Object Import control file parameters:
Element
Attribute Name
IMPORTPARAMS
CHECKIN_AFTER_IMPORT
Required if versioning is
enabled.Checks in objects when
they successfully import.
IMPORTPARAMS
CHECKIN_COMMENTS
Optional. Applies the comments to

the checked in objects.
IMPORTPARAMS
APPLY_LABEL_NAME
Optional. Applies the label name

on the imported objects.
IMPORTPARAMS
RETAIN_GENERATED_VALUE
Required if you use Sequence

Generator, Normalizer, or XML
Source Qualifier transformations.
Retains existing Sequence
Generator, Normalizer, and XML
Source Qualifier transformation
current values in the destination.
IMPORTPARAMS
COPY_SAP_PROGRAM
Optional. Copies SAP program

information into the target
repository.
IMPORTPARAMS
APPLY_DEFAULT_CONNECTION
Optional. Applies the default

connection when a connection
used by a session does not exist in
the target repository. The default
connection is the first connection
from the sorted list of available
connections. Finds the list of
connections in the Workflow
Manager.
FOLDERMAP
SOURCEFOLDERNAME
Required. Import folder name to

match to a folder in the target
repository.
FOLDERMAP
SOURCEREPOSITORYNAME
Required. Repository containing

the source folder.
FOLDERMAP
TARGETFOLDERNAME
Required. Target folder name for

matching.
FOLDERMAP
TARGETREPOSITORYNAME
Required. Repository containing

the target folder.
1063
Element
Attribute Name
TYPEFILTER
TYPENAME
Optional. Imports the objects from

a specific node, such as sources,
targets, or mappings.
RESOLVECONFLICT
LABELOBJECT, QUERYOBJECT,
TYPEOBJECT, AND SPECIFICOBJECT
elements.
You can specify conflict resolutions

for objects.
LABELOBJECT
LABELNAME
Required. Identifies objects by

label name for conflict resolution
specification.
LABELOBJECT
RESOLUTION
Required. Replace, Reuse,

Rename.
QUERYOBJECT
QUERYNAME
Required. Identifies objects from

this query for conflict resolution
specification.
QUERYOBJECT
RESOLUTION
Required. Replace, Reuse, or

Rename.
TYPEOBJECT
OBJECTTYPENAME
Required. Object type for this

conflict resolution. For a list of
object types, see Object Import
Control File Parameters on page
1063.
TYPEOBJECT
RESOLUTION

Rename.
SPECIFICOBJECT
NAME
Required. Specific object name for

this conflict resolution.
SPECIFICOBJECT
DBDNAME
Optional. Source DBD to identify

source object.
SPECIFICOBJECT
OBJECTTYPENAME
Required. Object type for this

conflict resolution. For a list of
object types, see Object Import
Control File Parameters on page
1063.
SPECIFICOBJECT
FOLDERNAME
Required. Source folder the

containing object.
SPECIFICOBJECT
REPOSITORYNAME
Required. Source repository

containing the object.
SPECIFICOBJECT
RESOLUTION

Rename.
You can use the following object types with the OBJECTTYPENAME attribute:
1064
All
Aggregator
App Multi-Group Source Qualifier
Application Source Qualifier
Assignment
Command
Control
Custom Transformation
Decision
Email
Event-raise
Event-wait
Expression
External Procedure
Filter
Input transformation
Joiner
Lookup Procedure
Mapping
Mapplet
MQ Source Qualifier
Normalizer
Output Transformation
Rank
Router
Scheduler
Session
Sequence
SessionConfig
Sorter
Source Definition
Source Qualifier
Start
Target Definition
Timer
Transaction Control
Update Strategy
User Defined Function
Workflow
Worklet
XML Source Qualifier
Note: Use the object type All to reuse or replace all objects.
1065
Object Import Control File Examples

The parameters you specify in the control file code determine the actions that take place when you run the
ObjectImport command in pmrep. The following examples discuss instances in which you use the
ObjectImport command with a control file to import repository objects. The elements and attribute names that
are key to performing the described tasks are designated with comments in the code.
The following table provides a description of sample object import control files:
Function
Description
Import source objects.
Use the TYPEFILTER element to import only source objects.
Import multiple objects into a folder.
Use the IMPORTPARAMS and FOLDERMAP elements to import

multiple objects.
Check in and label imported objects.
Use the CHECKIN_AFTER_IMPORT and APPLY_LABEL_NAME

attributes of the IMPORTPARAMS element to label imported objects.
Retain Sequence Generator and

Normalizer transformation values.
Use the RETAIN_GENERATED_VALUE attribute of the

IMPORTPARAMS element to retain Sequence Generator and
Normalizer values when you import objects.
Import objects and local shortcut

objects to the same repository.
Use all attributes of the FOLDERMAP element to import objects and

local shortcut objects that reference the objects.
Import shortcut objects from another

repository.
Use all attributes of the FOLDERMAP element to import shortcut

objects from another repository.
Import objects to multiple folders.
Use all attributes of the FOLDERMAP element to import objects to

multiple folders.
Import specific objects.
Use the TYPEFILTER element to import specific objects.
Reuse and replace dependent objects.
Use the OBJECTTYPENAME and RESOLUTION attributes of the

TYPEOBJECT element to reuse and replace dependent objects.
Replace invalid mappings.
Use the QUERYOBJECT element to replace invalid mappings.
Rename objects.
Use the RESOLUTION attribute of the SPECIFICOBJECT element to

rename objects.
Copy SAP mappings and SAP

program information.
Use the COPY_SAP_PROGRAM attribute of the IMPORTPARAMS

element to copy SAP mappings and SAP program information.
Apply default connection attributes.
Use the APPLY_DEFAULT_CONNECTION attribute of the

IMPORTPARAMS element to apply default connection attributes.
Resolve object conflicts.
Use the RESOLVECONFLICT element to resolve object conflicts.
Importing Source Objects

You can import source objects. For example, you want to replace all the duplicate objects labeled Monthend
in the target folder. However, you want to rename conflicting source objects that contain Yr_End in the
object name. You have a query called yr_end_qry that finds these objects.
1066
You might create a control file with the following attributes:

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE IMPORTPARAMS SYSTEM "impcntl.dtd">
<IMPORTPARAMS CHECKIN_AFTER_IMPORT ="NO">
<FOLDERMAP SOURCEFOLDERNAME ="OLD_ACCOUNTING"
SOURCEREPOSITORYNAME ="OLD_REPOS"
TARGETFOLDERNAME ="NEW_ACCOUNTING"
TARGETREPOSITORYNAME ="NEW_REPOS"/>

<TYPEFILTER TYPENAME ="SOURCE"/>
<RESOLVECONFLICT>
<LABELOBJECT LABELNAME ="Monthend"
RESOLUTION = "REPLACE"/>
<QUERYOBJECT QUERYNAME ="yr_end_qry"
RESOLUTION ="RENAME"/>
</RESOLVECONFLICT>
</IMPORTPARAMS>
Importing Multiple Objects into a Folder

You can import multiple objects into a folder, check them in, and label them. For example, you want to import
the objects to folder SRC_F1 and apply the label LABEL_IMPORT_NEW to the objects.
<xml version="1.0" encoding="UTF-8"?>

<IMPORTPARAMS CHECKIN_AFTER_IMPORT="YES" CHECKIN_COMMENTS="NEWOBJECTS"
APPLY_LABEL_NAME="LABEL_IMPORT_NEW">
<FOLDERMAP SOURCEFOLDERNAME="SRC_F1" SOURCEREPOSITORYNAME="SRC_REPO1"
TARGETFOLDERNAME="TGT_F1" TARGETREPOSITORYNAME="TGT_REPO1"/>
</IMPORTPARAMS>
Checking In and Labeling Imported Objects

You can import objects into a folder, check them in, label them, and resolve the conflict between session
configuration objects. For example, you want to export the objects from folder SRC_F1 and import them into
folder TGT_F1. The Repository Service creates a session configuration in the target folder by default. You
include the APPLY_LABEL_NAME attribute in the IMPORTPARAMS element to label the imported objects,
and the RESOLVECONFLICT element in the control file to resolve the conflict.


<IMPORTPARAMS CHECKIN_AFTER_IMPORT="YES" CHECKIN_COMMENTS="VERSION1"
APPLY_LABEL_NAME="LABEL_IMPORT_NEW">
<RESOLVECONFLICT>
<TYPEOBJECT OBJECTTYPENAME="SessionConfig" RESOLUTION="REUSE"/>
</RESOLVECONFLICT>
</IMPORTPARAMS>
Retaining Sequence Generator and Normalizer Values

You can retain the values of Sequence Generator and Normalizer transformations when you import objects
and replace all objects in the target folder.
1067


<IMPORTPARAMS CHECKIN_AFTER_IMPORT="YES" CHECKIN_COMMENTS="VERSION1"
APPLY_LABEL_NAME="LABEL_IMPORT_NEW" RETAIN_GENERATED_VALUE="YES">w
<RESOLVECONFLICT>
<TYPEOBJECT OBJECTTYPENAME="ALL" RESOLUTION="REPLACE"/>
</RESOLVECONFLICT>
</IMPORTPARAMS>
Importing Objects and Local Shortcut Objects to the Same

Repository
You can import objects and their respective local shortcut objects to the same repository. For example, you
have folders named SRC_SHARED_F1 and SRC_NONSHARED_F1. The SRC_NONSHARED_F1 folder is
not shared and contains local shortcut objects that reference objects in the SRC_SHARED_F1 folder. You
want to import the objects to different folders in the target repository, and you want the shortcut objects in
folder TGT_NONSHARED_F1 to point to the objects in TGT_SHARED_F1.
<IMPORTPARAMS CHECKIN_AFTER_IMPORT="NO">

<FOLDERMAP SOURCEFOLDERNAME="SRC_SHARED_F1" SOURCEREPOSITORYNAME="SRC__REPO1"
TARGETFOLDERNAME="TGT_SHARED_F1" TARGETREPOSITORYNAME="TGT_REPO1"/>
<FOLDERMAP SOURCEFOLDERNAME="SRC_NONSHARED_F1" SOURCEREPOSITORYNAME="SRC_REPO1"
TARGETFOLDERNAME="TGT_NONSHARED_F1" TARGETREPOSITORYNAME="TGT_REPO1"/>
</IMPORTPARAMS>
Importing Shortcut Objects from Another Repository

You can import objects from other repositories. For example, you have folders in a local repository that
contain shortcuts to objects in a global repository. You want to import the global shortcut objects to a
repository that is registered to the global repository and maintain shortcuts to the original objects in the global
repository.
<IMPORTPARAMS CHECKIN_AFTER_IMPORT="YES" CHECKIN_COMMENTS="global objects"
APPLY_LABEL_NAME="LABEL_IMPORT_GLOBAL_SHORTCUT">

<FOLDERMAP SOURCEFOLDERNAME="SRC_SHARED_F1" SOURCEREPOSITORYNAME="SRC_GDR_REPO1"
TARGETFOLDERNAME="SRC_SHARED_F1" TARGETREPOSITORYNAME="SRC_GDR_REPO2"/>
<FOLDERMAP SOURCEFOLDERNAME="SRC_NONSHARED_F1" SOURCEREPOSITORYNAME="SRC_LDR_REPO1"
TARGETFOLDERNAME="TGT_NONSHARED_F1" TARGETREPOSITORYNAME="SRC_LDR_REPO2"/>
</IMPORTPARAMS>
1068
Importing Objects to Multiple Folders

You can import objects to multiple folders that were exported from multiple folders. For example, you
exported objects from folders SRC_F1, SRC_F2, and SRC_F3, and you want to import them to target folders
TGT_F1, TGT_F2, TGT_F3 in repository TGT_REPO1.
<IMPORTPARAMS CHECKIN_AFTER_IMPORT="YES" CHECKIN_COMMENTS="mulfolders"
APPLY_LABEL_NAME="L1">

TARGETFOLDERNAME="TGT_F1 TARGETREPOSITORYNAME="TGT_REPO1"/>
<RESOLVECONFLICT>
<TYPEOBJECT OBJECTTYPENAME = "SESSIONCONFIG" RESOLUTION="REUSE"/>
</RESOLVECONFLICT>
</IMPORTPARAMS>
Importing Specific Objects

You can choose the objects you want to import. For example, you exported multiple object types to an XML
file. You want to import only mappings, and respective sources and targets, to a folder.
<IMPORTPARAMS CHECKIN_AFTER_IMPORT="YES" CHECKIN_COMMENTS="PMREP_IMPORT_TYPEFILTER"
APPLY_LABEL_NAME="LABEL_MAPPING_TYPEFILTER">
<FOLDERMAP SOURCEFOLDERNAME="SRC_F1" SOURCEREPOSITORYNAME="REPO_EX_1"
TARGETFOLDERNAME="TGT_F1" TARGETREPOSITORYNAME="REPO_EX1_"/>

<TYPEFILTER TYPENAME="MAPPING"/>
</IMPORTPARAMS>
Reusing and Replacing Dependent Objects

You can import sessions, replace the mappings, and reuse the existing sources and targets in the target
folder. For example, you want to replace the mappings and reuse the source definitions, target definitions,
and session configuration objects.
<IMPORTPARAMS CHECKIN_AFTER_IMPORT="YES" CHECKIN_COMMENTS="PMREP_IMPORT_TYPEFILTER"
APPLY_LABEL_NAME="LABEL_SESSION_TYPEFILTER">
<FOLDERMAP SOURCEFOLDERNAME="PMREP_CHECKED_OUT" SOURCEREPOSITORYNAME="REPO_EX_1"
TARGETFOLDERNAME="PMREP_CHECKED_OUT_IMPORT_TYPEFILTER_SESSION"
TARGETREPOSITORYNAME="REPO_EX_1"/>
<TYPEFILTER TYPENAME="SESSION"/>
<RESOLVECONFLICT>
1069


<TYPEOBJECT OBJECTTYPENAME = "MAPPING" RESOLUTION="REPLACE"/>

<TYPEOBJECT OBJECTTYPENAME = "SOURCE DEFINITION" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME = "TARGET DEFINITION" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME = "SESSIONCONFIG" RESOLUTION="REUSE"/>

<TYPEOBJECT OBJECTTYPENAME = "ALL" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME = "SOURCE DEFINITION" RESOLUTION="REPLACE"/>
<TYPEOBJECT OBJECTTYPENAME = "MAPPING" RESOLUTION="REPLACE"/>
</RESOLVECONFLICT>
</IMPORTPARAMS>
Note: When you reuse or replace an object type, the resolution for that object type overrides the resolution
for all object types. The preceding example replaces source definitions and mappings and reuses the
remaining objects. Use the object type All to reuse or replace all objects. For more information about object
types, see Object Import Control File Parameters on page 1063.
Replacing Invalid Mappings

You can replace invalid mappings and associated child objects that are returned by a query. For example,
you want to replace objects returned by the query QUERY_PARENT_RENAME.
<IMPORTPARAMS CHECKIN_AFTER_IMPORT="YES"
CHECKIN_COMMENTS="PMREP_IMPORT_QUERY_PARENT_REPLACE_CHILD_REUSE"
APPLY_LABEL_NAME="LABEL_QUERY_PARENT_RENAME_CHILD_REUSE">
<FOLDERMAP SOURCEFOLDERNAME="PMREP_CHECKED_OUT" SOURCEREPOSITORYNAME="REPO_EX_1"
TARGETFOLDERNAME="PMREP_CHECKED_OUT" TARGETREPOSITORYNAME="REPO_EX_1"/>
<RESOLVECONFLICT>

<QUERYOBJECT QUERYNAME="QUERY_PARENT_RENAME" RESOLUTION="REPLACE"/>
</RESOLVECONFLICT>
</IMPORTPARAMS>
Renaming Objects
You can rename specific objects when object conflicts occur. For example, you want to the rename the
objects ADDRESS, ADDRESS1, R_LKP, MAP_MLET, R_S3, WF_RS1. The Repository Service appends the
object names with a number.
<IMPORTPARAMS CHECKIN_AFTER_IMPORT="YES"
CHECKIN_COMMENTS="PMREP_IMPORT_SPECIFICOBJECT_RENAME"
APPLY_LABEL_NAME="LABEL_IMPORT_SPECIFIC_OBJECT_RENAME">
<FOLDERMAP SOURCEFOLDERNAME="SRC_FOLDER1" SOURCEREPOSITORYNAME="REPO_EX_1"
TARGETFOLDERNAME="TGT_FOLDER1" TARGETREPOSITORYNAME="REPO_EX_1"/>
<RESOLVECONFLICT>

1070
<SPECIFICOBJECT NAME="ADDRESS" DBDNAME="sol805" OBJECTTYPENAME="Source Definition"

FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="REPO_EX_1" RESOLUTION="RENAME"/>
<SPECIFICOBJECT NAME="ADDRESS1" OBJECTTYPENAME="Target Definition"
<SPECIFICOBJECT NAME="R_LKP" OBJECTTYPENAME="Lookup Procedure"
<SPECIFICOBJECT NAME="MAP_MLET" OBJECTTYPENAME="Mapping" FOLDERNAME="PMREP_CHECKED_OUT"
REPOSITORYNAME="REPO_EX_1" RESOLUTION="RENAME"/>
<SPECIFICOBJECT NAME="R_S3" OBJECTTYPENAME="Session" FOLDERNAME="PMREP_CHECKED_OUT"
<SPECIFICOBJECT NAME="WF_RS1" OBJECTTYPENAME="Workflow" FOLDERNAME="PMREP_CHECKED_OUT"
</RESOLVECONFLICT></IMPORTPARAMS>
Copying SAP Mappings and SAP Program Information

You can copy SAP program information when you import SAP mappings. For example, you want to import
the SAP mappings and copy the program information associated with the object you are importing to folder
TGT_F1.

<IMPORTPARAMS CHECKIN_AFTER_IMPORT="YES" CHECKIN_COMMENTS="Version2 of objects"
APPLY_LABEL_NAME="LABEL71_REPLACE_FOLDER" COPY_SAP_PROGRAM="YES">
TARGETFOLDERNAME="TGT_F1" TARGETREPOSITORYNAME="REPO_EX_1"/>
</IMPORTPARAMS>
Applying Default Connection Attributes

You can apply a default connection attribute to a session if a connection is not present in the target
repository. For example, no connection exists in target repository REPO_EX_1.

<IMPORTPARAMS CHECKIN_AFTER_IMPORT="NO" APPLY_DEFAULT_CONNECTION="YES">
<RESOLVECONFLICT>
<SPECIFICOBJECT NAME="R_S3" OBJECTTYPENAME="Session" FOLDERNAME="PMREP_CHECKED_OUT"
REPOSITORYNAME="REPO_EX_1" RESOLUTION="REPLACE"/>
<RESOLVECONFLICT>
</IMPORTPARAMS>
Resolving Object Conflicts

You can resolve object conflicts for labeled objects in the target repository. For example, you have mappings,
mapplets, sources, and targets labeled LBL_MPNG_MPLTS_SRCS_TGTS. You want to replace these
objects and label them REPLACE_LBL_MPNG_MPLTS_SRCS_TGTS and reuse all transformations.
1071

<IMPORTPARAMS CHECKIN_AFTER_IMPORT="YES" CHECKIN_COMMENTS="PMREP_IMPORT_LABEL_REPLACE"
APPLY_LABEL_NAME="REPLACE_LBL_MPNG_MPLTS_SRCS_TGTS" >

<RESOLVECONFLICT>
<LABELOBJECT LABELNAME="LBL_MPNG_MPLTS_SRCS_TGTS" RESOLUTION="REPLACE"/>
<TYPEOBJECT OBJECTTYPENAME="Lookup Procedure" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME="Stored Procedure" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME="Expression" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME="Filter" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME="Aggregator" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME="Rank" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME="Normalizer" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME="Router" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME="Sequence" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME="Sorter" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME="update strategy" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME="Custom Transformation" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME="Transaction control" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME="External Procedure" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME="Joiner" RESOLUTION="REUSE"/>
<TYPEOBJECT OBJECTTYPENAME="SessionConfig" RESOLUTION="REUSE"/>
</RESOLVECONFLICT>
</IMPORTPARAMS>
Using the Deployment Control File

A deployment control file is an XML file that you use with the DeployFolder and DeployDeploymentGroup
pmrep commands to deploy a folder or deployment group. You can create a deployment control file manually
to provide parameters for deployment, or you can create a deployment control file with the Copy Wizard.
If you create the deployment control file manually, it must conform to the depcntl.dtd file that is installed with
the PowerCenter Client. You include the location of the depcntl.dtd file in the deployment control file.
You can specify a deployment timeout in the deployment control file. The deployment timeout is the period of
time that pmrep waits to acquire object locks in the target repository. By default, pmrep waits indefinitely until
it acquires locks or you cancel the deployment. To cancel a deployment while pmrep is waiting to acquire
locks, press Ctrl+C.
Note: You must create the deployment control file manually to use some deployment parameters such as
DEPLOYTIMEOUT.
The following is a sample of the depcntl.dtd file:
<!ELEMENT DEPLOYPARAMS (DEPLOYFOLDER?, DEPLOYGROUP?)>
<!ATTLIST DEPLOYPARAMS
DEFAULTSERVERNAME
CDATA
#IMPLIED
COPYPROGRAMINFO
(YES | NO) "YES"
COPYMAPVARPERVALS
(YES | NO) "NO"
RETAINMAPVARPERVALS (YES | NO) "NO"
COPYWFLOWVARPERVALS (YES | NO) "NO"
COPYWFLOWSESSLOGS
(YES | NO) "NO"
COPYDEPENDENCY
(YES | NO) "YES"
LATESTVERSIONONLY
(YES | NO) "NO"
CHECKIN_COMMENTS
CDATA
#IMPLIED
1072
DEPLOYTIMEOUT
RETAINGENERATEDVAL
RETAINSERVERNETVALS
COPYDEPLOYMENTGROUP
CDATA
"-1"
(YES | NO) "YES"
(YES | NO) "YES">
(YES | NO) "NO">


<!ELEMENT DEPLOYFOLDER (REPLACEFOLDER?, DEPLOYEDFOLDEROWNER?, OVERRIDEFOLDER*)>
<!ATTLIST DEPLOYFOLDER
NEWFOLDERNAME
CDATA
#IMPLIED>

<!ELEMENT REPLACEFOLDER EMPTY>
<!ATTLIST REPLACEFOLDER
FOLDERNAME
CDATA
RETAINMAPVARPERVALS
(YES |
RETAINWFLOWVARPERVALS (YES |
RETAINWFLOWSESSLOGS
(YES |
MODIFIEDMANUALLY
(YES |
RETAINORIGFOLDEROWNER (YES |
NO)
NO)
NO)
NO)
NO)
#REQUIRED
"NO"
"YES"
"NO"
"NO"
"NO">


<!ELEMENT OVERRIDEFOLDER EMPTY>
<!ATTLIST OVERRIDEFOLDER
SOURCEFOLDERNAME
CDATA
#REQUIRED
SOURCEFOLDERTYPE
(LOCAL | GLOBAL) "LOCAL"
TARGETFOLDERNAME
CDATA
#REQUIRED
TARGETFOLDERTYPE
(LOCAL | GLOBAL) "LOCAL"
MODIFIEDMANUALLY
(YES | NO)
"NO"

<!ELEMENT DEPLOYGROUP (REPLACEDG?, TARGETDGOWNER?, OVERRIDEFOLDER*, APPLYLABEL?)>
<!ATTLIST DEPLOYGROUP
CLEARSRCDEPLOYGROUP (YES | NO) "NO">
NEWDEPLOYGROUPNAME
CDATA #IMPLIED

<!ELEMENT APPLYLABEL EMPTY>
<!ATTLIST APPLYLABEL
SOURCELABELNAME
CDATA
#IMPLIED
SOURCEMOVELABEL
(YES | NO)
"NO"
TARGETLABELNAME
CDATA
#IMPLIED
TARGETMOVELABEL
(YES | NO)
"NO">

<!ELEMENT DEPLOYEDFOLDEROWNER EMPTY>
<!ATTLIST DEPLOYEDFOLDEROWNER
USERNAME
CDATA
#IMPLIED
SECURITYDOMAIN
CDATA
GROUPNAME
CDATA #IMPLIED>
#IMPLIED


<!ELEMENT REPLACEDG EMPTY>
<!ATTLIST REPLACEDG
DGNAME
CDATA
#REQUIRED
SECURITYDOMAIN
CDATA
#IMPLIED

<!ELEMENT TARGETDGOWNER EMPTY>
<!ATTLIST TARGETDGOWNER
USERNAME
CDATA
#IMPLIED
SECURITYDOMAIN
CDATA
#IMPLIED
1073
Deployment Control File Parameters

The following table lists pmrep deployment control file parameters:
Element
Attribute Name
DEPLOYPARAMS
DEFAULTSERVERNAME
Optional. Integration Service registered

in the target repository to run workflows.
For any deployment, you can specify
one default server name.
COPYPROGRAMINFO
Optional. Copies SAP installed ABAP

program.
COPYMAPVARPERVALS
Optional. Copies mapping variable

persistent values.
RETAINMAPVARPERVALS
Optional. Retains mapping variable

persistent values in the target.
COPYWFLOWVARPERVALS
Optional. Copies workflow variable

persistent values.
COPYWFLOWSESSLOGS
Optional. Copies workflow logs.
COPYDEPENDENCY
Optional. Copies dependency

information for objects in mappings.
COPYDEPLOYMENTGROUP
Optional. Copies the deployment group

along with the objects in the deployment
group to the target repository.
VALIDATETARGETREPOSITORY
Optional. Validates objects in the target

repository.
LATESTVERSIONONLY
Optional. Copies the latest version.
CHECKIN_COMMENTS
Optional. Overrides the default comment

and adds a comment in the target
repository when you copy or deploy an
object. You must set
LATESTVERSIONONLY to true to use
this attribute.
DEPLOYTIMEOUT
Optional. Period of time (in seconds)

that pmrep attempts to acquire locks on
objects in the target repository. A value
of 0 fails the copy operation immediately
if pmrep cannot obtain a lock. A value of
-1 instructs pmrep to wait indefinitely
until it acquires locks or the user cancels
the operation. Default is -1.
RETAINGENERATEDVAL
Optional. Keeps the current value for

Sequence Generator or Normalizer
transformations.
RETAINSERVERNETVALS
Optional. Retains server-network-related

values in tasks.
(Use with DeployFolder and

DeployDeploymentGroup)
1074
Element
Attribute Name
DEPLOYFOLDER
NEWFOLDERNAME
Optional. Creates a folder with this

name.
FOLDERNAME
Required. Names the folder after

replacing it.
RETAINMAPVARPERVALS
Optional. Retains mapping variable

persistent values in the target.
RETAINWFLOWVARPERVALS
Optional. Retains workflow variable

persistent values.
RETAINWFLOWSESSLOGS
Optional. Retains workflow session logs

in the target.
MODIFIEDMANUALLY
Optional. Compares folders if objects in

the target folder have been created or
modified since the previous deployment.
RETAINORIGFOLDEROWNER
Optional. Retains the existing folder

owner. pmrep ignores any information
provided in the
DEPLOYEDFOLDEROWNER element.
OVERRIDEFOLDER
SOURCEFOLDERNAME
Required. If deploying a folder, specifies

the current folder that shortcuts point to.
(Use with DeployFolder)

REPLACEFOLDER
(Use with DeployFolder)

If deploying a deployment group,

specifies the following folders:
- Folder or folders that shortcuts point to
- Folder or folders containing the
deployment group objects
SOURCEFOLDERTYPE
Optional. If deploying a folder, specifies

the type of folder that shortcuts point to.
Use local or global shortcuts.
TARGETFOLDERNAME
Required. If deploying a folder, specifies

the folder that shortcuts point to.
If deploying a deployment group,
specifies the following folders:
- Folder or folders that shortcuts point to
- Folder or folders containing the
deployment group objects
TARGETFOLDERTYPE
Optional. If deploying a folder, specifies

the type of folder that shortcuts point to.
Use local or global shortcuts.
MODIFIEDMANUALLY
Optional. Compares folders if objects in

the target folder have been created or
modified since the previous deployment.
Use this attribute only with the
DeployDeploymentGroup command.
1075
Element
Attribute Name
DEPLOYGROUP
CLEARSRCDEPLOYGROUP
Optional. Removes objects from the

source group after deploying.
NEWDEPLOYGROUPNAME
Optional. Creates a deployment group

with this name. Ignored if REPLACEDG
is specified. Default is the source
deployment group name.
REPLACEDG
DGNAME
Optional. Name of the deployment group

to be replaced.
RETAINORIGINALOWNER
Optional. Specifies whether to retain the

owner of the deployment group being
replaced in the target repository.
TARGETDGOWNER
USERNAME
Optional. Owner of the copied

deployment group. Default is the owner
of the source deployment group.
SECURITYDOMAIN
Optional. Security domain of the target

deployment group.
APPLYLABEL
SOURCELABELNAME
Optional. Applies a label to all the

objects in the source group.
SOURCEMOVELABEL
Optional. Moves the label from a

different version of the object in the
source group to the deployment group
version of the object. If the Repository
Agent detects the label is applied to
another version of the same object, you
can choose to move the label to the
selected version of the object.
TARGETLABELNAME
Optional. Applies a label to all the

objects deployed to the target repository.
TARGETMOVELABEL
Optional. Moves the label from a

different version of the object in the
target group to the deployment group
version of the object. If the Repository
Agent detects the label is applied to
another version of the same object, you
can choose to move the label to the
latest version of the object.
DEPLOYEDFOLDEROWNE
R
USERNAME
Optional. Owner of the deployed folder

or deployment group in the target
repository.
(Use with
(Use with

1076
Element
Attribute Name
SECURITYDOMAIN
Optional. Name of the security domain

that the owner of the deployed folder or
deployment group belongs to.
GROUPNAME
Optional. Group owner of the deployed

folder or deployment group in the target
repository.
Deployment Control File Examples

The parameters you specify in the deployment control file code determine the actions that occur when you
execute the DeployFolder or DeployDeploymentGroup commands in pmrep. The following examples discuss
instances in which you use the DeployFolder and DeployDeploymentGroup commands with a deployment
control file.
Deploying the Latest Version of a Folder

You can deploy the latest version of a folder and include all dependencies. For example, you need to retain
the current values in a Sequence Generator transformation, and you need to point the shortcuts from the
sc_folder to the new_sc_folder. After you copy the folder, you want to rename it to new_year.
You might create a control file with following attributes:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE DEPLOYPARAMS SYSTEM "depcntl.dtd">
<DEPLOYPARAMS DEFAULTSERVERNAME ="info7261"
COPYPROGRAMINFO ="NO"
COPYWFLOWVARPERVALS ="NO"
COPYWFLOWSESSLOGS ="NO"
COPYDEPENDENCY ="YES"
LATESTVERSIONONLY = "NO">
<REPLACEFOLDER FOLDERNAME ="NEW_YEAR"
RETAINMAPVARPERVALS ="YES"/>
<OVERRIDEFOLDER SOURCEFOLDERNAME ="SC_FOLDER"
OVERRIDEFOLDERNAME ="NEW_SC_FOLDER"/>
</DEPLOYPARAMS>
Deploying the Latest Version of a Deployment Group

You can deploy the latest version of a deployment group and apply a label to the objects in the deployment
group. For example, you want to apply the label NEW_SRC_LABEL_NAME to all objects in the source group,
and NEW_TGT_LABEL_NAME to all objects in the target group. You might create a control file with following
attributes:
<DEPLOYPARAMS DEFAULTSERVERNAME="dg_sunqa2_51880"
COPYPROGRAMINFO="YES"
COPYMAPVARPERVALS="YES"
COPYWFLOWVARPERVALS="YES"
COPYWFLOWSESSLOGS="NO"
Deployment Control File Examples
1077
COPYDEPENDENCY="YES"
LATESTVERSIONONLY="YES"
RETAINGENERATEDVAL="YES"
RETAINSERVERNETVALS="YES">
<DEPLOYGROUP CLEARSRCDEPLOYGROUP="NO">
<OVERRIDEFOLDER SOURCEFOLDERNAME="SRC_FOLDER1"
SOURCEFOLDERTYPE="LOCAL"
TARGETFOLDERNAME="TGT_FOLDER1"
TARGETFOLDERTYPE="LOCAL"/>
<APPLYLABEL SOURCELABELNAME="NEW_SRC_LABEL_NAME"
SOURCEMOVELABEL="YES"
TARGETLABELNAME="NEW_TGT_LABEL_NAME"
TARGETMOVELABEL="YES" />
</DEPLOYGROUP>
</DEPLOYPARAMS>
Listing Multiple Source and Target Folders

Use the OVERRIDEFOLDER element in the control file to list multiple source and target folders. Use the
SOURCEFOLDERNAME and TARGETFOLDERNAME attributes to specify the following folders in the source
and target repositories:
The folder or folders that shortcuts point to
The folder or folders containing the deployment group objects
When you run the pmrep command, DeployDeploymentGroup, the deploy process picks the right target folder
to use after checking the objects in the deployment group.
For example, if a deployment group contains objects in two folders with shortcuts to a third folder, you can
create a control file with three occurrences of OVERRIDEFOLDER. The following sample control file deploys
a deployment group that contains objects in the folders OBJECTFOLDER1 and OBJECTFOLDER2 that
contain shortcuts pointing to the folder SHAREDSHORTCUT:
<DEPLOYPARAMS DEFAULTSERVERNAME="dg_sun_71099"
COPYPROGRAMINFO="YES"
COPYMAPVARPERVALS="YES"
COPYWFLOWVARPERVALS="YES"
COPYWFLOWSESSLOGS="NO"
COPYDEPENDENCY="YES"
LATESTVERSIONONLY="YES"
RETAINGENERATEDVAL="YES"
RETAINSERVERNETVALS="YES">
<DEPLOYGROUP CLEARSRCDEPLOYGROUP="NO">
<OVERRIDEFOLDER SOURCEFOLDERNAME="OBJECTFOLDER1"
TARGETFOLDERNAME="OBJECTFOLDER1"
<OVERRIDEFOLDER SOURCEFOLDERNAME="OBJECTFOLDER2"
TARGETFOLDERNAME="OBJECTFOLDER2"
<OVERRIDEFOLDER SOURCEFOLDERNAME="SHAREDSHORTCUTS"
SOURCEFOLDERTYPE="GLOBAL"
TARGETFOLDERNAME="SHAREDSHORTCUTS"
TARGETFOLDERTYPE="GLOBAL"/>
</DEPLOYGROUP>
</DEPLOYPARAMS>
1078
Tips for Working with pmrep Files

Use the -n option when you use the pmrep commands Updatesrcprefix or Updatetargprefix.
When you include the -n option, you must enter the name of the source or target instance for the -t option.
The source or target instance name must match the name displayed in the session properties or the name
output by the Listtablesbysess command.
Use the -n option to use the Listtablesbysess command with the Updatesrcprefix or Updatetargprefix
commands in a shell script if the source and target instance names match. Also, use the -n option to update a
source even if the session uses a shortcut to a mapping.
When using the pmrep command ListObjects, enter a character or set of characters that is not used in
repository object names for the column separator, end of record indicator, and end of listing indicator.
When you enter characters to separate records and columns, and to indicate the end of the listing, use
characters that are not included in repository object names. This helps you use a shell script to parse the
object metadata.
In pmrep, use the -v option when restoring a repository that uses an external directory service for user
management.
When you include the -v option with Restore, you can retain the external directory service registration for the
repository. If you do not enter this option with the valid administrator user name and password, the restored
repository defaults to repository authentication mode and you lose the association between login names and
user names.
Tips for Working with pmrep Files
1079
Index
A
AbortTask (pmcmd)
description 939
abortWorkflow
infacmd wfs 822
AbortWorkflow (pmcmd)
description 941
AddAlertUser (infacmd isp) 192
AddConnectionPermissions (infacmd isp) 194
AddDomainLink (infacmd isp) 196
AddDomainNode (infacmd isp) 198
AddGroupPrivilege (infacmd isp) 200, 214
AddLicense (infacmd isp) 202
AddNamespace (infacmd isp) 203
AddNodeResource (infacmd isp) 206
AddParameterSetEntries (infacmd dis) 108
AddRolePrivilege (infacmd isp) 208
AddServiceLevel (infacmd isp) 210
AddToDeploymentGroup (pmrep)
description 981
AddUserPrivilege (infacmd isp) 212
alerts
configuring SMTP settings using infacmd isp 563
listing SMTP settings using infacmd 441
listing subscribed users infacmd isp 393
subscribing users to 192
unsubscribing from using infacmd isp 458
Analyst Service
creating in a domain 61
listing configuration for 67
listing properties for 68
updating properties for 70
upgrading business glossary data 85
Analyst Service process
configuring properties for 72
application archive (iar) files
deploying to Data Integration Service 118
application service processes
getting status for 375
application services
disabling 345
getting properties for 371
getting status for 376
removing using infacmd isp 483
applications
listing objects for 122
purging the result set cache for 142
removing from Data Integration Service 156
renaming 145
restoring 147
starting 151
stopping 153
updating 157
1080
applications services
enabling 355, 819
ApplyLabel (pmrep)
description 982
AssignedToLicense (infacmd isp) 216
AssignGroupPermission (infacmd isp) 218
AssignISToMMService (infacmd isp) 220
AssignLicense (infacmd isp) 222
AssignPermission (pmrep)
description 984
AssignRoleToGroup (infacmd isp) 223
AssignRoletoUser (infacmd isp) 225
AssignRSToWSHubService (infacmd isp) 227
AssignUserPermission (infacmd isp) 229
audit trail tables
creating 64
creating, Content Management Service 87
deleting 66
deleting, Content Management Service 91
B
BackUp (pmrep)
description 986
BackupApplication (infacmd dis) 110
BackupContents (infacmd mrs) 573
BackupDARepositoryContents (infacmd isp) 231
BackupDomain (infasetup)
description 893
binary log files
converting to text, XML, or readable text 233
Blaze service
stopping 154
C
CancelDataObjectCacheRefresh (infacmd dis) 111
cancelProfileExecution (infacmd ps) 644
cancelWorkflow
infacmd wfs 826
ChangeOwner (pmrep)
description 987
CheckIn (pmrep)
description 988
CheckInObject (infacmd mrs) 575
CleanUp (pmrep)
description 988
ClearDeploymentGroup (pmrep)
description 989
CloseForceListener (infacmd pwx) 666
CloseListener (infacmd pwx) 668
column
options for infacmd 804
columns
command line mode for pmcmd
connecting 934
command line programs
overview 32
syntax for 34
command line utilities
configuring 29
domains.infa file 31
command line utilities (configure Metadata Manager utilities 30
command line utilities (configure PowerCenter utilities 30
commands
entering options and arguments for 33
compute node
listing attributes for 721
setting attributes 724
concurrent workflows
starting from command line 964
stopping from command line 969
CondenseLogger (infacmd pwx) 671
configuring
command line utilities 29
Connect (pmcmd)
description 942
Connect (pmrep)
description 989
connect string
examples 980
syntax 980
connection
Web Content-Kapow Katalyst 295
connection options
DB2 for infacmd 264
SEQ for infacmd 286
VSAM for infacmd 293
connection permissions
adding to users or groups 194
listing for users or groups 399
listing using infacmd isp 400
connections
creating with infacmd 234
exporting using infacmd isp 360
importing using infacmd isp 388
listing options for using infacmd isp 406
Oracle 281
removing from domains using infacmd isp 460
renaming with infacmd 493
updating using infacmd isp 526
connectivity
connect string examples 980
content
importing from application files 729
Content Management Service
listing options for 94
purging orphaned reference data 96
removing using infacmd cms 97
synchronizing data with master CMS machine 99
updating options for 101
Upgrading 105
Content Management Service process
configuring options for 103
control file
deployment 1072
object import 1061
control file (continued)

ObjectImport XML example 1066
control files
examples for domain objects 887
examples for Model repository objects 888
infacmd 874
naming conventions 875
parameters for domain objects 876, 880
parameters for Model repository objects 877, 882
rules and guidelines 887
schema files 874
ConvertLogFile (infacmd isp) 233
CPU profile
calculating using infacmd isp 498
Create (pmrep)
description 991
CreateAuditTables (infacmd as) 64
CreateAuditTables (infacmd cms) 87
CreateConnection (infacmd isp) 234
CreateConnection (pmrep)
description 991
CreateContent (infacmd tdm) 817
CreateContents (infacmd mrs) 577
CreateDARepositoryContents (infacmd isp) 297
createdatamaps (infacmd pwx) 673
CreateDeploymentGroup (pmrep)
description 997
CreateFolder (infacmd isp) 298
CreateFolder (pmrep)
description 997
CreateGrid (infacmd isp) 300
CreateGroup (infacmd isp) 302
CreateGroup (pmrep)
description 999
CreateIntegrationService (infacmd isp) 303
CreateLabel (pmrep)
description 999
CreateListenerService (infacmd pwx) 676
CreateLoggerService (infacmd pwx) 678
CreateMMService (infacmd isp) 313
CreateOSProfile (infacmd isp) 317
CreateProject (infacmd mrs) 579, 580
CreateReportingService (infacmd isp) 320
CreateRepositoryService (infacmd isp) 324
CreateRole (infacmd isp) 329
CreateSAPBWService (infacmd isp) 331
CreateSchedule (infacmd sch) 736
CreateService (infacmd as) 61
CreateService (infacmd cms) 89
CreateService (infacmd dis) 113
CreateService (infacmd mrs) 582
CreateService (infacmd search) 763
CreateService (infacmd tdm) 811
CreateUser (infacmd isp) 334
CreateWH (infacmd ps) 646
CreateWSHubService (infacmd isp) 337
D
Data Analyzer repository
backing up content 231
creating content 297
deleting content 340
restoring contents using infacmd isp 496
upgrading contents using infacmd isp 567
upgrading users and groups using infacmd isp 568
Index
1081
Data Integration Service

configuring compute properties 161
creating 113
listing compute properties 125
Data Integration Service options
infacmd syntax 169
Data Integration Service process
listing properties for 133, 138
data object cache
refreshing 144
data objects
DB2
infacmd connection options 264
DefineDomain (infasetup)
description 895
DefineGatewayNode (infasetup)
description 906
DefineWorkerNode (infasetup)
description 912
Delete (pmrep)
description 999
DeleteAuditTables (infacmd as) 66
DeleteAuditTables (infacmd cms) 91
DeleteConnection (pmrep)
description 1000
DeleteContents (infacmd mrs) 585
DeleteDARepositoryContents (infacmd isp) 340
DeleteDeploymentGroup (pmrep)
description 1000
DeleteDomain (infasetup)
description 915
DeleteFolder (infacmd mrs) 587
DeleteFolder (pmrep)
description 1001
DeleteLabel (pmrep)
description 1001
DeleteNamespace (infacmd isp) 342
DeleteObject (pmrep)
description 1001
DeleteParameterSetEntries (infacmd dis) 116, 129
DeleteProject (infacmd mrs) 588
DeleteSchedule (infacmd sch) 739
depcntl.dtd
listing 1072
DeployApplication (infacmd dis) 118
DeployDeploymentGroup (pmrep)
description 1002
deployed applications
backing up 110
listing 120
DeployFolder (pmrep)
description 1004
DeployImport (infacmd rtm) 729
deploying objects
depcntl.dtd 1072
deployment control file
description 1072
deployment groups
listing multiple folders 1078
DeployObjects
infacmd oie 634
description 452
DisableNodeResource (infacmd isp) 343
1082
Index
DisableService (infacmd isp) 345

DisableService (infacmd tdm) 820
DisableServiceProcess (infacmd isp) 347
DisableUser (infacmd isp) 349
Disconnect (pmcmd)
description 944
DisplayAllLogger (infacmd pwx) 683
DisplayCPULogger (infacmd pwx) 685
DisplayEventsLogger (infacmd pwx) 688
DisplayMemoryLogger (infacmd pwx) 690
DisplayRecordsLogger (infacmd pwx) 692
displayStatsListener (infacmd pwx) 695
DisplayStatusLogger (infacmd pwx) 698
domain gateway hosts
pinging 451
domain monitoring
list options 421
purge options 456
update options 540
domains
backing up using infasetup 893
creating using infasetup 895
deleting using infasetup 915
listing linked domains using infacmd isp 407
listing properties using infacmd isp 409
pinging 451
removing links using infacmd isp 463
restoring using infasetup 920
updating properties using infacmd isp 529
dropTables (infacmd wfs) 830
DropWH (infacmd ps) 647
DTD file
plug-in template 1038
E
EditUser (infacmd isp) 351
EditUser (pmrep)
description 1005
EnableNodeResource (infacmd isp) 354
EnableService (infacmd isp) 355
EnableService (infacmd tdm) 819
EnableServiceProcess (infacmd isp) 357
EnableUser (infacmd isp) 358
environment variables
configuring for command-line programs 39
ICMD_JAVA_OPTS 40
INFA_CLIENT_RESILIENCE_TIMEOUT 41
INFA_CODEPAGENAME 42
INFA_DEFAULT_DATABASE_PASSWORD 42
INFA_DEFAULT_DB_TRUSTSTORE_PASSWORD 43
INFA_DEFAULT_DOMAIN 44
INFA_DEFAULT_DOMAIN_PASSWORD 45
INFA_DEFAULT_DOMAIN_USER 46
INFA_DEFAULT_PWX_OSEPASSWORD 46
INFA_DEFAULT_PWX_OSPASSWORD 47
INFA_JAVA_CMD_OPTS 48
INFA_NODE_KEYSTORE_PASSWORD 50
INFA_NODE_TRUSTSTORE_PASSWORD 51
INFA_PASSWORD 49
INFA_REPCNX_INFO 52
INFA_REPOSITORY_PASSWORD 52
INFATOOL_DATEFORMAT 53
Execute (infacmd ps) 649
executeProfile (infacmd ps) 651
ExecuteQuery (pmrep)
description 1005
ExecuteSQL (infacmd sql) 773

Exit (pmrep)
description 1007
Export (infacmd rtm) 731
export control files
infacmd 874
parameters for domain objects 876
parameters for Model repository objects 877
schema files 874
exportControl.xsd
infacmd control files 874
ExportDomainObjects (infacmd isp)
description 360
ExportObjects
infacmd oie 635
exportResources
infacmd oie 637
ExportToPC (infacmd ipc) 187
ExportUsersAndGroups (infacmd isp) 362
external security modules
registering 1038
unregistering 1047
F
features
validating 570
FileSwitchLogger (infacmd pwx) 701
FindCheckout (pmrep)
description 1007
folders
deleting 1001
deploying 1004
modifying 1029
moving objects between using infacmd isp 450
moving using infacmd isp 448
updating description using infacmd isp 531
G
gateway
updating information using infacmd isp 532
GenerateAbapProgramToFile (pmrep)
description 1009
GenerateEncryptionKey (infasetup)
description 918
infacmd xrf 872
GetConnectionDetails (pmrep)
description 1008
getDomainObjectPermissions (infacmd aud) 74
getExecutionStatus (infacmd ps) 652
GetFolderInfo (infacmd isp) 364
GetLastError (infacmd isp) 366
GetLog (infacmd isp) 367
GetNodeName (infacmd isp) 371
getPrivilegeAssociation (infacmd aud) 76
getProfileExecutionStatus (infacmd ps) 654
GetRequestLog
infacmd ms 622
GetRunningSessionsDetails (pmcmd)
description 944
GetServiceDetails (pmcmd)
description 945
GetServiceOption (infacmd isp) 371
GetServiceProcessOption (infacmd isp) 373
GetServiceProcessStatus (infacmd isp) 375
GetServiceProperties (pmcmd)
description 947
GetServiceStatus (infacmd isp) 376
GetSessionLog (infacmd isp) 378
GetSessionStatistics (pmcmd)
description 948
GetSystemLogDirectory (infacmd isp) 381
GetTaskDetails (pmcmd)
description 950
getUserGroupAssociation (infacmd aud) 78, 80
getUsersPersonalInfo (infacmd aud) 82
GetWorkflowDetails (pmcmd)
description 952
GetWorkflowLog (infacmd isp) 385
grids
creating 300
listing nodes using infacmd isp 411
updating assigned nodes using infacmd isp 533
group permissions
assigning to objects 218
listing for domain objects 413
removing on objects 469
groups
creating in domains 302
exporting 362
importing using infacmd isp 388, 391
listing for a user 417
H
Help (infacmd) 387
Help (pmcmd)
description 955
Help (pmrep)
description 1011
I
IBM DB2
connect string example 980
ICMD_JAVA_OPTS
configuring 40
impcntl.dtd
description 1061
Import (infacmd rtm) 733
import control files
infacmd 874
parameters for domain objects 880
parameters for Model repository objects 882
Index
1083
import control files (continued)

schema files 874
import from PowerCenter
options 190
importControl.xsd
ImportDomainObjects (infacmd isp)
description 388
importing objects
impcntl.dtd 1061
ObjectImport XML example 1066
ImportObjects
infacmd oie 639
ImportUsersAndGroups (infacmd isp)
description 391
configuring 41
INFA_CODEPAGENAME
configuring 42
configuring 42
configuring 43
INFA_DEFAULT_DOMAIN
configuring 44
configuring 45
configuring 46
configuring 46
configuring 47
INFA_JAVA_CMD_OPTS
configuring 48
configuring 50
configuring 51
INFA_PASSWORD
configuring 49
INFA_REPCNX_INFO
configuring 52
configuring 52
infacmd
control files 874
disassociating Metadata Manager Service 515
displaying help for commands 387
Integration Service options 307, 615
licenses, unassigning 517
listing plugin identifiers for 58
nodes, switching from worker to gateway 510
Reporting Service options 322
return codes 59
running commands 59
SAP BW Service options 333
SAP BW service process options 334
security domains, listing 433
service process options 311
updating domain information 60
version information, displaying 571
Web Services Hub service options 339
infacmd advanced
validating features 570
infacmd as
configuring properties for Analyst Service process 72
creating Analyst Service in a domain 61
1084
Index
infacmd as (continued)
creating audit trail tables 64
deleting audit trail tables 66
listing configuration for Analyst Service 67
listing properties for Analyst Service process 68
updating properties for Analyst Service 70
infacmd bg
Upgrading Business Glossary data in the Model repository 85
infacmd cms
configuring options for Content Management Service process 103
creating audit trail tables 87
creating Content Management Service in a domain 89
deleting audit trail tables 91
listing options for Content Management Service 93
listing options for Content Management Service process 94
purging orphaned reference data 96
removing Content Management Service from a domain 97
synchronizing data 99
updating options for Content Management Service 101
upgrading the service 105
infacmd commands
getting help for 387
infacmd dis
adding parameter set entries 108
backing up deployed application 110
configuring application properties 159
configuring compute properties 161
configuring data object properties 163
configuring properties for Data Integration Service 167
configuring properties for Data Integration Service process 177
creating Data Integration Service 113
data object options 164
deleting parameter set entries 116, 129
deploying application archive (iar) files 118
list parameter sets in an application 132
list the objects in a parameter set 130
listing compute properties 125
listing deployed applications 120
listing objects for applications 122
listing properties for applications 124
listing properties for Data Integration Service 137
listing properties for sequence objects 133
listing properties of Data Integration Service process 138
listing properties of data objects 127
lists sequence objects 135
purging cache for logical data objects 140
purging result set cache 142
refreshing data object cache 144
removing applications 156
renaming deployed applications 145
restoring applications from backup files 147
starting applications 151
stopping applications 153
stopping Blaze Service 154
stopping refresh of logical data object cache 111
updating applications 157
updating current value for sequence data object 149
updating parameter set entries 165
infacmd ipc
exporting objects from Model repository 187
infacmd isp
adding a domain link 196
adding licenses to domains 202
adding nodes to a domain 198
adding resources to nodes 206
adding service levels 210
adding users to groups in a domain 214
alerts, configuring SMTP settings 563
infacmd isp (continued)

alerts, listing subscribed users 393
alerts, unsubscribing from 458
assigning connection permissions to users or groups 194
assigning group permissions on objects 218
assigning Integration Service 220
assigning licenses to application service 222
assigning privileges to groups 200
assigning privileges to roles in groups 208
assigning privileges to users 212
assigning role to groups for domains or application services 223
assigning roles to users 225
assigning user permissions on objects 229
associating a repository with Web Services Hub 227
backing up content for Data Analyzer repository 231
connection permissions, listing by group 400
connections, exporting 360
connections, importing 388
connections, listing 404
connections, listing options for 406
connections, removing from domains 460
connections, updating properties 526
converting binary log files 233
CPU profile, calculating 498
creating connection 234
creating content for Data Analyzer repository 297
creating folders 298
creating grids 300
creating groups in domains 302
creating Integration Service in a domain 303
creating Metadata Manager Service in a domain 313
creating operating system profiles in a domain 317
creating Reporting Service in a domain 320
creating Repository Service in a domain 324
creating roles in a domain 329
creating SAP BW Service in a domain 331
creating users in a domain 334
creating Web Services Hub in a domain 337
Data Analyzer repository, restoring contents 496
Data Analyzer repository, upgrading contents 567
Data Analyzer repository, upgrading users and groups 568
deleting content from Data Analyzer repository 340
disabling application services 345
disabling PowerCenter resources 343
disabling services processes on a node 347
disabling user accounts 349
domains, listing linked domains 407
domains, listing properties 409
domains, removing links 463
domains, updating properties 529
editing user account properties 351
enabling applications services 355
enabling resources 354
enabling service processes on a node 357
enabling user accounts 358
export control files 875
exporting users and groups to a file 362
folders, listing 410
folders, moving 448
folders, moving objects between 450
folders, removing 465
folders, updating description 531
gateway information, updating 532
getting Integration Service process property 373
getting log events for sessions 378
getting log events for workflows 385
getting node names 371
getting recent error messages 366

getting service properties 371
getting specified log events 367
getting status of an application service 376
getting status of application service process on a node 375
getting system log directory path 381
grids, listing nodes 411
grids, removing 466
grids, updating assigned nodes 533
groups, listing 395
groups, listing privileges for 415
groups, removing 467
groups, removing privileges from 471
import control files 880
Integration Services, updating 535
LDAP authentication, setting up 502
LDAP connection, listing 418
LDAP server configuration, listing 430
LDAP server configuration, updating 504
licenses, displaying information 507
licenses, listing 420
licenses, removing 473
licenses, updating 537
listing domain objects for group 413
listing domain objects for users 443
listing folder properties 364
listing groups for a user 417
listing node role 426
listing permissions for users or groups for a connection 399
listing services assigned to a license 216
listing SMTP settings for outgoing mail server 441
listing users with permissions for a connection 402
log events, purging 454
Metadata Manager Service properties, updating 539
migrating users 446
nodes, disassociating from domains 524
nodes, listing 427, 436
nodes, listing options 423
nodes, removing 475
nodes, shutting down 508
nodes, switching from gateway to worker 512
nodes, updating 546
operating system profile, listing 429
operating system profile, removing 478
operating system profile, updating 550
passwords, resetting user passwords 495
permissions, removing from user or group connections 461
pinging objects 451
removing group permissions on objects 469
removing permissions for users and groups 500
removing user permissions on objects 489
rename connection 493
Reporting Service, updating 552
Repository Services, updating 554
resources, listing for nodes 424
resources, removing from nodes 476
roles, exporting 360
roles, importing 388
roles, listing 396
roles, listing privileges for 432
roles, removing 479
roles, removing from a group 518
roles, removing from user 520
roles, removing privileges from 481
SAP BW Services, updating 558
service levels, listing 435
service levels, removing 484
service levels, updating 560
Index
1085

service processes, updating 561
services, listing 439
services, listing privileges for 438
services, removing 483
subscribing users to notifications 192
synchronizing users and groups in security domain with LDAP users
and groups 513
updating node role 548
users and groups, exporting 360
users and groups, importing 388, 391
users, listing 397
users, listing privileges for 445
users, removing 486
users, removing from a group 487
users, removing privileges from 491
Web Services Hub, disassociating a repository 522
Web Services Hub, updating 565
infacmd isp list domain monitoring options 421
infacmd isp purge monitoring data 456
infacmd isp update domain monitoring options 540
infacmd mrs
backing up the Model repository contents to a file 573
checking in objects 575
creating a project 579, 580
creating repository content for a Model Repository Service 577
creating the Model Repository Service 582
deleting a folder 587
deleting a project 588
deleting the Model repository contents 585
listing checked out objects 592
Listing files in the backup folder 590
Listing folders in the Model Repository Service repository 593
listing locked objects 595
Listing options for the Model Repository Service 599
Listing projects in the Model Repository Service repository 597
listing service process options for the Model Repository Service 600
populating version control system 602
reassigning checked-out object 603
reassigning locked object 603
rebuilding object dependency graph 605
renaming a folder 607
restoring contents of Model repository 608
reverting checked-out objects 610
unlocking object 611
Updating options for the Model Repository Service 613
Updating service process options for the Model Repository Service
618
upgrading the contents of the Model Repository Service 620
infacmd ms
listing mappings in an application 626
running a mapping deployed to Data Integration Service 628
upgrading mapping parameter file 632
writing the mapping log 622
infacmd oie
deploying objects 634
export control files 875
exporting objects 635
exporting resources to Metadata Manager 637
import control files 880
importing objects 639
infacmd ps
creating data profiling warehouse 646
gcenceling profile model 644
getting profile model status 654
getting profile task status 652
listing profile and scorecard results 656
migrating keys 663
1086
Index
infacmd ps (continued)
migrating profile results 657
migrating scorecard results 659
purging profile and scorecard results 660
removing profiling warehouse contents 647
running a profile model 651
running profile and scorecard results 649
infacmd pwx
creating data maps 673
creating Listener Service 676
creating Logger Service 678
displaying all Logger Service messages 683
displaying counts of change records processed by Logger Service
692
displaying CPU information for Logger Service 685
displaying events for Logger Service 688
displaying information for active Listener Service tasks 703
displaying memory use for Logger Service 690
displaying monitoring statistics for the Listener Service and its tasks
695
displaying status of Writer subtask for Logger Service 698
forcing Listener Service to stop 666
starting logging cycle for Logger Service 671
stopping Listener Service 668
stopping Listener Service tasks 708
stopping Logger Service 705
switching to new set of Logger Service log files 701
updating Listener Service properties 712
updating Logger Service properties 715
upgrading nonrelational data objects 710
infacmd rms
configuring properties for Resource Manager Service 726
listing compute node attributes 721
listing properties for Resource Manager Service 723
setting compute node attributes 724
infacmd rtm
exporting reference tables 731
importing content from application files 729
importing reference tables to Model repositories 733
infacmd sch
creating a schedule 736
deleting a schedule 739
updating a schedule 752
infacmd search
configuring properties for Search Service 769
configuring properties for Search Service process 770
creating Search Service 763
listing properties for Search Service 766
listing properties of Search Service process 767
infacmd sql
column options 804
configuring properties for virtual tables 808
listing permissions for SQL data service 777
listing permissions for stored procedures 780
listing permissions for virtual tables 783
listing properties for columns in virtual tables 774
listing properties for SQL data service 776
listing properties for virtual tables 782
listing SQL data services for a Data Integration Service 779
purging virtual table cache 785
refreshing virtual table cache 787
renaming SQL data service 788
setting group and user permissions on virtual tables 797
setting permissions for SQL data service 792
setting permissions on virtual table columns 790
setting user and group permissions for stored procedures 794
SQL data service options 806
starting SQL data service 800
infacmd sql (continued)

stopping SQL data service 801
updating SQL data service options 805
virtual table options 810
infacmd sqlupdate virtual column options 803
infacmd tdm
creating Test Data Manager Service Content in a domain 817
creating Test Data Manager Service in a domain 811
disabling the Test Data Manager Service 820
enabling the Test Data Manager Service 819
infacmd wfs
aborting a workflow instance 822
canceling a workflow instance 826
dropping database tables 830
listing active workflow instances 831
listing persisted mapping outputs 833
listing workflow parameters 834
listing workflows in an application 837
recovering a workflow instance 838
starting a workflow instance 842
updating persisted mapping outputs 840
infacmd ws
listing permissions for a web service 852
listing permissions for a web service operation 849
listing properties for a web service operation 847
ListOperationOptions 847
ListOperationPermissions 849
ListWebServiceOptions 851
ListWebServicePermissions 852
ListWebServices 854
RenameWebService 855
SetOperationPermissions 857
SetWebServicePermissions 860
StartWebService 863
StopWebService 865
update properties for a web service 868
update properties for a web service operation 866
UpdateOperationOptions 866
UpdateWebServiceOptions 868
infacmd xrf
generating readable XML 872
updating export XML 872
infasetup
domains, backing up 893
domains, defining 895
domains, deleting 915
domains, restoring 920
gateway nodes, defining 906
gateway nodes, updating 923
return codes 892
run 892
worker nodes, defining 912
worker nodes, updating 929
INFATOOL_DATEFORMAT
configuring 53
Informatica utilities (installing 28
Informatica utilities (security configuration 31
InstallAbapProgram (pmrep)
description 1011
Integration Service
assigning to Metadata Manager Service 220
creating 303
Integration Service process
getting properties for 373
interactive mode for pmcmd

connecting 936
setting defaults 936
K
KillUserConnection (pmrep)
description 1013
L
labels
creating using pmrep 999
deleting 1001
LDAP authentication
setting up using infacmd isp 502
LDAP connection
LDAP server configuration
licenses
adding to domains 202
displaying using infacmd isp 507
listing services assigned to 216
unassigning using infacmd 517
links
List (infacmd ps) 656
infacmd wfs 831
ListAlertUsers (infacmd isp)
description 393
ListAllGroups (infacmd isp)
description 395
ListAllRoles (infacmd isp)
description 396
ListAllUsers (infacmd isp)
description 397
ListAllUsers (pmrep)
description 1014
ListApplicationObjects (infacmd dis) 122
ListApplicationOptions (infacmd dis) 124
ListApplications (infacmd dis) 120
ListBackupFiles (infacmd mrs) 590
ListCheckedOutObjects (infacmd mrs) 592
ListColumnOptions (infacmd sql) 774
ListComputeNodeAttributes (infacmd rms) 721
ListComputeOptions (infacmd dis) 125, 161
ListConnectionOptions (infacmd isp)
description 406
ListConnectionPermissionByUser (infacmd isp) 402
ListConnectionPermissions (infacmd isp) 399
ListConnectionPermissionsByGroup (infacmd isp)
description 400
ListConnections (infacmd isp)
description 404
ListConnections (pmrep)
description 1014
ListDataObjectOptions (infacmd dis) 127
ListDomainLinks (infacmd isp)
description 407
Index
1087
ListDomainOptions (infacmd isp)

description 409
ListFolders (infacmd isp)
description 410
ListFOlders (infacmd mrs) 593
ListGridNodes (infacmd isp)
description 411
ListGroupPermissions (infacmd isp) 413
ListGroupPrivileges (infacmd isp)
description 415
ListGroupsForUser (infacmd isp) 417
ListLicenses (infacmd isp)
description 420
ListLockedObjects (infacmd mrs) 595
infacmd wfs 833
ListMappings (infacmd ms) 626
listMonitoringOptions (infacmd isp) 421
ListNodeOptions (infacmd isp)
description 423
ListNodeResources (infacmd isp)
description 424
ListNodeRoles (infacmd isp) 426
ListNodes (infacmd isp)
description 427
ListObjectDependencies (pmrep)
description 1014
ListObjects (pmrep)
description 1017
listing folders 1021
transformation types 1019
infacmd ws 847
ListOSProfiles (infacmd isp)
description 429
ListParameterSetObjects (infacmd dis) 130
ListParameterSets (infacmd dis) 132
ListPlugins (infacmd) 58
ListProjects (infacmd mrs) 597
ListRepositoryLDAPConfiguration (infacmd isp)
description 430
ListRolePrivileges (infacmd isp)
description 432
ListSchedule (infacmd sch) 741
ListSecurityDomains (infacmd)
description 433
ListSequenceObjectProperties (infacmd dis) 133
ListSequenceObjects (infacmd dis) 135
ListServiceLevels (infacmd isp)
description 435
ListServiceNodes (infacmd isp)
description 436
ListServiceOptions (infacmd as) 67
ListServiceOptions (infacmd cms) 93
ListServiceOptions (infacmd dis) 137
ListServiceOptions (infacmd mrs) 599
ListServiceOptions (infacmd rms) 723
ListServiceOptions (infacmd sch) 743
ListServiceOptions (infacmd search) 766
ListServicePrivileges (infacmd isp)
description 438
ListServiceProcessOptions (infacmd as) 68
ListServiceProcessOptions (infacmd cms) 94
ListServiceProcessOptions (infacmd dis) 138
ListServiceProcessOptions (infacmd mrs) 600
ListServiceProcessOptions (infacmd sch) 745
ListServiceProcessOptions (infacmd search) 767
1088
Index
ListServices (infacmd isp)

description 439
ListSMTPOptions (infacmd isp) 441
ListSQLDataServiceOptions (infacmd sql) 776
ListSQLDataServicePermissions (infacmd sql) 777
ListSQLDataServices (infacmd sql) 779
ListStoredProcedurePermissions (infacmd sql) 780
ListTableOptions (infacmd sql) 782
ListTablePermissions (infacmd sql) 783
ListTablesBySess (pmrep)
description 1022
ListTaskListener (infacmd pwx) 703
ListtLDAPConnectivity (infacmd isp)
description 418
ListUserConnections (pmrep)
description 1023
ListUserPermissions (infacmd isp) 443
ListUserPrivileges (infacmd isp)
description 445
infacmd ws 851
infacmd ws 852
ListWebServices
infacmd ws 854
listWorkflowParameters
infacmd wfs 834
listWorkflows
infacmd wfs 837
local parameter files
using with pmcmd StartWorkflow 966
log events
purging using infacmd isp 454
truncating using pmrep 1043
logical data object cache
stopping refresh for 111
logical data objects
purging the cache for 140
M
mapping log
accessing with infacmd ms 622
mapping outputs
updating with infacmd 840
mappings
listing 626
mappings deployed to Data Integration Service
running 628
MassUpdate (pmrep)
description 1023
Metadata Manager Service
Metadata Manager utilities
configuring 30
installing 28
security configuration 31
connect string syntax 980
MigrateEncryptionKey (infasetup)
description 919
migrateProfileResults (infacmd ps) 657
migrateScorecards (infacmd ps) 659
migrateUsers
infacmd isp 446
mixed-version domain
running pmcmd 934
running pmrep 978
Model repository
backing up contents to a file 573
checking objects in 575
deleting contents of 585
listing checked out objects in 592
Listing files in the backup folder 590
Listing folders in the Model Repository Service repository 593
listing locked objects in 595
Listing projects in the Model Repository Service repository 597
Lists options for the Model Repository Service 599
reassigning checked-out object in 603
reassigning locked object in 603
rebuilding object dependency graph 605
restoring contents of 608
reverting checked-out objects in 610
unlicking object in 611
Updates options for the Model Repository Service 613
Updates service process options for the Model Repository Service
618
upgrading the contents of the Model Repository Service 620
Model repository objects
exporting 187
creating 582
creating repository content for 577
listing 600
ModifyFolder (pmrep)
description 1029
MoveFolder (infacmd isp)
description 448
MoveObject (infacmd isp)
description 450
N
nodes
adding resources to 206
defining gateway using infasetup 906
defining worker using infasetup 912
disassociating from domains infacmd isp 524
getting name of 371
listing all in a domain 427
listing options using infacmd isp 423
listing role 426
pinging 451
removing from domains 475
switching from gateway to worker infacmd isp 512
switching from worker to gateway infacmd 510
updating 546
updating gateway using infasetup 923
updating role 548
updating worker using infasetup 929
Notify (pmrep)
description 1030
O
object import control file
description 1061
ObjectExport (pmrep)
description 1031
ObjectImport (pmrep)
description 1033
objects
assigning user permissions on 229
checking in 988
deleting 1001
deploying to an archive file 634
exporting 1031
exporting to object export file 635
importing 1033
importing from object export file 639
removing user permissions on 489
operating system profile
operating system profiles
Oracle
connect string syntax 980
connection options for 281
OVERRIDEFOLDER
sample control file 1078
P
parameter files
using with pmcmd StartTask 963
using with pmcmd StartWorkflow 966
passwords
encrypting 54
resetting user passwords using infacmd isp 495
PauseAll (infacmd sch) 746
PauseSchedule (infacmd sch) 748
permissions
assigning using pmrep 984
removing from user or group connections using infacmd isp 461
persistent input file
creating with pmrep 1060
Ping (infacmd isp)
description 451
PingService (pmcmd)
description 956
plug-ins
XML templates 1038
pmcmd
command line mode 934
folders, designating for executing commands 960
folders, designating no default folder 972
Integration Service, connecting to 942
Integration Service, disconnecting from 944
Integration Service, pinging 956
interactive mode 936
interactive mode, exiting from 944
nowait mode, setting 960
parameter files 963, 966
PowerCenter Integration Service, getting properties 947
return codes 935
running in a mixed-version domain 934
script files 937
service settings, getting 961
session statistics, getting 948
sessions, getting details about 944
tasks, aborting 939
tasks, completing before returning the prompt 973
tasks, getting details about 945, 950
tasks, starting 961
Index
1089
pmcmd (continued)
tasks, stopping 967
version, displaying 973
wait mode, setting 960
workflows, aborting 941
workflows, determining if running 975
workflows, getting details about 945, 952
workflows, recovering 956
workflows, removing from a schedule 971
workflows, scheduling 958
workflows, starting 964
workflows, stopping 969
pmpasswd
encrypting passwords 54
syntax 54
pmrep
checked-out objects, listing 1007
checkouts, undoing 1044
command line mode 979
connection details, listing 1008
connection information, showing 1042
connection name, changing 1042
connections, creating 991
connections, deleting 1000
connections, listing 1014
connections, updating 1048
deployment control file parameters 1074
deployment groups, adding objects to 981
deployment groups, clearing objects from 989
deployment groups, creating 997
deployment groups, deleting 1000
deployment groups, deploying 1002
deployment, rolling back 1040
email addresses, updating 1049
folder properties, modifying 1029
folders, creating 997
folders, deleting 1001
folders, deploying 1004
folders, listing 1021
folders, modifying properties 1029
generating ABAP program 1009
groups, creating 999
help 1011
installing ABAP program 1011
interactive mode 979
interactive mode, exiting 1007
interactive mode, exiting from 1007
labels, applying 982
labels, creating 999
labels, deleting 1001
logs, deleting 1043
notification messages, sending 1030
object dependencies, listing 1014
object import control parameters 1063
object versions, purging 1033
objects, changing ownership 987
objects, checking in 988
objects, deleting 1001
objects, exporting 1031
objects, importing 1033
objects, listing 1017
objects, validating 1055
overview 978
permission, assigning 984
persistent input files, creating 1060
plug-ins, registering 1037
plug-ins, unregistering 1046
privileges, removing 1040
1090
Index
pmrep (continued)
queries, executing 1005
repositories, backing up 986
repositories, connecting to 989
repositories, creating 991
repositories, deleting 999
repositories, registering 1036
repositories, restoring 1039
repositories, unregistering 1045
repository connection file, specifying 52
repository statistics, updating 1052
resources, cleaning up 988
running in a mixed-version domain 978
script files 980
scripts, running 1041
sequence values, updating 1050
table owner names, updating 1051
tables, listing by session 1022
target table name prefixes, updating 1052
uninstall ABAP program 1054
user connections, listing 1023
user connections, terminating 1013
user properties, editing 1005
users, listing 1014
version information, displaying 1057
PopulateVCS (infacmd mrs) 602
post-session email
updating addresses with pmrep 1049
PowerCenter resources
disabling 343
enabling 354
PowerCenter utilities
configuring 30
installing 28
security configuration 31
PowerExchange Listener Service
creating 676
displaying monitoring statistics for the Listener Service and its tasks
695
forcing to stop 666
listing tasks 703
stopping 668
stopping tasks 708
updating properties 712
PowerExchange Logger Service
creating 678
displaying all messages 683
displaying counts of change records processed 692
displaying CPU information 685
displaying events 688
displaying memory use 690
displaying status of Writer subtask 698
shutting down 705
starting logging cycle 671
switching to new set of log files 701
updating properties 715
PrintSPNAndKeytabNames (infacmd isp) 452
privileges
assigning to groups in a domain 200
assigning to roles 208
listing for a group using infacmd isp 415
listing for a role using infacmd isp 432
listing for a user 445
listing for services using infacmd isp 438
removing 1040
removing from a group using infacmd isp 471
removing from a role using infacmd isp 481
removing from a user using infacmd isp 491
profile model
canceling 644
executing 651
getting status 654
profile tasks
getting status 652, 663
profiles
executing 649
listing results for 656
purging results for 660
profiling warehouse contents
removing 647
Purge (infacmd cms) 96
Purge (infacmd ps) 660
PurgeDataObjectCache (infacmd dis) 140
PurgeLog (infacmd isp)
description 454
PurgeMonitoringOptions (infacmd isp) 456
PurgeResultSetCache (infacmd dis) 142
PurgeTableCache (infacmd sql) 785
PurgeVersion (pmrep)
description 1033
Q
queries
executing 1005
R
reassignCheckedOutObject (infacmd mrs) 603
rebuildDependencyGraph (infacmd mrs) 605
recoverWorkflow
infacmd wfs 838
RecoverWorkflow (pmcmd)
description 956
reference tables
exporting 731
importing to Model repositories 733
RefreshDataObjectCache (infacmd dis) 144
RefreshTableCache (infacmd sql) 787
Register (pmrep)
description 1036
registering
plug-in using pmrep 1037
security module using pmrep 1038
RegisterPlugin (pmrep)
description 1037
RemoveAlertUser (infacmd isp)
description 458
RemoveConnection (infacmd isp)
description 460
RemoveConnectionPermissions (infacmd isp)
description 461
RemoveDomainLink (infacmd isp)
description 463
RemoveFolder (infacmd isp)
description 465
RemoveGrid (infacmd isp)
description 466
RemoveGroup (infacmd isp)
description 467
RemoveGroupPermission (infacmd isp) 469
RemoveGroupPrivilege (infacmd isp)
description 471
RemoveLicense (infacmd isp)

description 473
RemoveNode (infacmd isp)
description 475
RemoveNodeResource (infacmd isp)
description 476
RemoveOSProfile (infacmd isp)
description 478
RemoveRole (infacmd isp)
description 479
RemoveRolePrivilege (infacmd isp)
description 481
RemoveService (infacmd cms) 97
RemoveService (infacmd isp)
description 483
RemoveServiceLevel (infacmd isp)
description 484
RemoveUser (infacmd isp)
description 486
RemoveUserFromGroup (infacmd isp)
description 487
RemoveUserPermission (infacmd isp) 489
RemoveUserPrivilege (infacmd isp)
description 491
RenameApplication (infacmd dis) 145
RenameConnection (infacmd isp) 493
RenameFolder (infacmd mrs) 607
RenameSQLDataService (infacmd sql) 788
RenameWebService
infacmd ws 855
Reporting Service
repositories
backing up using pmrep 986
connecting to using pmrep 989
creating relational 991
deleting details from 1043
registering 1036
unregistering 1045
Repository Service
ResetPassword (infacmd isp)
description 495
Resource Manager Service
Resource Manager Service options
infacmd syntax 728
resources
exporting to object export file 637
viewing using infacmd isp 424
Restore (pmrep)
description 1039
RestoreApplication (infacmd dis) 147
RestoreContents (infacmd mrs) 608
RestoreDARepositoryContents (infacmd isp)
description 496
RestoreDomain (infasetup)
description 920
restoring
repositories using pmrep Restore 1039
ResumeAll (infacmd sch) 749
ResumeSchedule (infacmd sch) 751
resyncData (infacmd cms) 99
Index
1091
return codes
infacmd 59
infasetup 892
pmcmd 935
RevertObject (infacmd mrs) 610
RmPrivilege (pmrep)
description 1040
roles
assigning to a user using infacmd isp 225
importing using infacmd isp 388
removing from a user using infacmd isp 520
RollbackDeployment (pmrep)
description 1040
Run (pmrep)
description 1041
RunCPUProfile (infacmd isp)
description 498
RunMapping
infacmd ms 628
running a mapping
with a run-time parameter set 628
S
SAP BW Service
Scheduler Service options
infacmd syntax 757, 760
ScheduleWorkflow (pmcmd)
description 958
schema files
scorecards
executing 649
listing results for 656
migrating 659
purging results for 660
script files
running 1041
using for pmrep commands 980
Search Service
creating 763
Search Service process
security domains
listing using infacmd 433
SEQ
service levels
adding 210
service processes
disabling on a node 347
enabling on nodes 357
services
1092
Index
services (continued)
pinging 451
sessions
getting log events for 378
SetColumnPermissions (infacmd sql) 790
SetComputeNodeAttributes (infacmd rms) 724
SetConnectionPermissions (infacmd isp) 500
SetFolder (pmcmd)
description 960
SetLDAPConnectivity (infacmd isp)
description 502
infacmd wfs 840
SetNoWait (pmcmd)
description 960
infacmd ws 857
SetRepositoryLDAPConfiguration (infacmd isp)
description 504
SetSequenceState (infacmd dis) 149
SetSQLDataServicePermissions (infacmd sql) 792
SetStoredProcedurePermissions (infacmd sql) 794
SetTablePermissions (infacmd sql) 797
SetWait (pmcmd)
description 960
infacmd ws 860
ShowConnectionInfo (pmrep)
description 1042
ShowLicense (infacmd isp)
description 507
ShowSettings (pmcmd)
description 961
ShutDownLogger (infacmd pwx) 705
ShutdownNode (infacmd isp)
description 508
SQL data service
listing for a Data Integration Service 779
listing permissions for 777
renaming 788
setting permissions for 792
starting 800
stopping 801
StartApplication (infacmd dis) 151
StartSQLDataService (infacmd sql) 800
StartTask (pmcmd)
description 961
using a parameter file 963
StartWebService
infacmd ws 863
startWorkflow
infacmd wfs 842
StartWorkflow (pmcmd)
description 964
using a parameter file 966
statistics
updating repository 1052
StopApplication (infacmd dis) 153
stopBlazeService (infacmd dis) 154
StopSQLDataService (infacmd sql) 801
StopTask (pmcmd)
description 967
StopTaskListener (infacmd pwx) 708
StopWebService
infacmd ws 865
StopWorkflow (pmcmd)
description 969
stored procedures
SwitchConnection (pmrep)
description 1042
SwitchToGatewayNode (infacmd)
description 510
SwitchToKerberosMode (infasetup)
description 922
SwitchToWorkerNode (infacmd isp)
description 512
synchronizeProfile (infacmd ps) 663
SyncSecurityDomains (infacmd isp) 513
syntax
command line programs 34
Data Integration Service infacmd options 169
Resource Manager Service infacmd options 728
Scheduler Service infacmd options 757, 760
T
table owner name
updating with pmrep 1051
TDM service
disabling 820
Teradata Parallel Transporter connection
infacmd 289
Test Data Manager Service
creating in a domain 811, 817
TruncateLog (pmrep)
description 1043
U
UnassignISMMService (infacmd)
description 515
UnassignLicense (infacmd)
description 517
UnassignRoleFromGroup (infacmd isp)
description 518
UnassignRoleFromUser (infacmd isp)
description 520
UnassignRSWSHubService (infacmd isp)
description 522
UnassociateDomainNode (infacmd isp)
description 524
UndeployApplication (infacmd dis) 156
UndoCheckout (pmrep)
description 1044
UninstallAbapProgram (pmrep)
description 1054
unlocking
locked object 611
unlockObject (infacmd mrs) 611
Unregister (pmrep)
description 1045
UnregisterPlugin (pmrep)
description 1046
UnscheduleWorkflow (pmcmd)
description 971
UnsetFolder (pmcmd)
description 972
UpdateApplication (infacmd dis) 157
UpdateApplicationOptions (infacmd dis) 159
UpdateColumnOptions (infacmd sql) 803

UpdateConnection (infacmd isp)
description 526
UpdateConnection (pmrep)
description 1048
UpdateDataObjectsOptions (infacmd dis) 163
UpdateDomainOptions (infacmd isp)
description 529
UpdateEmailAddr (pmrep)
description 1049
updateExportXML
infacmd xrf 872
UpdateFolder (infacmd isp)
description 531
UpdateGatewayInfo (infacmd isp)
description 532
UpdateGatewayInfo (infacmd) 60
UpdateGatewayNode (infasetup)
description 923
UpdateGrid (infacmd isp)
description 533
UpdateIntegrationService (infacmd isp)
description 535
UpdateKerberosAdminUser (infasetup)
description 928
UpdateKerberosConfig (infasetup)
description 928
UpdateLicense (infacmd isp)
description 537
UpdateListenerService (infacmd pwx) 712
UpdateLoggerService (infacmd pwx) 715
UpdateMMService (infacmd isp)
description 539
UpdateMonitoringOptions (infacmd isp) 540
UpdateNamespace (infacmd isp) 543
UpdateNodeOptions (infacmd isp)
description 546
UpdateNodeRole (infacmd isp) 548
infacmd ws 866
UpdateOSProfile (infacmd isp)
description 550
UpdateParameterSetEntries (infacmd dis) 165
UpdateReportingService (infacmd isp)
description 552
UpdateRepositoryService (infacmd isp)
description 554
UpdateSAPBWService (infacmd isp)
description 558
UpdateSchedule (infacmd sch) 752
UpdateSeqGenVals (pmrep)
description 1050
UpdateServiceLevel (infacmd isp)
description 560
UpdateServiceOptions (infacmd as) 70
UpdateServiceOptions (infacmd cms) 101
UpdateServiceOptions (infacmd dis) 167
UpdateServiceOptions (infacmd mrs) 613
UpdateServiceOptions (infacmd rms) 726
UpdateServiceOptions (infacmd sch) 755
UpdateServiceOptions (infacmd search) 769
UpdateServiceProcess (infacmd isp)
description 561
UpdateServiceProcessOptions (infacmd as) 72
UpdateServiceProcessOptions (infacmd cms) 103
UpdateServiceProcessOptions (infacmd dis) 177
UpdateServiceProcessOptions (infacmd mrs) 618
UpdateServiceProcessOptions (infacmd sch) 758
Index
1093
UpdateServiceProcessOptions (infacmd search) 770

UpdateSMTPOptions (infacmd isp)
description 563
UpdateSQLDataServiceOptions (infacmd sql) 805
UpdateSrcPrefix (pmrep)
description 1051
updating non-reusable sessions 1051
UpdateStatistics (pmrep)
description 1052
UpdateTableOptions (infacmd sql) 808
UpdateTargPrefix (pmrep)
description 1052
updating non-reusable sessions 1052
infacmd ws 868
UpdateWorkerNode (infasetup)
description 929
UpdateWSHubService (infacmd isp)
description 565
Upgrade (infacmd cms) 105
Upgrade (infacmd sch) 761
UpgradeContents (infacmd mrs) 620
UpgradeDARepositoryContents (infacmd isp)
description 567
UpgradeDARepositoryUsers (infacmd isp)
description 568
UpgradeModels (infacmd pwx) 710
upgradeRepository (infacmd bg) 85
user accounts
disabling in a domain 349
editing properties for 351
enabling 358
user permissions
listing for domain objects 443
users
adding to group in a domain 214
exporting 362
importing using infacmd isp 388, 391
listing groups for a user 417
listing types of permissions for 402
migrating with infacmd 446
users and groups
removing permissions for 500
users and groups in security domain
synchronizing with LDAP users and groups 513
V
Validate (pmrep)
description 1055
ValidateandRegisterFeature (infasetup)
description 932
validateFeature (infacmd advanced) 570
validating objects
with pmrep 1055
Version (infacmd)
description 571
Version (pmcmd)
description 973
Version (pmrep)
description 1057
1094
Index
virtual columns
updating options 803
virtual schemas
virtual table cache
purging 785
refreshing 787
virtual table column
virtual tables
VSAM
W
wait mode
configuring using pmcmd 937
WaitTask (pmcmd)
description 973
WaitWorkflow (pmcmd)
description 975
Web Content-Kapow Katalyst
connection 295
web service
listing with infacmd 854
renaming with infacmd 855
setting permissions with infacmd 860
starting with infacmd 863
stopping with infacmd 865
web service operation
setting permissions with infacmd 857
web service options
infacmd syntax 869
Web Services Hub
associating a repository using infacmd isp 227
disassociating a repository using infacmd isp 522
Workflow Service
dropping database tables 830
workflows
getting log events for 385
listing 837
recovering using pmcmd syntax 956
starting from command line 964
stopping from command line 969
workflows deployed to Data Integration Service
aborting 822
canceling 826
recovering 838
starting 842
X
XML file
plug-in templates 1038
Index
1095

In 100 CommandReference en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

In 100 CommandReference en

Uploaded by

Copyright:

Available Formats

Informatica (Version 10.

Informatica Command Reference

Chapter 1: Command Line Programs and Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 2: Installing and Configuring Command Line Utilities. . . . . . . . . . . . . . . . . 28

Chapter 3: Using the Command Line Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 4: Environment Variables for Command Line Programs. . . . . . . . . . . . . . . 38

Configuring ICMD_JAVA_OPTS on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Configuring INFA_NODE_TRUSTSTORE_PASSWORD on UNIX. . . . . . . . . . . . . . . . . . . . 51

Chapter 5: Using infacmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Chapter 6: infacmd as Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 7: infacmd aud Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Chapter 8: Infacmd bg Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Chapter 9: infacmd cms Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Chapter 10: infacmd dis Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Chapter 11: Infacmd es Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Chapter 12: infacmd ipc Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Chapter 13: infacmd isp Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Reporting Source Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Chapter 14: infacmd mrs Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572

Chapter 15: infacmd ms Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622

Chapter 16: infacmd oie Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634

Chapter 17: infacmd ps Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644

Chapter 18: infacmd pwx Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665

Chapter 19: infacmd rms Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721

Chapter 20: infacmd rtm Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729

Chapter 21: infacmd sch Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736

Chapter 22: infacmd search Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . 763

Chapter 23: infacmd sql Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773

Chapter 24: infacmd tdm Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811

Chapter 25: infacmd wfs Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822

listWorkflowParams Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836

Chapter 26: infacmd ws Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847

Chapter 27: infacmd xrf Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872

Chapter 28: infacmd Control Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874

Chapter 29: infasetup Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891

Running Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892

Chapter 30: pmcmd Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933

Chapter 31: pmrep Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977

Chapter 32: Working with pmrep Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059

Deployment Control File Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074

Access all of your Informatica resources in one place.

Review your support cases.

Informatica Product Availability Matrixes

Informatica Web Site

Informatica How-To Library

Informatica Knowledge Base

Informatica Support YouTube Channel

Informatica Global Customer Support

Command Line Programs and

Command Line Programs and Utilities Overview, 26

Command Line Programs and Utilities Overview

Administer domains and nodes.

The following table describes the PowerCenter utilities:

Encrypt passwords to use with pmcmd and pmrep environment variables.

The following table describes the Metadata Manager utilities:

Command Line Programs and Utilities Overview

Installing and Configuring

Installing and Configuring Command Line Utilities Overview, 28

Installing the Command Line Utilities, 28

Configuring the Command Line Utilities, 29

Security Configuration for Informatica Utilities , 31

Installing and Configuring Command Line Utilities

Installing the Command Line Utilities