Michael J McCafferty wrote:
It's most likely not Apache httpd... which is why it's not already on
port 80. He's probably using Apache Tomcat, which listens on an
alternate port (8080) to not conflict with a concurrently running Apache
httpd on port 80.


To use Tomcat with Apache, the customer should use mod_jk. Tomcat and Apache have been designed to interoperate. Some how-tos/tutorials:

http://www.serverwatch.com/tutorials/article.php/10825_2203891_2
http://www.johnturner.com/howto/apache2-tomcat4127-jk-rh9-howto.html
http://www.howtoforge.com/apache2_tomcat5_mod_jk_integration

I currently have 5 Tomcat servers at randomlogic.net (Tomcat 6 and Apache 2.0.x), all of which work with the single Apache server through mod_jk (including randomlogic.net itself). In addition, if SSL is needed, it is easier to do this as Apache will provide the SSL encryption while nothing need be done in Tomcat to add it (Note: If Tomcat is running on a different box than Apache, then this may not be desirable as the communication between Tomcat and Apache will not be encrypted.). https://www.randomlogic.net uses SSL in this manner as Tomcat runs on the same machine as the Apache web server.

Setting up Apache+Tomcat using mod_jk is trivial and is the preferred way to integrate the two. Some of the how-tos state that mod_jk has to be compiled, but I did not have to do this. All I had to do was configure Apache to load it.

PGA
--
Paul G. Allen, BSIT/SE
Owner, Sr. Engineer
Random Logic Consulting
http://www.randomlogic.com


--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to