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
discover Method
You use the discover method to return key attributes for each discovered object to the terminal window or
to a properties file.
The method can be run for one or all plug-ins. The returned attributes include the values of the resource's
configuration options. If you save discovery results to a file, you can use that file to supply the required
resource configuration data when you run another method that requires the resource's configuration data.
Syntax
The syntax for the discover method is as follows.
{{java -jar bundles/agent-VERSION/pdk/lib/dcs-tools-pdk-VERSION.jar -m discover -p PluginName -a
properties
Argument Description
-p PluginName Identifies the plug-in to run by the product portion of the plug-in name. For example, to run jboss-
plugin.jar, you specify -p jboss. If you do not specify the plug-in name, discovery is performed
for all the plug-ins in the agent's plugin directory.
-a properties
Writes the discovery results to files. If you do not use this option, the results are returned only to the
terminal window.
You can use any of the following discovery method options.
Command Purpose Comments
-m discover
To run discovery for all plug-ins. Results are returned to the terminal
window.
-m discover -p jboss
To run discovery for one plug-in, (in this
case, JBoss).
Results are returned to the terminal
window.
-m discover -p jboss -a
properties
To run discovery for a plug-in (JBoss) and
save results to files.
Results are written to files, and to the
terminal window.
-m discover -a properties
To run discovery for all plug-ins and save
results to files
Results are written to files, and to the
terminal window.
metric Method
You use the metric method to fetch the metric template and the metric value for each metric for objects that
are managed by the plug-in.
You can also use the method for the following:
n
Metrics that are collected by default
n
Metrics belonging to a specific metric category
n
Metrics that are indicator metrics
n
To return only the metric template, without the metric values, for the metrics
n
Fetch metrics repeatedly for a specified number of times, and return the time that it took to perform the
fetch action for each metric.
Chapter 1 Introduction to Plug-in Development
VMware, Inc. 31