This section covers information you need to understand before running the Directory Preparation Script, and contains the following topics:
The Directory Preparation Script proceeds through three steps, as follows:
Collects your choices for utility options.
For a list of the specific information this step requests, see Information You Need to Gather.
Generates a shell script and LDIF file from your options choices that will be used to modify the LDAP directory. If you are not using a Sun product for your directory server, or have customized your Directory Server, stop the process here without running the shell script. For further information, see Directory Server Considerations that follows.
Runs the shell script created from your options choices. Your LDAP is modified accordingly.
At the end of each step, the utility asks you if you want to continue. No changes are made to the LDAP directory until the third step.
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 the same machine as your directory server.
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.
During the first step of the Directory Preparation Script, it requests information about your Directory Server. Prepare for this by gathering the information shown in The following table. (To help you keep track of this information, use Appendix A, Directory Configuration Worksheet.
Information Item Needed |
Default Value |
---|---|
Directory Server root path name |
/var/opt/mps/serverroot |
Which instance of Directory Server to use? (If more than one.) |
N/A |
Directory Manager Distinguished Name (DN) |
"cn=DirectoryManager" |
Directory Manager's Password |
N/A |
Directory Server being used for user/group data? (yes), or configuration data only? (no) |
yes |
User and group root suffix (if yes to previous question) |
“o=usergroup” |
Schema version? (pick one of the following) 1 Schema 1 1.5 Schema 2 Compatibility Mode 2 Schema 2 Native Mode [For more information on how to choose a schema, see About the Schema Choices. If you have one version of the schema installed and want to upgrade to a higher level, refer to the Sun Java System Communications Services 6 2005Q4 Schema Migration Guide before running this utility.] |
1 |
Root suffix (if using Schema 1 or Schema 2 Compatibility Mode) [If you choose Schema 1 or 1.5, you will need a DC tree. If the DC tree does not yet exist, the Directory Preparation Script creates only the root suffix node, its does not create the rest of the DC tree. You must create the rest of your DC tree yourself.] |
o=internet |
Update schema? [If this Directory Server is being used for user/group data, you must have a config directory containing the schema files.] |
yes |
Add Directory Server indexes? (adds icsCalendar, icsCalendarOwned) [If you answer yes, the Directory Preparation Script does the indexing for Messaging Server, Calendar Server, and Communications Server, even if you are not using all of them.] |
yes |
Calendar Server supports the following schema choices:
Corresponds to the Directory Preparation Script schema version choice 1.
Sun LDAP Schema 2 compatibility mode
Corresponds to schema version choice 1.5.
Sun LDAP Schema 2 native mode
Corresponds to schema version choice 2.
If you are still trying to decide which schema to use, for further explanation, see the Sun Java Enterprise System Technical Overview, the Sun Java Enterprise System 2005Q4 Installation Guide for UNIX, and theSun Java System Communications Services 6 2005Q4 Schema Migration Guide.
The following table lists simplified guidelines which summarize why you might choose each of the schema versions for your installation.
If you are using Schema 2, Access Manager must be installed and configured.
Do not use the Access Manager console to administer users. For information on how to administer users, see Chapter 14, Administering Users and Resources.
Attribute indexes improve the performance of search algorithms. The script offers to index attributes. If you choose to do so, it will add indexes not only for Calendar Server, but also for Messaging Server and Communications Express. Therefore, once you have run the indexing for one product, you do not need to reindex for the other product. In deed, if you try to index the same attributes again, nothing happens. The script calls db2index for each attribute being indexed, but only if the index does not already exist.
The following table lists all the attributes the Directory Preparation Script indexes, grouped by suffix category. It also lists the type of indexes created for each attribute. For more information about Directory Server indexing, see http://docs.sun.com/coll/1316.1.
Suffix |
Attributes Indexed |
Type of Indexes Added |
---|---|---|
User/Group |
|
pres,eq,approx,sub |
mailAlternateAddress |
pres,eq,approx,sub |
|
mailEquivalentAddress |
pres,eq,approx,sub |
|
member |
eq |
|
cosspecifier |
pres |
|
User/Group (for Access Manager – Schema 2) |
inetDomainBaseDN |
pres,eq |
sunPreferredDomain |
pres,eq |
|
associatedDomain |
pres,eq |
|
o |
pres,eq |
|
sunOrganizationAlias |
pres,eq |
|
DC Tree (for Schema 1) |
inetDomainBaseDN |
pres,eq |
inetCanonicalDomainName |
pres,eq |
|
Personal Address Book (PAB) |
memberOfManagedGroup |
pres,eq |
memberOfPAB |
pres,eq |
|
memberOfPABGroup |
pres,eq |
|
un |
eq |
|
icsCalendar |
pres,eq,approx,sub |
|
icsCalenarOwned |
pres,eq,approx,sub |
|
New PAB |
displayname |
pres,eq,sub |
MemberOfPiBook |
eq |
|
MemberofPiGroup |
eq |
Should you decide to add further indexes on your own, instructions for adding indexes can be found in the Directory Server documentation.