mdm 901 install guide

MDM Multidomain Edition (Version 9.0.1)

Installation Guide

Informatica MDM Multidomain Hub - Version 9.0.1 - September 2010, revised October 2010Copyright (c) 2010 Informatica. 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 is 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 and Siperian 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.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and other software which is licensed under the Apache License, Version 2.0 (the “License”). You may obtain a copy of the License at http://www.apache.org/licenses/

LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

This product includes software which is licensed under 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.

This product includes software which is licensed under the CDDL (the “License”). You may obtain a copy of the License at http://www.sun.com/cddl/cddl.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. See the License for the specific language governing permissions and limitations under the License.

This product includes software which is licensed under the BSD License (the “License”). You may obtain a copy of the License at http://www.opensource.org/licenses/bsd-license.php. 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. See the License for the specific language governing permissions and limitations under the License.

This product includes software Copyright (c) 2003-2008, Terence Parr, all rights reserved which is licensed under the BSD License (the “License”). You may obtain a copy of the License at http://www.antlr.org/license.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. See the License for the specific language governing permissions and limitations under the License.

This product includes software Copyright (c) 2000 - 2009 The Legion Of The Bouncy Castle (http://www.bouncycastle.org) which is licensed under a form of the MIT License (the “License”). You may obtain a copy of the License at http://www.bouncycastle.org/licence.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. See the License for the specific language governing permissions and limitations under the License.

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 non-infringement, 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”) may include 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 NOTLIMITED 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.

Contents

Preface

Intended Audience .........................................................................................................................................xiiiContents ...........................................................................................................................................................xivLearning About Informatica MDM Hub.....................................................................................................xvInformatica Global Customer Support ......................................................................................................xviiInformatica Resources .................................................................................................................................xviii

Informatica Customer Portal ............................................................................................................xviiiInformatica Documentation .............................................................................................................xviiiInformatica Web Site ...........................................................................................................................xixInformatica How-To Library..............................................................................................................xixInformatica Knowledge Base..............................................................................................................xixInformatica Multimedia Knowledge Base ........................................................................................xix

Chapter 1: Introduction

Before You Begin ..............................................................................................................................................2Installation Overview........................................................................................................................................3Designing Your Informatica MDM Hub Installation..................................................................................4

Implementation Components................................................................................................................4Installation Environments......................................................................................................................5Example Installations..............................................................................................................................5

Documenting Your Installation ......................................................................................................................8Installation and Post-Installation Documentation .............................................................................8Create an Installation Documentation Directory ...............................................................................9

Chapter 2: Installing the Hub Store

About the Hub Store ......................................................................................................................................12Master Database and Operational Reference Store (ORS) .............................................................12

iii

Relationships Among Databases in the Hub Store ......................................................................... 12Single Informatica MDM Hub Version Requirement..................................................................... 13Oracle RAC Considerations ................................................................................................................ 14

Overview of Steps to Install the Hub Store................................................................................................ 17Prepare Your Oracle Deployment for Informatica MDM Hub.............................................................. 18

Install and Configure Oracle ............................................................................................................... 18Turning Off the Oracle Recycle Bin .................................................................................................. 19Setting Oracle PLSQL Compiler Flags (Oracle 10gR2 Only)........................................................ 19

Create an Oracle Database for the Hub Store............................................................................................ 20Create Tablespaces Used by the Hub Store................................................................................................ 21

Tablespaces to Create ........................................................................................................................... 21Creating CMX_DATA ......................................................................................................................... 22Creating CMX_INDX ......................................................................................................................... 22Creating CMX_TEMP ......................................................................................................................... 22

Create the Hub Store...................................................................................................................................... 23About the setup.sql Script.................................................................................................................... 23Create the Hub Store (Unix) ............................................................................................................... 24Create the Hub Store (Windows) ....................................................................................................... 28

Test the Database Connection...................................................................................................................... 32Create a Proxy User ........................................................................................................................................ 33

Proxy Users in Informatica MDM Hub Implementations ............................................................. 33Creating a Proxy User........................................................................................................................... 33

Create an Additional ORS Database............................................................................................................ 36About the setup_ors.sql Script............................................................................................................ 36Adding an ORS (Unix) ......................................................................................................................... 37Adding an ORS (Windows)................................................................................................................. 39

Chapter 3: Installing the Hub Server

About the Hub Server .................................................................................................................................... 44Application Server and Connection Pooling .................................................................................... 44Manually Configuring Message Queues for Asynchronous SIF Requests................................... 44PostInstallSetup..................................................................................................................................... 45Single Informatica MDM Hub Version Requirement..................................................................... 45

iv Informatica MDM Hub 9.0.1 Installation Guide

Installing the Hub Server (JBoss/Unix).......................................................................................................46Installation Overview............................................................................................................................46Preparing for Installation......................................................................................................................46Running the Hub Server Installer .......................................................................................................49Configuring the Hub Server.................................................................................................................54Performing Post-Installation Tasks ....................................................................................................56

Installing the Hub Server (WebLogic/Unix)...............................................................................................57Installation Overview............................................................................................................................57Preparing for Installation......................................................................................................................57Running the Hub Server Installer .......................................................................................................59Configuring the Hub Server.................................................................................................................64Performing Post-Installation Tasks ....................................................................................................66

Installing the Hub Server (WebSphere/Unix) ............................................................................................67Installation Overview............................................................................................................................67Preparing for Installation......................................................................................................................67Running the Hub Server Installer .......................................................................................................69Configuring the Hub Server.................................................................................................................73Performing Post-Installation Tasks ....................................................................................................75

Installing the Hub Server (JBoss/Windows)...............................................................................................77Installation Overview............................................................................................................................77Preparing for Installation......................................................................................................................78Running the Hub Server Installer .......................................................................................................81Configuring the Hub Server.................................................................................................................85Performing Post-Installation Tasks ....................................................................................................87

Installing the Hub Server (WebLogic/Windows).......................................................................................88Installation Overview............................................................................................................................88Preparing for Installation......................................................................................................................88Running the Hub Server Installer .......................................................................................................90Configuring the Hub Server.................................................................................................................95Performing Post-Installation Tasks ....................................................................................................97

Installing the Hub Server (WebSphere/Windows) ....................................................................................98Installation Overview............................................................................................................................98Preparing for Installation......................................................................................................................98

Contents v

Running the Hub Server Installer..................................................................................................... 100Configuring the Hub Server .............................................................................................................. 104Performing Post-Installation Tasks.................................................................................................. 106

Changing Passwords After Installation...................................................................................................... 107Changing the Password for the CMX_SYSTEM User ................................................................. 107Changing the Password for the CMX_ORS User ......................................................................... 107

Chapter 4: Installing the Cleanse Match Server

About the Cleanse Match Server ................................................................................................................ 110Supported Cleanse Match Engines................................................................................................... 110PostInstallSetup................................................................................................................................... 110Single Informatica MDM Hub Version Requirement................................................................... 111

Installing the Cleanse Match Server (JBoss/Unix) .................................................................................. 112Installation Overview ......................................................................................................................... 112Preparing for Installation ................................................................................................................... 112Running the Cleanse Match Server Installer................................................................................... 117Configuring the Cleanse Match Server ............................................................................................ 121Performing Post-installation Tasks .................................................................................................. 127

Installing the Cleanse Match Server (WebLogic/Unix) .......................................................................... 129Installation Overview ......................................................................................................................... 129Preparing for Installation ................................................................................................................... 129Running the Cleanse Match Server Installer................................................................................... 134Configuring the Cleanse Match Server ............................................................................................ 138Performing Post-installation Tasks .................................................................................................. 146

Installing the Cleanse Match Server (WebSphere/Unix)........................................................................ 148Installation Overview ......................................................................................................................... 148Preparing for Installation ................................................................................................................... 148Running the Cleanse Match Server Installer................................................................................... 155Configuring the Cleanse Match Server ............................................................................................ 159Performing Post-installation Tasks .................................................................................................. 166

Installing the Cleanse Match Server (JBoss/Windows) .......................................................................... 168Installation Overview ......................................................................................................................... 168Preparing for Installation ................................................................................................................... 168

vi Informatica MDM Hub 9.0.1 Installation Guide

Running the Cleanse Match Server Installer ...................................................................................172Configuring the Cleanse Match Server.............................................................................................176Performing Post-installation Tasks...................................................................................................179

Installing the Cleanse Match Server (WebLogic/Windows)...................................................................184Installation Overview..........................................................................................................................184Preparing for Installation....................................................................................................................184Running the Cleanse Match Server Installer ...................................................................................192Configuring the Cleanse Match Server.............................................................................................196Performing Post-installation Tasks...................................................................................................199

Installing the Cleanse Match Server (WebSphere/Windows) ................................................................204Installation Overview..........................................................................................................................204Preparing for Installation....................................................................................................................204Running the Cleanse Match Server Installer ...................................................................................211Configuring the Cleanse Match Server.............................................................................................215Performing Post-installation Tasks...................................................................................................218

Chapter 5: Launching the Hub Console

About the Hub Console ...............................................................................................................................224Starting the Hub Console .............................................................................................................................225Post-setup Tasks ............................................................................................................................................229

Chapter 6: Clustering

Installing the Hub Server into a WebLogic Server Cluster (Unix) ........................................................232Installation Overview..........................................................................................................................232Creating a WebLogic Cluster .............................................................................................................232Installing the Hub Server on Nodes in the Cluster ........................................................................233Configuring Services and Deploying the Hub Server ....................................................................234Deploying the Cleanse Match Server................................................................................................235

Installing the Hub Server into a WebSphere Server Cluster (Unix) ......................................................236Installation Overview..........................................................................................................................236Before You Install ...............................................................................................................................236Installing the Hub Server and Cleanse Match Server Software....................................................236

Contents vii

Creating a WebSphere Cluster .......................................................................................................... 237Configuring Services and Deploying the Hub Server ................................................................... 238Deploying the Cleanse Match Server ............................................................................................... 240

Installing the Hub Server into a WebLogic Server Cluster (Windows) ................................................ 241Installation Overview ......................................................................................................................... 241Creating a WebLogic Cluster............................................................................................................. 241Installing the Hub Server on Nodes in the Cluster ....................................................................... 242Configuring Services and Deploying the Hub Server ................................................................... 242Deploying the Cleanse Match Server ............................................................................................... 244

Installing the Hub Server into a WebSphere Server Cluster (Windows).............................................. 245Installation Overview ......................................................................................................................... 245Before You Install ............................................................................................................................... 245Installing the Hub Server and Cleanse Match Server Software ................................................... 245Creating a WebSphere Cluster .......................................................................................................... 246Configuring Services and Deploying the Hub Server ................................................................... 247Deploying the Cleanse Match Server ............................................................................................... 249

Chapter 7: Uninstalling Informatica MDM Hub

Uninstalling Informatica MDM Hub (JBoss / Unix).............................................................................. 252Uninstalling the Cleanse Match Server ............................................................................................ 252Uninstalling the Hub Server .............................................................................................................. 253

Uninstalling Informatica MDM Hub (WebLogic / Unix)...................................................................... 254Uninstalling the Cleanse Match Server ............................................................................................ 254Uninstalling the Hub Server .............................................................................................................. 256

Uninstalling Informatica MDM Hub (WebSphere / Unix) ................................................................... 256Uninstalling the Cleanse Match Server ............................................................................................ 257Uninstalling the Hub Server .............................................................................................................. 258

Uninstalling Informatica MDM Hub (JBoss / Windows)...................................................................... 258Uninstalling the Cleanse Match Server ............................................................................................ 259Uninstalling the Hub Server .............................................................................................................. 260

Uninstalling Informatica MDM Hub (WebLogic / Windows).............................................................. 261Uninstalling the Cleanse Match Server ............................................................................................ 261Uninstalling the Hub Server .............................................................................................................. 262

viii Informatica MDM Hub 9.0.1 Installation Guide

Uninstalling Informatica MDM Hub (WebSphere / Windows)............................................................263Uninstalling the Cleanse Match Server.............................................................................................263

Uninstalling the Hub Store from Oracle....................................................................................................264Database Objects to Drop .................................................................................................................264Dropping Hub Store Databases ........................................................................................................265Uninstalling the Hub Server...............................................................................................................266

..........................................................................................................................................................................266

Chapter 8: Troubleshooting

Informatica MDM Hub Log Files ..............................................................................................................268Informatica MDM Hub Log Files (Unix)........................................................................................268Informatica MDM Hub Log Files (Windows)................................................................................271ORS Debug Log Setup .......................................................................................................................275

Bypassing Prerequisite Installation .............................................................................................................276Updating Parameters After Installation .....................................................................................................276

Updating Hub Server Parameters After Installation ......................................................................276Updating Cleanse Match Server Parameters After Installation ....................................................277

Checking the Hub and Cleanse Match Server Silent Install....................................................................278Checking the Hub Server and Cleanse Match Server Silent Install (Unix).................................278Checking the Hub Server and Cleanse Match Server Silent Install (Windows).........................282

MATCH Process Error: VerifyNeedToStrip ............................................................................................286VerifyNeedToStrip (Unix) .................................................................................................................286VerifyNeedToStrip (Windows) .........................................................................................................287

Inaccurate Start/Stop Timestamp for ORS ..............................................................................................287major.minor Version Errors When Loading Cleanse Match Server......................................................288Low Cleanse/Match Application Server Performance............................................................................288Troubleshooting (JBoss / Unix) .................................................................................................................289

Changing the Hub Server Parameters (JBoss/Unix) .....................................................................289Manually Redeploying the Hub Server (JBoss/Unix) ....................................................................290Manually Undeploying the Cleanse Match Server (JBoss/Unix) .................................................290Setting the JVM Size (JBoss/Unix)...................................................................................................291

Troubleshooting (WebLogic / Unix) .........................................................................................................292Changing the Hub Server Parameters (WebLogic/Unix) .............................................................292

Contents ix

Changing the Cleanse Match Server Parameters (WebLogic/Unix)........................................... 295Changing the Hub Server Parameters for the Database (WebLogic/Unix) .............................. 298Manually Redeploying Hub Server (WebLogic/Unix) .................................................................. 299Manually Undeploying the Cleanse Match Server (WebLogic/Unix) ........................................ 300Setting the JVM Size (WebLogic/Unix) .......................................................................................... 300

Troubleshooting (WebSphere / Unix) ...................................................................................................... 301Changing the Hub Server Parameters (WebSphere/Unix) .......................................................... 301Changing the Cleanse Match Server Parameters (WebSphere/Unix)......................................... 302Changing the Hub Server Parameters for the Database (WebSphere/Unix)............................ 303Manually Redeploying the Hub Server Application (WebSphere/Unix) ................................... 304Manually Undeploying the Cleanse Match Server (WebSphere/Unix) ...................................... 305Setting the JVM Size (WebSphere/Unix)........................................................................................ 305Changing the SOAP Request Timeout (WebSphere/Unix)......................................................... 306

Troubleshooting (JBoss / Windows)......................................................................................................... 306Changing the Hub Server Parameters (JBoss/Windows)............................................................. 306Manually Redeploying Hub Server (JBoss/Windows) .................................................................. 307Manually Undeploying the Cleanse Match Server (JBoss/Windows)......................................... 308Setting the JVM Size (JBoss/Windows) .......................................................................................... 308

Troubleshooting (WebLogic / Windows)................................................................................................. 309Changing the Hub Server Parameters (WebLogic/Windows)..................................................... 309Changing the Cleanse Match Server Parameters (WebLogic/Windows)................................... 311Changing the Hub Server Parameters for the Database (WebLogic/Windows) ...................... 314Manually Redeploying Hub Server (WebLogic/Windows).......................................................... 315Manually Undeploying the Cleanse Match Server (WebLogic/Windows) ................................ 316Setting the JVM Size (WebLogic/Windows).................................................................................. 316

Troubleshooting (WebSphere / Windows) .............................................................................................. 316Changing the Hub Server Parameters (WebSphere/Windows) .................................................. 317Changing the Cleanse Match Server Parameters (WebSphere/Windows)................................. 317Changing the Hub Server Parameters for the Database (WebSphere/Windows).................... 318Manually Redeploying Hub Server (WebSphere/Windows)........................................................ 319Manually Undeploying the Cleanse Match Server (WebSphere/Windows) .............................. 320Setting the JVM Size (WebSphere/Windows)................................................................................ 320Changing the SOAP Request Timeout (WebSphere/Windows)................................................. 320

x Informatica MDM Hub 9.0.1 Installation Guide

Appendix A: Installing from the Command Line

Preparing for Installation..............................................................................................................................324Installing from the Command Line (JBoss/Unix) ...................................................................................325

Installing Hub Server ..........................................................................................................................325Installing the Cleanse Match Server..................................................................................................328

Installing from the Command Line (WebLogic/Unix) ...........................................................................332Installing the Hub Server....................................................................................................................332Installing the Cleanse Match Server..................................................................................................334

Installing from the Command Line (WebSphere/Unix) .........................................................................337Installing Hub Server ..........................................................................................................................337Installing the Cleanse Match Server..................................................................................................340

Silent Installation from the Command Line..............................................................................................344Considerations When Using Silent Installation ..............................................................................344Properties Files for Silent Installation ..............................................................................................344Creating Your Properties File ............................................................................................................345Running the Silent Install ...................................................................................................................353

Appendix B: Manually Configuring Informatica System Message Queues

About Informatica MDM Hub Message Queues.....................................................................................356Configuring Message Queues (JBoss/Unix) .............................................................................................356

Creating and Configuring a New Message Queue..........................................................................357Configuring Additional Message Queues ........................................................................................358

Configure Message Queues (WebLogic/Unix).........................................................................................359Creating and Configuring a New Message Queue..........................................................................359Configuring Additional Message Queues ........................................................................................361

Configuring Message Queues (WebSphere/Unix) ...................................................................................362Creating and Configuring a New Message Queue..........................................................................362Configuring Additional Message Queues ........................................................................................364

Configure Message Queues (JBoss/Windows).........................................................................................365Creating and Configuring a New Message Queue..........................................................................365Configuring Additional Message Queues ........................................................................................367

Configure Message Queues (WebLogic/Windows).................................................................................368

Contents xi

Creating and Configuring a New Message Queue ......................................................................... 368Configuring Additional Message Queues ........................................................................................ 370

Configure Message Queues (WebSphere / Windows)............................................................................ 371Creating and Configuring a New Message Queue ......................................................................... 371Configuring Additional Message Queues ........................................................................................ 373

xii Informatica MDM Hub 9.0.1 Installation Guide

Preface

Welcome to the Informatica MDM Hub™ 9.0.1 Installation Guide. This guide explains how to perform a first-time installation of Informatica MDM Hub Server and the Cleanse Match Server.

Note If you are upgrading from a previous version of Informatica MDM Hub, see the Informatica MDM Hub Upgrade Guide instead.

Chapter Contents

• Intended Audience

• Contents

• Learning About Informatica MDM Hub

• Informatica Global Customer Support

• Informatica Resources

Intended Audience

This guide is for database administrators, system administrators, and implementers who are responsible for installing and setting up Informatica MDM Hub. System administrators must be familiar with their target operating system. Database administrators must be familiar with the database environment on which they are installing the Informatica MDM Hub. Knowledge of Oracle administration is particularly important. Other administration and configuration tasks are described in the Informatica MDM Hub Administrator Guide.

xiii

Contents

Contents

This guide contains the following chapters.

For more detail on the property files for the MDM Hub, see the appendices in the Informatica MDM Hub Administrator Guide.

Chapter 1, “Introduction” Describes Informatica MDM Hub architecture and orients you to the installation process

Chapter 2, “Installing the Hub Store” Explains how to install the Hub Store

Chapter 3, “Installing the Hub Server” Explains how to install and configure Hub Server

Chapter 4, “Installing the Cleanse Match Server”

Explains how to install and configure Cleanse Match Server

Chapter 5, “Launching the Hub Console”

Explains how to launch the Hub Console

Chapter 6, “Clustering” Explains how to configure clustering for Informatica MDM Hub.

Chapter 7, “Uninstalling Informatica MDM Hub”

Explains how to uninstall your Informatica MDM Hub system

Chapter 8, “Troubleshooting” Explains how to troubleshoot your installation

Appendix A, “Installing from the Command Line”

Explains how to install Informatica Hub Server and Cleanse Match Server from the command line. Unix implementations only.

Appendix B, “Manually Configuring Informatica System Message Queues”

Explains how to configure message queues for use with Informatica MDM Hub.

Index Index for this guide

xiv Informatica MDM Hub 9.0.1 Installation Guide

Learning About Informatica MDM Hub


What’s New in Informatica MDM Hub

The What’s New in Informatica MDM Hub describes the new features in this Informatica MDM Hub release.

Informatica MDM Hub Release Notes

The Informatica MDM Hub Release Notes contain important information about this release of Informatica MDM Hub. Read the Informatica MDM Hub Release Notes before installing Informatica MDM Hub.

Informatica MDM Hub Overview

The Informatica MDM Hub Overview introduces Informatica MDM Hub, describes the product architecture, and explains core concepts that all users need to understand before using the product.

Informatica MDM Hub Installation Guide

The Informatica MDM Hub Installation Guide for your platform explains how to install Informatica MDM Hub and Cleanse Match Server. There is an Informatica MDM Hub Installation Guide for each supported platform.

Informatica MDM Hub Upgrade Guide

The Informatica MDM Hub Upgrade Guide explains to installers how to upgrade a previous Informatica MDM Hub version to the most recent version.

Informatica MDM Hub Cleanse Adapter Guide

The Informatica MDM Hub Cleanse Adapter Guide explains to installers how to configure Informatica MDM Hub to use the supported adapters and cleanse engines.

xv


Informatica MDM Hub Data Steward Guide

The Informatica MDM Hub Data Steward Guide explains how to use Informatica MDM Hub. It provides a description of the Informatica MDM Hub platform through a discussion of Informatica MDM Hub concepts and tasks. Data stewards and users who are new to Informatica MDM Hub should read the Informatica MDM Hub Data Steward Guide first.

Informatica MDM Hub Administrator Guide

The Informatica MDM Hub Administrator Guide explains how to configure, administer, and manage an Informatica MDM Hub implementation. It provides a description of the Informatica MDM Hub platform through a discussion of Informatica MDM Hub concepts, services, tools, and databases. Administrators should read the Informatica MDM Hub Administrator Guide first.

Informatica MDM Hub Services Integration Framework Guide

The Informatica MDM Hub Services Integration Framework Guide explains how to use the Informatica MDM Hub Services Integration Framework (SIF) to integrate Informatica MDM Hub functionality with your applications and how to create applications using the data provided by Informatica MDM Hub. SIF allows you to integrate Informatica MDM Hub smoothly with your organization's applications.

Informatica MDM Hub Metadata Manager Guide

The Informatica MDM Hub Metadata Manager Guide explains how to use the Informatica MDM Hub Metadata Manager tool to validate their organization’s metadata, promote changes between repositories, import objects into repositories, export repositories, and related tasks.

Informatica MDM Hub Resource Kit Guide

The Informatica MDM Hub Resource Kit Guide explains how to install and use the Informatica MDM Hub Resource Kit, which is a set of utilities, examples, and libraries that assist developers with integrating the Informatica MDM Hub into their

xvi Informatica MDM Hub 9.0.1 Installation Guide

Informatica Global Customer Support

applications and workflows. This document provides a description of the various sample applications that are included with the Resource Kit.

Informatica Training and Materials

Informatica provides live, instructor-based training to help you become a proficient user as quickly as possible. From initial installation onward, a dedicated team of qualified trainers ensure that your staff is equipped to take advantage of this powerful platform. To inquire about training classes or to find out where and when the next training session is offered, please visit our website or contact Informatica directly.


You can contact a Customer Support Center by telephone or through the WebSupport Service. WebSupport requires a user name and password. You can request a user name and password at http://my.informatica.com. Use the following telephone numbers to contact Informatica Global Customer Support:

North America / South America

Europe / Middle East / Africa Asia / Australia

Toll Free

North America +1 877 463 2435

Brazil 0800 891 0202

Mexico 001 888 209 8853

Toll Free

United Kingdom00800 4632 4357or 0800 023 4632

France 00800 4632 4357

Netherlands 00800 4632 4357

Germany 00800 4632 4357

Switzerland 00800 4632 4357

Israel 00800 4632 4357

Spain 900 813 166

Portugal 800 208 360

Italy 800 915 985

Toll Free

Australia 1 800 151 830

New Zealand 1 800 151 830

Singapore 001 800 4632 4357

xvii

http://my.informatica.com

Informatica Resources


Informatica Customer Portal

As an Informatica customer, you can access the Informatica Customer Portal site at http://my.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, the Informatica Multimedia Knowledge Base, Informatica Documentation Center, and access to the Informatica user community.

Informatica Documentation

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

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

Standard Rate

North America+1 650 653 6332

Standard Rate

Belgium +32 15 281 702

France 0805 804632

Germany +49 1805 702 702

Netherlands +31 306 022 797

Switzerland 0800 463 200

Standard Rate

India +91 80 4112 5738

North America / South America

Europe / Middle East / Africa Asia / Australia

xviii Informatica MDM Hub 9.0.1 Installation Guide






Informatica Web Site

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

Informatica How-To Library

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

Informatica Knowledge Base

As an Informatica customer, you can access the Informatica Knowledge Base at http://my.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 Multimedia Knowledge Base

As an Informatica customer, you can access the Informatica Multimedia Knowledge Base at http://my.informatica.com. The Multimedia Knowledge Base is a collection of instructional multimedia files that help you learn about common concepts and guide you through performing specific tasks. If you have questions, comments, or ideas about the Multimedia Knowledge Base, contact the Informatica Knowledge Base team through email at [email protected].

xix

http://www.informatica.com






xx Informatica MDM Hub 9.0.1 Installation Guide

1
Introduction
This chapter summarizes the installation process and describes steps that you must complete before proceeding with Informatica MDM Hub installation. Subsequent chapters describe each step in the installation process.

Note: If you are upgrading from an earlier version of Informatica MDM Hub, see the Informatica MDM Hub Upgrade Guide instead for upgrade and configuration details.

Chapter Contents

• Before You Begin

• Installation Overview

• Designing Your Informatica MDM Hub Installation

• Documenting Your Installation

1

Before You Begin

Before You Begin

Before you begin, be sure to complete the following tasks:

Task Resource

Read the Informatica MDM Hub Release Notes for requirements and additional information about pre-installation preparation.

Informatica MDM Hub Release Notes

Read the worksheet for your installation—created by an Informatica Global Customer Support representative (see“Informatica Global Customer Support” on page xvii)—indicating the hardware and software needed to install Informatica MDM Hub at your location.


Install and configure your site’s cleanse engine according to the vendor’s instructions.

Vendor documentation for your cleanse engine

Read the Informatica MDM Hub Overview for an introduction to the product architecture and key components.

Informatica MDM Hub Overview

2 Informatica MDM Hub 9.0.1 Installation Guide

Installation Overview


To install Informatica MDM Hub, complete the following steps in the exact order specified:

Step Task Instructions

1 Install the Hub Store in your Oracle database.

“Installing the Hub Store” on page 11

2 Install the Hub Server software. “Installing the Hub Server” on page 43

3 Install and configure one or more Cleanse Match Servers.

“Installing the Cleanse Match Server” on page 109

4 Launch the Hub Console and verify your installation.

“Launching the Hub Console” on page 223

Introduction 3

Designing Your Informatica MDM Hub Installation


Before you install Informatica MDM Hub, you need to decide how and where to set up the various components that will comprise your Informatica MDM Hub implementation.

Implementation Components

As described in the Informatica MDM Hub Overview, an Informatica MDM Hub installation includes the following key components.

Component Description

Hub Store A collection of databases in which business data is stored and consolidated. A Hub Store consists of one Master Database (which contains environment configuration settings for the Informatica MDM Hub) and one or more Operational Reference Stores—or ORS databases (which contains master data, content metadata, processing rules, and other information related to business data).

Hub Server Run-time component that manages core and common services for the Informatica MDM Hub. The Hub Server is a J2EE application, deployed on the application server, that orchestrates the data processing within the Hub Store, as well as integration with external applications.

The Hub Console, which is packaged inside the Hub Server application, is the Informatica MDM Hub user interface that comprises a set of administrative and data management tools for administrators and data stewards. It can be launched on any client machine via a URL using a browser and Sun’s Java Web Start.

Cleanse Match Server Run-time component handles cleanse and match requests and is deployed in the application server environment. The Cleanse Match Server contains a cleanse server that handles data cleansing operations, and a match server that handles match operations.

Cleanse Engine(s) Any of the supported cleanse engines, as described in Informatica MDM Hub Cleanse Adapter Guide. The Cleanse Match Server and the cleanse engine work together to standardize the data and to optimize the data for match and consolidation.



Installation Environments

Informatica MDM Hub implementations comprise multiple environments, such as development, test, and production. Each type of environment comes with its own set of unique requirements and priorities. Therefore, the installation design will differ for each environment.

Example Installations

There are many possible ways in which you can set up the various Informatica MDM Hub components in your environment. This section provides two examples of Informatica MDM Hub installations. Their purpose is instructive rather than prescriptive—they illustrate some general principles to consider while designing your installation. They are not intended as recommended or even suggested installation designs.

Introduction 5


All Components on a Single Host

In the following example, all Informatica MDM Hub core components are installed on a single host machine.

o

This layout simplifies communication among the components within a single host environment.



Components Distributed on Multiple Hosts

In the following example, various Informatica MDM Hub components are distributed among multiple host machines.

Note: There needs to be an Oracle client installed on both the Hub Server and the Cleanse Match Server.

Consider the following issues:• Hub Server machines can be deployed in an clustered application server

environment for failover purposes.

• Cleanse Match Server machines can be installed in a clustered environment for scalability purposes (see Chapter 6, “Clustering”).

Introduction 7

Documenting Your Installation


You need to capture the details of your Informatica MDM Hub setup during and after installation in case you encounter issues in your environment. This information can prove extremely useful with verification and troubleshooting. If necessary, you can provide copies of this information to Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii).

Installation and Post-Installation Documentation

Sources of information about your Informatica MDM Hub installation include:

Important: The instructions in this document remind you to capture and save this information if needed for future reference. You will create a folder (such as install_doc) where you will centrally store copies of all your installation documentation.

Information About Source of Information

ORS metadata Validation Results report from the Metadata Manager tool in the Hub Console. Used to document ORS metadata after the installation. For instructions, see Informatica MDM Hub Metadata Manager Guide.

configuration settings Environment Report from the Enterprise Manager tool in the Hub Console. Used to document Hub Server, Cleanse Match Server, Master Database, and ORS database information after installation. For instructions, see Appendix D, “Viewing Configuration Details,” in the Informatica MDM Hub Administrator Guide.

database changes Database debug log. Used to log database events for your Hub Store once an ORS is registered in the Hub Console. Enabled according to the instructions in “Enabling Debug Logging” on page 270.

installation process Informatica MDM Hub Installer log files. Used to capture events that occur during Hub Server and Cleanse Match Server installation.

Hub Server and Cleanse Match Server

Hub Server and Cleanse Match Server log files, which capture run-time events after these components are running.

Hub Console Hub Console log files that capture activity while using the Hub Console.



Create an Installation Documentation Directory

Create a folder (such as install_doc) where you will centrally store copies of all your installation artifacts—such as the Validation Results and Environment reports, database debug log, log files, and other items described in “Installation and Post-Installation Documentation” on page 8.

Important: In the event that problems arise with your installation, you will need to create an archive file of this directory and send it to Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii) for analysis.

Introduction 9

2
Installing the Hub Store
This chapter explains how to install the Hub Store on an Oracle database platform. Your Oracle database administrator might need to complete the tasks in this chapter. Unless otherwise indicated, the instructions in this chapter apply to all supported application servers on all supported platforms. Refer to the Informatica MDM Hub Release Notes for system requirements.

Chapter Contents

• About the Hub Store

• Overview of Steps to Install the Hub Store

• Prepare Your Oracle Deployment for Informatica MDM Hub

• Create an Oracle Database for the Hub Store

• Create Tablespaces Used by the Hub Store

• Create the Hub Store

• Test the Database Connection

• Create a Proxy User

• Create an Additional ORS Database

11

About the Hub Store

About the Hub Store

The Hub Store is where business data is stored and consolidated in Informatica MDM Hub.

Master Database and Operational Reference Store (ORS)

The Hub Store is a collection of databases that includes:

Relationships Among Databases in the Hub Store

An Informatica MDM Hub implementation contains one Master Database and zero or more ORS databases. If no ORS exists, then only the Configuration workbench tools are available in the Hub Console. An Informatica MDM Hub implementation can have multiple ORSs, such as separate ORSs for development and production, or separate ORSs for each geographical location or for different parts of the organization.

Element Description

Master Database Contains the Informatica MDM Hub environment configuration settings—user accounts, security configuration, ORS registry, message queue settings, and so on. A given Informatica MDM Hub environment can have only one Master Database. The default name of the Master Database is CMX_SYSTEM.

Operational Reference Store (ORS)

Database that contains the master data, content metadata, the rules for processing the master data, the rules for managing the set of master data objects, along with the processing rules and auxiliary logic used by the Informatica MDM Hub in defining the best version of the truth (BVT). An Informatica MDM Hub configuration can have one or more ORS databases. The default name of an ORS is CMX_ORS.


About the Hub Store

This architecture allows you to distribute ORS databases across multiple server machines, each controlled by a central Master Database. You can access and manage multiple ORSs from one Master Database. The Master Database stores the connection settings and properties for each ORS.

Note: An ORS is typically registered in only one Master Database.

User accounts to access Hub Store databases are created globally—within the Master Database—and then assigned to specific ORSs.

Single Informatica MDM Hub Version Requirement

All the components of your Informatica MDM Hub implementation must be of the same Informatica MDM Hub version. If you have multiple versions of Informatica MDM Hub installed, each version must be installed in a separate environment. Different versions of Informatica MDM Hub cannot co-exist in the same environment.

Installing the Hub Store 13

About the Hub Store

Oracle RAC Considerations

This section provides an overview of using Oracle RAC with your Informatica MDM Hub implementation. Additional manual configuration steps are required in order to make use of Oracle RAC features and to optimize the environment for performance. Note that there are some components of the Informatica MDM Hub that do not support Oracle RAC load-balanced connections.

For more information, see the following documents:• Informatica MDM Hub Upgrade Guide

• Informatica MDM Hub Release Notes

Use of Oracle Service Names

The recommended approach from Oracle is to use Oracle service names instead of Oracle SIDs—even for non-RAC installations. This approach provides a more flexible method of specifying the connection and allows for the customer to dynamically reallocate database servers using service names.

About Oracle RAC Load-Balanced Connections

Oracle RAC provides the ability to specify a connection to an Oracle service that is load balanced between multiple database instances. This feature can be used in a fail-safe environment to seamlessly provide an available connection to the database even when one or more RAC instances are unavailable.

The following is an example of a tnsnames.ora entry that allows for a load-balanced connection to an Oracle service called mrm_service.domain.com.

MRM_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))


About the Hub Store

(CONNECT_DATA=(SERVICE_NAME = mrm_service.domain.com))

Connections to mrm_service are load balanced between the RAC nodes on server1, server2, or server3.

Setting Up Oracle RAC with Informatica MDM Hub

Configuring Informatica MDM Hub with Oracle RAC is the same as configuring a regular (single instance) Oracle database, except that the database connections must be specified to use the multiple instances.

A tnsnames entry (as shown previously) is used to reference the Oracle service that is hosting the Informatica MDM Hub. The JDBC connection is automatically configured to connect to the load-balanced service using a wizard in the Databases tool in the Hub Console, as described in the Informatica MDM Hub Administrator Guide.

Informatica MDM Hub Components and Load Balanced Connections

Once the tnsnames.ora entry and the JDBC data source is configured to make use of the Oracle RAC load-balanced connection, most Informatica MDM Hub components will make use of this and will automatically use the available nodes. However, some parts of the Informatica MDM Hub that build their own direct JDBC connection do not support load balancing because the metadata used to specify the multiple virtual IPs (VIPs) of the Oracle RAC nodes is not known.

Oracle RAC node balancing works for the following Informatica MDM Hub components:


Batch Jobs When called from a command line, because batch jobs use the tnsnames.ora settings.

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


About the Hub Store

The following components do not use Oracle RAC load balancing (if the main node is down, they cannot connect):• Batch Jobs called from the Hub Console

