Creating a standard reconciliation job

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 jobs. 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.

Creating-a-custom-reconciliation-job

If you have any dataset that needs to have different identification rules or merge precedence rules, you can either edit the existing standard rules or create a custom job.

edit Standard ID Merge rules.jpg

For identification, you can specify a standard rule only at class level and not at a dataset level. You can add and remove an attribute in the rule, and set a priority. For example, Chris, the configuration manager at Calbro Services, knows that for the CALBRO.APPS dataset, the TokenID, Name, and SerialNumber attributes are not sufficient to identify some instances. Chris adds the custom CalbroID attribute that identifies those instances in the CALBRO.APPS dataset, and assigns Priority 1. Because CALBRO.APPS has a priority of 1, for CALBRO.APPS, the reconciliation engine uses identification rule configured for the CalbroID attribute.

For merge, you can set a precedence value for a dataset. You can also assign a precedence value to a particular class or attribute in a specific dataset. For example a company, Calbro Services wants to keep the default precedence value of 100 for BMC_Product in the BMC Configuration Import dataset. However, they consider BMC_Product in the CALBRO.APPS dataset to be more accurate than BMC Configuration Import dataset. They assign a higher than 100 precedence value to BMC_Product in the CALBRO.APPS dataset.

The standard job contains the most common reconciliation activities:

Identifying class instances that are the same entity in two or more datasets.
Merging class instances from one dataset (such as BMC Discovery) to another dataset (by default, the production dataset is BMC.ASSET).

Important

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.

Before you begin

Confirm whether the standard rules are suitable. To edit the standard rules, see,
(Identification rules) Configuring-reconciliation-identification-rules.
(Merge rules) Creating-precedence-sets-and-associations-for-reconciliation-merge-activities.
Understand the guidelines for obtaining best results from the reconciliation jobs. For information about the guidelines, see Reconciliation-best-practices.

Important

When running standard reconciliation jobs, use standard identification and merge rules that are provided out of the box. When creating custom reconciliation jobs, create and use custom identification and merge rules.

If you are migrating from an older version of BMC CMDB and if a custom job uses a standard rule, you must delete those jobs and recreate the custom job with custom rules.

After recreating the jobs, perform the migration tasks.

To create a standard reconciliation job

Log in to CMDB Portal.
see, Accessing-and-navigating-the-CMDB-Portal.
In CMDB Portal, select Jobs > Manage Reconciliation.
Click Create Job and enter a job name.
Select the appropriate settings for the job.
To view the details of every setting, hover the cursor over each setting.
To use the standard rules for Identify and Merge activities, select Use Standard Rules for Dataset.
Select Disable Progress Bar on UI During Job Execution for better job performance.
To add an Identify activity, click Add activity > Identify and perform the following steps:
The [expand] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
To add a Merge activity, click Add activity > Merge and perform the following steps:
The [expand] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
To add Purge activity, click Add Activity > Purge and perform the following steps:
The [expand] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
(Optional) Select a schedule for the job run frequency.
Click Save.
(Optional) To run the job immediately, open the job from All Job Run Activities and click Start Job.

Important

Changes made to the new job definitions are delayed until the next scheduled Job Definition check interval parameter runs. To load the changes immediately, open and save the job from the UI.
If a class does not have any standard identification rule associated with it, the rules defined for the parent class are applied by default. If you want to change the default rules, create a custom identification rule.

Creating a standard reconciliation job

Before you begin

To create a standard reconciliation job

On this page