loading table of contents...

4.2.3.2. Upgrade with Yum

The first step, you should do, when you want to update your system, is to find out what package updates are available. With YUM, you simply call yum list updates cm8-*

In a second step, you may check if your configuration files below /etc/coremedia are still up to date or if there are any changes required. You can do that manually by inspecting the package description for each update or you can update the packages and see if there are missing tokens. By default, the CoreMedia RPM files will check if all necessary properties are defined in the configuration file, if that already exists. If properties are missing, the package won't be installed and the missing properties will be reported on the console or in the system log at /var/log/messages.

To print out the description of an RPM, you need to execute:

yum info <PACKAGE NAME>

If for example, you execute yum info cm8-wfs-tomcat the RPM metadata will be printed and in the description, you will see a list of properties you need to define.

Name        : cm8-wfs-tomcat
Arch        : noarch
Version     : 16
Release     : 1.develop.1362133163
Size        : 17 M
Repo        : installed
From repo   : local
Description : This rpm packages cm7-wfs-tomcat.
            : revision: 20130301-1119
            : To configure this service you have to define a
            : configuration property file at
            : /etc/coremedia/cm7-wfs-tomcat.properties containing:
            : configure.CMS_DB_URL configure.CMS_HOST
            : configure.WFS_IP configure.WFS_HOST
            : configure.WFS_HEAP configure.WFS_PERM
            : configure.CMS_DB_USER configure.CMS_DB_PASSWORD

Example 4.21. Yum info


Given that your YUM configuration is correct and all packages are accessible from your YUM repositories, you have to manually proceed the following steps to upgrade your services:

  1. sudo yum update cm8-* for all CoreMedia DXP 8 packages. It is important, that you upgrade all packages within one transaction, as it makes it easier to roll back, if something went wrong.

  2. After all packages have been installed successfully, you need to restart all CoreMedia services in the same order you started them during the initial deployment.