************************************************************** * Instructions for installing * the Training Management Databas ************************************************************** 1. It is assumed that a machine has been set up to run both Oracle and a web server that supports servlets (such as JavaWebServer1.1.3). We'll also need the appropriate JDBC for the database that we are using (presumable Oracle 8). We'll call this machine , and it could have, for example, the name carver.npac.syr.edu. We will assume that JavaWebServer has been installed and is located in the directory . For example, it may be located under /npac/home/mpierce/JavaWebServer1.1.3/. 2. The following files are needed to run the Training Database: (a) admin.sql, table.sql, sequence.sql: SQL files for setting up the data tables and sequencing them. The admin.sql file provides the system with an initial administrator. The data, name, and password should be changed as soon as possible. These are provided in the release. (b) oracle.zip: Dynamically creates the html pages from the data in the tables. (c) Training.jar: Contains the java classes required to interact with the database. Provided in the release. (d) configure.txt: Some configuration information that is used by the jar file. Can be edited. Provided in the release. 3. Log onto the database and load the tables and sequences at the sql prompt: [dbServer> source ~oracle/.cshrc [dbServer> sqlplus marlon/marlon [sql> @tables.sql [sql> @sequence.sql [sql> @admin.sql The first two lines are executed by the unix shell. The three sql files must be executed in the order shown. 4. Modify the CLASSPATH variable in .cshrc to the following: CLASSPATH=.:/usr/npac/java/lib/classes.zip:/lib/class es111.zip:/lib/oracle.zip:/lib/jws. jar:/lib/javac.jar:/servlets/Traini ng.jar The file classes.zip should come with the JDK release. The files classes111.zip, jws.jar, and javac.jar should come with the JavaWebServer release. If the CLASSPATH variable is already set, you may want to change the following to CLASSPATH=<...all the above stuff...>:$CLASSPATH. 5. Place all files described in Section 2 in the appropriate directories, as given in the CLASSPATH list above; i.e. put Training.jar in /npac/home/mpierce/JavaWebServer1.1.3/servlets. The file configure.txt also goes in the servlets directory. 6. Reread the CLASSPATH shell variable: source ~/.cshrc. 7. Restart the httpd daemon. If you are using JavaWebServer, this can be done with the Admin Tool. 8. Move the gif images provided to /public_html/images. This location can be changed by modifying the config.txt file. 9. You can now access the Welcome page from a web browser: http:///servlets/ascdb.pub.WelcomePage ascdb.pub.WelcomePage is a servlet that is included in the Training.jar file. You may also wish to create a servlet alias for this file. If you are using JavaWebServer, start the admin tool, click the modify button, choose the option "servlet alias" and then choose "add". You can then alias the above servlet as "Training". The welcome page can then be accessed by a web browser at the web page http:///Training. Note the above assumes you are using port 80 for the httpd daemon. 10. To use the interface, it is first necessary to add entries for Country, State, and Surtitle to the Lookup Tables. These are needed in order to add classes and users. 11. IMPORTANT NOTE: JDBC connects with the data base through a Driver Manager (DM). The DM has a URL address like this jdbc:subprotocal://host:port/databasename so, for instance, on carver the above line is jdbc:oracle:thin@carver.npac.syr.edu:1521:europe. This will have to be changed to something appropriate for the ASC system. This line is given in the file configure.txt that is included with the distribution, as are other important text strings that might possibly need to be modified. 12. Note that the CLASSPATH must be set correctly, as described above, for the Java Webserver daemon httpd to be able to access the data base pages. In other words, if you want to use the machine carver.npac.syr.edu as the data base server, then if you start httpd on this machine as root, then root must have the proper $CLASSPATH as described above. Note that clients do not need to set their classpaths to use the database.