ePages Patch Installation 6.15.4
Created: 6.12.2; Updated: 6.15.3

Table of Contents

1 Patch Installation Requirements

The patch 6.15.4 can only be applied to ePages 6.15.3 on Red Hat RHEL/CentOS.

Sybase ASE is no longer supported with ePages 6.15.4. You must migrate to MySQL before you can install the patch as described in Migrate Data from Sybase to MySQL.

The default MySQL database engine must be InnoDB. Check this by executing the SQL command 'SHOW ENGINES'.

In the MySQL configuration file (mostly /etc/my.cnf) option skip-networking must not be set to '1'. The default value is '0' so that you don't need to change a original configuration file.

If the ePages database server doesn't run, start it:

Windows
Start the database service MySQL
Linux
Execute as root: /etc/init.d/epages6 start_db
Stop all non-ePages applications (e.g. editors) that access files in directory %EPAGES% (Linux: $EPAGES, see /etc/default/epages6).

IMPORTANT: Backup your data to be able to restore the initial state if the patch process fails or causes inconsistencies with customizations.

For Linux the ePages repository must be updated by executing following command:

  curl http://epages-software.de/RPMS/rpmify/rpmify-epages.sh | sh

1.1 Linux: Patching with YUM Repository

On Linux servers, the patch may be installed by a RPM update if ePages is installed on a single server (not distributed over several servers).

ePages Perl 5.12.3 must be installed (as described in section User Specific Configuration), before the patch installation by RPM update may be started.

If all conditions apply, ePages may be patched by executing following command:

  yum -y update 'epages-j' --disablerepo epages-setup --enablerepo epages-update
  yum -y update 'epages-*' --disablerepo epages-setup --enablerepo epages-update

1.2 Logging the Patch Installation

Backup all log files from %EPAGES_LOG%\* (Linux: $EPAGES_LOG, see /etc/default/epages6) and delete these files in %EPAGES_LOG%.

2 Patch a Single Server ePages Installation

In Windows execute the following steps as Windows user Administrator or as a user with administrator permissions.

In Linux execute the following steps as Linux user root.

2.1 Preparations

2.1.1 Unpack the Package

Copy the file epages-6.15.4-patch.tar.gz into a local directory and unpack the patch:

Windows:

  cd /d c:\temp
  gzip -d epages-6.15.4-patch.tar.gz
  tar ixf epages-6.15.4-patch.tar
  cd patch_6_15_4

Linux:

  . /etc/default/epages6
  cd /tmp
  tar izxf epages-6.15.4-patch.tar.gz
  cd patch_6_15_4

2.1.2 User Specific Configuration

