CDM Mapping for Cloud

This topic provides information about mapping for cloud nodes. The CIs created are described in this topic.

Data models

Note

The default mapping works with CMDB versions 7.5, 7.6, and 7.6.03 and later. The data model in each is slightly different.

BMC_Impact relationships are not normally created with CMDB 7.6.03 and later, since the CMDB automatically maintains them itself. See the information about impact relationships for more details.

Click here for reference information on impact and the data models.

Different versions of the CMDB have subtly different data models. Syncmappings can support multiple data models with datamodel declarations. CMDB data models are assigned simple integer values:

Data model	CMDB versions	Effect
6	7.6.03 and later	HasImpact and ImpactDirection attributes are set as appropriate.
5	7.6.03 and later	Only to be used with legacy SIM version 7.4. BMC_Impact relationships with Name “ImpactOnly” are created.
4	7.6.03 and later	No impact details are set by BMC Discovery. They may be set by Impact Normalization in the CMDB.
3	7.6 before 7.6.03	BMC_Impact relationships with name “IMPACT” are created.
2	7.5	BMC_Impact relationships with name “IMPACT” are created.

BMC_CloudInstance (Provider)

The CloudProvider node is mapped to a BMC_CloudInstance CI with the following attributes:

Attribute	Details
`Name`	Cloud provider `name`
`ShortDescription`	Cloud provider `short_name`, or`name`
`Description`	Cloud provider `name`
`ManufacturerName`	Publisher comes from the `publishers` attribute in the metadata of the related cloud pattern. If no publishers are set, the default publisher is used where a default is specified in CMDB_SyncConfig.tpl.
`Model`	Cloud provider `code`
`TokenId`	Cloud provider `key`
`Company`	Cloud provider`company.`
`Category`	"`Cloud`"
`Type`	"`Cloud Provider`"
`Item`	"`Cloud Provider`"

BMC_CloudInstance relationships

Relationship

Name

Source

Destination

BMC_Component

CLOUDREGIONFORPROVIDER

BMC_CloudInstance(Provider)

Impacted

BMC_CloudInstance(Region)

BMC_CloudInstance (Region)

The CloudRegion node is also mapped to a BMC_CloudInstance CI. It has the following attributes:

Attribute	Details
`Name`	Cloud region `name`
`ShortDescription`	Cloud region `short_name`, or`name`
`Description`	A description of the form "Region name : Cloud account ID"
`ManufacturerName`	Publisher comes from the `publishers` attribute in the metadata of the related cloud pattern. If no publishers are set, the default publisher is used where a default is specified in CMDB_SyncConfig.tpl.
`Model`	Cloud region `code`
`TokenId`	Cloud region `key`
`CloudId`	Cloud region `id`
`Company`	Cloud region `company.`
`Category`	"`Cloud`"
`Type`	"`Cloud Provider`"
`Item`	"`Cloud Region`"

BMC_CloudInstance relationships

Relationship

Name

Source

Destination

BMC_Component

CLOUDSERVICEINREGION

BMC_CloudInstance
(Region)

BMC_CloudInstance(Service)

Impacted

BMC_CloudInstance (Service)

The CloudService node is also mapped to a BMC_CloudInstance CI. It has the following attributes:

Attribute	Details
`Name`	Cloud service `name`
`ShortDescription`	Cloud service `short_name`, or`name`
`Description`	A description of the form "Region name : Cloud account ID"
`ConsumedService`	Cloud service `type`
`LastScanDate`	Cloud service l`ast_update_success`
`ManufacturerName`	Publisher comes from the `publishers` attribute in the metadata of the related cloud pattern. If no publishers are set, the default publisher is used where a default is specified in CMDB_SyncConfig.tpl.
`Model`	Cloud service `code`
`TokenId`	Cloud service `key`
`CloudId`	Cloud service `id`
`Category`	"`Cloud`"
`Type`	"`Cloud Provider`"
`Item`	`Cloud service type`

BMC_CloudInstance (Provider)

BMC_Cluster

A cluster dependent on CloudService mapped to a BMC_Cluster CI. It has the following attributes:

