3) Configure Commercial Sferyx Editor
(Optional)
Sferyx applet is moved out of melete webapp and now
lives in its own webapp.This is to simplify melete rollout process.
-
Download sferyx from
https://source.sakaiproject.org/contrib/etudes/sferyx/trunk and place
it under sakai source directory.
-
Place your purchased applet jar file under /src/webapp/sferyx.
-
Compile and deploy sferyx webapp using maven.
NOTE: Make sure
you configured melete.uploadDir setting in Sakai.properties (See step 2).
4)
Internationalize Messages (Optional)
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.
Image buttons are no longer required and is read from
messages.properties file as text.
5) 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
6)
Compile Melete
First, undeploy any previous Melete versions from your source before
deploying Melete 2.7.2 as artifacts name has changed.
At the command prompt, go to the melete source directory which you placed
under sakai and run maven commands just like you did for sakai.
To build and deploy Melete, run 'mvn clean install sakai:deploy'
Notes:
- If you are using a sakai version other than 2.6.1, before building,
change the version in pom.xml. The default version in pom.xml is
<version>2.6.1</version>. Sakai version can be obtained from master/pom.xml
from version element.
7) Database
Changes
Few tables are modified. Run upgrade script manually.
- Mysql Users: /components/src/sql/mysql/melete27_upgrade.sql
- Oracle Users: /components/src/sql/oracle/melete27_upgrade.sql
Start tomcat, make sure there are no errors in the logs.
Questions?
Contact sakai-dev@collab.sakaiproject.org or dev@etudes.org
Up | Install Guide | Upgrade Guide | Permissions | Common Problems
Back to top
