Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Component relationships

Service management relationships are impact relationships.

Note

Relationships that qualify as impact relationships by setting HasImpact=Yes are considered or used by the cell.

The following table lists the main relationship classes that can qualify as impact relationships. These classes have been derived from BMC_BaseRelationship instances. 

Main relationship classes

Class name

Class description

BMC_Dependency

BMC_Dependency describes component relationships that are dependent on each other. This is different from impact relationships in that a dependency can be at a lower, direct level, while an impact is often at a higher, more indirect level.

BMC_Component

BMC_Component is used to define composite objects. One key component relationship in the CMD is between the system and system component classes. This relationship defines a composite computer system, which is made up of a computer system instance and subinstances of disk drives, monitors, software, network cards, and so on.

BMC_MemberOfCollection

BMC_MemberOfCollection is used to define groupings of instances in a logical manner. It is used to define the network topology or the set of CIs that make up a business process or service.

BMC_ElementLocation

BMC_ElementLocation associates  ManagedElement with a Location for positioning, inventory, maintenance, and similar purposes.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*