Informatica Cloud (Spring 2015)

Administrator Guide

Informatica Cloud Administrator Guide

Spring 2015
April 2015
Copyright (c) 1993-2015 Informatica Corporation. All rights reserved.
This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use
and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in
any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S.
and/or international Patents and other Patents Pending.
Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as
provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14
(ALT III), as applicable.
The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us
in writing.
Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange,
PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica
On Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and
Informatica Master Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world.
All other company and product names may be trade names or trademarks of their respective owners.
Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights
reserved. Copyright Sun Microsystems. All rights reserved. Copyright RSA Security Inc. All Rights Reserved. Copyright Ordinal Technology Corp. All rights
reserved.Copyright Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright Meta
Integration Technology, Inc. All rights reserved. Copyright Intalio. All rights reserved. Copyright Oracle. All rights reserved. Copyright Adobe Systems
Incorporated. All rights reserved. Copyright DataArt, Inc. All rights reserved. Copyright ComponentSource. All rights reserved. Copyright Microsoft Corporation. All
rights reserved. Copyright Rogue Wave Software, Inc. All rights reserved. Copyright Teradata Corporation. All rights reserved. Copyright Yahoo! Inc. All rights
reserved. Copyright Glyph & Cog, LLC. All rights reserved. Copyright Thinkmap, Inc. All rights reserved. Copyright Clearpace Software Limited. All rights
reserved. Copyright Information Builders, Inc. All rights reserved. Copyright OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved.
Copyright Cleo Communications, Inc. All rights reserved. Copyright International Organization for Standardization 1986. All rights reserved. Copyright 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.
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; and http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html.
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.
This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775;
6,640,226; 6,789,096; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110; 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422;
7,676,516; 7,720,842; 7,721,270; 7,774,791; 8,065,266; 8,150,803; 8,166,048; 8,166,071; 8,200,622; 8,224,873; 8,271,477; 8,327,419; 8,386,435; 8,392,460;
8,453,159; 8,458,230; 8,707,336; 8,886,617 and RE44,478, International Patents and other Patents Pending.
DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the
implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is
error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and
documentation is subject to change at any time without notice.
NOTICES
This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software
Corporation ("DataDirect") which are subject to the following terms and conditions:
1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT
INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT
LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.
Part Number: IC-AG-22000-0002

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Informatica Cloud Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Informatica Cloud Communities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Informatica Cloud Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Informatica Cloud Connector Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Informatica Cloud Trust Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 1: Introduction to Informatica Cloud Administration. . . . . . . . . . . . . . . . . . . . 9

Informatica Cloud Administration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica Cloud Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica Cloud User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Informatica Cloud Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Informatica Cloud Sidebar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Logging in to Informatica Cloud. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Informatica Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Getting Started with Informatica Cloud Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2: Organization Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Organization Administration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Organization Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Creating an Organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Organization Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Organization General Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Organization Email Notification Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Organization Authentication Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Connection Properties Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Organization Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Creating a Sub-organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Linking Organizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Changing Between Organizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
License Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
License Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
License Categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Sub-organization Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Monitoring Application Job Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
License Expiration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Table of Contents

Chapter 3: Secure Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Informatica Cloud Secure Agent Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Runtime Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Secure Agent Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Secure Agent IP Address Ranges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Secure Agent Installation on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Downloading the Secure Agent Installation Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Installing the Secure Agent on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Configuring the Proxy Settings on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Configuring a Login for a Windows Secure Agent Service. . . . . . . . . . . . . . . . . . . . . . . . . 25
Uninstalling the Secure Agent on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Secure Agent Installation on Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Downloading the Secure Agent Installation Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Installing and Registering the Secure Agent on Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Configuring the Proxy Settings on Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Uninstalling the Secure Agent on Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Secure Agent Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Configuring Secure Agent Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Viewing Secure Agent Status and Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
View the Secure Agent Status on Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
View the Secure Agent Audit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Runtime Environment Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Configuring Secure Agents in Runtime Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Rules and Guidelines for the Secure Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Stopping and Restarting the Secure Agent on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Starting and Stopping the Secure Agent on Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Deleting a Secure Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 4: User and User Group Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

User and User Group Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Admin Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Designer Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Service Consumer Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
User Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Configuring a User Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Viewing User Group Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Deleting a User Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Object-Level Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Configuring Object-Level Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Rules and Guidelines for Roles, User Groups, and Permissions. . . . . . . . . . . . . . . . . . . . . . . . 41

Table of Contents

Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
User Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Configuring a User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Viewing User Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Deleting a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Audit Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
User Configuration Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 5: Connector Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Connector Administration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Installing an Informatica Cloud Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Microsoft Dynamics CRM Connector Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Step 1. Configuring Java Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Step 2. Resolving Hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Step 3. Editing the Kerberos Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Step 4. Editing the Kerberos Login Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Step 5. Downloading Java Security Policy Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
NetSuite Connector Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Step 1. Creating a Configuration File to Map NetSuite Fields. . . . . . . . . . . . . . . . . . . . . . . 50
Step 2. Configuring the NetSuiteCustomFields.ini File. . . . . . . . . . . . . . . . . . . . . . . . . . . 51
SAP IDocs and RFCs/BAPI Connector Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Step 1. Downloading and Installing the Microsoft Visual C++ Redistributable. . . . . . . . . . . . 51
Step 2. Downloading and Configuring SAP Libraries for IDoc and BAPI/RFC. . . . . . . . . . . . 52
Step 3. Configuring saprfc.ini for IDoc and BAPI/RFC. . . . . . . . . . . . . . . . . . . . . . . . . . . 53
SAP Table Connector Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Step 1. Downloading and Installing the Microsoft Visual C++ Redistributable. . . . . . . . . . . . 55
Step 2. Downloading and Configuring the Libraries for Table Read and Write. . . . . . . . . . . . 56
Step 3. Configuring saprfc.ini for SAP Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Step 4. Configuring SAP User Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Step 5. Installing SAP Table Connection Transport Files. . . . . . . . . . . . . . . . . . . . . . . . . 60
Siebel Connector Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Configuring an ODBC Connection for Siebel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 6: Object Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Object Migration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Migration Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Migrating an Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Post-migration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Migration Rules and Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Table of Contents

Preface
Welcome to Informatica Cloud, Informaticas hosted applications. Informatica Cloud uses functionality from
PowerCenter and Informatica Data Quality to provide easy-to-use, web-based applications.
The Informatica Cloud Administrator Guide explains how administrators can set up and maintain Informatica
Cloud organizations.

Informatica Resources
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 http://mysupport.informatica.com.

Informatica Cloud Web Site

You can access the Informatica Cloud web site at http://www.informatica.com/cloud. This site contains
information about Informatica Cloud editions and applications.

Informatica Cloud Communities

Use the Informatica Cloud Community to discuss and resolve technical issues in Informatica Cloud. You can
also find technical tips, documentation updates, and answers to frequently asked questions.
Access the Informatica Cloud Community at:
http://www.informaticacloud.com/community
Developers can learn more and share tips at the Cloud Developer community:
http://www.informaticacloud.com/devcomm

Informatica Cloud Marketplace

Visit the Informatica Marketplace to try and buy Informatica Cloud Connectors, Informatica Cloud integration
templates, and Data Quality mapplets:

https://community.informatica.com/community/marketplace/informatica_cloud_mall

Informatica Cloud Connector Documentation

You can access documentation for Informatica Cloud Connectors at the Informatica Cloud Community:
https://community.informatica.com/cloud/index.htm
You can also download individual connector guides: https://community.informatica.com/docs/DOC-2687.

Informatica Knowledge Base

As an Informatica customer, you can access the Informatica Knowledge Base at
http://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 Cloud Trust Site

You can access the Informatica Cloud trust site at http://trust.informaticacloud.com. This site provides real
time information about Informatica Cloud system availability, current and historical data about system
performance, and details about Informatica Cloud security policies.

Informatica Global Customer Support

You can contact a Customer Support Center by telephone or online.
For online support, click Submit Support Request in the Informatica Cloud application. You can also use
Online Support to log a case. Online Support requires a login. You can request a login at
https://mysupport.informatica.com.
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

CHAPTER 1

Introduction to Informatica Cloud

Administration
This chapter includes the following topics:

Informatica Cloud Administration Overview, 9

Informatica Cloud Components, 9

Informatica Cloud User Interface, 10

Logging in to Informatica Cloud, 11

Informatica Administrator, 11

Getting Started with Informatica Cloud Administration, 11

Informatica Cloud Administration Overview

Informatica Cloud administrators are responsible for the following activities:

Informatica Cloud organization and organization hierarchy setup and management

Informatica Cloud organization license management

Runtime environment management

User and user group setup and management

Connector configuration and management

Object migration

By default, the user who creates an Informatica Cloud organization is the organization administrator. The
organization administrator is the Informatica Cloud user responsible for managing the organization. If an
organization has multiple administrators, the organization administrator is considered the lead administrator.
By default, all users assigned the Admin role, which includes the organization administrator, have full access
to the entire organization.

Informatica Cloud Components

Informatica Cloud includes the following components:

Informatica Cloud
A browser-based application that runs at the Informatica Cloud hosting facility. It provides the ability to
configure connections, create users, and create, run, schedule, and monitor tasks.
Informatica Cloud hosting facility
A facility where the Informatica Cloud application runs. The Informatica Cloud hosting facility stores all
task and organization information.
Informatica Cloud applications
Applications used to perform tasks such as data synchronization, contact validation, and data replication.
Informatica Cloud Secure Agent
A component of Informatica Cloud installed on a local machine that runs all tasks and provides firewall
access between the hosting facility and your organization. When the Secure Agent runs a task, it
connects to the Informatica Cloud hosting facility to access task information, connects directly and
securely to sources and targets, transfers data between sources and targets, and performs any
additional task requirements.

Informatica Cloud User Interface

The Informatica Cloud user interface includes menus at the top of the page and a sidebar. Use the menus to
work with Informatica Cloud and the sidebar to access information about Informatica Cloud.

Informatica Cloud Menus

Informatica Cloud provides several menus:

10

Home. Provides a training video and tips to use Informatica Cloud.

Monitor. View details about tasks that are running or complete. Access the Service and Process Monitor.

Apps. Access Informatica Cloud applications and task wizards.

Design. Design task flows, bundles, integration templates, and mappings. Access the Service and
Process Designer.

Chapter 1: Introduction to Informatica Cloud Administration

Configure. Configure Informatica Cloud components, such as Secure Agents, connections, and saved
queries. And download bundles and Informatica Cloud Connectors.

Administer. Perform tasks to administer the organization, such as organization properties configuration
and object migration.

Click the Help icon on the sidebar to access help about the page that is currently in view.
When you log in to Informatica Cloud, the Informatica Cloud Messages page might appear to tell you about
upcoming maintenance.

Informatica Cloud Sidebar

The Informatica Cloud sidebar provides instant access to the online help, the Informatica Cloud community,
and online videos.
Users with a paid license or within the 30-day trial period can submit a support request directly to Informatica
Global Customer Support.
During available hours, users with a paid license can also get real time help from a Informatica Global
Customer Support specialist. To open a chat window, click the Live Chat icon on the Informatica Cloud
sidebar.

Logging in to Informatica Cloud

Before you log in, verify that the browser meets the minimum system requirements.
1.

On the Informatica Cloud Login page, enter your user name and password. Your user name is typically
your email address.

2.

When you log in to Informatica Cloud for the first time, you might need to configure a security question.
Informatica Cloud uses the security question to verify your identity if you forget your password.

Informatica Administrator
If you have access to the Informatica Administrator tool, you can use it to view Informatica Cloud organization
properties. You cannot make any changes to the properties using the Administrator tool.
For more information about the Administrator tool, see the Informatica Administrator Guide.

Getting Started with Informatica Cloud Administration

Before your company can use Informatica Cloud, you must set up your organization.
Perform the following tasks to prepare your company's Informatica Cloud organization:

Create the organization and organization hierarchy and configure organization properties.

Ensure the organization and sub-organizations have the appropriate licenses.

Logging in to Informatica Cloud

11

12

Install and configure Secure Agents and runtime environments.

Set up users and user groups.

Download and configure connectors.

Chapter 1: Introduction to Informatica Cloud Administration

CHAPTER 2

Organization Administration
This chapter includes the following topics:

Organization Administration Overview, 13

Organization Creation, 13

Organization Properties, 14

Organization Hierarchies, 16

License Management, 17

Organization Administration Overview

An Informatica Cloud organization is a secure area within the Informatica Cloud repository where you store
information and objects.
Informatica Cloud administrators maintain Informatica Cloud organizations and sub-organizations.
Administration of Informatica Cloud organizations includes the following tasks:

Creating the organization

Setting organization properties

Creating and maintaining the organization hierarchy

Maintaining organization licenses

To accomplish these tasks, log in to Informatica Cloud as an administrator.

You can also view organization properties with the Informatica Administrator tool which you can access within
the Informatica domain. For more information about the Informatica Administrator tool, see the Informatica
Administrator Guide.

