Source data organization at Calbro Services
Calbro Services maintains its discovery data in CSV files that store information about all the hardware components in its environment. There are separate CSV files for computers, processors, disk drives, memory, and so on.
Mapping Calbro source data to BMC Atrium CMDB
The organization of the discovery data for computers and disk drives is shown in the following figure.
Organization of the computer and disk drive data
The records in the Computer CSV correspond to instances of the
BMC_ComputerSystem class in BMC Atrium CMDB. The records in the Disk Drive CSV correspond to instances of the
BMC_DiskDrive class in BMC Atrium CMDB.
Mapping Calbro relationship classes
Much of the value of BMC Atrium CMDB comes from the ability to store information about the relationships between configuration items (CIs), not just information about the CIs themselves.
Each record in the Disk Drive CSV contains the name of its corresponding computer in the AssociatedComputer column. This relationship associates a specific instance of a disk drive in the external database with a specific instance of a computer. For example, in the following figure, disk 1520 in the Disk Drive CSV is associated with computer vm2-w4-dev01 in the Computer CSV.
Because each disk drive is associated with a computer, you can select a relationship that associates a particular instance of
BMC_DiskDrive with a particular instance of
BMC_ComputerSystem. In this case, the AssociatedComputer attribute in the
BMC_DiskDrive class and the HostName attribute in the
BMC_ComputerSystem class contain the data necessary to create the relationship.
Each relationship class in BMC Atrium CMDB defines one CI class as the source member of the relationship and another CI class as the destinationmember of the relationship. In this case, BMC_ComputerSystem is the source (primary) member and
BMC_DiskDrive is the destination (secondary) member of the
BMC_HostedSystemComponents relationship class. For more information about relationship classes, see Relationship classes in the Common Data Model.
The transformations that bring data from the external data store into the CI classes (in this case,
BMC_ComputerSystem ) must finish before the transformation for the relationship class can run, because that transformation needs the instance IDs of the related CIs for their relationship instance. The wizard schedules the transformations in this order automatically.
The relationship between computer systems and disk drives at Calbro Services is stored within the source CSVs, as shown in the following figure. The following figure shows how data from the external database is transferred into BMC Atrium CMDB to create CIs, and then how a relationship class instance is created based on attributes in the CI classes.
Creating relationships based on attributes in both CI classes
BMC_DiskDrive instance, a match between its AssociatedComputer value and the Name value in a
BMC_ComputerSystem instance causes the creation of a
BMC_HostedSystemComponents relationship between the two CIs.
The instance IDs of these member CIs are stored in the relationship instance as
Source.InstanceId for the
BMC_ComputerSystem instance and
Destination.InstanceId for the