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
RegistryServerDetector Class
The RegistryServerDetector interface is used to discover server objects that are found by scanning the
Windows registry.
Scan criteria are specified in a <scan> element in the plug-in descriptor.
The following element attributes define where to search in the registry and what registry key to look for.
n
registry - This attribute specifies a registry path in the Windows registry. Subkeys of the specified path
are scanned. You can designate several search roots by appending the path with an asterisk.
n
include - This attribute specifies the name of a key in the Windows registry. A <scan> element can
contain multiple include attributes. The registry scan does not support wildcards in the registry key
name.
The following <scan> element results in a scan for a subkey of "SOFTWARE\Microsoft\Internet Explorer.
<scan registry="SOFTWARE\Microsoft\Internet Explorer">
<include name="AppName"/>
</scan>
RegistryServerDetector is called for each resource in the Windows registry that matches the scan criteria.
You can extend the search to multiple root keys by ending the key name with "". For example,
SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\MySQL" only searches for subkeys of ...\Uninstall
that start with MySQL.
Interface Hierarchy
org.hyperic.hq.product.RegistryServerDetector
Interface References
package org.hyperic.hq.product;
import java.util.List;
import org.hyperic.sigar.win32.RegistryKey;
import org.hyperic.util.config.ConfigResponse;
Implementing Methods
This interface implements the following methods.
getServerResources(Conf
igResponse,String):List
public List getServerResources(ConfigResponse platformConfig, String
path, RegistryKey current)
throws PluginException;
This method is called if the associated autodiscovery implementation is
implementing this interface.
Parameters: platformConfig Configuration for the underlying platform object.
path Value of the matched key.
current Current registry object.
Returns:
A list of ServerResource objects.
Exceptions:
org.hyperic.hq.product.PluginException
getRegistryScanKeys():L
ist
public List getRegistryScanKeys();
Endpoint Operations Management Agent Plug-in Development Kit
58 VMware, Inc.