To upgrade the system from TrackStudio 3.1.x to TrackStudio 3.2.y:
- Stop the TrackStudio 3.1.x instance.
- Backup your database. The backup will allow you to continue to use version 3.1.x until until any unforeseen problems with TrackStudio 3.2.y are solved.
- Install the TrackStudio 3.2.y into a separate directory.
- Upgrade database:
- TrackStudio SA: Run Server Manager from TrackStudio 3.2.y, go to the Database -> Database Management tab, and press the Upgrade Database button.
- TrackStudio WAR: Execute the update script for your DBMS. Use the appropriate script from sql\upgrade-31-32 directory.
- Configure TrackStudio.
- TrackStudio SA: Run Server Manager from TrackStudio 3.2.y.
- TrackStudio WAR: Edit the trackstudio properties files.
- Copy all files from the TrackStudio 3.2.x. upload directory into the Upload directory for the new instance. To determine the upload directory path, see the trackstudio.uploadDir property in the trackstudio.properties file.
- Delete the contents of the Index directory. To determine the index directory path, see the trackstudio.indexDir property in the trackstudio.properties file.
- Start TrackStudio 3.2.y
- Login as root.
- Update e-mail templates:
|
Property |
Value |
|
Subject |
<${task.getProjectAlias()}>: ${addval.taskViewFactory.inEmailText(task).getName()} ${addval.taskViewFactory.inEmailText(task).getNumber()} |
|
Content Type |
HTML |
|
From |
Submitter |
|
Reply To |
TrackStudio |
|
E-mail Body |
Copy/paste from templates/common_html.ftl |
|
Property |
Value |
|
Subject |
<${task.getProjectAlias()}>: ${addval.taskViewFactory.inEmailText(task).getName()} ${addval.taskViewFactory.inEmailText(task).getNumber()} |
|
Content Type |
text |
|
From |
Submitter |
|
Reply To |
TrackStudio |
|
E-mail Body |
Copy/paste from templates/common_text.ftl |
Important Information Regarding Upgrading Your Database:
- XML Import/Export allows you to transfer the data of TrackStudio 3.2 between various database types, but it cannot be used to transfer data between various versions of TrackStudio.
- If errors or problems occur while upgrading the database, you should contact us and continue using TrackStudio 3.1.x until the problem is resolved.
- If you are using the default HSQLDB DBMS, your database files look like test.lck, test.log, test.properties and test.script. Do not delete them.
- Both the Upload and Index directories can be specified in a flexible manner in trackstudio.* configuration files, to set them outside the TrackStudio instance directory. This has implications when upgrading.
- In previous versions, fields of the class Timestamp were used for datetime objects in the database. The ability to search datetime objects using greater-than or less-than operators was required, so as of version 3.2, we have changed from Timestamp to Calendar for all datetime fields. This change affects scripts as well, because they have direct access to the TrackStudio object model. Here are a few examples of how you can upgrade your 3.1 scripts to be compatible with 3.2:
task.getSubmitdate().getTime()
task.getUpdatedate().getTime()
task.getSubmitdate().getTime().getTime()
task.getUpdatedate().getTime().getTime()
Description