• Apache Web Server
• Bulletin Board
• CGI script
• Calendars
• Clamav
• CreditCards
• Disk Space
• Domain Alias
• Domain Name Registration
• Domain Name
• Email AutoReplying
• Email Forwarding
• Email
• FTP Access
• FormeMail
• FrontPage Web Administrator
• FrontPage
• Graphical Usage Statistic
• Guestbook
• HTML
• Hosting Services Provider
• Hosting
• HyperText Markup Language
• IMAP Email Server
• IP address
• Internet
• JSP Actions
• JSP Directives
• JSP Scripting Elements and Variables
• JSP
• JVM
• Jakarta Tomcat
• Java Applets
• Java Server Pages
• Java Servlets Manager
• Java Servlets
• Java Virtual Machine
• Java
• JavaScript
• Linux
• Mail Lists
• Mason
• MySQL
• OS Commerce Shopping Cart
• PERL
• PHP
• POP3 Email Accounts
• Phishing
• Private JVM
• Private Java Virtual Machine
• Python
• RAID
• Referrer Log
• Ruby On Rails
• Ruby
• SFTP
• SMTP
• SPF
• SSH
• SSI
• SSL
• Safe Harbor
• Search Engine
• Secure FTP
• Secure Shell
• Secure Sockets Layer SSL
• Sender Policy Framework
• Server Side Includes SSI
• Servlets
• Shared SSL
• Shared Web Hosting
• Shopping Cart
• Simple Mail Transfer Protocol
• Simple Search
• Spam Assassin
• Spam Corral
• Spamhaus Block List
• Spamhaus Exploits Block List
• Streaming MultiMedia Server
• Tomcat
• Transfers per Month
• URL
• Uniform Resource Locator
• Web Based Email
• Web Hosting Services Provider
• Web Mail
• World Wide Web
• Index

Tomcat Java Servlets Manager
In many production environments, it is very useful to have the capability to deploy a new web application, or undeploy an existing one, without having to shut down and restart the entire container. In addition, you can request an existing application to reload itself, even if you have not declared it to be reloadable in the Tomcat 5 server configuration file.

To support these capabilities, Tomcat 5 includes a web application (installed by default on context path /manager) that supports the following functions:

• List the currently deployed web applications, as well as the sessions that are currently active for those web apps.
• Reload an existing web application, to reflect changes in the contents of /WEB-INF/classes or /WEB-INF/lib.
• List the OS and JVM property values.
• List the available security roles defined in the user database.
• Remove an installed web application.
• Start a stopped application (thus making it available again).
• Stop an existing application (so that it becomes unavailable), but do not undeploy it.
• Undeploy a deployed web application and delete its document base directory.