Check if all patch relevant variables in the configuration files in %EPAGES_CONFIG%\Database.d\*.conf (Linux: $EPAGES_CONFIG/Database.d/*.conf) have correct values. The variables are described in following documents:

2.2 Patch Installation

The patch can be installed in 2 steps:

prepare
Initial preparation step being executed while the store is online.
install
Patch installation being executed while the store is offline.
The first step (prepare) may be omitted, then it is executed automatically within the second step (install).

2.2.1 Initial Preparation Step

Run the following commands:

Windows:

  perl patch.pl prepare

Linux:

  ./patch.sh prepare

If errors occur, stop the patch process, check the log file and contact ePages support. The log files are located in:

Windows:

  %EPAGES_SHARED%\Patches\var-patch_6_15_4\logs\HOSTNAME\DATE-prepare.log

Linux:

  $EPAGES_SHARED/var-patch_6_15_4/logs/HOSTNAME/DATE-prepare.log

HOSTNAME is the name of the machine and DATE is the Date in the format YYYY-MMM-DD-HH.MM.SS (e.g. 2007-May-31-15.34.23).

2.2.2 Patch Execution

Run the following commands:

Windows:

  perl patch.pl install

Linux:

  ./patch.sh install

If errors occur, stop the patch process, check the log file and contact ePages support. The log files are located in:

Windows:

  %EPAGES_SHARED%\Patches\var-patch_6_15_4\logs\HOSTNAME\DATE-install.log

Linux:

  $EPAGES_SHARED/Patches/var-patch_6_15_4/logs/HOSTNAME/DATE-install.log

HOSTNAME is the name of the machine and DATE is the Date in the format YYYY-MMM-DD-HH.MM.SS (e.g. 2007-May-31-15.34.23).

3 Patch a Distributed ePages Installation

A distributed ePages installation consists of multiple servers. Exactly one of them is the primary server (hereinafter called 'alpha server') and one or more secondary servers:

Alpha server
the primary server on which the ePages service is running. If the ePages service is running on multiple servers, choose exactly one of them as your alpha server.
Secondary server(s)
All other servers of your installation with ePages-Perl installed.
The patch is installed by executing following commands:

1. on alpha server (see section Initial Preparation on the Alpha Server):

   Windows:  perl patch.pl prepare
   Linux:    ./patch.sh prepare

2. on any secondary server (see section Install the Patch on Secondary Servers):

   Windows:  perl patch.pl preinstall
   Linux:    ./patch.sh preinstall

3. on alpha server (see section Install the Patch on the Alpha Server):

   Windows:  perl patch.pl install
   Linux:    ./patch.sh install

4. on any secondary server (see section Post-Installation on All Servers):

   Windows:  perl patch.pl postinstall
   Linux:    ./patch.sh postinstall

5. on alpha server (see section Post-Installation on All Servers):

   Windows:  perl patch.pl postinstall
   Linux:    ./patch.sh postinstall

The first step (prepare) consists of preparation tasks being executed while the store is online.

Other steps must be executed while the store is offline.

The first step (Initial Preparation on the Alpha Server) may be omitted, then it is executed automatically within the third step (Install the Patch on the Alpha Server).

3.1 Initial Preparation on the Alpha Server

On the alpha server run the initial preparation steps as described in sections Preparations and Initial Preparation Step.

3.2 Install the Patch on Secondary Servers

In Windows, execute the following steps as a user with administration permissions (Administrator or another user of local admin group on Windows systems).

In Linux execute the following steps as Linux user root.

1. First, prepare all secondary servers for patch installation as described in section Preparations.

2. Run on all secondary servers following commands:

Windows:

  perl patch.pl preinstall

Linux:

  ./patch.sh preinstall

If errors occur, stop the patch process, check the log file and contact ePages support. The log files are located in:

Windows:

  %EPAGES_SHARED%\Patches\var-patch_6_15_4\logs\HOSTNAME\DATE-preinstall.log

Linux:

  $EPAGES_SHARED/Patches/var-patch_6_15_4/logs/HOSTNAME/DATE-preinstall.log

HOSTNAME is the name of the machine and DATE is the date in the format YYYY-MMM-DD-HH.MM.SS (e.g. 2007-May-31-15.34.23).

3.3 Install the Patch on the Alpha Server

If you executed step Initial Preparation on the Alpha Server, now run the patch installation on the alpha server as described in section Patch Execution.

If you did not execute step Initial Preparation on the Alpha Server, run the patch installation on the alpha server as described in sections Preparations and Patch Installation.

3.4 Post-Installation on All Servers

In Windows, execute the following steps as a user with administration permissions (Administrator or another user of local admin group on Windows systems).

In Linux execute the following steps as Linux user root.

Run following commands first on the secondary servers, then on the alpha server:

Windows:

  perl patch.pl postinstall

Linux:

  ./patch.sh postinstall

If errors occur, stop the patch process, check the log file and contact ePages support. The log files are located in:

Windows:

  %EPAGES_SHARED%\Patches\var-patch_6_15_4\logs\HOSTNAME\DATE-postinstall.log

Linux:

  $EPAGES_SHARED/Patches/var-patch_6_15_4/logs/HOSTNAME/DATE-postinstall.log

HOSTNAME is the name of the machine and DATE is the date in the format YYYY-MMM-DD-HH.MM.SS (e.g. 2007-May-31-15.34.23).

4 Final Tasks

4.1 Changed File Config/Scheduler.conf

The patch changes the configuration file %EPAGES_CONFIG%\Scheduler.conf (Linux: $EPAGES_CONFIG/Scheduler.conf). Check after the patch if the changed values are correct for you.

You'll find the changes in following file:

The original configuration file is stored in:

4.2 Read Patch Logging

Verify the log files for errors in %EPAGES_LOG%\*, especially file error.log. In error.log ignore following warning:

  Can't connect to the MC at ..

The warning is written because the ePages service must not run while patch installation.

4.3 Purge Outdated Files

After successful installation of the patch, following outdated files exist:

These outdated files must be removed by excuting following command on any involved machine:

Windows:

  perl patch.pl cleanup

Linux:

  ./patch.sh cleanup


Copyright ePages GmbH 2013