Synchronizing Updates
If you turned on an update refusal setting for the local cluster and an update is made to a shared document type on the other side of the cluster gateway, all document flow to the local cluster stops. At this point, you need to synchronize the document types by using one of the methods described below:
For update refusals set on the local side of a gateway, deliver a document of the type that was refused to the remote side of the gateway.
Change the event type definition;
On the remote side of the gateway, revert the update back to the previous document type definition.
On the local side of the gateway, update the document type definition.
Turn off the update refusal flag.
After you synchronize the updates, document flow to the local cluster will restart.
Note:Broker Server issues alerts for event flow suspension and resumption.