Version 1 (modified by 14 years ago) (diff) | ,
---|
Upgrading
Upgrades *must* be tested against a *backup* of your live database!
- A test environment with a standalone server and a test database is highly recommended.
Upgrading the web application side:
- Download a released war file or build a custom version.
- Stop the running servlet (e.g. Tomcat).
- Move the old war file and deployed folder to a backup location.
- Place the new war file in the webapps directory and start the servlet.
Upgrading the database side:
- Where there are no changes to the schema (domain class folder) between versions nothing further needs to be done.
- Officially released versions (1.0.0, 1.1.2 etc) will have upgrade scripts released either here or with the software.
- Upgrade scripts will be sequential (to upgrade from 1.0.0 to 1.0.2 may have two sets of scripts that must be executed in order).