Configuration parameters in the ics.conf file include:
The following table shows the Local configuration parameters with each parameter’s default value and description.
Table E–1 Local Configuration Parameters in the ics.conf File
The following table shows the Calendar Store Configuration parameters with each parameter’s default value and description.
Table E–2 Calendar Store Configuration Parameters in the ics.conf File
Parameter |
Default Value |
Description |
---|---|---|
"anonymous" |
Calendar ID (calid) used for anonymous logins. |
|
"yes" |
Determines if a user calendar can have more than one event scheduled for the same time slot when the calendar is created:
|
|
"@@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 Calendar Access Control To specify Access Control Entries for one or more calendars using the command-line utilities, see cscal. |
|
"@@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. |
"America/ New_York" |
Time zone ID to be used when:
|
|
"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. |
|
defaultcalendar |
"yes" |
Specifies whether a user's default calendar is included in user's free/busy calendar list. |
defaultcalendar |
"no" |
Specifies whether a user's default calendar can be removed from user's free/busy calendar list. |
"0" |
Maximum number of attendees allowed in an LDAP group when expanding an event. Value of "0" means to expand the group entirely. |
|
"60" |
Maximum number of events that can be created by a recurrence expansion. |
|
defaultcalendar |
"yes" |
Specifies whether a user's default calendar is included in the user's subscribed calendar list. |
defaultcalendar |
"no" |
Specifies whether a user's default calendar can be removed from the user's subscribed calendar list. |
"200" |
Maximum number of results returned from LDAP lookup from user search. Value of "0" means no limit. |
|
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. |
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. |
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. |
"." |
Location of primary disk partition where calendar information is stored. |
The following table shows the calendar log configuration parameters with each parameter’s default value and description.
Table E–3 Calendar Log Configuration Parameters in the ics.conf File
Parameter |
Default Value |
Description |
---|---|---|
"admin.log" |
Name of log file for logging administrative tools. |
|
"0" |
Size of log buffers (in bytes). |
|
"dwp.log" |
Name of log file for logging Database Wire Protocol related administrative tools. |
|
"604800" |
Number of seconds before log files expire. |
|
"60" |
Number of seconds between flushing buffers to log files. |
|
"http.log" |
Name of current log file for the cshttpd service. |
|
"httpd.access" |
Name of current HTTP access log file. |
|
"logs" |
Directory location of log files. |
|
"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. |
|
"10" |
Maximum number of log files in log directory. |
|
"2097152" |
Maximum size of each log file (in bytes). |
|
"20971520" |
Maximum disk space for all log files (in bytes). |
|
"5242880" |
Minimum free disk space (in bytes) that must be available for logging. |
|
"notify.log" |
Name of log file for the csnotifyd service. |
|
"86400" |
Number of seconds before log files are rotated. |
The following table lists the ics.conf parameters that pertain to administrators.
Table E–4 Configuration Parameters for Administrators
The following table shows the various services configuration parameters with each parameter’s default value and description.
Table E–5 Services Configuration Parameters in the ics.conf File
Parameter |
Default Value |
Description |
---|---|---|
"yes" |
Enable ("yes") or disable ("no") alarm notifications for administration tools. |
|
"yes" |
If "yes", start the csadmind database checkpoint thread. |
|
"8388608" |
Maximum cache size (in bytes) for Berkeley Database for administration sessions. |
|
"yes" |
If "yes", start the csadmind database deadlock detection thread. |
|
"no" |
If "yes", start the csadmind low disk space monitor thread. |
|
"yes" |
If "yes", start the csadmind service when starting all services and stop csadmind when stopping all services. |
|
"120" |
Number of seconds before timing out an HTTP connection in csadmind. |
|
"100" |
Maximum number of administration sessions allowed. |
|
"10" |
Maximum number of running threads per administration session. |
|
N/A |
Maximum number of a concurrent administration processes allowed. |
|
service.admin.port **CAUTION** |
N/A |
Set by the system. Do not change. |
"900" |
Number of seconds before timing out an administration connection. |
|
"no" |
If "yes", start the csadmind service response thread. |
|
" " |
Temporary directory for administration session requests. |
|
"1800" |
Number of seconds before timing out an HTTP session in csadmind. |
|
"2" |
Number of seconds to wait between checking for started, stopped, or ready calendar service. |
|
"300" |
Number of seconds to wait for any calendar service to start. |
|
"300" |
Number of seconds to wait for any calendar service to stop. |
|
"60" |
Number of seconds to wait between sending stop commands to any calendar service. |
|
"o=internet" |
Root suffix of the DC tree in the directory. |
|
"no" |
If "yes", client IP addresses are checked against DNS if allowed HTTP access. |
|
"0" |
Number of seconds to delay after successfully authenticating a user using plain text passwords. |
|
"calmaster" |
Space separated list of user ID's with administration rights to this Calendar Server. |
|
"no" |
If "yes", allow login via proxy. |
|
"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). |
|
"" (Null) |
HTTP host for retrieving HTML documents. |
|
"yes" |
Tells the server to whether or to support cookies (yes/no). It must be set to "yes" to enable single sign-on. |
|
"8388608" |
Maximum cache size of Berkeley DB for HTTP sessions. |
|
"" (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). |
|
"" (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). |
|
"." |
Directory location relative to local.queuedir (or an absolute path if specified) where imported files are temporarily stored. |
|
"yes" |
If "yes", all requests that reference an existing session are verified as originating from the same IP address. |
|
"yes" |
If "yes", start the cshttpd service when starting all services and stop cshttpd when stopping all services. |
|
"120" |
Number of seconds before timing out an HTTP connection. |
|
"yes" |
If "yes", LDAP connections for authentication and user preferences are created and maintained. |
|
"INADDR_ANY" |
Specifies the TCP address that HTTP services will listen on for client requests. "INADDR_ANY" indicates any address. |
|
"no" |
If "yes", HTTP connections to server are fully logged. |
|
"5000" |
Maximum number of HTTP sessions in cshttpd service. |
|
"20" |
Maximum number of threads to service HTTP requests in cshttpd service. |
|
"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 Using Load Balancing Across Multiple CPU's |
|
"80" |
Port for HTTP requests from Calendar Server users. |
|
"" |
If specified and not "", filter for allowing proxy login based on TCP domains. Same syntax as service.http.domainallowed. |
|
"900" |
Number of seconds before timing out an HTTP session. |
|
"http" |
Temporary directory for HTTP sessions. |
|
"1800" |
Number of seconds before timing out an HTTP session in cshttpd service. |
|
" " |
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" |
|
"html" |
Directory that contains the default calendar client. If allowing only WCAP access, set to "". |
|
"no" |
If "yes", use cache in LDAP SDK. |
|
"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. |
|
"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. |
|
.allowpubliccalendarwrite |
"yes" |
If "yes", allow anonymous users to write to publicly writable calendars. |
"text/calendar" |
Specifies the default output format for commands currently applied only for freebusy. |
|
"30" |
Specifies the default offset from the current time in days for get_freebusy for beginning of the range. |
|
"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. |
"yes" |
If "yes", allow calendars to be created. |
|
"yes" |
If "yes", allow calendars to be deleted. |
|
"no" |
If "yes", allow users to change their passwords via this server. |
|
allowpublicwritablecalendars |
"yes" |
If "yes", allow users to have publicly writable calendars. |
"no" |
If "yes", allow the set_userprefs.wcap attribute to modify the user preference "cn" (LDAP user's common name). |
|
"no" |
If "yes", allow the set_userprefs.wcap attribute to modify the user preference "givenname" (LDAP user's given name). |
|
"no" |
If "yes", allow the set_userprefs.wcap attribute to modify the user preference “icsCalendar" (a user's default calendar identifier). |
|
"no" |
If "yes", allow the set_userprefs.wcap attribute to modify the user preference "mail" (user's email address). |
|
.preferredlanguage |
"no" |
If "yes", allow the set_userprefs.wcap attribute to modify the user preference "preferredlanguage" (LDAP user's preferred language). |
"no" |
If "yes", allow the set_userprefs.wcap attribute to modify the user preference "sn" (LDAP user's surname). |
|
"no" |
If "yes", allow the set_userprefs.wcap attribute to modify the user preference "nswccalid", which is the user's default calendar ID. |
|
"no" |
If "yes", default user calendars are initially set to public read/private write. If no, default user calendars are initially set to private read/private write. |
|
"no" |
If "yes", enables LDAP proxy authorization for get_userprefs.wcap command. If "no", anonymous LDAP search is performed. |
|
"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). |
|
"3.0" |
WCAP version. |
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:
service.http.ssl.usessl = “yes”
service.http.ssl.port.enable = “yes”
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–6 Configuration Parameters for SSL
The following table shows the hosted (virtual) domain configuration parameters with each parameter’s default value and description.
Table E–7 Configuration Parameters for Hosted Domain Support
The following table shows the alarm notification server configuration parameters with each parameter’s default value and description.
Table E–8 Alarm Notification Configuration Parameters in the ics.conf File
The following table shows the Calendar Lookup Database (CLD) parameters with each parameter’s default value and description.
Table E–9 Calendar Lookup Database (CLD) Parameters in the ics.conf File
Parameter |
Default Value |
Description |
---|---|---|
"n" |
Enable ("y") or disable ("n") calendar lookup plug-ins. |
|
"*" |
Specifies the name of a specific calendar lookup plug-in to load. If this value is an asterisk ("*"), Calendar Server loads all plug-ins. |
|
"local" |
Specifies the type of CLD plug-in to use: "local" specifies that all calendars are stored on the local server where Calendar Server is running and no plug-in is loaded. "directory" specifies the LDAP CLD plug-in, which uses a calendar owner’s icsDWPHost LDAP attribute to determine the server where a specified calendar is stored. |
|
" " |
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 a user who logs into Calendar Server through Communications Express, or using WCAP commands, does not have an icsDWPHost attribute, Calendar Server uses this parameter to auto-provision the attribute. If a user 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. |
|
"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". |
|
"10" |
Specifies the maximum size in megabytes of the checkpoint file. |
|
"4" |
Specifies the size in megabytes of shared memory. |
|
"1000" |
Specifies the maximum number of database threads. |
|
"." |
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. |
|
"60" |
Specifies the number of seconds between checkpoints. |
|
"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" |
"1" |
Maximum number of backlogged requests before the server obtains a new network connection. |
|
"2" |
Initial number of connections for the Database Wire Protocol service client to make to each Database Wire Protocol service host. |
|
"2" |
Initial number of threads for handling Database Wire Protocol service requests. |
|
"1000" |
Maximum number of connections allowed to a server using the Database Wire Protocol service. |
|
"20" |
Maximum number of threads allowed to a server using the Database Wire Protocol service. |
|
"n" |
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.)
|
|
" " |
Specifies the IP address of the server using the Database Wire Protocol (DWP) service at the specified machine’s hostname. |
|
"9779" |
Specifies the port number of the server using the Database Wire Protocol (DWP) service at the specified machine’s hostname. |
|
" " |
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. |
|
" " |
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. |
|
"65536" |
Stack size for Database Wire Protocol service threads. |
|
Base DN to authenticate against if LDAP plug-in is used for the calendar locate mechanism. |
||
Host name of the LDAP server to access if an LDAP plug-in is used for the calendar locate mechanism. |
||
Bind credentials (password) for the user specified in the setting local.authldapbinddn if an LDAP plug-in is used for the calendar locate mechanism. |
||
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. |
||
"389" |
Port number of the LDAP server to access if an LDAP plug-in is used for the calendar locate mechanism. |
|
"n" |
If "y", 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. |
|
" " |
If csapi.plugin.loadall is "n" and csapi.plugin.authentication is "y", only load this specific plug-in. If not specified or blank (" "), load all authentication class plug-ins. |
|
"0" |
Size of Database Wire Protocol service log buffers (in bytes). |
|
"604800" |
Number of seconds before the Database Wire Protocol service log files expire. |
|
"60" |
Number of seconds between flushing buffers to the Database Wire Protocol service log files. |
|
"logs" |
Directory location of the Database Wire Protocol service log files. |
|
"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. |
|
"10" |
Maximum number of Database Wire Protocol related log files in log directory. |
|
"2097152" |
Maximum size of each Database Wire Protocol log file (in bytes). |
|
"20971520" |
Maximum disk space for all Database Wire Protocol log files (in bytes). |
|
"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. |
|
"86400" |
Number of seconds before Database Wire Protocol service log files are rotated. |
|
" " |
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. |
|
" " |
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. |
|
"localhost" |
The hostname of the machine on which the Database Wire Protocol service is running. |
|
"1000" |
Maximum number of concurrently running Database Wire Protocol service threads. |
|
"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 CPUs, see Using Load Balancing Across Multiple CPU's |
|
"no" |
If "yes", start the csdwpd service when starting all services and stop csdwpd when stopping all services |
|
"86400" |
Amount of time (in seconds) before closing the Database Wire Protocol service persistent connections that are idle. |
|
"59779" |
Port number that the Database Wire Protocol service listens to. This value is the default port for the LDAP CLD plug-in. |
|
"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"). |
The following table describes the configuration parameters in the ics.conf file for the LDAP data cache.
Table E–10 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). |
To configure resource calendars, use the parameters found in The following table:
Table E–11 Configuration Parameters for Resource Calendars
The following table shows the SSO configuration parameters with each parameter’s default value and description when you are using Access Manager.
Table E–12 SSO Configuration Parameters in the ics.conf File (Through Access Manager)
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–13 SSO Configuration Parameters in the ics.conf File Using Communications Servers Trusted Circle Technology
The following table shows the Group Scheduling Engine (GSE) configuration parameters with each parameter’s default value and description.
Table E–14 Group Scheduling Engine (GSE) Configuration Parameters in the ics.conf File
The following table lists the ics.conf parameters used to configure database handling, and gives each parameter’s default value and description.
Table E–15 Database Configuration Parameters in the ics.conf File
Parameter |
Default Value |
Description |
---|---|---|
"60" |
Number of seconds between checkpointing database transactions. |
|
"yes" |
If "yes" remove database checkpoint files after their transactions are synchronized. Do not set this to “no” unless you have enabled automatic backups. |
|
"100" |
Number of milliseconds between checking for database deadlocks that need to be broken. |
|
"." |
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 |
|
"10" |
Maximum megabytes for a database checkpoint file. |
|
"10000" |
Maximum number of threads that database environment must be prepared to accommodate. |
|
"4" |
Megabytes of shared memory for database environment. |
|
" " |
Email for user or alias that is responsible for administering the database. |
|
"yes" |
If "yes", data base statistics (reads, writes, deletes) will be counted. |
|
"100" |
Maximum number of calendars that can have counters. A calendar is enabled for counters using the cscal command line utility. |
|
"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. |
|
"25" |
Port for SMTP host. |
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–16 ics.conf Parameters Used by the Automatic Backup Process
Parameter |
Default Value |
Description |
---|---|---|
defaultstore.log |
Name of the log file. |
|
"." |
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. maxdays |
"7" |
Maximum 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.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 |
"120" |
Time in seconds between opening of new transaction logs. |
alarm.msgalarmnoticercpt |
"root@ localhost" |
Email address of the administrator to notify when necessary. |
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. |
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–17 Calendar Database Parameters for ENS Messages
Parameter |
Default Value |
Description |
---|---|---|
"enp:///ics/alarm" |
Specifies the URL for the ENS message. |
|
"" |
Specifies the content type of the alarm data. Value can be "text/xml" or "text/calendar". |
|
"no" |
Creates an ENS message when a calendar is created. |
|
"enp:///ics/calendarcreate" |
Specifies the URL for the ENS message. |
|
"text/xml" |
Specifies the content type of the message data: "text/xml" (default) or "text/calendar". |
|
"no" |
Creates an ENS message when a calendar is deleted. |
|
"enp:///ics/calendardelete" |
Specifies the URL for the ENS message. |
|
"text/xml" |
Specifies the content type of the message data: "text/xml" (default) or "text/calendar". |
|
"no" |
Creates an ENS message when a calendar is modified. |
|
"enp:///ics/calendarmodify" |
URL for the ENS message. |
|
"text/xml" |
Specifies the content type of the message data: "text/xml" (default) or "text/calendar". |
|
"no" |
Creates an ENS message when an event is created. |
|
"enp:///ics/caleventcreate" |
Specifies the URL for the ENS message. |
|
"text/xml" |
Specifies the content type of the message data: "text/xml" (default) or "text/calendar". |
|
"no" |
Creates an ENS message when an event is modified. |
|
"enp:///ics/caleventmodify" |
Specifies the URL for the ENS message. |
|
"text/xml" |
Specifies the content type of the message data: "text/xml" (default) or "text/calendar". |
|
"no" |
Creates an ENS message when an event is deleted. |
|
"enp:///ics/caleventdelete" |
Specifies the URL for the ENS message. |
|
"text/xml" |
Specifies the content type of the message data: "text/xml" (default) or"text/calendar". |
|
"no" |
Creates an ENS message when a todo is created. |
|
"enp:///ics/caltodocreate" |
Specifies the URL for the ENS message. |
|
"text/xml" |
Specifies the content type of the message data: "text/xml" (default) or "text/calendar". |
|
"no" |
Creates an ENS message when a todo is modified. |
|
"enp:///ics/caltodomodify" |
Specifies the URL for the ENS message. |
|
"text/xml" |
Specifies the content type of the message data: "text/xml" (default) or "text/calendar". |
|
"no" |
Creates an ENS message when a todo is deleted. |
|
"enp:///ics/caltododelete" |
Specifies the URL for the ENS message. |
|
"text/xml" |
Specifies the content type of the message data: "text/xml" (default) or "text/calendar". |
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–18 Event Notification Server (ENS) Configuration Parameters in the ics.conf File
The following table shows the Calendar Server API (CSAPI) configuration parameters with each parameter’s default value and description.
Table E–19 CSAPI Configuration Parameters in the ics.conf File
The following table shows the csmonitor utility configuration parameters with each parameter’s default value and description.
Table E–20 csmonitor Utility Configuration Parameters in the ics.conf File
Parameter |
Default Value |
Description |
---|---|---|
"0" |
Specifies whether csmonitor should loop continuously: "0"–Do not loop continuously. "1"–Loop continuously. This option requires more system resources, but it can useful in debug mode. |
|
"60" |
Specifies the delay in seconds between two monitoring loops. |
|
none |
Specifies the email address csmonitor sends messages from. |
|
none |
Specifies the email address csmonitor should send messages to. |
|
service.monitor.csdb.logthreshold |
"90" |
Specifies a threshold value in percent of the total disk space for the maximum disk occupation considered to be normal. If the disk occupation where the calendar database (csdb directory) resides exceeds this value, csmonitor sends a warning email message. |
"csmonitor.log" |
Specifies the csmonitor log file name. |
|
"2097152" |
Specifies the maximum log file size. If the log file exceeds this size, csmonitor saves the log as csmonitor.log.timestamp and resets the log. |
|
"0" |
Specifies the debug level. The higher this value, csmonitor sends more precise and verbose messages. |