Enable automation, visibility, and operational intelligence by centralizing all data in ServiceNow. Our scoped app enables ServiceNow's digital workflow management and automation within VMware's vRealize Suite. Integrates with vRA 7.X and 8.X, vRO, vCenter, vROps, NSX-T, and Horizon.
Check out our Guide to Enable ServiceNow's Digital Workflow Management and Automation in vRA in the supporting links and documents!
PLEASE CONTACT US PRIOR TO INSTALLING.
CMDB Data Synchronization
- Integrated with the ServiceNow Identification and Reconciliation Engine (IRE)
- Integrated with the ServiceNow credential store.
- Flexible framework that allows for population of custom data attributes and tables.
OOTB integrations into VMware vRealize Automation 7.X and 8.X (vRA), vRealize Orchestrator (vRO), vRealize Operations (vROps) and VMware vCenter.
CMDB
- Populates CMDB with relevant CIs and relationships from vRA
- Populates CMDB with relevant CIs and relationships from vCenter
Service Catalog Integration for vRA
- Automatically creates service catalog items for vRA catalog items.
- Allows users to request vRA Catalog Items from ServiceNow service catalog.
- Automatically updates the CMDB when requests in vRA finish.
- Request catalog items on behalf of specific vRA users from ServiceNow
- Control user and group access to specific catalog items.
- Assign approval policies. Supports multiple stages of user and group approval.
- Trigger incidents when vRA catalog requests fail.
Change Management
Create and assign approval policies to catalog items.
- Supports OOTB ServiceNow approval processes.
- Enables the easy creation of custom approval policies in ServiceNow.
- Supports multiple stages of group and user approval.
- Supports change windows, meaning that automated requests will execute in a user specified change window.
Incident Management
Trigger Incidents and assign incidents to support groups automatically when problems in the environment are detected such as:
- Connectivity issues between ServiceNow, MID Server, and external systems.
- Authorization issues between ServiceNow and external systems.
- Catalog request failures for provisioning and day 2 operations.
- CMDB operation failures.
Robust Error Handling
Automatically detects and analyzes errors encountered during automated processes.
- Analyzed errors are automatically presented in a dashboard that described their root cause.
- High impact errors trigger the automatic creation of incidents.
Support Levels
Assign support groups to various criteria so that the proper groups are automatically notified when issues are encountered.
- Assign support groups and level of impact for specific classes of errors.
- Assign support groups for specific external system endpoints.
The Cloud Automation Framework brings visibility and business alignment to company’s cloud investments. The ServiceNow Certified scoped-application is the most robust integration between ServiceNow and VMware’s vRealize Automation (vRA). By having full, up to date knowledge of the infrastructure and providing the tools to take action on that information, it brings the tools to manage the business and leverage the investment.
Please see the Cloud Automation Framework documentation:
https://icgautomation.atlassian.net/wiki/spaces/PD/pages/25428020/Cloud+Automation+Framework+Release+1.X
ServiceNOW Configuration
Version
ServiceNOW Madrid or higher
- User Criteria Scoped API
- Configuration Management For Scoped Apps (CMDB)
VMWare Configuration
Version
vRA must be version 7.0 or higher.To connect a vRA instance to ServiceNOW, all vRA components must be on the same network as the MID server used to facilitate communication between ServiceNOW and the vRA instance.
Any firewalls must allow traffic on ports 161, 443, and 6514 between the MID Server and the following vRA Components
- vRA Appliance
- IaaS Server
- vRO Server
LDAP must be configured for ServiceNOW and the vRA components as described in the ServiceNOW wiki: http://wiki.servicenow.com/?title=LDAP_Integration#gsc.tab=
MID Server Configuration
Operating System
Windows or Linux operating system.
Version
The MID server must be running the 64-bit version. If the MID server installation files are downloaded according to the instructions listed on the ServiceNOW wiki, then this requirement will be met.
http://wiki.servicenow.com/index.php?title=MID_Server_Installation#Downloading_MID_Server_Files
Installationhttps://docs.servicenow.com/bundle/london-servicenow-platform/page/product/mid-server/concept/c_MIDServerInstallation.html
Hardware
Each MID server must have at least:
- 2 CPUs
- 8192 MB (8 GB) of Memory
- 20 GB total on the primary Hard Disk
The MID server must be able to resolve the following vRA components by FQDN:
- vRA Appliance
- IaaS Server
If multiple MID servers are used for failover, then the MID server cluster must adhere to the guidelines as described on the ServiceNOW wiki:
http://wiki.servicenow.com/index.php?title=MID_Server_Clusters#gsc.tab=0