This file is used to check if the connectivity and the Discovery of the Websphere MQ Server is possible from the Applications Manager server. This standalone program is an excerpt of the same process we use to add the Websphere MQ Server monitor. The usage to run this file is as below:
Windows
Via command prompt, navigate to <AppManager_Home>/bin/troubleshooting directory and execute the WebsphereMQDebug.bat file with the usage below:
WebsphereMQDebug.bat [MQ Host] [Listener Port] [Server Connection Channel] [Queue Manager] [CCSID] [SSLEnabled] [CipherSuite] [username] [password] [BrokerEnabled] [IIBv10] [IIBPort] [brokeruser] [brokerpass]
Check the image below for more details about the arguments:
Linux:
Via terminal, navigate to <AppManager_Home>/bin/troubleshooting directory and execute the WebsphereMQDebug.sh file with the usage below:
WebsphereMQDebug.sh [MQ Host] [Listener Port] [Server Connection Channel] [Queue Manager] [CCSID] [SSLEnabled] [CipherSuite] [username] [password] [BrokerEnabled] [IIBv10] [IIBPort] [brokeruser] [brokerpass]
This will initiate the process to discover the WebSphere MQ Server and on success will also fetch the data for the default attributes monitored and shown as the output. From this, you will be able to find if discovery is possible and if data is returned for all attributes or not. In case there is any issue for an attribute data it'll be shown as null. This infers that the data is not available in that server and has to be checked on the WebSphere MQ server.
For more info or assistance do send us the output of the above command for analysis along with Support Information File.