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

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


BMC Atrium Core 9.1.04

All versions
BMC Atrium Core includes the BMC Configuration Management Database (BMC CMDB) and BMC Atrium Integrator. Use BMC CMDB to store and manage the configuration items (CIs) that represent your IT environment. Use BMC Atrium Integrator to transfer data between an external datastore and BMC CMDB.

Release notes and notices
updated 21 Dec
This section provides information about what is new or changed in this space, including urgent issues, documentation updates, service packs, and patches.


To stay informed of changes to this space, place a watch on this page.




February 28, 20189.1.04.002: Patch 2 for version 9.1.04 This patch is offered as a deployable package. It consolidates all the Hot Fixes delivered for BMC Atrium Core version 9.1.04 into a single patch release. This patch also includes REST API implementation for notification engine that is used for integrating any external product, such as TrueSight Operation Management
December 05, 20179.1.04

This release provides an all-new BMC Atrium CMDB user interface. The new dashboard is persona-based for the Configuration Manager and includes the following highlights: Health metrics to know the integrity and completeness of the production data sets, a Data Flow section that provides easy access of data from collection to consumption, a consolidated configuration console for settings, and the walkthroughs widget that provides real-time interactive steps to perform tasks.

Related topics

Known and corrected issues

Support information

BMC Remedy ITSM Suite components and installers



As an end user, access and navigate the CMDB user interface and Atrium Integrator.



As a developer or application programmer, develop interfaces and toolkits and customize BMC CMDB.

Managing the Common Data Model


Information and best practices for managing the Common Data Model.



As an administrator, configure the core CMDB components and archive the CMDB data, configure BMC Atrium Core Web Services, and manage the Product Catalog.



As an administrator, set up integrations with other BMC products or third-party software.



Resolve common issues or errors, review logs, or contact Support.



(On-premises only) Plan an installation or upgrade based on recommended deployment architecture, best practices, sizing, and system requirements.



(On-premises only) Install and perform initial system configuration.



(On-premises only) Upgrade based on the latest system requirements and software.

PDFs and videos


The following table lists topics that contain videos that supplement or replace the text-based documentation.

These videos are valid for BMC Atrium Core version 9.1.04.

TopicDuration (in minutes)Description
CMDB Overview4:42

This video provides an overview of the features implemented in the CMDB Version 9.1.04 release.

CMDB Dashboard7:55

This video takes you on a quick tour and familiarizes you with the new CMDB dashboard components.

CMDB Datasources5:39

This video provides an overview of the new Datasources component in the dashboard.

CMDB Normalization6:19

This video provides an overview of the Normalization component in the dashboard.

CMDB Reconciliation7:11

This video provides an overview of the Reconciliation component in the dashboard.


FAQs and additional resources

This topic provides information that supplements the BMC CMDB 9.1.04 documentation. It contains the following sections:

Frequently asked questions

This section provides answers to frequently asked questions (FAQs) about BMC CMDB components.

BMC CMDB Reconciliation Engine FAQs

 What is Reconciliation Engine?

Reconciliation Engine is a component installed with the BMC 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.

For more information, see the following resources:

 What should I do to prevent errors that might occur when running Reconciliation Engine jobs?

Before you run a Reconciliation Engine (RE) job, perform the following:

  • Perform CDM metadata diagnostics - Run the CDMChecker utility to:
  • Perform data diagnostics
  • Perform Reconciliation Engine-specific data diagnostics
  • Perform manual checks for RE jobs
    • Make sure that all the classes and attributes used in standard or custom rules of all the RE jobs exist in your CDM data model. If a certain job is imported in your CDM, the job might fail.
    • Make sure that the data sets (source, target and precedence data set) referred in all the RE jobs also exist in the BMC_Dataset class.
  • Check whether indexes are set
    • During upgrade, for optimal RE performance, ensure that the out-of-the-box indexes set up on BMC.CORE:BMC_BaseElement and BMC.Core:BMC_BaseRelationship forms.Discrepancies, if any, are logged in the Atrium Installer log file. The following image displays an example message:

 What are the best practices that need to be followed before starting reconciliation activity?

Watch the video on Reconciliation Engine best practices:

Configure recommended settings

Ensure that the System-level settings and Job-level settings are configured as per the recommendations. See the following images for recommended settings:

System-level settings

Job-level settings

For more information, see  Configuring Reconciliation Engine system parameters .

 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.
 What are custom rules and when should custom rules be used?

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.

For more information about using custom rules, see Creating an identification ruleset for reconciliation.

 What are identification rules and precedence rules and how do I 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.

For more information, see Standard identification and precedence rules for reconciliation jobs.

 How do I define precedence order?

Watch the following video:

For more information, see Configuring standard precedence rules for reconciliation .

 What should I not do with my CMDB data?
  • Do not set a Reconciliation Engine ID manually in any dataset.
  • Do not manually delete data, which is marked as soft delete.
  • Do not delete datasets manually. You must also need to clean up dataset references from Reconciliation Engine, Normalization Engine etc.
 How should I use qualifications in Reconciliation Engine 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.

 What is a data analyzer tool in CMDB?

The CMDB Data Analyzer is a collection of tools that enable you to perform data analysis and also identify  data inconsistencies  in any CMDB dataset.

For more information, see  Using CMDB Data Analyzer to Investigate CMDB Data Issues .

 What does reconcile only normalized CIs mean?

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 do I reconcile manually created CIs?

To reconcile manually created CIs, perform the following steps:

  1. Create a custom job.
  2. Define the job for the classes in which you populate the data.
  3. Identify the CIs. 
    1. Ensure that you adhere to the identification rules for the discovered jobs so that your CI matches with the discovered CIs.
    2. 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)
  4. 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:

 How do I find duplicate CIs in the same dataset?

 Run the CMDB Data Analyzer utility to find duplicate CIs. See  Using CMDB Data Analyzer to Investigate CMDB Data Issues .

 How do I find same CI in multiple datasets?

