Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Upgrade Liferay From 7.4 to Quarterly Release

Written By

Laura Li

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • Please provide details on how we can upgrade from 7.4 Update 20 to Quarterly Release 2023.Q3.2.

Environment

  • Liferay 7.4 Update 20, Liferay 2023.Q3.2

Resolution

  1. Replace the content in {JBoss_Home}/standalone/deployments/ROOT.war with content of liferay-dxp-2023.q3.2-1698775649.war. (For Tomcat, replace the content in ROOT folder with content of liferay-dxp-2023.q3.2-1698775649.war).
  2. Replace the content in {Liferay_Home}/osgi with content of liferay-dxp-osgi-2023.q3.2-1698775649.zip
  3. If the environment permits accessing internet, the new elasticsearch-sidecar can be downloaded automatically when server starts up; otherwise, we can extract elasticsearch-sidecar from 2023.Q3.2 Tomcat bundle and replace the content in {Liferay_Home}/elasticsearch-sidecar folder.
  4. Go to {Liferay_Home}/tools/portal-tools-db-upgrade-client and run "./db_upgrade.sh". (If tools folder does not exist, extract it from 2023.Q3.2 Tomcat bundle.)
  5. Follow the steps in the pop-up screen to fill in correct information and wait for upgrade process to complete. 

Note:

  1. If the upgrade fails, it connects to Gogo shell automatically. We can run "upgrade:check" to see which process fails. 
  2. Then run "upgrade:execute {Service_Name}" to upgrade this service separately. 
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?