You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Theparanoidone Theparanoidone <th...@yahoo.com> on 2008/06/12 21:14:01 UTC
Farm War Deployer / Deploment Strategies
Hola~
I'm looking for an efficient way to deploy a tomcat project to 2 or more tomcat servers simultaneously.
Changes to are tomcat project may affect the way it communicates with a database, and therefore we'd like to make sure the deployment takes place swiftly.
What are some of the better ways to deploy a project to multiple servers???
According to this link from 2007, the farm war deployer is broken... but it hints at other methods:
http://marc.info/?l=tomcat-user&m=117345255505224&w=2
It also seems to state it's still broken in the docs here:
http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-deployer.html
What are some of the better ways to deploy a project to multiple servers???
Thoughts?
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Farm War Deployer / Deploment Strategies
Posted by Johnny Kewl <jo...@kewlstuff.co.za>.
----- Original Message -----
From: "Theparanoidone Theparanoidone" <th...@yahoo.com>
To: <us...@tomcat.apache.org>
Sent: Thursday, June 12, 2008 9:14 PM
Subject: Farm War Deployer / Deploment Strategies
> Hola~
>
> I'm looking for an efficient way to deploy a tomcat project to 2 or more
> tomcat servers simultaneously.
>
> Changes to are tomcat project may affect the way it communicates with a
> database, and therefore we'd like to make sure the deployment takes place
> swiftly.
>
> What are some of the better ways to deploy a project to multiple
> servers???
>
>
>
> According to this link from 2007, the farm war deployer is broken... but
> it hints at other methods:
> http://marc.info/?l=tomcat-user&m=117345255505224&w=2
>
> It also seems to state it's still broken in the docs here:
> http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-deployer.html
>
Oh sorry, my previous post assumed you were using sticky sessions... didnt
realize you clustering (persisting sessions), and to be honest I'd almost
forgotten it was there, looked at it along time ago and decided sticky is
for me ;)
I think heres your answer...
http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-deployer.html
Maybe sticky is also for you ;)
This is the article I read yonks ago.. and decided I can live with sticky...
http://www.onjava.com/pub/a/onjava/2004/11/24/replication1.html
Good luck!
---------------------------------------------------------------------------
HARBOR : http://www.kewlstuff.co.za/index.htm
The most powerful application server on earth.
The only real POJO Application Server.
See it in Action : http://www.kewlstuff.co.za/cd_tut_swf/whatisejb1.htm
---------------------------------------------------------------------------
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Farm War Deployer / Deploment Strategies
Posted by Johnny Kewl <jo...@kewlstuff.co.za>.
----- Original Message -----
From: "Theparanoidone Theparanoidone" <th...@yahoo.com>
To: <us...@tomcat.apache.org>
Sent: Thursday, June 12, 2008 9:14 PM
Subject: Farm War Deployer / Deploment Strategies
> Hola~
>
> I'm looking for an efficient way to deploy a tomcat project to 2 or more
> tomcat servers simultaneously.
>
> Changes to are tomcat project may affect the way it communicates with a
> database, and therefore we'd like to make sure the deployment takes place
> swiftly.
>
> What are some of the better ways to deploy a project to multiple
> servers???
With JK, the right way is from JKStatus, stop the servers.
Change dB
Then deploy new war...
Then bring them back one by one....
If its not JK, then I guess you have to stop them from the manager/html
If that dB change, is huge and needs translating/restructuring... thats the
big down time.
dB's are always a mission, you end up wrting a lot of script, or little util
programs to make the change go as fast as possible.
When its just a content change, we just drop the wars in and let each tomcat
wake itself up and do the change when its ready.
Not sure if we doing it right, but have had no problems.
Have fun...
---------------------------------------------------------------------------
HARBOR : http://www.kewlstuff.co.za/index.htm
The most powerful application server on earth.
The only real POJO Application Server.
See it in Action : http://www.kewlstuff.co.za/cd_tut_swf/whatisejb1.htm
---------------------------------------------------------------------------
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org