You can now send CIs and relationships between UCMDB and ServiceNow. HP UCMDB introduced two independent, bi-directional integrations with ServiceNow in Content Pack 14. There is now a Data Push into ServiceNow and a Population from ServiceNow. They both use XML mapping to dynamically map CI types between them, without requiring code changes.

Data Push into ServiceNow

This integration is supported in HP UCMDB 9.02 and later. Queries are created in the UCMDB to select the CIs and relationships to be sent to ServiceNow, and for every query an XML mapping file is created to match it. An integration point is then created that can have multiple jobs. Each of these jobs can be a full synchronization or a delta mode that will only push data that has change since the last job was executed. Multiple jobs can satisfy many needs such as Discovered data, data to support Cloud Service Automation provisioning or data contained in application maps. The discovered data jobs can be synched with the discovery schedule to ensure the most up to date Cis and relationships are sent to ServiceNow after the discovery has run. To ensure CSA data is up to date for RFC’s in ServiceNow these jobs could be scheduled at a high frequency such as minutes. The application map data would not be needed as frequently and can be on demand or after corresponding discovery jobs.

This integration is limited to a long list of supported OOTB CI types, but the integration can be customized for others. The HP Third party integration guide also lists these limitations:

  • The integration mapping file only allows mapping concrete CITs and relationships to the CITs and relationships in ServiceNow. That is, a parent CIT cannot be used to map its children CIs.
  • Since this adapter uses the ServiceNow Direct Web Services API, which does not support CI coalescing (reconciliation), if some Cis being pushed from UCMDB are already present in the ServiceNow CMDB, before the integration with UCMDB is installed, and if those Cis are (a) also in UCMDB; and (b) pushed into ServiceNow by the integration, those Cis are duplicated. (This is because UCMDB does not know these Cis are already in the ServiceNow CMDB.) After the adapter is installed, UCMDB keeps track of the Cis it pushes to ServiceNow, to prevent duplication.
  • ServiceNow Web Service Import Sets are currently not supported.

Population from ServiceNow

This integration is supported in HP UCMDB 10.01 and later. A ServiceNow integration patch must be installed on the UCMDB data probe. XML mapping files will then be created to indicate the topology to be retrieved from ServiceNow and how it will be mapped to the UCMDB class model. An integration point on the UCMDB will then be used to manage the data pull. A business case for utilizing this integration would be to send Business element instances created in ServiceNow to be utilized in the UCMDB for modeling, as this is not discovered data. There are many options because this integration supports all available CITs and relationships in ServiceNow. The HP Third party integration guide also lists these limitations:

  • Data replication in chunks is not supported.
  • Only full synchronization is supported (not delta synchronization).
  • Integration only works with Jython 2.5.3 and later.