Use this procedure to install InfoSphere MDM using
the graphical installation mode. The installation must be run in an
environment that already has a database and an application server
in place.
Before you begin
Note: If you prefer to install using a non-graphical installation
mode, skip directly to the appropriate topic:
Make sure that you meet these prerequisites:
- You have completed all of the installation preparation tasks,
including preparing your IBM®
WebSphere® Application Server and
database.
- Your configured passwords meet all of the
requirements.
- You have installed IBM
Java™ SDK 1.8.0.
- You have installed Microsoft Visual
C++ 64 bit.
- You have installed IBM Installation
Manager and added the necessary repositories.
- Your IBM
WebSphere Application Server deployment
manager and node are started.
- Your database is started.
- You have installed IBM
Rational® Application Developer if
you are installing InfoSphere
MDM Workbench on
a workstation.
If you are installing on Microsoft
Windows:
- You must be running in Administrator mode for IBM
Installation Manager to write to the Windows registry.
Administrator mode is not used for IBM
AIX® or Linux®.
- On a Microsoft
Windows 7 operating system, you must install MDM into a
directory that is not virtualized.
Important: You must have the WebSphere Application Server deployment manager (Dmgr) JVM Heap size arguments set to 2048 MB
and 4096 MB, as described in
this IBM Support article. To increase the heap size:
- Open the WebSphere Application Server Integrated
Solutions Console and go to .
- Under Server Infrastructure, expand Java and Process
Management, then click Process definition.
- Under Additional Properties, click Java Virtual
Machine.
- Set the Initial heap size to 2048 MB and the Maximum heap
size to 4096 MB.
- Click OK, save your changes, and synchronize your changes with the
nodes.
On InfoSphere MDM
deployments using an IBM DB2 for Linux, UNIX, and Windows database, Unicode UTF-32 (CODEUNITS32) is
the default string unit specification. CODEUNITS32 treats each character unit as 32 bits (4
bytes).
Important: If you customize the default database creation script to remove the
CODEUNITS32 setting, you must also manually change an entry in the file
<MDM_INSTALL_HOME>/mds/sql/maddbx.dbp. Under the
[DB2]
section, ensure that colsizeaschar=F
. This change must be
completed before running the Configure_MasterDataManagement
madconfig target to
deploy InfoSphere MDM.
About this task
If you have IBM
Rational Application Developer installed,
make sure that you do not install InfoSphere MDM into
the same package group.
Procedure
-
Review the prerequisites listed earlier in this topic and ensure that you have completed all of
the necessary preparation steps. These steps are not optional.
-
Optionally, enable enhanced debug logging in ./InstallationManager/logs by
copying
STARTUPKIT_INSTALL_HOME/InstallationManagerDebug/log.properties
into ./InstallationManager/logs.
Important: After you have enabled enhanced debug logging, the logged information in
./InstallationManager/logs can include password details entered by the user
during the installation. Ensure that these logs are stored in a secure place to avoid password
exposure.
-
Start IBM Installation
Manager.
-
On the IBM Installation
Manager
home screen, click Install.
-
On the Install Packages panel, select the InfoSphere MDM
Standard Edition or Advanced Edition option and any additional features that you
require. Click Next.
-
Review and accept the license agreement, then click Next.
-
Depending on your operating system, you may be asked to define the Shared Resource directory.
InfoSphere MDM
should not share a resource directory with other applications. Ensure that this is not the
case.
-
Choose whether to install into an existing package group or create a new package group.
Tip: If you are unsure of what to choose, then accept the default. Most installations
should create a new package group.
Important: If you have IBM
Rational Application Developer installed, make
sure that you do not install InfoSphere MDM into the same
package group. Select Create a new package group.
-
On the same panel, define the Installation Directory into which you want
to install each component. If you choose to install a component in a directory other than the
default, select that component and click Browse in the
Installation Directory field. Click Next.
Important: On Microsoft
Windows 7 operating systems, the Program
Files directory is virtualized and requires administrative privileges. To be able to run
the application without administrative privileges, you must install into a directory that is not
virtualized.
-
On the language panel, English is always selected. If you want to support any languages in
addition to English, select them. Click Next.
-
On the features panel, select the InfoSphere MDM features,
applications, and optional components to install.
Review the disk space information, then click Next.
-
On the next set of panels, enter the configuration information:
Tip: Use your completed installation worksheets for guidance. As you move through each
of these configuration panels, the screen displays a green checkmark icon or a red X icon to
indicate whether the panel has been completed successfully.
-
On the Database Configuration panel:
- Enter the database details. If your database home value is valid, then the Test
Connection button becomes active.
Tip: If you are using a Microsoft SQL Server database that uses Windows Authentication, do not enter the database user credentials on this
panel. The credentials are automatically populated by the installation application.
- If you are using Oracle RAC database, select the Service Name
option.
- If you wish to enable SSL encryption for the MDM database, select the SSL
Authentication check box, then provide the SSL trust store path and password.
Note: The
SSL trust store type is presumed to be PKCS12. If you wish to use a different type of trust store,
perform a silent installation instead of using the graphical installation mode.
- Click Test Connection. The database must be accessible and running for
the test to be successful.
Note: If you do not wish to test the connection, select No
connection test required.
- If you wish to save your settings in a script so that you can manually and repeatably install
the MDM database again, select Extract scripts for manual database
installation.
-
On the Database Table Spaces panel, define your database table
spaces:
- Select Copy database details from the database configuration panel to
repeat the database details that you entered in the previous panel.
- Decide whether to use existing table spaces or create new ones, then select either
Use existing table spaces or Create new table
spaces.
Tip: Consider whether existing table spaces are dedicated for InfoSphere MDM only or are
general purpose table spaces. If they are general purpose, then create new table spaces that will be
dedicated for InfoSphere MDM.
- If you choose to create new table spaces, then you must either choose from a list of suggested
names or define new names.
Note: If you did not select Test Connection on the
previous panel, then the lists will not be prepopulated with existing table space names. In this
case, the default names will be used.
-
On the History Configuration panel, select the industry type, history
triggers, and language options necessary for your business requirements.
-
On the WebSphere Application Server Configuration panel:
- Select whether you are installing InfoSphere MDM into a Base
edition or Network Deployment edition instance of WebSphere Application Server, depending on what edition you configured during the prerequisite
installation steps.
- Enter the required details of the WebSphere
Application Server instance where InfoSphere MDM will be
installed.
- Manually specify the server details or select Retrieve Host Details to
obtain your cell, node, and server information. Use each drop down list to select the retrieved
cell, node, and server.
- If you wish to define a new server, select the Specify New Server Name
option, then provide a name for the new server instance.
- For Network Deployment edition installations, if you wish to install the application in a
cluster deployment, define the cluster name and select Install MDM application on
cluster.
Tip: In clustered network deployments, the server name for each web
application must be different.
- Click Verify MDM Instance on Server to ensure that there is not already
an InfoSphere MDM
application installed on the server.
Restriction: You cannot deploy more than one InfoSphere MDM application
instance on each server.
Note: If you do not wish to verify the application instance, you can
select No MDM instance verification required. This option should only be used
if you fully understand the risk that the installation may fail if another InfoSphere MDM instance is
present.
-
On the Messaging Configuration panel, select the messaging type to use for
this installation. Your selection depends on which messaging service you have configured during the
prerequisite installation steps.
If you select IBM
WebSphere MQ, then you will be asked to provide the
details of your existing WebSphere MQ instance.
Note: If
you installed a remote WebSphere MQ instance (on a
different machine than the one where you are running IBM Installation Manager), make sure that you clear the
Configure a local IBM WebSphere MQ instance option to prevent the installer
from creating a local queue manager. Keep the option selected if you do want to create a queue
manager.
-
On the MDM Application Configuration panel:
- Provide the new application name, user password, and RMI port. The installation application will
use these details to set up InfoSphere MDM.
- Select either Probabilistic matching or Deterministic
matching for your matching style.
- If your application is running across different time zones or your data has time-sensitive
values under different time zones, select Enable multiple time zone
deployment and select a Default time zone.
-
If you are installing any of the InfoSphere MDM web application
user interfaces, use the corresponding panel for each to define the application settings:
- Select Retrieve details from WebSphere Application Server configuration
panel to copy the application server details that you defined on the main application
WebSphere Application Server configuration panel.
Restriction: If you are installing on WebSphere
Application Server Base edition, you cannot select both Retrieve details from WebSphere
Application Server configuration panel and the Retrieve Host
Details button. After selecting the Retrieve details from WebSphere
Application Server configuration panel option, do not click Retrieve Host
Details.
- Provide all of the required deployment parameters for each application. These parameter values
will be similar to those that you have already provided for the main application.
- If you wish to specify a new server name for this web application, select Specify New
Server Name and define the new name.
Note: If you choose to do this, you must define a
different server name for each of the web applications that you configure.
- For WebSphere Application Server Network Deployment
edition installations, if you wish to install the application in a cluster deployment, define the
cluster name and select Install MDM application on cluster.
Tip: In clustered network deployments, the server name for each web application must be
different.
- If you wish to enable SSL encryption for the application, select Enable
SSL.
-
Click Install.
The installation application installs InfoSphere MDM. Depending on
your configuration selections, the installation process can take a significant amount of
time.
-
On the final IBM Installation
Manager panel:
- To automatically launch the installation configuration tool immediately after closing IBM Installation
Manager, select
Configure Master Data Management.
- To open the log file viewer, click View Log Files.
-
Click Finish, then close IBM Installation
Manager.
Now you must complete the configuration of your new installation.
If you selected the
option to launch the installation configuration tool on the final Installation Manager panel, then
the console will open. If you did not select the option, or if the console fails to open
automatically, then you must manually launch the console:
- From a command line, navigate to
MDM_INSTALL_HOME/mds/scripts and run the following command
to open the installation configuration tool.
Upon being launched, the installation configuration tool prompts you to provide the
necessary information to complete the installation configuration.
-
Provide the details of your deployment as prompted by the installation configuration
tool.
After you provide the user credentials for WebSphere Application Server and the database as
prompted, the installation configuration tool performs a set of pre-configuration validation tests to validate your
installation environment. These validation tests help to ensure that all of the required components
are in place to complete the installation and configuration smoothly.
If the pre-configuration validation is successful, the configuration tool completes the
configuration of your installation.
What to do next
After installation, if you want to add or remove a feature (for
example, add an application or another language translation), or modify any of your configuration
settings, run the madconfig target Modify_MDM
.