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

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. Also the update to 6.22.0 must be installed before doing further updates to later versions.

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 commands to configure the repository containing 6.20 packages.

First, list your configured repositories:

$ zypper lr

Next, disable your existing Open-Xchange package repository. Assuming it is called ox, the command would be:

$ zypper mr -d ox

Finally, add the repository for 6.20.7 packages:

$  zypper ar http://software.open-xchange.com/OX6/6.20/SLES11/ ox-6.20

After updating your system, disable the repository again:

$ zypper mr -d ox-6.20

Instead of disabling the repositories you can also remove them with the command zypper rr.


  • An Open-Xchange Server installation v6.20.7 or later. This update guide is valid for a system installed through our Download and Installation Guide for SLES 11
  • If you have custom packages done by Open-Xchange, please discuss with your Open-Xchange contact when these packages are available for 6.22. Do not attempt the update earlier
  • If you have built custom packages yourself which install config files in the OX config tree, please check the page v6.22 Packaging Changes
  • If you have custom plugins written by yourself which depend on Open-Xchange Server OSGI bundles, check the pages v6.22 Packaging Changes and v6.22 Necessary Code Changes for changes you might need to do.
  • Custom packages built for 6.20.7 or earlier might not work with 6.22.
  • As for every update we strongly recommend that you make a backup of your system(s) before you proceed.

Update Open-Xchange Repositories

First, you need to add the current repositories to your zypper configuration to access the v6.22 packages.

To do so, start with listing your existing repositories.

$ zypper lr

Then, disable your configured Open-Xchange repositories. Assuming they are called ox and ox-updates, the commands would be:

$ zypper mr -d ox
$ zypper mr -d ox-updates

Instead of disabling the repositories, you can also remove them with zypper rr.

Finally, add the new Open-Xchange repositories for SLES11:

$ zypper ar http://software.open-xchange.com/OX6/6.22/6.22.0/frontend/SLES11/ ox-frontend 
$ zypper ar http://software.open-xchange.com/OX6/6.22/6.22.0/backend/SLES11/ ox-backend
$ zypper ar http://software.open-xchange.com/OX6/6.22/6.22.0/usm/SLES11/ ox-usm

If you have a valid maintenance subscription, please run the following command so that the most recent packages get installed:

$ zypper ar http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/6.22.0/updates/frontend/SLES11/ ox-updates-frontend
$ zypper ar http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/6.22.0/updates/backend/SLES11/ ox-updates-backend
$ zypper ar http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/6.22.0/updates/usm/SLES11/ ox-updates-usm

A warning will be shown because the Open-Xchange packages are not yet signed by a cryptographic key. To accept and continue the installation, press Y.

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. The repository usm is also only needed on backend servers.

Updating repositories and update packages

Reload the package index:

$ zypper ref

A warning will be shown because the Open-Xchange packages are not yet signed by a cryptographic key. To accept and continue the installation, press Y.

Download and update all installed Open-Xchange packages:

$ zypper dup -r ox-backend -r ox-frontend -r ox-usm

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:

$ zypper in open-xchange-l10n-de-de open-xchange-gui-l10n-de-de

For French:

 $ zypper in open-xchange-l10n-fr-fr open-xchange-gui-l10n-fr-fr

For British English:

 $ zypper in open-xchange-gui-l10n-en-gb

Adjusting runlevel configuration

Starting with v6.22 there are no longer two separate process, but only one, open-xchange. Therefore, the runlevel configuration needs to be adjusted:

$ insserv open-xchange

NOTE: Admin functionality is only available if the package open-xchange-admin is installed. If you are updating a system without admin packages installed it still won't have admin functionality after the update.

Restart Open-Xchange

To restart Open-Xchange Server after the update, run

$ rcopen-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.

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.

It is safe to remove:

  • All files and subdirectories below:

unless you have built your own packages which install files into these directories.

  • All files ending in .rpmsave or .rpmnew once you are confident that your configuration is working after the update.