About the attribute key:
See this documentation page. Extract:
The key of a node is a unique identifier for the entity that the node represents. However, the key of a node is persistent unlike the node ID.
This attribute typically contains strings like 1yvZYerAjrgHlIDSHd95og==
In a syncmapping TPL, the host 'key' field is mapped to the 'key' field in BMC_ComputerSystem or other classes:
270 computersystem := sync.BMC_ComputerSystem(
271 key := host.key,
About the attributes ADDMIntegrationID, correlation_id and "Unique CI Source ID":
ADDMIntegrationId is an attribute of BMC CMDB.
correlation_id is an attribute of ServiceNow.
Unique CI Source ID is an attribute of RemedyForce. The exact name is __RF_UniqueCISourceID_CaseSens__c.
They are used by Discovery to retrieve its CIs. Their values are derived from the key attribute.
For example:
Host.key: vArj+BWumb7N7D6gFmscmw==
BMC_Computer.ADDMIntegrationId: vArj+BWumb7N7D6gFmscmw==#BMC_ComputerSystem
About the attribute TokenId (BMC CMDB)
See this documentation page. Extract:
TokenId is an attribute that in some circumstances aids reconciliation[...]
For the CMDB, TokenID is optional.
Most of the time, the data inserted by Discovery (name, domain, serial, uuid ...) into the cmdb is enough for RE to identify CIs. In this case, there are no technical reasons to copy/paste/mix the same data into the TokenID.
To complete/reformulate this documentation page:
-
When the attribute Host.__cdm_override_token_id is set, BMC_ComputerSystem.TokenId is set too.
-
Discovery tries to set Host.__cdm_override_token_id in case of virtualization (vmware, Xen, oraclevm, KVM, HyperV...)
-
When Host.hostname and Host.dns_domain are precise enough (not "localhost"), BMC_ComputerSystem.TokenId is set.
-
The TokenId won't be set if Discovery has to synchronize a KVM Host node while it has no related VirtualMachine node.