IBM Support

Applications fail to start after InfoSphere MDM and InfoSphere RDM installations on WebSphere Application Server v8.5.5.12

Troubleshooting


Problem

During InfoSphere MDM and InfoSphere RDM installations that are deployed on WebSphere Application Server v8.5.5.12, the applications are not started as expected after completion of the installation configuration madconfig target.

Diagnosing The Problem

Application startups will fail after being installed on WebSphere Application Server v8.5.5.12.

Resolving The Problem

Complete the following steps to work around this issue:

For InfoSphere MDM installations:

    1. Open the WebSphere Application Server Integrated Solutions console (admin console).
    2. Go to Business-level applications > MDM-old-web-services-<INSTANCE_ID> > MDM-old-web-services-<INSTANCE_ID > Startup behavior.
    3. Set the startup order to 1.
    4. Complete the same steps for the following applications:
      - MDM-web-services-<INSTANCE_ID> (set the startup order to 2)
      - MDM-native-<INSTANCE_ID> (set the startup order to 3)
      - MDM-web-services-virtual-<INSTANCE_ID> (set the startup order to 4)
    5. Go to Business-level applications > MDM-operational-server-EBA-<INSTANCE_ID> > com.ibm.mdm.hub.server.app-<INSTANCE_ID>_0001.eba.
    6. Set the starting weight to 10.

    Important: If additional InfoSphere MDM User Interface applications have been installed, assign a unique startup order to each UI application.

    7. Go to Business-level applications > MDM-old-web-services-<INSTANCE_ID> > MDM-old-web-services-<INSTANCE_ID> > Class loader At WAR class loader policy.
    8. Select the option to enable a 'Single class loader for application'.
    9. Synchronize the nodes and restart the server.

For InfoSphere RDM installations:
    1. Open the WebSphere Application Server Integrated Solutions console (admin console).
    2. Go to Business-level applications > CDH-old-web-services-<INSTANCE_ID> > CDH-old-web-services-<INSTANCE_ID > Startup behavior.
    3. Set the startup order to 1.
    4. Complete the same steps for the following applications:
      - CDH-web-services-<INSTANCE_ID> (set the startup order to 2)
      - RDMClientEAR-<INSTANCE_ID> (set the startup order to 3)
    5. Go to Business-level applications > CDH-operational-server-EBA-<INSTANCE_ID> > com.ibm.mdm.cdh.app-<INSTANCE_ID>_0001.eba.
    6. Set the starting weight to 10.

    Important: If additional InfoSphere RDM User Interface applications have been installed, assign a unique startup order to each UI application.

    7. Go to ¨Business-level applications > CDH-old-web-services-<INSTANCE_ID> > CDH-old-web-services-<INSTANCE_ID> > Class loader At WAR class loader policy.
    8. Select the option to enable a 'Single class loader for application'.
    9. Synchronize the nodes and restart the server.

[{"Product":{"code":"SSWSR9","label":"IBM InfoSphere Master Data Management"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"11.0;11.3;11.4;11.5;11.6;11.6.0.1;11.6.0.2","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
27 April 2022

UID

swg22009597

Page Feedback