After you have finished the installation, you need to create a configuration file and
verify that your installation and basic configuration were successful.
To finish the installation:
- Create a file called isapidispatch.ini in the application root directory; a
sample file can be found in the FGLASDIR\etc directory.
- The GAS ISAPI Extension should be ready to use. Open a web browser and enter the URL to the
"demos.html" page. The URL should look
like:
http://<server>:<port>/<virtual directory>/demos.html
For
example, if the server is "localhost", the port is the default port, and the virtual directory is
"gas", then the URL should be:
http://localhost/gas/demos.html
If
everything is correct, the "demos" page should be displayed; otherwise, see Troubleshooting
installation.
Note:
- All requests having an URL that begins with the virtual directory
name, for example "/gas/", will be served by the GAS ISAPI Extension.
Files present in the application root directory will not be served
by IIS. There is no way to configure IIS to change this behavior.
Therefore, the isapidispatch.ini file should be the only file
present in the application root directory.
- While IIS allows you to map more than one wildcard application
to a virtual directory, the GAS ISAPI Extension should be the last
one of the list, as it will not forward URLs to other ones.
- As in the standalone GAS, the GAS ISAPI Extension serves application
resource files and static files, such as demos.html.