• Creating a Hierarchy Manager (HM) sandbox – uses a direct JDBC connection

• Metadata Manager when DDL is required (because DDL uses a direct JDBC connection)

Cleanse Server Uses load-balanced JDBC connections from the cleanse server connection pool.

Metadata Manager When only DML is required – uses the application server connection pool.



Overview of Steps to Install the Hub Store

Overview of Steps to Install the Hub Store

To install the Hub Store, complete the following steps in the exact order specified:

If you need to add more ORS databases to your Hub Store, run the setup_ors.sql script (provided in your Informatica MDM Hub distribution) according to the instructions in “Create an Additional ORS Database” on page 36.

Note: Your Oracle database administrator might need to complete the tasks in this chapter.


1 Install and configure Oracle on a machine other than the machine on which your Hub Server will run.

“Prepare Your Oracle Deployment for Informatica MDM Hub” on page 18

2 Create an Oracle database for your Hub Store.

Oracle documentation

3 Create the Oracle tablespaces required for the Hub Store.

“Create Tablespaces Used by the Hub Store” on page 21

4 Create the Hub Store—Master Database and ORS database(s)—by running the setup.sql script provided in your Informatica MDM Hub distribution.

“Create the Hub Store” on page 23

5 Test the database connection. “Test the Database Connection” on page 32

6 Register the newly-created ORS database using the Databases tool in the Hub Console.

“Configuring Operational Record Stores and Datasources” in the Informatica MDM Hub Administrator Guide (see “Post-setup Tasks” on page 229)

7 Enable database logging for this ORS using the Enterprise Manager tool in the Hub Console.

Appendix D, “Viewing Configuration Details,” in the Informatica MDM Hub Administrator Guide (see “Post-setup Tasks” on page 229)


Prepare Your Oracle Deployment for Informatica MDM Hub


This section describes how to prepare your Oracle deployment for Informatica MDM Hub. It applies to all supported platforms and application servers.

Install and Configure Oracle

Install and configure Oracle on a machine that complies with the hardware and software requirements described in the Informatica MDM Hub Release Notes. Refer to this document for a list of supported Oracle versions.

The following software (part of your Oracle distribution) must be installed on every machine on which you want to run the Hub Server:• Oracle client

• Oracle Java utilities (required by the Oracle client)

• SQL*Loader

Note: Be sure to install Oracle with all Java options selected.



Turning Off the Oracle Recycle Bin

The Oracle Recycle Bin is enabled by default. The Oracle Recycle Bin can interfere with Informatica MDM Hub processes. Therefore, it is recommended that you disable the Oracle Recycle Bin for your Hub Store (RECYCLEBIN=OFF), and explicitly purge any existing objects in the Recycle Bin. There are two recycle bins (USER_RECYCLEBIN and DBA_RECYCLEBIN), and you can disable at the system or session level. For instructions, refer to your Oracle documentation.

Setting Oracle PLSQL Compiler Flags (Oracle 10gR2 Only)

Note: Skip this section if you are not using Oracle 10gR2 in your Informatica MDM Hub implementation.

If you are using Oracle 10gR2, you must set the PLSQL compiler flags. In 10gR2, the default value for PLSQL_COMPILER_FLAGS is NATIVE. This causes Informatica MDM Hub packages to fail to compile. You must set PLSQL_COMPILER_FLAGS to be INTERPRETED.

To set the Oracle PLSQL compiler flags:1. Log into Oracle with DBA privileges (or SYSTEM).

2. Launch SQL*Plus.

3. Run the following commands from the command prompt:

SHOW PARAMETER plsql_compiler_flags;ALTER SYSTEM SET plsql_compiler_flags=INTERPRETED;

4. Close the connection to Oracle.


Create an Oracle Database for the Hub Store

Create an Oracle Database for the Hub Store

Once Oracle has been properly installed and configured, create an Oracle database according to your Oracle documentation. This Oracle database will contain your Hub Store.

Note: If your Informatica MDM Hub implementation will have multiple ORS databases distributed across different host servers, you will need to create Oracle databases on each of those machines.

For subsequent Hub Store setup, you will need the following information about this database:

Configuration Information

Oracle server TNS name

Oracle connection type (SERVICE or SID)

Oracle SERVICE or SID name

Oracle listener port number (such as 1521)

Oracle database server name (host running Oracle)

Oracle Connect URL (for SERVICE connection type only, and only if you need to change the default value)

Oracle SYSTEM username (such as SYSTEM)

Oracle SYSTEM password


Create Tablespaces Used by the Hub Store


This section describes how to create the Oracle tablespaces used by the Hub Store.

Note: The instructions for running SQL commands assume that you are logged into your Oracle database with administrator (or SYSTEM) privileges and are running commands from a SQL*Plus command prompt.

Tablespaces to Create

Hub Store requires three tablespaces with the following names:

Note: It is recommended that you use these default tablespace names for your Hub Store.

Your installation needs to be properly sized. In addition to the CMX_TEMP tablespace, sufficient ORACLE TEMP space must be available. The sizes described in this section are examples. Adjust the default sizes and number of data files based on your initial analysis of data volumes to be loaded into the Informatica MDM Hub.

Tablespace Description Instructions

CMX_DATA Default tablespace for the ORS schema.

“Creating CMX_DATA” on page 22

CMX_INDX Used for indexes created and used by Informatica MDM Hub.

“Creating CMX_INDX” on page 22

CMX_TEMP Used for temporary tables created and used by Informatica MDM Hub; used for stored procedures.

“Creating CMX_TEMP” on page 22



Creating CMX_DATA

Create the CMX_DATA tablespace as a locally-managed or manually-configured tablespace. Use commands similar to the following example.

CREATE TABLESPACE CMX_DATANOLOGGINGDATAFILE '<Oracle_install_dir>/CMX_DATA1.dbf' SIZE 2048M REUSEEXTENT MANAGEMENT LOCAL;COMMIT;

where <Oracle_install_dir> is your Oracle installation directory (also known as ORACLE_BASE).

Creating CMX_INDX

Create the CMX_INDEX tablespace as a locally-managed or manually-configured tablespace. Use commands similar to the following example.

CREATE TABLESPACE CMX_INDX NOLOGGING DATAFILE '<Oracle_install_dir>/CMX_INDX1.dbf' SIZE 2048M REUSE EXTENT MANAGEMENT LOCAL;COMMIT;


Creating CMX_TEMP

Important: This tablespace must not be created as an Oracle TEMPORARY tablespace.

Create the CMX_TEMP tablespace as a locally-managed or manually-configured tablespace. Use commands similar to the following example.

CREATE TABLESPACE CMX_TEMPNOLOGGINGDATAFILE '<Oracle_install_dir>/CMX_TEMP1.dbf' SIZE 2048M REUSE EXTENT MANAGEMENT LOCAL;


Create the Hub Store

COMMIT;



This section describes how to create the Hub Store and its constituent databases. At a minimum, your Hub Store consists of one Master Database and zero or more ORS databases (typically at least one ORS database, and possibly more).

About the setup.sql Script

Your Informatica MDM Hub distribution includes a setup.sql script that you use to create the Hub Store. This script:• creates the Master Database (default name: CMX_SYSTEM)

• creates one ORS database (default name: CMX_ORS)

• imports the initial metadata from the cmx_system.dmp file (which contains REPOS tables and other objects required to set up the initial state of your Hub Store)

You run this script when you first install Informatica MDM Hub. Once the Hub Store is created, if you need to add more ORS databases, you can run the setup_ors.sql script according to the instructions in “Create an Additional ORS Database” on page 36.

Default Database Names and Usernames

When running the setup.sql script, the default master database name is CMX_SYSTEM and the default ORS database name is CMX_ORS. If you must use a



different name for the Master Database or usernames that own these databases, contact Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii).

PROXY_ROLE

The setup.sql script creates the PROXY_ROLE when cmx_ors is created. The cmx_ors user owns this role. The setup.sql script grants the required privileges on all REPOS tables, views, sequences, procedures, packages, and functions to PROXY_ROLE.

Create the Hub Store (Unix)

Complete the following steps to create the Hub Store:1. Create a directory on the Oracle database server or on a client workstation that has

the Oracle client installed with Oracle utilities (imp).

Copy all of the files from the Informatica MDM Hub distribution (<infamdm_install_directory>/server/resources/database/oracle) to the directory you just created.

2. Change directory to the temporary directory you just created.

3. Start SQL*PLUS and connect to the server as SYSTEM or as a user with DBA privileges.

4. Execute the setup.sql script (in the database/oracle directory) by typing one of the following commands:

@setup.sql;

OR

start setup.sql

5. Answer the following prompts:



Important: The text in brackets is the default information for each prompt. Press Enter to accept the default values and go to the next prompt.

Prompt Description

Enter Oracle Server TNS name: Name by which your Oracle database is known on your network. The TNS Name, which is set at Oracle installation, has the following format:

mydatabase.mycompany.com

For more information about TNS names, see your Oracle documentation.

Enter Oracle Connection Type (SERVICE, SID) [SERVICE]:

Connection type. One of the following values:

• SERVICE: Connect to Oracle via the service name.

• SID: Connect to Oracle via the Oracle System ID.

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

Enter Oracle SERVICE name: Name of the Oracle SERVICE. Displayed only if the selected Oracle Connection Type is SERVICE.

Enter Oracle SID Name: Name of the Oracle SID. Displayed only if the selected Oracle Connection Type is SID.

Enter Oracle Listener Port number [1521]:

Port number used by the Oracle listener.

Enter Oracle database server name: Name of the host running Oracle.



Enter Connect URL (only for SERVICE type):

Custom SERVICE Connect URL here for RAC (if different from the default).

Format:

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

Example:

jdbc:oracle:thin:@//shoskin-mac:1521/shoskin

The setup.sql script automatically constructs a Connect URL based on your previous selections. For a SERVICE connection type (only), you have the option to specify a different URL. For a SID connection type, the format is:

jdbc:oracle:thin:@database_host:port:SID

Enter Oracle SYSTEM username: [SYSTEM]

Oracle SYSTEM username.

Enter Oracle SYSTEM password: Password for the Oracle SYSTEM account.

Enter name of new CMX System (Master) user [CMX_SYSTEM]:

Oracle user name that the script creates. This user owns all the Master Database database objects in the Hub Store.

Enter Name of Data tablespace [CMX_DATA]:

Name of the tablespace to contain the data components for the Master Database. See “Creating CMX_DATA” on page 22.

Enter name of Temporary tablespace [TEMP]:

Name of the tablespace to contain the temporary components for the Master Database. See “Creating CMX_TEMP” on page 22.

Import into CMX_SYSTEM: Enter the Oracle export file name [cmx_system.dmp]

Name of the Oracle export file containing the initial metadata for the Master Database (REPOS tables and other objects required to set up the initial state of your Hub Store). This is included as part of the Informatica MDM Hub install. Do not change this name— accept the default. The script will look for the default dump file. If it does not find this file, the script generates a warning and proceeds to the next prompt.

Import into CMX_SYSTEM: Enter the source schema name (fromuser) for the export file [CMX_SYSTEM]:

Username under which the cmx_system.dmp file was exported. Accept the default. Do not change this username.

Prompt Description



6. After the setup script is complete, check the following log files:

• setup.log

• cmx_sys_imp.log

• cmx_ors_imp.log

Enter name of User [CMX_ORS]: Oracle user name that the script creates. This user owns all the ORS database objects in the Hub Store.

Enter password for ORS User [!!CMX!!]:

Password for the CMX_ORS user account.

Enter name of MRM Data tablespace [CMX_DATA]:

Name of the tablespace to contain the data components for the ORS. See “Creating CMX_DATA” on page 22.

Enter name of MRM Index tablespace [CMX_INDX]:

Name of the tablespace to contain the indexes for the ORS. See “Creating CMX_INDX” on page 22.

Enter name of MRM Temporary tablespace (Not an Oracle temp tablespace) [CMX_TEMP]:

Name of the tablespace to contain the temporary components for the ORS. See “Creating CMX_TEMP” on page 22.

Enter name of the Oracle Temporary tablespace [TEMP]:

Name of the Oracle temporary tablespace. This is different from the CMX_TEMP tablespace created earlier.

Enter GGS install path if applicable: Directory containing the GGSCI executable. Applicable only if your Informatica MDM Hub implementation will use Golden Gate software for data replication. For more information, see the Informatica MDM Zero Downtime (ZDT) Install Guide.

Import into ors_name: Enter the Oracle export file name [cmx_ors.dmp]:

Name of the Oracle export file containing the initial metadata for the ORS database (other objects required to set up the initial state of your ORS). You can use another export file name. This is part of the Informatica MDM Hub install. If the script does not find this file, it generates a warning and proceeds to the next prompt.

Import into ors_name: Enter source schema name (fromuser) for the export file [CMX_ORS]:

Username under which the ORS dump file was exported. Accept the default. Do not change this username.

Prompt Description



These log files are created in the directory from which you ran the script. Review these files to ensure that no errors occurred.

• You may see some warnings, which can be ignored.

• Errors must be addressed. If you see database error in the logs, resolve these first with your DBA and/or database vendor, and then re-run the setup.sql script.

• Copy the log files to the installation documentation directory you created earlier. See “Documenting Your Installation” on page 8 for instructions.

Note: After you install the Informatica MDM Hub software, you will need to register the newly-created ORS databases (CMX_ORS) using the Databases tool in the Hub Console. For more information, see “Post-setup Tasks” on page 229.

Create the Hub Store (Windows)

If Oracle is running in the Windows environment, complete the following steps to create the Hub Store:1. Create a temporary directory on the Oracle database server or on a client

workstation that has Oracle client installed with Oracle utilities.

Copy all of the files from the Informatica MDM Hub distribution (<infamdm_install_directory>\server\resources\database\oracle) to the temporary directory you just created.

2. Open a command window.

Go to the Windows Start menu. choose Run and enter cmd.

3. Go to the temporary directory you just created.

4. To start SQL*PLUS, enter:

sqlplus

Press Enter.

5. Connect to the server as SYSTEM or as a user with DBA privileges.

6. Execute the setup.sql script (in your distribution’s database\oracle directory) by typing the following command:



@setup.sql

7. Answer the following prompts.

Important: The text in brackets is the default information for each prompt. Press Enter to use the default information and go to the next prompt.

Prompt Description

Enter Oracle Server TNS name: Name by which your Oracle database is known on your network. The TNS Name, which is set at Oracle installation, has the following format:



Enter Oracle Connection Type (SERVICE, SID) [SERVICE]:

Connection type. One of the following values:

• SERVICE: Connect to Oracle via the service name.



Enter Oracle SERVICE name: Name of the Oracle SERVICE. Displayed only if the selected Oracle Connection Type is SERVICE.

Enter Oracle SID Name: Name of the Oracle SID. Displayed only if the selected Oracle Connection Type is SID.

Enter Oracle Listener Port number [1521]:

Port number used by the Oracle listener.

Enter Oracle database server name: Name of the host running Oracle.



Enter Connect URL (only for SERVICE type):

Custom SERVICE Connect URL here for RAC (if different from the default).

Format:

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

Example:

jdbc:oracle:thin:@//shoskin-mac:1521/shoskin

The setup.sql script automatically constructs a Connect URL based on your previous selections. For a SERVICE connection type (only), you have the option to specify a different URL.

Enter Oracle SYSTEM username: [SYSTEM]

Oracle SYSTEM username.

Enter Oracle SYSTEM password: Password for the Oracle SYSTEM account.

Enter name of new CMX System (Master) user [CMX_SYSTEM]:

Oracle user name that the script creates. This user owns all the Master Database database objects in the Hub Store.

Enter Name of Data tablespace [CMX_DATA]:

Name of the tablespace to contain the data components for the Master Database. See “Creating CMX_DATA” on page 22.

Enter name of Temporary tablespace [TEMP]:


Import into CMX_SYSTEM: Enter the Oracle export file name [cmx_system.dmp]

Name of the Oracle export file containing the initial metadata for the Master Database (REPOS tables and other objects required to set up the initial state of your Hub Store). This is included as part of the Informatica MDM Hub install. Do not change this name— accept the default. The script will look for the default dump file. If it does not find this file, the script generates a warning and proceeds to the next prompt.

Import into CMX_SYSTEM: Enter the source schema name (fromuser) for the export file [CMX_SYSTEM]:

Username under which the cmx_system.dmp file was exported. Accept the default. Do not change this username.

Enter name of User [CMX_ORS]: Oracle user name that the script creates. This user owns all the ORS database objects in the Hub Store.

Prompt Description



8. After the setup script is complete, check the following log files:

• setup.log

• cmx_system.dmpimp.log

• cmx_ors.dmpimp.log

These log files are created in the directory from which you ran the script. Review these files to ensure that no errors occurred.






Name of the tablespace to contain the indexes for the ORS. See “Creating CMX_INDX” on page 22.


Name of the tablespace to contain the temporary components for the ORS. See “Creating CMX_TEMP” on page 22.


Name of the Oracle temporary tablespace. This is different from the CMX_TEMP tablespace created earlier.

Enter GGS install path if applicable: Directory containing the GGSCI executable. Applicable only if your Informatica MDM Hub implementation will use Golden Gate software for data replication. For more information, see the Informatica MDM Zero Downtime (ZDT) Install Guide.

Import into ors_name: Enter the Oracle export file name [cmx_ors.dmp]:

Name of the Oracle export file containing the initial metadata for the ORS database (other objects required to set up the initial state of your ORS). You can use another export file name. This is part of the Informatica MDM Hub install. If the script does not find this file, it generates a warning and proceeds to the next prompt.

Import into ors_name: Enter source schema name (fromuser) for the export file [CMX_ORS]:

Username under which the ORS dump file was exported. Accept the default. Do not change this username.

Prompt Description


Test the Database Connection

• You may see some warnings, which can be ignored.

• Errors must be addressed. If you see database error in the logs, resolve these first with your DBA and/or database vendor, and then re-run the setup.sql script.

• Copy the log files to the installation documentation directory you created earlier. See “Documenting Your Installation” on page 8 for instructions.

Test the Database Connection

Test the database connections from all the machines on which you plan to run either the Hub Server or a Cleanse Match Server. To test these connections, complete the following steps on each machine:1. Create the TNS names entries for the database.

Important: Each machine must have the same TNS name.

2. Verify that the database connections work properly.

For more information about TNS names entries, refer to your Oracle documentation.

Note: After you install the Informatica MDM Hub software, you will need to register the newly-created ORS databases (CMX_ORS) using the Databases tool in the Hub Console. For more information, see “Post-setup Tasks” on page 229.


Create a Proxy User

Create a Proxy User

This section describes how to create a proxy user for your Informatica MDM Hub implementation. Creating a proxy user is an optional task but is recommended for certain situations.

Proxy Users in Informatica MDM Hub Implementations

A proxy user is a database user that is configured to have limited privileges to provide restricted data access to an ORS. You can configure multiple proxy users for a single ORS.

Proxy users are typically configured in production environments with stricter security requirements than in non-production environments. For example, a proxy user can be authorized to run Informatica MDM Hub batch jobs from the Hub Console or in job scheduling scripts.

Creating a Proxy User

The proxy role (PROXY_ROLE) is automatically created and assigned as part of the initial ORS database creation. Therefore, before you create a proxy user, you must have completed the following tasks:• created the ORS according to the instructions in “Create the Hub Store” on page

23 or “Create an Additional ORS Database” on page 36

• registered the database using the Databases tool in the Hub Console according to the instructions in the Informatica MDM Hub Administrator Guide

Once you have created a proxy user, you can associated it with the ORS using the Databases tool in the Hub Console.


Create a Proxy User

Creating a Proxy User (Unix)

To create a proxy user:1. Go to the following directory:

<infamdm_install_directory>/server/resources/database/oracle

2. Launch SQL*Plus and connect to the database as the system user.

3. Run mk_proxy_ors_user.sql to create a proxy user.

Answer the prompts to specify the proxy username and password, schema owner and password, tablespaces, and whether the proxy user will be used for replication.

4. Lock the original ORS by running the following SQL statement:

alter user <original_ors> account lock;

where <original_ors> is the original ORS owner account, which should be locked before granting privileges in order to prevent new objects from being created while the grant_priv_to_proxy_role.sql script is being run.

5. Run grant_priv_to_proxy_role.sql.

6. Unlock the original ORS by running the following SQL statement:

alter user <original_ors> account unlock

7. Register the proxy user using the Databases tool in the Hub Console according to the instructions in the Informatica MDM Hub Administrator Guide.

When registering, remove the current database registration (if it exists), and then add a new registration, specifying the ORS in the Schema Name field and the proxy user information.

8. Verify your configuration by running batch jobs and tests using the proxy user.

Creating a Proxy User (Windows)

To create a proxy user in the Windows environment:1. Go to the following directory:

<infamdm_install_directory>\hub\server\resources\database\oracle

2. Launch SQL*Plus and connect to the database as the system user.


Create a Proxy User

3. Run mk_proxy_ors_user.sql to create a proxy user.

Answer the prompts to specify the proxy username and password, schema owner and password, tablespaces, and whether the proxy user will be used for replication.

4. Lock the original ORS by running the following SQL statement:

alter user <original_ors> account lock;

where <original_ors> is the original ORS owner account, which should be locked before granting privileges in order to prevent new objects from being created while the grant_priv_to_proxy_role.sql script is being run.

5. Run grant_priv_to_proxy_role.sql.

6. Unlock the original ORS by running the following SQL statement:

alter user <original_ors> account unlock

7. Register the proxy user using the Databases tool in the Hub Console according to the instructions in the Informatica MDM Hub Administrator Guide.

When registering, remove the current database registration (if it exists), and then add a new registration, specifying the ORS in the Schema Name field and the proxy user information.

8. Verify your configuration by running batch jobs and tests using the proxy user.

For information about creating a proxy user during an upgrade, see the Informatica MDM Hub Upgrade Guide.


Create an Additional ORS Database


This section describes how to add an additional ORS database to the Hub Store. The instructions in this section assume that you have already created the Hub Store—with a Master Database and one ORS—according to the instructions in “Create the Hub Store” on page 23.

About the setup_ors.sql Script

Your Informatica MDM Hub distribution includes a setup_ors.sql script that:• creates one ORS database (default name: CMX_ORS)

• imports the initial metadata from the cmx_ors.dmp file (which contains the objects required to set up the initial state of your ORS)

Important: A Master Database is required to run the setup_ors.sql script. It does not create a Master Database for you.

Default Database Name

When running the setup_ors.sql script, the default ORS database name is CMX_ORS. The script allows you to change this name.

PROXY_ROLE

The setup_ors.sql script creates the PROXY_ROLE when cmx_ors is created. The cmx_ors user owns this role. The setup_ors.sql script grants the required privileges on all REPOS tables, views, sequences, procedures, packages, and functions to PROXY_ROLE.



Adding an ORS (Unix)

To set up the Hub Store with an additional ORS database:1. Create a directory on the Oracle database server or on a client workstation that has

the Oracle client installed with Oracle utilities (imp).

Copy all of the files from the distribution directory database/oracle/ to this temporary directory.

2. Change directory to the temporary directory you just created.

3. Start SQL*PLUS by typing “sqlplus” and connect to the server as SYSTEM or as a user with DBA privileges.

4. Execute the setup_ors.sql script (in the database/oracle directory) by typing the following command:

Linux and Solaris:

@setup_ors.sql;

HP-UX:

start setup_ors.sql


Note: The text in brackets is the default information for each prompt. Press Enter to accept the default values and go to the next prompt.

Prompt Description

Enter name of User [CMX_ORS]: Oracle user name that the script creates. This user owns all the ORS database objects in the Hub Store. If this user name already exists, the user will be dropped and recreated. To learn about changing this name, see “Changing the Password for the CMX_ORS User” on page 107.







6. After the setup scripts are complete, there are log files in the temporary directory from which you ran the scripts:


Name of the tablespace to contain the indexes. See “Creating CMX_INDX” on page 22.




Name of the Oracle temporary tablespace. Do not confuse this with the CMX_TEMP tablespace.

Note: Some database processing to create the ORS user occurs before the next prompt is displayed.

Enter ORACLE server TNS name: Name by which your Oracle database is known on your network. The TNS Name, which is set at Oracle installation, has the following format:



Enter name of DBA User [SYSTEM]: Oracle user account with administrative access, such as the Oracle SYSTEM username.

Enter password of DBA User: Password for the specified DBA User account.

Enter file to import [cmx_ors.dmp]: Name of the Oracle export file containing the initial metadata for the ORS database (other objects required to set up the initial state of your ORS). You can use another export file name. This is part of the Informatica MDM Hub install. If the script does not find this file, it generates a warning and proceeds to the next prompt.

Enter import fromuser name [cmx_ors]: Username under which the ORS dump file was exported as part of an upgrade. Accept the default. Do not change this username. The fact that the dump file does not exist is not a problem.

Enter GGS install path: Directory containing the GGSCI executable. Applicable only if your Informatica MDM Hub implementation will use Golden Gate software for data replication. For more information, see the Informatica MDM Zero Downtime (ZDT) Install Guide.

Prompt Description



• setup_ors.log


Review these files to ensure no errors occurred. You may see warnings, which can be ignored. Errors must be addressed.

If you see database errors in the logs, resolve these first with your DBA. Then re-run the setup_ors.sql script.

7. After creating the ORS, you need to register it in the Master Database using the Databases tool in the Hub Console according to the instructions in “Post-setup Tasks” on page 229.

Adding an ORS (Windows)

To set up the Informatica MDM Hub schemas with an additional ORS database:1. Create a temporary directory on the Oracle database server or on a client

workstation that has Oracle client installed with Oracle utilities.

Copy all of the files from the Informatica MDM Hub distribution (from <infamdm_install_directory>\server\resources\database\oracle) to the temporary directory you just created.

2. Open a command window.

Go to the Windows Start menu. choose Run and enter cmd.

3. Go to the temporary directory you just created.

4. To start SQL*PLUS, enter:

sqlplus

Press Enter.

5. Connect to the server as SYSTEM or as a user with DBA privileges.

6. Execute the setup_ors.sql script (in the database\oracle directory) by typing the following command:

@setup_ors.sql




Note: The text in brackets is the default information for each prompt. Press Enter to use the default information and go to the next prompt.

Prompt Description

Enter name of User [CMX_ORS]: Oracle user name that the script creates. This user owns all the ORS database objects in the Hub Store. If this user name already exists, the user will be dropped and recreated. To learn about changing this name, see “Changing the Password for the CMX_ORS User” on page 107.






Name of the tablespace to contain the indexes. See “Creating CMX_INDX” on page 22.




Name of the Oracle temporary tablespace. Do not confuse this with the CMX_TEMP tablespace.

Note: Some database processing to create the ORS user occurs before the next prompt is displayed.

Enter ORACLE server TNS name: Name by which your Oracle database is known on your network. The TNS Name, which is set at Oracle installation, has the following format:



Enter name of DBA User [SYSTEM]: Oracle user account with administrative access, such as the Oracle SYSTEM username.

Enter password of DBA User: Password for the specified DBA User account.



Note: When creating the CMX_ORS schema, you are prompted for the TEMPORARY tablespace name. Do not confuse this with the CMX_TEMP tablespace. When prompted, enter the Oracle temporary tablespace name (usually TEMP).

8. After the setup scripts are complete, there are log files in the temporary directory from which you ran the scripts:

• setup_ors.log


Review these files to ensure no errors occurred. You may see warnings, which can be ignored. Errors must be addressed.

If you see database error in the logs, resolve these first with your DBA and your RDBMS vendor, and then re-run the setup_ors.sql script.

9. After creating the ORS, you need to register it in the Master Database using the Databases tool in the Hub Console according to the instructions in “Post-setup Tasks” on page 229.

Enter file to import [cmx_ors.dmp]: Name of the Oracle export file containing the initial metadata for the ORS database (other objects required to set up the initial state of your ORS). You can use another export file name. This is part of the Informatica MDM Hub install. If the script does not find this file, it generates a warning and proceeds to the next prompt.

Enter import fromuser name [cmx_ors]: Username under which the ORS dump file was exported as part of an upgrade. Accept the default. Do not change this username. The fact that the dump file does not exist is not a problem.

Enter GGS install path: Directory containing the GGSCI executable. Applicable only if your Informatica MDM Hub implementation will use Golden Gate software for data replication. For more information, see the Informatica MDM Zero Downtime (ZDT) Install Guide.

Prompt Description


3
Installing the Hub Server
This chapter explains how to install and configure the Hub Server in your Informatica MDM Hub implementation. Instructions are organized alphabetically by application server and platform.

Note: If you have a previously-installed version of the Hub Server, see the Informatica MDM Hub Upgrade Guide instead for upgrade instructions. This chapter covers new installations.

Chapter Contents

• About the Hub Server

• Installing the Hub Server (JBoss/Unix)

• Installing the Hub Server (WebLogic/Unix)

• Installing the Hub Server (WebSphere/Unix)

• Installing the Hub Server (JBoss/Windows)

• Installing the Hub Server (WebLogic/Windows)

• Installing the Hub Server (WebSphere/Windows)

• Changing Passwords After Installation

43

About the Hub Server


Note: This section applies to the Hub Server regardless of platform or application server environment.

The Hub Server is the run-time component that manages core and common services for the Informatica MDM Hub. The Hub Server is a J2EE application, deployed on the application server, that orchestrates the data processing within the Hub Store, as well as integration with external applications.

Application Server and Connection Pooling

Informatica MDM Hub uses connection pooling from data source facilities provided by your J2EE application server. The Hub Server requires:• one data source for the Master Database

• a data source for each ORS database that is accessed through the server.

Manually Configuring Message Queues for Asynchronous SIF Requests

The Hub Server installer automatically sets up message queues and connection factory configuration. If you need to manually configure your message queues or connection factories for testing or troubleshooting purposes, see Appendix B, “Manually Configuring Informatica System Message Queues.”



PostInstallSetup

After the Hub Server installer copies the files to the Informatica installation directory, the Hub Server must be deployed and configured on the application server via the post-installation process. You can choose to have the installation program perform the post-installation process for you, or you can end the program before post-installation begins and do it manually using the postinstallsetup script.

Separating the installation and post-installation (deployment) functions has a few advantages:• It enables you to make sure that the application server starts up successfully before

you deploy it.

• It simplifies troubleshooting.

• It enables you to deploy the application using the application server’s administration console.



Installing the Hub Server 45

Installing the Hub Server (JBoss/Unix)


This section describes how to install the Hub Server running in the JBoss application server environment on the Unix platform.

Note: JBoss 5 should use JDK 1.6.0.14 or higher.


Hub Server installation involves the following steps:

Preparing for Installation

Complete the tasks in this section before you install the Hub Server.


1 Prepare the target environment, including setting up the application server.

“Preparing for Installation” on page 46

2 Install the Hub Server by running the installer.

“Running the Hub Server Installer” on page 49

3 Specify or change Hub Server configuration settings.

“Configuring the Hub Server” on page 54



Fulfill Hardware and Software Requirements

Before you install the Hub Server, fulfill the hardware and software requirements for the Hub Server as described in the Informatica MDM Hub Release Notes. In particular, make sure you have the correct version of the Oracle drivers.

Obtain an Informatica License File

Have an Informatica license file. The Hub Server installer will not install Informatica MDM Hub without a valid license file. Contact Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii) for a license.

Verify Physical Memory

Verify that you have sufficient physical memory available to satisfy the runtime needs of all the Informatica software you intend to install. Use the following formula to determine your physical memory requirements:Total Informatica runtime memory footprint = JDK JVM max heap size of the application server +OS native heap size (which varies for 32-bit and 64-bit platforms)

Verify Available Storage

The Hub Server requires 500MB of available disk space.

Install and Configure JBoss

Install and configure JBoss according to the instructions in the JBoss documentation.

Configure JBoss to Use an Oracle Datasource

Contact Oracle to obtain any JDBC drivers you may need for your database configuration. Once you obtain the drivers, configure JBoss as follows:

To configure JBoss to use an Oracle data source:• Copy the new Oracle JDBC driver files to your

<JBoss_install_dir>/server/<configuration_name>/lib directory.


Disable JMX Invoker Authentication

If JMX Invoker Authentication is enabled for your JBoss server, you must disable it in order to successfully create a datasource during ORS registration in the Hub Console. To disable JMX Invoker Authentication:1. Edit the following file:

<JBoss_install_dir>/server/<configuration_name>/deploy/jmx-invoker-service.xml

2. Remove or comment out the following lines:



Configure the JVM Memory Allocation Pool

Configure the JVM memory allocation pool parameters. Start with the following settings and modify as appropriate for your implementation.

set JAVA_OPTS=%JAVA_OPTS% -Xms256m -Xmx768m -Xss1000k -XX:PermSize=64m -XX:MaxPermSize=256m

Starting the JBoss Server

In order to successfully launch the Hub Console, you need to complete the following steps to start the JBoss server:1. Go to the following directory:

jboss-5.1.0.GA/bin

2. Run the following command:

run.sh -b 0.0.0.0


Running the Hub Server Installer

The Hub Server Installer is the program used to install the Hub Server software. It is included in your Informatica MDM Hub distribution.

Installation Considerations• Important: You must use the same username to install both Hub Server and

Cleanse Match Server. In addition, if you are installing the server and cleanse software on the same machine, the users who install them must belong to the same Unix group.

• File names and directories in this section may vary slightly depending on what type of installation you are performing.

Installation Steps

To run the Hub Server Installer:1. Make sure that your application server is started and running correctly.

2. If you are installing from a remote client, start an X windows session and set the display value to the remote client.

3. Go to the directory where the Hub Server installer resides. In the distribution, the Hub Server installer is in the following directory:

• Solaris: /mrmserver/solaris

• HP-UX: /mrmserver/hpux

• Linux: /mrmserver/linux

• AIX: /mrmserver/aix

4. Begin the installation process with the following command:

For the GUI installer:



./hub_install.bin

For the Console mode installer (see Appendix A, “Installing from the Command Line”):

./hub_install.bin -i console

Note: To bypass the prerequisite validation in the installation, see “Bypassing

Prerequisite Installation” on page 276.

The Hub Server Installer displays the Introduction screen.

5. Click Next to continue.

The License Agreement screen is displayed.

6. Select “I accept the terms of the License Agreement” and then click Next.

The Choose Install Folder screen is displayed.

Important: Do not use a path that has spaces in the directory or folder names.

Note: If you enter a location that has a previously-installed version of Informatica software, the Hub Server installer will ask you if you want to replace your existing installation. For details on the upgrade process, see the Informatica MDM Hub Upgrade Guide.

7. Do one of the following:

• Click Next to install Hub Server in the default location.

• Enter the path to the installation folder. Click Next.

• Click the Choose button to choose another location in which to install the Informatica Hub Server. Click Next.

The Choose Link Folder screen is displayed.

8. Choose a link folder (or select the option to not create links). Click Next.

The Enter Location of License File screen is displayed.

9. Click Choose to select a license file.

Make sure you have a valid license file from Informatica. The Hub Server installer will not install Informatica MDM Hub without a license file. Contact Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii) for a license.



If you entered the license path, click Next to continue.

The Application Server screen is displayed.

10. Select the JBoss application server. Click Next.

Note: You must be sure that you have supported versions of your application server, or the Hub Server installer will display error messages and you will be unable to continue with the installation. For the latest application server compatibility requirements, see the Release Notes.

The JBoss Application Server Home screen is displayed.

11. Configure your JBoss settings.

a. Specify the application server installation directory. Click Next.

The JBoss Application Server Configuration Name screen is displayed.

b. Specify the Configuration Name (default is production). Click Next.

The JBoss Pre-requisites warning is displayed.

c. Click OK.

The JBoss Application Server screen is displayed.

d. Specify your RMI port.

The default port number is in the following file:

<JBoss_install_dir>server/<configuration_name>/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml

Open bindings-jboss-beans.xml and specify your RMI port number.

Note: The JBoss port can conflict with the default Oracle port. If that is the case for your installation, you must change one of the ports to resolve the conflict. To change the port number, open bindings-jboss-beans.xml for editing, search for the word port, and set the port value to match the value you have set on the JBoss Application Server Port screen.

12. Click Next.

The Database Selection screen is displayed.

13. Select Oracle. Click Next.

The Oracle Database Connection Type Selection screen is displayed.



14. Select the connection type you want (Service Name or SID). Click Next.

The Oracle Database Information screen is displayed.

