Informatica MDM Multidomain Edition for

Oracle (Version 10.0.0)

Installation Guide for JBoss

Informatica MDM Multidomain Edition for Oracle Installation Guide for JBoss

Version 10.0.0
November 2014

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

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

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

The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us
in writing.
Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange,
PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica
On Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and
Informatica Master Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world.
All other company and product names may be trade names or trademarks of their respective owners.

Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights
reserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All rights
reserved.Copyright © Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright © Meta
Integration Technology, Inc. All rights reserved. Copyright © Intalio. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © Adobe Systems
Incorporated. All rights reserved. Copyright © DataArt, Inc. All rights reserved. Copyright © ComponentSource. All rights reserved. Copyright © Microsoft Corporation. All
rights reserved. Copyright © Rogue Wave Software, Inc. All rights reserved. Copyright © Teradata Corporation. All rights reserved. Copyright © Yahoo! Inc. All rights
reserved. Copyright © Glyph & Cog, LLC. All rights reserved. Copyright © Thinkmap, Inc. All rights reserved. Copyright © Clearpace Software Limited. All rights
reserved. Copyright © Information Builders, Inc. All rights reserved. Copyright © OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved.
Copyright Cleo Communications, Inc. All rights reserved. Copyright © International Organization for Standardization 1986. All rights reserved. Copyright © ej-
technologies GmbH. All rights reserved. Copyright © Jaspersoft Corporation. All rights reserved. Copyright © is International Business Machines Corporation. All rights
reserved. Copyright © yWorks GmbH. All rights reserved. Copyright © Lucent Technologies. 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.

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, <[email protected]>. 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; and https://code.google.com/p/lz4/.

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.

This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775;
6,640,226; 6,789,096; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110; 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422;
7,676,516; 7,720,842; 7,721,270; 7,774,791; 8,065,266; 8,150,803; 8,166,048; 8,166,071; 8,200,622; 8,224,873; 8,271,477; 8,327,419; 8,386,435; 8,392,460;
8,453,159; 8,458,230; and RE44,478, International Patents and other Patents Pending.

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

NOTICES

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

1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT
INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT
LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

Part Number: MDM-JIG-100000-0002

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica My Support Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica Product Availability Matrixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Informatica Support YouTube Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Informatica Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Informatica Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 1: Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

MDM Multidomain Edition Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Designing the MDM Hub Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

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

Read the Release Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Extract the Installer Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Verify License Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Verify the Minimum System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Install Java Development Kit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Set Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Set the Operating System Locale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Set Up the X Window Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Install and Configure Oracle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Disable the Oracle Recycle Bin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Set the NLS_LANG Environment Variable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Configure the init.ora Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Create an Oracle Database Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Create Tablespaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Grant Privileges to DBA User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Add the Oracle TNS Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Test the Database Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Install and Configure Oracle RAC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Use Oracle Service Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Use Oracle RAC Load-Balanced Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Configure the tnsnames.ora File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4 Table of Contents
Install and Configure JBoss. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Disable HornetQ Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Disabling Remoting-Connector Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Configure JBoss for Informatica Data Director. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Create a JBoss Cluster and Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Configure JBoss for Multiple MDM Hub Master Databases. . . . . . . . . . . . . . . . . . . . . . . . 25
Starting JBoss On UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Start JBoss On Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Install and Configure Cleanse Engines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Choose a Timeline Granularity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Configure the Informatica Platform Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Sample Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Create an Installation Documentation Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Create an Informatica ActiveVOS Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 3: Hub Store Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Create the MDM Hub Master Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Create an Operational Reference Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Import the Metadata into the MDM Hub Master Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Import the Metadata into the Operational Reference Store. . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 4: Hub Store Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Verify Access to Oracle Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 5: Hub Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Installing the Hub Server in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Installing the Hub Server in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Installing the Hub Server in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Configuring the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Sample Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Installing and Deploying the Hub Server on Nodes in the Cluster. . . . . . . . . . . . . . . . . . . . . . . 60

Chapter 6: Hub Server Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Copy the Installation Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Installation Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Installation Prerequisites Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Debug Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Post-Installation Setup Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Hub Server Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
JBoss Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Verify the Version and Build Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Configure the Hub Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Table of Contents 5
 Deploying the Hub Server EAR File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Configuring the Logging Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Setting the Configuration Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Changing the JBoss Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Configuring JBoss for Multiple Process Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Running the Post Install Script Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Manually Redeploying the Hub Server Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Manually Creating Data Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Manually Configuring JMS Message Queues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Step 1. Create a Connection Factory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Step 2. Create a JMS Message Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Step 3. Verify the JMS Message Queue Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Step 4. Add a Message Queue Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Step 5. Add a Message Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Changing the Operational Reference Store User Password. . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Repackaging Custom JAR Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Configure JBoss Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Configuring an EJB Client for the Hub Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Configure Logging for Informatica Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Starting the Hub Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Registering an Operational Reference Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Configuring JBoss Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Adding MDM-ActiveVOS Users to the Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
ActiveVOS Web Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Configuring the ActiveVOS URNs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Chapter 7: Process Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Installing the Process Server in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Installing the Process Server in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Installing the Process Server in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Configuring the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Sample Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Installing and Deploying the Process Server on Nodes in the Cluster. . . . . . . . . . . . . . . . . . . . 89

Chapter 8: Process Server Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Copy the Installation Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Installation Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Post-Installation Setup Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Process Server Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Debug Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Installation Prerequisites Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
JBoss Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

6 Table of Contents
Verify the Version and Build Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Configure the Process Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Deploying the Process Server EAR File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Configuring the Process Server with Cleanse Engines. . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Configuring the Process Server to Delete Temporary Files. . . . . . . . . . . . . . . . . . . . . . . . 94
Configuring the Logging Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Setting the Configuration Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Running the PostInstallSetup Script Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Manually Redeploying the Process Server EAR File. . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Configure Process Server for Multithreading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Configuring the Process Server for Multithreading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Configuring Multiple Process Servers for Cleanse and Match Operations. . . . . . . . . . . . . . . . . . 97
Configuring Multiple Process Servers for Batch Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Configure Match Population. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Enabling Match Population. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Chapter 9: Resource Kit Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Setting Up the MDM Hub Sample Operational Reference Store. . . . . . . . . . . . . . . . . . . . . . . 101
Registering the Informatica MDM Hub Sample Operational Reference Store. . . . . . . . . . . . . . . 104
Installing the Resource Kit in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Installing the Resource Kit in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Installing the Resource Kit in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Configuring the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Sample Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Installing and Deploying the Resource Kit into a JBoss Cluster. . . . . . . . . . . . . . . . . . . . . . . . 114

Chapter 10: Troubleshooting the MDM Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Troubleshooting the Installation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Chapter 11: Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Uninstallation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Uninstalling the Hub Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Uninstalling the Process Server in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Uninstalling the Process Server in Graphical Mode On UNIX. . . . . . . . . . . . . . . . . . . . . . 121
Uninstalling the Process Server in Graphical Mode On Windows. . . . . . . . . . . . . . . . . . . 121
Uninstalling the Hub Server in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Uninstalling the Hub Server in Graphical Mode on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . 122
Uninstalling the Hub Server in Graphical Mode on Windows. . . . . . . . . . . . . . . . . . . . . . 122
Uninstalling the Resource Kit in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Uninstalling the Resource Kit in Graphical Mode on UNIX. . . . . . . . . . . . . . . . . . . . . . . . 122
Uninstalling the Resource Kit in Graphical Mode on Windows. . . . . . . . . . . . . . . . . . . . . 123
Uninstalling the Process Server in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Table of Contents 7
 Uninstalling the Hub Server in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Uninstalling the Resource Kit in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Manually Undeploying the Process Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Manually Undeploying the Hub Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

8 Table of Contents
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, you can access the Informatica My Support Portal at
http://mysupport.informatica.com.

The site contains product information, user group information, newsletters, access to the Informatica
customer support case management system (ATLAS), the Informatica How-To Library, the Informatica
Knowledge Base, Informatica Product Documentation, and access to the Informatica user community.

Informatica Documentation
The Informatica Documentation team takes 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 [email protected]. We will use your feedback to improve our
documentation. Let us know if we can contact you regarding your comments.

The Documentation team updates documentation as needed. To get the latest documentation for your
product, navigate to Product Documentation from http://mysupport.informatica.com.

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

Informatica Web Site

You can access the Informatica corporate web site at http://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.

9
 Informatica How-To Library
As an Informatica customer, you can access the Informatica How-To Library at
http://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
http://mysupport.informatica.com. Use the Knowledge Base to search for documented solutions to known
technical issues about Informatica products. You can also find answers to frequently asked questions,
technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge
Base, contact the Informatica Knowledge Base team through email at [email protected].

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 [email protected] 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 http://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 [email protected].

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.

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

10 Preface
CHAPTER 1

Installation Overview
This chapter includes the following topics:

• MDM Multidomain Edition Installation, 11

• Installation Tasks, 12
• Designing the MDM Hub Installation, 13

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

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

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. Install the MDM Hub components. Use the setup script provided with the MDM Hub distribution to create
the Hub Store. Use the MDM Hub installer to install the Hub Server and the Process Server.
3. Perform the post-installation configuration tasks. Test the database connections. Configure the Hub
Server and the Process Server to ensure that you can use the MDM Hub features.

12 Chapter 1: Installation Overview

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.

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.

Designing the MDM Hub Installation 13

 The following figure shows a distributed installation of the MDM Hub components:

14 Chapter 1: Installation Overview

CHAPTER 2

Pre-Installation Tasks
This chapter includes the following topics:

• Read the Release Notes, 15

• Extract the Installer Files, 15
• Verify License Key, 16
• Verify the Minimum System Requirements, 16
• Install Java Development Kit, 17
• Set Environment Variables, 17
• Set the Operating System Locale, 17
• Set Up the X Window Server, 17
• Install and Configure Oracle, 18
• Install and Configure Oracle RAC, 21
• Install and Configure JBoss, 23
• Install and Configure Cleanse Engines, 26
• Choose a Timeline Granularity, 26
• Configure the Informatica Platform Properties File, 28
• Create an Installation Documentation Directory, 40
• Create an Informatica ActiveVOS Schema, 40

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.

