Platform requirements
The Health Center client and monitoring agent have unique platform requirements. The functions that are available with the agent depend on the level of runtime environment that you are using.
Platform requirements for the client
The Health Center client is Eclipse RCP-based. The minimum operating system requirements for the client are therefore the same as the Eclipse RCP project. For a list of operating systems supported by Eclipse, view the readme file for your Eclipse build. Eclipse builds are listed at http://download.eclipse.org/eclipse/downloads/.
To monitor Bluemix® applications, the client requires IBM® SDK, Java™ Technology Edition, Version 7 or later.
Platform requirements for the agent
The monitoring agent requires one of the following products, each of which has an agent that is installed by default:
- IBM Bluemix with a Liberty for Java or SDK for Node.js runtime environment.
- IBM SDK for Node.js Version 1.1.0.10 onwards. From Versions 1.1.0.7 and 1.2.0.6, the SDK for Node.js contains the Node Application Metrics agent; refer to the Node Application Metrics documentation for information about platform requirements.
Note: You can run the agent on a non-IBM Node.js SDK. However, this scenario is not supported by IBM.
- IBM SDK, Java Technology Edition, Version 5, service refresh 8 onwards
- IBM SDK, Java Technology Edition, Version 6, service refresh 1 onwards
Note: Health Center Version 3.0 and later agents do not run on IBM SDK for Linux on System i® and System p architecture, Java Technology Edition, Version 6, service refreshes 1 through 9. Either use an earlier Health Center agent, such as the one supplied with your level of SDK, or upgrade your version of SDK to at least Version 6, service refresh 10. For more information, see Known limitations.
- Later versions of IBM SDK, Java Technology Edition
- WebSphere® Real Time for Linux, Version 2, service refresh 2 onwards (APAR IZ61672 is required for service refresh 2)
- WebSphere Real Time for Linux, Version 3
Function support
The following tables show the Health Center functions that are supported for various releases of IBM SDK and WebSphere Real Time (not Bluemix).
Support is indicated by the following symbols:
- A dash indicates no support.
- A single tick indicates support in the latest agent only.
- Two ticks indicate support in the default agent and the latest agent.
| Node Application Metrics function |
|---|
| Profiling |
| Garbage collection |
| Environment |
| Events |
| Memory |
| CPU usage |
Note: Because releases of the Node Application Metrics agent are independent of releases of Health Center, the functions that are available with the latest agent might be different from the functions that are shown in the table.
| Health Center function | Initial release and later |
|---|---|
| Profiling | ✓✓ |
| Garbage collection | ✓✓ |
| Locking | ✓✓ |
| Classes | ✓✓ |
| Environment | ✓✓ |
| Events | - |
| Memory | ✓✓ |
| Large object allocation | ✓✓ |
| IO | ✓✓ |
| Dumps | ✓✓ |
| Headless mode | ✓✓ |
| Native memory breakdown | ✓✓ |
| Network | ✓ |
| Method trace | ✓ |
| Threads | ✓ |
| Enabling verbose garbage collection at run time | ✓✓ |
| Allocation sampling | ✓ |
| Attaching the agent to a running application | ✓ |
| Class histogram | ✓ |
| CPU usage | ✓ (not z/OS®) |
| Health Center function | Service refresh 3 and earlier | Service refresh 4 or later | Service refresh 7 or later |
|---|---|---|---|
| Profiling | ✓✓ | ✓✓ | ✓✓ |
| Garbage collection | ✓✓ | ✓✓ | ✓✓ |
| Locking | ✓✓ | ✓✓ | ✓✓ |
| Classes | ✓✓ | ✓✓ | ✓✓ |
| Environment | ✓✓ | ✓✓ | ✓✓ |
| Events | - | - | - |
| Memory | ✓✓ | ✓✓ | ✓✓ |
| Large object allocation | ✓✓ | ✓✓ | ✓✓ |
| IO | ✓✓ | ✓✓ | ✓✓ |
| Dumps | ✓✓ | ✓✓ | ✓✓ |
| Headless mode | ✓✓ | ✓✓ | ✓✓ |
| Native memory breakdown | ✓✓ | ✓✓ | ✓✓ |
| Network | - | - | - |
| Method trace | ✓ | ✓ | ✓ |
| Threads | ✓ | ✓ | ✓ |
| Enabling verbose garbage collection at run time | ✓✓ | ✓✓ | ✓✓ |
| Allocation sampling | ✓ | ✓ | ✓ |
| Attaching the agent to a running application | ✓ | ✓ | ✓ |
| Class histogram | ✓ | ✓ | ✓ |
| CPU usage | - | ✓ | ✓ (not z/OS) |
| Function | Initial release | Service refreshes 1 through 3 | Service refresh 4 or later |
|---|---|---|---|
| Profiling | ✓✓ | ✓✓ | ✓✓ |
| Garbage collection | ✓✓ | ✓✓ | ✓✓ |
| Locking | ✓✓ | ✓✓ | ✓✓ |
| Classes | ✓✓ | ✓✓ | ✓✓ |
| Environment | ✓✓ | ✓✓ | ✓✓ |
| Events | - | - | - |
| Memory | ✓✓ | ✓✓ | ✓✓ |
| Large object allocation | ✓✓ | ✓✓ | ✓✓ |
| IO | ✓✓ | ✓✓ | ✓✓ |
| Dumps | ✓✓ | ✓✓ | ✓✓ |
| Headless mode | ✓✓ | ✓✓ | ✓✓ |
| Native memory breakdown | ✓✓ | ✓✓ | ✓✓ |
| Network | - | - | - |
| Method trace | ✓ | ✓✓ | ✓✓ |
| Threads | ✓ | ✓ | ✓ |
| Enabling verbose garbage collection at run time | - | ✓✓ | ✓✓ |
| Allocation sampling | - | ✓✓ | ✓✓ |
| Attaching the agent to a running application | ✓ | ✓ | ✓ |
| Class histogram | ✓ | ✓ | ✓ |
| CPU usage | - | - | ✓ |
| Function | Service refreshes 1 and 2 (not for production use) | Service refreshes 3 and 4 (not for production use) | Service refresh 5 | Service refreshes 6 and 7 | Service refresh 8 | Service refreshes 9 through 12 | Service refresh 13 or later |
|---|---|---|---|---|---|---|---|
| Profiling | ✓ | ✓✓ | ✓✓ | ✓✓ | ✓✓ | ✓✓ | ✓✓ |
| Garbage collection | ✓ | ✓✓ | ✓✓ | ✓✓ | ✓✓ | ✓✓ | ✓✓ |
| Locking | ✓ | ✓✓ | ✓✓ | ✓✓ | ✓✓ | ✓✓ | ✓✓ |
| Classes | ✓ | ✓✓ | ✓✓ | ✓✓ | ✓✓ | ✓✓ | ✓✓ |
| Environment | ✓ | ✓ | ✓✓ | ✓✓ | ✓✓ | ✓✓ | ✓✓ |
| Events | - | - | - | - | - | - | - |
| Memory | ✓ | ✓ | ✓ | ✓ | ✓✓ | ✓✓ | ✓✓ |
| Large object allocation | - | - | ✓ | ✓ | ✓ | ✓✓ | ✓✓ |
| IO | - | - | ✓ | ✓ | ✓ | ✓✓ | ✓✓ |
| Dumps | ✓ | ✓ | ✓ | ✓ | ✓ | ✓✓ | ✓✓ |
| Headless mode | ✓ | ✓ | ✓ | ✓ | ✓ | ✓✓ | ✓✓ |
| Native memory breakdown | - | - | - | - | - | - | - |
| Network | - | - | - | - | - | - | - |
| Method trace | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Threads | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Enabling verbose garbage collection at run time | - | - | - | - | - | - | - |
| Allocation sampling | - | - | - | - | - | - | - |
| Attaching the agent to a running application | - | - | - | ✓ | ✓ | ✓ | ✓ |
| Class histogram | - | - | - | ✓ | ✓ | ✓ | ✓ |
| CPU usage | - | - | - | - | - | - | ✓ |
| Function | Service refresh 8 (not for production use) | Service refresh 9 (not for production use) | Service refreshes 10 and 11 | Service refresh 12 or later |
|---|---|---|---|---|
| Profiling | ✓ | ✓✓ | ✓✓ | ✓✓ |
| Garbage collection | ✓ | ✓✓ | ✓✓ | ✓✓ |
| Locking | ✓ | ✓✓ | ✓✓ | ✓✓ |
| Classes | ✓ | ✓ | ✓✓ | ✓✓ |
| Environment | ✓ | ✓ | ✓✓ | ✓✓ |
| Events | - | - | - | - |
| Memory | ✓ | ✓ | ✓ | ✓✓ |
| Large object allocation | - | - | ✓ | ✓✓ |
| IO | - | - | ✓ | ✓ |
| Dumps | ✓ | ✓ | ✓ | ✓ |
| Headless mode | ✓ | ✓ | ✓ | ✓ |
| Native memory breakdown | - | - | - | - |
| Network | - | - | - | - |
| Method trace | ✓ | ✓ | ✓ | ✓ |
| Threads (excluding owned monitor information) | ✓ | ✓ | ✓ | ✓ |
| Enabling verbose garbage collection at run time | - | - | - | - |
| Allocation sampling | - | - | - | - |
| Attaching the agent to a running application | - | - | ✓ | ✓ |
| Class histogram | - | - | ✓ | ✓ |
| CPU usage | - | - | - | - |
| Function | Version 2 service refresh 2 with APAR IZ61672 | Version 2 service refresh 3 or later |
|---|---|---|
| Profiling | ✓✓ | ✓✓ |
| Garbage collection | ✓✓ | ✓✓ |
| Locking | ✓✓ | ✓✓ |
| Classes | ✓✓ | ✓✓ |
| Environment | ✓✓ | ✓✓ |
| Events | - | - |
| WebSphere Real Time | - | ✓✓ |
| Memory | ✓ | ✓ |
| Large object allocation | - | - |
| IO | - | ✓ |
| Dumps | - | - |
| Headless mode | - | - |
| Native memory breakdown | - | - |
| Network | - | - |
| Method trace | ✓ | ✓ |
| Threads | ✓ | ✓ |
| Enabling verbose garbage collection at run time | - | - |
| Allocation sampling | - | - |
| Attaching the agent to a running application | - | ✓ |
| Class histogram | ✓ | ✓ |
| CPU usage | - | - |