Navigation:  Add2Exchange Administration Guide > Synchronization Concepts >

Synchronization Profiles

Print this Topic Previous pageReturn to chapter overviewNext page

Important

As of version 5.6 of this manual, there is an important terminology change.  Formerly, the terms one-way and two-way were used to describe mutual relationships (see Folder Grouping).  These terms are now used to describe profiles and mean the same thing as unidirectional and bidirectional.

A synchronization profile is the collection of trigger settings which define the general behavior of a relationship.  The profile is a set of relationship settings made in coordination with each other to achieve one of the synchronization models.

A relationship is not required to conform exactly to the profiles discussed here and there is no individual "profile setting".  The term "synchronization profile" just represents a useful collection of settings.

While relationship settings are independent of one another, they are generally set in coordination to achieve one of two kinds of behavior: one-way or two-way.  One-way and two-way profiles typically share the same behavior for adds, edits and deletes in the source folder.  Changes in the source are synchronized to the destination folder.

The profiles differ in how they treat edits and deletes to copies in the destination folder.  (Adds to the destination aren't considered here because they are never subject to the relationship.  See the section Relationship Fundamentals to understand why this is the case.)

One-way relationships prevent edits and deletes of replicas in the destination from affecting the originating items.

Two-way relationships allow edits and deletes of replicas in the destination to be reflected by the originating items.

Documentation Convention

Further examples of synchronization behavior use logos to represent whether they are part of a one-way profile, a two-way profile or both kinds of profile.  Examples may illustrate one or both kinds of behavior.  In each of the following examples, both logos will appear, but if one doesn't apply to the example it will be crossed out.

One-way:  

Two-way:  

The following table summarizes typical profile behavior.  Note that a relationship may be configured to give a hybrid of the two behaviors.  The triggers shown are for replicas in the destination folder only.


One-way

Two-way

Edits

Discard edits to the replica and reset to match originating item.

- or -

Preserve modifications and make a new replica.

Synchronize edits back to the originating item.

Deletes

Make a new replica of the originating item

- or -

Keep originating item in source but don't recopy

Delete the originating item.

One-way Synchronization

One-way synchronization generally means that changes to destination replicas are prevented from affecting the originating items.  What happens to the modified replica depends on the relationship settings.  One-way behavior usually means that edits are discarded.

Edits are made to a replica in the Private Mailbox.

Changes do NOT synchronize to the originating contact in the Public Folder.

Instead a new replica is made in the Private Mailbox, replacing the modified copy.

An example of an alternate setting that is still considered one-way is to preserve a modified replica and create a new copy.

When a replica is modified under this configuration, the originating contact and modified replica are dissociated from each other.  The copy is no longer considered a replica since it is not subject to the relationship and is no longer synchronized with the originating item. A new replica is made which follows the usual synchronization rules.

Edits are made to a replica in the Private Mailbox.

A new replica is made alongside the modified one in the Private Mailbox.

Be Aware

Because the former and new replicas appear similar (except for the hair), they are sometimes mistaken for duplicates.  Educate your users about this issue when using this configuration.

The delete trigger in a one-way relationship also has multiple settings.  The usual behavior is to recopy the originating item to the destination, effectively preventing the deletion.

A replica is deleted from the Private Mailbox.

A new replica is made in the Private Mailbox.

An alternate setting that is still considered one-way is to allow the replica to be deleted.  The originating item is unaffected but will not be copied to the destination in the future, even if it is modified.  This is called pruning.

A replica is deleted from the Private Mailbox.

The originating contact in the Public Folder is NOT deleted.  It is also not recopied by subsequent synchronization.

Two-way Synchronization

Two-way synchronization means that changes (edits and deletes) of destination replicas are synchronized back to the originating item in the source.

Edits are made to a replica in the Private Mailbox.

Changes are synchronized to the originating contact in the Public Folder.

A replica is deleted from the Private Mailbox.

The originating contact in the Public Folder is also deleted.

blog comments powered by Disqus

 


Page url: http://guides.diditbetter.com/a2e-guide/synchronization_profiles.htm