Chris,
On Fri, Aug 22, 2014 at 4:50 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > > So just write a batch script that looks like this: > > @ECHO OFF > SET CATALINA_BASE=whatever > SET CATALINA_HOME=whatever > > CALL %CATALINA_HOME%\bin\catalina.sh start > You meant of course: CALL %CATALINA_HOME%\bin\catalina.bat start (Windows catalina.bat, Linux/Mac catalina.sh) > > Name it tomcat-start-environmentX.bat and create one for each > environment. If you want to be able to start/stop them, etc. then you > can use bin\startup.bat for an example of how to copy command-line > arguments from the current script and pass them to another (hint: it's > not as easy as it is in a *NIX shell). > > I wouldn't ever recommend setting CATALINA_HOME and CATALINA_BASE > globally. If you want to use multiple environments without installing > a Windows Servics or writing your own wrappers, etc. then you *must* > use the environment variables to control where Tomcat looks for things. > > +1 Agreed - that's what I suggested as well - do not set up these environment variables globally, just set them in your startup script for that execution only. Btw, the only variables that I set up globally on my system are JAVA_HOME and PATH, since I use them for other purposes, too - not just starting up Tomcat instances. It's useful to have %JAVA_HOME%\bin on your %Path% (as the first thing in the list, before %SystemRoot% and other windows default paths). Cheers! Neven
