Child pages
  • SCORM Cloud Integration
Skip to end of metadata
Go to start of metadata

Integration of SCORM Cloud, the hosted SCORM player from Rustici Software

About the Player

The SCORM Cloud player quickly and easily adds SCORM to a Sakai installation. It gives you compatibility with SCORM 2004, SCORM 1.2 and AICC in about five minutes by adding a new Resource Type to your system with obvious gradebook integration as a bonus feature. Recently added as a feature of SCORM Cloud is a new reporting tool that lets you dig deep to see what your users are doing within a course.

Courses installed with the SCORM Cloud player are hosted in the cloud, ready to be called whenever you need them. There are monthly charges for hosting, but a free trial account is available so you can play with SCORM Cloud to see how it works with your courses and system. Trial is based on number of registrations, so you can technically run a trial forever. (OK, a while. There are limits.) And now you can even play with SCORM Cloud prior to integration. Just upload your course, then send out a link to a learner/student (or yourself); click the link, launch the course, see SCORM Cloud in action!

Currently available for versions 2.5.x and 2.6.x.

Always happy to answer any questions about SCORM Cloud here or over in our support forum.


Installation & Configuration

Import & Launch (Including Gradebook Integration)

Reporting Features



Install of the SCORM Cloud module should only take about five minutes. It involves copy and paste of three sets of files, registering your account and that's about it.

  • Download and extract the .zip file (either version 2.5.x or 2.6.x).
  • Copy the scormcloud-pack folder into the components folder in your Sakai installation.
  • Copy the scormcloud-api-0.8.jar into the shared folder of your Sakai installation. (The number is the version number, so that changes.)
  • Copy the scormcloud-tool.war folder into the webapps folder of your Sakai installation.
  • Restart your Sakai, then log in and go to the administration workspace.
  • Create a new worksite and select SCORM Cloud on the list of tools for the site.
  • Go to your new worksite and click SCORM Cloud in the left-side navigation menu.
  • Click configure plug-in on the welcome screen.
  • Add your SCORM Cloud account information (link to sign up if haven't yet) that came in your welcome email or click the link within the mod to sign up for a free trial account.
  • You should see SCORM Cloud available as a new Resource Type!

Source Installation


Once you've added the plugin to a particular site, there are two main steps to configure it. The first is ensuring that the right Sakai roles have the correct permissions for using the plugin, and the second is entering the some information related to the SCORM Cloud service.

Setting permissions for various tools is a typical Sakai administration task, and the permissions associated with the SCORM Cloud plugin are no different, so we won't go into detail about how to set permissions, but we'll instead note the permissions that are unique to the plugin below.

  • scormcloud.admin: Any role with this security permission will be allowed to do nearly any activity with the plugin, such as creating, configuring, previewing, and deleting SCORM resources, as well as viewing and utilizing the interface found in the SCORM Cloud tool that will be linked to from the tool menu after installation. This role is intended for only site administrators (teachers and teacher assistants).
  • scormcloud.configure: This is essentially the one separate permission from those granted by scormcloud.admin listed above. This permission must be granted in order to view and update the credentials used for the SCORM Cloud service. Typically, if those credentials will be installation-wide (used for all sites), a Sakai administrator will set them after installation and will have no need to grant this permission to any role. However, if credentials will be site-specific and not installation wide, an administrator will need to grant this permission to whatever role should be allowed to set those credentials for a given site.
  • No labels