Configuration of JEUSQueueTest

This test auto-discovers the queues on a JEUS server, and reports the status of production and consumption on each queue. This test also reveals the number of messages that were processed/dispatched/delivered/expired/moved out of each queue. Besides, the count of consumers accessing each queue and the number of messages that per pending on each queue are also reported. By analyzing these details, administrators can proactively isolate and correct impending overloads and probable delivery bottlenecks on the queues.

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, specify the port at which the specified host listens to. By default, this is set to 9736.

• To enable the eG agent to communicate and continuously monitor the target JEUS server, the eG agent should be configured with the credentials of the user with administrator privileges on the server. In highly-secure environments, administrators may not want to expose the credentials of the user possessing administrator privileges. In such environments, for monitoring the JEUS server, administrators have an option to create a new user on the JEUS server and assign administrator privilege to that user. The steps to create a new user with administrator privilege are explained in the Monitoring JEUS Server document. This user should also be granted permission to access the JNDI objects on the server such that the eG agent can pull out performance metrics from the JEUS server. To know how to grant permission to access the resources, refer to the Monitoring JEUS Server document.

• Confirm the Password by retyping it in the CONFIRM PASSWORD text box.

• To collect metrics from the target server, the eG agent should be configured to use JMX to connect to the JRE used by the target server and pull out the performance metrics. By default, JMX support is enabled for the JRE used by the target server. The JMX connector listens on port 9736, by default. Therefore, type 9736 as the LISTENER PORT. However, if the host is configured with multiple sever instances, then you should specify the port number at which the JMX listens in your environment. Ensure that you specify the same port that you configured while creating the listener (if required) using the JEUS WebAdmin Console. To know the details on the listener port, refer to the Monitoring JEUS Server document.

• The export name is the reference name of the RMI connector that is to be used as a JMX connector. The procedure to obtain the export name is detailed in the Monitoring JEUS Server document. Specify the name of the export against the EXPORT NAME parameter.

• Provide the name of the sever instance that is being monitored in the Server Name text box. Also, ensure that the JVM monitoring is enabled for the target server. To obtain the name of the server instance, refer to the Monitoring JEUS Server document.

• To make diagnosis more efficient and accurate, eG 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, by default, for a particular server, 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 bad and normal 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.