This documentation supports the 18.08 version of BMC Atrium Core.

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

Creating precedence sets and associations for reconciliation merge activities

A precedence set defines the precedence value for a dataset in a merge activity. Each source dataset is paired with one, and that precedence set serves as the default precedence value for all classes and attributes in that dataset. The highest value among all source datasets determines the data that is written to the target dataset. 


Within a precedence set, you can specify individual precedences for specific classes or attributes, assigning them a precedence value higher or lower than that of the dataset. This prevents one source dataset from providing all the data in a merge. Class-level precedence values apply to all attributes of the class. 

When the merge activity runs, it specifies the precedence value at the most granular level used for a given attribute.

Best practice

  • Use the highest class level applicable to take advantage of inheritance.
  • A precedence set can be paired with different datasets in different activities. Likewise, a given dataset can be paired with different precedence association sets in different activities. Therefore, design your precedence sets for flexibility. You need fewer of them.
Precedence values do not apply to the CMDB internal core attributes.

For example:

AssignedTo, AttributeDataSourceList, ClassId, CMDBRowLevelSecurity, CMDBWriteSecurity, CreateDate, DatasetId, InstanceId, LastModifiedBy, ModifiedDate, NormalizationStatus, ReconciliationIdentity, ReconciliationMergeStatus, Submitter are some CMDB internal core attributes and precedence values are not applicable for these attributes. 

Before you begin

Before creating a precedence set, check if you can use the standard identification and precedence rules for reconciliation jobs shipped with the product.

If you can use the standard rules for merge precedence, you do not need to create a precedence set. 

To create a precedence set for a reconciliation merge activity

  1. Open the Reconciliation console.
  2. In the Reconciliation console, select a job with a merge activity.
    The Administrative Information tab lists the activities and you can confirm whether a merge activity exists in the job.
  3. Click Edit Job .
    The job editor opens.
  4. Select the merge activity and click Edit Activity.


    The Precedence area appears.
  5. In the Precedence area, click View/Edit Precedence Set 

  6. In the New/Edit Precedence Set area, enter the following required precedence set information.

    Name

    Type a unique name for the precedence set. The name cannot contain any characters that are not allowed in file names for the operating system of your server. For example, on a Windows server, your job name cannot contain the following characters: \ / : * ? " < > |.

    Namespace

    Select a namespace. Only classes in the selected namespaces can participate in the activity. For more information, see Dynamic dataset and qualification values in event-driven reconciliation jobs.

    Defer If Null

    Define how to handle empty, or NULL, attributes in the dataset associated with the precedence set. The Defer if Null setting at the precedence set level is overridden by the same setting in any precedences defined for the set.

    Note: This field is visible for custom jobs and not for standard jobs.


     
    Checked — If the value of an attribute in this dataset is NULL and this precedence value is the highest, defer to the dataset with the next highest precedence value. Do not write NULL to the production dataset.

    Unchecked — Apply the precedence value for this dataset regardless of whether an attribute value is NULL.

    Warning

    If used incorrectly, Defer if Null can cause instances that cannot be deleted.

    Append to Lists

    Set whether list values from all source datasets are appended to list-formatted character attributes in the production dataset. Duplicate entries are not appended to the list. A list-formatted attribute is a character attribute that is intended to hold a list of values according to a specified format. The Append to Lists setting at the precedence set level is overridden by the same setting in any precedences defined for the set.

    Checked — If this precedence set has the highest precedence value for a list-formatted character attribute in a merge activity, the list values from all source datasets are appended to the list in the target dataset. If some other set has the highest precedence value for the attribute, Append to Lists for that set determines whether values are appended.

    Unchecked — If this precedence set has the highest precedence value for a list-formatted character attribute in a merge activity, the list values from the source dataset paired with this set overwrite the list in the production dataset.

    Precedence Value

    Enter or select a value for the dataset that uses this precedence set. The weight is 0 to 1000, inclusive, with higher numbers meaning a higher priority. The precedence value is overridden by the value in any precedences defined for the set.

    Require Explicit Precedences

    Define whether to define precedences for all classes or attributes. Select this option to require explicit precedence entries for classes and attributes. You must add precedence rules for the classes and attributes. To apply this precedence set to all classes and attributes for which a precedence is not defined, clear this option.

  7. Click Add Rule.
  8. Enter the following required precedence rule information:

    Status

    Select Active. You can later disable the activity by changing this to Inactive.

    Class

    Select the class to which this precedence applies.

    Namespace

    Select a namespace. Only classes in the selected namespaces can participate in the activity. For more information, see Dynamic dataset and qualification values in event-driven reconciliation jobs.

    Attribute

    If the precedence is for an attribute, select it from the Attribute list.

    Precedence

    Type or select a value from 0 to 1000, inclusive. Data with higher numbers have a higher priority.
    These precedence values determine which data set, including the target if needed, supplies the data that is written to the target data set for each class and attribute. 

  9. Click OK to add the rule.
  10. Click Save to save the precedence set, and then click Close

    You can now relate the precedence set to a dataset by creating a precedence association.

Precedence associations for reconciliation merge activities

A precedence Association links a dataset with a precedence set and is reusable among merge activities.

Each merge activity is linked to one precedence Association that determines the precedence for each dataset that participates in the activity.

Note

If you have upgraded to version 8.1.00, consider the following notes.

  • You are no longer required to explicitly create precedence associations. These associations are handled intenally when you add precedence values to the datasets and their respective classes or attributes.
  • In the user Interface the concept of tiebreaker is not valid. You cannot define multiple precedence sets for the same dataset.
  • If you have upgraded from a previous version to version 8.1.00 or later If there is a tie for the highest precedence value between precedence Sets, the dataset and set with the higher Tiebreaker Value takes precedence in the User Interface. Other precedences sets with lower tiebreaker values do not get reflected in the new UI. They are ignored.

To create a precedence association

  1. In the precedence area of the merge activity, click the ... button.
  2. In the precedence Association Editor, enter a name for the association.
  3. Click Add Precedence Association.
  4.  From the Dataset list, select a source dataset.
  5.  From the Precedence Set list, select an existing precedence set.
  6. Select a Tiebreaker Value for this pairing within the set. 

    If there is a tie for the highest precedence value between precedence sets, the dataset and set with the higher Tiebreaker Value takes precedence in merges.
  7.  Click Save.
  8. Click Save, and then click Close.





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

Comments