Replicator 7.4 - Firewalled Replication

Windows Server 2003

1.For each web application server on the farms inside and outside of the firewall, install the Microsoft components required by Replicator for Windows Server 2003. These components are described in the Metalogix Replicator Quick Start Deployment Guide.

2.For each web application server in the farm outside the firewall, install BITS Server Extensions. For instructions, see http://technet.microsoft.com/en-us/library/cc740133%28WS.10%29.aspx.

Configuration Overview

The configuration for firewalled replication only affects how you set up your Replication Connections between web applications. All other aspects of configuring and managing Replicator are unchanged. For the complete steps required to configure replication, see the Metalogix Replicator Quick Start Deployment Guide.

When you create a connection from the web application inside the firewall and select the Firewalled replication mode, Replicator automatically creates a connection for the other web application. Since the other web application cannot communicate with the web application inside the firewall, the automatically created connection does not require any credentials for the web application inside the firewall.

The following sections highlight the specific steps you must perform to configure firewalled replication depending on your replication scenario.

Configuring One Way Replication with the Source behind a Firewall

In this scenario, the target Replicator instance (Extranet Portal) cannot download packages from the source web application (Corporate Portal) because of the firewall. The source Replicator instance must upload files to target using the server extensions.

To configure Replicator for this scenario:

1.Enable the web application on the inside of the firewall.

2.Set a passphrase for the web application outside the firewall under Advanced Settings before enabling the web application. If the web application was already enabled, then set the passphrase, disable, and then re-enable.

3.On the web application inside the firewall, create a Replication Group for one way replication. This group cannot exist on the other web application.

4.On the web application inside the firewall, create a Replication Connection to the other web application. The connection must have the following settings:

a.Under Target Web Application enter the passphrase which was set for the web application in step 1.

b.Under Selected Replication Groups, select the group you created in step 3.

c.Under BITS Transport Settings and Replication Mode, select Firewalled.

By specifying the firewalled replication mode, Replicator automatically creates a Replication Connection on the other web application for replication.

5.On the web application inside the firewall, create a Replication Map Family that specifies the SharePoint changes you want to replicate. Configure the map family to use the group created in step 3.

After completing these steps, changes made to the web application inside the firewall are replicated to the other web application.

Configuring Bidirectional Replication with a Firewall

In this scenario, the Replicator instance outside the firewall (London Branch Portal) cannot download packages from the web application inside the firewall (Corporate Portal). Nor can it inform the Replicator instance inside the firewall that packages are available for download. The firewalled Replicator instance must upload files to the other instance using the server extensions and must also regularly poll the web application outside the firewall for available packages.

To configure Replicator for this scenario:

1.Enable the web application on the inside of the firewall.

2.Set a passphrase for the web application outside the firewall under Advanced Settings before enabling the web application. If the web application was already enabled, then set the passphrase, disable, and then re-enable.

3.On the web application inside the firewall, create a Replication Group for bidirectional replication. You can also use the preconfigured Worldwide Connections group.

4.On the web application outside the firewall, create a Replication Group with the same name as the one created in step 3.

5.On the web application inside the firewall, create a Replication Connection to the other web application. The connection must have the following settings:

a.Under Target Web Application enter the passphrase which was set for the web application in step 1.

b.Under Selected Replication Groups, select the group you created in step 3.

c.Under BITS Transport Settings and Replication Mode, select Firewalled.

By specifying the firewalled replication mode, Replicator automatically creates a Replication Connection on the other web application for replication.

6.On the web application outside the firewall, edit the automatically created Replication Connection. Under Selected Replication Groups, select the group you created in step 3.

7.On either web application, create a Replication Map Family that specifies the SharePoint changes you want to replicate. Configure the map family to use the group created in step 3. Since the group exists for both web applications, Replicator automatically configures the other web application to use the same map family for bidirectional replication.

After completing these steps, changes made to either web application are replicated to the other web application.