The synchronization process takes place whenever a connection between the two systems is established and configured. Before you proceed, we recommend that you take a look at a brief overview of the synchronization process to find out how things work behind the scenes.
The synchronization process involves four main components - two task management systems that host the data that you want to sync, and two Exalate Nodes. The Exalate Node connected to each task management system acts like a gateway and is responsible for:
- Detecting the fact that the data “under sync” has been changed or new data needs to be brought “under sync”
- Extracting the relevant data from the tracker and formatting it as a structured message-replica
- Exchanging the data with other nodes connected to the network
- Applying incoming messages locally in a way that makes sense, either updating the existing entity or creating a new one
How the Exalate Nodes Interact with the Platforms and their Data?
- Exalate Node (Blue) interfaces with instance(Blue) for retrieving Incident information
- It either polls instance (Blue) for any changes since the last full synchronization or gets triggered by instance (Blue) stating that a change has occurred.
- Then it collects all the relevant Incident information and composes a message.
- Exalate Node (Blue) sends the message to Exalate Node (Red) for further processing.
- Exalate Node (Red) decomposes the message and applies the message to the instance (Red), such as updating an issue summary
- Exalate Node (Red) interfaces with instance (Red) to retrieve the changes which have been triggered by the synchronization and composes an acknowledgment message.
- Exalate Node (Red) sends the acknowledgment message back to Exalate Node (Blue).
- Exalate Node (Blue) processes the acknowledgment message and applies it to instances (Blue).
Outgoing and Incoming Sync Processors
Outgoing and incoming sync processors are basically the messages that Exalate nodes exchange during the synchronization process.
With the outgoing sync processor, you can specify what information can be sent to the destination instance. Exalate runs the outgoing sync processor when you start the synchronization or update the local issue which is under sync.
The incoming sync processor contains information on how to handle incoming data from the remote instance. Exalate runs the incoming sync processor every time there's new data received from the remote side.
You can define what data should be sent and how to handle it on the destination instance with the help of the Outgoing and Incoming Rules.
The Step-by-Step Synchronization Process
- The synchronization process starts with one of the available triggers: operation, trigger, API, post function, or through polling for change.
- Exalate runs the outgoing sync processor and extracts a replica from the entity.
- The outgoing sync event is registered in the Sync Queue.
- The outgoing sync event is then sent to the destination instance.
- The incoming sync request is registered in the Sync queue on the destination side.
- Exalate runs the incoming sync processor with the received message and applies the change to the local entity.
- Exalate runs the destination instance outgoing sync processor to create an acknowledgment message and sends this message to the source instance.
- The act of synchronization is completed and all sync operation data is cleaned.