Sun Java System Calendar Server 6.3 Administration Guide

ProcedureTo Enable and Configure the LDAP Data Cache for Calendar Server Version 6.3

Before You Begin

For overview information about the LDAP Data Cache, see 1.7 LDAP Data Cache Option for Calendar Server Version 6.3.

  1. Log in as an administrator with permission to change the configuration.

  2. Change to the /etc/opt/SUNWics5/cal/config directory.

  3. Save your old ics.conf file by copying and renaming it.

  4. Enable the LDAP data cache by editing the parameter as shown in the following table:


    Description and Default Value  


    Enable or disable the LDAP cache. If “yes”, the cache is enabled. If “no” the cache is disabled. The default is “no”.


    Specifies the number of seconds for the checkpoint thread to sleep. The default time is 60 seconds. 


    Specifies whether or not to remove the database log files after they have been processed. The default is "yes" .


    Specifies the physical location of LDAP data cache database. The default is:  



    Specifies the maximum size in megabytes of the checkpoint file. The default is 10 megabytes. 


    Specifies the maximum number of threads for the LDAP data cache database. The default is "1000" .


    Specifies the number of megabytes of shared memory. The default is "4" megabytes.


    Not currently implemented. 

    Specifies the time to live (TTL) in seconds for an LDAP data cache entry. The default is "3600" seconds (1 hour).


    Specifies whether or not to log the access to the LDAP data cache and to print statistics in the log file. The default is no .  

    Note –

    This parameter applies only to debug mode.


    Specifies the interval in seconds when each statistics report is written to the log file. The default is "1800" seconds (30 minutes).


    Specifies the interval in seconds between each database cleanup. The default is "1800" seconds (30 minutes).

  5. Save the file as ics.conf.

  6. Restart Calendar Server.


See Also

For information about tuning the LDAP data cache, see 21.5 Improving Performance of the LDAP Data Cache.

Caution – Caution –

If Calendar Server or the server where Calendar Server is running is not properly shut down, manually delete all files in the ldap_cache directory to avoid any database corruption that might cause problems during a subsequent restart.