PerfServlet input

 

The PerfServlet input and output is used for simple end-to-end retrieval of performance data that any tool, provided by either IBM or a third-party vendor, can handle The PerfServlet is deployed in one of the appserver instance within the domain. By default, the PerfServlet collects all of the performance data across a WAS cell. However, it is possible to limit the data returned by the servlet to either a specific node, server, or PMI module:

Node

.The servlet can limit the information it provides to a specific host by using the node parameter. For example, to limit the data collection to the node ‘rjones’, invoke the following URL:

http://hostname/wasPerfTool/servlet/perfservlet?node=rjones

Server

The servlet can limit the information it provides to a specific server by using the server parameter. For example, in order to limit the data collection to the ‘testserver’ server on all nodes, invoke the following URL:

http://hostname/wasPerfTool/servlet/perfservlet?server=testserver

To limit the data collection to the ‘testserver’ server located on the host ‘rjones’, invoke the following URL:

http://hostname/wasPerfTool/servlet/perfservlet?node=rjones&server=testserver

Module

The servlet can limit the information it provides to a specific PMI module by using the module parameter. You can request multiple modules by using the following URL:

http://hostname/wasPerfTool/servlet/perfservlet?module=beanModule+jvmRuntimeModule

For example, to limit the data collection to the beanModule on all servers and nodes, invoke the following URL:

http://hostname/wasPerfTool/servlet/perfservlet?module=beanModule

To limit the data collection to the beanModule on the server ‘testserver’ on the node rjones, invoke the following URL:

http://hostname/wasPerfTool/servlet/perfservlet?node=rjones&server=testserver&module=beanModule

To find the list of the modules, invoke the PerfServlet help with the following URL:

http://hostname/wasPerfTool/servlet/perfservlet?action=help

In WAS ND (ND), the PerfServlet automatically connects to the deployment manager to provide PMI data about the entire cell. When the performance servlet is first initialized, it retrieves the list of nodes and servers within the domain in which it is deployed. Because the collection of this data is expensive, the performance servlet holds this information as a cached list. If a new node is added to the domain or a new server is started, the performance servlet does not automatically retrieve the information about the newly created element. To force the servlet to refresh its configuration, add the refreshConfig parameter to the invocation as follows:

http://hostname/wasPerfTool/servlet/perfservlet?refreshConfig=true

You may want to configure other parameters of the performance servlets according to your specific needs. You can define the host, port number, connector type, and a user name and password.

 

• Host. This defines the host name where the server is running. The default value is "localhost." For base installations, use "localhost" or "host" where appserver is running. In ND installations, use the Deployment Manager's host name.

  There can be more than one server instance in ND installations and a performance servlet can be installed in any one of the servers.

   

• Port. This is the port through which the server will connect. The default value is '8880' (SOAP connector port in base installation). In a base installation, use the appserver SOAP or RMI connector port.

  In a ND installation, use the Deployment Manager's SOAP or RMI port.

  The port numbers for SOAP/RMI connector can be configured in the console under Servers > Application Servers > server > End Points.

   

• Connector. The connector type can be either SOAP or RMI. The default value is SOAP.

   

• Username. If security is enabled provide the user name.

   

• Password. If security is enabled provide the password.

---

 

Related concepts

PerfServlet output

 

Related tasks

Retrieving performance data with PerfServlet