AppSuite:UpdatingOXPackages: Difference between revisions
No edit summary |
(added cluster warning, grouped warnings at the top.) |
||
| Line 1: | Line 1: | ||
= Updating OX App Suite packages = | <div class="title">Updating OX App Suite packages</div> | ||
''Synopsys'': This article describes how to update OX App Suite packages from one service pack to another. | |||
== Warnings == | |||
Before we begin, here are several things that you should keep in mind: | |||
* If you are updating a cluster, please do it one node after the other. Turn the node off, update, turn it on again, make sure it works in the cluster. | |||
* Please ''update the frontend before the backend''. Otherwise the old frontend won't work with the new backend and it's manifests. | |||
* Please ''do not restart Open-Xchange during the database update''. A database update can happen after installing minor or major updates. As soon as the first user tries to log in to the system or if any provisioning action is done, this update starts. | |||
== How to get updates? == | == How to get updates? == | ||
| Line 15: | Line 23: | ||
= Updating OX App Suite Packages = | = Updating OX App Suite Packages = | ||
== Installing Updates == | == Installing Updates == | ||
A new service pack usually introduces new packages and requires configuration changes. To get all required new packages and configuration changes, the following '''must''' be done when installing updates. | A new service pack usually introduces new packages and requires configuration changes. To get all required new packages and configuration changes, the following '''must''' be done when installing updates. | ||
(Please, keep the [[#Warning|warning about frontend updates before backend updates]] in mind) | |||
=== On Debian based distributions === | === On Debian based distributions === | ||
| Line 42: | Line 49: | ||
<pre>$ /etc/init.d/open-xchange restart</pre> | <pre>$ /etc/init.d/open-xchange restart</pre> | ||
=== On RPM based distributions === | === On RPM based distributions === | ||
| Line 77: | Line 81: | ||
<pre>$ /etc/init.d/open-xchange restart</pre> | <pre>$ /etc/init.d/open-xchange restart</pre> | ||
(Please, keep the [[#Warnings|warning about database updates]] in mind) | |||
==== SLES11 ==== | ==== SLES11 ==== | ||
| Line 102: | Line 104: | ||
<pre>$ rcopen-xchange restart</pre> | <pre>$ rcopen-xchange restart</pre> | ||
(Please, keep the [[#Warnings|warning about database updates]] in mind. | |||
[[Category: OX7]] | [[Category: OX7]] | ||
Revision as of 13:46, 26 August 2013
Synopsys: This article describes how to update OX App Suite packages from one service pack to another.
Warnings
Before we begin, here are several things that you should keep in mind:
- If you are updating a cluster, please do it one node after the other. Turn the node off, update, turn it on again, make sure it works in the cluster.
- Please update the frontend before the backend. Otherwise the old frontend won't work with the new backend and it's manifests.
- Please do not restart Open-Xchange during the database update. A database update can happen after installing minor or major updates. As soon as the first user tries to log in to the system or if any provisioning action is done, this update starts.
How to get updates?
OX App Suite updates can be accessed by customers with a valid license.
Have a look at the article: How to create an OXAccount and unlock Keys within the License Database for more information about how to create an account in the LDB.
In addition, you need to configure the OXReportClient.
Updating OX App Suite Packages
Installing Updates
A new service pack usually introduces new packages and requires configuration changes. To get all required new packages and configuration changes, the following must be done when installing updates.
(Please, keep the warning about frontend updates before backend updates in mind)
On Debian based distributions
Add the following entry to /etc/apt/sources.list.d/open-xchange.list
deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/products/appsuite/stable/appsuiteui/updates/DebianSqueeze/ / deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/products/appsuite/stable/backend/updates/DebianSqueeze/ /
Then run
$ apt-get update $ apt-get dist-upgrade
If you want to see, what apt-get is going to do without actually doing it, you can run:
$ apt-get dist-upgrade -s
After the new packages are installed, the open-xchange process needs a restart:
$ /etc/init.d/open-xchange restart
On RPM based distributions
RHEL6/CentOS6
Add the following entries to /etc/yum.repos.d/ox.repo:
[ox-updates-appsuiteui] name=Open-Xchange Updates baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/products/appsuite/stable/appsuiteui/updates/RHEL6/ gpgkey=http://software.open-xchange.com/oxbuildkey.pub enabled=1 gpgcheck=1 metadata_expire=0m [ox-updates-backend] name=Open-Xchange Updates baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/products/appsuite/stable/backend/updates/RHEL6/ gpgkey=http://software.open-xchange.com/oxbuildkey.pub enabled=1 gpgcheck=1 metadata_expire=0m
and run
$ yum update
$ yum upgrade
After the new packages are installed, the open-xchange process needs a restart:
$ /etc/init.d/open-xchange restart
(Please, keep the warning about database updates in mind)
SLES11
Add the updates repository to the repository list:
$ zypper ar http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/products/appsuite/stable/appsuiteui/updates/SLES11/ OXAPPSUITEUIUPDATES $ zypper ar http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/products/appsuite/stable/backend/updates/SLES11/ OXBACKENDUPDATES
and run
$ zypper dup -r OXAPPSUITEUIUPDATES $ zypper dup -r OXBACKENDUPDATES
You might need to run
$ zypper ref
to update the repository metadata before running zypper up.
After the new packages are installed, the open-xchange process needs a restart:
$ rcopen-xchange restart
(Please, keep the warning about database updates in mind.