Installing the Cleanse Match Server - Knowledge Base

Transcription

MDM Multidomain Edition (Version 9.0.1)
Installation Guide for DB2
Informatica MDM Multidomain Hub - Version 9.0.1 - May 2011
Copyright (c) 2011 Informatica. All rights reserved.
This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing
restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited.
No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior
consent of Informatica Corporation. This Software is be protected by U.S. and/or international Patents and other Patents Pending.
Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as
provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013©(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR
52.227-14 (ALT III), as applicable.
The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report
them to us in writing.
Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer,
PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B
Data Exchange, Informatica On Demand and Siperian are trademarks or registered trademarks of Informatica Corporation in the United States and in
jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners.
Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies.
All rights reserved. Copyright © Sun Microsystems. All rights reserved.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and other software which is licensed under the
Apache License, Version 2.0 (the “License”). You may obtain a copy of the License at http://www.apache.org/licenses/
LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and
limitations under the License.
This product includes software which is licensed under the GNU Lesser General Public License Agreement, which may be found at
http://www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, “as-is”, without warranty of any kind, either express or
implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose.
This product includes software which is licensed under the CDDL (the “License”). You may obtain a copy of the License at
http://www.sun.com/cddl/cddl.html. The materials are provided free of charge by Informatica, “as-is”, without warranty of any kind, either express or implied,
including but not limited to the implied warranties of merchantability and fitness for a particular purpose. See the License for the specific language governing
permissions and limitations under the License.
This product includes software which is licensed under the BSD License (the “License”). You may obtain a copy of the License at
http://www.opensource.org/licenses/bsd-license.php. The materials are provided free of charge by Informatica, “as-is”, without warranty of any kind, either
express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. See the License for the specific
language governing permissions and limitations under the License.
This product includes software Copyright (c) 2003-2008, Terence Parr, all rights reserved which is licensed under the BSD License (the “License”). You may
obtain a copy of the License at http://www.antlr.org/license.html. The materials are provided free of charge by Informatica, “as-is”, without warranty of any
kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. See the License for the
specific language governing permissions and limitations under the License.
This product includes software Copyright (c) 2000 - 2009 The Legion Of The Bouncy Castle (http://www.bouncycastle.org) which is licensed under a form of
the MIT License (the “License”). You may obtain a copy of the License at http://www.bouncycastle.org/licence.html. The materials are provided free of charge
by Informatica, “as-is”, without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and
fitness for a particular purpose. See the License for the specific language governing permissions and limitations under the License.
DISCLAIMER: Informatica Corporation provides this documentation “as is” without warranty of any kind, either express or implied, including, but not limited
to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or
documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The
information in this software and documentation is subject to change at any time without notice.
NOTICES
This Informatica product (the “Software”) may include certain drivers (the “DataDirect Drivers”) from DataDirect Technologies, an operating company of
Progress Software
Corporation (“DataDirect”) which are subject to the following terms and conditions:
1. THE DATADIRECT DRIVERS ARE PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NON-INFRINGEMENT.
2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS,
WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF
ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY,
MISREPRESENTATION AND OTHER TORTS.
Contents
Preface
Intended Audience ...........................................................................................................................................xi
Contents............................................................................................................................................................xii
Learning About Informatica MDM Hub....................................................................................................xiv
Informatica Global Customer Support .......................................................................................................xvi
Informatica Resources ..................................................................................................................................xvii
Informatica Customer Portal .............................................................................................................xvii
Informatica Documentation ..............................................................................................................xvii
Informatica Web Site ..........................................................................................................................xvii
Informatica How-To Library............................................................................................................xviii
Informatica Knowledge Base............................................................................................................xviii
Informatica Multimedia Knowledge Base ......................................................................................xviii
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 Record Store (ORS)..................................................................12
iii
Relationships Among Databases in the Hub Store ......................................................................... 12
Single Informatica MDM Hub Version Requirement..................................................................... 14
Overview of Steps to Install the Hub Store................................................................................................ 14
Prepare Your DB2 Deployment for Informatica MDM Hub ................................................................. 16
Install and Configure DB2................................................................................................................... 16
Manual Database Creation............................................................................................................................. 16
Modify the Build Properties .......................................................................................................................... 19
Create a DB2 Database for the Hub Store ................................................................................................. 24
Tablespaces Used by the Hub Store .................................................................................................. 24
Create the Hub Store...................................................................................................................................... 25
About the Scripts .................................................................................................................................. 25
Create the Master Database (UNIX) ................................................................................................. 26
Create the Master Database (Windows) ............................................................................................ 28
Test the Database Connection...................................................................................................................... 29
Create an ORS Database................................................................................................................................ 30
About the db2ant.bat create_ors Script............................................................................................. 30
Adding an ORS (UNIX) ...................................................................................................................... 30
Adding an ORS (Windows)................................................................................................................. 32
Chapter 3: Installing the Hub Server
About the Hub Server .................................................................................................................................... 36
Application Server and Connection Pooling .................................................................................... 36
Manually Configuring Message Queues for Asynchronous SIF Requests................................... 36
PostInstallSetup..................................................................................................................................... 37
Single Informatica MDM Hub Version Requirement..................................................................... 37
Installing the Hub Server (JBoss/UNIX) ................................................................................................... 38
Installation Overview ........................................................................................................................... 38
Preparing for Installation ..................................................................................................................... 38
Running the Hub Server Installer....................................................................................................... 41
Configuring the Hub Server ................................................................................................................ 46
Performing Post-Installation Tasks.................................................................................................... 48
Installing the Hub Server (WebSphere/UNIX) ......................................................................................... 49
Installation Overview ........................................................................................................................... 49
iv
Informatica MDM Hub 9.0.1 Installation Guide
Preparing for Installation......................................................................................................................49
Running the Hub Server Installer .......................................................................................................51
Configuring the Hub Server.................................................................................................................59
Performing Post-Installation Tasks ....................................................................................................61
Installing the Hub Server (JBoss/Windows)...............................................................................................62
Installation Overview............................................................................................................................62
Installing the Hub Server (WebSphere/Windows) ....................................................................................73
Changing Passwords After Installation ........................................................................................................86
Changing the Password for the CMX_SYSTEM User....................................................................86
Changing the Password for the CMX_ORS User............................................................................86
Chapter 4: Installing the Cleanse Match Server
About the Cleanse Match Server...................................................................................................................88
Supported Cleanse Match Engines .....................................................................................................88
PostInstallSetup .....................................................................................................................................88
Single Informatica MDM Hub Version Requirement .....................................................................89
Installing the Cleanse Match Server (JBoss/UNIX) ..................................................................................89
Running the Cleanse Match Server Installer .....................................................................................94
Configuring the Cleanse Match Server.............................................................................................100
Performing Post-installation Tasks...................................................................................................107
Installing the Cleanse Match Server (WebSphere/UNIX)......................................................................108
Installation Overview..........................................................................................................................108
Contents
v
Preparing for Installation ................................................................................................................... 108
Running the Cleanse Match Server Installer................................................................................... 115
Configuring the Cleanse Match Server ............................................................................................ 120
Performing Post-installation Tasks .................................................................................................. 127
Installing the Cleanse Match Server (JBoss/Windows) .......................................................................... 128
Installation Overview ......................................................................................................................... 128
Installing the Cleanse Match Server (WebSphere/Windows)................................................................ 145
Installation Overview ......................................................................................................................... 145
Chapter 5: Launching the Hub Console
About the Hub Console............................................................................................................................... 166
Starting the Hub Console ............................................................................................................................ 167
Post-Installation Tasks ................................................................................................................................. 170
Chapter 6: Uninstalling Informatica MDM Hub
Uninstalling Informatica MDM Hub (JBoss/UNIX) ............................................................................. 172
Uninstalling the Cleanse Match Server ............................................................................................ 172
Uninstalling the Hub Server .............................................................................................................. 173
Uninstalling Informatica MDM Hub (WebSphere/UNIX)................................................................... 175
Uninstalling Informatica MDM Hub (JBoss/Windows) ........................................................................ 177
vi
Uninstalling Informatica MDM Hub (WebSphere/Windows) ..............................................................179
Uninstalling the Cleanse Match Server.............................................................................................179
Dropping Hub Store Databases........................................................................................................180
Uninstalling the Hub Server...............................................................................................................182
Uninstalling the Hub Store from DB2.......................................................................................................183
Database Objects to Drop .................................................................................................................183
Chapter 7: Troubleshooting
Informatica MDM Hub Log Files ..............................................................................................................186
Informatica MDM Hub Log Files (UNIX) .....................................................................................186
Informatica MDM Hub Log Files (Windows)................................................................................189
Bypassing Prerequisite Installation .............................................................................................................191
Updating Parameters After Installation .....................................................................................................191
Updating Hub Server Parameters After Installation ......................................................................191
Updating Cleanse Match Server Parameters After Installation ....................................................192
Checking the Hub and Cleanse Match Server Silent Install....................................................................193
Checking the Hub Server and Cleanse Match Server Silent Install (UNIX)..............................193
Checking the Hub Server and Cleanse Match Server Silent Install (Windows).........................196
MATCH Process Error: VerifyNeedToStrip ............................................................................................198
VerifyNeedToStrip (UNIX)...............................................................................................................198
VerifyNeedToStrip (Windows) .........................................................................................................199
Inaccurate Start/Stop Timestamp for ORS ..............................................................................................199
major.minor Version Errors When Loading Cleanse Match Server......................................................200
Low Cleanse/Match Application Server Performance............................................................................200
Troubleshooting (JBoss/UNIX).................................................................................................................201
Changing the Hub Server Parameters (JBoss/UNIX)...................................................................201
Manually Redeploying the Hub Server (JBoss/UNIX) .................................................................202
Manually Undeploying the Cleanse Match Server (JBoss/UNIX) ..............................................203
Setting the JVM Size (JBoss/UNIX)................................................................................................203
Troubleshooting (WebSphere/UNIX) ......................................................................................................204
Changing the Hub Server Parameters (WebSphere/UNIX) ........................................................204
Changing the Cleanse Match Server Parameters (WebSphere/UNIX) ......................................205
Changing the Hub Server Parameters for the Database (WebSphere/UNIX)..........................206
Contents
vii
Manually Redeploying the Hub Server Application (WebSphere/UNIX) ................................ 207
Manually Undeploying the Cleanse Match Server (WebSphere/UNIX) ................................... 208
Setting the JVM Size (WebSphere/UNIX)..................................................................................... 208
Changing the SOAP Request Timeout (WebSphere/UNIX)...................................................... 209
Troubleshooting (JBoss/Windows) ........................................................................................................... 209
Changing the Hub Server Parameters (JBoss/Windows)............................................................. 209
Manually Redeploying Hub Server (JBoss/Windows) .................................................................. 210
Manually Undeploying the Cleanse Match Server (JBoss/Windows)......................................... 212
Setting the JVM Size (JBoss/Windows) .......................................................................................... 212
Troubleshooting (WebSphere/Windows)................................................................................................. 213
Changing the Hub Server Parameters (WebSphere/Windows) .................................................. 213
Changing the Cleanse Match Server Parameters (WebSphere/Windows)................................. 214
Changing the Hub Server Parameters for the Database (WebSphere/Windows).................... 214
Manually Redeploying Hub Server (WebSphere/Windows)........................................................ 216
Manually Undeploying the Cleanse Match Server (WebSphere/Windows) .............................. 217
Setting the JVM Size (WebSphere/Windows)................................................................................ 217
Changing the SOAP Request Timeout (WebSphere/Windows)................................................. 218
Appendix A: Installing from the Command Line
Preparing for Installation ............................................................................................................................. 220
Installing from the Command Line (JBoss/UNIX) ................................................................................ 221
Installing Hub Server.......................................................................................................................... 221
Installing the Cleanse Match Server ................................................................................................. 224
Installing from the Command Line (WebSphere/UNIX)...................................................................... 226
Installing Informatica Hub Server.................................................................................................... 227
Installing the Cleanse Match Server ................................................................................................. 229
Silent Installation from the Command Line ............................................................................................. 232
Considerations When Using Silent Installation.............................................................................. 232
Properties Files for Silent Installation.............................................................................................. 233
Creating Your Properties File ........................................................................................................... 233
Running the Silent Install................................................................................................................... 239
viii
Appendix B: Manually Configuring Informatica System Message Queues
About Informatica MDM Hub Message Queues.....................................................................................242
Configuring Message Queues (JBoss/UNIX)...........................................................................................242
Creating and Configuring a New Message Queue..........................................................................243
Configuring Additional Message Queues ........................................................................................244
Configuring Message Queues (WebSphere/UNIX) ................................................................................245
Configure Message Queues (JBoss/Windows).........................................................................................248
Configure Message Queues (WebSphere/Windows) ..............................................................................251
Appendix C: Manually Creating Datasources
Informatica MDM Hub Datasources.........................................................................................................256
Manually Creating Datasources in Websphere 6.1.0.29...........................................................................256
Start the WebSphere Application Server .........................................................................................256
Specifying the Location of the Driver Libraries .............................................................................256
Creating the Security Account ...........................................................................................................257
Creating the JDBC Provider ..............................................................................................................257
Creating the Master Datasource ........................................................................................................258
Changing the CMX_ORS User Password .......................................................................................258
Contents
ix
x Informatica MDM Hub 9.0.1 Installation Guide
Intended Audience
Preface
Welcome to the Informatica MDM Hub™ 9.0.1 Installation Guide. This guide explains
how to perform a first-time installation of Informatica MDM Hub Server and the
Cleanse Match Server.
Note If you are upgrading from a previous version of Informatica MDM Hub, see the
Informatica MDM Upgrade Technical Note 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 DB2 administration is particularly
important. Other administration and configuration tasks are described in the Informatica
MDM Hub Administrator Guide.
xi
Contents
Contents
This guide contains the following chapters.
Chapter 1, “Introduction”
Recommended reading for for all users.
Describes Informatica MDM Hub architecture and
orients you to the installation process
Chapter 2, “Installing the Hub Store”
Recommended reading for DBAs.
Explains how to install the Hub Store
Chapter 3, “Installing the Hub Server” Recommended reading for system / application
server administrators.
Explains how to install and configure Hub Server
Chapter 4, “Installing the Cleanse
Match Server”
Recommended reading for system / application
server administrators.
Explains how to install and configure Cleanse Match
Server
Chapter 5, “Launching the Hub
Console”
Recommended reading for all users.
Explains how to launch the Hub Console
Chapter 6, “Clustering”
Recommended reading for system /application server
administrators.
Explains how to configure clustering for Informatica
MDM Hub.
Chapter 6, “Uninstalling Informatica
MDM Hub”
administrators.
Explains how to uninstall your Informatica MDM
Hub system
Chapter 7, “Troubleshooting”
Recommened reading for all users.
Explains how to troubleshoot your installation
Appendix A, “Installing from the
Command Line”
administrators.
Explains how to install Informatica Hub Server and
Cleanse Match Server from the command line. UNIX
implementations only.
Appendix B, “Manually Configuring
Informatica System Message Queues” administrators.
Explains how to configure message queues for use
with Informatica MDM Hub.
xii
Contents
Appendix C, “Manually Creating
Datasources”
Recommended reading for system administrators
Explains how to manually create a master database
and one or more additional ORSs.
Index
Index for this guide
xiii
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 a Informatica MDM Hub
Installation Guide for each supported platform.
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.
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
xiv
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 a 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 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.
xv
You can contact a Customer Support Center by telephone or through the WebSupport
Service. WebSupport requires a user name and password. You can request a user name
and password at http://my.informatica.com. Use the following telephone numbers to
contact Informatica Global Customer Support:
North America / South
America
Europe / Middle East /
Africa
Asia / Australia
Toll Free
Toll Free
Toll Free
North America
+1 877 463 2435
United Kingdom
00800 4632 4357
or 0800 023 4632
Australia 1 800 151 830
Brazil 0800 891 0202
Mexico 001 888 209 8853
France 00800 4632 4357
New Zealand 1 800 151 830
Singapore 001 800 4632 4357
Netherlands 00800 4632 4357
Germany 00800 4632 4357
Switzerland 00800 4632 4357
or 0800 463 200
Israel 00800 4632 4357
Spain 900 813 166
Portugal 800 208 360
Italy 800 915 985
Standard Rate
Standard Rate
Standard Rate
North America
+1 650 653 6332
France 0805 804632
India +91 80 4112 5738
Germany 1805 702 702
Netherlands 030 6022 797
xvi
Informatica Customer Portal
As an Informatica customer, you can access the Informatica Customer Portal site at
http://my.informatica.com. The site contains product information, user group
information, newsletters, access to the Informatica customer support case management
system (ATLAS), the Informatica How-To Library, the Informatica Knowledge Base,
the Informatica Multimedia Knowledge Base, Informatica Documentation Center, and
access to the Informatica user community.
Informatica Documentation
The Informatica Documentation team takes every effort to create accurate, usable
documentation. If you have questions, comments, or ideas about this documentation,
contact the Informatica Documentation team through email at infa_
[email protected]. We will use your feedback to improve our
documentation. Let us know if we can contact you regarding your comments.
The Documentation team updates documentation as needed. To get the latest
documentation for your product, navigate to the Informatica Documentation Center
from http://my.informatica.com.
Informatica Web Site
You can access the Informatica corporate web site at http://www.informatica.com.
The site contains information about Informatica, its background, upcoming events,
and sales offices. You will also find product and partner information. The services area
of the site includes important information about technical support, training and
education, and implementation services.
xvii
Informatica How-To Library
As an Informatica customer, you can access the Informatica How-To Library at
http://my.informatica.com. The How-To Library is a collection of resources to help
you learn more about Informatica products and features. It includes articles and
interactive demonstrations that provide solutions to common problems, compare
features and behaviors, and guide you through performing specific real-world tasks.
Informatica Knowledge Base
As an Informatica customer, you can access the Informatica Knowledge Base at
http://my.informatica.com. Use the Knowledge Base to search for documented
solutions to known technical issues about Informatica products. You can also find
answers to frequently asked questions, technical white papers, and technical tips. If you
have questions, comments, or ideas about the Knowledge Base, contact the
Informatica Knowledge Base team through email at [email protected].
Informatica Multimedia Knowledge Base
As an Informatica customer, you can access the Informatica Multimedia Knowledge
Base at http://my.informatica.com. The Multimedia Knowledge Base is a collection of
instructional multimedia files that help you learn about common concepts and guide
you through performing specific tasks. If you have questions, comments, or ideas about
the Multimedia Knowledge Base, contact the Informatica Knowledge Base team
through email at [email protected].
xviii
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.
Chapter Contents
•
Before You Begin
•
Installation Overview
•
Designing Your Informatica MDM Hub Installation
•
Documenting Your Installation
Introduction 1
Before You Begin
Before You Begin
Before you begin, be sure to complete the following tasks:
Task
Resource
Read the Informatica MDM Hub Release Notes for
requirements and additional information about
pre-installation preparation.
Informatica MDM Hub Release Notes
Read the worksheet for your installation—created
by an Informatica Global Customer Support
representative (see“Informatica Global Customer
Support” on page xvi)—indicating the hardware
and software needed to install Informatica MDM
Hub at your location.
Product Availability Matrics
Install and configure your site’s cleanse engine, if
applicable, according to the vendor’s instructions.
Vendor documentation for your
cleanse engine
Read the Informatica MDM Hub Overview for an
introduction to the product architecture and key
components.
Informatica MDM Hub Overview
2 Informatica MDM Hub 9.0.1 Installation Guide
To install Informatica MDM Hub, complete the following steps in the exact order
specified:
Step
Task
Instructions
1
Install the Hub Store in your DB2
database.
“Installing the Hub Store” on page 11
2
Install the Hub Server software.
“Installing the Hub Server” on page 35
3
Install and configure one or more
Cleanse Match Servers.
“Installing the Cleanse Match Server” on
page 87
4
Launch the Hub Console and verify your “Launching the Hub Console” on page
installation.
165
Introduction 3
Before you install Informatica MDM Hub, you need to decide how and where to set
up the various components that will comprise your Informatica MDM Hub
implementation.
Implementation Components
As described in the Informatica MDM Hub Overview, an Informatica MDM Hub
installation includes the following key components.
Component
Description
Hub Store
A collection of databases in which business data is stored and
consolidated. A Hub Store consists of one Master Database (which
contains environment configuration settings for the Informatica
MDM Hub) and one or more Operational Record Stores—or ORS
databases (which contains master data, content metadata, processing
rules, and other information related to business data).
Hub Server
Run-time component that manages core and common services for
the Informatica MDM Hub. The Hub Server is a J2EE application,
deployed on the application server, that orchestrates the data
processing within the Hub Store, as well as integration with external
applications.
The Hub Console, which is packaged inside the Hub Server
application, is the Informatica MDM Hub user interface that
comprises a set of administrative and data management tools for
administrators and data stewards. It can be launched on any client
machine via a URL using a browser and Sun’s Java Web Start.
Cleanse Match Server
Run-time component that handles cleanse and match requests and is
deployed in the application server environment. The Cleanse Match
Server contains a cleanse server that handles data cleansing
operations, and a match server that handles match operations.
Cleanse Engine(s)
Any of the supported cleanse engines, as described in Informatica
MDM Hub Cleanse Adapter Guide. The Cleanse Match Server and the
cleanse engine work together to standardize the data and to optimize
the data for match and consolidation.
Installation Environments
Informatica MDM Hub implementations comprise multiple environments, such as
development, test, and production. Each type of environment comes with its own set
of unique requirements and priorities. Therefore, the installation design will differ for
each environment.
Example Installations
There are many possible ways in which you can set up the various Informatica MDM
Hub components in your environment. This section provides two examples of
Informatica MDM Hub installations. Their purpose is instructive rather than
prescriptive—they illustrate some general principles to consider while designing your
installation. They are not intended as recommended or even suggested installation
designs.
Introduction 5
All Components on a Single Host
In the following example, all Informatica MDM Hub core components are installed on
a single host machine.
o
This layout simplifies communication among the components within a single host
environment.
Components Distributed on Multiple Hosts
In the following example, various Informatica MDM Hub components are distributed
among multiple host machines.
Note: There needs to be an DB2 client installed on both the Hub Server and the
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
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 xvi).
Installation and Post-Installation Documentation
Sources of information about your Informatica MDM Hub installation include:
Information About
Source of Information
ORS metadata
Validation Results report from the Metadata Manager tool in the Hub
Console. Used to document ORS metadata after the installation.
For instructions, see Informatica MDM Hub Metadata Manager Guide.
configuration settings
Environment Report from the Enterprise Manager tool in the Hub
Console. Used to document Hub Server, Cleanse Match Server,
Master Database, and ORS database information after installation.
For instructions, see Appendix D, “Viewing Configuration Details,”
in the Informatica MDM Hub Administrator Guide.
database changes
Database debug log. Used to log database events for your Hub Store
once an ORS is registered in the Hub Console. Enabled according to
the instructions in “Enabling Debug Logging” on page 188.
installation process
Informatica MDM Hub Installer log files. Used to capture events that
occur during Hub Server and Cleanse Match Server installation.
Hub Server and
Hub Server and Cleanse Match Server log files, which capture
run-time events after these components are running.
Hub Console
Hub Console log files that capture activity while using the Hub
Console.
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.
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 xvi) for analysis.
Introduction 9
Installing the Hub Store
This chapter explains how to install the Hub Store on a DB2 database platform.
Your DB2 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 product availability matrix
for system requirements.
Chapter Contents
•
About the Hub Store
•
Overview of Steps to Install the Hub Store
•
Prepare Your DB2 Deployment for Informatica MDM Hub
•
Manual Database Creation
•
Create a DB2 Database for the Hub Store
•
Tablespaces Used by the Hub Store
•
Create the Hub Store
•
Test the Database Connection
•
Create an ORS Database
Installing the Hub Store 11
About the Hub Store
About the Hub Store
The Hub Store is where business data is stored and consolidated in Informatica MDM
Hub.
Master Database and Operational Record Store (ORS)
The Hub Store is a collection of databases that includes:
Element
Description
Master Database
Contains the Informatica MDM Hub environment configuration
settings—user accounts, security configuration, ORS registry,
message queue settings, and so on. A given Informatica MDM Hub
environment can have only one Master Database. The name of the
schema containing the “Master Repository” is CMX_SYSTEM.
Operational Record
Store (ORS)
Database that contains the master data, content metadata, the rules
for processing the master data, the rules for managing the set of
master data objects, along with the processing rules and auxiliary
logic used by the Informatica MDM Hub in defining the best version
of the truth (BVT). A Informatica MDM Hub configuration can have
one or more ORSes. 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 one or
more ORS databases. 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.
About the Hub Store
This architecture allows you to distribute ORS schemas 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 should only be 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.
13
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.
To install the Hub Store, complete the following steps in the exact order specified:
Step
Task
Instructions
1
Install and configure DB2 on a
machine other than the machine on
which your Hub Server will run.
“Prepare Your DB2 Deployment for
Informatica MDM Hub” on page 16
2
Create a DB2 database for your Hub
Store.
“Create a DB2 Database for the Hub Store”
on page 24
3
Create the DB2 tablespaces required
for the Hub Store.
“Tablespaces Used by the Hub Store” on
page 24
4
Create the Hub Store—Master
Database and ORS database(s)—by
running the scripts provided in your
Informatica MDM Hub distribution.
“Create the Hub Store” on page 25
5
Test the database connection.
“Test the Database Connection” on page 29
6
Register the newly-created ORS
database using the Databases tool in
the Hub Console.
“Configuring Operational Record Stores and
Datasources” in the Informatica MDM Hub
Administrator Guide (see “Post-Installation
Tasks” on page 170)
7
Enable database logging for this ORS
using the Enterprise Manager tool in
the Hub Console.
Appendix D, “Viewing Configuration
Details,” in the Informatica MDM Hub
Administrator Guide (see “Post-Installation
Tasks” on page 170)
High-level overview of the DB2 installation
The steps to create cmx_system and ORS.
1. Modify db-build.properties in
hub[hub-root]\server\resources\database\db2
2.
db2ant.bat create_db
to create database
This command will create thedatabase automatically. If you want to create your
database manually see “Create the Hub Store” on page 25 for more information
on manually creating a database.
to create cmx_system
3.
db2ant.bat create_system
4.
db2ant.bat compile_system
5.
db2ant.bat create_ors
6.
db2ant.bat compile
to create ORS.
Note: The compile may take a long time.
If you need to add more ORS databases to your Hub Store, run the db2ant.bat create_
ors script (provided in your Informatica MDM Hub distribution) according to the
instructions in “Create an ORS Database” on page 30.
Note: Your DB2 database administrator might need to complete the tasks in this
chapter.
15
Prepare Your DB2 Deployment for Informatica MDM Hub
Prepare Your DB2 Deployment for Informatica MDM
Hub
This section describes how to prepare your DB2 deployment for Informatica MDM
Hub. It applies to all supported platforms and application servers.
Install and Configure DB2
Install and configure DB2 on a machine that complies with the hardware and software
requirements described in the Product Availability Matrix (PAM) for Informatica MDM
Multidomain Edition 9.0.1 for DB2. Refer to this document for a list of supported DB2
versions.
The following software (part of your DB2 distribution) must be installed on every
machine on which you want to run the Hub Server:
• DB2 client
•
Cleanse Server
•
DB2 Java utilities (required by the DB2 client)
Note: Be sure to install DB2 with all Java options selected.
The MDM Hub provides the necessary scripts for automatic database creation as part
of the installation. To create a database manually there are several requirements.
Requirements
1. The database should be created with compatibility vector turned on (db2set DB2_
COMPATIBILITY_VECTOR=ORA). See more details in the official IBM
documentation:
http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?to
pic=/com.ibm.db2.luw.apdv.porting.doc/doc/r0052867.html.
2.
The database should be created with "UTF-8 TERRITORY US" locale.
3.
In tablespace creation the page size for system’s temporary tablespace should be
equal to the user’s temporary tablespace.
Options
Below is a list of recommended / mandatory options for manual database creation:
[DB2 environmental]
db2set DB2CODEPAGE=1208
db2set DB2_COMPATIBILITY_VECTOR=ORA
db2set DB2_DEFERRED_PREPARE_SEMANTICS=YES
db2set DB2_RESTORE_GRANT_ADMIN_AUTHORITIES=ON
db2set DB2_HASH_JOIN=YES
db2set DB2_ANTIJOIN=YES
db2set DB2_INLIST_TO_NLJN=NO
db2set DB2_SELECTIVITY=ALL
db2set DB2NTNOCACHE=ON
db2set DB2_EXTENDED_OPTIMIZATION=ON,ENHANCED_MULTIPLE_
DISTINCT,IXOR,SNHD
[Instance]
update dbm
update dbm
update dbm
update dbm
update dbm
update dbm
[DB]
update
update
update
update
update
update
update
update
update
update
update
update
update
update
update
db
db
db
db
db
db
db
db
db
db
db
db
db
db
db
cfg
cfg
cfg
cfg
cfg
cfg
cfg
cfg
cfg
cfg
cfg
cfg
cfg
cfg
cfg
cfg
cfg
cfg
cfg
cfg
cfg
using
using
using
using
using
using
using
using
using
using
using
using
using
using
using
using
using
using
using
using
using
SYSADM_GROUP DB2ADMNS
MON_HEAP_SZ AUTOMATIC
JAVA_HEAP_SZ 2048
AGENT_STACK_SZ 256
SHEAPTHRES 0
INTRA_PARALLEL YES
LOCKLIST AUTOMATIC
MAXLOCKS AUTOMATIC
PCKCACHESZ 50000
DBHEAP AUTOMATIC
CATALOGCACHE_SZ 25000
LOGBUFSZ 4096
UTIL_HEAP_SZ 50000
BUFFPAGE 250
STMTHEAP AUTOMATIC
APPLHEAPSZ AUTOMATIC
APPL_MEMORY AUTOMATIC
STAT_HEAP_SZ AUTOMATIC
LOGFILSIZ 128000
LOGPRIMARY 10
LOGSECOND 200
17
update
update
update
update
db
db
db
db
cfg
cfg
cfg
cfg
using
using
using
using
auto_reval deferred_force
decflt_rounding round_half_up
SORTHEAP 0
SHEAPTHRES_SHR AUTOMATIC
[Grants]
GRANT EXECUTE ON MODULE SYSIBMADM.UTL_DIR TO PUBLIC WITH GRANT
OPTION
GRANT EXECUTE ON MODULE SYSIBMADM.UTL_FILE TO PUBLIC WITH GRANT
OPTION
GRANT EXECUTE ON MODULE SYSIBMADM.DBMS_SQL TO PUBLIC WITH GRANT
OPTION
[Buffer pools]
CREATE BUFFERPOOL REPOS_POOL IMMEDIATE SIZE 1500 PAGESIZE 32 K
CREATE BUFFERPOOL CMX_POOL IMMEDIATE SIZE 3000 PAGESIZE 32 K
[Tablespaces]
CREATE REGULAR TABLESPACE CMX_REPOS PAGESIZE 32 K MANAGED BY
DATABASE USING ( FILE 'c:\dbhub901\CMX_REPOS\/cmx_repos01.dat'
500 M ) EXTENTSIZE 16 AUTORESIZE YES OVERHEAD 10.5 PREFETCHSIZE
16 BUFFERPOOL REPOS_POOL DROPPED TABLE RECOVERY ON
CREATE REGULAR TABLESPACE CMX_DATA PAGESIZE 32 K MANAGED BY DATABASE
USING ( FILE 'c:\dbhub901\CMX_DATA\/cmx_data01.dat'
500
M ) EXTENTSIZE 16 AUTORESIZE YES OVERHEAD 10.5 PREFETCHSIZE 16
BUFFERPOOL CMX_POOL DROPPED TABLE RECOVERY ON
CREATE REGULAR TABLESPACE CMX_TEMP PAGESIZE 32 K MANAGED BY DATABASE
USING ( FILE 'c:\dbhub901\CMX_TEMP\/cmx_temp01.dat'
500
CREATE REGULAR TABLESPACE CMX_INDX PAGESIZE 32 K MANAGED BY DATABASE
USING ( FILE 'c:\dbhub901\CMX_INDX\/cmx_indx01.dat'
500
CREATE USER TEMPORARY TABLESPACE CMX_USER_TEMP PAGESIZE 32 K MANAGED
BY DATABASE USING ( FILE 'c:\dbhub901\USER_TEMP\/cmx_user_
temp01.dat' 500 M ) EXTENTSIZE 16 AUTORESIZE YES OVERHEAD 10.5
PREFETCHSIZE 16 BUFFERPOOL CMX_POOL
CREATE SYSTEM TEMPORARY TABLESPACE CMX_SYS_TEMP PAGESIZE 32 K
MANAGED BY DATABASE USING ( FILE 'c:\dbhub901\SYSTEM_TEMP\/cmx_
sys_temp01.dat'
500 M ) EXTENTSIZE 16 AUTORESIZE YES OVERHEAD
10.5 PREFETCHSIZE 16 BUFFERPOOL CMX_POOL
Modify the Build Properties
The parameters above may vary depending on hardware configuration and sizing
requirements.
• 16GB dedicated to DB2 instance:
•
update dbm cfg using INSTANCE_MEMORY 4194304
•
update db cfg using DATABASE_MEMORY 4035830
•
ALTER BUFFERPOOL REPOS_POOL IMMEDIATE SIZE 16384
•
ALTER BUFFERPOOL CMX_POOL IMMEDIATE SIZE 262144
•
4GB dedicated to DB2 instance:
•
update dbm cfg using INSTANCE_MEMORY 940000
•
update db cfg using DATABASE_MEMORY 800000
•
ALTER BUFFERPOOL REPOS_POOL IMMEDIATE SIZE 3200
•
ALTER BUFFERPOOL CMX_POOL IMMEDIATE SIZE 32768
Additional recommendations:
• Drop default system temporary tablespace so that only CMX_SYS_TEMP
tablespace remains with CMX_POOL defined: DROP TABLESPACE
tempspace1.
•
To enable parallel I/O if DB files reside on several discs or on the RAID; can have
exact degree of parallelism usually equal to number of used discs: db2set DB2_
PARALLEL_IO=*
Before executing any kind of the provided database-related scripts, it is necessary to
modify the db-build.properties file bundled with the distribution. It summarizes all
database-related parameters into single place: database instance (optional in case of
manual database creation); master repository (CMX_SYSTEM); ORS (by default
CMX_ORS).
19
Go to the distribution folder \database\db2 , and copy the db2 folder to your local
machine. Open the db-build.properties file in the \db2 folder..
Note: The file might be archived, so extract its contents to some temporary folder
first.
Windows version
For the Windows db-build.properties file, modify the following items:
###Section of properties indented for changing
#Database host name or IP address - host name where DB2 is running
db2.host=vm1-dazarov
#Database port - TCP/IP port number used by DB2 on db2.host
db2.port=50000
#Database admin user login - the user name that is included in the
#DB2ADMINs group
db2.admin.user=db2admin
#Database admin user password - the password for the db2.admin.user
db2.admin.password=ibmdb2a
#Database user login on behalf of which schemas are created
#-- the user name that is not included in the into DB2ADMNS group
#a. For db2.user to be able to look into system dictionaries they
#must be included in the user SYSMON group.
#b. Create group, for example DB2MONGRP, add our user to this group
#and perform:
#1. db2 "update dbm cfg using sysmon_group DB2MONGRP"
#2. db2stop force
#3. db2start
#Itis also possible to use admin user here
db2.user=db2user
#Database user password - the password for db2.user
db2.password=ibmdb2
#Database name - the database name - the db2.db name should not
#exceed 8 characters
db2.db_name=SIP901
#System schema name db2.cmx_system_schema=CMX_SYSTEM
#ORS schema name - the name for the ORS in uppercase
db2.cmx_ors_schema=CMX_ORS
#OS group name for database administrators - the DB2 administrative
#group(default is DB2ADMNS)
db2.admin.group=DB2ADMNS
#Database instance name of node name for remote clients
#- the DB2 instance name
db2.instance=NDE2D708
#Path for database files at database server host - the path to where
#the database is located. Use ‘\\’ as separators.
db2.storage.path=c:\\sip901\\database
#Switch database statements log on/off at build time
db2.verbose=true
#ORS database logging indicator (1 - on, 0 - off) - the debug
#indicator.(1:debug enabled, 0:debug disabled)
db2.debug.ind=1
#ORS database log file path - the path to where the debug is
#located. This path should exist in the system.
db2.debug.path=c:\\temp\\
#ORS database log file name - the debug log file nameS
db2.debug.file=cmx_debug.log
###Section of properties not intended to be changed except special
cases
###In case of automatic database creation pay attention to the
following attributes:
### - db2.cmx_transaction_log.path
### - db2.cmx_transaction_log.logfilsiz
### - db2.cmx_transaction_log.logprimary
### - db2.cmx_transaction_log.logsecond
#Shell name to execute working processes
shell.name=sh
#Temporary folder name
tmp.path=tmp
#Build log files folder
log.path=logs
compile_dev.log_file=compile_dev.log
obfuscate.log_file=obfuscate.log
create_db.log_file=create_db.log
create_remote_db.log_file=create_remote_db.log
create_system.log_file=create_system.log
compile_system.log_file=compile_system.log
create_ors.log_file=create_ors.log
21
compile.log_file=compile.log
compile_pkg.log_file=compile_pkg.log
rebind_packages.log_file=rebind_packages.log
drop_schema.log_file=drop_schema.log
migrate_ors.log_file=migrate_ors.log
migrate_system.log_file=migrate_system.log
#Path for catalog tablespace
db2.syscat.path=${db2.storage.path}\\SYSCAT\\
#Path for user tablespace
db2.user.path=${db2.storage.path}\\USER\\
#Path for temporary tablespace
db2.systemp.path=${db2.storage.path}\\SYSTEMP\\
#CMX_REPOS buffer pool nbame
db2.cmx_repos_bp=REPOS_POOL
#CMX_BP buffer pool name
db2.cmx_bp=CMX_POOL
#Path for CMX_REPOS tablespace
db2.cmx_repos.path=${db2.storage.path}\\CMX_REPOS\\
#Path for CMX_DATA tablespace
db2.cmx_data.path=${db2.storage.path}\\CMX_DATA\\
#Path for CMX_TEMP tablespace
db2.cmx_temp.path=${db2.storage.path}\\CMX_TEMP\\
#Path for CMX_INDX tablespace
db2.cmx_indx.path=${db2.storage.path}\\CMX_INDX\\
#Path for CMX_USER_TEMP tablespace
db2.cmx_user_temp.path=${db2.storage.path}\\USER_TEMP\\
#Path for CMX_SYS_TEMP tablespace
db2.cmx_sys_temp.path=${db2.storage.path}\\SYSTEM_TEMP\\
#Path for transaction logs at database host
#In case of automatic database creation make this path exists before
running create_db/create_remote_db
db2.cmx_transaction_log.path=${db2.storage.path}/LOGS
#DB2 LOGFILSIZ option value (refer database manual for details)
db2.cmx_transaction_log.logfilsiz=102400
#DB2 LOGPRIMARY option value (refer database manual for details)
db2.cmx_transaction_log.logprimary=10
#DB2 LOGSECONDARY option value (refer database manual for details)
db2.cmx_transaction_log.logsecond=10
#Path to release scripts
script.release_scripts.path=${basedir}
#Path to system schema IXF files
script.system.schema.path=${basedir}/data_schema_system
#Path to ORS schema IXF files
script.ors.schema.path=${basedir}/data_schema_ors
#Path to packages
script.pkg.path=${basedir}
#Path to db2 specific procedures
script.db2spec.path=${basedir}
#Path to intermediate packages
script.preprocessed.path=${basedir}
#Path to external Java stored procedures jar files
script.jar.path=${basedir}/jar
#Path to release scripts
script.release_dbs.path=${basedir}
#Path to release tool scripts
script.release_dbs.tools.path=${basedir}
#Path to release common scripts
script.release_dbs.common.path=${basedir}
#Path to ORS migration scripts
script.migrate.ors.path=${basedir}/db_changes/db2/ors
#Path to system migration scripts
script.migrate.system.path=${basedir}/db_changes/db2/system
#Path to intermediate packages
script.obfuscated.path=${basedir}
#ant-contrib jar file name
ant_contrib.file=ant-contrib-1.0b3.jar
#Intermediate tool path
preprocessor.jar.path=../Projects/Build/Release
#Internal flag
db2.obfuscate=false
For UNIX:
All path-based properties in the db2-build.properties files should converted to
UNIX style, namely replace all "\\" entries with "/" (there should not be any
Windows-style full paths like c:\\temp).
If you want to change the name of your system schema name or your ORS schema
name, modify the entries in the db-build.properties file.
23
Note: You may need to restart your DB2 server after creating the data base.
This section describes how to create a DB2 database with the help of bundled scripts.
If you choose to create the database manually, you may want to skip this section.
Once DB2 has been properly installed and configured, and the db-build.properties
file has been modified, create the DB2 database and the associated tablespaces using
the db2ant.bat create_db script.
Note: The instructions for running the commands assume that you are logged into
your DB2 database with administrator (or ADMIN) privileges and are running
commands from a command prompt.
Open a DB2 command window. To create the database and tablespaces, change
directories to ...\database\db2 and type:
db2ant.bat create_db
This script creates both the DB2 database and the associated tablespaces. It is included
with your Informatica MDM distribution. The DB2 database will contain your Hub
Store. The script also sets the appropriate DB2 registry values.
Tablespaces Used by the Hub Store
Hub Store requires six tablespaces with the following names:
Tablespace
Description
CMX_DATA
Default tablespace for the ORS schema (regular tablespace).
CMX_INDX
Used for indexes created and used by Informatica MDM Hub (regular
tablespace).
CMX_TEMP
Used for temporary tables created and used by Informatica MDM Hub;
used for stored procedures (regular tablespace).
CMX_REPOS
Contains objects belonging to ORS repository (regular tablespace)
Tablespace
Description
CMX_USER_
TEMP
The tablespace used for operational temporary tables (user temporary
tablespace).
CMX_SYS_
TEMP
The tablespace required for SQL operations (system temporary tablespace).
Note: These tablespace names are required for your Hub Store.
For subsequent Hub Store setup, you will need the following information about this
database:
Configuration Information
Database server port (such as 50000)
DB2 database server name (host running DB2)
DB2 ADMIN username (such as ADMIN)
DB2 SYSTEM password
Note: If your Informatica MDM Hub implementation will have multiple ORS
databases distributed across different host servers, you will need to create DB2
databases on each of those machines.
This section describes how to create the Hub Store and its additional databases. At a
minimum, your Hub Store consists of one Master Database and one or more ORS
databases.
About the Scripts
Your Informatica MDM Hub distribution includes the scripts to create the Hub Store
and an additional ORS. Before using these scripts it is important to modify
db-build.properties file (see previous chapter).
25
These scripts are:
• db2ant.bat create_system - creates the Master Schema
(name: CMX_SYSTEM)
•
db2ant.bat create_ors - creates one ORS schema
(default name: CMX_ORS)
•
•
db2ant.bat compile
- compiles stored procedures for master schema
- compiles the master database
Note: For any *NIX systems, name of the shell scripts is db2ant.sh.
You can run these scripts for stored procedures for a particular ORS when you first
install the Informatica MDM Hub. Once the Hub Store is created, if you need to add
more ORS databases, you can run db2ant.bat create_ors according to the
instructions in “Create an ORS Database” on page 30.
Default Database Names and Usernames
When running the script, the default master schema name is CMX_SYSTEM and the
default ORS schema name is CMX_ORS. The ORS can be named any name less than
eight characters. MDM Hub can support multiple ORSs
Create the Master Database (UNIX)
Complete the following steps to create the Master Database:
1. Create a directory on the DB2 database server host or on a client workstation that
has the DB2 client installed with DB2 utilities (db2-binary).
Copy all of the files from the Informatica MDM Hub distribution (<infamdm_
distribution_folder>/database/db2) to the directory you just created..
Note: These files might be archived.
2.
Change directory to the temporary directory you just created.
3.
Modify the db-build.properties file. See “Modify the Build Properties” on
page 19 for more details).
4.
Execute the script in the database/db2 directory:
./db2ant.sh create_system
5.
After the setup script is complete, check the following log file:
•
create_system.log
These log files are in the directory /database/db2/logs. 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 errors in the logs, resolve these
first with your DBA and/or database vendor, and then re-run the db2ant.sh
create_system script.
•
Copy the log files to the installation documentation directory you created
earlier. See “Documenting Your Installation” on page 8 for instructions.
27
6.
Execute the script in the database/db2 directory:
db2ant.sh complie_system./db2ant.sh compile_system
After the compile script is complete, this log file is created in the log directory
from which you ran the scripts:
•
7.
compile_system.log
Review this file 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.
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-Installation Tasks” on page 170.
Create the Master Database (Windows)
If DB2 is running in the Windows environment, complete the following steps to create
the Master Database:
1. Create a temporary directory on the DB2 database server host or on a client
workstation that has a DB2 client installed with DB2 utilities.
Copy all of the files from the Informatica MDM Hub distribution (<infamdm_
distribution_folder>/database/db2) to the directory you just created.
Note: The files may be archived .
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.
page 19 for more details.
5.
Run the db2ant.bat create_system script. Change diretories to
...\database\db2 directory and type the following command:
db2ant.bat create_system
6.
After the setup script is complete, check the following log file:
•
create_system.log
These log files are in the directory /database/db2/logs. Review these files to
ensure that no errors occurred.
7.
•
You may see some warnings, which can be ignored.
•
Errors must be addressed. If you see database errors in the logs, resolve these
first with your DBA and/or database vendor, and then re-run the
db2ant.bat create_system.
•
Copy the log files to the installation documentation directory you created
earlier. See “Documenting Your Installation” on page 8 for instructions.
•
compile_system.log
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. Connect to the database with the following command:
db2 connect to local_db_name user username
using password.
The user is the user that will be used for accessing ORSs in this database.
2.
Check to make sure that you can list all the tables with the following command:
db2 list tables for all;
29
3.
Disconnect from the database wiht following command:
db2 disconnect_local_db_name
4.
Verify that the database connections work properly.
This section describes how to create an ORS database in the Hub Store.
The instructions in this section assume that you have already created the Master
Database according to the instructions in “Create the Hub Store” on page 25.
About the db2ant.bat create_ors Script
Your Informatica MDM Hub distribution includes a db2ant.bat create_ors script
that:
• creates one ORS schema (default name: CMX_ORS)
Important: A Master schema is required to run the db2ant.bat create_ors script.
It does not create a Master Schema for you.
Default Schema Name
When running the db2ant.bat create_ors script, the default ORS schema name is
CMX_ORS. You can change this name in the db2-build.properties file.
Adding an ORS (UNIX)
To set up the Hub Store with an additional ORS schema:
1. Create a directory on the DB2 database server host or on a client workstation that
has the DB2 client installed with DB2 utilities.
Copy all of the files from the distribution directory <infamdm_distribution_
folder>/database/db2) to the directory you just created.
Note: The directory might be archived.
2.
Change directory to the temporary directory you just created.
3.
Modify the db-build.properties file so that the db2.cmx_ors_schema has the
name of the new schema. See “Modify the Build Properties” on page 19 for more
details.
4.
Run the db2ant.sh create_ors script.
Change directories to the .../database/db2 directory and type the appropriate
command for your system:
Linux, Solaris, and AIX:
./db2ant.sh create_ors
5.
After the setup scripts are complete, these log files are created in the log directory
•
create_ors.log
ignored. Errors must be addressed.
If you see database errors in the logs, resolve these first with your DBA. Then
re-run the db2ant.sh create_ors script.
6.
Run the db2ant.sh compile script.
7.
•
compile.log
The compile may take a long time.
these first with your DBA
8.
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-Installation Tasks” on page 170.
31
Adding an ORS (Windows)
To set up the Informatica MDM Hub schemas with an additional ORS schema:
1. Create a temporary directory on the DB2 database server or on a client
workstation that has DB2 client installed with DB2 utilities.
Copy all of the files from the Informatica MDM Hub distribution (from <MDM_
to the temporary
directory you just created.
Install_Directory>\server\resources\database\db2)
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.
page 19 for more details.
5.
Run the db2ant.bat create_ors script. Change directories to the
...\database\db2 directory and type the following command:
db2ant.bat create_ors
6.
After the setup scripts are complete, these log files are created in the log directory
•
create_ors.log
Review these files to ensure no errors occurred. You may see warnings, which can
be ignored. Errors must be addressed.
If you see database error in the logs, resolve these first with your DBA and your
RDBMS vendor, and then re-run the db2ant.bat create_ors script.
7.
Run the db2ant.bat compile script.
The compile may take a long time.
8.
•
compile.log
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-Installation Tasks” on page 170.
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-Installation Tasks” on page 170.
33
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.
Chapter Contents
•
About the Hub Server
•
Installing the Hub Server (JBoss/UNIX)
•
Installing the Hub Server (WebSphere/UNIX)
•
Installing the Hub Server (JBoss/Windows)
•
Installing the Hub Server (WebSphere/Windows)
•
Changing Passwords After Installation
35
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 datasource facilities provided by
your J2EE application server. The Hub Server requires:
• one datasource for the Master Database
•
a datasource for each ORS database that is accessed through the server.
Manually Configuring Message Queues for Asynchronous
SIF Requests
The Hub Server installer automatically sets up message queues and connection factory
configuration. If you need to manually configure your message queues or connection
factories for testing or troubleshooting purposes, see Appendix B, “Manually
Configuring Informatica System Message Queues.”
PostInstallSetup
After the Hub Server installer copies the files to the Informatica installation directory,
the Hub Server must be deployed and configured on the application server via the
post-installation process. You can choose to have the installation program perform the
post-installation process for you, or you can end the program before post-installation
begins and do it manually using the postinstallsetup script.
Separating the installation and post-installation (deployment) functions has a few
advantages:
• It enables you to make sure that the application server starts up successfully before
you deploy it.
•
It simplifies troubleshooting.
•
It enables you to deploy the application using the application server’s
administration console.
37
This section describes how to install the Hub Server running in the JBoss application
server environment on the UNIX platform.
Note: JBoss 5 should use JDK 1.6.0.14 or highter..
Hub Server installation involves the following steps:
Step
Task
Instructions
1
Prepare the target environment, including “Preparing for Installation” on page 38
setting up the application server.
2
Install the Hub Server by running the
installer.
“Running the Hub Server Installer” on
page 41
3
Specify or change Hub Server
configuration settings.
“Configuring the Hub Server” on page 46
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 DB2 drivers.
Obtain an Informatica License File
Obtain an Informatica license file. The Hub Server installer will not install the
Informatica MDM Hub without a valid license file. Contact Informatica Global
Customer Support (see “Informatica Global Customer Support” on page xvi) 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)
Note: Your memory requirements will depend on your particular implementation and
data volumes.
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 a DB2 Datasource
To configure JBoss to use a DB2 datasource:
39
•
Copy the following new DB2 JDBC driver files to your
<JBoss_install_dir>/lib directory:
•
db2jcc.jar
•
db2jcc_licence_cu.jar
These files are part of your Informatica MDM DB2 distribution.
•
The user that runs the application server should have rights to execute DB2
commands (like: db2 connect to).
Add these lines to the user's shell properties file:
if [ -f <db2_instance_owner_home>/db2/sqllib/db2profile ]; then
<db2_instance_owner_home>/db2/sqllib/db2profile fi
Disable JMX Invoker Authentication
If JMX Invoker Authentication is enabled for your JBoss server, you must disable it in
order to successfully create a datasource during ORS registration in the Hub Console.
To disable JMX Invoker Authentication:
1. Edit the following file:
<JBoss_install_dir>/server/<configuration_
name>/deploy/jmx-invoker-service.xml
2.
Remove or comment out the following lines:

