MDM Multidomain Edition (Version 9.0.1) Installation Guide

Transcription

1 MDM Multidomain Edition (Version 9.0.1) Installation Guide

2 Informatica MDM Multidomain Hub - Version September 2010, revised October 2010 Copyright (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 (a) and (a) (1995), DFARS (1)(ii) (OCT 1988), FAR (a) (1995), FAR , or FAR (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 ( and other software which is licensed under the Apache License, Version 2.0 (the License ). You may obtain a copy of the License at 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 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 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 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) , Terence Parr, all rights reserved which is licensed under the BSD License (the License ). You may obtain a copy of the License at 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) The Legion Of The Bouncy Castle ( which is licensed under a form of the MIT License (the License ). You may obtain a copy of the License at 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.

3 Contents Preface Intended Audience...xiii Contents...xiv Learning About Informatica MDM Hub...xv Informatica Global Customer Support...xvii Informatica Resources...xviii Informatica Customer Portal...xviii Informatica Documentation...xviii Informatica Web Site...xix Informatica How-To Library...xix Informatica Knowledge Base...xix Informatica Multimedia Knowledge Base...xix Chapter 1: Introduction Before You Begin...2 Installation Overview...3 Designing Your Informatica MDM Hub Installation...4 Implementation Components...4 Installation Environments...5 Example Installations...5 Documenting Your Installation...8 Installation and Post-Installation Documentation...8 Create an Installation Documentation Directory...9 Chapter 2: Installing the Hub Store About the Hub Store...12 Master Database and Operational Reference Store (ORS)...12 iii

4 Relationships Among Databases in the Hub Store Single Informatica MDM Hub Version Requirement Oracle RAC Considerations Overview of Steps to Install the Hub Store Prepare Your Oracle Deployment for Informatica MDM Hub Install and Configure Oracle Turning Off the Oracle Recycle Bin Setting Oracle PLSQL Compiler Flags (Oracle 10gR2 Only) Create an Oracle Database for the Hub Store Create Tablespaces Used by the Hub Store Tablespaces to Create Creating CMX_DATA Creating CMX_INDX Creating CMX_TEMP Create the Hub Store About the setup.sql Script Create the Hub Store (Unix) Create the Hub Store (Windows) Test the Database Connection Create a Proxy User Proxy Users in Informatica MDM Hub Implementations Creating a Proxy User Create an Additional ORS Database About the setup_ors.sql Script Adding an ORS (Unix) Adding an ORS (Windows) Chapter 3: Installing the Hub Server About the Hub Server Application Server and Connection Pooling Manually Configuring Message Queues for Asynchronous SIF Requests PostInstallSetup Single Informatica MDM Hub Version Requirement iv Informatica MDM Hub Installation Guide

5 Installing the Hub Server (JBoss/Unix)...46 Installation Overview...46 Preparing for Installation...46 Running the Hub Server Installer...49 Configuring the Hub Server...54 Performing Post-Installation Tasks...56 Installing the Hub Server (WebLogic/Unix)...57 Installation Overview...57 Preparing for Installation...57 Running the Hub Server Installer...59 Configuring the Hub Server...64 Performing Post-Installation Tasks...66 Installing the Hub Server (WebSphere/Unix)...67 Installation Overview...67 Preparing for Installation...67 Running the Hub Server Installer...69 Configuring the Hub Server...73 Performing Post-Installation Tasks...75 Installing the Hub Server (JBoss/Windows)...77 Installation Overview...77 Preparing for Installation...78 Running the Hub Server Installer...81 Configuring the Hub Server...85 Performing Post-Installation Tasks...87 Installing the Hub Server (WebLogic/Windows)...88 Installation Overview...88 Preparing for Installation...88 Running the Hub Server Installer...90 Configuring the Hub Server...95 Performing Post-Installation Tasks...97 Installing the Hub Server (WebSphere/Windows)...98 Installation Overview...98 Preparing for Installation...98 Contents v

6 Running the Hub Server Installer Configuring the Hub Server Performing Post-Installation Tasks Changing Passwords After Installation Changing the Password for the CMX_SYSTEM User Changing the Password for the CMX_ORS User Chapter 4: Installing the Cleanse Match Server About the Cleanse Match Server Supported Cleanse Match Engines PostInstallSetup Single Informatica MDM Hub Version Requirement Installing the Cleanse Match Server (JBoss/Unix) Installation Overview Preparing for Installation Running the Cleanse Match Server Installer Configuring the Cleanse Match Server Performing Post-installation Tasks Installing the Cleanse Match Server (WebLogic/Unix) Installation Overview Preparing for Installation Running the Cleanse Match Server Installer Configuring the Cleanse Match Server Performing Post-installation Tasks Installing the Cleanse Match Server (WebSphere/Unix) Installation Overview Preparing for Installation Running the Cleanse Match Server Installer Configuring the Cleanse Match Server Performing Post-installation Tasks Installing the Cleanse Match Server (JBoss/Windows) Installation Overview Preparing for Installation vi Informatica MDM Hub Installation Guide

7 Running the Cleanse Match Server Installer Configuring the Cleanse Match Server Performing Post-installation Tasks Installing the Cleanse Match Server (WebLogic/Windows) Installation Overview Preparing for Installation Running the Cleanse Match Server Installer Configuring the Cleanse Match Server Performing Post-installation Tasks Installing the Cleanse Match Server (WebSphere/Windows) Installation Overview Preparing for Installation Running the Cleanse Match Server Installer Configuring the Cleanse Match Server Performing Post-installation Tasks Chapter 5: Launching the Hub Console About the Hub Console Starting the Hub Console Post-setup Tasks Chapter 6: Clustering Installing the Hub Server into a WebLogic Server Cluster (Unix) Installation Overview Creating a WebLogic Cluster Installing the Hub Server on Nodes in the Cluster Configuring Services and Deploying the Hub Server Deploying the Cleanse Match Server Installing the Hub Server into a WebSphere Server Cluster (Unix) Installation Overview Before You Install Installing the Hub Server and Cleanse Match Server Software Contents vii

8 Creating a WebSphere Cluster Configuring Services and Deploying the Hub Server Deploying the Cleanse Match Server Installing the Hub Server into a WebLogic Server Cluster (Windows) Installation Overview Creating a WebLogic Cluster Installing the Hub Server on Nodes in the Cluster Configuring Services and Deploying the Hub Server Deploying the Cleanse Match Server Installing the Hub Server into a WebSphere Server Cluster (Windows) Installation Overview Before You Install Installing the Hub Server and Cleanse Match Server Software Creating a WebSphere Cluster Configuring Services and Deploying the Hub Server Deploying the Cleanse Match Server Chapter 7: Uninstalling Informatica MDM Hub Uninstalling Informatica MDM Hub (JBoss / Unix) Uninstalling the Cleanse Match Server Uninstalling the Hub Server Uninstalling Informatica MDM Hub (WebLogic / Unix) Uninstalling the Cleanse Match Server Uninstalling the Hub Server Uninstalling Informatica MDM Hub (WebSphere / Unix) Uninstalling the Cleanse Match Server Uninstalling the Hub Server Uninstalling Informatica MDM Hub (JBoss / Windows) Uninstalling the Cleanse Match Server Uninstalling the Hub Server Uninstalling Informatica MDM Hub (WebLogic / Windows) Uninstalling the Cleanse Match Server Uninstalling the Hub Server viii Informatica MDM Hub Installation Guide

9 Uninstalling Informatica MDM Hub (WebSphere / Windows) Uninstalling the Cleanse Match Server Uninstalling the Hub Store from Oracle Database Objects to Drop Dropping Hub Store Databases Uninstalling the Hub Server Chapter 8: Troubleshooting Informatica MDM Hub Log Files Informatica MDM Hub Log Files (Unix) Informatica MDM Hub Log Files (Windows) ORS Debug Log Setup Bypassing Prerequisite Installation Updating Parameters After Installation Updating Hub Server Parameters After Installation Updating Cleanse Match Server Parameters After Installation Checking the Hub and Cleanse Match Server Silent Install Checking the Hub Server and Cleanse Match Server Silent Install (Unix) Checking the Hub Server and Cleanse Match Server Silent Install (Windows) MATCH Process Error: VerifyNeedToStrip VerifyNeedToStrip (Unix) VerifyNeedToStrip (Windows) Inaccurate Start/Stop Timestamp for ORS major.minor Version Errors When Loading Cleanse Match Server Low Cleanse/Match Application Server Performance Troubleshooting (JBoss / Unix) Changing the Hub Server Parameters (JBoss/Unix) Manually Redeploying the Hub Server (JBoss/Unix) Manually Undeploying the Cleanse Match Server (JBoss/Unix) Setting the JVM Size (JBoss/Unix) Troubleshooting (WebLogic / Unix) Changing the Hub Server Parameters (WebLogic/Unix) Contents ix

10 Changing the Cleanse Match Server Parameters (WebLogic/Unix) Changing the Hub Server Parameters for the Database (WebLogic/Unix) Manually Redeploying Hub Server (WebLogic/Unix) Manually Undeploying the Cleanse Match Server (WebLogic/Unix) Setting the JVM Size (WebLogic/Unix) Troubleshooting (WebSphere / Unix) Changing the Hub Server Parameters (WebSphere/Unix) Changing the Cleanse Match Server Parameters (WebSphere/Unix) Changing the Hub Server Parameters for the Database (WebSphere/Unix) Manually Redeploying the Hub Server Application (WebSphere/Unix) Manually Undeploying the Cleanse Match Server (WebSphere/Unix) Setting the JVM Size (WebSphere/Unix) Changing the SOAP Request Timeout (WebSphere/Unix) Troubleshooting (JBoss / Windows) Changing the Hub Server Parameters (JBoss/Windows) Manually Redeploying Hub Server (JBoss/Windows) Manually Undeploying the Cleanse Match Server (JBoss/Windows) Setting the JVM Size (JBoss/Windows) Troubleshooting (WebLogic / Windows) Changing the Hub Server Parameters (WebLogic/Windows) Changing the Cleanse Match Server Parameters (WebLogic/Windows) Changing the Hub Server Parameters for the Database (WebLogic/Windows) Manually Redeploying Hub Server (WebLogic/Windows) Manually Undeploying the Cleanse Match Server (WebLogic/Windows) Setting the JVM Size (WebLogic/Windows) Troubleshooting (WebSphere / Windows) Changing the Hub Server Parameters (WebSphere/Windows) Changing the Cleanse Match Server Parameters (WebSphere/Windows) Changing the Hub Server Parameters for the Database (WebSphere/Windows) Manually Redeploying Hub Server (WebSphere/Windows) Manually Undeploying the Cleanse Match Server (WebSphere/Windows) Setting the JVM Size (WebSphere/Windows) Changing the SOAP Request Timeout (WebSphere/Windows) x Informatica MDM Hub Installation Guide

11 Appendix A: Installing from the Command Line Preparing for Installation Installing from the Command Line (JBoss/Unix) Installing Hub Server Installing the Cleanse Match Server Installing from the Command Line (WebLogic/Unix) Installing the Hub Server Installing the Cleanse Match Server Installing from the Command Line (WebSphere/Unix) Installing Hub Server Installing the Cleanse Match Server Silent Installation from the Command Line Considerations When Using Silent Installation Properties Files for Silent Installation Creating Your Properties File Running the Silent Install Appendix B: Manually Configuring Informatica System Message Queues About Informatica MDM Hub Message Queues Configuring Message Queues (JBoss/Unix) Creating and Configuring a New Message Queue Configuring Additional Message Queues Configure Message Queues (WebLogic/Unix) Creating and Configuring a New Message Queue Configuring Additional Message Queues Configuring Message Queues (WebSphere/Unix) Creating and Configuring a New Message Queue Configuring Additional Message Queues Configure Message Queues (JBoss/Windows) Creating and Configuring a New Message Queue Configuring Additional Message Queues Configure Message Queues (WebLogic/Windows) Contents xi

12 Creating and Configuring a New Message Queue Configuring Additional Message Queues Configure Message Queues (WebSphere / Windows) Creating and Configuring a New Message Queue Configuring Additional Message Queues xii Informatica MDM Hub Installation Guide

13 Preface Welcome to the Informatica MDM Hub 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

14 Contents Contents This guide contains the following chapters. 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 Chapter 5, Launching the Hub Console Chapter 6, Clustering Chapter 7, Uninstalling Informatica MDM Hub Chapter 8, Troubleshooting Appendix A, Installing from the Command Line Appendix B, Manually Configuring Informatica System Message Queues Index Explains how to install and configure Cleanse Match Server Explains how to launch the Hub Console Explains how to configure clustering for Informatica MDM Hub. Explains how to uninstall your Informatica MDM Hub system Explains how to troubleshoot your installation Explains how to install Informatica Hub Server and Cleanse Match Server from the command line. Unix implementations only. Explains how to configure message queues for use with Informatica MDM Hub. Index for this guide For more detail on the property files for the MDM Hub, see the appendices in the Informatica MDM Hub Administrator Guide. xiv Informatica MDM Hub Installation Guide

15 Learning About Informatica MDM Hub 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

16 Learning About Informatica MDM Hub 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 Installation Guide

17 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. Informatica Global Customer Support 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 Use the following telephone numbers to contact Informatica Global Customer Support: North America / South America Toll Free North America Brazil Mexico Europe / Middle East / Africa Toll Free United Kingdom or France Netherlands Germany Switzerland Israel Spain Portugal Italy Asia / Australia Toll Free Australia New Zealand Singapore xvii

18 Informatica Resources North America / South America Standard Rate North America Europe / Middle East / Africa Standard Rate Belgium France Germany Netherlands Switzerland Asia / Australia Standard Rate India Informatica Resources Informatica Customer Portal As an Informatica customer, you can access the Informatica Customer Portal site at 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 at infa_ documentation@informatica.com. 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 xviii Informatica MDM Hub Installation Guide

19 Informatica Resources Informatica Web Site You can access the Informatica corporate web site at 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 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 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 at KB_Feedback@informatica.com. Informatica Multimedia Knowledge Base As an Informatica customer, you can access the Informatica Multimedia Knowledge Base at 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 at KB_Feedback@informatica.com. xix

20 Informatica Resources xx Informatica MDM Hub Installation Guide

21 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

22 Before You Begin Before You Begin Before you begin, be sure to complete the following tasks: Task Read the Informatica MDM Hub Release Notes for requirements and additional information about pre-installation preparation. 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. Read the Informatica MDM Hub Overview for an introduction to the product architecture and key components. Resource Informatica MDM Hub Release Notes Informatica Global Customer Support Vendor documentation for your cleanse engine Informatica MDM Hub Overview 2 Informatica MDM Hub Installation Guide

23 Installation Overview 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 Installing the Hub Store on page 11 database. 2 Install the Hub Server software. Installing the Hub Server on page 43 3 Install and configure one or more Cleanse Match Servers. 4 Launch the Hub Console and verify your installation. Installing the Cleanse Match Server on page 109 Launching the Hub Console on page 223 Introduction 3

24 Designing Your Informatica MDM Hub Installation 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 Hub Store Hub Server Cleanse Match Server Cleanse Engine(s) Description 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). 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. 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. 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. 4 Informatica MDM Hub Installation Guide

25 Designing Your Informatica MDM Hub Installation 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

26 Designing Your Informatica MDM Hub Installation 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. 6 Informatica MDM Hub Installation Guide

27 Designing Your Informatica MDM Hub Installation 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

28 Documenting Your Installation 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: Information About ORS metadata configuration settings database changes installation process Hub Server and Cleanse Match Server Hub Console Source of Information 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. 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 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. 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 log files, which capture run-time events after these components are running. Hub Console log files that capture activity while using the Hub Console. 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. 8 Informatica MDM Hub Installation Guide

29 Documenting Your Installation 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

30 Documenting Your Installation 10 Informatica MDM Hub Installation Guide

31 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

32 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: Element Master Database Operational Reference Store (ORS) Description 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. 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. 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. 12 Informatica MDM Hub Installation Guide

33 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

34 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) ) 14 Informatica MDM Hub Installation Guide