Run Reconciliation Engine's (RE) 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.

 How do I find orphan CIs?

Run the CMDB Data Analyzer utility to find orphan CIs. See  Using CMDB Data Analyzer to Investigate CMDB Data Issues .

 What are the most common failures in RE and why?

The following table lists the common RE issues and provides access to relevant resources and workaround to these issues.



Duplicate CIs in discovery/source datasets. This error message is logged in the RE Job log.

See Reconciliation Engine multiple CI match issues.

ARERR[120092] The dataset ID and Reconciliation Identity combination is not unique.

  • Check the instance or data of the source dataset
  • Check whether the instance is duplicate
  • Check if your identification rules are correct (by using multiple attributes)

Multiple instances found in target dataset.

This error message is logged in the RE Job log.

  • Check if your identification rules are correct
  • Check the instances or duplicate data in the target dataset

ARERR[101049] Dataset <> does not exist.

Aborting... Activity ended with error.

This error occurs when you delete or rename any dataset and it does not get updated on all required places such as precedence sets etc.

Perform the following:

  1. Check all existing precedence sets and do a cleanup of dataset in question.
  2. Create a dataset with the same name which RE is looking for
Cannot find the endpoint of relationship.

This error occurs if you manually modify a CI and fail to modify its relationship, causing data integrity issues.

For more information, see Reconciliation Engine merge activity issues.
 How to migrate RE jobs from one computer to another?

To migrate the RE jobs, you must:

  1. Export the RE job data using the Reconciliation Console. See Exporting reconciliation definitions.
  2. Import the ARX data using BMC Remedy Data Import tool. See   Enabling the Data Import Utility  in the BMC Remedy AR System online documentation.
 What to do if RE process terminates or is unresponsive?

The Reconciliation Engine process terminates because:

  • The AR System server or database is busy and is unable to process the requests coming from RE.
  • The AR System server is either not responding or not reachable.

In the above scenarios, RE awaits for a response from the AR System server and then terminates itself.

For more information, see the Knowledge Article.

 The scheduled RE jobs are not running or are getting delayed. What do I do?

Perform the following:

  • Check whether the job schedule is deleted or modified.
  • Check whether the Application Pending form has an entry for that job.
    • If there is no entry for that job, enable the AR API, SQL and Filter logs.
    • If the entry exists, check the AR Dispatcher log.
  • Check whether RE is registered with the AR Dispatcher.
  • Check the number of entries in the Application Pending form.
    • If there are many entries in the form and if you do not need them, delete those entries from the form.
  • Check whether the RE job entry is in the Queued state in the RE job run. If yes, delete the entry from the Queued state.
  • If you are using RE in a server group environment, ensure that the Reconciliation-Engine-Suspended flag is set to False (F). Note: You cannot set this value manually.
 Changes to RE job, rules, or qualification sets are not reflecting in the Atrium Console. What do I do?

Perform the following:

  1. Enable server-side logs.
    1. Edit the file located in the <AR_Installation_Home>\midtier\WEB-INF\classes folder. Add the following lines:

      log4j.rootLogger=DEBUG, atrium
        log4j.appender.atrium.File=C:/Program Files/BMC Software/ARSystem/midtier/logs/atrium-ui.log
        log4j.appender.atrium.layout.ConversionPattern==%d[%t] %-5p %C{1} - %m%n

      and DEBUG DEBUG

    2. (BMC Atrium Core 7.6.04 or earlier): Edit the <AR_HOME>\ARSystem\midtier\WEB-INF\flex\services-config.xml file.

      (BMC Atrium Core 8.0 or later): Edit the <AR_HOME>\ARSystem\midtier\WEB-INF\AtriumWidget\flex\services-config.xml file.

      In the services-config.xml file, modify the logging level from Warn to Debug. 

      For example, change the following line:
      <target class="flex.messaging.log.ConsoleTarget" level="WARN">
      <target class="flex.messaging.log.ConsoleTarget" level=“DEBUG">
  2. Enable client-side logs.
    For information about enabling client-side logs, see BMC Atrium Core Console client-side logging.
 How to create a RE job for multiple source datasets?

 See this  knowledge article .

Additional resources from BMC

The following hyperlinks provide information outside of the BMC Atrium Core online documentation that you might find helpful:

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


  1. Thomas Hammer

    Hi, did you change the type of documentation provided for a specific version? Are you only publishing new and changed features and functions in new versions? Starting with 9.1.04 as it seems not the full documentation is available under one hood anymore. 9.1 up to 9.1.03 seems to be the last section where all topics are covered. The space banner claims: This space contains documentation for version 9.1 to 9.1 Service Pack 3 and its patches. The documentation for version 9.1.04 and its patches is available here. But following the link you will miss many chapters of the documentation. Only one example: Federated data is not included in 9.1.04 nor 18.05 doc pages. Did BMC announce this change in documentation structure and I've missed it? Then I'm sorry for asking. Please may I ask you to provide a link to that announcement? Thank you.

    Jul 03, 2018 02:48
    1. Kanchana Iyer

      Dear Thomas,

      Thanks for your question. Starting 9.1.04, the CMDB has started building a new User Interface in a phased manner. This new space contains documentation for only the part of the UI that is new and refers to the older space where the UI hasn’t changed yet. When the new UI fully replaces the old UI, the documentation in this space will also cover all the topics from the older spaces. We apologize for the inconvenience caused to you.

      I hope this helps.

      Thanks and regards,


      Jul 24, 2018 01:10