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.
Enterprise or network level requirements
You must configure one system in your enterprise or network to act as an EIM domain controller, which is a specially configured Lightweight Directory Access Protocol (LDAP) server that stores and provides EIM domain data. There are a number of considerations for choosing which directory services product to use as a domain controller, including the fact that not all LDAP server products provide EIM domain controller support.
Another consideration is the availability of administration tools. One option is that you can use the EIM APIs in your own applications to perform administrative functions. If you plan to use the IBM® Tivoli® Directory Server for IBM i as the EIM domain controller, you can use IBM Navigator for i to manage EIM. If you plan to use the IBM Directory product, you can use the eimadmin utility.
You can find more detailed information about choosing a directory server to provide EIM domain controller support in Plan an EIM domain controller.
System and application requirements
Each system that participates in an EIM domain must meet the following requirements:
- Have LDAP client software installed.
- Have an implementation of the EIM APIs.
Each application that will participate in an EIM domain must be able to use the EIM APIs to perform mapping lookup and other operations.
A platform does not have to be able to serve as an EIM domain controller to participate in an EIM domain.
As long as a platform provides EIM client (API) support that system can participate in an EIM domain. It is not necessary that a platform provide EIM domain controller support unless you want to use that particular platform as the EIM domain controller for your enterprise.