Default CDM Mapping
Root node kind mappings
- CDM Mapping for Host
- CDM Mapping for MFPart
- CDM Mapping for Network Device
- CDM Mapping for Printer
- CDM Mapping for SNMP Managed Device
- CDM Mapping for Storage
- CDM Mapping for Cloud
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 and relationships, 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. See the Pattern templates for examples.
So that BMC Helix Discovery can correctly maintain the CIs it creates in its dataset, it stores a unique key on every CI, in the
ADDMIntegrationId attribute. These keys are sometimes directly populated from the key on a corresponding node in the BMC Helix Discovery datastore, but in other situations they are constructed by using rules that are appropriate for the mapping structure. See the syncmapping definitions for details of how keys are populated.
If the CMDB is configured for multitenancy, all CIs can have a
Company attribute set appropriately. See Multitenancy for details.