35 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: Component Batch Jobs SIF API Connections Description When called from a command line, because batch jobs use the tnsnames.ora settings. Use load-balanced JDBC connections from the application server connection pool. Installing the Hub Store 15

36 About the Hub Store Component Cleanse Server Metadata Manager Description Uses load-balanced JDBC connections from the cleanse server connection pool. When only DML is required uses the application server connection pool. 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) 16 Informatica MDM Hub Installation Guide

37 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: Step Task Instructions 1 Install and configure Oracle on a machine other than the machine on which your Hub Server will run. 2 Create an Oracle database for your Hub Store. 3 Create the Oracle tablespaces required for the Hub Store. 4 Create the Hub Store Master Database and ORS database(s) by running the setup.sql script provided in your Informatica MDM Hub distribution. Prepare Your Oracle Deployment for Informatica MDM Hub on page 18 Oracle documentation Create Tablespaces Used by the Hub Store on page 21 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. 7 Enable database logging for this ORS using the Enterprise Manager 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) Appendix D, Viewing Configuration Details, in the Informatica MDM Hub Administrator Guide (see Post-setup Tasks on page 229) 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. Installing the Hub Store 17

38 Prepare Your Oracle Deployment for Informatica MDM Hub 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. 18 Informatica MDM Hub Installation Guide

39 Prepare Your Oracle Deployment for Informatica MDM Hub 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. Installing the Hub Store 19

40 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 20 Informatica MDM Hub Installation Guide

41 Create Tablespaces Used by the Hub Store 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: Tablespace Description Instructions CMX_DATA Default tablespace for the ORS Creating CMX_DATA on page 22 schema. CMX_INDX Used for indexes created and used by Creating CMX_INDX on page 22 Informatica MDM Hub. CMX_TEMP Used for temporary tables created and used by Informatica MDM Hub; used for stored procedures. Creating CMX_TEMP on page 22 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. Installing the Hub Store 21

42 Create Tablespaces Used by the Hub Store Creating CMX_DATA Creating CMX_INDX Create the CMX_DATA tablespace as a locally-managed or manually-configured tablespace. Use commands similar to the following example. CREATE TABLESPACE CMX_DATA NOLOGGING DATAFILE '<Oracle_install_dir>/CMX_DATA1.dbf' SIZE 2048M REUSE EXTENT MANAGEMENT LOCAL; COMMIT; where <Oracle_install_dir> is your Oracle installation directory (also known as ORACLE_BASE). 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; where <Oracle_install_dir> is your Oracle installation directory (also known as ORACLE_BASE). 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_TEMP NOLOGGING DATAFILE '<Oracle_install_dir>/CMX_TEMP1.dbf' SIZE 2048M REUSE EXTENT MANAGEMENT LOCAL; 22 Informatica MDM Hub Installation Guide

43 Create the Hub Store COMMIT; where <Oracle_install_dir> is your Oracle installation directory (also known as ORACLE_BASE). Create the Hub Store 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 Installing the Hub Store 23

44 Create the Hub Store 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 OR start setup.sql 5. Answer the following prompts: 24 Informatica MDM Hub Installation Guide

45 Create the Hub Store 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 Enter Oracle Server TNS name: Enter Oracle Connection Type (SERVICE, SID) [SERVICE]: Enter Oracle SERVICE name: Enter Oracle SID Name: Enter Oracle Listener Port number [1521]: Enter Oracle database server name: Description 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. 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. Name of the Oracle SERVICE. Displayed only if the selected Oracle Connection Type is SERVICE. Name of the Oracle SID. Displayed only if the selected Oracle Connection Type is SID. Port number used by the Oracle listener. Name of the host running Oracle. Installing the Hub Store 25

46 Create the Hub Store Prompt Enter Connect URL (only for SERVICE type): Enter Oracle SYSTEM username: [SYSTEM] Enter Oracle SYSTEM password: Enter name of new CMX System (Master) user [CMX_SYSTEM]: Enter Name of Data tablespace [CMX_ DATA]: Enter name of Temporary tablespace [TEMP]: Import into CMX_SYSTEM: Enter the Oracle export file name [cmx_ system.dmp] Import into CMX_SYSTEM: Enter the source schema name (fromuser) for the export file [CMX_SYSTEM]: Description Custom SERVICE Connect URL here for RAC (if different from the default). Format: host:port/service_name Example: 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 Oracle SYSTEM username. Password for the Oracle SYSTEM account. Oracle user name that the script creates. This user owns all the Master Database database objects in the Hub Store. Name of the tablespace to contain the data components for the Master Database. See Creating CMX_DATA on page 22. Name of the tablespace to contain the temporary components for the Master Database. See Creating CMX_TEMP on page 22. 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. Username under which the cmx_system.dmp file was exported. Accept the default. Do not change this username. 26 Informatica MDM Hub Installation Guide