Extract the installer files to a directory on your machine. Verify that the utility that you use for extraction also
extracts empty folders.

15
 Download the MDM Hub compressed installation files from the Informatica Electronic Software Download site
to a directory on your machine. You can then extract the installer files.

If you intend to install the licensed version of ActiveVOS Server, download and extract the ActiveVOS Server
installer.

If you intend to install Informatica platform, download the Informatica platform compressed installation files to
a directory on your machine.

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

16 Chapter 2: Pre-Installation Tasks

Install Java Development Kit
Complete the Java Development Kit (JDK) requirements for the following operating systems:

• On AIX, install a supported version of JDK for the MDM Hub installation.
• On HP-UX, install separate, supported versions of JDKs for the MDM Hub and the Informatica platform
installation.

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

When you run the installer in graphical mode, you must use a graphics display server. On UNIX, the graphics
display server is typically an X Window server. If you do not have the X Window server 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 server to another
UNIX machine.

Install Java Development Kit 17

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

Shell Command Example

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

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

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

export display export display

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

If the X Window server does not support the font that the installer uses, the installer might display incorrect
labels on the buttons.

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.

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

18 Chapter 2: Pre-Installation Tasks

 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.

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.

Install and Configure Oracle 19

 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.

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.

20 Chapter 2: Pre-Installation Tasks

 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.

