iwproxy / virtualization / web daemon config?

System

Hi all -
I'm on a 5.5.2 Solaris TeamSite implementation.

I have a pretty good idea what the capabilities of using the iwproxy configuration sections in the iw.cfg are but, as often as I read the documentation in the Admin Guide, the actual implementation still seems very cryptic - and that's even after discounting the regex portion of if. Several examples of different configurations would really help.

In lieu of that, I've got a scenario with some intermingled questions:
I've got an intranet branch with about 150 sub-branches which are departmental sites, each with a dev and qa workarea. These are all static sites, not requiring an application engine for virtualization. I also have an iPlanet web server that provides the port 80 web daemon functionality for the TeamSite implementation.

Given the above, what would be the correct iwproxy configuration to allow correct virtualization to the different workareas, STAGING area, and editions for each of these 150 branches? By correct virtualization, I mean that any request from within TeamSite made by clicking on a file will correctly display that file and any linked / included files as if the docroot for the request were the root of the TeamSite area from which it was requested.

For example, if I decide to do a comparison between a modified index.hmtl file in the dev workarea and the previous release in the branch's STAGING area, I could get a side by side visual comparison that, on one side, is correctly resolved from within the dev workarea and on the other side, is correctly resolved from within the STAGING area. Or, one edition vs. another, etc.

This seems like some basic functionality to me but I'm not easily understanding its implementation.

And here's an additional question: coming from a 4.2.1 impelmentation where the iPlanet server was an integral part of the setup, I get the feeling that the web daemon function within a 5.5.x implementation can be provided with a web daemon provided by Interwoven. Is this correct? I have the iPlanet implementation as an artifact of a 4.2.1 implementation.

Thanks for any input