In this article, I’ll show you how you can quickly perform an integration between VCAC and Service Now for the purposes of creating and updating CIs in the CMDB for VM machine instances. I’m using the VCO/VCAC plugin for this integration, instead of the previously used VCAC Designer (no longer required!). For this integration you will need:

  • VCAC 6.x – I’ve tested this with versions 6.01 and 6.1
  • VCO/VCAC plugin version 6.x – Any version of the plugin from 6.x on should work fine
  • Make sure you have already run the “Install vCO Customization” workflow as part of the vCO/VCAC plugin previously. If not, you must run this first to enable workflow stub integration
  • Experience with VCAC, VCO, custom properties, and workflow stubs.

The basic high level steps are as follows:

1) Download and install the package I’ve provided here: at –  com.vmware.set.west.servicenow. You will see a new folder called SNOW with 4 new workflows for insert and update cmdb.





2) Add your Service Now SOAP host WSDL for the cmdb_ci_vmware_instance table. You can do this by running the Add a SOAP host workflow. Once done, make sure you can browse it from the Explorer tab in VCO.





3) Update the Configuration item in VCO to reflect your new SOAP host. This will allow the workflows to point to the correct SOAP host you added in the previous step.




 4) Run the VCO workflows for adding the master workflows to your VCAC stubs. Choose either BuildingMachine or MachineProvisioned for the master_cmdb_insert workflow, and MachineDisposing for updating the master_cmdb_update workflow. The workflow is called “Assign a state change workflow to a blueprint and its virtual machines” and will add the custom properties to one or more of your Blueprints when you select each of the respective master workflows.





5) Create a Build Profile in VCAC to run the stub properties and VCO workflow IDs and attach it to a Blueprint. You can basically copy and past the workflow ID and property from the Blueprint into the Build Profile.





6) Request your Blueprint from the catalog. You will see a new CI in your Service Now instance. You should also notice the sys_id as a custom property for the newly provisioned VM in VCAC.






7) Destroy the machine in VCAC and you will notice the updated CI in Service Now is set to Retired with additional notes




8) Modify and add fields to your liking.


One comment has been added so far

  1. Great mechanism, thanks! Could this same download be used in an estate that is only using vSphere 6.x (i.e. No vCAC)?

Leave a Reply

Your email address will not be published.