You can run an aNewSpring course in an external system if it support SCORM and if you have the possibility to set up a proxy server (see below).

When using SCORM, it is not possible to send notifications, because email addresses of the users are not registered.

If the external system also supports LTI (or AICC), we would recommend this. A proxy server is not required for LTI and AICC.


Roles

For the steps in this article, you need the administrator role.


Steps

1) Create a course
First you need to create a course. Go to the Templates tab and click +Course. For more information: 'Creating a course'.

2) Export to SCORM
After creating the course, go to the settings. At the bottom of the page, there are a few export options.

Before you export, make sure the right subenvironment is selected, the proxy prefix is filled in and you can fill in an LMS ID (optional).

Proxy prefix
The proxy prefix needs to be filled in in the course settings. This should be the domain that the LMS runs on.

LMS ID
It is wise to use an LMS ID and it's important to do so if you link with multiple external systems. Users are created with an external ID that is supposed to be unique. If you link with multiple systems, it can happen that the same external ID is used for multiple users. This would cause a user one external system to log in as a user from another external system.
By filling in an LMS ID (this can be a short code that identifies the external system), this will be added to the ID's that come from the external system to make sure that it will be unique.

Next, click Export SCORM.

3) SCORM importeren
Import the ZIP file in the external system, make sure that a proxy server has been set up (see below) and follow any extra steps that are necessary in that system.


Proxy server

When you export a SCORM package from aNewSpring, this basically just contains a link that refers to the course. The course will actually run in aNewSpring.

When using SCORM, the communication between the LMS (the external system) and the content (aNewSpring) happens via JavaScript in the browser.

Without a proxy server, the browser will block the connection, because both systems have different domains. (Cross Domain Scripting)

The browser does not accept that data comes from different domains:

It's up to the manager of the domain name to set up a revere proxy, so the LMS and aNewSpring both connect via a different sub domain of the same domain. For example lms.example.com for the LMS and ans.example.com for the content (aNewSpring).

If the LMS already runs on that domain, it is sufficient to only serve aNewSpring through the proxy server.

It is also important that the document.domain setting in the LMS points to the main domain. This will also be set for aNewSpring.

Using these setups, the browser will accept the communication and you can successfully run aNewSpring via SCORM: