This documentation supports the 21.05 version of BMC Helix CMDB.To view an earlier version, select the version from the Product version menu

Creating a custom reconciliation job

By creating a custom reconciliation job, you can use the custom identification rules and merge precedence exceptions.

Tip

For standard identification rules, you can set rules only at a class level regardless of the dataset.

For custom identification rules, although you can set the rule only at a class level, you can define multiple rules for the same class. These rules can be applied to different datasets through different reconciliation jobs. When you create a new custom reconciliation job and add an identification activity, you can select a specific custom rule that is defined for a class from the list of custom rules. The rule that is defined for the class is now associated to the dataset that is a member of the reconciliation job.

Related topics

Creating-a-standard-reconciliation-job

Configuring-reconciliation-identification-rules

Before you begin

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 custom reconciliation job

  1. From CMDB Portal, select Jobs > Manage Reconciliation.
  2. Click Create Job and enter a job name.
  3. Select the appropriate settings for the job.
    To view the details of every setting, hover the cursor over each setting.
  4. To use custom rules for Identify and Merge activities, clear the Use Standard Rules for Dataset check box.
  5. Select Disable Progress Bar on UI During Job Execution for better job performance.
  6. To add an Identify activity, click Add activity > Identify and perform the following steps:
    Steps to add Identify activity
    1. (Optional) Specify a name for the activity and configure the following parameters:
      • Namespace
      • Sequence
      • Status
      • Continue on Error
    2. Select Source and Production datasets from the lists.
    3. In Selected Dataset, click the Standard Rules icon to use an identification rule.
      Standard ID rules Icon.jpg
    4. (Optional) Set the preferences for the following options:
      • Generate IDs
      • Exclude Sub-classes
    5. (Optional) In Qualification, add a qualification set to select which classes and instances to include in the identification activity. 
      1. Clear the Use all classes and instances check box to restrict the Identify activity by using a qualification set.
      2. Click Select qualification ruleset to select a qualification set.

  7. To add a Merge activity, click Add activity > Merge and perform the following steps:
    Steps to add Merge activity
    1. (Optional) Specify a name for the activity and configure the following parameters:
      • Namespace
      • Sequence
      • Status
      • Continue on Error
    2. Select Source and Target datasets from the lists.
      ImportantYou can select multiple datasets as a source dataset in the Merge activity instead of creating multiple jobs to merge data into the same production dataset.Merge_Multiple datasets1.jpg
    3. In Selected Dataset, click the Standard Rules icon to view and add the standard merge precedence rule for the selected dataset.
      Std Merge rules icon.jpg
    4. Select a Precedence association set for the datasets selected for this activity.
      In a standard reconciliation job, BMC Default Precedence set is selected by default and cannot be changed.
      To change the values in the precedence association set, see Creating-precedence-sets-and-associations-for-reconciliation-merge-activities.
    5. Set Merge Order based on your requirements:
      Merge order
      Description
      By Class in separate transactions
      The CIs are merged one class at a time. Only after the CIs in a class are merged, the CIs from the next class are merged. Tip: Use this option to keep the reconciliation performance high.
      Related CIs in one transaction
      All CIs are merged at the same time.
      Related CIs in separate transactions
      Only the CIs that belong in a hierarchy are merged at a time.
    6. (Optional) Select Include Unchanged CIs.

  8. To add Purge activity, click Add Activity > Purge and perform the following steps:
    Steps to add Purge activity
    1. (Optional) Specify a name for the activity and configure the following parameters:
      • Namespace
      • Sequence
      • Status
      • Continue on Error
    2. Select Source dataset from the list.
    3. (Optional) In Qualification, add a qualification set to select the classes and instances to be purged.
      1. Clear the Use all classes and instances checkbox to restrict the Purge activity by using a qualification set.
      2. Click Select qualification ruleset to select a qualification set.
    4. In Purge Instances, select the desired option:
      • Identified and unidentified - Both identified and unidentified instances are purged.
      • Identified - Only identified instances are purged.
      • Unidentified - Only unidentified instances are purged.
    5. (Optional) To verify the instances that are marked as deleted in the target dataset, select Verify Soft Deleted in Target Dataset.
      Verify soft deleted.jpg
  9. (Optional) Select a schedule for the job run frequency.
  10. Click Save.
  11. (Optional) To run the job immediately, open the job from All Job Run Activities and click Start Job.