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
ServerDetector Class
The ServerDetector class is the base implementation for autodiscovery. ServerDetector is an abstract class,
so cannot be directly used for auto-discovery. An auto-discovery implementation must inherit
ServerDetector.
Class Hierarchy
java.lang.Object
org.hyperic.hq.product.GenericPlugin
org.hyperic.hq.product.ServerDetector
Resource Properties
The table below describes the resource data that you can define in the plug-in descriptor for a plug-in that
uses an auto-discovery implementation based on ServerDetector.
Resource properties that are not user-configurable are defined in <property> elements in the descriptor.
Property Description Usage
INSTALLPATH
Overwrites the installation path. Optional
INSTALLPATH_MATCH
See Using Extra Filters below. Optional
INSTALLPATH_NOMATCH
See Using Extra Filters below. Optional
VERSION_FILE
See Using Extra Filters below. Optional
INVENTORY_ID
Overwrites the autoinventory ID (AIID). Optional
AUTOINVENTORY_NAME
Formats the discovered object name. Optional
Using Extra Filters
You can use the additional filters INSTALLPATH_MATCH, INSTALLPATH_NOMATCH and VERSION_FILE to filter
discovered resources based on the discovered installation path.
The filters are used in the following order.
1 If VERSION_FILE is not detected, the resource is skipped.
2 If INSTALLPATH_MATCH is not detected from the installation path, the resource is skipped.
3 If INSTALLPATH_NOMATCH is detected from installation path, the resource is skipped.
Using INSTALLPATH
Every server type object must have a value for the installation path property. When you create a server
object manually from the user interface, this property is required.
For server types that are auto-discovered, the installation path is resolved automatically. It is usually either
the server home directory or the process working directory. You can use INSTALLPATH to overwrite a
resource's discovered installation path.
Endpoint Operations Management Agent Plug-in Development Kit
62 VMware, Inc.