Upgrade Content Delivery
Upgrading Content Delivery involves a complete backup, a complete erase, an installation and a restore.
- Backing up a database using loaddb BACKUP
This procedure backs up a Content Delivery database. The backup you create can be restored to another system, even if that system has a different operating system than the computer on which you create the backup. TheBACKUPcommand outperforms other ways of restoring the database, especially if the database is large. - Backing up the configuration files
A number of files are not backed up by theloaddb BACKUPcommand. Still, you need to keep those through the upgrade, therefore you have to save and restore them just like the database itself. - Removing the previous Content Delivery installation
When the database and the critical files are backed up, you can remove everything related to the old version of Content Delivery: database, application and remaining files. - Installing Content Delivery new version
When all parts of the old version of Content Delivery are removed, you can proceed to a normal installation of Content Delivery with the new version following the same instructions as for a normal installation. - Restoring a database using loaddb RESTORE
This procedure restores your Content Delivery database. Backups can be restored to another system, even if the system that you restore the backup to has a different operating system than the computer on which the backup was created. TheRESTOREcommand outperforms other ways of restoring the database, especially if the database is large. - Creating graphs for publications
If Content Delivery is upgraded from a version older than 7.5, you need to useloaddbin order to generate a graph for every existing publication. - Restoring the configuration files
When the database has been restored after a Content Delivery upgrade, you need to restore the files that are not backed up with theloaddb BACKUPcommand. - Fixing Content Delivery database permissions after restore
After restoring the Content Delivery database, you need to grant access to the database, related to the new version of the base skin, with the command:loaddb FIX-PERMISSIONS. - Re-indexing Content for Searches
Content is automatically indexed for searching upon upload and when a publication is prepared. However, when you add new categories, change existing search categories, or change the lists of binary formats that are indexed, you must manually reindex for those changes to appear in a search. - Restoring your default skin
Restore your default skin by executing the following command:loaddb SKINS-RESTORE. There is no need to execute this command if you are restoring your database to a different machine but with the same version of Content Delivery, and you have made default skin modifications there. - Manually installing a license file
If you did not have a license file when you installed or upgraded Content Delivery, or if you have a new license file to install, follow this procedure.