Organization Creation
You can create an organization on the Informatica Cloud website.
When you sign up for an organization with Informatica Cloud, Informatica Cloud creates an organization
administrator account with your email address as the user name and generates a temporary password. As an
organization administrator, you are assigned the Admin role, which has full access to the organization.

13

Informatica Cloud sends your user name, password, and Informatica Cloud URL to your email address. When
you log in to Informatica Cloud for the first time, click Login with Temporary Password in the email, or enter
the user name and password provided in the email.

Creating an Organization
You can sign up for a trial version of Informatica Cloud on the Informatica Cloud website, which will create an
organization. After you receive the trial version, you can click Buy Now to subscribe to an Informatica Cloud
edition.
1.

Go to http://www.informatica.com and click the link to start a trial version of Informatica Cloud, and then
enter the information on the form.
Informatica Cloud sends you a temporary password and a link to Informatica Cloud.

2.

To sign up for the full version, log in to Informatica Cloud and then in the Informatica Cloud sidebar, click
Buy Now.

Organization Properties
Configure properties for your organization and sub-organizations on the My Organization page.
You can configure the following properties:

General organization properties

Email notification properties

Authentication properties

Connection properties storage

To access the My Organization page, select Administer > Organization.

Organization General Properties

You can set general properties for your organization such as the job execution profile and schedule offset.
The job execution profile is the Informatica Cloud user account used to run contact validation tasks. For new
organizations, by default, Informatica Cloud uses the organization administrator user account that created the
organization as the job execution profile. You can change the job execution profile to any user account in the
organization.
The schedule offset is a small amount of time added to schedule start times to help prevent server overload
at standard schedule start times. An organization has a single schedule offset that is applied to all schedules.
The schedule offset does not affect the start time of manually started tasks or task flows.
Though not displayed, the schedule offset for your organization is added to the time range configured for all
schedules. This ensures that scheduled tasks run as often as expected. For example, you configure a
schedule to run every hour from 8:00 a.m. to 12:00 p.m and the schedule offset for your organization is 15
seconds. Your schedule runs at 8:00:15, 9:00:15, 10:00:15, 11:00:15, and 12:00:15.

14

Chapter 2: Organization Administration

Organization Email Notification Properties

You can configure Informatica Cloud at an organizational level to send email notification when tasks
complete successfully, complete with errors, or fail.
Email notification properties can also be set at the task level. When a user specifies email notification in a
task or task flow, Informatica Cloud sends email to the addresses in the task or task flow instead of the
addresses configured for the organization.

Organization Authentication Properties

Set authentication properties for your organization and sub-organizations.
You can specify the following authentication options:

Password restrictions, such as the minimum number of characters and the minimum character mix
allowed in a valid password, password reuse, and password expiration.

Whether to enable or disable two-factored authentication.

Password Restrictions
Configure the following password restrictions for all users in the organization:
Password length
Specify a number between 4 and 12 characters for the minimum length allowed for a valid password.
Password expiration
Specify whether passwords expire. If you specify that passwords expire, then specify the number of days
until the password expires.
Minimum number of characters
Specify the minimum number of characters allowed in a valid password.
Minimum character mix
Specify the number of character sets required in valid passwords. Passwords can contain a mix of the
following character sets:

Lowercase alphabetic characters

Uppercase alphabetic characters

Numeric characters

Special characters

For example, if you set the Minimum Character Mix Option to 1, then passwords must contain at least
one of the character sets. If you set the Minimum Character Mix Option to 2, then passwords must
contain at least two of the character sets.

Two-Factor Authentication
Two-factor authentication uses trusted IP address ranges in addition to account passwords to enhance
Informatica Cloud security. Configure the Two-Factor Authentication organization property when you want to
increase security for your organization.
When you configure two-factor authentication, you enter one or more trusted IP address ranges. A user with
a valid login must have an IP address within the trusted IP address ranges to connect to your organization.
Informatica Cloud supports IP address formats in IP version 4 (IPv4) and version 6 (IPv6).

Organization Properties

15

Note: If you enter an invalid IP address range, users cannot access your organization. Contact your network
administrator for valid IP address ranges.

Connection Properties Storage

You can configure where to store connection properties for the organization.
You can store connection properties with Informatica Cloud or with a local Secure Agent. You might store
connection properties with a local Secure Agent if you need the connection properties to reside within your
firewall. To store connection properties with a local Secure Agent, the organization must have the Externalize
Connections license.
When you store connection properties with Informatica Cloud, the connection properties are always available.
Informatica Cloud backs up connection properties regularly as part of standard backup procedures.
When you store properties with a local Secure Agent, the Secure Agent must be running to allow tasks to run
and to allow users to work with connections. Back up connection properties regularly to prevent loss of data.
A best practice is to back up connection properties after you change the location or the encryption key for
connection properties. Connection properties are stored in the following directory:
<SecureAgent_InstallDir>/main/data
Informatica Cloud generates an encryption key to secure connection properties stored with a Secure Agent.
As the basis for the encryption key, you can use a randomly generated password or you can enter a custom
password.
Use a custom password when you want to update the encryption key periodically. You can change the
custom password when you want to update the encryption key.
When you change where you want to store connection properties, Informatica Cloud moves the connection
properties to the appropriate location. For example, your license expires, so you configure the organization to
store connections with Informatica Cloud. Informatica Cloud moves the connection properties from the local
Secure Agent to Informatica Cloud.
To determine where to store connection properties, configure the Connection Properties Storage
organization property.

Organization Hierarchies
An organization hierarchy is a hierarchy of related organizations that includes a parent organization and one
or more sub-organizations. The administrator for a parent organization can create an organization hierarchy
and manage sub-organization licenses. To create a sub-organization, the parent organization must have the
Org Hierarchy license.
An example of an organization hierarchy in practice is the use of sub-organizations for development, test,
and production environments. You can use a sub-organization to develop tasks, a sub-organization to test
the tasks, and another sub-organization to run the tasks. You can migrate the task objects from one suborganization to another sub-organization. Another example is to create an organization hierarchy to reflect
different groups of users, where you create a sub-organization for each group.
An organization hierarchy can include a limited number of sub-organizations. The Maximum SubOrganizations organization property states the maximum number of sub-organizations that are allowed for
your organization. To increase the number of sub-organizations allowed for your organization, contact
Informatica Global Customer Support.

16

Chapter 2: Organization Administration

A sub-organization cannot be a parent to any organizations or be a part of any other organization hierarchy.
You can add a sub-organization to the hierarchy in the following ways:

Create a sub-organization.

Link an existing organization. In the organization hierarchy, the organization that you link to becomes a
sub-organization, and the organization you link from becomes the parent organization.

Creating a Sub-organization
The administrator of the parent organization can create a sub-organization.
1.

Log in to the parent organization and then click Administer > Sub-organizations.

2.

On the Sub-organizations page, click New.

3.

To enable user access, create user accounts and configure organization properties.

Linking Organizations
You can link an organization if all of the following conditions apply:

You have a user account with the organization.

The organization is not part of another organization hierarchy.

You are the administrator of the parent organization with the Org Hierarchy license.

Note: You cannot remove a link between organizations.

1.

Log in to the organization that you want to be the parent organization and click Administer > Suborganizations.

2.

On the Sub-organizations page, click Link Existing Organization.

3.

In the Informatica Cloud Login dialog box, enter the user name and password that you use to log in to
the organization that you want to set up as a sub-organization.

4.

Click OK.

5.

In the Link Sub-organization dialog box, click OK to link the organization.

The organization displays on the Sub-organizations page.

Changing Between Organizations

An organization can have multiple sub-organizations. If you are set up as a user in multiple organizations,
you can change between organizations in the organization hierarchy.
To change to a different organization in the hierarchy:
u

In the upper right corner of the Informatica Cloud application, select the organization you want to view.

License Management
Licenses determine the Informatica Cloud subscription level for the organization and provide access to
Informatica Cloud applications, features, connectors, and bundles.
As an administrator, you review licenses set up for your company, monitor job activities to see how usage
aligns with your license subscription, and manage license expiration.
License Management

17

License Types
When you create an Informatica Cloud organization, Informatica Cloud assigns the organization a license
type for each application.
Informatica Cloud uses the following types of licenses:
Trial
You can use the application free of charge for a 30-day period. At the end of the trial period, you can
subscribe to the application. A trial subscription might provide limited access to the features of the data
application.
Subscription
You can use the application for the duration of the contract period. Near the end of the contract period,
Informatica Cloud indicates that the contract is about to expire. Renew the contract to continue to use
the application.
Free subscription
You can use the Data Synchronization application free of charge. A free subscription might provide
limited access to the features of the Data Synchronization application.

License Categories
Informatica Cloud licenses are categorized by application, feature, and functionality.
The following license categories are available:
Application license
Application licenses provide access to Informatica Cloud applications such as Data Synchronization,
Contact Validation, Data Replication, and Mapping Configuration.
Feature license
Feature licenses provide access to features such as fine-grained security, object migration, and
Salesforce connectivity.
Organization hierarchy license
Use the organization hierarchy license to create a specified number of sub-organizations under the
parent organization.
Connector license
Connector licenses provide connections to entities such as Amazon Redshift, NetSuite, and JDBC.
Bundle license
Bundle licenses provide access to a set of objects that improve developer productivity and enhance the
overall quality of data conversion and data integration projects.
Package license
Package licenses provide access to packages such as the Financial Data and Data Standardization Data
Quality packages.

18

Chapter 2: Organization Administration

Sub-organization Licenses
A sub-organization can be assigned licenses that are assigned to the parent organization and have licenses
or subscriptions maintained by the parent organization.
When you add a sub-organization, the sub-organization inherits all licenses and subscription options of the
parent with the following exceptions:

A sub-organization does not inherit the Org Hierarchy license.

A sub-organization does not inherit bundle licenses. To use a bundle in the sub-organization, a user must
install the bundle.

If you link a sub-organization that has a license that the parent organization does not have, then the suborganization loses the license.
After you create or link a sub-organization, you can edit the licenses of the sub-organization.
Note: You cannot edit the job limit of a sub-organization's license.

Editing Sub-Organization Licenses

The organization administrator can edit the licenses for the sub-organizations in the organization hierarchy.
1.

Log in to the parent organization and click on Administer > Sub-organizations.

2.

Under Actions, click on the key icon next to the sub-organization you want to edit.

3.

Select licenses to enable features, and clear licenses to disable features.

4.

Optionally, modify expiration dates.

5.

Click OK to save your changes.

Monitoring Application Job Details

You can check the number of rows that your organization has processed and the number of jobs that your
organization has run with each application.
Some organizations have a daily or monthly limit on the number of jobs that can run for each application type.
If your organization reaches the daily or monthly limit for an application, you cannot run additional jobs until
the next day or the next month, respectively.
If your organization subscribes to Informatica Cloud Express, you might want to check the monthly processed
row counts because they can affect your monthly payment price. You might also want to check the number of
jobs your organization runs. Organizations subscribed to Informatica Cloud Express can run 250 jobs a day
for the subscribed application.
Trial organizations can process a limited number of rows and jobs each day and month for each application
type. The following number of rows and jobs are allowed for trial organizations by default:

10,000 rows each day for each application, and 300,000 rows each month for each application

25 jobs each day for each application, and 250 jobs each month for each application

To view the number of processed rows and jobs that your organization has run, select Administer >
Licenses.

License Management

19

License Expiration
When a license expires, you cannot access the application or features associated with the license and
scheduled jobs associated with the license are disabled.
After you extend the license and enable the license, you can access the application or features and the
scheduled jobs resume processing. If all licenses for the organization expire, you cannot log in to Informatica
Cloud.
Sub-organization licenses must expire at the same time or before the parent organization licenses expire. If
the parent organization license is disabled or set to expire at an earlier date, you must align these changes
for the sub-organization. Edit the sub-organization licenses to confirm the changes.
You can review the expiration date for licenses. To extend a license, contact Informatica Global Customer
Support.

20

Chapter 2: Organization Administration

CHAPTER 3

Secure Agents
This chapter includes the following topics:

Informatica Cloud Secure Agent Overview, 21

Secure Agent Installation on Windows, 23

Secure Agent Installation on Linux, 26

Secure Agent Properties, 28

Runtime Environment Configuration, 32

Rules and Guidelines for the Secure Agent, 33

Stopping and Restarting the Secure Agent on Windows, 33

Starting and Stopping the Secure Agent on Linux, 34

Deleting a Secure Agent, 34

Informatica Cloud Secure Agent Overview

