• A Java Servlet Engine/Container. Must be compatible with the Servlet 2.2 API. Note that Jetspeed is developed under Tomcat (http://jakarta.apache.org) so this is the most desirable platform.
• JDK 1.2 or higher Java Virtual Machine. Jetspeed has been tested on most SUN and IBM Virtual Machines.

This installation procedure covers installing Jetspeed as a J2EE Web Application. Installing a Web application is simple. With Web apps, the entire application can be contained in a single archive file and deployed by placing the file into a specific directory.

Here are the complete steps for downloading Jetspeed, building it, and then installing the default Web Application.

• 1. Checkout the complete Jetspeed source from our CVS server. You will need to logon to the CVS server as anonymous and then execute these CVS commands:
  • set CVSROOT=:pserver:anon@cvs.working-dogs.com:/products/cvs/jetspeed
  • cvs login .......... (password is "anon")
  • cvs checkout jetspeed
• 2. Build Jetspeed
  • cd <jetspeedRoot>/build
  • [Win32/DOS] .\build webapp
  • [Win32/cygnus] bash build.sh webapp
  • [unix] ./build.sh webapp
• 3. Get a Servlet 2.2 runner (container). We use Tomcat in this installation.
  • Tomcat Homepage
• 4. Unzip the Tomcat distribution

• 5. Copy the Jetspeed WAR file to the Tomcat webapps directory
  • [Win32] copy <jetspeedRoot>\bin\jetspeed.war <tomcat_home>\webapps\
  • [Unix] cp <jetspeedRoot>/bin/jetspeed.war <tomcat_home>/webapps/
• 6. Start Tomcat
  • [Win32] <tomcat_home>\bin\startup.bat
  • [Unix] <tomcat_home>/bin/startup.sh
• 7. Connect to Jetspeed
  • http://localhost:8080/jetspeed/
  • There are 2 default accounts created:
  • • Login: turbine Password: turbine
    • Login: admin Password: jetspeed
• 7a. When signing up a new user in Jetspeed, the registration process includes a step where an email is sent to the new user. In order for this process to work on Windows NT or 2000, you will need to have a local SMTP server running. The Apaches James Mail Enterprise Server is available from:
  • http://java.apache.org/james/
  • The mail host settings will need to be modified:

  <tomcat_home>/webapps/jetspeed/WEB-INF/conf/TurbineResources.properties

Jetspeed uses Turbine's security model to authorize users and persist minimal user information. Turbine security should work with any JDBC 2.0 compliant driver. The following databases are tested:

• DB2
• Hypersonic SQL
• MySQL
• Oracle
• Postgres
• Sybase

Jetspeed is distributed with a populated Hypersonic-SQL database. This database is selected as the default database in the TurbineResources.properties file. To configure Jetspeed with a different database, modify the TurbineResources.properties file. Here is an example for Oracle:

• database.default.driver=oracle.jdbc.driver.OracleDriver
• database.default.url=jdbc:oracle:thin:@<host>:1521:<sid>
• database.default.username= <your-oracle-user>
• database.default.password= <your-password>

You will need to replace:

	the host of the Oracle instance, such as localhost
	the name of Oracle database sid at the host
	the oracle user(schema) name

The TurbineResources.properties file can be found in /webapp/WEB-INF/conf.

The database scripts for setting up the database are included with the source code distribution, under the src/sql/external folder. Run the appropriate script, such as turbine-db2.sql for DB2, to create the database tables. This step is not necessary with Hypersonic SQL.

To populate the database, a script is provided: /src/sql/external/default_roles_persmissions.sql. Only run the statements for your specific database as commented.

The script will create two database users:

• Login: turbine Password: turbine
• Login: admin Password: jetspeed