This documentation applies to the 8.1 version of BMC Atrium Core, which is in "End of Version Support." You will not be able to leave comments.

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

Planning to use federated data

Federated data is data stored outside BMC Atrium Configuration Management Database (BMC Atrium CMDB) but linked to configuration items (CIs) so that it is accessible through BMC Atrium CMDB. The most common types of federated data are related information and detailed attributes.

Related information is information about a CI that does not itself qualify as a CI and therefore should not be stored in a CMDB. Detailed attributes are attributes of CIs stored in BMC Atrium CMDB, but they are attributes that are not important enough to track at the level of a CMDB.

In BMC Atrium CMDB, not only can you view federated data, you can retrieve that data for use by a consuming application as if it were part of BMC Atrium CMDB. This feature enables you to access outside data from central CMDB repository and lets you use your existing data store infrastructure.

The following figure illustrates both types for a BMC_ComputerSystem instance named Computer A. The instance can be linked to incident records about Computer A, which are related information, and also linked to discovered attributes of Computer A that were not imported into BMC Atrium CMDB.

Federated data


Federated data is not bidirectional. BMC Atrium CMDB can establish links only from its own data to an external source, not from the external source to itself.

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.