Installation Guide For Weblogic: Informatica MDM Multidomain Edition For Oracle (Version 10.1.0)

Informatica MDM Multidomain Edition for
Oracle (Version 10.1.0)
Installation Guide for

WebLogic
Informatica MDM Multidomain Edition for Oracle Installation Guide for WebLogic
Version 10.1.0
December 2015
Copyright (c) 1993-2015 Informatica LLC. All rights reserved.
This software and documentation contain proprietary information of Informatica LLC and are provided under a license agreement containing restrictions on use and
disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any
form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica LLC. This Software may be protected by U.S. and/or
international Patents and other Patents Pending.
Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as
provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013©(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14
(ALT III), as applicable.
The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us
in writing.
Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange,
PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica
On Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and
Informatica Master Data Management are trademarks or registered trademarks of Informatica LLC in the United States and in jurisdictions throughout the world. All
other company and product names may be trade names or trademarks of their respective owners.
Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights
reserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All rights
reserved.Copyright © Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright © Meta
Integration Technology, Inc. All rights reserved. Copyright © Intalio. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © Adobe Systems
Incorporated. All rights reserved. Copyright © DataArt, Inc. All rights reserved. Copyright © ComponentSource. All rights reserved. Copyright © Microsoft Corporation. All
rights reserved. Copyright © Rogue Wave Software, Inc. All rights reserved. Copyright © Teradata Corporation. All rights reserved. Copyright © Yahoo! Inc. All rights
reserved. Copyright © Glyph & Cog, LLC. All rights reserved. Copyright © Thinkmap, Inc. All rights reserved. Copyright © Clearpace Software Limited. All rights
reserved. Copyright © Information Builders, Inc. All rights reserved. Copyright © OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved.
Copyright Cleo Communications, Inc. All rights reserved. Copyright © International Organization for Standardization 1986. All rights reserved. Copyright © ej-
technologies GmbH. All rights reserved. Copyright © Jaspersoft Corporation. All rights reserved. Copyright © International Business Machines Corporation. All rights
reserved. Copyright © yWorks GmbH. All rights reserved. Copyright © Lucent Technologies. All rights reserved. Copyright (c) University of Toronto. All rights reserved.
Copyright © Daniel Veillard. All rights reserved. Copyright © Unicode, Inc. Copyright IBM Corp. All rights reserved. Copyright © MicroQuill Software Publishing, Inc. All
rights reserved. Copyright © PassMark Software Pty Ltd. All rights reserved. Copyright © LogiXML, Inc. All rights reserved. Copyright © 2003-2010 Lorenzi Davide, All
rights reserved. Copyright © Red Hat, Inc. All rights reserved. Copyright © The Board of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright
© EMC Corporation. All rights reserved. Copyright © Flexera Software. All rights reserved. Copyright © Jinfonet Software. All rights reserved. Copyright © Apple Inc. All
rights reserved. Copyright © Telerik Inc. All rights reserved. Copyright © BEA Systems. All rights reserved. Copyright © PDFlib GmbH. All rights reserved. Copyright ©
Orientation in Objects GmbH. All rights reserved. Copyright © Tanuki Software, Ltd. All rights reserved. Copyright © Ricebridge. All rights reserved. Copyright © Sencha,
Inc. All rights reserved. Copyright © Scalable Systems, Inc. All rights reserved. Copyright © jQWidgets. All rights reserved. Copyright © Tableau Software, Inc. All rights
reserved. Copyright© MaxMind, Inc. All Rights Reserved. Copyright © TMate Software s.r.o. All rights reserved. Copyright © MapR Technologies Inc. All rights reserved.
Copyright © Amazon Corporate LLC. All rights reserved. Copyright © Highsoft. All rights reserved. Copyright © Python Software Foundation. All rights reserved.
Copyright © BeOpen.com. All rights reserved. Copyright © CNRI. All rights reserved.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and/or other software which is licensed under various versions
of the Apache License (the "License"). You may obtain a copy of these Licenses at http://www.apache.org/licenses/. Unless required by applicable law or agreed to in
writing, software distributed under these Licenses is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied. See the Licenses for the specific language governing permissions and limitations under the Licenses.
This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software
copyright © 1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under various versions of the GNU Lesser General Public License
Agreement, which may be found at http:// www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any
kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose.
The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California,
Irvine, and Vanderbilt University, Copyright (©) 1993-2006, all rights reserved.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and
redistribution of this software is subject to terms available at http://www.openssl.org and http://www.openssl.org/source/license.html.
This product includes Curl software which is Copyright 1996-2013, Daniel Stenberg, <daniel@haxx.se>. All Rights Reserved. Permissions and limitations regarding this
software are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software for any purpose with or
without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
The product includes software copyright 2001-2005 (©) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms
available at http://www.dom4j.org/ license.html.
The product includes software copyright © 2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to
terms available at http://dojotoolkit.org/license.
This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations
regarding this software are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/license.html.
This product includes software copyright © 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at
http:// www.gnu.org/software/ kawa/Software-License.html.
This product includes OSSP UUID software which is Copyright © 2002 Ralf S. Engelschall, Copyright © 2002 The OSSP Project Copyright © 2002 Cable & Wireless
Deutschland. Permissions and limitations regarding this software are subject to terms available at http://www.opensource.org/licenses/mit-license.php.
This product includes software developed by Boost (http://www.boost.org/) or under the Boost software license. Permissions and limitations regarding this software are
subject to terms available at http:/ /www.boost.org/LICENSE_1_0.txt.
This product includes software copyright © 1997-2007 University of Cambridge. Permissions and limitations regarding this software are subject to terms available at
http:// www.pcre.org/license.txt.
This product includes software copyright © 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms
available at http:// www.eclipse.org/org/documents/epl-v10.php and at http://www.eclipse.org/org/documents/edl-v10.php.
This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?License, http://
www.stlport.org/doc/ license.html, http://asm.ow2.org/license.html, http://www.cryptix.org/LICENSE.TXT, http://hsqldb.org/web/hsqlLicense.html, http://
httpunit.sourceforge.net/doc/ license.html, http://jung.sourceforge.net/license.txt , http://www.gzip.org/zlib/zlib_license.html, http://www.openldap.org/software/release/
license.html, http://www.libssh2.org, http://slf4j.org/license.html, http://www.sente.ch/software/OpenSourceLicense.html, http://fusesource.com/downloads/license-
agreements/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/krb5-
current/doc/mitK5license.html; http://jibx.sourceforge.net/jibx-license.html; https://github.com/lyokato/libgeohash/blob/master/LICENSE; https://github.com/hjiang/jsonxx/
blob/master/LICENSE; https://code.google.com/p/lz4/; https://github.com/jedisct1/libsodium/blob/master/LICENSE; http://one-jar.sourceforge.net/index.php?
page=documents&file=license; https://github.com/EsotericSoftware/kryo/blob/master/license.txt; http://www.scala-lang.org/license.html; https://github.com/tinkerpop/
blueprints/blob/master/LICENSE.txt; http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html; https://aws.amazon.com/asl/; https://github.com/
twbs/bootstrap/blob/master/LICENSE; and https://sourceforge.net/p/xmlunit/code/HEAD/tree/trunk/LICENSE.txt.
This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and Distribution
License (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php), the Sun Binary Code License
Agreement Supplemental License Terms, the BSD License (http:// www.opensource.org/licenses/bsd-license.php), the new BSD License (http://opensource.org/
licenses/BSD-3-Clause), the MIT License (http://www.opensource.org/licenses/mit-license.php), the Artistic License (http://www.opensource.org/licenses/artistic-
license-1.0) and the Initial Developer’s Public License Version 1.0 (http://www.firebirdsql.org/en/initial-developer-s-public-license-version-1-0/).
This product includes software copyright © 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this
software are subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab.
For further information please visit http://www.extreme.indiana.edu/.
This product includes software Copyright (c) 2013 Frank Balluffi and Markus Moeller. All rights reserved. Permissions and limitations regarding this software are subject
to terms of the MIT license.
See patents at https://www.informatica.com/legal/patents.html.
DISCLAIMER: Informatica LLC provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied
warranties of noninfringement, merchantability, or use for a particular purpose. Informatica LLC does not warrant that this software or documentation is error free. The
information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is
subject to change at any time without notice.
NOTICES
This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software
Corporation ("DataDirect") which are subject to the following terms and conditions:
1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT
INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT
LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.
Part Number: MDM-OIG-10100-0002

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Informatica My Support Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Informatica Product Availability Matrixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Informatica Support YouTube Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Informatica Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Informatica Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 1: Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

MDM Multidomain Edition Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Designing the MDM Hub Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Chapter 2: Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Read the Release Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Extract the Installer Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Verify License Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Verify the Minimum System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Set Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Set the Operating System Locale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Set Up the X Window Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Install and Configure Oracle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Disable the Oracle Recycle Bin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Set the NLS_LANG Environment Variable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Configure the init.ora Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Create an Oracle Database Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Create Tablespaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Grant Privileges to DBA User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Add the Oracle TNS Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Test the Database Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Install and Configure Oracle RAC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Use Oracle Service Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Use Oracle RAC Load-Balanced Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Configure the tnsnames.ora File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Install and Configure WebLogic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4 Table of Contents
Create a WebLogic Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Configuring the HTTPS Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Configure WebLogic to Use an Oracle Data Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Create a Master Data Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Create an Operational Reference Store Data Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Configure WebLogic for Multiple MDM Hub Master Databases. . . . . . . . . . . . . . . . . . . . . . 30
Configure WebLogic for Informatica Data Director. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Install and Configure External Cleanse Engines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Determine the Timeline Granularity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Configure the Informatica Platform Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Sample Informatica Platform Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Create an Installation Documentation Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Chapter 3: ActiveVOS Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

ActiveVOS Pre-Installation Tasks Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Create an Informatica ActiveVOS Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Create an Administrative User in WebLogic Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Chapter 4: Hub Store Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Create the MDM Hub Master Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Create an Operational Reference Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Import the Metadata into the MDM Hub Master Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Import the Metadata into the Operational Reference Store. . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Chapter 5: Hub Store Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Verify Access to Oracle Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Chapter 6: Hub Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Installing the Hub Server in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Installing the Hub Server in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Installing the Hub Server in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Configuring the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Sample Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Installing the Hub Server on Environments with Managed Servers. . . . . . . . . . . . . . . . . . . . . . 68
Chapter 7: Hub Server Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Copy the Installation Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Installation Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Installation Prerequisites Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Debug Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Post-Installation Setup Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Hub Server Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Table of Contents 5
WebLogic Server Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Verify the Version and Build Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Configure the Hub Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Configuring the Logging Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Setting the Configuration Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Deploying the Hub Server EAR File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Changing the WebLogic Server Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Configure the Hub Server on Environments with Managed Servers. . . . . . . . . . . . . . . . . . . . . . 77
Configuring the Hub Server Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Repackaging the Hub Server EAR File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Deploying the Hub Server Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Running the Post Install Script Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Manually Redeploying the Hub Server Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Manually Creating Data Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Manually Configuring JMS Message Queues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Step 1. Create a JMS Server and Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Step 2. Configure a Connection Factory for the Module. . . . . . . . . . . . . . . . . . . . . . . . . . 84
Step 3. Add Message Queues to the Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Step 4. Create a Subdeployment Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Step 5. Add a Message Queue Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Step 6. Add a Message Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Improve API Performance on JBoss AS 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Configure WebLogic for Secure ActiveVOS Communication. . . . . . . . . . . . . . . . . . . . . . . . . . 87
Changing the Operational Reference Store User Password. . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Repackaging Custom JAR Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Restart WebLogic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Configure JBoss Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Configure Logging for Informatica Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Starting the Hub Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Registering an Operational Reference Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Chapter 8: Process Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Installing the Process Server in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Installing the Process Server in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Installing the Process Server in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Configuring the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Sample Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Installing the Process Server on Environments with Managed Servers. . . . . . . . . . . . . . . . . . . 101
Chapter 9: Process Server Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Copy the Installation Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Installation Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
6 Table of Contents
Post-Installation Setup Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Process Server Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Debug Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Installation Prerequisites Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
WebLogic Server Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Verify the Version and Build Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Configure the Process Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Deploying the Process Server EAR File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Configuring the Process Server with Cleanse Engines. . . . . . . . . . . . . . . . . . . . . . . . . . 107
Configuring the Process Server to Delete Temporary Files. . . . . . . . . . . . . . . . . . . . . . . 107
Configuring the Logging Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Configuring the Process Server Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Running the PostInstallSetup Script Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Manually Redeploying the Process Server EAR File . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Configure the Process Server on Environments with Managed Servers. . . . . . . . . . . . . . . . . . 108
Configuring the Process Server Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Repackaging the Process Server EAR File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Deploying the Process Server Application on a WebLogic Cluster. . . . . . . . . . . . . . . . . . . 109
Configure Process Server for Multithreading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Configuring the Process Server for Multithreading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Configuring Multiple Process Servers for Cleanse and Match Operations. . . . . . . . . . . . . . . . . 112
Configuring Multiple Process Servers for Batch Processes. . . . . . . . . . . . . . . . . . . . . . . . . . 113
Configure Match Population. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Enabling Match Population. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Chapter 10: ActiveVOS Post-Installation Tasks for the Application Server. . . . . 116
Create a Trusted User in WebLogic Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Configure WebLogic for Secure ActiveVOS Communication. . . . . . . . . . . . . . . . . . . . . . . . . 117
Editing the Default Security Realm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Adding ActiveVOS Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Creating Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Adding Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Editing the abTaskClient Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Chapter 11: ActiveVOS Post-Installation Tasks for the Business Entity

Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
ActiveVOS Web Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Configuring the ActiveVOS URNs for the Business Entity Workflow Adapter. . . . . . . . . . . . . . . 121
Set the ActiveVOS Protocol to HTTPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Configure Task Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Configure Task Triggers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Setting the Default Approval Workflow for the Entity 360 Framework. . . . . . . . . . . . . . . . . . . . 123
Configure the Primary Workflow Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Table of Contents 7
Generating Business Entity and Business Entity Services Configuration Files. . . . . . . . . . . . . . 125
Configure the MDM Identity Services for ActiveVOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Chapter 12: Resource Kit Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Setting Up the MDM Hub Sample Operational Reference Store. . . . . . . . . . . . . . . . . . . . . . . 126
Registering the Informatica MDM Hub Sample Operational Reference Store. . . . . . . . . . . . . . . 129
Installing the Resource Kit in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Installing the Resource Kit in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Installing the Resource Kit in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Configuring the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Sample Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Chapter 13: Troubleshooting the MDM Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Troubleshooting the Installation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Chapter 14: Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Uninstallation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Uninstalling the Hub Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Uninstalling the Process Server in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Uninstalling the Process Server in Graphical Mode On UNIX. . . . . . . . . . . . . . . . . . . . . . 144
Uninstalling the Process Server in Graphical Mode On Windows. . . . . . . . . . . . . . . . . . . 144
Uninstalling the Hub Server in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Uninstalling the Hub Server in Graphical Mode on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . 145
Uninstalling the Hub Server in Graphical Mode on Windows. . . . . . . . . . . . . . . . . . . . . . 145
Uninstalling the Resource Kit in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Uninstalling the Resource Kit in Graphical Mode on UNIX. . . . . . . . . . . . . . . . . . . . . . . . 145
Uninstalling the Resource Kit in Graphical Mode on Windows. . . . . . . . . . . . . . . . . . . . . 146
Uninstalling the Process Server in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Uninstalling the Hub Server in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Uninstalling the Resource Kit in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Manually Undeploying the Process Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Manually Undeploying the Hub Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Appendix A: Installation and Configuration Checklist. . . . . . . . . . . . . . . . . . . . . . . . 148

Installation Checklist Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Step 1. Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Step 2. Create the Hub Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Step 3. Install the Hub Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Step 4. Hub Server Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Step 5. Install the Process Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Step 6. Process Server Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Step 7. Install the Resource Kit (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
8 Table of Contents
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Table of Contents 9
Preface
The Informatica MDM Multidomain Edition Installation Guide is written for database administrators, system
administrators, and implementers who are responsible for installing and setting up the Informatica MDM Hub.
This guide assumes that you have knowledge of operating systems, database environments, and your
application server.
Informatica Resources
Informatica My Support Portal

As an Informatica customer, the first step in reaching out to Informatica is through the Informatica My Support
Portal at https://mysupport.informatica.com. The My Support Portal is the largest online data integration
collaboration platform with over 100,000 Informatica customers and partners worldwide.
As a member, you can:
• Access all of your Informatica resources in one place.

• Review your support cases.
• Search the Knowledge Base, find product documentation, access how-to documents, and watch support
videos.
• Find your local Informatica User Group Network and collaborate with your peers.
Informatica Documentation
The Informatica Documentation team makes every effort to create accurate, usable documentation. If you
have questions, comments, or ideas about this documentation, contact the Informatica Documentation team
through email at infa_documentation@informatica.com. We will use your feedback to improve our
documentation. Let us know if we can contact you regarding your comments.
The Documentation team updates documentation as needed. To get the latest documentation for your
product, navigate to Product Documentation from https://mysupport.informatica.com.
Informatica Product Availability Matrixes

Product Availability Matrixes (PAMs) indicate the versions of operating systems, databases, and other types
of data sources and targets that a product release supports. You can access the PAMs on the Informatica My
Support Portal at https://mysupport.informatica.com/community/my-support/product-availability-matrices.
10
Informatica Web Site
You can access the Informatica corporate web site at https://www.informatica.com. The site contains
information about Informatica, its background, upcoming events, and sales offices. You will also find product
and partner information. The services area of the site includes important information about technical support,
training and education, and implementation services.
Informatica How-To Library

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

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

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

You can contact a Customer Support Center by telephone or through the Online Support.
Online Support requires a user name and password. You can request a user name and password at
http://mysupport.informatica.com.
Preface 11
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/.
12 Preface
CHAPTER 1
Installation Overview
This chapter includes the following topics:
• MDM Multidomain Edition Installation, 13

• Installation Tasks, 15
• Designing the MDM Hub Installation, 15
MDM Multidomain Edition Installation

MDM Multidomain Edition is a master data management solution that enhances data reliability and data
maintenance procedures. The MDM Multidomain Edition is also referred to as the MDM Hub. You can access
the MDM Hub features through the Hub Console.
The MDM Hub installation consists of the following components:
Hub Store
The Hub Store stores and consolidates business data for the MDM Hub. The Hub Store consists of the
following components:
• MDM Hub Master Database. Contains the MDM Hub environment configuration settings, such as user
accounts, security configuration, Operational Reference Store registry, and message queue settings.
The Hub Store consists of one or more MDM Hub Master Databases. You can access and manage
an Operational Reference Store from an MDM Hub Master Database. The default name of an MDM
Hub Master Database is CMX_SYSTEM.
• Operational Reference Store. Contains the master data, content metadata, and the rules to process
and manage the master data. You can configure separate Operational Reference Store databases for
different geographies, different organizational departments, and for the development and production
environments. You can distribute Operational Reference Store databases across multiple server
machines. The default name of an Operational Reference Store is CMX_ORS.
Hub Server
The Hub Server is a J2EE application that you must deploy on an application server. The Hub Server
processes data within the Hub Store and integrates the MDM Hub with external applications. The Hub
Server is the run-time component that manages core and common services for the MDM Hub.
Process Server
The Process Server processes batch jobs such as load, recalculate BVT, and re-validate, and performs
data cleansing and match operations. The Process Server is deployed in an application server
13
environment. The Process Server interfaces with the cleanse engine that you configure to standardize
and optimize data for match and consolidation.
Resource Kit
The Resource Kit is a set of samples, applications, and utilities to integrate the MDM Hub into your
applications and workflows. You can select the Resource Kit components that you want to install.
Informatica Data Director

Informatica Data Director (IDD) is a data governance tool. Use Informatica Data Director to access the
master data that is stored in an Informatica MDM Hub Store. Master data is organized by business
entities. Business entities can be any type of top-level data that has significance for an organization,
such as customers, suppliers, employees, or accounts. The master data represents the best version of
the truth that the organization can achieve about the business entities
Provisioning Tool
You can use the Provisioning tool to create business entity models and configure the Entity 360
framework for Informatica Data Director. To create a business entity model, you create a root node and
then establish relationships between nodes. These relationships are based on foreign key constraints
that you define using the Hub Console. After you build the business entity model and configure the
nodes, you can publish the configuration to the MDM Hub.
Informatica Platform
Comprises the Informatica services and Informatica clients that you use to perform Informatica platform
staging. The Informatica services consist of services to support the domain and application services to
perform tasks and manage databases. The Informatica domain is the administrative unit for the
Informatica environment. You use the clients to access the services in the domain. When you install the
Informatica platform as part of the MDM Hub installation, you install the Data Integration Service, Model
Repository Service, and Informatica Developer (the Developer tool).
Dynamic Data Masking
Dynamic Data Masking is a data security product that operates between the MDM Hub and a database
to prevent unauthorized access to sensitive information. Dynamic Data Masking intercepts requests sent
to the database and applies data masking rules to the request to mask the data before it is sent back to
the MDM Hub.
Informatica ActiveVOS
Informatica ActiveVOS is a business process management (BPM) tool. BPM tools support automated
business processes, including change-approval processes for data. When you combine Informatica
ActiveVOS with the MDM Hub and Informatica Data Director, you ensure that changes to master data
undergo a review-and-approval process before the data is included in the best version of the truth (BVT)
records. When you install ActiveVOS Server as part of the Hub Server installation, you install the
ActiveVOS Server, ActiveVOS Console, and Process Central. You also install predefined MDM
workflows, tasks, and roles.
14 Chapter 1: Installation Overview

Installation Tasks
You must complete the pre-installation tasks before you install the MDM Hub components. After the
installation, complete the post-installation tasks.
To install the MDM Hub, complete the following tasks:
1. Complete the pre-installation tasks. Complete the pre-installation tasks to ensure that you can
successfully run the installers for the Hub Server and the Process Server and create the Hub Store.
2. Create the following Hub Store components:
• MDM Hub Master Database. You must create the MDM Hub Master Database before you install the
Hub Server and the Process Server.
• Operational Reference Store. You can create Operational Reference Stores at any time after you
complete the pre-installation tasks.
Use the setup script provided with the MDM Hub distribution to create the components of the Hub Store.
3. Install the Hub Server. Use the MDM Hub installer to install the Hub Server.
4. Install the Process Server. Use the MDM Hub installer to install the Process Server.
5. Perform the post-installation configuration tasks. Test the database connections. To ensure that you can
use the MDM Hub features, configure the Hub Server and the Process Server.
Designing the MDM Hub Installation

Before you install the MDM Hub, you must decide how to set up the components of the Informatica MDM Hub
implementation. All the components of the MDM Hub implementation must have the same version. If you
have multiple versions of the MDM Hub, install each version in a separate environment.
You can install the MDM Hub in multiple environments, such as development, test, and production. The
requirements and priorities for each type of environment is unique. Therefore, the installation design differs
for each environment.
The following examples show some ways in which the MDM Hub components can be set up in an MDM Hub
implementation:
All components on a single host

You can install all the MDM Hub components on a single host machine. This environment simplifies
communication among the components.
Installation Tasks 15
The following figure shows all MDM Hub components installed on a single host:
Components distributed on multiple hosts

You can distribute the installation of the MDM Hub components on multiple host machines.
The following figure shows a distributed installation of the MDM Hub components:
16 Chapter 1: Installation Overview

CHAPTER 2
Pre-Installation Tasks
• Read the Release Notes, 17

• Extract the Installer Files, 17
• Verify License Key, 18
• Verify the Minimum System Requirements, 18
• Set Environment Variables, 19
• Set the Operating System Locale, 19
• Set Up the X Window Server, 19
• Install and Configure Oracle, 20
• Install and Configure Oracle RAC, 23
• Install and Configure WebLogic, 24
• Install and Configure External Cleanse Engines, 30
• Determine the Timeline Granularity, 30
• Configure the Informatica Platform Properties File, 32
• Create an Installation Documentation Directory, 44
Read the Release Notes

For updates to the installation and upgrade process, read the Informatica MDM Multidomain Edition Release
Notes. You can also find information about known and fixed limitations for the release.
Extract the Installer Files

The installer files are compressed and distributed.
You need to extract the installer files. Verify that the utility that you use for extraction also extracts empty
folders.
17
Download and extract the following installation files from the Informatica Electronic Software Download site to
a directory on your machine:
• Download and extract the MDM Hub installer for your operating system.
• Download and extract the database files.
• If you intend to install the licensed version of ActiveVOS Server, download and extract the ActiveVOS
Server installer for your operating system.
• If you intend to install Informatica platform, download the Informatica platform server installation files for
your operating system.
• If you intend to install Informatica platform, download the Informatica platform client installation files.
Verify License Key

Before you install the software, verify that you have the license key. You can get the license key in the
following ways:
• Installation DVD. If you receive the Informatica installation files in a DVD, the license key file is included in
the Informatica License Key CD.
• FTP download. If you download the Informatica installation files from the Informatica Electronic Software
Download (ESD) site, the license key is in an email message from Informatica. Copy the license key file to
a directory accessible to the user account that installs the product.
Contact Informatica Global Customer Support if you do not have a license key.
Verify the Minimum System Requirements

Before you install the MDM Hub, verify that the machine meets the hardware and software requirements.
Verify that the machine meets the following minimum system requirements to install the MDM Hub
components:
RAM
Production environment: 12 GB
Development environment: 2 GB minimum, 4 GB recommended
Disk Space
1 GB
To verify that you have sufficient physical memory available to meet the run-time needs of the MDM Hub
components that you intend to install, use the following formula:
Total MDM Hub components run-time memory requirement = JDK JVM max heap size of the
application server + operating system native heap size
The hardware requirements for an MDM Multidomain Edition implementation are dependent on the data,
processing volumes, and business rules.
For more information about product requirements and supported platforms, see the Product Availability Matrix
on the Informatica My Support Portal:
https://mysupport.informatica.com/community/my-support/product-availability-matrices
18 Chapter 2: Pre-Installation Tasks

Set Environment Variables
Set the environment variables before you install the MDM Hub.
You must set JAVA_HOME and PATH environment variables to point to JDK 1.7.0_45 or later.
If you want to install Informatica platform on AIX or HP-UX, set the INFA_JDK_HOME environment variable
to point to the JDK directory.
Set the Operating System Locale

You must set the same operating system locale for the Hub Server, the Hub Store, and the Hub Console.
Choose one of the following locales for the MDM Hub components:
• en_US
• fr_FR
• de_DE
• ja_JP
• ko_KR
• zh_CN
• ES
• pt_BR
Set Up the X Window Server

To run the installer in graphical mode, use a graphics display server. If you are logged in remotely to a UNIX
machine, you can use an X Window server to redirect the graphics display to your local host.
If you do not have a display device installed on the machine where you want to install the product, you can
run the installer by using an X Window server installed on another machine. Use the DISPLAY variable to
redirect output of the X Window to another machine that has X Window and xterm installed.
The following table lists the commands to set the DISPLAY environment variable:
Shell Command
C setenv DISPLAY <host name>:0
Bash/Korn export DISPLAY=<host name>:0
Bourne DISPLAY=<host name>:0

export display
If you do not know the host name of the machine that has the X Window server that you want to use, ask
your network administrator. You can also use the IP address of the machine. For more information about
redirecting the DISPLAY variable, see the documentation from the UNIX or X Window vendor.
Set Environment Variables 19

If the X Window server does not support the font that the installer uses, the installer displays the labels on the
buttons incorrectly.
Install and Configure Oracle

You must install and configure Oracle before you create the Hub Store. Install Oracle according to
instructions in the Oracle documentation.
Ensure that you install JServer JAVA Virtual Machine and Oracle Database Java Packages during the Oracle
database installation.
Note: You cannot use a multitenant container database for the MDM Hub. If you use Oracle 12c, ensure that
the Oracle Database setting OPTIMIZER_ADAPTIVE_FEATURES is set to FALSE.
You must install the following software on every machine on which you will run the Hub Server or Process
Server:
• Oracle client
• Oracle Java utilities
• SQL*Loader
Before you start Oracle, perform the following configuration tasks:
• Disable the Oracle Recycle Bin

• Configure the init.ora Parameters
Disable the Oracle Recycle Bin

You must disable the Oracle Recycle Bin because it can interfere with the MDM Hub processes.
The Oracle Recycle Bin is enabled by default. Disable the Oracle Recycle Bins, USER_RECYCLEBIN and
DBA_RECYCLEBIN. You can disable the recycle bins at the system or session level. Also, ensure that you
purge existing objects in the recycle bin.
For more information, see the Oracle documentation.
Set the NLS_LANG Environment Variable

Set the NLS_LANG environment variable for the environment in which the client applications, such as the
Oracle loader, the Hub Server, and the Process Server, run. The NLS_LANG environment variable specifies
the correct locale behavior for Oracle. NLS_LANG sets the language, territory, and character set that the
client applications use.
Specify the NLS_LANG parameter in the following format:

NLS_LANG = language_territory.charset
For example, in a Linux environment that uses French, the NLS_LANG parameter is NLS_LANG =
French_France.UTF8. The language is French, the territory is France, and the character set is UTF8. For
more information about NLS_LANG settings, see the Oracle documentation.
Note: If you want to store and search for records that contain Chinese, Japanese, or Korean characters,
ensure that you set the character set to UTF-8.

Specifying the NLS_LANG Value On UNIX
You can specify the value of NLS_LANG on a UNIX C shell session.
1. On the UNIX terminal, change to the C shell.

2. To specify the value of NLS_LANG, enter the following command:
% export NLS_LANG <language>_<territory>.<charset>
Specifying the NLS_LANG Value On Windows

You can specify the value of NLS_LANG on the Windows environment.
1. Navigate to Control Panel > System > Advanced system settings.

2. In the System Properties dialog box, click the Advanced tab.
3. Click Environment Variables.
The Environment Variables dialog box appears.
4. Click New.
The New System Variable dialog box appears.
5. In the Variable Name field, enter NLS_LANG.
6. In the Variable Value field, enter the NLS_LANG value.
The format for the NLS_LANG value is <language>_<territory>.<charset>.
Configure the init.ora Parameters

You must configure the init.ora parameters for the production environment of the MDM Hub installation.
Create an Oracle Database Instance

After you install and configure the Oracle database, create an Oracle database instance.
If the MDM Hub will have multiple Operational Reference Stores distributed across different host servers,
create an Oracle database instance on each server.
Create Tablespaces
You must create the CMX_DATA, CMX_INDX, CMX_TEMP tablespaces for the Hub Store.
The following table describes the Oracle tablespaces for the Hub Store:
Default Tablespace Name Description
CMX_DATA Default tablespace for the Operational Reference Store schema.

Important: Do not change the default tablespace name of CMX_DATA for your
Hub Store.
CMX_INDX Tablespace to contain indexes that the MDM Hub creates and uses.
CMX_TEMP Tablespace to contain temporary tables for Informatica MDM Hub.
You must create enough space for the CMX_TEMP tablespace. When you create the tablespaces, adjust the
default tablespace sizes and number of data files based on the volume of data to be loaded into the MDM
Hub.
Install and Configure Oracle 21

Creating Tablespaces
Create tablespaces as permanent tablespaces that are managed locally or configured manually.
1. Log in to Oracle as a database administrator or a user with SYSTEM privileges.

2. Run the command to create a tablespace from SQL*Plus.
The following example shows the command you can use to create the CMX_DATA tablespace:
CREATE BIGFILE TABLESPACE CMX_DATA
NOLOGGING
DATAFILE '<Oracle install directory>/CMX_DATA1.dbf' SIZE 2048M REUSE
EXTENT MANAGEMENT LOCAL;
The default tablespace name is CMX_DATA. Do not use another tablespace name because the Repository
Manager will generate validation errors.
The following example shows the command you can use to create the CMX_INDX tablespace:
CREATE BIGFILE TABLESPACE CMX_INDX
NOLOGGING
DATAFILE '<Oracle install directory>/CMX_INDX1.dbf' SIZE 2048M REUSE EXTENT
MANAGEMENT LOCAL;
The following example shows the command you can use to create the CMX_TEMP tablespace:
CREATE BIGFILE TABLESPACE CMX_TEMP
NOLOGGING
DATAFILE '<Oracle install directory>/CMX_TEMP1.dbf' SIZE 2048M REUSE EXTENT
MANAGEMENT LOCAL;
If you do not use the default tablespace name for CMX_INDX and CMX_TEMP, you must set the
DEFERRED_SEGMENT_CREATION parameter to FALSE to prevent Repository Manager validation errors.
Configuring the DEFERRED_SEGMENT_CREATION Parameter

If you use a custom tablespace name for CMX_INDX or CMX_TEMP, set the DEFERRED_SEGMENT_CREATION
parameter to FALSE to prevent Repository Manager validation errors.
1. Run the following SQL command:

ALTER SYSTEM SET DEFERRED_SEGMENT_CREATION=FALSE SCOPE=BOTH;
2. Restart the database.
Grant Privileges to DBA User

You can create the MDM Hub Master Database and the Operational Reference Store as a SYS user or as a
DBA user with privileges to grant options. If you use the DBA user, you must grant privileges to the DBA user
with grant options for distributed transactions before you create the MDM Hub Master Database and the
Operational Reference Store.
1. Start SQL*Plus and connect to the database as a user that has privileges to grant options.
2. Use the following statements to grant privileges to the DBA user:
GRANT SELECT ON sys.pending_trans$ TO dbauser with grant option;
GRANT SELECT ON sys.dba_pending_transactions TO dbauser with grant option;
GRANT SELECT ON sys.dba_2pc_pending TO dbauser with grant option;
GRANT EXECUTE ON sys.dbms_xa TO dbauser with grant option;

Add the Oracle TNS Name
The Hub Server and Process Server installer do not add the TNS name into the tnsnames.ora file. You must
add TNS name entries to the tnsnames.ora file on the Hub Server and Process Server machines to connect
to the Oracle database.
u Add the following entry in the tnsnames.ora file:

<TNS NAME> =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(Host = <Oracle server host name>)(Port = <Oracle
server port>))
)
(CONNECT_DATA =
(SERVICE_NAME = <Oracle SID>)
)
)
Note: Ensure that the TNS names on the Hub Server machine and the Process Server machine are the
same.
Test the Database Connection

Test the connection to the database from each machine on which you want to run a Hub Server or Process
Server.
u Use the following command to test the database connection:

sqlplus <user name>/<password>@<TNS Name>
Install and Configure Oracle RAC

You can install the Hub Store on Oracle RAC. Before you install the Hub Store on Oracle RAC, you must
complete manual configuration steps to use features and optimize the environment for performance.
For information about installing and configuring Oracle RAC, see the Oracle documentation.
Use Oracle Service Names

You can use Oracle service names instead of Oracle SIDs for Oracle RAC installations. Use Oracle service
names for a more flexible method to specify the connection and to dynamically reallocate database servers.
Use Oracle RAC Load-Balanced Connections

Use Oracle RAC load-balanced connections in a fail-safe environment to ensure that a database connection
is available even when one or more Oracle RAC nodes become unavailable.
You can use Oracle RAC to specify a connection to an Oracle service that is enabled with load balancing and
high availability. Oracle RAC distributes the workload among all available nodes in the cluster. If a node
becomes unavailable, the work fails over to another node.
Most MDM Hub components use load balancing and available nodes. The MDM Hub components that build
their own direct JDBC connection cannot use load balancing. These components do not know the virtual IPs
of the Oracle RAC nodes.
Install and Configure Oracle RAC 23

The following table describes the Informatica MDM Hub components that use Oracle RAC load balancing:
Component Description
Batch Jobs Use load balancing when batch jobs are called from a command line because batch
jobs use the tnsnames.ora settings.
Note: Batch jobs cannot use load balancing when called from the Hub Console.
Services Integration Use load-balanced JDBC connections from the application server connection pool.
Framework API
Connections
Process Server Uses load-balanced JDBC connections from the Process Server connection pool.
Repository Manager Uses load-balanced JDBC connections from the application server connection pool
when only DML is required.
Note: Repository Manager cannot use load balancing when DDL is required
because DDL uses a direct JDBC connection.
Configure the tnsnames.ora File

You must configure all the Oracle RAC nodes of the database cluster in the tnsnames.ora file.
The following tnsnames.ora entry example shows you how to specify multiple Oracle RAC nodes for an
Oracle service called mdm_service.domain.com:
MDM_SERVICE.DOMAIN.COM =
(DESCRIPTION =
(ADDRESS_LIST=
(ADDRESS= (PROTOCOL = TCP)(HOST = server1-vip)(PORT = 1521))
(FAILOVER = on)
(LOAD_BALANCE = on)
)(
CONNECT_DATA=
(SERVICE_NAME = mdm_service.domain.com)
)
The connections to mdm_service.domain.com are load-balanced between the Oracle RAC nodes on server1,
server2, or server3.
Install and Configure WebLogic

Install and configure WebLogic Server according to the instructions in the WebLogic documentation.
Note: Install the application server in the same time zone as the database server.
Before you install the Hub Server and the Process Server on the WebLogic application server, create
WebLogic domains. Use the WebLogic Administration console to create domains for the Hub Server and the
Process Server applications. For more information, see the WebLogic documentation.

Ensure that you perform the following configurations:
• If the operating system uses Internet Protocol version 6 (IPv6), you must add -
Djava.net.preferIPv4Stack=true to the script that is in the bin directory of the base domain:
On UNIX. startWebLogic.sh
On Windows. startWebLogic.cmd
• In a multi-node or clustered environment, add the following JVM option to the WebLogic startup script:
-Djgroups.bind_addr=<bind_addr>
where, <bind_addr> specifies the interface on which to receive and send messages.
You must ensure that each node in the multi-node or clustered environment binds to its own network
interface.
• To enhance the performance of the MDM Hub environment, add the following JVM option for JIT code
cache size to JAVA_OPTIONS in the WebLogic startup script:
-XX:ReservedCodeCacheSize=256m
• Add the following JVM option to JAVA_OPTIONS in the WebLogic startup script to set the
oracle.jdbc.J2EE13Compliant system variable:
-Doracle.jdbc.J2EE13Compliant=true
• Set the maximum JVM heap size (-Xmx) to 4 GB or higher in the WebLogic startup script. Change the
following settings:
set JAVA_OPTIONS=%JAVA_OPTIONS% -server -Xms2048m -Xmx4096m -Xss2000k -
XX:PermSize=256m -XX:MaxPermSize=1024m
The -Xmx parameter must be three to four times the size of –XX:MaxPermSize and -XX:PermSize must
be one third or one fourth the size of -XX:MaxPermSize.
• Set the WLS_MEM_ARGS_64BIT memory variable to appropriate values in the following file:
On UNIX. <Domain Home Directory>/bin/setDomainEnv.sh
On Windows. <Domain Home Directory>\bin\setDomainEnv.cmd
For example:
WLS_MEM_ARGS_64BIT="-Xms256m -Xmx1024m -XX:PermSize512m"
• If you want to install Informatica platform, add the following option to JAVA_OPTIONS in the WebLogic
startup script:
-DUseSunHttpHandler=true
You set the option to true so that WebLogic uses the Sun HTTP Handler for the HTTP connection
between the MDM Hub and the Informatica platform.
• Add the following option to JAVA_OPTIONS in the WebLogic startup script to set the log4j.xml file
configuration path:
-DFrameworksLogConfigurationPath="<Path to the log4j.xml file>"
Create a WebLogic Cluster

You can choose to install the MDM Hub in a WebLogic clustered environment.
The following steps provide a high-level overview of the process to set up the WebLogic cluster. For more
information, see the WebLogic documentation.
1. Install WebLogic.
2. Create a domain called mydomain in the following directory:
Install and Configure WebLogic 25

On UNIX. /BEA/User_Projects/domain
On Windows. \BEA\User_Projects\domain
3. Run the following command to start the Administration Server:
On UNIX. ./startWebLogic.sh
4. Log in to the WebLogic Administrator Console and create a machine, M1.
5. In machine M1, create the managed server MS1.
6. Add the managed server MS1 to machine M1.
7. On machine M1, navigate to the following directory:
On UNIX. <Domain_directory>/bin
On Windows. <Domain_directory>\bin
8. Run the following command to start each Managed Server:
On UNIX.
./startManagedWebLogic.sh <machine name> http://<host of the admin server>:<port of
the admin server>
On Windows.
startManagedWebLogic.cmd <machine name> http://<host of the admin server>:<port of
the admin server>
9. Install WebLogic on another physical machine.
Note: Ensure that all machine in a cluster have the same version of WebLogic.
10. Create machine, M2.
11. In machine M2, create a domain called mydomain in the same directory structure as that you use for the
first machine.
On UNIX. /BEA/User_Projects/domain/
On Windows. \BEA\User_Projects\domain\
12. In machine M2, create the managed server MS2.
13. Add the managed server MS2 to machine M2.
14. Add the managed servers MS1 and MS2 to the cluster domain.
15. On machine M2, navigate to the following directory:
On UNIX. <Domain_directory>/bin
On Windows. <Domain_directory>\bin
On UNIX.
the admin server>
On Windows.
startManagedWebLogic.cmd <machine name Ex:M1> http://<host of the admin
server>:<port of the admin server>

Configuring the HTTPS Protocol
You can configure the HTTPS protocol for the MDM Hub communications. Use the WebLogic Server
Administration Console to configure the HTTPS protocol. Alternatively, you can use the default JDK secure
certificates to enable HTTPS.
1. Start the WebLogic Server Administration Console.

2. In the Home Page, under the Environmentsection, click Servers.
The Summary of Servers page appears.
3. In the Servers list, click the AdminServer(admin) link.
The Settings for AdminServer page appears.
4. Enable the SSL Listen Port Enabled option.
5. Enter the port number in the SSL Listen Port field.
6. Click the SSL tab.
7. From the Hostname Verification list, select None.
8. Click Save.
Configure WebLogic to Use an Oracle Data Source

Configure WebLogic to use an Oracle data source. If you install the Process Server on a different machine
from the one that runs the Hub Server, then on the Process Server machine, create data sources for each
Contact Oracle to get JDBC driver for the database configuration.
1. To configure WebLogic to use an Oracle data source, copy the Oracle JDBC driver to the following
directory:
On UNIX. <WebLogic install directory>/wlsserver/server/lib
On Windows. <WebLogic install directory>\wlsserver\server\lib
2. Add the path to the JDBC driver to the WEBLOGIC_CLASSPATH variable in the following file:
On UNIX. <WebLogic install directory>/wlsserver/common/bin/commEnv.sh
On Windows. <WebLogic install directory>\wlsserver\common\bin\commEnv.cmd
Note: Place the path to the JDBC driver before the path to other Weblogic Server libraries.
Create a Master Data Source

If you want to install the Process Server on a different machine from the one that runs the Hub Server or the
Oracle database, then on the Process Server machine, create a data source for the Master Database.
1. Start the WebLogic Administration Console.

2. Click the Lock & Edit button to acquire a lock.
3. Click Services > JDBC > Data Sources, and then click New.
The JDBC Data Sources Properties page appears.
4. Specify the following data source properties:
Name
Name of the JDBC data source. Set the name to MDM Master Data Source.

JNDI Name
JNDI path to where the JDBC data source will be bound. Specify jdbc/siperian-cmx_system-ds.
Database Type
Database type that you want to connect to. Select Oracle.
Database Driver
JDBC driver that you want to use to connect to the database. Select Oracle driver (Thin XA).
5. Click Next.
The Transaction Options page appears.
6. Click Next.
The Connection Properties page appears.
7. Enter values for the following connection properties:
Database Name
Name of the database you want to connect to.
Host Name
DNS name or IP address of the server that hosts the database.
Port
Port on which the database server listens for connections requests.
Database User Name

Database user name that you want to use for each connection in the data source.
Password
Password of the database user account.
Confirm Password
8. Click Next.
The Test Database Connection page appears.
9. Click Test Configuration to test the driver connections.
If the test is unsuccessful, you must update the values in the Connection Properties page and then
retry the connection until successful.
10. Click Next.
The Select Targets page appears.
11. Select the server on which you want to deploy the data source.
12. Click Finish.
13. Click Activate Changes.
Create an Operational Reference Store Data Source

If you want to install the Process Server on a different machine from the one that runs the Hub Server or the
Oracle database, then on the Process Server machine, create a data source for the Operational Reference
Store.

2. Click the Lock & Edit button to acquire a lock.
3. Click Services > JDBC > Data Sources, and then click New.
4. Specify the following data source properties:
Name
Name of the JDBC data source. Set the name to MDM ORS Data Source.
JNDI Name
JNDI path to where the JDBC data source will be bound. Specify jdbc/siperian-<oracle host
name>-<oracle sid>-<Operational reference Store name>-ds.
Database Type
Database type that you want to connect to. Select Oracle.
Database Driver
JDBC driver that you want to use to connect to the database. Select Oracle driver (Thin XA).
5. Click Next.
6. Click Next.
Database Name
Name of the database you want to connect to.
Host Name
Port
Database User Name

Password
Confirm Password
8. Click Next.
9. Click Test Configuration to test the driver connections.
10. Click Next.
11. Select the server on which you want to deploy the data source.
12. Click Finish.

Configure WebLogic for Multiple MDM Hub Master Databases

If you want to configure more than one MDM Hub Master Database, you have to install an MDM Hub instance
for each MDM Hub Master Database. You must deploy each MDM Hub instance on a separate WebLogic
domain. Create as many WebLogic domains as the number of MDM Hub Master Databases and the MDM
Hub instances that you want to install.
Configure WebLogic for Informatica Data Director

If you use Informatica Data Director, configure WebLogic and then restart the application server for the
changes to take effect.
• To save records that contain UTF-8 characters, add the following JVM option to the WebLogic startup
script.
-Dfile.encoding=UTF-8
Install and Configure External Cleanse Engines

If you intend to use a cleanse engine, such as Address Doctor, to use with the Process Server, install and
configure the cleanse engine.
For instructions on how to configure the MDM Hub to integrate with the cleanse engine, see the Informatica
MDM Multidomain Edition Cleanse Adapter Guide.
Determine the Timeline Granularity

Before you install the MDM Hub components, determine the timeline granularity. Timeline granularity is the
time measurement that you want to use to define effective periods for versions of records. For example, you
can choose the effective periods to be in years, months, or seconds.
You can configure the timeline granularity of year, month, day, hour, minute, or seconds to specify effective
periods of data in the MDM Hub implementation. You can configure the timeline granularity that you need
when you create or update an Operational Reference Store.
Important: The timeline granularity that you configure cannot be changed.
When you specify an effective period in any timeline granularity, the system uses the database time locale for
the effective periods. To create a version that is effective for one timeline measurement unit, the start date
and the end date must be the same.

The following table lists the timeline granularity that you can configure and the formats:
Timeline Granularity Timeline Format
Year yyyy
Month mm/yyyy
Day dd/mm/yyyy
Hour dd/mm/yyyy hh
Minute dd/mm/yyyy hh:mm
Second dd/mm/yyyy hh:mm:ss
Use one of the following timeline granularity options:
Year
When the timeline granularity is year, you can specify the effective period in the year format, such as
2010. An effective start date of a record starts at the beginning of the year and the effective end date
ends at the end of the year. For example, if the effective start date is 2013 and the effective end date is
2014, then the record would be effective from 01/01/2013 to 31/12/2014.
Month
When the timeline granularity is month, you can specify the effective period in the month format, such as
01/2013. An effective start date of a record starts on the first day of a month. The effective end date of a
record ends on the last day of a month. For example, if the effective start date is 02/2013 and the
effective end date is 04/2013, the record is effective from 01/02/2013 to 30/04/2013.
Day
When the timeline granularity is day, you can specify the effective period in the date format, such as
13/01/2013. An effective start date of a record starts at the beginning of a day, that is 12:00. The
effective end date of the record ends at the end of a day, which is 23:59. For example, if the effective
start date is 13/01/2013 and the effective end date is 15/04/2013, the record is effective from 12:00 on
13/01/2013 to 23:59 on 15/04/2013.
Hour
When the timeline granularity is hour, the effective period includes the year, month, day and hour, such
as 13/01/2013 15. An effective start date of a record starts at the beginning of an hour of a day. The
effective end date of the record ends at the end of the hour that you specify. For example, if the effective
start date is 13/01/2013 15 and the effective end date is 15/04/2013 10, the record is effective from
15:00 on 13/01/2013 to 10:59 on 15/04/2013.
Minute
When the timeline granularity is minute, the effective period includes the year, month, day, hour, and
minute, such as 13/01/2013 15:30. An effective start date of a record starts at the beginning of a minute.
The effective end date of the record ends at the end of the minute that you specify. For example, if the
effective start date is 13/01/2013 15:30 and the effective end date is 15/04/2013 10:45, the record is
effective from 15:30:00 on 13/01/2013 to 10:45:59 on 15/04/2013.
Second
When the timeline granularity is second, the effective period includes the year, month, day, hour, minute,
and second, such as 13/01/2013 15:30:45. An effective start date of a record starts at the beginning of a
second. The effective end date ends at the end of the second that you specify. For example, if the
Determine the Timeline Granularity 31

effective start date is 13/01/2013 15:30:55 and the effective end date is 15/04/2013 10:45:15, the record
is effective from 15:30:55:00 on 13/01/2013 to 10:45:15:00 on 15/04/2013.
Configure the Informatica Platform Properties File

If you want to install Informatica platform as part of the MDM Hub installation, create an Informatica platform
properties file. Specify the options for the installation in the properties file, and save the file with the name
SilentInput.properties.
1. Open a text editor.

2. Create an Informatica platform properties file in the text editor.
3. Configure the values of the installation parameters.
4. Save the properties file with the name SilentInput.properties.
Configure the following installation parameters:
LICENSE_KEY_LOC
Absolute path and file name of the license key file.
USER_INSTALL_DIR
Directory in which to install Informatica.
INSTALL_TYPE
Indicates whether to install or upgrade Informatica.
If the value is 0, the installer performs an installation of Informatica. If the value is 1, the installer
upgrades a previous version of Informatica.
ENABLE_USAGE_COLLECTION
Indicates whether to configure Informatica DiscoveryIQ, a product usage tool that sends routine reports
on data usage and system statistics to Informatica. You can choose to not send any usage statistics to
Informatica.
To configure Informatica DiscoveryIQ to send usage statistics to Informatica, set the parameter to 1. For
information about how to disable sending usage statistics, see the Informatica Administrator Guide.
ENABLE_KERBEROS
Indicates whether to configure the Informatica domain to run on a network with Kerberos authentication.
To configure the Informatica domain to run on a network with Kerberos authentication, set the parameter
to 1.
SERVICE_REALM_NAME
Name of the Kerberos realm to which the Informatica domain services belong. The service realm name
and the user realm name must be the same.
USER_REALM_NAME
Name of the Kerberos realm to which the Informatica domain users belong. The service realm name and
the user realm name must be the same.

KEYTAB_LOCATION
Directory where you store all keytab files for the Informatica domain. The name of a keytab file in the
Informatica domain must follow a format set by Informatica.
KRB5_FILE_LOCATION
Path and file name of the Kerberos configuration file. Informatica requires krb5.conf name for the
Kerberos configuration file.
SPN_SHARE_LEVEL
Indicates the service principal level for the domain. Set the property to one of the following levels:
• Process. The domain requires a unique service principal name (SPN) and keytab file for each node
and each service on a node. The number of SPNs and keytab files required for each node depends
on the number of service processes that run on the node. Recommended for production domains.
• Node. The domain uses one SPN and keytab file for the node and all services that run on the node.
The domain also requires a separate SPN and keytab file for all HTTP processes on the node.
Recommended for test and development domains.
Default is process.
HTTPS_ENABLED
Indicates whether to secure the connection to Informatica Administrator. If the value is 0, the installer
sets up an unsecure HTTP connection to Informatica Administrator. If the value is 1, the installer sets up
a secure HTTPS connection to Informatica Administrator.
DEFAULT_HTTPS_ENABLED
Indicates whether the installer creates a keystore file.
If the value is 1, the installer creates a keystore and uses it for the HTTPS connection. If the value is 0,
the installer uses a keystore file that you specify.
CUSTOM_HTTPS_ENABLED
Indicates whether the installer uses an existing keystore file.
If the value is 1, the installer uses a keystore file that you specify. If DEFAULT_HTTPS_ENABLED=1,
you must set this parameter to 0. If DEFAULT_HTTPS_ENABLED=0, you must set this parameter to 1.
KSTORE_PSSWD
Plain text password for the keystore file.
KSTORE_FILE_LOCATION
Absolute path and file name of the keystore file.
HTTPS_PORT
Port number to use for the secure connection to Informatica Administrator.
CREATE_DOMAIN
Indicates whether to create an Informatica domain.
If the value is 1, the installer creates a node and an Informatica domain. If the value is 0, the installer
creates a node and joins the node to another domain created in a previous installation.
KEY_DEST_LOCATION
Directory in which to store the encryption key on the node created during the installation.
Configure the Informatica Platform Properties File 33

PASS_PHRASE
Keyword to use to create an encryption key to secure sensitive data in the domain. The keyword must
meet the following criteria:
• From 8 to 20 characters long

• Includes at least one uppercase letter
• Includes at least one lowercase letter
• Includes at least one number
• Does not contain spaces
JOIN_DOMAIN
Indicates whether to join the node to another domain created in a previous installation.
If the value is 1, the installer creates a node and joins the node to another domain. If
CREATE_DOMAIN=1, you must set the parameter to 0. If CREATE_DOMAIN=0, you must set this
parameter to 1.
KEY_SRC_LOCATION
Directory that contains the encryption key on the master gateway node of the Informatica domain that
you want to join.
SSL_ENABLED
Enables or disables secure communication between services in the Informatica domain.
Indicates whether to set up secure communication between services within the domain. If the value is
true, secure communication between services within the domain is enabled. You can set the property to
true if CREATE_DOMAIN=1. You must set the property to true if JOIN_DOMAIN=1.
SECURITY_DOMAIN_NAME
Name of the default security domain in the domain to which you join the node you create.
TLS_CUSTOM_SELECTION
Indicates whether to use SSL certificates that you provide to enable secure communication in the
Informatica domain.
To use SSL certificates that you provide, set this property to True.
NODE_KEYSTORE_DIR
Required if TLS_CUSTOM_SELECTION is set to True. Directory that contains the keystore files. The
directory must contain files named infa_keystore.jks and infa_keystore.pem.
NODE_KEYSTORE_PASSWD
Required if TLS_CUSTOM_SELECTION is set to True. Password for the keystore infa_keystore.jks.
NODE_TRUSTSTORE_DIR
Required if TLS_CUSTOM_SELECTION is set to True. Directory that contains the truststore files. The
directory must contain files named infa_truststore.jks and infa_truststore.pem.
NODE_TRUSTSTORE_PASSWD
Required if TLS_CUSTOM_SELECTION is set to True. Password for the infa_truststore.jks file.
SERVES_AS_GATEWAY
Indicates whether to create a gateway or worker node.

If the value is 1, the installer configures the node as a gateway node. If the value is 0, the installer
configures the node as a worker node.
DB_TYPE
Database for the domain configuration repository.
Enter one of the following values:
• Oracle
• DB2
• MSSQLServer
DB_UNAME
Database user account name for the domain configuration repository.
DB_PASSWD
Password for the database user account.
DB_SSL_ENABLED
Indicates whether the database for the domain configuration repository is secure. To create the domain
configuration repository in a secure database, set this parameter to True. If this parameter is set to True,
you must provide the JDBC connection string with the secure database parameters.
TRUSTSTORE_DB_FILE
Path and file name of the truststore file for the secure database.
TRUSTSTORE_DB_PASSWD
Password for the truststore file.
DB_CUSTOM_STRING_SELECTION
Determines whether to use a JDBC URL or a custom connection string to connect to the domain
configuration database.
If the value is 0, the installer creates a JDBC URL from the database properties you provide. If the value
is 1, the installer uses the custom connection string you provide. If you create the domain configuration
repository on a secure database, set the parameter to 1.
DB_SERVICENAME
Required if DB_CUSTOM_STRING_SELECTION=0.
Service name for Oracle databases.
DB_ADDRESS
Host name and port number for the database instance in the format HostName:Port.
ADVANCE_JDBC_PARAM
You can set this parameter if DB_CUSTOM_STRING_SELECTION=0.
Optional parameters to include in the JDBC URL connection string. Verify that the parameter string is
valid. The installer does not validate the parameter string before it adds the string to the JDBC URL. If
this parameter is empty, the installer creates the JDBC URL without additional parameters.
DB_CUSTOM_STRING

Valid custom JDBC connection string.
DOMAIN_NAME
Name of the domain.
The default domain name is Domain_<MachineName>. The name must not exceed 128 characters and
must be 7-bit ASCII. It cannot contain a space or any of the following characters: ` % * + ; " ?
DOMAIN_HOST_NAME
Host name of the machine that hosts the node.
Note: Do not use localhost. The host name must explicitly identify the machine.
NODE_NAME
Required if CREATE_DOMAIN=1.
Name of the node to create on the machine. The node name is not the host name for the machine.
DOMAIN_PORT
If you create a domain, this is the port number for the node to create. The default port number for the
node is 6005. If the default port number is not available on the machine, the installer displays the next
available port number.
If you join a domain, this is the port number of the gateway node of the domain you want to join.
DOMAIN_USER
User name for the domain administrator.
DOMAIN_PSSWD
Password for the domain administrator. The password must be more than two characters but cannot
exceed 16 characters.
DOMAIN_CNFRM_PSSWD
Enter the password again to confirm.
JOIN_NODE_NAME
Required if JOIN_DOMAIN=1.
Name of the node that you are joining to the domain. The node name is not the host name for the
machine.
JOIN_HOST_NAME
Host name of the machine on which to create the node that you are joining to the domain. The node host
name cannot contain the underscore (_) character.
Note: Do not use localhost. The host name must explicitly identify the machine.
JOIN_DOMAIN_PORT
Port number of the gateway node of the domain that you want to join.

ADVANCE_PORT_CONFIG
Indicates whether to display the list of port numbers for the domain and node components. If the value is
0, the installer assigns default port numbers to the domain and node components. If the value is 1, you
can set the port numbers for the domain and node components.
MIN_PORT
You can set this parameter if ADVANCE_PORT_CONFIG=1.
Lowest port number in the range of dynamic port numbers that you can assign to the application service
processes that run on the node.
MAX_PORT
Highest port number in the range of dynamic port numbers that you can assign to the application service
processes that run on the node.
TOMCAT_PORT
Port number that the Service Manager uses on the node. The Service Manager listens for incoming
connection requests on this port. Client applications use this port to communicate with the services in the
domain. This is the port that the Informatica command line programs use to communicate to the domain.
This is also the port for the SQL data service JDBC/ODBC driver. Default is 6006.
AC_PORT
You can set this parameter if CREATE_DOMAIN=1 and ADVANCE_PORT_CONFIG=1.
Port number that Informatica Administrator uses. Default is 6007.
SERVER_PORT
Port number that controls server shutdown for the domain Service Manager. The Service Manager
listens for shutdown commands on this port. Default is 6008.
AC_SHUTDWN_PORT
You can set this parameter if CREATE_DOMAIN=1 and ADVANCE_PORT_CONFIG=1.
Port number that controls server shutdown for Informatica Administrator. Informatica Administrator
listens for shutdown commands on this port. Default is 6009.
On Windows, specify whether to run the Informatica service under the same user account as the account
used for installation.
Set the following properties if you want to run the Informatica service under a different user account:
USE_LOGIN_DETAILS
Indicates whether to run the Windows service under a different user account. If the value is 0, the
installer configures the service to run under the current user account. If the value is 1, the installer
configures the service to run under a different user account.
WIN_USER_ID
User account with which to run the Informatica Windows service.
Use the following format:

Domain Name\User Account

The user account must have the Act as operating system permission.
WIN_USER_PSSWD
Password for the user account with which to run the Informatica Windows service.
Sample Informatica Platform Properties File

The following example shows the contents of the sample silentInput.properties file:
# Use the sample file SilentInput.properties to install Informatica services without
user interaction.
# Use the sample properties file to define the parameters for the silent
installation.
# To upgrade Informatica, use the SilentInput_upgrade.properties or
SilentInput_upgrade_NewConfig.properties file.
# Use the following guidelines when you edit this file:
# Back up the file before you modify it.
# Any error condition that causes the installation to fail, such as an installation
directory that is not valid,
# generates a log file in SYSTEM_DRIVE_ROOT. For example: c:\silentErrorLog.log
#######
# The LICENSE_KEY_LOC property represents the absolute path and file name of the
license key file.
# Set the property if you are installing or upgrading Informatica.
LICENSE_KEY_LOC=c:\license.key
# The USER_INSTALL_DIR property represents the directory in which to install the new
version of Informatica.
# Set the property if you are installing or upgrading Informatica.
# The property must point to a valid directory with write permissions enabled.
USER_INSTALL_DIR=c:\Informatica\9.6.1
# The INSTALL_TYPE property determines whether to install or upgrade Informatica.

# Set INSTALL_TYPE=0 to perform a new installation of Informatica.
# To upgrade Informatica, use the SilentInput_upgrade.properties file.
# To upgrade Informatica to a different node configuration, use the
SilentInput_upgrade_NewConfig.properties file.
INSTALL_TYPE=0
# Provide Kerberos Network Authentication parameters:
#Set this property to 1 if you are Enabling Kerberos

ENABLE_KERBEROS=0
#Provide Service realm name.

SERVICE_REALM_NAME=
#Provide User realm name.

USER_REALM_NAME=
#provide KeyTab location.
KEYTAB_LOCATION=
#Provide Kerberos configuration file location.

KRB5_FILE_LOCATION=
# The SPN_SHARE_LEVEL property determines whether the service principal level for the
domain is Node or Process.
# Value NODE Use Node Level. Configure the domain to share SPNs and keytab
files on a node.
# Value PROCESS Use Process Level. Configure the domain to use a unique service
principal name (SPN) and keytab file for each node and each service on a node.
SPN_SHARE_LEVEL=

# The HTTPS_ENABLED property determines whether to secure the connection to Informatica
Administrator.
# Value 0 Use HTTP connection. Set up an unsecure HTTP connection to
Informatica Administrator.
# Value 1 Use HTTPS connection. Set up a secure HTTPS connection to the
HTTPS_ENABLED=0
# The DEFAULT_HTTPS_ENABLED property determines whether the installer creates a

keystore file.
# Set the property if HTTPS_ENABLED=1 (uses HTTPS connection).
# Value 0 Use a keystore file that you specify.
# Value 1 Create a keystore and use it for the HTTPS connection.
DEFAULT_HTTPS_ENABLED=1
# The CUSTOM_HTTPS_ENABLED property determines whether the installer uses an existing

keystore file.
# Value 0 Set the property to 0 if DEFAULT_HTTPS_ENABLED=1.
# Value 1 Install Informatica using a keystore file that you specify. Set
the property to 1 if DEFAULT_HTTPS_ENABLED=0.
CUSTOM_HTTPS_ENABLED=0
# The KSTORE_PSSWD property represents the password for the keystore file.
# Set the property to the plain text password for the keystore file if
CUSTOM_HTTPS_ENABLED=1.
KSTORE_PSSWD=MyKeystorePassword
# The KSTORE_FILE_LOCATION property represents the location of the keystore file.

# Set the property to the absolute path and file name of the keystore file if
CUSTOM_HTTPS_ENABLED=1.
KSTORE_FILE_LOCATION=c:\MyKeystoreFile
# The HTTPS_PORT property represents the port number to use for the secure connection
to Informatica Administrator.
HTTPS_PORT=8443
# The CREATE_DOMAIN property determines whether to create an Informatica domain.

# Value 0 Create a node and join the node to another domain created in a
previous installation. Set the property to 0 if JOIN_DOMAIN=1.
# Value 1 Create a node and an Informatica domain.
CREATE_DOMAIN=1
#Please Specify the site key Destination location

KEY_DEST_LOCATION=c:\Informatica\9.6.1\isp\config\keys
#set the property to Pass Phrase, this field needs to set only for CREATE DOMAIN case
PASS_PHRASE_PASSWD=
# The JOIN_DOMAIN property determines whether to join the node to another domain
created in a previous installation.
# Value 0 Create a node and an Informatica domain. Set the property to 0 if
CREATE_DOMAIN=1.
# Value 1 Create a node and join the node to another domain created in a
previous installation. Set the property to 1 if CREATE_DOMAIN=0.
JOIN_DOMAIN=0
# Set the property to the site key source location and this needs to set only for JOIN
DOMAIN case
KEY_SRC_LOCATION=c:\temp\siteKey
# The SSL_ENABLED property enables or disables Transport Layer Security (TLS).

# Set the property to true to enable secure communication between services within

the domain.
# Set the property to true or false if CREATE_DOMAIN=1.
# The property will not be used if JOIN_DOMAIN=1, as the node will get added on the
basis of domain security.
SSL_ENABLED=false
# The property SECURITY_DOMAIN_NAME represents the LDAP name for the Kerberos
enabled domain
# Set the property if JOIN_DOMAIN=1 and ENABLE_KERBEROS=1
SECURITY_DOMAIN_NAME=
#################################################
#Provide TLS information for domain. Set TLS_CUSTOM_SELECTION equals to true if you
want domain level TLS option.
TLS_CUSTOM_SELECTION=false
################################
#Below fields are only required when you set TLS_CUSTOM_SELECTION=true
NODE_KEYSTORE_DIR=c:\temp
NODE_KEYSTORE_PASSWD=
NODE_TRUSTSTORE_DIR=c:\temp
NODE_TRUSTSTORE_PASSWD=
# The SERVES_AS_GATEWAY property determines whether to create a gateway or worker node.

# Set the property if JOIN_DOMAIN=1.
# Value 0 The installer configures the node as a worker node.
# Value 1 The installer configures the node as a gateway node.
SERVES_AS_GATEWAY=0
# The DB_TYPE property represents the database type for the domain configuration
database.
# Set the property to the database types (case-sensitive): Oracle.
DB_TYPE=Oracle
# The DB_UNAME property represents the database user account name for the domain
configuration repository.
DB_UNAME=UserName
# The DB_PASSWD property represents the database password for the database user account.
DB_PASSWD=UserPassword
# The DB_SSL_ENABLED property represents whether the database is in SSL mode or not.
#Set the property to "true" if you want to enable secure communication.
# Also if this property is set to true then DB_CUSTOM_STRING_SELECTION property must be
set to 1 to use
#only custom string option property DB_CUSTOM_STRING which should include the following
secure DB parameters:
#EncryptionMethod=SSL;HostNameInCertificate=;ValidateServerCertificate=
DB_SSL_ENABLED=false
# The TRUSTSTORE_DB_FILE and TRUSTSTORE_DB_PASSWD properties to be set only if enable

secure communication
#for the DB property i.e DB_SSL_ENABLED=true
# Set the TRUSTSTORE_DB_FILE property to the location of the trust store file for the DB
# Set the TRUSTSTORE_DB_PASSWD as a password of the trust store file for the DB
TRUSTSTORE_DB_FILE=
TRUSTSTORE_DB_PASSWD=

# Set TRUSTED_CONNECTION=0 if DB_TYPE is set to a database type other than
MSSQLServer or if you install Informatica on Linux or UNIX.
# If the property is empty, the installer uses Microsoft SQL Server
authentication.
# In join node scenario, when JOIN_DOMAIN=1

# Set this value to empty,for all cases.
TRUSTED_CONNECTION=
# The DB_CUSTOM_STRING_SELECTION property determines whether to use a JDBC URL or a

custom connection string to connect to the domain configuration database.
# Set DB_CUSTOM_STRING_SELECTION=1 if TRUSTED_CONNECTION=1. Also provide the
default valid connection string in DB_CUSTOM_STRING.
# Value 0 The installer creates a JDBC URL from the database properties you
provide
# Value 1 The installer uses the custom connection string you provide.
DB_CUSTOM_STRING_SELECTION=0
# The DB_SERVICENAME property represents the service name or database name of the
database.
# Set the property if DB_CUSTOM_STRING_SELECTION=0.
# Set the property to the service name for Oracle and IBM DB2 databases.
# Set the property to the database name for Microsoft SQL Server and Sybase ASE
databases.
# Leave the property blank if DB_CUSTOM_STRING_SELECTION=1.
DB_SERVICENAME=DBServiceName
# The DB_ADDRESS property represents the host name and port number for the database
instance.
# Set the property in the format HostName:PortNumber.
# Leave the property blank if DB_CUSTOM_STRING_SELECTION=1.
DB_ADDRESS=HostName:PortNumber
# The ADVANCE_JDBC_PARAM property represents additional parameters in the JDBC URL

connection string.
# If DB_CUSTOM_STRING_SELECTION=0, you can set the property to include optional
parameters in the JDBC URL connection string.
# The parameter string must be valid.
# If the parameter is empty, the installer creates the JDBC URL without additional
parameters.
ADVANCE_JDBC_PARAM=
# The DB_CUSTOM_STRING property represents a valid custom JDBC connection string.

DB_CUSTOM_STRING=
# The DOMAIN_NAME property represents the name of the domain to create. The default
domain name is Domain_<MachineName>.
# Set the property if CREATE_DOMAIN=1.
# The domain name must not exceed 128 characters and must be 7-bit ASCII only. It
cannot contain a space or any of the following characters: ` % * + ; " ? , < > \ /
DOMAIN_NAME=DomainName
# The DOMAIN_HOST_NAME property represents the host name of the machine.

# * If you create a domain, this is the host name of the machine on which to create
the node.

# If the machine has a single network name, use the default host name.
# If the machine has multiple network names, you can modify the default host
name to use an alternate network name. Optionally, you can use the IP address.
# * If you join a domain, this is the host name of the machine that hosts the
gateway node of the domain you want to join.
# Do not use localhost. The host name must explicitly identify the machine.
DOMAIN_HOST_NAME=HostName
# The NODE_NAME property represents the node to create on the machine. The node name is
not the host name for the machine.
NODE_NAME=NodeName
# The DOMAIN_PORT property represents the port number.

# * If you create a domain, set the property to the port number for the node to
create.
# The default port number for the node is 6005.
# If the default port number is not available on the machine, the installer
displays the next available port number.
# * If you join a domain, set the property to the port number of the gateway node
of the domain you want to join.
DOMAIN_PORT=
# The DOMAIN_USER property represents the user name for the domain administrator.
# If you create a domain, you can use this user name to initially log in to the
# If you join a domain, this is the user name to use to log in to the domain that
you want to join.
DOMAIN_USER=AdminUser
# The DOMAIN_PSSWD property represents the password for the domain administrator.
# The password must be more than 2 characters but cannot exceed 128 characters.
DOMAIN_PSSWD=
# The DOMAIN_CNFRM_PSSWD property confirms the password you set for the domain
administrator.
# Set the property to the password you set in the DOMAIN_PSSWD property to confirm
the password.
DOMAIN_CNFRM_PSSWD=
# The JOIN_NODE_NAME property represents the name of the node to create on this
machine. The node name is not the host name for the machine.
JOIN_NODE_NAME=NodeName
# The JOIN_HOST_NAME property represents the host name of the machine that hosts the
gateway node of the domain you want to join.
JOIN_HOST_NAME=DomainHostName
# The JOIN_DOMAIN_PORT property represents the port number of the gateway node of the
domain you want to join.
JOIN_DOMAIN_PORT=
# The ADVANCE_PORT_CONFIG property determines whether to display the list of port

numbers for the domain and node components.
# If ADVANCE_PORT_CONFIG=1, set the MIN_PORT, MAX_PORT, TOMCAT_PORT, AC_PORT,
SERVER_PORT, and AC_SHUTDWN_PORT properties.
# Value 0 The installer assigns default port numbers to the domain and node
components.
# Value 1 You can manually set the port numbers for the domain and node
components.

ADVANCE_PORT_CONFIG=0
# The MIN_PORT property represents the lowest port number in the range of port numbers
that can be assigned to the application service processes that run on this node.
# Set the property if ADVANCE_PORT_CONFIG=1.
MIN_PORT=
# The MAX_PORT property represents the highest port number in the range of port numbers
that can be assigned to the application service processes that run on this node.
MAX_PORT=
# The TOMCAT_PORT property represents the port number used by the Service Manager on
the node. Default is 6006.
# The Service Manager listens for incoming connection requests on this port.
# Client applications use this port to communicate with the services in the domain.
# This is the port that the Informatica command line programs use to communicate
with the domain.
# This is also the port for the SQL data service JDBC/ODBC driver.
TOMCAT_PORT=
# The AC_PORT property represents the port number used by Informatica Administrator.
Default is 6007.
# Set the property if CREATE_DOMAIN=1 and ADVANCE_PORT_CONFIG=1.
AC_PORT=
# The SERVER_PORT property controls the server shutdown for the domain Service Manager.
The Service Manager listens for shutdown commands on this port. Default is 6008.
SERVER_PORT=
# The AC_SHUTDWN_PORT property represents the port number that controls the server
shutdown for Informatica Administrator. Default is 6009.
# Informatica Administrator listens for shutdown commands on this port.
AC_SHUTDWN_PORT=
#######
# On Windows, set the following properties to specify whether to run the Informatica
service under the same user account as the account used for installation.
#######
# The USE_LOGIN_DETAILS property determines whether to run the Windows service under a
different user account.
# Value 0 The installer configures the service to run under the current
user account.
# Value 1 The installer configures the service to run under a different
user account.
USE_LOGIN_DETAILS=0
# The WIN_USER_ID property represents the user account with which to run the
Informatica Windows service.
# Set the property if USE_LOGIN_DETAILS=1.
# The user account must have the "Act as part of the operating system" permission.
# Use the format DomainName\UserAccount.
WIN_USER_ID=WindowsUserAcct

# The WIN_USER_PSSWD property represents the password for the user account with which
to run the Informatica Windows service.
WIN_USER_PSSWD=WindowsUserPassword
#######
# After you create the properties file, save the file with the name
SilentInput.properties and
# run the silent installer to perform the Informatica services installation.
#######
Create an Installation Documentation Directory

Create a directory to store copies of installation files, such as the validation results, environment reports,
database debug logs, and log files.
For example, you can create the directory install_doc. If you need to troubleshoot the installation, you can
create an archive file of the installation documentation directory and send it to Informatica Global Customer
Support for analysis.

CHAPTER 3
ActiveVOS Pre-Installation Tasks

• ActiveVOS Pre-Installation Tasks Overview, 45

• Create an Informatica ActiveVOS Schema, 45
• Create an Administrative User in WebLogic Environments, 47
ActiveVOS Pre-Installation Tasks Overview

When you install the Hub Server, you are prompted to enter the ActiveVOS Console administrative user
name and password. If you are upgrading an environment configured to use embedded ActiveVOS as the
BPM, you must install ActiveVOS during the Hub Server upgrade process to configure ActiveVOS security.
Create an Informatica ActiveVOS Schema

Before you run the Hub Server installer, you need to create the ActiveVOS database schema. To create the
schema, you run a script.
1. Open a command prompt.

2. Navigate to the following location in the distribution directory:
On UNIX. <distribution directory>/database/bin
On Windows. <distribution directory>\database\bin
3. Run the following command:
On UNIX. sip_ant.sh create_bpm
On Windows. sip_ant.bat create_bpm
4. Answer the prompts that appear.
45
The prompt displays default text in brackets. Press Enter to use the default value and go to the next
prompt.
Property Description
Database Type The type of database. For an Oracle database, specify Oracle. The
database type must be the same as the database type selected for the
MDM Hub Master Database and the Operational Reference Stores.
Oracle Connection Type Connection type. Use one of the following values:
- SERVICE. Uses the service name to connect to Oracle.
- SID. Uses the Oracle System ID to connect to Oracle.
ActiveVOS Database Host Name Name of the machine that hosts the database.
ActiveVOS Database Port Port number that the database listener uses.
Database Service Name Name of the Oracle service. This property is required when the
selected Oracle connection type is SERVICE.
Oracle Net Connect Identifier Oracle TNS name.

(TNS Name)
Database SID Name of the Oracle System ID. This property is required when the
selected Oracle connection type is SID.
DBA User Name User name of the database administrative user.
DBA Password Password of the administrative user.
ActiveVOS User Name User name of the ActiveVOS Server administrative user.
ActiveVOS User Password Password of the administrative user.
ActiveVOS User Tablespace The name of the tablespace that contains the records that are involved
in MDM workflows.
ActiveVOS User Temp The name of the temporary tablespace.

Tablespace
5. After you create the schema, review sip_ant.log in the following directory:
The sip_ant.log file logs any errors that might occur when you run the sip_ant script to create the
ActiveVOS database schema.
46 Chapter 3: ActiveVOS Pre-Installation Tasks

Create an Administrative User in WebLogic
Environments
Add the ActiveVOS Console administrative user with the role abAdmin in the application server. If you do not
add an administrative user, the deployment fails.
1. In the WebLogic console, create the abAdmin role.

2. In the WebLogic console, create the ActiveVOS Console administrative user, and then assign the user to
the abAdmin role.
3. Restart the application server.
Create an Administrative User in WebLogic Environments 47

CHAPTER 4
Hub Store Installation

• Create the MDM Hub Master Database, 48

• Create an Operational Reference Store, 50
• Import the Metadata into the MDM Hub Master Database, 52
• Import the Metadata into the Operational Reference Store, 53
Create the MDM Hub Master Database

After you install Oracle, you must create an MDM Hub Master Database. The default name of the MDM Hub
Master Database is CMX_SYSTEM.
Note: If you change the folder names in the distribution directory, metadata import fails.

3. To create the MDM Hub Master Database, run the following command:
On UNIX. sip_ant.sh create_system
On Windows. sip_ant.bat create_system
4. Answer the prompts described in the following table:
48
Note: The prompt displays default text in brackets. Press Enter to use the default value and go to the
next prompt.
Prompts Description
Enter the database type (ORACLE, MSSQL, Database type. Specify ORACLE.
DB2)
Enter Oracle Connection Type (service, sid). Connection type. Use one of the following values:
[service] - SERVICE. Uses the service name to connect to Oracle.
Default is SERVICE.
Enter the database host name [localhost] Name of the host that is running the database. Default is
localhost.
Enter the database port number [1521] Port number that the database listener uses. Default is
1521.
Enter the MDM Hub Master Database schema Name of the MDM Hub Master Database schema. Defaut
name [cmx_system] is cmx_system.
Enter the MDM Hub Master Database user User name to access the MDM Hub Master Database.
name [cmx_system] Defaut is cmx_system.
Enter the MDM Hub Master Database user Password to access the MDM Hub Master Database.
password
Enter the database service name [orcl] Name of the Oracle service. This prompt is displayed if
the selected Oracle connection type is SERVICE. Default
is orcl.
Enter Oracle Net connect identifier (TNS TNS name that is used to connect to the Oracle
Name). [orcl] database. Default is orcl.
Master Database Connect URL: Connect URL for the Oracle connection type SERVICE.
"jdbc:oracle:thin:@//<host_name>:<port>/ You can type y to change the default connect URL. To
<service_name>". use the default connect URL, type n.
Do you want to change the connect URL (y/n)
[n]
Enter database SID [orcl] Name of the Oracle System ID. This prompt is displayed
if the selected Oracle connection type is SID.
Enter locale name from the list: de, en_US, fr, Operating system locale. Default is en_US.
ja, ko, zh_CN. [en_US]
Enter the DBA user name [SYS] User name of the administrative user. Default is SYS.
Enter the DBA password Password of the administrative user.
Enter the name of the MDM index tablespace Name of the tablespace to contain the index components
[CMX_INDX] for the MDM Hub Master Database. Default is
CMX_INDX.
Create the MDM Hub Master Database 49

Prompts Description
Enter the name of the MDM temporary Name of the tablespace to contain the temporary
tablespace (Not an Oracle temporary components for the MDM Hub Master Database. Default
tablespace) [CMX_TEMP] is CMX_TEMP.
Enter the name of the Oracle temporary Name of the Oracle temporary tablespace. Default is
tablespace [TEMP] TEMP.
5. To verify that the MDM Hub Master Database was created successfully, review sip_ant.log in the
following directory:
MDM Hub Master Database.
Create an Operational Reference Store

After you complete the pre-installation tasks, you can create an Operational Reference Store. The default
name of the Operational Reference Store is CMX_ORS.

On UNIX. sip_ant.sh create_ors
On Windows. sip_ant.bat create_ors
next prompt.
Prompts Description
Enter the database type (ORACLE, MSSQL, DB2) Database type. Specify ORACLE.
[service] - SERVICE. Uses the service name to connect to Oracle.
Default is SERVICE.
50 Chapter 4: Hub Store Installation

Prompts Description
Enter the Operational Reference Store schema Name of the host that is running the database. Default
host name [localhost] is localhost.
Enter the Operational Reference Store schema Port number that the database listener uses. Default is
port number [1521] 1521.
Enter the Operational Reference Store database Name of the Oracle service. This prompt is displayed if
service name [orcl] the selected Oracle connection type is SERVICE.
Enter Oracle Net connect identifier (TNS Name) Oracle TNS name. Default is orcl.
[orcl]
Master Database Connect URL: Connect URL for the Oracle connection type
"jdbc:oracle:thin:@//<host_name>:<port>/ SERVICE. You can type y to change the default
<service_name>". connect URL. To use the default connect URL, type n.
Do you want to change the connect URL (y/n) [n]
Enter database SID [orcl] Name of the Oracle System ID. This prompt is
displayed if the selected Oracle connection type is
SID.
Enter the Operational Reference Store schema Name of the Operational Reference Store database.
name [cmx_ors] Default is cmx_ors.
Enter the Operational Reference Store schema User name to access the Operational Reference
user name [cmx_ors] Store. Default is cmx_ors.
Enter the Operational Reference Store schema Password to access the Operational Reference Store.
user password
Enter locale name from the list: de, en_US, fr, ja, Operating system locale.
ko, zh_CN. [en_US]
Enter the DBA user name [SYS] User name of the administrative user. Default is SYS.
Enter the DBA password Password of the administrative user.
Enter the name of the MDM index tablespace Name of the tablespace to contain the index
[CMX_INDX] components for the Operational Reference Store.
Default is CMX_INDX.
Enter the name of the MDM temporary tablespace Name of the tablespace to contain the temporary
(Not an Oracle temporary tablespace) components for the Operational Reference Store.
[CMX_TEMP] Default is CMX_TEMP.
Enter the name of the Oracle temporary Name of the Oracle temporary tablespace. Default is
tablespace [TEMP] TEMP.
5. To verify that the Operational Reference Store was created successfully, review sip_ant.log in the
Create an Operational Reference Store 51

Import the Metadata into the MDM Hub Master
Database
After you create the MDM Hub Master Database, import the initial metadata into the MDM Hub Master
Database. The initial metadata includes repository tables and other objects that the MDM Hub requires in the
Hub Store.

3. To import the initial metadata, run the following command:
On UNIX. sip_ant.sh import_system
On Windows. sip_ant.bat import_system
next prompt.
Prompts Description
DB2)
[service] SERVICE
Uses the service name to connect to Oracle.
SID
Uses the Oracle System ID to connect to Oracle.

Default is SERVICE.
Enter the database host name [localhost] Name of the host that is running the database.
Enter the database port number [1521] Port number that the database listener uses. Default is
1521.
Enter the MDM Hub Master Database service Name of the Oracle service. This prompt is displayed if the
name [orcl] selected Oracle connection type is SERVICE. Default is
orcl.
Enter Oracle Net connect identifier (TNS TNS name that is used to connect to the Oracle database.
Name). [orcl] Default is orcl.

Prompts Description
"jdbc:oracle:thin:@//<host_name>:<port>/ You can type y to change the default connect URL. To use
<service_name>". the default connect URL, type n.
[n] :
Enter database SID Name of the Oracle System ID. This prompt is displayed if
the selected Oracle connection type is SID.
Enter the MDM Hub Master Database Name of the MDM Hub Master Database schema. Default
schema name [cmx_system] is cmx_system.
Enter the MDM Hub Master Database User name to access the MDM Hub Master Database.
schema user name [cmx_system] Default is cmx_system.
Enter the MDM Hub Master Database Password to access the MDM Hub Master Database.
schema user password
Enter locale name [en_US] Operating system locale. Default is en_US. Default is
en_US.
5. After you import the initial metadata, review the following log files for errors:
• seed.log. Contains database errors.
The seed.log file is in the following directory:
On UNIX. <distribution directory>/database/bin/oracle
On Windows. <distribution directory>\database\bin\oracle
• sip_ant.log. Contains user input errors.
The sip_ant.log file is in the following directory:
Import the Metadata into the Operational Reference

Store
After you create the Operational Reference Store, import the initial metadata into the Operational Reference
Store. The initial metadata includes repository tables and other objects that the MDM Hub requires in the Hub
Store.

3. To import the initial metadata, run the following command:
Import the Metadata into the Operational Reference Store 53

On UNIX. sip_ant.sh import_ors
On Windows. sip_ant.bat import_ors
next prompt.
Prompts Description
DB2)
[service] SERVICE
Uses the service name to connect to Oracle.
SID
Uses the Oracle System ID to connect to Oracle.

