Installation Guide for JBoss - kb.informatica.com Documentation/5/MDM… · The Informatica MDM Multidomain Edition Installation Guide is written for database administrators, system

Informatica MDM Multidomain Edition for IBM DB2 (Version 9.7.1 HotFix 6)

Installation Guide for JBoss

Informatica MDM Multidomain Edition for IBM DB2 Installation Guide for JBoss

Version 9.7.1 HotFix 6March 2016

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

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

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

The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing.

Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica On Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging, Informatica Master Data Management, and Live Data Map are trademarks or registered trademarks of Informatica LLC in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners.

Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights reserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All rights reserved. Copyright © Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright © Meta Integration Technology, Inc. All rights reserved. Copyright © Intalio. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © Adobe Systems Incorporated. All rights reserved. Copyright © DataArt, Inc. All rights reserved. Copyright © ComponentSource. All rights reserved. Copyright © Microsoft Corporation. All rights reserved. Copyright © Rogue Wave Software, Inc. All rights reserved. Copyright © Teradata Corporation. All rights reserved. Copyright © Yahoo! Inc. All rights reserved. Copyright © Glyph & Cog, LLC. All rights reserved. Copyright © Thinkmap, Inc. All rights reserved. Copyright © Clearpace Software Limited. All rights reserved. Copyright © Information Builders, Inc. All rights reserved. Copyright © OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo Communications, Inc. All rights reserved. Copyright © International Organization for Standardization 1986. All rights reserved. Copyright © ej-technologies GmbH. All rights reserved. Copyright © Jaspersoft Corporation. All rights reserved. Copyright © International Business Machines Corporation. All rights reserved. Copyright © yWorks GmbH. All rights reserved. Copyright © Lucent Technologies. All rights reserved. Copyright (c) University of Toronto. All rights reserved. Copyright © Daniel Veillard. All rights reserved. Copyright © Unicode, Inc. Copyright IBM Corp. All rights reserved. Copyright © MicroQuill Software Publishing, Inc. All rights reserved. Copyright © PassMark Software Pty Ltd. All rights reserved. Copyright © LogiXML, Inc. All rights reserved. Copyright © 2003-2010 Lorenzi Davide, All rights reserved. Copyright © Red Hat, Inc. All rights reserved. Copyright © The Board of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright © EMC Corporation. All rights reserved. Copyright © Flexera Software. All rights reserved. Copyright © Jinfonet Software. All rights reserved. Copyright © Apple Inc. All rights reserved. Copyright © Telerik Inc. All rights reserved. Copyright © BEA Systems. All rights reserved. Copyright © PDFlib GmbH. All rights reserved. Copyright © Orientation in Objects GmbH. All rights reserved. Copyright © Tanuki Software, Ltd. All rights reserved. Copyright © Ricebridge. All rights reserved. Copyright © Sencha, Inc. All rights reserved. Copyright © Scalable Systems, Inc. All rights reserved. Copyright © jQWidgets. All rights reserved. Copyright © Tableau Software, Inc. All rights reserved. Copyright© MaxMind, Inc. All Rights Reserved. Copyright © TMate Software s.r.o. All rights reserved. Copyright © MapR Technologies Inc. All rights reserved. Copyright © Amazon Corporate LLC. All rights reserved. Copyright © Highsoft. All rights reserved. Copyright © Python Software Foundation. All rights reserved. Copyright © BeOpen.com. All rights reserved. Copyright © CNRI. All rights reserved.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and/or other software which is licensed under various versions of the Apache License (the "License"). You may obtain a copy of these Licenses at http://www.apache.org/licenses/. Unless required by applicable law or agreed to in writing, software distributed under these Licenses is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the Licenses for the specific language governing permissions and limitations under the Licenses.

This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software copyright © 1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under various versions of the GNU Lesser General Public License Agreement, which may be found at http:// www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose.

The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine, and Vanderbilt University, Copyright (©) 1993-2006, all rights reserved.

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution of this software is subject to terms available at http://www.openssl.org and http://www.openssl.org/source/license.html.