Attribute	Details
`TokenId`	`TokenId` is of the form `"ADDM:%lb_service.key%"`.
`Name`	Cluster `name`.
`NameFormat`	"ClusterName"
`ManufacturerName`	Publisher comes from the `publishers` attribute in the metadata of the related cloud pattern. If no publishers are set, the default publisher is used where a default is specified in CMDB_SyncConfig.tpl.
`Model`	Cluster `type`.
`Description`	Cluster `name`.
`ShortDescription`	Cluster `name`.
`isCloud`	`Yes` if the service exists directly within a cloud; `null` if not.
`ComponentAliases`	Cluster `aliases`.
`CloudID`	Cluster unique cloud identifier (`cloud_id`).
`Company`	Cloud service `Company`.
`Category`	"Unknown".
`Type`	"Unknown".
`Item`	"BMC Discovered".

Relationship	Name	Source	Destination
`BMC_Dependency`	`CLOUDSERVICECLUSTER`	`BMC_CloudInstance` (Service)	`BMC_Cluster` Impacted

BMC_LogicalSystemComponent

The cloud LoadBalancerService is mapped to BMC_LogicalSystemComponent. It has the following attributes:

Attribute	Details
`TokenId`	`TokenId` is of the form `"ADDM:%lb_service.key%"`.
`Name`	Load balancer service `name` or Load balancer service `name : cloud service name` if the target is Remedyforce.
`ShortDescription`	Load balancer service `short_name`, or`name`
`Description`	Load balancer service `name`
`ManufacturerName`	Publisher comes from the `publishers` attribute in the metadata of the related cloud pattern. If no publishers are set, the default publisher is used where a default is specified in CMDB_SyncConfig.tpl.
`isCloud`	`Yes` if the service exists directly within a cloud; null if not
`Model`	Load balancer service `model`
`CloudID`	Load balancer service unique cloud identifier (`cloud_id`).
`Company`	Cloud service `Company`
`Category`	`"Network"`
`Type`	`"Service"`
`Item`	`"Load Balancer service"`

BMC_LogicalSystemComponent relationships

Relationship	Name	Source	Destination
`BMC_Dependency`	`LOADBALANCERSERVICE`	`BMC_CloudInstance`(Service)	`BMC_LogicalSystemComponent`Impacted

BMC_ResourcePool

The cloud LoadBalancerPool is mapped to BMC_ResourcePool. It has the following attributes:

Attribute	Details
`TokenId`	`TokenId` is of the form `"ADDM:%lb_pool.key%"`.
`Name`	Load balancer pool `name` or Load balancer pool `name : cloud service name` if the target is Remedyforce.
`ShortDescription`	Load balancer pool `short.name`
`Description`	Load balancer pool `name`
`ResourceType`	Other (0)
`Company`	Cloud service `Company`
`Category`	`"Network"`
`Type`	`"Service"`
`Item`	`"Load Balancer pool"`

BMC_ResourcePool relationships

Relationship	Name	Source	Destination
`BMC_Component`	`HOSTEDRESOURCEPOOL`	`BMC_CloudInstance`(Service)	`BMC_ResourcePool`
`BMC_Dependency`	`LOADBALANCERSERVICE`	`BMC_ResourcePool`(Service)	`BMC_LogicalSystemComponent`Impacted

BMC_AdminDomain (AdminCollection)

The cloud AdminCollection node is mapped to BMC_AdminDomain. It has the following attributes:

Attribute	Details
`Name`	Administrative collection `name` orAdministrative collection `name : cloud service name` if the target is Remedyforce.
`ShortDescription`	Administrative collection `short_name`, or`name`
`Description`	Administrative collection `name`
`ManufacturerName`	Publisher comes from the `publishers` attribute in the metadata of the related cloud pattern. If no publishers are set, the default publisher is used where a default is specified in CMDB_SyncConfig.tpl.
`Model`	Administrative collection `type`
`TokenId`	Administrative collection `key`
`CloudID`	Administrative collection unique cloud identifier (`cloud_id`).
`Company`	Cloud service `Company`
`Category`	`"Cloud"`
`Type`	`"Administrative Collection"`
`Item`	Administrative collection `name`

BMC_AdminDomain (AdminCollection) relationships

Relationship	Name	Source	Destination
`BMC_Dependency`	`CLOUDADMINCOLLECTION`	`BMC_CloudInstance`(Service)	`BMC_AdminDomain`
`BMC_Dependency`	`ADMINCOLLECTIONMEMBER`	`BMC_AdminDomain`	`BMC_BaseElement`

BMC_AdminDomain (CloudManagementGroup, NestedCloudManagementGroup, OwnedManagementGroup)

The cloud CloudManagementGroup, NestedCloudManagementGroup, and OwnedManagementGroup nodes are each mapped to BMC_AdminDomain. This mapping was updated in the November 2020 TKU. It has the following attributes:

