After gathering the necessary server and client profile information, you set up the Oracle Directory Server Enterprise Edition for LDAP. You use the idsconfig to build the directory information tree with the definitions on your checklists.
When you create the DIT using the idsconfig command, you effectively build the client profile and its attributes as listed in Table 3–1. Store client profiles in a well-known location on the LDAP server. A single profile on the server provides the advantage of defining the configuration of all the clients that use that server. Any subsequent change to the profile attributes is propagated automatically to the clients. The root DN for the given domain must have an object class of nisDomainObject and a nisDomain attribute containing the client's domain. All profiles are located in the ou=profile container relative to this container. These profiles should be readable anonymously.
You can create the directory definitions from any Oracle Solaris system on the network. However, in this case, the output of the idsconfig command includes the Directory Manager's password in clear text. As an alternative to avoid publishing the password, issue the command on the directory server itself.
For more information about the idsconfig command, see the idsconfig (1M) command man page.