jWWWData: a World Wide Web JDBC Data Base Client
The installation procedure of jWWWData is divided into a set of steps. All of them have to be executed properly before the system can be run.
jWWWData is a Java application using the JDBC SQL API. Before downloading jWWWData you need first to download/purchase and install:
Case 1: ODBC Compliant Database
The Java JDK 1.1.2 already contains the JavaSoft JDBC-ODBC Bridge Driver able interface to all ODBC compliant Data Base Management Systems.
Case 2: JDBC Compliant Database
In some cases (e.g. Decibel) the Data Base management Systems is provided together with the JDBC Driver.
NOTE: the proper installation and configuration of these Data Base Management Systems and their related JDBC/ODBC drivers is responsibility of the end users and is not described in this document.
jWWWData Distribution
The jWWWData Download page takes to a second page containing various compressed files. These are the compressed files:
You should download the set files corresponding to your system.
The distribution files are "pkzip" archives.
Supposing that the files set has been downloaded in the directory
c:\tmp
these are the commands that have to be executed:
c: (the actual target disk must be put here, so instead of c: we could have d:, e: and so on) cd \ (to go to the root) pkunzip -d c:\tmp\htm_w32.zip (to decompress the HTML files) pkunzip -d c:\tmp\jwww_w32.zip (to decompress jWWWData files)
When using a Windows version on "pkunzip" care must be taken so that the original directories/files names are kept.
The distribution files are "tar" archives, compressed with "gzip".
Supposing that the files set has been downloaded in the directory
~/tmp
these are the commands that have to be executed:
cd ~ (to go to the home directory) gzip -dc ~/tmp/htm_unx.tgz | tar xvf - (to decompress the HTML files) gzip -dc ~/tmp/jwww_unx.tgz | tar xvf - (to decompress jWWWData files)
The World Wide Web Server has to be set up in such a way that the jWWWData CGI can access all the relevant HTML files. Supposing that the server is similar to the NCSA one, hereafter are listed the required changes.
In the file "access.conf" an entry similar to the following has to be inserted. This change will make the SWWINGS directory visible to the WWW Server. The actual syntax of the SWWINGS directory name depends on the operating system. In this example the Windows syntax has been used.
<Directory C:/SWWINGS/> </Directory>
In the file "srm.conf", and namely in the "alias" section, an entry similar to the following has to be inserted. This change will allow the hyper-links in the jWWWData HTML pages to work properly. The actual syntax of the SWWINGS directory name depends on the operating system. In this example the Windows syntax has been used.
Alias /swwings/ C:/SWWINGS/
The environment variable CLASSPATH, which specifies where Java has to look for the class files, has to be modified so that it contains the location of the jWWWData class files.
Windows
Supposing that jWWWData files have been put under "C:\SWWINGS" the file AUTOEXEC.BAT must contain a line like the following:
set CLASSPATH=<other directories>;C\SWWING\CLASSES
Unix
Supposing that jWWWData files have been put under "~/swwings" the shell init file (e.g .cshrc) must contain a line like the following:
setenv CLASSPATH <other directories>:${HOME}/swwings/classes
In the same way the environment variable "PATH" must be updated so that it contains the C:\SWWINGS\BIN (or ~/swwings/bin) directory.
It is now possible to create the first schema as described in the Detailed Description.
When the schema is ready, users can ran the schema compiler (swwings.jWWWData.jDComp), using the script (jdcomp.bat or jdcomp.sh) provided in the C:\SWWINGS\BIN (or ~/swwings/bin) directory.
This script will generate the Java module jDSchema.java and a set of scripts files (*.BAT and *.sh) and the starting HTML page.The Java module has to be compiled with the JDK compiler, using the following command:
javac jDSchema.java
The resulting class file jDSChema.class has to be put in the directory specified with the clause #schema-path in the schema itself (see the Detailed Description).
The generated script files can be put, for convenience, in the C:\SWWINGS\BIN (or ~/swwings/bin) directory. The <output name>-cgi.(bat|sh) script needs to be copied in the directory where the WWW Server keeps the CGI scripts.
The generated HTML page needs to be put in the directory, visible to the WWW Server, selected by the users as starting place for accessing the jWWWData system.
The utility <output name>init.(bat|sh) and <output name>-load.(bat|sh) can now be used to initialise and populate the database.
If everything went fine it is now possible to start jWWWData by opening with a WWW Browser the starting HTML page and clicking on the Start button.