This article describes how to update to a newer version. To identify the versions of the application being upgraded, see Release Version Numbering.
If you are running a version of with a release date prior to 2017_01 or 2019_01, you must install a minimum required version of before you can upgrade to the current version.
In general, the update process has the following steps:
There are three ways to run the update process:
Before you upgrade on a Windows server:
C:\Agiloft\bin\ew-control.exe -a restart
If you don't install every new version as it's released, you might need to upgrade to a minimum required version before proceeding to the current version of . Review the list below and start by installing the earliest version of that you don't yet have. You might need to install multiple minimum versions before you can upgrade to the current version of . For example, if you're running version 2016_02 and want to upgrade to 2019_02, you must install 2017_01, then 2019_01, then 2019_02.
If you're running a version of with a release date prior to 2019_01, you must upgrade to the 2019_01 release before installing a later version.
Download the 2019_01 installer package from https://www.agiloft.com/ewdownload/upgrade/ and upgrade your system to 2019_01.
You cannot upgrade to version 2019_01 using the in-system Software Update option. You must download and run the installer package to upgrade to 2019_01.
After the successful upgrade, upgrade to the current version of , releases 2019_02 and later.
If you're running a version of with a release date prior to 2017_01, you must upgrade to the 2017_01 release before installing a later version.
The online update option is the simplest method.
If you aren't installing for the first time, you can update the software by simply downloading and installing the latest version. The latest official release of can be found at https://www.agiloft.com/ewdownload/.
The EWUpdate utility works the same way as the manual installer, but runs from the command line. If you run the utility with no options, it performs an update with all default options selected. If you need to change the options for the utility, use the command line options listed below.
Command Line Options
These options are available in the manual installer and in the EWUpdate command line utility. Default options can be changed using the command-line options listed, which correspond to the options presented in the installer. The list below consists of the most commonly recommended options.
Corresponding ewupdate command-line option
Backup database data using OS-level backup
This command only applies if the built-in MySQL server is used. Under normal circumstances a full OS-level backup is made. Use this option to skip the default OS-level backup of the MySQL directory. No database restoration is possible if the upgrade fails.
Skip checkers unless any patchers were run
When the application server starts, it performs data checks for consistency, which might take a long time. Use this option to skip data checking if no data was changed on update. This can speed the time taken to start the application server.
Skip project backup if possible
At the very beginning of the update process all existing projects are saved to the backup directory. If this option is set then no project backup is performed, if allowed. Some update modes require a project backup, in which case it isn't skipped.
Don't delete temporary files after update
During the update, temporary files are normally stored on the hard drive. These may include data backups, unpacked new code, etc. By default, temporary files are removed after an update. If this option is set, temporary files are left on the device. The temporary files are automatically deleted before the next update.
Don't backup temporary files - logs etc
If this option is set then no temporary files such as log files are backed up before the update. This saves used disk space and shortens the update time.
For additional update options, use the –help command to print a full list of commands.
Example: ewupdate --stable -s,--stable Download stable release version (Offical Release) -l,--latest Download latest release version (Beta) -d,--devel Download development version (Alpha) -C,--custom <host> Download from custom server -F,--file <file> Upgrade from a distribution that has already been downloaded to the local hard drive -f,--force Unattended update, all prompts are answered 'yes' -c,--caution Unattended update, all prompts are answered 'no' -k,--skiposlevel Skip OS level backup (avoid using this when skipping project backup) -K,--skipprjbckp Skip project backups (avoid using this when skipping OS level backup) -t,--keeptemp Keep temp files -p,--scup Skip checkers unless patchers were run -i,--backuptemp Backup temporary files such as logs (when unattended mode) -r,--requiredspace <Gb> Disk space (Gb) required for update (use with care) -w,--warn <MMM or MMM:NNN> Displays a warning message to customers about an impending update. Argument syntax is MMM or MMM:NNN, where MMM is the number of minutes before update and NNN is the estimated update duration in minutes -A,--allowsameversion Do update even if new version is same as old one -X,--forceincompat Forces an upgrade between releases that should not be compatible. Do not use this option. -v,--verbose Print error details -h,--help Prints this help
If the upgrade fails, the setup stops, shows an error message, and then rolls back to the pre-update version. It retains all your settings. The error message provides the installer logs, which you can use to trace the cause of the upgrade failure and resolve it before trying the upgrade again.