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.

BMC Atrium Core architecture and features

This section describes how the components in BMC Atrium Core integrate with each other and other applications to form a solution. This architecture is shown in the following figure. Other features and applications such as federation, web services, and the service oriented architecture are also described.

The BMC Atrium Configuration Management Database (BMC Atrium CMDB) provides the features that you need to implement a configuration management database (CMDB) in your environment. Any application that is integrated with BMC Atrium CMDB (for example, a data provider like BMC Atrium Discovery and Dependency Mapping or a data consumer like BMC Asset Management) can access the data from a centralized database.

BMC Atrium Core architecture

The following points explain the architecture:

  • At the center of BMC Atrium Core is BMC Atrium CMDB. BMC Atrium CMDB uses a federated data model, featuring a centralized database linked to other data stores, to share configuration data without the high setup and maintenance costs associated with a pure centralized approach.
  • The data inside BMC Atrium CMDB consists of configuration items (CIs) and the relationships among them. A CI is a physical, logical, or conceptual entity that is part of your environment and has configurable attributes.
  • Each CI or relationship is stored in a particular dataset within BMC Atrium CMDB. Data from each source or discovery tool is organized into datasets, which are then reconciled so that one production dataset represents your environment. A dataset can store data from a particular provider, a snapshot of data at a particular time, or any other set you want to create.

    The Sandbox dataset is an overlay dataset for the BMC Asset dataset that allows you to make changes in a separate partition without changing the production data and without duplicating the entire dataset. The Sandbox functions as a control mechanism so that BMC Atrium CMDB is not overloaded with unintended data when multiple sources update the BMC Atrium CMDB.
  • When CIs and its CI Relationships are added (manually, imported, automation, etc.) into the BMC Atrium CMDB, each entry is assigned to a particular dataset identifier. This dataset identifier defines the specific source of information (data provider) that provided the CIs, its attribute data, and relationship connections.
    For example, CIs and its relationships discovered from BMC Atrium Discovery and Dependency Mapping have BMC.ADDM as the dataset identifier. When the CI information of the discovered CIs is reconciled against other dataset identifiers, it is stored into a Golden dataset identifier of BMC.ASSET, thus allowing data consumers to access the trusted and most accurate data.

    In addition, the Sandbox dataset identifier represents an overlay dataset for the BMC.ASSET dataset identifier, which allows CMDB managers to define comparison requirements against the Production (BMC.ASSET) dataset identifier before the changes are incorporated into the CI record. This allows Change Managers to be notified of changes made to a CI, thus giving them the opportunity to ensure a Change Request was submitted and approved to support the modification.
  • The Normalization Engine makes sure that data from different data providers is consistent in BMC Atrium CMDB. After data is normalized before or after it is created in a dataset, it can be reconciled and saved to the BMC Atrium CMDB production dataset.


    BMC recommends that you normalize data before reconciliation.

  • The Reconciliation Engine merges data from multiple import datasets into the BMC Asset dataset. This consolidated view of your data is the production dataset that data consumers should use and on which you should base business decisions. The Reconciliation Engine also performs tasks such as deleting or purging records on a scheduled basis, comparing data for reporting or for Remedy AR System workflow triggers, and copying datasets into other datasets to protect the data.
    BMC Asset Management displays data from the BMC Asset dataset by default. If you manually edit data using BMC Asset Management, you should save those changes to the BMC.ASSET.SANDBOX dataset rather than writing them directly to the BMC Asset dataset, thereby enabling the changes to be reconciled with those from all active import datasets.

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