Previous Topic: Create and Manage Relationships with USM Web ViewNext Topic: Delete Relationships


Create Relationships

You can create relationships to establish associations between CIs. When you create relationships, consider the following nonrecommended scenarios that the Web View does not prevent:

Follow these steps:

  1. Perform a search or browse for the CI that you want to be the source in the relationship.

    The USM Properties page opens for the CI you select.

  2. Click From this CI or To this CI in the Relationships section to create the correct directional relationship.

    The Create New Relationship page displays.

  3. Complete the following mandatory fields:
    Semantic

    Specifies the relationship type. Select one of the BinaryRelationship types defined in the USM schema.

    Source

    Defines the source CI in the relationship. This field is already populated with the CI you originally selected. You can change the source CI if necessary.

    Target

    Defines the target CI in the relationship. Click the field to open an embedded instance of the USM Web View Starting page from which you can find and select the target CI. Click the Select this link when you find the appropriate CI to populate the Target field.

    All required fields are defined.

  4. Complete the remaining optional fields.

    Note: The remaining optional fields vary depending on the CI selected.

  5. (Optional) Complete any of the optional fields as necessary. For more information, see the descriptions to the right of each field.
  6. Click Submit Changes.

    The relationship is created between the CIs within the service defined in the scope field. If the CIs did not already exist in the service, they are added with the new relationship.

Note: Creating/modifying entities using the USM Web View creates/modifies CIs/relationships in the same way as they would be created by a separate connector, which shows up as the “Update of the Persistent Store” data source. The properties in these entities take priority over properties from other connectors in the reconciliation process, and therefore they “override” the values from other connectors.