Configure the JVM Memory Allocation Pool
Configure the JVM memory allocation pool parameters. Start with the following
settings and modify as appropriate for your implementation.
set JAVA_OPTS=%JAVA_OPTS% -Xms256m -Xmx768m -Xss1000k
-XX:PermSize=64m -XX:MaxPermSize=256m
Starting the JBoss Server
In order to successfully launch the Hub Console, you need to complete the following
steps to start the JBoss server:
1. Go to the following directory:
jboss-5.1.0.GA/bin
2.
Run the following command:
run.sh -b 0.0.0.0
Running the Hub Server Installer
The Hub Server Installer is the program used to install the Hub Server software. It is
included in your Informatica MDM Hub distribution.
Installation Considerations
•
Important: You must use the same username to install both Hub Server and
Cleanse Match Server. In addition, if you are installing the server and cleanse
software on the same machine, the users who install them must belong to the same
UNIX group.
•
File names and directories in this section may vary slightly depending on what type
of installation you are performing.
Installation Steps
To run the Hub Server Installer:
1. Make sure that your application server is started and running correctly.
2.
If you are installing from a remote client, start an X windows session and set the
display value to the remote client.
41
3.
4.
Go to the directory where the Hub Server installer resides. In the distribution, the
Hub Server installer is in the following directory:
•
Solaris: /solaris/mrmserver
•
HP-UX: /hpux/mrmserver
•
Linux: /linux/mrmserver
•
AIX: /aix/mrmserver
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 191.
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 Upgrade
Technical Note.
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
xvi) for a license.
If you entered the license path, click Next to continue.
The Application Server screen is displayed.
10.
Select the JBoss application server. Click Next.
Note: You must be sure that you have supported versions of your application
server, or the Hub Server installer will display error messages and you will be
unable to continue with the installation. For the latest application server
compatibility requirements, see the Release Notes.
The JBoss Application Server Home screen is displayed.
11.
Configure your JBoss settings.
a.
Specify the application server installation directory. Click Next.
The JBoss Application Server Configuration Name screen is displayed.
b.
Specify the Configuration Name (default is production). Click Next.
The JBoss Pre-requisites warning is displayed.
c.
Click OK.
The JBoss Application Server 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.
43
Note: The JBoss port can conflict with the default DB2 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 jboss-service.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 DB2. Click Next.
The DB2 Database Connection Type Selection screen is displayed.
14.
Enter the following settings for the DB2 database to which you want to connect:
server name, port number, Database Name, System Schema, DBA Username and
DBA Password. Click Next.
The 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
“PostInstallSetup” on page 37. 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.
17.
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.
18.
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 186). 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 xvi).
Location / Log File
Description
<MDM_Install_Directory>/hub/server/Informatica_MDM_
Hub_Server_InstallLog.xml
Contains log messages for the Hub
Server installation.
<MDM_Install_
Directory>/hub/server/logs/installPrereq.log
Contains the prerequisite messages
generated during installation.
<MDM_Install_Directory>/hub/server/infamdm_installer_
debug.txt
Contains debug messages.
<MDM_Install_
Directory>/hub/server/logs/postInstallSetup.log
Contains the
postInstallSetup messages
for the script.
<MDM_Install_Directory>/hub/server/logs/cmxserver.log
Hub Server log. When the server
started, it created this file.
JBoss log files (such as <JBoss_install_
Located in the tree under the JBoss
install directory.
dir>/server/<configuration_name>/log/server.log)
45
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 <MDM_Install_
Directory>/hub/server/conf/jboss-log4j.xml for logging. The default value is
INFO for jboss-log4j.xml. You can turn on DEBUG for mrmserver by replacing INFO
with DEBUG in jboss-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 <MDM_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=db2
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
name>/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml
in the following attribute: <attribute name="Port">1099</attribute>.
file,
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:
<MDM_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 48.
5.
Restart the application server.
Changing Passwords
After you have installed Hub Server, you can change the password for the CMX_
SYSTEM and CMX_ORS users. For more information, see “Changing Passwords
After Installation” on page 86.
47
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:
/<MDM_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 202.
This section describes how to install the Hub Server running in the WebSphere
application server environment on the UNIX platform.
Step
Task
Instructions
1
2
installer.
page 51
3
49
Obtain 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 xvi) for a license.
+OS native heap size (which varies for 32-bit and 64-bit platforms)
data volumes.
Install and Configure WebSphere
Install and configure WebSphere according to your WebSphere documentation.
Configure WebSphere to Use a DB2 Datasource
To configure WebSphere to use a DB2 datasource:
•
<WebSphere_install_dir>/lib directory:
•
db2jcc.jar
•
Note: Be sure to use the approriate IBM driver for your DB2 version. See the
Informatica MDM Hub Release Notes for more information.
commands (like: db2 connect to).
Add these lines to the user's shell properties file:
•
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.
•
51
Installation Steps
To run the Hub Server Installer:
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:
4.
•
Solaris: /solaris/mrmserver
•
HP-UX: /hpux/mrmserver
•
Linux: /linux/mrmserver
•
AIX: /aix/mrmserver
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”):
The Hub Server Installer displays the Introduction screen.
5.
6.
Select the “I accept the terms of the License Agreement” button and then click
Next.
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.
7.
•
Click Next to install Hub Server in the default location.
•
•
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.
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
xvi) for a license.
If you entered the license path, click Next to continue.
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.
53
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.
Fill in the WebSphere Username field and the WebSphere Password. Click
Next.
•
Fill in the server name, and the RMI, and SOAP ports for your WebSphere
55
12.
The DB2 Database Connection Type Selection screen is displayed.
13.
server name, port number, Database Name, System Schema, DBA Username, and
DBA Password.
Click Next.
14.
Click Next.
The Deploy screen is displayed.
15.
later. For more information about the post-installation process, see
“PostInstallSetup” on page 37. Click Next.
57
16.
appropriate screens.
17.
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.
18.
Click Done to exit the Hub Server installer.
Location / Log File
Description
<MDM_Install_
debug.txt
<MDM_Install_
Contains the
for the script.
WebSphere log files in the following location:
Located in the tree under the
WebSphere install directory.
<WebSphere_install_
dir>/profiles/AppSrv01/logs/<servername>.
Name of log files: startServer.log, stopServer.log, SystemErr.log, and
SystemOut.log.
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
59
deployed the EAR file on the Sales machine, the application on Sales would not be able
to locate the installation for configuration information such as logging.
You can configure the <MDM_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.
You can configure the cmxserver.properties file located in
<MDM_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.
cmx.home=/infamdm/hub/server
cmx.appserver.type=websphere
cmx.appserver.naming.protocol=iiop
files.location=/infamdm/hub/server/logs
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:
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 61.
5.
Changing Passwords
Server installer.
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:
/<MDM_Install_Directory>/hub/server
61
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\!\!
Checking the Version and Build Number
Check one of the following files to find out the Hub Server version and build number:
• manifest.mf JAR entry inside the <MDM_Install_Directory>
/hub/siperian-mrm-hub.ear file
•
Other places to check:
<MDM_Install_Directory>/hub/bin/versionInfo.sh file
<infamdm_install_directory>/hub/conf/versionInfo.xml
This section describes how to install the Hub Server running in the JBoss application
server environment on the Windows platform.
Note: JBoss 5 should use JDK 1.6.0.14 or highter..
Step
Task
Instructions
1
2
installer.
page 67
3
63
Have a Informatica license file. The Hub Server installer will not install Informatica
+ Window’s native heap size
By default, Windows has a 2GB limit to the amount of memory it will allow to be used
by a single process. This 2GB limit is the limit within which the total Informatica
MDM Hub runtime memory footprint must fit.
Make sure that there is enough physical RAM available to satisfy the runtime needs of
all the Informatica software you intend to install. With all your non-Informatica
applications turned on, use the following formula to determine if your physical RAM is
adequate:
min physical RAM available >= Window’s native process memory limit
>=(application server JVM maximum heap size + <cleanse_engine>
memory size)
For more information about RAM and physical memory, consult your Windows
documentation.
Install and configure JBoss according to the instructions in the JBoss documentation.
Configure JBoss to Use a DB2 Data Source
To configure JBoss to use a DB2 data source:
• Copy the following new DB2 JDBC driver files to your
<JBoss_install_dir>\server\<configuration_name>lib
•
db2jcc.jar
•
directory:
65
Disable JMX Invoker Authentication (Windows)
If JMX Invoker Authentication is enabled for your JBoss server, you must disable it in
order to successfully create a datasource during ORS registration in the Hub Console.
To disable JMX Invoker Authentication:
1. Edit the following file:
<jboss_home>\server\<configuration_
name>\deploy\jmx-invoker-service.xml
2.
Remove or comment out the following lines:

