WebLogic Installation Guide for - Informatica · Informatica MDM Multidomain Edition for Oracle (Version 9.7.1 HotFix 5) Installation Guide for WebLogic

Informatica MDM Multidomain Edition for Oracle (Version 9.7.1 HotFix 5)

Installation Guide for WebLogic

Informatica MDM Multidomain Edition for Oracle Installation Guide for WebLogic

Version 9.7.1 HotFix 5November 2015

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

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

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

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

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

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

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; and http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html.

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

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

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

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

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

NOTICES

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

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

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

Part Number: MDM-OIG-97100-HF5-0001

Table of Contents

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

Informatica My Support Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

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

Informatica Product Availability Matrixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Informatica Support YouTube Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

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

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

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

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

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

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

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

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

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

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

Set Up the X Window Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

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

Install and Configure Oracle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Disable the Oracle Recycle Bin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Configure the init.ora Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Create an Oracle Database Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Create Tablespaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Grant Privileges to DBA User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Add the Oracle TNS Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Test the Database Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Install and Configure Oracle RAC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Use Oracle Service Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Use Oracle RAC Load-Balanced Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Configure the tnsnames.ora File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Install and Configure WebLogic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configure WebLogic to Use an Oracle Data Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Create a Master Data Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4 Table of Contents

Create an Operational Reference Store Data Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Create a WebLogic Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Install and Configure Cleanse Engines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Create an Installation Documentation Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

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

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

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

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

Chapter 4: Hub Store Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Verify Access to Oracle Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

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

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

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

Configuring the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Sample Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Installing the Hub Server on Clustered or Non-clustered Environments with Managed Servers. . . . 43

Chapter 6: Hub Server Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Copy the Installation Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Installation Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Installation Prerequisites Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Debug Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Post-Installation Setup Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Hub Server Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

WebLogic Server Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Verify the Version and Build Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Configure the Hub Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Deploying the Hub Server EAR File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Configuring the Logging Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Setting the Configuration Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Changing the WebLogic Server Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Running the Post Install Script Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Manually Redeploying the Hub Server Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Manually Configuring JMS Message Queues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Step 1. Create a JMS Server and Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Step 2. Configure a Connection Factory for the Module. . . . . . . . . . . . . . . . . . . . . . . . . . 51

Step 3. Add Message Queues to the Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Table of Contents 5

Step 4. Create a Subdeployment Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

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

Step 6. Add a Message Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

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

Restart WebLogic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

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

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

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

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

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

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

Configuring the Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Sample Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Running the Silent Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

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

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

Installation Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Post-Installation Setup Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Process Server Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Debug Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Installation Prerequisites Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

WebLogic Server Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Verify the Version and Build Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Configure the Process Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Deploying the Process Server EAR File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

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

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

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

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

Running the PostInstallSetup Script Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

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

Configure Process Server for Multithreading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Configuring the Process Server for Multithreading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

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

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

Configure Match Population. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Enabling Match Population. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

6 Table of Contents

Chapter 9: Troubleshooting the MDM Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Troubleshooting the Installation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Chapter 10: Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Uninstallation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Uninstalling the Hub Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

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

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

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

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

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

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

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

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

Manually Undeploying the Process Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Manually Undeploying the Hub Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Table of Contents 7

PrefaceThe Informatica MDM Multidomain Edition Installation Guide is written for database administrators, system administrators, and implementers who are responsible for installing and setting up the Informatica MDM Hub. This guide assumes that you have knowledge of operating systems, database environments, and your application server.

Informatica Resources

Informatica My Support PortalAs an Informatica customer, you can access the Informatica My Support Portal at http://mysupport.informatica.com.

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

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

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

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

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

8

http://mysupport.informatica.com

mailto:[email protected]


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

http://www.informatica.com

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

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

Informatica Support YouTube 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 http://mysupport.informatica.com. Developed from the real-world experience of hundreds of data management projects, Informatica Velocity represents the collective knowledge of our consultants who have worked with organizations from around the world to plan, develop, deploy, and maintain successful data management solutions. If you have questions, comments, or ideas about Informatica Velocity, contact Informatica Professional Services at [email protected].

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

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 9



mailto:[email protected]

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

http://www.informaticamarketplace.com



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, 10

• Installation Tasks, 11

• Designing the MDM Hub Installation, 11

MDM Multidomain Edition InstallationMDM Multidomain Edition is a master data management solution that enhances data reliability and data maintenance procedures. The MDM Multidomain Edition is also referred to as the MDM Hub. You can access the MDM Hub features through the Hub Console.

The MDM Hub installation consists of the following components:

Hub Store

The Hub Store stores and consolidates business data for the MDM Hub. The Hub Store consists of the following components:

• MDM Hub Master Database. Contains the MDM Hub environment configuration settings, such as user accounts, security configuration, Operational Reference Store registry, and message queue settings. The Hub Store consists of one MDM Hub Master Database. You can access and manage Operational Reference Stores from the MDM Hub Master Database. The default name of the MDM Hub Master Database is CMX_SYSTEM.

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

Hub Server

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

Process Server

The Process Server processes batch jobs such as load, recalculate BVT, and revalidate, and performs data cleansing and match operations. The Process Server is deployed in an application server environment. The Process Server interfaces with the cleanse engine that you configure to standardize and optimize data for match and consolidation.

10

Installation TasksYou must complete the pre-installation tasks before you install the MDM Hub components. After the installation, complete the post-installation tasks.

To install the MDM Hub, complete the following tasks:

1. Complete the pre-installation tasks. Complete the pre-installation tasks to ensure that you can successfully run the installers for the Hub Server and the Process Server and create the Hub Store.

2. Install the MDM Hub components. Use the setup script provided with the MDM Hub distribution to create the Hub Store. Use the MDM Hub installer to install the Hub Server and the Process Server.

3. Perform the post-installation configuration tasks. Test the database connections. Configure the Hub Server and the Process Server to ensure that you can use the MDM Hub features.

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

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

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

All components on a single host

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

Installation Tasks 11

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

Components distributed on multiple hosts

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

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

12 Chapter 1: Installation Overview

C H A P T E R 2

Pre-Installation TasksThis chapter includes the following topics:

• Verify License Key, 13

• Verify the Minimum System Requirements, 13

• Set Environment Variables, 14

• Set the Operating System Locale, 14

• Set Up the X Window Server, 14

• Verify the JDBC Driver Version, 15

• Install and Configure Oracle, 15

• Install and Configure Oracle RAC, 18

• Install and Configure WebLogic, 19

• Install and Configure Cleanse Engines, 24

• Create an Installation Documentation Directory, 24

Verify License KeyBefore you install the software, verify that you have the license key available. You can get the license key in the following ways:

• Installation DVD. If you receive the Informatica installation files in a DVD, the license key file is included in the Informatica License Key CD.

• FTP download. If you download the Informatica installation files from the Informatica Electronic Software Download (ESD) site, the license key is in an email message from Informatica. Copy the license key file to a directory accessible to the user account that installs the product.

Contact Informatica Global Customer Support if you do not have a license key.

Verify the Minimum System RequirementsBefore you install the MDM Hub, verify that the machine meets the hardware and software requirements.

Verify that the machine meets the following minimum system requirements to install the MDM Hub components:

13

RAM

Production environment: 12 GB

Development environment: 2 GB minimum, 4 GB recommended

Disk Space

1 GB

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

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

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

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

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

You must set JAVA_HOME and PATH environment variables to point to JDK 1.7.0_45 or later.

Set the Operating System LocaleYou must set the same operating system locale for the Hub Server, the Hub Store, and the Hub Console.

Choose one of the following locales for the MDM Hub components:

• en_US

• fr_FR

• de_DE

• ja_JP

• ko_KR

• zh_CN

Set Up the X Window ServerWhen you run the installer in graphical mode, you must use a graphics display server. On UNIX, the graphics display server is typically an X Window server. If you do not have the X Window server installed on the machine where you want to install the product, you can run the installer using an X Window server installed on another machine. Use the DISPLAY variable to redirect output of the X Window server to another UNIX machine.

14 Chapter 2: Pre-Installation Tasks


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

Shell Command Example

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

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

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

DISPLAY=”10.1.50.23:0”export display

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

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

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

The lib directory is in the following location:

On UNIX. <distribution directory>/database/lib

On Windows. <distribution directory>\database\lib

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


Install and Configure OracleYou must install and configure Oracle before you create the Hub Store. Install Oracle according to instructions in the Oracle documentation.

Ensure that you install JServer JAVA Virtual Machine and Oracle Database Java Packages during the Oracle database installation.

Note: You cannot use a multitenant container database for the MDM Hub.

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

• Oracle client

• Oracle Java utilities

• SQL*Loader

Verify the JDBC Driver Version 15

Before you start Oracle, perform the following configuration tasks:

• Disable the Oracle Recycle Bin

• Configure the init.ora Parameters

Disable the Oracle Recycle BinYou must disable the Oracle Recycle Bin because it can interfere with the MDM Hub processes.

The Oracle Recycle Bin is enabled by default. Disable the Oracle Recycle Bins, USER_RECYCLEBIN and DBA_RECYCLEBIN. You can disable the recycle bins at the system or session level. Also, ensure that you purge existing objects in the recycle bin.

