Inform and coordinate with EUS to get a manual VM snapshot of the target Fuse hosts before starting Fuse Roll-up patch.

Pay attention to existing Fabric versioning scheme on the target Fabric server.

1. unzip patch-management-package-6.3.0.redhat-329.zip into top level system directory.

Login into karaf console, apply the patch-management upgrade, create a new version.

2. fabric:version-create 1.3.1

Edit the default profile in the new version to replace the old patch management bundles:
3. profile-edit --pid io.fabric8.version/patch=1.2.0.redhat-630329 default 1.3.1

Upgrade the root container first
4. container-upgrade 1.3.1 root

5. stop the root container

6. Backup/remove the org.apache.karaf.exception-<version> jar from the lib/endorsed directory.

7. start root container

Upgrade each child containers
Child containers can be mix-bagged of old version and new version (Not recommend though)
8. Container-upgrade 1.3.1 uci-mq-broker, etc.

Create a new version (from the patch-management upgraded version above) for applying the roll-up patch.
9. fabric:version-create --parent 1.3.1 1.4

Then run the patch commands to install the roll-up on the new version:
Use 3 slashes on Linux OS.
10. patch:add file:///home/esbuser/patches/jboss-fuse-karaf-6.3.0.redhat-329.zip

Check patchID with the command
11. patch list

Install the patch to the fabric environment
12. patch:fabric-install --username fabricserver --password password --upload --version 1.4 jboss-fuse-karaf-6.3.0.redhat-329

Sync the git repo.
13. patch:fabric-synchronize

Now upgrade each containers (root container first) to the roll-up patched version.
upgrading the ensemble containers one at a time and waiting until
they are restarted and in the success state before proceeding to the next.
14. fabric:container-upgrade 1.4 root, etc.

If all goes well, the container should get to the state "requires full restart."
After restarting, the container should download and install remaining bundles and then finish provisioning.

Browser not supported