Changes between Version 2 and Version 3 of SopUpdateBbmriApp


Ignore:
Timestamp:
2013-04-24T11:30:04+02:00 (12 years ago)
Author:
antonak
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SopUpdateBbmriApp

    v2 v3  
    22== Export war & mysql file ==
    33 1. Run the app on your molgenis-legacy workspace (using tomcat, not standalone)
    4  1.  Export the war file
     4 1. Export the war file
    55   1. In eclipse: File--> export --> Web -->  war file
    66 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.
    77
    8      
    98== Deploy to server ==
    10       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/) .
    11  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. 
    12  1. Deploy at test molgenis14 (Take a look here also http://www.molgenis.org/wiki/SopCreateMolgenisVM#SopDeploymentForDevs ) : 
     9 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/) .
     10 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.
     11 1. Deploy at test molgenis14 (Take a look here also http://www.molgenis.org/wiki/SopCreateMolgenisVM#SopDeploymentForDevs ) :
    1312   1. Ask credentials for molgenis35, molgenis14 from Pieter or Morris.
    1413   1. Copy the war file and the mysql migration script to the server as follows:
    15      1. scp  <filename>.war [mailto:molgenis@molgenis35.target.rug.nl:./ molgenis@molgenis14.target.rug.nl:./]
    16    1. Ssh to the server:      
     14     1. scp  <filename>.war [mailto:molgenis@molgenis35.target.rug.nl:./ molgenis@molgenis14.target.rug.nl:./]
     15   1. Ssh to the server:
    1716     * ssh [mailto:molgenis@molgenis35.target.rug.nl molgenis@molgenis14.target.rug.nl]
    1817     * You are now at /srv/molgenis/ where your files where copied.
    1918     * The database is bbmri, so in order to apply the migration steps you created:
    20      * '''BACKUP your DATABASE FIRST''': 
    21        * mysqldump bbmri -u molgenis –pmolgenis  > ~/databaseDumps/<date>bbmriDB.mysql
     19     * '''BACKUP your DATABASE FIRST''':
     20       * mysqldump bbmri -u molgenis –pmolgenis  > ~/databaseDumps/<date>bbmriDB.mysql
    2221
    23 
    24 
    25      *   Check the dumbed file if it is not just an error file …
    26      *   Apply migration steps:
    27        * mysql -u molgenis –pmolgenis
    28        * use bbmri
    29        * <apply mysql commands>
    30      * '''Backup & replace the war file on server''':
    31        * The war file is in /usr/share/tomcat6/webapps/biobanks.war
    32        * cp  /usr/share/tomcat6/webapps/biobanks.war ~/warFiles/<date_bbmri.war>
    33      * Now replace the file there with your recent file uploaded in the server. This will OVERWITE the old file and tomcat will take affect immediately. Do not delete the old first, that won’t work! Just overwrite it!
    34        * cp   <filename>.war  /usr/share/tomcat6/webapps/biobanks.war
    35      *  You can check the tomcat & mysql service with: 
    36        * sudo service tomcat6 status
    37        * sudo service mysqld status
     22 * Check the dumbed file if it is not just an error file …
     23 * Apply migration steps:
     24   * mysql -u molgenis –pmolgenis
     25   * use bbmri
     26   * <apply mysql commands>
     27 * '''Backup & replace the war file on server''':
     28   * The war file is in /usr/share/tomcat6/webapps/biobanks.war
     29   * cp  /usr/share/tomcat6/webapps/biobanks.war ~/warFiles/<date_bbmri.war>
     30 * Now replace the file there with your recent file uploaded in the server. This will OVERWITE the old file and tomcat will take affect immediately. Do not delete the old first, that won’t work! Just overwrite it!
     31   * cp   <filename>.war  /usr/share/tomcat6/webapps/biobanks.war
     32 * You can check the tomcat & mysql service with:
     33   * sudo service tomcat6 status
     34   * sudo service mysqld status
    3835
    3936 * Check your deployment at: [https://molgenis14.target.rug.nl/biobanks/ https://molgenis35.target.rug.nl/biobanks/]
     37
     38     '''The same steps apply to the production server molgenis14 . '''