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 > Install

Install

The following section provides information about installing OpsCx for VROPS version 1.00.

Before installing OpsCx for VROPS, consider the installation prerequisites . Determine whether the product will operate in a consolidated setup or it will be used in a distributed setup. Before you start with the installation process, familiarize yourself with the conventions listed in the table in this section.

Installation of OpsCx for VROPS consists of several tasks. Complete them in the following order:

Obtain and install OpsCx for VROPS. See Install OpsCx for VROPS topic.
Install the OMi topology synchronization package and the OMi content pack for metrics. See Installing the Topology Synchronization Package and Importing the Content Pack topic.

Although performing this task is mandatory only if you plan to collect VROPS topology, visualize VROPS metrics, or if you intend to enrich the collected VROPS events with topology-related information, it is recommended that you perform it in any case.

OpsCx for VROPS does not support upgrade scenarios. If you have a previous product version installed on the target host, remove it first. It is recommended that all relevant data is backed up prior to the removal.

Due to a known issue in OpsCx for VROPS, filenames of the shared configuration files in a distributed setup contain a suffix that denotes the host operating system: _nt on Windows systems and _linux on Linux systems. In this document, the suffix is omitted from the configuration file names for better readability.

Conventions Used in the Installation, Configuration, and Other Procedures

The following placeholders are used in the instructions throughout this document. When performing the steps, specify the actual value in place of each placeholder:

Placeholder	Meaning	Example of Default Values
`<Version>`	Product version string of OpsCx for VROPS: major version, minor version, and build number. It is embedded in the filename of the installation package.	Example: `02.00.032` This string represents the version 2.00 and the build number 32.
`<OvInstallDir>`	Directory where Operations Agent and OpsCx for VROPS are installed on the Operations Connector host.	Windows: `C:\Program Files\HP \ \HP BTO Software` Value (Linux): `/opt/OV`
`<OvDataDir>`	Data directory of Operations Agent that is jointly used by Operations Connector and OpsCx for VROPS.	Windows: `C:\ProgramData\HP\HP BTO Software` The `C:\ProgramData` directory is hidden by default. Value (Linux): `/var/opt/OV`
`<OMiHome>`	Directory where Operations Manager i is installed.	Windows: `C:\HPBSM` Value (Linux): `/opt/HP/BSM`

All paths in this document use slash (/) as path delimiters except in contexts where the operating system specifics are stated. When performing the steps, use the path delimiters that your operating system supports.

Install

Related topics