Default is SERVICE.
Enter the Operational Reference Store schema Name of the host that is running the database.
host name [localhost]
Enter the Operational Reference Store schema Port number that the database listener uses. Default is
port number [1521] 1521.
Enter the Operational Reference Store Name of the Oracle service. This prompt is displayed if
database service name the selected Oracle connection type is SERVICE.
Enter Oracle Net connect identifier (TNS TNS name that is used to connect to the Oracle
Name). [orcl] database. Default is orcl.
"jdbc:oracle:thin:@//<host_name>:<port>/ You can type y to change the default connect URL. To
<service_name>". use the default connect URL, type n.
[n] :
Enter database SID Name of the Oracle System ID. This prompt is displayed
if the selected Oracle connection type is SID.
Enter the Operational Reference Store schema Name of the Operational Reference Store database.
name [cmx_ors] Default is cmx_ors.
Enter the Operational Reference Store schema User name to access the Operational Reference Store.
user name [cmx_ors] Default is cmx_ors.
Enter the Operational Reference Store schema Password to access the Operational Reference Store.
user password

Prompts Description
Enter locale name [en_US] Operating system locale. Default is en_US.
Enter the integer code of Operational Reference Specify timeline units to use. Default is days.
Store Timeline Granularity: Year 5, Month 4, Note: The timeline granularity that you configure cannot
Day 3, Hour 2, Minute 1, Second 0 [3] be modified later.
For more information about timeline, see the Informatica
MDM Multidomain Edition Configuration Guide.
5. After you import the initial metadata, review the following log files for errors:
• seed.log. Contains database errors.
The seed.log file is in the following directory:
On UNIX. <distribution directory>/database/bin/oracle
On Windows. <distribution directory>\database\bin\oracle
• sip_ant.log. Contains user input errors.
The sip_ant.log file is in the following directory:
Import the Metadata into the Operational Reference Store 55