15. Enter the following settings for the Oracle database to which you want to connect: server name, port number, Service Name or Oracle SID (depends on your selected connection type), Informatica MDM Hub system schema name, CMX Username, and CMX password (for the CMX username). Click Next.

Note: The default password for the CMX user is !!cmx!!

16. If the selected Oracle connection type is Service Name, then the Customization of Connect URL screen is displayed. Change the system-generated URL, if you want. Click Next.

The Deploy screen is displayed.

17. Click Yes to run the script during the installation, or click No to manually run it later. For more information about the post-installation process, see “PostInstallSetup” on page 45. Click Next.

The Pre-Installation Summary screen is displayed.

18. If you want to change any options, click the Previous button to navigate to the appropriate screens.

Note: The folder path displayed in the preinstallation summary for the Do not create links option is incorrect, but the software created the correct path on the server.

19. Once the summary reflects the options you want, click Install to start the installation process.

The Please Wait screen displays while the Hub Server installer configures your system.

When the installation completes, the Install Complete screen is displayed.

20. Click Done to exit the Hub Server Installer.



Installation Log Files

The following files are useful for troubleshooting any Hub Server installation process (see “Informatica MDM Hub Log Files” on page 268). Copy these log files to the installation documentation directory that you created in “Create an Installation Documentation Directory” on page 9. In case of installation problems, these files will be useful to provide to Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii).

Location / Log File Description

<infamdm_install_directory>/hub/server/Informatica_MDM_Hub_Server_InstallLog.xml

Contains log messages for the Hub Server installation.

<infamdm_install_directory>/hub/server/logs/installPrereq.log

Contains the prerequisite messages generated during installation.

<infamdm_install_directory>/hub/server/infamdm_installer_debug.txt

Contains debug messages.

<infamdm_install_directory>/hub/server/logs/postInstallSetup.log

Contains the postInstallSetup messages for the script.

<infamdm_install_directory>/hub/server/logs/cmxserver.log

Hub Server log. When the server started, it created this file.

JBoss log files (such as <JBoss_install_dir>/server/<configuration_name>/log/server.log)

Located in the tree under the JBoss install directory.



Configuring the Hub Server

This section describes how to configure the Hub Server after it is installed.

Hub Server EAR File

During run time, the Hub Server application must locate the installation from which it was deployed. Therefore, do not transfer the EAR file for deployment on another machine. For example, if you installed Hub Server on a Marketing machine and then deployed the EAR file on the Sales machine, the application on Sales would not be able to locate the installation for configuration information such as logging.

Configuring the Logging Settings

You can configure the <infamdm_install_directory>/hub/server/conf/log4j.xml for logging. The default value is INFO for log4j.xml. You can turn on DEBUG for mrmserver by replacing INFO with DEBUG in log4j.xml. For JBoss, the jboss-log4j.xml file is located instead in the conf directory under the JBoss default server directory.

Setting the Configuration Properties

You can configure the cmxserver.properties file located in <infamdm_install_directory>/hub/server/resources directory. After you update this file, you must restart the Hub Server application to reload the settings in the file. The values in this file reflect your installation.



Your file looks similar to this:

cmx.home=/infamdm/hub/servercmx.server.masterdatabase.type=oraclecmx.appserver.type=jbosscmx.appserver.rmi.port=1099cmx.appserver.naming.protocol=jnpjnlp.initial-heap-size=128mjnlp.max-heap-size=192mcmx.server.datalayer.cleanse.execution=SERVERcmx.server.datalayer.cleanse.working_files.location=/infamdm/hub/server/logscmx.server.datalayer.cleanse.working_files=LOCAL

Note: If you are using JBoss and need to change ports because of port conflicts, you must ensure that the cmx.appserver.rmi.port value is the same as the JNP port number, not the RMI port number. The value of the JNP port number is in the <JBoss_install_dir>/server/<configuration_

name>/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml file, in the following attribute: <property name="port">1099</property>.

Changing Your JBoss Settings

If you keyed in incorrect JBoss settings during the installation process, you can change those values after installation.

To change your JBoss settings:1. Open the following file for editing:

<infamdm_install_directory>/bin/build.properties

2. Modify your JBoss configuration settings.

3. Save and close build.properties.

4. Run the postInstallSetup.sh script according to the instructions in “Running the Post-Install Process Manually” on page 56.

5. Restart the application server.



Changing Passwords

After you have installed Hub Server, you can change the password for the CMX_SYSTEM and CMX_ORS users. For more information, see “Changing Passwords After Installation” on page 107.

Performing Post-Installation Tasks

This section describes tasks that you might need to perform after running the Hub Server installer.

Running the Post-Install Process Manually

If you chose to have the Hub Server installer skip the post-install process, you must run this script manually. By default, this script is located in the following directory:

/<infamdm_install_directory>/hub/server

To run the post-install process manually, run the following command from a command prompt:

postinstallsetup.sh

Manually Redeploying the Hub Server Application (JBoss/Unix)

If you need to manually redeploy the Hub Server application, see the instructions in “Manually Redeploying the Hub Server (JBoss/Unix)” on page 290.


Installing the Hub Server (WebLogic/Unix)


This section describes how to install the Hub Server running in the WebLogic application server environment on the Unix platform.






















Install and Configure WebLogic

Install and configure WebLogic Server according to your WebLogic documentation. Before you install the Hub Server, use the WebLogic Administration Wizard to create a WebLogic domain for the Hub Server according to your WebLogic documentation.

Note: To use a WebLogic clustered environment, contact Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii).



Configure WebLogic to Use an Oracle Data Source

Contact Oracle to obtain any JDBC drivers you may need for your database configuration. Once you obtain the drivers, configure WebLogic as follows:

To use an Oracle data source with WebLogic:• Copy the new Oracle JDBC driver files to your

<WebLogic_install_dir>/weblogicxx/server/lib directory.

where weblogicxx is the WebLogic directory for your version of WebLogic.






Installation Steps





3. Go to the directory where the Informatica MDM Hub installer resides. In the distribution, the Hub Server installer is in the following directory:







./hub_install.bin



Note: To bypass the prerequisite validation in the installation, see “Bypassing Prerequisite Installation” on page 276.




6. Select the “I accept the terms of the License Agreement” button and then click Next.

















10. Select WebLogic. Click Next.

The WebLogic Application Server Home screen is displayed.


11. Configure your WebLogic settings.

a. Choose a path to the WebLogic domain/directory for Informatica MDM Hub. This is the domain you created in earlier. Click Next.

The Application Server Login screen is displayed.

b. In the WebLogic Application Server Login, enter the following information:

Field Description

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

Server Name of the server 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 your WebLogic Server is listening.



The Hub Server installer collects information for the administrative login and uses it to create the JDBC data source to the Master Database.

If you type in incorrect login information, the verification process in the Hub Server installer will stop until you correct the information.

12. Click Next.



















20. Click Done to exit the Hub Server installer.














WebLogic log files under <weblogic_domain>/servers/<weblogic_server>/logs.: access.log, <weblogic_server>.log and <weblogic_domain>.log

Located in the tree under the WebLogic install directory.





Hub Server EAR File

During run time, the Hub Server application must locate the installation from which it was deployed. Therefore, do not transfer the EAR file for deployment on another machine. For example, if you installed Hub Server on a Marketing machine and then deployed the EAR file on the Sales machine, the application on Sales would not be able to locate the installation for configuration information such as logging.


You can configure the <infamdm_install_directory>/hub/server/conf/log4j.xml for logging. The default value is INFO for log4j.xml. You can turn on DEBUG for mrmserver by replacing INFO with DEBUG in log4j.xml.




cmx.home=/infamdm/hub/servercmx.server.masterdatabase.type=oraclecmx.appserver.type=weblogiccmx.appserver.rmi.port=7001



cmx.appserver.naming.protocol=t3jnlp.initial-heap-size=128mjnlp.max-heap-size=192mcmx.server.datalayer.cleanse.execution=SERVERcmx.server.datalayer.cleanse.working_files.location=/infamdm/hub/server/logscmx.server.datalayer.cleanse.working_files=LOCAL

Changing Your WebLogic Settings

If you keyed in incorrect WebLogic settings during the installation process, you can change those values after installation.

To change your WebLogic settings:1. Open the following file for editing:


2. Modify your WebLogic configuration settings under the #Server settings section.




Changing Passwords










postInstallSetup.sh -Dweblogic.password=<weblogicPassword> -Ddatabase.password=<yourDBPassword>

where <weblogicPassword> is the password for your WebLogic application server. and <yourDBPassword> is your database password.

Note: If you include the “!” character in your password, you must include a “\” before the ! character. For example, if your password is !!cmx!!, enter the password as follows: \!\!cmx\!\!

Manually Redeploying the Hub Server Application

If you need to manually redeploy the Hub Server application, see the instructions in “Manually Redeploying Hub Server (WebLogic/Unix)” on page 299.

Manually Restarting WebLogic

You must restart WebLogic after you install the Hub Server. The installation process automatically enables the AnonymousAdminLookupEnabled method, causing the ORS to fail unless you restart WebLogic.


Installing the Hub Server (WebSphere/Unix)


This section describes how to install the Hub Server running in the WebSphere application server environment on the Unix platform.






















Install and Configure WebSphere

Install and configure WebSphere according to your WebSphere documentation.

Configure WebSphere to Use an Oracle Data Source

Contact Oracle to obtain any JDBC drivers you may need for your database configuration. Once you obtain the drivers, configure WebSphere as follows:

To configure WebSphere to use an Oracle data source:



• Copy the new Oracle JDBC driver files to your <WebSphere_install_dir>/lib directory.






Installation Steps



3. Go to the directory where the Hub Server installer resides. In the distribution, the Hub Server installer is in the following directory:









./hub_install.bin
























10. Choose WebSphere. Click Next.


The WebSphere Application Server Home screen is displayed.

11. Configure your WebSphere settings.

a. Choose a path to the WebSphere application server. Click Next.

The prerequisites warning screen is displayed.

b. Click OK.

The WebSphere Security Selection screen is displayed. Choose whether WebSphere is security enabled from the two options; Yes or No. No is the default.

• If you click No and Next, the WebSphere Application Server Port screen is displayed.Set the server name, and the RMI and SOAP ports for your WebSphere application server. Click Next.

• If you click Yes and Next,the WebSphere Application Server Port and User Credentials screen is displayed.Set the server name, and the RMI and SOAP ports for your WebSphere application server. Fill in the WebSphere Username field and the WebSphere Password. Click Next.





















The following files are useful for troubleshooting any Hub Server installation process (see “Informatica MDM Hub Log Files” on page 268). Copy these log files to the installation documentation directory that you created in “Create an Installation



Documentation Directory” on page 9. In case of installation problems, these files will be useful to provide to Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii).



Hub Server EAR File

During run time, the Hub Server application must locate the installation from which it was deployed. Therefore, do not transfer the EAR file for deployment on another machine. For example, if you installed Hub Server on a Marketing machine and then












WebSphere log files in the following location: <WebSphere_install_dir>/profiles/AppSrv01/logs/<servername>.

Name of log files: startServer.log, stopServer.log, SystemErr.log, and SystemOut.log.

Located in the tree under the WebSphere install directory.



deployed the EAR file on the Sales machine, the application on Sales would not be able to locate the installation for configuration information such as logging.


You can configure the <infamdm_install_directory>/hub/server/conf/log4j.xml for logging. The default value is INFO for log4j.xml. You can turn on DEBUG for mrmserver by replacing INFO with DEBUG in log4j.xml.




cmx.home=/infamdm/hub/servercmx.server.masterdatabase.type=oraclecmx.appserver.type=webspherecmx.appserver.rmi.port=2809cmx.appserver.naming.protocol=iiopjnlp.initial-heap-size=128mjnlp.max-heap-size=192mcmx.server.datalayer.cleanse.execution=SERVERcmx.server.datalayer.cleanse.working_files.location=/infamdm/hub/server/logscmx.server.datalayer.cleanse.working_files=LOCAL

Changing Your WebSphere Settings

If you keyed in incorrect WebSphere settings during the installation process, you can change those values after installation.

To change your WebSphere settings:1. Open the following file for editing:




2. Modify your WebSphere configuration settings.




Changing Passwords








postinstallsetup.sh -Ddatabase.password=<yourDBPassword>





If you need to manually redeploy the Hub Server application, see the instructions in “Manually Redeploying the Hub Server Application (WebSphere/Unix)” on page 304.


Installing the Hub Server (JBoss/Windows)


This section describes how to install the Hub Server running in the JBoss application server environment on the Windows platform.

Note: JBoss 5 should use JDK 1.6.0.14 or higher..



















Verify that you have sufficient physical memory available to satisfy the runtime needs of all the Informatica software you intend to install. Use the following formula to determine your physical memory requirements:

Total Informatica runtime memory footprint = JDK JVM max heap size of the application server + Window’s native heap size

By default, Windows has a 2GB limit to the amount of memory it will allow to be used by a single process. This 2GB limit is the limit within which the total Informatica MDM Hub runtime memory footprint must fit.

Make sure that there is enough physical RAM available to satisfy the runtime needs of all the Informatica software you intend to install. With all your non-Informatica



applications turned on, use the following formula to determine if your physical RAM is adequate:

min physical RAM available >= Window’s native process memory limit >=(application server JVM maximum heap size + <cleanse_engine> memory size)

For more information about RAM and physical memory, consult your Windows documentation.




Install and configure JBoss according to the instructions in the JBoss documentation.

Configure JBoss to Use an Oracle Data Source

Contact Oracle to obtain any JDBC drivers you may need for your database configuration. Once you obtain the drivers, configure JBoss as follows:

To configure JBoss to use an Oracle data source:• Copy the new Oracle JDBC driver files to your

<JBoss_install_dir>\server\<configuration_name>\lib directory.





Disable JMX Invoker Authentication (Windows)

If JMX Invoker Authentication is enabled for your JBoss server, you must disable it in order to successfully create a datasource during ORS registration in the Hub Console. To disable JMX Invoker Authentication:1. Edit the following file:

<jboss_home>\server\<configuration_name>\deploy\jmx-invoker-service.xml

2. Remove or comment out the following lines:





jboss-5.1.0.GA\bin


run.bat -b 0.0.0.0





Cleanse Match Server.


Installation Steps

To install Hub Server:1. Make sure that the application server has started and running correctly.

2. Run the Hub Server installer (hub_install.exe), which is located on the distribution in the \mrmserver\windows directory.

The Hub Server installer displays the Introduction screen.






Note: If you enter a location that has a previously installed version of Informatica software, the install will ask you if you want to patch your existing installation. For details on the upgrade process, see the Informatica MDM Hub Upgrade Guide.




• Click Next to install Informatica MDM Hub in C:\infamdm\hub\server.


• Click the Choose button to choose another location to install Informatica MDM Hub and then click Next.

The Choose Shortcut Folder screen is displayed.

6. Select a shortcut folder, then click Next to continue.


7. Click Choose to select a license file. Informatica provides you with a license file. If you do not have the license file, you cannot continue with the install. Contact Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii) to obtain the license file.

Click Next to continue.


8. Choose JBoss and then click Next.







c. Click OK.

The JBoss Application Server Port screen is displayed.



<JBoss_install_dir>\server\<configuration_name>\conf\bindingservice.beans\META-INF\bindings-jboss-beans.xml.

Open bindings-jboss-beans.xml and specify your RMI port number.



Note: The JBoss port can conflict with the default Oracle port. If that is the case for your installation, you must change one of the ports to resolve the conflict. To change the port number, open bindings-jboss-beans.xml for editing, search for the word “port”, and set the port value to match the value you have set on the JBoss Application Server Port screen.

10. Click Next.






13. Enter the following settings for the Oracle database to which you want to connect: server name, port number, Service Name or Oracle SID (depends on your selected connection type), Informatica MDM Hub system schema name, CMX Username, and CMX password (for the CMX username).


14. Click Next.


The PostInstallSetup script (Deploy) screen is displayed.

16. Click Yes to run the script during the installation, or click No to manually run it later. For more information about the post-installation process, see “Running the Post-Install Process Manually” on page 87. Click Next.


17. If you want to change any options, click the Previous button to navigate to the appropriate screens. Once the summary reflects the options you want, click Install to start the installation process.








<infamdm_install_directory>\hub\server\Informatica_MDM_Hub_Server_InstallLog.xml


<infamdm_install_directory>\hub\server\logs\installPrereq.log


<infamdm_install_directory>\hub\server\infamdm_installer_debug.txt


<infamdm_install_directory>\hub\server\logs\postInstallSetup.log


<infamdm_install_directory>\hub\server\logs\cmxserver.log


JBoss log files

Example: <JBoss_install_dir>\server\<configuration_name>\log\server.log






Hub Server EAR File

During runtime, the Hub Server application must locate the installation it was deployed from. Therefore, it is not recommended to carry the EAR file to deploy onto another machine. For example, if you installed Hub Server on a Marketing machine and then deployed the EAR on the Sales machine, the application would not be able to locate the installation for configuration information such as logging.


You can configure the log4j.xml for logging. The default value is INFO. You can turn on DEBUG for mrmserver by replacing INFO with DEBUG in log4j.xml. After you update this file, you must restart the Hub Server application. For JBoss, the log4j.xml file is located instead in the conf directory under the JBoss default server directory (such as <JBoss_install_dir>\server\<configuration_name>\conf\jboss-log4j.xml).


You can configure the cmxserver.properties file located in <infamdm_install_directory>\hub\server\resources directory. After you update this file, you must restart the Hub Server application to reload the settings in the file. The values in this file reflect your installation.

Your file should look similar to the following example:

cmx.home=C:\infamdm\hub\servercmx.server.masterdatabase.type=oracle



cmx.application.server.type=jbosscmx.appserver.web.port=8080cmx.appserver.rmi.port=1099cmx.appserver.naming.protocol=jnpcmx.appserver.soap.connector.port=jnlp.initial-heap-size=128mjnlp.max-heap-size=192mcmx.server.datalayer.cleanse.execution=SERVERcmx.server.datalayer.cleanse.working_files.location=C:\infamdm\hub\server\logscmx.server.datalayer.cleanse.working_files=LOCAL

Note: If you are using JBoss and need to change ports because of port conflicts, you must ensure that the cmx.appserver.rmi.port value is the same as the JNP port number, not the RMI port number. The value of the JNP port number is in the <JBoss_install_dir>\server\<configuration_

name>\conf\bindingservice.beans\META-INF\bindings-jboss-beans.xml file, in the following attribute: <property name="port">1099</property>.

Changing Your JBoss Settings

If you keyed in the incorrect JBoss settings during the installation process, complete the following:1. Open the following file for editing:

<infamdm_install_directory>\server\bin\build.properties

2. Modify your JBoss configuration settings.

3. Save and close build.properties file.

4. Run the postInstallSetup script according to the instructions in “Running the Post-Install Process Manually” on page 87.


Changing Passwords







If you chose to have the Informatica MDM Hub installation program skip the post-install process, you must run this script manually.

By default, this script is located in the following directory:

<infamdm_install_directory>\hub\server

For example, the default is C:\infamdm\hub\server.

To run the post-install script manually, run the following command from a command prompt:

postInstallSetup.bat


If you need to manually redeploy the Hub Server application, see the instructions in “Manually Redeploying Hub Server (JBoss/Windows)” on page 307.


Installing the Hub Server (WebLogic/Windows)


This section describes how to install the Hub Server running in the WebLogic application server environment on the Windows platform.






















Make sure that there is enough physical RAM available to satisfy the runtime needs of all the Informatica software you intend to install. With all your non-Informatica applications turned on, use the following formula to determine if your physical RAM is adequate:








Install and configure WebLogic according to your WebLogic documentation.

Configure a WebLogic Domain

Before you install the Hub Server, use the WebLogic Administration Wizard to create a WebLogic domain for the Hub Server according to your WebLogic documentation.

Note: To use a WebLogic clustered environment, contact Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii).

Configure WebLogic to Use an Oracle Data Source

Contact Oracle to obtain any JDBC drivers you may need for your database configuration. Once you obtain the drivers, configure WebLogic as follows:

To configure WebLogic to use an Oracle data source:• Copy the new Oracle JDBC driver files to your

<WebLogic_install_dir>\weblogicxx\server\lib directory.

where weblogicxx is the WebLogic directory for your version of WebLogic.








Installation Steps

To install Hub Server:1. Make sure that your application server is started and running correctly.





















8. Choose WebLogic and then click Next.


9. Configure your WebLogic settings.

a. Choose a path to the WebLogic domain installation directory for the domain you want to use for Informatica MDM Hub. This is the domain you created in “Configure a WebLogic Domain” on page 90. Click Next.

The WebLogic Application Server Login screen is displayed.

b. Enter the following information:

The Hub Server installer collects information for the administrative login and uses it to create the JDBC data source to the Master Database.

If you type in incorrect login information, the verification process in the Hub Server installer will stop until you correct the information.

10. Click Next.



Field Description













14. Click Next.























WebLogic log files. For example:

<weblogic_domain>\servers\AdminServer\logs\AdminServer.log

<weblogic_domain>\servers\AdminServer\logs\<domain_name>.log






Hub Server EAR File



You can configure the <infamdm_install_directory>\hub\server\conf\log4j.xml for logging. The default value is INFO for log4j.xml. You can turn on DEBUG for mrmserver by replacing INFO with DEBUG in log4j.xml. After you update this file, you must restart the Hub Server application.


You can configure the cmxserver.properties file located in <infamdm_install_directory>\hub\server\resources directory. After you update this file, you must restart the Hub Server application to reload the settings in the file. The values in this file reflect your installation.

Your file should look similar to the following example:

cmx.home=C:\infamdm\hub\servercmx.server.masterdatabase.type=oraclecmx.application.server.type=weblogiccmx.appserver.rmi.port=7001



cmx.appserver.naming.protocol=t3cmx.appserver.soap.connector.port=jnlp.initial-heap-size=128mjnlp.max-heap-size=192mcmx.server.datalayer.cleanse.execution=SERVERcmx.server.datalayer.cleanse.working_files.location=C:\infamdm\hub\server\logscmx.server.datalayer.cleanse.working_files=LOCAL

Changing Your WebLogic Settings

If you keyed in the incorrect WebLogic settings during the installation process, complete the following:1. Open the following file for editing:


2. Modify your WebLogic configuration settings under the #Server settings section of build.properties.


4. Run the postInstallSetup.bat script according to the instructions in “Running the Post-Install Process Manually” on page 97.


Changing Passwords












postInstallSetup.bat -Dweblogic.password=<weblogicPassword> -Ddatabase.password=<yourDBPassword>



If you need to manually redeploy the Hub Server application, see the instructions in “Manually Redeploying Hub Server (WebLogic/Windows)” on page 315.


Installing the Hub Server (WebSphere/Windows)


This section describes how to install the Hub Server running in the WebSphere application server environment on the Windows platform.
















Obtain the Informatica License File






Make sure that there is enough physical RAM available to satisfy the runtime needs of all the Informatica software you intend to install. With all your non-Informatica applications turned on, use the following formula to determine if your physical RAM is adequate:








Install and configure WebSphere according to your WebSphere documentation.

Configuring WebSphere to Use an Oracle Data Source

Contact Oracle to obtain any JDBC drivers you may need for your database configuration. Once you obtain the drivers, configure WebSphers as follows:

To configure WebSphere to use an Oracle data source:• Copy the new Oracle JDBC driver files to your

<WebSphere_install_dir>\lib directory.








Installation Steps

To install Hub Server:1. Make sure that your application server is started and running correctly.





















8. Choose WebSphere. Click Next.


9. Configure your WebSphere settings.

a. Choose a path to the WebSphere application server. Click Next.

The reminder screen is displayed.

b. Make sure you have fulfilled the prerequisites and Click OK.

c. The WebSphere Security Selection screen is displayed. Choose whether WebSphere is security enabled from the two options; Yes or No. No is the default.

• If you click No and Next, the WebSphere Application Server Port screen is displayed.Set the server name, and the RMI and SOAP ports for your WebSphere application server. Click Next.

• If you click Yes and Next,the WebSphere Application Server Port and User Credentials screen is displayed.Set the server name, and the RMI and SOAP ports for your WebSphere application server. Fill in the WebSphere Username field and the WebSphere Password. Click Next.

10. The Database Selection screen is displayed.

Select Oracle. Click Next.






13. Click Next.





Hub Server EAR File



You can configure the <infamdm_install_directory>\hub\server\conf\log4j.xml for logging. The default value is INFO for log4j.xml. You can turn on DEBUG for mrmserver by replacing INFO with DEBUG in log4j.xml. After you update this file, you must restart the Hub Server application.


You can configure the cmxserver.properties file located in <infamdm_install_directory>\hub\server\resources directory. After you update this file, you must



WebSphere log files. For example: <WebSphere_install_dir>\profiles\AppSrv01\logs\<ServerName> folder





restart the Hub Server application to reload the settings in the file. The values in this file reflect your installation.


cmx.home=C:\infamdm\hub\servercmx.server.masterdatabase.type=oraclecmx.application.server.type=webspherecmx.appserver.rmi.port=2809cmx.appserver.naming.protocol=iiopcmx.appserver.soap.connector.port=8880jnlp.initial-heap-size=128mjnlp.max-heap-size=192mcmx.server.datalayer.cleanse.execution=SERVERcmx.server.datalayer.cleanse.working_files.location=C:\infamdm\hub\server\logscmx.server.datalayer.cleanse.working_files=LOCAL

Changing Your WebSphere Settings

If you keyed in the incorrect WebSphere settings during the installation process, complete the following:1. Open the following file for editing:


2. Modify your WebSphere configuration settings.


4. Run the postInstallSetup script according to the instructions in “Running the Post-Install Process Manually” on page 106.


Changing Passwords












postInstallSetup.bat -Ddatabase.password=!!cmx!!


If you need to manually redeploy the Hub Server application, see the instructions in “Manually Redeploying Hub Server (WebSphere/Windows)” on page 319.


Changing Passwords After Installation


After you have installed Hub Server, you can change passwords for CMX_SYSTEM and CMX_ORS users.

Changing the Password for the CMX_SYSTEM User

After you have installed Hub Server, you can change the password for the CMX_SYSTEM user. If you do so, you must also:• Change the password for the CMX user in Oracle.

• Set the same password in the data source in the application server.

For more information about changing passwords in Informatica MDM Hub, see the Informatica MDM Hub Administrator Guide.

Changing the Password for the CMX_ORS User

After you have installed Hub Server, you can change the username and password for the CMX_ORS user. If you do so, you must also:• Change the password for the CMX_ORS user in Oracle.

• Set the same password in the data source in the application server.

• Register the schema with the same username and password as you configured in the database and the application server. All these usernames and passwords must be the same.


4
Installing the Cleanse Match Server
This chapter explains how to install and configure the Cleanse Match Server in your Informatica MDM Hub implementation. Instructions are organized alphabetically by application server and platform.

Note: If you have a previously installed version of the Cleanse Match Server, see the Informatica MDM Hub Upgrade Guide for upgrade instructions. This chapter covers new installations.

Chapter Contents

• About the Cleanse Match Server

• Installing the Cleanse Match Server (JBoss/Unix)

• Installing the Cleanse Match Server (WebLogic/Unix)

• Installing the Cleanse Match Server (WebSphere/Unix)

• Installing the Cleanse Match Server (JBoss/Windows)

• Installing the Cleanse Match Server (WebLogic/Windows)

• Installing the Cleanse Match Server (WebSphere/Windows)

109

About the Cleanse Match Server


The Cleanse Match Server run-time component handles cleanse and match requests and is deployed in the application server environment. The Cleanse Match Server contains:• a cleanse server that handles data cleansing operations

• a match server that handles match operations

The Cleanse Match Server interfaces with any of the supported cleanse engines, as described in Informatica MDM Hub Cleanse Adapter Guide. The Cleanse Match Server and the cleanse engine work together to standardize the data and to optimize the data for match and consolidation.

Supported Cleanse Match Engines

Informatica assumes that you are familiar with your cleanse engine and have already installed and configured it prior to installing Informatica MDM Hub. See the Informatica MDM Hub Release Notes for the cleanse engines and their versions that are supported by Informatica MDM Hub.

PostInstallSetup

The Cleanse Match Server installer, by default, runs the post-installation process (postInstallSetup script) to deploy the application on your application server and perform some application server configuration. However, while running the install, you can choose to not run this post-installation process, in which case the Cleanse Match Server installer only copies the files to the installation directory. Once copied, you must manually deploy the Cleanse Match Server application on the application server and perform application server configuration.



Separating the installation and deployment functions allows you to:• Avoid deploying the application as part of the installation process. You can

manually run the script later when you are sure the application starts up successfully.

• Deploy the application using the application server’s administrator console.

• Run the script to redeploy the application instead of reinstalling the entire Cleanse Match Server.

• Troubleshoot deployment problems outside of the installation process.



Installing the Cleanse Match Server 111

Installing the Cleanse Match Server (JBoss/Unix)


This section describes how to install the Cleanse Match Server running in the JBoss application server environment on the Unix platform.


Cleanse Match Server installation involves the following steps:


Complete the tasks in this section before you install the Cleanse Match Server.




2 Install the Cleanse Match Server by running the installer.

“Running the Cleanse Match Server Installer” on page 117

3 Specify or change Cleanse Match Server configuration settings.

“Configuring the Cleanse Match Server” on page 121




Before you install the Cleanse Match Server, fulfill the hardware and software requirements for the Cleanse Match Server as described in the Informatica MDM Hub Release Notes.


On the machine where you will run the Cleanse Match Server, install and configure your JBoss environment according to your JBoss documentation.


Contact Oracle to obtain any JDBC drivers you may need for your database configuration. Once you obtain the files, configure JBoss as follows:

To configure JBoss to use an Oracle data source:1. Copy the new Oracle JDBC driver files to your

<JBoss_install_dir>/server/<configuration_name>/lib directory.




Install and Configure Your Cleanse Engine

Install and configure your cleanse engine. Obtain any required unlock codes for that software. Make sure that you have the latest patches installed. Verify that your cleanse server operates properly. For instructions on how to configure Informatica MDM Hub to integrate with your cleanse engine, see the Informatica MDM Hub Cleanse Adapter Guide.




Have an Informatica license file. The Cleanse Match Server installer will not install Cleanse Match Server without a valid license file. Contact Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii) to obtain a license file.

Your Informatica license has the information you need to install the Cleanse Server with the Cleanse Match Server you are using. During the Cleanse Server installation, the Cleanse Match Server installer asks you for information on the Cleanse Match Server, checks the license file for corresponding Cleanse Match Server information, then stores that information in the cmxcleanse.properties file.

If you have installed a Cleanse Match Server that does not have corresponding information in the Informatica license file, the Cleanse Match Server installer does not store any information in the properties file. Therefore, the properties file displays either blank or default values for that Cleanse Match Server.

To make sure that the cmxcleanse.properties file is updated you must obtain the correct Informatica license file and reinstall the Cleanse Match Server.

Configure JBoss for the Cleanse Match Server

This section describes how to configure JBoss before installing the Cleanse Match Server.

Removing Obsolete Oracle Drivers

Before you install the Cleanse Match Server, delete any instances of old Oracle drivers from your JBoss directory structure. The most likely place to find them is in the <JBoss_install_dir>/server/<configuration_name>/lib directory. The files are: • ocrs12.jar

• orai18n.jar

• nls_charset12.jar



Creating Data Sources for Each ORS

If you install the Cleanse Match Server on a different machine from the one running the Hub Server, on the Cleanse Match Server machine you must create data sources for each ORS. You must also do some Oracle configuration, as well as some JBoss configuration. See “Configuring JBoss to Use an Oracle Data Source” on page 115 for more information on the Oracle configuration.

Configuring JBoss to Use an Oracle Data Source

Note: If you are running Oracle on the same host that is running Cleanse Match Server, you can skip this section.

To configure JBoss to use an Oracle data source:1. Copy a sample datasource file (name-ds.xml) into your JBoss deploy directory.

By default the JBoss deploy directory is:<JBoss_install_dir>/server/<configuration_name>/deploy

You can find the samples in:

<JBoss_install_dir>/docs/examples/jca

You can change the name of the sample datasource file, but the file must end with -ds.xml to be recognized as a datasource descriptor.

2. Edit the datasource definition to match your database connection parameters. Edit the following parameters:

Parameter Description

jndi-name Set jndi-name to the following value for a Hub Server datasource:

jdbc/siperian-cmx_system-ds

Set jndi-name to the following value for the cleanse server datasource:

jdbc/siperian-<oracle_hostname>-<oracle_sid>-<ors_schema_name>-ds

where oracle_hostname is the name of your host, oracle_sid is the name of your Oracle instance and ors_schema_name is the name of your ORS.



Configuring JBoss for Both Cleanse Match Server and Hub Server

For JBoss, if you must run both Hub Server and Cleanse Match Server on the same JBoss server, you must manually configure JBoss before starting the server.

To configure JBoss before installing Hub Server and Cleanse Match Server:1. When there is the potential for conflict between the JBoss port and the Oracle

port, change the port used by one of the applications. To change the port for the JBoss application server, edit the following file:

<JBoss_install_dir>/server/<configuration_name>/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml

The default connector port is 8080. Change this to any unused port that does not conflict with other applications.



jboss-5.1.0.GA/bin


run.sh -b 0.0.0.0

connection-url The JDBC driver connection URL string for your driver. Make sure that the database name, host, and port are correct for the database to which you are connecting. For example:

jdbc:oracle:thin:@server_name:1521:orcl

username Default username used when creating a new connection. The default user in Oracle for the Hub Server is cmx, and for the Cleanse Match Server is cmx_ors.

password The default password used when creating a new connection.




Running the Cleanse Match Server Installer

The Cleanse Match Server Installer is the program used to install the Cleanse Match Server software. It is included in your Informatica MDM Hub distribution.

Installation Considerations• Important: If you are installing the Hub Server, the application server, the Cleanse

Server, and the cleanse engine on the same machine, the user names you use to install them must belong to the same Unix group.

• Important: You can install Hub Server and Cleanse Match Server using any username you want, but you must use the same user name to install both servers.


• Do not use the root user when installing the Cleanse Match Server on RedHat Linux. Instead, create and use a separate user profile for installing Informatica MDM Hub. This is a limitation of InstallAnywhere, as the root user does not have a .profile.

• The Cleanse Match Server installer can also be used to upgrade existing installations. If you have a previously installed version of Informatica software, see the Informatica MDM Hub Upgrade Guide to learn more. This section covers new installations.

Installation Steps

To install Cleanse Match Server:1. Make sure that your application server is started and running correctly.

2. If you are installing from a remote client, start an X Windows session and set the DISPLAY value to the remote client.



3. Run the Informatica Cleanse Match Installer. The Cleanse Match Server installer is on the distribution in the following directory:

Solaris:

/solaris/mrmcleanse/

HP-UX:

/hpux/mrmcleanse/

Linux:

/linux/mrmcleanse/

AIX:

/aix/mrmcleanse/

4. Execute the following command to begin the installation process.

./hub_cleanse_install.bin

The Cleanse Match Server Installer displays the Introduction screen.


5. Click Next.


6. Accept the terms of the license agreement and click Next.


7. Click the Choose button to choose another location to install Cleanse Match Server, or click Next to accept the default.

Important: Do not use a path that has spaces in the directory or folder name.


8. Click Choose to select a license file. You cannot continue with the installation if you do not have a license file. Contact Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii) to obtain a license file. Click Next to continue.


9. Choose the JBoss application server and click Next.




10. Configure JBoss settings:





c. Specify your RMI port.


<JBoss_install_dir>/server/<configuration_name> /conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml

Note: The JBoss port can conflict with the default Oracle port. If that is the case for your installation, you must change one of the ports to resolve the conflict. To change the port number, open bindings-jboss-beans.xml for editing, search for the word port, and set the port value to match the value you have set on the JBoss Application Server Port screen.

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

Note: After installation, you will need to perform additional configuration for your cleanse engine according to the instructions in the Informatica MDM Hub Cleanse Adapter Guide.

• If you are using AddressDoctor, you must configure AddressDoctor using the Cleanse Match Server installer.

• Specify the Unlock Code, Optimization, Memory, and Correction Type parameters. For backslashes (\) in any of these parameters, use a double backslash (\\) instead. Click Next.

The Configure AddressDoctor Preload screen is displayed.

• Specify the AddressDoctor preload parameters. Click Next.

The Choose AddressDoctor Database Path screen is displayed.

