Planning Enterprise Identity Mapping for eServer™

An implementation plan is essential to successfully configuring and using Enterprise Identity Mapping (EIM) in a mixed platform enterprise. To develop your implementation plan, you need to collect data about the systems, applications, and users that will use EIM. You will use the information you gather to make decisions about how best to configure EIM for a mixed platform environment.

The following list provides a roadmap of the planning tasks that you should complete before configuring and using EIM in a mixed platform environment. Read through the information in these pages to learn how to successfully plan your EIM configuration needs, including what skills your implementation team needs, what information you need to gather, and configuration decisions you need to make. You may find it helpful to print the EIM planning work sheets (number 8 in the list below) so you can complete them as you work through the planning process.

  1. Enterprise Identity Mapping setup requirements for eServer
    To implement Enterprise Identity Mapping (EIM) successfully, you must meet three requirements: enterprise or network level, system, and application.
  2. Identifying needed skills and roles
    Enterprise Identity Mapping (EIM) is designed so that a single person can easily be responsible for configuration and administration in a small organization. Or, in a larger organization, you may prefer to have a number of different individuals handle these responsibilities.
  3. 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, you need to plan for the domain to be shared between many applications and systems.
  4. Planning an Enterprise Identity Mapping domain controller
    As you gather information to define your Enterprise Identity Mapping (EIM) domain, you need to determine which directory server product will act as the EIM domain controller.
  5. Developing an Enterprise Identity Mapping registry definition naming plan
    To use Enterprise Identity Mapping (EIM) to map the user identity in one user registry to an equivalent user identity in another user registry, both user registries must be defined to EIM.
  6. Developing an identity mapping plan
    A critical part of the initial Enterprise Identity Mapping (EIM) implementation planning process requires that you determine how you want to use identity mapping in your enterprise.
  7. Enterprise Identity Mapping implementation planning worksheets
    As you work through the Enterprise Identity Mapping (EIM) planning process, you might find it helpful to use these worksheets to gather information that you will need to configure and use EIM in your enterprise. Examples of completed sections of the worksheets are provided in the planning pages as appropriate.
  8. Planning for Enterprise Identity mapping application development
    For an application to use Enterprise Identity Mapping (EIM) and participate in a domain, that application must be able to use the EIM APIs.
Parent topic: Planning for Enterprise Identity Mapping