WebSphere Support in up.time

up.time enables you to monitor the performance and health of J2EE/Java applications that are running on a WebSphere server.

You can now identify correlations between system performance and the J2EE application server, track end-user and database response times, as well as a number of other statistics, for a WebSphere server. The diagram below shows how you can profile the many components of a J2EE environment and analyze the performance data to identify tuning opportunities, possible issues with application code, end-user response time problems, and database throughput.

WebSphere Reporting

Performance Counters

In addition to the WebSphere metrics that up.time collects, detailed system level performance metrics are also available. This enables you to analyze system compute performance, memory usage, disk and network performance, and then relate underlying system behavior to specific metrics within WebSphere. You can also use the information that up.time collects to generate reports that chart the historical performance of the server and the applications that are running on it.

EJB Counters

The following counters contain information about the Enterprise JavaBeans (EJBs) that are running on the WebSphere server:

  • CreateCount
    The number of times that the Enterprise JavaBeans that are running on the server were created.
  • RemoveCount
    The number of times that the EJBs were removed.
  • PassivateCount
    The number of times that EJBs were removed from the cache. Note that passivation preserves the state of the EJBs on the disk.
  • MethodCallCount
    The total number of method calls that were made to the EJBs.
  • MethodResponseTime
    The average response time, in milliseconds, on the bean methods.

Connection Pool Counters

The following counters contain performance information for JDBC connections to the data sources used by the WebSphere server:

  • PoolSize
    The size of the connection pool to the data source.
  • FreePoolSize
    The number of free connections in the pool.
  • PercentUsed
    The percentage of the connection pool that is currently in use.
  • WaitTime
    The average time, in milliseconds, that a connection is used. The average time is the difference between the time at which the connection is allocated and the time at which it is returned.
  • CreateCount
    The total number of connections that were created.
  • CloseCount
    The total number of connections that were closed.
  • WaitingThreadCount
    The number of threads that are currently waiting for a connection.
  • UseTime
    The average time, in milliseconds, that a connection is used. The average use time is the difference between the time at which the connection is allocated and that time at which it is returned.

Java Virtual Machine Counters

The following counters contain performance information for the Java Virtual Machine (JVM) that is running on a WebSphere server:

  • cpuUsage
    The percent of CPU resources that were used since the last query.
  • HeapSize
    The total amount of memory that is available for the JVM.
  • UsedMemory
    The amount of memory that is being used by the JVM.

Transaction Counters

The following counters contain information about WebSphere global transactions (ones that span multiple resource managers):

  • ActiveCount
    The number of global transactions which are concurrently active.
  • CommittedCount
    The total number of global transactions that have been committed.
  • RolledBackCount
    The total number of global transactions that have been rolled back.

Other Counters

The following counters contain information about the servlets that are running on the WebSphere server:

  • LiveCount
    The number of servlet sessions that are currently cached in memory.
  • PoolSize
    The average number of threads in the servlet connection thread pool.
  • TimeSinceLastActivated
    The difference, in milliseconds, between the previous and current access time stamps of a servlet session. This counter does not include session time out values.