Configure Data Collection in Distributed Setups

In a distributed setup, to integrate VROPS events, topology, and metrics into OMi, complete the following procedure on your Operations Connector host.

In case you do not want to integrate all VROPS entity types, omit the actions specific to the type you chose to exclude.

Complete the following procedure on your Operations Connector host:

1. Change the current directory to <OvDataDir>/conf/HPBsmIntVROps and open the vrops_remote.conf file (the shared integration configuration file) in a plain text editor.

2. Replace the values in quotation marks in the lines of the following options in the configuration file:

   • vRops-hostname: The FQDN or IP address of your VROPS UI virtual machine.

3. 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.

4. Save your changes.

5. Log on to the Operations Connector web interface.

6. Import the policies by navigating to the <OvDataDir>/installation/HPBsmIntVROps/policies directory and selecting the following files:

   • For VROPS events:

     • daa3e5f4-0d01-465a-83f0-2a6b332bc7db_data

     • daa3e5f4-0d01-465a-83f0-2a6b332bc7db_hader.xml

   • For VROPS topology:
     

     • e3d48a5b-cee5-4ed9-bb41-468d1763c7c1_data
     • e3d48a5b-cee5-4ed9-bb41-468d1763c7c1_hader.xml

     For VROPS self-discovery topology:

     • 0d15490e-df89-48a8-9430-42b7b9fbb2a1_data
     • 0d15490e-df89-48a8-9430-42b7b9fbb2a1_hader.xml

   • For VROPS metrics:

     • 77bc423c-7c54-4e55-a702-c7e261b443d5_data
     • 77bc423c-7c54-4e55-a702-c7e261b443d5_hader.xml

   In Operations Connector, the type of policies for VROPS events and metrics is REST Web Service Listener, and the type of policies for VROPS topology and self-discovery topology is XML File. Operations Connector validates them after importing.

7. Review the policies to make sure their settings are proper for your OpsCx for VROPS configuration.

8. Activate the imported policies from the Operations Connector web interface.

9. Open a Command Prompt window (command shell).

10. If Operations Connector is hosted on a Linux system, change the current directory:

    cd /opt/OV/bin64

11. 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.

12. To verify the user 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>'

13. If Operations Connector is hosted on a Linux system, change the current directory:

    cd /opt/OV/bin

14. Considering the operating system on the Operations Connector host, run the following command to register the corresponding component with Operations Agent:

    For Windows:

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

    For Linux:

    ovcreg -add <OvDataDir>/installation/HPBsmIntVROps/ovc/HPBsmIntVROps.xml

15. To start the shared data collection service, run the following command:

    ovc -start VROPS

Related topics

Configuration Options

Installation Prerequisites