Tomcat4.01 configuration Raiders
Related Website: http://www.yufeng.net -----------------------------
Tomcat4.01 Raiders 1: Introduction Tomcat is an important subproject in the Jakarta project, which is selected as the most innovative Java Product in 2001, and it is the official SUN's official editor's editor of JavaWorld. Recommended servlets and JSP containers (you can see http://java.sun.com/products/jsp/tomcat/), so it is more and more loved by software companies and developers. The latest specifications for servlet and JSP can be implemented in the new version of Tomcat.
2: Installation and configuration of Tomcat latest version is 4.0.1, this version uses a new servlet container Catalina, fully implements servlet2.3 and jsp1.2 specification. Note that your system must have JDK1.2 or higher before installation.
(1): Installation 1: Windows platform download jakarta-tomcat-4.0.1.exe from the Tomcat website, install Tomcat, install the Tomcat, install it, you will automatically look for your JDK and JRE when installing steps.
2: Linux platform Download jakarta-tomcat-4.0.1.tar.gz, unzip it to a directory.
(2): Configuring the Tomcat need to set the java_home variable set java_home = c: / jdk (Win98, use in msdos mode, or put it in autoexec.bat) Export java_home = / usr / local / jdk (use under Linux, put it under Linux Between / etc / bashrc or / etc / profile)
(3): After running, you can run the Tomcat server, enter the bin directory of Tomcat, start Tomcat with Startup with Startup, linux with startup.sh, the corresponding shutdown Tomcat command is shutdown and shutdown.sh. Enter http: // localhost: 8080 / test in the browser after startup, because the Tomcat itself has a web server function, so we don't have to install Apache, of course, it can also be integrated with Apache, which will be introduced below. Below you can test their own JSP and servlet examples.
Three: Application
(1): Directory Structure Tomcat directory structure is as follows: Directory Name: Introduction BIN: Starts and close Tomcat Script CONF: Contains Different Profiles, Server.xml (Tomcat's primary configuration file) and Web.xml Work: Store JSP Class files after compiling WebApp: Store application example, after you have to deploy the application, you should also put it in this directory logs: Store log file lib / japser / common: These three directory mainly store Tomcat required JAR files
(2): Server.xml Configuration Introduction Let's describe the basic configuration information in this file, more specific configuration information See Tomcat's document server: port specifies a port, this port is responsible for monitoring the Tomcat request Shutdown Specifying the port Send Command String Service: Name Specifies the name of the service "Connector between the client and the service): port specifies the port number to be created by the server side, and the processing from the client's request minprocessors server starts creation Request thread number MAXPROCESSORS Maximum number of processing requests Enablelookups If true, you can get the actual host name of the remote client by calling request.getRemoteHost (). If false does not perform DNS queries, Yes Back to its IP address redirectport Specifies that the server is processing the HTTP request to receive an SSL transmission request, the reticient port number acceptCount, which can be placed when all the threads that can be used, can be placed in the processing queue. Number, the request exceeding this number will not process the timeout (in milliseconds) of the connectionTimeout (in milliseconds) Engine (in milliseconds) Engine (indicating the request processor, receiving, and processing from the Connector): DefaultHost Specifies the default processing request The host name, which is at least one of the name attribute values of one of the host elements, which is a web application, usually a WAR file, and see the Servlet specification for the specific information of WAR): DocBase application path or WAR The path stored path Path indicates the prefix of the URL of this web application, which is very important to http: // localhost: 8080 / path / **** reloadable, if true, Tomcat automatically detects the application The program's / web-inf / lib and / web-inf / class change, automatically loads new applications, we can change the application host in the case of Tomcat: Name Specifies the host Name AppBase application basic directory, that is, the directory where the application is placed unpackward, if true, Tomcat Will automatically decompress the WAR file, otherwise it is not extracted, running the application Logger directly from the WAR file: ClassName Specifies the class name used by the Logger, which must implement org.apache.catalina.logger interface Prefix Specifies the prefix for the log file Specifies the suffix timestamp of the log file. If TRUE is true, the log file name is to join the time, as in the following example: localhost_log.2001-10-04.txt realm (indicating that the user name, password, and role : ClassName Specifies the class name used by Realm. This class must implement org.apache.catalina.Realm interface Valve (functionality is similar to Logger, its Prefix, and SUFFIX attributes, the same example): classname Specifies the class name used by Valve, If org.apache.catalina.valves.accessLogvalve class can record the application's access information Directory specifies that the location of the Log file is stored in Pattern, and the CommON mode records the remote host name or IP address, user name, date,
The string of the first line, HTTP response code, the number of bytes sent. Combined approaches more than the value recorded by the Common mode: 1: After I test, I set up PATH = "", reloadable = true, then put a WAR file to the webapps directory, the result cannot detect this file (heavy up Tomcat can be), and the Tomcat will automatically detect this new application. If the WAR file cannot be automatically detected, we can use the methods described below to deploy applications.
2: In the default server.xml, the Realm element only sets a className property, but in this file, several examples connected via JDBC to the database (commented), we can implement container security through Realm elements. Container Managed Security.
3: There are still some elements. We have not introduced, such as parameter, loader, you can get information about these elements through Tomcat documents.
(3): management
1: Configure the specific management before we add a user to Tomcat, so that this user has permission to manage. Open the Tomcat-Users.xml file under the conf directory, add the following line in the appropriate location:
Then recover Tomcat, enter http: // localhost: 8080 / manager /, will pop up in the browser, enter the username and password above.
2: Application list Enter http: // localhost: 8080 / manager / list in your browser, the browser will display the following information:
OK - Listed Applications for Virtual Host Localhost / EX: Running: 1 / Webdav: Running: 0 /: Running: 0 /: Running: 0
The above information is the path to the application of the application, the current state (running or stopped), which is connected to this program.
3: Re-load the application Enter http: // localhost: 8080 / manager / relocalhost: 8080 / manager / recocalhost: 8080 / manager / repline? Path = / example, the browser is shown below:
OK - Reloaded Application AT Context Path / Examples
Indicates that the Example application is loaded. If we set the reloadable property of Server.xml's Context element to True (see above), it is not necessary to reload the application using this manner because Tomcat will be loaded.
4: Display session information Enter http: // localhost: 8080 / manager / sessions? Path = / examples, browser is shown in the browser:
OK - Session Information For Application At Context Path / Examples Default Maximum Session Inactive Interval 30 Minutes5: Start and close Applications Enter http: // localhost: 8080 / manager / start? Path = / examples and http: /////// Localhost: 8080 / manager / stop? path = / examples Start and close the Examples application, respectively.
6: Deployment and revocation of WAR has two organizations, one is to organize files according to a certain directory structure, one is a compression package for a suffix, so there are two ways to deploy: (1): Browse Enter: http: // localhost: 8080 / manager / install? Path = / examples & war = file: / c: Examples will be deployed according to the Table of Table
(2): If you enter: http: // localhost: 8080 / manager / install? Path = / examples & war = jar: file: / c: Examples.war! / Will press the WAR organization of the compression package to note this URL The second half must have! / Number. You can access by http: // localhost: 8080 / examples after deployment.
Enter: http:// localhost: 8080 / manager / remove? Path = / examples will revoke the application just deployed.
(4): Although Tomcat can also make a web server, but it has a static HTML speed than Apache, and its functionality as a web server is far less than Apache, so we want to integrate Apache and Tomcat. We use the Linux system as an example. Download the Apache 1.3.22 source version from the Apache website, then configure the installation of Apache using the following command:
Mkdir / usr / local / apache tar zxvf apache.1.32.tar.gz cd apache.1.32 ./configure --prefix = / usr / local / apache --Nable-module = so make make install
Note that the configure command specifies the target installation directory and joins the DSO (Dynamic Shared Object) support, and be careful not to forget this option.
Then download the WebApp module, and put the mod_webapp.so file after decompression into the Libexec directory of Apache, edit the httpd.conf under Apache's confed, and add the following three lines in this file:
LoadModule WebApp_Module Libexec / Mod_Webapp.so WebAppConnection WarpConnection Warp Localhost: 8008 WebAppDeploy Examples WarpConnection / Examples /
The first line is to join the WebApp module. If you do not add DSO support when compiling Apache, you cannot use the loadModule instruction, the second line specifies the connection of Tomcat and Apache, and the third line specifies the application application. The two instructions use the format as follows:
WebAppConnection [Connection Name] [PROVIDER] [Host: Port] WebAppDeploy [Application Name] [Connection Name] [URL PATH] Where Connection Name Specifies the connection name, the Provider can only be WARP, Port Port and your Tomcat configuration file server. The last few rows of XML should be consistent. The document is as follows:
Application Name consistent with the app name you deployed in Tomcat, the URL PATH specifies the URL to access this application. For example, the above example can access the Examples app in Tomcat via http: // localhost / example.
(5): Chinese problem general JSP garbled problem can be solved by adding <% @ page contentty = "text / html; charset = GB2312"%> by joining in JSP, as for servlet2.3 can be used in servlet2.3 HTTPServeletRequest.setCharacterencoding function. For more detailed Chinese issues, please see the Chinese character encoding problem in JSP / servlet.
IV: Summary Tomcat acts as a servlet (JSP is also compiled into a servlet) container, and its application prospect is very good. If combined with JBOSS, you can implement Sun's J2EE specification (with JBoss as an EJB server). JBoss's official website also provides JBoss integrated Tomcat3.2 * for download. Another open source application server (ENHYDRA) is also based on Tomcat, which provides a more friendly management interface, and deploying applications is also simpler and more powerful.
Win98 environment variable configuration, by editing C: /autoexec.bat Add set java_home = c: /jdk1.4set catalina_home = c: / jatarta-tomcat-3set classpath = c: / jatarta-tomcat-3 / common / lib / servlet .jar; .set path = c: / windows; c: /jdk1.4/bin may also need to increase your environmental space, edit C; /Config.sys Add shell = C: /command.com / E: 1024 / P will play Windows, you can
