GoServe: Installation

Installation

If you followed either of the 'getting started' documents, you will have already installed GoServe. In general, only two files (plus data) are needed to run GoServe as a Web or Gopher server: the GOSERVE.EXE program file, and the appropriate Rexx filter. The default filter name has filename GOFILTER, with an extension that is the TCP/IP port number to be used (for example, 'GOFILTER.80' for the filter for a default Web server, or 'GOFILTER.70' for the filter for a Gopher server). The filter must be in the working directory for GoServe.

It is recommended that GOSERVE.EXE and the Rexx filter be placed in one directory (for example, 'D:\GoServe'), and data for the server be placed in a different directory. By default, the latter is expected to be on the same drive as the GoServe directory, and named '\gohttp' for a Web server or '\gogopher' for a Gopher server.

Both the data directory and the filter name can easily be changed by using the GoServe options notebook or by a command line option, if required.

In all cases, the Rexx filter must be in the working directory for GoServe. The working directory is also used by GoServe for the GOSERVE.INI file (which holds user settings, such as window position and audit selections), and for any Audit and Audit Archive files.

When you unzip the GOSERV.ZIP file, you should find the following files:

goserve.doc -- this document gohttp.doc -- how to get started as a Web server gogopher.doc -- how to get started as a Gopher server goserve.exe -- the server program gofilter.80 -- sample (working) filter for HTTP gofilter.70 -- sample filter for Gopher goremote.80 -- sample filter for WWW remote control of GoServe moveaud.cmd -- sample remote control command makeicon.cmd -- installation aid

gohttp.zip -- sample pages, etc., for a Web server [unzip to a separate directory, perhaps D:\GoHTTP]. This also includes the GoServe Web documentation in HTML. gogopher.zip -- sample menus, etc., for a Gopher server [unzip to a separate directory, perhaps D:\GoGopher]

license.txt -- IBM license agreement for OS/2 Tools

Please see the 'how to get started' documents for step-by-step instructions for installation.

Uninstalling GoServe

To uninstall GoServe, it is only necessary to delete the directories used by GoServe, with their contents. No changes are made to the OS/2 system. (Note that prior to version 1.74, GoServe saved settings in OS2.INI. Later versions automatically migrate this information to the GoServe working directory.)

Requirements

GoServe is a 32-bit OS/2 application, which requires OS/2 2.x or OS/2 Warp. For OS/2 Warp, version 1.31 (or later) of GoServe is needed.

GoServe requires TCP/IP for OS/2, or equivalent, to be installed and operational (either on a real network or using the loopback driver). Only the TCP/IP base kit should be needed, or the OS/2 Warp Internet Access Kit from the Bonuspak.

Over time, CSDs for TCP/IP become available--if TCP/IP problems are suspected, always try the latest CSD.

Running GoServe 'stand-alone'

GoServe and Web Explorer can be run on a stand-alone machine that is not connected to a network, provided that TCP/IP is installed and the loopback driver is started. This is especially useful for developing Web pages offline, or for demonstrations. To do this, two additions are needed to a standard TCP/IP installation (such as the OS/2 Warp Internet Access Kit):

To the file called 'HOSTS' (no extension) in your \TCPIP\ETC directory add the line:
```
  127.0.0.1  loopy
```
where 'loopy' is the name by which you want your machine to be known when using the loopback connection. This name can be a single word (e.g., 'loopy'), or an internet-style name (e.g., 'loopy.my.org'). It's a good idea to have both formats, on two lines:
```
  127.0.0.1  loopy.my.org
  127.0.0.1  loopy
```
If there is no \TCPIP\ETC\HOSTS file, create one.
Before running GoServe, execute the command:
```
  ifconfig lo 127.0.0.1
```
This only needs to be run once, so can be run from STARTUP.CMD or from any command referenced in your Startup folder. Note that the second word is the lowercase of the two letters 'L' and 'O'.

Once set up, you can then connect to GoServe on your own machine using (for example) the URL:

  http://loopy

The loopback address will be active even when connected to a network, so you can always connect to GoServe running on the same machine using the loopback name that you chose, provided that your browser does not have a proxy or SOCKS server enabled (the proxy won't be able to find your local loopback address).

Even if you are not connected to a network, your browser should not have a proxy or SOCKS server enabled (or it will try and use the network to find it before checking the HOSTS file).

[ previous section | GoServe | next section ]