In such type of scenarios you can easily consume performance statistics from your WebSphere instance. The way is to establish a JMX connection to the JVM and gather the metrics.
However remote JMX connections are not firewall friendly as they require a non standard port for communication.This non standard port has also to be defined in the WebSphere configuration.
WebSphere provides a small and easy to install servlet applications that delivers performance data over http in a xml format.
The application is called PerfServletApp.ear, Performance Servlet or PerfServlet.
The installation is straight forward. Navigate to Applications > Application types > WebSphere enterprise applications > Install and deploy the PerfServletApp.ear located in <WebSphere-Install-Root>/installableApps/PerfServletApp.ear
After deployment the Performance Servlet is reachable under the URL
Filtering the results
The performance servlet provides a basic filter functionality for the xml results. To filter the results simply add parameters to the url. IBM defined serveral parameters:
- Node: http://localhost:9082/wasPerfTool/servlet/perfservlet?node=Marcel-PCNode03
- Server: http://localhost:9082/wasPerfTool/servlet/perfservlet?server=server1
- Module (!): http://localhost:9082/wasPerfTool/servlet/perfservlet?module=testmodule1
- etc.The filters can be combined:
- http://localhost:9082/wasPerfTool/servlet/perfservlet?node=Marcel-PCNode03&server=server1&module=jvmRuntimeModule+systemModule
The PerfServlet has a kind of man page:
http://localhost:9082/wasPerfTool/servlet/perfservlet?action=help
However the PerfServlet is limited and not really for use in large network deployment topology.
Comments
Post a Comment