WebSphere MQ Channels Test

This test connects to a WebSphere MQ server, auto-discovers the channels that have been configured for this server, and monitors the status of each of these channels.

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 channel configured for the WebSphere MQ server.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed.


The host for which the test is to be configured.


The port number at which the specified host listens.


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'.


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.


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.


If SYSTEM channels are to be monitored, then set this flag to No. If not, set the flag to Yes.


Specify a comma-separated list of channel names or channel name patterns to be monitored. For example, your specification can be: *.EG.*,CLNT.JPM.*,*.CSI.SVRCONN. In this case, the test will monitor  only those channels with names that embed the string “.EG.”, names that start with “CLNT.JPM”, and names that end with “.CSI.SVRCONN”.


If a SYSTEM channel or a pattern that matches a SYSTEM channel is configured in the include channels text box, then this test will monitor such SYSTEM channels, even if the IgnoreSystemChannels flag is set to Yes.


Specify the version the WebSphere MQ server that is being monitored. For instance, 6 or 7.


Indicate whether the inactive channels are to be monitored or not using this flag. If you prefer to monitor the inactive channels, then set this flag to Yes. If not, set this flag to No. By default, this flag is set to No.


Specify the comma-separated list of inactive channels that are to be excluded for monitoring in the ExcludeChannels text box. By default, the value of this parameter is none.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Channel status

Indicates the current status of this channel.


The table below indicates the values that this measure can report and their corresponding numeric equivalents:

Measure Value Numeric Value
Running 0
Requesting 1
Binding 2
Starting 3
Initializing 4
Inactive 5
Paused 6
Retrying 7
Stopping 8
Stopped 9


By default, this measure reports the above-mentioned Measure Values while indicating the current status of each channel. However, in the graph of this measure, the status of the channels will be represented using the corresponding numeric equivalents as mentioned in the table above.

MQ channel availability

Reports the current availability of this channel.


A value of 100% signifies that the channel is available for clients to connect to. A value of 0% indicates channel unavailability.

Current messages

The number of messages being currently handled by this channel.


A continuous increase of this value signifies that the receiver is not able to cope up with the incoming traffic.

Messages handled

The number of messages that transmitted through the channel during the last measurement period



Buffers received

The number of buffers of data received over this channel during the last measurement period.


This metric indicates the workload over a channel.

Buffers sent

Indicates the number of buffers of data transmitted over this channel during the last measurement period.


This metric indicates the workload over a channel.

Data received

Indicates the rate at which data is received over this channel during the last measurement period



Data transmitted

Indicates the rate at which data is transmitted over this channel during the last measurement period



Time since last message

Reflects the time that has elapsed since the last message was transmitted over this channel.


If an unusually long time has elapsed since when the last message was transmitted, it could reflect an error in the application (e.g., a hung application that is no longer transmitting messages over the channel).


To enable the eG agent to monitor the IBM MQ server effectively, start the command server for each queue manager that you want the eG agent to monitor. A command server is mandatory for all administration involving PCFs, the MQAI, and also for remote administration. The eG agent’s MQ library is a PCF. So, the command server needs to be started.