thank you, /deploy /undeploy work pretty much the same and they fit perfectly my needs.
As for your statement:
> The documentation that I can see (http://jakarta.apache.org/tomcat/tomcat-5.5-doc/manager-howto.html) as well as the deployer tool do not mention install or remove.
i take the liberty to dissent from you.
There are several places in that doc page where install and remove are mentioned. Those statements are taken literally from 4.1 doc and are, i think, a bit misleading.
I attach here a patch for the manager-howto to show how IMHO it should be corrected (english syntax excluded) :)
Pls have a look to it.
Thanks, Gabriele.
Index: manager-howto.xml
===================================================================
RCS file:
/home/cvspublic/jakarta-tomcat-catalina/webapps/docs/manager-howto.xml,v
retrieving revision 1.13
diff -u -r1.13 manager-howto.xml
--- manager-howto.xml 28 Jul 2004 14:49:50 -0000 1.13
+++ manager-howto.xml 20 Dec 2004 14:28:27 -0000
@@ -23,8 +23,8 @@
<blockquote>
<a href="#Deploy A New Application Remotely">Deploy A New Application
Remotely</a><br />
<a href="#Deploy A New Application from a Local Path">Deploy A New Application
from a Local Path</a><br />
-<a href="#List Currently Deployed and Installed Applications">
-List Currently Deployed and Installed Applications</a><br />
+<a href="#List Currently Deployed Applications">
+List Currently Deployed Applications</a><br />
<a href="#Reload An Existing Application">Reload An Existing
Application</a><br />
<a href="#List OS and JVM Properties">List OS and JVM Properties</a><br />
<a href="#List Available Global JNDI Resources">
@@ -64,8 +64,8 @@
<ul>
<li>Deploy a new web application, on a specified context path, from
the uploaded contents of a WAR file.</li>
-<li>Install a new web application, which can be anywhere on the
- server's disks.</li>
+<li>Deploy a new web application, on a specified context path, from the
+ server file system.</li>
<li>List the currently deployed web applications, as well as the
sessions that are currently active for those web apps.</li>
<li>Reload an existing web application, to reflect changes in the
@@ -76,12 +76,11 @@
tools that are preparing <code><ResourceLink></code> elements
nested in a <code><Context></code> deployment description.</li>
<li>List the available security roles defined in the user database.</li>
-<li>Remove an installed web application.</li>
<li>Start a stopped application (thus making it available again).</li>
<li>Stop an existing application (so that it becomes unavailable), but
do not undeploy it.</li>
<li>Undeploy a deployed web application and delete its document base
- directory.</li>
+ directory (unless it was deployed from file system).</li>
</ul>
<p>There are two ways to configure the Manager web application
@@ -272,6 +271,11 @@
have been translated for your platform. The examples below show the English
version of the messages.</p>
+<p><strong>WARNING:</strong> the legacy commands <code>/install</code> and
+<code>/remove</code> are deprecated.
+They are presently equivalent to <code>/deploy</code> and
<code>/undeploy</code>
+and could be removed in a future release.</p>
+
<subsection name="Deploy A New Application Remotely">
<source>
@@ -316,7 +320,7 @@
<li><em>Application already exists at path /foo</em>
<blockquote>
<p>The context paths for all currently running web applications must be
- unique. Therefore, you must either remove or undeploy the existing web
+ unique. Therefore, you must undeploy the existing web
application using this context path, or choose a different context path
for the new one. The <code>update</code> parameter may be specified as
a parameter on the URL, with a value of <code>true</code> to avoid this
@@ -347,15 +351,15 @@
<subsection name="Deploy A New Application from a Local Path">
-<p>Install and start a new web application, attached to the specified context
+<p>Deploy and start a new web application, attached to the specified context
<code>path</code> (which must not be in use by any other web application).
-This command is the logical opposite of the <code>/remove</code> command.</p>
+This command is the logical opposite of the <code>/undeploy</code> command.</p>
-<p>There are a number of different ways the install command can be used.</p>
+<p>There are a number of different ways the deploy command can be used.</p>
-<h3>Install a version of a previously deployed webapp</h3>
+<h3>Deploy a version of a previously deployed webapp</h3>
-<p>This can be used to deploy a previous version of a web applicaion, which
+<p>This can be used to deploy a previous version of a web application, which
has been deployed using the <code>tag</code> attribute. Note that the work
directory for the manager webapp will contain the previously deployed WARs;
removing it would make the deployment fail.
@@ -364,9 +368,9 @@
</source>
</p>
-<h3>Install a Directory or WAR by URL</h3>
+<h3>Deploy a Directory or WAR by URL</h3>
-<p>Install a web application directory or ".war" file located on the Tomcat
+<p>Deploy a web application directory or ".war" file located on the Tomcat
server. If no <code>path</code> is specified, the directory name or the war
file
name without the ".war" extension is used as the path. The <code>war</code>
parameter specifies a URL (including the <code>file:</code> scheme) for either
@@ -376,7 +380,7 @@
the entire WAR file.</p>
<p>In this example the web application located in the directory
-<code>/path/to/foo</code> on the Tomcat server is installed as the
+<code>/path/to/foo</code> on the Tomcat server is deployed as the
web application context named <code>/footoo</code>.
<source>
http://localhost:8080/manager/deploy?path=/footoo&war=file:/path/to/foo
@@ -384,7 +388,7 @@
</p>
<p>In this example the ".war" file <code>/path/to/bar.war</code> on the
-Tomcat server is installed as the web application context named
+Tomcat server is deployed as the web application context named
<code>/bar</code>. Notice that there is no <code>path</code> parameter
so the context path defaults to the name of the web application archive
file without the ".war" extension.
@@ -393,15 +397,15 @@
</source>
</p>
-<h3>Install a Directory or War from the Host appBase</h3>
+<h3>Deploy a Directory or War from the Host appBase</h3>
-<p>Install a web application directory or ".war" file located in your Host
+<p>Deploy a web application directory or ".war" file located in your Host
appBase directory. If no <code>path</code> is specified the directory name
or the war file name without the ".war" extension is used as the path.</p>
<p>In this example the web application located in a sub directory named
<code>foo</code> in the Host appBase directory of the Tomcat server is
-installed as the web application context named <code>/foo</code>. Notice
+deployed as the web application context named <code>/foo</code>. Notice
that there is no <code>path</code> parameter so the context path defaults
to the name of the web application directory.
<source>
@@ -410,19 +414,19 @@
</p>
<p>In this example the ".war" file <code>bar.war</code> located in your
-Host appBase directory on the Tomcat server is installed as the web
+Host appBase directory on the Tomcat server is deployed as the web
application context named <code>/bartoo</code>.
<source>
http://localhost:8080/manager/deploy?path=/bartoo&war=bar.war
</source>
</p>
-<h3>Install using a Context configuration ".xml" file</h3>
+<h3>Deploy using a Context configuration ".xml" file</h3>
-<p>If the Host deployXML flag is set to true you can install a web
+<p>If the Host deployXML flag is set to true you can deploy a web
application using a Context configuration ".xml" file and an optional
".war" file or web application directory. The context <code>path</code>
-is not used when installing a web application using a context ".xml"
+is not used when deploying a web application using a context ".xml"
configuration file.</p>
<p>A Context configuration ".xml" file can contain valid XML for a
@@ -445,14 +449,14 @@
for a web application ".war" file or directory it overrides any
docBase configured in the context configuration ".xml" file.</p>
-<p>Here is an example of installing an application using a Context
+<p>Here is an example of deploying an application using a Context
configuration ".xml" file.
<source>
http://localhost:8080/manager/deploy?config=file:/path/context.xml
</source>
</p>
-<p>Here is an example of installing an application using a Context
+<p>Here is an example of deploying an application using a Context
configuration ".xml" file and a web application ".war" file located
on the server.
<source>
@@ -460,9 +464,9 @@
</source>
</p>
-<h3>Installation Notes</h3>
+<h3>Deployment Notes</h3>
-<p>If the Host is configured with unpackWARs=true and you install a war
+<p>If the Host is configured with unpackWARs=true and you deploy a war
file, the war will be unpacked into a directory in your Host appBase
directory.</p>
@@ -473,12 +477,12 @@
<p>For security when untrusted users can manage web applications, the
Host deployXML flag can be set to false. This prevents untrusted users
-from installing web applications using a configuration XML file and
-also prevents them from installing application directories or ".war"
+from deploying web applications using a configuration XML file and
+also prevents them from deploying application directories or ".war"
files located outside of their Host appBase.</p>
-<h3>Install Response</h3>
+<h3>Deploy Response</h3>
<p>If installation and startup is successful, you will receive a response
like this:</p>
@@ -492,7 +496,7 @@
<li><em>Application already exists at path /foo</em>
<blockquote>
<p>The context paths for all currently running web applications must be
- unique. Therefore, you must either remove or undeploy the existing web
+ unique. Therefore, you must undeploy the existing web
application using this context path, or choose a different context path
for the new one. The <code>update</code> parameter may be specified as
a parameter on the URL, with a value of <code>true</code> to avoid this
@@ -538,14 +542,14 @@
be installed</em>
<blockquote>
If the Host deployXML flag is set to false this error will happen
- if an attempt is made to install a web application directory or
+ if an attempt is made to deploy a web application directory or
".war" file outside of the Host appBase directory.
</blockquote></li>
</ul>
</subsection>
-<subsection name="List Currently Deployed and Installed Applications">
+<subsection name="List Currently Deployed Applications">
<source>
http://localhost:8080/manager/list
@@ -553,7 +557,7 @@
<p>List the context paths, current status (<code>running</code> or
<code>stopped</code>), and number of active sessions for all currently
-deployed and installed web applications. A typical response immediately
+deployed web applications. A typical response immediately
after starting Tomcat might look like this:</p>
<source>
OK - Listed applications for virtual host localhost
@@ -604,7 +608,7 @@
</blockquote></li>
<li><em>No context exists for path /foo</em>
<blockquote>
- <p>There is no deployed or installed application on the context path
+ <p>There is no deployed application on the context path
that you specified.</p>
</blockquote></li>
<li><em>No context path was specified</em>
@@ -615,9 +619,10 @@
<blockquote>
Currently, application reloading (to pick up changes to the classes or
<code>web.xml</code> file) is not supported when a web application is
- installed directly from a WAR file. It only works when the web application
- is installed from an unpacked directory. If you are using a WAR file,
- you should <code>remove</code> and then <code>install</code> the
+ deployed directly from a WAR file. It only works when the web application
+ is deployed from an unpacked directory. If you are using a WAR file,
+ you should <code>undeploy</code> and then <code>deploy</code> or
+ <code>deploy</code> with the <code>update</code> parameter the
application again to pick up your changes.
</blockquote></li>
</ul>
@@ -802,7 +807,7 @@
</blockquote></li>
<li><em>No context exists for path /foo</em>
<blockquote>
- <p>There is no deployed or installed application on the context path
+ <p>There is no deployed application on the context path
that you specified.</p>
</blockquote></li>
<li><em>No context path was specified</em>
@@ -820,7 +825,7 @@
</source>
<p>Signal an existing application to make itself unavailable, but leave it
-deployed or installed. Any request that comes in while an application is
+deployed. Any request that comes in while an application is
stopped will see an HTTP error 404, and this application will show as
"stopped" on a list applications command.</p>
@@ -845,7 +850,7 @@
</blockquote></li>
<li><em>No context exists for path /foo</em>
<blockquote>
- <p>There is no deployed or installed application on the context path
+ <p>There is no deployed application on the context path
that you specified.</p>
</blockquote></li>
<li><em>No context path was specified</em>
@@ -863,11 +868,14 @@
http://localhost:8080/manager/undeploy?path=/examples
</source>
-<p><strong><font color="red">WARNING</font> - This command will
-delete the contents of the web application directory if it exists within the
-<code>appBase</code> directory (typically "webapps") for this virtual host
-</strong>. This will also delete the source .WAR if expanding occurred, as
-well as the XML Context definition. If you simply want to take an application
+<p><strong><font color="red">WARNING</font> - This command will delete any web
+application artifacts that exist within <code>appBase</code> directory
+(typically "webapps") for this virtual host</strong>.
+This will delete the the application .WAR, if present,
+the application directory resulting either from a deploy in unpacked form
+or from .WAR expansion as well as the XML Context definition from
+<code>$CATALINA_HOME/conf/[enginename]/[hostname]/</code> directory.
+If you simply want to take an application
out of service, you should use the <code>/stop</code> command instead.</p>
<p>Signal an existing application to gracefully shut itself down, and
@@ -898,7 +906,7 @@
</blockquote></li>
<li><em>No context exists for path /foo</em>
<blockquote>
- <p>There is no deployed or installed application on the context path
+ <p>There is no deployed application on the context path
that you specified.</p>
</blockquote></li>
<li><em>No context path was specified</em>--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
