infosphere mdm collaboration server: installation guide · iv infosphere mdm collaboration server:...

IBM InfoSphere Master Data Management CollaborationServer

Installation GuideVersion 10 Release 0

GC19-3497-00

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 99.

Edition notice

This edition applies to version 10, release 0, modification 0 of IBM InfoSphere Master Data ManagementCollaboration Server (program number 5724-V51) and to all subsequent releases and modifications until otherwiseindicated in new editions.

© Copyright IBM Corporation 2000, 2011.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Preface . . . . . . . . . . . . . . . vWhat's new in Version 10.0? . . . . . . . . . vContacting IBM Software Support . . . . . . . vi

Chapter 1. Installing . . . . . . . . . 1Installation requirements . . . . . . . . . . 1

Hardware requirements. . . . . . . . . . 1Software requirements . . . . . . . . . . 2Installing Perl . . . . . . . . . . . . . 2

Chapter 2. Product overview . . . . . . 9System architecture . . . . . . . . . . . . 9Information flow . . . . . . . . . . . . 10Product services . . . . . . . . . . . . . 11Installation scenarios . . . . . . . . . . . 11Performance planning . . . . . . . . . . . 13

Chapter 3. Installing and setting up thedatabase . . . . . . . . . . . . . . 15Setting up your DB2 database . . . . . . . . 15

Guidelines for setting up a DB2 database . . . 15Creating the DB2 instance . . . . . . . . 19Creating the DB2 database . . . . . . . . 19Creating buffer pools . . . . . . . . . . 19Creating table spaces . . . . . . . . . . 20Adding database users and granting permissions 22DB2 configurations . . . . . . . . . . . 23Setting up the DB2 client on InfoSphere MDMCollaboration Server . . . . . . . . . . 31IBM DB2 database setup checklist . . . . . . 32

Setting up your Oracle database . . . . . . . 33Updating operating system settings for Oracle. . 33Disk considerations for the database . . . . . 33Creating a new database . . . . . . . . . 34Oracle setup for high availability . . . . . . 34Oracle parameter file settings . . . . . . . 36Creating table spaces . . . . . . . . . . 37Setting up transaction logs . . . . . . . . 39Creating database schema users . . . . . . 40Setting up Oracle on the application server . . . 40Installing Oracle XML DB component . . . . 41Oracle setup checklist . . . . . . . . . . 42

Chapter 4. Installing and setting up theapplication server . . . . . . . . . . 43Exporting and importing LTPA tokens between WASdomains . . . . . . . . . . . . . . . 43Setting up WebSphere Application Server . . . . 43Setting up WebLogic Server . . . . . . . . . 44

Chapter 5. Installing the product. . . . 45Installation checklist worksheet . . . . . . . . 45Default port numbers . . . . . . . . . . . 47Preparing to install the product. . . . . . . . 48

Setting up the installation media . . . . . . . 49Installing the product silently using a response file 49Sample basic response file . . . . . . . . . 50Installing the product using the wizard . . . . . 51

Chapter 6. Configuring the product . . 55Setting the environment variables . . . . . . . 55Creating the env_settings.ini file . . . . . . . 56

Setting the common parameters in theenv_settings.ini file . . . . . . . . . . . 56Configuring cache parameters . . . . . . . 56Setting the common database parameters . . . 57Storing database passwords in an encryptedformat . . . . . . . . . . . . . . . 57Setting DB2 parameters . . . . . . . . . 58Setting Oracle parameters . . . . . . . . 60Configuring the application server parameters. . 62Configuring WebSphere MQ parameters . . . . 65

Validate the environment . . . . . . . . . . 66Configure the installation. . . . . . . . . . 66Using the compatibility scripts . . . . . . . . 67Configuring the application server. . . . . . . 67

Configuring WebSphere Application Server . . . 67Configuring Oracle WebLogic Server . . . . . 68

Deploying the product in a cluster environment . . 71Overview of clustering and workloadmanagement . . . . . . . . . . . . . 71Deploying InfoSphere MDM Collaboration Serverusing WebSphere Application Server DeploymentManager . . . . . . . . . . . . . . 72

Configuring runtime properties. . . . . . . . 74Running schema creation scripts . . . . . . . 74

Creating a schema . . . . . . . . . . . 75Error handling for table space name mapping file 78

Configuring GDS feature . . . . . . . . . . 79Creating a .bindings file for Windows . . . . 79Setting Global Data Synchronization parameters 81Configuring Global Data Synchronizationmemory parameters for messaging . . . . . 83Setting up an AS2 connector . . . . . . . . 83Connecting to a data pool . . . . . . . . 84

Chapter 7. Verifying the installation . . 85Post-installation checklist . . . . . . . . . . 85Setting up a test company using a script. . . . . 86Loading Global Data Synchronization data model 86Starting the product . . . . . . . . . . . 87Logging in to the product . . . . . . . . . 88Logging in to Global Data Synchronization . . . . 88Configuring the product using the Firststepsapplication . . . . . . . . . . . . . . 89Stopping the product . . . . . . . . . . . 89

Chapter 8. Troubleshooting theinstallation program . . . . . . . . . 91

© Copyright IBM Corp. 2000, 2011 iii

Chapter 9. Uninstalling the product . . 95Uninstalling the product silently using a responsefile . . . . . . . . . . . . . . . . . 95Uninstalling the product using the wizard . . . . 95Uninstalling the product using text mode . . . . 96

Chapter 10. Installing IBM SoftwareAssistant. . . . . . . . . . . . . . 97

Notices . . . . . . . . . . . . . . 99Trademarks . . . . . . . . . . . . . . 101

Index . . . . . . . . . . . . . . . 103

iv InfoSphere MDM Collaboration Server: Installation Guide

Preface

IBM® InfoSphere® Master Data Management Collaboration Server is a productinformation management solution for building a consistent central repository. Itlinks product, location, trading partner, organization, and terms of tradeinformation, which is typically scattered throughout the enterprise.

About this publication

This installation guide provides information about how to install and configureInfoSphere MDM Collaboration Server.

Intended audience

This installation guide is intended for installers, system administrators, and IBMProfessional Services personnel to successfully deploy the product in yourenvironment.

Prerequisite and related information

Before using this installation guide, become familiar with the followinginformation:v InfoSphere MDM Collaboration Server information centerv Your application server documentationv Your database software documentation

How to send your comments

Your feedback is important in helping to provide the most accurate andhigh-quality information. If you have any comments about this book or anyotherInfoSphere MDM Collaboration Server documentation, use the following formto send us your comments:

http://www.ibm.com/software/data/rcf/

What's new in Version 10.0?There are many new features and functions in IBM InfoSphere Master DataManagement Collaboration Server Version 10.0.

InfoSphere MDM Collaboration Server is included in InfoSphere MDM EnterpriseEdition and InfoSphere MDM Collaborative Edition.

InfoSphere MDM Collaboration Server enables companies to create a single,up-to-date repository of product information that can be used throughout theirorganization for strategic business initiatives.

Key changes to the product include:

Content Management Solution integrationAttribute Value Synchronization between InfoSphere MDM Collaboration

© Copyright IBM Corp. 2000, 2011 v

Server and Content Management Solution Integration. See Contentmanagement configuration files for more information.

Administration enhancementsSystem administration enhancements and serviceability enhancements forlog collecting. See Log files for more information.

Performance best practicesIdentified best practices from enhancing good performance. See Enhancinggood performance for more information.

Migration support for InfoSphere MDM Collaboration Server users

v Migrating from V5.3.2, Fix Pack 18 to V10.0.0v Migrating from V6.0.0, Fix Pack 11 to V10.0.0v Migrating from V9.0.0, Fix Pack 7 to V10.0.0v Migrating from V9.1.0, Fix Pack 1 to V10.0.0

Migration support for Global Data Synchronization users

v Migration from Global Data Synchronization version 1.3.x to InfoSphereMDM Collaboration Server version 10.0

Invoking Java API from scriptingThe following tasks are documented to support the use of the Java API:v How to obtain access to the current context in the Java API code when

invoked from scripting.v How to pass arguments and obtain return values, including any

restrictions on what type of arguments can be passed and returned.v All other special considerations and restrictions to be aware of.v Lists of example code.

Contacting IBM Software SupportIBM Software Support provides assistance with product defects, answering FAQs,and performing rediscovery.

Before you begin

After trying to find your answer or solution by using other self-help options suchas technotes, you can contact IBM Support. Before contacting IBM Support, yourcompany must have an active IBM maintenance contract, and you must beauthorized to submit problems to IBM. For information about the types ofavailable support, see the Support portfolio topic in the Software Support Handbook.

When contacting IBM Software Support it is important to understand whatsupport is available through IBM:v Specific product questions: If you have been trained on the product, you can

submit specific questions or concerns.v Defect support: The analysis and necessary work required to resolve a product

defect or provide a workaround.v Script operations: For questions regarding a script operation or for reporting a

possible defect with a script operation, you must simplify your question orproblem to approximately 5 lines of code or less.– IBM does not provide support for debugging and analysis of custom scripts.

v Enhancement requests: Requests for new functionality added to the product.

vi InfoSphere MDM Collaboration Server: Installation Guide

http://www14.software.ibm.com/webapp/set2/sas/f/handbook/offerings.html

Requests that are not within the scope of IBM Software Support and require you tocontact either your Sales or Professional Services representative:v Miscellaneous work: Work or assistance that requires extensive IBM involvement

during installation or the implementation process which includes complexinstallations or installation across multiple platforms.

v Support for untrained customers: Requests for step by step IBM help but do nothave the required IBM product training. IBM Education offers customer trainingif additional staff training is needed. Check the IBM Web site for specificinformation about available courses.

v Custom scripts or scripting: No support is provided for scripts that you havewritten or require debugging. All customized scripts written by ProfessionalServices become owned and maintained by you, the customer, after Service'swork has been completed. Technical Support is not available for writing ordebugging custom scripts.

v Data recovery: We strongly advise you to routinely backup your data.v Performance or tuning assistance or recommendations that require customer

data.

Procedure1. Determine if a technote already exists regarding your issue. For additional

information on viewing technotes, see Searching knowledge bases.2. Determine whether a peer or your internal support team can provide

assistance.3. Define the problem, gather background information, and determine the severity

of the problem. For help, see the “Before contacting IBM Software Support” inthe Software Support Handbook.

Required background information

v All configuration settings and information.v The expected behavior versus what the current behavior is.v All changes or modification that you have recently implemented.v Determine if the issue can be recreated.v Define the steps that lead to the issues you are experiencing.

4. Gather your diagnostic information:v You can also use the IBM Support Assistant basic data collection feature to

collect your critical log and configuration files, see www.ibm.com/software/support/isa/ for additional information.

v Create your own IBM Support Assistant Lite collector tool through theworkbench.a. Download the product add-on in the IBM Support Assistant workbench.b. Click Collect and Send Data. Three options display on the left.c. Choose ...Using IBM Support Assistant Lite.d. Create the generated collector by completing each of the collector options:

– Select a collector (if the installed product add-on does not display, itdoes not have a Must Gather document and cannot create an IBMSupport Assistant Lite collector)

– Specify the target directory– Specify the filename– Click the Export button

Preface vii

http://www14.software.ibm.com/webapp/set2/sas/f/handbook/getsupport.html#1

http://www.ibm.com/software/support/isa/

http://www.ibm.com/software/support/isa/

e. Transfer the exported IBM Support Assistant Lite collector to a remotesystem using ftp or any other available file transfer protocol.

f. Unzip the exported IBM Support Assistant Lite collector to your targetlocation.

g. Setup JAVA_HOME or ensure that Java™ is in your path statement.h. Run the runISALite.bat command for Windows or the runISALite.sh

script for UNIX and LINUX from the tools IBM Support Assistant Litedirectory on the remote system.

i. Provide the appropriate responses to any collection prompts.j. Review the collected files or send them to IBM support.

5. Submit your problem to IBM Software Support in one of the following ways:v Online: (Recommended)

a. Click Open service request given under the Choose your task section onthe left-side navigation bar of the IBM InfoSphere Master DataManagement Collaboration Server Support site.

b. Click ESR / SR and follow the instructions provided on the ESR Web site.Use the following guidelines and tips for using ESR and submittingPMRs:– Attach documents directly to the PMR to make them available to IBM

Support Services.– ESR manages a list of all PMRs that you have viewed so that you have

immediate access to them to check on their status.– Use ESR to set up automatic PMR notifications.– Send updates for PMR's that you open to IBM Support Services

directly from ESR.– When submitting a PMR you must indicate a severity level in order to

help us prioritize our resources with respect to other PMRs you open:

Severity 1Critical business impact: This indicates that you are unable touse the program resulting in a critical impact on operations.This condition requires an immediate solution.

Note: Critical business impact typically means that yourproduction system is down and in order for IBM SoftwareSupport to work outside of your business working hours, youmust ensure that you have a contact available by phone 24x7to facilitate inquiries by the investigating engineer, run tests inyour production instance, etc.

Severity 2Significant business impact: This indicates the program isusable but severely limited.

Severity 3Some business impact: This indicates the program is usablewith less significant features (not critical to operations)unavailable.

Severity 4Minimal business impact: This indicates the problem causeslittle impact on operations or that a reasonable circumventionto the problem has been implemented.

viii InfoSphere MDM Collaboration Server: Installation Guide

http://www.ibm.com/support/entry/portal/Overview/Software/Information_Management/InfoSphere_Master_Data_Management_Server_for_Product_Information_Management

– To open an Enhancement Request (a request for new general productfunctionality and is not related to a specific customization):- Open a PMR with severity 2, 3, or 4, (depending of the potential

business gain of the request) and the request is sent to IBM ProductManagement for review. You will receive an Enhancement Requestnumber for tracking purposes, which replaces the PMR number.Typically, your approval is required to close the PMR.

v By phone: For the phone number to call in your country, go to the Contactspage of the Software Support Handbook.

What to do next

If the problem you submit is for a software defect or for missing or inaccuratedocumentation, IBM Software Support creates an Authorized Program AnalysisReport (APAR). The APAR describes the problem in detail. Whenever possible,IBM Software Support provides a workaround that you can implement until theAPAR is resolved and a fix is delivered. IBM publishes resolved APARs on theIBM Support Web site daily, so that other users who experience the same problemcan benefit from the same resolution.

Preface ix

http://www.software.ibm.com/webapp/set2/sas/f/handbook/contacts.html

http://www.software.ibm.com/webapp/set2/sas/f/handbook/contacts.html

x InfoSphere MDM Collaboration Server: Installation Guide

Chapter 1. Installing

IBM InfoSphere Master Data Management Collaboration Server provides a highlyscalable enterprise Product Information Management (PIM) solution – middlewarethat establishes a single, integrated, consistent view of information about productsand services both inside and outside of an enterprise.

This installation information is also available in the InfoSphere MDM CollaborationServer Installation Guide, which is available in book format in a PDF file.Right-click on the link, and select Save Target As to download the PDF file to yourcomputer.

Translated versions of the InfoSphere MDM Collaboration Server Installation Guide canbe found on the IBM Publication Center.

Installation of the InfoSphere MDM Collaboration Server products requires thefollowing basic steps:v Chapter 3, “Installing and setting up the database,” on page 15v Chapter 4, “Installing and setting up the application server,” on page 43v Chapter 5, “Installing the product,” on page 45v Chapter 6, “Configuring the product,” on page 55v Chapter 7, “Verifying the installation,” on page 85

See How to install InfoSphere MDM Collaboration Server to watch an educationalvideo about the installation process.

The following sections describe the product and how to install and configure it toyour needs.

Installation requirementsBefore you can install IBM InfoSphere Master Data Management CollaborationServer, ensure that you have met all the hardware and software requirements, teamrequirements, and the application server and database configurations requirementsto run InfoSphere MDM Collaboration Server.

Machines hosting InfoSphere MDM Collaboration Server have to have a hostname. As defined in the common specifications, the length of a full specifieddomain name cannot exceed 255 characters. Each node within a domain name islimited to a length of 63 characters. Accordingly, a host name can have a maximumlength of 63 characters and cannot contain blanks.

InfoSphere MDM Collaboration Server is capable to run on a machine having ahost name with a length of 63 characters.

Hardware requirementsHardware requirements can vary greatly based on your data and yourenvironment.

When you run the installation program, it first checks your system to determine ifyou have enough hard disk space to successfully install the product.

© Copyright IBM Corp. 2000, 2011 1

http://publib.boulder.ibm.com/infocenter/ieduasst/imv1r0/topic/com.ibm.iea.mdmcs/mdmcs/10.0/Installation.html

For hardware requirements for your environment, review the detailed systemrequirements on the InfoSphere MDM Collaboration Server Support Web site.

Software requirementsSoftware requirements for InfoSphere MDM Collaboration Server depend on whichproduct components you are using and whether you are installing InfoSphereMDM Collaboration Server on a single server or multiple servers.

When you run the installation program, it first checks your system to determine ifyou are running a supported operating system, database, and application server.

Important: InfoSphere MDM Collaboration Server is an enterprise softwaredesigned for deployment within a secure network only. Exposure to an unsafeexternal network can result in the compromise of network security.

For software requirements for your environment, review the detailed systemrequirements on the InfoSphere MDM Collaboration Server Support Web site.

Installing PerlPerl is required to use IBM InfoSphere Master Data Management CollaborationServer. InfoSphere MDM Collaboration Server requires Perl version 5.8, althoughversion 5.10 is preferred. InfoSphere MDM Collaboration Server also requiresseveral Perl modules.

About this task

Review the following flow chart for the steps involved in installing Perl.

Procedure

To install Perl successfully, you must complete these steps:1. Select the source that you want to use for Perl. See “Sources of Perl” on page 3

for more information.2. If necessary, build and install Perl from the source.

Sart

Build Perl in InfoSphereMDM Collaboration

Server user'shome directory

NO Use OS-supplied Perl?

YES

Step 1

Step 2All Perl

modulesinstalled?

Install otherrequired Perl

modules

YES

END

NO

2 InfoSphere MDM Collaboration Server: Installation Guide



3. Install any Perl modules that InfoSphere MDM Collaboration Server requires.

Sources of PerlYou can use the Perl that is typically installed by default with your operatingsystem, a commercially distributed Perl such as ActiveState ActivePerl, or you cancreate a custom installation of Perl in the home directory for your IBM InfoSphereMaster Data Management Collaboration Server user.

Consider these factors when deciding which version of Perl to install and use withInfoSphere MDM Collaboration Server:

Table 1. Considerations for choosing which version of Perl to install

Sources of Perl Root access C Compiler Perl modulesInstallationportability

Technicalexperiencerequired

Perl suppliedwith operatingsystem

Required Required ifinstallingmodules fromsource;specifically, the Ccompilerprovided by theoperating systemis required.

The full Ccompiler is notincluded as partof the operatingsystem (except onLinux), and mustbe purchasedseparately.Note: Except forLinux whichincludes the GCCC compiler, allother operatingsystems requireyou to purchasethe C compilerseparately:

v AIX: IBM xlc

v HP-UX: HPANSI/C

v Solaris: SunStudio Ccompiler

Required modulesnot installed bydefault.

Limited, mustinstall withinoperating system

Minimal, becausegenerally part ofoperating system

Commerciallydistributed Perl

Not required ifinstalling in thehome directoryfor theInfoSphereMDMCollaborationServer user

Not required All requiredmodules areinstalled bydefault.

Completelyself-contained.Can be reinstalledon other servers.

Minimal, due toease ofinstallation

Chapter 1. Installing 3

Table 1. Considerations for choosing which version of Perl to install (continued)

Sources of Perl Root access C Compiler Perl modulesInstallationportability

Technicalexperiencerequired

Perl installed inInfoSphereMDMCollaborationServer homedirectory

Not required forPerl, but isrequiredtemporarily forthe GNU utilities.

Required, butbuilt using thefreely availableGNU compiler.Can instead usethe C compilerfor the operatingsystem, if youprefer.

All are included. Completelyself-contained.Can copy theinstallationdirectory tosimilar servers, aslong as anidentical PATH isused on eachserver.

Moderate.Experiencebuilding fromsource is highlyrecommended.

Installing GNU utilitiesDepending on your operating system and your choice for the source of Perl, youmight need to install the freely available GNU utilities. If you plan to use theversion of Perl that is supplied with your operating system, and you have the Ccompiler for your operating system installed on the server where you are installingInfoSphere MDM Collaboration Server, you do not need to install the GNUutilities.

Before you begin

You must have root access to install the GNU utilities.

About this task

Installing Perl requires the following GNU utilities: GNU C compiler (g), GNUautoconf, GNU automake, GNU m4, GNU libtool and GNU make.

Procedure1. Download the GNU utilities for your operating system. Linux already includes

the GNU utilities; you can download the GNU utilities for the other supportedoperating systems from these Web sites:

IBM AIXAIX Toolbox, available at: http://www.ibm.com/systems/power/software/aix/linux/toolbox/download.html

Sun SolarisSun Freeware, available at: http://sunfreeware.com

HP-UXHP-UX Porting and Archive Center, available at: http://hpux.connect.org.uk. GCC is available from the HP Developer &Solution Partner Program (DSPP).

2. Install the GNU utilities following the information provided with the packagethat you downloaded.

3. Make sure that the directory containing the GCC utility, the C compiler, is thefirst directory in the PATH statement. For example, if GCC is installed in/usr/local/bin, /usr/local/bin should be first in the PATH statement.


http://www.ibm.com/systems/power/software/aix/linux/toolbox/download.html

http://www.ibm.com/systems/power/software/aix/linux/toolbox/download.html

http://sunfreeware.com

http://hpux.connect.org.uk

http://hpux.connect.org.uk

Building and installing Perl in the home directory of theInfoSphere MDM Collaboration Server userYou can install Perl in the home directory of the IBM InfoSphere Master DataManagement Collaboration Server user.

Before you beginv You have installed a C compilerv Make sure that the PATH statement for the InfoSphere MDM Collaboration

Server user includes the directory where the C compiler is installed.

Procedure1. Download the Perl source code from the following Web site:

http://www.perl.com2. Uncompress the Perl source code into a writable directory.3. Change directories to the directory where you uncompressed the Perl source

code.4. Execute the following command to configure the Perl build:

./Configure –des –Dprefix=<mdmpim_home>/perl –Dcc=gcc

mdmpim_home is the directory where InfoSphere MDM Collaboration Server isinstalled.

5. Execute the make command.6. Execute the make test command. Do not proceed until this command

completes successfully.7. Execute the make install command. This command copies the Perl interpreter

and all standard modules into the directory that you specified earlier as thecustom Perl installation directory for InfoSphere MDM Collaboration Server.