47 Create the Hub Store Prompt Enter name of User [CMX_ORS]: Enter password for ORS User [!!CMX!!]: Enter name of MRM Data tablespace [CMX_DATA]: Enter name of MRM Index tablespace [CMX_INDX]: Enter name of MRM Temporary tablespace (Not an Oracle temp tablespace) [CMX_TEMP]: Enter name of the Oracle Temporary tablespace [TEMP]: Enter GGS install path if applicable: Import into ors_name: Enter the Oracle export file name [cmx_ ors.dmp]: Import into ors_name: Enter source schema name (fromuser) for the export file [CMX_ORS]: Description Oracle user name that the script creates. This user owns all the ORS database objects in the Hub Store. Password for the CMX_ORS user account. Name of the tablespace to contain the data components for the ORS. See Creating CMX_ DATA on page 22. 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. 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. 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. Username under which the ORS dump file was exported. Accept the default. Do not change this username. 6. After the setup script is complete, check the following log files: setup.log cmx_sys_imp.log cmx_ors_imp.log Installing the Hub Store 27

48 Create the Hub Store 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: 28 Informatica MDM Hub Installation Guide

49 Create the Hub 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 Enter Oracle Server TNS name: Enter Oracle Connection Type (SERVICE, SID) [SERVICE]: Enter Oracle SERVICE name: Enter Oracle SID Name: Enter Oracle Listener Port number [1521]: Enter Oracle database server name: Description 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. 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. Name of the Oracle SERVICE. Displayed only if the selected Oracle Connection Type is SERVICE. Name of the Oracle SID. Displayed only if the selected Oracle Connection Type is SID. Port number used by the Oracle listener. Name of the host running Oracle. Installing the Hub Store 29

50 Create the Hub Store Prompt Enter Connect URL (only for SERVICE type): Enter Oracle SYSTEM username: [SYSTEM] Enter Oracle SYSTEM password: Enter name of new CMX System (Master) user [CMX_SYSTEM]: Enter Name of Data tablespace [CMX_ DATA]: Enter name of Temporary tablespace [TEMP]: Import into CMX_SYSTEM: Enter the Oracle export file name [cmx_ system.dmp] Import into CMX_SYSTEM: Enter the source schema name (fromuser) for the export file [CMX_SYSTEM]: Enter name of User [CMX_ORS]: Description Custom SERVICE Connect URL here for RAC (if different from the default). Format: host:port/service_name Example: 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. Oracle SYSTEM username. Password for the Oracle SYSTEM account. Oracle user name that the script creates. This user owns all the Master Database database objects in the Hub Store. Name of the tablespace to contain the data components for the Master Database. See Creating CMX_DATA on page 22. Name of the tablespace to contain the temporary components for the Master Database. See Creating CMX_TEMP on page 22. 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. Username under which the cmx_system.dmp file was exported. Accept the default. Do not change this username. Oracle user name that the script creates. This user owns all the ORS database objects in the Hub Store. 30 Informatica MDM Hub Installation Guide

51 Create the Hub Store Prompt Enter password for ORS User [!!CMX!!]: Enter name of MRM Data tablespace [CMX_DATA]: Enter name of MRM Index tablespace [CMX_INDX]: Enter name of MRM Temporary tablespace (Not an Oracle temp tablespace) [CMX_TEMP]: Enter name of the Oracle Temporary tablespace [TEMP]: Enter GGS install path if applicable: Import into ors_name: Enter the Oracle export file name [cmx_ ors.dmp]: Import into ors_name: Enter source schema name (fromuser) for the export file [CMX_ORS]: Description Password for the CMX_ORS user account. Name of the tablespace to contain the data components for the ORS. See Creating CMX_ DATA on page 22. 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. 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. 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. Username under which the ORS dump file was exported. Accept the default. Do not change this username. 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. Installing the Hub Store 31

52 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 Informatica MDM Hub Installation Guide

53 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. Installing the Hub Store 33

54 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. 34 Informatica MDM Hub Installation Guide

55 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. Installing the Hub Store 35

56 Create an Additional ORS Database 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. 36 Informatica MDM Hub Installation Guide

57 Create an Additional ORS Database 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 HP-UX: start setup_ors.sql 5. Answer the following prompts: 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 Enter name of User [CMX_ORS]: Enter password for ORS User [!!CMX!!]: Enter name of MRM Data tablespace [CMX_DATA]: Description 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. Password for the CMX_ORS user account. Name of the tablespace to contain the data components for the ORS. See Creating CMX_ DATA on page 22. Installing the Hub Store 37

58 Create an Additional ORS Database Prompt Enter name of MRM Index tablespace [CMX_INDX]: Enter name of MRM Temporary tablespace (Not an Oracle temp tablespace) [CMX_TEMP]: Enter name of the Oracle Temporary tablespace [TEMP]: Enter ORACLE server TNS name: Enter name of DBA User [SYSTEM]: Enter password of DBA User: Enter file to import [cmx_ors.dmp]: Enter import fromuser name [cmx_ors]: Enter GGS install path: Description Name of the tablespace to contain the indexes. See Creating CMX_INDX on page 22. Name of the tablespace to contain the temporary components for the Master Database. See Creating CMX_TEMP 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. 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. Oracle user account with administrative access, such as the Oracle SYSTEM username. Password for the specified DBA User account. 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. 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. 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. 6. After the setup scripts are complete, there are log files in the temporary directory from which you ran the scripts: 38 Informatica MDM Hub Installation Guide

59 Create an Additional ORS Database setup_ors.log cmx_ors.dmpimp.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 7. Answer the following prompts: Installing the Hub Store 39

60 Create an Additional ORS Database 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 Enter name of User [CMX_ORS]: Enter password for ORS User [!!CMX!!]: Enter name of MRM Data tablespace [CMX_DATA]: Enter name of MRM Index tablespace [CMX_INDX]: Enter name of MRM Temporary tablespace (Not an Oracle temp tablespace) [CMX_TEMP]: Enter name of the Oracle Temporary tablespace [TEMP]: Enter ORACLE server TNS name: Enter name of DBA User [SYSTEM]: Enter password of DBA User: Description 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. Password for the CMX_ORS user account. Name of the tablespace to contain the data components for the ORS. See Creating CMX_ DATA on page 22. Name of the tablespace to contain the indexes. See Creating CMX_INDX on page 22. Name of the tablespace to contain the temporary components for the Master Database. See Creating CMX_TEMP 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. 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. Oracle user account with administrative access, such as the Oracle SYSTEM username. Password for the specified DBA User account. 40 Informatica MDM Hub Installation Guide

61 Create an Additional ORS Database Prompt Enter file to import [cmx_ors.dmp]: Enter import fromuser name [cmx_ors]: Enter GGS install path: Description 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. 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. 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. 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 cmx_ors.dmpimp.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. Installing the Hub Store 41

62 Create an Additional ORS Database 42 Informatica MDM Hub Installation Guide

63 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

64 About the Hub Server 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. 44 Informatica MDM Hub Installation Guide

65 About the Hub Server 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. 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 Server 45

66 Installing the Hub Server (JBoss/Unix) 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 or higher. Installation Overview Hub Server installation involves the following steps: Step Task Instructions 1 Prepare the target environment, including Preparing for Installation on page 46 setting up the application server. 2 Install the Hub Server by running the installer. 3 Specify or change Hub Server configuration settings. Preparing for Installation Running the Hub Server Installer on page 49 Configuring the Hub Server on page 54 Complete the tasks in this section before you install the Hub Server. 46 Informatica MDM Hub Installation Guide

67 Installing the Hub Server (JBoss/Unix) 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. Installing the Hub Server 47

68 Installing the Hub Server (JBoss/Unix) 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: <!-- Uncomment to require authenticated users > <interceptor code="org.jboss.jmx.connector.invoker.authenticationinterceptor" securitydomain="java:/jaas/jmx-console"/ --> 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 ga/bin 2. Run the following command: run.sh -b Informatica MDM Hub Installation Guide

69 Installing the Hub Server (JBoss/Unix) 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: Installing the Hub Server 49

70 Installing the Hub Server (JBoss/Unix)./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. 50 Informatica MDM Hub Installation Guide

71 Installing the Hub Server (JBoss/Unix) 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. Installing the Hub Server 51

72 Installing the Hub Server (JBoss/Unix) 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. 52 Informatica MDM Hub Installation Guide

73 Installing the Hub Server (JBoss/Unix) 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 <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 (such as <JBoss_install_ dir>/server/<configuration_name>/log/server.log) Description Contains log messages for the Hub Server installation. Contains the prerequisite messages generated during installation. Contains debug messages. Contains the postinstallsetup messages for the script. Hub Server log. When the server started, it created this file. Located in the tree under the JBoss install directory. Installing the Hub Server 53

74 Installing the Hub Server (JBoss/Unix) 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. 54 Informatica MDM Hub Installation Guide

75 Installing the Hub Server (JBoss/Unix) Your file looks similar to this: cmx.home=/infamdm/hub/server cmx.server.masterdatabase.type=oracle cmx.appserver.type=jboss cmx.appserver.rmi.port=1099 cmx.appserver.naming.protocol=jnp jnlp.initial-heap-size=128m jnlp.max-heap-size=192m cmx.server.datalayer.cleanse.execution=server cmx.server.datalayer.cleanse.working_ files.location=/infamdm/hub/server/logs cmx.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 Restart the application server. Installing the Hub Server 55

76 Installing the Hub Server (JBoss/Unix) 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 Informatica MDM Hub Installation Guide

77 Installing the Hub Server (WebLogic/Unix) 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. Installation Overview Hub Server installation involves the following steps: Step Task Instructions 1 Prepare the target environment, including Preparing for Installation on page 57 setting up the application server. 2 Install the Hub Server by running the installer. 3 Specify or change Hub Server configuration settings. Preparing for Installation Running the Hub Server Installer on page 59 Configuring the Hub Server on page 64 Complete the tasks in this section before you install the Hub Server. Installing the Hub Server 57

