Kolab 2.2.3

Installation Manual

The Kolab Groupware Solution

Edition 1

Jeroen van Meeuwen, RHCE

Kolab Systems Engineering

vanmeeuwen@kolabsys.com

Legal Notice

Copyright © 2010 Kolab Systems AG This material may only be distributed subject to the terms and conditions set forth in the GNU Free Documentation License (GFDL), V1.2 or later (the latest version is presently available at http://www.gnu.org/licenses/fdl.txt).

Abstract

A short overview and summary of the book's subject and purpose, traditionally no more than one paragraph long. Note: the abstract will appear in the front matter of your book and will also be placed in the description field of the book's RPM spec file.

Preface

1. Document Conventions

This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.

In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default.

1.1. Typographic Conventions

Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.

Mono-spaced Bold

Used to highlight system input, including shell commands, file names and paths. Also used to highlight keycaps and key combinations. For example:

To see the contents of the file my_next_bestselling_novel in your current working directory, enter the cat my_next_bestselling_novel command at the shell prompt and press Enter to execute the command.

The above includes a file name, a shell command and a keycap, all presented in mono-spaced bold and all distinguishable thanks to context.

Key combinations can be distinguished from keycaps by the hyphen connecting each part of a key combination. For example:

Press Enter to execute the command.
Press Ctrl+Alt+F1 to switch to the first virtual terminal. Press Ctrl+Alt+F7 to return to your X-Windows session.

The first paragraph highlights the particular keycap to press. The second highlights two key combinations (each a set of three keycaps with each set pressed simultaneously).

If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in mono-spaced bold. For example:

File-related classes include filesystem for file systems, file for files, and dir for directories. Each class has its own associated set of permissions.

Proportional Bold

This denotes words or phrases encountered on a system, including application names; dialog box text; labeled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:

Choose System → Preferences → Mouse from the main menu bar to launch Mouse Preferences. In the Buttons tab, click the Left-handed mouse check box and click Close to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).
To insert a special character into a gedit file, choose Applications → Accessories → Character Map from the main menu bar. Next, choose Search → Find… from the Character Map menu bar, type the name of the character in the Search field and click Next. The character you sought will be highlighted in the Character Table. Double-click this highlighted character to place it in the Text to copy field and then click the Copy button. Now switch back to your document and choose Edit → Paste from the gedit menu bar.

The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context.

Mono-spaced Bold Italic or Proportional Bold Italic

Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:

To connect to a remote machine using ssh, type ssh username@domain.name at a shell prompt. If the remote machine is example.com and your username on that machine is john, type ssh john@example.com.
The mount -o remount file-system command remounts the named file system. For example, to remount the /home file system, the command is mount -o remount /home.
To see the version of a currently installed package, use the rpm -q package command. It will return a result as follows: package-version-release.

Note the words in bold italics above — username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.

Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:

Publican is a DocBook publishing system.

1.2. Pull-quote Conventions

Terminal output and source code listings are set off visually from the surrounding text.

Output sent to a terminal is set in mono-spaced roman and presented thus:

books        Desktop   documentation  drafts  mss    photos   stuff  svn
books_tests  Desktop1  downloads      images  notes  scripts  svgs

Source-code listings are also set in mono-spaced roman but add syntax highlighting as follows:

package org.jboss.book.jca.ex1;

import javax.naming.InitialContext;

public class ExClient
{
   public static void main(String args[]) 
       throws Exception
   {
      InitialContext iniCtx = new InitialContext();
      Object         ref    = iniCtx.lookup("EchoBean");
      EchoHome       home   = (EchoHome) ref;
      Echo           echo   = home.create();

      System.out.println("Created Echo");

      System.out.println("Echo.echo('Hello') = " + echo.echo("Hello"));
   }
}

1.3. Notes and Warnings

Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.

Note

Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.

Important

Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' won't cause data loss but may cause irritation and frustration.

Warning

