WebSphere MQ Test

This test checks the availability of a WebSphere MQ server to handle connection requests from clients.

Target of the test : A WebSphere MQ server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every WebSphere MQ server monitored

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed .

Host

The host for which the test is to be configured.

Port

The port number at which the specified host listens.

User

If you want to login as a specific MQ user to execute this test, then specify a valid user name in the User text box. The test will fail if an invalid user name is specified here. If no such authentication is required, then this parameter can be set to 'none'.

Password

If a specific User is entered, then the password of that user has to be specified in the Password text box.

Confirm Password

Confirm the password by retyping it in the Confirm Password text box.

ServerConnChannel

The name of the server connection channel for the WebSphere MQ server. The default value is "SYSTEM.DEF.SVRCONN". If you prefer not to use this default server connection channel for monitoring purposes, then you can create a custom channel in the WebSphere MQ server and use it for monitoring. The steps for achieving this have been detailed in Creating a Custom Channel topic.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

MQ port availability

Reflects whether the port on which the WebSphere MQ server is listening is available for connections.

Percent

This metric takes a value of 100 if the port is available, and 0 if it is not.

MQ connection availability

Indicates whether connection to the MQ server is available for MQ clients or not.

Percent

This metric is 100 if the eG agent is able to connect to the MQ server using the parameters specified (e.g., serverConnChannel). The value of this metric is 0 if the agent is not able to connect to the MQ server. Connection problems can occur if the server is down or unavailable. Invalid user name/password can also result in connection failures.