• Choose the AddressDoctor database path. Click Next.

• If you are using Business Objects DQ XI, you must configure Business Objects DQ XI using the Cleanse Match Server installer. Specify the Host,



Port, and Sub File parameters for your Business Objects DQ XI cleanse engine. Click Next.

12. Choose to run the script during the installation, or later (see “Running PostInstallSetup” on page 127). Click Next.

The Pre-Installation Summary screen is displayed. If you want to change any options, click the Previous button to navigate to the appropriate screens. Once the summary screen reflects the options you want, click Install to start the installation process.

The Please Wait screen is displayed while Informatica configures your system.

When the installation process completes, the Install Complete screen is displayed.

13. Click Done to exit the Cleanse Match Server installer.


The following log files are useful for troubleshooting any Cleanse Match Server installation process. Copy these log files to the installation documentation directory that you created in “Create an Installation Documentation Directory” on page 9. In case of installation problems, these files will be useful to provide to Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii).

File Description

<infamdm_install_directory>/hub/cleanse/Informatica_MDM_Hub_Cleanse_Match_Server_InstallLog.xml

Shows the Cleanse Match Server install errors and status.

<infamdm_install_directory>/hub/cleanse/logs/postInstallSetup.log

Shows the postInstallSetup script results.

<infamdm_install_directory>/hub/cleanse/logs/cmxserver.log

Cleanse server logs.

<infamdm_install_directory>/hub/cleanse/infamdm_installer_debug.txt

Shows what was chosen during the installation.

<infamdm_install_directory>/hub/cleanse/logs/installPrereq.log



Located in the tree under the install directory for your application server.



Configuring the Cleanse Match Server

This section describes how to configure the Cleanse Match Server after it is installed.

Configuration Considerations• Important: During runtime, Cleanse Match Server must locate the installation

from which it was deployed. Therefore, do not move the EAR file to deploy onto another machine. For example, if you installed Cleanse Match Server on a Marketing machine and then deployed the EAR on the Sales machine, the application would not be able to locate the installation for configuration information (such as logging).

• Note: The cmxcleanse.properties file must be repackaged when a change is made to cmx.home. Any other parameter simply requires a restart of the Cleanse Match Server application.

Configuring Cleanse Match Server with Various Cleanse Engines

To find out how to configure the various cleanse engines, see the Informatica MDM Hub Cleanse Adapter Guide.

Checking the Version and Build Number

Check one of the following files to find out the Cleanse Match Server version and build number:• manifest.mf JAR entry inside the <infamdm_install_directory>

/hub/cleanse/siperian-mrm-cleanse.ear file

• Another place to check is: <infamdm_install_directory>/hub/cleanse/bin/versionInfo.sh file



Deleting Temporary Files

By default, the temporary files generated by the cleanse service are left on disk. You can configure the cleanse server to clean these up by setting a flag in the cleanse server properties file (cmxcleanse.properties) which, by default, is stored in the following directory:

<infamdm_install_directory>/hub/cleanse/resources/

The entry appears as follows:

cmx.server.datalayer.cleanse.working_files=KEEP

You can change the value to FALSE to delete these files after the cleanse/strip and tokenization processes are completed.

cmx.server.datalayer.cleanse.working_files=FALSE

Configuring Logging Settings

You can configure the cleanse application for logging. The settings are listed in the log4j.xml file, located in the <infamdm_install_directory>/hub/cleanse/conf/directory.

The default value is INFO for log4j.xml. You can turn on DEBUG for Cleanse Match Server by replacing INFO with DEBUG in log4j.xml. For JBoss, the jboss-log4j.xml file is located in the <JBoss_install_dir>/server/<configuration_name>/conf directory.

Setting Configuration Properties

You can further configure your Cleanse Match Server installation by customizing the values in the cmxcleanse.properties file located in the resources directory (such as: <infamdm_install_directory>/hub/cleanse/resources/

After you update cmxcleanse.properties, you must restart the Cleanse Match Server application to reload the settings in the file. Your file reflects your installation, but it looks similar to the following example:

cmx.server.logging.location=/u1/infamdm/hub/cleanse/logs



cmx.server.datalayer.cleanse.working_files.location=/u1/infamdm/hub/cleanse/tmpcmx.server.datalayer.cleanse.working_files=KEEPcmx.server.datalayer.cleanse.execution=LOCAL

cmx.home=/u1/infamdm/hub/cleansecmx.appserver.type=jboss

Adding the Oracle TNS Name to ORS Database

The Cleanse Match Server processes cleanse jobs either online or in batches. In the case of an online operation, the application sends back result as an XML response via HTTP protocol. In the case of a batch job, the batch commands that Cleanse Match Server launches use Oracle SQL loader to write the data back.

When the loader is invoked, it uses the parameters in tnsnames.ora to connect to the Oracle database. The Cleanse Match Server installer does not add the TNS name into Oracle installation. Therefore, on the Cleanse Match Server server machine, you must add the TNS entry to the tnsnames.ora file.

The following is an example of an entry for Oracle 10g clients:

<TNS NAME> =(DESCRIPTION =(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = <ORACLE_SERVER_HOSTNAME>)(PORT =<ORACLE_SERVER_PORT>)))(CONNECT_DATA = (SID = <ORACLE_SID>)))

The following is an example of an entry for Oracle 11 clients (note the SERVICE_NAME):

<TNS NAME> =(DESCRIPTION =(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = <ORACLE_SERVER_HOSTNAME>)(PORT =<ORACLE_SERVER_PORT>)))(CONNECT_DATA = (SERVICE_NAME = <ORACLE_SID>)))



You enter this TNS name when you register the ORS database through Hub Console. For more information about using the Hub Console, see the Informatica MDM Hub Administrator Guide.

Note: The TNSnames on the Hub Server machine and the Cleanse Match Server machine must be the same.

Configuring Multiple Cleanse Match Servers

You can configure multiple Cleanse Match Server servers in order to parallelize the data cleansing work. Depending on your needs, choose one of the following alternatives:• Dual servers installed and configured on a single machine. This allows you to take

advantage of the processing power of a single machine. For more information, see “Configuring Dual Cleanse Servers” on page 124.

• Multiple servers on multiple machines. This allows you to balance the load across multiple machines across a network. Informatica MDM Hub uses round-robin load balancing to spread cleansing tasks between all the cleanse servers that are online. For more information, see “Configuring Multiple Cleanse Match Servers on Multiple Machines” on page 126.

Configuring Dual Cleanse Servers

You can configure multiple instances of Cleanse Match Server to run on a single machine. The effectiveness of this approach depends on the hardware you are using as well as your particular data cleansing requirements.

Multiple instances of Cleanse Match Server must run on separate application server instances. That is, they must be in separate physical processes.

The process of configuring dual cleanse servers is primarily an exercise in application server configuration.



Note: This procedure requires that you be expert in the administration and troubleshooting of your application server implementation.

These are the steps to configuring dual cleanse servers:1. Install and configure the first instance of Cleanse Match Server as explained in

“Running the Cleanse Match Server Installer” on page 117 and “Configuring the Cleanse Match Server” on page 121.

2. Configure your system to run multiple instances of your application server. For more information, see “Configuring Multiple Instances of your Application Server” on page 125.

3. Deploy Cleanse Match Server to the second instance of your application server. For more information, see “Deploying Cleanse Match Server on a Second Application Server Instance” on page 126.

Configuring Multiple Instances of your Application Server

To configure your application server:1. Ensure that the machine you are configuring has sufficient memory to host

multiple instances of the application server.

2. Configure each Cleanse Match Server instance in a separate application server instance:

Copy the JBoss files to a new directory. Change the port settings to allow multiple instances to coexist without conflicting ports. For more information, see your JBoss documentation.

3. Test the second instance you just created.

Now you can deploy Cleanse Match Server. For more information, see “Deploying Cleanse Match Server on a Second Application Server Instance” on page 126.



Deploying Cleanse Match Server on a Second Application Server Instance

There are two alternatives for deploying Cleanse Match Server on the second instance of your application server:• You can install an additional copy of Cleanse Match Server into a different

directory using the Cleanse Match Server installer.

Installing an additional copy using the Cleanse Match Server installer gives you full independence of the two Cleanse Match Server instances. There are no extra steps required to support this configuration. You can run the postInstallSetup script to deploy Cleanse Match Server to your second instance.

• You can deploy your existing Cleanse Match Server EAR into the new application server instance.

The second approach is lighter and allows multiple instances to share the Informatica MDM Hub configuration settings. The disadvantage is that both servers share the temporary directories and write to the same log file. This complicates diagnostics when both instances run Cleanse Match Server at the same time.

Using this approach, you cannot use the postInstallSetup script to deploy the additional cleanse instance, you must deploy it manually on the application server.

Deploying the EAR File Manually

To deploy the EAR file manually copy the ear file in the following location:

<JBoss_install_dir>/server/<configuration_name>/deploy

Configuring Multiple Cleanse Match Servers on Multiple Machines

Informatica MDM Hub supports running multiple Cleanse Match Server servers per ORS database. This allows you to parallelize the work of cleansing the data.



When Cleanse Match Server is not installed on the same application server as Hub Server, then you must manually configure the application server to create the data sources for Cleanse Match Server to take advantage of connection pooling and improved performance. For more information, see your application server documentation.

Note: If the data source does not exist, Cleanse Match Server uses the JDBC connection.

To configure multiple Cleanse Match Servers:1. After you have installed and configured Hub Server and Cleanse Match Server,

install your cleanse match engine and Cleanse Match Server on another machine.

2. Create the data sources for each of your Cleanse Match Server servers. This must have exactly the same name and JNDI name as the Hub Server configuration. For instructions, see the Informatica MDM Hub Administrator Guide.

3. Using Hub Console, connect to the data store.

4. Choose the Cleanse Match Server workbench.

5. Add the new Cleanse Match Server.

You can see all the cleanse servers in the Cleanse Match Server workbench.

Performing Post-installation Tasks

This section describes tasks that you might need to perform after running the Cleanse Match Server installer.

Running PostInstallSetup

In the process of installing the Cleanse Match Server, you can choose whether to run the postInstallSetup script automatically to deploy Cleanse Match Server. If you choose not to run this script automatically as part of the installation process, you must run it yourself. For more information, see “PostInstallSetup” on page 110.



The postInstallSetup script is stored in <infamdm_install_directory>/hub/cleanse/. To run the script manually, enter the following at the command prompt:

./postInstallSetup.sh

You can also use this script if you need to redeploy the application to the application server. Alternatively, you can also use the application server’s tool to do the deployment yourself, as long as the Cleanse Match Server EAR file is deployed from the Informatica Cleanse Match Server installation directory. Basic guidelines for redeployment are listed below. For more information, see your application server documentation.

To run the postInstallSetup process manually on the JBoss application server:1. Stop the server.

2. Delete the siperian-mrm-cleanse.ear file from: <JBoss_install_dir>/server/<configuration_name>/deploy directory.

3. Copy the siperian-mrm-cleanse.ear file from the Cleanse Match Server installation directory to the deploy directory.

4. Start the server.


Installing the Cleanse Match Server (WebLogic/Unix)


This section describes how to install the Cleanse Match Server running in the WebLogic application server environment on the Unix platform.

















On the machine where you will run the Cleanse Match Server, install and configure your WebLogic environment according to your WebLogic documentation.










Configure WebLogic for Cleanse Match Server

You must configure WebLogic to work with the Cleanse Match Server.

Creating a WebLogic Domain

Before installing the Cleanse Match Server on the WebLogic application server, you must create a WebLogic domain for the Cleanse Match Server application using the WebLogic Administration Wizard. For more information, see your WebLogic documentation.


If you install the Cleanse Match Server on a different machine from the one running Hub Server, you must create data sources for each ORS. You must do this on the application server on the Cleanse Match Server machine. You must configure the location of the JDBC driver as well as create a datasource for each ORS.

Setting the Location of the JDBC Driver

Contact Oracle to obtain any JDBC drivers you may need for your database configuration. Once you obtain the drivers, configure WebLogic as follows.

To set the location of the JDBC driver, add the Oracle JDBC Driver JAR file to the following directory:

<WebLogic_install_dir>/weblogicxx/server/lib

where weblogicxx is the directory for your version of WebLogic. See the Informatica MDM Hub Release Notes for the supported versions of these drivers.



Configuring WebLogic to Use an Oracle Datasource

Note: If you are running Oracle on the same host that is running Cleanse Match Server, you can skip this section. This section is required only when the Cleanse Match Server runs on another machine or another appserver (not the same application server as the one running the Hub Server).

To configure WebLogic to use an Oracle data source:1. Launch the WebLogic Administrator Console.

2. Create a data source called “MRM Data Source”.

a. Acquire a lock by clicking the Lock & Edit button.

Under Services > JDBC > Data Sources, configure a new master data source. Click New.

Set the name to “MRM Data Source”.

Set the JNDI name to “jdbc/siperian-cmx_system-ds”.

Select “Oracle” as the Database Type and “Oracle's driver (Thin XA) Versions 9.0.1,9.2.0,10” as the Database Driver. Click Next.

b. On Transaction Options page, click Next.

Set Database Name=<YourDatabaseName>

Set Host Name=<YourDatabaseHostname>

Set Port = <YourPortNumber>

Set Database User Name = cmx

Set Password = !!cmx!!

Set Confirm Password = !!cmx!!

Click Next.

c. Test the driver connections by clicking Test Configuration.

If the test is unsuccessful, you must update values in this page and then retry the connection until successful. If the test is successful, click Next.

d. On the Select Targets page, select “AdminServer”.



Click Finish.

e. Click Activate Changes.

3. Create a Data Source called “ORS Data Source”.

a. Acquire lock by clicking the Lock & Edit button.

Under Services > JDBC > Data Sources configure a new ORS data source.

Click New.

Set the name to “ORS Data Source”.

Use “jdbc/siperian-<oracle_hostname>-<oracle_sid>-<ors_schema_name>-ds” for the JNDI name; where oracle_hostname is the name of your host, oracle_sid is the name of your Oracle instance, and ors_schema_name is the name of your ORS.

Select “Oracle” as the Database Type and “Oracle's driver (Thin XA) Versions 9.0.1, 9.2.0, 10” as the Database Driver.

Click Next.

b. On the Transaction Options page, click Next.

Set Database Name=<YourDatabaseName>

Set Host Name=<YourDatabaseHostname>

Set Port = <YourPortNumber>

Set Database User Name = <NameOfYourORS>

For example CMX_ORS

Set Password = !!cmx!!

Set Confirm Password = !!cmx!!

Click Next.

c. Test the driver connections, click “Test Configuration”.

If the test is unsuccessful, you need to update values in this page and then retry the connection until successful. If the test is successful, click Next.

d. On the Select Targets page, select “AdminServer”.

Click Finish.



Click Activate Changes.

Note: Use all lower case when creating the JNDI names.











Installation Steps




Solaris:


HP-UX:

/hpux/mrmcleanse/

Linux:

/linux/mrmcleanse/

AIX:

/aix/mrmcleanse/





5. Click Next.











9. Choose the WebLogic application server and click Next.


10. Configure WebLogic settings:

a. Choose a path to the WebLogic domain home for the domain you want to use for Cleanse Match Server. This is the domain you created in “Creating a WebLogic Domain” on page 131.

Click Next.

The WebLogic Application Server Login screen is displayed.

b. Enter the login for your WebLogic application:

WebLogic collects information for the administrative login that the installation process needs to create the JDBC data source to the Master Database.

Enter the host name, server name, user name, password, and port number. If you type in incorrect login information, the Cleanse Match Server installer does not allow you to continue. For more information, see “Changing the Username and Password for WebLogic” on page 296

11. Click Next.


Field Description










• Specify the Unlock Code, Optimization, Memory, and Correction Type parameters. For backslashes(\) in any of these parameters, use a double backslash (\\) instead. Click Next.


• Specify the AddressDoctor preload parameters. Click Next. The Choose AddressDoctor Database Path screen is displayed.


• If you are using Business Objects DQ XI, you must configure Business Objects DQ XI using the Cleanse Match Server installer. Specify the Host, Port, and Sub File parameters for your Business Objects DQ XI cleanse engine. Click Next.







The following log files are useful for troubleshooting any Cleanse Match Server installation process. Copy these log files to the installation documentation directory that you created in “Create an Installation Documentation Directory” on page 9. In



case of installation problems, these files will be useful to provide to Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii).






File Description











WebLogic log files under <weblogic_domain>/servers/<weblogic_server>/logs.: access.log, <weblogic_server>.log and <weblogic_domain>.log.


















You can configure the cleanse application for logging. The settings are listed in the log4j.xml file, located in the <infamdm_install_directory>/hub/cleanse/conf/ directory.



The default value is INFO for log4j.xml. You can turn on DEBUG for Cleanse Match Server by replacing INFO with DEBUG in log4j.xml.


You can further configure your Cleanse Match Server installation by customizing the values in the cmxcleanse.properties file located in the resources directory (such as: <infamdm_install_directory>/hub/cleanse/resources).


cmx.server.logging.location=/u1/infamdm/hub/cleanse/logscmx.server.datalayer.cleanse.working_files.location=/u1/infamdm/hub/cleanse/tmpcmx.server.datalayer.cleanse.working_files=KEEPcmx.server.datalayer.cleanse.execution=LOCAL

cmx.home=/u1/infamdm/hub/cleansecmx.appserver.type=weblogic












Configuring Cleanse Match Server for Multi-Threading

By default, Cleanse Match Server runs in single-threaded mode. If you have a Cleanse Match Server server with more than one CPU, then you may get performance benefits by configuring Cleanse Match Server for multi-threaded operation.

To configure Cleanse Match Server for multi-threading:1. Go to the following directory:

<infamdm_install_directory>/hub/cleanse/resources

and open the cmxcleanse.properties file for editing.



2. Find the following entry in the cmxcleanse.properties file:

# Cleanse Properties# control the number thread to use while cleaningcmx_server.cleanse.num_of_thread=1

3. Set the cmx_server.cleanse.num_of_thread parameter to the number of threads appropriate for your system.

The default, recommended value is 1 thread. Thread counts can be changed without needing to restart the server.

There are several factors you should consider:

• Number of processor cores available on your machine

You might consider setting the number of threads to the number of processor cores available on your machine. 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.

• Remote database connection

If you are working with a remote database, you might consider setting the threads to a number that is slightly higher than the number of processor cores, so that the wait of one thread can be used by another thread. Setting the number of threads slightly higher also enables you to account for the possible latency that might occur with a remote database.

• Process memory requirements

If you are running a memory-intensive process, you must restrict the total memory allocated to all threads that are run under the JVM to 1 Gigabyte. Because Informatica MDM Hub runs in a 32-sit JVM environment, each thread requires memory from the same JVM, and therefore the total amount of memory is restricted.

If you set the num_of_thread property to any illegal values, such as a negative number, 0, a character or a string, then the property value will be automatically reset to the default value (1).

Note: You must change this value after migration from an earlier hub version or all the values will default to one (1) thread.








2. Configure each Cleanse Match Server instance in a separate application server instance. On WebLogic, create a separate domain for each new cleanse instance. For more information, see your WebLogic documentation.








The second approach is lighter and allows multiple instances to share the Informatica MDM Hub configuration settings. The disadvantage is that both



servers share the temporary directories and write to the same log file. This complicates diagnostics when both instances run Cleanse Match Server at the same time.



To deploy the EAR file manually, use the admin console for deployment. Accept all defaults.

















In the process of installing Cleanse Match Server, you can choose whether to run the postInstallSetup script automatically to deploy Cleanse Match Server. If you choose not to run this script automatically as part of the installation process, you must run it yourself. For more information, see “PostInstallSetup” on page 110.


./postInstallSetup.sh -Dweblogic.password=<weblogicPassword> -Ddatabase.password=<yourDBPassword>



You can also use this script if you need to redeploy the application to the application server. Alternatively, you can also use the application server’s tool to do the deployment yourself, as long as the Cleanse Match Server EAR file is deployed from the Informatica Cleanse Match Server installation directory. The section below lists basic guidelines for redeployment. For more information, see your application server documentation.



Redeploying Manually on WebLogic

To redeploy manually on the WebLogic application server:1. Undeploy the siperian-mrm-cleanse.ear file using the WebLogic Server

Administration Console.

2. Deploy the siperian-mrm-cleanse.ear file using the WebLogic Server Administration Console in stage mode.


Installing the Cleanse Match Server (WebSphere/Unix)


This section describes how to install the Cleanse Match Server running in the WebSphere application server environment on the Unix platform.

















On the machine where you will run the Cleanse Match Server, install and configure your WebSphere environment according to your WebSphere documentation.










Configure WebSphere for Cleanse Match Server

If you install Cleanse Match Server on a different machine from the one running Hub Server, on the Cleanse Match Server machine, you must create separate data sources for each ORS.

Configure WebSphere to Use an Oracle Data Source

To configure WebSphere to use an Oracle data source, add the Oracle JDBC Driver JAR file to the following directory:

<WebSphere_install_dir>/lib

See the Informatica MDM Hub Release Notes for the supported versions of these drivers. Contact Oracle for the the files necessary for your database configuration.

Creating Master Data Sources in WebSphere 6.1.0.29

To create your WebSphere 6.1.0.29 master data sources:1. Start the application server and launch the WebSphere Application Server Admin

Console.

2. Login with any user name.

3. Specify the location of the driver libraries:

a. Expand Environment in the console navigation tree.

b. Click the WebSphere Variables link.

c. Update the ORACLE_JDBC_DRIVER_PATH variable to point to the JDBC driver location. (E.g.: /u1/was61029/AppServer/Lib).

4. Create the security account to be used by the Informatica MDM Master Data Source:

a. Expand Security in the console navigation tree.

Click Secure administration, applications, and infrastructure link.



b. Expand Java Authentication and Authorization Service under Authentication in right side of the console window.

Click J2C Authentication Data.

c. Click New to create a new security account.

d. Set the following:

Alias = CMX_SYSTEM

User ID = cmx_system

Do not change this username.

Password = !!cmx!!

To learn about changing this password, see “Changing the Password for the CMX_SYSTEM User” on page 152.

e. Click OK to save.

5. Create the JDBC Provider:

a. Expand Resources in the console navigation tree and then expand the JDBC menu.

Click the JDBC Providers link.

Make sure that the scope is set to Node. (Change and apply if this needs adjustment).

b. Click New to create a new JDBC Provider.

Select Oracle from database type list.

Select Oracle JDBC Driver from provider type list.

Select XA data source from implementation type list.

c. Change the name to “Informatica MDM Oracle JDBC Provider (XA)”.

Click Next and Finish to save.

6. Create the Informatica MDM Master Data Source:

a. Click the created provider.

b. Click the Data Sources link (under Additional Properties in right side of the console window).



c. Click New to create the new data source.

d. Fill in the form with the following values:

Name = Informatica MDM Master Data Source

JNDI Name = jdbc/siperian-cmx_system-ds

Component-managed Authentication Alias = <hostname>/cmx_system

e. Click Next and the URL will be available.

URL = jdbc:oracle:thin:@<oracle_hostname>:<oracle_port_number>:<oracle_sid>

f. Click Next and Finish.

Note: The JNDI name must be in lower case.


After you have installed Informatica MDM Hub, you can change the password for CMX_SYSTEM. If you do so, you must also:• Change the password for the CMX user in Oracle

• Set the same password in the datasource on the application server

Creating ORS Data Sources in WebSphere 6.0.1.29

To create your WebSphere 6.0.1.29 ORS data sources:1. Start the application server and launch the WebSphere Application Server Admin

Console.





c. Update the ORACLE_JDBC_DRIVER_PATH variable to point to the JDBC driver location. (for example, /u1/was6103/AppServer/Lib).



4. Create the security account to be used by the Informatica MDM ORS Data Source:


Click Secure administration, applications, and infrastructure link in WebSphere 6.1.0.29.

b. Expand Java Authentication and Authorization Service under Authentication in right side of the console window.


Click New to create a new security account.

c. Set the following:

Alias = cmx_ors

User ID = cmx_ors

Password = !!cmx!!

To learn about changing this username and password, see “Changing the Username and Password for the CMX_ORS User” on page 154.

d. Click OK to save.



Click JDBC Providers link.



Select Oracle from database type list.

Select Oracle JDBC Driver from provider type list.

Select XA data source from implementation type list.





6. Create the Informatica MDM ORS Data Source:




Fill in the form with the following values:

Name = Informatica MDM ORS Data Source

JNDI Name = jdbc/siperian-<oracle_hostname>-<oracle_SID>-cmx_ors-ds

Component-managed Authentication Alias = <hostname>/cmx_ors

d. Click Next and the URL is accessible.

URL= jdbc:oracle:thin:@<oracle_hostname>:<oracle-port_num-

ber>:<oracle_sid>

e. Click Next and Finish.


Changing the Username and Password for the CMX_ORS User

After you have installed the Informatica MDM Hub, you can change the username and password for CMX_ORS.

If you do so, you must also:• Change the password for the CMX_ORS user in Oracle.

• Set the same password in the datasource on the application server.

• Register the schema with the same username and password.











Installation Steps






Solaris:


HP-UX:

/hpux/mrmcleanse/

Linux:

/linux/mrmcleanse/

AIX:

/aix/mrmcleanse/





5. Click Next.









9. Choose the WebSphere application server and click Next.



10. Configure WebSphere settings:

Choose a path to the WebSphere application server and click Next.

11. The WebSphere Security Selection screen is displayed. Choose whether WebSphere is security enabled from the two options; Yes or No. No is the default.

• If you click No and Next, the WebSphere Application Server screen is displayed.Set the server name and SOAP port for your WebSphere application server. Click Next.

• If you click Yes and Next,the WebSphere Application Server and User Credentials screen is displayed.Set the server name and SOAP port for your WebSphere application server. Fill in the Username field and the Password. Click Next.




• Specify the Unlock Code, Optimization, Memory, and Correction Type parameters. For backslashes(\) in any of these parameters, use a double backslash (\\) instead. Click Next.


• Specify the AddressDoctor preload parameters. Click Next. The Choose AddressDoctor Database Path screen is displayed.












File Description
























You can configure the cleanse application for logging. The settings are listed in the log4j.xml file, located in the <infamdm_install_directory>/hub/cleanse/conf/ directory.

The default value is INFO for log4j.xml. You can turn on DEBUG for Cleanse Match Server by replacing INFO with DEBUG in log4j.xml.


You can further configure your Cleanse Match Server installation by customizing the values in the cmxcleanse.properties file located in the resources directory (such as: <infamdm_install_directory>/hub/cleanse/resources).


cmx.server.logging.location=/u1/infamdm/hub/cleanse/logscmx.server.datalayer.cleanse.working_



files.location=/u1/infamdm/hub/cleanse/tmpcmx.server.datalayer.cleanse.working_files=KEEPcmx.server.datalayer.cleanse.execution=LOCAL

cmx.home=/u1/infamdm/hub/cleansecmx.appserver.type=websphere












Configuring Cleanse Match Server for Multi-Threading

By default, Cleanse Match Server runs in single-threaded mode. If you have a Cleanse Match Server server with more than one CPU, then you may get performance benefits by configuring Cleanse Match Server for multi-threaded operation.

To configure Cleanse Match Server for multi-threading:1. Go to the following directory:

<infamdm_install_directory>/hub/cleanse/resources

and open the cmxcleanse.properties file for editing.

2. Find the following entry in the cmxcleanse.properties file:

# Cleanse Properties# control the number thread to use while cleaningcmx_server.cleanse.num_of_thread=1

3. Set the cmx_server.cleanse.num_of_thread parameter to the number of threads appropriate for your system.

The default, recommended value is 1 thread. Thread counts can be changed without needing to restart the server.

There are several factors you should consider:

• Number of processor cores available on your machine

You might consider setting the number of threads to the number of processor cores available on your machine. 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.

• Remote database connection



If you are working with a remote database, you might consider setting the threads to a number that is slightly higher than the number of processor cores, so that the wait of one thread can be used by another thread. Setting the number of threads slightly higher also enables you to account for the possible latency that might occur with a remote database.

• Process memory requirements

If you are running a memory-intensive process, you must restrict the total memory allocated to all threads that are run under the JVM to 1 Gigabyte. Because Informatica MDM Hub runs in a 32-sit JVM environment, each thread requires memory from the same JVM, and therefore the total amount of memory is restricted.

If you set the num_of_thread property to any illegal values, such as a negative number, 0, a character or a string, then the property value will be automatically reset to the default value (1).

Note: You must change this value after migration from an earlier hub version or all the values will default to one (1) thread.




















On WebSphere, you must either have the Network Deployment edition of WebSphere, which allows you to create and manage multiple instances, or use the



wsinstance script and adjust the settings. In either case, change the defalcators port settings using the WAS Admin Console so the values for the separate instances don’t conflict. If you are using the wsinstance script, install the Admin console on the new instance manually and change admin_host port assignment. For more information, see your WebSphere documentation.











To deploy the EAR file manually, use the admin console for deployment. Accept all defaults.




In the process of installing Cleanse Match Server, you can choose whether to run the postInstallSetup script automatically to deploy Cleanse Match Server. If you choose not to run this script automatically as part of the installation process, you must run it yourself. For more information, see “PostInstallSetup” on page 110.


postinstallsetup.sh -Ddatabase.password=<yourDBPassword>


You can also use this script if you need to redeploy the application to the application server. Alternatively, you can also use the application server’s tool to do the deployment yourself, as long as the Cleanse Match Server EAR file is deployed from the Informatica Cleanse Match Server installation directory. The section below lists basic guidelines for redeployment. For more information, see your application server documentation.

Redeploying Manually on WebSphere

To redeploy manually on the WebSphere application server:1. Undeploy the siperian-mrm-cleanse.ear file using the WebSphere Server

Administration Console.

2. Install the siperian-mrm-cleanse.ear file using the WebSphere Application Server Administrative Console. Be sure to allow the deployment to generate default bindings by checking the option in the “Preparing for the application installation” panel.


Installing the Cleanse Match Server (JBoss/Windows)


This section describes how to install the Cleanse Match Server running in the JBoss application server environment on the Windows platform.

















On the machine where you will run the Cleanse Match Server, install and configure your JBoss environment according to your JBoss documentation.


To configure JBoss to use an Oracle data source:1. Contact Oracle to obtain any JDBC drivers you may need for your database

configuration. Once you obtain the drivers, configure JBoss as follows:

2. Copy the new Oracle JDBC driver file(s) to your<JBoss_install_dir>\server\<configuration_name>\lib directory.









Have an Informatica license file. The Cleanse Match Server installer will not install Cleanse Match Server without a valid license file. Contact Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii) for a license file.




Configure JBoss for Cleanse Match Server

This section describes how to configure JBoss before installing the Cleanse Match Server.

Removing Obsolete Oracle Drivers

Before you install the Cleanse Match Server, delete any instances of old Oracle drivers from your JBoss directory structure. The most likely place for the following files to delete is JBoss\server\<configuration_name>\lib. • ocrs12.jar

• orai18n.jar

• nls_charset12.jar




If you install Cleanse Match Server on a different machine from the one running Hub Server, on the Cleanse Match Server machine, you must create data sources for each ORS. You must do some Oracle configuration as well as some JBoss configuration. See “Configuring JBoss to Use an Oracle Data Source” on page 171 for details.

Configuring JBoss to Use an Oracle Data Source

Note: If you are running Oracle on the same host that is running Cleanse Match Server, you can skip this section.

To configure JBoss to use an Oracle data source:1. Copy a sample datasource file (name-ds.xml) into your JBoss deploy directory.

By default, the JBoss deploy directory is:

<JBoss_install_dir>\server\<configuration_name>\deploy

You can find the samples in:

<JBoss_install_dir>\docs\examples\jca

You can change the name of the sample datasource file, but the file must end with -ds.xml to be recognized as a datasource descriptor.

2. Edit the datasource definition to match your database connection parameters. Edit the following parameters:


jndi-name Set to the following value for a Hub Server datasource:

jdbc/siperian-cmx_system-ds

Set to the following value for the cleanse server datasource:

jdbc/siperian-<oracle_hostname>-<oracle_sid>-<ors_schema_name>-ds

where oracle_hostname is the name of your host, oracle_sid is the name of your Oracle instance and ors_schema_name is the name of your ORS.





jboss-5.1.0.GA\bin


run.bat -b 0.0.0.0



Installation Considerations• Important: You can install Hub Server and Cleanse Match Server using any

username you want, but you must use the same user name to install both servers.


connection-url

JDBC driver connection URL string for your driver. Make sure that the database name, host, and port are correct for the database to which you are connecting. Example:

jdbc:oracle:thin:@server_name:1521:orcl

username Default username used when creating a new connection. The default user in Oracle for the Hub Server is cmx, and for the Cleanse Match Server is cmx_ors.

password The default password used when creating a new connection.




• The Cleanse Match Server installer can also be used to upgrade existing installations. If you have a previously-installed version of Informatica MDM Hub software, see the Informatica MDM Hub Upgrade Guide to learn more. This section covers new installations.

Installation Steps


2. Run the Informatica Cleanse Match Server installer (hub_cleanse_install.exe). The Cleanse Match Server installer is on the distribution in the \mrmcleanse\windows directory.

The Cleanse Match Server installer displays the Introduction screen.

3. Click Next.


4. Click the I accept the terms of the License Agreement button and then click Next.



• Click Next to install Cleanse Match Server in C:\infamdm\hub\cleanse.

• Click the Choose button to choose another location to install Cleanse Match Server and then click Next.


Note: Cleanse Match Server will fail to load if the total length of this path exceeds 256 characters.

The Choose Shortcut Folder is displayed.

6. Select a location for the product icons. Click Next.


7. Click Choose to select a license file. Informatica provides you with a license file. If you do not have the license file, you cannot continue with the install. Contact



Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii) to obtain a license file.



9. Choose the JBoss application server and click Next.

The JBoss Application Server Home screen is displayed

10. Configure JBoss settings:






Important: If you change the default port number, you also need to change it in the following file:

<JBoss_install_dir>\server\<configuration_name> \conf\bindingservice.beans\META-INF\bindings-jboss-beans.xml

d. Click Next.












12. In the Deploy screen, click Yes to run the script during the installation, or click No to manually run it later (see “Running PostInstallSetup” on page 179 for instructions).

13. In the Pre-Installation Summary screen, if you want to change any options, click the Previous button to navigate to the appropriate screens. Once the summary screen reflects the options you want, click Install to start the installation process.



14. Choose Yes to restart your system, or choose No to restart it later and click Done to exit the Cleanse Match Server installer.



File Description

<infamdm_install_directory>\hub\cleanse\Informatica_MDM_Hub_Cleanse_Match_Server_InstallLog.xml


<infamdm_install_directory>\hub\cleanse\logs\postInstallSetup.log


<infamdm_install_directory>\hub\cleanse\logs\cmxserver.log


<infamdm_install_directory>\hub\cleanse\infamdm_installer_debug.txt







from which it was deployed. Therefore, do not move the EAR file to deploy onto another machine. For example, if you installed Cleanse Match Server on a Marketing machine and then deployed the EAR on the Sales machine, the application would not be able to locate the installation for configuration information such as logging.



For more information regarding cleanse engine configuration, see the Informatica MDM Hub Cleanse Adapter Guide.

<infamdm_install_directory>\hub\cleanse\logs\installPrereq.log


JBoss log files (such as <JBoss_install_dir>\server\<configuration_name>\log\server.log).


File Description




Check one of the following files to find out the Cleanse Match Server version and build number:• manifest.mf JAR entry inside the <infamdm_install_

directory>\hub\cleanse\siperian-mrm-cleanse.ear file

• Another place to check is: <infamdm_install_directory>\hub\cleanse\bin\versionInfo.bat file


By default, the temporary files generated by the cleanse service are left on disk. You can configure the cleanse server to clean these up by setting a flag in the cmxcleanse.properties file which is stored, by default, in the following directory:

<infamdm_install_directory>\hub\cleanse\resources\



You can change the value to FALSE to delete the file after cleanse/strip is completed.



You can configure the cleanse application for logging. The settings are listed in the log4j.xml file, located in the <infamdm_install_directory>\hub\cleanse\conf directory.

The default value is INFO in the log4j.xml file. You can enable DEBUG for the Cleanse Match Server by replacing INFO with DEBUG in the log4j.xml file.

