The latest v6.20 release will remain accessible on our servers. If you need to access the repository after the release of v6.22, please use the following lines in your <code>yum</code> repository configuration to access v6.20 packages:

The latest v6.20 release will remain accessible on our servers. If you need to access the repository after the release of v6.22, please use the following lines in your <code>yum</code> repository configuration to access v6.20 packages:

−

<code>

+

Start a console and create a software repository file for Open-Xchange:

−

[ox]

+

<code>$ vim /etc/yum.repos.d/ox.repo</code>

−

name=Open-Xchange

+

[ox]

−

baseurl=http://software.open-xchange.com/OX6/6.20/RHEL5/

+

name=Open-Xchange

−

gpgkey=http://software.open-xchange.com/oxbuildkey.pub

+

baseurl=http://software.open-xchange.com/OX6/6.20/RHEL5/

−

enabled=1

+

gpgkey=http://software.open-xchange.com/oxbuildkey.pub

−

gpgcheck=1

+

enabled=1

−

metadata_expire=0m

+

gpgcheck=1

−

+

metadata_expire=0m

−

+

−

# if you have a valid maintenance subscription, please uncomment the

+

# if you have a valid maintenance subscription, please uncomment the

−

# following and add the ldb account data to the url so that the most recent

+

# following and add the ldb account data to the url so that the most recent

Update of Open-Xchange Server v6.20 to v6.22 on CentOS5

This article will guide you through the update of an existing Open-Xchange Server 6 installation to the newest major release, v6.22.

Supported update path

Please note that the update to v6.22 is only supported from an installed version 6.20.7 or later. If you have an earlier version of Open-Xchange Server 6 installed, please update to the latest release of v6.20 before attempting an update to v6.22.

The latest v6.20 release will remain accessible on our servers. If you need to access the repository after the release of v6.22, please use the following lines in your yum repository configuration to access v6.20 packages:

Start a console and create a software repository file for Open-Xchange:

Please note that frontend and backend packages are now provided from two different repositories. Depending on your setup and the packages installed on the specific system you're updating it is possible that you only need one of these repositories. All packages providing open-xchange-admin functionality are included in the backend repository.

Updating repositories and update packages

Reload the package index:

$ apt-get update

Download and update all installed packages:

$ apt-get dist-upgrade

Install additional language packages if necessary

Starting with v6.22 the localization files for German, French and British English are no longer part of the core packages. This change was necessary to allow customers to uninstall these languages when they are not needed. If you want to offer German, French and/or British English to your customers as language option, you need to install the corresponding packages after the update.

For German:

$ apt-get install open-xchange-l10n-de-de open-xchange-gui-l10n-de-de

For French:

$ apt-get install open-xchange-l10n-fr-fr open-xchange-gui-l10n-fr-fr

For British English:

$ apt-get install open-xchange-l10n-en-gb open-xchange-gui-l10n-en-gb

Restart Open-Xchange

To restart Open-Xchange Server after the update, run

$ /etc/init.d/open-xchange restart

This script will check on startup if the old processes for open-xchange-groupware and open-xchange-admin are running, and stops them if they are. You might still want to check with

$ ps aux | grep open-xchange

that there is now only one process running Open-Xchange Server.

Leftover configuration files and runtime data

After the update you may see leftover configuration files and runtime data below /opt/open-xchange/etc.

Some of these files belong to packages which have been uninstalled during the update, they are marked with the status rc in the output of dpkg -l. You can remove these packages with the command

$ dpkg --purge <packagename>

Other orphaned files may be runtime data or temporary files which do not belong to any package and therefore couldn't be removed during the package update.

Finally, there may be backup files created by the package manager during earlier updates.