6.1

Table Of Contents
The server manages metadata, including:
n
Platform, server, and service resource types and how the plug-in's targeted resources map to the
inventory model.
n
The configuration schema for each resource.
Technical Overview
vRealize Operations Manager plug-ins are self-contained .jar or .xml files that are deployed on both the
server and every agent that you want to run the plug-in. Every plug-in contains, at a minimum, an XML
descriptor, which is either a standalone .xml file or embedded in the .jar file.
Plug-in Implementations
Consider measurement, control, and so on, as types of plug-ins. These types of plug-ins can be created for
any type of object.
You write different implementations of plug-in types, depending on the type of object and how it
communicates and presents its data. The different implementations are:
n
Script
n
JMX
n
SQL
n
SNMP
Using Support Classes to Simplify a Plug-in
vRealize Operations Manager includes a number of support classes that you can invoke in your own plug-
ins to abstract and simplify its construction.
vRealize Operations Manager provides the following support classes:
Table 11. vRealize Operations Manager Support Classes
Category Support Classes When to Invoke the Support Class
Scripting qmail, Sendmail, Sybase
SNMP Squid, Cisco IOS
JMX JBoss, WLS, WAS, ActiveMQ, Jetty
JDBC MySQL, PostgreSQL, Oracle To gather database system tables
metrics
Win-Perf Counters IIS, Exchange, DS, .NET To gather metrics from an application
that surfaces perf counters
SIGAR System, Process, Netstat To communicate with an operating
system. SIGAR is HQ's proprietary OS-
independent API
Net Protocols HTTP, FTP, SMTP, and so on To communicate with platform
services that HQ already has built-in,
but you might want to gather
additional metrics from it
Vendor Citrix, DB2, VMware
Endpoint Operations Management Agent Plug-in Development Kit
8 VMware, Inc.