org.jboss.hal.resources.previews.patching.patching.html Maven / Gradle / Ivy

Go to download
The method of applying a patch to ${build.shortName} depends on your installation method. If you installed ${build.shortName} using the ZIP or installer methods, you must use the ZIP-based patch management system. If you used RPMs to install ${build.shortName} on Red Hat Enterprise Linux, you must use RPM patches.
Important.

Before applying or rolling back a patch, you should back up your ${build.shortName} server, including all deployments and configuration files.

Cumulative patches for a ZIP or Installer installation of ${build.shortName} are available to download from the Red Hat Customer Portal.

For multiple ${build.shortName} hosts in a managed domain environment, individual hosts can be patched from your ${build.shortName} domain controller.

In addition to applying a patch, you can also roll back the application of a patch.

Important Notes on ZIP/Installer Installation Patching


    If you apply a patch that updates a module, the new patched JARs that are used at runtime are stored in ${build.installDir}/modules/system/layers/base/.overlays/PATCH_ID/MODULE. The original unpatched files are left in ${build.installDir}/modules/system/layers/base/MODULE, but these JARs are not used at runtime.
    In order to significantly decrease the size of cumulative patch releases for ${build.shortName}, you now cannot perform a partial roll back of a cumulative patch. For a patch that has been applied, you will only be able to roll back the whole patch.
    For example, if you apply CP03 to ${build.shortName}, you will not be able to roll back to CP01 or CP02. If you would like the ability to roll back to each cumulative patch release, each cumulative patch must be applied separately in the order they were released.