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
vRealize Operations Manager uses the remote API (http://www.jcp.org/en/jsr/detail?id=160) specified by
JSR-160 to manage products that support JMX 1.2/JSR-160, including the ones listed above. For JMX-enabled
servers that do not support JSR-160, vRealize Operations Manager uses vendor-specific connectors.
vRealize Operations Manager JMX support classes enable auto-discovery of MBean servers and MBeans,
collection of MBean attributes, and execution of MBean operations.
To enable monitoring, you must configure the JMX-enabled target to accept remote connections. In many
cases, the remote connector is enabled by default, otherwise, you must configure it for remote access.
JMX Product Product Information Link
J2SE 1.5 http://download.oracle.com/javase/1.5.0/docs/api/javax/management/remote/package-summary.html
MX4J http://mx4j.sourceforge.net/docs/ch03.html
ActiveMQ http://activemq.apache.org/jmx.html
JOnAS http://jonas.objectweb.org/current/doc/doc-en/integrated/howto/JSR160_support.html#JSR160_support
ServiceMix http://servicemix.apache.org/jmx-console.html
Auto-Discovery of JMX Resources
vRealize Operations Manager discovers a JMX application or server using a Sigar process query.
MBeans are discovered by querying the MBean server for MBeans whose names match those configured in
the plug-in descriptor. Sigar is used to discover servers. Services are discovered via MBean Server queries
(MBeanServer.queryMBeans()).
Measurement
MxMeasurement uses Sigar queries for process metrics. Metrics that map to
MBean attributes are obtained via an MBean query
(MBeanServer.getAttribute()).
NOTE Sun JVM 1.5 type applies to any of the above and any other JMX-enabled server running under a Sun
1.5 JVM but has its own set of metrics and control actions. Unlike the other server types, Sun JVM 1.5
instances are not auto-discovered.
Configuration Properties for JMX Monitoring
vRealize Operations Manager JMX support classes require the JMX URL and JMX user credentials so that
they can connect to a remote MBean server.
The required credentials are as follows:
jmx.url The JMX service URL. See
http://download.oracle.com/javase/1.5.0/docs/api/javax/management/remote/JMXServiceURL.html
jmx.username Username, if authentication is required
jmx.password Password, if authentication is required
Configuration options that a user can configure are defined in a <config> element in a plug-in descriptor.
The Plug-in Development Kit includes a global configuration schema named jmx that contains the required
configuration option definitions, as follows.
<config>
<option name="jmx.url" description="JMX URL to MBeanServer"
default="service:jmx:rmi:///jndi/rmi://localhost:6969/jmxrmi"/>
<option name="jmx.username" description="JMX username" optional="true" default=""/>
<option name="jmx.password" description="JMX password" optional="true" default="" type="secret"/>
Chapter 1 Introduction to Plug-in Development
VMware, Inc. 21