Migrating from a previous release

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.

For links to the conversion scripts, see the Database Migration section of this guide.

Changes in sakai.properties

In addition to new sakai.properties values introduced for Sakai 2.5, there are also some changes to address when upgrading from a previous version of Sakai:

(warning) : In Worksite Setup/Site Info the names of properties associated with the ability to add participants via email address have changed:

Old Name (Sakai 2.4 and earlier)

New Name (Sakai 2.5.0 and later)

invalidEmailInIdAccountString

invalidNonOfficialAccountString

noEmailInIdAccountName

officialAccountName

noEmailInIdAccountLabel

officialAccountLabel

emailInIdAccountName

nonOfficialAccountName

emailInIdAccountLabel

nonOfficialAccountLabel

emailInIdAccount.url

nonOfficialAccount.url

emailInIdAccountInstru

nonOfficialAccountInstru

noEmailInIdAccountValue

officialAccountValue

emailInIdAccountValue

nonOfficialAccountValue

(warning) : Upgrade OSP Permissions. If you are upgrading from a pre-2.5.0 version of Sakai, then you need to force conversion of the OSP permissions by setting osp.upgrade25=true in your sakai.properties file. (See also discussion.)

(warning) : The properties associated with the WebDAV authentication cache have changed. In Sakai 2.5.0 and earlier the following properties were used:

maximumSize@org.sakaiproject.user.impl.AuthenticationCache
timeoutMs@org.sakaiproject.user.impl.AuthenticationCache
failureThrottleTimeoutMs@org.sakaiproject.user.impl.AuthenticationCache

These settings have been replaced as of Sakai 2.5.2 with:

maxElementsInMemory@org.sakaiproject.user.api.AuthenticationManager.cache
timeToLive@org.sakaiproject.user.api.AuthenticationManager.cache

(warning) : Those upgrading from a pre-2.5.0 version need to change osp.reports.useWarehouse to sakai.reports.useWarehouse.

(warning) and

Users who have been running Sakai prior to 19 July 2006 release of Sakai 2.2.0 should check the field size of the SAKAI_PERSON_T "Notes" field. A field size change was added to the 2.1.2 to 2.2.0 conversion script on 17 January 2007. Depending on when deployers executed the 2.1.2->2.2.0 conversion script for the 2.1->2.2 upgrade, this update may have been missed. See the following Jiras as well as the sakai-dev "Notes in SAKAI_PERSON_T table" thread discussion for more information.

MySQL

--- reference/trunk/docs/conversion/sakai_2_1_2-2_2_0_mysql_conversion.sql	2007/01/17 18:57:13	20392
+++ reference/trunk/docs/conversion/sakai_2_1_2-2_2_0_mysql_conversion.sql	2007/01/17 19:10:09	20393
@@ -2237,3 +2237,9 @@
 ----------------------------------------------------------------------------------------------------------------------------------------

 ALTER TABLE SAKAI_SESSION CHANGE SESSION_IP SESSION_IP VARCHAR (128);
+
+----------------------------------------------------------------------------------------------------------------------------------------
+-- Increase the field size for the NOTES field in the SAKAI_PERSON_T table
+----------------------------------------------------------------------------------------------------------------------------------------
+
+ALTER TABLE SAKAI_PERSON_T CHANGE NOTES NOTES varchar(4000);

Oracle

--- reference/trunk/docs/conversion/sakai_2_1_2-2_2_0_oracle_conversion.sql	2007/01/17 18:57:13	20392
+++ reference/trunk/docs/conversion/sakai_2_1_2-2_2_0_oracle_conversion.sql	2007/01/17 19:10:09	20393
@@ -2243,3 +2243,9 @@
 ----------------------------------------------------------------------------------------------------------------------------------------

 ALTER TABLE SAKAI_SESSION MODIFY SESSION_IP VARCHAR2 (128);
+
+----------------------------------------------------------------------------------------------------------------------------------------
+-- Increase the field size for the NOTES field in the SAKAI_PERSON_T table
+----------------------------------------------------------------------------------------------------------------------------------------
+
+ALTER TABLE SAKAI_PERSON_T MODIFY (NOTES varchar2(4000));