|
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
- 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.
Copyright © Thunderstone Software Last updated: Thu Mar 11 16:13:32 EST 2010
|