This documentation supports the 21.3 version of BMC Helix 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


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

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 Helix 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