Use Case

  • Collects different topology data from vROps and creates new CIs in OpsBridge through OPSC Rest policy

Requirements

This section provides information about the requirements, which should be met, In order for the integration template to function properly.

Integration Requirements


vROps RequirementsOperations Connector Requirements

Authentication

  • Integration User

  • N/A

Permissions

  • Admin

  • N/A

Environment

  • N/A

Network Requirements


Network Requirements

Communication

  • ZigiOps → vROps (80/443)

  • ZigiOps → Operations Connector (30005)

Setup

To enable the integration, you should follow the steps below.

  1. You should start with the selection of the integrated systems and the integrated entities. The integrated entities should be pre-selected if there are no issues with the credentials/permissions, used in the connected systems configuration. 

    Example

  2. Press the Save button to save the changes. 

    Example

  3. You should enable the operations to start the integration. 

    Example

Operations Explanation

This section provides information about the predefined operations of this integration template, including the default field mapping configuration. Each operation consists of two tabs - Source, Field Map. The Source tab contains the trigger, trigger conditions and expressions configuration. The Field Map tab contains the mapping configuration. 

01-vCenter Server

This operation polls the data from vROps. It is designed to collect vCenter Server data from vROps and Ci in OMi. ThevCenter Server data is collected from the vROps instance, then it is internally processed through the field mapping configuration, and finally, a request is sent to OPsC to create a new Ci.

Source

From this tab you could customize the polling interval, trigger conditions and expressions or use the defaults. 

Example

Field Map

From this tab you could customize the field, value, and conditional mappings, which suit your requirements. 

Example

02-Datacenter

This operation polls the data from vROps.  It is designed to collect Datacenter data from vROps and create Ci in OMi. The Datacenter data is collected from the vROps instance, then it is internally processed through the field mapping configuration, and finally, a request is sent to OPsC to create a new Ci.

Source

From this tab you could customize the polling interval, trigger conditions and expressions or use the defaults. 

Example

Field Map

From this tab you could customize the field, value, and conditional mappings, which suit your requirements. 

Example

03-ESX Server

This operation polls the data from vROps.  It is designed to collect ESX Server data from vROps and create Ci in OMi. The ESX Server data is collected from the vROps instance, then it is internally processed through the field mapping configuration, and finally, a request is sent to OPsC to create a new Ci.

Source

From this tab you could customize the polling interval, trigger conditions and expressions or use the defaults. 

Example

Field Map

From this tab you could customize the field, value, and conditional mappings, which suit your requirements. 

Example

04-Virtual Machine

This operation polls the data from vROps. It is designed to collect Virtual Machines data from vROps and create Ci in OMi. The Virtual Machines data is collected from the vROps instance, then it is internally processed through the field mapping configuration, and finally, a request is sent to OPsC to create a new Ci.

Source

From this tab you could customize the polling interval, trigger conditions and expressions or use the defaults. 

Example

Field Map

From this tab you could customize the field, value, and conditional mappings, which suit your requirements. 

Example

05-IP Address

This operation polls the data from vROps.  It is designed to collect IP Address data from vROps and create CI in OMi. The IP Address data is collected from the vROps instance, then it is internally processed through the field mapping configuration, and finally, a request is sent to OPsC to create a new Ci.

Source

From this tab you could customize the polling interval, trigger conditions and expressions or use the defaults. 

Example

Field Map

From this tab you could customize the field, value, and conditional mappings, which suit your requirements. 

Example

Recommendations

This section provides information about the recommended considerations, which should be taken into account, before starting the integration.

Mapping

The predefined templates are complied with the specifics of the integrated systems. It is recommended to confirm if your integrated systems have any required fields, which must be reported, so you could map them accordingly. Please note that if a required field is not mapped, the operation might fail. In this case, you could review the troubleshooting page for more information about the operation's execution history.