For the stable project submission, each group is required to setup their project on the Alfalfa.rutgers.edu running Tomcat using the CS Oracle account previously provided. Depending on how organized your code is, this may be a very easy process or may require some changes. Please make sure to fully try your application out on the new server.

Preliminary Steps

• All URLs referenced by your application either on the server or client should be relative. If any absolute URLs are required, you must store the link for this URL in a text file so that it can be easily changed without recompiling code.
• As mentioned on multiple occasions and in the project description, your client must be launched as a jar file using JNLP and Java WebStart. JNLP is not very different from what you did in Assignment 3 with executable jars except that instead of modifying a MANIFEST.MF file, you must modify the appropriate JNLP files. Please review recitation notes (9/25/2006) for help.
• Your program will be tested from a stand alone computer that has a browser and the JRE installed. Eclipse nor any other installed code will be permitted in demonstrating the project. PLEASE TEST YOUR APPLICATION BY RUNNING IT FORM MULTIPLE MACHINES

The server alfalfa.rutgers.edu contains one tomcat installation and one root web folder for each team. A "Hello World" index.html has been placed in each web application folder to give you an idea where things belong. Refer to the following chart for information about each group:

Group	Server Folder	Server Port	Web Application Folder	URL
Konnightion	/projects/cs431/ServerInstalls/tomcat-konnightion	9001	/projects/cs431/AppFolders/Konnightion	http://alfalfa.rutgers.edu:9001/
GradTracker	/projects/cs431/ServerInstalls/tomcat-gradtracker	9002	/projects/cs431/AppFolders/GradTrackers	http://alfalfa.rutgers.edu:9002/
LaserWolf	/projects/cs431/ServerInstalls/tomcat-laserwolf	9003	/projects/cs431/AppFolders/LaserWolf	http://alfalfa.rutgers.edu:9003/

You can start/stop Tomcat by going to the server folder's bin directory and running the startup.sh/shutdown.sh scripts. By default, all of your servers have been started so the link provided should work initially.

Guidelines for setting up your project:

• Post only compiled code. Since groups will be able to access other groups work, no source code should be posted.
• You web application should have a single html file that points to a single client file. *ALL* of the swing code should be packaged into a single JAR that is loaded via Java Web Start.
• While your Client must be a single JAR and an HTML, your server should be composed of multiple class files, all of which will be placed in the WEB-INF/classes folder.
• For the server setup, you will also need to upload any library jars you are using as well as the proper web.xml.

Final Words: Server setup is a non-trivial task that even with the best designers can still have many unforeseen problems, so don't be too upset if your code doesn't work right away. There may also be network or quota problems that arise, so please do not hesitate to e-mail both Scott Selikoff and Lars Sorensen if you are experiencing problems related to the network. Also, Scott Selikoff is available for general assistence.