Attribute	Details
`Name`	Management Group `name`
`ShortDescription`	Management Group `short_name` or `name`
`Description`	Management Group `name`
`ConsumedService`	Management Group `type`
`isCloud`	`Yes` if the service exists directly within a cloud; `null` if not.
`LastScanDate`	Cloud service l`ast_update_success`
`ManufacturerName`	Publisher comes from the `publishers` attribute in the metadata of the related cloud pattern. If no publishers are set, the default publisher is used where a default is specified in CMDB_SyncConfig.tpl.
`Model`	Management Group `type`
`SerialNumber`	Management Group id
`TokenId`	Management Group `cloud_id`
`CloudID`	Management Group `cloud_id`
`Company`	Cloud service `Company`
`Category`	"Cloud"
`Type`	"Cloud Management Group"
`Item`	Management Group type

BMC_AdminDomain (CloudManagementGroup) relationships

Relationship	Name	Source	Destination
`BMC_MemberOfCollection`	`CLOUDMANAGEMENTGROUPPROVIDER`	`BMC_CloudRegion`	`BMC_AdminDomain` (CloudManagementGroup) impacted
`BMC_Component`	`CLOUDMANAGEMENTGROUPHIERARCHY`	`BMC_AdminDomain`(parent CloudManagementGroup)	`BMC_CloudManagementGroup`(child CloudManagementGroup)
`BMC_MemberOfCollection`	`CLOUDMANAGEMENTGROUPOWNEDACCOUNT`	`BMC_AdminDomain`(owning CloudManagementGroup)	`BMC_AdminDomain`(owned CloudManagementGroup)

BMC_ConcreteCollection

The cloud Deployment node is mapped to BMC_ConcreteCollection. It has the following attributes:

Attribute	Details
`Name`	Deployment `name` or Deployment `name : cloud service name` if the target is Remedyforce.
`ShortDescription`	Deployment `short_name`, or`name`
`Description`	Deployment `name`
`Model`	Deployment `type`
`TokenId`	Deployment `key`
`CloudID`	Deployment unique cloud identifier (`cloud_id`).
`Company`	Cloud service `Company`
`Category`	`"Cloud"`
`Type`	`"Deployment"`
`Item`	Deployment `name`

BMC_ConcreteCollection relationships

Relationship	Name	Source	Destination
`BMC_Dependency`	`CLOUDDEPLOYMENT`	`BMC_CloudInstance`(Service)	`BMC_ConcreteCollection`
`BMC_Dependency`	`CLOUDDEPLOYMENT`	`BMC_Cluster`(Service)	`BMC_ConcreteCollection`
`BMC_Dependency`	`CLOUDDEPLOYMENT`	`BMC_Cluster`(Cloud)	`BMC_ConcreteCollection`
`BMC_Dependency`	`MEMBERINDEPLOYMENT`	`BMC_ConcreteCollection`	`BMC_BaseElement`

Mapping of VirtualMachine nodes, SoftwareInstance nodes, and contained Database nodes

Where VirtualMachine nodes, SoftwareInstance nodes, and contained Database nodes that are cloud-hosted are populated, it is done so using the same rules as for those on a Host node. The mapping rules are shown below:

BMC_VirtualSystemEnabler and virtualization

When a physical machine hosts one or more virtual machines, the BMC Helix Discovery model represents it as a number of Virtual Machine nodes related to the physical Host (BMC_ComputerSystem ) or Management software (BMC_SoftwareServer ), one Virtual Machine node per virtual host. A BMC_VirtualSystemEnabler CI is created for each VirtualMachine node.

Attribute	Details
key	The SoftwareInstance key, or for RuntimeEnvironments, the host_key/SoftwareInstance product / SoftwareInstance version
`Name`	VirtualMachine `name`
`ShortDescription`	VirtualMachine `short_name` or `name`
`Description`	VirtualMachine `name`
`BuildNumber`	VirtualMachine `build`
`EnablerType`	Enumeration representing the type of virtualization technology
`EndOfExtendedSupport`	End of Extended Support date.
`EndOfLife`	End of Life date.
`EndOfSecuritySupport`	End of Security Support date.
`EndOfSupport`	End of Support date.
`InstanceName`	`<type>:<hostname>:<DNS domain>:<instance name>` where `<type>` is the value of the BMC Helix Discovery type attribute from the corresponding SoftwareInstance or Database node, for example, “Microsoft SQL Server” or “Oracle Database”
`isCloud`	`Yes` if the virtual machine is known to be cloud hosted; null if not
`ManufacturerName`	Publisher.
`MarketVersion`	VirtualMachine `product_version`
`Model`	VirtualMachine `type`
`PatchNumber`	VirtualMachine `patch`
`ServicePack`	VirtualMachine `service_pack`
`TokenID`	Attribute that aids reconciliation of CIs populated by multiple data sources. `TokenId` is of the form "ADDM`:`hashedkey", where hashedkey is a hash of Software Instance key
`VersionNumber`	VirtualMachine `version`
`ComponentAliases`	VirtualMachine `cdm_component_aliases`
`Company`	Host Company
`Category`	"`Software`"
`Type`	"`Operating System Software`"
`Item`	"`Virtualization OS`"

