Sakai Logo

Sakai 2.7.1 maintenance release

Release Date: 24 August 2010

The Sakai 2.7.1 maintenance release provides a significant number of bug fixes that provide improved stability, performance and security for the sakai-2.7 series.


Steve SmailThe Sakai 2.7 series is dedicated to the memory of Steve Smail, Programmer/Analyst in Library Information Technology at Indiana University, who died in late December 2009. He was a respected and long-time member of the Sakai developer community; many knew him through his work on the Sakaibrary project, Citations Helper and previous library resource integration efforts as well as his regular participation at Sakai conferences.

Issues Addressed


Core projects tracked separately:



Demo: The Sakai Demo is a pre-built version of Sakai with Apache Tomcat and a simple configuration, perfect for a quick and easy demo of Sakai. The Sakai demo is NOT intended for large scale implementations. It is suitable only for evaluating the software and running small pilot implementations on a single server. Win md5
Mac/*nix sakai-demo-2.7.1.tar.gz md5
Binary: The Sakai Binary is a pre-built version of Sakai without Apache Tomcat, jar dependencies, or extra configuration files. Download the Binary release if you want to just drop the Sakai bundle into a pre-existing Tomcat environment. Win md5
Mac/*nix sakai-bin-2.7.1.tgz md5
Source: The Sakai Source is all the Sakai source code for this release.  Start from Source if you plan to make any code-level changes to your Sakai system. Win md5
Mac/*nix sakai-src-2.7.1.tgz md5
Javadocs Win md5
Mac/*nix sakai-javadoc-2.7.1.tgz md5

Source Code

Sakai uses Subversion for source control and provides maintenance branches - which include the latest bug fixes - for its most current releases. You can check out Sakai 2.7 using a subversion client. If you don't wish to track and merge changes with subversion you can use 'svn export' instead.

2.7.1 tag: svn co 2.7.1

2.7.x Maintenance Branch: svn co 2.7.x

Trunk (latest development) svn co trunk


For 2.7.1 release notes, installation guides and other documentation visit our 2.7 documentation space in our public wiki.

System Requirements

Sakai is Java-based and will run on a wide variety of platforms. That said, a number of supporting technologies are required to run Sakai in a production setting.

Java SE 6

Oracle's Sun Java SE 6, a.k.a Java 1.6, is the preferred version to use with Sakai 2.7. Certain files, such as *.jsp and *.jws, require compilation so downloading and attempting to use only the run time environment (JRE 6.0) will not suffice. Mac OS X 10.6 (Snow Leopard) includes the full version of Java SE 6 so Mac users do not need to install Java. If you find Sun's version and naming conventions confusing, see Sun Java SE Naming and Versions for an outline of their practices.

Oracle's Sun Java 2 Platform Standard Edition 5.0 (J2SE JDK 5.0) (a.k.a Java 1.5) has completed the EOL process and is no longer supported. If are still running Java 1.5 please note that security vulnerabilities exist in JDK/JRE 5.0 updates 1.5.0_17 and earlier. Sun recommends that you install JDK/JRE 5.0 Update 18+ (the final update is JDK/JRE 5.0 Update 22).

Applet Warning: security vulnerabilities have been reported for applets under certain minor versions of the JRE. Sakai does include some applets, so see Sun's security alert to get details on recommended minor versions.

Apache Tomcat 5.5.30

Although Tomcat is not the only available servlet container, it is highly recommended for Sakai, and the documentation assumes Tomcat use. Sakai QA was conducted on Tomcat 5.5.30, and this is the recommended version.

Tomcat 6.0.x: Sakai 2.7.1 is not compatible with Tomcat 6.0+ out-of-the box (OOTB).

IBM Websphere 6.1+

As an alternative to Apache Tomcat, Sakai also supports the IBM Websphere Application Server. Websphere 6.1 is a J2EE 1.4 compliant application server. It supports Java Standard Edition 1.5 and provides an enterprise-level platform for hosting the Sakai CLE in a secure, scalable, and highly available application server environment. To install Websphere, follow these instructions.

Apache Maven 2.0.10+

Maven 2 is the build tool used to deploy the source code and is therefore not necessary if you only plan to install the Sakai Demo with the default configuration. For production deployments it is an essential supporting technology.


MySQL 5.1+ (table type: InnoDB), MySQL 5.0.45+ (table type: InnoDB); Oracle 10g, 9i; DB2 9.1, 9.7, HSQLDB (demo only)

Sakai utilizes HSQLDB as its "out of the box" database, requiring no special installation steps to set up but this database is not recommended for production installations.

MySQL InnoDB: Sakai requires transaction support so the InnoDB storage engine is required for MySQL deployments.

Database Drivers

For MySQL 5.1/5.0 we recommend mysql-connector-java-5.1.13+ with query caching enabled.

Regardless of the version of Oracle in use, we recommend using a recent Oracle 11g driver (See SAK-11960.)

New Developers

The best introduction for new developers is found in a wiki space called the Programmer's Cafe. A number of experienced Sakai developers have banded together there to produce guides and tutorial materials for those who wish to start hacking on Sakai.

Issue Tracking

Bug reports and feature requests may be created and monitored through Jira.

Older Releases

With the advent of the Sakai 2.7 series, official Community support for Sakai 2.5 ceases. Organizations running Sakai 2.5 (or earlier versions) are strongly encouraged to upgrade to the latest versions of Sakai 2.6 or 2.7 in order to take advantage of continued maintenance support.


The Sakai 2.7 series is licensed under the: Educational Community License version 2.0.