a quick way to test OpenClinica 3.4

For those of us who want to test release 3.4 before installing it, here is a quick way to do just that.
What we'll do is:

  1. rename the war to oc34.war
  2. let tomcat deploy it
  3. create a new, empty database oc33
  4. make a backup of our existing 3.1.2, 3.1.3, 3.1.4, 3.2 or 3.3 database
  5. restore that as oc34
  6. copy the directory openclinica.data
  7. modify datainfo.properties
  8. start oc33

start with the war

Start with downloading the zip with the war and then unzip it and rename the war to oc34.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 oc34.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 oc34 with encoding='UTF-8' owner=clinica;

sudo -u postgres /usr/bin/pg_dump openclinica > pg_dump_openclinica_20141011
sudo -u postgres /usr/bin/psql oc34 < pg_dump_openclinica_20141011

(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 oc34.data

datainfo.properties anyone?

If you like you can go through datainfo.properties, to edit it to your favorite settings. But the defaults work. Be aware that in this version the location of the datainfo.properties has been changed: it is now located in oc34.config of the tomcat directory!

start oc34

As a last step, go to tomcat's manager/html and start oc34.

what to look for?

On https://docs.openclinica.com/release-notes/release-notes-openclinica-3.4-current-production-release you can find a summary of what's new in this release.

We definitely like the new token, because it enables us to get data from other Events in our CRF, as described here.

one last thing

After you've evaluated version 3.4 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.

this page was last reviewed October 2014