This product includes Curl software which is Copyright 1996-2013, Daniel Stenberg, <[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; https://code.google.com/p/lz4/; https://github.com/jedisct1/libsodium/blob/master/LICENSE; http://one-jar.sourceforge.net/index.php?page=documents&file=license; https://github.com/EsotericSoftware/kryo/blob/master/license.txt; http://www.scala-lang.org/license.html; https://github.com/tinkerpop/blueprints/blob/master/LICENSE.txt; http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html; https://aws.amazon.com/asl/; https://github.com/twbs/bootstrap/blob/master/LICENSE; https://sourceforge.net/p/xmlunit/code/HEAD/tree/trunk/LICENSE.txt; https://github.com/documentcloud/underscore-contrib/blob/master/LICENSE, and https://github.com/apache/hbase/blob/master/LICENSE.txt.

This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and Distribution License (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php), the Sun Binary Code License Agreement Supplemental License Terms, the BSD License (http:// www.opensource.org/licenses/bsd-license.php), the new BSD License (http://opensource.org/licenses/BSD-3-Clause), the MIT License (http://www.opensource.org/licenses/mit-license.php), the Artistic License (http://www.opensource.org/licenses/artistic-license-1.0) and the Initial Developer’s Public License Version 1.0 (http://www.firebirdsql.org/en/initial-developer-s-public-license-version-1-0/).

This product includes software copyright © 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this software are subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab. For further information please visit http://www.extreme.indiana.edu/.

This product includes software Copyright (c) 2013 Frank Balluffi and Markus Moeller. All rights reserved. Permissions and limitations regarding this software are subject to terms of the MIT license.

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

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

NOTICES

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

1.THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

Part Number: MDM-JDG-97100-HF6-0001

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

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Informatica Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Informatica Product Availability Matrixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Informatica Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Informatica Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 1: Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10MDM Multidomain Edition Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Designing the MDM Hub Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2: Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Verify License Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Verify the Minimum System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Install Java Development Kit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Set Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Set the Operating System Locale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Set Up the X Window Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Verify the JDBC Driver Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Install and Configure IBM DB2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Create the Hub Store Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Install DB2 Run-Time Client and Catalog the DB2 Database. . . . . . . . . . . . . . . . . . . . . . . 16

Hub Store Tablespaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Manually Create the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Use a Script to Create the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Create Packages on the Database Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Install and Configure JBoss. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Disabling Remoting-Connector Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Configure JBoss for Informatica Data Director. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Create a JBoss Cluster and Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Starting JBoss On UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Start JBoss On Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Install and Configure Cleanse Engines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Create an Installation Documentation Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4 Table of Contents

Chapter 3: Hub Store Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Create the MDM Hub Master Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Create an Operational Reference Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Import the Seed into the MDM Hub Master Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Import the Seed into the Operational Reference Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 4: Hub Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Installing the Hub Server in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Installing the Hub Server in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Installing the Hub Server in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Configuring the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Sample Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Installing and Deploying the Hub Server on Nodes in the Cluster. . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 5: Hub Server Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Copy the Installation Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Installation Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Installation Prerequisites Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Debug Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Post-Installation Setup Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Hub Server Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

JBoss Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Verify the Version and Build Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configure the Hub Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Deploying the Hub Server EAR File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Configuring the Logging Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Setting the Configuration Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Changing the JBoss Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Running the Post Install Script Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Manually Deploying the Hub Server Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Manually Configuring JMS Message Queues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Step 1. Create a Connection Factory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Step 2. Create a JMS Message Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Step 3. Verify the JMS Message Queue Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Step 4. Add a Message Queue Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Step 5. Add a Message Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Repackaging Custom JAR Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configure JBoss Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Configuring an EJB Client for the Hub Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Starting the Hub Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Registering an Operational Reference Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Table of Contents 5

Configuring JBoss Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 6: Process Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Installing the Process Server in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Installing the Process Server in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Installing the Process Server in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Configuring the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Sample Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Installing and Deploying the Process Server on Nodes in the Cluster. . . . . . . . . . . . . . . . . . . . 68

Chapter 7: Process Server Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Copy the Installation Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Installation Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Post-Installation Setup Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Process Server Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Debug Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Installation Prerequisites Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

JBoss Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Verify the Version and Build Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Configure the Process Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Deploying the Process Server EAR File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Configuring the Process Server with Cleanse Engines. . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Configuring the Process Server to Delete Temporary Files. . . . . . . . . . . . . . . . . . . . . . . . 72

Configuring the Logging Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Setting the Configuration Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Running the PostInstallSetup Script Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Manually Redeploying the Process Server EAR File. . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Configure Process Server for Multithreading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Configuring the Process Server for Multithreading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Configuring Multiple Process Servers for Cleanse and Match Operations. . . . . . . . . . . . . . . . . . 75

Configuring Multiple Process Servers for Batch Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Configure Match Population. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Enabling Match Population. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Chapter 8: Troubleshooting the MDM Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Troubleshooting the Installation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Chapter 9: Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Uninstallation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Uninstalling the Hub Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Uninstalling the Process Server in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Uninstalling the Process Server in Graphical Mode On UNIX. . . . . . . . . . . . . . . . . . . . . . . 82

6 Table of Contents

Uninstalling the Process Server in Graphical Mode On Windows. . . . . . . . . . . . . . . . . . . . 82

Uninstalling the Hub Server in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Uninstalling the Hub Server in Graphical Mode on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . 83

Uninstalling the Hub Server in Graphical Mode on Windows. . . . . . . . . . . . . . . . . . . . . . . 83

Uninstalling the Process Server in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Uninstalling the Hub Server in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Manually Undeploying the Process Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Manually Undeploying the Hub Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Table of Contents 7

PrefaceThe 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 NetworkInformatica Network hosts Informatica Global Customer Support, the Informatica Knowledge Base, and other product resources. To access Informatica Network, visit https://network.informatica.com.

As a member, you can:

• Access all of your Informatica resources in one place.

• Search the Knowledge Base for product resources, including documentation, FAQs, and best practices.

• View product availability information.

• Review your support cases.

• Find your local Informatica User Group Network and collaborate with your peers.

Informatica Knowledge BaseUse the Informatica Knowledge Base to search Informatica Network for product resources such as documentation, how-to articles, best practices, and PAMs.

To access the Knowledge Base, visit https://kb.informatica.com. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team at [email protected].

Informatica DocumentationTo get the latest documentation for your product, browse the Informatica Knowledge Base at https://kb.informatica.com/_layouts/ProductDocumentation/Page/ProductDocumentSearch.aspx.

If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through email at [email protected].

8

HTTPS://NETWORK.INFORMATICA.COM/

http://kb.informatica.com

mailto:[email protected]

https://kb.informatica.com/_layouts/ProductDocumentation/Page/ProductDocumentSearch.aspx


Informatica Product Availability MatrixesProduct Availability Matrixes (PAMs) indicate the versions of operating systems, databases, and other types of data sources and targets that a product release supports. If you are an Informatica Network member, you can access PAMs at https://network.informatica.com/community/informatica-network/product-availability-matrices.

Informatica VelocityInformatica Velocity is a collection of tips and best practices developed by Informatica Professional Services. 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 are an Informatica Network member, you can access Informatica Velocity resources at https://velocity.informatica.com.

If you have questions, comments, or ideas about Informatica Velocity, contact Informatica Professional Services at [email protected].

Informatica MarketplaceThe Informatica Marketplace is a forum where you can find solutions that augment, extend, or enhance your Informatica implementations. By leveraging any of the hundreds of solutions from Informatica developers and partners, you can improve your productivity and speed up time to implementation on your projects. You can access Informatica Marketplace at https://marketplace.informatica.com.

Informatica Global Customer SupportYou can contact a Global Support Center by telephone or through Online Support on Informatica Network.

To find your local Informatica Global Customer Support telephone number, visit the Informatica website at the following link: http://www.informatica.com/us/services-and-training/support-services/global-support-centers.

If you are an Informatica Network member, you can use Online Support at http://network.informatica.com.

Preface 9

https://network.informatica.com/community/informatica-network/product-availability-matrices

https://velocity.informatica.com


https://marketplace.informatica.com

http://www.informatica.com/us/services-and-training/support-services/global-support-centers/

http://network.informatica.com

C H A P T E R 1

Installation OverviewThis chapter includes the following topics:

• MDM Multidomain Edition Installation, 10

• Installation Tasks, 11

• Designing the MDM Hub Installation, 11

MDM Multidomain Edition InstallationMDM 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 MDM Hub Master Database. You can access and manage Operational Reference Stores from the MDM Hub Master Database. The default name of the 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 Stores for different geographies, different organizational departments, and for the development and production environments. You can distribute Operational Reference Stores 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 revalidate, and performs data cleansing and match operations. The Process Server is deployed in an application server environment. The Process Server interfaces with the cleanse engine that you configure to standardize and optimize data for match and consolidation.

10

Installation TasksYou 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.

Designing the MDM Hub InstallationBefore you install the MDM Hub, you must decide how to set up the components of the Informatica MDM Hub implementation. All the components of the MDM Hub implementation must have the same version. If you have multiple versions of the MDM Hub, install each version in a separate environment.

You can install the MDM Hub in multiple environments, such as development, test, and production. The requirements and priorities for each type of environment is unique. Therefore, the installation design differs for each environment.

The following examples show some ways in which the MDM Hub components can be set up in an MDM Hub implementation:

All components on a single host

You can install all the MDM Hub components on a single host machine. This environment simplifies communication among the components.

Installation Tasks 11

The following figure shows all MDM Hub components installed on a single host:

Components distributed on multiple hosts

You can distribute the installation of the MDM Hub components on multiple host machines.

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

12 Chapter 1: Installation Overview

C H A P T E R 2

Pre-Installation TasksThis chapter includes the following topics:

• Verify License Key, 13

• Verify the Minimum System Requirements, 13

• Install Java Development Kit, 14

• Set Environment Variables, 14

• Set the Operating System Locale, 14

• Set Up the X Window Server, 15

• Verify the JDBC Driver Version, 15

• Install and Configure IBM DB2, 15

• Install and Configure JBoss, 22

• Install and Configure Cleanse Engines, 25

• Create an Installation Documentation Directory, 25

Verify License KeyBefore 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 RequirementsBefore 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:

13

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 Informatica Network: https://network.informatica.com/community/informatica-network/product-availability-matrices/overview

Install Java Development KitIf you are installing the Informatica MDM Hub on AIX, install a supported version of Java Development Kit (JDK).

Set Environment VariablesSet 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.

Set the Operating System LocaleYou 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

14 Chapter 2: Pre-Installation Tasks

https://network.informatica.com/community/informatica-network/product-availability-matrices/overview

Set Up the X Window ServerWhen 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.

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”export display

DISPLAY=”10.1.50.23:0”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.

Verify the JDBC Driver VersionEnsure that the correct version of the JDBC driver file is present in the lib directory in the MDM Hub distribution.

The lib directory is in the following location:

On UNIX. <distribution directory>/database/lib

On Windows. <distribution directory>\database\lib

For information about supported JDBC driver versions, see the Product Availability Matrix on the Informatica My Support Portal:

https://mysupport.informatica.com/community/my-support/product-availability-matrices

Install and Configure IBM DB2You must install and configure IBM DB2 before you create the Hub Store. Install IBM DB2 according to instructions in the IBM DB2 documentation.

You must install the following software on every machine on which you will run the Hub Server:

• DB2 client

Set Up the X Window Server 15

• DB2 Java utilities for the DB2 client

Create the Hub Store UsersTo access the Hub Store, create users in the IBM DB2 environment.

u Create users for the following Hub Store components:

• MDM Hub Master Databases.

• Operational Reference Stores.

Install DB2 Run-Time Client and Catalog the DB2 DatabaseIf you install the Process Server on a machine other than the IBM DB2 database machine, you need the DB2 Run-Time Client.

1. Install the DB2 Run-Time Client on each machine on which the Process Server and the application server will be installed.

2. Calalog the IBM DB2 database from each DB2 client.

Hub Store TablespacesYou need to create tablespaces for the Hub Store.

The following table describes the tablespaces that the Hub Store requires:

Tablespace Description

CMX_DATA Default tablespace for the Operational Reference Store schema.

CMX_INDX Tablespace to contain indexes that the MDM Hub creates and uses.

CMX_TEMP Tablespace to contain temporary tables that the MDM Hub creates and uses.

CMX_REPOS Tablespace to contain the Operational Reference Store objects.

CMX_USER_TEMP Temporary tablespace to contain operational temporary tables.

CMX_SYS_TEMP Temporary tablespace for SQL operations.

Manually Create the DatabaseThe MDM Hub distribution includes a script to create the database. If you need to create the database manually, ensure that you meet all requirements.

Ensure that you create the database with the compatibility vector turned on and with the UTF-8 TERRITORY US locale.


Set Environment and Registry VariablesIf you create the database manually, set the environment and registry variables that the MDM Hub requires.

Use the following commands to set the environment and registry variables:

db2set DB2CODEPAGE=1208db2set DB2_COMPATIBILITY_VECTOR=db2set DB2_DEFERRED_PREPARE_SEMANTICS=YESdb2set DB2_RESTORE_GRANT_ADMIN_AUTHORITIES=ONdb2set DB2_HASH_JOIN=YESdb2set DB2_ANTIJOIN=YESdb2set DB2_INLIST_TO_NLJN=NOdb2set DB2_SELECTIVITY=ALLdb2set DB2_SKIPINSERTED=YESdb2set DB2_SKIPDELETED=YESdb2set DB2_EXTENDED_OPTIMIZATION=ON,ENHANCED_MULTIPLE_DISTINCT,IXOR,SNHDdb2set DB2NTNOCACHE=ONdb2set DB2_REDUCED_OPTIMIZATION=REDUCE_LOCKING

Set the Database Manager Configuration for the Database InstanceYou need to optimize the database manager configuration for the database instance.

Use the following commands to optimize the database manager configuration:

db2 update dbm cfg using MON_HEAP_SZ AUTOMATICdb2 update dbm cfg using JAVA_HEAP_SZ 2048db2 update dbm cfg using AGENT_STACK_SZ 256db2 update dbm cfg using SHEAPTHRES 0db2 update dbm cfg using INTRA_PARALLEL YES

Note: The values specified in the commands are minimum requirements for the MDM Hub.

Set Database Configuration ParametersSet the configuration parameters for the database.

Use the following commands to set the database configuration parameters:

db2 update db cfg using LOCKLIST AUTOMATICdb2 update db cfg using MAXLOCKS AUTOMATICdb2 update db cfg using PCKCACHESZ 128000db2 update db cfg using DBHEAP AUTOMATICdb2 update db cfg using CATALOGCACHE_SZ 25000db2 update db cfg using LOGBUFSZ 4096db2 update db cfg using UTIL_HEAP_SZ 50000db2 update db cfg using BUFFPAGE 250db2 update db cfg using STMTHEAP AUTOMATICdb2 update db cfg using APPLHEAPSZ AUTOMATICdb2 update db cfg using APPL_MEMORY AUTOMATICdb2 update db cfg using STAT_HEAP_SZ AUTOMATICdb2 update db cfg using LOGFILSIZ 128000db2 update db cfg using LOGPRIMARY 10db2 update db cfg using LOGSECOND 200db2 update db cfg using auto_reval deferred_forcedb2 update db cfg using decflt_rounding round_half_updb2 update db cfg using SHEAPTHRES_SHR AUTOMATICdb2 update db cfg using DFT_DEGREE 1

Note: The values specified in the commands are minimum requirements for the MDM Hub.

Install and Configure IBM DB2 17

Grant Privileges to SYSIBMADM ModulesYou must grant privileges to UTL_DIR, UTL_FILE, and DBMS_SQL SYSIBMADM modules.

Use the following commands to grant privileges to modules:

GRANT EXECUTE ON MODULE SYSIBMADM.UTL_DIR TO PUBLIC WITH GRANT OPTIONGRANT EXECUTE ON MODULE SYSIBMADM.UTL_FILE TO PUBLIC WITH GRANT OPTIONGRANT EXECUTE ON MODULE SYSIBMADM.DBMS_SQL TO PUBLIC WITH GRANT OPTION

Define Buffer Pools for the Database ManagerDefine the REPOS_POOL and CMX_POOL buffer pools.

Use the following commands to define buffer pools:

CREATE BUFFERPOOL REPOS_POOL IMMEDIATE SIZE 1500 PAGESIZE 32 KCREATE BUFFERPOOL CMX_POOL IMMEDIATE SIZE 3000 PAGESIZE 32 K

Create TablespacesYou need to create tablespaces that the Hub Store requires.

Create the tablespaces in the following sequence:

1. CMX_DATA

2. CMX_INDX

3. CMX_REPOS

4. CMX_TEMP

5. CMX_USER_TEMP

6. CMX_SYS_TEMP

Use the following commands to create tablespaces for the Hub Store:

CREATE TABLESPACE CMX_DATA PAGESIZE 32 K MANAGED BY DATABASE USING ( FILE 'c:\dbhub9x\CMX_DATA\cmx_data01.dat' 500 M ) EXTENTSIZE 16 AUTORESIZE YES OVERHEAD 10.5 PREFETCHSIZE 16 BUFFERPOOL CMX_POOL DROPPED TABLE RECOVERY ON

CREATE TABLESPACE CMX_INDX PAGESIZE 32 K MANAGED BY DATABASE USING ( FILE 'c:\dbhub9x\CMX_INDX\cmx_indx01.dat' 500 M ) EXTENTSIZE 16 AUTORESIZE YES OVERHEAD 10.5 PREFETCHSIZE 16 BUFFERPOOL CMX_POOL DROPPED TABLE RECOVERY ON

CREATE TABLESPACE CMX_REPOS PAGESIZE 32 K MANAGED BY DATABASE USING ( FILE 'c:\dbhub9x\CMX_REPOS\cmx_repos01.dat' 500 M ) EXTENTSIZE 16 AUTORESIZE YES OVERHEAD 10.5 PREFETCHSIZE 16 BUFFERPOOL REPOS_POOL DROPPED TABLE RECOVERY ON

CREATE TABLESPACE CMX_TEMP PAGESIZE 32 K MANAGED BY DATABASE USING ( FILE 'c:\dbhub9x\CMX_TEMP\cmx_temp01.dat' 500 M ) EXTENTSIZE 16 AUTORESIZE YES


OVERHEAD 10.5 PREFETCHSIZE 16 BUFFERPOOL CMX_POOL DROPPED TABLE RECOVERY ON

CREATE USER TEMPORARY TABLESPACE CMX_USER_TEMP PAGESIZE 32 K MANAGED BY DATABASE USING ( FILE 'c:\dbhub9x\USER_TEMP\cmx_user_temp01.dat' 500 M ) EXTENTSIZE 16 AUTORESIZE YES OVERHEAD 10.5 PREFETCHSIZE 16 BUFFERPOOL CMX_POOL

CREATE SYSTEM TEMPORARY TABLESPACE CMX_SYS_TEMP PAGESIZE 32 K MANAGED BY DATABASE USING ( FILE 'c:\dbhub9x\SYSTEM_TEMP\cmx_sys_temp01.dat' 500 M ) EXTENTSIZE 16 AUTORESIZE YES OVERHEAD 10.5 PREFETCHSIZE 16 BUFFERPOOL CMX_POOL

Create the Database Proxy RoleIf you want to create an Operational Reference Store (ORS) with multiple users, create the database proxy role. The default ORS user name is the same as the ORS name. After you create the ORS, you can assign the proxy role to an ORS user with a custom user name.

1. Open an IBM DB2 command window.

2. To connect to the database, run the following command: db2 connect to <database name> user <database user> using <database user password>

3. To create the database proxy role, run the following command: db2 CREATE ROLE PROXY_ROLE

Grant Access to the Database Proxy RoleIf you created the database proxy role, grant the proxy role access to control permissions. To create and drop base objects, the database proxy role needs access to control permissions.


2. To connect to the database, run the following command: db2 CONNECT TO <database name> USER <database user> USING <database user password>

3. To grant the proxy role access to control permissions, run the following command: db2 GRANT ACCESSCTRL ON DATABASE TO ROLE PROXY_ROLE;

Grant Privileges to the Custom Operational Reference Store UserAfter you create the database proxy role, and grant access to control permissions to the proxy role, grant permissions to the custom Operational Reference Store (ORS) user.


2. To connect to the database, run the following command: db2 CONNECT TO <database name> USER <database user> USING <database user password>

3. To grant permissions to the custom ORS user, run the following commands: GRANT CONNECT ON DATABASE TO USER <custom ORS user name>GRANT BINDADD ON DATABASE TO USER <custom ORS user name>


GRANT CREATETAB ON DATABASE TO USER <custom ORS user name>GRANT CREATE_EXTERNAL_ROUTINE ON DATABASE TO USER <custom ORS user name>GRANT CREATE_NOT_FENCED_ROUTINE ON DATABASE TO USER <custom ORS user name>GRANT EXECUTE ON PROCEDURE SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS(VARCHAR(30),VARCHAR(128),VARCHAR(128)) TO USER <custom ORS user name>GRANT ROLE PROXY_ROLE TO <custom ORS user name>GRANT CREATEIN,DROPIN,ALTERIN ON SCHEMA ors_schema_name TO USER <custom ORS user name>GRANT LOAD ON DATABASE TO USER <custom ORS user name>GRANT USE OF TABLESPACE CMX_DATA TO USER <custom ORS user name> GRANT USE OF TABLESPACE CMX_INDX TO USER <custom ORS user name> GRANT USE OF TABLESPACE CMX_REPOS TO USER <custom ORS user name> GRANT USE OF TABLESPACE CMX_TEMP TO USER <custom ORS user name> GRANT USE OF TABLESPACE CMX_USER_TEMP TO USER <custom ORS user name> GRANT USE OF TABLESPACE SYSTOOLSPACE TO USER proxy_user_name GRANT EXECUTE ON MODULE SYSIBMADM.UTL_DIR TO USER <custom ORS user name> GRANT EXECUTE ON MODULE SYSIBMADM.UTL_FILE TO USER <custom ORS user name>

Use a Script to Create the DatabaseThe MDM Hub distribution includes a script to create the database and associated tablespaces. You can choose to use the script or manually create the database and associated tablespaces.

On UNIX, before you create the database, update the db2.storage.path property in the database.properties file with the correct database storage path. The database.properties file is in the following directory:

<distribution directory>/database/bin/db2

1. Open a command prompt.

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

On UNIX. <distribution directory>/database/binOn Windows. <distribution directory>\database\bin

3. To create the database, run the following command:

On UNIX. sip_ant.sh create_dbOn Windows. sip_ant.bat create_db

4. Answer the prompts described in the following table:

Prompt Description

Enter the database type (ORACLE, MSSQL, DB2)

Database type. Specify DB2.

Enter the database instance name [db2]

Name of the database instance. Default is db2.

Enter the database name [SIP97]

Name of the database. Default is SIP97.

Enter the database storage path [C:\DB2DATA]

Path to the directory where database must be stored. Default is C:\DB2DATA.Note: On UNIX, accept the default value. The database storage path that you specify in the database.properties file will be used.


Prompt Description

Enter the DBA user name [DB2ADMIN]

User name of the administrative user. Default is DB2ADMIN.

Enter the DBA password Password of the administrative user.

Create the database proxy role [y/n] [y]

Specifies whether you want to create the database proxy role.Enter one of the following values:- y. Creates a database proxy role. If you want to create multiple Operational

Reference Store (ORS) users, you need to create a database proxy role.- n. Database proxy role is not created. If you want to create a single ORS user,

you do not need a database proxy role.Default is y.

The script creates the database and the following tablespaces:

• CMX_DATA

• CMX_INDX

• CMX_TEMP

• CMX_REPOS

• CMX_USER_TEMP

• CMX_SYS_TEMP

To verify that the database was created successfully, review sip_ant.log in the following directory:

On UNIX. <distribution directory>/database/bin

On Windows. <distribution directory>\database\bin

Create Packages on the Database ServerYou can create packages on the database server by connecting to it and using the bind command.


2. Navigate to the following directory:

On UNIX. <IBM DB2 install dir>/SQLLIB/bndOn Windows. <IBM DB2 install dir>\SQLLIB\bnd

3. Use the following command to connect to the database: db2 connect to <database name> user <database user> using <database user password>

Note: The database user must have the bind permission.

4. Use the following bind command: db2 bind @db2cli.lst blocking all grant public sqlerror continue CLIPKG 10

The required packages are created.


Install and Configure JBossInstall 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. Configure the full profile in the standalone-full.xml for non-clustered environments. Configure the full high availability profile in the standalone-full-ha.xml file for clustered environments.

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

Ensure that you perform the following configurations:

• Add -Djava.net.preferIPv4Stack=true when you set up JBoss specific properties, JAVA_OPTS in the following file if the operating system uses Internet Protocol version 6 (IPv6):

On UNIX. <JBoss_install_dir>/bin/standalone.confOn Windows. <JBoss_install_dir>\bin\standalone.conf.bat The following sample shows the setting:

# Set up JBoss specific properties JAVA_OPTS="-Dprogram.name=$PROGNAME -Djava.net.preferIPv4Stack=true $JAVA_OPTS"

• Add -Ddb2.jcc.charsetDecoderEncoder=3 when you set up JBoss specific properties, JAVA_OPTS in the following file to use the MDM Hub Sample Operational Reference Store:

On UNIX. <JBoss_install_dir>/bin/standalone.conf.shOn Windows. <JBoss_install_dir>\bin\standalone.conf.bat The following sample shows the setting:

# Set up JBoss specific propertiesset "JAVA_OPTS=%JAVA_OPTS% -Ddb2.jcc.charsetDecoderEncoder=3"

• In multi-node and clustered environments, 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.

Ensure that each node binds to its own network interface.

• 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 -Xmx4096m -XX:PermSize=256m -XX:MaxPermSize=1024mThe -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 one of the following files:

- standalone-full.xml. For non-clustered environments.

- standalone-full-ha.xml. For clustered environments.

The files are in the following directory:

On UNIX. <JBoss_install_dir>/standalone/configurationOn Windows. <JBoss_install_dir>\standalone\configuration

The default is 300.

The following sample shows the setting:<profile>...


<subsystem xmlns="urn:jboss:domain:transactions:1.4"> <core-environment> <process-id> <uuid/> </process-id> </core-environment> <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/> <coordinator-environment default-timeout="3600"/> </subsystem> ...</profile>

• In clustered environments, verify the following settings in the standalone-full-ha.xml file:

- Protocol stack

- JGroups default stack based on the protocol stack that is set

Disabling Remoting-Connector SecurityYou 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 one of the following files in a text editor:

• standalone-full.xml. For non-clustered environments.

• standalone-full-ha.xml. For clustered environments.

The files are in the following directory:

On UNIX. <Jboss installation directory>/standalone/configurationOn Windows. <Jboss installation directory>\standalone\configuration

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=<"security realm name">/></subsystem>

Configure JBoss for Informatica Data DirectorIf 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 following file in a text editor:

• standalone-full.xmlThe file is in the following directory:

On UNIX. <Jboss installation directory>/standalone/configurationOn Windows. <Jboss installation directory>\standalone\configuration

2. To configure asynchronous handling for the logger, under <subsystem xmlns="urn:jboss:domain:logging:1.2">, add the following XML code:

<async-handler name="ASYNC"> <level name="INFO"/> <queue-length value="1024"/>

Install and Configure JBoss 23

<overflow-action value="BLOCK"/> <subhandlers> <handler name="FILE"/> <handler name="CONSOLE"/> </subhandlers> </async-handler>

3. To configure asynchronous handling for the root logger, under <subsystem xmlns="urn:jboss:domain:logging:1.2">, add the <handler name="ASYNC"/> XML element.

The following sample code shows the configuration:<root-logger> <level name="INFO"/> <handlers> <handler name="ASYNC"/> </handlers> </root-logger>

4. Restart the application server.

Create a JBoss Cluster and NodesYou 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. Navigate to the following directory:

On UNIX. <JBoss installation directory>/binOn Windows. <JBoss installation directory>\bin

3. Run the following command to start JBoss on each machine on which cluster nodes exist:

On UNIX. standalone.sh -Djboss.server.base.dir=../<node path> -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=<port offset value> -Djboss.node.name=<Name of the cluster node> -b 0.0.0.0 -Djboss.partition.name=<Partition name>On Windows. standalone.bat -Djboss.server.base.dir=../<node path> -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=<port offset value> -Djboss.node.name=<Name of the cluster node> -b 0.0.0.0 -Djboss.partition.name=<Partition name>Set the port offset value if multiple cluster nodes run on the same machine. Use the default partition name or ensure that the partition name is the same for all nodes that belong to a cluster.

Starting JBoss On UNIXStart the JBoss application server before you install the Hub Server and the Process Server.

1. Go to the following directory:

JBoss_install_dir/bin2. Run the following command:

standalone.sh -c standalone-full.xml -b 0.0.0.0JBoss starts and listens on the available network interfaces for the current host that are defined in the hosts file in the following directory:

/etc/hosts


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


JBoss_install_dir\bin2. Run the following command:

standalone.bat -c standalone-full.xml -b 0.0.0.0JBoss starts and listens on the available network interfaces for the current host that are defined in the hosts file in the following directory:

C:\WINDOWS\system32\drivers\etc\hosts

Install and Configure Cleanse EnginesInstall 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.

Create an Installation Documentation DirectoryCreate 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.

Install and Configure Cleanse Engines 25

C H A P T E R 3

Hub Store InstallationThis chapter includes the following topics:

• Create the MDM Hub Master Database, 26

• Create an Operational Reference Store, 27

• Import the Seed into the MDM Hub Master Database, 29

• Import the Seed into the Operational Reference Store, 30

Create the MDM Hub Master DatabaseAfter you install IBM DB2, you must create an MDM Hub Master Database. The default name of the MDM Hub Master Database is CMX_SYSTEM.

Note: Do not change the folder names in the distribution directory.

1. Disconnect database connections.




4. To create the MDM Hub Master Database, run the following command:

On UNIX. sip_ant.sh create_systemOn Windows. sip_ant.bat create_system


Prompts Description



Enter the database host name [localhost] Name of the host that is running the database. Default is localhost.

Enter the database port number [50000] Port number that the database listener uses. Default is 50000.

26

Prompts Description

Enter the database instance name [SIP97]

Name of the database instance. Default is SIP97.

Enter the MDM Hub Master Database schema name [cmx_system]

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

Enter the MDM Hub Master Database user name [cmx_system]

User name to access the MDM Hub Master Database. Defaut is cmx_system.

Enter the MDM Hub Master Database user password

Password to access the MDM Hub Master Database.

Enter the DBA user name [DB2ADMIN] User name of the administrative user. Default is DB2ADMIN.


Use the database proxy role [y/n] [y] Specifies whether you want to use the database proxy role that you create when you perform the pre-installation tasks.Enter one of the following values:- y. Uses the database proxy role.- n. Database proxy role is not used.Default is y.

Note: The prompt displays default text in brackets. Press Enter to use the default value and go to the next prompt.

To verify that the MDM Hub Master Database was created successfully, review sip_ant.log in the following directory:



Create an Operational Reference StoreAfter you install IBM DB2, you must create an Operational Reference Store. The default name of the Operational Reference Store is CMX_ORS.


1. Disconnect database connections.




4. Run the following command:

On UNIX. sip_ant.sh create_orsOn Windows. sip_ant.bat create_ors

Create an Operational Reference Store 27


Prompts Description



Enter the Operational Reference Store schema host name [localhost]

Name of the host that is running the database. Default is localhost.

Enter the Operational Reference Store schema port number [50000]

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

Enter the Operational Reference Store database instance name [SIP97]

Name of the database instance. Default is SIP97.

Enter the Operational Reference Store schema name [cmx_ors]

Name of the Operational Reference Store database. Default is cmx_ors.

Enter the Operational Reference Store schema user name [cmx_ors]

User name to access the Operational Reference Store. Default is cmx_ors.

Enter the Operational Reference Store schema user password

Password to access the Operational Reference Store.

Enter the DBA user name [DB2ADMIN] User name of the administrative user. Default is DB2ADMIN.




To verify that the Operational Reference Store was created successfully, review sip_ant.log in the following directory:



28 Chapter 3: Hub Store Installation

Import the Seed into the MDM Hub Master DatabaseAfter you create the MDM Hub Master Database, import the seed into the MDM Hub Master Database. The seed contains the initial metadata such as REPOS tables, and other objects that the MDM Hub requires in the Hub Store.






On UNIX. sip_ant.sh import_systemOn Windows. sip_ant.bat import_system


Prompts Description



Enter the database host name [localhost] Name of the host that is running the database.

Enter the database port number [50000] Port number that the database listener uses. Default is 50000.

Enter the database instance name [SIP97] Name of the database. Default is SIP97.

Enter the MDM Hub Master Database schema name [cmx_system]

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

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

User name to access the MDM Hub Master Database. Default is cmx_system.Note: On UNIX, ensure that you use a user name with 8 characters or less.

Enter the MDM Hub Master Database schema user password

Password to access the MDM Hub Master Database.

Enter locale name [en_US] Operating system locale. Default is en_US. Default is en_US.

Import the Seed into the MDM Hub Master Database 29

Prompts Description

Connect URL [jdbc:db2://localhost:50000/SIP97:currentSchema=CMX_SYSTEM;]

Connect URL for IBM DB2. Default is jdbc:db2://localhost:50000/SIP97:currentSchema=CMX_SYSTEM.



5. After you import the seed, review the following log files for errors:

• seed.log. Contains database errors.The seed.log file is in the following directory:

On UNIX. <distribution directory>/database/bin/db2On Windows. <distribution directory>\database\bin\db2

• sip_ant.log. Contains user input errors.The sip_ant.log file is in the following directory:


Import the Seed into the Operational Reference Store

After you create the Operational Reference Store, import the seed into the Operational Reference Store. The seed contains the initial metadata such as REPOS tables, and other objects that the MDM Hub requires in the Hub Store.






On UNIX. sip_ant.sh import_orsOn Windows. sip_ant.bat import_ors

30 Chapter 3: Hub Store Installation


Prompts Description



Enter the Operational Reference Store schema host name [localhost]

Name of the host that is running the database.

Enter the Operational Reference Store schema port number [50000]

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

Enter the database name [SIP97] Name of the database. Default is SIP97.

Enter the Operational Reference Store schema name [cmx_ors]

Name of the Operational Reference Store database. Default is cmx_ors.

Enter the Operational Reference Store schema user name [cmx_ors]

User name to access the Operational Reference Store. Default is cmx_ors.

Enter the Operational Reference Store schema user password

Password to access the Operational Reference Store.

Enter locale name [en_US] Operating system locale. Default is en_US.

Enter the integer code of Operational Reference Store Timeline Granularity: Year 5, Month 4, Day 3, Hour 2, Minute 1, Second 0 [3]

Specify timeline units to use. Default is days.Note: The timeline granularity that is once configured cannot be modified.



5. After you import the seed, review the following log files for errors:

• seed.log. Review for database errors.The seed.log file is in the following directory:

On UNIX. <distribution directory>/database/bin/db2On Windows. <distribution directory>\database\bin\db2

• sip_ant.log. Review for errors that relate to the values you provide to import the seed.The sip_ant.log file is in the following directory:


Import the Seed into the Operational Reference Store 31

C H A P T E R 4

Hub Server InstallationThis chapter includes the following topics:

• Installing the Hub Server in Graphical Mode, 32

• Installing the Hub Server in Console Mode, 34

• Installing the Hub Server in Silent Mode, 36

• Installing and Deploying the Hub Server on Nodes in the Cluster, 40

Installing the Hub Server in Graphical ModeYou 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>/mrmserverOn Windows. <distribution directory>\windows\mrmserver


On UNIX. hub_install.binOn 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.

32

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 IBM DB2 UDB 9, and click Next.

The DB2 Database Information window appears.

15. Enter the following settings for the IBM DB2 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.

Database Name Name of the database that you created.

System Schema Name of the MDM Hub Master Database.

Installing the Hub Server in Graphical Mode 33


System Schema User Name

The IBM DB2 database user that you use to access the system schema.Note: Use the same user that you used to import seed into the MDM Hub Master Database.

System Schema Password

Password of the user used to connect to the system schema.

The Product Usage Toolkit window appears.

16. On the Product Usage Toolkit page, select the Environment Type.

17. If you have a proxy server, select Yes, and enter the proxy server details. Otherwise, select No.

You can enter the following proxy server details:

• Proxy server name/IP

• Proxy server port

• Proxy server domain name. Leave blank if not applicable.

• Proxy server user name. Leave blank if not applicable.

• Proxy server password. Leave blank if not applicable.

18. Click Next.

The Deploy page appears.

19. To run the post install script during the installation, select Yes, run the script during this installation. To manually run the script later, select No, I will run it later.

The Pre-Installation Summary window appears.

20. After the Pre-Installation Summary window displays the options you want, click Install to start the installation process.

When the installation completes, the Install Complete window appears.

21. Click Done to exit the Hub Server installer.

Installing the Hub Server in Console ModeYou can install the Hub Server in console mode on UNIX.


2. Navigate to the following directory in the MDM Hub distribution:

On UNIX. <distribution directory>/<operating system name>/mrmserver3. Run the following command from the command prompt:

./hub_install.bin -i console4. 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.

34 Chapter 4: Hub Server Installation

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.

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 DB2, and press Enter.

17. Specify the settings for the DB2 database to which you want to connect.

Press Enter to accept the default values, or replace the defaults with the correct values.

The following table describes the prompts:

Prompt Description





Installing the Hub Server in Console Mode 35

Prompt Description





18. Press Enter.


19. From the Product Usage Toolkit options, select the environment type. Type 1 for Production, type 2 for Test/QA, or type 3 for Development, and then press Enter.

20. Select whether you have a proxy server. Press Enter for Yes. Otherwise, type 2 for No and then press Enter.







The summary of the installation choices appears.

21. Choose whether you want to run the postInstallSetup script as part of the installation, or run it manually later.

22. Press Enter.


23. 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 information appears.

24. Press Enter to exit the installer.

Installing the Hub Server in Silent ModeYou 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 FileInformatica 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/mrmserverOn Windows. \silent_install\mrmserverAfter you customize the file, re-save it. You can rename the file and put it anywhere on the machine.

Note: In the silent properties file, slash and backslash are special characters. You must enter two of each of these characters when you enter information in the file, such as when you enter an installation path. For example, to enter the path to the server directory, you must enter \\u1\\infamdm\\hub\\server.

2. Create a backup copy of the silentInstallServer_sample.properties file.

3. Use a text editor to open the file and change the values of the installation parameters.

4. Save the properties file with a new name such as silentInstallServer.properties.

The following table describes the installation parameters that you can modify:

Property Name Description

INSTALLER_UI Specifies the type of installation. Set to silent.

USER_INSTALL_DIR Directory where you want to install Hub Server.For example, C\:\\<infamdm_install_directory>\\hub\\server.

SIP.LICENSE.PATH Path to the Informatica license file.

SIP.LICENSE.FILENAME License file name. Set to siperian.license.

SIP.AS.CHOICE Name of the application server. Specify 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.DB.CHOICE Name of the database server. Specify DB2.

SIP.DB.SERVER Host name of the database server.

Installing the Hub Server in Silent Mode 37


SIP.DB.PORT Database server port number.

SIP.DB.DBNAME Name of the database instance.

SIP.DB.SCHEMA_NAME Schema name of the MDM Hub Master Database.

SIP.DB.USER Database user name.The IBM DB2 database user that you use to access the system schema.Note: Use the same user that you used to import seed into the MDM Hub Master Database.

SIP.DB.PASSWORD Password of the user used to connect to the system schema.

SIP.DB.URL Connect URL to the DB2 Service. Specified only if SIP.DB2.CONNECTION.TYPE is "Service Name" and you want to use a Connect URL that differs from the one constructed in the database creation script. Otherwise, remove this variable from the file.

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.

CSM_TYPE The type of product usage toolkit installation. Can be Production, Test, or Development. Default is Production.

CSM_HOST Name of the proxy server host. Leave blank if the environment does not have a proxy server.

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

CSM_DOMAIN Name of the proxy server domain. Leave blank if the environment does not have a proxy server or if the domain name is not required.

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

CSM_PROXY_PASSWORD Proxy server password. Leave blank if the environment does not have a proxy server or if the proxy server password is not required.

Sample Properties FileThe 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 filenameSIP.LICENSE.PATH=C\:\\SIP.LICENSE.FILENAME=siperian.license


## Properties for JBoss application serverSIP.AS.CHOICE="JBoss"SIP.AS.HOME=C\:\\jboss-eap-6.1.0\\jboss-eap-6.1JBOSS.AS.PORT_1=4447SIP.JBOSS.CONFIGURATION_NAME=standalone

## Properties for IBM DB2 serverSIP.DB.CHOICE="DB2"SIP.DB.SERVER=localhostSIP.DB.PORT=50000SIP.DB.DBNAME=INFAMDMSIP.DB.SCHEMA_NAME=cmx_systemSIP.DB.USER=DB2ADMINSIP.DB.PASSWORD=!!cmx!!

## 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 postInstallSetupRUN_DEPLOYMENT_FLAG=1

#Product Usage Toolkit Installation#CSM_TYPE is the type of Product Usage Toolkit installation.# valid values are:Production,Test,Development. Should not be blank.CSM_TYPE=Production

# If the network haa a proxy server, fill in the following parameters (leave empty if no proxy):# proxy server hostCSM_HOST=# proxy server portCSM_PORT=# Proxy server domain name (leave blank, if not applicable)CSM_DOMAIN=# Proxy server user name (leave blank, if not applicable)CSM_PROXY_USER_NAME=#Proxy server password (leave blank, if not applicable)CSM_PROXY_PASSWORD=

Running the Silent InstallerAfter you configure the properties file, you can start the silent installation.

1. Ensure that the application server is running.

2. Open a command window.


On UNIX. ./hub_install.bin -f <location_of_silent_properties_file_for_hub_server>On Windows. hub_install.exe -f <location_of_silent_properties_file_for_hub_server>The silent installer runs in the background. The process can take a while. If you ran the postInstallSetup script for the Hub Server as part of the silent installation, check the postinstallSetup.log files to verify that the installation was successful.

The log file is available in the following directory:On UNIX. <infamdm_install_directory>/hub/server/logs/On Windows. <infamdm_install_directory>\hub\server\logs\

Installing the Hub Server in Silent Mode 39

Installing and Deploying the Hub Server on Nodes in the Cluster

If you have a clustered environment, install the Hub Server on all the nodes of the cluster to which you must deploy the Hub Server application. You must complete the installation on one node of a cluster before you proceed to install on another node of a cluster.

For example, a JBoss cluster has two nodes that run in host1 and host2 and use RMI ports 4447 and 4448. You need to install the Hub Server on node1 and node2. You must complete the Hub Server installation on any one node, such as node2, before you start installation on the other node, node1.

Ensure that the directory structure of the Hub Server installation is the same on all the nodes.

1. Run the following command to start the JBoss application server on each cluster node machine:

On UNIX. <JBoss installation directory>/bin/standalone.sh -c standalone-full.xml -b 0.0.0.0 -Djboss.as.management.blocking.timeout=700 -u <multicast address> -Djgroups.bind_addr=<bind address> -Djboss.node.name=<node name> -Djboss.server.base.dir=../<node path>On Windows. <JBoss installation directory>\bin\standalone.bat -c standalone-full.xml -b 0.0.0.0 -Djboss.as.management.blocking.timeout=700 -u <multicast address> -Djgroups.bind_addr=<bind address> -Djboss.node.name=<node name> -Djboss.server.base.dir=../<node path>

2. Open a command prompt, and navigate to the following directory:

On UNIX. <distribution directory>/<operating system name>/mrmserverOn Windows. <distribution directory>\windows\mrmserver

3. To start the Hub Server installer on a cluster node, run the following command:

On UNIX. ./hub_install.binOn Windows. hub_install.exe



5. Click Next.



The Choose an Install Folder window appears.

7. Select the location of the Hub Server installation.


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




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.







a. Specify the application server installation directory, and then click Next.


b. Enter standalone, and then click Next.



c. Specify the remote port of the cluster node that is running on the machine.

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 IBM DB2 UDB 9, and click Next.

The DB2 Database Information window appears.

15. Enter the following settings for the IBM DB2 database to which you want to connect, and click Next:

The following table describes the configuration parameter fields:










16. Select a connection URL customization option, and click Next.






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





19. Click Next.


20. Select the Yes, run the script during this installation post installation setup script option.

The Yes, run the script during this installation option runs the post installation setup script during the installation.

21. Click Next.


22. After the Pre-Installation Summary window displays the options you want, click Install to start the installation process.


23. Click Done to exit the Hub Server installer.

24. After the installation, open the cmxserver.properties file on each cluster node.

The cmxserver.properties file is in the following directory:

On UNIX. <infamdm installation directory>/hub/server/resourcesOn Windows. <infamdm installation directory>\hub\server\resources

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

Property Description

jboss.cluster Specify whether EJB servers are clustered for the Hub Server. To enable EJB clustering, set to true.

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.

26. To create a directory named EAR, run the following command:

On UNIX.cd <infamdm install directory>/hub/server/libmkdir ear

On Windows.cd <infamdm install directory>\hub\server\libmkdir ear

27. To repackage the siperian-mrm.ear file, run the following command:

On UNIX.cd <infamdm install directory>/hub/server/binsip_ant.sh repackage

On Windows.cd <infamdm install directory>\hub\server\binsip_ant.bat repackage


28. 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 43

C H A P T E R 5

Hub Server Post-Installation Tasks

This chapter includes the following topics:

• Copy the Installation Log Files, 45

• Verify the Version and Build Number, 47

• Configure the Hub Server, 48

• Running the Post Install Script Manually, 49

• Manually Deploying the Hub Server Application, 50

• Manually Configuring JMS Message Queues, 50

• Repackaging Custom JAR Files, 53

• Configure JBoss Cache, 54

• Configuring an EJB Client for the Hub Console, 55

• Starting the Hub Console, 55

44

• Registering an Operational Reference Store, 56

• Configuring JBoss Security, 58

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

Installation Log FileThe installation log file contains information about the installed files.

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


File Name Informatica_MDM_Hub_Server_Install_<timestamp>.xml

Location On UNIX. <infamdm_install_directory>/hub/server/UninstallerData/LogsOn 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 FileThe installation prerequisites log file contains information about the prerequisite checks that the installer performs.

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


File Name installPrereq.log

Location On UNIX. <infamdm_install_directory>/hub/server/LogsOn Windows. <infamdm_install_directory>\hub\server\Logs

Usage Get information about the prerequisite checks performed by the installer.

Contents Logs of prerequisite validation checks.

Copy the Installation Log Files 45

Debug Log FileThe installer writes actions and errors to the debug log file.

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


File Name infamdm_installer_debug.txt

Location On UNIX. <infamdm_install_directory>/hub/server/On Windows. <infamdm_install_directory>\hub\server\

Usage Get information about the choices that are made during installation.

Contents Detailed summary of actions performed by the installer.

Post-Installation Setup Log FileThe post-installation log file contains information about the post-installation process.

The following table describes the properties of the post-installation setup log file:


File Name postInstallSetup.log

Location On UNIX. <infamdm_install_directory>/hub/server/logsOn 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 FileThe Hub Server log file contains information about Hub Server operations.

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


File Name cmxserver.log

Location On UNIX. <infamdm_install_directory>/hub/server/logsOn Windows. <infamdm_install_directory>\hub\server\logs

Usage Get information about the Hub Server operations.

Contents Summary of the Hub Server operations.

46 Chapter 5: Hub Server Post-Installation Tasks

JBoss Log FileThe JBoss log file contains information about JBoss processes.

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


File Name server.log

Location On UNIX. <JBoss_install_dir>/standalone/logOn 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 NumberYou must ensure that the correct version and build number of the Hub Server is installed.

Perform one of the following steps to verify the Hub Server version and build number:

• Verify the version and build number in the manifest.mf JAR entry in the siperian-mrm.ear file. The siperian-mrm.ear file is in the following directory:On UNIX. <infamdm_install_directory>/hub/serverOn 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/confOn Windows. <infamdm_install_directory>\hub\server\conf

• On UNIX. Run versionInfo.sh that is in the following directory:

<infamdm_install_directory>/hub/server/binOn Windows. Run versionInfo.bat that is in the following directory:

<infamdm_install_directory>\hub\server\bin

Note: For AIX systems, change the versionInfo.sh script to run Java from the <JAVA_HOME>/jre/bin directory.

Verify the Version and Build Number 47

Configure the Hub ServerAfter 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 FileYou 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 SettingsYou 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/confOn 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 PropertiesYou can configure the Hub Server properties in the cmxserver.properties file.

1. Open cmxserver.properties in the following directory:

On UNIX. <infamdm_install_directory>/hub/server/resourcesOn 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\servercmx.server.masterdatabase.type=db2cmx.appserver.type=jbosscmx.appserver.version=7cmx.appserver.web.port=8080cmx.appserver.rmi.port=4447cmx.appserver.naming.protocol=remotecmx.appserver.soap.connector.port=


jnlp.initial-heap-size=128mjnlp.max-heap-size=512mcmx.server.datalayer.cleanse.execution=SERVERcmx.server.datalayer.cleanse.working_files.location=C:\infamdm\hub\server\logscmx.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 SettingsIf 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.

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


2. Navigate to the PostInstallSetup script in the following directory:

On UNIX. <infamdm installation directory>/hub/serverOn Windows. <infamdm installation directory>\hub\server


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>

Running the Post Install Script Manually 49

Manually Deploying the Hub Server ApplicationYou 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 or standalone-full-ha.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 installation directory>/<configuration name>/deploymentsOn Windows.

• <JBoss installation directory>\<configuration name>\deployments3. Copy siperian-mrm.ear from the source to the target directories:

On UNIX.

Source: Hub Server installation directory

Target: <JBoss installation directory>/<configuration name>/deploymentsOn Windows.

Source: Hub Server installation directory

Target: <JBoss installation directory>\<configuration name>\deployments 4. Manually configure JMS and data sources in the standalone-full.xml or standalone-full-ha.xml file

as appropriate.


See the JBoss documentation for more information.

Manually Configuring JMS Message QueuesIf you need to troubleshoot issues, you can manually configure JMS message queues. For example, you might need to manually create message queues if the automated queue creation process fails or if the queues are accidentally dropped after installation.

The Services Integration Framework (SIF) uses a message-driven bean on the JMS message queue to process incoming asynchronous SIF requests. Configure the message queue and the connection factory for the application server that you use for the MDM Hub implementation. When you configure a JMS message queue, you also create a connection factory.

To manually configure the JMS message queue, perform the following tasks:

1. Create a 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 FactoryYou 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 QueueTo 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.

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.


Name

Queue name. Specify java:/queue/<queue name>.

JNDI Names

JNDI Name. Specify java:/queue/<queue name>.

6. Clear the Durable option, and click Save.

The queue is created.

Manually Configuring JMS Message Queues 51

Step 3. Verify the JMS Message Queue ConfigurationYou 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/configurationOn Windows. <JBoss_install_dir>\standalone\configuration

2. Verify the following JMS message queue configuration:

XA connection factory name

java:/siperian.mrm.jms.xaconnectionfactoryJMS queue name

queue/siperian.sif.jms.queue

Step 4. Add a Message Queue ServerBefore 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.


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.

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


2. Click Message Queues under the Configuration workbench.


4. Right-click the message queue server in the middle pane of the Message Queues tool, and then click Add Message Queue.

The Add Message Queue dialog box appears.



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.

Repackaging Custom JAR FilesIf you have custom JAR files, repackage the JAR files in the siperian-mrm.ear file after you install the Hub Server.

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

On UNIX.cd <infamdm_install_directory>/hub/server/libmkdir ear

On Windows.cd <infamdm_install_directory>\hub\server\libmkdir 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/binsip_ant.sh repackage

On Windows.cd <infamdm_install_directory>\hub\server\binsip_ant.bat repackage

Repackaging Custom JAR Files 53

Configure JBoss CacheYou can configure JBoss Cache to handle caching requirements. Modify the JBoss cache properties for tuning performance.

Change the jbossCacheConfig.xml file in the following location to configure JBoss Cache:

On UNIX. <infamdm_install_dir>/hub/server/resources/jbossCacheConfig.xml

On Windows. <infamdm_install_dir>\hub\server\resources\jbossCacheConfig.xml

Change the following properties in the jbossCacheConfig.xml file:

lockAcquisitionTimeout

Increase the value of the property to 60000 or higher, to ensure that the Hub Server acquires a cache object lock.

sync replTimeout

Increase the value of the property to 30000 or higher, to ensure that the Hub Server acquires a cache object lock.

stateRetrieval timeout

Increase the value of the property to 60000, to ensure initial state retrieval.

clustering

Set up the clustering property for a clustered environment.

Set the clusterName attribute to use the same cluster name for all the members of a single cluster.

Ensure that you remove the clustering property for a single node environment.

jgroupsConfig

Set UDP configurations for the property to ensure that there is no conflict between different cluster members.

Set the mcast_addr=<multicast_address> attribute to use the same value for all the members of a single cluster. Use different values for different clusters, or non-clustered MDM Hub Servers on the same network.

Set the mcast_port=<multicast_port> attribute to use the same value for all the members of a single cluster. Use different values for different clusters, or non-clustered MDM Hub servers on the same network.

eviction

Change the eviction time for ReposObjects and DataObjects if there is enough memory and these objects need to remain in memory for a longer duration.

Change the eviction time as shown in the following sample:

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


Configuring an EJB Client for the Hub ConsoleIf 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:


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.

Starting the Hub ConsoleStart 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 the following URL: http://<MDM Hub host>:<port>/cmx/

where <MDM Hub host> is the local Informatica 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 MDM Hub prompts you to select the target database. The target database is the MDM Hub Master Database.

5. Click Connect.

The Hub Console appears.

Configuring an EJB Client for the Hub Console 55

Registering an Operational Reference StoreAfter you create an Operational Reference Store, you must register it. 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.


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.


5. Click the Register database button.

The Informatica MDM Hub Connection Wizard appears and prompts you to select the database type.

6. Select the IBM DB2, and click Next.

7. Configure connection properties for the database.

a. Specify the connection properties, and click Next.

The following table lists and describes the connection properties:


Database Display Name

Name for the Operational Reference Store that must appear in the Hub Console.

Machine Identifier

Prefix given to keys to uniquely identify records from the Hub Store instance.

Database server name

IP address or name of the server that hosts the IBM DB2 database.

Database name Name of the database that you create.

Database hostname

IP address or name of the server that hosts the IBM DB2 database.

Schema Name Name of the Operational Reference Store.



User name User name for the Operational Reference Store. By default, this is the user name that you specify in the script that you use to create the Operational Reference Store. This user owns all the Operational Reference Store database objects in the Hub Store.If a proxy user is configured for the Operational Reference Store, then you can specify the proxy user instead.

Password Password associated with the user name for the Operational Reference Store.For IBM DB2, the password is case sensitive.By default, this is the password that you specify when you create the Operational Reference Store.If a proxy user is configured for the Operational Reference Store, then you specify the password for the proxy user instead.

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.

b. Review the summary, and specify additional connection properties.

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


Connection URL Connect URL. The Connection Wizard generates the connect URL by default. The following example shows the format of the connect URL:

jdbc:db2://database_host:port/db_name

Create datasource after registration

Select to create the datasource on the application server after registration.Note: If you do not select the option, you must manually configure the data source.

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.

Registering an Operational Reference Store 57

Configuring JBoss SecurityYou 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.

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/standalone/configuration/standalone-full.xml

On Windows.<Jboss_install_dir>\jboss-eap-6.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=<"security realm name"> /></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.shOn 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?a) Management User (mgmt-users.properties)b) Application User (application-users.properties)

Specify the option b.

Realm (ApplicationRealm) Specify the name of the security realm. Default 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.

4. Enable JBoss security on the Hub Server.

a. Open cmxserver.properties in the following directory:


b. Uncomment the following property in the cmxserver.properties file:

#cmx.jboss7.security.enabled=trueThe cmxserver.properties file is in the following directory:


5. Run the following command to repackage the siperian-mrm-server.ear file:

On UNIX.cd <infamdm_install_directory>/hub/server/binsip_ant.sh repackage

On Windows.cd <infamdm_install_directory>\hub\server\binsip_ant.bat repackage

6. Deploy the siperian-mrm-server.ear file.

Related Topics:• “Disabling Remoting-Connector Security” on page 23

• “Manually Deploying the Hub Server Application” on page 50

Configuring JBoss Security 59

C H A P T E R 6

Process Server InstallationThis chapter includes the following topics:

• Installing the Process Server in Graphical Mode, 60

• Installing the Process Server in Console Mode, 62

• Installing the Process Server in Silent Mode, 64

• Installing and Deploying the Process Server on Nodes in the Cluster, 68

Installing the Process Server in Graphical ModeYou can install the Process Server in graphical mode.

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.

If you install the Process Server and the Hub Server on the same machine, use the operating system user account that you use for the Hub Server to install the Process Server. Use the root user to install the Process Server only when the root user account is already used for the Hub Server.


2. Open a command prompt and navigate to the Process Server installer in the distribution directory. By default the installer is in the following directory:

On UNIX. <distribution directory>/<operating system name>/mrmcleanseOn Windows. <distribution directory>\windows\mrmcleanse


On UNIX. hub_cleanse_install.binOn Windows. hub_cleanse_install.exe



5. Click Next.



The Choose Install Folder window appears.

7. Select the location of the Process Server installation.

60



Important: Process Server fails to load if the total length of the path exceeds 256 characters or includes spaces in the directory or folder names.



8. Select a location for the product icons, and click Next.

The Enter Location of License File window appears.






a. Specify the path to the JBoss installation directory, and then click Next.


b. Specify the Configuration Name, and then click Next.



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.










16. Click Next.


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

18. Click Next.


Installing the Process Server in Graphical Mode 61

19. After the summary window displays the options you want, click Install to start the installation process.


20. Select Yes, restart my system to restart the system, or select No, I will restart the system myself to restart it later.

21. Click Done to exit the Process Server installer.

After installation, you must perform additional configuration for the cleanse engine according to the instructions in the Informatica MDM Multidomain Edition Cleanse Adapter Guide.

Installing the Process Server in Console ModeYou 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.


2. Navigate to the following directory in the MDM Hub distribution:

On Solaris. <distribution directory>/solaris/mrmcleanseOn HP-UX. <distribution directory>/hpux/mrmcleanseOn Linux. <distribution directory>/linux/mrmcleanseOn 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.

62 Chapter 6: Process Server Installation

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.

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. Click Next.

17. From the Product Usage Toolkit options, select the environment type. Type 1 for Production, type 2 for Test/QA, or type 3 for Development, and then press Enter.

18. Select whether you have a proxy server. Press Enter for Yes. Otherwise, type 2 for No and then press Enter.








19. Choose whether you want to run the postInstallSetup script as part of the installation, or run it manually later.

20. Press Enter.


Installing the Process Server in Console Mode 63

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

22. Press Enter.

The Process Server is installed according to the information you specify, and the install complete information appears.

23. Press Enter to exit the installer.

Installing the Process Server in Silent ModeYou 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.

Configuring the Properties FileInformatica 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/mrmcleanseOn Windows. \silent_install\mrmcleanseNote: 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:


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.

SIP.ADDRESSDOCTOR.SETCONFIGFILE Location of the Address Doctor configuration file if your cleanse engine is Address Doctor.

SIP.ADDRESSDOCTOR.PARAMETERSFILE Location of the Address Doctor parameter file.

SIP.ADDRESSDOCTOR.DEFAULTCORRECTIONTYPE Address Doctor Cleanse Engine correction type. Specify PARAMETERS_DEFAULT.

RUN_DEPLOYMENT_FLAG Runs the postInstallSetup script as part of the silent installation. Set to 1 if you want to run postInstallSetup. Set to 0 if you do not want to run postInstallSetup at the end of the silent installation.

USER_REQUESTED_RESTART Set the property only for the Windows operating system. Specifies whether the operating system needs a restart or not. Default is No.

SIP.FLDIRECT.HOST Host name of FirstLogic.

SIP.FLDIRECT.PORT FirstLogic direct port.

SIP.FLDIRECT.SUBFILE FirstLogic Direct subfile

Installing the Process Server in Silent Mode 65


CSM_TYPE The type of product usage toolkit installation. Can be Production, Test, or Development. Default is Production.

CSM_HOST Name of the proxy server host. Leave blank if the environment does not have a proxy server.

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

CSM_DOMAIN Name of the proxy server domain. Leave blank if the environment does not have a proxy server or if the domain name is not required.

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

CSM_PROXY_PASSWORD Proxy server password. Leave blank if the environment does not have a proxy server or if the proxy server password is not required.

Sample Properties FileThe 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 filenameSIP.LICENSE.PATH=C\:\\SIP.LICENSE.FILENAME=siperian.license

## Properties for JBoss application serverSIP.AS.CHOICE="JBoss"SIP.JBOSS.AS.VERSION=7SIP.AS.HOME=C\:\\jboss-eap-6.1\\jboss-asJBOSS.AS.PORT_1=4447SIP.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.xmlSIP.ADDRESSDOCTOR.PARAMETERSFILE=C\:\\siperian\\hub\\cleanse\\resources\\AddressDoctor\\5\\Parameters.xmlSIP.ADDRESSDOCTOR.DEFAULTCORRECTIONTYPE=PARAMETERS_DEFAULT

## Following FirstLogicDirect properties should be set if you have license for FirstLogicDirect.SIP.FLDIRECT.HOST=localhostSIP.FLDIRECT.PORT=20004SIP.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 postInstallSetupRUN_DEPLOYMENT_FLAG=1

## If you want to restart the operating system as a part of silent install, set following properties to 'YES'.RESTART_NEEDED=NOUSER_REQUESTED_RESTART=NO

#Product Usage Toolkit Installation#CSM_TYPE is the type of Product Usage Toolkit installation.# valid values are:Production,Test,Development. Should not be blank.CSM_TYPE=Production

# If the network haa a proxy server, fill in the following parameters (leave empty if no proxy):# proxy server hostCSM_HOST=# proxy server portCSM_PORT=# Proxy server domain name (leave blank, if not applicable)CSM_DOMAIN=# Proxy server user name (leave blank, if not applicable)CSM_PROXY_USER_NAME=#Proxy server password (leave blank, if not applicable)CSM_PROXY_PASSWORD=

Running the Silent InstallerAfter you configure the properties file, you can start the silent installation.

1. Ensure that the application server is running.

2. Open a command window.


On UNIX. ./hub_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 the Process Server in Silent Mode 67

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


C H A P T E R 7

Process Server Post-Installation Tasks

This chapter includes the following topics:

• Copy the Installation Log Files, 69

• Verify the Version and Build Number, 71

• Configure the Process Server, 72

• Configure Process Server for Multithreading, 74

• Configuring Multiple Process Servers for Cleanse and Match Operations, 75

• Configuring Multiple Process Servers for Batch Processes, 77

• Configure Match Population, 77

Copy the Installation Log FilesThe 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 FileThe installation log file contains information about the installed files.

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


File Name Informatica_MDM_Cleanse_Match_Server_Install_<timestamp>.xml

Location On UNIX. <infamdm_install_directory>/hub/cleanse/UninstallerData/LogsOn Windows. <infamdm_install_directory>\hub\cleanse\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.

69

Post-Installation Setup Log FileThe post-installation log file contains information about the post-installation process.

The following table describes the properties of the post-installation setup log file:


File Name postInstallSetup.log

Location On UNIX. <infamdm_install_directory>/hub/cleanse/logsOn 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 FileThe Process Server log file contains information about the Process Server operations.

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


File Name cmxserver.log

Location On UNIX. <infamdm_install_directory>/hub/cleanse/logsOn Windows. <infamdm_install_directory>\hub\cleanse\logs

Usage Get information about the Process Server operations.

Contents Summary of the Process Server operations.

Debug Log FileThe installer writes actions and errors to the debug log file.

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


File Name infamdm_installer_debug.txt

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

Usage Get information about the choices that are made during installation.

Contents Detailed summary of actions performed by the installer.

70 Chapter 7: Process Server Post-Installation Tasks

Installation Prerequisites Log FileThe installation prerequisites log file contains information about the prerequisite checks that the installer performs.

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


File Name installPrereq.log

Location On UNIX. <infamdm_install_directory>/hub/cleanse/LogsOn 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 FileThe JBoss log file contains information about JBoss processes.

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


File Name server.log

Location On UNIX. <JBoss_install_dir>/standalone/logOn 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 NumberYou 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/cleanseOn 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

Verify the Version and Build Number 71

• On UNIX. Run versionInfo.sh that is in the following directory:

<infamdm_install_directory>/hub/cleanse/binOn 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 ServerAfter you install the Process Server, you need to configure it. You can configure logging settings, and change application server, and Process Server settings.

Deploying the Process Server EAR FileDeploy 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 EnginesAfter 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 FilesYou 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 SettingsYou 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/confOn Windows. <infamdm_install_directory>\hub\cleanse\conf

2. Set the value for the following category names:

• com.siperian

• com.delos

• com.informatica

Set the value of category names to DEBUG for the most detailed logging, INFO for less detailed logging, and ERROR for the least detailed logging. The default is INFO.

3. Set the value for the Threshold parameters to DEBUG.

4. Save and close the file.

Setting the Configuration PropertiesYou 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/resourcesOn 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/logscmx.server.datalayer.cleanse.working_files.location=/u1/infamdm/hub/cleanse/tmpcmx.server.datalayer.cleanse.working_files=KEEPcmx.server.datalayer.cleanse.execution=LOCALcmx.home=/u1/infamdm/hub/cleansecmx.appserver.type=jboss

3. If you do not create the database proxy role for the Hub Store users, add the following properties to the cmxcleanse.properties file:

cmx.server.grant.control=falsecmx.server.grant.ignore=true

The properties ensure that access control is denied to the database proxy users.

4. Save and close the cmxcleanse.properties file.

5. Restart the Process Server application to reload the settings in the file.

Configure the Process Server 73

Running the PostInstallSetup Script ManuallyIf you skipped the post install script during installation, you must run the post install script manually.


2. Navigate to the PostInstallSetup script in the following directory:

On UNIX. <infamdm installation directory>/hub/cleanseOn Windows. <infamdm installation directory>\hub\cleanse


On UNIX. postinstallsetup.shOn Windows. postinstallsetup.bat

Manually Redeploying the Process Server EAR FileYou 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/deploymentsOn Windows. <JBoss_install_dir>\standalone/deployments

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/cleanseOn Windows. <infamdm_install_directory>\hub\cleanse


On UNIX. postinstallsetup.shOn Windows. postinstallsetup.bat

6. Start the JBoss application server.

Configure Process Server for MultithreadingBy 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 MultithreadingUse the Hub Console to configure the Process Server for multithreading.

1. Expand the Utilities workbench in the Hub Console, and then click Process Server.

The Process Server tool displays the configured Process Servers.


3. Select the Process Server for which you must configure multithreading.

4. Click Edit Process Server.

The Process Server tool displays the Add/Edit Process Server dialog box.

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.

Configuring Multiple Process Servers for Cleanse and Match Operations 75

2. Configure multiple application servers.

3. Install and configure the Process Server on each application server.

4. Set the distributed cleanse and match properties in the cmxcleanse.properties file.

The following table describes the distributed cleanse and match properties:


cmx.server.match.distributed_match Specifies whether a Process Server is enabled for distributed cleanse and match. Set to 1 to enable distributed cleanse and match.

cmx.server.cleanse.min_size_for_distribution Specifies the minimum size for distribution. The MDM Hub distributes the cleanse job if the minimum size for distribution is reached. The default is 1,000.

The cmxcleanse.properties is in the following directory:On UNIX. <infamdm_install_directory>/hub/cleanse/resourcesOn 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.

9. Configure properties for each Process Server to enable a distributed cleanse process.

The following table describes the properties to set:


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

Enable Cleanse 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.

The following table describes the properties to set:


Offline Specifies whether a Process Server is online or offline. Disable this property to ensure that a Process Server is online.

Enable Batch 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 PopulationThe 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.

Configuring Multiple Process Servers for Batch Processes 77

http://mysupport.informatica.com

Enabling Match PopulationYou 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/matchOn Windows. <infamdm_install_directory>\hub\cleanse\resources\match

2. In the C_REPOS_SSA_POPULATION metadata table, verify that the population is registered.

The seed database for the MDM Hub installation has some populations registered in the C_REPOS_SSA_POPULATION table, but not enabled.

3. If the C_REPOS_SSA_POPULATION table does not contain the population, add it to the table and enable it.

The population name is the same as the ysp file name. For example, if the ysp file name is US.ysp, the population name is US.To add the population to an Operational Reference Store, use the following steps:

a. Connect to the Operational Reference Store schema that you want to add the population to.

b. In SQL*Plus, run the add_std_ssa_population.sql script in the following directory:

On UNIX. <infamdm_install_directory>/server/resources/database/custom_scripts/oracleOn 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 (example: INFA.0001) DEFAULT [INFA.0001]

Unique value for the ROWID_SSA_POP column of the C_REPOS_SSA_POPULATION metadata table. Default is 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.

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.


C H A P T E R 8

Troubleshooting the MDM HubThis chapter includes the following topic:

• Troubleshooting the Installation Process, 79

Troubleshooting the Installation ProcessIf the installation fails, use the following information to troubleshoot the failure.

Cannot Start JBoss or Launch the Hub Console After InstallationAfter 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

Failed to verify the need to tokenize recordsWhen 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/libOn Windows. <infamdm_install_directory>\hub\cleanse\libThe 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/resourcesOn Windows. <infamdm_install_directory>\server_install_dir>\cleanse\resources

79

major.minor version errors when loading the Process ServerIf 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 exceptionIf 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 XAExceptionWhen you restart JBoss after you install the Hub Server, the following exception might be generated:

javax.transaction.xa.XAExceptionYou can ignore the exception.

Address Doctor exception during certificationAddress 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.shOn Windows. run.bat

3. Set the JAVA_OPTS variable as follows:JAVA_OPTS=${JAVA_OPTS} -Xss2000k

4. Save and close the file.

80 Chapter 8: Troubleshooting the MDM Hub

C H A P T E R 9

UninstallationThis chapter includes the following topics:

• Uninstallation Overview, 81

• Uninstalling the Hub Store, 81

• Uninstalling the Process Server in Graphical Mode, 82

• Uninstalling the Hub Server in Graphical Mode, 83

• Uninstalling the Process Server in Console Mode, 83

• Uninstalling the Hub Server in Console Mode, 84

• Manually Undeploying the Process Server, 84

• Manually Undeploying the Hub Server, 84

Uninstallation OverviewTo 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 StoreYou 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.


2. Click the Databases tool under the Configuration workbench.

The Database Information page appears.

81


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 the command line processor to connect to the IBM DB2 instance.

8. Use the following command for each Hub Store schema to drop the schema: executingdb2 set schema <schema_name>executingdb2 set path <schema_name>

executingdb2 set sqlcompat plsql

executingdb2 -tf@ -vf Clean_DB2_Schema_Progress.sqldb2 -td@ -s -f Clean_DB2_Schema.sqldb2 terminate

If you drop the schemas with the cascade option, the associated schemas are dropped.

Uninstalling the Process Server in Graphical ModeYou can uninstall the Process Server in graphical mode.

Uninstalling the Process Server in Graphical Mode On UNIXTo 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 WindowsTo 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.

82 Chapter 9: Uninstallation

3. Click Uninstall.


4. Click Done.

Uninstalling the Hub Server in Graphical ModeYou can uninstall the Hub Server in graphical mode.

Uninstalling the Hub Server in Graphical Mode on UNIXTo 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.


5. Click Done.

Uninstalling the Hub Server in Graphical Mode on WindowsTo 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.


4. Click Done.

Uninstalling the Process Server in Console ModeYou 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.


<infamdm_install_dir>/hub/cleanse/UninstallerData

Uninstalling the Hub Server in Graphical Mode 83

2. Type the following command to run the uninstaller:

./"Uninstall Informatica MDM Hub Cleanse Match Server"

Uninstalling the Hub Server in Console ModeYou can uninstall the Hub Server in console mode on UNIX. If you installed the Hub Server in console mode, uninstall the Hub Server in console mode.


<infamdm_install_dir>/hub/server/UninstallerData2. Type the following command to run the uninstaller:

./"Uninstall Informatica MDM Hub Server"

Manually Undeploying the Process ServerYou 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/deploymentsOn 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 ServerYou 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/deploymentsOn 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.

84 Chapter 9: Uninstallation

Index

Cconfiguring JBoss

for the MDM Hub 22custom jar files

repackaging 53

Ddatabase

create manually 16create using a script 20

databases target database 55

Eenvironment variables

DISPLAY 15

Ggraphical mode

installation requirements 15

HHub Console

starting 55Hub Server

configuration properties 48deploying on JBoss cluster 40installation log files 45installing 32, 34logging settings 48manually redeploying 50postinstallsetup script 49silent installation 36, 39silent properties file 37uninstalling 84version and build number 47

Hub Store tablespaces 16uninstalling 81

Iinstallation requirements

X Window Server 15installing

Hub Server 32, 34

installing (continued)Process Server 60, 62

JJBoss

clustering on JBoss 24

port conflicts 48settings 49starting on UNIX 24starting on Windows 25

JBoss cache configuring 54eviction 54lockAcquisitionTimeout 54mcast_addr 54mcast_port 54stateRetrieval timeout 54sync replTimeout 54wakeUpInterval 54

JBoss cluster deploying Hub Server 40deploying Process Server 68

JBoss security disabling 23enabling 58

JMS message queues configuring 50

Llog file

debug log file 46, 70Hub Server log file 46installation log file 45, 69installation prerequisites log file 45, 71JBoss log file 47, 71post install setup log file 46, 70Process Server log file 70

MMaster Database

creating 26importing metadata 29

match population enabling 77, 78

MDM Hub components 10designing the installation 11installation tasks 11introduction 10

85

MDM Hub (continued)setting environment variables 14system requirements 13

OOperational Reference Store

creating 27importing metadata 30registering 56

ORS owner role create 19

Ppostinstallsetup script

for Hub Server 49for Process Server 74running 49, 74

Process Server configuration properties 73configuring 72deploying 74deploying on JBoss cluster 68installation log files 69installing 60, 62logging settings 73multithreading, configuring 75postinstallsetup script 74silent installation 64silent properties file 64threads for batch processing 74threads for cleanse operations 74uninstalling 83version and build number 71

Rremoting-connector security

disabling 23enabling 58

Ssilent installation

of Hub Server 39silent installer

running 67

Ttarget database

selecting 55troubleshooting

post-installation process 79

Uuninstalling

Hub Server 84Hub Store 81Process Server 83

XX Window Server

installation requirements 15

86 Index

Documents

Installation Guide for JBoss - kb.informatica.com Documentation/5/MDM… · The Informatica MDM Multidomain Edition Installation Guide is written for database administrators, system