IIS isapi filter settings for Insight

[pointreyes]

While I can get the isapi filter to work for the manager, I cannot get it to work for Insight. I get a directory error message which I suspect is due to the uriworkermap.properties file not having the proper properties for Insight. Here is what I have in the properties file:
/*.jsp=ajp13w
/*.jsf=ajp13w
/*.js=ajp13w
/*.do=ajp13w
/*.xhtml=ajp13w
/*.jnlp=ajp13w
/manager/*=ajp13w
/insight/*=ajp13w

AFAIK since I have the manager working in the insight instance that the server.xml connector port settings are correct.

What do I need to do to get the isapi filter to work with Insight?

[sandrews]

The Insight Dashboard is located under the /insight context path. All web resources are under that context.

Are you able to access other applications via AJP? If not you will likely need to add the AJP listener in server.xml.

[pointreyes]

After having some much degradation of static content loading using ISAPI in IIS7, I tested using Apache and insight works just fine using mod_jk which tells me that the server.xml file is properly configured.

I'm working on another solution. Instead of using ISAPI I'm now trying the Microsoft module known as the Application Request Routing which appears similiar to the mod_proxy method used in Apache. By using a proxy method which even Apache is recommending using mod_proxy over mod_jk might be the answer to stop using ISAPI for IIS7. For support reasons, it is preferred that IIS is used instead of Apache.

If you have any suggestions on settings using ARR, I'll gladly try them.