78 Installing the Hub Server (WebLogic/Unix) 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 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). 58 Informatica MDM Hub Installation Guide

79 Installing the Hub Server (WebLogic/Unix) 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. 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. Installing the Hub Server 59

80 Installing the Hub Server (WebLogic/Unix) 3. Go to the directory where the Informatica MDM Hub 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 the I accept the terms of the License Agreement button 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. 60 Informatica MDM Hub Installation Guide

81 Installing the Hub Server (WebLogic/Unix) 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 WebLogic. Click Next. The WebLogic Application Server Home screen is displayed. 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. 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 Host Server User Name Password Port Number Description Name of the host computer on which WebLogic is installed. Name of the server on which WebLogic is deployed. Name of the user for the WebLogic installation. Password that corresponds to the WebLogic user. Port number on which your WebLogic Server is listening. Installing the Hub Server 61

82 Installing the Hub Server (WebLogic/Unix) 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. 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. 62 Informatica MDM Hub Installation Guide

83 Installing the Hub Server (WebLogic/Unix) 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 <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 WebLogic log files under <weblogic_domain>/servers/<weblogic_ server>/logs.: access.log, <weblogic_server>.log and <weblogic_ domain>.log Description Contains log messages for the Hub Server installation. Contains the prerequisite messages generated during installation. Contains debug messages. Contains the postinstallsetup messages for the script. Hub Server log. When the server started, it created this file. Located in the tree under the WebLogic install directory. Installing the Hub Server 63

84 Installing the Hub Server (WebLogic/Unix) 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. 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/server cmx.server.masterdatabase.type=oracle cmx.appserver.type=weblogic cmx.appserver.rmi.port= Informatica MDM Hub Installation Guide

85 Installing the Hub Server (WebLogic/Unix) cmx.appserver.naming.protocol=t3 jnlp.initial-heap-size=128m jnlp.max-heap-size=192m cmx.server.datalayer.cleanse.execution=server cmx.server.datalayer.cleanse.working_ files.location=/infamdm/hub/server/logs cmx.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: <infamdm_install_directory>/bin/build.properties 2. Modify your WebLogic configuration settings under the #Server settings section. 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 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. Installing the Hub Server 65

86 Installing the Hub Server (WebLogic/Unix) 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 -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. 66 Informatica MDM Hub Installation Guide

87 Installing the Hub Server (WebSphere/Unix) 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. Installation Overview Hub Server installation involves the following steps: Step Task Instructions 1 Prepare the target environment, including Preparing for Installation on page 67 setting up the application server. 2 Install the Hub Server by running the installer. 3 Specify or change Hub Server configuration settings. Preparing for Installation Running the Hub Server Installer on page 69 Configuring the Hub Server on page 73 Complete the tasks in this section before you install the Hub Server. Installing the Hub Server 67

88 Installing the Hub Server (WebSphere/Unix) 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 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: 68 Informatica MDM Hub Installation Guide

89 Installing the Hub Server (WebSphere/Unix) Copy the new Oracle JDBC driver files to your <WebSphere_install_dir>/lib directory. 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 Installing the Hub Server 69

90 Installing the Hub Server (WebSphere/Unix) 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 the I accept the terms of the License Agreement button 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. 70 Informatica MDM Hub Installation Guide

91 Installing the Hub Server (WebSphere/Unix) 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. Choose WebSphere. 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 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 Database Selection screen is displayed. 12. Select Oracle. Click Next. The Oracle Database Connection Type Selection screen is displayed. Installing the Hub Server 71

92 Installing the Hub Server (WebSphere/Unix) 13. Select the connection type you want (Service Name or SID). Click Next. The Oracle Database Information screen is displayed. 14. 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!! 15. 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. 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 PostInstallSetup on page 45. Click Next. The Pre-Installation Summary screen is displayed. 17. 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. 18. 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. 19. 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 72 Informatica MDM Hub Installation Guide

93 Installing the Hub Server (WebSphere/Unix) 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 <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 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. Description Contains log messages for the Hub Server installation. Contains the prerequisite messages generated during installation. Contains debug messages. Contains the postinstallsetup messages for the script. Hub Server log. When the server started, it created this file. Located in the tree under the WebSphere 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 Installing the Hub Server 73

94 Installing the Hub Server (WebSphere/Unix) 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. 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/server cmx.server.masterdatabase.type=oracle cmx.appserver.type=websphere cmx.appserver.rmi.port=2809 cmx.appserver.naming.protocol=iiop jnlp.initial-heap-size=128m jnlp.max-heap-size=192m cmx.server.datalayer.cleanse.execution=server cmx.server.datalayer.cleanse.working_ files.location=/infamdm/hub/server/logs cmx.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: 74 Informatica MDM Hub Installation Guide

95 Installing the Hub Server (WebSphere/Unix) <infamdm_install_directory>/bin/build.properties 2. Modify your WebSphere 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 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 -Ddatabase.password=<yourDBPassword> 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\!\! Installing the Hub Server 75

96 Installing the Hub Server (WebSphere/Unix) Manually Redeploying the Hub Server Application If you need to manually redeploy the Hub Server application, see the instructions in Manually Redeploying the Hub Server Application (WebSphere/Unix) on page Informatica MDM Hub Installation Guide

97 Installing the Hub Server (JBoss/Windows) 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 or higher.. Installation Overview Hub Server installation involves the following steps: Step Task Instructions 1 Prepare the target environment, including Preparing for Installation on page 78 setting up the application server. 2 Install the Hub Server by running the installer. 3 Specify or change Hub Server configuration settings. Running the Hub Server Installer on page 81 Configuring the Hub Server on page 85 Installing the Hub Server 77

98 Installing the Hub Server (JBoss/Windows) Preparing for Installation Complete the tasks in this section before you install the Hub Server. 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 + 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 78 Informatica MDM Hub Installation Guide

99 Installing the Hub Server (JBoss/Windows) 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. 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 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. 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 Installing the Hub Server 79

100 Installing the Hub Server (JBoss/Windows) 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: <!-- Uncomment to require authenticated users > <interceptor code="org.jboss.jmx.connector.invoker.authenticationinterceptor" securitydomain="java:/jaas/jmx-console"/ --> 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 ga\bin 2. Run the following command: run.bat -b Informatica MDM Hub Installation Guide

101 Installing the Hub Server (JBoss/Windows) 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. File names and directories in this section may vary slightly depending on what type of installation you are performing. 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. 3. Click Next to continue. The License Agreement screen is displayed. 4. Select the I accept the terms of the License Agreement button 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 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. Installing the Hub Server 81

102 Installing the Hub Server (JBoss/Windows) 5. Do one of the following: Click Next to install Informatica MDM Hub in C:\infamdm\hub\server. Enter the path to the installation folder. Click Next. 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. The Enter Location of License File screen is displayed. 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. The Application Server screen is displayed. 8. Choose JBoss and then click Next. The JBoss Application Server Home screen is displayed. 9. 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 Port 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. 82 Informatica MDM Hub Installation Guide

103 Installing the Hub Server (JBoss/Windows) 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. The Database Selection screen is displayed. 11. Select Oracle. Click Next. The Oracle Database Connection Type Selection screen is displayed. 12. Select the connection type you want (Service Name or SID). Click Next. The Oracle Database Information screen is displayed. 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). Note: The default password for the CMX user is!!cmx!! 14. Click Next. 15. 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 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. The Pre-Installation Summary screen is displayed. 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. When the installation completes, the Install Complete screen is displayed. 18. Click Done to exit the Hub Server installer. Installing the Hub Server 83

104 Installing the Hub Server (JBoss/Windows) 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 <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 Description Contains log messages for the Hub Server installation. Contains the prerequisite messages generated during installation. Contains debug messages. Contains the postinstallsetup messages for the script. Hub Server log. When the server started, it created this file. Located in the tree under the JBoss install directory. 84 Informatica MDM Hub Installation Guide

105 Installing the Hub Server (JBoss/Windows) Configuring the Hub Server This section describes how to configure the Hub Server after it is installed. 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. Configuring the Logging Settings 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). 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 should look similar to the following example: cmx.home=c:\infamdm\hub\server cmx.server.masterdatabase.type=oracle Installing the Hub Server 85

106 Installing the Hub Server (JBoss/Windows) cmx.application.server.type=jboss cmx.appserver.web.port=8080 cmx.appserver.rmi.port=1099 cmx.appserver.naming.protocol=jnp cmx.appserver.soap.connector.port= jnlp.initial-heap-size=128m jnlp.max-heap-size=192m cmx.server.datalayer.cleanse.execution=server cmx.server.datalayer.cleanse.working_ files.location=c:\infamdm\hub\server\logs cmx.server.datalayer.cleanse.working_files=local Note: If you 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 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 Informatica MDM Hub Installation Guide

107 Installing the Hub Server (JBoss/Windows) 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 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 Manually Redeploying the Hub Server Application 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 87

108 Installing the Hub Server (WebLogic/Windows) 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. Installation Overview Hub Server installation involves the following steps: Step Task Instructions 1 Prepare the target environment, including Preparing for Installation on page 88 setting up the application server. 2 Install the Hub Server by running the installer. 3 Specify or change Hub Server configuration settings. Preparing for Installation Running the Hub Server Installer on page 90 Configuring the Hub Server on page 95 Complete the tasks in this section before you install the Hub Server. 88 Informatica MDM Hub Installation Guide

109 Installing the Hub Server (WebLogic/Windows) 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 + 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. Installing the Hub Server 89

110 Installing the Hub Server (WebLogic/Windows) Verify Available Storage The Hub Server requires 500MB of available disk space. Install and Configure WebLogic 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. 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. 90 Informatica MDM Hub Installation Guide

111 Installing the Hub Server (WebLogic/Windows) Installation Considerations Important: You must use the same username to install both Hub Server and Cleanse Match Server. File names and directories in this section may vary slightly depending on what type of installation you are performing. Installation Steps To install Hub Server: 1. Make sure that your application server is 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. 3. Click Next to continue. The License Agreement screen is displayed. 4. Select the I accept the terms of the License Agreement button 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 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. 5. Do one of the following: Click Next to install Informatica MDM Hub in C:\infamdm\hub\server. Enter the path to the installation folder. Click Next. 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. The Enter Location of License File screen is displayed. Installing the Hub Server 91

