You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@tomcat.apache.org by Steve Holmlund <st...@snippets.com> on 2001/04/27 00:08:24 UTC

Tomcat/IIS 5 /examples solution?

Ok, it was a trip to jGuru and a post by Eric M. from December that may have
provided the answer to my problem. Eric reiterated the isapi_redirect.dll
install procedure in 28 steps. Step #26 was to "start Tomcat".

I didn't think this was necessary as I thought that IIS "started Tomcat" by
having it installed as a filter. Then I re-read the tomcat-iis-howto and lo
and behold, after "Configuring the ISAPI Redirector" Step 9, there is the
following:

"That's all, you should now start Tomcat and ask IIS to serve you the
/examples context."

So I fire up the Jakarta NT Service on the server and test from another
machine.

With IIS running, this works:
http://192.168.1.2/examples/jsp/index.html (192.168.1.2 is server IP)

If I stop IIS, that URL no longer works and I must enter:
http://192.168.1.2:8080/examples/jsp/index.html

which I presume is the standalone Tomcat working???

Can someone confirm that this is correct? If you know and have the time, I
would appreciate understanding why you must both add the filter and start
Tomcat separately. I don't really understand the theory of operation.

Thanks!
Steve

RE: Tomcat/IIS 5 /examples solution?

Posted by Steve Holmlund <st...@snippets.com>.

Thanks, Steve and Jeff, for the explanations. It's all starting to make
sense now.

Steve H.

> If it works as you described then you have it all working (yes
> the response
> to port 8080 is tomcat standalone working, you can turn off responses
> to port 8080 in server.xml if you wish).
>
> The reason you have to start Tomcat is beause the isapi redirector only
> redirects requests to tomcat over the ajp port (8007 by default)
> the redirector
> doesn't run tomcat unless you run tomcat as an "in process server" see the
> manual on that one.

Re: Tomcat/IIS 5 /examples solution?

Posted by Steve Ruby <st...@rubysolutions.com>.

If it works as you described then you have it all working (yes the response
to port 8080 is tomcat standalone working, you can turn off responses
to port 8080 in server.xml if you wish).

The reason you have to start Tomcat is beause the isapi redirector only
redirects requests to tomcat over the ajp port (8007 by default) the redirector
doesn't run tomcat unless you run tomcat as an "in process server" see the
manual on that one.



Steve Holmlund wrote:
> 
> Ok, it was a trip to jGuru and a post by Eric M. from December that may have
> provided the answer to my problem. Eric reiterated the isapi_redirect.dll
> install procedure in 28 steps. Step #26 was to "start Tomcat".
> 
> I didn't think this was necessary as I thought that IIS "started Tomcat" by
> having it installed as a filter. Then I re-read the tomcat-iis-howto and lo
> and behold, after "Configuring the ISAPI Redirector" Step 9, there is the
> following:
> 
> "That's all, you should now start Tomcat and ask IIS to serve you the
> /examples context."
> 
> So I fire up the Jakarta NT Service on the server and test from another
> machine.
> 
> With IIS running, this works:
> http://192.168.1.2/examples/jsp/index.html (192.168.1.2 is server IP)
> 
> If I stop IIS, that URL no longer works and I must enter:
> http://192.168.1.2:8080/examples/jsp/index.html
> 
> which I presume is the standalone Tomcat working???
> 
> Can someone confirm that this is correct? If you know and have the time, I
> would appreciate understanding why you must both add the filter and start
> Tomcat separately. I don't really understand the theory of operation.
> 
> Thanks!
> Steve