<?xml version="1.0" encoding="ISO-8859-1"?>

<!--  $Id: wtimer-config-lion.xml,v 1.1 2003/02/04 18:53:44 gerd Exp $
   -  ======================================================================
   -
  -->

<!-- ===================================================================== -->
<!-- Database access configuration:                                        -->
<!-- ===================================================================== -->

<!ENTITY database-name "wtimer">

  <!-- database-name: the ODBC name of the database. There must be an
     - odbc.ini entry for this name.
    -->

<!ENTITY database-user "www">

  <!-- database-user: the username to connect as. Some ODBC drivers allow
     - it to specify the username in odbc.ini (preferrable)
    -->

<!ENTITY database-passwd "">

  <!-- database-passwd: the password authenticating the user. Some ODBC drivers
     - allow it to specify the username in odbc.ini (preferrable)
    -->

<!ENTITY database-timeout "60">

  <!-- database-timeout: (only interpreted by wtimerd) After the database
     - connection has not been used for this number of seconds, it is closed.
    -->

<!-- ===================================================================== -->
<!-- LOGIN CONFIGURATION                                                   -->
<!-- ===================================================================== -->

<!ENTITY login-dialog "yes">

  <!-- login-dialog: Whether the application displays its own login dialog
     - ("yes") or not ("no").
     -
     - "yes" means that the application stores passwords in the database,
     - and that it provides a dialog to change passwords.
     -
     - "no" means that the application automatically logs in as the user
     - contained in the REMOTE_USER variable. The web server must have been
     - configured such that it provides this variable. In this case, the
     - passwords in the database are ignored, and there is no dialog to
     - change passwords. Note that it is still required that a user record
     - exists in the database to log in.
     -
     - Choose "yes" if you do not already have a user database, and choose
     - "no" if you have one. Think of a directory of users, and you
     - want to configure that your web server authenticates against the
     - directory. WTimer simply takes over what the web server thinks
     - who the current user is.
     -
     - The application adds the suffix "/auth" to the URL when it wants
     - to have the REMOTE_USER variable, so you can configure the access
     - restrictions for a certain URL.
    -->

<!-- ===================================================================== -->
<!-- URL CONFIGURATION                                                     -->
<!-- ===================================================================== -->

<!ENTITY static-url-prefix "/npc/wtimer/static/">

  <!-- static-url-prefix: Where to find statically served files like images.
       This entity should be either empty or end with a slash.
    -->


<!ENTITY ajp-mount-point "/npc/wtimer/servlets/">

  <!-- ajp-mount-point: (only interpreted by wtimerd, and only if a Jakarta
     - connector (mod_jk) is used at the web server side) Where the servlets
     - are mounted. For example, if this value is "/servlets/", the
     - wtimer application can be reached under "/servlets/wtimer".
     - This value must correspond to the configuration of the web server.
    -->

<!-- ===================================================================== -->
<!-- CONFIGURATION OF THE AJP SERVER WTIMERD (SERVLET SERVER)              -->
<!-- ===================================================================== -->

<!-- ajp-*: Only used by wtimerd! -->

<!ENTITY ajp-bindaddress "localhost">

  <!-- ajp-bindaddress: The network interface to which the server binds.
     - This can be a host name, an IP address, or "*" which means to bind
     - to all network interfaces.
    -->

<!ENTITY ajp-port "8007">

  <!-- ajp-port: The TCP port where the server listens for incoming
     - connections.
     - This value must correspond to the configuration of the web server.
    -->

<!ENTITY ajp-allowhost "">

  <!-- ajp-allowhost: If non-empty, only the mentioned web servers can
     - connect to the AJP server. This should be a space-separated list
     - of host names or individual IP addresses. If empty, there are
     - no restrictions.
    -->

<!ENTITY ajp-backlog "200">

  <!-- ajp-backlog: The backlog parameter of the "listen" system call.
     - It counts usually the number of established, but not yet accepted
     - connections, but there is no real standard, so operating
     - systems can interpret this number differently.
     - This number should be much higher than ajp-processes.
    -->

<!ENTITY ajp-processes "2">

  <!-- ajp-processes: The number of pre-initialized processes. "0" means
     - to start a new process for every connection. Positive numbers mean
     - to start exactly that number of worker processes.
     - For low numbers of concurrent users, "0" is perfectly ok. For high
     - numbers of concurrent users, choose a small multiple of the number
     - of CPUs.
    -->

<!ENTITY ajp-https "yes">

  <!-- ajp-https: whether the web server is secure ("yes") or not ("no").
     - It is necessary to set this variable because the AJP protocol does
     - not pass the HTTPS environment variable, like CGI does.
    -->

<!ENTITY ajp-pid-file "/var/run/wtimer/wtimer.pid">

  <!-- ajp-pid-file: The file containing the process ID of the wtimer
     - daemon
    -->


<!-- ******************* For Emacs: ********************* -->
<!--
Local Variables:
mode: xml
End:
-->