Install and Configure Oracle RAC 21

 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.

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))
(ADDRESS= (PROTOCOL = TCP)(HOST = server2-vip)(PORT = 1521))
(ADDRESS= (PROTOCOL = TCP)(HOST = server3-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.

22 Chapter 2: Pre-Installation Tasks

Install and Configure JBoss
Install and configure JBoss according to the instructions in the JBoss documentation. Ensure that you install
the standalone configuration. Use the full profile of the standalone configuration. You can configure the full
profile in the standalone-full.xml file.

Note: Install the application server in the same time zone as the database server.

Ensure that you perform the following configurations:

• Add appropriate attributes to the JAVA_OPTS property in the following file:

On UNIX. <JBoss Installation Directory>/bin/standalone.conf
On Windows. <JBoss Installation Directory>\bin\standalone.conf.bat
The following table describes the attributes that you can add to the JAVA_OPTS property:

Attributes Description

-Dorg.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE=16384 The maximum size of the HTTP

headers, in bytes. The smart
search requests might fail if the
header size is low.

-Djava.net.preferIPv4Stack=true Set to true if your operating

system uses Internet Protocol
version 6 (IPv6).

For example:
JAVA_OPTS="-Dprogram.name=$PROGNAME -Djava.net.preferIPv4Stack=true $JAVA_OPTS"
• Add the following JVM option to the JBoss startup script to force JBoss and JGroups to use the same bind
address:
-Djgroups.bind_addr=<bind_addr>
In the sample, <bind_addr> specifies the interface on which to receive and send messages.
• Set the maximum JVM heap size (-Xmx) to 4 GB or higher in the JBoss startup script. Change the
following settings:
set JAVA_OPTS=%JAVA_OPTS% -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.
• Increase the transaction timeout to 3600 in the following file:
On UNIX. <JBoss Installation Directory>/standalone/configuration/standalone-full.xml
On Windows. <JBoss Installation Directory>\standalone\configuration\standalone-full.xml

The default is 300.

The following sample shows the setting:
<profile>
.
.
.
<subsystem xmlns="urn:jboss:domain:transactions:1.3">
<core-environment>
<process-id>
<uuid/>

Install and Configure JBoss 23

 </process-id>
</core-environment>
<recovery-environment socket-binding="txn-recovery-environment" status-socket-
binding="txn-status-manager"/>
<coordinator-environment default-timeout="3600"/>
</subsystem>
.
.
.
</profile>
• Add the following option to JAVA_OPTIONS in the JBoss startup script to set the log4j.xml file
configuration path:
-DFrameworksLogConfigurationPath="<Path to the log4j.xml file>"

Disable HornetQ Security

If hornetQ security is enabled for the JBoss server, disable it.

1. Open the following file in a text editor:

On UNIX.
<Jboss_install_dir>/standalone/configuration/standalone-full.xml
On Windows.
<Jboss_install_dir>\standalone\configuration\standalone-full.xml
2. Set hornetQ security to false as shown in the following example:
<hornetq-server>
<security-enabled>false</security-enabled>
...
</hornetq-server>
3. Save and close the file.

Disabling Remoting-Connector Security

You can configure remoting-connector to use the JBoss application server in a secured or unsecured mode.
In the unsecured mode, you can log into the Hub Console from a remote machine.

To use JBoss in an unsecured mode, disable the remoting-connector security.

1. Open the following file in a text editor:

On UNIX.
<Jboss_install_dir>/standalone/configuration/standalone-full.xml
On Windows.
<Jboss_install_dir>\standalone\configuration\standalone-full.xml
2. Remove the security-realm attribute from the following code:
<subsystem xmlns="urn:jboss:domain:remoting:1.1">
<connector name="remoting-connector" socket-binding="remoting" security-
realm="ApplicationRealm"/>
</subsystem>

Configure JBoss for Informatica Data Director

If you use a JBoss environment running on Java 1.7, and need to use Informatica Data Director, configure
the standalone-full.xml file for asynchronous handling of loggers.

1. Open the standalone-full.xml file for editing. The file is in the following directory:

24 Chapter 2: Pre-Installation Tasks

 • On UNIX. <JBoss installation directory>/jboss-eap-6.1.1/standalone/configuration
• On Windows. <JBoss installation directory>\jboss-eap-6.1.1\standalone\configuration
2. Under <subsystem xmlns="urn:jboss:domain:logging:1.2"> in the standalone-full.xml file, add the
following XML code to configure asynchronous handling for the logger:
<async-handler name="ASYNC">
<level name="INFO"/>
<queue-length value="1024"/>
<overflow-action value="BLOCK"/>
<subhandlers>
<handler name="FILE"/>
<handler name="CONSOLE"/>
</subhandlers>
</async-handler>
3. Under <subsystem xmlns="urn:jboss:domain:logging:1.2"> in the standalone-full.xml file, add the
following XML code to configure asynchronous handling for the root logger:
<root-logger>
<level name="INFO"/>
<handlers>
<handler name="ASYNC"/>
</handlers>
</root-logger>
4. Restart the application server.

Create a JBoss Cluster and Nodes

You can install the MDM Hub in a JBoss clustered environment. A JBoss cluster consists of one or more
cluster nodes on one or more machines. You must ensure that the directory structure of the JBoss installation
is the same on all the cluster nodes.

1. Install and configure JBoss on all machines on which you want cluster nodes according to the
instructions in the JBoss documentation.
Ensure that you install the standalone configuration.
2. Run the following command to start JBoss on each machine on which cluster nodes exist:
On UNIX. <JBoss_install_dir>/bin/standalone.sh -c standalone-full.xml -b 0.0.0.0 -u
<multicast address> -Djgroups.bind_addr=<bind address> -Djboss.node.name=<node name> -
Djboss.server.base.dir=../<node path>
On Windows. <JBoss_install_dir>\bin\standalone.bat -c standalone-full.xml -b 0.0.0.0 -u
<multicast address> -Djgroups.bind_addr=<bind address> -Djboss.node.name=<node name> -
Djboss.server.base.dir=../<node path>

Configure JBoss 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. To install multiple MDM Hub instances on the same machine, deploy
each MDM Hub instance on a separate JBoss instance and run each JBoss instance on a different port.

To configure each JBoss instance to run on a different port, perform the following tasks:

• Change the port-offset attribute of the socket-binding-group element in the following file:
On UNIX. <JBoss_install_dir>/standalone/configuration/standalone-full.xml
On Windows. <JBoss_install_dir>\standalone\configuration\standalone-full.xml

Install and Configure JBoss 25

 The following sample shows the setting:
<socket-binding-group name="standard-sockets" default-interface="public" port-
offset="${jboss.socket.binding.port-offset:1}">
Set the port-offset attribute of each JBoss instance to a different value.
• Before you start a JBoss instance, set the JBoss home for the JBoss instance at the command prompt.
• Start the second and any subsequent JBoss instances by running the following command:
standalone.bat -c standalone-full.xml -b 0.0.0.0 -Djboss.service.binding.set=ports-01

Starting JBoss On UNIX

Start the JBoss application server before you install the Hub Server and the Process Server.

1. Go to the following directory:

JBoss_install_dir/bin
2. Run the following command:
standalone.sh -c standalone-full.xml -b 0.0.0.0
JBoss starts and the IP address is bound with the machine name in the hosts file in the following
directory: \\WINDOWS\system32\drivers\etc\hosts

Start JBoss On Windows

Start the JBoss application server before you install the Hub Server and the Process Server.

1. Go to the following directory:

JBoss_install_dir\bin
2. Run the following command:
standalone.bat -c standalone-full.xml -b 0.0.0.0
JBoss starts and the IP address is bound with the machine name in the hosts file in the following
directory: \\WINDOWS\system32\drivers\etc\hosts

Install and Configure Cleanse Engines

Install and configure a cleanse engine, such as Address Doctor, to use with the Process Server.

Verify that the Process Server operates properly. For instructions on how to configure the MDM Hub to
integrate with the cleanse engine, see the Informatica MDM Multidomain Edition Cleanse Adapter Guide.

Choose a Timeline Granularity

Timeline graularity is the coarseness of effective periods, which is the period for which a version of a record
is valid. You can choose a timeline granularity that meets your business requirements. You can choose a
coarse timeline granularity, such as year, or the finest timeline granularity, which is seconds.

26 Chapter 2: Pre-Installation Tasks

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.

Note: 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 unit, the effective start date and the effective 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.

Choose a Timeline Granularity 27

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

28 Chapter 2: Pre-Installation Tasks

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 29

 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.

30 Chapter 2: Pre-Installation Tasks

 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

Required if DB_CUSTOM_STRING_SELECTION=0.

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

Required if DB_CUSTOM_STRING_SELECTION=1.

Configure the Informatica Platform Properties File 31

 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

Required if JOIN_DOMAIN=1.

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

Required if JOIN_DOMAIN=1.

Port number of the gateway node of the domain that you want to join.

32 Chapter 2: Pre-Installation Tasks

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

You can set this parameter if ADVANCE_PORT_CONFIG=1.

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

You can set this parameter if ADVANCE_PORT_CONFIG=1.

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

You can set this parameter if ADVANCE_PORT_CONFIG=1.

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

Configure the Informatica Platform Properties File 33

 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 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=

34 Chapter 2: Pre-Installation Tasks

# 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
Informatica Administrator.

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

Configure the Informatica Platform Properties File 35

 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=

36 Chapter 2: Pre-Installation Tasks

 # 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 if DB_CUSTOM_STRING_SELECTION=0.
# 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.

# Set the property if DB_CUSTOM_STRING_SELECTION=1.

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.

Configure the Informatica Platform Properties File 37

 # 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
Informatica Administrator.
# 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.
# Set the property if JOIN_DOMAIN=1.

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.
# Set the property if JOIN_DOMAIN=1.

JOIN_HOST_NAME=DomainHostName

# The JOIN_DOMAIN_PORT property represents the port number of the gateway node of the
domain you want to join.
# Set the property if JOIN_DOMAIN=1.

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.

38 Chapter 2: Pre-Installation Tasks

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.
# Set the property if ADVANCE_PORT_CONFIG=1.

MAX_PORT=

# The TOMCAT_PORT property represents the port number used by the Service Manager on
the node. Default is 6006.
# Set the property if ADVANCE_PORT_CONFIG=1.
# 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.
# Set the property if ADVANCE_PORT_CONFIG=1.

SERVER_PORT=

# The AC_SHUTDWN_PORT property represents the port number that controls the server
shutdown for Informatica Administrator. Default is 6009.
# Set the property if ADVANCE_PORT_CONFIG=1.
# 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

Configure the Informatica Platform Properties File 39

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

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.
Note: The prompt displays default text in brackets. Press Enter to use the default value and go to the
next prompt.
Enter database type. (ORACLE, MSSQL, DB2)
Database type, which must be the same as the one selected for the MDM Hub Master Database and
the Operational Reference Stores. 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.

40 Chapter 2: Pre-Installation Tasks

 Enter the DB host name. [localhost]
Name of the machine that hosts the database.

Enter the DB port number. [1521]

Port number that the database listener uses.

Enter the DB service name. [orcl]

Name of the Oracle service. This prompt appears if the selected Oracle connection type is
SERVICE.

Enter Oracle Net connect identifier (TNS Name). [orcl]

Oracle TNS name.

Enter database SID. [orcl]

Name of the Oracle System ID. This prompt appears if the selected Oracle connection type is SID.

Enter the DBA user name. [SYS]

User name of the administrative user.

Enter the DBA password.

Password of the administrative user.

Enter ActiveVOS user name. [AVOS]

User name of the ActiveVOS Server administrative user.

Enter ActiveVOS user password.

Password of the administrative user.

Enter ActiveVOS user tablespace. [CMX-DATA]

The name of the tablespace that contains the records involved in MDM workflows.

Enter ActiveVOS user temp tablespace. [TEMP]

The name of the temporary tablespace.
5. After you create the schema, review sip_ant.log in the following directory:
On UNIX. <distribution directory>/database/bin
On Windows. <distribution directory>\database\bin
The sip_ant.log file logs any errors that might occur when you run the sip_ant script to create the
ActiveVOS database schema.

Create an Informatica ActiveVOS Schema 41

CHAPTER 3

Hub Store Installation

This chapter includes the following topics:

• Create the MDM Hub Master Database, 42

• Create an Operational Reference Store, 44
• Import the Metadata into the MDM Hub Master Database, 45
• Import the Metadata into the Operational Reference Store, 47

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.

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_system
On Windows. sip_ant.bat create_system
4. Answer the prompts that appear.
Note: The prompt displays default text in brackets. Press Enter to use the default value and go to the
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: Default is 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.

42
 Default is SERVICE.

Enter the MDM Hub Master Database user name. [cmx_system]

Name of the MDM Hub Master Database user. Default is cmx_system.

Enter the database host name. [localhost]

Name of the machine that hosts the database. Default is localhost.

Enter the database port number. [1521]

Port number that the database listener uses. Default is 1521.

Enter the database service name. [orcl]

Name of the Oracle service. This prompt appears if the selected Oracle connection type is
SERVICE.

Enter Oracle Net connect identifier. (TNS Name) [orcl]

Oracle TNS name. Default is orcl.

Master Database Connect URL: "jdbc:oracle:thin:@//<host_name>:<port>/<service_name>".

Connect URL for the Oracle connection type SERVICE. You cannot change the connect URL.

Enter database SID. [orcl]

Name of the Oracle System ID. This prompt appears if the selected Oracle connection type is SID.

Enter the Master Database user password

Password to access the MDM Hub Master Database.

Enter the MDM Hub Master Database schema name. [cmx_system]

Name of the MDM Hub Master Database schema. Default is cmx_system.

Enter locale name from the list: de, en_US, fr, ja, ko, zh_CN. [en_US]
Operating system locale.

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.
5. After you create the MDM Hub Master Database, review sip_ant.log in the following directory:
On UNIX. <distribution directory>/database/bin
On Windows. <distribution directory>\database\bin
The sip_ant.log file logs any errors that might occur when you run the sip_ant script to create the
MDM Hub Master Database.

Create the MDM Hub Master Database 43

Create an Operational Reference Store
After you create the MDM Hub Master Database, you must create an Operational Reference Store. The
default name of the Operational Reference Store is CMX_ORS.

Note: If you change the folder names in the distribution directory, metadata import fails.

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_ors
On Windows. sip_ant.bat create_ors
4. Answer the prompts that appear.
Note: The prompt displays default text in brackets. Press Enter to use the default value and go to the
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: Default is 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 Oracle Net connect identifier (TNS Name) [orcl]

Oracle TNS name. Default is orcl.

Master Database Connect URL: "jdbc:oracle:thin:@//<host_name>:<port>/<service_name>". Do you want to change

the connect URL? (y/n) [n]
Connect URL for the Oracle connection type SERVICE. You can type y to change the default
connect URL. Default is n.

Enter database SID. [orcl]

Name of the Oracle System ID. This prompt appears if the selected Oracle connection type is SID.

44 Chapter 3: Hub Store Installation

 Enter the Operational Reference Store database user name. [cmx_ors]
Name of the Operational Reference Store database user. Default is cmx_ors.

Enter the Operational Reference Store database user password.

Password of the Operational Reference Store database user.

Enter 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.
5. After you create the Operational Reference Store, review sip_ant.log in the following directory:
On UNIX. <distribution directory>/database/bin
On Windows. <distribution directory>\database\bin
The sip_ant.log file logs any errors that might occur when you run the sip_ant script to create the
Operational Reference Store.

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.

Note: If you change the folder names in the distribution directory, metadata import fails.

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 import_system
On Windows. sip_ant.bat import_system

Import the Metadata into the MDM Hub Master Database 45

 4. Answer the prompts that appear.
Note: The prompt displays default text in brackets. Press Enter to use the default value and go to the
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 database host name. [localhost]

Name of the machine that hosts the database. Default is localhost.

Enter the 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. Default is orcl.

Master Database Connect URL: "jdbc:oracle:thin:@//<host_name>:<port>/<service_name>". Do you want to change

the connect URL? (y/n) [n]
Connect URL for the Oracle connection type SERVICE. You can type y to change the default
connect URL. Default is n.

Enter the database SID.

Name of the Oracle System ID. This prompt appears if the selected Oracle connection type is SID.

Enter the MDM Hub Master Database user password.

Password to access the MDM Hub Master Database.

Enter a locale name from the list: de, en_US, fr, ja, ko, zh_CN. [en_US]
Operating system locale. Default is en_US.
5. After you import the initial metadata, review the seed.log file in the following directory for errors:
On UNIX. <distribution directory>/database/bin/oracle
On Windows. <distribution directory>\database\bin\oracle
6. Review sip_ant.log in the following directory:
On UNIX. <distribution directory>/database/bin
On Windows. <distribution directory>\database\bin
The sip_ant.log file logs any errors that might occur when you run the sip_ant script to import
metadata into the MDM Hub Master Database.

46 Chapter 3: Hub Store Installation

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 theHub
Store.

Note: If you change the folder names in the distribution directory, metadata import fails.

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 import_ors
On Windows. sip_ant.bat import_ors
4. Answer the prompts that appear.
Note: The prompt displays default text in brackets. Press Enter to use the default value and go to the
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.

Name of the Oracle service. This prompt appears if the selected Oracle connection type is
SERVICE.

Enter Oracle Net connect identifier (TNS Name). [orcl]

TNS name that you use to connect to the Oracle database. Default is orcl.

Operational Reference Store Database Connect URL: "jdbc:oracle:thin:@//<host_name>:<port>/<service_name>". Do

you want to change the connect URL? (y/n) [n]
Connect URL for the Oracle connection type SERVICE. You can type y to change the default
connect URL. Default is n.

Enter the database SID.

Name of the Oracle System ID. This prompt appears if the selected Oracle connection type is SID.

Import the Metadata into the Operational Reference Store 47

 Enter the Operational Reference Store database user name. [cmx_ors]
Name of the Operational Reference Store database. Default is cmx_ors.

Enter the Operational Reference Store database user password.

Password to access the Operational Reference Store.

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 integer code of Operational Reference Store Timeline Granularity: Year 5, Month 4, Day 3, Hour 2, Minute 1,
Second 0. [3]
Timeline displays data change events of business entities and their relationships. Timeline is
enabled by default for relationship base objects. Timeline granularity is the timeline unit that you use
to specify effective periods of data in the MDM Hub implementation. Choose a timeline granularity
that meets your business requirements. Default is 3.
Note: The timeline granularity that you configure cannot 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 seed.log file in the following directory for errors:
On UNIX. <distribution directory>/database/bin/oracle
On Windows. <distribution directory>\database\bin\oracle
6. Review sip_ant.log in the following directory:
On UNIX. <distribution directory>/database/bin
On Windows. <distribution directory>\database\bin
The sip_ant.log file logs any errors that might occur when you run the sip_ant script to import
metadata into the Operational Reference Store.

48 Chapter 3: Hub Store Installation

CHAPTER 4

Hub Store Post-Installation Tasks

This chapter includes the following topic:

• Verify Access to Oracle Components, 49

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

49
 • 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

50 Chapter 4: Hub Store Post-Installation Tasks

CHAPTER 5

Hub Server Installation

This chapter includes the following topics:

• Installing the Hub Server in Graphical Mode, 51

• Installing the Hub Server in Console Mode, 54
• Installing the Hub Server in Silent Mode, 56
• Installing and Deploying the Hub Server on Nodes in the Cluster, 60

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
3. Run the following command:
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.

51
 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.
On UNIX, the Choose Link Folder window appears.
On Windows, the Choose Shortcut Folder window appears.
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 JBoss, and then click Next.
The JBoss Application Server Home window appears.
12. Configure the following JBoss settings:
a. Specify the application server installation directory, and then click Next.
The JBoss Application Server Configuration Name window appears.
b. Specify the Configuration Name, and then click Next.
The default value is standalone.
The JBoss Application Server Port window appears.
c. Specify the remote port.
Note: The JBoss port can conflict with the default database server port. If ports conflict, change one
of the ports to resolve the conflict. For more information on changing ports, see the JBoss
documentation.
13. Click Next.
The Database Selection window appears.
14. Select Oracle 11g R2, 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:
The following table describes the configuration parameter fields:

Field Name Description

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.

52 Chapter 5: Hub Server Installation

 Field Name Description

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.
The Install ActiveVOS window appears.
20. If you want to install the bundled, licensed version of Informatica ActiveVOS, select Yes and perform the
following substeps. Otherwise, select No. 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. 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.
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 step 21, click Choose and browse to the following Informatica platform file locations:
• Installation response file
• Installation archive file
23. 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.
The Deploy window appears.
24. Click Next.
The Pre-Installation Summary window appears.
25. After the Pre-Installation Summary window displays the options you want, click Install to start the
installation process.

Installing the Hub Server in Graphical Mode 53

 When the installation completes, the Install Complete window appears.
26. 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.

1. Start the application server.

2. Navigate to the following directory in the MDM Hub distribution:
On UNIX. <distribution directory>/<operating system name>/mrmserver
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.
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 JBoss settings.
a. Specify the application server installation directory, and press Enter.
The JBoss application server configuration name information appears.
b. Specify the configuration name. The default value is standalone.
c. Press Enter.

54 Chapter 5: Hub Server Installation

 d. Specify the remote port.
Note: If the JBoss port conflicts with the default database port, then change one of the ports to
resolve the conflict.
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.
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.
The summary of the installation choices appears.
25. Choose whether you want to run the postInstallSetup script as part of the installation, or run it
manually later.
26. 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.
27. Press Enter to exit the installer.

Installing the Hub Server in Console Mode 55

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.

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.

56 Chapter 5: Hub Server Installation

Property Name Description

SIP.AS.CHOICE Name of the application server. Specify JBoss.

SIP.AS.HOME The path to the JBoss installation directory.

JBOSS.AS.PORT_1 The JBoss remote port number.

JBOSS.AS.PORT_2 The JBoss native port number.

SIP.JBOSS.CONFIGURATION_NAME The JBoss configuration name. The default value is

standalone.

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.

Installing the Hub Server in Silent Mode 57

 Property Name Description

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]

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.

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

58 Chapter 5: Hub Server Installation

 SIP.LICENSE.PATH=C\:\\
SIP.LICENSE.FILENAME=siperian.license

## Properties for JBoss application server

SIP.AS.CHOICE="JBoss"
SIP.AS.HOME=C\:\\jboss-eap-6.1.1
## JBoss RMI port
JBOSS.AS.PORT_1=4447
## JBoss management native port
JBOSS.AS.PORT_2=9999
SIP.JBOSS.CONFIGURATION_NAME=standalone
## 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.exe for Windows or
ActiveVOS_Server_unix_9.2.4.sh for Linux/UNIX)
AVOS_INSTALLER_PATH=/export/home/mdmqa/software/builds/ActiveVOS/9.2.4/GA/
ActiveVOS_Server_unix_9.2.4.sh
## ActiveVOS server install directory
AVOS_INSTALL_DIR=/export/home/mdmqa/infamdmsl/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 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

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.

