Use this information to learn about creating a group registry definition in an EIM domain that describes and represent a group of registry definitions.
Logically grouping the registry definitions allows you to reduce the amount of work that you must perform to configure EIM mapping. You can manage a group registry definition similarly to the way that you manage an individual registry definition.
All members of the group registry definition typically contain at least one common user identity to which you want to create a target or source association. By grouping members together you are able to create only one association, rather than multiple associations, to the group registry definition and user identity.
For example, John Day logs on to his primary system with a user identity of jday and uses the same user identity, JOHND, on multiple systems. Therefore, the user registry for each system contains the JOHND user identity. Typically, John Day creates a separate target association from the John Day EIM identifier to each of the individual user registries that contain the JOHND user identity. To reduce the amount of work that he must perform to configure EIM mapping, he can create one group registry definition with all the user registries that hold the JOHND user identity as members of the group. He is then able to create a single target association from the John Day EIM identifier to the group registry definition rather than multiple target associations from the John Day EIM identifier to each of the individual registry definitions. This single target association to the group registry definition allows John Day's user identity of jday to map to the JOHND user identity.
Read the following information about group registry definitions:
