4.6 Configuring Calendar Services (Daemons)

This section contains instructions on how to configure calendar services (daemons).

This section contains the following topics:

• To Configure Start and Stop Services

• To Configure the Watcher Process for Calendar Server Version 6.3

• To Configure Administrative Services (csadmind)

• To Configure HTTP Services (cshttpd) for Calendar Server Version 6.3

• To Configure Alarm Notification for Calendar Server Version 6.3

See also, Chapter 9, Configuring Automatic Backups (csstored).

To Configure Start and Stop Services

The start-cal and stop-cal commands are wrapper scripts that allow ease of starting and stopping Calendar Server. The utility is defined in Appendix D, Calendar Server Command-Line Utilities Reference.

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

2. Stop Calendar Server services by issuing the stop-cal command.

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

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

5. Edit one or more of the parameters as shown in the following table:

   Parameter	Description and Default Value
   local.serveruid	Runtime user identifier (uid). The default is "icsuser". This is the user identifier to use when super-user privileges are not needed.
   local.servergid	Runtime group identifier (gid). The default is "icsgroup". This is the group identifier to use when super-user privileges are not needed.
   local.autorestart	If this parameter is set to "yes", if a service that is connected to the watcher dies without properly disconnecting, it is automatically restarted.
   local.autorestart.timeout	Defines the auto-restart timeout interval. To avoid infinite restart attempts on auto-start, if a service dies twice in a specific interval, it will not be restarted. The default setting is 10 minutes.

6. Save the file as ics.conf.

7. Restart Calendar Server.

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

To Configure the Watcher Process for Calendar Server Version 6.3

The watcher process, watcher, monitors failed socket connections. It is used with both Calendar Server and Messaging Server. To set the Calendar Server parameters to configure Watcher, perform the following steps:

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

2. Stop Calendar Server services by issuing the stop-cal command.

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

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

5. Edit one or more of the parameters as shown in the following table:

   Parameter	Description and Default Value
   local.watcher.enable	If this parameter is set to "yes", the start program attempts to start the watcher before any other services. And daemons will connect to it through a socket connection. The default is "no", but the configuration program changes it to "yes".
   local.watcher.port	This is the port on which the watcher listens. Messaging Server uses port 49994. A different port should be used for Calendar Server, for example 49995.
   local.watcher.config.file	The configuration file for watcher. If the path is relative, it is relative to the config directory. The default is watcher.cnf.
   service.autorestart	If set to "yes", the watcher automatically restarts any registered service that dies without properly disconnecting. If the service dies twice in 10 minutes, watcher will not restart it.

6. Save the file as ics.conf.

7. Restart Calendar Server.

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

See Also

For more information about the Watcher process, see Sun Java System Messaging Server 6.3 Administration Guide. Both Chapter 4 and Chapter 23 have information.

If Watcher is enabled, each service the Watcher is monitoring must be registered with the Watcher process. This is done automatically and internally by Calendar Server daemons. Alternatively, the daemons create a pid files in the cal-svr-base/data/proc directory that contain the process ID of each service and its status, either "init", or "ready".

To Configure Administrative Services (csadmind)

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

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

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

4. Edit one or more of the parameters as shown in the following table:

   Parameter	Description and Default Value
   local.store.checkpoint.enable	If "yes", start the csadmind database checkpoint thread. If "no", no checkpoint log files created. The default is "yes".
   service.admin.dbcachesize	Maximum cache size (in bytes) for Berkeley Database for administration sessions. The default is "8388608".
   local.store.deadlock.enable	If "yes", start the csadmind database deadlock detection thread. The default is "yes".
   service.admin.diskusage	If "yes", start the csadmind low disk space monitor thread. The default is "no". Disk usage is not monitored by default.
   service.admin.enable	If "yes", start the csadmind service when starting all services and stop csadmind when stopping all services. The default is “yes”.
   service.admin.maxthreads	Maximum number of running threads per administration session. The default is “10”.
   service.admin.resourcetimeout	Number of seconds before timing out an administration connection. The default is “900”.
   service.admin.serverresponse	If "yes", start the csadmind service response thread. The default is “no”.
   service.admin.sessiondir.path	Temporary directory for administration session requests. No default.
   service.admin.sessiontimeout	Number of seconds before timing out an HTTP session in csadmind. The default is “1800”.
   service.admin.sleeptime	Number of seconds to wait between checking for started, stopped, or ready calendar service. The default is “2”.
   service.admin.starttime	Number of seconds to wait for any calendar service to start. The default is “300”.
   service.admin.stoptime	Number of seconds to wait for any calendar service to stop. The default is “300”.
   service.admin.stoptime.next	Number of seconds to wait between sending stop commands to any calendar service. The default is “60”.

5. Save the file as ics.conf.

6. Restart Calendar Server.

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

To Configure HTTP Services (cshttpd) for Calendar Server Version 6.3

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

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

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

