CT2 Release Procedure

From UG

Revision as of 00:51, 7 January 2010 (edit) Alex (Talk | contribs) ← Older edit		Revision as of 00:55, 7 January 2010 (edit) (undo) Alex (Talk | contribs) Newer edit →
Line 32:		Line 32:
	rm -r { directory name }		rm -r { directory name }
-
-	== Patch DB for New Release ==
-
-	through Navicat
	== Start tomcat ==		== Start tomcat ==
	type ./startup.sh		type ./startup.sh
		+
		+	== Patch DB for New Release ==
		+
		+	through Navicat
	== Deploy war file with New Release  ==		== Deploy war file with New Release  ==
	from tomcat manager		from tomcat manager

---

Revision as of 00:55, 7 January 2010

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

Notify

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, Alex Dobrovolsky

Stop Tomcat

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

Make a backup of the webapp folder

cp -ra Client Client.bak
cp -ra internal internal.bak

Create a mysqldump of Cybertrax Internal database

mysqldump -uroot -pJaG118Svc! -R --lock-all-tables cybertraxInternal > /var/backup/ct2_2009_jan_6

Delete Internal webapp dir

rm -r { directory name }

Start tomcat

type ./startup.sh

Patch DB for New Release

through Navicat

Deploy war file with New Release

from tomcat manager