Dashboard > Hyperic HQ 3.0 Documentation > Development Resources > Plugin Development Center
Hyperic HQ 3.0 Documentation Log In | Sign Up   View a printable version of the current page.
Plugin Development Center
Added by Ryan Morgan, last edited by Doug MacEachern on Mar 09, 2007  (view change)
Labels: 
(None)

Plugin Development Center

This section describes how to build HQ plugins, the interface between Hyperic HQ and the managed product.

Plugin Overview

Hyperic HQ plugins are self-contained .jar or .xml files which are deployed on the server-side and agent-side. Plugins are not aware of server vs. agent side deployment. However, the plugins are used differently by the server and agent. On the server-side, plugin metadata is extracted for the following:

  • Platform, Server and Service resource types
  • Config Schema for each resource type
  • Measurements
  • Optional help text to enable product-specific instrumentation
  • Control actions

On the agent-side, plugin implementations are invoked for the following:

  • Measurement
  • Control
  • Auto Inventory
  • Response Time

All of this information is described in the Plugin XML Descriptor, which is either a standalone .xml file or embedded in the .jar file.

There are 4 plugin implementations:

Plugin Deployment

Bundled plugins are deployed to both the server and agent in the following locations:

server-3.0.x/hq-engine/server/default/deploy/hq.ear/hq-plugins/
agent-3.0.x/pdk/plugins/

The server supports hot-deployment, plugins can be updated or added without restarting the server.
The agent does not support hot-deployment, it must be restarted when updating or adding a plugin.

Custom plugins can be added in the directories listed above or to a subdirectory 'hq-plugins' within the parent directory.
For example, if the server is installed at:

/usr/local/hyperic/server-3.0.x/

Add your custom plugins to:

/usr/local/hyperic/hq-plugins/
hq-plugins/ must exist prior to starting the server

Hot-deployment on the server side using the custom hq-plugins/ directory requires that this directory exists prior to starting the server.
So you will need to restart the server after the /usr/local/hyperic/hq-plugins/ directory is created.

If the agent is installed at:

/usr/local/hyperic/agent-3.0.x/

Add your custom plugins to:

/usr/local/hyperic/hq-plugins/

Similar on Windows, if the server is installed at:

C:\Program Files\Hyperic HQ\server-3.0.x\

Add your custom plugins to:

C:\Program Files\Hyperic HQ\hq-plugins\

If the agent is installed at:

C:\Program Files\Hyperic HQ\agent-3.0.x\

Add your custom plugins to:

C:\Program Files\Hyperic HQ\hq-plugins\

Using this approach, there is no need to copy custom plugins each time the server or agent is upgraded to a new version.

Invoking Plugins Outside the Server or Agent

When developing plugins, it's helpful to be able to invoke plugin methods directly for quick testing. The Invoking Plugins Standalone document describes this process.

Auto Inventory Plugin (Hyperic HQ 3.0 Documentation)
Control Plugin (Hyperic HQ 3.0 Documentation)
Invoking Plugins Standalone (Hyperic HQ 3.0 Documentation)
JBoss Custom MBean Plugin (Hyperic HQ 3.0 Documentation)
JMX Plugin (Hyperic HQ 3.0 Documentation)
Measurement Plugin (Hyperic HQ 3.0 Documentation)
Plugin XML Descriptor (Hyperic HQ 3.0 Documentation)
Process Monitor Plugin (Hyperic HQ 3.0 Documentation)
Product Plugin (Hyperic HQ 3.0 Documentation)
Protocol Monitor Plugin (Hyperic HQ 3.0 Documentation)
qmail Plugin (Hyperic HQ 3.0 Documentation)
Script Plugin (Hyperic HQ 3.0 Documentation)
SNMP Plugin (Hyperic HQ 3.0 Documentation)
SQL Query Plugin (Hyperic HQ 3.0 Documentation)
Windows Plugin (Hyperic HQ 3.0 Documentation)

SourceForge
Site running on a free Atlassian Confluence Open Source Project License granted to Hyperic HQ. Evaluate Confluence today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.4 Build:#809 Jun 12, 2007) - Bug/feature request - Contact Administrators
SourceForge.net Logo