WAS Web Applications Test
This test auto-discovers the web applications that are executing on the target WebSphere application server and for each web application, this test reports key performance statistics such as throughput, errors encountered by the web application etc.
Target of the test : A WebSphere application server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for each web application running on the target WebSphere application server being monitored
Parameters | Description |
---|---|
Test period |
How often should the test be executed . |
Host |
The IP address of the WebSphere application server |
Port |
The port number of the WebSphere application server |
ServerHostName |
Specify the host name of the application server instance being monitored. |
AppPort |
Specify the port number to be used for accessing the egurkha application that has been deployed on the server. |
NodeName |
eG Enterprise can auto-discover and auto-manage the target application server that is hosted on a container. In such containerized environments, this test can auto-discover the node name corresponding to the target server instance and report the metrics. To this effect, this parameter is set to EG_ENV_WAS_NODE. On the other hand, if the IBM WebSphere Application Server is directly installed in the target environment, you should specify the node name of the server instance being monitored. To know the node name, do the following:
|
ServerName |
eG Enterprise can auto-discover and auto-manage the target application server that is hosted on a container. In such containerized environments, this test can auto-discover the name of target server instance and report the metrics. To this effect, this parameter is set to EG_ENV_SERVER_NAME. On the other hand, if the IBM WebSphere Application Server is directly installed in the target environment, you should provide the name of the server instance being monitored in the SERVERNAME text box. To know the server name, do the following:
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:
|
ConnectorPort |
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:
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:
|
SSL |
Select Yes if SSL (Secured Socket Layer) is to be used to connect to the WebSphere server, and No if it is not. |
User |
If security has been enabled for the WebSphere server being monitored, then provide a valid USER name to login to the WebSphere server. While monitoring IBM Websphere Application server 8.x and above, if the user belongs to an external LDAP directory, then, ensure that the User is assigned the Monitor role. If the WebSphere server does not require any authentication, then the USER text box should contain the default value 'none'. |
Password |
If security has been enabled for the WebSphere server being monitored, then provide the Password that corresponds to the specified User name. If the WebSphere server does not require any authentication, then leave the Password text box with its default setting. |
Confirm Password |
If security has been enabled, confirm the specified Password by retyping it in the Confirm Password text box. If the WebSphere server does not require any authentication, then leave the Confirm Password text box with its default setting. |
Measurement |
Description |
Measurement Unit |
Interpretation |
---|---|---|---|
Loaded servlets |
Indicates the number of servlets that were loaded since the last measurement period. |
Number |
|
Reload count |
Indicates the number of servlets that were reloaded since the last measurement period. |
Number |
|
Request count |
Indicates the number of requests that a servlet/JSP processed since the last measurement period. |
Number |
|
Concurrent requests |
Indicates the current number of requests processed concurrently. |
Number |
|
Error count |
Indicates the number of errors in JSP/Servlet since the last measurement period. |
Number |
|
Service time |
Indicates the response time of the JSP/servlet. |
Secs |
|
Throughput |
Indicates the throughput of this web application. |
Reqs/Sec |
|