VMware vCenter Operations Manager - 1.0 User Manual
VMware vCenter Operations Manager
Adapter Guide
vCenter Operations Manager 1.0
This document supports the version of each product listed and
supports all subsequent versions until the document is replaced
by a new edition. To check for more recent editions of this
document, see http://www.vmware.com/support/pubs.
EN-000930-02
VMware vCenter Operations Manager Adapter Guide
You can find the most up-to-date technical documentation on the VMware Web site at:
http://www.vmware.com/support/
The VMware Web site also provides the latest product updates.
If you have comments about this documentation, submit your feedback to:
docfeedback@vmware.com
Copyright © 2012 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual
property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks
and names mentioned herein may be trademarks of their respective companies.
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
2 VMware, Inc.
Contents
VMware vCenter Operations Manager Adapter Guide 5
Updated Information 7
Understanding Adapters 9
1
How Adapters Collect and Process Data 9
Types of Data that Adapters Collect 10
Adapter Architecture 11
Available Adapters 13
2
vCenter and VCM Adapters 13
vCenter Operations Manager Advanced Suite Adapters 13
vCenter Operations Manager Enterprise Suite Adapters 14
Product Adapters 14
Generic Adapters 20
Field Adapters 21
Installing and Configuring Adapters 23
3
Install an Adapter in a Standalone Installation 23
Install an Adapter in a vApp Installation 24
Add an Adapter Instance 25
Modifying Adapter Configuration Files 25
Troubleshooting Adapters 27
4
General Troubleshooting Steps 27
View Collection Information 27
Viewing System Log Files 30
Index 33
VMware, Inc. 3
VMware vCenter Operations Manager Adapter Guide
4 VMware, Inc.
VMware vCenter Operations Manager Adapter Guide
The VMware vCenter Operations Manager Adapter Guide provides information about how
vCenter Operations Manager uses adapters to consume data from the enterprise. It also provides a summary
of the currently available adapters.
Intended Audience
This information is intended for anyone who wants to install and configure adapters for
vCenter Operations Manager.
VMware, Inc. 5
VMware vCenter Operations Manager Adapter Guide
6 VMware, Inc.
Updated Information
The VMware vCenter Operations Manager Adapter Guide is updated with each release of the product or when
necessary.
This table provides the update history of the VMware vCenter Operations Manager Adapter Guide.
Revision Description
EN-000930-02
EN-000930-01 Provided more detailed instructions in “Install an Adapter in a Standalone Installation,” on page 23 and
EN-000930-00 Initial release.
n
Changed the title to VMware vCenter Operations Manager Adapter Guide.
n
Added information about the 5.6 licensing model. See “vCenter Operations Manager Advanced Suite
Adapters,” on page 13 and “vCenter Operations Manager Enterprise Suite Adapters,” on page 14.
n
Removed information about the BMC PATROL adapter.
n
Added a description of the HP OpenView adapter. See “HP OpenView Adapter,” on page 15.
n
Added a description of the Keynote adapter. See “Keynote Adapter,” on page 16.
“Install an Adapter in a vApp Installation,” on page 24.
VMware, Inc. 7
VMware vCenter Operations Manager Adapter Guide
8 VMware, Inc.
Understanding Adapters 1
A key feature of vCenter Operations Manager is its ability to consume data from across the enterprise.
vCenter Operations Manager uses adapters to collect data from a variety of data sources, including specific
third-party products.
This chapter includes the following topics:
n
“How Adapters Collect and Process Data,” on page 9
n
“Types of Data that Adapters Collect,” on page 10
n
“Adapter Architecture,” on page 11
How Adapters Collect and Process Data
Adapters work with the vCenter Operations Manager Collector to collect and process data.
The Collector acts as a gateway between vCenter Operations Manager and its adapters. The adapters connect
to and collect data from data sources, transform the data into a format that vCenter Operations Manager can
consume, and pass the data to the Collector for final processing.
Depending on the data source and the adapter implementation, an adapter might collect data by making API
calls, using a command-line interface, or sending database queries. Some adapters collect data for each resource
independently and other adapters extract data for all resources based on a specified time range.
vCenter Operations Manager uses embedded adapters and external adapters. Embedded adapters are the most
common type of adapter implementation.
Embedded Adapters
An embedded adapter is a Java component that runs as a plug-in in the Collector. Embedded adapters actively
connect to a data source and pull values from it.
Advantages of embedded adapters include better maintainability, control, and visibility into the management
of the adapter and the data that it collects. Embedded adapters also use common functions, such as job
scheduling, that are already part of the Collector.
VMware, Inc.
9
VMware vCenter Operations Manager Adapter Guide
Embedded adapters create resources through manual or auto-discovery. A particular embedded adapter might
support one or both resource creation methods.
Manual discovery
Auto-discovery
You configure and manage embedded adapters in the user interface.
You send a request to the data source to return all available resources and select
the resources to add. This method is often referred to as discovering resources
or the discovery process.
The data collection process discovers new resources and creates the resources
for you. You do not need to manually add new resources.
External Adapters
External adapters push data from outside sources. The key advantage of an external adapter is flexibility in
how the adapter is created and deployed.
External adapters use vCenter Operations Manager OpenAPI to send information. OpenAPI has a simple form,
which accepts data through an HTTP request, and an advanced form, which uses Java RMI.
External adapters use auto-discovery to create resources. With auto-discovery, the data collection process
discovers new resources and creates the resources for you. You do not need to manually add new resources.
You configure and manage external adapters outside of the user interface.
Types of Data that Adapters Collect
Adapters typically collect metrics, resource relationships, and change events from an external data source. Not
all adapters can collect all types of data.
n
A metric is an instance of an attribute for a particular resource. For each metric,
vCenter Operations Manager collects and stores multiple instances over time. Each piece of data is called
a metric observation or value.
n
Resource relationships describe how resources are related to each other. For example, one resource might
be a child resource and another resource might be a parent resource.
n
A change event is any change to the environment, such as a system reboot.
vCenter Operations Manager stores metrics in the File System Database (FSDB). The standalone version of
vCenter Operations Manager can store change events in a Microsoft SQL or Oracle database. The vApp version
of vCenter Operations Manager stores change events in a PostgreSQL database.
10 VMware, Inc.
Adapter Architecture
vCenter Operations Manager
Analytics process
Collector
FSDB
Embedded
adapter
MS SQL, Oracle,
or PostgreSQL
database
External
adapter
Embedded
adapter
Data
source
Store data
Data
source
Pull data
Pull data
Push data
Message Broker
Data
source
Adapters work with certain vCenter Operations Manager components to collect, process, and store collected
data.
Figure 1-1. Adapter Architecture
Chapter 1 Understanding Adapters
Collector
Message Broker
Analytics process
Acts as a gateway between vCenter Operations Manager and its adapters.
Adapters pass collected data to the Collector for final processing.
In the standalone version of vCenter Operations Manager, the Collector is
installed in the primary server by default. In a vApp installation, the Collector
runs on the Analytics virtual machine. You can also install collectors on one or
more remote servers.
Passes metric information between vCenter Operations Manager components.
Receives data gathered from monitored resources, analyzes the data, and
creates statistical models to detect abnormal behavior.
vCenter Operations Manager stores metrics in the FSDB. The standalone
version can store change events in a Microsoft SQL or Oracle database. The
vApp version stores change events in a PostgreSQL database.
VMware, Inc. 11
Loading...