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

Posted to users@tomcat.apache.org by Borislav Iordanov <bo...@speakeasy.net> on 2001/04/05 03:49:22 UTC

ISAPI filter question

Hi,

I've used tomcat for a while, starting it from the command line. Now, I've
configured the ISAPI filter for IIS 5.0 under Windoz 2000 Professional and
it works fine also. Except, I'm wondering why do I have to start tomcat from
the shell as usual? Why doesn't the ISAPI filter start it? What are all
those configuration variables (classpaths, tomcat home directory) in
'workers.properties' used for, if the filter seems to be communicating with
tomcat through TCP/IP (on the port 8007 set for the worker)? Maybe I'm
missing some configuration variable that'll make the filter start tomcat
automatically...

Thanks,
Borislav

RE: ISAPI filter question

Posted by Borislav Iordanov <bo...@speakeasy.net>.

Thanks a lot for your help!
Borislav

-----Original Message-----
From: Ricardo Gladwell [mailto:ricardo.gladwell@ubqtmedia.com]
Sent: Thursday, April 05, 2001 5:25 AM
To: tomcat-user@jakarta.apache.org
Subject: RE: ISAPI filter question


The ISAPI filter is not responsible for starting Tomcat: it merely handles
redirecting requests from IIS to Tomcat. You can configure your machine to
start Tomcat automatically:

http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/NT-Service-howto.htm
l

And you can even configure Tomcat to start in the same service as your web
server:

http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/in-process-howto.htm
l

Most of this documentation should be in the Tomcat standard download.
Yours...

--
Ricardo Gladwell
UBQT Media PLC
Mobile: (07779) 841 444

> -----Original Message-----
> From: Borislav Iordanov [mailto:borislav@speakeasy.net]
> Sent: 05 April 2001 02:49
> To: Tomcat User List
> Subject: ISAPI filter question
>
>
> Hi,
>
> I've used tomcat for a while, starting it from the command line. Now, I've
> configured the ISAPI filter for IIS 5.0 under Windoz 2000 Professional and
> it works fine also. Except, I'm wondering why do I have to start
> tomcat from
> the shell as usual? Why doesn't the ISAPI filter start it? What are all
> those configuration variables (classpaths, tomcat home directory) in
> 'workers.properties' used for, if the filter seems to be
> communicating with
> tomcat through TCP/IP (on the port 8007 set for the worker)? Maybe I'm
> missing some configuration variable that'll make the filter start tomcat
> automatically...
>
> Thanks,
> Borislav
>

RE: ISAPI filter question

Posted by Ricardo Gladwell <ri...@ubqtmedia.com>.

The ISAPI filter is not responsible for starting Tomcat: it merely handles
redirecting requests from IIS to Tomcat. You can configure your machine to
start Tomcat automatically:

http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/NT-Service-howto.htm
l

And you can even configure Tomcat to start in the same service as your web
server:

http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/in-process-howto.htm
l

Most of this documentation should be in the Tomcat standard download.
Yours...

--
Ricardo Gladwell
UBQT Media PLC
Mobile: (07779) 841 444

> -----Original Message-----
> From: Borislav Iordanov [mailto:borislav@speakeasy.net]
> Sent: 05 April 2001 02:49
> To: Tomcat User List
> Subject: ISAPI filter question
>
>
> Hi,
>
> I've used tomcat for a while, starting it from the command line. Now, I've
> configured the ISAPI filter for IIS 5.0 under Windoz 2000 Professional and
> it works fine also. Except, I'm wondering why do I have to start
> tomcat from
> the shell as usual? Why doesn't the ISAPI filter start it? What are all
> those configuration variables (classpaths, tomcat home directory) in
> 'workers.properties' used for, if the filter seems to be
> communicating with
> tomcat through TCP/IP (on the port 8007 set for the worker)? Maybe I'm
> missing some configuration variable that'll make the filter start tomcat
> automatically...
>
> Thanks,
> Borislav
>