The WsMqLocalQTest connects to a WebSphere MQ server, auto-discovers the local queues that have been configured for this server, and monitors the status of each of the local queues. The 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 name of the server for which the test is to be configured has to be specified.

• The port number to which the selected server is listening has to be specified in the PORT textbox.

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

• In the SERVERCONNCHANNEL text box, enter the name of the server connection channel for the WebSphere MQ server. The default value is “SYSTEM.DEF.SVRCONN”.

• If SYSTEM queues are to be monitored, then set the IGNORESYSTEMQUEUES flag to False. If not, set the flag to True.

• The IGNOREQUEUES parameter takes a default value of “none”. If so, none of the queues (other than the SYSTEM queues) are ignored while monitoring an MQ server. Otherwise, this parameter represents a comma separated list of patterns. Any queue name that matches one of the patterns specified for a test is not considered for monitoring by the eG agent.

• Specify a comma separated list of patterns that are to be included in the scope of monitoring in the INCLUDE QUEUES text box. By default, this parameter takes a value of none.

• In the NUMDDMESSAGES text box, specify the number of messages to be displayed in the detailed diagnosis information. For instance, if NUMDDMESSAGES is set as 20, then the details for the first 20 messages in the queue will be displayed in detailed diagnosis. If this value is ‘all’ or -1, then every message in the queue will be available as part of the detailed diagnosis information.

• To make diagnosis more efficient and accurate, the eG system 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 component, choose the Onoption against DETAILED DIAGNOSIS. 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 requencies 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 *ldquo;$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.