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
Overview
The table below describes each of the classes in the auto-discovery class hierarchy.
Table 2‑1. Auto-Discovery Classes
Class Description When to Use
ServerDetector
Abstract class.
ServerDetector is the base auto-
discovery class.
ServerDetector is an abstract class
and must be inherited, rather than
used directly. It may be extended by a
custom auto-discovery class.
PlatformServiceDetector
Abstract class.
Intended for use by platform types
with service types, but no server
types.
DaemonDetector
Discovers server types via a Sigar
query of system process table.
MxServerDetector
Discovers JMX server types via a
Sigar query of system process table.
Discovers JMX services by MBean
query.
SunMxServerDetector
Detector for Sun 1.5+ JVMs with
remote JMX enabled. Note, JVM
resource must be explicitly
configured.
SNMPDetector
Discovers SNMP server types via a
Sigar query of system process table.
Discovers SNMP services view
SNMP request.
Auto-Discovery Interfaces
The built-in auto-discovery classes in VMware vRealize Operations Manager each implement one or more
interfaces.
The interfaces that are implemented are listed below.
org.hyperic.hq.product.
AutoServerDetector
This interface is used by the default scan, which discovers servers by
scanning the process table or Windows registry.
org.hyperic.hq.product.
FileServerDetector
This interface is used by the file system scan. Plug-ins specify file patterns to
match in etc/hq-server-sigs.properties.
When a file or directory matches one of these patterns, the method is
invoked. The plug-in uses the matched file or directory as a hint to find
server installations.
org.hyperic.hq.product.
RuntimeDiscoverer
This interface is used by the run-time scan. This differs from the default and
filesystem scan, which do not necessarily require a server to be running
before it can be detected. Classes that implement the RuntimeDiscoverer
interface communicate directly with a running target server to discover
resources.
Endpoint Operations Management Agent Plug-in Development Kit
40 VMware, Inc.