For more information, see the Oracle documentation.

Configure the init.ora ParametersYou must configure the init.ora parameters for the production environment of the MDM Hub installation.

Create an Oracle Database InstanceAfter you install and configure the Oracle database, create an Oracle database instance.

If the MDM Hub will have multiple Operational Reference Stores distributed across different host servers, create an Oracle database instance on each server.

Create TablespacesYou must create the CMX_DATA, CMX_INDX, CMX_TEMP tablespaces for the Hub Store.

The following table describes the Oracle tablespaces for the Hub Store:

Default Tablespace Name Description

CMX_DATA Default tablespace for the Operational Reference Store schema.Important: Do not change the default tablespace name of CMX_DATA for your Hub Store.

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

CMX_TEMP Tablespace to contain temporary tables for Informatica MDM Hub.

You must create enough space for the CMX_TEMP tablespace. When you create the tablespaces, adjust the default tablespace sizes and number of data files based on the volume of data to be loaded into the MDM Hub.

Creating TablespacesCreate tablespaces as permanent tablespaces that are managed locally or configured manually.

1. Log in to Oracle as a database administrator or a user with SYSTEM privileges.

2. Run the command to create a tablespace from SQL*Plus.


The following example shows the command you can use to create the CMX_DATA tablespace:

CREATE BIGFILE TABLESPACE CMX_DATANOLOGGINGDATAFILE '<Oracle install directory>/CMX_DATA1.dbf' SIZE 2048M REUSEEXTENT MANAGEMENT LOCAL;

The default tablespace name is CMX_DATA. Do not use another tablespace name because the Repository Manager will generate validation errors.

The following example shows the command you can use to create the CMX_INDX tablespace:

CREATE BIGFILE TABLESPACE CMX_INDXNOLOGGINGDATAFILE '<Oracle install directory>/CMX_INDX1.dbf' SIZE 2048M REUSE EXTENT MANAGEMENT LOCAL;

The following example shows the command you can use to create the CMX_TEMP tablespace:

CREATE BIGFILE TABLESPACE CMX_TEMPNOLOGGINGDATAFILE '<Oracle install directory>/CMX_TEMP1.dbf' SIZE 2048M REUSE EXTENT MANAGEMENT LOCAL;

If you do not use the default tablespace name for CMX_INDX and CMX_TEMP, you must set the DEFERRED_SEGMENT_CREATION parameter to FALSE to prevent Repository Manager validation errors.

Configuring the DEFERRED_SEGMENT_CREATION ParameterIf you use a custom tablespace name for CMX_INDX or CMX_TEMP, set the DEFERRED_SEGMENT_CREATION parameter to FALSE to prevent Repository Manager validation errors.

1. Run the following SQL command: ALTER SYSTEM SET DEFERRED_SEGMENT_CREATION=FALSE SCOPE=BOTH;

2. Restart the database.

Grant Privileges to DBA UserYou can create the MDM Hub Master Database and the Operational Reference Store as a SYS user or as a DBA user with privileges to grant options. If you use the DBA user, you must grant privileges to the DBA user with grant options for distributed transactions before you create the MDM Hub Master Database and the Operational Reference Store.

1. Start SQL*Plus and connect to the database as a user that has privileges to grant options.

2. Use the following statements to grant privileges to the DBA user: GRANT SELECT ON sys.pending_trans$ TO dbauser with grant option;GRANT SELECT ON sys.dba_pending_transactions TO dbauser with grant option;GRANT SELECT ON sys.dba_2pc_pending TO dbauser with grant option;GRANT EXECUTE ON sys.dbms_xa TO dbauser with grant option;

Add the Oracle TNS NameThe Hub Server and Process Server installer do not add the TNS name into the tnsnames.ora file. You must add TNS name entries to the tnsnames.ora file on the Hub Server and Process Server machines to connect to the Oracle database.

u Add the following entry in the tnsnames.ora file:

<TNS NAME> = (DESCRIPTION = (ADDRESS_LIST =

Install and Configure Oracle 17

(ADDRESS = (PROTOCOL = TCP)(Host = <Oracle server host name>)(Port = <Oracle server port>)) ) (CONNECT_DATA = (SERVICE_NAME = <Oracle SID>) ))

Note: Ensure that the TNS names on the Hub Server machine and the Process Server machine are the same.

Test the Database ConnectionTest the connection to the database from each machine on which you want to run a Hub Server or Process Server.

u Use the following command to test the database connection:

sqlplus <user name>/<password>@<TNS Name>

Install and Configure Oracle RACYou can install the Hub Store on Oracle RAC. Before you install the Hub Store on Oracle RAC, you must complete manual configuration steps to use features and optimize the environment for performance.

For information about installing and configuring Oracle RAC, see the Oracle documentation.

Use Oracle Service NamesYou can use Oracle service names instead of Oracle SIDs for Oracle RAC installations. Use Oracle service names for a more flexible method to specify the connection and to dynamically reallocate database servers.

Use Oracle RAC Load-Balanced ConnectionsUse Oracle RAC load-balanced connections in a fail-safe environment to ensure that a database connection is available even when one or more Oracle RAC nodes become unavailable.

You can use Oracle RAC to specify a connection to an Oracle service that is enabled with load balancing and high availability. Oracle RAC distributes the workload among all available nodes in the cluster. If a node becomes unavailable, the work fails over to another node.

Most MDM Hub components use load balancing and available nodes. The MDM Hub components that build their own direct JDBC connection cannot use load balancing. These components do not know the virtual IPs of the Oracle RAC nodes.


The following table describes the Informatica MDM Hub components that use Oracle RAC load balancing:

Component Description

Batch Jobs Use load balancing when batch jobs are called from a command line because batch jobs use the tnsnames.ora settings.Note: Batch jobs cannot use load balancing when called from the Hub Console.

Services Integration Framework API Connections

Use load-balanced JDBC connections from the application server connection pool.

Process Server Uses load-balanced JDBC connections from the Process Server connection pool.

Repository Manager Uses load-balanced JDBC connections from the application server connection pool when only DML is required.Note: Repository Manager cannot use load balancing when DDL is required because DDL uses a direct JDBC connection.

Configure the tnsnames.ora FileYou must configure all the Oracle RAC nodes of the database cluster in the tnsnames.ora file.

The following tnsnames.ora entry example shows you how to specify multiple Oracle RAC nodes for an Oracle service called mdm_service.domain.com:

