Troubleshooting installation - validate installation

Edit online

If there are problems with the installation, the symptoms are widespread. Many parts of the system are not going to work and there are various WebSphere® MQ and WebSphere eXtreme Scale errors in the logs. If you are having systemic problems, use this list as a set of items to validate to troubleshoot the installation.

Installation validation checklist

This table lists common installation problems and their fixes.
Table 1. Installation validation checklist
Problem Resolution

Installation Manager Data Sources page

All data sources must be in a separate "schema". The meaning of schema varies per RDBMS. 		Reconfigure the data source properties file. See Updating a properties file.

Installation Manager Message Fabric page

The WebSphere MQ configuration requires a user name and password. By default, WebSphere MQ does not validate passwords and thus any password is viable now.		 --

Installation Manager Member Configuration page

The name of the catalog member must match one of the WebSphere eXtreme Scale catalog servers that are configured on the Data Grid page. Each catalog server that is specified on the Data Grid page must have one associated matching catalog member on one or more installations.

Do one of the following tasks:

  • Add the catalog members with the expand system in the installation manager.
  • Reconfigure the WebSphere eXtreme Scale properties to match the expected deployment. See Updating a properties file.

Installation Manager Data Grid page

If authentication is enabled, the user name and password must be set to the following values at installation:

  • User name - wxsUser
  • Password - P@$$w0rd

Do one of the following tasks:

  • Reconfigure the WXS properties for gridUser and gridPassword with the correct values. See Updating a properties file.
  • Disable client authentication.

Installation Manager Data Grid page

If more than one catalog server is specified and configured in a multi-node installation, all catalog servers must be started before the application can start.

Run the execute member start catalog or the execute member start_service catalog command on each node simultaneously.
The database schemas must be set up before you start the application. The Installation Manager warns you if the schemas are not set up. --
When you do a multi-node installation, use the Extend an existing cluster feature for all additional nodes beyond the first. During the initial installation, select the Properties configuration. For subsequent installations. After the system is up, use the Data Grid configuration option to extend the cluster. --
For non-POC installations, WebSphere MQ must be running before you start the system or system startup fails.
  1. Restart WebSphere MQ.
  2. Restart the operational and informational members by using one of the following sets of commands:
    • execute member start operational and execute member start informational (Linux® and Windows)
    • execute member start_service operational and execute member start_service informational (Windows as a Windows service)
The WebSphere MQ user that is specified during the installation must have the appropriate permissions as documented. If the WebSphere MQ user does not have the appropriate permissions, the system might not start or otherwise function properly.
  1. Apply the required permissions, to the WebSphere MQ user, as documented in the WebSphere MQ documentation.
  2. Restart the operational and informational members by using one of the following sets of commands:
    • execute member start operational and execute member start informational (Linux and Windows)
    • execute member start_service operational and execute member start_service informational (Windows as Windows services)
By default, the system is configured to create WebSphere MQ queues automatically. This feature requires extended permissions for the WebSphere MQ user that is specified during the installation as documented. If these feature permissions are not enabled, the system might not start or otherwise function properly.

Do one of the following tasks:

  • Apply the required permissions for automatic queue creation to the WebSphere MQ user as documented in the WebSphere MQ documentation. Then restart the operational and informational members by using one of the following sets of commands:
    • execute member start operational and execute member start informational (Linux and Windows)
    • execute member start_service operational and execute member start_service informational (Windows as Windows services)
  • Disable automatic queue creation and explicitly create the queues as documented in the WebSphere MQ documentation. Then restart the operational and informational members by using one of the following sets of commands:
    • execute member start operational and execute member start informational (Linux and Windows)
    • execute member start_service operational and execute member start_service informational (Windows as Windows services)
The default queue sizes for WebSphere MQ might not be appropriate under load and various features might time out if related queues fill. Increase the size of the queues on WebSphere MQ following the WebSphere MQ documentation.
Access to JMX data is secured with an SSL authentication layer. Authentication requires an WebSphere Liberty-specific REST connector to be made available to the JMX client. Refer to System monitoring with Java Management Extensions (JMX)