Default ServiceNow Mapping

Root node kind mappings

Each root node kind in the Discovery model is mapped to ServiceNow as follows:

Note

If possible, you should make modification to class definitions in the CMDB before setting up the CMDB sync connection. Changes made to the class definitions in the CMDB are only read by BMC Helix Discovery when the CMDB sync connection is set up, or when the services are restarted. You cannot restart services through the BMC Helix Discovery UI, so you should raise a case with Customer Support.

Extending and modifying the standard mappings

If you need to extend or modify the standard mappings, it is best to do so with extension mappings, rather than by editing the standard mappings. Extension mappings are able to create new CIs relationships, reference fields, set additional CI attributes, and change the standard values of existing CI attributes. The standard mappings should only be edited as a last resort, if the mapped structure needs to be different.

Relationships and Reference fields

The default mappings makes use of relationships and references between CIs.

Relationships have a relationship type, for example, "Runs on::Runs" (converted in TPL as "Runs_on__Runs") and are shown in the Related Items section on the CI form and in the Dependency Viewer in ServiceNow. Relationships between two CIs are stored in a separate relationship table in ServiceNow and allow many to many relationships.

A reference is a field in the CI record itself (that is, a foreign key). A reference to another CI can only be defined if a reference field has been designed in the ServiceNow CMDB table. For example, the table cmdb_ci_ip_address (IP Address) has a reference field “nic” which can be used to link to a record in the cmdb_ci_network_adapter table.

Default ServiceNow Mapping

Root node kind mappings

Extending and modifying the standard mappings

Relationships and Reference fields

Comments