The Informatica Cloud Secure Agent is a lightweight program that runs all tasks and enables secure
communication across the firewall between your organization and Informatica Cloud. When the Secure Agent
runs a task, it connects to the Informatica Cloud hosting facility to access task information. Then the Secure
Agent connects directly and securely to sources and targets, transfers data between sources and targets,
and performs any additional task requirements.
When you install a Secure Agent, all Informatica Cloud users in the organization share the Secure Agent.
The Secure Agent must be running to run tasks. Run multiple Secure Agents to improve scalability or to
create backup agents. You can run one Secure Agent on each machine. You assign Secure Agents to
runtime environments, which you assign to connections and tasks.
To set up and manage Secure Agents for your business needs, you perform the following tasks:
1.

Install Secure Agents.

2.

Set Secure Agent properties.

3.

Configure runtime environments.

21

Runtime Environments
A runtime environment is an environment that you configure to access connections and to run tasks. You can
assign one or more Secure Agents to a runtime environment.
By default, a Secure Agent is assigned to its own runtime environment. If you have the Secure Agent Cluster
license, you can add more than one Secure Agent to a runtime environment.
You can create runtime environments to serve different functions. For example, you create a production
runtime environment and a test runtime environment. You configure connections in the production runtime
environment to the production organization in Salesforce and the production databases. You configure
connections in the test runtime environment to the sandbox organization in Salesforce and the test
databases. You test changes to mappings in the test runtime environment to ensure they run properly before
deploying the changes to the production runtime environment.
A runtime environment with more than one Secure Agent can increase scalability and flexibility, because
tasks can run if one of the Secure Agents is available. In addition, when you add or delete Secure Agents to
a runtime environment with other Secure Agents, you do not have to edit associated connections or tasks.
If you assign more than one Secure Agent to a runtime environment, then all the Secure Agents must be
functionally the same. Verify that the installation directory and directory paths are the same on each Secure
Agent machine in the runtime environment. Ensure that all Secure Agents assigned to a particular runtime
environment are configured and enabled to connect to the same external systems, which includes access to
the files needed for connections, such as libraries, initialization files, and JAR files. If files are used as part of
data integration tasks, ensure the files are available in a shared file system location.
When you start a task in a runtime environment with more than one Secure Agent, one of the Secure Agents
runs the task. After a task is complete, to see which Secure Agent ran the task, go to Monitor > Activity Log
and click on the task name. You might need to access the local machine with the Secure Agent that ran the
task to see success files and error files for certain connections.

Secure Agent Requirements

The following table describes the requirements for the Secure Agent:
Requirement
Operating System

Description
Use one of the following operating systems:
- Microsoft Windows versions:
- Windows 7 (32-bit or 64-bit)
- Windows XP Pro SP2 or SP3 (32-bit)
- Windows 2008 R2 (32-bit or 64-bit)
- Linux (32-bit or 64-bit) with the following configuration:
- Red Hat Enterprise Linux version 6.x and above
- SUSE Linux Enterprise version 11.0 and above

Disk Space

500 MB.

Internet Access

Access to the web server that runs the Informatica Cloud application.

Connectivity

Network connectivity or internet access to sources and targets.

For more information about Secure Agent requirements, contact Informatica Global Customer Support.

22

Chapter 3: Secure Agents

Secure Agent IP Address Ranges

If your organization uses a protective firewall, include the Secure Agent IP address ranges on the list of
approved IP addresses. This ensures the Secure Agent can perform all necessary tasks through the firewall.
For the IP address ranges used by the Secure Agent, see the following community article:
https://community.informatica.com/docs/DOC-2173.

Secure Agent Installation on Windows

On Windows, the Secure Agent runs as a Windows service. When you install the Secure Agent, you also
install the Informatica Cloud Secure Agent Manager.
By default, the Secure Agent starts when you start Windows. Use the Secure Agent Manager to stop and
restart the Secure Agent. You can also use the Secure Agent Manager to check the Secure Agent status, and
configure proxy information.
You can launch the Secure Agent Manager from the Start menu or desktop icon.
When you close the Secure Agent Manager, it minimizes to the Windows taskbar notification area for quick
access. Closing the Secure Agent Manager does not affect the Secure Agent status.
When you install a Secure Agent, you perform the following steps:
1.

Ensure the machine on which you run the Secure Agent meets the minimum requirements.

2.

Download the Secure Agent installation wizard.

3.

Install and register the Secure Agent.

You can perform the following tasks for a Secure Agent:

View the Secure Agent status.

View the Secure Agent details.

View the Secure Agent audit.

Stop the Secure Agent.

Restart the Secure Agent.

Configure proxy settings.

Configure a Windows network login.

Delete a Secure Agent.

Uninstall a Secure Agent.

Downloading the Secure Agent Installation Wizard

Download the Secure Agent installation wizard from Informatica Cloud. You can download and run the
Secure Agent on any machine that meets the minimum requirements.
1.

Click Configure > Runtime Environments, and then click Download Secure Agent.

2.

Select the operating system on which you will run the Secure Agent, and then click Download.

3.

Save the installation wizard to the machine where you want to run the Secure Agent.
The name of the Windows Secure Agent installation file is agent_install.exe. The name of the Linux
Secure Agent installation file is agent_install.bin.

Secure Agent Installation on Windows

23

Installing the Secure Agent on Windows

You can install one Secure Agent on each machine. You must uninstall the existing Secure Agent from the
machine before you install a new Secure Agent. After the installation completes, a registration page appears.
Use your Informatica Cloud username and password to register the Secure Agent. After you complete the
registration, the Secure Agent Manager displays the Secure Agent status.
If the organization requires a proxy server to connect to the internet, the installation wizard configures the
proxy settings for the Secure Agent based on the proxy settings in the browser. You must configure the proxy
settings if they change or are incorrectly configured by the installation program.
Configure a login to allow the Secure Agent to access directories to configure and run tasks. When you
configure or run tasks that use Flat File or FTP/SFTP connection types, the Secure Agent might require
permissions to read or write information to related directories.
To install the Secure Agent on Windows:
1.

Open the directory where you downloaded agent_install.exe, and double-click the file.

2.

Choose the installation folder and click Next.

3.

Review the pre-installation summary and click Install.

4.

After the installer completes, click Done.

A registration page appears.

5.

Enter your Informatica Cloud user name and password and click Register.
The Secure Agent starts.
The Informatica Cloud Secure Agent window displays the status of the Secure Agent. You can restart,
stop, and configure the Secure Agent proxy in this window. You can close the window at any time. The
Secure Agent continues to run as a service until stopped.

6.

Close the Secure Agent Manager.

The Secure Agent Manager minimizes to the Windows taskbar notification area. Closing the Secure
Agent Manager does not affect the Secure Agent status.

Configuring the Proxy Settings on Windows

If your organization uses an outgoing proxy server to connect to the internet, the Secure Agent connects to
the Informatica Cloud application through the proxy server. The Secure Agent installation wizard configures
the proxy server settings for the Secure Agent based on settings configured in the browser. Configure proxy
server settings if they change or if they are incorrectly configured by the installation program.
Contact your network administrator for the correct proxy settings.
To configure the proxy settings for the Secure Agent on a Windows machine:
1.

To launch the Secure Agent Manager, click Start > All Programs > Informatica Cloud Secure Agent >
Informatica Cloud Secure Agent.
If the Secure Agent Manager is active, you can click the Informatica Cloud icon in the Windows taskbar
notification area to open the Secure Agent Manager.
The Secure Agent Manager displays the Secure Agent status.

24

2.

In the Secure Agent Manager, click Proxy.

3.

To enter proxy server settings, click Use a Proxy Server.

Chapter 3: Secure Agents

4.

Enter the following information:

Field

Required/

Description

Optional

5.

Proxy Host

Required

Host name of the outgoing proxy server that the Secure Agent uses.

Proxy Port

Required

Port number of the outgoing proxy server.

User Name

Optional

User name to connect to the outgoing proxy server.

Password

Optional

Password to connect to the outgoing proxy server.

Click OK.
The Secure Agent Manager restarts the Secure Agent to apply the new settings.

Configuring a Login for a Windows Secure Agent Service

On Windows, you can configure a network login for the Secure Agent service. A login allows the Secure
Agent to access the network with the privileges and permissions associated with the login.
Configure a login to allow the Secure Agent to access directories to configure and run tasks. When you
configure or run tasks that use Flat File or FTP/SFTP connection types, the Secure Agent might require
permissions to read or write information to related directories.
For example, to browse to a directory to configure a Flat File or FTP/SFTP connection, the Secure Agent
login might require permission to access the directory. Without a Secure Agent login with the appropriate
permissions, Informatica Cloud cannot display the directory in the Browse for Directory dialog box.
To configure a login for a Secure Agent service:
1.

From the Windows Control Panel, click Administrative Tools > Services.

2.

In the Services window, right-click the Informatica Cloud Secure Agent service and click Properties.

3.

In the properties dialog box, click the Log On tab.

4.

To configure a login, select This Account.

5.

Enter an account and associated password.

Use an account with the required privileges and permissions for the network security defined for the
domain. By default, the account format is <domain_name>\<user_name>.

6.

Click OK.

7.

In the Services window, restart the Secure Agent service for the changes to take effect.

Uninstalling the Secure Agent on Windows

You can uninstall the Secure Agent. You might uninstall the Secure Agent if you no longer want to run the
Secure Agent on the machine or if you want to reinstall the Secure Agent.
Before you uninstall the Secure Agent, make sure no connections are configured to use it.

Secure Agent Installation on Windows

25

To uninstall the Secure Agent:

1.

Click Start > All Programs > Informatica Cloud Secure Agent > Uninstall Informatica Cloud Secure
Agent.
The Secure Agent uninstaller launches.

2.

Click Uninstall.

3.

When the uninstall completes, click Done.

4.

Delete any remaining files in the installation directory.

After you uninstall the Secure Agent, log files may still exist in the directory where you installed the
Secure Agent.

Secure Agent Installation on Linux

On Linux, the Secure Agent runs as a process. You can use a shell command line to install, register, start,
stop, and uninstall the Secure Agent. You can also use the shell command line to check the Secure Agent
status. Once started, the Secure Agent continues to run as a process until stopped.
Note: A Secure Agent that runs on Linux does not support tasks that contain a Microsoft SQL Server source
or target.
When you install a Secure Agent, you perform the following steps:
1.

Ensure the machine on which you run the Secure Agent meets the minimum requirements.

2.

Download the Secure Agent installation wizard.

3.

Install, start, and register the Secure Agent.

You can perform the following tasks for a Secure Agent:

View the Secure Agent status.

View the Secure Agent details.

View the Secure Agent audit.

Edit the Secure Agent.

Start and stop the Secure Agent.

Configure proxy settings.

Delete a Secure Agent.

Uninstall the Secure Agent.

Downloading the Secure Agent Installation Wizard

Download the Secure Agent installation wizard from Informatica Cloud. You can download and run the
Secure Agent on any machine that meets the minimum requirements.
1.

Click Configure > Runtime Environments, and then click Download Secure Agent.

2.

Select the operating system on which you will run the Secure Agent, and then click Download.

3.

Save the installation wizard to the machine where you want to run the Secure Agent.
The name of the Linux Secure Agent installation file is agent_install.bin.

26

Chapter 3: Secure Agents

Installing and Registering the Secure Agent on Linux

You can install one Secure Agent on each machine. You must uninstall the existing Secure Agent from the
machine before you install a new Secure Agent. After the installation completes, start the Secure Agent, then
use your Informatica Cloud username and password to register the Secure Agent.
If the organization requires a proxy server to connect to the internet, the installation wizard configures the
proxy settings for the Secure Agent based on the proxy settings in the browser. You must configure the proxy
settings if they change or are incorrectly configured by the installation program.
To install the Secure Agent on Linux:
1.

In a shell command line, navigate to the directory where you downloaded the file and enter the following
command:
agent_install.bin i console
The installer completes.

2.

To start the Secure Agent, navigate to the directory where you installed the Secure Agent and enter the
following command:
infaagent startup
After the Secure Agent starts, register the Secure Agent.

3.

To register the Secure Agent, navigate to the following directory:

4.

Enter the following command using your Informatica Cloud username and password:

<SecureAgent_InstallDirectory>/main/agentcore
consoleAgentManager.sh

configure <username> <password>

You can check the registration status of a Secure Agent using the following command in the same
directory:
consoleAgentManager.sh

isConfigured

Configuring the Proxy Settings on Linux

If your organization uses an outgoing proxy server to connect to the internet, the Secure Agent connects to
the Informatica Cloud application through the proxy server. The Secure Agent installation wizard configures
the proxy server settings for the Secure Agent based on settings configured in the browser. If the proxy
server settings are not set correctly or change, update the proxy server settings defined for the Secure Agent.
Contact the network administrator to determine the proxy settings.
To configure the proxy server settings for the Secure Agent on a Linux machine:
1.

Open the following directory:

<SecureAgent_InstallDirectory>\main

2.

Edit the following properties in the proxy.ini file:

