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
n
lifecycle Method on page 30
You use the lifecycle method to load a plug-in and report any errors found in the plug-in.
n
discover Method on page 31
You use the discover method to return key attributes for each discovered object to the terminal
window or to a properties file.
n
metric Method on page 31
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.
n
track Method on page 35
You use the track method to track log or configuration events.
n
generate Method on page 35
You use the generate method to generate documentation from the plug-in descriptor.
lifecycle Method
You use the lifecycle method to load a plug-in and report any errors found in the plug-in.
Syntax
The syntax for the lifecycle method is as follows.
$ java -jar bundles/agent-VERSION/pdk/lib/dcs-tools-pdk-VERSION.jar -p PluginName -m lifecycle -
Dplugins.include=PluginName
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.
-Dplugins.include=PluginName
Ensures that only the specified plug-in is loaded. When this is not included, all
plug-ins are loaded.
Example: Results of Running the lifecycle Method on a Plug-in Without Errors
This command runs the lifecycle method for the jboss plug-in. In the example, no errors are found.
$ java -jar bundles/agent-VERSION/pdk/lib/dcs-tools-pdk-VERSION.jar -m lifecycle -p jboss -
Dplugins.include=jboss
Example: Results of Running the lifecycle Method on a Plug-in Containing Errors
This command runs the lifecycle method for the websphere plug-in. In the example, errors are found.
$ java -jar bundles/agent-VERSION/pdk/lib/dcs-tools-pdk-VERSION.jar -m lifecycle -p websphere -
Dplugins.include=websphere
WARN [main] [MetricsTag] MsSQL 2000 include not found: mssql-cache
WARN [main] [MetricsTag] WebSphere 6.1 include not found: WebSphere 6.0
WARN [main] [MetricsTag] WebSphere 6.1 Application include not found: WebSphere 6.0 Application
WARN [main] [MetricsTag] WebSphere 6.1 EJB include not found: WebSphere 6.0 EJB
WARN [main] [MetricsTag] WebSphere 6.1 Webapp include not found: WebSphere 6.0 Webapp
WARN [main] [MetricsTag] WebSphere 6.1 Connection Pool include not found: WebSphere 6.0
Connection Pool
WARN [main] [MetricsTag] WebSphere 6.1 Thread Pool include not found: WebSphere 6.0 Thread Pool
WARN [main] [MetricsTag] WebSphere Admin 6.1 include not found: WebSphere Admin 6.0
Endpoint Operations Management Agent Plug-in Development Kit
30 VMware, Inc.