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

Datasets

BMC CMDB enables you to create datasets, each of which holds a distinct set of configuration data. Datasets can store data from a variety of discovery applications for the BMC Atrium CMDB. The same computer system or other CIs can exist in more than one dataset.

Data that is transferred from the BMC BladeLogic Client Automation Inventory database to the BMC Atrium CMDB is stored in a special dataset. The BMC Atrium Discovery data transfer creates a second dataset, and existing BMC Remedy Asset Management data resides in a third dataset. The following table shows the dataset names and associated IDs.


 The following table shows the datasets in CMDB:


After data is transferred, discovered data remains separate from data in the BMC Asset dataset. To create one unified dataset of all your asset data, you can use the Reconciliation Engine. After the configuration data has been reconciled, it can be used by consumers of BMC Atrium CMDB.

For example, when working with the BMC Configuration Import and BMC.ADDM datasets, the Reconciliation Engine uses the following Reconciliation Engine jobs to consolidate data from the two datasets into the BMC Asset dataset:

  • Configuration Discovery Reconciliation Process — Reconciles the BMC Configuration Import dataset with the BMC Asset dataset
  • BMC Atrium Discovery Reconciliation Process — Reconciles the BMC.ADDM dataset with the BMC Asset dataset

Important

If you create a CI by any other source, such as BMC. ADDM, no record in AST:Attribute is created for the corresponding CI. The record in AST:Attribute is created only after reconciliation, when the CI is pushed to the BMC.ASSET dataset.


 

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