In this update, we moved most configuration parameters to the new System Options Screen. You will need to populate this screen with values that previously you had been storing in various config files. Once populated, you won't have to update this screen each time you upgrade as these values are stored in the database.
Migration Steps
- Shut down project (e.g. turn off Tomcat)
Make copies of any configuration files you've modified and don't want to be overwritten (VetView-authentication-config.properties, VetView-database-config.properties, VetView-communication-config.properties (all 3 in the <VetView Installation Folder>/WEB-INF folder/classes folder), or zk.xml (in the <VetView Installation Folder>/WEB-INF folder).
Again, please note that for this update, you definitely DO NOT want to copy/paste your config files. We took most configuration parameters and moved them to the System Options Screen.
- If you never specified a path for attachments and custom labels/reports (on this Lab Setup Tab), and you have some of those, you'll need to make copies of those attachments, reports, and labels. They will be located in the <VetView Installation Folder>/upload folder.
- Apply database upgrade scripts
- VetView 0.9.2.3 to 0.9.2.4 Migration.SQL
- Localization Update Script
- Deploy new war file
Make any necessary updates to configuration files that you saved in step 2.
For this one particular update from 0.9.2.3 to 0.9.2.4, you'll need to go to the System Options Setup Screen and populate all the values you use. In future upgrades, you won't need to populate those values, since they will be stored in your database.
- Restart Project
- If you're running the Lab Portal, you'll need to switch out the WAR file for the new 0.9.2.4 Lab Portal WAR, and update the config file for it as well.
- If you're running the UVIS Interface, you'll need to switch out the WAR file for the new 0.9.2.4 UVIS Interface WAR,and update the config file for it too.
- Lastly, if you want to run new TCP/IP instrument interface, you'll need to run the TCP/IP script (unless you've run it before) and deploy the TCP/IP WAR.
Remember that the download links will not work if you are not logged in with the shared downloader account.