Info |
---|
About this pageThis page is focused on upgrading from Sakai 22 to Sakai 23. It provides a link (below) to the Sakai 22 upgrade information that you will need if you are upgrading first to Sakai 22. Do that first and then come back here for the final steps to migrate to Sakai 23. |
Select here to upgrade to Sakai 22, a prerequisite for upgrading to Sakai 23. If you are already on Sakai 22.3, you can ignore this link.
1.0 Database Conversion Scripts
Please run ALL the scripts from your original version to the version to which you are upgrading. There are two sets of database upgrade scripts, one for MySQL and one for Oracle. Use the appropriate scripts for your database type.
...
The current version of Sakai at the time Sakai 23.0 was released was Sakai 22.3, therefore make sure you upgrade to 22.3 before upgrading to 23.0. If your on a later version of Sakai 22 then you may need to adjust your script to remove lines that you already have run in 22.4 from the 22 script.
2.0 Post upgrade tasks
Elasticsearch/OpenSearch
Elasticsearch was replaced with it’s open source fork OpenSearch. According to OpenSearch the index from Elasticsearch 7 are compatible and it may not be necessary to rebuild the index completely. However if your coming from another version of Sakai or have some issue then here are the steps:
While the node(s) have been shutdown remove the elasticsearch work directory
OpenSearch will begin indexing new documents automatically
to add existing previous to the upgrade to the index there are 2 options
rebuild only specific sites
An admin will access each site they wish to rebuild and go to the search tool where they will see the Admin tab
There will be a button to rebuild only this sites index
rebuild all sites
An admin will goto a site with the search tool where they will see the Admin tab
There will be button to rebuild the whole index
Rebuilding the whole index can be a time consuming task and for those with terabytes of data it can take days, therefore it will be wise to perform this task during a low usage time.
Reminder rebuilding the whole index doesn’t have to be done immediately after an upgrade and can scheduled independently, you could even have solution where option a is used until there is a window to rebuild the whole index.
3.0 Browser Compatibility
Sakai is designed to work with modern browsers. Recommended browsers (those with the most QA testing effort against them) are Google Chrome, Safari, and Mozilla Firefox. Microsoft Edge should work fine. Sakai should work on most modern tablet and mobile devices. IE 11 is a poor browser choice as it is deprecated, slow, and has not implemented modern features. New functionality like Rubrics, may not work with IE 11.
4.0 Upgrading the Sakai skin
https://github.com/sakaiproject/sakai/tree/master/reference
...