Reconciliation Engine enhancements in version 8.1.00
BMC Atrium Core 8.1.00 includes the following enhancements for the Reconciliation Engine:
For information about issues corrected in this release, see Known and corrected issues.
Standard Rules Editor and precedence set Editor user interfaces enhanced for better usability
The Precedence rules tab present in the Standard Rules Editor has been enhanced for better usability and improved interaction. The enhanced view is similar to a spreadsheet view, where you can see all the datasets in a grid and the corresponding attributes and classes in the Precedence Object column.
As a CMDB administrator you can choose to add/remove the datasets displayed in the columns using the Add or Remove Datasets from the Column icon at the right. You can also filter classes and attributes in the Precedence Object column using the search field above the column. The grid based UI allows you to see the precedence rules applied for a given attribute or class across all datasets at a glance.
All interactions for a rule are done through the cells in the grid. To set or edit a precedence rule for a certain class or attribute, you should navigate to the relevant cell and double-click to enter or edit data. You can use the slider to select the numeric value you want to enter.
The procedure to create a precedence Set for a reconciliation Merge activity is also simplified. The user interface to create or update precedence set is now enhanced to display the precedence rules and the related datasets in a grid format.
To view the procedure to add or edit standard rules, see Configuring standard precedence rules for reconciliation.
To view the procedure to view or edit existing precedence sets or to create new precedence sets see, Defining a Precedence Association Set for reconciliation Merge activities.
Enhanced Precedence Set User Interface
Changes implemented in indexes to enhance performance
An index (InstanceId; ClassId; DatasetId; ReconciliationIdentity; NormalizationStatus; RequestId) was removed from the BMC.CORE:BMC_BaseRelationship and the BMC.CORE:BMC_BaseElement forms in BMC Atrium CMDB. Two new indexes (ADDMIntegrationId; DatasetId and TokenId; DatasetId) were added on the BMC.CORE:BMC_BaseElement form.
After implementing these changes in the indexes, the product saw a considerable performance improvement. These enhancements are available for fresh installation or the upgrade of the product. Any other customizations that you have made to the indexes are retained when upgrading to BMC Atrium Core 8.1.
Fail safe feature enhanced for improved monitoring of the reconciliation jobs
The Fail safe feature in the reconciliation engine monitors the progress of all the running jobs. This enhancement to the reconciliation engine automatically restarts a non-responding job. The job can be of any type - scheduled, continuous, or non continuous. The reconciliation engine restarts the job automatically after the job remains idle beyond the configured job idle time.
For more information, see Monitoring reconciliation jobs using the Fail safe feature.
Possible to uniquely identify the PartitionID attribute
In the Standard Rules Editor, in the Identification Rule tab navigate to the BMC_ComputerSystem class. The Priority 3 and Priority 5 rules are updated with PartitionId attribute. This change in the BMC_ComputerSystem class now allows you to uniquely identify the CIs for which the PartitionID attribute is populated. The PartitionId field was added to CDM for IBM LPARs
These new rules are available is for OOTB (Out of the box) jobs for fresh install and upgrade. These changes implemented enhance Reconciliation engine performance.
Configuring the process log file size
The Reconciliation engine log file size can now be controlled. In the Reconciliation Engine if the logging level is set to debug, all the logs are recorded in the arrecond.log log file. It is now possible to control this file size.
For more information, see Restricting the Reconciliation Engine log file size.
Compare activity report enhanced for better usability
The compare activity report is enhanced to allow you to search the CI name in the compare activity report. Earlier the CI name was not present in the activity report, which made it difficult to locate the common CIs between the two datasets compared. The instance ID string follows with the CI name.
For more information see, Viewing a compare activity report