This documentation supports the 18.08 version of BMC Atrium Core.

To view the latest version, select the version from the Product version menu.

Standard reconciliation jobs

In most cases, you can use a standard reconciliation job or the standard rules to identify and merge your data. 

You should start with a standard identify and merge job. Unless you need different identification or precedence (merge) rules, you can use a Standard Identification and Merge Job and modify the activity options while still using the standard rules. 

  • You can create and modify a standard identification and merge job that uses the standard rules for the following customizations:
    • If you need to change the source and production data set in an identify activity
    • If you need to change the Generate IDs or Exclude Subclasses options in an identify activity
    • If you need to change the source and target data sets in a merge activity
    • If you need to change the Include Unmerged CIs option or the Merge Order option in a merge activity
  • If you have one data set that needs to have different identify or precedence rules, you might have to create a custom job, disable the standard rules, and create custom identify or precedence rules. 

For merge, you can set a precedence value for a data set, or, if required, you can assign a precedence value to a particular class or attribute in a specific data set. For example a company, Calbro wants to keep the default precedence value of 800 for BMC_Product in the BMC Configuration Import data set, but they want to assign a higher precedence value to BMC_Product in the CALBRO.APPS data set because it is an import of software products that they consider more accurate. 

For identification, you cannot specify a rule for a particular data set, but you can check whether adding an attribute at a lower priority addresses the needs of a specific data set. For example, if Calbro knows that for the CALBRO.APPS data set, the TokenIDName, and SerialNumber attributes are not sufficient to identify some instances, Calbro can add the custom CalbroID attribute that identifies those instances in that data set. By setting it to a priority of 3, the default rules work for most data sets, but for CALBRO.APPS after the priority 1 and 2 attributes fail to identify instances, the reconciliation engine uses the CalbroID attribute.

The standard job contains the most common reconciliation activities:

  • Identifying class instances that are the same entity in two or more data sets.
  • Merging class instances from one data set (such as discovery) to another data set (by default, the production data set BMC.ASSET).


By default, a standard job identifies and merges CIs that have not been normalized. To reconcile only CIs that have been normalized, enable the Process Normalized CIs Only option when creating a job.

Best practices

We recommend that you adhere to the following guidelines when creating a standard reconciliation job:

  • After discovering data, normalize the data, and reconcile it into your production data set immediately after your discovery application loads data into BMC CMDB.
  • Do not create jobs that simultaneously identify the same data set or merge data into the same target data set. Simultaneous reconciliation can either overwrite data you wanted to keep from the other job or create duplicate CI instances.
    If you need to create multiple jobs to merge data into the same production data set, use the execute activity to run the jobs sequentially or set the jobs as continuous and run them in parallel with the View Other Datasets for Parallel Continuous Jobs option selected. You can configure this option from the new CMDB dashboard, select Configurations > Core Configurations page, and click the Reconciliation component in the left pane. 
  • Do not run the BMC Atrium integration engine, normalization engine, and reconciliation engine at the same time because they might have an impact on system resource availability.
  • For a large amount of data, such as an initial load, run separate identify and merge jobs to allow for better diagnostics.
  • For incremental updates, run identify and merge activities in one job. For new CIs, the identify and merge activities may take more time to run. For modified CIs, the identify activity runs quickly because the CIs have reconciliation IDs.
  • Consider indexing attributes used in identification rules. Consult your DBA to determine what indexes would help you.
  • Do not rename the out-of-the-box reconciliation jobs, because other products could be using the names given to those jobs.

To create a standard reconciliation job

The procedure for creating a standard reconciliation job is available through an interactive Walkthroughs widget. From the dashboard page, or from the Reconciliation component, click the Walkthroughs widget, and then click Creating a Standard Reconciliation Job. The walk-through guides you with the steps you must follow to create the job. 

Was this page helpful? Yes No Submitting... Thank you