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
Using Auto-Discovery Support
Classes in Plug-ins 2
You can use the vRealize Operations Manager auto-discovery functionality in a custom plug-in. As most
platform types are discovered by the system plug-in, custom plug-ins discover server and service resource
types.
Auto-Discovery Implementation
The auto-discovery class performs the discovery process. For many resource types, you can reference one of
the vRealize Operations Manager built-in auto-discovery classes. If necessary, you can write a custom auto-
discovery class that extends a vRealize Operations Manager auto-discovery class. Most of the
vRealize Operations Manager auto-discovery implementations discover two levels of resources - servers,
and the services that run in them, so typically you only specify a single implementation in the descriptor.
Parameters Required by the Implementation
In addition to specifying the auto-discovery class, the plug-in descriptor must define the parameters that the
class requires.
This chapter includes the following topics:
n
“Auto-Discovery Classes,” on page 39
n
“Auto-Discovery Interfaces,” on page 40
n
“Specifying Auto-Discovery Implementation for a Resource Type,” on page 41
n
“Measurement Plug-ins,” on page 41
Auto-Discovery Classes
Auto-discovery rules for a resource type are defined in the XML descriptor of the plug-in that manages the
type.
Auto-Discovery Class Hierarchy
VMware vRealize Operations Manager auto-discovery class is as follows.
org.hyperic.hq.product.GenericPlugin
org.hyperic.hq.product.ServerDetector
org.hyperic.hq.product.PlatformServiceDetector
org.hyperic.hq.product.DaemonDetector
org.hyperic.hq.product.MxServerDetector
org.hyperic.hq.product.SunMxServerDetector
org.hyperic.hq.product.SNMPDetector
VMware, Inc.
39