112 Installing the Hub Server (WebLogic/Windows) 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. The Application Server screen is displayed. 8. Choose WebLogic and then click Next. The WebLogic Application Server Home screen is displayed. 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: Field Host Server User Name Password Port Number Description Name of the host computer on which WebLogic is installed. Name of the server on which WebLogic is deployed. Name of the user for the WebLogic installation. Password that corresponds to the WebLogic user. 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. 10. Click Next. The Database Selection screen is displayed. 11. Select Oracle. Click Next. 92 Informatica MDM Hub Installation Guide

113 Installing the Hub Server (WebLogic/Windows) The Oracle Database Connection Type Selection screen is displayed. 12. Select the connection type you want (Service Name or SID). Click Next. The Oracle Database Information screen is displayed. 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). Note: The default password for the CMX user is!!cmx!! 14. Click Next. 15. 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 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 97. Click Next. The Pre-Installation Summary screen is displayed. 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. When the installation completes, the Install Complete screen is displayed. 18. Click Done to exit the Hub Server installer. Installing the Hub Server 93

114 Installing the Hub Server (WebLogic/Windows) 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 <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 WebLogic log files. For example: <weblogic_ domain>\servers\adminserver\logs\adminserver.log <weblogic_domain>\servers\adminserver\logs\<domain_ name>.log Description Contains log messages for the Hub Server installation. Contains the prerequisite messages generated during installation. Contains debug messages. Contains the postinstallsetup messages for the script. Hub Server log. When the server started, it created this file. Located in the tree under the WebLogic install directory. 94 Informatica MDM Hub Installation Guide

115 Installing the Hub Server (WebLogic/Windows) Configuring the Hub Server This section describes how to configure the Hub Server after it is installed. 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. 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. After you update this file, you must restart the Hub Server application. 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 should look similar to the following example: cmx.home=c:\infamdm\hub\server cmx.server.masterdatabase.type=oracle cmx.application.server.type=weblogic cmx.appserver.rmi.port=7001 Installing the Hub Server 95

116 Installing the Hub Server (WebLogic/Windows) cmx.appserver.naming.protocol=t3 cmx.appserver.soap.connector.port= jnlp.initial-heap-size=128m jnlp.max-heap-size=192m cmx.server.datalayer.cleanse.execution=server cmx.server.datalayer.cleanse.working_ files.location=c:\infamdm\hub\server\logs cmx.server.datalayer.cleanse.working_files=local 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: <infamdm_install_directory>\server\bin\build.properties 2. Modify your WebLogic configuration settings under the #Server settings section of build.properties. 3. Save and close build.properties file. 4. Run the postinstallsetup.bat script according to the instructions in Running the Post-Install Process Manually on page 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 Informatica MDM Hub Installation Guide

117 Installing the Hub Server (WebLogic/Windows) 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 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 -Dweblogic.password=<weblogicPassword> -Ddatabase.password=<yourDBPassword> where <weblogicpassword> is the password for your WebLogic application server. and <yourdbpassword> is your database password. 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/Windows) on page 315. Installing the Hub Server 97

118 Installing the Hub Server (WebSphere/Windows) 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. Installation Overview Hub Server installation involves the following steps: Step Task Instructions 1 Prepare the target environment, including Preparing for Installation on page 98 setting up the application server. 2 Install the Hub Server by running the installer. 3 Specify or change Hub Server configuration settings. Preparing for Installation Running the Hub Server Installer on page 100 Configuring the Hub Server on page 104 Complete the tasks in this section before you install the Hub Server. 98 Informatica MDM Hub Installation Guide

119 Installing the Hub Server (WebSphere/Windows) 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 the 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 + 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. Installing the Hub Server 99

120 Installing the Hub Server (WebSphere/Windows) Verify Available Storage The Hub Server requires 500MB of available disk space. Install and Configure WebSphere 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. 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. File names and directories in this section may vary slightly depending on what type of installation you are performing. 100 Informatica MDM Hub Installation Guide

121 Installing the Hub Server (WebSphere/Windows) Installation Steps To install Hub Server: 1. Make sure that your application server is 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. 3. Click Next to continue. The License Agreement screen is displayed. 4. Select the I accept the terms of the License Agreement button 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 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. 5. Do one of the following: Click Next to install Informatica MDM Hub in C:\infamdm\hub\server. Enter the path to the installation folder. Click Next. 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. The Enter Location of License File screen is displayed. 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. Installing the Hub Server 101

122 Installing the Hub Server (WebSphere/Windows) The Application Server screen is displayed. 8. Choose WebSphere. Click Next. The WebSphere Application Server Home screen is displayed. 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. The Oracle Database Connection Type Selection screen is displayed. 11. Select the connection type you want (Service Name or SID). Click Next. The Oracle Database Information screen is displayed. 12. 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). Note: The default password for the CMX user is!!cmx!! 13. Click Next. 102 Informatica MDM Hub Installation Guide

123 Installing the Hub Server (WebSphere/Windows) 14. 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 PostInstallSetup script (Deploy) screen is displayed. 15. 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 106. Click Next. The Pre-Installation Summary screen is displayed. 16. 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. When the installation completes, the Install Complete screen is displayed. 17. 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 <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 Description Contains log messages for the Hub Server installation. Contains the prerequisite messages generated during installation. Contains debug messages. Contains the postinstallsetup messages for the script. Installing the Hub Server 103

124 Installing the Hub Server (WebSphere/Windows) Location / Log File <infamdm_install_ directory>\hub\server\logs\cmxserver.log WebSphere log files. For example: <WebSphere_install_ dir>\profiles\appsrv01\logs\<servername> folder Description Hub Server log. When the server started, it created this file. Located in the tree under the WebSphere install directory. Configuring the Hub Server This section describes how to configure the Hub Server after it is installed. 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. 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. After you update this file, you must restart the Hub Server application. 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 104 Informatica MDM Hub Installation Guide

125 Installing the Hub Server (WebSphere/Windows) 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=c:\infamdm\hub\server cmx.server.masterdatabase.type=oracle cmx.application.server.type=websphere cmx.appserver.rmi.port=2809 cmx.appserver.naming.protocol=iiop cmx.appserver.soap.connector.port=8880 jnlp.initial-heap-size=128m jnlp.max-heap-size=192m cmx.server.datalayer.cleanse.execution=server cmx.server.datalayer.cleanse.working_ files.location=c:\infamdm\hub\server\logs cmx.server.datalayer.cleanse.working_files=local 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: <infamdm_install_directory>\server\bin\build.properties 2. Modify your WebSphere 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 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. Installing the Hub Server 105

126 Installing the Hub Server (WebSphere/Windows) 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 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 -Ddatabase.password=!!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 (WebSphere/Windows) on page Informatica MDM Hub Installation Guide

127 Changing Passwords After Installation 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. Installing the Hub Server 107

128 Changing Passwords After Installation 108 Informatica MDM Hub Installation Guide

129 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

130 About the Cleanse Match Server 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 PostInstallSetup 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. 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. 110 Informatica MDM Hub Installation Guide

131 About the Cleanse Match Server 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. 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 Cleanse Match Server 111

132 Installing the Cleanse Match Server (JBoss/Unix) 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. Installation Overview Cleanse Match Server installation involves the following steps: Step Task Instructions 1 Prepare the target environment, including Preparing for Installation on page 112 setting up the application server. 2 Install the Cleanse Match Server by running the installer. 3 Specify or change Cleanse Match Server configuration settings. Preparing for Installation Running the Cleanse Match Server Installer on page 117 Configuring the Cleanse Match Server on page 121 Complete the tasks in this section before you install the Cleanse Match Server. 112 Informatica MDM Hub Installation Guide

133 Installing the Cleanse Match Server (JBoss/Unix) Fulfill Hardware and Software Requirements 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. Install and Configure JBoss On the machine where you will run the Cleanse Match Server, install and configure your JBoss environment according to your 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 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. 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 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. Installing the Cleanse Match Server 113

134 Installing the Cleanse Match Server (JBoss/Unix) Obtain an Informatica License File 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 114 Informatica MDM Hub Installation Guide

135 Installing the Cleanse Match Server (JBoss/Unix) 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 jndi-name Description 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. Installing the Cleanse Match Server 115

136 Installing the Cleanse Match Server (JBoss/Unix) Parameter connection-url username password Description 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: 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. The default password used when creating a new connection. 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 Change this to any unused port that does not conflict with other applications. 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 ga/bin 2. Run the following command: run.sh -b Informatica MDM Hub Installation Guide

137 Installing the Cleanse Match Server (JBoss/Unix) 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. File names and directories in this section may vary slightly depending on what type of installation you are performing. 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. Installing the Cleanse Match Server 117

138 Installing the Cleanse Match Server (JBoss/Unix) 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. Note: To bypass the prerequisite validation in the installation, see Bypassing Prerequisite Installation on page Click Next. The License Agreement screen is displayed. 6. Accept the terms of the license agreement and click Next. The Choose Install Folder screen is displayed. 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. The Enter Location of License File screen is displayed. 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. The Application Server screen is displayed. 9. Choose the JBoss application server and click Next. 118 Informatica MDM Hub Installation Guide

139 Installing the Cleanse Match Server (JBoss/Unix) The JBoss Application Server Home screen is displayed. 10. Configure 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 Application Server Port screen is displayed. c. 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 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, Installing the Cleanse Match Server 119

140 Installing the Cleanse Match Server (JBoss/Unix) 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. Installation Log Files 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 <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 <infamdm_install_ directory>/hub/cleanse/logs/installprereq.log JBoss log files (such as <JBoss_install_ dir>/server/<configuration_name>/log/server.log) Description Shows the Cleanse Match Server install errors and status. Shows the postinstallsetup script results. Cleanse server logs. Shows what was chosen during the installation. Contains the prerequisite messages generated during installation. Located in the tree under the install directory for your application server. 120 Informatica MDM Hub Installation Guide

141 Installing the Cleanse Match Server (JBoss/Unix) 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 Installing the Cleanse Match Server 121

142 Installing the Cleanse Match Server (JBoss/Unix) 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 122 Informatica MDM Hub Installation Guide

