community
Upgrade FAQ
Questions about Teamwork upgrade
For more information about Teamwork upgrade read the user guide.
What I have to do before upgrading Teamwork?
These are the required operations to preserve all your data and your configurations settings:
1. Backup your database
2. Backup the entire web application: TEAMWORK_HOME/webapps/ROOT which includes also the folder TEAMWORK_HOME/webapps/ROOT/applications/teamwork/portal/news which contains images uploaded for company news.
3. Backup your repository, where files get uploaded: if you have not
customized this folder you can find it in
TEAMWORK_HOME/teamworkRepository.
Can I upgrade by hand?
There are cases where upgrade by hand is the only option; say if you
don't have a graphical interface, or if the server running detection
fails, getting "Server seems to be running: must stop it before
upgrade/reinstall" even at server stopped.
This is from the installation guide:
The only files that should not be replaced, eventually synchronized, for an upgrade are:
- [ROOT]/WEB-INF/lic.properties
- [ROOT]/WEB-INF/config.properties
- [ROOT]/commons/settings/global.properties
In order to upgrade with the installer
1. make a complete backup of your application and data
2. stop the application server (Tomcat or other)
3. extract the zip or tar.gz or rpm files, merging with the existing files. Take care that the pre-existing folders must be merged with the new ones, which is default on Windows, but not on Linuxes and OSXs.
4. remove the line SETUP_DB_UPDATE_DONE=yes from the global.properties file
5. restart the application server
The application on restart after upgrade does also a database upgrade.
I have upgrade problems
If in the platform log file there is an exception like "Caused by: java.sql.SQLException: Unknown column", this means that the database schema upgrade and data default update did not work. When updating, Teamwork does two operations:
1. may alter database schema
2. may copy data from old colums to new columns
3. if numeric of boolean columns have been added, old records are updated with default values, tipically 0
So if anything want wrong in this process, you can manually force Teamwork to repeat the upgrade process. If the alter schema process of your database is not transactional (e.g. SQL Server is, and Oracle is not), some upgrades may have been processed, and others not. Only the missed updates will be re-attempted by the procedure.
Notice that in these circumstances, the Teamwork user configured in the JDBC connection, i.e. in the config.properties file, must have alter schema rigths, not just read and write.
In order to manyually force to repeat the update progress, proceed as follows:
1. stop the web server, do all backups
2. delete the line SETUP_DB_UPDATE_DONE=yes in the global.properties file, if there; if there is SETUP_DB_UPDATE_DONE=no, leave it as it is
3. clean the platform.log file, after a backup
4. restart the web server.
Schema update for MySql from (3.1.0 or 3.2.0) to 3.2.1 or 3.2.2
see in Teamwork3 install/upgrade PDF .
