6.1
Table Of Contents
- Endpoint Operations Management Agent Plug-in Development Kit
- Contents
- About the Endpoint Operations Management Agent Plug-in Development Kit
- Introduction to Plug-in Development
- The Role of the Server and Agent in Plug-ins
- Technical Overview
- Plug-in Implementations
- Using Support Classes to Simplify a Plug-in
- Writing Plug-ins
- JMX Plug-in
- Script Plug-ins
- SNMP Plug-in
- JMX-Based Management
- Auto-Discovery of JMX Resources
- Configuration Properties for JMX Monitoring
- Creating a Custom JMX Plug-in
- Defining Service Types to Provide Management via Custom MBeans
- Defining an ObjectName to Access Custom MBeans
- Defining Configuration Properties to Appear in the User Interface
- Defining and Gathering Metrics
- Specifying the Availability Metric for MBeans
- Implementing Control Actions
- Defining the Server Auto-Inventory Element
- Discovering Custom Properties
- Running and Testing Plug-ins from the Command Line
- Using Auto-Discovery Support Classes in Plug-ins
- Working with Plug-in Descriptors
- Plug-In Support Classes
- Index
The class name varies by type of plug-in. The class in the code snippet is for a JMX plug-in. For a script
plug-in you use the following.
<plugin type="autoinventory" class="org.hyperic.hq.product.DaemonDetector"/>
Auto-discovering Services Resources
You can specify the auto-discovery of a services running on the server by adding another line so that the
plug-in recognizes that the server is hosting services that it must discover.
<property name="HAS_BUILTIN_SERVICES" value="true"/>
For each hosted service enumerated in the plug-in, within the <service> tag, you again call the
autoinventory plug-in, but without a class argument.
<plugin type="autoinventory"/>
Endpoint Operations Management Agent Plug-in Development Kit
46 VMware, Inc.