Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Operations Connector10.11

Integrate > VMware vRealize Operations Manager > Configure > Configure Topology Collection in Consolidated Setups

Configure Topology Collection in Consolidated Setups

In a consolidated setup, perform the following steps on your Operations Connector host to integrate VROPS topology into OMi:

Change the current directory to <OvDataDir>/conf/HPBsmIntVROps and open the vrops_topology.conf file (the topology integration configuration file) in a plain text editor.
In the configuration file, replace the value in quotation marks in the line of the following option:

vrops-hostname: The FQDN or IP address of your VROPS virtual machine.
Decide which VMware vSphere virtual systems should be included in the topology data:
- To include only the virtual systems that have IP addresses assigned, leave the value of the dns_lookup_enabled option unchanged (true).
- To include the virtual systems without IP addresses also, set the value of the dns_lookup_enabled option to false.
Review the preconfigured values of basic configuration options and adjust them as needed. Add and configure advanced options if necessary. For descriptions of basic and advanced options, see Integration Configuration Options topic.
Save your changes.
Log on to the Operations Connector web interface and import the policy for VROPS topology by navigating to the <OvDataDir>/installation/HPBsmIntVROps/policies directory and selecting the following files:
- e3d48a5b-cee5-4ed9-bb41-468d1763c7c1_data
- e3d48a5b-cee5-4ed9-bb41-468d1763c7c1_header.xml
The type of the Operations Connector policy for VROPS topology is XML File. Operations Connector validates it after importing.
Import the policy for VROPS self-discovery topology by navigating to the <OvDataDir>/installation/HPBsmIntVROps/policies directory and selecting the following files:
- 0d15490e-df89-48a8-9430-42b7b9fbb2a1_data
- 0d15490e-df89-48a8-9430-42b7b9fbb2a1_header.xml
The type of the Operations Connector policy for VROPS self-discovery topology is XML File. Operations Connector validates it after importing.
Review the policies to make sure their settings are proper for yourOpsCx for VROPS configuration.
From the Operations Connector web interface, activate the imported policies.
Open a Command Prompt window (command shell).

If Operations Connector is hosted on a Linux system, change the current directory to cd /opt/OV/bin64.
Run the following commands to set the VROPS user name and password on the OpsCx for VROPS so that the Connector can get metrics data from VROPS machine.

Only the VROPS user with administrative or REST API privileges can access the VROPS machine for collecting metrics. For information on creating user account with these privileges, see the section VROPS user roles and accounts in the topic Installation Prerequisites.

genintcrypt --generate

genintcrypt --set vrops_user

genintcrypt --set vrops_password

Specify the credentials of the user account with administrative or REST API privileges for vrops_user and vrops_password.

The user name can be in any of the following formats:
- username@domain
- username@domain@auth_source
Type the correct user name and password when prompted. The typed text is not visible in the command prompt window. If you make an error, do not attempt to correct the text, but rather run the command again.
To verify the entered credentials, run the following commands:

genintcrypt --check vrops_user

genintcrypt --check vrops_password

A correct configuration is denoted by the following response of each command:

genintcrypt:Value exists for ID '<ArgumentName>'

If Operations Connector is hosted on a Linux system, change the current directory to cd /opt/OV/bin
To register the corresponding component with Operations Agent, run the following command:

For Windows:

ovcreg -add \ "<OvDataDir>\installation\HPBsmIntVROps\ovc\HPBsmIntVROps_Topology.xml"

For Linux:

ovcreg -add \ <OvDataDir>/installation/HPBsmIntVROps/ovc/HPBsmIntVROps_Topology.xml
To start the collection service, run the following command:

ovc -start vropst

Startup of the service initiates topology collection from VROPS and forwarding of the topology to OMi.

Verify your connection settings by checking for the presence of the vrops_topology.xml file in the <OvDataDir>/datafiles/HPBsmIntVROps directory on the Operations Connector host. If the file does not exist, check the corresponding OpsCx for VROPS log file. For details, see Log Files topic.

If you deactivate the policy for VROPS topology, topology changes continue to be collected while the policy remains inactive after the deactivation. The processing and forwarding of accumulated changes resumes when you reactivate the policy.

Configure Topology Collection in Consolidated Setups

Related topics