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
You can use the following table to determine the elements that you can define for each object that a plug-in
manages.
Element Description and Usage
Configurable resource
data
n
<config>
n
<option>
<config> is a mandatory container element for <option> elements. A named <config>
element is a reusable building block that can be included by reference in other <config>
elements. This is useful when you define a group of options that apply to multiple managed
objects in the object plug-in. You can designate a <config> element as global, in which case
<config> elements in other plug-in descriptors can also reference it.
<option> specifies a resource attribute with a value that must be supplied by the user. It
can be supplied in the descriptor or by a plug-in class, but it must be editable. You can
define the permissible values for a selector list, whether they are optional or mandatory, and
so on.
Non-configurable
resource data
n
<properties>
n
<property>
<properties> is a container element for one or more <property> elements.
<property> specifies a non-configurable resource attribute. Its value might be discovered
(for example RAM, or CPU speed), returned by a plug-in class, or defined in the descriptor.
Resource data defined as a <property> cannot be entered or edited in the user interface.
Management functions for
a resource type
n
<plugin>
n
<actions>
<plugin> specifies a management function (auto-discovery, measurement, control, log
tracking, and so on) for a resource type, and the Java class that performs that function.
Each management function for a resource type is specified in a separate <plugin> element.
<actions> specifies a list of control operations, supported by the resource type, that the
plugin can perform. The <actions> element is required as a sibling for a control-type
<plugin> element.
Metrics for a resource
type
n
<metrics>
n
<metric>
<metrics> is container for one or more <metric> elements. A named <metrics> element
in the root of the plug-in is a reusable building block that can be included by reference in
<metrics> elements in multiple resource elements within the descriptor. This is useful
when you define a set of metrics that apply to multiple object types that are managed by the
plug-in.<metric> specifies a measurement that the plug-in obtains for an object type. The
attributes in the <metric> element define the type of metric (availability, throughput,
utilization), units of measure, whether the metric is an indicator, and so on.
Metrics for use within the
descriptor
n
filter
The filter element defines a name and value pair variable that you can use in the
descriptor. filter is meaningful only within the descriptor.
The filter element make a descriptor easier to write, understand, debug, and maintain. It
makes it easier to define the template for each metric.
Endpoint Operations Management Agent Plug-in Development Kit
50 VMware, Inc.