Updating XStudio

Updating XStudio for all the users is quite straight froward.
The first thing to do to avoid loosing some data is to ask all the users to close their XStudio instance and wait until the upgrade procedure is completed.

Backup the database

Please refer to your Database Server guide for more information or check out this section of the installation guide.


Updating a standalone version

Windows clients

  • Do NOT delete your old standalone version. Just run the setup program and install the new version into the same location.
  • Run the new updated version. At the first run, the *.conf files and the database schema will be automatically updated (you will be asked for the admin password for security reason).
  • If you are using a launcher you personally developed (not included in the distribution), you will need to recompile it using the latest version of launcher_lib.jar.


Linux/Unix/MacOSX clients

  • Do NOT delete your old standalone version
  • Rename all the *.conf files as *.conf.bak (and leave them in the same location)
  • Unzip the package to the old install folder (this will overwrite all the files - except *.conf files of course since you renamed them
  • Run the new updated version. At the first run, the *.conf files and the database schema will be automatically updated (you will be asked for the admin password for security reason).
  • If you are using a launcher you personally developed (not included in the distribution), you will need to recompile it using the latest version of launcher_lib.jar.




That's it! the database is updated and your standalone version is ready to be used. All the users having a standalone version will need to do the same (except that the database update will not occur as you already did it).



At this point, the web users will not be able to start anymore their web versions though.


Updating the web version (for all the users)

  • Backup all the *.conf files and the *.jnlp file that are on the web server
  • Unzip the package and overwrite the old web install folder
  • Edit the *.jnlp file and update the codebase attribute (open the backuped version if you don't remember the exact URL)
  • Edit the *.conf files and manually update them (open the backup versions if you don't remember some values - especially the encrypted passwords :))

    WARNING: Do NOT just overwite all the *.conf and *.jnlp with the backuped ones as there may be some structural changes in it (sometimes not very visible)

    However, if you already updated a standalone version, you can copy the *.conf files to the web server (as they have been updated as well).

  • Restart your web server (Apache or Tomcat)
  • If you are using a launcher you personally developed (not included in the distribution), you will need to recompile it using the latest version of launcher_lib.jar.


(client browsers may have to clear their cache)