Installing Fix Packs and Hotfixes on Liferay DXP

To install Fix Packs and hotfixes on Liferay DXP, customers must first download the latest Patching Tool. For more information on how to configure the Patching Tool, see: Using the Patching Tool.

Notes: 

Resolution

Important: Be sure to backup your Liferay DXP installation and database regularly, especially before patching.

  1. Stop the application server first.
  2. Download the patch file(s) to the {PATCHING_TOOL_HOME}/patches folder:
    • If you are installing a Fix Pack, download the Fix Pack to the folder. (Do not unzip the file)
    • If you are installing a hotfix, download the hotfix along with its related Fix Pack to the folder. (Do not unzip the files)
  3. Execute the command: patching-tool info (Windows) or ./patching-tool.sh info (Unix/Linux) in order to confirm the patch is available to be installed.
    • If the patching tool output indicates that the patch is Currently not installed; Won't be installed fulfill the required dependencies prior to completing the next steps.
  4. Execute the command: patching-tool install (Windows) or ./patching-tool.sh install (Unix/Linux).
    • It is not necessary to revert prior to installing a new patch.  The patching tool will revert the previously installed Fix Packs before installing any new patches.
  5. Confirm the patch was installed by executing patching-tool info (Windows) or ./patching-tool.sh info (Unix/Linux). You should see an I next to the installed patch or patches.
  6. Clean up the cache folders within DXP's {$LIFERAY_HOME}:
    1. Delete the $LIFERAY_HOME/osgi/state folder.
    2. Empty the $LIFERAY_HOME/Work folder
    3. Empty the $LIFERAY_HOME/tomcat-version/temp folder
    4. Empty the $LIFERAY_HOME/tomcat-version/work folder
  7. Start the application server again.

If the hotfix is not installed, or if you receive an error that is not covered in the documentation below, please open a Help Center ticket and provide the full patching-tool output.

Note: If there are any issues with the installed fixes, verify that there are no remaining files within the application server cache from the previous patch installation of a Fix Pack or hotfix. Consult the platform vendor's documentation on where to find the cache.

Do not delete these two files!

During the installation, patching-backup-deps.zip and patching-backup.zip files will be created and stored in the /ROOT/WEB-INF folder.

The patching-backup.zip file is necessary for installing future patches because Patching Tool reverts the previously installed Fix Packs before installing a new one. In order to revert the installed Fix Pack, the Patching Tool examines the contents of the patching-backup.zip in order to determine what changes have been made that it needs to revert. 

Note: The web.xml file inside the /WEB-INF folder will always be overwritten by the one inside the patch. Any custom configurations made by system administrators will be lost. Administrators should remember to add back whatever custom configurations before restarting the application server.

While removing the patching-backup.zip file does not affect the Patching Tool's report of what is installed in the bundle, we do not recommend removing the file from the ROOT/WEB-INF because doing so will cause future installations to fail.

If there are any other hooks and plugins already installed, there is no need to remove them first. The Patching Tool updates the Liferay product's core infrastructure first. If there are any Liferay plugins installed, there is a separate command to update them. See the article: Updating Plugins After Applying a Patch.

Note: Patching a Cluster requires additional considerations


Additional Information

Updating the Patching Tool: When a patch you’re trying to install requires a Patching Tool update, the Patching Tool will tell you. To update the Patching Tool, download the latest version from the Download page. Overwrite the existing Patching Tool by unzipping the new one to the patching-tool folder’s parent folder.

Database Indexes: If there are new database indexes created by the patch, the Patching Tool tells you to update them. To get the list, run this command:

patching-tool index-info

Since there’s no database connection at patching time, the indexes must be created at portal startup. If the server has permissions to modify the database indexes, instruct Liferay DXP to create the indexes automatically at startup by adding this setting to your portal-ext.properties file:

database.indexes.update.on.startup=true

Otherwise, you must create the indexes manually. Check the patching-tool index-info command output for more details.

Handling Hotfixes and Patches: Hotfixes are on-demand fixes provided directly to specific customers, and Fix Packs are larger bundles of hotfixes provided to all customers at regular intervals. If you already have a hotfix installed and the Fix Pack that contains that hotfix is released, the Patching Tool can manage this for you. Fix packs always supersede hotfixes; so when you install your Fix Pack, the redundant hotfix you already have is uninstalled and the Fix Pack version is installed in its place.

Since Fix Packs are cumulative, the latest Fix Pack contains all of the updates from the previous Fix Packs for the same Liferay version. You only need to install the latest one, and in most cases there is no need to manually uninstall the previous version.

Fix Pack Dependencies:  Most hotfixes depend on a certain Fix Pack. If you attempt to install a hotfix that depends on a certain Fix Pack, the Patching Tool notifies you. Go to the Downloads page and obtain the necessary Fix Pack. Once all the necessary patches  are available in the patches folder (your hotfix and required Fix Pack), the Patching Tool installs them.

See also:

Was this article helpful?
14 out of 17 found this helpful