How to Map the CI Attribute to the Web Service Field

The integration uses an adapter to transform Service Manager web service fields to Universal CMDB CI attributes. The adapter in turn specifies what XSL transformation files the integration should use to convert Service Manager web services messages into a properly formatted Universal CMDB CI and/or relationship.

Out-of-the-box, each integration query has a corresponding XSL transformation file that maps to a particular CI type in Universal CMDB. Without an XSL transformation entry, Universal CMDB cannot receive any CI attribute updates from your Service Manager system.

Unlike for the Push feature, you do not need to create real queries for Population on the UCMDB server.

If you want to add a new attribute to the integration, you must edit the XSL transformation file for the parent CI type and add an entry for the CI attribute. For information about which CI types each population query manages, see Integration queries. In order to create a proper XSL mapping, you must be familiar with the service and object names that Service Manager publishes as Web services. For information on publishing tables and columns as Web service fields, see the Service Manager help.

The following steps illustrate how to map a UCMDB CI attribute called host_vendor to a Service Manager web service field called OSVendor.

To map a CI attribute to a web service field:

  1. Log in to UCMDB as an administrator.
  2. Navigate to Data Flow Management > Adapter Management.
  3. Navigate to the Service Manager Adapter configuration files path: ServiceManagerAdapter9.41 > Configuration Files.
  4. Click the XSL transformation file that manages the parent CI type of your CI attribute. For example, open computer_population.xslt to add an attribute to the SM Computer Population query.
  5. Find the element that defines the name of the Universal CMDB CI Type where the integration will store CI attribute values. For example, the element <ci class="node"> will store CI attributes in the Universal CMDB Node CI Type.
  6. Within the ci naming element (<ci class="node">), you will see an element of the following format that defines how to transform each web service field into an Universal CMDB CI attribute:
    <attribute name="UCMDB_CI_attribute_name" type="UCMDB_CI_attribute_type" ignoreCIIfEmpty="true">
    <xsl:value-of select="SMAttributeName "/></attribute>

    UCMDB_CI_attribute_name is the name of attribute in the Universal CMDB system.

    UCMDB_CI_attribute_type is the type of attribute of the Universal CMDB system which this integration supports. Currently the following types are supported: String, StringList, Integer, Long, Double, Boolean, IPAddress, Date, Float, and IntList.

    ignoreCIIfEmpty is a parameter that specifies whether or not to ignore the CI during population if this attribute has an empty value (true: ignore; false: not ignore).

    Note

    SMAttributeName is the name of a web service attribute published by the Service Manager system.

    CI attributes in the computer_population.xslt file are illustrated in the following screenshot:

    Refer to the following screenshot to match CI attributes in the ucmdbNode web service object:

  7. Copy an existing XSL transformation element to use it as a template to create a new transformation entry.
  8. Paste the new XSL transformation element within the proper table naming element. For example, <ci class="node">.
  9. Update the CI attribute name and web service field name within the new element to match the attribute you want to add to the integration. For example, create the following XSL transformation element to add the os_vendor attribute to the integration.
    <attribute name="os_vendor" type="String"><xsl:value-of select="file.node/OSVendor"/></attribute>

    New attribute in the computer_population.xslt file is illustrated in the following screenshot:

  10. Save the XSL transformation file.

When you create/edit and then save a configuration file in Adapter Management, UCMDB automatically restarts the adapter with the new configuration file.