tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Iain Downie" <iain.dow...@bto.org>
Subject Re: 2 instances of Tomcat
Date Mon, 08 Dec 2003 09:03:46 GMT
Thanks for the tips, I'll be trying this all out next week.
Iain

----- Original Message -----
From: "Dan Johnsson" <dan.johnsson@omegapoint.se>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Sent: Friday, December 05, 2003 11:46 PM
Subject: Re: 2 instances of Tomcat


> > what about having two JDK?
> >
> > Iain
>
> As you have identified, this all falls back on having multiple
> production environments (with its own set of installed software of
> specific versions) deployed on the same machine.
>
> The good new is that java is multiple-deploy-enabled. I e, the java
> binaries does not in any way crave a specific install point, a specific
> set of (system global) environment variables being set or anything like
> that.
>
> When consulting enterprising running Java I consistently give this piece
> of advice regarding install-points and environment variables:
>
> * If you have a single production environment on one machine:
> - Prefer a version-dependent install-point (e g c:\j2sdk1.4.2_02 on
> windows) and create a version-independent virtual install-point
> (short-cut c:\j2se).
> - Use a version-independent install-point if you have to
> - Set JAVA_HOME on system level to the version-independent virtual
> install-point.
> - When updating: install the new version at a ('nother)
> version-dependent install-point, redirect your virtual install-point,
> and you're ready to go. You will (of course) have to restart your
> services that use java, but nothing more drastical then that.
>
> * If you have multiple production environments on the same machine
> - Use version-dependent install-points for your different versions
> - Never use version-independent install-points
> - Do not set JAVA_HOME on system level. Instead, set it in the scripts
> that start your different services.
> - When updating: install the new version (at its on install-point), and
> change the service-start scripts.
>
> OK: now you have your JVMs set up. Time to install Tomcat. Good news:
> Tomcat is also multiple-deploy enabled. So, just follow the same rules
> (this time the rule referring to CATALINA_HOME).
>
> [An interesting note: by setting CATALINA_BASE to an external directory,
> you can easily update tomcat and reuse your configurations and logs (as
> long as the format of server.xml have not changed, that is).]
>
> Reboot your machine; start your services; take off
>
> Good luck
>
> Dan Johnsson, System Architect and Security Consultant
> ______________________________________________
> Dan Johnsson               | Säkerhetsarkitekt
> dan.johnsson@omegapoint.se | www.omegapoint.se
> tel 0709-15 88 43          | fax 08-517 008 29
> Omegapoint AB - din säkra punkt i tillvaron
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message