What to do next

Make sure to prepend this Perl installation directory to the PATH statement for thisuser.

Modifying the PATH statement to include the Perl directoryIf you installed Perl in the home directory for the IBM InfoSphere Master DataManagement Collaboration Server user, you must prepend the \bin directory ofthe directory where you installed Perl to the PATH statement. This directory mustbe first on the PATH statement so that this installation of Perl is found before anyother installation of Perl.

Procedure1. Edit the .bashrc file for the IBM InfoSphere Master Data Management

Collaboration Server user.2. Add the following statement to this .bashrc file:

PATH={mdmpim_home}/perl/bin:$PATH

Replace mdmpim_home with the home directory for the IBM InfoSphere MasterData Management Collaboration Server user.

3. Save the .bashrc file.4. Update the current shell by issuing the same statement:

PATH={mdmpim_home}/perl/bin:$PATH

Replace mdmpim_home with the home directory for the IBM InfoSphere MasterData Management Collaboration Server user.


http://www.perl.com

Sample .bashrc fileA .bashrc file is a system file for UNIX and Linux. This file sets up the initialexecution environment for deploying and running a PIM instance on a UNIX andLinux server.

Sample .bashrc file in a WebSphere® Application Server environment

The following sample .bashrc file is used in a WebSphere Application Serverenvironment.

export TOP=<mdm4pim installdir>

# set Oracle specific settingsexport ORACLE_HOME=/opt/oracle/instantclient_11_1export LD_LIBRARY_PATH=${ORACLE_HOME}export LIBPATH=${ORACLE_HOME}export PATH=$ORACLE_HOME:$ORACLE_HOME/bin:$PATH

# set DB2 specific setting. <db2 installdir>/sqllib/db2profile

export PERL5LIB=$TOP/bin/perllibexport JAVA_HOME=<WAS installdir>/javaexport LANG=en_US

Sample .bashrc file in a WebLogic environment

The following sample .bashrc file is used in a WebLogic environment.

export TOP=<mdm4pim installdir>

# set Oracle specific settingsexport ORACLE_HOME=/opt/oracle/instantclient_11_1export LD_LIBRARY_PATH=${ORACLE_HOME}export LIBPATH=${ORACLE_HOME}export PATH=$ORACLE_HOME:$ORACLE_HOME/bin:$PATH

# set DB2 specific setting. <db2 installdir>/sqllib/db2profile

export PERL5LIB=$TOP/bin/perllibexport JAVA_HOME=<Weblogic 10.3 install dir>/jdk160_05export LANG=en_US

Perl modulesAfter you have installed Perl, you might need to install the Perl modules. If youare using the version of Perl provided by your operating system, you need to usethe C compiler that was used to build Perl.

About this task

These Perl modules are freely available from http://www.cpan.org and can beinstalled directly from the Internet or downloaded and installed from the sourcecode.

Installing Perl modules:


http://www.cpan.org

You can install Perl modules using the CPAN module while connected to theInternet or can you download Perl modules from the CPAN site and install themwhile disconnected from the Internet.

Before you begin

v If you are using the operating system installation of Perl, you must have rootaccess.

v If you are using a custom installation of Perl, make sure that the Perl installationdirectory is the first directory in the PATH statement.

About this task

When configuring InfoSphere MDM Collaboration Server, your Perl installation isvalidated and any missing Perl modules are displayed.

You might want to download and use the Devel::Loaded module, because it cantell you which modules you already have installed. After you have installed thismodule, enter the pmall command.

Note: If pmall is not in your PATH, it will be located in the \bin directory in theroot directory of your Perl installation. You can use the which perl command tofind the location of the Perl interpreter in a Perl installation supplied by youroperating system. The which perl command returns a symlink that points to theroot of the Perl installation.

Currently, the following Perl modules are required:v Config::IniFiles (included with InfoSphere MDM Collaboration Server, no need

to install this module separately)v Config::Properties (included with InfoSphere MDM Collaboration Server, no

need to install this module separately)v Term::ReadKeyv File::Findv Getopt::Longv Net::Domainv File::Copyv File::Tempv File::Basenamev IO::Handlev File::Path

Installing Perl modules with an Internet connection:

If you have an Internet connection for each of the servers in your IBM InfoSphereMaster Data Management Collaboration Server installation, you can use the CPANmodule that is part of your default Perl installation to download and install otherPerl modules.

Before you begin


v If you are using a custom installation of Perl, make sure that the installationdirectory is the first directory in the PATH statement.


Procedure

1. Issue the CPAN command. To run CPAN in a shell environment where you canissue commands and respond to prompts, type cpan and press Enter. Or, youcan issue the following command to install specific modules and any of itsdependent modules:perl –MCPAN –e’install <module_name>’

2. If you are running CPAN for the first time, you must configure CPAN. Acceptall the default values when prompted. When configuration is complete, you areeither given a prompt to initiate an action or the action that you alreadyspecified is initiated.

Installing Perl modules without an Internet connection:

If you do not have an Internet connection for each of the servers in your IBMInfoSphere Master Data Management Collaboration Server installation, you candownload the Perl modules from CPAN and then copy them to your servers foryou to install.

Before you begin


v If you are using a custom installation of Perl, make sure that the installationdirectory is the first directory in the PATH statement.

Procedure

1. Download the Perl modules from http://search.cpan.org. You must review thedependencies for the modules and download all of those dependent modulesthat are not installed on your InfoSphere MDM Collaboration Server servers aswell.

Note: The home page of many modules on the CPAN site has a dependencieslink that you can review to determine the dependencies of a module.

2. For each of the modules that you have downloaded, complete the followingsteps:a. Unpack it into a writeable directory.b. Execute the Perl configure command: perl Makefile.pl.c. Execute the make command.d. Execute the make test command. Do not proceed until this command

completes successfully.e. Execute the make install command.


http://search.cpan.org

Chapter 2. Product overview

Global companies require a single source of product and services information toaddress business needs such as global data synchronization, e-commerce, supplychain management, and trading partner management.

Using IBM InfoSphere Master Data Management Collaboration Server, companiescan manage, link, and synchronize information about items, locations,organizations, trading partners, and trade terms internally and externally. PIMsolutions using InfoSphere MDM Collaboration Server offer these features:v A flexible, scalable repository to manage, and link information about products,

locations, trading partners, organizations, and terms of tradev Tools for modeling, capturing, creating, and managing information with high

user productivity and information qualityv Methods of integrating and synchronizing information internally with legacy

systems, enterprise applications, repositories, and mastersv Workflow for business users to support multi-department and multi-enterprise

business processesv Methods of exchanging and synchronizing information externally with business

partnersv Methods of accessing PIM information using many internal and external

electronic and human interaction points

System architectureIBM InfoSphere Master Data Management Collaboration Server has a scalablearchitecture that provides security, data archival capability, and operationalredundancy (or high availability). Data archiving is the process of removing olddata or information from the system and moving it to another system where it canbe retrieved at a later time.

For best performance, run InfoSphere MDM Collaboration Server on a dedicatedsystem. Also, restrict access to the system to maintain security.

InfoSphere MDM Collaboration Server provides a PIM solution developmentplatform with scheduler, business process management, event processing, queuemanagement, and other common components. It supports SQL-like business dataquery, object-oriented scripting, Java API programming, web service development,and other PIM solution development features.

InfoSphere MDM Collaboration Server includes a web-based application with athree-tier architecture that consists of:1. A web-based user interface for rendering PIM content in a browser, including

static, dynamic or cached data in the client side. This tier runs on a webbrowser.

2. A middle tier with the functional modules that process user requests andproduce PIM content in the server side. This tier runs on an application server.

3. A database management system (DBMS) that stores the data that is required bythe middle tier. This tier runs on a database server.


Information flowThe flow of information in IBM InfoSphere Master Data ManagementCollaboration Server is interdependent on several components.

The following image provides an example of the flow of information between theclient, Web server, or application server (where InfoSphere MDM CollaborationServer is installed), and the database server.

User

Database Server

Scheduler ServerWeb Server andApplication Server

HTTP

JDBC

The scheduler service, which manages import and export jobs in the background,can be located on the application server or on a separate server, depending on loadrequirements. If the scheduler is placed on a separate server, InfoSphere MDMCollaboration Server must bind the scheduler service to a specific Remote MethodInvocation (RMI) port.

The following information flow is illustrated in this image:v An application server handles HTTP requests from users.v Services are started or stopped using RMI.v The Scheduler service uses the same RMI port as the one used to control

services.v Application and scheduler servers communicate with the database server using

JDBC.v The scheduler can be run on a dedicated machine or on an application server.

In this example, the first server runs every service except the scheduler, and thesecond server runs the RMI registry, admin process, and scheduler.


Product servicesIBM InfoSphere Master Data Management Collaboration Server includes severalcomponents implemented as JVM services.

The six JVM services and the RMI (Java Remote Method Invocation) registry runconcurrently in the product. The RMI registry registers all product services andmust be running prior to starting all other services.

Table 2. JVM Services

JVM Service Description

admin The admin service starts and stops modules on remote machines.

appsvr The application server service serves Java Server Pages.

eventprocessor The event processor service dispatches events between all the modules.

queuemanager The queue manager service sends documents outside of InfoSphere MDM CollaborationServer.

scheduler The scheduler service runs all scheduled jobs in the background.

The scheduler provides a unified view to manage all jobs that have been scheduled withinInfoSphere MDM Collaboration Server. Through the Jobs Console, a job can be executedbased on a defined timetable and monitored with status information.

The scheduler service communicates with the application through the unified databaseserver and file system, as well as through the rmiregistry.

workflow The workflow engine processes workflow events that are posted to the database.

rmiregistry The RMI (Remote Method Invocation) registry service is a standard Java method that findsand invokes methods or functions on remote systems.

RMI is type of RPC (Remote Procedure Call). In Java, a remote system can be located onanother physical system or on the same machine but in a different JVM. The rmiregistry isa simple directory. Java objects connect to the registry and register how to connect to themand what methods or functions they have. Other services lookup the function they need inthe registry to find out where it is, then call the remote object and execute the method. Anexample is to shutdown a service. The RootAdmin Javaobject looks up InfoSphere MDMCollaboration Server services in the registry, finds out how to contact them, and invokestheir shutdown method. As such, the rmiregistry service does not require a great deal ofsystem resources.

Installation scenariosYou can install IBM InfoSphere Master Data Management Collaboration Server ona single computer or in a clustered environment on several computers.

Simple configuration

In the simple configuration, the product services run on a single computer.

The following image depicts a simple configuration of the product:

Chapter 2. Product overview 11

Single Application Server

HTTP

JDBC

Application Server

Database ServerRDBMS

User

AdminApp ServerEvent Processor

RMI RegistryScheduler

Queue Manager

Complex configuration

In the complex configuration, the product services run in a cluster on severalcomputers.

The following image depicts a complex configuration of the product:

Application Server

Application Server

Application Server

Application Server

Database Server

Load Balancer

AdminRMI Registry

Scheduler

AdminRMI Registry

Scheduler

NFS

AdminApp ServerEvent ProcessorRMI RegistryQueue Manager

Admin

Workflow Engine

App ServerRMI Registry

JDBC

NetworkAttachedStorage($TOP)

HTTP

SharedStorage

User

Netw

ork


Performance planningIt is important that you plan accordingly before installing IBM InfoSphere MasterData Management Collaboration Server. Your planning can greatly affect theperformance of InfoSphere MDM Collaboration Server.

The following common guidelines should be adhered to in order to avoid majorperformance problems:v Testing, profiling and modifying the solution

– For each line item, ensure that you set aside 20% extra time to completetesting, profiling and modifying the solution as needed. Include this 20%extra time before there are any known performance problems.

v Define all of your use cases– The use cases are performance sensitive. Ensure that you identify the

requirements, dependencies and desired performance. Allow extra time foruse cases that have a high potential for performance problems. For example,use cases that have a high potential for performance problems may include alarge number of specs, large amount of location data or large numbers ofworkflow steps. You should test and profile the use cases as they aredeveloped or as early as possible if there are any other dependencies. Ensurethat you do not delay performance testing till the end of the project. You needto establish a baseline for the use cases and have them approved by thecustomer.

v Identify the hardware needed for testing– For hardware, ensure that you identify the hardware needed for performance

testing and have it available early in the project. The hardware forperformance testing should be a replica of the hardware planned forproduction. Performance testing and user acceptance testing should always bedone on hardware that is identical to production.

v Allocate the size of the hardware– Allocating the correct hardware is critical to proper sustained performance of

the solution. The correct size of the hardware required to effectively run thefinal solution depends on the volume of the activity on the system and theoverall complexity of the solution. Correct sizing can be done by workingwith the technical sales team, IBM services team or the performance team.

v Tune the allocated hardware– Correctly sized hardware is only effective when it is properly tuned. There

are two key areas that commonly appear as the cause of performanceproblems:

Latency and bandwidth between the application server and databaseThe latency should be under 0.25ms between the application serverand the database. This can be measured using the traceroutecommand on most systems. The connection between the two shouldbe a gigabit Ethernet capable of transferring large files atapproximately 25MB/s via sftp.

Number of open descriptors is too lowUnexpected problems can be avoided by checking the number ofopen descriptors and verifying that they are set according toWebSphere Application Server guidelines to 8000. The number ofopen descriptors can be checked using the ulimit –a command onmost machines.

v Balance the load and allow for failover

Chapter 2. Product overview 13

– An easy way to address potential overloading of the application server is touse a load balancer. Multiple instances of the scheduler can be started on oneor more servers and various services of the scheduler will load balancethemselves automatically.


Chapter 3. Installing and setting up the database

You must set up the database to complete the IBM InfoSphere Master DataManagement Collaboration Server installation.

To install and set up the database, refer to the documentation for your database. Toconfigure the database for use with InfoSphere MDM Collaboration Server, refer tothe following topics.

InfoSphere MDM Collaboration Server uses two kinds of connections to connect tothe database:v A native database client to run scripts for creating schema or companiesv A JDBC driver

Note: See the system requirements for details: http://www-01.ibm.com/software/data/infosphere/mdm_server_pim/requirements.html.

Setting up your DB2 databaseIf you plan to use a DB2® database with IBM InfoSphere Master Data ManagementCollaboration Server, you must install the supported version of DB2 beforeinstalling InfoSphere MDM Collaboration Server.

Supported DB2 versions are described in the system requirements on the productsupport site:

http://www-01.ibm.com/software/data/infosphere/mdm_server_pim/requirements.html

After installing the database software, make sure that you apply the latest fix pack.

Use the DB2 database configuration guidelines in the following sections to set upyour DB2 database.

Guidelines for setting up a DB2 databaseTo set up a DB2 database and its environment, you must use these guidelines tocreate the instance, database, buffer pools, and table spaces.

The following aspects must be taken into consideration when setting up thedatabase:

Database instance

Create a new, separate database for the InfoSphere MDM CollaborationServer schema. This guide uses PIMDB as the name of this new database.Because of the large amounts of data that InfoSphere MDM CollaborationServer manages, do not share an existing database, but instead create anew one. The database must be created using character encoding UTF-8.

In most implementations, the InfoSphere MDM Collaboration Serverdatabase uses approximately 90% OLTP (online transaction processing) and






10% batch processing. OLTP causes lots of concurrent activity and singlerow updates during business hours and large batch processing activityduring off-peak time.

To avoid that the DB2 system is not I/O bound it is important to usebetween 10 and 15 spindles per CPU core and dedicated LUNs (LogicalUnit Numbers) per database file system. It is also advisable to separateDB2 transaction logs and data on separate spindles and LUNs. Use filesystems instead of raw devices and create one file system per LUN. UseRAID-10 for transaction logs and RAID-10 or RAID-5 for data LUNs. Setthe DB2_PARALLEL_IO registry variable and set the EXTENTSIZE to theRAID stripe size. Use AUTOMATIC (the default) for NUM_IOCLEANERS,NUM_IOSERVERS, and PREFETCHSIZE.

Note: For more information to achieve balanced I/O for your DB2 system,refer to: http://www-128.ibm.com/developerworks/db2/bestpractices/.

Buffer pool requirementsDue to the large size of tables in InfoSphere MDM Collaboration Server, the pagesize used to create the buffer pools is 16KB and 32KB.

You must create the buffer pools, and stop and restart the DB2 instance, before youcreate the table spaces.

The following table lists the buffer pools needed for use by table spaces and therecommended size for each buffer pool:

Table 3. Required buffer pools and recommended sizes.

Buffer pool Used by this table space Size

USERSBP USERS Automatic

INDXBP INDX Automatic

BLOBBP BLOB_TBL_DATA Automatic

XML_DATA_BP XML_DATA Automatic

XML_LARGE_BP XML_LARGE_DATA Automatic

XML_INDX_BP XML_INDEX Automatic

ITA_DATA_BP ITA_DATA Automatic

ITA_IX_BP ITA_IX Automatic

ITM_DATA_BP ITM_DATA Automatic

ITM_IX_BP ITM_IX Automatic

ITD_DATA_BP ITD_DATA Automatic

ITD_IX_BP ITD_IX Automatic

ICM_DATA_BP ICM_DATA Automatic

ICM_IX_BP ICM_IX Automatic

LCK_DATA_BP LCK_DATA Automatic

LCK_IX_BP LCK_IX Automatic

TEMPUSRBP user's temporary table space Automatic

TEMPSYSBP system's temporary table space Automatic


http://www-128.ibm.com/developerworks/db2/bestpractices/

Table 3. Required buffer pools and recommended sizes. (continued)

Buffer pool Used by this table space Size

IBMDEFAULTBP SYSCATSPACE

This is automatically created whenyou create the database.

Automatic

The buffer pools ITA_DATA_BP, ITA_IX_BP, ITD_DATA_BP, ITD_IX_BP,ITM_DATA_BP, ITM_IX_BP, LCK_DATA_BP and LCK_IX_BP are required forInfoSphere MDM Collaboration Server production instances.

Table space requirementsThis section describes the table space requirements.

Definitions

The following table lists the storage type, bufferpool and the management type forthe table spaces:

Only the USERS, INDX, BLOB_TBL_DATA, TEMP_USER and TEMP_SYSTEMtable spaces are required for a default development environment. In a productionenvironment, it is recommended that you create all listed table spaces and bufferpools so highly utilized tables such as ITA, ITD, ITM, ICM and LCK can beassociated to separate table spaces when running the create_schema.sh script later.

Note: You must use a tablespace mapping file to use these additional table spacesand buffer pools. This file is described in the Create schema section.

Table 4. Table space, type, management and buffer pool.

Table space Type Management Buffer pool

USERS REGULAR Automatic ordatabase-managed

USERSBP

INDX REGULAR Automatic ordatabase-managed

INDXBP

BLOB_TBL_DATA LARGE Automatic ordatabase-managed

BLOBBP

XML_DATA REGULAR Automatic ordatabase-managed

XML_DATA_BP

XML_LARGE_DATA REGULAR Automatic ordatabase-managed

XML_LARGE_BP

XML_INDEX REGULAR Automatic ordatabase-managed

XML_INDX_BP

TEMP_USER USER TEMPORARY Automatic oroperatingsystem-managed

TEMPUSRBP

TEMP_SYSTEM SYSTEMTEMPORARY

Automatic oroperatingsystem-managed

TEMPSYSBP

ITA_DATA REGULAR Automatic ordatabase-managed

ITA_DATA_BP

ITM_DATA REGULAR Automatic ordatabase-managed

ITM_DATA_BP

Chapter 3. Installing and setting up the database 17

Table 4. Table space, type, management and buffer pool. (continued)

Table space Type Management Buffer pool

ITD_DATA REGULAR Automatic ordatabase-managed

ITD_DATA_BP

ICM_DATA REGULAR Automatic ordatabase-managed

ICM_DATA_BP

LCK_DATA REGULAR Automatic ordatabase-managed

LCK_DATA_BP

ITA_IX REGULAR Automatic ordatabase-managed

ITA_IX_BP

ITM_IX REGULAR Automatic ordatabase-managed

ITM_IX_BP

ITD_IX REGULAR Automatic ordatabase-managed

ITD_IX_BP

ICM_IX REGULAR Automatic ordatabase-managed

ICM_IX_BP

LCK_IX REGULAR Automatic ordatabase-managed

LCK_IX_BP

TEMP_USER32 USER TEMPORARY Automatic oroperatingsystem-managed

TEMPUSRBP32

TEMP_SYSTEM32 SYSTEMTEMPORARY

Automatic oroperatingsystem-managed

TEMPSYSBP32

There are two types of table space management:

Database managed space (DMS)space that is managed by DB2.

System managed space (SMS)space that is managed by the operating system.

The TEMP_USER and TEMP_USER32 table spaces are SMS user temporary tablespaces that store the declared temporary tables after the application defines suchtables. The use of temporary table space increases throughput of data whilerunning complex SQL queries that need additional space to process large amountsof data.

By creating intermediate tables used to process large amounts of data that aremade available for the duration of the application connection, you reduce the needto rebuild these intermediate tables, improving the performance of the system.

The TEMP_SYSTEM and TEMP_SYSTEM32 are SMS system temporary tablespaces that are used during SQL operations for internal temporary tables, forsorting, storing intermediate results, and for reorganizing tables and other transientdata.

When you create physical and logical volumes for the table spaces, physicallyspread the table spaces in different disks to make use of parallel IO. Specificallyspread the ITA_IX table space into different high performance disks because it is ahigh-use and high-growth table space.


The table spaces listed above should be created with the AUTORESIZE YES option.

Instead of using database or operating system managed table spaces you can alsouse Automatic Storage for all the table spaces. By using the Automatic Storage option,the database manager will automatically manage the container and space allocationfor the table spaces as you create and populate them. This is the default behaviorwhen a new database is created.

Creating the DB2 instanceThe first step in setting up DB2 for use with IBM InfoSphere Master DataManagement Collaboration Server is to create a DB2 instance.

About this task

An instance is a logical database manager environment where you create databasesand set configuration parameters globally. You can have many databases in aninstance, but it is recommended to have one instance with one database for yourInfoSphere MDM Collaboration Server production environment.

For more information on how to create a DB2 instance, see the DB2 documentationor consult your DBA.

Creating the DB2 databaseThe second step in setting up DB2 for use with IBM InfoSphere Master DataManagement Collaboration Server is to create a DB2 database.

About this task

This guide assumes that you know how to create a DB2 database. For moreinformation on how to create a DB2 instance, see the DB2 documentation orconsult your DBA.

Procedure

Create the DB2 database. When creating the database make sure to use CODESETUTF-8 option in the "CREATE DATABASE" statement.

Example