CHAPTER 5
Hub Store Post-Installation Tasks

This chapter includes the following topic:
• Verify Access to Oracle Components, 56
Verify Access to Oracle Components

If you have a custom Oracle environment, ensure that the Hub Store has access to the required Oracle
components.
The Hub Store requires access to the following Oracle components:
• Oracle Java Virtual Machine

• Oracle XML Database
• ALL_CONSTRAINTS
• ALL_CONS_COLUMNS
• ALL_DIRECTORIES
• ALL_INDEXES
• ALL_IND_COLUMNS
• ALL_JOBS (used for migration)
• ALL_TABLES
• ALL_TAB_COLUMNS
• ALL_VIEWS
• DBMS_APPLICATION_INFO
• DBMS_JOB
• DBMS_OUTPUT
• DBMS_STANDARD
• DBMS_SQL
• DBMS_STATS
• DBMS_UTILITY
• DUAL
• PLITBLM
• STANDARD
56
• SYS_STUB_FOR_PURITY_ANALYSIS
• USER_CONSTRAINTS
• USER_CONS_COLUMNS
• USER_EXTERNAL_TABLES
• USER_INDEXES
• USER_JAVA_POLICY
• USER_OBJECTS
• USER_SEQUENCES
• USER_SOURCE
• USER_TABLES
• USER_TAB_COLS
• USER_TAB_COLUMNS
• USER_TRIGGERS
• UTL_FILE
• V$NLS_PARAMETERS
• V$VERSION
Verify Access to Oracle Components 57

