Hi,

The beta docs [1] for our patching process aren't quite in sync with the actual process. There are two approaches for Fabric with the 6.1 release:

1. Using OSGI commands.

Profiles are created for you when you apply the patch and the order of the steps is a bit mixed up. Essentially, what needs to happen is you create a new version, apply the patch to that version and then upgrade the container:

1. Create a new version:

JBossFuse:karaf@root> fabric:version-create 1.1
Created version: 1.1 as copy of: 1.0

2.  Apply the patch to the new version:

patch-apply --version 1.1 file:///Users/sjavurek/Fuse/patches/GradleTester/target/patches/activemq.zip

3. upgrade the container

JBossFuse:karaf@root> container-upgrade 1.1 root
Upgraded container root from version 1.0 to 1.1
JBossFuse:karaf@root> container-list 
[id]                           [version] [connected] [profiles]                                         [provision status]
root*                          1.1       true        fabric, fabric-ensemble-0000-1, jboss-fuse-full    success

Customers can see the new patch profile created, i.e:

BossFuse:karaf@root> profile-list |grep patch
default                                  0              patch-activemq-patch
patch-activemq-patch      

The parent of this profile is default so it will be picked up. One can also check specific jars included in the patch, i.e:

JBossFuse:karaf@root> list |grep -i activemq
[ 131] [Active     ] [Created     ] [       ] [   50] activemq-osgi (5.9.0.redhat-61037X)
[ 139] [Active     ] [Created     ] [       ] [   50] activemq-karaf (5.9.0.redhat-61037X)
[ 207] [Active     ] [            ] [       ] [   60] activemq-camel (5.9.0.redhat-61037X)

Where 61037X is my patched version in this example

2. Patching from the FMC

A. Customers need to take care that when the upload a new patch that the version they want to patch is selected in the drop down box.
B. The "patch tab" no longer exists but instead is a tiny icon. They need to click this to upload the patch.
C. Add details about the patch location. After uploading patch you are returned to the previous screen.
D. To migrate to the container there are two choices:
1. From the manage tab
2. From the containers tab

I've attached screenshots of this proces:

FMCPatchDoc1.tiff - highlights step A & B
FMCPatchDoc2.tiff - highlights step C and also highlights which version you are applying the patch to
FMCPatchDoc3.tiff - highlights step D1
FMCPatchDoc4.tiff - highlights step D2
FMCPatchDoc5.tiff - finished migration

[1] https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html/Configuring_and_Running_Red_Hat_JBoss_Fuse/files/ESBRuntimePatchFabric.html