VM:Webgateway Web Server
Select where you want to go:

System Administrator Tasks - Configuration

Overview
Converting Webshare Configuration
Identifying System Administrators
Identifying System Operators
Identifying TCP Sockets and Server Root Domains
Defining Characteristics Associated with a Filetype
Setting Up Filters for Static Files
Setting Up VM:Webgateway to Serve Files from User Pages
Identifying CGI Userids
Allowing Users to Change VM Passwords from a Browser
Setting Up VM:Webgateway Accounting
Setting VM Options
Setting Up VM:Webgateway to Use Worker Machines
Configuration Quick Reference

Identifying TCP Sockets and Server Root Domains


Summary of Information to Specify | Information in Detail

You can configure TCP sockets and server root domains from a web browser using the Configure TCP Sockets configuration form or from a VM userid that has SYSADMIN authorization using the CONFIG SOCKET command.

Summary of Information to Specify

  1. IP address and TCP socket
  2. Location of the server root domain
  3. Contact name and e-mail address of the person or group responsible for maintaining the information served from the server root domain (optional)
  4. Whether you want VM:Webgateway to serve data using SSL (if you are using SSL Feature)

Information in Detail

  1. IP address and TCP socket

    The IP address identifies a host computer's Internet address.

    VM:Webgateway receives requests to serve data from a web browser through TCP/IP. Before VM:Webgateway can receive requests, a VM:Webgateway system administrator must indicate a TCP socket VM:Webgateway will use to listen for requests from web browsers.

  2. Location of the server root domain

    Identify the server root domain that VM:Webgateway associates with the TCP socket.

    When VM:Webgateway receives a URL from a web browser, the request comes in on a specific TCP socket. VM:Webgateway looks for the data to serve on the server root domain associated with the TCP socket on which the request was received.


    Note: You can define more than one TCP socket for VM:Webgateway to use. Each TCP socket is associated with only one server root domain.

    A system administrator can use one of the following for the server root domain:

    Minidisk
    When serving files from a minidisk, the files you want to serve must reside on a single minidisk. The VM:Webgateway SVM must have read access to the minidisk, and every file you want to serve must be identified in one or more DIRMAP files.

    SFS directory
    When serving files from an SFS directory, the files you want to serve must reside in a single SFS directory or its subdirectories. The VM:Webgateway SVM must have read authorization to the SFS directory, its subdirectories, and all files you want to serve.

    BFS directory
    When serving files from a BFS directory, the files you want to serve must reside in a single BFS directory or its subdirectories. The VM:Webgateway SVM must have read and search permissions to the directory and subdirectories. In addition, VM:Webgateway must have read permission to all static files you want to serve and read and execute permissions to all CGI programs you want to serve.

    CMS search order
    When serving files using CMS search order, the files you want to serve must reside on minidisks or in SFS directories accessed by the VM:Webgateway SVM. If more than one version of a file exists, VM:Webgateway serves the first version it locates using the CMS search order. The VM:Webgateway SVM must have read access to each minidisk from which it will serve files. The VM:Webgateway SVM must have read authorization to each SFS directory from which it will serve files and also read authorization to each file it will serve. Every file you want VM:Webgateway to serve must be identified in one or more DIRMAP files.

  3. Contact name and e-mail address of the person or group responsible for maintaining the information served from the server root domain (optional)

    You can optionally specify a contact name and e-mail address that VM:Webgateway will display on configuration forms and in certain communications to users. Examples of such communications are:

    • Messages stating the product's configuration was successfully updated.
    • Output generated by a CGI programmer.
    • Error documents that VM:Webgateway serves when it encounters problems serving files from the server root domain. VM:Webgateway uses the e-mail address to include a mailto: URL. With the contact information in an error document, the web browser user who receives the error document can report the problem to someone who can fix it.

    What you specify affects how the message displays.
    • If you specify both a contact name and e-mail address, the message will read, "Send comments or questions to contact-name," where contact-name is hyperlinked to the mailto: URL. The e-mail is automatically addressed to the contact's e-mail address.
    • If you specify only a contact name, the message will read, "Send comments or questions to contact-name." There is no hyperlink to the mailto: URL.
    • If you specify only a contact e-mail address, the message will read, "Send comments or questions to email-address," where email-address is hyperlinked to the mailto: URL.
    • If you specify neither contact name nor contact e-mail address, no message will display.

    From a web browser: On the View, Change, Delete, or Add TCP Socket Definitions configuration form, enter contact information in the Contact name and E-mail address fields.

    From a VM userid: Use the CONTACTNAME and CONTACTEMAIL options on the CONFIG SOCKET command to specify the contact information.

  4. Whether you want VM:Webgateway to serve data using SSL (if you are using SSL Feature)

    From a web browser: On the View, Change, Delete, or Add TCP Socket Definitions configuration form, indicate whether you want to use SSL by responding to the question Do you want to use SSL?.

    From a VM userid: Using the CONFIG SOCKET command, indicate that you want to use SSL by specifying the SSL parameter or indicate that you do not want to use SSL by specifying the NOSSL parameter.

    If you are turning SSL on, specify the SSL parameters.


Top
Select where you want to go:

Copyright © 1998, Sterling Software, Inc.