installation guide for jboss documentation...1 • • • • •

Informatica MDM Multidomain Edition for IBM DB2 (Version 10.1 HotFix 1)

Installation Guide for JBoss

Informatica MDM Multidomain Edition for IBM DB2 Installation Guide for JBoss

Version 10.1 HotFix 1April 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-10100-HF1-0001

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

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Informatica My Support Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

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

Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Informatica Support YouTube Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Informatica Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Informatica Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

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

Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Designing the MDM Hub Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 2: Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Read the Release Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Extract the Installer Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Verify License Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Verify the Minimum System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Install Java Development Kit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Set Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Set the Operating System Locale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Set Up the X Window Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Install and Configure IBM DB2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configure IBM DB2 Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Create the Hub Store Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

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

Hub Store Tablespaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Create the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Manually Create the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

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

Update the Alert Configuration Of the Health Indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Create Packages on the Database Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Install and Configure JBoss. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Create a JBoss Cluster and Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Configuring the HTTPS Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4 Table of Contents

Disabling Remoting-Connector Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Configure JBoss for Informatica Data Director. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Configure JBoss for Multiple MDM Hub Master Databases. . . . . . . . . . . . . . . . . . . . . . . . 28

Configure JBoss for Secure ActiveVOS Communication. . . . . . . . . . . . . . . . . . . . . . . . . . 28

Starting JBoss On UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Start JBoss On Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Install and Configure External Cleanse Engines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Determine the Timeline Granularity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Configure the Informatica Platform Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Sample Informatica Platform Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Create an Installation Documentation Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 3: ActiveVOS Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44ActiveVOS Pre-Installation Tasks Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Create an Informatica ActiveVOS Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Editing the ActiveVOS Security Domain in JBoss Environments. . . . . . . . . . . . . . . . . . . . . . . . 45

Create an Administrative User in JBoss Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Configure JBoss for Secure ActiveVOS Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 4: Hub Store Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Create the MDM Hub Master Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Create an Operational Reference Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Import the Metadata into the MDM Hub Master Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Import the Metadata into the Operational Reference Store. . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 5: Hub Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Installing the Hub Server in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

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

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

Configuring the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Sample Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Installing and Deploying the Hub Server on Nodes in a Cluster. . . . . . . . . . . . . . . . . . . . . . . . 64

Chapter 6: Hub Server Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Copy the Installation Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

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

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

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

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

Hub Server Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

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

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

Table of Contents 5

Configure the Hub Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Configuring the Logging Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Setting the Configuration Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Deploying the Hub Server EAR File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Changing the JBoss Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Configure the Hub Server for a JBoss Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Configuring the Hub Server Properties for a JBoss Cluster. . . . . . . . . . . . . . . . . . . . . . . . 73

Repackaging the Hub Server EAR File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Deploying the Hub Server Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Configuring JBoss for Multiple Process Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Running the Post Install Script Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Manually Redeploying the Hub Server Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Manually Creating Data Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Manually Configuring JMS Message Queues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Step 1. Create a Connection Factory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

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

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

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

Step 5. Add a Message Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Improve API Performance on JBoss AS 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Changing the Operational Reference Store User Password. . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Repackaging Custom JAR Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Configure JBoss Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Configure Logging for Informatica Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Starting the Hub Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Registering an Operational Reference Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Configuring JBoss Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Chapter 7: Process Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Installing the Process Server in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

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

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

Configuring the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Sample Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

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

Chapter 8: Process Server Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . 100Copy the Installation Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Installation Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Post-Installation Setup Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Process Server Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Debug Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

6 Table of Contents

Installation Prerequisites Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

JBoss Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Verify the Version and Build Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Configure the Process Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Deploying the Process Server EAR File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

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

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

Configuring the Logging Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Configuring the Process Server Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Running the PostInstallSetup Script Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

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

Configure Process Server for Multithreading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Configuring the Process Server for Multithreading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

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

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

Configure Match Population. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Enabling Match Population. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Chapter 9: ActiveVOS Post-Installation Tasks for the Application Server. . . . . . 111Create a Trusted User in JBoss Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Chapter 10: ActiveVOS Post-Installation Tasks for the Business Entity Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113ActiveVOS Web Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Configuring the ActiveVOS URNs for the Business Entity Workflow Adapter. . . . . . . . . . . . . . . 114

Set the ActiveVOS Protocol to HTTPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Configure Task Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Configure Task Triggers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Setting the Default Approval Workflow for the Entity 360 Framework. . . . . . . . . . . . . . . . . . . . 116

Configure the Primary Workflow Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Generating Business Entity and Business Entity Services Configuration Files. . . . . . . . . . . . . . 118

Configure the MDM Identity Services for ActiveVOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Chapter 11: Resource Kit Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Setting Up the MDM Hub Sample Operational Reference Store. . . . . . . . . . . . . . . . . . . . . . . 119

Registering the Informatica MDM Hub Sample Operational Reference Store. . . . . . . . . . . . . . . 121

Installing the Resource Kit in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Installing the Resource Kit in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Installing the Resource Kit in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Configuring the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Sample Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Table of Contents 7

Chapter 12: Resource Kit Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Validate the MDM Hub Sample Operational Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Chapter 13: Troubleshooting the MDM Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Troubleshooting the Installation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Chapter 14: Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Uninstallation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Uninstalling the Hub Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

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

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

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

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

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

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

Uninstalling the Resource Kit in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Uninstalling the Resource Kit in Graphical Mode on UNIX. . . . . . . . . . . . . . . . . . . . . . . . 137

Uninstalling the Resource Kit in Graphical Mode on Windows. . . . . . . . . . . . . . . . . . . . . 138

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

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

Uninstalling the Resource Kit in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Manually Undeploying the Process Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Manually Undeploying the Hub Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Appendix A: Installation and Configuration Checklist. . . . . . . . . . . . . . . . . . . . . . . . 141Installation Checklist Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Step 1. Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Step 2. Create the Hub Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Step 3. Install the Hub Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Step 4. Hub Server Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Step 5. Install the Process Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Step 6. Process Server Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Step 7. Install the Resource Kit (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

8 Table of Contents

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 My Support PortalAs an Informatica customer, the first step in reaching out to Informatica is through the Informatica My Support Portal at https://mysupport.informatica.com. The My Support Portal is the largest online data integration collaboration platform with over 100,000 Informatica customers and partners worldwide.

As a member, you can:

• Access all of your Informatica resources in one place.

• Review your support cases.

• Search the Knowledge Base, find product documentation, access how-to documents, and watch support videos.

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

Informatica DocumentationThe Informatica Documentation team makes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through email at [email protected]. We will use your feedback to improve our documentation. Let us know if we can contact you regarding your comments.

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

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. You can access the PAMs on the Informatica My Support Portal at https://mysupport.informatica.com/community/my-support/product-availability-matrices.

9

http://mysupport.informatica.com

mailto:[email protected]


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

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

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

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

Informatica Support YouTube ChannelYou can access the Informatica Support YouTube channel at http://www.youtube.com/user/INFASupport. The Informatica Support YouTube channel includes videos about solutions that guide you through performing specific tasks. If you have questions, comments, or ideas about the Informatica Support YouTube channel, contact the Support YouTube team through email at [email protected] or send a tweet to @INFASupport.

Informatica MarketplaceThe Informatica Marketplace is a forum where developers and partners can share solutions that augment, extend, or enhance data integration implementations. By leveraging any of the hundreds of solutions available on the Marketplace, you can improve your productivity and speed up time to implementation on your projects. You can access Informatica Marketplace at http://www.informaticamarketplace.com.

Informatica VelocityYou can access Informatica Velocity at https://mysupport.informatica.com. Developed from the real-world experience of hundreds of data management projects, Informatica Velocity represents the collective knowledge of our consultants who have worked with organizations from around the world to plan, develop, deploy, and maintain successful data management solutions. If you have questions, comments, or ideas about Informatica Velocity, contact Informatica Professional Services at [email protected].

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

Online Support requires a user name and password. You can request a user name and password at http://mysupport.informatica.com.

10 Preface

http://www.informatica.com




http://www.youtube.com/user/INFASupport


http://www.informaticamarketplace.com

https://mysupport.informatica.com



The telephone numbers for Informatica Global Customer Support are available from the Informatica web site at http://www.informatica.com/us/services-and-training/support-services/global-support-centers/.

Preface 11

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

C H A P T E R 1

Installation OverviewThis chapter includes the following topics:

• MDM Multidomain Edition Installation, 12

• Installation Tasks, 14

• Designing the MDM Hub Installation, 14

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 or more MDM Hub Master Databases. You can access and manage an Operational Reference Store from an MDM Hub Master Database. The default name of an MDM Hub Master Database is CMX_SYSTEM.

• Operational Reference Store. Contains the master data, content metadata, and the rules to process and manage the master data. You can configure separate Operational Reference Store databases for different geographies, different organizational departments, and for the development and production environments. You can distribute Operational Reference Store databases across multiple server machines. The default name of an Operational Reference Store is CMX_ORS.

Hub Server

The Hub Server is a J2EE application that you must deploy on an application server. The Hub Server processes data within the Hub Store and integrates the MDM Hub with external applications. The Hub Server is the run-time component that manages core and common services for the MDM Hub.

Process Server

The Process Server processes batch jobs such as load, recalculate BVT, and re-validate, and performs data cleansing and match operations. The Process Server is deployed in an application server

12

environment. The Process Server interfaces with the cleanse engine that you configure to standardize and optimize data for match and consolidation.

Resource Kit

The Resource Kit is a set of samples, applications, and utilities to integrate the MDM Hub into your applications and workflows. You can select the Resource Kit components that you want to install.

Informatica Data Director

Informatica Data Director (IDD) is a data governance tool. Use Informatica Data Director to access the master data that is stored in an Informatica MDM Hub Store. Master data is organized by business entities. Business entities can be any type of top-level data that has significance for an organization, such as customers, suppliers, employees, or accounts. The master data represents the best version of the truth that the organization can achieve about the business entities

Provisioning Tool

You can use the Provisioning tool to create business entity models and configure the Entity 360 framework for Informatica Data Director. To create a business entity model, you create a root node and then establish relationships between nodes. These relationships are based on foreign key constraints that you define using the Hub Console. After you build the business entity model and configure the nodes, you can publish the configuration to the MDM Hub.

Informatica Platform

Comprises the Informatica services and Informatica clients that you use to perform Informatica platform staging. The Informatica services consist of services to support the domain and application services to perform tasks and manage databases. The Informatica domain is the administrative unit for the Informatica environment. You use the clients to access the services in the domain. When you install the Informatica platform as part of the MDM Hub installation, you install the Data Integration Service, Model Repository Service, and Informatica Developer (the Developer tool).

Dynamic Data Masking

Dynamic Data Masking is a data security product that operates between the MDM Hub and a database to prevent unauthorized access to sensitive information. Dynamic Data Masking intercepts requests sent to the database and applies data masking rules to the request to mask the data before it is sent back to the MDM Hub.

Informatica ActiveVOS

Informatica ActiveVOS is a business process management (BPM) tool. BPM tools support automated business processes, including change-approval processes for data. When you combine Informatica ActiveVOS with the MDM Hub and Informatica Data Director, you ensure that changes to master data undergo a review-and-approval process before the data is included in the best version of the truth (BVT) records. When you install ActiveVOS Server as part of the Hub Server installation, you install the ActiveVOS Server, ActiveVOS Console, and Process Central. You also install predefined MDM workflows, tasks, and roles.

Zero Downtime

Zero downtime refers to the ability to maintain access to data in a Hub Store while you upgrade Informatica MDM Multidomain Edition. In a zero downtime environment, you set up duplicate Hub Stores: a source database and a target database. Whenever the data changes in the source database, the changes are replicated to the target database. When you upgrade Informatica MDM Multidomain Edition, you make the target database active while you update the source database. Zero downtime is available for either Oracle databases or IBM DB2 databases. For information about installing a zero downtime environment, see the Informatica MDM Multidomain Edition Zero Downtime (ZDT) Installation Guide for your database.

MDM Multidomain Edition Installation 13

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. Create the following Hub Store components:

• MDM Hub Master Database. You must create the MDM Hub Master Database before you install the Hub Server and the Process Server.

• Operational Reference Store. You can create Operational Reference Stores at any time after you complete the pre-installation tasks.

Use the setup script provided with the MDM Hub distribution to create the components of the Hub Store.

3. Install the Hub Server. Use the MDM Hub installer to install the Hub Server.

4. Install the Process Server. Use the MDM Hub installer to install the Process Server.

5. Perform the post-installation configuration tasks. Test the database connections. To ensure that you can use the MDM Hub features, configure the Hub Server and the Process Server.

Designing the MDM Hub 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.

14 Chapter 1: Installation Overview

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:

Designing the MDM Hub Installation 15

C H A P T E R 2

Pre-Installation TasksThis chapter includes the following topics:

• Read the Release Notes, 16

• Extract the Installer Files, 16

• Verify License Key, 17

• Verify the Minimum System Requirements, 17

• Install Java Development Kit, 18

• Set Environment Variables, 18

• Set the Operating System Locale, 18

• Set Up the X Window Server, 18

• Install and Configure IBM DB2, 19

• Install and Configure JBoss, 24

• Install and Configure External Cleanse Engines, 30

• Determine the Timeline Granularity, 30

• Configure the Informatica Platform Properties File, 31

• Create an Installation Documentation Directory, 43

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

Extract the Installer FilesThe installer files are compressed and distributed.

You need to extract the installer files. Verify that the utility that you use for extraction also extracts empty folders.

16

Download and extract the following installation files from the Informatica Electronic Software Download site to a directory on your machine:

• Download and extract the MDM Hub installer for your operating system.

• Download and extract the database files.

• If you intend to install the licensed version of ActiveVOS Server, download and extract the ActiveVOS Server installer for your operating system.

• If you intend to install Informatica platform, download the Informatica platform server installation files for your operating system.

• If you intend to install Informatica platform, download the Informatica platform client installation files.

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

RAM

Production environment: 12 GB

Development environment: 2 GB minimum, 4 GB recommended

Disk Space

1 GB

To verify that you have sufficient physical memory available to meet the run-time needs of the MDM Hub components that you intend to install, use the following formula:

Total MDM Hub components run-time memory requirement = JDK JVM max heap size of the application server + operating system native heap size

The hardware requirements for an MDM Multidomain Edition implementation are dependent on the data, processing volumes, and business rules.

For more information about product requirements and supported platforms, see the Product Availability Matrix on the Informatica My Support Portal: https://mysupport.informatica.com/community/my-support/product-availability-matrices

Verify License Key 17

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

Install Java Development KitInstall a supported version of the Java Development Kit (JDK) for the MDM Hub installation. The JDK is not bundled with the MDM Hub installers. If you want to install Informatica platform on HP-UX, install the supported version of the JDK. The JDK is not bundled with the Informatica platform installer for HP-UX. The JDK is bundled with the Informatica platform installers for all other platforms.

Set Environment VariablesSet the environment variables before you install the MDM Hub.

Set the JAVA_HOME and PATH environment variables to point to the JDK directory.

If you want to install Informatica platform on AIX or HP-UX, set the INFA_JDK_HOME environment variable to point to the JDK directory.

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

• ES

• pt_BR

Set Up the X Window ServerTo run the installer in graphical mode, use a graphics display server. If you are logged in remotely to a UNIX machine, you can use an X Window server to redirect the graphics display to your local host.

If you do not have a display device installed on the machine where you want to install the product, you can run the installer by using an X Window server installed on another machine. Use the DISPLAY variable to redirect output of the X Window to another machine that has X Window and xterm installed.

18 Chapter 2: Pre-Installation Tasks

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

Shell Command

C setenv DISPLAY <host name>:0

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

Bourne DISPLAY=<host name>:0export display

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

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

Install and Configure 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

• DB2 Java utilities for the DB2 client

Configure IBM DB2 DriversAfter you install IBM DB2, copy the IBM DB2 driver files from the IBM DB2 installation directory to the MDM Hub distribution directory.

Copy the db2jcc.jar and db2jcc_license_cu.jar IBM DB2 driver files from the following directory:

On UNIX. <IBM DB2 installation directory>/java

On Windows. <IBM DB2 installation directory>\java

Copy the IBM DB2 driver files to the following directory:

On UNIX. <distribution directory>/database/lib

On Windows. <distribution directory>\database\lib

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 and Configure IBM DB2 19

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.

Create the DatabaseUse one of the following procedures to create a database:

• Manually create the database

• Use a script to create the database

Manually Create the DatabaseTo 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 the DB2 Environment and DB2 Registry VariablesIf you create the database manually, set the DB2 environment and DB2 registry variables that the MDM Hub requires.

Use the following commands to set the DB2 environment and DB2 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=YES


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

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

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. To run the script, you need administrative privileges with write and execute permissions to the DB2 data directory.

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.

Enter the DBA user name [DB2ADMIN]

User name of the administrative user. Default is DB2ADMIN.

Enter the DBA password Password of the administrative user.


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

Update the Alert Configuration Of the Health IndicatorTo run batch jobs from the Hub Console, the database system monitor data must not run out of memory. You need to update the threshold check configuration of the database system indicator to no for the database instance.

Run the following command to update the database system indicator configuration:

db2 update alert cfg for dbm using db2.mon_heap_util set THRESHOLDSCHECKED no

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

1. Open an IBM DB2 command window.

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.

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


Ensure that you perform the following configurations:

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

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

Attributes Description

-Dorg.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE=16384 The maximum size of the HTTP headers, in bytes. The smart search requests might fail if the header size is low.

-Djava.net.preferIPv4Stack=true Set to true if your operating system uses Internet Protocol version 6 (IPv6).

-Djboss.as.management.blocking.timeout=5000 The time in seconds to wait for JBoss to deploy. If you do not set the value to 5000, JBoss might fail to start. Default is 300.

For example:

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 Installation Directory>/bin/standalone.conf.shOn Windows. <JBoss Installation Directory>\bin\standalone.conf.bat The following sample shows the setting:

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

• To enhance the performance of the MDM Hub environment, add the following JVM option for JIT code cache size to JAVA_OPTIONS in the JBoss startup script:

-XX:ReservedCodeCacheSize=256m• In a multi-node or clustered environment, add the following JVM option to the JBoss startup script:

-Djgroups.bind_addr=<bind_addr>where, <bind_addr> specifies the interface on which to receive and send messages.

You must ensure that each node in the multi-node or clustered environment binds to its own network interface.

• Set the maximum JVM heap size (-Xmx) to 4 GB or higher in the JBoss startup script. Change the following settings:

set "JAVA_OPTS=-server -Xms2048m -Xmx4096m -XX:PermSize=256m -XX:MaxPermSize=1024m -Xss2000k -Dorg.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE=16384 -Dsolr.autoSoftCommit.maxTime=5000"

The -Xmx parameter must be three to four times the size of –XX:MaxPermSize and -XX:PermSize must be one third or one fourth the size of -XX:MaxPermSize.

• Increase the transaction timeout to 3600 in the following file:

- standalone-full.xml

Install and Configure JBoss 25

The file is in the following directory:

On UNIX. <JBoss Installation Directory>/standalone/configurationOn Windows. <JBoss Installation Directory>\standalone\configurationThe 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>

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.


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


Configuring the HTTPS ProtocolYou can configure the HTTPS protocol for the MDM Hub communications. Use the standalone-full.xml file to configure the HTTPS protocol.

1. Use a text editor to open the standalone-full.xml file in the following directory:

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

2. Add the following code: <subsystem xmlns="urn:jboss:domain:web:1.4" default-virtual-server="default-host" native="false"><connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true"><ssl name="ssl" key-alias="<Key alias>" password="<password>" certificate-key-file="<Security certificate key file path>" protocol="TLSv1" verify-client="false"/></connector><virtual-server name="default-host" enable-welcome-root="true"><alias name="Alias name of the virtual host>"/></virtual-server></subsystem>

3. Save and close the file.

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

Configure JBoss for Multiple MDM Hub Master DatabasesIf you want to configure more than one MDM Hub Master Database, you have to install an MDM Hub instance for each MDM Hub Master Database. To install multiple MDM Hub instances on the same machine, deploy each MDM Hub instance on a separate JBoss instance and run each JBoss instance on a different port.

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

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

<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:1}">