143 Installing the Cleanse Match Server (JBoss/Unix) cmx.server.datalayer.cleanse.working_ files.location=/u1/infamdm/hub/cleanse/tmp cmx.server.datalayer.cleanse.working_files=keep cmx.server.datalayer.cleanse.execution=local cmx.home=/u1/infamdm/hub/cleanse cmx.appserver.type=jboss 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>)) ) Installing the Cleanse Match Server 123

144 Installing the Cleanse Match Server (JBoss/Unix) 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. 124 Informatica MDM Hub Installation Guide

145 Installing the Cleanse Match Server (JBoss/Unix) 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 Configure your system to run multiple instances of your application server. For more information, see Configuring Multiple Instances of your Application Server on page 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. Installing the Cleanse Match Server 125

146 Installing the Cleanse Match Server (JBoss/Unix) 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. 126 Informatica MDM Hub Installation Guide

147 Installing the Cleanse Match Server (JBoss/Unix) 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. Installing the Cleanse Match Server 127

148 Installing the Cleanse Match Server (JBoss/Unix) 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. 128 Informatica MDM Hub Installation Guide

149 Installing the Cleanse Match Server (WebLogic/Unix) 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. Installation Overview Cleanse Match Server installation involves the following steps: Step Task Instructions 1 Prepare the target environment, including Preparing for Installation on page 129 setting up the application server. 2 Install the Cleanse Match Server by running the installer. 3 Specify or change Cleanse Match Server configuration settings. Preparing for Installation Running the Cleanse Match Server Installer on page 134 Configuring the Cleanse Match Server on page 138 Complete the tasks in this section before you install the Cleanse Match Server. Installing the Cleanse Match Server 129

150 Installing the Cleanse Match Server (WebLogic/Unix) Fulfill Hardware and Software Requirements 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. Install and Configure WebLogic On the machine where you will run the Cleanse Match Server, install and configure your WebLogic environment according to your WebLogic documentation. 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. Obtain an Informatica License File 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. 130 Informatica MDM Hub Installation Guide

151 Installing the Cleanse Match Server (WebLogic/Unix) 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 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. Creating Data Sources for Each ORS 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. Installing the Cleanse Match Server 131

152 Installing the Cleanse Match Server (WebLogic/Unix) 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. 132 Informatica MDM Hub Installation Guide

153 Installing the Cleanse Match Server (WebLogic/Unix) 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. Installing the Cleanse Match Server 133

154 Installing the Cleanse Match Server (WebLogic/Unix) Click Activate Changes. Note: Use all lower case when creating the JNDI names. 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. File names and directories in this section may vary slightly depending on what type of installation you are performing. 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. 134 Informatica MDM Hub Installation Guide

155 Installing the Cleanse Match Server (WebLogic/Unix) 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. Note: To bypass the prerequisite validation in the installation, see Bypassing Prerequisite Installation on page Click Next. The License Agreement screen is displayed. 6. Accept the terms of the license agreement and click Next. The Choose Install Folder screen is displayed. 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. The Enter Location of License File screen is displayed. Installing the Cleanse Match Server 135

156 Installing the Cleanse Match Server (WebLogic/Unix) 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. The Application Server screen is displayed. 9. Choose the WebLogic application server and click Next. The WebLogic Application Server Home screen is displayed. 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: Field Host Server User Name Password Port Number Description Name of the host computer on which WebLogic is installed. Name of the server on which WebLogic is deployed. Name of the user for the WebLogic installation. Password that corresponds to the WebLogic user. Port number on which your WebLogic Server is listening. 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 Click Next. 12. Configure cleanse engine settings for the cleanse engine you use. 136 Informatica MDM Hub Installation Guide

157 Installing the Cleanse Match Server (WebLogic/Unix) 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. 13. Choose to run the script during the installation, or later (see Running PostInstallSetup on page 146). 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. 14. Click Done to exit the Cleanse Match Server installer. Installation Log Files 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 Installing the Cleanse Match Server 137

158 Installing the Cleanse Match Server (WebLogic/Unix) 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 <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 <infamdm_install_ directory>/hub/cleanse/logs/installprereq.log WebLogic log files under <weblogic_domain>/servers/<weblogic_ server>/logs.: access.log, <weblogic_server>.log and <weblogic_ domain>.log. Description Shows the Cleanse Match Server install errors and status. Shows the postinstallsetup script results. Cleanse server logs. Shows what was chosen during the installation. Contains the prerequisite messages generated during installation. 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. 138 Informatica MDM Hub Installation Guide

159 Installing the Cleanse Match Server (WebLogic/Unix) 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. Installing the Cleanse Match Server 139

160 Installing the Cleanse Match Server (WebLogic/Unix) 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. 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/tmp cmx.server.datalayer.cleanse.working_files=keep cmx.server.datalayer.cleanse.execution=local cmx.home=/u1/infamdm/hub/cleanse cmx.appserver.type=weblogic 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. 140 Informatica MDM Hub Installation Guide

161 Installing the Cleanse Match Server (WebLogic/Unix) 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 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. Installing the Cleanse Match Server 141

162 Installing the Cleanse Match Server (WebLogic/Unix) 2. Find the following entry in the cmxcleanse.properties file: # Cleanse Properties # control the number thread to use while cleaning cmx_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. 142 Informatica MDM Hub Installation Guide

163 Installing the Cleanse Match Server (WebLogic/Unix) 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 143. 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 145. 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 134 and Configuring the Cleanse Match Server on page 138. Installing the Cleanse Match Server 143

164 Installing the Cleanse Match Server (WebLogic/Unix) 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 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 144. 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. On WebLogic, create a separate domain for each new cleanse instance. For more information, see your WebLogic 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 144. 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 144 Informatica MDM Hub Installation Guide

165 Installing the Cleanse Match Server (WebLogic/Unix) 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, use the admin console for deployment. Accept all defaults. 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. Installing the Cleanse Match Server 145

166 Installing the Cleanse Match Server (WebLogic/Unix) 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 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 -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\!\! 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. 146 Informatica MDM Hub Installation Guide

167 Installing the Cleanse Match Server (WebLogic/Unix) 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 147

168 Installing the Cleanse Match Server (WebSphere/Unix) 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. Installation Overview Cleanse Match Server installation involves the following steps: Step Task Instructions 1 Prepare the target environment, including Preparing for Installation on page 148 setting up the application server. 2 Install the Cleanse Match Server by running the installer. 3 Specify or change Cleanse Match Server configuration settings. Preparing for Installation Running the Cleanse Match Server Installer on page 155 Configuring the Cleanse Match Server on page 159 Complete the tasks in this section before you install the Cleanse Match Server. 148 Informatica MDM Hub Installation Guide

169 Installing the Cleanse Match Server (WebSphere/Unix) Fulfill Hardware and Software Requirements 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. Install and Configure WebSphere On the machine where you will run the Cleanse Match Server, install and configure your WebSphere environment according to your WebSphere documentation. 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. Obtain an Informatica License File 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. Installing the Cleanse Match Server 149

170 Installing the Cleanse Match Server (WebSphere/Unix) 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 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 To create your WebSphere 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. 150 Informatica MDM Hub Installation Guide

171 Installing the Cleanse Match Server (WebSphere/Unix) 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). Installing the Cleanse Match Server 151

172 Installing the Cleanse Match Server (WebSphere/Unix) 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. Changing the Password for the CMX_SYSTEM User 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 To create your WebSphere ORS 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. (for example, /u1/was6103/appserver/lib). 152 Informatica MDM Hub Installation Guide

173 Installing the Cleanse Match Server (WebSphere/Unix) 4. Create the security account to be used by the Informatica MDM ORS Data Source: a. Expand Security in the console navigation tree. Click Secure administration, applications, and infrastructure link in WebSphere b. Expand Java Authentication and Authorization Service under Authentication in right side of the console window. Click J2C Authentication Data. 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. 5. Create the JDBC Provider: a. Expand Resources in the console navigation tree and then expand the JDBC menu. Click 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. Installing the Cleanse Match Server 153

174 Installing the Cleanse Match Server (WebSphere/Unix) 6. Create the Informatica MDM ORS 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. 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_number>:<oracle_sid> e. Click Next and Finish. Note: The JNDI name must be in lower case. 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. 154 Informatica MDM Hub Installation Guide

175 Installing the Cleanse Match Server (WebSphere/Unix) 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. File names and directories in this section may vary slightly depending on what type of installation you are performing. 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. Installing the Cleanse Match Server 155

176 Installing the Cleanse Match Server (WebSphere/Unix) 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. Note: To bypass the prerequisite validation in the installation, see Bypassing Prerequisite Installation on page Click Next. The License Agreement screen is displayed. 6. Accept the terms of the license agreement and click Next. The Choose Install Folder screen is displayed. 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. The Enter Location of License File screen is displayed. 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. The Application Server screen is displayed. 9. Choose the WebSphere application server and click Next. 156 Informatica MDM Hub Installation Guide

177 Installing the Cleanse Match Server (WebSphere/Unix) 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. 12. 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. 13. Choose to run the script during the installation, or later (see Running PostInstallSetup on page 167). Click Next. Installing the Cleanse Match Server 157

178 Installing the Cleanse Match Server (WebSphere/Unix) 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. 14. Click Done to exit the Cleanse Match Server installer. Installation Log Files 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 <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 <infamdm_install_ directory>/hub/cleanse/logs/installprereq.log 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. Description Shows the Cleanse Match Server install errors and status. Shows the postinstallsetup script results. Cleanse server logs. Shows what was chosen during the installation. Contains the prerequisite messages generated during installation. Located in the tree under the install directory for your application server. 158 Informatica MDM Hub Installation Guide

179 Installing the Cleanse Match Server (WebSphere/Unix) 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 Installing the Cleanse Match Server 159

180 Installing the Cleanse Match Server (WebSphere/Unix) 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. 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_ 160 Informatica MDM Hub Installation Guide

181 Installing the Cleanse Match Server (WebSphere/Unix) files.location=/u1/infamdm/hub/cleanse/tmp cmx.server.datalayer.cleanse.working_files=keep cmx.server.datalayer.cleanse.execution=local cmx.home=/u1/infamdm/hub/cleanse cmx.appserver.type=websphere 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>)) ) Installing the Cleanse Match Server 161

182 Installing the Cleanse Match Server (WebSphere/Unix) 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 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 cleaning cmx_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 162 Informatica MDM Hub Installation Guide

