Infrastructure Management deployment with BMC Atrium CMDB

Integrating Infrastructure Management with the 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 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 Atrium CMDB—By default, 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 Atrium CMDB to define the components for monitoring.

Related topics

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

Integrating Atrium Service Context with BMC TrueSight Infrastructure Management Open link

Integrating with Atrium CMDB to automatically detect business service impact relationships Open link  

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

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

PATROL Agent supports the distribution of service models across the nodes of an PATROL Agent 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 PATROL Agent Server in a multiple-server deployment was known as the Central Server. In 10.0, the Central Server has been replaced by the TrueSight 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 Open link and Use cases for centralized service models Open link .

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