Configuring your Web Server on Windows

These instructions cover the two most popular web servers for Windows.

• The first is the Microsoft offering which is either IIS or PWS. PWS is known as the Personal Web Server under Windows 95 and Windows 98 and as Peer Web Services under NT.

• The alternative is to use the Apache web server which can be downloaded for free from the Apache web site.

The instructions for both servers are similar and can be easily applied to other web servers. If you have problems please contact AVS Support.

Microsoft PWS or IIS

1. Check that PWS or IIS is installed properly
   

2. In the PWS Internet Service Manager set up the following virtual directories:
   (Names marked with a * must correspond to the names given during installation. These names can be modified 
   

   Suggested Name	Directory	Possible Value
   /GsharpWE/	The GsharpWE examples	C:\UNIRAS\7v3\example\GsharpWE\
   /GsharpTmpFiles/	Your directory for temporary files	C:\Windows\TEMP\GsharpWE\ or C:\WinNT\Temp\GsharpWE\
   /Gsharp/	The Gsharp On-line Help	C:\UNIRAS\7v3\help\

   and the following directory which can run scripts:
   

   Suggested Name	Directory	Possible Value
   /Gsharp-bin/	The GsharpWE cgi-bin scripts	C:\UNIRAS\7v3\example\cgi-bin\

    

   The location C:\UNIRAS\7v3\ must match the location where GsharpWE in installed.
   
   If you use a name other than /Gsharp-bin/ you will need to modify the following files
   

3. Run the Toolmaster & Gsharp configuration option of the AVS Toolmaster 7.3 program group on the start menu and set the values of GsharpTmpFilesActualDir, GsharpTmpFilesWebDir and GsharpWEcgi-binDir to match the values used in step 2.

   In step 2 the following examples were used:

   GsharpTmpFilesActualDir: C:\Windows\TEMP\GsharpWE\ or c:\WinNT\Temp\GsharpWE\
   GsharpTmpFilesWebDir: /GsharpTmpFiles/
   GsharpWEcgi-binDir: /Gsharp-bin/
   

4. Make sure the directory for holding your temporay files exists and can be written to by your web server.

5. Reboot your system and restart the web server.
   

6. GsharpWE should now work. You can try the examples by loading the following file in your browser: http://yourmachine/GsharpWE/

Setting Up the Apache Web server 

1. Check that Apache is configured properly to run on your machine.
   
2. Edit the Apache configuration file conf/httpd.conf and set aliases for the Gsharp directories that you will be using e.g.

   Alias /GsharpWE/ "C:/Program Files/Gsharp 3.3/example/GsharpWE/"
   Alias /GsharpTmpFiles/ "C:/Windows/TEMP/GsharpWE/"
   #Alias /GsharpTmpFiles/ "C:/WinNT/TEMP/GsharpWE/"
   Alias /Gsharp/ "C:/Program Files/Gsharp 3.3/help/"
   
   ScriptAlias /Gsharp-bin/ "C:/Program Files/Gsharp 3.3/example/cgi-bin/"

   Note that the location specified above must match the lacations specified when running the Toolmaster & Gsharp Configuration option of the AVS Toolmaster 7.3 program group on the start menu.

If you use a name other than Gsharp-bin you will need to modify the following files

You can also use the conf/httpd.conf file to set up the environment variables which tell Gsharp about your installation (You can also set these variables using the Configure Gsharp option of the Gsharp program group on the start menu).

SetEnv GsharpTmpFilesActualDir "c:/Windows/TEMP/GsharpWE"
#SetEnv GsharpTmpFilesActualDir "c:/WinNT/TEMP/GsharpWE"
SetEnv GsharpTmpFilesWebDir "/GsharpTmpFiles/"
SetEnv GsharpWEcgi-binDir "/Gsharp-bin/"

1. Finally some older versions of Apache require that you configure them to use the registry to decide which application to use to run each script. If the following line is included in your httpd.conf then uncomment it.

   ScriptInterpreterSource registry

   The GsharpWE Installation process configures Windows so that files with a .gsw extension use GsharpWE.

2. Make sure the directory for holding your temporay files exists and can be written to by your web server.

3. Restart the Apache Web Server and you should be able to run the GsharpWE examples from http://yourmachine/GsharpWE/. If you still get problems, check the error log file for the Apache web server.