These FAQs will help you determine when to publish Engage 360 interactions for Tin Can API (also known as Experience API or xAPI), how to publish, and where to host your published content.
Should I Publish for Tin Can API?
If your LMS supports Tin Can API and you plan to distribute only HTML5 and/or Flash content, you can absolutely publish for Tin Can API. If you plan to distribute content for the Articulate Mobile Player app, you can publish for Tin Can API, but you may need to host your content on a server that's separate from your LMS (see the next section for details).
You'll need to check with your LMS provider to see if Tin Can API support is available. If your LMS provider doesn't yet support it, we recommend urging them to do so. Our white paper on Tin Can API implementation provides helpful information for your LMS provider.
Where Should Tin Can API Content Be Hosted, in the LMS or an External Server?
If you're distributing only HTML5 and/or Flash content, the location of the published output won't matter. On the other hand, if you plan to distribute content for the Articulate Mobile Player app and your LMS hasn't yet enabled private content authorization for mobile apps, you'll need to host your published output on a server that's separate from your LMS. And if you're hosting content on a separate server, you'll need to modify the Launch URL when publishing. Here's how:
- In Engage, click Publish on the ribbon.
- Select the LMS option on the left edge of the publishing window.
- From the LMS drop-down list at the bottom of the window, select Tin Can API.
- Click the Reporting and Tracking button.
- In the Launch URL field, type the full URL to the interaction.html file where it'll be hosted on the external server.
- Click OK, and complete the publishing process.
- Zip the published output.
- Upload the zipped version of the published content to your LMS.
- And upload the unzipped version to your external server.
If your LMS provider has already implemented Tin Can API with private content authorization for mobile apps, simply publish for LMS, zip the published output, and upload it directly to your LMS.
If you'd like to encourage your LMS provider to support private content authorization, our white paper on Tin Can API implementation provides helpful information.
Can Tin Can API Content Be Viewed Offline in the Articulate Mobile Player?
No, an internet connection is required to view Tin Can API content in the Articulate Mobile Player app.
Why Am I Getting a "Cannot Access Content" Error When Launching Tin Can API Content in the Articulate Mobile Player?
If you're hosting Tin Can API content in your LMS (rather than an external server) but your LMS doesn't yet support private content authorization for mobile apps, you'll see a Cannot Access Content error message when attempting to launch the content in the Articulate Mobile Player app. Use either of these options to correct it:
Which Version of Tin Can API Does Engage 360 Use?
Engage 360 publishes content to Tin Can API version 1.0.