You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Andersen, Bjoern" <bj...@atos.net> on 2013/11/17 12:56:27 UTC
Deployment Problem - behavior changed from 5.x to 7.x
Hi.
I got a Problem with Tomcat deployment. I am using TC 7.0.42, OS: Win2k8r2, J 1.7.0._45.
We used to deploy unpacked webapps (dirs) on a Tomcat 5.0.26 outside the Webapps-dir. We used the manager (web-IF) to deploy these apps, giving the context name and the local directory. The tomcat ran the app from this location. It creates a <contex>.xml in it's config dir.
Now in TC7, the tomcat COPIES the APP from the given location to the default Webapps directory. But we want it to run from where it is, not a copy. One way to archieve this is to manually create a <context>.xml file in the conf/server/localhost dir. But our deployment process needs it to be done via web interface. So, is there any possibility to configure tomcat 7 to behave like tomcat 5 when deploying local webapp directories from outside the webapps dir? I tried autoDeploy and unpackWars to false, but it didn't help. :(
--
Björn Andersen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Deployment Problem - behavior changed from 5.x to 7.x
Posted by "Andersen, Bjoern" <bj...@atos.net>.
Hi Konstantin,
Thanks for your answer.
What I'm trying to do:
Background: The APPs can't be simply undeployed and re-deployed (delete and create) because there are tons of files NOT in the war in several subdirs that are not to be deletet during a release change. So what we do is this:
- We got die APP-Dirs outside Webapps.
- We got a script doing the deployment and several other (non-TC) things. This can only send a html request. So we do this..
- Step1: Undelpoy APP via request against TC manager, like server:port/manager/undeploy?path=/context
It undeploys the APP from TC but does not delete the Dir as it is not in the Webapps dir.
- Step2: Copy the new app in the APP dir and remove old files.
- Step3: Redeploy APP via request against TC manager (->"Deploy a Directory or WAR by URL"),
like server:port/manager/deploy?path=/context&war=file:/path/to/foo
Now, Step 3 is the Problem. In TC5, it would just add the APP to TC as it was before, running from /path/to/foo. A generic foo.xml would be automatically created in the conf subdir. It worked well.
Now, in TC7 with this command, it doesn't run the APP from /path/to/foo any more but instead copies it from /path/to/foo to webapps dir and run it from there. That doesn't work for us. We need the "old" behavior.
Any idea how we can archive this?
--
Bjoern Andersen
-----Original Message-----
From: Konstantin Kolinko [mailto:knst.kolinko@gmail.com]
Sent: Sunday, November 17, 2013 2:51 PM
To: Tomcat Users List
Subject: Re: Deployment Problem - behavior changed from 5.x to 7.x
2013/11/17 Andersen, Bjoern <bj...@atos.net>:
> Hi.
>
> I got a Problem with Tomcat deployment. I am using TC 7.0.42, OS: Win2k8r2, J 1.7.0._45.
>
> We used to deploy unpacked webapps (dirs) on a Tomcat 5.0.26 outside the Webapps-dir. We used the manager (web-IF) to deploy these apps, giving the context name and the local directory. The tomcat ran the app from this location. It creates a <contex>.xml in it's config dir.
>
> Now in TC7, the tomcat COPIES the APP from the given location to the
> default Webapps directory. But we want it to run from where it is, not
> a copy. One way to archieve this is to manually create a <context>.xml
> file in the conf/server/localhost dir. But our deployment process
> needs it to be done via web interface. So, is there any possibility to
> configure tomcat 7 to behave like tomcat 5 when deploying local webapp
> directories from outside the webapps dir? I tried autoDeploy and
> unpackWars to false, but it didn't help. :(
5.0 was deprecated so long ago, that it is beyond my knowledge. What exactly are you trying to do, step by step?
Documentation for the Manager webapp is here:
http://tomcat.apache.org/tomcat-7.0-doc/manager-howto.html#Deploy_A_New_Application_from_a_Local_Path
There exist Ant and Maven front-ends (HTTP clients) for that API which are documented elsewhere.
> But our deployment process needs it to be done via web interface.
Why? What is your deployment process?
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
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: Deployment Problem - behavior changed from 5.x to 7.x
Posted by Konstantin Kolinko <kn...@gmail.com>.
2013/11/17 Andersen, Bjoern <bj...@atos.net>:
> Hi.
>
> I got a Problem with Tomcat deployment. I am using TC 7.0.42, OS: Win2k8r2, J 1.7.0._45.
>
> We used to deploy unpacked webapps (dirs) on a Tomcat 5.0.26 outside the Webapps-dir. We used the manager (web-IF) to deploy these apps, giving the context name and the local directory. The tomcat ran the app from this location. It creates a <contex>.xml in it's config dir.
>
> Now in TC7, the tomcat COPIES the APP from the given location to the default Webapps directory. But we want it to run from where it is, not a copy. One way to archieve this is to manually create a <context>.xml file in the conf/server/localhost dir. But our deployment process needs it to be done via web interface. So, is there any possibility to configure tomcat 7 to behave like tomcat 5 when deploying local webapp directories from outside the webapps dir? I tried autoDeploy and unpackWars to false, but it didn't help. :(
5.0 was deprecated so long ago, that it is beyond my knowledge. What
exactly are you trying to do, step by step?
Documentation for the Manager webapp is here:
http://tomcat.apache.org/tomcat-7.0-doc/manager-howto.html#Deploy_A_New_Application_from_a_Local_Path
There exist Ant and Maven front-ends (HTTP clients) for that API which
are documented elsewhere.
> But our deployment process needs it to be done via web interface.
Why? What is your deployment process?
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org