HQ Architecture
Hyperic HQ Architecture
Hyperic HQ is a distributed-infrastructure management system. The major pieces of the HQ system architecture are shown below.
Diagram of the HQ Server
Diagram of the HQ Agent
Learn more about each component of the HQ architecture:
If you have any comments or suggestions for this help page, please submit them at the bottom of the page by clicking Add Comment.
Hyperic HQ Repository
The data repository forms the bedrock of the HQ system. It stores all HQ-related data in a relational schema and is responsible for ensuring data integrity and coordinating concurrent access to data. Access to the data repository is regulated by the Hyperic HQ Server.
Hyperic HQ Server
As HQ's central nervous system, the HQ Server coordinates all system functions, including:
- Processing incoming monitoring data
- Detecting alert conditions and sending out alerts
- Managing inventory, including merging auto-discovery information into current inventory
- Enforcing security
- Maintaining HQ operational schedules (for control actions and auto-discovery scans)
- Processing user-driven actions initiated via the HQ GUI or command line interface
In large environments, the HQ Server can be clustered to enhance fault tolerance and to share the overall system load across multiple machines.
Hyperic HQ Agent
Acting as the sensory facilities of the HQ system, Agents are deployed throughout the network infrastructure to provide points-of-presence for discovering inventory, gathering data, controlling software, and other "in the trenches" tasks.
The HQ Shell's Agent installer makes quick work of installing and managing all your HQ Agents – without ever having to visit each managed machine.
Hyperic HQ GUI
HQ's graphical user interface makes it easy to manage your infrastructure from anywhere. The GUI interacts with the HQ Server and exposes Server functionality through a rich, user-friendly web-based interface. The GUI is implemented as a portal, which makes it easy to customize the content and look-and-feel for each user.
Hyperic HQ Shell
To complement the GUI, the HQ shell provides a text-based interface to the HQ Server. Almost everything that can be done through the HQ GUI can also be done using the HQ shell. The HQ shell can be driven programmatically, giving power users the ability to automate HQ activities by writing HQ-shell scripts.
Learn more about HQ's command-line interface.
Hyperic HQ Product Plugins
A plugin-oriented design allows HQ to support a wide variety of products and platforms. Each plugin allows HQ to interface with a specific product.
Plugins are packaged as a single .jar file, for ease of deployment. Each plugin has a declarative component and a functional component. The declarative component is deployed within the HQ Server to describe how the product's organizational concepts fit into the HQ inventory model, and what kinds of metrics and control actions are supported. The functional component is deployed within the Agent and is responsible for the actual product-specific work of auto-discovery, metric collection, and resource control.
Learn more about how to develop plugins.