- What's New in Hyperic HQ 4.6
- Documentation Packaging and Publishing
- Product Plugin Management and Deployment
- Plugin Manager
- Server-Agent Plugin Synchronization
- New Hyperic Server Property to Enable and Disable SAPS
- Required Plugin Descriptor Element to Support SAPS
- Security Changes
- iPad and iPhone Support
- Updated Plugins
- HQApi Updates
- Resolved Issues in Hyperic HQ 4.6
- Known Issues in Hyperic HQ 4.6
The Hyperic HQ 4.6 features described below are also in vFabric Hyperic 4.6.
The complete vFabric Hyperic documentation set is built in to Hyperic 4.6, and can be accessed by clicking help on any page in the Hyperic user interface. The Hyperic Server option to connect to the Hyperic support site (http://support.hyperic.com) for help content is removed from Hyperic 4.6. (In previous Hyperic releases, only help pages for the user interface were packaged in the product, and there was a configuration option on the HQ Server Settings page to toggle between product-internal help and help served from http://support.hyperic.com.)
Upon G.A. of VMware vFabric Platform 5.0, vFabric Hyperic 4.6 documentation, including downloadable PDFs, will also be available at http://pubs.vmware.com/vfabric5/topic/com.vmware.vfabric.hyperic.4.6/vFabric_Hyperic_4.6.html, where Hyperic documentation will be published henceforth. Documentation for vFabric 4.6 and later will not be maintained on the Hyperic support site.
Hyperic 4.6 provides new features that ease the process of deploying and managing product plugins. These features include a user interface for managing product plugins, and new Hyperic Server and Hyperic Agent behaviors for ensuring consistent plugin deployment across a Hyperic environment.
The new plugin management features are briefly described in the paragraphs below. For more detailed information, see "Plugin Deployment and Management" in vFabric Hyperic Administration at http://pubs.vmware.com/vfabric5/topic/com.vmware.vfabric.hyperic.4.6/vFabric_Hyperic_Administration.html.
Plugin Manager is a new user interface that enables you to deploy and manage plugins across a Hyperic deployment from the Hyperic user interface. You can use Plugin Manager to deploy and remove plugins on the Hyperic Server and all agents reporting to the server.
The new Server-Agent Plugin Synchronization (SAPS) feature ensures that product plugins are consistently deployed across a Hyperic deployment. SAPS is enabled by new behaviors on the Hyperic Server and Hyperic Agent. When a Hyperic 4.6 Agent starts up, it sends a plugin status report to the Hyperic Server. If an agent's deployed plugins do not exactly match those deployed on the Hyperic server, the server updates the agent's plugins appropriately. Similarly, each time the Hyperic Server is restarted, it compares the product plugins it deploys to most recent plugin status reported by each agent — if an agent's deployed plugins do not exactly match those deployed on the Hyperic server, the server updates the agent's plugins appropriately. SAPS is enabled by default; it can be disabled using the new server.pluginsync.enable server property, described in the next section.
Hyperic 4.6 provides a new Hyperic Server property, server.pluginsync.enable, which you can use to disable the SAPS feature described in the previous section. To disable SAPS, add server.pluginsync.enable=false to ServerHome/conf/hq-server.conf, and restart the Hyperic Server.
As of Hyperic 4.6, all product plugins must have a version. The version of a plugin must be specified in a <property> element in the root <plugin> element in the XML descriptor for a product plugin. For more information, see vFabric Hyperic Product Plug-in Development at http://pubs.vmware.com/vfabric5/topic/com.vmware.vfabric.hyperic.4.6/vFabric_Hyperic_Product_Plug-in_Development.html.
The paragraphs below briefly summaries new and changed security features in Hyperic 4.6. For more detailed information, see "Hyperic Security Features and Recommendations" in vFabric Hyperic Installation and Configuration at http://pubs.vmware.com/vfabric5/topic/com.vmware.vfabric.hyperic.4.6/vFabric_Hyperic_Installation_and_Configuration.html.
If you use SSL for agent-to-server communication, you can use trusted SSL certificates from a certificate authority, or a self-signed certificate generated by Hyperic. Hyperic recommends you configure user-managed keystores for the Hyperic 4.6 Server and Hyperic 4.6 Agents. Using unverified certificate reduces the security of the Hyperic environment.
For a more secure environment, run only Hyperic 4.6 Agents with a Hyperic 4.6 Server.
In Hyperic 4.6, for a -full installation, the installer prompts for whether you want to configure Hyperic Server for a user-managed keystore.
If you respond "yes", the installer prompts you to supply the path to the keystore and its password.
If you respond "no", the installer creates a keystore for the server, with a self-signed certificate.
For an -upgrade installation, the installer does not prompt for whether you want to configure Hyperic Server for a user-managed keystore. For compatibility with pre-4.6 Hyperic Agents, the installer automatically creates a keystore and self-signed certificate for the server.
The properties that configure location and password for a user-managed keystore on the server are server.keystore.path and server.keystore.password in ServerHome/conf/hq-server.conf
By default, a Hyperic 4.6 Agent creates its own keystore with a self-signed certificate the first time it starts up. To configure the agent for a user-managed keystore, you must specify the path and password of that keystore in the agent.properties file.
The properties that configure the location and password for a user-managed keystore on the agent are agent.keystore.path and agent.keystore.password in AgentHome/conf/agent.properties
If the server presents an unverified certificate to a 4.6 agent, the agent warns that the authenticity of the Hyperic Server host cannot be established. It prompts for confirmation that you want to connect and import that certificate.
Similarly, if a 4.6 agent presents an unverified certificate to the 4.6 server, the server issues a warning, and prompts for confirmation to continue.
Instructions for upgrading the Hyperic Server and all Hyperic Agents to 4.6 are provided on "Hyperic 4.6 Upgrade Processes and Options" in vFabric Hyperic Installation and Configuration at http://pubs.vmware.com/vfabric5/topic/com.vmware.vfabric.hyperic.4.6/vFabric_Hyperic_Installation_and_Configuration.html.
Note that if you use Hyperic Product plugins that communicate with managed servers over SSL, it may be necessary to import the managed server's SSL certificate into the Hyperic Agent's keystore. For more information, about SSL and Hyperic product plugins, see "Hyperic Security Features and Recommendations" in vFabric Hyperic Installation and Configuration at http://pubs.vmware.com/vfabric5/topic/com.vmware.vfabric.hyperic.4.6/vFabric_Hyperic_Installation_and_Configuration.html.
You can access the Hyperic 4.6 user interface from iPads and iPhones.
All Hyperic plugins XML descriptors are updated to define the version of the plugin as a <property> element named "version".
In addition, the following Hyperic plugins are updated with new functionality, or to support more recent versions of the managed product:
- GemFire. Updated to support the security updates described above in Security Changes.
- RabbitMQ. No longer requires access the erlang.cookie file — the plugin now uses the rabbitmq-management plugin. The configuration process has changed, and additional metrics are available. For more information see "RabbitMQ" in vFabric Hyperic Resource Configuration and Metrics at http://pubs.vmware.com/vfabric5/topic/com.vmware.vfabric.hyperic.4.6/vFabric_Hyperic_Resource_Configuration_and_Metrics.html. In addition, this plugin has been updated to support the security updates described above in Security Changes.
- vSphere. Updated to support the security updates described above in Security Changes.
- tc Server. Support for tc Server 7.0 added.
- Jboss. Support for Jboss 5.1 and 6.0 added.
- PostgreSQL. Support for PostgreSQL 9.0 added.
- WebSphere. Improvements to enable better troubleshooting of auto-discovery issues.
- WebLogic Server Plugin. Enhanced to enable discovery of node managers and managed servers in a WebLogic domain without accessing the Administration Server for the domain. In previous releases, it was necessary to discover the Administration Server for a domain, and then configure that resource with WebLogic Server credentials, in order to discover the node manager and managed servers in the domain.
Hyperic 4.6 includes HQApi 5.0. Changes include:
- client.properties — Supports encrypted passwords, and can be stored in either ~/.hq or hqapi1-client-n.n.n/conf. In previous versions, the APIs look for server connection properties in ~/.hq/client.properties; to use a connection properties in a different location you had to supply the path to the client.properties on the command line, using the --properties command qualifier. (Supplying the properties file location on the command line is still supported.) For more information about specifying connection properties in a file, see "HQApi Command-Line Tools" in vFabric Hyperic Web Services API at http://pubs.vmware.com/vfabric5/topic/com.vmware.vfabric.hyperic.4.6/vFabric_Hyperic_Web_Services_API.html.
- groovyshell — New API that allows you to run Groovy scripts from the command shell.
- maintenance — Updated to enable maintenance downtime to be scheduled for individual resources. In previous releases, maintenance could only be scheduled for a group of resources.
|Issues Fixed for Hyperic HQ 220.127.116.11 (1 issues)|
|HHQ-5223||Closed||vmware, iis, ntds, exchange, mssql plugins have incorrect metric names|
|Known Issue with Firefox 3.x|
Some pages in the Hyperic user interface intermittently appear blank in Firefox 3.x. The user interface was tested with Firefox 3.x and 4.x. The problem was detected in 3.x. For more information, see https://jira.hyperic.com/browse/HHQ-4434.
|Known Issues for Hyperic HQ 18.104.22.168 (1 issues)|
|HHQ-5458||Reopened||Unable to see more than 15 Groups when trying to add additional Compatible Groups to an existing Mixed Group|