Installing and Configuring the Filter for Redirecting Requests from Microsoft Internet Information Server (IIS) to Destiny

echinoidqueenΔιακομιστές

4 Δεκ 2013 (πριν από 3 χρόνια και 9 μήνες)

113 εμφανίσεις

Installing and Configuring the Filter for
Redirecting Requests from Microsoft
Internet Information Server (IIS) to Destiny
www.fsc.follett.com
Installing and Configuring the Filter for Redirecting
Requests from Microsoft Internet Information Server
(IIS) to Destiny
This document contains the instructions for installing, configuring, testing, and using the Destiny Internet
Server Application Programming Interface (ISAPI) filter for Microsoft Internet Information Server (IIS).
Note: IIS is a third party product and is not directly supported by Follett Software Company.
For information beyond the scope of this article (setup, configuration, etc., of IIS), refer to Microsoft's
documentation.
Installing the ISAPI filter to IIS
1. Contact Follett Software’s Technical Support (1-800-722-7424) to acquire the filter files.
2. Copy WCP_ISAPI.DLL and WCP_ISAPI.INI into the IIS Scripts folder (..\INETPUB\SCRIPTS).
3. Edit the WCP_ISAPI.INI file and enter the required settings:
[Relay]
Host = IP address or domain name of Destiny server

(This defaults to 127.0.0.1 if left blank).

Port = Port number of Destiny

(This defaults to 8080 if left blank.)

UseProxy = (Yes/No)

(Default value is No. If changed to Yes, the ProxyHost and ProxyPort values below are used to
route requests to a proxy server. The values below are used in place of the above host and port
information. If there is no proxy server between IIS and Destiny, leave this value "No.")
ProxyHost = IP address of proxy server

(May be left blank if a proxy server is not being used.)
ProxyPort = Port number of proxy server

(May be left blank if a proxy server is not being used.)
Configuring IIS to Use the ISAPI Filter on Windows 2000
1. Using the Internet Services Manager, right click on Default Web Site (or, if another web site has
been configured specifically for Destiny, select that web site) and select the Properties menu
item (Figures 1 and 2).
Redirecting Requests from Microsoft Internet Information Server (IIS) to Destiny
Page 2 of 6 © Copyright 2004 Follett Software Company.
Figure 1

Figure 2

Redirecting Requests from Microsoft Internet Information Server (IIS) to Destiny
© Copyright 2004 Follett Software Company. Page 3 of 6
2. Click the ISAPI Filters tab and click Add (Figure 3).
Figure 3

3. Enter a filter name. (Figure 4)
Example: Destiny Plug-In.
Enter the full path to the WCP_ISAPI.DLL file in the Executable field.
(Default: C:\INETPUB\SCRIPTS\WCP_ISAPI.DLL)

Click OK.
Figure 4

Redirecting Requests from Microsoft Internet Information Server (IIS) to Destiny
Page 4 of 6 © Copyright 2004 Follett Software Company.
4. On the ISAPI Filters tab, click Apply and click OK to save the filter configuration.
5. Important: From the Services control panel, restart the IIS Service (Worldwide Web Publishing
Service).
When the filter configuration is first saved, the Status field is blank and the Priority field reads
"Unknown." These indicators change after you restart the IIS service. (Figure 5)
Figure 5

Configuring the ISAPI filter to IIS on Windows 2003
1. Perform the same steps as for Windows 2000.
2. In IIS Admin, open Web Service Extensions.
3. Highlight All Unknown ISAPI Extensions.
4. Select Allow. Make sure the status changes to "Allowed" next to "All Unknown ISAPI
Extensions." (Figure 6)
Redirecting Requests from Microsoft Internet Information Server (IIS) to Destiny
© Copyright 2004 Follett Software Company. Page 5 of 6
Figure 6

Using the IIS Filter
Append "/common/welcome.jsp" to the URL used to access IIS.
Example: Assuming the site domain is "http://MySchool.edu" (with IIS listening on port 80), the
URL would be:
http://MySchool.edu/common/welcome.jsp
Testing the IIS Filter
Append "/webopac/filterstatus" to the URL used to access IIS.
Example: Assuming the site domain is "http://MySchool.edu" (with IIS listening on port 80), the
URL would be:
http://MySchool.edu/webopac/filterstatus
One of three results will appear in the browser window:
A. If the filter is installed, configured correctly, and able to connect to Destiny, the Filter Status page
appears with a green background. The IP address and port that requests are being forwarded to
(Destiny) also appears, as well as a Remote Connection Status message indicating that a
connection was successfully made. (Figure 6)
Redirecting Requests from Microsoft Internet Information Server (IIS) to Destiny
Page 6 of 6 © Copyright 2004 Follett Software Company.
Figure 6

B. If the filter is installed and configured correctly but unable to connect to Destiny, the Filter Status
page appears with a red background. The IP address and port that requests are being forwarded
to (Destiny) also appears, as well as a Remote Connection Status message listing specific error
information. (Figure 7)
Figure 7

C. If the filter is not installed correctly or is inactive, a 404 error appears when the filter test URL is
entered in the browser.