Sample statement for creating a database:CREATE DATABASE PIMDB AUTOMATIC STORAGE YES ON ’/u01/db2inst1’,’/u02/db2inst1’ USING CODESET UTF-8 TERRITORY US

In this example, PIMDB is the database name /u01/db2inst1 and /u02/db2inst1are the automatic storage paths on the DB2 server, change the storage pathsappropriate to your server. Change the territory from US to your appropriateterritory. For a list of DB2 supported values for territory, refer the DB2documentation: http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.admin.nls.doc/doc/r0004565.html.

Creating buffer poolsThe third step in setting up DB2 for use with IBM InfoSphere Master DataManagement Collaboration Server is to create the buffer pools for use by DB2.


http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.admin.nls.doc/doc/r0004565.html

http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.admin.nls.doc/doc/r0004565.html

About this task

A buffer pool is memory that you use to cache table and index data pages as theyare being read from disk or being modified.

This guide assumes that you know how to create buffer pools. For moreinformation on how to create buffer pools, see the DB2 documentation or consultyour DBA.

For information on buffer pool requirements for use with InfoSphere MDMCollaboration Server, see Buffer pool requirements.

Procedure

Create the buffer pools.

Example

Use the following statements for creating buffer pools in DB2 V9 and later:

Note: The bufferpools TEMPSYSBP32 and TEMPUSRBP32 have 32K page size.CREATE BUFFERPOOL USERSBP SIZE AUTOMATIC PAGESIZE 16K;CREATE BUFFERPOOL INDXBP SIZE AUTOMATIC PAGESIZE 16K;CREATE BUFFERPOOL BLOBBP SIZE AUTOMATIC PAGESIZE 16K;CREATE BUFFERPOOL ITA_DATA_BP SIZE AUTOMATIC PAGESIZE 16K;CREATE BUFFERPOOL ITA_IX_BP SIZE AUTOMATIC PAGESIZE 16K;CREATE BUFFERPOOL ITD_DATA_BP SIZE AUTOMATIC PAGESIZE 16K;CREATE BUFFERPOOL ITD_IX_BP SIZE AUTOMATIC PAGESIZE 16K;CREATE BUFFERPOOL ITM_DATA_BP SIZE AUTOMATIC PAGESIZE 16K;CREATE BUFFERPOOL ITM_IX_BP SIZE AUTOMATIC PAGESIZE 16K;CREATE BUFFERPOOL ICM_DATA_BP SIZE AUTOMATIC PAGESIZE 16K;CREATE BUFFERPOOL ICM_IX_BP SIZE AUTOMATIC PAGESIZE 16K;CREATE BUFFERPOOL LCK_DATA_BP SIZE AUTOMATIC PAGESIZE 16K;CREATE BUFFERPOOL LCK_IX_BP SIZE AUTOMATIC PAGESIZE 16K;CREATE BUFFERPOOL TEMPUSRBP SIZE AUTOMATIC PAGESIZE 16K;CREATE BUFFERPOOL TEMPSYSBP SIZE AUTOMATIC PAGESIZE 16K;CREATE BUFFERPOOL TEMPUSRBP32 SIZE AUTOMATIC PAGESIZE 32K;CREATE BUFFERPOOL TEMPSYSBP32 SIZE AUTOMATIC PAGESIZE 32K;CREATE BUFFERPOOL XML_DATA_BP SIZE AUTOMATIC PAGESIZE 32K;CREATE BUFFERPOOL XML_LARGE_BP SIZE AUTOMATIC PAGESIZE 32K;CREATE BUFFERPOOL XML_INDX_BP SIZE AUTOMATIC PAGESIZE 32K;

Only the USERSBP, INDXBP, BLOBBP, TEMPUSRBP, and TEMPSYSBP buffer poolsare required for a development instance.

Creating table spacesThe fourth step in setting up DB2 for use with IBM InfoSphere Master DataManagement Collaboration Server is to create the table spaces in a database thathas automatic storage enabled.

About this task

This guide assumes that you know how to create table spaces. For moreinformation on how to create table spaces, see the DB2 documentation or consultyour DBA.

For details on table space requirements for use with InfoSphere MDMCollaboration Server, see Table space requirements


Procedure

Create the table spaces.

Example

The example below provides sample statements for creating table spaces. Modifythe container path /db/a1/db2inst1/ and /db/a5/db2inst1/ appropriate paths inyour DB2 server.

Regular table spaces:CREATE REGULAR TABLESPACE USERS PAGESIZE 16K MANAGED BY AUTOMATIC STORAGE

BUFFERPOOL USERSBPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE INDX PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL INDXBPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE LARGE TABLESPACE BLOB_TBL_DATA PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL BLOBBPFILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE ITA_DATA PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL ITA_DATA_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE ITM_DATA PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL ITM_DATA_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE ITD_DATA PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL ITD_DATA_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE ICM_DATA PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL ICM_DATA_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE LCK_DATA PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL LCK_DATA_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE ITA_IX PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL ITA_IX_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE ITM_IX PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL ITM_IX_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE ITD_IX PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL ITD_IX_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE ICM_IX PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL ICM_IX_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE LCK_IX PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL LCK_IX_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

Temporary table spaces:


CREATE USER TEMPORARY TABLESPACE TEMP_USER PAGESIZE 16K MANAGEDBY AUTOMATIC STORAGE

BUFFERPOOL TEMPUSRBP;

CREATE SYSTEM TEMPORARY TABLESPACE TEMP_SYSTEM PAGESIZE 16K MANAGEDBY AUTOMATIC STORAGE

BUFFERPOOL TEMPSYSBP;

CREATE USER TEMPORARY TABLESPACE TEMP_USER32 PAGESIZE 32K MANAGEDBY AUTOMATIC STORAGEBUFFERPOOL TEMPUSRBP32;

CREATE SYSTEM TEMPORARY TABLESPACE TEMP_SYSTEM32 PAGESIZE 32K MANAGEDBY AUTOMATIC STORAGEBUFFERPOOL TEMPSYSBP32;

CREATE REGULAR TABLESPACE XML_DATA PAGESIZE 32K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL XML_DATA_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 100M;

CREATE LARGE TABLESPACE XML_LARGE_DATA PAGESIZE 32K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL XML_LARGE_BPFILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 100M;

CREATE REGULAR TABLESPACE XML_INDEX PAGESIZE 32K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL XML_INDX_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 100M;

Note: Only the USERS, INDX, BLOB_TBL_DATA, TEMP_USER, andTEMP_SYSTEM table spaces are required for a development instance.

Adding database users and granting permissionsTo install and use IBM InfoSphere Master Data Management Collaboration Servereffectively, you must add a database user and grant the necessary permissions.

Before you begin

The InfoSphere MDM Collaboration Server database schema needs a database userauthenticated at the server level.

Procedure1. Create a user at the operating system level.

a. Create an operating system user. You must have root authority to create auser, or you need to contact your DB2 server administrator for help.

b. Set the password for the user. You can try to connect to the server using theuser ID to verify that the user can connect to the server.

c. Set a new password for the user. With AIX®, the password expiresimmediately after you log in to the server.

2. Create a database user pim and grant the required permissions using theinstance owner login (the default instance owner login is db2inst1). You needto grant these permissions:v DBADM (this authority is optional)v CREATETABv BINDADDv CONNECTv CREATE_NOT_FENCEDv IMPLICIT_SCHEMA


v LOAD ON DATABASESample SQL:db2 CONNECT TO <databasename> user <Username> using <password>db2 GRANT DBADM, CREATETAB, BINDADD, CONNECT, CREATE_NOT_FENCED,IMPLICIT_SCHEMA, LOAD ON DATABASE TO USER PIM

3. Grant user permissions to use space on all the InfoSphere MDM CollaborationServer specific table spaces. You can grant user permissions using the followingSQL statements:db2 GRANT USE OF TABLESPACE USERS TO PIMdb2 GRANT USE OF TABLESPACE INDX TO PIMdb2 GRANT USE OF TABLESPACE BLOB_TBL_DATA TO PIMdb2 GRANT USE OF TABLESPACE TEMP_USER TO PIMdb2 GRANT USE OF TABLESPACE XML_DATA TO PIMdb2 GRANT USE OF TABLESPACE XML_LARGE_DATA TO PIMdb2 GRANT USE OF TABLESPACE XML_INDEX TO PIM

4. Grant user permissions to any additional table spaces that you create for theInfoSphere MDM Collaboration Server production environment. You can grantuser permissions using the following SQL statements:db2 GRANT USE OF TABLESPACE ICM_DATA TO PIMdb2 GRANT USE OF TABLESPACE ICM_IX TO PIMdb2 GRANT USE OF TABLESPACE ITM_DATA TO PIMdb2 GRANT USE OF TABLESPACE ITM_IX TO PIMdb2 GRANT USE OF TABLESPACE ITD_DATA TO PIMdb2 GRANT USE OF TABLESPACE ITD_IX TO PIMdb2 GRANT USE OF TABLESPACE ITA_DATA TO PIMdb2 GRANT USE OF TABLESPACE ITA_IX TO PIMdb2 GRANT USE OF TABLESPACE LCK_DATA TO PIMdb2 GRANT USE OF TABLESPACE LCK_IX TO PIM

5. Create a new schema entitled PIM for the user PIM.Sample SQL as created by Control Center.CREATE SCHEMA PIM AUTHORIZATION PIM;

What to do next

Repeat these steps if you want one more database schema user for another instanceof InfoSphere MDM Collaboration Server. For example, if you want another testinstance of InfoSphere MDM Collaboration Server running on the applicationserver that needs a database schema in the same database, then you need to createa database user and schema with the name pimtest in the database. This needs anoperating system user with the name pimtest.

Important: You can share the database for InfoSphere MDM Collaboration Serverwith development or QA environments, but not with a production environment. Ifyou share the InfoSphere MDM Collaboration Server production database, it willimpact production performance.

DB2 configurationsYou can customize profile registry variables, database manager configurationparameters, and DB2 configuration parameters to optimize performance with IBMInfoSphere Master Data Management Collaboration Server.

IBM DB2 database profile registry updatesIBM InfoSphere Master Data Management Collaboration Server requires thatcertain profile registry values be updated for DB2.


The following profile registry variables are required for use by InfoSphere MDMCollaboration Server:

DB2_SKIPINSERTEDThe DB2_SKIPINSERTED registry variable allows statements using eitherCursor Stability or Read Stability isolation levels to skip uncommittedinserted rows as if they had not been inserted. This registry variable doesnot impact the behavior of cursors on the DB2 catalog tables. This registryvariable is activated at database startup, while the decision to skipuncommitted inserted rows is made at statement compile or bind time.

Set the value to OFF.

DB2_SKIPDELETEDThe DB2_SKIPDELETED registry variable allows statements using eitherCursor Stability or Read Stability isolation levels to unconditionally skipdeleted keys during index access and deleted rows during table access.With DB2_EVALUNCOMMITTED enabled, deleted rows are automaticallyskipped, but uncommitted pseudo-deleted keys in type-2 indexes are notskipped unless DB2_SKIPDELETED is also enabled. This registry variabledoes not impact the behavior of cursors on the DB2 catalog tables. Thisregistry variable is activated with the db2start command.

Set the value to OFF.

DB2_EVALUNCOMMITTEDThe DB2_EVALUNCOMMITTED registry variable allows, where possible,table or index access scans to defer or avoid row locking until a datarecord is known to satisfy predicate evaluation. With this variable enabled,predicate evaluation may occur on uncommitted data.DB2_EVALUNCOMMITTED is applicable only to statements using eitherCursor Stability or Read Stability isolation levels. For index scans, theindex must be a type-2 index. Furthermore, deleted rows are skippedunconditionally on table scan access while deleted keys are not skipped fortype-2 index scans unless the registry variable DB2_SKIPDELETED is alsoset. The activation of the DB2_EVALUNCOMMITTED registry variable iseffective on the db2start command. The decision as to whether deferredlocking is applicable is made at statement compile or bind time.

Set the value to NO.

DB2CODEPAGE

The DB2CODEPAGE registry variable is used to specify the character setthat is used during export and import of data in DB2.

Set the value to 1208.

DB2COMM

The DB2COMM registry variable determines which protocol's connectionmanagers will be enabled when the database manager is started. You canset this variable for multiple communication protocols by separating thekeywords with commas.

Set the value to tcpip.

DB2_PARALLEL_IO

The DB2_PARALLEL_IO registry variable changes the way DB2 calculatesthe I/O parallelism of a table space. When I/O parallelism is enabled(either implicitly, by the use of multiple containers, or explicitly, by settingDB2_PARALLEL_IO), it is achieved by issuing the correct number of


prefetch requests. Each prefetch request is a request for an extent of pages.For example, a table space has two containers and the prefetch size is fourtimes the extent size. If the registry variable is set, a prefetch request forthis table space will be broken into four requests (one extent per request)with a possibility of four prefetchers servicing the requests in parallel.

Set the value to "*" (asterisk)

Other Profile Registry variables are not required, but may be set if there is aspecific requirement.

You can set the DB2 registry variables using the following DB2 commands in DB2server:db2set DB2_SKIPINSERTED=OFFdb2set DB2_EVALUNCOMMITTED=NOdb2set DB2_SKIPDELETED=OFFdb2set DB2COMM=tcpipdb2set DB2_PARALLEL_IO=*db2set DB2CODEPAGE=1208

DB2 database manager configuration parametersIBM InfoSphere Master Data Management Collaboration Server requires certainDB2 database manager configuration parameters be set before installing and usingthe product.

The following table shows the database manager configuration parameters andcorresponding values that must be set for use with InfoSphere MDM CollaborationServer. In each case, the syntax of the command to update the parameter is

db2 update dbm cfg using <parameter> <value>

Table 5. DB2 database manager configuration parameters.

Parameter Description Value

MON_HEAP_SZ The memory required formaintaining the private viewsof the database systemmonitor data is allocated fromthe monitor heap. Its size iscontrolled by the mon_heap_szconfiguration parameter.

Automatic

SHEAPTHRES Private and shared sorts usememory from two differentmemory sources. The size ofthe shared sort memory area isstatically predetermined at thetime of the first connection toa database based on the valueof sheapthres. This has to atleast two times the size ofsortheap of any databasehosted by the DB2 instance.

0 (Automatic)


Table 5. DB2 database manager configuration parameters. (continued)


ASLHEAPSZ The application support layerheap represents acommunication buffer betweenthe local application and itsassociated agent. This buffer isallocated as shared memoryby each database manageragent that is started.

1024

QUERY_HEAP_SZ This parameter specifies themaximum amount of memorythat can be allocated for thequery heap. A query heap isused to store each query in theagent's private memory. As aminimum, you should setquery_heap_sz to a value atleast five times larger thanaslheapsz.

5120

Sample statements for updating database manager configurations in DB2 V9 andlater:update dbm cfg using MON_HEAP_SZ 5120update dbm cfg using QUERY_HEAP_SZ 5120update dbm cfg using ASLHEAPSZ 1024update dbm cfg using SHEAPTHRES 0

There is no requirement to update SHEAPTHRES for new installations as 0 is thedefault value.

DB2 database configuration parametersIBM InfoSphere Master Data Management Collaboration Server requires certainDB2 configuration parameters be set before installing and using the product.

The following table shows the database configuration parameters that must be setfor use with InfoSphere MDM Collaboration Server:

Table 6. DB2 database configuration parameters


DFT_QUERYOPT The query optimization classis used to direct theoptimizer to use differentdegrees of optimizationwhen compiling SQL queries.This parameter providesadditional flexibility bysetting the default queryoptimization class.

5


Table 6. DB2 database configuration parameters (continued)


DBHEAP There is one database heapper database, and thedatabase manager uses it onbehalf of all instances ofInfoSphere MDMCollaboration Serverconnected to the database. Itcontains control blockinformation for tables,indexes, table spaces, andbuffer pools. It also containsspace for the log buffer(logbufsz), and the catalogcache (catalogcache_sz).Therefore, the size of theheap will be dependent onthe number of control blocksstored in the heap at a giventime. The control blockinformation is kept in theheap until all instances ofInfoSphere MDMCollaboration Serverdisconnect from thedatabase.

The minimum amount thedatabase manager needs toget started is allocated at thefirst connection. The dataarea is expanded as neededup to the maximum specifiedby dbheap.

Automatic

CATALOGCACHE_SZ This parameter indicates themaximum amount of spacethat the catalog cache canuse from the database heap(dbheap).

5120

LOGBUFSZ This parameter allows you tospecify the amount of thedatabase heap (defined bythe dbheap parameter) to useas a buffer for log recordsbefore writing these recordsto disk This parameter mustalso be less than or equal tothe dbheap parameter.

4096

UTIL_HEAP_SZ This parameter indicates themaximum amount ofmemory that can be usedsimultaneously by theBACKUP, RESTORE and LOADand load recovery utilities.

5120




LOCKLIST This parameter indicates theamount of storage that isallocated to the lock list.There is one lock list perdatabase and it contains thelocks held by all instances ofInfoSphere MDMCollaboration Serverconcurrently connected to thedatabase. Depending on thesize of the database, thisparameter might require anincrease .

Automatic

APP_CTL_HEAP_SZ This parameter determinesthe maximum size, in 4 KBpages, for the applicationcontrol shared memory.Application control heaps areallocated from this sharedmemory.

512

SORTHEAP This parameter defines themaximum number of privatememory pages to be used forprivate sorts, or themaximum number of sharedmemory pages to be used forshared sorts.

Automatic

STMTHEAP The statement heap is usedas a workspace for the SQLcompiler during compilationof an SQL statement. Thisparameter specifies the sizeof this workspace.

Automatic

APPLHEAPSZ This parameter defines thenumber of private memorypages available to be used bythe database manager onbehalf of a specific agent orsubagent.

Automatic

STAT_HEAP_SZ This parameter indicates themaximum size of the heapused in collecting statisticsusing the RUNSTATScommand.

Automatic

MAXLOCKS Lock escalation is the processof replacing row locks withtable locks, reducing thenumber of locks in the list.This parameter defines apercentage of the lock listheld by an application thatmust be filled before thedatabase manager performsescalation.

Automatic




LOCKTIMEOUT This parameter specifies thenumber of seconds thatInfoSphere MDMCollaboration Server willwait to obtain a lock.

60

NUM_IOCLEANERS This parameter allows you tospecify the number ofasynchronous page cleanersfor a database. These pagecleaners write changed pagesfrom the buffer pool to diskbefore a database agentrequires the space in thebuffer pool.

Automatic

NUM_IOSERVERS I/O servers are used onbehalf of the database agentsto perform prefetch I/O andasynchronous I/O by utilitiessuch as backup and restore.This parameter specifies thenumber of I/O servers for adatabase.

Automatic

MAXAPPLS This parameter specifies themaximum number ofconcurrent instances ofInfoSphere MDMCollaboration Server that canbe connected (both local andremote) to a database.

Automatic

AVG_APPLS The SQL optimizer uses thisparameter to help estimatehow much of the buffer poolwill be available at run time.

Automatic

MAXFILOP This parameter specifies themaximum number of filehandles that can be open foreach database agent.

640

Sample statement for updating database configurations in DB2 V9 and later:update db cfg using SELF_TUNING_MEM ONupdate db cfg using DFT_QUERYOPT 5update db cfg using CATALOGCACHE_SZ 6000update db cfg using LOGBUFSZ 4096update db cfg using UTIL_HEAP_SZ 5120update db cfg using BUFFPAGE 1024update db cfg using APP_CTL_HEAP_SZ 512update db cfg using LOCKTIMEOUT 60update db cfg using MAXFILOP 640update db cfg using AUTO_MAINT ONupdate db cfg using AUTO_TBL_MAINT ONupdate db cfg using AUTO_RUNSTATS ONupdate db cfg using AUTO_STMT_STATS ON

You must not update the following parameters for new installations. Theparameters are already set with correct values, by default, in DB2 V9 and later:


DBHEAPLOCKLISTMAXLOCKSSORTHEAPSTMTHEAPAPPLHEAPSZSTAT_HEAP_SZNUM_IOCLEANERSNUM_IOSERVERSMAXAPPLSAVG_APPLS

Transaction log files for the databaseTransaction log files provide you with the ability to recover your environment to aconsistent state and preserve the integrity of your data. Log file storage must beoptimized because log files are written sequentially, and the database managerreads log files sequentially during database recovery.

It is recommended to put the logs on file system and they should always reside ontheir own physical disks, separate from the database tablespaces and databasesoftware. The disks ideally should be dedicated to DB2 logging to avoid thepossibility of any other processes accessing or writing to these disks. Idealplacement of the logs is on the outer edge of the disk where there are more datablocks per track. It is strongly recommended to protect the log against single diskfailures by using a RAID 10 or RAID 5 array.

Table 7. Transaction log files and parameters

Parameter Description

NEWLOGPATH This parameter is used to change the logpath to create the transaction log files on aseparate partition/volume than the defaultvolume or the one used for databasetablespace containers.

Set it to a directory that is the destination oflog files. Make sure that the directory iscreated before setting it. Make sure thatthere is enough space on the destinationbefore setting the new log path.

For example: update db cfg for PIMDBusing NEWLOGPATH /u02/db2data/logs

LOGFILSIZ This parameter defines the size of eachprimary and secondary log file. The size ofthese log files limits the number of logrecords that can be written to them beforethey become full and a new log file isrequired. Set it to 30000 if it is adevelopment/test database otherwise set itto 60000. The size is number of pages eachof size 4 KB.

For example: update db cfg for PIMDBusing LOGFILSIZ 60000


Table 7. Transaction log files and parameters (continued)

Parameter Description

LOGPRIMARY The primary log files establish a fixedamount of storage allocated to the recoverylog files. This parameter allows you tospecify the number of primary log files to bepre-allocated. Set it to 20 if it is adevelopment database otherwise set it to 40.

For example: update db cfg for PIMDBusing LOGPRIMARY 40

LOGSECOND This parameter specifies the number ofsecondary log files that are created and usedfor recovery log files (only as needed). Whenthe primary log files become full, thesecondary log files (of size logfilsiz) areallocated one at a time as needed, up to amaximum number as controlled by thisparameter. Set its value to 2.

For example: update db cfg for PIMDBusing LOGSECOND 2

Restart the database after making db configuration changes with db2stop anddb2start commands:

db2stop force

db2start

The following table has information about recommended values of differentconfiguration parameters that influence the transaction log size and numbers forsmall, medium and large InfoSphere MDM Collaboration Server databaseimplementations:

Table 8. Recommended values of different configuration parameters

Parameter Small Medium Large

LOGFILSIZ 30000 60000 70000

LOGPRIMARY 30 40 50

