Updating OX App Suite packages

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. Have a look here, too: Upgrading a single node
  • If you don't have a cluster of OX nodes, then your complete installation needs to be taken down temporarily.
  • 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.

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://CUSTOMERID:PASSWORD@software.open-xchange.com/products/appsuite/stable/appsuiteui/updates/DebianWheezy/ /
deb http://CUSTOMERID:PASSWORD@software.open-xchange.com/products/appsuite/stable/backend/updates/DebianWheezy/ /
deb http://CUSTOMERID:PASSWORD@software.open-xchange.com/products/appsuite/stable/appsuiteui/updates/DebianJessie/ /
deb http://CUSTOMERID:PASSWORD@software.open-xchange.com/products/appsuite/stable/backend/updates/DebianJessie /

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://CUSTOMERID:PASSWORD@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://CUSTOMERID:PASSWORD@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)

RHEL7/CentOS7

Add the following entries to /etc/yum.repos.d/ox.repo:

[ox-updates-appsuiteui]
name=Open-Xchange Updates
baseurl=http://CUSTOMERID:PASSWORD@software.open-xchange.com/products/appsuite/stable/appsuiteui/updates/RHEL7/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

[ox-updates-backend]
name=Open-Xchange Updates
baseurl=http://CUSTOMERID:PASSWORD@software.open-xchange.com/products/appsuite/stable/backend/updates/RHEL7/
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://CUSTOMERID:PASSWORD@software.open-xchange.com/products/appsuite/stable/appsuiteui/updates/SLES11/ OXAPPSUITEUIUPDATES
$ zypper ar http://CUSTOMERID:PASSWORD@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.

SLES12

Add the updates repository to the repository list:

$ zypper ar http://CUSTOMERID:PASSWORD@software.open-xchange.com/products/appsuite/stable/appsuiteui/updates/SLE_12/ OXAPPSUITEUIUPDATES
$ zypper ar http://CUSTOMERID:PASSWORD@software.open-xchange.com/products/appsuite/stable/backend/updates/SLE_12/ 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.

Updating OX App Suite Packages for older versions

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

If you want to update an older version of Open-Xchange App Suite to the latest maintenance release, add the following entry to /etc/apt/sources.list.d/open-xchange.list. Replace VERSION with the version you are using (e.g. 7.6.2). See AppSuite:Version_Support_Committment for the currently supported versions. Also, make sure that your repository configuration points at the versioned base installation repositories (instead of using the stable symlink.)

deb http://CUSTOMERID:PASSWORD@software.open-xchange.com/products/appsuite/VERSION/appsuiteui/updates/DebianWheezy/ /
deb http://CUSTOMERID:PASSWORD@software.open-xchange.com/products/appsuite/VERSION/backend/updates/DebianWheezy/ /
deb http://CUSTOMERID:PASSWORD@software.open-xchange.com/products/appsuite/VERSION/appsuiteui/updates/DebianJessie/ /
deb http://CUSTOMERID:PASSWORD@software.open-xchange.com/products/appsuite/VERSION/backend/updates/DebianJessie /

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

If you want to update an older version of Open-Xchange App Suite to the latest maintenance release, add the following entry to /etc/yum.repos.d/ox.repo. Replace VERSION with the version you are using (e.g. 7.4.2, 7.6.0). See AppSuite:Version_Support_Committment for the currently supported versions. Also, make sure that your repository configuration points at the versioned base installation repositories (instead of using the stable symlink.)

[ox-updates-appsuiteui]
name=Open-Xchange Updates
baseurl=http://CUSTOMERID:PASSWORD@software.open-xchange.com/products/appsuite/VERSION/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://CUSTOMERID:PASSWORD@software.open-xchange.com/products/appsuite/VERSION/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

If you want to update an older version of Open-Xchange App Suite to the latest maintenance release, add the following entry to the repository list. Replace VERSION with the version you are using (e.g. 7.4.2, 7.6.0). See AppSuite:Version_Support_Committment for the currently supported versions. Also, make sure that your repository configuration points at the versioned base installation repositories (instead of using the stable symlink.)

$ zypper ar http://CUSTOMERID:PASSWORD@software.open-xchange.com/products/appsuite/VERSION/appsuiteui/updates/SLES11/ OXAPPSUITEUIUPDATES
$ zypper ar http://CUSTOMERID:PASSWORD@software.open-xchange.com/products/appsuite/VERSION/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.