You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Nehal Sangoi <ne...@patni.com> on 2005/10/24 11:48:35 UTC
Do not want change into the warfile name
Hi All,
I need to deploy only one warfile. e.g = "example.war" to multiple tomcat
instances having different context names. Currently, i am using ant's build
script with manager deployer.
Hence, while deploying the warfile to multiple instances, in the "webapps"
of every instance, the war file's name gets changed to what the context name
is provided into the build script.
This means, if i have a context named " clay " , then the existing warfile "
example.war " gets renamed to "clay.war" and gets deployed under the webapps
of clay tomcat instance.
Kidnly, help me -- how can i configure manager deploy, for not having my
warfile name changed according to context detail.
Thanks & Regards,
Nehal
RE: Do not want change into the warfile name
Posted by Nehal Sangoi <ne...@patni.com>.
I need to retain the original name of war file for further use in
Load-Balancing and Clustering.
Thank you for the information provided.
In my ANT script, i changed the "url". Context Path i kept same for all the
urls and it worked fine.
Thanks once again, to all who replied to my query.
-----Original Message-----
From: David Delbecq [mailto:delbd@oma.be]
Sent: Monday, October 24, 2005 3:37 PM
To: Tomcat Users List
Subject: Re: Do not want change into the warfile name
Well contexts are used to name web applications
web applications are accessed using
http://host:port/contextName/
That is if you set context to 'clay', it's the
expected behaviour it's accessible using
http://host:port/clay/
For this, war is stored on server using name 'clay.war'
If it was to be named 'example.war' then it would
be accessible using http://host:port/example and
it's context would be example, not clay.
Am not sure why you want the war not be named
with context name, as it's the expected behaviour
of tomcat.
Nehal Sangoi a écrit :
>Hi All,
>
>I need to deploy only one warfile. e.g = "example.war" to multiple tomcat
>instances having different context names. Currently, i am using ant's build
>script with manager deployer.
>
>Hence, while deploying the warfile to multiple instances, in the "webapps"
>of every instance, the war file's name gets changed to what the context
name
>is provided into the build script.
>
>This means, if i have a context named " clay " , then the existing warfile
"
>example.war " gets renamed to "clay.war" and gets deployed under the
webapps
>of clay tomcat instance.
>
>Kidnly, help me -- how can i configure manager deploy, for not having my
>warfile name changed according to context detail.
>
>
>Thanks & Regards,
>Nehal
>
>
>
>
>------------------------------------------------------------------------
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Do not want change into the warfile name
Posted by David Delbecq <de...@oma.be>.
Well contexts are used to name web applications
web applications are accessed using
http://host:port/contextName/
That is if you set context to 'clay', it's the
expected behaviour it's accessible using
http://host:port/clay/
For this, war is stored on server using name 'clay.war'
If it was to be named 'example.war' then it would
be accessible using http://host:port/example and
it's context would be example, not clay.
Am not sure why you want the war not be named
with context name, as it's the expected behaviour
of tomcat.
Nehal Sangoi a écrit :
>Hi All,
>
>I need to deploy only one warfile. e.g = "example.war" to multiple tomcat
>instances having different context names. Currently, i am using ant's build
>script with manager deployer.
>
>Hence, while deploying the warfile to multiple instances, in the "webapps"
>of every instance, the war file's name gets changed to what the context name
>is provided into the build script.
>
>This means, if i have a context named " clay " , then the existing warfile "
>example.war " gets renamed to "clay.war" and gets deployed under the webapps
>of clay tomcat instance.
>
>Kidnly, help me -- how can i configure manager deploy, for not having my
>warfile name changed according to context detail.
>
>
>Thanks & Regards,
>Nehal
>
>
>
>
>------------------------------------------------------------------------
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Block HTTP Connector Port in server.xml and still use manager deployer for Tomcat Deployments
Posted by Nehal Sangoi <ne...@patni.com>.
Hi All,
I have a Tomcat Server (5.5.9) and an Apache webserver. These are physically
two different machines. I want to do application deployments in Tomcat using
Manager-Deploy Ant Build Script. But, does not want to use Tomcat's HTTP
Connector Port found in server.xml.
Basically, for some reasons, we need to block that port.
How can i use Apache webserver's port for manager deployer and deploy the
applications?
Kindly, help me.
And, Thanks in advance.
Regds,
Nehal
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Réf. : Do not want change into the warfile name
Posted by Richard Leotard <Ri...@exane.com>.
Hi
If you do not want to jave your context rename, you need to specify it in the manager application
"Nehal Sangoi" <ne...@patni.com>
24/10/2005 11:48
Veuillez répondre à "Tomcat Users List"
Pour : "'Tomcat Users List'" <us...@tomcat.apache.org>
cc : (ccc : Richard Leotard/Dev_middle/Paris/Exane)
Objet : Do not want change into the warfile name
*** Ce message vous a été émis sur Internet par
users-return-134830-Richard.Leotard=exane.com@tomcat.apache.org / Message sent through Internet by
users-return-134830-Richard.Leotard=exane.com@tomcat.apache.org ***
Hi All,
I need to deploy only one warfile. e.g = "example.war" to multiple tomcat
instances having different context names. Currently, i am using ant's
build
script with manager deployer.
Hence, while deploying the warfile to multiple instances, in the "webapps"
of every instance, the war file's name gets changed to what the context
name
is provided into the build script.
This means, if i have a context named " clay " , then the existing warfile "
example.war " gets renamed to "clay.war" and gets deployed under the
webapps
of clay tomcat instance.
Kidnly, help me -- how can i configure manager deploy, for not having my
warfile name changed according to context detail.
Thanks & Regards,
Nehal
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
___________________________________
The integrity of this message cannot be guaranteed on the internet .Therefore EXANE cannot be considered responsible for the contents.
If you are not the intended recipient of this message ,please delete it and notify the sender.
This message is provided for information purposes only and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments
Although it may contain some elements from publications produced by Exane's research department ,this message is not research.
Please consult our web site for important disclaimers and disclosures concerning Exane's research (http://www.exane.com)
___________________________________