This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

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

Determining when to use standard reconciliation jobs and rules

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

BMC recommends that you start with a Standard Identification & Merge Job and customize the job or rules as needed. Unless you need different identification or precedence (merge) rules, you can use a Standard Identification & Merge Job and modify the activity options while using the standard rules.

  • If you have custom classes or attributes, you can modify the standard identify and precedence rules, and use a Standard Identification & Merge Job.
  • You can create and modify a Standard Identification & Merge Job that uses the standard rules for the following customizations:
    • If you need to change the production dataset 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 datasets in a merge activity
    • If you need to change the Include Unchanged CIs option or the Merge Order option in a merge activity
  • If you have one dataset that needs to have different identify or precedence rules, first, see if you can modify the standard identify or precedence (merge) rules without affecting the existing rules. If you cannot, then you might have to create a custom job, disable the standard rules, and create custom identify or precedence rules.

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

    For identification, you cannot specify a rule for a particular dataset, but you can check if adding an attribute at a lower priority can address the needs of a specific dataset. For example, if Calbro knows that for the CALBRO.APPS dataset, the TokenID, Name, and SerialNumber attributes are not sufficient to identify some instances. Calbro can add the custom CalbroID attribute that identifies those instances in that dataset. By setting it to a priority of 3, the default rules work for most datasets, but for CALBRO.APPS, after the priority 1 and 2 attributes fail to identify instances, the Reconciliation Engine uses the CalbroID attribute.
Was this page helpful? Yes No Submitting... Thank you

Comments