LOGSECOND 2 2 2

Total Space Required 3.7 GB 9.6 GB 13.8 GB

Setting up the DB2 client on InfoSphere MDM CollaborationServer

You must set up the DB2 client on InfoSphere MDM Collaboration Server.

Before you begin

Before you set up the DB2 client on WebSphere Application Server, you must:v Install DB2 Admin/Developer/Run-Time Client on WebSphere Application

Server.v Make sure that the DB2 software and the instances on DB server and application

server are on same fix pack level. You can use db2level command to check thelevel. Apply the fix pack if they are not on the same level.


Procedure1. Create an IBM DB2 instance on the application server.

This step is not required if the database and application server are installed onthe same machine.If you are running the database server and the application server on the samemachine that is running on IBM AIX, you must modify the .profile file of theDB2 instance owner and the user used to install InfoSphere MDMCollaboration Server to include these two commands: export EXTSHM=on anddb2set DB2ENVLIST=EXTSHM. Then, you must stop and start DB2.

2. When running InfoSphere MDM Collaboration Server on a different server,catalog the database to be able to connect to the database from InfoSphereMDM Collaboration Server.Run the following commands as the DB2 instance owner (usually db2inst1) onthe application server:db2 "catalog tcpip node <nodename> remote <dbhostname> server <sname/port#>"db2 terminatedb2 "catalog database <dbname> as <dbname> at node <nodename>"db2 terminate

Replace the variables in the above commands with this information:

nodenamename for the remote instance.

dbhostnamehostname or IP address of the database server.

sname/port#service name or port number for the connection port of the local DB2instance, in the /etc/services file.

To identify the correct port number, first find out the correct servicename e.g., value of the SVCENAME parameter of the database manager(DBM) and then search for that service name in the /etc/services file.

dbnamedatabase name.

IBM DB2 database setup checklistUse this checklist to verify your IBM DB2 setup prior to installing IBM InfoSphereMaster Data Management Collaboration Server.

There is also a script to check DB2 parameters and configuration. It is available in$TOP/bin/db_checklist/db2_checklist.sql. Use this SQL script to verify DB2settings are correctly set for InfoSphere MDM Collaboration Server.

Table 9. IBM DB2 setup checklist

Check the IBM DB2 server release. The version of the DB2 server should be theversion that is identified in the detailedsystem requirements.

Check the database codeset. The character set and national character setshould be UTF8. On the database serverlogged in as instance owner:

$db2 get db cfg for <database name>

This should have |Database code set| set toUTF-8


http://www.ibm.com/software/data/infosphere/mdm_server_pim/requirements.html


Table 9. IBM DB2 setup checklist (continued)

Check the parameter file entries. Follow the DB2 configuration sectionsprovided, to make sure you have maderequired parameter changes for the DB2registry variables, database manager, and thedatabase.

Check the table spaces setup. Make sure the required table spaces aresetup in the database.

Check the transaction logs setup. Make sure that the transaction logs arecreated on a separate partition.

Check the database user setup. View the database user name and passwordin the $TOP/bin/conf/env_settings.ini fileand make sure that the database user iscreated and all required privileges aregranted to the user.

Check the connectivity to the databaseserver.

The database server and the database servernode must be catalogued on the applicationserver and the database must be accessiblefrom the application server.

v Check the database connectivity with

db2 connect to pimdb user pim_db_userusing db_user_password

Setting up your Oracle databaseIf you plan to use an Oracle database with IBM InfoSphere Master DataManagement Collaboration Server, you must install the supported version ofOracle before installing InfoSphere MDM Collaboration Server.

Supported Oracle versions are described in the system requirements on theproduct support site:


After installing the database software, make sure that you apply the latest fix pack.

Use the Oracle database configuration guidelines in the following sections to set upyour Oracle database.

Updating operating system settings for OracleThere are several settings for system semaphores and shared memory that Oraclerecommends. Refer to the Oracle documentation specific to your platform forconfiguration information.

Disk considerations for the databaseThe preparation for optimal workload distribution is a significant considerationwhen setting up the database for IBM InfoSphere Master Data ManagementCollaboration Server.




In most of the customer implementations, the InfoSphere MDM CollaborationServer Database processing workload is shared in the following way:v 90% OLTP (Online Transaction Processing)v 10% Batch Processing

Distributing the workload in this manner means that concurrent activity and singlerow updates are performed during peak business hours and large batch processingis performed during off-peak-time. You must understand the type of workloadyour database is expected to perform in order to layout the physical database mosteffectively.

In order to achieve a balanced I/O, the InfoSphere MDM Collaboration ServerDBA team recommends using a greater number of relatively low-capacity disksallocated for the database rather than fewer high-capacity disks. A minimum of 6to 10 disks per CPU is recommends for optimal performance. Having too few largedisks may cause database to wait on disc I/O and impact performance.

RAID 10 provides excellent performance and availability. If overall cost is aconcern, use RAID 5 with Fast Write Cache. If cost is not a concern, then RAID 10is strongly recommended for the storing data.

The InfoSphere MDM Collaboration Server DBA team recommends physicallyseparating data, index and UNDOTBS1 table space on the disks when you createtable spaces and add data files.

Creating a new databaseIt is recommended to setup a separate database for use with IBM InfoSphereMaster Data Management Collaboration Server.

About this task

This guide assumes that you know how to create a new Oracle database. For moreinformation on how to create an Oracle database, see the Oracle documentation orconsult your DBA.

Create a database once you are certain that the installation and setup prerequisitesare met.

Procedure

Create a new Oracle database.

Important: InfoSphere MDM Collaboration Server uses AL32UTF8 character set.Therefore, the database character set must be set to AL32UTF8 and the nationalcharacter set must be set to AL16UTF16 at the time you create the InfoSphereMDM Collaboration Server database.If you already have a UTF8 database created for any InfoSphere MDMCollaboration Server application schema that is not an InfoSphere MDMCollaboration Server 5.3 schema, and if you are upgrading the InfoSphere MDMCollaboration Server to V5.3, then you can reuse the same UTF8 database. You donot have to create a separate AL32UTF8 database.

Oracle setup for high availabilityFor high availability and scalability, Oracle provides the Transparent ApplicationFailover (TAF) feature that is a part of Real Application Clusters (RAC). TAF


enables IBM InfoSphere Master Data Management Collaboration Server to beavailable continuously in the event of database server failure.

About this task

The Oracle TAF feature supports failover of read transactions only; writetransactions during database failure are rolled back. InfoSphere MDMCollaboration Server continues to run when there is a database failure. However,InfoSphere MDM Collaboration Server users are required to resubmit thetransaction after failure. Unsaved data will be lost and users are required to reenterthe data. Because Oracle will not load balance the existing database connectionsbetween all the nodes after the failover, it is recommended that you restartInfoSphere MDM Collaboration Server after the failover to utilize all the databaseserver nodes.

For installation and configuration of Oracle database with RAC, refer to the Oracledocumentation. It is recommended that you set up the server-side TAF service onthe Oracle server.

Procedure1. Configure the Oracle client for TAF.

a. Configure the TAF parameters along with the Oracle RAC nodes in thetnsnames.ora file of the Oracle client. The following sample shows thetnsnames entry:

ibm.world =(DESCRIPTION_LIST =(FAILOVER = yes)(LOAD_BALANCE = yes)(DESCRIPTION =(ADDRESS =(PROTOCOL = TCP)(HOST = fresno1)(PORT = 1521)(HOST = fresno2)(PORT=1521))(CONNECT_DATA =(SERVICE_NAME = ibm.world)(SERVER = dedicated)(FAILOVER_MODE =(BACKUP=ibm.world.bkp)(TYPE=select)(METHOD=preconnect)(RETRIES=20)(DELAY=3)))))

The FAILOVER_MODE section of the tnsnames.ora file lists the failoverparameters and their values:

BACKUP=ibm.world.bkpThis parameter names the backup service name that will take overfailed connections when a node crashes. In this example, the


primary server is fresno1 and TAF will reconnect failed transactionsto the fresno2 instance in case of server failure.

TYPE=selectThis parameter tells TAF to restart all read-only in-flighttransactions from the beginning of the transaction.

METHOD=preconnectThis parameter directs TAF to create two connections when thetransactions start: one to the primary fresno1 database and a backupconnection to the fresno2 database. In case of instance failure, thefresno2 database will be ready to resume the failed transaction.

RETRIES=20This parameter directs TAF to retry a failover connection up to 20times.

DELAY=3This parameter tells TAF to wait three seconds between connectionretries.

2. Configure InfoSphere MDM Collaboration Server to use the OCI driver whenusing TAF. See Chapter 6, “Configuring the product,” on page 55 for setting upOCI driver.a. After the configuration is complete, you must manually modify the db_url

property in the common.properties file. The db_url property should use thetnsnames.ora entry with TAF parameters similar to parameters as shown inthe following example: db_url=jdbc:oracle:oci:@ibm.world

Oracle parameter file settingsOracle uses configuration parameters to locate files and specify runtime parameterscommon to all Oracle products.

When an Oracle program or application requires a translation for a particularconfiguration variable, Oracle consults the associated parameter. All Oracleparameters are stored in the registry.

The following parameters are set for the use with IBM InfoSphere Master DataManagement Collaboration Server:

Table 10. Oracle parameters

Parameter Description Required value

SGA_TARGET SGA_TARGET specifies the total size ofall SGA components. If theSGA_TARGET is specified, then thefollowing memory pools areautomatically sized:

v Buffer cache (DB_CACHE_SIZE)

v Shared pool (SHARED_POOL_SIZE)

v Large pool (LARGE_POOL_SIZE)

v Java pool (JAVA_POOL_SIZE)

v Streams pool (STREAMS_POOL_SIZE)

50% of your physical memory onthe DB server, assuming you areusing the DB server for Oracleonly and Oracle DB is used forInfoSphere MDM CollaborationServer only.


Table 10. Oracle parameters (continued)

Parameter Description Required value

DB_BLOCK_SIZE The parameter sets the size (in bytes) ofan Oracle database block. This value isset at database creation, and cannot besubsequently changed. DB BLOCK SIZEis critical for the InfoSphere MDMCollaboration Server schema and mustbe at least 8192. Schema creation willfail if the db_block_size is too small.

Required Value: 8192

QUERY_REWRITE_ENABLED Used to enable or disable queryrewriting for materialized views.

Required Value: TRUE

PROCESSES The parameter specifies the maximumnumber of operating system userprocesses that can simultaneouslyconnect to an Oracle Server.

Required value: 200

OPEN_CURSORS The parameter specifies the maximumnumber of open cursors a session canhave at once, and constrains thePL/SQL cursor cache size, whichPL/SQL uses to avoid re-parsingstatements re-executed by a user.

Required value: 600

MAX_ENABLED_ROLES Specifies the maximum number ofdatabase roles that a user can enable,including sub-roles.

Required value: 60

LOG_BUFFER Specifies the amount of memory, inbytes, that is used to buffer redo entriesbefore they are written to a redo log fileby LGWR . Redo entries keep a recordof changes made to database blocks.

Required value: 5242880

OPTIMIZER_INDEX_CACHING Adjusts the cost-based optimizer'sassumptions for what percentage ofindex blocks are expected to be in thebuffer cache for nested loops joins. Thisaffects the cost of executing a nestedloops join where an index is used.Setting this parameter to a higher valuemakes nested loops join look lessexpensive to the optimizer. Range ofvalues is 0 to 100 percent.

Required value: 90

OPTIMIZER_INDEX_COST_ADJ Used to tune optimizer performancewhen too few or too many index accesspaths are considered. A lower valuemakes the optimizer more likely toselect an index. That is, setting it to 50percent will make the index access pathlook half as expensive as normal. Rangeof Values is 1 to 10000.

Required value: 50

Creating table spacesThe fourth step in setting up DB2 for use with IBM InfoSphere Master DataManagement Collaboration Server is to create the table spaces in a database thathas automatic storage enabled.


About this task

This guide assumes that you know how to create table spaces. For moreinformation on how to create table spaces, see the DB2 documentation or consultyour DBA.

For details on table space requirements for use with InfoSphere MDMCollaboration Server, see Table space requirements

Procedure

Create the table spaces.

Example

The example below provides sample statements for creating table spaces. Modifythe container path /db/a1/db2inst1/ and /db/a5/db2inst1/ appropriate paths inyour DB2 server.

Regular table spaces:CREATE REGULAR TABLESPACE USERS PAGESIZE 16K MANAGED BY AUTOMATIC STORAGE

BUFFERPOOL USERSBPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE INDX PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL INDXBPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE LARGE TABLESPACE BLOB_TBL_DATA PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL BLOBBPFILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE ITA_DATA PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL ITA_DATA_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE ITM_DATA PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL ITM_DATA_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE ITD_DATA PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL ITD_DATA_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE ICM_DATA PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL ICM_DATA_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE LCK_DATA PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL LCK_DATA_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE ITA_IX PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL ITA_IX_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE ITM_IX PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL ITM_IX_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE ITD_IX PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL ITD_IX_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;


CREATE REGULAR TABLESPACE ICM_IX PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL ICM_IX_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

CREATE REGULAR TABLESPACE LCK_IX PAGESIZE 16K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL LCK_IX_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 1G;

Temporary table spaces:CREATE USER TEMPORARY TABLESPACE TEMP_USER PAGESIZE 16K MANAGEDBY AUTOMATIC STORAGE

BUFFERPOOL TEMPUSRBP;

CREATE SYSTEM TEMPORARY TABLESPACE TEMP_SYSTEM PAGESIZE 16K MANAGEDBY AUTOMATIC STORAGE

BUFFERPOOL TEMPSYSBP;

CREATE USER TEMPORARY TABLESPACE TEMP_USER32 PAGESIZE 32K MANAGEDBY AUTOMATIC STORAGEBUFFERPOOL TEMPUSRBP32;

CREATE SYSTEM TEMPORARY TABLESPACE TEMP_SYSTEM32 PAGESIZE 32K MANAGEDBY AUTOMATIC STORAGEBUFFERPOOL TEMPSYSBP32;

CREATE REGULAR TABLESPACE XML_DATA PAGESIZE 32K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL XML_DATA_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 100M;

CREATE LARGE TABLESPACE XML_LARGE_DATA PAGESIZE 32K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL XML_LARGE_BPFILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 100M;

CREATE REGULAR TABLESPACE XML_INDEX PAGESIZE 32K MANAGED BY AUTOMATIC STORAGEBUFFERPOOL XML_INDX_BPNO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 100M;

Note: Only the USERS, INDX, BLOB_TBL_DATA, TEMP_USER, andTEMP_SYSTEM table spaces are required for a development instance.

Setting up transaction logsOracle relies on online redo log files to record transactions. Each time a transactiontakes place in the database, an entry is added to the redo log files.

About this task

Database performance can be increased by correctly tuning the size of the redo logfiles. Uncommitted transactions also generate the redo log entries.

Some important considerations when creating redo logs:v Place all the redo log groups on one disk without any other files. That means

separate the redo log files from data files.v Use the fastest of available disks for redo logs if possible.v Consider availability: members of the same group should be on different

physical disks and controllers for recoverability purposes.v Avoiding the use of RAID 5 for redo logs. See “Disk considerations for the

database” on page 33 for information on optimal disk allocations.v Separate redo logs from archived redo logs by creating them on separate disks.


Redo log files are written sequentially by the Log Writer (LGWR) process. Thisoperation can be made faster if there is no concurrent activity on the same disk.Dedicating separate disks to redo log files usually ensures that LGWR runssmoothly with no further tuning necessary. If your system supports asynchronousI/O, but this feature is not currently configured, then test to see if using thisfeature is beneficial.

Procedure1. Create six redo log groups with files of size 300 MB each.2. Multiplex (mirror) the redo logs by creating two members in each redo log

group.

Important: No two members of the same group should be on the same disk.

Creating database schema usersOracle database schema users must be set up for use with IBM InfoSphere MasterData Management Collaboration Server.

Before you begin

Before you can create database schema users, you need the following userinformation:v Default tablespace: users.v Temporary tablespace: temp.v Authentication: Password.v Status: Unlocked.v Roles to be granted: Connect, and Resource.v System Privileges to be granted: unlimited tablespace, select any dictionary,

query rewrite, and create any synonym.

About this task

You can create a database user for InfoSphere MDM Collaboration Server that isreferenced in the common.properties file using SQL commands.

Procedure

Execute these SQL commands at the SQL prompt:v SQL> Create user PIM identified by PIM default tablespace

users temporary tablespace temp;v SQL> Grant connect, resource, unlimited tablespace, select

any dictionary, query rewrite, create any synonym to PIM;

Setting up Oracle on the application serverAfter you have created a database, set the character sets, created the table spaces,transaction logs, and database schema users, you are ready to install Oracle 11Client on the application server.

About this task

The file tnsnames.ora can be found in the $ORACLE_HOME/network/admin directory.Check connectivity between the application server and database server usingtnsping and/or SQLPlus on the application server.


Note: See the system requirements for details: http://www-01.ibm.com/software/data/infosphere/mdm_server_pim/requirements.html.

Procedure

Install Oracle 11 Client on the application server. Make sure you have an entry ofthe database in tnsnames.ora file on the application server where the Oracle clientis installed.

Installing Oracle XML DB componentYou need to install Oracle XML DB component to store XML documents in thedatabase.

About this task

The Oracle XML DB component is required for IBM InfoSphere Master DataManagement Collaboration Server. This component enables the efficient processingand storage of XML documents in the database. You can perform these steps formanually installing this component. You can also use Oracle's databaseconfiguration assistant for installation. Refer to Oracle documentation athttp://docs.oracle.com/cd/E11882_01/appdev.112/e23094/appaman.htm#ADXDB5700 for more information.

Procedure1. Change directory to $ORACLE_HOME/rdbms/admin in the Oracle database server.2. Log on to SQLPlus using SYS or SYSDBA user sqlplus "/as sysdba"3. Run the catqm.sql script with the following parameters:

v xdb_password is the password for XML DB repositoryv xdb_ts_name is the tablespace to use for Oracle XML DB, it must be

