6. Prepare your database

• 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/melete282.sql,

OR

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.

7. LTI Configuration (Optional)

Melete can link to Publisher's content using BasicLTI and SimpleLTI (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.

Sometimes a vendor gives 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.

Configure below stated properties in Sakai.properties file to set site-wide license. This is just an example here, your vendor will give you the key/url and passwords.

basiclti.consumer_instance_guid=etudes.org
basiclti.consumer_instance_name=Etudes Inc
basiclti.consumer_instance_url=http://etudes.org
basiclti.consumer_instance_secret.mhhe.com=xxxxx

basiclti.consumer_instance_key.dr-chuck.com=lmsng.school.edu
basiclti.consumer_instance_secret.dr-chuck.com=secret

Properties for SimpleLTI lauch are:
simplelti.org_id=etudes.org
simplelti.org_secret.appspot.com=secret

For detailed specifications, you can consult this document.
https://source.sakaiproject.org/svn/basiclti/trunk/basiclti-docs/resources/docs/sakai_basiclti_portlet.doc

Back to Top

8. Update Sakai Roles

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.

1. Log on as Sakai admin.

2. 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.

3. 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.

CAUTION: a. IF YOU FAIL TO CHECK THE MELETE.STUDENT AND MELETE.AUTHOR PERMISSIONS FOR YOUR ROLES, MELETE WILL NOT WORK PROPERLY. b. IF YOU ADD MELETE TO _EXISTING SITES_, USERS WILL NOT HAVE THE MELETE PERMISSIONS THAT YOU CHECKED. YOU WILL NEED TO USE !SITE.HELPER OR OTHER SCRIPT TO PROPAGATE THE MELETE PERMISSION TO EXISTING SITES.

9. Melete Portal Icon

If you are using sakai's default cascading style sheet create the icons folder under tomcat/webapps/library/skin/default/

or download it from here.

and copy the image modules-menu.png from melete-app/src/webapp/melete/images to

tomcat/webapps/library/skin/default/icons.

Add the below line to tomcat/webapps/library/skin/default/portal.css

.icon-sakai-melete
{
background-image: url(icons/modules-menu.png);
}

Questions?

Contact sakai-dev@collab.sakaiproject.org or dev@etudes.org

Up | Install Guide | Upgrade Guide | Permissions | Common Problems

Back to top