I was able to get the site up and running. Here's what I ended up doing: - put virtual directory "Jakarta" as per the document, but under my customdomain instead of under the default website. - put the isapi_redirect.dll filter on the customdomain. (both these ultimately caused problems with other asp sites on the box when they were on the default web site). - updated the web.xml file to have a reference to "/" to get the requests. - updated the urlproperties to also have reference to "/" for the requests.
Thanks for all the help! -----Original Message----- From: Larry Isaacs [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 05, 2001 1:47 PM To: 'Tomcat Users List' Subject: RE: IIS 5 Tomcat Configuration If you see jakarta/isapi_redirect.dll being requested as if it were a page, it means that isapi_redirect.dll is being called recursively. It may only be used as a filter once for it to work correctly. I don't have time to actually test the following right now, but you are welcome to try these. If you want both sites to access the same instance of Tomcat, I believe you can move the filter up one level to the "computer" node. That way the single isapi_redirect.dll will be used by both sites. If you want to have each access a separate version of Tomcat or use a different configuration, there is a not yet documented feature in the Tomcat 3.3 version of isapi_redirect.dll to allow you to pull this off. When the isapi_redirect.dll is loaded, it will try to determine its full path. It will then try to read a properties file with the same full path but an extension of ".properties" instead of ".dll". If this file exists, it will be used to obtain the settings instead of the registry. Thus, add the filter to the first site in the usual way. Then for the second site, make a copy of the isapi_redirect.dll in the same directory and rename it, for example "isapi_redirect2.dll". Create a file named isapi_redirect2.properties in the same directory containing: extension_uri=/jakarta/isapi_redirect2.dll log_file=<path to log file> log_level=<desired level> worker_file=<path to worker.properties> worker_mount_file=<path to uriworkermap.properties> Add isapi_redirect2.dll to the second site as a filter. You could set up the first isapi_redirect.dll to use a properties file too, if desired. The result of this is that you get two instances of the filter rather than one which calls itself recursively. This is supposed to work. However, I haven't yet actually tried this, which is why it isn't yet documented. Let me know if you try this and you have problems. Cheers, Larry > -----Original Message----- > From: Lybarger, Mark E. [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 05, 2001 12:52 PM > To: 'Tomcat Users List' > Subject: RE: IIS 5 Tomcat Configuration > > > I tried Katherine's advice, in another post, and am getting a > little further > (THANKS!). I'm now seeing a Tomcat 404 error thrown for > jakarta/isapi_reirect.dll when asking for any page. Nice to > see errors from > tomcat, that shows that IIS is giving up the pages. > > The isapi_redirect filter is on both the default web site, and my > customdomain site. I'll try to remove it from my > customdomain and see how > that helps. > > Also, The documents mention adding a virtual directory in the default > website (pointing to the native folder). I had this on the > default website, > but moved it to my customdomain. Does this make a difference > where this > virtual directory should be placed? > > -----Original Message----- > From: Larry Isaacs [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 05, 2001 12:57 PM > To: 'Tomcat Users List' > Subject: RE: IIS 5 Tomcat Configuration > > > Which node was the isapi_redirect.dll filter added. If added > to just a web site, remove it and add it to the "computer" node > so it applies to all web sites. I assume this will make > a difference, though I have not yet actually tried it. > > Cheers, > Larry > > > -----Original Message----- > > From: Lybarger, Mark E. [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, December 05, 2001 11:41 AM > > To: '[EMAIL PROTECTED]' > > Subject: IIS 5 Tomcat Configuration > > > > > > I've hit a snag setting up tomcat 4.0.1 and iis 5.0. I followed the > > directions for Tomcat 3.3 and also used the following guide: > > > http://members.ozemail.com.au/~lampante/howto/tomcat/iisnt/index.html > > > > Tomcat works fine using port 8080 on localhost. IIS > > integration works fine. > > I can use mydomain/examples/, and they all work good. > > > > Next I wanted to setup a custom domain under IIS and have > > that point to the > > examples area. I setup a new web site, gave it my static ip > > address, and > > pointed it to the examples folder in the tomcat area. The > > problem is that > > when i go point my browser to http://mycustomdomain/ the > > pages are only > > rendering html, any jsp tags do not seem to be being > > processed by tomcat. > > Maybe i shouldn't have pointed the new website to the > > examples area? any > > suggestions? > > > > -- > > To unsubscribe: > <mailto:[EMAIL PROTECTED]> > > For additional commands: > <mailto:[EMAIL PROTECTED]> > > Troubles with the list: > <mailto:[EMAIL PROTECTED]> > > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
