BMC Atrium Core 9.1

The BMC Atrium Core solution works with other BMC Atrium solutions to facilitate the alignment of your IT organization with business priorities. BMC Atrium Core provides tight integration across management tools used in your IT environment, saving your IT organization time and money. BMC Atrium Core includes the following component products. - BMC Atrium Configuration Management Database (BMC Atrium CMDB), which stores information about the configuration items (CIs) in your IT environment and the relationships between them. - BMC Atrium Integrator, which transfers data between an external datastore and BMC Atrium CMDB.

This release consolidates all the Hot Fixes delivered for BMC Atrium Core version 9.1 and later into a single service pack. New REST APIs are introduced as a part of Digital Enterprise Management initiative. Also, the Pentaho version is upgraded to 6.0.1.0.

This release consolidates all the Hot Fixes delivered for BMC Atrium Core version 9.1.02 into a single patch release. This patch release includes BMC Atrium CMDB and BMC Atrium User Interface related fixes.

This release consolidates all the Hotfixes delivered for BMC Atrium Core version 9.1 and later into a single patch.

The format of describing the component version is modified in order to have a fixed location to get the version information. Hereafter, the versioning of components is as follows:Version Number.Service Pack.Patch.Hotfix

Frequently asked questions

BMC Atrium CMDB Reconciliation Engine FAQs

What is Reconciliation Engine?

The Reconciliation Engine is a component installed with the BMC Atrium CMDB. The main function of the Reconciliation Engine is the creation of a production dataset that contains accurate data from all available sources. Data in the production dataset is then used by consuming applications.

Under what conditions should the OOTB configuration settings be changed?

You should consider changing the default configuration settings in the following scenarios:

If you are dealing with large volume of data, increase the value of the Definition Check Interval field.

If you need specific log details, ensure that you change the log level to Debug. (Change the default log value only when you need and reset it back to default log level when you are done). Additionally, set the Maximum Job Log File Size value to 50000 KB.

If the RE Job is not responding for a long period, set Job Idle Time value to the desired time other than the default value (0).

What are standard rules and when should standard rules be used?

Standard identification and precedence rules simplify the process of creating reconciliation jobs. Standard rules use defaults for Identify and Merge activities and automate the creation of reconciliation jobs.

The standard rules work with all classes in the Common Data Model (CDM) and BMC extensions. They identify each class using attributes that typically have unique values, and they merge based on precedence set for BMC datasets. Standard reconciliation jobs always use these standard rules, but you can also use standard rules when you create your own reconciliation job.

You must use standard rules:

When configuration items are published into the CMDB or when the data is pulled from the CMDB.

To uniquely identify attributes of the discovered configuration items.

A set of rules that are created as per your specific business requirements and are not part of the standard rules are termed as custom rules. You can use custom rules for CI classes.

The following is an example scenario in which you might want to create custom rules:

If you have extended the Common Data Model by adding a new attribute, which is specific to your requirement and which might not be populated by any discovery tool. You might want to define custom rules to identify your assets based on this attribute.

What are identification rules and precedence rules and how to define them?

Standard identification and precedence rules simplify the process of creating reconciliation jobs. A reconciliation job is provided with a standard rule sets of identification and precedence rules.

These standard rules work with all classes in the Common Data Model (CDM) and BMC extensions. They identify each class using attributes that typically have unique values, and they merge based on precedences set for BMC datasets. Standard reconciliation jobs always use these standard rules, but you can also use them when you create a custom reconciliation job.

Do not delete datasets manually. You must also need to clean up dataset references from Reconciliation Engine, Normalization Engine etc

How to use qualifications in RE activity?

For most reconciliation activities, you can specify a qualification set for the purpose of restricting the instances that participate in an activity. Qualification sets, which are reusable between activities, are qualification rules that each select certain attribute values. Any instance that matches at least one qualification in a set can participate in an activity that specifies the qualification set.

For example, you might create a qualification set that selects instances that were discovered within the last 24 hours and have the domain "Frankfurt" if your company just opened a Frankfurt office and you are reconciling its discovered CIs for the first time.

As a best practice, BMC recommends that you must reconcile only those CIs that have been normalized or those that do not require normalization. To reconcile the appropriate CIs, enable the Process Normalized CIs Only option in the Job Editor.

How to reconcile manually created CIs?

To reconcile manually created CIs, perform the following steps:

Create a custom job.

Define the job for the classes in which you populate the data.

Identify the CIs.

Ensure that you adhere to the identification rules for the discovered jobs so that your CI matches with the discovered CIs.

Ensure that you populate at least those columns/attributes correctly that are defined in the identification rules (This helps in correct identification of the CI with the existing CI)

Set a lower precedence value for the manual dataset, but set a highest precedence to the manually edited columns/attributes of the dataset.

What are the possible causes of a partial merge? What do I do if CIs merge partially?

CIs are partially merged when the merge process fails due to data issues.

See the following flowchart that explains the checks to be performed if the CIs are partially merged:

Run Reconciliation Engine's Identification activity across multiple datasets. For example, open the BMC.CORE:BaseElement form and enter the RE ID value and search. If a CI having the same RE ID is found in multiple datasets, it means that the same CI exists in those datasets.

Was this page helpful? YesNoSubmitting...What is wrong with this page?ConfusingMissing screenshots, graphicsMissing technical detailsNeeds a videoNot correctNot the information I expectedYour feedback:

The current CDM Diagram contains a minor error in the "BMC_BaseElement"."ReconciliationIdentificationError" is written with some unrecognized characterlooking like a checked box instead of the substring "fi".

You may want to fix this as part of the next planned update.

Mar 09, 2017 10:21

Anagha Deshpande

Hello Marco,

Thanks for bringing this to our notice. I will work with SME and will upload the corrected diagram.