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

About the Integration

This integration adds a new content type into Resources. This allows you to upload a SCORM package into Resources and registers the content package with Icodeon. Clicking on the name of the resource will launch the Icodeon SCORM player. The advantage to this sort of integration is that SCORM can be leveraged anywhere in Sakai that integrates with Resources via the file picker.

Icodeon posts statistics back into tables that exist in the Sakai database. At this point there are no reports or other features that take advantage of this data. But since we pass the site and learner information to Icodeon, its conceivable this data can be queried for any number of use cases. We'd love for others to get involved to help build out the functionality in this area.

The current integration works with version 2.0.5 of Icodeon.

Screencast Demo


YouTube Demo

Screencast.com Demo

Screenshots

Installation

The version is contrib works against a 2.6 Sakai code base, if you want to run on 2.5 you may need to back port the pom.xml's.

You'll need to grab the Icodeon components for Sakai, the rSmart common contrib module, as well as modify the Icodeon war package.

rSmart common library

You'll want to check this out into an existing Sakai working directory, in the standard contrib way.

2.6.x version

2.5.x version

To build the rsmart-common components add the rsmart-common module the top level pom.xml for Sakai, or manually build from within the rsmart-common module, like this:

Sakai Icodeon Components

The Icodeon components for Sakai can be found in the following module:

You'll want to check this out into an existing Sakai working directory, in the standard contrib way.

To build the Sakai Icodeon components, add the icodeon module the top level pom.xml for Sakai, or manually build from within the icodeon module, like this:

component/

This module contains the content resource type component

impl/

This module contains the content resource type implementation

tool/

This module contains the content resource type associated front end helpers that are necessary to load SCORM packages into Sakai.

The Icodeon launching url is managed in IcodeonHttpAccess. It should be easy to use this existing integration with another player by simply creating an alternative implementation for this class.

icodeon/

The Icodeon war needs to be modified to apply a custom "PlugIn_Resolver", and adjust Icodeon to leverage the same hibernate session as Sakai. This module contains the necessary code and build script to rebuild and deploy the Icodeon War

Steps to Rebuild the Icodeon WAR

This part is not built into the normal Sakai maven build, you'll need to perform the following additional steps in order to deploy Icodeon into Sakai's tomcat:

  1. download and extract the icodeon distribution
  2. modify the paths in the icodeon/build.sh script. The names should be self documenting
  3. cd icodeon
  4. run the build script
  5. restart tomcat

    You'll need to convert the build script to bat or ant if you aren't in a unix friendly environment.

Here's what the build script does:

Configuration

To enable the scorm content resource type you need to add the following to your sakai or local.properties

Technical Information about the Integration

The SakaiCHSResolver is the Sakai custom PlugIn_resolver that is responsible for turning the course_id parameter passed to the player into content. The course_id is actually a reference to content stored in CHS. The resolver extracts the content onto the file system and the player takes it from there.

There are modifications to the provided HibernateUtil.java file to enable a shared hibernate session between Icodeon and Sakai. The work primarily involved moving the existing Icodeon integration code they ship with out of the /maven folder and a shared library containing the model classes, and a component that registers the hbms. Because of Sakai's component manager and handling of shared libraries, this is somewhat a manual process. I wish there was a better way to handle this moving forward, its making deploying Icodeon updates a little tricky. I tried the normal vendor drop approach here, without much luck, because things moved around too much.

There are some modifications to the web.xml to reference the custom plugin and register the persistence engine that captures the learner activity.

3 Comments

  1. a note on the steps to build the icodean war above: they will only work if you have maven set to skip unit tests. This is dangerous behaviour that should not be encouraged (and makes me hesitant to run this in production). The dependencies missing for the tests to run include:

    <dependency>
    <groupId>commons-beanutils</groupId>
    <artifactId>commons-beanutils</artifactId>
    <version>1.7.0</version>
    </dependency>
    <dependency>
    <groupId>org.apache.struts</groupId>
    <artifactId>struts-core</artifactId>
    <version>1.3.10</version>
    </dependency>
    <dependency>
    <groupId>javax.servlet</groupId>
    <artifactId>jstl</artifactId>
    <version>1.1.2</version>
    <scope>provided</scope>
    </dependency>
    <dependency>
    <groupId>axis</groupId>
    <artifactId>axis</artifactId>
    <version>1.4</version>
    </dependency>

    (guessing at the versions here)

    1. Anonymous

      how  to get icodeon java version source ,thanks

      1. Sorry, anonymous comments should be turned off (are now). This page has the instructions on how to get the source (see the Installation section). If you have specific questions, please ask them on the sakai-dev list. You can subscribe to that list at http://collab.sakaiproject.org/mailman/listinfo/sakai-dev