Installing the Hub Server in Silent Mode 59

 3. Run the following command:
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 and Deploying the Hub Server on Nodes in

the Cluster
If you have a clustered environment, install the Hub Server on each node of the cluster where you need to
deploy the Hub Server application. You must ensure that the directory structure of the Hub Server installation
is the same on all the cluster nodes.

If the cluster has two nodes that run on host1 and host2, using RMI ports 4447 and 4448, the properties in
the cmxserver.properties file can have the following values:

• cmx.appserver.hostname= host1.<domain>.com,host2.<domain>.com
• cmx.appserver.rmi.port=4447,4448
Where the host name and port number of the first server are host1, and 4447, and the host name and port
number of the second server are host2, and 4448.

Note: Separate the port numbers by a comma with no space between them. The order of host names and
port numbers must be the same.

1. Start the JBoss application server on each cluster node.

2. Run the following file on each cluster node to start the Hub Server installer:
On UNIX. ./hub_install.bin
On Windows. hub_install.exe
3. When the installer prompts for the configuration name, enter standalone.
4. When the installer prompts for the remote port, enter the remote port of the cluster node that is running
in the machine.
5. Click Yes when the installer prompts you to run the postInstallSetup script to deploy the application.
6. After the installation, open the cmxserver.properties file on each cluster node.
The cmxserver.properties file is in the following location:
On UNIX. <infamdm_install_directory>/hub/server/resources/cmxserver.properties
On Windows. <infamdm_install_directory>\hub\server\resources\cmxserver.properties

60 Chapter 5: Hub Server Installation

7. Change the following properties in the cmxserver.properties file:

Property Description

cmx.appserver.hostname Specify host names of the cluster servers in the

following format:
<host_name>.<domain>.com

cmx.appserver.rmi.port Specify remote port numbers.

8. Restart the JBoss application server on each cluster node.

You can use any node in the JBoss cluster to access the Hub Server.

Installing and Deploying the Hub Server on Nodes in the Cluster 61

CHAPTER 6

Hub Server Post-Installation

Tasks
This chapter includes the following topics:

• Copy the Installation Log Files, 62

• Verify the Version and Build Number, 65
• Configure the Hub Server, 66
• Configuring JBoss for Multiple Process Servers , 67
• Running the Post Install Script Manually, 68
• Manually Redeploying the Hub Server Application, 68
• Manually Creating Data Sources, 69
• Manually Configuring JMS Message Queues, 70
• Changing the Operational Reference Store User Password, 73
• Repackaging Custom JAR Files, 73
• Configure JBoss Cache, 74
• Configuring an EJB Client for the Hub Console, 75
• Configure Logging for Informatica Platform, 76
• Starting the Hub Console, 76
• Registering an Operational Reference Store, 77
• Configuring JBoss Security, 79
• Adding MDM-ActiveVOS Users to the Application Server, 81
• ActiveVOS Web Applications, 81
• Configuring the ActiveVOS URNs, 82

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.

62
Installation Log File
The installation log file contains information about the installed files.

The following table describes the properties of the installation log file:

Property Description

File Name Informatica_MDM_Hub_Server_Install_<ti

mestamp>.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:

Property Description

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.

Debug Log File

The installer writes actions and errors to the debug log file.

Copy the Installation Log Files 63

 The following table describes the properties of the debug log file:

Property Description

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:

Property Description

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.

64 Chapter 6: Hub Server Post-Installation Tasks

 The following table describes the properties of the Hub Server log file:

Property Description

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.

JBoss Log File

The JBoss log file contains information about JBoss processes.

The following table describes the properties of the JBoss log file:

Property Description

File Name server.log

Location On UNIX. <JBoss_install_dir>/

standalone/log
On Windows. <JBoss_install_dir>
\standalone\log

Usage Get information about JBoss processes for

troubleshooting.

Contents Contains JBoss event logs and error messages.

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-server.ear file.
The siperian-mrm-server.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

Verify the Version and Build Number 65

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

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.

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.

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:

On UNIX. <infamdm_install_directory>/hub/server/conf
On Windows. <infamdm_install_directory>\hub\server\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 log4j.xml file.

Setting the Configuration Properties

You can configure the Hub Server properties in the cmxserver.properties file.

66 Chapter 6: Hub Server Post-Installation Tasks

 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=jboss
cmx.appserver.version=7
cmx.appserver.web.port=8080
cmx.appserver.rmi.port=4447
cmx.appserver.naming.protocol=remote
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
Note: If you need to change ports because of port conflicts, ensure that the cmx.appserver.rmi.port
value is the same as the remote port number.
3. Restart the Hub Server application to reload the settings in the cmxserver.properties file.

Changing the JBoss Settings

If you want to change any of the JBoss 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 JBoss configuration settings.
3. Save and close the build.properties file.
4. Run the postInstallSetup script.
5. Restart the JBoss application server.

Configuring JBoss for Multiple Process Servers

If you want to configure multiple Process Servers, configure a separate JBoss instance for each additional
Process Server.

u Copy the JDBC files from the JBoss instance of the Hub Server to the JBoss instance on which you want
to deploy the Process Servers.
The JDBC files are in the following directory:
On UNIX. <JBoss installation directory>/modules/com/informatica/mdm/jdbc/main
On Windows. <JBoss installation directory>\modules\com\informatica\mdm\jdbc\main

