View Source

notify all stake holders before the release.
for this deploy we are pulling from svn trunk
execute all steps in the SF ENVs first and test the application.
if tests pass, then execute steps on SD ENVs.
In the unlikely event that things go very badly, we switch over to the old application in SD.

put both web servers into maintenance mode (SF WEB, SD WEB)

cd /var/www/html
sudo ./set_eas_mode.sh MAINT

Log into PROD DB and back up the DB

sudo -u postgres -i
/home/dba/scripts/dbbackup.sh > /var/tmp/dbbackup.log

Log into to the PROD ETL server and deploy the new code.

REM see warning above
cd "C:\Program Files\MAD\"
del etl
setup.bat

Then run the 1.1.5 DB migrate job.

 
cd "C:\Program Files\MAD\el\src"
python job.py --action INIT --job migrate_to_1.1.5 --env SF_PROD

Enable scheduled job called "export_flat_file_to_ftp".

Test the job by running it manually.

Log into the web server and deploy the application as shown here.

# see warning at top
cd /var/www/html
sudo ./deploy_eas_init.sh

Test the application to make sure everything works.

If testing passes, deploy the web app to SD PROD WEB.

Make sure the SD web application works.

You will not be able to log into the web application in SD if DB replication is running.

Make sure SF PROD WEB is in LIVE mode. If not, do this...

cd /var/www/html
sudo ./set_eas_mode.sh LIVE

Put SD PROD WEB server into STANDBY mode

cd /var/www/html
sudo ./set_eas_mode.sh SD_STANDBY