Ce contenu n'est pas disponible dans la langue sélectionnée.

21.2. Patching a Container in a Fabric


Abstract

In a fabric patches are applied to profiles and the patched version of the profile is applied to the container. The management console is the recommended tool for patching containers in a fabric. The fabric shell also has the commands needed to apply a patch and roll it out to running containers.

Overview

The bundles loaded by a container in a fabric is controlled by the container's Fabric Agent. The agent inspects the profiles applied to the container to determine what bundles to load, and the version of each bundle, and then loads the specified version of each bundle for the container.
A patch typically includes a new version of one or more bundles, so to apply the patch to container in a fabric you need to update the profiles applied to it. This will cause the Fabric Agent to load the patched versions of the bundles.
The management console is the recommended tool for patching containers in a fabric. However, the command console's fabric shell also provides the commands needed to patch containers running in a fabric.

Procedure

Patching a container in a fabric involves:
  1. Getting a patch file.
    • Customer Support sends you a patch.
    • Customer Support sends you a link to download a patch.
    • You, or your organization, generate a patch file for an internally created application.
  2. Uploading one or more patch files to the fabric's Maven repository.
  3. Applying the patch(es) to a profile version.
    This creates a new profile version that points to the new versions of the patched bundles and repositories.
  4. Migrate one or two containers to the patched profile version to ensure that the patch does not introduce any new issues.
  5. After you are certain that the patch works, migrate the remaining containers in the fabric to the patched version.

Using the management console

The management console is the easiest and most verbose method of patching containers in a fabric. Its Patching tab uploads patches to a fabric's Maven repository and applies the patch to a specified profile version. You can then use the management console to roll the patch out to all of the containers in the fabric.
See Using the Management Console for more information.

Using the command console

The Red Hat JBoss Fuse command console can also be used to patch containers running in a fabric. To patch a fabric container:
  1. Upload the patch file to the fabric's Maven repository.
  2. Create a new profile version to which the patch will be applied.
  3. Modify all of the profiles in the new version which require the patch.
  4. Use the fabric:container-upgrade command to roll the patch out to the containers running in the fabric.

Applying patches P3 or later to JBoss Fuse A-MQ 6.0

If you need to apply patch P3 or later to JBoss Fuse A-MQ 6.0, you must first apply the P3 prerequisite patch before applying the patch. The P3 prerequisite patch is a fix to the fabric-agent bundle that resolves a patching bug. This is applicable only to fabric environments and the patch must be applied before applying any patch P3 or higher. Once a container has been patched with the P3 prerequisite patch, it does not need to be installed again before applying any new patches.
For example, to apply the P3 patch to a fresh installation of JBoss A-MQ 6.0, you would perform the following steps:
  1. Apply the P3 prerequisite patch, using the patching process described in this section.
  2. Apply the P3 patch, using the patching process described in this section.

Applying rollup patches to JBoss Fuse A-MQ 6.0

The P3 prerequisite patch must also be installed before installing a rollup patch to JBoss Fuse A-MQ 6.0. In other words, the rollup patches do not incorporate the P3 prerequisite patch.
Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2026 Red Hat
Retour au début