After you update this file, you must restart the Cleanse Match Server application and rerun postInstallSetup.bat. For JBoss, the jboss-log4j.xml file is located in the JBoss\server\<configuration_name>\conf directory.




You can further configure your Cleanse Match Server installation by customizing the values in the cmxcleanse.properties file located in the resources directory (such as: C:\infamdm\hub\cleanse\resources).


cmx.server.datalayer.cleanse.working_files.location=C:\infamdm\hub\cleanse\tmpcmx.server.datalayer.cleanse.working_files=KEEPcmx.server.datalayer.cleanse.execution=LOCAL

cmx.home=C:\infamdm\hub\cleansecmx.appserver.type=jboss

Adding the Oracle TNS Name to the ORS Database

Cleanse Match Server processes cleanse jobs either online or in batches. In the case of an online operation, the application sends back the result as an XML response via HTTP protocol. In the case of a batch job, the batch commands that Cleanse Match Server application launches use Oracle SQL loader to write the data back.

When the loader is invoked, it uses the parameters in tnsnames.ora to connect to the Oracle database. The Cleanse Match Server installer does not add the TNS name into the Oracle installation. Therefore, on the cleanse server machine, you must add the TNS entry to the tnsnames.ora file.







Enter this TNS name when you register the ORS database using the Databases tool in the Hub Console according to the instructions in the Informatica MDM Hub Administrator Guide.

Note: The TNS names on the Hub Server machine and the Cleanse Match Server machine must be the same.


This section describes tasks to complete after you have installed the software.


If you chose to have the Cleanse Match Server installer skip the post-install process, you must run this manually.


<infamdm_install_directory>\hub\cleanse












2. Configure your system to run multiple instances of your application server according to the instructions in “Configuring Multiple Instances of Your Application Server” on page 180.

3. Deploy Cleanse Match Server to the second instance of your application server. For more information, see “Deploying Cleanse Match Server on the Second Application Server Instance” on page 181.

Configuring Multiple Instances of Your Application Server



2. Configure each Cleanse Match Server instance in a separate application server instance. Copy the JBoss files to a new directory. Change the port settings to allow multiple instances to coexist without conflicting ports. For more information, see your JBoss documentation.




Now you can deploy Cleanse Match Server, as described in the next section.

Deploying Cleanse Match Server on the Second Application Server Instance






Using this approach, you cannot use the postInstallSetup script to deploy the additional cleanse instance, but you can deploy them manually on the application server.


To deploy the EAR file manually, copy the file to the following directory:

<JBoss_install_dir>\server\<configuration_name>\deploy



Using Multiple Cleanse Servers

Informatica MDM Hub supports running multiple Cleanse Match Server servers per ORS database. This allows you to parallelize the work of cleansing the data. However, only one Cleanse Match Server application is supported on a single system.

When Cleanse Match Server is not installed on the same application server as Hub Server, then you must manually configure the application server to create the datasources for Cleanse Match Server to take advantage of connection pooling and improved performance.

Note: If the datasource does not exist, the Cleanse Match Server uses the JDBC connection.

To configure multiple cleanse servers1. After you have installed and configured the Hub Server and Cleanse Match Server,

install your cleanse engine and Cleanse Match Server on another machine.

2. For each Cleanse Match Server server, on the application server create the datasource for each cmx_system. This needs to have exactly the same name and JNDI name as the Hub Server configuration. For more information about creating datasources, see the Informatica MDM Hub Administrator Guide.



5. Add the new cleanse server.

Informatica MDM Hub uses round-robin load-balancing to spread cleansing tasks between all the cleanse servers that are online. You can see all the cleanse servers in the Cleanse Match Server workbench.

Distributed Cleanse Match Servers

When running a stage/match job, if more than one Cleanse Match Server is registered, and if the total number of records to be staged/matched is more than 500, then the job will get distributed in parallel between the different cleanse/match servers.



Below are the parameters that need to be set to utilize the cleanse servers based on the server configuration.

Note: To configure distributed cleanse and distributed match, you must set Thread Count and CPU Rating values when you register the Cleanse Match Server in the Hub Console.


Thread Count Reflects the number of threads that a server will be asked to handle. We recommend that you set the thread count higher than the number of CPUs available if the servers are widely distributed and/or latency is high, so that servers can be doing more work during wait time.

CPU Rating Rates the relative “strength” of the CPUs across the machines; the “lowest power” machine would have a rating of 1.0. Other CPUs on different machines would have a number relative number to the lowest powered machine.


Installing the Cleanse Match Server (WebLogic/Windows)


This section describes how to install the Cleanse Match Server running in the WebLogic application server environment on the Windows platform.

















On the machine where you will run the Cleanse Match Server, install and configure your WebLogic environment according to your WebLogic documentation.










Configure WebLogic for Cleanse Match Server

This section describes how to configure WebLogic to work with the Cleanse Match Server.

Creating a WebLogic Domain

Before installing Cleanse Match Server on the WebLogic application server, you must create a WebLogic domain for the Cleanse Match Server application using the WebLogic Administration Wizard. For more information, see your WebLogic documentation.


If you install Cleanse Match Server on a different machine from the one running Hub Server, you must create data sources for each ORS. You must do this on the application server on the Cleanse Match Server machine. You must configure the location of the JDBC driver as well as create a datasource for each ORS.

Setting the Location of the JDBC Driver

Contact Oracle to obtain any JDBC drivers you may need for your database configuration. Once you obtain the drivers, configure WebLogic as follows:• Add the Oracle JDBC Driver JAR files to the

<WebLogic_install_dir>\weblogicxx\server\lib directory.

where weblogicxx is the directory for your version of WebLogic. See the Informatica MDM Hub Release Notes for the supported versions of these drivers.



Configuring WebLogic to Use an Oracle Data Source

If you are running the Hub Server on the same host that is running the Cleanse Match Server, you can skip this section.

To configure WebLogic to use an Oracle data source:1. Launch the WebLogic administrator console.

2. Create a connection pool called “MRM Connection Pool”.

e. Under Services > JDBC > Connection Pools > Configure a new JDBC connection pool.

• Select “Oracle” as the Database Type and “Oracle’s driver (Thin XA)” as the Database Driver.

• Set Name = MRM Connection Pool

• Set Database Name = <YourDatabaseName>

• Set Host Name = <YourHostname>

• Set Port = <YourPortNumber >

• Set Database User Name = cmx

• Set password = !!cmx!!

f. Add the following properties:

g. Test the driver connections, create, and deploy.

h. Go to the Connections tab, choose Advanced Options > Show.

Enable “Supports Local Transaction” and click Apply.

3. Create a connection pool called “ORS Connection Pool”.

Property Value

TestConnectionsOnRelease false

TestTableName C_REPOS_DATABASE

TestConnectionsOnReserve false



a. Choose Services > JDBC > Connection Pools > Configure a new JDBC Connection Pool.

• Select Oracle as the database type and Other as the database driver.

• Set Name = ORS Connection Pool


• Set Host Name = <YourHostname>

• Set Port = <YourPortNumber>

• Set Database User Name = <NameOfYourORS>

For example CMX_ORS.

• Set the Password to “!!cmx!!”

b. Set the following properties:

c. Test the driver connections, create, and deploy.

d. Go to the Connections tab, choose Advanced Options > Show.

Enable “Supports Local Transaction” and click Apply.

4. Create a Data Source called “MRM Data Source”

Under Services > JDBC > Data Sources > Configure a new JDBC data source named “MRM Data source”.

• Use “jdbc/siperian-cmx_system-ds” for the JNDI name.

• Set the pool name to “MRM Connection Pool”.

• Select myserver and click Create.


Property Value

TestConnectionsOnRelease false

TestTableName C_REPOS_DB_RELEASE

TestConnectionsOnReserve false



Use “jdbc/siperian-hostname-oracleinstance-ors-ds” for the JNDI name, where hostname is the name of your host, oracleinstance is the name of your Oracle instance and ors is the name of your ORS.

• Set the pool name to “ORS Connection Pool”

• Select myserver and click Create.


You must create data sources and connection pools for every ORS you plan to register.

Configuring WebLogic to Use an Oracle Datasource

Notes:• If you are running Oracle on the same host that is running Cleanse Match Server,

you can skip this section.

• These instructions apply to WebLogic 9.x or WebLogic 10.x.

To configure WebLogic to use an Oracle data source:1. Launch the WebLogic Administrator Console.

2. Create a data source called “MRM Data Source”.

a. Acquire a lock by clicking the Lock & Edit button.

Under Services > JDBC > Data Sources configure a new master data source.

Click New.

• Set the name to “MRM Data Source”.

• Set the JNDI Name to “jdbc/siperian-cmx_system-ds”.

• Select “Oracle” as the Database Type and “Oracle's driver (Thin XA) Versions 9.0.1, 9.2.0, 10” as the Database Driver.

• Click Next.

b. On the Transaction Options page, click Next.




• Set Host Name = <YourDatabaseHostname>


• Set Database User Name = cmx

• Set Password = !!cmx!!

• Set Confirm Password = !!cmx!!

• Click Next.

c. Test the driver connections by clicking Test Configuration.

If the test is unsuccessful, you must update values in this page then retry the connection until successful. If the test is successful, click Next.

d. On Select Targets page, select “AdminServer”.

Click Finish.

e. Click Activate Changes.


a. Acquire lock by clicking the Lock & Edit button.

Under Services > JDBC > Data Sources configure a new ORS data source.

Click New.

• Set the name to “ORS Data Source”.

• Use “jdbc/siperian-hostname-oracleinstance-ors-ds” for the JNDI name; where hostname is the name of your host, oracleinstance is the name of your oracle instance and ors is the name of your ORS.

• Select “Oracle” as the Database Type and “Oracle's driver (Thin XA) Versions 9.0.1, 9.2.0, 10” as the Database Driver.

• Click Next.

b. On Transaction Options page, click Next.


• Set Host Name = <YourDatabaseHostname>




• Set Database User Name = <NameOfYourORS>

For example CMX_ORS.

• Set Password = !!cmx!!

• Set Confirm Password = !!cmx!!

• Click Next.

c. Test the driver connections, click Test Configuration.

If the test is unsuccessful, you need to update values in this page then retry the connection until successful. If the test is successful. Click Next.

d. On Select Targets page, select “AdminServer”.

Click Finish.











Installation Steps

To install the Cleanse Match Server:1. Make sure that your application server is started and running correctly.



3. Click Next.














7. Click Choose to select a license file. Informatica provides you with a license file. If you do not have the license file, you cannot continue with the install. Contact Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii) to obtain a license file.



9. Choose the WebLogic application server and click Next.


10. Configure WebLogic Server settings.

a. Choose a path to the WebLogic domain installation directory for the domain you want to use for Informatica MDM Hub. This is the domain you created in “Creating a WebLogic Domain” on page 186. Click Next.

The Application Server Login screen is displayed.

b. Enter the following information:

Field Description





The Cleanse Match Server installer collects information for the administrative login and uses it to create the JDBC data source to the Master Database.

If you type in incorrect login information, the verification process in the Cleanse Match Server installer will stop until you correct the information.

You can correct this information after the installation process is complete. For more information, see “Changing the Username and Password for WebLogic” on page 313.

c. Click Next.













Field Description










File Description











WebLogic log files under <weblogic_domain>\servers\<weblogic_server>\logs.: access.log, <weblogic_server>.log and <weblogic_domain>.log














After you update this file, you must restart the Cleanse Match Server application and rerun postInstallSetup.bat.


You can further configure your Cleanse Match Server installation by customizing the values in the cmxcleanse.properties file located in the resources directory (such as: <infamdm_install_directory>\hub\cleanse\resources).


cmx.server.datalayer.cleanse.working_



files.location=C:\infamdm\hub\cleanse\tmpcmx.server.datalayer.cleanse.working_files=KEEPcmx.server.datalayer.cleanse.execution=LOCAL

cmx.home=C:\infamdm\hub\cleansecmx.appserver.type=weblogic



















postInstallSetup.bat -Dweblogic.password=your_password -Ddatabase.password=!!cmx!!

where your_password is the password for your WebLogic application server.










2. Configure your system to run multiple instances of your application server. For more information, see “Configuring Multiple Instances of Your Application Server” on page 200.





2. Configure each Cleanse Match Server instance in a separate application server instance. On WebLogic, create a separate domain for each cleanse instance. For more information, see your WebLogic documentation.













To deploy the EAR file manually, use the Administrative Console for deployment. Accept all defaults.





When Cleanse Match Server is not installed on the same application server as Hub Server, then you must manually configure the application server to create the datasources for Cleanse Match Server to take advantage of connection pooling and improved performance.












Installing the Cleanse Match Server (WebSphere/Windows)


This section describes how to install the Cleanse Match Server running in the WebSphere application server environment on the Windows platform.

















On the machine where you will run the Cleanse Match Server, install and configure your WebSphere environment according to your WebSphere documentation.










Configure WebSphere for Cleanse Match Server

This section describes how to configure WebSphere for the Cleanse Match Server.

Configuring WebSphere to Use an Oracle Data Source

If you install Cleanse Match Server on a different machine from the one running Hub Server, on the Cleanse Match Server machine, you must create data sources for each ORS.

Contact Oracle to obtain any JDBC drivers you may need for your database configuration.

To configure WebSphere to use an Oracle data source, add the Oracle JDBC Driver JAR files to the <WebSphere_install_dir>\lib directory. See the Informatica MDM Hub Release Notes for the supported versions of these drivers.

Creating Master Data Sources in WebSphere 6.1.0.29

To create your WebSphere master data sources:1. Start the application server. Choose Start > Programs > IBM WebSphere >

Application Server v6 > Profiles > <app_server_name> > Start the Server.

2. Start the WebSphere Application Server Admin Console. Choose Start > Programs > IBM WebSphere > Application Server v6 > Profiles > <app_

server_name> > Administrative Console.





c. Update the ORACLE_JDBC_DRIVER_PATH variable to point to the JDBC driver location. (such as <WebSphere_install_dir>\AppServer\lib).



5. Create the security account to be used by the Informatica MDM Master Data Source:


Click the Secure administration, application and infrastructure link.

b. Expand Java Authentication and Authorization Service under Authentication in the right side of the console window.


c. Click New to create a new security account.

d. Set the following:

• Alias = CMX_SYSTEM

• User ID = cmx_system

Do not change this username.

• Password = !!cmx!!

To learn about changing this password, see “Changing the Password for the CMX_SYSTEM User” on page 208.

e. Click OK to save.


a. Expand Resources in the console navigation tree and expand the JDBC menu.

• Click the JDBC Providers link.

• Make sure that the scope is set to Node. (Change and apply if this needs adjustment).


• Select Oracle from database type list.

• Select Oracle JDBC Driver from provider type list.

• Select XA data source from implementation type list.


• Click Next and Finish to save.



7. Create the Informatica MDM Master Data Source:




d. Fill in the form with the following values:

• Name = Informatica MDM Master Data Source

• JNDI Name = jdbc/siperian-cmx_system-ds

• Component-managed Authentication Alias = <hostname>/cmx_system

e. Click Next and specify the following value:

• URL = jdbc:oracle:thin:@<oracle_hostname>:<oracle_port_number>:<oracle_sid>

f. Click Next and Finish.



After you have installed Informatica MDM Hub, you can change the password for CMX_SYSTEM. If you do so, you must also:• Change the password for the CMX user in Oracle

• Set the same password in the datasource on the application server

Creating ORS Data Sources in WebSphere 6.1.0.29

To create your WebSphere 6.1.0.29 ORS data sources:1. Start the application server. Choose Start > Programs > IBM WebSphere >

Application Server v6 > Profiles > <configuration_name> > Start the Server.

2. Start the WebSphere application server admin console. Choose Start > Programs > IBM WebSphere > Application Server v6 > Profiles > <configuration_

name> > Administrative Console.







c. Update the ORACLE_JDBC_DRIVER_PATH variable to point to the JDBC driver location. (for example, <WebSphere_install_dir>/AppServer/lib).

5. Create the security account to be used by the Informatica MDM ORS Data Source:


Click the Secure administration, application and infrastructure link.

b. Expand Java Authentication and Authorization Service under Authentication in the right side of the console window.


Click New to create a new security account.

c. Set the following:

• Alias = cmx_ors

• User ID = cmx_ors

• Password = !!cmx!!

To learn about changing this username and password, see “Changing the Username and Password for the CMX_ORS User” on page 210.

d. Click OK to save.



Click JDBC Providers link.





• Select Oracle from database type list.

• Select Oracle JDBC Driver from provider type list.

• Select XA data source from implementation type list.



7. Create the Informatica MDM ORS Data Source:




Fill in the form with the following values:

• Name = Informatica MDM ORS Data Source

• JNDI Name = jdbc/siperian-<oracle_hostname>-<oracle_SID>-cmx_ors-ds

• Component-managed Authentication Alias = <hostname>/cmx_ors

d. Click Next.The URL will be available.

• URL= jdbc:oracle:thin:@<oracle_hostname>:<oracle-port_

number>:<oracle_sid>

e. Click Next and Finish.


Changing the Username and Password for the CMX_ORS User

After you have installed the Informatica MDM Hub, you can change the username and password for CMX_ORS.

If you do so, you must also:• Change the password for the CMX_ORS user in Oracle.

• Set the same password in the datasource on the application server.



• Register the schema with the same username and password.







Installation Steps




3. Click Next.














7. Click Choose to select a license file. Informatica provides you with a license file. If you do not have the license file, you cannot continue with the install. Contact Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii) to obtain a license file.



9. Choose the WebSphere application server and click Next.


10. Configure WebSphere settings:

a. Choose a path to the WebSphere application server and click Next.

11. The WebSphere Security Selection screen is displayed. Choose whether WebSphere is security enabled from the two options; Yes or No. No is the default.

• If you click No and Next, the WebSphere Application Server screen is displayed.Set the server name and SOAP port for your WebSphere application server. Click Next.



• If you click Yes and Next,the WebSphere Application Server and User Credentials screen is displayed.Set the server name and SOAP port for your WebSphere application server. Fill in the Username field and the Password. Click Next.



















File Description











WebSphere log files in the following location: <WebSphere_install_dir>\profiles\AppSrv01\logs\<servername>















After you update this file, you must restart the Cleanse Match Server application and rerun postInstallSetup.bat.


You can further configure your Cleanse Match Server installation by customizing the values in the cmxcleanse.properties file located in the resources directory (such as: <infamdm_install_directory>\hub\cleanse\resources).


cmx.server.datalayer.cleanse.working_



files.location=C:\infamdm\hub\cleanse\tmpcmx.server.datalayer.cleanse.working_files=KEEPcmx.server.datalayer.cleanse.execution=LOCAL

cmx.home=C:\infamdm\hub\cleansecmx.appserver.type=websphere



















postInstallSetup.bat -Ddatabase.password=!!cmx!!










2. Configure your system to run multiple instances of your application server. For more information, see “Configuring Multiple Instances of Your Application Server” on page 219.






On WebSphere, you must either have the Network Deployment edition of WebSphere, which allows you to create and manage multiple instances, or use the instance script and adjust the settings. In either case, change the default_host port settings using the WAS Admin Console so the values for the separate instances don’t conflict. If you are using the wsinstance script, install the Admin console on the new instance manually and change admin_host port assignment. For more information, see your WebSphere documentation.













To deploy the EAR file manually, use the Administrative Console for deployment. Accept all defaults.



When Cleanse Match Server is not installed on the same application server as Hub Server, then you must manually configure the application server to create the



datasources for Cleanse Match Server to take advantage of connection pooling and improved performance.















5
Launching the Hub Console
This chapter introduces the Hub Console and provides instructions for launching the Hub Console.

Chapter Contents

• About the Hub Console

• Starting the Hub Console

• Post-setup Tasks

223

About the Hub Console

About the Hub Console

Administrators and data stewards can access Informatica MDM Hub features via the Informatica MDM Hub user interface, which is called the Hub Console. The Hub Console comprises a set of tools. Each tool allows you to perform a specific action, or a set of related actions. The available tools in the Hub Console depend on your Informatica license agreement.

You do not need to install the Hub Console because the Hub Console is launched from the Hub Server installation using Java Web Start. Or go to:

http://<hostname>:<port>/cmx/siperian-console.jnlp

Make sure that Java Web Start has been installed. The following URL is a page that has a link to the Web Start installer:

http://<hostname>:<port>/cmx

In these URLs, hostname is the host running your application server and port is the port on which that application server is listening.


Starting the Hub Console


To launch the Hub Console:1. Open a browser window and enter the following URL:

http://YourHubHost:<port>/cmx/

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

Note: You must use an HTTP connection to start the Hub Console. SSL connections are not supported.

The Hub Console launch screen is displayed.

2. Click the Launch button.

The first time (only) that you launch Hub Console from a client machine, Java Web Start downloads application files.

Launching the Hub Console 225


3. Java Web Start will load.

4. The Hub Console login screen is displayed.

5. Enter a user name and password.

Note: If you do not have a user name and password set up, contact Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii).

6. Click OK.

After you have logged in with a valid user name and password, Informatica MDM Hub will prompt you to choose a target database.



The first time you start the Hub Console, you will be prompted to select the Master Database. After you have registered one or more Operational Reference Stores (ORS databases) using the Databases tool, this list will also include any registered databases as well.

The list of databases to which you can connect is determined by your security profile.

• The Master Database stores Informatica MDM Hub environment configuration settings—user accounts, security configuration, ORS registry, message queue settings, and so on. A given Informatica MDM Hub environment can have only one Master Database.

• An Operational Reference Store (ORS) stores the rules for processing the master data, the rules for managing the set of master data objects, along with the processing rules and auxiliary logic used by the Informatica MDM Hub in defining the best version of the truth (BVT). An Informatica MDM Hub configuration can have one or more ORS databases.

7. Select the Master Database or the ORS to which you want to connect.

8. Click Connect.

Note: You can easily change the target database once inside the Hub Console.

The Hub Console is displayed, as shown in the following example.



Note: What you see might differ from this example screen shot.


Post-setup Tasks

Post-setup Tasks

Verify your Informatica MDM Hub installation by completing the following tasks.


1 Register the newly-created ORS database using the Databases tool in the Hub Console.

“Configuring Operational Record Stores and Datasources” in the Informatica MDM Hub Administrator Guide

2 Enable database logging for this ORS using the Enterprise Manager tool in the Hub Console.

Appendix D, “Viewing Configuration Details,” in the Informatica MDM Hub Administrator Guide

3 Register any installed Cleanse Match Servers using the Cleanse Match Server tool in the Hub Console.

“Configuring Data Cleansing” in the Informatica MDM Hub Administrator Guide

4 Run the validation process on the newly-created ORS database using the Metadata Manager tool in the Hub Console. Save a copy of the final validation results in your installation documentation folder.

Informatica MDM Hub Metadata Manager Guide

5 Generate an Environment Report of your current Informatica MDM Hub configuration (Hub Servers, Cleanse Match Servers, the Master Database, ORS databases, and version history) using the Enterprise Manager tool in the Hub Console. Save a copy of the Environment Report in your installation documentation folder.

Appendix D, “Viewing Configuration Details,” in the Informatica MDM Hub Administrator Guide

6 Copy the following log files to the document directory you created in “Create an Installation Documentation Directory” on page 9:

• Hub Console log (console.log)

• Hub Server log (cmxserver.log)• Cleanse Match Server log

(cmxserver.log)• Database log (cmx_debug.log)

“Informatica MDM Hub Log Files” on page 268


Post-setup Tasks

7 Archive your installation documentation directory. If requested, submit the contents of this directory to Informatica Global Customer Support.

“Informatica Global Customer Support” on page xvii



6
Clustering
This chapter explains how to set up clustering when you install Informatica MDM Hub with WebLogic or WebSphere.

Note: Currently, clustering using the Informatica MDM Hub is supported only in WebLogic and WebSphere environment.

Chapter Contents

• Installing the Hub Server into a WebLogic Server Cluster (Unix)

• Installing the Hub Server into a WebSphere Server Cluster (Unix)

• Installing the Hub Server into a WebLogic Server Cluster (Windows)

• Installing the Hub Server into a WebSphere Server Cluster (Windows)

231

Installing the Hub Server into a WebLogic Server Cluster (Unix)


The following instructions apply to installing the Hub Server into a WebLogic Server cluster on Unix. See the documentation on the BEA/WebLogic web site for detailed instructions on setting up the WebLogic Server cluster.


Hub Server installation into a cluster involves the following steps:

Creating a WebLogic Cluster

The steps below provide a high-level overview of the process of setting up your WebLogic cluster. You should refer to your BEA WebLogic documentation for details.1. Create a clustered domain. For details on setting up a clustered domain see Cluster

Implementation procedures.

Create an Admin server (for example, on port 7001) and two managed servers (for example, on port 8001, 8002) and one cluster that includes the managed servers.

2. Start the node manager.

3. Start the Admin server using the startWeblogic.cmd command.


1 Create a WebLogic cluster. “Creating a WebLogic Cluster” on page 232

2 Install the Hub Server on nodes in the cluster.

“Installing the Hub Server on Nodes in the Cluster” on page 233

3 Configure the required services and deploy the Hub Server in the cluster.

“Configuring Services and Deploying the Hub Server” on page 234

4 Deploy the Cleanse Match Server in the cluster.

“Deploying the Cleanse Match Server” on page 235



4. Start the managed servers either through the WebLogic Server console or using startManagedWebLogic.cmd. See the file startManagedWebLogic_readme.txt for instructions on using the script.

5. Open the WebLogic Console connected to the Admin server.

6. Configure the Cluster IP Address. See the Cluster Address section of the BEA/WebLogic setup documentation located on the BEA/WebLogic web site for details. Follow the instructions for creating the cluster address Development and Test Environments, for example: 192.168.1.113:8001, 192.168.1.113:8002.

7. Restart all the managed servers.You can either use the console or stop all of the servers and start them again by repeating Step 4.

For details and to learn more, see your WebLogic documentation.

Installing the Hub Server on Nodes in the Cluster

Install Hub Server on the Admin Server and all nodes of the cluster that the MRM server will be deployed to by running following command:

./hub_install.bin -DSIPERIAN_INSTALL_PREREQ_VALIDATION=false

The path for the Informatica MDM Hub install should be the same on all nodes of the cluster.

Choose between the following methods for installing the Informatica MDM Hub on all of the nodes in the cluster: 1. Run the Hub Server installer on all nodes and click No when prompted to run the

postInstallSetup script to deploy the application.

2. Run the Hub Server installer on the first node of the cluster. Click No when prompted to run the postInstallSetup script to deploy the application. Copy the Hub Server home directory to all nodes in the cluster.

Clustering 233


Configuring Services and Deploying the Hub Server

To configure the services and deploy the Hub Server once the cluster is running:1. Start the Hub Server installer with following command:

./hub_install.bin -DSIPERIAN_INSTALL_PREREQ_VALIDATION=false

2. When asked by the installer 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 when using the production cluster IP address configuration.

cd <infamdm_install_directory>/bin./sip_ant.sh repackage

3. Open the WebLogic Server console and manually create the JMS queue. For more information on how to create JMS queues, see Appendix B, “Manually Configuring Informatica System Message Queues.”

Note: While creating JMS Server for Informatica MDM Hub, make sure to select a Migratable Server as target. For more information on why the JMS Server target should be a migratable server, see “Configuring Migratable Targets for JMS Servers” in the WebLogic documentation.

When configuring the JMS Module, make the target “All servers in the cluster”.

4. Open the WebLogic Server console and manually create the connection pools and data sources for CMX_SYSTEM and ORS databases. Deploy them to the cluster. See “Create the Hub Store” on page 23 in this guide for information about creating these data sources.

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

6. If production Cluster IP address is used, update the cmx.appserver.hostname setting in the cmxserver.properties file on all nodes in the cluster and set it to the cluster IP address.

The MRM Server is now ready to use. The MRM Server can be accessed using either of the nodes in the cluster if the development cluster IP is used or with the cluster name in the production clusters. Once the application is started, the EJB clustering will distribute the requests between the managed servers and manage any fail-over.



Note: When registering new ORSs in the Hub Console, the data sources and connection pools for these ORSs have to be created manually.

Deploying the Cleanse Match Server

To deploy the Cleanse Match Server once the cluster is running:1. Start the Cleanse Match Server install with following command:

./hub_cleanse_install.bin -DSIPERIAN_INSTALL_PREREQ_VALIDATION=false

2. When the installer prompts you for the WebLogic listener port, enter the managed server ports for any node in the cluster if the cluster is setup with the development Cluster IP address.


3. Run following command to repackage the EAR file:

cd <install_home>/bin./sip_ant.sh repackage

4. Manually deploy the MRM Server EAR file through the WebLogic Server console.

5. If production Cluster IP is used update the cmx.appserver.hostname setting in the cmxserver.properties file on all nodes in the cluster and set it to the cluster IP address.

6. When registering new ORSs in Hub Console, the data sources and connection pools for these ORSs have to be created manually in the Hub Server environment.

Clustering 235

Installing the Hub Server into a WebSphere Server Cluster (Unix)


Follow the steps in this section to set up and configure WebSphere with Informatica MDM Hub applications. The following instructions apply to installing the Hub Server and Cleanse Match Server into a WebSphere Server (WAS) cluster.



Before You Install

See the WebSphere Network Install Guide for detailed instructions on installing WebSphere and setting up the WAS cluster.

Installing the Hub Server and Cleanse Match Server Software

Install the Hub Server and Cleanse Match Server on each of the nodes of the cluster servers to which the Informatica MDM Hub will be deployed.


1 Prepare the target environment. “Before You Install” on page 236

2 Install Hub Server and Cleanse Match Server software.

“Installing the Hub Server and Cleanse Match Server Software” on page 236

3 Create a WebLogic cluster. “Creating a WebSphere Cluster” on page 237







1. While installing Hub Server and Cleanse Match Server, the path for the Informatica MDM Hub install should be the same on all nodes of the cluster.

2. When WebSphere server name, SOAP port, and RMI port are requested during installation, provide one of the cluster server's names and its corresponding SOAP and RMI port information.

3. Choose between the following two methods for installing the Informatica MDM Hub on all of the nodes in the cluster:

a. Run the Informatica MDM Hub installers on all nodes and click No when prompted to run the postInstallSetup script to deploy the application.

b. Run the Informatica MDM Hub installers on the first node of the cluster. Click No when prompted to run the postInstallSetup script to deploy the application. Copy the Informatica MDM Hub home directory to all nodes in the cluster if all nodes use the same operating system.

Creating a WebSphere Cluster

To create a WebSphere cluster:1. Start the WebSphere nodes and the WebSphere manager.

2. In the WebSphere admin console, select create Cluster > add Cluster members.

3. Add all the default ports in the virtual host that are associated with cluster members.

4. In the admin console, select Environment > Virtual Hosts > default_host > Host Aliased > new (*:9081, *:9082 and so on)

5. Start the cluster (wait until you see a solid green icon in the console).

For more information on creating clusters, go to the following:

http://publib.boulder.ibm.com/infocenter/wsphelp/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/trun_wlm_member.html

For more information on creating cluster members, go to the following:


6. Make sure the cluster and all cluster servers are running.

Clustering 237



This section describes the steps to configure the services and deploy Hub Server once the cluster is running.1. Copy the Oracle 10.2.0.3 JDBC driver (ojdbc14.jar) to:

WAS61ND_Home/AppServer/lib

2. In the admin console, add the JDBC driver path info into the ORACLE_JDBC_DRIVER_PATH:

Environment > WebSphere Variables > ORACLE_JDBC_DRIVER_PATH

3. Start the Hub Server installation with following command:

./hub_install.bin

4. When prompted for the WebSphere server name, SOAP, and RMI ports, enter one of the cluster server names and its corresponding SOAP and RMI port information.

5. Click No when prompted to run the postInstallSetup script to deploy the application.

6. After the installation, open <install_home>/resources/cmxserver.properties and add all of the cluster server's machine names in cmx.appserver.hostname and RMI ports in cmx.appserver.rmi.port, with the property information separated by commas.

For example, if the cluster has four servers which are running in host1, host2, host3, host4 using RMI ports 2812, 2813, 2814 and 2815 respectively, then the cmx.appserver.hostname and cmx.appserver.rmi.port property in <install_home>/resources/cmxserver.properties would look like this:

cmx.appserver.rmi.port=2812,2813,2814,2815cmx.appserver.hostname=host1,host2,host3,host4

where <install_home> is the home of your Hub Server installation.

Make sure there is no space or tab between port numbers. These port numbers should be separated only by a comma, and host name and port numbers should be in the same order. For example, first server's host name and port number should be host1 and 2812; second server's host name and port number should be host2 and 2813 and so on.



7. Run the following command to repackage the EAR file:


where <install_home> is the home of your Hub Server installation.

8. Open the WebSphere console and manually create a JMS Queue.

For more information on how to create JMS Queue, see Appendix B, “Manually Configuring Informatica System Message Queues.” Designate the cluster member as the target for JMS Bus, Queue, and Activation. This step needs to be done for every member/server in the cluster.

9. Open WebSphere console and manually create the connection pools and data sources for CMX_SYSTEM and ORSs and deploy them to the cluster.

See Appendix B, “Manually Configuring Informatica System Message Queues” for more information.

10. Manually deploy the Hub Server EAR to the cluster through the WebSphere console.

a. In the WebSphere admin console, select Applications > Enterprise Applications, and click Install.

b. Enter the local path for the siperian-mrm.ear and click Next.

c. Use the default settings and click Next.

d. Map modules to servers, select the cluster name you want to deploy, check both JARs, click Apply. Click Next.

e. Choose the default method and the authentication data = cmx_system, and check siperian-server.jar. Click Apply.

Map resource references to resources, browse target resource JNDI name for siperian-server.jar, and select and apply siperian.mrm.jms.xaconnectionfactory from the list. Click Next.

11. Verify the information in the summary and click Next.

12. Save the change.

13. Stop the following: cluster, manager, and node. Restart them in the following order: node, manager, cluster.

Clustering 239


The MRM Server is ready to use. MRM Server can be accessed using any of the nodes in the cluster if host aliases are set. MRM Server can also be accessed through IBM HTTP Server if cluster is set for load balancing.



Here are the steps to deploy the Cleanse Match Server once the cluster is running:1. Start the Cleanse Match Server installer with following command:


2. When asked by the installer for the WebSphere server name and SOAP port, enter one of the cluster server's names and its corresponding SOAP port information.



where <install_home> is the home of your Cleanse Match Server installation.

4. Manually deploy the Cleanse Match Server EAR to the cluster through the WebSphere Admin console.


Installing the Hub Server into a WebLogic Server Cluster (Windows)


The following instructions apply to installing the Hub Server into a WebLogic Server cluster. See the documentation on the BEA/WebLogic website for detailed instructions on setting up the WebLogic Server cluster.

Note: This example assumes that an IP solution is in place. If an IP solution is not being used, the syntax in the cmxserver.properties will need to have servers and ports listed separately.



Creating a WebLogic Cluster

The steps below provide a high-level overview of the process of setting up your WebLogic cluster. You should refer to your BEA WebLogic documentation for details.1. Create a clustered domain. For details on setting up a clustered domain see Cluster

Implementation procedures.

Create an Admin server (for example, on port 7001) and two managed servers (for example, on port 8001, 8002) and one cluster that includes the managed servers.

2. Start the node manager.


1 Create a WebLogic cluster. “Creating a WebLogic Cluster” on page 241

2 Install the Hub Server software on nodes in the cluster.

“Installing the Hub Server on Nodes in the Cluster” on page 242





Clustering 241


3. Start the Admin server using the startWeblogic.cmd command.

4. Start the managed servers either through the WebLogic Server console or using startManagedWebLogic.cmd. See the file startManagedWebLogic_readme.txt for instructions on using the script.

5. Open the WebLogic Console connected to the Admin server.

6. Configure the Cluster IP Address. See the Cluster Address section of the BEA/WebLogic setup documentation located on the BEA/WebLogic website for details. Follow the instructions for creating the cluster address Development and Test Environments, for example: 192.168.1.113:8001, 192.168.1.113:8002.

7. Restart all the managed servers.You can either use the console or stop all of the servers and start them again by repeating Step 4.

For details and to learn more, see your WebLogic documentation.

Installing the Hub Server on Nodes in the Cluster

Install the Hub Server on the Admin Server and all nodes of the cluster that MRM server will be deployed to by running following command:

hub_install.exe -DSIPERIAN_INSTALL_PREREQ_VALIDATION=false

