Changes between Version 21 and Version 22 of SopUpdateBbmriApp
- Timestamp:
- 2013-05-29T13:03:15+02:00 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SopUpdateBbmriApp
v21 v22 7 7 1. The database is updated as follows: apply the mysql changes that you have made locally to the database on the server, so that you have the latest version of data for the server and the changes you want applied there. About the database changes you need to track them in a migration a file like one in the end of this document. 8 8 9 10 9 == Quick tutorial == 11 1) Copy the mysqldump from the live server to the test server 12 2) Deploy the new war file on the testserver 13 2.1) Check if there are errors according to changes in the model. There are 2 ways: 14 * compare the mysql from the live and the testserver 15 * check in the application if there are errors 16 2.2) If there are changes, make the migration script 17 10 1) Copy the mysqldump from the live server to the test server [[BR]]2) Deploy the new war file on the testserver[[BR]] 2.1) Check if there are errors according to changes in the model. There are 2 ways: 11 12 * compare the mysql from the live and the testserver 13 * check in the application if there are errors 14 15 2.2) If there are changes, make the migration script 18 16 19 17 == Deploy to server == … … 51 49 52 50 === Insert the data from live server to test server === 53 compare the sql file from test server with the live server. 54 then make a migrationscript and insert this tables into testserver 51 compare the sql file from test server with the live server. then make a migrationscript and insert this tables into testserver 52 55 53 === * mysql -u molgenis -pmolgenis bbmri < 29Maydump.mysql === 56 54 === 57 55 58 === Apply migration steps: === 59 60 61 56 === Apply migration steps: === 57 * mysql -u molgenis –pmolgenis 58 * use bbmri 59 * <apply mysql commands> 62 60 * '''Backup & replace the war file on server''': 63 61 * The war file is in /usr/share/tomcat6/webapps/biobanks.war