Installing Kolab Groupware Solution + Horde

My team has been assigned with the task to identify suitable email/collaboration suite to be proposed to our customers. We need some basic features such as email (with imap & pop support) calendaring, to do list and mail/groupware clients connection capabilities such as Kontact, Evolution and optionally MS Outlook.

For a start we decided to tryout Kolab Groupware Solution as some their features are suitable for our client’s environment such as using OpenPkg as the installation medium (our clients could use any type of distro), the usage of Postfix, OpenLDAP and Cyrus IMAP as the back end and last but not least the solution utilize Horde as their front end interface.

Below is the simplified installation guide for installing the solution. We are using a fresh installed Centos 5 machine with minimum package installation.

- Make sure SELinux is disabled (use setup)

- Install GCC for compilation process
yum install gcc

- Install GCC (compatibility 3.4) for to resolve gcc conflict
yum install compat-gcc-34

- Making GCC-34 as default gcc tool
mv /usr/bin/gcc /usr/bin/gcc41
ln -sf /usr/bin/gcc34 /usr/bin/gcc

- Create kolab template directory
mkdir /kolab-template
cd /kolab-template

- Download kolab sources
wget -r -l1 -nd --no-parent http://ftp.belnet.be/packages/kolab/server/release/kolab-server-2.1.0/sources/

- Verify file integrity (optional)
gpg --verify MD5SUMS
md5sum -c MD5SUMS

[Checkpoint #1]

- Create kolab production directory
cp -afv /kolab-template /kolab
cd /kolab

- Make sure that the following names are not in /etc/passwd or /etc/groups,
“kolab” “kolab-r” “kolab-n” if exist delete and run “pwconv”

- Start compilation.
sh obmtool kolab 2>&1 | tee kolab-build.log

*This process takes some time, so it is advisable to use ’screen’ if your are connected remotely.

- If compilation failed, simply delete/rename the /kolab folder
and restart process at [Checkpoint #1]

- Start installation
/kolab/etc/kolab/kolab_bootstrap -b

- Start the services
/kolab/bin/openpkg rc all start

- Try access (using your web browser)
https://kolab_adress/admin

- Stop kolab services
/kolab/bin/openpkg rc all stop

- Download modified kolab sources (for horde support)
mv obmtool.conf obmtool.conf.bak
wget -r -l1 -nd --no-parent http://build.pardus.de/downloads/kolab-horde-tmp

- Some hacking to the obmtool.conf due to links provided already dead
- Change
URL="ftp://ftp.klaralvdalens-datakonsult.se/pub/kolab/server/current/2.1"
- to
URL="http://build.pardus.de/downloads/kolab-horde-tmp"

- Start re-compilation
sh obmtool kolab 2>&1 | tee kolab-build.log

- Start re-installation
/kolab/etc/kolab/kolab_bootstrap -b

- Re-start the kolab services
/kolab/bin/openpkg rc all start

- Try access (using your web browser)
http://kolab_address/horde

REFERENCES
http://wiki.kolab.org/index.php/Kolab2_Installation_-_Source
http://wiki.kolab.org/index.php/Fedora_6
http://wiki.kolab.org/index.php/Kolab2_Installation_-_Horde


Sponsored links

Being a webmaster, it’s necessary to acquire full knowledge of the online marketing tips and tricks. The search engine submission of the website is the most important of all. And also try to focus on keywords and meta tags since it’s the most important factor that enales you to make the most of the ppc.

Popularity: 33% [?]



Stumble it!

RSS feed | Trackback URI

7 Comments »

Comment by Alan
2007-07-15 23:26:41

How is this solution working out? Have you deployed to any of your Clients? If so, how do they find it?

 
Comment by Admin
2007-07-16 09:24:08

The installation is pretty straight forward as it is using OpenPKG. Aparts from gcc compilation issue which we have sorted out by using compat-gcc-34 and some minor changes need to be done during horde installation (due to ‘klaralvdalens’ server not providing needed files anymore), overall installation are quite smooth.

We can simply say that given the correct way to do it (using the quick howto above) without any glitches, we can do complete installation in a few hours only. That includes the time needed for compilation processes and packages downloading time.

We are yet to deploy kolab on any of our clients. We are still in the process of evaluating other alternatives. Currently we are looking into Dbmail + horde. So stay tuned for more updates.

 
Comment by Dave
2007-08-02 23:27:10

Horde is great - but it is a pain to keep updated in my opinion.

You might also want to check Zimbra - http://www.zimbra.com/

Comment by admin
2007-08-03 10:37:01

Agree. Horde offers many good features but the customization part is quite tricky. We have tried Zimbra before and quite impressed with it. Zimbra is a solid package with all needed features already provided out of the box. The only thing is it requires high specification system. It suitable for some of our customers, but for others with limited budget, we need to offer something more lightweight.

 
 
2007-08-28 23:35:41

[…] to MS Outlook that unites mature KDE applications, like Kmail’s shared email folders, Kolab groupware, KOrganizer calendar sharing, KNotes sticky notes, and Google synchronization into one […]

 
Comment by Gunnar Wrobel
2007-10-02 00:50:46

Nice to hear that this seems to have worked for you. The installation procedure will of course get much simpler once Horde is included by default in the Kolab Server. We are going to release another beta of the server soon that will allow you to get Horde included without any extra effort.

 
Comment by tita
2007-10-03 20:22:11

it is really nice. but how can login to horde?

thank u

 
Name (required)
E-mail (required - never shown publicly)
URI
Your Comment (smaller size | larger size)
You may use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong> in your comment.