TOC PREV NEXT INDEX

CorporateTime Server

Administrator's Guide

View in pdf format
Go to Reference Manual


Connecting to your Directory Server


This appendix describes additional configuration procedures necessary to connect your calendar server to your external LDAP directory server.

Critical Path InJoin Directory Server

Configuration of search parameters

To allow for thorough and efficient searches using the calendar server with Critical Path InJoin Directory Server, the following parameters in both servers must be tuned for each installation. The dependencies between the parameters should be understood in order to configure the search behaviour appropriate for your organization.

Calendar server search parameters

Other calendar server configuration parameters

The other configuration parameters that you must set are listed below. Consult Reference Appendix B, "Server Parameters," for correct settings and further details for each of these parameters.

NOTE

The calendar server administrator cannot change a user or resource password through the Admin GUI or any of the utilities uniuser, unires, unipasswd. The user or resource can change their password through a calendar client.

[UTL]

adm_modrespassword

adm_moduserpassword

[LDAP]

attr_uid

groupobjectclass

groupmemberattribute

groupfilter

Support for "\" in T.61 character set

When using pre-3.0 versions of the Critical Path InJoin Directory Server directory server (formerly ISOCOR Global Directory Server), the calendar server converts data to the T.61 character set before it is sent to the directory. If your calendar server is set up this way, note that the T.61 character set does not support the the backslash character "\" without the following modification:

In /etc/charset/T61.MAP (line 93) change:

0x5C<tab>0xFFFD<tab># SUBSTITUTE

to:

0x5C<tab>0x005C<tab># REVERSE SOLIDUS

Syntegra Global Directory Server

Configuration of search parameters

To allow for thorough and efficient searches using the calendar server with Syntegra Global Directory Server, the following parameters in both servers must be tuned for each installation. The dependencies between the parameters should be understood in order to configure the search behaviour appropriate for your organization.

Calendar server search parameters

Syntegra Global Directory Server search parameters

Adding given names

User entries might not have a given name attribute; you may assign given names when adding users to the calendar server.

For example:

A DID=cn=Chris Robbins, ou=Research, o=Acme, c=US/G=Chris

A DID=cn=Thomas Addison, ou=Administration, o=Acme, c=US/G=Thomas

Resource creation

Although this directory server permits the creation of resources above the base DN, it is not recommended as the calendar server will not be able to access the resource after creation.

Netscape Directory Server and iPlanet Directory Server

Configuration of search parameters

To allow for thorough and efficient searches using the calendar server with Netscape Directory Server and iPlanet Directory Server, the following parameters in both servers must be tuned for each installation. The dependencies between the parameters should be understood in order to configure the search behaviour appropriate for your organization.

Calendar server search parameters

Maximum size of returned set for a search
Minimum length of search string

Netscape Directory Server and iPlanet Directory Server search parameters

Size limit
Look through limit
Time limit

Tuning for speed vs flexibility

Two different approaches or options are summarized below:
Table F 1 · Tuning searches
Server Configuration file Parameter Default Value Option 1 Option 2
Calendar server unison.ini maxsearchresult 100 >= configured users dependent on value set for mincharsearch and total number of configured calendar users
" " mincharsearch 0 0 >1
Directory Server slapd.conf sizelimit 200 >= number of users in largest node (minimum value = 200) >= number of users in largest node
" " lookthroughlimit 5000 >= number of users in largest node (minimum value = 200) >= number of users in largest node
" " timelimit 3600 value should be high enough to prevent time-out value should be high enough to prevent time-out

Option 1
Option 2
NOTE

It is recommended that you set the LDAP sizelimit and lookthroughlimit parameters to be equal or greater than the number of users in the largest node. Smaller values may cause problems with the unidsdiff utility. If you need to set these parameters to a smaller value (minimum = 200), then every time you run unidsdiff, you should first increase these values to the recommended level, perform the operation, and then return these parameters to their previous values.

In any case, it is recommended that you do not set sizelimit and lookthroughlimit to any value less than 200.


TOC PREV NEXT INDEX
 
Copyright information