Red Hat SummitRed Hat AMQ 6
As of February 2025, Red Hat is no longer supporting Red Hat AMQ 6. If you are using AMQ 6, please upgrade: Migrating to AMQ 7.Este conteúdo não está disponível no idioma selecionado.
Chapter 21. Applying a Patch
Abstract
Applying a patch is a two step process. The first step creates a new profile version. The second step rolls the patch out to the containers.
Overview
Once a patch file is uploaded to the Fabric Ensemble's Maven repository, it can be applied to the containers in the fabric. To make it so that you can roll out the patch to controlled set of containers, and to be able to roll the patch back, applying a patch is a two step process:
- Apply the patch to an existing profile version.This creates a new profile version based on the one being patched. This ensures that none of the running containers are updated with the patch automatically.
- Migrate one or more containers to the patched profile version.This deploys the patch to running containers. It is recommended that the initial roll out of a patch is limited to a few containers. Once the patch has been proven to work, you can then migrate the remaining containers to the patched profile version,
Important
The patched bundles in the Fabric Ensemble's Maven repository will be used in place of the bundles original bundles. The original bundles, however, will still be available for use.
Procedure
To apply a patch:
- Select the management console's Patching tab.
- Upload one or more patches.
- From the Version to patch drop-down list, select the version to which you want to apply the patch(es).This is the version that will be copied and modified to use the uploaded patch(es).
- Click .A new profile version will be created based on the selected profile version. The selected version will be copied and any of the profiles that use bundles in the patch(es) will be modified to use the bundle version from the patch instead of the original version.ImportantThe new profile version is not used by any of the running containers, so the changes have not been applied to any of the containers.
- Migrate one or more containers to the newly patched profile version.
