Getting Started with .NET Edition

Creating Your SCORM Engine IIS Web Application

In the Internet Information Services app in Windows, you’ll want to create a new virtual directory for ScormEngineInterface which we commonly name simply "ScormEngineInterface".

Letting Your DBMS (e.g., SQL Server) Know about SCORM Engine

In order to run SCORM Engine, we have to execute some data definition language (DDL) statements in SQL to make sure that the tables our application needs are in your database. To do this, launch Microsoft SQL Server Management Studio (MSSMS). In the SQLSERVER directory, open the files 1-2013.2_SQLSERVER_SCORMENGINE.sql and 2-2013.2_SQLSERVER_VANILLAINTEGRATION.sql. If you already know which database your SCORM Engine tables and data will live, select it. Then execute the two files in sequence.

If you’re using one of the other DBMSes supported by SCORM Engine (MySQL, Oracle, or PostgreSQL), use the relevant tool and execute the same SQL in the corresponding directory for your DBMS.

Teaching IIS to Speak SCORM Engine

Even though you’ve already set up your SCORM Engine IIS web application, you still need to update the configuration that will be used by IIS so that it can play nicely with SCORM Engine.

At a minimum, you’ll need to update the following values in SCORMEngineSettings.config to reflect your local environment.

Upload/Import

• WebPathToContentRoot: a URL that points to the top-level directory where your content will live after it’s been uploaded and unzipped

• FilePathToContentRoot: an absolute filepath to the same directory on your filesystem

• FilePathToUploadedZippedPackage: an absolute filepath to the directory on your filesystem where your content will get uploaded before being unzipped

Database Connectivity

• DataPersistenceEngine: the DBMS you’re using (e.g., "sqlserver")

• DatabaseConnectionString: the connection string required by that DBMS to create a valid connection

Console

• ConsolePassword: console uses this value for basic authentication. After the first authentication, subsequent authorization is governed by a cookie.

Testing Your SCORM Engine Installation

Once you’ve gotten this far, you should be able to navigate to the SCORM Engine console directly in your ScormEngineInterface. E.g., something like this:

[yoursite]/ScormEngineInterface/tools/console/

Provided you’ve got your database connection configured correctly, you should be prompted to log in. After you’ve used your ConsolePassword to log in, you should see the dashboard of your console. If both the database and filesystem tests are passing, you’re ready to try importing content!

Try importing a Tin Can package. If the import works, return to the console dashboard and try launching it in preview mode. If preview mode works, try launching it with an actual registration. If that works, return to the console dashboard and see if you see corresponding statements in your Statement Viewer. If you do, then you’re ready to be driven by SCORM Engine! Now it’s time to work on your integration...