IBM Hybrid Connect registration and usage reporting provides cloud-based tracking of cloud resident and on-premises installations of certain IBM middleware products, including the latest WebSphere Liberty beta.
Now, WebSphere Application Server traditional is joining the family of products that you can track through the Hybrid Connect service.
To test out tracking your WAS traditional servers and clusters, you’ll need to install Fix Pack 188.8.131.52, plus an additional test fix as described in the configuration instructions. Note that this is a test fix, and as such is not supported for production workloads.
Once configured for Hybrid Connect, each WAS traditional server registers with the service and provides the following information:
- The installation version and any installed APARs
- The Java runtime used
- The host and directory on which it is configured
- The server name.
Additionally, each registered server or cluster periodically reports usage metrics to indicate what resources are being used, including:
- Available processors
- CPU consumption
- Memory consumption
- If the Performance Monitoring Infrastructure (PMI) metric is enabled, the number of HTTP requests handled
Registration and usage reporting are controlled by the administrator and can be turned on or off at any time. To view registration and usage of WebSphere instances, see the previous blog entry about using the Hybrid Connect management console with Liberty.