IIS 6 or later

Note: This documentation is for an old version of Webinator. The latest documentaion is here.

IIS 6 or later

In IIS 6 and later, Texis ISAPI is used as an ISAPI Extension, not an ISAPI Filter. The extension is applied as a ``wildcard application map'' on a virtual directory. This means that all requests that come to the specified virtual directory will not map to the real location of the virtual directory, but instead be processed by Texis ISAPI.

For IIS 6 to use Texis ISAPI, there are two separate things that need to be done. A virtual directory needs to be set up to use ProxyModule.dll, and Texis ISAPI needs to be added it to IIS 6's Allowed Extensions list.

To create a virtual directory that invokes ProxyModule.dll on IIS 6:

Open the IIS Configuration
- Right click on My Computer on the desktop.
- Select Manage...
- Open Services and Applications in the tree.
- Open Internet Information Services.
- Open Web Sites.
- Open the website you want to add Texis ISAPI to (most likely Default Web Site).
Add a new virtual directory
- Right click on the website you want to add Texis ISAPI to, and select New -> Virtual Directory...
- The Virtual Directory Creation Wizard opens. Click Next>.
- In the Alias box, enter texis, and click Next.
- In the Path box, enter the real physical path you want the virtual directory to map to, and click Next. Webinator uses the directory <INSTALLDIR>/etc/ISAPI-virtualdir by default.
  Note that it doesn't matter what directory is selected. This directory will never be used because all requests will be intercepted by Texis ISAPI. The only reason a directory must be selected is because IIS insists that all virtual directories map to a real physical location.
- At the Virtual Directory Access Permissions screen, just click Next to complete the wizard, as we won't be using any of the permissions.
- Click Finish to complete the wizard and return to the Computer Management window.
Apply ProxyModule.dll as a Wildcard Application Map
- Back in the Right-click on the newly created virtual directory and select Properties.
- The lower half of the properties window is labeled Application Settings. Click Create to make a custom set of application settings for this virtual directory.
- After clicking Create, the Configuration should no longer be disabled. Click Configuration.
- The lower half of the new Application Configuration window details Wildcard Application Maps, which is currently empty. Click Insert.
- Next to the Executable field, click the Browse button and locate ProxyModule.dll.
  - (By default Webinator places this file in C:\windows\system32\inetsrv on 32bit windows, C:\windows\SysWOW64\inetsrv on 64bit windows).
- Uncheck the box next to Verify that file exists, and click OK.
- ProxyModule.dll will now be in the list of Wildcard Application Maps. Click OK to close the Application Configuration window, and OK to close the virtual directory's properties window.

To add Texis ISAPI to IIS' list of allowed extensions on IIS 6:

By default IIS blocks all ISAPI extensions as a security measure. Texis ISAPI must be explicitly allowed in IIS' configuration.

Back in the Computer Management window, open Web Service Extensions, underneath Internet Information Services.
The right side of the window should now have a list of rules. Right-click beneath the existing rules and select Add a new web service extension...
In the Extension Name field, enter Texis ISAPI.
Next to the Required files text area, click the Add... button.
Next to Path to file:, click Browse... and locate ProxyModule.dll, (just as in the previous set of instructions), and click OK to close the Add File dialog.
Check the box next to Set extension status to Allowed, and click OK to close the window.

IIS 6 should now be properly set up to use Texis ISAPI. Note that the extension doesn't get loaded until a request is made, so no entry will be made in the Event Log about startup until at least one request that uses the extension has been made.