Task | For more information, see... |
Ensure the cross-reference table is set up. | |
Define publishable document type for the notification documents that each source sends when the object being synchronized is changed. | |
Define an publishable document type for the canonical document, which describes the data change for all target resources. | |
Define logic on the source Integration Server to receive the source resource’s notification document, build the canonical document, and publish the canonical document. This includes the following tasks:  Create a trigger to subscribe to the source’s notification document. Note that you only need to create this trigger if the source publishes its notification document.Create a service that builds the canonical document from the fields in the source’s notification document and publishes the canonical document to notify targets of the data change. | |
Define logic on the target Integration Server that receives the canonical document and interacts with a target resource to make the equivalent change to the object on the target. This includes the following tasks: Create a trigger that subscribes to the canonical document that the source Integration Server publishes.Create an IS document type for the native document that the target Integration Server sends the target resource, so the target can make the equivalent change.Create a service that builds the target native document from fields in the canonical document. | |
If you are doing n-way synchronizations, add logic to perform echo suppression to the services you created for key cross‑referencing. |