Refusing Document Type Updates Across a Gateway
By default, changes made to shared document types on one side of a gateway are propagated to a Broker cluster on the other side of the gateway. However, you can configure a cluster to refuse updates made on the other side of a gateway. This setting provides the following security measures:
Lockdown of a local cluster. Unauthorized changes made in a neighboring cluster are not carried over to the local cluster.
Protection against accidental changes made to shared document types in the neighboring cluster.
Configuring a cluster to refuse updates is done at the local end of a gateway. If you want the Broker clusters on both sides of a gateway to refuse updates, you must configure the setting from both sides.