CHAPTER 6
Hub Server Installation

• Installing the Hub Server in Graphical Mode, 58

• Installing the Hub Server in Console Mode, 61
• Installing the Hub Server in Silent Mode, 63
• Installing the Hub Server on Environments with Managed Servers, 68
Installing the Hub Server in Graphical Mode

You can install the Hub Server in graphical mode.
You must use the same user name to install the Hub Server and the Process Server. If you install the Hub
Server and the Process Server on the same machine, the users who install them must belong to the same
UNIX group.
1. Start the application server.

2. Open a command prompt and navigate to the Hub Server installer in the distribution directory.
By default, the installer is in the following directory:
On UNIX. <distribution directory>/<operating system name>/mrmserver
On Windows. <distribution directory>\windows\mrmserver
On UNIX. ./hub_install.bin
On Windows. hub_install.exe
4. Select the language for the installation, and then click OK.
The Introduction window appears.
5. Click Next.
The License Agreement window appears.
6. Select the I accept the terms of the License Agreement option, and then click Next.
The Choose an Install Folder window appears.
7. Select the location of the Hub Server installation.
• To choose the default location, click Next.
• To enter a path, type the path to the installation folder, and click Next.
58
Note: The installation fails if you specify a path that has spaces in the directory or folder names.
• To choose another location, click Choose, and then click Next.
8. On UNIX, choose a link folder or select the option to not create links and click Next. On Windows, select
the location to create a product icon or select the option not to create a product icon.
9. Click Next.
The Enter the location of the license file window appears.
10. Click Choose to select a license file, and click Next.
The Application Server window appears.
11. Select WebLogic, and then click Next.
The WebLogic Application Server Home window appears.
12. Configure the following WebLogic Server settings:
a. Choose a path to the WebLogic domain installation directory for the domain that you want to use for
the MDM Hub. Click Next.
The WebLogic Application Server Login window appears.
b. Enter the following WebLogic Server login information:
Field Name Description
Host Name of the host computer that has the WebLogic installation.
Server Name of the WebLogic Server instance in the domain on which WebLogic is deployed.
User Name Name of the user for the WebLogic installation.
Password Password that corresponds to the WebLogic user.
Port Number Port number on which the WebLogic Server is listening.
13. Click Next.

The Database Selection window appears.
14. Select the Oracle version, and click Next.
The Oracle Database Connection Type Selection window appears.
15. Select the Service Name or SID connection type, and click Next.
The Oracle Database Information window appears.
16. Enter the following settings for the Oracle database to which you want to connect, and click Next:
Server Host name of the MDM Hub Master Database server.
Port Port number of the MDM Hub Master Database.
Service Name or Oracle Specify the connection type that you select when you create the MDM Hub
SID Master Database.
Installing the Hub Server in Graphical Mode 59

System Schema Name of the MDM Hub Master Database.
System Schema Password of the system schema user to connect to the MDM Hub Master
Password Database.
17. Click Next.

If the selected Oracle connection type is Service Name, then the Customization of Connect URL
window appears.
18. Select one of the following connection URL customization options:
• Yes. You can enter a custom connect URL to connect to the MDM Hub Master Database.
• No. The default URL that the MDM Hub installer generates based on the Oracle server, port, and
service name is used to connect to the MDM Hub Master Database.
The Install ActiveVOS window appears.
19. Change the connect URL if required, and click Next.
20. If you want to install the bundled, licensed version of Informatica ActiveVOS, select Yes and perform the
following substeps. Otherwise, select No, and click Next.
a. On the ActiveVOS Installer page, click Choose and browse to the ActiveVOS_Server installation
file in the distribution package. Click Next.
b. On the Choose ActiveVOS Installation Folder page, accept the default installation path or specify
a preferred location. Click Next.
c. On the Database Information page, enter the details that you specified when you created the
ActiveVOS database schema. Click Next.
d. On the Application Server Web URL page, accept the default URL or specify the URL that you
want to use to call ActiveVOS web services. Ensure the URL contains the correct port number for
the connection to the application server. Click Next.
The post installation setup script uses the URL to call ActiveVOS web services, deploy the
predefined MDM workflows to ActiveVOS, and create the URN mapping.
e. Enter a user name and password to create an administrative user for the ActiveVOS Console.
Important: The user name and password must be the same as the ActiveVOS Console user name
and password that was created in the application server.
f. Click Next.
21. Select one of the following Informatica platform installation options:
• Yes. Install Informatica platform.
• No. Does not install Informatica platform.
22. If you select Yes in the preceding step, click Choose and browse to the following Informatica platform
file locations:
• Installation response file
• Platform installation file
23. On the Product Usage Toolkit page, select the Environment Type.
24. If you want to use a proxy server, select Yes, and enter the proxy server details. Otherwise, select No.
60 Chapter 6: Hub Server Installation

You can enter the following proxy server details:
• Proxy server name/IP
• Proxy server port
• Proxy server domain name. Leave blank if not applicable.
• Proxy server user name. Leave blank if not applicable.
• Proxy server password. Leave blank if not applicable.
25. Click Next.
The Deploy page appears.
26. Select one of the following post installation setup script options:
• Yes, run the script during this installation. Runs the post installation script during the installation.
• No, I will run it later. Allows you to manually run the post installation script later.
27. Click Next.
The Pre-Installation Summary window appears.
28. After the Pre-Installation Summary window displays the options you want, click Install to start the
installation process.
When the installation completes, the Install Complete window appears.
29. Click Done to exit the Hub Server installer.
Installing the Hub Server in Console Mode

You can install the Hub Server in console mode on UNIX.

2. Navigate to the following directory in the MDM Hub distribution:
3. Run the following command from the command prompt:
./hub_install.bin -i console
4. Enter the number of the locale you want to choose for the installation, and then press Enter.
The introduction information about the installation appears.
5. Press Enter.
The license agreement appears.
6. Read the License Agreement. Type Y to accept the terms of the license agreement, or type N if you do
not want to accept the license agreement and want to exit the installation program.
7. Press Enter.
If you entered Y in the preceding step, information about the installation folder appears.
8. Choose a folder for the Hub Server installation.
• To choose the default folder, press Enter.
• To change the path, type the absolute path of the installation folder, and press Enter.
9. Confirm the location of the installation folder. Type Y to confirm the installation folder, or type N to
change the installation folder.
Installing the Hub Server in Console Mode 61

10. Press Enter.
A list of link location options appears.
11. Enter the number of a link location option.
The prompt for the license file location appears.
12. Enter the absolute path of the license file, and press Enter.
A list of application server options appears.
13. Enter the number for the application server that you want to select, and press Enter.
The application server information appears.
14. Configure the WebLogic settings.
a. Specify the path to the WebLogic domain in which you want to install the Hub Server, and press
Enter.
The prompts for the WebLogic application server login information appears.
b. Enter the host name, server name, user name, password, and listener port for the WebLogic Server,
or accept the default values, and press Enter.
15. Press Enter.
The database selection prompt appears.
16. Select Oracle, and press Enter.
17. Select the Oracle database connection type you want, Service Name or SID, and press Enter.
18. Specify the settings for the Oracle database to which you want to connect.
Press Enter to accept the default values, or replace the defaults with the correct values. The settings
include, server name, port number, Service Name or Oracle SID, the MDM Hub system master schema
name such as CMX_SYSTEM, and system schema password for the system schema user name.
19. Press Enter.
20. If the selected Oracle connection type is Service Name, then the installer prompts you to confirm or
change the connect URL. Change the system-generated URL if required, and press Enter.
21. If you want to install the bundled, licensed version of the ActiveVOS Server, press Enter for Yes.
Otherwise, type 2 for No and press Enter.
If you selected Yes, the installer prompts you to provide information about your ActiveVOS installation.
a. Specify the location of the ActiveVOS Server installation file.
b. Specify the location where you want to install the ActiveVOS Server.
c. Enter information about the ActiveVOS database that you specified when you created the
ActiveVOS schema.
d. Specify the URL that you want to use to call MDM and ActiveVOS web services.
e. Enter a user name and password to create an administrative user for the ActiveVOS Server
Administration Console.
22. Press Enter.
The Informatica platform installation prompt appears.
23. If you want to install the Informatica platform, press Enter for Yes. Otherwise, type 2 for No and press
Enter.
The prompts for the Informatica platform installation response file and archive file locations appear.

24. Enter the locations of the Informatica platform installation response file and archive file, and press Enter.
25. From the Product Usage Toolkit options, select the environment type. Type 1 for Production, type 2 for
Test/QA, or type 3 for Development, and then press Enter.
26. Select whether you have a proxy server. Press Enter for Yes. Otherwise, type 2 for No and then press
Enter.
The summary of the installation choices appears.
27. Choose whether you want to run the postInstallSetup script as part of the installation, or run it
manually later.
28. Verify the information in the pre-installation summary. If the information is correct, press Enter to start
the installation.
The Hub Server is installed according to the configuration information you provide. When the process is
complete, the installation complete message appears.
29. Press Enter to exit the installer.
Installing the Hub Server in Silent Mode

You can install the Hub Server without user interaction in silent mode. You might want to perform a silent
installation if you need multiple installations, or if you need to install on a machine cluster. A silent installation
does not show any progress or failure messages.
Before you run the silent installation for the Hub Server, you must configure the properties file for the silent
installation. The installer reads the file to determine the installation options. The silent installation process
might complete successfully even if you provide incorrect settings, such as an incorrect application server
path or port. You must ensure that you provide correct settings in the properties file.
Copy the Hub Server installation files to the hard disk on the machine where you plan to install the Hub
Server. To install in silent mode, complete the following tasks:
1. Configure the installation properties file and specify the installation options in the properties file.
2. Run the installer with the installation properties file.
Installing the Hub Server in Silent Mode 63

Configuring the Properties File
Informatica provides a sample properties file that includes the parameters that the installer requires. You can
customize the sample properties file to specify the options for the installation. Then run the silent installation.
The silent installer does not validate the settings in the properties files. You must ensure that you specify
correct settings and verify them before you run the silent installer.
1. Find the silentInstallServer_sample.properties file in the following directory:

On UNIX. /silent_install/mrmserver
On Windows. \silent_install\mrmserver
After you customize the file, re-save it. You can rename the file and put it anywhere on the machine.
Note: In the silent properties file, slash and backslash are special characters. You must enter two of
each of these characters when you enter information in the file, such as when you enter an installation
path. For example, to enter the path to the server directory, you must enter \\u1\\infamdm\\hub\
\server.
2. Create a backup copy of the silentInstallServer_sample.properties file.
3. Use a text editor to open the file and change the values of the installation parameters.
4. Save the properties file with a new name such as silentInstallServer.properties.
The following table describes the installation parameters that you can modify:
Property Name Description
INSTALLER_UI Specifies the type of installation. Set to silent.
USER_INSTALL_DIR Directory where you want to install Hub Server.

For example, C\:\\<infamdm_install_directory>\\hub\
\server.
SIP.LICENSE.PATH Path to the Informatica license file.
SIP.LICENSE.FILENAME License file name. Set to siperian.license.
SIP.AS.CHOICE Name of the application server. Specify WebLogic.
SIP.AS.HOME The path to the WebLogic installation directory.
SIP.APPSERVER.HOST Host name such as localhost.
SIP.APPSERVER.SERVER Admin Server name such as AdminServer.
SIP.APPSERVER.USERNAME User name to access WebLogic.
SIP.APPSERVER.PASSWORD Password to access WebLogic.
WEBLOGIC.AS.PORT Application server port number.
SIP.DB.CHOICE Name of the database server. Specify Oracle.

SIP.ORACLE.CONNECTION.TYPE Oracle connection type. Specify one of the following values:

Service Name
The Hub Server uses the service name to connect to Oracle.
SID
The Hub Server uses the Oracle system ID to connect to Oracle.
SIP.DB.SERVER Host name of the database server.
SIP.DB.PORT Database server port number.
SIP.DB.SID If SIP.ORACLE.CONNECTION.TYPE is SID, then set the

SIP.DB.SID property to the Oracle database system ID. Otherwise,
set the SIP.DB.SID property to the Oracle service name.
SIP.DB.SCHEMA_NAME Schema name of the MDM Hub Master Database.
SIP.DB.PASSWORD Password of the user used to connect to the system schema.
AVOS.INSTALL Specifies whether you want to install Informatica ActiveVOS or not.

If you want to install Informatica ActiveVOS, set the property to Yes.
Otherwise, set to No.
AVOS_INSTALLER_PATH The path to the ActiveVOS Server installer.
AVOS_INSTALL_DIR The path to the location where you want to install the ActiveVOS Server.
AVOS.ORACLE.CONNECTION.TYPE Oracle connection type. Specify one of the following values:

Service Name
The Hub Server uses the service name to connect to Oracle.
SID
The Hub Server uses the Oracle system ID to connect to Oracle.
AVOS.DB.SERVER Name of the machine that hosts the ActiveVOS database.
AVOS.DB.PORT Port number that the database listener uses.
AVOS.DB.SID Name of the Oracle System ID or the name of the Oracle service.
AVOS.DB.SCHEMA_NAME Name of the ActiveVOS database schema. Default is avos.
AVOS.DB.PASSWORD Password of the administrative user.
SIP.APPSERVER.WEB.URL URL to the application server in the following format:

http://[server]:[port]
AVOS.CONSOLE.USER User name of the ActiveVOS server administrator. The user name must
be the same as the ActiveVOS Console user name that was created in
the application server during the pre-installation process.

AVOS.CONSOLE.PASSWORD Password of the ActiveVOS server administrator. The password must be

the same as the ActiveVOS Console password that was created in the
application server during the pre-installation process.
INSTALL.PLATFORM.YES Specifies whether you want to install Informatica platform or not.

If you want to install Informatica platform, set the property to 1.
Otherwise, set to 0.
INFA.PLATFORM.ZIP Path to the compressed Informatica platform installer.
INFA.PLATFORM.PROPERTIES Path to the Informatica platform installation properties file that you
create.
RUN_DEPLOYMENT_FLAG Runs the postInstallSetup script as part of the silent installation. Set to 1
if you want to run postInstallSetup. Set to 0 if you do not want to run
postInstallSetup at the end of the silent installation.
If you install ActiveVOS, you must set to 0 to configure ActiveVOS
security after the installation.
CSM_TYPE The type of product usage toolkit installation. Can be Production, Test,
or Development. Default is Production.
CSM_HOST Name of the proxy server host. Leave blank if the environment does not
have a proxy server.
CSM_PORT Proxy server port. Leave blank if the environment does not have a proxy
server.
CSM_DOMAIN Name of the proxy server domain. Leave blank if the environment does
not have a proxy server or if the domain name is not required.
CSM_PROXY_USER_NAME Proxy server user name. Leave blank if the environment does not have a
proxy server or if the proxy server user name is not required.
CSM_PROXY_PASSWORD Proxy server password. Leave blank if the environment does not have a
proxy server or if the proxy server password is not required.
Sample Properties File

The following example shows the contents of the sample silentInstallServer_sample.properties file:
## Command to run silent install
## For Windows: hub_install.exe -f <property_file>
## For Unix: hub_install.bin -f <property_file>
INSTALLER_UI=silent
## Hub Server Install directory.

USER_INSTALL_DIR=C\:\\infamdm\\hub\\server
## License path and filename

SIP.LICENSE.PATH=C\:\\
SIP.LICENSE.FILENAME=siperian.license
## Properties for WebLogic application server

SIP.AS.CHOICE="WebLogic"

SIP.AS.HOME=C\:\\bea\\user_projects\\domains\\base_domain
SIP.APPSERVER.HOST=localhost
SIP.APPSERVER.SERVER=AdminServer
SIP.APPSERVER.USERNAME=weblogic
SIP.APPSERVER.PASSWORD=weblogic
WEBLOGIC.AS.PORT=7001
## Properties for Oracle server

SIP.DB.CHOICE="Oracle
"SERVICE_NAME_SELECTED_RESULT=1
SIP.DB.SERVER=localhost
SIP.DB.PORT=1521
SIP.DB.SID=orcl
SIP.DB.SCHEMA_NAME=cmx_system
SIP.DB.PASSWORD=!!cmx!!
## Do you want to install ActiveVOS (Yes/No)

AVOS.INSTALL=Yes
## Path to ActiveVOS Installer (ActiveVOS_Server_windows_9.2.4.1.exe for Windows or
ActiveVOS_Server_unix_9.2.4.1.sh for Linux/UNIX)
AVOS_INSTALLER_PATH=c\:\\ActiveVOS_Server_windows_9.2.4.1.exe
## ActiveVOS server install directory
AVOS_INSTALL_DIR=C\:\\infamdm\\avos\\server
## Database type is the same as for HUB (There is no ability to set a different
database type for ActiveVOS)
## Oracle connection data
## Connection Type SID or Service Name
AVOS.ORACLE.CONNECTION.TYPE="Service Name"
AVOS.DB.SERVER=psraxmdmqa1
AVOS.DB.PORT=1521
## Oracle SID name or service name
AVOS.DB.SID=MDMAIX.informatica.com
AVOS.DB.SCHEMA_NAME=av1
AVOS.DB.PASSWORD=INFAdba1
##If you are moving from standalone ActiveVOS to embedded ActiveVOS, enter the details
for the standalone ActiveVOS schema.
SIP.APPSERVER.WEB.URL=http://localhost:8080
## Avos console's administrator username
AVOS.CONSOLE.USER=aeadmin
## Avos console's administrator password
AVOS.CONSOLE.PASSWORD=admin
##The user name and password must be the same as the ActiveVOS Console user name and
password
that was created in the application server during the pre-installation process.
## If you want to install Informatica Platform, set to 1

## If you DO NOT want to install Informatica Platform, set to 0
INSTALL.PLATFORM.YES=1
## Path to the Informatica Platform installer (zip or tar file)

INFA.PLATFORM.ZIP=C\:\\961HF1_Server_Installer_winem-64t.zip
## For UNIX: INFA.PLATFORM.ZIP=/export/home/user/961HF1_Server_Installer_linux-x64.tar
## Path to silent installer properties file

INFA.PLATFORM.PROPERTIES=C\:\\SilentInput.properties
## If you want to run postInstallSetup as a part of silent install, then set following
property.
## set RUN_DEPLOYMENT_FLAG to 1 if you want to run postInstallSetup
## or set RUN_DEPLOYMENT_FLAG to 0 if you do not want to run postInstallSetup
RUN_DEPLOYMENT_FLAG=1
#Product Usage Toolkit Installation

#CSM_TYPE is the type of Product Usage Toolkit installation.
# valid values are:Production,Test,Development. Should not be blank.
CSM_TYPE=Production
# If the network has a proxy server, fill in the following parameters (leave empty if
no proxy):
# proxy server host
CSM_HOST=
# proxy server port
CSM_PORT=
# Proxy server domain name (leave blank, if not applicable)
CSM_DOMAIN=
# Proxy server user name (leave blank, if not applicable)
CSM_PROXY_USER_NAME=
#Proxy server password (leave blank, if not applicable)
CSM_PROXY_PASSWORD=
Running the Silent Installer

After you configure the properties file, you can start the silent installation.
1. Ensure that the application server is running.

2. Open a command window.
On UNIX. ./hub_install.bin -f <location_of_silent_properties_file_for_hub_server>
On Windows. hub_install.exe -f <location_of_silent_properties_file_for_hub_server>
The silent installer runs in the background. The process can take a while. If you ran the postInstallSetup
script for the Hub Server as part of the silent installation, check the postinstallSetup.log files to verify that
the installation was successful.
The log file is available in the following directory:
On UNIX. <infamdm_install_directory>/hub/server/logs/
On Windows. <infamdm_install_directory>\hub\server\logs\
Installing the Hub Server on Environments with

Managed Servers
If you have an environment with an Administration Server and Managed Servers, install the Hub Server on
the Administration Server and on each Managed Server. You can install on clustered or a nonclustered
environments.
Ensure that the directory structure of the Hub Server installation is the same on all the nodes.
1. Start the WebLogic Administration Server and the Managed Servers on all the machines.
2. Open a command prompt and navigate to the Hub Server installer in the distribution directory.
By default, the installer is in the following directory:
On Windows. <distribution directory>\windows\mrmserver
3. To start the Hub Server installer, run the following command:

On UNIX. ./hub_install.bin -DSIPERIAN_INSTALL_PREREQ_VALIDATION=false
On Windows. hub_install.exe -DSIPERIAN_INSTALL_PREREQ_VALIDATION=false
You must start the Hub Server installer on the Administration Server and all the Managed Servers in the
cluster.
5. Click Next.
The Choose an Install Folder window appears.
7. Select the location of the Hub Server installation.
8. On UNIX, choose a link folder or select the option to not create links and click Next. On Windows, select
9. Click Next.
The Enter the location of the license file window appears.
the MDM Hub. Click Next.
b. Enter the following WebLogic Server login information:
Host Name of the host computer that has the WebLogic installation.
Port Number Port number on which the Administration Server is listening.
13. Click Next.

The Database Selection window appears.
14. Select the Oracle version, and click Next.
Installing the Hub Server on Environments with Managed Servers 69

The Oracle Database Connection Type Selection window appears.
15. Select the Service Name or SID connection type, and click Next.
The Oracle Database Information window appears.
16. Enter the following settings for the Oracle database to which you want to connect, and click Next:
Server Host name of the MDM Hub Master Database server.
Port Port number of the MDM Hub Master Database.
Service Name or Oracle Specify the connection type that you select when you create the MDM Hub
SID Master Database.
System Schema Name of the MDM Hub Master Database.
System Schema Password of the system schema user to connect to the MDM Hub Master
Password Database.
17. Click Next.

If the selected Oracle connection type is Service Name, then the Customization of Connect URL
window appears.
18. Select one of the following connection URL customization options:
• Yes. You can enter a custom connect URL to connect to the MDM Hub Master Database.
• No. The default URL that the MDM Hub installer generates based on the Oracle server, port, and
service name is used to connect to the MDM Hub Master Database.
19. Change the connect URL if required, and click Next.
20. If you want to install the bundled, licensed version of Informatica ActiveVOS, select Yes and perform the
following substeps. Otherwise, select No, and click Next.
a. On the ActiveVOS Installer page, click Choose and browse to the ActiveVOS_Server installation
file in the distribution package. Click Next.
b. On the Choose ActiveVOS Installation Folder page, accept the default installation path or specify
a preferred location. Click Next.
c. On the Database Information page, enter the details that you specified when you created the
ActiveVOS database schema. Click Next.
d. On the Application Server Web URL page, accept the default URL or specify the URL that you
want to use to call ActiveVOS web services. Ensure the URL contains the correct port number for
the connection to the application server. Click Next.
The post installation setup script uses the URL to call ActiveVOS web services, deploy the
predefined MDM workflows to ActiveVOS, and create the URN mapping.
e. Enter a user name and password to create an administrative user for the ActiveVOS Console.
f. Click Next.

21. Select one of the following Informatica platform installation options:
• Yes. Install Informatica platform.
• No. Does not install Informatica platform.
22. If you select Yes in the preceding step, click Choose and browse to the following Informatica platform
file locations:
• Installation response file
• Platform installation file
24. If you want to use a proxy server, select Yes, and enter the proxy server details. Otherwise, select No.
25. Click Next.
26. Select the No, I will run it later post installation setup script option.
The No, I will run it later option allows you to manually run the post installation setup script later.
27. Click Next.
28. Click Next.
29. After the Pre-Installation Summary window displays the options you want, click Install to start the
installation process.
30. Click Done to exit the Hub Server installer.
If you use the development cluster IP, you can access the Hub Server through the nodes in the cluster. If you
use the production cluster IP, you can use the cluster names to access the Hub Server. After you start the
Hub Server application, the EJB clustering distributes requests between the Managed Servers and manages
failovers.
Installing the Hub Server on Environments with Managed Servers 71

CHAPTER 7
Hub Server Post-Installation

Tasks
• Copy the Installation Log Files, 73

• Verify the Version and Build Number, 75
• Configure the Hub Server, 76
• Configure the Hub Server on Environments with Managed Servers, 77
• Running the Post Install Script Manually, 81
• Manually Redeploying the Hub Server Application, 81
• Manually Creating Data Sources, 82
• Manually Configuring JMS Message Queues, 83
• Improve API Performance on JBoss AS 7.2 , 86
• Configure WebLogic for Secure ActiveVOS Communication, 87
• Changing the Operational Reference Store User Password, 87
• Repackaging Custom JAR Files, 87
• Restart WebLogic, 88
• Configure JBoss Cache, 88
• Configure Logging for Informatica Platform, 89
72
• Starting the Hub Console, 90
• Registering an Operational Reference Store, 90
Copy the Installation Log Files

The installation log files are useful for troubleshooting the Hub Server installation process. Copy the log files
to the installation documentation directory. Informatica Global Customer Support might request copies of the
log files if you contact them regarding installation issues.
Installation Log File

The installation log file contains information about the installed files.
The following table describes the properties of the installation log file:
File Name Informatica_MDM_Hub_Server_Install_<timestamp>.xml
Location On UNIX. <infamdm_install_directory>/hub/server/UninstallerData/Logs

On Windows. <infamdm_install_directory>\hub\server\UninstallerData\Logs
Usage Get information about the files installed and registry entries created.
Contents Directories created, names of the files installed and commands run, and status for each installed file.
Installation Prerequisites Log File

The installation prerequisites log file contains information about the prerequisite checks that the installer
performs.
The following table describes the properties of the installation prerequisites log file:
File Name installPrereq.log
Location On UNIX. <infamdm_install_directory>/hub/server/Logs

On Windows. <infamdm_install_directory>\hub\server\Logs
Usage Get information about the prerequisite checks performed by the installer.
Contents Logs of prerequisite validation checks.
Copy the Installation Log Files 73

Debug Log File
The installer writes actions and errors to the debug log file.
The following table describes the properties of the debug log file:
File Name infamdm_installer_debug.txt
Location On UNIX. <infamdm_install_directory>/hub/server/

On Windows. <infamdm_install_directory>\hub\server\
Usage Get information about the choices that are made during installation.
Contents Detailed summary of actions performed by the installer.
Post-Installation Setup Log File

The post-installation log file contains information about the post-installation process.
The following table describes the properties of the post-installation setup log file:
File Name postInstallSetup.log
Location On UNIX. <infamdm_install_directory>/hub/server/logs

On Windows. <infamdm_install_directory>\hub\server\logs
Usage Get information about the post-installation actions performed by the installer and get information
about the errors in the post-installation process.
Contents Summary of actions performed by the installer during the post-installation process.
Hub Server Log File

The Hub Server log file contains information about Hub Server operations.
The following table describes the properties of the Hub Server log file:
File Name cmxserver.log
Location On UNIX. <infamdm_install_directory>/hub/server/logs

On Windows. <infamdm_install_directory>\hub\server\logs
Usage Get information about the Hub Server operations.
Contents Summary of the Hub Server operations.
74 Chapter 7: Hub Server Post-Installation Tasks

WebLogic Server Log Files
The WebLogic Server log file contains information about WebLogic processes.
The following table describes the properties of the WebLogic Server log files:
File Name access.log

<weblogic_server>.log
<weblogic_domain>.log
Location On UNIX. <Weblogic_domain>/servers/<Weblogic_server>/logs

On Windows. <Weblogic_domain>\servers\<Weblogic_server>\logs
Usage Get information about server processes such as messages and transactions.
Contents Contains message processing status, JMS connection status, transaction details, java exceptions,
and file access details.
Verify the Version and Build Number

You must ensure that the correct version and build number of the Hub Server is installed.
Perform one of the following steps to verify the Hub Server version and build number:
• Verify the version and build number in the manifest.mf JAR entry in the siperian-mrm.ear file. The
siperian-mrm.ear file is in the following directory:
On UNIX. <infamdm_install_directory>/hub/server
On Windows. <infamdm_install_directory>\hub\server
• Verify the version and build number in the versionInfo.xml file that is in the following directory:
On UNIX. <infamdm_install_directory>/hub/server/conf
On Windows. <infamdm_install_directory>\hub\server\conf
• On UNIX. Run versionInfo.sh that is in the following directory:
<infamdm_install_directory>/hub/server/bin
On Windows. Run versionInfo.bat that is in the following directory:
<infamdm_install_directory>\hub\server\bin
Note: For AIX systems, change the versionInfo.sh script to run Java from the <JAVA_HOME>/jre/bin
directory.
Verify the Version and Build Number 75

Configure the Hub Server
After you install the Hub Server, you need to configure it. You can configure logging settings, and change
application server and Hub Server settings.
Configuring the Logging Settings

You can configure the Hub Server for logging. Specify the configuration settings for logging in the log4j.xml
file.
1. Open log4j.xml in the following directory:

