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 nameClass description
BMC_DependencyBMC_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_ComponentBMC_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_MemberOfCollectionBMC_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_ElementLocationBMC_ElementLocation associates  ManagedElement with a Location for positioning, inventory, maintenance, and similar purposes.
Was this page helpful? Yes No Submitting... Thank you

Comments