                              ChemConsoleServer v-0.3
                                       by 
                                   Nathan Stevens
                                nat250@cyberwar.com

/*
 * ChemConsoleServer
 * Copyright (c) 1999 Nathan Stevens, all rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted.
 *
 * This software is provided "as is" and any express or implied warranties,
 * including, but not limited to, the implied warranties of merchantability
 * or fitness for any particular purpose are disclaimed. In no event shall
 * Nathan Stevens be liable for any direct, indirect, incidental, special,
 * exemplary, or consequential damages (including, but not limited to,
 * procurement of substitute goods or services; loss of use, data, or
 * profits; or business interruption) however caused and on any theory of
 * liability, whether in contract, strict liability, or tort (including
 * negligence or otherwise) arising in any way out of the use of this
 * software, even if advised of the possibility of such damage.
 */  

Contents:
  1) About
  2) Installation
  3) Using
  4) Bugs
  5) TO DO

About:
  ChemConsoleServer, as the name implies, is the Server component of the
  ChemConsole client software. It basically extends the functions of 
  ChemConsole from a single machine to a network of machines almost 
  seamlessly.

Installation:
  To use ChemConsoleServer you must have a JRE1.1.* VM installed, which has 
  support for RMI (Remote Method Invocation). The only Java VM I know of that
  doesn't have RMI support built in is Microsoft's VM, Jview, so don't use it
  either for the Client or the Server. The host computer must also have 
  networking configured correctly else the Server will not work. 

  First thing to do is get the correct file for your platform.
  CCServer-0.3.tar.gz                                     Unix
  CCServer-0.3.zip                                       win32

  Next follow the instructions for installing ChemConsole to finish the rest 
  of the installation. There should now be a directory named CCS-0.3 in the 
  installation directory. Change to CCS-0.3 directory and using a text editor 
  edit the startup script "ccs.sh" or the bat file "ccs.bat" to fit your 
  specific platform.

Using:
  The first you thing need to do before starting the ChemConsoleServer is to 
  edit the configuration files in the "Config" directory. Using a text editor
  open the file "main.cfg", you should see three numbers in there. The first
  is the number of Babel clients allowed to connect, next is the max number of 
  of mopac clients and finally the max number of gaussian clients. Change
  these values to fit your needs. Next open the "babel.cfg" file and change
  value in there to fit you needs. The first line determines weather the 
  BabelServer is accepting clients, is either true or false. The next lines 
  contains the location of the Babel binary. The "mopac.cfg" file as a similar
  format with one extra line with tells the program weather or not to keep or
  remove the "*.dat" ending of Input files. Set it to true if the version of
  Mopac you are using requires that the  "*.dat" extension be removed when 
  specifying the input file name, set false other wise.
  
  Once that you are done with configuration, start the RMI Registry in the 
  background if it is not already running.
  In Unix this would be  "rmiregistry &" 
  In win32 this would be "start /min rmiregistry"
  Now execute the correct, previously configured script for your platform. A
  messages should appear confirming that the ChemConsoleServer is indeed 
  running. If you want to view the Stats of ChemConsoleServer while it's running
  just use the "-v" option. For example in UNIX this would be "ccs.sh -v".
  
  note: 
    If you plan on providing Mopac services on the ChemConsoleServer please
    consult the file  "mREADME.txt" in this directory.   
   
Bugs:
  There should be at least one nasty bug I missed, so if you find it send a 
  detailed description of the bug to my email addresses. (nat250@cyberwar.com)

TO-DO:
  1) Implement the other services that the client now supports
  2) Add remote addmistration capabilities
  3) Add a GUI configuration tool  
  4) Do real make file
  5) Clean up code
  
note:
  Some are you maybe asking, what's with the O.3 version number? What 
  happened to version 0.1 and 0.2? Well, technically this is the 0.1 version, 
  but to make it easier for users to determine what version of ChemComsole 
  will work with what version ChemConsoleServer, I decided to make them both 
  have the same version number.  For example, a 0.3 version of ChemConsole 
  would require a 0.3 version of ChemConsoleServer and so on. 



