To begin monitoring your environment with vRealize Operations Manager, you configure the VMware vSphere solution, which includes two adapters, one for vCenter Server and one for vCenter Server actions. When the solution adapters are configured, vRealize Operations Manager collects data from the target vCenter Server instances.

You use this version of the wizard to configure your initial vCenter Server instances. After you complete the wizard, where you configure the vCenter Adapter, the vCenter Python Actions Adapter, and set the monitoring goals for vRealize Operations Manager, other versions of the wizard appear, depending on the solution you are configuring.

During your initial configuration of vRealize Operations Manager, select Administration > Solutions in the left pane. On the Solutions tab, select VMware vSphere and click Configure on the toolbar.

The wizard includes two pages, Configure Adapters and Define Monitoring Goals, if you select the option to skip policy customizations, and three if you answer the questions to generate a new default policy.

Manage Solution Page Options



Adapter Type list

Provides a list of the adapters included in the solution.

Configured adapters provide the settings and credentials that vRealize Operations Manager needs to communicate with your vCenter Server instances or action instances.

Instance Name list

List of configured adapter instances based on the selected adapter type.

This list is blank until you configure at least one instance.

Adapter Settings

Settings used to uniquely identify the target vCenter Server instance.

Display name. Enter the name for the vCenter Server instance as you want it to appear in vRealize Operations Manager. A common practice is to include the IP address so that you can readily identify and differentiate between instances.

Description. Enter any additional information that helps you manage your instances.

Basic Settings

Minimum settings used to connect to the target vCenter Server.

vCenter Server. Enter the FQDN or IP address of the target vCenter Server instance. The FQDN or IP address must be reachable from all nodes in the vRealize Operations Manager cluster.

Credentials. Click the plus sign to add a credential name, which is the display name, the user name of the credentials you are using to connect to this vCenter Server instance, and the associated password.

Test Connection. Click to verify that the provided credentials can connect to the target vCenter Server and so that you can validate the certificate. The certificate presented is the leaf certificate for the vCenter Server instance, not the complete certificate chain. Click OK only if the certificate presented in the dialog box matches the certificate for your target vCenter Server.

Advanced Settings

Provides options related to designating specific collectors to manage this adapter instance, managing object discovery and change events, or associating a second set of credentials with the adapter instance.


Determines which vRealize Operations Manager collector is used to manage the adapter processes. If you have only one adapter instance, select Automatically select collector. If you have multiple collectors in your environment, and you want to distribute the workload to optimize performance, select the collector to manage the adapter processes for this instance.

Auto Discovery

Determines whether new objects added to the monitored system are discovered and added to vRealize Operations Manager after the initial configuration of the adapter.

If the value is true, vRealize Operations Manager collects information about any new objects that are added to the monitored system after the initial configuration. For example, if you add more hosts and virtual machines, these objects are added during the next collections cycle. This is the default value.

If the value is false, vRealize Operations Manager monitors only the objects that are present on the target system when you configure the adapter instance.

This option is not available for the vCenter Python Actions adapter.

Process Change Events

Determines whether the adapter uses an event collector to collect and process the events generated in the vCenter Server instance.

If the value is true, the event collector collects and publishes events from vCenter Server. This is the default value.

If the value is false, the event collector does not collect and publish events.

This option is not available for the vCenter Python Actions adapter.

Registration User and Password

Provides the option to use a different set of credentials than you provided as the standard credentials.

The standard credentials must be provided. The standard credentials should have at least read permissions so that vRealize Operations Manager can collect data.

These advanced credentials allow you to register a vCenter Server with a different set of credentials. The registration user commonly has more access rights. For example, this user account can register a vCenter Server extension or asset. You use the advanced credentials in conjunction with the standard credentials when you need to manage security by minimizing access.

This option is not available for the vCenter Python Actions adapter.

The Define Monitoring Goals page provides you with the default policy option, which determines how vRealize Operations Manager collects and analyzes data in your monitored environment.

Define Monitoring Goals Page Options



Which objects do you want to be alerted on in your environment?

Determines which objects you manage with vRealize Operations Manager.

Which types of alerts do you want to enable?

Determines which alert badge notifications you want to see in your environment.

Alert definitions are configured to affect Health, Risk, or Efficiency when an alert is generated. Select one or more of the alert types for which you want to receive alerts.

How much do you want to overcommit CPU and memory in your environment?

Determines how objects are monitored based on how you prefer to oversubscribe resources and whether you want to allow overcommitment for CPU and Memory.

CPU overcommitment is running more vCPUs on a host than the total number of physical processor cores in the host.

Memory overcommitment is allowing a virtual machine to use more memory space than the physical host has available.

Do you want to include Network & Storage I/O when analyzing capacity and workload?

Determines whether you want network and storage input and output values included in your capacity calculations.

The Ready to Complete page appears when you define a new policy rather than selecting the option to skip policy customization. Click Finish to complete the wizard.