


                            JaBaSE 1.5 final release




               CopyRight 1997 Axel Irriger <Silvan@Technologist.com>



1. Introduction

        First, thank you very much for using JaBaSE.
        My main purpose while creating was that it should be a small but fast and efficient server.
        I really hope I reached this goal ;))
        For suggestions concerning this server I'm available at every time ;)
        My next project will be an offline-browser..
        But : Don't think, I'll not to go in developing JaBaSE. To go on I need help. It's impossible for me         to 'forsee' what extensions are wanted.
        So, if you have *any* suggestion for further version, please e-mail me with a brief description of 	          your suggestion. You can reach me *always* at"Silvan@Technologist.com". Please understand, if I don't                         mail you back at onces, but I *will* answer *any* e-mail I get! And I'll tell the person, if the thing                         is possible he/she wants..

2. Installation

        It's not hard to install JaBaSE. The only thing to do is to extract the archiv into a directory of         your choice.
        Then, you have to configure the server.
        I wanted, to make the neccessary informations to make as easy as possible, but following some         descriptions...

3. first-time configuration

        The configuration program is called "SetConfig.class". It's started using the java interpreter or some         kind of runtime kit.
        On my machine, using Windows95 by Microsoft, the line is "java SetConfig".
        Now, your asked for some informations which are neccessary for JaBaSE to run!
        The questions : 
        "Please enter WWW-Port: "                       Here a you have to enter a port,
                                                        on which JaBaSE is initialised.
                                                        Normally you enter "80" here.
                                                        But if you run it in an IntraNet
                                                        where you also have "normal" Internet
                                                        access you can initialise it on an
                                                        other port.

        "Please enter WWW-Root-Directory:"              Now you must enter a directoryname.
                                                        In this directory the server searches
                                                        for requested files.
                                                        Is the directory within the server dir
                                                        you only have to enter the sub-dir name.
                                                        Else you must specify the whole directory
                                                        name.
                                                        For example : The server is installed in
                                                        "d:\Server\" and the HTML-files are in
                                                        "d:\Server\files" so you can just enter
                                                        "files".
                                                        But if the files are in "d:\HTTPFiles" you
                                                        have to enter "d:\HTTPFiles". Otherwise the server
                                                        would be unable to find the files....
                                                        The directory name or path does not follow a "\".

        "Please enter WWW-standard-file:"               The server's always sending a file, if there's no                                                         specific request from the client.
                                                        For example, if you type in NetScape's Navigator
                                                        "http://www.myServer.com/myFile.htm" the client wants                  						                the file "myFile.htm" to be sent.
                                                        But if you only enter "http://www.myServer.com" the                                                                                                                 client does not specify a file. In this case a                                                         standard-file is sent.
                                                        This file you can specify here.
                                                        Normally the file is called "index.htm" or                                                                                                                 "index.html", but this isn't a must ;))

        "Please enter the complete path to the perl-interpreter with file name:"
                                                        This information is neccessary for executin Perl-CGI
                                                        Scripts.
                                                        Is the perl-interpreter is *not* reachable by just 								  typing "perl" you have to enter the whole path to the 								  interpreter.
                                                        Else you can just enter "perl" ;))
	
        "Please enter relative CGI-directory:"           Are the HTML-File located in "d:\HTMLFiles" it's (at                                                              the moment) a must that the CGI-dir is within this                                                             dir, as a sub-dir.
                                                        You have to enter the dir here. It's usually called  								  "cgi-bin" without slash(!) "\". You can also call it                                                         							         as you want...
       "Should the Error-Window be merged to the Main-Window [true, false] : "
								  This specifies if errors should be shown in the 								  main window or if a second window should be 								  opened. If you've got a small monitor or 								  normally many windows open, you better type in 								  "yes" (without '"' of course). Then all errors 								  will be displayed in the main window. Otherwise 								  type in "true" (also without '"');

        Okay, after entering these things a file is created calles "server.cfg".
        It's a normal text-file, so you *can* modify it yourself instead of running "SetConfig".

4. Starting the server

        After this "first-time configuration" you can start the server.
        This you make by typing "java Server" or starting a runtime kit with "Server" as the class-file.         ("Server.class" is the main file!)
        Now the server will initialise itself.
        If nothing went wrong, you see the line "Server init successful" with printing the WWW-Port and the         WWW-root-directory.
        Now the server's waiting for incoming requests.
        In the window "Errors" you can see errors during data transmission or so (if you specified it,                otherwise they will be shown in the main window!)
	  There are some points under "Aministration" of interest for you. With "Online configuration" you can         change everything typed in the normal configuration, except the WWW-Port.
        Under "Access Statistics" you find a statistic of files requested by the users with the times of                 request.
        Uhm, the last point "Shutdown server" should be self-explainative ;-) If not, try and test lol

        All Error-reports are important for *you*.
        If there are any understanding problems or problems with fixing the errors I will help you, if I can.
        I would be really pleased if you tell me any problems.
        I can only fix them and make it more efficient if I can speak with the users!

I hope the documentation wasn't too long and everything is understood now.
If not, feel free to e-mail me and I'll fix the section or add some things!


                                   1997 Axel Irriger <Silvan@Technologist.com>

