The In V6R2011, compression of synchronization streams had initially been introduced with an extension of the "sync businessobject mql" command and rules for compressed synchronization, which were added to the FCS Synchronization Server. With V6R2011x, the zipsync function further extends and automates the compression of synchronization streams for all synchronization scenarios, including:
A synchronization process occurring between two locations, or a store and a location, is considered to be WAN-wide (in other words, occurring in a WAN-environment) if the two locations, or the store and the location, belong to distinct sites. For example, assume there is a store with two locations, A and B. Location A belongs to site A and location B belongs to site B. Any synchronization that occurs between location A and location B is considered to be WAN-wide. A synchronization that occurs between the store and location A, or the store and location B, is also considered to be WAN-wide because the store belongs to the central site by default. If compressed synchronization is enabled, any WAN-wide FCS synchronization is compressed. More precisely, the files exchanged during the synchronization process are compressed. The FCS server that sends the file compresses the data (if it is not already compressed), and the FCS server that receives the file decompresses it. The compression function does not compress files that are already compressed, as this would cause a performance loss. FCS determines whether a file is already compressed or not by examining the file extension. With V6R2011x, compressed synchronization is enabled by default. In other words, after any V6R2011x setup or upgrade, compressed synchronization will be turned on. MQL provides commands to activate and configure compressed synchronization.
For example, you can configure the list of file extensions that specify whether files are compressed by using MQL commands. For details, see MQL Commands for Compressed Synchronization
and the command | |||||||