Enabling CMDB synchronization

BMC Discovery uses  CMDB synchronization  to synchronize discovered data with CMDB.

Current CMDB sync mappings (in  November 2019  and subsequent TKUs) set the new InstanceName and ComponentAlias attributes for the CMDB CIs. BMC Helix Integration Service matches the  InstanceName and ComponentAlias attributes with those contained in the incident request. The incident request is populated by BMC TrueSight Operations Management (TSOM).

The BMC Discovery CMDB sync mappings are delivered as a TKU/Knowledge package and are installed by using  Knowledge management . For more information on TKU content and availability, see  Schedule and Roadmap .

To enable CMDB synchronization

1. If you need to update your TKU (it is currently an earlier release than November 2019), download the latest TKU/Knowledge package from  BMC Electronic Product Download  site. 
2. Upload and apply the knowledge package to BMC Discovery. For more information, see  Uploading knowledge .
3. Configure synchronization between BMC Discovery and CMDB. For more information, see  Setting up a CMDB synchronization connection .

CMDB sync mapping details

The BMC Discovery CMDB sync mappings have been updated to set InstanceName on CIs on the following classes, where the corresponding node in Discovery has an instance attribute:

• BMC_SoftwareServer
• BMC_DataBase
• BMC_Cluster
• BMC_ApplicationSystem

On BMC_VirtualSystemEnabler CIs, InstanceName is set from the Discovery attribute vm_name.

ComponentAliases is an attribute that is set by default for a number products represented by the following CDM classes:

• For BMC_ComputerSystem CIs corresponding to servers, ComponentAliases is set to a value of the form:
  • BMC_ComputerSystem:<hostname>:<DNS domain>
• BMC_Cluster CIs for Microsoft Cluster and VMware Virtual Center clusters:
  • Microsoft Cluster:<cluster name>
  • vCenter Cluster:<hostname of vCenter server>:<DNS domain>
• For BMC_SoftwareServer and BMC_DataBase CIs representing many relational database types, for example, “Microsoft SQL Server” or “Oracle Database”:
  • <type>:<hostname>:<DNS domain>:<instance name>
where type is the value of the Discovery type attribute from the corresponding SoftwareInstance or Database node.

The standard component aliases may be extended to more software types in future TKU releases.