Virtualization relationships

Relationship	Name	Source	Destination
`BMC_HostedSystemComponents`	`HOSTEDSYSTEMCOMPONENTS`	`BMC_ComputerSystem` (physical)	`BMC_VirtualSystemEnabler`Impacted
`BMC_Dependency`	`HOSTEDVIRTUALMACHINE`	`BMC_CloudInstance`	`BMC_VirtualSystemEnabler`Impacted
`BMC_Dependency`	`VIRTUALSYSTEMOS`	`BMC_VirtualSystemEnabler`	`BMC_ComputerSystem` (virtual host) `BMC_ComputerSystem` (virtual network device) `BMC_ComputerSystem` (virtual SNMP managed device) `BMC_ComputerSystem` (virtual storage system) Impacted
`BMC_VirtualSystemEnabler`	`VIRTUALSYSTEMOS`	`BMC_VirtualSystemEnabler`	`BMC_ComputerSystem` (virtual)

BMC_SoftwareServer and BMC_ApplicationSystem

Each SoftwareInstance in the BMC Helix Discovery model is mapped to either a BMC_SoftwareServer CI or a BMC_ApplicationSystem CI:

SoftwareInstance nodes with DDD triggers are directly running on a single host, and are mapped to BMC_SoftwareServer
SoftwareInstance nodes composed of other SoftwareInstance nodes are mapped to BMC_ApplicationSystem.

SoftwareInstance nodes are also mapped (in an indirect manner) to BMC_Product.

Except as noted, the attributes set are the same in BMC_SoftwareServer and BMC_ApplicationSystem.

Attribute	Details
key	The SoftwareInstance key, or for RuntimeEnvironments, the host_key/SoftwareInstance product / SoftwareInstance version
`TokenId`	Attribute that aids reconciliation of CIs populated by multiple data sources. `TokenId` is of the form "ADDM`:`hashedkey", where hashedkey is a hash of Software Instance key
`Name`	Software Instance `name`
`ShortDescription`	Software Instance `short_name` or Software Instance`name`
`Description`	Software Instance `name`
`BuildNumber`	Software Instance `build`
`EndOfExtendedSupport`	End of Extended Support date.
`EndOfLife`	End of Life date.
`EndOfSecuritySupport`	End of Security Support date.
`EndOfSupport`	End of Support date.
`InstanceName`	`<type>:<hostname>:<DNS domain>:<instance name>` where `<type>` is the value of the BMC Helix Discovery type attribute from the corresponding SoftwareInstance or Database node, for example, “Microsoft SQL Server” or “Oracle Database”
`isCloud`	`Yes` if the software instance is known to be cloud hosted; null if not
`ManufacturerName`	Publisher specified in the maintaining Pattern or on the Software Instance
`MarketVersion`	Software Instance `product_version`
`Model`	Software Instance `type`
`OtherSoftwareServerType`	Software Instance `type` (Only in `BMC_SoftwareServer`)
`PatchNumber`	Software Instance `patch`
`ServicePack`	Software Instance `service_pack`
`SoftwareServerType`	Enumeration representing the type of SoftwareServer. Often 0 meaning "Other". (Only in `BMC_SoftwareServer`)
`VersionNumber`	Software Instance `version`
`ComponentAliases`	Software Instance `cdm_component_aliases`
`CloudID`	Software Instance unique cloud identifier (`cloud_id`).
`Company`	Software Instance Company.
`Category`	"`Software`"
`Type`	"`Application`"
`Item`	Product category from the maintaining Pattern

Note

The Item attribute is populated from the Pattern that is maintaining the Software Instance. To obtain a list of all the possible Item values, perform the following query in the Discovery Generic Query page:

search Pattern show categories processwith countUnique(0)

BMC_SoftwareServer and BMC_ApplicationSystem relationships

As shown in the table, BMC_SoftwareServer and BMC_ApplicationSystem CIs can be related to each other with a BMC_Dependency relationship. This is mapped from both Dependency and Communication relationships between the SoftwareInstance nodes in the BMC Helix Discovery model.

BMC_SoftwareServer and BMC_ApplicationSystem CIs also have relationships to BMC_Product, shown in the Product relationships table.

Relationship	Name	Source	Destination
`BMC_Dependency`	`APPLICATIONSYSTEMCOMPUTER`	`BMC_ComputerSystem` (Host) `BMC_Cluster` `BMC_CloudInstance` `BMC_ComputerSystem` (Network Device)	`BMC_SoftwareServer`Impacted
`BMC_Component`	`APPLICATIONSYSTEMHIERARCHY`	`BMC_ApplicationSystem` (containing) Impacted	`BMC_SoftwareServer` (contained)
`BMC_Component`	`APPLICATIONSYSTEMHIERARCHY`	`BMC_SoftwareServer` (containing)	`BMC_SoftwareServer` (contained)
`BMC_Dependency`	`APPLICATIONSYSTEMDEPENDENCY`	`BMC_SoftwareServer` or `BMC_ApplicationSystem` (depended upon) Impacted	`BMC_SoftwareServer` or `BMC_ApplicationSystem` (dependant)
`BMC_Dependency`	`APPLICATIONSYSTEMDEPENDENCY`	`BMC_SoftwareServer` (facet)	`BMC_SoftwareServer` (main facet) Impacted

Communication relationships between nodes are mapped to a dependency between CIs.

Relationship

Name

Source

Destination

BMC_Dependency

APPLICATIONSYSTEMDEPENDENCY

Server (depended upon)

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService BMC_Cluster BMC_VirtualSystemEnabler
BMC DataBase BMC DataBase(Cloud)

(dependant)

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
BMC_Cluster BMC_VirtualSystemEnabler
BMC DataBase BMC DataBase(Cloud)

Impacted

BMC_Dependency

APPLICATIONSYSTEMDEPENDENCY

Client (dependant)

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService BMC_Cluster
BMC_VirtualSystemEnabler
BMC DataBase BMC DataBase(Cloud)

Impacted

Server (depended upon)

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
BMC_Cluster BMC_VirtualSystemEnabler
BMC DataBase BMC DataBase(Cloud)

Observed Communication relationships between nodes are mapped to Dependency between CIs. Due to the very high volume of Observed Communication relationships, only those that are part of application models are synchronized.

Relationship

Name

Source

Destination

BMC_Dependency

APPLICATIONSYSTEMDEPENDENCY

Listening

BMC_SoftwareServer

Impacted

BMC_Dependency

APPLICATIONSYSTEMDEPENDENCY

BMC_SoftwareServer

Connecting

BMC_SoftwareServer

Impacted

Management relationships

Relationship	Name	Source	Destination
`BMC_Dependency`	`SYSTEMMANAGER`	`BMC_Cluster BMC_SoftwareServer` First-order SI.`BMC_ApplicationSystem` Second-order SI`.`	`BMC_SoftwareServer` First-order SI. `BMC_ApplicationSystem` Second-order SI. `BMC_ComputerSystem BMC_Cluster`
`BMC_Dependency`	`SOFTWAREMANAGER`	`BMC_Cluster BMC_SoftwareServer` First-order SI.`BMC_ApplicationSystem` Second-order SI.	`BMC_SoftwareServer` First-order SI. `BMC_ApplicationSystem` Second-order SI. `BMC_ComputerSystem BMC_Cluster`
`BMC_HostedSystemComponents`	`HOSTEDSYSTEMCOMPONENTS`	`BMC_Cluster BMC_SoftwareServer` First-order SI.`BMC_ApplicationSystem` Second-order SI`. BMC_ComputerSystem`	`BMC_VirtualSystemEnabler` (hosted)

Although the manager impacts the CI it is managing, we do not mark the relationship as impactful, to avoid impact cycles.

BMC_Document

The synchronization mapping attribute DocumentType "TLS Certificate" is part of the BMC_Document CIs. When SoftwareInstance or LoadBalancerService nodes represent web servers for which TLS/SSL certificates have been discovered, they have related Detail nodes with type "TLS Certificate". The BMC_Document mapping was introduced in Technology Knowledge Update TKU 2020-Sep-1. For more information, see TLS Certificates Discovery.