The path for the Hub Server install should be the same on all nodes of the cluster.

Choose between the following methods for installing the Informatica MDM Hub on all of the nodes in the cluster: 1. Run the Hub Server installer on all nodes and click No when prompted to run the

postInstallSetup script to deploy the application.

2. Run theHub Server installer on the first node of the cluster. Click No when prompted to run the postInstallSetup script to deploy the application. Copy the Hub Server root installation directory to all nodes in the cluster.


To configure the services and deploy the Hub Server once the cluster is running:1. Start the Hub Server installer with following command:



hub_install.exe -DSIPERIAN_INSTALL_PREREQ_VALIDATION=false

2. When asked by the installer 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.


3. If a production Cluster IP address is used, update the cmx.appserver.hostname setting in the cmxserver.properties file on all nodes in the cluster and set it to the cluster IP address.


cd <install_Install_Dir>\binsip_ant.bat repackage

5. Open the WebLogic Server console and manually create the JMS queue. For more information on how to create JMS queues, see Appendix B, “Manually Configuring Informatica System Message Queues.”

While creating JMS Server for Informatica MDM Hub, make sure to select a Migratable Server as target. For more information on why the JMS Server target should be a migratable server, see “Configuring Migratable Targets for JMS Servers” in the BEA/WebLogic documentation.

When configuring the JMS Module, make the target “All servers in the cluster”.

6. Open the WebLogic Server console and manually create the connection pools and data sources for CMX_SYSTEM and ORSs. Deploy them to the cluster. See “Create the Hub Store” on page 23 for information about creating these data sources.

7. Manually deploy the MRM Server EAR through the WebLogic Server console.

The MRM Server is now ready to use. The MRM Server can be accessed using either of the nodes in the cluster if the development cluster IP is used or with the cluster name in the production clusters. Once the application is started, the EJB clustering will distribute the requests between the managed servers and manage any failover.

Note: When registering new ORSs in Hub Console, the data sources and connection pools for these ORSs have to be created manually.

Clustering 243



To deploy the Cleanse Match Server once the cluster is running:1. Start the Cleanse Match Server installer with following command:

hub_cleanse_install.exe -DSIPERIAN_INSTALL_PREREQ_VALIDATION=false

2. When the installer prompts you for the WebLogic listener port, enter the managed server ports for any node in the cluster if the cluster is setup with the development Cluster IP address.


3. If a production Cluster IP is used update the cmx.appserver.hostname setting in the cmxserver.properties file on all nodes in the cluster and set it to the cluster IP address.


cd <install_Install_Dir>\binsip_ant.bat repackage

5. Manually deploy the MRM Server EAR file through the WebLogic Server console.

6. When registering new ORSs in Hub Console, the data sources and connection pools for these ORSs have to be created manually in the WebLogic Server console.


Installing the Hub Server into a WebSphere Server Cluster (Windows)


Follow the steps in this section to set up and configure WebSphere with Informatica MDM Hub applications. The following instructions apply to installing the Hub Server and Cleanse Match Server into a WebSphere Server (WAS) cluster.



Before You Install

See the WebSphere Network Install Guide for detailed instructions on installing WebSphere and setting up the WAS cluster.

Installing the Hub Server and Cleanse Match Server Software

Install the Hub Server and Cleanse Match Server on each of the nodes of the cluster servers to which the Informatica MDM Hub will be deployed.


1 Prepare the target environment. “Before You Install” on page 245

2 Install Hub Server and Cleanse Match Server software.

“Installing the Hub Server and Cleanse Match Server Software” on page 245

3 Create a WebLogic cluster. “Creating a WebSphere Cluster” on page 246





Clustering 245


1. While installing Hub Server and Cleanse Match Server, the path for the Informatica MDM Hub install should be the same on all nodes of the cluster.

2. When WebSphere server name, SOAP port, and RMI port are requested during installation, provide one of the cluster server's names and its corresponding SOAP and RMI port information.

3. Choose between the following two methods for installing the Informatica MDM Hub on all of the nodes in the cluster:

a. Run the Informatica MDM Hub installers on all nodes and click No when prompted to run the postInstallSetup script to deploy the application.

b. Run the Informatica MDM Hub installers on the first node of the cluster. Click No when prompted to run the postInstallSetup script to deploy the application. Copy the Informatica MDM Hub root installation directory to all nodes in the cluster if all nodes use the same operating system.

Creating a WebSphere Cluster

To create a WebSphere cluster:1. Start the WebSphere nodes and the WebSphere manager.

2. In the WebSphere admin console, select create Cluster > add Cluster members.

3. Add all the default ports in the virtual host that are associated with cluster members.

4. In the admin console, select Environment > Virtual Hosts > default_host > Host Aliased > new (*:9081, *:9082 and so on)

5. Start the cluster (wait until you see a solid green icon in the console).

For more information on creating clusters, go to the following:


For more information on creating cluster members, go to the following:


6. Make sure the cluster and all cluster servers are running.




This section describes the steps to configure the services and deploy the Hub Server once the cluster is running.1. Copy the Oracle 10.2.0.4 JDBC driver (ojdbc5.jar) to:

<WebSphere_install_dir>\AppServer\

2. In the admin console, add the JDBC driver path (it should be <WebSphere_install_dir>\AppServer\lib) into the ORACLE_JDBC_DRIVER_PATH:

Environment > WebSphere Variables > <ORACLE_JDBC_DRIVER_PATH>

3. Start the Hub Server installer with following command:

hub_install.exe

4. When prompted for the WebSphere server name, SOAP, and RMI ports, enter one of the cluster server names and its corresponding SOAP and RMI port information.

5. Click No when prompted to run the postInstallSetup script to deploy the application.

6. After the installation, open <server_install_dir>\resources\cmxserver.properties and add all of the cluster server's machine names in cmx.appserver.hostname and RMI ports in cmx.appserver.rmi.port, with the property information separated by commas.

For example, if the cluster has four servers which are running in host1, host2, host3, host4 using RMI ports 2812, 2813, 2814 and 2815 respectively, then the cmx.appserver.hostname and cmx.appserver.rmi.port property in <server_install_dir>/resources/cmxserver.properties would look like this:

cmx.appserver.rmi.port=2812,2813,2814,2815cmx.appserver.hostname=host1,host2,host3,host4

Make sure there is no space or tab between port numbers. These port numbers should be separated only by a comma, and host name and port numbers should be in the same order. For example, first server's host name and port number should be host1 and 2812; second server's host name and port number should be host2 and 2813 and so on.

7. Run the following command to repackage the EAR file:

Clustering 247


cd <server_install_dir>/bin sip_ant.bat repackage

8. Open the WebSphere console and manually create a JMS Queue. Designate the cluster member as the target for JMS Bus, Queue, and Activation. This step needs to be done for every member/server in the cluster. For more information on how to create a JMS Queue, see Appendix B, “Manually Configuring Informatica System Message Queues.”

9. Open WebSphere console and manually create the connection pools and data sources for CMX_SYSTEM and ORSs and deploy them to the cluster.

See Appendix B, “Manually Configuring Informatica System Message Queues” for more information.

10. Manually deploy the Hub Server EAR to the cluster through the WebSphere console.

a. In the WebSphere admin console, select Applications > Enterprise Applications, and click Install.

b. Enter the local path for the siperian-mrm.ear and click Next.

c. Use the default settings and click Next.

d. Map modules to servers, select the cluster name you want to deploy, check both JARs, click Apply. Click Next.

e. Choose the default method and the authentication data = cmx_system, and check siperian-server.jar. Click Apply.

Map resource references to resources, browse target resource JNDI name for siperian-server.jar, and select and apply siperian.mrm.jms.xaconnectionfactory from the list. Click Next.

11. Verify the information in the summary and click Next.

12. Save the change.

13. Stop the following: cluster, manager, and node. Restart them in the following order: node, manager, cluster.

The MRM Server is ready to use. MRM Server can be accessed using any of the nodes in the cluster if host aliases are set. MRM Server can also be accessed through IBM HTTP Server if cluster is set for load balancing.





Here are the steps to deploy the Cleanse Match Server once the cluster is running:1. Start the Cleanse Match Server installer with following command:

hub_cleanse_install.exe

2. When asked by the installer for the WebSphere server name and SOAP port, enter one of the cluster server's names and its corresponding SOAP port information.


cd <Cleanse_Install_Directory>\binsip_ant.bat repackage

4. Manually deploy the Cleanse Match Server EAR to the cluster through the WebSphere Admin console.

Clustering 249

7
Uninstalling Informatica MDM Hub
This chapter describes how to uninstall your Informatica MDM Hub implementation.

Chapter Contents

• Uninstalling Informatica MDM Hub (JBoss / Unix)

• Uninstalling Informatica MDM Hub (WebLogic / Unix)

• Uninstalling Informatica MDM Hub (WebSphere / Unix)

• Uninstalling Informatica MDM Hub (JBoss / Windows)

• Uninstalling Informatica MDM Hub (WebLogic / Windows)

• Uninstalling Informatica MDM Hub (WebSphere / Windows)

251

Uninstalling Informatica MDM Hub (JBoss / Unix)


Uninstalling Informatica MDM Hub involves the following steps:

Uninstalling the Cleanse Match Server

This section describes how to remove a Cleanse Match Server installation from your system.

Note: If you have more than one Cleanse Match Server running, you must perform these steps for each Cleanse Match Server you want to uninstall.

Removing the Cleanse Match Server

To uninstall a Cleanse Match Server:1. If the Cleanse Match Server is running, stop it by stopping the application server.

2. Navigate to the following directory:

<infamdm_install_directory>/hub/cleanse/UninstallerData

3. Run Uninstall_Informatica_MDM_Hub_Cleanse_Match_Server.

The Uninstall introduction screen is displayed.

4. Click Uninstall to begin the uninstall process.

While the process is underway, the Please Wait screen is displayed.

When the process is done, the Uninstall Complete screen is displayed.

5. Click Done.


1 Remove each instance of the Cleanse Match Server software.

“Uninstalling the Cleanse Match Server” on page 252

2 Remove the Hub Server software. “Uninstalling the Hub Server” on page 253

3 Remove the Hub Store (databases and users) from Oracle.

“drop user <username> cascade;” on page 265



Note: The installation process begins by undeploying any pre-existing Cleanse Match Servers. If the undeployment process fails, you will need to undeploy manually according to the instructions in “Manually Undeploying the Cleanse Match Server” on page 253.

Manually Undeploying the Cleanse Match Server

If for some reason you need to manually undeploy the Cleanse Match Server in the JBoss application server environment, delete the siperian-mrm-cleanse.ear from the <JBoss_install_dir>/server/<configuration_name>/deploy directory.

Note: Restart the JBoss application server if the JBoss auto-deploy process does not remove the applications. For more information, refer to your JBoss administration documentation.

Uninstalling the Hub Server

This section describes how to remove a Hub Server installation from your system.

Removing the Hub Server

To uninstall Hub Server:1. Navigate to the <infamdm_install_

directory>/hub/server/UninstallerData directory and execute Uninstall_Informatica_MDM_Hub_Server.



When the process is underway, the Please Wait screen is displayed.


3. Click Done.

Important: When uninstalling the Hub Server, check for the presence of the following files and delete them if they were not deleted from the <JBoss_

Uninstalling Informatica MDM Hub 253

Uninstalling Informatica MDM Hub (WebLogic / Unix)

Home>/server/<configuration_name>/deploy folder. These files must be removed before you can upgrade to the current version of Informatica MDM Hub:

siperian-mrm.earsiperian-mrm-ds.xmlsiperian-mrm-cleanse.ear

Manually Undeploying the Hub Server

The uninstall process should automatically do the following actions for you:• Delete siperian-mrm.ear and siperian-mrm-ds.xml from the <JBoss_

install_dir>/server/<configuration_name>/deploy directory.

• Remove the following files from server/default/deploy/messaging if they exist. These files contain the JMS configuration queue.

• siperian-jms-ds.xml

• siperian-destination-service.xml























5. Click Done.



If for some reason you need to manually undeploy the Cleanse Match Server in the WebLogic application server environment, uninstall the siperian-mrm-cleanse.ear application using the WebLogic Server Administration Console. Make sure that the process finishes completely. For more information, see your WebLogic documentation.


Uninstalling Informatica MDM Hub (WebSphere / Unix)










3. Click Done.


The install process should automatically uninstall the siperian-mrm.ear application using the WebLogic Server Administration Console.























5. Click Done.



If for some reason you need to manually undeploy the Cleanse Match Server in the WebSphere application server environment, uninstall the siperian-mrm-cleanse.ear application using the WebSphere Application Server Administrative Console. Make sure that the process finishes completely. For more information, refer to your WebSphere documentation


Uninstalling Informatica MDM Hub (JBoss / Windows)










3. Click Done.


The install process should automatically undeploy the siperian-mrm.ear application using the WebSphere Application Server Administrative Console.
















• Click the Start button and select Programs > Infamdm > Hub > Cleanse > Uninstall Informatica MDM Hub Cleanse Match Server, or

• Navigate to the <infamdm_install_directory>\hub\cleanse\UninstallerData directory and double-click Uninstall Informatica MDM Hub Cleanse Match Server.exe.


3. Click Uninstall to begin the uninstallation.


The Uninstall Complete screen is displayed.

4. Click Done.


For JBoss, delete the siperian-mrm-cleanse.ear file from the server\<configuration_name>\deploy directory.

Note: Restart the JBoss application server if the JBoss auto-deploy process does not remove the applications. For more information, refer to your JBoss Administration documentation.






To uninstall the Hub Server:1. Do one of the following:

• Click the Start button and select Programs > Infamdm > Hub > Server > Uninstall Informatica MDM Hub Server, or

• Navigate to the <infamdm_install_directory>\hub\server\UninstallerData directory and double-click Uninstall Informatica MDM Hub Server.exe.




3. Click Done.

You must restart the application server after you uninstall.


If you are using the JBoss application server, delete siperian-mrm.ear and siperian-mrm-ds.xml from the <JBoss_install_dir>/server/<configuration_name>/deploy directory.

Also remove the following files from server/<configuration_name>/deploy/messaging if they exist. These files contain the JMS configuration queue.• siperian-jms-ds.xml

• siperian-destination-service.xml

Note: Restart the server if the auto-deploy process of JBoss doesn’t remove the applications. For more information, see your JBoss documentation.


Uninstalling Informatica MDM Hub (WebLogic / Windows)








• Click the Start button and select Programs > Infamdm > Hub > Cleanse > Uninstall Informatica MDM Hub Cleanse Match Server, or














4. Click Done.


For WebLogic, uninstall the siperian-mrm-cleanse.ear application using the WebLogic Server Administration Console. Make sure that the process finishes completely. For more information, refer to your WebLogic documentation




To uninstall the Hub Server:1. Click the Start button and select Programs > Infamdm > Hub > Server >

Uninstall Informatica Hub Server

Or navigate to the <infamdm_install_directory>\hub\server\UninstallerData directory and double-click Uninstall Informatica MDM Hub Server.exe.




3. Click Done.



For WebLogic, uninstall the siperian-mrm.ear application using the WebLogic Server Administration Console. Make sure that the process finishes completely. For more information, see your WebLogic documentation.


Uninstalling Informatica MDM Hub (WebSphere / Windows)

Uninstalling Informatica MDM Hub (WebSphere / Windows)







• Click the Start button and select Programs > Infamdm> Hub > Cleanse > Uninstall Informatica MDM Hub Cleanse Match Server, or













Uninstalling the Hub Store from Oracle

4. Click Done.


For WebSphere, uninstall the siperian-mrm-cleanse.ear application from the WebSphere Application Server Administrative Console. Make sure that the process finishes completely. See your WebSphere documentation for more information.


This section describes how to uninstall the Hub Store for all supported platforms and application server environments.

Note: File names and directories in this section may vary slightly depending on what type of installation you are performing.

Database Objects to Drop

When uninstalling the Hub Store, you must:• drop any Hub Store database schemas (Master Database and any ORS databases)

that you created by running the setup.sql and/or setup_ors.sql scripts

• remove all user logins for those database schemas

For example, if you created CMX_SYSTEM (Master Database) and CMX_ORS (ORS database) using setup.sql, and CMX_ORS2 (ORS database) using setup_ors.sql, you must drop the following objects:

Oracle Object Type To Be Dropped

Database schema CMX_SYSTEM, CMX_ORS, and CMX_ORS2

User CMX, CMX_SYSTEM, CMX_ORS, CMX_ORS2, and any users you created that access those schemas



Dropping Hub Store Databases

Note: You must have Oracle DBA privileges to complete the instructions in this section.

To drop Hub Store databases:1. Log into Hub Console according to the instructions in “Starting the Hub Console”

on page 225.

2. Start the Databases tool according to the instructions in the Informatica MDM Hub Administrator Guide.

3. Acquire a write lock.

4. In the list of databases, select the ORS database(s) that you want to unregister, and then click the button.

Note: If you are running WebLogic, enter the WebLogic user name and password when prompted.

The Databases tool prompts you to confirm unregistering the ORS.

5. Click Yes.

6. Connect to the Oracle instance using SQL*PLUS, using a login with DBA privileges.

7. For each of the schemas listed in “Database Objects to Drop” on page 264, issue the following command (dropping the user with the CASCADE option also drops the associated database):

drop user <username> cascade;

8. For the Master Database, issue the following command (dropping the user with the CASCADE option also drops the associated database):

drop user <username> cascade;





To uninstall the Hub Server:1. Do one of the following:

• Click the Start button and select Programs > Infamdm > Hub > Server > Uninstall Informatica MDM Hub Server, or

• Navigate to the infamdm_install_directory\hub\server\UninstallerData directory and double-click Uninstall Informatica MDM Hub Server.exe.



3. Click Done.



If for some reason you need to manually undeploy the Hub Server in the WebSphere environment, uninstall the siperian-mrm.ear application using the WebSphere Application Server Administrative Console. Make sure that the process finishes completely. For more information, see your WebSphere documentation.


8
Troubleshooting
This chapter explains how to troubleshoot your installation and make changes to your application and database servers after running the installation process.

Chapter Contents

• Informatica MDM Hub Log Files

• Bypassing Prerequisite Installation

• Updating Parameters After Installation

• Checking the Hub and Cleanse Match Server Silent Install

• MATCH Process Error: VerifyNeedToStrip

• Inaccurate Start/Stop Timestamp for ORS

• major.minor Version Errors When Loading Cleanse Match Server

• Low Cleanse/Match Application Server Performance

• Troubleshooting (JBoss / Unix)

• Troubleshooting (WebLogic / Unix)

• Troubleshooting (WebSphere / Unix)

• Troubleshooting (JBoss / Windows)

• Troubleshooting (WebLogic / Windows)

• Troubleshooting (WebSphere / Windows)

267

Informatica MDM Hub Log Files


This section describes the Informatica MDM Hub log files that you can use for troubleshooting your installation.

Informatica MDM Hub Log Files (Unix)

This section describes the Informatica MDM Hub log files on the Unix platform.

About the Informatica MDM Hub Log Files

Informatica MDM Hub creates the following log files:• console.log

• cmxserver.log (for Master Reference Manager)

• cmx_debug.log

console.log

This log file is created in c:/Documents and Settings/<user_home>/siperian/console.log. It contains the log messages from the Hub Console. Any errors that occur when communicating with the application server or error messages from the application server or console error messages are logged to this file. By default console.log is ON and created.

This log file is a rolling log file. Once it reaches 5 MB, it is copied to console.log.1 and resumes. Hub Server does this indefinitely, potentially creating very many log files. It is a good idea to periodically delete the old files, or transfer them to some other storage.

The console.log file is created on the local machine from which you launch and use the Hub Console.

Note: The PATH given for the console log is a Windows path, not a Unix one, as the console.log file is written on the local machine on which you have launched Hub Console.



cmxserver.log (for Master Reference Manager)

This is the log file for the application server. During installation, if you choose the default location, cmxserver.log appears in <infamdm_install_directory>/hub/server/logs. In general the file location is <infamdm_install_directory>/hub/server/logs.

This log file contains all of the logging and debugging information from the application server. By default cmxserver.log is ON and created. This log file is a rolling log file and once it reaches 5MB, it is copied to cmxserver.log.1 and resumes. Hub Server does this indefinitely, potentially creating very many files. It is a good idea to periodically delete the old files, or transfer them to some other storage.

Note: If you are using JBoss for Informatica MDM Hub, the cmxserver log is in <infamdm_install_directory>/hub/server/logs/cmxserver.log by default. Also, for JBoss, the cmxserver.log contains the log information for both the Hub Server and Cleanse Match Server.

cmxserver.log (for Cleanse Match Server)

This log file is for the CLEANSE, TOKENIZATION, and SIMULATION functions. It is located in the <cleanse_install_directory>/hub/cleanse/logs directory. This log file contains all of the debugging and error messages for the Cleanse process (Landing >Staging). By default cmxserver.log is ON. This log file is a rolling log file and once it reaches 5MB, it is copied to cmxserver.log.1 and resumes.

cmx_debug.log

This log file is for the database stored procedures. This log file contains all of the logging information for the PUT, GET, GETLIST, MATCH, LOAD, MERGE, and AUTOMERGE stored procedures. By default cmx_debug.log is OFF, as there is some performance overhead associated with logging. To set debug logging on, see “Enabling Debug Logging” on page 270.

The Enterprise Manager allows you to change the name of the debug file. See more about the Enterprise Manager in the Informatica MDM Hub Administrator Guide.

Troubleshooting 269


Enabling Debug Logging

By default, debug logging is off, as there is some performance overhead associated with logging. For more information about the debug log, see the instructions in the Informatica MDM Hub Administrator Guide for the Enterprise Manager tool in the Hub Console.

To enable debug logging:1. On the database server machine, add the utl_file_dir to your Oracle SPFile,

specifying a debug log directory that is accessible and writable by Oracle. There are two ways in which you can set the value for utl_file_dir:

• Start SQL*Plus and run the following commands:

connect sys/password as sysdba

alter system set utl_file_dir='<debug_log_path>' scope=spfile sid='sid_name'

Restart the Oracle instance and run the following command:

show parameter utl_file_dir

You should see the utl_file_dir setting you specified.

• Open the Oracle Enterprise Manager URL for your database instance:

http://<database_machine>:1158/em. Log into the system as sysdba.

Go to Database Configuration > All Initialization Parameters > Select the SPFile tab > enter the value for utl_file_dir, save changes, and restart the Oracle instance.

2. Use the Enterprise Manager tool in the Hub Console to enable debugging and configure log file settings in your ORS database according to the instructions in the Informatica MDM Hub Administrator Guide.

3. Test debug by running the following code in SQL*PLUS:

exec CMXLB.debug_print ('Testing debug - should appear in file');

4. Go to the debug log directory and open a file named cmx_debug.

If your configuration change succeeded, this file should contain the test message:

Testing debug - should appear in file



Changing the Log File Locations

Do not edit the cmxserver.properties file to change the location of the logs.• For Informatica MDM Hub on JBoss, edit the following file:

<JBoss_install_dir>/server/<configuration_name>/conf/log4j.xml

• For Informatica MDM Hub on WebSphere, edit the following file:

<server_install_dir>/conf/log4j.xml

• For Cleanse Match Server, edit the following file:

<cleanse_install_directory>/conf/log4j.xml

Maintaining the Log Files

The rolling nature of all Informatica MDM Hub log files means that you must periodically perform some housekeeping, either deleting old logs or moving them to permanent storage to keep them from becoming too numerous and taking up too much space.

Informatica MDM Hub Log Files (Windows)

This section describes the Informatica MDM Hub log files on the Windows platform.

About the Informatica MDM Hub Log Files

Informatica MDM Hub creates the following log files:• console.log

• cmxserver.log (for Master Reference Manager)

• cmxserver.log (for Cleanse Match Server)

• cmxserver.log (for Cleanse Match Server)

Note: Some files include password information.

Troubleshooting 271


console.log

This file is created in C:\Documents and Settings\<user_Install_Dir>\siperian\console.log It contains the messages from the Hub Console. Any errors that occur when communicating with the application server or error messages from the application server or console error messages are logged to this file.

By default cmxconsole.log is ON and created. It is a good idea to periodically delete the old files, or transfer them to some other storage.

cmxserver.log (for Master Reference Manager)

This is the log file for the application server. During installation, if you choose the default location, cmxserver.log appears in C:\<infamdm_install_directory>\hub\server\logs. In general, the file location is <infamdm_install_directory>\hub\server\logs.

This file contains all of the logging and debugging information from the application server. By default cmxserver.log is ON and created. This file is a rolling file and once it reaches 5MB, it is copied to cmxserver.log.1 and resumes. Hub Server does this indefinitely, potentially creating very many files. It is a good idea to periodically delete the old files, or transfer them to some other storage.

Note: If you are using JBoss for Informatica MDM Hub, the cmxserver.log is in <infamdm_install_directory>\logs\cmxserver.log by default. Also, for JBoss, the cmxserver.log contains the information for both the Hub Server and Cleanse Match Server.

cmxserver.log (for Cleanse Match Server)

This file is for the CLEANSE\TOKENIZATION\SIMULATION. It is located in the install directory <infamdm_install_directory>\hub\cleanse\logs. This file contains all of the debugging and error messages for the Cleanse process (Landing > Staging). By default cmxserver.log is ON. This file is a rolling file and once it reaches 5MB, it is copied to cmxserver.log.1 and resumes.



cmx_debug.log

The cmx_debug.log file is for the database stored procedures. It contains all of the logging information for the PUT, GET, GETLIST, MATCH, LOAD, MERGE, and AUTOMERGE stored procedures. By default cmx_debug.log is OFF. To set debug logging on, see “Enabling Debug Logging” on page 273.

The Enterprise Manager allows you to change the name of the debug file. See more about the Enterprise Manager in the Informatica MDM Hub Administrator Guide.

Note: If debug logging is enabled, make sure that the log file size multiplied by the maximum number of database log files does not exceed the storage available, or the maximum file size of your operating system.

Enabling Debug Logging

By default, debug logging is off, as there is some performance overhead associated with logging. For more information about the debug log, see the instructions in the Informatica MDM Hub Administrator Guide for the Enterprise Manager tool in the Hub Console.

To enable debug logging:1. On the database server machine, add the utl_file_dir to your Oracle SPFile,

specifying a debug log directory that is accessible and writable by Oracle. There are two ways in which you can set the value for utl_file_dir:

• Start SQL*Plus and run the following commands:

connect sys/password as sysdba

alter system set utl_file_dir='<debug_log_path>' scope=spfile sid='sid_name'

Restart the Oracle instance and run the following command:

show parameter utl_file_dir

You should see the utl_file_dir setting you specified.

• Open the Oracle Enterprise Manager URL for your database instance: http://<database_machine>:1158/em. Log into the system as sysdba.

Troubleshooting 273


Go to Database Configuration > All Initialization Parameters > Select the SPFile tab > enter the value for utl_file_dir, save changes, and restart the Oracle instance.

2. Use the Enterprise Manager tool in the Hub Console to enable debugging and configure log file settings in your ORS database according to the instructions in the Informatica MDM Hub Administrator Guide.

3. Test the debug log by running the following code in SQL*PLUS:

exec CMXLB.debug_print ('Testing debug - should appear in file');

4. Go to the debug log directory (such as c:\cmx_log\), open a file named cmx_debug, and verify that debug logging is enabled. If your configuration change succeeded, this file should contain the test message:

Testing debug - should appear in file

Setting the Location of the Log Files

Important: DO NOT edit the cmxserver.properties file to change the location of the logs.

where <infamdm_install_directory> is the directory into which you installed Hub Server and Cleanse Match Server.

Component Configuration file to edit to set the location of the logs

JBoss <JBoss_install_dir>\server\<configuration_name>\conf\log4j.xml

Hub Server <infamdm_install_directory>\conf\log4j.xml

Cleanse Match Server <infamdm_install_directory>\conf\log4j.xml



ORS Debug Log Setup

To set the ORS debug logging in Oracle, instead of using UTL_FILE_DIR, you can use a directory object by completing the following steps:1. Create a directory on your file system (example: /app/infamdm/debug_log)

where the debug log will be stored.

2. Grant the Oracle user (usually the DBA user) read and write access to this directory.

3. Log into Oracle as the Oracle/DBA user.

4. Create a directory object (such as SIP_DEBUG_LOG).

CREATE OR REPLACE DIRECTORY sip_debug_log AS '/app/infamdm/debug_log'

5. Grant the following privileges to the directory object you just created.

To grant privileges to a PUBLIC user, use the following command:

GRANT READ, WRITE ON DIRECTORY sip_debug_log TO PUBLIC;

If you are not granting privileges to the PUBLIC user, use the following steps to grant each ORS to the directory object.

GRANT READ, WRITE ON DIRECTORY sip_debug_log TO <ORS_USER_ID1>;GRANT READ, WRITE ON DIRECTORY sip_debug_log TO <ORS_USER_ID2>;GRANT READ, WRITE ON DIRECTORY sip_debug_log TO <ORS_USER_ID3>;


UPDATE C_REPOS_DB_RELEASE SET DEBUG_FILE_PATH = 'SIP_DEBUG_LOG', DEBUG_FILE_NAME = 'cmx_debug.log', DEBUG_IND = 1;

7. Log out of Oracle, then log in again.

8. Test your work by issuing the following command:

EXEC CMXLB.DEBUG_PRINT('Test logging')

9. Check the log file for the following entry: Test logging.

Troubleshooting 275

Bypassing Prerequisite Installation

Bypassing Prerequisite InstallationTo bypass the prerequisite validation in the installation, you can add the following parameter to the install command:

-DSIPERIAN_INSTALL_PREREQ_VALIDATION=false

Updating Parameters After Installation

This section describes how to update Hub Server and Cleanse Match Server parameters after installation.

Updating Hub Server Parameters After Installation

If the environment changes or parameters were entered incorrectly during the installation process, you can manually correct the information after you run the installation.

The postInstallSetup script undeploys your current application (if there is one), repackages your application with the new information, configures your message queues, installs or recreates your datasource and deploys the newly packaged application to your application server.

Note: For more information on running postInstallSetup, see “PostInstallSetup” on page 45.

For instructions on specific application servers and platforms, see the following topics:• “Changing the Hub Server Parameters (JBoss/Unix)” on page 289

• “Changing the Hub Server Parameters (WebLogic/Unix)” on page 292

• “Changing the Hub Server Parameters (WebSphere/Unix)” on page 301

• “Changing the Hub Server Parameters (JBoss/Windows)” on page 306

• “Changing the Hub Server Parameters (WebLogic/Windows)” on page 309

• “Changing the Hub Server Parameters (WebSphere/Windows)” on page 317


Updating Parameters After Installation

Updating Cleanse Match Server Parameters After Installation

If the environment changes or parameters were entered incorrectly during the installation process, you can manually correct the information after you run the installation.

For instructions, see:• “Changing the Cleanse Match Server Parameters (WebLogic/Unix)” on page 295

• “Changing the Cleanse Match Server Parameters (WebSphere/Unix)” on page 302

• “Changing the Cleanse Match Server Parameters (WebSphere/Unix)” on page 302

• “Changing the Cleanse Match Server Parameters (WebLogic/Windows)” on page 311

• “Changing the Cleanse Match Server Parameters (WebLogic/Windows)” on page 311

The postInstallSetup script is used to use manually repackage the application and redeploy it on your application. It undeploys your current application (if there is one), repackages your application with the new information, configures your message queues, installs or recreates your datasource and deploys the newly packaged application to your application server. For more information on running postInstallSetup, see “PostInstallSetup” on page 45.

Troubleshooting 277

Checking the Hub and Cleanse Match Server Silent Install


This section describes how to confirm that your silent install was successful. A failed silent install could be due to many factors, including incorrect information in the silent property file (such as the incorrect application-server installation paths, or the fact that the file contains too many port numbers). To verify that your silent install succeeded, you can check files for entries related to the silent install, and folders for files related to the silent install.

Checking the Hub Server and Cleanse Match Server Silent Install (Unix)

This section applies to checking silent installs in the Unix environment.

Checking the Hub Server Silent Install

The following tables list the files or folders you should check when you perform a silent Hub Server install.

Location Check For

<server_install_dir>/logs postInstallSetup.log: Check for any ERROR in the log.

<server_install_dir>/bin/build.properties where the appserver is WebLogic

Database credentials:

Look for the following properties and make sure their values are correct. Example values:

masterdatabase.type=ORACLE

masterdatabase.server=mdb_server

masterdatabase.databasename=cmx_system

masterdatabase.jdbc.driverclassname=oracle.jdbc.xa.client.OracleXADataSource

masterdatabase.jdbc.jndiname=jdbc/siperian-cmx_system-ds

masterdatabase.jdbc.url=jdbc:oracle:thin:@mdb_server:1521:orcl

masterdatabase.user=cmx



<server_install_dir>/bin/build.properties where the appserver is WebSphere

Database credentials:




masterdatabase.port=1521

masterdatabase.dbname=orcl

masterdatabase.schemaname=cmx_system


<server_install_dir>/conf/siperian-mrm-ds.xml where the appserver is JBoss.

Database credentials


<xa-datasource-property name="URL">jdbc:oracle:thin:@mdb_server:1521:orcl</xa-datasource-property>

<xa-datasource-property name="User">cmx</xa-datasource-property>

<xa-datasource-property name="Password">!!cmx!!</xa-datasource-property>

<server_install_dir>/bin/build.properties where the appserver is WebLogic

WebLogic credentials


weblogic.host=localhost

weblogic.server=AdminServer

weblogic.username=weblogic

weblogic.rmi.port=7001

weblogic.naming.protocol=t3

weblogic.version=9.x

<server_install_dir>/resources/cmxserver.properties

cmx.server.masterdatabase.type, cmx.appserver.type, cmx.appserver.rmi.port and cmx.appserver.soap.connector.port

Location Check For

Troubleshooting 279


If any of the contents of the files or the properties listed in the table above are incorrect, you must enter the correct contents or properties manually into the silent-install property file, then restart the installation. Alternatively, you can make corrections to the individual files, such as the cmxserver.properties file, and rerun the postInstallSetup command manually from the same <server_install_dir>.

Checking the Cleanse Match Server Silent Install

The following tables list the files or folders you should check when you perform a silent Cleanse Match Server install.

<server_install_dir>/setSiperian.bat where the appserver is JBoss

Check for following variables and make sure their values are correct in your environment.

SET SIP_HOME=C:/infamdm/hub/server

SET JBS_HOME=C:/jboss-5.1.0.GA

SET JBS_DEPLOY_DIR=C:/jboss-5.1.0.GA/server/<configuration_name>/deploy

<server_install_dir>\setSiperian.bat where appserver is WebLogic


SET SIP_HOME=C:\infamdm\hub\server

SET WLS_HOME=C:\bea\user_projects\domains\base_domain

SET WLS_DEPLOY_DIR=C:\bea\user_projects\domains\base_domain\autodeploy

<server_install_dir>/setSiperian.bat where appserver is WebSphere


SET SIP_HOME=C:/infamdm/hub/server

SET WAS_HOME=C:/Program Files/IBM/WebSphere/AppServer

SET WAS_SERVER=server1

Location Check For

<cleanse_install_directory>/logs

postInstallSetup.log: Check for any ERROR in the file

Location Check For



<cleanse_install_directory>/resources/cmxcleanse.properties

and cmx.appserver.type files

# Address Doctor Properties

cleanse.library.addressDoctor.property.AddressDoctor.UnlockCode=

cleanse.library.addressDoctor.property.AddressDoctor.DatabasePath=C:/addressdoctor

cleanse.library.addressDoctor.property.AddressDoctor.Optimization=ADDRESSES_SORTED_BY_COUNTRIES

cleanse.library.addressDoctor.property.AddressDoctor.MemoryMB=600

cleanse.library.addressDoctor.property.AddressDoctor.CorrectionType=CORRECT_ONLY

cleanse.library.addressDoctor.property.AddressDoctor.PreLoad.CERTIFIED.PRELOAD_PART=US

cleanse.library.addressDoctor.property.AddressDoctor.PreLoad.CERTIFIED.PRELOAD_FULL=

cleanse.library.addressDoctor.property.AddressDoctor.PreLoad.CORRECTION_ONLY.PRELOAD_PART=CA, US

cleanse.library.addressDoctor.property.AddressDoctor.PreLoad.CORRECTION_ONLY.PRELOAD_FULL=

# Trillium Director Properties