2. Set the value for the following category names:
• com.siperian
• com.delos
• com.informatica
Set the value of category names to DEBUG for the most detailed logging, INFO for less detailed logging,
and ERROR for the least detailed logging. The default is INFO.
3. Set the value for the Threshold parameters to DEBUG.
4. Save and close the log4j.xml file.
Setting the Configuration Properties

You can configure the Hub Server properties in the cmxserver.properties file.
1. Open cmxserver.properties in the following directory:

On UNIX. <infamdm_install_directory>/hub/server/resources
On Windows. <infamdm_install_directory>\hub\server\resources
2. Set the Hub Server properties.
The following text shows a sample configuration of the cmxserver.properties file:
cmx.home=C:\infamdm\hub\server
cmx.server.masterdatabase.type=oracle
cmx.appserver.type=weblogic
cmx.appserver.rmi.port=7001
cmx.appserver.naming.protocol=t3
cmx.appserver.soap.connector.port=
jnlp.initial-heap-size=128m
jnlp.max-heap-size=512m
cmx.server.datalayer.cleanse.execution=SERVER
cmx.server.datalayer.cleanse.working_files.location=C:\infamdm\hub\server\logs
cmx.server.datalayer.cleanse.working_files=LOCAL
3. Restart the Hub Server application to reload the settings in the cmxserver.properties file.
Deploying the Hub Server EAR File

You must deploy the Hub Server EAR file on the same machine on which you install the Hub Server.
The Hub Server application must be able to find the Hub Server installation from which you deploy it.
Therefore, do not transfer the EAR file for deployment on another machine. For example, if you install the

Hub Server on a test machine and then deploy the EAR file on the production machine, the application on
production machine cannot find the installation for configuration information such as logging.
Changing the WebLogic Server Settings

If you want to change any of the WebLogic Server settings that you specify during the installation process,
change them after the installation.
1. Open build.properties in the following directory:

On UNIX. <infamdm_install_directory>/hub/server/bin
On Windows. <infamdm_install_directory>\hub\server\bin
2. Change the WebLogic Server configuration settings.
3. Save and close the build.properties file.
4. Run the postInstallSetup script.
5. Restart the WebLogic Server application server.
Configure the Hub Server on Environments with

Managed Servers
After you install the Hub Server on environments with Managed Servers, configure the Hub Server.
For example, if the WebLogic environment has two Managed Servers that run on host1 and host2, and use
RMI ports 8001 and 8002, configure the host name and port numbers in the cmxserver.properties file of
the Manages Servers. Repackage the Hub Server EAR file and deploy it on the WebLogic application server.
Configuring the Hub Server Properties

After you install the Hub Server in a WebLogic cluster, configure the Hub Server properties on the
Administration Server and on each Managed Server.
You can configure the Hub Server properties in the cmxserver.properties file.
1. Stop the WebLogic application server on the Administration Server and all the Managed Servers of the
cluster.
2. Open the cmxserver.properties file on the Administration Server and on all the Managed Servers in
the cluster.
The cmxserver.properties file is in the following directory:
On UNIX. <infamdm install directory>/hub/server/resources
On Windows. <infamdm install directory>\hub\server\resources
3. Change the following properties in the cmxserver.properties file:
Configure the Hub Server on Environments with Managed Servers 77

cmx.appserver.hostname Specify machine names of all the Managed Servers separated by a comma. For
example, if the WebLogic cluster environment has two Managed Servers that
run on host1 and host2, set the property to
cmx.appserver.hostname=host1,host2.
cmx.appserver.rmi.port Specify RMI port numbers that the Managed Servers use separated by a
comma. For example, if the Managed Servers in the WebLogic cluster
environment use RMI ports 8001 and 8002, set the property to
cmx.appserver.rmi.port=8001,8002.
jnlp.initial-heap-size Specify the initial heap size in megabytes for Java Web Start for JVM. Default is
128m.
jnlp.max-heap-size Specify the maximum heap size in megabytes for Java Web Start for JVM.
Default is 512m.
In the properties description, the host name and port number of the first server are host1 and 8001, the
host name and port number of the second server are host2 and 8002.
4. Start the WebLogic application server on the Administration Server and on all the Managed Servers of
the cluster.
Repackaging the Hub Server EAR File

After you configure the Hub Server properties, repackage the siperian-mrm.ear file on the Administration
Server.
1. To create a directory named EAR, run the following command:

On UNIX.
cd <infamdm install directory>/hub/server/lib
mkdir ear
On Windows.
cd <infamdm install directory>\hub\server\lib
mkdir ear
2. To repackage the siperian-mrm.ear file, run the following command:
On UNIX.
cd <infamdm install directory>/hub/server/bin
sip_ant.sh repackage
On Windows.
cd <infamdm install directory>\hub\server\bin
sip_ant.bat repackage
Deploying the Hub Server Applications

After you install and configure the Hub Server, deploy the Hub Server applications on the Administration
Server of the WebLogic cluster.
Perform the following tasks to deploy the Hub Server applications:
1. Run the PostInstallSetup script.

2. Specify the targets for deployments.
3. Restart WebLogic Server.
Step 1. Run the PostInstallSetup Script

To deploy the Hub Server application, run the PostInstallSetup script on the WebLogic Administration
Server.
Ensure that you deploy the Hub Server application from the Hub Server installation directory.
1. Start the WebLogic Administration Server and the Managed Servers on all the machines that are part of
the WebLogic cluster.
2. If the Administation Server and the Managed Servers are on different machines, copy the following
deployment files to the installation directory of the Administration Server:
Deployment File Name Description
siperian-mrm.ear Required. The Hub Server application.
provisioning-ear.ear Required. The Provisioning tool application.
entity360view-ear.ear Optional. The Entity 360 framework.
informatica-mdm-platform-ear.ear Optional. The Informatica platform application.
The deployment files are in the following directory:

On UNIX. <infamdm install directory>/hub/server
On Windows. <infamdm install directory>\hub\server
3. Open a command prompt, and navigate to the PostInstallSetup script in the following directory:
On UNIX. <infamdm installation directory>/hub/server
On Windows. <infamdm installation directory>\hub\server
Note: If you do not have embedded ActiveVOS in your environment, do not include the ActiveVOS user
names and passwords in the command.
On UNIX. ./postInstallSetup.sh -Dweblogic.password=<WebLogic password> -
Ddatabase.password=<MDM Hub Master database password> -Davos.username=<ActiveVOS Console
username> -Davos.password=<ActiveVOS Console password> -Davos.password=<ActiveVOS
Console password> -Davos.jdbc.database.username=<ActiveVOS database username>-
Davos.jdbc.database.password=<ActiveVOS database password>
Note: If you include the exclamation mark (!) in your password, you must include a backslash before the
exclamation mark. For example, if your password is !!cmx!!, enter the password as follows: \!\!cmx\!\!
On Windows. postInstallSetup.bat -Dweblogic.password=<WebLogic password> -
Console password> -Davos.jdbc.database.username=<ActiveVOS database username> -
The ActiveVOS Console credentials are the same credentials as the administrative user in the
application server.
Configure the Hub Server on Environments with Managed Servers 79

The ActiveVOS database credentials are the same credentials that were used to run the create_bpm
script.
5. Stop and restart the WebLogic Administration Server and the Managed Servers on all the machines that
are part of the WebLogic cluster.
For more information, see the WebLogic documentation.
Step 2. Specify the Targets for Deployments

After you run the PostInstallSetup script, specify the Managed Servers to which you want to deploy the
Hub Server applications.

2. Specify all the Managed Servers as targets for the following Hub Server deployments:
ave_weblogic.ear Optional. The ActiveVOS server application.
activevos-central.war Optional. The ActiveVOS Central application.
3. Specify all the Managed Servers as targets for the JMS Server SiperianJMSServer.
4. Specify all the Managed Servers as targets for the following data sources:
• MDM Hub Master Database data source
• Operational Reference Store datasource
5. Specify all the Managed Servers as targets for the startup and shutdown classes.
Step 3. Restart WebLogic Server

After you specify the target Managed Servers for the Hub Server deployment files, restart the WebLogic
Administration Server and all the Managed Servers.

On UNIX.
the admin server>
On Windows.
the admin server>

Running the Post Install Script Manually
If you skipped the post install script during installation, you can run the post install script manually.
On UNIX. <infamdm installation directory>/hub/server
On Windows. <infamdm installation directory>\hub\server
Note: If you do not have embedded ActiveVOS in your environment, do not include the ActiveVOS user
names and passwords in the command.
On UNIX. ./postInstallSetup.sh -Dweblogic.password=<WebLogic password> -
Console password> -Davos.jdbc.database.username=<ActiveVOS database username>-
Note: If you include the exclamation mark (!) in your password, you must include a backslash before the
exclamation mark. For example, if your password is !!cmx!!, enter the password as follows: \!\!cmx\!\!
On Windows. postInstallSetup.bat -Dweblogic.password=<WebLogic password> -
Console password> -Davos.jdbc.database.username=<ActiveVOS database username> -
The ActiveVOS Console credentials are the same credentials as the administrative user in the
application server.
The ActiveVOS database credentials are the same credentials that were used to run the create_bpm
script.
Manually Redeploying the Hub Server Application

You can use the postInstallSetup script to deploy or redeploy the Hub Server application to WebLogic Server.
However, you can also use the default application server tool to deploy the Hub Server application.
Ensure that you deploy the Hub Server application from the Hub Server installation directory.
1. Use the WebLogic Server Administration Console to undeploy the following deployment files:
2. Use the WebLogic Server Administration Console to deploy all the deployment files.
Running the Post Install Script Manually 81

For more information, see the WebLogic Server documentation.
Manually Creating Data Sources

If you want to configure multiple Process Servers, manually configure data sources. Also, manually configure
data sources if you need to troubleshoot issues. For example, create data sources manually if the automated
queue creation process fails.
1. Configure WebLogic to use a data source.

a. Contact the database provider to get the JDBC driver for the database configuration.
b. Copy the JDBC driver to the following directory:
On UNIX. <WebLogic install directory>/wlserver/server/lib
On Windows. <WebLogic install directory>\wlserver\server\lib
c. Add the path to the JDBC driver to the WEBLOGIC_CLASSPATH variable in the following file:
On UNIX. <WebLogic install directory>/wlserver/common/bin/commEnv.sh
On Windows. <WebLogic install directory>\wlserver\common\bin\commEnv.cmd
Note: Place the path to the JDBC driver before the path to other WebLogic Server libraries.
3. Click Services > Data Sources.
The Summary of Data Sources page appears.
4. Click New and select Generic Data Source.
5. Provide the following JDBC data source properties, and click Next:
Name
Name for the JDBC data source.
On Oracle. <Oracle host name>-<SID>-<operational reference store name>
JNDI Name
JNDI path to which the JDBC data source is bound.
On Oracle. jdbc/siperian-<Oracle host name>-<SID>-<operational reference store name>-ds
Database Type
Database that you want to connect to.
The Database Driver page appears.
6. Select the database driver that you want to use to connect to the database, and click Next.
Oracle driver (Thin XA)
7. Click Next.

Database Name
Name of the database that you want to connect to.
Host Name
Port
Database User Name

Password
Confirm Password
9. Click Next.
10. Review the connection properties, and enter a table name such as C_REPOS_DB_RELEASE in the
Test Table Name field.
11. Click Test Configuration.
12. Click Next.
13. Select AdminServer as the server on which you want to deploy the data source.
14. Click Finish.
15. In the Change Center of the Administration Console, click Activate Changes.
16. Restart WebLogic to ensure that all changes are activated.
Manually Configuring JMS Message Queues

If you need to troubleshoot issues, you can manually configure JMS message queues. For example, you
might need to manually create message queues if the automated queue creation process fails or if the
queues are accidentally dropped after installation.
The Services Integration Framework (SIF) uses a message-driven bean on the JMS message queue to
process incoming asynchronous SIF requests. Configure the message queue and the connection factory for
the application server that you use for the MDM Hub implementation. When you configure a JMS message
queue, you also create a connection factory.
To manually configure the JMS message queue, perform the following tasks:
1. Create a JMS server and module.

2. Create a connection factory for the module.
3. Add JMS message queues to the module.
Manually Configuring JMS Message Queues 83

4. Create a subdeployment queue.
5. Add a message queue server.
6. Add a message queue.
Note: When you create JMS message queues for the MDM Hub in a clustered environment, ensure that you
select a target server that you can migrate. When you configure the JMS module, make the target “All
servers in the cluster.” For more information see the WebLogic documentation.
Step 1. Create a JMS Server and Module

Use the Weblogic Administration Console to create a JMS message queue. Create a JMS server and a
module for the message queue.
1. Start the WebLogic Console, and click Lock&Edit.

2. Navigate to Services > Messaging > JMS Servers.
3. Create a JMS Server with the name SiperianJMSServer, and click Next.
4. Select the server name in the Target list, and click Finish.
5. Navigate to Services > Messaging > JMS Modules.
6. Create a JMS Module with the name SiperianModule, and click Next.
7. Select the Target Server check box.
8. Click Next, and then click Finish.
Step 2. Configure a Connection Factory for the Module

Create and configure a connection factory for the module that you created.
1. Navigate to the SiperianModule that you created in “Step 1. Create a JMS Server and Module” on page
84.
2. Click New under Summary of Resources.
3. Choose Connection Factory, and click Next.
4. Specify siperian.mrm.jms.xaconnectionfactory for both the name and the JNDI name, and click
Next.
5. Select Target Server, and click Finish.
The siperian.mrm.jms.xaconnectionfactory connection factory is created.
6. Under Configuration, go to the siperian.mrm.jms.xaconnectionfactory connection factory that you
created.
7. Click Transactions.
8. Select the XA Connection Factory Enabled check box.
9. Click Save.
Step 3. Add Message Queues to the Module

You can add JMS message queues to the module that you created.
1. Navigate to SiperianModule, and click New under Summary of Resources.

2. Choose Queue, and click Next.

3. Specify siperian.sif.jms.queue for both the name and the JNDI name, and click Next.
4. Choose the JMS Server that you created in “Step 1. Create a JMS Server and Module” on page 84, and
click Finish.
Step 4. Create a Subdeployment Queue

After you add JMS message queues to the module that you created, create a subdeployment queue.
1. Under Summary of Resources, go to SiperianModule, and click New.

2. Choose Queue, and click Next.
3. Click the Create a new Subdeployment button.
4. Verify that the Subdeployment Name is siperian.sif.jms.queue, and click OK.
5. Specify siperian.sif.jms.queue for both the name and the JNDI name, and click Next.
6. Choose the JMS Server that you created, and click Finish.
Step 5. Add a Message Queue Server

You must add a message queue server to the MDM Hub implementation before you add a message queue.
1. Start the Hub Console.

2. Click Message Queues under the Configuration workbench.
3. Click Write Lock > Acquire Lock.
4. Right-click on the middle pane of the Message Queues tool, and then click Add Message Queue
Server.
The Add Message Queue Server dialog box appears.
5. Enter values for the following fields:
Connection Factory Name
Name of the connection factory. Specify siperian.mrm.jms.xaconnectionfactory.
Display Name
Name of the message queue server that must appear in the Hub Console. Specify
Siperian.Mrm.Jms.Xaconnectionfactory.
6. Click OK.
The message queue server is added.
Step 6. Add a Message Queue

You can add a message queue to a message queue server.

2. Click Message Queues under the Configuration workbench.
4. Right-click the message queue server in the middle pane of the Message Queues tool, and then click
Add Message Queue.
Manually Configuring JMS Message Queues 85

The Add Message Queue dialog box appears.
5. Enter values for the following fields:
Queue Name
Name of the message queue. Specify siperian.sif.jms.queue.
Display Name
Name of the message queue that must appear in the Hub Console. Specify
Siperian.Sif.Jms.Queue.
6. Click OK.
The message queue is added to the message queue server.
7. In the right pane, select the Use with message triggers option.
8. Click Test.
The result of the message queue test appears.
Improve API Performance on JBoss AS 7.2

You can improve the API performance on JBoss AS 7.2, which is a part of JBoss Enterprise Application
Platform 6.1, by increasing the maximum values for the data source connection pool, the default thread pool,
and the default HTTP connection pool.
1. Navigate to the following directory:

<JBoss Installation Directory>/standalone/configuration
2. Open the standalone-full.xml file in an XML editor.
3. For the JDBC data source connection pool, find the xa-pool element, and set max-pool-size to 300.
<xa-pool>
<min-pool-size>5</min-pool-size>
<max-pool-size>300</max-pool-size>
.....
</xa-pool>
4. For the default thread pool, find the thread-pools element, and set max-threads to 300.
<thread-pools>
<thread-pool name="default">
<max-threads count="300"/>
<keepalive-time time="100" unit="milliseconds"/>
</thread-pool>
</thread-pools>
5. For the HTTP connection pool, find the connector name="HTTP" element, and add the attribute max-
connections="300" .
<connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" max-
connections="300"/>
6. Save the file.

Configure WebLogic for Secure ActiveVOS
Communication
To use the HTTP Secure (HTTPS) protocol for communication between ActiveVOS and the MDM Hub, you
must configure the application server.
1. In the WebLogic console, enable the SSL listen port for the application server.
<infamdm installation directory>\hub\server
For UNIX:
postinstallSetup.sh -Ddatabase.password=<MDM Hub Master Database password> -
Dweblogic.password=<WebLogic password>
For Windows:
postinstallSetup.bat -Ddatabase.password=<MDM Hub Master Database password> -
Changing the Operational Reference Store User

Password
After you install the Hub Server, you can change the password for the Operational Reference Store. If you
change the password for the Operational Reference Store, perform the following tasks:
1. Change the password for the Operational Reference Store user.

2. Set the same password in the data source on the application server.
3. Register the schema with the same user name and password.
Repackaging Custom JAR Files

If you have custom JAR files, repackage the JAR files in the siperian-mrm.ear file after you install the Hub
Server.
1. Run the following command to create a directory named EAR:

On UNIX.
cd <infamdm_install_directory>/hub/server/lib
mkdir ear
On Windows.
cd <infamdm_install_directory>\hub\server\lib
mkdir ear
Configure WebLogic for Secure ActiveVOS Communication 87

2. Run the following command to copy each custom JAR file to the EAR directory that you create in the
preceding step:
On UNIX.
copy <original_location_of_custom_jar_file>/<custom_JAR_filename>.jar ear
On Windows.
copy <original_location_of_custom_jar_file>\<custom_JAR_filename>.jar ear
3. Run the following command to repackage the EAR file:
On UNIX.
cd <infamdm_install_directory>/hub/server/bin
On Windows.
cd <infamdm_install_directory>\hub\server\bin
Restart WebLogic
The installation process enables the AnonymousAdminLookupEnabled method of the WebLogic Server. The
AnonymousAdminLookupEnabled method must be enabled for the registration of the Operational Reference
Store. If you do not restart WebLogic Server after you install the Hub Server, the Operational Reference
Store fails.
Configure JBoss Cache

You can configure JBoss Cache to handle caching requirements. Modify the JBoss cache properties for
tuning performance.
Change the jbossCacheConfig.xml file in the following location to configure JBoss Cache:
On UNIX. <infamdm_install_dir>/hub/server/resources/jbossCacheConfig.xml
On Windows. <infamdm_install_dir>\hub\server\resources\jbossCacheConfig.xml
Change the following properties in the jbossCacheConfig.xml file:
lockAcquisitionTimeout
Increase the value of the property to 60000 or higher, to ensure that the Hub Server acquires a cache
object lock.
sync replTimeout
Increase the value of the property to 30000 or higher, to ensure that the Hub Server acquires a cache
object lock.
stateRetrieval timeout
Increase the value of the property to 60000, to ensure initial state retrieval.
clustering
Set up the clustering property for a clustered environment.

Set the clusterName attribute to use the same cluster name for all the members of a single cluster.
Ensure that you remove the clustering property for a single node environment.
jgroupsConfig
Set UDP configurations for the property to ensure that there is no conflict between different cluster
members.
Set the mcast_addr=<multicast_address> attribute to use the same value for all the members of a
single cluster. Use different values for different clusters, or non-clustered MDM Hub Servers on the same
network.
Set the mcast_port=<multicast_port> attribute to use the same value for all the members of a single
cluster. Use different values for different clusters, or non-clustered MDM Hub servers on the same
network.
eviction
Change the eviction time for ReposObjects and DataObjects if there is enough memory and these
objects need to remain in memory for a longer duration.
Change the eviction time as shown in the following sample:

<region name="/ReposObjects">
<property name="timeToLive" value="86400000" /> <!—24 hours is the minimum
required-->
</region>
<region name="/DataObjects">
<property name="timeToLive" value="86400000" /> <!—24 hours is the minimum
required-->
</region>
Configure Logging for Informatica Platform

If you Installed Informatica platform, configure the MDM Hub to log Informatica platform processes.
1. Open the log4j.xml file from the following directory:

2. Add the following lines to the log4j.xml file.
<category name="com.informatica.mdm.platform">
<priority value="ALL"/>
</category>
<appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
<param name="Threshold" value="ALL"/>
</appender>
3. Save and close the log4j.xml file.
Configure Logging for Informatica Platform 89

Starting the Hub Console
Start the Hub Console to access the MDM Hub. Use an HTTP connection to start the Hub Console.
Ensure that you have a user name and password set up before you start the Hub Console.
1. Open a browser window and enter one of the following URLs:

http://<MDM Hub host>:<port>/cmx/
where <MDM Hub host> is the local MDM Hub host and port is the port number. Check with your
administrator for the correct port number.
The Hub Console launch window appears.
2. Click Launch.
Java Web Start loads.
Note: The first time you launch the Hub Console from a client machine, Java Web Start downloads
application files.
The MDM Hub Login dialog box appears.
3. Enter a user name and password.
4. Click OK.
The Change database dialog box appears.
5. Select the target database.
The target database is the MDM Hub Master Database.
6. Select a language from the list, and click Connect.
The Hub Console user interface appears in the language that you select. If you need to change the
language in which the Hub Console user interface appears, restart the Hub Console with the language of
your choice.
Registering an Operational Reference Store

After you create an Operational Reference Store, you must register it. Register an Operational Reference
Store with a single MDM Hub Master Database. You can register an Operational Reference Store through the
Hub Console.
Note: When you register an Operational Reference Store in a clustered environment, manually create the
data sources and connection pools for the Operational Reference Stores.

2. Select the MDM Hub Master database, and click Connect.
3. Start the Databases tool under the Configuration workbench.
5. Click the Register database button.
The Informatica MDM Hub Connection Wizard appears and prompts you to select the database type.
6. Select the Oracle database type, and click Next.

7. Configure connection properties for the database.
a. Select an Oracle connection method, and click Next.
The following table describes the Oracle connection methods that you can select:
Connection Method Description
Service Connect to Oracle by using the service name.
SID Connect to Oracle by using the Oracle System ID.
For more information about SERVICE and SID names, see the Oracle documentation.
b. Specify the connection properties for the connection type that you select, and click Next.
The following table lists and describes the connection properties:
Database Name for the Operational Reference Store that must appear in the Hub Console.
Display Name
Machine Prefix given to keys to uniquely identify records from the Hub Store instance.
Identifier
Database IP address or name of the server that hosts the Oracle database.
hostname
SID Oracle System Identifier that refers to the instance of the Oracle database running
on the server. The SID field appears if you selected the SID connection type.
Service Name of the Oracle SERVICE used to connect to the Oracle database. The Service
field appears if the you selected the Service connection type.
Port The TCP port of the Oracle listener running on the Oracle database server. The
default is 1521.
Oracle Name by which the database is known on your network as defined in the
TNS Name TNSNAMES.ORA file of the application server.
For example: mydatabase.mycompany.com.
You set the Oracle TNS name when you install the Oracle database. For more
information about the Oracle TNS name, see the Oracle documentation.
Schema Name Name of the Operational Reference Store.
Password Password associated with the user name for the Operational Reference Store.
For Oracle, the password is not case sensitive.
By default, this is the password that you specify when you create the Operational
Reference Store.
Registering an Operational Reference Store 91

Dynamic Data Not required. Do not populate this field, because the value that you provide is not
Masking host used.
DDM Optional. URL to connect to the Dynamic Data Masking application. The URL is
connection similar to the URL that you use to connect to the database, except that the Dynamic
URL Data Masking application URL uses the Dynamic Data Masking host name and port
number.
Note: The Schema Name and the User Name are both the names of the Operational Reference
Store that you specified when you created the Operational Reference Store. If you need this
information, consult your database administrator.
The Summary page appears.
c. Review the summary, and specify additional connection properties.
The following table lists additional connection properties that you can configure:
Connection URL Connect URL. The Connection Wizard generates the connect URL by
default. The following list shows the format of the connect URL for the
Oracle connection types:
Service connection type
jdbc:oracle:thin:@//database_host:port/
service_name
SID connection type

jdbc:oracle:thin:@//database_host:port:sid
For a service connection type only, you have the option to customize
and later test a different connection URL.
Create data source after Select to create the data source on the application server after
registration registration.
Note: If you do not select the option, you must manually configure the
data source.
d. For a service connection type, if you want to change the default URL, click the Edit button, specify
the URL, and then click OK.
8. Click Finish.
The Registering Database dialog box appears.
9. Click OK.
The MDM Hub registers the Operational Reference Store.
10. Select the Operational Reference Store that you registered, and click the Test database connection
button to test the database settings.
The Test Database dialog box displays the result of the database connection test.
11. Click OK.
The Operational Reference Store is registered, and the connection to the database is tested.

CHAPTER 8
Process Server Installation

• Installing the Process Server in Graphical Mode, 93

• Installing the Process Server in Console Mode, 95
• Installing the Process Server in Silent Mode, 97
• Installing the Process Server on Environments with Managed Servers, 101
Installing the Process Server in Graphical Mode

You can install the Process Server in graphical mode.
On UNIX, use the same user name that you used to install the Hub Server for the Process Server. If you
install the Hub Server and the Process Server on the same machine, the users who install them must belong
to the same UNIX group.
On UNIX, if you install the Process Server and the Hub Server on the same machine, use the operating
system user account that you use for the Hub Server to install the Process Server. Use the root user to install
the Process Server only when the root user account is already used for the Hub Server.

2. Open a command prompt, and navigate to the following directory:
By default the installer is in the following directory:
On UNIX. <distribution directory>/<operating system name>/mrmcleanse
On Windows. <distribution directory>\windows\mrmcleanse
On UNIX. hub_cleanse_install.bin
On Windows. hub_cleanse_install.exe
5. Click Next.
The Choose Install Folder window appears.
7. Select the location of the Process Server installation.
93
Important: Process Server fails to load if the total length of the path exceeds 256 characters or includes
spaces in the directory or folder names.
On UNIX, the Choose Link Folder window appears.
On Windows, the Choose Shortcut Folder window appears.
8. Select a location for the product icons, and click Next.
The Enter Location of License File window appears.
a. Choose a path to the WebLogic domain installation directory for the domain you want to use for the
MDM Hub. Click Next.
b. Enter values for the login parameters.
The following table describes the login parameters:
Parameter Description
Host Name of the host computer on which WebLogic is installed.
For example, AdminServer.
Port Number Port number on which the WebLogic Server is listening.
12. Configure cleanse engine settings for the cleanse engine you use.
• If you use Address Doctor, specify the Configuration file and Parameters file locations and the
Correction Type parameter.
• If you use Business Objects DQ XI, specify the Host, Port, and Sub File parameters for the Business
Objects DQ XI cleanse engine.
13. Click Next.
15. If you have a proxy server, select Yes, and enter the proxy server details. Otherwise, select No.
94 Chapter 8: Process Server Installation

16. Click Next.
17. Select one of the following post installation setup script options:
• Yes, run the script during this installation. Runs the post installation script during the installation.
• No, I will run it later. Allows you to manually run the post installation script later.
18. Click Next.
19. After the summary window displays the options you want, click Install to start the installation process.
20. Select Yes, restart my system to restart the system, or select No, I will restart the system myself to
restart it later.
21. Click Done to exit the Process Server installer.
After installation, you must perform additional configuration for the cleanse engine according to the
instructions in the Informatica MDM Multidomain Edition Cleanse Adapter Guide.
Installing the Process Server in Console Mode

You can install the Process Server in console mode on UNIX.
Note: Do not use the root user when you install the Process Server on RedHat Linux. The root user does not
have a .profile, which InstallAnywhere requires. Instead, create and use a separate user profile to install the
Process Server.

On Solaris. <distribution directory>/solaris/mrmcleanse
On HP-UX. <distribution directory>/hpux/mrmcleanse
On Linux. <distribution directory>/linux/mrmcleanse
On AIX. <distribution directory>/aix/mrmcleanse
./hub_cleanse_install.bin -i console
5. Press Enter.
6. Read the License Agreement. Type Y to accept the license agreement, or type N if you do not want to
accept the license agreement and want to exit the installation program.
7. Press Enter.
Installing the Process Server in Console Mode 95

8. Choose the folder for the Process Server installation.
• To choose the default location, press Enter.
9. Confirm the location of the installation folder. Type Y to confirm the installation folder, or type N to
10. Press Enter.
The prompt for the license file location appears.
11. Enter the absolute path of the license file, and press Enter.
A list of application server options appears.
12. Type the number for the application server that you want to select, and press Enter.
The application server information appears.
a. Specify the path to the WebLogic domain in which you want to install the Hub Server, and press
Enter.
14. Press Enter.
15. Configure the cleanse engine settings.
• If you use Address Doctor, configure the following parameters:
- Specify the configuration file location, and press Enter.
- Specify the parameters file location, and press Enter.
- Specify the default correction type, and press Enter.

