ePages Patch Installation | → 6.15.1 | Created: 6.12.2; Updated: 6.15.1 |
Table of Contents |
The patch 6.15.1 can only be applied to ePages 6.15.0.
Sybase ASE is no longer supported with ePages 6.15.1. 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:
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.com/RPMS/rpmify/rpmify-epages.sh | sh
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:
Red Hat RHEL/CentOS:
yum -y update 'epages-*' --disablerepo epages-setup --enablerepo epages-update
SuSE SLES (check if you really want to update all packages as in list-updates):
zypper mr -e epages-update zypper clean -a zypper list-updates zypper update zypper mr -d epages-update
Backup all log files from %EPAGES_LOG%\* (Linux: $EPAGES_LOG, see /etc/default/epages6) and delete these files in %EPAGES_LOG%.
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.
Copy the file epages-6.15.1-patch.tar.gz into a local directory and unpack the patch:
Windows:
cd /d c:\temp gzip -d epages-6.15.1-patch.tar.gz tar ixf epages-6.15.1-patch.tar cd patch_6_15_1
Linux:
. /etc/default/epages6 cd /tmp tar izxf epages-6.15.1-patch.tar.gz cd patch_6_15_1
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:
The patch can be installed in 2 steps:
Run the following commands:
Windows:
perl patch.pl prepare
Linux:
. /etc/default/epages6 ./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_1\logs\HOSTNAME\DATE-prepare.log
Linux:
$EPAGES_SHARED/var-patch_6_15_1/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).
Run the following commands:
Windows:
perl patch.pl install
Linux:
. /etc/default/epages6 ./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_1\logs\HOSTNAME\DATE-install.log
Linux:
$EPAGES_SHARED/Patches/var-patch_6_15_1/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).
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:
1. on alpha server (see section Initial Preparation on the Alpha Server): 1. on alpha server (see section Initial Preparation on the Alpha Server):
2. on alpha server (see section Initial Preparation on the Alpha Server):
Windows: perl patch.pl prepare Linux: ./patch.sh prepare
3. on any secondary server (see section Install the Patch on Secondary Servers):
Windows: perl patch.pl preinstall Linux: ./patch.sh preinstall
4. on alpha server (see section Install the Patch on the Alpha Server):
Windows: perl patch.pl install Linux: ./patch.sh install
5. on any secondary server (see section Post-Installation on All Servers):
Windows: perl patch.pl postinstall Linux: ./patch.sh postinstall
6. 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).
On the alpha server run the initial preparation steps as described in sections Preparations and Initial Preparation Step.
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:
. /etc/default/epages6 ./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_1\logs\HOSTNAME\DATE-preinstall.log
Linux:
$EPAGES_SHARED/Patches/var-patch_6_15_1/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).
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.
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:
. /etc/default/epages6 ./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_1\logs\HOSTNAME\DATE-postinstall.log
Linux:
$EPAGES_SHARED/Patches/var-patch_6_15_1/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).
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:
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.