vCenter Operations Manager and vFabric Hyperic Integration

As detailed in the previous section, Hyperic is used as a source of data for vCenter Operations Manager from individual, key vCloud infrastructure management servers. This proxy functions as a result of the vCenter Operations Manager Hyperic adapter that is installed and enables the required process and service information to be presented to vCenter Operations Manager.

As shown in the figure, vCenter Operations Manager Enterprise supports the Hyperic Adapter, which enables the exchange of information between vCenter Operations Manager Enterprise and Hyperic HQ data. The adapter provides the following functionality:

Transforms the collected data into the format vCenter Operations Enterprise is designed to consume.

Passes the data to the vCenter Operations Enterprise collector for final processing.

In addition to the standard adapter functions, the adapter supports manual and auto discovery, and the ability to create relationships based on the associations found in Hyperic HQ.

The Hyperic adapter’s data source is the Hyperic HQ database. The adapter uses standard JDBC access to the database for running SQL queries. The adapter uses the vCenter Operations API to communicate and deliver data to vCenter Operations.

The vCenter Operations Manager Hyperic adapter can collect data from different resources and creates resource kinds dynamically according to platform types and server types in Hyperic. Resources in vCenter Operations represent Hyperic platforms and servers.

Resources in Hyperic are one of the following kinds.

A platform, which is either an operating system platform such as Linux, Solaris, Windows 32-bit, or UNIX, or a virtual and network platform such as Cisco IOS, VMware vFabric GemFire® Distributed System, NetApp Filer, vSphere Host, or a vSphere virtual machine.

A server, which is a software product that runs on a platform such as Tomcat, JBoss, Exchange, SQL, or Oracle.

Services and platform services, which are software components that run on either a server or a platform. Server services can be either internal server components such as database tables or .NET applications or they can be a deployed item such as CustomerEntityEJB. Examples of platform services include DHCP, DNS, and CPU and network interfaces.

The Hyperic adapter can also collect data for Hyperic services. Service metrics are stored under a specific instance and group and the service name is used as the instance name.

Sources map to vCenter Operations resources using resource names in vCenter Operations to match the names from the eam_resource table in the Hyperic HQ database. All available types of resources in the source system can be collected.

The adapter can import relationships between Hyperic platforms and servers. Relationships are based on the platform_id column value in the eam_server table. Relationships are imported during manual discovery only.

The adapter can collect all metrics for Hyperic platforms, servers, and services. Use a single query for each adapter instance to retrieve the metric data for children instances. Metrics are collected using a query to the HQ_METRIC_DATA tables and viewed using a time filter.

Availability metrics are collected from the HQ_AVAIL_DATA_RLE table. The system current time is used as the timestamp of the collected Availability metric.

Collection interval used is assigned to adapter instance resource and attribute package.

There are no events collected from Hyperic HQ.

The adapter supports Hyperic HQ versions 3.x and 4.0.

The following table lists the default vCenter Operations Enterprise port connections for supported databases. You must specify the port number when you configure the adapter instance resource.

The following table lists the default vCenter Operations Enterprise URLs used to connect to data sources. The Hyperic adapter requires a standard JDBC connection URL.

Database	URL
MySQL	jdbc:mysql://<db_host>:<db_port>/<hqdb_name>
Oracle	jdbc:oracle://<db_host>:<db_port>/<hqdb_name>

Database	Port Number
MySQL	3306 TCP
Oracle	1521 TCP