AppSuite:UpdatingOXPackages

Updating OX App Suite packages

This article describes how to update OX App Suite packages from one service pack to another.

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.

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

| NOTE: Please take care, that you do not restart Open-Xchange during the process where it updates it's database. 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.

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

| NOTE: Please take care, that you do not restart Open-Xchange during the process where it updates it's database. 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.

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

| NOTE: Please take care, that you do not restart Open-Xchange during the process where it updates it's database. 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.