Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle GlassFish Server 3.1 Add-On Component Development Guide |
1. Introduction to the Development Environment for GlassFish Server Add-On Components
3. Extending the Administration Console
4. Extending the asadmin Utility
Defining Statistics That Are to Be Monitored
Defining an Event Provider by Writing a Java Class
Defining Event Types in an Event Provider Class
Example of Defining an Event Provider by Writing a Java Class
Defining an Event Provider by Writing an XML Fragment
Packaging a Component's Event Providers
Updating the Monitorable Object Tree
Representing a Component's Statistics in an Event Listener Class
Subscribing to Events From Event Provider Classes
Dotted Names and REST URLs for an Add-On Component's Statistics
Example of Adding Monitoring Capabilities
6. Adding Configuration Data for a Component
7. Adding Container Capabilities
8. Creating a Session Persistence Module
9. Packaging, Integrating, and Delivering an Add-On Component
Monitoring is the process of reviewing the statistics of a system to improve performance or solve problems. By monitoring the state of components and services that are deployed in the GlassFish Server, system administrators can identify performance bottlenecks, predict failures, perform root cause analysis, and ensure that everything is functioning as expected. Monitoring data can also be useful in performance tuning and capacity planning.
An add-on component typically generates statistics that the GlassFish Server can gather at run time. Adding monitoring capabilities enables an add-on component to provide statistics to GlassFish Server in the same way as components that are supplied in GlassFish Server distributions. As a result, system administrators can use the same administrative interfaces to monitor statistics from any installed GlassFish Server component, regardless of the origin of the component.
The following topics are addressed here: