Changes between Version 28 and Version 29 of SopUpdateBbmriApp

Timestamp:

2013-05-29T13:59:01+02:00 (12 years ago)

Author:

antonak

Comment:

--

SopUpdateBbmriApp

@@ -10 +10 @@
 
 = Detailed tutorial =
-= Export war & mysql file =
-=  1. Run the app on your molgenis-legacy workspace (using tomcat, not standalone)
+= 1. Export war & mysql file locally  =
+== 1.1 Run the app on your molgenis-legacy workspace (using tomcat, not standalone) ==
  1. Export the war file
    1. In eclipse: File--> export --> Web --> war file
  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.
 
- =
-= '''Deploy to server''' =
+= '''2. Deploy to test server''' =
  1. As also listed here: http://www.molgenis.org/wiki/MolgenisServers the '''test server''' is at molgenis35(https://molgenis35.target.rug.nl/biobanks/) and the '''production server''' at molgenis14(https://catalogue.bbmri.nl/biobanks/) .
  1. First deploy at test server, notify [mailto:david.van.enckevort@nbic.nl david.van.enckevort AT nbic.nl]. He will notify BBMRI office, they will review the changes and if everything is ok proceed to updating bbmri production server.
@@ -23 +22 @@
    1. Ask credentials for molgenis35/molgenis14 from Pieter or Morris.
 
-=== create migration script according to data in live server ===
- 1. If you know the exact changes of the database, compared to the old version in live server, then the migration script is the commands that synchornize the two versions.
- 1. You can compare the mysql dump files between the live and the local version. This is easier if you dump only the schemas (not the data) .
+=== 2.1 Create migration script according to data in live server ===
+ 1. If you know the exact changes of the database, compared to the old version in live server, then the migration script is consisted of the commands that synchornize the two versions.
+ 1. You do not know, you can can compare the mysql dump files between the live and the local version. This is easier if you dump only the schemas (not the data) .
    1. First ssh to molgenis14
    1. create a dump file: mysqldump --no-data, -d bbmri -u molgenis –pmolgenis > ~/databaseDumps/<date>bbmriDBlive.mysql
@@ -31 +30 @@
    1. diff <date>bbmriDBlive.mysql <date>bbmriDBlocal.mysql
 
-=== copy war file & migration script from your  computer to test server ===
+=== 2.2 copy war file & migration script from your  computer to test server ===
  1. Copy the war file and the mysql migration script  from your computer  to the server as follows:
    1. scp  <filename>.war molgenis@molgenis35.target.rug.nl:./
    1. scp <migrationScriptFilename> molgenis@molgenis35.target.rug.nl:./
 
-=== Export data from LIVE server ===
+=== 2.3 Export data from LIVE server ===
  1. Ssh to the server:
    * ssh  !molgenis@molgenis14.target.rug.nl
@@ -42 +41 @@
    * mysqldump bbmri -u molgenis –p > ~/databaseDumps/<date>bbmriDB.mysql
 
-=== Copy data from LIVE server to your computer ===
+=== 2.4 Copy data from LIVE server to your computer ===
  1. scp  molgenis@molgenis14.target.rug.nl:./databaseDumps/<date>bbmriDB.mysql  ./mysql<date>LIVEdata.mysql
 
-=== Copy data from your computer to test server ===
+=== 2.5 Copy data from your computer to test server ===
  1. scp   ./mysql<date>LIVEdata.mysql molgenis@molgenis35.target.rug.nl:./databaseDumps/mysql<date>LIVEdata.mysql
 
-=== Deploy at test server ===
+=== 2.6 Deploy at test server ===
  1. Ssh to the server:
    * ssh  !molgenis@molgenis35.target.rug.nl
    * You are now at /srv/molgenis/ where your files where copied.
 
-=== Backup ===
+=== 2.7 Backup ===
  1. '''BACKUP your DATABASE FIRST''':
    * mysqldump bbmri -u molgenis –pmolgenis  > ~/databaseDumps/<date>bbmriDB.mysql
    * Check the dumbed file if it is not just an error file …
 
-=== Insert the data from live server to test server ===
+=== 2.8 Insert the data from live server to test server ===
 compare the sql file from test server with the live server. then make a migrationscript and insert this tables into testserver
 
@@ -64 +63 @@
   ===
 
-=== Apply migration steps: ===
+=== 2.9 Apply migration steps: ===
  * mysql -u molgenis –pmolgenis
  * use bbmri