cleanse.library.trilliumDir.property.config.file.1=C:/infamdm/hub/cleanse/resources/Trillium/samples/director/td_default_config_Global.txt

cleanse.library.trilliumDir.property.config.file.2=C:/infamdm/hub/cleanse/resources/Trillium/samples/director/td_default_config_US_detail.txt

cleanse.library.trilliumDir.property.config.file.3=C:/infamdm/hub/cleanse/resources/Trillium/samples/director/td_default_config_US_summary.txt

#FirstLogicDirect Properties

cleanse.library.firstLogicDirect.property.config.file=C:/infamdm/hub/cleanse/resources/firstLogicDirect/fld_default_config.txt

<cleanse_install_directory>/resources/cmxserver.properties

cmx.home=$USER_INSTALL_DIR$

# Application server type: jboss, websphere or weblogic

cmx.appserver.type=$SIP.APPSERVER.TYPE$

# default setting: 8880 for websphere only (this is not being used in jboss and weblogic

cmx.appserver.soap.connector.port=$SIP.WEBSPHERE.SOAP.PORT$

<cleanse_install_directory>/setSiperianEnv.bat where the appserver is JBoss

All the settings in setSiperianEnv.bat for Cleanse Match Server are the same as for the Hub Server.

Location Check For

Troubleshooting 281


If any of the contents of the files or the properties listed in the table above are incorrect, you must enter the correct contents or properties manually into the silent-install property file, then restart the installation. Alternatively, you can make corrections to the individual files, such as the cmxcleanse.properties file, and rerun the postInstallSetup command manually from the same <cleanse_install_directory>.

Checking the Hub Server and Cleanse Match Server Silent Install (Windows)

This section applies to checking silent installs in the Windows environment.

Checking the Hub Server Silent Install (Windows)

Check these files or folders when you perform a silent Hub Server install.

<cleanse_install_directory>/setSiperianEnv.bat where appserver is WebLogic


<cleanse_install_directory>/setSiperianEnv.bat where appserver is WebSphere


Location Check For

<server_install_dir>\logs postInstallSetup.log: Check for any ERROR in the log.

Location Check For



<server_install_dir>\bin\build.properties where the appserver is WebLogic

Database credentials.




masterdatabase.databasename=cmx_system

masterdatabase.jdbc.driverclassname=oracle.jdbc.xa.client.OracleXADataSource

masterdatabase.jdbc.jndiname=jdbc\siperian-cmx_system-ds

masterdatabase.jdbc.url=jdbc:oracle:thin:@mdb_server:1521:orcl


<server_install_dir>\bin\build.properties where the appserver is WebSphere

Database credentials.




masterdatabase.port=1521

masterdatabase.dbname=orcl

masterdatabase.schemaname=cmx_system


<server_install_dir>\conf\siperian-mrm-ds.xml where the appserver is JBoss.

database credentials


<xa-datasource-property name="URL">jdbc:oracle:thin:@mdb_server:1521:orcl<\xa-datasource-property>

<xa-datasource-property name="User">cmx<\xa-datasource-property>

<xa-datasource-property name="Password">!!cmx!!<\xa-datasource-property>

Location Check For

Troubleshooting 283


If any of the items are incorrect, enter the correct contents or properties manually into the silent-install property file, then restart the installation. You can also make corrections to the individual files, such as the cmxserver.properties file, and rerun the postInstallSetup command manually from the same <server_install_dir>.

<server_install_dir>\bin\build.properties where the appserver is WebLogic

WebLogic credentials


weblogic.host=localhost

weblogic.server=AdminServer

weblogic.username=weblogic


weblogic.naming.protocol=t3

weblogic.version=9.x

<server_install_dir>\resources\cmxserver.properties

cmx.server.masterdatabase.type, cmx.appserver.type, cmx.appserver.rmi.port and cmx.appserver.soap.connector.port

<server_install_dir>\setSiperian.bat where the appserver is JBoss



SET JBS_HOME=C:\jboss-5.1.GA

SET JBS_DEPLOY_DIR=C:\jboss-5.1.GA\server\<configuration_name>\deploy

<server_install_dir>\setSiperian.bat where appserver is WebLogic



SET WLS_HOME=C:\bea\user_projects\domains\base_domain

SET WLS_DEPLOY_DIR=C:\bea\user_projects\domains\base_domain\autodeploy

<server_install_dir>\setSiperian.bat where appserver is WebSphere



SET WAS_HOME=C:\Program Files\IBM\WebSphere\AppServer

SET WAS_SERVER=server1

Location Check For



Checking the Cleanse Match Server Silent Install (Windows)

Check these files or folders when you perform a silent Cleanse Match Server install.

Location Check For

<cleanse_install_directory>\logs

postInstallSetup.log: Check for any ERROR in the file

<cleanse_install_directory>\resources\cmxcleanse.properties

and cmx.appserver.type files

# Address Doctor Properties

cleanse.library.addressDoctor.property.AddressDoctor.UnlockCode=

cleanse.library.addressDoctor.property.AddressDoctor.DatabasePath=C:/addressdoctor

cleanse.library.addressDoctor.property.AddressDoctor.Optimization=ADDRESSES_SORTED_BY_COUNTRIES

cleanse.library.addressDoctor.property.AddressDoctor.MemoryMB=600

cleanse.library.addressDoctor.property.AddressDoctor.CorrectionType=CORRECT_ONLY

cleanse.library.addressDoctor.property.AddressDoctor.PreLoad.CERTIFIED.PRELOAD_PART=US

cleanse.library.addressDoctor.property.AddressDoctor.PreLoad.CERTIFIED.PRELOAD_FULL=

cleanse.library.addressDoctor.property.AddressDoctor.PreLoad.CORRECTION_ONLY.PRELOAD_PART=CA, US

cleanse.library.addressDoctor.property.AddressDoctor.PreLoad.CORRECTION_ONLY.PRELOAD_FULL=

# Trillium Director Properties

cleanse.library.trilliumDir.property.config.file.1=C:\infamdm\hub\cleanse\resources\Trillium\samples\director\td_default_config_Global.txt

cleanse.library.trilliumDir.property.config.file.2=C:\infamdm\hub\cleanse\resources\Trillium\samples\director\td_default_config_US_detail.txt

cleanse.library.trilliumDir.property.config.file.3=C:\infamdm\hub\cleanse\resources\Trillium\samples\director\td_default_config_US_summary.txt

#FirstLogicDirect Properties

cleanse.library.firstLogicDirect.property.config.file=C:\infamdm\hub\cleanse\resources\firstLogicDirect\fld_default_config.txt

<cleanse_install_directory>\resources\cmxserver.properties

cmx.home=$USER_INSTALL_DIR$

# Application server type: jboss, websphere or weblogic

cmx.appserver.type=$SIP.APPSERVER.TYPE$

# default setting: 8880 for websphere only (this is not being used in jboss and weblogic

cmx.appserver.soap.connector.port=$SIP.WEBSPHERE.SOAP.PORT$

Troubleshooting 285

MATCH Process Error: VerifyNeedToStrip

If any of the contents of the files or the properties listed in the table above are incorrect, you must enter the correct contents or properties manually into the silent-install property file, then restart the installation. Alternatively, you can make corrections to the individual files, such as the cmxserver.properties file, and rerun the postInstallSetup command manually from the same <infamdm_install_directory>.

MATCH Process Error: VerifyNeedToStrip

This section applies if you encounter VerifyNeedToStrip error SIP-16062 during the execution of the Match process.

VerifyNeedToStrip (Unix)

If you receive VerifyNeedToStrip error SIP-16062 while you run a Match process, check the following library and environment variable settings:• The library path environment variable should contain the following path for the

Informatica profile:

<server_install_dir>/lib

The library path environment variable depends on the platform:

• AIX: LIBPATH

• HP-UX: SHLIB_PATH

• Solaris, Suse, or RedHat: LD_LIBRARY_PATH

<cleanse_install_directory>\setSiperianEnv.bat where the appserver is JBoss


<cleanse_install_directory>\setSiperianEnv.bat where appserver is WebLogic


<cleanse_install_directory>\setSiperianEnv.bat where appserver is WebSphere


Location Check For


Inaccurate Start/Stop Timestamp for ORS

Example (HP-UX):

SHLIB_PATH=/u1/infamdm/hub/cleanse/lib

• The SSAPR environment variable should include the following path for all users (such as the WebLogic user and the Informatica user):

<server_install_dir>/resources

Example:

SSAPR=/u1/infamdm/hub/cleanse/resources

VerifyNeedToStrip (Windows)

If you receive VerifyNeedToStrip error SIP-16062 while you run a Match process, check the following library and environment variable settings:• The PATH environment variable should contain the following path for the

Informatica profile:

<cleanse_install_directory>\cleanse\lib

Example:

PATH=C:\infamdm\hub\cleanse\lib

• The SSAPR environment variable should include the following path for all users (such as the WebLogic user and the Informatica user):

<infamdm_install_directory>\cleanse\resources

Example:

SSAPR=C:\infamdm\hub\cleanse\resources

Inaccurate Start/Stop Timestamp for ORS

If you create an ORS, then export it, and subsequently reuse the .dmp file of this previously-installed ORS to create a second ORS, the start date and end date columns in the C_REPOS_DB_VERSION table of this ORS will have a different value from the actual start date and end date. This difference in date does not affect any functionality.

Troubleshooting 287

major.minor Version Errors When Loading Cleanse Match Server

major.minor Version Errors When Loading Cleanse Match Server

If you see multiple major.minor console errors when you try to load your Cleanse Match Server, check that your system has the correct Java version installed (Java 1.5).

Low Cleanse/Match Application Server Performance

Application Server performance can be slow due to a high number of performance log entries in the log4j.xml file.

To remedy this, modify the log4j.xml file to exclude performance-related logging as follows:

<category name="siperian.performance" additivity="false"> <priority value="OFF"/><appender-ref ref="fileAppender"/></category>


Troubleshooting (JBoss / Unix)


This section provides troubleshooting instructions for JBoss on Unix.

Changing the Hub Server Parameters (JBoss/Unix)

You can change the following Hub Server parameters:• JBoss application server and RMI port number

• Database server and instance name

Changing the RMI Port Number for JBoss

To change the application server and RMI port number:1. Open the following file in a text editor:

<infamdm_install_directory>/resources/cmxserver.properties

2. Change the following value:

cmx.appserver.rmi.port=1099

3. Go to <infamdm_install_directory> and run postInstallSetup.sh.


Changing the Database Server and Instance Name for JBoss

To change the database server and instance name:1. Open the following file in a text editor:

<JBoss_install_dir>/server/<configuration_name>/deploy/siperian-mrm-ds.xml

2. Change the following values:

<xa-datasource-property name="URL">jdbc:oracle:thin:@host:port:instance</xa-datasource-property>

Troubleshooting 289


where host is the name of the host running your Oracle database, port is the port number on which Oracle is listening, and instance is the name of your Oracle instance.

Note: Do not run postInstallSetup for JBoss.


Manually Redeploying the Hub Server (JBoss/Unix)

Informatica provides the postInstallSetup script that both the Hub Server installer and user can use to deploy/redeploy the Hub Server application to the application server. However, you can also use the default application server’s tool to do the deployment yourself, as long as it is deployed from the Hub Server installation directory. To manually redeploy the Hub Server application:1. Stop the server.

2. Remove the siperian-mrm.ear from <JBoss_install_dir>/server/<configuration_name>/deploy to make sure the application is totally removed.

3. Copy the siperian-mrm.ear from the Hub Server installation directory.


Refer to your JBoss documentation for more information.

Manually Undeploying the Cleanse Match Server (JBoss/Unix)

The installation process begins by undeploying any pre-existing Cleanse Match Servers. If this process fails, you will need to undeploy manually. Delete the siperian-mrm-cleanse.ear from the <JBoss_install_dirE>/server/<configuration_name>/deploy directory.

Note: Restart the server if the auto-deploy process of JBoss does not remove the applications. See your JBoss administration documentation for more information.



Setting the JVM Size (JBoss/Unix)

If you are using AddressDoctor Cleanse Engine as your cleanse engine to run any batch process, you must make sure that the stack size for the JVM is sufficient. If you do not set this properly for your application server, AddressDoctor will throw an exception during certification.

To set the JVM size for JBoss:1. Go to your JBoss home directory.

2. Navigate to the bin directory.

3. Open run.sh in a text editor.

4. Set the JAVA_OPTS variable as follows:

JAVA_OPTS=${JAVA_OPTS} -Xmx1024m

5. Save and close the run.sh file.

Troubleshooting 291

Troubleshooting (WebLogic / Unix)


This section provides troubleshooting instructions for WebLogic on Unix.

Changing the Hub Server Parameters (WebLogic/Unix)

You can change the following parameters:• WebLogic domain name

• WebLogic application server and RMI port number

• WebLogic username and password

• WebLogic host or server name

Changing the Domain for WebLogic

To change the WebLogic domain:1. Open the following file in a text editor:

<infamdm_install_directory>/setSiperianEnv.sh

2. Change the following values with the new domain path:

For WebLogic:

SET WLS_HOME=/<WebLogic_install_dir>/user_projects/domains/<domain_name>SET WLS_DEPLOY_DIR=/<WebLogic_install_dir>/user_projects/domais/<domain_name>/autodeploy

3. Go to <infamdm_install_directory> and run the following command:


where weblogicPassword is the WebLogic password and yourDBPassword is the password for your database.




Some Unix systems require that you keep the application server running while you run the script, or the script will fail.


Changing the RMI Port Number for WebLogic





3. Open the following file in a text editor:




5. Go to <infamdm_install_directory> and run postInstallSetup.sh.

You must keep the application server running while you run the script, or the script will fail.


Changing the Username for WebLogic

To change the username for the WebLogic domain:1. Open the following file in a text editor:



weblogic.username=<username>



Troubleshooting 293






Changing the Host or Server Name for WebLogic

To change the WebLogic host or server:1. Open the following file in a text editor:



weblogic.host=<host_name>weblogic.server=<server_name>









Changing the Cleanse Match Server Parameters (WebLogic/Unix)




• WebLogic host and server name



<infamdm_install_directory>/setSiperianEnv.sh


For WebLogic:

SET WLS_HOME=/<WebLogic_install_dir>/user_projects/domains/<domain_name> SET WLS_DEPLOY_DIR=/<WebLogic_install_dir>/user_projects/domains/<domain_name>/autodeploy



where weblogicPassword is the WebLogic password and is yourDBPassword the password for your database.




Troubleshooting 295


Changing the Application Server and RMI Port Number for WebLogic






postInstallSetup.sh -Dweblogic.password=<weblogicPassword>-Ddatabase.password=<yourDBPassword>





Changing the Username and Password for WebLogic

To change the username and password for the WebLogic domain:1. Open the following file in a text editor:























Troubleshooting 297


Changing the Hub Server Parameters for the Database (WebLogic/Unix)

You can change the following database parameters for WebLogic:• Database server name

• Database instance name

Changing Server Name for the Database

To change the database server name:1. Open the following file in a text editor:



masterdatabase.server=<database_host_name> masterdatabase.jdbc.url=jdbc:oracle:thin:@<database_host_name>:<port>:<instance_name>









Changing Instance Name for the Database

To change the instance name:1. Open the following file in a text editor:



masterdatabase.jdbc.url=jdbc:oracle:thin:@<database_host_name>:<port>:<instance_name>







Manually Redeploying Hub Server (WebLogic/Unix)

Informatica provides the postInstallSetup script that both the Hub Server installer and user can use to deploy/redeploy the Hub Server application to the application server. However, you can also use the default application server’s tool to do the deployment yourself, as long as it is deployed from the Hub Server installation directory.

Use the WebLogic Server Administration Console to undeploy and deploy the siperian-mrm.ear from the Hub Server installation directory. Deploy the application in stage mode. Refer to your WebLogic documentation for more information.

Troubleshooting 299


Manually Undeploying the Cleanse Match Server (WebLogic/Unix)

The installation process begins by undeploying any pre-existing Cleanse Match Servers. If this process fails, you will need to undeploy manually. Uninstall the siperian-mrm-cleanse.ear application using the WebLogic Server Administration Console. Make sure that the process finishes completely. For more information, see your WebLogic documentation.

Setting the JVM Size (WebLogic/Unix)


To set the JVM size for WebLogic server:1. Go to your WebLogic home directory.

2. Open setDomainEnv.sh in a text editor.

3. Set the MEM_ARGS variable as follows:

set MEM_ARGS=${MEM_ARGS} -Xmx1024m

4. Save and close the setDomainEnv.sh file.


Troubleshooting (WebSphere / Unix)


This section provides troubleshooting instructions for WebSphere on Unix.

Changing the Hub Server Parameters (WebSphere/Unix)

You can change the following parameters:• RMI port number

• SOAP port number

To change the RMI or SOAP port numbers:1. Open the following file in a text editor:


2. Change any of the following values:

cmx.appserver.rmi.port=2809cmx.appserver.soap.connector.port=8880


postInstallSetup.sh -Ddatabase.password=<yourDBPassword>




Troubleshooting 301


Changing the Cleanse Match Server Parameters (WebSphere/Unix)

You can change the SOAP port number.

To change the SOAP port numbers:1. Open the following file in a text editor:

<infamdm_install_directory>/resources/cmxcleanse.properties


cmx.appserver.soap.connector.port=8880


postInstallSetup.sh





Changing the Hub Server Parameters for the Database (WebSphere/Unix)

You can change the following database parameters for WebSphere:• Database server name









where yourDBPassword is the password for your database.







Troubleshooting 303










Manually Redeploying the Hub Server Application (WebSphere/Unix)

Informatica provides the postInstallSetup script that both the Hub Server installer and user can use to deploy/redeploy the Hub Server application to the application server. However, you can also use the WebSphere Application Server Administrative Console to redeploy siperian-mrm.ear as long as it is deployed from the Hub Server installation directory.

Use the WebSphere Application Server Administrative Console to redeploy siperian-mrm.ear. To redeploy the Hub Server on the WebSphere application server:1. Use the WebSphere Server Administration Console to undeploy the

siperian-mrm.ear file.

2. Use the WebSphere Application Server Administrative Console to install the siperian-mrm.ear file.

Be sure to allow the deployment to generate default bindings by checking the option in the “Preparing for the application installation” panel.



Manually Undeploying the Cleanse Match Server (WebSphere/Unix)

The installation process begins by undeploying any pre-existing Cleanse Match Servers. If this process fails, you will need to undeploy manually. Uninstall the siperian-mrm-cleanse.ear application from the WebSphere Application Server Administrative Console. Make sure that the process finishes completely. See your WebSphere documentation for more information.

Setting the JVM Size (WebSphere/Unix)


To set the JVM size for WebSphere:1. Open the WebSphere Console.

2. Go to Servers > Application Server > <Your_Server> > Process Definition > Java Virtual Machine

3. Add the following to the Generic JVM Arguments

-Xss1024k - Initializes the stack with at least 256 KB

-Xss1024m - Initializes the stack when running in CASS mode

-Xmx1024m - Initializes the heap with a maximum of 1024 MB

-Xms128m - Initializes the heap with at least 128 MB

4. Save the configuration.

5. Restart the server.

Troubleshooting 305

Troubleshooting (JBoss / Windows)

Changing the SOAP Request Timeout (WebSphere/Unix)

If the postinstallsetup process fails due to a timeout error, you can increase the SOAP request timeout value and retry the process. Locate and edit the following file:

<portal_profile_root>/properties/soap.client.props

Change the following value from:

com.ibm.SOAP.requestTimeout=180

to



This section provides troubleshooting instructions for JBoss on Windows.

Changing the Hub Server Parameters (JBoss/Windows)

You can change the following parameters:• JBoss application server and RMI port number

• Database server and instance name

Changing the Application Server and RMI Port Number for JBoss


<infamdm_install_directory>\resources\cmxserver.properties



3. Go to <infamdm_install_directory> and run postInstallSetup.bat.




Changing the Database Server and Instance Name for JBoss

To change the database server and instance name:1. Open the following file in a text editor:

<JBoss_install_dir>\server\<configuration_name>\deploy\siperian-mrm-ds.xml


<xa-datasource-property name="URL">jdbc:oracle:thin:@hostname:1521:orcl</xa-datasource-property>

where hostname is the name of the host.

Note: Do not run postinstall for JBoss.


Manually Redeploying Hub Server (JBoss/Windows)

Informatica provides the postInstallSetup script that both the Hub Server installer and user can use to deploy or redeploy the Hub Server application to the application server. However, you can also use the default application server’s tool to do the deployment yourself, as long as it is deployed from the Hub Server installation directory. Refer to your application server documentation for more information.

To manually deploy Hub Server:1. Stop the server.

2. Remove the siperian-mrm.ear from <JBoss_install_dir>\server\<configuration_name>\deploy\siperian-* files and <JBoss_install_dir>\server\<configuration_name>\deploy\messaging\siperian-* to make sure all related files and application are totally removed.

3. Copy the siperian-mrm.ear from Hub Server installation directory to <JBoss_install_dir>\server\<configuration_name>\deploy.

4. Copy siperian-mrm-ds.xml from <server_install_dir>\conf to <JBoss_install_dir>\server\<configuration_name>\deploy.

Troubleshooting 307


5. Copy siperian-jms-ds.xml and siperian-destination-service.xml from <server_install_dir>\conf to <JBoss_install_dir>\server\<configuration_name>\deploy\messaging.


Manually Undeploying the Cleanse Match Server (JBoss/Windows)

The installation process begins by undeploying any pre-existing Cleanse Match Servers. If this process fails, you will need to undeploy manually. Delete the siperian-mrm-cleanse.ear from the <JBOSS_HOME>/server/<configuration_name>/deploy directory.

Note: Restart the server if the auto-deploy process of JBoss doesn't remove the applications. See your JBoss administration documentation for more information.

Setting the JVM Size (JBoss/Windows)


To set the JVM size for JBoss:1. Go to your JBoss installation directory.

2. Navigate to the bin directory.

Open run.bat in a text editor.

3. Set the JAVA_OPTS variable as follows:

JAVA_OPTS="%JAVA_OPTS% -Xss1000k"

4. Save and close the run.bat file.


Troubleshooting (WebLogic / Windows)


This section provides troubleshooting instructions for WebLogic on Windows.

Changing the Hub Server Parameters (WebLogic/Windows)




• WebLogic host or server name



<infamdm_install_directory>\setSiperianEnv.bat


SET WLS_HOME=D:<\WebLogic_install_dir>\user_projects\domains\<domain_name>SET WLS_DEPLOY_DIR=D:\<WebLogic_install_dir>\user_projects\domains\<domain_name>\autodeploy


postInstallSetup.bat -Dweblogic.password=<weblogicPassword>-Ddatabase.password=<yourDBPassword>




Troubleshooting 309


Changing the RMI Port Number for WebLogic


<infamdm_install_directory>\bin\build.properties




<infamdm_install_directory>\resources\cmxserver.properties








Changing the Username for WebLogic

To change the username for the WebLogic domain:1. Open the following file in a text editor:





















Changing the Cleanse Match Server Parameters (WebLogic/Windows)




• WebLogic host and server name

Troubleshooting 311




<infamdm_install_directory>\setSiperianEnv.bat


SET WLS_HOME=D:\<WebLogic_install_dir>\user_projects\domains\<domain_name>SET WLS_DEPLOY_DIR=D:\<WebLogic_install_dir>\user_projects\domains\<domain_name>\autodeploy






Changing the Application Server and RMI Port Number for WebLogic


<server_install_dir>\bin\build.properties









5. Go to <server_install_dir> and run the following command:





Changing the Username and Password for WebLogic

To change the username and password for the WebLogic domain:1. Open the following file in a text editor:



weblogic.username=<user_name>

3. Go to your install directory and run the following script:

postInstallSetup.bat -Dweblogic.password=YourPassword-Ddatabase.password=YourDBPassword

where YourPassword is your WebLogic user’s password and where YourDBPassword is your database password.







Troubleshooting 313



3. Go to your install directory and run the following script:

postInstallSetup.bat -Dweblogic.password=YourPassword-Ddatabasec.password=YourDBPassword

where YourPassword is your password and where YourDBPassword is your database password.



Changing the Hub Server Parameters for the Database (WebLogic/Windows)

You can change the following database parameters for WebLogic:• Database server name





















where yourDBPassword is the WebLogic password and is yourDBPassword the password for your database.



Manually Redeploying Hub Server (WebLogic/Windows)


To manually deploy Hub Server, use the WebLogic Server Administration Console to undeploy and deploy the siperian-mrm.ear from the Hub Server installation directory. Deploy the application in stage mode.

Troubleshooting 315

Troubleshooting (WebSphere / Windows)

Manually Undeploying the Cleanse Match Server (WebLogic/Windows)

The installation process begins by undeploying any pre-existing Cleanse Match Servers. If this process fails, you will need to undeploy manually. Uninstall the siperian-mrm-cleanse.ear application using the WebLogic Server Administration Console. Make sure that the process finishes completely. For more information, see your WebLogic documentation.

Setting the JVM Size (WebLogic/Windows)


To set the JVM size for WebLogic Server:1. Go to your WebLogic installation directory.

2. Open the startWeblogic.cmd file in a text editor.

3. Set the MEM_ARGS variable as follows:

set MEM_ARGS=%MEM_ARGS% -Xss1000k

4. Save and close the startWeblogic.cmd file.


This section provides troubleshooting instructions for WebSphere on Windows.



Changing the Hub Server Parameters (WebSphere/Windows)

You can change the following parameters:• RMI port number

• SOAP port number

To change the RMI or SOAP port numbers:1. Open the following file in a text editor:



cmx.appserver.rmi.port=2809cmx.appserver.soap.connector.port=8880

3. Go to <server_install_dir> and run the following command:

postInstallSetup.bat -Ddatabase.password=<yourDBPassword>




Changing the Cleanse Match Server Parameters (WebSphere/Windows)

You can change the SOAP port number.

To change the SOAP port numbers:1. Open the following file in a text editor:

<cleanse_install_directory>\resources\cmxcleanse.properties


Troubleshooting 317


cmx.appserver.soap.connector.port=8880





Changing the Hub Server Parameters for the Database (WebSphere/Windows)

You can change the following database parameters for WebSphere:• Database server name


























Manually Redeploying Hub Server (WebSphere/Windows)


To manually deploy Hub Server, use the WebSphere Application Server Administrative Console to uninstall and install the siperian-mrm.ear from the Hub Server installation directory. Be sure to allow the deployment to generate default bindings by checking for the option in the “Preparing for the application installation” panel.

Troubleshooting 319


Manually Undeploying the Cleanse Match Server (WebSphere/Windows)

The installation process begins by undeploying any pre-existing Cleanse Match Servers. If this process fails, you will need to undeploy manually. Uninstall the siperian-mrm-cleanse.ear application from the WebSphere Application Server Administrative Console. Make sure that the process finishes completely. See your WebSphere documentation for more information.

Setting the JVM Size (WebSphere/Windows)


To set the JVM size for WebSphere:1. Open the WebSphere Console.

2. Go to Servers > Application Server > <Your_Server> > Process Definition > Java Virtual Machine

3. Add the following to the Generic JVM Arguments

-Xss1000k

4. Save the configuration.

5. Re-start the server.

Changing the SOAP Request Timeout (WebSphere/Windows)

If the postinstallsetup process fails due to a timeout error, you can increase the SOAP request timeout value and retry the process. Locate and edit the following file:

<portal_profile_root>\properties\soap.client.props

Change the following value from:




to


Troubleshooting 321

A
Installing from the Command Line
Informatica supports command-line installation for the Hub Server and the Cleanse Match Server software. This section explains how to install these applications from the command line, without using the GUI interface.

Chapter Contents

• Preparing for Installation

• Installing from the Command Line (JBoss/Unix)

• Installing from the Command Line (WebLogic/Unix)

• Installing from the Command Line (WebSphere/Unix)

• Silent Installation from the Command Line

323



If you prefer to install Hub Server and Cleanse Match Server without using the GUI installer, you can manually install the Hub Server and Cleanse Match Server from the command line.

Before you install:• Make sure that you have fulfilled the hardware and software requirements for Hub

Server as outlined in the Informatica MDM Hub Release Notes. In particular, make sure you have the correct version of the Oracle drivers.

• Make sure you have a license file from Informatica. You cannot install the Informatica MDM Hub if you do not have a license file. Contact Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii) for a license.

• Make sure that you have your application server installed and configured. For more information, see your application server documentation.


Installing from the Command Line (JBoss/Unix)


This section describes how to install the Hub Server and Cleanse Match Server software from the Unix command line.

Installing Hub Server

Complete all of the preparation tasks described for the Hub Server installation prior to the command-line installation. See “Preparing for Installation” on page 46.

To install Hub Server from the command line:1. Make sure that your application server is started and running correctly.

2. Run the following command from the command prompt:


The installer displays the Introduction screen.

Press Enter to continue.

3. Read the License Agreement. Type Y for yes and press Enter to continue. Type N for no if you do not want to accept the License Agreement and want to exit the install program.

The installer displays information about the install folder.

4. Press Enter to use the default installation folder for the Hub Server installation (/infamdm/hub/server). If you want to change the installation folder, type in the absolute path for the location and press Enter.

Confirm the installation folder (Y/N) and press Enter to continue.

The installer displays information about the link location.

5. Select the link location.

The installer displays license file information.

6. Check the default license file location. To accept the default location, press Enter. To change the location, type the new absolute path to the license file location and press Enter.

Installing from the Command Line 325


The names of the supported application servers are listed. Type the number for your application server and press Enter to continue. The default is the JBoss application server. Press Enter to accept the default.

As the GUI-based installer does, the command line installer depends on your application server.

The JBoss Application Server information is displayed.


a. Specify the application server installation directory. Press Enter.

The JBoss Application Server Configuration Name information is displayed.

b. Specify the Configuration Name (default is production). Press Enter.


c. Press Enter.

The database JDBC driver files are copied to the <JBoss_install_dir>/server/<configuration_name>/lib directory.

Note: If you type BACK at this point, the install will not be able to go back to the previous step.




<JBoss_install_dir>/server/<configuration_name>/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml

Note: The JBoss port can conflict with the default Oracle port. If that is the case for your installation, you must change one of the ports to resolve the conflict. To change the port number, open bindings-jboss-beans.xml for editing, search for the word port., and set the port value to match the value you have set on the JBoss Application Server screen.

e. Press Enter to continue.

The database selection prompt is displayed.

8. Select Oracle. Press Enter.



9. Select the Oracle Database Connection Type you want (Service Name or SID). Press Enter.


10. When prompted, specify the settings for the Oracle database to which you want to connect. Press Enter to accept the default value, or replace the defaults with the correct values. These settings include: server name, port number, Service Name or Oracle SID (depends on your selected connection type), Informatica MDM Hub system schema name, CMX Username, and CMX password (for the CMX username). Press Enter.


11. If the selected Oracle connection type is Service Name, then you will be prompted to confirm or change the Connect URL. Change the system-generated URL, if you want. Press Enter to continue.

12. The deployment information is displayed. Choose whether you want to run the postInstallSetup script as part of the installation, or run it manually later.

13. Press Enter to accept the default value.

A summary of your installation choices is displayed.

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

The Hub Server will be installed according to the configuration information you supplied. When the process is complete, the Install Complete information is displayed.

15. Press Enter to exit the installer.

16. Verify the command-line installation by checking these log files:

The following files are useful for troubleshooting any Hub Server installation process (see “Informatica MDM Hub Log Files” on page 268). Save these files right after a failure and provide them when you report it to Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii):






Save a copy of these log files to the installation documentation directory described in “Documenting Your Installation” on page 8.


Before installing the Cleanse Match Server you need to complete the preparation for installation. See “Preparing for Installation” on page 112.

Note: Do not use the root user when installing the Cleanse Match Server on RedHat Linux. Instead, create and use a separate user profile for installing Informatica MDM Hub. This is a limitation of InstallAnywhere, as the root user does not have a .profile.

To install the Cleanse Match Server from the command line:1. Make sure that your application server is started and running correctly.


./hub_cleanse_install.bin -i console

This will start the installation and the Introduction is displayed.

3. Press Enter to continue.

The License Agreement is displayed.




Shows what was chosen during installation.










4. Read the License agreement. Type Y for yes and press Enter to continue. Type N for no if you do not want to accept the License Agreement and exit the install program.

Information about the installation folder is displayed.

5. Press Enter to use the default installation folder for the Cleanse Match Server. If you want to change the default installation folder, type in the absolute path for the location and press Enter.

License file information is displayed.

6. Check default license file location. Press Enter to accept the default. To change the location, type in the valid location. Press Enter to continue.

The names of the supported application servers are listed.

Type the number for your application server and press Enter to continue. To accept the default application server (JBoss), press Enter.

As the GUI-based installer does, the command line installer depends on your application server.

The JBoss Application Server home is displayed.


a. Specify the application server installation directory. Press Enter.

The JBoss Application Server Configuration Name is displayed.

b. Specify the Configuration Name (default is production). Press Enter.

The JBoss Application Server screen is displayed.



<JBoss_install_dir>/server/<configuration_name>/conf/bindingservice/META-INF/bindings-jboss-beans.xml

Note: The JBoss port can conflict with the default Oracle port. If that is the case for your installation, you must change one of the ports to resolve the conflict. To change the port number, open bindings-jboss-beans.xml for editing, search for the word port., and set the port value to match the value you have set on the JBoss Application Server screen.




As the GUI-based installer does, the command line installer depends on which cleanse engines you have licensed.



• If you are using AddressDoctor:

• Specify the Unlock Code, Optimization, Memory, and Correction Type parameters. For backslashes (\) in any of these parameters, use a double backslash (\\) instead. Press Enter.

The Configure AddressDoctor Preload information is displayed.

• Specify the AddressDoctor preload parameters. Press Enter.

The Choose AddressDoctor Database Path information is displayed.

• Choose the AddressDoctor database path. Press Enter.

• If you are using Business Objects DQ XI, you must configure Business Objects DQ XI using the Cleanse Match Server installer. Specify the Host Name, Port, and Sub File (the default is dqxiserver1_substitutions.xml) parameters for your Business Objects DQ XI cleanse engine. Press Enter.

10. The Deploy screen provides the option to run the postInstallSetup script now or run it manually later.

a. Press Enter to accept the default value.

b. If you want to change any of the information in the pre-installation summary, type BACK to go to a specific screen of information and make changes.

The Informatica Cleanse Match Server will be installed according to the configuration information you supplied. When the process is complete, the Install Complete information is displayed.


12. Verify the following files, which are useful for troubleshooting any Cleanse Match Server installation process. Save these files right after a failure and provide them



when you report it to Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii):


File Description














Installing from the Command Line (WebLogic/Unix)



Installing the Hub Server

Before installing the Hub Server complete all of the preparation prior to installation. See “Preparing for Installation” on page 57.




The Introduction displays, giving your further information about the installation.



4. Information about the install folder is displayed.


Confirm the installation folder (Y/N) and press Enter to continue.




7. Check the default license file location. To accept the default location press Enter. To change the location, type the new absolute path to the license file location and press Enter.



8. Type the number (3) for the WebLogic Application Server and press Enter to continue.

As the GUI-based installer does, the command line installer depends on your application server. The WebLogic Application Server Home is displayed.

9. Type a valid entry for the WebLogic Application Server location and then press Enter.

The WebLogic login information is displayed.

10. Enter the login information for your WebLogic domain. Press Enter to continue.

The database selection prompt is displayed.

11. Select Oracle. Press Enter.














19. Verify the command-line installation by checking these log files:

The following files are useful for troubleshooting any Hub Server installation process. Save these files right after a failure and provide them when you report it to Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii):



Before installing the Cleanse Match Server complete the tasks described in “Preparing for Installation” on page 129.












WebLogic log files under: <weblogic_domain>/servers/<weblogic_server>/logs.: access.log, <weblogic_server>.log, and <weblogic_domain>.log















6. Check the default license file location. Press Enter to accept the default. To change the location, type in the valid location. Press Enter to continue.


7. Type the number (3) for the WebLogic Application Server and press Enter to continue.

The WebLogic application server home information is displayed.

8. Enter the location for your WebLogic Application Server home.


The WebLogic application server login information is displayed.

10. Specify your WebLogic settings.



Enter the host name, server name, user name, and password. Then enter the listen port number for your WebLogic server.


As the GUI-based installer does, the command line installer depends on which cleanse engines you have licensed.










