|Here is how you do it:
- Create a new virtual directory (VD) within EACH of your new IIS virtual domains (each IIS website) with which you want to use ServletExec. For SE AS the name of this VD must be "Scripts", for SE ISAPI it's name is "ServletExec". You'd do this in the MMC (Microsoft Management Console). The important thing is that all SE-enabled IIS websites must use exactly the same name for the VD. Typically you already have IIS site 'A' (Default Web Site) using a VD named "Scripts" or "ServletExec". So for IIS site 'B', site 'C', etc... you need to use the same name for your VD.
- Point each VD to the physical folder on your hard drive where the ServletExec DLL resides. This is probably "...\Inetpub\Scripts\", and be sure to give each VD "Execute (including scripts)" (or "Scripts and Executables") Permission in the MMC.
FYI: Each VD that points to the folder where the DLL resides, for each IIS Domain, MUST have the exact same name and must have "Scripts and Executables" Permission [also known as "Execute (including scripts)" permission]. Also the ServletExec filter that is set up in the Metabase (Master properties dialog, not the properties dialog for the website) must point to the ServletExec DLL file that resides in the physical "Scripts" folder.
The reason that the VD must have the same name in each IIS website is because on the first request, the SE DLL will ask IIS "which VD points to me?" and it will 'cache" the answer from then on (until the next time IIS is cycled). That VD is then used when requests are routed to SE to be processed. If more than 1 VD in a single IIS website points to the SE DLL then you may need to ensure that ALL of them have the proper permission settings since it's unclear which VD IIS will say is the one that points to the SE DLL. It's likely the first one you see listed in the MMC, but that may not be true in all cases. It's up to IIS.