The WASConnPoolTest monitors the usage of the connection pools on the WebSphere server. 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.

• Specify the IP address of the WebSphere application server in the HOST text box.

• Specify the port number of the WebSphere application server in the PORT text box.

• 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 node name of the application server instance being monitored in the NODENAME text box. 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.

  If the server instance being monitored is part of a WebSphere cluster, then you need to provide the host name that corresponds to the connector port of the Deployment Manager of the cluster as the SERVERNAME. To determine the SERVERNAME in this case, do the following:

  • Connect to the WebSphere Administrative console using the URL: http://<DeploymentManagerIP>:<DeploymentManagerPort> or https://<DeploymentManagerIP>:<DeploymentManagerPort>.
  • Login to the WebSphere Administrative console
  • Expand the System Administration node in the tree-structure in the left pane of the console and click on the Deployment Manager sub-node within.
  • In the right panel, click on the Configuration tab page to view the configuration of the Deployment Manager. In the Additional Properties section of the Configuration tab page, expand the Ports node.
  • A list of ports will then appear. Click on the Details button alongside the ports list.
  • If the SOAP port has been set as the connector port in your environment, then scroll down the page that appears next until you view the Port Name, SOAP_CONNECTOR_ADDRESS. Make note of the Host name that corresponds to this port name. If the RMI port is the connector port in your environment, then make note of the Host name that corresponds to the Port name, BOOTSTRAP_ADDRESS.
  • Specify this Host name as the SERVERNAME.

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

  If the server instance being monitored is part of a WebSphere cluster, then you need to provide the SOAP/RMI port of the Deployment Manager of the cluster as the CONNECTORPORT. To determine the CONNECTORPORT in this case, do the following:

  • Connect to the WebSphere Administrative console using the URL: http://<DeploymentManagerIP>:<DeploymentManagerPort> or https://<DeploymentManagerIP>:<DeploymentManagerPort>.
  • Login to the WebSphere Administrative console.
  • Expand the System Administration node in the tree-structure in the left pane of the console and click on the Deployment Manager sub-node within.
  • In the right panel, click on the Configuration tab page to view the configuration of the Deployment Manager. In the Additional Properties section of the Configuration tab page, expand the Ports node.
  • A list of ports will then appear. 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'.

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