The following is a list of the considerations for your LDAP directory:
A directory server must be installed, configured and running before you run the Directory Preparation Script.
You must run the Directory Preparation Script on every machine on which a directory server resides.
If you add an additional machine (such as a replica) at a future date, run the Directory Preparation Script against it, too.
For a list of the LDAP directory servers supported by Calendar Server 62005Q4, refer to Chapter 1, Sun Java System Calendar Server 6 2005Q4 Release Notes, in Sun Java System Communications Services 2005Q4 Release Notes.
If you have customized your LDAP directory, the following considerations may apply:
If you have indexed some attributes, you may have to reindex those attributes after the Directory Preparation Script runs.
If you have added other .ldif files (schema definitions), they should not be affected, so no action should be necessary. However, back up your custom schema definition files before running the Directory Preparation Script.
For all customizations, including the first two just listed, stop the Directory Preparation Script after it generates the script and before it actually updates the LDAP directory. Then inspect the script to evaluate how its proposed actions will affect your LDAP directory. Take whatever actions you think necessary to protect your customizations before running the script against your LDAP.
If you are not using a Sun product for your directory server, the simplest solution for deploying the Calendar Server is to upgrade your directory server to the Sun Java System Directory Server.
For information about installing and configuring a Directory Server, see http://docs.sun.com/coll/1316.1.
Alternately, you can use the script generated by the Directory Preparation Script (without actually running the script) to understand the updates you need to make to your non-Sun LDAP directory.