Fuse Management Console makes applying patches to your containers easy and risk-free. You upload patches to the fabric's central Maven repository, create a new profile version, and then migrate containers to the new version. If the patch causes problems, you can always roll back the containers to the non-patched version.
Patches are ZIP files that contain the artifacts needed to update a targeted set of
bundles in a container. The patch file includes a .patch file that
lists the contained artifacts. The artifacts are typically one or more bundles. They
can, however, include configuration files and feature descriptors.
The patching process is straight forward:
You get a patch file.
Customer Support sends you a patch.
Customer Support sends you a link to download a patch.
You use the Fuse Management Console's Patching tab to upload one or more ZIP files.
You apply the patches to a profile version.
This creates a new profile version that points to the new versions of the patched bundles and repositories.
You migrate one or two containers to the patched profile version to ensure that the patch does not introduce any new issues.
After you are certain that the patch works, migrate the remaining containers in the fabric to the patched version.
 |  | |
 |
