test

Sun Java System Calendar Server 6.3 Administration Guide

ProcedureTo 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.

Note –

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".