This wiki does not contain official documentation and is currently deprecated and read only. Please try reading the documentation on the Liferay Developer Network, the new site dedicated to Liferay documentation. DISCOVER Build your web site, collaborate with your colleagues, manage your content, and more. DEVELOP Build applications that run inside Liferay, extend the features provided out of the box with Liferay's APIs. DISTRIBUTE Let the world know about your app by publishing it in Liferay's marketplace. PARTICIPATE Become a part of Liferay's community, meet other Liferay users, and get involved in the open source project. Upgrade Instructions from 4.3 to 4.4
Prerequisite #
In order to upgrade to 4.4.X, you must start at 4.3.0 or above. If you are using version 4.2.2 or before, please see Upgrade Instructions from 4.2 to 4.3.
Basic Installation Outline #
- Undeploy the old version of Liferay, and then shut down your application server. For Tomcat, you'd delete the ROOT folder from <Tomcat Home>/webapps.
- Copy the new versions of the dependency .jars to a location on your server's classpath, overwriting the ones you already have for the old version of Liferay. For Tomcat, these are stored in <Tomcat Home>/common/lib/ext.
- Deploy the new Liferay .war file. This is different by application server. For Tomcat, you'd create a ROOT folder in <Tomcat Home>/webapps and unzip the .war file there.
- Start (or restart) your application server. Liferay should come up.
Service Builder #
Those using Service Builder to build their custom service should:
- Run ServiceBuilder for each custom service
- Edit their custom {Model}LocalServiceImpl classes and make them extend from {Model}LocalServiceBaseImpl.
- Run ServiceBuilder again for each of the custom services after the previous change
Changes required for developers #
If you are upgrading your extension environment, many of the DTD references in the various "-ext.xml" files have changed (liferay-portlet-ext.xml in particular). Be sure to compare your "<!DOCTYPE" references with the "main" file to insure they reference the same DTD
Example: Liferay 4.3.x: <!DOCTYPE liferay-portlet-app PUBLIC "-LiferayDTD Portlet Application 4.3.0EN" "http://www.liferay.com/dtd/liferay-portlet-app_4_3_0.dtd">
Liferay 4.4.x <!DOCTYPE liferay-portlet-app PUBLIC "-LiferayDTD Portlet Application 4.4.0EN" "http://www.liferay.com/dtd/liferay-portlet-app_4_4_0.dtd">
Upgrade Troubleshooting #
4.3.3 to 4.4.2 Screenshots #
