Performance Monitoring

1. Across locations, platforms, and applications in virtual, physical and cloud environments.

Bank of Montreal: Huge Savings in Virtualization

"We've been able to stretch the hardware a lot further, and in some cases we're getting 50-to-1 virtual workloads per server with up.time."

"We saved 50% during our initial implementation of up.time across 275 servers and couldn’t be happier with uptime’s solution and their service.”

Bank of Montreal.

Contact Us

+ 1.416.868.0152
info@uptimesoftware.com

More Information

> 10 Reasons to Consider up.time (1-Page PDF)

> up.time Product Data Sheet (1-page PDF)

Easy WebSphere Monitoring

up.time's Alerts will keep you aware of potential user experience and transaction performance problems, keep you in control of your WebSphere performance.
Reports and 3-D graphs will help you understand the correlation between WebSphere performance and application server behavior.
Quickly profile and diagnose WebSphere application/database issues before they become serious.
Affordable with Per-Physical-Server Pricing: Complete application and server monitoring for one price. No tiers or management packs and free lifetime upgrades with support. Just count your physical servers (even in virtual environments!). Installs in minutes, deploys in as little as 1-day.
For more tech specs, visit: WebSphere Monitoring and WebSphere Reporting

WebSphere Performance Monitoring and Reporting Software for Your Critical WebSphere Application Servers.

WebSphere Report

Why is up.time your answer for monitoring WebSphere?

Reports, Graphs, and Alerts detect WebSphere performance problems before they affect your end users or impact service levels. up.time will always let you know when your application response time degrades in any way.

Quickly identify potential WebSphere performance problems in your J2EE environment by combining up.time's detailed system performance metrics with connection pool, JVM, EJB, and servlet metrics.

up.time is ideal for characterizing the behavior of applications running in WebSphere inside a development/QA environment. Monitor and report on how these applications perform both when testing and again once deployed in a production environment.

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 monitoring

Performance Counters

In addition to the WebSphere metrics that 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.

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.

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.

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.

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.

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.

Start Monitoring and Reporting on WebSphere in less than 15 minutes:

Download a 30-Day Free Trial Here.

Recommended by: