kerimsatirli.com

Zarafa 6.04 / 6.20 on CentOS 5.2 with Plesk 8.6 Set-up guide

posted in Guides on September 18th, 2008

Part 10 - updating Zarafa to the latest veresion:

Please note that updating from Zarafa 6.04 to Zarafa 6.20 is a rather big switch, since the 6.20 branch supports multiple companies, whereas the 6.04 branch does not.

This means that you will have to backtrack through this tutorial and compare any configuration files (especially: server.cfg and ical.cfg with their .rpmnew versions and makes changes where necessary.

For the most part, you will be able to cross-copy settings, but you should still take the time to read through the files to understand what you are changing and updating.

As always, before starting any update process, make sure you backup your mySQL database and any Zarafa Stores you have.

  1. go to the Zarafa Download page and download the correct version for your system
    * make sure to select the right architecture (32-bit or 64-bit)
  2. go to the Zarafa Portal and convert your old serial to a new one
  3. upload the file to your server
  4. unpack the file like you normally do, e.g.:
    tar -xvzf zarafa-x-y-z.tar.gz
  5. change to the newly created directory, like you normally do, e.g.:
    cd zarafa-x-y-z
  6. stop all Zarafa services by typing::
    /etc/init.d/zarafa-gateway stop
    /etc/init.d/zarafa-ical stop
    /etc/init.d/zarafa-monitor stop
    /etc/init.d/zarafa-server stop
    /etc/init.d/zarafa-spooler stop
  7. update the Zarafa files by typing:
    rpm -Uvh libvmime*
    rpm -Uvh libical*
    rpm -Uvh zarafa*
  8. move old Webaccess to a backup location by typing:
    mv /var/www/vhosts/domain.com/httpsdocs/webaccess /var/www/vhosts/domain.com/httpsdocs/webaccess.old
  9. move Webaccess to a web-accessible directory by typing:
    mv /var/www/html/webaccess /var/www/vhosts/domain.com/httpsdocs/webaccess
  10. remove the Zarafa .htaccess file by typing:
    rm -rf /var/www/vhosts/domain.com/httpsdocs/webaccess/.htaccess
  11. move Webaccess Mobile to the Webaccess directory by typing:
    mv /var/www/html/webaccess-mobile/ /var/www/vhosts/domain.com/httpsdocs/webaccess/mobile
  12. type php -v
    1. if you get an error, continue with Part 7 and then continue below
    2. if you get no error, continue below
  13. insert the commands listed here into your vhost_ssl.conf file and update them where necessary
    * note that the only changes are in the php_admin_value open_basedir field:
    /etc/zarafa/webaccess-ajax and /etc/zarafa/webaccess-mobile have been appended
  14. update permissions and give webaccess/tmp/ full permissions like you normally do, e.g.:
    chmod -R 777 /var/www/vhosts/domain.com/httpsdocs/webaccess/tmp/

  15. update permissions and give webaccess/mobile/ full permissions like you normally do, e.g.:
    chmod -R 777 /var/www/vhosts/domain.com/httpsdocs/webaccess/mobile
  16. move Z-Push back to the web-accessible directory by typing:
    mv /var/www/vhosts/domain.com/httpsdocs/webaccess.old/z-push /var/www/vhosts/domain.com/httpsdocs/webaccess/
    * note that you can remove the webaccess.old directory once you have confirmed that everything is working
  17. update your Apache configuration by typing:
    /usr/local/psa/admin/sbin/websrvmng -u --vhost-name=domain.com -r -a
  18. disable dagent.cfg by typing:
    mv /etc/zarafa/dagent.cfg /etc/zarafa/dagent.old
    * note that this is described on the official Zarafa forums
  19. start all Zarafa services by typing::
    /etc/init.d/zarafa-ical start
    /etc/init.d/zarafa-monitor start
    /etc/init.d/zarafa-server start
    /etc/init.d/zarafa-spooler start
    /etc/init.d/zarafa-licensed start
    * note that zarafa-licensed was added in the 6.20 branch and is not available in 6.04

 

Pages: 1 2 3 4 5 6 7 8 9 10 11 12

tagged with:,,,,,,,


7 Responses to 'Zarafa 6.04 / 6.20 on CentOS 5.2 with Plesk 8.6 Set-up guide'

Subscribe to comments with RSS or TrackBack to 'Zarafa 6.04 / 6.20 on CentOS 5.2 with Plesk 8.6 Set-up guide'.

  1. Brian said, on October 4th, 2008 at 5:26 pm

    This is an excellent tutorial. Two questions–what if I did the install with 6.2 instead of 6.04 then upgrade? Second, have you attempted to run this in multi-company mode to give more of your domains access to the installation? I’m thinking about trying to deploy this to multiple customers I have running.

    Brian

  2. Kerim Satirli said, on October 5th, 2008 at 9:57 am

    Thanks Brian.

    I gave 6.2 a try on my homeserver and the install was, basically, the same - the only difference being that the config files had a few more items in there (for multicompany support) and I also needed to update the key and alter my start-up scripts.

    I have not yet attempted to run Zarafa in multi-company mode, but I will give it a try soonish (within 2 weeks, I guess), I’ll post my experiences here.

  3. Bart said, on October 31st, 2008 at 7:58 am

    Hi,

    Great guide, however When it comes to the MAPI, I have a problem.

    I get the following error:

    Not Found: MAPI include files not found

    However, there is no mention in ur documents about this. How did you over come this problem since the mapi.so.0.0.0 is not compatible with PHP 5.2.6 (Yet, im using 5.1.6)

    Thanks
    B

  4. Kerim Satirli said, on October 31st, 2008 at 6:03 pm

    Hi Bart,

    the problem with mapi.so.0.0.0 can be solved by following Step 7 of the guide.

  5. Alex said, on October 31st, 2008 at 6:42 pm

    Hi Kerim,

    your how to inspired me to set up the Zarafa 6.20 from source on my Plesk 8.6 based on openSuSE 10.3.

    So far I am quite impressed, especially by the active sync component z-push adds to it. But as long as no real CalDAV implementation is there and I found out how to work on ldap for my vCards this is not going to replace mobile.me for me :-)

    But one question do I have - what did you do about IMAP and port 143? Do you still run imapd from Plesk ? In my case I would only move 5 email accounts (basically my family) towards zarafa when the time has come, but the other users on my server should stay on their original Plesk setup.

    Kind regars,
    Alex

  6. Kerim Satirli said, on November 1st, 2008 at 10:39 am

    Alex,

    thanks for your feedback, much appreciated!

    CalDAV will eventually come, of that I am sure, but for now, you are correct: mobileMe might be better suited for your needs.

    I personally only sync via ActiveSync, so Zarafa works perfectly for me, that and the fact that I’d rather host my own data as opposed to having it up in the cloud.

    That said, to answer your actual question: I do not use Zarafa’s gateway functions and keep email within Plesk.

    I do however, modify how Qmail handles emails. See here for more information.

  7. Bart said, on November 3rd, 2008 at 1:27 am

    Thanks Kerim,

    My problem was that Plesk had the domain name CHROOT’d so it was not able to use the MAPI files located in /usr/share/php/mapi/. To overcome this, I had to add the following file:

    /var/www/vhosts/domain.com/conf/vhost.conf

    Then add the following into the file:

    Options +FollowSymLinks
    php_admin_value open_basedir “/var/www/vhosts/domain.com/httpdocs:/etc/zarafa/webaccess-ajax:/tmp:/usr/lib/php/modules:/usr/share/php/mapi/”

    Once the above was added all working.

    Hope that helps others.

    Cheers
    Bart

Leave a Reply