183 Installing the Cleanse Match Server (WebSphere/Unix) 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. 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 164. 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 166. Installing the Cleanse Match Server 163

184 Installing the Cleanse Match Server (WebSphere/Unix) 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 155 and Configuring the Cleanse Match Server on page Configure your system to run multiple instances of your application server. For more information, see Configuring Multiple Instances of your Application Server on page 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 165. 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: On WebSphere, you must either have the Network Deployment edition of WebSphere, which allows you to create and manage multiple instances, or use the 164 Informatica MDM Hub Installation Guide

185 Installing the Cleanse Match Server (WebSphere/Unix) 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. 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 165. 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, use the admin console for deployment. Accept all defaults. Installing the Cleanse Match Server 165

186 Installing the Cleanse Match Server (WebSphere/Unix) 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. 166 Informatica MDM Hub Installation Guide

187 Installing the Cleanse Match Server (WebSphere/Unix) Running PostInstallSetup 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. 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 -Ddatabase.password=<yourDBPassword> 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\!\! 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 167

188 Installing the Cleanse Match Server (JBoss/Windows) 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. Installation Overview Cleanse Match Server installation involves the following steps: Step Task Instructions 1 Prepare the target environment, including Preparing for Installation on page 168 setting up the application server. 2 Install the Cleanse Match Server by running the installer. 3 Specify or change Cleanse Match Server configuration settings. Preparing for Installation Running the Cleanse Match Server Installer on page 172 Configuring the Cleanse Match Server on page 176 Complete the tasks in this section before you install the Cleanse Match Server. 168 Informatica MDM Hub Installation Guide

189 Installing the Cleanse Match Server (JBoss/Windows) Fulfill Hardware and Software Requirements 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. Install and Configure JBoss On the machine where you will run the Cleanse Match Server, install and configure your JBoss environment according to your JBoss documentation. Configure JBoss to Use an Oracle Data Source 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. 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 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. Installing the Cleanse Match Server 169

190 Installing the Cleanse Match Server (JBoss/Windows) Obtain an Informatica License File 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. 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 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 170 Informatica MDM Hub Installation Guide

191 Installing the Cleanse Match Server (JBoss/Windows) Creating Data Sources for Each ORS 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: Parameter jndi-name Description 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. Installing the Cleanse Match Server 171

192 Installing the Cleanse Match Server (JBoss/Windows) Parameter connection-u rl username password Description 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: 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. The default password used when creating a new connection. 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 ga\bin 2. Run the following command: run.bat -b 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: 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. File names and directories in this section may vary slightly depending on what type of installation you are performing. 172 Informatica MDM Hub Installation Guide

193 Installing the Cleanse Match Server (JBoss/Windows) 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 To install Cleanse Match Server: 1. Make sure that your application server is started and running correctly. 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. The License Agreement screen is displayed. 4. Click the I accept the terms of the License Agreement button and then click Next. The Choose Install Folder screen is displayed. 5. Do one of the following: 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. Important: Do not use a path that has spaces in the directory or folder names. 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. The Enter Location of License File screen is displayed. 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 Installing the Cleanse Match Server 173

194 Installing the Cleanse Match Server (JBoss/Windows) Informatica Global Customer Support (see Informatica Global Customer Support on page xvii) to obtain a license file. 8. Click Next to continue. The Application Server screen is displayed. 9. Choose the JBoss application server and click Next. The JBoss Application Server Home screen is displayed 10. Configure 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 Application Server Port screen is displayed. c. Specify your RMI port. 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. 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. 174 Informatica MDM Hub Installation Guide

195 Installing the Cleanse Match Server (JBoss/Windows) 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. 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. The Please Wait screen is displayed while Informatica configures your system. When the installation completes, the Install Complete screen is displayed. 14. Choose Yes to restart your system, or choose No to restart it later and click Done to exit the Cleanse Match Server installer. Installation Log Files 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 <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 Description Shows the Cleanse Match Server install errors and status. Shows the postinstallsetup script results. Cleanse server logs. Shows what was chosen during the installation. Installing the Cleanse Match Server 175

196 Installing the Cleanse Match Server (JBoss/Windows) File <infamdm_install_ directory>\hub\cleanse\logs\installprereq.log JBoss log files (such as <JBoss_install_ dir>\server\<configuration_name>\log\server.log). Description Contains the prerequisite messages generated during installation. 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 For more information regarding cleanse engine configuration, see the Informatica MDM Hub Cleanse Adapter Guide. 176 Informatica MDM Hub Installation Guide

197 Installing the Cleanse Match Server (JBoss/Windows) 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.bat 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 cmxcleanse.properties file which is stored, by default, 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 the file after cleanse/strip is 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 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. Installing the Cleanse Match Server 177

198 Installing the Cleanse Match Server (JBoss/Windows) 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: C:\infamdm\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.datalayer.cleanse.working_ files.location=c:\infamdm\hub\cleanse\tmp cmx.server.datalayer.cleanse.working_files=keep cmx.server.datalayer.cleanse.execution=local cmx.home=c:\infamdm\hub\cleanse cmx.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. 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>)) ) 178 Informatica MDM Hub Installation Guide

199 Installing the Cleanse Match Server (JBoss/Windows) 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>)) ) 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. Performing Post-installation Tasks This section describes tasks to complete after you have installed the software. Running PostInstallSetup If you chose to have the Cleanse Match Server installer skip the post-install process, you must run this manually. By default, this script is located in the following directory: <infamdm_install_directory>\hub\cleanse To run the post-install process manually, run the following command from a command prompt: postinstallsetup.bat Installing the Cleanse Match Server 179

200 Installing the Cleanse Match Server (JBoss/Windows) 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 172 and Configuring the Cleanse Match Server on page 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 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 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. 180 Informatica MDM Hub Installation Guide

201 Installing the Cleanse Match Server (JBoss/Windows) 3. Test the second instance you just created. Now you can deploy Cleanse Match Server, as described in the next section. Deploying Cleanse Match Server on the 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, but you can deploy them manually on the application server. Deploying the EAR File Manually To deploy the EAR file manually, copy the file to the following directory: <JBoss_install_dir>\server\<configuration_name>\deploy Installing the Cleanse Match Server 181

202 Installing the Cleanse Match Server (JBoss/Windows) 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 servers 1. 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. 3. Using Hub Console, connect to the data store. 4. Choose the Cleanse Match Server workbench. 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. 182 Informatica MDM Hub Installation Guide

203 Installing the Cleanse Match Server (JBoss/Windows) Below are the parameters that need to be set to utilize the cleanse servers based on the server configuration. Parameter Thread Count CPU Rating Description 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. 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. 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. Installing the Cleanse Match Server 183

204 Installing the Cleanse Match Server (WebLogic/Windows) 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. Installation Overview Cleanse Match Server installation involves the following steps: Step Task Instructions 1 Prepare the target environment, including Preparing for Installation on page 184 setting up the application server. 2 Install the Cleanse Match Server by running the installer. 3 Specify or change Cleanse Match Server configuration settings. Preparing for Installation Running the Cleanse Match Server Installer on page 192 Configuring the Cleanse Match Server on page 196 Complete the tasks in this section before you install the Cleanse Match Server. 184 Informatica MDM Hub Installation Guide

205 Installing the Cleanse Match Server (WebLogic/Windows) Fulfill Hardware and Software Requirements 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. Install and Configure WebLogic On the machine where you will run the Cleanse Match Server, install and configure your WebLogic environment according to your WebLogic documentation. 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. Obtain an Informatica License File 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. Installing the Cleanse Match Server 185

206 Installing the Cleanse Match Server (WebLogic/Windows) 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 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. Creating Data Sources for Each ORS 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. 186 Informatica MDM Hub Installation Guide

207 Installing the Cleanse Match Server (WebLogic/Windows) 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: Property TestConnectionsOnRelease TestTableName TestConnectionsOnReserve Value false C_REPOS_DATABASE false 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. Installing the Cleanse Match Server 187

208 Installing the Cleanse Match Server (WebLogic/Windows) 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 Database Name = <YourDatabaseName> 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: Property TestConnectionsOnRelease TestTableName TestConnectionsOnReserve Value false C_REPOS_DB_RELEASE false 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. 5. Create a Data Source called ORS Data Source. 188 Informatica MDM Hub Installation Guide

209 Installing the Cleanse Match Server (WebLogic/Windows) 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. Note: Use all lower case when creating the JNDI names. 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 Database Name = <YourDatabaseName> Installing the Cleanse Match Server 189

210 Installing the Cleanse Match Server (WebLogic/Windows) 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 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. 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-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 Database Name = <YourDatabaseName> Set Host Name = <YourDatabaseHostname> Set Port = <YourPortNumber> 190 Informatica MDM Hub Installation Guide

211 Installing the Cleanse Match Server (WebLogic/Windows) 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. Click Activate Changes. Note: Use all lower case when creating the JNDI names. Installing the Cleanse Match Server 191

212 Installing the Cleanse Match Server (WebLogic/Windows) 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: 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. File names and directories in this section may vary slightly depending on what type of installation you are performing. 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 To install the Cleanse Match Server: 1. Make sure that your application server is started and running correctly. 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. The License Agreement screen is displayed. 4. Click the I accept the terms of the License Agreement button and then click Next. 192 Informatica MDM Hub Installation Guide

213 Installing the Cleanse Match Server (WebLogic/Windows) The Choose Install Folder screen is displayed. 5. Do one of the following: 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. Important: Do not use a path that has spaces in the directory or folder names. 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. The Enter Location of License File screen is displayed. 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. 8. Click Next to continue. The Application Server screen is displayed. 9. Choose the WebLogic application server and click Next. The WebLogic Application Server Home screen is displayed. 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 Host Server Description Name of the host computer on which WebLogic is installed. Name of the server on which WebLogic is deployed. Installing the Cleanse Match Server 193

214 Installing the Cleanse Match Server (WebLogic/Windows) Field User Name Password Port Number Description Name of the user for the WebLogic installation. Password that corresponds to the WebLogic user. Port number on which your WebLogic Server is listening. 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. 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. 194 Informatica MDM Hub Installation Guide

