a quick way to test OpenClinica 3.1.3
For those of us who want to test release 3.1.3 before installing it, here is a quick way to do just that.
What we'll do is:
- rename the war to oc313.war
- let tomcat deploy it
- create a new, empty database oc313
- make a backup of the 3.1.2 database
- restore that as oc313
- copy the directory openclinica.data
- check datainfo.properties
- start oc313
start with the war
Start with downloading the zip with the war and then unzip it and rename the war to oc313.war. Once you've done that, copy the war to tomcat/webapps. Tomcat will start deploying it, but it will not be able to start it, because there is no corresponding database. If tomcat does not deploy the war automatically, check with ls -al if tomcat is the owner and if not, issue chown tomcat:tomcat oc313.war
copying the database
We assume that you will want a copy of your existing database and the way to do that is making a new, empty database. Then making a dump of your production database and restoring that to the new one.
sudo -u postgres /usr/bin/psql
create database oc313 with encoding='UTF-8' owner=clinica;
\l
\q
sudo -u postgres /usr/bin/pg_dump openclinica > pg_dump_openclinica_20121125
sudo -u postgres /usr/bin/psql oc313 < pg_dump_openclinica_20121125
(The \l is to check if the creation of the database was successful and the \q to quit psql.)
don't forget the data
Now before we start we must copy the data-directories and we do that with:
cd /usr local/tomcat
sudo -u tomcat cp -r openclinica.data oc313.data
datainfo.properties anyone?
If you like you can go through datainfo.properties, to edit it to your favorite settings. But the defaults work.
start oc313
As a last step, go to tomcat's manager/html and start oc313.
what to look for?
First of all: login to your 3.1.2 instance and also to your 3.1.3 instance and notice the difference in performance.
Especially in large Studies with lots of CRFs you should notice a better performance (sometimes 40%) when opening and saving.
Same applies to Notes & Discrepancies.
And look at the option Configure Password Requirements in the Users-section.
And there's also the option to migrate CRF-data to a newer version of the CRF, on a Subject basis.
fig. 1: example of CRF version migration
one last thing
After you've evaluated version 3.1.3 and decided that indeed you want to upgrade, make a backup first! Do it for example as described here and when you've done that, store the files on another server and a tape and burn them on CD. Well, you get the picture.
Other how-to-pages can be found here.