The Patching Tool applies Fix Packs (including Security Fix Packs and Service Packs) for versions prior to Liferay DXP 7.3 SP3. It also applies Hotfixes for any DXP version.
If you’re applying an Update (or Security Update) on Liferay DXP 7.3 SP3+, please see Updating Liferay.
The patching steps for DXP bundles and DXP application server installations are similar. Since DXP bundles include the preconfigured Patching Tool, you can apply patches right away. DXP application server installations, however, require installing and configuring the Patching Tool before patching.
Always back up your database and installation before patching.
If you’re running DXP in a Docker container, please follow the instructions at Patching DXP in Docker.
If you’re patching a DXP bundle, continue with the basic patching steps below. If you’re patching DXP on an application server, make additional preparations before following the patching steps.
Download the patch to your
patching-tool/patchesfolder—don’t unzip the patch.
Shut down your application server.
On Unix-style systems, you can usually replace files that are running, but the old ones reside in memory.
On Windows systems, files in use are locked and can’t be patched.
Install the patch by running the Patching Tool’s
installcommand from the
cd patching-tool ./patching-tool.sh install
The output looks like this:
There's no configuration available. Running auto-discovery in the parent folder. Directory is not set in command line, using ../ Auto discovery looks for portal segments. The selected directory is "/home/russell/liferay-bundles/cross-cluster-replication_7.2_LRDOCS-8715/liferay-dxp-220.127.116.11-sp3". Configuration has been written into the default.properties: patching.mode=binary war.path=../tomcat-9.0.33/webapps/ROOT/ global.lib.path=../tomcat-9.0.33/lib/ext/ liferay.home=../ One patch is ready to be installed. Applying dxp-10... Cleaning up: [1%..10%..20%..30%..40%..50%..60%..70%..80%..90%..100%] Installing patches: [1%..10%..20%..30%..40%..50%..60%..70%..80%..90%..100%] Syncing... The patches contain database index modification. Run the patching tool with the index-info parameter for more information. The installation was successful. One patch is installed on the system.
Verify that the patch installed by executing the
infocommand and checking the information on the currently installed patches:
The output lists the currently installed patches:
Loading product and patch information... Product information: * installation type: binary * build number: 7210 * service pack version: - available SP version: 3 - installable SP version: 3 * patching-tool version: 2.0.15 * time: 2021-01-21 18:02Z * host: russell-pc (8 cores) * plugins: no plugins detected Currently installed patches: dxp-10-7210 Available patches: dxp-8-7210, dxp-10-7210 Detailed patch list: [ -] dxp-8-7210 :: Currently not installed; Won't be installed: dxp-10 contains the fixes included in this one :: Built for LIFERAY [*I] dxp-10-7210 :: Installed; Will be installed. :: Built for LIFERAY
Clean up all DXP cache.
cd [Liferay Home] rm -rf osgi/state
rm -rf work/*
Delete the application server cache. Please consult the application server vendor’s documentation on where where to find the cache.
If a module’s changes are only internal, the changes are invisible to the OSGi framework, the module stays installed, and the module’s state persists. Clearing the OSGi bundle state information before the next DXP startup ensures that such modules reinstall with the appropriate state.
If the patch release notes mention micro or minor schema/data changes, use the Database Upgrade Tool to apply minor changes (required) and any micro changes you want.
If you’re updating from Liferay DXP 7.2 GA1 or Fix Pack 1 to DXP 7.2 SP1 / Fix Pack 2 (or above), you must update the data and database using the Database Upgrade Tool.
If you customized DXP’s
web.xmlfile, merge your customizations into the new
web.xmlfile that the Fix Pack includes. Fix Packs always overwrite the existing
If the patch has any index updates, configure DXP to update the indexes on startup.
infocommand to check for index updates.
cd patching-tool ./patching-tool.sh info
Only indexes that start with
IX_are updated. Make sure that your custom indexes do not use this naming convention.
If you are installing DXP 7.3 back onto an application server, ZIP the patched DXP application from its temporary location back into a
.warfile and copy the file into your application server. Refer to the DXP installation instructions for your application server.
Start the application server again.
Congratulations! Your DXP instance is patched and running.
If the patch doesn’t install or if you’re unable to resolve errors that occur, please open a Help Center ticket and provide the full Patching Tool
info output by running
./patching-tool.sh info > output.txt and attaching the
output.txt file to the ticket.
Preparing to Patch DXP on an Application Server¶
If you installed DXP on an application server, make these preparations:
If you’re patching DXP 7.3 and it is deployed as a
.warfile, unzip the
.warto a temporary location for patching.
Install the Patching Tool, if you have not yet installed it.
Configure the Patching Tool for your DXP installation by running the
cd patching-tool ./patching-tool.sh auto-discovery
If you’re patching DXP 7.3, set the Patching Tool’s
war.pathproperty (e.g., in
default.properties) to your unzipped DXP
Continue with the Patching Steps in the previous section.
Now you know how to patch a DXP Bundle and a DXP application server installation.