d8888 888 888      88888888888 888      d8b                                 888       888          888       .d8888b.           888                               
      d88888 888 888          888     888      Y8P                                 888   o   888          888      d88P  Y88b          888                               
     d88P888 888 888          888     888                                          888  d8b  888          888      Y88b.               888                               
    d88P 888 888 888          888     88888b.  888 88888b.   .d88b.  .d8888b       888 d888b 888  .d88b.  88888b.   "Y888b.   88888b.  88888b.   .d88b.  888d888 .d88b.  
   d88P  888 888 888          888     888 "88b 888 888 "88b d88P"88b 88K           888d88888b888 d8P  Y8b 888 "88b     "Y88b. 888 "88b 888 "88b d8P  Y8b 888P"  d8P  Y8b 
  d88P   888 888 888          888     888  888 888 888  888 888  888 "Y8888b.      88888P Y88888 88888888 888  888       "888 888  888 888  888 88888888 888    88888888 
 d8888888888 888 888          888     888  888 888 888  888 Y88b 888      X88      8888P   Y8888 Y8b.     888 d88P Y88b  d88P 888 d88P 888  888 Y8b.     888    Y8b.     
d88P     888 888 888          888     888  888 888 888  888  "Y88888  88888P'      888P     Y888  "Y8888  88888P"   "Y8888P"  88888P"  888  888  "Y8888  888     "Y8888  
                                                                 888                                                          888                                        
                                                            Y8b d88P                                                          888                                        
                                                             "Y88P"                                                           888   

All Things WebSphere

Concerns and issues relating to all versions of WebSphere Application Server

Tuesday, February 21, 2012

 

WebSphere Application Server Performance Tuning Toolkit

IBM has released the WebSphere Application Server Performance Tuning Toolkit that gives the ability to monitor multiple WebSphere Application Servers from an eclipse workspace*. This tools uses WAS Performance Monitoring statistics to get and chart statistics that indicate the health and well being of your server. * Please note that the tool has been released on an as-is basis with no support

Now available in IBM Support Assistant
http://www-304.ibm.com/support/docview.wss?uid=swg21577660.

http://www.ibm.com/developerworks/websphere/downloads/peformtuning.html




Why this tool instead of the other monitoring solutions
1. Its free :-)
2. No agents needed on the server
2.  Monitor multiple servers

3. This tool  provides a standalone viewer for PMI and mbean statistics. It has a RCP GUI which uses the  WebSphere application server admin thin client  to call a JMX proxy, the JMX proxy will communicate with the WAS via the SOAP/RMI.

4, Predefined alerts and actions.
· If the heapsize reaches the maximum heap size, it will generate a runtime alert.
· If the thread pool reaches the threshold, it will generate a threadpool alert.
· If the CPU usage reaches 90%, it will generate a runtime alert.
· If some servlet error occur, it will generate a servlet alert.
· If some connection timeout occurs, it will generate a connection alert
· If there are some thread waiting for connection, it will generate a connection alert
· If there are more then 1000 prepared statement discarded, it will generate a connection alert
· If application try to use some invalidated session, it will generate a session alert
· If there is no room for new session, it will generate a session alert
· If some hung thread decleared, it will generate a threadpool alert
· If some transactions rolled back, it will generate a transaction alert
· If some transactions timeout, it will generate a transaction alert
· You can define your own rules.

5. Monitoring

The monitor panel presents performance data (Servlet Response Time, Transaction Response Time, Jdbc Response Time, Servlet Throughput, Transaction Throughput, Jdbc Throughput, Concurrency) in a classified views to help you with correlation and provide a comprehensive view of the state of the server. 
you analyze the performance problems in your environment.



Response Time page
The response time page presents the response time of a server. It collects data from four components i.e. servlet, transaction, EjbMethod and JDBC.

Throughoutput page
The throughoutput page presents the throughoutpage of a server. 
It displays data from four components. i.e. servlet, transaction, EjbMethod and JDBC.



Concurrency page
The concurrency page presents the concurrency of a server collecting data rom four components transaction, EjbMethod and JDBC.


Alert page
The alert page presents the alert evens of a server. 
You can find the alert detail from the alert type and alert description columns.

Servlet page
The servlet page presents the servlet detail informations of a server. 
You can find the response time, throughoutput, concurrency and error count in the columns. 
When you expand the row , you will get the servlet page detail of you application.

Transaction page
The transaction page presents the transaction information of a server.
 It displays  response time, through output, roll back count, global timeout count, local timout count, global response time, local response time.

EJB page
The EJB page presents the EJB information of a server. It collects and displays response time, throughput and concurrent invocation data. 
When you expand the row, you can find the detail contribution of your application. The different colors mean the degree of the contributions.

Connection Pool page
The connection pool page presents the connection pool information of a server. 
It collects data from connection use time, connection through output, error count, wait time, JDBC through output, JDBC response time, JDBC concurrency, statement discard.
When you expand the row, you can find the detail information of different JDBC connections. 

Runtime page
The runtime page presents the runtime information of a server. 
It collects data from CPU usage, Max heap size, heap size, used heap size.

Session page
The session page presents the session information of a server.
It collects data from live count, life time, affinity break, time out count, active non-exist count, no room count, cache discard count. 
When you expand the row, you can find the detail information of your different applications. The different colors mean the different contribution to the whole time.

ThreadPool page
The Thread pool page presents the thread pool information of a server.
It collects data from max size, pool size, use pool, min size, declared thread hung count, concurrent hung thread count, cleared thread hung count. 
When you expand the row, you can find the detail information of different thread pools. The colors mean the different contributions.

For more see http://www.ibm.com/developerworks/websphere/downloads/peformtuning.html

FAQ: 

Has this tool been used on most distributed platforms (windows, linux, AIX, solairs)?   z/OS supported?   I saw the UI option for 'tail systemout.log', will this work on Windows?  or the tool can do some converting to allow 'tail' to work?
The tool can monitor all the platform include z/OS. but some configuration functions do not work zWAS because of the difference between ZOS and distribute platform. The tail function works on window. Infact, the log was collected via JMX. It does not use the "tail -f" command, and you can take it as a improved log viewer in admin console. The toolkit is based on the PMI and JMX, but it does not use any functions of TPV.

 The tool seems to be able to grab the server information including proxy.  What if we have IHS web server configured, will this web server be monitored?   If messaging SIBus is configured, I guess this will not be monitored?  If we have application client (for java client testing) installed, which is not viewable from the dmgr cell, assuming it will not be monitored either?
The toolkit does not support IHS  by now.  It does NOT monitor SIBus as well,  but we may be able to add this function in future if needed. The app client is also not monitored.



Labels:


Comments:

Post a Comment

Subscribe to Post Comments [Atom]



Links to this post:

Create a Link



<< Home

Archives

December 2006   September 2008   January 2009   February 2009   March 2009   September 2009   October 2009   November 2009   December 2009   January 2010   February 2010   March 2010   April 2010   October 2010   January 2011   February 2011   April 2011   May 2011   June 2011   July 2011   August 2011   September 2011   October 2011   November 2011   December 2011   January 2012   February 2012   March 2012   April 2012   May 2012   June 2012   July 2012   August 2012   September 2012   October 2012   November 2012   January 2013   May 2013   June 2013   July 2013   September 2013   October 2013   June 2014  

This page is powered by Blogger. Isn't yours?

Subscribe to Posts [Atom]