When Web Server Utility detects a Web server, it displays two types of entries in the Add Detected Web Server dialog: the Web server’s static page aliases and its CGI aliases.
Static page aliases
A Web server’s static page alias maps a URL to a file-system directory. When given a URL to a static page, the Web server uses the information in its static page alias to locate the file specified in the URL.
When you select a static page alias in Web Server Utility’s Add Detected Web Server dialog and click Add, Web Server Utility creates a new .hdr site configuration file. The .hdr file contains information that the HAHTsite
Chapter 3: Web server configuration (WinNT)
CGI aliases
A Web server’s CGI alias maps a URL to a program file. When given a URL to a CGI program, the Web server uses the information in its CGI alias to locate the program specified in the URL.
When you select a CGI alias in Web Server Utility’s Add Detected Web Server dialog and click Add, Web Server Utility creates a new .hca site configuration file. The .hca file contains the information the HAHTsite IDE/IP needs to build a URL to the HAHTsite Application Server’s hsrun program.
If you have Perl scripts or other program files that you want to publish to a Web server’s CGI directory, check the Add as Static box. Web Server Utility will create a new .hdr file, which will enable you to publish, from the HAHTsite IDE/IP, your program files to the Web server’s CGI directory.
To set up an interface to a detected Web server
Here are the recommended steps for setting up a configuration for a detected Web server and a HAHTsite Application Server.
1 Click and expand the Web server you want to use.
A typical Web server directory tree includes:
• A single directory whose name is the same as that of the host.
• Under this directory, a list of the Web server’s static page and CGI aliases.
To examine a component that you may want to add, click to select the item and then click Properties.... For example, if you click /cgi-bin in the preceding figure and click Properties..., a dialog like the one shown below appears. (The fields in this dialog are read-only.)
The dialog in Figure 3-4 indicates that, on the host “barney,” the Netscape FastTrack administrator has created an alias named cgi-bin pointing to the HAHTsite directory d:\hahtsite\cgibin. The URL field shows the URL that points to this HAHTsite directory.
The following is an example of the dialog’s Port tab:
The Port tab indicates that the Netscape FastTrack server on Barney uses port 80 and searches directory d:\hahtsite\doctree for static files.
The Web Server tab (not illustrated) displays the name and revision of the Web server.
3 After inspecting the information, click OK to return to the Add Detected Web Server dialog.
4 Click Add to add the Web server component to the HAHTsite site
Chapter 3: Web server configuration (WinNT)
If Web Server Utility identifies the component as a CGI directory, the checkbox “Add as Static” asks whether static pages should be published to this destination. Where not relevant, the checkbox is dimmed out. In most cases, you should accept the default (no).
If you have Perl scripts or other program files that you want to publish to a Web server’s CGI directory, check the Add as Static box. Web Server Utility will create a new .hdr file, which enables you to publish program files from your HAHTsite project to the Web server’s CGI directory.
Repeat these steps for all expanded items that you want to add. (The Add button is dimmed out if Add is not a relevant action.)
Clicking Add saves the Application Server configuration information you have inspected into the appropriate .hca and .hdr configuration files.
During inspection, if you see a configuration problem (for example, an incorrect URL to the Web server’s CGI directory), you can use Modify (see “To modify a configuration” on page 47) to change the Application Server’s configuration as needed to accommodate the Web server’s configuration.
Alternatively, you can change the Web server’s configuration, using the Web server’s administration tool the run the Web Server Utility again.
To set up an interface to an undetected Web server
Here are the recommended steps for setting up an interface to an undetected web server:
1 If Web Server Utility does not detect your Web server, click Add Web Server to display the Static Web Server Information dialog.
In this dialog, you can browse for and select Web server directories, construct URLs and aliases, and define methods for transferring information between the Web server and Application Server.
2 In the Name field, enter a name to identify this particular Web server interface. This name will appear in the Web Server Utility’s main dialog.
3 From the Web Server Type list box, select the Web server’s type.
4 The Browse URL field contains a URL that points to the Web server’s static (doctree) directory; change it as needed.
5 Click Add... to display the Transfer Location dialog.
Chapter 3: Web server configuration (WinNT)
6 In the Protocol list box, select the method that will be used to transfer files between the Web server and the Application Server: File Copy, FTP, or HTTP.
Note - The Web Server Utility specifies, but does not set up, the transfer method. Thus, File Copy may require a shared directory, while FTP requires you to set up an FTP site. Web Server Utility does not set up these methods.
7 In the Path field, enter the Web server’s doctree directory.
This is the place where the Web server looks for HTML files. If you do not know the name of the directory, click the Browse box on the right of the field.
8 In the OS Type drop-down box, select the Web server host’s operating system: Windows NT, Windows 95, or UNIX.
9 If you selected the FTP transfer protocol, you can optionally add a
Username and Password that will be used to logon to the FTP server when a project is published from the IDE/IP. You can also specify the number of retries if a file transfer fails.
If you do not specify a username and password, the IDE/IP user will be prompted to enter these values at publish time.
10 Click OK to return to Web Server Utility’s main dialog.
Note - In most cases, you will add only one transfer location for a static page alias. However, you can add multiple transfer locations if, for example, you have a mirrored Web site or are using a router that can fetch pages from multiple locations.