Introduction
WEB application deployment is accomplished in a number of ways within the TOMCAT server.
statically; The Web application is setup before Tomcat is started
dynamically; By directly manipulating already deployed Web applications (relying on auto-deployment feature) or remotely by us ing the Tomcat Manager Web application
The Tomcat Manager is a Web application this can be used interactively (via HTML GUI) or programmatically (via url-based a PI) to deploy and manage Web applications.
There is a number of ways to perform deployment this rely on the Manager Web application. Apache Tomcat provides tasks for Apache Ant build tool. Apache Tomcat maven Plugin project provides integration with Apache maven. There is also a tool called the Client Deployer, which can being used from a command line and provides additional Functionali Ty such as compiling and validating Web applications as well as packaging Web application into Web application RESOURC E (WAR) files.
installation
There is no installation required for static deployment of Web applications as this is provided out of the box by Tomcat. Nor is a installation required for deployment functions with the Tomcat Manager, although some configuration is Requir Ed as detailed in the Tomcat Manager manual. An installation are however required if you wish to use the Tomcat Client Deployer (TCD).
The TCD isn't packaged with the TOMCAT core distribution, and must therefore being downloaded separately from the Downloads Area. The download is usually labelled Apache-tomcat-7.0.x-deployer.
A Word on Context
In talking about deployment of Web applications, the concept of a Context are required to being understood. A Context is the what Tomcat calls a Web application.
Tomcat WEB Application Deployment