When downloading a release build, there are three kinds of builds that you can download:
|Release 1.6 (Latest) - May 26, 2005||Download From:|
|Jetspeed Release 1.6 - Binary||jetspeed-1.6-war.zip|
|Jetspeed Release 1.6 - Source||jetspeed-1.6-src.zip|
|Release 1.5 - April 22, 2004||Download From:|
|Jetspeed Release 1.5 - Binary||jetspeed-1.5-war.zip|
|Jetspeed Release 1.5 - Source||jetspeed-1.5-src.zip|
|Release 1.4 - October 29, 2003||Download From:|
|Jetspeed Release 1.4 - Binary||jetspeed-1.4-war.zip|
|Jetspeed Release 1.4 - Source||jetspeed-1.4-src.zip|
The Jetspeed Nightly Builds are automatically updated from CVS every night on the Jakarta server. Each zip file is a snapshot of the entire CVS at the end of the given day. You will need to build Jetspeed from the nightly snapshots. The last seven builds are available for download in both GZIP and ZIP formats. The last seven builds are available from here: Nightly Builds
The best way to get the latest Jetspeed source is to checkout directly from CVS. Follow the Jakarta CVS instructions available here and checkout the jakarta-jetspeed module.
cvs -d :pserver:firstname.lastname@example.org:/home/cvspublic login
cvs -d :pserver:email@example.com:/home/cvspublic checkout jakarta-jetspeed
To check for a particular date, use the -D option:
cvs -d :pserver:firstname.lastname@example.org:/home/cvspublic checkout -D 2002-06-04 jakarta-jetspeed
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.
The default Jetspeed deployment uses its own 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:
Jetspeed is distributed with a populated Hypersonic-SQL database. This database is selected as the default database in the Torque.properties file. To configure Jetspeed with a different database, modify BOTH the project.properties in the root directory and the webapp/WEB-INF/conf/Torque.properties file. Here is an example for MySQL:
Another example for Oracle:
You will need to replace:
|<host>||the host of the Oracle instance, such as localhost|
|<sid>||the name of Oracle database sid at the host|
|<username>||the oracle user(schema) name|
The Torque.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, scripts are provided: /src/sql/external/populate*.sql. Only run the statements for your specific database as commented.
The script will create two database users:
If you would also like to store your PSML resources in the database, see the instructions here.
Due to classloader problems involving the XML parser, Tomcat 4.1.x is suggested.