Microsoft
Software
Hardware
Network
Question : Tomcat - Best practices to "re"-deploy a webapp?
I am wondering what the best practice is for re-deploying a web application after I've made updates to the application on my development server. My current method is to upload my *new* war file to the server using MS Remote Desktop (which takes about 14 minutes), shut down Tomcat, manually delete the old war file and app folder, manually delete the "work" directory (just in case), manually copy the new war file into the webapps directory, and restart Tomcat.
Of course when I use this method, everyone's session expires and it takes several steps. I've used the manager servlet in Tomcat before but I've noticed sometimes all the new changes don't take affect. And I still need to manually copy the war file to the server (I don't want to make the manager public to the internet do I - I hope not)?!
Just curious the best way to perform this action? Many thanks.
System:
MS Server 2008
Apache HTTP Server
Tomcat 6.x
Answer : Tomcat - Best practices to "re"-deploy a webapp?
I deploy it manually (right now btw.)
But I do this just once every month or so. (Servicepack etc)
Random Solutions
My system log is being filled up with this error: WINS encountered a JET error - Event ID 4224
wi-fi requires reboot to be enabled
Event 3034
Exchange 2003, DNS, MX Records and Internet Mail SMTP Connector help
Conflicts using one or more SMTP Connectors in Exchange
Cisco Aironet (1130/1200 Series) Multiple SSID / VLAN issue
Computers in DMZ can't join domain
Unable to RDP into 2003 Server SP1, also Event 333 (maybe unrelated?)
Can't install software after connecting to domain
Sendmail 8.12.x message delivery error - Messages destined for both Valid/Invalid users not delivered to the valid users.