CDM Mapping for MFPart
This topic provides information about CDM mapping for MFPart nodes. The CIs created are described in this topic.
Data models
BMC_ComputerSystem
The MFPart node is used to model a logical server within the mainframe. The root MFPart node is mapped to a root BMC_ComputerSystem CI with the following attributes:
Attribute | Details |
---|---|
TokenId | MFPart key attribute. See TokenId rules. |
Name | MFPart key attribute |
NameFormat | "Mainframe" |
ShortDescription | MFPart name attribute |
Description | MFPart description attribute |
CapabilityList | Server |
ComponentAliases | Component alias from mainframe discovery |
isVirtual | Yes if either MFPart virtual or partition is set; null otherwise |
LastScanDate | MFPart last_update_success — the date and time the MFPart was last scanned |
ManufacturerName | MFPart vendor — the manufacturer of the mainframe |
MFIntegrationID | MFPart mf_integration_id — MainView identifier used for launch in context |
Model | MFPart model |
PrimaryCapability | Server |
VirtualSystemType | LPAR or VM/VM Guest |
Category | "Hardware" |
Type | "Processing Unit" |
Item | "Server" |
BMC_OperatingSystem
The root MFPart is also mapped to a single BMC_OperatingSystem CI, with the following attributes:
Attribute | Details |
---|---|
Name | MFPart __mfpart_id or MFPart __mfpart_id : hostname if the target is Remedyforce. |
NameFormat | "Mainframe" |
ShortDescription | OS type followed by OS serial number |
Description | "OS-__mfpart_id |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | MFPart vendor |
MFIntegrationID | MFPart mf_integration_id — MainView identifier used for launch in context |
Model | MFPart os_type — "z/OS" or "z/VM OS" |
OSType | z/OS or z/VM |
SerialNumber | MFPart os_serial |
VersionNumber | MFPart os_version |
Category | "Software" |
Type | "Operating System Software" |
Item | "Standard OS" |
Operating system relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_HostedSystemComponents | SYSTEMOS | BMC_ComputerSystem | BMC_OperatingSystem |
BMC_Mainframe
An MFPart corresponding to a Native LPAR is directly connected to a Mainframe node. The Mainframe is mapped to a BMC_Mainframe CI as follows:
Attribute | Details |
---|---|
Name | Mainframe key |
Description | Mainframe description |
ShortDescription | Mainframe name |
AvailableCPs | Mainframe available_cps |
CapabilityList | Mainframe |
ComponentAliases | Component alias from mainframe discovery |
InstalledCPUs | Mainframe num_processors |
ManufacturerName | Mainframe vendor |
MFIntegrationID | Mainframe mf_integration_id — MainView identifier used for launch in context |
Model | Mainframe model |
PrimaryCapability | Mainframe |
Category | Hardware |
Type | Processing Unit |
Item | Mainframe |
Mainframe relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Component | SYSTEMPARTITION | BMC_Mainframe | BMC_ComputerSystem |
BMC_HostedSystemComponents | HOSTEDSYSTEMCOMPONENTS | BMC_Mainframe | BMC_VirtualSystemEnabler |
BMC_VirtualSystemEnabler
For Native LPARs, the MFPart and Mainframe nodes are mapped to a BMC_VirtualSystemEnabler CI as follows:
Attribute | Details |
---|---|
Name | Mainframe key with suffix "-VSE" |
ShortDescription | MFPart part_type |
ComponentAliases | Component alias from mainframe discovery |
Description | MFPart part_type followed by Mainframe key |
EnablerType | MFPart __cdm_enabler_type |
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” |
ManufacturerName | MFPart vendor |
MFIntegrationID | Mainframe mf_integration_id — MainView identifier used for launch in context |
Model | MFPart part_type |
Category | "Software" |
Type | "Operating System Software" |
Item | "Virtualization OS" |
For zVM LPARs, the BMC Helix Discovery model represents the virtualization as a Software Instance node connected to the containing Native LPAR. That Software Instance is mapped to a BMC_VirtualSystemEnabler as follows:
Attribute | Details |
---|---|
Name | Software Instance __cdm_component_alias |
NameFormat | "Mainframe" |
ShortDescription | Software Instance vm_id |
Description | "z/VM-" followed by Software Instance __cdm_component_alias |
BuildNumber | Software Instance build |
ComponentAliases | Component alias from mainframe discovery |
EnablerType | Software Instance cdm_vm_enabler_type |
MFIntegrationID | MFPart mf_integration_id — MainView identifier used for launch in context |
Model | Software Instance type |
PatchNumber | Software Instance patch |
ServicePack | Software Instance service_pack |
VersionNumber | Software Instance version |
Category | "Software" |
Type | "Operating System Software" |
Item | "Virtualization OS" |
BMC_VirtualSystemEnabler relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency | VIRTUALSYSTEMOS | BMC_VirtualSystemEnabler | BMC_ComputerSystem (contained) |
BMC_HostedSystemComponents | HOSTEDSYSTEMCOMPONENTS | BMC_Mainframe / BMC_ComputerSystem (containing) | BMC_VirtualSystemEnabler Impacted |
BMC_Sysplex / BMC_Cluster
The root MFPart is related to a Cluster node to represent its sysplex. This is mapped to BMC_Sysplex in CMDB versions prior to 7.6.03, and to BMC_Cluster in version 7.6.03. In either case, the attributes are populated as follows:
Attribute | Details |
---|---|
Name | Cluster key |
NameFormat | "Mainframe" |
ShortDescription | Cluster name |
Description | Cluster description |
ComponentAliases | Component alias from mainframe discovery |
MFIntegrationID | MFPart mf_integration_id — MainView identifier used for launch in context |
Model | "Sysplex" |
Types | "SysPlex" |
Category | "Software" |
Type | "Cluster" |
Item | "Mainframe" |
BMC_Sysplex / BMC_Cluster relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Component | CLUSTEREDSYSTEM | BMC_Sysplex / BMC_Cluster | BMC_OperatingSystemImpacted |
BMC_MFCouplingFacility
The MFPart and Cluster are both related to a number of Coupling Facility nodes. Each one is mapped to a BMC_MFCouplingFacility CI as follows:
Attribute | Details |
---|---|
Name | Coupling Facility key |
NameFormat | "Mainframe" |
Description | Coupling Facility description |
ShortDescription | Coupling Facility name |
CFRMName | Coupling Facility cfrm_name |
ComponentAliases | Component alias from mainframe discovery |
MFIntegrationID | MFPart mf_integration_id — MainView identifier used for launch in context |
Model | "CF" |
NodeDescriptor | Coupling Facility node_descriptor |
Storage | Coupling Facility storage |
Category | Hardware |
Type | Processing Unit |
Item | Mainframe |
BMC_MFCouplingFacility relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency | COUPLINGFACILITYOS | BMC_MFCouplingFacility | BMC_OperatingSystemImpacted |
BMC_HostedSystemComponents | SYSPLEXCOUPLINGFACILITY | BMC_Sysplex / BMC_Cluster | BMC_MFCouplingFacility |
BMC_StorageSubsystem
The root MFPart can be related to a number of StorageCollection nodes. Each node is mapped to a BMC_StorageSubsystem CI as follows:
Name | StorageCollection key |
NameFormat | "Mainframe" |
ShortDescription | StorageCollection name |
Description | StorageCollection key |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | StorageCollection vendor |
MFIntegrationID | MFPart mf_integration_id — MainView identifier used for launch in context |
Model | StorageCollection type |
PrimaryCapability | StorageSubsystem |
Category | "Hardware" |
Type | "Disk device" |
Item | "Disk array" |
BMC_StorageSubsystem relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency | STORAGESUBSYSTEMOS | BMC_StorageSubsystem | BMC_OperatingSystemImpacted |
BMC_DiskDrive / BMC_TapeDrive
Both the root MFPart and the StorageCollection nodes are related to Storage nodes, representing disk and tape drives. Disk drives are mapped to BMC_DiskDrive CIs as follows:
Name | Storage key |
NameFormat | "Mainframe" |
ShortDescription | Storage name |
Description | Storage key |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | Storage vendor |
MediaType | 1 (fixed hard disk) |
MFIntegrationID | MFPart mf_integration_id — MainView identifier used for launch in context |
Model | Storage model |
PNPDeviceID | Storage device_id |
SerialNumber | Storage volume_id |
Category | "Hardware" |
Type | "Disk device" |
Item | "Disk drive" |
Tape drives are mapped to BMC_TapeDrive CIs as follows:
Name | Storage key |
NameFormat | "Mainframe" |
ShortDescription | Storage name |
Description | Storage key |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | Storage vendor |
MediaType | 0 (removable media) |
MFIntegrationID | MFPart mf_integration_id — MainView identifier used for launch in context |
Model | Storage model |
PNPDeviceID | Storage device_id |
Category | "Hardware" |
Type | "Tape device" |
Item | "Tape drive" |
BMC_DiskDrive / BMC_TapeDrive relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_HostedSystemComponents | STORAGESUBSYSTEMDASD | BMC_StorageSubsystem | BMC_DiskDrive |
BMC_Dependency | DASDOS | BMC_DiskDrive | BMC_OperatingSystem |
BMC_HostedSystemComponents | STORAGESUBSYSTEMTAPE | BMC_StorageSubsystem | BMC_TapeDrive |
BMC_Dependency | TAPEOS | BMC_TapeDrive | BMC_OperatingSystemImpacted |
BMC_MFSoftwareServer / BMC_SoftwareServer
Each Software Instance related to the root MFPart is mapped to a corresponding CI. In CMDB versions prior to 7.6.03, the CI has the extension class BMC_MFSoftwareServer; in CMDB version 7.6.03, the CI has the base BMC_SoftwareServer class. In both cases, the attributes are as follows:
Attribute | Details |
---|---|
Name | Software Instance key |
NameFormat | "Mainframe" |
ShortDescription | Software Instance name |
Description | Software Instance key |
BuildNumber | Software Instance build |
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” |
ComponentAliases | Component alias from mainframe discovery |
JobName | Software Instance job_id CMDB versions prior to 7.6.03 |
ManufacturerName | Publisher specified in the maintaining Pattern or on the Software Instance |
MFJobName | Software Instance job_id CMDB versions 7.6.03 and later |
MFIntegrationID | MFPart mf_integration_id — MainView identifier used for launch in context |
Model | Software Instance short_type CMDB versions prior to 7.6.03 |
Model | Software Instance type CMDB versions 7.6.03 and later |
OtherSoftwareServerType | Software Instance type |
PatchNumber | Software Instance patch |
ServicePack | Software Instance service_pack |
ServerID | Software Instance server_id CMDB versions prior to 7.6.03 |
MFServerID | Software Instance server_id CMDB versions 7.6.03 and later |
VersionNumber | Software Instance version |
Category | "Software" |
Type | "Application" |
Item | "BMC Discovered" |
BMC_MFSoftwareServer / BMC_SoftwareServer relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency | APPLICATIONSYSTEMCOMPUTER | BMC_ComputerSystem | BMC_SoftwareServer |
BMC_Dependency | APPLICATIONSYSTEMDEPENDENCY | BMC_SoftwareServer (depended upon) | BMC_SoftwareServer (dependant) |
BMC_ApplicationService
SoftwareComponent is mapped to BMC_ApplicationService.
Attribute | Details |
---|---|
Name | Software Component name |
ShortDescription | Software Component name |
Description | Software Component name |
Model | Software Component type |
VersionNumber | Software Component version |
ApplicationServiceType | Enumeration value representing the service type |
Category | "Software" |
Type | "Application Service" |
Item | "BMC Discovered" |
Application service relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_ApplicationSystemServices | APPLICATIONSYSTEMSERVICES(for non-clustered components) | BMC_SoftwareServer | BMC_ApplicationServiceImpacted |
BMC_ApplicationSystemServices | CLUSTERSERVICES(for clustered components) | BMC_SoftwareServer | BMC_ApplicationServiceImpacted |
BMC_Application
BusinessApplicationInstance is mapped to BMC_Application. Contained SoftwareInstance and BusinessApplicationInstance nodes are mapped to corresponding BMC_Component relationships.
Name | Business Application Instance name |
ShortDescription | Business Application Instance name |
Description | Business Application Instance name |
MarketVersion | Business Application Instance product_version |
Model | Business Application Instance type |
VersionNumber | Business Application Instance version |
Category | "Software" |
Type | "Application" |
Item | "Application Platform" |
Application relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency | APPLICATIONSYSTEMCOMPUTER | BMC_ComputerSystem | BMC_Application |
BMC_Component | APPLICATIONSYSTEMHIERARCHY | BMC_Application Impacted | BMC_SoftwareServer / BMC_MFSoftwareServer |
BMC_Component | APPLICATIONSYSTEMHIERARCHY | BMC_Application (containing) Impacted | BMC_Application (contained) |
BMC_DataBase
DatabaseDetail nodes representing logical databases are mapped to BMC_DataBase:
Attribute | Details |
---|---|
Name | DatabaseDetail name |
NameFormat | "Mainframe" |
ShortDescription | DatabaseDetail instance |
Description | DatabaseDetail name |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | "IBM" |
MFIntegrationID | MFPart mf_integration_id |
Model | DatabaseDetail type |
SerialNumber | DatabaseDetail instance |
Category | "Miscellaneous" |
Type | "Instance" |
Item | "Database" |
BMC_DataBase relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency | MANAGEDDATABASE | BMC_SoftwareServer | BMC_DataBase Impacted |
BMC_SystemResource
Resources such as table spaces inside databases are represented as DatabaseDetail nodes. These are mapped to BMC_SystemResource CIs:
Attribute | Details |
---|---|
Name | DatabaseDetail key |
NameFormat | "Mainframe" |
ShortDescription | DatabaseDetail name |
Description | DatabaseDetail key |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | "IBM" |
MFIntegrationID | MFPart mf_integration_id |
Model | DatabaseDetail type |
SerialNumber | DatabaseDetail instance |
Category | "Unknown" |
Type | DatabaseDetail type |
Item | "BMC Discovered" |
MQ resources are represented as Detail nodes related to MQ Software Instance nodes. These are also mapped to BMC_SystemResource CIs:
Attribute | Details |
---|---|
Name | Detail key |
NameFormat | "Mainframe" |
ShortDescription | Detail name |
Description | Detail key |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | "IBM" |
MFIntegrationID | MFPart mf_integration_id |
Model | Detail type |
SerialNumber | Detail instance |
Category | "Unknown" |
Type | Detail type |
Item | "BMC Discovered" |
BMC_SystemResource relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency | SYSTEMRESOURCES | BMC_SoftwareServer | BMC_SystemResource (Database detail) |
BMC_Dependency | SYSTEMRESOURCES | BMC_SoftwareServer | BMC_SystemResource Impacted (MQ resources) |
BMC_Dependency | DATABASEINDEXSPACE | BMC_DataBase | BMC_SystemResource Impacted |
BMC_Dependency | DATABASEPAGESET | BMC_DataBase | BMC_SystemResource Impacted |
BMC_Dependency | DATABASETABLESPACE | BMC_DataBase | BMC_SystemResource Impacted |
BMC_Transaction
Transactions within IMSTM and CICS are represented as Detail nodes related to Software Instance nodes. These are mapped to BMC_Transaction:
Attribute | Details |
---|---|
Name | Detail key |
NameFormat | "Mainframe" |
ShortDescription | Detail name |
Description | Detail key |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | "IBM" |
MFIntegrationID | MFPart mf_integration_id |
Model | Detail type |
SerialNumber | Detail instance |
Category | "Unknown" |
Type | "Unknown" |
Item | "BMC Discovered" |
BMC_Transaction relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency | SERVERTRANSACTION | BMC_SoftwareServer | BMC_Transaction Impacted |
BMC_Activity
Programs within Transactions are represented as further Detail nodes contained inside the Transaction Detail nodes. These are mapped to BMC_Activity:
Attribute | Details |
---|---|
Name | Detail name |
NameFormat | "Mainframe" |
ShortDescription | Detail name |
Description | Detail name |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | "IBM" |
Model | Detail type |
SerialNumber | Detail instance |
Category | "Unknown" |
Type | "Unknown" |
Item | "BMC Discovered" |
BMC_Activity relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency | TRANSACTIONPROGRAM | BMC_Activity | BMC_Transaction Impacted |
BMC_ConcreteCollection
FunctionalComponent nodes representing CAM Functional Components are mapped to BMC_ConcreteCollection.
Attribute | Details |
---|---|
Name | Functional Component name |
ShortDescription | Functional Component name |
Description | Functional Component name |
Model | Functional Component type |
Company | MFPart Company |
Category | "Software" |
Type | "Application" |
Item | "Functional Component" |
Functional Component relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Component | ITEMINFUNCTIONALCOMPONENT | BMC_ConcreteCollection | BMC_SoftwareServer First-order SI. |
BMC_Component | ITEMINFUNCTIONALCOMPONENT | BMC_ConcreteCollection | BMC_ApplicationSystem Second-order SI. |
BMC_Component | ITEMINFUNCTIONALCOMPONENT | BMC_ConcreteCollection | BMC_ApplicationService |
BMC_Component | ITEMINFUNCTIONALCOMPONENT | BMC_ConcreteCollection | BMC_Cluster |
BMC_Component | ITEMINFUNCTIONALCOMPONENT | BMC_ConcreteCollection | BMC_DataBase |
BMC_Component | ITEMINFUNCTIONALCOMPONENT | BMC_ConcreteCollection | BMC_Application |
BMC_Component | FUNCTIONALCOMPONENTINAPPLICATION | BMC_Application | BMC_ConcreteCollection |
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
TokenId rules
TokenId is an attribute that, in some circumstances, aids the reconciliation of CIs populated by multiple data sources. BMC Helix Discovery sets TokenId depending on the Node kind.
For most Nodes, TokenId is one of the forms:
key
or
ADDM:%key%
or
ADDM:%hashed_key%
For databases, TokenId is a database host found as a result of all possible combinations of where the database might be running:
%hosting_ci.TokenId%:%database_node.type%:%si_instance%:%database_node.instance%
and
%hosting_ci.Name%:%database_node.type%:%si_instance%:%database_node.instance%
For the Fibre Channel Node, TokenId is of the form:
WWN:%wwpn%
For physical hosts, TokenId is of the form:
%host.hostname%:%host.dns_domain%
If the domain name is unavailable, then
%host.hostname%
For virtual hosts that are running in the cloud, TokenId contains instance_id.
- For Alibaba, TokenId is of the form:
%alibaba_instance_id%
- For Azure, TokenId is of the form:
%azure_vm_id%
- For AWS, TokenId is of the form:
%aws_instance_id%
- For GCP, TokenId is of the form:
%gce_instance_id%
- For IBM, TokenId is of the form:
%instance_id%
- For OCI, TokenId is of the form:
%ocid%
For virtual hosts that are running in the hypervisor, TokenId contains UUID.
- For AHV, TokenId is of the form:
AHV-UUID:%uuid%
- For 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:
HYPERV-ID:%vm_uuid%
- For KVM (including RedHat Enterprise Virtualization), TokenId is of the form:
KVM-ID:%uuid%
- For VMware, TokenId is of the form where each letter represents a hexadecimal digit:
VI-UUID:%uuid%
- For Xen (including Oracle VM), TokenId is of the form:
XEN-ID:%uuid%
The following table shows how TokenId looks like for different Node Kinds:
Node Kind | CI | TokenId |
---|---|---|
AdminCollection | BMC_AdminDomain | key |
Cluster (cloud) | BMC_Cluster | key |
LoadBalancerService | BMC_LogicalSystemComponent | ADDM:%key% |
LoadBalancerPool | BMC_ResourcePool | ADDM:%key% |
CloudManagementGroup | BMC_AdminDomain | cloud_id |
CloudProvider | BMC_CloudInstance | key |
CloudRegion | BMC_CloudInstance | key |
CloudService | BMC_CloudInstance | key |
Cluster | BMC_Cluster | ADDM:%hashed_key% |
Database (cloud) | BMC_DataBase | ADDM:%key% |
Database
| BMC_DataBase
| %hosting_ci.TokenId%:%database_node.type%:%si_instance%:%database_node.instance% |
%hosting_ci.Name%:%database_node.type%:%si_instance%:%database_node.instance% | ||
HardwareComponent | BMC_HardwareSystemComponent | ADDM:%hashed_key% |
HardwareContainer | BMC_ComputerSystem | ADDM:%hashed_key% |
HostContainer | BMC_ComputerSystem | ADDM:%hashed_key% |
Host
| BMC_ComputerSystem
| %host.hostname%:%host.dns_domain% |
%host.hostname% | ||
ALIBABA-ID:%alibaba_instance_id% | ||
AWS-ID:%aws_instance_id% | ||
GCP-ID:%gce_instance_id% | ||
IBM-ID:%instance_id% | ||
OCI-ID:%ocid% | ||
AZURE-ID:%azure_vm_id% | ||
HYPERV-ID:%vm_uuid% | ||
XEN-ID:%uuid% | ||
KVM-UUID:%uuid% | ||
AHV-UUID:%uuid% | ||
VI-UUID:%uuid% | ||
LoadBalancerGroup | BMC_Cluster | ADDM:%key% |
MFPart | BMC_ComputerSystem | key |
Namespace | BMC_AdminDomain | key |
Deployment | BMC_ConcreteCollection | key |
NetworkService | BMC_LogicalSystemComponent | ADDM:%key% |
FibreChannelPort | BMC_NetworkPort | WWN:%wwpn% |
SoftwareCluster | BMC_Cluster | ADDM:%hashed_key% |
SoftwareComponent | BMC_ApplicationService | ADDM:%hashed_key% |
SoftwareInstance | BMC_ApplicationSystem | ADDM:%hashed_key% |
SoftwareInstance | BMC_SoftwareServer | ADDM:%hashed_key% |
VirtualMachine | BMC_VirtualSystemEnabler | ADDM:%hashed_key% |
StorageDevice | BMC_Cluster | ADDM:%key% |
StoragePool | BMC_ResourcePool | ADDM:%key% |
StorageSystemGroup | BMC_Cluster | ADDM:%key% |
StorageProcessor | BMC_HardwarePackage | ADDM:%key% |
HardwareContainer | BMC_HardwareSystemComponent | ADDM:%hashed_key% |