Skip to Content
Information
This documentation supports the 20.02 version of Remedy Asset Management.To view an earlier version, select the version from the Product version menu.

Understanding the identification activity

The identification activity matches instances among multiple datasets, confirming that each represents the same real-life object. Instances are records in a configuration management database, whether they represent CIs or relationships.

Suppose that BMC BladeLogic Client Automation, the BMC BladeLogic Client Automation Scanner Service, and BMC Atrium Discovery detect computer A and create an instance of computer A in each of their datasets. The Reconciliation Engine compares each dataset with the BMC Asset dataset separately to determine if computer A already exists in the BMC Asset dataset.

Related topic

Reconciling data

The identification activity first compares Token IDs that each discovery source creates based on Windows Management Instrumentation (WMI) scanning technology or UNIX system calls. Because BMC Atrium Integration Engine pulls relationship data that relates child components (such as disk drives or IP addresses) with their parent computer systems, the Reconciliation Engine considers Token IDs unique to each computer system. 

Qualified CIs are readily selected by the identification rules for merging to the BMC Asset dataset and are assigned a reconciliation identity. 

If a TokenId is unqualified, the identification process compares other key attributes (for example, Name and SerialNumber) to the instances in the BMC Asset dataset to find the best match. 

The reconciliation process uses out-of-the-box rules to reconcile BMC Atrium Discovery CIs to the Asset dataset. You can modify those rules as required. 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Remedy Asset Management 20.02