Skip to main content
Skip table of contents

ServiceNow VMware instances topology to vROps topology

Use Case

Requirements

#

ServiceNow

vROps

Connected Systems

Authentication (supported methods)

  • Username and Password

  • Username and Password (local or active directory)

  • API Token (local or active directory)

Permissions

  • cmdb_ci_vmware_instance (READ)

  • sys_db_object (READ)

  • sys_glide_object (READ)

  • Administrator (role)

Environment

  • Integration User:

    • Timezone → “GMT”

    • Date Format → “yyyy-MM-dd”

    • User ID → Same as the “Username”

  • ZigiOps Management Pack

  • Correlation Field

Network Requirements

Setup

  1. Log in to your ZigiOps instance.

  2. Go to ZigiOps → Configurator and load the integration template.

  3. Select the desired Integrated Systems and Integrated Systems and click the Save button to continue.

  4. Enable the integration from the Slider button located in the middle section of the screen.

How does the ServiceNow vROps Integration work?

  1. When there is a new or updated VMware virtual machine in ServiceNow, ZigiOps detects it automatically and transforms all the data, based on a predefined mapping. ZigiOps allows advanced mapping and filtering to fit all of your requirements.

  2. When ready, ZigiOps transfers the data, and creates a vROps virtual machine. All the necessary instances are transferred in real time and the topology in vROps is kept up to date.

  3. When there are any updates in a VMware virtual machine in ServiceNow, ZigiOps collects the changes and updates the vROps virtual machine accordingly, enriching the vROps topology.

Visit our website for more information, about our ServiceNow vROps integration.

Specifics

No specifics are available for this integration.

ServiceNow vROps integration setup with ZigiOps. Learn how to transfer ServiceNow VMware instances topology as vROps topology. Read our technical documentation.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.