The new Open-Xchange Server v6.22 is the first step on the way to the next generation Open-Xchange App Suite. The update provides a new and improved Open-Xchange Server backend with enhancements for both generations.
Especially on the backend, Open-Xchange implemented various changes and improvements like a new and clear structure for the configuration files and packages, an improved exception framework, unified OSGi, etc.
On this page you can find an overview of the differences between the Open-Xchange 6.20.x and the Open-Xchange v.6.22 backend. There are new requirements, update guides, and multiple other changes.
Please read the different articles and manuals regarding the update. We encourage administrators of Open-Xchange 6 v6.20.x to install this update. The further feature development will be based on v6.22
Custom Packages: Unfortunately custom packages will not be ready with 6.22 release. If you have custom packages provided by Open-Xchange, please discuss with your Open-Xchange contact when these packages will be available for 6.22.
Custom Plugins: If you have custom plugins written by yourself which depend on Open-Xchange Server OSGI bundles please check the information about necessary code and packaging changes below.
Furthermore, Open-Xchange provides the complete v6.22 materials as a document which is available here: Software Repository.
|Old version||New version||Update supported|
(1) If you don't update to 6.20.7 before you start the 6.22 update, it is possible that some important scripts have not run on your system(s) and configuration options might be missing. If you have already updated to 6.22 from an v6.20 version earlier than 6.20.7 and you are experiencing problems, please contact Open-Xchange Support.
Please note that after updating to 6.22 there is no way to get back to an earlier version of Open-Xchange. Please make sure that you have a full backup of your Open-Xchange installation(s).
If you have several Open-Xchange systems in a cluster setup, you need to shut down all of them before attempting the upgrade. Parallel operation of v6.20 and v6.22 nodes in one cluster may lead to unforeseen errors and is not supported even for a short time.
|Open-Xchange GUI / Clients||Open-Xchange Server||Supported|
|Older versions of Open-Xchange GUI||v6.22.x|
|OXtender 2 for Microsoft Outlook||v6.22.x|
|OXtender for Business Mobility||v6.22.x|
|Open-Xchange Web Interface v1.2||v6.22.x|
|OXtender for cPanel||v6.22.x|
|OXtender 1 for Microsoft Outlook|
|OXtender for SyncML|
|Parallels Operations Automation||(Supported with upcoming 6.22.1, Q4 2012)|
Open-Xchange provides an overview page regarding the main improvements of the new v6.22. Please have a look at Backend Improvements 6.22
In v6.22 we simplified the directory tree containing all configuration files to not longer include the subdirectories
For more details see the packaging changes overview page.
If you have any configuration management or templating system for automatic deployment of OX instances in place, theses changes mean that you will have to adapt that system to the new configuration file tree.
With the consolidation of the admin process and the groupware process in 6.22 we also consolidated the former splitted RMI libraries. So the files
/opt/open-xchange/lib/ox_admin_hosting_rmiclient.jar were combined into the file
This means that you have to adjust your software to use the new library if you use the RMI interface.
With v6.22 we have significantly reduced the number of packages necessary to install Open-Xchange Server. We encourage administrators of Open-Xchange v6.20.x to read the article Package changes with 6.22 before updating to Open-Xchange v6.22. This article describes in detail which new packages correspond to which old ones.
The changes in the package structure should be completely transparent to the system administrator and are handled by standard package management tools during the upgrade.
If you have any custom system for automatic installation and deployment of OX instances in place, it is very likely that you need to adapt your system to the new package structure.
The package open-xchange-upsell-generic has been dropped for this release. An update will replace the package with open-xchange-upsell-multiple which offers the same features. The configuration needs to be converted though:
The URL must point to an HTML document which holds the content previously defined in upsell.properties' modules/com.openexchange.upsell.generic/html.
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. Please see the update guide for your distribution for details.
Admin functionality will now be a part of the Groupware Process as optional bundle. This means the former, as root running, Admin daemon will no longer exist.
Admin functionality is only available when the corresponding packages are installed.
As a result of this change, there is now only one startup script which starts the Open-Xchange Server. The new unified process is called
Following are potential pitfalls :
The changes of the configuration files for the administration daemon are described in Administration daemon configuration changes for 6.22.
To update the software to Open-Xchange v6.22, please use the following Update Guides. There you can also find information on how to start the groupware with / without admin part, on known issues and manual steps required.
To download and install the software, please use the following Installation Guides.
Open-Xchange will discontinue the support for OXtender 1 for Microsoft Outlook with the new release v6.22. Additional, at the new backend, the Open-Xchange WebDAV XML API will no longer be officially supported. Open-Xchange will provide an upgrade path to the OXtender 2 for Microsoft Outlook.
If the user installs the upcoming OLOX1 6.18.19 we will provide the following information to the user when trying to sync against the OX server >= 6.22. Open-Xchange provides via a pop-up window at the product the following migration possibilities:
If the user closes the pop-up window, the OLOX 1 will be deactivated for the current session and profil. After installing OLOX2 and starting Outlook the user has to select the new OLOX2 profile and the migration is done.
A complete migration path is documented at http://oxpedia.org/wiki/index.php?title=OLOX_Migration
old 6.20 admin daemon still running, shutting down... done
old 6.20 groupware still running, shutting down...
In that case, remove the pidfile(s):
rm -f /var/run/open-xchange-admindaemon.pid; rm -f /var/run/open-xchange-groupware.pid