Planning an Enterprise Identity Mapping domain

 

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, plan for the domain to be shared between many applications and systems.

As you work through the EIM planning topic, you will gather the information that 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.

The following table lists the information gather when planning your domain and suggests the EIM implementation team role or roles that could be responsible for each information item needed.

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.

Table 1. Information needed for EIM domain planning

Information needed	Role
1. Whether there is an existing domain to use that suits your needs, or if you should create one.	EIM administrator
2. Which directory server will act as the EIM domain controller. (See Planning an Enterprise Identity Mapping domain controller for detailed information about choosing a domain controller.)	Directory server (LDAP) administrator or EIM administrator
3. A name for the domain. (You can also provide an optional description.)	EIM administrator
4. Where in the directory to store EIM domain data. 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.	Both the directory server (LDAP) administrator or EIM administrator
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 Developing an Enterprise Identity Mapping registry definition naming plan for more information.)	EIM team
6. The people and entities that will participate in the domain. To make initial testing easier, you may want to limit the number of participants to one or two.	EIM team

Now that you have an understanding about what you will need to define your EIM domain, you should view Planning an Enterprise Identity Mapping domain controller for information on storing EIM domain data.

 

Parent topic:

Planning Enterprise Identity Mapping for eServer