Agents Administration - Tests
 

Configuration of WsMqChlInstTest

This test connects to a WebSphere MQ server, auto-discovers the channels that have been configured for this server and monitors the instances of each channel. Using this test, administrators can figure out the utilization of the instances in each channel and identify the channel that is overloaded in terms of instances. This test also throws light on the maximum number of instances configured for the channels.

The default parameters associated with this test are as follows:

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • In the HOST text box, the host for which the test is to be configured has to be specified.

  • In the PORT text box, enter the port number at which the target host being monitored 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.

  • Specify the name of the server connection channel for the WebSphere MQ server in the SERVERCONNCHANNEL text box. 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.

  • Specify the full path to the install directory of the IBM WebSphere MQ server in the MQ HOME text box. For example, if the IBM WebSphere MQ server is installed on a Windows operating system, then the path will be C:\Program Files\IBM\WebSphere MQ. On the other hand, if the target server is installed on Linux operating system, then, the path will be /opt/mqm.

  • Specify the full path to the install directory of the Queue Manager in the QUEUE MANAGER HOME text box. For example, if the IBM WebSphere MQ server is installed on a Windows operating system, then, the path will be C:\Program Files\IBM\WebSphere MQ\Qmgrs\MAS!EG!QM1. On the other hand, if the IBM WebSphere MQ is installed on Linux operating system, then, the full path to the Queue Manager Home will be /var/mqm/qmgrs/IB9QMGRx.

  • Specify the time duration (in seconds) beyond which this test should time out in the TIMEOUT text box. The default is 60 seconds.

  • The DD FREQUENCY parameter refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY .

  • To make diagnosis more efficient and accurate, the eG suite 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.

  • If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

  • Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.