I've set up Tomcat pages to be served through IIS as per the article at 
http://www.onjava.com/pub/a/onjava/2002/11/20/tomcat.html.

I did the following:

1) Appended extra tag to server.xml:
<Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
port="8009" minProcessors="5" maxProcessors="75"
acceptCount="10" debug="0"/>

2) Created worker.properties file
worker.list=testWorker
worker.testWorker.port=8009
worker.testWorker.host=localhost
worker.testWorker.type=ajp13

3) Created uriworkermap.properties files
/examples/*=testWorker
/examples/*.jsp=testWorker
/examples/servlet/*=testWorker
/admin/*=testWorker
/admin/*.jsp=testWorker

4)Added relevant reg keys for Jakarta Isapi Redirector
As per http://www.onjava.com/pub/a/onjava/2002/12/18/tomcat.html?page=2

5) Created IIS virtual directory & added Isapi entry

The example Tomcat webapps work OK through IIS but I'm getting strange 
behaviour for the admin webapp.

For example, using http://localhost/admin doesn't kick off the default 
page index.jsp as expected. When I specifically reference the index.jsp 
file it displays the login screen & I can login but the admin menu down 
the left hand side doesn't generate all the expected icons. Clicking on 
any of the icons that are rendered causes an error "Servlet not available".

I get the same problems when accessing the admin webapp using the default 
port 8080.

Any suggestions?

Cheers

Mark