Integration Server 10.15 | Publish-Subscribe Developer’s Guide | Synchronizing Data Between Multiple Resources | Data Synchronization with webMethods
 
Data Synchronization with webMethods
 
Equivalent Data and Native IDs
Canonical Documents
Key Cross-Referencing and the Cross-Reference Table
Echo Suppression for N-Way Synchronizations
To perform data synchronization with webMethods, when a resource makes a data change, it notifies Integration Server by sending a document that describes the data change. If the source resource is using a webMethods adapter, the adapter can send an adapter notification that describes the data change.
The data from the source is typically in a layout or structure that is native to the source. You set up processing in Integration Server that maps values from the notification document to build a common‑structure document, referred to as a canonical document. Each target receives the canonical document, which they use to update the equivalent data on their systems.
The following diagram illustrates the basics of performing data synchronization with webMethods software.
Step
Description
1
The source resource makes a data change.
2
Integration Server receives notification of the change on the source. For example, in the above illustration, an adapter checks for changes on the source. When the adapter recognizes a change on the source, it sends an adapter notification that contains information about the change that was made. The adapter might either publish the adapter notification or directly invoke a service passing it the adapter notification.
For more information about adapter notifications, see the guide for the specific adapter that you are using with a source resource.
3
A service that you create receives the notification of change on the source. For example, it receives the adapter notification. This service maps data from the change notification document to a canonical document. A canonical document is a common business document that contains the information that all target resources will require to incorporate data changes. The canonical document has a neutral structure among the resources. For more information, see Canonical Documents.
After forming the canonical document, the service publishes the canonical document. The targets subscribe to the canonical document.
4
On a target, the trigger that subscribes to the canonical document invokes a service that you create. This service maps data from the canonical document into a document that has a structure that is native to the target resource. The target resource uses the information in this document to make the equivalent change.
5
The target resource makes a data change that is equivalent to the change that the source initiated. If the target resource is using an adapter, an adapter service can be used to make the data change.
For more information about adapter services, see the guide for the specific adapter that you are using with a target resource.