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
The command is required for the following methods.
n
metric
n
control
n
track
n
lifedata
The command is not supported for the following methods.
n
discover
n
generate
-a MethodAction
The MethodAction argument is either supported or required by the method that is called. For example, when
you run the track method, you specify whether you want to track log or configuration events by including
either -a log or -a config in the command line.
-DOption=Value
-DOption=Value sets a property value, where Option=Value specifies the property name and the value that
you assign it.
You must include a -DOption=Value in the command line for every property that you specify. In addition,
you must supply
n
The value of a resource property that is required by the method called.
You can reference a generated properties file, rather than supplying each resource property on the
command line.
n
The value of an agent or system property that manages agent behavior or plug-in execution.
Generating and Using Resource Properties Files
You can create resource properties files to use when you run plug-ins from the command line. Using a
resource properties file removes the need for you to specify individual property values multiple times in the
command line.
n
Resource Properties Files on page 28
Generally, plug-ins require the values of one or more resource properties to run. To simplify the
process of testing a plug-in, you can supply the properties in a file instead of the command line.
n
Names and Locations of Properties Files on page 28
The discover method's properties action writes configuration data for each discovered object in a
directory tree whose root directory, plug-in-properties, is in your current working directory.
n
Content of Properties Files on page 28
When you run the metric, control, or track methods on an object you must supply resource
configuration data, either explicitly on the command line, or using the properties file for the resource.
n
Inherited Resource Properties on page 29
Some resource properties might be inherited from a parent resource.
Chapter 1 Introduction to Plug-in Development
VMware, Inc. 27