• If you use Business Objects DQ XI, configure the following parameters:
- Specify the host name, and press Enter.
- Specify the port, and press Enter.
- Specify the sub file, and press Enter.
16. From the Product Usage Toolkit options, select the environment type. Type 1 for Production, type 2 for
Test/QA, or type 3 for Development, and then press Enter.
17. Select whether you have a proxy server. Press Enter for Yes. Otherwise, type 2 for No and then press
Enter.
manually later.
19. Press Enter.

the installation. If you need to make changes, type BACK to the specific information and make changes.
The Hub Server is installed according to the configuration information you provide. When the process is
complete, the installation complete information appears.
21. Press Enter.
The Process Server is installed according to the information you specify, and the install complete
information appears.
Installing the Process Server in Silent Mode

You can install the Process Server without user interaction in silent mode. You might want to perform a silent
Before you run the silent installation for the Process Server, you must configure the properties file for the
silent installation. The installer reads the file to determine the installation options. The silent installation
process might complete successfully even if you provide incorrect settings, such as an incorrect application
server path or port setting. You must ensure that you provide correct settings in the properties file.
Copy the Process Server installation files to the hard disk on the machine where you plan to install the
Process Server. To install in silent mode, complete the following tasks:

1. Locate the sample silentInstallCleanse_sample.properties file in the distribution directory.

The file is in the distribution directory in the following directory:
On UNIX. /silent_install/mrmcleanse
On Windows. \silent_install\mrmcleanse
each when you enter information in the file, such as when you enter an installation path. For example, to
enter the path to the Process Server directory, you must enter \\u1\\infamdm\\hub\\cleanse.
2. Create a backup copy of silentInstallCleanse_sample.properties.
4. Save the properties file with a name such as silentInstallCleanse.properties.
Installing the Process Server in Silent Mode 97

The following table describes the installation parameters that you can modify:
INSTALLER_UI Specifies the type of installation. Set to silent.
USER_INSTALL_DIR Directory to install Process Server.

