Upgrading Opencast from 6.x to 7.x
This guide describes how to upgrade Opencast 6.x to 7.x. In case you need information about how to upgrade older versions of Opencast, please refer to the old release notes.
How to Upgrade
- Stop your current Opencast instance
- Replace Opencast 6.x with 7.x
- Back-up Opencast files and database (optional)
- Upgrade the database
- Upgrade the ActiveMQ configuration
- Review the configuration changes and adjust your configuration accordingly
- Migrate the scheduled events
As part of performance optimizations, some tables were modified. This requires a database schema update. Also, one table is no longer needed and can be dropped. As with all database migrations, we strongly recommend to create a database backup before attempting the upgrade.
You can find the database upgrade script in
docs/upgrade/6_to_7/. This script is suitable for both, MariaDB and
So far, this is not required
Removal of Deprecated Access Control Ruleset
Opencast 7 finally removes the long-since deprecated
security/xacml flavor for access control lists. This had not been
used since before Opencast 1.2 (we could not track down its exact deprecation date due to its age). Additionally, all
rule-sets which had been modified since had also been automnatically been updated to
serves as replacement for the old flavor.
In case Opencast still encounters such a rule set, it will now be ignored and access will be denied by default. A simple update of the permissions would fix this if that is required.
Due to the extreme unlikeliness of anyone encountering this problem, there is no automatic migration. In case you run a system migrated from a pre-1.2 Matterhorn, you can make sure that there are no old rule-sets left using the following SQL queries:
-- Check OAI-PMH publications: select * from oc_oaipmh_elements where flavor = 'security/xacml'; -- Check engage publications: select * from oc_search where mediapackage_xml like '%"security/xacml"%'; -- Check asset manager: select * from oc_assets_snapshot where mediapackage_xml like '%"security/xacml"%';
etc/org.opencastproject.scheduler.impl.SchedulerServiceImpl.cfgno longer needs the
etc/org.opencastproject.scheduler.impl.SchedulerServiceImpl.cfghas a new option
maintenancewhich temporarily disables the scheduler if set to
The way the Scheduler stores its data was changed in Opencast 7 to improve performance when checking for conflicts.
The necessary database schema changes are part of the upgrade script in
To actually migrate the data, set the
maintenance configuration option of
true and start opencast. The migration will start
automatically. Wait until the migration is complete. Once complete, the opencast log will contain a line saying
Finished migrating scheduled events. Check if there were any errors during the migration. If not, stop opencast and
maintenance back to
false to put the scheduler back into its normal mode of operation.
You should avoid running Opencast 7 without migrating the scheduled events first. Otherwise, your capture agents may fetch an empty calendar.