The Relationship Criteria page lets you define the name of the unmanaged relationship policy and filtering criteria that you want to use to discover an unmanaged relationship. The page also lets you specify the type of managed relationship that you want to create after discovering the unmanaged relationship.
Follow these steps:
Note: Page fields marked with an asterisk (*) are required.
For example, consider a scenario where a connector publishes unmanaged relationships IsHostedBy. These relationships have virtual systems as source CIs and VMWare hosts as target CIs. The service you are populating must have reversed semantic IsHostFor, where the sources are VMWare hosts and targets are virtual systems. In such scenarios, enable the Reverse the created relationships option to reverse the source CI and target CI positions in the managed relationships.
Note: In a typical scenario, an unmanaged relationship policy creates a managed copy of the discovered unmanaged relationship. The created managed relationship has the same semantic (if the Same as Discovered option is used in Step 3), source CI, and target CI as the original unmanaged relationship. However, if you want to swap the source and target CIs positions in the created managed relationship, use this option.
This value specifies the type of managed relationship that you want to create for the discovered unmanaged relationship.
Important! Select Same as Discovered if you want to create a managed relationship of the same type as the discovered relationship.
For USM property definitions, see the USM Schema Documentation that is provided on the CA SOI Bookshelf.
Note: Select at least one option; you cannot leave this field blank.
|
Copyright © 2013 CA.
All rights reserved.
|
|