I install the latest Tomcat and then run the installer typically. Occasionally I'll deploy the war without running the installer. I like doing the initial config via the installer. Especially since we do not install our apps the the root volume (C:), if I forget to change the path in config.properties before starting TC we end up with a junk directory in C: for the reporting location.
Not sure why I use the installer for new installs but rename the old 'midtier' dir and drop in the new one from the war for upgrades and patches. I have the same C: directory problem as with an install. It is just a flow I have developed over time. I think largely it is left over from when I didn't understand TC very well and the installers automagically deploy the web app so I didn't have to worry about it. Then for upgrades/patches I just need to drop the new dir in the right place. If it doesn't go well just shutdown TC, and put the previously working files back. Jason On Mon, Jan 5, 2015 at 11:11 AM, John Baker <jba...@javasystemsolutions.com> wrote: > Wes > > I can't see why anyone would use an installer over installing the latest > supported version of Tomcat, ie the latest version of Tomcat 7, and > dropping the Mid Tier war file into Tomcat/webapps (renaming arsys.war). > These are great learning steps if you've not done them before, and about > 5 minutes of effort if you have. I'd always deploy the latest (ie most > secure/patched) version of Tomcat, not a packaged version that could be > six months out of date. > > > John > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
