A Hotfix is a fix or collection of fixes delivered between Updates (or between Fix Packs for versions before DXP 7.3 SP3) to address a customer’s confirmed critical DXP issues. You can request at Hotfix via a Help Center ticket. After receiving a Hotfix, you can install it using the Patching Tool.
Always back up your database and installation before applying a Hotfix.
If you’re running DXP in a Docker container, please apply your Hotfix by following the instructions at Patching DXP in Docker.
Here’s how to request a Hotfix:
- Go to the Help Center
- Submit a ticket.
The Liferay Support Team works with you to determine if the issue is with the product, and provides a fix for any unintended product behavior.
The Patching Tool applies Hotfixes. Here’s how to configure it:
If you deployed DXP as a
.warfile on your application server, unzip the
.warto a temporary location for applying the Hotfix.
patching-tool.shPatching Tool script in your Liferay Home or install the Patching Tool if the DXP installation doesn’t have it.
- DXP Tomcat Bundle:
- DXP app server installation: Install the Patching Tool on the server host.
- DXP Tomcat Bundle:
Configure the Patching Tool for the DXP installation.
DXP Tomcat Bundle: Configure the tool automatically be running the
DXP app server installation: Configure the Patching Tool manually, including setting the Patching Tool’s
war.pathproperty (e.g., in
default.properties) to your unzipped DXP
Download the patch from your Help Center ticket 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
Verify that the patch installed by executing the
infocommand and checking the information on the currently installed patches:
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.note
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 you are installing DXP 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! You applied a Hotfix to your DXP installation.