For example, C\:\
\<infamdm_install_directory>\\hub\
\cleanse.
SIP.LICENSE.PATH Path to the Informatica license file.
SIP.LICENSE.FILENAME License file name. Set to siperian.license.
SIP.OS.CHOICE=Red Hat Linux Remove the comment on the property if the operating
system for the installation is Red Hat Linux.
To remove the comment, remove the pound sign (#) in
front of the property.
SIP.OS.CHOICE=Suse Linux Remove the comment on the property if the operating

system for the installation is Suse Linux.
To remove the comment, remove the pound sign (#) in
front of the property.
SIP.ADDRESSDOCTOR.SETCONFIGFILE Location of the Address Doctor configuration file if

your cleanse engine is Address Doctor.
SIP.ADDRESSDOCTOR.PARAMETERSFILE Location of the Address Doctor parameter file.
SIP.ADDRESSDOCTOR.DEFAULTCORRECTIONTYPE Address Doctor Cleanse Engine correction type.

Specify PARAMETERS_DEFAULT.
RUN_DEPLOYMENT_FLAG Runs the postInstallSetup script as part of the silent

installation. Set to 1 if you want to run
postInstallSetup. Set to 0 if you do not want to run
postInstallSetup at the end of the silent installation.
USER_REQUESTED_RESTART Set the property only for the Windows operating

system. Specifies whether the operating system needs
a restart or not. Default is No.
SIP.FLDIRECT.HOST Host name of FirstLogic.

SIP.FLDIRECT.PORT FirstLogic direct port.
SIP.FLDIRECT.SUBFILE FirstLogic Direct subfile
CSM_TYPE The type of product usage toolkit installation. Can be

Production, Test, or Development. Default is
Production.
CSM_HOST Name of the proxy server host. Leave blank if the

environment does not have a proxy server.
CSM_PORT Proxy server port. Leave blank if the environment does

not have a proxy server.
CSM_DOMAIN Name of the proxy server domain. Leave blank if the

environment does not have a proxy server or if the
domain name is not required.
CSM_PROXY_USER_NAME Proxy server user name. Leave blank if the

proxy server user name is not required.
CSM_PROXY_PASSWORD Proxy server password. Leave blank if the

proxy server password is not required.

The following example shows the contents of the sample silentInstallCleanse_sample.properties file:
## command to run silent install...
## For Windows: hub_cleanse_install.exe -f <property_file>
## For Unix: hub_cleanse_install.bin -f <property_file>
INSTALLER_UI=silent
## Hub Server Install directory.

USER_INSTALL_DIR=C\:\\siperian\\hub\\cleanse
## License path and filename

SIP.LICENSE.PATH=C\:\\
SIP.LICENSE.FILENAME=siperian.license
## Properties for WebLogic application server

SIP.AS.HOME=C\:\\bea\\user_projects\\domains\\base_domain
## Following AddressDoctor properties should be set if you have license for
AddressDoctor.
SIP.ADDRESSDOCTOR.SETCONFIGFILE=C\:\\siperian\\hub\\cleanse\\resources\\AddressDoctor\
\5\\SetConfig.xml
SIP.ADDRESSDOCTOR.PARAMETERSFILE=C\:\\siperian\\hub\\cleanse\\resources\\AddressDoctor\
\5\\Parameters.xml
SIP.ADDRESSDOCTOR.DEFAULTCORRECTIONTYPE=PARAMETERS_DEFAULT
Installing the Process Server in Silent Mode 99

## Following FirstLogicDirect properties should be set if you have lincense for
FirstLogicDirect.
SIP.FLDIRECT.HOST=localhost
SIP.FLDIRECT.PORT=20004
SIP.FLDIRECT.SUBFILE=dqxiserver1_substitutions.xml
## If you want to run postInstallSetup as a part of silent install, then set following
property.
## set RUN_DEPLOYMENT_FLAG to 1 if you want to run postInstallSetup
## or set RUN_DEPLOYMENT_FLAG to 0 if you do not want to run postInstallSetup
## If you want to restart the operating system as a part of silent install, set
following properties to 'YES'.
RESTART_NEEDED=NO
USER_REQUESTED_RESTART=NO
#Product Usage Toolkit Installation

#CSM_TYPE is the type of Product Usage Toolkit installation.
# valid values are:Production,Test,Development. Should not be blank.
CSM_TYPE=Production
# If the network has a proxy server, fill in the following parameters (leave empty if
no proxy):
# proxy server host
CSM_HOST=
# proxy server port
CSM_PORT=
# Proxy server domain name (leave blank, if not applicable)
CSM_DOMAIN=
# Proxy server user name (leave blank, if not applicable)
CSM_PROXY_USER_NAME=
#Proxy server password (leave blank, if not applicable)
CSM_PROXY_PASSWORD=


On UNIX. ./hub_cleanse_install.bin -f
<location_of_silent_properties_file_for_cleanse_match_server>
On Windows. hub_cleanse_install.exe -f
<location_of_silent_properties_file_for_cleanse_match_server>
The silent installer runs in the background. The process can take a while. If you ran the post install script
for the Process Server as part of the silent installation, check the postinstallSetup.log files to verify that
the installation was successful.
On UNIX. <infamdm_install_directory>/hub/cleanse/logs/
On Windows. <infamdm_install_directory>\hub\cleanse\logs\

Installing the Process Server on Environments with
Managed Servers
Install the Process Server on the Administration Server and on all the Managed Servers to which you must
deploy the Process Server application. In a clustered environment, ensure that the path for the Process
Server installation is the same on all the cluster nodes.
1. Start the WebLogic Administration Server and the Managed Servers on all the machines.
2. Open a command prompt, and navigate to the following directory:
By default the installer is in the following directory:
On UNIX. <distribution directory>/<operating system name>/mrmcleanse
On Windows. <distribution directory>\windows\mrmcleanse
3. To start the Process Server installer, run the following command:
On UNIX. ./hub_cleanse_install.bin -DSIPERIAN_INSTALL_PREREQ_VALIDATION=false
On Windows. hub_cleanse_install.exe -DSIPERIAN_INSTALL_PREREQ_VALIDATION=false
5. Click Next.
7. Select the location of the Process Server installation.
Important: Process Server fails to load if the total length of the path exceeds 256 characters or includes
spaces in the directory or folder names.
8. Select a location for the product icons, and click Next.
The Enter Location of License File window appears.
a. Choose a path to the WebLogic domain installation directory for the domain you want to use for the
MDM Hub. Click Next.
b. Enter values for the login parameters.
Installing the Process Server on Environments with Managed Servers 101

The following table describes the login parameters:
Parameter Description
Host Name of the host computer on which WebLogic Administration Server us created.
For example, AdminServer.
Port Number If the cluster is set up with the development cluster IP address, specify the
Administration Server port number for any node in the WebLogic cluster.
If you use the production cluster IP address, specify the cluster port number.
12. Configure cleanse engine settings for the cleanse engine you use.
• If you use Address Doctor, specify the Configuration file and Parameters file locations and the
Correction Type parameter.
• If you use Business Objects DQ XI, specify the Host, Port, and Sub File parameters for the Business
Objects DQ XI cleanse engine.
13. Click Next.
15. If you have a proxy server, select Yes, and enter the proxy server details. Otherwise, select No.
16. In the Deploy page, select the No, I will run it later post installation setup script option.
The No, I will run it later option allows you to manually run the post installation script later.
17. Click Next.
18. After the summary window displays the options you want, click Install to start the installation process.
19. Select Yes, restart my system to restart the system, or select No, I will restart the system myself to
restart it later.
20. Click Done to exit the Process Server installer.

CHAPTER 9
Process Server Post-Installation

Tasks
• Copy the Installation Log Files, 103

• Verify the Version and Build Number, 106
• Configure the Process Server, 106
• Configure the Process Server on Environments with Managed Servers, 108
• Configure Process Server for Multithreading, 111
• Configuring Multiple Process Servers for Cleanse and Match Operations, 112
• Configuring Multiple Process Servers for Batch Processes, 113
• Configure Match Population, 114
Copy the Installation Log Files

The installation log files are useful for troubleshooting the Process Server installation process. Copy the log
files to the installation documentation directory. Informatica Global Customer Support might request copies of
the log files if you contact them regarding installation issues.
Installation Log File

The installation log file contains information about the installed files.
The following table describes the properties of the installation log file:
File Name Informatica_MDM_Cleanse_Match_Server_Install_<timestamp>.xml
Location On UNIX. <infamdm_install_directory>/hub/cleanse/UninstallerData/Logs

On Windows. <infamdm_install_directory>\hub\cleanse\UninstallerData\Logs
103
Usage Get information about the files installed and registry entries created.
Contents Directories created, names of the files installed and commands run, and status for each installed file.
Post-Installation Setup Log File

The post-installation log file contains information about the post-installation process.
The following table describes the properties of the post-installation setup log file:
File Name postInstallSetup.log
Location On UNIX. <infamdm_install_directory>/hub/cleanse/logs

On Windows. <infamdm_install_directory>\hub\cleanse\logs
Usage Get information about the post-installation actions that the installer performs and get information
about the errors in the post-installation process.
Contents Summary of actions performed by the installer during the post-installation process.
Process Server Log File

The Process Server log file contains information about the Process Server operations.
The following table describes the properties of the Process Server log file:
File Name cmxserver.log
Location On UNIX. <infamdm_install_directory>/hub/cleanse/logs

On Windows. <infamdm_install_directory>\hub\cleanse\logs
Usage Get information about the Process Server operations.
Contents Summary of the Process Server operations.
104 Chapter 9: Process Server Post-Installation Tasks

Debug Log File
The installer writes actions and errors to the debug log file.
The following table describes the properties of the debug log file:
File Name infamdm_installer_debug.txt
Location On UNIX. <infamdm_install_directory>/hub/cleanse/

On Windows. <infamdm_install_directory>\hub\cleanse\
Usage Get information about the choices that are made during installation.
Contents Detailed summary of actions performed by the installer.
Installation Prerequisites Log File

The installation prerequisites log file contains information about the prerequisite checks that the installer
performs.
The following table describes the properties of the installation prerequisites log file:
File Name installPrereq.log
Location On UNIX. <infamdm_install_directory>/hub/cleanse/Logs

On Windows. <infamdm_install_directory>\hub\cleanse\Logs
Usage Get information about the prerequisite checks performed by the installer.
Contents Logs of prerequisite validation checks.
WebLogic Server Log Files

The WebLogic Server log file contains information about WebLogic processes.
The following table describes the properties of the WebLogic Server log files:
File Name access.log

<weblogic_server>.log
<weblogic_domain>.log
Location On UNIX. <Weblogic_domain>/servers/<Weblogic_server>/logs

On Windows. <Weblogic_domain>\servers\<Weblogic_server>\logs
Copy the Installation Log Files 105

Usage Get information about server processes such as messages and transactions.
Contents Contains message processing status, JMS connection status, transaction details, java exceptions,
and file access details.
Verify the Version and Build Number

You must ensure that the correct version and build number of the Process Server is installed.
Perform one of the following steps to verify the Process Server version and build number:
• Verify the version and build number in the manifest.mf JAR entry in the siperian-mrm-cleanse.ear file.
The siperian-mrm-cleanse.ear file is in the following directory:
On UNIX. <infamdm_install_directory>/hub/cleanse
On Windows. <infamdm_install_directory>\hub\cleanse
• Verify the version and build number in the versionInfo.xml file that is in the following directory:
On UNIX. <infamdm_install_directory>/hub/cleanse/conf
On Windows. <infamdm_install_directory>\hub\cleanse\conf
• On UNIX. Run versionInfo.sh that is in the following directory:
<infamdm_install_directory>/hub/cleanse/bin
On Windows. Run versionInfo.bat that is in the following directory:
<infamdm_install_directory>\hub\cleanse\bin
Note: For AIX systems, change the versionInfo.sh script to run Java from <JAVA_HOME>/jre/bin/java.
Configure the Process Server

After you install the Process Server, you need to configure it. You can configure logging settings, and change
application server, and Process Server settings.
Deploying the Process Server EAR File

Deploy the Process Server EAR file on the same machine where you install the Process Server.
Deploy the Process Server application on the same machine on which you install the Process Server. For
example, if you install the Process Server on a test machine, then deploy the EAR file on the test machine. If
you deploy the EAR on the production machine, the application on production machine cannot locate the
installation for configuration information such as logging.

Configuring the Process Server with Cleanse Engines
After you install the Process Server you can configure a cleanse engine with the Process Server.
For more information about cleanse engine configuration, see the Informatica MDM Multidomain Edition
Cleanse Adapter Guide.
Configuring the Process Server to Delete Temporary Files

You can configure the Process Server to delete the temporary files that the cleanse process generates.
1. Open the cmxcleanse.properties file.

The cmxcleanse.properties file is located in the following directory:
On UNIX.
<infamdm_install_directory>/hub/cleanse/resources/
On Windows.
<infamdm_install_directory>\hub\cleanse\resources\
2. Set the cmx.server.datalayer.cleanse.working_files property to FALSE.
Default is KEEP.
Configuring the Logging Settings

You can configure the Process Server for logging. Specify the configuration settings for logging in the
log4j.xml file.
1. Open log4j.xml in the following directory:

On UNIX. <infamdm_install_directory>/hub/cleanse/conf
On Windows. <infamdm_install_directory>\hub\cleanse\conf
2. Set the value for the following category names:
• com.siperian
• com.delos
• com.informatica
Set the value of category names to DEBUG for the most detailed logging, INFO for less detailed logging,
and ERROR for the least detailed logging. The default is INFO.
3. Set the value for the Threshold parameters to DEBUG.
4. Save and close the file.
Configuring the Process Server Properties

You can configure the Process Server properties in the cmxcleanse.properties file.
1. Open cmxcleanse.properties in the following directory:

On UNIX. <infamdm_install_directory>/hub/cleanse/resources
On Windows. <infamdm_install_directory>\hub\cleanse\resources
2. Configure the Process Server properties.
Configure the Process Server 107

A sample configuration of the cmxcleanse.properties is as follows:
cmx.server.datalayer.cleanse.working_files.location=C:\infamdm\hub\cleanse\tmp
cmx.server.datalayer.cleanse.working_files=KEEP
cmx.server.datalayer.cleanse.execution=LOCAL
cmx.home=C:\infamdm\hub\cleanse
3. Save and close the cmxcleanse.properties file.
4. Restart the Process Server application to reload the settings in the file.
Running the PostInstallSetup Script Manually

If you skipped the post install script during installation, you can run the post install script manually.
On UNIX. <infamdm installation directory>/hub/cleanse
On Windows. <infamdm installation directory>\hub\cleanse
On UNIX. ./postInstallSetup.sh -Dweblogic.password=<weblogic Password> -
Ddatabase.password=<Database Password>
On Windows. postInstallSetup.bat -Dweblogic.password=<weblogic Password> -
Manually Redeploying the Process Server EAR File

You can manually redeploy the Process Server on the WebLogic application server.
1. Use the WebLogic Server Administration Console to undeploy the siperian-mrm-cleanse.ear file.
2. Use the WebLogic Server Administration Console to deploy the siperian-mrm-cleanse.ear file.
Ensure that you deploy the Process Server EAR file from the Process Server installation directory.
Configure the Process Server on Environments with

Managed Servers
After you install the Process Server on environments with Managed Servers, configure the Process Server.
Configure the Process Server properties in the cmxcleanse.properties file on all the Managed Servers
where you want to deploy the Process Server. Repackage the Process Server EAR file and deploy it on the
WebLogic application server.
Configuring the Process Server Properties

After you install the Process Server on an environment with Managed Servers, configure the Process Server
properties on the Administration Server and all the Managed Servers.
1. Stop the WebLogic application server on the Administration Server and all the Managed Servers of the
cluster.

2. Open cmxcleanse.properties in the following directory:
3. Configure the Process Server properties.
The following sample shows the configuration of the cmxcleanse.properties file:
cmx.server.datalayer.cleanse.working_files.location=C:\infamdm\hub\cleanse\tmp
cmx.server.datalayer.cleanse.working_files=KEEP
cmx.server.datalayer.cleanse.execution=LOCAL
cmx.home=C:\infamdm\hub\cleanse
4. Save and close the cmxcleanse.properties file.
5. Start the WebLogic application server on the Administration Server and on all the Managed Servers of
the cluster.
Repackaging the Process Server EAR File

After you configure the Process Server properties, repackage the siperian-mrm-cleanse.ear file on the
Administration Server.
1. To create a directory named EAR, run the following command:

On UNIX.
cd <infamdm install directory>/hub/cleanse/lib
mkdir ear
On Windows.
cd <infamdm install directory>\hub\cleanse\lib
mkdir ear
2. To repackage the siperian-mrm-cleanse.ear file, run the following command:
On UNIX.
cd <infamdm install directory>/hub/cleanse/bin
On Windows.
cd <infamdm install directory>\hub\cleanse\bin
Deploying the Process Server Application on a WebLogic Cluster

After you install and configure the Process Server, deploy the Process Server application to the
Administration Server.
Perform the following tasks to deploy the Process Server application:
1. Run the PostInstallSetup script.

2. Specify the targets for deployments.
3. Restart WebLogic Server.
Configure the Process Server on Environments with Managed Servers 109

Step 1. Run the PostInstallSetup Script
To deploy the Process Server application, run the PostInstallSetup script on the WebLogic Administration
Server.
Ensure that you deploy the Process Server application from the Process Server installation directory.
2. If the Administation Server and the Managed Servers are on different machines, copy the siperian-
mrm-cleanse.ear file to the installation directory of the Administration Server.
The siperian-mrm-cleanse.ear file is in the following directory:

On UNIX. <infamdm install directory>/hub/server
On Windows. <infamdm install directory>\hub\server
On UNIX. <infamdm installation directory>/hub/cleanse
On Windows. <infamdm installation directory>\hub\cleanse
On UNIX. ./postInstallSetup.sh -Dweblogic.password=<weblogic Password> -
On Windows. postInstallSetup.bat -Dweblogic.password=<weblogic Password> -
5. Stop the WebLogic Administration Server and the Managed Servers on all the machines that are part of
Step 2. Specify the Targets for Deployments

After you run the PostInstallSetup script, specify the Managed Servers to which you want to deploy the
Process Server application.

2. Specify all the Managed Servers as targets for the siperian-mrm-cleanse.ear deployment.
3. Specify all the Managed Servers as targets for the following data sources:
• MDM Hub Master Database data source
• Operational Reference Store datasource
Step 3. Restart WebLogic Server

After you specify the target Managed Servers for the Process Server deployment file, restart the WebLogic
Administration Server and all the Managed Servers.


On UNIX.
the admin server>
On Windows.
the admin server>
Configure Process Server for Multithreading

By default, cleanse operations runs in single-threaded mode and batch jobs run in multi-threaded mode. If
the server on which you install the Process Server has more than one CPU, then you can configure the
cleanse operations to be multithreaded to increase performance. The batch operations are multi-threaded by
default, but you can configure the number of threads to use.
You can use the Hub Console to configure the Process Server for multithreading. You need to set the threads
to use for cleanse operations and batch processes. Consider the following factors when you set the thread
count property:
Number of processor cores available on the machine

Set the number of threads to the number of processor cores available on the machine for cleanse
operations. For example, set the number of threads for a dual-core machine to two threads, and set the
number of threads for a single quad-core to four threads.
Set the number of threads to four times the number of processor cores available on the machine for
batch operations. For example, set the number of threads for a dual-core machine to eight threads, and
set the number of threads for a single quad-core to 16 threads.
Remote database connection

If you use a remote database, set the threads for cleanse operations to a number that is slightly higher
than the number of processor cores, so that the wait of one thread is used by another thread. Setting the
number of threads slightly higher accounts for latency that might occur with a remote database.
Process memory requirements
If you run a memory-intensive process, restrict the total memory allocated to all cleanse operation
threads that run under the JVM to 1 GB.
Note: After migration to a later MDM Hub version, you must change the thread count or default values
are used.
Configuring the Process Server for Multithreading

Use the Hub Console to configure the Process Server for multithreading.
1. Expand the Utilities workbench in the Hub Console, and then click Process Server.
The Process Server tool displays the configured Process Servers.
3. Select the Process Server for which you must configure multithreading.
4. Click Edit Process Server.
The Process Server tool displays the Add/Edit Process Server dialog box.
Configure Process Server for Multithreading 111

5. Set the Threads for Cleanse Operations property.
The default value is 1. You can change the threads for cleanse operations without restarting the Process
Server.
6. Set the Threads for Batch Processing.
The default value is 20.
7. Click OK and then click Save.
Configuring Multiple Process Servers for Cleanse

and Match Operations
You can configure multiple Process Servers for each Operational Reference Store database. You can
configure multiple Process Servers to run on a single machine or on multiple machines.
Ensure that you configure each Process Server to run on a separate application server.
1. Install and configure an instance of the Process Server.

2. Configure multiple application servers.
3. Install and configure the Process Server on each application server.
4. Set the distributed cleanse and match properties in the cmxcleanse.properties file.
The following table describes the distributed cleanse and match properties:
cmx.server.match.distributed_match Specifies whether a Process Server is enabled for

distributed cleanse and match. Set to 1 to enable distributed
cleanse and match.
cmx.server.cleanse.min_size_for_distribution Specifies the minimum size for distribution. The MDM Hub
distributes the cleanse job if the minimum size for
distribution is reached. The default is 1,000.
The cmxcleanse.properties is in the following directory:

5. Deploy the Process Server on each application server.

6. Use the Hub Console to connect to the database.
7. Choose the Process Server tool in the Utilities workbench.
8. Click the Add Process Server button to add the Process Server.
9. Configure properties for each Process Server to enable a distributed cleanse process.

The following table describes the properties to set:
Offline The MDM Hub ignores the settings for the Offline property. Taking the Process Server
online or offline is an administrative task.
Enable Cleanse Specifies whether to use the Process Server for cleanse operations. Enable to use
Operations Process Server for cleanse operations. Disable if you do not want to use the Process
Server for cleansing. Default is enabled.
Threads for Specifies the number of threads that a server must handle. Set the thread count higher
Cleanse than the number of CPUs available.
Operations
Enable Match Specifies whether to use the Process Server for match operations. Enable to use
Processing Process Server for match operations. Disable if you do not want to use the Process
Server for match operations. Default is enabled.
CPU Rating Rates the relative strength of CPUs of the Process Server machines. Assign a higher
rating to a machine with a more powerful CPU. The MDM Hub assigns jobs to
machines based on CPU rating.
10. Click OK and then Save.
Configuring Multiple Process Servers for Batch

Processes
You can configure multiple Process Servers for each Operational Reference Store database. You can
configure multiple Process Servers to run on a single machine or on multiple machines.
Ensure that you configure each Process Server to run on a separate application server.
1. Install and configure an instance of the Process Server.

2. Configure multiple application servers.
3. Install and configure the Process Server on each application server.
4. Deploy the Process Server on each application server.
5. Use the Hub Console to connect to the database.
6. Choose the Process Server tool in the Utilities workbench.
7. Click the Add Process Server button to add a Process Server.
8. Configure properties for each Process Server to enable for batch processing.
Configuring Multiple Process Servers for Batch Processes 113

The following table describes the properties to set:
Offline Specifies whether a Process Server is online or offline. Disable this property to ensure
that a Process Server is online.
Enable Batch Specifies whether to use the Process Server for batch processing. Enable to use
Processing Process Server for batch jobs. Disable if you do not want to use the Process Server
for batch jobs. Default is enabled.
Threads for Batch Specifies the number of threads that a server must handle for batch processing. Set
Processing the threads to four times the number of processor cores available on the machine.
9. Click OK and then Save.
Configure Match Population

The match population contains the standard population set to use for the match process. Each supported
country, language, or population has a standard population set. You must enable the match population to use
for the match rules.
The match population is available as a population.ysp file with the Informatica MDM Hub installation. The
population name is the same as the ysp file name. If you add a Japanese population, and want to use the
Person_Name_Kanji match field, add _Kanji to the population name. For example, Japan_Kanji or
Japan_i_Kanji. If you do this, the standard Person_Name match field is not available.
The population that you use must be compatible with the SSA-Name3 version of the MDM Hub. If you need
additional population files or if you need an updated population file to upgrade to a later version, log a service
request at the Informatica MySupport Portal at http://mysupport.informatica.com. The first population file that
you request with the product is free. You might need population files for other countries or you might need an
updated population file to upgrade to a later version of the MDM Hub.
Enabling Match Population

You must enable the match population to use for the match rules.
1. Copy the <population>.ysp files to the following location:

On UNIX. <infamdm_install_directory>/hub/cleanse/resources/match
On Windows. <infamdm_install_directory>\hub\cleanse\resources\match
2. In the C_REPOS_SSA_POPULATION metadata table, verify that the population is registered.
The seed database for the MDM Hub installation has some populations registered in the
C_REPOS_SSA_POPULATION table, but not enabled.
3. If the C_REPOS_SSA_POPULATION table does not contain the population, add it to the table and
enable it.
The population name is the same as the ysp file name. For example, if the ysp file name is US.ysp, the
population name is US.

To add the population to an Operational Reference Store, use the following steps:
a. Connect to the Operational Reference Store schema that you want to add the population to.
b. In SQL*Plus, run the add_std_ssa_population.sql script in the following directory:
On UNIX. <infamdm_install_directory>/server/resources/database/custom_scripts/oracle
On Windows. <infamdm_install_directory>\server\resources\database\custom_scripts
\oracle
c. Answer the prompts described in the following table:
Prompt Description
Enter the population to add Name of the population.
Enter a value for ROWID_SSA_POP Unique value for the ROWID_SSA_POP column of the
(example: INFA.0001) DEFAULT [INFA. C_REPOS_SSA_POPULATION metadata table. Default is
0001] INFA.0001
The population is registered in the C_REPOS_SSA_POPULATION table.
d. Run the following command to enable the population:

UPDATE c_repos_ssa_population SET enabled_ind = 1 WHERE population_name = '<Your
Population> ';
COMMIT;
4. Restart the Process Server after you enable populations.

5. Log in to the Hub Console to verify that the population is enabled.
The population appears in the Match/Merge Setup user interface for base objects.
Configure Match Population 115

CHAPTER 10
ActiveVOS Post-Installation
Tasks for the Application Server
• Create a Trusted User in WebLogic Environments, 116

• Configure WebLogic for Secure ActiveVOS Communication, 117
• Editing the Default Security Realm, 117
• Adding ActiveVOS Roles, 117
• Creating Groups, 118
• Adding Users, 118
• Editing the abTaskClient Role, 119
Create a Trusted User in WebLogic Environments

To use the ActiveVOS workflow engine, create a trusted user with the role of abTrust, abServiceConsumer,
and abTaskClient in the application server.
The trusted user is the same user as the ActiveVOS workflow adapter user in the Hub Console. The name of
the trusted user cannot be the same name as the application server adminstrative user.
1. In the WebLogic console, create the following roles:

• abTrust
• abServiceConsumer
• abTaskClient
2. In the WebLogic console, create the trusted user, and then assign the user to the abTrust,
abServiceConsumer, and abTaskClient roles.
116
Configure WebLogic for Secure ActiveVOS
Communication
To use the HTTP Secure (HTTPS) protocol for communication between ActiveVOS and the MDM Hub, you
must configure the application server.
1. In the WebLogic console, enable the SSL listen port for the application server.
<infamdm installation directory>\hub\server
For UNIX:
postinstallSetup.sh -Ddatabase.password=<MDM Hub Master Database password> -
For Windows:
postinstallSetup.bat -Ddatabase.password=<MDM Hub Master Database password> -
Editing the Default Security Realm

In WebLogic, a security realm is a container for managing user credentials and roles.
1. In the WebLogic Server Administration Console, in the MDM10 domain, click Security Realms.
2. Click the default realm, called myRealm.
3. Click the Providers tab, and then click the Authentication tab.
4. On the Authentication tab, click DefaultAuthenticator.
5. Click the Configuration tab, and then click the Common tab.
6. From the Control Flag list, select OPTIONAL.
7. Click Save.
8. Restart the WebLogic instance.
Adding ActiveVOS Roles

Add the ActiveVOS roles to the security realm.
2. Select the security realm.
3. Click the Roles and Policies tab, and then click the Realm Roles tab.
4. On the Realm Roles tab, expand Global Roles, and then click Roles.
Configure WebLogic for Secure ActiveVOS Communication 117

5. Click New.
6. In the Name field, type the ActiveVOS role abAdmin and click OK.
7. Click New.
8. In the Name field, type the ActiveVOS role abTaskClient and click OK.
Creating Groups
Create a group for MDM Hub administrators and another group for MDM Hub users.
2. Select the realm you created.
3. Click the Users and Groups tab.
4. Click Groups.
5. Click New.
6. In the Name field, type MDMAVadmins and click OK.
7. Click New.
8. In the Name field, type MDMAVusers and click OK.
Adding Users
Add the MDM Hub administrators and users that you want to authenticate with the ActiveVOS Server.
Note: The user names, passwords, and roles must match in the MDM Hub, ActiveVOS, and WebLogic. The
passwords must adhere to WebLogic password standards.
1. Add users with user credentials that match MDM Hub administrators and MDM Hub users.
a. On the Users and Groups tab, click Users.
b. Click New.
c. In the Name field, type the user name of an MDM Hub administrator or user.
d. In the Password fields, type and retype the password for this user name.
e. Click OK.
f. Repeat to add all the MDM Hub administrators and users that you want to authenticate with the
ActiveVOS Server.
2. Assign the administrators to the MDMAVadmins group.
a. On the Users and Groups tab, click an MDM Hub administrator.
b. Click Groups.
c. In the Available list, select the MDMAVadmins group and move it to the Chosen list.
d. Click Save.
e. Repeat to add the rest of the MDM Hub administrators.
3. Assign the users to the MDMAVusers group.
118 Chapter 10: ActiveVOS Post-Installation Tasks for the Application Server
Editing the abTaskClient Role
Edit the abTaskClient role, and add a security policy to permit users in the MDMAVusers group to
authenticate with the ActiveVOS Server.
1. Click the Roles and Policies tab, and then click the Realm Roles tab.
2. On the Realm Roles tab, expand Global Roles > Roles.
3. In the abTaskClient row, click View Role Conditions.
4. Click Add Conditions.
5. From the Predicate List, select Group.
6. Click Next.
7. In the Group Argument Name field, type MDMAVusers and click Add.
8. Click Finish.
9. Click Save.
Editing the abTaskClient Role 119

CHAPTER 11
ActiveVOS Post-Installation
Tasks for the Business Entity
Adapter
• ActiveVOS Web Applications, 120

• Configuring the ActiveVOS URNs for the Business Entity Workflow Adapter, 121
• Set the ActiveVOS Protocol to HTTPS, 121
• Configure Task Assignment, 122
• Configure Task Triggers, 122
• Setting the Default Approval Workflow for the Entity 360 Framework, 123
• Configure the Primary Workflow Engine, 124
• Generating Business Entity and Business Entity Services Configuration Files, 125
• Configure the MDM Identity Services for ActiveVOS, 125
ActiveVOS Web Applications

When you install the bundled, licensed version of the ActiveVOS Server, you are also licensed to use two
ActiveVOS web applications. After you add users to the application server container, you can use these
applications.
You use the web applications for different purposes:
ActiveVOS Console
Administrators use the ActiveVOS Console to manage deployed processes, the alerting system, and
endpoint locations. You can also configure the engine for performance monitoring and management.
ActiveVOS Central
Business users can use ActiveVOS Central to manage tasks, requests, and reports. However, in
general, business users use an Informatica Data Director (IDD) application to manage tasks because
they can open the entities to review from the Task Manager.
To use ActiveVOS Central, you must add the MDM Hub users to the application server container.
For more information about the web applications, see the Informatica ActiveVOS documentation.
120
Configuring the ActiveVOS URNs for the Business
Entity Workflow Adapter
The ActiveVOS Server has two predefined uniform resource names (URNs) that it uses internally. You need
to update the URL in the URN mappings to use the host name and the port number where the ActiveVOS
Server runs.
1. Launch the ActiveVOS Console. In a browser, type the following URL, substituting the correct host name
and port number:
Encrypted connections.https://[host]:[port]/activevos
Non-encrypted connections.http://[host]:[port]/activevos
2. In the ActiveVOS Console, on the Home page, click Administration > Configure Server > URN
Mappings.
3. For the following URNs, update the paths to reflect the host name and port number of the ActiveVOS
Server:
URN URL Path
ae:internal-reporting Encrypted connections. https://[host]:[port]/activevos/

internalreports
Non-encrypted connections. http://[host]:[port]/activevos/
internalreports
ae:task-inbox Encrypted connections. https://[host]:[port]/activevos-

central/avc
Non-encrypted connections. http://[host]:[port]/activevos-
central/avc
4. Verify that urn:mdm:service is mapped to the host name and port number of the MDM Hub Server:
Encrypted connections.https://[host]:[port]/cmx/services/BeServices
Non-encrypted connections.http://[host]:[port]/cmx/services/BeServices
Set the ActiveVOS Protocol to HTTPS

To enable secure communication between ActiveVOS and the MDM Hub, set the protocol to HTTPS in the
Hub Console Workflow Manager.
You must first configure the application server for HTTPS communications.

2. Acquire a write lock.
3. Click Workflow Manager under the Configuration workbench.
4. In the Workflow Manager, click the Workflow Engines tab.
5. Select the ActiveVOS workflow engine, and then click the Edit button.
6. In the Edit Workflow dialog box, set the protocol to HTTPS.
Configuring the ActiveVOS URNs for the Business Entity Workflow Adapter 121
7. In a WebLogic environment, in the Edit Workflow dialog box, enter the user name and password of the
user that belongs to the abAdmin role.
Configure Task Assignment

To configure task assignment for the ActiveVOS workflow adapter based on business entities, use the IDD
Configuration Manager to configure task assignment for each subject area. The user can either assign the
task directly or allow the Task Manager to assign tasks to users.
1. Log in to the Informatica Data Director Configuration Manager.

http://[host]:[port]/bdd/config/
2. Select the application to update.
3. Click Edit.
4. In the Subject Areas tab, select a subject area, and then click Edit Subject Area.
5. Click the Task Assignment tab, and then click Add.
6. From the Task Assignment dialog box, select the task to configure from the Task list.
7. Select the roles and users to which the task can be assigned. Click OK.
8. Click Save.
9. Click Generate Business Entity Schema. Configuration Manager generates the business entity and
business entity service configuration.
10. In the MDM Hub, use the Repository Manager to validate the Operational References Store. The
Repository Manager validation refreshes the repository data that is cached in the application server.
Configure Task Triggers

You must configure task triggers to use ActiveVOS workflows based on business entities with the Task
Manager. If you do not configure task triggers, the tasks do not appear in the Task Manager.
To configure triggers, use the Provisioning tool to edit the task configuration file from the Advance
Configuration page. For more information, see the Informatica MDM Multidomain Edition Provisioning Tool
Guide.
You can configure the following startWorkflow attributes to configure task triggers:
process
The name of the ActiveVOS workflow process.
taskKind
Defines the type of user interface required for the process. Can be REVIEW, MERGE, or UNMERGE.
The taskKind is returned by the ActiveVOS workflow engine.
taskTemplate
The name of the task template to use.
122 Chapter 11: ActiveVOS Post-Installation Tasks for the Business Entity Adapter
firstTask Type
The first task in the workflow. Optional. This parameter allows the task to be assigned when the task is
created.
Two-step approval code sample

The following code sample shows the startWorkflow element configuration for the ActiveVOS adapter
based on business entities for the two-step approval task:
<startWorkflow process="BeTwoStepApprovalTask" taskKind="REVIEW"

taskTemplate="DefaultApproval" firstTaskType="AVOSBeReviewNoApprove"/>
One-step approval code sample

based on business entities for the one-step approval task:
<startWorkflow process="BeOneStepApprovalTask" taskKind="REVIEW"

taskTemplate="DefaultApproval" firstTaskType="AVOSBeFinalReview"/>
Update with approval code sample

based on business entities for the update-with-approval task:
<startWorkflow process="BeUpdateWithApprovalTask" taskKind="REVIEW"

taskTemplate="DefaultApproval" firstTaskType="AVOSBeUpdate"/>
Setting the Default Approval Workflow for the Entity

360 Framework
When a user creates or updates a business entity, a default approval workflow is triggered upon clicking
save. To configure a workflow as the default workflow, use the Provisioning tool.
1. Log in to the Provisioning tool.

2. Click Advanced Configuration > Task Configuration (XML).
The task configuration XML file appears.
3. To configure the task properties for tasks created by the default workflow, add the default approval task
template configuration to the XML file.
The following code sample shows a default approval task template that sets the priority to NORMAL,
sets the due date to seven days from the current date, and sets the status of the task to OPEN:
<taskTemplate name="DefaultApproval">
<title>Review changes in (taskRecord[0].label)</title>
<priority>NORMAL</priority>
<dueDate>+7d</dueDate>
<status>OPEN</status>
</taskTemplate>
4. To specify which workflow is triggered by default, add the default approval trigger configuration to the
XML file.
Setting the Default Approval Workflow for the Entity 360 Framework 123
The following code sample shows the ReviewNoApprove workflow set as the default workflow when
users of any role create or update a business entity:
<trigger name="DefaultApproval">
<startWorkflow process="ReviewNoApprove" taskKind="REVIEW"
taskTemplate="DefaultApproval"/>
<event name="CreateBE"/>
<event name="UpdateBE"/>
<role name="*"/>
</trigger>
5. Click Validate + Publish.
6. Log in to the IDD Configuration Manager.
7. Select the IDD application, and then click Clear Cache.
Configure the Primary Workflow Engine

To configure the primary workflow engine, add a workflow engine for ActiveVOS workflows based on
business entities. The secondary workflow engine is for existing customers who want to process existing
tasks with a deprecated workflow engine.
1. In the Hub Console, click Workflow Manager in the Configuration workbench.

2. Acquire a write lock.
3. Select the Workflow Engines tab and click the Add button.
4. In the Add Workflow dialog box, enter the workflow engine properties.
The following table describes the workflow engine properties:
Field Description
Workflow Engine The display name of the workflow engine
Adapter Name Select BE ActiveVOS for the ActiveVOS workflow adapter based on composite objects.
Host The host name of the Informatica ActiveVOS instance.
Post The port name of the Informatica ActiveVOS instance.
Username The user name of the trusted user.
Password The password of the trusted user.
Protocol The protocol for communication between the MDM Hub and ActiveVOS. The protocol
can be http or https.
5. Click OK.
124 Chapter 11: ActiveVOS Post-Installation Tasks for the Business Entity Adapter
Generating Business Entity and Business Entity
Services Configuration Files
To generate business entity and business entity services configuration files, use the Informatica Data Director
Configuration Manager.
1. In the Configuration Manager Applications pane, select the Informatica Data Director application whose
configuration you want to generate into a business entity and business entity service configuration.
2. Click Generate Business Entity Schema.
Configuration Manager generates the business entity and business entity service configuration.
3. Configuration Manager displays messages of issues encountered while generating the business entity
and business entity services configuration. The messages indicate if Configuration Manager resolved the
issue during the generation process and describes the changes Configuration Manager made to resolve
the issue. If Configuration Manager did not fix the issue, note the issue and the suggested action you
can take to resolve the issue.
Configure the MDM Identity Services for ActiveVOS

If you use embedded ActiveVOS, ensure that you configure ActiveVOS to use MDM Identity Services. To
configure the MDM Identity Services for ActiveVOS, use the ActiveVOS Console to set the Identity Services
password to the password of the MDM Hub workflow engine user.
1. In the ActiveVOS console, select Admin > Configure Services > Identity Services.
2. In the Provider Configuration section, enable the Enable check box and select MDM from the Provider
Type list.
3. In the Connection tab, enter the password of the MDM Hub user with the user name admin.
4. Click Update.
5. Test that ActiveVOS can log in to the MDM Hub as the admin user, and that ActiveVOS can retrieve a list
of roles for the user you specify as the User for test.
a. Select the Test tab.
b. In the User for test field, enter an MDM Hub user that is assigned to a role.
c. Click Test Settings.
Note: The test fails if an Operational Reference Store is not configured and the user for test does
not belong to a role.
Generating Business Entity and Business Entity Services Configuration Files 125
CHAPTER 12
Resource Kit Installation

• Setting Up the MDM Hub Sample Operational Reference Store, 126

• Registering the Informatica MDM Hub Sample Operational Reference Store, 129
• Installing the Resource Kit in Graphical Mode, 131
• Installing the Resource Kit in Console Mode, 134
• Installing the Resource Kit in Silent Mode, 136
Setting Up the MDM Hub Sample Operational

Reference Store
Before you can use the MDM Hub sample Operational Reference Store, you must set it up. Before you install
the Resource Kit, set up the MDM Hub sample Operational Reference Store. To set up the MDM Hub sample
Operational Reference Store, create an Operational Reference Store and import mdm_sample into it.

On UNIX. sip_ant.sh create_ors
On Windows. sip_ant.bat create_ors
next prompt.
Enter database type. (ORACLE, MSSQL, DB2)
Database type. Specify ORACLE.
Enter Oracle Connection Type (service, sid). [service]

Connection type. Use one of the following values:
• SERVICE. Uses the service name to connect to Oracle.
• SID. Uses the Oracle System ID to connect to Oracle.
126
Default is SERVICE.
Enter the Operational Reference Store database host name. [localhost]

Name of the machine that hosts the database. Default is localhost.
Enter the Operational Reference Store database port number. [1521]

Port number that the database listener uses. Default is 1521.
Enter the Operational Reference Store database service name. [orcl]

Name of the Oracle service. This prompt appears if the selected Oracle connection type is
SERVICE.
Enter the Operational Reference Store database SID. [orcl]

Name of the Oracle system identifier. This prompt appears if the selected Oracle connection type is
SID.
Enter Oracle Net connect identifier (TNS Name) [orcl]

Oracle TNS name. Default is orcl.
Connect URL. [jdbc:oracle:thin:@//<host name>:<port>/<service_name or SID>]
Connect URL for the database connection.
Enter the Operational Reference Store database user name. [cmx_ors]

User name of the MDM Hub sample Operational Reference Store database. Default is cmx_ors.
Enter the Operational Reference Store database user password.

Password of the MDM Hub sample Operational Reference Store user.
Enter a locale name from the list: de, en_US, fr, ja, ko, zh_CN. [en_US]
Operating system locale. Default is en_US.
Enter the DBA user name. [SYS]

User name of the administrative user. Default is SYS.
Enter the DBA password.

Password of the administrative user.
Enter the name of the MDM index tablespace. [CMX_INDX]

Name of the tablespace to contain the index components for the Operational Reference Store.
Default is CMX_INDX.
Enter the name of the MDM temporary tablespace. [CMX_TEMP]

Name of the tablespace to contain the temporary components for the Operational Reference Store.
Default is CMX_TEMP.
Enter the name of the Oracle temporary tablespace. [TEMP]

Name of the Oracle temporary tablespace. Default is TEMP.
4. After you create the sample Operational Reference Store, review sip_ant.log in the following directory:
Setting Up the MDM Hub Sample Operational Reference Store 127

5. To import mdm_sample, run the following command:
On UNIX. sip_ant.sh import_schema
On Windows. sip_ant.bat import_schema
next prompt.
Enter database type. (ORACLE, MSSQL, DB2)
Database type. Specify ORACLE.
Enter Oracle Connection Type (service, sid). [service]

Connection type. Use one of the following values:
• SERVICE. Uses the service name to connect to Oracle.
• SID. Uses the Oracle System ID to connect to Oracle.
Default is SERVICE.
Enter the Operational Reference Store database host name. [localhost]

Name of the machine that hosts the database. Default is localhost.
Enter the Operational Reference Store database port number. [1521]

Port number that the database listener uses. Default is 1521.
Enter the Operational Reference Store database service name. [orcl]

Name of the Oracle service. This prompt appears if the selected Oracle connection type is
SERVICE.
Enter the Operational Reference Store database SID. [orcl]

Name of the Oracle system identifier. This prompt appears if the selected Oracle connection type is
SID.
Enter Oracle Net connect identifier (TNS Name) [orcl]

Oracle TNS name. Default is orcl.
Connect URL. [jdbc:oracle:thin:@//<host name>:<port>/<service_name or SID>]
Connect URL for the database connection.
Enter the Operational Reference Store database user name. [cmx_ors]

Name of the MDM Hub sample Operational Reference Store database. Default is cmx_ors.
Enter the Operational Reference Store database user password.

Name of the MDM Hub sample Operational Reference Store database user.
Enter a locale name from the list: de, en_US, fr, ja, ko, zh_CN. [en_US]
Operating system locale. Default is en_US.
Enter the path to the ZIP dump file. [<distribution directory>\resources\database]
Path to the mdm_sample.zip file.
Enter the name of the ZIP dump file. [mdm_sample.zip]

Name of the ZIP dump file. Default is mdm_sample.zip.
128 Chapter 12: Resource Kit Installation

Registering the Informatica MDM Hub Sample
Operational Reference Store
After you set up the MDM Hub sample Operational Reference Store, you must register it. Register the MDM
Hub sample Operational Reference Store through the Hub Console.

2. Select the MDM Hub Master Database, and click Connect.
3. Start the Databases tool under the Configuration workbench.
5. Click the Register database button.
The Informatica MDM Hub Connection Wizard appears and prompts you to select the database type.
6. Select the type of database, and click Next.
7. Configure connection properties for the database.
a. Select an Oracle connection method, and click Next.
The following table describes the Oracle connection methods that you can select:
Connection Method Description
Service Connect to Oracle by using the service name.
SID Connect to Oracle by using the Oracle System ID.
b. Specify the connection properties for the connection type that you select, and click Next.
The following table lists and describes the connection properties:
Database Name for the Operational Reference Store that must appear in the Hub Console.
Display Name
Machine Prefix fixed to keys to uniquely identify records from the Hub Store instance.
Identifier
Database IP address or name of the server that hosts the Oracle database.
hostname
SID Oracle System Identifier that refers to the instance of the Oracle database running
on the server. The SID field appears if you selected the SID connection type.
Registering the Informatica MDM Hub Sample Operational Reference Store 129
Service Name of the Oracle SERVICE used to connect to the Oracle database. The Service
field appears if the you selected the Service connection type.
Port The TCP port of the Oracle listener running on the Oracle database server. The
default is 1521.
Oracle Name of the database on the network as defined in the TNSNAMES.ORA file of the
TNS Name application server.
For example: mydatabase.mycompany.com.
You set the Oracle TNS name when you install the Oracle database. For more
information about the Oracle TNS name, see the Oracle documentation.
Schema Name Name of the Operational Reference Store. Specify mdm_sample.
Password Password associated with the user name for the Operational Reference Store.
For Oracle, the password is not case sensitive.
By default, this is the password that you specify when you create the Operational
Reference Store.
The Summary page appears.
c. Review the summary, and specify additional connection properties.

The following table lists additional connection properties that you can configure:
Connection URL Connect URL. The Connection Wizard generates the connect URL by
default. The following list shows the format of the connect URL for the
Oracle connection types:
Service connection type
jdbc:oracle:thin:@//database_host:port/
service_name
SID connection type

jdbc:oracle:thin:@//database_host:port/sid
For a service connection type, you have the option to customize and
later test a different connection URL.
Create data source after Select to create the data source on the application server after
registration registration.
Note: If you do not select the option, you must manually configure the
data source.
d. For a service connection type, if you want to change the default URL, click the Edit button, specify
the URL, and then click OK.
8. Click Finish.
The Registering Database dialog box appears.
9. Click OK.

The MDM Hub registers the MDM Hub sample Operational Reference Store.
10. Select the MDM Hub sample Operational Reference Store that you registered, and click the Test
database connection button to test the database settings.
The Test Database dialog box displays the result of the database connection test.
11. Click OK.
The Operational Reference Store is registered, and the connection to the database is tested.
Installing the Resource Kit in Graphical Mode

You can install the Resource Kit in graphical mode.
Before you install the Resource Kit, you must have installed and configured the MDM Hub.

2. Open a command prompt and navigate to the Resource Kit installer. By default the installer is in the
On UNIX. <distribution directory>/<operating system name>/mrmresourcekit
On Windows. <distribution directory>\windows\mrmresourcekit
On UNIX. hub_resourcekit_install.bin
On Windows. hub_resourcekit_install.exe
5. Click Next.
The Installation Feature window appears.
7. Select the Resource Kit features that you want to install and click Next.
You can select the following options:
Sample Schema
Installs the MDM Hub sample schema resources. You must create a sample schema and register it
with the Hub Server before you install the sample applications.
Samples and Utilities

Installs the sample applications and utilities.
The list of sample applications that are deployed is stored in the build.properties file in the
<Resourcekit_Home>\samples
SIF SDK and Javadocs

Installs the javadocs, libraries, and resources associated with the SIF SDK.
Installing the Resource Kit in Graphical Mode 131

BPM SDK
Installs the resources associated with the BPM SDK.
Jaspersoft
Copies the Jaspersoft installer to the Resource Kit home.
SSA-NAME3
Copies the SSA-NAME3 installer to the Resource Kit home.
A message about the requirement of having created and registered a sample schema with the MDM Hub
appears.
8. Click OK.
9. Select the location of the Resource Kit installation.
• To return to the default installation location, click Restore Default Folder.
10. On UNIX, choose a link folder or select the option to not create links, and click Next. On Windows, select
The Configuration Selection window appears.
11. Select a configuration option, and click Next.
You can select one of the following options:
Configure Samples
Installs and configures the samples.
Source Only
Installs the sources of samples but does not configure the samples.
If you select Configure samples, the Resource Kit App Server window appears. If you select Source
only, the Pre-Installation Summary window appears.
12. From the Resource Kit App Server window, select the application server on which you want to install
the Resource Kit, and click Next.
The Application Server Home window for the application server that you select appears.
13. Configure the application server settings.
the MDM Hub, and click Next.

b. Enter the WebLogic Server login information.
Enter values in the following login parameter fields:
Host
Name of the host computer that has the WebLogic installation.
Server
Name of the WebLogic Server instance in the domain on which WebLogic is deployed.
User Name
Name of the user for the WebLogic installation.
Password
Password that corresponds to the WebLogic user.
Port Number
Port number on which the WebLogic Server is listening.
The Informatica MDM Hub Server window appears.
14. Enter the information for the Hub Server installation, and click Next.
Enter values in the following fields:
Server Name
Name of the server that hosts the Hub Server.
Server HTTP Port

Port number of the Hub Server.
Informatica MDM Administrative password

Password to access the MDM Hub.
The Resource Kit ORS ID window appears.

15. Select a Resource Kit ORS ID from the list, and then click Next.
The list contains the Operational Reference Store IDs that you created. Select an Operational Reference
Store ID related to the sample schema.
If you have not registered the sample schema, you will not see the Operational Reference Store ID for
the sample schema. Register the sample Operational Reference Store, and then restart the installation.
The Deployment Selection window appears.
16. Select one of the following options and click Next:
Yes, run it during this installation.
Deploys and configures the Resource Kit during the installation.
No, it can be deployed later.

Select this option to deploy and configure manually at a later time.
If you chose to install the Samples and Utilities feature, you must deploy and configure the
Resource Kit in this installation step. If you do not deploy the Resource Kit in this step, you cannot
make changes and redeploy the samples by using the postInstallSetup script provided in the
Resource Kit.
If you choose to run the post-installation setup manually, you cannot deploy the EAR file by using
the postInstallSetup script at a later time. You must manually edit the EAR file and deploy it to make
any changes to your installation.
Installing the Resource Kit in Graphical Mode 133

17. Review the Pre-Installation Summary to confirm your installation choices, and then click Install.
18. Click Done to exit the Resource Kit installer.
Installing the Resource Kit in Console Mode

You can install the Resource Kit in console mode.
Ensure that you register the MDM_SAMPLE schema before you install the Resource Kit.

On UNIX. <distribution directory>/<operating system name>/resourcekit
On Windows. <distribution directory>/windows/resourcekit
On UNIX. ./hub_resourcekit_install.bin -i console
On Windows. hub_resourcekit_install.exe -i console
5. Press Enter.
6. Read the License Agreement. Type Y to accept the terms of the license agreement, or type N if you do
not want to accept the license agreement and want to exit the installation program.
7. Press Enter.
8. Enter the numbers of the Resource Kit features that you want to install separated by commas, and press
Enter.
The prompt for the sample schema installation appears.
9. Choose a folder for the Resource Kit installation.
• To choose the default folder, press Enter.
10. Confirm the location of the installation folder. Type OK to confirm the installation folder or type Cancel to
11. Press Enter.
A list of link location options appears.
12. Enter the number of a link location option.
The prompt for the link file location appears.
13. Enter the absolute path of the link file, and press Enter.
The source sample configuration options appears.

14. Enter a configuration option, and press Enter.
Option Description
1 Installs and configures the samples
2 Installs the sources of samples but does not configure the samples
If you enter 1, a list of application server options appears. If you enter 2, the pre-Installation summary
appears.
15. If you entered 1, enter the number for the application server that you want to select, and press Enter.
The application server information prompts appear.
a. Specify the path to the WebLogic domain in which you want to install the Resource Kit, and press
Enter.
The Hub Server installation information prompts appear.
17. Enter the information for the Hub Server installation, and press Enter.
The following table describes the prompts for the Hub Server installation information:
Prompt Description
Server Name Name of the server that hosts the Hub Server.
Server HTTP Port Port number of the Hub Server.
Informatica MDM Administrative password Password to access the MDM Hub.
A list of MDM Hub ORS IDs appears.
18. Enter the Operational Reference Store ID of the MDM sample schema, and press Enter.
If you did not register the sample schema, you will not see the Operational Reference Store ID for the
sample schema. Register the sample Operational Reference Store, and then restart the installation.
The deployment selection prompt appears.
manually later.
20. Press Enter.
the installation.
The Resource Kit is installed according to the configuration information you provide. When the process is
complete, the installation complete information appears.
Installing the Resource Kit in Console Mode 135

Installing the Resource Kit in Silent Mode
You can install the Resource Kit without user interaction in silent mode. You might want to perform a silent
Before you run the silent installation for the Resource Kit, you must configure the properties file for the silent
installation. The installer reads the file to determine the installation options. The silent installation process
might complete successfully even if you provide incorrect settings, such as an incorrect application server
path or port. You must ensure that you provide correct settings in the properties file.
Copy the Resource Kit installation files to the hard disk on the machine where you plan to install the
Resource Kit. To install in silent mode, complete the following tasks:

1. Find the silentInstallResourceKit_sample.properties file in the following directory:

On UNIX. /silent_install/mrmresourcekit
On Windows. \silent_install\mrmresourcekit
After you customize the file, save it. You can rename the file and put it anywhere on the machine.
each of these characters when you enter information in the file, such as when you enter an installation
path. For example, to enter the path to the server directory, you must enter \\u1\\infamdm\\hub\
\resourcekit.
2. Create a backup copy of the silentInstallResourceKit_sample.properties file.
4. Save the properties file with a new name such as silentInstallresourcekit.properties.
The following table describes the installation parameters that you can change:
INSTALLER_UI Specifies the mode of installation. Set to silent.
SIP.INSTALL.TYPE Specifies the type of installation. Set to SIPERIAN_SAMPLE_INSTALL.
SIP.INSTALL.SAMPLE.SCHEMA Specifies if you want to install the sample schema.

Specify one of the following values:
- 0. Does not install the sample schema
- 1. Installs the sample schema

SIP.INSTALL.SAMPLES Specifies if you want to install samples and utilities.

- 0. Does not install samples and utilities
- 1. Installs samples and utilities
SIP.INSTALL.SIF.SDK Specifies if you want to install the Services Integration Framework (SIF) SDK.
- 0. Does not install the SIF SDK
- 1. Installs SIF SDK
SIP.INSTALL.BPM.SDK Specifies if you want to install the BPM SDK.

- 0. Does not install the BPM SDK
- 1. Installs the SIF SDK
SIP.INSTALL.JASPERSOFT Specifies if you want to install the Jaspersoft reporting tool.

- 0. Does not install the BPM SDK
- 1. Installs the SIF SDK
SIP.INSTALL.SSANAME3 Specifies if you want to install SSA-NAME3.

- 0. Does not install SSA-NAME3
- 1. Installs SSA-NAME3
USER_INSTALL_DIR Directory where you want to install the Resource Kit, such as C\:\
\<infamdm_install_directory>\\hub\\resourcekit.
RUN_CONFIGURE_FLAG Specifies if you want to configure samples.

- 0. Does not configure samples
- 1. Installs and configures samples
Default is 1.
If you set the RUN_CONFIGURE_FLAG property to 1, comment out or set
the RUN_CONFIGURE_SETUP property to 0. To configure samples, ensure
that the application server and the Hub Server are started and the sample
schema is registered in the Hub Console.
RUN_CONFIGURE_SETUP Specifies if you want to configure only source samples.

- 0. Does not install sources of samples
- 1. Installs sources of samples
If you set the RUN_CONFIGURE_SETUP property to 1, comment out or set
the RUN_CONFIGURE_FLAG property to 0. If you set the
RUN_CONFIGURE_SETUP property to 1, you cannot configure and deploy
samples later.
Installing the Resource Kit in Silent Mode 137

SIP.SERVER.NAME Name of the server on which the Hub Server is deployed.
SIP.SERVER.HTTP.PORT Port on which the Hub Server is listening.
SIP.ADMIN.PASSWORD Password to access the Hub Server.
SIP.ORS.ID Operational Reference Store ID of the MDM Hub sample schema.
RUN_DEPLOYMENT_FLAG Runs the postInstallSetup script as part of the silent installation.

- 0. Does not run the postInstallSetup script
- 1. Runs the postInstallSetup script

The following example shows the contents of the sample silentInstallResourceKit_sample.properties
file:
INSTALLER_UI=silent
SIP.INSTALL.TYPE=SIPERIAN_SAMPLE_INSTALL
#Installation Features
#0=Do not install
#1=Install
SIP.INSTALL.SAMPLE.SCHEMA=1
SIP.INSTALL.SAMPLES=1
SIP.INSTALL.SIF.SDK=1
SIP.INSTALL.BPM.SDK=1
SIP.INSTALL.JASPERSOFT=1
SIP.INSTALL.SSANAME3=1
## Resource Kit Install directory.

USER_INSTALL_DIR=C\:\\siperian\\hub\\resourcekit
## If you want to configure samples as a part of silent installation, set following

property:
RUN_CONFIGURE_FLAG=1
## If you want to install only source samples as a part of silent installation, set
following property:
#RUN_CONFIGURE_SETUP=0
## Set the properties for one of the application servers JBoss, WebSphere, or WebLogic.
## properties for WebLogic application server

SIP.AS.HOME=C\:\\weblogic\\user_projects\\domains\\base_domain
## properties for MDM Hub Server

SIP.SERVER.NAME=localhost
SIP.SERVER.HTTP.PORT=7001

SIP.ADMIN.PASSWORD=admin
#sip ors id from hub server

SIP.ORS.ID=localhost-orcl-MDM_SAMPLE
## If you want to run postInstallSetup as a part of silent installation, set the

following property:
## If you want to run postInstallSetup as a part of silent installation, set the
following property:


On UNIX. ./hub_resourcekit_install.bin -f
<location_of_silent_properties_file_for_resourcekit>
On Windows. .\hub_resourcekit_install.exe -f
<location_of_silent_properties_file_for_resourcekit>
The silent installer runs in the background. The process can take a while. Check the postinstallSetup.log
files to verify that the installation was successful.
On UNIX. <infamdm_install_directory>/logs/postInstall.log
On Windows. <infamdm_install_directory>\logs\postInstall.log
Installing the Resource Kit in Silent Mode 139

CHAPTER 13
Troubleshooting the MDM Hub

This chapter includes the following topic:
• Troubleshooting the Installation Process, 140
Troubleshooting the Installation Process

If the installation fails, use the following information to troubleshoot the failure.
PostInstallSetUp script fails because the ActiveVOS server deployment times out
When you install the Hub Server, the post-installation setup process might fail after trying to deploy the
ActiveVOS server.
To resolve the issue, increase the value of the deploy.wait.time property in the build.properties file in
the following directory:
On UNIX. <infamdm installation directory>/hub/server/bin
On Windows. <infamdm installation directory>\hub\server\bin
PostInstallSetUp script fails with java.lang.OutOfMemoryError

When you install the Hub Server in a Solaris operating system, the postInstallSetUp script might fail with
java.lang.OutOfMemoryError.
To resolve the issue, perform the following steps after you complete the installation:
1. Open the build.properties file in the following directory:

<infamdm installation directory>/hub/server/bin
2. In the <wldeploy> target, add following memory settings:
<jvmarg value="-Xms2048m"/>
<jvmarg value="-Xmx2048m"/>
<jvmarg value="-XX:PermSize=512m"/>
<jvmarg value="-XX:MaxPermSize=1024m"/>
3. Save the file.
4. Run the postInstallSetUp script.
Inaccurate start or stop timestamp for Operational Reference Store

When you export an Operational Reference Store that you create, the MDM Hub creates a .dmp file. You can
reuse the .dmp file of the Operational Reference Store to create a second Operational Reference Store. The
start date and end date columns in the C_REPOS_DB_VERSION table of the Operational Reference Store
will contain incorrect start date and end date. You can ignore this error as it does not affect any functionality.
140
The Hub Server cannot connect to the cmx_system schema
To verify that the Hub Server cannot connect to the cmx_system schema, review the application server log.
For example, you might find the following error, which confirms that the database is not accessible:
Caused by: java.sql.SQLException: ORA-28000: the account is locked
DSRA0010E: SQL State = 99999, Error Code = 28,000
To resolve the issue, resolve the database connection issue. Use the application server console to test the
connection to the database. If you cannot resolve the connection to the cmx_system schema, re-create the
cmx_system schema.
Failed to verify the need to tokenize records

When you run the Match process, you might receive the following error:
SIP-16062: Failed to verify the need to tokenize records.
Verify the following environment variable settings:
• The library path environment variable must contain the following path:
On UNIX. <infamdm_install_directory>/hub/cleanse/lib
On Windows. <infamdm_install_directory>\hub\cleanse\lib
The library path environment variable depends on the operating system:
- AIX. LIBPATH
- HP-UX. SHLIB_PATH
- Solaris, Suse, or RedHat. LD_LIBRARY_PATH
- Windows. PATH
• The SSAPR environment variable must include the following path for all users:
On UNIX. <infamdm_install_directory>/server_install_dir>/cleanse/resources
On Windows. <infamdm_install_directory>\server_install_dir>\cleanse\resources
major.minor version errors when loading the Process Server

If you see multiple major.minor console errors when you try to load the Process Server, check that the
system has the correct Java version installed.
Hub Server cache timeout exception

If the Hub server cannot acquire a cache object lock, you must change the jbossCacheConfig.xml file to
increase the lock acquisition and replication timeouts. The jbossCacheConfig.xml file is in the following
location:
On UNIX. <infamdm_install_dir>/server/resources/jbossCacheConfig.xml.
On Windows. <infamdm_install_dir>\server\resources\jbossCacheConfig.xml.
For example, increase lock acquisition timeout and replication timeout as shown in the following sample:
<locking
...
lockAcquisitionTimeout="30000"
...
/>
<sync replTimeout="30000"/>
Troubleshooting the Installation Process 141

Address Doctor exception during certification
Address Doctor generates an exception during certification. Ensure that the stack size for the JVM is
sufficient.
1. Navigate to the WebLogic home directory.

2. Open the following file in a text editor.
On UNIX. setDomainEnv.sh
On Windows. startWeblogic.cmd
3. Use the following command to set the MEM_ARGS variable:
On UNIX.
set MEM_ARGS=${MEM_ARGS} -Xss2000k
On Windows.
set MEM_ARGS=%MEM_ARGS% -Xss2000k
4. Save and close the file.
Operational Reference Store does not have a workflow engine configured

If you install the MDM Hub and then import an Operational Reference Store (ORS) from a previous version,
you see a fatal error that indicates that the ORS does not have a workflow engine configured. This error
occurs because the Siperian BPM workflow engine is not registered by default. Use the Workflow Manager to
register the Siperian BPM workflow engine with the name that the ORS expects to find.
142 Chapter 13: Troubleshooting the MDM Hub

CHAPTER 14
Uninstallation
• Uninstallation Overview, 143

• Uninstalling the Hub Store, 143
• Uninstalling the Process Server in Graphical Mode, 144
• Uninstalling the Hub Server in Graphical Mode, 145
• Uninstalling the Resource Kit in Graphical Mode, 145
• Uninstalling the Process Server in Console Mode, 146
• Uninstalling the Hub Server in Console Mode, 146
• Uninstalling the Resource Kit in Console Mode, 147
• Manually Undeploying the Process Server, 147
• Manually Undeploying the Hub Server, 147
Uninstallation Overview
To uninstall the MDM Hub, you need to remove the Process Server, the Hub Server, and the Hub Store from
the MDM Hub implementation.
Use the following steps to uninstall the MDM Hub:
1. Uninstall the Hub Store.

2. Uninstall the Process Server.
3. Uninstall the Hub Server.
Uninstalling the Hub Store

You can uninstall the Hub Store by dropping the Hub Store schemas and removing the user logins for the
Hub Store schemas. Before you drop the Hub Store schemas, use the Hub Console to unregister the Hub
Store schemas.
You must have administrator privileges to drop the Hub Store schemas.
143
2. Click the Databases tool under the Configuration workbench.
The Database Information page appears.
4. From the list of databases, select the Operational Reference Store to unregister.
5. Click the Unregister database button.
The Databases tool prompts you to confirm unregistering the Operational Reference Store.
6. Click Yes.
7. Use SQL*Plus to connect to the Oracle instance.
8. Use the following command for each Hub Store schema to drop the schema:
drop user <user name> cascade;
If you drop the schemas with the cascade option, the associated schemas are dropped.
Uninstalling the Process Server in Graphical Mode

You can uninstall the Process Server in graphical mode.
Uninstalling the Process Server in Graphical Mode On UNIX

To uninstall the MDM Hub, you must remove the Process Server. You must perform the steps to uninstall the
Process Server for each Process Server in the MDM Hub implementation.
1. Stop the application server.

<infamdm_install_directory>/hub/cleanse/UninstallerData
3. Run the uninstaller.
./"Uninstall Informatica MDM Hub Cleanse Match Server"
4. Click Uninstall.
When the uninstallation process is complete, the Uninstall Complete window appears.
5. Click Done.
Uninstalling the Process Server in Graphical Mode On Windows

To uninstall the MDM Hub, you must remove the Process Server. You must perform the steps to uninstall the
Process Server for each Process Server in the MDM Hub implementation.

2. Click Start and then click Programs > Infamdm > Hub > Cleanse > Uninstaller Data > Uninstall
Informatica MDM Hub Cleanse Match Server.
The Uninstall introduction window appears.
3. Click Uninstall.
4. Click Done.
144 Chapter 14: Uninstallation

Uninstalling the Hub Server in Graphical Mode
You can uninstall the Hub Server in graphical mode.
Uninstalling the Hub Server in Graphical Mode on UNIX

To uninstall the MDM Hub, you must remove the Hub Server from the MDM Hub implementation.
1. Ensure that you stop the application server.

<infamdm_install_directory>/hub/server/UninstallerData
3. Run the uninstaller.
./"Uninstall Informatica MDM Hub Server"
4. Click Uninstall.
5. Click Done.
Uninstalling the Hub Server in Graphical Mode on Windows

To uninstall the MDM Hub, you must remove the Hub Server from the MDM Hub implementation.
1. Ensure that you stop the application server.

2. Click Start and then click Programs > Infamdm > Hub > Server > UninstallerData > Uninstall
Informatica MDM Hub Server.
3. Click Uninstall.
4. Click Done.
Uninstalling the Resource Kit in Graphical Mode

You can uninstall the Resource Kit in graphical mode.
Uninstalling the Resource Kit in Graphical Mode on UNIX

To uninstall the Resource Kit, you must remove the Resource Kit from the MDM Hub implementation.

<infamdm_install_directory>/hub/resourcekit/UninstallerData
./"Uninstall Informatica MDM Hub Resource Kit"
The Uninstall Informatica MDM Hub Resource Kit window appears.
Uninstalling the Hub Server in Graphical Mode 145

4. Click Uninstall.
The Uninstall Complete window appears with a list of items that could not be removed.
5. Click Done.
6. Manually remove the following directory:
<infamdm_install_dir>/hub/resourcekit
Uninstalling the Resource Kit in Graphical Mode on Windows

To uninstall the Resource Kit, you must remove the Resource Kit from the MDM Hub implementation.

<ResourceKit_install_dir>\deploy\UninstallerData
3. Double-click Uninstall Informatica MDM Hub Resource Kit.exe
The Uninstall Informatica MDM Hub Resource Kit window appears.
4. Click Uninstall.
The Uninstall Complete window appears with a list of items that could not be removed.
5. Click Done.
6. Manually remove the following directory:
<infamdm_install_dir>\hub\resourcekit
Uninstalling the Process Server in Console Mode

You can uninstall the Process Server in console mode on UNIX. If you installed the Process Server in
console mode, uninstall the Process Server in console mode.
1. Go to the following directory:

<infamdm_install_dir>/hub/cleanse/UninstallerData
2. Type the following command to run the uninstaller:
./"Uninstall Informatica MDM Hub Cleanse Match Server"
Uninstalling the Hub Server in Console Mode

You can uninstall the Hub Server in console mode on UNIX. If you installed the Hub Server in console mode,
uninstall the Hub Server in console mode.

<infamdm_install_dir>/hub/server/UninstallerData
2. Type the following command to run the uninstaller:
./"Uninstall Informatica MDM Hub Server"
146 Chapter 14: Uninstallation

Uninstalling the Resource Kit in Console Mode
You can uninstall the Resource Kit in console mode. If you installed the Resource Kit in console mode,
uninstall the Resource Kit in console mode.

On UNIX. <infamdm_install_dir>/hub/resourcekit/UninstallerData
On Windows. <infamdm_install_dir>\hub\resourcekit\UninstallerData
On UNIX. "Uninstall Informatica MDM Hub Resource Kit.bin" -i console
On Windows. "Uninstall Informatica MDM Hub Resource Kit.exe" -i console
Manually Undeploying the Process Server

You might need to manually undeploy the Process Server from the WebLogic Server environment.
u Use the WebLogic Server Administration Console to manually undeploy the siperian-mrmcleanse.ear
file.
Manually Undeploying the Hub Server

You might need to manually undeploy the Hub Server from the WebLogic Server environment.
u Use the WebLogic Server Administration Console to undeploy the following deployment files:
Uninstalling the Resource Kit in Console Mode 147

APPENDIX A
Installation and Configuration

Checklist
This appendix includes the following topics:
• Installation Checklist Overview, 148

• Step 1. Pre-Installation Tasks, 148
• Step 2. Create the Hub Store, 150
• Step 3. Install the Hub Server, 150
• Step 4. Hub Server Post-Installation Tasks, 151
• Step 5. Install the Process Server, 151
• Step 6. Process Server Post-Installation Tasks, 152
• Step 7. Install the Resource Kit (Optional), 152
Installation Checklist Overview

The installation and configuration checklist summarizes the tasks that you must perform to complete an
installation.
Step 1. Pre-Installation Tasks

Before you install, perform the following tasks:
 Read the Release Notes for updates to the installation process.
 Download and extract the installer files.
 Verify the license key. Before you install the software, verify that you have the license key for the product
you plan to install. Contact Informatica Global Customer Support if you do not have a license key.
 Verify the minimum system requirements to install MDM Multidomain Edition.
 Set up the environment variables you must configure to work with the MDM Multidomain Edition
installation.
148
 Set an operating system locale for the MDM Hub components.
 Set up the X Window Server. If you want to run the installer in graphical mode on UNIX, set up the X
Window Server.
 Install and configure Oracle according to instructions in the Oracle documentation.

• Disablethe Oracle Recycle Bin. Disable the Oracle Recycle Bin because it can interfere with the MDM
Hub processes.
• Set the NLS_LANG environment variable. Set the NLS_LANG environment variable for the environment
in which the client applications, such as the Oracle loader, the Hub Server, and the Process Server,
run. NLS_LANG sets the language, territory, and character set that the client applications use.
• Configure
the init.ora parameters. Configure the init.ora parameters for the production environment of
the MDM Hub installation.
• Createan Oracle database instance. Create an Oracle database instance for the MDM Hub Master
Database and the Operational Reference Stores.
• Createtablespaces. You must create the CMX_DATA, CMX_INDX, CMX_TEMP tablespaces for the
Hub Store.
• Ifyou use the DBA user to create the MDM Hub Master Database and the Operational Reference
Stores, grant privileges to the DBA user.
• Add the Oracle TNS name. Add the TNS name entries to the tnsnames.ora file on the Hub Server and
Process Server machines to connect to the Oracle database.
• Testthe database connection. Test the connection to the database from each machine on which you
want to run the Hub Server or the Process Server.
• If you want to create the Hub Store in an Oracle RAC environment, install and configure Oracle RAC.
 Install and configure WebLogic according to the instructions in the WebLogic documentation.
• Ifthe operating system uses Internet Protocol version 6 (IPv6), configure the WebLogic startup script to
use it.
• Configure the WebLogic startup script to force WebLogic and JGroups to use the same bind address.
• Configure the WebLogic startup script to make it J2EE13 compliant.
• Set the maximum JVM heap size in the WebLogic startup script.
• Configure an appropriate value for the WebLogic memory variable.
• Ifyou want to install Informatica platform, configure Java options in the WebLogic startup script to use
the Sun HTTP Handler.
• Set the log4j.xml file configuration path in the WebLogic startup script.
• Configure WebLogic to use an Oracle data source. If you install the Process Server and the Hub Server
on separate machines, create data sources for each Operational Reference Store on the Process
Server machine.
• Create a master data source. If you install the Process Server and the Hub Server or Oracle on
separate machines, create a data source for the Master Database on the Process Server machine.
• Create an Operational Reference Store data source. If you install the Process Server and the Hub
Server or Oracle on separate machines, create a data source for the Operational Reference Store on
the Process Server machine.
• If you want to install the MDM Hub in a WebLogic clustered environment, create a WebLogic cluster.
Step 1. Pre-Installation Tasks 149

• Configure WebLogic for multiple MDM Hub Master Databases. If you want to configure multiple MDM
Hub Master Databases, you have to install an MDM Hub instance for each MDM Hub Master Database.
To install multiple MDM Hub instances on the same machine, deploy each MDM Hub instance on
separate WebLogic domains.
 Install and configure external cleanse engines that you might want to use for cleanse operations.
 Determine the timeline granularity that you want to use. Timeline granularity is the time measurement
that you want to use to define effective periods for versions of records. To be prepared to configure the
timeline granularity when you create or update an Operational Reference Store, determine the timeline
granularity.
 Configure the Informatica platform properties file. If you want to install Informatica platform as part of the
MDM Hub installation, create an Informatica platform properties file.
 Create an installation documentation directory to store copies of installation files, such as the validation
results, environment reports, and log files.
 Create the ActiveVOS database schema. Create the ActiveVOS database schema before you install the
Hub Server. The ActiveVOS database stores data about the state of the processes.
 Create the user for the ActiveVOS Console with the role abAdmin.
Step 2. Create the Hub Store

To create a Hub Store, perform the following tasks:
 Create the MDM Hub Master Database. You must create the MDM Hub Master Database before you
install the Hub Server. The MDM Hub Master Database will store the MDM Hub environment
configuration settings.
 Create an Operational Reference Store. You can create an Operational Reference Store at any time after
you install and configure the database environment.
 Import the metadata into the MDM Hub Master Database. The metadata includes repository tables and
other objects that the MDM Hub requires in the Hub Store.
 Import the metadata into the Operational Reference Store. The metadata includes repository tables and
other objects that the MDM Hub requires in the Hub Store.
Step 3. Install the Hub Server

Use the Hub Server installer to install the Hub Server on a Windows or UNIX machine. If you have a
clustered environment, you can install the Hub Server on multiple cluster nodes.
150 Appendix A: Installation and Configuration Checklist

Step 4. Hub Server Post-Installation Tasks
After you install the Hub Server, perform the following tasks:
 Copy the installation log files to the installation documentation directory that you created. Use the log
files to troubleshoot installation issues.
 Verify the version and build number of the Hub Server.
 Perform the following Hub Server configurations:

• Deploy the Hub Server EAR file on the same machine on which you installed the Hub Server.
• Configure the Hub Server for logging in the log4j.xml file.
• Configure the Hub Server properties in the cmxserver.properties file.
• If
you skipped the post-installation setup script during installation, run the post-installation setup script
manually.
• If the Hub Server deployment fails, manually redeploy the Hub Server.
 If you want to configure multiple Process Servers, manually configure data sources.
 If you want to troubleshoot issues, or the automated queue creation process fails, manually configure
JMS Message queues.
 If you want to change the password for the Operational Reference Store (ORS), change it.
 If you have custom JAR files, repackage the JAR files in the siperian-mrm.ear file after you install the
Hub Server.
 To enable the AnonymousAdminLookupEnabled method of WebLogic for the registration of the ORS,
restart WebLogic.
 To handle caching requirements, configure JBoss Cache.
 If you installed Informatica platform, configure the MDM Hub to log Informatica platform processes.
 Configure the Developer tool to write the workspace metadata to the machine where the user is logged
in.
 Start the Hub Console to verify access to the Hub Server.
 Register Operational Reference Stores that you create by using the Hub Console.
 Configure the ActiveVOS URNs. Configure the URN mappings in the ActiveVOS Console to reflect the
host name and the port number of the ActiveVOS Server.
 Add ActiveVOS Console user and the workflow adapter users to the application server. You must use the
same user names, passwords, and roles in the MDM Hub, ActiveVOS, and the application server.
Step 5. Install the Process Server

Use the Process Server installer to install the Process Server on a Windows or UNIX machine. If you have a
clustered environment, you can install the Process Server on multiple cluster nodes.
Step 4. Hub Server Post-Installation Tasks 151

Step 6. Process Server Post-Installation Tasks
After you install the Hub Server, perform the following tasks:
 Copy the installation log files to the installation documentation directory that you created.
 Verify the version and build number of the Process Server.
 Perform the following Process Server configurations:

• Deploy the Process Server EAR file on the same machine on which you installed the Process Server.
• Configure the Process Server with external cleanse engines.
• Configure the Process Server to delete the temporary files that the cleanse process generates.
• Configure the Process Server for logging in the log4j.xml file.
• Configure the Hub Server properties in the cmxserver.properties file.
• If
you skipped the post-installation setup script during installation, run the post-installation setup script
manually.
• If the Process Server deployment fails, manually redeploy the Process Server.
 Configure the Process Server for multithreading. If the server on which you install the Process Server
has more than one CPU, then you can configure the cleanse operations to be multithreaded to increase
performance. The batch operations are multi-threaded by default, but you can configure the number of
threads to use.
 Configure multiple Process Servers for cleanse and match operations.
 Configure multiple Process Servers for batch processes.
 Configure match population. You must configure the match population to use for the match rules.
 Configure the Process Server for smart search.
Step 7. Install the Resource Kit (Optional)

You can install the samples, applications, and utilities in the Resource Kit. Use the Resource Kit installer to
install the Resource Kit on a Windows or UNIX machine.
To install the Resource Kit, perform the following tasks:
 Set up the MDM Hub sample Operational Reference Store (ORS). The Resource Kit samples and utilities
require the sample ORS.
 Register the MDM Hub sample Operational Reference Store in the Hub Console.
 Run the Resource Kit installer. Use the Resource Kit installer to install the Resource Kit on a Windows or
UNIX machine. If you have a clustered environment, you can install the Hub Server on multiple cluster
nodes.
152 Appendix A: Installation and Configuration Checklist

Index
A Hub Store
tablespaces, creating 21
abTaskClient role uninstalling 143
editing 119
ActiveVOS
URN, setting 121
I
Informatica ActiveVOS
C creating the schema 45

Informatica platform
clustering properties file 32
on WebLogic 25 installation requirements
configuring Oracle X Window Server 19
configure the init.ora parameters 21 installing
disable the Oracle Recycle Bin 20 Hub Server 58, 61
Oracle RAC 23 Process Server 93, 95
configuring WebLogic Resource Kit 131, 134
for Informatica Data Director 30
custom jar files
repackaging 87
J
JBoss
D port conflicts 76
JBoss cache
databases configuring 88
connection testing 23 eviction 88
target database 90 lockAcquisitionTimeout 88
mcast_addr 88
mcast_port 88
E stateRetrieval timeout 88
sync replTimeout 88
environment variables wakeUpInterval 88
DISPLAY 19 JMS message queues
configuring 83
G L
graphical mode
installation requirements 19 log file
debug log file 74, 105
Hub Server log file 74
H installation log file 73, 103

installation prerequisites log file 73, 105
Hub Console post install setup log file 74, 104
starting 90 Process Server log file 104
Hub Server WebLogic Server log files 75, 105
configuration properties 76
deploying on WebLogic cluster 68
installation log files 73
installing 58, 61, 131
M
logging settings 76 Master Database
postinstallsetup script 81 creating 48
silent installation 63, 68, 136 importing metadata 52
silent properties file 64 match population
uninstalling 146, 147 enabling 114
version and build number 75
153
MDM Hub
components 13 S
designing the installation 15 Sample Schema
installation tasks 15 installing 126
introduction 13 registering 129
setting environment variables 19 security realm
system requirements 18 default, editing 117
MDM Hub EAR files silent installation
repackaging 78 of Hub Server 68
message queues silent installer
adding to the module 84 running 100
O T
Operational Reference Store tablespaces
creating 50 creating 21
importing metadata 53 target database
registering 90 selecting 90
timeline
granularity 30
P tns name
adding 23
postinstallsetup script troubleshooting
for Hub Server 81 post-installation process 140
running 81, 108
postInstallSetup script
for Process Server 108
Process Server U
configuration properties 107 uninstalling
configuring 106 Hub Server 146, 147
deploying on WebLogic cluster 101 Hub Store 143
installation log files 103 Process Server 146
installing 93, 95 URN
logging settings 107 setting ActiveVOS 121
multithreading, configuring 111
postInstallSetup script 108
redeploying 108
silent installation 97 W
silent properties file 97 WebLogic
threads for batch processing 111 clustering 25
threads for cleanse operations 111 configuring 24
uninstalling 146 WebLogic cluster
version and build number 106 deploying Hub Server 68
Process Server EAR file deploying Process Server 101
repackaging 109 WebLogic Server
settings 77
workflow engines
R adding 124
Resource Kit
installing 131, 134
silent properties file 136 X
uninstalling 146 X Window Server
roles installation requirements 19
abTaskClient, editing 119
ActiveVOS, adding 117
154 Index

Installation Guide For Weblogic: Informatica MDM Multidomain Edition For Oracle (Version 10.1.0)

Uploaded by

Copyright:

Available Formats

You might also like

Installation Guide For Weblogic: Informatica MDM Multidomain Edition For Oracle (Version 10.1.0)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installation Guide For Weblogic: Informatica MDM Multidomain Edition For Oracle (Version 10.1.0)

Uploaded by

Copyright:

Available Formats

Informatica MDM Multidomain Edition for

Oracle (Version 10.1.0)

Installation Guide for

Copyright (c) 1993-2015 Informatica LLC. All rights reserved.

See patents at https://www.informatica.com/legal/patents.html.

Part Number: MDM-OIG-10100-0002

Chapter 1: Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 2: Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 3: ActiveVOS Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 4: Hub Store Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 5: Hub Store Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Chapter 6: Hub Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 7: Hub Server Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Chapter 8: Process Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Chapter 9: Process Server Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Chapter 11: ActiveVOS Post-Installation Tasks for the Business Entity

Chapter 12: Resource Kit Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Chapter 13: Troubleshooting the MDM Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Chapter 14: Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Appendix A: Installation and Configuration Checklist. . . . . . . . . . . . . . . . . . . . . . . . 148

Informatica My Support Portal

As a member, you can:

• Access all of your Informatica resources in one place.

Informatica Product Availability Matrixes

Informatica How-To Library

Informatica Knowledge Base

Informatica Support YouTube Channel

Informatica Global Customer Support

• MDM Multidomain Edition Installation, 13

MDM Multidomain Edition Installation

The MDM Hub installation consists of the following components:

Informatica Data Director

Dynamic Data Masking

14 Chapter 1: Installation Overview

To install the MDM Hub, complete the following tasks:

Designing the MDM Hub Installation

All components on a single host

Components distributed on multiple hosts

16 Chapter 1: Installation Overview

• Read the Release Notes, 17

Read the Release Notes

Extract the Installer Files

Verify License Key

Verify the Minimum System Requirements

Development environment: 2 GB minimum, 4 GB recommended

18 Chapter 2: Pre-Installation Tasks

Set the Operating System Locale

Set Up the X Window Server

C setenv DISPLAY <host name>:0

Bash/Korn export DISPLAY=<host name>:0

Bourne DISPLAY=<host name>:0

Set Environment Variables 19

Install and Configure Oracle

• Disable the Oracle Recycle Bin

Disable the Oracle Recycle Bin

For more information, see the Oracle documentation.

Set the NLS_LANG Environment Variable

Specify the NLS_LANG parameter in the following format: