For the general upgrade process, see the Upgrading the Nuxeo Platform.
This chapter highlights some major information about upgrade from Nuxeo Platform 5.6 to Nuxeo Platform 5.8. Most of it is useful information you need to have to fully understand what has changed in this release. If you need an exhaustive list, see the 5.6 -> 5.8 upgrade notes.
You may also want to have a look at the 5.8 release notes.
If you have followed the Fast Track releases since Nuxeo Platform 5.6, you can refer to the Upgrade from 5.7.x to 5.8 section.
Installation & Configuration
Follow the Installation instruction.
Java 7 Required
Since version 5.7.1, the Nuxeo Platform enforces the use of Java 7 because it's faster (better GC among other things) and because Java 6 is getting unsupported, see NXP-11226.
Upgrade to Tomcat 7
Since version 5.7.2, the Nuxeo Platform was upgraded to Tomcat 7. Please follow the upgrade notes of NXP-10071.
Data migration
Relations
Since Nuxeo Platform 5.7.1 all the relations (including comments and publication relations, but excluding annotations) are stored by default in the VCS database. If you upgrade from a previous configuration (before 5.6) where you created relations, comments or publications, then these relation objects were stored using Jena. To keep using this configuration, please follow the upgrade notes of NXP-10350.
Derby Storage Moved to H2
For test and development instances that use the default configuration, audit logs storage has been moved from Derby to H2. If you plan on upgrading your test data on H2 from 5.6 to 5.8, note that audit logs will be lost unless you migrate data from Derby to H2 or change database configuration to use the old Derby database for audit logs.
This also applies to vocabularies, annotations, activities, local configuration and sequences.
SQL Server
The column type for ID columns has been changed from VARCHAR to NVARCHAR, for efficiency reasons. All new tables will be created with NVARCHAR, but existing tables must be migrated. Please follow the upgrade notes of NXP-10862.
Oracle
The default path optimization has changed since NXP-10210: therefore you need to drop the ANCESTORS table. The data will be recomputed. If a timeout occurs at startup, you'll have to recompute the data by hand with the procedure
BEGIN nx_init_ancestors; END;
/
Code Migration
EL expressions in Action Filters
From Nuxeo Platform 5.7.3, EL expressions in action filters are using a more generic context to allow better filtering expressions. Please follow the upgrade notes of NXP-10566.
Document Context Used in Action Filters
From Nuxeo Platform 5.8, the document used to evaluate action filters using the category CREATE_DOCUMENT_FORM is the changeableDocument (document being created) instead of the currentDocument (parent of the document being created), see NXP-12605.
Permission checks will now fail because there are no security checks on the document until it is created in the repository - see details at NXP-21465.
As a workaround, you can define EL expressions, such as #{documentManager.hasPermission(currentDocument.ref, 'Perm1')}.
Query Models and Result Provider Farms Removal
Content views and page providers have been in place since 5.4.2 to replace old query models and result provider farms, so old classes have been removed for 5.8.
Please follow detailed upgrade notes for these features.
Configuration Migration
Actions on Content View Actions of Ordered Folders
Since NXP-11845, the default content view presenting ordering actions only presents actions with category ORDERABLE_CURRENT_SELECTION_LIST (labelled "Orderable Document List Toolbar" in Studio). It previously presented also actions available to non-orderable content views, CURRENT_SELECTION_LIST (labelled "Document List Toolbar" in Studio).
When upgrading to 5.7.2 or higher, actions using this category will need to use the ORDERABLE_CURRENT_SELECTION_LIST to be available on the default content view orderable_document_content.
Upgrade from 5.7.x to 5.8
Previous Fast Track upgrades notes: