Hyperic recommends to use the Plugin Manager of its Web User Interface to install new plugins in the Hyperic Server and Agent(s) version 4.6. To do so, please follow the standard VMware Hyperic documentation for the Plugin Manager: https://support.hyperic.com/display/DOCS46/Plugin+Deployment+and+Management.
In previous versions of Hyperic, only manual deploy of plugins is available. In this case, it is recommended to use the alternative approach described below.
Copy the Hyperic plugins to these folders:
The complete information about deploying Hyperic plugins is at http://support.hyperic.com/display/EVO/Deploy+Plugin.
Once deployed, the new plugins are added to the Auto-Discovery list and can now be added to the Inventory of monitored Resources. For more information, see the section below or go to Hyperic documentation: http://support.hyperic.com.
Tomcat and Karaf servers must be running to enable Hyperic to discover them.
Start the Hyperic server, if it was not running.
Start the Hyperic agent, if it was not running. Otherwise, restart it.
Information on how to start/stop/restart Hyperic agent and Hyperic server is in the Hyperic documentation http://support.hyperic.com.
Open your browser and log in to Hyperic server (default
http://localhost:7080/). You will see new discovered servers in the Auto-Discovery.
Sometimes servers are not detected correctly. In this case you need to restart Hyperic HQ Agent. From the
<HypericAgent>/bindirectory, restart agent with the following command:
hq-agent.bat restart (on Windows)
sh hq-agent.sh restart (on Linux)
Click the Add to Inventory button.
Click the Resources tab.
Find and select Apache Camel(CXF) [Tomcat]([Karaf]) 2.x from the list of servers, depending on which combination you wish to monitor. For example, you may wish to monitor Camel/Tomcat and CXF/Tomcat.
Select a service group.
For Camel you should see the group of the routes specified by context and name.
For CXF you should see the group of the services specified by port and operation.
Hyperic will collect the metrics for these groups, and the initial results will be displayed.
These will subsequently updated as the examples are run.