Set the port-offset attribute of each JBoss instance to a different value.

• Before you start a JBoss instance, set the JBoss home for the JBoss instance at the command prompt.

• Start the second and any subsequent JBoss instances by running the following command:standalone.bat -c standalone-full.xml -b 0.0.0.0 -Djboss.service.binding.set=ports-01

Configure JBoss for Secure ActiveVOS CommunicationTo use the HTTP Secure (HTTPS) protocol for communication between ActiveVOS and the MDM Hub, you must configure the application server.

This procedure describes one possible way to configure JBoss to use the HTTPS protocol. For alternate methods, see the JBoss documentation.

1. Use the Java keytool command to generate a keystore and an alias. Note the keystore password that you create.

For more information, see the Java documentation.


2. Add the connector configuration to standalone-full.xml.

a. Open the following file in a text editor:

<JBoss installation directory>\standalone\configuration\standalone-full.xmlb. Add the following XML code to standalone-full.xml.

<subsystem xmlns="urn:jboss:domain:web:1.4" default-virtual-server="default-host" native="false"> <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" redirect-port="443"/> <connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" enable-lookups="false" secure="true"> <ssl name="tomcat-ssl" key-alias="tomcat" password="<keystore password>" certificate-key-file="c:\\as\\ssl\\keystore" protocol="TLSv1"/> </connector>

3. Configure JBoss to import the Java Virtual Machine (JVM) certificate.


<JBoss installation directory>\bin\standalone.conf.batb. Add the following command to standalone.conf.bat.

set "JAVA_OPTS=%JAVA_OPTS% -Djavax.net.ssl.trustStore=c:\\as\\ssl\\keystore -Djavax.net.ssl.trustStorePassword=<keystore password>"


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

1. Open a command prompt and go to the following directory:

<JBoss installation directory>/bin2. Run the following command:

standalone.sh -c standalone-full.xml -b 0.0.0.0 -Djboss.as.management.blocking.timeout=700

JBoss starts on the available network interfaces and listens for the current host that is defined in the hosts file in the /etc/hosts directory.

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

1. Go to the following directory:

<JBoss installation directory>\bin2. Run the following command:

standalone.bat -c standalone-full.xml -b 0.0.0.0 -Djboss.as.management.blocking.timeout=700

JBoss starts on the available network interfaces and listens for the current host that is defined in the hosts file in the C:\WINDOWS\system32\drivers\etc\hosts directory.


Install and Configure External Cleanse EnginesIf you intend to use a cleanse engine, such as Address Doctor, to use with the Process Server, install and configure the cleanse engine.

For instructions on how to configure the MDM Hub to integrate with the cleanse engine, see the Informatica MDM Multidomain Edition Cleanse Adapter Guide.

Determine the Timeline GranularityBefore you install the MDM Hub components, determine the timeline granularity. Timeline granularity is the time measurement that you want to use to define effective periods for versions of records. For example, you can choose the effective periods to be in years, months, or seconds.

You can configure the timeline granularity of year, month, day, hour, minute, or seconds to specify effective periods of data in the MDM Hub implementation. You can configure the timeline granularity that you need when you create or update an Operational Reference Store.

Important: The timeline granularity that you configure cannot be changed.

When you specify an effective period in any timeline granularity, the system uses the database time locale for the effective periods. To create a version that is effective for one timeline measurement unit, the start date and the end date must be the same.

The following table lists the timeline granularity that you can configure and the formats:

Timeline Granularity Timeline Format

Year yyyy

Month mm/yyyy

Day dd/mm/yyyy

Hour dd/mm/yyyy hh

Minute dd/mm/yyyy hh:mm

Second dd/mm/yyyy hh:mm:ss

Use one of the following timeline granularity options:

Year

When the timeline granularity is year, you can specify the effective period in the year format, such as 2010. An effective start date of a record starts at the beginning of the year and the effective end date ends at the end of the year. For example, if the effective start date is 2013 and the effective end date is 2014, then the record would be effective from 01/01/2013 to 31/12/2014.

Month

When the timeline granularity is month, you can specify the effective period in the month format, such as 01/2013. An effective start date of a record starts on the first day of a month. The effective end date of a record ends on the last day of a month. For example, if the effective start date is 02/2013 and the effective end date is 04/2013, the record is effective from 01/02/2013 to 30/04/2013.


Day

When the timeline granularity is day, you can specify the effective period in the date format, such as 13/01/2013. An effective start date of a record starts at the beginning of a day, that is 12:00. The effective end date of the record ends at the end of a day, which is 23:59. For example, if the effective start date is 13/01/2013 and the effective end date is 15/04/2013, the record is effective from 12:00 on 13/01/2013 to 23:59 on 15/04/2013.

Hour

When the timeline granularity is hour, the effective period includes the year, month, day and hour, such as 13/01/2013 15. An effective start date of a record starts at the beginning of an hour of a day. The effective end date of the record ends at the end of the hour that you specify. For example, if the effective start date is 13/01/2013 15 and the effective end date is 15/04/2013 10, the record is effective from 15:00 on 13/01/2013 to 10:59 on 15/04/2013.

Minute

When the timeline granularity is minute, the effective period includes the year, month, day, hour, and minute, such as 13/01/2013 15:30. An effective start date of a record starts at the beginning of a minute. The effective end date of the record ends at the end of the minute that you specify. For example, if the effective start date is 13/01/2013 15:30 and the effective end date is 15/04/2013 10:45, the record is effective from 15:30:00 on 13/01/2013 to 10:45:59 on 15/04/2013.

Second

When the timeline granularity is second, the effective period includes the year, month, day, hour, minute, and second, such as 13/01/2013 15:30:45. An effective start date of a record starts at the beginning of a second. The effective end date ends at the end of the second that you specify. For example, if the effective start date is 13/01/2013 15:30:55 and the effective end date is 15/04/2013 10:45:15, the record is effective from 15:30:55:00 on 13/01/2013 to 10:45:15:00 on 15/04/2013.

Configure the Informatica Platform Properties FileIf you want to install Informatica platform as part of the MDM Hub installation, create an Informatica platform properties file. Specify the options for the installation in the properties file, and save the file with the name SilentInput.properties.

1. Open a text editor.

2. Create an Informatica platform properties file in the text editor.

3. Configure the values of the installation parameters.

4. Save the properties file with the name SilentInput.properties.

Configure the following installation parameters:LICENSE_KEY_LOC

Absolute path and file name of the license key file.

USER_INSTALL_DIR

Directory in which to install Informatica.

INSTALL_TYPE

Indicates whether to install or upgrade Informatica.

Configure the Informatica Platform Properties File 31

If the value is 0, the installer performs an installation of Informatica. If the value is 1, the installer upgrades a previous version of Informatica.

ENABLE_USAGE_COLLECTION

Indicates whether to configure Informatica DiscoveryIQ, a product usage tool that sends routine reports on data usage and system statistics to Informatica. You can choose to not send any usage statistics to Informatica.

To configure Informatica DiscoveryIQ to send usage statistics to Informatica, set the parameter to 1. For information about how to disable sending usage statistics, see the Informatica Administrator Guide.

ENABLE_KERBEROS

Indicates whether to configure the Informatica domain to run on a network with Kerberos authentication.

To configure the Informatica domain to run on a network with Kerberos authentication, set the parameter to 1.

SERVICE_REALM_NAME

Name of the Kerberos realm to which the Informatica domain services belong. The service realm name and the user realm name must be the same.

USER_REALM_NAME

Name of the Kerberos realm to which the Informatica domain users belong. The service realm name and the user realm name must be the same.

KEYTAB_LOCATION

Directory where you store all keytab files for the Informatica domain. The name of a keytab file in the Informatica domain must follow a format set by Informatica.

KRB5_FILE_LOCATION

Path and file name of the Kerberos configuration file. Informatica requires krb5.conf name for the Kerberos configuration file.

SPN_SHARE_LEVEL

Indicates the service principal level for the domain. Set the property to one of the following levels:

• Process. The domain requires a unique service principal name (SPN) and keytab file for each node and each service on a node. The number of SPNs and keytab files required for each node depends on the number of service processes that run on the node. Recommended for production domains.

• Node. The domain uses one SPN and keytab file for the node and all services that run on the node. The domain also requires a separate SPN and keytab file for all HTTP processes on the node. Recommended for test and development domains.

Default is process.

HTTPS_ENABLED

Indicates whether to secure the connection to Informatica Administrator. If the value is 0, the installer sets up an unsecure HTTP connection to Informatica Administrator. If the value is 1, the installer sets up a secure HTTPS connection to Informatica Administrator.

DEFAULT_HTTPS_ENABLED

Indicates whether the installer creates a keystore file.

If the value is 1, the installer creates a keystore and uses it for the HTTPS connection. If the value is 0, the installer uses a keystore file that you specify.


CUSTOM_HTTPS_ENABLED

Indicates whether the installer uses an existing keystore file.

If the value is 1, the installer uses a keystore file that you specify. If DEFAULT_HTTPS_ENABLED=1, you must set this parameter to 0. If DEFAULT_HTTPS_ENABLED=0, you must set this parameter to 1.

KSTORE_PSSWD

Plain text password for the keystore file.

KSTORE_FILE_LOCATION

Absolute path and file name of the keystore file.

HTTPS_PORT

Port number to use for the secure connection to Informatica Administrator.

CREATE_DOMAIN

Indicates whether to create an Informatica domain.

If the value is 1, the installer creates a node and an Informatica domain. If the value is 0, the installer creates a node and joins the node to another domain created in a previous installation.

KEY_DEST_LOCATION

Directory in which to store the encryption key on the node created during the installation.

PASS_PHRASE

Keyword to use to create an encryption key to secure sensitive data in the domain. The keyword must meet the following criteria:

• From 8 to 20 characters long

• Includes at least one uppercase letter

• Includes at least one lowercase letter

• Includes at least one number

• Does not contain spaces

JOIN_DOMAIN

Indicates whether to join the node to another domain created in a previous installation.

If the value is 1, the installer creates a node and joins the node to another domain. If CREATE_DOMAIN=1, you must set the parameter to 0. If CREATE_DOMAIN=0, you must set this parameter to 1.

KEY_SRC_LOCATION

Directory that contains the encryption key on the master gateway node of the Informatica domain that you want to join.

SSL_ENABLED

Enables or disables secure communication between services in the Informatica domain.

Indicates whether to set up secure communication between services within the domain. If the value is true, secure communication between services within the domain is enabled. You can set the property to true if CREATE_DOMAIN=1. You must set the property to true if JOIN_DOMAIN=1.

SECURITY_DOMAIN_NAME

Name of the default security domain in the domain to which you join the node you create.


TLS_CUSTOM_SELECTION

Indicates whether to use SSL certificates that you provide to enable secure communication in the Informatica domain.

To use SSL certificates that you provide, set this property to True.

NODE_KEYSTORE_DIR

Required if TLS_CUSTOM_SELECTION is set to True. Directory that contains the keystore files. The directory must contain files named infa_keystore.jks and infa_keystore.pem.

NODE_KEYSTORE_PASSWD

Required if TLS_CUSTOM_SELECTION is set to True. Password for the keystore infa_keystore.jks.

NODE_TRUSTSTORE_DIR

Required if TLS_CUSTOM_SELECTION is set to True. Directory that contains the truststore files. The directory must contain files named infa_truststore.jks and infa_truststore.pem.

NODE_TRUSTSTORE_PASSWD

Required if TLS_CUSTOM_SELECTION is set to True. Password for the infa_truststore.jks file.

SERVES_AS_GATEWAY

Indicates whether to create a gateway or worker node.

If the value is 1, the installer configures the node as a gateway node. If the value is 0, the installer configures the node as a worker node.

DB_TYPE

Database for the domain configuration repository.

Enter one of the following values:

• Oracle

• DB2

• MSSQLServer

DB_UNAME

Database user account name for the domain configuration repository.

DB_PASSWD

Password for the database user account.

DB_SSL_ENABLED

Indicates whether the database for the domain configuration repository is secure. To create the domain configuration repository in a secure database, set this parameter to True. If this parameter is set to True, you must provide the JDBC connection string with the secure database parameters.

TRUSTSTORE_DB_FILE

Path and file name of the truststore file for the secure database.

TRUSTSTORE_DB_PASSWD

Password for the truststore file.

DB2_TABLESPACE

Name of the tablespace in which to create the tables. Specify a tablespace that meets the pageSize requirement of 32768 bytes.


