So what kind of data does Waveset expose using JMX MBeans? The following table contains a list of MBeans, describes the data they provide, and explains how to use that data.
MBean |
Description |
Use |
---|---|---|
Cluster |
Names of the servers in the Waveset cluster, including which servers Waveset considers active. |
Provides a quick status of the cluster from the perspective of one Waveset server. |
ObjectRepository |
Waveset repository configuration data, including database name and version, JDBC driver version, and connection pooling settings |
Shows everything you need to know about how Waveset talks to the repository. |
Performance |
Contains sub-beans for DataExporter, DataQueue, FormConverter, ObjectChangeNotification, Reconcile, Rule, TaskInstanceCache, ViewMaster, and WorkItemCache execution. |
Identifies GUI performance problems and provides visibility into how these subsystems perform. You can enable these beans to capture data that can quickly isolate why a particular page loads slowly on a production server. |
Scheduler |
Internal processing counters for the Scheduler |
Provides detailed visibility into what the Scheduler is doing at any given point in time. Making use of this bean requires an in-depth understanding of how the Scheduler works. |
Server |
Current status of this Waveset server |
Shows server status |
<resource name> |
Operational statistics for each resource and connector used by Waveset. |
Shows the count and maximum, minimum, and average time for each resource operation. Gives visibility into the performance of the resource, the Waveset interface, and the Waveset activity on each resource. |
Every application server also provides a number of useful MBeans. These MBeans typically supply information about the application server's processing elements such as HTTP processing, DataSource operations, classloading, and JSP compilation. If you have never browsed the MBeans provided by your application server, consider doing so.