Fuse MQ Enterprise - Managing and Monitoring a Broker

Patching a Standalone Broker

Overview

Patching a standalone broker directs the broker to load the patch versions of artifacts instead of the non-patch versions. The patch shell provides commands to patches to the broker's environment, see which bundles are effected by applying the patch, apply the patch to the container, and back the patch out if needed.

To make sure that the a patch can be rolled back Fuse MQ Enterprise applies the patch in a non-destructive manner. The patching process does not overwrite the artifacts included in the original installation. The patched artifacts are placed in the broker's system folder. When the patch is applied, the broker's configuration is changed so that it points to the patched artifacts instead of the artifacts from the original installation. This makes it easy for the system to be restored to its original state or to selectively back out patches.

	Important
	Patches do not persist across installations. If you delete and reinstall a Fuse MQ Enterprise instance you will need to download the patches and reapply them.

Applying a patch

To apply a patch to a standalone broker:

Add the patch to the broker's environment using the patch:add command.
Example 49 shows the command for adding the patch contained in the patch file patch.zip from the local file system.
Example 49. Adding a Patch to a Broker's Environment
```
FuseMQ> patch:add file://patch.zip
```
This command copies the specified patch file to the broker's system folder and unpacks it.
Simulate installing the patch using the patch:simulate command.
This will generate a log of the changes that will be made to the broker when the patch is installed, but will not make any actual changes to the broker.
Tip
The patch:list command will display a list of all patches added to the broker's system folder.
Review the simulation log to understand the changes that will be made to the broker.
Apply the patch to the broker using the patch:install command.
Tip
The patch:list command will display a list of all patches added to the broker's system folder.

The broker will need to restart to apply the patch. If you are using a remote console, you will lose the connection to the broker. If you are using the broker's local console, it will automatically reconnect when the broker restarts.

Rolling back a patch

Occasionally a patch will not work or introduce new issues to a broker. In these cases you can easily back the patch out of the system and restore it pre-patch behavior using the patch:rollback command. As shown in Example 50, the command takes the name of patch to be backed out.

Example 50. Rolling Back a Patch

FuseMQ> patch:rollback patch1

	Tip
	The patch:list command will display a list of all patches added to the broker's `system` folder.

The broker will need to restart to rollback the patch. If you are using a remote console, you will lose the connection to the broker. If you are using the broker's local console, it will automatically reconnect when the broker restarts.

Comments powered by Disqus