Patch Installation Requirements
The patch 7.0.0 can only be applied to the previous ePages version.
Note
|
The patch 7.0.0 works only on Linux, not on Windows. |
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. Execute as Linux user root:
/etc/init.d/epages6 start_db
Stop all non-ePages applications (e.g. editors) that access files in directory $EPAGES.
Important
|
Backup your data to be able to restore the initial state if the patch process fails or causes inconsistencies with customizations. The patch itself does not backup any data (neither databases nor files). |
Patching requires internet connection to outside, at least HTTP and FTP clients must be able to download files from the internet.
Move all log files from $EPAGES_LOG/* to a backup directory.
If errors occur, stop the patch process, check the log file and contact ePages support. The log files are located in (HOSTNAME is the name of the machine):
$EPAGES_SHARED/Patches/var-patch_7_0_0/logs/HOSTNAME/*.log
Patch a Single Server ePages Installation
In Linux execute the following steps as Linux user root.
Red Hat: Patching with YUM Repository
Single server installations on Red Hat Linux may be patched by executing following commands:
rpm -hUv http://epages.com/repo/epages/yum/epages-release.noarch.rpm
/var/epages/update-epages.sh --singlehost
Debian: Patching with APT Repository
Single server installations on Debian Linux may be patched by executing following commands:
curl -O http://www.epages.com/repo/epages/apt/epages-release_all.deb
dpkg -i epages-release_all.deb
apt-get -y update
/var/epages/update-epages.sh --singlehost
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.
Execute the following steps on the servers as defined.
Execute the following steps as Linux user root.
Download and Unpack the Package on All Servers
On each server (one after the other, not parallel), run following commands for your operating system.
Red Hat: Download and Unpack the Package
Run following commands:
rpm -hUv http://epages.com/repo/epages/yum/epages-release.noarch.rpm
/var/epages/update-epages.sh --distributed
Debian: Download and Unpack the Package
Run following commands:
curl -O http://www.epages.com/repo/epages/apt/epages-release_all.deb
dpkg -i epages-release_all.deb
apt-get -y update
/var/epages/update-epages.sh --distributed
Initial Preparation on Secondary Servers
Run the following command on each secondary server:
echo "$(hostname)=beta" >> Conf/Hosts
Initial Preparation on the Alpha Server
Run the following commands on the alpha server:
echo "$(hostname)=alpha" >> Conf/Hosts
./patch.sh prepare
Pre-Installation on Secondary Servers
Run the following command on all secondary servers:
./patch.sh preinstall
Install the Patch on the Alpha Server
Run the following command on the alpha server:
./patch.sh install
Post-Installation on Secondary Servers
Run the following command on all secondary servers:
./patch.sh postinstall
Re-Open Stores on the Alpha Server
Run following command on the alpha server:
./patch.sh reopen
Final Tasks
Changed File Config/Scheduler.conf
The patch changes the configuration file $EPAGES_CONFIG/Scheduler.conf. Check after the patch if the changed values are correct for you.
You’ll find the changes in following file:
-
$EPAGES_PATCHES/patch_7_0_0/Conf/ConfigurationFiles/imp_Scheduler_7_0_0.conf
The original configuration file is stored in:
-
$EPAGES_PATCHES/var_patch_7_0_0/backup/$(hostname)/Shared/Config/Scheduler.conf
Read Patch Log Files
Verify the log files of the patch process. The log files are located in (HOSTNAME is the name of the machine):
$EPAGES_SHARED/var-patch_7_0_0/logs/HOSTNAME/*.log
Beside the patch log files, the patch process writes errors as well into the ePages standard log files in $EPAGES_LOG/*. Verify log files in $EPAGES_LOG/* as well, especially file error.log. In error.log ignore following warning(s):
Can't connect to the MC at ..
The warning is written because the ePages service must not run while patch installation.
Purge Outdated Files
After successful installation of the patch, following outdated files exist:
-
$EPAGES_CONFIG/StoreTypes.d/OLD_VERSION
-
$EPAGES_SHARED/Static/*
-
$EPAGES_WEBROOT/StoreTypes/OLD_VERSION
These outdated files must be removed by excuting following command on any involved machine:
./patch.sh cleanup
Configure Web Services for Multistore Installations
After patching a Multistore installation web services must be configured in the PBO.
Edit the PBO settings by replacing values in <brackets> as shown below:
-
Changes in PBO of MasterDB: Go to Shops >> MASTERSHOPNAME >> Tab: MultiStore and edit:
Site - WebService URL: 'http://<Domain>/epages/Site.soap' Site - WebserviceUser: '/Users/wsadmin' Site - WebservicePassword: 'wsadmin'
WebService URL: 'http://<MasterShopDomain>/epages/MASTERSHOPNAME.soap' WebserviceUser: '/Shops/MASTERSHOPNAME/Users/admin' WebservicePassword: 'admin'
-
Changes in PBO of MultiStoreDB: Go to Shops >> SUBSHOPNAME >> Tab: MultiStore and edit:
WebService URL: 'http://<SubShopDomain>/epages/SUBSHOPNAME.soap' WebserviceUser: '/Users/wsadmin' WebservicePassword: 'wsadmin'