jboss-5.1.0.GA\bin
2.
run.bat -b 0.0.0.0
•
•
Installation Steps
To install Hub Server:
1. Ensure 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.
4.
Next.
software, the install will ask you if you want to patch your existing installation. For
details on the upgrade process, see the Informatica MDM Upgrade Technical Note.
67
5.
•
Click Next to install Informatica MDM Hub in C:\infamdm\hub\server.
•
•
Click the Choose button to choose another location to install Informatica
MDM Hub and then click Next.
The Choose Shortcut Folder screen is displayed.
6.
Select a shortcut folder, then click Next to continue.
7.
Click Choose to select a license file. Informatica provides you with a license file. If
you do not have the license file, you cannot continue with the install. Contact
Informatica Global Customer Support (see “Informatica Global Customer
Support” on page xvi) to obtain the license file.
8.
Choose JBoss and then click Next.
9.
a.
b.
c.
Click OK.
d.
<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.
10.
Click Next.
11.
The DB2 Database Information screen is displayed.
12.
server name, port number, Database Name, System Schema, DBA Username. and
DBA Password
13.
Click Next.
The PostInstallSetup script (Deploy) screen is displayed.
14.
later. For more information about the post-installation process, see “Running the
Post-Install Process Manually” on page 73. Click Next.
15.
appropriate screens. Once the summary reflects the options you want, click Install
to start the installation process.
16.
(see “Informatica MDM Hub Log Files (Windows)” on page 189). Copy these log files
to the installation documentation directory that you created in “Create an Installation
69
Location / Log File
Description
<MDM_Install_Directory>\hub\server\Informatica_MDM_
<MDM_Install_
Directory>\hub\server\logs\installPrereq.log
<MDM_Install_Directory>\hub\server\infamdm_installer_
debug.txt
<MDM_Install_
Directory>\hub\server\logs\postInstallSetup.log
Contains the
for the script.
<MDM_Install_Directory>\hub\server\logs\cmxserver.log
JBoss log files
install directory.
Example: <JBoss_install_dir>\server\<configuration_
name>\log\server.log
Hub Server EAR File
During runtime, the Hub Server application must locate the installation it was deployed
from. Therefore, it is not recommended to carry the EAR file to deploy onto another
deployed the EAR on the Sales machine, the application would not be able to locate
the installation for configuration information such as logging.
You can configure the log4j.xml for logging. The default value is INFO. You can turn
on DEBUG for mrmserver by replacing INFO with DEBUG in log4j.xml. After you
update this file, you must restart the Hub Server application. For JBoss, the log4j.xml
file is located instead in the conf directory under the JBoss default server directory
(such as <JBoss_install_dir>\server\<configuration_
name>\conf\jboss-log4j.xml).
Directory>\hub\server\resources directory. After you update this file, you must
Your file should look similar to the following example:
cmx.home=C:\infamdm\hub\server
71
cmx.application.server.type=jboss
cmx.appserver.web.port=8080
cmx.appserver.naming.protocol=jnp
cmx.appserver.soap.connector.port=
files.location=C:\infamdm\hub\server\logs
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_home>/server/default/conf/bindingservice.beans
/META-INF/bindings-jboss-beans.xml file, in the following attribute: <attribute
name="Port">1099</attribute>.
Changing Your JBoss Settings
If you keyed in the incorrect JBoss settings during the installation process, complete
the following:
<MDM_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 73.
5.
Changing Passwords
Server installer.
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:
<MDM_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
“Manually Redeploying Hub Server (JBoss/Windows)” on page 210.
This section describes how to install the Hub Server running in the WebSphere
application server environment on the Windows platform.
73
Step
Task
1
2
installer.
page 77
3
Instructions
Obtain the Informatica License File
Obtain an Informatica license file. The Hub Server installer will not install Informatica
+ 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.
75
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)
data volumes.
For more information about RAM and physical memory, consult your Windows
documentation.
Install and configure WebSphere according to your WebSphere documentation.
Configuring WebSphere to Use a DB2 Datasource
To configure WebSphere to use a DB2 datasource:
• Copy the following new DB2 JDBC driver files to your
<WebSphere_install_dir>\lib directory:
•
db2jcc.jar
•
•
db2_workaround_checker.jar
•
•
Installation Steps
To install Hub Server:
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.
4.
Next.
software, the install will ask you if you want to patch your existing installation.
77
5.
•
Click Next to install Informatica MDM Hub in C:\infamdm\hub\server.
•
•
Click the Choose button to choose another location to install Informatica
MDM Hub and then click Next.
The Choose Shortcut Folder screen is displayed.
6.
Select a shortcut folder, then click Next to continue.
7.
Support” on page xvi) to obtain the license file.
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.
10.
b.
Make sure you have fulfilled the prerequisites and Click OK.
c.
default.
•
displayed.
Set the server name, and the RMI and SOAP ports for your WebSphere
•
Next.
•
Fill in Server Name, RMI port, and SOAP Port. Click Next.
79
11.
server name, port number, Database Name, System Schema, DBA Username, and
DBA Password.
Note: The default password for the CMX user is <yourDB2password>.
12.
Click Next.
The PostInstallSetup script (Deploy) screen is displayed.
13.
later. For more information about the post-installation process, see “Running the
Post-Install Process Manually” on page 85. Click Next.
14.
appropriate screens. Once the summary reflects the options you want, click Install
to start the installation process.
15.
81
Location / Log File
Description
<MDM_Install_Directory>\hub\server\Informatica_MDM_
<MDM_Install_
Directory>\hub\server\logs\installPrereq.log
<MDM_Install_Directory>\hub\server\infamdm_installer_
debug.txt
<MDM_Install_
Directory>\hub\server\logs\postInstallSetup.log
Contains the
for the script.
<MDM_Install_Directory>\hub\server\logs\cmxserver.log
WebSphere log files. For example: <WebSphere_install_
dir>\profiles\AppSrv01\logs\<ServerName> folder
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
deployed the EAR on the Sales machine, the application would not be able to locate
the installation for configuration information such as logging.
You can configure the C:\infamdm\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.
Directory>\hub\server\resources directory. After you update this file, you must
cmx.home=C:\infamdm\hub\server
cmx.application.server.type=websphere
83
cmx.appserver.naming.protocol=iiop
cmx.appserver.soap.connector.port=8880
files.location=C:\infamdm\hub\server\logs
Changing Your WebSphere Settings
If you keyed in the incorrect WebSphere settings during the installation process,
complete the following:
<MDM_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 85.
5.
Changing Passwords
Server installer.
If you chose to have the Informatica MDM Hub installation program skip the
post-install process, you must run this script manually.
<MDM_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=<yourDB2password>
Check one of the following files to find out the Hub Server version and build number:
\hub\siperian-mrm-hub.ear file
•
<MDM_Install_Directory>\hub\bin\versionInfo.bat file
<infamdm_install_directory>\hub\conf\versionInfo.xml
“Manually Redeploying Hub Server (WebSphere/Windows)” on page 216.
85
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
SYSTEM user. If you do so, you must also:
• Change the password for the CMX user in DB2.
•
Set the same password in the datasource 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 DB2.
•
Set the same password in the datasource 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 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.
Chapter Contents
•
About the Cleanse Match Server
•
Installing the Cleanse Match Server (JBoss/UNIX)
•
Installing the Cleanse Match Server (WebSphere/UNIX)
•
Installing the Cleanse Match Server (JBoss/Windows)
•
Installing the Cleanse Match Server (WebSphere/Windows)
87
The Cleanse Match Server run-time component handles cleanse and match requests
and is deployed in the application server environment. The Cleanse Match Server
contains:
• a cleanse server that handles data cleansing operations
•
a match server that handles match operations
The Cleanse Match Server interfaces with any of the supported cleanse engines, as
described in Informatica MDM Hub Cleanse Adapter Guide. The Cleanse Match Server and
the cleanse engine work together to standardize the data and to optimize the data for
match and consolidation.
Supported Cleanse Match Engines
Informatica assumes that you are familiar with your cleanse engine and have already
installed and configured it prior to installing Informatica MDM Hub. See the Informatica
MDM Hub Release Notes for the cleanse engines and their versions that are supported by
Informatica MDM Hub.
PostInstallSetup
The Cleanse Match Server installer, by default, runs the post-installation process
(postInstallSetup script) to deploy the application on your application server and
perform some application server configuration. However, while running the install, you
can choose to not run this post-installation process, in which case the Cleanse Match
Server installer only copies the files to the installation directory. Once copied, you must
manually deploy the Cleanse Match Server application on the application server and
perform application server configuration.
Separating the installation and deployment functions allows you to:
• Avoid deploying the application as part of the installation process. You can
manually run the script later when you are sure the application starts up
successfully.
•
Deploy the application using the application server’s administrative console.
•
Run the script to redeploy the application instead of reinstalling the entire Cleanse
Match Server.
•
Troubleshoot deployment problems outside of the installation process.
This section describes how to install the Cleanse Match Server running in the JBoss
application server environment on the UNIX platform.
Cleanse Match Server installation involves the following steps:
Step
Task
Instructions
1
89
Step
Task
Instructions
2
Install the Cleanse Match Server by
running the installer.
“Running the Cleanse Match Server
Installer” on page 94
3
Specify or change Cleanse Match Server
“Configuring the Cleanse Match Server”
on page 100
Complete the tasks in this section before you install the Cleanse Match Server.
Before you install the Cleanse Match Server, fulfill the hardware and software
requirements for the Cleanse Match Server as described in the Informatica MDM Hub
Release Notes.
On the machine where you will run the Cleanse Match Server, install and configure
your JBoss environment according to your JBoss documentation.
Configure JBoss to Use an DB2 Data Source
To configure JBoss to use an DB2 datasource:
1. Copy the following new DB2 JDBC driver files to your
<JBoss_Installation_Directory>/server/<configuration_name>/lib
directory:
•
db2jcc.jar
•
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. 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 xvi) 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.
91
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.
Creating Datasources 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 datasources for
each ORS. You must also do some DB2 configuration, as well as some JBoss
configuration.
Using a DB2 Datasource with JBoss
To configure JBoss to use an DB2 datasource, add these DB2 JDBC Driver JAR files
to the following directory:
<JBoss_install_dir>/server/<configuration_name>/lib
•
db2jcc.jar
•
Configuring JBoss to Use an DB2 Data Source
Note: If you are running DB2 on the same host that is running Cleanse Match Server,
you can skip this section.
1. Copy a sample datasource file (name-ds.xml) into your JBoss deploy directory.
By default the JBoss deploy directory is:
<JBoss_install_dir>/server/<configuration_name>/deploy
You can find the samples in:
<JBoss_install_dir>/docs/examples/jca
You can change the name of the sample datasource file, but the file must end with
-ds.xml to be recognized as a datasource descriptor.
2.
Edit the datasource definition to match your database connection parameters. Edit
the following parameters:
Parameter
Description
jndi-name
Set jndi-name to the following value for a Hub Server datasource:
jdbc/siperian-cmx_system-ds
Set jndi-name to the following value for the cleanse server
datasource:
jdbc/siperian-<db2_hostname>-<database_name>-ds
connection-url The JDBC driver connection URL string for your driver. Make
sure that the database name, host, and port are correct for the
database to which you are connecting. For example:
jdbc:db2://<server_name>:5000/<database_name>
username
Username used when creating a new connection.
password
DB2 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.
93
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 DB2 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_home>/server/default/conf/bindingservice.beans
/META-INF/bindings-jboss-beans.xml
The default connector port is 8080. Change this to any unused port that does not
conflict with other applications.
jboss-5.1.0GA/bin
2.
run.sh -b 0.0.0.0
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.
•
Important: If you are installing the Hub Server, the application server, the Cleanse
Server, and the cleanse engine on the same machine, the user names you use to
install them must belong to the same UNIX group.
•
Important: You can install Hub Server and Cleanse Match Server using any
username you want, but you must use the same user name to install both servers.
•
•
Do not use the root user when installing the Cleanse Match Server on RedHat
Linux. Instead, create and use a separate user profile for installing Informatica
MDM Hub. This is a limitation of InstallAnywhere, as the root user does not have
a .profile.
•
commands (like: db2 connect to). Add these lines to the user's shell properties
file:
•
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 Upgrade Technical Note to learn more. This section covers new
installations.
Installation Steps
To install Cleanse Match Server:
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/
95
4.
Execute the following command to begin the installation process.
./hub_cleanse_install.bin
The Cleanse Match Server Installer displays the Introduction screen.
5.
Click Next.
6.
Accept the terms of the license agreement and click Next.
7.
Click the Choose button to choose another location to install Cleanse Match
Server, or click Next to accept the default.
Important: Do not use a path that has spaces in the directory or folder name.
8.
Click Choose to select a license file. You cannot continue with the installation if
you do not have a license file. Contact Informatica Global Customer Support (see
“Informatica Global Customer Support” on page xvi) to obtain a license file. Click
Next to continue.
9.
Choose the JBoss application server and click Next.
10.
Configure JBoss settings:
a.
b.
c.
<JBoss_install_home>/server/<configuration_name>
/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml
97
search for the word port, and set the port value to match the value you have
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.
•
12.
Choose the AddressDoctor database path. Click Next.
Choose to run the script during the installation, or later (see “Running
PostInstallSetup” on page 107). Click Next.
The Pre-Installation Summary screen is displayed. If you want to change any
options, click the Previous button to navigate to the appropriate screens. Once the
summary screen reflects the options you want, click Install to start the installation
process.
The Please Wait screen is displayed while Informatica configures your system.
When the installation process completes, the Install Complete screen is displayed.
13.
Click Done to exit the Cleanse Match Server installer.
The following log files are useful for troubleshooting any Cleanse Match Server
installation process. Copy these log files to the installation documentation directory
that you created in “Create an Installation Documentation Directory” on page 9. In
case of installation problems, these files will be useful to provide to Informatica Global
Customer Support (see “Informatica Global Customer Support” on page xvi).
File
Description
<MDM_Install_Directory>/hub/cleanse/Informatica_
Hub_Cleanse_Match_Server_InstallLog.xml
Shows the Cleanse Match Server install
errors and status.
<MDM_Install_
Directory>/hub/cleanse/logs/postInstallSetup.log
Shows the postInstallSetup script results.
<MDM_Install_
Directory>/hub/cleanse/logs/cmxserver.log
Cleanse server logs.
<MDM_Install_Directory>/hub/cleanse/infamdm_
installer_debug.txt
Shows what was chosen during the
installation.
<MDM_Install_
Directory>/hub/cleanse/logs/installPrereq.log
dir>/hub/cleanse/<configuration_
name>/log/server.log)
Located in the tree under the install
directory for your application server.
99
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.
Check one of the following files to find out the Cleanse Match Server version and build
number:
/hub/cleanse/siperian-mrm-cleanse.ear file
•
<MDM_Install_Directory>/hub/cleanse/bin/versionInfo.sh file
<infamdm_install_directory>/hub/cleanse/conf/versionInfo.xml
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:
<MDM_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 <MDM_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 jboss-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: <MDM_Install_Directory>/resources).
Installing the Cleanse Match Server 101
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
files.location=/u1/infamdm/hub/cleanse/tmp
cmx.server.datalayer.cleanse.execution=LOCAL
cmx.home=/u1/infamdm/hub/cleanse
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:
<MDM_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
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-bit 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 104.
•
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 106.
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 94 and “Configuring the
Cleanse Match Server” on page 100.
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 104.
3.
Deploy Cleanse Match Server to the second instance of your application server.
For more information, see “Deploying Cleanse Match Server on a Second
Application Server Instance” on page 105.
Configuring Multiple Instances of your Application Server
To configure your application server:
Ensure that the machine you are configuring has sufficient memory to host
multiple instances of the application server.
1.
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 105.
Deploying Cleanse Match Server on a Second Application Server
Instance
There are two alternatives for deploying Cleanse Match Server on the second instance
of your application server:
• You can install an additional copy of Cleanse Match Server into a different
directory using the Cleanse Match Server installer.
Installing an additional copy using the Cleanse Match Server installer gives you full
independence of the two Cleanse Match Server instances. There are no extra steps
required to support this configuration. You can run the postInstallSetup script
to deploy Cleanse Match Server to your second instance.
•
You can deploy your existing Cleanse Match Server EAR into the new application
server instance.
The second approach is lighter and allows multiple instances to share the
Informatica MDM Hub configuration settings. The disadvantage is that both
servers share the temporary directories and write to the same log file. This
complicates diagnostics when both instances run Cleanse Match Server at the same
time.
Using this approach, you cannot use the postInstallSetup script to deploy the
additional cleanse instance, you must deploy it manually on the application server.
Deploying the EAR File Manually
To deploy the EAR file manually copy the ear file in the following location:
<JBoss_install_dir>/server/<configuration_name>/deploy
Configuring Multiple Cleanse Match Servers on Multiple
Machines
Informatica MDM Hub supports running multiple Cleanse Match Server servers per
ORS database. This allows you to parallelize the work of cleansing the data.
When Cleanse Match Server is not installed on the same application server as Hub
Server, then you must manually configure the application server to create the
datasources for Cleanse Match Server to take advantage of connection pooling and
improved performance. For more information, see your application server
documentation.
Note: If the datasource 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 datasources 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 88.
The postInstallSetup script is stored in <MDM_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.
(WebSphere/UNIX)
This section describes how to install the Cleanse Match Server running in the
WebSphere application server environment on the UNIX platform.
Step
Task
Instructions
1
2
3
on page 120
Release Notes.
your WebSphere environment according to your WebSphere documentation.
Guide.
a license file.
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 datasources for
each ORS.
Configure WebSphere to Use an DB2 Datasource
To configure WebSphere to use an DB2 datasource, add these DB2 JDBC Driver JAR
files to the following directory:
<WebSphere_install_dir>/lib
•
db2jcc.jar
•
Creating Master Datasources in 6.1.0.29
To create your WebSphere 6.1.0.29 master datasources:
1. Start the application server and launch the WebSphere Application Server
Administrative 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 DB2_UNIVERSAL_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
Datasource:
a.
Expand Security in the console navigation tree.
Click Secure administration, applications, and infrastructure link.
b.
Expand Java Authentication and Authorization Service Configuration
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 = <yourDB2password>
To learn about changing this password, see “Changing the Password for
the CMX_SYSTEM User” on page 112.
e.
5.
Click OK to save.
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 DB2 from database type list.
Select DB2 JDBC UNIVERSAL DRIVER from provider type list.
Select XA data source from implementation type list.
c.
Change the name to “Informatica MDM DB2 JDBC UNIVERSAL
Provider (XA)”.
111
Click Next and Finish to save.
6.
Create the Informatica MDM Master datasource:
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 datasource.
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 Finish.
Note: The JNDI name must be in lower case.
After you have installed Informatica MDM Hub, you can change the password for
CMX_SYSTEM. If you do so, you must also:
• Set the same password in the datasource on the application server
Creating ORS Datasources in WebSphere 6.0.1.29
To create your WebSphere 6.0.1.29 ORS datasources:
Start the application server and launch the WebSphere Application Server
1.
2.
3.
a.
b.
c.
Update the DB2_JDBC_UNIVERSAL_DRIVER_PATH variable to point to
the JDBC driver location. (for example, /u1/was6103/AppServer/Lib).
4.
Create the security account to be used by the Informatica MDM ORS datasource:
a.
Click Secure administration, applications, and infrastructure link in
WebSphere 6.1.0.29.
b.
Expand Java Authentication and Authorization Service under
Authentication in right side of the console window.
c.
Set the following:
Alias = cmx_ors
User ID = cmx_ors
Password =
<yourDB2password>
To learn about changing this username and password, see “Changing the
Username and Password for the CMX_ORS User” on page 114.
d.
5.
Click OK to save.
a.
menu.
Click JDBC Providers link.
adjustment).
b.
Select DB2 JDBC Driver from provider type list.
Provider (XA)”.
113
6.
Create the Informatica MDM ORS datasource:
a.
b.
console window).
c.
Name = Informatica MDM ORS Data Source
JNDI Name = jdbc/siperian-<db2_hostname>-<database_
name>-cmx_ors-ds
Component-managed Authentication Alias = <hostname>/cmx_
ors
d.
Note: The JNDI name must be in lower case.The JNDI name in the JDBC
data source setup WebSphere uses the '-' character in its notation. If the
physical server used in the connection also contains the '-' character, the '~'
character must prefix the “-” in the server name.
For example:
Name: siperian-my~-host-sip901-cmx_ors-ds
JNDI name: jdbc/siperian-my~-host-sip901-cmx_ors-ds
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:
•
Set the same password in the datasource on the application server.
•
Register the schema with the same username and password.
•
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.
•
•
•
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.
•
installations. If you have a previously installed version of Informatica software, see
the Informatica MDM Upgrade Technical Note to learn more. This section covers new
installations.
Installation Steps
2.
If you are installing from a remote client, start an X Windows session and set the
DISPLAY value to the remote client.
115
3.
Run the Informatica Cleanse Match Installer. The Cleanse Match Server installer is
on the distribution in the following directory:
Solaris:
/solaris/mrmcleanse/
HP-UX:
/hpux/mrmcleanse/
Linux:
/linux/mrmcleanse/
AIX:
/aix/mrmcleanse/
4.
Execute the following command to begin the installation process.
./hub_cleanse_install.bin
The Cleanse Match Server Installer displays the Introduction screen.
5.
Click Next.
6.
Accept the terms of the license agreement and click Next.
7.
Server, or click Next to accept the default.
Important: Do not use a path that has spaces in the directory or folder name.
8.
Click Choose to select a license file. You cannot continue with the installation if
you do not have a license file. Contact Informatica Global Customer Support (see
“Informatica Global Customer Support” on page xvi) to obtain a license file. Click
Next to continue.
9.
Choose the WebSphere application server and click Next.
10.
Configure WebSphere settings:
Choose a path to the WebSphere application server and click Next.
11.
default.
•
displayed.
Set the Server Name and SOAP port for your WebSphere application server.
Click Next.
•
Next.
12.
Set the Server Name and SOAP port for your WebSphere application server. Click
Next.
13.
Adapter Guide.
•
•
parameters. For backslashes(\) in any of these parameters, use a double
14.
•
Specify the AddressDoctor preload parameters. Click Next. The Choose
AddressDoctor Database Path screen is displayed.
•
Choose to run the script during the installation, or later (see “Running
PostInstallSetup” on page 127). Click Next.
117
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.
When the installation process completes, the Install Complete screen is displayed.
15.
Click Done to exit the Cleanse Match Server installer.
File
Description
<MDM_Install_Directory>/hub/cleanse/Infamdm_Hub_
Cleanse_Match_Server_InstallLog.xml
errors and status.
<MDM_Install_
<MDM_Install_
installer_debug.txt
installation.
<MDM_Install_
<WebSphere_install_
SystemOut.log.
119
•
information (such as logging).
•
Engines
To find out how to configure the various cleanse engines, see the Informatica MDM Hub
Cleanse Adapter Guide.
number:
/hub/cleanse/siperian-mrm-cleanse.ear file
•
<MDM_Install_Directory>/hub/cleanse/bin/versionInfo.sh file
<infamdm_install_directory>/hub/cleanse/conf/versionInfo.xml
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:
<MDM_Install_Directory>/hub/cleanse/resources/
You can change the value to FALSE to delete these files after the cleanse/strip and
tokenization processes are completed.
log4j.xml file, located in the <MDM_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.
as: <MDM_Install_Directory>/resources).
cmx.server.logging.location=/u1/infamdm/hub/cleanse/logs
files.location=/u1/infamdm/hub/cleanse/tmp
cmx.home=/u1/infamdm/hub/cleanse
cmx.appserver.type=websphere
<MDM_Install_Directory>/hub/cleanse/resources
2.
cmx_server.cleanse.num_of_thread=1
3.
•
•
•
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.
2.
more information, see “Configuring Multiple Instances of your Application
3.
For more information, see “Deploying Cleanse Match Server on a Second
Configuring Multiple Instances of your Application Server
1. Ensure that the machine you are configuring has sufficient memory to host
2.
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
wsinstance script and adjust the settings. In either case, change the defalcators port
settings using the WAS Administrative Console so the values for the separate
instances don’t conflict. If you are using the wsinstance script, install the
administrative console on the new instance manually and change admin_host port
assignment. For more information, see your WebSphere documentation.
3.
Now you can deploy Cleanse Match Server. For more information, see “Deploying
Cleanse Match Server on a Second Application Server Instance” on page 125.
Deploying Cleanse Match Server on a Second Application Server
Instance
required to support this configuration. You can run the postInstallSetup script
to deploy Cleanse Match Server to your second instance.
•
server instance.
time.
additional cleanse instance, you must deploy it manually on the application server.
To deploy the EAR file manually, use the Informatica MDM Administrative Console
for deployment. Accept all defaults.
Configuring Multiple Cleanse Match Servers on Multiple
Machines
ORS database. This allows you to parallelize the work of cleansing the data.
improved performance. For more information, see your application server
documentation.
Note: If the datasource 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 datasources 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.
4.
5.
Add the new Cleanse Match Server.
You can see all the cleanse servers in the Cleanse Match Server workbench.
This section describes tasks that you might need to perform after running the Cleanse
Match Server installer.
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 88.
The postInstallSetup script is stored in <MDM_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
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.
(JBoss/Windows)
This section describes how to install the Cleanse Match Server running in the JBoss
application server environment on the Windows platform.
Step
Task
1
2
Instructions
Step
Task
Instructions
3
on page 138
Release Notes.
your JBoss environment according to your JBoss documentation.
Configure JBoss to Use a DB2 Datasource
1. Edit the jboss-service.xml file, making sure the XidFactory padding is set to
true. This file is in <JBoss_install_dir>\server\<configuration_
name>\conf. Here is the fragment of the XML to set that value:
<mbean code="org.jboss.tm.XidFactory"
name="jboss:service=XidFactory">
<attribute name="Pad">true</attribute>
</mbean>
This information is already in the file, but commented out:

