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
n
FileServerDetector Class on page 53
The FileServerDetector interface is used to discover server resources based on a file system scan. This
interface is used when a user manually invokes new autodiscovery on platform object level.
n
MxServerDetector Class on page 57
The MxServerDetector class auto-discovers JMX servers.
n
RegistryServerDetector Class on page 58
The RegistryServerDetector interface is used to discover server objects that are found by scanning the
Windows registry.
n
ServerDetector Class on page 62
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.
n
SNMPDectector Class on page 64
You can use the SNMPDetector class in XML-only plug-ins that extend the Network Device plug-in, or
SNMP-enabled servers, such as Squid.
DaemonDetector Class
The DaemonDetector class auto-discovers a single process and adds the related PTQL query to the resource
configuration.
Class Hierarchy
java.lang.Object
org.hyperic.hq.product.GenericPlugin
[org.hyperic.hq.product.ServerDetector|ServerDetector]
org.hyperic.hq.product.DaemonDetector
Resource Properties
This table describes the resource data that you can define in the plug-in descriptor for a plug-in that uses
DaemonDetector.
Property Description Usage
PROC_QUERY
Initiates a PTQL query to identify the server object. Mandatory
AUTOINVENTORY_NAME
Formats the auto-inventory name as defined by the plug-in. Optional
INSTALLPATH_MATCH Returns true if the installation path matches the specified substring.
Optional
INSTALLPATH_NOMATCH Returns false if the installation path matches the specified substring.
Optional
INVENTORY_ID
The installation path parameter. Optional
PROC_QUERY
The default PTQL query to scan for.
HAS_BUILTIN_SERVICES Scans for built-in service objects. The default is false.
Optional
VERSION_FILE Returns true if the specified file exists in the installation path.
Optional
Example: Usage
This example defines a new server object that is auto-discovered using a PTQL process query.
<server name="My Single Process Server">
<property name="PROC_QUERY" value="State.Name.eq=myprocess"/>
Endpoint Operations Management Agent Plug-in Development Kit
52 VMware, Inc.