Understanding the integration data mappings

A data mapping in BMC Atrium Integrator defines how data in the BMC BladeLogic Decision Support for Server Automation database corresponds to data in BMC Atrium CMDB and which actions need to taken when data is transferred between them. That is, data mappings explicitly define the mapping between columns in the BMC BladeLogic Decision Support for Server Automation database and the attributes of a BMC Atrium CMDB CI or relationship class.

When you install BMC BladeLogic Atrium Integration, the data mappings required to transfer data are created automatically in the BMC Atrium Integrator. 

BMC BladeLogic Atrium Integration creates the following data mappings:

• BL_DEL_BIOSELEMENT
• BL_DEL_COMPUTERSYSTEM
• BL_DEL_DISKDRIVE
• BL_DEL_IPENDPOINT
• BL_DEL_LOCALFILESYSTEM
• BL_DEL_MEMORY
• BL_DEL_NETWORKPORT
• BL_DEL_OPERATINGSYSTEM
• BL_DEL_PROCESSOR
• BL_DEL_VIRTUALSYSTEM
• BL_LOAD_SRVR_PROPS
• BL_PULL_BIOSELEMENT
• BL_PULL_COMPUTERSYS_CO
• BL_PULL_COMPUTERSYSTEM
• BL_PULL_DISKDRIVE
• BL_PULL_IPENDPOINT
• BL_PULL_LOCALFILESYSTEM
• BL_PULL_MEMORY
• BL_PULL_NETWORKPORT
• BL_PULL_OPERATINGSYSTEM
• BL_PULL_PROCESSOR
• BL_PULL_VIRTUALSYSTEM

BMC BladeLogic Atrium Integration creates the following relationship class mappings:

• BL_PULL_BIOSELEMENT_RELATIONSHIP
• BL_PULL_DISKDRIVE_RELATIONSHIP
• BL_PULL_IP_RELATIONSHIP
• BL_PULL_LOCALFILESYSTEM_RELATIONSHIP
• BL_PULL_MEMORY_RELATIONSHIP
• BL_PULL_NETWORK_RELATIONSHIP
• BL_PULL_OS_RELATIONSHIP
• BL_PULL_PROCESSOR_RELATIONSHIP
• BL_PULL_VIRTUALSYSTEM_RELATIONSHIP