Always make a backup of your database before applying an upgrade.
Use the backup & restore functionality in eHour or use the backup features of your database.
Upgrading from 1.4.2 to 1.4.3
First, follow the installation instructions for a new install except for the the database steps; do not re-install your database.
eHour 1.4.2 requires Java 7 and Apache Tomcat 7 (or any other container supporting the servlet 3 spec).
After installation perform these steps:
1.From eHour 1.4.2's home directory, copy the following files to eHour 1.4.3's home directory.
| eHour 1.4 | eHour 1.4 |
|---|---|
| conf/ehour.properties | conf/ehour.properties |
2.Copy the 1.4.3 WAR file to Tomcat's webapps folder. Yes, the normal way of deploying with Tomcat.
3. Restart Apache Tomcat
Database update required when upgrading to 1.4.2
Take note when you're upgrading from 1.4.1 you need to apply the database update scripts for MySQL or PostgreSQL.
When upgrading from 1.4.2 and the upgrade script failed on your MySQL db, then you need to run the v1.4.1 to v1.4.3 script.
Upgrading from 1.4.1 to 1.4.2
First, follow the installation instructions for a new install except for the the database steps; do not re-install your database.
eHour 1.4.2 requires Java 7 and Apache Tomcat 7 (or any other container supporting the servlet 3 spec).
After installation perform these steps:
1.From eHour 1.4.1's home directory, copy the following files to eHour 1.4.2's home directory.
| eHour 1.4 | eHour 1.4 |
|---|---|
| conf/ehour.properties | conf/ehour.properties |
2. Make sure to add the database configuration to the ehour.properties file. In previous versions this configuration was located in the ehour.xml file but with 1.4.2 it moved to the ehour.properties file.
3.Remove the conf/Catalina/localhost/ehour.xml file from Tomcat's installation directory as the database configuration is now done in the ehour.properties file
4.Copy the 1.4.2 WAR file to Tomcat's webapps folder. Yes, the normal way of deploying with Tomcat.
5. Restart Apache Tomcat
Database update required when upgrading to 1.4.2
Take note when you're using MySQL or PostgreSQL a database upgrade is required.
Upgrading from 1.3 to 1.4
Follow the installation instructions for a new install but do not re-install your database.
From eHour 1.3's home directory, copy the following files to eHour 1.4's home directory:
| eHour 1.3 | eHour 1.4 |
|---|---|
| conf/ehour.properties | conf/ehour.properties |
Restart Apache Tomcat
You can upgrade from version 0.9.1 straight to 1.4. When upgrading an older version than 0.9.1, please first upgrade to 0.9.1.
Database update required when upgrading to 1.4
Take note that a database update is required when you are upgrading to version 1.4 and using MySQL or PostgreSQL.
Upgrading from 1.x to 1.3
Follow the installation instructions for a new install but do not re-install your database.
From eHour 1.x's home directory, copy the following files to eHour 1.3's home directory:
| eHour 1.x | eHour 1.3 |
|---|---|
| conf/ehour.properties | conf/ehour.properties |
Restart Apache Tomcat
You can upgrade from version 0.9.1 straight to 1.3. When upgrading an older version than 0.9.1, please first upgrade to 0.9.1.
Database update required when upgrading to 1.3
Take note that a database update is required when you are upgrading to version 1.3 and using MySQL or PostgreSQL.
Upgrading from a version older than 1.2.1
Due to a change in how the configured locale and currency is stored, you may need to reset the used currency and language. In eHour go to System -> Configure eHour -> Localization tab and set the locales to your preferred values.
Upgrading from 0.9.1 to 1.0
Follow the installation instructions for a new install but do not re-install your database.
From eHour 0.9.1's home directory, copy the following files to eHour 1.0's home directory:
| eHour 0.9.1 | eHour 1.0 |
|---|---|
| conf/ehour.properties | conf/ehour.properties |
Restart Apache Tomcat
Upgrading from 0.8.4 to 0.9.1
There are some significant changes between the way 0.8.4 and 0.9.1 is deployed. To upgrade 0.8.4 to 0.9.1, do a fresh install of 0.9.1 using the installation instructions but skip the Database setup part.
Take note that when you're running eHour as a Windows service you need to uninstall the 0.8.4 service first using the eHour-uninstallService.bat script in eHour's 0.8.4 directory.
Upgrading from 0.8.3 to 0.8.4
In the sql/mysql/upgrade directory of the distribution there is an update.v0_8.3_to_v0.8.4.mysql.sql script, execute that on your 0.8.3 database to upgrade the tables:
mysql ehour -u user -p < update_v0.8.3_to_v0.8.4.mysql.sql
Copy the ehour-0.8.4.war to your tomcat deploy directory. Update the version number of the war file in the ehour.xml (conf/Catalina/localhost/ehour.xml) and restart Tomcat.
After you restarted Tomcat and you still end up in the previous version, delete the ehour directory in Tomcat's webapps dir.
Take note that when you're running eHour as a Windows service you need to uninstall the service first using the eHour-uninstallService.bat script.
Upgrading from 0.8.2 to 0.8.3
For the audit and configurable logo's a few modifications need to be made to the database.
In the sql directory of the distribution there is an update.v0_8.2_to_v0.8.3.mysql.sql script, execute that on your 0.8.2 database to upgrade the tables:
mysql ehour -u user -p < update_v0.8.2_to_v0.8.3.mysql.sql
Copy the ehour-0.8.3.war to your tomcat deploy directory. Update the version number of the war file in the ehour.xml (conf/Catalina/localhost/ehour.xml) and restart Tomcat.
After you restarted Tomcat and you still end up in the previous version, delete the ehour directory in Tomcat's webapps dir.
Take note that when you're running eHour as a Windows service you need to uninstall the service first using the eHour-uninstallService.bat script.