Difference between revisions of "OX6:Update to 6 22"
(→Update and Installation Open-Xchange Server v6.22)
(→Supported Update Path)
|Line 23:||Line 23:|
|Line 40:||Line 40:|
(1) If you don't [http://oxpedia.org/wiki/index.php?title=UpdatingOXPackages 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.
(1) If you don't [http://oxpedia.org/wiki/index.php?title=UpdatingOXPackages 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. .
= Rollback =
= Rollback =
Revision as of 13:06, 4 October 2012
- 1 Update and Installation Open-Xchange Server v6.22
- 2 Supported Update Path
- 3 Rollback
- 4 Supported Server / Client Combinations
- 5 Improvements Overview of 6.20.x to 6.22 Backend
- 6 Configuration Changes
- 7 Packages changes
- 8 Dropped packages
- 9 No separate admin daemon
- 10 Startup Scripts
- 11 Changes to programming APIs which might break custom plugins to the OX Server
- 12 Installation and Update Guide for Open-Xchange v6.22
- 13 Migration from OLOX1 to OLOX2
Update and Installation Open-Xchange Server v6.22
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.
Supported Update Path
|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. In this case 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 backup. (TODO)
Supported Server / Client Combinations
Open-Xchange Database Support (Parallel Setup)
|Open-Xchange Database||v6.22.x||(after running v6.22 update tasks)|
|v6.20.7||(after running v6.22 update tasks)|
|v6.20.x||(after running v6.22 update tasks)|
Improvements Overview of 6.20.x to 6.22 Backend
Open-Xchange provides an overview page regarding the main improvements of the new v6.22. Please have a look at Backend Improvements 6.22
The overview page provides a list of
- unchanged config files with old and new location
- push.properties renamed to push-udp.properties
- completely new config files
- config files that do not longer exist
- merged / split config files
- config options which need to be changed and their containing files
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.
The overview page provides a list of
- new packages and metapackages with short description
- removed metapackages
- remaining metapackages and what they do
- dropped packages with their replacements
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.
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.
No separate admin daemon
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.
following are potential pitfalls :
- ox-admin-scriptconf.sh is merged to /opt/open-xchange/etc/ox-scriptconf.sh, check NRFILES and Memory setting to fit the environment.
- If /etc/security/limits.conf does set limits for the open-xchange user, those need to be adopted.
- administrative tasks are now executed as user open-xchange (for example the filestore mount is no longer accessed as root).
- The mutual process is not able to open tcp sockets below 1024.
- Monitoring for the admin process is no longer needed.
- admindaemon used to limit its network usage to IPv4 which is not the case anymore. This means that proper network setup is needed to avoid DNS and routing issues caused by dual stack usage.
The overview page provides a list of
- startup scripts
We encourage administrators of Open-Xchange v6.20.x to read the [list] before updating to Open-Xchange v6.22.
Changes to programming APIs which might break custom plugins to the OX Server
- Exception handling has changed, see Backend Improvements 6.22
- If you build your own packages, you need to change a few things, see: TODO
Installation and Update Guide for Open-Xchange v6.22
Quick Installation Guide (supported packages)
To download and install the software, please use the following Installation Guides.
- Download and Installation Guide for Debian GNU/Linux 6.0 (Squeeze)
- Download and Installation Guide for SUSE Linux Enterprise Server 11
- Download and Installation Guide for RedHat Enterprise Linux 5
- Download and Installation Guide for RedHat Enterprise Linux 6
- Download and Installation Guide for CentOS 5
- Download and Installation Guide for CentOS 6
Update Guide (supported packages)
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.
- Update Guide from 6.20 to 6.22 for Debian GNU/Linux 6.0 (Squeeze)
- Update Guide from 6.20 to 6.22 for SUSE Linux Enterprise Server 11
- Update Guide from 6.20 to 6.22 for RedHat Enterprise Linux 5
- Update Guide from 6.20 to 6.22 for RedHat Enterprise Linux 6
- Update Guide from 6.20 to 6.22 for CentOS 5
- Update Guide from 6.20 to 6.22 for CentOS 6
Migration from OLOX1 to OLOX2
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:
- User can use the OXUpdater to install the new version
- User can directly start installing by clicking on a provided link
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
- After the start of the new OLOX 2 profile, contacts, appointments and tasks will be synchronized
- Per default server configuration, mails older as one year won't be synchronized
- Notice and Journal information won't be synchronized. It is possible to export and import the information via the Outlook functionalities