Page History

...

Next, move the SHRINE webclient to that same backup location. Later on, we will be restoring i2b2_config_data.js from this backup. If you choose not to make any backups, make sure to at least keep a copy of i2b2_config_data.js and js-i2b2/cells/SHRINE/cell_config_data.js!

$ mv /opt/shrine/tomcat/webapps/shrine-webclient /opt/shrine/upgrade-backups/shrine-webclient

...

After this, restore the previous i2b2_config_data.js and cell_config_data.js file from your backup and place it in the new shrine-webclient folder:

$ cp /opt/shrine/upgrade-backup/shrine-webclient/i2b2_config_data.js /opt/shrine/tomcat/webapps/shrine-webclient/i2b2_config_data.js

$ cp /opt/shrine/upgrade-backup/shrine-webclient/js-i2b2/cells/SHRINE/cell_config_data.js /opt/shrine/tomcat/webapps/shrine-webclient/js-i2b2/cells/SHRINE/cell_config_data.js

Schema Changes in 1.18

SHRINE 1.18 adds columns to the SHRINE_QUERY table, and also creates the HUB_QUERY and HUB_QUERY_RESULT tables.

...

$ /opt/shrine/tomcat/bin/startup.sh

Instructions for Updating the SHRINE Web Client from 1.17.1 to 1.18.0

...

Image Removed

...

Now use svn to check out the latest version of the webclient here:  https://open.med.harvard.edu/svn/shrine/releases/1.18.0/code/shrine-webclient 

From the command line in linux this would be something like: svn co https://open.med.harvard.edu/svn/shrine/releases/1.18.0/code/shrine-webclient

...

Now copy the i2b2_config_data.js file from 1.17.1 (see step 2) newly checked out shrine-webclient directory.

Image Removed

Now copy the cell_config_data.js file from 1.17.1 (see step 3) into the newly checked out shrine-webclient directory at location shrine-webclient/js-i2b2/cells/SHRINE/

Image Removed

...

...