The WASJVMTest monitors the usage of the WebSphere JVM heap. This page depicts the default parameters that need to be configured for the WASJVMTest.

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

• In the SERVERHOSTNAME text box, specify the host name of the application server instance being monitored.

• In the APPPORT text box, specify the port number to be used for accessing the egurkha application that has been deployed on the server.

• Specify the NODENAME of the application server instance being monitored. To know the node name, do the following:

  • Login to the WebSphere Administrative Console.

  • Expand the Servers node in the tree structure in the left pane of the console, and click on Application Servers within.

  • A list of application server instances and their corresponding node names will then appear in the right pane of the console. From this list, you can figure out the Node that corresponds to the application server instance being monitored, and specify that name against the NODENAME parameter.

Note

As websphere is case-sensitive, please pay attention to the case of the characters in the NODENAME, and provide this specification accordingly.

• Provide the name of the server instance being monitored in the SERVERNAME text box. To know the server name, do the following:

  • Login to the WebSphere Administrative Console.

  • Expand the Servers node in the tree structure in the left pane of the console, and click on Application Servers within.

  • A list of application server instances and their corresponding node names will then appear in the right pane of the console. From this list, you can figure out the Name of the monitored server instance, and specify that name against the SERVERNAME parameter.

• The applications that are deployed on a server instance use the CONNECTORPORT for all internal communications with the application server. The connector port can be a SOAP port or an RMI port. The default connector port however, is the SOAP port. To know the connector port number, do the following:

  • Login to the WebSphere Administrative Console.

  • Expand the Servers node in the tree structure in the left pane of the console, and click on Application Servers within.

  • A list of application server instances and their corresponding node names will then appear in the right pane of the console. In the right pane, click on the server name link that corresponds to the server instance that is being monitored.

  • Doing so invokes the Configuration of the application server instance clicked on. Scroll down the Configuration tab page to view the Communications section.

  • Expand the Ports link in this section to view a list of ports. If the default connector port is in use, then the port number displayed against SOAP_CONNECTOR_ADDRESS should be specified as the CONNECTORPORT.If an RMI port has been explicitly set as the connector port, then specify the port number displayed against BOOTSTRAP_ADDRESS as the CONNECTORPORT.

• Select Yes if SSL (Secured Socket Layer) is to be used to connect to the WebSphere server, and No if it is not. 

• If security has been enabled for the WebSphere server being monitored, then provide a valid USER name and PASSWORD, and confirm the password by retyping it in the CONFIRM PASSWORD text box. If the WebSphere server does not require any authentication, then the USER, PASSWORD, and CONFIRM PASSWORD text boxes should contain the default value 'none'.

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

When changing default configurations of tests, the values with "$" indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to "xyz" and $port will be changed to "80" when configuring a test.