Planning considerations for an EIM domain controller
Restriction: EIM requirements on LDAP include the following:
- An LDAP directory server that supports the LDAP (Version 3)
protocol. It must also understand the following attributes:
- ibm-entryUUID attribute
- ibmattributetypes: acIEntry, acIPropagate, acISource, entryOwner, ownerPropagate, ownerSource
- New attribute types and object classes for EIM (schema updates)
Table 1 lists the LDAP servers that can be used as an EIM domain controller.
| LDAP servers | Operating system | Hardware |
|---|---|---|
| IBM Directory Server v5.1 | AIX, Linux, Windows 2000 | pSeries or xSeries |
| IBM Tivoli Directory Server LDAP server | z/OS | zSeries |
| OS/400 Directory Services | OS/400 | iSeries |
After reviewing the LDAP directory servers available to you, you
can record your choice in the following work sheet.
| Parameter name and description | Customized value |
|---|---|
ldapHost —
This consists of:
Example:
|
Rules:
- The LDAP server must be configured for your desired bind mechanisms in order for them to operate successfully. Refer to Accessing the EIM domain for more information.
- Before an EIM domain controller can be migrated to the next release, the LDAP administrator must apply the enhanced schema elements to the LDAP directory.
- New EIM lookup applications and administration applications (introduced in z/OS V1R6 or later) will work only with the enhanced domain controller. Existing EIM administration applications continue to work with the enhanced domain controller. However, the new policy and certificate support are not available. For more information regarding EIM client applications, see Planning for EIM client applications.