Configure JDK and Tomcat via SSH on SuSE Linux, located behind F5

Installation of JDK

Download JDK: Pre-found JDK download locations are copied to the Clipboard, putty via SSH to the server, find a suitable location to download the JDK installation files, such as "/usr/java", and then enter in this directory:

Server:/usr/java # wget Http://www.sun.com/....../jdk-6u13-linux-x64-rpm.bin will start downloading after a carriage return.

Install: Execute Server:/usr/java #/jdk-6u13-linux-x64-rpm.bin, will automatically unzip and install, the JDK6 version of the installation is complete, directly input java-version can see the relevant installation information, For better use, however, you need to configure environment variables.

Configure environment variables: Using VIM to modify profile files

Server:/usr/java # Vim/etc/profile

Add the following statement at the end of the file:

Export java_home=/usr/java/jdk1.6.0_13

Export classpath=.: $JAVA _home/jre/lib: $JAVA _home/lib/tools.jar

Export Jre_home= $JAVA _home/jre

Export path= $JAVA _home/bin: $PATH

Then logout, and then, using echo $JAVA _home, you can see that the environment variable is already in effect. The JDK installation is complete.

Setup for Tomcat

Download: Find the download location of Tomcat in advance copy to clipboard and then download

Server:/usr/java # wget http://tomcat.apache.org/download...../apache-tomcat-6.0.18.tar.gz

Install: Copy this installation file to/usr/local/and then unzip:

Server:/usr/local # tar Xvzf apache-tomcat-6.0.18.tar.gz

It's a good idea to adjust the catalog and put Tomcat files under/usr/local/tomcat.

Boot: Run in Tomcat's Bin directory

Server:/usr/local/tomcat/bin #./startup.sh

Then you can see the cute tom Cat in the browser.

The problem that needs to be paid attention to after F5 because this application is used to analyze the statistics of web traffic, after the deployment of this suse, you can see that there is a network of monitoring requests to access this 80 ports every once in a while, so I dealt with the servlet, This request is filtered directly by return, and is not included in the statistical range. Later found that such processing, after a period of time, 80 ports can not be accessed, ask F5 related engineers, see the server's 80 port is down the state. Try to get rid of this filtration strategy, eh? It's good again, 80 ports have been normal. After repeated testing found that the F5 generated by the monitoring request, can not return directly, or even returned an empty string, that is not the case:

Response.getwriter (). Print ("");

Return

You must return a valid string to ensure the 80 port is normal, so modify the following filtering method to solve the problem:

Response.getwriter (). Print ("404");

Return