Installation Prerequisites

The following sections list the prerequisites that need to be fulfilled to enable installation of OpsCx for VROPS.

Application software

Before you install OpsCx for VROPS, the following software applications must be installed and configured:

Application	Supported Versions
VROPS	6.x
Operations Manager i	10.01 or later
Operations Connector	10.01 or later Operations Connector must be configured as a connected server in Operations Manager i and properly integrated to Operations Manager i. It can be installed either on the VROPS virtual machine or on a separate host. For 10.11 version, to install the VROPS connector, run the following command: <Connector_Installer.exe> -DSKIPCHECKS=true

TCP/IP Ports

The following table lists the ports that OpsCx for VROPS uses by default. In your Operations Connector environment, these ports may not be used by other software applications.

Port Number	Port Description
443	Default REST Web Service Listener port on the VROPS UI virtual machine (default HTTPS port). Used for receiving metrics from the VROPS UI virtual machine.
30005	Default port of Operations Connector policies of the REST Web Service Listener type. Used for dispatching VROPS events and metrics to the respective Operations Connector policies.
30006	Default socket communication port. Used for receiving events and topology data from a remote VROPS virtual machine.

If VROPS and Operations Connector communicate through a firewall, make sure the firewall rules allow connections through the listed ports.

If the default ports are not free, you can still change the port numbers while configuring OpsCx for VROPS. Remember that changing the port numbers include mandatory actions also in the third-party system management application or Operations Connector in order to reconfigure specific ports.

VROPS user roles and accounts

Only a user with administrative or REST API privileges can access the VROPS machine for collecting the metrics, topology, and events. To create a user account with these privileges, perform the following:

1. Create a user role in the VROPS machine with either of the following privileges:

   • administrative privileges

   • REST API privileges with "All other Read, Write APIs" and "Read access to APIs" permissions
2. (Optional) Create an user account if not already created.
3. Assign the newly created user role to an existing user or a newly created user account and set the Objects permission as "allow access to all objects in the System".

See VROPS documentation for information on creating user roles and accounts.

The user name can be in any of the following formats:

• username@domain
• username@domain@auth_source