ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzalv_5.4.0.1/rzalv_plan_domain.htm

70 lines
5.9 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="Plan an Enterprise Identity Mapping domain" />
<meta name="DC.Relation" scheme="URI" content="rzalv_plan_eim_for_eserver.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="rzalv_plan_domain" />
<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>Plan an Enterprise Identity Mapping domain</title>
</head>
<body id="rzalv_plan_domain"><a name="rzalv_plan_domain"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Plan an Enterprise Identity Mapping domain</h1>
<div><p>Part of the initial Enterprise Identity Mapping (EIM) implementation planning process requires that you define an EIM domain. To gain the maximum benefit from having a centralized repository of mapping information, you need to plan for the domain to be shared between many applications and systems. </p>
<p>As you work through the EIM planning topic, you will gather the information that you need to define the domain and to record it on the planning work sheets. The example sections from the work sheets may help guide you to gather and record this information at each planning stage in this topic.</p>
<p>The following table lists the information you need to gather when planning your domain and suggests the EIM implementation team role or roles that could be responsible for each information item needed. </p>
<div class="note"><span class="notetitle">Note:</span> Although the table lists a particular role as a suggestion for assigning the responsibility of gathering the described information, you should assign roles based on the needs and security policy for your organization. For example, in a smaller organization you may prefer to designate a single person as the EIM administrator to be responsible for all aspects of planning, configuration, and managing EIM. </div>
<div class="p">
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 1. Information needed for EIM domain planning</caption><thead align="left"><tr><th align="left" valign="top" width="50%" id="d0e27">Information needed</th>
<th valign="top" width="50%" id="d0e29">Role </th>
</tr>
</thead>
<tbody><tr><td valign="top" width="50%" headers="d0e27 ">1. Whether there is an existing domain to use that suits your needs, or if you should create one.</td>
<td valign="top" width="50%" headers="d0e29 ">EIM administrator</td>
</tr>
<tr><td valign="top" width="50%" headers="d0e27 ">2. Which directory server will act as the EIM domain controller. (See <a href="rzalv_plan_controller.htm#rzalv_plan_controller">Plan an EIM domain controller</a> for detailed information about choosing a domain controller.)</td>
<td valign="top" width="50%" headers="d0e29 ">Directory server (LDAP) administrator or EIM administrator </td>
</tr>
<tr><td valign="top" width="50%" headers="d0e27 ">3. A name for the domain. (You can also provide an optional description.)</td>
<td valign="top" width="50%" headers="d0e29 ">EIM administrator</td>
</tr>
<tr><td valign="top" width="50%" headers="d0e27 ">4. Where in the directory to store EIM domain data. <div class="note"><span class="notetitle">Note:</span> Depending on your choice of system for hosting the directory server and your choice of a directory for storing EIM domain data, you may need to perform some directory services configuration tasks before the domain can be created.</div>
</td>
<td valign="top" width="50%" headers="d0e29 ">Both the directory server (LDAP) administrator or EIM administrator </td>
</tr>
<tr><td valign="top" width="50%" headers="d0e27 ">5. The applications and operating systems that will participate in the domain. If you are configuring your first domain, this initial set may consist of as few as one system. (See <a href="rzalv_reg_plan.htm#rzalv_reg_plan">Develop an EIM registry definition naming plan</a> for more information.)</td>
<td valign="top" width="50%" headers="d0e29 ">EIM team</td>
</tr>
<tr><td valign="top" width="50%" headers="d0e27 ">6. The people and entities that will participate in the domain. <div class="note"><span class="notetitle">Note:</span> To make initial testing easier, you may want to limit the number of participants to one or two.</div>
</td>
<td valign="top" width="50%" headers="d0e29 ">EIM team</td>
</tr>
</tbody>
</table>
</div>
</div>
<p>Now that you have an understanding about what you will need to define your EIM domain, you can begin to <a href="rzalv_plan_controller.htm#rzalv_plan_controller">plan an EIM domain controller</a> for storing EIM domain data.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalv_plan_eim_for_eserver.htm">Plan Enterprise Identity Mapping for eServer</a></div>
</div>
</div>
</body>
</html>