Configuring JBoss for Multiple Process Servers 67

Running the Post Install Script Manually
If you skipped the post install script during installation, you must run the post install script manually.

1. Open a command prompt.

2. Navigate to the PostInstallSetup script in the following directory:
On UNIX. <infamdm installation directory>/hub/server
On Windows. <infamdm installation directory>\hub\server
3. Run the following command:
On UNIX. postInstallSetup.sh -Ddatabase.password=<MDM_Hub_Master_DB_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 -Ddatabase.password=<MDM_Hub_Master_DB_Password>

Manually Redeploying the Hub Server Application

You can manually deploy the Hub Server application. Ensure that you deploy the Hub Server application from
the Hub Server installation directory.

Note: If you manually change the configuration of data sources in standalone-full.xml when JBoss is
running, the changes are lost when you run the post-installation setup script.

1. Stop the JBoss application server.

2. Remove the siperian-mrm.ear file from the following location.
On UNIX.
• <JBoss_install_dir>/<configuration_name>/deployments
On Windows.
• <JBoss_install_dir>\<configuration_name>\deployments
3. Copy siperian-mrm.ear from the source to the target directories:
On UNIX.
Source: Hub Server installation directory
Target: <JBoss_install_dir>/<configuration_name>/deployments
On Windows.
Source: Hub Server installation directory
Target: <JBoss_install_dir>\<configuration_name>\deployments
4. Manually configure JMS and data sources in the standalone-full.xml file.
5. Start the application server.
See the JBoss documentation for more information.

68 Chapter 6: Hub Server Post-Installation Tasks

Manually Creating Data Sources
If you want to configure multiple Process Servers, configure a separate JBoss instance for each additional
Process Server and manually configure data sources. Also, if you need to troubleshoot issues, you can
manually create data sources for the MDM Hub. For example, create data sources manually if the automated
queue creation process fails.

1. Open the JBoss Management console.

2. Click Profile.
The data sources page appears.
3. Click Connector > Datasources.
4. Click the XA Datasources tab.
The JDBX XA Datasources page appears.
5. Click Add.
The Create XA Datasource dialog box appears.
6. Enter values in the Name and JNDI Name fields.
Name
jdbc/siperian-<Oracle host name>-orcl-<operational reference store name>-ds

JNDI Name
java:jboss/datasources/jdbc/siperian-<Oracle host name>-orcl-<operational reference store name>-
ds
7. Click Next.
The Datasource Class window appears.
8. Select the oracle.jdbcdriver for the database, and click Next.
The XA Properties window appears.
9. Enter the key and value pairs, and click Next.
The following table lists the key value pairs:

Key Value

ConnectionProperties oracle.jdbc.J2EE13Compliant=true

URL Use one of the following values based on the Oracle

connection type:
For SERVICE. jdbc:oracle:thin:@//<Oracle host
name>:1521:<service name>
For SID. jdbc:oracle:thin:@<Oracle host name>:
1521:orcl

The Connection Settings window appears.

10. Enter values for the following connection settings, and click Done:
Username
Name of the Operational Reference Store.

Manually Creating Data Sources 69

 Password
Password to access the Operational Reference Store.

The JDBC XA Datasources page appears.

11. In the Selection section, edit the properties under the Pool tab.

Property Value

Min Pool Size 5

Max Pool Size 100

Strict Minimum false

Prefill enabled false

Flush Strategy FailingConnectionOnly

Idle Timeout 0

Track Statements false

12. In the Selection section, edit the properties under the Validation tab.

Property Value

Valid Connection Checker Not applicable

Check Valid Sql Not applicable

Validate On Match false

Background Validation false

Validation Millis 0

Stale Connection Checker Not applicable

Exception Sorter org.jboss.jca.adapters.jdbc.extensions.oracle.Oracle

ExceptionSorter

13. Select the data source that you added, and click Enable.
The data source that you added is enabled.

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.

70 Chapter 6: Hub Server Post-Installation Tasks

 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 connection factory.

2. Create a JMS message queue.
3. Verify the JMS message queue configuration.
4. Add a message queue server.
5. Add a message queue.

Step 1. Create a Connection Factory

You can manually create a connection factory.

1. Open the JBoss Management console.

2. Click Profile > Messaging > Destinations.
The JMS Messaging Provider page appears.
3. To view the settings of the default JMS messaging provider, click View.
The Messaging Destinations page appears.
4. Select the Connection Factories link.
The configured connection factories appear.
5. To add a connection factory, click Add.
The Create Connection Factory dialog box appears.
6. Enter values for the following fields:
Name
Connection Factory name. Specify java:/ConnectionFactory.

JNDI Names
JNDI Name. Specify Java:/ConnectionFactory.

Connector
Connector that you use to connect to the server. The following connectors are available:
• in-vm. Use the in-vm connector to connect to a local server.
• netty. Use the netty connector to connect to a remote server.
7. Click Save.
The connection factory is created.

Step 2. Create a JMS Message Queue

To manually create a JMS message queue, use the JBoss Management console.

1. Open the JBoss Management console.

2. Click Profile > Messaging > Destinations.
The JMS Messaging Provider page appears.

Manually Configuring JMS Message Queues 71

 3. Click View to view the settings of the default JMS messaging provider.
The JMS Queue destination appears.
4. To create a JMS queue, click Add.
The Create JMS Queue dialog box appears.
5. Enter values for the following fields:
Name
Queue name. Specify queue/<queue name>.

JNDI Names
JNDI Name. Specify java:/queue/<queue name>.
6. Clear the Durable option, and click Save.
The queue is created.

Step 3. Verify the JMS Message Queue Configuration

You can verify the JMS message queue configuration in the standalone-full.xml file.

1. Open the standalone-full.xml file in the following directory:

On UNIX. <JBoss_install_dir>/standalone/configuration
On Windows. <JBoss_install_dir>\standalone\configuration
2. Verify the following JMS message queue configuration:
XA connection factory name
java:/siperian.mrm.jms.xaconnectionfactory

JMS queue name

queue/siperian.sif.jms.queue

Step 4. Add a Message Queue Server

Before you add a message queue, you must add a message queue server to the MDM Hub implementation .

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 java:/ConnectionFactory.

Display Name
Name of the message queue server that must appear in the Hub Console. Specify Java:/
ConnectionFactory.
6. Click OK.
The message queue server is added.

72 Chapter 6: Hub Server Post-Installation Tasks

 Step 5. Add a Message Queue
You can add a message queue to a message queue server.

1. Start the Hub Console.

2. Click Message Queues under the Configuration workbench.
3. Click Write Lock > Acquire Lock.
4. Right-click the message queue server in the middle pane of the Message Queues tool, and then click
Add Message Queue.
The Add Message Queue dialog box appears.
5. Enter values for the following fields:
Queue Name
Name of the message queue. Specify java:/queue/<queue name>.

Display Name
Name of the message queue that must appear in the Hub Console. Specify Java:/Queue/<Queue
Name>.
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.

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-server.ear file after you install
the Hub Server.

1. Run the following command to create a directory named EAR:

Changing the Operational Reference Store User Password 73

 On UNIX.
cd <infamdm_install_directory>/hub/server/lib
mkdir ear
On Windows.
cd <infamdm_install_directory>\hub\server\lib
mkdir ear
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
sip_ant.sh repackage
On Windows.
cd <infamdm_install_directory>\hub\server\bin
sip_ant.bat repackage

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.

74 Chapter 6: Hub Server Post-Installation Tasks

 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>

Configuring an EJB Client for the Hub Console

If you do not want to use the default JBoss EAP 6.1.1 EJB client with the Hub Console, configure another
EJB client.

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 ejb-client-version property to one of the following values that corresponds to the EJB client
that you want to use:
• jboss-6.0.1
• jboss-6.1.1
• jboss-6.1.1-BZ1032293
3. Restart the Hub Server application to reload the settings in the cmxserver.properties file.

Configuring an EJB Client for the Hub Console 75

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:

On UNIX. <infamdm_install_directory>/hub/server/conf
On Windows. <infamdm_install_directory>\hub\server\conf
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.

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.

76 Chapter 6: Hub Server Post-Installation Tasks

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.

1. Start the Hub Console.

The Change database dialog box appears.
2. Select the MDM Hub Master database, and click Connect.
3. Start the Databases tool under the Configuration workbench.
4. Click Write Lock > Acquire Lock.
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.
The Connection Properties page appears.
b. Specify the connection properties for the connection type that you select, and click Next.
The following table lists and describes the connection properties:

Property Description

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.

Registering an Operational Reference Store 77

 Property Description

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.

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.

78 Chapter 6: Hub Server Post-Installation Tasks

 The following table lists additional connection properties that you can configure:

Property Description

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.

Configuring JBoss Security

You can configure EJB security at the JBoss application server level or at the Hub Server level to prevent
unauthorized access to data and other resources in the MDM Hub. To configure EJB security at the JBoss
application server level, enable the JBoss remoting-connector security.

1. Log in to the Hub Console and change the Hub Console password to a password that adheres to the
JBoss password policy.
Note: Ensure that the password that you set adheres to the JBoss password policy, as well as the MDM
Hub global password policy that you set. This is important because the same password needs to be set
for the Hub Console and for JBoss.

Configuring JBoss Security 79

 For information on the MDM Hub global password policy, see the Informatica MDM Multidomain Edition
Configuration Guide.
a. Disable remoting-connector security.
b. Change the Hub Console password to adhere to the JBoss password policy.
1. Log in to the Hub Console, change the database to the MDM Hub Master Database and click
Connect.
2. Select the Users tool under Configuration workbenches and acquire a write lock.
3. Select the admin user under the User tab, and click the Change password icon.
The Change Password dialog box appears.
4. Change the password to adhere to the JBoss password policy, and click OK.
2. Enable the remoting-connector security.
a. Open the following file in a text editor:
On UNIX.
<Jboss_install_dir>/jboss-eap-6.1.1/standalone/configuration/standalone-full.xml
On Windows.
<Jboss_install_dir>\jboss-eap-6.1.1\standalone\configuration\standalone-full.xml
b. Add the security-realm attribute as shown in the following code:
<subsystem xmlns="urn:jboss:domain:remoting:1.1">
<connector name="remoting-connector" socket-binding="remoting" security-
realm="ApplicationRealm"/>
</subsystem>
3. Register the MDM Hub users that must have access to the Hub Server in JBoss.
a. You can run the following script as one of the ways to register the MDM Hub users:
On UNIX. <JBoss_install_dir>/bin/add-user.sh
On Windows. <JBoss_install_dir>\bin\add-user.bat
b. Answer the prompts in the following table:

Prompt Value

What type of user do you wish to add? Specify the option b.

a) Management User (mgmt-users.properties)
b) Application User (application-
users.properties)

Realm (ApplicationRealm) Use the default value. Deafult is

ApplicationRealm.

Username User name of the MDM Hub user.

Password Password of the MDM Hub user that adheres to

JBoss password policy.

What roles do you want this user to belong to? You must specify hubconsole.

80 Chapter 6: Hub Server Post-Installation Tasks

 4. Enable JBoss security on the Hub Server.
a. Open cmxserver.properties in the following directory:
On UNIX. <infamdm_install_directory>/hub/server/resources
On Windows. <infamdm_install_directory>\hub\server\resources
b. Uncomment the following property in the cmxserver.properties file:
#cmx.jboss7.security.enabled=true
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
5. Run the following command to repackage the siperian-mrm-server.ear file:
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
6. Deploy the siperian-mrm-server.ear file.

RELATED TOPICS:
• “Disabling Remoting-Connector Security” on page 24
• “Manually Redeploying the Hub Server Application” on page 68

Adding MDM-ActiveVOS Users to the Application

Server
To finish the integration of the ActiveVOS Server with the MDM Hub, you need to set up container-based
authentication in the application server and add users.

For step-by-step instructions on configuring container-based authentication, see the How-To Library
document Container-based Authentication for MDM-ActiveVOS in JBoss
https://mysupport.informatica.com/docs/DOC-13236.

Note: You need to use the same user names, passwords, and roles in the MDM Hub, ActiveVOS, and the
application server. Ensure that the password complies with the password standard for the application server.

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:

Adding MDM-ActiveVOS Users to the Application Server 81

 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 IDD Task Inbox.

For more information about the web applications, see the Informatica ActiveVOS documentation.

Configuring the ActiveVOS URNs

The ActiveVOS Server has two predefined uniform resource names (URNs) that it uses to direct to web
pages. You need to update the URL in the URN mappings to use the host name and 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:
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 correct host name and port number:

URN URL Path

ae:internal-reporting http://[host]:[port]/activevos/internalreports

ae:task-inbox http://[host]:[port]/activevos-central/avc

4. Verify that urn:MDMHost:InfaMDM is mapped to:

http://[host]:[port]/cmx/services/SifService

82 Chapter 6: Hub Server Post-Installation Tasks

CHAPTER 7

Process Server Installation

This chapter includes the following topics:

• Installing the Process Server in Graphical Mode, 83

• Installing the Process Server in Console Mode, 85
• Installing the Process Server in Silent Mode, 86
• Installing and Deploying the Process Server on Nodes in the Cluster, 89

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.

1. Start the application server.

2. Open a command prompt and navigate to the Process Server installer in the distribution 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. Run the following command:
On UNIX. hub_cleanse_install.bin
On Windows. hub_cleanse_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 Install Folder window appears.
7. Select the location of the Process Server installation.

83
 • To choose the default location, click Next.
• To choose another location, click Choose, and then click Next.
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.
9. Click Choose to select a license file, and click Next.
The Application Server window appears.
10. Select JBoss, and then click Next.
The JBoss Application Server Home window appears.
11. Configure the following JBoss settings:
a. Specify the path to the JBoss installation directory, and then click Next.
The JBoss Application Server Configuration Name window appears.
b. Specify the Configuration Name, and then click Next.
The default value is standalone.
The JBoss Application Server Port window appears.
c. Specify the remote port.
d. Click Next.
12. Configure cleanse engine settings for the cleanse engine you use.
• If you use Address Doctor, specify the Configuration file and Parameter 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.
The Deploy window appears.
14. To run the post install script during the installation, select Yes, run the script during this installation.
To manually run the post install script, select No, I will run it later.
15. Click Next.
The Pre-Installation Summary window appears.
16. After the summary window displays the options you want, click Install to start the installation process.
When the installation completes, the Install Complete window appears.
17. Select Yes, restart my system to restart the system, or select No, I will restart the system myself to
restart it later.
18. 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.

84 Chapter 7: Process Server Installation

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.

1. Start the application server.

2. Navigate to the following directory in the MDM Hub distribution:
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
3. Run the following command from the command prompt:
./hub_cleanse_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 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 the folder for the Process Server installation.
• To choose the default location, 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.
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.
13. Configure the JBoss settings.
a. Specify the application server installation directory, and press Enter.
The JBoss application server configuration name information appears.
b. Specify the configuration name. The default value is standalone.
c. Press Enter.
The JBoss Pre-requisites warning appears.
d. Press Enter.

Installing the Process Server in Console Mode 85

 e. Specify the remote port.
Note: If the JBoss port conflicts with the default database port, then change one of the ports to
resolve the conflict.
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.

The deployment information appears.

16. Choose whether you want to run the postInstallSetup script as part of the installation, or run it
manually later.
17. Press Enter.
The summary of the installation choices appears.
18. Verify the information in the pre-installation summary. If the information is correct, press Enter to start
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.
19. Press Enter.
The Process Server is installed according to the information you specify, and the install complete
information appears.
20. Press Enter to exit the installer.

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
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 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. Configure the installation properties file and specify the installation options in the properties file.
2. Run the installer with the installation properties file.

86 Chapter 7: Process Server Installation

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. 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
Note: In the silent properties file, slash and backslash are special characters. You must enter two of
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.
3. Use a text editor to open the file and change the values of the installation parameters.
4. Save the properties file with a name such as silentInstallCleanse.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 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.AS.CHOICE Name of the application server. Specify JBoss.

SIP.AS.HOME The path to the JBoss installation directory.

JBOSS.AS.PORT_1 The JBoss Port number.

SIP.JBOSS.CONFIGURATION_NAME The JBoss configuration name. The default value is

standalone.

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.

Installing the Process Server in Silent Mode 87

 Property Name Description

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.DEFAULTCORRECTIONTYP Address Doctor Cleanse Engine correction type.

E 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

Sample Properties File

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 JBoss application server

SIP.AS.CHOICE="JBoss"
SIP.JBOSS.AS.VERSION=7
SIP.AS.HOME=C\:\\jboss-eap-6.1.1
JBOSS.AS.PORT_1=4447
SIP.JBOSS.CONFIGURATION_NAME=standalone

## 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

## Following FirstLogicDirect properties should be set if you have lincense for

FirstLogicDirect.
SIP.FLDIRECT.HOST=localhost
SIP.FLDIRECT.PORT=20004

88 Chapter 7: Process Server Installation

 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
RUN_DEPLOYMENT_FLAG=1

## 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

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.
3. Run the following command:
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.
The log file is available in the following directory:
On UNIX. <infamdm_install_directory>/hub/cleanse/logs/
On Windows. <infamdm_install_directory>\hub\cleanse\logs\

Installing and Deploying the Process Server on

Nodes in the Cluster
If you have a clustered environment, install the Process Server on each node of the cluster where you need
to deploy the Process Server application. You must ensure that the path for the Process Server installation is
the same on all the cluster nodes.

1. Start the JBoss application server on each cluster node.

2. Run the following file on each cluster node to start the Process Server installer:
On UNIX. ./hub_cleanse_install.bin
On Windows. hub_cleanse_install.exe
3. When the installer prompts for the configuration name, enter standalone.
4. When the installer prompts for the remote port, enter the remote port of the cluster node that is running
in the machine.
5. Click Yes when the installer prompts you to run the postInstallSetup script to deploy the application.
6. Restart the JBoss application server on each cluster node.

Installing and Deploying the Process Server on Nodes in the Cluster 89

CHAPTER 8

Process Server Post-Installation

Tasks
This chapter includes the following topics:

• Copy the Installation Log Files, 90

• Verify the Version and Build Number, 93
• Configure the Process Server, 93
• Configure Process Server for Multithreading, 96
• Configuring Multiple Process Servers for Cleanse and Match Operations, 97
• Configuring Multiple Process Servers for Batch Processes, 98
• Configure Match Population, 99

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:

Property Description

File Name Informatica_MDM_Cleanse_Match_Server_I

nstall_<timestamp>.xml

Location On UNIX.
<infamdm_install_directory>/hub/
cleanse/UninstallerData/Logs
On Windows. <infamdm_install_directory>
\hub\cleanse\UninstallerData\Logs

90
 Property Description

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:

Property Description

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:

Property Description

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.

Copy the Installation Log Files 91

 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:

Property Description

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:

Property Description

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.

JBoss Log File

The JBoss log file contains information about JBoss processes.

92 Chapter 8: Process Server Post-Installation Tasks

 The following table describes the properties of the JBoss log file:

Property Description

File Name server.log

Location On UNIX. <JBoss_install_dir>/

standalone/log
On Windows. <JBoss_install_dir>
\standalone\log

Usage Get information about JBoss processes for

troubleshooting.

Contents Contains JBoss event logs and error messages.

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.

Verify the Version and Build Number 93

 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.

If the Process Server is not deployed on the same application server as the Hub Server, you must manually
configure the application server to create data sources for the Process Server. Copy the data source
definition from the standalone-full.xml file of the application server on which the Hub Server is deployed to
the standalone-full.xml file of the application server on which the Process Server is deployed.

The standalone-full.xml file is in the following location:

On UNIX. <JBoss_install_dir>/standalone/configuration

On Windows. <JBoss_install_dir>\standalone\configuration

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