Field

Description

InfaAgent.ProxyHost

Host name of the outgoing proxy server that the Secure Agent uses.

InfaAgent.ProxyPort

Port number of the outgoing proxy server.

Secure Agent Installation on Linux

27

Field

Description

InfaAgent.ProxyUser

User name to connect to the outgoing proxy server.

InfaAgent.ProxyPassword

Password to connect to the outgoing proxy server.

3.

Save and close the file.

4.

Restart the Secure Agent.

Uninstalling the Secure Agent on Linux

You can uninstall the Secure Agent. You might uninstall the Secure Agent if you no longer want to run the
Secure Agent on the machine or if you want to reinstall the Secure Agent.
Before you uninstall the Secure Agent, make sure no connections are configured to use it.
To uninstall the Secure Agent on Linux:
1.

Open the command line.

2.

Navigate to the directory where you installed the Secure Agent.

3.

Enter the following command in the command line to stop the Secure Agent Linux process:

4.

To uninstall the Secure Agent, run rm -rf on the directory where you installed the Secure Agent to
remove Secure Agent files.

infaagent shutdown

Secure Agent Properties

You can edit the Secure Agent name, update Secure Agent configuration properties, and add custom
configuration properties for the Secure Agent. Modify the Secure Agent configuration properties to change or
optimize Secure Agent behavior.
For example, to configure the Secure Agent Core to perform a connectivity check every five seconds, you
can set the maintenance-check-period property to 5.
You can configure the following types of Secure Agent configuration properties:
Secure Agent Core
The following table describes the Secure Agent Core properties that you can configure:

28

Secure Agent Core

Property

Description

resource-releasewaiting-time

Number of seconds that the Secure Agent Core waits for the Secure Agent
Manager to exit.

tomcat-notificationperiod

Number of seconds that the Secure Agent Core waits for the Apache Tomcat
process to notify the Secure Agent Core that it is ready.

Chapter 3: Secure Agents

Secure Agent Core

Property

Description

upgrade-check-period

Number of seconds that the Secure Agent Core checks for upgrade from the
server. The minimum value that you can enter is 30 seconds.

maintenance-checkperiod

Number of seconds that the Secure Agent Core waits to perform maintenance
checks.

waiting-time-fortomcat-shutdown

Number of seconds that the Secure Agent Core waits for the Apache Tomcat
process to shut down before aborting it.

rmi-info-refresh-period

Number of seconds that the Secure Agent Core waits to refresh the Java RMI
information.

tomcat-check-period

Number of seconds that the Secure Agent Core waits to check if the Apache
Tomcat process is running. Secure Agent Core starts the Apache Tomcat process
if it is supposed to be running.

waiting-time-for-jobscomplete

Number of seconds that the Apache Tomcat process waits for jobs to complete
before shutting down to upgrade the Secure Agent.

Secure Agent Manager

The following table describes the Secure Agent Manager properties that you can configure:
Secure Agent Manager
Property

Description

start_as_windows_service

Indicates whether the Secure Agent Core starts as a Windows service.

Use one of the following values:
- True. The Secure Agent Core starts as a Windows service.
- False. The Secure Agent Core starts as a process.

DTM
The following table describes the ETL engine properties that you can configure:
DTM Property

Description

AgentConnectionTimeout

Number of seconds that the Secure Agent communication requests to wait

before it times out.

SalesForceConnectionTimeout

Number of seconds that the Salesforce web service requests to wait

before it times out.

Note: Configure other DTM properties only when Informatica Global Customer Support instructs you to.

Secure Agent Properties

29

Apache Tomcat JRE

The following table describes the Apache Tomcat JRE properties that you can configure:
Apache Tomcat JRE
Property

Description

JRE_OPTS

The JRE VM options for the Apache Tomcat process.

INFA_MEMORY

The JRE VM options that are set for virtual machine memory for the Apache
Tomcat process.

INFA_SSL

Configure this property only when Informatica Global Customer Support

instructs you to.

Secure Agent Core JRE

The following table describes the Secure Agent JRE properties that you can configure:
Secure Agent Core JRE Property

Description

JRE_OPTS

The JRE VM options set for the Secure Agent Core.

Apache Tomcat
Configure the Apache Tomcat properties only when Informatica Global Customer Support instructs you
to.
Secure Agent Core Log4J
Configure the Secure Agent Core Log4J logging properties only when Informatica Global Customer
Support instructs you to.
Apache Tomcat Log4J
Configure the Apache Tomcat Log4J logging properties only when Informatica Global Customer Support
instructs you to.
Secure Agent Manager Log4J
Configure the Secure Agent Manager Log4J logging properties only when Informatica Global Customer
Support instructs you to.

Configuring Secure Agent Properties

Complete the following steps to edit the Secure Agent details.
1.

Click Configure > Runtime Environments.

2.

On the Runtime Environments page, if necessary, expand the runtime environments to see the list of
Secure Agents. Click the Secure Agent name from the list.

3.

Click Edit on the View Secure Agents page or select Edit Secure Agent under Actions.
The Edit Secure Agent page appears.

4.

If you want to change the Secure Agent name, in Agent Name, enter the new name.

5.

To edit a Secure Agent configuration property, in the Type list, select the type.
The properties associated with the type appear.

30

Chapter 3: Secure Agents

6.

To edit a property value, click the Edit Agent Configuration icon next to the property that you want to
edit.

7.

To reset the property to the system default, click the Reset Agent Configuration to system default
icon.
You can configure properties for the following configuration types:

8.

9.

Agent Core

Agent Manager

DTM

Apache Tomcat JRE

Agent Core JRE

To add custom properties, complete the following steps:

a.

Select a configuration type.

b.

Choose INFO or DEBUG sub-type to determine logging level.

c.

Enter a name and value.

Click the Add icon or the Delete icon to add or delete properties.

10.

To reset all the configuration properties to the default settings, click Reset All.

11.

Click OK to save your changes.

Viewing Secure Agent Status and Details

You can view detailed information about a Secure Agent on the View Secure Agents page. For example,
you can view the Secure Agent status, Secure Agent audit information, and Secure Agent properties. You
can also refresh the status of a Secure Agent.
To view Secure Agent details:
1.

Click Configure > Runtime Environments.

The Runtime Environments page lists all Secure Agents for your organization. If necessary, expand the
runtime environments to see the list of Secure Agents.

2.

Click the name of the Secure Agent that you want to view.
The View Secure Agent page displays Secure Agent details and version. It also displays the Secure
Agent package and configuration details.

3.

To refresh the status of the Secure Agent, click Refresh Status.

View the Secure Agent Status on Linux

If desired, you can view the Secure Agent status on Linux instead of on the Informatica Cloud View Secure
Agent page.
To view the Secure Agent status on Linux:
1.

In a shell command line, navigate to the following directory:

<SecureAgent_InstallDirectory>/main/agentcore

2.

Run the following command:

consoleAgentManager.sh

getstatus

The command returns the Secure Agent status.

Secure Agent Properties

31

3.

To refresh the status of the Secure Agent, you can repeat Step 2, or you can run the following command:
consoleAgentManager.sh

updatestatus

You might need to use the updatestatus command if you have intermittent connectivity with the Secure
Agent.

View the Secure Agent Audit

The Secure Agent audit includes start and stop times, server connection and upgrade information.
You can configure the number of rows displayed on the page.
To view the Secure Agent audit:
1.

Click Configure > Runtime Environments.

2.

On the Runtime Environments page, click the name of the Secure Agent. If necessary, expand the
runtime environments to see the list of Secure Agents.

3.

On the View Secure Agent page, click View Agent Audit.

The Secure Agent Audit page appears.

4.

Use the Rows per Page option to change the number of rows that display on each page.

Runtime Environment Configuration

You can configure runtime environments to group Secure Agents. You can also edit or delete Secure Agents
and monitor the status of Secure Agents.
Go to Configure > Runtime Environments to perform the following tasks:

Create a runtime environment

Download a Secure Agent

Rename or delete a runtime environment

Add Secure Agents to or remove Secure Agents from a runtime environment

To add or remove a Secure Agent, select the appropriate action under the runtime environment.

Edit or delete a Secure Agent

Configuring Secure Agents in Runtime Environments

You can add Secure Agents to or remove Secure Agents from a runtime environment.
1.

Go to Configure > Runtime Environments.

2.

If you want to assign Secure Agents to a runtime environment, ensure that the Secure Agents are
currently unassigned.
Secure Agents can only be assigned to one runtime environment.

3.

Under Actions for the runtime environment you want to configure, select Add or Remove Secure
Agents.
The Add or Remove Secure Agents window appears.

32

Chapter 3: Secure Agents

4.

Select the Secure Agents you want to assign to the runtime environment, or clear the Secure Agents you
want to unassign to the runtime environment.
If there is one Secure Agent in a runtime environment and the runtime environment is used in any
connections, you cannot unassign the Secure Agent. Configure the connection to use a different runtime
environment before unassigning the Secure Agent, or, if you have the Secure Agent Cluster license, add
a different Secure Agent to the runtime environment.

Rules and Guidelines for the Secure Agent

Use the following rules and guidelines for the Secure Agent:

The machine that runs the Secure Agent must meet the minimum requirements.

You do not have to install the Secure Agent on the machine that you use to connect to Informatica Cloud.
For example, you might use machine A to connect to Informatica Cloud and Machine B to run the Secure
Agent.

If you install the Secure Agent on Linux, do not include spaces in the directory path. If you include spaces,
the Secure Agent installation may stop responding.

If you install the Secure Agent on Windows, the Windows user account that installed the Secure Agent
must have access to all remote directories that contain flat source or target files.

If you install the Secure Agent on Windows 2008, make sure the Microsoft Visual C++ 2008
Redistributable Package (x86) is installed on the machine.

You can run more than one Secure Agent, but run only one Secure Agent on each machine.

The Secure Agent must be running to run tasks. If the Secure Agent loses connectivity to Informatica
Cloud, it tries to reestablish connectivity to continue the task. If it cannot reestablish connectivity, the
Secure Agent becomes disabled and the task fails.

If an Informatica Cloud application shuts down for more than 12 hours, the Secure Agent connection to
the Informatica Cloud application times out. Manually restart the Secure Agent on each client machine.

You must uninstall the Secure Agent before you install another Secure Agent on the same machine.

Stopping and Restarting the Secure Agent on

Windows
On Windows, the Secure Agent installation wizard starts the Secure Agent service. The installation wizard
also configures the Secure Agent service to run upon Windows startup.
You can use the Secure Agent Manager to stop or restart the Secure Agent.
1.

To launch the Secure Agent Manager, click Start > All Programs > Informatica Cloud Secure Agent >
Informatica Cloud Secure Agent.
If the Secure Agent Manager is active, you can click the Informatica Cloud icon in the Windows taskbar
notification area to open the Secure Agent Manager.
The Secure Agent Manager displays the Secure Agent status.

2.

To stop the Secure Agent, click Stop. To restart the Secure Agent, click Restart.

Rules and Guidelines for the Secure Agent

33

The Secure Agent Manager displays a message when the action is complete.
3.

Close the Secure Agent Manager.

The Secure Agent Manager minimizes to the Windows taskbar notification tray. Closing the Secure
Agent Manager does not affect the Secure Agent status.

Starting and Stopping the Secure Agent on Linux

After you download the Secure Agent program files on a Linux machine, you can run the Secure Agent as a
Linux process. Manually start the Secure Agent process on Linux.
1.

From the command line, navigate to the directory where you installed the Secure Agent.

2.

To start the Secure Agent, enter the following command:

infaagent startup

3.

To stop the Secure Agent, enter the following command:

infaagent shutdown

You can view the Secure Agent status from Informatica Cloud or from a Linux command line.

Deleting a Secure Agent

Delete a Secure Agent if you no longer need it to run tasks.
You cannot delete a Secure Agent if it is associated with a connection. Before you delete a Secure Agent,
update associated connections to use another Secure Agent.
1.

Click Configure > Runtime Environments.

2.

On the Runtime Environments page, under Actions, click Delete Secure Agent next to the Secure
Agent.
If the Secure Agent is running, a warning message appears. Stopping an active Secure Agent prevents
scheduled tasks associated with the Secure Agent from running. Ignore the warning if you do not need
the Secure Agent.

If you no longer need the Secure Agent, uninstall the Secure Agent.

34

Chapter 3: Secure Agents

CHAPTER 4

User and User Group

Administration
This chapter includes the following topics:

User and User Group Overview, 35

Roles, 36

User Groups, 37

Permissions, 39

Rules and Guidelines for Roles, User Groups, and Permissions, 41

Users, 42

User Configuration Examples, 45

User and User Group Overview