13. The Deploy screen provides the option to run the postInstallSetup script now or run it manually later.

a. Press ENTER to accept the default.





Installing from the Command Line (WebSphere/Unix)

15. Check the following files, which are useful for troubleshooting any Cleanse Match Server installation process, and for providing to Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii).




Installing Hub Server

Before installing the Hub Server complete the preparations for installation. See “Preparing for Installation” on page 67.


File Description











WebLogic log files under: <weblogic_domain>/servers/<weblogic_server>/logs.: access.log, <weblogic_server>.log, and <weblogic_domain>.log






The Introduction displays, giving your further information about the installation.



4. Information about the install folder is displayed.


Confirm the installation folder (Y/N). and press Enter to continue.



7. License file information is displayed.

Check default license file location. To accept the default location press Enter. To change the location, type the new absolute path to the license file location and press Enter.

The names of the supported application servers are listed. Type the number for your application server and press Enter to continue.

The WebSphere Application Server Home information is displayed.

8. Check the default location for the application server home. Replace the default with the correct information if necessary. Press Enter to continue.

The installer warns you of the WebSphere pre-requisites for JDBC drivers.

9. Check the database JDBC driver files location and press Enter to continue. The database JDBC driver files are copied to the <WebSphere_Home>/AppServer/lib directory.

Note: If you type BACK at this point, the install will not be able to go back to the previous step.



10. WebSphere Security Selection info is displayed with Yes and No options, No is the default.

• If you select No, the "WebSphere Application Server" information is displayed. Verify the Server name, RMI port, and SOAP port. Change the default information or press Enter to accept the default. Press Enter to continue.

• Is you select Yes, the "WebSphere Application Server and User Credentials" information is displayed. Verify the Server name, RMI port, and SOAP port. Enter Username and Password (this is blank by default.). Change the default information or press Enter to accept the default. Press Enter to continue.

11. The database selection prompt is displayed.

Select Oracle. Press Enter.














19. Verify the command-line installation by checking these log files. Save these files right after a failure and provide them when you report it to Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii):



Before installing the Cleanse Match Server complete the preparations for installation. See “Preparing for Installation” on page 148.




























6. Check the default license file location. Press Enter to accept the default. To change the location, type in the valid location. Press Enter to continue.


7. Type the number for the WebSphere application server and press Enter to continue.

8. Enter the location for the WebSphere Application Server, or accept the default. Press Enter.

9. WebSphere Security Selection info is displayed with Yes and No options, No is the default.

• If you select No, the "WebSphere Application Server" information is displayed. Verify the Server name and set the SOAP port for your application



server. Change the default information or press Enter to accept the default. Press Enter to continue.

• Is you select Yes, the "WebSphere Application Server and User Credentials" information is displayed. Enter Username and Password (this is blank by default). Verify the Server name and set the SOAP port for your application server. Change the default information or press Enter to accept the default. Press Enter to continue.

10. As the GUI-based installer does, the command line installer depends on which cleanse engines you have licensed.

Configure cleanse engine settings for the cleanse engine you use.









The Deploy screen provides the option to run the postInstallSetup script now or run it manually later.

a. Press Enter to accept the default value.





c. Press Enter to exit the installer.

11. Check the following files, which are useful for troubleshooting any Cleanse Match Server installation process, and for providing to Informatica Global Customer Support (see “Informatica Global Customer Support” on page xvii).


File Description















Silent Installation from the Command Line


You can run a “silent install” from the command line for both Hub Server and the Cleanse Match Server installation. With silent installation, you will not see any of the screens or messages associated with the installation. You might want to use a silent install if you are performing multiple installs, or if you are installing on a machine cluster. Silent installation can be run on either Unix or Windows systems.

Considerations When Using Silent Installation

The silent install is not interactive—it is truly silent. Therefore, you will not see any screens, progress messages, or failure messages, even if the silent installation fails during installation.

The silent install does not validate your settings. The silent installation process might complete successfully even if you have provided incorrect settings, such as the wrong application server path or an incorrect port setting. Such problems might become known only after completing the silent installation, when you attempt to run Informatica MDM Hub.

Note: Do not use the root user when installing the Cleanse Match Server on RedHat Linux. Instead, create and use a separate user profile for installing the Informatica MDM Hub. This is a limitation of InstallAnywhere, as the root user does not have a .profile to setup environment variables during installation.

Properties Files for Silent Installation

To run a silent install, you need to create two silent properties files—one for the Hub Server and one for the Cleanse Match Server. There are sample silent properties files located in the Informatica distribution directory in the following location:

Component Location

Hub Server <infamdm_install_directory>/silent_install/mrmserver

Cleanse Match Server

<infamdm_install_directory>/silent_install/mrmcleanse



Start with these sample files and modify them according to your environment.

Important: In the silent properties file, backslashes (\)and foreslashes (/) are special characters, so you must enter two of each when you enter information in this file, such as when you enter an installation path. For example, to enter the path to the cleanse directory (\u1\infamdm\hub\cleanse), you must enter: \\u1\\infamdm\\hub\\cleanse.

Creating Your Properties File

Important: Because the silent installer does not validate the settings in your properties files, be sure to specify the correct settings and verify them before you run the silent installer.

Create two silent properties files:

You can rename these files and they can be located anywhere in the machine.

Properties File for Hub Server

The following tables contain the properties to be set for Hub Server silent install.

Install Directory and License Properties

Set the following properties for the install directory, license path and filename:

Component Property File Name

Hub Server silentInstallServer_sample.properties

Cleanse Match Server silentInstallCleanse_sample.properties

Property Value

INSTALLER_UI silent

USER_INSTALL_DIR Directory to install Hub Server. Example: <infamdm_install_directory>//hub//server



Application Server Properties

Set properties for only one application server: JBoss, WebSphere, or WebLogic.

JBoss Properties

WebLogic Properties

SIP.LICENSE.PATH Path to your Informatica license file

SIP.LICENSE.FILENAME License filename (siperian.license)

Property Value

SIP.AS.CHOICE Application server name: “JBoss”

SIP.AS.HOME Path to JBoss home

JBOSS.AS.PORT_1 Your JBoss port number. Example: 8080

SIP.JBOSS.CONFIGURATION_NAME Configuration name. Default is production.

Property Value

SIP.AS.CHOICE Application server name: “WebLogic”

SIP.AS.HOME Path to WebLogic home. Example: //bea//user_projects//domains//base_domain

SIP.APPSERVER.HOST Host name. Example: localhost

SIP.APPSERVER.SERVER Admin Server name. Example: AdminServer

SIP.APPSERVER.USERNAME User name. Example: weblogic

SIP.APPSERVER.PASSWORD Password. Example: weblogic

WEBLOGIC.AS.PORT Application server port. Example: 7001

Property Value



WebSphere Properties

Database Properties

Set properties for only one database server: Oracle or DB2.

Oracle Properties

Property Value

SIP.AS.CHOICE Application server name: “WebSphere”

SIP.AS.HOME Path to WebSphere home. Example:

//WebSphere//AppServer

SIP.AS.SERVER Server name Example: server1

SIP.AS.PORT_2 Port 2 (RMI port). Example: 2809

SIP.AS.PORT_3 Port 3 (SOAP port). Example: 8880

SIP.WEBSPHERE.SECURITY.ENABLED (No or Yes)

if SIP.WEBSPHERE.SECURITY.ENABLED is 'Yes', following two properties need to be set

SIP.APPSERVER.USERNAME=username

SIP.APPSERVER.PASSWORD=password

Property Value

SIP.DB.CHOICE Database server type. “Oracle”

SIP.ORACLE.CONNECTION.TYPE Connection type. One of the following values:

• Service Name: Connect to Oracle via the service name.



SIP.DB.SERVER Database server name. Example: localhost

SIP.DB.PORT Database port. Example: 1521



PostInstallSetup Properties

If you want to run postInstallSetup as part of a silent install, set this property:

SIP.DB.SID If SIP.ORACLE.CONNECTION.TYPE is "SID", then SIP.DB.SID should be the Oracle Database schema ID (SID). Otherwise, the setting of SIP.DB.SID should be the Oracle service name.

SIP.DB.SCHEMA_NAME Database schema name: Example: cmx_system

SIP.DB.USER Database user name. Example: cmx

SIP.DB.PASSWORD Database password. Example: !!cmx!!

SIP.DB.URL_SILENT only when SIP.ORACLE.CONNECTION.TYPE is "Service Name" and if you want to customize JDBC Connection URL, set SIP.ORACLE.CONNECTION.CUSTOMIZATION to 'Yes'.

Otherwise, either don't use this variable in this file or set it to "No'.

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 variable will be used only when SIP.ORACLE.CONNECTION.CUSTOMIZATION=Yes for oracle in "Service Name" connection type.

Property Value

RUN_DEPLOYMENTSETUP Set this to “Yes” if you want to run postInstallSetup. Set to “No” if you do not want to run postInstallSetup at the end of the install.

Property Value



Properties File for Cleanse Match Server

The following tables contain the properties to be set for Cleanse Match Server silent install properties file.

Set these install directory, license path, and filename properties:

Application Server Properties

Set properties for only one application server: JBoss, WebSphere, or WebLogic.

JBoss Properties

WebLogic Properties

Property Value

INSTALLER_UI silent

USER_INSTALL_DIR Directory to install Cleanse Match Server. Example: <infamdm_install_directory>//hub//cleanse.

SIP.LICENSE.PATH Path to your Informatica license file

SIP.LICENSE.FILENAME License filename (siperian.license)

Property Value

SIP.AS.CHOICE Application server name: “JBoss”

SIP.AS.HOME Path to JBoss home

JBOSS.AS.PORT_1 Your JBoss port number. Example: 8080

SIP.JBOSS.CONFIGURATION_NAME Configuration name. Default is production.

Property Value

SIP.AS.CHOICE Application server name: “WebLogic”

SIP.AS.HOME Path to WebLogic home. Example:C\:\\bea\\user_projects\\domains\\base_domain



WebSphere Properties

Operating Systems

If the operating system (OS) for the installation is Linux, then one of the OS choices must be uncommented in the properties file. Remove the pound sign (#) in front of the property to uncomment it.

SIP.APPSERVER.HOST Host name. Example: localhost

SIP.APPSERVER.SERVER Admin Server name. Example: AdminServer

SIP.APPSERVER.USERNAME User name. Example: weblogic

SIP.APPSERVER.PASSWORD Password. Example: weblogic

SIP.AS.PORT Application server port. Example: 7001

Property Value

SIP.AS.CHOICE Application server name: “WebSphere”

SIP.AS.HOME Path to WebSphere home

Example:C\:\\Program Files\\WebSphere\\AppServer

SIP.AS.SERVER Application server name. Example: server1

SIP.WEBSPHERE.SOAP.PORT Port used for SOAP services. Example: 8880

SIP.WEBSPHERE.SECURITY.ENABLED if SIP.WEBSPHERE.SECURITY.ENABLED is 'Yes', following two properties need to be set

SIP.APPSERVER.USERNAME=username

SIP.APPSERVER.PASSWORD=password

Property Value

SIP.OS.CHOICE=Red Hat Linux Uncomment to use Red Hat Linux

SIP.OS.CHOICE=Suse Linux Uncomment to use SUSE Linux

Property Value



Cleanse Engine Properties

Set the properties for the cleanse engine you will be using with the Informatica Cleanse Match Server.

AddressDoctor Cleanse Engine Properties

FirstLogic Direct Properties

Property Value

SIP.ADDRESSDOCTOR.UNLOCKCODE Your AddressDoctor Cleanse Engine unlock code.

SIP.ADDRESSDOCTOR.OPTIMIZATION AddressDoctor Cleanse Engine optimization setting. Example: ADDRESSES_SORTED_BY_COUNTRIES

SIP.ADDRESSDOCTOR.MEMORYMB AddressDoctor Cleanse Engine memory allocation. Example: 600

SIP.ADDRESSDOCTOR.VALIDATIONTYPE AddressDoctor Cleanse Engine validation type. Example: CORRECT_ONLY

SIP.ADDRESSDOCTOR.PRELOAD.PART AddressDoctor Cleanse Engine preload part setting. Example: US

SIP.ADDRESSDOCTOR.PRELOAD.FULL AddressDoctor Cleanse Engine preload full setting.

SIP.ADDRESSDOCTOR.PRELOAD.CORRECTIONPART

AddressDoctor Cleanse Engine preload correction setting part. Example: CA, US

SIP.ADDRESSDOCTOR.PRELOAD.CORRECTIONFULL

AddressDoctor Cleanse Engine preload correction setting full.

SIP.ADDRESSDOCTOR.DBPATH Path to AddressDoctor Cleanse Engine database. Example: //home//oracle//infamdm//addressdoctor

Property Value

SIP.FLDIRECT.HOST Hostname. Example: localhost

SIP.FLDIRECT.PORT FirstLogic Direct port. Example: 20004



PostInstallSetup Properties

If you want to run postInstallSetup as part of a silent install, set this property:

Restarting Your Operating System

To restart your operating system as a part of the silent install, change the value for these properties:

SIP.FLDIRECT.SUBFILE FirstLogic Direct subfile. Example:

dqxiserver1_substitutions.xml

Property Value

RUN_DEPLOYMENTSETUP Set to one of the following values:

• “Yes” if you want to run postInstallSetup.• “No” if you do not want to run

postInstallSetup at the end of the install.

Property Value

RESTART_NEEDED One of the following values:

• YES to restart.• NO (default) if you do not want to restart.

USER_REQUESTED_RESTART One of the following values:

• YES to restart.

• NO (default) if you do not want to restart.

Property Value



Running the Silent Install

Once you have created the properties files for the Hub Server and Cleanse Match Server, you can run the silent install.

To run the silent installs:1. Make sure that your application server is started and running correctly.

2. For the Hub Server install, run the following command from the command prompt:

./hub_install.bin -f <location_of_silent_properties_file_for_hub_server>

3. For the Cleanse Match Server, run the following command from the command prompt:

./hub_cleanse_install.bin -f <location_of_silent_properties_file_for_cleanse_server>

4. After installation, check the postInstallSetup.log file to see if the installation was successful.

• If you set the RUN_DEPLOYMENTSETUP property to No, check for the existence of the <infamdm_install_directory>/logs/postInstall.log file.

• If you set the RUN_DEPLOYMENTSETUP property to Yes, you can check to see that <infamdm_install_directory/logs/postInstallSetup.log has BUILD SUCCESSFUL (or failure if the install was not successful) at the end of the log file.


B
Manually Configuring Informatica System
Message Queues

This appendix covers the steps for manually configuring JMS message queues and connection factories.

Note: Normally, message queues and connection factories are created automatically during the installation process. These instructions are for troubleshooting purposes if, for example, the automated queue creation process failed or if the queues were dropped accidentally after the installation.

Chapter Contents

• About Informatica MDM Hub Message Queues

• Configuring Message Queues (JBoss/Unix)

• Configure Message Queues (WebLogic/Unix)

• Configuring Message Queues (WebSphere/Unix)

• Configure Message Queues (JBoss/Windows)

• Configure Message Queues (WebLogic/Windows)

• Configure Message Queues (WebSphere / Windows)

355

About Informatica MDM Hub Message Queues

About Informatica MDM Hub Message Queues

The Services Integration Framework (SIF) uses a message-driven bean (MDB) on the JMS queue (named siperian.sif.jms.queue) to process incoming asynchronous SIF requests. This message queue and the connection factory (named siperian.mrm.jms.xaconnectionfactory) need to be configured for the specific application server you are using for your Informatica MDM Hub implementation.

Correctly configuring your message queues is essential to a fully-functioning Informatica MDM Hub installation. The Informatica MDM Hub installer automatically configures your message queues during installation.

Configuring Message Queues (JBoss/Unix)

The JMS message queues are automatically configured by the Informatica installer. To verify that JMS messages queues have been configured correctly., check the JMS configuration under <JBoss_install_dir>/server/<configuration_name>/deploy/messaging. In the siperian-jms-ds.xml file, you should find siperian.mrm.jms.xaconnectionfactory (the XA connection factory), and in siperian-destinations-service.xml file, you should find the file siperian.sif.jms.queue.

The JBoss server is manually configured for Informatica by editing the siperian-destinations-service.xml file to add the message queues and connection factories.



Creating and Configuring a New Message Queue

To configure the message queues and connection factories:1. Open the jboss/server/<configuration_

name>/deploy/messaging/siperian-destinations-service.xml file in an editor.

Add the following queue declaration:

<mbean code="org.jboss.mq.server.jmx.Queue" name="jboss.mq.destination:service=Queue,name=siperian.sif.jms.queue"> <depends optional-attribute-name="DestinationManager"> jboss.mq:service=DestinationManager </depends></mbean>

2. Open the jboss/server/<configuration_name>/deploy/jms/jms-ds.xml file in an editor.

3. Add the following declaration for a JMS connection factory (XA enabled).

<tx-connection-factory> <jndi-name>siperian.mrm.jms.xaconnectionfactory</jndi-name> <xa-transaction/> <rar-name>jms-ra.rar</rar-name> <connection-definition> org.jboss.resource.adapter.jms.JmsConnectionFactory </connection-definition> <config-property name="SessionDefaultType" type="java.lang.String"> javax.jms.Topic </config-property> <config-property name="JmsProviderAdapterJNDI" type="java.lang.String"> java:/DefaultJMSProvider </config-property> <max-pool-size>20</max-pool-size> <security-domain-and-application>JmsXARealm</security-domain-and-application> </tx-connection-factory>

The JBoss JMS message queues and connection factory are now configured.

Manually Configuring Informatica System Message Queues 357


Configuring Additional Message Queues

The following steps enable you to set up message queues for testing. This is also an example of how to step additional queues. These steps are optional.

To configure a test message queue1. Open the jboss/server/<configuration_

name>/deploy/messaging/siperian-destinations-service.xml file in an editor.

2. Add the following queue declaration:

<mbean code="org.jboss.jms.server.destination.QueueService" name="jboss.messaging.destination:service=Queue,name=siperian.sif.test.jms.queue"xmbean-dd="xmdesc/Queue-xmbean.xml"><depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends> <depends>jboss.messaging:service=PostOffice</depends>

</mbean>

<mbean code="org.jboss.jms.server.destination.TopicService" name="jboss.messaging.destination:service=Topic,name=siperian.sif.test.jms.topic"xmbean-dd="xmdesc/Topic-xmbean.xml"><depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends><depends>jboss.messaging:service=PostOffice</depends>

</mbean>

Note: This configuration is needed only for testing purposes.


Configure Message Queues (WebLogic/Unix)


Manually configure the WebLogic application server by creating a new connection factory and message queues.


This section describes how to create and configure a new message queue.

Create a New JMS Server and Module1. Start the WebLogic Console.

Click Lock&Edit.

2. Go to Services > Messaging > JMS Servers.

Create a new JMS Server using the name “SiperianJMSServer”. Click Next.

3. Select the server name in the Target drop-down list.

Click Finish.

4. Go to Services > Messaging > JMS Modules.

Create a new JMS Module using the name “SiperianModule”. Click Next.

5. Choose the Target server by selecting the check box.

Click Next and then click Finish.

Create a Connection Factory for the New Module1. Go to the “SiperianModule” that you just created.

Click New under Summary of Resources.

Choose Connection Factory. Click Next.

2. Specify “siperian.mrm.jms.xaconnectionfactory” for both the name and the JNDI name.

Click Next.

3. Choose Target Server.

Click Finish.



Configure the New Connection Factory1. Go to the siperian.mrm.jms.xaconnectionfactory you just created, under

Configuration.

Click Transactions.

2. Select the XA Connection Factory Enabled check box.

Save the change.

Add Some Message Queues to the Module1. Go to the “SiperianModule” again.


Choose Queue. Click Next.

2. Specify “siperian.sif.jms.queue” for both the name and the JNDI name.

Click Next.

3. Choose the JMS Server you just created.

Click Finish. Click Activate Changes.

Create a New Subdeployment Queue1. Go to the “SiperianModule” once more.



2. Click on the “Create a new Subdeployment” button.

Make sure the Subdeployment Name is “siperian.sif.jms.queue”, and click OK.

3. Use “siperian.sif.jms.queue” for both the name and the JNDI name.

Click Next.

4. Choose the JMS Server you just created and click Finished.


The WebLogic JMS message queues and connection factories are now configured.





To configure a test message queue:1. In the WebLogic Console, click Lock&Edit.


Choose the “SiperianModule”. Click New under Summary of Resources.

3. Choose Queue and click Next.

Specify “siperian.sif.test.jms.queue” for both the name and the JNDI name. Click Next.


Click Finish.

5. Click Activate Changes



Configuring Message Queues (WebSphere/Unix)


Manually configure the WebSphere 6.1 application server by creating a new connection factory and message queues.


Follow these steps to create a new message queue.

Create and Configure a New Bus in the WebSphere Server1. In the WebSphere Console, go to Service integration > Buses.

Create a new bus with name “SiperianBus” and save the change.

2. Go to the SiperianBus you just created and click Bus Members.

Add a new member in the Server drop-down list.

3. Choose the server on which your application is running.

Click Next and select Data Store.

Click Next under this and make sure the Create default data source with generated JNDI name is checked.

4. Click Next, then click Finish. Save the change.

5. Go to the SiperianBus you just created and click Destination.

Click New and choose the Queue as destination type. Click Next.

6. Use the name “SiperianQueue” as the Identifier and click Next.

Choose the Bus member you just created and click Next.

7. Click Finish. Save the change.

Configure a New Connection Factory1. In the WebSphere Console go to Resources > JMS > JMS Providers.

Select “Node=<servername>Node01” from the drop-down list.

Choose Default messaging provider.



2. Click JMS queue connection factory. Configure a new JMS connection factory using “siperian.mrm.jms.xaconnectionfactory” for both the name and the JNDI name.

3. Choose the “SiperianBus” as the Bus name for the JMS connection factory.

Save the change.

4. Click on Queues.

Select the scope “Node=<servername>Node01” from the drop-down list.

Configure a new JMS queue1. Click on the New button.

Select Default messaging provider and click OK.

Use “siperian.sif.jms.queue”for both the name and the JNDI name.

Choose the “SiperianBus” as Bus name, choose the “SiperianQueue” you created as Queue name. Save the change.

2. Click on JMS activation specification. Select the scope “Node=<servername>Node01” from drop-down list.

3. Configure a new Informatica Activation.

Click New. Use “SiperianActivation” for both the name and the JNDI name. Choose Queue as the Destination type and “siperian.sif.jms.queue” as the Destination JNDI name. Choose “SiperianBus” as Bus name. Save the change.




The following steps set up message queues for testing. This is also an example of how to step additional queues. These steps are optional.

Create the Test Message Queue1. In the WebSphere Console, go to Service integration > Buses.

Select the SiperianBus and click Destination.

2. Click New and choose the Queue as destination type. Click Next.

3. Use the name “SiperianTestQueue” as the Identifier and click Next.

4. Choose the Bus member and click Next.

Click Finish and save the change.

Configure the Test Message Queue1. In the WebSphere Console, go to Resources > JMS Providers > Default

Messaging.

Click on Queue and configure a new JMS queue using “siperian.sif.test.jms.queue” for the both name and the JNDI name.

2. Choose “SiperianBus” as Bus name. Choose the “SiperianTestQueue” you just

created as the Queue name.



Configure Message Queues (JBoss/Windows)


The Informatica System message queues are automatically configured by the Informatica installer. To verify that the Informatica System messages queues have been configured correctly., check the JMS configuration under <JBoss_install_dir>\server\<configuration_name>\deploy\messaging. In the file siperian-jms-ds.xml you should find siperian.mrm.jms.xaconnectionfactory (the XA connection factory) and in siperian-destinations-service.xml you should find the file siperian.sif.jms.queue.

The JBoss application server is manually configured for Informatica by editing the siperian-destinations-service.xml file to add the Informatica System message queues and connection factories.


To configure the Informatica System message queues and connection factories1. Open the jboss\server\<configuration_

name>\deploy\jms\siperian-destinations-service.xml file in an editor.

Add the following queue declaration:

<mbean code="org.jboss.jms.server.destination.QueueService" name="jboss.messaging.destination:service=Queue,name=siperian.sif.jms.queue"xmbean-dd="xmdesc/Queue-xmbean.xml"><depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends><depends>jboss.messaging:service=PostOffice</depends> </mbean>

2. Open the jboss\server\<configuration_name>\deploy\messaging\siperian-jms-ds.xml file in an editor.

3. Add the following declaration for a JMS connection factory (XA enabled).

<tx-connection-factory>

<jndi-name>siperian.mrm.jms.xaconnectionfactory</jndi-name>



<xa-transaction/>

<rar-name>jms-ra.rar</rar-name>

<connection-definition>

org.jboss.resource.adapter.jms.JmsConnectionFactory

</connection-definition>

<config-property name="SessionDefaultType" type="java.lang.String">

javax.jms.Topic

</config-property>

<config-property name="JmsProviderAdapterJNDI" type="java.lang.String">

java:/DefaultJMSProvider</config-property>

<max-pool-size>20</max-pool-size>

<security-domain-and-application>JmsXARealm</security-domain-and-application>

<depends>jboss.messaging:service=ServerPeer</depends>

</tx-connection-factory>

The JBoss Informatica System message queues and connection factory are now configured.




The following steps enable you to set up Informatica System message queues for testing. This is also an example of how to step additional queues. These steps are optional.

To configure a test message queue:1. Open the file jboss\server\<configuration_

name>\deploy\messaging\siperian-destinations-service.xml in an editor.

2. Add the following queue declaration:

<mbean code="org.jboss.jms.server.destination.QueueService"name="jboss.messaging.destination:service=Queue,name=siperian.sif.test.jms.queue" xmbean-dd="xmdesc/Queue-xmbean.xml"> <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends><depends>jboss.messaging:service=PostOffice</depends>

</mbean>

<mbean code="org.jboss.jms.server.destination.TopicService"name="jboss.messaging.destination:service=Topic,name=siperian.sif.test.jms.topic"xmbean-dd="xmdesc/Topic-xmbean.xml"><depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends><depends>jboss.messaging:service=PostOffice</depends>

</mbean>



Configure Message Queues (WebLogic/Windows)


Manually configure the WebLogic application server by creating a new connection factory and message queues.



Create a New JMS Server and Module1. Start the WebLogic Console.

Click Lock&Edit.

2. Go to Services > Messaging > JMS Servers.

Create a new JMS Server using the name “SiperianJMSServer”. Click Next.

3. Select the server name in the Target drop-down list.

Click Finish.


Create a new JMS Module using the name “SiperianModule”. Click Next.

5. Choose the Target server by selecting the check box.

Click Next and then click Finish.

Create a Connection Factory for the New Module1. Go to the “SiperianModule” that you just created.


Choose Connection Factory. Click Next.

2. Specify “siperian.mrm.jms.xaconnectionfactory” for both the name and the JNDI name.

Click Next.

3. Choose Target Server.

Click Finish.



Configure the New Connection Factory1. Go to the siperian.mrm.jms.xaconnectionfactory you just created, under

Configuration.

Click Transactions.

2. Select the XA Connection Factory Enabled check box.

Save the change.

Add Some Message Queues to the Module1. Go to the “SiperianModule” again.



2. Specify “siperian.sif.jms.queue” for both the name and the JNDI name.

Click Next.


Click Finish. Click Activate Changes.

Create a New Subdeployment Queue1. Go to the “SiperianModule” once more.



2. Click on the “Create a new Subdeployment” button.

Make sure the Subdeployment Name is “siperian.sif.jms.queue”, and click OK.

3. Use “siperian.sif.jms.queue” for both the name and the JNDI name.

Click Next.

4. Choose the JMS Server you just created and click Finished.


The WebLogic message queues and connection factory are now configured.





To configure additional test message queues:1. In the WebLogic Console, click Lock&Edit.


Choose the “SiperianModule”. Click New under Summary of Resources.

3. Choose Queue and click Next.

Specify “siperian.sif.test.jms.queue” for both the name and the JNDI name. Click Next.


Click Finish.

5. Click Activate Changes.



Configure Message Queues (WebSphere / Windows)


Manually configure the WebSphere 6.1 application server by creating a new connection factory and message queues.



Create and Configure a New Bus1. In the WebSphere Console, go to Service integration > Buses.

Create a new bus with name “SiperianBus” and save the change.

2. Go to the SiperianBus you just created and click Bus Members.

Add a new member in the Server drop-down list.

3. Choose the server your application is running.

Click Next and select Data Store.

Click Next under this and make sure the Create default data source with generated JNDI name is checked.

4. Click Next, then click Finish. Save the change.

5. Go to the SiperianBus you just created and click Destination.

Click New and choose the Queue as destination type. Click Next.

6. Use the name “SiperianQueue” as the Identifier and click Next.

Choose the Bus member you just created and click Next.

7. Click Finish. Save the change.

Configure a New Connection Factory1. In the WebSphere Console go to Resources > JMS > JMS Providers.

Select “Node=<servername>Node01” from the drop-down list.

Choose Default messaging provider.



2. Click JMS queue connection factory. Configure a new JMS connection factory using “siperian.mrm.jms.xaconnectionfactory” for both the name and the JNDI name.

3. Choose the “SiperianBus” as the Bus name for the JMS connection factory.

Save the change.

4. Click on Queues.

Select the scope “Node=<servername>Node01” from the drop-down list.

Configure a New JMS Queue1. Click on the New button.

Select Default messaging provider and click OK. Use “siperian.sif.jms.queue”for both the name and the JNDI name.

Choose the “SiperianBus” as Bus name, choose the “SiperianQueue” you created as Queue name. Save the change.

2. Click on JMS activation specification. Select the scope “Node=<servername>Node01” from drop-down list.

3. Configure a new Informatica Activation.

Click New. Use “SiperianActivation” for both the name and the JNDI name. Choose Queue as the Destination type and “siperian.sif.jms.queue” as the Destination JNDI name. Choose “SiperianBus” as Bus name. Save the change.




The following steps set up message queues for testing. This is also an example of how to step additional queues. These steps are optional.

Create the Test Message Queue1. In the WebSphere Console, go to Service integration > Buses.

Select the SiperianBus and click Destination.

2. Click New and choose the Queue as destination type then click Next.

3. Use the name “SiperianTestQueue” as the Identifier and click Next.

4. Choose the Bus member and click Next.

Click Finish and save the change.

Configure the Test Message Queue1. In the WebSphere Console, go to Resources > JMS Providers > Default

Messaging.

Click on Queue and configure a new JMS queue using “siperian.sif.test.jms.queue” for the both name and the JNDI name.

2. Choose “SiperianBus” as Bus name. Choose the “SiperianTestQueue” you just created as the Queue name.



Index

Aadding message queues

to the module 360application server 44audience xiii

Cchanging

application server and RMI port numberJBoss 306WebLogic 312

Cleanse Match Server parametersWebLogic 311

Cleanse Match Serverabout 110application server instances, configuring

multiple 125, 144, 164, 180, 200,219

cmxcleanse.properties file 176, 196, 215cmxserver.log 269, 272configuration settings 122, 140, 160, 178,

197, 216deploying 181, 201, 220

manually 181, 201, 220deploying manually 126, 145, 165deploying on second application server

instance 126, 144, 165

dual cleanse servers 124, 143, 164, 180,199, 218

logging settings 122, 139, 160, 177, 197,216

multiple, configuring 126, 145, 166multi-threading, configuring 141, 162Oracle TNS server name 123, 140, 161,

178, 198, 217parameters, updating 277post-installation 110temporary files, deleting 122, 139, 160,

177, 197, 216version and build number 121, 139, 159,

177, 196, 215Cleanse Server

silent install, troubleshooting 280, 285CMX_DATA tablespace 22cmx_debug.log 273cmx_debug.log file 269, 273CMX_INDX tablespace 22CMX_ORS User

changing username and password 210cmx_ors.dmpimp.log file 39, 41CMX_TEMP tablespace 22cmxcleanse.properties file 176, 196, 215cmxserver.log file 53, 63, 73, 84, 94, 104,269, 328, 334, 340command line installation

about 324

375

configuring cleanse engines 176, 196, 215configuring dual cleanse servers 180, 199,218connection factory

configuring new 371connection pooling 44console.log file 268, 272contents xivcustomer support xvii

Ddatabase

changingserver name 314

changing Hub Server parameters 314changing instance name 299, 303, 315,

319changing server name 298, 303, 318server and instance name, JBoss 307

databasesconnection testing 32target database 227

debug log file, enabling 270, 273documentation

audience xiiicontents xivother documentation xv

HHub Console

about the Hub Console 224starting 225target database

selecting 227Hub Server

about Hub Server 44application server 44configuration properties 54, 64, 74, 85,

95, 104connection pooling 44database parameters, updating 314, 318deploying manually 290logging settings 54, 64, 74, 85, 95, 104parameters, updating 276silent install, troubleshooting 278, 282WebLogic settings 65, 96

Hub Storeabout the Hub Store 12database configuration options 12installing 17Master Database 12Operational Reference Store (ORS) 12ORS database, creating 36tablespaces, creating 21

Iinfamdm_installer_debug.txt file 53, 63, 73,84, 94, 103, 328, 334, 340Informatica MDM Hub

documentation xvlog files 268, 271

Informatica, contacting xviiinstallation

silent 344installing

Hub Store 17overview of 3


JJBoss

changing Application Server and RMIport number 289

changing database server and instancename 307

changing settings 86Cleanse Match Server and Hub Server,

configuring 116Hub Server

changing parameters 306parameters, updating 289, 306

port conflicts 86settings 55, 86

Llicense file 47, 58, 68, 78, 89, 99, 114, 130,149, 170, 185, 205, 324log files

cmx_debug.log file 269cmx_ors.dmpimp.log file 39, 41cmxserver.log file 53, 63, 73, 84, 94, 104,

269, 328, 334, 340console.log file 268infamdm_installer_debug.txt file 53, 63,

73, 84, 94, 103, 328, 334, 340Informatica_MDM_Hub_Server_Install-

Log.xml file 53, 63, 73, 84, 94,103, 327, 334, 340

location, changing 271maintaining 271overview of 268postInstallSetup.log file 53, 63, 73, 84,

94, 103, 328, 334, 340

setup_ors.log file 39, 41

MMaster Database 12Master Reference Manager

cmxserver.log 269, 272match process error

VerifyNeedToStrip 287message queues

configuring additionalJBoss 367WebLogic 9.x 370WebSphere 6.1 373

using 355WebLogic

9.x configuration 368

OOperational Reference Stores (ORS)

about ORSs 12Oracle

TNS nameadding to the ORS database 178, 198,

217ORS database

creating additional 36

Ppassword

changing for CMX_SYSTEM user 208port conflicts 86postInstallSetup.log file 53, 63, 73, 84, 94,103, 328, 334, 340

377

SServices Integration Framework Guide (SIF)xvisetup_ors.log file 39, 41silent install

Cleanse Server, troubleshooting 280, 285Hub Server, troubleshooting 278, 282troubleshooting 278, 282

silent install, from command line 344silent installation 344support xvii

Ttablespaces

CMX_DATA 22CMX_INDX 22CMX_TEMP 22creating 21temporary tablespace 41

target databaseselecting 227

technical support xviitroubleshooting

changing domain, WebLogic 309cmxserver.log file 272log files

cmx_debug.log file 273cmxserver.log file 272console.log file 272location of 274log4j.xml file 274overview of 271

log4j.xml file 274

silent install 278, 282silent install, Cleanse Server 280, 285silent install, Hub Server 278, 282WebLogic

changing domain 312changing host or server name 311changing Hub Server parameters 309changing RMI Port Number 310changing username 310changing username and password 313Cleanse Match Server parameters,

updating 311, 317

Uuninstalling

Hub Store 264

VVerifyNeedToStrip error message 287version and build number

checking 177, 196, 215

WWebLogic

changinghost or server name, troubleshooting

313changing Application Server and RMI

port number 296changing domain, troubleshooting 309changing settings 96Cleanse Match Server


parameters, updating 295, 302configuration 359Hub Server

parameters, updating 292, 309settings 65, 96

WebSpherechanging Hub Server parameters 317

changing settings 105Hub Server

parameters, updating 301, 317settings 74, 105

WebSphere 6.1configure a new JMS queue 372

WebSphere Server cluster 245

379

mdm 901 install guide

Documents

informatica platform

informatica data explorer

informatica data quality

informatica data services

apache license

software andor documentation

informatica b2b data

product names