ECOMET.TXT -- eComet Internet Application Server Setup
======================================================
Last Revised on July 21, 2000

The Internet Application Server is enabled when specific commands are 
sent to the XAP Gateway from the XAPMON program. Once enabled, any MTB 
program in the XAP directory may be run using the web browser.

Here are the steps involved in setting up the eComet Server. These
instructions assume that the target machine on which eComet will 
be operating is already installed with the TCP/IP protocol and a www 
browser, such as Netscape. Some browsers may require that the machine 
be connected to the Internet before functioning properly.

1. Configure the XAP Gateway

   Specify a TYPE 4 gateway in the [GATEWAYS] section of your COMET.INI 
   file. Only one XAP gateway is required.

2. Configure the XAP Program Directory and the COS System Directory

   a.  Create a Comet directory with the DIR name of "XAP". For security 
       purposes, this will be the only directory from which eComet 
       applications may be run.

       Note: If you have more than 50 directories configured, make sure 
       that the XAP directory is configured in the first 50. If it isn't, 
       eComet will not work (as the program running in a background partition 
       does not access directories beyond the first 50 configured). 

   b.  If one does not already exist, create a COS directory as well.  This 
       is the directory where the CGI environment files will exist. 

       Note: If you have more than 50 directories configured, make sure 
       that the COS directory is configured in the first 50. If it isn't, 
       eComet will not work (as the program running in a background partition 
       does not access directories beyond the first 50 configured). 

   c.  To take advantage of eComet's context preservation feature, you must
       create an additional NON-Comet folder in which COMMON context files 
       will be stored. The location and name of this folder is very specific.  
       It must be called "TEMP" and must be located within the COS directory. 

3. Move the following files into the XAP folder:

     File             Description
     -----------      -----------------------------------
     CGITEST.OBJ      CGI test program
     #XAP             Command file for the XAPMON program
     #XAP.I00         Index file for #XAP

4. Run the Comet Utility menu and select program #13 (DIRMAINT).

   a.  Add the CGITEST.OBJ program to the XAP directory (it's an MTB object 
       program).

   b.  Add the #XAP file to the XAP directory (it's a keyed file, 94/7)

5. Run XAPMON to activate the eComet Internet Application Server

   Status messages will indicate if the server was successfully 
   started. XAPMON will report activity every 10 seconds. If you escape 
   out of it with F2 or F3/F10, the XAP Gateway will still be active. 

6. Run CGITEST from the browser.

   From the same machine, the following URL may be used:

      http://localhost/xap/cgitest

   From another machine on the network, you must know the IP address of 
   the eComet machine. For example, if the IP address were 192.168.1.1,
   then the following URL may be used: 

      http://192.168.1.1/xap/cgitest

   You should see a browser screen signifying successful execution of 
   CGITEST. This program may be used to display query strings sent from
   the browser, cookies, and the CGI Environment Variables. 


You have finished setting up the eComet Internet Application Server.


Note: The #XAP file may be moved to another Comet directory if desired.
Since the only programs that can be executed by eComet are those that
reside in the XAP directory, you should have total control over the
contents of that directory.