You can use a combination of roles, user groups, and object-level permissions to secure the objects and data
for your organization.
You can use the following levels of privileges and permissions to define security for your organization:
Role
A role is a collection of privileges, and it defines the general tasks that a user can perform.
User Group
A user group is a collection of permissions for object types.
Object-level Permissions
Object-level permissions determine user permissions for individual objects.
To work with user groups or object-level permissions, your organization must have the Fine-Grained Security
license. For information about this license, contact Informatica Global Customer Support.
In addition to these security measures, you can increase the requirements to the organization with the TwoFactor Authentication and Minimum Character Mix organization properties. You can also limit the ability to
preview data with the Allow Data Preview user security option.

35

Roles
A role determines a user's privileges and defines the general tasks that a user can perform. An organization
administrator must assign at least one role to each user.
Roles determine the functionality and Informatica Cloud menus that are available to a user. For example, to
access and perform any tasks on the Administer menu, you need the Admin role.
You can use the following roles in Informatica Cloud:

Admin

Designer

Service consumer

In addition to roles, user groups and object-level permissions can determine the ability of a user to view and
perform tasks on an object.
The following table describes the privileges for each role:
Privilege

Admin
Role

Designer
Role

Service Consumer

Access to all available functionality on the

Home menu.

Yes

Yes

Yes

Access to all available functionality on the

Monitor menu.

Yes

Yes

No

Access to all available functionality on the

Apps menu.

Yes

Yes

Partial. Can view tasks, run

tasks, and download workflow
XML.
For data replication tasks, can
create and reset targets.

Access to all available functionality on the

Design menu.

Yes

Yes

Partial. Can run task flows and

test run a mapping.

Access to all available functionality on the

Configure menu.

Yes

Yes

No

Access to all available functionality on the

Administer menu.

Yes

No

No

Admin Role
The Admin role has access to all Informatica Cloud functionality and can perform any task in the
organization.
The best practice is to assign the Admin role to one or two trusted users and assign the users to an
administrative user group that allows access to all objects and permissions. These users can act as
alternative organization administrators and can help troubleshoot access control and other issues that might
occur as you increase organization security.

36

Chapter 4: User and User Group Administration

Designer Role
The Designer role has limited access to Informatica Cloud functionality.
The Designer role has access to all available functionality on the Home, Monitor, Apps, Design, and
Configure menus. The Designer role can configure and test tasks, configure all related objects, and monitor
jobs. The Designer role does not have access rights to the Administer menu.

Service Consumer Role

The Service Consumer role has limited access to Informatica Cloud functionality. The Service Consumer role
can view and run tasks and download workflow XML.
The Service Consumer role has the following privileges:

Access to all available functionality on the Home menu.

From the Apps menu, ability to view tasks, run tasks, download workflow XML, and create and reset
targets for data replication tasks.

From the Design menu, ability to run task flows and test run mappings.

The Service Consumer role does not have access rights to the following menus:

Monitor

Configure

Administer

User Groups
A user group is a collection of permissions for object types. If your organization has the Fine-Grained
Security license, you can create and manage user groups.
An organization administrator can create and assign user groups. The user group defines the types of objects
that a user can access, and the related tasks a user can perform.
Assign each user to at least one user group. Any user not assigned to a user group has limited access to
Informatica Cloud functionality, as users are restricted from any objects and permissions not included in their
user group. You can assign a user to more than one user group.
Important: To ensure that the organization administrator does not lose administrative privileges to
Informatica Cloud functionality, set up an administrative user group with access to all objects and assign the
organization administrator to the group. A best practice is to assign a few other administrators to this group
as well to serve as backup to the organization administrator.
The User Groups page displays a list of all user groups in the organization.
You can perform the following tasks for a user group:

Configure a user group.

Edit a user group.

View user group details.

Delete a user group.

User Groups

37

Configuring a User Group

When you configure a user group, define the name, description, and permissions for the group. You can also
add users to the group.
1.

To create a user group, click Administer > User Groups, and then click New.
To edit a user group, click Administer > User Groups, click the user group you want to edit, and then
click Edit.

2.

On the New User Group page or Edit User Group page, configure the following details:
User Group
Field

Description

Name

Name of the user group. User group names are not case sensitive.
The user group name must be unique within the organization. User group names can
contain alphanumeric characters, spaces, and the following special characters:
_.+-

Description
3.

Description of the user group.

Select the permissions that you want to grant to the user group.
If you select a permission that requires Read permission, Read permission is automatically selected. For
example, to delete a connection you must be able to view the connection, so when you select Delete
permission, Read permission is also selected.
Permissions that are not relevant for the object type are disabled.
To select all permissions, click Check All. To clear all permissions, click Clear All.

4.

To add users to the group, you can move users from the Available Users list to the Selected Users list.
You can also add a user to the group individually when you edit the user.

5.

To save all changes, click OK.

Viewing User Group Details

You can view details about a user group, such as the name and permissions for the user group.
1.

Click Administer > User Groups, and then click the name of the user group.
The View User Group page displays user groups details.

2.

To edit the user group, click Edit.

Deleting a User Group

Delete a user group if you no longer need the user group. Remove all users from the user group before you
delete the user group.

38

1.

Click Administer > User Groups.

2.

On the User Group page, click the Delete icon next to the name of the user group.

Chapter 4: User and User Group Administration

Permissions
Permissions determine the access a user has at the object level. You can configure permissions for object
types at the user group-level or configure permissions for specific objects in object-level permissions.
The following list describes the types of permissions that you can configure:
Read
View objects and view details about each object. Use a connection or schedule in a task.
Create
Create objects. Download and install the Secure Agent.
Update
Edit objects. Requires read permission, which is automatically granted.
Delete
Delete objects. Requires read permission, which is automatically granted.
Run
Run tasks and task flows. Restart tasks from the activity log. Monitor jobs and stop jobs in the activity
monitor. Add tasks to a task flow if you have update permission on the task flow. Requires read
permission, which is automatically granted.
Change Permission
Configure permissions for individual objects of the selected type. Requires read permission, which is
automatically granted.

Permissions

39

The following image shows the Permissions area of the User Groups page.

These permissions control what is allowed in Informatica Cloud. They do not control operating system
permissions, such as the ability to start, stop, or configure the Secure Agent on Windows or Linux.

Object-Level Permissions
Object-level permissions define security for specific objects. If your organization has the Fine-Grained
Security license, you can create and manage object-level permissions.
An organization administrator can use object-level permissions to add or remove individual objects from the
user group domain.
By default, the user group defines the objects that a user can access. User group permissions are configured
by object type. Object-level permissions add additional or custom security for specific objects.
For example, you have a Developer user group that allows all users in the group to configure, delete, and run
all tasks. You also have a Scheduling user group that allows its users to configure schedules and task flows,
but not tasks. When a task no longer requires the Developer user group to edit it, you can edit task
permissions to secure the task and move it into production. Configure the task permissions to remove all
permissions for the Developer group. At the same time, you can grant the Scheduling group view and run
permissions.

40

Chapter 4: User and User Group Administration

Configuring Object-Level Permissions

An organization administrator can configure permissions for individual objects in the organization.
1.

Navigate to the object that you want to configure.

For example, to configure permissions for a schedule, click Configure > Schedules to view the
Schedules page.

2.

Click the Change Permission icon for the object. If the Change Permission icon is not available, click
the Edit icon, and then select Change Permissions.
The Change Permissions page displays the user groups in the organization.
If custom permissions have not been configured for the object, Default Permissions is selected, and the
Permissions table displays the permissions that each user group has for the object by default.
If custom permissions have already been configured for the object, the Custom Permissions option is
selected, and the Permissions table displays the custom permissions configured for each user group.

3.

To change the permissions, click Custom Permissions.

The Permissions table displays all relevant permissions for the object. Permissions that are not relevant
are disabled. For example, since the object already exists, the Create permission is disabled.

4.

Configure the permissions that you want to allow for each user group.
To revert to the default permissions configured for all user groups, click Default Permissions.

5.

Click OK.

Rules and Guidelines for Roles, User Groups, and

Permissions
Use the following rules and guidelines for roles, user groups, and object-level permissions:

Assign each user a single role.

When implementing user groups, create an administrative user group with access to all objects. Assign
the organization administrator and backup administrators to the user group.

When implementing user groups, create a set of user groups to provide access to all necessary objects
and assign users to the user groups appropriately.

You can assign a user to more than one user group, but the best practice is to assign each user to a
single user group.

To edit an object, the user also needs read permission for all objects used within the object. For example,
when you assign a user the read and update permission for data synchronization tasks, verify that the
user also has read permission for the connections, saved queries, mapplets, and schedules to be used in
those tasks.

When a user edits a task, objects without read permission do not display. To avoid unexpected results,
the user should cancel all changes and avoid editing the task until you grant the appropriate read
permissions.

When configuring a task flow, a user needs run permission on tasks to be added to the task flow.

To edit a task flow, a user needs run permission for all tasks in the task flow. Without run permission on
all tasks, the user cannot save changes to the task flow.

To monitor jobs or to stop a running job, a user needs run permission for the task or task flow.

Rules and Guidelines for Roles, User Groups, and Permissions

41

To migrate objects, the user account in both the source and target organizations should have the Admin
role with full access to the repository.

When adding a new license to an organization, Informatica Cloud does not grant permissions to user
groups. After receiving a new license, update user groups as necessary to allow access to new objects.

Users
A user is an Informatica Cloud user account that allows secure access to an organization. A user can perform
tasks in the organization based on the role and user group assigned to the user. Object-level permissions
can also affect the tasks a user can perform.
The Users page displays a list of all Informatica Cloud users in the organization.
You can perform the following tasks for a user:

Create a user.

Edit a user.

View user details.

Delete a user.

User Properties
The organization administrator can configure users for the organization.
When you configure a user, you configure the following information:

User properties. Properties such as the user name, password, and maximum login retry attempts.

User details. Information about the user, such as the name, job title, and phone number of the user.

User security. Security options, such as the role, user group, and ability to preview data.

The role for a user defines the general tasks that the user can perform in the organization. The user group for
a user defines the objects the user can work with and the specific tasks that the user can perform. However,
if a user is assigned to a role with limited privileges, the user group cannot override these limitations. For
example, a user in the Service Consumer role is assigned to a user group that has run permissions on tasks.
Because the Service Consumer role limits the user's access to the activity monitor, the user cannot monitor
jobs.

42

Chapter 4: User and User Group Administration

Configure the following user properties for each user:

User Property

Description

User Name

Informatica Cloud user name that identifies the user within the organization. Used to log
in to Informatica Cloud.
The user name must be a valid email address and unique within Informatica Cloud. For
example, john@abc.com.
User names can contain alphanumeric characters and the following special characters:
_.+You cannot modify a user name.

Salesforce User
Name

Salesforce user name.

Confirm Salesforce
User Name

Confirmation of Salesforce user name.

Password

Password for the user account.

The password cannot be the same as the user name.

Confirm Password

Confirmation of the password.

Maximum Login
Attempts

Maximum number of login attempts the user can make before the user is locked out.

Change Password on
Login

Determines if the user must reset the password after the user logs in.

Ignore License
Expiration Messages

Allows you to stop the display of license expiration messages:

If locked out, the user must contact Informatica Global Customer Support to reset the
account.

Select this option to require a user to create a new password after the user logs in.

- False. Shows all license expiration messages.

- True. Does not display license expiration messages.

Configure the following user details for each user:

User Detail

Description

First Name

First name of the user.

Last Name

Last name of the user.

Job Title

Job title of the user.

Phone Number

10-digit telephone number of the user. For example, (123) 456-7890, 123-456-7890, or
123.456.7890.

Emails

Email addresses that receive notification from Informatica Cloud.

Enter one or more valid email addresses. Use commas to separate multiple email addresses.
Email addresses can contain alphanumeric characters and the following special characters:
_.+-

Users

43

User Detail

Description

Time Zone

Time zone where the user is located. When the user logs in, all times reflect the time zone of
the user. For example, schedules display the local time in the user time zone.
Default time zone is Pacific Daylight Time, Los Angeles.

Description

Description of the user. Maximum length is 255 characters.

Configure the following security options for each user:

User Security
Option

Description

User Roles

Informatica Cloud role for the user.

Note: Best practice is to assign one role to a user.

User Groups

User group for the user. A user group can help define or limit the tasks that a user can
perform.
The organization administrator configures user groups. If no user groups are listed, no user
groups are defined for the organization.
Note: When you implement user groups, best practice is to assign every user to a user group.

Allow Data
Preview

Allows the user to preview data when configuring a data synchronization task.
By default, this option is enabled. For maximum data security, clear this option.

Configuring a User
1.

To create a user, click Administer > Users, and then click New.
To edit a user, click Administer > Users, click the user name in the list of users, and then click Edit.

2.

On the New User page or Edit User page, configure the user properties.

3.

Configure the user details and security options, and then click OK.

Viewing User Details

You can view details about a user, such as the name, role, and contact information.
u

