The concept of publish (pub) and subscribe (sub) is similar to that in JMS, which can be said to be a core part of data synchronization in WebMethods.
There are two main aspects of Pub&sub: local and distribution
The local pub&sub is done in one is, not involving the broker, the implementation is relatively simple, the basic steps are: establish a notification to the source data source monitoring, if the data source changes, the specified call a service p Synchronization of the target data source is implemented in service p by invoking the adapter service of the target data source.
The more complex is the data pub&sub involved in the broker. WebMethods provides us with the key cross-refrence and the Echo suppresion to support it. Key Cross-refrence completes the document record, while Echo Suppresion is provided for bidirectional synchronization to avoid duplicate synchronizations.
In WebMethods's design, the information for key cross-refrence and the Echo suppresion is stored in a single table that records the basic information (KEY) of the broker's document and whether the lock (echo suppresion).
Specific concepts and system processes are detailed in the official guideline, and if necessary, I'll put some of these notes in the future.