Page tree

Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Integrating Infrastructure Management with the BMC Atrium CMDB has the following benefits:

  • Provides more effective probable cause analysis—Infrastructure Management leverages the service relationship information from the configuration items (CIs) in BMC Atrium CMDB for the service model components that you are monitoring in Infrastructure Management to produce better results for probable cause analysis. 
  • Keeps the service model components of Infrastructure Management synchronized with the service model components stored in the BMC Atrium CMDB—By default, BMC Atrium CMDB automatically publishes service model components to the cell. 
  • Faster deployment of Infrastructure Management—Instead of manually configuring CIs in Infrastructure Management, you can import CIs from BMC Atrium CMDB to define the components for monitoring.

The following diagram illustrates the components of an Infrastructure Management deployment with BMC Atrium CMDB.

To enable the functionality provided by these components, you must install the BMC CMDB Extensions, which installs BMC Impact Model Designer.

Infrastructure Management supports distribution of service models across the nodes of a Infrastructure Management enterprise environment. You implement distributed service models when the number of CIs in a service model exceeds the maximum limit of CIs allowed in a single server. For information about sizing a deployment, see Sizing charts and guidelines for event and impact management.


In previous releases, the parent Infrastructure Management Server in a multiple-server deployment was known as the Central Server. In 10.0, the Central Server has been replaced by the Presentation Server for most deployments. A Central Server is still required for Distributed service models. The Central Server acts as a single point of entry for users and provides a common point to access service models. For more information, see Distributed service models and Use cases for centralized service models.

Related topics

Using the BMC Atrium CMDB as a source of service model data

Integrating BMC Atrium Service Context with BMC TrueSight Infrastructure Management

Integrating BMC Atrium CMDB with Infrastructure Management

Integrating with BMC Application Problem Resolution

Integrating with BMC Remedy Service Desk

Benefits of integrating BMC Change Management with Infrastructure Management

Integrating with BMC Application Problem Resolution