Simply remove the “!--” and “--” to un-comment the statement to match the
example above.
2.
<JBoss_install_dir>\server\<configuration_name>\lib directory:
•
db2jcc.jar
•
Guide.
Customer Support (see “Informatica Global Customer Support” on page xvi) for a
license file.
Configure JBoss for Cleanse Match Server
This section describes how to configure JBoss before installing the Cleanse Match
Server.
Creating Datasources for Each ORS
Server, on the Cleanse Match Server machine, you must create datasources for each
ORS. You must do some DB2 configuration as well as some JBoss configuration.
Setting the Location of the JDBC Driver
To configure JBoss to use a DB2 datasource, copy the following DB2 files to your
JBoss\server\<configuration_name>\lib directory:
•
db2jcc.jar
•
Configuring JBoss to Use a DB2 Datasource
1. Copy a sample datasource file (name-ds.xml) into your JBoss deploy directory.
By default, the JBoss deploy directory is:<JBoss_install_
dir>\server\<configuration_name>\deploy
You can find the samples in:<JBoss_install_dir>\docs\examples\jca
You can change the name of the sample datasource file, but the file must end with
-ds.xml to be recognized as a datasource descriptor.
2.
Edit the datasource definition to match your database connection parameters. Edit
the following parameters:
Parameter
Description
jndi-name
Set the following value for a Hub Server datasource:
jdbc/siperian-cmx_system-ds
Set the following value for the cleanse server datasource:
jdbc/siperian-<hostname>-<database_name>-ds
connection-u JDBC driver connection URL string for your driver. Make sure that
rl
the database name, host, and port are correct for the database to
which you are connecting. Example:
jdbc:db2://<server_name>:5000/<database_name>
username
Username used when creating a new connection.
password
DB2 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 both Hub Server and Cleanse Match Server:
1. Set the Isolated attribute of the JBoss’s EAR deployer to true in the
name>\deploy\ear-deployer.xml. This configures
all your EARs to be in
isolated class loader spaces using call by value for remote interfaces.
For example:
<mbean code="org.jboss.deployment.EARDeployer"
name="jboss.j2ee:service=EARDeployer">

