Installing InfoSphere MDM into a clustered environment

Use this procedure to run a custom installation of InfoSphere® MDM into a clustered environment.

1. 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.
2. Verify that these items are completed for your application server:
   1. WebSphere Application Server is installed on each required machine in your cluster.
   2. The necessary clusters are created in WebSphere Application Server.
   3. If you are using a DB2® or Oracle database, you must set the JDBC_DRIVER_PATH environment variable.
   4. Synchronize all managed nodes.
   5. Note the WebSphere Application Server host name and port in your installation worksheet.
3. Verify that your database and database client software are installed on the necessary machines, and that the database is started.
4. If you are using IBM WebSphere MQ messaging, complete these steps for each machine in the cluster. If you are using IBM WebSphere Default Messaging, continue to the next step.
   1. Verify that WebSphere MQ is installed.
   2. Run the custSetupMQServer.mqsc and ChannelAuth.mqsc scripts to create the WebSphere MQ queue manager, channel, and queues. These scripts are part of the Installation Startup Kit, which you can extract from Part 1 of the distribution assets (IBM InfoSphere Master Data Management Standard & Advanced Edition Mulitplatform Multilingual <version> Part 1).
5. Open IBM Installation Manager and click Install.
6. On the Install Packages panel, select the edition and click Next.
7. Continue through the prompts to accept the license agreement, select an installation location, and select languages.
8. Configure your InfoSphere MDM installation details:
   Tip: Use your completed installation worksheets for guidance. As you move through each of these configuration panels, the screen displays a green check mark or red x to indicate whether the panel has been completed successfully.
   1. On the Database Configuration panel:
      • Enter the database details. If your database home value is valid, then the Test Connection button becomes active.
      • Click Test Connection. The database must be accessible and running for the test to be successful.
      • After a successful connection test, you can set up table spaces. Select either Use existing tablespaces or Create new tablespaces. If you choose to create new table spaces, then you must define the new names.
   2. On the History Configuration panel, select the industry, triggers, and language options necessary for your business requirements.
   3. On the WebSphere Application Server Configuration panel:
      • Enter the information that you used to set up your application server.
      • 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 need to provide a different value, you can type it in the field.
      • Click Verify MDM Instance on Server.
   4. On the 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.
      • Select the messaging type to use for this installation. If you select IBM WebSphere MQ, then you will be asked to provide the details of your WebSphere MQ instance.
        Tip: If you installed WebSphere MQ on a different machine than the one where you are running IBM Installation Manager, make sure that you clear the Configure messaging server option to prevent the installer from creating a queue manager. Keep the option selected if you do want to create a queue manager.
   5. On the Install Configuration Review panel:
      • Select the install type. You can either choose to automatically configure the application components as part of the main installation process or run scripts after the main installation to configure them later.
      • Expand the Properties headings to review the details that you have configured for this installation.
      • Click Verify Installation Requirements to run a number of prerequisite checks. The checks will help you to confirm that your environment and configuration is sufficient to successfully complete the installation.
      • Review the prerequisite validation test results. Click Show details to see more information of for each test, and follow the provided links to view the log file and help for each result.
        Tip: You can ignore warnings by clicking Show details, then selecting Ignore the warning. I understand the risks. Errors cannot be ignored.
      • If necessary, take any corrective action to address any warnings or errors, then click Recheck Status.
      • When the checks pass successfully, click Install.
   The installation application will install InfoSphere MDM. Depending on your configuration, the installation process can take a significant amount of time.
9. On the final IBM Installation Manager panel, click View Log Files if you want to open the log file viewer.
10. Click Finish, then close IBM Installation Manager.
11. From a command line, navigate to MDM_INSTALL_HOME/mds/scripts and run the following command to open the installation configuration tool:
    • On Microsoft Windows systems, run

      madconfig.bat Configure_MasterDataManagement

    • On Linux or UNIX systems, run

      madconfig.sh Configure_MasterDataManagement

12. Provide the details of your deployment as prompted by the installation configuration tool.
    The configuration tool will complete the configuration of your installation.
13. For Microsoft Windows installations, the ODBC datasource will be available only on the server in which InfoSphere MDM is installed. To create the ODBC datasource in other servers that have nodes that are part of the cluster, perform the following steps with a user that is authorized to modify the Windows registry:
    1. Browse to <WAS_PROFILE_HOME>/installedApps/<CELL>/MDM-native-<INSTANCE_ID>.ear/native.war/scripts.
    2. Invoke the madconfig target register_odbc:

       madconfig register_odbc

    3. Invoke the madconfig target create_datasource along with a value for the property mad.db.dsn:

       madconfig create_datasouce -Dmad.db.dsn=<DATABASE_NAME>_<INSTANCE_ID>

       Note: The value for mad.db.dsn can be obtained from <WAS_PROFILE_HOME>/installedApps/<CELL>/MDM-native-<INSTANCE_ID>.ear/native.war/conf/com.ibm.mdm.mds.jni.cfg as part of value for property MAD_CONNSTR.
    4. When prompted, provide values for the following parameters:
       • Database type
       • Database host
       • Database port
       • Database name
       • Schema name