Click Administer > Users, and then click the user name.
User details appear on the View User page.
To edit the user, click Edit.

Deleting a User
Delete a user if the user no longer needs to access Informatica Cloud.

44

1.

Click Administer > Users.

2.

On the Users page, click the Delete icon next to the user name.

Chapter 4: User and User Group Administration

Audit Logs
The audit log displays Informatica Cloud events for each user. It displays user login, create, update, and
delete operations.
To view the audit log, click Administer > Audit Log.
By default, the audit log shows events for the past 12 months. To change the length of time that events
appear in the audit log, contact Informatica Global Customer Support.

User Configuration Examples

The following examples illustrate ways in which you can configure user groups, permissions, and users to
control access to Informatica Cloud according to your business needs.

You want your development team to create tasks and task flows. To do this, the development team needs
to view sample data in development, but you want to restrict access to production data. You also have a
reporting team that needs to run tasks, but does not have the technical knowledge to configure tasks
safely.
For these two teams, create two separate user groups. For the development team, create a Developer user
group and control the user group as follows:
1.

Configure the Developer group with full permissions for tasks and related objects, but only read
permission for connections.

2.

Assign the Designer role and the Developer group to the users in your development team. When
configuring users, select Allow Data Preview to help with task development.

3.

If possible, create development connections to sample data. If you have both development and
production connections, configure production connections so the Developer group does not have read
permission. This prevents the Developer group from using production connections in tasks.

4.

After testing is complete and tasks are ready to move into production, have an organization administrator
or other qualified user configure the tasks to use production connections.

5.

Edit the Developer user group to remove the permission to run tasks. If development is complete for a
task type, you can also remove permission to read or update the task type and related objects as well.
By removing the read permission, you prevent the Developer group from accessing any information
about production tasks.

For the reporting team, create a Reporting user group, and control the group as follows:
1.

Configure the Reporting group with permission to read and run tasks and task flows, and permission to
read, create, and update schedules. Do not allow the group to edit or delete objects in the organization,
or to change permissions for objects in the organization.

2.

Assign the Designer role and the Reporting group to the users in your reporting team.

You want a site operator who can assign roles and user groups and configure access control, but cannot
create, edit, or run tasks.
1.

Assign the Admin role to the site operator user. With the Admin role, the site operator can configure
users and user groups and manage the organization. To limit access to tasks, connections, and
schedules, assign the site operator to a restrictive Site Operator user group.

User Configuration Examples

45

2.

46

Configure the Site Operator user group as follows:

Assign permissions to read objects and to configure permissions for all object types. If the Site
Operator group needs to download and install the Secure Agent, also grant the group create
permission for Secure Agents.

Restrict all other permissions. By revoking the create, update, delete, or run permissions on objects,
you limit the Site Operator group to performing administrative tasks.

Chapter 4: User and User Group Administration

CHAPTER 5

Connector Administration
This chapter includes the following topics:

Connector Administration Overview, 47

Installing an Informatica Cloud Connector, 47

Microsoft Dynamics CRM Connector Administration, 48

NetSuite Connector Administration, 50

SAP IDocs and RFCs/BAPI Connector Administration, 51

SAP Table Connector Administration, 55

Siebel Connector Administration, 61

Connector Administration Overview

Informatica Cloud Connectors provide connectivity to source and target types that are not supported natively
in Informatica Cloud.
When you install a connector, the connector becomes available as a new connection type for the entire
organization. A user can create connections and use the connections in tasks. Some connectors require
configuration before they can be used.
For documentation about individual Informatica Cloud Connectors, see the
Informatica Cloud Connector Documentation community article.
If you have a request for a connector that is not yet available, or if you would like information about building
an Informatica Cloud Connector, contact Informatica Global Customer Support.

Installing an Informatica Cloud Connector

You can install an Informatica Cloud Connector as a free trial or send notification that you would like to buy
the connector. After you install an Informatica Cloud Connector, it becomes available as connection types for
the entire organization.
1.

Click Configure > Published Connectors.

2.

On the Published Connectors page, to select an Informatica Cloud Connector for free trial, click Free
Trial for the connector.

47

The connector becomes available as a connection type for the entire organization. The connection type
displays with the following naming convention: <connector name> - <publisher name>.
3.

If you would like to buy a license for a connection with an expired free trial, click Contact Us.
An Informatica Cloud representative will contact you with purchase details about a license.

After you install a connector, it displays on the Published Connectors page with the "Connector Available"
message.

Microsoft Dynamics CRM Connector Administration

If you use Active Directory to access Microsoft Dynamics CRM data, perform the additional steps before you
use Microsoft Dynamics CRM connections:
1.

Configure Java security for a Microsoft Dynamics CRM instance that uses self-signed certificates.

2.

Resolve hosts.

3.

Edit the Kerberos configuration file.

4.

Edit the Kerberos login configuration file.

5.

Download Java security policy files.

After you perform the additional configuration, restart the Secure Agent.

Step 1. Configuring Java Security

Configure Java security for Microsoft Dynamics CRM instances that use Active Directory and self-signed
certificates.
1.

Generate root and intermediate SSL certificates for HTTPS URL (.cer files).

2.

Use the command line to navigate to the following directory:

3.

Use the following command to import HTTPS certificates to the Informatica Java Runtime Environment
(JRE):

<SecureAgent_InstallDir>/jre/bin/

keytool -importcert -alias <certificate alias name> -file " <certificate path>
\<certificate filename>" -keystore ..\lib\security\cacerts -trustcacerts
The Certificate Alias Name is any unique name and certificate file name includes the full path to the .cer
files used in Step 1.
The default JRE password is "changeit".

Step 2. Resolving Hosts

Resolve hosts for Microsoft Dynamics CRM instances that use Active Directory authentication.
To resolve the hosts used for Microsoft Dynamics CRM deployment, add the Microsoft Dynamics CRM IP
address and the name to the hosts file.
In Windows 7, you can find the hosts file in the following directory:
C:\Windows\System32\drivers\etc

48

Chapter 5: Connector Administration

Step 3. Editing the Kerberos Configuration File

Edit the Kerberos configuration file for Microsoft Dynamics CRM instances that use Active Directory
authentication.
1.

Open the Kerberos configuration file, krb5.conf, located in the following directory:

2.

Configure the following values in the file:

<SecureAgent_InstallDir>/main/bin/rdtm/javalib/msdcrm/conf
[libdefaults]
default_realm = <fully qualified domain name>
default_tkt_enctypes = rc4-hmac
default_tgs_enctypes = rc4-hmac
permitted_enctypes = rc4-hmac
[realms]
<fully qualified domain name> = {
kdc = <domain controller hostname>.<fully qualified domain name>
default_domain = <fully qualified domain name>
}
[domain_realm]
.<fully qualified domain name> = <fully qualified domain name>

Step 4. Editing the Kerberos Login Configuration File

Edit the Kerberos login configuration file for Microsoft Dynamics CRM instances that use Active Directory
authentication. The Kerberos login configuration file, login.conf, is located in the following directory:
<SecureAgent_InstallDir>\main\bin\rdtm\javalib\msdcrm\conf

If the Microsoft Dynamics CRM server pool identity is set to a specific user account, add the
serverprincipal="<user name>" entry to the file as follows:
spnego-client {
com.sun.security.auth.module.krb5LoginModule required
serverprincipal="<user name>"
storePass=true;
};
The user name is the user account used by the application pool and defined in the Active Directory
properties.

If the Microsoft Dynamics CRM server pool identity is set to a network service, add the
serverprincipal="<URL>" entry to the file as follows:
spnego-client {
com.sun.security.auth.module.krb5LoginModule required
serverprincipal="<URL>"
storePass=true;
};
The URL is the HTTP SPN entry for the Microsoft Dynamics CRM instance.

Step 5. Downloading Java Security Policy Files

Download Java security policy files for Microsoft Dynamics CRM instances that use Active Directory
authentication.
You can download Java security policy files from the following location:
http://www.oracle.com/technetwork/java/javase/downloads/jce-6-download-429243.html.
Unzip the zip package and copy the local_policy.jar and US_export_policy.jar files to the following directory:
<SecureAgent_InstallDir>\jre\lib\security
Overwrite the existing files in the directory.

Microsoft Dynamics CRM Connector Administration

49

NetSuite Connector Administration

Before users can use a NetSuite connection, an administrator must perform the following tasks:
1.

Create a configuration file to associate NetSuite record field names with related NetSuite search record
field names.
This must be done before NetSuite objects can be used as sources in tasks. When a field name in a
NetSuite record matches the related field name in the corresponding SearchBasic search record, users
can define a filter for the field in tasks. When a field name in a record does not match the related search
record field name, users cannot define a filter for the field in tasks.
Users define filters for fields in the following locations:

2.

Data Filters page of the Data Synchronization Task wizard

Query options in a Source transformation in the Mapping Designer

Query options in the Sources page of the Mapping Configuration Task wizard when the source object
in the mapping is parameterized

If necessary, configure the NetSuiteCustomFields.ini file.

Some custom fields in NetSuite custom objects might not appear in Informatica Cloud, particularly
transaction body fields and transaction column fields. If these custom fields are missing, configure the
NetSuiteCustomFields.ini file to ensure that these fields are available in Informatica Cloud.

Step 1. Creating a Configuration File to Map NetSuite Fields

To ensure that users can define filters for NetSuite fields, create a configuration file to map the fields.
1.

Create a text file named RecordToFieldsMap.ini.

2.

Use the following guidelines to configure the RecordToFieldsMap.ini file:

Create a separate section for each NetSuite record.

In each section, list the record field names and related SearchBasic field names, as follows:
[<record 1>]
<record field name>=<SearchBasic field name>
<record field name2>=<SearchBasic field name2>
[<record 2>]
<record field name>=<SearchBasic field name>
<record field name2>=<SearchBasic field name2>
<record field name3>=<SearchBasic field name3>
For example:
[Account]
acctName=name
addr1=address1

3.

Copy the RecordToFieldsMap.ini file to both of the following directories:

<SecureAgent_InstallDir>\main\bin\rdtm\javalib
<SecureAgent_InstallDir>\main\tomcat\plugins

4.

50

Update both files as required. Make sure the files contain matching information.

Chapter 5: Connector Administration

Step 2. Configuring the NetSuiteCustomFields.ini File

If necessary, specify custom NetSuite fields in the NetSuiteCustomFields.ini file so that they are available in
Informatica Cloud.
1.

Make a copy of the NetSuiteCustomFields.ini file, which is located in the following folder:
<SecureAgent_InstallDir>\packages\packageNetsuiteConnector.<version>\package\rdtm\javalib

2.

Modify the file to include custom NetSuite fields following these guidelines:

Create a separate section for each NetSuite record for which you want to add custom fields.

Add the custom fields using the following format, where the value of scriptId is the ID field in the
NetSuite user interface for each custom field:
[<Object Name>]
scriptIds = <custom field name1>,<custom field name2>,<custom field name3>
For example:
[Sales]
scriptIds = discountPrice,salesDescription,salesEvent

3.

Save the NetSuiteCustomFields.ini in the following location:

<SecureAgent_InstallDir>\main\bin\rdtm-extra\reserved\userfiles\netsuite

SAP IDocs and RFCs/BAPI Connector Administration

Before users can use an SAP connection to process data through IDocs or RFCs/BAPIs, the SAP
Administrator must perform the following tasks:
1.

If necessary, download and install the Microsoft Visual C++ Redistributable.

2.

Download and configure the SAP libraries.

3.

Configure the saprfc.ini file.

Step 1. Downloading and Installing the Microsoft Visual C++

Redistributable
If you do not have Microsoft Visual C++ (VC++) installed, download and install the Microsoft Visual C++
redistributable (x86) from the Microsoft website. You can then run applications developed with VC++.
1.

Download and install two versions of the VC++ redistributable.

For more information about this issue from SAP, see SAP Note 684186 on the SAP website:
http://service.sap.com/notes.

SAP IDocs and RFCs/BAPI Connector Administration

51

The following table shows the secure agent system and the related VC++ redistributable versions to
install:
Secure Agent System

VC++ Redistributable Version

Windows 7 64-bit

Microsoft VC++ 2008:

http://www.microsoft.com/en-us/download/details.aspx?id=29
Microsoft VC++ 2010:
http://www.microsoft.com/en-us/download/details.aspx?id=5555

Windows Server 2008 64-bit

Microsoft VC++ 2008:

http://www.microsoft.com/en-us/download/details.aspx?id=29
Microsoft VC++ 2010:
http://www.microsoft.com/en-us/download/details.aspx?id=5555

Windows 7 32-bit or Windows Server

2008 R2 32-bit

Microsoft VC++ 2005:

http://www.microsoft.com/en-us/download/details.aspx?id=14431
Microsoft VC++ 2008:
http://www.microsoft.com/en-us/download/details.aspx?id=29