94 Chapter 8: Process Server Post-Installation Tasks

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

Setting the Configuration 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.
A sample configuration of the cmxcleanse.properties is as follows:
cmx.server.logging.location=/u1/infamdm/hub/cleanse/logs
cmx.server.datalayer.cleanse.working_files.location=/u1/infamdm/hub/cleanse/tmp
cmx.server.datalayer.cleanse.working_files=KEEP
cmx.server.datalayer.cleanse.execution=LOCAL
cmx.home=/u1/infamdm/hub/cleanse
cmx.appserver.type=jboss
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 must run the post install script manually.

1. Open a command prompt.

2. Navigate to the PostInstallSetup script in the following directory:
On UNIX. <infamdm installation directory>/hub/cleanse
On Windows. <infamdm installation directory>\hub\cleanse
3. Run the following command:
On UNIX. postInstallSetup.sh
On Windows. postInstallSetup.bat

Manually Redeploying the Process Server EAR File

You can manually redeploy the Process Server EAR file.

1. Stop the JBoss application server.

2. Delete the siperian-mrm-cleanse.ear file from the deploy directory.
The deploy directory is in the following location:
On UNIX. <JBoss_install_dir>/standalone/deployments
On Windows. <JBoss_install_dir>\standalone/deployments

Configure the Process Server 95

 3. Copy the siperian-mrm-cleanse.ear file from the Process Server installation directory to the deploy
directory.
4. Navigate to the post install script in the following directory:
On UNIX. <infamdm_install_directory>/hub/cleanse
On Windows. <infamdm_install_directory>\hub\cleanse
5. Run the following command:
On UNIX. postinstallsetup.sh
On Windows. postinstallsetup.bat
6. Start the JBoss application 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.

96 Chapter 8: Process Server Post-Installation Tasks

 2. Click Write Lock > Acquire Lock.
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.
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:

Property Description

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:

On UNIX. <infamdm_install_directory>/hub/cleanse/resources
On Windows. <infamdm_install_directory>\hub\cleanse\resources

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.

Configuring Multiple Process Servers for Cleanse and Match Operations 97

 9. Configure properties for each Process Server to enable a distributed cleanse process.
The following table describes the properties to set:

Property Description

Offline The MDM Hub ignores the settings for the Offline
property. Taking the Process Server online or offline
is an administrative task.

Enable Cleanse Operations Specifies whether to use the Process Server for
cleanse operations. Enable to use Process Server
for cleanse operations. Disable if you do not want to
use the Process Server for cleansing. Default is
enabled.

Threads for Cleanse Operations Specifies the number of threads that a server must
handle. Set the thread count higher than the number
of CPUs available.

Enable Match Processing Specifies whether to use the Process Server for
match operations. Enable to use 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.

98 Chapter 8: Process Server Post-Installation Tasks

 The following table describes the properties to set:

Property Description

Offline Specifies whether a Process Server is online or

offline. Disable this property to ensure that a
Process Server is online.

Enable Batch Processing Specifies whether to use the Process Server for
batch processing. Enable to use 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 Processing Specifies the number of threads that a server must
handle for batch processing. Set 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.

Configure Match Population 99

 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.

100 Chapter 8: Process Server Post-Installation Tasks

CHAPTER 9

Resource Kit Installation

This chapter includes the following topics:

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

• Registering the Informatica MDM Hub Sample Operational Reference Store, 104
• Installing the Resource Kit in Graphical Mode, 106
• Installing the Resource Kit in Console Mode, 108
• Installing the Resource Kit in Silent Mode, 110
• Installing and Deploying the Resource Kit into a JBoss Cluster, 114

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.

1. Navigate to the following location in the distribution directory:

On UNIX. <distribution directory>/database/bin
On Windows. <distribution directory>\database\bin
2. Run the following command:
On UNIX. sip_ant.sh create_ors
On Windows. sip_ant.bat create_ors
3. Answer the prompts that appear.
Note: The prompt displays default text in brackets. Press Enter to use the default value and go to the
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.

101
 • 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]

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:
On UNIX. <distribution directory>/database/bin
On Windows. <distribution directory>\database\bin
The sip_ant.log file logs any errors that might occur when you run the sip_ant script to create the
Operational Reference Store.

102 Chapter 9: Resource Kit Installation

5. To import mdm_sample, run the following command:
On UNIX. sip_ant.sh import_schema
On Windows. sip_ant.bat import_schema
6. Answer the prompts that appear.
Note: The prompt displays default text in brackets. Press Enter to use the default value and go to the
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.

Setting Up the MDM Hub Sample Operational Reference Store 103

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.

1. Start the Hub Console.

The Change database dialog box appears.
2. Select the MDM Hub Master Database, and click Connect.
3. Start the Databases tool under the Configuration workbench.
4. Click Write Lock > Acquire Lock.
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.

The Connection Properties page appears.

b. Specify the connection properties for the connection type that you select, and click Next.
The following table lists and describes the connection properties:

Property Description

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.

104 Chapter 9: Resource Kit Installation

 Property Description

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:

Property Description

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.

Registering the Informatica MDM Hub Sample Operational Reference Store 105
 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.

1. Start the application server.

2. Open a command prompt and navigate to the Resource Kit installer. By default the installer is in the
following directory:
On UNIX. <distribution directory>/<operating system name>/mrmresourcekit
On Windows. <distribution directory>\windows\mrmresourcekit
3. Run the following command:
On UNIX. hub_resourcekit_install.bin
On Windows. hub_resourcekit_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 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
following directory:
<Resourcekit_Home>\samples

SIF SDK and Javadocs

Installs the javadocs, libraries, and resources associated with the SIF SDK.

106 Chapter 9: Resource Kit Installation

 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.
The Choose Install Folder window appears.
9. Select the location of the Resource Kit installation.
• To choose the default location, click Next.
• To enter a path, type the path to the installation folder, and click Next.
Note: The installation fails if you specify a path that has spaces in the directory or folder names.
• To return to the default installation location, click Restore Default Folder.
• To choose another location, click Choose, and then click Next.
On UNIX, the Choose Link Folder window appears.
On Windows, the Choose Shortcut Folder window appears.
10. 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.
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.
a. Specify the application server installation directory, and then click Next.
The JBoss Application Server Configuration Name window appears.
b. Specify the configuration name, and then click Next.
The default value is standalone.
c. Specify the remote port.
The Informatica MDM Hub Server window appears.
14. Enter the information for the Hub Server installation, and click Next.

Installing the Resource Kit in Graphical Mode 107

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

The Pre-Installation Summary window appears.

17. Review the Pre-Installation Summary to confirm your installation choices, and then click Install.
When the installation completes, the Install Complete window appears.
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.

1. Start the application server.

2. Navigate to the following directory in the MDM Hub distribution:
On UNIX. <distribution directory>/<operating system name>/resourcekit
On Windows. <distribution directory>/windows/resourcekit

108 Chapter 9: Resource Kit Installation

 3. Run the following command from the command prompt:
On UNIX. ./hub_install.bin -i console
On Windows. hub_resourcekit_install.exe -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. 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.
• To change the path, type the absolute path of the installation folder, and press Enter.
10. Confirm the location of the installation folder. Type OK to confirm the installation folder or type Cancel to
change the installation folder.
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.
16. Configure the JBoss settings.
a. Specify the application server installation directory, and press Enter.
The information about the JBoss application server configuration name appears.
b. Specify the configuration name. The default value is standalone.
c. Press Enter.

Installing the Resource Kit in Console Mode 109

 d. Specify the remote port.
Note: If the JBoss port conflicts with the default database port, change one of the ports to resolve
the conflict.
The Hub Server 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.
19. Choose whether you want to run the postInstallSetup script as part of the installation, or run it
manually later.
20. Press Enter.
The summary of the installation choices appears.
21. Verify the information in the pre-installation summary. If the information is correct, press Enter to start
the installation.
The Resource Kit is installed according to the configuration information you provide. When the process is
complete, the installation complete information appears.
22. Press Enter to exit the installer.

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
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 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. Configure the installation properties file and specify the installation options in the properties file.

110 Chapter 9: Resource Kit Installation

 2. Run the installer with the installation properties file.

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 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.
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\
\resourcekit.
2. Create a backup copy of the silentInstallResourceKit_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 silentInstallresourcekit.properties.
The following table describes the installation parameters that you can change:

Property Name Description

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.

Specify one of the following values:
- 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.
Specify one of the following values:
- 0. Does not install the SIF SDK
- 1. Installs SIF SDK

SIP.INSTALL.BPM.SDK Specifies if you want to install the BPM SDK.

Specify one of the following values:
- 0. Does not install the BPM SDK
- 1. Installs the SIF SDK

Installing the Resource Kit in Silent Mode 111

 Property Name Description

SIP.INSTALL.JASPERSOFT Specifies if you want to install the Jaspersoft reporting

tool.
Specify one of the following values:
- 0. Does not install the BPM SDK
- 1. Installs the SIF SDK

SIP.INSTALL.SSANAME3 Specifies if you want to install SSA-NAME3.

Specify one of the following values:
- 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.

SIP.AS.CHOICE Name of the application server. Specify JBoss.

SIP.AS.HOME The path to the JBoss installation directory.

JBOSS.AS.PORT_1 The JBoss port number.

SIP.JBOSS.CONFIGURATION_NAME The JBoss configuration name. The default value is

standalone.

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.

112 Chapter 9: Resource Kit Installation

 Property Name Description

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

Sample Properties File

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 JBoss 7 application server

SIP.AS.CHOICE="JBoss"
SIP.AS.HOME=C\:\\jboss-eap-6.1.1
JBOSS.AS.PORT_1=4447
SIP.JBOSS.CONFIGURATION_NAME=standalone

## properties for MDM Hub Server

SIP.SERVER.NAME=localhost
SIP.SERVER.HTTP.PORT=4447
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:
RUN_DEPLOYMENT_FLAG=1
## If you want to run postInstallSetup as a part of silent installation, set the
following property:
RUN_DEPLOYMENT_FLAG=0

