Installing Sakai

Added by Mark J. Norton, last edited by Peter A. Knoop on Aug 23, 2006  (view change)

Before installing Sakai, you may want to consider what Sakai Training is available.

Installing Sakai comes in two flavors at this time:

Sakai 1.5 QuickStart Installation

Use the [ARCHIVE:Sakai 1.5 QuickStart Edition] installation procedure to install the last complete version of Sakai. This version uses the Hypersonic database, so if you want to use mySQL or Oracle, you will additional configuration work do do.

Sakai 1.5 Developer Installation

Use the [ARCHIVE:Sakai 1.5 Developer Edition] installion procedure to install the very latest Sakai code from the CVS tree. This also uses Hypersonic, but that's generally preferred for development since the databases are small and in-memory. You may need to re-configure for another database if you are specifically developing against it.

Sakai 2.0 Installation

Three packages will be available for Sakai 2.0:

QuickDemo - Get from zip file to running in less than 5 minutes.

QuickProd - Get source zip file and instructions on how to compile Sakai and configure it for MySQL and Oracle. This should be suitable for building a customized installation of Sakai suitable for a particular institution. This includes localizing skins and building a local provider. It is not suitable for new tool development. This environment is not connected to the Sakai CVS server.

Development - The local developer creates a local development environment referencing the Sakai CVS server. This environment is suitable for tool development. This environment is not supplied, the local developer will need to read documentation on the Sakai 1.5.1 website to setup the environment.

The reason that QuickProd is not connected to CVS is that it would not be useful. The installer can't check in their changes since they are local to their institution. They won't be making changes to core Sakai code since they are trying to put the released version into production. The user won't expect to get updates from CVS since they are dealing with a released version and, in the case of 1.5.1, dealing with a branch that won't get further development.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (1)

 

  1. Apr 11, 2005

    Anonymous says:

    Some linux servers require additional steps in order for sakai to startup proper...

    Some linux servers require additional steps in order for sakai to startup properly. This is because the sakai-z-last webapp is loaded differently by tomcat on these systems. If on startup you see a number of bean creation errors (evident in the catalina.out log), and you see a blank screen when viewing sakai, you should try this workaround:

    Add a context file for each war file in the jakarta-tomcat-[version]/webapps directory. This is done by going into the jakarta-tomcat-[version]/conf/Catalina/[host] directory and copying the
    sakai-portal.xml to sakai-[module].xml for each war and replacing the contents of the file with the appropriate module name. Do this for each one except the sakai-z-last webapp. This forces the sakai-z-last module to load after the others, and sakai will startup as expected.