Tomcat and IIS on different machines

[dav_c]

Hallo,

I'm trying to achieve a set up where I have IIS residing on a machine in the DMZ, acting as a web server. I also have Tomcat on an internal server acting as the jsp / servlet engine. I want the 2 to work together so IIS takes dynamic content from Tomcat.

I have managed to use isapi_redirect to configure Tomcat and IIS to work togther when they are both on the same machine (ie - install isapi_redirect, change Tomcat workers file and uri_mapping file and change IIS registry).

However, I cannot find any info on getting them to work on seperate machines. When I try to configure IIS, I get stumped because my virtual directory needs a location which is on a seperate machine. Also the ISAP filter needs to point to a location on a different machine. does anyone know the best way to do this (I cannot map drives within the dmz either)

Thanks in adbvace for any help

[technobard]

These two links should help:
http://jakarta.apache.org/tomcat/con...onfig/iis.html http://jakarta.apache.org/tomcat/con...g/workers.html

As I understand it, workers.properties supports different hosts and different ports.

The virtual directory shouldn't require direct access to Tomcat managed directories. uriworkermap.properties maps URL paths to workers defined in workers.properties.

[dav_c]

Thanks for the response. however, I still think I need to specify the tomcat directories on the iis machine. uri_workermap.properties and workers.properties must reside within the tomcat directory structure. The iis virtual directory and the registry settings on the iss machine must both point to uriworkermap.properties - so i'm still stumped as to how i can specify the location of uriworkermap.properties from the iis machine within the dmz. any further help would be good.

thanks again

[technobard]

Hmmm...not an ideal solution, but what if you simply copy the workers.properties and uriworkermap.properties files to the IIS machine? If you make changes, you'd have to keep them in sync, but if you only need access to those files, that should do it.

Along the same lines, you could install Tomcat both on the IIS machine and on the non-DMZ machine. You would then use the .properties files from the local install, but only reference contexts that are on the non-DMZ machine. I'm not sure that this buys you much beyond the first option, but it does give you the ability to host different contexts on different servers, load balancing, etc. if you want in the future.