You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Iain Downie <ia...@bto.org> on 2003/12/05 13:44:36 UTC
2 instances of Tomcat
Hi List,
I found some info on this on web and faqs, but I think my question is a bit
different from the general 2 instances discussions I have found.
Red Hat 7.2 Linux
JDK 1.3.1
Tomcat 4.0.3
All run smoothly. I need to install some WorldPay stuff for testing and
live. They assure me that their servlets will not work on JDK1.3.0+, and
more importantly, will not run on anything above Tomcat 3.2.4.
Can I install this lower Tomcat and a lower JDK? I think I can get away no
bother with the Tomcat, but what about the JDK. I ask as there are 'env'
variables that are set up as TOMCAT_HOME and JAVA_HOME. I think I can
duplicate TOMCAT_HOME (ie. TOMCAT2_HOME) and cater for it in the start
files, but what about having two JDK?
Iain
____________________________________________
British Trust for Ornithology, The Nunnery,
Thetford, Norfolk IP24 2PU, UK ® Charity No. 216652
BirdWeb Gateway: http://www.bto.org/birdweb
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: 2 instances of Tomcat
Posted by Graham Reeds <gr...@omnieng.co.uk>.
> All run smoothly. I need to install some WorldPay stuff for testing and
> live. They assure me that their servlets will not work on JDK1.3.0+, and
> more importantly, will not run on anything above Tomcat 3.2.4.
WorldPay has a very smooth payment system. Several of the products I have
purchased online uses them. Did you ask whether they plan to upgrade their
payment system to a newer version of TC?
G.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: 2 instances of Tomcat
Posted by Ben Souther <bs...@fwdco.com>.
2 instances of Java shouldn't be a problem. Start your second instance of
Tomcat with a script that sets the JAVA_HOME env variable to point to the
second java dir.
You'll have change the ports on the second tomcat instance.
On Friday 05 December 2003 07:44 am, Iain Downie wrote:
> Hi List,
>
> I found some info on this on web and faqs, but I think my question is a bit
> different from the general 2 instances discussions I have found.
>
> Red Hat 7.2 Linux
> JDK 1.3.1
> Tomcat 4.0.3
>
> All run smoothly. I need to install some WorldPay stuff for testing and
> live. They assure me that their servlets will not work on JDK1.3.0+, and
> more importantly, will not run on anything above Tomcat 3.2.4.
>
> Can I install this lower Tomcat and a lower JDK? I think I can get away no
> bother with the Tomcat, but what about the JDK. I ask as there are 'env'
> variables that are set up as TOMCAT_HOME and JAVA_HOME. I think I can
> duplicate TOMCAT_HOME (ie. TOMCAT2_HOME) and cater for it in the start
> files, but what about having two JDK?
>
> Iain
> ____________________________________________
> British Trust for Ornithology, The Nunnery,
> Thetford, Norfolk IP24 2PU, UK ® Charity No. 216652
> BirdWeb Gateway: http://www.bto.org/birdweb
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
--
Ben Souther
F.W. Davison & Company, Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: 2 instances of Tomcat
Posted by Iain Downie <ia...@bto.org>.
Thanks for the tips, I'll be trying this all out next week.
Iain
----- Original Message -----
From: "Dan Johnsson" <da...@omegapoint.se>
To: "Tomcat Users List" <to...@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
Re: 2 instances of Tomcat
Posted by Dan Johnsson <da...@omegapoint.se>.
> 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