Each root node kind in the Discovery model is mapped to the Common Data Model as follows:
|Restart tideway service after making changes to CDM|
If any changes are made to the CDM, for example, adding attributes, you cannot sync to those attributes until the tideway service has been restarted. On restart of the tideway service, the CDM is read and all customized classes and attributes are available to CMDB sync.
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.
So that Discovery can properly maintain the CIs it creates in its dataset, it stores a unique "key" on every CI, in the attribute named ADDMIntegrationId. These keys are sometimes directly populated from the key on a corresponding node in the Discovery data store, but in other situations they are constructed using rules appropriate for the mapping structure. See the syncmapping definitions for details of how keys are populated.
|ADDMIntegrationId key length|
If the ADDMIntegrationId key length exceeds 255 characters, then BMC Atrium CMDB raises an exception and the node is not synchronized. This is fixed in BC Atrium Discovery 8.2.01 where an MD5 hash of keys exceeding this length is used instead of the key.
If you have patterns which create keys longer than 255 characters, and you have extended the permissible size of the attribute in BMC Atrium CMDB, and you upgrade to BMC Atrium Discovery 8.2.01 then you will see duplicate CIs.