<attribute name="Isolated">true</attribute>
</mbean>
2.
Set the UseJBossWebLoader setting to false in the following file:
name>\deploy\jboss-web.deployer\META-INF\jboss-service.xml
This disables JBoss from using a unified class loader as the web application class
loader. For example:
<attribute name="UseJBossWebLoader">false</attribute>
3.
When there is the potential for conflict between the JBoss port and the DB2 port,
change the port used by one of the applications. To change the port for the JBoss
application server, edit the following file:
name>\deploy\jboss-web.deployer\server.xml
The default connector port is 8080. Change this setting to any unused port that
does not conflict with other applications.
jboss-5.1.0.GA\bin
2.
run.bat -b 0.0.0.0
•
•
•
installations. If you have a previously-installed version of Informatica MDM Hub
software, see the Informatica MDM Upgrade Technical Note to learn more. This section
covers new installations.
Installation Steps
2.
Run the Informatica Cleanse Match Server installer (hub_cleanse_install.exe).
The Cleanse Match Server installer is on the distribution in the
\windows\mrmcleanse directory.
The Cleanse Match Server installer displays the Introduction screen.
3.
Click Next.
4.
Click the I accept the terms of the License Agreement button and then click
Next.
5.
•
Click Next to install Cleanse Match Server in C:\infamdm\hub\cleanse.
•
Server and then click Next.
Note: Cleanse Match Server will fail to load if the total length of this path exceeds
256 characters.
The Choose Shortcut Folder is displayed.
6.
Select a location for the product icons. Click Next.
7.
Support” on page xvi) to obtain a license file.
8.
9.
Choose the JBoss application server and click Next.
The JBoss Application Server Home screen is displayed
10.
Configure JBoss settings:
a.
b.
c.
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\jboss-service.xml
search for the word port, and set the port value to match the value you have
d.
11.
Click Next.
Adapter Guide.
•
•
•
•
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 140 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.
When the installation completes, the Install Complete screen is displayed. This
screen shows messages relevant to your specific installation, such as upgrading
shared libraries.
14.
Choose Yes to restart your system, or choose No to restart it later and click Done
to exit the Cleanse Match Server installer.
File
Description
<MDM_Install_Directory>\hub\cleanse\Infamdm_Hub_
Cleanse_Match_Server_InstallLog.xml
errors and status.
<MDM_Install_
Directory>\hub\cleanse\logs\postInstallSetup.log
<MDM_Install_
Directory>\hub\cleanse\logs\cmxserver.log
<MDM_Install_Directory>\hub\cleanse\infamdm_
installer_debug.txt
installation.
<MDM_Install_
Directory>\hub\cleanse\logs\installPrereq.log
dir>\hub\cleanse\<configuration_
name>\log\server.log).
•
information such as logging.
•
Engines
For more information regarding cleanse engine configuration, see the Informatica MDM
Hub Cleanse Adapter Guide.
number:
• manifest.mf JAR entry inside the <MDM_Install_
Directory>\hub\cleanse\siperian-mrm-cleanse.ear file
•
<MDM_Install_Directory>\hub\cleanse\bin\versionInfo.bat file
<infamdm_install_directory>\hub\cleanse\conf\versionInfo.xml
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:
<MDM_Install_Directory>\hub\cleanse\resources\
You can change the value to FALSE to delete the file after cleanse/strip is completed.
log4j.xml file, located in the <MDM_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.
as: C:\infamdm\hub\cleanse\resources).
files.location=C:\infamdm\hub\cleanse\tmp
cmx.home=C:\infamdm\hub\cleanse
This section describes tasks to complete after you have installed the software.
If you chose to have the Cleanse Match Server installer skip the post-install process,
you must run this manually.
<MDM_Install_Directory>\hub\cleanse
prompt:
postInstallSetup.bat
<MDM_Install_Directory>\hub\cleanse\resources
2.
Cmx_server.cleanse.num_of_thread=1
3.
•
•
•
2.
Configure your system to run multiple instances of your application server
according to the instructions in “Configuring Multiple Instances of Your
Application Server” on page 142.
3.
For more information, see “Deploying Cleanse Match Server on the Second
Configuring Multiple Instances of Your Application Server
Ensure that the machine you are configuring has sufficient memory to host
1.
2.
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.
Now you can deploy Cleanse Match Server, as described in the next section.
Deploying Cleanse Match Server on the Second Application
Server Instance
required to support this configuration. You can run the postInstallSetup script to
deploy Cleanse Match Server to your second instance.
•
server instance.
time.
additional cleanse instance, but you can deploy them manually on the application
server.
To deploy the EAR file manually, copy the file to the following directory:
<JBoss_install_dir>\server\<configuration_name>\deploy
Using Multiple Cleanse Servers
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.
improved performance.
Note: If the datasource does not exist, the Cleanse Match Server uses the JDBC
connection.
To configure multiple cleanse servers
After you have installed and configured the Hub Server and Cleanse Match Server,
install your cleanse engine and Cleanse Match Server on another machine.
1.
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.
4.
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
Parameter
Description
Thread Count
Reflects the number of threads that a server will be asked to handle. We
recommend that you set the thread count higher than the number of CPUs
available if the servers are widely distributed and/or latency is high, so that
servers can be doing more work during wait time.
CPU Rating
Rates the relative “strength” of the CPUs across the machines; the “lowest
power” machine would have a rating of 1.0. Other CPUs on different
machines would have a number relative number to the lowest powered
machine.
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.
(WebSphere/Windows)
This section describes how to install the Cleanse Match Server running in the
WebSphere application server environment on the Windows platform.
Step
Task
Instructions
1
Step
Task
Instructions
2
3
on page 156
Release Notes.
your WebSphere environment according to your WebSphere documentation.
Guide.
Obtain the Informatica License File
a license file.
Configure WebSphere for Cleanse Match Server
This section describes how to configure WebSphere for the Cleanse Match Server.
Configuring WebSphere to Use a DB2 Datasource
Server, on the Cleanse Match Server machine, you must create datasources for each
ORS.
To configure WebSphere to use a DB2 datasource, add these DB2 JDBC Driver JAR
files to the <WebSphere_install_dir>\AppServer\lib directory.
•
db2jcc.jar
•
Creating Master Datasources in WebSphere
To create your WebSphere master datasources:
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 Administrative Console. Choose Start >
Programs > IBM WebSphere > Application Server v6 > Profiles >
<configuration_name> > Administrative Console.
3.
4.
5.
a.
b.
c.
the JDBC driver location. (such as <WebSphere_install_
dir>\AppServer\lib).
Create the security account to be used by the Informatica MDM Master
datasource:
a.
Click the Secure administration, application and infrastructure link.
b.
Authentication in the right side of the console window.
c.
d.
Set the following:
•
Alias = CMX_SYSTEM
•
Do not change this username.
•
To learn about changing this password, see “Changing the Password for
the CMX_SYSTEM User” on page 150.
e.
6.
Click OK to save.
a.
b.
c.
Expand Resources in the console navigation tree and expand the JDBC
menu.
•
Click the JDBC Providers link.
•
adjustment).
•
•
Select DB2 JDBC UNIVERSAL Driver from provider type list.
•
Provider (XA)”.
•
7.
Create the Informatica MDM Master datasource:
a.
b.
console window).
c.
d.
e.
•
Name = Informatica MDM Master Data Source
•
•
system
CMX_SYSTEM. If you do so, you must also:
• Change the password for the CMX user in DB2
•
Set the same password in the datasource on the application server
Creating ORS Datasources in WebSphere 6.1.0.29
To create your WebSphere 6.1.0.29 ORS datasources:
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 Administrative Console. Choose Start >
Programs > IBM WebSphere > Application Server v6 > Profiles >
<configuration_name> > Administrative Console.
3.
4.
5.
a.
b.
c.
the JDBC driver location. (for example, <WebSphere_install_
dir>/AppServer/lib).
Create the security account to be used by the Informatica MDM ORS datasource:
a.
Click the Secure administration, application and infrastructure link.
b.
Authentication in the right side of the console window.
c.
Set the following:
•
Alias = cmx_ors
•
User ID = cmx_ors
•
To learn about changing this username and password, see “Changing the
Username and Password for the CMX_ORS User” on page 152.
d.
6.
Click OK to save.
a.
menu.
Click JDBC Providers link.
adjustment).
b.
c.
•
•
Select DB2 JDBC Driver from provider type list.
•
Provider (XA)”.
7.
Create the Informatica MDM ORS datasource:
a.
b.
console window).
c.
•
Name = Informatica MDM ORS Data Source
•
JNDI Name = jdbc/siperian-<db2_hostname>-<database_
name>-cmx_ors-ds
•
d.
ors
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:
•
Set the same password in the datasource on the application server.
•
Register the schema with the same username and password.
•
•
•
installations. This section covers new installations.
Installation Steps
2.
Run the Informatica Cleanse Match Server installer (hub_cleanse_install.exe).
The Cleanse Match Server installer is on the distribution in the
\Windows\mrmcleanse directory.
The Cleanse Match Server installer displays the Introduction screen.
3.
Click Next.
4.
Click the I accept the terms of the License Agreement button and then click
Next.
5.
•
Click Next to install Cleanse Match Server in C:\infamdm\hub\cleanse.
•
Server and then click Next.
Note: Cleanse Match Server will fail to load if the total length of this path exceeds
256 characters.
The Choose Shortcut Folder is displayed.
6.
Select a location for the product icons. Click Next.
7.
Support” on page xvi) to obtain a license file.
8.
9.
Choose the WebSphere application server and click Next.
Enter a path to the WebSphere application server and click Next.
10.
default.
•
displayed.
•
Next.
11.
Set the Server Name and SOAP port for your WebSphere application server. Click
Next.
12.
Adapter Guide.
•
•
•
•
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 159 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.
15.
Choose Yes to restart your system, or choose No to restart it later and click Done
to exit the Cleanse Match Server installer.
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 xvi).
File
Description
<MDM_Install_Directory>\hub\cleanse\Informatica_
errors and status.
<MDM_Install_
Directory>\hub\cleanse\logs\postInstallSetup.log
<MDM_Install_
Directory>\hub\cleanse\logs\cmxserver.log
<MDM_Install_Directory>\hub\cleanse\infamdm_
installer_debug.txt
installation.
<MDM_Install_
Directory>\hub\cleanse\logs\installPrereq.log
<WebSphere_install_
dir>\profiles\AppSrv01\logs\<servername>
SystemOut.log.
•
information such as logging.
•
Engines
For more information regarding cleanse engine configuration, see the Informatica MDM
Hub Cleanse Adapter Guide.
number:
• manifest.mf JAR entry inside the <MDM_Install_
Directory>\hub\cleanse\siperian-mrm-cleanse.ear file
•
<MDM_Install_Directory>\hub\cleanse\bin\versionInfo.bat file
<infamdm_install_directory>\hub\cleanse\conf\versionInfo.xml
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:
<MDM_Install_Directory>\hub\cleanse\resources\
You can change the value to FALSE to delete the file after cleanse/strip is completed.
log4j.xml file, located in the <MDM_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.
as: C:\infamdm\hub\cleanse\resources).
files.location=C:\infamdm\hub\cleanse\tmp
cmx.home=C:\infamdm\hub\cleanse
This section describes tasks to complete after you have installed the software.
If you chose to have the Cleanse Match Server installer skip the post-install process,
you must run this manually.
<MDM_Install_Directory>\hub\cleanse
prompt:
postInstallSetup.bat -Ddatabase.password=<yourDB2password>
<MDM_Install_Directory>\hub\cleanse\resources
2.
Cmx_server.cleanse.num_of_thread=1
3.
•
•
•
2.
more information, see “Configuring Multiple Instances of Your Application
3.
For more information, see “Deploying Cleanse Match Server on the Second
Configuring Multiple Instances of Your Application Server
1. Ensure that the machine you are configuring has sufficient memory to host
2.
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 Administrative Console so the values for the separate
instances don’t conflict. If you are using the wsinstance script, install the
Administrative Console on the new instance manually and change admin_host port
assignment. For more information, see your WebSphere documentation.
3.
Now you can deploy Cleanse Match Server, as described in the next section.
Deploying Cleanse Match Server on the Second Application
Server Instance
required to support this configuration. You can run the postInstallSetup script to
deploy Cleanse Match Server to your second instance.
•
server instance.
time.
additional cleanse instance, but you can deploy them manually on the application
server.
To deploy the EAR file manually, use the Informatica MDM Administrative Console
for deployment. Accept all defaults.
Using Multiple Cleanse Servers
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.
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.
4.
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
Parameter
Description
Thread Count
Reflects the number of threads that a server will be asked to handle. We
recommend that you set the thread count higher than the number of CPUs
available if the servers are widely distributed and/or latency is high, so that
servers can be doing more work during wait time.
CPU Rating
Rates the relative “strength” of the CPUs across the machines; the “lowest
power” machine would have a rating of 1.0. Other CPUs on different
machines would have a number relative number to the lowest powered
machine.
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.
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-Installation Tasks
165
Administrators and data stewards can access Informatica MDM Hub features via the
Informatica MDM Hub user interface, which is called the Hub Console. The Hub
Console comprises a set of tools. Each tool allows you to perform a specific action, or
a set of related actions. The available tools in the Hub Console depend on your
Informatica license agreement.
You do not need to install the Hub Console because the Hub Console is launched
from the Hub Server installation using Java Web Start. Or go to:
http://<hostname>:<port>/cmx/siperian-console.jnlp
Make sure that Java Web Start has been installed. The following URL is a page that has
a link to the Web Start installer:
http://<hostname>:<port>/cmx/
In these URLs, hostname is the host running your application server and port is the
port on which that application server is listening.
To launch the Hub Console:
1. Open a browser window and enter the following URL:
http://YourHubHost:<port>/cmx/
where YourHubHost is your local Informatica MDM Hub host and port is the
port number. Check with your administrator for the correct port number.
Note: You must use an HTTP connection to start the Hub Console. SSL
connections are not supported.
The Hub Console launch screen is displayed.
2.
Click the Launch button.
The first time (only) that you launch Hub Console from a client machine, Java Web
Start downloads application files.
167
The Hub Console login screen is displayed.
3.
Enter a user name and password.
Note: If you do not have a user name and password set up, contact Informatica
xvi).
4.
Click OK.
After you have logged in with a valid user name and password, Informatica MDM
Hub will prompt you to choose a target database.
The first time you start the Hub Console, you will be prompted to select the
Master Database. After you have registered one or more Operational Record
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.
•
5.
An Operational Record 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). A Informatica MDM Hub
configuration can have one or more ORS databases.
Select the Master Database or the ORS to which you want to connect.
Click Connect.
Note: You can easily change the target database once inside the Hub Console.
The Hub Console is displayed, as shown in the following example.
Note: What you see might differ from this example screen shot.
169
Verify your Informatica MDM Hub installation by completing the following tasks.
Step
Task
1
Register the newly-created ORS database “Configuring Operational Record Stores
using the Databases tool in the Hub
and Datasources” in the Informatica MDM
Console.
Hub Administrator Guide
2
Register any installed Cleanse Match
Servers using the Cleanse Match Server
tool in the Hub Console.
“Configuring Data Cleansing” in the
Informatica MDM Hub Administrator Guide
3
Run the validation process on the
newly-created ORS database using the
Metadata Manager tool in the Hub
Console. Save a copy of the final
validation results in your installation
documentation folder.
Informatica MDM Hub Metadata Manager
Guide
4
Generate an Environment Report of your Appendix D, “Viewing Configuration
Details,” in the Informatica MDM Hub
current Informatica MDM Hub
Administrator Guide
configuration (Hub Servers, Cleanse
Match Servers, the Master Database,
ORS databases, and version history)
using the Enterprise Manager tool in the
Hub Console. Save a copy of the
Environment Report in your installation
documentation folder.
5
Copy the following log files to the
document directory you created in
“Create an Installation Documentation
Directory” on page 9:
•
•
•
•
6
Instructions
“Informatica MDM Hub Log Files” on
page 186
Hub Console log (console.log)
Hub Server log (cmxserver.log)
Cleanse Match Server log
(cmxserver.log)
Database log (cmx_debug.log)
Archive your installation documentation
directory. If requested, submit the
contents of this directory to Informatica
Global Customer Support.
“Informatica Global Customer Support”
on page xvi
Uninstalling Informatica MDM Hub
This chapter describes how to uninstall your Informatica MDM Hub implementation.
Chapter Contents
•
Uninstalling Informatica MDM Hub (JBoss/UNIX)
•
Uninstalling Informatica MDM Hub (WebSphere/UNIX)
•
Uninstalling Informatica MDM Hub (JBoss/Windows)
•
Uninstalling Informatica MDM Hub (WebSphere/Windows)
Uninstalling Informatica MDM Hub 171
Uninstalling Informatica MDM Hub involves the following steps:
Step
Task
Instructions
1
Remove each instance of the Cleanse
Match Server software.
“Uninstalling the Cleanse Match Server”
on page 172
2
Remove the Hub Server software.
“Uninstalling the Hub Server” on page 173
3
Remove the Hub Store (databases and
users) from DB2.
“Uninstalling the Hub Store from DB2”
on page 183
Uninstalling the Cleanse Match Server
This section describes how to remove a Cleanse Match Server installation from your
system.
Note: If you have more than one Cleanse Match Server running, you must perform
these steps for each Cleanse Match Server you want to uninstall.
Removing the Cleanse Match Server
To uninstall a Cleanse Match Server:
1. If the Cleanse Match Server is running, stop it by stopping the application server.
2.
Navigate to the following directory:
<MDM_Install_Directory>/hub/cleanse/UninstallerData
3.
Run Uninstall_Informatica_Hub_Cleanse_Match_Server.
The Uninstall introduction screen is displayed.
4.
Click Uninstall to begin the uninstall process.
While the process is underway, the Please Wait screen is displayed.
When the process is done, the Uninstall Complete screen is displayed.
5.
Click Done.
Note: The installation process begins by undeploying any pre-existing Cleanse
Match Servers. If the undeployment process fails, you will need to undeploy
manually according to the instructions in “Manually Undeploying the Cleanse
Match Server” on page 173.
Manually Undeploying the Cleanse Match Server
If for some reason you need to manually undeploy the Cleanse Match Server in the
JBoss application server environment, delete the siperian-mrm-cleanse.ear from
the <JBoss_install_dir>/server/<configuration_name>/deploy directory.
Note: Restart the JBoss application server if the JBoss auto-deploy process does not
remove the applications. For more information, refer to your JBoss administration
documentation.
Uninstalling the Hub Server
This section describes how to remove a Hub Server installation from your system.
Removing the Hub Server
To uninstall Hub Server:
1. Navigate to the<MDM_Install_Directory>/hub/server/UninstallerData
directory and execute Uninstall_Informatica_Hub_Server.
2.
When the process is underway, the Please Wait screen is displayed.
3.
Click Done.
Important: When uninstalling the Hub Server, check for the presence of the following
files and delete them if they were not deleted from the <JBoss_
Home>/server/<configuration_name>/deploy folder. These files must be removed
before you can upgrade to the current version of Informatica MDM Hub:
siperian-mrm.ear
siperian-mrm-ds.xml
siperian-mrm-cleanse.ear
Manually Undeploying the Hub Server
The uninstall process should automatically do the following actions for you:
• Delete siperian-mrm.ear and siperian-mrm-ds.xml from the <JBoss_
install_dir>/server/<configuration_name>/deploy directory.
•
Remove the following files from server/default/deploy/messaging if they exist.
These files contain the JMS configuration queue.
•
siperian-jms-ds.xml
•
siperian-destination-service.xml
(WebSphere/UNIX)
Step
Task
Instructions
1
on page 175
2
3
users) from DB2.
on page 183
Note: You may have to manually remove some artifacts on the file system left behind
after uninstalling (directories, log files, custom code, etc.).
system.
Note: If you have more than one Cleanse Match Server running, you must perform
these steps for each Cleanse Match Server you want to uninstall.
2.
Navigate to the following directory:
<MDM_Install_Directory>/hub/cleanse/UninstallerData
3.
Run Uninstall_Informatica_Hub_Cleanse_Match_Server.
4.
5.
Click Done.
Note: The installation process begins by undeploying any pre-existing Cleanse
Match Servers. If the undeployment process fails, you will need to undeploy
manually according to the instructions in “Manually Undeploying the Cleanse
Match Server” on page 176.
If for some reason you need to manually undeploy the Cleanse Match Server in the
WebSphere application server environment, uninstall the
siperian-mrm-cleanse.ear application using the WebSphere Application Server
Administrative Console. Make sure that the process finishes completely. For more
information, refer to your WebSphere documentation
To uninstall Hub Server:
1. Navigate to the <MDM_Install_Directory>/hub/server/UninstallerData
directory and execute Uninstall_Informatica_Hub_Server.
2.
When the process is underway, the Please Wait screen is displayed.
3.
Click Done.
The install process should automatically undeploy the siperian-mrm.ear application
using the WebSphere Application Server Administrative Console.
Step
Task
Instructions
1
on page 177
2
3
users) from DB2.
on page 183
system.
2.
•
Click the Start button and select Programs > Infamdm > Hub > Cleanse
> Uninstall Informatica MDM Hub Cleanse Match Server, or
•
Navigate to the <MDM_Install_
Directory>\hub\cleanse\UninstallerData directory and double-click
Uninstall_Informatica_MDM_Hub_Cleanse_Match_Server.exe.
3.
Click Uninstall to begin the uninstallation.
The Uninstall Complete screen is displayed.
4.
Click Done.
For JBoss, delete the siperian-mrm-cleanse.ear file from the
server\<configuration_name>\deploy directory.
Note: Restart the JBoss application server if the JBoss auto-deploy process does not
remove the applications. For more information, refer to your JBoss Administration
documentation.
To uninstall the Hub Server:
1. Do one of the following:
•
Click the Start button and select Programs > Infamdm > Hub > Server >
Uninstall Informatica MDM Hub Server, or
•
Navigate to the <MDM_Install_
Directory>\hub\server\UninstallerData
directory and double-click Uninstall_Informatica_MDM_Hub_Server.exe.
2.
3.
Click Done.
You must restart the application server after you uninstall.
If you are using the JBoss application server, delete siperian-mrm.ear and
siperian-mrm-ds.xml from the <JBoss_install_dir>/server/<configuration_
name>/deploy directory.
Also remove the following files from server/<configuration_name>/deploy/jms
if they exist.These files contain the JMS configuration queue.
•
siperian-jms-ds.xml
•
siperian-jmsmq-service.xml
Note: Restart the server if the auto-deploy process of JBoss doesn’t remove the
applications. For more information, see your JBoss documentation.
(WebSphere/Windows)
Step
Task
Instructions
1
on page 179
2
“Dropping Hub Store Databases” on page
180
3
users) from DB2.
on page 183
system.
2.
•
Click the Start button and select Programs > Infamdm> Hub > Cleanse >
Uninstall Informatica MDM Hub Cleanse Match Server, or
•
Navigate to the MDM_Install_Directory\hub\cleanse\UninstallerData
directory and double-click Uninstall_Informatica_MDM_Hub_Cleanse_
Match_Server.exe.
3.
4.
Click Done.
For WebSphere, uninstall the siperian-mrm-cleanse.ear application from the
WebSphere Application Server Administrative Console. Make sure that the process
finishes completely. See your WebSphere documentation for more information.
Dropping Hub Store Databases
Note: You must have DB2 DBA privileges to complete the instructions in this section.
To drop Hub Store databases:
1. Log into Hub Console according to the instructions in “Starting the Hub Console”
on page 167.
2.
Start the Databases tool according to the instructions in the Informatica MDM Hub
Administrator Guide.
3.
Acquire a write lock.
4.
In the list of databases, select the ORS database(s) that you want to unregister, and
button.
then click the
The Databases tool prompts you to confirm unregistering the ORS.
5.
Click Yes.
6.
Connect to the DB2 instance using SQL*PLUS, using a login with DBA privileges.
7.
For each of the schemas listed in “Database Objects to Drop” on page 183, issue
the following command (dropping the user with the CASCADE option also drops
the associated database):
connect to db2 as admin user
executing
db2 set schema cmx_ors
executing
db2 set path cmx_ors
executing
db2 terminate
executing
db2 set sqlcompat plsql
executing
db2 -td@ -vf clean_db2_schema_progress.sql
db2 -td@ -s -f clean_db2_schema.sql
db2 terminate
8.
For the Hub Store, issue the following command (dropping the user with the
CASCADE option also drops the associated database).
Connect to db2 as admin user:
executing
db2 set schema cmx_system
executing
db2 set path cmx_system
executing
db2 terminate
executing
db2 set sqlcompat plsql
executing
db2 -td@ -vf clean_db2_schema_progress.sql
db2 -td@ -s -f clean_db2_schema.sql
db2 terminate
To uninstall the Hub Server:
1. Do one of the following:
2.
•
Click the Start button and select Programs > Infamdm > Hub > Server >
Uninstall Informatica MDM Hub Server, or
•
Navigate to the MDM_Install_Directory\hub\server\UninstallerData
directory and double-click Uninstall_Informatica_MDM_Hub_Server.exe.
3.
Click Done.
You must restart the application server after you uninstall.
If for some reason you need to manually undeploy the Hub Server in the WebSphere
environment, uninstall the siperian-mrm.ear application using the WebSphere
Application Server Administrative Console. Make sure that the process finishes
completely. For more information, see your WebSphere documentation.
Uninstalling the Hub Store from DB2
This section describes how to uninstall the Hub Store for all supported platforms and
application server environments.
Note: File names and directories in this section may vary slightly depending on what
type of installation you are performing.
Database Objects to Drop
When uninstalling the Master Database, you must:
• Drop any Master Database database schemas (Master Database and any ORS
databases).
The scripts to do use are:
clean_db2_schema_progress.sql
clean_db2_schema.sql
•
After you run the scripts, drop the database:
executing
drop database <database_alias>
Troubleshooting
This chapter explains how to troubleshoot your installation and make changes to your
application and database servers after running the installation process.
Chapter Contents
•
Informatica MDM Hub Log Files
•
Bypassing Prerequisite Installation
•
Updating Parameters After Installation
•
Checking the Hub and Cleanse Match Server Silent Install
•
MATCH Process Error: VerifyNeedToStrip
•
Inaccurate Start/Stop Timestamp for ORS
•
major.minor Version Errors When Loading Cleanse Match Server
•
Low Cleanse/Match Application Server Performance
•
Troubleshooting (JBoss/UNIX)
•
Troubleshooting (WebSphere/UNIX)
•
Troubleshooting (JBoss/Windows)
•
Troubleshooting (WebSphere/Windows)
Troubleshooting
185
This section describes the Informatica MDM Hub log files that you can use for
troubleshooting your installation.
Informatica MDM Hub Log Files (UNIX)
This section describes the Informatica MDM Hub log files on the UNIX platform.
About the Informatica MDM Hub Log Files
Informatica MDM Hub creates the following log files:
• console.log
•
cmxserver.log (for Master Reference Manager)
•
cmx_debug.log
•
cmxserver.log (for Cleanse Match Server)
console.log
This log file is created in c:/Documents and Settings/<user_
home>/infamdm/console.log. It contains the log messages from
the Hub Console.
Any errors that occur when communicating with the application server or error
messages from the application server or console error messages are logged to this file.
By default console.log is ON and created.
This log file is a rolling log file. Once it reaches 5 MB, it is copied to console.log.1
and resumes. Hub Server does this indefinitely, potentially creating very many log files.
It is a good idea to periodically delete the old files, or transfer them to some other
storage.
The console.log file is created on the local machine from which you launch and use
the Hub Console.
Note: The PATH given for the console log is a Windows path, not a UNIX one, as the
console.log file is written on the local machine on which you have launched Hub
Console.
This is the log file for the application server. During installation, if you choose the
default location, cmxserver.log appears in <MDM_Install_
Directory>/hub/server/logs. In general the file location is <MDM_Install_
Directory>/hub/server/logs.
This log file contains all of the logging and debugging information from the
application server. By default cmxserver.log is ON and created. This log file is a
rolling log file and once it reaches 5MB, it is copied to cmxserver.log.1 and resumes.
Hub Server does this indefinitely, potentially creating very many files. It is a good idea
to periodically delete the old files, or transfer them to some other storage.
This log file is for the CLEANSE, TOKENIZATION, and SIMULATION functions.
It is located in the <Cleanse_Install_Directory>/hub/cleanse/logs directory.
This log file contains all of the debugging and error messages for the Cleanse process
(Landing >Staging). By default cmxserver.log is ON. This log file is a rolling log file
and once it reaches 5MB, it is copied to cmxserver.log.1 and resumes.
cmx_debug.log
This log file is for the database stored procedures. This log file contains all of the
logging information for the PUT, GET, GETLIST, MATCH, LOAD, MERGE, and
AUTOMERGE stored procedures. By default cmx_debug.log is ON. To set debug
logging on, see “Enabling Debug Logging” on page 188.
Troubleshooting
187
Enabling Debug Logging
To enable debug logging you need to modify the build.properties file before you
create the database.
db2.debug.ind=1
db2.debug.path=/home/db2inst1/cmx_debug/
db2.debug.file=cmx_ors_debug.log
For more information about the debug log, see the instructions in the Informatica MDM
Hub Administrator Guide for the Enterprise Manager tool in the Hub Console.
Changing the Log File Locations
Do not edit the cmxserver.properties file to change the location of the logs.
• For Informatica MDM Hub on WebSphere, edit the following file:
<MDM_Install_Directory>/conf/log4j.xml
•
For Cleanse Match Server, edit the following file:
<MDM_Install_Directory>/conf/log4j.xml
Maintaining the Log Files
The rolling nature of all Informatica MDM Hub log files means that you must
periodically perform some housekeeping, either deleting old logs or moving them to
permanent storage to keep them from becoming too numerous and taking up too
much space.
Informatica MDM Hub Log Files (Windows)
This section describes the Informatica MDM Hub log files on the Windows platform.
About the Informatica MDM Hub Log Files
Informatica MDM Hub creates the following log files:
• console.log
•
•
•
cmx_debug.log
•
Note: Some files include password information.
console.log
This file is created in C:\Documents and Settings\<MDM_Install_
Directory>\infamdm\console.log
It contains the messages from the Hub Console. Any errors that occur when
communicating with the application server or error messages from the application
server or console error messages are logged to this file.
By default cmxconsole.log is ON and created. It is a good idea to periodically delete
the old files, or transfer them to some other storage.
This is the log file for the application server. During installation, if you choose the
default location, cmxserver.log appears in C:\<MDM_Install_
Directory>\hub\server\logs. In general, the file location is <MDM_Install_
Directory>\hub\server\logs.
Troubleshooting
189
This file contains all of the logging and debugging information from the application
server. By default cmxserver.log is ON and created. This file is a rolling file and once
it reaches 5MB, it is copied to cmxserver.log.1 and resumes. Hub Server does this
indefinitely, potentially creating very many files. It is a good idea to periodically delete
the old files, or transfer them to some other storage.
This file is for the CLEANSE\TOKENIZATION\SIMULATION. It is located in the
install directory <MDM_Install_Directory>\hub\cleanse\logs. This file contains
all of the debugging and error messages for the Cleanse process (Landing > Staging).
By default cmxserver.log is ON. This file is a rolling file and once it reaches 5MB, it
is copied to cmxserver.log.1 and resumes.
cmx_debug.log
The cmx_debug.log file is for the database stored procedures. It contains all of the
logging information for the PUT, GET, GETLIST, MATCH, LOAD, MERGE, and
AUTOMERGE stored procedures. By default cmx_debug.log is ON. To set debug
logging on, see “Enabling Debug Logging” on page 190. The Enterprise Manager
allows you to change the name of the debug file.
Note: If debug logging is enabled, make sure that the log file size multiplied by the
maximum number of database log files does not exceed the storage available, or the
maximum file size of your operating system.
Enabling Debug Logging
To enable debug logging you need to modify the build.properties file before you
create the database
db2.debug.ind=1
db2.debug.path=/home/db2inst1/cmx_debug/
db2.debug.file=cmx_ors_debug.log.
For more information about the debug log, see the instructions in the Informatica MDM
Hub Administrator Guide for the Enterprise Manager tool in the Hub Console.
Setting the Location of the Log Files
Important: DO NOT edit the cmxserver.properties file to change the location of the
logs.
Component
Configuration file to edit to set the location of the logs
Hub Server
<infamdm_install_directory>\conf\log4j.xml
<infamdm_install_directory>\conf\log4j.xml
where <infamdm_install_directory> is the directory into which you installed
HubServer and Cleanse Match Server.
Bypassing Prerequisite Installation
To bypass the prerequisite validation in the installation, you can add the following
parameter to the install command:
-DSIPERIAN_INSTALL_PREREQ_VALIDATION=false
This section describes how to update Hub Server and Cleanse Match Server
parameters after installation.
Updating Hub Server Parameters After Installation
If the environment changes or parameters were entered incorrectly during the
installation process, you can manually correct the information after you run the
installation.
The postInstallSetup script undeploys your current application (if there is one),
repackages your application with the new information, configures your message
queues, installs or recreates your datasource and deploys the newly packaged
application to your application server.
Troubleshooting
191
Note: For more information on running postInstallSetup, see “PostInstallSetup”
on page 37.
For instructions on specific application servers and platforms, see the following topics:
• “Changing the Hub Server Parameters (WebSphere/UNIX)” on page 204
•
“Changing the Hub Server Parameters (WebSphere/Windows)” on page 213
Updating Cleanse Match Server Parameters After
Installation
If the environment changes or parameters were entered incorrectly during the
installation process, you can manually correct the information after you run the
installation.
For instructions, see:
• “Changing the Cleanse Match Server Parameters (WebSphere/UNIX)” on page
205
•
“Changing the Cleanse Match Server Parameters (WebSphere/Windows)” on page
214
The postInstallSetup script is used to use manually repackage the application and
redeploy it on your application. It undeploys your current application (if there is one),
repackages your application with the new information, configures your message
queues, installs or recreates your datasource and deploys the newly packaged
application to your application server. For more information on running
postInstallSetup, see “PostInstallSetup” on page 37.
Checking the Hub and Cleanse Match Server Silent
Install
This section describes how to confirm that your silent install was successful. A failed
silent install could be due to many factors, including incorrect information in the silent
property file (such as the incorrect application-server installation paths, or the fact that
the file contains too many port numbers). To verify that your silent install succeeded,
you can check files for entries related to the silent install, and folders for files related to
the silent install.
Checking the Hub Server and Cleanse Match Server Silent
Install (UNIX)
This section applies to checking silent installs in the UNIX environment.
Checking the Hub Server Silent Install
The following tables list the files or folders you should check when you perform a
silent Hub Server install.
Location
Check For
<MDM_Install_
Directory>/logs
postInstallSetup.log: Check for any ERROR in the log.
<MDM_Install_
Directory>/setSiperian.bat
where appserver is WebSphere
Check for following variables and make sure their values are correct in your
environment.
SET SIP_HOME=C:/infamdm/hub/server
SET WAS_HOME=C:/Program Files/IBM/WebSphere/AppServer
SET WAS_SERVER=server1
If any of the contents of the files or the properties listed in the table above are
incorrect, you must enter the correct contents or properties manually into the
silent-install property file, then restart the installation. Alternatively, you can make
corrections to the individual files, such as the cmxserver.properties file, and rerun
the postInstallSetup command manually from the same <server_install_dir>.
Troubleshooting
193
Checking the Cleanse Match Server Silent Install
The following tables list the files or folders you should check when you perform a
silent Cleanse Match Server install.
Location
Check For
<MDM_Install_
Directory>/logs
postInstallSetup.log: Check for any ERROR in the file
<Cleanse_Install_
Directory>
/resources/cmxcleanse.pr
operties
# IDQ Properties
# Address Doctor Properties
cleanse.library.addressDoctor.property.AddressDoctor.UnlockCode=
and cmx.appserver.type files cleanse.library.addressDoctor.property.AddressDoctor.DatabasePath=C:/addressdo
ctor
cleanse.library.addressDoctor.property.AddressDoctor.Optimization=ADDRESSES
_SORTED_BY_COUNTRIES
cleanse.library.addressDoctor.property.AddressDoctor.MemoryMB=600
cleanse.library.addressDoctor.property.AddressDoctor.CorrectionType=CORRECT
_ONLY
cleanse.library.addressDoctor.property.AddressDoctor.PreLoad.CERTIFIED.PREL
OAD_PART=US
OAD_FULL=
cleanse.library.addressDoctor.property.AddressDoctor.PreLoad.CORRECTION_
ONLY.PRELOAD_PART=CA, US
ONLY.PRELOAD_FULL=
# Trillium Director Properties
cleanse.library.trilliumDir.property.config.file.1=C:/infamdm/hub/cleanse/resource
s/Trillium/samples/director/td_default_config_Global.txt
s/Trillium/samples/director/td_default_config_US_detail.txt
s/Trillium/samples/director/td_default_config_US_summary.txt
<Cleanse_Install_
Directory>
/resources/cmxserver.pro
perties
cmx.home=$USER_INSTALL_DIR$
# Application server type: websphere
cmx.appserver.type=$SIP.APPSERVER.TYPE$
# default setting: 8880 for websphere only
cmx.appserver.soap.connector.port=$SIP.WEBSPHERE.SOAP.PORT$
Location
Check For
<Cleanse_Install_
All the settings in setSiperianEnv.bat for Cleanse Match Server are the same
Directory>/setSiperianEnv.bat as for the Hub Server.
where the appserver is JBoss
<Cleanse_Install_
Directory>/setSiperianEnv.bat as for the Hub Server.
corrections to the individual files, such as the cmxcleanse.properties file, and rerun
the postInstallSetup command manually from the same <Cleanse_Install_
Directory>.
Troubleshooting
195
Checking the Hub Server and Cleanse Match Server Silent
Install (Windows)
This section applies to checking silent installs in the Windows environment.
Checking the Hub Server Silent Install (Windows)
Check these files or folders when you perform a silent Hub Server install.
Location
Check For
<server_install_dir>\logs postInstallSetup.log: Check for any ERROR in the log.
<server_install_
Database credentials.
dir>\bin\build.properties where
the appserver is WebSphere
Look for the following properties and make sure their values are correct.
Example values:
masterdatabase.type=DB2
masterdatabase.server=Server_name
masterdatabase.port=port
masterdatabase.dbname=database_name
masterdatabase.schemaname=cmx_system
masterdatabase.user=db2admin
<server_install_
cmx.server.masterdatabase.type, cmx.appserver.type, cmx.appserver.rmi.port
dir>\resources\cmxserver.prop and cmx.appserver.soap.connector.port
erties
<MDM_Install_
Directory>\setSiperian.bat
Check for following variables and make sure their values are correct in your
environment.
SET SIP_HOME=C:\infamdm\hub\server
SET WAS_HOME=C:\Program Files\IBM\WebSphere\AppServer
SET WAS_SERVER=server1
If any of the items are incorrect, enter the correct contents or properties manually into
the silent-install property file, then restart the installation. You can also make
the postInstallSetup command manually from the same <server_install_dir>.
Checking the Cleanse Match Server Silent Install (Windows)
Check these files or folders when you perform a silent Cleanse Match Server install.
Location
Check For
<MDM_Install_
Directory>\logs
postInstallSetup.log: Check for any ERROR in the file
<MDM_Install_Directory>
\resources\cmxcleanse.pr
operties
#IDQ Properties
# Address Doctor Properties
and cmx.appserver.type files cleanse.library.addressDoctor.property.AddressDoctor.UnlockCode=
cleanse.library.addressDoctor.property.AddressDoctor.DatabasePath=C:/addressdo
ctor
cleanse.library.addressDoctor.property.AddressDoctor.Optimization=ADDRESSES
_SORTED_BY_COUNTRIES
cleanse.library.addressDoctor.property.AddressDoctor.MemoryMB=600
cleanse.library.addressDoctor.property.AddressDoctor.CorrectionType=CORRECT
_ONLY
OAD_PART=US
OAD_FULL=
ONLY.PRELOAD_PART=CA, US
ONLY.PRELOAD_FULL=
# Trillium Director Properties
cleanse.library.trilliumDir.property.config.file.1=C:\infamdm\hub\cleanse\resource
s\Trillium\samples\director\td_default_config_Global.txt
s\Trillium\samples\director\td_default_config_US_detail.txt
s\Trillium\samples\director\td_default_config_US_summary.txt
<MDM_Install_Directory>
\resources\cmxserver.pro
perties
cmx.home=$USER_INSTALL_DIR$
# Application server type: websphere
cmx.appserver.type=$SIP.APPSERVER.TYPE$
# default setting: 8880 for websphere only
cmx.appserver.soap.connector.port=$SIP.WEBSPHERE.SOAP.PORT$
Troubleshooting
197
Location
Check For
<MDM_Install_
Directory>\setSiperianEnv.bat as for the Hub Server.
the postInstallSetup command manually from the same <MDM_Install_Directory>.
This section applies if you encounter VerifyNeedToStrip error SIP-16062 during
the execution of the Match process.
VerifyNeedToStrip (UNIX)
If you receive VerifyNeedToStrip error SIP-16062 while you run a Match process,
check the following library and environment variable settings:
• The library path environment variable should contain the following path for the
Informatica profile:
<MDM_Install_Directory>/lib
The library path environment variable depends on the platform:
•
AIX: LIBPATH
•
HP-UX: SHLIB_PATH
•
Solaris, Suse, or RedHat: LD_LIBRARY_PATH
Example (HP-UX):
SHLIB_PATH=/u1/infamdm/hub/cleanse/lib
•
The SSAPR environment variable should include the following path for all users
(such as the Informatica user):
<MDM_Install_Directory>/resources
Example:
SSAPR=/u1/infamdm/hub/cleanse/resources
VerifyNeedToStrip (Windows)
If you receive VerifyNeedToStrip error SIP-16062 while you run a Match process,
check the following library and environment variable settings:
• The PATH environment variable should contain the following path for the
Informatica profile:
<MDM_Install_Directory>\cleanse\lib
Example:
PATH=C:\infamdm\hub\cleanse\lib
•
The SSAPR environment variable should include the following path for all users
(such as the Informatica user):
<MDM_Install_Directory>\cleanse\resources
Example:
SSAPR=C:\infamdm\hub\cleanse\resources
If you create an ORS, then export it, and subsequently reuse the .dmp file of this
previously-installed ORS to create a second ORS, the start date and end date columns
in the C_REPOS_DB_VERSION table of this ORS will have a different value from
the actual start date and end date. This difference in date does not affect any
functionality.
Troubleshooting
199
major.minor Version Errors When Loading Cleanse Match Server
major.minor Version Errors When Loading Cleanse
Match Server
If you see multiple major.minor console errors when you try to load your Cleanse
Match Server, check that your system has the correct Java version installed (Java 1.6).
Low Cleanse/Match Application Server Performance
Application Server performance can be slow due to a high number of performance log
entries in the log4j.xml file.
To remedy this, modify the log4j.xml file to exclude performance-related logging as
follows:
<category name="siperian.performance" additivity="false">
<priority value="OFF"/>
<appender-ref ref="fileAppender"/>
</category>
This section provides troubleshooting instructions for JBoss on UNIX.
Changing the Hub Server Parameters (JBoss/UNIX)
You can change the following Hub Server parameters:
• JBoss application server and RMI port number
•
Database server and instance name
Changing the RMI Port Number for JBoss
To change the application server and RMI port number:
1. Open the following file in a text editor:
<MDM_Install_Directory>/resources/cmxserver.properties
2.
Change the following value:
3.
Go to <MDM_Install_Directory> and run postInstallSetup.sh.
4.
Changing the Database Server and Instance Name for JBoss
To change the database server and instance name:
name>/deploy/siperian-mrm-ds.xml
2.
Change the following values:
<xa-datasource-property
name="URL">jdbc:DB2-<host>:<port>:<instance></xa-datasource-prope
rty>
Troubleshooting
201
where host is the name of the host running your DB2 database, port is the port
number on which DB2 is listening, and instance is the name of your DB2
instance.
Note: Do not run postInstallSetup for JBoss.
3.
Manually Redeploying the Hub Server (JBoss/UNIX)
Informatica provides the postInstallSetup script that both the Hub Server installer
and user can use to deploy/redeploy the Hub Server application to the application
server. However, you can also use the default application server’s tool to do the
deployment yourself, as long as it is deployed from the Hub Server installation
directory. To manually redeploy the Hub Server application:
1. Stop the server.
2.
Remove the siperian-mrm.ear from <JBoss_install_
dir>/server/<configuration_name>/deploy to make sure the application is
totally removed.
3.
Copy the siperian-mrm.ear from the Hub Server installation directory.
4.
Start the server.
Refer to your JBoss documentation for more information.
(JBoss/UNIX)
The installation process begins by undeploying any pre-existing Cleanse Match Servers.
If this process fails, you will need to undeploy manually. Delete the
siperian-mrm-cleanse.ear from the <JBoss_install_
dirE>/server/<configuration_name>/deploy directory.
Note: Restart the server if the auto-deploy process of JBoss does not remove the
applications. See your JBoss administration documentation for more information.
Setting the JVM Size (JBoss/UNIX)
If you are using AddressDoctor Cleanse Engine as your cleanse engine to run any
batch process, you must make sure that the stack size for the JVM is sufficient. If you
do not set this properly for your application server, AddressDoctor will throw an
exception during certification.
To set the JVM size for JBoss:
1. Go to your JBoss home directory.
2.
Navigate to the bin directory.
3.
Open run.sh in a text editor.
4.
Set the JAVA_OPTS variable as follows:
JAVA_OPTS=${JAVA_OPTS} -Xmx1024m
5.
Save and close the run.sh file.
Troubleshooting
203
This section provides troubleshooting instructions for WebSphere on UNIX.
Changing the Hub Server Parameters (WebSphere/UNIX)
You can change the following parameters:
• RMI port number
•
SOAP port number
To change the RMI or SOAP port numbers:
<MDM_Install_Directory>/resources/cmxserver.properties
2.
Change any of the following values:
3.
Go to <MDM_Install_Directory> and run the following command:
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 must keep the application server running while you run the script, or the
script will fail.
4.
Changing the Cleanse Match Server Parameters
(WebSphere/UNIX)
You can change the SOAP port number.
To change the SOAP port numbers:
<MDM_Install_Directory>/resources/cmxcleanse.properties
2.
3.
where yourDBPassword the password for your database.
script will fail.
4.
Troubleshooting
205
Changing the Hub Server Parameters for the Database
(WebSphere/UNIX)
You can change the following database parameters for WebSphere:
• Database server name
•
Database instance name
Changing Server Name for the Database
To change the database server name:
2.
masterdatabase.server=<database_server_name>
masterdatabase.port=<port>
masterdatabase.dbname=<database_name>
masterdatabase.jdbc.url=jdbc:db2://
<database_host_name>:<port>/<database_name>
3.
where yourDBPassword is the password for your database.
script will fail.
4.
Changing Instance Name for the Database
To change the instance name:
2.
3.
script will fail.
4.
(WebSphere/UNIX)
and user can use to deploy/redeploy the Hub Server application to the application
server. However, you can also use the WebSphere Application Server Administrative
Console to redeploy siperian-mrm.ear as long as it is deployed from the Hub
Server installation directory.
Use the WebSphere Application Server Administrative Console to redeploy
siperian-mrm.ear. To redeploy the Hub Server on the WebSphere application
server:
1. Use the WebSphere Server Administration Console to undeploy the
siperian-mrm.ear file.
Troubleshooting
207
2.
Use the WebSphere Application Server Administrative Console to install the
siperian-mrm.ear file.
Be sure to allow the deployment to generate default bindings by checking the
option in the “Preparing for the application installation” panel.
(WebSphere/UNIX)
If this process fails, you will need to undeploy manually. Uninstall the
siperian-mrm-cleanse.ear application from the WebSphere Application Server
Administrative Console. Make sure that the process finishes completely. See your
WebSphere documentation for more information.
Setting the JVM Size (WebSphere/UNIX)
To set the JVM size for WebSphere:
1. Open the WebSphere Console.
2.
Go to Servers > Application Server > <Your_Server> > Process Definition
> Java Virtual Machine
3.
Add the following to the Generic JVM Arguments
-Xss1024k
- Initializes the stack with at least 256 KB
-Xss1024m
- Initializes the stack when running in CASS mode
-Xmx1024m
- Initializes the heap with a maximum of 1024 MB
-Xms128m
- Initializes the heap with at least 128 MB
4.
Save the configuration.
5.
Restart the server.
Changing the SOAP Request Timeout (WebSphere/UNIX)
If the postinstallsetup process fails due to a timeout error, you can increase the SOAP
request timeout value and retry the process. Locate and edit the following file:
<portal_profile_root>/properties/soap.client.props
Change the following value from:
com.ibm.SOAP.requestTimeout=180
to
This section provides troubleshooting instructions for JBoss on Windows.
Changing the Hub Server Parameters (JBoss/Windows)
• JBoss application server and RMI port number
•
Database server and instance name
Changing the Application Server and RMI Port Number for
JBoss
To change the application server and RMI port number:
<MDM_Install_Directory>\resources\cmxserver.properties
2.
Change the following value:
3.
Go to <MDM_Install_Directory> and run postInstallSetup.bat.
4.
Troubleshooting
209
Changing the Database Server and Instance Name for JBoss
To change the database server and instance name:
name>\deploy\siperian-mrm-ds.xml
2.
<xa-datasource-property
name="URL">jdbc:DB2-<hostname>:<port><datasource>-</xa-datasource
-property>
where hostname is the name of the host.
Note: Do not run postinstall for JBoss.
3.
Manually Redeploying Hub Server (JBoss/Windows)
and user can use to deploy or redeploy the Hub Server application to the application
directory. Refer to your application server documentation for more information.
To manually deploy Hub Server:
1. Stop the server.
2.
Remove the siperian-mrm.ear from <JBoss_install_
dir>\server\<configuration_name>\deploy\siperian-* files and <JBoss_
install_dir>\server\<configuration_name>\deploy\jms\siperian-* to make
sure all related files and application are totally removed.
3.
Copy the siperian-mrm.ear from Hub Server installation directory to <JBoss_
install_dir>\server\<configuration_name>\deploy.
4.
Copy siperian-mrm-ds.xml from <server_install_dir>\conf to <JBoss_
install_dir>\server\<configuration_name>\deploy.
5.
Copy siperian-jms-ds.xml and siperian-destination-service.xml from <server_
install_dir>\conf to <JBoss_install_dir>\server\<configuration_
name>\deploy\messaging.
6.
Start the server.
Troubleshooting
211
(JBoss/Windows)
If this process fails, you will need to undeploy manually. Delete the
siperian-mrm-cleanse.ear from the <JBoss_install_
dir>/server/<configuration_name>/deploy directory.
Note: Restart the server if the auto-deploy process of JBoss doesn't remove the
applications. See your JBoss administration documentation for more information.
Setting the JVM Size (JBoss/Windows)
To set the JVM size for JBoss:
1. Go to your JBoss installation directory.
2.
Navigate to the bin directory.
Open run.bat in a text editor.
3.
Set the JAVA_OPTS variable as follows:
JAVA_OPTS="%JAVA_OPTS% -Xss1000k"
4.
Save and close the run.bat file.
This section provides troubleshooting instructions for WebSphere on Windows.
Changing the Hub Server Parameters
(WebSphere/Windows)
• RMI port number
•
SOAP port number
To change the RMI or SOAP port numbers:
<MDM_Install_Directory>\resources\cmxserver.properties
2.
3.
postInstallSetup.bat -Ddatabase.password=<yourDB2Password>
script will fail.
4.
Troubleshooting
213
Changing the Cleanse Match Server Parameters
(WebSphere/Windows)
You can change the SOAP port number.
To change the SOAP port numbers:
<MDM_Install_Directory>\resources\cmxcleanse.properties
2.
3.
postInstallSetup.bat -Ddatabase.password=<yourDB2Password>
where yourDB2Password the password for your database.
script will fail.
4.
Changing the Hub Server Parameters for the Database
(WebSphere/Windows)
You can change the following database parameters for WebSphere:
• Database server name
•
Database instance name
Changing Server Name for the Database
To change the database server name:
<MDM_Install_Directory>\bin\build.properties
2.
masterdatabase.server=<database_server_name>
masterdatabase.port=<port>
masterdatabase.dbname=<database_name>
3.
postInstallSetup.bat -Ddatabase.password=<yourDBPassword>
script will fail.
4.
Troubleshooting
215
Changing Instance Name for the Database
To change the instance name:
<MDM_Install_Directory>\bin\build.properties
2.
3.
postInstallSetup.bat -Ddatabase.password=<yourDBPassword>
script will fail.
4.
Manually Redeploying Hub Server (WebSphere/Windows)
and user can use to deploy or redeploy the Hub Server application to the application
directory. Refer to your application server documentation for more information.
To manually deploy Hub Server, use the WebSphere Application Server Administrative
Console to uninstall and install the siperian-mrm.ear from the Hub Server
installation directory. Be sure to allow the deployment to generate default bindings by
checking for the option in the “Preparing for the application installation” panel.
(WebSphere/Windows)
If this process fails, you will need to undeploy manually. Uninstall the
siperian-mrm-cleanse.ear application from the WebSphere Application Server
Administrative Console. Make sure that the process finishes completely. See your
WebSphere documentation for more information.
Setting the JVM Size (WebSphere/Windows)
To set the JVM size for WebSphere:
Open the WebSphere Console.
1.
2.
Go to Servers > Application Server > <Your_Server> > Process Definition
> Java Virtual Machine
3.
Add the following to the Generic JVM Arguments
-Xss1024k - Initializes the stack with at least 256 KB
-Xss1024m - Initializes the stack when running in CASS mode
-Xmx1024m - Initializes the heap with a maximum of 1024 MB
-Xms128m - Initializes the heap with at least 128 MB
-Xss1000k
4.
Save the configuration.
5.
Re-start the server.
Troubleshooting
217
Changing the SOAP Request Timeout
(WebSphere/Windows)
If the postinstallsetup process fails due to a timeout error, you can increase the SOAP
request timeout value and retry the process. Locate and edit the following file:
<portal_profile_root>\properties\soap.client.props
Change the following value from:
to
Installing from the Command Line
Informatica supports command-line installation for the Hub Server and the Cleanse
Match Server software. This section explains how to install these applications from the
command line, without using the GUI interface.
Chapter Contents
•
•
Installing from the Command Line (JBoss/UNIX)
•
Installing from the Command Line (WebSphere/UNIX)
•
Silent Installation from the Command Line
219
If you prefer to install Hub Server and Cleanse Match Server without using the GUI
installer, you can manually install the Hub Server and Cleanse Match Server from the
command line.
Before you install:
• Make sure that you have fulfilled the hardware and software requirements for Hub
Server as outlined in the Informatica MDM Hub Release Notes. In particular, make
sure you have the correct version of the DB2 drivers.
•
Make sure you have a license file from Informatica. You cannot install the
Informatica MDM Hub if you do not have a license file. Contact Informatica
xvi) for a license.
•
Make sure that you have your application server installed and configured. For more
information, see your application server documentation.
This section describes how to install the Hub Server and Cleanse Match Server
software from the UNIX command line.
Installing Hub Server
To install Hub Server from the command line:
2.
Run the following command from the command prompt:
The installer displays the Introduction screen.
Press Enter to continue.
3.
Read the License Agreement. Type Y for yes and press Enter to continue. Type N
for no if you do not want to accept the License Agreement and want to exit the
install program.
The installer displays information about the install folder.
4.
Press Enter to use the default installation folder for the Hub Server installation
(/infamdm/hub/server). If you want to change the installation folder, type in the
absolute path for the location and press Enter.
Confirm the installation folder (Y/N) and press Enter to continue.
The installer displays information about the link location.
5.
Select the link location.
The installer displays license file information.
6.
Check the default license file location. To accept the default location, press Enter.
To change the location, type the new absolute path to the license file location and
press Enter.
The names of the supported application servers are listed. Type the number for
your application server and press Enter to continue. The default is the JBoss
application server. Press Enter to accept the default.
221
As the GUI-based installer does, the command line installer depends on your
application server.
The JBoss Application Server information is displayed.
7.
a.
Specify the application server installation directory. Press Enter.
The JBoss Application Server Configuration Name information is displayed.
b.
Specify the Configuration Name (default is production). Press Enter.
c.
Press Enter.
The database JDBC driver files are copied to the
<JBoss_install_dir>/server/<configuration_name>/lib directory.
Note: If you type BACK at this point, the install will not be able to go back to
the previous step.
d.
name>/conf/jboss-service.xml
e.
The database selection prompt is displayed.
8.
Select DB2. Press Enter.
The DB2 Database Information screen is displayed.
9.
When prompted, specify the settings for the DB2 database to which you want to
connect. Press Enter to accept the default value, or replace the defaults with the
correct values. Press Enter.
10.
The deployment information is displayed. Choose whether you want to run the
postInstallSetup script as part of the installation, or run it manually later.
11.
Press Enter to accept the default value.
A summary of your installation choices is displayed.
12.
Verify the information in the pre-installation summary. If the information is
correct, press Enter to begin the installation.
The Hub Server will be installed according to the configuration information you
supplied. When the process is complete, the Install Complete information is
displayed.
13.
Press Enter to exit the installer.
14.
Verify the command-line installation by checking these log files:
The following files are useful for troubleshooting any Hub Server installation
process (see “Informatica MDM Hub Log Files” on page 186). Save these files
right after a failure and provide them when you report it to Informatica Global
Customer Support (see “Informatica Global Customer Support” on page xvi):
Location / Log File
Description
<MDM_Install_
debug.txt
Shows what was chosen during
installation.
<MDM_Install_
Contains the
for the script.
install directory.
Save a copy of these log files to the installation documentation directory described in
“Documenting Your Installation” on page 8.
223
Note: Do not use the root user when installing the Cleanse Match Server on RedHat
Linux. Instead, create and use a separate user profile for installing Informatica MDM
Hub. This is a limitation of InstallAnywhere, as the root user does not have a .profile.
To install the Cleanse Match Server from the command line:
2.
./hub_cleanse_install.bin -i console
This will start the installation and the Introduction is displayed.
3.
The License Agreement is displayed.
4.
Read the License agreement. Type Y for yes and press Enter to continue. Type N
for no if you do not want to accept the License Agreement and exit the install
program.
Information about the installation folder is displayed.
5.
Press Enter to use the default installation folder for the Cleanse Match Server. If
you want to change the default installation folder, type in the absolute path for the
location and press Enter.
License file information is displayed.
6.
Check default license file location. Press Enter to accept the default. To change
the location, type in the valid location. Press Enter to continue.
The names of the supported application servers are listed.
Type the number for your application server and press Enter to continue. To
accept the default application server (JBoss), press Enter.
As the GUI-based installer does, the command line installer depends on your
application server.
The JBoss Application Server home is displayed.
7.
a.
Specify the application server installation directory. Press Enter.
The JBoss Application Server Configuration Name is displayed.
b.
Specify the Configuration Name (default is production). Press Enter.
c.
name>/conf/jboss-service.xml
8.
As the GUI-based installer does, the command line installer depends on which
cleanse engines you have licensed.
9.
Adapter Guide.
•
If you are using AddressDoctor:
•
backslash (\\) instead. Press Enter.
The Configure AddressDoctor Preload information is displayed.
•
Specify the AddressDoctor preload parameters. Press Enter.
The Choose AddressDoctor Database Path information is displayed.
•
10.
Choose the AddressDoctor database path. Press Enter.
The Deploy screen provides the option to run the postInstallSetup script now
or run it manually later.
225
a.
b.
If you want to change any of the information in the pre-installation summary,
type BACK to go to a specific screen of information and make changes.
The Informatica Cleanse Match Server will be installed according to the
configuration information you supplied. When the process is complete, the
Install Complete information is displayed.
11.
12.
Verify the following files, which are useful for troubleshooting any Cleanse Match
Server installation process. Save these files right after a failure and provide them
when you report it to Informatica Global Customer Support (see “Informatica
Global Customer Support” on page xvi):
File
Description
errors and status.
<MDM_Install_
<MDM_Install_
installer_debug.txt
installation.
<MDM_Install_
(WebSphere/UNIX)
This section describes how to install the Hub Server and Cleanse Match Server
software from the UNIX command line.
Installing Informatica Hub Server
For the command-line installation, be sure to complete all of the preparation tasks
described for the Hub Server installation prior to doing the command line installation.
See “Preparing for Installation” on page 49 for details.
To install Hub Server from the command line:
2.
The Introduction displays, giving your further information about the installation.
3.
Read the License Agreement. Type Y for yes and press Enter to continue. Type N
for no if you do not want to accept the License Agreement and want to exit the
install program.
4.
Information about the install folder is displayed.
5.
Press Enter to use the default installation folder for the Hub Server installation
(/infamdm/hub/server). If you want to change the installation folder, type in the
absolute path for the location and press Enter.
Confirm the installation folder (Y/N). and press Enter to continue.
The installer displays information about the link location.
6.
Select the link location.
7.
Check default license file location. To accept the default location press Enter. To
change the location, type the new absolute path to the license file location and
press Enter.
The names of the supported application servers are listed. Type the number for
your application server and press Enter to continue.
The WebSphere Application Server Home information is displayed.
227
8.
Check the default location for the application server home. Replace the default
with the correct information if necessary. Press Enter to continue.
The installer warns you of the WebSphere pre-requisites for JDBC drivers.
9.
Check the database JDBC driver files location and press Enter to continue. The
database JDBC driver files are copied to the <WebSphere_Home>/AppServer/lib
directory.
Note: If you type BACK at this point, the install will not be able to go back to the
previous step.
The application server port information is displayed. If you need to change the
port information for the WebSphere Application Server, enter the information
here.
10.
Verify the Server name, RMI port, and SOAP port. Change the default
information or press Enter to accept the default. Press Enter to continue.
The database selection prompt is displayed.
11.
Select DB2. Press Enter.
12.
When prompted, specify the settings for the DB2 database to which you want to
connect. Press Enter to accept the default value, or replace the defaults with the
correct values. These settings include: Server Name, Port, Database Name, System
Schema, DBA Username, and DBA password. Press Enter.
13.
The deployment information is displayed. Choose whether you want to run the
postInstallSetup script as part of the installation, or run it manually later.
14.
A summary of your installation choices is displayed.
15.
Verify the information in the pre-installation summary. If the information is
correct, press Enter to begin the installation.
The Hub Server will be installed according to the configuration information you
supplied. When the process is complete, the Install Complete information is
displayed.
16.
17.
Verify the command-line installation by checking these log files. Save these files
right after a failure and provide them when you report it to Informatica Global
Customer Support (see “Informatica Global Customer Support” on page xvi):
Location / Log File
Description
<MDM_Install_
<MDM_Install_Directory>/hub/server/informatica_
installer_debug.txt
<MDM_Install_
Contains the
for the script.
<WebSphere_install_
SystemOut.log.
Linux. Instead, create and use a separate user profile for installing Informatica MDM
Hub. This is a limitation of InstallAnywhere, as the root user does not have a .profile.
To install the Cleanse Match Server from the command line:
2.
./hub_cleanse_install.bin -i console
229
This will start the installation and the Introduction is displayed.
3.
The License Agreement is displayed.
4.
Read the License agreement. Type Y for yes and press Enter to continue. Type N
for no if you do not want to accept the License Agreement and exit the install
program.
Information about the installation folder is displayed.
5.
Press Enter to use the default installation folder for the Cleanse Match Server. If
you want to change the default installation folder, type in the absolute path for the
location and press Enter.
6.
Check the default license file location. Press Enter to accept the default.
To change the location, type in the valid location. Press Enter to continue.
The names of the supported application servers are listed.
7.
Type the number for the WebSphere application server and press Enter to
continue.
The WebSphere application server home information is displayed.
8.
Enter the location for the WebSphere Application Server, or accept the default.
The WebSphere application server port information is displayed.
9.
Set the Server name and set the SOAP port number for your application server (or
accept the defaults).
10.
As the GUI-based installer does, the command line installer depends on which
cleanse engines you have licensed.
11.
Adapter Guide.
•
If you are using AddressDoctor:
•
backslash (\\) instead. Press Enter.
The Configure AddressDoctor Preload information is displayed.
•
Specify the AddressDoctor preload parameters. Press Enter.
The Choose AddressDoctor Database Path information is displayed.
•
Choose the AddressDoctor database path. Press Enter.
The Deploy screen provides the option to run the postInstallSetup script now
or run it manually later.
a.
b.
If you want to change any of the information in the pre-installation summary,
type BACK to go to a specific screen of information and make changes.
The Informatica Cleanse Match Server will be installed according to the
configuration information you supplied. When the process is complete, the
Install Complete information is displayed.
c.
12.
Check the following files, which are useful for troubleshooting any Cleanse Match
Server installation process, and for providing to Informatica Global Customer
Support (see “Informatica Global Customer Support” on page xvi).
File
Description
errors and status.
<MDM_Install_
<MDM_Install_
<MDM_Install_Directory>/hub/cleanse/informatica_
installer_debug.txt
installation.
<MDM_Install_
231
File
Description
Application server log files.
You can run a “silent install” from the command line for both Hub Server and the
Cleanse Match Server installation. With silent installation, you will not see any of the
screens or messages associated with the installation. You might want to use a silent
install if you are performing multiple installs, or if you are installing on a machine
cluster. Silent installation can be run on either UNIX or Windows systems.
Considerations When Using Silent Installation
The silent install is not interactive—it is truly silent. Therefore, you will not see any
screens, progress messages, or failure messages, even if the silent installation fails
during installation.
The silent install does not validate your settings. The silent installation process might
complete successfully even if you have provided incorrect settings, such as the wrong
application server path or an incorrect port setting. Such problems might become
known only after completing the silent installation, when you attempt to run
Informatica MDM Hub.
Linux. Instead, create and use a separate user profile for installing the Informatica
MDM Hub. This is a limitation of InstallAnywhere, as the root user does not have a
.profile to setup environment variables during installation.
Properties Files for Silent Installation
To run a silent install, you need to create two silent properties files—one for the Hub
Server and one for the Cleanse Match Server. There are sample silent properties files
located in the Informatica distribution directory in the following location:
Component
Location
Hub Server
<MDM_Install_Directory>/silent_install/mrmserver
<MDM_Install_Directory>/silent_install/mrmcleanse
Cleanse
Match Server
Start with these sample files and modify them according to your environment.
Important: In the silent properties file, backslashes (\)and foreslashes (/) are special
characters, so you must enter two of each when you enter information in this file, such
as when you enter an installation path. For example, to enter the path to the cleanse
directory (\u1\infamdm\hub\cleanse), you must enter:
\\u1\\infamdm\\hub\\cleanse.
Creating Your Properties File
Important: Because the silent installer does not validate the settings in your properties
files, be sure to specify the correct settings and verify them before you run the silent
installer.
Create two silent properties files:
Component
Property File Name
Hub Server
silentInstallServer_sample.properties
silentInstallCleanse_sample.properties
You can rename these files and they can be located anywhere in the machine.
233
Properties File for Hub Server
The following tables contain the properties to be set for Hub Server silent install.
Install Directory and License Properties
Set the following properties for the install directory, license path and filename:
Property
Value
INSTALLER_UI
silent
USER_INSTALL_DIR
Directory to install Hub Server. Example:
<MDM_Install_
Directory>//hub//server
SIP.LICENSE.PATH
Path to your Informatica license file
SIP.LICENSE.FILENAME
License filename (siperian.license)
Application Server Properties
Set properties for only one application server: WebSphere.
WebSphere Properties
Property
Value
SIP.AS.CHOICE
Application server name: “WebSphere”
SIP.AS.HOME
Path to WebSphere home. Example:
//WebSphere//AppServer
SIP.AS.Server
Server name Example: server1
SIP.AS.PORT_2
Port 2 (RMI port). Example: 2809
SIP.AS.PORT_3
Port 3 (SOAP port). Example: 8880
Database Properties
Set properties for only one database server: DB2.
DB2 Properties
Property
Value
SIP.DB.CHOICE
Database server type. “DB2”
SIP.DB.SERVER
Database server name.
Example: localhost
SIP.DB.PORT
Database port.
Example: 50000
SIP.DB.SCHEMA_NAME
Database schema name:
Example: cmx_system
SIP.DB.USER
Database user name. Example: db2admin
SIP.DB.PASSWORD
Database password. Example: !!cmx!!
SIP.DB.URL
Connect URL to the DB2 Service. Specified
only if SIP.DB2.CONNECTION.TYPE is
"Service Name" and you want to use a Connect
URL that differs from the one constructed in
the database creation script. Otherwise, remove
this variable from the file.
PostInstallSetup Properties
If you want to run postInstallSetup as part of a silent install, set this property:
Property
Value
RUN_DEPLOYMENTSETUP
Set this to “Yes” if you want to run
postInstallSetup. Set to “No” if you do not
want to run postInstallSetup at the end of the
install.
Properties File for Cleanse Match Server
The following tables contain the properties to be set for Cleanse Match Server silent
install properties file.
235
Set these install directory, license path, and filename properties:
Property
Value
INSTALLER_UI
silent
USER_INSTALL_DIR
Directory to install Cleanse Match Server.
Example: <MDM_Install_
Directory>//hub//cleanse.
SIP.LICENSE.PATH
Path to your Informatica license file
SIP.LICENSE.FILENAME
License filename (siperian.license)
Application Server Properties
Set properties for only one application server: JBoss or WebSphere.
JBoss Properties
Property
Value
SIP.AS.CHOICE
Application server name: “JBoss”
SIP.AS.HOME
Path to JBoss home
JBOSS.AS.PORT_1
Your JBoss port number. Example: 1099
SIP.JBOSS.CONFIGURATION_NAME
Configuration name. Default is production.
WebSphere Properties
Property
Value
SIP.AS.CHOICE
Application server name: “WebSphere”
SIP.AS.HOME
Path to WebSphere home
Example:
C\:\\Program
Files\\WebSphere\\AppServer
SIP.AS.SERVER
Application server name. Example: server1
SIP.WEBSPHERE.SOAP.PORT
Port used for SOAP services.
Example: 8880
Property
Value
SIP.WEBSPHERE.SECURITY.ENABLED If SIP.WEBSPHERE.SECURITY.ENABLED
is 'Yes', following two properties need to be set
SIP.APPSERVER.USERNAME=username
SIP.APPSERVER.PASSWORD=password
Operating Systems
If the operating system (OS) for the installation is Linux, then one of the OS choices
must be uncommented in the properties file. Remove the pound sign (#) in front of
the property to uncomment it.
Property
Value
SIP.OS.CHOICE=Red Hat Linux
Uncomment to use Red Hat Linux
SIP.OS.CHOICE=Suse Linux
Uncomment to use SUSE Linux
Cleanse Engine Properties
Set the properties for the cleanse engine you will be using with the Informatica Cleanse
Match Server.
AddressDoctor Cleanse Engine Properties
Property
Value
SIP.ADDRESSDOCTOR.UNLOCKCODE
Your AddressDoctor Cleanse Engine
unlock code.
SIP.ADDRESSDOCTOR.OPTIMIZATION
AddressDoctor Cleanse Engine
optimization setting. Example: ADDRESSES_
SORTED_BY_COUNTRIES
SIP.ADDRESSDOCTOR.MEMORYMB
AddressDoctor Cleanse Engine memory
allocation. Example: 600
SIP.ADDRESSDOCTOR.VALIDATIONTYPE
AddressDoctor Cleanse Engine validation
type. Example: CORRECT_ONLY
SIP.ADDRESSDOCTOR.PRELOAD.PART
AddressDoctor Cleanse Engine preload part
setting. Example: US
237
Property
Value
SIP.ADDRESSDOCTOR.PRELOAD.FULL
AddressDoctor Cleanse Engine preload full
setting.
SIP.ADDRESSDOCTOR.PRELOAD.CORREC AddressDoctor Cleanse Engine preload
TIONPART
correction setting part. Example: CA, US
SIP.ADDRESSDOCTOR.PRELOAD.CORREC AddressDoctor Cleanse
TIONFULL
correction setting full.
SIP.ADDRESSDOCTOR.DBPATH
Engine preload
Path to AddressDoctor Cleanse Engine
database. Example:
//home//db2//infamdm//addressdoctor
PostInstallSetup Properties
If you want to run postInstallSetup as part of a silent install, set this property:
Property
Value
RUN_DEPLOYMENTSETUP
Set to one of the following values:
•
•
“Yes” if you want to run postInstallSetup.
“No” if you do not want to run
postInstallSetup at the end of the install.
Restarting Your Operating System
To restart your operating system as a part of the silent install, change the value for
these properties:
Property
Value
RESTART_NEEDED
One of the following values:
•
•
USER_REQUESTED_RESTART
One of the following values:
•
•
YES to restart.
NO (default) if you do not want to restart.
YES to restart.
NO (default) if you do not want to restart.
Running the Silent Install
Once you have created the properties files for the Hub Server and Cleanse Match
Server, you can run the silent install.
To run the silent installs:
2.
For the Hub Server install, run the following command from the command
prompt:
./hub_install.bin -f
hub_server>
3.
<location_of_silent_properties_file_for_
For the Cleanse Match Server, run the following command from the command
prompt:
./hub_cleanse_install.bin -f
file_for_cleanse_server>
4.
<location_of_silent_properties_
After installation, check the postInstallSetup.log file to see if the installation
was successful.
•
If you set the RUN_DEPLOYMENTSETUP property to No, check for the existence
of the <MDM_Install_Directory>/logs/postInstall.log file.
•
If you set the RUN_DEPLOYMENTSETUP property to Yes, you can check to see
that <MDM_Install_Directory/logs/postInstallSetup.log has BUILD
SUCCESSFUL (or failure if the install was not successful) at the end of the
log file.
239
Manually Configuring Informatica System
Message Queues
This appendix covers the steps for manually configuring JMS message queues and
connection factories.
Note: Normally, message queues and connection factories are created automatically
during the installation process. These instructions are for troubleshooting purposes if,
for example, the automated queue creation process failed or if the queues were
dropped accidentally after the installation.
Chapter Contents
•
About Informatica MDM Hub Message Queues
•
Configuring Message Queues (JBoss/UNIX)
•
Configuring Message Queues (WebSphere/UNIX)
•
Configure Message Queues (JBoss/Windows)
•
Configure Message Queues (WebSphere/Windows)
Manually Configuring Informatica System Message Queues
241
The Services Integration Framework (SIF) uses a message-driven bean (MDB) on the
JMS queue (named siperian.sif.jms.queue) to process incoming asynchronous
SIF requests. This message queue and the connection factory (named
siperian.mrm.jms.xaconnectionfactory) need to be configured for the specific
application server you are using for your Informatica MDM Hub implementation.
Correctly configuring your message queues is essential to a fully-functioning
Informatica MDM Hub installation. The Informatica MDM Hub installer
automatically configures your message queues during installation.
The JMS message queues are automatically configured by the Informatica installer. To
verify that JMS messages queues have been configured correctly., check the JMS
configuration under <JBoss_install_dir>/server/<configuration_
name>/deploy/messaging. In the siperian-jms-ds.xml file, you should find
siperian.mrm.jms.xaconnectionfactory (the XA connection factory), and in
siperian-destinations-service.xml file, you should find the file
siperian.sif.jms.queue.
The JBoss server is manually configured for Informatica by editing the
siperian-destinations-service.xml file to add the message queues and
connection factories.
Creating and Configuring a New Message Queue
To configure the message queues and connection factories:
1. Open the jboss/server/<configuration_
name>/deploy/messaging/siperian-destinations-service.xml
file in an
editor.
Add the following queue declaration:
<mbean code="org.jboss.mq.server.jmx.Queue"
2.
name="jboss.mq.destination:service=Queue,name=siperian.sif.jms.qu
eue">
<depends optional-attribute-name="DestinationManager">
jboss.mq:service=DestinationManager
</depends>
</mbean>
Open the jboss/server/<configuration_name>/deploy/jms/jms-ds.xml
file in an editor.
3.
Add the following declaration for a JMS connection factory (XA enabled).
<tx-connection-factory>
<jndi-name>siperian.mrm.jms.xaconnectionfactory</jndi-name>
<xa-transaction/>
<rar-name>jms-ra.rar</rar-name>
<connection-definition>
org.jboss.resource.adapter.jms.JmsConnectionFactory
</connection-definition>
<config-property name="SessionDefaultType"
type="java.lang.String">
javax.jms.Topic
</config-property>
<config-property name="JmsProviderAdapterJNDI"
java:/DefaultJMSProvider
</config-property>
<max-pool-size>20</max-pool-size>
<security-domain-and-application>JmsXARealm</security-domain-andapplication>
</tx-connection-factory>
243
The JBoss JMS message queues and connection factory are now configured.
Configuring Additional Message Queues
The following steps enable you to set up message queues for testing. This is also an
example of how to step additional queues. These steps are optional.
To configure a test message queue
1. Open the jboss/server/<configuration_
name>/deploy/messaging/siperian-destinations-service.xml
file in an
editor.
2.
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=siperian.sif
.test.jms.queue"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends
optional-attribute-name="ServerPeer">jboss.messaging:service=Serv
erPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
</mbean>
<mbean code="org.jboss.jms.server.destination.TopicService"
name="jboss.messaging.destination:service=Topic,name=siperian.sif
.test.jms.topic"
xmbean-dd="xmdesc/Topic-xmbean.xml">
<depends
erPeer</depends>
</mbean>
Note: This configuration is needed only for testing purposes.
Manually configure the WebSphere 6.1 application server by creating a new connection
factory and message queues.
Follow these steps to create a new message queue.
Create and Configure a New Bus in the WebSphere Server
1.
In the WebSphere Console, go to Service integration > Buses.
Create a new bus with name “SiperianBus” and save the change.
2.
Go to the SiperianBus you just created and click Bus Members.
Add a new member in the Server drop-down list.
3.
Choose the server on which your application is running.
Click Next and select Data Store.
Click Next under this and make sure the Create default data source with
generated JNDI name is checked.
4.
Click Next, then click Finish. Save the change.
5.
Go to the SiperianBus you just created and click Destination.
Click New and choose the Queue as destination type. Click Next.
6.
Use the name “SiperianQueue” as the Identifier and click Next.
Choose the Bus member you just created and click Next.
7.
Click Finish. Save the change.
Configure a New Connection Factory
1.
In the WebSphere Console go to Resources > JMS > JMS Providers.
Select “Node=<servername>Node01” from the drop-down list.
Choose Default messaging provider.
245
2.
3.
Click JMS queue connection factory. Configure a new JMS connection factory
using “siperian.mrm.jms.xaconnectionfactory” for both the name and the
JNDI name.
Choose the “SiperianBus” as the Bus name for the JMS connection factory.
Save the change.
4.
Click on Queues.
Select the scope “Node=<servername>Node01” from the drop-down list.
Configure a new JMS queue
1.
Click on the New button.
Select Default messaging provider and click OK.
Use “siperian.sif.jms.queue”for both the name and the JNDI name.
Choose the “SiperianBus” as Bus name, choose the “SiperianQueue” you
created as Queue name. Save the change.
2.
Click on JMS activation specification. Select the scope
“Node=<servername>Node01” from drop-down list.
3.
Configure a new Informatica Activation.
Click New. Use “SiperianActivation” for both the name and the JNDI name.
Choose Queue as the Destination type and “siperian.sif.jms.queue” as the
Destination JNDI name. Choose “SiperianBus” as Bus name. Save the change.
The following steps set up message queues for testing. This is also an example of how
to step additional queues. These steps are optional.
Create the Test Message Queue
1. In the WebSphere Console, go to Service integration > Buses.
Select the SiperianBus and click Destination.
2.
3.
Use the name “SiperianTestQueue” as the Identifier and click Next.
4.
Choose the Bus member and click Next.
Click Finish and save the change.
Configure the Test Message Queue
In the WebSphere Console, go to Resources > JMS Providers > Default
Messaging.
1.
Click on Queue and configure a new JMS queue using
“siperian.sif.test.jms.queue” for the both name and the JNDI name.
2.
Choose “SiperianBus” as Bus name. Choose the “SiperianTestQueue” you just
created as the Queue name.
247
The Informatica System message queues are automatically configured by the
Informatica installer. To verify that the Informatica System messages queues have been
configured correctly., check the JMS configuration under <JBoss_install_
dir>\server\<configuration_name>\deploy\messaging. In the file
siperian-jms-ds.xml you should find siperian.mrm.jms.xaconnectionfactory
(the XA connection factory) and in siperian-destinations-service.xml you
should find the file siperian.sif.jms.queue.
The JBoss application server is manually configured for Informatica by editing the
file to add the Informatica System message
queues and connection factories.
siperian-destinations-service.xml
To configure the Informatica System message queues and
connection factories
1. Open the jboss\server\<configuration_
name>\deploy\jms\siperian-destinations-service.xml file in an editor.
2.
3.
name="jboss.messaging.destination:service=Queue,name=siperian.sif
.jms.queue"
<depends
erPeer</depends>
</mbean>
Open the jboss\server\<configuration_
name>\deploy\messaging\siperian-jms-ds.xml file in an editor.
Add the following declaration for a JMS connection factory (XA enabled).
<tx-connection-factory>
<jndi-name>siperian.mrm.jms.xaconnectionfactory</jndi-name>
<xa-transaction/>
<rar-name>jms-ra.rar</rar-name>
<connection-definition>
org.jboss.resource.adapter.jms.JmsConnectionFactory
</connection-definition>
<config-property name="SessionDefaultType"
javax.jms.Topic
</config-property>
<config-property name="JmsProviderAdapterJNDI"
java:/DefaultJMSProvider
</config-property>
<max-pool-size>20</max-pool-size>
<security-domain-and-application>JmsXARealm</security-domain-andapplication>
</tx-connection-factory>
The JBoss Informatica System message queues and connection factory are now
configured.
249
The following steps enable you to set up Informatica System message queues for
testing. This is also an example of how to step additional queues. These steps are
optional.
To configure a test message queue:
1. Open the file jboss\server\<configuration_
name>\deploy\messaging\siperian-destinations-service.xml
in an
editor.
2.
name="jboss.messaging.destination:service=Queue,name=siperian.si
f.test.jms.queue"
<depends
optional-attribute-name="ServerPeer">jboss.messaging:service=Ser
verPeer</depends>
</mbean>
<mbean code="org.jboss.jms.server.destination.TopicService"
name="jboss.messaging.destination:service=Topic,name=siperian.si
f.test.jms.topic"
xmbean-dd="xmdesc/Topic-xmbean.xml">
<depends
optional-attribute-name="ServerPeer">jboss.messaging:service=Ser
verPeer</depends>
</mbean>
Manually configure the WebSphere 6.1 application server by creating a new connection
factory and message queues.
This section describes how to create and configure a new message queue.
Create and Configure a New Bus
1.
Create a new bus with name “SiperianBus” and save the change.
2.
Go to the SiperianBus you just created and click Bus Members.
Add a new member in the Server drop-down list.
3.
Choose the server your application is running.
Click Next and select Data Store.
Click Next under this and make sure the Create default data source with
generated JNDI name is checked.
4.
Click Next, then click Finish. Save the change.
5.
Go to the SiperianBus you just created and click Destination.
6.
Use the name “SiperianQueue” as the Identifier and click Next.
Choose the Bus member you just created and click Next.
7.
Click Finish. Save the change.
Configure a New Connection Factory
1.
In the WebSphere Console go to Resources > JMS > JMS Providers.
Select “Node=<servername>Node01” from the drop-down list.
Choose Default messaging provider.
251
2.
Click JMS queue connection factory. Configure a new JMS connection factory
using “siperian.mrm.jms.xaconnectionfactory” for both the name and the
JNDI name.
3.
Choose the “SiperianBus” as the Bus name for the JMS connection factory.
Save the change.
4.
Click on Queues.
Select the scope “Node=<servername>Node01” from the drop-down list.
Configure a New JMS Queue
1.
Click on the New button.
Select Default messaging provider and click OK.
Use “siperian.sif.jms.queue”for both the name and the JNDI name.
Choose the “SiperianBus” as Bus name, choose the “SiperianQueue” you
created as Queue name. Save the change.
2.
Click on JMS activation specification. Select the scope
“Node=<servername>Node01” from drop-down list.
3.
Configure a new Informatica Activation.
Click New. Use “SiperianActivation” for both the name and the JNDI name.
Choose Queue as the Destination type and “siperian.sif.jms.queue” as the
Destination JNDI name. Choose “SiperianBus” as Bus name. Save the change.
The following steps set up message queues for testing. This is also an example of how
to step additional queues. These steps are optional.
Create the Test Message Queue
1.
Select the SiperianBus and click Destination.
2.
Click New and choose the Queue as destination type then click Next.
3.
Use the name “SiperianTestQueue” as the Identifier and click Next.
4.
Choose the Bus member and click Next.
Click Finish and save the change.
Configure the Test Message Queue
1.
In the WebSphere Console, go to Resources > JMS Providers > Default
Messaging.
Click on Queue and configure a new JMS queue using
“siperian.sif.test.jms.queue” for the both name and the JNDI name.
2.
Choose “SiperianBus” as Bus name. Choose the “SiperianTestQueue” you just
created as the Queue name.
253
Manually Creating Datasources
This appendix covers the steps for manually creating datasources for the Informatica
MDM Hub.
Chapter Contents
•
Informatica MDM Hub Datasources
•
Manually Creating Datasources in Websphere 6.1.0.29
Manually Creating Datasources 255
Normally, datasources are created automatically during the installation process. The
instructions for manually creating datasources are here for troubleshooting purposes.
If, for example, the automated queue creation process failed or if for some other
reason you need to manually create your datasources.
Manually Creating Datasources in Websphere
6.1.0.29
To manually create datasources for the WebSphere application server, follow the steps
in this section.
• Start the application server
•
Specify the location of the driver libraries
•
Create a security account
•
Create a JDBC provider
•
Create a Master datasource
Start the WebSphere Application Server
To start the WebSphere application server:
1. Start the WebSphere application server.
2.
Start the WebSphere Application Server Admin Console.
3.
Specifying the Location of the Driver Libraries
To specify the location of the driver libraries:
1. In the console navigation tree, select Environment > WebSphere Variables.
2.
Update the DB2_UNIVERSAL_JDBC_DRIVER_PATH variable to point to the
JDBC driver location (for example, /WAS61028/AppServer/lib).
Creating the Security Account
To create the security account to be used by the ORS datasource:
1. In the console navigation tree, select Security>Global
2.
Expand JAAS Configuration under Authentication on the right side of the
console.
3.
To create a new security account, click New.
4.
Set the new security account parameters as follows:
Alias = CMX_SYSTEM
Password = <db2_password>
Note: Do not change the username (User ID).
For information about how to change the above parameters, see “Changing the CMX_
ORS User Password” on page 258.
5. Click OK to save this information.
Creating the JDBC Provider
To create the JDBC provider for the ORS datasource:
1. In the console navigation tree, select Resources > JDBC Providers.
2.
Ensure that the scope is set to Node. (Change and apply if this needs to be
changed).
3.
To create a new JDBC provider, click New.
4.
•
Select “DB2” from the database type list.
•
Select “DB2 JDBC Driver” for the provider type.
•
Select “XA datasource” from the implementation type list.
Click Next.
Change the provider name to “Informatica DB2 JDBC Provider (XA)”.
Manually Creating Datasources 257
5.
Click OK to save.
Creating the Master Datasource
To create the master datasource:
1. Click the created provider.
2.
Select Additional Properties > Data Sources.
3.
To create the new datasource, click New.
4.
Configure the new datasource as follows:
Name = MDM Master Data Source
Component-managed Authentication Alias = <hostname>/cmx_system
5. Click OK to save.
Changing the CMX_ORS User Password
CMX_ORS. If you do so, you must also:
• change the password for the CMX_ORS user in DB2
•
set the same password in the datasource on the application server
•
register the schema with the same username and password
A
application server 36
audience xi
C
changing
application server and RMI port number
JBoss 209
about 88
application server instances, configuring
multiple 104, 125, 142, 161
cmxcleanse.properties file 138, 156
cmxserver.log 187, 190
configuration settings 101, 121, 139, 157
deploying 143, 162
manually 143, 162
deploying manually 105, 126
deploying on second application server
instance 105, 125
dual cleanse servers 104, 124, 142, 160
logging settings 101, 121, 139, 157
multiple, configuring 106, 126
multi-threading, configuring 102, 122,
140, 159
parameters, updating 192
post-installation 88
temporary files, deleting 101, 121, 139,
157
version and build number 62, 85, 100,
120, 138, 156
Cleanse Server
silent install, troubleshooting 194, 197
cmx_debug.log 190
cmx_debug.log file 187, 190
CMX_ORS User
changing username and password 152
cmxcleanse.properties file 138, 156
cmxserver.log file 45, 59, 70, 82, 187, 223,
229
command line installation
about 220
configuring cleanse engines 138, 156
configuring dual cleanse servers 142, 160
connection factory
configuring new 251
connection pooling 36
console.log file 186, 189
contents xii
customer support xvi
D
database
changing instance name 207, 216
changing server name 206, 214
server and instance name, JBoss 210
databases
connection testing 29
target database 168
debug log file, enabling 188, 190
documentation
audience xi
contents xii
other documentation xiv
259
H
Hub Console
about the Hub Console 166
starting 167
target database
selecting 168
Hub Server
about Hub Server 36
application server 36
configuration properties 46, 60, 71, 83
connection pooling 36
database parameters, updating 214
deploying manually 202
logging settings 46, 60, 71, 83
parameters, updating 191
silent install, troubleshooting 193, 196
Hub Store
about the Hub Store 12
database configuration options 12
installing 14
Master Database 12
Operational Record Store (ORS) 12
ORS database, creating 30
tablespaces, creating 24
I
infamdm_installer_debug.txt file 45, 59, 70,
82, 223, 229
Informatica MDM Hub
documentation xiv
log files 186, 189
Informatica, contacting xvi
installation
silent 232
installing
Hub Store 14
overview of 3
J
JBoss
changing Application Server and RMI
port number 201
changing database server and instance
name 210
changing settings 72
Cleanse Match Server and Hub Server,
configuring 93
Cleanse Match Server, configuring 132
Hub Server
changing parameters 209
parameters, updating 201, 209
port conflicts 72
settings 47, 72
JBoss Hub Server, configuring 132
L
license file 39, 50, 64, 75, 91, 109, 130, 147,
220
log files
cmx_debug.log file 187
cmxserver.log file 45, 59, 70, 82, 187,
223, 229
console.log file 186
infamdm_installer_debug.txt file 45, 59,
70, 82, 223, 229
Informatica_MDM_Hub_Server_Install-
Log.xml file 45, 59, 70, 82, 223,
229
location, changing 188
maintaining 188
overview of 186
postInstallSetup.log file 45, 59, 70, 82,
223, 229
setup_ors.log file 31, 32, 33
M
Master Database 12
Master Reference Manager
cmxserver.log 187, 189
match process error
VerifyNeedToStrip 199
message queues
configuring additional
JBoss 250
WebSphere 253
using 241, 255
O
Operational Record Stores (ORS)
about ORSs 12
ORS database
creating additional 30
P
password
changing for CMX_SYSTEM user 150
port conflicts 72
postInstallSetup.log file 45, 59, 70, 82, 223,
229
S
Services Integration Framework Guide (SIF)
xv
setup_ors.log file 31, 32, 33
silent install
Cleanse Server, troubleshooting 194, 197
Hub Server, troubleshooting 193, 196
troubleshooting 193, 196
silent install, from command line 232
silent installation 232
support xvi
T
tablespaces
creating 24
temporary tablespace 32
target database
selecting 168
technical support xvi
troubleshooting
cmxserver.log file 189, 190
log files
cmx_debug.log file 190
cmxserver.log file 189, 190
console.log file 189
overview of 189
silent install 193, 196
silent install, Cleanse Server 194, 197
silent install, Hub Server 193, 196
261
V
VerifyNeedToStrip error message 199
version and build number
checking 138, 156
W
WebSphere
changing Hub Server parameters 213
changing settings 84
Hub Server
parameters, updating 204, 213
settings 61, 84
WebSphere 6.1
configure a new JMS queue 252

Installing the Cleanse Match Server - Knowledge Base

Transcription

Similar documents

creating a tax return

Workshop 1 - Nissan 4x4 Owners Club

the Fortec Brochure

Rejseplanen as a datahub - Nordic Public Transport

Standard— The easiest way to get a Swift is to order it

Installing ANSYS 15 Mount the iso files using Virtual Clone

www.livorsi.com/auto Quick Release Billet Hub Adapter Kit

Flo-Torq Reflex