Linux

Not required.

Verify that your system meets the requirements for each redistributable version you install.
2.

Restart the Secure Agent after installation.

Step 2. Downloading and Configuring SAP Libraries for IDoc and

BAPI/RFC
Download and configure the SAP RFC SDK libraries. Contact Informatica Global Customer Support if you
encounter any issues when you download the libraries.
Note: If you performed this step for an SAP table connection and want to connect to Unicode SAP systems,
you do not need to download and configure the classic RFC SDK 7.2 libraries again. However, if you want to
connect to non-Unicode SAP systems, you must download and configure the classic RFC SDK 7.1 libraries.
1.

Go to the SAP Service Marketplace: http://service.sap.com.

Note: You must have SAP credentials to access the Service Marketplace.

2.

Download the classic RFC SDK libraries for the Secure Agent system.

To connect to Unicode SAP systems, download the classic RFC SDK Unicode 7.2 libraries.

To connect to non-Unicode SAP systems, download the classic RFC SDK non-Unicode 7.1 libraries.

Verify that you download the classic RFC SDK libraries and not the SAP NetWeaver RFC SDK libraries.

52

Chapter 5: Connector Administration

The following table lists the Secure Agent system and the associated service archive (SAR) file for the
RFC SDK Unicode 7.2 libraries and RFC SDK non-Unicode 7.1 libraries:
Secure Agent System

SAP File Name

Windows 64-bit

RFC_10-10009747.SAR

Windows 32-bit

RFC_10-10009746.SAR

Linux 64-bit

RFC_10-10009745.SAR

Linux 32-bit

RFC_10-10009742.SAR

Use the most recent patch available. The SAP file name might vary based on the version.
3.

Use the SAPCAR.exe utility to unzip the SAR file.

4.

Copy the files in the lib directory to the following directory:

<Secure Agent installation directory>\main\bin\rdtm

5.

Set the following permissions for each RFC SDK library:

Read, write, and run permissions for the current user.

Read and run permissions for all other users.

Step 3. Configuring saprfc.ini for IDoc and BAPI/RFC

SAP uses the communications protocol, Remote Function Call (RFC), to communicate with other systems. To
enable the Secure Agent to connect to the SAP system as an RFC client, create and configure saprfc.ini on
the machines that host the Secure Agent.

saprfc.ini Entry Types for IDoc and BAPI/RFC

The SAP connection uses the following types of entries to connect to SAP:
Type A
Type A. For SAP IDoc Writer and BAPI/RFC connections. Connects to an SAP system. Each Type A
entry specifies one SAP system. The following text shows a sample Type A entry:
DEST=sapr3
TYPE=A
ASHOST=sapr3
SYSNR=00
RFC_TRACE=0
Type B
For SAP Table, IDoc Writer, and BAPI/RFC connections. Use a type B entry to enable SAP load
balancing with the SAP message server. The following text shows a sample Type B entry:
DEST=sapr3
TYPE=B
R3NAME=ABV
MSHOST=infamessageserver.informatica.com
GROUP=INFADEV

SAP IDocs and RFCs/BAPI Connector Administration

53

Type R
For SAP IDoc Reader connections only. Connects to an SAP system to receive outbound IDocs. The
following text shows a sample Type R entry:
DEST=sapr346CLSQA
TYPE=R
PROGID=PID_LSRECEIVE
GWHOST=sapr346c
GWSERV=sapgw00
RFC_TRACE=1

saprfc.ini Parameters for IDoc and BAPI/RFC

For SAP IDoc and BAPI/RFC connections, configure the Type A, B, and R entries in saprfc.ini.
The following table describes the saprfc.ini parameters to use for SAP IDoc and BAPI/RFC connections:
saprfc.ini Parameter

Type

Description

DEST

A, B, R

Logical name of the SAP system for the connection.

All DEST entries must be unique. You must have only one DEST
entry for each SAP system.
Use up to 32 characters to define a logical name.

TYPE

A, B, R

Type of connection. Set to A, B, or R.

ASHOST

Host name or IP address of the SAP application. Informatica Cloud

uses this entry to attach to the application server.

SYSNR

SAP system number.

R3NAME

Name of the SAP system.

MSHOST

Host name of the SAP Message Server.

GROUP

Group name of the SAP application server.

PROGID

Program ID. The Program ID must be the same as the Program ID

for the logical system you define in the SAP system to send or
receive IDocs or to consume business content data.

GWHOST

Host name of the SAP gateway.

GWSERV

Server name of the SAP gateway.

RFC_TRACE

A, R

Debugs RFC connection-related problems. 0 is disabled. 1 is

enabled.

The following text shows a sample saprfc.ini:

DEST=SAPR3
TYPE=A
ASHOST=SAPR3
SYSNR=00
DEST=SAPR346CLSQA
TYPE=R
PROGID=PID_LSRECEIVE
GWHOST==sapr346c
GWSERV=sapgw00

54

Chapter 5: Connector Administration

Configuring saprfc.ini for IDoc and RFC/BAPI

Configure the saprfc.ini file for SAP IDoc and RFC/BAPI connections.
1.

Use a DOS editor or WordPad to create the saprfc.ini file.

Notepad can introduce errors to the saprfc.ini file.

2.

In the saprfc.ini file, create an entry for each SAP connection that you want to use.
Create a Type A entry for an IDoc Reader or RFC/BAPI connection type. Create a Type R entry for an
IDoc Writer connection type. Create a Type B entry for load balancing.
If you connect to multiple SAP systems, create appropriate entries for each system with unique DEST
parameters.

3.

Save the file.

4.

Copy saprfc.ini to the following directory for every Secure Agent machine that you want to use:
<SecureAgent_InstallDir>/main/bin/rdtm.

SAP Table Connector Administration

Before users can use an SAP Table connection to process SAP table data, the SAP Administrator must
perform the following tasks:
1.

Download and install the Microsoft Visual C++ redistributable.

2.

Download and configure the SAP libraries.

3.

Configure the saprfc.ini file.

4.

Configure SAP user authorization.

5.

Install transport files.

After the administrator has performed the configuration, users can set up and use an SAP table connection in
data synchronization and mapping configuration tasks.

Step 1. Downloading and Installing the Microsoft Visual C++

Redistributable
If you do not have Microsoft Visual C++ (VC++) installed, download and install the Microsoft Visual C++
redistributable (x86) from the Microsoft website. You can then run applications developed with VC++.
1.

Download and install two versions of the VC++ redistributable.

For more information about this issue from SAP, see SAP Note 684186 on the SAP website:
http://service.sap.com/notes.

SAP Table Connector Administration

55

The following table shows the secure agent system and the related VC++ redistributable versions to
install:
Secure Agent System

VC++ Redistributable Version

Windows 7 64-bit

Microsoft VC++ 2008:

http://www.microsoft.com/en-us/download/details.aspx?id=29
Microsoft VC++ 2010:
http://www.microsoft.com/en-us/download/details.aspx?id=5555

Windows Server 2008 64-bit

Microsoft VC++ 2008:

http://www.microsoft.com/en-us/download/details.aspx?id=29
Microsoft VC++ 2010:
http://www.microsoft.com/en-us/download/details.aspx?id=5555

Windows 7 32-bit or Windows Server

2008 R2 32-bit

Microsoft VC++ 2005:

http://www.microsoft.com/en-us/download/details.aspx?id=14431
Microsoft VC++ 2008:
http://www.microsoft.com/en-us/download/details.aspx?id=29

Linux

Not required.

Verify that your system meets the requirements for each redistributable version you install.
2.

Restart the Secure Agent after installation.

Step 2. Downloading and Configuring the Libraries for Table Read

and Write
Before you can use an SAP Table connection, download and configure the SAP libraries. Install and
configure the SAP libraries on the Secure Agent machine.
The libraries that you use are based on whether you want to read from SAP tables or write to SAP tables.

Downloading and Configuring Libraries to Read from SAP Tables

Download the SAP JCo libraries, configure the PATH system variable, and copy a library to the Secure
Agent. Contact Informatica Global Customer Support if you encounter any issues when you download the
libraries.
1.

Go to the SAP Service Marketplace: http://service.sap.com/connectors.

Note: You will need SAP credentials to access the Service Marketplace.

2.

Download the appropriate installer for 32-bit SAP JCo libraries and unzip the following file:
Secure Agent System

SAP File Name

Windows

sapjco3-NTintel-3.0.11.zip

Linux

sapjco3-linuxintel-3.0.11.tgz

Note: Use the most recent version available.

56

Chapter 5: Connector Administration

3.

Set the PATH environment variable to the location where you unzipped the file.

4.

Copy the sapjco3.jar to the following Secure Agent directories:

<SecureAgent_InstallDir>/main/tomcat/plugins/300620
<SecureAgent_InstallDir>/main/bin/rdtm/javalib
The <agent_install_dir>/main/tomcat/plugins/300620 directory is created after Informatica enables the
SAP Table connector license for the organization.

5.

Restart the Secure Agent.

Downloading and Configuring Libraries to Write to SAP Tables

Download and configure the SAP RFC SDK 7.2 libraries. Contact Informatica Global Customer Support if you
encounter any issues when you download the libraries.
Note: If you performed this step for an SAP IDoc or RFC/BAPI connection, you do not need to do it again.
1.

Go to the SAP Service Marketplace: http://service.sap.com

Note: You must have SAP credentials to access the Service Marketplace.

2.

Download the Classic RFC SDK Unicode 7.2 libraries for the Secure Agent system.
Verify that you use the Classic RFC SDK libraries and not the NetWeaver RFC SDK libraries.
SAP provides the RFC SDK Unicode 7.2 libraries in the following service archive (SAR) files:
Secure Agent System

SAP File Name

Windows 64-bit

RFC_10-10009747.SAR

Windows 32-bit

RFC_10-10009746.SAR

Linux 64-bit

RFC_10-10009745.SAR

Linux 32-bit

RFC_10-10009742.SAR

Use the most recent version available. The SAP file name might vary based on the version.
3.

Use the SAPCAR.exe utility to unzip the SAR file.

4.

Copy the files in the lib directory to the following directory:

<Secure Agent installation directory>\main\bin\rdtm

5.

Set the following permissions for each RFC SDK library:

Read, write, and execute permissions for the current user.

Read and execute permissions for all other users.

SAP Table Connector Administration

57

Step 3. Configuring saprfc.ini for SAP Tables

SAP uses the communications protocol, Remote Function Call (RFC), to communicate with other systems. To
enable the Secure Agent to connect to the SAP system as an RFC client, create and configure saprfc.ini on
the machines that host the Secure Agent.

saprfc.ini Entry Types for SAP Tables

The SAP table connection uses the following types of entries to connect to SAP:
Type A
For all SAP connections. Connects to an SAP system. Each Type A entry specifies one SAP system.
The following text shows a sample Type A entry:
DEST=sapr3
TYPE=A
ASHOST=sapr3
SYSNR=00
RFC_TRACE=0
Type B
For all SAP connections. Enables SAP to create a connection to the application server with the least
load at run time. Use a type B entry to enable SAP load balancing. The following text shows a sample
Type B entry:
DEST=sapr3
TYPE=B
R3NAME=ABV
MSHOST=infamessageserver.informatica.com
GROUP=INFADEV

saprfc.ini Parameters for SAP Tables

For SAP table connections, configure the Type A or Type B entries in saprfc.ini.
The following table describes the saprfc.ini parameters to use for SAP table connections:
saprfc.ini Parameter

Type

Description

DEST

A, B

Logical name of the SAP system for the connection.

All DEST entries must be unique. You must have only one DEST
entry for each SAP system.
Use up to 32 characters to define a logical name.

58

TYPE

A, B

Type of connection. Set to A or B.

ASHOST

A, B

Host name or IP address of the SAP application. Informatica Cloud

uses this entry to attach to the application server.

SYSNR

A, B

SAP system number.

R3NAME

Name of the SAP system.

MSHOST

Host name of the SAP Message Server.

Chapter 5: Connector Administration

saprfc.ini Parameter

Type

Description

GROUP

Group name of the SAP application server.

RFC_TRACE

Debugs RFC connection-related problems. 0 is disabled. 1 is

enabled.

Configuring saprfc.ini for SAP Tables

Configure the saprfc.ini file for SAP Table connections.
1.

Use a DOS editor or WordPad to create the saprfc.ini file.

2.

In saprfc.ini, create an entry for each SAP connection that you want to use.
Create a Type A entry for each system with unique DEST parameters. Create a Type B entry to
configure load balancing.

3.

Save the file.

Configuring the Location of the saprfc.ini File

Save the saprfc.ini file to the Secure Agent machine and configure the RFC_INI environment variable to point
to the file.
1.

