From: kkolinko In many production environments it is very useful to have the capability
@@ -36,7 +40,7 @@ to manage your web applications without having to shut down and restart
Tomcat. This document is for the HTML web interface to the web application
manager. The interface is divided into six sections:
+ The interface is divided into six sections:
-
The Manager section has three links: +
The Manager section has three links:
The Applications section lists information about all the installed web applications and provides links for managing them. For each web application -the following is displayed: +the following is displayed:
Otherwise, the Message will start with FAIL and include an
-error message. Possible causes for problems include:
+error message. Possible causes for problems include:
@@ -152,7 +153,6 @@ error message. Possible causes for problems include:
The path parameter is required.
If this command succeeds, you will see a Message like this:
Otherwise, the Message will start with FAIL and include an
-error message. Possible causes for problems include:
+error message. Possible causes for problems include:
@@ -192,7 +192,6 @@ error message. Possible causes for problems include:
The path parameter is required.
Otherwise, the Message will start with FAIL and include an
-error message. Possible causes for problems include:
+error message. Possible causes for problems include:
@@ -250,7 +249,6 @@ error message. Possible causes for problems include: the application again to pick up your changes.
/deploy Ant command, and the related deploy features available
in the HTML manager.
-
+
If this command succeeds, you will see a Message like this:
Otherwise, the Message will start with FAIL and include an
-error message. Possible causes for problems include:
+error message. Possible causes for problems include:
@@ -298,7 +296,6 @@ error message. Possible causes for problems include:
The path parameter is required.
In this example the web application located in the directory
C:\path\to\foo on the Tomcat server (running on Windows)
-is deployed as the web application context named /footoo.
+is deployed as the web application context named /footoo.
In this example the ".war" file /path/to/bar.war on the
Tomcat server (running on Unix) is deployed as the web application
context named /bar. Notice that there is no path
parameter so the context path defaults to the name of the web application
-archive file without the ".war" extension.
+archive file without the ".war" extension.
foo in the Host appBase directory of the Tomcat server is
deployed as the web application context named /foo. Notice
that there is no path parameter so the context path defaults
-to the name of the web application directory.
+to the name of the web application directory.
In this example the ".war" file bar.war located in your
Host appBase directory on the Tomcat server is deployed as the web
-application context named /bartoo.
+application context named /bartoo.
A Context configuration ".xml" file can contain valid XML for a
web application Context just as if it were configured in your
Tomcat server.xml configuration file. Here is an
-example for Tomcat running on Windows:
+example for Tomcat running on Windows:
Use of the WAR or Directory URL is optional. When used to select a web application ".war" file or directory it overrides any docBase configured in the context configuration ".xml" file.
Here is an example of installing an application using a Context -configuration ".xml" file for Tomcat running on Windows. +configuration ".xml" file for Tomcat running on Windows.
Here is an example of installing an application using a Context configuration ".xml" file and a web application ".war" file located -on the server (Tomcat running on Unix). +on the server (Tomcat running on Unix).
|
- |
- |
- |
|
- |
|
- |
|
- |
- |
- |