Team@Work Web Application Installation Guide 

Guide Contents 
1. Prerequisites. 
  a. Installation package. 
  b. Third party required software. 
    i. Java Development Kit. 
    ii. Jakarta Tomcat. 
2. Installation Procedure. 
  a. Preparation. 
  b. Installation. 
  c. Configuring the web application. 
  d. Testing and troubleshooting. 
  e. Finishing instructions. 

--------------------------------------------------------------------------------

1. Prerequisites 
To install correctly Team@Work web application some requirements should be met prior to installation. 

1.a. Installation Package. 
When you install the Team@Work server package a subdirectory is created in the installation directory, which is called web_client.
In this directory you will find a Java Web Application Archive (.war file) named "teamatwork.war".
This application is installed into a web container (currently only Tomcat 4.1 is supported).
This guide will explain the installation procedure. 

1.b. Third party required software. 
If you have a Jakarta Tomcat version 4.1.24 up and running with a Sun JDK 1.4 or newer you can skip this section and go directly to 2. Installation Procedure. 

1.b.i. Java Development Kit. 
Prior to installing/configuring the Jakarta Tomcat you need to download, install and configure an appropriate Java Development Kit.
The Team@Work web application requires a Sun JRE 1.4 or newer, so the required JDK is the Sun's JDK 1.4 or newer.
If you don't have it installed already you can download it from:
	http://java.sun.com/j2se/downloads.html

Install the JDK prior to continuing the setup process. 


1.b.i. Jakarta Tomcat. 
The Team@Work Web Application is a Java Web Application and as such requires a JSP/Servlet container to run.
Currently the only supported JSP/Servlet container is Jakarta Tomcat 4.1.
If you do not have a running version of this container you can download it from:
	http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.24/
	http://jakarta.apache.org/tomcat/

If you don't know which version to download keep in mind that you need a binary release of the container.
Also keep in mind, that due to more narrow JDK selection (Sun's JDK 1.4 is a prerequisite) you can download the *-LE-jdk14.* file, which is smaller because it does not contain packages, that are included in newer JDK versions. 


2. Installation Procedure 
These notes provide information about the installation procedure itself.
These instructions presume, that you have downloaded, installed and configured a running Jakarta Tomcat Web Container version 4.1.x according to the installation instructions of Tomcat and that the JDK version you are using is Sun JDK 1.4 or newer.

2.a. Preparation. 
Before you can install the Team@Work web application you need to find the "teamatwork.war" file. If you haven't copied it take a look at section 1.a. Installation package. 

2.b. Installation. 
To install the Team@Work web application copy the teamatwork.war file to the webapps directory, found in the Tomcat installation directory.

Windows:
The directory would look like:
	C:\Program Files\Apache Group\Tomcat 4.1\webapps 

LINUX:
The directory would look like:
	/usr/local/jakarta-tomcat-4.1.24/webapps 

If you haven't yet started the Tomcat Web Container it is time to do that. Start the Tomcat Web Container.
After you copy the .war archive the Tomcat server should automatically pick it up, decompress it and instantiate the web application. You can check that by openning a web browser (such as Internet explorer) and going to address:
	http://localhost:8080/teamatwork/
If the installation has gone well you should see the Team@Work web client index page.
Please note that 8080 is the default port for Tomcat. Usualy you don't need to change it. If you prefer another port for some reasons, you must substitute 8080 with the correct port number. The port is specified when installing the Tomcat Web Container. If you want to change it consult Tomcat documentation on how to do that.

2.c. Configuring the web application. 
After you have seen, that the application is up and running, you have to set up the connection between the web application and the Team@Work server.
To do that open a web browser on the computer that runs Tomcat and go to address:
	http://localhost:8080/teamatwork/setup.jsp

Remember to substitute "8080" with the correct port number, if needed.
For security reasons the setup page can only be accessed from the localhost, so you have to be on the same machine, on which the Tomcat is running. You can not configure the web application from a remote machine.
On the setup page fill in the host and port where Team@Work server is running.
Press the Save Data button to store the connection settings.
To check if you have set up the web application correctly go to the Team@Work web client index page at:
	http://localhost:8080/teamatwork/

Log in with the built-in user name "administrator" and password "123456". If the Team@Work server is running and the connection parameters are set correctly, you should enter the application. If the Team@Work Server is temporarily down, or the connection parameters were wrong, a message occurs. 

2.d. Testing and troubleshooting. 
If a problem emerges the first source where you should look is the Tomcat documentation. Make sure you have installed correctly the Sun JDK and the Tomcat Web Container. Make sure the JDK and the Tomcat Web Container are really the required versions (Sun JDK 1.4 or newer and Tomcat version 4.1.24 or newer). Please note, that Tomcat 5.x may NOT be compatible with the 4.1.x family. Tomcat 5.x.y is a different Web Container family, not a newer version.

A typical mistake is made by the Tomcat Windows installer if you have an older version of the JDK installed on your computer. In that case you will receive errors when trying to look at the server pages that state: "Invalid class version 48.0, expected 47.0" or a message resembling this one. This means, that the JDK Tomcat is running on is different that the JDK that Tomcat uses to compile the Java Server Pages (JSPs). Consult the Tomcat documentation on how to set up correctly the JSP compiler. Normally that involves setting up OS environment variables and copying files from the JDK to Tomcat.

If the web application is accessible, but error messages occur when trying to log in make sure the application is set up correctly as stated in 2.c. Configuring the web application. 

2.e. Finishing instructions 
The Java Server Pages are compiled on-first-run, and that can take some time on slower machines. It is a good practice to log in as a user after installing the application and to navigate through the pages, so that they can be compiled and ready for use by the users. Browsing through the pages will normally take a couple of minutes. 