XML_DATAv temp_ts_name is the temporary tablespace, example TEMPv secure_file_for_repo is NO (if you want to use SecureFile LOB then

XML_DATA table space should use Oracle's Automatic StorageManagement).

For example:@catqm.sql pass4xdb XML_DATA TEMP NO

4. Ensure that XML DB installation is successful.

Note: XML DB protocol access is not required for InfoSphere MDMCollaboration Server.

5. In the Oracle initialization parameter file, add the following parameter orensure that the existing value for the compatible parameter is 11.2.0.1. RestartOracle after changing the parameter value to compatible = 11.2.0.1.




Oracle setup checklistYou can check your installation of Oracle against this checklist.

Table 11. Setup check list

X Oracle Setup Check List

Check the Oracle database server release. The version of the Oracle server should be theversion that is identified in the detailed systemrequirements.

Check the database character set. The character set and national character set shouldbe AL32UTF8. Connect as system user and check thecharacter set of the database.

SQL>

select * from nls_database_parameterswhere PARAMETER in (NLS_CHARACTERSET,NLS_NCHAR_CHARACTERSET);

Check the init parameter file entries. Execute the SQLs found in $TOP/bin/db_checklist/oracle_checklist.sql to verify all the init parameterfile entries are set correctly according to InfoSphereMDM Collaboration Server recommendations.

Check the tablespaces setup. Make sure the required table spaces are set up in thedatabase.

Check the redo log files. Make sure there is enough redo log files created inthe database. To get information about existing redolog files in the database, connect as a system userand issue the following query:

select * from v$log;

Check the database user setup. View the database user name and password in$TOP/etc/default/common.properties file and makesure that the database user is created and allrequired privileges are granted to the user. SeeAdding database users and granting permissions formore information.

Check the tnsnames.ora file entry for the database. Make sure there is an entry of the database in thetnsnames.ora file on the application server wherethe Oracle client is installed. The tnsnames.ora filecan be found in the following directory:$ORACLE_HOME/network/admin directory.Note: Due to a limitation in the schema installation,the service name in tnsnames.ora must match theSID of the database; in other words, OCI utilitiessuch as sqlplus must be able to connect using aservice name, which is the same as the SID.

Check the listener on the database server. The database must be accessible from the applicationserver.




Chapter 4. Installing and setting up the application server

Before IBM InfoSphere Master Data Management Collaboration Server will runcorrectly, you must set up the application server.

Exporting and importing LTPA tokens between WAS domainsIf you use more then one server in your environment, and single sign-on isrequired, all of the WAS servers must share the same LTPA key in order to validateand create the LTPA tokens.

About this task

You need to use LTPA keys in order for WAS to digitally sign LTPA tokens.

Procedure1. Log into the local instance admin console.2. Click Security > Secure administration, applications, and infrastructure.3. Click Authentication mechanisms and expiration under Authentication.4. In the Cross-cell single sign-on section, provide the following:

v A password in the Password and Confirm Password fields. This passwordencrypts and decrypts the LTPA keys that are contained in either animported or exported property file.

v A qualified key file name. Ensure that the value is a fully qualified file namethat points to the properties file that you are export the LTPA keys to. Forexample, /opt/IBM/MDM/mdmkeys.properties

v Click Export keys to export the LTPA keys to the fully qualified key filename.

5. Copy the mdmkeys.properties file to the remote server.6. Log into the remote instance admin console and repeat Step 2 and Step 3.7. Provide the fully qualified key file name and password of the LTPA keys.8. Click Import keys to import the LTPA keys from the fully qualified key file

name.

Setting up WebSphere Application ServerBefore you can install IBM InfoSphere Master Data Management CollaborationServer, you must set up your WebSphere Application Server. To set up WebSphereApplication Server, you must install the deployment manager.

Refer to the following topic on WebSphere Application Server information center:http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.installation.base.doc/info/aes/ae/tins_install.html

If you plan to use the clustering and workload management features of WebSphereApplication Server, you must install the deployment manager, as shown in thefollowing figure.


http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.installation.base.doc/info/aes/ae/tins_install.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.installation.base.doc/info/aes/ae/tins_install.html

The figure above shows two profiles:1. Dmgr01 – with dmgr01 for deployment manager2. AppSrv01 – with server1 for a managed node, for example, mdmpimNode01.

Setting up WebLogic ServerBefore you can install IBM InfoSphere Master Data Management CollaborationServer, you must set up your WebLogic Server.

Refer to the WebLogic Server information center: http://download.oracle.com/docs/cd/E12840_01/wls/docs103/sitemap.html

Note: Sun JDK 1.6.0 Update 12 is required for 64-bit WebLogic Application serversupport.

When installing the WebLogic Server, ensure that you perform a custom install.When performing a custom install, you will manually choose which components toinstall. Ensure that the following two components are not chosen:v WebLogic JDBC Driversv Third Party JDBC Drivers

Profile AppSrv01

server1(managed

node)Node Agent

Profile Dmgr01

dmgr01(deployment

manager)

Figure 1. Installing WebSphere Application Server


http://download.oracle.com/docs/cd/E12840_01/wls/docs103/sitemap.html

http://download.oracle.com/docs/cd/E12840_01/wls/docs103/sitemap.html

Chapter 5. Installing the product

You can use the installer, which performs the installation and configuration of theproduct. You can use the Launchpad and Firststeps tools to get started using theproduct.

You perform the product installation in two phases:1. Copying of the product files

Note: InfoSphere MDM Collaboration Server contains certain installationscripts that extract the contents of the $TOP directory. The script is designed toextract the data in a physical drive and not on shared network drives mountedon the server. Therefore, if you have a directory named dir1 and a sharednetwork drive named mount1, and if you try to extract the contents of theinstallation script in the /drive1/mount1 directory, then the script might notwork. In this situation, ensure that you extract the contents from the disk into aphysical drive, for example drive2, and then copy the contents to the/drive1/mount1 directory.

2. Configuring the product:a. Creating the InfoSphere MDM Collaboration Server database and its schemab. Deploying of the .EAR or .WAR file and starting the application on the

application server.

Installation checklist worksheetVerify that you are installing IBM InfoSphere Master Data ManagementCollaboration Server correctly using this installation checklist.

Table 12. Installation checklist

Parameter Description My Value

Installation Directory The directory in which you haveinstalled InfoSphere MDMCollaboration Server. The location ofthis folder is chosen by the systemadministrator. For example:$HOME/mdmpim

If you are migrating to a higherrelease, not a fix pack of the samerelease, you must use a newinstallation directory to avoid .jarfile version mismatches.

Application Server The directory where you haveinstalled the application server. Thelocation of this folder is chosen bythe system administrator. Forexample: /tools/WebSphere/AppServer7_32


Table 12. Installation checklist (continued)


JDK The directory where you haveinstalled the JDK. Typically, this isthe same directory as the WAS orWebLogic's JVM. For example,$WAS_HOME/javaRemember: The bit version of theJDK should be same as the DB2 clientversion. The DB2 client instance thatis used by InfoSphere MDMCollaboration Server should be 64-bitto connect directly to it.

Database Home The directory where the databaseclient is installed. The location of thisfolder is chosen by the systemadministrator. For example:/tools/db2inst1

WAS Nodename The WebSphere Application Servernode name. Nodename is createdpart of application server profilecreation and used in configuringenv_settings.ini. For example:MDMPIMNode

WAS AppServer Name The WebSphere Application Servername is a logical name for theapplication server. Application servername is created part of applicationserver profile creation and used inconfiguring env_settings.ini. Forexample: server1

WAS Vhost Name The WebSphere Application Serverhost name is the domain namesystem (DNS) or the IP address ofthis computer. It is created part ofapplication server profile creationand used in configuringenv_settings.ini. For example:appsrv01

WAS Cell Name The WebSphere Application Servercell name is the generated part of theapplication server profile creationand used in configuringenv_settings.ini. For example:MDMPIMNode01Cell

WAS Profile Name The WebSphere Application Serverprofile name is the name chosen forcreating a profile. At least one profilemust exist to have a functionalapplication installation. For example:AppSrv01

DB Username The database user name

DB Password The database password

DB ClassName The database class name. Use thedefault value.


Table 12. Installation checklist (continued)


AppServer Port The application server port number isthe HTTP transport port.

Default Locale The default locale

WL_HOME The Oracle WebLogic Server homedirectory

CCD_WL_DOMAIN The Oracle WebLogic Server domainname

CCD_WL_DOMAIN_DIR The Oracle WebLogic Server domaindirectory name

CCD_WL_SERVER The Oracle WebLogic Server servername

CCD_WL_PW The Oracle WebLogic Serverpassword

CCD_WL_USER The Oracle WebLogic Server username

Default port numbersDuring the installation of IBM InfoSphere Master Data Management CollaborationServer, ensure that you are aware of the following default port numbers used bythe product.

InfoSphere MDM Collaboration Server default port numbers

In the env_settings.ini file, the product uses the following three default portnumbers:

Table 13. InfoSphere MDM Collaboration Server default port numbers

Port Description Default property Default port number

RMI registry port The Remote MethodInvocation (RMI) registryport.

rmi_port 17507

InfoSphere MDMCollaboration Server

The InfoSphere MDMCollaboration Serverapplication server port.

[appserver.appsvr]port

7507

Global DataSynchronization feature

The Global DataSynchronization feature isan optional port.

[appserver.appsvrgds]port

7527

DB2 default port numbers

To identify the DB2 default port numbers, ensure that you perform the followingsteps:1. From the DB2 server using the instance owner ID, type the following

command:

db2 get dbm cfg |grep SVCE

You will receive output similar to the following:

Chapter 5. Installing the product 47

TCP/IP Service name (SVCENAME) = ldap2svcids

You will either receive a number, such as, 60000, or text. The number is the portnumber that should be used in the db_url property. If you receive text, performthe next step.

2. Type the following command:

grep <text> /etc/services

For example:

grep ldap2svcids /etc/servicesldap2svcids 3700/tcpldap2svcidsi 3701/tcp

3700 is the port number to use in the db_url property. You cannot connect tothe DB2 server remotely if neither text or a number is specified.

Default port numbers for the product services

InfoSphere MDM Collaboration Server services run in WebSphere ApplicationServer. The WebSphere Application Server admin console port number is set by theWebSphere Application Server product installation. See Port number settings inWebSphere Application Server versions for default port numbers.

If you start any of the InfoSphere MDM Collaboration Server services in a debugmode, the following default port numbers are used:

appsvr service: (7507 + 30000 = ) 37507scheduler service: (7507 + 31000 = ) 38507admin service: (7507 + 32000 = ) 39507evenprocessor service: (7507 + 33000 = ) 40507workflowengine service: (7507 + 34000 = ) 41507queuemanager service: (7507 + 35000 = ) 42507

Preparing to install the productBefore you can install IBM InfoSphere Master Data Management CollaborationServer, you must create users, set up your environment, and start your applicationserver.

Procedure1. Check to ensure that all installation requirements are fulfilled for your specific

operating environment.2. Start the database manager and WebSphere Application Server.3. Create a user on the application server with write access to the installation

directory of InfoSphere MDM Collaboration Server.

Note:

4. If you intend to use functions that require messaging and queuing software,you must install WebSphere MQ, specifically the Runtime component and theJava Messaging component. For more information on WebSphere MQ, refer tothe WebSphere MQ information center:http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp .


http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.migration.base.doc/info/aes/ae/rmig_portnumber.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.migration.base.doc/info/aes/ae/rmig_portnumber.html

http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp

5. Install bash in the /bin/bash directory. If using a different shell, such as sh,then execute bash first. See PIM system administrator for more information.

6. Optional: Set these options:v If set -u is set in the automatically generated bash profile, change it to set

+u. The -u option treats the unset parameters as an error.v If you plan on running the installation in a specific locale, set your shell

environment to the specified locale by setting the following environmentvariables:> export LANG=<locale code>> export LC_ALL=<locale code>> export LC_CTYPE=<locale code>

Use the locale -a command to see which locales are available on thesystem, and then select the appropriate one to use. If needed, consult thesystem configuration manuals or your system administrator for help withsetting up the shell for a specific locale.

Setting up the installation mediaThe installation media for installing IBM InfoSphere Master Data ManagementCollaboration Server is available either as physical CDs or as downloadableinstallation image files from Passport Advantage®.

Procedure1. If you obtained InfoSphere MDM Collaboration Server in the form of physical

CDs, check that you have all of the installation disks.2. If you downloaded installation image files for InfoSphere MDM Collaboration

Server from Passport Advantage, uncompress the installation image files intothe desired installation directory.

Installing the product silently using a response fileYou can install IBM InfoSphere Master Data Management Collaboration Serversilently, where the installation choices are provided to you in a response fileinstead of in the panels of the installation wizard. This method is particularlyhelpful when performing multiple installations that are identical.

Before you begin

InfoSphere MDM Collaboration Server utilizes an installer to generate productbinaries. This installer is run using following command:./setup.bin -silent -options options_file_name

Before running this script, ensure that you perform the following steps:1. Check to make sure the /tmp directory has at least 400 MB of space for

installation.2. Ensure that java_home is part of the classpath. For example, if using WebSphere

Application Server, this java_home may be set to WAS_Install_Directory/javadirectory.

About this task

When installing the product silently, you cannot perform post installationconfiguration tasks.


Procedure1. Create the response file. You can use the sample response file to create your

response file. Provide the response file as input when you start the installer.2. Start the installer in silent mode by issuing the following command:

./setup.bin -silent -options options_file_name

Specify the response file you created for the options_file_name.

Sample basic response fileYou can use the following sample basic response file to install IBM InfoSphereMaster Data Management Collaboration Server silently. The stack specifies theapplication server and database products that you are using in your environment.

You can create a response file by recording the parameters from running theinstallation wizard using the -options-record command option. Or, you can createthe response file manually, however, you must ensure that the following requiredparameters are included in the response file:v -P installLocation <valid_installation_directory>

Note: If the -P option is not available in the response file, the installer install theproduct in the /opt/IBM/MDMPIM directory.

v -G licenseAccepted=truev -V stack=<WASDB2 | WASORA | BEAORA>

The stack specifies the application server and database products that you are usingin your environment.

Lines that start with a number sign (#) are considered comments and are ignored.

The following is a sample response file:

## InstallShield Options File## Wizard name: Install# Wizard source: assembly.dat# Created on: Mon Feb 08 15:05:36 PDT 2010# Created by: InstallShield Options File Generator## This file contains values that were specified during a recent# execution of Install. It can be used to configure Install with# the options specified below when the wizard is run with the# "-options" command line option.Read each setting’s documentation# for information on how to change its value.# A common use of an options file is to run the wizard in silent# mode. This lets the options file author specify wizard settings# without having to run the wizard in graphical or console mode.# To use this options file for silent mode execution, use the# following command line arguments when running the wizard:## -options "responsefile_Aix.txt" -silent###########################################################################


############################################################################ Has the license been accepted## The license must be accepted before installation so this value# must be true for the install to be successful.

-G licenseAccepted=false

############################################################################ Stack selection parameter.## The value of this parameter indicates the application# server/database combination you will be using. The following stacks# are supported on this platform: WASDB2 WASORA#

-V stack=WASDB2

############################################################################ IBM InfoSphere Master Data Management Collaboration Server 10.0Install Location## The install location of the product. Specify a valid directory into# which the product should be installed. If the directory contains# spaces, enclose it in double-quotes. For example, to install the# product to C:\Program Files\My Product, use## -P installLocation="C:\Program Files\My Product"#

-P installLocation="/home/pimUser/PIM10.0"

Installing the product using the wizardYou can install IBM InfoSphere Master Data Management Collaboration Serverusing a graphical installer that presents you with installation options in a series ofwizard panels.

Before you beginv Before you install the product using the wizard, make sure the supported JVM

versions (either version 1.4.2, 1.5, or 1.6) are installed on your computer.v If the destination directory is on a system that has an older version of

InfoSphere MDM Collaboration Server, stop the current installation, uninstall theold version, and restart the installer. Refer to the IBM InfoSphere Master DataManagement Collaboration Server Migration Guide for more information.


v The configuration depends on the PERL utility being used. If a proper version ofPERL is not found on the system, the configuration will not proceed and anoption to exit the installer will be displayed.

About this task

Installing the product using the wizard generates a basic response file which youcan use for future installations and upgrades to the product. Enter values in allfields as prompted while configuring the installation of the InfoSphere MDMCollaboration Server to ensure that the installation and configuration take placewithout error.

Procedure1. Start the installer.

a. Open the Launchpad and select the Install Product link. The Launchpadfile is called launchpad.sh and is on the CD that is shipped with theproduct. This file can be found within the Launchpad/disk1 directory. Theinstaller launches in the wizard.

b. Choose Launch the installation application in the right pane.2. Select a language to use for the installation wizard, and click OK.3. At the Welcome screen click Next.4. At the IBM software license acceptance screen, select I accept the terms in the

license agreement and then click Next. The installation program checks yoursystem to determine if the operating system on which the installer is runningis supported. If a message similar to the following displays, you can ignore itand proceed with the installation as long as you have confirmed that youroperating system is support. See the system requirements for a list ofsupported operating systems.

You are attempting to install InfoSphere MDM CollaborationServer on a version of the operating system for which no formaltesting was targeted by release time. You can continue the installation,but be aware that you may encounter difficulties with your particularenvironment. For more details please consult the Release Notes.

5. Select the application server and database combination from the available listof combinations, and click Next. The installation program checks your systemto determine if the necessary software is present and the directory in which itis located.

6. Perform the following during the pre-installation checking:a. Specify that the installation is a new installation and provide a destination

directory for the installation.b. When you see your results from the requirement checking display, click

Next.7. Select your database and application server from the list. Provide values for

the attributes for each and click Next. At the product directory screen,perform one of the following tasks:v In the Directory Name field, type the full path of the directory into which

you want to install InfoSphere MDM Collaboration Server, and click Next.This directory must be the directory that you have given write access toearlier when creating the InfoSphere MDM Collaboration Server user.

v Click Browse to select a directory, and click Next.v Accept the default path, and click Next.



8. The summary screen lists the features that will be installed, the specifiedproduct directory, and the amount of disk space required. Click Next.

9. After the installer completes the installation, click Next. A screen displays amessage about successful product installation and provides you an option toautomatically configure InfoSphere MDM Collaboration Server.

10. Choose Select to Configure InfoSphere MDM Collaboration Server.11. Click Next to complete the installation.

Results

Log details are provided in /tmp/MDMPIMinstallLog.txt file. If the installation failsbefore the installer creates the installation location, you can view the log filedetails. After the installation is successful, ensure that the product version entry isincluded in the version.xml file. You can use this information when you want toupgrade InfoSphere MDM Collaboration Server.


Chapter 6. Configuring the product

You can configure the product manually making sure to set your environmentvariables, your runtime properties, your database drivers, and the applicationserver settings.

About this task

Attention: You must provide all the parameters you are prompted for during theproduct configuration stage. If you fail to provide all the parameters, the productconfiguration will remain incomplete.

Procedure1. Set your environment variables.2. Add the Perl installation directory to your PATH statement.3. Generate and configure the env_settings.ini file.4. Configure the application server.5. Create the schema.

Setting the environment variablesYou must set up specific environment variables in order for IBM InfoSphere MasterData Management Collaboration Server to run successfully.

About this task

Previous versions of InfoSphere MDM Collaboration Server used environmentvariables to store configuration information. InfoSphere MDM Collaboration ServerVersion 10.0 uses a file called <install dir>/bin/conf/env_settings.ini tocontain the configuration. You can create an env_settings.ini file in one of threeways:v Using the deploy.properties.sample Java-style properties file,v Using the <install dir>/bin/conf/env_settings.ini.default templatev Using the <install dir>/bin/conf/deploy.samples sample file.

See “Creating the env_settings.ini file” on page 56 for more information.

Procedure1. Set and export the following environment variables in the InfoSphere MDM

Collaboration Server user's .bashrc file.

PERL5LIB = <install dir>/bin/perllibLANG=<locale value>, for example en_US

Note: Locale C should not be set as a default as it may cause problems whenusing Perl.

Note: For Oracle WebLogic Server installations, additional environmentvariables might need configuring. See the Oracle WebLogic Application Serverinformation center for more information.


2. Logout and login as the InfoSphere MDM Collaboration Server user to pick upthe changes to .bashrc file.

What to do next

You need to set up the env_settings.ini file.

Creating the env_settings.ini fileIf you installed the product manually and you did not use the installer application,you need to create the env_settings.ini file manually. You will also need to editthe file.

Before you begin

Ensure that you have run the <install dir>/setup.sh script before creating theenv_settings.ini file.

About this task

See How to configure the env_settings.ini file to watch an educational video aboutcreating and modifying the env_settings.ini file.

Procedure1. Copy the <install dir>/bin/conf/env_settings.ini.default file as:

<install dir>/bin/conf/env_settings.inicp <install dir>/bin/conf/env_settings.ini.default<install dir>/bin/conf/env_settings.ini.default

2. Set the appropriate environment parameters.

Setting the common parameters in the env_settings.ini fileAfter you create the env_settings.ini file, you need to set the commonparameters.

Procedure1. Open the env_settings.ini file.2. Set the following parameters:

java_homeThe path of Java home.

jar_dirThe location of the third-party JAR files.

encrypt_passwordOptional: If you choose to encrypt the database password, add theencrypt_password parameter to the [db] section, set it to yes, andremove the password parameter from the [db] section.

Configuring cache parametersYou must configure a few cache parameters in order for IBM InfoSphere MasterData Management Collaboration Server to be able to use a unique multicastaddress for its cache system.


http://publib.boulder.ibm.com/infocenter/ieduasst/imv1r0/topic/com.ibm.iea.mdmcs/mdmcs/10.0/Configuration.html

About this task

InfoSphere MDM Collaboration Server uses a distributed cache. A distributedcache uses an IP multicast. Multicast addresses are typically in the 239.0.0.0 to239.255.255.255 range. Refer to your network administration to determine thecorrect multicast address.

Procedure1. Open the env_settings.ini file, and go to the [cache] section.2. Set the following parameters:

multicast_addrThe multicast address that the cache system uses.

multicast_ttlTime-to-live multicast parameter needs to be set to 0 for single-systeminstallations and 1 for clusters.

Setting the common database parametersIn order to set up the database, you need to configure the database type andcommon parameters, as well as, configure the database type-specific parameters.

You need to set the following parameters regardless of the database you are using:

type Possible values are DB2 or Oracle.

home The database home directory.

usernameThe user name to connect to database.

passwordThe password to connect to database.

Note: Decide if the database password is to be stored in an encryptedformat or plain format and set the encrypted_password parameter in theenv_settings.ini file accordingly.

hostnameThe host name of the DB2 or Oracle server.

port The port the database server listens on.

Storing database passwords in an encrypted formatFor audit and security purposes, a best practice is to always store sensitiveinformation, such as passwords, in an encrypted format.

About this task

There are other database related scripts, for example, schema and companycreation and deletion scripts, migration scripts and maintenance scripts require theargument dbpassword if the encrypt_password parameter is set to yes in theenv_settings.ini file. If the argument is not passed, you will be prompted for thedatabase password. If the encrypt_password parameter is set to no or is not set atall, you can run the scripts without the dbpassword argument. Depending on thevalue of the encrypt_password parameter, the db.xml file will store either the plaintext password or encrypted password.

Chapter 6. Configuring the product 57

Procedure1. Add the encrypt_password parameter to the [db] section of the

env_settings.ini file.2. Set the encrypt_password parameter to yes if you want the password to be

encrypted.

Note: If you do not want to encrypt the password, keep the passwordparameter, as is, in the [db] section.

3. Run bin/configureEnv.sh -dbpassword=<database password>. You will beprompted to enter the password if it is not given as an argument, for example,if --overwrite option is not used. If --overwrite option is not used, a warningwill be given to tell the user to run the script with the dbpassword argument. Ifthe encrypt_password parameter in the env_settings.ini file is not set or set tono, the dbpassword argument is not required for the configurEnv.sh script. Itcan be run as previously.

4. Confirm that this script created the db.xml file in the $TOP/etc/defaultdirectory. This step is very important since this is the only place from wherethe Java code can read the encrypted password or plain text password and usethe decrypted password in a JDBC connection.

5. Whenever any of the database related properties in the [db] section of theenv_settings.ini file are changed, run bin/configureEnv.sh-dbpassword=<database password> to recreate the db.xml file. You will beprompted to enter the password if its not given as an argument. In this case, ifthe encrypt_password parameter in the env_settings.ini is not set or set to no,the dbpassword argument is not required for the configurEnv.sh script. It canbe run as previously.

6. Confirm that this script created the db.xml file in the $TOP/etc/defaultdirectory. This step is very important since this is the only place from wherethe Java code can read the encrypted password or plain text password and usethe decrypted password in a JDBC connection.

7. With this change, if you need to create IBM InfoSphere Master DataManagement Collaboration Server schema, invoke create_schema, for example:

bin/db/create_schema.sh -dbpassword=<database password>

You will be prompted to enter the password if its not given as an argument. Ifthe encrypt_password parameter in the env_settings.ini file is not set or is setto no, the dbpassword argument is not required for the scripts. They can be runas previously.

8. Run bin/test_db.sh -dbpassword=<database password>. You will be promptedto enter the password if its not given as an argument. If the encrypt_passwordparameter in the env_settings.ini file is not set or is set to no, the dbpasswordargument is not required for the scripts. They can be run as previously.

9. Start the services.

Setting DB2 parametersEnsure you set the following DB2 parameters.

About this task

DB2 provides a JDBC driver, which can be used either in Type 2 architecture orType 4 architecture. You can use either architecture with IBM InfoSphere MasterData Management Collaboration Server.


Procedure1. You need to configure the [db.<type>] section which corresponds to the value

of type in the database section. For example, if you are using DB2, set type=db2in the database section and configure the [db.db2] section.

2. Configure the JDBC driver type parameter in the [db] section for DB2.a. For Type 4 architecture:

1) Type 4 architecture is the default type.2) Set the jdbc_driver_type parameter to 4.3) Set the port parameter in the [db] section to the port the DB2 listener is

on. Ask your database administrator for the port.b. For Type 2 architecture:

1) Set the jdbc_driver_type parameter to 2. The port and hostnameparameters in the db.db2 section are ignored.

3. Configure the [db.db2] section for DB2. Set the following parameters:a. Set the following parameters in the [db.db2] section.

alias This parameter is in the [db.db2] section in the env_settings.ini file.This parameter is used by the CLP and the JDBC Type 2 drivers. It isthe alias the CLP uses in the CONNECT statement.

db_nameThis parameter is in the [db.db2] section in the env_settings.ini file. Thedb_name parameter defaults to the value of the alias parameter,therefore, db_name needs to be set only when the name of the databasediffers from the alias the client uses. This parameter is only used forType 4 connections.

Example

Here is a simple example if you were using a Type 4 connection, you would havethe following:

Client alias = ’mydb’, db name = ’mydb’

[db]type-=db2username=dbuesrpassword=somepwdhome=/home/db2inst1/sqllibhostname=my-dbserver.company.comport=60004jdbc_driver_type=4

[db.db2]alias=mydb

