Sun Java System Calendar Server 6.3 Administration Guide

Part V Appendixes

This part contains the appendixes for the Administration Guide.

Appendix A Directory Configuration Worksheet

This worksheet helps you collect the information you will be asked for when running comm_dssetup.pl. The first column shows you the silent mode options and the expected information that is to follow it. The second column shows you the same option in interactive mode with the default answer.

There is a line provided in the right column for the answer you want to give. It applies to both the silent and interactive modes. For silent mode, use the answers as the value that follows the option. For interactive mode, enter your value at the prompt.

For examples and instructions on how to run comm_dssetup.pl, see the Sun Java System Communications Suite 5 Installation and Configuration Guide.

Table A–1 Directory Server Setup Script (comm_dssetup.pl) Worksheet

Silent Mode Options  

Interactive Dialog and Defaults  

-i yes | no

Add new Directory Server indexes (yes/no). 

Default: yes 

Your value: 

-R yes | no

Reindex now (yes/no). 

Default: yes 

Your value:  

-c Directory Server Root

Directory Server root path name. 

Default: /var/opt/Sun/dsins

Your value:  

-d Directory Server Instance

Directory Server instance subdirectory. 

Default: none 

Your value:  

-r DC Root Suffix

DC Tree root suffix. 

Default: o=internet

Your value:  

-u User and Group Base Suffix

User/Group root suffix. 

Default: o=usergroup

Your value:  

-s yes | no

Update schema (yes/no). 

Default: yes 

Your value:  

-D Directory Manager DN

Directory Manager Distinguished Name (DN). 

Default: "cn=Directory Manager".

Your value:  

-w Directory Manager DN Password

Directory Manager DN password. 

Default: none. 

Your value:  

-b yes | no

Use this directory to store both configuration and user data (yes) or configuration data only (no). 

Default: yes 

Your value:  

-t 1|1.5|2

Schema version: 

  • Option 1 – Schema version 1

  • Option 1.5 – Schema version 2 Compatibility Mode

  • Option 2 – Schema version 2 Native Mode

    Default: 1

    Your value:

-m yes|no

Do you want to modify the directory server? 

Default: yes 

no- prints out script but does not execute it. 

-S PathtoSchemaFile

Path to the directory where the schema files are located. 

Default: ./schema

Your value:  

Appendix B Calendar Server Configuration Worksheet

This appendix contains the following worksheets to help you keep track of the information you need to run the Calendar Server configuration program, which is described in Chapter 2, Initial Runtime Configuration Program for Calendar Server 6.3 software (csconfigurator.sh)

B.1 Administration, User Preferences and Authentication Screen Worksheet

Table B–1 Administration, User Preferences and Authentication Screen Worksheet

Option  

Description  

LDAP Server Host Name 

Host name of the LDAP directory server you are using for user authentication. 

Default: current host. 

Your value:  

LDAP Server Port 

Port number that the LDAP server listens on. 

Default: 389. 

Your value:  

Base DN 

Entry in the LDAP directory used as the starting point from which searches will occur. 

Default: o=host.com.

Your value:  

Directory Manager DN 

User name that can make changes in the directory server schema. 

Default: cn=Directory Manager.

Your value:  

Directory Manager Password 

Password of the Directory Manager DN. 

Default: None 

Your value:  

Administrator User ID 

User ID of the Calendar Server Administrator. This user must be a user in the above LDAP directory server. 

Default: calmaster.

Your value:  

Administrator Password 

Password of the Calendar Server Administrator. 

Default: None 

Your value:  

B.2 Email and Email Alarms Worksheet

Table B–2 Email and Email Alarms Worksheet

Option 

Description 

Email Alarms 

Specifies whether Calendar Server should send an email alarm message to a Calendar Server administrator in case a server problem occurs. 

Default: Enabled. 

Your value:  

Administrator Email Address 

Email address of the Calendar Server Administrator who will receive the email alarm messages. 

Default: None. 

Your value:  

SMTP Host Name 

Host name of the SMTP server where email alarm messages should be sent. 

Default: Current host. 

Your value:  

B.3 Runtime Configuration Worksheet

Table B–3 Runtime Configuration Worksheet

Option 

Description 

Service Port 

Port number that Calendar Server listens on to provide Web (HTTP) access to users. 

Default: 80. 

Your value: 

Maximum Sessions 

Maximum number of Calendar Server sessions. 

Default: 5000. 

Your value: 

Maximum Threads 

Maximum number of Calendar Server threads. 

Default: 20. 

Your value: 

Number of Server Processes 

Maximum number of Calendar Server processes. 

Default: Number of CPU's on the server where you are installing Calendar Server. 

Your value: 

Runtime User ID 

UNIX user name under which Calendar Server will run. 

Default: icsuser.

Your value: 

Runtime Group ID 

UNIX group under which Calendar Server will run. 

Default: icsgroup.

Your value: 

Calendar Server Startup 

Start after successful installation. 

Default: Checked. 

Your value: 

Start on system startup. 

Default: Checked. 

Your value: 

B.4 Database, Logs, and Temporary Files Directories Worksheet

Table B–4 Database, Logs, and Temporary Files Directories Worksheet

Option  

Description  

Database Directory 

Directory where Calendar Server should create and store the calendar database files. 

Default: /var/opt/SUNWics5/csdb

Your value:  

Logs Directory 

Directory where Calendar Server writes log files. 

Default: /var/opt/SUNWics5/logs

Your value:  

Temporary Files Directory 

Directory where the Calendar Server writes temporary files. 

Default: /var/opt/SUNWics5/tmp

Your value:  

Appendix C Calendar Server Configuration Worksheet

C.1 Calendar Server Configuration Worksheet

The following table lists the values you set when you run the Calendar Server configuration program (csconfigurator.sh).

Table C–1 Calendar Server Configuration Worksheet

Component  

Description and Comments  

LDAP Server Host Name 

For example: ldaphost.sesta.com

Your value:  

LDAP Server Port 

Port number that the LDAP server listens on. 

Default: 389. 

Your value:  

Directory Manager DN 

User name that can make changes in the directory server schema. 

Default: cn=Directory Manager.

Your value:  

Directory Manager Password 

Password of the Directory Manager DN. 

Default: None 

Your value: 

Administrator User ID 

User ID of the Calendar Server administrator. This user must be a user in the above LDAP directory server. 

Default: calmaster.

Your value:  

Administrator Password 

Password of the Calendar Server administrator. 

Default: None 

Your value:  

Email Alarms 

Specifies whether Calendar Server should send an email alarm message to a Calendar Server administrator in case a server problem occurs. 

Default: Enabled. 

Your value: 

Administrator Email Address 

Email address of the Calendar Server administrator who will receive the email alarm messages. 

Default: None. 

Your value: 

SMTP Host Name 

Host name of the SMTP server where email alarm messages should be sent. 

Default: Current host. 

Your value: 

Service Port 

Port number that Calendar Server listens on to provide Web (HTTP) access to users. 

Default: 80. 

Your value: 

Maximum Sessions 

Maximum number of Calendar Server sessions. 

Default: 5000. 

Your value: 

Maximum Threads 

Maximum number of Calendar Server threads. 

Default: 20. 

Your value: 

Number of Server Processes 

Maximum number of Calendar Server processes. 

Default: Number of CPU's on the server where you are installing Calendar Server. 

Your value: 

Runtime User ID 

Default value: icsuser

For an HA configuration, add to /etc/passwd on all nodes in the cluster.

Your value:  

Runtime Group ID 

Default value: icsgroup

For an HA configuration, add to /etc/group on all nodes in the cluster.

Your value: 

Calendar Server Startup 

Start after successful installation. 

Default: Checked. 

Your value: For an HA configuration, do not check this option.

Start on system startup. 

Default: Checked. 

Your value: For an HA configuration, do not check this option.

Database Directory 

Default: /var/opt/SUNWics5/csdb

For example: /global/cal/var/opt/SUNWics5/csdb

Your value:  

Logs Directory 

Default: /var/opt/SUNWics5/logs

For example: /global/cal/var/opt/SUNWics5/logs

Your value 

Temporary Files Directory 

Default: /var/opt/SUNWics5/tmp

For example: /global/cal/var/opt/SUNWics5/tmp

Your value: 

Appendix D Calendar Server Command-Line Utilities Reference

For a short description of each utility, see D.2 Short Description of Command-Line Utilities.

Calendar Server provides command-line utilities not included in the Delegated Administrator bundled with Access Manager.

These Calendar Server utilities can be invoked from batch, shell, and scripting programs such as Perl. Some of these utilities (csuser, csresource and csdomain) have been superseded by the Delegated Administrator utility, but the rest are still used, even in a Schema version 2 environment. For Schema version 1, you must continue to use csuser, csresource and csdomain, and not use Delegated Administrator.

If needed, these utilities use default values from the ics.conf configuration file.

The command-line utilities are located in the following directory: cal-svr-base/SUNWics5/cal/sbin

All of the utilities must be started from the sbin directory, with the exception of start-cal and stop-cal which can be run from any directory, if the full path is specified.


Note –

Error messages from these administrative tools are written to the admin.log file found in the csdb directory.


This chapter provides the following information:

D.1 Running the Command-Line Utilities

Run the command-line utilities while logged in as the user and group where Calendar Server is running, or as root. This was specified during installation; the defaults are icsuser and icsgroup.

For example, if your Calendar Server base directory is cal-svr-base, to run the cscal utility list command, you would do the following after logging in:

cd cal-svr-base/SUNWics5/cal/sbin
./cscal list

D.1.1 Syntax for Command-Line Utilities

Calendar Server command-line utilities use the following syntax:

utility [ -option [value]] command [target]

where:

utility is the executable name of the utility, such as cscal or csuser.

option determines which action the command performs. Options are in lowercase and preceded by a hyphen (-), such as -d. An option enclosed in brackets ([]) is optional. If indicated, of two or more options can be used at the same time.

value further qualifies the action specified by option, such as a description used with the -d option. A value enclosed in brackets ([]) is optional. Values that include spaces must be enclosed in quotation marks (" "). Multiple values must be enclosed in quotation marks (""), and each value must be separated by a space, unless indicated otherwise, such as the use of a semicolon delimited list.

command is an action the utility performs such as list or create. Commands separated by a vertical bar (|) indicate that either one (but not both) can be used at the same time.

target is the object on which the command takes effect, such as a calendar ID or user ID.

D.1.2 Usage Rules for Command-Line Utilities

The following rules are general usage guidelines for the command line utilities:

D.1.3 Return Code in Scripts

If you run the command-line utilities from a script, the return code is “0” if the utility run successfully or “-1” for a failure.

D.2 Short Description of Command-Line Utilities

The following table gives a short description the Calendar Server command-line utilities.

Table D–1 Calendar Server Command-Line Utilities Summary

Utility  

Description  

D.3 csattribute

Manages the LDAP attributes of a calendar user or resource for Schema version 1. 

D.4 csbackup

Backs up individual calendars, users, and the calendar database. 

D.5 cscal

Manages calendars and their properties. 

D.6 csclean

Removes user and resource calendars for Calendar Server users whose status attribute (inetUserStatus) has been marked as “deleted” by Delegated Administrator. 

D.7 cscomponents

Manages calendar components: events and tasks (todos). 

D.8 csdb

Manages the calendar database. 

D.9 csdomain

Manages Calendar Server attributes in the domain LDAP entry for Schema version 1. 

D.10 csexport

Exports a calendar in iCalendar (.ics) or XML (.xml) format.

D.11 csimport

Imports a calendar in iCalendar (.ics) or XML (.xml) format.

D.13 cspurge

Allows the manual purge of entries in the Delete Log database (ics50deletelog.db).

D.14 csrename

Allows the renaming of user ID's. Causes the whole database to be rewritten. 

D.15 csresource

Manages calendar resources such as conference rooms and equipment. 

D.16 csrestore

Restores individual calendars, users, and the calendar database. 

D.17 csschedule

Manages scheduling entries in the Group Scheduling Engine (GSE) queue. 

D.18 csstats

Displays counters in a Calendar Server. 

D.19 csuser

Manages calendar users for Schema version 1. 

D.20 start-cal

Starts all Calendar Server processes. 

D.21 stop-cal

Stops all Calendar Server processes. 

D.3 csattribute

The csattribute utility only works in Schema version 1 mode. It manages Calendar Server user or resource LDAP entry attributes. Commands are:


Note –

If your site is using the LDAP CLD plug-in, do not use csattribute to change the icsDWPHost attribute when trying to specify a new back-end host server. Modifying icsDWPHost does not cause a new calendar to be created on the new back-end host. For more information, see Chapter 5, Configuring Calendar Database Distribution Across Multiple Machines in Calendar Server Version 6.3


D.3.1 Requirements

D.3.2 Syntax


csattribute [-q|-v] 
             -a attribute=value 
            [-t resource | user]
            [-d domain] 
            add target

csattribute [-q|-v] 
             -a attribute[=value] 
            [-t resource | user]
            [-d domain] 
            delete target

csattribute [-q | -v] 
            [-t resource | user] 
            [-d domain] 
            list target

The following table describes the commands available for csattribute.

Table D–2 csattribute Utility Commands

Command  

Description  

add target

Adds an LDAP attribute and value to a specified target (user or resource object). 

list target

Lists the attributes of a target object. 

delete target

Deletes an attribute from a target. 

version

Displays the version of the utility. 

The following table describes the csattribute utility command options.

Table D–3 csattribute Utility Command Options

Option 

Description  

-v

Run in verbose mode: Display all available information about the command being performed. Default is off. 

-q

Run in quiet mode: 

  • Display no information if the operation is successful (errors, if they occur, are displayed).

  • Suppress confirmation prompting for dangerous commands.

    Default is off.

-a attribute =value

or 

-a attribute [=value ]

An LDAP attribute and value: 

  • attribute is required when using the -a option.

  • value is required when the -a option is used with the add command, but it is optional when the -a option is used with the delete and list commands.

-t user | resource

Type of target (user or resource object). Default is user. 

[-d domain]

Specifies the name of a domain. Default is taken from the service.defaultdomain parameter in the ics.conf file.

D.3.3 Examples

D.4 csbackup

The csbackup utility backs up the calendar database, a specified calendar, or a user’s default calendar. Commands are:

The caldb.conf version file located in the specified backup directory shows the version number of the database that was backed up.

For information about csrestore, see D.16 csrestore.

D.4.1 Requirements

D.4.2 Syntax


csbackup [-q|-v] 
          -f database target

csbackup [-q|-v] 
          -c calid 
         calendar target

csbackup [-q|-v] 
          -a userid 
         [-b basedn] 
         defcal target

The following table describes the commands available for csbackup.

Table D–4 csbackup Utility Commands

Command  

Description  

database target

Backs up the calendar database to the specified target database directory. By default, the target database directory is: 

cal-svr-base/SUNWics5/cal/sbin/target-directory

If you specify only the target database directory, do not include the slash (/) before the directory name. For example:

csbackup database backupdir

Note: The csbackup utility fails if the target backup directory already exists and you do not specify the -f option. For example, the following command fails if backupdir exists, even if the directory is empty:

csbackup database backupdir

Therefore, if you specify a target backup directory that already exists, include the -f option when you run csbackup.

You can also specify a nonexistent target backup directory and let csbackup create the directory for you.

calendar calid target

Backs up the specified calendar ID to the specified target output file. The data format of the file is assumed by the file extension, .ics for text/calendar or .xml for text/xml.

defcal userid target

Backs up the default calendar of the specified user ID to the specified target file. The data format of the file is assumed by the file extension, .ics for text/calendar and .xml for text/xml.

version

Displays the version of the utility. 

The following table describes the csbackup utility command options.

Table D–5 csbackup Utility Command Options

Option 

Description  

-v

Run in verbose mode: Display all available information about the command being performed. Default is off. 

-q

Run in quiet mode: 

  • Display no information if the operation is successful (errors, if they occur, are displayed).

  • Suppress confirmation prompting for dangerous commands.

    Default is off.

-a userid

The user ID of the calendar user to backup. This option is required for the default option. There is no default. 

-b basedn

The base DN to be used for this user. The default is taken from the setting service.schema2root, defined in the ics.conf file.

The Base DN (distinguished name) is the entry in your LDAP directory used as the starting point from which searches occur. 

For example, if you specify a base DN of ou=people, o=sesta.com, all LDAP search operations executed by Calendar Server examine only the ou=people subtree in the o=sesta.com directory tree.

-c calid

The calendar ID to backup. This option is required with the calendar command. There is no default.

