Tomcat幫助文件翻譯未完成

All commands that the Manager application knows how to process are specified in a single request URI like this:
http://{host}:{port}/manager/{command}?{parameters}
where {host} and {port} represent the hostname and port number on which Tomcat is running, {command} represents the Manager command you wish to execute, and {parameters}

represents the query parameters that are specific to that command. In the illustrations below, customize the host and port appropriately for your installation.

Most commands accept one or more of the following query parameters:


path

- The context path (including the leading slash) of the web application you are dealing with. To select the ROOT web application, specify "/". NOTE - It is not possible to perform administrative commands on the Manager application itself.

war - URL of a web application archive (WAR) file, pathname of a directory which contains the web application, or a Context configuration ".xml" file. You can use URLs in any of the following formats:

file:/absolute/path/to/a/directory - The absolute path of a directory that contains the unpacked version of a web application. This directory will be attached to the context path you specify without any changes.

file:/absolute/path/to/a/webapp.war - The absolute path of a web application archive (WAR) file. This is valid only for the /deploy command, and is the only acceptable format to that command.

jar:file:/absolute/path/to/a/warfile.war!/ - The URL to a local web application archive (WAR) file. You can use any syntax that is valid for the JarURLConnection class for reference to an entire JAR file.

file:/absolute/path/to/a/context.xml - The absolute path of a web application Context configuration ".xml" file which contains the Context configuration element.

directory - The directory name for the web applciation context in the Host's application base directory.

webapp.war - The name of a web application war file located in the Host's application base directory.




Each command will return a response in text/plain format (i.e. plain ASCII with no HTML markup), making it easy for both humans and programs to read). The first line of the response wil begin with either OK or FAIL, indicating whether the requested command was successful or not. In the case of failure, the rest of the first line will contain a description of the problem that was encountered. Some commands include additional lines of information as described below.

Internationalization Note - The Manager application looks up its message strings in resource bundles, so it is possible that the strings have been translated for your platform. The examples below show the English version of the messages.

WARNING: the legacy commands /install and /remove are deprecated. They are presently equivalent to /deploy and /undeploy, but could be removed in a future release.
http://localhost:8080/manager/deploy?path=/foo
Upload the web application archive (WAR) file that is specified as the request data in this HTTP PUT request, install it into the appBase directory of our corresponding virtual host, and start it on the context path specified by the path request parameter. If no path is specified the directory name or the war file name without the .war extension is used as the path. The application can later be undeployed (and the corresponding application directory removed) by use of the /undeploy.

The .WAR file may include Tomcat specific deployment configuration, by including a Context configuration XML file in /META-INF/context.xml.

URL parameters include:


update: When set to true, any existing update will be undeployed first. The default value is set to false.

tag: Specifying a tag name, this allows associating the deployed webapp with a version number. The application version can be later redeployed when needed using only the tag.


NOTE - This command is the logical opposite of the /undeploy command.

If installation and startup is successful, you will receive a response like this:
OK - Deployed application at context path /foo
Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:


Application already exists at path /foo

The context paths for all currently running web applications must be unique. Therefore, you must undeploy the existing web application using this context path, or choose a different context path for the new one. The update parameter may be specified as a parameter on the URL, with a value of true to avoid this error. In that case, an undeploy will be performed on an existing application before performing the deployment.


Encountered exception

An exception was encountered trying to start the new web application. Check the Tomcat 5 logs for the details, but likely explanations include problems parsing your /WEB-INF/web.xml file, or missing classes encountered when initializing application event listeners and filters.


Invalid context path was specified

The context path must start with a slash character. To reference the ROOT web application use "/".


No context path was specified
The path parameter is required.
Deploy and start a new web application, attached to the specified context path (which must not be in use by any other web application). This command is the logical opposite of the /undeploy command.

There are a number of different ways the deploy command can be used.

Deploy a version of a previously deployed webapp

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.
http://localhost:8080/manager/deploy?path=/footoo&tag=footag
Deploy a Directory or WAR by URL