Here is an example using a Type 4 connection when the alias is different from thedb name:

Client alias = ’mydb’, db name = ’mdmpim’[db]type-=db2username=dbuesrpassword=somepwd


home=/home/db2inst1/sqllibhostname=my-dbserver.company.comport=60004jdbc_driver_type=4

[db.db2]alias=mydbdb_name=mdmpim...

Here is a simple example if you were using a Type 2 connection, you would havethe following:

[db]type-=db2username=dbuesrpassword=somepwdhome=/home/db2inst1/sqllib#hostname=my-dbserver.company.com#port=60004jdbc_driver_type=2

Setting Oracle parametersEnsure you set the following Oracle parameters.

About this task

Oracle supports the following JDBC driver types:

thin This is the default type.

OCI The OCI driver allows the use of TAF (Transparent Application Failover)for RAC (Real Application Cluster) installations.

You can use either driver type with IBM InfoSphere Master Data ManagementCollaboration Server.

Procedure1. You need to configure the [db.<type>] section which corresponds to the value

of type in the database section. For example, if you are using Oracle, settype=oracle in the database section and configure the [db.oracle] section.

2. Configure the [db] section for Oracle.a. Set the JDBC driver type. Set the driver type to either thin or OCI.

3. Configure the [db.oracle] sections for Oracle.

instanceThe name of the Oracle instance. The instance used in the JDBCconnect string and the SQLPlus connect string if the tns_nameparameter is not set.

tns_nameThis parameter is in the [db.oracle] section in the env_settings.ini file.The TNS name is used by SQLPLus to connect to the database. Set thisonly if the SQLPlus uses a different name to connect to the databaseother than JDBC. This parameter defaults to the value of the instance


parameter, therefore, tns_name only needs to be set when the clientconnection differs from the SID of the database.

SID This parameter is in the [db.oracle] section in the env_settings.ini file.

Example

Here is a simple example:

