This documentation supports the 20.02 version of BMC CMDB.

To view an earlier version, select the version from the Product version menu.

Base level and first level classes in the Common Data Model

This sections provides details about some of the base level and first level classes that are available in the Common Data Model. 

Base level and first level configuration item classes in the Common Data Model 

The following table describes the BMC_BaseElement Configuration Item (CI) class and its subclasses in the Common Data Model (CDM). Most CI classes have subclasses that help further define a CI class. 

For a complete list of CI classes and subclasses in the Common Data Model, you can view the CDM Help or the CDM diagram at PDFs and videos.

 CI classes in the Common Data Model

Class

Description

BMC_BaseElement

As the superclass for all other CI classes, BMC_BaseElement is key to the design of the CDM. Though you are unlikely to create any instances of this class, you can use its form as a single place to query for all configuration items. Attributes of this class are inherited by all CI classes. In addition to the attributes, such as Name that is populated for all CIs, BMC_BaseElement contains the core attributes such as InstanceId, ReconciliationIdentity, and ClassId that are populated automatically by the BMC CMDB. It even includes several display-only attributes for which values are set temporarily and then discarded.

BMC_AccessPoint

The BMC_AccessPoint class represents the ability to use or invoke a service. Its subclasses include different types of endpoints, such as IP endpoints and LAN endpoints.

BMC_Collection

The BMC_Collection class and its subclasses store information about physical collections, such as subnets and LANs, and logical collections, such as roles and user communities.

BMC_Document

The BMC_Document class stores information about documentation in your environment, such as design and regulation-compliance requirements.

BMC_Equipment

The BMC_Equipment class stores information about physical equipment that is not related to computing. This can include buildings, vehicles, and other facilities related items.

BMC_LogicalEntity

The BMC_LogicalEntity class tree provides mechanisms for grouping configuration items together into logical elements. This includes business processes, services, and physical locations.

BMC_Person

The BMC_Person class stores information about the people who manage and depend on the other CIs in your environment.

BMC_Settings

The BMC_Settings class is an abstract class under which you can create subclasses to provide detailed settings information about a managed element.

BMC_System

The BMC_System class is the superclass for systems such as computer systems, mainframes, application systems, clusters, printers, virtual systems, and network devices. These systems aggregate a set of managed components.

BMC_SystemComponent

The BMC_SystemComponent class stores information about the components that compose a system. This includes physical components like disk drives, monitors, and so on; applications, such as MS Word and other soft elements, such as network drivers and file shares.

BMC_SystemService

The BMC_SystemService class contains the information necessary to represent and manage services that a device or software provides.


Base level and first level relationship classes in the Common Data Model

The following table describes the BMC_BaseRelationship relationship class and its subclasses in the Common Data Model. Most relationship classes have subclasses that help further define a relationship. These subclasses, which are all categorization classes, can have additional attributes, but most often they further define a relationship only by using different Configuration Item (CI) classes as their members. 

For a complete list of relationship classes in the Common Data Model, you can view the CDM Help or the CDM diagram at PDFs and videos.

 Relationship classes in the Common Data Model

Class

Description

BMC_BaseRelationship

As the superclass for all other relationship classes, BMC_BaseRelationship is key to the design of the CDM. Though you are unlikely to create any instances of this class, you can use its form as a single place to query all relationships. Relationship classes inherit the attributes of these classes. In addition to the attributes such as Name that you populate for all relationships, BMC_BaseRelationship contains the core attributes such as InstanceId, and ClassId that are populated automatically by BMC CMDB. It even includes several display-only attributes for which values are set temporarily and then discarded.

BMC_Component

Used to define composite objects such as a computer system, which is made up of a computer system instance, a disk drive instance, monitors, software, network cards, and so on.

BMC_Dependency

Describes configuration items that are dependent on each other. This relationship can be used to define application dependencies, such as a particular program that is dependent on an application server and database for it to run.

BMC_ElementLocation

Relates any configuration item to a physical location in your environment.

BMC_MemberOfCollection

Used to define groupings of instances in a logical manner. This is used to define network topology, or to define the set of configuration items that make up a business process or service.

BMC_Impact

Represents impact relationships between any CIs.
Note: BMC_Impact is deprecated. To indicate an impact relationship, instantiate any other relationship class and set the HasImpact attribute to Yes. This strategy reflects the fact that members of any type of relationship can impact each other.

BMC_Genealogy

Establishes relationships between a parent virtual machine (VM) and its child VMs. For example, If you have a VM named win2k-vm1 and a clone of that VM named win2k-vm2, the win2k-vm1 VM is the parent and the win2k-vm2 VM is the child.

When creating relationship instances, populate the Name attribute according to the Relationship Normalization table in Mapping Your Data to BMC Atrium CMDB Classes and use the source and destination Configuration Items (CI) classes specified in the table.

The number of relationship classes in the Common Data Model is far fewer than the logical types of relationships that you might want to use, so you can achieve a more granular level of categorization by populating the Name attribute. For example, to specify that a BMC_Component instance represents a product-to-patch relationship, PRODUCTPATCH is used for the Name attribute.

By using only Name values that appear in the Relationship Normalization table, you maintain consistency with relationships created by BMC products, increasing the accuracy of reconciliation. Future releases of BMC CMDB will require compliance with the values in this table for compatibility with BMC products.

Tip

The Normalization Engine sets relationship Name values according to the Relationship Normalization table. For more information about this, see Normalization and best-practice relationship rules.

Federated data classes in the Common Data Model

The following table describes the federated data classes in the Common Data Model.

Federated data classes in the Common Data Model 

Class

Description

BMC_FederatedBaseElement

Base class for federated data. It is an abstract class used to logically group federated data classes. This class has no attributes.

BMC_FederatedBaseRelationship

Base class for relationships between federated data and data stored in BMC CMDB. This class is an abstract class used to logically group federated relationship classes. A federated relationship class is not mapped to any data. Instead, it contains a relationship qualification that acts as a join condition between a data-model class and a federated data class. All federated data relationship classes are derived from BMC_FederatedBaseRelationship.


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

Comments