MDM_SERVICE.DOMAIN.COM =(DESCRIPTION =(ADDRESS_LIST=(ADDRESS= (PROTOCOL = TCP)(HOST = server1-vip)(PORT = 1521))(ADDRESS= (PROTOCOL = TCP)(HOST = server2-vip)(PORT = 1521))(ADDRESS= (PROTOCOL = TCP)(HOST = server3-vip)(PORT = 1521))(FAILOVER = on)(LOAD_BALANCE = on))(CONNECT_DATA=(SERVICE_NAME = mdm_service.domain.com))

The connections to mdm_service.domain.com are load-balanced between the Oracle RAC nodes on server1, server2, or server3.

Install and Configure WebLogicInstall and configure WebLogic Server according to the instructions in the WebLogic documentation.

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

Before you install the Hub Server and the Process Server on the WebLogic application server, create WebLogic domains. Use the WebLogic Administration console to create domains for the Hub Server and the Process Server applications. For more information, see the WebLogic documentation.

Install and Configure WebLogic 19

Ensure that you perform the following configurations:

• If the operating system uses Internet Protocol version 6 (IPv6), you must add -Djava.net.preferIPv4Stack=true to the script that is in the bin directory of the base domain:

On UNIX. startWebLogic.shOn Windows. startWebLogic.cmd

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

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

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

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

• Add the following JVM option to JAVA_OPTS in the WebLogic startup script to set the oracle.jdbc.J2EE13Compliant system variable:

-Doracle.jdbc.J2EE13Compliant=true• Set the maximum JVM heap size (-Xmx) to 4 GB or higher in the WebLogic startup script.

Change the following settings:set JAVA_OPTS=%JAVA_OPTS% -server -Xms2048m -Xmx4096m -Xss2000k -XX:PermSize=256m -XX:MaxPermSize=1024m

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

• Set the WLS_MEM_ARGS_64BIT memory variable to appropriate values in the following file:

On UNIX. <Domain Home Directory>/bin/setDomainEnv.shOn Windows. <Domain Home Directory>\bin\setDomainEnv.cmdFor example:

WLS_MEM_ARGS_64BIT="-Xms256m -Xmx1024m -XX:PermSize512m"

Configure WebLogic to Use an Oracle Data SourceConfigure WebLogic to use an Oracle data source. If you install the Process Server on a different machine from the one that runs the Hub Server, then on the Process Server machine, create data sources for each Operational Reference Store.

Contact Oracle to get JDBC driver for the database configuration.

1. To configure WebLogic to use an Oracle data source, copy the Oracle JDBC driver to the following directory:

On UNIX. <WebLogic_install_dir>/server/libOn Windows. <WebLogic_install_dir>\server\lib

2. Add the path to the JDBC driver to the WEBLOGIC_CLASSPATH variable in the following file:

On UNIX. <WebLogic_install_dir>/common/bin/commEnv.shOn Windows. <WebLogic_install_dir>\common\bin\commEnv.cmdNote: Place the path to the JDBC driver before the path to other Weblogic Server libraries.


Create a Master Data SourceIf you want to install the Process Server on a different machine from the one that runs the Hub Server or the Oracle database, then on the Process Server machine, create a data source for the Master Database.

1. Start the WebLogic Administration Console.

2. Click the Lock & Edit button to acquire a lock.

3. Click Services > JDBC > Data Sources, and then click New.

The JDBC Data Sources Properties page appears.

4. Specify the following data source properties:

Name

Name of the JDBC data source. Set the name to MDM Master Data Source.

JNDI Name

JNDI path to where the JDBC data source will be bound. Specify jdbc/siperian-cmx_system-ds.

Database Type

Database type that you want to connect to. Select Oracle.

Database Driver

JDBC driver that you want to use to connect to the database. Select Oracle driver (Thin XA).

5. Click Next.

The Transaction Options page appears.

6. Click Next.

The Connection Properties page appears.

7. Enter values for the following connection properties:

Database Name

Name of the database you want to connect to.

Host Name

DNS name or IP address of the server that hosts the database.

Port

Port on which the database server listens for connections requests.

Database User Name

Database user name that you want to use for each connection in the data source.

Password

Password of the database user account.

Confirm Password


8. Click Next.

The Test Database Connection page appears.

9. Click Test Configuration to test the driver connections.

If the test is unsuccessful, you must update the values in the Connection Properties page and then retry the connection until successful.

10. Click Next.


The Select Targets page appears.

11. Select the server on which you want to deploy the data source.

12. Click Finish.

13. Click Activate Changes.

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

1. Start the WebLogic Administration Console.

2. Click the Lock & Edit button to acquire a lock.

3. Click Services > JDBC > Data Sources, and then click New.

The JDBC Data Sources Properties page appears.

4. Specify the following data source properties:

Name

Name of the JDBC data source. Set the name to MDM ORS Data Source.

JNDI Name

JNDI path to where the JDBC data source will be bound. Specify jdbc/siperian-<oracle host name>-<oracle sid>-<Operational reference Store name>-ds.

Database Type

Database type that you want to connect to. Select Oracle.

Database Driver

JDBC driver that you want to use to connect to the database. Select Oracle driver (Thin XA).

5. Click Next.

The Transaction Options page appears.

6. Click Next.


7. Enter values for the following connection properties:

Database Name

Name of the database you want to connect to.

Host Name

DNS name or IP address of the server that hosts the database.

Port

Port on which the database server listens for connections requests.

Database User Name

Database user name that you want to use for each connection in the data source.

Password



Confirm Password


8. Click Next.

The Test Database Connection page appears.

9. Click Test Configuration to test the driver connections.

If the test is unsuccessful, you must update the values in the Connection Properties page and then retry the connection until successful.

10. Click Next.

The Select Targets page appears.

11. Select the server on which you want to deploy the data source.

12. Click Finish.


Create a WebLogic ClusterYou can choose to install the MDM Hub in a WebLogic clustered environment.

The following steps provide a high-level overview of the process to set up the WebLogic cluster. For more information, see the WebLogic documentation.

1. Install WebLogic.

2. Create a domain called mydomain in the following directory:

On UNIX. /BEA/User_Projects/domainOn Windows. \BEA\User_Projects\domain

3. Use the following command to start the Admin server:

On UNIX. ./startWebLogic.shOn Windows. startWebLogic.cmd

4. Log in to the WebLogic Administrator Console and create a machine, M1.

5. In machine M1, create the managed server MS1.

6. Add the managed server MS1 to machine M1.

7. On machine M1, navigate to the following directory:

On UNIX. <Domain_directory>/binOn Windows. <Domain_directory>\bin

8. Use the following command to start the managed servers:

On UNIX../startManagedWebLogic.sh <machine name> http://<host of the admin server>:<port of the admin server>

On Windows.startManagedWebLogic.cmd <machine name> http://<host of the admin server>:<port of the admin server>

9. Install WebLogic on another physical machine.

Note: Ensure that all machine in a cluster have the same version of WebLogic.

10. Create machine, M2.


11. In machine M2, create a domain called mydomain in the same directory structure as that you use for the first machine.

On UNIX. /BEA/User_Projects/domain/On Windows. \BEA\User_Projects\domain\

12. In machine M2, create the managed server MS2.

13. Add the managed server MS2 to machine M2.

14. Add the managed servers MS1 and MS2 to the cluster domain.

15. On machine M2, navigate to the following directory:

On UNIX. <Domain_directory>/binOn Windows. <Domain_directory>\bin

16. Use the following command to start the managed servers:

On UNIX../startManagedWebLogic.sh <machine name> http://<host of the admin server>:<port of the admin server>

On Windows.startManagedWebLogic.cmd <machine name Ex:M1> http://<host of the admin server>:<port of the admin server>

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

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

Create an Installation Documentation DirectoryCreate a directory to store copies of installation files, such as the validation results, environment reports, database debug logs, and log files.

For example, you can create the directory install_doc. If you need to troubleshoot the installation, you can create an archive file of the installation documentation directory and send it to Informatica Global Customer Support for analysis.


C H A P T E R 3

Hub Store InstallationThis chapter includes the following topics:

• Create the MDM Hub Master Database, 25

• Create an Operational Reference Store, 27

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

• Import the Seed into the Operational Reference Store, 30

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

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

1. Disconnect database connections.

2. Open a command prompt.

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

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

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

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

5. Answer the prompts described in the following table:

Prompts Description

Enter the database type (ORACLE, MSSQL, DB2)

Database type. Specify ORACLE.

Enter Oracle Connection Type (service, sid). [service]

Connection type. Use one of the following values:- SERVICE. Uses the service name to connect to Oracle.- SID. Uses the Oracle System ID to connect to Oracle.Default is SERVICE.

25

Prompts Description

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

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

Enter the MDM Hub Master Database schema name [cmx_system]

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

Enter the MDM Hub Master Database user name [cmx_system]

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

Enter the MDM Hub Master Database user password

Password to access the MDM Hub Master Database.

Enter the database service name [orcl] Name of the Oracle service. This prompt is displayed if the selected Oracle connection type is SERVICE. Default is orcl.

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

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

Master Database Connect URL: "jdbc:oracle:thin:@//<host_name>:<port>/<service_name>".Do you want to change the connect URL (y/n) [n]

Connect URL for the Oracle connection type SERVICE. You can type y to change the default connect URL. To use the default connect URL, type n.

Enter database SID [orcl] Name of the Oracle System ID. This prompt is displayed if the selected Oracle connection type is SID.

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

Operating system locale. Default is en_US.

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

Enter the DBA password Password of the administrative user.

Enter the name of the MDM index tablespace [CMX_INDX]

Name of the tablespace to contain the index components for the MDM Hub Master Database. Default is CMX_INDX.

Enter the name of the MDM temporary tablespace (Not an Oracle temporary tablespace) [CMX_TEMP]

Name of the tablespace to contain the temporary components for the MDM Hub Master Database. Default is CMX_TEMP.

Enter the name of the Oracle temporary tablespace [TEMP]

Name of the Oracle temporary tablespace. Default is TEMP.

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

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

26 Chapter 3: Hub Store Installation

On UNIX. <distribution directory>/database/bin

On Windows. <distribution directory>\database\bin

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


1. Disconnect database connections.




4. Run the following command:

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


Prompts Description

Enter the database type (ORACLE, MSSQL, DB2) Database type. Specify ORACLE.


Connection type. Use one of the following values:- SERVICE. Uses the service name to connect to Oracle.- SID. Uses the Oracle System ID to connect to Oracle.Default is SERVICE.

Enter the Operational Reference Store schema host name [localhost]

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

Enter the Operational Reference Store schema port number [1521]

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

Enter the Operational Reference Store database service name [orcl]

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

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

Oracle TNS name. Default is orcl.

Master Database Connect URL: "jdbc:oracle:thin:@//<host_name>:<port>/<service_name>".Do you want to change the connect URL (y/n) [n]


Create an Operational Reference Store 27

Prompts Description

Enter database SID [orcl] Name of the Oracle System ID. This prompt is displayed if the selected Oracle connection type is SID.

Enter the Operational Reference Store schema name [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.

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

Enter the DBA password Password of the administrative user.

Enter the name of the MDM index tablespace [CMX_INDX]

Name of the tablespace to contain the index components for the Operational Reference Store. Default is CMX_INDX.

Enter the name of the MDM temporary tablespace (Not an Oracle temporary tablespace) [CMX_TEMP]

Name of the tablespace to contain the temporary components for the Operational Reference Store. Default is CMX_TEMP.

Enter the name of the Oracle temporary tablespace [TEMP]

Name of the Oracle temporary tablespace. Default is TEMP.


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

On UNIX. <distribution directory>/database/bin

On Windows. <distribution directory>\database\bin

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







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


Prompts Description




Connection type. Use one of the following values:SERVICE

Uses the service name to connect to Oracle.

SID

Uses the Oracle System ID to connect to Oracle.

Default is SERVICE.

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

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

Enter the MDM Hub Master Database service name [orcl]

Name of the Oracle service. This prompt is displayed if the selected Oracle connection type is SERVICE. Default is orcl.



Master Database Connect URL: "jdbc:oracle:thin:@//<host_name>:<port>/<service_name>".Do you want to change the connect URL (y/n) [n] :


Enter database SID Name of the Oracle System ID. This prompt is displayed if the selected Oracle connection type is SID.

Enter the MDM Hub Master Database 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.

Import the Seed into the MDM Hub Master Database 29

Prompts Description

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.


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

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

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

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


Import the Seed into the Operational Reference Store

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






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



Prompts Description




Connection type. Use one of the following values:SERVICE

Uses the service name to connect to Oracle.

SID

Uses the Oracle System ID to connect to Oracle.

Default is SERVICE.

Enter the Operational Reference Store schema host name [localhost]

Name of the host that is running the database.

Enter the Operational Reference Store schema port number [1521]

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

Enter the Operational Reference Store database service name

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



Master Database Connect URL: "jdbc:oracle:thin:@//<host_name>:<port>/<service_name>".Do you want to change the connect URL (y/n) [n] :


Enter database SID Name of the Oracle System ID. This prompt is displayed if the selected Oracle connection type is SID.

Enter the Operational Reference Store schema name [cmx_ors]

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

Enter the Operational Reference Store schema user name [cmx_ors]

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

Enter the Operational Reference Store schema user password

Password to access the Operational Reference Store.

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

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

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


Import the Seed into the Operational Reference Store 31

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

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

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

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



C H A P T E R 4

Hub Store Post-Installation TasksThis chapter includes the following topic:

• Verify Access to Oracle Components, 33

Verify Access to Oracle ComponentsIf you have a custom Oracle environment, ensure that the Hub Store has access to the required Oracle components.

The Hub Store requires access to the following Oracle components:

• Oracle Java Virtual Machine

• Oracle XML Database

• ALL_CONSTRAINTS

• ALL_CONS_COLUMNS

• ALL_DIRECTORIES

• ALL_INDEXES

• ALL_IND_COLUMNS

• ALL_JOBS (used for migration)

• ALL_TABLES

• ALL_TAB_COLUMNS

• ALL_VIEWS

• DBMS_APPLICATION_INFO

• DBMS_JOB

• DBMS_OUTPUT

• DBMS_STANDARD

• DBMS_SQL

• DBMS_STATS

• DBMS_UTILITY

• DUAL

• PLITBLM

• STANDARD

33

• SYS_STUB_FOR_PURITY_ANALYSIS

• USER_CONSTRAINTS

• USER_CONS_COLUMNS

• USER_EXTERNAL_TABLES

• USER_INDEXES

• USER_JAVA_POLICY

• USER_OBJECTS

• USER_SEQUENCES

• USER_SOURCE

• USER_TABLES

• USER_TAB_COLS

• USER_TAB_COLUMNS

• USER_TRIGGERS

• UTL_FILE

• V$NLS_PARAMETERS

• V$VERSION

34 Chapter 4: Hub Store Post-Installation Tasks

C H A P T E R 5

Hub Server InstallationThis chapter includes the following topics:

• Installing the Hub Server in Graphical Mode, 35

• Installing the Hub Server in Console Mode, 37

• Installing the Hub Server in Silent Mode, 39

• Installing the Hub Server on Clustered or Non-clustered Environments with Managed Servers, 43

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.

35

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

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

On UNIX, the Choose Link Folder window appears.

On Windows, the Choose Shortcut Folder window appears.

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

9. Click Next.

The Enter the location of the license file window appears.

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

The Application Server window appears.

11. Select WebLogic, and then click Next.

The WebLogic Application Server Home window appears.

12. Configure the following WebLogic Server settings:

a. Choose a path to the WebLogic domain installation directory for the domain you want to use for the MDM Hub. Click Next.

The WebLogic Application Server Login window appears.

b. Enter WebLogic Server login information.

The following table describes the login parameter fields:

Field Name Description

Host Name of the host computer that has the WebLogic installation.

Server Name of the WebLogic Server instance in the domain on which WebLogic is deployed.

User Name Name of the user for the WebLogic installation.

Password Password that corresponds to the WebLogic user.

Port Number Port number on which the WebLogic Server is listening.

13. Click Next.

The Database Selection window appears.

14. Select the Oracle version, and click Next.

The Oracle Database Connection Type Selection window appears.

15. Choose the Service Name or SID connection type, and click Next.

The Oracle Database Information window appears.

16. Enter the following settings for the Oracle database to which you want to connect, and click Next:

36 Chapter 5: Hub Server Installation

The following table describes the configuration parameter fields:

Field Name Description

Server Name Host name of the MDM Hub Master Database server.

Port Number Port number of the MDM Hub Master Database.

Service Name or Oracle SID

Specify the connection type that you select when you create the MDM Hub Master Database.

Schema Name Name of the MDM Hub Master Database.

System Schema Password Password of the system schema user to connect to the MDM Hub Master Database.

17. Click Next.

If the selected Oracle connection type is Service Name, then the Customization of Connect URL window appears.

18. Change the connect URL if required, and click Next.

The Product Usage Toolkit window appears.

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

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

You can enter the following proxy server details:

• Proxy server name/IP

• Proxy server port

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

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

• Proxy server password. Leave blank if not applicable.

21. Click Next.

The Deploy page appears.

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

The Pre-Installation Summary window appears.

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

When the installation completes, the Install Complete window appears.

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


Installing the Hub Server in Console Mode 37

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

a. Specify the path to the WebLogic domain in which you want to install the Hub Server, and press Enter.

The prompts for the WebLogic application server login information appears.

b. Enter the host name, server name, user name, password, and listener port for the WebLogic Server, or accept the default values, and press Enter.

15. Press Enter.

The database selection prompt appears.

16. Select Oracle, and press Enter.

17. Select the Oracle database connection type you want, Service Name or SID, and press Enter.

18. Specify the settings for the Oracle database to which you want to connect.

Press Enter to accept the default values, or replace the defaults with the correct values. The settings include, server name, port number, Service Name or Oracle SID, the MDM Hub system master schema name such as CMX_SYSTEM, and system schema password for the system schema user name.

19. Press Enter.


20. If the selected Oracle connection type is Service Name, then the installer prompts you to confirm or change the connect URL. Change the system-generated URL if required, and press Enter.


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

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

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

24. Press Enter.


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

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

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

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

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

SIP.APPSERVER.HOST Host name such as localhost.

SIP.APPSERVER.SERVER Admin Server name such as AdminServer.

SIP.APPSERVER.USERNAME User name to access WebLogic.

SIP.APPSERVER.PASSWORD Password to access WebLogic.

WEBLOGIC.AS.PORT Application server port number.

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



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

The Hub Server uses the service name to connect to Oracle.

SID

The Hub Server uses the Oracle system ID to connect to Oracle.

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

SIP.DB.PORT Database server port number.

SIP.DB.SID If SIP.ORACLE.CONNECTION.TYPE is SID, then set the SIP.DB.SID property to the Oracle database system ID. Otherwise, set the SIP.DB.SID property to the Oracle service name.

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

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

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 filename

Installing the Hub Server in Silent Mode 41

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

## Properties for WebLogic application serverSIP.AS.CHOICE="WebLogic"SIP.AS.HOME=C\:\\bea\\user_projects\\domains\\base_domainSIP.APPSERVER.HOST=localhostSIP.APPSERVER.SERVER=AdminServerSIP.APPSERVER.USERNAME=weblogicSIP.APPSERVER.PASSWORD=weblogicWEBLOGIC.AS.PORT=7001

## Properties for Oracle serverSIP.DB.CHOICE="Oracle## Oracle connection type should be SID or Service Name## set following to make Oracle connection type Service Name.## For connection type SID, the value of following variable should be 0.SERVICE_NAME_SELECTED_RESULT=1SIP.DB.SERVER=localhostSIP.DB.PORT=1521## If SIP.ORACLE.CONNECTION.TYPE is "SID", then SIP.DB.SID should be Oracle sid;## Otherwise, value of SIP.DB.SID should be oracle service nameSIP.DB.SID=orclSIP.DB.SCHEMA_NAME=cmx_systemSIP.DB.PASSWORD=!!cmx!!

## only when Oracle connection type is Service Name and if you want to customize## JDBC Connection URL, set SIP.ORACLE.CONNECTION.CUSTOMIZATION.YES to 1.## Otherwise, either don't use this variable in this file or set it to 0.#SIP.ORACLE.CONNECTION.CUSTOMIZATION.YES=1

## only when SIP.ORACLE.CONNECTION.CUSTOMIZATION is set to 'Yes', SIP.DB.URL_SILENT need to be set to a customized database url.## The value of SIP.DB.URL_SILENT should start with jdbc:oracle:thin:@", and this veriable will be used only when##SIP.ORACLE.CONNECTION.CUSTOMIZATION=Yes for oracle in "Service Name" connection type.#SIP.DB.URL_SILENT=

## If you want to run postInstallSetup as a part of silent install, then set following property.## set RUN_DEPLOYMENT_FLAG to 1 if you want to run postInstallSetup## or set RUN_DEPLOYMENT_FLAG to 0 if you do not want to run postInstallSetupRUN_DEPLOYMENT_FLAG=1

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

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


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

1. Ensure that the application server is running.

2. Open a command window.


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

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

Installing the Hub Server on Clustered or Non-clustered Environments with Managed Servers

If you have a clustered environment, install the Hub Server on the Administration Server and on all nodes of the cluster. If you have a nonclustered environment with an Administration Server and Managed Servers, install the Hub Server on the Administration Server and all the Managed Servers.

If the WebLogic environment has two Managed Servers that run on host1 and host2, and use RMI ports 8001 and 8002, the properties in cmxserver.properties can have the following values:

• cmx.appserver.hostname=host1,host2

• cmx.appserver.rmi.port=8001,8002

Where, the host name and port number of the first server are host1 and 8001, the host name and port number of the second server are host2 and 8002.

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

Install the Hub Server after you start the cluster.

1. Start the Hub Server installer on the Administration Server and all the Managed Servers.

Run the following command to start the Hub Server installer:On UNIX. ./hub_install.bin -DSIPERIAN_INSTALL_PREREQ_VALIDATION=falseOn Windows. hub_install.exe -DSIPERIAN_INSTALL_PREREQ_VALIDATION=false

2. Click No when the installer prompts you to run the postInstallSetup script to deploy the application.

3. If a clustered environment is set up with the development cluster IP address, when the installer prompts for the WebLogic listener port, enter the Managed Server ports for any node in the cluster.

Use the DNS name and the cluster port if you use the production cluster IP address.

4. After the installation, open the cmxserver.properties file for all the Managed Servers.

Installing the Hub Server on Clustered or Non-clustered Environments with Managed Servers 43

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

5. Change the following properties in the cmxserver.properties file for all the Managed Servers:

Property Description

cmx.appserver.hostname Specify machine names of the Managed Servers.

cmx.appserver.rmi.port Specify RMI port numbers.

6. Run the following command to repackage the Hub Server EAR file:

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

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

7. Open the WebLogic Server console, and manually create JMS queues. For more information about how to create JMS queues, see the Informatica MDM Multidomain Edition Configuration Guide.

Note: When you create JMS 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.

8. Open the WebLogic Server console, and manually create the connection pools and data sources for the MDM Hub Master Database and Operational Reference Stores.

9. Manually deploy the Hub Server EAR through the WebLogic Server console.

Note: Select the cluster server name to which you must deploy the application.

If you use the development cluster IP, you can access the Hub Server through the nodes in the cluster. If you use the production cluster IP, you can use the cluster names to access the Hub Server. After you start the Hub Server application, the EJB clustering distributes requests between the Managed Servers and manages failovers.


C H A P T E R 6

Hub Server Post-Installation Tasks

This chapter includes the following topics:

• Copy the Installation Log Files, 46

• Verify the Version and Build Number, 48

• Configure the Hub Server, 49

• Running the Post Install Script Manually, 50

• Manually Redeploying the Hub Server Application, 50

• Manually Configuring JMS Message Queues, 51

• Repackaging Custom JAR Files, 53

• Restart WebLogic, 54

• Configure JBoss Cache, 54

45

• Starting the Hub Console, 55

• Registering an Operational Reference Store, 56

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.

46 Chapter 6: Hub Server Post-Installation Tasks

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.

Copy the Installation Log Files 47

WebLogic Server Log FilesThe WebLogic Server log file contains information about WebLogic processes.

The following table describes the properties of the WebLogic Server log files:


File Name access.log<weblogic_server>.log<weblogic_domain>.log

Location On UNIX. <Weblogic_domain>/servers/<Weblogic_server>/logsOn Windows. <Weblogic_domain>\servers\<Weblogic_server>\logs

Usage Get information about server processes such as messages and transactions.

Contents Contains message processing status, JMS connection status, transaction details, java exceptions, and file access details.

Verify the Version and Build 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-server.ear file. The siperian-mrm-server.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.


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

Deploying the Hub Server EAR FileYou must deploy the Hub Server EAR file on the same machine on which you install the Hub Server.

The Hub Server application must be able to find the Hub Server installation from which you deploy it. Therefore, do not transfer the EAR file for deployment on another machine. For example, if you install the Hub Server on a test machine and then deploy the EAR file on the production machine, the application on production machine cannot find the installation for configuration information such as logging.

Configuring the Logging SettingsYou can configure the Hub Server for logging. Specify the configuration settings for logging in the log4j.xml file.

1. Open log4j.xml in the following directory:

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

2. Set the value for the following category names:

• com.siperian

• com.delos

• com.informatica

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

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

4. Save and close the log4j.xml file.

Setting the Configuration PropertiesYou can configure the Hub Server properties in the cmxserver.properties file.

1. Open cmxserver.properties in the following directory:

On UNIX. <infamdm_install_directory>/hub/server/resourcesOn Windows. <infamdm_install_directory>\hub\server\resources

2. Set the Hub Server properties.

The following text shows a sample configuration of the cmxserver.properties file:

cmx.home=C:\infamdm\hub\servercmx.server.masterdatabase.type=oraclecmx.appserver.type=weblogiccmx.appserver.rmi.port=7001cmx.appserver.naming.protocol=t3cmx.appserver.soap.connector.port=jnlp.initial-heap-size=128mjnlp.max-heap-size=512m

Configure the Hub Server 49

cmx.server.datalayer.cleanse.execution=SERVERcmx.server.datalayer.cleanse.working_files.location=C:\infamdm\hub\server\logscmx.server.datalayer.cleanse.working_files=LOCAL

3. Restart the Hub Server application to reload the settings in the cmxserver.properties file.

Changing the WebLogic Server SettingsIf you want to change any of the WebLogic Server settings that you specify during the installation process, change them after the installation.

1. Open build.properties in the following directory:

On UNIX. <infamdm_install_directory>/hub/server/binOn Windows. <infamdm_install_directory>\hub\server\bin

2. Change the WebLogic Server configuration settings.

3. Save and close the build.properties file.

4. Run the postInstallSetup script.

5. Restart the WebLogic Server application server.

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


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

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


On UNIX. ./postInstallSetup.sh -Dweblogic.password=<Weblogic_Password> -Ddatabase.password=<DB_Password>Note: If you include the exclamation mark (!) in your password, you must include a backslash before the exclamation mark. For example, if your password is !!cmx!!, enter the password as follows: \!\!cmx\!\!

On Windows. postInstallSetup.bat -Dweblogic.password=<Weblogic_Password> -Ddatabase.password=<DB_Password>

Manually Redeploying the Hub Server ApplicationYou can use the postInstallSetup script to deploy or redeploy the Hub Server application to WebLogic Server. However, you can also use the default application server tool to deploy the Hub Server application.

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

1. Use the WebLogic Server Administration Console to undeploy the siperian-mrm.ear file.

2. Use the WebLogic Server Administration Console to deploy the siperian-mrm.ear file.


For more information, see the WebLogic Server documentation.

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

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

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

1. Create a JMS server and module.

2. Create a connection factory for the module.

3. Add JMS message queues to the module.

4. Create a subdeployment queue.

5. Add a message queue server.

6. Add a message queue.

Step 1. Create a JMS Server and ModuleUse the Weblogic Administration Console to create a JMS message queue. Create a JMS server and a module for the message queue.

1. Start the WebLogic Console, and click Lock&Edit.

2. Navigate to Services > Messaging > JMS Servers.

3. Create a JMS Server with the name SiperianJMSServer, and click Next.

4. Select the server name in the Target list, and click Finish.

5. Navigate to Services > Messaging > JMS Modules.

6. Create a JMS Module with the name SiperianModule, and click Next.

7. Select the Target Server check box.

8. Click Next, and then click Finish.

Step 2. Configure a Connection Factory for the ModuleCreate and configure a connection factory for the module that you created.

1. Navigate to the SiperianModule that you created in “Step 1. Create a JMS Server and Module” on page 51.

2. Click New under Summary of Resources.

3. Choose Connection Factory, and click Next.

4. Specify siperian.mrm.jms.xaconnectionfactory for both the name and the JNDI name, and click Next.

Manually Configuring JMS Message Queues 51

5. Select Target Server, and click Finish.

The siperian.mrm.jms.xaconnectionfactory connection factory is created.

6. Under Configuration, go to the siperian.mrm.jms.xaconnectionfactory connection factory that you created.

7. Click Transactions.

8. Select the XA Connection Factory Enabled check box.

9. Click Save.

Step 3. Add Message Queues to the ModuleYou can add JMS message queues to the module that you created.

1. Navigate to SiperianModule, and click New under Summary of Resources.

2. Choose Queue, and click Next.

3. Specify siperian.sif.jms.queue for both the name and the JNDI name, and click Next.

4. Choose the JMS Server that you created in “Step 1. Create a JMS Server and Module” on page 51, and click Finish.


Step 4. Create a Subdeployment QueueAfter you add JMS message queues to the module that you created, create a subdeployment queue.

1. Under Summary of Resources, go to SiperianModule, and click New.

2. Choose Queue, and click Next.

3. Click the Create a new Subdeployment button.

4. Verify that the Subdeployment Name is siperian.sif.jms.queue, and click OK.

5. Specify siperian.sif.jms.queue for both the name and the JNDI name, and click Next.

6. Choose the JMS Server that you created, and click Finish.


Step 5. Add a Message Queue ServerYou must add a message queue server to the MDM Hub implementation before you add a message queue.

1. Start the Hub Console.

2. Click Message Queues under the Configuration workbench.

3. Click Write Lock > Acquire Lock.

4. Right-click on the middle pane of the Message Queues tool, and then click Add Message Queue Server.

The Add Message Queue Server dialog box appears.

5. Enter values for the following fields:

Connection Factory Name

Name of the connection factory. Specify siperian.mrm.jms.xaconnectionfactory.


Display Name

Name of the message queue server that must appear in the Hub Console. Specify Siperian.Mrm.Jms.Xaconnectionfactory.

6. Click OK.

The message queue server is added.

Step 6. Add a Message 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.

5. Enter values for the following fields:

Queue Name

Name of the message queue. Specify siperian.sif.jms.queue.

Display Name

Name of the message queue that must appear in the Hub Console. Specify Siperian.Sif.Jms.Queue.

6. Click OK.

The message queue is added to the message queue server.

7. In the right pane, select the Use with message triggers option.

8. Click Test.

The result of the message queue test appears.

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

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

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:

Repackaging Custom JAR Files 53

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

Restart WebLogicThe installation process enables the AnonymousAdminLookupEnabled method of the WebLogic Server. The AnonymousAdminLookupEnabled method must be enabled for the registration of the Operational Reference Store. If you do not restart WebLogic Server after you install the Hub Server, the Operational Reference Store fails.

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

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

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

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

Change the following properties in the jbossCacheConfig.xml file:

lockAcquisitionTimeout

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

sync replTimeout

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

stateRetrieval timeout

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

clustering

Set up the clustering property for a clustered environment.

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

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


jgroupsConfig

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

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

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

eviction

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

Change the eviction time as shown in the following sample:

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

Starting the Hub ConsoleStart the Hub Console to access the MDM Hub. Use an HTTP connection to start the Hub Console.

Ensure that you have a user name and password set up before you start the Hub Console.

1. Open a browser window and enter the following URL: http://<MDM Hub host>:<port>/cmx/

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

The Hub Console launch window appears.

2. Click Launch.

Java Web Start loads.

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

The MDM Hub Login dialog box appears.

3. Enter a user name and password.

4. Click OK.

The MDM Hub prompts you to select the target database. The target database is the MDM Hub Master Database.

5. Click Connect.

The Hub Console appears.

Starting the Hub Console 55

Registering an Operational Reference StoreAfter you create an Operational Reference Store, you must register it. You can register an Operational Reference Store through the Hub Console.

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


The Change database dialog box appears.

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

3. Start the Databases tool under the Configuration workbench.


5. Click the Register database button.

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

6. Select the Oracle, and click Next.

7. Configure connection properties for the database.

a. Select an Oracle connection method, and click Next.

The following table describes the Oracle connection methods that you can select:

Connection Method Description

Service Connect to Oracle by using the service name.

SID Connect to Oracle by using the Oracle System ID.

For more information about SERVICE and SID names, see the Oracle documentation.


b. Specify the connection properties for the connection type that you select, and click Next.

The following table lists and describes the connection properties:


Database 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 hostname

IP address or name of the server that hosts the Oracle database.

SID Oracle System Identifier that refers to the instance of the Oracle database running on the server. The SID field appears if you selected the SID connection type.

Service Name of the Oracle SERVICE used to connect to the Oracle database. The Service field appears if the you selected the Service connection type.



Port The TCP port of the Oracle listener running on the Oracle database server. The default is 1521.

Oracle TNS Name

Name by which the database is known on your network as defined in the TNSNAMES.ORA file of the application server.For example: mydatabase.mycompany.com.You set the Oracle TNS name when you install the Oracle database. For more information about the Oracle TNS name, see the Oracle documentation.

Schema Name

Name of the Operational Reference Store.

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 of the Operational Reference Store database objects in the Hub Store.

Password Password associated with the user name for the Operational Reference Store.For Oracle, the password is not case sensitive.By default, this is the password that you specify when you create the Operational Reference Store.

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

The Summary page appears.

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

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


Connection URL Connect URL. The Connection Wizard generates the connect URL by default. The following list shows the format of the connect URL for the Oracle connection types:Service connection type

jdbc:oracle:thin:@//database_host:port/service_name

SID connection type

jdbc:oracle:thin:@//database_host:port:sidFor a service connection type only, you have the option to customize and later test a different connection URL.

Create datasource after registration

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

d. For a service connection type, if you want to change the default URL, click the Edit button, specify the URL, and then click OK.

Registering an Operational Reference Store 57

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.


C H A P T E R 7

Process Server InstallationThis chapter includes the following topics:

• Installing the Process Server in Graphical Mode, 59

• Installing the Process Server in Console Mode, 61

• Installing the Process Server in Silent Mode, 63

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

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

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

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


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

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


On UNIX. hub_cleanse_install.binOn Windows. hub_cleanse_install.exe

4. Select the language for the installation, and then click OK.

The Introduction window appears.

5. Click Next.

The License Agreement window appears.

6. Select the I accept the terms of the License Agreement option, and then click Next.

The Choose Install Folder window appears.

7. Select the location of the Process Server installation.

59

• To choose the default location, click Next.

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

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

On UNIX, the Choose Link Folder window appears.

On Windows, the Choose Shortcut Folder window appears.

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

The Enter Location of License File window appears.

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

The Application Server window appears.

10. Select WebLogic, and then click Next.

The WebLogic Application Server Home window appears.

11. Configure the following WebLogic Server settings:

a. Choose a path to the WebLogic domain installation directory for the domain you want to use for the MDM Hub. Click Next.

The WebLogic Application Server Login window appears.

b. Enter values for the login parameters.

The following table describes the login parameters:

Parameter Description

Host Name of the host computer on which WebLogic is installed.

Server Name of the WebLogic Server instance in the domain on which WebLogic is deployed. For example, AdminServer.

User Name Name of the user for the WebLogic installation.

Password Password that corresponds to the WebLogic user.

Port Number Port number on which the WebLogic Server is listening.

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

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

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

13. Click Next.


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

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




60 Chapter 7: Process Server Installation




16. Click Next.

The Deploy page appears.

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

18. Click Next.

The Pre-Installation Summary window appears.

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

When the installation completes, the Install Complete window appears.

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

21. Click Done to exit the Process Server installer.

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

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

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


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

On Solaris. <distribution directory>/solaris/mrmcleanseOn HP-UX. <distribution directory>/hpux/mrmcleanseOn Linux. <distribution directory>/linux/mrmcleanseOn AIX. <distribution directory>/aix/mrmcleanse

3. Run the following command from the command prompt: ./hub_cleanse_install.bin -i console

4. Enter the number of the locale you want to choose for the installation, and then press Enter.

The introduction information about the installation appears.

5. Press Enter.

The license agreement appears.

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

7. Press Enter.

If you entered Y in the preceding step, information about the installation folder appears.

Installing the Process Server in Console Mode 61

8. Choose the folder for the Process Server installation.

• To choose the default location, press Enter.

• To change the path, type the absolute path of the installation folder, and press Enter.

9. Confirm the location of the installation folder. Type Y to confirm the installation folder, or type N to change the installation folder.

10. Press Enter.

The prompt for the license file location appears.

11. Enter the absolute path of the license file, and press Enter.

A list of application server options appears.

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

The application server information appears.

13. Configure the WebLogic settings.

a. Specify the path to the WebLogic domain in which you want to install the Hub Server, and press Enter.

The prompts for the WebLogic application server login information appears.

b. Enter the host name, server name, user name, password, and listener port for the WebLogic Server, or accept the default values, and press Enter.

14. Press Enter.

15. Configure the cleanse engine settings.

• If you use Address Doctor, configure the following parameters:

- Specify the configuration file location, and press Enter.

- Specify the parameters file location, and press Enter.

- Specify the default correction type, and press Enter.

• If you use Business Objects DQ XI, configure the following parameters:

- Specify the host name, and press Enter.

- Specify the port, and press Enter.

- Specify the sub file, and press Enter.

The deployment information appears.

16. Click Next.

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

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









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

20. Press Enter.


21. Verify the information in the pre-installation summary. If the information is correct, press Enter to start the installation. If you need to make changes, type BACK to the specific information and make changes.

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

22. Press Enter.

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

23. Press Enter to exit the installer.

Installing the Process Server in Silent ModeYou can install the Process Server without user interaction in silent mode. You might want to perform a silent installation if you need multiple installations, or if you need to install on a machine cluster. A silent installation does not show any progress or failure messages.

Before you run the silent installation for the Process Server, you must configure the properties file for the silent installation. The installer reads the file to determine the installation options. The silent installation process might complete successfully even if you provide incorrect settings, such as an incorrect application server path or port setting. You must ensure that you provide correct settings in the properties file.

Copy the Process Server installation files to the hard disk on the machine where you plan to install the Process Server. To install in silent mode, complete the following tasks:

1. Configure the installation properties file and specify the installation options in the properties file.

2. Run the installer with the installation properties file.

Configuring the Properties FileInformatica provides a sample properties file that includes the parameters that the installer requires. You can customize the sample properties file to specify the options for the installation. Then run the silent installation.

The silent installer does not validate the settings in the properties files. You must ensure that you specify correct settings and verify them before you run the silent installer.

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

The file is in the distribution directory in the following directory:

On UNIX. /silent_install/mrmcleanseOn Windows. \silent_install\mrmcleanseNote: In the silent properties file, slash and backslash are special characters. You must enter two of each when you enter information in the file, such as when you enter an installation path. For example, to enter the path to the Process Server directory, you must enter \\u1\\infamdm\\hub\\cleanse.

2. Create a backup copy of silentInstallCleanse_sample.properties.

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

Installing the Process Server in Silent Mode 63

4. Save the properties file with a name such as silentInstallCleanse.properties.

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


INSTALLER_UI Specifies the type of installation. Set to silent.

USER_INSTALL_DIR Directory to install Process Server.For example, C\:\\<infamdm_install_directory>\\hub\\cleanse.

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

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

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

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

SIP.APPSERVER.HOST Host name such as localhost.

SIP.APPSERVER.SERVER Admin Server name such as AdminServer.

SIP.APPSERVER.USERNAME User name to access WebLogic.

SIP.APPSERVER.PASSWORD Password to access WebLogic.

WEBLOGIC.AS.PORT Application server port number.

SIP.OS.CHOICE=Red Hat Linux Remove the comment on the property if the operating system for the installation is Red Hat Linux.To remove the comment, remove the pound sign (#) in front of the property.

SIP.OS.CHOICE=Suse Linux Remove the comment on the property if the operating system for the installation is Suse Linux.To remove the comment, remove the pound sign (#) in front of the property.

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

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

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

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

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



SIP.FLDIRECT.HOST Host name of FirstLogic.

SIP.FLDIRECT.PORT FirstLogic direct port.

SIP.FLDIRECT.SUBFILE FirstLogic Direct subfile

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

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

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

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

CSM_PROXY_USER_NAME Proxy server user name. Leave blank if the 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 WebLogic application serverSIP.AS.CHOICE="WebLogic"SIP.AS.HOME=C\:\\bea\\user_projects\\domains\\base_domainSIP.APPSERVER.HOST=localhostSIP.APPSERVER.SERVER=AdminServerSIP.APPSERVER.USERNAME=weblogicSIP.APPSERVER.PASSWORD=weblogicWEBLOGIC.AS.PORT=7001## 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\

Installing the Process Server in Silent Mode 65

\5\\Parameters.xmlSIP.ADDRESSDOCTOR.DEFAULTCORRECTIONTYPE=PARAMETERS_DEFAULT

## Following FirstLogicDirect properties should be set if you have license for FirstLogicDirect.SIP.FLDIRECT.HOST=localhostSIP.FLDIRECT.PORT=20004SIP.FLDIRECT.SUBFILE=dqxiserver1_substitutions.xml

## If you want to run postInstallSetup as a part of silent install, then set following property.## set RUN_DEPLOYMENT_FLAG to 1 if you want to run postInstallSetup## or set RUN_DEPLOYMENT_FLAG to 0 if you do not want to run postInstallSetupRUN_DEPLOYMENT_FLAG=1

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

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

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

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

1. Ensure that the application server is running.

2. Open a command window.


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

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


Installing and Deploying the Process Server on Nodes in the Cluster

If you have a clustered environment, install the Process Server on the Admin Server and on all nodes of the cluster to which you must deploy the Process Server application. You must ensure that the path for the Process Server installation is the same on all the cluster nodes.

1. Start the Process Server installer on all nodes of the cluster.

Run the following command to start the Process Server installer:On UNIX. ./hub_cleanse_install.bin -DSIPERIAN_INSTALL_PREREQ_VALIDATION=falseOn Windows. hub_cleanse_install.exe -DSIPERIAN_INSTALL_PREREQ_VALIDATION=false

2. Click No when the installer prompts you to run the postInstallSetup script to deploy the application.

3. When the installer prompts for the WebLogic listener port, enter the managed server ports for any node in the cluster if the cluster is set up with the development cluster IP address.

Use the DNS name and the cluster port if you use the production cluster IP address.

4. Run the following command to repackage the Process Server EAR file:

On UNIX.cd <infamdm_install_directory>/hub/cleanse/bin./sip_ant.sh repackage

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

5. Manually deploy the Process Server EAR through the WebLogic Server console.

Note: Select the cluster server name to which you must deploy the application.

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

C H A P T E R 8

Process Server Post-Installation Tasks

This chapter includes the following topics:

• Copy the Installation Log Files, 68

• Verify the Version and Build Number, 70

• Configure the Process Server, 71

• Configure Process Server for Multithreading, 73

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

• Configuring Multiple Process Servers for Batch Processes, 75

• Configure Match Population, 76

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.

68

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 69

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.

WebLogic Server Log FilesThe WebLogic Server log file contains information about WebLogic processes.

The following table describes the properties of the WebLogic Server log files:


File Name access.log<weblogic_server>.log<weblogic_domain>.log

Location On UNIX. <Weblogic_domain>/servers/<Weblogic_server>/logsOn Windows. <Weblogic_domain>\servers\<Weblogic_server>\logs

Usage Get information about server processes such as messages and transactions.

Contents Contains message processing status, JMS connection status, transaction details, java exceptions, and file access details.

Verify the Version and Build 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

70 Chapter 8: Process Server Post-Installation Tasks

On Windows. <infamdm_install_directory>\hub\cleanse\conf• On UNIX. Run versionInfo.sh that is in the following directory:

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

<infamdm_install_directory>\hub\cleanse\bin

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

Configure the Process ServerAfter you install the Process Server, you need to configure it. You can configure logging settings, and change application server, and Process Server settings.

Deploying the Process Server EAR FileDeploy the Process Server EAR file on the same machine where you install the Process Server.

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

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.

Configure the Process Server 71

Configuring the Logging SettingsYou can configure the Process Server for logging. Specify the configuration settings for logging in the log4j.xml file.

1. Open log4j.xml in the following directory:

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

2. Set the value for the following category names:

• com.siperian

• com.delos

• com.informatica

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

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

4. Save and close the file.

Setting the Configuration PropertiesYou can configure the Process Server properties in the cmxcleanse.properties file.

1. Open cmxcleanse.properties in the following directory:

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

2. Configure the Process Server properties.

A sample configuration of the cmxcleanse.properties is as follows:

cmx.server.datalayer.cleanse.working_files.location=C:\infamdm\hub\cleanse\tmpcmx.server.datalayer.cleanse.working_files=KEEPcmx.server.datalayer.cleanse.execution=LOCALcmx.home=C:\infamdm\hub\cleansecmx.appserver.type=weblogic

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 must run the post install script manually.


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

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



On UNIX. ./postInstallSetup.sh -Dweblogic.password=<weblogic Password> -Ddatabase.password=<Database Password>On Windows. postInstallSetup.bat -Dweblogic.password=<weblogic Password> -Ddatabase.password=<Database Password>

Manually Redeploying the Process Server EAR FileYou can manually redeploy the Process Server on the WebLogic application server.

1. Use the WebLogic Server Administration Console to undeploy the siperian-mrm-cleanse.ear file.

2. Use the WebLogic Server Administration Console to deploy the siperian-mrm-cleanse.ear file.

Ensure that you deploy the Process Server EAR file from the Process Server installation directory.

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

Configure Process Server for Multithreading 73

Configuring the Process Server for MultithreadingUse the Hub Console to configure the Process Server for multithreading.

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

The Process Server tool displays the configured Process Servers.


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

4. Click Edit Process Server.

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

5. Set the Threads for Cleanse Operations property.

The default value is 1. You can change the threads for cleanse operations without restarting the Process Server.

6. Set the Threads for Batch Processing.

The default value is 20.

7. Click OK and then click Save.

Configuring Multiple Process Servers for Cleanse and Match Operations

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

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

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

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 75

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. If the C_REPOS_SSA_POPULATION table does not contain the population, add it to the table and enable it.

The population name is the same as the ysp file name. For example, if the ysp file name is US.ysp, the population name is US.



To add the population to an Operational Reference Store, use the following steps:

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

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

On UNIX. <infamdm_install_directory>/server/resources/database/custom_scripts/oracleOn Windows. <infamdm_install_directory>\server\resources\database\custom_scripts\oracle

c. Answer the prompts described in the following table:

Prompt Description

Enter the population to add Name of the population.

Enter a value for ROWID_SSA_POP (example: INFA.0001) DEFAULT [INFA.0001]

Unique value for the ROWID_SSA_POP column of the C_REPOS_SSA_POPULATION metadata table. Default is INFA.0001

The population is registered in the C_REPOS_SSA_POPULATION table.

d. Run the following command to enable the population: UPDATE c_repos_ssa_population SET enabled_ind = 1 WHERE population_name = '<Your Population> ';COMMIT;

4. Restart the Process Server.

5. Log in to the Hub Console to verify that the population is enabled.

The population appears in the Match/Merge Setup user interface for base objects.

Configure Match Population 77

C H A P T E R 9

Troubleshooting the MDM HubThis chapter includes the following topic:

• Troubleshooting the Installation Process, 78

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

Inaccurate start or stop timestamp for Operational Reference StoreWhen you export an Operational Reference Store that you create, the MDM Hub creates a .dmp file. You can reuse the .dmp file of the Operational Reference Store to create a second Operational Reference Store. The start date and end date columns in the C_REPOS_DB_VERSION table of the Operational Reference Store will contain incorrect start date and end date. You can ignore this error as it does not affect any functionality.

The Hub Server cannot connect to the cmx_system schemaTo verify that the Hub Server cannot connect to the cmx_system schema, review the application server log. For example, the following error might appear in Websphere log SystemOut.log:

Caused by: java.sql.SQLException: ORA-28000: the account is locked DSRA0010E: SQL State = 99999, Error Code = 28,000

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

78

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

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 WebLogic home directory.

2. Open the following file in a text editor.On UNIX. setDomainEnv.shOn Windows. startWeblogic.cmd

3. Use the following command to set the MEM_ARGS variable:On UNIX.

set MEM_ARGS=${MEM_ARGS} -Xss2000kOn Windows.

set MEM_ARGS=%MEM_ARGS% -Xss2000k4. Save and close the file.

Troubleshooting the Installation Process 79

C H A P T E R 1 0

UninstallationThis chapter includes the following topics:

• Uninstallation Overview, 80

• Uninstalling the Hub Store, 80

• Uninstalling the Process Server in Graphical Mode, 81

• Uninstalling the Hub Server in Graphical Mode, 82

• Uninstalling the Process Server in Console Mode, 82

• Uninstalling the Hub Server in Console Mode, 83

• Manually Undeploying the Process Server, 83

• Manually Undeploying the Hub Server, 83

Uninstallation OverviewTo uninstall the MDM Hub, you need to remove the Process Server, the Hub Server, and the Hub Store from the MDM Hub implementation.

Use the following steps to uninstall the MDM Hub:

1. Uninstall the Hub Store.

2. Uninstall the Process Server.

3. Uninstall the Hub Server.

Uninstalling the Hub StoreYou can uninstall the Hub Store by dropping the Hub Store schemas and removing the user logins for the Hub Store schemas. Before you drop the Hub Store schemas, use the Hub Console to unregister the Hub Store schemas.

You must have administrator privileges to drop the Hub Store schemas.


2. Click the Databases tool under the Configuration workbench.

The Database Information page appears.

80


4. From the list of databases, select the Operational Reference Store to unregister.

5. Click the Unregister database button.

The Databases tool prompts you to confirm unregistering the Operational Reference Store.

6. Click Yes.

7. Use SQL*Plus to connect to the Oracle instance.

8. Use the following command for each Hub Store schema to drop the schema: drop user <user name> cascade;

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

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

Uninstalling the Process Server in Graphical Mode On UNIXTo uninstall the MDM Hub, you must remove the Process Server. You must perform the steps to uninstall the Process Server for each Process Server in the MDM Hub implementation.

1. Stop the application server.

2. Navigate to the following directory: <infamdm_install_directory>/hub/cleanse/UninstallerData

3. Run the uninstaller. ./"Uninstall Informatica MDM Hub Cleanse Match Server"

4. Click Uninstall.

When the uninstallation process is complete, the Uninstall Complete window appears.

5. Click Done.

Uninstalling the Process Server in Graphical Mode On WindowsTo uninstall the MDM Hub, you must remove the Process Server. You must perform the steps to uninstall the Process Server for each Process Server in the MDM Hub implementation.

1. Stop the application server.

2. Click Start and then click Programs > Infamdm > Hub > Cleanse > Uninstaller Data > Uninstall Informatica MDM Hub Cleanse Match Server.

The Uninstall introduction window appears.

3. Click Uninstall.


4. Click Done.

Uninstalling the Process Server in Graphical Mode 81

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

Uninstalling the Hub Server in Graphical Mode on UNIXTo uninstall the MDM Hub, you must remove the Hub Server from the MDM Hub implementation.

1. Ensure that you stop the application server.

2. Navigate to the following directory: <infamdm_install_directory>/hub/server/UninstallerData

3. Run the uninstaller.

./"Uninstall Informatica MDM Hub Server"The Uninstall introduction window appears.

4. Click Uninstall.


5. Click Done.

Uninstalling the Hub Server in Graphical Mode on WindowsTo uninstall the MDM Hub, you must remove the Hub Server from the MDM Hub implementation.

1. Ensure that you stop the application server.

2. Click Start and then click Programs > Infamdm > Hub > Server > UninstallerData > Uninstall Informatica MDM Hub Server.

The Uninstall introduction window appears.

3. Click Uninstall.


4. Click Done.

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

1. Go to the following directory:

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

./"Uninstall Informatica MDM Hub Cleanse Match Server"

82 Chapter 10: Uninstallation

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.

1. Go to the following directory:

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

./"Uninstall Informatica MDM Hub Server"

Manually Undeploying the Process ServerYou might need to manually undeploy the Process Server from the WebLogic Server environment.

u Use the WebLogic Server Administration Console to manually undeploy the siperian-mrmcleanse.ear file.

For more information, see the WebLogic documentation.

Manually Undeploying the Hub ServerYou might need to manually undeploy the Hub Server from the WebLogic Server environment.

u Use the WebLogic Server Administration Console to manually undeploy the siperian-mrm.ear file.

For more information, see the WebLogic documentation.

Uninstalling the Hub Server in Console Mode 83

Index

Cclustering

on WebLogic 23configuring Oracle

configure the init.ora parameters 16disable the Oracle Recycle Bin 16Oracle RAC 18

custom jar files repackaging 53

Ddatabases

connection testing 18target database 55

Eenvironment variables

DISPLAY 14

Ggraphical mode

installation requirements 14

HHub Console

starting 55Hub Server

configuration properties 49deploying on WebLogic cluster 43installation log files 46installing 35, 37logging settings 49postinstallsetup script 50silent installation 39, 43silent properties file 40uninstalling 83version and build number 48

Hub Store tablespaces, creating 16uninstalling 80

Iinstallation requirements

X Window Server 14

installing Hub Server 35, 37Process Server 59, 61

JJBoss

port conflicts 49JBoss cache

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

JMS message queues configuring 51

Llog file

debug log file 47, 69Hub Server log file 47installation log file 46, 68installation prerequisites log file 46, 70post install setup log file 47, 69Process Server log file 69WebLogic Server log files 48, 70

MMaster Database

creating 25importing metadata 28

match population enabling 76

MDM Hub components 10designing the installation 11installation tasks 11introduction 10setting environment variables 14system requirements 13

message queues adding to the module 52

OOperational Reference Store

creating 27

84

Operational Reference Store (continued)importing metadata 30registering 56

Ppostinstallsetup script

for Hub Server 50for Process Server 72running 50, 72

Process Server configuration properties 72configuring 71deploying on WebLogic cluster 67installation log files 68installing 59, 61logging settings 72multithreading, configuring 74postinstallsetup script 72redeploying 73silent installation 63silent properties file 63threads for batch processing 73threads for cleanse operations 73uninstalling 82version and build number 70

Ssilent installation

of Hub Server 43silent installer

running 66

Ttablespaces

creating 16target database

selecting 55tns name

adding 17troubleshooting

post-installation process 78

Uuninstalling

Hub Server 83Hub Store 80Process Server 82

WWebLogic

clustering 23configuring 19

WebLogic cluster deploying Hub Server 43deploying Process Server 67

WebLogic Server settings 50

XX Window Server

installation requirements 14

Index 85

Documents

WebLogic Installation Guide for - Informatica · Informatica MDM Multidomain Edition for Oracle (Version 9.7.1 HotFix 5) Installation Guide for WebLogic