Build and Deploy Sakai by running Maven. Perform appropriate Post-installation Configuration of the application. Migration from an earlier version of Sakai typically involves a database conversion for which scripts are supplied with the release , an update to any custom skins, and possibly changes to any custom code see the Release Notes to learn if this is the case.
For links to the conversion scripts, see the Database Configuration section of this guide. Installation Guide Next. Installation Guide. Table of Contents 1. Overview 1. Choose an Install Type 1. Demo Installation 1. Binary Installation 1. Source Installation 1. Migrating from a Previous Release 2. Set up Environment 2. Verify Java Installation 2. Verify Java Environment Variables 2.
Install Tomcat 2. Configure Tomcat 2. Install Maven 2. Configure Maven 3. Build and Deploy 3. Download Source 3. Unpack Source 3. Run Maven 4.
Post-Installation Configuration 4. Create folder for properties file 4. 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. If you don't wish to track and merge changes with subversion you can use 'svn export' instead. For 2. 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.
Oracle's Sun Java SE 6 , a. If are still running Java 1. There may be occasions when you want to build and deploy Sakai without executing the set of unit tests that accompany many of the Sakai modules. If so add -Dmaven. The programmers' cafe build profile is favored by many developers new to Sakai as well as those developing or testing new capabilities. Overview Blog. Sakai 12 install guide source. Created by Former user Deleted.
Last updated: Dec 14, by Wilma Hodges. To begin with the following items must be installed you may skip any you all ready have installed. Java 1. Oracle's Sun Java SE 8 , a. To confirm that Java is both installed on your system and is the correct version for Sakai, run java -version from the command line: java -version If Java is installed, basic version and build information will be displayed.
Example output: java version "1. Several environment variables and related properties must be set for Java. Use a reasonably current version of Git to get the source. Extract the distribution archive into your installation directory.
The Apache Maven project management framework provides Sakai with "a set of build standards, artifact repository model and a software engine that manages and describes projects" Better Builds, p.
As part of the installation process you will use Maven as a build tool in order to compile, test and deploy Sakai to a servlet container such as Apache Tomcat. A number of environment variables must be set for optimal Maven performance. Later versions of Tomcat may cause problems. Append -Dsakai. Specify -Dsakai. Some other configuration from the Sakai 21 and prior example may also be relevant.
There are two ways to acquire Sakai source code. Sakai source code can be checked forked from our Github repository. The latest development work is located in the master branch ; stable releases can be found in tags while maintenance and other work is performed in a Settings in sakai.
All settings in sakai. You may want to create a local. Properties listed in local. For list of sakai. Tool collections for the home page can be configured for each site type. However, if the wsetup. Synoptic tools will be added or dropped from home page depending on whether their linked tool exists in the site or not.
Site maintainers can now create groups based on sections and roles. To switch back to the old 2. Sakai includes a property called inactiveInterval org. Sessio nManager, which dictates the length of inactive time before a users session times out and allows for the enabling of a session timeout warning.
Session status is now checked by the Sakai portal. If the remaining session time is less than the warning time say 10 minutes. When a session expires, the any page requests are redirected to the URL indicated by the loggedOutUrl sakai property. Enabling Sakai to both send and receive email requires setting a number of properties in sakai. Recommend running on , and using a standard mailer on 25 to forward mail to Sakai.
0コメント