Return-Path:
Deployment is the term used for the process of installing a web
@@ -51,15 +41,14 @@
Web application deployment may be accomplished in a number of ways
- within the Tomcat server.
-
+ within the Tomcat server.
The Tomcat Manager is a tool that allows URL-based web application deployment features. There is also a tool called the Client Deployer, @@ -125,11 +114,13 @@ these Context Descriptors to perform their roles properly.
- The locations for Context Descriptors are; -
Files in (1) are named [webappname].xml but files in (2) are named context.xml. If a Context Descriptor is not provided for a Context, Tomcat configures the Context using default values. Modified: tomcat/trunk/webapps/docs/manager-howto.xml URL: http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/manager-howto.xml?rev=918445&r1=918444&r2=918445&view=diff ============================================================================== --- tomcat/trunk/webapps/docs/manager-howto.xml (original) +++ tomcat/trunk/webapps/docs/manager-howto.xml Wed Mar 3 12:37:43 2010 @@ -30,41 +30,7 @@
-Introduction
-
-Configuring Manager Application Access
-Supported Manager Commands
-
-Deploy A New Application Remotely- -Executing Manager Commands With Ant
-Deploy A New Application from a Local Path
- -List Currently Deployed Applications
-Reload An Existing Application
-List OS and JVM Properties
- -List Available Global JNDI Resources
-List Available Security Roles
-Session Statistics
-Start an Existing Application
-Stop an Existing Application
- -Undeploy an Existing Application
-Server Status
-Finding memory leaks
-
-What is JMX Proxy Servlet?- - +
-Query command
-Set command
-
Context
to a new host install the
manager.xml
context configuration file in the
$CATALINA_BASE/conf/[enginename]/[hostname]
folder. Here is an
-example:
+example:
<Context path="/manager" debug="0" privileged="true" docBase="/usr/local/kinetic/tomcat6/server/webapps/manager"> </Context>-
If you have Tomcat configured to support multiple virtual hosts (websites) you would need to configure a Manager for each.
-There are three ways to use the Manager
web application.
+
There are three ways to use the Manager
web application.
localhost
with
@@ -130,19 +95,18 @@
Executing Manager Commands
With Ant for more information.-+ the directory into which you have installed Tomcat. +The description below uses the variable name $CATALINA_BASE to refer the +
+The description below uses the variable name $CATALINA_BASE to refer the base directory against which most relative paths are resolved. If you have not configured Tomcat for multiple instances by setting a CATALINA_BASE directory, then $CATALINA_BASE will be set to the value of $CATALINA_HOME, - the directory into which you have installed Tomcat.
-
It would be quite unsafe to ship Tomcat with default settings that allowed
anyone on the Internet to execute the Manager application on your server.
@@ -150,7 +114,7 @@
who attempts to use it must authenticate themselves, using a username and
password that have the role manager-script associated with
them. Further, there is no username in the default users file
-($CATALINA_BASE/conf/tomcat-users.xml
) that is assigned this
role. Therefore, access to the Manager application is completely disabled
by default.
In addition to the password restrictions the manager web application
could be restricted by the remote IP address or host by adding a
RemoteAddrValve
or RemoteHostValve
. Here is
-an example of restricting access to the localhost by IP address:
+an example of restricting access to the localhost by IP address:
<Context path="/manager" privileged="true" docBase="/usr/local/kinetic/tomcat6/server/webapps/manager"> @@ -205,7 +169,6 @@ allow="127\.0\.0\.1"/> </Context>-
/META-INF/context.xml
.
-URL parameters include: +
URL parameters include:
update
: When set to true, any existing update will be
undeployed first. The default value is set to false.NOTE - This command is the logical
opposite of the /undeploy
command.
This can be used to deploy a previous version of a web application, which
has been deployed using the tag
attribute. Note that the work
directory for the manager webapp will contain the previously deployed WARs;
-removing it would make the deployment fail.
+removing it would make the deployment fail.
In this example the web application located in the directory
/path/to/foo
on the Tomcat server is deployed as the
-web application context named /footoo
.
+web application context named /footoo
.
In this example the ".war" file /path/to/bar.war
on the
Tomcat server 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.
+file without the ".war" extension.
In this example the web application located in a sub directory named
foo
in the Host appBase directory of the Tomcat server is
deployed as the web application context named /foo
. Notice
-that the context path used is the name of the web application directory.
+that the context path used is 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 /bar
.
+application context named /bar
.
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:
+example:
When the optional war
parameter is set to the URL
for a web application ".war" file or directory it overrides any
docBase configured in the context configuration ".xml" file.
Here is an example of deploying an application using a Context -configuration ".xml" file. +configuration ".xml" file.
- +Here is an example of deploying an application using a Context configuration ".xml" file and a web application ".war" file located -on the server. +on the server.
- +