There are three editions of ELMA: Community, Standard, and Enterprise (to learn more about each edition, follow this link). The process of updating these versions is identical.
When you run the installation software, the User Account Control dialog box may be displayed; click Yes to start installing updates.
Select the language that will be used in the installation process:
If ELMA Designer is running, the installation software will display a notification that it needs to be closed. Close ELMA Designer and restart the installation software.
Updating ELMA includes the following steps:
Step 1. On the start screen of the wizard confirm that you wish to install updates by clicking Next.
If possible, close all the running applications before clicking Next.
Step 2. Read the license agreement. After that, select I accept the agreement. Click Next to continue.
Step 3. Check the installation folder and type: “Update”. Confirm the installation parameters by clicking Install; to go to the previous step, click Back or cancel the installation.
Step 4. Wait until updates are installed on your PC. This process may take a while. Once all the files have been copied, the next step will open automatically.
To complete the installation, click Finish.
The installed version of the system will be displayed in the ELMA Designer authentication window:
The version number will be displayed in the Web Application authentication window as well:
When updating ELMA, remember that:
- Custom notification templates are replaced with default templates in the folder ..\UserConfig\Notifications. The replaced custom templates are saved in the folder ..\UserConfig\Notifications\Old\<system version number>, while the templates of the current system version are stored in the folder ..\UserConfig\Notifications\Original\<current system version number>.
To restore a custom template, copy the content of the required template (.xml file) and paste it to the current template (file with the same name).
- If triggers were created in the database, they will be reset after updating. Because of this, you need to manually create triggers again by running the earlier saved query via the database manager.
In some cases, after updating the system the following issue may occur: when converting a database, the transaction log size may increase by several times and take up all the disk space on the database server. In this case, the update process will be interrupted.
To solve this issue, log truncation is required when working with MSSQL. To learn more about managing the transaction log, follow these links: https://msdn.microsoft.com/en-us/library/ms190440(v=sql.105).aspx or https://support.microsoft.com/en-us/kb/873235.
If you use Firebird, the transaction log is automatically cleared during its backup copying or after full backup copying and consequent restoring or the database. Therefore, to solve the issue of increasing transaction log size, plan and configure backup copying of the database and the transaction log.
This article provides advice on updating ELMA and covers the main issues that occur when updating.