These Detail nodes are mapped to BMC_Document CIs with the following attributes:

Attribute	Details
`Name`	Detail name
`ShortDescription`	Detail short_name
`Description`	Detail common_name
`Author`	Detail issuer. The certificate issuer.
`DocumentType`	TLS Certificate, Windows Certificate, or Amazon ACM Certificate.
`EndDate`	Detail expiry_date. The certificate end (valid to) date.
`SerialNumber`	Detail serial. The certificate serial number.
`StartDate`	Detail start_date. The certificate start (valid from) date.
`Company`	Host Company.
`Category`	"Software"
`Type`	"TLS Certificate"
`Item`	"BMC Discovered"

BMC_Document relationships

Relationship	Name	Source	Destination
`BMC_Dependency`	`CERTIFICATE`	`BMC_Document`	`BMC_SoftwareServer`(SI, Load Balancer, Management Controller, Cloud Service, or Host)

BMC_DataBase

Database nodes (logical databases) are mapped to BMC_DataBase:

Attribute	Details
key	The SoftwareInstance key, or for RuntimeEnvironments, the host_key/SoftwareInstance product / SoftwareInstance version
`TokenId`	Attribute that aids reconciliation of CIs populated by multiple data sources. `TokenId` is of the form `"%hosting_ci.TokenId%:%database_node.type%:%si_instance%:%database_node.instance%"` or `"%hosting_ci.Name%:%database_node.type%:%si_instance%:%database_node.instance%"`
`Name`	Database `name` or Database `name : software cluster name"` if the target is Remedyforce.
`ShortDescription`	Database `instance`
`Description`	Description is of the form `"%database_node.name% in %si_instance% on %hosting_ci.Name%"` or `"%database_node.name% on %cloud_svc_ci.Name%"`
`InstanceName`	`<type>:<hostname>:<DNS domain>:<instance name>` where `<type>` is the value of the BMC Helix Discovery type attribute from the corresponding SoftwareInstance or Database node, for example, “Microsoft SQL Server” or “Oracle Database”
`IsCloud`	`Yes` if the database is known to be cloud hosted; null if not
`Model`	DatabaseDetail `type`
`ComponentAliases`	Database component aliases
`CloudID`	Database unique cloud identifier (`cloud_id`).
`Company`	Host Company.
`Category`	"`Miscellaneous`"
`Type`	"`Instance`"
`Item`	"`Database`"
`ManufacturerName`	Software Instance `vendor`
`MarketVersion`	Software Instance `product_version`
`PatchNumber`	Software Instance `patch`
`ServicePack`	Software Instance `service_pack`
`VersionNumber`	Software Instance `version`

BMC_DataBase relationships

Relationship	Name	Source	Destination
`BMC_Dependency`	`MANAGEDDATABASE`	`BMC_SoftwareServer`	`BMC_DataBase`Impacted
`BMC_Dependency`	`MANAGEDDATABASE`	`BMC_ApplicationSystem`	`BMC_DataBase`Impacted
`BMC_Dependency`	`MANAGEDDATABASE`	`BMC_Cluster`	`BMC_DataBase`Impacted
`BMC_Dependency`	`MANAGEDDATABASE`	`BMC_CloudInstance`	`BMC_DataBase`Impacted

CDM Mapping for Cloud

Data models

BMC_CloudInstance (Provider)

BMC_CloudInstance relationships

BMC_CloudInstance (Region)

BMC_CloudInstance relationships

BMC_CloudInstance (Service)

BMC_Cluster

BMC_LogicalSystemComponent

BMC_LogicalSystemComponent relationships

BMC_ResourcePool

BMC_ResourcePool relationships

BMC_AdminDomain (AdminCollection)

BMC_AdminDomain (AdminCollection) relationships

BMC_AdminDomain (CloudManagementGroup, NestedCloudManagementGroup, OwnedManagementGroup)

BMC_AdminDomain (CloudManagementGroup) relationships

BMC_ConcreteCollection

BMC_ConcreteCollection relationships

Mapping of VirtualMachine nodes, SoftwareInstance nodes, and contained Database nodes

BMC_VirtualSystemEnabler and virtualization

Virtualization relationships

BMC_SoftwareServer and BMC_ApplicationSystem

BMC_SoftwareServer and BMC_ApplicationSystem relationships

BMC_Document

BMC_DataBase

BMC_DataBase relationships

Comments