WebSphere MQ Channels Test

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

This parameter is applicable only if SSL-enabled channel is used for communication to the target MQ server, if not, set this parameter to none.

A cipher suite is a set of cryptographic algorithms that are used before a client application and server exchange information over an SSL/TLS connection. It consist of sets of instructions on how to secure a network through SSL (Secure Sockets Layer) or TLS (Transport Layer Security). In this text box, provide the cipher suite that is allowed for SSL/TLS connection to the target server. By default, this parameter is set to none. To know if SSL-enabled channel is used for communication, refer to Pre-Requisites for Monitoring IBM WebSphere MQ Servers

This parameter is applicable only if SSL-enabled channel is used for communication to the target MQ server, if not, set this flag to No.

If two-way SSL authentication is used then set this flag to Yes. Set this flag to No if one-wy SSL communication is used.

This parameter is applicable only if SSL-enabled channel is used for communication to the target MQ server, if not, set this parameter to none.

Truststore is used to store certificates from Certified Authorities (CA) that verify and authenticate the certificate presented by the server in an SSL connection. Therefore, the eG agent should have access to the truststore where the certificates are stored to authenticate and connect with the target server and collect metrics. For this, first extract the certificates from the server into the following default location /opt/egurkha/jre/lib/security/egmqsslstore.jks. To know how to create and extract the certificate into the truststore, refer toPre-Requisites for Monitoring IBM WebSphere MQ Servers. Then, provide the truststore file name in this text box. For example: egmqsslstore.jks. However, if you are using a different location to store the certificate then, provide the full path to this file in this text box. By default, none is specified against this text box.

This parameter is applicable only if SSL-enabled channel is used for communication to the target MQ server, if not, set this parameter to none.

If a Truststore File name or file path is provided, then, in this text box, provide the password that is used to obtain the associated certificate details from the Truststore File.

This parameter is applicable only if SSL-enabled channel is used for communication to the target MQ server, if not, set this parameter to none.

Confirm the password by retyping it in this text box.

This parameter is applicable only if two-way SSL authentication is used, if not, set this parameter to none.

Keystore contains the private keys for the certificates that the client can provide to the server upon request. eG agent requires access to the keystore where client certificate is stored to send that to the server so that the server validates the certificate against the one contained in its trustore. For this purpose, first create the client certificate in the following default location /opt/egurkha/jre/lib/security/egmqsslstore.jks. To know how to create the certificate, refer to Pre-Requisites for Monitoring IBM WebSphere MQ Servers. Then, provide the keystore file name in this text box. For example:egmqsslstore.jks. However, if you are using a different location to store the certificate then, provide the full path to this file in this text box. By default, none is specified against this text box. If you are using one-way SSL authentication, this parameter is set to none.

This parameter is applicable only if two-way SSL authentication is used, if not, set this parameter to none.

If a Keystore File name or file path is provided, then, in this text box, provide the password that is used to obtain the associated certificate details from the Keystore File.

This parameter is applicable only if two-way SSL authentication is used, if not, set this parameter to none.

Confirm the password by retyping it in this text box.

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

Note:

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.