Hi all, I'm working on a project to deploy Tomcat with our software, and my primary responsibility is the installer/installation process. I've found a lot of good documentation on how to install Tomcat, and how to link it to either Apache or IIS. I can't seem to find any documentation on _why_ to do that though.
Maybe the question is something that should be handled on a case-by-case basis, and that is why there is no information about it. From what I can tell the points break down as follows: 1) Running Tomcat as a standalone server requires client (browser) access to the port and interface. This could result in a very "expensive" process of getting clearance to open a new port on the host's firewall, etc etc. 2) Running Tomcat as an integrated part of the web server avoids the need for having outside access to the Tomcat server. Tomcat instead opens an AJP port (on the loopback interface for example) and communicates to the web server using that port. Is this the only real difference between the two, or are there other pros and cons that I'm not considering. Thanks in advance for any feedback/comments offered. -Rohan Visuvasam --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