Warnings should not be ignored. Ignoring warnings will most likely cause data loss.

2. We Need Feedback!

You should over ride this by creating your own local Feedback.xml file.

Chapter 1. About Kolab Groupware

The installation of Kolab requires you prepare the system for installation.

Part I. Kolab Groupware Server Installation

Installation Manual for Kolab Groupware on server systems

Table of Contents

2. Installation Introduction

3. Kolab Server on Enterprise Linux

3.1. Prerequisites

3.1.1. Server System
3.1.2. YUM Repositories

3.2. Repository Configuration

3.2.1. EPEL Repository Configuration
3.2.2. Kolab Repository Configuration

3.3. Standalone Server Installation

4. Kolab Initial Configuration

4.1. Manual Configuration

5. Kolab Webclient Installation

Chapter 2. Installation Introduction

Kolab Groupware is not just one big server component. It consists various, well-known, mature Open Source software components.

Chapter 3. Kolab Server on Enterprise Linux

3.1. Prerequisites

3.1.1. Server System
3.1.2. YUM Repositories

3.2. Repository Configuration

3.2.1. EPEL Repository Configuration
3.2.2. Kolab Repository Configuration

3.3. Standalone Server Installation

The installation of the Kolab Groupware server requires you prepare the system for installation. This part of the installation manual addresses the installation procedure on Enterprise Linux systems, which include:

Red Hat Enterprise Linux 5 (recommended)
CentOS 5

3.1. Prerequisites

This section lists the prerequisites for a Kolab Groupware server system on Enterprise Linux.

3.1.1. Server System

These are the system prerequisites for a supported Kolab server installation on Enterprise Linux.

System Resources

FIXME: 4GB of RAM
FIXME: Intel or AMD 64-bit 2.4Ghz+

Operating System Resources

The following software packages may not be installed on the Kolab Groupware server system:
- cyrus-imapd
- openldap

You can verify whether any of those packages is installed using the following command:

rpm -qv <package-name>

Should any of the aforementioned packages be installed on the Kolab Groupware server system already, please verify whether they have been used before removing them. Should the packages have been used, consider moving to Kolab Groupware on this server system a migration and continue with the migration manual available at:

FIXME: Provide a URL for the migration manual

3.1.2. YUM Repositories

A Kolab Groupware server system requires the following YUM repositories to be installed in complete, available and enabled;

The Extra Packages for Enterprise Linux (EPEL) repository.
For more details on the installation and configuration of the EPEL repository, please refer to Section 3.2.1, “EPEL Repository Configuration”.
The Kolab Groupware repository.
For more details on the installation and configuration of the Kolab repository, please refer to Section 3.2.2, “Kolab Repository Configuration”.

3.2. Repository Configuration

3.2.1. EPEL Repository Configuration

FIXME: Something on EPEL repository configuration

3.2.2. Kolab Repository Configuration

FIXME: Something on Kolab repository configuration

3.3. Standalone Server Installation

When the prerequisite requirements are met, install the Kolab Groupware Server components:

yum install kolab

This will install a completely standalone Kolab Groupware server. Continue to Chapter 4, Kolab Initial Configuration

Chapter 4. Kolab Initial Configuration

4.1. Manual Configuration

para

Run, as root:
```
# setup-kolab.pl
```
This will start a configuration dialog.
Yet Another Step...

4.1. Manual Configuration

this section goes to manual configuration of Kolab (this is what setup-kolab.pl should actually be doing)

after yum install kolab
copy /etc/kolab/templates/kolab.conf.template to /etc/kolab/kolab.conf
check out /etc/kolab/kolab.conf
    - set the fqdn
    - check

Chapter 5. Kolab Webclient Installation

para

how to configure the webserver to show the web interface over SSL only

Revision History

Revision History

Revision 0

Sun May 16 2010

Dude McPants

Initial creation of book by publican

Index

F

feedback

contact information for this manual, We Need Feedback!