Use SilkPerformer's Performance Explorer tool, following the steps below: Launch Performance Explorer and select the MONITOR SERVER button in the workflow bar. Select the radio button "Select from predefined Data Sources", do not use the radio button "Have Data Sources detected" as the data source detection module does not detect IBM WebSphere Application Servers. Select APPLICATION SERVERS/IBM WEBSPHERE APPLICATION SERVER/IBM WEBSPHERE APPLICATION SERVER 3.5/4.0 and connect to the host running the Application Server. Once a connection to the server is established; this may take 3 to 5 seconds, the dialog shows the root nodes of the WebSphere Administrative domain. Select PERFORMANCE COUNTERS and click the ADD button to add them to the monitoring template. Important note : Performance Explorer connects to a daemon, or service, named IBM WS AdminServer. This service is running per default unless the Standard Edition of IBM WebSphere Application Server 3.5, 4.0 is being used. Typical Performance Measures on WebSphere Application Servers 3.5: Runtime Module: Contains performance counters related to the Java Virtual Machine Thread Pool: Answers questions like how many threads are currently active or how many threads were created, this includes idle and active threads. Bean Data: Specific performance information about deployed EJBs. For example how many beans were created or the response time of method invocations. Transaction Data: Contains everything about transactions like how many transactions are currently in progress or the average time it takes to execute one transaction. Connection Manager: Contains performance counters for JDBC connections. Servlet Engine: Contains performance counters giving an idea how deployed Servlets and JSPs perform. Typical Performance Measures on WebSphere Application Servers 4.x: BeanModule: Specific data about deployed EJBs. For example how many beans were created? ConnectionPoolModule: This module contains performance counters about JDBC connections like how many JDBC connections are currently in the pool. JvmRuntimeModule: Java Virtual Machine specific performance counters. ServletSessionModule: This module contains performance counters about Servlet sessions. For example how many sessions are active or the average session live time. TransactionModule: This module contains performance counters giving information how many transactions are in progress or the average time it takes to execute one transaction. WebApplicationModule: Provides information about deployed Servlets and JSPs. For example the average time it takes the Servlet to process requests. To monitor using WebSphere's "Performance Servlet" you will need to configure this first, please see the resolution below: How do I configure IBM WebSphere Application Server 4.x "Performance Servlet" in order to monitor using Performance Explorer?
↧