Deploy a web application directory or ".war" file located on the Tomcat server. If no path is specified, the directory name or the war file name without the ".war" extension is used as the path. The war parameter specifies a URL (including the file: scheme) for either a directory or a web application archive (WAR) file. The supported syntax for a URL referring to a WAR file is described on the Javadocs page for the java.net.JarURLConnection class. Use only URLs that refer to the entire WAR file.

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.
http://localhost:8080/manager/deploy?path=/footoo&war=file:/path/to/foo
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.
http://localhost:8080/manager/deploy?war=jar:file:/path/to/bar.war!/
Deploy a Directory or War from the Host appBase

Deploy a web application directory or ".war" file located in your Host appBase directory. If no path is specified the directory name or the war file name without the ".war" extension is used as the path.

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 there is no path parameter so the context path defaults to the name of the web application directory.
http://localhost:8080/manager/deploy?war=foo
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.
http://localhost:8080/manager/deploy?path=/bartoo&war=bar.war
Deploy using a Context configuration ".xml" file

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 path is not used when deploying a web application using a context ".xml" configuration file.

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:
<Context path="/foobar" docBase="/path/to/application/foobar"         debug="0">    <ResourceLink name="users" global="UserDatabase"                type="org.apache.catalina.UserDatabase"/></Context>
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.
http://localhost:8080/manager/deploy?config=file:/path/context.xml
相關推薦

Tomcat幫助文件翻譯未完成

                        All commands that the Manager application knows how to process are specified in a single request URI like this:

Win10使用Tex Live和VS Code和Latex Workshop外掛編寫Latex文件（未完成版本）

首先取Tex Live官網下載安裝包：https://www.tug.org/texlive/acquire-netinstall.html 我下載的是 http://mirror.ctan.org/systems/texlive/tlnet/install-tl-windows.exe 不過我記得這

ST 電機控制工作臺幫助文件翻譯之介紹（快速開始）



分散式日誌框架之ExceptionLess【二】：自行搭建幫助文件【翻譯】

原文地址：https://github.com/exceptionless/Exceptionless/wiki/Self-Hosting ExceptionLess自行託管環境搭建一、測試環境如果你想在本地測試ExceptionLess，請遵循本節如下步驟。但是，請注意！以下事項僅

《Spring Data 官方文件翻譯》3. 其他幫助資源

原文連結 3.其他幫助資源學習一個新的框架並不總是那麼容易的。在這一章中，我們嘗試提供一份我們認為比較容易遵循的指南，用於開始學習Spring Data Cassandra模型。但是，如果您遇到了問題或者您僅僅想要尋找一些建議，可以自由使用以下連結： 3.1. 技術支援這裡提供了一些支援

文件翻譯第003篇：Process Monitor幫助文件（Part 3，附Process Monitor的簡單演示）

【匯入與匯出配置】一旦您配置了一個篩選器，您可以使用“工具（Tools）”選單中的“儲存篩選器（SaveFilters）”選單項將其儲存。Process Monitor將您所儲存的篩選器新增到“讀取篩選器（Load Filter）”選單，便於您能夠方便地訪

sqlmap幫助文件(配合實踐翻譯)

用過sqlmap，也用過不少功能了，為了更加了解這個工具，決定翻譯一下，利用自己的實戰經驗去翻譯翻譯確實有點辛苦，有些選項還實踐不了，但是收穫還是很多的不惜感嘆：sqlmap真強大啊~~~~~~~~ 建議使用 ctrl + f 進行查查詢，方便自己方便別人

網路抓包工具翻譯幫助文件詳解教程

How To Set Up a Capture 1. 確保你做的事是被允許的！           （1）意思是在不違反法律的情況下抓取可以被允許抓取的包。 2.一般設定           （1）許可權的設定，你是否有許可權去獲取使用者或者管理員的資料。

tomcat配置文件結構

tomcat配置文件結構cd /export/servers/tomcat7bin ——Tomcat執行腳本目錄conf ——Tomcat配置文件lib ——Tomcat運行需要的庫文件（JARS）logs ——Tomcat執行時的LOG文件temp ——Tomcat臨時文件存放目錄webapps ——Tom

