An application or application suite may have need to transfer data between the local client and another system, whether a server, or a peer. It may be transferring data to the local system because it needs to operate without benefit of a consistent connection to the server, or because the application prefers to deal with local data for performance reasons. Generally, this can be referred to as data synchronization. The synchronization could be two-way, in which data modification may occur on client and server, or one-way, in which data modification may occur on only one side or the other. Data synchronization generally requires some code to make the exchange of data. This might commonly or generically be called a Sync Engine.
The Sync Engine generally deals with the transfer of data, but when does the data transfer occur? How are the synchronization options configured? How are the synchronization tasks defined? By plugging the Sync Engine into the Sync Manager framework, one can take advantage of the Sync Manager.
The Sync Manager provides two main benefits to users of the Lotus® Expeditor platform:
- A common user interface for managing synchronization tasks including start, stop, schedule and configure
- A mechanism for the scheduling synchronization tasks for the platform
The Sync Manager does not actually do any synchronization itself -- it interacts with the contributed Sync Engines to perform the synchronization. A Sync Engine must be provided in order to use Sync Manager for data synchronization.
Parent topic: Using Sync Manager: XPD622