Home › Implementors Handbook › Upgrade Documentation ›

Upgrading to OpenVPMS version 1.3

Submitted by tony on Tue, 24/03/2009 - 09:46

This page outlines the required steps to upgrade a 1.2 release OpenVPMS installation to release 1.3.

Step Description 
Download OpenVPMS Installation Files 
  • Download the latest OpenVPMS Installation files from here.
  • Unzip the Installation Pack onto your OpenVPMS server; This should create a openvpms-release-1.3 folder with the necessary files to install or update OpenVPMS.
Stop Tomcat Service 
  • Stop Tomcat
Database Backup The 1.2 to 1.3 database upgrade process is quite extensive so we strongly suggest performing a MySQL database backup prior to attempting the upgrade.  Use the MySQl administrative tool or phpmyadmin under Linux to create a backup.
OpenVPMS Database Upgrade Depening on the size of your OpenVPMS database the upgrade process can take some time so we suggest you give yourself plenty of time for the process to complete.
  • Open a command prompt.
  • Navigate to openvpms-release-1.3\update\db folder
  • Start the mysql command line client and enter the following commands 
    mysql -u root -p
mysql> use openvpms;
mysql> source migrate-1.2-to-1.3.sql ;
mysql> quit;
Download and install the Mysql JDBC driver  This release does not package  the Mysql database JDBC driver that is required by OpenVPMS to talk to a Mysql database installation.  This is due to license restrictions on the Mysql connector. 



Using your current OpenVPMS-1.2 installation you can copy the necessary files from this installation to the  new 1.2 installation and Tomcat using these instructions:
  • In the openvpms-release-1.2\lib folder find the file mysql-connector-java-5.1.5-bin.jar and copy to openvpms-release-1.3\lib folder.
  • This file should already be in the Tomcat shared\lib  folder from the 1.2 upgrade.
Reload the Archetypes 
  • Navigate to C:\openvpms-release-1.3\bin
  • Run the archetype load utility  by typing archload
Update the OpenVPMS web application 
  • Navigate to the Apache Tomcat webapps folder
  • Delete the existing  openvpms.war file
  • Delete the existing openvpms folder
  • Copy the  openvpms.war  file from the openvpms-release-1.3\webapps  folder to the Tomcat webapps folder.
Start Tomcat 
  • Restart Tomcat
Software Configuration

Version 1.3 consists of some significant software changes, specifically the new enhanced scheduler.

You will need to do some significant configuration steps in order to get the Scheduling and Worklist workspaces operational.  This includes:

  • Adding new Scheduling and Worklist views in Administration ->Organisation and associating them with practice locations.
  • Adding existing schedules and worklists to the views and setting their display order.

This version also includes automatic post code lookups using a new suburb lookup. We suggest you:

  • Check you have a default state selected in Administration -> Lookups
  • Check the suburbs and postcodes created from your existing data during the data migration process.  You may find many duplicated suburbs due to there being different suburb name postcode combinations in the original data.  You may need to inactivate some of these suburbs to clean up your suburb list during data entry.

  If you have any questions on these ad other software changes please post them on the forum.

 

Syndicate content