SAP 官網中文幫助文件&BP中文資料匯總

target oba rac pro 資料 packages spa app soft 系統描述版本連接 SAP ME 制造執行 SAP Manufacturing Execution (SAP ME) 15.0 點擊我 SAP ECC

Tomcat 配置文件

nec 命令 reads ssp 適用於服務器 window time policy Tomcat 站點配置1、bin目錄下 1、catalina tomcat 主腳本、執行Java命令調用tomcat的啟動與停止 2、cpappend 用於windows系統內部，將

matlab之“audioread”函數幫助文檔翻譯

rst border 由於 owin 大小 ner sig 測試 number 課程設計（1）原文 audioread Read audio file Syntax [y,Fs] = audioread(filename) [y,F

shell判斷批處理的目錄下的流文件是否處理完成

top $0 err delete date proc conf shel script #!/bin/bash log_error() {? ? echo -e $target date "+%Y-%m-%d %H:%M:%S" ["\033[31merror\

Sphinx 生成 Windows 幫助文件 (.chm文件)

點擊 pro HR image lib absolute sphinx pen 開發本文不介紹 Sphinx 的用法，只簡要羅列 Windows 下生成 .chm 文件的步驟。 0. 首先檢查機器是否安裝了 HTML Help Workshop 軟件，一般安

shell腳本切割tomcat日誌文件

下使用調試 awk mkdir cat size 內容 monit 日誌文件轉自：http://www.cnblogs.com/lishun1005/p/6054816.html 鑒於在調試logback和log4j的文件切割一直無法成功，隨性用shell寫個腳本用來切

【Webpack 雜談】幫助文檔翻譯：Webpack的模塊

加載器 coffee ejs 什麽是異步項目 htm 優秀模塊頁面出自Webpack官方文檔（撰寫時，是v4.1.1）其實Webpack本身有中文文檔，不知道是誰去撰寫的，但是自己翻譯一遍感覺更好理解。 https://webpack.js.org/concep

tomcat配置文件(1)

tomcat配置文件組件說明Tomcat的配置文件構成：通常在我們安裝完tomcat之後在/etc/tomcat目錄生成了一堆的配置文件,我們來看看這些配置文件的作用,tomcat的配置文件是使用java語言編寫： server.xml：主配置文件； web.xml：每個w

Tomcat 日誌文件分割

出現 http 日誌內容解決 a.out ron 其中如果新到公司，拿到了前輩們留下的程序 “病歷書” ，上面記載了項目上的一些經常會犯的毛病，還有相應的解決方法。其中有的是因為後臺代碼邏輯上的一些原因， N手代碼通病了吧（這個還是以後再治吧

Linux 查看Tomcat日誌文件

usr 跟蹤 cat 字節結果輸入寫入 a.out 才有命令為：tail -f catalina.out tail 命令用途從指定點開始將文件寫到標準輸出。使用tail命令的-f選項可以方便的查閱正在改變的日誌文件，tail -f filename會把filena

intellij idea 官方幫助文檔翻譯（一）安裝

5G cati 歡迎界面 www. 1.8 一點過去的方便使用安裝需求：　　硬件需求：　　　　最低2GB內存，推薦4GB內存　　　　最少要有1.5GB的硬盤空間，以及1GB空間用於緩存　　　　最低1024*768的分辨率　　軟件需求：　　　　

搜尋

基礎教學

Mysql入門 Sql入門 Android入門 Docker入門 Go語言入門 Ruby程式入門 Python入門 Python進階 Django入門 Python爬蟲入門

最近訪問

首頁
前端設計
程式設計
免費資源
實用技巧
資料庫
資訊
字典

Copyright © 2002-2020 程式人生 796T.COM All rights reserved.

Tomcat幫助文件翻譯 未完成

Deploy a version of a previously deployed webapp

Deploy a Directory or WAR by URL

Deploy a Directory or War from the Host appBase

Deploy using a Context configuration ".xml" file

相關推薦

Tomcat幫助文件翻譯未完成