top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration

Tomcat: Behavior changed from 5.x to 7.x

+2 votes
66 views

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 .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 .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. :(

posted Nov 17, 2013 by Abhay Kulkarni

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

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.

answer Nov 17, 2013 by Jai Prakash
Similar Questions
0 votes

Is there a way by which we can handle the tomcat deployment of war files from a central location via a Web UI screen ?

I 'm aware of PROBE (http://code.google.com/p/psi-probe/) by which we can do the deployment from a Web UI screen but for that we need to individually deploy the Probe.war across all instances .

Is there a way out by which we can handle the tomcat deployments from a central location ( i.e by avoiding deploying probe.war on all instances) on to different physical machines.

Please suggest & share your valuable thoughts

+1 vote

I was just wondering, if we do have a method to perform remote deployment.

I did take a look at the code for the Tomcat deployer and as per my understanding, it performs a HTTP PUT request, with the deployment file, to the Manager application to further perform the deployment.

If for some reason, the Manager application is / can not be deployed, is there still a way to achieve remote deployment on to Tomcat? Or is it a must, that we must be having Manager application deployed to deploy applications remotely?

0 votes

We are using tomcat 7.X for our project. So far we deploy only one application in tomcat.

Now we are planning to deploy one more application with existing one.

There is requirement that failure of deployment of new application should not affect existing application deployment and tomcat startup. As per my understanding, If any application deployment fails, Tomcat startup will fail.

Please let us know if there is any way to start the tomcat in case of failure of one application deployment also.

0 votes

Does heartbleeding bug impact on Tomcat 6.x, 7.x and 8.x ? I noticed that Tomcat native connector version 1.1.22 uses : OpenSSL 0.9.8 which doesn't have the heartbleeding bug, but 1.1.24 and 1.1.29 also include the buggy openssl.

How can I find which version of Tomcat uses which version of Tomcat native connector ? For example, how can I figure out which version of Tomcat native connector is used by Tomcat 7.0 build 47.

Contact Us
+91 9880187415
sales@queryhome.net
support@queryhome.net
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Bangalore-560102
Karnataka INDIA.
QUERY HOME
...