This week's book giveaway is in the OCAJP forum.
We're giving away four copies of Programmer's Guide to Java SE 8 Oracle Certified Associate (OCA) and have Khalid A Mughal & Rolf W Rasmussen on-line!
See this thread for details.
Win a copy of Programmer's Guide to Java SE 8 Oracle Certified Associate (OCA) this week in the OCAJP forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

migrate from to tomcat 7/mod_jk

 
Charles Murphy
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is there a step by step guide for migrating from apache/jserv to tomcat 7/mod_jk?
I believe jserv is no longer supported, and we have a couple of applets running under jserv.
 
Tim Holloway
Saloon Keeper
Pie
Posts: 18276
56
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Welcome to the JavaRanch, Charles!

Actually, the preferred method is to use apache mod_proxy these days. It's easier to set up than mod_jk. In theory you can do more load balancing in mod_jk, but that's just my perception and may be wrong. I use mod_proxy myself.
 
Charles Murphy
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Tim Holloway wrote:Welcome to the JavaRanch, Charles!

Actually, the preferred method is to use apache mod_proxy these days. It's easier to set up than mod_jk. In theory you can do more load balancing in mod_jk, but that's just my perception and may be wrong. I use mod_proxy myself.


Thank you for the advice. If it's not too much trouble do you have a tutorial/resource which illustrates migrating from jserv to mod_proxy for serving applets?
 
Tim Holloway
Saloon Keeper
Pie
Posts: 18276
56
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Applets don't get involved one way or the other. Especially since sandbox rules mandate that the applet has to load from the same server as the page that requests them, so both page and applet URLs will almost invariably end up going through the same proxy configuration.

Using mod_proxy is fairly easy and well-documented, since it's all done on the Apache side. The only part of it where Tomcat normally is of interest is that Apache has to know which Tomcat port is at the other end of the proxy pipeline. It's 8009 by default.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic