This is an excellent walk-through of how to configure IIS and Tomcat:
http://it.megocollector.co
I don't think you've done several of the steps, although I can't be sure. If you truly have only done what you documented, then you're missing some configuration.
It would probably help you to look at the Tomcat doc for the IIS connector as well:
http://tomcat.apache.org/c
but I would start with the first link.
Main Topics
Browse All Topics





by: Thread7Posted on 2009-11-06 at 09:28:41ID: 25761109
Just an update. I don't think the three properties files posted above matter one bit. I ran process monitor and checked to see if those properties files ever get accessed. They do not. C:\Tomcat\ISAPI\isapi_redi rect.dll gets accessed on every http://localhost/pagename. xxx call from a browser. But after restarting services, etc. Nothing I do makes those properties files get accessed. .html rect.dll is gettig accessed on every call from a browser. Even with "Prohibit" set up in "Web Service Extensions".
In fact, I went into the "Computer Management" / "Web Service Extensions", and changed the "Tomcat ISAPI" extension from "Allow" to "Prohibited". Nothing changed. All my page calls are still blank. If I delete the Tomcat ISAPI extension that I created in IIS, and restart the World Wide Web service. Then I at least get my non-Tomcat pages to work. Ie. http://localhost/frontpage
But C:\Tomcat\ISAPI\isapi_redi
One more thing. I an using Win 2003 64-bit. All the java, tomcat, and isapi dlls I installed are 32-bit. Right now, I am leaning towards thinking that this is not a problem. After all, tomcat on port 8080 works fine.
Any ideas?