CDM Mapping for Host
This topic provides information for CDM mapping for Host nodes. The CIs created are described in this topic.
BMC_ComputerSystem
A root Host node is mapped to a root BMC_ComputerSystem CI with the following attributes:
Attribute | Details |
---|---|
Name | The fully qualified name of the host if available, otherwise the hostname as reported by the OS; if no names are available, then the IP address |
NameFormat | " |
ShortDescription | Host |
Description | The host name and the fully qualified domain name separated by a colon, or if the fully qualified domain name is not available, then just the host name. |
CapabilityList | A single value corresponding to Server, Desktop, Laptop, or Other |
Domain | Host |
HostName | Host |
isVirtual |
|
isCloud | Yes if the host is known to be cloud hosted; null if not |
LastScanDate | Host |
ManufacturerName | Host |
Model | Host |
PrimaryCapability | Server, Desktop, Mainframe, or Laptop |
SerialNumber | Host |
PartitionId | Host |
TokenId | See TokenId rules below |
TotalPhysicalMemory | Host |
VirtualSystemType | Enumeration value corresponding to the type of virtual machine |
Workgroup | Host |
ComponentAliases | BMC_ComputerSystem:hostname |
Category | " |
Type | " |
Item | " |
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency | STORAGEUSE | BMC_ComputerSystem (Storage system) |
|
BMC_Dependency | BACKENDSTORAGEUSE | BMC_ComputerSystem (Backend Storage system) |
|
|
|
|
|
BMC_Dependency Introduced in January 2021 TKU. | NETWORKLINK | BMC_ComputerSystem (Network Device (SAN Switch))impacted |
|
TokenId rules
TokenId
is an attribute that in some circumstances aids reconciliation of CIs populated by multiple data sources. The following describes how BMC Discovery sets TokenId for BMC_ComputerSystem
.
For most hosts, TokenId
is of the form hostname:
DNS domain name, if the domain name is unavailable then hostname.
For some virtual hosts, TokenId
contains a UUID:
- For VMware,
TokenId
is of the form "VI-UUID:
ABCD-
EF-
GH-
IJ-
KLMNOP". Where each letter represents a hexadecimal digit. - For Hyper-V,
TokenId
is of the form "HYPERV-ID:
ABCD-
EF-
GH-
IJ-
KLMNOP". With Hyper-V, the UUID is only available on the physical machine, so TokenId is only set for virtual machines that have been successfully linked to their hosting physical machines. - For Xen (including Oracle VM),
TokenId
is of the form "XEN-ID:
ABCD-
EF-
GH-
IJ-
KLMNOP". - For KVM (including RedHat Enterprise Virtualization),
TokenId
is of the form "KVM-ID:
ABCD-
EF-
GH-
IJ-
KLMNOP".
BMC_OperatingSystem
The root Host is also mapped to a single BMC_OperatingSystem CI, with the following attributes:
Attribute | Details |
---|---|
Name | Host |
NameFormat | " |
ShortDescription | " |
Description | Host |
ManufacturerName | Host |
MarketVersion | Host |
Model | Host |
OSType | Enumeration value for OS type |
OSProductSuite | Enumeration value for OS product suite |
ServicePack | Host |
VersionNumber | Host |
Company | Host Company |
Category | " |
Type | " |
Item | " |
Operating system relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
BMC_Processor
The root Host is mapped to a number of BMC_Processor CIs.
- For physical machines, the number of CIs corresponds to the number of physical CPU packages present in the machine.
- For virtual machines, the number of CIs corresponds to the number of logical CPUs the OS is scheduling across.
In some circumstances, it is not possible to discover the number of physical CPU packages in a physical machine. In such cases, no BMC_Processor CIs are created for the machine.
All the BMC_Processor CIs for a host are normally identical to each other, though they can be different in cases that a physical machine has more than one type of CPU.
If BMC Discovery ProcessorInfo nodes are not present, the system reverts to the previous (before version 11.0 mapping) using Host node attributes.
Note
This mapping is unusual, in that it creates a number of BMC_Processor CIs corresponding to the number of processors in a Host, stored as numeric attributes. As a result, you cannot modify the created CIs with an extension mapping in the usual way with "mapping from", because there is no suitable traversal loop to extend. Instead, if you wish to make modifications, you should copy this mapping to a new file with a new name, then declare that it "overrides" this one in its overview block.
Attribute | Details |
---|---|
Name | Host |
NameFormat | " |
ShortDescription | Host |
Description | Description of the processor, its index, and host |
isVirtual | True if the Host is virtual; not set if physical. (Not present in CMDB 7.5.) |
ManufacturerName | Manufacturer of the processor. |
MaxClockSpeed | Host |
Model | Host |
NumberOfCores | Host |
NumberOfLogicalProcessors | Host |
OtherProcessorFamilyDescription | Host |
ProcessorArchitecture | Enumeration representing the architecture |
ProcessorFamily | Enumeration representing the processor family |
ProcessorStatus | 1 — CPU enabled |
ProcessorType | 2 — Central processor |
UpgradeMethod | 1 — Unknown |
Company | Host Company |
Category | " |
Type | " |
Item | " |
Processor relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
BMC_NetworkPort, BMC_IPEndpoint and BMC_LANEndpoint
Each Network Interface node connected to the root Host in the BMC Discovery model is mapped to a BMC_NetworkPort CI, and its MAC address is mapped to a BMC_LANEndpoint CI. Each of its associated IP addresses are mapped to BMC_IPEndpoint CIs.
Where BMC Discovery has been able to connect a Network Interface node to a Network Device node (via associated port nodes), a BMC_Dependency relationship is created between the two BMC_ComputerSystem CIs representing the host and the network device.
BMC_NetworkPort
Attribute | Details |
---|---|
Key | NetworkInterface |
Name | NetworkInterface |
ShortDescription | NetworkInterface |
Description | NetworkInterface |
AutoSense | Yes (0) or No (1) or null if not known |
FullDuplex | Yes (0) or No (1) or null if not known |
LinkTechnology | Ethernet (2) |
ManufacturerName | NetworkInterface |
PermanentAddress | NetworkInterface |
PortType | Ethernet (2) |
Speed | NetworkInterface |
Company | HostCompany |
Category | " |
Type | " |
Item | " |
Each Fibre Channel HBA card node is mapped to the BMC_NetworkPort CI with the following attributes:
Attribute | Details |
---|---|
Key |
|
Name | FibreChannelHBA |
ShortDescription | FibreChannelPort wwpn |
Description | FibreChannelHBA description and FibreChannelPort wwpn or just FibreChannelPort wwpn |
LinkTechnology | Fibre Channel (4) |
ManufacturerName | FibreChannelHBA vendor |
Model | FibreChannelHBA model |
PermanentAddress | FibreChannelPort wwpn |
PortType | Fibre Channel (6) |
SerialNumber | FibreChannelHBA serial |
Company | HostCompany |
Category | “H |
Type | “Card” |
Item | “Fibre Channel HBA card” |
BMC_NetworkPort relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
BMC_LANEndpoint
MAC addresses in the BMC Discovery data model are stored in the conventional form with colons separating each pair of hexadecimal digits; in the CDM, MAC addresses are stored as just the hexadecimal digits, with no separating colons.
Attribute | Details |
---|---|
Key |
|
Name | NetworkInterface |
NameFormat | " |
ShortDescription | NetworkInterface |
Description | "MAC address |
Address | MAC address (no separating colons) |
MACAddress | MAC address (no separating colons) |
ProtocolType | Ethernet (14) |
Company | HostCompany |
Category | " |
Type | " |
Item | " |
BMC_LANEndpoint relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
|
|
|
|
BMC_IPEndpoint
Attribute | Details |
---|---|
Key | "%host.key%/IP/%ip_addr%" or |
Name | NetworkInterface |
NameFormat | " |
ShortDescription | IP Address |
Description | IP Address |
AddressType | IPv4 (1) or IPv6 (2) |
Address | IP Address ip_addr |
DNSHostName | IP Address |
ManagementAddress | Yes (1) if the IP address was used to scan the host; No (0) if not. (Not in CMDB 7.5.) |
ProtocolType | IPv4 (2) or IPv6 (3) |
PrefixLength | IP Address prefix_length |
SubnetMask | IP Address |
Company | HostCompany |
Category | " |
Type | " |
Item | " |
BMC_IPEndpoint relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
|
|
|
|
BMC_Dependency | BINDSTO | BMC_LANEndpoint |
|
BMC_IPConnectivitySubnet
BMC Discovery Subnet nodes are mapped to BMC_IPConnectivitySubnet
:
Attribute | Details |
---|---|
Name | Subnet |
ShortDescription | Subnet |
Description | Subnet |
SubnetNumber | Subnet |
AddressType | IPv4 (1) or IPv6 (2) |
PrefixLength | IP Address |
SubnetMask | IP Address |
Company | HostCompany |
Category | " |
Type | " |
Item | " |
Subnet relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
BMC_Cluster
Host cluster
Host Cluster nodes are mapped to BMC_Cluster
:
Attribute | Details |
---|---|
TokenId | See TokenId rules. |
Name | Cluster |
NameFormat | " |
InstanceName |
|
ManufacturerName | The manufacturer name. |
Model | The cluster type |
Description | Cluster |
ShortDescription | Cluster |
ComponentAliases | Cluster cdm_component_aliases |
Company | HostCompany |
Category | " |
Type | " |
Item | " |
Host Cluster relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
|
|
|
|
BMC_Dependency | CLUSTERMANAGER |
|
|
BMC_Dependency | CLUSTERMANAGER |
| BMC_Cluster Managed cluster Impacted |
Software cluster
Software Cluster nodes are mapped to BMC_Cluster
:
Attribute | Details |
---|---|
TokenId | See TokenId rules. |
Name | Software Cluster |
ShortDescription | Cluster |
Description | Cluster |
InstanceName |
|
ManufacturerName | Publisher from the Pattern maintaining the Software Cluster |
MarketVersion | Software Cluster |
Model | Software Cluster |
PatchNumber | Software Cluster |
VersionNumber | Software Cluster |
ComponentAliases | Software Cluster |
Company | HostCompany |
Category | " |
Type | " |
Item | Category specified in the maintaining Pattern or " |
Software Cluster relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
|
|
|
|
BMC_IPEndpoint (Cluster)
ClusterService node IP addresses are mapped to BMC_IPEndpoint
CIs.
Attribute | Details |
---|---|
Name |
|
NameFormat | "IP" |
ShortDescription | Cluster service name |
Description |
|
AddressType | IPv4 (1) or IPv6 (2) |
Address | IP Address ip_addr |
ProtocolType | IPv4 (2) or IPv6 (3) |
Company | HostCompany |
Category |
|
Type | " |
Item | " |
IP address relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_HostedAccessPoint |
|
|
|
BMC_Dependency |
|
|
|
BMC_SystemResource (Cluster)
ClusterService node IP addresses are also mapped to BMC_SystemResource
CIs.
Attribute | Details |
---|---|
key | cluster_service.key |
Name | ClusterService |
ShortDescription | ClusterService name |
Description | ClusterService name: DNS name" or |
ResourceType | Cluster Resource Group (2) |
Company | HostCompany |
Category | "Unknown" |
Type | "Unknown" |
Item | "BMC Discovered" |
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_HostedSystemComponents |
|
|
|
BMC_Dependency |
|
|
|
BMC_LogicalSystemComponent (Cluster)
LoadBalancerService nodes are mapped to BMC_LogicalSystemComponent CIs.
Attribute | Details |
---|---|
key | Load balancer service |
TokenId | "ADDM:%lb_service.key%" |
Name | Load balancer service |
ShortDescription | Load balancer service |
Description | Load balancer service |
isCloud | Load balancer service |
Company | Cluster Company |
Category | "Network" |
Type | "Service" |
Item | "Load balancer service" |
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency |
|
|
|
BMC_ResourcePool (Cluster)
LoadBalancerPool nodes are mapped to BMC_ResourcePool CIs.
Attribute | Details |
---|---|
key | Load balancer pool |
TokenId |
|
Name | Load balancer pool |
ShortDescription | Load balancer pool |
Description | Load balancer pool |
ResourceType | 0 (Other) |
OtherResourceType | "Load Balancer Pool" |
Company | Cluster Company |
Category | "Network" |
Type | "Service" |
Item | "Load balancer pool" |
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency |
|
|
|
BMC_HardwareSystemComponent
Any Management Controller node with a direct Management relationship to the root Host in the BMC Discovery model is mapped to a BMC_HardwareSystemComponent CI.
Note
There is no way to map the ManagementController's IP information to the CDM.
BMC_HardwareSystemComponent
Attribute | Details |
---|---|
Name | Management controller |
ShortDescription | Management controller name. |
Description | Vendor name, controller model and type. With serial if known. |
LastScanDate | Management controller last_update_success |
ManufacturerName | Management controller vendor name. |
Model | Management controller model. |
PowerManagementSupported | Yes (0) or null if not known. |
SerialNumber | Management controller serial number. |
Company | Host Company. |
VersionNumber | Management controller version number. |
ComponentAliases | Management controller cdm_component_aliases |
Category | "Hardware" |
Type | "Hardware" |
Item | "Management controller" |
Hardware system component relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
BMC_ComputerSystem (Host Container)
HostContainer nodes are mapped to BMC_ComputerSystem
representing the partitioned container.
Attribute | Details |
---|---|
TokenId | Attribute that aids reconciliation of CIs populated by multiple data sources. |
Name | Host Container |
ShortDescription | Host Container |
Description | Host Container |
CapabilityList | "Other" (2) |
LastScanDate | Host |
ManufacturerName | Host Container |
Model | Host Container |
OtherCapabilityDescription | Host Container |
PrimaryCapability | "Blade System" (48) or "Other" (2) |
SerialNumber | Host Container |
TotalPhysicalMemory | Host Container |
ComponentAliases | VM cdm_component_aliases |
Company | Host Container Company. |
Category | " |
Type | " |
Item | Host Container |
Host containment relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
|
|
|
|
BMC_VirtualSystemEnabler and virtualization
When a physical machine hosts one or more virtual machines, the BMC 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.
Note
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 |
Description | VirtualMachine |
BuildNumber | VirtualMachine |
EnablerType | Enumeration representing the type of virtualization technology |
InstanceName |
where |
isCloud | Yes if the virtual machine is known to be cloud hosted; null if not |
ManufacturerName | Publisher. |
MarketVersion | VirtualMachine |
Model | VirtualMachine |
PatchNumber | VirtualMachine |
ServicePack | VirtualMachine |
VersionNumber | VirtualMachine |
ComponentAliases | VirtualMachine cdm_component_aliases |
Company | Host Company |
Category | " |
Type | " |
Item | " |
Virtualization relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
BMC_HostedSystemComponents | HOSTEDSYSTEMCOMPONENTS | BMC_CloudInstance | BMC_VirtualSystemEnabler Impacted |
|
|
|
Impacted |
|
|
|
|
BMC_SoftwareServer and BMC_ApplicationSystem
Each SoftwareInstance
in the BMC 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 toBMC_SoftwareServer
SoftwareInstance
nodes composed of otherSoftwareInstance
nodes are mapped toBMC_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 |
---|---|
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 |
ShortDescription | Software Instance |
Description | Software Instance |
BuildNumber | Software Instance |
InstanceName |
where |
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 |
Model | Software Instance |
OtherSoftwareServerType | Software Instance |
PatchNumber | Software Instance |
ServicePack | Software Instance |
SoftwareServerType | Enumeration representing the type of SoftwareServer. Often 0 meaning "Other". (Only in |
VersionNumber | Software Instance |
ComponentAliases | Software Instance cdm_component_aliases |
Company | Software Instance Company. |
Category | " |
Type | " |
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 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_Component | APPLICATIONSYSTEMHIERARCHY | BMC_SoftwareServer (containing) | BMC_SoftwareServer (contained) |
|
|
|
|
| APPLICATIONSYSTEMDEPENDENCY | BMC_SoftwareServer (facet) | BMC_SoftwareServer (main facet)Impacted |
Communication relationships between nodes are mapped to a dependency between CIs.
Relationship | Name | Source | Destination |
---|---|---|---|
|
| Server (depended upon)
| (dependant)
Impacted |
|
| Client (dependant)
Impacted | Server (depended upon)
|
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 |
---|---|---|---|
|
| Listening
|
Impacted |
|
|
| Connecting
Impacted |
Management relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency | SYSTEMMANAGER | First-order SI. Second-order SI
|
|
BMC_Dependency | SOFTWAREMANAGER |
| 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_Document
The new synchronization mapping attribute DocumentType "TLS Certificate" has been added to 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 the 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" |
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_DataBase
Database
nodes (logical databases) are mapped to BMC_DataBase
:
Attribute | Details |
---|---|
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 |
ShortDescription | Database |
Description | Description is of the form
|
InstanceName |
where |
IsCloud | Yes if the database is known to be cloud hosted; null if not. |
Model | DatabaseDetail |
ComponentAliases | Database component aliases |
Company | Host Company. |
Category | " |
Type | " |
Item | " |
ManufacturerName | Software Instance |
MarketVersion | Software Instance |
PatchNumber | Software Instance |
ServicePack | Software Instance |
VersionNumber | Software Instance |
BMC_DataBase relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
| MANAGEDDATABASE | BMC_ApplicationSystem | BMC_DataBase Impacted |
| MANAGEDDATABASE | BMC_Cluster | BMC_DataBase Impacted |
BMC_Dependency | MANAGEDDATABASE | BMC_CloudInstance | BMC_DataBase Impacted |
BMC_Product
BMC_Product
represents the installed aspects of a product. BMC Discovery uses SoftwareInstance nodes and associated metadata to provide an accurate picture of the installed products, regardless of how the products are installed. The mapping groups the SoftwareInstance
nodes according to the product information on the maintaining patterns, and maintains one BMC_Product CI for each unique product version on the Host. SoftwareInstance nodes with different types can belong to a single product. So, for example, a server running four Oracle database instances and one Oracle TNS Listener would have five SoftwareInstance nodes; those five SoftwareInstances would map to a single Oracle Database BMC_Product
CI.
Attribute | Details |
---|---|
Name |
|
NameFormat | " |
ShortDescription |
|
Description |
|
BuildNumber | Software Instance |
ManufacturerName | Publisher from Pattern or |
MarketVersion | Software Instance |
Model | Product name from Pattern or |
PatchNumber | Software Instance |
ServicePack | Software Instance |
VersionNumber | Software Instance |
Company | Host Company. |
Category | " |
Type | " |
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)
Product relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
BMC_ApplicationService
SoftwareComponent
is mapped to BMC_ApplicationService
.
Attribute | Details |
---|---|
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 Component key. |
Name | Software Component |
ShortDescription | Software Component |
Description | Software Component |
Model | Software Component |
VersionNumber | Software Component |
ApplicationServiceType | Enumeration value representing the service type. Either comes from the component or defaults to unknown. |
Company | Host Company. |
Category | " |
Type | " |
Item | " |
Application service relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
| CLUSTERSERVICES (for clustered components) |
| BMC_ApplicationService Impacted |
BMC_Application
BusinessApplicationInstance
is mapped to BMC_Application
. Contained SoftwareInstance and BusinessApplicationInstance nodes are mapped to corresponding BMC_Component relationships. Only Hosts directly contained within the application are synced. A Host that is included in a ModelDefinition, but is not at the "top" of the application model, will be implicitly included in the CMDB through software CIs.
Attribute | Details |
---|---|
Name | Business Application Instance |
ShortDescription | Business Application Instance |
Description | Business Application Instance |
MarketVersion | Business Application Instance |
VersionNumber | Business Application Instance |
Model | Business Application Instance |
ComponentAliases | Business Application Instance cdm_component_aliases |
Company | Host Company. |
Category | " |
Type | " |
Item | " |
Application relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
| BMC_Application Impacted |
|
|
| BMC_Application Impacted | BMC_Cluster |
|
| BMC_Application Impacted |
|
|
|
|
|
|
|
| BMC_ConcreteCollection |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
BMC_Component | APPLICATIONSYSTEMCOMPONENT | BMC_Application | BMC_SoftwareServer |
BMC_Component | APPLICATIONSYSTEMCOMPONENT | BMC_Application |
|
BMC_Component | APPLICATIONSYSTEMCOMPONENT | BMC_Application | BMC_ApplicationService |
BMC_Component | APPLICATIONSYSTEMCOMPONENT | BMC_Application | BMC_VirtualSystemEnabler |
|
|
|
|
|
|
| BMC_ConcreteCollection |
BMC_Component | APPLICATIONSYSTEMCOMPONENT | BMC_Application | BMC_Cluster |
BMC_Component | APPLICATIONSYSTEMCOMPONENT | BMC_Application | BMC_DataBase |
BMC_Component | APPLICATIONSYSTEMCOMPONENT | BMC_Application | Load Balancer) |
BMC_Component | APPLICATIONSYSTEMCOMPONENT | BMC_Application | BMC_Printer |
BMC_Component | APPLICATIONSYSTEMCOMPONENT | BMC_Application |
|
BMC_ConcreteCollection
FunctionalComponent
nodes representing CAM Functional Components are mapped to BMC_ConcreteCollection
.
Attribute | Details |
---|---|
Name | Functional Component |
ShortDescription | Functional Component |
Description | Functional Component |
Model | Functional Component |
Company | Host |
Category | " |
Type | " |
Item | " |
Functional Component relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| BMC_Cluster |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The relationship between BMC_Application
and BMC_ConcreteCollection
is used for Functional Components reached from any of the following node kinds:
- SoftwareInstance (first or second order)
- SoftwareComponent
- SoftwareCluster
- DatabaseDetail
- BAI
Dependency relationships
Relationship | Name | Source (Depended) | Destination |
---|---|---|---|
BMC_Dependency | APPLICATIONSYSTEMDEPENDENCY |
(Impacted) |
|
Relationship | Name | Source | Destination (Dependant) |
---|---|---|---|
BMC_Dependency | APPLICATIONSYSTEMDEPENDENCY |
|
(Impacted) |
Comments
Log in or register to comment.