The upgrade process to Content Controller 2.0 is a fairly straight forward process, but there are a few moving parts that you should be aware of.
Content Controller 2.0 handles account and content licenses differently from Content Controller 1.2. During the upgrade process, your existing licenses and usage will automatically be migrated to the new license format.
When you log in to Content Controller after the upgrade, in the Accounts section, you will see a new tab labeled Licenses. Here, you will see all of the licenses created during the migration.
For more information about the new licensing system, see:
Your account manager will be in touch to schedule a time for the upgrade. Please note that there will be a period of downtime while your upgrade is completed. If you are on managed hosted, we'll handle all of the configuration for you, so you can stop reading here, unless you don't want to.
If you're hosting Content Controller yourself, we'll schedule a call to help walk you through the upgrade process. Some important things to be aware of:
- There will need to be some downtime for this upgrade - especially if you have a large number of registrations. You must stop traffic from flowing to the servers. We recommend redirecting traffic to a static page that says maintenance is in progress, or something similar. If you have questions about the best way to handle this, feel free to send us a message.
- If you want to use License Alert Emails or Password Resets, then you will need to have an SMTP email service that can be used by Content Controller. We've had good luck with SendGrid, but you can also use AWS SES or any other solution that works for you.
- We recommend (as always) to make a backup before deploying this upgrade. It is not possible to roll back to CC 1.2 from 2.0 without a DB backup.
Here are a few Ansible configuration changes that you may need to make for this release:
- To add email support, add the following config to your
# Settings to enable Content Controller to send emails (such as license alert emails) enable_emails: true # Allow Content Controller to send emails cc_smtp_host: localhost # Defaults to localhost (optional) cc_smtp_port: 25 # Defaults to 25 (optional) cc_smtp_username: user # (optional) cc_smtp_password: 'password' # (optional) cc_smtp_transport: TLS # One of ['SSL', 'TLS', 'PLAIN'] - Defaults to 'PLAIN' (optional) cc_smtp_from_name: 'Content Controller' # Default from name for emails - Defaults to 'Content Controller' (optional) cc_smtp_from_email: 'firstname.lastname@example.org' # Default from email address - Defaults to 'email@example.com' (optional)
- If your
host_varsfile contains a setting for
engine_use_modern_player, please remove it, or set it to
We highly recommend using Modern Player with Content Controller 2.0, due to the improved user experience on mobile devices, and the accessibility improvements for those pursuing 508 compliance.
- Please make sure your
host_varsfile does not contain
- You will need to pass in an extra flag to run the SCORM Engine DB schema upgrades with this deployment. Add this to your ansible-playbook command for this release only:
If you have any questions, please send a message to firstname.lastname@example.org.