Installing the Resource Kit in Silent Mode 113

 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.
3. Run the following command:
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.

The log file is available in the following directory:

On UNIX. <infamdm_install_directory>/logs/postInstall.log

On Windows. <infamdm_install_directory>\logs\postInstall.log

Installing and Deploying the Resource Kit into a

JBoss Cluster
After you install the Hub Server and register the MDM Hub sample Operational Reference Store, you can
install the Resource Kit.

In a clustered environment, install the Resource Kit on each node of the cluster where you want to deploy the
Resource Kit.

Note: Ensure that the directory structure of the Resource Kit installation is the same on all the cluster nodes.

1. Start the application server.

2. Open a command prompt and navigate to the Resource Kit installer. By default the installer is in the
following directory:
On UNIX. <distribution directory>/<operating system name>/mrmresourcekit
On Windows. <distribution directory>\windows\mrmresourcekit
3. Run the following command:
On UNIX. hub_resourcekit_install.bin
On Windows. hub_resourcekit_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 Installation Feature window appears.
7. Select the Resource Kit features that you want to install and click Next.

114 Chapter 9: Resource Kit Installation

 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
following directory:
<Resourcekit_Home>\samples

SIF SDK and Javadocs

Installs the javadocs, libraries, and resources associated with the SIF SDK.

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. Select the location of the Resource Kit installation.
• To choose the default location, click Next.
• To enter a path, type the path to the installation folder, and click Next.
Note: The installation fails if you specify a path that has spaces in the directory or folder names.
• To return to the default installation location, click Restore Default Folder.
• To choose another location, click Choose, and then click Next.
On UNIX, the Choose Link Folder window appears.
On Windows, the Choose Shortcut Folder window appears.
9. 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.
The Configuration Selection window appears.
10. 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.
11. 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.

Installing and Deploying the Resource Kit into a JBoss Cluster 115
 12. Configure the application server settings.
a. Specify the application server installation directory, and then click Next.
The JBoss Application Server Configuration Name window appears.
b. Specify the configuration name, and then click Next.
The default value is standalone.
c. Specify the remote port.
The Informatica MDM Hub Server window appears.
13. 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.

14. 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.
15. Select the Yes, run it during this installation option, and click Next.
The Pre-Installation Summary window appears.
16. Review the Pre-Installation Summary to confirm your installation choices, and then click Install.
When the installation completes, the Install Complete window appears.
17. Click Done to exit the Resource Kit installer.
18. Restart the cluster servers and member nodes.

116 Chapter 9: Resource Kit Installation

CHAPTER 10

Troubleshooting the MDM Hub

This chapter includes the following topic:

• Troubleshooting the Installation Process, 117

Troubleshooting the Installation Process

If the installation fails, use the following information to troubleshoot the failure.

Cannot start JBoss or launch the Hub Console after installation

After installation, JBoss might not restart after you stop JBoss. When you launch the Hub Console, the Hub
Console fails to launch and generates the following error:
SIP-09070: Failed to initialize repository layer.

To resolve the issue, run the following code in a batch file to restart JBoss:
rmdir C:\<JBoss installation directory>\standalone\tmp /s /q
\mkdir C:\<JBoss installation directory>\standalone\tmp
C:\<JBoss installation directory>\bin\standalone.bat -c standalone-full.xml -b 0.0.0.0

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

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.

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, the following error might appear in Websphere log SystemOut.log:
Caused by: java.sql.SQLException: ORA-28000: the account is locked
DSRA0010E: SQL State = 99999, Error Code = 28,000

117
 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"/>

Java XAException
When you restart JBoss after you install the Hub Server, the following exception might be generated:
javax.transaction.xa.XAException

You can ignore the exception.

118 Chapter 10: Troubleshooting the MDM Hub

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 bin directory under the JBoss root directory.

2. Open the following file in a text editor.
On UNIX. run.sh
On Windows. run.bat
3. Set the JAVA_OPTS variable as follows:
JAVA_OPTS=${JAVA_OPTS} -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.

Troubleshooting the Installation Process 119

CHAPTER 11

Uninstallation
This chapter includes the following topics:

• Uninstallation Overview, 120

• Uninstalling the Hub Store, 120
• Uninstalling the Process Server in Graphical Mode, 121
• Uninstalling the Hub Server in Graphical Mode, 122
• Uninstalling the Resource Kit in Graphical Mode, 122
• Uninstalling the Process Server in Console Mode, 123
• Uninstalling the Hub Server in Console Mode, 123
• Uninstalling the Resource Kit in Console Mode, 124
• Manually Undeploying the Process Server, 124
• Manually Undeploying the Hub Server, 124

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.

1. Start the Hub Console.

120
 2. Click the Databases tool under the Configuration workbench.
The Database Information page appears.
3. Click Write Lock > Acquire Lock.
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.

2. Navigate to the following directory:
<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.

1. Stop the application server.

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.
When the uninstallation process is complete, the Uninstall Complete window appears.
4. Click Done.

Uninstalling the Process Server in Graphical Mode 121

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.

2. Navigate to the following directory:
<infamdm_install_directory>/hub/server/UninstallerData
3. Run the uninstaller.
./"Uninstall Informatica MDM Hub Server"
The Uninstall introduction window appears.
4. Click Uninstall.
When the uninstallation process is complete, the Uninstall Complete window appears.
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.
The Uninstall introduction window appears.
3. Click Uninstall.
When the uninstallation process is complete, the Uninstall Complete window appears.
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.

1. Stop the application server.

2. Navigate to the following directory:
<infamdm_install_directory>/hub/resourcekit/UninstallerData
3. Run the following command:
./"Uninstall Informatica MDM Hub Resource Kit"
The Uninstall Informatica MDM Hub Resource Kit window appears.

122 Chapter 11: Uninstallation

 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.

1. Stop the application server.

2. Navigate to the following directory:
<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.

1. Go to the following directory:

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

Uninstalling the Process Server in Console Mode 123

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.

1. Go to the following directory:

On UNIX. <infamdm_install_dir>/hub/resourcekit/UninstallerData
On Windows. <infamdm_install_dir>\hub\resourcekit\UninstallerData
2. Run the following command from the command prompt:
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 JBoss application server.

1. To manually undeploy the Process Server, delete siperian-mrm-cleanse.ear from the following
directory:
On UNIX. <JBoss_install_dir>/standalone/deployments
On Windows. <JBoss_install_dir>\standalone\deployments
2. Restart the JBoss application server if the JBoss auto-deploy process does not remove the application.
For more information, see the JBoss documentation.

Manually Undeploying the Hub Server

You might need to manually undeploy the Hub Server from the JBoss application server.

1. To manually undeploy the Hub Server, delete siperian-mrm.ear from the following directory:
On UNIX. <JBoss_install_dir>/standalone/deployments
On Windows. <JBoss_install_dir>\standalone\deployments
2. Restart the JBoss application server if the JBoss auto-deploy process does not remove the application.
For more information, see the JBoss documentation.

124 Chapter 11: Uninstallation

INDEX

A Hub Server (continued)

version and build number 65
ActiveVOS Hub Store
adding users to the application server 81 tablespaces, creating 20
URN, setting 82 uninstalling 120
application server
adding MDM Hub users 81
I
C Informatica ActiveVOS
creating the schema 40
configuring JBoss Informatica platform
disabling hornetQsecurity 24 properties file 28
for the MDM Hub 23 installation requirements
configuring Oracle X Window Server 17
configure the init.ora parameters 19 installing
disable the Oracle Recycle Bin 18 Hub Server 51, 54
Oracle RAC 21 Process Server 83, 85
custom jar files Resource Kit 106, 108
repackaging 73

J
D JBoss
databases clustering
connection testing 21 on JBoss 25
target database 76 port conflicts 67
settings 67
starting on UNIX 26

E starting on Windows 26
JBoss cache
environment variables configuring 74
DISPLAY 17 eviction 74
lockAcquisitionTimeout 74
mcast_addr 74

G mcast_port 74
stateRetrieval timeout 74
graphical mode sync replTimeout 74
installation requirements 17 wakeUpInterval 74
JBoss cluster
deploying Hub Server 60

H deploying Process Server 89

JBoss security
Hub Console disabling 24
starting 76 enabling 79
Hub Server JMS message queues
configuration properties 67 configuring 71
deploying on JBoss cluster 60
installation log files 63
installing 51, 54, 106
logging settings 66
L
manually redeploying 68 log file
postinstallsetup script 68 debug log file 64, 92
silent installation 56, 59, 110 Hub Server log file 65
silent properties file 56 installation log file 63, 90
uninstalling 123, 124 installation prerequisites log file 63, 92

125
log file (continued)
JBoss log file 65, 93 R
post install setup log file 64, 91 remoting-connector security
Process Server log file 91 disabling 24
enabling 79
Resource Kit
M installing 106, 108
silent properties file 111
Master Database uninstalling 123
creating 42
importing metadata 45
match population
enabling 99 S
MDM Hub Sample Schema
components 11 installing 101
designing the installation 13 registering 104
installation tasks 12 silent installation
introduction 11 of Hub Server 59
setting environment variables 17 silent installer
system requirements 16 running 89

O T
Operational Reference Store tablespaces
creating 44 creating 20
importing metadata 47 target database
registering 77 selecting 76
timeline
granularity 27
P tns name
adding 21
postinstallsetup script troubleshooting
for Hub Server 68 post-installation process 117
for Process Server 95
running 68, 95
Process Server
configuration properties 95 U
configuring 94 uninstalling
deploying 95 Hub Server 123, 124
deploying on JBoss cluster 89 Hub Store 120
installation log files 90 Process Server 123
installing 83, 85 URN
logging settings 94 setting ActiveVOS 82
multithreading, configuring 96
postinstallsetup script 95
silent installation 86
silent properties file 87 X
threads for batch processing 96 X Window Server
threads for cleanse operations 96 installation requirements 17
uninstalling 123
version and build number 93

126 Index