steffen: server/doc QIM2,NONE,1.1

[cvs at intevation.de]

Author: steffen

Update of /kolabrepository/server/doc
In directory doto:/tmp/cvs-serv26677

Added Files:
	QIM2 
Log Message:
QIM

--- NEW FILE: QIM2 ---
Quick Install Manual - Kolab 2.0
Author: Steffen Hansen <steffen at klaralvdalens-datakonsult.se>
Based on Kolab1 QIM by Martin Konold <martin.konold at erfrakon.de>
$Id: QIM2,v 1.1 2004/08/16 00:15:54 steffen Exp $

Please have a look at the documentation available from www.kolab.org.

Please report Problems with the QIM or the software to FIXME so that
we can improve Kolab and its documentation permanently.

Upgrading from an alpha or beta release we do not encourage, as the
LDAP layout has changed greatly. You may however want to manually
merge old ldif data into the new tree, after the Kolab installation.

Instructions for installing binaries are appended to this
documentation.

=========================================================
Important!

Kolab 2 is based on OpenPKG 2.1. SuSE 9.1 users might experience
problems with the openpkg-2.1.0-2.1.0.rpm.sh bootstrap package

We highly recommend to use the following environment variables in
order to be safe from some potential surprises.

	LC_ALL=C
	LC_MESSAGES=C
	LANG=C
	SUPPORTED=C
        export LC_ALL LC_MESSAGES LANG SUPPORTED


Do _NOT_ use an NFS mounted partition for installing Kolab
(e.g. /kolab). Cyrus IMAPD cannot work over NFS and it would be
suboptimal anyway. Explanation at
http://asg.web.cmu.edu/cyrus/imapd/install-FAQ.html#nfs .

=========================================================
====== Installation from Source =========================
      (see below for binary installation)

We recommend to install the Kolab Server from source though at the end
of this QIM we provide instructions how to install from binaries on
Debian 3.0 (woody).

Preparation of OpenPKG environment (see also http://www.openpkg.de)

1. Download everything from
ftp://ftp.kolab.org/kolab/server/development/current/sources

2. Run obmtool as root to build and install the packages:
   ./obmtool kolab | tee kolab.log

Please examine the log file kolab.log carefully for errors.

Especially make sure that in the kolab.log there are no errors.

Now you succeeded in bootstrapping the kolab environment and building
and installing the required OpenPKG and Kolab rpms. To upgrade or
replace the default package selection, just edit obmtool.conf -- it
contains a list of everything installed.

New users kolab, kolab-r and kolab-n have been added to /etc/passwd
and groups with the same names to /etc/group.

4. Put the following script in /etc/init.d/kolab or wherever your system
expects startup scripts.

Depending on the OS you may require a different location or syntax. Please consult the manual
of your operating system.

For LSB complient systems the startup script /etc/init.d/kolab looks like

#!/bin/sh
#
## chkconfig: 345 99 01
# description: starts and stops the Kolab server
# #
[ ! -f /kolab/etc/rc.d/rc.kolab ] && exit 0
case "$1" in
  start|stop|restart|reload|status)
    /kolab/bin/openpkg rc all $1
    ;;
  *)
    echo "usage: $0
    start|stop|restart|reload|status" 1>&2
    ;;
esac
                                               
Now continue with section
==> "Setup after RPM-Installation"


============================================================
====== Installation from Binaries  =========================
FIXME: TODO

============================================================
====== Setup after RPM-Installation ========================

Please follow the instructions in the output 
from the installation of the kolab rpm carefully. 
If installing a fresh system,
especially look for a bootstrapping command 
like "/kolab/etc/kolab/kolab_bootstrap -b". Execute that command and
follow the instructions.

As root you may now start the kolab server manually via

	/kolab/bin/openpkg rc all start

Note 1: Please watch carefully the output when running the
kolab_bootstrap script -- you will then see the important manager
password on the screen which is required for administrating kolab
server via webinterface.

	https://kolabserver.yourdomain.com/admin

Note 2: Note that kolab startup takes its time. Just give it some seconds and watch the
syslog in the meantime. It should all come up nicely.

On Linux the output of "netstat -ntplou" gives you an idea which services got
activated.

===========================================================================