caTissue Upgrade notes

p5 -> v1.2

The first deployed version of caTissue at the LCBRU was v1.1.p5 - in April 2011 v1.2 was released.

Notes from initial upgrade testing:

jboss must be stopped before upgrade takes place, or it will fail.

Initial upgrade command is 'ant upgrade_p5'

Once database is correctly migrated, further deployments of the caTissue to account for changes to the caTissueInstall.properties file can be made by 'ant deploy_app'.

v1.2 -> CaTissuePlus

In January 2013 we began a move to CaTissuePlus, formally supported by Krishagni. This co-incided with migration from the legacy hardware to the University LAMP service. Work was conducted and validated on ​https://lcbru-catissue-dev.rcs.le.ac.uk/ including testing the API client 'sampler' app.

There were a number of issues:

• Initially the API client failed because barcodes were being automatically assigned by CaTissue - this is the default behaviour of the application but LCBRU deployment approach is to disable this feature and assign all barcodes manually.

• There was a backend java / hibernate error reported regarding a missing column 'WUSTLKEY' which related to users being identified at login time. This did not affect the functioning of the API client but was resolved with a database amendment anyway:

  alter table csm_migrate_user change MIGRATED_LOGIN_NAME WUSTLKEY varchar(100);

• There were issues with the use of the load balancer on the LAMP service and mod_proxy being used to forward requests, which meant that secure addressing was not required in WEB-INF/flex/services-config.xml - the my-secure-amf channel endpoint class needed to be changed to AMFEndpoint not AMFSecureEndpoint.

• The API 'sampler' app did not work with CaTissuePlus v2.0 - JBOSS returned "ERROR 2013-01-23 11:45:21,814 -catissuecore.client.CaCoreAppServicesDelegator - Delegate Editnull, java.lang.NullPointerException". A patched version was supplied by Atul Kaushal on 25.1.2013 which was tested and found to work on 28.1.2013. Further testing was conducted oin parallel with live data processing that week.

Repeated testing with various database dumps from the live CaTissue v1.2 system are possible by dropping the database and creating it again, then loading the dump before running 'ant upgrade_db' from the catissue home directory. The csm_migrate_user fix above will need to be re-run each time. However, 'ant upgrade_db' did not successfully upgrade the database.