SCORM 4 Cross Domain

SCORM 4 Cross Domain
SCORM 4 Cross Domain

SCORM 4 Cross Domain is for you if you want to distribute your content to other organizations (customers, clients, or vendors) who already have a Learning Management System that speaks SCORM, but you don’t want to give up control of your content.

Some possible reasons for needing SCORM 4 Cross Domain:

  • You have proprietary content source files that must stay on your content server and can not be released.
  • Your content updates often, daily or weekly, and it is a logistical nightmare to distribute new content packages after each change.
  • Your courseware uses server-side or proprietary language that would not run properly on another server environment.
    You just simply want to keep control of your content packages and not release them to your customer.

The basics of how it works

For this example, let’s call the two servers Client LMS and Content Server. The Content Server holds the SCORM course package and the Client LMS holds the learner information and student records in its database. When a course is taken for credit in the Content Server this data needs to get over to the Client LMS so that the students are given credit for their interactions in the course. Normally this request would be blocked by the browser because of JavaScript security rules. SCORM 4 Cross Domain solves this problem.

More on how it works

Place a “stub file” on the Client LMS. This “stub file” is a valid SCORM or package that can be loaded onto the Client LMS. This “stub file” is a zip file containing an imsmanifest.xml file (SCORM), which sets up the proper table of contents within the Client LMS. It also contains a SCO start file with a single hyperlink which links to a URL on the Content Server. That URL on the Content Server must be able to determine the start file for the course and launch that file so that the Client LMS can display it. This hyperlink URL will contain information about the course to be launched as well as information about the student and maybe the session. Once the Content Server receives the request to launch a course then it calls back to the Client LMS and tells it that the session has started then the “stub file” issues an Initialize command to the Content Server. This way the Content Server knows it has a connection and a course. Once the connection is made and content is initialized, between the Client LMS and the Content Server, the same connection can be used to send data about the student’s interactions with the course.

SCORM connected packages can interchange the following data:


Supports the full SCORM 1.2 and 2004 Run-Time API
Written in JavaScript so the processing load is on the client, not the server
Can run on any server. Just copy onto your web accessible server directory and you’re done!

Want a Demo?

If you would like a demonstration of the administration functionality or for more information