- HQ 4.2 Features
- Alerting Changes
- Global Alert Notification Shutoff
- Notification Filtering Removed
- Global Alert Setting Changes are Immediate and Persistent
- HQ API Changes
- Changed Breadcrumb Behavior on Resource Pages
- HQ 4.2 Packaging Changes
- New Configuration Requirement for Running HQ Database on Oracle
- JDBC Drivers Removed from Database Plugins
- MQ Library Removed from WebSphere Plugin
- No Platform-Specific HQ Server Package for Solaris SPARC
- Issues Fixed in HQ 4.2
- Known Issues in HQ 4.2
HQ 4.2 provides enhanced capabilities for controlling the volume of alert notifications.
In HQ 4.2 you can globally disable all alert notifications immediately, including notifications for alerts that have an escalation in progress. Disabling alert notifications is different from disabling alerts. When you globally disable alerts, HQ will continue to send out notifications for alerts that are currently in escalation until the escalation ends.
The Alert Notifications control is in the Global Alert Properties section of the "HQ Server Settings" page. The change takes effect immediately without need to restart the HQ Server. The setting will persist through HQ Server restarts. For more information see Key Facts about HQ Alerting and Controlling Alert and Notification Volume.
The ability to filter notification for a specific alert definition, provided in previous versions of HQ, is removed in HQ 4.2, replaced by the Global Alert Notification Shutoff feature described above.
In HQ 4.2, changes to any of the configuration options in the Global Alert Properties section of the "HQ Server Settings" page take effect immediately, without HQ Server restart, and persist after HQ Server restart. For more information, see associated help.
HQ Web services API has multiple fixes and enhancements. Notably, the resource API now has full XML sync support is added. The APIs sync option now supports resource creation. For documentation, see Web Services API.
The breadcrumbs on resource pages in the HQ user interface have been revised to ease the process of navigating among related resources and backtracking to previously viewed resources.
Prior to HQ 4.2, the breadcrumbs on a resource page reflected the inventory level and resource type of the currently selected resource, in this form:
InventoryLevel > ResourceType > ResourceName
For example, the breadcrumbs when you select a Linux platform with FQDN "West10.demo.net" would be:
Platforms > Linux > West10.demo.net
The Platforms link opens the Browse page for all platforms; the Linux link opens the Browse page for platforms whose resource type is "Linux".
In HQ 4.2 the breadcrumbs on a resource page reflect where the resource fits in a resource hierarchy. Breadcrumbs correspond to steps you took (resources you selected) to navigate down a resource hierarchy. For example, if you navigate to a service, starting at the top of the hosting hierarchy - by browsing to a platform and drilling down - the breadcrumbs are links to the platform and server you visited along the way:
Browse > PlatformName > ServerName > ServiceName
When you navigate to a resource that is outside the currently resource hierarchy, the breadcrumb trail is purged. For example, if you drill down to a service, as described above, and then navigate to an application that the service belongs to (from the service's Inventory page) the breadcrumbs are purged and the application is your new starting point. Note that, when you jump outside the current hosting hierarchy, a link to the previously viewed resource appears - so you can get back to it easily, if you wish. For example
Browse > ApplicationName
Return to ServiceName
Clicking Browse in the breadcrumb trail opens the Browse page for the inventory level (platform, server, or service) most recently browsed.
The HQ Server in Hyperic HQ no longer includes the Oracle JDBC driver. If you are installing or upgrading to Hyperic HQ 4.2 and use Oracle for the HQ database, perform these steps before installing HQ Server.
To obtain the driver:
- Go to http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
- Select the link "Oracle Database 10g Release 2 (10.2.0.4), (10.2.0.3), (10.2.0.2), (10.2.0.1.0) drivers"
- On the page that appears accept the licensing agreement.
- Download the ojdbc14.jar file.
After obtaining the driver:
- Copy ojdbc14.jar to hyperic-hq-installer/installer-4.2.n/lib.
- Proceed with the HQ installation process.
The HQ plugins for MSSQL, Oracle, Informix, DB2, and Sybase no longer include the database vendor's JDBC plugin. After installing or upgrading to Hyperic HQ 4.2 you must download and install the vendor-provided JDBC drivers for these plugins to work.
Note: The database plugins in HQ Enterprise 4.2 still include the JDBC drivers.
The HQ plugin for WebSphere no longer includes the MQ library. After installing or upgrading to Hyperic HQ you must download and install the MQ library for the MQ plugin to work.
HQ Enterprise 4.2 still includes the MQ library.
|Note for Solaris Sparc Environment|
As of HQ 4.2 there is no platform-specific HQ Server package for Solaris SPARC. Install a no-JRE HQ Server package in Solaris SPARC environments. For information about how to ensure that HQ Server can determine what JRE to use, see HQ Components and JRE Location.
A platform-specific HQ Agent package with a bundled JRE is available for SPARC Solaris in a tarball.
Note: You must use GNU Tar to unpack HQ tarballs.