Hey rdas4,
you'll need to consider the mapping action of the entities as well. By default, when you migrateOut, the mappingAction is "NewOrExisting", meaning the entity will be created on the destination if it doesn't exist, and if it does exist, map to said entity, but don't update it.
there are a few ways to get that guy updated,
first, we can use the manageMappings command to target the cluster wide property, using something like the following,
./gmu.sh manageMappings -b Bundles/mybundle.xml -t CLUSTER_PROPERTY -a "NewOrUpdate"
//this will target all cluster wide properties in the bundle and modify the action to "NewOrUpdate" and they will be ready to overwrite the destination values upon import.
the other method that comes to mind is on the 'migrateOut' operation, we have an option to change the default action of all the entities,
--defaultAction <action> Default mapping action: [NewOrExisting,NewOrUpdate,Ignore]default=NewOrExisting
so something like the following
./gmu.sh migrateOut -z args/Gateway1.args --serviceName /blah --dest ./Bundles/blah.xml --defaultAction "NewOrUpdate"
(something like this )
all entities in the bundle will now be ready to overwrite upon the destination import.
hope this helps,
Doyle