What Items Are Synchronized

In a multi-site deployment A configuration of a Loftware environment that includes Loftware instances located at different sites within the same WAN. In a multi-site deployment, each Loftware instance acts as either a headquarters or a facility. of Loftware Enterprise SP, objects in headquarters (HQ) The location of a Loftware Application Server and Loftware Database Server that are associated with facilities. These servers must be associated with a Loftware license for which Usage is set to Production and Multi-Site is set to true. Each HQ can communicate with multiple facilities. By synchronizing, an HQ can replicate objects to facilities and replicate transactional data generated at facilities back to the HQ. can be synchronized with objects at a facility An object in Loftware that represents the location of a Loftware Application Server and Loftware Database Server that are associated with a headquarters (HQ). These servers must be associated with a Loftware license for which Usage is set to Facility and Multi-Site is set to true. Each facility can communicate with only one headquarters. By synchronizing, an HQ can replicate objects to facilities and replicate transactional data generated at facilities back to the HQ.. Also, the transactional data generated at the facility can be synchronized with transactional data at the headquarters.

Note: Facilities and other functionality related to multi-site deployment are available only if your Loftware Enterprise SP license has the Multi-Site property enabled. Some options are displayed only if you are signed in to the headquarters site.

Configuration Sync Replicates Objects

Objects are replicated only from headquarters to facilities. If objects are created or altered at a facility, they may be replaced or deleted during synchronization to provide the facility with the most current configuration of objects from headquarters. However, to reduce the chance of extensive accidental deletion, folders that are replicated from headquarters to facilities and are later deleted from headquarters are not automatically deleted from facilities. Folders can be manually deleted at facility sites.

If you do not want objects from headquarters to replace some objects at the facility, you can restrict which folders and which types of objects are synchronized if you have the necessary permissions. You can also disable synchronization for an individual object at a facility.

Important! Because synchronization of objects is configured at both headquarters and facilities, if there are objects within a synchronized folder at a facility that you do not want to be changed or deleted when synchronization occurs, you must disable synchronization for those objects at the facility.

Tip: In most cases, disabling synchronization for an object at a facility prevents headquarters from synchronizing that object with that facility. However, if the object is moved or renamed at the headquarters, then the object at the facility is likewise moved or renamed, but is not otherwise altered. Also, if there is a conflict (not just a difference) between the headquarters and a facility, the object configuration from headquarters overrides that of the object at the facility as required to resolve the conflict.

By default, built-in folders and built-in objects are not replicated. Also, facilities, Remote Sites, and LDAP authentication information are not replicated. Although workflow templates can be replicated and then managed at facilities, workflows occur at headquarters. Workflow data (such as information about which step of the workflow an object is in) is not replicated to facilities and is not included in transactional data received from facilities.

Cross reference tables can be replicated by synchronizing the data services associated with them.

Transaction Sync Replicates Transactional Data

Transactional data is replicated from facility to headquarters only. If you have configured a facility so that printing is normally processed at the headquarters, there may not be much transactional data produced at the facility.

Although workflow templates can be replicated and then managed at facilities, workflows occur at headquarters. Workflow data (such as information about which step of the workflow an object is in) is not replicated to facilities and is not included in transactional data received from facilities.

Differences between Scheduled Sync and Manual Sync

When a scheduled sync occurs, only objects or transactional data that have changed since the previous sync are replicated. When you manually initiate a sync, all specified objects or transactional data are replicated, regardless of whether there have been any changes since the previous synchronization.