Starting with version 2.80 Web Connection also supports Netscape Web servers or any other Web Server that can operate via CGI. CGI configuration by the Setup program is only partial with only the files being copied, but no configuration settings made on the Web server itself. The following steps describe Netscape installation, but they apply equally for other CGI servers.

• Configure NetScape Server to use CGI and make sure you can run CGI scripts on your server prior to installing Web Connection. You will need to create a virtual directory that allows CGI execution manually and then use Setup to copy the Web Connection files to this directory.

• Run the Web Connection Setup program and select Netscape server.

• The setup program will ask you for a virtual directory to copy the Web Connection Executable and sample HTML files to. This directory must be a path that can Execute CGI scripts (as configured through the Netscape Web Administration interface). The Netscape Virtual Directory setting and Execute rights must be configured manually!!!

• The CGI file installed is NPH-WC.EXE with a configuration file of NPH-WC.INI. All script links you see in this documentation as WC.DLL will have to be adjusted to NPH-WC.EXE. The Setup program automatically changes all the code and sample page links automatically to NPH-WC.EXE, so the demos should run without change.

• CGI servers require a slightly different version of the wwRequest object that handles the differing CGI server variable names. Instead of wwRequest you need to use wwShellCGI (contained in wwPostRequest.prg). The following code change in the startup program is requried to make this happen

  *** Load the Web Connection class libraries
  DO WCONNECT
  
  *** Load the server - wcDemoServer defined below
  goWCServer=CREATE("wcDemoServer")
  
  *** If running a CGI Web server uncomment the following line
  goWCServer.oRequest = CreateObject("wwShellCGI")  
  

  
  Operation with Netscape or any other CGI server does not allow operation as an Automation server since CGI executable load once and immediately unload after completion and thus can't keep an automation server alive.