public class GbjHypericPluginGenerator extends Object
The VMware Hyperic system monitoring tool uses specialized "plugins" to be able to recognize and manipulate its various servers and services. These plugins are either a single XML file, or a jar file that contains the XML file plus various code files that support the functionality defined in the XML file. GbjHypericPluginGenerator generates a compatible XML file that works with a specific stone, monitored by a an instance of GbxJmxCacheStatsMonitor running on a specific JMX port.
Prior to running GbjHypericPluginGenerator, make sure that $GEMSTONE is set in the environment.
To run GbjHypericPluginGenerator, execute:
java -d64 com.gemstone.gbjstats.GbjHypericPluginGenerator <stonename> <jmxport>
Where <stonename> is the name of the associated stone and <jmxport> is the JMX port being used by the GbjJmxCacheStatMonitor application monitoring this stone.
Execution of this code produces an output file with the name:
gs_<version>_<stonename>_<jmxport>-plugin.xml.
Where <stonename> and <jmxport> are as above and <version> is the version of the Gemstone system associated with $GEMSTONE.
You will then need to copy this file to the appropriate $HYPERIC directories for the agent(s) and server(s) that will need to monitor and manage this GemStone environment. Refer to your Hyperic documentation for details.
Note that different plugins will need to be generated for each stone (configured with the appropriate $GEMSTONE so that the version information is correct). Also, each separate stone will require a different GbjJmxCacheStatsMonitor application, each running on a different JMX port. For distributed GemStone environments, there will also need to be a separate GbjJmxCacheStatsMonitor for each remote shared page cache. GbjJmxCacheStatsMonitors on remote caches should all use the same JMX port as is assigned to the stone GbjJmxCacheStatsMonitor.