76 lines
5.2 KiB
HTML
76 lines
5.2 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="Group registry definitions" />
|
||
|
|
<meta name="abstract" content="Use this information to learn about creating a group registry definition in an EIM domain that describes and represent a group of registry definitions." />
|
||
|
|
<meta name="description" content="Use this information to learn about creating a group registry definition in an EIM domain that describes and represent a group of registry definitions." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzalveserverregistry.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2002, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2002, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzalvgroupregistrydefinitions" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Group registry definitions</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzalvgroupregistrydefinitions"><a name="rzalvgroupregistrydefinitions"><!-- --></a>
|
||
|
|
<img src="./delta.gif" alt="Start of change" /><!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Group registry definitions</h1>
|
||
|
|
<div><p>Use this information to learn about creating a group registry definition
|
||
|
|
in an EIM domain that describes and represent a group of registry definitions. </p>
|
||
|
|
<p>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.</p>
|
||
|
|
<p>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.</p>
|
||
|
|
<p>For example, John Day logs on to his primary system with a user identity
|
||
|
|
of <samp class="codeph">jday</samp> and uses the same user identity, <samp class="codeph">JOHND</samp>,
|
||
|
|
on multiple systems. Therefore, the user registry for each system contains
|
||
|
|
the <samp class="codeph">JOHND</samp> 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 <samp class="codeph">JOHND</samp> 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 <samp class="codeph">JOHND</samp> user identity as members of the group. He
|
||
|
|
is then able to create a single target association from the <samp class="codeph">John Day </samp>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 <samp class="codeph">jday</samp> to map to the <samp class="codeph">JOHND</samp> user
|
||
|
|
identity.</p>
|
||
|
|
<p>Read the following information about group registry definitions: </p>
|
||
|
|
<ul><li>All of the members (individual registry definitions) of the group registry
|
||
|
|
definition must have the same case sensitivity. </li>
|
||
|
|
<li>All of the members (individual registry definitions) of the group registry
|
||
|
|
definition must be defined in the EIM domain before you can add them to a
|
||
|
|
group registry definition. </li>
|
||
|
|
<li>A registry definition can be a member of more than one group, but you
|
||
|
|
should avoid specifying an individual user registry as a member of multiple
|
||
|
|
group registry definitions because lookup operation might return <a href="rzalvambiguousgroupregistry.htm">ambiguous
|
||
|
|
results</a>. The group registry definition cannot be a member
|
||
|
|
of another group registry definition. </li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalveserverregistry.htm" title="This information explains how you can create a registry definition to hold all your user registries for a system.">EIM registry definitions</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
||
|
|
</html>
|