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
dcs-tools-pdk.jar Command Syntax
To run a plug-in from the command line, it is important that you understand the syntax and the functions of
each of the methods.
The command for running a plug-in from the command line is structured as follows:
java -jar AgentVersion/bundles/AgentBundle/pdk/lib/dcs-tools-pdk-VERSION.jar -m Method -a
MethodAction -p PluginName -t ResourceType -Doption=value
You can use the following information to guide you in your choices.
-m Method
The -m Method command specifies the method to run.
The Method can be one of the following:
lifecycle
For details and functionality, see “lifecycle Method,” on page 30.
discover
For details and functionality, see “discover Method,” on page 31.
metric
For details and functionality, see “metric Method,” on page 31.
control
For details and functionality, see GUID-8713429D-A37D-42B9-BEE3-67B8EBDAA6C0#GUID-8713429D-
A37D-42B9-BEE3-67B8EBDAA6C0.
track
For details and functionality, see “track Method,” on page 35.
generate
For details and functionality, see “generate Method,” on page 35.
-p PluginName
The -p PluginName command is the product portion of the plug-in name, without the -plugin.jar or -
plugin.xml portion. For example, to run jboss-plugin.jar, you specify -p jboss.
If you use a generated properties file to supply resource properties, you do not have to specify the plug-in to
run on the command line, because the resource properties file identifies the plug-in.
The command is required for the following methods.
n
lifecycle
n
metric
n
control
n
track
The command is optional for the following methods.
n
discover
n
generate
The command is not supported for livedata.
-t ResourceType
The -t ResourceType command specifies the name of a resource type managed by the plug-in you are
running.
If the name includes spaces, you must enclose it in quotes, for example, "JBoss 4.2".
If you use a generated properties file to supply resource properties, you do not have to specify the resource
type on the command line, because the resource properties file identifies the resource type name for the
resource.
Endpoint Operations Management Agent Plug-in Development Kit
26 VMware, Inc.