215 Installing the Cleanse Match Server (WebLogic/Windows) 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 199 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. The Please Wait screen is displayed while Informatica configures your system. When the installation completes, the Install Complete screen is displayed. 14. Choose Yes to restart your system, or choose No to restart it later and click Done to exit the Cleanse Match Server installer. Installation Log Files 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 <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 <infamdm_install_ directory>\hub\cleanse\logs\installprereq.log WebLogic log files under <weblogic_domain>\servers\<weblogic_ server>\logs.: access.log, <weblogic_server>.log and <weblogic_ domain>.log Description Shows the Cleanse Match Server install errors and status. Shows the postinstallsetup script results. Cleanse server logs. Shows what was chosen during the installation. Contains the prerequisite messages generated during installation. Located in the tree under the install directory for your application server. Installing the Cleanse Match Server 195

216 Installing the Cleanse Match Server (WebLogic/Windows) 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 For more information regarding cleanse engine configuration, 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.bat file 196 Informatica MDM Hub Installation Guide

217 Installing the Cleanse Match Server (WebLogic/Windows) 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 cmxcleanse.properties file which is stored, by default, 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 the file after cleanse/strip is 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 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. 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.datalayer.cleanse.working_ Installing the Cleanse Match Server 197

218 Installing the Cleanse Match Server (WebLogic/Windows) files.location=c:\infamdm\hub\cleanse\tmp cmx.server.datalayer.cleanse.working_files=keep cmx.server.datalayer.cleanse.execution=local cmx.home=c:\infamdm\hub\cleanse cmx.appserver.type=weblogic 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. 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>)) ) 198 Informatica MDM Hub Installation Guide

219 Installing the Cleanse Match Server (WebLogic/Windows) 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. Performing Post-installation Tasks This section describes tasks to complete after you have installed the software. Running PostInstallSetup If you chose to have the Cleanse Match Server installer skip the post-install process, you must run this manually. By default, this script is located in the following directory: <infamdm_install_directory>\hub\cleanse To run the post-install process manually, run the following command from a command prompt: postinstallsetup.bat -Dweblogic.password=your_password -Ddatabase.password=!!cmx!! where your_password is the password for your WebLogic application server. 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. Installing the Cleanse Match Server 199

220 Installing the Cleanse Match Server (WebLogic/Windows) 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 192 and Configuring the Cleanse Match Server on page Configure your system to run multiple instances of your application server. For more information, see Configuring Multiple Instances of Your Application Server on page 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 201. 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. On WebLogic, create a separate domain for each cleanse instance. For more information, see your WebLogic documentation. 3. Test the second instance you just created. Now you can deploy Cleanse Match Server, as described in the next section. 200 Informatica MDM Hub Installation Guide

221 Installing the Cleanse Match Server (WebLogic/Windows) Deploying Cleanse Match Server on the 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, but you can deploy them manually on the application server. Deploying the EAR File Manually To deploy the EAR file manually, use the Administrative Console for deployment. Accept all defaults. 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. Installing the Cleanse Match Server 201

222 Installing the Cleanse Match Server (WebLogic/Windows) 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 servers 1. 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. 3. Using Hub Console, connect to the data store. 4. Choose the Cleanse Match Server workbench. 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. 202 Informatica MDM Hub Installation Guide

223 Installing the Cleanse Match Server (WebLogic/Windows) Below are the parameters that need to be set to utilize the cleanse servers based on the server configuration. Parameter Thread Count CPU Rating Description 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. 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. 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. Installing the Cleanse Match Server 203

224 Installing the Cleanse Match Server (WebSphere/Windows) 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. Installation Overview Cleanse Match Server installation involves the following steps: Step Task Instructions 1 Prepare the target environment, including Preparing for Installation on page 204 setting up the application server. 2 Install the Cleanse Match Server by running the installer. 3 Specify or change Cleanse Match Server configuration settings. Preparing for Installation Running the Cleanse Match Server Installer on page 211 Configuring the Cleanse Match Server on page 215 Complete the tasks in this section before you install the Cleanse Match Server. 204 Informatica MDM Hub Installation Guide

225 Installing the Cleanse Match Server (WebSphere/Windows) Fulfill Hardware and Software Requirements 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. Install and Configure WebSphere On the machine where you will run the Cleanse Match Server, install and configure your WebSphere environment according to your WebSphere documentation. 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. Obtain an Informatica License File 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. Installing the Cleanse Match Server 205

226 Installing the Cleanse Match Server (WebSphere/Windows) 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 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 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. 3. Login with any user name. 4. 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. (such as <WebSphere_install_dir>\AppServer\lib). 206 Informatica MDM Hub Installation Guide

227 Installing the Cleanse Match Server (WebSphere/Windows) 5. Create the security account to be used by the Informatica MDM Master Data Source: a. Expand Security in the console navigation tree. 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 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 208. e. Click OK to save. 6. Create the JDBC Provider: 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). 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. Installing the Cleanse Match Server 207

228 Installing the Cleanse Match Server (WebSphere/Windows) 7. 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 specify the following value: 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. Changing the Password for the CMX_SYSTEM User 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 To create your WebSphere 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. 208 Informatica MDM Hub Installation Guide

229 Installing the Cleanse Match Server (WebSphere/Windows) 3. Login with any user name. 4. 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. (for example, <WebSphere_install_dir>/AppServer/lib). 5. Create the security account to be used by the Informatica MDM ORS Data Source: a. Expand Security in the console navigation tree. 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 J2C Authentication Data. 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. 6. Create the JDBC Provider: a. Expand Resources in the console navigation tree and then expand the JDBC menu. Click 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. Installing the Cleanse Match Server 209

230 Installing the Cleanse Match Server (WebSphere/Windows) 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. 7. Create the Informatica MDM ORS 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. 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. Note: The JNDI name must be in lower case. 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. 210 Informatica MDM Hub Installation Guide

231 Installing the Cleanse Match Server (WebSphere/Windows) Register the schema with the same username and password. 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: 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. File names and directories in this section may vary slightly depending on what type of installation you are performing. 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 To install Cleanse Match Server: 1. Make sure that your application server is started and running correctly. 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. The License Agreement screen is displayed. Installing the Cleanse Match Server 211

232 Installing the Cleanse Match Server (WebSphere/Windows) 4. Click the I accept the terms of the License Agreement button and then click Next. The Choose Install Folder screen is displayed. 5. Do one of the following: 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. Important: Do not use a path that has spaces in the directory or folder names. 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. The Enter Location of License File screen is displayed. 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. 8. Click Next to continue. The Application Server screen is displayed. 9. Choose the WebSphere application server and click Next. The WebSphere Application Server Home screen is displayed. 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. 212 Informatica MDM Hub Installation Guide

233 Installing the Cleanse Match Server (WebSphere/Windows) 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. 12. 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. 13. 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 218 for instructions). 14. 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. The Please Wait screen is displayed while Informatica configures your system. When the installation completes, the Install Complete screen is displayed. 15. Choose Yes to restart your system, or choose No to restart it later and click Done to exit the Cleanse Match Server installer. Installing the Cleanse Match Server 213

234 Installing the Cleanse Match Server (WebSphere/Windows) Installation Log Files 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 <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 <infamdm_install_ directory>\hub\cleanse\logs\installprereq.log 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. Description Shows the Cleanse Match Server install errors and status. Shows the postinstallsetup script results. Cleanse server logs. Shows what was chosen during the installation. Contains the prerequisite messages generated during installation. Located in the tree under the install directory for your application server. 214 Informatica MDM Hub Installation Guide

235 Installing the Cleanse Match Server (WebSphere/Windows) 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 For more information regarding cleanse engine configuration, 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.bat file Installing the Cleanse Match Server 215

236 Installing the Cleanse Match Server (WebSphere/Windows) 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 cmxcleanse.properties file which is stored, by default, 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 the file after cleanse/strip is 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 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. 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.datalayer.cleanse.working_ 216 Informatica MDM Hub Installation Guide

237 Installing the Cleanse Match Server (WebSphere/Windows) files.location=c:\infamdm\hub\cleanse\tmp cmx.server.datalayer.cleanse.working_files=keep cmx.server.datalayer.cleanse.execution=local cmx.home=c:\infamdm\hub\cleanse cmx.appserver.type=websphere 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. 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>)) ) Installing the Cleanse Match Server 217

238 Installing the Cleanse Match Server (WebSphere/Windows) 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. Performing Post-installation Tasks This section describes tasks to complete after you have installed the software. Running PostInstallSetup If you chose to have the Cleanse Match Server installer skip the post-install process, you must run this manually. By default, this script is located in the following directory: <infamdm_install_directory>\hub\cleanse To run the post-install process manually, run the following command from a command prompt: postinstallsetup.bat -Ddatabase.password=!!cmx!! 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. 218 Informatica MDM Hub Installation Guide

239 Installing the Cleanse Match Server (WebSphere/Windows) 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 211 and Configuring the Cleanse Match Server on page Configure your system to run multiple instances of your application server. For more information, see Configuring Multiple Instances of Your Application Server on page 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 220. 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: 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. 3. Test the second instance you just created. Now you can deploy Cleanse Match Server, as described in the next section. Installing the Cleanse Match Server 219

240 Installing the Cleanse Match Server (WebSphere/Windows) Deploying Cleanse Match Server on the 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, but you can deploy them manually on the application server. Deploying the EAR File Manually To deploy the EAR file manually, use the Administrative Console for deployment. Accept all defaults. 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 220 Informatica MDM Hub Installation Guide

241 Installing the Cleanse Match Server (WebSphere/Windows) 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 servers 1. 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. 3. Using Hub Console, connect to the data store. 4. Choose the Cleanse Match Server workbench. 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. Parameter Thread Count Description 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. Installing the Cleanse Match Server 221

242 Installing the Cleanse Match Server (WebSphere/Windows) Parameter CPU Rating Description 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. 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. 222 Informatica MDM Hub Installation Guide

243 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

244 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: Make sure that Java Web Start has been installed. The following URL is a page that has a link to the Web Start installer: In these URLs, hostname is the host running your application server and port is the port on which that application server is listening. 224 Informatica MDM Hub Installation Guide

245 Starting the Hub Console Starting the Hub Console To launch the Hub Console: 1. Open a browser window and enter the following URL: 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

246 Starting the Hub Console 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. 226 Informatica MDM Hub Installation Guide

247 Starting the Hub Console 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. Launching the Hub Console 227

248 Starting the Hub Console Note: What you see might differ from this example screen shot. 228 Informatica MDM Hub Installation Guide