You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Zhenxin wang <zh...@docomolabs-usa.com> on 2002/08/06 01:45:13 UTC
deployment using the manager app
Hi,
While Tomcat 4.0.4 is running, I deployed a new application with the "manager" from a war file, everything looks good and the the newly installed app is accessible from the browser. But, I checked the directory of webapps, there is no newly created directory, and there is no change to the conf/server.xml file either (no newly added context for the installed app). If it is the corrrect behavior, that means this dynamic deployment is only transient.
Then, I shutdown the server and restarted, the newly installed app is not accessible anymore.
I wonder why is it not made persistent, what are the issues?
How can I make it persistent? (By creating directory and modify server.xml file?)
--Zhenxin Wang
DoCoMo Labs USA
Re: deployment using the manager app
Posted by Dan Sandberg <x...@cs.stanford.edu>.
Sorry, I misunderstood your problem. You have to create that directory
and copy the files there yourself ( I use scp + manager depoy together
in a script ).
I see your point -- It should be an easy change to make so the directory
that Tomcat deploys the webapp to is one that is under the appBase
directory.
Anyone know where this code is? Is this implemented alreadyin 4.1?
-Dan
Zhenxin wang wrote:
>Hi, Dan
>
>Thanks for the reply. For what you mentioned in the first paragraph, can you
>explain in a bit more detail how can I make the manager to create the right
>directories? I can bear with the limitatations about the directory names.
>
>--Zhenxin
>
>
>----- Original Message -----
>From: "Dan Sandberg" <x...@cs.stanford.edu>
>To: "Tomcat Developers List" <to...@jakarta.apache.org>
>Sent: Monday, August 05, 2002 5:00 PM
>Subject: Re: deployment using the manager app
>
>
>
>
>>The easiest way to deal with this is to tell the manager to deploy the
>>webapp into whichever directory is specified as the 'appBase' in the
>>Host tag of server.xml.
>>
>>Since apps that are under that directory are automatically deployed,
>>you're all set.
>>
>>The limitations are that the context name will be the same as the
>>directory name, and that you can only have one 'appBase' directory.
>>
>>We should put this in a FAQ -- I was wondering the same thing a few
>>weeks ago.
>>
>>-Dan
>>
>>Zhenxin wang wrote:
>>
>>
>>
>>>Hi,
>>>
>>>While Tomcat 4.0.4 is running, I deployed a new application with the
>>>
>>>
>"manager" from a war file, everything looks good and the the newly installed
>app is accessible from the browser. But, I checked the directory of webapps,
>there is no newly created directory, and there is no change to the
>conf/server.xml file either (no newly added context for the installed app).
>If it is the corrrect behavior, that means this dynamic deployment is only
>transient.
>
>
>>>Then, I shutdown the server and restarted, the newly installed app is not
>>>
>>>
>accessible anymore.
>
>
>>>I wonder why is it not made persistent, what are the issues?
>>>How can I make it persistent? (By creating directory and modify
>>>
>>>
>server.xml file?)
>
>
>>>--Zhenxin Wang
>>>DoCoMo Labs USA
>>>
>>>
>>>
>>>
>>>
>>
>>
>>--
>>To unsubscribe, e-mail:
>>
>>
><ma...@jakarta.apache.org>
>
>
>>For additional commands, e-mail:
>>
>>
><ma...@jakarta.apache.org>
>
>
>>
>>
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: deployment using the manager app
Posted by Zhenxin wang <zh...@docomolabs-usa.com>.
Hi, Dan
Thanks for the reply. For what you mentioned in the first paragraph, can you
explain in a bit more detail how can I make the manager to create the right
directories? I can bear with the limitatations about the directory names.
--Zhenxin
----- Original Message -----
From: "Dan Sandberg" <x...@cs.stanford.edu>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Sent: Monday, August 05, 2002 5:00 PM
Subject: Re: deployment using the manager app
> The easiest way to deal with this is to tell the manager to deploy the
> webapp into whichever directory is specified as the 'appBase' in the
> Host tag of server.xml.
>
> Since apps that are under that directory are automatically deployed,
> you're all set.
>
> The limitations are that the context name will be the same as the
> directory name, and that you can only have one 'appBase' directory.
>
> We should put this in a FAQ -- I was wondering the same thing a few
> weeks ago.
>
> -Dan
>
> Zhenxin wang wrote:
>
> >Hi,
> >
> >While Tomcat 4.0.4 is running, I deployed a new application with the
"manager" from a war file, everything looks good and the the newly installed
app is accessible from the browser. But, I checked the directory of webapps,
there is no newly created directory, and there is no change to the
conf/server.xml file either (no newly added context for the installed app).
If it is the corrrect behavior, that means this dynamic deployment is only
transient.
> >
> >Then, I shutdown the server and restarted, the newly installed app is not
accessible anymore.
> >I wonder why is it not made persistent, what are the issues?
> >How can I make it persistent? (By creating directory and modify
server.xml file?)
> >
> >--Zhenxin Wang
> >DoCoMo Labs USA
> >
> >
> >
>
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: deployment using the manager app
Posted by Dan Sandberg <x...@cs.stanford.edu>.
The easiest way to deal with this is to tell the manager to deploy the
webapp into whichever directory is specified as the 'appBase' in the
Host tag of server.xml.
Since apps that are under that directory are automatically deployed,
you're all set.
The limitations are that the context name will be the same as the
directory name, and that you can only have one 'appBase' directory.
We should put this in a FAQ -- I was wondering the same thing a few
weeks ago.
-Dan
Zhenxin wang wrote:
>Hi,
>
>While Tomcat 4.0.4 is running, I deployed a new application with the "manager" from a war file, everything looks good and the the newly installed app is accessible from the browser. But, I checked the directory of webapps, there is no newly created directory, and there is no change to the conf/server.xml file either (no newly added context for the installed app). If it is the corrrect behavior, that means this dynamic deployment is only transient.
>
>Then, I shutdown the server and restarted, the newly installed app is not accessible anymore.
>I wonder why is it not made persistent, what are the issues?
>How can I make it persistent? (By creating directory and modify server.xml file?)
>
>--Zhenxin Wang
>DoCoMo Labs USA
>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: servlet and jsp application scope variable problem (easy?)
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Tue, 6 Aug 2002, Richard Diaz wrote:
> Date: Tue, 6 Aug 2002 19:58:52 -0700 (PDT)
> From: Richard Diaz <ri...@yahoo.com>
> Reply-To: Tomcat Users List <to...@jakarta.apache.org>
> To: Tomcat Users List <to...@jakarta.apache.org>
> Subject: servlet and jsp application scope variable problem (easy?)
>
> in my servlet I create an application scope object and
> set its values. While -in- the servlet these values
> are correct. However, when I reference the application
> scope object in a JSP page (or in another servlet) all
> of its values are ZERO, not what I set them to.
>
> I -can- set the values of these object with JSP pages
> and the values STAY but I am using MVC and I don't
> want to give control to my JSP pages.
>
> I am having NO problems with my session variables.
>
> code in the SERVLET file:
>
> import myDomain.base.*;
> ...
> ServletContext context = getServletContext();
> ...
> Max TwcMax = new myDomain.base.Max();
> ...
> TwcMax.setbookmarks (99);
> ...
> context.setAttribute("myDomain.base.Max", TwcMax);
> ...
>
> Code in the JSP FILE:
> ...
> <jsp:useBean id="TwcMax" scope="application"
> class="myDomain.base.Max" />
> ...
> <% TwcMax.setbookmarks(44); %>
> ...
The name you use in the "id" attribute of a <jsp:useBean> must match the
attribute name under which you store your attribute. Change your servlet
statement to:
context.setAttribute("TwcMax", TwcMax);
and you'll have a lot better luck.
>
> I think that's all the code you need, I hope this is
> an easy problem, many thanks in advance for your
> help...
> Richard Diaz
Craig
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
servlet and jsp application scope variable problem (easy?)
Posted by Richard Diaz <ri...@yahoo.com>.
in my servlet I create an application scope object and
set its values. While -in- the servlet these values
are correct. However, when I reference the application
scope object in a JSP page (or in another servlet) all
of its values are ZERO, not what I set them to.
I -can- set the values of these object with JSP pages
and the values STAY but I am using MVC and I don't
want to give control to my JSP pages.
I am having NO problems with my session variables.
code in the SERVLET file:
import myDomain.base.*;
...
ServletContext context = getServletContext();
...
Max TwcMax = new myDomain.base.Max();
...
TwcMax.setbookmarks (99);
...
context.setAttribute("myDomain.base.Max", TwcMax);
...
Code in the JSP FILE:
...
<jsp:useBean id="TwcMax" scope="application"
class="myDomain.base.Max" />
...
<% TwcMax.setbookmarks(44); %>
...
I think that's all the code you need, I hope this is
an easy problem, many thanks in advance for your
help...
Richard Diaz
=====
__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: deployment using the manager app
Posted by Zhenxin wang <zh...@docomolabs-usa.com>.
Hi, Craig
You are right. I tried the deploy from the browser, which is handled by the
goGet.
I forgot to check the doPut.
--Zhenxin
----- Original Message -----
From: "Craig R. McClanahan" <cr...@apache.org>
To: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Tuesday, August 06, 2002 7:04 PM
Subject: Re: deployment using the manager app
>
>
> On Tue, 6 Aug 2002, Zhenxin wang wrote:
>
> > Date: Tue, 6 Aug 2002 18:18:48 -0700
> > From: Zhenxin wang <zh...@docomolabs-usa.com>
> > Reply-To: Tomcat Users List <to...@jakarta.apache.org>
> > To: Tomcat Users List <to...@jakarta.apache.org>
> > Subject: Re: deployment using the manager app
> >
> > I just installe the Tomcat4.1.8, try the manager app and it does not
have
> > the "deploy" command.
> > After checking the code, that seems to be case.
> > So how can i do it with manager, if want to persistently and dynamically
> > deploy a new app?
> >
>
> Tomcat 4.1.8 definitely includes the deploy functionality -- but it is in
> doPut(), not doGet(), and it only works with client software that can
> issue an HTTP PUT command (like the custom Ant task
> "org.apache.catalina.ant.DeployTask").
>
> If you look at the source code for ManagerServlet starting at line 408
> (the comment is "// Saving configuration") you will see the logic to save
> the updated version of server.xml after a deploy occurs. There is similar
> logic in the undeploy() method. Therefore, applications deployed and
> undeployed using these mechanisms will indeed cause server.xml to be
> updated appropriately.
>
> > Thanks!
> >
> > --Zhenxin
>
> Craig
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: deployment using the manager app
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Tue, 6 Aug 2002, Zhenxin wang wrote:
> Date: Tue, 6 Aug 2002 18:18:48 -0700
> From: Zhenxin wang <zh...@docomolabs-usa.com>
> Reply-To: Tomcat Users List <to...@jakarta.apache.org>
> To: Tomcat Users List <to...@jakarta.apache.org>
> Subject: Re: deployment using the manager app
>
> I just installe the Tomcat4.1.8, try the manager app and it does not have
> the "deploy" command.
> After checking the code, that seems to be case.
> So how can i do it with manager, if want to persistently and dynamically
> deploy a new app?
>
Tomcat 4.1.8 definitely includes the deploy functionality -- but it is in
doPut(), not doGet(), and it only works with client software that can
issue an HTTP PUT command (like the custom Ant task
"org.apache.catalina.ant.DeployTask").
If you look at the source code for ManagerServlet starting at line 408
(the comment is "// Saving configuration") you will see the logic to save
the updated version of server.xml after a deploy occurs. There is similar
logic in the undeploy() method. Therefore, applications deployed and
undeployed using these mechanisms will indeed cause server.xml to be
updated appropriately.
> Thanks!
>
> --Zhenxin
Craig
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: deployment using the manager app
Posted by Zhenxin wang <zh...@docomolabs-usa.com>.
I just installe the Tomcat4.1.8, try the manager app and it does not have
the "deploy" command.
After checking the code, that seems to be case.
So how can i do it with manager, if want to persistently and dynamically
deploy a new app?
Thanks!
--Zhenxin
----- Original Message -----
From: "Jacob Kjome" <ho...@visi.com>
To: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Tuesday, August 06, 2002 4:46 PM
Subject: Re: deployment using the manager app
>
> Whoops. I just realized you are using Tomcat-4.0.4. I am not so sure
> about that version. I skipped it altogether and moved on to the latest
and
> greatest in Tomcat-4.1.x. Currently, I use Tomcat-4.1.8 which does have
> deploy/undeploy.
>
> In fact, there are ant tasks that come with 4.1.x that do this for
> you. The tasks are contained in catalina-ant.jar in
> $CATALINA_HOME/server/lib. Just move those to $ANT_HOME/lib and you are
set.
>
> If you want a sample build file which has those tasks set up, I can send
> that to you. Otherwise, you can use the manager directly like, I imagine,
> you are doing now.
>
> Let me know if you have any problems.
>
> Jake
>
> At 10:10 AM 8/6/2002 -0700, you wrote:
> >Hi, Jade
> >
> >Thanks for the reply.
> >Looks like the manager app does not have the deploy/undeploy commands.
> >Does the deploy/undeploy functionality exist somewhere in Tomcat?
> >
> >--Zhenxin
> >
> >----- Original Message -----
> >From: "Jacob Kjome" <ho...@visi.com>
> >To: "Tomcat Users List" <to...@jakarta.apache.org>
> >Sent: Monday, August 05, 2002 8:29 PM
> >Subject: Re: deployment using the manager app
> >
> >
> > > The key word here is "installed". If you use the manager
install/remove
> > > tasks, the app will only exist in memory. There is no modification to
the
> > > server.xml or anything to persist it across server restarts. What you
> >want
> > > is the deploy/undploy tasks. Make sure to make a backup of
server.xml,
> > > though, because the server.xml will physically be modified and all
> >comments
> > > will be removed. An application set up using "deploy" *will* persist
> > > across server restarts.
> > >
> > > Jake
> > >
> > > At 04:45 PM 8/5/2002 -0700, you wrote:
> > > >Hi,
> > > >
> > > >While Tomcat 4.0.4 is running, I deployed a new application with the
> > > >"manager" from a war file, everything looks good and the the newly
> > > >installed app is accessible from the browser. But, I checked the
> >directory
> > > >of webapps, there is no newly created directory, and there is no
change
> >to
> > > >the conf/server.xml file either (no newly added context for the
installed
> > > >app). If it is the corrrect behavior, that means this dynamic
deployment
> > > >is only transient.
> > > >
> > > >Then, I shutdown the server and restarted, the newly installed app is
not
> > > >accessible anymore.
> > > >I wonder why is it not made persistent, what are the issues?
> > > >How can I make it persistent? (By creating directory and modify
> >server.xml
> > > >file?)
> > > >
> > > >--Zhenxin Wang
> > > >DoCoMo Labs USA
> > >
> >
> >
> >--
> >To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> >For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: deployment using the manager app
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Tue, 6 Aug 2002, Jacob Kjome wrote:
> Date: Tue, 06 Aug 2002 18:46:00 -0500
> From: Jacob Kjome <ho...@visi.com>
> Reply-To: Tomcat Users List <to...@jakarta.apache.org>
> To: Tomcat Users List <to...@jakarta.apache.org>
> Subject: Re: deployment using the manager app
>
>
> Whoops. I just realized you are using Tomcat-4.0.4. I am not so sure
> about that version. I skipped it altogether and moved on to the latest and
> greatest in Tomcat-4.1.x. Currently, I use Tomcat-4.1.8 which does have
> deploy/undeploy.
>
> In fact, there are ant tasks that come with 4.1.x that do this for
> you. The tasks are contained in catalina-ant.jar in
> $CATALINA_HOME/server/lib. Just move those to $ANT_HOME/lib and you are set.
>
> If you want a sample build file which has those tasks set up, I can send
> that to you. Otherwise, you can use the manager directly like, I imagine,
> you are doing now.
>
There is also a model build.xml file incorporating these tasks, documented
in the "Application Developer's Guide" documentation that comes with
Tomcat 4.1. Among other things, this one takes pains to set up your
compilation classpath to be similar to the environment that your webapp
will see at runtime -- for example, it puts things like
$CATALINA_HOME/common/lib and $CATALINA_HOME/shared/lib on the compile
class path for you, in the same order that the Catalina class loaders will
see them at runtime.
On a stock install of Tomcat 4.1, this Guide is available at
<http://localhost:8080/tomcat-docs/appdev/>.
> Let me know if you have any problems.
>
> Jake
>
Craig
> At 10:10 AM 8/6/2002 -0700, you wrote:
> >Hi, Jade
> >
> >Thanks for the reply.
> >Looks like the manager app does not have the deploy/undeploy commands.
> >Does the deploy/undeploy functionality exist somewhere in Tomcat?
> >
> >--Zhenxin
> >
> >----- Original Message -----
> >From: "Jacob Kjome" <ho...@visi.com>
> >To: "Tomcat Users List" <to...@jakarta.apache.org>
> >Sent: Monday, August 05, 2002 8:29 PM
> >Subject: Re: deployment using the manager app
> >
> >
> > > The key word here is "installed". If you use the manager install/remove
> > > tasks, the app will only exist in memory. There is no modification to the
> > > server.xml or anything to persist it across server restarts. What you
> >want
> > > is the deploy/undploy tasks. Make sure to make a backup of server.xml,
> > > though, because the server.xml will physically be modified and all
> >comments
> > > will be removed. An application set up using "deploy" *will* persist
> > > across server restarts.
> > >
> > > Jake
> > >
> > > At 04:45 PM 8/5/2002 -0700, you wrote:
> > > >Hi,
> > > >
> > > >While Tomcat 4.0.4 is running, I deployed a new application with the
> > > >"manager" from a war file, everything looks good and the the newly
> > > >installed app is accessible from the browser. But, I checked the
> >directory
> > > >of webapps, there is no newly created directory, and there is no change
> >to
> > > >the conf/server.xml file either (no newly added context for the installed
> > > >app). If it is the corrrect behavior, that means this dynamic deployment
> > > >is only transient.
> > > >
> > > >Then, I shutdown the server and restarted, the newly installed app is not
> > > >accessible anymore.
> > > >I wonder why is it not made persistent, what are the issues?
> > > >How can I make it persistent? (By creating directory and modify
> >server.xml
> > > >file?)
> > > >
> > > >--Zhenxin Wang
> > > >DoCoMo Labs USA
> > >
> >
> >
> >--
> >To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> >For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: deployment using the manager app
Posted by Jacob Kjome <ho...@visi.com>.
Whoops. I just realized you are using Tomcat-4.0.4. I am not so sure
about that version. I skipped it altogether and moved on to the latest and
greatest in Tomcat-4.1.x. Currently, I use Tomcat-4.1.8 which does have
deploy/undeploy.
In fact, there are ant tasks that come with 4.1.x that do this for
you. The tasks are contained in catalina-ant.jar in
$CATALINA_HOME/server/lib. Just move those to $ANT_HOME/lib and you are set.
If you want a sample build file which has those tasks set up, I can send
that to you. Otherwise, you can use the manager directly like, I imagine,
you are doing now.
Let me know if you have any problems.
Jake
At 10:10 AM 8/6/2002 -0700, you wrote:
>Hi, Jade
>
>Thanks for the reply.
>Looks like the manager app does not have the deploy/undeploy commands.
>Does the deploy/undeploy functionality exist somewhere in Tomcat?
>
>--Zhenxin
>
>----- Original Message -----
>From: "Jacob Kjome" <ho...@visi.com>
>To: "Tomcat Users List" <to...@jakarta.apache.org>
>Sent: Monday, August 05, 2002 8:29 PM
>Subject: Re: deployment using the manager app
>
>
> > The key word here is "installed". If you use the manager install/remove
> > tasks, the app will only exist in memory. There is no modification to the
> > server.xml or anything to persist it across server restarts. What you
>want
> > is the deploy/undploy tasks. Make sure to make a backup of server.xml,
> > though, because the server.xml will physically be modified and all
>comments
> > will be removed. An application set up using "deploy" *will* persist
> > across server restarts.
> >
> > Jake
> >
> > At 04:45 PM 8/5/2002 -0700, you wrote:
> > >Hi,
> > >
> > >While Tomcat 4.0.4 is running, I deployed a new application with the
> > >"manager" from a war file, everything looks good and the the newly
> > >installed app is accessible from the browser. But, I checked the
>directory
> > >of webapps, there is no newly created directory, and there is no change
>to
> > >the conf/server.xml file either (no newly added context for the installed
> > >app). If it is the corrrect behavior, that means this dynamic deployment
> > >is only transient.
> > >
> > >Then, I shutdown the server and restarted, the newly installed app is not
> > >accessible anymore.
> > >I wonder why is it not made persistent, what are the issues?
> > >How can I make it persistent? (By creating directory and modify
>server.xml
> > >file?)
> > >
> > >--Zhenxin Wang
> > >DoCoMo Labs USA
> >
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: deployment using the manager app
Posted by Zhenxin wang <zh...@docomolabs-usa.com>.
Hi, Jade
Thanks for the reply.
Looks like the manager app does not have the deploy/undeploy commands.
Does the deploy/undeploy functionality exist somewhere in Tomcat?
--Zhenxin
----- Original Message -----
From: "Jacob Kjome" <ho...@visi.com>
To: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Monday, August 05, 2002 8:29 PM
Subject: Re: deployment using the manager app
> The key word here is "installed". If you use the manager install/remove
> tasks, the app will only exist in memory. There is no modification to the
> server.xml or anything to persist it across server restarts. What you
want
> is the deploy/undploy tasks. Make sure to make a backup of server.xml,
> though, because the server.xml will physically be modified and all
comments
> will be removed. An application set up using "deploy" *will* persist
> across server restarts.
>
> Jake
>
> At 04:45 PM 8/5/2002 -0700, you wrote:
> >Hi,
> >
> >While Tomcat 4.0.4 is running, I deployed a new application with the
> >"manager" from a war file, everything looks good and the the newly
> >installed app is accessible from the browser. But, I checked the
directory
> >of webapps, there is no newly created directory, and there is no change
to
> >the conf/server.xml file either (no newly added context for the installed
> >app). If it is the corrrect behavior, that means this dynamic deployment
> >is only transient.
> >
> >Then, I shutdown the server and restarted, the newly installed app is not
> >accessible anymore.
> >I wonder why is it not made persistent, what are the issues?
> >How can I make it persistent? (By creating directory and modify
server.xml
> >file?)
> >
> >--Zhenxin Wang
> >DoCoMo Labs USA
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: deployment using the manager app
Posted by Jacob Kjome <ho...@visi.com>.
The key word here is "installed". If you use the manager install/remove
tasks, the app will only exist in memory. There is no modification to the
server.xml or anything to persist it across server restarts. What you want
is the deploy/undploy tasks. Make sure to make a backup of server.xml,
though, because the server.xml will physically be modified and all comments
will be removed. An application set up using "deploy" *will* persist
across server restarts.
Jake
At 04:45 PM 8/5/2002 -0700, you wrote:
>Hi,
>
>While Tomcat 4.0.4 is running, I deployed a new application with the
>"manager" from a war file, everything looks good and the the newly
>installed app is accessible from the browser. But, I checked the directory
>of webapps, there is no newly created directory, and there is no change to
>the conf/server.xml file either (no newly added context for the installed
>app). If it is the corrrect behavior, that means this dynamic deployment
>is only transient.
>
>Then, I shutdown the server and restarted, the newly installed app is not
>accessible anymore.
>I wonder why is it not made persistent, what are the issues?
>How can I make it persistent? (By creating directory and modify server.xml
>file?)
>
>--Zhenxin Wang
>DoCoMo Labs USA