Discovery use case

The goals of the Discovery use case are:

• Discover infrastructure and applications
• Granular configuration visibility
• Dependencies and relationships
• Near real-time updates

The following diagram shows the flow of information and the components involved in the use case. The steps that follow the diagram define the abbreviations used in the diagram.

This use case has the following steps:

1. BMC Atrium Discovery and Dependency Mapping (BMC Atrium Discovery, or ADDM) runs against all infrastructure components that are tracked in BMC Atrium CMDB. Clients (desktops, laptops, and mobile devices) are not included in the scope of this use case.
2. BMC Atrium Discovery pushes discovered information into an import dataset in BMC Atrium CMDB either when the information is discovered or as part of a scheduled export. The information is then processed by the Reconciliation Engine into the production dataset.
3. Service relationships are pulled from BMC Atrium CMDB into other BMC products, including BMC Server Automation (BSA), BMC Network Automation (BNA), BMC ProactiveNet Performance Management (BPPM), and the BMC Capacity Management solutions (BMC Capacity Management [CM] and Capacity Management Essentials [CME]), which can also extract relationships to Application, Location and Organization CI classes. The extracted information includes the relevant views of the service model so that these products can perform service-aware functions.

Discovery is the responsibility of BMC Atrium Discovery.

Customers using BMC Server Automation (BSA) must run the BMC Server Automation integration to BMC Atrium CMDB in order to synchronize them and allow BMC Server Automation to extract the service model from the BMC Atrium CMDB.

1. BMC Server Automation runs Component Discovery on an enrolled virtual machine (VM).
2. This information is extracted from BMC Server Automation by the ETL process of BMC BladeLogic Decision Support for Server Automation and pushed into the BMC Server Automation import dataset in the BMC Atrium CMDB. It is then processed by the Reconciliation Engine into the production dataset.