Chat now with support
Chat with Support

Metalogix Replicator 7.4 - Product and Concepts Guide

Groups, Connections and Map Families

This section explains the relationship between groups, connections, and map families as you configure Replicator. Groups specify which connections are used to replicate changes in a network. Connections specify how web applications interact with each other. Map Families define what SharePoint changes are replicated and how often.

Consider a company with three web applications as follows:

·Corporate Office Portal, the primary intranet site for all employees located in North America.

·London Office Portal mirrors the Corporate Office and serves all employees located in Europe.

·Extranet Portal publishes a limited amount of information from the Corporate Portal that is intended for external use.

We want to design Replicator to replicate SharePoint changes as follows:


Groups identify which connections in a Replication Network will be used to replicate changes as specified by a map family. When defining groups, consider the following relationships:

·A map family only has one group.

·A group allows you to specify which connections fit within a map family.

·A single connection can belong to multiple groups.

The following illustrations show how group membership affects what is replicated between connected web applications. The red lines indicate that the connection is a member of the group used by the map family.

Bidirectional Replication

For bidirectional replication, both connections for a pair of web applications must belong to the same group. When you create the map family for Branch Offices Group on Corporate Office Portal, the map family is replicated to London Office Portal. Since the Branch Offices Group exists on London Office Portal, the map family also captures changes made to London Office Portal and replicates them along the same group to Corporate Office Portal.

One-way Replication

For one-way replication, the map family's group must only exist on the outbound web application. When the map family for the Extranet Group is replicated to Extranet Portal that group does not exist on extranet and so no changes are captured and replicated from Extranet Portal.

Related Documents