(Database SID = ’mydb’, client uses ’mydb’ to connect using sqlplus

[db]type-=oracleusername=dbuesrpassword=somepwdhome=/opt/oracle/app/product/11.1.0/db_1hostname=my-dbserver.company.comport=1525

[db.oracle]instance=mydb

Here is an example where the sqlplus is different from SID:

(Database SID = ’mdmpim’, client uses ’mydb’ to connect using sqlplus

[db]type-=oracleusername=dbuesrpassword=somepwdhome=/opt/oracle/app/product/11.1.0/db_1hostname=my-dbserver.company.comport=1525

[db.oracle]instance=mydbtns_name=mdmpim

Setting up Oracle to use the OCI driversThe OCI is an application-programming interface to Oracle databases. It consists ofa library of C language routines to allow C programs (or programs written in otherthird generation languages) to send SQL statements to the database and interactwith it in other ways. The OCI driver allows the use of TAF (TransparentApplication Failover) for RAC (Real Application Cluster) installations. You need toset up and configure support for the OCI driver for Oracle, and change the IBMInfoSphere Master Data Management Collaboration Server environment settings.

Before you begin

Ensure that the Oracle client is installed. See the system requirements for details:http://www-01.ibm.com/software/data/infosphere/mdm_server_pim/requirements.html.




Procedure

Add the following environment variables in ..bashrc or .bash_profile file in IBMInfoSphere Master Data Management Collaboration Server.v $ORACLE_HOME - This is the directory where Oracle client software is

installed.v $LD_LIBRARY_PATH - This a environment variable for Sun and Linux®. Use

$LIBPATH for AIX® and $SHLIB_PATH for HPUX.v $PATH

For example, the environment variables in .bashrc or .bash_profile file will looklike:export ORACLE_HOME=/opt/oracle/11g/client_1export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATHexport PATH=$ORACLE_HOME/bin:$PATH

Configuring the application server parametersOnce you install the product and have set up and configured your database, youcan perform additional configurations of the application server. After theinstallation is configured, use the shell scripts in the <install_dir>/bin/godirectory to start, stop, and abort InfoSphere MDM Collaboration Server.

Configuring the application server requires three steps. In the env_settins.ini file:1. Set the appserver type and common properties in the [appserver] section.2. Configure the parameters for the appserver type in the [appserver.<type>]

section.3. Configure the parameters for each appserver service in the

[appserver.<service name>] section.4. Add the security properties username and password to the [appserver] section.

Setting the common application server parametersIn order to set up the application server, you need to configure the applicationserver type and common parameters, as well as, configure the applicationtype-specific parameters.

Procedure

Set the following parameters in the [appserver] section of the env_settings.ini file:

type Possible values are websphere70 or weblogic103.

home The home directory of the appserver.

rmi_portThe RMI port.

What to do next

See “Setting WebSphere Application Server parameters” or “Setting OracleWebLogic Server parameters” on page 64 depending on which application serveryou are using.

Setting WebSphere Application Server parametersIf you are using WebSphere Application Server as your application server forrunning IBM InfoSphere Master Data Management Collaboration Server, you must


verify the configuration settings, start the application server, configure group andserver settings, run some scripts, and then start the application server.

Before you begin

Before you can set up InfoSphere MDM Collaboration Server, you must ensure thatit is configured.

Procedure1. Configure the [appserver.websphere70] or [appserver.websphere80] section

with the following parameters:

application_server_profileThe name of the WebSphere Application Server profile.

cell_nameThe name of the WebSphere Application Server cell where InfoSphereMDM Collaboration Server will be installed.

node_nameThe name of the node in the WebSphere Application Server cell whereInfoSphere MDM Collaboration Server will be installed.

admin_securitySet this parameter to true if WebSphere Application Serveradministrative security is enabled.

2. Configure the [appserver.appsvr] section with the following parameters:

port The port that InfoSphere MDM Collaboration Server runs on.

appserver_nameThe name of the WebSphere Application Server component which willbe created in a later step.

vhost_nameThe name of the WebSphere Application Server virtual host componentwhich will be created in a later step.

3. Add the security parameters username and password to the [appserver] section.For example:

[appserver]# type must match an appserver sectiontype=websphere70rmi_port=17507## Application server admin user name and password. This info isrequired for Weblogic; it is also required for WebSphere when admin_securityin [appserver.websphere70] section is set to true.#username=#password=## must be absolute pathhome=/opt/IBM/WebSphere

Note: If you choose not to save the credential information in theenv_settins.ini file, you can provide it from the command line. To providethe credentials from the command line, perform the following steps:


a. Redeploy InfoSphere MDM Collaboration Server to the application server.The application server shell script, install_war.sh, installs InfoSphere MDMCollaboration Server into the WebSphere application server.

b. Ensure that the default WebSphere Application Server (server1) is installedand running. You also need to verify that you can log into the server. Formore information about the default WebSphere application server, see theadministration information in the WebSphere Application Serverinformation center at: http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp

c. Run the application server shell script, install_war.sh, with optionalparameters, which is located in the $TOP/bin/websphere/ directory:

Syntaxinstall_war.sh [ --wsadminUsername=<WAS admin user name> --wsadminPwd=<password for WAS admin user>]

The install_war.sh script will install the WAR file for each appserver defined in the [services] section in env_settings.ini. WhenWebSphere Application Server security is enabled, add thewsadminUsername and wsadminPwd arguments to the install_war.shcommand.

Note: When WebSphere Application Server security is enabled, thefollowing arguments are no longer required in the$TOP/bin/start_local.sh, $TOP/bin/start_rmi_appsrv.sh,$TOP/bin/stop_local.sh, and $TOP/bin/rmi_status.sh commands:

--wsadminUsername=<WAS admin user name> --wsadminPwd=<password for WAS admin user>

d. Optional: If you want to install GDS feature along with InfoSphere MDMCollaboration Server installation, you need to run the application servershell script for GDS, install_gds_war.sh, which is located in the$TOP/bin/websphere/ directory:

Syntaxinstall_gds_war.sh

Setting Oracle WebLogic Server parametersBefore you can configure the Oracle WebLogic server, you must configure IBMInfoSphere Master Data Management Collaboration Server successfully bymodifying the environment variables.

Procedure1. Modify the following parameters for the appserver service in the

env_settings.ini file. Type the following:a. In [appserver.weblogic103] Set the following parameters:

domain_namethe name of the Oracle WebLogic domain where InfoSphere MDMCollaboration Server will be installed.

domain_dirThe root of the domains directory.

admin_portThe port the Oracle WebLogic Server administration server listenson.

admin_serverHost name of the machine where the admin server runs.


http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp

http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp

server_nameThe host name of the system which runs InfoSphere MDMCollaboration Server.

usernameUsername which has admin permissions on the InfoSphere MDMCollaboration Server Oracle WebLogic domain.

passwordPassword for the admin user.

b. In [appserver.appsvr] Set the port to the HTTP port InfoSphere MDMCollaboration Server will be available on.

2. Add the security parameters username and password to the [appserver] section.For example:

[appserver]# type must match an appserver sectiontype=websphere70rmi_port=17507## Application server admin user name and password. This info isrequired for Weblogic; it is also required for WebSphere when admin_securityin [appserver.websphere70] section is set to true.#username=#password=## must be absolute pathhome=/opt/IBM/WebSphere

Note: If you choose not to save the credential information in theenv_settins.ini file, you can provide it from the command line. To providethe credentials from the command line, perform the following steps:a. Redeploy InfoSphere MDM Collaboration Server to the application server.b. Follow steps 1, 4, 5, and 6 in the following topic Configuring Oracle

WebLogic Server in the information center.3. Save your changes.

Configuring WebSphere MQ parametersFor IBM InfoSphere Master Data Management Collaboration Server functions thathave dependencies on WebSphere MQ to work, you need to update theenv_settings.ini file.

Procedure1. Open the env_settings.ini file, and go to the [mq] section.2. Set the following parameters:

enabledSet to yes to enable the support for functions which have dependencieson MQ.

home The installation directory of the WebSphere MQ client. Lowest versionrequired is 7.0.1.

3. Save your changes.


Validate the environmentBefore you can configure the application server, you need to verify that yourenvironment is installed and configured properly.

About this task

This script needs to only be run once.

Procedure1. Go to the <install_dir> directory.2. Run the <install_dir>/setup.sh script. This script does the following:

v Checks if the database client is configured.v Validates the Perl installation and notifies you of any missing Perl modules.

Note: If any Perl modules are missing, install those Perl modules and runthis script again.

Configure the installationBefore you can configure the application server, you need to configure theinstallation.

About this task

The configureEnv.sh script does the following:v validates the env_settings.ini file and notifies you if there are any errors.v generates the configuration for IBM InfoSphere Master Data Management

Collaboration Server servicesv generates the installation.txt file for the WebLogic environmentv generates a <install dir>/build/build.properties file for Antv generates the common.properties file

Note: Comments inside the common.properties file will be stripped afterrunning the configureEnv.sh script. If you want to catch the descriptions foreach property, refer to the common.properties.default file.

Note: If the common.properties file does exist, a warning message is reportedand displays the missing properties which exists in thecommon.properties.template file. If the common.properties file does not exist,you can either copy the properties from the common.properties.default file ordelete the common.properties file and run the configureEnv.sh script to generatea new one.

You must run this script after a change is made to the env_settings.ini file or theaddition of any JARs to the JAR directory in an enterprise installation.

Procedure1. Go to the <install dir>/bin directory.2. Run the <install dir>/bin/configureEnv.sh script.


Using the compatibility scriptsUse the compatibility scripts to add some of the old environment variables used inprevious versions of IBM InfoSphere Master Data Management CollaborationServer. The variables include $TOP, $CCD_DB, and $JAVA_RT.

Procedure

Add the following compatibility script lines to the .bashrc:

rootDir=`perl $PERL5LIB/getTop.pl`source $rootDir/bin/compat.sh

Configuring the application serverTo run IBM InfoSphere Master Data Management Collaboration Server successfully,you must configure either WebSphere Application Server or the Oracle WebLogicServer.

Configuring WebSphere Application ServerIf you are using WebSphere Application Server as your application server forrunning IBM InfoSphere Master Data Management Collaboration Server, you canconfigure the application server using these steps.

Before you begin

If you are installing the product on AIX, you must increase the size of the ncargsparameter to accommodate the long list of arguments that our product installationrequires. Issue the following command: chdev -l sys0 -a ncargs=NewValue.NewValue can be a value from 6 (the operating system default) to 128 andrepresents the number of 4K blocks to be allocated for the argument list.

Procedure1. Add a WebSphere Application Server group. This group will be used to grant

permissions in ${WAS_HOME} which is necessary for the InfoSphere MDMCollaboration Server application server. Some examples of group names are:wasgrp, wasgroup, or pimgroup.On AIX server, you can add a group using the SMIT administration tool. Formore information about creating a group and setting permissions for the group,see your operating system documentation. Ensure that the InfoSphere MDMCollaboration Server user is always part of the WebSphere Application Servergroup.

2. Add the InfoSphere MDM Collaboration Server user to the group created in theprevious step. To check group membership, run the id command from theUNIX command prompt as the InfoSphere MDM Collaboration Server user. Ifthe group is not in the list of groups, log out, log in, and run the id commandto check an ID again.

3. Start the WebSphere Application Server default server. To start the WebSphereApplication Server default server, issue the following command as root:${WAS_HOME}/bin/startServer.sh server1

4. In the WebSphere administration console, change the umask for the server1process to 002. In the Run as group text box for server1, set the text box to thegroup created in the first step.


5. Stop the WebSphere administration console. To stop the administration console,issue the following command as root:${WAS_HOME}/bin/stopServer.sh server1

6. Change the permissions on the WebSphere Application Server directory so thatthe group has write permission:# chgrp -R wasgroup (WAS_HOME) # chmod -R g+rw (WAS_HOME)

Note: WAS_HOME will not be defined here because you must run thecommands as root. You must manually enter the WebSphere Application Serverinstallation path, for example: chmod -R g+rw /opt/IBM/WebSphere/AppServer.The group used here must be the same as the one you set up in step 4.

7. Start the application server and the administrative console. To start theWebSphere Application Server, issue the following command as root:${WAS_HOME}/bin/startServer.sh server1

Generally, InfoSphere MDM Collaboration Server is installed on the rootdirectory of WebSphere Application Server but some installations use aninstallation ID (such as wasadmin) to run the WebSphere Application Serverconsole.

8. After installing InfoSphere MDM Collaboration Server, and after performing theprevious configuration steps, run the following scripts in the listed order:a. $TOP/bin/websphere/create_vhost.sh. You will be prompted to create two

virtual hosts, if GDS is also configured in the env_settings.ini file. Createtwo virtual hosts .

b. $TOP/bin/websphere/create_appsvr.sh. You will be prompted to create twoapplication servers, if GDS is also configured in the env_settings.ini file.Create two application servers.

c. $TOP/bin/websphere/install_war.sh. You will be prompted to install theapplication server configured for IBM InfoSphere Master Data ManagementCollaboration Server in the [appserver.appsvr] section of theenv_settings.ini file. Install InfoSphere MDM Collaboration Server on thedefault application server (appsvr_<SERVER_NAME>).

d. $TOP/bin/websphere/install_gds_war.sh. You will be prompted to installthe application server configured for Global Data Synchronization in the[appserver.appsvr] section of the env_settings.ini file. Install Global DataSynchronization on the application server (appgds_<SERVER_NAME>.

Configuring Oracle WebLogic ServerConfiguring Oracle WebLogic Server is a two-step process. You must create aserver domain and a domain component

Create Oracle WebLogic Server domain for InfoSphere MDMCollaboration ServerPrior to deploying Oracle WebLogic Server by running the configuration file, youmust create a domain for Oracle WebLogic Server.

Before you begin

Before you can deploy Oracle WebLogic Server by running the configuration file,you must:v Ensure that WebLogic is installed.


v If WebLogic is installed by the root user, ensure that the IBM InfoSphere MasterData Management Collaboration Server user has write permissions on the <beahome>/wlserver_10.3/nodemanager directory and the files within it.

v Ensure that Sun JDK 1.6 is installed.

Procedure1. As the InfoSphere MDM Collaboration Server user, run the /opt/bea/

wlserver_10.3/common/bin/config.sh script.2. Select Create a new WebLogic domain. Click Next.3. Select Generate a domain configured automatically. Click Next.4. Provide a user name and password.

Remember: Ensure that you remember your user name and password. Youwill need this information to configure your InfoSphere MDM CollaborationServer server.

5. Select Production mode and choose your Sun JDK. Click Next.6. Select Yes and click Next.7. Accept the defaults and click Next.8. Click Add and provide the following values:

v In the Listen port field, provide your InfoSphere MDM Collaboration Serverport

v In the Server name field, type ccd_server

Note: Do not check SSL enabled.

Remember: Ensure that you remember your port and server name values.v Click Next.

9. Click Next to bypass the Configure clusters window. Do not change anythingon this window.

10. Select the Unix machine tab and click Add. Type your system's hostname inthe name box field and click Next.

11. Add AdminServer and ccd_server values to your system's hostname and clickNext.

12. Click Next to bypass the Review window.13. Type you WebLogic domain path in the Domain name field and click Next.

Remember: Ensure that you remember the domain path. You will need thisinformation to configure your WebLogic server.

14. Click Done.

Configuring Oracle WebLogic ServerIf you are using Oracle WebLogic Server as your application server for runningIBM InfoSphere Master Data Management Collaboration Server, you can configurethe server using these steps.

Before you begin

Ensure that you have the $TOP/etc/default/weblogic103/installation.txt file.This file contains the Oracle WebLogic Server information customized for thisinstallation. This file was generated when you ran the configureEnv.sh script.


Procedure1. Start the AdminServer.

a. Open a command prompt and access to your domain directory. Yourdomain directory was used in setting up your Oracle WebLogic Server.

b. Run the script startWebLogic.sh.c. Provide your user name and password. Your username and password

should be the same that you used when you set up your Oracle WebLogicServer.

d. After you see <Server started in RUNNING> mode, open a browser and goto http://localhost:7001/console.

e. Log in again using the same user name and password.2. Create a Startup class for ccd_server.

a. Click Lock & Edit.b. Click Startup and Shutdown classes.c. Click New.d. Select Startup class and click Next.e. In the Startup class section of the installation.txt file, provide values for

fields and click Next.f. Select ccd_server in the servers table and click Finish.g. Click Activate Changes to apply changes.

3. Configure the ccd_server.a. Click Lock & Edit.b. Click Servers, then click ccd_server in the table.c. In the Configuration tab, click Server start.d. In the Server start section of the installation.txt file, provide values for the

fields and click Save.e. Click back on General.f. Click Activate Changes to apply changes.

4. Delete the application if you have a previous installation of InfoSphere MDMCollaboration Server application.a. Click Lock & Edit.b. Select the checkbox for the InfoSphere MDM Collaboration Server

application.c. Click Delete.d. Click Yes to confirm the deletion of the deployment.e. Click Activate Changes to apply changes.

5. Create a new deployment.a. Click Lock & Edit.b. Click Deployments.c. Click Install.d. Copy the value of the deployment path from the installation.txt file into the

Path field. Click Next.e. Select the Install this deployment as an application radio button. Click

Next.f. Select ccd_server. Click Next.g. Update the Name field using the value of the deployment name from the

installation.txt file. Click Next.


h. Select the No, I will review the configuration later. radio button. ClickFinish.

i. Click Activate Changes to apply changes.6. Start the deployment.

Note: These steps enable the InfoSphere MDM Collaboration Server Server tostart without the AdminServer in the future. You must start the WebLogicservers at least once with the AdminServer so that the WebLogic servers arereachable to copy configuration settings from the AdminServer.a. Run the start_local.sh or start_rmi_and_appserver.sh scripts to start the

InfoSphere MDM Collaboration Server appserver service. Running thestart_local.sh script starts other services in addition to the appserver service.

b. Run the rmi_status.sh script to confirm that the appserver service is started.c. Click Deployments in the WebLogic Server Administration Console.d. Select the ccd check box in the Deployments table.e. Click Start > Servicing all requests. Click Yes.

Deploying the product in a cluster environmentYou can use deployment scripts to deploy IBM InfoSphere Master DataManagement Collaboration Server in a clustered environment. You use theWebSphere Application Server Deployment Manager to deploy InfoSphere MDMCollaboration Server.

Overview of clustering and workload managementIBM InfoSphere Master Data Management Collaboration Server uses the clusteringand workload management features by WebSphere Application Server.

InfoSphere MDM Collaboration Server supports the deployment of the InfoSphereMDM Collaboration Server product in this clustered environment as shown in thefollowing figure.


Deploying InfoSphere MDM Collaboration Server usingWebSphere Application Server Deployment Manager

Before you can deploy IBM InfoSphere Master Data Management CollaborationServer, you must configure your application server, create a cluster, configure yourhost, sync the application servers, and restart the cluster and InfoSphere MDMCollaboration Server.

Before you begin

Ensure you performing the following prerequisites:v Start the WebSphere Application Server Deployment Manager before installing

InfoSphere MDM Collaboration Server and creating the cluster.

Important: Ensure that you do not use the install_war.sh script on an existingcluster or cluster member. If you run this script on an existing cluster or clustermember, a failed error message is displayed.

Important: Before the deployment, ensure that only server1 exists. If any otherservers exist, delete it.

v Ensure that you “Setting up WebSphere Application Server” on page 43v If you are using IBM WebSphere MQ, ensure you have installed WebSphere MQ

Client on all instances of InfoSphere MDM Collaboration Server on every cluster.

About this task

Deploy InfoSphere MDM Collaboration Server using WebSphere ApplicationServer Deployment Manager:

WebSphere Application Server ND

InfoSphere MDMCollaboration Server

Cluster

server3

server2

server1

Node Agent

Deployment Manager LDAP

InfoSphereMDM

CollaborationServerData

Admin

Workflow

Scheduler

EventPro

QueueMgr

Figure 2. Cluster deployment for InfoSphere MDM Collaboration Server


Procedure1. Deploy the application on the application server. For more information, see

“Configuring WebSphere Application Server” on page 67.a. Ensure server1 is used in the env_settings.ini file. For example:

[appserver.websphere70] or [appserver.websphere80]application_server_profile=mdmpimcell_name=mdmpimNode01Cell

node_name=mdmpimNode01# set security to true if administrative security is enabled.Defaults to false if not setadmin_security=false

[appserver.appsvr]port=9080# for websphere, add appserver_name and vhost_nameappserver_name=server1vhost_name=mdmpim_vhost

Since server1 is already created, the step for create_appsvr.sh can beskipped.

b. Install InfoSphere MDM Collaboration Server to the application serverserver1.

c. Log in to InfoSphere MDM Collaboration Server: http://<hostname>:<port>/utils/enterLogin.jsp

2. Create the cluster with one existing application server. Refer the following topicin the WebSphere Application Server information center: http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/trun_wlm_cluster_v61.html A new cluster is created with one member that isconverted from the application server server1.

3. Create additional application servers. See the following topic in the WebSphereApplication Server information center: http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/trun_wlm_member.html Create additional members, for example, server2 atport 9081 and server3 at port 9082, in the cluster.

4. Configure the virtual host. See the following topic in the WebSphereApplication Server information center: http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/tcws_plugin_vhost.html Configure the virtual host mdmpim_vhost with hostaliases for all cluster members (hostnames/ports) on the WebSphereApplication Server admin console, for example:v *:9080 - for server1v *:9081 - for server2v *:9082 - for server3

5. Sync all of the application servers. Before restarting all of the cluster members,do a full synchronization and populate the application on server1 to all otherservers, that is, server2 and server3. See the following topic in the WebSphereApplication Server information center: http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/uagt_rnodes.html Select the node used for this application, for example,mdmpimNode01, and click Full Resynchronize. For more information about Full


http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/trun_wlm_cluster_v61.html




http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/trun_wlm_member.html



http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/tcws_plugin_vhost.html



http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/uagt_rnodes.html



Resynchronize, see http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tagt_svr_conf_nodes.html.

6. Restart the cluster.a. Stop the cluster. See the following topic in the WebSphere Application

Server information center: http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/trun_wlm_cluster_stop.html. For example, select the cluster MDMPIM and clickStop. All servers (members) are stopped.

b. Start the cluster. See the following topic in the WebSphere ApplicationServer information center:http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/trun_wlm_cluster_start.html. For example, select the cluster MDMPIM and clickStart. All servers (members) are started.

7. Stop and start servers server1, server2 and server3.a. Stop all of the servers. For more information, see Stopping the product.b. Start all of the servers. For more information, see Starting the product.

Configuring runtime propertiesYou must set a few runtime properties in the common.properties file as part ofconfiguring IBM InfoSphere Master Data Management Collaboration Server. Formore information about these parameters, see the comments in thecommon.properties file.

About this task

A compatibility script, for example, configureEnv.sh, supports limitedbackwards-compatibility. This script create the shell scripts, compat.sh in the<install dir>/bin directory. This script, compat.sh contains the most-commonlyused environment variables from the pre-6.1 configuration. Additionally, a perlscript <install dir>/bin/perllib/getTop.pl can be used to get the absolute path to<install dir>.

The script configureEnv.sh generates the common.properties file from the values inthe env_settings.ini file. The common.properties file must be customized after theconfigureEnv.sh script is run and before InfoSphere MDM Collaboration Server isstarted for the first time.

Procedure1. If you are using FTP, set the directory for using FTP for import operations by

specifying the FTP_root_dir parameter.2. Set the temporary directory by specifying a value for the tmp_dir parameter.

The directory /tmp is the default.

What to do next

See “Creating a schema” on page 75 for what to do next.

Running schema creation scriptsAfter you have installed the application server, the database and the IBMInfoSphere Master Data Management Collaboration Server application, you mustrun the scripts to create the schema for the database.


http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tagt_svr_conf_nodes.html



http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/trun_wlm_cluster_stop.html



http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/trun_wlm_cluster_start.html



Creating a schemaIBM InfoSphere Master Data Management Collaboration Server provides a scriptthat you use to create the schema for your database.

Before you begin

Before you can create a schema, you must:v Create valid tablespace names and ensure that they are valid.v Ensure database connectivity.

.

About this task

If you run the create_schema.sh script without the tablespace option, all tables andindexes will be created in the default table spaces USERs and INDX only. If youhave created all buffer pools and table spaces as outlined in the Creatingtablespaces topic, make sure to use an appropriate tablespace mapping file.

The <install dir>/bin/db/analyze_schema.sh runs the native database schemaanalyzer.

Procedure1. Use the following shell script to create the schema: <install

dir>/bin/db/create_schema.sh. It creates a log file called <installdir>/logs/schema.log.Attention: When you run the create_schema.sh script, errors are notdisplayed. Ensure that you review the log file to view any errors.

Note: Only run create_schema.sh once. If you run create_schema.sh on anexisting schema, you will replace it with an empty schema.

2. Optional: You can specify the --tablespace argument to specify a table spacename mapping file that shows the customized table space names for therequired table spaces: create_schema.sh --tablespace=<tablespace namemapping file>. If you do not specify the argument--tablespace=tablespace_name_mapping_file on the command line when you firstrun the create_schema.sh script, all tables and indexes will be created in thedefault table spaces USERS and INDX. If you do not specify the argument--tablespace=tablespace_name_mapping_file in a later run, the name used for theprevious create schema operation will be used. See “Table space name mappingfile” on page 76 for more information.

3. Review the log file after executing the create_schema.sh command to check forerrors.

Custom table space namesThe create schema script has been enhanced to take user-defined table space namesas parameters when creating schema.

By default, the system uses the default table space names users and indx. Manycomponents create tables and indexes dynamically using the default table spacenames. Next section describes overriding default table space names.

This custom table space functionality addresses the deployment issues and is fornew installations only, so there are no migration issues. If you have an existing


system deployed, your DBA must manually change the table space names for thecore database schema that were created by the ‘create_schema' scripts. Customtable space names for dynamically created tables and indexes can be entered incommon.properties file. If you have an existing system deployed, you need to plana downtime with your DBA for having different custom table space names.

Default table space names:

IBM InfoSphere Master Data Management Collaboration Server defines defaulttable space names, which are set and can be changed in the common.properties file.

Three table space names are hard-coded:

users for all tables except table ‘tdoc_dbl_doc_blob';

blob_tbl_datafor the table ‘tdoc_dbl_doc_blob' ONLY;

indx for index created for some of the tables/columns;

The default table space names can be changed through system configuration file:

$TOP/etc/default/common.properties

You can change these default table space names on these parameters in this file:user_tablespace_nameindex_tablespace_nameblob_tablespace_name

For example:user_tablespace_name=pim_dataindex_tablespace_name=pim_indexblob_tablespace_name=pim_blob

In this example pim_data, pim_index, pim_blob will replace users, indx andblob_tbl_data table spaces respectively. These table spaces will be used as defaulttable spaces in create_schema.sh, and for dynamically created tables.

These three entries are optional. If any of them is not defined, the hard-codeddefault values are used.

The default table space names must exist before installing InfoSphere MDMCollaboration Server. If you are using the default table space names, these mustexist in the database before installing the product. If you are going to usecustomized table space names, or you intend to modify them in the systemconfiguration file, these table space names must exist before installing the product.

Table space name mapping file:

A tablespace mapping file is used to define in which table space data and indexesfor a specific table will be stored. This file is a comma-delimited text file that mapsthe tables, table spaces, and index tables together, when you want to customizeyour table space names for specific tables.

In production environments it is recommended to use the table spaces as outlinedin the Tablespace requirements section of DB2 or Oracle databases, so frequently


used tables such as itd, ita, itm, icm and lck are stored in separate table spaces andbuffer pools. This helps to improve overall performance. To do so, you need tocreate a table space mapping file with the following contents:tctg_itd_item_detail,itd_data,itd_ixtctg_ita_item_attributes,ita_data,ita_ixtctg_itm_item,itm_data,itm_ixtctg_icm_item_category_map,icm_data,icm_ixtutl_lck_lock,lck_data,lck_ix

The table space name mapping file includes the text in each line with the followingformat:

table_name,(table_tablespace_name), (index_tablespace_name)

As shown above, both table_tablespace_name and index_tablespace_name are optional.For example:tctg_sel_selection,ctg_tables,tctg_dys_dynamic_selection,ctg_tables,tctg_itm_item,tctg_itd_item_detail,ctg_tables,ctg_indxtctg_ita_item_attributes,ctg_tables,ctg_indx

Properties of table space name mapping file:

1. If table_tablespace_name and index_tablespace_name are not specified,the default tablespace names are used.

2. All the tables used by InfoSphere MDM Collaboration Server, that arenot included, use the default table space names.

3. Blank lines are ignored.4. Lines that starts with '#' are considered as comment lines and are

ignored, for example:#----------------------------# This is a comment line#----------------------------

If table_tablespace_name and index_tablespace_name are not specified, the defaulttablespace name users and index tablespace name indx will be used.

If the InfoSphere MDM Collaboration Server table is not included in the<tablespace name mapping file>, it will use the default table and index tablespacenames users and indx.

In the <tablespace name mapping file>, any line that starts with '#' will beconsidered as comment line and will be ignored.

In the <tablespace name mapping file>, any blank line will be ignored.

A default mapping file is in:

$TOP/src/db/schema/gen/ tablespace_name_mapping_file.txt

This file follows the format specified above and it can be used as a template foruser's < tablespace name mapping file >. It includes all required table spaces thatare used by the SQL scripts in the $TOP/src/db/schema/gen directory for creatingtables and indexes for InfoSphere MDM Collaboration Server.


Testing the database connectivityBefore you can use IBM InfoSphere Master Data Management Collaboration Server,you must create the database schema.

About this task

When connecting the database, the <install dir>/bin/test_db.sh script tests thenative client and the JDBC connections. The script prints any errors.

The schema generation script, create_schema.sh, does not stop if it encounters anerror nor does it display errors. Examine the log file, <install dir>/logs/schema.log, to ensure that the schema was successfully created.

You can run the script, create_schema.sh, with the —verbose option. This optionprints the logging information to the log file. It also includes the SQL that was sentto the database and the output from the Java programs.

Procedure1. Verify database user. Verify that the database user referenced in the

common.properties file exists in the database with the proper privileges.2. Verify that you have command line connectivity and that InfoSphere MDM

Collaboration Server can connect to the database by issuing the following shellscript:a. Run test_db.sh. The command test_db.sh tests command line connectivity

using db2 or sqlplus. It also tests JDBC connectivity using Java.3. After the database user is set up correctly, create the InfoSphere MDM

Collaboration Server database schema.

Error handling for table space name mapping fileIn addition to the standard script errors in 'create schema', and the newtablespace_name_mapping_file command-line argument, the mapping file errors arevalidated.

The following mapping file errors are validated:1. If the mapping file does not exist, the system will return this error:

The tablespace name mapping file 'file_name' does not exist.

If this happens, the script will stop.2. If the mapping file is not a readable text file or invalid, the system will return

this error:

The tablespace name mapping file 'file_name' is invalid.

If this happens, the script will stop.3. If a line in the mapping file is not formatted as required, the system will return

this error:

The following line in the tablespace namemapping file 'file_name' is invalid andwill be ignored: the_line.

If this happens, the script will continue.


4. If a table name in a line in the mapping file does not exist or is not a valid IBMInfoSphere Master Data Management Collaboration Server table, the systemwill ignore the line and return this error:

Invalid table name: table_name.

If this happens, the script will continue.5. If a table name or the whole line is duplicated, ignore the line and report

warning to user:

Duplicated table name: table_name.

If this happens, the script will continue.

As described above, the table_tablespace_name and index_tablespace_name areoptional. If any of them are missing, create_schema.sh script uses the default tablespace names. No error message or warning will be returned.

If the tablespace name mapping has been completed successfully, the systemreturns this message:

The system has applied the tablespace name(s) for each table successfully.

If any error reported, the system returns this message:

The system failed to apply the tablespace name(s) for each tables

All message strings above are localized.

Configuring GDS featureYou must configure a few GDS parameters in order for IBM InfoSphere MasterData Management Collaboration Server to be able to exchange product data with adata pool.

Creating a .bindings file for WindowsIn order to properly configure the IBM InfoSphere Master Data ManagementCollaboration Server GDS WebSphere MQ settings, you need to create a .bindingsfile.

About this task

The following steps create a .bindings file on the Windows operating system.

Procedure1. Setup the WebSphere Message Queue classpath. The WebSphere Message

Queue default installation directory is at C:\Program Files\IBM\WebSphere MQin Windows that should be set as MQ_INSTALL_DIR. Assuming you need toupdate the system classpath variable (CLASSPATH) with the following jar files:v <MQ_INSTALL_DIR>\Java\lib\providerutil.jarv <MQ_INSTALL_DIR>\Java\lib\com.ibm.mqjms.jarv <MQ_INSTALL_DIR>\Java\lib\ldap.jarv <MQ_INSTALL_DIR>\Java\lib\jta.jarv <MQ_INSTALL_DIR>\Java\lib\jndi.jar


v <MQ_INSTALL_DIR>\Java\lib\jms.jarv <MQ_INSTALL_DIR>\Java\lib\connector.jarv <MQ_INSTALL_DIR>\Java\lib\fscontext.jarv <MQ_INSTALL_DIR>\Java\lib\com.ibm.mq.jar

2. Create a directory on the WebSphere MQ server and call it: C:\JNDI-Directory.

Note: If this directory already exists, delete any earlier versions of the.bindings files from it.

3. Go to the <MQ_INSTALL_DIR>\Java\bin directory and add the following changesto the JMSAdmin.config file. Ensure that the values for the following parametersare:v INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactoryv PROVIDER_URL=file:/C:/JNDI-Directory

Note: If these parameters are not present, include these with the above values.4. Open a command prompt and change the directory to <MQ_INSTALL_DIR>\Java\

bin. Issue the JMSAdmin.bat file. On successful initialization of this batch file,you will see a InitCtx> prompt. You are now ready to issue the MQSCcommands. If an exception occurs then check if the classpath system variable isproperly set for the jar files listed in step 1 above.

5. Issue the following commands in this sequence:a. InitCtx> def q(INBOUND_QUEUE_NAME)b. InitCtx> def q(OUTBOUND_QUEUE_NAME)c. InitCtx> def qcf(QUEUE_CONNECTION_FACTORY_NAME)

transport(CLIENT) channel(java.channel) host(WMQ_SERVER_IP)d. port(WMQ_SERVER_DEFINED_PORT) qmgr(QUEUE_MANAGER_NAME)e. InitCtx> end

For example:a. InitCtx> def q(XML_IN)b. InitCtx> def q(XML_OUT)c. InitCtx> def qcf(ptpQcf) transport(CLIENT) channel(java.channel)d. host(9.121.222.84) port(1414) qmgr(bcg.queue.manager)e. InitCtx> end

where:

XML_INThe inbound queue that is used by the GDS messaging service to readfrom.

XML_OUTThe outbound queue to which GDS will post messages.

ptpQcfThe queue connection factory name as defined in $TOP/bin/conf/env_settings.ini as a value for the queue_connection_factoryparameter under the [gds] section.

9.121.222.84The WebSphere MQ server IP address.

1414 The WebSphere MQ server defined listen port.


bcg.queue.managerThe queue manager name under which the queues are defined.

Note: If you receive a message similar to unable to bind object message, checkwhether the JNDI-Directory directory exists. Also, if there is already an earlierversion of the .bindings file in the folder, delete it and redo steps 4 and 5above.

6. Copy the generated .bindings file from the JNDI-Directory directory and pastethe file to the required destination at InfoSphere MDM Collaboration Serverunder the:v $TOP/etc/default,v $TOP/etc/default/, andv $TOP/etc/appsvrgds_<SERVER_NAME>

directories.

Setting Global Data Synchronization parametersEnsure that you set the following Global Data Synchronization feature parameters.

Procedure1. Open the env_settings.ini file, and go to the [gds] section.2. Set the following parameters:

enabledSet this parameter to one of two possible values, yes or no. Set it to yesif you want to enable GDS. The default is no.

company_codeSet this parameter to the company code for which you want to load theGDS data model.

gds_app_typeSet this parameter to one of two possible values, Demand or Supply.

ACTIVE_DATA_POOL_IDSet this parameter to one of two possible values, Transora or WWREV6.

inbound_queue_nameEnter the name of the WebSphere MQ inbound queue from where thelistener of the Global Data Synchronization feature of IBM InfoSphereMaster Data Management Collaboration Server will read XMLmessages.

outbound_queue_nameEnter the name of the WebSphere MQ outbound queue where theGlobal Data Synchronization feature of IBM InfoSphere Master DataManagement Collaboration Server will post or push XML messages.

queue_connection_factoryEnter the name of the WebSphere MQ queue connection factory.

datapool_glnEnter the GLN of the data pool with which the Global DataSynchronization feature of InfoSphere MDM Collaboration Server issupposed to exchange XML messages.


self_glnEnter the GLN of your organization. You need to populate thisparameter only if your organization is a retailer type of organization(gds_app_type=Demand).

3. Go to the [appserver.appsvrgds] section and set the following parameters:

port Set this parameter to a value of your choice. The value that you set isthe port number used by the Global Data Synchronization feature ofInfoSphere MDM Collaboration Server appserver for GUI. For example,7525.

appserver_nameSet this parameter to gds_<APP_SERVER_NAME>. For example,gds_appsvr.

vhost_nameSet this parameter to gds_<VIRTUAL_HOST_NAME>. For example,gds_vhost.

4. Go to the [services] section and set the following parameters:

appsvrappsvr, appsvrgds

5. Because many functions in Global Data Synchronization have dependencies onthe services provided by WebSphere MQ, set the following parameters in the[mq] section:

enabledSet to yes to enable the support for functions which have dependencieson MQ.

home The installation directory of the WebSphere MQ client. Lowest versionrequired is 7.0.1.

6. Save and close the env_settings.ini file.7. If you are using WebSphere Application Server as your application server, you

must complete these configuration steps for the WebSphere MQ .jar files.a. Change directories to the <install_dir>/jars directory.b. Create the following three soft links, replacing WAS_HOME with the home

directory for WebSphere Application Server and DEFAULT_APPSVR withthe name of the default application server:v ln -s <WAS_HOME>/profiles/<DEFAULT_APPSVR>/installedConnectors/

wmq.jmsra.rar/com.ibm.mq.jar com.ibm.mq.jar

v ln -s <WAS_HOME>/profiles/<DEFAULT_APPSVR>/installedConnectors/wmq.jmsra.rar/com.ibm.mqjms.jar com.ibm.mqjms.jar

v ln -s <WAS_HOME>/profiles/<DEFAULT_APPSVR>/installedConnectors/wmq.jmsra.rar/dhbcore.jar dhbcore.jar

c. Run the bin/configureEnv.sh script to update the classpath.

Example

Here is an example of the appserver.appsvr and appserver.appsvrgds sections ofthe env_settings.ini file:

#For PIM App Server[appserver.appsvr]port=7505appserver_name=pim_appsvr


vhost_name=pim_vhost#For GDS App Server[appserver.appsvrgds]port=7525appserver_name=gds_appsvrvhost_name=gds_vhost

Here is an example of the services section of the env_settings.ini file:

[services]admin=admineventprocessor=eventprocessorqueuemanager=queuemanagerscheduler=schedulerworkflowengine=workflowengineappsvr=appsvr,appsvrgds

Here is an example of the mq section of the env_settings.ini file:

[mq]enabled=yeshome=/opt/mqm

Configuring Global Data Synchronization memory parametersfor messaging

You need to configure the Global Data Synchronization memory parameters for themessaging module before you can use the Global Data Synchronization messagingservice.

Procedure1. Open the <Install_Dir>/bin/gdsmsg.sh file.2. Set the values for the initial heap size and the maximum heap size on the

CCD_JMS_JVM_DEBUG_OPTS parameter. The default values are -Xmx1024m-Xms512m.

Note: You must not attempt to set the maximum heap size more than thephysical memory available on your computer.

3. Save and close the <Install_Dir>/bin/gdsmsg.sh file.

Example

This is an example of setting the CCD_JMS_JVM_DEBUG_OPTS parameter for aninitial heap size of 512 MB and a maximum heap size of 1024 MB.

CCD_JMS_JVM_DEBUG_OPTS="-Xmx1024m -Xms512m"

Setting up an AS2 connectorYou must install and configure an AS2 connector to enable IBM InfoSphere MasterData Management Collaboration Server to communicate with a datapool.


About this task

The AS2 protocol is used for communication between InfoSphere MDMCollaboration Server and a datapool. This protocol provides fast and securetransmission of business data.

Procedure

Install and configure the AS2 connector. For more information, refer to your AS2connector documentation.

AS2 connectorThe AS2 (Applicability Statement 2) protocol is used for securely transmittingbusiness documents in the XML, binary, and Electronic Data Interchange (EDI)formats over the Internet. It is frequently used in business-to-business dataexchange operations. In order to ensure correct XML data exchange, the GlobalData Synchronization Network has identified and defined AS2 as the standard forcommunication between suppliers and data pools and data pools and retailers forend-to-end connectivity.

The AS2 protocol is based on the HTTP and SMIME protocols. It allows messagesto be encrypted and signed. It also allows the receiver of a message to generate aconfirmation message that is sent to the sender of the message.

The Global Data Synchronization feature of IBM InfoSphere Master DataManagement Collaboration Server requires a distinct AS2 connector softwareapplication that uses the AS2 protocol to communicate with a data pool. Thebusiness documents that are exchanged between InfoSphere MDM CollaborationServer and the data pool are in the XML format.

One example of an AS2 connector software that you can use is IBM WebSpherePartner Gateway. For more information about how to install and configureWebSphere Partner Gateway as your AS2 connector software, see the IBMWebSphere Partner Gateway information center.

Connecting to a data poolYou need to connect to a data pool to send or receive data.

Before you begin

Before you can connect to a data pool, you must register with the data pool.Registration with a data pool requires you to enter into a contract and to pay thesubscription fee. On successful registration, you get the URL that the data poolexposes to customers, and one or more global location numbers (GLNs).

Procedure1. Define a participant connection for sending information from IBM InfoSphere

Master Data Management Collaboration Server to the data pool. You need toenter the URL that the data pool exposes, the global location numbers that youreceived from the data pool on registering, and the protocol in which you planto send your product documents.

2. Define a participant connection for receiving information from the data pool.You need to enter the protocol in which you plan to receive productdocuments.

3. Activate the connections.


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic/com.ibm.wpg.entadv.doc/welcome_wpg.htm

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic/com.ibm.wpg.entadv.doc/welcome_wpg.htm

Chapter 7. Verifying the installation

To verify that you have successfully installed IBM InfoSphere Master DataManagement Collaboration Server, log in to the product user interface.

Post-installation checklistAfter installing IBM InfoSphere Master Data Management Collaboration Server, usethe following checks to ensure that you have set up the application correctly.

Database Configuration and Settings

Database Configuration for Oracle Database

All necessary InfoSphere MDM Collaboration Server configurations for Oracle areenabled in init.ora file in Oracle. Refer to “Setting up your Oracle database” onpage 33 for details on setting up Oracle for use with InfoSphere MDMCollaboration Server. Once the Oracle database is up, the necessary InfoSphereMDM Collaboration Server settings can be verified. You can consult your DBA forassistance with this.

Database Configuration for DB2 Database

All necessary InfoSphere MDM Collaboration Server settings for DB2 database areenabled in three different configuration areas:1. DB2 Registry variables.2. DB2 Database Manager Configuration.3. DB2 Database configuration.

All of these settings can be checked by running a shell script from DB2 Serverusing DB2 instance owner id to verify the IBM InfoSphere Master DataManagement Collaboration Server Installation Guide recommended value with thecurrent value for configuration settings. For details on setting up DB2 forInfoSphere MDM Collaboration Server, see “Setting up your DB2 database” onpage 15. For assistance with the shell script, consult your DBA.

WebSphere Application Server or WebLogic Application Serversettings

You can check settings in WebSphere Application Server admin console againstrecommendations for WebSphere Application Server in the WebSphere ApplicationServer documentation and against those made in the InfoSphere MDMCollaboration Server Installation Guide, and you can verify that the correct Javaand JDK libraries are used. For WebSphere Application Server setup information,see “Setting WebSphere Application Server parameters” on page 62.

Product settings

All product settings are stored in the common.properties file. Verify that all therequired settings are understood and used.

If necessary verify that the Mount manager is installed and configured correctly.


Setting up a test company using a scriptYour product information management (PIM) data is organized in IBM InfoSphereMaster Data Management Collaboration Server by companies. To be able to log into InfoSphere MDM Collaboration Server, you must create a test company usingthe script that is provided.

About this task

<install dir>/bin/db/cleanup_cmp.sh can be used to drop all information in acompany such as items and catalogs. The –code argument is required for bothcreate_cmp and cleanup_cmp

Procedure1. Use the following shell script to create the schema: <install

dir>/bin/db/create_cmp.sh. For example, For example, create_cmp.sh–code=<company code> --name=<company name>. It creates a log file <installdir>/logs/create_cmp.logThis script creates the company. You can use this empty test company in yourtest environment. You can use the create_cmp.sh script to create additional testcompanies.

Note: ID and password information is hard-coded when you create thecompany using the script, and so they are case sensitive.

2. Create an empty company called 'test' (which contains no predefined data), byrunning the following shell script:

<install dir>/bin/db/create_cmp.sh --code=test

The company demo is created with a single user: admin. The password foradmin is "trinitron". Passwords are case-sensitive. The admin user is createdwith full privileges and should be used by an administrator.

Remember: You must execute the create_cmp.sh shell script only when yoursystem is down. You must not execute the create_cmp.sh shell script multipletimes in parallel so that more than one instance is running at a given time,otherwise the scripts will fail.

3. Review the log file after executing create_cmp.sh to check for errors.

Loading Global Data Synchronization data modelYou need to load Global Data Synchronization data model to enable IBMInfoSphere Master Data Management Collaboration Server to publish productinformation to your data pool as well as to receive product information from yourdata pool.

About this task

The Global Data Synchronization feature of InfoSphere MDM Collaboration Serverloads the appropriate data model based on the configuration settings in theenv_settings.ini file. The data model is loaded by running theloadGDSDatamodel.sh script.


Procedure1. Navigate to the $TOP/bin/db directory.2. Run the loadGDSDatamodel.sh script.

Starting the productWhen you start IBM InfoSphere Master Data Management Collaboration Server,you also start all of its services, and the application servers including theapplication server of the Global Data Synchronization feature.

Before you begin

Before you start the product, you must ensure that you have configured theapplication server of the Global Data Synchronization feature in the [services]section of env_settings.ini file.

About this task

You need to run the start_local.sh script to start the product and all the servicesthat are needed to run the product, and the rmi_status.sh script to verify that theapplication is running. You also need to start the messaging service of the GlobalData Synchronization feature to send and receive XML messages.

Procedure1. Run the start_local.sh script. This script is located in the <install

directory>/bin/go directory.2. Run the gdsmsg.sh script with the start parameter if you have enabled the

Global Data Synchronization feature of InfoSphere MDM Collaboration Server.This script is located in the <install directory>/bin directory. You can use thestatus parameter to fetch the status of the Global Data Synchronization listenerservice.$<Install_Dir>/bin/gdsmsg.sh start

3. Run the rmi_status.sh script to verify that the application is up and running,and that the services have started. The following information is displayed:v admin_<name of instance>v appsvr_<name of instance>v eventprocessor_<name of instance>v queuemanager_<name of instance>v scheduler_<name of instance>v workflowengine_<name of instance>This process takes approximately 30-40 seconds, depending on the speed of theprocessor.

Example

This is an example of output from running the rmi_status.sh script showing thatall services have started on "pimserver1" where the Global Data Synchronizationfeature is enabled:[pim1@pimserver1 pim1]$ /opt/pim/pim1/pim900/bin/go/rmi_status.sh[success] rmistatus (Mon Mar 8 14:00:49 PDT 2010)//pimserver1:17507/samplemart/admin/admin_pimserver1//pimserver1:17507/samplemart/appsvr/appsvr_pimserver1//pimserver1:17507/samplemart/appsvr/appsvrgds_pimserver1

Chapter 7. Verifying the installation 87

//pimserver1:17507/samplemart/queuemanager/queuemanager_pimserver1//pimserver1:17507/samplemart/workflowengine/workflowengine_pimserver1//pimserver1:17507/samplemart/scheduler/scheduler_pimserver1//pimserver1:17507/samplemart/eventprocessor/eventprocessor_pimserver1

This is an example of output from running the rmi_status.sh script showing thatall services have started on "pimserver1" where the Global Data Synchronizationfeature is not enabled:[pim1@pimserver1 pim1]$ /opt/pim/pim1/pim900/bin/go/rmi_status.sh[success] rmistatus (Mon Mar 8 14:00:49 PDT 2010)//pimserver1:17507/samplemart/admin/admin_pimserver1//pimserver1:17507/samplemart/appsvr/appsvr_pimserver1//pimserver1:17507/samplemart/queuemanager/queuemanager_pimserver1//pimserver1:17507/samplemart/workflowengine/workflowengine_pimserver1//pimserver1:17507/samplemart/scheduler/scheduler_pimserver1//pimserver1:17507/samplemart/eventprocessor/eventprocessor_pimserver1

Logging in to the productIBM InfoSphere Master Data Management Collaboration Server provides abrowser-based user interface that you can use to manage and administer yoursystem. You log in with the user name, password, and company that you createdfrom the demo scripts.

Procedure1. Open your web browser and enter the URL and port for the Web server. It is

important to enter a fully qualified host name along with "/utils/enterLogin.jsp". The URL will be similar to the following:http://~/utils/enterLogin.jsp where ~ is the DNS name or IP address of thesystem on which the product is running, and the port is defined in thecommon.properties file.

Note: During the product installation, the web server port was set to 7507 in atwo tier configuration. If a different port is used, change the port reference inthe file "server.xml" for a three tier configuration

2. Use the user name, password, and company that was created from running thedemo test scripts. For example, enter the following information:

Username: AdminPassword: trinitronCompany Code: acme

For details see “Setting up a test company using a script” on page 86

Note: ID and password information was hard-coded when you created thecompany using the script, and so these are case sensitive.

Results

If the product home-page loads, the installation was successful. Log out of theapplication.

Logging in to Global Data SynchronizationGlobal Data Synchronization provides a browser-based user interface that you canuse to manage and administer your system.


Procedure

Open your web browser and enter the URL and port for the Web server. The URLwill be similar to the following:http://<Server_Name_OR_IP>:<Port_Number>/Login.do where<Server_Name_OR_IP> is the server name or IP address of the system on which theproduct is running, and the port is defined in the env_settings.ini file.For example, if the port number defined for Global Data Synchronization is 7527,you would have to define the port number in the following location:v File path and name: <MDMPIM_Install_Dir>/bin/conf/env_settings.iniv Section: [appserver.appsvrgds]v # This section is specifically for GDS.

[appserver.appsvrgds]port=7527

Therefore, the URL would be http://<Server_Name_OR_IP>:7527/Login.do

Results

If the product home-page loads, the installation was successful. Log in to theapplication.

Configuring the product using the Firststeps applicationAfter you have configured IBM InfoSphere Master Data Management CollaborationServer, you can use the Firststeps application to verify the configuration andperform certain tasks.

About this task

The Firststeps application enables you to get started with the product once theproduct has been installed and configured.

Procedure1. Open the Firststeps application. The Firststeps file is called launchpad.sh and is

located in the <product install> directory in the firststeps/disk1 directory.2. Click the Verify Installation link to check if the product has been installed

successfully.3. Click on the link to start the application.4. Run the rmi_status.sh script to check the status of the application. This script is

available in the <product install directory>/bin/go directory.5. Click the Create a company link to create a company. This step will succeed

only if the product schema has already been created.

Stopping the productTo update or change the runtime configuration of IBM InfoSphere Master DataManagement Collaboration Server, you must stop the product and all of itsservices, and the application servers including the application server of the GlobalData Synchronization feature.

Chapter 7. Verifying the installation 89

About this task

You need to run the abort_local.sh script to stop the product and all the services.You also need to stop the messaging service of the Global Data Synchronizationfeature.

Procedure1. Run the abort_local.sh script. This script is located in the <install

directory>/bin/go directory.2. Run the gdsmsg.sh script with the stop parameter if you have enabled the

Global Data Synchronization feature of InfoSphere MDM Collaboration Server.This script is located in the <install directory>/bin directory. Use the stopparameter to complete processing the messages that have been picked from themessage queue and then stop the Global Data Synchronization messagingservice. Use the abort parameter to stop the Global Data Synchronizationmessaging service immediately without processing the messages that have beenpicked from the message queue.$<Install_Dir>/bin/gdsmsg.sh stop


Chapter 8. Troubleshooting the installation program

Describes some common scenarios for troubleshooting the installation of IBMInfoSphere Master Data Management Collaboration Server.

Issue: Configuring the default_locale parameter to ensure userscan log in successfully

When installing InfoSphere MDM Collaboration Server, Version 6.0.0 or later, youcould have login problems and receive an error after importing a database dumpinto a different environment.

The following errors might occur after importing the database dump:

In the user interfaceWPC - ErrorAUS-20-014 Invalid username/password/company code.

In the $TOP/logs/<Appserver_hostname>/exception.log file2009-05-19 07:35:14,651 [jsp_2: enterLogin.jsp] ERRORcom.ibm.ccd.common.error.AustinException - Could not findlookup tablewith name: PropriÃ©tÃ©s LDAP, Exception:Could not findlookup tablewith name: PropriÃ©tÃ©s LDAP

One possible reason that users cannot log in to InfoSphere MDMCollaboration Server is that the value of the default_locale parameter isconfigured incorrectly. For example, if the default_locale parameter is setto a certain value, and then a database dump export was taken, thedefault_locale value in the environment where the dump is going to beimported should be set to the same value as the parameter value in theexported environment. That is, if the default_locale parameter was set tofr_FR in the exported environment, it should be set to fr_FR in theimported environment. If the values are not the same, users will not beable to log in to the system.

Issue: InfoSphere MDM Collaboration Server AppServer mightnot start, or install_war.sh may fail with "arg list too long" error

When installing InfoSphere MDM Collaboration Server, Version 6.0.0 or later, thefollowing error might occur:

/bin/go/init_svc_vars.sh: line 21: /usr/bin/mkdir:The parameter or environment lists are too long.

/bin/read_config_file.sh: line 34: /usr/bin/awk:The parameter or environment lists are too long.

If the ncargs parameter on AIX is not set to a high enough value, the install_war.shinstallation script might fail with the error message "arg list too long". Thisproblem might also cause the application server to fail.

The AIX default for the ncargs parameter is set to 6 * 4k.


Since the product needs a long list of arguments to install and run correctly, thisparameter might not specify enough memory to run the install_war.sh script or tostart the product.

To resolve the problem, the AIX administrator must increase the size of the ncargsparameter, by issuing the following command:

chdev -l sys0 -a ncargs=NewValue

where NewValue is the number of 4k blocks to be allocated for the argument list.You can specify a number between 6 (which is the default value) and 128. You canreview the current setting by issuing the following command:

lsattr -E -l sys0 -a ncargs

You can also change the value of the ncargs parameter (and view additionalinformation) using the smit or smitty AIX configuration commands. For moreinformation about any of these commands, refer to the AIX and pSeriesInformation Center.

Issue: Silent Installation - installer.bin is invalid in the silentmode

This issue is independent of the stacks running on HP. If this issue is encounteredin any installation or uninstall on HP, rename or replace the vpd.properties file toresolve this issue.

Issue: Console mode - When installing the product in theconsole mode using non-root, the installation program cannotfind WebSphere Application Server, Oracle and the old version ofInfoSphere MDM Collaboration Server, which was installed byroot.

List of possible causes:v If the installation of a WebSphere Application Server has been done with user A

and you plan to install InfoSphere MDM Collaboration Server with user B, theinstaller will not be able to search WebSphere Application Server because user Bwill look into its own vpd.properties file and not into user A's vpd.propertiesfile.

v The search for Oracle uses a separate path search query which will work in anyform without being dependent on the user. This is the same case with DB2.

v The search for WebLogic is dependent on the path in which it has been installed.It is required to make a hard code search in the directories /opt and /usr whichare usually used for installing BEA, but if BEA is installed in another path it willnot be searchable. The search option cannot be kept as" /" because it willdrastically slow the installer.

v The existing InfoSphere MDM Collaboration Server search is dependent onvpd.properties so if the first installation has been done with user A and you areinstalling a new instance of InfoSphere MDM Collaboration Server with user B,the installer will not be able to detect the existing instance.


http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.doc/doc/base/alphabeticallistofcommands.htm

http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.doc/doc/base/alphabeticallistofcommands.htm

Issue: Console Installation - There are error messages when theuser does not have the required access to the directory /tmp.

The Installer needs access to the /tmp directory to run properly. If access is notgiven to /tmp, the installer will not work and the OS will give a message to informyou that you cannot create the specified file to the /tmp dir, and the installer willexit.

Issue: NLS Console and Graphical Installation - The installer failsto find the BEA and ORACLE server and the installation hangson the pre-requisite screen.

While doing a prerequisite search for BEA, the installer will do search in /usr and/opt directories. In the case of BEA not being present, the Installer may take a longtime to move ahead. On the graphical panel, Cancel it and move to the next panel.

In Console mode, there is no option to cancel, so to avoid this issue, run theinstaller with the prerequisite search variable set to false. This issue is only withBEA. With Oracle, there is no issue.

Chapter 8. Troubleshooting the installation program 93

Chapter 9. Uninstalling the product

You can run either the uninstaller IBM InfoSphere Master Data ManagementCollaboration Server graphically or silently from the command line.

The uninstaller attempts to clean up the installation directory and any files createdby the user after the product was installed, with the possible exception of a logfile. For the cleanup of the installation directory to take place, ensure that no shellor application is using the _uninst directory as its current directory or is locking itin any other way. Graphical file managers, for example, that display the contents ofthe _uninst directory may or may not be locking the _uninst directory, so theseshells and applications should be closed, before running the uninstaller.

Uninstalling the product silently using a response fileYou can uninstall IBM InfoSphere Master Data Management Collaboration Serversilently, where the installation choices are provided to you in a response fileinstead of in the panels of the installation wizard. The uninstaller does not promptfor any user input, so it can be invoked to run silently, without the need for anoptions file.

Procedure1. Start the uninstaller application.2. Type the command to run the uninstaller. You can type one of the following

commands:

cd <product_installation_directory>./_uninst/uninstaller.bin -silent

or

<path to JRE>/bin/java -jar ./_uninst/uninstall.jar -silent

Example

Note: You must undo the WAS (or WebLogic) configuration as well as thedb2/oracle configuration.

Potential issues during silent unistallation:Uninstaller.bin is invalid in the silent mode: This issue is independent of thestacks running on HP. If you encounter this issue during an installation oruninstallation on HP, rename or replace the vpd.properties file to resolve thisissue.The JRE uninstall displays warning messages when the uninstall ends:Invoking the uninstaller using the jar file option might give a warning on Linuxoperating systems (for example: WARNING: could not delete locked file/tmp/build_aaa.).

Uninstalling the product using the wizardYou can uninstall IBM InfoSphere Master Data Management Collaboration Serverusing the wizard from the uninstallation application.


Procedure1. Start the uninstaller application.

v The uninstallation directory is called __uninstall and is located in the productinstall directory.

v Type following commands to start the uninstaller:

cd <product_installation_directory>./_uninst/uninstaller.bin

or type:

<path to JRE>/bin/java -jar ./_uninst/uninstall.jar

2. At the Welcome screen click Next.3. Choose the product you want to uninstall. Ensure that you select the entire

product to uninstall.The Summary screen lists the components that will beuninstalled and the product directory from which they will be removed.

4. Verify the information and click Next.5. Click Uninstall when you see the pre-uninstall summary details.6. After the uninstaller finishes successfully, click Finish.

Results

Potential issue with a console uninstallation:The uninstall cannot end from the finish panel. The expected behavior is thatno error messages occur when the uninstall is complete: If the uninstaller isinvoked with setup.jar using 64 bit JVM, the uninstall will not complete.

Uninstalling the product using text modeYou can uninstall the product using text mode in a command prompt window.

Procedure1. Start the uninstaller by issuing the following command with the -console flag:

> cd <product_installation_directory>> ./_uninst/uninstaller.bin -console

> cd <product_installation_directory>> <path to JRE>/bin/java -jar ./_uninst/uninstall.jar -console

2. Select a language and continue to the next screen. This screen is the same asthe installer language selection screen.

3. Choose 1 (Next) to continue the uninstallation.4. Review the uninstall preview screen. No progress screen is provided during the

uninstallation process.5. Review the uninstall summary screen. At the post-uninstall summary screen,

press 3 to finish the uninstallation process.


Chapter 10. Installing IBM Software Assistant

The IBM Support Assistant (ISA) for IBM InfoSphere Master Data ManagementCollaboration Server can be installed either from product interface or from ashell/command prompt.1. Download the IBM Support Assistant, Version 4.0 workbench.2. Use the installation program to install IBM Support Assistant by following the

instructions described here: http://www-306.ibm.com/software/support/isa/isa40/install.html .

3. Install the data collector add-on for InfoSphere MDM Collaboration Serverusing the instructions in the Troubleshooting section of the information center.


http://www-306.ibm.com/software/support/isa/isa40/install.html

http://www-306.ibm.com/software/support/isa/isa40/install.html

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM CorporationJ46A/G4555 Bailey AvenueSan Jose, CA 95141-1003U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. The sampleprograms are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.


Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rightsreserved.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, other countries,or both.

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at "Copyright andtrademark information" at www.ibm.com/legal/copytrade.shtml.

Adobe is either registered trademarks or trademarks of Adobe SystemsIncorporated in the United States, and/or other countries.

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems,Inc. in the United States, other countries, or both.

Intel, Intel Centrino, Celeron, Intel Xeon, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other product and service names might be trademarks of IBM or other companies.

Notices 101

http://www.ibm.com/legal/copytrade.shtml

Index

Special characters.bindings file

creating 79

Aallocating the hardware 13application server

installing and setting up 43architecture 9, 10AS2 connector 84

Ccache parameters

configuring 57comments

sending vcommon application server parameters

setting 62compatibility scripts 67components 11configuring 83

application server 67common database parameters 57

configuring 57Firststeps 89GDS feature 79manually 55Perl 5

configuring cache parameters 57configuring MQ parameters 65configuring the application server 62configuring WebLogic Server 69configuring WebSphere Application

Server 67connecting 84creating

.bindings file 79

Ddatabase

setting up and configuring 15setting up DB2 15setting up Oracle 33updating the parameter file

settings 36database schema

setting up 78datapool 84DB2

adding users 22buffer pool requirement 16configuring database manager 25creating an instance 19creating buffer pools 20creating table spaces 20, 38creating the database 19

DB2 (continued)custom table spaces 75

create schema 75default names 76error handling 78table space name mapping file 76

error handling 78granting permissions 22profile registry updates 24setting configuration parameters 26setting up 15setting up a database 15setting up the client 31setup checklist 32table space requirements 17table spaces 75

DB2 configurations 23default port numbers 47

Eencrypted passwords 57env_settings.ini

creating 56env_settings.ini file

setting common parameters 56environment

validate 66environment variable

setting up 55

Ffeatures

new in Version 10.0 v

GGDS memory parameters

configuring 83Global Data Synchronization 81

setting 81Global Data Synchronization memory

parameters for messaging 83

Hhardware 13high availability 10

IIBM Software Assistant

installing 97information flow 10installation 45

configure 66overview 1

installation requirements 1

installation requirements (continued)hardware 1software 2

installation scenarios 11installation wizard 51installation worksheets 45installing 48, 51

GNU utilities 4installing 4

installation media 49Oracle XML DB component 41Perl 2, 5

installing 2installing in user home

directory 5Perl modules 6, 7

installing 6installing all other modules 7

using a response file 49

Lload balancing and failover 13loading 86logging in 88, 89LTPA keys 43LTPA tokens 43

MMQ parameters

configuring 65

OOracle

creating a new database 34creating database schema users 40disk considerations 34setting up 33setting up on the application

server 40, 42setting up to use OCI drivers 61setting up transaction logs 39setup for high availability 35updating OS settings 33

Oracle WebLogic Serverconfiguring 68setting parameters 64

Ppasswords

encrypted 57performance

allocating the hardware 13hardware 13load balancing and failover 13project plan 13


performance (continued)timing 13tracking 13tuning 13use cases 13

Perl versions 3port numbers 47prerequisite information vproduct summary 9project plan 13protocol 84

Rrelated information vresponse file 95

installing 49runtime properties

configuring 74

Sschema

creating 75sending comments vservices 11setting 81, 84

DB2 parameters 58setting 58

Oracle parameters 60setting 60

setting up the environment variable 55silent installation 49silent uninstall 95starting product 87starting services 87stopping product 90stopping services 90storing database passwords 57summary 9supply side Global Data Synchronization

data model 86loading 86

system administrationservices 11

system architecture 9

Ttest company

setting up 86timing 13tracking 13trademarks 101transaction log files

setting up 30troubleshooting

contacting IBM Software Support vitroubleshooting the installation 91tuning 13

Uuninstalling 95, 96use cases 13

using text mode 96using the wizard 96

Vverifying the installation 85

WWebLogic

running the configuration file 68WebSphere Application Server

setting up 63


��

Printed in USA

GC19-3497-00

infosphere mdm collaboration server: installation guide · iv infosphere mdm collaboration server:...

Documents