Skill Level: Intermediate

This article provides an overview of installing InfoSphere MDM in WAS cluster.


IBM Installation Manager v1.7 or above.

IBM WebSphere Application Server Network Deployment v8.5.5 or above.

IBM WebSphere Application Server JAVA SDK v1.8 or above.

IBM Master Data Management install image .




  1. Verifying WebSphere Application Server SDK.

    Before proceed with creating WAS profiles, verify Java 1.8 is enabled by default for WAS profile creation.

    We can verify Java version using following command.

    <WAS_install_path>/bin/managesdk –listEnabledProfileAll

    If it’s set to older version, we need to modify by using following commands.

    1. List all Java SDK versions avaible using following command.

    <WAS_install_path>/bin/managesdk -listAvailable –verbose

    2. Set java SDK to point latest version availble using following.

    <WAS_install_path>/bin/managesdk.sh -setNewProfileDefault -sdkname 1.8_64
    <WAS_install_path>/bin/managesdk.sh -setCommandDefault -sdkname 1.8_64


    $./managesdk.sh -listAvailable -verbose

    CWSDK1003I: Available SDKs :

    CWSDK1005I: SDK name: 1.6_64

     – com.ibm.websphere.sdk.version.1.6_64=1.6

     – com.ibm.websphere.sdk.bits.1.6_64=64

     – com.ibm.websphere.sdk.location.1.6_64=${WAS_INSTALL_ROOT}/java

     – com.ibm.websphere.sdk.platform.1.6_64=linux

     – com.ibm.websphere.sdk.architecture.1.6_64=x86_64

     – com.ibm.websphere.sdk.nativeLibPath.1.6_64=${WAS_INSTALL_ROOT}/lib/native/linux/x86_64/

    CWSDK1005I: SDK name: 1.8_64

     – com.ibm.websphere.sdk.version.1.8_64=1.8

     – com.ibm.websphere.sdk.bits.1.8_64=64

     – com.ibm.websphere.sdk.location.1.8_64=${WAS_INSTALL_ROOT}/java_1.8_64

     – com.ibm.websphere.sdk.platform.1.8_64=linux

     – com.ibm.websphere.sdk.architecture.1.8_64=x86_64

     – com.ibm.websphere.sdk.nativeLibPath.1.8_64=${WAS_INSTALL_ROOT}/lib/native/linux/x86_64/

    ./managesdk.sh -setNewProfileDefault -sdkname 1.8_64
    CWSDK1022I: New profile creation will now use SDK name 1.8_64.
    CWSDK1001I: Successfully performed the requested managesdk task.

    ./managesdk.sh -setCommandDefault -sdkname 1.8_64
    CWSDK1021I: The command default SDK name is now set to 1.8_64.
    CWSDK1001I: Successfully performed the requested managesdk task.

  2. Creating WebSphere Application Server Cluster.

    Create WAS cluster by using following steps.

    • Start the WAS profile Management tool from  WAS_install_path/bin/ProfileManagement/pmt.sh
    • Create a Cell(Deployment manager+Application server) 
    • Start the deployment manager and node agent.
    • Create Custom profile, during creation provide IP address and SOAP port of deployment manager to which this profile will federated into.
      Note: For vertical cluster i.e, on same machine we can use localhost for hostname and for Horizontal cluster we need to input IP address/hostname of the target machine.
    • Make sure all nodes are up and running.
    • Use the following web address to access the administrative console:


      The value of hostname is either the fully qualified host name or the IP address of the WebSphere Application Server deployment manager. The value of port is the port number for the WebSphere administrative HTTP transport.

    • In the administrative console, click Servers > Clusters > WebSphere application server clusters > New. The Create a new cluster wizard starts.

    • Specify a name for the cluster. Create cluster members each on different nodes and save.

    • Synchronize the nodes. System administration >> Nodes >> Synchronize , select nodes part of cluster.
    • Start the cluster and ensure all the cluster members started.


  3. Set Driver path for Nodes.

    For MDM deployment on cluster, we need to set Driver path to database specific WAS environment variables manually.

    In this scenario, we are using DB2 as database and DB2 specific driver path variables has to be set with the scope as the Node.

    In the administrative console, click Environment > WebSphere Variables > DB2_JDBC_DRIVER_PATH and edit to provide <database_home>/java as input.

    Repeat this operation for each node in cluster.



  4. Prepare Database for MDM install.

    1. Create a database manually or using scripts present in disk1 on installation image.
    2. Ensure all required tablespaces created before proceeding with installation.
  5. MDM installation.

    1. Start IBM IM.
    2. Add MDM install image location in preferences.
    3. Select MDM New install feature.
    4. On WebSphere Application Server Configuration Panel, enter all inputs and and click on Retrieve Host details, where Host name and SOAP port corresponds to deployment manager.
    5. Select Install MDM application on cluster check box, it will populate with existing cluster name.  Select and do verify whether an instance of MDM already installed on the cluster.


          6. Proceed with installation, and it completes extraction process.

          7. Run ./madconfig.sh Configure_MasterDataManagment target from <MDM_HOME>/mds/scripts directory.

          8. Enter all of the required passwords and deployment details, as prompted.

  6. Verifying MDM installation on cluster deployment.

    Once target completes execution, we need to verify installation process.

    1. To check physical MDM IVT results, go to <MDM_HOME>/IVT/testCases/xml/response
    2. To check virtual MDM IVT results, go to <MDM_HOME>/IVT/testCases/xml_virtual/response and look at the response files.
    3. For successful deployment, all response files should have SUCCESS status.
    4. Check database table APPINSTANCE, it should be populated with all cluster member entries.

    $ db2 “select * from appinstance”

    ——————– ——————– ————————————————– ————————– ——————–
    1 1006 member2 2017-03-20- installer
    2 1006 member1 2017-03-20- installer

    2 record(s) selected.


  7. Verifying the functionality of the new Member

    To check whether the new Member is functional, invoke IVT after modifying certain property files to point to the new Member.

    1. Open <MDM_INSTALL_DIR>/IVT/properties/TestClient.properties

    2. Modify the values for the below properties


    Replace <HOST> with the host in which the new Member is present. Replace <BOOTSTRAP_ADDRESS> and <WC_defaulthost> with the respective port numbers that can be obtained from the WebSphere Admin Console.

    3. Invoke IVT.

    When the operating system is Windows,


    For other operating systems,


  8. Load balancing : Make User Interface Applications point to appropriate Cluster Member

    By default the user interfaces point to the primary Member in the Cluster. The applications have to be modified manually to make them point to an appropriate Cluster Member so that load balancing can be achieved. The location of these files is provided below:

    • Business Administration UI: <WAS_PROFILE_DIR>/installedApps/<CELL>/ba-App-<INSTANCE_ID>.earpropertiesUI.jar


    • Inspector: <WAS_PROFILE_DIR>/installedApps/<CELL>/inspector-<INSTANCE_ID>.earinspector.warWEB-INFclassesinspector.properties


    • Enterprise Viewer: <WAS_PROFILE_DIR>/installedApps/<CELL>/enterpriseviewer-<INSTANCE_ID>.earviewer.warWEB-INFclassesContextManager.prop


    • Web Reports: <WAS_PROFILE_DIR>/installedApps/<CELL>/webreports-<INSTANCE_ID>.earwebreports.warWEB-INFclasseswebreports.properties


    • Virtual MDM Web Services : <WAS_PROFILE_DIR>/installedApps/<CELL>/MDM-web-services-virtual-<INSTANCE_ID>.ear/ibminitiatews.war/WEB-INF/classes/ibminitiatews.properties

Join The Discussion