CDM Mapping for Cloud

This topic provides information about mapping for cloud nodes.

This page is best viewed in full screen mode

To access full screen mode, click the full screen  icon in the top right of the page.

The CIs created are described in this topic.

Data models

CMDB version differences

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 modelCMDB versionsEffect

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

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

Cloud region name

Model

Cloud region code

TokenId

Cloud region key
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

Cloud service name

ConsumedServiceCloud service type

Model

Cloud service code

TokenId

Cloud service key

Category

"Cloud"

Type

"Cloud Provider"

Item

Cloud service type

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

isCloud

Yes if  if the service exists directly within a cloud; null if not

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_ComponentHOSTEDRESOURCEPOOLBMC_CloudInstance
(Service)
BMC_ResourcePool

BMC_Dependency

LOADBALANCERSERVICE

BMC_ResourcePool
(Service)

BMC_LogicalSystemComponent
Impacted

BMC_AdminDomain

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

Attribute

Details

Name

Administrative collection name or
Administrative collection name : cloud service name if the target is Remedyforce.

ShortDescription

Administrative collection short_name, or name

Description

Administrative collection name

ModelAdministrative collection type
TokenIdAdministrative collection key

Company

Cloud service Company

Category

"Cloud"

Type

"Administrative Collection"

Item

Administrative collection name

BMC_AdminDomain relationships

Relationship

Name

Source

Destination

BMC_DependencyCLOUDADMINCOLLECTIONBMC_CloudInstance
(Service)
BMC_AdminDomain

BMC_Dependency

ADMINCOLLECTIONMEMBER

BMC_CloudInstance
(Service)

BMC_BaseElement

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

ModelDeployment type
TokenIdDeployment key

Company

Cloud service Company

Category

"Cloud"

Type

"Deployment"

Item

Deployment name

BMC_ConcreteCollection relationships

Relationship

Name

Source

Destination

BMC_DependencyCLOUDDEPLOYMENTBMC_CloudInstance
(Service)
BMC_ConcreteCollection
BMC_DependencyCLOUDDEPLOYMENTBMC_Cluster
(Service)
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 Discovery model represents it as a number of Virtual Machine nodes related to the physical Host, one Virtual Machine node per virtual host. A BMC_VirtualSystemEnabler CI is created for each VirtualMachine node.

Difference with previous releases

Previous releases of BMC Discovery, before version 11.2 created a single BMC_VirtualSystemEnabler CI to represent all virtual machines hosted by a physical machine. Upon first synchronization after upgrade from versions before 11.2, these singleton CIs will be marked as deleted, and new separate CIs will be created corresponding to the separate virtual machines.


Attribute

Details

Name

VirtualMachine name

ShortDescription

VirtualMachine short_name or name

Description

VirtualMachine name

BuildNumber

VirtualMachine build

EnablerType

Enumeration representing the type of virtualization technology

isCloudYes 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

VersionNumber

VirtualMachine version

ComponentAliasesVirtualMachine cdm_component_aliases
CompanyHost 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_HostedSystemComponentsHOSTEDSYSTEMCOMPONENTSBMC_CloudInstanceBMC_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 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

TokenIdAttribute 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

isCloudYes 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

ComponentAliasesSoftware Instance cdm_component_aliases

Company

Software Instance Company.

Category

"Software"

Type

"Application"

Item

Product category from the maintaining Pattern

Item values

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 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
BMC_Cluster
BMC_CloudInstance

BMC_SoftwareServer
Impacted

BMC_Component

APPLICATIONSYSTEMHIERARCHY

BMC_ApplicationSystem (containing)
Impacted

BMC_SoftwareServer (contained)

BMC_ComponentAPPLICATIONSYSTEMHIERARCHYBMC_SoftwareServer (containing)BMC_SoftwareServer (contained)

BMC_Dependency

APPLICATIONSYSTEMDEPENDENCY

BMC_SoftwareServer or BMC_ApplicationSystem (depended upon)
Impacted

BMC_SoftwareServer or BMC_ApplicationSystem (dependant)

BMC_Dependency

APPLICATIONSYSTEMDEPENDENCYBMC_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

(dependant)

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
BMC_Cluster
BMC_VirtualSystemEnabler

BMC DataBase

Impacted

BMC_Dependency

APPLICATIONSYSTEMDEPENDENCY

Client (dependant)

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
BMC_Cluster

BMC_VirtualSystemEnabler
BMC DataBase

Impacted

Server (depended upon)

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
BMC_Cluster
BMC_VirtualSystemEnabler

BMC DataBase

Observed Communication relationship between nodes 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

BMC_SoftwareServer

Impacted

BMC_Dependency

APPLICATIONSYSTEMDEPENDENCY

BMC_SoftwareServer

Connecting

BMC_SoftwareServer

Impacted

Management relationships

Relationship

Name

Source

Destination

BMC_DependencySYSTEMMANAGERBMC_Cluster
BMC_SoftwareServer
First-order SI.
BMC_ApplicationSystem
Second-order SI.
BMC_Cluster
BMC_DependencySOFTWAREMANAGER

BMC_Cluster
BMC_SoftwareServer
First-order SI.
BMC_ApplicationSystem
Second-order SI.

BMC_SoftwareServer First-order SI.
BMC_ApplicationSystem Second-order SI.

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

BMC_DataBase

Database nodes (logical databases) are mapped to BMC_DataBase:

Attribute

Details

TokenIdAttribute 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%"

Model

DatabaseDetail type

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

MANAGEDDATABASEBMC_ApplicationSystemBMC_DataBase
Impacted

BMC_Dependency

MANAGEDDATABASEBMC_ClusterBMC_DataBase
Impacted

Was this page helpful? Yes No Submitting... Thank you

Comments