For more information, see 15.2 Creating Calendar Unique Identifiers (calid's).

-f

To force any existing backup files to be deleted. 

In the current release, you must include the -f option if the backup target directory already exists, even if the directory is empty.

-l

To prepare the backup file for use with the SolsticeTM BackupTM or the Legato NetworkerTM backup programs. For more information, see Chapter 17, Backing Up and Restoring Calendar Server Data.

D.4.3 Examples

D.5 cscal

The cscal utility manages calendars and their properties. Commands are:

D.5.1 Requirements

D.5.2 Syntax


cscal [-q|-v] 
      [-a aces] 
      [-c charset] 
      [-d description] 
      [-g categories]
      [-k yes|no] 
      [-l langcode]
      [-m email]
      [-n name] 
      [-o owner’s uid]
      [-y otherowners]
      create|modify calid

cscal [-q|-v] 
      [-o owner’s uid]
      [-O] 
      delete|reset calid

cscal [-q|-v] 
      [-o owner’s uid]
      [-O] 
      disable|list [calid]

cscal [-q|-v] 
      [-k yes|no]
      [-o owner’s uid]
      [-O] 
      enable [calid]

Note –

Despite the fact that cscal does not check case when you enter the -o (owner’s uid), the search is case insensitive.


The following table describes the commands available for the cscal utility.

Table D–6 cscal Utility Commands

Command  

Description 

create calid

Creates the calendar specified by calid. 

Note: If your site is using the LDAP CLD plug-in, all calendars for a specific user must reside on the same back-end server, as indicated by the user’s icsDWPHost LDAP attribute. If you try to create a calendar for the user on a different back-end server, Calendar Server returns an error.

delete calid

Deletes the calendar specified by calid.

If the -o owner option is specified, deletes all calendars whose primary owner is the specified uid.

enable [ calid ]

Enables the calendar specified by calid. If calid is not specified, enables all calendars.

If the -o owner option is specified, enables all calendars whose primary owner is the specified uid.

disable [ calid ]

Disables the calendar specified by calid. If calid is not specified, disables all calendars.

If the -o owner option is specified, disables all calendars whose primary owner is the specified uid.

list [ calid ]

Lists properties of the calendar specified by calid. If calid is not specified, lists properties of all calendars.

If the -o owner's uid option is specified, lists all calendars whose primary owner is the specified owner uid.


Note –

When any of the permissions have been modified through the Calendar Express user interface, this command lists those ACE letters capitalized. There is no significance to this. The ACEs are case insensitive.


modify calid

Modifies the properties of the calendar specified by calid.

reset calid

Resets the properties of the calendar specified by calid to the default configuration settings.

version

Displays the version of the utility. 

The following table describes the cscal utility command options.

Table D–7 cscal Utility Command Options

Option  

Description  

-v

Run in verbose mode: Display all available information about the command being performed. Default is off. 

-q

Run in quiet mode: 

  • Display no information if the operation is successful (errors, if they occur, are displayed).

  • Suppress confirmation prompting for dangerous commands.

    Default is off.

-a [aces]

Access Control Entries (ACE's) for a specified calendar. ACE's determine who can access a calendar for group scheduling and the types of permissions they have, such as create, delete, read, and write privileges. An ACE string or Access Control List (ACL), must be enclosed in quotation marks (" ").

The default is the calstore.calendar.default.acl parameter in the ics.conf file.

For details about the ACE format, see 1.8 Access Control for Calendar Server Version 6.3.

-c charset

Character set. The default is no character set. 

-d description

Description (a viewable comment about the purpose of the calendar). The default is no description. 

-g category

Category. Multiple categories must be enclosed in quotation marks ("") and separated by spaces. The default is no category.

-k yes|no

Specifies whether double booking is allowed for a user calendar. For example, yes means the calendar can have more than one event scheduled for the same time slot.

If the -k option is omitted, the default is taken from the user.allow.doublebook parameter in the ics.conf file. However, the user.allow.doublebook parameter is used only when a calendar is created.

After a calendar is created, Calendar Server checks the calendar properties database, ics50calprops.db, to determine if doublebooking is allowed. If you need to change the calendar properties for a calendar to allow or disallow doublebooking, reissue cscal with the -k option.

-l langcode

Language code. The default is no language code. 

-m email

Email address. The default is no email. 

-n name

Viewable Name. The default is no name. 

-o owner

(Lowercase o) 

Primary owner. The default setting is the unique ID (uid) of the primary owner.

-O

(Uppercase O) 

Specifies all calendars of the primary owner. Default is the named calendar only. 

-y otherowners

Other calendar owners. Multiple owners must be enclosed in quotation marks ("") and separated by spaces. The default is no other owners.

D.5.3 Possible Problems Creating a Calendar on a Back-End Machine

If you try to create a calendar on a designated back-end machine, and you get the following error message: Invalid DWP Host Server. it means one of two things. Either your server is not configured properly, or the calendar owner has already been assigned to a different back-end server.

D.5.3.1 Back-End Machine Not Configured Properly

Look at the ics.conf file for the back-end server in question. Verify that the following settings exist:

service.dwp.enable = "yes"
caldb.cld.type = "directory"
local.hostname = "back-end hostname"

D.5.3.2 Calendar Owner Assigned to a Different Back-End Machine

Look at the user's LDAP entry and see if there is an icsDWPHost attribute present. The value of icsDWPHost must match the back—end server name on which you are attempting to create the calendar. You can not create a calendar for this user on a different back-end server.

D.5.4 Examples

D.6 csclean

The csclean utility only works in Schema version 2 mode. It removes user and resource calendars for users whose status attribute (icsStatus) has been marked as “deleted” by Delegated Administrator.

For Schema version 1, use csuser and cscal to remove all of the calendars for a deleted user.

D.6.1 Requirements

D.6.2 Syntax


csclean [-q | -v] 
        [-g graceperiod]
        clean domain

The following table describes the csclean utility command options.

Table D–8 csclean Utility Command Options

Option 

Description  

-q

Run in quiet mode: 

  • Display no information if the operation is successful (errors, if they occur, are displayed).

  • Suppress confirmation prompting for dangerous commands.

    Default is off.

-v

Run in verbose mode: Display all available information about the command being performed. Default is off. 

-ggraceperiod

Specifies the number of days to have elapsed since the calendar service was deleted for a user. 

The default is 10 days. 

domain

Specifies the domain in which to remove calendars for all users and resources. 

An asterisk (*) removes all calendars for all users and resources in all domains.

D.6.3 Examples

D.7 cscomponents

The cscomponents utility manages calendar components: events and tasks (todos). Commands are:

D.7.1 Requirements

D.7.2 Syntax


cscomponents [-v|-q] 
             [-e endtime] 
             [-s starttime] 
             [-t event|task]
             delete|list calid

The following table describes the commands available for the cscomponents utility.

Table D–9 cscomponents Utility Commands

Command  

Description  

delete calid

Deletes events and tasks in the calendar with the specified calendar ID. 

list calid

Lists events and tasks in the calendar with the specified calendar ID. 


Note –

When deleting tasks, you must specify the -soption with an actual DateTime Z String specifying the starting date for removal. If you do not specify a date, or you specify zero (0) as the value for the option, all tasks will be deleted from the calendar.


version

Prints the version of the utility to the screen. 

The following table describes the cscomponents utility command options.

Table D–10 cscomponents Utility Command Options

Option  

Description 

-v

Run in verbose mode: Display all available information about the command being performed. Default is off. 

-q

Run in quiet mode: 

  • Display no information if the operation is successful (errors, if they occur, are displayed).

  • Suppress confirmation prompting for dangerous commands.

    Default is off.

-e endtime

Ending time of the components. An end time of 0 means to the end of time. The default is 0.

-s starttime

Starting time of the components. A start time of 0 means from the beginning of time. The default is 0.


Note –

For tasks only, you must specify this option and the starting date specified must be a DateTime Z String. If the option is not specified, or the option is specified but the value is set to zero, all tasks for this calendar will be deleted.


-t event|task

Type of components (events or tasks) on which the action is performed. Default is both. 

D.7.3 Examples

D.8 csdb

The csdb utility manages the calendar databases (calendar, session, and statistics). Commands are:

D.8.1 Requirements

D.8.2 Syntax


csdb [-q|-v] 
     [-t caldb|sessdb|statdb] 
     create|delete [dbdir]

csdb [-q|-v] 
     [-t caldb|sessdb|statdb] 
     list [dbdir]

csdb [-q|-v] 
     [-f] 
     [-t caldb|sessdb|statdb] 
     recover [dbdir]

csdb check [dbdir]

csdb rebuild [-a, -V] 
     [-g] [dbdir [dstdir]]

The following table describes the commands available for the csdb utility.

Table D–11 csdb Utility Commands

Command 

Description  

create [dbdir]

Creates the databases in the specified database directory. If a database directory is not specified, the current directory is used. If a database does not exist when the server is started, Calendar Server creates one automatically. 

delete [dbdir]

Deletes the databases in the specified database directory. If a database directory is not specified, the current directory is used. A database cannot be deleted while it is open (when Calendar Server is running). 

list [dbdir]

Lists information about the databases in the specified database directory. If a database directory is not specified, the current directory is used. 

recover [dbdir]

Attempts to recover damaged calendar databases in the specified database directory. If a database directory is not specified, the current directory is used. Is not implemented for session or statistics databases. 

check [dbdir]

Scans a calendar database in the specified database directory to determine if any corruption has occurred and reports the results in its output. If a database directory is not specified, the current directory is used. 

rebuild [dbdir [dstdir]]

Scans all calendar databases in the specified database directory to determine if any corruption has occurred and generates a rebuilt calendar database (.db files). If a database directory is not specified, the current directory is used. After the databases are rebuilt, db_verify runs.

The dstdir specifies an optional destination directory.

version

Displays the version of the utility. 

The following table describes the csdb utility command options.

Table D–12 csdb Utility Command Options

Option  

Description  

-a

For rebuild command only, rebuilds only the alarms database.

-V

Must be passed in with -a for rebuilding the alarms database. Causes verify to be run against all databases, including alarms.

-v

Run in verbose mode: Display all available information about the command being performed. Default is off. 

-q

Run in quiet mode: 

  • Display no information if the operation is successful (errors, if they occur, are displayed).

  • Suppress confirmation prompting for dangerous commands.

    Default is off.

-f

Force the recovery of the calendar database. 

-g

For the rebuild command, rebuild the group scheduling engine (GSE) database in addition to the other calendar databases.

-t caldb|sessdb|statdb

Specifies the target database group: 

  • caldb (calendar)

  • sessdb (session)

  • statdb (statistics)

    Note: If -t is not specified, csdb operates on all database groups, except for the check, recover and rebuild commands, which operate only on caldb (calendar).

D.8.3 Examples

D.9 csdomain

The csdomain utility manages Calendar Server attributes in the domain LDAP entry. These attributes are part of the icsCalendarDomain object class. Commands are:

D.9.1 Requirements

D.9.2 Syntax


csdomain [-q | -v] 
          -n node 
         create domain

csdomain [-q | -v] 
         {-a attr[=value] | 
          -f filename} 
         add domain

csdomain [-q | -v] 
         [-a attr | 
          -f filename] 
         delete domain

csdomain [-q | -v] 
         list domain

The following table describes the commands available for the csdomain utility.

Table D–13 csdomain Utility Commands

Command  

Description  

create

Create a new domain in the LDAP directory. 

add

Add a Calendar Server attribute and its associated value in the domain LDAP entry. If you add or update domain attributes using csdomain, restart Calendar Server for the new values to take effect.

delete

Delete a Calendar Server attribute in the LDAP directory for a specific domain or delete all LDAP entries for an entire domain. 

list

Display Calendar Server attributes in the LDAP directory for a specific domain. 

version

Display the version of the utility. 

The following table describes the csdomain utility command options.

Table D–14 csdomain Utility Command Options

Option  

Description  

-v

Run in verbose mode: Display all available information about the command being performed. Default is off. 

-q

Run in quiet mode: 

  • Display no information if the operation is successful (errors, if they occur, are displayed).

  • Suppress confirmation prompting for dangerous commands.

    Default is off.

-aattr[=value]

Specifies the LDAP attribute property name and its optional value. 

For a list of these attributes and property names, see D.9.3 LDAP Attributes and Property Names.

-f filename

Specifies a text file that contains Calendar Server LDAP directory property names and their associated values.  

For example: 

createLowerCase="yes"

filterPrivateEvents="no"

fbIncludeDefCal="no"

subIncludeDefCal="no"

uiProxyUrl="https://proxyserver"

-n node

Applies to the create command as follows: 

  • For LDAP Schema version 1 – Specifies the node under which all users and resources are created. For example: o=node2,o=node1,o=sesta

  • For LDAP Schema version 2 – Specifies the name of the node created for this domain. For example: o=west.sesta.com

    If node is not specified, the domain name is used.

domain

For the add, delete, and list commands, specifies an existing domain in the LDAP directory. 

For the create command, specifies the unique name of a new domain that will be created in the LDAP directory. 

For example: west.sesta.com

D.9.3 LDAP Attributes and Property Names

The following tables describe the LDAP attributes and property names that apply to the csdomain utility. These attributes are part of the icsCalendarDomain object class. When you add or delete a value, you must use the property name and not the attribute name.

If you add or update domain LDAP attributes using csdomain, restart Calendar Server for the new values to take effect.

D.9.3.1 icsAllowRights Attribute: csdomain Utility

D.9.3 LDAP Attributes and Property Names describes the icsAllowRights attribute and properties that you can set with the csdomain utility. This attribute is a 32-bit numeric string, with each bit in the string corresponding to a specific user right. (In the current release, some bits are not used and are set to zero by default.) If a bit corresponding to a specific right is set (value=1), the right is not allowed. If the bit is not set (value=0), the right is allowed.

Each property in the icsAllowRights attribute has a corresponding ics.conf parameter. If a property is not set (value = 0) or is not present (service.virtualdomain.support = “no”), Calendar Server uses the corresponding ics.conf parameter as the default value.

The value for icsAllowRights is a numeric string and not an integer. To use icsAllowRights programmatically in bitwise operations, you must first convert its string value to an integer.

Table D–15 icsAllowRights LDAP Directory Attribute and Properties

Bit  

Property Name  

Description  

allowCalendarCreation

If set (bit 0=1), do not allow calendars to be created. 

Corresponding ics.conf parameter:

service.wcap.allowcreatecalendars

allowCalendarDeletion

If set (bit 1=1), do not allow calendars to be deleted. 

Corresponding ics.conf parameter:

service.wcap.allowdeletecalendars

allowPublicWritableCalendars

If set (bit 2=1), do not allow public writable calendars. 

Corresponding ics.conf parameter:

service.wcap.allowpublicwriteablecalendars

 

Not used in the current release. 

allowModifyUserPreferences

If set (bit 4=1), do not allow domain administrators to get or set user preferences using WCAP commands. 

Corresponding ics.conf parameter:

service.admin.calmaster.wcap.allowgetmodifyuserprefs

allowModifyPassword

If set (bit 5=1), do not allow user to change password via this server. 

Corresponding ics.conf parameter:

service.wcap.allowchangepassword

 

Not used in the current release. 

 

Not used in the current release. 

allowUserDoubleBook

If set (bit 8=1), do not allow double booking for user’s calendars. 

Corresponding ics.conf parameter:

user.allow.doublebook

allowResourceDoubleBook

If set (bit 9=1), do not allow double booking for resource calendars. 

Corresponding ics.conf parameter:

resource.allow.doublebook

10 

allowSetCn

If set (bit 10=1), do not allow user to set the common name (cn) attribute using the WCAP set_userprefs command.

Corresponding ics.conf parameter:

service.wcap.allowsetprefs.cn

11 

allowSetGivenName

If set (bit 11=1), do not allow user to set the givenName attribute using the WCAP set_userprefs command.

Corresponding ics.conf parameter:

service.wcap.allowsetprefs.givenname

12 

allowSetGivenMail

If set (bit 12=1), do not allow user to set the mail attribute using the WCAP set_userprefs command.

Corresponding ics.conf parameter:

service.wcap.allowsetprefs.mail

13 

allowSetPrefLang

If set (bit 13=1), do not allow user to set the preferredLanguage attribute using the WCAP set_userprefs command.

Corresponding ics.conf parameter:

service.wcap.allowsetprefs.preferredlanguage

14 

allowSetSn

If set (bit 14=1), do not allow user to set the surname (sn) attribute using the WCAP set_userprefs command.

Corresponding ics.conf parameter:

service.wcap.allowsetprefs.sn

15–31 

 

Not used in the current release. 

D.9.3.2 icsExtendedDomainPrefs Attribute: csdomain Utility

The following table describes the icsExtendedDomainPrefs attribute and properties that you can set with the csdomain utility. Each property has a corresponding ics.conf parameter. If a property is not set ( for example, value = 0, or service.virtualdomain.support=“no”), or is not present, Calendar Server uses the corresponding ics.conf parameter as the default value.

Table D–16 icsExtendedDomainPrefs LDAP Directory Attribute

Property Name  

Description  

allowProxyLogin

Specifies "yes" or "no" whether to allow proxy logins.

Corresponding ics.conf parameter:

service.http.allowadminproxy (default = "yes")

calmasterAccessOverride

Specifies "yes" or "no" whether the Calendar Server administrator can override access control.

Corresponding ics.conf parameter:

service.admin.calmaster.overrides.accesscontrol (default = "no")

calmasterCred

Specifies an ASCII string that is the password of the user ID specified as the Calendar Server domain administrator. 

Corresponding ics.conf parameter:

service.siteadmin.cred (no default)

calmasterUid

Specifies an ASCII string that is the user ID of the person designated as the Calendar Server domain administrator. 

Corresponding ics.conf parameter:

service.siteadmin.userid (no default)

createLowercase

Specifies "yes" or "no" whether Calendar Server should convert a calendar ID (calid) to lowercase when creating a new calendar or when searching for a calendar 

Corresponding ics.conf parameter:

calstore.calendar.create.lowercase (default = "no")

domainAccess

Specifies an access control list (ACL) for the domain. For information about ACLs, see 1.8.3 Access Control Lists (ACLs) in Calendar Server Version 6.3.

This ACL is used for cross domain searches. For more information, see 11.2 Cross Domain Searching in Calendar Server 6.3 Systems.


Caution – Caution –

Only a single instance of domainAccess is allowed. However, the system does not warn you if there is a duplicate. You must ensure there is only one, whenever you change the value.


fbIncludeDefCal

Specifies "yes" or "no" whether a user’s default calendar is included in user’s free/busy calendar list. 

Corresponding ics.conf parameter:

calstore.freebusy.include.defaultcalendar (default = "yes")

filterPrivateEvents

Specifies "yes" or "no" whether Calendar Server filters (recognizes) Private and Time and Date Only (confidential) events and tasks. If "no", Calendar Server treats them the same as Public events and tasks.

Corresponding ics.conf parameter:

calstore.filterprivateevents (default = "yes")

groupMaxSize

Specifies the maximum size of an LDAP group that will be expanded for an invitation. 

Corresponding ics.conf parameter:

calstore.group.attendee.maxsize (default is "0" – expand the group without regard to size)

language

Specifies the language for a domain. 

Corresponding ics.conf parameter:

local.domain.language

resourceDefaultAcl

Specifies an access control list (ACL) that is the default access control permissions used when a resource calendar is created. 

Corresponding ics.conf parameter:

resource.default.acl (default is

"@@o^a^r^g;@@o^c^wdeic^g;
@^a^rsf^g"

setPublicRead

Specifies whether user default calendars are initially set to public read/private write ("yes") or private read/private write ("no"). 

Corresponding ics.conf parameter:

service.wcap.login.calendar.publicread (default = "no")

searchFilter

Specifies a search filter for finding a user. 

Corresponding ics.conf parameter:

local.userSearchFilter

ssoCookieDomain

Specifies that the browser should send a cookie only to servers in the specified domain. The value must begin with a period (.). For example: ".sesta.com" 

Corresponding ics.conf parameter:

sso.cookiedomain (default is the current domain)

ssoUserDomain

Specifies the domain used as part of the user’s SSO authentication. 

Corresponding ics.conf parameter:

sso.userdomain (no default)

subIncludeDefCal

Specifies "yes" or "no" whether a user’s default calendar is included in the user’s subscribed calendar list. 

Corresponding ics.conf parameter:

calstore.subscribed.include.defaultcalendar (default = "yes")

uiAllowAnyone

Specifies "yes" or "no" whether the user interface should show and use the "Everybody" access control list (ACL). 

Corresponding ics.conf parameter:

ui.allow.anyone (default = "yes")

uiAllowDomain

Specifies "yes" or "no" whether the user interface should show and use the access control list (ACL) for this domain. 

Corresponding ics.conf parameter:

ui.allow.domain (default = "no")

uiBaseUrl

Specifies a URL for the base server address. For example: "https://proxyserver".

Corresponding ics.conf parameter: 

ui.base.url (no default)

uiConfigFile

Specifies an optional xml based configuration file that Calendar Server can read at startup that allows parts of the user interface to be hidden.

Corresponding ics.conf parameter:

ui.config.file (no default)

uiProxyURL

Specifies a URL for the proxy server address to prepend in an HTML UI JavaScript file. For example: "https://web_portal.sesta.com/"

Corresponding ics.conf parameter:

ui.proxyaddress.url (no default)

D.9.3.3 Other LDAP Directory Attributes: csdomain Utility

The following table describes other LDAP attributes and properties that you can set with the csdomain utility.

Table D–17 Other LDAP Directory Attributes for the csdomain Utility

LDAP Attribute  

Property Name 

Description  

icsAllowedServiceAccess

allowedAccessProtocols

Specifies whether access to Calendar Server is allowed. If set to “http”, access is denied. If set to any other value, access is allowed. 

Calendar Server uses this attribute only if the icsStatus attribute is not set.

icsDefaultAccess

userDefaultAcl

Specifies the ACL for a newly created user calendar. 

Corresponding ics.conf parameter:

calstore.calendar.default.acl

icsDomainNames

searchDomainNames

Specifies the external domains that this domain can search when looking for calendars or users. 

Corresponding ics.conf parameter: none

icsDWPBackEndHosts

(undefined) 

Specifies the default back-end host (DNS name) for a user if a host name is not explicitly provided. This attribute is used when Calendar Server is in LDAP CLD mode. 

icsStatus

statusCalendarDomain

Specifies that status of Calendar Server: 

  • active–Calendar Server is accessible.

  • inactive–Calendar Server is inaccessible. Calendars remain in the database and Calendar Server LDAP attributes remain unchanged.

  • deleted–Calendar Server is inaccessible, because the person is marked as deleted.

  • removed–Calendars have been removed from the calendar database.

    If icsStatus is set, its value overrides the icsAllowedServiceAccess attribute.

    If icsStatus is not set, Calendar Server uses the icsAllowedServiceAccess attribute.

icsTimezone

timezone

Specifies the default time-zone ID. For example, America/New_York or Asia/Tokyo. 

For the supported time zones, refer to the timezones.ics file.

D.9.4 Examples

D.10 csexport

The csexport utility exports a calendar to a file in iCalendar (.ics) or XML (.xml) format. Commands are:

D.10.1 Requirements

D.10.2 Syntax


csexport [-v|-q]
         -c calid
         calendar outputfile

The following table describes the commands available for the csexport utility.

Table D–18 csexport Utility Commands

Command  

Description  

calendar outputfile

Export the calendar to the specified output file. The data format of the file is determined by the specified filename extension: 

  • .ics for iCalendar (text/calendar)

  • .xml for XML (text/xml)

version

Display the version of the utility. 

The following table describes the csexport utility command options.

Table D–19 csexport Utility Command Options

Option  

Description 

-v

Run in verbose mode: Display all available information about the command being performed. Default is off. 

-q

Run in quiet mode: 

  • Display no information if the operation is successful (errors, if they occur, are displayed).

  • Suppress confirmation prompting for dangerous commands.

    Default is off.

-c calid

The calendar ID of the calendar to export. This option is required with the calendar command. There is no default. 

D.10.3 Examples

D.11 csimport

The csimport utility imports a calendar from a file in iCalendar (ics) or XML format that was saved with the csexport utility. Commands are:

Date calculations for importing a calendar’s components use the time zone specified in the X-NSCP-DTSTART-TZID associated with the component. If none is present, then the server time zone found in the ics.conf is used.

D.11.1 Requirements

D.11.2 Syntax


csimport [-v|-q]
          -c calid
         calendar inputfile

The following table describes the commands available for the csimport utility.

Table D–20 csimport Utility Commands

Command  

Description 

calendar inputfile

Import the calendar from the specified input file. The data format of the file is determined by the filename extension: 

  • .ics for iCalendar (text/calendar)

  • .xml for XML (text/xml)

version

Display the version of the utility. 

The following table describes the csimport utility command options.

Table D–21 csimport Utility Command Options

Option  

Description  

-v

Run in verbose mode: Display all available information about the command being performed. Default is off. 

-q

Run in quiet mode: 

  • Display no information if the operation is successful (errors, if they occur, are displayed).

  • Suppress confirmation prompting for dangerous commands.

    Default is off.

-c calid

The calendar ID of the calendar to import. This option is required with the calendar command. 

If the specified calendar ID already exits, the imported data is merged with the current calendar. There is no default. 

For more information, see 15.2 Creating Calendar Unique Identifiers (calid's).

D.11.3 Examples

D.12 csplugin

The csplugin manages CSAPI plug-ins configured for your Calendar Server installation. Commands are:

D.12.1 Requirements

D.12.2 Syntax


csplugin [-q|-v] 
         [-r] 
          -t ac|attr|auth|locate|lookup|xlate
         activate|deactivate plugin

csplugin [-q|-v] list

The following table describes the commands available for the csplugin utility.

Table D–22 csplugin Utility Commands

Command 

Description  

activate -t type name

Load and enable the specified plug-in type and plug-in name. (For descriptions of the supported plug-in types, see the -t option in Table D–23.)

deactivate -t type name

Shut down and disable the specified plug-in type and plug-in name. (For descriptions of the supported plug-in types, see the -t option in Table D–23.)

list

List all the supported plug-in types, names, and activation status. (For descriptions of the supported plug-in types, see the -t option in Table D–23.)

version

Display the version of the utility. 

The following table describes the csplugin utility command options.

Table D–23 csplugin Utility Command Options

Option  

Description  

-v

Run in verbose mode: Display all available information about the command being performed. Default is off. 

-q

Run in quiet mode: 

  • Display no information if the operation is successful (errors, if they occur, are displayed).

  • Suppress confirmation prompting for dangerous commands.

    Default is off.

-r

When used with the activate command, physically copies the plug-in into the Calendar Server plugin directory.

When used with the deactivate command, deletes the plug-in from the plugin directory.

-t type

Specifies one of the following supported types of plug-ins: 

  • ac— augments or overrides the default group scheduling access control mechanism.

  • attr— augments or overrides the mechanism for storing and retrieving user attributes.

  • auth— augments or overrides the login authentication mechanism.

  • locate— retrieves a calendar ID for the specified qualified URL.

  • lookup— augments or overrides the default calendar lookup mechanism.

  • xlate— augments or overrides the format translation of incoming and outgoing data.

D.12.3 Examples

D.13 cspurge

The cspurge utility allows the manual purge of entries in the Delete Log database (ics50deletelog.db).

D.13.1 Requirements

D.13.2 Syntax


cspurge [-q|-v] 
        -e endtime 
        -s starttime

The following table describes the cspurge utility command options.

Table D–24 cspurge Utility Command Options

Option  

Description  

-v

Run in verbose mode: Display all available information about the command being performed. Default is off. 

-q

Run in quiet mode: 

  • Display no information if the operation is successful (errors, if they occur, are displayed).

  • Suppress confirmation prompting for dangerous commands.

    Default is off.

-e endtime

Specifies the ending time in GMT (also referred to as UTC or Zulu). This value is up to (less than) the specified time. 

The default is 0, which means to the end of time. 

-s starttime

Specifies the starting time in GMT (also referred to as UTC or Zulu). This value includes (greater than or equal to) the specified time. 

The default is 0, which means from the beginning of time. 

D.13.3 Examples

D.14 csrename

The csrename utility allows you to rename one or more calendar users. This utility renames calendar users as follows:

The csrename utility is located in the following directory:

cal-svr-base/SUNWics5/cal/sbin

D.14.1 Requirements

Before you run csrename, you must first:

To run csrename, you must log in as icsuser (or as the Calendar Server runtime user ID specified during configuration). If you run csrename as superuser (root), you might need to reset the permissions for the new database files. To modify the LDAP directory server attributes, you must also have administrative rights for that directory.

If your Calendar Server installation has a front-end/back-end server configuration, you must run csrename on each back-end server.

D.14.2 Syntax

Use the following syntax to run csrename:


csrename [-t DestinationDB] 
         [-c ConfigFile]
         [-e ErrorFile] 
          -m MappingFile 
         rename [DB|LDAP]

table lists the options for this utility and gives a description of each.

Table D–25 Options for csrename

Option  

Description  

-t DestinationDB

Specifies the destination directory where csrename generates the new database with the converted user names. The default is MigratedDB. After csrename is finished, the caldb.berkeleydb.homedir.path parameter in the ics.conf file must point to the destination database. Either reset caldb.berkeleydb.homedir.path to point to the destination database directory, or move the destination database files to the directory indicated by the parameter.

-c ConfigFile

An input parameter that specifies a Calendar Server configuration file. The default is the ics.conf file. The csrename utility uses the caldb.berkeleydb.homedir.path parameter in the configuration file to determine the location of the input calendar database. The default location of the calendar database is /var/opt/SUNWics5/csdb.

-e ErrorFile

The file where csrename writes any errors or database entries that cannot be resolved. The default is MigrateError.

-m MappingFile

Specifies an input mapping file. The default is MigrateMapping. The input mapping file is a text file that maps existing user ID's to new user ID's. You must create the mapping file before you run csrename. Specify one entry per line with a space between the old and new values.

For example: 

tchang tc897675

jsmith js963123

bkamdar bk548769

If upon auditing your results, you find that one or more of your intended name changes was omitted, you can fix the error by creating a new mapping file with only the missed names in it and rerunning csrename.

DB|LDAP

Specifies the database that gets updated: 

DB converts user ID's in the new calendar database only (default).

LDAP converts user ID's in both the new calendar database and the LDAP directory server attributes.

D.14.3 Examples

D.15 csresource

The csresource utility creates and manages LDAP entries and calendars for resources, such as conference rooms or equipment. (The csresource utility is available only for calendars associated with a resource and returns an error if issued against a user’s calendar.) Commands are:

D.15.1 Requirements

D.15.2 Syntax


csresource [-q|-v] 
           [-a aces] 
           [-b  basedn] 
           [-d domain] 
           [-t description] 
           [-k yes|no] 
           [-o owner] 
           [-y otherowners] 
            -m email 
            -c calid 
           create common_name

csresource [-q|-v] 
           [-b basedn] 
           [-d domain]
           delete|disable|enable [common_name]

csresource [-q|-v] 
           [-b basedn]
           [-d domain]
           [-h host] 
           list [common_name]

Then following table describes the commands available for the csresource utility.

Table D–26 csresource Utility Commands

Command  

Description 

create common_name

Create a new resource for a specified calendar ID. 

delete [common_name]

Delete a resource or, if no resource common_name is specified, delete all resources.

enable [common_name]

Enable a resource or, if no resource common_name is specified, enable all resources.

disable [common_name]

Disable a resource or, if no resource common_name is specified, disable all resources.

list [common_name]

Display a single resource calendar or, if no resource name is specified, display all resource calendars.

If the -h host option is included, display the calendar attributes for the specified name (or all resource calendars) on that back-end server.


Note –

If the name contains a space in any of the above commands, it must be enclosed in quotation marks (" ").


The following table describes the csresource utility command options.

Table D–27 csresource Utility Command Options

Option  

Description  

-v

Run in verbose mode: Display all available information about the command being performed. Default is off. 

-q

Run in quiet mode: 

  • Display no information if the operation is successful (errors, if they occur, are displayed).

  • Suppress confirmation prompting for dangerous commands.

    Default is off.

-a [aces]

Access Control Entries (ACE's) for the specified calendar. ACE's determine who can access a calendar for group scheduling and the types of permissions they have, such as create, delete, read, and write privileges. An ACE string or Access Control List (ACL), must be enclosed in quotation marks ("").

The default is the resource.default.acl parameter in the ics.conf file.

For information about the ACE format, see 15.4 Calendar Access Control.

-b [basedn]

LDAP base DN (distinguished name) to be used for the specified resource. The default is taken from the local.ugldapbasedn parameter in the ics.conf file.

-c calid

The icsCalendar attribute. This option is required with the create command. For more information, see 15.2 Creating Calendar Unique Identifiers (calid's).

-d domain

Specifies the name of a domain. Default is taken from the service.defaultdomain parameter in the ics.conf file.

-t [description]

Specifies a viewable comment about the purpose of the calendar. The default is no description. 

-h host

Specifies the name of a back-end server where the resource calendar resides. This option applies only to the list command. 

-k yes|no

Specifies whether double booking is allowed for a calendar associated with a resource such as a conference room. For example, yes means the resource calendar can have more than one event scheduled for the same time slot.

If the -k option is omitted, the default is taken from the resource.allow.doublebook parameter in the ics.conf file. However, the resource.allow.doublebook parameter is used only when a calendar is created.

After a calendar is created, Calendar Server checks the calendar properties database (ics50calprops.db) to determine if double booking is allowed. If you need to change the calendar properties for a calendar to allow or disallow double booking, reissue csresource with the -k option.

-m email

Specifies the LDAP mail attribute (primary email address) for the resource. 

-o owner

Primary owner. 

Default is taken from service.siteadmin.userid in the ics.conf file.

-y otherowners

Other owners. Multiple owners must be enclosed in quotation marks (" ") and separated by spaces. The default is no other owners.

version

Display the version of the utility. 

D.15.3 Examples

D.16 csrestore

The csrestore utility restores the calendar database, a specified calendar, or a user’s default calendar that was saved using csbackup or csexport. Commands are:

The caldb.conf version file located in the specified backup directory shows the version number of the database that was backed up.


Caution – Caution –

The Calendar Server version 6.3 csrestore utility is not compatible with the Calendar Server version 2 csrestoreutility. Do not try to restore data that was backed up using the csrestore in version 2 because data loss can occur.


D.16.1 Requirements


Note –

csrestore does not take care about the user LDAP entries, subscribed or own calendar. You need to manually perform on the User LDAP entire to get the personal calendar back on the multi valued attribute, icsSubscribed.


D.16.2 Syntax


csrestore [-v|-q] 
          [-f] 
          database inputdir

csrestore [-v|-q] 
           -c calid 
          calendar inputfile

csrestore [-v|-q] 
           -a userid
          [-b basedn] 
          defcal inputfile

The following table describes the commands available for the csrestore utility.

Table D–28 csrestore Utility Commands

Command  

Description 

database inputdir

Restore the calendar database from the specified input directory or input file that contains a backup calendar database. This operation overwrites all previous contents of the current calendar database. 

calendar inputfile

Restore the specified calendar ID from the specified input file. The data format of the file is determined by the filename extension: 

  • .ics for iCalendar (text/calendar).

  • .xml for XML (text/xml).

    If the specified calendar ID already exists, the calendar's data is cleared before it is restored.

defcal inputfile

Restore the default calendar of the specified user ID from the input file specified. The data format of the file is determined by the filename extension: 

  • .ics for iCalendar (text/calendar).

  • .xml for XML (text/xml).

version

Display the version of the utility. 

The following table describes the csrestore utility command options.

Table D–29 csrestore Utility Command Options

Option  

Description  

-v

Run in verbose mode: Display all available information about the command being performed. Default is off. 

-q

Run in quiet mode: 

  • Display no information if the operation is successful (errors, if they occur, are displayed).

  • Suppress confirmation prompting for dangerous commands.

    Default is off.

-a userid

The user ID to restore. This option is required with the default option. There is no default. 

-b basedn

The LDAP base DN (distinguished name) to be used for the specified user ID. The default is taken from the setting local.ugldapbasedn defined in the ics.conf file.

-f

To force any existing database files to be deleted. 

-c calid

The calendar ID to restore. This option is required with the calendar command. There is no default.

For more information, see 15.2 Creating Calendar Unique Identifiers (calid's).

D.16.3 Examples

D.17 csschedule

The csschedule utility manages schedule entries stored in the Group Scheduling Engine (GSE) queue. Commands are:

D.17.1 Requirements

D.17.2 Syntax


csschedule [-q|-v] 
           [-c count] 
           [-e endtime] 
           [-s starttime]
           [-t scheduletime
             -o offset] 
           [-u uid] 
           list [calid]

csschedule [-q|-v] 
           [-t scheduletime 
             -o offset 
             -u uid 
             -n sequencenumber 
             -r rid] 
           list [calid]

csschedule [-q|-v]  
           [-t scheduletime 
             -o offset 
             -u uid 
             -n sequencenumber 
             -r rid] 
           delete [calid]

csschedule [-q|-v] 
           [-s starttime] 
           [-e endtime] 
           delete [calid]

         

The following table describes the commands available for the csschedule utility.

Table D–30 csschedule Utility Commands

Command  

Description  

list

Display entries held in the GSE queue requested by a specified calendar ID. 

delete

Delete an entry from the GSE queue requested by a specified calendar ID. 

version

Display the version of the utility. 

Then following table describes the csschedule utility command options.

Table D–31 csschedule Utility Command Options

Option  

Description  

-v

Run in verbose mode: Display all available information about the command being performed. Default is off. 

-q

Run in quiet mode: 

  • Display no information if the operation is successful (errors, if they occur, are displayed).

  • Suppress confirmation prompting for dangerous commands.

    Default is off.

-c count

The number of GSE queue entries to list. For example, specify 10 if you want to examine ten entries in the queue. 

-e endtime

The ending time of the entry in the GSE queue where 0 means to the end of time. The default is 0. 

-n sequencenumber

The sequence number of the event or task in the queue. 

-o offset

An offset number for a schedule time. The offset number uniquely identifies an entry in the GSE queue when there is more than one entry scheduled at the same time. 

-r rid

The recurrence ID (RID) of the event or todo. An RID is a semicolon delimited list of strings that identify each occurrence of a recurring event or todo.

-s starttime

The starting time of the entry in the GSE queue where 0 means from the beginning of time. The default is 0. 

-t scheduletime

A schedule time, for example: 20001231T103045Z

-u uid

The unique identifier (UID) of an entry in the GSE queue.

D.17.3 Examples

D.18 csstats

The csstats utility displays Calendar Server statistics. Commands are:

For more information about counters, see E.3 Counters Configuration (counter.conf) File.

D.18.1 Requirements

D.18.2 Syntax


csstats [-q|v] 
        [-r registry] 
        [-i iterations] 
        [-s delay] 
        list [subsystem] 

The following table describes the commands available for the csstats utility.

Table D–32 csstats Utility Commands

Command  

Description  

list [subsystem]

List counter statistics about a specified Calendar Server subsystem or. If subsystem is not specified, display basic information about the available subsystems, which are: 

  • alarm — monitoring of services alarm notifications

  • auth — login authentication

  • db — calendar database

  • disk — disk usage monitoring

  • gse — Group Scheduling Engine (GSE)

  • http — HTTP transport

  • response — server response times

  • sess — server session status

  • wcap — Web Calendar Access Protocol

Version

Display the version of the utility. 

The following table describes the csstats utility command options.

Table D–33 csstats Utility Command Options

Option  

Description 

-v

Run in verbose mode: Display all available information about the command being performed. Default is off. 

-q

Run in quiet mode: 

  • Display no information if the operation is successful (errors, if they occur, are displayed).

  • Suppress confirmation prompting for dangerous commands.

    Default is off.

-i iterations

The number of times to repeat statistical lookups. Default is 1. 

-r registry

The name and location of the file that stores counter statistics. The default is: 

/opt/SUNWics5/cal/lib/counter/counter

-s delay

The amount of time (in seconds) to wait before displaying each statistical lookup. The default is 1 second. 

D.18.3 Examples

D.19 csuser

The csuser utility works in Schema version 1 mode only. It manages calendar users' LDAP entries, and the users' default calendars. Commands are:


Note –

This utility does not enable users for Address Book as is required for Communications Express. This will have to be done manually with ldapmodify.


If you are using Directory Server, you can also use the ldapsearch and ldapmodify utilities. For information about these utilities, see the Directory Server documentation on the following Web site:

http://docs.sun.com/coll/1316.2

D.19.1 Requirements

D.19.2 Syntax


csuser [-q|-v]
       [-a aces] 
       [-b basedn]
        -m email address 
       [-d domain]
        -f filename
        -g givenname 
       [-k yes|no] 
       [-l langcode] 
        -s surname 
        -y userpassword
       create userid

csuser [-q|-v] 
       [-b basedn] 
       [-d domain] 
       [-h host] 
       list [userid]

csuser [-q|-v] 
       [-b basedn] 
       [-d domain]
       [check|delete|disable|enable|reset] userid

         

The following table describes the commands available for the csuser utility.

Table D–34 csuser Utility Commands

Command  

Description  

check userid

Check if the specified user ID is enabled for calendaring. 

create userid

Create the specified user ID and enable this user to log into Calendar Server. 

delete userid

Delete the specified user ID. 

disable userid

Disables the specified user ID for calendaring by adding icsAllowedServiceAcess="http" to the user's LDAP entry.

enable userid

Enables the specified user ID for calendaring by removing icsAllowedServiceAcess="http" from the user's LDAP entry.

list [userid]

List the calendar attributes for the specified user ID. If user ID is not specified, list attributes for all enabled users. 

If the -h server-name option is included, list the calendar attributes for the specified user ID (or all enabled users) on that back-end server.

reset userid

Reset all calendar attributes for a user ID to their default settings. 

Note: After the calendar attributes for a user ID have been reset, all of the calendar attributes are removed from the user’s LDAP entry, including icsCalendarUser (object class), icsSubscribed, icsCalendarOwned, icsCalendar, and icsDWPHost (if the user is in an LDAP CLD setup). A Calendar Server administrator then cannot create calendars on the user’s behalf.

These attributes are restored in the user’s LDAP entry when the Calendar Server administrator issues a csuser enable command for the user.

version

Display the version of the utility. 

The following table describes the csuser utility command options.

Table D–35 csuser Utility Command Options

Option  

Description  

-v

Run in verbose mode: Display all available information about the command being performed. Default is off. 

-q

Run in quiet mode: 

  • Display no information if the operation is successful (errors, if they occur, are displayed).

  • Suppress confirmation prompting for dangerous commands.

    Default is off.

-b basedn

The base DN to be used for all LDAP users. The default value is taken from the setting local.ugldapbasedn defined in the ics.conf file.

-d domain

Specifies the name of a domain. Default is taken from the service.defaultdomain parameter in the ics.conf file.

-a [aces]

Access Control Entries (ACE's) for a specified calendar. ACE's determine who can access a calendar for group scheduling and the types of permissions they have, such as create, delete, read, and write privileges. An ACE string or Access Control List (ACL), must be enclosed in quotation marks ("").

Default is: 

"@@o^a^r^g;@@o^c^wdeic^g;
@^a^sf^g;@^c^^g;@^p^r^g"

For details about the ACE format, see E.2.9 Calendar Server Services Configuration.

-f filename

File name to specify a password for options that require a password (-y parameter). If you are running csuser from a script, for added security, specify the password in filename.

-g givenname

The user's LDAP given name (first name). This option is required. There is no default. 

-h host

Specifies the name of a back-end server where the user’s calendar resides. This option applies only to the list command. 

-p port

The port number that LDAP server is listening to. The default value is taken from the setting local.ugldapport defined in the ics.conf file.

-k yes|no

If double booking is allowed for a user’s calendar. If yes, the user’s calendar can have more than one event scheduled for the same time slot.

Default is taken from the setting user.allow.doublebook defined in the ics.conf file.

-l [langcode]

Language code. Default is the value of local.sitelanguage in ics.conf.

-m email address

Specifies the LDAP mail attribute (primary email address) for the user. 

-s surname

The user's LDAP surname (last name). This option is required. There is no default. 

D.19.3 Examples


Note –

This command prevents jsmith@sesta.com from logging into Calendar Server to access calendar data, but it does not delete jsmith’s data from the calendar database. If jsmith is currently logged into Calendar Server, he retains access to calendar data until he logs off.


D.20 start-cal

The start-cal utility starts the Calendar Server services in this order:

D.20.1 Requirements

D.20.2 Syntax

start-cal

D.20.3 Example

cal-svr-base/SUNWics5/cal/sbin/start-cal

For more information, see 12.1 Starting and Stopping Calendar Server 6.3 Processes.

D.21 stop-cal

The stop-cal utility stops all Calendar Server services.

D.21.1 Requirements

D.21.2 Syntax

stop-cal

D.21.3 Example

cal-svr-base/SUNWics5/cal/sbin/stop-cal

For more information, see 12.1 Starting and Stopping Calendar Server 6.3 Processes.

Appendix E Calendar Server Configuration Parameters

Calendar Server configuration parameters are stored in configuration files, including ics.conf and counter.conf.

This chapter provides the following information:

E.1 Editing the ics.conf Configuration File

Calendar Server configuration parameters are stored in the following file:

/etc/opt/SUNWics5/config/ics.conf

The ics.conf file is a ASCII text file, with each line defining a parameter and its associated value(s). The parameters are initialized during Calendar Server installation. After installation, you can edit the file using a text editor.


Caution – Caution –

Modify the settings for parameters in the ics.conf file only as described in Sun documentation or as directed by a customer support representative.

For example: Remote administration is not enabled for Calendar Server. Do not change the service.admin.port parameter, because it is already set to its required value by Calendar Server. Otherwise, the csadmind process might not run properly.


ProcedureTo edit the ics.conf file:

  1. Log in as a user who has administrator rights to the system where Calendar Server is running.

  2. Change to the /etc/opt/SUNWics5/config directory where the ics.conf file is located.

  3. Edit parameters in the ics.conf file using a text editor such as vi. Conventions for parameters are:

    • All parameters must be in lower case only.

      • A parameter and its associated value(s) must be separated by an equal sign (=), with spaces or tabs allowed before or after the equal sign. For example:

        service.http.idletimeout = "120"

      • A parameter value must be enclosed in double quotation marks ("). If a parameter allows multiple values, the entire value string must be enclosed in double quotation marks. For example:

        calstore.calendar.owner.acl=
        "@@o^a^rsf^g;@@o^c^wdeic^g"
      • A comment line begins with an exclamation point (!). Comment lines are for informational purposes only and are ignored by Calendar Server.

        Some parameters are released as comments, beginning with either one or two exclamation points (! or !!). To use this type of parameter, you must remove the exclamation point(s), supply a value (if needed), and then restart Calendar Server for the parameter to take effect.

        For example, to use !!caldb.dwp.server.[hostname].ip, you must remove the exclamation points (!!), supply a value for hostname, and then restart Calendar Server.

      • If a parameter is not in the ics.conf file, add the parameter and its associated value to the file.

      • If a parameter appears more than once, the value of the last parameter listed overrides the previous value.

      • All options must start at the beginning of a line.

  4. After you make changes to parameters in the ics.conf file, stop and then restart Calendar Server for the new configuration values to take effect.

    If you prefer, you can also stop Calendar Server before you edit the ics.conf file. For more information, see 12.1 Starting and Stopping Calendar Server 6.3 Processes.

E.2 Configuration Parameters (ics.conf) File

This section lists the various configuration parameters in the ics.conf file. For convenience, they are broken down into functional groups as follows:


Caution – Caution –

The parameters listed below merely show their default settings. To implement certain features, you might need to change one or more parameters to different values. Refer to the chapters in Part III, Customizing Your Calendar Server Configuration for instructions on how to implement features, including which parameters to use and which values to assign them.



Note –

Duplicate parameters are allowed in the ics.conf file. The system takes the value of the last instance of the parameter in the file.


E.2.1 Tips for Customizations to the Configuration File

The configuration file is big. There are many parameters. If you make customizations, it can be difficult to find them or remember why you changed the values. To avoid confusion, add your customizations to the end of the file in a section you create for that purpose. For example, you can create a comment line with the following text: ! My ics.conf Changes. Then add any new parameters or any parameters that you are modifying, and their values. Add comments to each parameter describing why the change was made, with the current date. This will give you a history of the changes made to the system for later reference.

Every time you start or restart Calendar Server, the system reads the entire configuration file. The more parameters the system must process, the longer it takes to start up the system. If there are many duplicate parameters, it can slow the process noticeably. To avoid this, comment out obsolete duplicate parameters.

E.2.2 Calendar Server Local Instance Configuration Parameters

The following table shows the configuration parameters starting with local., showing each parameter’s default value and description.

Table E–1 Local Server Instance Configuration Parameters in the ics.conf File

Parameter  

Default Value  

Description  

local.autoprovision

"yes"

Enables ("yes") or disables ("no") autoprovisioning of the user's calendar.

local.domain.language

"en"

Default language for domains in this Calendar Server instance. 

local.hostname

" "

Host name of the machine on which Calendar Server is installed. 

local.installeddir

cal-svr-base/SUNWics5/ cal

Directory path location where Calendar Server is installed. 

local.instancedir

cal-svr-base/SUNWics5/ cal

Directory path location where configuration files and data for this instance of Calendar Server are installed. 

local.instance.lockdir.path

cal-svr-base/SUNWics5/ cal/data/lock

Specifies the location where lock files for this server instance are stored. 

local.instance.counter.path

cal-svr-base/SUNWics5/ cal/lib/counter

Specifies the location where counter files for this server instance are stored. 

local.plugindir.path

" "

Directory path location where CSAPI plug-ins for this instance of Calendar Server are installed. 

local.rfc822header.allow8bit

"no"

Allow (y) or not allow (n) 8-bit headers in email messages sent by this server.

local.servergid

"icsgroup"

Group ID (gid) for Calendar Server files, such as counters and logs.

local.serveruid

"icsuser"

User ID (UID) for Calendar Server files, such as counters and logs.

local.sitelanguage

"en"

Default language for this instance of Calendar Server. 

local.smtp.defaultdomain

" "

Name of the default domain used to lookup an attendee’s calendar ID that corresponds to an email address. For example, jsmith resolves to jsmith@sesta.com if the value for this is setting is "sesta.com".

local.supportedlanguages

"en"

User languages supported by this instance of Calendar Server. 

E.2.3 Calendar Server LDAP Authorization Configuration Parameters

Table E–2 LDAP Authorization Configuration Parameters in the ics.conf File

Parameter  

Default Value  

Description  

local.authldapbasedn

" "

Base DN for LDAP authentication. If not specified, local.ugldapbasedn is used.

local.authldaphost

"localhost"

Host for LDAP authentication. If not specified, local.ugldaphost is used.

local.authldapbindcred

" "

Bind credentials (password) for user specified in local.authldapbinddn.

local.authldapbinddn

" "

DN used to bind to LDAP authentication host to search for user's dn. If not specified, or if the value is " ", its an anonymous bind.

local.authldapport

"389"

Port for LDAP authentication. If not specified, local.ugldapport is used.

local.authldappoolsize

"1"

Minimum number of LDAP client connections that are maintained for LDAP authentication. If not specified, local.ugldappoolsize is used.

local.authldapmaxpool

"1024"

Maximum number of LDAP client connections that are maintained for LDAP authentication. If not specified, local.ugldapmaxpool is used.

E.2.4 Calendar Server LDAP User and Group Search Configuration Parameters

Table E–3 LDAP Authorization Configuration Parameters in the ics.conf File

Parameter  

Default Value  

Description  

local.lookupldap.search.minwildcardsize

"3"

Specifies the minimum string size for wildcard searches in an attendee lookup search. Zero (0) means always do a wildcard search. 

local.ugldaphost

"localhost"

Host name of machine that stores the LDAP user preferences. 

E.2.5 Calendar Server User Preferences Configuration Parameters

Table E–4 User Preferences Configuration Parameters in the ics.conf File

Parameter  

Default Value  

Description  

local.enduseradmincred

" "

Bind credentials (password) for LDAP user preferences authentication. 

local.enduseradmindn

" "

DN used to bind to LDAP user preferences host. There is no default DN. If the value is " ", or not specified, anonymous bind is assumed.

local.ugldapbasedn

" "

Base DN for LDAP user preferences. Must be specified and cannot be blank. 

local.ugldapicsextendeduserprefs

"ceColorSet,

ceFontFace,

ceFontSizeDelta,

ceDateOrder,

ceDateSeparator,

ceClock,

ceDayHead,

ceDayTail,

ceInterval,

ceToolText,

ceToolImage,

ceDefaultAlarmStart,

ceSingleCalendarTZID,

ceAllCalendarTZIDs,

ceDefaultAlarmEmail,

ceNotifyEmail,

ceNotifyEnable,

ceDefaultView,

ceExcludeSatSun,

ceGroupInviteAll"

Values for the options in the icsExtendedUserPrefs attribute.

local.user.authfilter

"uid=%u"

Filter to use for user lookup. 

E.2.6 Calendar Server Calendar Store Configuration Parameters

The following table shows the Calendar Store Configuration parameters with each parameter’s default value and description. The Calendar Store holds all event and todo records.

Table E–5 Calendar Store Configuration Parameters in the ics.conf File

Parameter  

Default Value 

Description  

calstore.anonymous.calid

"anonymous"

Calendar ID (calid) used for anonymous logins.

user.allow.doublebook

"yes"

Determines if a user calendar can have more than one event scheduled for the same time slot when the calendar is created: 

  • "no" prevents double booking.

  • "yes" allows double booking.

calstore.calendar.default.acl

"@@o^a^r^g;
@@o^c^wdeic^g;
@^a^fs^g;
@^c^^g;
@^p^r^g"

Specifies the default access control permissions used when a user creates a calendar. The format is specified by a semicolon-separated list of access control entry (ACE) argument strings. 

For details on the ACE format, see 15.4 Calendar Access Control

To specify Access Control Entries for one or more calendars using the command-line utilities, see D.5 cscal.

calstore.calendar.owner.acl

"@@o^a^rsf^g;
@@o^c^wdeic^g"

Specifies the default access control settings for owners of a calendar. 

calstore.calendar.create.

lowercase

"no"

Specifies whether Calendar Server should convert a calendar ID (calid) to lowercase when creating a new calendar or when looking up a calendar using the LDAP CLD plug-in.

Although this parameter regulates the case of the original calid, it does not affect related LDAP attributes that set values for the owner, subscribed, and ACE permissions. Setting this parameter to “yes” may affect the use of Communications Express, since Communications Express relies on values set in the LDAP attributes such as icsCalendarOwned to determine the calid. Therefore, use caution if you intend to set this parameter to “yes.”

calstore.default.timezoneID

"America/
New_York"

Time zone ID to be used when: 

  • A time zone ID is not supplied

  • A calendar time zone ID is not found

  • A user time zone ID is not found

    An invalid value causes the server to use to the GMT (Greenwich Mean Time) time zone.

calstore.filterprivateevents

"yes"

Specifies whether Calendar Server filters (recognizes) Private and Time and Date Only (confidential) events and tasks. If "no", Calendar Server treats them the same as Public events and tasks.

calstore.freebusy.include.

defaultcalendar

"yes"

Specifies whether a user's default calendar is included in user's free/busy calendar list. 

calstore.freebusy.remove.

defaultcalendar

"no"

Specifies whether a user's default calendar can be removed from user's free/busy calendar list. 

calstore.group.attendee.maxsize

"0"

Maximum size of an LDAP group that will be expanded for an invitation. A value of "0" means to expand the group without regard to size. A value of -1 means no expansion of LDAP groups allowed.

calstore.group.freebusy.maxsize

"0"

Maximum number of users present in any legitimate mailing list (group) used for calendar free/busy lookups. The default value allows an unlimited number of users.  

If a group contains an extremely large number of users, there can be performance issues and/or high memory consumption when doing a free/busy lookup. 

calstore.recurrence.bound

"60"

Maximum number of events that can be created by a recurrence expansion. 

calstore.subscribed.include.

defaultcalendar

"yes"

Specifies whether a user's default calendar is included in the user's subscribed calendar list. 

calstore.subscribed.remove.

defaultcalendar

"no"

Specifies whether a user's default calendar can be removed from the user's subscribed calendar list. 

calstore.userlookup.maxsize

"200"

Maximum number of results returned from LDAP lookup from user search. Value of "0" means no limit.

calstore.unqualifiedattendee.

fmt1.type

"uid"

Specifies how Calendar Server treats strings, such as jdoe or jdoe:tv, when performing a directory lookup for attendees of an event. Allowable values are: uid, cn, gid, res, mailto, cap.

calstore.unqualifiedattendee.

fmt2.type

"mailto"

Specifies how Calendar Server treats strings with an at sign (@), such as jdoe@sesta.com, when performing a directory lookup for attendees of an event. Allowable values are: uid, cn, gid, res, mailto, cap.

calstore.unqualifiedattendee.

fmt3.type

"cn"

Specifies how Calendar Server treats strings with a space, such as john doe, when performing a directory lookup for attendees of an event. Allowable values are: uid, cn, gid, res, cap.

store.partition.primary.path

"."

Location of primary disk partition where calendar information is stored. 

E.2.7 Calendar Log Information Configuration Parameters

The following table shows the calendar log configuration parameters with each parameter’s default value and description.

Table E–6 Calendar Log Configuration Parameters in the ics.conf File

Parameter  

Default Value  

Description 

logfile.admin.logname.

"admin.log"

Name of log file for logging administrative tools. 

logfile.buffersize

"0"

Size of log buffers (in bytes). 

logfile.dwp.logname

"dwp.log"

Name of log file for logging Database Wire Protocol related administrative tools. 

logfile.expirytime

"604800"

Number of seconds before log files expire. 

logfile.flushinterval

"60"

Number of seconds between flushing buffers to log files. 

logfile.http.access.logname

"httpd.access"

Name of the current HTTP access log file. 

logfile.http.logname

"http.log"

Name of current log file for the cshttpd service.

logfile.http.access.

logname

"httpd.access"

Name of current HTTP access log file. 

logfile.logdir

"logs"

Directory location of log files. 

logfile.loglevel

"NOTICE"

Determines the level of detail the server will log. Each log entry is assigned one of these levels: CRITICAL, ALERT, ERROR, WARNING, NOTICE, INFORMATION, and DEBUG.

logfile.maxlogfiles

"10"

Maximum number of log files in log directory. 

logfile.maxlogfilesize

"2097152"

Maximum size of each log file (in bytes). 

logfile.maxlogsize

"20971520"

Maximum disk space for all log files (in bytes). 

logfile.minfree

diskspace

"5242880"

Minimum free disk space (in bytes) that must be available for logging. 

logfile.notify.logname

"notify.log"

Name of log file for the csnotifyd service.

logfile.rollovertime

"86400"

Number of seconds before log files are rotated. 

logfile.store.logname

"store.log"

Store log file name. 

service.http.commandlog

"no"

This parameter is for debugging only. If set to "yes", the system logs all incoming commands into the http.commands log file.

Do not use this during production runtime. It will fill up the log file very quickly and could cause performance degradation. 

E.2.8 Calendar Server Administrator Configuration Parameters

The following table lists the ics.conf parameters that pertain to administrators.

Table E–7 Configuration Parameters for Administrators

Parameter  

Default Value  

Description 

service.siteadmin.

cred

" "

Password of the user ID specified as the Calendar Server administrator. This value is supplied at installation and is required by the installation program. 

service.siteadmin.

userid

"calmaster"

User ID of the person designated as the Calendar Server administrator. This value is supplied at installation and is required by the installation program. 

service.admin.calmaster.

overrides.accesscontrol

"no"

Indicates whether the Calendar Server administrator can override access control. 

service.admin.calmaster.

wcap.allowgetmodify

userprefs

"no"

Indicates whether the Calendar Server administrator can get and set user preferences using WCAP commands. 

service.admin.ldap.enable

"yes"

If "yes", enables LDAP for user authentication of the user specified in service.siteadmin.userid.

E.2.9 Calendar Server Services Configuration

The following table shows the various services configuration parameters with each parameter’s default value and description.

Table E–8 Services Configuration Parameters in the ics.conf File

Parameter 

Default Value  

Description 

service.admin.alarm

"yes"

Enable ("yes") or disable ("no") alarm notifications for administration tools.

local.store.

checkpoint.enable

"yes"

If "yes", start the csadmind database checkpoint thread.

service.admin.

dbcachesize

"8388608"

Maximum cache size (in bytes) for Berkeley Database for administration sessions. 

local.store.

deadlock.enable

"yes"

If "yes", start the csadmind database deadlock detection thread.

service.admin.

diskusage

"no"

If "yes", start the csadmind low disk space monitor thread.

service.admin.enable

"yes"

If "yes", start the csadmind service when starting all services and stop csadmind when stopping all services.

service.admin.

idletimeout

"120"

Number of seconds before timing out an HTTP connection in csadmind.

service.admin.

maxsessions

"100"

Maximum number of administration sessions allowed. 

service.admin.

maxthreads

"10"

Maximum number of running threads per administration session. 

service.admin.

numprocesses

N/A 

Maximum number of a concurrent administration processes allowed. 

service.admin.port

N/A 

**CAUTION** 

Set by the system. Do not change. 

service.admin.

resourcetimeout

"900"

Number of seconds before timing out an administration connection. 

service.admin.

serverresponse

"no"

If "yes", start the csadmind service response thread.

service.admin.

sessiondir.path

" "

Temporary directory for administration session requests. 

service.admin.

sessiontimeout

"1800"

Number of seconds before timing out an HTTP session in csadmind.

service.admin.

sleeptime

"2"

Number of seconds to wait between checking for started, stopped, or ready calendar service. 

service.admin.

starttime

"300"

Number of seconds to wait for any calendar service to start. 

service.admin.

stoptime

"300"

Number of seconds to wait for any calendar service to stop. 

service.admin.

stoptime.next

"60"

Number of seconds to wait between sending stop commands to any calendar service. 

service.dcroot

"o=internet"

Root suffix of the DC tree in the directory. 

service.

dnsresolveclient

"no"

If "yes", client IP addresses are checked against DNS if allowed HTTP access.

service.plaintext

loginpause

"0"

Number of seconds to delay after successfully authenticating a user using plain text passwords. 

service.http.admins

"calmaster"

Space separated list of user ID's with administration rights to this Calendar Server. 

service.http.

allowadminproxy

"yes"

If "yes", allow login via proxy.

service.http.

allowanonymouslogin

"yes"

If "yes", allow anonymous (no authentication) access. This is a special type of login that is allowed only specified, restricted access (usually read only access to public calendars).

service.http

.calendarhostname

"" (Null)

HTTP host for retrieving HTML documents. 

service.http.cookies

"yes"

Tells the server to whether or to support cookies. It must be set to "yes" to enable single sign-on.

service.http.

dbcachesize

"8388608"

Maximum cache size of Berkeley DB for HTTP sessions. 

service.http.

domainallowed

"" (Null)

If specified and not "", filter to allow access based on TCP domains. For example, "ALL:LOCAL.sesta.com" would allow local HTTP access to anyone in the sesta.com domain. Multiple filters are separated by CR-LF(line feed).

EXCEPT Operator 

You can use the EXCEPT operator to create exceptions to matching names or patterns when you have multiple entries in a list. For example, the expression: 

list1 EXCEPT list2

means that anything that matches list2 is matched, unless it also matches list2. 

For example: 

ALL: ALL EXCEPT isserver.siroe.com 

If this were a Deny filter, it would deny access to all services to all clients except those on the host machine, isserver.siroe.com. 

EXCEPT clauses can be nested. The expression: 

list1 EXCEPT list2 EXCEPT list3 

is evaluated as if it were 

list1 EXCEPT (list2 EXCEPT list3) 

service.http.

domainnotallowed

"" (Null)

If specified and not " ", filter to not allow access based on TCP domains. For example, "ALL:LOCAL.sesta.com" would deny HTTP access to anyone in the sesta.com domain. Multiple filters must be separated by CR-LF (line-feed).

EXCEPT Operator. For details about this operator, see the preceding entry, service.http.domainallowed.

service.http.

attachdir.path

"."

Directory location relative to local.queuedir (or an absolute path if specified) where imported files are temporarily stored.

service.http.

ipsecurity

"yes"

If "yes", all requests that reference an existing session are verified as originating from the same IP address. 

service.http.enable

"yes"

If "yes", start the cshttpd service when starting all services and stop cshttpd when stopping all services.

service.http.

idletimeout

"120"

Number of seconds before timing out an HTTP connection. 

service.http.

ldap.enable

"yes"

If "yes", LDAP connections for authentication and user preferences are created and maintained. 

service.http.listenaddr

"INADDR_ANY"

Specifies the TCP address that HTTP services will listen on for client requests. "INADDR_ANY" indicates any address.

service.http.logaccess

"no"

If "yes", HTTP connections to server are fully logged. 

service.http.

maxsessions

"5000"

Maximum number of HTTP sessions in cshttpd service.

service.http.

maxthreads

"20"

Maximum number of threads to service HTTP requests in cshttpd service.

service.http.

numprocesses

"1"

Maximum number of concurrently running HTTP service (cshttpd) processes that should run on a server.

For a server that has multiple CPU's, see 21.8 Using Load Balancing Across Multiple CPU's

service.http.port

"80"

Port for HTTP requests from Calendar Server users. 

service.http.

proxydomainallowed

""

If specified and not "", filter for allowing proxy login based on TCP domains. Same syntax as service.http.domainallowed.

service.http.

resourcetimeout

"900"

Number of seconds before timing out an HTTP session. 

service.http.

sessiondir.path

"http"

Temporary directory for HTTP sessions. 

service.http.sessiontimeout

"1800"

Number of seconds before timing out an HTTP session in cshttpd service.

service.http.sourceurl

" "

Directory relative to executable where all URL references to files are stored. 

service.http.tmpdir

 

Directory relative to executable where all URL references to files are stored. 

The default is: /var/opt/SUNWics5/tmp

service.http.uidir.path

"html"

Directory that contains the default calendar client. If allowing only WCAP access, set to "".

service.ldapmemcache

"no"

If "yes", use cache in LDAP SDK. 

service.ldapmemcachettl

"30"

If service.ldapmemcache is "yes", pass in this value to the LDAP SDK. This is the maximum number of seconds that an item can be cached. If 0, there is no limit to the amount of time that an item can be cached.

service.ldapmemcachesize

"131072"

If service.ldapmemcache is "yes", pass in this value to the LDAP SDK. This is the maximum amount of memory in bytes that the cache will consume. If 0, the cache has no size limit.

service.wcap.anonymous

.allowpubliccalendarwrite

"yes"

If "yes", allow anonymous users to write to publicly writable calendars. 

service.wcap.format

"text/calendar"

Specifies the default output format for commands currently applied only for freebusy. 

service.wcap.

freebusybegin

"30"

Specifies the default offset from the current time in days for get_freebusy for beginning of the range.

service.wcap.

freebusyend

"30"

Specifies the default offset from the current time in days for get_freebusy for end of the range.

service.wcap.freebusy.

redirecturl

““ 

For migration purposes, when migration is only partially done and calendars are split between the originating database and the Calendar Server target database. The URL of the originating database to look in, if a calendar is not found in the Calendar Server database. 

service.wcap.allow

createcalendars

"yes"

If "yes", allow calendars to be created.

service.wcap.allow

deletecalendars

"yes"

If "yes", allow calendars to be deleted.

service.wcap.allow

changepassword

"no"

If "yes", allows user passwords to be changed.

service.wcap.allow

publicwritablecalendars

"yes"

If "yes", allow users to have publicly writable calendars.

service.wcap.allow

setprefs.cn

"no"

If "yes", allow the set_userprefs.wcap attribute to modify the user preference cn (LDAP user's common name).

service.wcap.allow

setprefs.givenname

"no"

If "yes", allow the set_userprefs.wcap attribute to modify the user preference givenname (LDAP user's given name).

service.wcap.allow

setprefs.icsCalendar

"no"

If "yes", allow the set_userprefs.wcap attribute to modify the user preference icsCalendar (a user's default calendar identifier).

service.wcap.allow

setprefs.mail

"no"

If "yes", allow the set_userprefs.wcap attribute to modify the user preference mail (user's email address).

service.wcap.allowsetprefs.

preferredlanguage

"no"

If "yes", allow the set_userprefs.wcap attribute to modify the user preference preferredlanguage (LDAP user's preferred language).

service.wcap.allow

setprefs.sn

"no"

If "yes", allow the set_userprefs.wcap attribute to modify the user preference sn (LDAP user's surname).

service.wcap.allow

setprefs.nswccalid

"no"

If "yes", allow the set_userprefs.wcap attribute to modify the user preference nswccalid, which is the user's default calendar ID.

service.wcap.login.

calendar.publicread

"no"

If "yes", default user calendars are initially set to publicly readable and privately writable. If "no", default user calendars are initially set to privately readable and writable.

service.wcap.userprefs.

ldapproxyauth

"no"

If "yes", enables LDAP proxy authorization for get_userprefs.wcap command. If "no", anonymous LDAP search is performed.

service.wcap.validateowners

"no"

If "yes", the server must validate that each owner of a calendar exists in the directory (through LDAP or a CSAPI compatible user directory mechanism).

service.wcap.version

"3.0"

WCAP version. 

E.2.10 Calendar Server SSL Configuration Parameters

The following table shows the ics.conf SSL Configuration parameters with each parameter’s default value and description. While most of the SSL parameters take the default values, two of the parameters require you to change the value from the system default to the SSL value, as follows:

The table that follow shows the ics.conf parameters and their default settings. Verify that your ics.conf parameters have the appropriate values:

Table E–9 Configuration Parameters for SSL

Parameter  

Default Value  

Description  

encryption.rsa.

nssslactivation

"on"

Enables the RSA Cypher Encryption Family Services for SSL. 

encryption.rsa.

nsssltoken

"internal"

Specifies the location of the RSA Cypher Encryption Family token. 

encryption.rsa.

nssslpersonalityssl

"SampleSSLServerCert"

Specifies the certificate name for the RSA Cypher Encryption Family. 

service.http.tmpdir

/var/opt/SUNWis5/tmp

doma 

Specifies a temp directory. 

service.http.uidir.

path

"html"

Specifies directory where the UI files are found. 

service.http.ssl.

cachedir

"."

Specifies the physical path location for the SSL cache. 

service.http.ssl.

cachesize

"10000"

Specifies the maximum size of the SSL cache database. 

service.http.ssl.

usessl

"no"

For SSL configuration, change this value to "yes".

Specifies whether the cshttpd process should use the SSL subsystem.

service.http.ssl.

port.enable

"no"

For SSL configuration, change this value to “yes”. 


Note –

This does not disable the HTTP process from listening to its port. There is no way to actually disable HTTP, but you can assign it to another port that is non-functional.

Do not set service.http.enable="no". That would disable the HTTPS process also.


service.http.ssl.

port

"443"

Specifies the SSL port number where the cshttpd process listens for HTTPS requests from Calendar Server users.

Do not set this to the same default port used by HTTP ("80").

service.http.ssl.

securesession

"yes"

Specifies whether to encrypt the entire session. 

local.ssldbpath

"/etc/opt/SUNWics5/config"

Specifies the physical path location of the SSL Certificate Database. 

service.http.ssl.certdb.password — This parameter was removed from the ics.conf file. It was replaced by a configuration file.

sslpassword.com

sslpassword.conf is a text file that contains the certificate database password.

This file is used by the certutil utility but not by Calendar Server. Create sslpassword.conf in the following directory:

/etc/opt/SUNWics5/config

service.http.ssl.

sourceurl

"https://localhost:443"

Specifies the SSL host name and port number for the originating source URL. 

service.http.ssl.

ssl2.ciphers

""

Specifies ciphers for SSL2. 

service.http.ssl.

ssl2.sessiontimeout

"0"

Specifies the session timeout for SSL2. 

service.http.ssl.

ssl3.ciphers

"rsa_rc4_40_md5,
rsa_rc2_40_md5,
rsa_des_sha,
rsa_rc4_128_md5,
rsa_3des_sha"

Specifies a list of supported or valid SSL ciphers. 

service.http.ssl.

ssl3.sessiontimeout

"0"

Specifies the timeout value for the SSL session. 

E.2.11 Calendar Server Domain Configuration Parameters

The following table shows the domain configuration parameters with each parameter’s default value and description.

Table E–10 Configuration Parameters for Multiple Domain Support

Parameter  

Default Value  

Description  

local.domain.language

"en"

Default language for domains in this instance of Calendar Server. 

local.schemaversion

"1"

Specifies the version of the LDAP schema: 

  • "1" Sun LDAP Schema version 1. See also service.dcroot

  • "2" Sun LDAP Schema version 2. See also service.schema2root

service.dcroot

" "

Specifies the root suffix of the DC tree in the LDAP directory, if local.schemaversion="1". For example: "o=internet"

service.schema2root

" "

Specifies the root suffix underneath which all domains are found, if local.schemaversion="2". For example: "o=sesta.com"

service.defaultdomain

" "

Specifies the default domain for this instance of Calendar Server. Used when a domain name is not supplied during a login. For example: "sesta.com".

service.loginseparator

"@+"

Specifies a string of separators used for the login-separator when Calendar Server parses userid[login-separator]domain. Calendar Server tries each separator in turn.

service.siteadmin.userid

" "

Specifies the user ID of the domain administrator. 

service.siteadmin.cred

" "

Specifies the password of the domain administrator. 

service.virtualdomain.

support

"yes"

Enables ("yes") or disables ("no") support for multiple domains.


Caution – Caution –

Do not change this parameter to "no". Calendar Server supports multiple domains by default.


E.2.12 Configuration Parameters to Enable Email Notifications

The following three parameters enable or disable the system to send out notifications for cancellations, invitations and replies.

Table E–11 Alarm Notification Configuration Parameters in the ics.conf File

Parameter  

Default Value  

Description 

ine.cancellation.enable

"yes"

Determines whether email notifications are sent to attendees when an event is cancelled. 

ine.invitation.enable

"yes"

Determines whether email notifications are sent to attendees invited to an event. 

ine.reply.enable

"yes"

Determines whether email notifications are sent to the organizer when an attendee replies to an invitation. 

E.2.13 Alarm Notification Parameters

The following table shows the alarm notification server configuration parameters with each parameter’s default value and description.

Table E–12 Alarm Notification Configuration Parameters in the ics.conf File

Parameter  

Default Value  

Description 

alarm.diskstat.

msgalarmdescription

"percentage calendar partition disk space available"

Description sent with insufficient disk space messages. 

alarm.diskstat.

msgalarmstatinterval

"3600"

Number of seconds between monitoring disk space. 

alarm.diskstat.

msgalarmthreshold

"10"

Percentage of available disk space that triggers sending a warning message. 

alarm.diskstat.

msgalarmthresholddirection

"-1"

Whether alarm.diskstat.msgalarmthreshold is above or below percentage. -1 is below and 1 is above.

alarm.diskstat.

msgalarmwarninginterval

"24"

Number of hours between sending warning messages about insufficient disk space. 

alarm.msgalarmnoticehost

"localhost"

The host name of the SMTP server used to send server alarms. 

alarm.msgalarmnoticeport

"25"

The SMTP port used to send server alarms. 

alarm.msgalarmnoticercpt

"Postmaster
@localhost"

The email address to whom server alarms sent. 

alarm.msgalarmnoticesender

"Postmaster
@localhost"

The email address used as the sender when the server sends alarms. 

alarm.msgalarmnoticetemplate

""

The default format used to send email alarms: 

"From: %s\nTo: %s\nSubject: ALARM: %s of \"%s\" is n\n%s\n"

alarm.responsestat.

msgalarmdescription

"calendar service not responding"

Description sent with no-service-response messages. 

alarm.responsestat.

msgalarmstatinterval

"3600"

Number of seconds between monitoring services. 

alarm.responsestat.

msgalarmthreshold

"100"

Only trigger sending a warning message if there is no service response. 

alarm.responsestat.

msgalarmthresholddirection

"-1"

Specifies whether alarm.responsestat.

msgalarmthreshold is the percentage above or below the threshold.

A value of -1 is below, and a value of 1 is above.

alarm.responsestat.

msgalarmwarninginterval

"24"

Number of hours between sending warning messages about no service response sent out. 

E.2.14 Calendar Lookup Database Configuration

The following table shows the Calendar Lookup Database (CLD) parameters with each parameter’s default value and description.

Table E–13 Calendar Lookup Database (CLD) Parameters in the ics.conf File

Parameter 

Default Value  

Description  

csapi.plugin.calendarlookup

"no"

Enable ("yes") or disable ("no") calendar lookup plug-ins.

csapi.plugin.calendarlookup.name

"*"

Specifies the name of a specific calendar lookup plug-in to load. If this value is an asterisk ("*"), Calendar Server loads all plug-ins.

caldb.cld.type

"local"

Use "local" for a machine where everything is on the same machine, or for a machine that functions only as a back-end machine.

Use "directory" for machines that are only a front-end, or for a machine which functions as both the front-end and back-end.

caldb.dwp.server.default

" "

Specifies the fully qualified default DWP server name used by Calendar Server if a user or resource calendar entry in the LDAP server database does not have an icsDWPHost attribute.

If the LDAP entry for a user logging into Calendar Server (login.wcap), does not have an icsDWPHost attribute, Calendar Server uses the value of this parameter to add the attribute.

If a user LDAP entry already has an icsDWPHost attribute, caldb.dwp.server.default is not used.

This name must be resolvable by your Domain Name Service (DNS) into a valid IP address. 

caldb.cld.cache.enable

"yes"

Enables ("yes") or disables ("no") the Calendar Lookup Database (CLD) cache option. For optimum performance for the LDAP CLD plug-in, set to "yes".

caldb.cld.cache.logfilesizemb

"10"

Specifies the maximum size in megabytes of the checkpoint file. 

caldb.cld.cache.mempoolsizemb

"4"

Specifies the size in megabytes of shared memory. 

caldb.cld.cache.maxthread

"1000"

Specifies the maximum number of database threads. 

caldb.cld.cache.homedir.path

"."

Specifies the location of database event, task, and alarm files for the CLD cache option. The default value of "." specifies that these files are stored in the /var/opt/SUNWics5/csdb/cld_cache directory.

caldb.cld.cache.checkpointinterval

"60"

Specifies the number of seconds between checkpoints. 

caldb.cld.cache.circularlogging

"yes"

Specifies whether to remove the checkpoint files after they are synchronized for the CLD cache option. 

caldb.dwp.server.host-name.ip

" "

Specifies the host name of a server that is storing a calendar database. The server must be running the DWP (csdwpd) service. This name must be resolvable by your Domain Name Service (DNS) into a valid IP address. This parameter is used by the LDAP CLD plug-in. 

Note: In each part of the parameter, host-name must be identical and fully qualified. For example:

caldb.dwp.server.sesta.com.ip="sesta.com"

caldb.dwp.connthreshold

"1"

Maximum number of backlogged requests before the server obtains a new network connection. 

caldb.dwp.initconns

"2"

Initial number of connections for the Database Wire Protocol service client to make to each Database Wire Protocol service host. 

caldb.dwp.initthreads

"2"

Initial number of threads for handling Database Wire Protocol service requests. 

caldb.dwp.maxcons

"1000"

Maximum number of connections allowed to a server using the Database Wire Protocol service. 

caldb.dwp.maxthreads

"20"

Maximum number of threads allowed to a server using the Database Wire Protocol service. 

caldb.dwp.md5

"no"

Specifies if the server performs MD5 (Message Digest 5) one-way hash checking of all Database Wire Protocol service requests. (One-way hash functions are used to create digital signatures for message authentication.) 

  • "no" disables MD5 hash checking.

  • "yes" enables MD5 hash checking.

caldb.dwp.server.hostname.ip

" "

Specifies the IP address of the server using the Database Wire Protocol (DWP) service at the specified machine’s hostname. 

caldb.dwp.server.hostname.port

"59779"

Specifies the port number of the server using the Database Wire Protocol (DWP) service at the specified machine’s hostname. 

caldb.dwp.server.back-end-server.admin

" "

On a front-end server, specifies the user ID that is used for authentication for a DWP connection to a back-end server, where back-end-server is the name of the server. 

caldb.dwp.server.back-end-server.cred

" "

On a front-end server, specifies the password that is used for authentication for a DWP connection to a back-end server, where back-end-server is the name of the server.

caldb.dwp.stacksize

"65536"

Stack size for Database Wire Protocol service threads. 

caldb.cld.directory.ldapbasedn

none 

Base DN to authenticate against if LDAP plug-in is used for the calendar locate mechanism. 

caldb.cld.directory.ldaphost

none 

Host name of the LDAP server to access if an LDAP plug-in is used for the calendar locate mechanism. 

caldb.cld.directory.ldapbindcred

none 

Bind credentials (password) for the user specified in the setting local.authldapbinddn if an LDAP plug-in is used for the calendar locate mechanism.

caldb.cld.directory.ldapbinddn

none 

DN used to bind to for authentication to search for user's DN if an LDAP plug-in is used for the calendar locate mechanism. 

caldb.cld.directory.ldapport

"389"

Port number of the LDAP server to access if an LDAP plug-in is used for the calendar locate mechanism. 

csapi.plugin.authentication

"no"

If "yes", load only the plug-in specified in csapi.plugin.authentication.name or if not specified, load all authentication class plug-ins in alphabetical order. For authentication, use each of these plug-ins in alphabetical order.

csapi.plugin.authentication.name

" "

If csapi.plugin.loadall is "no" and csapi.plugin.authentication is "yes", only load this specific plug-in. If not specified or blank (" "), load all authentication class plug-ins.

logfile.dwp.buffersize

"0"

Size of Database Wire Protocol service log buffers (in bytes). 

logfile.dwp.expirytime

"604800"

Number of seconds before the Database Wire Protocol service log files expire. 

logfile.dwp.flushinterval

"60"

Number of seconds between flushing buffers to the Database Wire Protocol service log files. 

logfile.logdir

"logs"

Directory location of the Database Wire Protocol service log files. 

logfile.dwp.loglevel

"Notice"

Determines the level of detail the server will log for the Database Wire Protocol service. Each Database Wire Protocol log entry is assigned one of the following levels (starting with the most severe): Critical, Error, Warning, Notice, Information, and Debug. If you set this preference to Critical, the server will log the least amount of detail. If you want the server to log the most amount of detail, specify Debug. For example, if you specify Warning, only Critical, Error, and Warning level log entries are logged. 

logfile.dwp.maxlogfiles

"10"

Maximum number of Database Wire Protocol related log files in log directory. 

logfile.dwp.maxlogfilesize

"2097152"

Maximum size of each Database Wire Protocol log file (in bytes). 

logfile.dwp.maxlogsize

"20971520"

Maximum disk space for all Database Wire Protocol log files (in bytes). 

logfile.dwp.minfreediskspace

"5242880"

Minimum free disk space that must be available for logging Database Wire Protocol service activity (in bytes). When this value is reached, the server will attempt to free disk space by expiring old log files. All logging will be paused if no space can be freed up. 

logfile.dwp.rollovertime

"86400"

Number of seconds before Database Wire Protocol service log files are rotated. 

service.dwp.admin.userid

" "

On a back-end server, specifies the user ID that is used to authenticate a DWP connection. This parameter is optional. If a back-end server does not specify a user ID, no authentication is performed. 

service.dwp.admin.cred

" "

On a back-end server, specifies the password that is used to authenticate a DWP connection. This parameter is optional. If a back-end server does not specify a password, no authentication is performed. 

service.dwp.calendarhostname

"localhost"

The hostname of the machine on which the Database Wire Protocol service is running. 

service.dwp.maxthreads

"1000"

Maximum number of concurrently running Database Wire Protocol service threads. 

service.dwp.numprocesses

"1"

Maximum number of concurrently running Database Wire Protocol (DWP) service (csdwpd) processes that should run on a server.

For a server that has multiple CPU's, see 21.8 Using Load Balancing Across Multiple CPU's

service.dwp.enable

"no"

If "yes", start the csdwpd service when starting all services and stop csdwpd when stopping all services

service.dwp.idletimeout

"86400"

Amount of time (in seconds) before closing the Database Wire Protocol service persistent connections that are idle. 

service.dwp.port

"59779"

Port number that the Database Wire Protocol service listens to. This value is the default port for the LDAP CLD plug-in. 

service.dwp.ldap.enable

"yes"

Enable ("yes") or disable ("no") LDAP for remote user authentication for the Database Wire Protocol (csdwpd) service.

service.calendarsearch.ldap

"yes"

Specifies whether Calendar Server searches the LDAP directory and then the calendar database ("yes") or only the calendar database ("no").

E.2.15 Calendar Server LDAP Data Cache Configuration Parameters

The following table describes the configuration parameters in the ics.conf file for the LDAP data cache.

Table E–14 LDAP Data Cache Configuration Parameters

Parameter  

Description 

local.ldap.cache.enable

Enables ("yes") or disables ("no") the LDAP data cache. The default is "no".

local.ldap.cache.checkpointinterval

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

local.ldap.cache.circularlogging

Specifies whether or not to remove the old cache files. The default is "yes".

local.ldap.cache.homedir.path

Specifies the physical location of LDAP data cache database. The default is /var/opt/SUNWics5/csdb/ldap_cache.

local.ldap.cache.logfilesizemb

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

local.ldap.cache.maxthreads

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

local.ldap.cache.mempoolsizemb

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

local.ldap.cache.entryttl

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

local.ldap.cache.stat.enable

Specifies whether or not to log 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. 

local.ldap.cache.stat.interval

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

local.ldap.cache.cleanup.interval

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

E.2.16 Group and Resource Calendar Configuration Parameters

To configure group and resource calendars, use the parameters found in the following table.

Table E–15 Configuration Parameters for Resource Calendars

Parameter  

Default Value  

Description  

Use the following parameters only for groups: 

local.lookupldap

searchattr.groupid

"groupid"

This is a group's unique identifier. Similar to a uid for a user.

group.allow.doublebook

"no"

Determines if a group calendar can have more than one event scheduled for the same time slot when the calendar is created: 

  • "no" prevents double booking.

  • "yes" allows double booking.

    This parameter is used only when a group calendar is created.

    After a group calendar is created, Calendar Server checks the calendar properties (ics50calprops.db) to determine if double booking is allowed.

group.default.acl

see the description at right 

The default access control list for group calendars. 

The default is: "@@o^a^r^g;@@o^c^wdeic^g;@^a^rsf^g"

group.invite.

autoprovision

"yes"

Specifies whether a group calendar should be created when an invitation is sent to a group that does not yet have a default calendar. 

group.invite.

autoaccept

"no"

Specifies whether invitations to a group should be auto-accepted. 

group.invite.expand

"yes"

Specifies whether a group should be expanded when invited, such that all members show on the invitation. 

Use the following parameters only for resources: 

resource.allow.

doublebook

"no"

Determines if a calendar that belongs to a resource (such as a conference room or audio visual equipment) can have more than one event scheduled for the same time slot when the calendar is created: 

  • "no" prevents double booking.

  • "yes" allows double booking.

    This parameter is used only when a resource calendar is created.

    After a resource calendar is created, Calendar Server checks the calendar properties (ics50calprops.db) to determine if double booking is allowed.

    If you need to change the calendar properties for a resource calendar to allow or disallow double booking, use csresource with the -k option.

resource.default.acl

 

Specifies the default access control permissions used when a resource calendar is created. 

The default is: "@@o^a^r^g;@@o^c^wdeic^g;@^a^rsf^g"

resource.invite.

autoprovision

"yes"|"no"

Specifies whether resource calendars should be created automatically when an invitation is sent to a resource that does not have a default calendar yet. 

resource.invite.

autoaccept

"yes"|"no"

Specifies whether invitations sent to resources should be automatically accepted. 

Use the following parameters for both groups and resources: 

local.lookupldap

searchattr.owner

"owner"

Attribute to use for groups and resource owners. Default is "owner". Same attribute used as the default for both groups and resources; changing it for one changes it for the other.

local.lookupldap

searchattr.coowner

 

Attribute to use for groups and resource owners. Same attribute used as the default for both groups and resources; changing it for one changes it for the other. 

Default is "icsSecondaryowners".

local.lookupldap

searchattr.defaultacl

 

Attribute used to hold the default access control strings for groups and resources.  

Default is "icsDefaultacl"

local.lookupldap

searchattr.doublebook

 

Attribute used at autoprovisioning of group and resource calendars to specify whether more than one event can be scheduled for the same time slot. 

Default is "icsDoublebooking"

local.lookupldap

searchattr.autoaccept

 

Attribute used at autoprovisioning of group and resource calendars to specify whether events will automatically be accepted. 

Default is "icsAutoaccept"

local.lookupldap

searchattr.timezone

 

Attribute used at autoprovisioning of group and resource calendars to specify the time zone the calendar will use. 

Default is "icsTimezone"

E.2.17 Calendar Server Single Sign-on (SSO) Configuration Parameters

E.2.17.1 Configuring SSO Through Access Manager

The following table shows the SSO configuration parameters with each parameter’s default value and description when you are using Access Manager.

Table E–16 SSO Configuration Parameters in the ics.conf File (Through Access Manager)

Parameter  

Default  

Description  

local.calendar.sso.

singlesignoff

”yes”

Enables (”yes”) or disables (”no”) SSO for Calendar Server.

local.calendar.sso.

amcookiename

“iPlanetDirectoryPro”

Specifies the name of the Access Manager SSO cookie. 

local.calendar.sso.

amnamingurl

”http://AccessManager:port
/amserver/namingservice”

Specifies the URL of the Access Manager SSO naming service.

local.calendar.sso.

amloglevel

”3”

Specifies the log level for Access Manager SSO. Range is from 1 (quiet) to 5 (verbose). 

local.calendar.sso.

logname

“am_sso.log”

Specifies the name of the Access Manager SSO API log file. 

E.2.17.2 Configuring SSO Through Communications Servers Trusted Circle Technology

The following table shows the SSO configuration parameters with each parameter’s default value and description when the Communications Servers trusted circle technology.

Table E–17 SSO Configuration Parameters in the ics.conf File Using Communications Servers Trusted Circle Technology

Parameter  

Default Value  

Description  

sso.appid

"ics50"

Unique application ID for this Calendar Server installation. Each trusted application must also have a unique application ID. For example: sso.appid="ics50"

sso.appprefix

"ssogrp1"

The prefix value to be used for formatting the SSO cookies. The same value needs to be used by all trusted applications, because only SSO cookies with this prefix will be recognized by Calendar Server. 

The application prefix must not end with a hyphen (-), because Calendar Server appends a hyphen to the value. For example:

sso.appprefix="ssogrp1"

sso.appid.url

none 

Verification URL for the value specified for sso.appid. For example:

"sso.ics50.url="http://siroe.com:80/
default.html"

sso.nnn.ip

none 

IP address of the value specified for sso.appid. For example: sso.ics50.ip=

"123.12.456.123"

sso.cookiedomain

"."

Causes the browser to send a cookie only to servers in the specified domain. 

The value must begin with a period (.). For example:

".sesta.com"

sso.enable

"1"

Enables or disables SSO: 

  • "1" (default) enables SSO functions.

  • "0" disables SSO functions.

    If this parameter is missing from ics.conf, Calendar Server ignores SSO functions.

sso.singlesignoff

"true"

If set to "true", the server removes all SSO cookies for the user that match the value for sso.appprefix when the user logs out. If "false" the server removes only its SSO user cookie.

sso.userdomain

" "

Sets the domain used as part of the user's SSO authentication. 

sso.appid.url

" "

Specifies the verify URL values for peer SSO hosts. A parameter is required for each trusted peer. 

appid is the application ID of a peer SSO host whose SSO cookies are to be trusted. For Calendar Server, the appid is ics50.

verifyurl identifies the URL of the trusted peer in the format: "http://host:port/VerifySSO?". Do not omit the question mark (?) after VerifySSO.

host is the URL of the host, and port is the port number for the host. 

For example, for Calendar Server on sesta.com with port number 8883:

sso.ics50.url=

"http://sesta.com:8883/VerifySSO?"

E.2.18 Calendar Server Group Scheduling Engine (GSE) Configuration Parameters

The following table shows the Group Scheduling Engine (GSE) configuration parameters with each parameter’s default value and description.

Table E–18 Group Scheduling Engine (GSE) Configuration Parameters in the ics.conf File

Parameter  

Default Value  

Description  

gse.autorefresh

replystatus

"yes"

Specifies if the auto refresh feature is enabled or disabled. If auto refresh is enabled, after an attendee replies to an event organizer, that attendee’s reply status is automatically propagated to other attendees for that scheduled event. 

  • "yes" enables auto refresh.

  • "no" disables auto refresh.

gse.belowthreshold

timeout

"3"

Specifies (in seconds) how long to wait before the server scans the schedule queue for incoming jobs. If there are more jobs in the queue than the maximum threads allocated, the last thread will always scan the job queue again. Therefore, this setting only takes effect when the number of jobs is below the maximum threads allocated. 

Increasing this number reduces the frequency the server scans the job queue and improves overall performance. 

gse.maxthreads

"10"

Specifies the maximum number of concurrent threads the server uses to process the schedule queue. Each thread processes one job in the queue. 

gse.retryexpired

interval

"86400"

Specifies (in seconds) the maximum length of time the server will retry to complete a group scheduling job. If the time exceeds the maximum length of time specified, the server treats the job as a retry expired condition and reports the error. 

Note that the default of 86400 seconds equals one day. 

gse.retryinterval

"300"

Specifies (in seconds) how often the server will retry a previous failing job. The server retries a failing job only when a network error is encountered. The server treats most such errors, however, as fatal errors and does not consider them as retries. 

gse.stacksize

"65535"

Specifies the maximum stack size (in bytes) of a group scheduling thread. 

E.2.19 Calendar Server Berkeley Database Configuration Parameters

The following table lists the ics.conf parameters used to configure database handling, and gives each parameter’s default value and description.

Table E–19 Database Configuration Parameters in the ics.conf File

Parameter  

Default Value  

Description 

caldb.berkeleydb.

checkpointinterval

"60"

Number of seconds between checkpointing database transactions. 

caldb.berkeleydb.

circularlogging

"yes"

If "yes" remove database checkpoint files after their transactions are synchronized. Do not set this to “no” unless you have enabled automatic backups.

caldb.berkeleydb.

deadlockinterval

"100"

Number of milliseconds between checking for database deadlocks that need to be broken. 

caldb.berkeleydb.

homedir.path

"."

Directory (relative to the location of the program executable files or an absolute path if specified) where database event, task, and alarm files are stored. The default is “.”, which specifies: 

/var/opt/SUNWics5/csdb

caldb.berkeleydb.

logfilesizemb

"10"

Maximum megabytes for a database checkpoint file. 

caldb.berkeleydb.

maxthreads

"10000"

Maximum number of threads that database environment must be prepared to accommodate. 

caldb.berkeleydb.

mempoolsizemb

"4"

Megabytes of shared memory for database environment. 

caldb.calmaster

" "

Email for user or alias that is responsible for administering the database. 

caldb.counters

"yes"

If "yes", data base statistics (reads, writes, deletes) will be counted.

caldb.counters.

maxinstances

"100"

Maximum number of calendars that can have counters. A calendar is enabled for counters using the cscal command line utility.

caldb.smtpmsgfmtdir

"en"

Specifies the directory under /etc/opt/SUNWics5/config that contains the localized version of the files used to format email notifications.

For example, "en" specifies the directory for the English localized version, and "fr" specifies the directory for the French localized version. 

caldb.smtpport

"25"

Port for SMTP host. 

local.caldb.deadlock.autodetect

"no"

Periodically checks if the Berkeley database is in a deadlock state and, if so, instructs the database to reset. 

E.2.20 Automatic Backups of the Calendar Database

The following table lists the parameters used by the automatic backup process (csstored), gives the default value where available, and describes the ics.conf parameter.

Table E–20 ics.conf Parameters Used by the Automatic Backup Process

Parameter  

Default Value  

Description  

logfile.store.logname

defaultstore.log

Name of the log file. 

logfile.logdir

"."

Path to the log directory. 

caldb.berkeleydb.homedir.

path

none 

Path to live database. 

caldb.berkeleydb.archive.

path

none 

Path to the archive backup. 

caldb.berkeleydb.hotbackup.

path

none 

Path to the hot backup. 

caldb.berkeleydb.archive.

enable

"yes"

Enable/disable automatic archive backups. 

caldb.berkeleydb.hotbackup.

enable

"yes"

Enable/disable automatic hot backups. 

caldb.berkeleydb.hotbackup.

mindays

"3"

Minimum number of hot backup copies kept on disk. 

caldb.berkeleydb.hotbackup.

threshold

"70"

Percentage of used disk space that triggers purging of old hot backup copies. 

caldb.berkeleydb.archive.

interval

"86400"

Interval in seconds between backups. Default is 24 hours, which is 86400 seconds. 

caldb.berkeleydb.archive.

mindays

"3"

Minimum number of archive backup copies kept on disk. 

caldb.berkeleydb.archive.

maxdays

"7"

Maximum number of archive backup copies kept on disk. 

caldb.berkeleydb.archive.

threshold

"70"

Percentage of used disk space that triggers purging of old archive backup copies. 

caldb.berkeleydb.

circularlogging

"yes"

Enables/disables management of the number of, and disk space occupied by, backup copies. 

caldb.berkeleydb.archive.

interval

"86400"

Time in seconds between backups. 

The default is 24 hours, or 86400 seconds. 

service.store.enable

(not included in ics.conf file)

"yes"

Enables csstored to be started by start-cal. Must be added to the ics.conf file, set to "no", if you want to disable csstored from being started by start-cal.

E.2.21 Calendar Database Parameters for ENS Messages

The following table describes the parameter, default value, and description for each of the parameters used to configure the calendar database. If you require a value other than the default, you must set it in the ics.conf file.

Table E–21 Calendar Database Parameters for ENS Messages

Parameter  

Default Value  

Description  

caldb.serveralarms.url

"enp:///ics/alarm"

Specifies the URL for the ENS message. 

caldb.serveralarms.

contenttype

""

Specifies the content type of the alarm data. Value can be "text/xml" or "text/calendar".

caldb.berkeleydb.ensmsg.

createcal

"no"

Creates an ENS message when a calendar is created. 

caldb.berkeleydb.ensmsg.

createcal.url

"enp:///ics/calendarcreate"

Specifies the URL for the ENS message. 

caldb.berkeleydb.ensmsg.

createcal.contenttype

"text/xml"

Specifies the content type of the message data: "text/xml" (default) or "text/calendar".

caldb.berkeleydb.ensmsg.

deletecal

"no"

Creates an ENS message when a calendar is deleted. 

caldb.berkeleydb.ensmsg.

deletecal.url

"enp:///ics/calendardelete"

Specifies the URL for the ENS message. 

caldb.berkeleydb.ensmsg.

deletecal.contenttype

"text/xml"

Specifies the content type of the message data: "text/xml" (default) or "text/calendar".

caldb.berkeleydb.ensmsg.

modifycal

"no"

Creates an ENS message when a calendar is modified. 

caldb.berkeleydb.ensmsg.

modifycal.url

"enp:///ics/calendarmodify"

URL for the ENS message. 

caldb.berleleydb.ensmsg.

modifycal.contenttype

"text/xml"

Specifies the content type of the message data: "text/xml" (default) or "text/calendar".

caldb.berkeleydb.ensmsg.

createevent

"no"

Creates an ENS message when an event is created. 

caldb.berkeleydb.ensmsg.

createevent.url

"enp:///ics/caleventcreate"

Specifies the URL for the ENS message. 

caldb.berleleydb.ensmsg.

createevent.contenttype

"text/xml"

Specifies the content type of the message data: "text/xml" (default) or "text/calendar".

caldb.berkeleydb.ensmsg.

modifyevent

"no"

Creates an ENS message when an event is modified. 

caldb.berkeleydb.ensmsg.

modifyevent.url

"enp:///ics/caleventmodify"

Specifies the URL for the ENS message. 

caldb.berleleydb.ensmsg.

modifyevent.contenttype

"text/xml"

Specifies the content type of the message data: "text/xml" (default) or "text/calendar".

caldb.berkeleydb.ensmsg.

deleteevent

"no"

Creates an ENS message when an event is deleted. 

caldb.berkeleydb.ensmsg.

deleteevent.url

"enp:///ics/caleventdelete"

Specifies the URL for the ENS message. 

caldb.berkeleydb.ensmsg.

deleteevent.contenttype

"text/xml"

Specifies the content type of the message data: "text/xml" (default) or"text/calendar".

caldb.berkeleydb.ensmsg.

createtodo

"no"

Creates an ENS message when a todo is created. 

caldb.berkeleydb.ensmsg.

createtodo.url

"enp:///ics/caltodocreate"

Specifies the URL for the ENS message. 

caldb.berleleydb.ensmsg.

createtodo.contenttype

"text/xml"

Specifies the content type of the message data: "text/xml" (default) or "text/calendar".

caldb.berkeleydb.ensmsg.

modifytodo

"no"

Creates an ENS message when a todo is modified. 

caldb.berkeleydb.ensmsg.

modifytodo.url

"enp:///ics/caltodomodify"

Specifies the URL for the ENS message. 

caldb.berleleydb.ensmsg.

modifytodo.contenttype

"text/xml"

Specifies the content type of the message data: "text/xml" (default) or "text/calendar".

caldb.berkeleydb.ensmsg.

deletetodo

"no"

Creates an ENS message when a todo is deleted. 

caldb.berkeleydb.ensmsg.

deletetodo.url

"enp:///ics/caltododelete"

Specifies the URL for the ENS message. 

caldb.berkeleydb.ensmsg.

deletetodo.contenttype

"text/xml"

Specifies the content type of the message data: "text/xml" (default) or "text/calendar".

E.2.22 Event Notification Server (ENS) Configuration

Calendar Server, when configured to do so, uses an external generic service called the Event Notification Server (ENS), which accepts reports of server-level events that can be categorized into specific areas of interest and notifies other servers that have registered interest in certain categories of events. Calendar Server uses ENS to send and receive alarm notifications that include the creation, deletion, or modification of calendar events and tasks as well as general operational warning and error messages.

The following table shows the Event Notification Server (ENS) configuration parameters in ics.conf. with each parameter’s default value and description.

Table E–22 Event Notification Server (ENS) Configuration Parameters in the ics.conf File

Parameter  

Default Value  

Description  

service.ens.enable

"yes"

If "yes", start the enpd service when starting all services and stop enpd when stopping all services.

service.ens.host

"localhost"

The host name of the machine on which ENS is running. 

service.ens.port

"57997"

The port number of the machine on which ENS is running. 

service.ens.library

"xenp"

The name of ENS plug-in. 

service.notify.enable

"yes"

If "yes", start the csnotifyd service when starting all services and stop csnotifyd when stopping all services.

service.notify.

maxretrytime

"-1"

How many times csnotifyd will consecutively retry and fail to contact ENS. 

A value of "-1" causes the alarm thread to retry indefinitely.

service.notify.

retryinterval

"3"

Number (in seconds) that csnotifyd waits before attempting to recontact ENS after a connection failure.

service.notify.

startupretrytime

"0"

Total number of seconds Calendar Server keeps trying to contact ENS before it stops. This setting is similar to caldb.serveralarms.maxretrytime except that it applies only when the alarm thread is first starting. Once the alarm thread has successfully started, caldb.serveralarms.maxretrytime is used.

A value of "0" tells the alarm thread to exit immediately if it fails to connect to ENS at startup.

ens.startlistener

"0"

Acceptable values: 

  • "1"

  • "0"

caldb.berkeleydb.

alarmretrytime

"300"

Retry time in seconds after a recoverable alarm delivery error. 

caldb.berkeleydb.ensmsg.

createcal

"no"

If "yes", create an Event Notification Service message when a calendar is created using the following format: 

enp://ics/createcal?calid=cal

caldb.berkeleydb.ensmsg.

modifycal

"no"

If "yes", create an Event Notification Service message when a calendar is modified using the following format:

enp://ics/modifycal?calid=cal

caldb.berkeleydb.ensmsg.

deletecal

"no"

If "yes", create an Event Notification Service message when a calendar is deleted using the following format:

enp://ics/deletecal?calid=cal

caldb.berkeleydb.ensmsg.

advancedtopics

"no"

Specifies how modify event notifications are published: 

  • If "yes", the system differentiates between reply, refresh, or modify transactions by publishing to the respective topic:

    caldb.berkeleydb.ensmsg.replyevent

    caldb.berkeleydb.ensmsg.refreshevent

    caldb.berkeleydb.ensmsg.modifyevent

  • If "no", the system publishes all three types (reply, refresh, modify) to the following topic:

    caldb.berkeleydb.ensmsg.modifyevent

caldb.berkeleydb.ensmsg.

createevent

"no"

If "yes", create an ENS message when an event is created.

caldb.berkeleydb.ensmsg.

deleteevent

"no"

If "yes", create an ENS message when an event is deleted.

caldb.berkeleydb.ensmsg.

modifyevent

"no"

If "yes", create an ENS message when an event is modified.

caldb.berkeleydb.ensmsg.

refreshevent

"no"

Specifies whether Calendar Server should create an ENS message when an event is refreshed. 

caldb.berkeleydb.ensmsg.

refreshevent.contenttype

"text/xml"

Specifies the content type of the message data for the refresh of an event. Values can be "text/xml" or "text/calendar".

caldb.berkeleydb.ensmsg.

refreshevent.url

"enp:///ics/caleventrefresh"

Specifies the URL for ENS message for the refresh of an event. 

caldb.berkeleydb.ensmsg.

replyevent

"no"

Specifies whether Calendar Server should create an ENS message for a reply to an event. 

caldb.berkeleydb.ensmsg.

replyevent.contenttype

"text/xml"

Specifies the content type of the message data for a reply to an event. Values can be "text/xml" or "text/calendar".

caldb.berkeleydb.ensmsg.

replyevent.url

"enp:///ics
/caleventreply"

Specifies the URL for the ENS message for a reply to an event. 

caldb.berkeleydb.ensmsg.

createtodo

"no"

If "yes", create an Event Notification Service message when a todo (task) is created using the following format:

enp://ics/createtodo?
uid=uid&rid=rid

caldb.berkeleydb.ensmsg.

modifytodo

"no"

If "yes", create an Event Notification Service message when a task is modified using the following format: 

enp://ics/modifytodo?
uid=uid&rid=rid

caldb.berkeleydb.ensmsg.

deletetodo

"no"

If "yes", create an Event Notification Service message when a task is deleted using the following format:

enp://ics/deletetodo?uid=uid&rid=rid

caldb.berkeleydb.ensmsg.

qsize

"10000"

Initial size of the in-memory ENS message queue. This queue stores all ENS messages other than alarm reminders. 

caldb.berkeleydb.ensmsg.

schedreq

"no"

If "yes", create an Event Notification Service message when a scheduling request is written to the calendar is deleted using the following format:

enp://ics/schedreq?calid=cal
&method=method&type={event|todo}
&uid=uid&rid=rid

caldb.serveralarms

"yes"

If "yes", alarm emails will be sent. 

caldb.serveralarms.

acktimeout

"30"

Specifies the number of seconds ENS’s alarm thread waits for an acknowledgment from csnotifyd after publishing an alarm notification. If the timeout expires, the alarm thread assumes the alarm notification is no longer processing and publishes the alarm notification again. 

caldb.serveralarms.

dispatchtype

"ens"

Specifies the dispatch type for Calendar Server alarms: 

  • If "ens", the server uses the external ENS to send and receive alarms.

  • If "smtp", the server sends alarms as standard SMTP messages and to bypass ENS.

caldb.serveralarms.

initthreads

"10"

Initial number of server alarm threads. 

caldb.serveralarms.

maxretrytime

"-1"

How many times the alarm thread will consecutively retry and fail to contact ENS. 

"-1" causes the alarm thread to retry indefinitely.

caldb.serveralarms.

maxthreads

"10"

Maximum number of server alarm threads. 

caldb.serveralarms.

retryinterval

"5"

Number (in seconds) that the alarm thread (in csadmind) waits before attempting to recontact ENS. 

caldb.serveralarms.

stacksize

"65536"

Stack frame size for server alarm threads. 

caldb.serveralarms.startup

retrytime

"0"

Total number of seconds Calendar Server keeps trying to contact ENS before failing. This setting is similar to the setting caldb.serveralarms.maxretrytime except that it applies only when the alarm thread is first starting. Once the alarm thread has started successfully, caldb.serveralarms.maxretrytime is used. 

If "0", the alarm thread exits immediately if it fails to connect to ENS at startup.

caldb.smtphost

"localhost"

Send alarm emails to this SMTP host. 

E.2.23 Calendar Server API Configuration

The following table shows the Calendar Server API (CSAPI) configuration parameters with each parameter’s default value and description.

Table E–23 CSAPI Configuration Parameters in the ics.conf File

Parameter  

Default Value  

Description  

csapi.plugin.authentication

"no"

If the value is "yes", load only the plug-in specified in csapi.plugin.authentication.name.

csapi.plugin.accesscontrol

"no"

Enable ("yes") or disable ("no") Access Control plug-in.

csapi.plugin.authentication

"no"

If the value is "yes", load only the plug-in specified in csapi.plugin.authentication.name.

If the value is "no", or if not specified, load all authentication class plug-ins in alphabetical order. For authentication, use each of these plug-ins in alphabetical order.

csapi.plugin.authentication.

name

" "

If csapi.plugin.loadall is "no" and csapi.plugin.authentication is "yes", only load this specific plug-in. If not specified or blank (" "), load all authentication class plug-ins.

csapi.plugin.database

"yes"

If "yes", load only the plug-in specified in csapi.plugin.database.name.

If "no", or if not specified, load all database plug-ins in alphabetical order.

csapi.plugin.database.name

"cs_caldb
_berkeley"

If csapi.plugin.loadall is "no" and csapi.plugin.database is "yes", load only this plug-in. If not specified or blank (" "), load all database plug-ins in alphabetical order.

csapi.plugin.datatranslator

"yes"

If "yes", load only the plug-in specified in csapi.plugin.datatranslator.name or if not specified, load all data translator class plug-ins in alphabetical order. For data translation, use each of these plug-ins in alphabetical order.

csapi.plugin.datatranslator.

name

"cs_data
translatorcsv"

If csapi.plugin.loadall is "no" and csapi.plugin.datatranslator is "yes", load this specific plug-in.

If blank (" "), or not specified, load all data translator class plug-ins.

csapi.plugin.dbtranslator

"yes"

Enable ("yes") or disable ("no") database-to-output format plug-ins.

csapi.plugin.dbtranslator.name

"*"

If csapi.plugin.dbtranslator is "yes", then either:

  • If "*", load all the database-to-output format plug-ins.

  • If this value is a library name, load only this specific plug-in.

 

If csapi.plugin.dbtranslator is "no", this setting is ignored.

csapi.plugin.loadall

"no"

If "yes", load all plug-ins found in the plug-ins directory. (Plug-ins have an .so extension.)

If "no", only load the specific class of plug-ins flagged by their respective parameters. For example, set csapi.plugin.authentication to "yes" to load authentication class plug-ins.

csapi.plugin.userprefs

"no"

If "yes", load only the plug-in specified in csapi.plugin.userprefs.name or if not specified, load all user preferences class plug-ins in alphabetical order. For user preferences, use each of these plug-ins in alphabetical order.

csapi.plugin.userprefs.

name

" "

If csapi.plugin.loadall is "no" and csapi.plugin.userprefs is "yes", this parameter is used. If not specified or blank (" "), load all user preferences class plug-ins. Otherwise, only load this specific plug-in.

E.3 Counters Configuration (counter.conf) File

Calendar Server counters (statistics) configuration parameters are in the following file:

/etc/opt/SUNWics5/config/counter.conf

The counter.conf file is an ASCII text file, with each line defining a counter and its parameters: name, type, size (in bytes), and description. A parameter with spaces must be enclosed in double quotation marks (" "). A comment line must begin with an exclamation point (!). Comment lines are for informational purposes only.

The first part of a counter's name identifies the counter object used with the csstats utility. For more information about the command-line utilities, see Appendix D, Calendar Server Command-Line Utilities Reference.


Note –

Do not modify the counter.conf file unless instructed to do so by customer support staff.


This section describes the Calendar Server counter.conf parameters, including:

E.3.1 Alarm Counters

The following table shows each alarm counter’s name, type, size, and description.

Table E–24 Alarm Counters in the counter.conf File

Name  

Type 

Size  

Description 

alarm.high

GAUGE 

Highest ever recorded value. 

alarm.low

GAUGE 

Lowest ever recorded value. 

alarm.current

GAUGE 

Current monitored valued. 

alarm.warningstate

GAUGE 

Warning state: yes (1) or no (0). 

alarm.countoverthreshold

COUNTER 

Number of times crossing threshold. 

alarm.countwarningsent

COUNTER 

Number of warnings sent. 

alarm.timelastset.desc

TIME 

Last time current value was set. 

alarm.timelastwarning

TIME 

Last time warning was sent. 

alarm.timereset

TIME 

Last time reset was performed. 

alarm.timestatechanged.desc

TIME 

Last time alarm state changed. 

E.3.2 Disk Usage Counters

The following table shows each disk usage counter’s name, type, size, and description.

Table E–25 Disk Usage Counters in the counter.conf File

Name  

Type 

Size  

Description  

diskusage.availSpace

GAUGE 

Total space available in the disk partition. 

diskusage.lastStatTime

TIME 

The last time statistic was taken. 

diskusage.calPartitionPath

STRING 

512 

Calendar partition path. 

diskusage.percentAvail

GAUGE 

Disk partition space available percentage. 

diskusage.totalSpace

GAUGE 

Total space in the disk partition. 

E.3.3 HTTP Counters

The following table shows each HTTP counter’s name, type, size, and description.

Table E–26 HTTP (httpstat) Counters in the counter.conf File

Name  

Type  

Size  

Description  

httpstat.avgConnectionTime

GAUGE 

Average connection response time. 

httpstat.currentStartTime

TIME 

When Calendar Server was started. 

httpstat.lastConnectionTime

TIME 

Last time new client connection was accepted. 

httpstat.maxConnections

COUNTER 

Maximum number of concurrent connections served. 

httpstat.maxSessions

COUNTER 

Maximum number of WCAP sessions served. 

httpstat.numConnections

COUNTER 

Total number of connections served. 

httpstat.numCurrentConnections

GAUGE 

Current number of active connections. 

httpstat.numCurrentSessions

GAUGE 

Current number of WCAP sessions. 

httpstat.numFailedConnections

COUNTER 

Total number of failed connections served. 

httpstat.numGoodLogins.desc

COUNTER 

Number of successful logins served by the current HTTP server. 

httpstat.numFailedLogins

COUNTER 

Number of failed logins served by the current HTTP server. 

E.3.4 Group Scheduling Counters

The following table shows each Group Scheduling Engine (GSE) counter’s name, type, size, and description.

Table E–27 Group Scheduling Engine (GSE) Counters in the counter.conf File

Name 

Type  

Size 

Description  

gsestat.lastWakeUpTime

TIME 

Last time GSE wakes up and process job. 

gsestat.lastJobProcessedTime

TIME 

Last time GSE processes a job. 

gsestat.numJobsProcessed

COUNTER 

Total number of jobs GSE processed. 

gsestat.numActiveWorkerThreads

COUNTER 

Total number of active Worker Threads. 

E.3.5 Authentication Counters

The following table shows each Authentication counter’s name, type, size, and description.

Table E–28 Authentication (authstat) Counters in the counter.conf File

Name  

Type  

Size 

Description  

authstat.lastLoginTime

TIME 

Last time a user logged in. 

authstat.numSuccessfulLogins

COUNTER 

Total number of successful logins served. 

authstat.numFailedLogins

COUNTER 

Total number of failed logins served. 

E.3.6 WCAP Counters

The following table shows each WCAP counter’s name, type, size, and description.

Table E–29 WCAP (wcapstat) Counters in the counter.conf File

Name  

Type  

Size 

Description  

wcapstat.numRequests

COUNTER 

Total number of WCAP requests. 

E.3.7 Database Counters

The following table shows each Database counter’s name, type, size, and description.

Table E–30 Database (dbstat) Counters in the counter.conf File

Name  

Type  

Size  

Description 

dbstat.numReads

COUNTER 

Total number of database reads. 

dbstat.numWrites

COUNTER 

Total number of database writes. 

dbstat.numDeletes

COUNTER 

Total number of database deletes. 

dbstat.lastReadTime

TIME 

Last time of database read. 

dbstat.lastWriteTime

TIME 

Last time of database write. 

dbstat.lastDeleteTime

TIME 

Last time of database delete. 

E.3.8 Server Response Counters

The following table shows each Server Response counter’s name, type, size, and description.

Table E–31 Server Response Counters in the counter.conf File

Name  

Type  

Size  

Scale 

Description 

serverresponse.lastStatTime

TIME 

 

Last time statistic was taken. 

serverresponse.responseTime

GAUGE 

Server response time in milliseconds. 

E.3.9 Session Status Counters

The following table shows each Session Status counter’s name, type, size, and description.

Table E–32 Sessions Status Counters in the counter.conf File

Name  

Type  

Size  

Scale  

Description 

sessstat.maxSessions.desc

COUNTER 

Maximum number of HTTP sessions served. 

sessstat.numCurrentSessions

GAUGE 

Current number of HTTP sessions. 

E.4 Calendar Server Email Notifications

Calendar Server sends the types of email messages described in E.4.1 Calendar Server Email Notifications Configuration Parameters and Format Files. The format of these messages is controlled by the associated format (.fmt) file listed in the table. Format files are located in specific directories for each locale (such as /en for English and /fr for French) in the following directory:

/etc/opt/SUNWics5/config

For example, the English version of the task (todo) alarm message format is specified in the file:

/etc/opt/SUNWics5/config/en/mail_todoalarm.fmt

This section describes:

E.4.1 Calendar Server Email Notifications Configuration Parameters and Format Files

The following table shows the message type, ics.conf parameter name, default format file description, and recipient for each Calendar Server Mail parameter.

Table E–33 Calendar Server Email Formats in the ics.conf File

Message Type  

Parameter 

Format File (default)  

Description 

Recipients  

Event Publish 

calmail.imipeventpublish.

fname

"mail_eventpublish.fmt"

Announces an event or a change to an existing event 

Those listed in Notification 

Event Cancel 

calmail.imipeventcancel.

fname

"mail_eventcancel.fmt"

Announces an event cancellation 

Those listed in Notification 

Reply to Event 

calmail.imipeventreply.

fname

"mail_eventreply.fmt"

Replies to an event notification. 

Those listed in Notification 

Request Event 

calmail.imipeventrequest.

fname

"mail_eventrequest.fmt"

Subscribes to an event notification. 

Those listed in Notification 

Event Alarm 

calmail.eventreminder.

fname

"mail_eventreminder.fmt"

Reminder for an upcoming event 

Those listed in Reminder 

Recurring Event Notification 

calmail.imipevent

notificationrecur.fname

"mail_event

notificationrecur.fmt"

Notifies of a recurring event 

Those listed in Notification 

Event Cancel Notification 

calmail.imipeventcancel

notification.fname

"mail_eventcancel

notification.fmt"

Notifies of a cancelled event 

Those listed in Notification 

Recurring Event Cancel Notification 

calmail.imipeventcancel

notificationrecur.fname

"mail_eventcancel

notificationrecur.fmt"

Notifies of a cancelled recurring event 

Those listed in Notification 

Attendee Reply: Accept Notification 

calmail.imipeventaccept

notification.fname

"mail_eventaccept

notification.fmt"

Notifies the event organizer that an attendee accepted the invitation. 

Event Organizer 

Attendee Reply: Decline Notification 

calmail.imipeventdecline

notification.fname

"mail_eventdecline

notification.fmt"

Notifies the event organizer that an attendee declined the invitation. 

Event Organizer 

Attendee Reply: Tentative Accept Notification 

calmail.imipeventtentative

acceptnotification.fname

"mail_eventtentative

acceptnotification.fmt"

Notifies the event organizer that an attendee has tentatively accepted the invitation. 

Event Organizer 

Attendee Reply: Accept Notification for Recurring Event 

calmail.imipeventaccept

notificationrecur.fname

"mail_eventaccept

notificationrecur.fmt"

Notifies the event organizer that an attendee has accepted an invitation to a recurring event. 

Event Organizer 

Attendee Reply: Decline Notification for Recurring Event 

calmail.imipeventdecline

notificationrecur.fname

"mail_eventdecline

notificationrecur.fmt"

Notifies the event organizer that an attendee declined an invitation to a recurring event. 

Event Organizer 

Attendee Reply: Tentative Accept Notification for a Recurring Event 

calmail.imipevent

tentativeaccept

notificationrecur.fname

"mail_eventtentative

acceptnotificationrecur.fmt"

Notifies the event organizer that an attendee tentatively accepted an invitation to a recurring event. 

Event Organizer 

Task Publish 

calmail.imiptodopublish.

fname

"mail_todopublish.fmt"

Announces a task or a change to an existing task 

Those listed in Notification 

Task Cancel 

calmail.imiptodocancel.fname

"mail_todocancel.fmt"

Announces a task cancellation 

Those listed in Notification 

Reply to Task 

calmail.imiptodoreply.

fname

"mail_todoreply.fmt"

Replies to a task notification 

Those listed in Notification 

Todo Request 

calmail.imiptodorequest.

fname

"mail_todorequest.fmt"

Subscribes to a todo notification. 

Those listed in Notification 

Task Alarm 

calmail.todoreminder.

fname

"mail_todoreminder.fmt"

Reminder for an upcoming task 

Those listed in Reminder 

Calendar Server generates notification messages by combining a particular event or task with the contents of a format file. The values of data fields within an event or task can be output to the message. The notification message can also include MIME header lines and associated special values. Using special character sequences (format notations), you can include the values of events, tasks, and MIME headers in the message. The lines in the format file are format strings comprised of special character sequences that are replaced with actual values from calendar data fields when the mail message is generated. Special character sequences consist of two characters, the first is the percent sign (%) and the second represents the specific format notation.

The following sections describe special character sequences:

E.4.2 Calendar Server Special Character Sequences for Event Notifications

The following table shows the format code and meaning for special character sequences used in event notifications.

Table E–34 Special Character Sequences for Event Notifications

Format Code  

Meaning  

%0

Start time in localized format 

%1

End time in localized format 

%A

exdates in iCalendar format (semicolon-separated list of ISO 8601 date strings listing dates to exclude)

%a

rdates in iCalendar format (semicolon-separated list of ISO 8601 date strings listing recurrence dates)

%B

Start time (also see %Z)

%b

Output the start time and end time in iCalendar format. If the start time parameter has a value equal to the date, only the month/day/year portion of the date is output. If the end time has the same month/day/year value as the start time, only the start time is generated. 

%C

Create time 

%c

Event class 

%d

Event description. (also see %F)

%E

End time (also see %Z)

%e

Exception rules in iCalendar format 

%F

Event description - folded line, iCalendar format (also see %d)

%G

The event's geographic location (latitude and longitude) 

%g

Organizer's email address. (There is no guarantee as to the authenticity of this value.) 

%K

Organizer email in the form of a mailto:url

%k

Alarm count 

%L

Location 

%l

Recurrence rules in iCalendar format 

%M

Modify time 

%N

New line 

%n

The current time stamp used with DTSTAMP

%P

Priority 

%r

Recurrence id (blank if this event does not recur) 

%S

Event sequence number 

%s

Summary 

%t

Event status 

%U

Unique Event Identifier 

%Z

Used in conjunction with the time field code to force the time to be rendered in UTC. (%B displays the start time in local time whereas %ZB displays the start time in UTC time.)

%%

Displays the percent (%) character

%

Specifies a sub-format for the data identified by code. (For details, see E.4.3 Calendar Server Notifications Date Sub-Format Strings.)

E.4.3 Calendar Server Notifications Date Sub-Format Strings

Date-time values can be formatted in many different ways. Using a sub-format, you can provide additional information to describe how a date-time value should be formatted. If a sub-format is not specified, the server uses a default format to output the date. Using a sub-format field allows you to specify the exact format to be used.

For example, %B specifies that the output string includes the event's begin time. This default format prints out the date, time, the time zone, and everything possible about the date. The sub-format string for date values is a strftime format string (see E.4.6 Special Character Sequences for Dates). If you were only interested in the month and year of the start time, instead of %B, you would use: %(%m %Y)B.

E.4.3.1 Example

The following example:


The event begins: %B%N
 The event ends: %(%b %d, %Y %I:%M %p)E%N

produces output that resembles the following notification:


The event begins Feb 02, 1999 23:30:00 GMT Standard Time
 The event ends Feb 03, 1999 02:30 AM

E.4.4 Calendar Server Notifications Conditional Printing Format

Sometimes it is desirable to print a line only under certain conditions. For example, the following lines:


title: %S%N
 start: %B%N
 end: %E%N  

produce output that resembles the following notification:


title: Staff Meeting
 start: Feb 04, 1999 09:00:00
 end: Feb 04, 1999 10:00:00 

There are two conditions, however, where the above example would yield misleading or incorrect results:

In these situations, it is best not to print the end time at all. By default, only the year, month, and day are printed when a time stamp has the attribute of being all-day. Furthermore, if an event start time has the all-day attribute and the event ends on the same day as it starts, a special conditional flag is set. Use the ? modifier to print conditional values only when the special conditional flag is not set.

For example, if you change the lines in the above example to:


title: %S%N
 start: %B%N
 end: %?E%N 

The last line will not be printed for all-day events for which the start day and end day are the same. It produces the following output for typical all-day events (such as birthdays or anniversaries):


title: Staff Meeting
 start: Feb 04, 1999

The ? flag can be combined with other modifiers. For example:

The event ends: %?(%b %d, %Y %I:%M %p)E%N

E.4.5 Special Character Sequences for Task Notifications

The following table shows the format code and meaning for Special Character Sequences for Task Notifications.

Table E–35 Special Character Sequences for Task Notifications

Format Code  

Meaning  

%A

exdates in iCalendar format (semicolon-separated list of ISO 8601 date strings listing dates to exclude)

%a

rdates in iCalendar format (semicolon-separated list of ISO 8601 date strings listing recurrence dates)

%B

start time (also see %Z)

%C

create time 

%c

task class 

%D

due date and time. 

%d

task description. (also see %F)

%E

due date and time in IMIP format 

%e

exception rules in iCalendar format 

%F

task description - folded line, iCalendar format (also see %d)

%G

this task's geographic location, the latitude and longitude. 

%g

organizer's email address (cannot guarantee the authenticity of this value) 

%K

organizer’s email in the form of a mailto:URL

%k

alarm count 

%L

the location 

%l

recurrence rules in iCalendar format 

%M

modify time 

%N

a new line 

%n

"now" (the current time stamp and used with DTSTAMP)

%P

priority 

%r

the recurrence ID (blank if this task does not recur) 

%S

is the task’s Sequence Number 

%s

summary 

%t

the status 

%U

the UID

%Z

used in conjunction with time field code to force the time to be rendered in UTC (%B displays the start time in local time whereas %ZB displays the start time in UTC time)

%%

displays the % character

% (sub-format code)

specify a sub-format for the data identified by code (for details, see E.4.3 Calendar Server Notifications Date Sub-Format Strings)

E.4.6 Special Character Sequences for Dates

The following table shows the format code and meaning for Special Character Sequences for dates.


Note –

The special date format codes appear in this section only for convenience. Calendar Server does not rewrite any of the codes, but simply uses the operating system implementation.


Table E–36 Special Character Sequences for Dates

Format Code  

Meaning 

%a

Abbreviated weekday name 

%A

Full weekday name 

%b

Abbreviated month name 

%B

Full month name 

%c

Date and time representation appropriate for locale 

%d

Day of month as decimal number (01 - 31)

%H

Hour in 24 hour format (00 - 23)

%I

Hour in 12 hour format (01 - 12)

%j

Day of year as decimal number (001 - 366)

%m

Month as decimal number (01 - 12)

%M

Minute as decimal number (00 - 59)

%p

Current locale's A.M./P.M. indicator for 12 hour clock 

%S

Second as decimal number (00 - 59)

%U

Week of year as decimal number, with Sunday as first day of week (00 - 53)

%w

Weekday as decimal number (0 - 6; Sunday is 0)

%W

Week of year as decimal number, with Monday as first day of week (00 - 53)

%x

Date representation for current locale 

%X

Time representation for current locale 

%y

Year without century, as decimal number (00 - 99)

%Y

Year with century, as decimal number 

%Z

Time-zone name or abbreviation; no characters if time zone is unknown 

%%

Percent sign 

E.4.7 Simple Event Reminder Example

The following example shows the default event reminder message format:


1  EVENT REMINDER
 2  ~~MIME-Version: 1.0%N
 3  ~~Content-Type: text/plain; charset=%s%N
 4  ~~Content-Transfer-Encoding: %x%N%N
 5      Summary: %s%N
 6        Start: %(%a, %d %b %Y %I:%M %p)B%N
 7        End: (%a, %d %b %Y %I:%M %p)E%N
 8      Location: %L%N%N
 9  Description: %N%d%N

         

The description of each line in this example is:

The following sample resembles the notification message generated by the above example:


From: jsmith@sesta.com (James Smith)
 Date: Wed, 15 Nov 1999 19:13:49
 To: jsmith@sesta.com
 Subject: EVENT REMINDER
 MIME-Version: 1.0
 Content-Type: text/plain; charset=us-ascii
 Content-Transfer-Encoding: 7bit
   Summary: smtp_rig event 1
       Start: Tues, 16 Nov 1999 02:00 PM
       End: Tues, 16 Nov 1999 03:00 PM
   Location: Green Conference Room
   Description: This is the description for a randomly generated event.

E.4.8 Complex Event Reminder Example

The following example shows a more complex multipart message. This example has a text part and an IMIP PUBLISH part.


EVENT PUBLICATION
 ~~MIME-Version: 1.0%N
 ~~Content-Type: multipart/mixed; boundary="%b"%N%N
 This is a multi-part message in MIME format.%N
 ~~--%b%N
 ~~Content-Type: text/plain; charset=%s%N
 ~~Content-Transfer-Encoding: %x%N%N
     Summary: %s%N
       Start: %(%a, %d %b %Y %I:%M %p)B%N
       End: %(%a, %d %b %Y %I:%M %p)E%N
     Location: %L%N%N
    Description: %N%d%N%N
 ~~--%b%N
 ~~Content-Type: text/calendar; method=%m; component=%c; charset=%s%N
 ~~Content-Transfer-Encoding: %x%N%N
 BEGIN:VCALENDAR%N
PRODID:-//iPlanet/Calendar Hosting Server//EN%N
 METHOD:PUBLISH%N
 VERSION:2.0%N
 BEGIN:VEVENT%N
 ORGANIZER:%K%N
 DTSTAMP:%Zn%N
 DTSTART:%ZB%N
 DTEND:%ZE%N
 SUMMARY:%s%N
UID:%U%N
 %R
 %A
 %a
 %e
 %l
 SEQUENCE:%S%N
 LOCATION:%L%N
 GEO:%G%N
 %F
 STATUS:%t%N
 END:VEVENT%N
 END:VCALENDAR%N
 ~~--%b--