Integration Server 10.15 | Publish-Subscribe Developer’s Guide | Synchronizing Data Between Multiple Resources | For N-Way Synchronizations Add Echo Suppression to Services | Adding Echo Suppression to Notification Services
 
Adding Echo Suppression to Notification Services
 
Incorporating Echo Suppression Logic into a Notification Service
The echo suppression logic in a notification service determines whether a latch is open or closed before it attempts to build and publish the canonical document.
*If the latch is open, the resource is the source of the data change. In this case, the notification service on the source Integration Server builds the canonical document and publishes it. The notification service should include logic that closes the latch to prevent a circular update.
*If the latch is closed, the resource has already made the data change. In this case, the notification service does not need to build the canonical document to notify resources about the data change because the notification service on the source Integration Server has already done so. The notification service should simply re‑open the latch and terminate processing.
The following diagram highlights the part of data synchronization that this section addresses.