4. Edit one or more of the parameters as shown in the following table:

   Parameter	Description and Default Value
   service.http.admins	Space separated list of user ID's with administration rights to this Calendar Server. The default is "calmaster".
   service.http.allowadminproxy	If "yes", allow login via proxy, which is the default.
   service.http.allowanonymouslogin	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). The default is "yes".
   service.http.calendarhostname	HTTP host for retrieving HTML documents. To enable users to use a fully qualified host name to access calendar data, this value must be the fully qualified host name (including the machine name, DNS domain and suffix) of the machine on which Calendar Server is running, such as mycal@sesta.com. If not specified, the local HTTP host is used.
   service.http.commandlog	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.
   service.http.commandlog.all	This parameter is for debugging only. If set to "yes", the system logs all HTTP requests into the http.access log file. Do not use this during production runtime. It will fill up the log file very quickly and could cause performance degradation.
   service.http.cookies	Tells the server to whether or to support cookies (yes/no). It must be set to "yes" to enable single sign-on. The default is "yes".
   service.http.dbcachesize	Maximum cache size of Berkeley database for HTTP sessions. The default is "8388308".
   service.http.domainallowed	If specified and not blank (" "), 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). The default is blank ("").
   service.http.domainnotallowed	If specified and not blank (" "), 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). The default is blank (" ").
   service.http.attachdir.path	Directory location relative to local.queuedir (or an absolute path if specified) where imported files are temporarily stored. The default is the current directory (".").
   service.http.ipsecurity	If "yes", all requests that reference an existing session are verified as originating from the same IP address. The default is “yes”.
   service.http.enable	If "yes", start the cshttpd service when starting all services and stop cshttpd when stopping all services. The default is “yes”. Caution – Disabling the HTTP service with this parameter will also disable HTTPS.
   service.http.idletimeout	Number of seconds before timing out an HTTP connection. The default is “120”.
   service.http.listenaddr	Specifies the TCP address that HTTP services will listen on for client requests. The default is "INADDR_ANY", which indicates any address.
   service.http.logaccess	If "yes", HTTP connections to server are fully logged. The default is “no”.
   service.http.maxsessions	Maximum number of HTTP sessions in cshttpd service. The default is “5000”.
   service.http.maxthreads	Maximum number of threads to service HTTP requests in cshttpd service. The default is “20”.
   service.http.numprocesses	Maximum number of concurrently running HTTP service (cshttpd) processes that should run on a server. The default is “1”. For a server that has multiple CPU's, see 21.8 Using Load Balancing Across Multiple CPU's.
   service.http.port	Port for HTTP requests from Calendar Server users. The default is “80”.
   service.http.proxydomainallowed	If specified and not "", filter for allowing proxy login based on TCP domains. Same syntax as service.http.domainallowed. The default is "".
   service.http.resourcetimeout	Number of seconds before timing out an HTTP session. The default is “900”.
   service.http.sessiondir.path	Directory for the HTTP session database. The default is “http”.
   service.http.sessiontimeout	Number of seconds before timing out an HTTP session in cshttpd service. The default is “1800”.
   service.http.sourceurl	Directory relative to executable where all URL references to files are stored. The default is "" (null).
   service.http.tmpdir	Temporary directory for HTTP sessions. The default is “/var/opt/SUNWics5/tmp”.

5. Save the file as ics.conf.

6. Restart Calendar Server.

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

To Configure Alarm Notification for Calendar Server Version 6.3

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

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

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

4. Edit one or more of the following ics.conf parameters as shown in the following table:

   Parameter	Description and Default Value
   alarm.diskstat.msgalarmdescription	Description sent with insufficient disk space messages.  The default description is: “percentage calendar partition diskspace available”.
   alarm.diskstat.msgalarmstatinterval	Number of seconds between monitoring disk space. The default is “3600”.
   alarm.diskstat.msgalarmthreshold	Percentage of available disk space that triggers sending a warning message. The default is “10”.
   alarm.diskstat.msgalarmthresholddirection	Whether alarm.diskstat.msgalarmthreshold is above or below percentage. -1 is below and 1 is above. The default is “-1”.
   alarm.diskstat.msgalarmwarninginterval	Number of hours between sending warning messages about insufficient disk space. The default is “24”.
   alarm.msgalarmnoticehost	The host name of the SMTP server used to send server alarms. The default is “localhost”.
   alarm.msgalarmnoticeport	The SMTP port used to send server alarms. The default is “25”.
   alarm.msgalarmnoticercpt	The email address to whom server alarms sent. “Postmaster@localhost”
   alarm.msgalarmnoticesender	The email address used as the sender when the server sends alarms. The default is “Postmaster@localhost”
   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	Description sent with no service response messages. The default is “calendar service not responding”.
   alarm.responsestat.msgalarmstatinterval	Number of seconds between monitoring services. The default is “3600”.
   alarm.responsestat.msgalarmthreshold	The default is “100” (only trigger sending a warning message if no service response.)
   alarm.responsestat. msgalarmthresholddirection	Specifies whether alarm.responsestat.msgalarmthreshold is above or below percentage. -1 is below and 1 is above. The default is “-1”
   alarm.responsestat. msgalarmwarninginterval	Number of hours between sending warning messages about no service response sent out. The default is “24”.
   local.rfc822header.allow8bit	Allow (“y”) or not allow (“n”) 8 bit headers in email messages sent by this server.
   service.admin.alarm	Enable ("yes") or disable ("no") alarm notifications for administration tools. The default is “yes”.

5. Save the file as ics.conf.

6. Restart Calendar Server.

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