The path to the architect the next day Apache Tomcat HTTPS application

One, summing up the study of the day before

In the previous day's study we know, understand and master the Web server combined with App server is a kind of architecture, and hands-on through the Apache HTTP server and TOMCAT6 carried out an integrated experiment.

The advantage of such an architecture is that:

• Reduce the pressure on the app server side, using Web server to divide the pressure, that is, Web server is only responsible for static HTML content, while app server is responsible for processing Java requests, which is a great boost to the performance of the system.

Security, the Web server side does not have any Java source code including compiled things, open to the Internet only Web server, so hackers even through the 80 port into our web server, what he can get? In addition to static HTML content, any logic, password he can not get, why? Here... Because our app server "hides" behind the Web server's butt.

Places to look for:

If you show up with such an architecture, your Java EE project must be clearly divided into those <servlet-mapping> in Web.xml, for example:

We can know that *.do, *.action, *.jsp are the things that Java needs to parse, right!

But if your servlet is written like this,

/abc

/123

/def

So when we are mapping, we need to put/abc,/123,/def write a line of jkmount statements, is not ... OK, let's say we have 100 servlet in this project (this is a small one), you're not going to write me this boring stuff in the httpd.conf file. 100, right?

So, we need to have a moment to plan our servlet, that is, pattern, so I've always stressed that you have to unify the servlet when you name it:

/servlet/myservletabc

So, when I do this Web server to the app server mapping, is not just one sentence: jkmount/servlet/* ajp13 can be done?

U the same architecture has different variants:

2 Iis+tomcat

Because Microsoft's IIS itself is a Web Server, it can also be done through a plugin called "ISAPI" through IIS and Tomcat, but I strongly recommend that because Java originates from UNIX systems and is attributed to Unix, UNIX does not recognize IIS. , please be sure to use Apache, you are Java is not much milk (dot net).

2 Apache+weblogic

2 IBM Httpserver (a variant of Apache) +IBM Was6.x/was7. X

2 Tomcat Cluster

Apache hangs n multiple tomcat, by tomcat1...tomcat2...tomcat3 ... and other components

2 WebLogic Cluster

Apache hangs n multiple WebLogic, by weblogic1...weblogic2...weblogic3 ... and other components

2 wasnd (ibmwebsphere App Server Network Deployment)

IBM Httpserver hangs n more than was, by WAS1 ... WAS2 ... WAS3 ... and other components