We’ll periodically update JATOS with new features and bug fixes. We recommend you stay up to date with the latest release. However if you are currently running a study it’s always safest to keep the same JATOS version throughout the whole experiment.
Since version 3.3.5 you can update your JATOS automatically (if you have admin rights and running on Mac OS or Linux (including Docker), that is). Windows is not yet supported.
The process is pretty self-explanatory, but anyway, we’ll explain it here in detail:
If your JATOS version is not the latest one available, you will get a notification in your JATOS’ home page.
- We expect no problems, but sh&t happens. We recommend that you back up your result data and study assets folder before continuing.
- Click on Update, confirm that you want to continue and the latest JATOS version will be downloaded from GitHub and saved in your system’s temporary folder. Usually the variant downloaded will be the one without bundled Java. Only in cases where JATOS switches to a newer version of Java a bundled version is required (see below). The download might take a while depending on your internet connection.
After dównload is complete, you will be asked again for confirmation. By default, JATOS will back up: it will copy the content of its own installation folder into a folder with the name backup_x.x.x (x.x.x is the version before the update). This will usually include your H2 database, your study assets and logs - but not your MySQL database (should you have one). If anything goes wrong in the auto-update, you have everything in this backup folder to start the old JATOS again. This backup will use up disk space (therefore you can opt out).
- After clicking the Go on button, JATOS will stop itself, replace its program files and re-start itself again. This might take up to a minute.
- Refresh your JATOS home page every now and then until you see your updated JATOS’ login screen again.
- Check the new JATOS with the build-in test page localhost:9000/jatos/test in the browser. All tests should be OK.
Pre-releases will not be available as auto-updates by default. If you want to force this to be the case (and you know what you’re doing), append the parameter “&showPreReleases” to your JATOS home page URL.
Auto-updating might not always be possible. JATOS versions will be flagged so that they are not available for auto-update. You’ll have to do a manual update.
Versions with newer Java required
As of today, JATOS (v.3.3.4) uses Java 8. Future versions will likely require newer Java versions. If you’re updating from a JATOS version using Java 8 to (say) another version using Java 11, the auto-update process will automatically download JATOS bundled with the new Java, regardless of wich variant you are currently using. If you do not like the bundled Java and use your own version you can always remove the folder jre later on after the update.
Updating a local installation of JATOS
(The procedure is different if you want to update JATOS on a server installation)
To be absolutely safe you can install the new JATOS version and keep the old one untouched. This way you can switch back if something fails. Just remember that only one JATOS can run at the same time. Always stop your old JATOS instance before starting another one.
After updating you can check the new JATOS with the build-in test page localhost:9000/jatos/test in the browser. All tests should be OK.
You can update your local JATOS instance in two main ways:
First, easy way: discarding your result data
If you don’t care about result data stored in JATOS:
- Export any studies you wish to keep from the old JATOS installation.
- Download and install the new version as if it were a new fresh download. Don’t start it yet.
- Stop the old JATOS and start the new JATOS.
What will be transferred:
- Files and subfolders in study’s assets folder
- All your studies’ and components’ properties
- The properties of the first (Default) batch
What will be lost:
- All result data will be lost
- All workers in all batches (including Default batch)
- All batches other than the Default batch
- All study logs
Second way: keeping everything (including your result data)
If you do want to keep your studies, batches, and your result data you’ll have to move them to the new JATOS.
- Stop JATOS (on Unix systems, type
$ ./loader.sh stopon the terminal. On Windows MS, close your command window)
- Go to the folder of your old JATOS installation. From there copy your assets root folder to the new JATOS installation (Note: By default your assets root folder is called
study_assets_rootand lays in the JATOS folder but you might have changed this. You can find the location and name in
conf/production.conf. It is specified in the line beginning with
- From the folder of your old JATOS installation copy the folders
study_logsto the folder of the new JATOS installation.
- If you had changed the
conf/production.conffile in your old JATOS instance (for example to set a custom location for your
study_assets_rootfolder) you’ll have to do this again in the new JATOS version. We recommend re-editing the new version of the file, rather than just overwriting the new with the old version, in case anything in the
production.conffile has changed.
- Start the new JATOS (on Unix systems, type
$ ./loader.sh starton the terminal. On Windows double click the
- Open JATOS’ test page in a browser
/jatos/testand test that everything is OK
What will be transferred:
- Files and subfolders in study assets folder
- All your study and components properties
- All batches, together with their workers, generated links, and results
- All study logs
What will be lost: nothing