Platform requirements

The Health Center client and Health Center agent have unique platform requirements. The functionality available with the agent depends on the level of Java™ Runtime Environment (JRE) you are using.

Platform requirements for the client

The Health Center client requires either the Microsoft® Windows® or Linux® x86 operating system using the supplied JRE. The client is Eclipse RCP-based; the minimum operating system requirements for the client are the same as the Eclipse RCP project, see http://www.eclipse.org/documentation/.

Platform requirements for the agent

The application that you want to monitor requires a minimum level of JRE with a Health Center agent installed. Later levels of JRE provide more Health Center function; the table shows at which JRE service refresh each function becomes available.

Some JRE levels come with an agent installed by default. To enable more function, install a later, updated, agent. See Installing the Health Center agent for more information. The level of function provided by default and updated agents is described in the following table.

To use Health Center on a production system, run Java 5 JRE SR10 or later, or run Java 6 JRE SR5 or later.

Using the Health Center in production environments

The Health Center has a minimal affect on the system being monitored. However, it is not suitable for production use on Java 5 JRE before SR10, or Java 6 JRE before SR5.

Java version Function with default agent Function with updated agent Suitable for production use Command-line options to enable agent
Java 5 SR8 No agent included Profiling, Garbage collection, locking, classes, environment, memory No
-agentlib:healthcenter 
-Xtrace:output=perfmon.%p.out
Java 5 SR9 Profiling, Garbage collection, locking Profiling, Garbage collection, locking, classes, environment, memory No
-agentlib:healthcenter 
-Xtrace:output=perfmon.%p.out
Java 5 SR10 or later Profiling, Garbage collection, locking, classes, environment Profiling, Garbage collection, locking, classes, environment, memory, large object allocation, IO Yes
-Xhealthcenter
Java 6 SR1 No agent included Profiling, Garbage collection, locking, classes, environment, memory No
-agentlib:healthcenter 
-Xtrace:output=perfmon.%p.out
Java 6 SR2 No agent included Profiling, Garbage collection, locking, classes, environment, memory No
-agentlib:healthcenter 
-Xtrace:output=perfmon.%p.out
Java 6 SR3 Profiling, Garbage collection, locking, classes Profiling, Garbage collection, locking, classes, environment, memory No
-agentlib:healthcenter 
-Xtrace:output=perfmon.%p.out
Java 6 SR4 Profiling, Garbage collection, locking, classes Profiling, Garbage collection, locking, classes, environment, memory No
-agentlib:healthcenter 
-Xtrace:output=perfmon.%p.out
Java 6 SR5 or later Profiling, Garbage collection, locking, classes, environment Profiling, Garbage collection, locking, classes, environment, memory, large object allocation, IO Yes
-Xhealthcenter
WebSphere® Real Time for Linux V2 SR2 with APAR IZ61672 Profiling, Garbage collection, locking, classes, environment Profiling, Garbage collection, locking, classes, environment, memory No
-agentlib:healthcenter
-Xtrace:output=perfmon.%p.out
Start of changeWebSphere Real Time for Linux V2 SR3 or later service refreshesEnd of change Start of changeProfiling, Garbage collection, locking, classes, environment, WebSphere Real TimeEnd of change Start of changeProfiling, Garbage collection, locking, classes, environment, memory, WebSphere Real Time, IOEnd of change Start of changeYesEnd of change Start of change
-Xhealthcenter
End of change


© Copyright IBM Corporation 2005, 2010. All Rights Reserved.
© Copyright Sun Microsystems, Inc. 1997, 2007, 901 San Antonio Rd., Palo Alto, CA 94303 USA. All rights reserved.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This information center is powered by Eclipse technology. (http://www.eclipse.org/)