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 territory on the other side of the gateway. However, you can configure a territory to refuse updates made on the other side of a gateway. This setting provides the following security measures:
Lock down of a local territory. Unauthorized changes made in a neighboring territory are not carried over to the local territory.
Protection against accidental changes made to shared document types in the neighboring territory.
Configuring a territory to refuse updates is done at the local end of a gateway. If you want the Broker territories on both sides of a gateway to refuse updates, you must configure the setting from both sides.