This reveals the health of the tomcat class loaders and daemon threads, and also indicates the Jvm availability. 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 name of the server for which the test is to be configured has to be specified.

• In the PORT text box, specify the port number at which the host listens.

• The JvmDetailTest makes use of a file named JVMDetails.jsp to generate measures. By default, this file is located in the /lib directory. To execute the JvmDetailTest, move this file to one of the application directories of the Tomcat server. (On Unix, you can execute the script /opt/egurkha/bin/setup_jserver to do this.) While configuring the JvmDetailTest, specify the location of the application directory where the JVMDetails.jsp file resides, in the EGURI text box, in the followingformat: http://. For example, assume that the JVMDetails.jsp is available in the JavaTest directory of the host 192.168.10.57:7077. Therefore, EGURI would be: http://192.168.10.57:7077/JavaTest. list box specifies the directory of the installed virtual desktop manager server. Ex:c:\progra~1\vmwaredecide how often this test needs to be executed. 

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