For an saprfc.ini file that contains information about a source SAP system, copy the file to a directory
local to each Secure Agent that you want to read from SAP. Repeat this step for every Secure Agent that
you want to read from SAP.

2.

For an saprfc.ini file that contains information about a target SAP system, copy the saprfc.ini file to the
following directory: <SecureAgent_InstallDir>/main/bin/rdtm. Repeat this step for every Secure Agent
that you want to read from SAP.

3.

For each Secure Agent machine that you use, configure the RFC_INI environment variable to point to
the location of the saprfc.ini file.

Step 4. Configuring SAP User Authorization

Configure the SAP user account to process SAP table data.
The following table describes the required authorization to read from SAP tables:
Read Object Name
S_BTCH_JOB

Required Authorization
DELE, LIST, PLAN, SHOW.
Set Job Operation to RELE.

S_PROGRAM

BTCSUBMIT, SUBMIT

S_RFC

SYST, SDTX, SDIFRUNTIME, /INFADI/TBLRDR

S_TABU_DIS

&_SAP_ALL

SAP Table Connector Administration

59

The following table describes the required authorization to write to SAP tables:
Write Object Name

Required Authorization

S_RFC

/INFATRAN/ZPMW

S_TABU_DIS

&_SAP_ALL

Step 5. Installing SAP Table Connection Transport Files

Install the SAP Table connection transport files on the SAP machines that you want to access. Before you
install the transports on your production system, install and test the transports in a development system.
The following table describes the objects included in the transport:
Object Name

Object Type

Description

/INFADI/TABLEACCESS

Package

Namespace for all objects listed below.

/INFADI/TBLRDR

Function
Group

Namespace for the function module.

/INFADI/RFC_READ_TABLES

Function
Module

Function module used to generate a query based on

Informatica Cloud task metadata.
Also used to schedule the program to execute data
extraction.

/INFADI/EXECUTE_DYNQUERY

Program

ABAP/4 program to execute a query and to push data to

Informatica Cloud SAP table connection.
Called in executed sync or async mode.

/INFADI/IMPORTFLDS

Table

Internal structure referenced by the function module.

/INFADI/TABLEDATA

Table

Internal table type referenced by the function module.

Installing Transport Files

Install transport files from a Secure Agent directory to read from a Unicode or non-Unicode SAP system. The
transport files are for SAP version ECC 5.0 or later.
To install transport files for an earlier version or to write to an SAP system, contact Informatica Global
Customer Support.
1.

Find the transport files in the following directory on the Secure Agent machine:
<SecureAgent_InstallDir>\main\bin\rdtm\sap-transport\SAPTableReader.

2.

Copy the cofile transport file to the Cofile directory in the SAP transport management directory on each
SAP machine that you want to access.
The cofile transport file uses the following naming convention: TABLE_READER_K<number>.G00.

3.

Remove "TABLE_READER_" from the file name.

For example, for a cofile transport file named TABLE_READER_K900556.G00, rename the file to
K900556.G00.

4.

60

Copy the data transport file to the Data directory in the SAP transport management directory on each
SAP machine that you want to access.

Chapter 5: Connector Administration

The data transport file uses the following naming convention: TABLE_READER_R<number>.G00.
5.

Remove "TABLE_READER_" from the file name.

6.

To import the transports to SAP, in the STMS, add the transport request to the system queue. To do so,
click Extras > Other Requests > Add.

7.

In the Add Transport Request to Import Queue dialog box, enter the request number for the cofile
transport.
The request number inverts the order of the renamed cofile as follows: G00K<number>.
For example, for a cofile transport file renamed K900556.G00, enter the following request number:
G00K900556.

8.

In the Request area of the import queue, select the select the transport request number that you added,
and click Import.

Siebel Connector Administration

You can use an Informatica Cloud ODBC connection to connect to Siebel. To ensure connectivity, configure
an ODBC connection for Siebel.

Configuring an ODBC Connection for Siebel

1.

On the Secure Agent machine, use the ODBC Administrator to configure a System DSN.

2.

In the Informatica Cloud organization, configure an ODBC connection to use the System DSN and a SQL
authenticated login.

Siebel Connector Administration

61

CHAPTER 6

Object Migration
Object Migration Overview
You can migrate objects from a source organization to a target organization. A source organization is the
organization that contains the object that you want to migrate. The target organization is the organization
where you want to migrate the object.
For example, you might have separate organizations for development, test, and production environments.
You create tasks in the development organization. After task development, you migrate the tasks from the
development organization (the source organization) to the test organization (the target organization). After
you test and validate tasks in the test organization, you then migrate the tasks from the test organization to
the production organization.
You can migrate the following types of objects:

Tasks and task flows

Mappings and mapplets

Integration templates

Connections

Saved queries

If you select tasks or task flows from the source organization, any related objects (tasks, connections,
integration templates, mappings, mapplets, and saved queries) are also selected.

Migration Requirements
Before you migrate an object, ensure you meet the following requirements:

62

You must have at least two organizations registered with Informatica Cloud.

The target organization must have the Migration license.

You have a user account for both organizations.

Your user account in the target organization must have the Admin role.

You have at least one Secure Agent in the target organization.

Migrating an Object
1.

Log in to the Informatica Cloud account of the target organization.

2.

Click Administer > Migrate Objects.

3.

On the Migrate Objects page, click Start Migration.

4.

In the Source Organization area, click Log In.

5.

In the Informatica Cloud Login dialog box, enter the user name and password for the source
organization and click OK.

6.

In the Objects to Migrate area, click Add Objects.

7.

In the Add Objects dialog box, select the type of object to migrate.
All objects of that type display in the Available Objects list.

8.

Move the objects that you want to migrate from the Available Objects list to the Selected Objects list.
You can use the Shift or Ctrl keys to select multiple objects.

9.
10.

To migrate additional objects, repeat steps 7 - 8 for each type of object that you want to migrate.
Click OK.
The Objects to Migrate area displays the selected objects, dependent objects, and related messages.
You can use the Delete icon to remove an object from the list.

11.

To migrate the listed objects, click OK. When a confirmation message displays, click OK again.
A summary of the migration displays when the migration completes.

Post-migration Tasks
Perform the following tasks after you migrate objects:

Schedule tasks and task flows. Schedule information is not migrated with tasks or task flows.

Configure connection passwords and security token after migration. Connection passwords and security
tokens are not migrated.

After you migrate a data replication task, verify the target prefix information.

After you migrate objects, verify the runtime environment. The migration process assigns all connections
to the first available runtime environment in the list of runtime environments in the target organization.

Migration Rules and Guidelines

Consider the following rules and guidelines when you migrate objects:

If you select mapping configuration tasks, integration templates, mappings, or mapplets with the same
names as existing objects in your target organization, you have the option to overwrite the target objects
with the source objects. Other types of tasks, task flows, connections, and saved queries might not be
overwritten.

Mapplets in bundles are not migrated with tasks.

Migrating an Object

63

64

When you migrate an object, the migration includes all dependent objects except for objects installed from
a bundle. In the target organization, you can only see and access the objects with valid licenses.

You can migrate an object that uses objects from a bundle when the target organization has the bundle
installed.

When you select an object for migration more than once, Informatica Cloud migrates an object one time.
For example, if you select a mapping and several tasks based on the mapping, Informatica Cloud
migrates the mapping one time.

Schedule information is not migrated with tasks or task flows.

As a security measure, passwords and security tokens are not migrated with connections.

Informatica Cloud assigns all migrated connections to the first available runtime environment in the list of
runtime environments for the target organization.

When you migrate a data replication task, Informatica Cloud includes target prefix information.

Chapter 6: Object Migration

INDEX

Informatica Global Customer Support

contact information 8

access permissions 41
Admin role 36
audit logs 45
authentication 15

C
Changing organizations 17
Cloud Developer community
URL 7
configuring 32
connections
additional configuration for Microsoft Dynamics CRM 48
configuration for SAP IDoc and RFC/BAPI connections 51
configuration for SAP table connections 51, 55
SAP configuration requirements 60
storing properties 16
connectors 47
custom configuration properties
Secure Agent 28, 30

D
Designer role 37
directories
configuring Secure Agent login to access 25

E
email notification
overview 15
encryption key password
for connection properties 16

I
Informatica Cloud
components 9
license types 18
menus 10
Informatica Cloud Community
URL 7
Informatica Cloud Connectors
installing 47
Informatica Cloud hosting facility
description 9
Informatica Cloud sidebar
description 11
Informatica Cloud web site
URL 7

Java security
for Microsoft Dynamics CRM connections using Active Directory 48
Java security policy files
for Microsoft Dynamics CRM connections using Active Directory 49

K
Kerberos configuration file
for Microsoft Dynamics CRM connections using Active Directory 49
Kerberos login configuration file
for Microsoft Dynamics CRM connections using Active Directory 49

L
libraries
to read from and write to SAP tables 56
to read from SAP tables 56
to write to SAP tables 57
license types
overview 18
licenses
editing sub-organization licenses 19
expiration 20
management 17
Org Hierarchy license 19
sub-organizations 19
types 18
Linux
configuring proxy settings 27
Secure Agent installation 27
starting and stopping the Secure Agent 34
uninstalling the Secure Agent 28
Live Chat
access 11

M
Main page
description 10
Microsoft Dynamics CRM
additional configuration for Active Directory 48
configuring Java security Active Directory 48
configuring the Kerberos configuration file for Active Directory 49
configuring the Kerberos login configuration file for Active Directory
49
downloading Java security policy files for Active Directory 49
resolving hosts for Active Directory 48

65

migration
objects 63
of objects between organizations 62
requirements 62
rules and guidelines 63
Minimum Character Mix
organization property 15

N
NetSuite
administration 50
configuration for custom NetSuite fields 50
configuration for search record field names 50
filters 50

O
object migration 62
object-level permissions
overview 40
ODBC
connecting to Siebel 61
organization hierarchy
creating a sub-organization 17
linking an organization as a sub-organization 17
overview 16
organization security
overview 35
organizations
authentication 15
changing within an organization hierarchy 17
creating 14
creating a sub-organization 17
license expiration 20
linking an organization as a sub-organization 17
storing connection properties 16

P
passwords
expiration 15
restrictions 15
permissions
configuring for a user group 38
configuring for individual objects 41
for individual objects 40
overview 39
required to perform tasks 41
rules and guidelines 41
privileges
description 36
proxy settings
configuring on Linux 27
configuring on Windows 24

R
registering
Secure Agent on Linux 27
requirements
Secure Agent 22
resolving hosts
for Microsoft Dynamics CRM connections using Active Directory 48

66

Index

roles
Admin 36
best practices 41
Designer 37
overview 36
rules and guidelines 41
Service Consumer 37
runtime environments
adding and removing Secure Agents 32
assigning more than one Secure Agent 22
assigning Secure Agents 32
configuring 32

S
SAP
additional configuration for IDocs and RFC/BAPI connection types
51
additional configuration for SAP table connections 51, 55
installing transport files for processing table data 60
SAP libraries
for SAP IDoc and RFC/BAPI connections 51, 52, 55
to read from and write to SAP tables 56
to read from SAP tables 56
to write to SAP tables 57
SAP user authorization
configuring to process table data 59
saprfc.ini
configuring for IDoc and RFC/BAPI 55
configuring for SAP IDoc and BAPI/RFCI 53
configuring for SAP tables 58, 59
entry types for IDoc and RFC/BAPI 53
entry types for SAP tables 58
parameters for IDoc and RFC/BAPI 54
parameters for SAP tables 58
Secure Agent
description 9
downloading 32
storing connection properties 16
Secure Agent Manager
stopping and restarting the Secure Agent 33
Secure Agents
custom configuration properties 28, 30
assigning to runtime environments 32
configuring a Windows service login 25
deleting 34
downloading 23
installing and registering on Linux 27
installing on Windows 24
IP address ranges for firewall access 23
overview 21
requirements 22
rules and guidelines 33
starting and stopping on Linux 34
stopping and restarting on Windows 33
uninstalling on Linux 28
uninstalling on Windows 25
view details, refresh status 31
viewing history 32
viewing status on Linux 31
security
two-factor authentication 15
Service Consumer role 37
sidebar
Informatica Cloud 11
Siebel
configuring connection through ODBC 61

sub-organizations
creating 17
editing licenses 19
in an organization hierarchy 16
job limits 19
license expiration 20
licenses 19
linking an existing organization 17

T
time zones
associating with a user 44
in email notification 15
trust site
description 8
two-factor authentication
description 15

U
user groups
best practices 41
configuring 38
deleting 38
object-level permissions 40

user groups (continued)

overview 37
rules and guidelines 41
viewing details 38
users
configuring 44
deleting 44
overview 42
properties 42
viewing details 44

V
viewing
Secure Agent status 31
user details 44
user group details 38

W
Windows
configuring proxy settings 24
Windows service
configuring Secure Agent login 25

Index

67