Show Table of Contents
Chapter 16. Applying Patches
Abstract
Red Hat JBoss A-MQ supports incremental patching. Red Hat will supply you with easy to install patches that only make targeted changes to a deployed broker.
16.1. Introduction to Patching
Patching enables you apply fixes to a broker without needing to reinstall an updated version of Red Hat JBoss A-MQ. It also allows you to back out the patch, if it causes problems with your deployed applications. Patches are ZIP files that contain the artifacts needed to update a targeted set of bundles in a container. The artifacts are typically one or more bundles. They can, however, include configuration files and feature descriptors.
In addition, since JBoss A-MQ 6.2.1, a full distribution can be used as a rollup patch. This enables you to upgrade all aspects of an existing JBoss A-MQ distribution—including installed features, bundles and configurations—while preserving custom configuration changes.
You get a patch file in one of the following ways:
- Customer Support sends you a patch.
- Customer Support sends you a link to download a patch.
- Download a patch directly from the Red Hat customer portal.
The process of applying a patch to a broker depends on how the broker is deployed:
- Standalone—the broker's command console's patch shell has commands for managing the patching process
- Fabric—patching a fabric requires applying the patch to a profile and then applying the profile to a broker.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.