In a single-partition database, if DB2_TABLESPACE is empty, the installer creates the tables in the default tablespace. In a multipartition database, define the tablespace in the catalog partition of the database.

DB_CUSTOM_STRING_SELECTION

Determines whether to use a JDBC URL or a custom connection string to connect to the domain configuration database.

If the value is 0, the installer creates a JDBC URL from the database properties you provide. If the value is 1, the installer uses the custom connection string you provide. If you create the domain configuration repository on a secure database, set the parameter to 1.

DB_SERVICENAME

Required if DB_CUSTOM_STRING_SELECTION=0.

Service name for IBM DB2 databases.

DB_ADDRESS


Host name and port number for the database instance in the format HostName:Port.

ADVANCE_JDBC_PARAM

You can set this parameter if DB_CUSTOM_STRING_SELECTION=0.

Optional parameters to include in the JDBC URL connection string. Verify that the parameter string is valid. The installer does not validate the parameter string before it adds the string to the JDBC URL. If this parameter is empty, the installer creates the JDBC URL without additional parameters.

DB_CUSTOM_STRING


Valid custom JDBC connection string.

DOMAIN_NAME

Name of the domain.

The default domain name is Domain_<MachineName>. The name must not exceed 128 characters and must be 7-bit ASCII. It cannot contain a space or any of the following characters: ` % * + ; " ?

DOMAIN_HOST_NAME

Host name of the machine that hosts the node.

Note: Do not use localhost. The host name must explicitly identify the machine.

NODE_NAME

Required if CREATE_DOMAIN=1.

Name of the node to create on the machine. The node name is not the host name for the machine.

DOMAIN_PORT

If you create a domain, this is the port number for the node to create. The default port number for the node is 6005. If the default port number is not available on the machine, the installer displays the next available port number.

If you join a domain, this is the port number of the gateway node of the domain you want to join.


DOMAIN_USER

User name for the domain administrator.

DOMAIN_PSSWD

Password for the domain administrator. The password must be more than two characters but cannot exceed 16 characters.

DOMAIN_CNFRM_PSSWD

Enter the password again to confirm.

JOIN_NODE_NAME

Required if JOIN_DOMAIN=1.

Name of the node that you are joining to the domain. The node name is not the host name for the machine.

JOIN_HOST_NAME


Host name of the machine on which to create the node that you are joining to the domain. The node host name cannot contain the underscore (_) character.

Note: Do not use localhost. The host name must explicitly identify the machine.

JOIN_DOMAIN_PORT


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

ADVANCE_PORT_CONFIG

Indicates whether to display the list of port numbers for the domain and node components. If the value is 0, the installer assigns default port numbers to the domain and node components. If the value is 1, you can set the port numbers for the domain and node components.

MIN_PORT

You can set this parameter if ADVANCE_PORT_CONFIG=1.

Lowest port number in the range of dynamic port numbers that you can assign to the application service processes that run on the node.

MAX_PORT


Highest port number in the range of dynamic port numbers that you can assign to the application service processes that run on the node.

TOMCAT_PORT


Port number that the Service Manager uses on the node. The Service Manager listens for incoming connection requests on this port. Client applications use this port to communicate with the services in the domain. This is the port that the Informatica command line programs use to communicate to the domain. This is also the port for the SQL data service JDBC/ODBC driver. Default is 6006.

AC_PORT

You can set this parameter if CREATE_DOMAIN=1 and ADVANCE_PORT_CONFIG=1.


Port number that Informatica Administrator uses. Default is 6007.

SERVER_PORT


Port number that controls server shutdown for the domain Service Manager. The Service Manager listens for shutdown commands on this port. Default is 6008.

AC_SHUTDWN_PORT

You can set this parameter if CREATE_DOMAIN=1 and ADVANCE_PORT_CONFIG=1.

Port number that controls server shutdown for Informatica Administrator. Informatica Administrator listens for shutdown commands on this port. Default is 6009.

On Windows, specify whether to run the Informatica service under the same user account as the account used for installation.

Set the following properties if you want to run the Informatica service under a different user account:

USE_LOGIN_DETAILS

Indicates whether to run the Windows service under a different user account. If the value is 0, the installer configures the service to run under the current user account. If the value is 1, the installer configures the service to run under a different user account.

WIN_USER_ID

User account with which to run the Informatica Windows service.

Use the following format:

Domain Name\User AccountThe user account must have the Act as operating system permission.

WIN_USER_PSSWD

Password for the user account with which to run the Informatica Windows service.

Sample Informatica Platform Properties FileThe following example shows the contents of the sample silentInput.properties file:

# Use the sample file SilentInput.properties to install Informatica services without user interaction.# Use the sample properties file to define the parameters for the silent installation.# To upgrade Informatica, use the SilentInput_upgrade.properties or SilentInput_upgrade_NewConfig.properties file.# Use the following guidelines when you edit this file:# Back up the file before you modify it. # Any error condition that causes the installation to fail, such as an installation directory that is not valid, # generates a log file in SYSTEM_DRIVE_ROOT. For example: c:\silentErrorLog.log#######

# The LICENSE_KEY_LOC property represents the absolute path and file name of the license key file.# Set the property if you are installing or upgrading Informatica.

LICENSE_KEY_LOC=c:\license.key

# The USER_INSTALL_DIR property represents the directory in which to install the new version of Informatica.# Set the property if you are installing or upgrading Informatica.


# The property must point to a valid directory with write permissions enabled.USER_INSTALL_DIR=c:\Informatica\9.6.1

# The INSTALL_TYPE property determines whether to install or upgrade Informatica.# Set INSTALL_TYPE=0 to perform a new installation of Informatica. # To upgrade Informatica, use the SilentInput_upgrade.properties file.# To upgrade Informatica to a different node configuration, use the SilentInput_upgrade_NewConfig.properties file.

INSTALL_TYPE=0

# Provide Kerberos Network Authentication parameters:

#Set this property to 1 if you are Enabling KerberosENABLE_KERBEROS=0

#Provide Service realm name.SERVICE_REALM_NAME=

#Provide User realm name.USER_REALM_NAME=#provide KeyTab location.KEYTAB_LOCATION=

#Provide Kerberos configuration file location.KRB5_FILE_LOCATION=

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

SPN_SHARE_LEVEL=

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

HTTPS_ENABLED=0

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

# The CUSTOM_HTTPS_ENABLED property determines whether the installer uses an existing keystore file.# Value 0 Set the property to 0 if DEFAULT_HTTPS_ENABLED=1.# Value 1 Install Informatica using a keystore file that you specify. Set the property to 1 if DEFAULT_HTTPS_ENABLED=0.CUSTOM_HTTPS_ENABLED=0

# The KSTORE_PSSWD property represents the password for the keystore file.# Set the property to the plain text password for the keystore file if CUSTOM_HTTPS_ENABLED=1.

KSTORE_PSSWD=MyKeystorePassword

# The KSTORE_FILE_LOCATION property represents the location of the keystore file.# Set the property to the absolute path and file name of the keystore file if CUSTOM_HTTPS_ENABLED=1.

KSTORE_FILE_LOCATION=c:\MyKeystoreFile


# The HTTPS_PORT property represents the port number to use for the secure connection to Informatica Administrator.

HTTPS_PORT=8443

# The CREATE_DOMAIN property determines whether to create an Informatica domain.# Value 0 Create a node and join the node to another domain created in a previous installation. Set the property to 0 if JOIN_DOMAIN=1.# Value 1 Create a node and an Informatica domain.CREATE_DOMAIN=1

#Please Specify the site key Destination locationKEY_DEST_LOCATION=c:\Informatica\9.6.1\isp\config\keys

#set the property to Pass Phrase, this field needs to set only for CREATE DOMAIN casePASS_PHRASE_PASSWD=

# The JOIN_DOMAIN property determines whether to join the node to another domain created in a previous installation.# Value 0 Create a node and an Informatica domain. Set the property to 0 if CREATE_DOMAIN=1.# Value 1 Create a node and join the node to another domain created in a previous installation. Set the property to 1 if CREATE_DOMAIN=0.JOIN_DOMAIN=0

# Set the property to the site key source location and this needs to set only for JOIN DOMAIN caseKEY_SRC_LOCATION=c:\temp\siteKey

# The SSL_ENABLED property enables or disables Transport Layer Security (TLS).# Set the property to true to enable secure communication between services within the domain.# Set the property to true or false if CREATE_DOMAIN=1. # The property will not be used if JOIN_DOMAIN=1, as the node will get added on the basis of domain security.

SSL_ENABLED=false

# The property SECURITY_DOMAIN_NAME represents the LDAP name for the Kerberos enabled domain# Set the property if JOIN_DOMAIN=1 and ENABLE_KERBEROS=1

SECURITY_DOMAIN_NAME=

##################################################Provide TLS information for domain. Set TLS_CUSTOM_SELECTION equals to true if you want domain level TLS option.

TLS_CUSTOM_SELECTION=false################################ #Below fields are only required when you set TLS_CUSTOM_SELECTION=trueNODE_KEYSTORE_DIR=c:\tempNODE_KEYSTORE_PASSWD=NODE_TRUSTSTORE_DIR=c:\tempNODE_TRUSTSTORE_PASSWD=

# The SERVES_AS_GATEWAY property determines whether to create a gateway or worker node.# Set the property if JOIN_DOMAIN=1.# Value 0 The installer configures the node as a worker node.# Value 1 The installer configures the node as a gateway node.

SERVES_AS_GATEWAY=0

# The DB_TYPE property represents the database type for the domain configuration database.


# Set the property to the database types (case-sensitive): DB2.

DB_TYPE=DB2

# The DB_UNAME property represents the database user account name for the domain configuration repository.

DB_UNAME=UserName

# The DB_PASSWD property represents the database password for the database user account.

DB_PASSWD=UserPassword

# The DB_SSL_ENABLED property represents whether the database is in SSL mode or not.#Set the property to "true" if you want to enable secure communication.# Also if this property is set to true then DB_CUSTOM_STRING_SELECTION property must be set to 1 to use#only custom string option property DB_CUSTOM_STRING which should include the following secure DB parameters:#EncryptionMethod=SSL;HostNameInCertificate=;ValidateServerCertificate= DB_SSL_ENABLED=false

# The TRUSTSTORE_DB_FILE and TRUSTSTORE_DB_PASSWD properties to be set only if enable secure communication #for the DB property i.e DB_SSL_ENABLED=true# Set the TRUSTSTORE_DB_FILE property to the location of the trust store file for the DB# Set the TRUSTSTORE_DB_PASSWD as a password of the trust store file for the DB

TRUSTSTORE_DB_FILE=

TRUSTSTORE_DB_PASSWD=

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

# In join node scenario, when JOIN_DOMAIN=1 # Set this value to empty,for all cases. TRUSTED_CONNECTION=

# The DB2_TABLESPACE property represents the name of the tablespace in which to create the tables.# Set the property if DB_TYPE=DB2.# Specify a tablespace that meets the pageSize requirement of 32768 bytes.# In a single-partition database, if DB2_TABLESPACE is empty, the installer creates the tables in the default tablespace.# In a multi-partition database, define the tablespace in the catalog partition of the database.

DB2_TABLESPACE=

# The DB_CUSTOM_STRING_SELECTION property determines whether to use a JDBC URL or a custom connection string to connect to the domain configuration database.# Set DB_CUSTOM_STRING_SELECTION=1 if TRUSTED_CONNECTION=1. Also provide the default valid connection string in DB_CUSTOM_STRING.# Value 0 The installer creates a JDBC URL from the database properties you provide# Value 1 The installer uses the custom connection string you provide.

DB_CUSTOM_STRING_SELECTION=0


# The DB_SERVICENAME property represents the service name or database name of the database.# Set the property if DB_CUSTOM_STRING_SELECTION=0.# Set the property to the service name for Oracle and IBM DB2 databases.# Set the property to the database name for Microsoft SQL Server and Sybase ASE databases.# Leave the property blank if DB_CUSTOM_STRING_SELECTION=1.

DB_SERVICENAME=DBServiceName

# The DB_ADDRESS property represents the host name and port number for the database instance.# Set the property if DB_CUSTOM_STRING_SELECTION=0.# Set the property in the format HostName:PortNumber.# Leave the property blank if DB_CUSTOM_STRING_SELECTION=1.

DB_ADDRESS=HostName:PortNumber

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

ADVANCE_JDBC_PARAM=

# The DB_CUSTOM_STRING property represents a valid custom JDBC connection string.# Set the property if DB_CUSTOM_STRING_SELECTION=1.

DB_CUSTOM_STRING=

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

DOMAIN_NAME=DomainName

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

DOMAIN_HOST_NAME=HostName

# The NODE_NAME property represents the node to create on the machine. The node name is not the host name for the machine.

NODE_NAME=NodeName

# The DOMAIN_PORT property represents the port number.# * If you create a domain, set the property to the port number for the node to create.# The default port number for the node is 6005.# If the default port number is not available on the machine, the installer displays the next available port number.# * If you join a domain, set the property to the port number of the gateway node of the domain you want to join.

DOMAIN_PORT=

# The DOMAIN_USER property represents the user name for the domain administrator.


# If you create a domain, you can use this user name to initially log in to the Informatica Administrator.# If you join a domain, this is the user name to use to log in to the domain that you want to join.

DOMAIN_USER=AdminUser

# The DOMAIN_PSSWD property represents the password for the domain administrator. # The password must be more than 2 characters but cannot exceed 128 characters.

DOMAIN_PSSWD=

# The DOMAIN_CNFRM_PSSWD property confirms the password you set for the domain administrator.# Set the property to the password you set in the DOMAIN_PSSWD property to confirm the password.

DOMAIN_CNFRM_PSSWD=

# The JOIN_NODE_NAME property represents the name of the node to create on this machine. The node name is not the host name for the machine.# Set the property if JOIN_DOMAIN=1.

JOIN_NODE_NAME=NodeName

# The JOIN_HOST_NAME property represents the host name of the machine that hosts the gateway node of the domain you want to join.# Set the property if JOIN_DOMAIN=1.

JOIN_HOST_NAME=DomainHostName

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

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

ADVANCE_PORT_CONFIG=0

# The MIN_PORT property represents the lowest port number in the range of port numbers that can be assigned to the application service processes that run on this node.# Set the property if ADVANCE_PORT_CONFIG=1.

MIN_PORT=

# The MAX_PORT property represents the highest port number in the range of port numbers that can be assigned to the application service processes that run on this node.# Set the property if ADVANCE_PORT_CONFIG=1.

MAX_PORT=

# The TOMCAT_PORT property represents the port number used by the Service Manager on the node. Default is 6006.# Set the property if ADVANCE_PORT_CONFIG=1.# The Service Manager listens for incoming connection requests on this port. # Client applications use this port to communicate with the services in the domain. # This is the port that the Informatica command line programs use to communicate with the domain. # This is also the port for the SQL data service JDBC/ODBC driver.

TOMCAT_PORT=


# The AC_PORT property represents the port number used by Informatica Administrator. Default is 6007.# Set the property if CREATE_DOMAIN=1 and ADVANCE_PORT_CONFIG=1.

AC_PORT=

# The SERVER_PORT property controls the server shutdown for the domain Service Manager. The Service Manager listens for shutdown commands on this port. Default is 6008.# Set the property if ADVANCE_PORT_CONFIG=1.

SERVER_PORT=

# The AC_SHUTDWN_PORT property represents the port number that controls the server shutdown for Informatica Administrator. Default is 6009.# Set the property if ADVANCE_PORT_CONFIG=1.# Informatica Administrator listens for shutdown commands on this port.

AC_SHUTDWN_PORT= ######## On Windows, set the following properties to specify whether to run the Informatica service under the same user account as the account used for installation.#######

# The USE_LOGIN_DETAILS property determines whether to run the Windows service under a different user account. # Value 0 The installer configures the service to run under the current user account.# Value 1 The installer configures the service to run under a different user account.

USE_LOGIN_DETAILS=0

# The WIN_USER_ID property represents the user account with which to run the Informatica Windows service.# Set the property if USE_LOGIN_DETAILS=1.# The user account must have the "Act as part of the operating system" permission.# Use the format DomainName\UserAccount.

WIN_USER_ID=WindowsUserAcct

# The WIN_USER_PSSWD property represents the password for the user account with which to run the Informatica Windows service.

WIN_USER_PSSWD=WindowsUserPassword

######## After you create the properties file, save the file with the name SilentInput.properties and # run the silent installer to perform the Informatica services installation.#######

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

Create an Installation Documentation Directory 43

C H A P T E R 3

ActiveVOS Pre-Installation TasksThis chapter includes the following topics:

• ActiveVOS Pre-Installation Tasks Overview, 44

• Create an Informatica ActiveVOS Schema, 44

• Editing the ActiveVOS Security Domain in JBoss Environments, 45

• Create an Administrative User in JBoss Environments, 46

• Configure JBoss for Secure ActiveVOS Communication, 47

ActiveVOS Pre-Installation Tasks OverviewBefore you upgrade or install the Hub Server, you must create the ActiveVOS Console administrative user in the application server. Before you install, you can also configure the application server to use the HTTP Secure (HTTPS) protocol for communication between ActiveVOS and the MDM Hub.

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

Create an Informatica ActiveVOS SchemaBefore you run the Hub Server installer, you need to create the ActiveVOS database schema. To create the schema, you run a script.




3. Run the following command:

On UNIX. sip_ant.sh create_bpmOn Windows. sip_ant.bat create_bpm

4. Answer the prompts that appear.

44

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

Note: IBM DB2 datasources are case-sensitive. To avoid issues related to case-sensitivity, Informatica recommends using all uppercase letters when defining names, such as schema names, table names, column names, and trigger names.

Property Description

Database Type Type of database to use. For IBM DB2, specify DB2. The database type must be the same as the database type selected for the MDM Hub Master Database and the Operational Reference Stores.

ActiveVOS Database Host Name Name of the machine that hosts the database.

ActiveVOS Database TCP/IP Port Port number that the database listener uses.

ActiveVOS Database Name Name of the database.

ActiveVOS Database Schema/User Name

User name of the ActiveVOS Server administrative user.

ActiveVOS User Password Password of the administrative user.

DBA User Name User name of the database administrative user.

DBA Password Password of the administrative user.

ActiveVOS Tablespace Name The name of the tablespace that contains the records that are involved in MDM workflows.

5. After you create the schema, review sip_ant.log in the following directory:

On UNIX. <distribution directory>/database/binOn Windows. <distribution directory>\database\binThe sip_ant.log file logs any errors that might occur when you run the sip_ant script to create the ActiveVOS database schema.

Editing the ActiveVOS Security Domain in JBoss Environments

Enable container-based authentication in JBoss.

1. Open standalone-full.xml in an editor.

2. Find the security-domain element for ActiveVOS.

3. Comment out the existing login-module.

4. Add a login-module child element, as shown in the following code:

<security-domain name="ActiveVOS"> <authentication>

Editing the ActiveVOS Security Domain in JBoss Environments 45

<login-module code="RealmUsersRoles" flag="required"> <module-option name="usersProperties" value="${jboss.server.config.dir}/application-users.properties"/> <module-option name="rolesProperties" value="${jboss.server.config.dir}/application-roles.properties"/> <module-option name="realm" value="ApplicationRealm"/> <module-option name="unauthenticatedIdentity" value="anonymous"/> </login-module> </authentication></security-domain>

5. If the JBoss application server is running, restart the server.

Create an Administrative User in JBoss Environments

Create the ActiveVOS Console administrative user with the role of abAdmin in the application server. If you do not create an administrative user, the deployment fails. Use the ActiveVOS Console administrative user name and password when the Hub Server installer prompts you to enter the administrative user credentials for the ActiveVOS Console.

1. From the command prompt, run add-user.bat.

The add-user.bat file is in the following directory

JBoss install directory\bin2. Answer the prompts that appear.

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

What type of user do you wish to add? a) Management User or b) Application User

Enter b to select Application User.

Realm (ApplicationRealm)

Enter the same realm name that you specified in the login-module that you added to the standalone-full.xml file.

Username

Enter the ActiveVOS Console administrator name.

Password

Enter a password that complies with the JBoss password standard.

What roles do you want this user to belong to?

Enter abAdmin.

About to add user <username> for realm <realmname>. Is this correct?

To add the user, enter yes.

46 Chapter 3: ActiveVOS Pre-Installation Tasks

Is this new user going to be used for one AS process to connect to another AS process?

Enter yes.


Configure JBoss for Secure ActiveVOS Communication

To use the HTTP Secure (HTTPS) protocol for communication between ActiveVOS and the MDM Hub, you must configure the application server.

This procedure describes one possible way to configure JBoss to use the HTTPS protocol. For alternate methods, see the JBoss documentation.

1. Use the Java keytool command to generate a keystore and an alias. Note the keystore password that you create.

For more information, see the Java documentation.

2. Add the connector configuration to standalone-full.xml.


<JBoss installation directory>\standalone\configuration\standalone-full.xmlb. Add the following XML code to standalone-full.xml.

<subsystem xmlns="urn:jboss:domain:web:1.4" default-virtual-server="default-host" native="false"> <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" redirect-port="443"/> <connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" enable-lookups="false" secure="true"> <ssl name="tomcat-ssl" key-alias="tomcat" password="<keystore password>" certificate-key-file="c:\\as\\ssl\\keystore" protocol="TLSv1"/> </connector>

3. Configure JBoss to import the Java Virtual Machine (JVM) certificate.


<JBoss installation directory>\bin\standalone.conf.batb. Add the following command to standalone.conf.bat.

set "JAVA_OPTS=%JAVA_OPTS% -Djavax.net.ssl.trustStore=c:\\as\\ssl\\keystore -Djavax.net.ssl.trustStorePassword=<keystore password>"


Configure JBoss for Secure ActiveVOS Communication 47

C H A P T E R 4

Hub Store InstallationThis chapter includes the following topics:

• Create the MDM Hub Master Database, 48

• Create an Operational Reference Store, 50

• Import the Metadata into the MDM Hub Master Database, 51

• Import the Metadata into the Operational Reference Store, 52

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: If you change the folder names in the distribution directory, metadata import fails.




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

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


48

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

Prompts Description


Database type. Specify DB2.Note: DB2 datasources are case-sensitive. To avoid issues related to case-sensitivity, Informatica recommends to use all uppercase letters when you define the schema names, table names, column names, triggers, and so on.

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.

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 locale name from the list: de, en_US, fr, ja, ko, zh_CN. [en_US]

Operating system locale. Default is en_US.

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


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

On UNIX. <distribution directory>/database/binOn Windows. <distribution directory>\database\binThe sip_ant.log file logs any errors that might occur when you run the sip_ant script to create the MDM Hub Master Database.

6. If you intend to configure single sign-on authentication for other applications such as Salesforce, increase the BLOB column length. Run the following command on the MDM Hub Master Database:

SET SCHEMA CMX_SYSTEM; ALTER TABLE C_REPOS_SAM_PROVIDER_FILE ALTER COLUMN PROVIDER_FILE SET DATA TYPE BLOB (10240000); CALL ADMIN_CMD('REORG TABLE C_REPOS_SAM_PROVIDER_FILE');

Create the MDM Hub Master Database 49

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






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



Prompts Description


Database type. Specify DB2.Note: DB2 datasources are case-sensitive. To avoid issues related to case-sensitivity, Informatica recommends using all uppercase letters when defining the MDM databases schema names, table names, column names, triggers, and so on.

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 locale name from the list: de, en_US, fr, ja, ko, zh_CN. [en_US]

Operating system locale.

50 Chapter 4: Hub Store Installation

Prompts Description

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


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

On UNIX. <distribution directory>/database/binOn Windows. <distribution directory>\database\binThe sip_ant.log file logs any errors that might occur when you run the sip_ant script to create the Operational Reference Store.

Import the Metadata into the MDM Hub Master Database

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





3. To import the initial metadata, run the following command:

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.

Import the Metadata into the MDM Hub Master Database 51

Prompts Description

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.

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 initial metadata, review the following log files for errors:

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

On UNIX. <distribution directory>/database/bin/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 Metadata into the Operational Reference Store

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





3. To import the initial metadata, run the following command:

52 Chapter 4: Hub Store Installation

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



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.

Connect URL. [jdbc:db2://<host name>:<port>/<database name>]

Connect URL for the master database. Default is jjdbc:db2://<host name>:<port>/<database name>.

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


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 you configure cannot be modified later.For more information about timeline, see the Informatica MDM Multidomain Edition Configuration Guide.

5. After you import the initial metadata, review the 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 Metadata into the Operational Reference Store 53

C H A P T E R 5

Hub Server InstallationThis chapter includes the following topics:

• Installing the Hub Server in Graphical Mode, 54

• Installing the Hub Server in Console Mode, 57

• Installing the Hub Server in Silent Mode, 59

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

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.

54

Note: The installation fails if you specify a path that has spaces in the directory or folder names.

• To choose another location, click Choose, and then click Next.

8. On UNIX, choose a link folder or select the option to not create links and click Next. On Windows, select the location to create a product icon or select the option not to create a product icon.

9. Click Next.

The Enter the location of the license file window appears.

10. Click Choose to select a license file, and click Next.

The Application Server window appears.

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

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.

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 Install ActiveVOS window appears.

Installing the Hub Server in Graphical Mode 55

16. If you want to install the bundled, licensed version of Informatica ActiveVOS, select Yes and perform the following substeps. Otherwise, select No, and click Next.

a. On the ActiveVOS Installer page, click Choose and browse to the ActiveVOS_Server installation file in the distribution package. Click Next.

b. On the Choose ActiveVOS Installation Folder page, accept the default installation path or specify a preferred location. Click Next.

c. Enter the ActiveVOS database credentials that you specified when you created the ActiveVOS database schema. Click Next.

d. On the Application Server Web URL page, accept the default URL or specify the URL that you want to use to call ActiveVOS web services. Ensure the URL contains the correct port number for the connection to the application server. Click Next.

The post installation setup script uses the URL to call ActiveVOS web services, deploy the predefined MDM workflows to ActiveVOS, and create the URN mapping.

e. Enter the administrative user name and password to create an administrative user for the ActiveVOS Console.

Important: The user name and password must be the same as the ActiveVOS Console user name and password that was created in the application server.

f. Click Next.

17. Select one of the following Informatica platform installation options:

• Yes. Install Informatica platform.

• No. Does not install Informatica platform.

18. If you select Yes in the preceding step, click Choose and browse to the following Informatica platform file locations:

• Installation response file

• Platform installation file

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

20. If you want to use 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.

21. Click Next.

The Deploy page appears.

22. Select one of the following post installation setup script options:

• Yes, run the script during this installation. Runs the post installation script during the installation.

• No, I will run it later. Allows you to manually run the post installation script later.

23. Click Next.

The Pre-Installation Summary window appears.

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

56 Chapter 5: Hub Server Installation

When the installation completes, the Install Complete window appears.

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

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.

Installing the Hub Server in Console Mode 57

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






User belonging to the DB2ADMNS user group 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.



18. Press Enter.

19. If you want to install the bundled, licensed version of the ActiveVOS Server, press Enter for Yes. Otherwise, type 2 for No and press Enter.

If you selected Yes, the installer prompts you to provide information about your ActiveVOS installation.

a. Specify the location of the ActiveVOS Server installation file.

b. Specify the location where you want to install the ActiveVOS Server.

c. Enter information about the ActiveVOS database that you specified when you created the ActiveVOS schema.

d. Specify the URL that you want to use to call MDM and ActiveVOS web services.

e. Enter a user name and password to create an administrative user for the ActiveVOS Server Administration Console.


20. Press Enter.

The Informatica platform installation prompt appears.

21. If you want to install the Informatica platform, press Enter for Yes. Otherwise, type 2 for No and press Enter.

The prompts for the Informatica platform installation response file and archive file locations appear.


22. Enter the locations of the Informatica platform installation response file and archive file, and press Enter.

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

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

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

26. Verify the information in the pre-installation summary. If the information is correct, press Enter to start the installation.

The Hub Server is installed according to the configuration information you provide. When the process is complete, the installation complete message appears.

27. Press Enter to exit the installer.

Installing the Hub Server in 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.

Installing the Hub Server in Silent Mode 59

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 remote port number.

JBOSS.AS.PORT_2 The JBoss native port number.

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

SIP.DB.CHOICE Name of the database server. Specify DB2.

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

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.

AVOS.INSTALL Specifies whether you want to install Informatica ActiveVOS or not.If you want to install Informatica ActiveVOS, set the property to Yes. Otherwise, set to No.

AVOS_INSTALLER_PATH The path to the ActiveVOS Server installer.

AVOS_INSTALL_DIR The path to the location where you want to install the ActiveVOS Server.

AVOS.DB.SERVER Name of the machine that hosts the ActiveVOS database.

AVOS.DB.PORT Port number that the database listener uses.

AVOS.DB.DBNAME Name of the database.

AVOS.DB.SCHEMA_NAME Name of the ActiveVOS schema. Default is AVOS.

AVOS.DB.USER User name of the database administrative user. Default is avos.

AVOS.DB.PASSWORD Password of the administrative user.

SIP.APPSERVER.WEB.URL URL to the application server in the following format:http://[server]:[port]

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

AVOS.CONSOLE.PASSWORD Password of the ActiveVOS server administrator. The password must be the same as the ActiveVOS Console password that was created in the application server during the pre-installation process.

INSTALL.PLATFORM.YES Specifies whether you want to install Informatica platform or not.If you want to install Informatica platform, set the property to 1. Otherwise, set to 0.

INFA.PLATFORM.ZIP Path to the compressed Informatica platform installer.

INFA.PLATFORM.PROPERTIES Path to the Informatica platform installation properties file that you create.



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

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.4.0## JBoss RMI port JBOSS.AS.PORT_1=4447 ## JBoss management native port JBOSS.AS.PORT_2=9999SIP.JBOSS.CONFIGURATION_NAME=standalone

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

## Do you want to install ActiveVOS (Yes/No)


AVOS.INSTALL=Yes## Path to ActiveVOS Installer (ActiveVOS_Server_windows_9.2.4.1.exe for Windows or ActiveVOS_Server_unix_9.2.4.1.sh for Linux/UNIX)AVOS_INSTALLER_PATH=c\:\\ActiveVOS_Server_windows_9.2.4.1.exe## ActiveVOS server install directoryAVOS_INSTALL_DIR=C\:\\infamdm\\avos\\server

## Database type is the same as for HUB (There is no ability to set a different database type for ActiveVOS)

## DB2 connection data#AVOS.DB.SERVER=localhost#AVOS.DB.PORT=50000#AVOS.DB.DBNAME=AVOS#AVOS.DB.SCHEMA_NAME=AVOS#AVOS.DB.USER=avos#AVOS.DB.PASSWORD=!!cmx!!

##If you are moving from standalone ActiveVOS to embedded ActiveVOS, enter the details for the standalone ActiveVOS schema.

SIP.APPSERVER.WEB.URL=http://localhost:8080## Avos console's administrator usernameAVOS.CONSOLE.USER=aeadmin## Avos console's administrator passwordAVOS.CONSOLE.PASSWORD=admin##The user name and password must be the same as the ActiveVOS Console user name and passwordthat was created in the application server during the pre-installation process.

## If you want to install Informatica Platform, set to 1## If you DO NOT want to install Informatica Platform, set to 0INSTALL.PLATFORM.YES=1

## Path to the Informatica Platform installer (zip or tar file)INFA.PLATFORM.ZIP=C\:\\961HF1_Server_Installer_winem-64t.zip## For UNIX: INFA.PLATFORM.ZIP=/export/home/user/961HF1_Server_Installer_linux-x64.tar

## Path to silent installer properties fileINFA.PLATFORM.PROPERTIES=C\:\\SilentInput.properties

## If you want to run postInstallSetup as a part of silent install, then set following property.## set RUN_DEPLOYMENT_FLAG to 1 if you want to run postInstallSetup## or set RUN_DEPLOYMENT_FLAG to 0 if you do not want to run 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 has 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 and Deploying the Hub Server on Nodes in a 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.





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.








b. Enter standalone, and then click Next.



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


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:




Installing and Deploying the Hub Server on Nodes in a Cluster 65





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.



The Install ActiveVOS window appears.

16. If you want to install the bundled, licensed version of Informatica ActiveVOS, select Yes and perform the following substeps. Otherwise, select No, and click Next.

a. On the ActiveVOS Installer page, click Choose and browse to the ActiveVOS_Server installation file in the distribution package. Click Next.

b. On the Choose ActiveVOS Installation Folder page, accept the default installation path or specify a preferred location. Click Next.

c. Enter the ActiveVOS database credentials that you specified when you created the ActiveVOS database schema. Click Next.

d. On the Application Server Web URL page, accept the default URL or specify the URL that you want to use to call ActiveVOS web services. Ensure the URL contains the correct port number for the connection to the application server. Click Next.

The post installation setup script uses the URL to call ActiveVOS web services, deploy the predefined MDM workflows to ActiveVOS, and create the URN mapping.

e. Enter the administrative user name and password to create an administrative user for the ActiveVOS Console.


f. Click Next.

17. Select one of the following Informatica platform installation options:

• Yes. Install Informatica platform.

• No. Does not install Informatica platform.

18. If you select Yes in the preceding step, click Choose and browse to the following Informatica platform file locations:

• Installation response file

• Platform installation file


20. If you want to use a proxy server, select Yes, and enter the proxy server details. Otherwise, select No.








21. Click Next.


22. Select the No, I will run it later post installation setup script option.

Ensure that you run the post installation setup script after the installation.

23. Click Next.


24. Click Next.


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


26. Click Done to exit the Hub Server installer.

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

Installing and Deploying the Hub Server on Nodes in a Cluster 67

C H A P T E R 6

Hub 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 Hub Server, 72

• Configure the Hub Server for a JBoss Cluster, 73

• Configuring JBoss for Multiple Process Servers , 75

• Running the Post Install Script Manually, 76

• Manually Redeploying the Hub Server Applications, 76

• Manually Creating Data Sources, 77

• Manually Configuring JMS Message Queues, 79

• Improve API Performance on JBoss AS 7.2 , 82

• Changing the Operational Reference Store User Password, 83

• Repackaging Custom JAR Files, 83

• Configure JBoss Cache, 84

• Configure Logging for Informatica Platform, 85

• Starting the Hub Console, 85

68

• Registering an Operational Reference Store, 86

• Configuring JBoss Security, 87

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 69

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.

70 Chapter 6: 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 71

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.

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.


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.

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.

Configure the Hub Server for a JBoss ClusterAfter you install the Hub Server in a WebSphere cluster, configure the Hub Server for the cluster environment.

You need to configure the Hub Server properties, repackage the Hub Server EAR file, and deploy the Hub Server applications.

Configuring the Hub Server Properties for a JBoss ClusterAfter you install the Hub Server in a JBoss cluster, configure the Hub Server properties that are related to the cluster environment. You can configure the Hub Server properties in the cmxserver.properties file.

For example, a JBoss cluster has two nodes that run on host1 and host2 and uses RMI ports 4447 and 4448. You need to install the Hub Server properties on node1 and node2.

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

2. Open the cmxserver.properties file on all nodes in the cluster.

The cmxserver.properties file is in the following directory:On UNIX. <infamdm install directory>/hub/server/resourcesOn Windows. <infamdm install directory>\hub\server\resources

Configure the Hub Server for a JBoss Cluster 73

3. Change the following properties in the cmxserver.properties file on all nodes in the cluster:


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

cmx.appserver.hostname Specify machine names of the cluster servers in the following format:

<host name>.<domain>.comFor example, if the cluster has two nodes that run in host1 and host2 and use RMI ports 4447 and 4448, then the properties in cmxserver.properties can have the following values: cmx.appserver.hostname=host1.<domain>.com,host2.<domain>.com

cmx.appserver.rmi.port Specify remote port numbers.For example, if the cluster has two nodes that run in host1 and host2 and use RMI ports 4447 and 4448, then cmx.appserver.rmi.port=4447,4448.Note: Separate the port numbers by a comma with no space between them. Ensure that the order of the port numbers correspond to the order of the host names.

jnlp.initial-heap-size Specify the initial heap size in megabytes for Java Web Start for JVM. Default is 128m.

jnlp.max-heap-size Specify the maximum heap size in megabytes for Java Web Start for JVM. Default is 512m.

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

Repackaging the Hub Server EAR FileAfter you configure the Hub Server properties, repackage the siperian-mrm.ear file.

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

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


Deploying the Hub Server ApplicationsYou can manually deploy the Hub Server applications. Ensure that you deploy the Hub Server applications from the Hub Server installation directory.

1. Stop the JBoss application server.

2. Copy the following deployment files from the source to the target directories:

Deployment File Name Description

siperian-mrm.ear Required. The Hub Server application.

provisioning-ear.ear Required. The Provisioning tool application.

entity360view-ear.ear Optional. The Entity 360 framework.

informatica-mdm-platform-ear.ear Optional. The Informatica platform application.

On UNIX.

Source: Hub Server installation directory

Target: <JBoss installation directory>/<configuration_name>/deploymentsOn Windows.


Target: <JBoss installation directory>\<configuration_name>\deployments

3. Manually configure JMS and data sources in the standalone-full.xml file.


See the JBoss documentation for more information.

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

u Copy the JDBC files from the JBoss instance of the Hub Server to the JBoss instance on which you want to deploy the Process Servers.

The JDBC files are in the following directory:On UNIX. <JBoss installation directory>/modules/com/informatica/mdm/jdbc/mainOn Windows. <JBoss installation directory>\modules\com\informatica\mdm\jdbc\main

Configuring JBoss for Multiple Process Servers 75

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

1. Open a command prompt, and navigate to the PostInstallSetup script in the following directory:

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


Note: If you do not have embedded ActiveVOS in your environment, do not include the ActiveVOS user names and passwords in the command.

On UNIX. postInstallSetup.sh -Ddatabase.password=<MDM Hub Master database password> -Davos.username=<ActiveVOS Console username> -Davos.password=<ActiveVOS Console password> -Davos.jdbc.database.username=<ActiveVOS database username>-Davos.jdbc.database.password=<ActiveVOS database password>Note: If you include the exclamation mark (!) in your password, you must include a backslash before the exclamation mark. For example, if your password is !!cmx!!, enter the password as follows: \!\!cmx\!\!

On Windows. postInstallSetup.bat -Ddatabase.password=<MDM Hub Master database password> -Davos.username=<ActiveVOS Console username> -Davos.password=<ActiveVOS Console password> -Davos.jdbc.database.username=<ActiveVOS database username> -Davos.jdbc.database.password=<ActiveVOS database password>The ActiveVOS Console credentials are the same credentials as the administrative user in the application server.

The ActiveVOS database credentials are the same credentials that were used to run the create_bpm script.

Manually Redeploying the Hub Server ApplicationsYou can manually deploy the Hub Server applications. Ensure that you deploy the Hub Server applications from the Hub Server installation directory.

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


2. Remove the following deployment files from the JBoss deployment directory:



provisioning-ear.ear Required. The Provisioning tool application.





The deployment files are in the following directory:

On UNIX.

• <JBoss installation directory>/<configuration_name>/deploymentsOn Windows.

• <JBoss installation directory>\<configuration_name>\deployments

3. Copy the deployment files from the source to the target directories:

On UNIX.


Target: <JBoss installation directory>/<configuration_name>/deploymentsOn Windows.


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


See the JBoss documentation for more information.

Manually Creating Data SourcesYou can manually configure datasources if you want to perform the following installation tasks:

• Configure multiple Process Servers

• Troubleshoot installation issues

1. Create the following directory structure under <JBoss installation directory>/modules/:

/com/informatica/mdm/jdbc/main2. In the main directory, create the module.xml file with the following content:

<?xml version="1.0" encoding="UTF-8"?><module xmlns="urn:jboss:module:1.0" name="com.informatica.mdm.jdbc"> <resources> <resource-root path="<JDBC driver file name>"/> </resources> <dependencies> <module name="javax.api"/> <module name="javax.transaction.api"/> </dependencies></module>

3. Download and copy the supported version of the JDBC drivers to the main directory.

4. Open the JBoss Management console, and click Profile.

The Datasources page appears.

Manually Creating Data Sources 77

5. Click Connector > Datasources.

6. Click the XA Datasources tab.

The JDBC XA Datasources page appears.

7. Click Add.

The Create XA Datasource dialog box appears.

8. Enter values in the Name and JNDI Name fields, and click Next.

Name

jdbc/siperian-<IBM DB2 DB host name>-<database name>-<operational reference store name>-ds

JNDI Name

java:jboss/datasources/jdbc/siperian-<IBM DB2 host name>-<database name>-<operational reference store name>-ds

The XA Datasource page appears.

9. In the XA Datasource Class field, enter com.informatica.mdm.jdbc, and click Next.

The XA Properties page appears.

10. Enter the key and value pairs, and click Next.

The following table lists the key value pairs:

Key Value

DatabaseName Name of the database that you create.

DeferPrepares false

DriverType 4

PortNumber 50000

ServerName IBM DB2 server name

fullyMaterializeInputStreams true

fullyMaterializeLobData true

progressiveStreaming 2

The Connection Settings window appears.

11. Enter values for the following connection settings, and click Done:

Username

Name of the Operational Reference Store.

Password


The JDBC XA Datasources page appears.


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

Property Value

Min Pool Size 5

Max Pool Size 100

Strict Minimum false

Prefill enabled false

Flush Strategy FailingConnectionOnly

Idle Timeout 0

Track Statements false

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

Property Value

Valid Connection Checker org.jboss.jca.adapters.jdbc.extensions.db2.DB2ValidConnectionChecker

Check Valid Sql Not applicable

Validate On Match false

Background Validation false

Validation Millis 0

Stale Connection Checker org.jboss.jca.adapters.jdbc.extensions.db2.DB2StaleConnectionChecker

Exception Sorter org.jboss.jca.adapters.jdbc.extensions.db2.DB2ExceptionSorter

14. Select the data source that you added, and click Enable.

The data source that you added is enabled.

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.

Manually Configuring JMS Message Queues 79

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.

Note: When you create JMS message queues for the MDM Hub in a clustered environment, ensure that you select a target server that you can migrate. When you configure the JMS module, make the target “All servers in the cluster.” For more information see the WebLogic documentation.

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

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.

Manually Configuring JMS Message Queues 81

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.

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


<JBoss Installation Directory>/standalone/configuration2. Open the standalone-full.xml file in an XML editor.

3. For the JDBC data source connection pool, find the xa-pool element, and set max-pool-size to 300.

<xa-pool> <min-pool-size>5</min-pool-size> <max-pool-size>300</max-pool-size> .....</xa-pool>

4. For the default thread pool, find the thread-pools element, and set max-threads to 300.

<thread-pools> <thread-pool name="default"> <max-threads count="300"/> <keepalive-time time="100" unit="milliseconds"/> </thread-pool></thread-pools>


5. For the HTTP connection pool, find the connector name="HTTP" element, and add the attribute max-connections="300" .

<connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" max-connections="300"/>

6. Save the file.

Changing the Operational Reference Store User Password

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

1. Change the password for the Operational Reference Store user.

2. Set the same password in the data source on the application server.

3. Register the schema with the same user name and password.

Repackaging Custom JAR 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

Changing the Operational Reference Store User Password 83

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

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

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

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

Change the following properties in the jbossCacheConfig.xml file:

lockAcquisitionTimeout

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

sync replTimeout

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

stateRetrieval timeout

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

clustering

Set up the clustering property for a clustered environment.

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

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

jgroupsConfig

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

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

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

eviction

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

Change the eviction time as shown in the following sample:

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


Configure Logging for Informatica PlatformIf you Installed Informatica platform, configure the MDM Hub to log Informatica platform processes.

1. Open the log4j.xml file from the following directory:

On UNIX. <infamdm_install_directory>/hub/server/confOn Windows. <infamdm_install_directory>\hub\server\conf

2. Add the following lines to the log4j.xml file.

<category name="com.informatica.mdm.platform"> <priority value="ALL"/> </category> <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender"> <param name="Threshold" value="ALL"/> </appender>

3. Save and close the log4j.xml file.

Starting the Hub 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 one of the following URLs: http://<MDM Hub host>:<port>/cmx/

where <MDM Hub host> is the local MDM Hub host and port is the port number. Check with your administrator for the correct port number.

The Hub Console launch window appears.

2. Click Launch.

Java Web Start loads.

Note: The first time you launch the Hub Console from a client machine, Java Web Start downloads application files.

The MDM Hub Login dialog box appears.

3. Enter a user name and password.

4. Click OK.

The Change database dialog box appears.

5. Select the target database.

The target database is the MDM Hub Master Database.

6. Select a language from the list, and click Connect.

The Hub Console user interface appears in the language that you select. If you need to change the language in which the Hub Console user interface appears, restart the Hub Console with the language of your choice.

Configure Logging for Informatica Platform 85

Registering an Operational Reference StoreAfter you create an Operational Reference Store, you must register it. Register an Operational Reference Store with a single MDM Hub Master Database. You can register an Operational Reference Store through the Hub Console.

Note: When you register an Operational Reference Store in a clustered environment, manually create the data sources and connection pools for the Operational Reference Stores.



2. Select the MDM Hub Master database, and click Connect.

3. Start the Databases tool under the Configuration workbench.


5. Click the Register database button.

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

6. Select the IBM DB2 database type, 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.

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.



Dynamic Data Masking host

Not required. Do not populate this field, because the value that you provide is not used.

DDM connection URL

Optional. URL to connect to the Dynamic Data Masking application. The URL is similar to the URL that you use to connect to the database, except that the Dynamic Data Masking application URL uses the Dynamic Data Masking host name and port number.

Note: The Schema Name and the User Name are both the names of the Operational Reference Store that you specified when you created the Operational Reference Store. If you need this information, consult your database administrator.

The Summary page appears.

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 data source after registration

Select to create the data source 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.

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.

Configuring JBoss Security 87

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.


On UNIX.<Jboss install directory>/standalone/configuration/standalone-full.xml

On Windows.<Jboss install directory>\standalone\configuration\standalone-full.xml

b. Add the security-realm attribute as shown in the following code: <subsystem xmlns="urn:jboss:domain:remoting:1.1"> <connector name="remoting-connector" socket-binding="remoting" security-realm=<"ApplicationRealm">/></subsystem>

3. Register the MDM Hub users that must have access to the Hub Server in JBoss.

a. You can run the following script as one of the ways to register the MDM Hub users:

On UNIX. <Jboss install directory>/bin/add-user.shOn Windows. <Jboss install directory>\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) Use the name of the security realm. Default is ApplicationRealm.

Username User name of the MDM Hub user.


Prompt Value

Password Password of the MDM Hub user that adheres to JBoss password policy.


You must specify hubconsole.

4. Enable JBoss security on the Hub Server.

a. Open cmxserver.properties in the following directory:

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

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

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

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

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

On UNIX.cd <infamdm install directory>/hub/server/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 27

• “Manually Redeploying the Hub Server Applications” on page 76

Configuring JBoss Security 89

C H A P T E R 7

Process Server InstallationThis chapter includes the following topics:

• Installing the Process Server in Graphical Mode, 90

• Installing the Process Server in Console Mode, 92

• Installing the Process Server in Silent Mode, 94

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

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

On UNIX, use the same user name that you used to install the Hub Server for the Process Server. If you install the Hub Server and the Process Server on the same machine, the users who install them must belong to the same UNIX group.

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



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.

90



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

On UNIX, the Choose Link Folder window appears.

On Windows, the Choose Shortcut Folder window appears.

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

The Enter Location of License File window appears.






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


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




d. Click Next.

12. Configure cleanse engine settings for the cleanse engine you use.

• If you use Address Doctor, specify the Configuration file and Parameters file locations and the Correction Type parameter.

• If you use Business Objects DQ XI, specify the Host, Port, and Sub File parameters for the Business Objects DQ XI cleanse engine.

13. Click Next.


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







16. Click Next.


17. Select one of the following post installation setup script options:

• Yes, run the script during this installation. Runs the post installation script during the installation.

• No, I will run it later. Allows you to manually run the post installation script later.

18. Click Next.

Installing the Process Server in Graphical Mode 91


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.



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.


5. Press Enter.


6. Read the License Agreement. Type Y to accept the license agreement, or type N if you do not want to accept the license agreement and want to exit the installation program.

7. Press Enter.


8. Choose the folder for the Process Server installation.

• To choose the default location, press Enter.


9. Confirm the location of the installation folder. Type Y to confirm the installation folder, or type N to 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.

92 Chapter 7: Process Server Installation

12. Type the number for the application server that you want to select, and press Enter.

The application server information appears.



The JBoss application server configuration name information appears.


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.

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

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









19. Press Enter.


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

Installing the Process Server in Console Mode 93

21. Press Enter.

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


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


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.



JBOSS.AS.PORT_1 The JBoss Port number.


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 95


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.4.0JBOSS.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 lincense 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 has 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=





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

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

Installing and Deploying the Process Server on Nodes in the Cluster

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

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

to install on another node of a cluster. 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.


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

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



5. Click Next.




7. Select the location of the Process Server installation.



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



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

The Enter Location of License File window appears.








b. Enter standalone, and then click Next.



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



12. Configure cleanse engine settings for the cleanse engine you use.

• If you use Address Doctor, specify the Configuration file and Parameters file locations and the Correction Type parameter.

• If you use Business Objects DQ XI, specify the Host, Port, and Sub File parameters for the Business Objects DQ XI cleanse engine.

13. Click Next.


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







16. Click Next.


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

18. Click Next.


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


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

21. Click Done to exit the Process Server installer.

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

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

C H A P T E R 8

Process Server Post-Installation Tasks


• Copy the Installation Log Files, 100

• Verify the Version and Build Number, 102

• Configure the Process Server, 103

• Configure Process Server for Multithreading, 107

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

• Configuring Multiple Process Servers for Batch Processes, 109

• Configure Match Population, 110

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.

100

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.

Copy the Installation Log Files 101

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

102 Chapter 8: Process Server Post-Installation Tasks

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

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 find 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 datasources for the Process Server.

To configure the application server to create datasources for the Process Server, perform the following tasks:

1. Copy the <datasources> definition for the MDM Hub Master Database and each Operational Reference Store from the standalone-full.xml file on the Hub Server machine to the standalone-full.xml file on the Process Server machine.The standalone-full.xml file is in the following location:

<JBoss installation directory>/standalone/configurationThe following sample code shows the <datasources> definition:

<subsystem xmlns="urn:jboss:domain:datasources:1.2"> <datasources> ..... ..... <xa-datasource jndi-name="java:jboss/datasources/jdbc/siperian-cmx_system-ds" pool-name="jdbc/siperian-cmx_system-ds" enabled="true" use-java-context="true" spy="false" use-ccm="true"> <xa-datasource-property name="URL"> jdbc:oracle:thin:@//localhost:1522/orcl </xa-datasource-property> <xa-datasource-property name="ConnectionProperties"> oracle.jdbc.J2EE13Compliant=true </xa-datasource-property> <driver>com.informatica.mdm.jdbc</driver> <xa-pool> <min-pool-size>5</min-pool-size> <max-pool-size>100</max-pool-size> <prefill>false</prefill> <use-strict-min>false</use-strict-min> <flush-strategy>FailingConnectionOnly</flush-strategy> <is-same-rm-override>false</is-same-rm-override> <no-tx-separate-pools>true</no-tx-separate-pools> <pad-xid>false</pad-xid>

Configure the Process Server 103

<wrap-xa-resource>true</wrap-xa-resource> </xa-pool> <security> <user-name>cmx</user-name> <password>!!cmx!!</password> </security> <validation> <validate-on-match>false</validate-on-match> <background-validation>false</background-validation> <use-fast-fail>false</use-fast-fail> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"/> </validation> <statement> <track-statements>false</track-statements> </statement> </xa-datasource>

<xa-datasource jndi-name="java:jboss/datasources/jdbc/siperian-orcl-mdm_sample-ds" pool-name="jdbc/siperian-orcl-mdm_sample-ds" enabled="true" use-java-context="true" spy="false" use-ccm="true"> <xa-datasource-property name="URL"> jdbc:oracle:thin:@//localhost:1522/orcl </xa-datasource-property> <xa-datasource-property name="ConnectionProperties"> oracle.jdbc.J2EE13Compliant=true </xa-datasource-property> <driver>com.informatica.mdm.jdbc</driver> <xa-pool> <min-pool-size>5</min-pool-size> <max-pool-size>100</max-pool-size> <prefill>false</prefill> <use-strict-min>false</use-strict-min> <flush-strategy>FailingConnectionOnly</flush-strategy> <is-same-rm-override>false</is-same-rm-override> <no-tx-separate-pools>true</no-tx-separate-pools> <pad-xid>false</pad-xid> <wrap-xa-resource>true</wrap-xa-resource> </xa-pool> <security> <user-name>MDM_SAMPLE</user-name> <password>!!cmx!!</password> </security> <validation> <validate-on-match>false</validate-on-match> <background-validation>false</background-validation> <use-fast-fail>false</use-fast-fail> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"/> </validation> <statement> <track-statements>false</track-statements> </statement> </xa-datasource>

<drivers> <driver name="h2" module="com.h2database.h2"> <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class> </driver> <driver name="com.informatica.mdm.jdbc" module="com.informatica.mdm.jdbc"> <xa-datasource-class>com.ibm.db2.jcc.DB2Driver</xa-datasource-class> </driver> <driver name="com.activevos" module="com.activevos"> <xa-datasource-class>oracle.jdbc.OracleDriver</xa-datasource-class> </driver> </drivers> </datasources></subsystem>


2. On the Process Server machine, add the following directory structure under <JBoss installation directory>\modules:com\informatica\mdm\jdbc\main

3. On the Hub Server machine, copy the following files from <JBoss installation directory>\modules:

• module.xml

• Supported version of the JDBC drivers

4. On the Process Server machine, copy to <JBoss installation directory>\modules\com\informatica\mdm\jdbc\main.

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.


Configure the Process Server 105

Configuring the Process Server 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. Save and close the cmxcleanse.properties file.

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

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

1. Open a command prompt, and 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.


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.

Configure Process Server for Multithreading 107

The default value is 20.

7. Click OK and then click Save.

Configuring Multiple Process Servers for Cleanse and Match Operations

You can configure multiple Process Servers for each Operational Reference Store database. You can configure multiple Process Servers to run on a single machine or on multiple machines.

Ensure that you configure each Process Server to run on a separate application server.

1. Install and configure an instance of the Process Server.

2. Configure multiple application servers.

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

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

The following table describes the distributed cleanse and match properties:


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

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

The cmxcleanse.properties is in the following directory: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.

Configuring Multiple Process Servers for Batch Processes 109

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.

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. Restart the Process Server after you enable populations.

4. 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 9

ActiveVOS Post-Installation Tasks for the Application Server

This chapter includes the following topic:

• Create a Trusted User in JBoss Environments, 111

Create a Trusted User in JBoss EnvironmentsTo use the ActiveVOS workflow engine, create a trusted user with the role of abTrust, abServiceConsumer, and abTaskClient in the application server. The trusted user is trusted by MDM Hub and by ActiveVOS. The user facilitates secure communication between the MDM Hub and ActiveVOS.

The trusted user is the same user as the ActiveVOS workflow adapter user in the Hub Console. The name of the trusted user cannot be the same name as the application server adminstrative user.

1. From the command prompt, run add-user.bat.

• In UNIX. <JBoss install director>/bin/add-user.sh• In Windows. <JBoss install director>\bin\add-user.bat


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

What type of user do you wish to add? a) Management User or b) Application User

Enter b to select Application User.

Realm (ApplicationRealm)

Enter the same realm name that you specified in the login-module that you added to the standalone-full.xml file.

Username

Enter the user name of the trusted user.

Password

Enter a password that complies with the JBoss password standard.


Enter abTrust,abServiceConsumer,abTaskClient.

111

About to add user <username> for realm <realmname>. Is this correct?

To add the user, enter yes.

Is this new user going to be used for one AS process to connect to another AS process?

Enter yes.


112 Chapter 9: ActiveVOS Post-Installation Tasks for the Application Server

C H A P T E R 1 0

ActiveVOS Post-Installation Tasks for the Business Entity Adapter


• ActiveVOS Web Applications, 113

• Configuring the ActiveVOS URNs for the Business Entity Workflow Adapter, 114

• Set the ActiveVOS Protocol to HTTPS, 114

• Configure Task Assignment, 115

• Configure Task Triggers, 115

• Setting the Default Approval Workflow for the Entity 360 Framework, 116

• Configure the Primary Workflow Engine, 117

• Generating Business Entity and Business Entity Services Configuration Files, 118

• Configure the MDM Identity Services for ActiveVOS, 118

ActiveVOS Web ApplicationsWhen you install the bundled, licensed version of the ActiveVOS Server, you are also licensed to use two ActiveVOS web applications. After you add users to the application server container, you can use these applications.

You use the web applications for different purposes:

ActiveVOS Console

Administrators use the ActiveVOS Console to manage deployed processes, the alerting system, and endpoint locations. You can also configure the engine for performance monitoring and management.

ActiveVOS Central

Business users can use ActiveVOS Central to manage tasks, requests, and reports. However, in general, business users use an Informatica Data Director (IDD) application to manage tasks because they can open the entities to review from the Task Manager.

To use ActiveVOS Central, you must add the MDM Hub users to the application server container.

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

113

Configuring the ActiveVOS URNs for the Business Entity Workflow Adapter

The ActiveVOS Server has two predefined uniform resource names (URNs) that it uses internally. You need to update the URL in the URN mappings to use the host name and the port number where the ActiveVOS Server runs.

1. Launch the ActiveVOS Console. In a browser, type the following URL, substituting the correct host name and port number:

Encrypted connections.https://[host]:[port]/activevosNon-encrypted connections.http://[host]:[port]/activevos

2. In the ActiveVOS Console, on the Home page, click Administration > Configure Server > URN Mappings.

3. For the following URNs, update the paths to reflect the host name and port number of the ActiveVOS Server:

URN URL Path

ae:internal-reporting Encrypted connections. https://[host]:[port]/activevos/internalreportsNon-encrypted connections. http://[host]:[port]/activevos/internalreports

ae:task-inbox Encrypted connections. https://[host]:[port]/activevos-central/avcNon-encrypted connections. http://[host]:[port]/activevos-central/avc

4. Verify that urn:mdm:service is mapped to the host name and port number of the MDM Hub Server:

Encrypted connections.https://[host]:[port]/cmx/services/BeServicesNon-encrypted connections.http://[host]:[port]/cmx/services/BeServices

Set the ActiveVOS Protocol to HTTPSTo enable secure communication between ActiveVOS and the MDM Hub, set the protocol to HTTPS in the Hub Console Workflow Manager.

You must first configure the application server for HTTPS communications.


2. Acquire a write lock.

3. Click Workflow Manager under the Configuration workbench.

4. In the Workflow Manager, click the Workflow Engines tab.

5. Select the ActiveVOS workflow engine, and then click the Edit button.

6. In the Edit Workflow dialog box, set the protocol to HTTPS.

114 Chapter 10: ActiveVOS Post-Installation Tasks for the Business Entity Adapter

7. In a WebLogic environment, in the Edit Workflow dialog box, enter the user name and password of the user that belongs to the abAdmin role.

Configure Task AssignmentTo configure task assignment for the ActiveVOS workflow adapter based on business entities, use the IDD Configuration Manager to configure task assignment for each subject area. The user can either assign the task directly or allow the Task Manager to assign tasks to users.

1. Log in to the Informatica Data Director Configuration Manager.

http://[host]:[port]/bdd/config/2. Select the application to update.

3. Click Edit.

4. In the Subject Areas tab, select a subject area, and then click Edit Subject Area.

5. Click the Task Assignment tab, and then click Add.

6. From the Task Assignment dialog box, select the task to configure from the Task list.

7. Select the roles and users to which the task can be assigned. Click OK.

8. Click Save.

9. Click Generate Business Entity Schema. Configuration Manager generates the business entity and business entity service configuration.

10. In the MDM Hub, use the Repository Manager to validate the Operational References Store. The Repository Manager validation refreshes the repository data that is cached in the application server.

Configure Task TriggersYou must configure task triggers to use ActiveVOS workflows based on business entities with the Task Manager. If you do not configure task triggers, the tasks do not appear in the Task Manager.

To configure triggers, use the Provisioning tool to edit the task configuration file from the Advance Configuration page. For more information, see the Informatica MDM Multidomain Edition Provisioning Tool Guide.

You can configure the following startWorkflow attributes to configure task triggers:

process

The name of the ActiveVOS workflow process.

taskKind

Defines the type of user interface required for the process. Can be REVIEW, MERGE, or UNMERGE. The taskKind is returned by the ActiveVOS workflow engine.

taskTemplate

The name of the task template to use.

Configure Task Assignment 115

firstTask Type

The first task in the workflow. Optional. This parameter allows the task to be assigned when the task is created.

Two-step approval code sample

The following code sample shows the startWorkflow element configuration for the ActiveVOS adapter based on business entities for the two-step approval task:

<startWorkflow process="BeTwoStepApprovalTask" taskKind="REVIEW" taskTemplate="DefaultApproval" firstTaskType="AVOSBeReviewNoApprove"/>

One-step approval code sample

The following code sample shows the startWorkflow element configuration for the ActiveVOS adapter based on business entities for the one-step approval task:

<startWorkflow process="BeOneStepApprovalTask" taskKind="REVIEW" taskTemplate="DefaultApproval" firstTaskType="AVOSBeFinalReview"/>

Update with approval code sample

The following code sample shows the startWorkflow element configuration for the ActiveVOS adapter based on business entities for the update-with-approval task:

<startWorkflow process="BeUpdateWithApprovalTask" taskKind="REVIEW" taskTemplate="DefaultApproval" firstTaskType="AVOSBeUpdate"/>

Setting the Default Approval Workflow for the Entity 360 Framework

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

1. Log in to the Provisioning tool.

2. Click Advanced Configuration > Task Configuration (XML).

The task configuration XML file appears.

3. To configure the task properties for tasks created by the default workflow, add the default approval task template configuration to the XML file.

The following code sample shows a default approval task template that sets the priority to NORMAL, sets the due date to seven days from the current date, and sets the status of the task to OPEN:

<taskTemplate name="DefaultApproval"> <title>Review changes in (taskRecord[0].label)</title> <priority>NORMAL</priority> <dueDate>+7d</dueDate> <status>OPEN</status></taskTemplate>

4. To specify which workflow is triggered by default, add the default approval trigger configuration to the XML file.


The following code sample shows the ReviewNoApprove workflow set as the default workflow when users of any role create or update a business entity:

<trigger name="DefaultApproval"> <startWorkflow process="ReviewNoApprove" taskKind="REVIEW" taskTemplate="DefaultApproval"/> <event name="CreateBE"/> <event name="UpdateBE"/> <role name="*"/></trigger>

5. Click Validate + Publish.

6. Log in to the IDD Configuration Manager.

7. Select the IDD application, and then click Clear Cache.

Configure the Primary Workflow EngineTo configure the primary workflow engine, add a workflow engine for ActiveVOS workflows based on business entities. The secondary workflow engine is for existing customers who want to process existing tasks with a deprecated workflow engine.

1. In the Hub Console, click Workflow Manager in the Configuration workbench.

2. Acquire a write lock.

3. Select the Workflow Engines tab and click the Add button.

4. In the Add Workflow dialog box, enter the workflow engine properties.

The following table describes the workflow engine properties:

Field Description

Workflow Engine The display name of the workflow engine

Adapter Name Select BE ActiveVOS for the ActiveVOS workflow adapter based on composite objects.

Host The host name of the Informatica ActiveVOS instance.

Post The port name of the Informatica ActiveVOS instance.

Username The user name of the trusted user.

Password The password of the trusted user.

Protocol The protocol for communication between the MDM Hub and ActiveVOS. The protocol can be http or https.

5. Click OK.

Configure the Primary Workflow Engine 117

Generating Business Entity and Business Entity Services Configuration Files

To generate business entity and business entity services configuration files, use the Informatica Data Director Configuration Manager.

1. In the Configuration Manager Applications pane, select the Informatica Data Director application whose configuration you want to generate into a business entity and business entity service configuration.

2. Click Generate Business Entity Schema.

Configuration Manager generates the business entity and business entity service configuration.

3. Configuration Manager displays messages of issues encountered while generating the business entity and business entity services configuration. The messages indicate if Configuration Manager resolved the issue during the generation process and describes the changes Configuration Manager made to resolve the issue. If Configuration Manager did not fix the issue, note the issue and the suggested action you can take to resolve the issue.

Configure the MDM Identity Services for ActiveVOSIf you use embedded ActiveVOS, ensure that you configure ActiveVOS to use MDM Identity Services. To configure the MDM Identity Services for ActiveVOS, use the ActiveVOS Console to set the Identity Services password to the password of the MDM Hub workflow engine user.

1. In the ActiveVOS console, select Admin > Configure Services > Identity Services.

2. In the Provider Configuration section, enable the Enable check box and select MDM from the Provider Type list.

3. In the Connection tab, enter the password of the MDM Hub user with the user name admin.

Note: If you later change the password for the admin user, you must enter the new password in the ActiveVOS identity services settings.

4. Click Update.

5. Test that ActiveVOS can log in to the MDM Hub as the admin user, and that ActiveVOS can retrieve a list of roles for the user you specify as the User for test.

a. Select the Test tab.

b. In the User for test field, enter an MDM Hub user that is assigned to a role.

c. Click Test Settings.

Note: The test fails if an Operational Reference Store is not configured and the user for test does not belong to a role.


C H A P T E R 1 1

Resource Kit InstallationThis chapter includes the following topics:

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

• Registering the Informatica MDM Hub Sample Operational Reference Store, 121

• Installing the Resource Kit in Graphical Mode, 122

• Installing the Resource Kit in Console Mode, 125

• Installing the Resource Kit in Silent Mode, 127

Setting Up the MDM Hub Sample Operational Reference Store

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

1. Create an MDM Hub sample Operational Reference Store user on the machine on which the database is installed.

On UNIX, ensure that you create the user name with 8 characters or less.

2. Add the MDM Hub sample Operational Reference Store user to the DB2ADMNS and DB2USERS user groups.




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



Enter database type. (ORACLE, MSSQL, DB2)


119

Enter the Operational Reference Store database host name. [localhost]

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

Enter the Operational Reference Store database port number. [50000]

Port number that the database uses.Default is 50000.

Enter the database name. [SIP97]

Name of the database. Default is SIP97.


Connect URL for the database connection.

Enter the Operational Reference Store database user name. [cmx_ors]

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

Enter the Operational Reference Store database user password.

Password of the MDM Hub sample Operational Reference Store user.

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


Enter the DBA user name. [DB2ADMIN]

User name of the administrative user. Default is DB2ADMIN.

Enter the DBA password.

Password of the administrative user.

6. After you create the sample Operational Reference Store, review sip_ant.log in the following directory:

On UNIX. <distribution directory>/database/binOn Windows. <distribution directory>\database\binThe sip_ant.log file logs any errors that might occur when you run the sip_ant script to create the Operational Reference Store.

7. To import mdm_sample, run the following command:

On UNIX. sip_ant.sh import_schemaOn Windows. sip_ant.bat import_schema

120 Chapter 11: Resource Kit Installation



Enter database type. (ORACLE, MSSQL, DB2)


Enter the Operational Reference Store database host name. [localhost]

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

Enter the Operational Reference Store database port number. [50000]

Port number that the database uses.Default is 50000.

Enter the database name. [SIP97]

Name of the database. Default is SIP97.


Connect URL for the database connection.

Enter the Operational Reference Store database user name. [cmx_ors]

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

Enter the Operational Reference Store database user password.

Name of the MDM Hub sample Operational Reference Store database user.

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


Enter the path to the ZIP dump file. [<distribution directory>\resources\database]

Path to the mdm_sample.zip file.

Enter the name of the ZIP dump file. [mdm_sample.zip]

Name of the ZIP dump file. Default is mdm_sample.zip.

Registering the Informatica MDM Hub Sample Operational Reference Store

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



2. Select the MDM Hub Master Database, and click Connect.

3. Start the Databases tool under the Configuration workbench.


5. Click the Register database button.

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

6. Select the type of database, and click Next.

Registering the Informatica MDM Hub Sample Operational Reference Store 121

7. Configure connection properties for the database.

a. Specify the connection properties, and click Next.

Specify the connection properties, and click Next.

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

Create data source after registration

Select to create the data source 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 MDM Hub sample Operational Reference Store.

10. Select the MDM Hub sample Operational Reference Store that you registered, and click the Test database connection button to test the database settings.

The Test Database dialog box displays the result of the database connection test.

11. Click OK.

The Operational Reference Store is registered, and the connection to the database is tested.

Installing the Resource Kit in Graphical ModeYou can install the Resource Kit in graphical mode.

Before you install the Resource Kit, you must have installed and configured the MDM Hub.


2. Open a command prompt and navigate to the Resource Kit installer. By default the installer is in the following directory:

On UNIX. <distribution directory>/<operating system name>/mrmresourcekitOn Windows. <distribution directory>\windows\mrmresourcekit


On UNIX. hub_resourcekit_install.binOn Windows. hub_resourcekit_install.exe




5. Click Next.



The Installation Feature window appears.

7. Select the Resource Kit features that you want to install and click Next.

You can select the following options:Sample Schema

Installs the MDM Hub sample schema resources. You must create a sample schema and register it with the Hub Server before you install the sample applications.

Samples and Utilities

Installs the sample applications and utilities.The list of sample applications that are deployed is stored in the build.properties file in the following directory:

<Resourcekit_Home>\samplesSIF SDK and Javadocs

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

BPM SDK

Installs the resources associated with the BPM SDK.

Jaspersoft

Copies the Jaspersoft installer to the Resource Kit home.

SSA-NAME3

Copies the SSA-NAME3 installer to the Resource Kit home.

A message about the requirement of having created and registered a sample schema with the MDM Hub appears.

8. Click OK.


9. Select the location of the Resource Kit installation.




• To return to the default installation location, click Restore Default Folder.




10. On UNIX, choose a link folder or select the option to not create links, and click Next. On Windows, select the location to create a product icon or select the option not to create a product icon.

The Configuration Selection window appears.

11. Select a configuration option, and click Next.

You can select one of the following options:

Installing the Resource Kit in Graphical Mode 123

Configure Samples

Installs and configures the samples.

Source Only

Installs the sources of samples but does not configure the samples.

If you select Configure samples, the Resource Kit App Server window appears. If you select Source only, the Pre-Installation Summary window appears.

12. From the Resource Kit App Server window, select the application server on which you want to install the Resource Kit, and click Next.

The Application Server Home window for the application server that you select appears.

13. Configure the application server settings.



b. Specify the configuration name, and then click Next.



The Informatica MDM Hub Server window appears.

14. Enter the information for the Hub Server installation, and click Next.

Enter values in the following fields:Server Name

Name of the server that hosts the Hub Server.

Server HTTP Port

Port number of the Hub Server.

Informatica MDM Administrative password

Password to access the MDM Hub.

The Resource Kit ORS ID window appears.

15. Select a Resource Kit ORS ID from the list, and then click Next.

The list contains the Operational Reference Store IDs that you created. Select an Operational Reference Store ID related to the sample schema.

If you have not registered the sample schema, you will not see the Operational Reference Store ID for the sample schema. Register the sample Operational Reference Store, and then restart the installation.

The Deployment Selection window appears.

16. Select one of the following options and click Next:

Yes, run it during this installation.

Deploys and configures the Resource Kit during the installation.

No, it can be deployed later.

Select this option to deploy and configure manually at a later time.If you chose to install the Samples and Utilities feature, you must deploy and configure the Resource Kit in this installation step. If you do not deploy the Resource Kit in this step, you cannot make changes and redeploy the samples by using the postInstallSetup script provided in the Resource Kit.


If you choose to run the post-installation setup manually, you cannot deploy the EAR file by using the postInstallSetup script at a later time. You must manually edit the EAR file and deploy it to make any changes to your installation.


17. Review the Pre-Installation Summary to confirm your installation choices, and then click Install.


18. Click Done to exit the Resource Kit installer.

Installing the Resource Kit in Console ModeYou can install the Resource Kit in console mode.

Ensure that you register the MDM_SAMPLE schema before you install the Resource Kit.



On UNIX. <distribution directory>/<operating system name>/resourcekitOn Windows. <distribution directory>/windows/resourcekit

3. Run the following command from the command prompt:

On UNIX. ./hub_resourcekit_install.bin -i consoleOn Windows. hub_resourcekit_install.exe -i console

4. Enter the number of the locale you want to choose for the installation, and then press Enter.


5. Press Enter.


6. Read the License Agreement. Type Y to accept the terms of the license agreement, or type N if you do not want to accept the license agreement and want to exit the installation program.

7. Press Enter.


8. Enter the numbers of the Resource Kit features that you want to install separated by commas, and press Enter.

The prompt for the sample schema installation appears.

9. Choose a folder for the Resource Kit installation.

• To choose the default folder, press Enter.


10. Confirm the location of the installation folder. Type OK to confirm the installation folder or type Cancel to change the installation folder.

11. Press Enter.

A list of link location options appears.

12. Enter the number of a link location option.

The prompt for the link file location appears.

Installing the Resource Kit in Console Mode 125

13. Enter the absolute path of the link file, and press Enter.

The source sample configuration options appears.

14. Enter a configuration option, and press Enter.

Option Description

1 Installs and configures the samples

2 Installs the sources of samples but does not configure the samples

If you enter 1, a list of application server options appears. If you enter 2, the pre-Installation summary appears.

15. If you entered 1, enter the number for the application server that you want to select, and press Enter.

The application server information prompts appear.



The information about the JBoss application server configuration name appears.


c. Press Enter.

d. Specify the remote port.

Note: If the JBoss port conflicts with the default database port, change one of the ports to resolve the conflict.

The Hub Server information prompts appear.

17. Enter the information for the Hub Server installation, and press Enter.

The following table describes the prompts for the Hub Server installation information:

Prompt Description

Server Name Name of the server that hosts the Hub Server.

Server HTTP Port Port number of the Hub Server.

Informatica MDM Administrative password Password to access the MDM Hub.

A list of MDM Hub ORS IDs appears.

18. Enter the Operational Reference Store ID of the MDM sample schema, and press Enter.

If you did not register the sample schema, you will not see the Operational Reference Store ID for the sample schema. Register the sample Operational Reference Store, and then restart the installation.

The deployment selection prompt appears.


20. Press Enter.



21. Verify the information in the pre-installation summary. If the information is correct, press Enter to start the installation.

The Resource Kit is installed according to the configuration information you provide. When the process is complete, the installation complete information appears.


Installing the Resource Kit in Silent ModeYou can install the Resource Kit without user interaction in silent mode. You might want to perform a silent installation if you need multiple installations, or if you need to install on a machine cluster. A silent installation does not show any progress or failure messages.

Before you run the silent installation for the Resource Kit, you must configure the properties file for the silent installation. The installer reads the file to determine the installation options. The silent installation process might complete successfully even if you provide incorrect settings, such as an incorrect application server path or port. You must ensure that you provide correct settings in the properties file.

Copy the Resource Kit installation files to the hard disk on the machine where you plan to install the Resource Kit. To install in silent mode, complete the following tasks:





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

On UNIX. /silent_install/mrmresourcekitOn Windows. \silent_install\mrmresourcekitAfter you customize the file, save it. You can rename the file and put it anywhere on the machine.

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

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


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

Installing the Resource Kit in Silent Mode 127

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


INSTALLER_UI Specifies the mode of installation. Set to silent.

SIP.INSTALL.TYPE Specifies the type of installation. Set to SIPERIAN_SAMPLE_INSTALL.

SIP.INSTALL.SAMPLE.SCHEMA Specifies if you want to install the sample schema.Specify one of the following values:- 0. Does not install the sample schema- 1. Installs the sample schema

SIP.INSTALL.SAMPLES Specifies if you want to install samples and utilities.Specify one of the following values:- 0. Does not install samples and utilities- 1. Installs samples and utilities

SIP.INSTALL.SIF.SDK Specifies if you want to install the Services Integration Framework (SIF) SDK.Specify one of the following values:- 0. Does not install the SIF SDK- 1. Installs SIF SDK

SIP.INSTALL.BPM.SDK Specifies if you want to install the BPM SDK.Specify one of the following values:- 0. Does not install the BPM SDK- 1. Installs the SIF SDK

SIP.INSTALL.JASPERSOFT Specifies if you want to install the Jaspersoft reporting tool.Specify one of the following values:- 0. Does not install the BPM SDK- 1. Installs the SIF SDK

SIP.INSTALL.SSANAME3 Specifies if you want to install SSA-NAME3.Specify one of the following values:- 0. Does not install SSA-NAME3- 1. Installs SSA-NAME3

USER_INSTALL_DIR Directory where you want to install the Resource Kit, such as C\:\\<infamdm_install_directory>\\hub\\resourcekit.

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



RUN_CONFIGURE_SETUP Specifies if you want to configure only source samples.- 0. Does not install sources of samples- 1. Installs sources of samplesIf you set the RUN_CONFIGURE_SETUP property to 1, comment out or set the RUN_CONFIGURE_FLAG property to 0. If you set the RUN_CONFIGURE_SETUP property to 1, you cannot configure and deploy samples later.



JBOSS.AS.PORT_1 The JBoss port number.


SIP.SERVER.NAME Name of the server on which the Hub Server is deployed.

SIP.SERVER.HTTP.PORT Port on which the Hub Server is listening.

SIP.ADMIN.PASSWORD Password to access the Hub Server.

SIP.ORS.ID Operational Reference Store ID of the MDM Hub sample schema.

RUN_DEPLOYMENT_FLAG Runs the postInstallSetup script as part of the silent installation.- 0. Does not run the postInstallSetup script- 1. Runs the postInstallSetup script

Sample Properties FileThe following example shows the contents of the sample silentInstallResourceKit_sample.properties file:

INSTALLER_UI=silentSIP.INSTALL.TYPE=SIPERIAN_SAMPLE_INSTALL

#Installation Features#0=Do not install#1=Install

SIP.INSTALL.SAMPLE.SCHEMA=1SIP.INSTALL.SAMPLES=1SIP.INSTALL.SIF.SDK=1SIP.INSTALL.BPM.SDK=1SIP.INSTALL.JASPERSOFT=1SIP.INSTALL.SSANAME3=1

## Resource Kit Install directory.USER_INSTALL_DIR=C\:\\siperian\\hub\\resourcekit

## If you want to configure samples as a part of silent installation, set following property:RUN_CONFIGURE_FLAG=1## If you want to install only source samples as a part of silent installation, set following property:#RUN_CONFIGURE_SETUP=0

## Set the properties for one of the application servers JBoss, WebSphere, or WebLogic.

Installing the Resource Kit in Silent Mode 129

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

## properties for MDM Hub ServerSIP.SERVER.NAME=localhostSIP.SERVER.HTTP.PORT=4447SIP.ADMIN.PASSWORD=admin

#sip ors id from hub serverSIP.ORS.ID=localhost-orcl-MDM_SAMPLE

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





On UNIX. ./hub_resourcekit_install.bin -f <location_of_silent_properties_file_for_resourcekit>On Windows. .\hub_resourcekit_install.exe -f <location_of_silent_properties_file_for_resourcekit>

The silent installer runs in the background. The process can take a while. Check the postinstallSetup.log files to verify that the installation was successful.

The log file is available in the following directory:

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

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


C H A P T E R 1 2

Resource Kit Post-Installation Tasks

This chapter includes the following topic:

• Validate the MDM Hub Sample Operational Store, 131

Validate the MDM Hub Sample Operational StoreAfter you set up and register the MDM Hub sample Operational Reference Store, validate the metadata in the MDM Hub sample Operational Reference Store. Validation verifies the completeness and integrity of the metadata that describes the MDM Hub sample Operational Reference Store.

1. In the Hub Console, start the Repository Manager.

2. From the Select the repository to validate list, select the MDM Hub sample Operational Reference Store that you registered.

3. Select the Validate button.

The Select Validation Checks dialog box appears.

4. Enable all the validation checks, and click OK.

5. If validation errors are generated, regenerate MTIP views.

a. Start the Enterprise Manager and acquire a write lock.

b. On the ORS databases tab, select the MDM Hub sample Operational Reference Store name.

The Properties tab of the MDM Hub sample Operational Reference Store opens.

c. Click the Regenerate MTIP's button.

MTIP views are regenerated and the errors are fixed.

131

C H A P T E R 1 3

Troubleshooting the MDM HubThis chapter includes the following topic:

• Troubleshooting the Installation Process, 132

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

PostInstallSetUp script fails because the ActiveVOS server deployment times outWhen you install the Hub Server, the post-installation setup process might fail after trying to deploy the ActiveVOS server.

To resolve the issue, increase the value of the deploy.wait.time property in the build.properties file in the following directory:

On UNIX. <infamdm installation directory>/hub/server/bin

On Windows. <infamdm installation directory>\hub\server\bin

Operational Reference Store registration fails because the connection times outWhen you register the Operational Reference Store (ORS) in a JBoss cluster node, the ORS registration fails with a connection timeout error similar to the following:

SIP-10313: SIP-09061: Failed connecting with provider url abc03.java.net.ConnectException: JBAS012144: Could not connect to remote://abc03:9999. The connection timed out.

To resolve the issue, when you register an ORS, disable the JBoss administrative security, and then enable the JBoss administrative security after ORS registration.

132

Hub Server deployment fails because JBoss composite operation failsWhen you deploy the Hub Server in the JBoss application server, the Hub Server deployment fails with the following error:

JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => { "JBAS014671: Failed services" => {"jboss.web.deployment.default-host./cmx" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./cmx: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start contextCaused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context"

To resolve the issue, perform the following steps:


2. Use a text editor to open the standalone.xml file in the following directory:On UNIX. <JBoss Installation Directory>/standalone/configurationOn Windows. <JBoss Installation Directory>\standalone\configuration

3. Find the following code:<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1"> <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/></subsystem>

4. Add the deployment-timeout="300" attribute as shown in the following sample code:

<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1"> <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" deployment-timeout="300"/></subsystem>

5. Save changes, and start the JBoss application server.The default deployment timeout value is 60, which is changed to 300.

6. Deploy the Hub Server.

The Hub Server cannot connect to the cmx_system schemaTo verify that the Hub Server cannot connect to the cmx_system schema, review the application server log.

To resolve the issue, resolve the database connection issue. Use the application server console to test the connection to the database. If you cannot resolve the connection to the cmx_system schema, re-create the cmx_system schema.

Failed to verify the need to tokenize 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

Troubleshooting the Installation Process 133

- 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

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


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

134 Chapter 13: Troubleshooting the MDM Hub

C H A P T E R 1 4

UninstallationThis chapter includes the following topics:

• Uninstallation Overview, 135

• Uninstalling the Hub Store, 135

• Uninstalling the Process Server in Graphical Mode, 136

• Uninstalling the Hub Server in Graphical Mode, 137

• Uninstalling the Resource Kit in Graphical Mode, 137

• Uninstalling the Process Server in Console Mode, 138

• Uninstalling the Hub Server in Console Mode, 138

• Uninstalling the Resource Kit in Console Mode, 139

• Manually Undeploying the Process Server, 139

• Manually Undeploying the Hub Server, 139

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.


135

2. Click the Databases tool under the Configuration workbench.

The Database Information page appears.


4. From the list of databases, select the Operational Reference Store to unregister.

5. Click the Unregister database button.

The Databases tool prompts you to confirm unregistering the Operational Reference Store.

6. Click Yes.

7. Use 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: DROP TABLE ERRORSCHEMA.ERRORTABLECALL SYSPROC.ADMIN_DROP_SCHEMA('<Schema Name>', NULL, 'ERRORSCHEMA', 'ERRORTABLE')

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.


2. Click Start and then click Programs > Infamdm > Hub > Cleanse > Uninstaller Data > Uninstall Informatica MDM Hub Cleanse Match Server.

The Uninstall introduction window appears.

3. Click Uninstall.


4. Click Done.

136 Chapter 14: Uninstallation

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 Resource Kit in Graphical ModeYou can uninstall the Resource Kit in graphical mode.

Uninstalling the Resource Kit in Graphical Mode on UNIXTo uninstall the Resource Kit, you must remove the Resource Kit from the MDM Hub implementation.


2. Navigate to the following directory: <infamdm_install_directory>/hub/resourcekit/UninstallerData


./"Uninstall Informatica MDM Hub Resource Kit"The Uninstall Informatica MDM Hub Resource Kit window appears.

Uninstalling the Hub Server in Graphical Mode 137

4. Click Uninstall.

The Uninstall Complete window appears with a list of items that could not be removed.

5. Click Done.

6. Manually remove the following directory:

<infamdm_install_dir>/hub/resourcekit

Uninstalling the Resource Kit in Graphical Mode on WindowsTo uninstall the Resource Kit, you must remove the Resource Kit from the MDM Hub implementation.


2. Navigate to the following directory: <ResourceKit_install_dir>\deploy\UninstallerData

3. Double-click Uninstall Informatica MDM Hub Resource Kit.exe The Uninstall Informatica MDM Hub Resource Kit window appears.

4. Click Uninstall.

The Uninstall Complete window appears with a list of items that could not be removed.

5. Click Done.

6. Manually remove the following directory:

<infamdm_install_dir>\hub\resourcekit

Uninstalling the Process Server in Console 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/UninstallerData2. 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"


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


On UNIX. <infamdm_install_dir>/hub/resourcekit/UninstallerDataOn Windows. <infamdm_install_dir>\hub\resourcekit\UninstallerData

2. Run the following command from the command prompt:

On UNIX. "Uninstall Informatica MDM Hub Resource Kit.bin" -i consoleOn Windows. "Uninstall Informatica MDM Hub Resource Kit.exe" -i console

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. Remove the following deployment files from the JBoss deployment directory:





The deployment files are in the following directory:

On UNIX.

• <JBoss installation directory>/<configuration name>/deployments

Uninstalling the Resource Kit in Console Mode 139

On Windows.

• <JBoss installation directory>\<configuration name>\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.


A P P E N D I X A

Installation and Configuration Checklist

This appendix includes the following topics:

• Installation Checklist Overview, 141

• Step 1. Pre-Installation Tasks, 141

• Step 2. Create the Hub Store, 143

• Step 3. Install the Hub Server, 143

• Step 4. Hub Server Post-Installation Tasks, 143

• Step 5. Install the Process Server, 144

• Step 6. Process Server Post-Installation Tasks, 144

• Step 7. Install the Resource Kit (Optional), 145

Installation Checklist OverviewThe installation and configuration checklist summarizes the tasks that you must perform to complete an installation.

Step 1. Pre-Installation TasksBefore you install, perform the following tasks:

Read the Release Notes for updates to the installation process.

Download and extract the installer files.

Verify the license key. Before you install the software, verify that you have the license key for the product you plan to install. Contact Informatica Global Customer Support if you do not have a license key.

Verify the minimum system requirements to install MDM Multidomain Edition.

Install the Java Development Kit when you install MDM Multidomain Edition on AIX or HP-UX.

141

Set up the environment variables you must configure to work with the MDM Multidomain Edition installation.

Set an operating system locale for the MDM Hub components.

Set up the X Window Server. If you want to run the installer in graphical mode on UNIX, set up the X Window Server.

Install and configure IBM DB2 according to instructions in the IBM DB2 documentation.Ensure that you perform the following configurations:

•Configure IBM DB2 drivers.

•Add users to the DB2ADMNS and DB2USERS user groups. The IBM DB2 installer creates the DB2ADMNS and DB2USERS user groups. You must add users to the DB2ADMNS and DB2USERS groups.

• If you want to install the Process Server on a machine other than the IBM DB2 database machine, install the DB2 run-time client and catalog the database.

•Create database and the tablespaces. You must create database and the associated tablespaces for the Hub Store.

•Create packages on the database server. Create the packages on the database server that the MDM Hub requires.

Install and configure JBoss according to the instructions in the JBoss documentation.Ensure that you perform the following configurations:

•Configure the Java options property.

•Configure the JBoss startup script to force JBoss and JGroups to use the same bind address.

•Set the maximum JVM heap size in the JBoss startup script.

•Set the transaction timeout.

•Set the log4j.xml file configuration path in the JBoss startup script.

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

• If you want to use JBoss in an unsecured mode, disable the remoting-connector security.

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

• If you want to install the MDM Hub in a JBoss clustered environment, create a JBoss cluster and nodes.

•Configure JBoss for multiple MDM Hub Master Databases. If you want to configure multiple MDM Hub Master Databases, you have to install an MDM Hub instance for each MDM Hub Master Database. If you install multiple MDM Hub instances on the same machine, deploy each instance on a separate JBoss instance. Run each JBoss instance on a different port.

Install and configure external cleanse engines that you might want to use for cleanse operations.

Determine the timeline granularity that you want to use. Timeline granularity is the time measurement that you want to use to define effective periods for versions of records. To be prepared to configure the timeline granularity when you create or update an Operational Reference Store, determine the timeline granularity.

Configure the Informatica platform properties file. If you want to install Informatica platform as part of the MDM Hub installation, create an Informatica platform properties file.

Create an installation documentation directory to store copies of installation files, such as the validation results, environment reports, and log files.

142 Appendix A: Installation and Configuration Checklist

Create the ActiveVOS database schema. Create the ActiveVOS database schema before you install the Hub Server. The ActiveVOS database stores data about the state of the processes.

Create the user for the ActiveVOS Console with the role abAdmin.

Step 2. Create the Hub StoreTo create a Hub Store, perform the following tasks:

Create the MDM Hub Master Database. You must create the MDM Hub Master Database before you install the Hub Server. The MDM Hub Master Database will store the MDM Hub environment configuration settings.

Create an Operational Reference Store. You can create an Operational Reference Store at any time after you install and configure the database environment.

Import the metadata into the MDM Hub Master Database. The metadata includes repository tables and other objects that the MDM Hub requires in the Hub Store.

Import the metadata into the Operational Reference Store. The metadata includes repository tables and other objects that the MDM Hub requires in the Hub Store.

Step 3. Install the Hub ServerUse the Hub Server installer to install the Hub Server on a Windows or UNIX machine. If you have a clustered environment, you can install the Hub Server on multiple cluster nodes.

Step 4. Hub Server Post-Installation TasksAfter you install the Hub Server, perform the following tasks:

Copy the installation log files to the installation documentation directory that you created. Use the log files to troubleshoot installation issues.

Verify the version and build number of the Hub Server.

Perform the following Hub Server configurations:

•Deploy the Hub Server EAR file on the same machine on which you installed the Hub Server.

•Configure the Hub Server for logging in the log4j.xml file.

•Configure the Hub Server properties in the cmxserver.properties file.

• If you skipped the post-installation setup script during installation, run the post-installation setup script manually.

• If the Hub Server deployment fails, manually redeploy the Hub Server.

Step 2. Create the Hub Store 143

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

If you want to configure multiple Process Servers, manually configure data sources.

If you want to troubleshoot issues, or the automated queue creation process fails, manually configure JMS Message queues.

If you want to change the password for the Operational Reference Store (ORS), change it.

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

To handle caching requirements, configure JBoss Cache.

If you do not want to use the default EJB client, configure another EJB Client for the Hub Console.

If you installed Informatica platform, configure the MDM Hub to log Informatica platform processes.

Configure the Developer tool to write the workspace metadata to the machine where the user is logged in.

Start the Hub Console to verify access to the Hub Server.

Register Operational Reference Stores that you create by using the Hub Console.

Configure JBoss security to prevent unauthorized access to data and other resources in the MDM Hub.

Configure the ActiveVOS URNs. Configure the URN mappings in the ActiveVOS Console to reflect the host name and the port number of the ActiveVOS Server.

Add ActiveVOS Console user and the workflow adapter users to the application server. You must use the same user names, passwords, and roles in the MDM Hub, ActiveVOS, and the application server.

Step 5. Install the Process ServerUse the Process Server installer to install the Process Server on a Windows or UNIX machine. If you have a clustered environment, you can install the Process Server on multiple cluster nodes.

Step 6. Process Server Post-Installation TasksAfter you install the Hub Server, perform the following tasks:

Copy the installation log files to the installation documentation directory that you created.

Verify the version and build number of the Process Server.

Perform the following Process Server configurations:

•Deploy the Process Server EAR file on the same machine on which you installed the Process Server.

•Configure the Process Server with external cleanse engines.

•Configure the Process Server to delete the temporary files that the cleanse process generates.

144 Appendix A: Installation and Configuration Checklist

•Configure the Process Server for logging in the log4j.xml file.

•Configure the Hub Server properties in the cmxserver.properties file.

• If you skipped the post-installation setup script during installation, run the post-installation setup script manually.

• If the Process Server deployment fails, manually redeploy the Process Server.

Configure the Process Server for multithreading. If the server on which you install the Process Server has more than one CPU, then you can configure the cleanse operations to be multithreaded to increase performance. The batch operations are multi-threaded by default, but you can configure the number of threads to use.

Configure multiple Process Servers for cleanse and match operations.

Configure multiple Process Servers for batch processes.

Configure match population. You must configure the match population to use for the match rules.

Configure the Process Server for smart search.

Step 7. Install the Resource Kit (Optional)You can install the samples, applications, and utilities in the Resource Kit. Use the Resource Kit installer to install the Resource Kit on a Windows or UNIX machine.

To install the Resource Kit, perform the following tasks:

Set up the MDM Hub sample Operational Reference Store (ORS). The Resource Kit samples and utilities require the sample ORS.

Register the MDM Hub sample Operational Reference Store in the Hub Console.

Run the Resource Kit installer. Use the Resource Kit installer to install the Resource Kit on a Windows or UNIX machine. If you have a clustered environment, you can install the Hub Server on multiple cluster nodes.

Step 7. Install the Resource Kit (Optional) 145

Index

AActiveVOS

URN, setting 114

Cconfiguring JBoss

for the MDM Hub 24custom jar files

repackaging 83

Ddatabase

create manually 20create using a script 23

databases target database 85

Eenvironment variables

DISPLAY 18

Ggraphical mode

installation requirements 18

HHub Console

starting 85Hub Server

configuration properties 72deploying on JBoss cluster 64installation log files 69installing 54, 57, 122logging settings 72manually redeploying 75, 76postinstallsetup script 76silent installation 59, 64, 127silent properties file 60uninstalling 138, 139version and build number 71

Hub Store tablespaces 20uninstalling 135

IInformatica ActiveVOS

creating the schema 44Informatica platform

properties file 31installation requirements

X Window Server 18installing

Hub Server 54, 57Process Server 90, 92Resource Kit 122, 125

JJBoss

clustering on JBoss 26

port conflicts 72settings 73starting on UNIX 29starting on Windows 29

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

JBoss cluster deploying Hub Server 64deploying Process Server 98

JBoss security disabling 27enabling 87

JMS message queues configuring 79

Llog file

debug log file 70, 101Hub Server log file 70installation log file 69, 100installation prerequisites log file 69, 102JBoss log file 71, 102post install setup log file 70, 101Process Server log file 101

146

MMaster Database

creating 48importing metadata 51

match population enabling 110

MDM Hub components 12designing the installation 14installation tasks 14introduction 12setting environment variables 18system requirements 17

MDM Hub EAR files repackaging 74

OOperational Reference Store

creating 50importing metadata 52registering 86

Ppostinstallsetup script

for Hub Server 76running 76, 106

postInstallSetup script for Process Server 106

Process Server configuration properties 106configuring 103deploying 106deploying on JBoss cluster 98installation log files 100installing 90, 92logging settings 105multithreading, configuring 107postInstallSetup script 106silent installation 94silent properties file 94threads for batch processing 107threads for cleanse operations 107uninstalling 138version and build number 102

Rremoting-connector security

disabling 27

remoting-connector security (continued)enabling 87

Resource Kit installing 122, 125silent properties file 127uninstalling 138

SSample Schema

installing 119registering 121

silent installation of Hub Server 64

silent installer running 97

Ttarget database

selecting 85timeline

granularity 30troubleshooting

post-installation process 132

Uuninstalling

Hub Server 138, 139Hub Store 135Process Server 138

URN setting ActiveVOS 114

Wworkflow engines

adding 117

XX Window Server

installation requirements 18

Index 147

installation guide for jboss documentation...1 • • • • •

Documents