IRM allows BMC CI's to be automatically mapped to IRM objects. This mapping is achieved via specific key identifier fields in both the CMDB and IRM, and results in Proxy objects that hold the linking information.
After the mapping is in place, the integration software can generate a URL link from the CI Object in Atrium to the corresponding IRM object, and vice versa, allowing convenient access to an object in the other system.
By connecting the IRM and Atrium CMDB, the following features and workflows are enabled:
The Atrium CMDB to IRM path enables Atrium users to select a CI Object and if it has a link to an IRM Object, to locate the IRM Object within the IRM application. As a result, this allows the Atrium users to view its physical layer data from IRM, such as:
Location within Building, Floor, or a Rack
Physical Dependencies based upon ports and connected cabling
Logical Circuits routed via the device
Ownership information
Contract Information
Full Product Specifications (images, dimensions, environmental data (heat, power, weight), ports and slots.
The IRM to Atrium CMDB path enables the IRM user to select an IRM object and if it has a link to an Atrium CI Object, to open the selected CI Object in the Atrium CMDB system. As a result, this allows the IRM users to view the logical and configured service relationships such as:
Related Hardware based upon physical network P2P links
Related hardware based upon direct hardware connections
Service Connections based upon logical configurations
Installed Software
Service Connections
Current Hardware Configurations (Disk, Memory, filesystems, etc)
Current Real-time network status.
The following sections cover specific details of some of these workflows, as well as many additional details and features of the BMC Atrium CMDB CIs and the IRM system relation.
The contents of 4.5.4.2. BMC Atrium CMDB Integration
