aspose file tools*
The moose likes Tomcat and the fly likes migrate from to tomcat 7/mod_jk Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Products » Tomcat
Bookmark "migrate from to tomcat 7/mod_jk" Watch "migrate from to tomcat 7/mod_jk" New topic
Author

migrate from to tomcat 7/mod_jk

Charles Murphy
Greenhorn

Joined: Nov 27, 2013
Posts: 2
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

Joined: Jun 25, 2001
Posts: 16142
    
  21

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.


Customer surveys are for companies who didn't pay proper attention to begin with.
Charles Murphy
Greenhorn

Joined: Nov 27, 2013
Posts: 2
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

Joined: Jun 25, 2001
Posts: 16142
    
  21

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.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: migrate from to tomcat 7/mod_jk