PENS for SCORM Engine Customers

If you’re already using SCORM Engine 2010 or later (get upgrade info here), then you already have PENS installed and running by default. Nifty!

Here’s what you’ll need in order to tap into PENS in SCORM Engine:

  • SCORM Engine 2010 or later
  • A software developer
  • Your PENS endpoints (where authoring tools can send PENS commands, see below)
  • A PENS conformant authoring tool that wants to publish directly to your LMS (if the authoring tool needs help, send them here.)
  • The desire to make your LMS easier to use
  • Our email, in case you have questions
PENS integration with SCORM engine

1. Receive initial PENS command

The authoring tool that will be publishing to your LMS will have their content on a staging server, ready for you to grab it. Just tell the authoring tool to send their HTTP commands to your PENS endpoint:

  • Typical .NET installation: [server name etc]/ScormEngineInterface/PENS.aspx
  • Typical Javascript installation: [server name etc]/ScormEngineInterface/PENS.jsp

2. Download content from staging server

When SCORM Engine receives the HTTP command to download content from the staging server, it does so, and delivers content directly into your LMS. Engine takes care of the conversations that need to happen between your LMS and the authoring tool. At it’s simplest execution, this is all that takes place, but you might want to customize/authenticate things. There are two ways to do that.

  1. Modifying your SCORMEngineSettings file (see settings below)
  2. Start overriding some of SCORM Engine’s default logic in your integration layer (see methods below)

The PENS receipt message can be an HTTP command, or an email (in the form of a “mailto:” link.) If you use email confirmation, then you’ll want to code in your email credentials (see below.)

3. Wrapping it up

Though PENS doesn’t specify what should be done with the content after download, practically this will mean processing or importing the content into your system. Any number of alert messages will be sent, (again, in the form of an HTTP command or a “mailto:” link) to let the authoring tool know what steps Engine has taken in processing the content, or any errors that have happened along the way.

SCORMEngineSettings.config example settings:

.NET example settings:

Java example settings:

Integration methods to explore in the Integration Layer of the Engine:

  • Authentication: IsAllowed, PensShouldAcceptCommand
  • Download: GetPensCourseName, PensPerformPostRetrieveActions
  • Import: PensImport, GetPensDuplicateAction
  • Cleanup: PensShouldDeletePackageAfterImport, PensPerformPostImportActions

That’s it

PENS implementation with SCORM Engine is really easy. There are a lot of customizations that you can make to your PENS implementation, and we’d be happy to discuss specifics with you. Just email us here.