
Upgrade Instructions from 5.2 to 6.0
Alternative Languages: 日本語
This upgrade is recommended to anyone running Liferay Portal 5.2.3SE and wants to benefit from the New Features in Liferay Portal v6.0
Always use the latest version of 6.0 available as it will have fixed all the potential upgrade issues that may have been found. You should at least use v6.0.3 (there is no need to update to 6.0.1 or 6.0.2 first!)
Prerequisite #
It's recommended to upgrade first at least to 5.2.3SE if you are running any previous version.
Basic Upgrade #
If you're using a Liferay Bundle with MySQL or another external database attached: all you need to do is to back up your old bundle, saving the entire thing somewhere in case you need the configuration files, then download the new bundle and configure it for MySQL or whatever database you're using. Liferay 6.0 will auto-detect old versions of the database and upgrade automatically on start. Since all your data is in the database, your users and data will be preserved. Themes, additional plugins, and add-ons will need to be reinstalled however -- it would be wise to make a list of themes and plugins that you need, and to reinstall them after your upgrade.
Themes will need to be upgraded. You can learn to upgrade 5.2.x themes to 6.0.x via Upgrade 5.2.x Themes to 6.0.x
Additional Resources #
The official resource for topics including upgrading is the Portal Administrator's Guide. The book is available for print as well as a free PDF download.
How to keep the old values #
The default values of some properties have been changed. In order to keep the previous values, you have to run Liferay with the following system property:
java ... -Dexternal-properties=portal-legacy-5.2.properties
Application servers differ on how to add these parameters.
In Tomcat: modify setenv.sh/setenv.bat and append that option to the environment variable JAVA_OPTS (other documentations suggest catalina.sh/catalina.bat or catalina.conf, depending on the exact version you are using. setenv.sh or setenv.bat is not delivered with tomcat but - if existing - it will be embedded in the startup process, so it's a nice way to separate your own settings from tomcats default shell scripts).
Here are the complete contents of that file (portal-legacy-5.2.properties) for reference:
users.image.max.height=0 users.image.max.width=0 locale.prepend.friendly.url.style=0 auth.token.check.enabled=false permissions.user.check.algorithm=5 permissions.view.dynamic.inheritance=false image.hook.impl=com.liferay.portal.image.DatabaseHook cdn.host.http=${cdn.host} cdn.host.https=${cdn.host} virtual.hosts.default.community.name= breadcrumb.show.guest.group=false breadcrumb.show.parent.groups=false wiki.page.titles.regexp=([^/\\\\\\[\\]%&?@]+) wiki.page.titles.remove.regexp=([/\\\\\\[\\]%&?@]+)
Configure Database and Mail #
The configuration of the database parameters and those for mail integration are handled through the portal.properties to unify the configuration through all application servers.
It's still possible to use application server specific datasources and pools if desired by using certain configuration properties, that is, if you've been using them even with the 5.2.x releases.
Check Database Configuration for further details on how to adapt your existing configuration.