Installation instructions to deploy Melete 2.9.9 for Sakai 10.1.
Melete supports MySql4.1 and MySQL 5.0.xx, Oracle and HSQLDB.
- Get the Source
- Configure Melete
- Configure Commercial Sferyx Editor (Optional)
- Internationalize Messages (Optional)
- Modify Sakai Distribution, Compile and Deploy
- Prepare your Database
- LTI Configuration (Optional)
- Update Sakai Roles
- Melete Portal Icon
- User Documentation
Download the etudes-util and ltiContact (dependencies of Melete) and Melete software from SVN into your Sakai 10.1 source folder
sakai> svn co https://source.sakaiproject.org/contrib/etudes/etudes-util/tags/1.0.25/ etudes-util
sakai> svn co https://source.sakaiproject.org/contrib/etudes/ltiContact/tags/1.2/ ltiContact
sakai> svn co https://source.sakaiproject.org/contrib/etudes/melete/tags/2.9.9 melete
2.1 Packagingdir settings
The dependency files for the IMS-SCORM export process are in the /var/melete/packagefiles directory in the Melete source code.
a. Copy the /var directory and its contents into a directory. Make sure the owner and group of the directory is same as tomcat user.
b. Configure melete.packagingDir setting in Sakai.properties
Eg. If you are on unix/linux, and your packaging directory path is /var/melete/packagefiles, specify in sakai.properties.
2.2 Max Upload size for IMS import file
By setting this Sakai property, system administrators can set a different file upload limit for Melete IMS CP import than the upload max limit for content files. If this property is not set, then Melete assumes the max value as 50MB.
2.3 Print Material Default Setting (Optional)
By setting this Sakai property, system administrators can set the default preference for Melete Print. Instructors can change this setting for their site in Melete Preferences.
This is an optional setting. If not set, then Melete assumes default as “true”.
3.1 Sferyx Source
Purchase a license and binary source for Sferyx 10.2 or higher (http://www.sferyx.com)
Download sferyx from https://source.sakaiproject.org/contrib/etudes/sferyx/trunk and place it under sakai source directory.
Place the purchased applet jar file under /src/webapp/sferyx.
Compile and deploy sferyx webapp using maven.
3.2 Default Melete Editor
This is done by specifying the following property. For example, if the default Melete editor is Sferyx,
If this property is NOT set, the code uses the editor specified by the wysiwyg.editor property.
3.3 Set Available Melete Editors
You can set more than one editor in Melete (Sferyx and CK Editor, for now). Users can select their default editor for authoring under Melete’s Preferences.
List the editor choices for users in sakai.properties as specified below. For example, if the user has two choices, Sferyx and CK Editor, the settings will be as follows:
NOTE: Make sure that the names have proper spaces as this is used to display the labels of the available editors on the Preferences page.
If you want to run Melete in a different language than English, you need to update messages.properties of your language under melete-app/src/bundle and under melete-impl/src/bundle.
5.1 Code Change for Oracle Users ONLY
The Melete code uses the “straight_join” keyword for query optimization with a Mysql join. Oracle does not support this keyword. Please remove this keyword from melete/melete-impl/src/java/org/etudes/component/app/melete/ModuleDB.java.
5.2 Update the Sakai base pom.xml
Add lines to the Sakai master/pom.xml properties and dependency management section for the Etudes artifacts.
a. Properties: add to the <properties> section:
b. Dependencies: add to the <dependencyManagement><dependencies> section:
Note: This version is configured to build with Sakai 10.1. If you are using another version, you need to make a few changes.
The “10.1” version number is in a few files, used as the version number for the Sakai base pom. You need to edit these files to change this to match the version of Sakai you are using:
5.4 Run maven commands
Build your sakai including etudes-util, ltiContact and Melete. When you use maven to build sakai, it will include the sources needed for Melete.
Melete works with HSQLDB, Oracle or Mysql Database. It has been tested on Mysql4 and Mysql 5, but it has been deployed successfully with Oracle at many universities.
Melete shares the same database as Sakai’s and adds a few tables to the database.
Set up the Melete tables
You can either run the sql script manually; it is provided under /components/src/sql/mysql/melete29m9_upgrade.sql
Turn on auto.ddl and when tomcat starts, hibernate will generate the Melete tables on its own by reading xml files.
NOTE: With Auto.ddl on, check these secondary indices.
Index has been created for user_id column of melete_user_preference and course_id column of melete_course_module table.
Remove any duplicate indices. Index on module_id column of melete_course_module and melete_module_shdates table. section_id column of melete_section_resource table.
Melete can link to Publisher’s content using BasicLTI (IMS Basic Learning Tools Interoperability standard).BasicLTI allows the launching and sharing of information with an externally hosted tool using standard protocols, signed securely using the OAuth (www.oauth.net) security mechanism.
To use this feature, enable “Show Link to Publisher’s Content option” under Melete preferences.
Configure Sakai.properties to set BasicLTI.
basiclti.consumer_instance_guid=your institution domain name
You can either provide secret/password at the section level or you can set a site-wide license to some content i.e a single secret/password that is used to sign all of the requests coming from a LMS system. Here is an example to configure it.
basiclti.consumer_instance_key.<Provider domain name> =lmsng.school.edu
basiclti.consumer_instance_secret.<Provider domain name>=secret
For detailed specifications, you can consult this document.
Update Sakai Roles (under realms) to include Melete permissions to your roles. If you are upgrading Melete in your Sakai instance, no roles changes are needed.
Log on as Sakai admin.
Check appropriate Melete permissions under the roles in !site.template.course.
Check melete.author for instructor, teaching assistant types of roles (maintain) to which you want to give ‘authoring / manage’ rights.
Check melete.student for student types of custom roles that you have (access) to which you want to give ‘viewing’ rights.
If you have project sites and related roles in !site.template.project, appropriate permissions (melete.student or melete.author) need to be checked as defined above, based on what rights you want to give to the roles.
If you are using sakai’s default cascading style sheet create the icons folder under tomcat/webapps/library/skin/default/
and copy the image modules-menu.png from melete-app/src/webapp/melete/images to
Add the below line to tomcat/webapps/library/skin/default/portal.css
See relevant tutorials in our help pages.
Melete is licensed under the Apache License, Version 2.0
Contact email@example.com or firstname.lastname@example.org