CMDB dependent relationship rules

  • Release version: Yokohama
  • Updated January 30, 2025
  • 5 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of CMDB Dependent Relationship Rules

    CMDB dependent relationship rules define how Configuration Item (CI) types and relationship types depend on each other within ServiceNow’s Configuration Management Database (CMDB). These rules are essential for identifying dependent CIs, constructing business service maps, prioritizing CI identification, and matching related CIs in payloads. They support Service Mapping and can be customized to incorporate new CI types, helping you model complex service definitions accurately.

    Show full answer Show less

    Key Features

    • Dependent Relationship Rules: Include hosting and containment rules, each representing different relationship perspectives between CIs.
    • Hosting Rules: Define valid pairs of hosting and hosted CIs, typically involving physical or virtual hardware. They specify what CIs run on which resources, enabling accurate CI identification during discovery.
    • Containment Rules: Model the containment hierarchy, showing which CIs contain others, useful for representing logical CIs such as software components. They form hierarchical groups representing service structure.
    • Reference Rules: Primarily used in Cloud Management, they define valid referencing relationships between independent CI types, such as virtual machines referencing images.
    • Rule Management: Hosting and containment rules are managed via the CI Class Manager and Metadata Editor, with data stored in dedicated CMDB metadata tables.
    • Rules Requirements and Constraints: Ensure logical consistency by restricting CI types’ roles in hosting and containment rules, preventing loops and invalid configurations.

    Practical Use for ServiceNow Customers

    By creating and managing dependent relationship rules, you can:

    • Precisely define dependencies among CI types, improving the accuracy of service maps and impact analysis.
    • Control the order of CI identification during Discovery, ensuring foundational CIs are identified before dependent ones.
    • Support complex service definitions by establishing clear hosting, containment, and referencing relationships.
    • Customize your CMDB to include new CI types and accurately model their relationships to existing infrastructure.
    • Leverage Service Mapping more effectively by providing a structured dependency framework.

    Next Steps

    • Access and manage dependent relationship rules using the CI Class Manager and Metadata Editor in your ServiceNow instance.
    • Define hosting and containment rules for your CI classes to reflect your environment’s architecture.
    • Ensure compliance with rules requirements to maintain data integrity and avoid relationship conflicts.
    • Use these rules during Discovery and Service Mapping to enhance CI identification and service modeling.

    Service definitions consist of CI types and relationship types. Dependent relationship rules define the dependency structure of the CI types and the relationship types in these service definitions, helping in CI identification and in the construction of business service maps.

    The dependencies that are defined by these rules are used when identifying dependent CIs to prioritize the order of CI identification, and to match CIs and respective dependent CIs in a payload. Dependent relationship rules are also used by Service Mapping and can be defined for custom CI types. After defining a new CI type, you can define dependent relationship rules that specify how the new CI type is related to existing types in the CMDB.

    Dependent relationship rules consist of hosting and containment rules (dependent relationship rules), each type modeling the data from a different perspective of the CI. Containment rules represent CIs' configuration hierarchy, describing which CI contains which other CIs. Hosting rules represent CIs' placement in a business definition, describing what CIs run on.

    Both hosting and containment rules describe a relationship type between two CI types and the same relationship type can be used in a hosting rule and in a containment rule. It is the context in which the relationship is used that distinguishes between a containment and hosting rule.

    Manage dependent relationship rules:
    • To access rules at the class level, use the CI Class Manager. Navigate to All > Configuration > CI Class Manager.
    • To access grouped rules, use the Metadata Editor. Navigate to All > Configuration > Identification/Reconciliation > Metadata Editor.

    The plugins that have been activated on an instance determine which hosting and containment rules exist in a base system.

    Hosting rules

    Hosting rules represent all the possible valid combinations of pairs of hosting and hosted CIs in the service definition. Hosting rules are a flat set of rules that can be only one level deep, and which always involve resources, typically physical or virtual hardware. Each hosting rule is a stand-alone rule between two CI types, describing either a valid CI type that another CI type can host, or by which another CI type can be hosted. A hosting rule consists of a parent CI type, a relationship type (such as Hosted On::Hosts) and a child CI type. For example, you can have a hosting rule that specifies that the CI type ‘Application’ ‘Runs On::Runs’, the CI type ‘Hardware’.

    A CI can be hosted on multiple resources (such as Windows and Linux). This CI is represented by a hosting rule for the CI with each resource that the CI can be hosted on. During CI identification, the pair of CIs that are being examined, should satisfy at least one hosting rule.

    Hosting rules are stored in the CMDB Metadata Hosting Rules [cmdb_metadata_hosting] table.

    Containment rules

    Containment rules represent the containment hierarchy for a CI type, describing valid objects that a CI type can contain in the service definition, and valid objects that can be contained by the CI type. Containment rules are chained to each other in a containment rules group, with a CI type that is the top-level (root) parent of the group. The collection of containment rules construct a hierarchy-like map of containment relationships. Containment rules are logical concepts used to represent logical CIs, for example to describe software that runs on a server. A containment rule consists of a parent CI type, a relationship type (such as 'Contained By::Contains'), and a child CI type. For example, you might have a containment rule specifying that the CI type ‘Tomcat’ ‘Contains::Contained By' CI type ‘WAR File’.

    Endpoints are special containment rules that specify incoming or outgoing connections in the model, designating the CI types that data of some specified type flows in to or out from the service definition. After adding an endpoint to a containment rule, you cannot add any child rules to the endpoint rule.

    Containment rules are stored in the CMDB Metadata Containment Rules [cmdb_metadata_containment] table.

    Reference rules

    Reference rules are used mostly by Cloud Management to represent all of the possible valid combinations of pairs of referencing and referenced CIs in the service definition.

    • Reference rules are a flat set of rules that can be only one level deep.
    • Reference rules always involve resources, typically virtual entities. Each reference rule is a stand-alone rule between two CI types, describing either a valid CI type that another CI type can reference, or by which another CI type can be referenced. Both the CI classes should be able to live independent of each other.
    • A referencing rule consists of a parent CI type, a relationship type (such as Provisioned From::Provisioned) and a child CI type. For example, you can have a referencing rule that specifies that the CI type ‘Virtual Machine’ Provisioned From::Provisioned, the CI type ‘Image’.
    • A CI can reference multiple resources (for example, a VM Instance can have a reference relation with both the Image and the Hardware templates). This CI is represented by a referencing rule for the CI with each resource that the CI can be referenced from.
    • The reference rule cannot be part of the CI identification.
    • Reference rules are stored in the CMDB Metadata Reference Rules [cmdb_metadata_reference] table.

    Rules requirements

    The rules that you create are bound by the following requirements which narrow the relationships and ensure that only valid options are available in the drop-down lists in the Metadata Editor.
    • Given a CI type that is as a child in a containment rule: Not this CI type or its children can be a top-level (root) parent of any other containment rule, and it cannot be in any hosting rule, either as a parent or as a child.
    • Given a CI type that is a top-level (root) parent of a containment rule: It cannot be a child in a hosting rule (for example, you cannot be hosted on Tomcat, if Tomcat has any containment rules).
    • Given a CI type that is a child in a hosting rule: It cannot be in any containment rule, either as a parent or a child.
    • Given a CI type that is a parent in a hosting rule: It cannot be a child in any containment rule.
    • Hosting rules cannot create loops such as Tomcat –runs_on- VMWare –runs_on- Tomcat.

    Hosting and containment rules model

    Hosting and containment rules.

    Hosting rules that model the diagram:

    Tomcat 'Runs on' Hardware.

    Containment rules that model the diagram:
    • Tomcat 'Contains' Configuration File
    • Tomcat 'Contains' WAR
    • WAR has two endpoints for JDBC with MySQL:
      • Inbound
      • Outbound

    Valid set of rules

    
Tomcat Hosted Linux
Linux Hosted Computer

    The second metadata entry triggers the third requirement, which is satisfied (it is a hosting rule, not a containment rule).