CT2 Release Procedure

From UG

Revision as of 00:29, 3 March 2010 (edit) Paul (Talk | contribs) (→Make a backup of the webapp folder) ← Older edit		Revision as of 00:31, 3 March 2010 (edit) (undo) Paul (Talk | contribs) (→Delete Internal and Client webapp dirs and wars) Newer edit →
Line 35:		Line 35:
	rm -rf internal		rm -rf internal
-	rm -rf Client.war	+	rm -f Client.war
-	rm -rf internal.war	+	rm -f internal.war
	== Start tomcat ==		== Start tomcat ==

---

Revision as of 00:31, 3 March 2010

Contents 1 Notify 2 Stop Tomcat 3 Make a backup of the war file 4 Create a mysqldump of Cybertrax Internal database 5 Delete Internal and Client webapp dirs and wars 6 Start tomcat 7 Patch DB for New Release 8 Deploy war file with New Release

Notify

Admin ! Make sure you notify 6 hours in advance!

Dear Jaguar Global,

CT2 will not be available at 7:40 pm EST because we need to perform the server maintenance. This process is estimated to take less than an hour and an e-mail notification will be sent when CT2 is back online.

Thank you for your patience.

Best Regards, IT Dept

Stop Tomcat

go to /opt/tomcat/bin as root (su -)
type ./shutdown.sh
pgrep java
pkill -9 java

Make a backup of the war file

cp -a Client.war Client.war.bak
cp -a internal.war internal.war.bak

Create a mysqldump of Cybertrax Internal database

mysqldump -uroot -pJaG118Svc! -R --single-transaction cybertraxInternal > /var/backup/ct2_2009_jan_6.sql

Delete Internal and Client webapp dirs and wars

rm -rf Client
rm -rf internal

rm -f Client.war
rm -f internal.war

Start tomcat

type ./startup.sh

Patch DB for New Release

through Navicat

Deploy war file with New Release

from tomcat manager