Servertec   ISAPI Gateway
Content
Introduction
Release Notes
Features
FAQs
Requirements
Installation
iServer
Apache Gateway
ISAPI Gateway
NSAPI Gateway
CGI Gateway
Java Gateway
Add-ons
How To
Change Log
Future Plans
Knowledge Base
Documentation
Samples
Sales
Legal
Feedback

 

Use the instructions below to configure Microsoft Personal Web Server, Internet Information Server or other Application/Web Servers supporting ISAPI to use iServer as their Servlet Engine.
  1. Install and configure iServer.

  2. Install and configure Microsoft Personal Web Server, Internet Information Server or other Application/Web Server that supports ISAPI.

  3. Define variables used by the ISAPI Gateway.

    For Windows 9x/NT add the following entries to iserver.ini file in the Windows installation directory, normally c:\windows for Windows 9x and c:\winnt for Windows NT.

    [isapigateway]
    DEBUG=boolean
    SERVER=hostname:port
    INTERVAL=interval
    RETRY=retry
    ISERVER_URI=alias
    IGATEWAY_URI=/igateway/isapiGateway.dll

    alias the URI used to access the iServer ISAPI Gateway, normally /servlet.
    boolean whether to make a dump of the request/response to \temp\isapiGateway.log [ true | false ], normally false.
    host_name the name of the host computer running iServer. If iServer is running on the same computer as the iServer ISAPI Gateway then localhost can be used.
    interval the number of milliseconds to wait before attempting to retry a workgroup server that is down, a value greater than or equal to 50 ms, normally 1000 ms.
    port is the port number iServer is listening on, normally port 8080.
    retry the number of workgroup server to try to connect to, normally 3.

    Notes:
    A separate Server parameter must be entered for each workgroup server.

  4. Add the following Virtual Directory.

    For Microsoft Personal Web Server using Personal Web Manager click on Advanced and add the following Virtual Directory.

    Directory the directory where the iServer ISAPI Gateway was installed, normally c:\iws\bin\win32.
    Alias the base URI used to access the ISAPI Extension, normally igateway.
    Access the privileges, normally Execute.

    For Microsoft Internet Information Server using Internet Service Manager right mouse click on the Web Site, then click on New, followed by Virtual Directory and Use the New Virtual Directory Wizard to add the following Virtual Directory.

    Alias the base URI used to access the ISAPI Extension, normally igateway.
    Directory the directory where the iServer ISAPI Gateway was installed, normally c:\iws\bin\win32.
    Permissions the privileges, normally Execute.

    For Microsoft Internet Information Server after adding the Virtual Directory above, select the newly created Virtual Directory by right mouse clicking on igateway, then click on Properties and then on Directory Security tab. Finally in the Directory Security tab click on Edit and then set the Authentication Methods by selecting Allow Anonymous Access and clearing Basic Authentication and Windows NT Challenge/Response.

  5. Define the ISAPI Filter.

    For Microsoft Personal Web Server update the Registry.

    1. Modify c:\iws\install\win32\pws.reg as needed.

      "Filter DLLs"="c:\\iws\\bin\\win32\\isapiGateway.dll"

      Note: Each \\ represents a single \

    2. Register it.

      regedit c:\iws\install\win32\pws.reg

    For Microsoft Internet Information Server using Internet Service Manager right mouse click on the Web Site, then click on Properties and then on ISAPI Filters tab. Finally in ISAPI Filters tab add the following Filter.

    Filter Name the name of the Filter, normally isapiGateway.
    Executable the path to the ISAPI Filter,
    normally c:\iws\bin\win32\isapiGateway.dll.

  6. Restart the computer.
 top of page
 Built with iScript Copyright © 1997-2000 Servertec. All rights reserved.
Last Modified: Sun Jan 09 21:37:57 EST 2000